Database Develop

[STARTER] Upgrade Kit 3.7.5 | Apps 2 | Root, Flash, Unbrick, Tuts...

| Upgrade Kit (UPK) |
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Description :
This is a package which contains all needed things to root, install ClockWorkMod Recovery and upgrade/flash following described methods.
Includes :
ADB + basic cmds (reboot, logcat, reboot-recovery)
BlackJack (root utility, Froyo)
Bootloader Unlocker (Stock ICS firmwares) | It uses the u-boot.img by payback from 4pda.ru (Thanks jockjoint)
CWMT (ClockWorkMod Recovery Touch 5.8.1.3 flasher)
CWMT6 (ClockWorkMod Touch 6.0.1.4 flasher - USB broken)
Drivers (USB, Modem, Bluetooth)
FW Converter 2.1 by jes0411
KDZ Updater
LGMobile Update (B2C)
MSXML 6 SP1
PDF guides
R&D Test Tool (unbricking tool / hard reset)
README - About HTML file
TWRP 2.6.1.0 (TeamWin Recovery Project 2.4 flasher)
UnlockRoot 3 (ICS Root tool)
Windows Enabler (X64 / R&DTT)
Some packages are also available separately to avoid repetitive downloads. ▼ Direct Download
| Apps |
Description :
An setup package which lets you the choice between useful apps. There are predefined install types but you can also customize the installation. USB debugging must be enabled on your device. Read package's intro for more details.
Currently 75 apps. See the full list.
Screenshots :
​
ANTIVIRUSES MAY DETECT EXPLOITS
Some Extra files : V10E Patched (EU), V20S Patched (EU) | V30B (FRA) | Superuser+.zip (will push AnReboot + ES Explorer as well) | SuperOneClic 2.3.3 | Gingersnap 2 | ADB.zip | FW Converter | GPS_Fix_2.zip | and more...
Note : V10E & V20S here are the OPEN EUROPE versions in binary format, and are patched with CWMT so they're ready for root (flash superuser.zip from SDC via recovery, see below the root tut)
| Firmwares |​
Now I let this task to more competent than me
Check the flux list by luivit
WARNING : keep files's original name/case or you'll get errors while flashing.
Syntax = V10A_00.kdz | characters in red will never move. Characters in skyblue are according to versions.
AFRATL = language/brand code | VXXX = firmware version | (...) = Provider/Country
| The upgrade |​
You assume the fact that flashing may result in getting errors, and even bricking the phone.
You can use standard methods by using B2C, R&D Test Tool (to use with .kdz firmwares), or simply PC Suite. If you're going to manually downgrade with R&DTT, doing a factory reset before flashing may prevent of errors and bricks.
NOTE : Now LG blocks manual upgrades via B2C ("upgrade start" will show LG update window instead of performing the flash process), so neither KDZU nor R&DTT will work unless you apply the following tip to fix it.
But the fastest and safest method is to use the SmartFlash tool (also used for rooting). For this method you'll need a firmware in binary format which is in two separated files (*.fls & *.bin). You can downgrade as well if needed. The process takes only 3 min and erase all internal datas. So you'd better save all saveable things like contacts, apps etc... use your favorite way (full nand, titanium, listing...)
Requirements : any firmware, UPK, and USB drivers. Follow related PDF guides for manually flashing.
If for some reasons, you need a particular firmware, you could convert it in binaries yourself by using the FW Converter. Just put it in the same dir where the firmware is and run it. This tool is also able to patch FWs OTA with CWM
Note : don't apply the patch on ICS firmwares (V3XX) since it will break the boot. Refer to "Recovery for ICS" of this tutorial below
Reference thread by jes0411
| The root |​
Device's warranty won't be avoided ! Read this !
Method 1 - FW V10A / B
Download the latest GingerBreak
Allowed non Market Place apps (settings > apps > unknown sources)
USB debugging ON (settings > apps > dev > USB debugging)
A SDC must be present and mounted
Launch Polaris Office to explore your SDC, then touch the apk file
in the case you don't have a file explorer, install ES File Explorer or Solid Explorer (Apps)
Phone will reboot on sucess. Cool, it's rooted ! (now you can uninstall GingerBreak)
Loading can take several minutes. If after 10 minutes at most nothing happens, GingerBreak doesn't work for you....
Method 2 - Froyo (V1XX)
Required : installed USB drivers
Enable USB Debugging (settings > apps > development)
Plug the phone, launch BlackJack and follow instructions
Allow 127.0.0.1 connection if prompted by AVs / Firewalls. Read BlackJack's intro for more details.
Froyo alternative root method with Smartflash :
Follow steps as described in method 3 below, but with these patched binaries V10E (EU) instead
Method 3 - Gingerbread (V2XX)
Caution, this method is a full flash ! EVERYTHING on the internal memoy will be lost !
Required : installed USB drivers, Smartflash, patched FW binaries V20S (EU) (*.fls and *.bin) and the Superuser+(ESE) archieve
Copy Superuser+.zip in your SDC
Follow the PDF guide procedure (UPK)
Phone will reboot into Recovery, do a wipe / reset
Now select "install zip from sdcard" > "choose zip from sdcard" and select Superuser+.zip (will push AnReboot + ES Explorer)
Go back on main menu and validate on "reboot system now". System is now permanently rooted.
Method 4 : ICS (V30X)
Caution, this method is a full flash ! EVERYTHING on the internal memoy will be lost !
Required : installed USB drivers, Smartflash, V30B (EU) binaries, and UnlockRoot 3.
Flash your device (the PDF guide in UPK may help noobs) | Ignore this step if you have already updated your phone to ICS, so you won't lose any data !
Unplug it (this is important) and boot normally (don't put your sdc yet so overall process will be shorter)
Do a factory reset (settings > backup & reset) | Ignore this step if your system is already running ICS
Ensure of LG software connexion type is selected (settings > PC connexion > USB connexion type)
Enable USB debugging before pluging the phone (settings > developer options), then plug
Install UnlockRoot, run it and follow instructions
For getting a working custom recovery, refer to the tutorial "Recovery for ICS" below
| Unlocking the bootloader |​
This must be done through ICS 4.0.4 and is only needed if you want to flash a custom recovery like CWM or TWRP. You have to root first before attempting. See below the "Recovery for ICS" tut.
| The Recovery |​
You assume all facts by doing that
Ensure of : installed USB Drivers / rooted system / USB debugging ON (settings > apps > dev)
Plug phone, wait for installation complete (first time plug), launch "CWMT", "CWMT6" or "TWRP"
Grant root access if prompted by SuperUser (phone)
Use AnReboot (or else) to boot into recovery
If you try booting into recovery without a custom recovery flashed, phone will perform a factory reset by default !
To load into recovery (or DownloadMod etc..), you have to use an app since LG P970 doesn't have a key combination for it. AnreBoot is perfect (included in Apps). But, if you apply a modded kernel, it becomes possible to go into CWM while the initial boot process.
Two other apps : ROM Manager, Quick Boot.
Reference thread by xantaro
| Recovery for ICS |​
The following tutorial will help you getting a working custom recovery for stock ICS firmwares. This is an U-Boot flasher package, based on the work of payback from 4pda.ru. Thanks to jockjoint for the share.
You assume all facts by doing that
Ensure of : installed USB Drivers / rooted system / USB debugging ON
Follow the 4th root method for ICS if needed
Unlock the bootloader with the Bootloader Unlocker tool
Flash your favorite custom recovery, CWM or TWRP.
Don't forget to install an app like AnReboot to reboot into recovery. If you use one of my recovery flasher packages, check AnReboot in the task list.
| ROMs / Mods / Tools |​
(Discovery) Remove battery, hold power buton, plug USB cable and wait until LG logo appears. Yeah ! The phone boots and you can use it with an infinite supply without killing battery's life !! But the phone seems having to be in airplane mod, otherwise it will shut down and display the battery missing message.
> It also works with my GT540, holding the call key. This could work on any LG androphone.
See the [INDEX] thread by RomWiz which intends to list every existing ROMs, mods, tools etc... for our device.
Sim unlock tutorial by Orcusen
| The GPS hook fix |​
Read this thread.
| Troubleshooting |​
- New to Android ?
Throw an eye on the Noobs How-to thread by NOOBY0815
- Got a bootloop or bricked your phone ?
Try the emergency recovery ; launch LGMobile Update (aka B2C) > Support > Recovery phone (aka SOS...)
Try hard reseting with R&D Test Tool (follow pdf guide)
Use SmartFlash with binary files of a firmware
- Lost/freezed your home ?
Try nikpik's solution.
- Lost IMEI ?
Follow r3store's How-to guide

Found several sw following your post and this thread as well: http://www.android-hilfe.de/lg-p970...6673-lg-serverlinks-firmware-bin-gesucht.html
AESTL (no-brand Spain?)
V10A: http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP970/AESPTL/V10A_00/V10A_00.kdz
AORETL (Orange Spain)
V10B: http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP970/AORETL/v10b_00/V10B_00.kdz
ANEUTL (no-brand Europe?)
V10A: http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP970/ANEUTL/V10a_00/V10A_00.kdz
V10B: http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP970/ANEUTL/V10b_00/V10B_00.kdz
I just downloaded all of these kdz files, so they are active links right now.
BTW. We still need a forum for the LGP970 "Optimus Black",
http://forum.xda-developers.com/showthread.php?t=1089967&page=10

Anybody knows howto install new firmware on LG-p970?

wrong post sorry

@rgabi
KDZU doesn't work ?
thanks kzhus. Yesterday spanish links were still invalid. The europe link is now fixed, the folder "10b_00" has a lower case... they are a bit strange at LG... well I'm going to play more with links and cases...

You mean KDZ updater? I didn't try it ...yet. I am not sure that it works and I don't want to risk my phone.
Late edit:
I just flashed V10B_00 ANEUTL (european unbranded).
I was inspired by this tut: http://www.android-hilfe.de/anleitungen-fuer-lg-p970-black/106331-how-optimus-black-flashen-kdz.html
except steps 2, 3, 7, 8, 10
Instead of step 10 click on "Read phone information" and then on "Upgrade start".
Select Country -> Different country
Select Language -> English
Hit "OK"
LG Software phone update must launch and begin to update the software.
Stay back and wait for reboot!

Thanks flashed the latest european

rgabi88 said:
I was inspired by this tut: http://www.android-hilfe.de/anleitungen-fuer-lg-p970-black/106331-how-optimus-black-flashen-kdz.html
Click to expand...
Click to collapse
I'm gonna flash mine too if the update doesn't suit to me.
Also, following your given url, there is a link which points to a list of firmwares here. This is just a copy of the first edit of my thread lol. It seems that I was the first to publish those links. If some of you speak german, you can discuss here.

@Ilko:
Look here, please: http://forum.xda-developers.com/showpost.php?p=14129668&postcount=35
Anyway, thanks Ilko for "V10B" firmware links.
Still no dedicated forum?? C'mon, guys!!

What are the differences between V10A and V10B?
Any changelogs?

Ven84 said:
What are the differences between V10A and V10B?
Any changelogs?
Click to expand...
Click to collapse
Untill now:
I have spotted one more app: RemoteCall
I think that is not as hot as before when I surf the net, use GPS or view YouTube, but I am not sure... too soon to tell

I have RemoteCall in V10A

Ven84 said:
I have RemoteCall in V10A
Click to expand...
Click to collapse
Maybe orange Romania removed RemoteCall because they don't provide this level of support... I don't know.....
No other differences spotted...
I can't tell for sure, but it seems to have a better battery life. After 13 h 22 ins, is at 86%.

Tell me ... If I unbrand my phone ( as far as I can see it has the lg firmware, not the orange one, although it was bought from orange ), and flash the latest firmware, can I later restore it to the original one in case of warranty issues? thanks in advance

rgabi88 said:
@Ilko:
Look here, please: http://forum.xda-developers.com/showpost.php?p=14129668&postcount=35
Anyway, thanks Ilko for "V10B" firmware links.
Still no dedicated forum?? C'mon, guys!!
Click to expand...
Click to collapse
Yeah I just wish to contribute
I've seen that link, but didn't get... what should I understand ?
Also, unfortunately I can't perform a flash with kdzu. When I try to read info it crashes

My P970 does not work - turned into a paperweight
Translation by tradukka. (rsrs)
1 - when I turn the phone into the computer by holding the volume + PC finds the phone does not appear over the screen "S/W upgrade please wait while upgrading"
2 - Even so did the upgrade process and it happened as expected, giving dll error until the phone restarts.
He changed the boot screen (VIVO) by LG screen. the problem is it takes the LG logo and then flashes the screen and the buttons and does not enter the android.
please need help, because now I have a paper weight $ 500 .
I also have a SE X10 and X8, and none of them gave me trouble. This LG is complicated.

well, I'dlike to help, but I'm not a dev, only a contributor who wanted to make things fowarding with this thread.
Also, to get the s/w screen, you must pull out the battery, then hold V+, then plug the cable. It must work. Try flashing to a stock firmware, that's the only thing which I can advise you.

Ilko said:
Also, unfortunately I can't perform a flash with kdzu. When I try to read info it crashes
Click to expand...
Click to collapse
When I'll arrive at home, I will write a step by step guide from A to Z.

hmm? I wanted to write my own guide too, but if kdzu cant read phone info I dont wanna risk to flash, even if it should work anyway.

Phone is getting as hot as usual...

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.

[Q] Problem with kitkat by Milaq

Hello ,
I have not had success with version 3 kernel . After installation the system is in a loop trying to make the Cyanogenmod boot without success. Appears at a time, Moboot screen and then the screen goes black ( dimly lit ) ... Then the system reboots .
I used Tailor to create the partitions :
USB ( media) : 1.953 MiB
User ( ext3 ) : 1.758 MiB
Android (system ) : 600 MiB
Android ( cache ) : 200 MiB
Android (date ) : 23,148 GiB
Unused Space : None
I created a folder with name cminstall with the following files (all downloaded through the appropriate links) :
cm - 11-20140110 - UNOFFICIAL - tenderloin.zip
GAPPS - kk - 20131208.zip
moboot_038 - tenderloin.zip
recovery - clockwork - 6.0.4.6 - tenderloin.zip
I reseted the WebOS Touchpad through and hit the volume button until the USB connection symbol appeared. Finally , as with all Novacom drivers installed on your computer I entered the following command in the Windows command prompt :
novacom.exe boot mem :/ / < ACMInstaller5M
The system installation appears to be correct , but the system is in boot loop .
Any help is welcome .
Grateful.

Solved
euzimar said:
hello ,
i have not had success with version 3 kernel . After installation the system is in a loop trying to make the cyanogenmod boot without success. Appears at a time, moboot screen and then the screen goes black ( dimly lit ) ... Then the system reboots .
I used tailor to create the partitions :
Usb ( media) : 1.953 mib
user ( ext3 ) : 1.758 mib
android (system ) : 600 mib
android ( cache ) : 200 mib
android (date ) : 23,148 gib
unused space : None
i created a folder with name cminstall with the following files (all downloaded through the appropriate links) :
Cm - 11-20140110 - unofficial - tenderloin.zip
gapps - kk - 20131208.zip
moboot_038 - tenderloin.zip
recovery - clockwork - 6.0.4.6 - tenderloin.zip
i reseted the webos touchpad through and hit the volume button until the usb connection symbol appeared. Finally , as with all novacom drivers installed on your computer i entered the following command in the windows command prompt :
Novacom.exe boot mem :/ / < acminstaller5m
the system installation appears to be correct , but the system is in boot loop .
Any help is welcome .
Grateful.
Click to expand...
Click to collapse
solved by myself. Tanx.

euzimar said:
solved by myself. Tanx.
Click to expand...
Click to collapse
Glad you have resolved your problem but it would be if you could possibly add how you solved it in in order to help anybody that my have a similar problems.
All the best.

Solved
sstar said:
Glad you have resolved your problem but it would be if you could possibly add how you solved it in in order to help anybody that my have a similar problems.
All the best.
Click to expand...
Click to collapse
Off course,
After doing the firmware update A6 ( well described in various forums ) I decided to install a version of android 2.6 kernel . This version was released by Milaq ... It all worked . After that , I copied the files from version 3 kernel for the HP Touchpad in a different folder ( I used / AndroidSetup ) .
Prior to installing the files used the program for WebOS called Tailor to adjust the sizes of the partitions according to my needs . I've allocated the largest share available to the data partition of Android. I left a 2.0 GB partition for media Touchpad also like to use this program . I used the "resize " option in Tailor is quite simple . If it does not work the first time just try another. You need to check the partition and then change its size.
Now , within the ClockWorkMod I installed the files from version 3.0 kernel available by Milaq :
cm - 11-20140110 - UNOFFICIAL - tenderloin.zip
GAPPS - kk - 20131208.zip
recovery - clockwork - 6.0.4.6 - tenderloin.zip
I first installed the recovery - clockwork - 6.0.4.6 - tenderloin.zip and rebooted the tablet . Then I did the installation of the other two files and everything usually occurred .
I hope I have helped someone .

The 20140112 milaq nightly gives me reboots and google play crashes every time. I'll give it another try next weekend.

I uninstalled and reinstalled Hangouts, Chrome, Gmail, Navigation and Maps to stop those from crashing. Running GAPPS 20130812 and jcsullins 20140125.

Similar problems but finally was able to jump from CM9 to CM11(Milaq) version. Just few days of use but looks ok. I was unable to repartition within cwm recovery scripts, fsck command gave failed=4 error no matter what. Decided to perform the hard way everything.
Current software stack, files and system being used was
Windows7-64bit, Java7-64bit
ACMEInstaller3, ACMEUninstaller novacom bootpush apps
WebOSQuickInstall-4.5.0.jar, webosdoctorp304hstnhwifi.jar Java apps
Preware, Tailor WebOS apps
Moboot 0.3.8 boot menu app
ClockworkMod 6.0.4.7 boot recovery app, this is important must be this or newer to understand datamedia mounts
cm-11-20140208-UNOFFICIAL-tenderloin_milaq <- final Android ROM
Additional packages I used during the trial-and-error, you may need them or be without. Im not sure.
ClockworkMod 6.0.1.9 boot recovery app, this is not datamedia compatible but was able to see /cminstall from "webos" usbmedia partition
New cwm was not able to see webos data partition, all it could see was new /0 Android datamedia profile folders. Don't know why maybe mount point problems somewhere in a boot scripts. This game me problems so had finally upload some of the files to this /0 folders using ADB push command.
Partition table after the process, performed in Tailor WebOS application. This table is only for new Android 4 "datamedia" Google use cases.
Android(System) 600MB
Android(Cache) 200MB
USB(Media) 1024MB <- old /sdcard, but A4.4 datamedia don't use it. Leave it to WebOS.
Android(Data) +25GB <- rest data goes to this new data part, my 32GB touchpad had 25GB available
Unused 0MB
Before the rebuild process had to reboot once to ClockworkMod 6.0.1.9 and formatted existing /sdcard partition. It removed filesystem errors and was good to go. Format removed everything including some of the WebOS apps.
* Before anything else run cwm backup command and copy important user files from /sdcard folder to Windows7, copy backup files as well
* Start Palm Novacom ntservice (service name: NovacomD) to enable usb, this service may use startup=manual value.
* Start device to webos recovery (keep VolumeUP during boot), should large usb logo appear on screen
* Remove existing Android, run dos command "C:\Program Files\Palm, Inc\novacom" boot mem:// < ACMEUninstaller
* Run WebOSQuickInstall-4.5.0.jar Java application on Windows
* Find Preware webos application and install, it should go to HPTouchpad device
* Reboot device to WebOS system
* Run Preware application, find Tailor partition utility and install
* Run Tailor and change partitions, you may shrink and enlarge partitions until get what you want. Leave 1024MB for USB(data) partition its used by WebOS. You maybe could shrink it to 700MB but wanted to play safe even if no planning install WebOS apps.
Following steps I cannot remember exactly what I did but am now running CM11 and CWM 6.0.4.7 datamedia enabled apps. You may need to fiddle with /cminstall, /downloads and /0 folders if new cwm boot app cannot see old sdmedia files from "webos" data partition.
* While in WebOS mount usb fileshare to make it visible in Windows7 file explorer, create /cminstall and /downloads subfolders
* Copy moboot_0.3.8-tenderloin.zip and recovery-clockwork-6.0.1.9-tenderloin.zip to /cminstall folder
* Copy recovery-clockwork-6.0.4.7-tenderloin.zip to /downloads folder
* Reboot device to webos recovery (keep VolumeUP during boot)
* Run dos command I]"C:\Program Files\Palm, Inc\novacom" boot mem:// < ACMEInstaller3[/I] to apply zips in /cminstall folder
* Reboot device and choose cwm recovery app from boot menu
* Select Update zip command and choose new cwm.zip from /downloads folder, apply file
* Reboot device and choose cwm recovery app from boot menu
* Use Android sdk ADB tool to push files to device, cwm mount no longer works in win7 because of ext linux filesys in new /data part
* Use adb push <sourcefile> /0/<something>/. dos command to push zips to device folder
* Push copy cm-11-20140208-UNOFFICIAL-tenderloin_milaq.zip and gapps-kk-20140105.zip files to device
* Start device and choose cwm recovery app from boot menu
* Select Update zip command and choose cm11.zip from folder, then select gapps.zip
* AndroidROM and GooglePlay apps are now installed on device.
* Reboot device and choose CM11 from boot menu
* TrebutchetUI may constantly crash, use topright corner pull down menu and Settings/Apps/All/TrebutchetUI and clear cache.
* You may need to reboot back to cwm and clear cache and dalvik cache few times if Trebutchet keeps crashing. Try to choose Settings/Theme/System option if keeps crashing. I had to do this few times before it was happy.
This was the very hard way and am sure streamlined method was available. Anyway this gave me confidence I still have all the apps creating CM install from scratch.

Working Bootable recovery for the KFFOWI (Ford)

As you know, root has been achieved on this device. Now, let's move on to recovery. The recovery.img is a lot like the boot.img, in the way that you can boot from it. In theory, if we make a 3e recovery.bin for this device (TWRP/CWM), and we boot from it, we will be able to install any rom. Let's let the Recovery.bin development start!
THIS DEVICE DOES NOT SUPPORT FLASHING RECOVERIES. YOU HAVE TO BOOT FROM THEM IN FASTBOOT.​
This device now has 2 custom recoveries, those 2 being TWRP (Team Win Recovery Project) and CM (CyanogenMod) Recovery. CyanogenMod recovery is much like the stock recovery, with the only difference being that CM Recovery can install files that don't have the Amazon ZIP Signature. TWRP, on the other hand, has a touchscreen display, and is much more user friendly than CM Recovery. The links to both are here:
CM Recovery
TWRP
You can do many things in a Custom Recovery, such as:
Install custom ROMs (Found here)
Install modifications to your current OS (XPosed Framework, Root, etc.)
Install GAPPS (Google Applications, including Play Store and Play Services)
Wipe your current ROM
Backup your current ROM
Restore a backup of a previous ROM
If you have any questions, ask them here.
Now, press the thank button here and thank the developers that made these recoveries and ROMs possible, and you are good to go.
Good Luck!

Im dumping the recovery partition right now as well as the boot as well and the other two extra bootloader stuff that may help us

I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.

Awesomeslayerg said:
I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.
Click to expand...
Click to collapse
Well, we just need someone to build a recovery for this device. Once that is bootable, we can install roms. Also, since we will most likely not be able to unlock the bootloader, Safestrap might be our best bet.

True.. it's a mediatek soc so there's gotta be a way to unlock the bootloader because most of the mediatek devices have unlocked bootloader I think. And besides it gives us an unlock code so we need to see what that deal is

Just leaving here partitions structure:
Model: MMC 8GND3R (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 2097kB 1049kB KB
2 2097kB 3146kB 1049kB DKB
3 3146kB 21.4MB 18.2MB EXPDB
4 21.4MB 22.4MB 1049kB UBOOT
5 22.4MB 39.2MB 16.8MB boot
6 39.2MB 56.0MB 16.8MB recovery
7 56.0MB 56.5MB 524kB MISC
8 56.5MB 60.2MB 3670kB LOGO
9 60.2MB 65.4MB 5243kB TEE1
10 65.4MB 70.6MB 5243kB TEE2
11 70.6MB 1329MB 1258MB ext4 system
12 1329MB 1591MB 262MB ext4 cache
13 1591MB 7818MB 6227MB ext4 userdata

Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader

Awesomeslayerg said:
Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader
Click to expand...
Click to collapse
I have made this one and test ro readback partitions bug gets error 2004
Partition lists
storage, boot_channel & block_size maybe not good
Model: MMC 8GND3R (sd/mmc)
storage: SDMMC ????
Sometimes tablet wont boot and have to remove battery connector
Last SP Flash TOOL, linux version have much errors and force to remove battery
http://firmware.su/51343-sp-flash-tool.html
DO NO USE TO DOWNLOAD ANYTHING
UNDER CONSTRUCTION
scatter updated, UNTESTED

Lets go recovery!

idme print as su
unlock_code:
---------- Post added at 12:09 PM ---------- Previous post was at 11:52 AM ----------
There are 2 boads type and 2 preloaders......
Mine have preloader_prod.img board_id: 0025001040000015
Code:
# check if production device
if ("0025001000000015" == read_file_str("/proc/idme/board_id") ||
"0025001000010015" == read_file_str("/proc/idme/board_id") ||
"0025001010000015" == read_file_str("/proc/idme/board_id") ||
"0025001010010015" == read_file_str("/proc/idme/board_id") ||
"0025001020000015" == read_file_str("/proc/idme/board_id"))
then
ui_print("Copying preloader.img to boot partition 0 for unsecure device...");
package_extract_file("images/preloader.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
ui_print("Copying preloader_prod.img to boot partition 0 for secure device...");
package_extract_file("images/preloader_prod.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
endif;

my /proc/idme/board_id reads 0025001040000015

Can anyone try this: http://forum.xda-developers.com/showthread.php?t=2798257?
Sent from my KFFOWI using Tapatalk

I did yesterday didn't work

Awesomeslayerg said:
I did yesterday didn't work
Click to expand...
Click to collapse
Did you try Fastboot boot recovery.img with the one it gave?
Sent from my XT912 using Tapatalk

No I'll try today

Okay i used the MTK-TWRP thing right now and used it to unpack the recovery image and it looks like we can use this to our advantage to flash unverified files by editing some of the prop settings.

Can someone try this: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device? It might work.

How would we flash it?

Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Zips are flashable in flashfire...

Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Use the following commands to flash the recovery
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
- I have Cyanogenmod Recovery working except a few minor niggles
- Let you know once it's fully working
- It looks like we can't boot unsigned images that are flashed to the recovery partition
- If I boot the image from fastboot rather than flashing it then it works
- CVE-2014-0973 is patched in the bootloader

Bootloop after re-installing SuperSu / Missing Wi-Fi and SD-card connectivity after root

Hello everyone,
I recently bought a Predator 8 Tablet (GT-810) with Android 5.1 and proceeded to root it.
I only found 2 threads here, and both were VERY confusing and partly contradicted each other.
One suggested flashing 3 parts of an .img file which had previoulsy been extracted. Neither did I have the knowledge to do that nor I did not succeed finding a way to achieve that on the internet.
Predator 8 Booted to TWRP | Acer GT-810 | TWRP | Help us Root
So I managed to Unlock my GT-810 Bootloader through Settings | About | Tapping BUILD # morethan 7x | Enabled ADB/USB Debugging | OEM Unlock | Rebooting via POWER Button + "Vol UP" | fastboot oem unluck Automatically followed by a full Factory...
forum.xda-developers.com
I then decided to go with the less adventurous option from the second thread:
Acer Predator 8 TWRP 3.0.2
TWRP 3.0.2 for Acer Predator 8 ported by Ruben. - If you like my work please donate here, it will also give me a boost to make more things for this device :) : https://www.paypal.me/RubenCraveiro -----------...
forum.xda-developers.com
I succeeded in unlocking the bootloader.
After that, one person from the threads 5 years ago released some old files on Google Drive, among them an unsecuredbootimage.img, the TWRP.img and the SuperSu 2.46, which was supposed to work.
I flashed the unsecuredbootimage.img, then the TWRP.img, the SuperSU and when the root came up with RootChecker and I thought I was in heaven.
Unfortunately, I had no more access to either Wi-Fi, nor the SD-card. Wi-Fi would occasionally be greyed out, then turn on, but not find any network. The SD-card was not recgognized anymore.
I found a workaround which suggested I reflash only the "modem" file from within the boot.img, but I could not extract it.
How to Fix No WiFi, Calls, Network after Root or Custom ROM
In this tutorial, we will show you the steps to fix the no WiFi, Calls, or Network issues after root or flashing custom ROM on Android.
www.droidwin.com
I then proceeded to install Magisk. The Manager had already been installed, I transferred the latest version (23.0) as a zip file to the device and flashed it via TWRP.
When I tried to "patch a file" through Magisk / install, the "Let's go" option was always greyed out, so I was stuck there again.
When I checked the SuperSU, to my surprise, I could not find it any more within Android, it looked like it had disappeared, so I decided to reinstall it.
I went to recovery (TWRP) and flashed SuperSU 2.46 and since then I am in bootloop.
I need some help in exiting the bootloop and a solution for the missing Wi-Fi and SD-card connectivity.
Any suggestions would be greatly appreciated.
Android 5.1
Predator 8 Table GT-810
SuperSU 2.46
TWRP 2.8.7.0
The additional files I have:
STOCK boot.img (30 MB)
STOCK factory.img (10 MB)
TWRP 2.8.7.0 for the device (18 MB)
unsecuredboot.img for the device (9 MB)
Thanks in advance...