• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Going back to stock without losing Root?

O

offanairplane

Android Enthusiast
So I rooted my bolt using the Revoultionary method, and I've tried a couple of different AOSP roms, which I prefer, and both have been buggy enough that I can't use them for my daily driver (and really I am not a ROM swapper, I find one that works, and stick with it.)

So I want to go back to the stock ROM, but I don't want to lose root, because I have apps that require root.

If I flash an RUU file, like the ones here:
[ROM]Mecha Shipped Rom Collection - xda-developers

Will I lose root? Will it overwrite my bootloader? Will I lose my custom recovery?
I suspect that I would lose root. Correct me if I'm wrong.

But if that is the case, is there a way to install the current stock rom and not lose root?

Thanks!
 
You did not state which AOSP roms you tried but I can tell you I'm on Liquid's 3.2 and have not experienced any problems yet. As far as a stock rom that is rooted, you can try this. It's a debloated and rooted stock rom from the latest RUU.
 
Papadroid said:
You did not state which AOSP roms you tried but I can tell you I'm on Liquid's 3.2 and have not experienced any problems yet. As far as a stock rom that is rooted, you can try this. It's a debloated and rooted stock rom from the latest RUU.
Click to expand...

First I tried OMGB, which was flawless on my Incredible, but has several major bugs on the T-bolt.
Only one side of the headphone jack works (left side) and when I am talking on the car handsfree wired kit, the person talking sounds very high pitched and weird, but playing audio sounds fine (other than the right channel not working) which is weird.

And currently I am on Liquid 3.0, and it has a couple of bugs. ( I just downloaded it a couple of days ago, so is 3.2 brand new?)
1. When I am plugged into my car handsfree rig (which is wired) it makes a weird static noise that the person I am calling can hear but I can't. And it comes and goes. I never had that issue with my incredible or with my tbolt on the stock rom. I did have a similar issue running OMGB on my tbolt as well, though not identical.

2. Yesterday on the way home from work, I drove through several areas that have always had a strong 3G signal, but now even have a strong 4G signal. But I had no signal at all, not even 1X. I couldn't even make a call. The voice (CDMA?) signal came and went but the data never came back. So I rebooted into recovery and wiped the caches, and rebooted again. Then it seemed to work better, but still no 4G. I don't know when it happened because I'm on Wifi at work all day, so only when I was driving away and got out of the Wifi range, did it try to switch to 3G, but failed.

So, I'm getting frustrated, and ready to just say that the Thunderbolt hasn't been out as long as the Incredible, so that is why even the best ROM's still have bugs that haven't been all ironed out yet. And just go with the stock rom, until later.

Even now, I nand-restored back to OMGB and I have a 3G signal at my desk (a weak one, but that is normal).

And I backed up right before I did that, so now I restore back to Liquid and....ok, now I do have 3G again. I guess it's possible that could've been a network issue, but I drove a long way, and it didn't change at all. I had zero connectivity. I switched to airplane and back a few times, thinking that would force it to reconnect, but nope. In about 10 years as a verizon wireless customer I've never seen that before, so I'm not saying it's not the network, but I'd be surprised if it were.

And I have one more question about liquid.
I have read that the CM7 team still hasn't gotten 4G working on their ROM, nor does OMFGB. So how does Liquid have it already?
And when I'm on 4G it doesn't seem to be much faster if any than 3G.

Does Liquid 3.2 fix any of the problems I mentioned I'm having on Liquid 3.0?


Thanks for your help!


edit: And now I am connected to Wifi and it still shows the 3G icon at the top, and when I do something like refresh my facebook widget, the 3G arrows light up. Why would it be using 3G at all if I'm on Wifi? It never has in the past.
 
I'm not sure I can answer all your questions, all I can say is that yes 4G does work on AOSP Roms including CM7 and Liquid. I have not noticed any audio problems on 3.2 but YMMV. I do know that yesterday Phandroid posted an article that there was a massive data outage for Verizon both 3G and 4G. Maybe that was your problem yesterday. I know that on occassion I have not data for brief periods of time but that has been across all roms including sense roms based off of stock.
 
I dont have any of those issues on cm7. It works great for me.

If you really want to be stock again,first option is simply flash the rooted stock rom linked Above.

Second option is to flash the ruu. It will remove root and your custom recovery,but the revolutionary will remain. All you'll need to do is reflash recovery,then reflash superuser in recovery.

The revolutionary hboot will always block other things from overwriting it. It will remain until you remove it purposely :)
 
Papadroid said:
I'm not sure I can answer all your questions, all I can say is that yes 4G does work on AOSP Roms including CM7 and Liquid. I have not noticed any audio problems on 3.2 but YMMV. I do know that yesterday Phandroid posted an article that there was a massive data outage for Verizon both 3G and 4G. Maybe that was your problem yesterday. I know that on occassion I have not data for brief periods of time but that has been across all roms including sense roms based off of stock.
Click to expand...

Maybe so, but reading through the Liquid 3.2 ROM page, there are a lot of other bugs apparently. I want to try it, because it looks pretty sweet to me. But I just don't want a buggy rom. I don't want the stock rom either. I just want a really solid AOSP rom.

I'll give 3.2 a try and see how it goes.


Interesting about the data outage. That would explain it.
 
scotty85 said:
I dont have any of those issues on cm7. It works great for me.

If you really want to be stock again,first option is simply flash the rooted stock rom linked Above.

Second option is to flash the ruu. It will remove root and your custom recovery,but the revolutionary will remain. All you'll need to do is reflash recovery,then reflash superuser in recovery.

The revolutionary hboot will always block other things from overwriting it. It will remain until you remove it purposely :)
Click to expand...

Well, I certainly don't want to Unroot. I have apps that require root that I want to keep using. I am not being a smarty or anything, because I do appreciate the help, but even the title of the thread says I don't want to lose root. lol

I really don't want the stock Rom either. I just want a very stable GB rom. And so far, the stock one has been the most stable on my TB.


edit:
Option 2 sounds like the one for me. But I will try Liquid 3.2 with all the fixes applied, and if that one still bugs out on me, it will be back to the stock rom for me.


Thanks for the help.
 
offanairplane said:
Maybe so, but reading through the Liquid 3.2 ROM page, there are a lot of other bugs apparently. I want to try it, because it looks pretty sweet to me. But I just don't want a buggy rom. I don't want the stock rom either. I just want a really solid AOSP rom.

I'll give 3.2 a try and see how it goes.


Interesting about the data outage. That would explain it.
Click to expand...

I know that when 3.2 first came out it did have some bugs which is why I didn't flash it right away. I have been running it the past several days and everything I would typically use has worked and worked flawlessly for me. But like I said YMMV. Every phone is not created equal hence why some kernels work for person A and not for person B. I understand wanting a working ROM with no bugs. That is why I left MIUI. I loved it especially from a customizing standpoint but with two little girls at home I need to be able to send and receive MMS messages (plus the audio was horrible for me listening in my car). Try it and maybe it'll work good for you. Another option which I had done in the past was run BAMF side project 2.4 with a different launcher. It ran really well for me and was rock solid.
 
Papadroid said:
I know that when 3.2 first came out it did have some bugs which is why I didn't flash it right away. I have been running it the past several days and everything I would typically use has worked and worked flawlessly for me. But like I said YMMV. Every phone is not created equal hence why some kernels work for person A and not for person B. I understand wanting a working ROM with no bugs. That is why I left MIUI. I loved it especially from a customizing standpoint but with two little girls at home I need to be able to send and receive MMS messages (plus the audio was horrible for me listening in my car). Try it and maybe it'll work good for you. Another option which I had done in the past was run BAMF side project 2.4 with a different launcher. It ran really well for me and was rock solid.
Click to expand...

Flashed it a little while ago, along with all the fix-patches, and so far I really like the look of it. The only bug I have is when playing mp3's stored on my SD card, it skips, if I am doing anything on the phone, like opening menus, or other apps.
And judging by the thread for that ROM, I am not the only one having that issue, so maybe he'll put out a patch for it soon. But streaming music seems fine so far.

Thanks for recommending it.

I guess I didn't see it the first time, becuase I was looking in the master ROM list thread on XDA, and 3.0 was the latest on that list.
 
You may want to go over to Rootzwiki from now on as most devs have moved there. Very few Devs are updating there stuff at XDA.
 
offanairplane said:
Well, I certainly don't want to Unroot. I have apps that require root that I want to keep using. I am not being a smarty or anything, because I do appreciate the help, but even the title of the thread says I don't want to lose root. lol
Click to expand...

well,the link above was for a stock rooted rom :rolleyes: sorry if that wasnt made a little clearer. ;)

flashing the ruu,then flashing reflashing recovery and superuser gets you right back to being rooted.

at the risk of being a "smarty" myself,i thot we had answered your questions correctly ;)

offanairplane said:
I really don't want the stock Rom either. I just want a very stable GB rom. And so far, the stock one has been the most stable on my TB.
Click to expand...

i guess its largely your personal perception of things. i cant comment on conecting to your car issue,since i dont use that,but regular bluetooth(phone and media audio) works fantastically on cm7. not sure where you found info that 4g isnt working :confused: 4g is solid,and handoffs are fine. my speedtests are regularly 3 to 4 times faster on 4g,sometimes more :eek:

the stock rom has had far more issues for me than cm7 or any roms based on it. getting text during bluetooth conversation kicks me off so i have to reconncet my BT. its also plauged with dropped calls. the stock software to me is not particularly fast or smooth. cm7 has been my daily driver for months.

you might try miui. lots of folks seem to be pretty happy with it. :)
 
scotty85 said:
well,the link above was for a stock rooted rom :rolleyes: sorry if that wasnt made a little clearer. ;)

flashing the ruu,then flashing reflashing recovery and superuser gets you right back to being rooted.

at the risk of being a "smarty" myself,i thot we had answered your questions correctly ;)



i guess its largely your personal perception of things. i cant comment on conecting to your car issue,since i dont use that,but regular bluetooth(phone and media audio) works fantastically on cm7. not sure where you found info that 4g isnt working :confused: 4g is solid,and handoffs are fine. my speedtests are regularly 3 to 4 times faster on 4g,sometimes more :eek:

the stock rom has had far more issues for me than cm7 or any roms based on it. getting text during bluetooth conversation kicks me off so i have to reconncet my BT. its also plauged with dropped calls. the stock software to me is not particularly fast or smooth. cm7 has been my daily driver for months.

you might try miui. lots of folks seem to be pretty happy with it. :)
Click to expand...

I guess I just misunderstood you. Sorry.

Well, the car handsfree issue aside.

I am having a major issue now, and I don't know if it's related to the Liquid Smooth 3.2 rom or not. But half the time I try to make a phone call, or even answer an incoming call, I can't hear the person and they can't hear me, and all I hear is an echo of myself, and the other person says they hear an echo of themself. Then I'll hang up and call them again, and it will work fine.

Have you heard of that before?

The data issue I was having was definitely due to that outage, and not a problem with my phone, because I haven't had any issues since then.

What bugs did you notice on the stock rom?
 
mainly the ones i mentioned above. it dropped calles frequently. i talk on the phone a couple hours a day,and it would drop at least 2-3 calls a day. recieving a text,or other alert,would usually kick my bluetooth offline,requireing me to: turn off my earpiece. turn off bluetooth. wait a few seconds :eek:. turn bluetooth back on. turn earpiece back on. hope it connected to phone 1 audio,and not phone 2 or media. sometimes id have to unpair and repair it. leaving the range of the phone with the earpiece on and BT enabled for long enuff it would not repair. id have to reconnect as described above. :mad:

it was also not particularly fast or smooth,IMO. it was not terrible,but not spectacular either ;) scrolling homescreens,opening/closing app drawer and apps was not lightening fast or smooth,and sometimes id have to tap things a couple times to get them to work.

again,just my perceptions on my phone,with the stock kernel and no OC. your mileage may vary. the biggest disadvantage of any AOSP is vzw apps dont work :(
 
scotty85 said:
mainly the ones i mentioned above. it dropped calles frequently. i talk on the phone a couple hours a day,and it would drop at least 2-3 calls a day. recieving a text,or other alert,would usually kick my bluetooth offline,requireing me to: turn off my earpiece. turn off bluetooth. wait a few seconds :eek:. turn bluetooth back on. turn earpiece back on. hope it connected to phone 1 audio,and not phone 2 or media. sometimes id have to unpair and repair it. leaving the range of the phone with the earpiece on and BT enabled for long enuff it would not repair. id have to reconnect as described above. :mad:

it was also not particularly fast or smooth,IMO. it was not terrible,but not spectacular either ;) scrolling homescreens,opening/closing app drawer and apps was not lightening fast or smooth,and sometimes id have to tap things a couple times to get them to work.

again,just my perceptions on my phone,with the stock kernel and no OC. your mileage may vary. the biggest disadvantage of any AOSP is vzw apps dont work :(
Click to expand...

Don't get me wrong. I am not overly impressed with the stock ROM either. I think AOSP roms (the ones I've tried) are really fast and smooth, and I love that they aren't cluttered with a bunch of apps I'll never use.

I've never used any of the Verizon apps, so I can't say that I miss those. Which ones do you use?
 
I think I am going to go with a Sense rom until the Aosp roms get a little more bug-free. If it were small bugs, I would just deal with it, but bugs that don't allow me to make phone calls, are a big problem for me. I love Liquid Smooth 3.2 though, and I hope they do get the remaining bugs ironed out.

Anyway, I have a slightly off-topic question.
I am going to try Tesla Coil sense rom. And it says this in the notes:
"* MUST use either mr2 or mr2.5 GB Radio"

I had read somewhere that installing a radio is something you have to do from terminal and I am not comfortable with that. Can radios not just be flashed from recovery? I know on my old Eris they could, but maybe things have changed.
I never tried it on my Incredible.

And is that saying that I must find an MR2 or MR2.5 radio and install it, if I want this rom to work. Or does it come with a good radio already, and this is merely telling me that if I want to try another radio (other than the included one) I'll need to make sure it's either MR2 or MR2.5 ?


Thanks!



Also, from the radios listed here: http://forum.xda-developers.com/showthread.php?t=1048128

How do I tell which ones are MR2 or MR2.5?




And one more question.
Is it possible the problem I am having now with making calls could be a radio issue, and might be resolved by trying a different radio? Like I said, I really like LS_3.2 and I don't want to flash a different rom, if I can get this one working for me.
 
Papadroid said:
If you came from stock Gingerbread, you have the latest radio and don't need to worry about it.
Click to expand...

I see that now. I do have the 906 radio. I was stock GB when I got the phone a few weeks ago. Then I rooted and flashed OMGB, then Liquid Smooth 3.0, then Liquid Smooth 3.2

But apparently none of those roms changed my radio.
 
offanairplane said:
I think I am going to go with a Sense rom until the Aosp roms get a little more bug-free. If it were small bugs, I would just deal with it, but bugs that don't allow me to make phone calls, are a big problem for me. I love Liquid Smooth 3.2 though, and I hope they do get the remaining bugs ironed out.
Click to expand...

im still not sure what bugs youre unhappy about,but the best thing you can do if your not happy for any reason,is try somethin else :)

try the stock rom,try synergy,try em all :D

thats the good thing about making nandroid backups,you can always come back to the one you like and pick right up where you left off :)
 
scotty85 said:
im still not sure what bugs youre unhappy about,but the best thing you can do if your not happy for any reason,is try somethin else :)

try the stock rom,try synergy,try em all :D

thats the good thing about making nandroid backups,you can always come back to the one you like and pick right up where you left off :)
Click to expand...

I know. And I downloaded Tesla Coil-GB yesterday, and did a nand backup of my current Liquid setup, and even though I had nothing to lose, because I could just restore if I didn't like it, I still couldn't bring myself to flash it, because I really love Liquid 3.2. I feel about it like I felt about OMGB on my old Incredible. And that's a really good thing.
If I can get just a couple of issues resolved I will most likely stick with this rom for the life of my Thunderbolt.

Thanks for all the help by the way.
 
Papadroid said:
Radios can only be flashed through the bootloader, while Roms are flashed in Recovery.
Click to expand...

But you don't need to run any type of terminal on your computer to do this, right? You just name it appropriately, put it in the root directory of the SD card, and when you boot into the bootloader, it will detect the file ask if you want to update, you say yes and voila? See, that is a piece of cake. I was under the impression it was much more complicated than that on the Thunderbolt, which is why I haven't attempted it yet.

Of course, now that I know I have the newest radio, I probably won't mess with it anyway. But it's good to know I could.
 
offanairplane said:
But you don't need to run any type of terminal on your computer to do this, right? You just name it appropriately, put it in the root directory of the SD card, and when you boot into the bootloader, it will detect the file ask if you want to update, you say yes and voila? See, that is a piece of cake. I was under the impression it was much more complicated than that on the Thunderbolt, which is why I haven't attempted it yet.

Of course, now that I know I have the newest radio, I probably won't mess with it anyway. But it's good to know I could.
Click to expand...

That is correct.:D The only precaution is verifying the MD5 matches before flashing.
 
You must log in or register to reply here.
Back
Top Bottom