Database Develop

[Q] ROM Manager / Clock Work Recovery

hi,
I have read a cyanogenmod wiki page about clockwork recovery / ROM manager, and naturally I am very confused.
* Where does this install? (SBL/is it called from somewhere like GRUB?)
* What does this modify?
* How does one access this? I presume via Recovery Mode - Does one tell it to boot from an update.zip file that contains a programme to run; What does this programme do, and what does it modify?
* If I install ROM Manager / Clockwork Recovery, then if I decide to return the SGS to Samsung for warranty reasons, and I have not installed any other ROMS (e.g it is running stock), then will Samsung notice anything if they look, other than the update.zip file on the SD card.
* Can the installation and booting ClockWork Recovery damage *anything* on the SGS? (I mean only running it, and not installing any ROM images etc.
Best regards, me.
* Installing ClockworkMod Recovery
If you flashed a previous version of ClockworkMod Recovery using Odin, Flash back to a Stock Kernel using this Odin package: will add soon
Search for ROM Manager in the Market (free or paid) and install the app.
Open the ROM Manager application and choose the first option in the app, Flash ClockworkMod Recovery.
Click on your device Samsung Galaxy S i9000 and then you may need to give the app root permission if it prompts you. If it does prompt for Superuser access, make sure Remember or Always is selected before you choose Allow.
If it hangs after that and freezes up, just allow the app to Force Close. Then open it back up and repeat steps 2 & 3.
Optional: Choose Backup Current ROM from the ROM Manager to create a backup.
On the very first boot of the ClockworkMod Recovery, you may need to manually select "reinstall packages" if the ClockworkMod Recovery does not start. You should only ever have to do this once. It will be automatic from then on.
If the flash was successful a dialog box should pop up saying "Successfully flashed ClockworkMod recovery!". Press OK.

[Q] Project Voodoo: how to perform "Apply update.zip"

Hi,
My Samsung Galaxy S is very slow. In search of a way to increase performance I found 'Project Voodoo' and its 'lag fix'.
I tried to install the lag fix on my Samsung Galaxy S, but until now I haven't succeed! There is not a lot of help on the project Voodoo site, is I hope I will find some help over here.
Info about my SGS:
- android 2.2
- small band version: I9000XXJPP
- kernel:2.6.32.9 (root at SE-S608 #1)
- build; FROYO.XWJPA
I tried to perform the following steps (from the project voodoo website):
Update.zip method (recommended; computer not required):
1. Copy the Voodoo package as /sdcard/update.zip at the root of your SD Card.
2. Reboot into recovery using the 3 button combo for your phone or “adb reboot recovery”
3. Apply update.zip
4. Enjoy !
This is what I did:
- downloaded the update.zip file (option "Voodoo lagfix for Froyo, stable .zip, update.zip, installable with ClockWorkMod recovery and Rom Manager", on the download page of the project voodoo site)
- renamed the file to 'update.zip' and placed in the directory "/mnt/sdcard" (step 1 completed)
- rebooted my SGS via 'Vol UP + Home + Power on' (assuming this is the right reboot option, but also tried it with 'volume down', same result) --> step 2
- the phone restarted...but then it just did nothing else than with a normal startup, so I'm not able to select an option to perform step 3. I also went on my phone to the update.zip file, but not able to 'apply' the file
(so also step 4, enjoy, wasn't possible)
Does anybody know what I did wrong?/how it's been done right?

the quickest way would be to flash the voodoo kernel thru odin. it will take 15 seconds and thats it

i might get same problem!!! After flash voodoo kernel by using odin, i can't get in default red cwm to configure it, all i get is normal recovery 2e...... anyone know to fix it?

azzledazzle said:
the quickest way would be to flash the voodoo kernel thru odin. it will take 15 seconds and thats it
Click to expand...
Click to collapse
Will try that later today...let you know if that worked out well!

azzledazzle said:
the quickest way would be to flash the voodoo kernel thru odin. it will take 15 seconds and thats it
Click to expand...
Click to collapse
Took a little longer to try. But until now I did some other stuff (like rooting e.g.).
Now I'm trying to install the Voodoo lagfix using Odin. There is now a 'user manual' on the Project Voodoo website. But I'm not sure which tar-file I have to use to flash for my Samsung Galaxy S.
As I said; I've got Froyo XXJPP. But the Voodoo project has only the following tar-files:
[ ] stock+Voodoo-Froyo-GT-I9000-XWJS3.tar 18-Jan-2011 13:08 5.7M
[ ] stock+Voodoo-Froyo-GT-I9000-XWJS5.tar 14-Feb-2011 13:24 5.7M
[ ] stock+Voodoo-Froyo-GT-I9000-XXJPM.tar 11-Jan-2011 22:45 5.7M
[ ] stock+Voodoo-Froyo-GT-I9000-XXJPO.tar 11-Jan-2011 22:45 5.7M
[ ] stock+Voodoo-Froyo-GT-I9000-XXJPU.tar 11-Jan-2011 22:45 5.7M
[ ] stock+Voodoo-Froyo-GT-I9000-XXJPX.tar 11-Jan-2011 22:45 5.7M
[ ] stock+Voodoo-Froyo-GT-I9000-XXJPY.tar 11-Jan-2011 22:45 5.7M
So I guess it is either the XXJPO or the XXJPU version. Which one do I need to use?? (XXJPP is between XXJPO and XXJPU)

Lets take a look of this wonderful Thread ^^
http://forum.xda-developers.com/showthread.php?t=968288

@borisfeltmann
I assume you're in Scandinavia/Finland/Iceland, your original setup is identical to how mine was.
AFAIK, there's still no 2.2.1 for JPA. Having tried a few custom ROMs, I'm now back to the stock 2.2, flashed with speedmod, and happy with it (for now, anyway... who knows what tomorrow may bring). I've no lag at all now. I'd like to upgrade to 2.2.1, but for various reasons I really need the Norwegian language support.
If all you're after is a lagfix and nothing else, speedmod via Odin is worth it.

It sounds like you might have 3button recovery disabled. Providing you were doing the key combos right. I'd do this before you mess around any further http://forum.xda-developers.com/showthread.php?t=785201
Make sure you follow the guide carefully.

[Q] INIT.D HACK installed?

I download the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
was the INIT.D HACK installed correctly?
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
I don't know what to do now.
thanks

you need to either toggle safe system off, or flash a ROM to use for safe system, and then flash the init.d hack
and my suggestion is to flash CM7 or Monster, Mav, SD3, Liberty, Etc. Im on CM7, works very nice http://hash-of-codes.blogspot.com

thanks MrJudylicious,
but sorry don't know how to do it...
this is my first android phone i just follow the steps that Chaoticweaponry told on the other topic:
"1: Root your Droid 3 using the 1 click root method (search around XDA/Google)
2: Download Safestrap from Hashcode's website. - USE BOOTSTRAP IF YOU'RE ON STOCK/NON-SAFESTRAP ROMS
3: Install the .apk file using AppInstaller from the Android Market.
4: Start Safestrap (or similar) and allow superuser permissions - then install recovery.
5: Get Download All Files from Android Market.
6: Download the init.d hack.
7: Turn your phone off.
8: Press m + power, scroll down to BP Tools (volume down key) and select it (volume up key)
9: Scroll down to install zip from SD card (select using power button)
10: Go to internal sd card - downloads folder.
11: Find the init.d file, and install it.
12: Reboot the device (go to main menu on safestrap (or similar) recovery)
13: Done."
I don't know what is flash a ROM...
so the init.d hack is not working?
as I said, I put system safe on and installed complete.. then it won't boot I don't know why..
so I put system safe off and it booted.
can you tell me what to do step by step please?
i'm thankful
Pedro
ps: I got one app called "droid3bootstrap" but idk if it will serve.

if you can, tell me what I need to download and what I should do...
sorry for the inconvenience
thanks

I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d

MrJudylicious said:
I, personally, would leave safestrap on and download http://goo.gl/xkZ0S which is CM7 11-16build. Put that on the sd card and boot into recovery, toggle safe system, format /system under mounts, install .zip for CM7, clear data/cache, and boot into cm7, then once youre done i would go back into recovery and flash the files for the init.d
Click to expand...
Click to collapse
Thanks a lot MrJudylicious,
but what is this 'CM7 11-16 build'? what will it do on the phone?

I just wanted to install INIT.D HACK because I read that saves battery.

cm7 is a stripped down very functional, very fast operating system. if you want stock, you can visit his hash-of-codes.blogspot.com and under android downloads you can download the stock 5.6.890 /root + superuser ( http://goo.gl/3bTpJ ). you cannot flash to teh main system with safestrap, but you can with bootstrap. you could have issues installing more than one *strap, which is why i suggested you keep safestrap.

it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?

pedroramos said:
it's so confused...
my system version is already 5.6.890...
android version 2.3.4
CM7 is a ROM.
this stock 5.6.890 is another ROM? the INIT.D HACK is a ROM too?
Click to expand...
Click to collapse
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.

ChaoticWeaponry said:
INIT.D is a edit of the system settings to inprove speed, battery, etc. Not a ROM.
5.6.890 is a system version - although most refer to it as a ROM (Motoblur)
CM7 is a custom ROM.
Click to expand...
Click to collapse
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil

pedroramos said:
Ok... so let me know if I'm starting to understand:
I tried to flash init.d using the safestrap but I had the problem booting in safe system mode and the config changes of init.d wasn't applied.
you told me to flash(using safestrap) the CM7 ROM or the 5.6.890 Motoblur "ROM" and then flash the init.d to have the config changes.
buuuut, I unnistalled the safestrap, installed the bootstrap, flashed the init.d and it booted normal...
now the init.d configs are properly working?
Thanks for your patience
I'm very newbie yet but beginning to understand thank you.
and sorry for my english, I am from Brazil
Click to expand...
Click to collapse
This is why this didn't work
You install safestrap, it allows you to install roms to your /preinstall directory (directory for windows users ^^). You don't install a rom but install the init.d files to /preinstall and then try to boot off /preinstall (because safestrap is enabled). Obviously that wont work because when your phone boots it looks for system files in /preinstall but all that's there is the init.d hack.
You uninstalled safestrap, installed koush' and then installed the init.d files to /system which your phone actually runs off. At that point the init.d is correctly installed.
Another option(the one that people are telling you here) is to install safestrap, enable safestrap, install your rom to the safestrapped system and then install your init.d hack on top of the rom you just installed which is also correct.
it's 2 different ways to do the same thing slightly differently(although with the second method you basically have 2 /systems). I hope this helps clear up your confusion.

I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.

pedroramos said:
I was confused about what is ROMS and for what it serves...
let me see if I understand...
my OS is the android 2.3.4 which version is 5.6.890
the init.d is like a .exe that changes some configs.
the CM7 is like a firmware.
can I make this analogy?
but two thing are dark yet:
to use safestrap I would have to flash a ROM(CM7, 5.6.890 'motoblur', or another one) before flash the init.d...
but in the case of choosing the 'motoblur' ROM, won't my system change anything for it be the same as my 5.6.890 version?
you said that based on what I did using bootstrap, my init.d is working properly? is there any way to see it?
my another doubt is:
when I flash a ROM or a config like the init.d, is there any way to undo this?
thanks men for the explanation.
I'm grateful.
Click to expand...
Click to collapse
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
You can test that this works on your roms by flashing and then checking for a ".ItWorks" file in /data partition. If you are using ES File Explorer or similar you will need to be sure to allow it to show hidden files, otherwise you won't see this file.
Click to expand...
Click to collapse
In his development thread. This might work for you.

Willis111 said:
Your OS (android/system software version) is all firmware. CM7 is another firmware. Firmware is just a fancy way of saying "ROM" in this case and it just creates confusion.
If you were to install the motoblur safestrap rom (or any other rom) with safestrap enabled your system wont change, it flashes it to a backup partition instead and you would be booting it off your backup partition, your main system will remain untouched regardless of what you do to the second rom(that's what safestrap is all about).
Init.d is a directory in *nix that holds a bunch of scripts that the user is able to run.
As far as checking if the init.d hack is working, I assume the hack your using is Overminds, he posted
In his development thread. This might work for you.
Click to expand...
Click to collapse
I opened root explorer and there was a ".itworks"(with a medal of sheriff) on /data partition
you said that safestrap won't change my system because it install the ROM in a different partition and the boot is made by there.
doesn't bootstrap happen the same? bootstrap overwrite the original system?
a case:
I used bootstrap and suppose that I want to unflash the init.d.. how can I do it?
thanks a lot

I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?

pedroramos said:
I entered in the bootstrap again to explore the functions...
I went to backup and it was doing a backup for minutes and I realized that I think I didn`t make the backup before flash the init.d... so i`m not able to restore my system before the init.d?
Click to expand...
Click to collapse
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.

calash said:
Well...It depends on what your current phone state is. Are you in Safe Mode or non-safe mode?
If I am reading this thread correctly I would guess you are in non-safe mode but flashed in safe-mode. This means the hack is likely not working (I don't believe you can use SafeStrap to flash in non-safe).
In that case you will not have a backup but you have not done much to the system outside of the installs so it should not matter.
Unfortunately you picked the more complex recovery to start your android adventures with, and your starting instructions were incomplete. I prefer SafeStrap myself but it is really not that useful if you are not going to be doing some heavy hacking or rom flashing.
Click to expand...
Click to collapse
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..

It works 4 me

pedroramos said:
calash, thanks for reply
I downloaded the safestrap on the hashcode's site:
Droid 3 :: v1.06 [ 2011-11-20 ]
md5sum: 72ac240d099ff2ab2a755ce8ff95060b
I had never used recovery neither enable safe system before.
so I installed the "Droid3Safestrap-1.0.apk" >> installed recovery >> boot the phone >> entered in recovery menu >> enable safe system >> install zip from SD card >> selected the INIT.D HACK file >> it was installed >> i puted to boot the phone and it freezed.
I turned of battery and turn it on, it pasted the recovery menu and then it didn't boot.
I turned of battery again and entered in recovery menu >> disable safe system and the it booted.
I read this:
"Use Bootstrap. Its probably not booting because you need to install a ROM after you enable safe system for the first time." from ChaoticWeaponry
so I unnistalled the safestrap and installed the bootstraped...
I put to do the boot by the bootstrap >> select the init.d file >> it installed >> boot the cell and it booted normal..
Click to expand...
Click to collapse
Ok, so right now it sounds like you are using the basic Clockwork Mod recovery, identified by the installed Droid 3 Bootstrap from the market/downloaded. In this case you do not have a backup from before the change you applied (Side note: Backups are also called nandroid backups. They are the same, just a different term).
If you wanted to remove the init.d hack it would be a bit more difficult at this point. Not impossible but you may end up losing all your data. It depends on if the changes the init.d hack made are well documented or not. It is a fairly safe hack so I would not worry too much about it at this point.
For your reference the bootstrap you installed, also called Clockwork Mod, and SafeStrap do nearly the same thing, providing you with the menu at the very beginning when you power on the device and allows you to flash (what you did to install the init.d have), backup, and some other neat features.
The big difference is that SafeStrap allows you to have two operating systems, also called Roms, on the phone. These are identified as Safe and non-Safe. non-safe is whatever OS (or Rom, the terms mean the same on our phones) you start with while the Safe is a new install that you do in the same way as you flashed the init.d have.
As you work with it more you will get the hang of the various terms and software packages. For now you should be in good shape, even without a stock backup. We have ways to get back to a pure stock image if that needs comes up, just check the threads in the development forum for more information.

Samsung Galaxy Exhibit 4G

T-Mobile/Samsung have rebranded the Exhibit II 4G, giving us a new kernel, a bump to Android v2.3.6 and performance improvements (they claim) in the process. The phone we all love is now the Samsung Galaxy Exhibit 4G.
This stock ROM (UVLG3) is NOT vulnerable to USSD Dialer Attacks!
Rooting
Currently, zergrush will not root this phone's Android 2.3.6. Three known methods:
Root Stock 2.3.6 w/o a new kernel or ROM
root-stock.zip
Mirror
This zip will install Superuser, su and busybox, leaving you rooted, but otherwise no changes to your phone. ClockworkMod must be installed to flash this. So:
1. Flash ClockworkMod
2. Boot into ClockworkMod and flash root-stock.zip.
Rooted Community ROM (forkable)
t679.uvlg3.odex.01.zip
Mirror
(also see custom ROMs)
Linked above is Samsung's newest release for the Galaxy Exhibit, a stock rooted UVLG3 Gingerbread ROM. Busybox is also included. You must flash it via clockworkmod. Clockworkmod can be flashed with Samsung's stock recovery.
Custom rooted kernel
t679-root-v1.8.zip
Mirror
Kernel sources
The kernel is based on Samsung's kernel source. This kernel is rooted; if you flash it via stock recovery or cwm your ROM will be rooted with Superuser.apk, Busybox and the Galaxy Exhibit cwm-recovery installed. This kernel works with all Samsung Gingerbread releases.
Rooted ROM Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. The installation will format your data partition. I suggest Titanium Backup, available in the Market.
2. Download & copy the current t679.uv???.deodex.0x.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
3. Install Galaxy Exhibit Custom Recovery . If you're already rooted, you may install from the command line, otherwise you may install from Samsung's Recovery. Samsung's recovery only sees the internal SD, so copy the cwm zip there if you just have stock recovery. Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Select ROMwipe. This step is required!
6. Highlight install zip from sdcard, then press Home.
7. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
8. Highlight the rooted rom zip file, then press Home.
After you confirm your choice, installation should take less than three minutes.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied. Your first post-installation boot may be several minutes long.
Rooted Kernel Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. I suggest Titanium Backup, available in the Market.
2. Download & copy t679-root-v1.8.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
It's recommended to install Clockwork Mod, but you can also flash the kernel from Samsung's stock recovery. Samsung's recovery only sees the internal sd, so copy files there if you don't have cwm.
Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Highlight install zip from sdcard, then press Home.
6. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
7. Highlight the kernel zip file, then press Home.
After you confirm your choice, installation should take less than a minute.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied.
Please DO NOT PM me with support questions! They will be ignored! Post them in this thread!

Links and useful info
Galaxy Exhibit XDA Wiki
Galaxy Exhibit IRC channel
Galaxy Exhibit Themes
Custom ROMs
All ROMs listed require cwm for installation.
Peach Sunrise
RebelROM
XquiziT
CyanogenMod 9 Beta
Galaxy ExHibition
CM10 Port
AOKP (WIP)
CM7 (WIP)
CM9 Pure Nexus
Stalled, partially working
AOKP
KEMIUI
Help! I keep getting FCs!
Custom kernel for Rebel Rom
This is custom kernel 1.8 packaged specifically for RebelRom, tested on
version 3.0.8. This package includes kernel & modules only.
rrkernel.zip
Mirror 2
Stock 2.3.6 via Odin
uvlg3.odin.zip
Mirror
Adb for Windows
winadb.zip unzip and copy to your c:\Windows directory
Mirror
Flash2Stock
Flash2Stock (flash via cwm) will install stock UVLG3 and Samsung's stock recovery, un-rooting
your phone, removing ClockworkMod and returning your phone to factory condition.
uvlg3.flash2stock.zip
Mirror
SwapSD
SwapSD This simple app allows you to swap internal "usb storage" (aka /sdcard) and your removable sdcard (aka external_sd) so your larger "external sd" is mounted as "/mnt/sdcard/" and the smaller sd internal memory is mounted as "/mnt/sdcard/external_sd". This is done by changing a file called vold.fstab in your phone's /etc folder. The original device vold.fstab file is backed up to /etc/vold.fstab.backup when this app first runs. Your data on /mnt/sdcard and /mnt/sdcard/external_sd is not touched in any way whatsoever.
Dropbear (flash via cwm)
is a software package that provides a Secure Shell-compatible (ssh) server and client. It is designed as a replacement for standard OpenSSH for environments with low memory and processor resources, such as embedded systems. This archive also includes the scp and rsync utilities.
dropbear.zip
Mirror
Bloatware
These apps are safe to delete. You may also freeze them using Titanium backup.
AnalogClock.apk
Browser.apk (Only if you use an alternative browser)
Dlna.apk
DownloadProviderUI.apk
DualClock.apk
DualClock.apk
IQ-tmobile-release-signed-zipaligned-v1.1....
JobManager.apk
KiesAir.apk
MobileBackup-unsigned_v3.3.02.apk
MyFiles.apk(Only if you have an alternative File Browser i.e. Astro File Manager)
SamsungWidget_Program...
Swype.apk
TetheringManager2.apk(Only if you don't use T-Mo's tethering service)
TouchWizCalendar.apk
TouchWizCalculator.apk
TwCalendarAppWidget.apk
VideoPlayer.apk(Only if you have an alternative video player)
VoiceRecorder.apk
WiFi-Calling.apk(If you don't use it)
ZinioSettingsProvider.v2.03.3331.TMobile....
sihome-signed-tmo-android-8.apk
talkback.apk
tmobile_m4m_3_0_15.signed...
vvm-signed.apk
Partition Table
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20 all 0's
/dev/block/mmcblk0p21 all 0's
/dev/block/mmcblk0p22 all 0's
/dev/block/mmcblk0p23 all 0's
/dev/block/mmcblk0p24 all 0's
/dev/block/mmcblk0p25 all 0's
/dev/block/mmcblk0p26 all 0's
/dev/block/mmcblk0p27 efs (encrypted fs)
/dev/block/mmcblk0p28 /mnt/sdcard
Credits:VanillaTbone,s0unds,KemikalElite, jocala, Wildchild, bpear96, camcory, Intercepter and others. If your name belongs here or you have info that needs to be added please speak up!

Zergrush
Rooting the original Exhibit II via zergrush: Please read DooMLoRD's Easy Rooting Thread
Please note that this method does not work with Android 2.3.6 on the Galaxy Exhibit.

ClockworkMod
Galaxy Exhibit cwm-based recovery v6.0.1.2
6.0.1.2 has new features, including better support for both external and internal SD cards, faster backups and restores with a new backup format that de-duplicates data in between backups. Exclusive features for Galaxy Exhibit include:
wipe menu with rom wipe
All system wipes under one menu: rom (system/cache/data),cache,dalvik,cache/dalvik,data.
Stack zip files for installation:
Flash cm9 & gapps, etc. Select as many zip files for installation as you choose. Flash them all with one command.
Install system images:
Drop any recognized system image into a folder on your phone and recovery can flash it. You can even drop the entire contents of an odin tar/md5 file in a folder and cwm recovery will flash it all automatically.
All images must conform to Odin naming standards:
adsp.mbn
amss.mbn
boot.img
cache.img.ext4
preload.img.ext4
recovery.img
system.img.ext4
Click to expand...
Click to collapse
This is regular interface, not touch.
cwm.6012.t679.zip
Mirror
To initially install Galaxy Exhibit Custom Recovery you need to:
1. Copy cwm.galaxy.exhibit.zip to your internal SD storage.
2. Boot into stock recovery:
Starting recovery: Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons.
Or a different method some find easier:
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Recovery should start after the Galaxy Exhibit/T-Mobile logo.
3. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm.galaxy.exhibit.zip file.
If you already have cwm installed, to update follow the steps above, booting into your current cwm instead of stock recovery.
Should you need to install ClockworkMod via Odin:
cwm.6012.tar
Mirror

We have needed a new thread for our phone, thanks for making this!

kingdavidd said:
We have needed a new thread for our phone, thanks for making this!
Click to expand...
Click to collapse
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links and information.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any general discussion of our Galaxy Exhibits (concerning development as well). I also hope folks will evangelize and point people here rather than carry on in the older abandoned OP threads.

Nice job jocala! Thanks.
Sent from my Calculator with Android.

So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct? Much rather flash that then go back to stock then update. Thank you for that.
Sent from my SGH-T679 using xda premium

jocala said:
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any discussion of our Galaxy Exhibits.
Click to expand...
Click to collapse
Yea all the old threads OP's abandoned them and the original post had all old info, I am glad you're dedicated to this phone!

SurgeRush said:
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct?
Click to expand...
Click to collapse
Yep, that's it. Purely stock except for root, busybox & recovery.

Cant wait to see what roms come out of this
Sent from my SGH-T679 using XDA

The rebranding works out nicely, if for no other reason than providing a point of demarcation.
Many props to Jocala who is awesome, as we all know. It can't be said too often but we'll try not to overdo it. :thumbup:
Sent via frazzled carrier pigeon -->

Ditto here man. We'd all be screwed & tattooed without his know-how. BTW worth mentioning I had to refreeze all the bloatware again after the update. Noticed how the phone lagged and then checked Titanium Backup. Sure enough all the crap was back. Also re-check settings in programs like Juice Defender and Rom Toolbox. I had to re-enter some of them again as well.

Has anyone managed to update successfully while already being rooted? (Specifically by Zerg Rush method)
I've yet to received the OTA notification and still holding off If i should update using the software. Stock ROM but just rooted. Holding off on "flashing" anything as I've never done it before.

ArtfulDodger said:
Ditto here man. We'd all be screwed & tattooed without his know-how.
Click to expand...
Click to collapse
That's not true at all, but thanks for saying it. Anyone handy with *nix can do what I do, and 95% (or more) of the techniques I use were pioneered by others here on xda.

Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder(not in stock) T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though. It also looks like you might have taken a different approach to rooting the rom, maybe you could look at mine see if its just complete fail or not lol and or maybe pming me, to avoid clutter, on how you did urs.
ive made sooo many edits lol but just wanted to add too, thanx for all the work you have done for us.

cars1189 said:
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though.
Click to expand...
Click to collapse
The phones I use have always come odexed. I know of no other root methods. I don't have time to beta your rom, but feel free to post a link. I'm sure you'll have volunteers

cool, and no problem, and basically all i did was use the dsixd kitchen and added root(from in the kitchen menu), does that not really root it? does that just change the file permissions? cause when i did that it added the su binary so i assumed it did, but doesn't look like thats what you did, urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.

cars1189 said:
urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
Click to expand...
Click to collapse
You are correct

Flashed the ROM, all went smooth, but I can't install anything from the Market. Every time I try I get "ERROR "Blah" Could not be downloaded due to an error." Any ideas? Did a full romwipe and dalvik before flashing. The markets not even updating to Play store either.

TWRP WITH WORKING touch screen

Update for new year.
1-1-2020 Uploaded a version of twrp for Bold-N1 with working touchscreen.
thanks to the help of @vineethrp in This Post
Original thread hidden, since twrp build is fixed.
This initial version of TWRP, still has major issue. A second issue with the recovery is the screen will not turn on for about 30 seconds after boot. A time that lines up with the screen sleep timer. The touchscreen is not working. This has been a kernel issue on other devices that I am aware of.
The kernel source for th BOLD-N1 is released, and I have been reading through it. To no avail. I can't find the section that is checking for recovery mode.
For the time being, I have confirmed this version is working with the adb command line operations.
Partial list of functions found Here https://twrp.me/faq/openrecoveryscript.html
I have used the "install" and "sideload" operations.
In most cases (mods etc) sideload should be ok to try.
For the mod I was interested in (DM-Verity-No-Forceencrypt). The install does not support being done in sideload.
Because in the install script used, it checks the zip file name. Based on the file name it enables/disables options of the script.
Sideload changes the *.zip name, so more steps were necessary.
In the following steps, the device /data partition will be formatted. This will erase all your stored data, and more importantly,
it will remove the encryption.
The following steps require you to have already unlocked bootloader.
And,
As a reminder, whenever you modify your phone, you should NEVER relock the bootloader
INSTALL the attached TWRP img. Use Fastboot to install it.
Code:
fastboot flash recovery **insert-file-path-&name-here**
fastboot oem reboot-recovery
STEPS USED TO FLASH Disable_Dm-Verity_ForceEncrypt
Download zip file from developers XDA page HERE
Code:
adb shell twrp wipe data
adb shell reboot recovery
adb push Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip /sdcard/Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip
adb shell twrp install /sdcard/Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip
STEPS USED TO SIDELOAD MAGISK
Download from Developers GitHub repo HERE
I had trouble with the newest V20. Stay on tested version V19.2, unless you can troubleshoot problems on your own.
Code:
adb shell twrp sideload
adb sideload C:\Users\(your user name HERE)\Downloads\Magisk-v19.2.zip
Device tree used
https://github.com/mrmazakblu/Bold-N1_minimum_device
Kernel source
https://github.com/mrmazakblu/Bold-N1-Kernel.git
Released twrp folder on android file host HERE
Stock recovery image HERE
.

Call for help
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.

mrmazak said:
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.
Click to expand...
Click to collapse
No luck with decrypting here
Tried to backup stock recovery with no luck. Do u have a copy ?

greeneyez15o said:
No luck with decrypting here
Tried to backup stock recovery with no luck. Do u have a copy ?
Click to expand...
Click to collapse
How did you try to backup stock recovery?
Yes do have stock images loaded on filehost as well. I will add a link in the OP.
Let's try and figure out why you had trouble decrypt.
Start by flashing that twtp image to recovery. Boot I to the twrp then follow the steps I listed

mrmazak said:
How did you try to backup stock recovery?
Yes do have stock images loaded on filehost as well. I will add a link in the OP.
Let's try and figure out why you had trouble decrypt.
Start by flashing that twtp image to recovery. Boot I to the twrp then follow the steps I listed
Click to expand...
Click to collapse
Not sure, but now Im bootlooping to twrp :/

greeneyez15o said:
Not sure, but now Im bootlooping to twrp :/
Click to expand...
Click to collapse
do you know if your phone had received the ota update. there was an update made on
Wednesday, 16-Oct-19 03:27:28 UTC not sure when it was released, though.
it is possible, but unconfirmed that this update may have made this bootloop happen. because others have said that the update made them loose there root. Unknown about the unlock status

I am still trying to fix this twrp, as it is still only one I have seen.
I also have a different phone(umidigi F1) with same soc, mt6771.
A Dev made twrp for that device that even works decrypt. @PeterCxy.
I have forked his build tree. And am trying to copy his success. Unfortunately even though devices have same soc, the encryption method is different enough that the files used to make decrypt work on F1 are not present on N1.
A made a full firmware dump of the N1 at
https://github.com/mrmazakblu/blu_n0030ww_dump

working on porting , then building old Carliv touch recovery. since it can be used with the volume rocker as well as touch.
So far i have it ooting and adb works. Of course with device encrypted , the internal storage is not accessed. but once i get the fsab and vold correctly mapped, it will be ok.
am not posting the port till sdcard is fixed, and can be built from source.

sounds great man i just oem unlocked the bold n1 how do i go far as rooting wise without the custom recovery. using magisk or do i gotta wait until the carliv recovery is available

dxpeboiiii said:
sounds great man i just oem unlocked the bold n1 how do i go far as rooting wise without the custom recovery. using magisk or do i gotta wait until the carliv recovery is available
Click to expand...
Click to collapse
Well it's up to you. In this thread I have detailed how I used ADB with twrp to flash first decrypt install package, then magisk. Or you can patch boot.img with magisk manager then flash back to phone with fastboot or sp-flash tool.
Or if you are going to use gsi AOSP, you don't need any of these options.

Any word on the touch twrp. Im rooted with magisk but need viper4android and cant seem to flash properly without twrp... I tryed all kinds of ways

dxpeboiiii said:
Any word on the touch twrp. Im rooted with magisk but need viper4android and cant seem to flash properly without twrp... I tryed all kinds of ways
Click to expand...
Click to collapse
Did you try either of the 2 ways I explained how to use adb to install zips?
1- adb sideload
2- adb twrp install. Xzxsome-zip-name
But I thought viper4android has not worked on devices higher than marshmallow

I gotten it to work on my galaxy tab a on Oreo and my galaxy s7 and different varieties of devices. And yes i tryed the command from abd in twrp to install zip.. no success yet. BUT i have a otg from a samsung devices. And am able to use twrp within the mouse and keyboard. So tryna see what my options are as far as installin zips

dxpeboiiii said:
I gotten it to work on my galaxy tab a on Oreo and my galaxy s7 and different varieties of devices. And yes i tryed the command from abd in twrp to install zip.. no success yet. BUT i have a otg from a samsung devices. And am able to use twrp within the mouse and keyboard. So tryna see what my options are as far as installin zips
Click to expand...
Click to collapse
That's good, lets us know how the otg mouse works out. I did not have one to try it.

I got viper4android workin .. i downloaded a module called "Magisk SELInux permissive Script" this basically gave me the option to be permissive thats need for viper to work. And busybox but im pretty sure thats already installed from magisk but if not just install busybox. Should be good to go for audio mods?? bout to try dolby now.. let you kno how it goes

Basically i have the device unencrypted and under magisk settings you wanna uncheck "magisk hide" you will fail safety thing but me personally idc. But anyway follow the above comment along with wat i just said you should have no issues installin viper and dolby. I also recommend a otg for custom recovery. Just easier in my opinion. I basically got device setup how i want and backed it up thru twrp. But any question feel free to ask. More then welcome to help anybody .

deleted.

dml0211 said:
deleted.
Click to expand...
Click to collapse
I think you posted in wrong stop. I see you deleted before I got reply. Oh well.
But if you need to know which type of gsi to use on your device. The best bet is to use this app, from play store.
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck

mrmazak said:
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.
Click to expand...
Click to collapse
I got to fix the touch issue. After a bit of debugging I figured out that kernel is not able to find the firmware file for goodix:
Code:
[ 0.935177] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 0.935177] (5)[1:swapper/0]BOOTPROF: 935.177078:probe: probe=i2c_device_probe drv=goodix_i2c(ffffff80097f7b08) 77.446154ms
[ 0.935191] (5)[1:swapper/0]i2c i2c-0: Failed to register i2c client cap_touch at 0x5d (-16)
[ 0.935191] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 0.935204] (5)[1:swapper/0]i2c i2c-0: of_i2c: Failure registering /[email protected]/[email protected]
...
...
[ 2.422885] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 2.422892] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 2.423524] (4)[321:ueventd]ueventd: firmware: loading 'goodix_cfg_group.bin' for '/devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin'
[ 2.423633] (4)[321:ueventd]ueventd: firmware: could not find firmware for goodix_cfg_group.bin
[ 2.423664] (4)[321:ueventd]ueventd: loading /devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin took 0ms
[ 2.423695] (7)[222:goodix-parse_cf][GTP-ERR][goodix_read_cfg_bin:493] Cfg_bin image [goodix_cfg_group.bin] not available,error:-11, try_times:2
I digged in deeper an figured out that the firmware files are in /vendor/firmware folder and and I extracted it out and put it in
Code:
recovery/root/etc/firmware
and touch works as a result.
Code:
adb pull /vendor/firmware/goodix_cfg_group.bin
BTW, I have not yet figured out the reason for delayed screen on. I am debugging that and will let you know if I get some leads. I am also not able to get the decrypt working as of now.
Please let me know if you need any more details about how to get the touch working.

vineethrp said:
I got to fix the touch issue. After a bit of debugging I figured out that kernel is not able to find the firmware file for goodix:
Code:
[ 0.935177] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 0.935177] (5)[1:swapper/0]BOOTPROF: 935.177078:probe: probe=i2c_device_probe drv=goodix_i2c(ffffff80097f7b08) 77.446154ms
[ 0.935191] (5)[1:swapper/0]i2c i2c-0: Failed to register i2c client cap_touch at 0x5d (-16)
[ 0.935191] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 0.935204] (5)[1:swapper/0]i2c i2c-0: of_i2c: Failure registering /[email protected]/[email protected]
...
...
[ 2.422885] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 2.422892] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 2.423524] (4)[321:ueventd]ueventd: firmware: loading 'goodix_cfg_group.bin' for '/devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin'
[ 2.423633] (4)[321:ueventd]ueventd: firmware: could not find firmware for goodix_cfg_group.bin
[ 2.423664] (4)[321:ueventd]ueventd: loading /devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin took 0ms
[ 2.423695] (7)[222:goodix-parse_cf][GTP-ERR][goodix_read_cfg_bin:493] Cfg_bin image [goodix_cfg_group.bin] not available,error:-11, try_times:2
I digged in deeper an figured out that the firmware files are in /vendor/firmware folder and and I extracted it out and put it in
Code:
recovery/root/etc/firmware
and touch works as a result.
Code:
adb pull /vendor/firmware/goodix_cfg_group.bin
BTW, I have not yet figured out the reason for delayed screen on. I am debugging that and will let you know if I get some leads. I am also not able to get the decrypt working as of now.
Please let me know if you need any more details about how to get the touch working.
Click to expand...
Click to collapse
Thank you. I added the firmware to the recovery ramdisk and repacked. Just like you said. Now I have touch working. THis may have re-sparked my interest. I have more to work with now. Thanks.
Perhaps twrp is not properly mounting the /vendor and this is why we need to add that bin file to recovery/root. May also be same issue making the screen on time lag. Either way this seems like a big step forward.
I am working on adding the goodix firmware to the device tree I am building with, so will not need to do repacking. I have added the test build with working touch to the file host folder linked in OP