Database Develop

[Q] MIUI for the galaxy beam!! ^^

Hello, people of xdadevelopers! I'm new here and keen to learn up on custom Android roms. Sorry if i sound really noob or am doing things wrong in this forum, but... everybody has their own starting phases right?? ^^ Please guide me where I'm going wrong...
Anyway, I'm from Singapore and i own a SAMSUNG GALAXY BEAM GT-I8520 (rare and unheard of phone released only in Singapore x.x). I won't elaborate much, but basically I'm kind of still a student (therefore no money to buy other phones) and my mobile plan is left with about 11 months to go before i can renew my plan and select another phone for a cheaper price... I don't really like my phone because the moment Samsung released it, they decided to stop updates because there is not enough users of this phone so I'm stuck with 2.1 eclair. It also has a slow 500/700mhz processor and lags like he**. By the way, it was released around July 2010 at the same time with the Galaxy S, and they have really similar specs, that's why i posted in this area of the forums.
So, i was thinking of switching over to the MIUI rom which i desperately want... and i decided to follow the Galaxy S I9000 (because they are sister phones!) tutorials to flash over to MIUI in hope it would revitalise my phone, stop the laggyness and crashes, give it a new look, allow me to use features that i miss out in froyo or gingerbread!!
I can understand most terms and softwares about flashing... been researching for a few days... and i found this guide
http://forum.xda-developers.com/showthread.php?t=1101601
which tells me to replace my bootloader with a gingerbread bootloader through ezodin, then boot into recovery mode which is the custom cwm recovery, and from there straight up install my rom that was placed in the sd card, and walla i get my MIUI. I assume that the bootloader will give me CWM recovery because the guide doesnt tell me to get it through rom manager. I currently have the base google stock recovery, so question <1> do i have to install cwm recovery through rom manager first or will the gb bootloader give it to me once flashed? and question <2> i've tried to install it through rom manager but it didnt work the first try (i chose my phone model as the S) and even erased all my apps and data :S Is there a way to go around installing clorkworkmod? I understand my phone isn't EXACTLY Galaxy S, but they're similar...
Also, another problem i face is that i DON'T have the 3 button shortcut to recovery mode or download mode. I'm following this tutorial to try repair it, since I've heard a batch of Samsung galaxy s have flawed recover and download modes that can't be accessed by the 3 buttons. since the two phones were released around the same time, it could be that the galaxy beam was affected also. Everything is fine going through this tutorial (even getting to download mode trough ADB is fine), problem is i get stuck every single time in ODIN at SetupConnection. Question <3> any freaking idea how to solve this? I've gone through google and searched through this forum... Now i don't know what to do and don't dare try anything else or other flashing unless i fix this 3 button shortcut because i know i can only access recovery or download through ADB REBOOT RECOVERY / DOWNLOAD and the phone has to be plugged in, turned on, booted into android, and in usb debug mode. the ADB command won't work if the phone is off and i'm worried the GB bootloader will stop eclair from loading.
This leads to the question <4> if i decide not to follow this repairing tutorial and just flash the gingerbread bootloader up front, will it give me the 3 button shortcut boot? because if i am not able to load the eclair rom with gingerbread bootloader, and have no 3 button shortcut, i will not be able to boot into recovery to install rom and wipe data and cache etc. Also, if i flash the gingerbread bootloader, can i still load into my stock eclair rom? If i can load into the stock eclair rom, then i don't need the 3 button shortcut, i can go straight to doing usb debug and the ADB command again after flashing bootloader and rebooting to go straight into recovery and installing MIUI.
Question <5> What about gingerbread bootloaders that can backtrack and load froyo roms and eclair roms? Do these exist? Where to download? If so, i can load into my eclair rom and use ADB for recovery mode, eliminating the step: repairing the 3 buttons.
Question <6> Also, i noticed the guide didn't speak anything about kernels etc. From what I understand about kernels, it is the architecture or system between the hardware and the software. People can tweak kernels (leading to custom kernels) for different and maybe even better sound and video etc right? But the guide doesn't say anything about installing a custom kernel, so am i supposed to keep my current Zues kernel from Samsung, or is a custom kernel recommended by MIUI ALREADY provided in the zip folder i downloaded from here? (the I9000 one) When i flash this zip through CWM recovery, is the kernel changed together? Does this apply for the bootloader also? Is the bootloader supplied in the zip and flashed together at the same time? if everything, (rom kernel bootloader) is flashed together at the same time then i can eliminate many steps and just work on installing CWM recovery through rom manager. then use adb to boot into recovery and flash that one simple MIUI zip. no need for 3 button boot...
Question <7> Is there another way to get MIUI to install on my device without so much hassle? haha..
Thanks for the trouble, I know it's a lot of questions... Please answer whatever you can

umm, almost a 100 views... but no replies? :'(

I'd never heard of it until this post, I looked at some specs and they're quite significantly different to the SGS's ones, smaller screen and completely different processor(which is most important(TI OMAP 3440 720MHz in the Beam and Hummingbird S5PC110 in the SGS)). It's a completely different phone, don't even try to install MIUI for the I9000 on it unless you don't mind your phone being in a bricked state. I may not be right but it's my strong opinion. Here is the Xda wiki for it: http://forum.xda-developers.com/wiki/index.php?title=Samsung_Beam Which shows how to root and then OC it which may increase performance. And if you like the Miui look there is a look a like launcher floating round if you search. Good luck

true, they aren't exactly the same. the processor is definitely different, but i think MIUI was made for performance, which fits well with this lousy processor haha. screen shouldn't be a problem, most softwares fit to screens automatically. I've already Rooted and OC'ed it but its still slow.
Is there any way to flash everything at once, e.g. kernel rom everything flash together at the same time using ODIN, then maybe i will reboot and see if the MIUI works... The problematic part is the 3 buttons download mode. I'm willing to flash everything at once then see if i'm lucky and MIUI will work for me. I'm not willing to flash just kernel or etc, then can't get in to download mode already because phone cant be booted, thus cannot install ROM...
Does anybody know exactly what when flashed into the phone gives me the 3 button recovery and download...?
I also realised something in the wiki link u gave me...
Power+Menu+Volume Down -> Soft Reset
Power+menu+Volume Up -> Ready for Flash Screen
Could this be my recovery and download...? I'll try later.

I'll try and give you an example, the Galaxy SL or the I9003 came out the start of this year as a replacement for the original with the only difference being the chipset and display type. Quite a few people have got this phone and have being trying to get Miui to work on it hasn't happened. The I9000 kernel for Miui is made for the I9000, it only works with the Hummingbird chipset, end of story. I'm not stopping you from trying but expect the most likely consequence to be the phone dead, not running Miui.

Wow, if the I9003 which was even closer (spec-wise) to the I9000 can't flash I9000 MIUI, then my I8520 won't make it... :'( I understand what you mean, any kernel made for I9000 phones, even custom user-made ones, only work with specific hardware, like that chipset, unless that kernel some how is clever enough to work with my hardware, or probably just lucky enough to be compatible with my chipset.
I didn't know the software had to confirm so tightly to the hardware... I'd always thought software would automatically work with basic hardware, albeit there would be some issues and glitches, but at least it would still work. I thought maybe it would be possible to keep my Zues kernel, and just flash the rom, and let the rom use my kernel.. It wouldn't be very optimised because they weren't made for each other, but at least with a few bugs, still usable... But now I know my Zues kernel works with my hardware but probably wont work with I900 MIUI unless it was coded for my phone... Though, if my phone does have the same chipset and gpu, maybe it will work?
Seems like I'll have to continue to use this lousy unsupported phone :S
Thanks for your help

CM9 or ICS Alpha 3?

What is the difference with these 2 and which one should i choose. I got the alpha 3 right now
Sent from my GT-P1000 using XDA App

Hm... I'll chosse Cyanogenmod 9, I dont know because my tab is p1010 (no ics or cm9), but i think that Cyanogenmod is better.

Hey, did any of you try CM9? I tried 3 times and every time fail. Even after patched zImage came out. I can enter to recovery, do wipe factory, wipe cache but device doesn't boot. Stuck on inital GalaxyTab/SAmsung logo. Cant ask in correct thread as this is my first post.
I uploaded 1000L.zip, then with Heimdall uploaded zImage. Tried with 1000L.zip with replaced zImage in it but this zip can;t be installed (wrong file or sth).

Hi
i would download CM9 because GPS works

Do you know - what version of Google Voice Recognition is used in Alpha 3?
In CM9 you only have standard voice input without "open microphone" feature.

I've installed CM9, and it works, but it's an alpha and not for daily use. The developers are working hard, but there are no easily installable packages yet, or instructions how to get it installed or working. I started with Overcome 4.1, and got the current build. As it is, it's for the P1000L, so you have to get the P1000 kernel as well, and you have to replace the one in the ZIP with that one. You shouldn't just create a new ZIP, because it needs to be signed, and a new one won't be. Then you can update with recovery.
A lot of stuff works, but a number aren't, and as the phone is one of those not working (yet), people who want to just use the Tab probably shouldn't try this. If you like to get developing, or want to help out, know what you're doing and don't mind having a not fully functioning Tab, you can look up the the thread in the development section, get stuck in.

I installed CM9 yesterday and am LOVING it! I followed all directions from Humberos and others that are diligently working on bugs and have almost all functions working (calls/2g/3g/wifi/etc).
Camera doesn't work in normal functions, but will capture an image in panorama mode. This is coming along nicely!

CM9 and Alpha 3 has their good and bad, not to forget, both are still in testing stage and not meant for daily use at the moment.
For now it seems that cm9 has the upper hand in being more stable.

you could also try icedBoca... like the others, different things work
atm i'm on CM9 and most of the stuff works, but i can't connect to "hidden" wifi networks and internal sd / external sd mounting is a little bit mixed up

CM9 of course, I have the galaxy tab P1000N, and i have problems with alpha3 to much bugs and never fix them. Try to use CM9 with Humberos kernel, the room are much better and stable, free lag and never shut down. if u dont like try to use Boca rc1 final version

CM9
CM9 is better. I've tried both on my GSM P1000 and the CM9 is more refined and the repo is being constantly updated if you want to build it yourself.

Yep, CM9 is better but the Alpha 3 is good with few defaults...
I can't wait to flash the two...
What about HW acceleration with CM9 ? The build can play 720p but we don't know if we can play with big games like GTA...

CM9 is whole lot better, it has bluetooth, GPS and many more things working compared to Alpha 3. Today they have even declared USB Hosting is also working.
However, I would wait a little, till they incorporate all the small bugfixes in the ROM/Kernel.

brodzky said:
Hey, did any of you try CM9? I tried 3 times and every time fail. Even after patched zImage came out. I can enter to recovery, do wipe factory, wipe cache but device doesn't boot. Stuck on inital GalaxyTab/SAmsung logo. Cant ask in correct thread as this is my first post.
I uploaded 1000L.zip, then with Heimdall uploaded zImage. Tried with 1000L.zip with replaced zImage in it but this zip can;t be installed (wrong file or sth).
Click to expand...
Click to collapse
Have you wiped dalvik cache?
BTW I recommend you to use the flashable kernel (Download Page then go to "CwM flashable - Kernel", press P1000 or the appropriate model and download)
In fact a flashable zip should be SignApp'd. Have you do this after you modified a flashable zip. Ask the best friend in the new era how!

One question.. are the roms like, interchangable? Can I switch to each ROMs as per needed?
Also, can I downgrade back to a 2.3 version of Android afterwards?

delusioned said:
One question.. are the roms like, interchangable? Can I switch to each ROMs as per needed?
Also, can I downgrade back to a 2.3 version of Android afterwards?
Click to expand...
Click to collapse
With CWM/Recoverymode ,no. The problem is the ext4 formating. It is only possible if you flash the firmware 2.3 complete new with odin.

[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] GT-P1000 Custom ROM for Rooted Device

Hello everyone.
I have a Samsung Galaxy Tab which I bought few years ago when it was first release (probably 2010). In the past, this device doing so well even after I root it 2 months after I purchase this device. But recently (starting 2014), it starting to hang or crashed a lot whenever i play a games. I mean high graphic games (if my term correct :laugh like Sims Freeplay etc which always make it crashed. I've never experience crashing thing if I play average games like cards etc. Apart from that, my battery drained way too fast for certain games. For your information, I'm a very hardcore gamer. Since I'm doing my work at home, most of time I spend it on games (probably like 16-18 hours or more per day while doing work or else). Because of this very reason, I've been thinking to upgrade it to latest android version so I can play latest games on Google Store. So I've been reading about custom ROM and decided to make it. My problem is my device is already rooted and I dont remember anything about it either which root tutorial I followed before or what apps that I used to root it. Only thing I remember is that Root Developer said that I need to use this same root apps to unroot my device. So now what can I do to get this custom ROM work? Do I need to unroot > stocked ROM > root again > custom ROM? Or I just straight doing this custom rom? And what is best stable custom ROM available for my device?
Here is my spec :-
Model : Galaxy Tab GT-P1000 (Phone/WiFi/3G)
Firmware : 2.3.3
Baseband : P1000DXJPE
Kernel : 2.6.35.7 [email protected]#2
Build : GINGERBREAD.DXJPI
Status : Rooted (I forgot how I root this)
Overclocking : Never did.
P/S : Sorry for my bad english.

So your device is rooted.
Does it has custom recovery or stock recovery.
To find out, power down your tab,
then hold the volume-up button, and hold down the power button, until you see the Samsung logo.
Let go of the power button, but keep holding the volume up button.
Then read what it says.
It it says Recovery 3(e) then you have a stock recovery.
If it is custom, likely CWM (clockworkmod) recovery.
What vesion of CWM.
If, by some chance, you didn't put a custom recovery, then just use Overcome method.
The link is in my signature.
You are already on GB. Root or not doesn't matter.
Installing custom ROM doesn't need root anyway.

priyana said:
So your device is rooted.
Does it has custom recovery or stock recovery.
To find out, power down your tab,
then hold the volume-up button, and hold down the power button, until you see the Samsung logo.
Let go of the power button, but keep holding the volume up button.
Then read what it says.
It it says Recovery 3(e) then you have a stock recovery.
If it is custom, likely CWM (clockworkmod) recovery.
What vesion of CWM.
If, by some chance, you didn't put a custom recovery, then just use Overcome method.
The link is in my signature.
You are already on GB. Root or not doesn't matter.
Installing custom ROM doesn't need root anyway.
Click to expand...
Click to collapse
Hello priyana,
I already made to overcome ROM before I saw your reply here. It is because I follow your signature from your answer on this tread http://forum.xda-developers.com/showthread.php?t=2038010 and now I currently have Overcome CWM 5.1.2.6 which work well at this moment. It also look awesome. Still thanks a lot for your reply. I have few question here..
1. Is there any Overcome ROM with android version of 4.+.+ or I should use Android 4.3 Jelly Bean CM10.1 Nightly ROM?
2. Can I have more than 1 ROM installed? Because I like Overcome style and still need android 4.+.+ for games.
3. With this Overcome I currently use now, is it still rooted or do I need to root it again? Because I need root access for some of apps like freedom, etc.
4. In case I click reset to factory data reset on setting. Is it reset back as first time I install Overcome ROM?

myst_pretender said:
Hello everyone.
I have a Samsung Galaxy Tab which I bought few years ago when it was first release (probably 2010). In the past, this device doing so well even after I root it 2 months after I purchase this device. But recently (starting 2014), it starting to hang or crashed a lot whenever i play a games. I mean high graphic games (if my term correct :laugh like Sims Freeplay etc which always make it crashed. I've never experience crashing thing if I play average games like cards etc. Apart from that, my battery drained way too fast for certain games. For your information, I'm a very hardcore gamer. Since I'm doing my work at home, most of time I spend it on games (probably like 16-18 hours or more per day while doing work or else). Because of this very reason, I've been thinking to upgrade it to latest android version so I can play latest games on Google Store. So I've been reading about custom ROM and decided to make it. My problem is my device is already rooted and I dont remember anything about it either which root tutorial I followed before or what apps that I used to root it. Only thing I remember is that Root Developer said that I need to use this same root apps to unroot my device. So now what can I do to get this custom ROM work? Do I need to unroot > stocked ROM > root again > custom ROM? Or I just straight doing this custom rom? And what is best stable custom ROM available for my device?
Here is my spec :-
Model : Galaxy Tab GT-P1000 (Phone/WiFi/3G)
Firmware : 2.3.3
Baseband : P1000DXJPE
Kernel : 2.6.35.7 [email protected]#2
Build : GINGERBREAD.DXJPI
Status : Rooted (I forgot how I root this)
Overclocking : Never did.
P/S : Sorry for my bad english.
Click to expand...
Click to collapse
First, I'd seriously consider jumping to One of the better.... Um focused CyanogenMod 11, or OmniROM Builds if I were you. There is plently to be gained by updating the OS. Google Now being IMHO one of the better reasons to upgrade.
Secondly, I get your "Problem" its One in which I to share in. I guess it comes down to how well the "Developer" of your "Game" wishes to optimize their Code for. Most Games tend to work... Well enough... Other Games like Gameloft's My Little Pony have never worked well on either my Galaxy S (GT-I9000), or my Galaxy Tab (GT-P1000). Unfortunately for us these Devices only has a total of 512MB of which a portion is needed to run the OS which may leave you with something like 488MB free once your said and done. I suspect that these "Games" are probably more RAM hungry, and probably need a somewhat stronger CPU & GPU then what is on the P1000.
myst_pretender said:
Hello priyana,
I already made to overcome ROM before I saw your reply here. It is because I follow your signature from your answer on this tread http://forum.xda-developers.com/showthread.php?t=2038010 and now I currently have Overcome CWM 5.1.2.6 which work well at this moment. It also look awesome. Still thanks a lot for your reply. I have few question here..
1. Is there any Overcome ROM with android version of 4.+.+ or I should use Android 4.3 Jelly Bean CM10.1 Nightly ROM?
2. Can I have more than 1 ROM installed? Because I like Overcome style and still need android 4.+.+ for games.
3. With this Overcome I currently use now, is it still rooted or do I need to root it again? Because I need root access for some of apps like freedom, etc.
4. In case I click reset to factory data reset on setting. Is it reset back as first time I install Overcome ROM?
Click to expand...
Click to collapse
1) Overcome is a modded Android 2.3.6 (Gingerbread), TeamOvercome has since left the Stage, as Samsung will no longer maintain this Device. As to CyanogenMod... For the P1000 Int'l GSM... I'd recommend you use the following....
CM10 http://goo.im/devs/cm/p1/nightly/cm-10-20130203-NIGHTLY-p1.zip You can basically forget about wanting to use CM10.1 or CM10.2, as they are both broken, and are themselves pretty much unsupported
CM11 I'm quite partial to this ROM [ROM] SGT7 CM11.0 UNOFFIAL [4.4.2][P1/L/N][Kernel 3.0.x][2014-05-25] as the everything that, needs to work works again. Unlike CM10's .1 & .2. Namely the Camera. Just One word of caution here though. Due to the limited /system Partition. You should only install GApps_Minimal_4.4.2_signed.zip if you want to use something like AdAway on your Rooted Phablet.
As a side note I'd also recommend you try OmniROM. Though its a bit different to CyanogenMod. In that its NOT rooted! which is a major PITA! but there are ways to get 'round that. Unlike CM11 this ROM is updated nearly every day. Unlike the aforementioned CM11 Build this One will allow you to install the full GApps. But in the case of AdAway... Which depends on root, may not work unless you put a specific *.zip File into some Folder that insures that you have root every time you update it.
2) I'm not sure I think I read something about OmniROM beta testing some kind of dual boot system. But I gather its not ready for prime time yet though.
3) Yes its Kernel OS related you can reset your Phablet as many times as you wish it'll still be rooted. AFAIK only the Samsung Stock... And OmniROM ROMs are NOT rooted by default.
4) A factory reset should wipe all personal data on your Phablet Device. It would be analogues to a fresh install of Windows.. If you catch my drift.

I am on Omni.
To root you only need to download supersu.
I download the one from their website and flash via recovery.
Within its option, there is one that makes it survive a daily update/flash.
Sent from my GT-N7100 using XDA Free mobile app

priyana said:
I am on Omni.
To root you only need to download supersu.
I download the one from their website and flash via recovery.
Within its option, there is one that makes it survive a daily update/flash.
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
Or you root in that way for the first time, then you download The latest SuperSu Version, and then copy that into your /OpenDelta/FlashAfterUpdate Folder on your Internal SD (i.e. sdcard0) which should allow you to hold your root after each update. Otherwise it'll quickly become huge PITA to keep rooting your Phone on each daily update...
One other thing I dislike about OmniROM, is the fact that it does NOT support USB Mass Storage. Though to be honest... Neither does Google anymore. It only give you the choice of MTP: Samsung Kies Mode, or PTP: Pictbridge? Mode support. Though I'm lead to believe that UMS can be patched back into OmniROM if it hasn't already gone live.

Ichijoe said:
First, I'd seriously consider jumping to One of the better.... Um focused CyanogenMod 11, or OmniROM Builds if I were you. There is plently to be gained by updating the OS. Google Now being IMHO one of the better reasons to upgrade.
Secondly, I get your "Problem" its One in which I to share in. I guess it comes down to how well the "Developer" of your "Game" wishes to optimize their Code for. Most Games tend to work... Well enough... Other Games like Gameloft's My Little Pony have never worked well on either my Galaxy S (GT-I9000), or my Galaxy Tab (GT-P1000). Unfortunately for us these Devices only has a total of 512MB of which a portion is needed to run the OS which may leave you with something like 488MB free once your said and done. I suspect that these "Games" are probably more RAM hungry, and probably need a somewhat stronger CPU & GPU then what is on the P1000.
Click to expand...
Click to collapse
Hello Ichijoe..
At this moment, I'm running CM11.2 on my GT-P1000. As developer of CM11.2 on thread said it is overclocked to 1.4GHz so it running good so far. And to cover my device lack of RAM, I use ROEHSOFT RAM Expander which I set my virtual RAM (if my term is correct) to 5GB. Yes, I know as developer said Virtual RAM is max for 4GB and I dont even need more than 2GB for running this, so I will change it later when I have time. So far, for this past 3 days, my GT-P1000 running with super duper smooth, not crashed even once unless I'm doing crazy thing like running 15 games at the same time. With my previous android Gingerbread 2.3.3, I'm never able to run more than 2 games without getting hanged or crashed. The only problem I'm facing now is I cannot use my videocam as it will send me popup "Unfortunately camera has stopped working". I can use normal camera, only videocam not working. Other user of CM11.2 also facing same problem. But I dont really mind since I less use videocam like 1-2 times per year. I wonder if I install 3rd party video software will allow me to use videocam. Never tried it yet.
priyana said:
I am on Omni.
To root you only need to download supersu.
I download the one from their website and flash via recovery.
Within its option, there is one that makes it survive a daily update/flash.
Sent from my GT-N7100 using XDA Free mobile app
Click to expand...
Click to collapse
Hello Priyana,
As I mentioned above, I finally made it working. Thanks to both of you Priyana and Ichijoe, I'm able to continue my relationship with my precious tablet:laugh:. To be honest, I'm almost going to throw this tablet out of my house since I'm getting pissed of it because of always crashed over small apps. Thanks again.

myst_pretender said:
At this moment, I'm running CM11.2 on my GT-P1000. As developer of CM11.2 on thread said it is overclocked to 1.4GHz so it running good so far. And to cover my device lack of RAM, I use ROEHSOFT RAM Expander which I set my virtual RAM (if my term is correct) to 5GB.
Click to expand...
Click to collapse
Hi bro,
can you post link to your working CM 11.2 build? Is it for p1000 (GSM version of SG Tab) right?
Thx

Need Help...!
priyana said:
So your device is rooted.
Does it has custom recovery or stock recovery.
To find out, power down your tab,
then hold the volume-up button, and hold down the power button, until you see the Samsung logo.
Let go of the power button, but keep holding the volume up button.
Then read what it says.
It it says Recovery 3(e) then you have a stock recovery.
If it is custom, likely CWM (clockworkmod) recovery.
What vesion of CWM.
If, by some chance, you didn't put a custom recovery, then just use Overcome method.
The link is in my signature.
You are already on GB. Root or not doesn't matter.
Installing custom ROM doesn't need root anyway.
Click to expand...
Click to collapse
Hi,
I have Samsung Galaxy Tab GT-P 1000, I have 2 question and need your help:
1-can I upgrade my tab with Overcome Rom 4.0.0 or 4.1.0, with the method that’s you explain???
2- Only French and Arabic keyboard, I will used after with my tab, Is it possible???
3- Thank’s a lot by replay.
Note: This’s my actually specification :
Model N°: Galaxy Tab GT-P1000 (Phone/WiFi/3G)
IMEI : 353942041480480
Imei SV : 01
Serial N° : R26B371419N
Firmware : 2.3.6
Baseband : P1000XXJPZ
Kernel : 2.6.35.7 [email protected]#2
Version N° : GINGERBREAD.XWJQ8
P.S: No sim card in it (I do not need). Used just with free Hotspot Wifi to be connected…

1) yes. The method is for P1000 specifically
2) pretty sure French is there. Arabic was mentioned many times in overcome original thread, so I think also there.
3) you are welcome
Sent from my GT-N7100 using XDA Free mobile app

Hello guys,
Im on my attempt to resurrect my P1000 and Im interested to what Ichijoe said about ''CyanogenMod 11, or OmniROM Builds" can anyone point me to the right thread on how to (Im pretty much noob about this)
Also which one is better? CyanogenMod 11 or 10?

[Q] VERY worried about flashing miui rom and new bootloader.

I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.

Jeffril said:
I have just recently restarted using this phone due to my uscellular S4 getting turned off. I am now back on my LG-P990 currently rooted and running CM10.1. BUT most importantly to me is the fact that I have all my wonderful apps on my s4, I want to be able to use them by using the LG phone as a tether and calls not much else BUT CM10.1 tethering does not work, so i find myself flashing rom after rom, avatar rom, older CM mods, none would turn on tethering, so i flashed a modded version of MIUI for this phone and it worked except for ONE thing no signal, tethering turned on just fine so i decided to look around for other roms and found Slimrom TRYED to flash it didnt work, try to flash actual MIUI roms off there site, didnt work, met with an error in CWM Recovery after some searching I found its because Im running the OLD Bootloader -_- THIS is the issue im having IF MIUI does NOT work is it possible to downgrade the bootloader again so i can restore my CM10.1 backup? I have been working at this for a week, if there is something here about this can someone please just point me at it? I would appreciate any help.
On a side note i DID soft brick the phone the other day and found a program called nvflash witch flashed an install of CM mod. Dont know if that will help any.
Click to expand...
Click to collapse
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.

NoDze said:
I really do not understand how other ROMs deny Tethering. Did you flash the latest 2.x kernel by pengus77 after installing the rom? Did you make a clean install(wipe everything then install)? On the other hand, yes you can switch bootloaders as much as you like, just remember that changing the bootloader wipes everything on your internal memory, so do a backup. Did you try just plain old stock 4.0.4? Should work there. Ask anything you want, if you're still having questions.
Click to expand...
Click to collapse
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?

Jeffril said:
As to the flashing to stock i lost the original rom backup i had made along time ago and cant find the original firmware anywhere online. When I flashed CM 10.1 I just ran with it, when i go to try tethering it says "Turning on portable wifi hotspot." and it stays on that no matter what untill i restart, left the phone running for 2 days once and that was still stuck on that before i restarted. As for flashing a 2.x kernel i had no idea about that. But yes when i did the installs i would do a clean wipe and install. Most of what i read online led me to believe that there was an error with CM 10.1 nightlys that was not being fixed for the tethering. So that is why i decided to go to another rom. Two questions one how do i go about finding the original firmware for this phone and two how would i go about updating or downgrading the bootloaders and could i be pointed to the files please?
Click to expand...
Click to collapse
Okay, This is SFSP by @sgspluss which is a pretty fast, stable and battery-friendly slimmed down version of stock ICS. It is available for both Old and NewBL, so you might want to try that first. This is AIO Toolkit. I know that you've used it and bricked your phone, but try again, and for the love of God install the nvflash drivers because most people skip that part. You have to do it manually and if you're running Windows 8 you need to disable Driver Signature Verification. But yeah, you switch bootloaders with this.