Database Develop

Install pre 2.2 OTA with 100% working root 2.0 radio/720p video

UPDATE, you will have market issues, some apps will not show up. For a fix see this post:
http://forum.xda-developers.com/showthread.php?t=728451&highlight=market+ota
READ FIRST
DO NOT APPLY THE UPDATE.ZIP TWICE or YOU MAY BRICK YOUR PHONE!
Everyone should know that if you apply this update and VZW changes the radio in the official then you probably won't be able to upgrade your radio to it.
Also if you do this you will not be able to revert back to stock until a new RUU is released, and the problem with a new RUU is that they may close all known root methods. If you try with any current RUU's you will get a "Main version is older" error.
The radio is very good and 720p will work but everyone should know this might prevent future radio updates.
Click to expand...
Click to collapse
READ SECOND:
In case the OTA comes out and there is something truly different, you can follow this procedure to downgrade hboot and install an older RUU:
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
dinc_ota.zip
Put the file from mediafire.com on your SDCARD as update.zip
If rooted, you have to RUU your phone back to stock. Download the image from the link below, put on root of SDCARD and then boot into bootloader(powerdown, hold power and optical button in) then go to bootloader, then it should load the img and then apply it.
http://www.mediafire.com/?yum40znzwmmmtyl
Boot back to your phone and apply the first OTA update we got. If you dont do this, you might get errors trying to install the new update.
Then go to STOCK recovery.
Apply update.zip
Reboot, then activate.
Then follow this:
(Mine got stuck on rebooting phone, I just unplugged my phone and then plugged it back in again really fast again, it seemed to work like normal just starting the UnrEVOked 3.0 with phone hooked up)
UnrEVOked v3.0 Is Out - ROOT NO LONGER REQUIRED + NEW CLOCKWORK 2.5!!! - xda-developers
Then one final step for now to install root again really easy.
Download this
http://www.unrevoked.com/incredible/payload-update.zip
Put it on your SD card, then reboot into clockwork recovery
Go to install zip from SD-Card
Choose the payload-update.zip
You have root again and busybox is installed.
Some reason UnrEVOked 3.0 didnt reroot my phone but doing the steps above will have you with the latest update and 2.0 radio with 100% working root and working 720p video.
Picture proof it works, drocapped the pic, so you know root is all good.
{
"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"
}

Cool
This sounds really dangerous to me and while I appreciate the warnings, those warnings show pretty bad consequences. I think I will wait until unrEVOked simply provides a root-safe version of the OTA.

Can't wait to try this when I get home.. nice work

JTCGiants56 said:
Can't wait to try this when I get home.. nice work
Click to expand...
Click to collapse
Yea someone posted the leak file here, I thought I messed up at first because root wasn't on my phone! Then I figured it out so I figured I would post how to easily get root back on.

READ ME
Everyone should know that if you apply this update and VZW changes the radio in the official then you probably won't be able to upgrade your radio to it.
Also if you do this you will not be able to revert back to stock until a new RUU is released, and the problem with a new RUU is that they may close all known root methods. If you try with any current RUU's you will get a "Main version is older" error.
The radio is very good and 720p will work but everyone should know this might prevent future radio updates.
Please update your original post with this information.

Might hurt you in the end
If the official radio version ends up being like 1.7 or 1.9 everyone who did this will be screwed correct? There is no way to reverse this once you have flashed the leaked radio.
EDIT: Haha ^^^^^^ you beat me to it by 2 minutes

Spiteful Monkey said:
If the official radio version ends up being like 1.7 or 1.9 everyone who did this will be screwed correct? There is no way to reverse this once you have flashed the leaked radio.
Click to expand...
Click to collapse
Its not even just that. The update was a radio.diff file not a radio.img. I'm not 100% sure but I'm guessing that it just makes modifications to your radio, and not replace it.
If they make changes to the radio.diff it may not be able to make the proper changes to our radio because we are running a leaked version that already has changes in it.

Wonder if the update can be dismantled and only have the 720p added to the phones?

People should be able to get the stock recovery .zip, out of sone of these stock ruus so that wiping its not necessary... Redoing your entire phone is a pita... Much easier if someone can isolate the stock recovery file without messing with the data partition
Sent from my HTC Incredible using the XDA App

shoman24v said:
Wonder if the update can be dismantled and only have the 720p added to the phones?
Click to expand...
Click to collapse
A few have tried (including myself) and 720P doesn't work without the radio. It will show in the camcorder and you can select it, but if you try and record it will reboot on you.
I'll keep trying but it seems impossible to have 720P recording without the radio.

OP. unrevoked will root your phone for you. i'm guessing you're on windows. those extra steps are not necessary on linux or os x.

thank you for your info!
i didnt know i have to install payload-update.zip......

So basically we should just wait? All this is giving us right now is the 720p right??

thatdudebutch said:
So basically we should just wait? All this is giving us right now is the 720p right??
Click to expand...
Click to collapse
it should also push out a new bootscreen animation and install mobile hotspot (haha..we already have wireless tether..) rumor is also that swype now comes into play as well.

So if I'm reading this right you're saying there's a chance that you could never receive another OTA update?

I guess I will just wait until tomorrow when the OTA is released to make sure future upgrades work.

can someone who does this ota and then roots their phone make a nandroid of it stock...i think i may have messed something up real bad and i cant get it to stop boot looping...

I'm trying to RUU but it can't find the file? what am I doing wrong

Seagrizzly said:
I guess I will just wait until tomorrow when the OTA is released to make sure future upgrades work.
Click to expand...
Click to collapse
Tomorrow? Did I miss something?

im seriously debating unrooting my phone before the OTA hits...

[SELFKANG AOSP ROM] CyanogenMod 7.1 Alpha Release [UPDATE 11/16 PM]

** [UPDATE 11/16] = Minor update adding Droid3Bootstrap / RomManager support for installs. You DO NOT need Safestrap to install CM7 now. Any Bootstrap will work.
[UPDATE 11/10] = Better audio (still debugging why volume will occassionally fall back down -- if it does go into settings -> sound -> volume and drag the media slider up -- will reset it), fixed bluetooth -- 2nd ota patch .zip for 5.7.894 OTA users
It's an OMAP4 optimized AOSP build using CyanogenMod sources. I used some of the published Moto Source (9/18) where I felt it was appropriate to get the low level services running. You will not see any Blur files in this build.
Download Link Here
If you're running the 5.7.894 OTA, you will also want to apply a 2nd .zip afterward to update the few stock binaries that are in the build. It's under the .zip download links.
Changelog Here
For the most up-to-date information / builds check my blog: http://hash-of-codes.blogspot.com
What is working in this build:
Phone dial and recieve calls (10/18)
Wifi
SD Cards
Audio is getting better
GPS
3G data
Bluetooth
lots I can't list
Feel free to flash gapps and test away. To download GApps go here and select the top "universal CM7 link for GB"
What isn't working:
Camera app doesn't soft reset the phone anymore, but it isn't working yet either.
Phone app FC's on the boot. Just close the notification and it'll restart 3G immediately.
Audio is very funky atm. It's getting better. If you lose volume, try opening Setting -> Sound -> Volume and drag the "media" slider down and then back up.
GSM Users:
I reviewed some changes submitted by XDA's coreless88 and for the moment I'm just not comfortable putting them in the main build. They would default the phone to GSM/WCDMA. I WILL absolutely get the native support for both GSM and CDMA working as this build matures. It just may take a while. If you really want a GSM variant of this build let me know and I'll reproduce a version with his build.prop changes. For me personally, this can't be a daily driver till the audio issues are fixed.

Great I need calling so won't try it yet, but thanks for all your work

will test it out tonight o hell more like as soon as i get a chance lol

So if 3G works can I still get texts? I don't need to talk to anyone.

yeah texts works, gapps works. just a few funny things. and not like "ha ha" funny either!
still BA!

Once installed, can I do a backup of this and flash back and forth using Safestrap?
Edit: Backup of stock rom gives an error when generating a md5. Is that a problem?

Thanks for all you hard work on this.

im bricked. i flashed back to monster, cleared, and now i cannot boot into bp tools. i start in recovery, hit bp tools, and it goes back to bootlooping. i dont have the sbf as the link is down. can anyone help? AND i only had about 40% battery

MrJudylicious said:
im bricked. i flashed back to monster, cleared, and now i cannot boot into bp tools. i start in recovery, hit bp tools, and it goes back to bootlooping. i dont have the sbf as the link is down. can anyone help? AND i only had about 40% battery
Click to expand...
Click to collapse
Did you miss a step?
I just booted up for the first time about 5 seconds ago. Working great.
Thanks Hashcode!

i get to step 9 and at the end of the back up it says Error generating md5 sum! trying to make a different backup to see if i get same error.

Androidsims said:
Once installed, can I do a backup of this and flash back and forth using Safestrap?
Click to expand...
Click to collapse
Good Question! Short answer: yes.
For now, you have to run a backup (MotoBlur), then format /system, wipe data/cache and install the CM7 zip. When you're done with CM7, you can do another backup (if you want to save CM7) and then restore your original MotoBlur. Make sure to toggle the "Safe System" setting afterward.
As soon as I fix some things in the CM7 build so that the phone is usable, I'm going to work on Safestrap some more.
The next version of Safestrap will automatically store and load your userdata when you toggle the "Safe System" setting. So there won't be a need to perform all of the backup/restores. It will just be the 1 toggle and then reboot.
And sometime in the future, I'm going to put up a MotoBlur "ROM" .zip which runs in 2nd-system. SO stuff like SteelDroid or other ROMs can be safer to install/run. Devs can use that MotoBlur ROM as a template for doing theming, and other things.
It really depends on how well received Safestrap is and if the community wants to see more of it.

Androidsims said:
Did you miss a step?
I just booted up for the first time about 5 seconds ago. Working great.
Thanks Hashcode!
Click to expand...
Click to collapse
no no i booted into CM7 just fine. it was when i booted back into recovery, flashed monster1.2, cleared cache, then reboot lead me to bootloop

MrJudylicious said:
im bricked. i flashed back to monster, cleared, and now i cannot boot into bp tools. i start in recovery, hit bp tools, and it goes back to bootlooping. i dont have the sbf as the link is down. can anyone help? AND i only had about 40% battery
Click to expand...
Click to collapse
I have fastboots for both 5.5.959 and 5.6.890. I can do a mediafire share of whichever you need.

Hashcode said:
I have fastboots for both 5.5.959 and 5.6.890. I can do a mediafire share of whichever you need.
Click to expand...
Click to collapse
i was on 890 so i figured i should flash 890. it would be awesome if you could

MrJudylicious said:
i was on 890 so i figured i should flash 890. it would be awesome if you could
Click to expand...
Click to collapse
I'm going to put the fastboot files on my site for download. It might take a while. Showing 2 hours for the 420M file. I'll update this post with a link in a bit.
Edit:
Unfortunately the nature of flashing ROMs over your live system on a locked bootloader phone means that the hijiack is broken until you can get into the OS and reinstall some sort of Bootstrap. And this was exactly the reason why I developed Safestrap. :/
That being said, you'll likely be able to just flash your /system using the fastboot files and you'll be fine. And don't forget to wipe userdata when swapping ROMs. I've seen countless bootloops from not wipeing userdata. This is ESPECIALLY important for CM7 vs. MotoBlur.

oostah said:
i get to step 9 and at the end of the back up it says Error generating md5 sum! trying to make a different backup to see if i get same error.
Click to expand...
Click to collapse
I got the same error but proceeded anyways.
Man, I forgot how smooth CM is.... Loving the new lockscreen and built in Screenshot features too.

Hashcode said:
As soon as I fix some things in the CM7 build so that the phone is usable, I'm going to work on Safestrap some more.
The next version of Safestrap will automatically store and load your userdata when you toggle the "Safe System" setting. So there won't be a need to perform all of the backup/restores. It will just be the 1 toggle and then reboot.
And sometime in the future, I'm going to put up a MotoBlur "ROM" .zip which runs in 2nd-system. SO stuff like SteelDroid or other ROMs can be safer to install/run. Devs can use that MotoBlur ROM as a template for doing theming, and other things.
It really depends on how well received Safestrap is and if the community wants to see more of it.
Click to expand...
Click to collapse
thanks hashcode, for CM7 work, safestrap, etc...YOU ARE GREATNESS!!!

Hashcode said:
Good Question! Short answer: yes.
For now, you have to run a backup (MotoBlur), then format /system, wipe data/cache and install the CM7 zip. When you're done with CM7, you can do another backup (if you want to save CM7) and then restore your original MotoBlur. Make sure to toggle the "Safe System" setting afterward.
As soon as I fix some things in the CM7 build so that the phone is usable, I'm going to work on Safestrap some more.
The next version of Safestrap will automatically store and load your userdata when you toggle the "Safe System" setting. So there won't be a need to perform all of the backup/restores. It will just be the 1 toggle and then reboot.
And sometime in the future, I'm going to put up a MotoBlur "ROM" .zip which runs in 2nd-system. SO stuff like SteelDroid or other ROMs can be safer to install/run. Devs can use that MotoBlur ROM as a template for doing theming, and other things.
It really depends on how well received Safestrap is and if the community wants to see more of it.
Click to expand...
Click to collapse
So ultimately this will basically dual boot?
{
"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"
}

Androidsims said:
I got the same error but proceeded anyways.
Man, I forgot how smooth CM is.... Loving the new lockscreen and built in Screenshot features too.
Click to expand...
Click to collapse
OH, I totally forgot that the phone FCs on boot. It reloads 3G data shortly afterward. I have a fix coming for that as well.
You could say.. the OS boots too fast for it.
THe normal boot process for MotoBlur involves the phone coming up as GSM initially, doing a few checks for network, failing and then dropping into a Janky CDMA version of GSM.
CM7 currently boots straight to CDMA.

Hashcode said:
I'm going to put the fastboot files on my site for download. It might take a while. Showing 2 hours for the 420M file. I'll update this post with a link in a bit.
Edit:
Unfortunately the nature of flashing ROMs over your live system on a locked bootloader phone means that the hijiack is broken until you can get into the OS and reinstall some sort of Bootstrap. And this was exactly the reason why I developed Safestrap. :/
That being said, you'll likely be able to just flash your /system using the fastboot files and you'll be fine. And don't forget to wipe userdata when swapping ROMs. I've seen countless bootloops from not wipeing userdata. This is ESPECIALLY important for CM7 vs. MotoBlur.
Click to expand...
Click to collapse
I appreciate it. I have teh file blur_version.5.5.959.xt862.verizon.en.us.zip Is that the fastboot?
nevermind. i found it here http://rootzwiki.com/showthread.php?5103-SBF-Droid-3-Fastboot-files-(5.5.959-and-5.6.890)
i really appreciate you doing that for me though. i just shat a brick (no pun intended)

DROID 4 Utility Pre-Release [WINDOWS]

UPDATED PAGE!
Back with another utility... this time pre-release Droid 4! I haven't seen a Droid 4 board yet so I guess I have to put this under General.
There are no fastboot files as of writing this (2/11/2012) but once they come out I will be making a full version that includes fastboot restore. For now, only a few MB compared to GB full.
Includes Root function thanks to Dan Rosenberg's motofail exploit.
It is the only reason we can have a working utility root!
Donate to his fund for the Red Cross here
Note to all: I am giving control of the Droid 4 Utility to skylarmb (Although I will still be very involved )
Don't use Safestrap yet!
Hashcode is making a D4 version very soon!
Motorola Drivers (If its not working install this.)
32 Bit Link: http://www.motorola.com/staticfiles...al_Drivers/MotoHelper_2.1.32_Driver_5.4.0.exe
64 Bit Link: http://goo-inside.me/apps/mattlgroff/Motorola_End_User_Driver_Installation_5.4.0_64bit.msi
{
"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"
}
Size: 2.09 MB
MD5: 8b44666a5d97137292ec03e74f8b75d7
Link: http://goo-inside.me/apps/mattlgroff/Droid4Utility0.3.zip
Changes in 0.3----
Added new text at bottom
Removed Safestrap until D4 version released.
Added Overclock install. See guide here (Overclocking Your Droid Razr - DroidRzr.com)
(thanks coryjohn and OPPtimizer Project - http://code.google.com/p/opptimizer/ )
Used "Ultra" .zip compression.
Enjoy~!
If you feel like contributing to my Razr Dev fund you may do so here.
Screenshot of what the folder should look like in order for it to run:

And if anyone could do a system pull and send me a copy over a file-share site like mediafire or minu.us that would be very helpful to me. Thanks
EDIT: Nvm. I got one.

What do the different options do? I went from having a OG Droid, with cyanogenmod which was super straight forward to this and I have no idea what the fastboot or bootstrapping does.
If you still need the /system pull I can send you the link over PM.

moah909 said:
What do the different options do? I went from having a OG Droid, with cyanogenmod which was super straight forward to this and I have no idea what the fastboot or bootstrapping does.
If you still need the /system pull I can send you the link over PM.
Click to expand...
Click to collapse
Bootstrap is the way to get into a CWM-like recovery for the Razr. I have no way to test this on a D4, seeing as I don't have one.
ICS root works on the GSM ICS leak, so it may work for ours too.
Boot into Fastboot from Debugging (go directly to fastboot mode from the phone turned on and in USB Debugging mode)
Boot into Motorola Recovery from Debugging (same as above but into Moto Recovery)
ADB Shell (for more manually inclined users)
Reboot phone from Debugging

I have ADB 1.0.26 (at least that is what it says when I go to Start>Run>CMD>and type in adb.
Is there anything else I need to get the phone rooted? Any other drivers or anything along those lines. I know the phone needs to be in development mode, but I want to make sure all of the other software on the computer end is up-to-date since I've had a G1, Mytouch Slide 3G, G2, and Droid 3 before picking up this Droid 4.

Code3VW said:
I have ADB 1.0.26 (at least that is what it says when I go to Start>Run>CMD>and type in adb.
Is there anything else I need to get the phone rooted? Any other drivers or anything along those lines. I know the phone needs to be in development mode, but I want to make sure all of the other software on the computer end is up-to-date since I've had a G1, Mytouch Slide 3G, G2, and Droid 3 before picking up this Droid 4.
Click to expand...
Click to collapse
You'll need the latest Motorola drivers. I will add links in the OP

mattlgroff said:
You'll need the latest Motorola drivers. I will add links in the OP
Click to expand...
Click to collapse
Thanks! Has there been a tried and true wireless tether application yet?

Code3VW said:
Thanks! Has there been a tried and true wireless tether application yet?
Click to expand...
Click to collapse
I think most people use the one they use with CM.
code.google.com/p/android-wifi-tether/
This one I think. You have to install via the APK.
Please correct me if there is a different one of this is the wrong one. I'm actually curious myself.

I have no technical explanation for this, but...
DO NOT RUN THE .BAT FILE AS ADMINISTRATOR.
If I right-click the .bat file and click "run as administrator" in Windows 7, everything would appear to work (at least to the splash screen), but when I selected option 1 it would come back with a bunch of lines of "the system cannot find the path specified."
When I just double clicked the .bat file it ran properly and am now set.
Again, I have no idea why it worked this way, but it did...at least on my system. Windows 7 64-bit here, btw.
---------- Post added at 11:37 PM ---------- Previous post was at 11:10 PM ----------
ian3d said:
I think most people use the one they use with CM.
code.google.com/p/android-wifi-tether/
This one I think. You have to install via the APK.
Please correct me if there is a different one of this is the wrong one. I'm actually curious myself.
Click to expand...
Click to collapse
Turns out you were right...loaded Wifi Tether v3.1 beta 11 from here and it works no problem!

So we actually have safestrap already for the d4?
EXCITED! !!!!!!
Sent from my DROID4 using XDA App

phrir1 said:
So we actually have safestrap already for the d4?
EXCITED! !!!!!!
Sent from my DROID4 using XDA App
Click to expand...
Click to collapse
Yup! Still take care though... it's still dangerous without fastboot or SBF files.

Ya wont be flashing anything just yet hopefully we get an ics rom soon since its so close to the razr
Sent from my DROID4 using XDA App

Code3VW said:
Thanks! Has there been a tried and true wireless tether application yet?
Click to expand...
Click to collapse
I was wondering the same thing, if the RadioCom Tether Hack worked. But I tried to enable the tether on the phone, and Verizon pops up a message as long as I have a $29.95 data plan then I can tether. So I went forward and enabled teather since I have the unlimited plan, and all seems well. I went to My Verizon web and checked to see if I'm being charged, or if another service has been added, and I see non. So I will try using this for now.

Thank you XDA for putting my Utility on the front page =D

So I used the utility to root my droid 4, but I did not install the safe strap. At this point I do not plan on doing any flashing or even heavy customization. I just wanted root for install of wifi tether and titanium backup. Is there a need for safestrap before I plan on getting into flashing etc?

shadowace said:
So I used the utility to root my droid 4, but I did not install the safe strap. At this point I do not plan on doing any flashing or even heavy customization. I just wanted root for install of wifi tether and titanium backup. Is there a need for safestrap before I plan on getting into flashing etc?
Click to expand...
Click to collapse
I'd recommend against installing safestrap if you won't be flashing anything. =D

bricked my droid 4... for now...
I'm pretty pissed at my self... I softbricked my droid 4 days after i got it... now im just waiting for the fastboot restore option... I'll be checking back here every day now lol... does anyone know when it will be released, or is it even a guarantee it'll be released?

How did this happen? Best of luck on getting it fixed!
Sent from my DROID4 using XDA App

Well i had success using the droid razr utility before this one came out (of course cant fastboot recovery with it tho ), so i thought maybe the EternityProject WebTop Mod would work, so i tried installing it through adb and i went to do the 2nd step and found out webtop was disabled... I figure i did something wrong... so i went to restore the backup i made and all of the sudden its stuck in AP fastboot saying flash failure.
This really sucks cause i bought the lapdock 500 to go with the phone. Now I have 2 bricks sitting on my desk, until further notice.
I since i have insurance on this phone I am putting the phone up for sale on craigslist with an hdmi cable so someone can enjoy a small android tab and webtop if they want it for 120... anyone think I'll be able to sell it before the fastboot recovery is released?

Quick question....If I do a system pull and then try to throw a few things from UOT kitchen like battery percent.....would that work without the files being deodexed?

[HOWTO][P3113] Revert to Stock Android 4.0.4 ICS build UEBLH2

From Android Authority
{
"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"
}
The official firmware can be used to restore your tablet to its factory state, which means that it can be used as an escape route if you ever need to revert to stock firmware. For instance, this can be very handy if you stumble upon an bad or misbehaving custom ROM that makes your tablet malfunction.
This guide shows you how to revert the Galaxy Tab 2 7.0 P3113 to Android 4.0.4 ICS build UEBLH2 (stock official firmware).
Warning​
The instructions in this guide are intended for use with the Samsung Galaxy Tab 2 7.0, model number GT-P3113. Applying these instructions on another device or model may produce undesired outcomes.
The information in this guide is provided for instructional and educational purposes only. There is no guarantee that these instructions will work under your specific and unique circumstances.
Use these instructions at your own risk. We shall not hold any responsibility or liability for whatever happens to you or your device arising from your use of the info in this guide.
Read and understand the whole guide first before actually performing the instructions.
Requirements​
Samsung Galaxy Tab 2 7.0 GT-P3113
A Windows PC
Install your handset’s USB drivers on the PC. You may install the drivers by installing Samsung Kies.
Enable USB debugging on your handset.
Disable antivirus, firewall, and other security software. Also disable Samsung Kies and other software that accesses your phone. Such software can interfere with the procedure in this guide.
Download the following files to your computer:
UEBLH2 firmware update package for Galaxy Tab 2 7.0 GT-P3113 (P3113UEBLH2_P3113XARBLH2_XAR.zip, 785 MB)
Odin 3.04 (Odin3_v3.04.zip, 456.59 kB) (Attatched)
Make sure your device’s battery still has at least 70% power. You don’t want the device to shut down in the middle of the procedure.
Backup all personal data on your phone to make sure you have a copy of your personal data (e.g., contacts, SMS, MMS, Internet settings, Wi-Fi passwords, and the like) in case the procedure in this guide erases such data.
Instructions​
Using ZIP extraction software, extract the *.tar.md5 file contained in the UEBLH2 firmware update package.
Extract the contents of Odin3_v3.04.zip to your computer.
Turn off your tablet. Make sure it is not hooked up to your PC.
Run Odin on your computer by double-clicking Odin3 v3.04.exe.
Click the PDA button in Odin and load the *.tar.md5 file contained in the UEBLH2 firmware update package that you unzipped.
Do not change any other setting in Odin. Make sure that the checkbox for “Re-partition” is not ticked.
Reboot the tablet into Download Mode by holding down the Volume Down and Power buttons until you see the warning screen. Press the Volume Up key to continue to Download Mode.
Connect the tablet to your PC via USB cable. You should see an “Added!” message on the Odin window.
Click the Start button in Odin to begin flashing the firmware to your tablet. When installation completes and succeeds, Odin will display a “PASSED” message in one of its boxes. The tablet will also automatically reboot.
If, on rebooting, the screen gets stuck at the Samsung logo, try resolving it by doing the following:
Turn off the tablet.
Boot into Recovery Mode by holding down Power and Volume Up buttons together until the screen turns on. When the Samsung logo appears, let go of the Power button but keep holding down the Volume Up button until the device boots into recovery.
In Recovery Mode, select Wipe data/Factory reset and select Yes on next screen.
Select Reboot system now to reboot the tablet
Congratulations! You’ve successfully reverted your Samsung Galaxy Tab 2 7.0 to Android 4.0.4 Ice Cream Sandwich build UEBLH2.

"Disable my AV/security" before I download from unknown links ?
Cool story bro. :laugh: General tip for PC users , scan everything you download onto your desktop no matter the source with your AV. Especially an ".exe "
Nice guide apart from that.

thank you.. I didnt think of wipe data/factory. I was stuck on samsung logo. i wanted to return to stock since I'm giving the tablet to my nephew and don't want him doing crazy stuff. :victory:

Sean_Seany said:
"Disable my AV/security" before I download from unknown links ?
Cool story bro. :laugh: General tip for PC users , scan everything you download onto your desktop no matter the source with your AV. Especially an ".exe "
Nice guide apart from that.
Click to expand...
Click to collapse
NO, not disable before downloading, disable your AV before using Odin to flash, as IT IS A WELL KNOWN FACT that some AV programs can cause issues with flashing ROM's.

daniel644 said:
NO, not disable before downloading, disable your AV before using Odin to flash, as IT IS A WELL KNOWN FACT that some AV programs can cause issues with flashing ROM's.
Click to expand...
Click to collapse
Did you actually read what the OP posted ? Nah didnt think so . So why exactly do you need to disable AV/Secuirty for a USB file transfer ? Please enlighten me with your facts.....

Sean_Seany said:
Did you actually read what the OP posted ? Nah didnt think so . So why exactly do you need to disable AV/Secuirty for a USB file transfer ? Please enlighten me with your facts.....
Click to expand...
Click to collapse
If you are having issues disabling your antivirus software, then don't disable it. I never disable mine. The only reason I added it to the post is because in rare cases the AV can cause issues for some reason or another.

Sean_Seany said:
Did you actually read what the OP posted ? Nah didnt think so . So why exactly do you need to disable AV/Secuirty for a USB file transfer ? Please enlighten me with your facts.....
Click to expand...
Click to collapse
I think you misunderstand, when flashing files VIA ODIN certain antiviruses have been known to cause issues, personally I never have but it is a standard disclaimer on ANY Device to computer connection, when doing debugging or flashing not file transfers, I see the same disclaimer on all the Droid Razr Utility builds, and most ROM's being flashed via ODIN, it's rare but it could happen.

I think the reason for disabling your AV,is because it and your pc dont know the difference. When you run a program that flashes 'firmware' like Odin,it can be detected as malicious and blocked.HTC recommends the same thing for flashing with their exe files,and thats the same reason why its recommended during most rooting process'.

dude I thank you for this... I bought a gt 3113 3 days ago and it came with jb out of the box, dont get me wrong jb is awesome i run it on my sgs2 only thing is id like to use my tablet for streaming online content and most of the sites i view still use flash which jb no longer supports so i been looking for ways to revert it back to stock ics cause i love the ir function of the stock rom and most custom roms bork the ir blaster as per my research. anyway anymore details i should know before attempting this?? thanks in advance
Edit: do you have another linky for the FW? hotfile keeps erroring out on me thanks again

aj9507 said:
dude I thank you for this... I bought a gt 3113 3 days ago and it came with jb out of the box, dont get me wrong jb is awesome i run it on my sgs2 only thing is id like to use my tablet for streaming online content and most of the sites i view still use flash which jb no longer supports so i been looking for ways to revert it back to stock ics cause i love the ir function of the stock rom and most custom roms bork the ir blaster as per my research. anyway anymore details i should know before attempting this?? thanks in advance
Edit: do you have another linky for the FW? hotfile keeps erroring out on me thanks again
Click to expand...
Click to collapse
Yours came with JB??? Just curious what country are you in? The 3113 is US only no?? Maybe were finally getting our official release any day now...
Sent from my crack smoking SGH-i777

Slavestate said:
Yours came with JB??? Just curious what country are you in? The 3113 is US only no?? Maybe were finally getting our official release any day now...
Sent from my crack smoking SGH-i777
Click to expand...
Click to collapse
Yup usa version. 4.1 android love jb but hate that I can't stream from most sites due to lack of flash and most root methods I can't get to work
Sent from my GT-P3113 using Tapatalk HD

Flash works perfect on every jelly bean rom I have tried just simply sideload it but I suppose thats of topic.

yup sideloaded it and even running the older version of the browser to ensure flash support and its laggy and stutters lovin the tablet though

Yes.... some of these are preloaded with 4.1.1.
I bought 2 of these for my daughters. 1 was defective. When I took it back, the store didn't have anymore so they sent me to a store in another city.
I ended up with one running 4.0.4 and one running 4.1.1.

BuLLitz said:
Yes.... some of these are preloaded with 4.1.1.
I bought 2 of these for my daughters. 1 was defective. When I took it back, the store didn't have anymore so they sent me to a store in another city.
I ended up with one running 4.0.4 and one running 4.1.1.
Click to expand...
Click to collapse
PS:The 4.1.1 that came preloaded is UECLK7.
It can be found here...
http://androidjinn.com/how-to-install-ueclk7-android-4-1-1-jelly-bean-on-p3113-galaxy-tab-2.html/2
---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------
BuLLitz said:
PS:The 4.1.1 that came preloaded is UECLK7.
It can be found here...
http://androidjinn.com/how-to-install-ueclk7-android-4-1-1-jelly-bean-on-p3113-galaxy-tab-2.html/2
Click to expand...
Click to collapse
Following the instructions there, I can confirm that the versions are the same now. Both of my tablets are 4.1.1. In addition, KIES recognizes it as a valid version.

BuLLitz said:
PS:The 4.1.1 that came preloaded is UECLK7.
Following the instructions there, I can confirm that the versions are the same now. Both of my tablets are 4.1.1. In addition, KIES recognizes it as a valid version.
Click to expand...
Click to collapse
The update was officially pushed out today through Kies.
Sent from my crack smoking SGH-i777

well now
I used this and it worked quite well, but now the drivers won't install right when I plug it into my computer.
any suggestions?
thanks.

Re-enable debugging.

ROCK ON! Nice guide!!! I was on JB4.1.1, but, IMO, not good. i rolled back to 4.0.4

ugh
Thepooch said:
Re-enable debugging.
Click to expand...
Click to collapse
Not only can I not install drivers, I can't find the debugging either.
I'm not totally retarded, but I'm starting to feel like it

[Q] Flashing Stock Rom

I'm currently running CM9 on my tab 8.9, and while I'm generally happy with it, now Samsung have (finally!) released stock ICS for the 8.9, I'm tempted to just install this and be done with it (I'd also likely get a working camera!)
As I can't flash using Kies, I'm going to use Odin. I've downloaded the stock rom from SamFirmware, but just want to check on the process for flashing a stock rom using Odin.
I assume I just click PDA, select the .md5 file, and make sure 'Auto Reboot' is checked, but do I need to do anything else in Odin to make sure this works ok?

{
"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"
}
Jusy like this picture and click start....

Finally got round to trying this (! Better late than never).
Using Odin 1.85, the download seemed to work ok, and completed with no errors. The tab then rebooted, and after some screen flashing, the Samsung boot screen appeared, then the logo (which started pulsing). I then left it, and left it, and left it, but I just get the logo flashing on the screen, and it doesn't get any further.
I reset the tab, went back into Download mode, then tried again. Odin completed the download (again), the tab rebooted, but the same thing happened.
Am I meant to clear the cache using this method? I did have CMR 5.5.0.4/CM9 installed before trying this, but I thought this ROM overwrites everything and reverts it back to stock.

tman24 said:
Finally got round to trying this (! Better late than never).
Using Odin 1.85, the download seemed to work ok, and completed with no errors. The tab then rebooted, and after some screen flashing, the Samsung boot screen appeared, then the logo (which started pulsing). I then left it, and left it, and left it, but I just get the logo flashing on the screen, and it doesn't get any further.
I reset the tab, went back into Download mode, then tried again. Odin completed the download (again), the tab rebooted, but the same thing happened.
Am I meant to clear the cache using this method? I did have CMR 5.5.0.4/CM9 installed before trying this, but I thought this ROM overwrites everything and reverts it back to stock.
Click to expand...
Click to collapse
I had the same problem, I cleared CACHE and it worked...

kosmepe said:
I had the same problem, I cleared CACHE and it worked...
Click to expand...
Click to collapse
Ok, thanks. Took your advise, and cleared the cache (had to re-install CWMR first though). I then used Odin to re-install the latest ICS from Samsung, which installed ok this time.
One problem though, when you put the tab to sleep, then resume (using the power button), the screen just goes totally corrupt and unreadable. You can see something is happening on the screen to key presses, but you have to power off using the button. From a cold boot, everything is fine. It's just when you sleep/resume by the looks of it!

tman24 said:
Ok, thanks. Took your advise, and cleared the cache (had to re-install CWMR first though). I then used Odin to re-install the latest ICS from Samsung, which installed ok this time.
One problem though, when you put the tab to sleep, then resume (using the power button), the screen just goes totally corrupt and unreadable. You can see something is happening on the screen to key presses, but you have to power off using the button. From a cold boot, everything is fine. It's just when you sleep/resume by the looks of it!
Click to expand...
Click to collapse
This is a problem others have experienced. Look at the stickies in this section, All 8.9 questions, last few posts.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

jd1639 said:
This is a problem others have experienced. Look at the stickies in this section, All 8.9 questions, last few posts.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Mmmm. Being in the UK, I first reset everything, then installed XXKJ4 (3.2). This went fine, and a quick test with the suspend/resume showed no screen corruption. I then did the reset/cache wipe, and installed EULPO (4.04). This went fine, but a quick suspend/resume test showed the same corruption. As EULA3 is for the US only, I think I did the right thing.
I'm inclined to try re-flashing XXKJ4, and see if Kies updates it ok.

tman24 said:
Mmmm. Being in the UK, I first reset everything, then installed XXKJ4 (3.2). This went fine, and a quick test with the suspend/resume showed no screen corruption. I then did the reset/cache wipe, and installed EULPO (4.04). This went fine, but a quick suspend/resume test showed the same corruption. As EULA3 is for the US only, I think I did the right thing.
I'm inclined to try re-flashing XXKJ4, and see if Kies updates it ok.
Click to expand...
Click to collapse
Ok, getting a bit frustrated now. From a stock 3.2 build (with no screen corruption problems), I just did an ICS update from Kies, which worked ok, but STILL had the corruption issue when resuming from sleep!

tman24 said:
Ok, getting a bit frustrated now. From a stock 3.2 build (with no screen corruption problems), I just did an ICS update from Kies, which worked ok, but STILL had the corruption issue when resuming from sleep!
Click to expand...
Click to collapse
Google "tab 8.9 p7300 terribly messed up xda" there's a fix for the boot loader.
Sent from the short bus

...
---------- Post added at 12:35 PM ---------- Previous post was at 12:27 PM ----------
try to flash the ICS bootloader first

jd1639 said:
Google "tab 8.9 p7300 terribly messed up xda" there's a fix for the boot loader.
Sent from the short bus
Click to expand...
Click to collapse
Still working on this if you can believe it!
According to the thread, people who've experienced this say that flashing the stock 3.2 ROM (EULA3), followed by ICS fixes the problem. As I said though, this is a UK model P7310, so I tried flashing the UK 3.2 ROM (XXKJ4) followed by UK ICS (EULPO). I think EULA3 is the US 3.2 ROM, so will there be a problem flashing a UK 7310 with this ROM, and afterwards will I have to flash the US ICS ROM, or can I still use the UK ROM.
The solution sounded simple, but I'm guessing these are all US based forums.

carmobileproject said:
...
---------- Post added at 12:35 PM ---------- Previous post was at 12:27 PM ----------
try to flash the ICS bootloader first
Click to expand...
Click to collapse
Thanks. Where do I get this?
R u saying that I should install HC 3.2, then the ICS Bootloader, then ICS full? Odin's got the option to install a bootloader, but I wouldn't know which one to use or where to get it, unless you mean CWM, but this doesn't have a bootloader file in the archive.
Getting desperate!

I think you have to extract the bootloader.bin out of the correct hc stock Rom. If I remember the Rom was for the Hong Kong rom
I don't know if this will work or will brick your device but out of curiosity I downloaded the P7300 HC rom and extracted the bootloader.cin. You can find it at http:\\d-h.st/8tF
Sent from the short bus

tman24 said:
...One problem though, when you put the tab to sleep, then resume (using the power button), the screen just goes totally corrupt and unreadable. You can see something is happening on the screen to key presses, but you have to power off using the button. From a cold boot, everything is fine. It's just when you sleep/resume by the looks of it!
Click to expand...
Click to collapse
I'm having the same issue. I'm in New Zealand, my guess is that the NZ firmware is based on the UK one.
1) Flashed firmware using odin
2) Wouldn't boot, got stuck at 'Samsung' load screen (the one that kind of pulses)
2) Installed Clock Work Mod recovery mode using odin
3) Booted to recovery mode
4) Reset to factory defaults
When coming out of power save mode the screen is garbled. I've read an earlier post about clearing the cache, do you mean the option in CWM called "wipe cache partition'?
Thanks in advance.

There have been others with the garbled screen issue. Search kalt kaffe and bootloader.
Sent from the long bus, I got mainstreamed

jd1639 said:
There have been others with the garbled screen issue. Search kalt kaffe and bootloader.
Sent from the long bus, I got mainstreamed
Click to expand...
Click to collapse
It must be a bootloader problem. I've tried every combination now, even now I'm running CWM 6.0.0.8 and AOSP 4.1.2, and while everything installs and runs ok, I STILL get the garbled screen after resuming from sleep. Just trying to search the CM10 thread for bootloader, but search is currently down.
I'm just concerned that flashing the bootloader stands a real chance of bricking the tab, but I'm hoping if the loader works on CM10 it will work on AOSP.

I found a mention to it on page 109 of the thread: http://forum.xda-developers.com/showthread.php?t=1777398&page=109
I just found it in the FAQ here: http://forum.xda-developers.com/showthread.php?p=31771837#post31771837
Which links to this page: http://forum.xda-developers.com/showthread.php?t=1867124
"by now several people have confirmed that flashing the P7310UELA3 is a working solution to screen flickering after resume from standby. (Flash the UELA3 using Odin, then flash again the ROM you really want to run)"
Let me know how it goes, I'm out of time right now.

Wild_Qwerty said:
I found a mention to it on page 109 of the thread: http://forum.xda-developers.com/showthread.php?t=1777398&page=109
I just found it in the FAQ here: http://forum.xda-developers.com/showthread.php?p=31771837#post31771837
Which links to this page: http://forum.xda-developers.com/showthread.php?t=1867124
"by now several people have confirmed that flashing the P7310UELA3 is a working solution to screen flickering after resume from standby. (Flash the UELA3 using Odin, then flash again the ROM you really want to run)"
Let me know how it goes, I'm out of time right now.
Click to expand...
Click to collapse
Jeez, I love this forum. There are some great people here. Thanks to suggestions, I finally have a fully working tab 8.9, that you can put to sleep and wake up without any garbled screen. This is a UK spec 8.9, so I've been very careful on what I flashed
Stock HC always worked fine, but compared to ICS/JB, it's horrible. I got fed up with waiting for Samsung to release ICS for the tab, so tried flashing CM10, but had big problems. Eventually I got CM9 working ok (using CMR5), but this had bugs, and wasn't reliable. Then ICS was released properly, but after flashing this using Odin, I got the garbled screen problem. I went back to stock HC, and this worked fine. Tried re-flashing ICS using Kies AND Odin, but garbled screen. Tried ASOP JB, but still garbled screen!!!!!
Eventually, having nothing to lose, I flashed UELA3 as suggested, but on reboot this went into a boot loop at the Samsung loading screen. Tried re-flashing 3 times (with clear/wipe cache), but no change, BUT, EULA3 does install a new bootloader (I could see this during the Odin flash). So, I then re-flashed stock ICS, and bam, it works.
So, you were right, EULA3, despite the fact it doesn't fully load, was enough to install the correct bootloader, then flashing XEULPO ICS on top fixed the problem. ICS may not be quite as slick as JB, but it's not far behind. Guess we'll never see a Samsung JB for this tab, even though it's easily capable of running it, but for now, I'm ok with this.

Thanks for reporting back. It'll help the next person.
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round