Related
so i just bought my nook color today and i have some questions, i was searching around in the android development forum and their were about 50 different methods of doing everything.
i am experienced with android and how to do anything just if somebody could post up links in an order i need to follow to be able to get CM7 on to it.
if possible flashing to nand would be preferable but if all we have is SD support thats okay too
thanks for the help guys
also i know i will likely get flamed for this thread but just know i am experienced with android and i have ran it on a non native device before (htc vogue).
My go-to link for flashing CM7 to the internal memory:
http://forum.xda-developers.com/showpost.php?p=11452450&postcount=19
thoughtlesskyle said:
i am experienced with android and how to do anything just if somebody could post up links in an order i need to follow to be able to get CM7 on to it.
if possible flashing to nand would be preferable but if all we have is SD support thats okay too
thanks for the help guys
Click to expand...
Click to collapse
You can get just about anywhere with the nook via two steps:
1) run autonooter for your software version (THIS is for 1.1, obviously for the other versions it will be a different thread)
2) use the market to download ROM Manager, then flash the CWM recovery and download 7.0.2 from the app (or pull a different CWM zip from the forums onto your card if you prefer) and flash.
Simple enough
EpicFail236 said:
You can get just about anywhere with the nook via two steps:
1) run autonooter for your software version (THIS is for 1.1, obviously for the other versions it will be a different thread)
2) use the market to download ROM Manager, then flash the CWM recovery and download 7.0.2 from the app (or pull a different CWM zip from the forums onto your card if you prefer) and flash.
Simple enough
Click to expand...
Click to collapse
thanks, i was reading it from the app so i missed the 2nd part about loading it to my sd card thanks for all the help guys im going to try this now
so i did the rom manager thing picked nook color (old) that might have been the wrong choice but now it wont boot past recovery it just keeps rebooting into recovery
also it wont allow me to flash anything it says i have the wrong prop=encore help somebody
okay got that fixed thanks to one of the tutorials on here (thank god thought i bricked it)
so cm7 is booting now how long does this thing take, mine has been going for like 10 minutes but its not like bootlooping is this just because the tablet builds are huge or do i have cause to be uneasy (nook builds like stock software def didnt take this long)
http://wiki.cyanogenmod.com/index.php?title=Barnes_&_Noble_Nook_Color:_Full_Update_Guide Just in case
First boot will take 5min+.
Nburnes said:
http://wiki.cyanogenmod.com/index.php?title=Barnes_&_Noble_Nook_Color:_Full_Update_Guide Just in case
First boot will take 5min+.
Click to expand...
Click to collapse
we are on like 20 minutes now
thoughtlesskyle said:
okay got that fixed thanks to one of the tutorials on here (thank god thought i bricked it)
so cm7 is booting now how long does this thing take, mine has been going for like 10 minutes but its not like bootlooping is this just because the tablet builds are huge or do i have cause to be uneasy (nook builds like stock software def didnt take this long)
Click to expand...
Click to collapse
This isn't your Hero!!! I don't think you can brick this thing.... The Nook always tries to boot from SD before internal memory!!! I had a hell of a time getting CM7 to load originally (at least 10+ minutes). Once you get it loaded, put away that SD card you burned the recovery image too.....Put a new SD card in, install Rom Manager, and flash recovery to it from Rom Manager. Once you get there you can Nand and flash stuff just like you do on your phone.
**Edit** If you get really jammed up, here's the thread on returning to stock unrooted B&N firmware, so you can start over....
http://forum.xda-developers.com/showthread.php?t=914690&highlight=return+stock
6/5/2011 EDIT : Going to alter this post for two reasons. First, the information inside is pretty old news and stale for most, and not even very relevant for new users. Second, there is STILL confusion between these two branches that needs to be ironed out, imo.
If you are considering modding your new GTAB, I would suggest reading this. It's going to be a long read, but you'd rather not brick your device, right?
Some Terminology Pre-Reqs to Understand
"Soft-brick". The device is not booting up properly anymore, but is potentially fixable by using a tool called "nvflash".
"APX Mode". The is a low-level mode on the GTablet where you can makes repairs and un-brick the device.
"Nvflash". This is the name of the actual tool you use, when you are in APX mode.
"Clockworkmod". This is an alternate recovery tool. It adds a few things that the 1.1-based stock recovery does not have, such as full image backups, wiping user data and SD repartitioning. The 1.2-based stock recovery is a little better, but clockworkmod still has more options than 1.2 standard recovery
"/data partition". This is the area on the device where all your user data and user apps reside. A factory reset will wipe this area.
"/sdcard partition". This is the area on the device where all your content resides. It's also the area that gets mounted on your PC.
"Data wipe" or "User data wipe". This is a factory reset -- all user apps and data will be erased. Content in the device's /sdcard is not touched.
"SD repartition". This is a data wipe and a wipe of /sdcard. So both areas are erased.
"ROM" as defined for use should be considered a BOOT ROM. This is the base program running on your tablet, like an operating system it is the first line of code to load and while not every rom is a full replacement of the viewsonic operating system only one can be loaded at a time. (thanks mERRIL!)
"Kernel" as used here is the tablets details and settings written out so the software knows how to interact with the hardware. This is where things like overclocking can be done, along with changing the way your backlight or wifi utilizes power. (thanks mERRIL for both of these!)
Two Development Branches, and How to Check which version you have
This is the FIRST thing any new Gtablet user should check imo, before you attempt to mod your device. Viewsonic / US Merchants released a new development branch with a new bootloader and kernel (which they later pulled), and older mods do NOT play nice with it. There have been reports that at least a few TigerDirect users have gotten 4349 OOTB.
So, to check which branch you are on if you are on STOCK: Go to Settings -- About Tablet -- Tapu UI Version. If your firmware starts with "1.1", then you are on the 1.1 (old) branch. If your firmware starts with "1.2", then you are on the 1.2 (new) branch. Also an obvious difference between the two is that the 1.2 branch adds a lockscreen to the tablet.
The "Two Cliffs" analogy
Try to think of these two branches as two cliffs. If you are on either side and want to mod your device, the safest way is to use a mod that is built around the branch you are on. Here on XDA Developers site, most of their mods and custom kernels are based on the 1.1 branch (as of this writing). For 1.2 based mods, there are several options but most of them are not posted here on XDA. So you have options regardless of which branch you are on. There is no advantage of using one over the other, except possibly vendor support - 1.1 is still the ROM offered by the vendor, given that their one released 1.2 ROM was pulled.
It is possible to jump from 1.1 to 1.2, and back again. But think of this as a bridge between the two. I have done extensive tests in the last month on this, and it does work MOST of the time if you follow directions. But even when doing everything right , there is still a small chance that you will "fall of the bridge" and into the abyss (soft-brick). And if you attempt to jump between them with clockworkmod, you will fall for sure, 100% of the time. Think of clockworkmod as a "bridge that is out".
The most sturdy bridge, going on my own testing, is the one based on build 1.1-3588 full stock. This makes sense because this is what Viewsonic would want you to be on, before jumping to 1.2. The reverse (1.2-4349 stock, for example) is also fairly sturdy. But again, it is a higher risk than staying within the same branch.
I'm on a 1.2-based stock ROM. What are my modding options?
If you are on the 1.2 branch, there are actually quite a few options right now. The challange for a user is finding them and understanding that you have to be careful if you try to use a 1.1 mod instead (see the "Two Cliffs Analogy", above).
The current 1.2 based options on XDA are:
- Calkulin+Clemsyn 1.5ghz Froyo Combo VERSION 6
- Beasty's 2.2.1 ROM (Adam) + Clemsyn ver 11 1.5ghz kernel
- Clem / roebeet Honeycomb alpha combo (this is a Clem creation and is actually forked from my own HC port)
- Honeycomb Android Illuminate for The Gtablet
The current 1.2 based options NOT hosted on XDA are:
- Century Eyes (Froyo based "EDEN" port)
- Mountain Laurel (Froyo based "TapnTap" port)
- Brilliant Corners (Froyo based "VEGA"/"Viewpad" port)
- Bottle of Smoke (Honeycomb port, currently is a mashup from the Adam and VEGA devs)
Pershoot and Clem both have 1.2 kernels that you can use, as of this writing. Not all of that information is here, some are on other sites.
I'm on a 1.1-based stock ROM. What are my modding options?
On XDA, there are still a number of mod options and customized kernels, at your disposal. Again, a 1.1 to 1.1 mod should be fairly safe to attempt. If you want to jump to 1.2, I would recommend reading the modder's post to see if there are instructions for 1.1 jumpers. If not, the SAFEST way to jump is to flash back to 3588 stock (including stock recovery) and then flash to 4349 using stock recovery - that will get you onto the 1.2 dev branch.
There are still a lot of 1.1-based options, if you want to stick to that path. To name a few:
- VEGAn-TAB (probably the most popular GTAB mod, so far)
- VEGAn-TAB Ginger Edition
- Cyanogenmod 7.x
- G-Harmony
- Calkulin's G-Tab ROM
- TNT Lite (similar to Calkulin's ROM, and currently retired)
- gADAM (currently retired, as well)
There are also a few custom kernels for 1.1, specifically the ones by Pershoot and Clemsyn, here at XDA.
OK, so I've confirmed that I'm on one dev branch but I want to use a mod that's on another dev branch - what do I do?
My suggestions:
1- Read the modder's first post, for possible instructions.
2- If there are no instructions for branch jumpers, DO NOT assume that it's safe to jump. Ask the modder first, to be sure.
I am generalizing here, but the older 1.1 mods might not have instructions for 1.2 users, as you didn't exist at the time the mod was created. Imo, the SAFEST way to jump to a mod that's on another branch is to use stock. So 3588 stock to 4349 stock (using standard recovery) to go up, and 4349 stock to 3588 stock (using standard recovery) to go down. The main reason why it's the safest is because stock has the bootloader image in there, which is required to jump.
I attempted a 1.1 to 1.2 (or vice versa) jump, and now I'm stuck at the birds. Is this a soft-brick?
Yes, it's a soft-brick if you are stuck at the birds. You'll need nvflash the device to fix it. There is information here on XDA on how to do that, or you can find this on other tablet sites.
I attempted a 1.1 to 1.2 (or vice versa) jump, and now I'm stuck at the GTablet screen, or I'm boot looping. Is this a soft-brick?
Probably not - more likely is that you just need to do a data wipe, or a SD repartition if that does not work.
I have a Hannspad (or an Olipad) - does this apply to me?
I believe that it does, going on what I've read. Both these devices seem to be based on the TapUI, and the 1.2 development branch. So attempting a 1.1 GTAB ROM will likely have the same pitfalls. Also keep in mind that even 1.2-based GTAB ROMs have issues. for example, the Hannspad can boot a 1.2-based ROM (like "Bottle of Smoke") but the side keys won't work because the hardware is different. I don't have these devices myself, but I am going on third-party information.
Roebeet, can I safely install over the 3588 Stock Enhancement and Market Fix? I hate to lose the Market but definitely don't want to deal with a brick right now. Another user indicated he/she installed the update over a similarly configured machine and it worked but then applied the Stock Enhancement and Market fix and soft bricked.
I appreciate all the work you do for other users, including me.
interesting!!!
I love my devs!!! Seriously you guys rock!!!
P.S. I am sticking with Vegan GingerEdition
Great post and good info roebeet - stickied for the immediate future.
MSU_Sparty said:
Roebeet, can I safely install over the 3588 Stock Enhancement and Market Fix? I hate to lose the Market but definitely don't want to deal with a brick right now. Another user indicated he/she installed the update over a similarly configured machine and it worked but then applied the Stock Enhancement and Market fix and soft bricked.
I appreciate all the work you do for other users, including me.
Click to expand...
Click to collapse
I haven't tested all scenarios, as there are just too many of them. I specifically picked VEGAn as I know that's a very popular ROM and I could see new stock users flashing to that.
Rule of thumb: If you are going from a 1.1-based ROM to a 1.2-based ROM (or vice versa) and use clockworkmod, you will soft-brick your device.
Great work! More coffee for Roebeet
I guess ... better stick to TNT Lite 4.4 for now.
I am curious about (not in any hurry tho)
cwm+TnT Lite 4.4 ->fixrecovery.sh -> stock 3588 ->OTA 4349
--
msu_sparty.
I ran 3991 for a good while during the time the Wooters needed help.
I tried to install the Enhancement Pack on 3991 and it semi-bricked my
G-Tablet.
I wouldn't try it until someone tests it for sure -- unless you want to
be the tester!!!???
Rev
cbay said:
Great work! More coffee for Roebeet
I guess ... better stick to TNT Lite 4.4 for now.
I am curious about (not in any hurry tho)
cwm+TnT Lite 4.4 ->fixrecovery.sh -> stock 3588 ->OTA 4349
--
Click to expand...
Click to collapse
cwm+TnT Lite 4.4 ->fixrecovery.sh -> OTA 4349. This might work. Haven't tested it yet, but I will. It worked for build 3991, so it might work with 4349.
EDIT: One test, one success. Again, YMMV.
As a new tab owner where do I find the build number please?
Thank you
roebeet said:
cwm+TnT Lite 4.4 ->fixrecovery.sh -> OTA 4349. This might work. Haven't tested it yet, but I will. It worked for build 3991, so it might work with 4349.
Click to expand...
Click to collapse
Does fixrecovery.sh also add/enable the OTA updater? Or is there a update.zip for 4349 somewhere?
thanks for all the work,
--
Can 3588 enhancement be loaded with gapps for android market?
SoCal2 said:
As a new tab owner where do I find the build number please?
Thank you
Click to expand...
Click to collapse
Just go to settings-about device
butchconner said:
msu_sparty.
I ran 3991 for a good while during the time the Wooters needed help.
I tried to install the Enhancement Pack on 3991 and it semi-bricked my
G-Tablet.
I wouldn't try it until someone tests it for sure -- unless you want to
be the tester!!!???
Rev
Click to expand...
Click to collapse
Can you point me in the right direction to unbrick this thing? It semi-bricked mine, and I don't know where to start.
SoCal2 said:
As a new tab owner where do I find the build number please?
Thank you
Click to expand...
Click to collapse
Settings about
Thank god I was impatient and installed vegan 5.1.1 before this happened! Was waiting for ota 3588 before root as I was on 3389 this morning. I'm sure you guys won't be long figuring out if there anything worthwhile here.
cbay said:
Does fixrecovery.sh also add/enable the OTA updater? Or is there a update.zip for 4349 somewhere?
thanks for all the work,
--
Click to expand...
Click to collapse
No, it does not. All it does is flashes back 3588 recovery which is the recovery needed to flash between a 1.1-based and 1.2-based ROM.
yay! what we all knew to be the case a month ago is finally confirmed.
SoCal2,
The version number etc. is at Setting/About.
Rev
just lou,
A good start would be to read this thread. If you can do this procedure, it will NVFlash you back to stock version 2638 -- which we call bekit 1105 a lot.
http://forum.xda-developers.com/showthread.php?t=861950
Once you get to 2638, you can set up wifi and it will fairly quickly bring you an OTA Update notice and you can move up to 3588 -- and you can go where you want
from there.
Rev
Well best I recall mine was running 3588--whatever upgraded when I got it a couple weeks ago.
Sae the upgrade a few minutes ago, and opted to load it.
Now sits at "home", shows current (working) time, that I have linksys, that it is charged ((86%) and that sound is on.
Nothing else works. Oh yes, there is lower right hand icon showing an open padlock.
This came up after upgrade. I've powered off and on a couple of times.
Any recommendations?
Ok been running 4.04 for a sometime now. I got it as it first came out.
Some issues that u have noted outside of the bricking issue. **disclaimer I am running my own built version of this ROM deoxeded zipaligned bla bla bla plenty of tweaks etc and the ROM is faultless(not really it has its faults and I am about to list them) with exception of a few things that may or may not be kernel related. IT DID NOT flash the new .pit file. I have built the ROM as according to 4.03 builds and used Siyah kernel.
1. initial boot and dalvik cache build takes an extremely long time. Easily mistaken for bootloops and possibly another reason people prematurely ejected this ROM
2. Android is upgrading/updating splash does not exist. Further adds to the concern that phone has enternal bootloops...it doesn't it just doesn't warn you. It goes back to the gingerbread days where you wore a big question mark ? on your head "What is my device doing?"
3. Bluetooth enablement does not work. We go from 4.03 that had wifi issues much similar to fixed wifi and issues with bluetooth. Sux. Guess you cant win eh?
My guess is that this is specifically related to the kernel and framework. Ihave the framework decompiled now and I will be looking into maybe making some adjustments to allow for the bluetooth drivers in 4.03 kernels to interact with 4.04, rather than a whole new re-reslease of kernels just to combat this issue.
4. USB not detectable in Windows 7? Hmmm I am not sure what happened here? It worked flawlessly for 2 days and then all of a sudden not recognised? USB speeds were perfect when it did work, reflashing the ROM did not fix this? My guess is that this is also kernel<->framework related. Also to note here that within the siyah recovery you can mount USB no issues and transfere, so no eMMC corruptions before you freak out.
5. Vol down + power button for screen capture does not work? This again maybe because of the kernel used?
Can anyone give any reason for me not running the new pit and flashing stock kernel? Does the stock kernel require that there is a repartition or is this an assumption?
Additional notes: Further testing my eMMC with Gotbrickbug *MASSIVE thanks to chainfire for this support* personal thanks from me. Thanks Chainfire you're a legend! After testing it revealed oddly enough that my eMMC was inconclusive, so not that it helped me much, but I have flashed this firmware now several times and have not had any issues. Everything working smoothly and 100% except for the above mentioned.
I am tempted to flash the standard kernel now (again no repartition) and then do CFroot for the stock kernel image on this firmware to see if these issues are alleviated in 4.04?
Additional to this is that I have the 15 toggles mod by Jkay translated and compiled with exception of the last file on systemUI for 4.04. I would REALLY love to have this ROM running for everyone.
Any input suggestions warnings (besides the brick scare - I am not scared cause I doubt my phone will brick considering I have flashed it so many times now with the phone acting the same every single time)are welcomed. Please use your head when you respond and not your bricked phone, I would like intelligent answers and discussions. Preferrably not from n00bs or those that are only rehashing all that has spilled out across the petition thread already.
My understanding is that it is a repartition issue with bricking not a kernel or ROM issue its self. My understanding is that I can flash any kernel I like I can flash the stock one and I should be able to flash a rooted one after it to get back if I want?
Proceedure now:
Flash ROM
Flash kernel
Flash CFroot
Flash Modded recovery
Happy days?
I think most of those issues are due to Siyah, because I've tried the same builds running the stock kernel, and I didn't encounter most of them. Bluetooth fine, USB fine, etc. Nothing major. Still went back to LGP because the 4.0.4 implementations are quite ugly at this point.
Again flashed this ROM no problems.
I also attempted to run 4.04 czech republic version of this ROM to which it did not boot or run. Just to let those know that were considering doing this. I had 3 apks from that 4.04 build that refused to deodex? Also the sizes of all apks in this version of 4.04 (which does not come with a supplied .pit file) are vastly different to those in the Euro 4.04 supplied with .pit?
Yet to download and try 4.04 Chinese version? I figured someone else has probably already done this....the chinese are fast lil buggers. They don't much around! haha. If anyone has feel free (and please I would like you to contribute) to comment in this thread on your findings?
James
PS: Just about to flash standard kernel on unpartitioned GS2 if all goes well I will implement CF-Root. Cheers
donalgodon said:
I think most of those issues are due to Siyah, because I've tried the same builds running the stock kernel, and I didn't encounter most of them. Bluetooth fine, USB fine, etc. Nothing major. Still went back to LGP because the 4.0.4 implementations are quite ugly at this point.
Click to expand...
Click to collapse
Did you re-partition when you flashed stock kernel? I like the sounds of this. I have the 4.04 working nicely.....if i can achieve the above I will create a ROM and upload. Thank you for your valuable input
I may even test with the czec 4.04 kernel and see what happens there? Hmmm
Kernels are identicle sizes but not the same?
czec zimage: MD5 2A4AE1B758D934E2AD1791E318F94424
europe zimage: MD5 FCB26E67AE9E7F701793B6014E4AF7D2
see attached for additional size details? I am wondoering if czec might be better for no repartition was/is used in this 4.04 build?
James
WOW! I flashed standard kernel and I now have bluetooth enabled and I STILL kept root access. yeeeeeeeew! stoked!
Jarmezrocks said:
WOW! I flashed standard kernel and I now have bluetooth enabled and I STILL kept root access. yeeeeeeeew! stoked!
Click to expand...
Click to collapse
No fix for USB enablement? I have switched the customboot.sh for the MTP application. I however don't have MTP.apk in system? I may place this apk and then re-try to see if I might be able to get the thing to be recognised by my PC.
USB Mass storage is now working via the old method. I need to have the MTP client in system/app for this to work. No longer getting the USB device not recognised which is great.
Any kernel devs want to share with me how to embed the correct components in the kernel to allow for customboot.sh to work? I am certain then that USB mass storage will work when that script can be run and enabled at boot. I dare say that boot animations should work then also.
4.04 is starting to shape up nicely now
Hello...
I've spent about a good week and a half trying to root and install ICS on the A500 at where I work. My goal is to get ICS or higher on this device so that it can be used for testing purposes. I was able to root and install CWM but have not been able to flash ICS or JB. Am hoping you guys can point me in the right direction.
I have tried to flash cm-10-20121027-UNOFFICIAL-a500.zip and cm-9-20121221-NIGHTLY-a500.zip but what I get in both cases is my device hanging on the Acer logo. My last attempt I left the device like that over the weekend and this morning it was still displaying the logo.
The CM9 nightly wouldn't install at first until I came across a post that said to remove the first line of the install script, which I did, and the install seemed to happen but as I mentioned the device hung up at the Acer logo.
No idea how to move forward here... there are hundreds of posts and updates on the topic but quite frankly there are terms that I've never heard of, all sorts of caveats, specific recoveries that need to be used, dead links, etc... am making no progress.
I do have a backup up of HC, so am able to revert easily via CWM.
Current Android is 3.2.1, build is Acer_A500_7.014.02_COM_GEN2
@eyepoker..... I honestly don't see where your problem is provided you are prepared to load a custom ICS rom from any of the Developers in thread #3. Without picking out a favorite I would suggest any of "Civatos" FLEXxxxx ..... SHELLshock..... roms will give you a highly customized ICS Rom.
Be aware that you will have to load first an ICS Bootloader..... you cannot run these custom roms on a HC Bootloader, but in "Civatos" posts there are links to tutorials on how to do this.
The issue is that i can't flash a rom, it doesn't work. The device hangs with the Acer logo displayed and advances no farther after a flash and reboot.
Should my take away be that the latest CM nightly and the unofficial don't work? Should i not bother with CM? Is ClockworkMod old now - is there something else I should be looking for?
I'll look at the bootloader stuff you mentioned.
@eyepoker..... With respect you know your tab better than I, however unless you have bricked it (you don't say it is nor does anything you say about it suggest that is the case) then there is no earthly reason why you cannot load a ICS rom onto it. Now I am not going to say that there is a problem with the NIGHTLY updates of CM roms but is it possible that an app that you have previously installed is causing a problem with CM?
To prove to yourself that your tab can run ICS why don't you try the following.....
1) Follow the instructions in Civato's thread to load an unlocked ICS Bootloader..... I would recommend "v.8"
2) Download one of his ShellShock or Flex roms and put the zip file onto your External SD card - DON'T unzip the file leave it in it's zipped state.
3) Boot into CWM Recovery - do the necessary "wipes"
4) From within CWM install the zip from your SD Card
I am quite certain that the rom will install.
If the above doesn't work then I think there is far more wrong with your tab than it being unable to flash a rom.
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