Related
Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.
The key piece of information to remember is that rooting does't cause the issues we experience. It's the custom ROMs and hacks we install that cause problems
I think most everyone here remembers that we're doing these things at our own risk.
As for the OP, if you don't feel a desire for the features available after rooting or flashing a custom ROM, that's cool. It's not for everyone.
Rooting, flashing, hacking... it's for tinkerers. People who like to find out why something does or doesn't work and then find a fix for it.
I would place a bet on this:
The people who don't have root or don't want to root, and they rarely post their issues in comparision with those who have rooted.
Yes, Most of the issues you see here are self inflicted, but it's what we do. We like a challenge/problem, it gives us something to do. Another reason to stay up till 3 in the morning to find out WHY it's jacked up.
If your issues are so bad, RUU and stick with stock (A whole new set of issues).
We mention our problems so that developers can try and fix them for the next release. In all honesty, Ive had one 1 problem, that was when I installed AOSP 1.6, which btw is/will not supported by our phone officially, I got the dreaded SMS issue that SOME people are experiencing.
Well yea many people post about issues who are rooted, but it is caused by other things they are doing that require it. Simply rooting your device shouldn't cause anything to go wrong.
Roms and other things that require root access tend to be beta, and even if they are not beta they are created by people, and not everything will be perfect.
It is pretty hard to permakill your hero compared to other devices. The only way I know of using the software is through flashing the radio, or messing with ESID and stuff like that.
Which you aren't supposed to do .
Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.
rdisanza said:
Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.
Click to expand...
Click to collapse
There's not an issue with rooting in and of itself. Take me for instance. I've had some problems with my phone:
1. Apps2SD didn't work...but that was part of a ROM that was being beta tested.
2. Kernel locked up...that was due to an invalid setting I put into the kernel I was building.
3. Lost CPU kernel control...this is something I'm doing wrong in the kernel I am building. I simply restore a control file from a previous build and recompile.
These are things that were expected in testing and needed to be fixed or that I inflicted on my own.
I have a friend who has rooted his Hero, but hasn't applied any of the custom ROMs to his phone (although he has installed applications that require root). He's never had an issue with the phone.
It really depends on what you use it for.
rdisanza said:
Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.
Click to expand...
Click to collapse
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.
watzone69 said:
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.
Click to expand...
Click to collapse
lol I second this my wife hates the fact the I have tis really nice phone and when ever I am at home she can never get ahold of because I am always doing something to it.
to the OP rooting really is not hard I mean if you are hosting a MMORPG server you could surely do it, but if your happy with your phone as is then that is really awesome. I myself when I first got my phone knew ABSOLUTLY NOTHING about android or linux or what in the work a kernel or apk was but with the help of the great community here I have learned so much. Dont get me wrong I am no where near where a lot of the guys on here are but I am learning and helping as much as I can just as those that helped me (i mean I am just happy that I think I could go through and make a theme now lol). if you are happy with the phone as is the only benifit of rooting I would bring up is being able to make backups of everything that way if anything does happen to the phone then you dont have to go trough and redownload apps and set everyhting back up again.
if you do decide to make the leap there are many people here more than willing to help.
Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,
rdisanza said:
Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,
Click to expand...
Click to collapse
oh please understand I wasnt trying to insult you at all, and yes I understand the control thing. thats why I rooted originally but then I flashed my first rom and got addicted. Now if im not changing my phone in some way on a pretty much daily basis I start to get the DT's lol.
No insult taken my friend. The DT's, lol WORD!
Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.
HeroMeng said:
Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.
Click to expand...
Click to collapse
You don't have to push the asroot2 exploit!?!?!!?
Kcarpenter said:
You don't have to push the asroot2 exploit!?!?!!?
Click to expand...
Click to collapse
Not if you're flashing a custom rom that already has it.
You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.
gu1dry said:
You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.
Click to expand...
Click to collapse
I never had to do that when I rooted. Flashed MCR right after I rooted using above method and it worked fine.
Yes the asroot2 exploit is was allows to root the phone, so therefore you had run the exploit initially.
FIRST TRY... Edited system.img (KERNEL 2.6.36.3 only!!!)
WARNING: ONLY USE THIS IF YOU HAVE A BACKUP OF YOUR /DEV/BLOCK/MMCBLK0P3 IF YOU DONT HAVE ONE YET, MAKE ONE BY USING THIS:
IF FROM ADB:
ADB SHELL
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
IF FROM TERMINAL EMULATOR:
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
THIS IS A FUNCTIONAL FILE SYSTEM, I AM WORKING ON A CUSTOM ROM WITHOUT HAVING TO HAVE THE BOOTLOADER UNLOCKED.
THE ONLY THING THAT HAS CHANGED ON THIS SYSTEM.IMG IS THE BOOT ANIMATION (INSTEAD OF "ANDROID" IT HAS THE HONEYCOMB BEE) AND THE FONT HAS CHANGED ALSO...
AGAIN, THIS IS JUST A TEST, IT IS THE FULL FILE SYSTEM TO BE USED ON A DAILY BASIS BUT DOES NOT HAVE ANY OPTIMIZED FILES AT THIS TIME.
Alright, now that you have read the warning... download this file here:
LINK = http://www.megaupload.com/?d=1YZSDVZI = LINK
You can then push the file through ADB by typing:
dd if=/sdcard/blk0p3_sys.img of=/dev/block/mmcblk0p3
Post if it worked for you or if it did not, this will help me troubleshoot...
PLEASE MAKE SURE THAT YOU MAKE A BACKUP OF YOUR FILES FIRST!!! THIS FILE IS BASED ON USA MODEL 1.104.05_GEN1 ACER A500. I RECOMMEND TO TRY ONLY IF YOU HAVE HAD TO UNBRICK YOUR TABLET BEFORE. I DONT WANT TO MESS UP YOUR TABLET!!! YOU HAVE BEEN WARNED!!! JEJEJE
Please post if it has worked for you or if it glitched, I am currently in trial and error so... my tablet gets bricked 1-3 times a day because I am testing different things on the system images... hopefully, I can find a way to have root on the image or at least include:
1. File manager
2. ROOT or at least the Gingerbreak.apk already installed.
3. Terminal emulator
4. Custom background upon boot
As stated, it works for me but I have only 1 tablet so if you are daring enough, please dont hessitate to help me in getting this up and running...
I AM NOT A DEVELOPER SO PLEASE BARE WITH ME AS I AM TRYING TO LEARN AS I GO... JEJEJE
props to you!
u crazy.
I don't see any attachment or link...
Euclid's Brother said:
I don't see any attachment or link...
Click to expand...
Click to collapse
Sorry about that, i've updated the post... jejeje
Beta Rom
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
THANKS!!! this is what I am needing... at this time, there is NOTHING ELSE that has been changed on the file system... I am just testing making sure that my changes stick... I am hoping to be able to change some more things... As long as its working... I will continue changing things ... Until I can get an image that is worthy of "Custom ROM" status... jejeje
tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
Did you fix your issue if you haven't I'm on gtalk if you want help I pulled my hair out for 2.5 days before I fixed it
Sent from my A500 using XDA Premium App
cant figure out how to multiquote as clicking the buttons dont do anything.
but just look at "Crsdr37"'s post in general with the imgs and update zip to get back to stock and updates!!!
and to the person who made the IMG keep up the good work. im not gonna flash it and im happy with being stock and getting updates now ;D
Have you figured out how to apply the incremental updates to the img?
I suspect it's just replacing files, I'll look at it when I get to a PC.
Ive been away from my tablet today. I put the post up and went out tonight... jejeje
Thank you guys that tested my image... if it worked for you, THANKS!!! if ou didnt, then let me know what did not work...
THIS IS NOT NOT NOT AN UPDATED IMAGE, IF YOU CHECK THE DESCRIPTION, THIS IS A TEST IMAGE TO GET A CUSTOM ROM OVER TO THE ACER A500... I AM TESTING SO I WILL NOT ANSWER QUESTIONS ABOUT UPDATES... THAT IS FOR MY OTHER POST... SORRY PEOPLE.
Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.
i am going to try it as well nice thing you guys do
Great
Cheers man, !
So, pulling your system image from /DEV/BLOCK/MMCBLK0P3, then modifying it, then pushing it back works?
Let me try and understand here:
I thought the whole locked bootloader thing checked signatures on the images that are about to be loaded into memory, such as the image in /system.
According to this:
http://www.reddit.com/r/Android/comments/hkbf3/so_you_want_to_know_about_bootloaders_heres_the/
It says:
What does a bootloader do with digital signatures?
It uses them to check any update that passes through it.
So: dd any partition we want to modify, back it up in a safe place, mount the img we get from that, make changes within the img, and dd it back, = all good?
ie: signed bootloaders only have to do with installing update.zips on the sdcard?
Can someone clear this up for me?
Thanks!
Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.
netham45 said:
If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.
Click to expand...
Click to collapse
Dude, chill man... You are right, your question does ask about headway for the updates but here are the facts:
You are asking about updates on a BETA Rom that is just in testing...
I took your question to be if the ROM file had the updates (My fault for sure). I was not yelling per say nor trying to be rude but rather making sure that people are aware this is in no way an updated image and should not be treated as such... THIS IS A TEST ROM and since your question was posted within its thread, I took it as if it was directed to the image itself and not toward me and my development...
Look, as stated, im not a developer man, this stuff is a little hard for me to do. I do apologize because I did not answer your question correctly/completely but as far as the comment... Its what I meant. jejeje
tomlogan1 said:
Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.
Click to expand...
Click to collapse
Have restored to complete US stock. Had a lot of problems related to SD cards, had to swap them out to avoid errors on the actual update.zip file, but am back to normal. Now if I can just keep my hands off until the 3.1 update comes out, or there is custom ROM...
mapaz04 said:
Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
Click to expand...
Click to collapse
That's what I've doing for a while now....I guess I should have shared xD
been installing custom fonts and trying to change some of the system settings from other customized roms directly from the tablet.
Instead of reflashing wouldn't it be easier to just provide the files to push into the tablet? just my 0.02
Yeah, I can provide files for you guys to install but what I was going for was an image that contained everything already setup so you can just flash it over ur old one allowing the "customization" to appear upon install/pushin the file... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
I haven't been around for a while and could not quickly get up to date despite going through thread after thread here. I would appreciate some advice and clarification.
First, you guys are saying that GB won't be available for Vibrant, but this article clearly states that it is already available:
“update news! the android 2.3 gingerbread update for the samsung galaxy S vibrant is good to go. connect to samsung kies to hook it up.”
Could you please clarify? The problem is that I downloaded Keys 2.0, but my phone, which is 2.1 and rooted (nothing else done, no roms, etc), is not being recognized. Keys says that my phone isn't supported.
Could you guys please clarify what is really going on in terms of 2.3? Also, how can I get the update? Assuming that the article is false, many here say that 2.3 roms are battery hogs and it looks like I would have to update to 2.2 and then root it. If so, I'd appreciate a link to a pure 2.2 to be installed via Odin. Reading all these threads doesn't convince me that getting a rom, a modem, or a kernel really does that much to improve our phones.
Thanks!
Thats for the Bell/ Virgin Mobile Vibrant theres a difference ya know...
I thought that the phone is the same so it wouldn't matter or perhaps the devs could use it to create a better ROM. If not, I guess the situation is even worse because Samsung actually released the update for Vibrant but T-mobile is refusing to allow users to have it! Clusterf*ck. Steve Jobs was right about android when he talked about market fractionization last year. Oh well.
Ok, well given the bad news, I would appreciate some help from those of you who have flashed your phones to hell and back. I know there are different ROMs etc with different features. I don't use my phone heavily. Actually, the main feature I care about is 1.Good GPS and 2.Good battery life. I go on long cycling trips and my phone is the only thing I use to track my stats (sometimes five hours or longer).
Based on this info, could you guys tell me if upgrading to Android 2.2 be good enough or do any of the ROMs, kernels, and modems provide a clear advantage over stock 2.2? If so, could you recommend a few? Right now my phone is in a very bad shape - the GPS is often dying in mountains and the battery doesn't last much. At this point I have to upgrade just to clean up my phone, especially since it's not clear if/when 2.3 will be released. I am hoping that at least 2.2 should be very stable by now.
only thing in common is the name and the fact that they are both Galaxy S series phones, the canadian bell Vibrant is different hardware then our Vibrant.
I'd say go with something stable such as Bionix 1.3.1 or Trigger 3.2. If you wanna go with 2.2.1 go with a Darky ROM's port or Bi- Winning 3. All good ROMS I'd recommended. Regardless that's what I prefer pperhaps just play around with all types of ROM's you may like something else its not for me to decide.
Sent from my SGH-T959 using XDA App
i would suggest cm7 if u like gb its almost fully functitioning except gps is weak
Would you guys say that you have seen significant performance improvements (~30% or more) of ROMs over rooted stock 2.2? If so, have you also seen significant improvements by adding a kernel and/or a modem?
I know that it's not supposed to be too hard to flash and find out for myself, but I have never flashed anything and evaluating all the different combos can be quiet time consuming. Given that I work and study so much I barely have enough time to date, I was hoping that I could get some succinct advice that will cut my Android pains in half. I have read the thread about different modems and know that something like KB5 is a pretty good modem (still have no idea what it is or where do you get it and how you flash it); however, that thread missed one key comparison - the actual performance and battery improvement of a given modem (and even a kernel) over stock 2.2/2.3 or even over a ROM like Bionix. I'd appreciate any info/links regarding this.
Thanks.
Stop writing walls of text for no reason ... kernel will make your phone faster, particularly if you enable voodoo lagfix (helluvah lot faster >30% over stock)... modem will not make it faster but may make your data connection faster and battery last longer as well as morr signal ... look for the modem page for dl link....
Now go flash a rom!! All the roms here are amazing and huge improvements over stock, as are the kernels. Suggestions??? Print out all the names, put em on notecards and throw a dart... flash whatever you hit.
Sent from a cell tower to the XDA server to you.
Bell vibrant is completely different from ours ... the 2.3 for them is no help to us.. lol were not lying to you
Sent from a cell tower to the XDA server to you.
None of the Gingerbread roms are anywhere near where some of the Froyo roms are.
Team Whiskey Bionix 1.3.1 is the best I've used. NextGen V2 isnt' bad either. I just tried Simply Honey 5 RC1 and CM7 nightly #84. Out of the 4 roms I just listed, I flashed back to Bionix 1.3.1. It has the best speed and is the most stable I've ever used.
If you don't have the time to read about flashing your phone, I would suggest you either not do it or pay someone to do it for you. Set aside 2-3 hours if you want it done properly otherwise say goodbye to your phone.
I am in SoCal too and wouldn't mind paying someone to do it for me. The problem is then a whole other set of headaches: how do you trust someone to get hold of your private info? What about doing a good job? Arranging a pickup/dropoff, etc, etc. Also have no idea how much people charge for this service. Expensive enough and it might just be worth it to get a new phone, especially after I sell the Vibrant. Maybe that's what many of us need to do.
Im sure you can find someone nearby thatll do it as a favor and let you watch... problem solved
Sent from a cell tower to the XDA server to you.
I would never pay anyone to flash anything for me. Its a simple process.
To figure out what ROM's go good with what Modem I would go to this thread http://forum.xda-developers.com/showthread.php?t=959088 and a good kernel would be Bali or SuperDragonModz both great.
Excelsius said:
I am in SoCal too and wouldn't mind paying someone to do it for me. The problem is then a whole other set of headaches: how do you trust someone to get hold of your private info? What about doing a good job? Arranging a pickup/dropoff, etc, etc. Also have no idea how much people charge for this service. Expensive enough and it might just be worth it to get a new phone, especially after I sell the Vibrant. Maybe that's what many of us need to do.
Click to expand...
Click to collapse
I recommend listening to some of the other folks in the thread and flash bionix 1.3.1. The stock kernel is fine, as is the modem it ships with. Battery life will be as good as just about anything else.
If you really want to flash a custom kernel, go with Bali 1.8.8. Battery life will be similar, but that kernel has some additional features like voodoo sound, which uses the audio hardware more effectively. If that doesn't seem like something you care about I wouldn't worry about it.
The only catch is that you will need to flash bionix through CWM recovery, there are no prepackaged odin files that I am aware of. There are numerous threads to help you getting CWM installed, just check out the stickies.
Don't pay anyone, if your still not comfortable flashing anything, but you still really want to, PM me and I'll help you through it.
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
I'm in SoCal, running Cyanogen7 nightly 81. (Android 2.3)
I am running Bali, and did both the hardware GPS fix, and the software GPS fix using the terminal scripting.
I get around 10-12 locks, accuracy tends to be in the 12-14 foot range, so the GPS works flawlessly.
I've been a lurker on these forums for a LONG time now, but decided to register and post to kinda give back. In this case, to someone looking to fix up their Vibrant.
If you're interested, PM me. I work for Microsoft, and you're welcome to stop by and I'll show you everything I've done. (Yes, I have an Android phone, and a WP7 phone, both of which I love) If you like what you see, (You will) I'll set your phone up as my way of kinda returning all of the favors other users on this site have done for me, even though they didn't know it.
Excelsius said:
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
Click to expand...
Click to collapse
If you already have ROM manager, and have "Flashed Recovery" then you have Clockwork Mod. At this point, should be able follow the Bionix instructions after the CWM point.
Nandroid backs up EVERYTHING, including the Android OS version you are running. If you want to back up just your apps, use Titanium Backup, the premium version lets you do a "One touch" batch restore of all user apps. One thing to remember about Titanium: do NOT back up system data. Easiest rule of thumb for it, "Menu--> Batch--> backup all user apps" then let it do it's thing. flash your ROM, then go into Titanium (Almost positive the free version is part of Bionix) "Menu--> Batch--> Restore missing apps with data" If you have the premium version, you can restore them all with no further input, if you have the free version, you will have to accept and install each app as you go, but they all come back with your saved data.
If you are going to do a FULL wipe (Format storage so the phone is empty) first connect to USB Storage, and move your "Titanium Backup" folder from the root of your internal SD card to your PC. Then, before you run titanium for the first time after wiping, reverse the process. Apps are back.
Excelsius said:
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
Click to expand...
Click to collapse
The steps you listed are correct. You also of course need to have downloaded the bionix 1.3.1 zip file and placed it somewhere on your SD card (I make a ROMS folder on mine). As the instructions noted, you'll have to do reinstall packages twice (ie you do it once and the phone reboots into recovery and it looks like nothing happened, you do it again and go immediately to CWR recovery where you can select "install ROM from SD" or similar). From this point on you won't have to worry about CWR recovery, it will always be there. As StarGazer mentioned, when you flash this it will wipe your phones settings and all the apps (but not the SD card). There are a variety of backup apps that can help restore them, but I usually don't mind starting fresh once in a while, especially if your contacts are stored on Google.
Finally, once the bionix finishes flashing and the phone reboots for the first time, expect to hear a voice start talking to you about backing up partitions, estimated times, etc. This is the "voodoo lagfix" being applied, which is converting internal phone partitions from the Samsung RFS to ext4, which noticeably reduces lag on the phone when opening apps and so forth. Good luck
Thank you for your help, everyone. I was able to dedicate a few hours and just take care of it since it didn't feel right to waste someone else's time. Please note that I haven't PMed anyone and if there are readers here who are technologically challenged, perhaps they can take my place and get help from some of the generous people who offered help here.
I currently have Bionix 1.3.1, Bali 1.8.8, and KB5.
To give back to the community, I wanted to post benchmarks. I have some amazing results:
Android 2.1 (everything stock, rooted) - Quadrant benchmark 852 (average of 2 tests)
Bionix 1.3.1 (with stock kernel) - 1504 (average of 3 tests). That's a 43% improvement! Now this is likely due to Android 2.2 rather than Bionix. It's definitely worth going from 2.1 to 2.2.
Bionix 1.3.1 + Bali 1.8.8 (after adding the kernel) - 1852 (average of 3 tests). That's 19% more than stock 2.2 and 54% more than 2.1! This isn't 30%+ improvement that some people here think kernels provide, but ~20% is still not bad, considering that battery life is also very important.
Now as far as the KB5 modem goes, I saw no improvements using GPS Test and Speed Test. My GPS is still at about 50ft accuracy and internet speed is 6000x2300kbps. The real test will come during my 60 mile ride on Saturday.
Right now I am only hoping that the battery will last at least as long or more than on 2.1, despite the kernel.
Question: before flashing with Bionix I had applied the software GPS fix to my phone a year ago. Do I have to do it again or does Bionix already include the software tweak?
Once again, thanks everyone.
P.S: My clock on the phone is off by two minutes from the atomic clock. I noticed that the "Autoupdate" of date and time message doesn't appear when I start the phone. Is there a time syncing issue with Bionix?
Just incase anyone with an Atrix 4G and 4.5.145 firmware, I followed the instructions in the following threads to successfully install Atrix-MROM on a brand new Atrix 4G ATT with the latest update.
1- Bootloader Unlock: http://forum.xda-developers.com/showthread.php?t=1182871
2- Root: http://forum.xda-developers.com/showthread.php?t=1769497
3- CWM Flash: http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot
4- Atrix-MROM Flash: http://www.montuori.net/android-mrom/atrix-mrom/
Thank you Michael Montuori, the Atrix-MROM is awesome.
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
ravilov said:
Rooting (step 2) is completely irrelevant and unnecessary. I've said this before. Still not sure why people constantly think rooting does anything if they're going to flash a new ROM anyway.
Click to expand...
Click to collapse
I think this is because, normally, they would need it to flash CWM. But it doesn't happen on Atrix. .
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
ravilov said:
Yeah, that's pretty much what I thought. People scarred/traumatized by other brands/phones and thinking everything is the same on all the other ones.
Oh well. Hopefully they'll learn one day. Hopefully a little sooner than the Atrix REALLY becomes obsolete.
Click to expand...
Click to collapse
This is my first smart phone, and I am absolute noob in this field.
I have been using Nokia 1216 and similar monochrome display phones before it.
In that case, I gues you're actually doing quite well really... If you came from mono dumbphones straight to this and have already flashed a custom ROM, that's actually kinda impressive.
Thanks!!!
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Glad it helped you.
pinofly said:
Much thanks my friend I thoght I was stuck in 145, I applied numbers 1 and 3 and now Im unlocked and have CWM
Click to expand...
Click to collapse
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
aarizaga said:
Please can you tell me, where i found the tool for unlock bootloader of step 1, because the link is outdated, thank you.
Click to expand...
Click to collapse
It is in that thread. You can search: automatic_unlock_v4.2.zip
Or here it is:
h t t p s:// w w w . d r o p b o x . com/s/sr6ooho4zf9wqvo/automatic_unlock_v4.2.zip
Scan it first..
The MROM is simply amazing. Best battery life so far trying the cm7 based roms!
Sent from my MB860 using xda app-developers app
I am a neewbie, and when i learned how to flash custom roms, i was wondering, it is really necesary to root if you want a custom ROM?
now i was clarified.
So if want original firmware, and root acces, i just need an unlocked bootloader? And for rooting, can i just flash a fruitcake?
Sent from my MB860 using xda app-developers app
Hi, Thank you mmontuori for the excellent Rom and hard work to do it, and to Ravilov for the help.
I want to thanks in the post of the MROM in the development forum, but I can't do it because I don't have enough posts.
Well I finish yesterday to put all in order, only my contacts information I fail to restore.
The Go Backup didn't work.
One question, I don't installed the sv kernel, is necesary? because I feel that the battery it drain very quickly.
The rest appear so far to work very well, checking the holo launcher.
are you 100% sure everything on first post works with an ATRIX 4G 4.15.1455 from AT&T wiht the original motoblur?
i am newbee but wants to learn. its probably could i kill the phone?
thx!
Atrix 4g ATT 4.5.145 working well with CM 7.2
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Vengaence said:
I have an Atrix 4g that was about to be retired or sold, and decided to instead make it an android project to learn about modding and possibly make something useful out of an old device.
After combing the forums on this site and others, realized there was some risk involved of a hard brick, but since this is not my main phone anymore, I wasnt too worried about. I'll share the results...
The phone was running gingerbread 2.3.6, ATT 4.5.145 build
#1) Root phone (http://forum.xda-developers.com/showthread.php?t=1769497)
Step 10 did generate an error for me, I had to issue the alternate command and it worked fine.
I downloaded root checker by JOEYKRIM on google play store to ensure it was rooted properly afterwards.
#2) Backup the phone in case of trouble (I used titanium backup from google play store, requires rooting from step 1)
Add a schedule to backup all and execute the schedule now. Pretty easy stuff
#3) Unlock bootloader (http://forum.xda-developers.com/show....php?t=1182871)
This is probably the most dangerous step. I used the link above and would like to add a few comments. The link above is a script written to automate the process for those not terribly familiar with the android tools ADB and fastboot. This script is capable of unlocking your bootloader, fixing some common problems that happen along the way, and installing clockworkmod so you can access android recovery mode to install custom ROMs. However, it seems to come with an older version of the clockworkmod, therefore I used it for the bootloader only (option 1 from main menu). I also had to execute option 3 afterwards as I did get the failure to boot 0x1000 error. Long story short.. I used option 1, then option 3 and skip the rest.
#4) PUSH ROM files of your choice to phone (I used Cryogenmod 7.2 latest from http://download.cyanogenmod.org/?device=olympus)
You should also copy any other addon ROMs of your choice to the phone at this time as well. Google store app is one that is not included with CM 7.2 and you can get here (make sure to pick the one for the version of CM you are choosing) http://wiki.cyanogenmod.org/w/Google_Apps
To push the files to your phone, simply boot your phone in the stock ROM, connect it to your PC with usb, and make sure the USB connection notification is set to USB mass storage. You can then copy the ROM files in zip form to the root directory of the drive letter of the phone from your PC just like you'd copy to a USB stick. Change the USB notification/communication mode on the phone back to stock setting of motorola phone app afterwards, as this dismounts the internal SDCARD storage and the phone wont remount it until you do.
This is out of order from some of the other guides. The reason to place the ROM files first before anything else, is so you can install clockworkmod to make recovery possible, then go right into it and install the ROMs from recovery mode. I had some issue with installing recovery with CWM first, then CWM not working if the phone booted into the stock rom (looks like the recovery was overwritten. I simply had to have the ROM files ready to go then do CWM all at once to make this work.
#5) Install CWM clockworkmod. (http://wiki.cyanogenmod.org/w/Install_CM_for_olympus#Installing_recovery_using_fastboot)
Follow the steps under installing recovery under fastboot. A link is provided for the latest CWM 5.0.2.0, which is what I used instead of the 4.0 version included in the unlock bootloader script mentioned in MY step 2.
At step 7, my phone appeared to hang at Flash boot: SOS. Some other users reported this as well. I just let the phone sit there for 3-5 minutes to make sure it was done with the operation. I then manually rebooted the phone holding down volume down button and holding power button until the phone powered down. If the phone is still connected to the PC, it will automatically power back on, so continue to hold the volume down until fastboot appears, then tapped volume down to cycle through the menu and chose Android recovery from the boot menu and press volume UP to execute it. CWM loaded up just fine and I was able to choose recovery ROMs we pushed in step #3 of my guide there and reboot.
Sorry if this is not as detailed as it could be, but I wrote this a bit after the fact without taking screenshots or writing down every step of the way. This is my best recollection of what I went through and figured I'd share as many consider this a gamble with the Atrix 4g and ATT 4.5.145.
Overall experience with the CM 7.2 ROM:
I've been running the phone for a bit now with cryogenmod 7.2 without issue. The battery life is fanastic and there are many nifty options included with CM 7.2 I have not experienced the random reboots or overheating some others have mentioned.
The only issues I've ran into so far, the latest youtube app from google store does not seem to play videos. You can install a QR code scanner app from google play store of your choice, then download the youtube app that worked for me via QR code from http://forum.xda-developers.com/showthread.php?p=18157961#post18157961
Additionally, internal storage (what's considered the SDCARD on this phone) was not mounted by default in CM 7.2. Reference this to fix it. http://forum.xda-developers.com/showthread.php?t=1481252
I hope this helps users out there with old Atrix 4g's considering giving them new life. I'm going to try CM 10.x soon to see how jellybean runs on the Atrix 4g. Wish me luck!
Vengaence
Click to expand...
Click to collapse
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
palmbeach05 said:
Cwm 5.0.2.7 is the up to date recovery (possibly outdated now, see new 4.3.1 for recovery (haven't tried it out yet))
Everything you just posted has already been mentioned over several threads over the past 3 yrs. We all are well aware of these instructions, long before you essentially copied, pasted, and edited into your own words, that detail the process of rooting, unlocking the bootloader, flashing a custom recovery, and flashing a custom ROM.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Vengaence said:
The tone of your response implies that I'm trying to take some sort of credit for other people's work. The reason I posted is I've noticed some folks fairly recently with doubts about this process working specifically with this exact phone and ATT 4.5.145, and I wanted to share my experience and encourage others to do it if they were on the fence. I appreciate the work of this forum and other folks who have poured hours of time into these custom projects to make the android experience better.
I notice that you are a senior member. I'd suggest that replies are restricted on this forum to constructive responses, and not negative ones.
Thank you!
Click to expand...
Click to collapse
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
CWM versions for Atrix 4g
palmbeach05 said:
Actually it was more along the lines of you were repeating things that have been said already time and time again. That was the true meaning of my post. I do apologize if it may not have been conveyed in a manner that my intention clear.
Also, the recovery. I just flashed the new one from the new 4.3.1 thread. It is indeed an update, bringing it up to revision 6.0.4.6. This is a huge step forward and lays the groundwork for 4.4 (most kk roms require at a minimum cwm 6.0.4.4)
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Vengaence said:
--------------------------------------------------------------------------------------------------------------------------------
I notice you have an MB886, Atrix HD according to your signature. This thread is for the Atrix 4G. I'm not sure if you realized this. Maybe that is the reason why we are not seeing eye to eye. The Atrix 4g is older and is quirky and there have been many horror stories. I havn't seen many of those stories with the Atrix HD and things are more straight forward.
According to http://www.clockworkmod.com/rommanager
the latest CWM for the Atrix 4G is 5.0.2.0 and that's what is used by http://forum.xda-developers.com/showthread.php?t=2613829
as well to install later versions of CM such as 10.2 on the Atrix 4g. It's also what I used for CM 7.2
On your Atrix HD, CWM 6.0.4.x should be used.
Vengaence
Click to expand...
Click to collapse
Ah, correct and incorrect my friend. While my signature may point out what device i am currently on, it does not reflect my past. A peice of supporting evidence is over in AtrICS v2.0 (see home button fix)
As far as cwm goes, cwm has unofficial builds as well. Look through one of the threads, it will point you to a link about recoveries and there does exist a 5.0.2.8. EDIT It was Romracer's recovery, accesed through the unlock bootloadrr thread a few threads down from this one. The 5.0.8.x i think was more like a 5.8.1.8, but i think that was a touch version? Now CM and the other threads may say the 5.x is ok for all of our roms, but as android moves forward, so must our support from libs, apps, kernels, scripts, and of course, recoveries. That is why i promoted the 6.0.4.6 revision both here and in the new 4.3.1 thread.
Sent from my MB886 using xda app-developers app
So the whole reason I rooted this damn phone was to be able to install working stock apps. Not just the Music and Gallery apps either--ALL THE LG APPS. Which LS997-compatible 100%-working ROM can I flash and get them all, if any? I keep hearing one exists, but no one bothers sharing that info and when I search I find nothing.
Really? No one?
bgibson72 said:
Really? No one?
Click to expand...
Click to collapse
Look in the development section it's like the 5th one down has ls997 in the title
@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.
jerrycoffman45 said:
Look in the development section it's like the 5th one down has ls997 in the title
Click to expand...
Click to collapse
This one?
{ROMS}[LS997] Stock-ish Magisk+3minit+ModControl 3/10/17
Other than DirtySanta, this is the only other one with LS997 in the title on that page. I'll give it a shot, and thanks for answering.
Team DevDigitel said:
@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.
Click to expand...
Click to collapse
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!
bgibson72 said:
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!
Click to expand...
Click to collapse
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have
Team DevDigitel said:
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
Click to expand...
Click to collapse
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Click to expand...
Click to collapse
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Click to expand...
Click to collapse
That's what I like to hear! :good:
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Click to expand...
Click to collapse
Appreciate the heads up. Familiar with the long boot process from DS, lol.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
Click to expand...
Click to collapse
Magisk is a new animal for me, as I've had zero experience with it. I do have Titanium Backup installed, so I'll make a mental note on that.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have
Click to expand...
Click to collapse
Thanks again--I appreciate your hard work and dedication to this!
bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse
Team DevDigitel said:
bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse
Weeeeeeeeeeeeee!!!
Will do!
Click to expand...
Click to collapse