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?
Related
I originally asked in this in the Noob Guide thread, but this its driving new crazy so I figured id make a thread
Ok so I'm rooted now and have been trying to get CW recovery image installed but am having done difficulty.
I choose flash recovery from ROM manager, then reboot into recovery, stock 3e recovery so I reinstall packages, it comes back to the 3e image, reinstall packages again and now I have clockwork.
Now when I reboot the phone and then reboot to recovery again, I'm once again at the 3e recovery..if I reinstall packages again it will reboot me to clockwork, but it just won't stick.
I've done this multiple times now to no avail. Can anyone help me out here? Is it possible just to adb push the cw recovery image? I'm not a noob by any means, but this phone has been giving me a hell of a time, I would greatly appreciate any assistance here. Thanks in advance.
Sent from my SGH-T959 using XDA App
I posted in the noob guide back, I suppose a custom rom is out of the question?
They can replace the stock recovery.
If you want to stay stock, it must be possible... hopefully others can chime in if that was your intent.
Thank you for the response sir, a custom rom is the goal, since I couldnt find anyone else reporting the same problem, I was just scared to flash a rom when the recovery wouldn't flash.
I'll be flashing tonight when I get time. Thanks again for your help.
Not sure what OS you want, but I would suggest Trigger for stability.
Awesome, that's what I was leaning towards so that makes my decision easier. I wish CM7 or miui were more stable, so I guess froyo it is..
Sent from my SGH-T959 using XDA App
CM7 IS stable as far as using your phone as a phone and playing apps.
It does have battery drain issues (though not as bad as before), you can't charge the phone with it powered off, NO gps and 3d graphics is lacking.
Other than that, CM7 runs great. I've had it for a week now with no issues.
All that said, I would still suggest trigger.
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
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
I am working with a company phone at my bosses request..what he really wants is a rooted phone on Froyo with Clockwork recovery.
This proved to be more of a challenge than I thought (Froyo). I did try to get around the signed update problem in the E3 recovery but wasn't successful.
Finally, I odin'd back to Eclair and installed CWM. It is weird in that I have to reinstall the update package each time to get CWM.
My questions:
1) anyway to get it into CWM directly (each time?; so it defaults to the CWM)
2) re Froyo, I guess the only way is to use CWM to install a Froyo based ROM?
a) If so, any recommends on an almost stock rooted ROM with Exchange email? (would prefer one that had the bloat removed, however; prefer stability to speed)
b) If I flash a Froyo ROM, am I ok in that I don't have to mess with the new bootloader business?
Thanks for the help!
(an Atrix owner out of his element and nervous about the bootloader biz after having previously dealt with the Moto locked bl problems )
You don't need to mess with bootloaders in order to install froyo. If you're on eclair then just put the attached update.zip posted by s15274n on root of your internal sdcard. Do not rename it or anything. Get into recovery, reinstall packages TWICE and you'll have your recovery then flash any froyo rom you want. Yes, it is that simple. There are few latest ones posted by Jellette and fishman0919 in development section. For example this one ...
http://forum.xda-developers.com/showthread.php?t=1586472
OR this one...
http://forum.xda-developers.com/showthread.php?t=1565768
Or this one...
http://forum.xda-developers.com/showthread.php?t=1589429
PS Is it hot in valley already? lol
Alex9090 said:
You don't need to mess with bootloaders in order to install froyo. If you're on eclair then just put the attached update.zip posted by s15274n on root of your internal sdcard. Do not rename it or anything. Get into recovery, reinstall packages TWICE and you'll have your recovery then flash any froyo rom you want. Yes, it is that simple. There are few latest ones posted by Jellette and fishman0919 in development section. For example this one ...
http://forum.xda-developers.com/showthread.php?t=1586472
OR this one...
http://forum.xda-developers.com/showthread.php?t=1565768
Or this one...
http://forum.xda-developers.com/showthread.php?t=1589429
PS Is it hot in valley already? lol
Click to expand...
Click to collapse
Thank you, sir!
It is always hot here....
Hi all,
I have a friend with an AT&T Atrix 4G. I've had a Droid X and current have a Galaxy Nexus & Nexus 7. I did everything you could do to the X and know my way around the Nexus very well; the atrix is a little confusing to me. moto-fastboot and the idea that SBFing is bad are new concepts to me. On the Droid X, if you were in trouble, you just SBF'd.
My friend had some trouble with his Atrix the other day, he was stuck at the splash screen, we got it half way fixed and he was in a bootloop, and eventually we got a version of CM9 on there: 9.0.0-rco-atrix-kang. The phone is running now but the ROM is unstable. I'd like to know how to safely downgrade to a CM7 ROM. Is it as simple as booting into recovery, wiping, and flashing the earlier rom? Something blur based would be ideal at this point as he's just looking to have a stable phone back. He got into rooting/ roming on his own so I'm not sure what updates, if any, were on there before he started. Is there an easy way to check and see which bootloader version he's on, find out which SBF we can safely use, etc? He does have it unlocked, so that should make things easier (or maybe harder, this Atrix really is a mystery to me...).
TL;DR - How do you safely downgrade an Atrix 4G from CM9 to CM7 and which recovery is the best to be using?
I used to switch between CM10 and CM7 all the time, if the phone is rooted and bootloader is unlocked, it's as simple as wiping data/cache, wiping dalvik, format system, install ROM, boot, reboot, install gapps.
Did your friend follow directions and make a nandroid of original before wiping? That would be the simplest way.
エイトリックス から 送ります
He said he had a backup but that when he restored it it was bootlooping. I'm assuming it was some kind of issue with switching recoveries or something like that. With the Droid X there was a recovery for 2nd-init roms and a recovery for blur roms. With the Nexuses it's mostly TWRP or CWM but as long as you're on the latest you can flash anything. Is there any reason to downgrade recoveries on the Atrix? Is there one "up to date" recovery? I see a lot of posts that point to a 2011 thread with the "latest CWM based recovery" but that seems kind of old...
Alright so I think I have this sorted out for the most part, and my understanding is that RomRacer made a version of CWM that we should be using on the Atrix. I just can't find a link to download the thing, is there a thread in development? When I search all I find is a ton of threads telling me to use it and no one linking it.
Edit: http://forum.xda-developers.com/showthread.php?t=1204500 Right?
Or is TWRP better?
http://teamw.in/project/twrp2/72
Lot of people love TWRP, but I'm one of the few that still uses RomRacers CWM 5.0.2.7 (I think) and no issues flashing CM10.1 (android 4.2.1) Had it for over a year, and works great every time. If it's not broken, don't fix it.
As for the boot loop, those are usually fixed with a wipe. Try wiping everything and restoring.
Edit: Yeah, that seems like the proper thread. Sorry, haven't looked at it since I first rooted my phone. Try TWRP, most people swear by it. The touch does add a nice feature, but I'm too lazy to make the switch.
エイトリックス から 送ります
Once you have an unlocked BL and a custom recovery, switching between pretty much all ROMs is safe so long as you stay away from SBFs.
You can flash to stock rom and then install CM7 :laugh:
ravilov said:
Once you have an unlocked BL and a custom recovery, switching between pretty much all ROMs is safe so long as you stay away from SBFs.
Click to expand...
Click to collapse
Thanks for the help, I'm glad I checked in. On the Droid X whenever anything went wrong and someone posted a thread like this the first ten replies were "Just SBF" - that used to be safe, until they rolled out .621, but that was end-of-life anyway.
I digress; next time I see him we'll iron this out and he'll be off to the races. Thanks again.