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
Related
Well I was trying to put the MR2 radio on and flash over the BAMF 3.0 rom but accidently put the stock verizon IMG file back on. I lost root and as far as I know it's back to a stock phone. Well trying to root with the 1 click version because I dont have the time or patience for ADB right now but I can't get it to push any files. Keeps saying that there's an Error and throws the phone into bootloader.
if anyone could help me get rooted and BAMF back on it'd be GREATLY appreciated.
To my understanding you should not have lost the root. you simply need to download the right MR2 radio, put it in your Root SD and get into recovery. If you can't do it through your rom manager then do it manually by holding the power button and volume up. Select the right radio, reflash bamf 3.0 and reboot. I'm still learning myself, but from some of the mistakes I have made in the past, this seems as if it should work for you.
Alright i got the files to push now, after yelling and screaming obscenities at my phone lol. But now when its just about to finish it says "update failed main version older"
I lost EVERYTHING, i have no root access, S-ON, no root access via ROM manager
again I'm not the most advanced techy, but I would suggest plugging in your phone via USB, downloading the right MR2 again and re-downloading the bamf 3.0 again as well. ( When I run into a problem I like to know that I'm starting with a fresh canvis). put both into Root of SD, get into Clockwork and update the MR2. Once you have that updated, reboot. then reflash the Rom, Reboot. run your Titanium backup (Just apps not system data). Reboot normal and I would think you would be good to go. I'm sure someone will pipe up if I'm wrong, but thats what comes to mind for me.
I skimmed over and didn't see that you said you installed the stock verizon radio. I am not experienced enough to give advice from here and feel confident I was telling you the right thing to do. My guess is since you installed the
PG05IMG file, it now has the S-on and you will need to root again. Did you try the power button and volume up?
....
I got it to push files but then when update of the NEW rooted update ends it says update failed main version older
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
bandtrumpet7 said:
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
Click to expand...
Click to collapse
Well you shouldn't panic. Which radio did you flash? I would flash the MR2 one from this link http://forum.xda-developers.com/showthread.php?t=1154010 . If that doesn't work, I would download the rom directly from Synergy here http://androidfilehost.com/XxXViRuSXxX/roms/synergy/thunderbolt/
From recovery, wipe everything manually (Wipe data/cache/dalvik) than flash the file from where it is on your SD card. If you need specific instructions feel free to ask.
bandtrumpet7 said:
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
Click to expand...
Click to collapse
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
loonatik78 said:
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
Click to expand...
Click to collapse
Sure hope he's just confused...
loonatik78 said:
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
Click to expand...
Click to collapse
Lol I saw that, I decided not to say anything, I guess you have the sharper tongue than me
Ya pretty scary. I'm hoping he meant he rooted his phone and when he said unrooted, he meant "stock" froyo build on his phone.
Sounds like he is able to boot up, just not get any signal.
I'm guessing he is not too skilled in the ways of Android yet.
Lol just found something interesting. Synergy isn't even on rom manager? I was checking to see if the version ofcsynergy he was using was a previous froyo build, and I can't even find it on rom manager
He probably meant that he used Rom Manager to load the rom rather than using recovery.
haha weird
OK, so I was tired when I wrote my initial post, and I probably didn't make a whole lot of sense. Let me be a bit clearer.
For reference, no, I'm "not too skilled in the ways of Android yet". I've been living with Froyo, anxiously awaiting Gingerbread, and then got fed up and read about all the benefits that come with rooting. Now that an easier method has presented itself - the Revolutionary method, as opposed to opening a command prompt and doing the adb stuff, which I can do - I rooted a friend's phone - but decided to not take the plunge myself - I decided to go ahead and give GB a shot.
So let me break down what happened:
- My phone was unrooted previously, running the same software it came with. I'd done a few OTA updates that Verizon provided but had never gone into my phone. That's why I called it "stock", sorry if that terminology confused people. I just meant it was the OS that came on my phone - Android 2.2 w/ HTC Sense and all that jazz.
- I ran the Revolutionary method posted in the "Thunderbolt Android Development" forum. Worked fine. Ran Recovery and installed Superuser permissions as the documentation said. Worked great. Have a phone where if HBOOT launches, it says -Revolutionary- at the top, and it's got -S OFF. My phone technically is rooted.
- The Synergy mod was also posted in the "TB Android Development" forum. I downloaded that and installed it using ROM Manager (Install ROM from SD). Worked fine ... but then had no signal. Every other aspect of the phone seemed to be working. My radio just wasn't working.
- Downloaded an updated radio from the TB Android Dev. forum, ran that, it said it was updating the radio. Rebooted the phone after the update ... still no signal.
I "solved" this problem by flashing the leaked HTC/TB Gingerbread build, the latest one that was like 400 MB, and when I booted my phone up again I had Gingerbread on my phone with HTC Sense 2.1, and I had signal. So I'm living right now with a fully working phone, but I wanted to dip my foot into custom ROMs. So now I have a backup method just in case the radio thing doesn't work again, but what can I do to install a custom ROM and ensure that I get signal?
Thanks for the response, xebryus - and to everyone else, sorry I was a little confusing. Everybody starts from somewhere, right?
-BT7
Download the GB ROM you want, boot into clockwork (please don't install VIA ROM Manager). In clockwork using you Volume keys to move and the Home button to select....
Select Wipe Data/Factory Reset
Select Wipe Cache
Select Advanced
Select Wipe Dalvik
Select Go Back
Select Mounts and Storage
Select Format /system
Select Go Back Until you are at the first screen
Select Install from SD Card
Select Choose ZIP
Go to the folder where you downloaded the ROM
Select ROM
Select Yes.
When it is done Reboot.
Enjoy!
Sent from my SHIFTAO5P using XDA App
Hey, at least you didn't brick your phone, so kudos for you for getting that far.
As others have stated there are basically two kinds of radio versions out there. One that work with Froyo builds and ones that work with GB builds.
So depending on the rom you are loading, you just have to make sure you have the right radio to match the rom(the rom thread should tell you what radio it requires). From what you were saying, it sounded like you just had the wrong radio.
Anyways, couple of things you want to make sure you do. Any check to make sure the checksum is correct on the radio (so that it's not corrupt) otherwise you could have some major issues. Also, once you flash the radio and you get your phone back up, make sure to either rename or delete the PG05img file from your SD root, otherwise, again a major hassle.
Check out the noob thread at the top of this forum also. It has great info there that will help you on your journey.
Good Luck.
I have always felt more in control flashing from recovery or hboot but I'm curious why no rom manager?
Sent from my Tbolt running Das Bamf 3.0...
RevosFTS said:
I have always felt more in control flashing from recovery or hboot but I'm curious why no rom manager?
Sent from my Tbolt running Das Bamf 3.0...
Click to expand...
Click to collapse
When the TB first came out, it seemed that people were having issues with using rom manager to flash roms (alot of force closes, things in general not working correctly). So many experienced people said to use recovery rather than rom manager to flash anything on the TB.
I guess that idea just kinda stuck after that.
Ok thanks. I will still use recovery anyhow I am more used to it. Plus I'm kinda old school I love adb haha
Sent from my ADR6400L using XDA App
I have downloaded Synergy Rom and have no problems except that I am not able to get the radio to flash. I am on verizon and chose the MR3.5 radio. I did a battery pull and then pressed the power and volume down button to enter HBoot but I do not have an option to Upgrade. What am I doing wrong any help is appreciated. I need help quick, thanks!!!
1more thing when i am in the HBoot window my only options are Fastboot, Recovery, Factory Reset, Simlock, Hboot USB, System Info, Image Crc..... it says radio is 1.16.00.0402w.
Does this mean the radio was already upgraded. Why can I not get a signal then?
Did you rename the .zip and have it on the root of your SD card?
Sent from my ADR6400L using XDA App
HarlyFan said:
1more thing when i am in the HBoot window my only options are Fastboot, Recovery, Factory Reset, Simlock, Hboot USB, System Info, Image Crc..... it says radio is 1.16.00.0402w.
Does this mean the radio was already upgraded. Why can I not get a signal then?
Click to expand...
Click to collapse
Nope..402w is still MR1. Sounds like you are already in bootloader so at this point if it isn't updating then more than likely the file is named incorrectly as stated above.
Radios HAVE to be named PG05IMG.zip (3rd character is a ZERO, not the letter "O"). It HAS to be in the root folder of your SD card. Now, turn the phone OFF.
Next, hold down the VOL-DOWN button. Keep it held down. Is it still held down ? If so, push and hold down the POWER button. When the screen turns on, you can release both. This menu will automatically look for 3 or 4 files with certain names. One of the names (files) it looks for is .... PG05IMG.zip. When/if it finds it, it will check it and ask you if you want to load it. Tell it to load it and then leave your phone alone. It will update it and reboot like normal (if successful).
Does the thunderbolt need to be rooted to upload a stock PG05IMG from my SD card? Im trying to load PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_release_174685_signed.zip from my SD card as my handset is stuck at the bootup screen, thus wont reload through an RUU.
The phone was previously rooted by someone else and I did a system clear through the clockwork recovery (Version 3.1.0.2) menu to wipe their info. Afterwards, it only showed the bootscreen. Oops....
Ive tried to load the aforementioned file through the bootloader screen by renaming it PG05IMG.zip, etc, but the phone keeps rejecting it.
killgorian said:
Does the thunderbolt need to be rooted to upload a stock PG05IMG from my SD card? Im trying to load PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_release_174685_signed.zip from my SD card as my handset is stuck at the bootup screen, thus wont reload through an RUU.
The phone was previously rooted by someone else and I did a system clear through the clockwork recovery (Version 3.1.0.2) menu to wipe their info. Afterwards, it only showed the bootscreen. Oops....
Ive tried to load the aforementioned file through the bootloader screen by renaming it PG05IMG.zip, etc, but the phone keeps rejecting it.
Click to expand...
Click to collapse
What exactly are you trying to do? Completely unroot the thing and put S-On? I'd like to be sure before I dole out instructions. And why such an old RUU? Why not the 1.70 RUU. And how was the Tbolt rooted and S-Off'd before?
Honestly, Im just trying to get it to boot again as easily as possible. I dont care if it's rooted, unrooted, anything, I'd just like it to work.
I grabbed the old RUU because I figured I could update from there. It actually makes no difference to me at this point what's on it, I just want it to work again. lol
killgorian said:
Honestly, Im just trying to get it to boot again as easily as possible. I dont care if it's rooted, unrooted, anything, I'd just like it to work.
I grabbed the old RUU because I figured I could update from there. It actually makes no difference to me at this point what's on it, I just want it to work again. lol
Click to expand...
Click to collapse
I hope wiser minds than mine chime in, but I don't think flashing an old RUU would be wise if Revolution was used. Revolution replaces the hboot and I don't think flashing a new RUU replaces it. I'm not sure what bad would come of it, actually.
It sounds to me like you just need to flash a new ROM. I don't know what radios you have, but you probably have newer ones since those are the radios of choice for newer ROMs. I'd try that first. If that doesn't do it, then I think what needs to happen next it to figure out what hboot you have. If it was done via the jcase method, then flashing an RUU should work fine. If not, well... I'm not an expert on that front, but there are threads on that subject. I wish I could dish out a real simple answer, but I'm not sure it so simple.
Definitely sounds like all that is needed in the OP's case is to flash a new ROM (custom or stock) from recovery as loonatik suggested or possibly restore a backup if one exists. Just sounds like /system was formatted and nothing flashed afterwards.
Absolute_Zero said:
Definitely sounds like all that is needed in the OP's case is to flash a new ROM (custom or stock) from recovery as loonatik suggested or possibly restore a backup if one exists. Just sounds like /system was formatted and nothing flashed afterwards.
Click to expand...
Click to collapse
Thanks for confirming. If you can hold volume-down while powering it up and get into ClockworkMod, flashing another ROM is just a matter of a few button pushes.
Exactly what I thought. I've loaded custom roms on the a855 and Eris before, but the above file won't load. I'm wondering if the bl is locked but it has clockwork, so I'm confused...
That's an entire RUU. That's why. Go get just a ROM and flash through clockwork.
Hey just wanted to say that worked and thank you very much. I am a bit curious however as to why the full RUU didnt work...
killgorian said:
Hey just wanted to say that worked and thank you very much. I am a bit curious however as to why the full RUU didnt work...
Click to expand...
Click to collapse
A full RUU contains a LOT more than just a ROM. It must also be flashed differently; through the bootloader and not recovery. An RUU contains a new bootloader and radios, as well as a ROM. If you'd flashed that RUU correctly through the bootloader, you probably would have lost S-Off and root, or ended up with a device that did even less desirable things... like bootloop.
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Edit: Nevermind, it seems to be good to go. Thanks again for the help.
killgorian said:
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Click to expand...
Click to collapse
in the rom thread most devs put what radios are compatible and a link to the radio. Not sure how new plainjane is, but most of the newer radios work with all the custom roms.
killgorian said:
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Click to expand...
Click to collapse
If you used Revolution or updated to the patched bootloader, it's designed to not allow flashing over. That's probably why it failed.
Before I do anything else to screw this up!
I'm sitting at an exclamation in a triangle
here what I did..
1. installed stock/rooted rom
2. used clean flash to put on stock recovery
3. ran OTA Keeper to back up root
4. downloaded and started OTA update
it then rebooted and began but then Red Exclamation In A Triangle
anyone know where I should go or what I should do from here?
Thanks.
If your pc detects the phone- you'll prob have to do an ruu.exe to get it totally stock and then start over.. I did it earlier but I was having a diff problem (stuck in hboot)-- never got triangle/exclamation. I used the ruu from scottsroms (1.02.605.6).
yeah ok... I'll look into that. I haven't turned it back on yet.. Thanks
Just realized i forgot to "un-root" with the OTAKeeper app... I'm hoping that's what I did wrong. It booted back to where i was and said the update failed. So... I'm a tryin' again.
Thanks for the reply.. One can feel soooo alone when making mistakes
There's some other information in the OTA threads in "general" of others that have had the red triangle and were able to work around it.. I didn't read the specifics but check in there.
das0527 said:
7. Enjoy OTAed, unlocked, rooted kickassness of my Rezound while bouncing off the walls waiting for ICS.
Click to expand...
Click to collapse
Why wait?
I'm going to run through those steps later and check out the other threads. I'm able to get back to my phone as the update looks to of just been aborted....
If you guys don't have wives, keep it that way, I want to work on this all day but...... so I'll check in later and post how it goes. I don't see why those steps won't work though... Thanks a ton guys.
I planned on waiting until the official build of ICS & Sense is released OTA, especially after today's news about the new features in Sense 4.0, which I'm actually extremely impressed with.
Cool- well I'm sure you've already read elsewhere- but you can't really go wrong w/ any of the custom ics roms in the dev section. If you can handle a very occasional screen flicker every once in a while they're pretty much perfect.
reggie cheeks said:
Before I do anything else to screw this up!
I'm sitting at an exclamation in a triangle
here what I did..
1. installed stock/rooted rom
2. used clean flash to put on stock recovery
3. ran OTA Keeper to back up root
4. downloaded and started OTA update
it then rebooted and began but then Red Exclamation In A Triangle
anyone know where I should go or what I should do from here?
Thanks.
Click to expand...
Click to collapse
Did you lock the bootloader?
Sent from my ADR6425LVW using xda premium
No. I didn't. That was my mistake. Dumb of me. I'm gonna do the ruu and start over later, I'm out n about.
Sent from my ADR6425LVW using Tapatalk
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
esheesle said:
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
Click to expand...
Click to collapse
Had Ineffabilis from 12/29, was great, put Clean ICS on it from 1/24, worked well except for the bluetooth pain in the patookie. (and I use bluetooth ALOT)...
I flashed back to GB, I have Team Bamf on mine right now because it included the kernel. I am getting ready to put clean rom on it with the new main ver but I would like to put the new radio's on it first.
Can I put the new radio's on it without going through the steps above (flash stock, re lock, ruu, ota update, unlock, flash, etc) and if so how?
Thanks!
Figured it out. Gonna make a post.
esheesle said:
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
Click to expand...
Click to collapse
Right now I'm on Vigor Stock Rooted WWE 1.02.605.6 Deodexed . That's my mistake, right? I've got all the bloat.
Sent from my ADR6425LVW using Tapatalk
It's possible the deodexed part of it is the problem.
Do you have a nandroid made from right after you flashed Amon Ra recovery? Also, did you flash a stock recovery or do you still have Amon Ra? It won't work unless you have stock recovery.
If you don't have a nand, you can either run RUU (if you don't have the updated mainver issue) or have a look in this thread:
http://forum.xda-developers.com/showthread.php?t=1467329
con247 has made a stock ROM with the OTA in it so you don't have to download the update.
There aren't any instructions on what to do with the file you download and I didn't use his method so I can't really help but hopefully you'll get it. I don't remember it being spelled out in the thread anywhere which is why I decided it was just as easy for me to use my nand and flash a stock kernel and recovery and download it myself.
I had stock recovery and kernel at the time I ran the update. I've since went back to amon and I've downloaded vigor ota stock rooted and I was about to try that.
Oh and...I'm pretty sure my earliest back up was not my original, I think I made the mistake of flashing a Rom before my first backup
I do however really wish I had some instructions for the vigorotastockrooted.
& one last thing.. Ive never had mainver update.
Sent from my ADR6425LVW using Tapatalk
Yeah, I wish there were instructions for that stock + OTA too.
The OTA will update your mainver but to the official release that is in the OTA. Just so you know, I can now not flash the dbs kernel I was using before because I'm getting a "mainver is older" message.
I was trying to reflash kernels because my wifi is not working now, when I select "turn on wifi" that changes to "error". I had restored my nand of the Innedfabilis ROM I made right before reverting to stock and updating with the OTA. Just mentioning it since I'm posting here to try to help you and I guess it's just full disclosure.
Hmm. I'm thinking of sticking pre-ota as well, at least until I feel more confident about it. Thanks
Edit.... I ended up using con's vigorOta and xtreme tools (for simpler lock/relock) to update . Thanks for the help/insight!
Sent from my ADR6425LVW using Tapatalk
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.