Database Info

[ROM BML GB 2.3.6] HebrewBarebone

What is it ?
Plain BML stock Gingerbread 2.3.6 AntonX Barebone ROM.
Deodexed, so can be applied with tweaks.
Fully added Hebrew translation (in addition to English), applied with Right-To-Left tweak (when needed).
Debloated : WiFi Calling, T-mobile my acount and my device, Talkback, ThinkDroid Office, Android Keyboard (put Samsung keyboard instead), Voice dialer.
Added : Audio DSP Manager, Memo, Sidekick KD1 modem, ICS boot animation.
Optional Odexer script attached.
Why ?
If you speak Hebrew and you want the latest stock firmware for SGH-T959V with full Hebrew support and UI, this is the ROM for you.
To get even faster results flash the odexer script right after the ROM and you'll get your ROM odexed.
It should be more stable, clean and reliable than HebrewValhalla.
Oh, and WiFi tethering, TV Out, soft keys - all work...
How to apply
Requires BML file system with GB bootloaders.
If you're on MTD file system (CM7/ICS/JB) or Froyo - use Heimdall One Click back to stock with Root and flash via CWM (followed by the odexer script).
Please note : if you booted to the deodexed ROM without flashing the odexer script later
and you want to odex the ROM now - wipe dalvik cache before applying the odexer.
Hebrew Instructions - http://iandroid.co.il/forum/post491182.html#p491182
Downloads
Hebrew BareBone ROM
Odex-Your-ROM
Credits:
AntonX - Barebone ROM.
eollie - One Click Heimdall package.
Ericwgarza1 - Odexer script.

Tried to flash your rom like this :
1. flashed stock kg4 via odin
2. rebooted
3. Flashed AntonX 1.1.3 kernel via odin
4. Rebooted while partition were converted
5. got into cwm and flashed your rom
Wifi does not work. Tried it AT LEAST 3 times.
Please advise,
Thanks
Update : also tried it with the KJ6 you posted on iandroid and the wifi still doesnt work
The wifi DOES WORK with stock rom
Update #2 : flashed antonx 1.1.3 barebone rom with the rtl patch i kept from while ago and the wifi works
BTW after flashing the Heimdall package - in it's CWM menu you cant delete dalvik cache (it like fast reboots/restes the CWM mwnu)

Just checking... have you tried flashing the rom again after wifi fails?

Hi
Yes, But not on top of the non wifi working rom, but of fresh stock rom installation

Reflash it on the non-wifi working. Sometimes the wifi module doesn't flash quite right the first time, and it takes another go. Since everything else basically sticks around, as long as you don't wipe between your non-wifi-working and the reflash, sometimes that makes it work... when that happens, it usually ends up being that your recovery turned off the system mount before it actually was done. Oops.

Hi Fish
I have been using this ROM for weeks. You are doing things wrong. Leave Odin aside.
Use Heimdall package posted in OP (verify everything works) and just flash the ROM (you can skip the Voodoo lagfix procedure, it's automatic).
It will all be to your satisfactory.
sent from me

itzik2sh said:
Hi Fish
I have been using this ROM for weeks. You are doing things wrong. Leave Odin aside.
Use Heimdall package posted in OP (verify everything works) and just flash the ROM (you can skip the Voodoo lagfix procedure, it's automatic).
It will all be to your satisfactory.
sent from me
Click to expand...
Click to collapse
Ok Itzik,
Although i did it, I will do it now once again and will let you know wazzup.
Update : After flashing heimdall - wifi does not work Will try to flash some other stock or find other rom as a base
Update 2 : I give up for now.I'll try to make the cm9.1 work since it's really frustrating to me and I can mess too much with the phone and miss sms and calls. maybe will try it late at night in one of the upcoming days.
Thank you

Hi Fish
OK, we know now that the ROM is not the problem. I'll tell you what you can do; try to remove the battery, press the power button for 10 seconds and then leave phone untouched for 15 minutes. Return the battery and get to download mode.
Now make a 2 steps Heimdall. The one by Lumin (stock unrooted) and the AntonX kernel Heimdall package. Verify that you have WiFi and flash this ROM (followed by the odexer). Good luck!
sent from me

Well....What i did is :
1. Flashed stock KG4 2.3.6 rom via odin
2. rebooted system
3. Flashed Antonx 1.1.3 Kernel via odin
4. Rebooted
5. Flashed via CWM one after the other : anotnx deodexed 1.13 rom AND 0.93 hebfix patch itzik2sh made a while ago which i kept
Now it's on antonx 1.1.3 rom + hebrew support and wifi WORKS

Hi Fish
You keep doing things not according to instructions and what you post here is not even this ROM.
This ROM is full UI Hebrew enabled, already includes RTL fix and I do not recommend using Odin any more.
You can now take a nandroid backup and flash this ROM (and odexer), otherwise I don't see the relevance of this post.
sent from me

itzik2sh said:
Hi Fish
You keep doing things not according to instructions and what you post here is not even this ROM.
This ROM is full UI Hebrew enabled, already includes RTL fix and I do not recommend using Odin any more.
You can now take a nandroid backup and flash this ROM (and odexer), otherwise I don't see the relevance of this post.
sent from me
Click to expand...
Click to collapse
I'm sorry if i strayed away from the subject, But the reason i'm posting what i did is because what was suggested didn't worked for me and I wanted people that experienced the same problem to know i found a solution.
Thank you for your help

fish72 said:
the reason i'm posting what i did is because what was suggested didn't worked for me and I wanted people that experienced the same problem to know i found a solution.
Thank you for your help
Click to expand...
Click to collapse
Hi Fish
You said the problems you had came on Heimdall flash, even before ROM flash itself.
fish72 said:
Update : After flashing heimdall - wifi does not work
Click to expand...
Click to collapse
Then, You say what "worked" for you is flashing another ROM after an Odin..
fish72 said:
Now it's on antonx 1.1.3 rom + hebrew support and wifi WORKS
Click to expand...
Click to collapse
So, I saw no relevance to that post, unless you now back up and flash this ROM (and optionally the odexer), as I already suggested and find a problem there.

[Q] aroma

Hi
Everyone is talking about this aroma something to wipe before flashing new roms
I googled it, but i found there are 2 aromas, installer and file manager
Which one is used to do the full wipe?
Do i need both software?
Thank you
Sent from my GT-N8000 using xda app-developers app

bombamanz said:
Hi
Everyone is talking about this aroma something to wipe before flashing new roms
I googled it, but i found there are 2 aromas, installer and file manager
Which one is used to do the full wipe?
Do i need both software?
Thank you
Sent from my GT-N8000 using xda app-developers app
Click to expand...
Click to collapse
Aroma is a dev tool allowing a graphical user interface for users installing custom roms. It is customized by a dev to allow users the ability to add/change/modify rom features and settings. For our device there are 3 roms installed through aroma though only 2 give us the option to perform a wipe android revolution hd by mike1986 and omega by indie when running the script from your recovery it launches aroma installer and both of the mentioned roms give you the option of wiping your device before continuing with setup. Be careful of which recovery you use, most users agree the newer cwm recoveries dont like aroma and freeze on some screens. Not a huge deal as this just requires a reboot which will bring you back to cwm. The original high on android from the android dev how to root guide by zedomax seems to work well and from personal experience i can tell you twrp works as well. Hope this helps

Specialp said:
Aroma is a dev tool allowing a graphical user interface for users installing custom roms. It is customized by a dev to allow users the ability to add/change/modify rom features and settings. For our device there are 3 roms installed through aroma though only 2 give us the option to perform a wipe android revolution hd by mike1986 and omega by indie when running the script from your recovery it launches aroma installer and both of the mentioned roms give you the option of wiping your device before continuing with setup. Be careful of which recovery you use, most users agree the newer cwm recoveries dont like aroma and freeze on some screens. Not a huge deal as this just requires a reboot which will bring you back to cwm. The original high on android from the android dev how to root guide by zedomax seems to work well and from personal experience i can tell you twrp works as well. Hope this helps
Click to expand...
Click to collapse
First off, I have the N8013, not sure what you have. I found your post because i couldn't figure out what this damn aroma thing everyone is talking about is. so thanks for your response on that.
But i have a question, what version on TWRP are/were you using? Did you just install it from goomanager or rommanager(clockwork) or did you have to flash from odin?
I'm not excited about using this high on android recovery, so when you said you used twrp i figured i would ask.

Best recovery is:
eggwardo said:
First off, I have the N8013, not sure what you have. I found your post because i couldn't figure out what this damn aroma thing everyone is talking about is. so thanks for your response on that.
But i have a question, what version on TWRP are/were you using? Did you just install it from goomanager or rommanager(clockwork) or did you have to flash from odin?
I'm not excited about using this high on android recovery, so when you said you used twrp i figured i would ask.
Click to expand...
Click to collapse
Some RECOVERY had problems with aroma instaler. I tried a lot of them CWM, TRW etc. but only one of them have no problem when I instaling something where was the aroma been. This Recovery is in my signature. Here : HighOnAndroid Recovery
Even KitKat custom ROMs I flashed without problem.
It's my opinion only, but I'm very satisfied with it! Peter

[Q] Changing Stock kernels

Hi,
I have managed to put on a kernel that's not working. Is there a way to revert back to the original kernel? I do have a nandroid backup, but re-installing that didn't put on the old kernel.
I am using Liquidsmooth ROM. Any help would be appreciated.
Thanks.

if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.

DvineLord said:
if you can boot into the rom use flashimagegui, if not do the normal fastboot the boot.img then do it again with flashimagegui to get the modules.
what kernel did you try to flash? the only kernel that will work with new liquidsmooth is cm10.1_vz-oc-linaro.3.zip. it contains modules, if you aren't s-off then you need to flash boot.img in fastboot then flash again in recovery for the modules.
Click to expand...
Click to collapse
I did exactly that, presuming that it was working... But I have been facing issues. The phone restarts every once in a while and I have managed to get to this condition after multiple wipes and restoring a backup. Anyways I don't know what the issue is I was just wondering how to revert back to the original kernel.

im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.

DvineLord said:
im running Liquid-JB-v2.1-RC2-evita.zip and cm10.1_vz-oc-linaro.3.zip. there seem to be some general issues with the rom that present as basically glitching and gets worse overtime atleast for me. im pretty sure it isnt related to the kernel. but to revert kernel just load the liquidsmooth zip into flashimagegui and itll pull the needed files, let it wipe cache and dalvik then reboot.
Click to expand...
Click to collapse
I do not have s-off does the flashimagegui works even without it?

strommer666 said:
I do not have s-off does the flashimagegui works even without it?
Click to expand...
Click to collapse
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.

DvineLord said:
yes, Flash Image GUI
you should also s-off your phone it will make life ALOT easier and the process is simple take like 2 minutes.
Click to expand...
Click to collapse
Thanks I'll make sure I do that..

also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.

DvineLord said:
also new stable build of liquidsmooth just got released. you should flash it. imma flash it with a clean full wipe. but you should s-off first so you dont have to flash boot.img separately every rom.
Click to expand...
Click to collapse
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.

strommer666 said:
Ya, I saw the new version wanted to try that which is why I wanted to got to the old kernel version. I had tried installing it with the linaro kernel but it gets stuck on the boot screen.
Update: - I installed the flash gui image, then extracted and installed the kernel , factory reset the phone, then installed the latest liquid smooth build. But it is still not going ahead of the boot animation.
Update 3 :- Got the old kernel back. Did a restore. Working fine now . But still for some reason I cannot install the new ROM yet.
Click to expand...
Click to collapse
you need everything. you don't need to extract the kernel. just load the whole zip file.

DvineLord said:
you need everything. you don't need to extract the kernel. just load the whole zip file.
Click to expand...
Click to collapse
I did load the full file and the flash gui image extracted the kernel. The thing is I have the kernel now, but still I can't seem to be able to install the new version of the LiquidSmooth build. I am doing a nandroid backup of this thing and try installing it again.

well new liquidsmooth is nice, im using cwm now as recovery since ive had tons of issues with twrp since version 2.2.2.0

HELP! Stuck in bootloop after using Pimp My ROM.

Using stock Gingerbread kernel (DDLF2 rooted with Clockwork Recovery Mod installed - Amit Bagaria's CF-ROOT).
I had changed the default boot animation to the green transparent droid using Pimp My ROM (version 3.4). After this, the phone went into a boot loop. My mistake - didn't take a backup using Nandroid before trying the tweaks. Tried the restore default boot animation from within Pimp My ROM itself. However it says no primary boot animation to restore!! Also tried to unpimp all changes from within the tweaker itself, still doesn't work and shows the boot animation that was set which made it go into the bootloop. One thing I do notice is that the reboot happens after all media scanning is over.
I still have CWM though.
I don't want to lose any data. Can anyone please help recover?
Thanks in advance. Any help would be much appreciated.

timbuctoo said:
Using stock Gingerbread kernel (DDLF2 rooted with Clockwork Recovery Mod installed - Amit Bagaria's CF-ROOT).
I had changed the default boot animation to the green transparent droid using Pimp My ROM (version 3.4). After this, the phone went into a boot loop. My mistake - didn't take a backup using Nandroid before trying the tweaks. Tried the restore default boot animation from within Pimp My ROM itself. However it says no primary boot animation to restore!! Also tried to unpimp all changes from within the tweaker itself, still doesn't work and shows the boot animation that was set which made it go into the bootloop. One thing I do notice is that the reboot happens after all media scanning is over.
I still have CWM though.
I don't want to lose any data. Can anyone please help recover?
Thanks in advance. Any help would be much appreciated.
Click to expand...
Click to collapse
I used pimp my rom once and I almost bricked my phone... I assume you are on custom rom now... just reflash that custrom zip through CWM.. clear cache and dalvik and reboot in this you wont loose any data.... BUT BUT BUT just be sure you FLASH THAT PARTICULAR CUSTOM ROM ZIP FILE ONLY WHICH YOU CURRENTLY HAD ON YOUR DEVICE... FLASHING OTHER ROM WITHOUT WIPING THE DATA WILL CAUSE PERMANENT HARD BRICK AND YOU HAVE TO SAY R.I.P TO YOUR PHONE THEN SO BE CAREFULL

If u did a backup of build.prop u can replace with aroma file manager, or u can download one of the build.prop with tweaks by topdroid and replace with aroma fm
Sent from my GT-I9003 using xda app-developers app

Flashed Dhiru's CM10 ROM
Thank you members for the replies.
I flashed a custom ROM (Dhiru's CM 10 (alpha 5) based off 4.1.2).
My installation of CWM saved my hind and made the transition not too difficult.
mustafahussain, bro, yes, many features in Pimp My ROM don't even work in the stock Gingerbread DDLF2 ROM. I guess that why's the developer still has it at alpha. I'm not going to risk using the damn thing again. I'll opt for a safer alternative.

Aroma Installer now working !

http://forum.xda-developers.com/showthread.php?t=2310019
This rom i ran it and the Aroma installer worked flawlessly. No issues.

Easton999GS said:
http://forum.xda-developers.com/showthread.php?t=2310019
This rom i ran it and the Aroma installer worked flawlessly. No issues.
Click to expand...
Click to collapse
So you ran this on an ATT i337? How did it handle the need for a loki patched kernel? Did you use OUDHS's auto-loki recovery or flash an ATT kernel after the install?
The reason I ask is that my experience with the Aroma installer, when it's done installing the kernel, your only option is to reboot. Meaning you aren't able to flash a loki kernel or loki patch prior to rebooting. I guess you could just reboot back into recovery and flash the proper kernel or patch. Would be nice if Aroma had an option to reboot recovery after the install though.

acruxksa said:
So you ran this on an ATT i337? How did it handle the need for a loki patched kernel? Did you use OUDHS's auto-loki recovery or flash an ATT kernel after the install?
The reason I ask is that my experience with the Aroma installer, when it's done installing the kernel, your only option is to reboot. Meaning you aren't able to flash a loki kernel or loki patch prior to rebooting. I guess you could just reboot back into recovery and flash the proper kernel or patch. Would be nice if Aroma had an option to reboot recovery after the install though.
Click to expand...
Click to collapse
This didnt make me reboot. and I use the auto loki recovery. Wifi on the kernel however didnt work so i went back and flashed Ktoonz kernel and all is working well. dont forget to change APN settings

Easton999GS said:
This didnt make me reboot. and I use the auto loki recovery. Wifi on the kernel however didnt work so i went back and flashed Ktoonz kernel and all is working well. dont forget to change APN settings
Click to expand...
Click to collapse
Thanks for the clarification, I'm not planning on changing roms any time soon, but for the benefit of others I just wanted to know how Aroma worked with our phones requiring loki. If it doesn't make you reboot, that means we could also just flash loki-doki after exiting the aroma installer, or flash an already lokied kernel. Both workable options. Good to know in case other roms move to the aroma installer down the road.

acruxksa said:
Thanks for the clarification, I'm not planning on changing roms any time soon, but for the benefit of others I just wanted to know how Aroma worked with our phones requiring loki. If it doesn't make you reboot, that means we could also just flash loki-doki after exiting the aroma installer, or flash an already lokied kernel. Both workable options. Good to know in case other roms move to the aroma installer down the road.
Click to expand...
Click to collapse
Perfect, thats exactly how we would do it, run the installer, do not let it reboot, and flash our kernel then reboot, I was wondering if that would have worked. And if I remember on the G3, it would ask the user what kernel to install, would it be able to at that point use our loki kernel within the installer?

TheAxman said:
Perfect, thats exactly how we would do it, run the installer, do not let it reboot, and flash our kernel then reboot, I was wondering if that would have worked. And if I remember on the G3, it would ask the user what kernel to install, would it be able to at that point use our loki kernel within the installer?
Click to expand...
Click to collapse
That's what I'm thinking, one rom for every version of the i9505 with the option to pick our kernel. Would really simplify installations for ATT and tighten up the i9505 group as a whole. Allowing developers to focus more on content rather than 3 or 4 versions of the rom with minor differences.

acruxksa said:
That's what I'm thinking, one rom for every version of the i9505 with the option to pick our kernel. Would really simplify installations for ATT and tighten up the i9505 group as a whole. Allowing developers to focus more on content rather than 3 or 4 versions of the rom with minor differences.
Click to expand...
Click to collapse
If it is like the G3 aroma, we will be able to select a kernel for within the installer...
getting this to work for G4 is the best news I've heard since the loki patch....YES!!!!

At the end of every aroma script there is a check box with the option to unchecked " reboot device now" if you unchecked that box then the aroma script ends and your back in recovery without rebooting... Then you can flash your loki_patch...
Click to expand...
Click to collapse
The reason I ask is that my experience with the Aroma installer, when it's done installing the kernel, your only option is to reboot. Meaning you aren't able to flash a loki kernel or loki patch prior to rebooting. I guess you could just reboot back into recovery and flash the proper kernel or patch. Would be nice if Aroma had an option to reboot recovery after the install though.
Click to expand...
Click to collapse
[/QUOTE]
[/QUOTE]
At the end of every aroma script there is a check box with the option to unchecked " reboot device now" if you unchecked that box then the aroma script ends and your back in recovery without rebooting... Then you can flash your loki_patch...

I swear this is the BEST NEWS I have had all day. Its good to hear something positive for a change.
THANKS THANKS THANKS!