Just wanted to say thanks for the community here. It takes time to search through it all...but all the help you need is there. Took about 3-4 days of research and tinkering but I got everything I wanted.....I think lol.
1. Dinc Rooted S-On
2. Found out that sucked within about a day.....went to Dinc Rooted S-Off
3. Flashed Gingertiny Kernel
4. Fixed all sorts of FC's and updated a very old Super Permissions app that was thrown on from original root process.
5. Updated Radio to nice new EVO Radio
6. Installed Supercharger v6, Adrenaline Super-Shot, and ext4 Mods
7. Grinning ear-2-ear at the performance difference and apps I can use that needed root!
Thanks again peoples. I feel like I literally got a new phone....even though I've had my Dinc for more then a year easily.
Stupifier said:
Just wanted to say thanks for the community here. It takes time to search through it all...but all the help you need is there. Took about 3-4 days of research and tinkering but I got everything I wanted.....I think lol.
1. Dinc Rooted S-On
2. Found out that sucked within about a day.....went to Dinc Rooted S-Off
3. Flashed Gingertiny Kernel
4. Fixed all sorts of FC's and updated a very old Super Permissions app that was thrown on from original root process.
5. Updated Radio to nice new EVO Radio
6. Installed Supercharger v6, Adrenaline Super-Shot, and ext4 Mods
7. Grinning ear-2-ear at the performance difference and apps I can use that needed root!
Thanks again peoples. I feel like I literally got a new phone....even though I've had my Dinc for more then a year easily.
Click to expand...
Click to collapse
I agree with u man , when I got my droid incredible I really loved it for about a month . Then I hot suspended from school for fighting then I stayed at home and had nothing to do so I looked on YouTube and found out how to root my droid incredible . Then I learned how to flash roms and kernels and I REALLY loved my incredible. I love this community it taught me a lot
Sent from my ADR6300 using xda premium
what rom are you running Stupifier
I have not put any special ROM on my phone yet. Since I've owned my Dinc (not rooted) for over a year, I have become very attached to Sense and how its all setup. Just seemed like a lot of work to research a ROM I would like and set everything up....and I'm a little droid-exhausted after all the above I did.
I also spent ALOT of time setting up some real specific shortcuts on my old homescreens. I did not wanna lose all that work. For example, I easily have over 20 Evenghost shortcuts....and those take alot of time to setup individually. I don't have Titanium Backup Pro either since I'm cheap.
If anyone would like to try to WOW me with a specific ROM they use, I'll listen though.
I've been unrooted on this phone until just a few minutes ago. (rooted other android phones and tablets tho). I still got s-on because I dont wanna wipe my device right now, but I know i will eventually. I've been lurking inc development thread for a while and it seems like this will be the rom that i pick when i do decide http://forum.xda-developers.com/showthread.php?t=1558923. I may wait for it to stabilize a little tho. anyways what other benefits does s-off give? just the ability for custom roms and kernels? i see you updated the kernel and radio, does that work nicely with stock firmware? (im assuming 4.08.605.2)
Shano56 said:
I've been unrooted on this phone until just a few minutes ago. (rooted other android phones and tablets tho). I still got s-on because I dont wanna wipe my device right now, but I know i will eventually. I've been lurking inc development thread for a while and it seems like this will be the rom that i pick when i do decide http://forum.xda-developers.com/showthread.php?t=1558923. I may wait for it to stabilize a little tho. anyways what other benefits does s-off give? just the ability for custom roms and kernels? i see you updated the kernel and radio, does that work nicely with stock firmware? (im assuming 4.08.605.2)
Click to expand...
Click to collapse
How did you end up rooting? If you're rooted and have clockworkmod recovery you should actually be able to flash custom roms and kernels and even radios even with S-ON and especially if HBOOT is unlocked.
You should wipe to install custom roms anyways.
i used http://forum.xda-developers.com/showthread.php?t=1306400 and stopped before
3)prepare to downgrade
and yes i know to wipe before installing new roms i'm holding off on custom roms because i wont want to wipe right now
Shano, I used the exact same root guide you used. I would HIGHLY recommend continuing to step 3 and getting S-Off. I too stopped just before Step 3 and all it gave me was problems. From Force Closes, to unable to install certain important things like BusyBox and an Updated SuperUser app, and more. After about a day of that mess, I continued with that guide and got S-off. Looking back at it, I really wish the Author of that guide did not mention the possibility of stopping after Step 2. All it gave me was grief lol.
Also, once you finish the whole process in that guide....you can recover EVERYTHING you had previously (Apps, Settings, Data, Screen Layout, etc). Towards the end of Step 2, you are told to make a Backup. That backup is what you will recover once you are done. Then you got S-off Rooted without losing a dime.
well i already made a mistake and lost everything. im now on CM9 with s-on..however seem to still have some problems. i'll probably do that in the morning.
I just got a dinc a few weeks ago. I had a dx and the headphone jack crapped out on me. I snagged one one swappa for $70.
I was very active over at rootz (1300 posts), that's were the dx action seemed to be happening. Now, the dinc action is here.
Loving being able to flash kernels and having way more freedom than on the dx. I doubt i will ever go back to a moto phone, the locked bootloader really makes things difficult. The dinc will last me until my upgrade in Aug or longer.
Thanks to all who make flashing stuff on the dinc so easy.
One silly question. When we flashed a rom on the dx and it didn't boot for whatever reason, we would have to sbf the phone back to stock, there was no way to boot into recovery from power off. Is that a problem on the dinc? Or will holding vol down and power always boot you into recovery?
bobAbooE said:
One silly question. When we flashed a rom on the dx and it didn't boot for whatever reason, we would have to sbf the phone back to stock, there was no way to boot into recovery from power off. Is that a problem on the dinc? Or will holding vol down and power always boot you into recovery?
Click to expand...
Click to collapse
Correct. If the rom doesn't boot after flashing: pulling the battery and holding vol. down and power will take you to recovery. That's the typically suggested route if you waited say ten to fifteen minutes to no avail.
SlimSnoopOS said:
Correct. If the rom doesn't boot after flashing: pulling the battery and holding vol. down and power will take you to recovery. That's the typically suggested route if you waited say ten to fifteen minutes to no avail.
Click to expand...
Click to collapse
Thanks! That already bumps the dinc over the dx. Those locked bootloaders are a pain in the ass.
bobAbooE said:
Thanks! That already bumps the dinc over the dx. Those locked bootloaders are a pain in the ass.
Click to expand...
Click to collapse
I hear you, I've been spoiled with this phone since flashing anything is effortless. With the DX, were you able to install a new radio or update the kernel say when you went from froyo to gb? Was there only one kernel for froyo and one for GB or multiple per update?
bobAbooE said:
Thanks! That already bumps the dinc over the dx. Those locked bootloaders are a pain in the ass.
Click to expand...
Click to collapse
SlimSnoopOS said:
I hear you, I've been spoiled with this phone since flashing anything is effortless. With the DX, were you able to install a new radio or update the kernel say when you went from froyo to gb? Was there only one kernel for froyo and one for GB or multiple per update?
Click to expand...
Click to collapse
We just got what moto gave us. The radio would update once we received an update. There have been three updates for gb, 601, 605 and 621. 621 was pushed out and broke root. It was finally able to be rooted but your were stuck on 621 with no way to flash back to an older build. The sbf was our safety net. If you messed the phone up, who cares, just sbf and start over. Moto changed something in the bootloader that didn't allow that with the lastest update. Its since been fixed but it took about a month. The ones who tried before the fix were left with a permanent brick.
We do have something called "2nd init". It's a way to hijack the kernel and would allow us to flash cm7, miui, omfgb, cm9, aokp, gummy, etc. But it was still using the stock kernel.
Having this openness if fun. The guys who dev on the dx have done some amazing things with what they were stuck with.
bobAbooE said:
I just got a dinc a few weeks ago. I had a dx and the headphone jack crapped out on me. I snagged one one swappa for $70.
I was very active over at rootz (1300 posts), that's were the dx action seemed to be happening. Now, the dinc action is here.
Loving being able to flash kernels and having way more freedom than on the dx. I doubt i will ever go back to a moto phone, the locked bootloader really makes things difficult. The dinc will last me until my upgrade in Aug or longer.
Thanks to all who make flashing stuff on the dinc so easy.
One silly question. When we flashed a rom on the dx and it didn't boot for whatever reason, we would have to sbf the phone back to stock, there was no way to boot into recovery from power off. Is that a problem on the dinc? Or will holding vol down and power always boot you into recovery?
Click to expand...
Click to collapse
You should always be able to access hboot by pressing vol down and power, and then select recovery from there. This way you can just reflash a rom or restore a backup, instead of restoring the entire phone. We have something like sbf's but we call them ruu's, and they are flashed thru hboot and will return the phone to stock.
Sent from my ADR6300 using xda premium
just a technicality.... but vol - and power boots to Hboot. from Hboot you can boot to recovery.
if things go wrong (like rom does not boot or stuck in a bootloop) usually you can just re-flash a recovery, like clockwork, in Hboot. once your recovery works again, just flash another rom or do a restore.
Hboot should always be available... so there is no need to return to full stock again. if you can't get to Hboot, then you have real trouble. that would be very unusual.
edit-- wow am i slow typing with my phone
So i saw eariler in this thread, if the dinc is rooted, with su, and recovery i can flash roms? How so? I thought the bootloader had 2 b unlocked?
Sent from my s-off rooted htc rezound using Xparent ics blue tapatalk 2
My buddys dinc has root permissions, and clockworkmod recovery. So u r saying that he can flash roms with a locked bootloader, and s-on.
Sent from my s-off rooted htc rezound using Xparent ics blue tapatalk 2
zounduser said:
My buddys dinc has root permissions, and clockworkmod recovery. So u r saying that he can flash roms with a locked bootloader, and s-on.
Sent from my s-off rooted htc rezound using Xparent ics blue tapatalk 2
Click to expand...
Click to collapse
yes he can. however it seems to cause many problems. you must downgrade to froyo first to get s-off. back up all apps and data first
Shano56 said:
yes he can. however it seems to cause many problems. you must downgrade to froyo first to get s-off. back up all apps and data first
Click to expand...
Click to collapse
Its not really that it causes issues, its that it makes small issues much harder to diagnose and fix. Root and s-off are 2 different things, with root you can flash roms and most mods, with s-off you can flash directly from hboot, new hboots, radios, recoveries, unsigned ruus, and splash screens. If issues arise being able to flash from hboot is a big plus. I would also recommend downgrading and getting s-off.
Related
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
calm down take a breather us XDA users got your back, OK take out the battery and put it back in then go to the Hboot ( hold power and volume down) then once you get to the Hboot Settings use volume down to get to RECOVERY (i think its the third one) then once you get into Clockwork Recovery scroll down to (Backup and Restore) click then press (Restore) and then choose your Restore file it usually Year-month-day hope i helped you donate pls if i did
BE SURE TO KEEP THE CHARGER IN!!
p.s. if it turns off while its restoring even with the charger in let it boot into recovery mode and let it charge up a bit
incase you still need help gtalk me [email protected]
and p.s. CWM 3.0.0.5 is for gingerbread only
Certain roms require certain versions of clockworkmod. I don't know if this also applies to restoring from backups, though. Which type of rom did you flash?
If he flashed the add on 3.0.0.5 has ext3/ext4 support. Should be able to flash froyo and TB Rome.
Sent from my HTC Glacier using XDA App
3.0.0.6 supports ext3/ex4 3.0.0.5 only does Gingerbread
Edit: I'm being a dumbass yea what he said was right I'm overly tired and I have to explain to her why I was being a dumbass and trying to flash through fastboot but what I don't understand is why its still stuck at the boot screen
thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
Three options
Option one: (easiest)
Since you flashed 3.0.0.5 you must flash a Gingerbread ROM, (Which you can download from here ). Make sure to flash the G/apps after you flash the ROM.
Option two:
you can flash a 2.x.x.x Recovery image, or flash 3.0.0.6 via script or manually do it via the HBoot.
Option three:
Flash the PD15IMG and start over from ground one.
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
thisisjay said:
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
Click to expand...
Click to collapse
Ah. i think i see what happened. You rooted your phone. downloaded Clockwork Rom Manager, then flashed a recovery image (which was version 3.x). then tried to flash a 2.2 ROM.
Okay. so what.....
a common mistake but one that can be avoided by doing a little research.
Clockwork's 3.0.0.5 recovery image is only compatible with Gingerbread (2.3) based ROMs.
Clockwork's 2.x recovery image are only compatible with FroYo (2.2) based ROMs.
gorilla is 2.2 So it's not cannot be flashed by the recovery image you are using.
if that is correct then the text in the recovery image should be orange in color. If that is correct.....If i were in your shoes i'd load CM7 w/ the GAPPS > download CWRM from the markert > scroll to the bottom (all clockwork recoveries) and flash the newest 2.x. then boot into recovery / make sure the text is GREEN, not ORANGE, wipe then flash your GorillaSense.
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
danger-rat said:
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
3.0.0.5 is not backwards compatible, which is the official 3.x that you download via the Application. 3.0.0.6 which is "beta" flashed via the HBoot is backwards compatible.
It's seriously jacked if you ask me.
to go from lets say CM6 > CM7 one would do a nandroid backup of CM6, then go to CWRM flash the 3.0.0.5 recovery image > boot into recovery and flash the CM7.
now to get back to a 2.2 ROM you have to scroll to the bottom of CWRM app's and flash a 2.x version of the recovery then do your nandroid restore, flash the 2.2 recovery image.
From what i've heard once 3.0.0.6 is finished you can use that for everything.
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
danger-rat said:
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I haven't had any problems with mine. The only problem that was noted was the 3.0.0.5 prior to the official release wouldn't do Nandroid Backups directly from the application. Some were reporting it work work from the recovery image, but mine never did.
and i have a feeling the reason it's screwing with Partitions is this (CM7/CW3.x) is a Ext4 set up. And CM6/CW2.x is a Ext3 set up.
but since it went official the only problem i've seen is people flashing the the wrong recovery for the wrong ROM. People are flashing 3.x because 3 is higher than 2 so they think it's an upgrade and have no clue on the who/what/when/wheres and whys of what its for.
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
danger-rat said:
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yea between Google's way of doing thing and HTC, but i'm sure the chip-set has something to do with that. and with the sexy nexi only having 512Mb of memory the factor of tricking the phone to use the SD card has something to do with it i'm sure.
i have the 3.x recovery and i can flash iceglacier which is a 2.2 rom with out any issues. what i can't do is restore my backup from my other phone onto this replacement i just got. i made the backup with the 3.x recovery but i just keep getting stuck at the mytouch bootup screen... gonna try flashing the 2.x recovery and see if it lets me do the restore.
hey there everyone. just giving an update.......phone is still messed up. we tried putting gingerbread on and no go....tried flashing to PD15IMG and starting over. no go, it kept saying that "main version older <bad>" the phone wont go past the htc screen. im going on day 3 and no phone. *sigh* open for more advice. should i just buy another phone?
OMG OMG OMG i fixed it.......thank you for this post http://forum.xda-developers.com/showthread.php?t=957457 i re downloaded the PD(insert file name) and it worked. i broke down in tears. thank you guys sooooo much.
I used the .zip file to restore my mytouch, but now it wont go into Hboot.
I got the same problem and is fixed thanx to this link
http://forum.xda-developers.com/showthread.php?t=957457
now I have to root the phone again
Thank you
Thank goodness someone had this problem
I just ran into the same issue. whew good thing xda is here!!! Thanks fellas
Ok so as my previous post stated I just got my droid x and rooted it. I am in the process of installing a rom but have failed at this point.
For starters I have the droid x bootstrap installed and "running". Buy "running" I mean I can get to the clockwork recovery but only buy the bootstrap button or battery pull for 1min then boot. Booting while holding the home button stops at the exclamation android guy. I cant get past it no matter how hard I push the search button . So thats one of my problems but not a big one.
When I went to install liberty 1.5 I did a data factory reset and catch wipe then installed the rom. It got stuck on the liberty logo. So I tried again this time following the guide on these forms on how to install a rom correctly. Same thing. I tried three more times following three different guides and still was stuck at the liberty logo. So I gave up and followed the install guide on these forms again, but just restored from my backup. I am good and running again but I still have the liberty logo, which from what I read is normal.
When I got home from work I started digging into why it didn't work and found several things that may cause it. Now this is where I get lost. I have read the sometimes it just fails and you need to try again. But I also read the doing a SBF will also fix this. So I dug into what a SBF is and how to do it since this seams to be the #1 fix for everything. WHAT, UHH, MMMMM, K. So I read you will need to flash 2 files to SBF successfully. I have no problems with the RSD lite as it is only one file and you cant screw that up. But then I comes to choosing the right SBF file for your phone I get lost. All the versions listed are WAY below what I have. I am currently on 4.5.588. So I jumped over to androidforms to see if theirs anything their. They list x.x.596 as the most recent OTA but when I go to check for updates it says there are none.
SO, my questions are:
Is the reason I cant flash the liberty rom because I am running 4.5.588?
What do I flash if I need to SBF?
What am I missing about this OTA update? Is it being rolled out now or is my rom the most recent OTA?
Is their anything else I need to know that might help me in the future? Like I said I am new to this area of the forms and have not clew whats being released, changed, rooted, or what ever else.
I came from a rooted eris so Im not root dumb. But their is a big difference between the eris and the X.
ANY HELP WOULD BE AWESOME THANKS!!!!!!!!
BrownEye02 said:
Ok so as my previous post stated I just got my droid x and rooted it. I am in the process of installing a rom but have failed at this point.
For starters I have the droid x bootstrap installed and "running". Buy "running" I mean I can get to the clockwork recovery but only buy the bootstrap button or battery pull for 1min then boot. Booting while holding the home button stops at the exclamation android guy. I cant get past it no matter how hard I push the search button . So thats one of my problems but not a big one.
When I went to install liberty 1.5 I did a data factory reset and catch wipe then installed the rom. It got stuck on the liberty logo. So I tried again this time following the guide on these forms on how to install a rom correctly. Same thing. I tried three more times following three different guides and still was stuck at the liberty logo. So I gave up and followed the install guide on these forms again, but just restored from my backup. I am good and running again but I still have the liberty logo, which from what I read is normal.
When I got home from work I started digging into why it didn't work and found several things that may cause it. Now this is where I get lost. I have read the sometimes it just fails and you need to try again. But I also read the doing a SBF will also fix this. So I dug into what a SBF is and how to do it since this seams to be the #1 fix for everything. WHAT, UHH, MMMMM, K. So I read you will need to flash 2 files to SBF successfully. I have no problems with the RSD lite as it is only one file and you cant screw that up. But then I comes to choosing the right SBF file for your phone I get lost. All the versions listed are WAY below what I have. I am currently on 4.5.588. So I jumped over to androidforms to see if theirs anything their. They list x.x.596 as the most recent OTA but when I go to check for updates it says there are none.
SO, my questions are:
Is the reason I cant flash the liberty rom because I am running 4.5.588?
What do I flash if I need to SBF?
What am I missing about this OTA update? Is it being rolled out now or is my rom the most recent OTA?
Is their anything else I need to know that might help me in the future? Like I said I am new to this area of the forms and have not clew whats being released, changed, rooted, or what ever else.
I came from a rooted eris so Im not root dumb. But their is a big difference between the eris and the X.
ANY HELP WOULD BE AWESOME THANKS!!!!!!!!
Click to expand...
Click to collapse
im no pro but hopefully this info will help you, it did me.
http://forum.xda-developers.com/showthread.php?t=1073841 liberty info
http://forum.xda-developers.com/showthread.php?t=1085323 sbf'ing
The new 2.3.3 OTA is stable and very nice looking on my DX, OTA not rootable yet but give it time.
Biggest life saver about the DX is the the part of the phone that ppl mess up and turn their phones to bricks is extremely safe on the X, not bulletproof but all the info in these forums I believe can bring them back regardless of what happens. I was very overwhelmed at first with my X but very comfortable now that ive successfully managed the sbf.
Yeah that's one of the things I really noticed. If you brick your phone it seams its not the end. So im still a little confused with your explanation on SBFing. You say that 2.3.3 is the latest OTA but its not rootable. So am I looking at the wrong number when I say my version is 4.5.588.
Sent from my Rooted DROIDX.
Reading the noobs guide to droid x allowed me to figure out that I have the 30.04 bootloader and I will need to flash the 2.3.34 file. But I would still like to know why my version is so much higher then 2.3.34.
By far, this is the easiest way to sbf back to stock froyo
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Sent from my Xoom using XDA Premium App
chbennett said:
By far, this is the easiest way to sbf back to stock froyo
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
WOW that is easy. To bad you cant select what version it flashes. But still EASY. Ill keep that in mind if I need to SBF. THANKS!
http://droidmodderx.wordpress.com/how-to-sbf-your-droid-x-full-2-3-340/
Good video tutorial there... It also has files there as well
Sent from my DROIDX using XDA App
Well I gave liberty 1.5 another try and it still got stuck on the liberty screen. Any ideas?
Sent from my Rooted DROIDX.
Was able to flash the liberty gingerbread rom tonight! I am kind of wondering if the version of ota/bootloader I have is the reason liberty 1.5 wouldn't work for me.
BrownEye02 said:
Reading the noobs guide to droid x allowed me to figure out that I have the 30.04 bootloader and I will need to flash the 2.3.34 file. But I would still like to know why my version is so much higher then 2.3.34.
Click to expand...
Click to collapse
your looking at the version of the software build, complete jargon here but say your on android 2.2.1 version blah blah blah, what i was referring to was although you may have a higher version of 2.2.1 than what you are reading, a lower version of a higher android software such as 2.3.3 is better than a higher version of 2.2.1 same page?
Hey guys, I'm probably going to sound like a noob but I need some help with flashing a custom rom to my atrix. I've been trying for a couple of days now with no success. When I first got my atrix it was on 1.8.3. Upon trying to flash any roms I got stuck in a constant bootloop. So i figured I'd flash to newer firmware anyway. So I flash to 2.3.4. I follow the briefmobile instructions on rooting my atrix and the root appears successful. I then install tenfars cwm. Now back when i was on 1.8.3 I had unlocked the BL. but now upon my flash to 2.3.4 I notice that my unlocked symbol has gone away. Do i need to redo it? Anyways then I boot into recovery and have tried flashing aura or alien many times. It always says success, reboots and I reappear to my normal screen with normal kernel and all. The only difference is the extra apps in those rom's are installed. Thanks for any advice. I would love to flash a rom but not having my phone the way I want for the past couple of days is really making me tired of even bothering.
1) use romracers CWM
2) if you want the alien rom to look like the alien picture, you need to install the additional theme
3) pretty sure alien uses stock kernel
4) it doesn't hurt to re-do the pudding unlock
Sent from my MB860 using XDA Premium App
Alright, I have had my Bravo since January, rooted and flashed the BravoX RC2 rom along with a theme. During the summer, my wife was eligible for her upgrade, so we decided for me to upgrade to the Atrix on the condition that she was able to get the Bravo.
The phone has always had some freezing issues since updating to 2.2, but I think lately she has been getting very annoyed with this.
I would like to return the phone completely to stock, but due to the time since I last worked on it I'm a little unsure on how to go about it.
I wasn't expecting to get the upgrade when I did, and it was time sensitive so I didn't have time to remove my modifications to the Bravo before I gave it to her as I was planning, but a factory reset had removed all of BandroidX's apps, but left root access, the rom, and theme.
So, I know I will need to flash the 2.2 SBF to the phone in order to reset it completely to stock.
Because the phone currently is rom'ed and themed, do I need to first try to reset the phone using the BravoX bootstrap recovery?
Or does flashing the SBF completely overwrite everything that I've done with the phone erasing the rom, icon theming, and will it remove root access?
If you flash the sbf your phone will be completely stock... fresh froyo. Root access and everything else will be gone.
So, there won't be issues/conflicts with flashing the SBF all the way after having rom'ed and themed?
roadkizzle said:
So, there won't be issues/conflicts with flashing the SBF all the way after having rom'ed and themed?
Click to expand...
Click to collapse
No, flashing the sbf will erase your custom rom and theme for you.
Do you know how to properly flash the sbf with RSD Lite?
Yes, I've done that a couple of times. Really just done it from stock, or close to stock though, and a little new to working within OS's so was wanting clarification how the sbf sets itself.
I've been able to bring a few "bricks" back to life with there .sbf files. Love the things when flashing roms that have a bad bootloader or something else. Saved my skin several times. So ya flashing a .sbf is a total wipe and fresh install of whatever one you use. Just make sure you have a full battery at the start
I've been running Liberty on my Droid X for some time now and love it compared to the stock Blur interface. But it's gotten to the point where I'd like to update from Froyo to one of the more modern versions and see if that can liven up the phone again. So my question is this - from what I've read before I can update Liberty (or any other ROM for that matter) from a Froyo based version I need to restore the phone to a semi-stock state, update via an official OTA release, re-root and go from there. Is that true? If so, any convenient guide on how to do so? I did a bit of searching and couldn't find much and while I'm pretty technically inclined my skills do not extend into the phone region and back when I originally modified the phone there were many handy guides and videos to walk me through it.
Any help would be greatly appreciated.
Nate
If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk
Let the stupid questions begin...
Ok, I confirmed that I'm running 30.04 and I found a site that maintains the correct 4.5.602 file so I downloaded that. Is there anything that I need to back up before installing? Also, I read that a special program is required to install the SBF files so any assistance there would be appreciated as well.
Thanks!
Ok, so I managed to track down RSD-Lite and got it to recognize the device and start loading the sbf file however the phone couldn't get past the "manually power up the phone" phase (or something like that). It just kept showing the boot animation over and over again regardless of what I did - it would cycle between the red eye and the DROID text. I tried pushing and holding the power button, no good and none of the other buttons did anything either. Nothing worked. So I'm rerunning it again and we'll see if the second time is a charm...
Well crap, I got through the SBF install process and got the pass message from RSD but now my phone is stuck at the animation and won't go any further. I've left it running for the better part of 10 minutes and it just hangs. I'm now performing a manual factory data wipe to see if that will help.
EDIT: It appears that the factory data wipe got me through the locked animation. Still having minor issues getting through the programing and setup phase but I think it'll work eventually.
Thanks again for the help.
infazzdar said:
If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.
Well, it's sort of worked out.
Everything is up and running but ROM Toolbox isn't able to load any ROMs. It gets granted Superuser permission so I'm pretty sure that I've got the X rooted correctly but when it tries to boot into Clockwork it appears to get an error (icon with an exclamation point) and reboots into the regular Blur interface. I'm going to have a go at loading something like Liberty Gingerbread or 3.0 via zip file but it makes me nervous that the Toolbox Pro App can't get this done.
After determining that the Toolbox App was not booting into Clockwork I downloaded and installed the Droid X Bootstrapper App and got that running. It was able to correctly boot into recovery from which allowed me to install the Liberty 3 ROM. I'm now going back through the process of setting the phone up with the new ROM so we'll see how that goes. It appears to be working, but only time will tell if it's stable. One thing is for sure, a few hours on Blur'd Gingerbread and I was ready for something else again.
Jubakuba said:
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.
Click to expand...
Click to collapse
I was actually wondering whether it would or not, but I can't think of another way to update the bootloader.
Sent from my DROIDX using Tapatalk
Ok, so here's an issue that I'd appreciate some guidance on. After installing Liberty 3.0 it appears as if the phone can't fully charge. It was plugged in for 10hrs last night and yet this morning the battery only reads 61%. I don't know if it would be best to boot into recovery and wipe the battery stats not knowing if it's fully charged or not.
Thoughts?