Database Develop

[Q] Please don't flame - CW Recovery on VZW TAB?

I can't seem to find the answer - I've purchased the VZW Tab Bootstrapper, which at this point only seems to brick my tab - after Heimdalling, I installed Oldmacnut's Rooted Gingerbread Rom - ROM Manager says that CWR 3.0 is installed - if I push flash new recovery, the only devices i can select from are Galaxy i900 - assuming that the rom was built from this device - so, what do i need to do to get clockwork properly installed? If i volume up/power up, I get stock recovery - if I use ROM Manager, it gives me the triangle with a progress bar for a second or two, then reboots - don't want to reboot with the bootstrapper program again, as i don't want to re-brick my tab - unless I'm crazy, there doesn't seem to be an easy solution - am I crazy and/or blind? There seems to be a possible kernal solution, but I have to flash it, and I can't flash it if i can't get clockwork recovery going - i think. help....

yeah, all the bootstrappers only work for Froyo.
I released a CWM + EXT4 kernel with V1 of my Gingerbread roms, only the kernel doesnt have 3G.
I also started on a new kernel for both, 3G being an issue when i ran head first into CM7 for the tabs.
I then decided to hold off on the kernels as i was building a kernel for CM7, I thought I could release a new one.
Now, last night I thought about making a thread with all forms of "recovery" from Froyo to GB for people who need to reflash a tab back to stock, and offer a bone stock version, and a rooted version. I just need to finish uploading the remaining roms to my server for hosting before i can post it all.
I thought of this as alot of people ask where they can find X rom or X kernel, which is why i started on that mirror.
No reason to flame, the issue of CWM for GB and the bootstrappers have never been addressed publicly

Is there a way to stay on rfs with your cwm kernal you posted?

oldmacnut said:
yeah, all the bootstrappers only work for Froyo.
I released a CWM + EXT4 kernel with V1 of my Gingerbread roms, only the kernel doesnt have 3G.
I also started on a new kernel for both, 3G being an issue when i ran head first into CM7 for the tabs.
I then decided to hold off on the kernels as i was building a kernel for CM7, I thought I could release a new one.
Now, last night I thought about making a thread with all forms of "recovery" from Froyo to GB for people who need to reflash a tab back to stock, and offer a bone stock version, and a rooted version. I just need to finish uploading the remaining roms to my server for hosting before i can post it all.
I thought of this as alot of people ask where they can find X rom or X kernel, which is why i started on that mirror.
No reason to flame, the issue of CWM for GB and the bootstrappers have never been addressed publicly
Click to expand...
Click to collapse
Thanks - at least I know I'm not nuts - I honestly don't know that it's necessary to mess with the kernal that's in the GB rom you compiled - it works great as is - I'm just so used to flashing stuff through Clockwork from all the android phones I've had - new to the samsung/tab world, trying to get myself up to speed -
Thanks again for getting back to me, and please, PLEASE take care of yourself and family - this android world is supposed to be fun, not just for us that take advantage of the work that devs like yourself put in, but fun for the devs too - now put your feet up, pour yourself something cold, and watch some football.
Just make sure to have all the ROM's you started finished by morning...
My name is Jack, and I'm a romaholic.

Here is the thread you need to read first..
http://forum.xda-developers.com/showthread.php?t=1099036

TheATHEiST said:
Here is the thread you need to read first..
http://forum.xda-developers.com/showthread.php?t=1099036
Click to expand...
Click to collapse
Oops - copy that - thanks for the heads up.

Thread moved to Galaxy Tab Q&A.

Oldmacmnut,
I can't seem to get Heimdall working (or USB at all, for that matter) on my Tab. I have root, and I can reboot into recovery, although it isn't CWM recovery. I tend to believe that the problem is in a corrupt ROM install of some sort, and would like to either flash a stock ROM to get back to square 1 or a rooted ROM. Problem is, I think I need to figure out a way to do that through recovery as USB doesn't seem to work at all on any computer that I have tried. If you have a CWM Recovery that works, is it flashable in the stock recovery?
Thanks,
Seth

Rom

Seen an alpha 3 ICS rom. Can I just download that and flash it over my current rom or does it habecto be done certain way. I've flashed before on my evo but this seems a little bit more complicated
Sent from my SPH-P100 using XDA App

I'd rather go the full procedure they describe within their thread - imho especially you have needs for clockworkmod. Found that to be a quite safe way for me.

I would I just don't have access to a pc. Does ICS run fine on your tablet. Is it worth it
Sent from my SPH-P100 using XDA App

Once you have CWM Recovery installed, getting the ICS Alpha on your tab is not difficult if it's listed as supported in the thread.
Only thing: This is an ALPHA build. That means many things are not functional. The build is aimed at developers/testers.
Having given a shot at it, this build is surely not a daily driver for someone who needs its tab to be functional and reliable. Many of those problems have work arounds however but since the tablet is not mostly used by myself, I did not take the risk of having it be unreliable...
In short: it should work and not eat your hamster... But it is not a fully functional rom yet, be prepared for some trouble... Be sure you know how to go back in case of trouble... and read instructions carefully

If you want a good ICS rom here ya go. FYI!!! THIS IS FOR CDMA TABS!!!
Get rooted and CWM'd via Rodderick's thread in our Development section.
From there do the following (all credit to JT from here on out)
Download http://k.22aaf3.com/jt1134/vzwtab/cwm-recovery-5.0.2.7.tar
Extract the contents. You will have two files zImage and recovery.bin
Odin these two files to your tab while your tab is plugged in to the PC and in Download mode. This will bring your clockworkmod up to 5.0.2.7 which is a must to install the rom I'm about to link.
Next go to this thread
http://rootzwiki.com/topic/11697-rom-cdma-aosp-ics-cm9-build-31-0104-x-2/
At the bottom of the first post download the 3.1 ROM the 3.1 Patch and the gapps files.
Once those are downloaded boot your tab up to normal operations and plug it into your PC again. Now transfer those three files to your tab.
Boot up into clockwork recovery wipe the cache, dalvik, and do a factory data reset. Then flash the 3.1 file first, then flash the 3.1 Patch, then flash the gapps files.
If everything says it installed correctly the only things that won't be working are camera (which it does work in panorama mode) and possibly 3G. (Never tested 3G as I only use wifi).

Can you please post pictures and how can I check which cwm I already have? If I already have 5.0 can I just go ahead and flash? One more thing is this a whole new ICS or the ones going around. Thank you much

So I checked and I got 4.0 cwm. With that said. I don't have access to a pc. Is there any other way to upgrade to 5.0 cwm? PLEASE someone reply with yes. I'm getting bored with this andcwpuld like to try ICS. Thanks

rjumawan said:
So I checked and I got 4.0 cwm. With that said. I don't have access to a pc. Is there any other way to upgrade to 5.0 cwm? PLEASE someone reply with yes. I'm getting bored with this andcwpuld like to try ICS. Thanks
Click to expand...
Click to collapse
Without access to a PC I think you are making life very difficult for yourself.
You do not state what Tab you have; below I linked to the install for the P1010 only...I did this for reference because you will see it required Odin to flash it i.e. access to a PC.
http://forum.xda-developers.com/showpost.php?p=20195348&postcount=1

Thank for the reply. Yeah I know it makes it, harder just seeing if there was a way around it. I'm playing with the sprint galaxy tab. Not much to play with out there for it.

Issues With Touchpad

Hello, I have had a touchpad for some time and but CM9 and CWM on it some time ago, but it started having some issues recently. So I figured I should try and reinstall a newer version of CM and start from scratch.
I went to this post http://forum.xda-developers.com/showthread.php?t=2026692 and downloaded both the skz+tenderloin-1.10.zip and the gapps zip.
I then placed those into the Download folder on the touchpad.
This is where things took a turn. I rebooted to get into CWM, upon selecting it from the boot menu it kept restarting back to the boot menu. After a few tries it got into CWM. I then wiped the data and did a factory reset, wiped the cache, and then wiped the dalvik like the post said to do. I then went to install zip from sdcard. Found the skz+tenderloin zip and chose to install that. CWM says it starts to install but then before the progress bar fills up at all...it resets back to the bootloader.
At this point I am at a loss with what to do and I would really appreciate any help I can get with this.
UPDATE: I figured starting from scratch would be the best bet, so I have uninstalled CM9 and CWM using ACMEUninstall. Now I am wondering if it is worth using CM10 as my default Android or should I stick with the best CM9.
Either way, if I should use CM9 or 10 can someone either help me or point me in the right direction for the best tutorial on doing this properly?

Restore a backup then DL an updated version of CM9 to flash or upgrade to ACMEInstaller3 to give you a larger system partition along with the latest version of CWM in order to install a CM10 rom apart from oats which does not require the extra space .
There are numerous guides and you should probably read up on a little bit before just flashing a rom to avoid the problems you are having .

sstar said:
Restore a backup then DL an updated version of CM9 to flash or upgrade to ACMEInstaller3 to give you a larger system partition along with the latest version of CWM in order to install a CM10 rom apart from oats which does not require the extra space .
There are numerous guides and you should probably read up on a little bit before just flashing a rom to avoid the problems you are having .
Click to expand...
Click to collapse
The issue I am encountering is there is a ton of info out there, some outdated some not. I restored back to stock webOS with nothing else. I have ACMEInstaller 3 in the Palm directory, so I am ready to install the most stable/best CM9 currently out there, I just don't know which tutorial is the best one to follow. Could you perhaps just link me to one you recommend?

http://rootzwiki.com/topic/31548-ho...-with-sound-camera-microphone-updated-232013/

Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.

Saix_XIII said:
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Click to expand...
Click to collapse
I installed CM9 based on the link above with the AIO package. It worked flawlessly, hopefully my freezing/restarting issues happen less often now. Thanks to all who offered help.

Saix_XIII said:
Should I use CM10 or stick with 9? People say there are still issues with it and it's more of a preview build and not really meant to be used as your standard OS.
Click to expand...
Click to collapse
I can tell you that I use my Schizoid as my daily driver, and it's not a preview.

[ROMS] Stock Atrix HD Roms

Over the next week or so I plan on making stock, deodexed roms from our fastboot system.img's. Other than Root, Busybox, init.d support, insecure adb, and being deodexed, they'll be completely stock -- nothing removed, nothing else added -- and are to be used as roms, the base rom for ports, whatever.
If you don't need insecured adb, delete /system/etc/init.d/AdbdInsecured
I include it because its a necessary feature for me.
All the roms* will be uploaded to my Goo.im page for Atrix HD
All the roms are for the locked AT&T Atrix HD running Jellybean 4.1.1.
Do not flash Gapps with the Stock Roms
Currently Done
Mexico Retail 4.1.2
AT&T 4.1.1* (not mine, see below)
To Do
Bell 4.1.2 (Jellybean)
ATT 7.7.1Q-115 (ICS)
Bell 7.7.1Q-115 (ICS)
ATT 7.7.1Q-144 (ICS)
Mods
Currently the only Mod available is the Extended Reboot Menu for stock AT&T DeOdexed, I'll make the same mod for other stock roms as I have the time.
Mexico Retail Info
Jellybean 4.1.2
Moto Blur 98.2.2 (oddly, AT&T JB 4.1.1 is Blur 98.4.20 -- this rom is higher Android Version, Lower Blur Version -- weird)
Very little bloat
WIFI didn't work until I added in the kernel modules from Stock AT&T. If you have errors, see first if it could be module related and replace the offending one.
* STOCK AT&T INFO
The stock AT&T rom is located on the Batakang FTP server and was not done by me. I assume Mattlgroff or SirHoover did that one. Someone let me know so I can give proper credits & thanks. It does not contain InsecuredAdb or init.d support. When I finish up the other stock roms on the list I'll make a Stock AT&T of my own, unless the current one's maker doesn't mind me adding init.d support and InsecuredAdb like the rest of mine on goo.im will have.
To Rom Cooks
For init.d support, I hid the init.d initialize command in /system/etc/init.qcom.bt.sh. Let me know if there's a better place to put that command or a script activated earlier in the init process we can edit.
Feel free to use my stock roms for whatever project you want. Thanks and credits are appreciated but not required.
I'm unsure if the ICS roms will even work with the Jellybean kernel & boot. I'll be finding out later on today.
Credit and Thanks
Gotta give Mattlgroff credit for the InsecuredAdb and reverse engineering Chainfire's
Thank You to whoever uploaded the Stock ATT Deodex on Batakang, I'm using its updater-script, su binary, & superuser.apk. I was lazy on the su part

I'm working on getting ICS to boot with the AT&T Jellybean kernel.
So far I'm able to get it to boot, do a complete gapps setup, but after that, it bootloops within a minute of accessing the homescreen.
Boots after that loop on the animation or will give ~30 seconds of usable display before looping.
Factory resetting allows for completing the initial setup.
If I sit on the Gapps setup page, it'll eventually start looping, but much longer than if I finished and accessed the homescreen.
I'm unable to pull any kind of logcat, ddms, etc since I can't get the PC to recognize it over usb (driver error???)
Any ideas?
I've tried replacing kernel modules with JB versions -- didn't work. By then it was after midnight so I went to sleep. That's where I'm at now. Gonna start testing out JB binaries and libs today.
Since we're able to get a working display, that makes me think that a stock ICS rom for JB users is possible. We just gotta figure out what needs to be backported from Jellybean. Maybe a new init script or an init.d script that'll fix what JB sets that ICS doesn't like.
Can someone running ICS please upload their init scripts? I'd like to compare them with JB's.

RAZRHD 4.1.2 firmware if you're still interested: http://sbf.droid-developers.org/vanquish/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml.zip
As for getting ICS to boot, I think you're spot-on about the init files. Safestrap doesn't mess with / files, but it does create symlinks for /system, etc & execute init files that are placed in /system/etc/rootfs. This might be key to your efforts.
Epinter has a CM10 rom that uses a modified ICS kernel, but it has no problem running on my JB phone with SS (minus the camera). Although I had to repair his inits to fix a boot error & insert two /bin files. Perhaps you could use his rootfs/inits as a guide on getting ICS to work with SS on JB.
My safestrap fix for Epinter: http://forum.xda-developers.com/showthread.php?t=2178123
Epinter's ICS-based CM10: http://d-h.st/ML8
Update: Just found this: http://rootzwiki.com/topic/8794-bionic-safestrap-bootstrap-recovery-12142011/page__st__20
It says that SS moves anything in /system/etc/rootfs to /, so if you can get a hold of the ICS init files, that should be all you need to fix the boot.

SS, while convenient, is a serious pain in the ass as far as the init process goes....I miss Defy's 2nd-Init in that regard. Everything was in /system/bootmenu/*. The downfall with 2nd-Init is you lose and reinstall the bootmenu with every rom install -- Accidentally wipe /system and not install a rom? -- sbf time .
I'll take a look at the RAZR HD 4.1.2 fastboot today or tomorrow. Rainy day, so maybe today. I'm just hoping that the lapdock fix isn't kernel deep.
Thanks for the links, I'm sure they'll be invaluable.
I'm guessing here, but I think ICS's biggest issue is\will be USB -- I'm unable to get anything USB to work -- phone detecting USB or the PC detecting the Phone. Working blind with no logs, no usb, and a looping boot animation really sucks. With any luck, Moto didn't fully remove USB mounting via the kernel, only SW blocks in JB. While only briefly, I know that at least the display works, bluetooth turns on and off, I think audio works (can't remember if it beeped or not with the rocker presses),
Time to search for ICS init scripts then.

Later on tonight I'm going to upload the ICS dumps. They still don't work but I figured the libraries and binaries could be useful with CM10 porting. The Bell will be flashable since it has a working display -- if only until non stop looping .
For some interesting info...there are 2 different sets of ICS camera drivers. The first is 1st AT&T\Bell and the second is the other AT&T. Means ya got two different sets of drivers to test when porting .
/I really need to update my banner below :silly:
UPDATE
They're all uploading now. Should be done in 5-7 hours. My upload speed sucks.
All are flashable, but the ICS ones don't work. Only Tested 144-att and 115-bell.
I'm also uploading 4.1.2 Bell. It's untested but should work.
Obviously, only flash these on a rom slot. I've only used and tested on slot 1.

Skeevy , i really hope you or somebody else makes Paranoid Android available for AHD ( i know it's wishful thinking ).
For me its the only ROM worth flashing with the same android base version for the AHD . Not undermining the developer's efforts , all other ROMs (with same base version 4.1) that i came across here , I can get the same functionality and ui changes from a combination of custom launcher , root apps and some minor fixes here and there . I have not yet flashed a single custom ROM on my AHD , just rooted it and debloated it for the same reason .
I used to own a defy which was officially upgraded till froyo 2.2 only and boy did i flash the **** out of it . But that was only because of worthwhile functionalities in custom ROMs(be it CM 7,CM 10 by quarx, PA by you or MIUI) that couldn't be achieved by mere root apps or custom launchers .

thanks for this rom

AnkurBedi said:
Skeevy , i really hope you or somebody else makes Paranoid Android available for AHD ( i know it's wishful thinking ).
For me its the only ROM worth flashing with the same android base version for the AHD . Not undermining the developer's efforts , all other ROMs (with same base version 4.1) that i came across here , I can get the same functionality and ui changes from a combination of custom launcher , root apps and some minor fixes here and there . I have not yet flashed a single custom ROM on my AHD , just rooted it and debloated it for the same reason .
I used to own a defy which was officially upgraded till froyo 2.2 only and boy did i flash the **** out of it . But that was only because of worthwhile functionalities in custom ROMs(be it CM 7,CM 10 by quarx, PA by you or MIUI) that couldn't be achieved by mere root apps or custom launchers .
Click to expand...
Click to collapse
I'll be straight up with you, I could make PA for us but it wouldn't be the latest version. It would be 2.5.3 just like the Defy -- AOSPA (PA 3.0+) won't be possible until we're able to get AOSP to compile from source (the SourceForge crap). It would be based on Epinter's CM10, have the same bugs as CM10...basically I'd be making PA for another device then porting that over for us . It would probably take me 6-12 hours to do all the source merging, another 2 to compile, and a day to test then upload. There is no ETA cause I haven't started on anything nor is it on my to do list yet. Times are based on how long it took me to do the Defy merging, compiling, testing.
I'm unsure on the 4.1.2 Bell rom, but the 4.1.2 Mex Retail is worth using instead of stock -- less bloat, no entitlement checks.
I partially agree on the other 4.1 custom roms -- yes, you can do it all yourself, but not everyone can. Also, not everything is compatible, so if you don't know what you're doing and flash a bad, lets say audio tweak, and it doesn't work or loops you, you could be screwed simply by lack of knowledge. That's also why I released the one custom thing I've done as a standalone mod.
Rom cooks do a lot behind the scenes -- I've been working on a rom on and off since I've had my AHD. Only mentioned in here, in a PM, and maybe publicly once or twice. I've been testing various audio tweaks, launchers, scripts, mods....I don't want to give 2-3 week eta posts cause life happens, it might not work when I get to the moment of truth, and something always happens to make any specific eta I give wrong . I've been doing tons of testing, looking for something different than the AT&T stock base or RAZR port base(see this thread :silly, tons of apk decompiling (every 4.1.2 Atrix HD apk so far), and have been adding French\Canadian English to the MR base (25 apps in). Other than that, all I know is its gonna be PlayStation Certified (already have PS Store fully working). Can't say more cause I don't know any more than that :cyclops: Point is, other cooks do tons of crap behind the scenes to ensure a good, working environment that you can't get without doing\knowing some ****. If I wasn't trying to do so much I might have had something usable by now -- I've messed with ICS, CM10 porting, SF sources, stock smali mods, my own rom, alternate stock roms.
Luckily, I still have my Defy and Bravo. Quarx is still going strong and pushing out new CM's, kernels, and everything good. One can only hope that we'll have even a quarter of the roms the Defy has. I'm so glad my first Android phone was a Defy clone. I've learned a lot because of it.

Looking forward for your custom rom skeevy :thumbup:
Sent from my MB886 using xda app-developers app

Going to test out the Bell ROM and will report results later tonight or tomorrow. Thanks so much for the upload and the work youve done so far!

I'm trying to boot into the Bell ROM and am currently stuck at a bootloop when the boot image says "Android" not sure what to do to correct this problem, I have the zip file install in ROM Slot 1 with 2GB partition size
Edit: Tried again with 1GB size also just to see if there was any difference, the error im getting has to do with the md5 of the ROM, when i enable both checks it automatically fails, however if i bypass them and continue to flash the ROM it gets stuck in a bootloop as mentioned before

Thanks a lot for your hard work,skeevy. I had a Defy green lense two years ago and sold it a year ago. Luckily,I still can enjoy modding it coz my friend still got it. It's a beast phone with all those mods by you,quarx,epsilon and maniac103. With the lack of official updates and locked bootloader,Defy can do all the impossible things. I've even seen the newest 3.x kernel with CM10.1. You guys have done a great job. Let's hope Atrix HD got the same treatment.
Sent from my MB886 using Tapatalk 2

freshlycutlawn said:
I'm trying to boot into the Bell ROM and am currently stuck at a bootloop when the boot image says "Android" not sure what to do to correct this problem, I have the zip file install in ROM Slot 1 with 2GB partition size
Click to expand...
Click to collapse
Try replacing kernel modules with the stock AT&T ones. After that I'd be guessing and would need to see a logcat if possible. That's for Bell JB, btw. Not sure what to do with any of the ICS roms at the moment.
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.

skeevy420 said:
Try replacing kernel modules with the stock AT&T ones. After that I'd be guessing and would need to see a logcat if possible. That's for Bell JB, btw. Not sure what to do with any of the ICS roms at the moment.
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.
Click to expand...
Click to collapse
I will try that tonight when I get a chance and let you know how it works. The only thing im wondering is that since my device currently with bell is only on 4.0.4 that the kernel with jellybean roms wont work because I dont have the right kernel to go with the JB rom

freshlycutlawn said:
I will try that tonight when I get a chance and let you know how it works. The only thing im wondering is that since my device currently with bell is only on 4.0.4 that the kernel with jellybean roms wont work because I dont have the right kernel to go with the JB rom
Click to expand...
Click to collapse
Did not know that...could also be an init script issue then. Ignore the first suggestion, I assumed you were an AT&T JB user, use the Bell ICS modules instead.

skeevy420 said:
@huatz84
If we only had Quarx, Epsylon, and Maniac103....man, AHD development would really kick off. Those 3 get **** done. I mean, they only had JB running on a Froyo kernel with Froyo\GB hybrid drivers and only 317mb of /system space to work with.
Click to expand...
Click to collapse
Yeah..they are amazing. With the tiny system space,they can build a stable JB rom with Froyo kernel. They've made impossible things.
Btw,I just saw that Moto includes Razr HD and Razr M to their unlocked bootloader program. Hopefully,They add Atrix HD soon.

skeevy420 said:
Did not know that...could also be an init script issue then. Ignore the first suggestion, I assumed you were an AT&T JB user, use the Bell ICS modules instead.
Click to expand...
Click to collapse
I'm going to try to flash the Bell ICS file and see how that goes and if it triggers an OTA update, if theres anything I can do to help with the development of these ROMs please let me know, I have access to a Bell Atrix HD with an unlocked bootloader so id like to do all I can
Edit: Tried the 4.0.4 Bell ROM just now and I'm getting the same error while trying to flash
--Verify md5 for /external_sd/404-115-bell.zip
-- No md5 file found!
If I uncheck the boxes to verify the md5 I can successfully flash the zip but it still gets stuck in the bootloop like the JB ROM
EDIT:
Successfully booted into the ICS ROM since I was on 4.0.4 myself and am getting the prompt to update to 4.1.2 now, it looks like when you upgrade to 4.1.2 the kernel becomes incompatable with the older ROM's and vice versa. It looks like once one is on JB there is no going back. The flash worked without me ticking the boxes which doesn't seem to be the problem, only firmware, hopefully this helps and explains why the ICS ROMS begin to instantly bootloop once you try to boot into them since im assuming youve updated at this point. Since I used a 2GB ROM slot I was getting low memory errors so I'm going to remake the slot with 1GB and am going to reflash and try the update and see if the flash for 4.1.2 directly works and if I can boot back into 4.0.4 again.

huatz84 said:
Yeah..they are amazing. With the tiny system space,they can build a stable JB rom with Froyo kernel. They've made impossible things.
Btw,I just saw that Moto includes Razr HD and Razr M to their unlocked bootloader program. Hopefully,They add Atrix HD soon.
Click to expand...
Click to collapse
Me too. Sucks we have an unlockable bootloader that we can't unlock due to Moto not supporting it. Some HD's are unlockable which is the real teaser to the rest of us.
freshlycutlawn said:
I'm going to try to flash the Bell ICS file and see how that goes and if it triggers an OTA update, if theres anything I can do to help with the development of these ROMs please let me know, I have access to a Bell Atrix HD with an unlocked bootloader so id like to do all I can
Edit: Tried the 4.0.4 Bell ROM just now and I'm getting the same error while trying to flash
--Verify md5 for /external_sd/404-115-bell.zip
-- No md5 file found!
If I uncheck the boxes to verify the md5 I can successfully flash the zip but it still gets stuck in the bootloop like the JB ROM
EDIT:
Successfully booted into the ICS ROM since I was on 4.0.4 myself and am getting the prompt to update to 4.1.2 now, it looks like when you upgrade to 4.1.2 the kernel becomes incompatable with the older ROM's and vice versa. It looks like once one is on JB there is no going back. The flash worked without me ticking the boxes which doesn't seem to be the problem, only firmware, hopefully this helps and explains why the ICS ROMS begin to instantly bootloop once you try to boot into them since im assuming youve updated at this point. Since I used a 2GB ROM slot I was getting low memory errors so I'm going to remake the slot with 1GB and am going to reflash and try the update and see if the flash for 4.1.2 directly works and if I can boot back into 4.0.4 again.
Click to expand...
Click to collapse
Good to know that. Sucks JB doesn't work for you, but at least we're both able to get to the boot animation and loop it -- we could be stuck at the boot logo. With any luck I'm hoping that we can find the right combination of files to replace to get the roms to boot with the wrong kernels. We at least know its possible since JB kernel can have a working ICS rom for about 3 minutes .
Since you have an unlockable bootloader why don't you just flash a jellybean boot.img? Unpack and repack it so its not signed and you shouldn't have any issues. You could probably start using the RAZR HD unlocked bootloader roms and recoveries and never see us again.

Holy crap... I am running ICS on my JB AHD!!! It's been 10 minutes and no boot loops so far
I restored a Safestrap ICS backup, then put some ICS init files in etc/rootfs (I attached my flashable ZIP fix).
Camera doesn't work - same for WIFI but I'm sure it's a simple driver fix.
Also attached are the full ICS init files, in case you want to compare and contrast with JB inits. I omitted qcom inits in my fix.

Well that's awesome. 10 minutes beats what I've been able to do :highfive:
Wifi didn't work with MR either -- I needed AT&T wifi modules (or probably the wifi modules of the stock kernel currently running). -- /system/lib/modules/prima/* & system/lib/modules/config.ko
From what I can tell we have 3 sets of Camera Drivers (2 are ICS drivers, 1 more for JB) -- 115-att & 115-bell are the same\1st one, 144-att is 2nd, & all JB roms are the same\3rd. I'm unsure as to what all libs are necessary for the camera with us other than the obvious /lib/camera*, lib/hw/camera*, and bin/mm-qcamera-daemon. We might need to use the JB camera app as well. Also, the 144-att camera libs have more files than the 115's -- they're similar to the JB ones (1st driver doesn't have /lib/libchromatix_ov8820_hfr_60fps.so, everyone else does).
The biggest difference of the 3 JB roms, from what I can tell, are the kernel modules; libraries and drivers are the same.
I'm being a little optimistic, but hopefully whatever works for ICS on JB kernel will work for CM10 as well; and that we can invert what we're doing to get JB working with the ICS kernel.
I know what I'm doing today.

[Q] Vicious circle on p990.

Hello, i just bought an LG Optimus x2 and i'm trying to get CM10.1 (at least) inside of it.
the thing is, this phone came with what seems to be a custom firmware and bootloader. At bootup it says vtr.com which seems to be a chilean provider. (i'm in Uruguay....) Just bought it new... cant understand why this came like that.
If i try to put clockworkmod, i'm suppossed to do it on a rooted phone.
If i try to root the phone, everywhere says i need to access CWM...
I'm deeply confused.
This pone has not a menu when booting into recovery mode, it just says "firmware update, wait until update finished" i can't choose any file from SD external nor internal.
I have tried several tutorials, using nvflash, using superoneclick... Nothing works.
BTW, i have smartflash just in case i cant put CM10.1 so i tought about putting the official ICS rom, but i dont want to use it, i want cyanogenmod.
Would be a way to achieve what i want to put ICS, then root, then put clockworkmod, then go back to gingerbread and then put cyanogenmod?
Plz help, and thanks for your time.

A lot of ROM-choices
No problem:
1. Sounds to me you have to do a full wipe and start from scratch. The AIO-tool is perfectly suited for this: see AIO option 4. - it will wipe and repartition your phone, install bootloader and root your phone at once (and it can do a lot more).
2. Before wipe, please think about what bootloader (bl) you want: in general old bl is for the older gingerbread-based ROMs, new bl is for most newest ROMs (although some also run on old bl).
3. Then think about what ROM you want. ROM choice is very personal. You could experiment. Just remember to make backups along the way. With the AIO-tool you can even choose Dual Boot for enabling easy-switching between two ROMs (as long they are on the same bl). LG-ROMs are generally not considered best (although some disagree).
3a. I have been running CM7.2 with ETaNa 2.6.32.y kernel (requires old bl) for a long time and was very happy.
But this is an old ROM. If you want to have a newer there are several possibilities (which in general require new bl). I have been very happy with 3b and 3c.
3b. Currently, I am on Pengus77's Look Ma No Hands which is based on CM10 (Ice Cream Sandwich). It is fast and responsive, has low battery consumption and all features (like BT, HDMI) work.
3c. tonyp's CM10.1 (JellyBean) is fast and responsive too and most features (BT yes, but HDMI no) work.
3c. If you want tonyp's latest, try theROM is based on CM10.2 (newer optimised JellyBean). So it got the latest Android stuff, but is experimental (it is not made for our somewhat outdated phone) and some features (BT & HDMI no) do not work (I have not tried this ROM), but
3d. there are a lot of other good ROMs out there. Check the list here.
4. ICS and JB ROMs require different kernels. All ROMs come with required kernels, but these get updated too. I use Kowalski Kernel M1 and flash most updates.
5. After flashing and stabilising the ROM, you can overclock the cpu with eg. Cpu Adjuster. I have have overclocked to 1404MHz, but even 1500MHz is considered safe.
6. The p990 does not have much RAM, so you could consider using Greenify to freeze non-essential apps (eg. facebook/maps/...) which consume memory in standby. Please note, dedicated notifications will not work.
7. After finding the best setup for you, please consider to donate to related devs.
8. Be careful not to become a real flashoholic
Good luck!
PS 5. and 6. might not work on gingerbread-based ROMs

Awesome reply man! Just my 2 cents... CM10 is based on Jellybean too. In fact, it's a 4.1.2 incarnation, while Ice Cream Sandwich was/is 4.0.X. Google kept the jb name from 4.1 to 4.3 because all the updates weren't that major

Ok, thanks pals for your answers, i had some doubts about versions but oneearleft cleared them.
Finally i installed nightly 10.2 Cyanogenmod, had to make a couple of full wipes via reflashing, there was a method to do it wich buttons but didn't work.
Finally i flashed latest LG rom, then i could put CWM and after that Cyanogenmod. If i'm not too crazy, i did all using AIO-Tool.
Sorry if i cant be a bit clearer, but i finished 4AM and with a half bottle of booze inside, so i really cant remember much.
Thanks again.
EDIT: Also, CM10.2 (4.2.2) has BT working, Still could not try HDMI.
EDIT2: I forgot, (booze) at one point, when i installed an official LG-rom for a random provider (Claro-CTI) after a reboot, i saw the "android" android and the phone went to an infinite reboot loop.
That's why i flashed the official ICS rom from LG. This took out the odd botloader and put the nice LG logo with a crisp animation. (vtr.com one was awful and frozed)
Then after that i could flash cyanogenmod with the bootloader that rom brought.

Fyi the roms don't replace the bootloader. Being a tegra device, the bl has to be flashed as a separate step via nflash.

I dont know how it happened or why, i just saw the android and the device became looper. After that, i could reflash it.
I'm really confused about what happened but i have reflashed it several times, i tested CM7.1, CM10.1, 10.2 and i'm about to put P.A.C.man.
My main interest was to be more used to the flashing methods, bootloader and such. (i really knew/know nothing)
Now i'm about to find if i have the new or old bootloader so i can install PACman.
Wish me luck.

Ok now... This cellphone is awesome, sadly the only stable are way too old.
So, ¿Is anywhere a CM9 for this phone? I would love to keep cyanogenmod with it's own appearance and tools but without loosing HDMI, WiFi tether, BT and good battery life.
I've searching for it, but could'nt find.
Thanks.