Hello, I have rooted, updated, and gone into recovery to install the Yay SBF and update to zipalign and de-odex the system through the boostrap recovery, I get no errors, but when the system loads, all the odex files are still there. I would post this in the thread itself, but I cannot post there due to my post count.
Are the odex files supposed to remain there? Or is something not going right? I am totally confused, I have had 3 other Android phones, and have rooted and loaded custom roms, as well as created custom themes for theme, and have never encountered this issue, any help would be appreciated.
It is still deodexed.
Sent from my MB855 using XDA App
Thank you for the reply, like I said, I have done this to a number of phones, including my last phone, (T-Mo Vibrant), and have never had the .odex files remain in /system after flashing.
Try flashing through clockwork, bootstrap errors a lot when it comes to flashing, i'm deodexed and don't have a single odex in my phone (i'm also deblurred though, should be the same though)
Sent from one focused MoPho
I would use CWM, but I haven't unlocked my bootloader, I get good 4g where I live, and I drive a truck for a living and get good 4g most of the places I go, so I want to keep it, so at the moment, bootstrap is really my only option as far as I can tell
Unlocking takes 5 minutes. Then do all u need with the custom cwm then backup your rom then relock reroot and restore. I have a fully functional alien 4g rom with 1% battery and relocked bootloader. Hope this helps
Sent from my MB855 using xda premium
iamanonymous said:
Unlocking takes 5 minutes. Then do all u need with the custom cwm then backup your rom then relock reroot and restore. I have a fully functional alien 4g rom with 1% battery and relocked bootloader. Hope this helps
Click to expand...
Click to collapse
Not sure why I didn't thin k of doing that, I have read the thread that says how to do it, and didn't even think to do it lol, thank you for all the help all, I'm sure I will get this figured out with everyone's advice
Related
When I rooted about a month ago or so. Just before I added a new kernel, Rom and than theme; I did a backup of my stock. Than a few more backups of my phone as I was customizing my phone. But when I tried to restore my phone back to stock. That restore didn't work but the others did. My question is; is there a way to return to stock? Without having to do a factory reset and listing all my stuff?
Sent from my ADR6400L using XDA App
Check it
http://forum.xda-developers.com/showthread.php?t=1009423
Oh ok... Thanks, so just un root it basically. Got it.
Sent from my ADR6400L using XDA App
you could also install the plain jane rom. its basically a rom that is rooted stock. heres the link --> http://forum.xda-developers.com/showthread.php?t=1030608. dont ever un root! its a huge pain and usually completely un necessary
Thanks that sounds even better thanks for the help guys.
sent from my DARK HORSED thunderbolt; using XDA app
dak_181 said:
dont ever un root! its a huge pain
Click to expand...
Click to collapse
It's really not that much of a pain. I've rooted and unrooted my Tbolt twice since I've had it, once to take it to VZW and once to try to fix a hotspot issue. When you're comfortable with adb, unrooting/rooting only takes about 15 or 20 minutes. The longest part is waiting for the files to download.
Unrooting, for me at least, is a way to start fresh after I've flashed so many kernals and so many roms that I forget where I'm even at
If your going for a fresh start then un rooting could be right for you. i,however, like my multiple Roms and kernels i keep pretty good track of them with ROM manager. if anything ever happens i just load the backup i made of the stock settings right after i rooted
lgldrgdlr said:
It's really not that much of a pain. I've rooted and unrooted my Tbolt twice since I've had it, once to take it to VZW and once to try to fix a hotspot issue. When you're comfortable with adb, unrooting/rooting only takes about 15 or 20 minutes. The longest part is waiting for the files to download.
Unrooting, for me at least, is a way to start fresh after I've flashed so many kernals and so many roms that I forget where I'm even at
Click to expand...
Click to collapse
Keep the files and you can do it in 10. The longest thing is flashing the RUUs.
But if I had a problem like this I'd either go to a new ROM and start over or go back to stock and start entirely over.
I've recently install the bootstrap recovery, and I'm mainly doing this right now to do some theme changes. Point being, I see some say use CWM, and others say bootstrap.. So.. what's the difference? I understand that CWM is for unlocked bootloaders, but could I still get the same results for adding themes through bootstrap?
The method I used was installing and apk, giving it su permissions and loading into recovery from reboot. I dunno, I'm getting a little confused by all this and would like a little insight. I've looked around and really haven't found anything yet. Getting tired, so I figured I could maybe ask for a little help. Haha..
If anything could someone point me in the direction for more reading? =)
Thanks
Oh and one more thing.. Is oxed, de-oxed meaning just roms, or some other method?
bootstrap will work for themes. some roms require cwm aka unlocked bootloader. i always flash roms thru cwm and temes thru bootstrap and have 0 issues.
odex and de-odex does have to do with theming most of the photon roms are de odexed
Sent from my MB855 using XDA App
Thanks for the reply. So things considered.. Would the stock sprint rom be de odexed?
Hey guys,
Was having too many issues with GNex so I traded in for a rezound but hate all the bloat on it. Decided I'd finally stick my neck out there and try my noob hand at rooting and customizing it.
So, got my rezound unlocked and rooted and before i try anything, how do I ensure I don't brick the phone?
Searched around for a real dumbed down guide to backup and recovery but I'm at a kindergarten level with this stuff. For example, it took me about 4 hours to figure out how to unlock and root the phone and HTC gives you directions on unlocking.
Have titanium backup, and rom manager. I read there's 2 ways to create a recovery file - cwm and amon-ra, read about nandroid backup but don't know what these things mean or how they function.
Can anyone give me a quick tutorial in backing up the phone in case I eff it up?
Any help would be much appreciated, I apologize if this is too basic a question.
Thanks
No apologies! You have to start somewhere so it's all good. I would start with these two very helpful threads:
http://forum.xda-developers.com/showthread.php?t=1418653
http://forum.xda-developers.com/showthread.php?t=1418659
I would recommend using the Amon_Ra recovery from THIS post.
Since you are coming from a Gnex...is it safe to assume you know how to flash a custom recovery with the boot.img?
It's not safe to say I know how to do anything yet haha. I liked the non cluttered feel of the gnex so I didn't mess with it and I never did anything with my og Droid. Never flashed anything so I'm about as noob as they come. I unlocked and rooted this phone and that's my experience to this point. Again all help is good
Sent from my ADR6425LVW using XDA App
Thanks for the links btw. Slowly figuring this stuff out. Got amon ra recovery now... What does that do exactly? Just trying to ensure I can get back to where.I am in case I mess up my phone. Should I do a nandroid backup? Not sure what that means either but I see some threads about how to do it.
Sent from my ADR6425LVW using XDA App
biond said:
Thanks for the links btw. Slowly figuring this stuff out. Got amon ra recovery now... What does that do exactly? Just trying to ensure I can get back to where.I am in case I mess up my phone. Should I do a nandroid backup? Not sure what that means either but I see some threads about how to do it.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
A nandroid is an image of your phone in its current state. So yes, you should do a nandroid back up now before you flash a ROM so if something goes wrong you can restore it back to how it is now.
Then if you're going to flash a kernel after you flash a ROM you should probably make one before flashing the kernel as well in case something goes wrong.
Then when you have the phone the way you like it with a custom ROM/kernel you can make a nandroid at that point as well so you have that handy in case of anything going wrong somewhere down the line or if you just want to get back to that setup after trying out a different ROM. Then you just restore that instead of having to flash the other ROM/kernel again. If you want you can make nandroids of all your custom ROM configurations so you can switch them whenever you want. Of course you should keep an eye out in the threads of the ROMs in case of updates, and sometimes you need to wipe and flash the new version if there is an update.
Here's a few links with some good info:
Beginner's Guide to Rooting Android Devices
Quick INTRO TO ROOTING for those new to rooting
[HOW-TO] ADB for Dummies(How-To Learner's Guide)
If you've never flashed anything before and are planning on customizing this thing; welcome to the family of rezound.
welcome! The ReZound in my opinion is a great phone.
Alright, got myself some good information from you all. Nandroid backup done and saved on my PC so now I'm good to ROM? Eager to rid myself of the enormous amount of bloat the rezound comes with.
One more thing to add for you to know about your original backup, or subsequent ones- that wasn't brought up here.. (smarter folks shoot this down if I'm wrong).. Someone stated above that once you have your nandroid you're always ready to go back to that original backup with a simple flash. This is not the case if he's gone to another rom that uses a different kernel right? It seems some devs have found ways to work the kernel install into the rom install/flash, and others haven't.. Until there's a standard- there's never a guarantee that restoring that original nandroid will bring you back to your original kernel correct? You may have to d/l and install the boot.img after the restore.
That's part of my issue now. I keep ready about flashing roms and kernels but they all assume some level of proficiency when it's something I've never tried. I'm thinking of starting with clean Rom 1.5 but I want to keep some apps like nfl. I just can't find the bare bones explanation of what to do with the file and how to get my data back after i flash that Rom (a process I am foreign to). I download the zip to my PC.... Then what?
Sent from my ADR6425LVW using XDA App
You may also want to get the stock rooted kernel, and keep it with the nandroid. If, and when you want to restore, place your nandroid, and kernel on your sd card. Boot into Amon ra, and restore, then flash the kernel in fastboot. Not the best description, but I hope that helps....
Sent from my ADR6425LVW using Tapatalk
I'm running ineffabalis with their stock rooted kernel right now mainly because I want to wait until the kernel update process is a little more streamlined and the kernels themselves are a little more ironed out. That said, the complete newb sticky guide over in the dev section has a process that seems easy enough.. Basically involves a simple fastboot command from dos. It's written for ziggys but should translate to other kernels as well.
Sent from my ADR6425LVW using Tapatalk
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 used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Are you s-on then?
Did you RUU first? Might want to do that since you had made changes before. That will bring you back to nice and fresh stock.
The latest one is here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
IF YOU ARE S-ON... you can relock, RUU and then flash the recovery again and get root and see if that helps.
If you are s-off then await someone else's answer, but I think you run the RUU without relocking.
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
disdard said:
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
Click to expand...
Click to collapse
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
GetRipped said:
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
feralicious said:
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
Click to expand...
Click to collapse
Oh hai there.:angel:
disdard said:
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Click to expand...
Click to collapse
It sounds like you just need a new launcher. If you're getting to that point are you able to pull it down and see the notification area?
If yes then you could use Droid Explorer to push another launcher to the phone.
If not, yeah you maybe looking at starting over. Have you tried using a different recovery? I know personally I've had issues with every launcher except for Amon Ra.
I ran RUU, and once reset to stock breezed through the process of rerooting. Unfortunately had that done before any of the other replies, because it would have been easier to just do the resetting. But I got into the mess while trying to straighten out the issue of my dialer and people app disappearing so just fully going back to stock ensured I got the entire mission accomplished. And at the point it would boot to, you couldn't pull up the notification window so a new launcher wouldn't have fixed it.
Atleast I learned a bunch through the process!!! Just getting into rooting and customization, took the first step and rooted and kinda figured out how things work. Once I figure out a little more and decide which ROM I want to try, I'd like to try a custom ROM. All stuff I'm familiar doing with computers just gotta figure out exactly how it all works on phones....
Glad you are back up and running! Sorry if my method was more involved/time consuming.
I would suggest that before you flash a custom ROM you make a nandroid of your stock set up. Then you can always flash back to that if you don't like the ROM or run into issues and avoid troubleshooting or RUUing just to fix something.
It's a good safety net and a good habit to always have a nandroid to go back to in case of issues. I usually keep one handy of stock and of any ROMs I like, and always make one before flashing a new ROM or even a theme for a ROM.