Database Info

[FROYO-ODIN] Leak USCC Mesmerize Froyo EA11 Stock + Root

So here's what Samsung has been sitting on for the last few months..
{
"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"
}
I present to you an 'official' build including the kernel, radio, and full-blown froyo tastiness, for the USCC Samsung Mesmerize. Pre-rooted for your convenience, just download and flash with the latest version of ODIN. These are stock images plus root so your phone will function as if you just turned it on for the first time, albeit with a finger that magically instills root powers into any device you touch..
README
Step 0.5: I recommend disabling the Voodoo Lagfix before doing any of this. You need your sdcard partitioned normally. Let me repeat: Disable the Voodoo Lagfix if you are using a Voodoo kernel prior to flashing the Odin files.
Step 1
Download ODIN here: Odin v1.3
Step 2
Install the Samsung USB drivers: 64bit | 32bit
Step 3
WARNING: These files are for the USCC Samsung Mesmerize. Do NOT flash these to another device.
Download the ODIN package: USCC Froyo [ODIN]
Step 4
Unzip the ODIN package and you will find two files. One ends in tar.md5 This is the ODIN package that you will flash to your device. The other file ends in .pit. This file is a configuration file of sorts for your device. It is not needed unless you have trouble.
Step 5
Backup the data on your device. You are going to lose it.
Step 5.5
Backup the data on your device. It is not coming back.
Step 6
Open up ODIN. Load the tar.md5 file into the PDA section.
Step 7
Put your phone into download mode. The easiest way to do this is to issue the "reboot download" command from adb. If you don't have adb installed, simply download the attached adb.zip. Extract the files to a new folder and open up a command prompt in that folder by holding down shift then right-clicking inside the folder window. There will be a menu entry "Open command window here". Select it. Then, type "adb reboot download" (no quotes) and press enter. If this fails you need to turn on USB debugging on your device and try again. Settings>Applications>Development:Enable USB Debugging
For more information on ADB I strongly recommend reading the "ADB Workshop" by Adrynalyne and Captainkrtek.
Alternatively, you can power your phone off. Hold down the "Volume Down" button and plug in the USB cable (make sure the other end is plugged into the computer first).
If all is successful, you should see a yellow triangle around a hard-working android and the words 'Downloading... Do not turn off target' (also in yellow).
*Step 8*
Once your phone is in download mode it should pop up in ODIN. Once ODIN has found the device, make sure you have the tar.md5 file loaded in PDA from step 6, and press START! ODIN will begin flashing your device. After a few minutes it should reboot into recovery, flash some text, and reboot again into Froyo! If all goes well, the white box in ODIN will turn green (=
Troubleshooting
Lag or low quadrant score: re-flash using the .pit file
Odin doesn't recognize your phone: install the Samsung USB drivers and reboot
Odin says checksum failed: re-download package and try again
Looking Forward
That's all! You will need to setup your phone again like you did when you first got it. While annoying, it's worth it! Once you have everything setup you're good to go. Check back periodically for Froyo ROMs and customizations. There are already some on the way and many more coming since Froyo has been out for awhile -_-
Links:
<--USCC Froyo EA11 ODIN Stock + Root
http://www.megaupload.com/?d=WG39PL2H <--USCC Froyo EA11 ODIN Stock + Root Mirror phidelt82
http://www.megaupload.com/?d=XRDDYL75 <--USCC Froyo EA11 ODIN Stock + Root + Recovery Mirror phidelt82
http://rom2.galaxysense.com/mesmerize/USCC_Froyo_Root_Recovery_EA11.zip <--USCC Froyo EA11 ODIN Stock + Root + Recovery
(I will add more versions as they become available..)
Credits:
<phidelt82 | donate> hosting, help, and testing (this guy will flash anything I throw at him)
<CaptainKrtek | donate> HUGE thanks to CaptainKretk for offering to host these on his server. However, he does not have magical bandwidth that doesn't cost anything.. so if you appreciate his bandwidth, please help him out. I have.
<jt11134 | donate> Thank jt for the <2e> recovery that's in the integrated package rom + recovery package. Plus, he's the master behind much of the Fascinate AOSP progress.
more to come
Finally, I put some time into fixing this up for you all. If you appreciate my time, buy me a beer or two (=
<dcow | donate>

Thank you!!!! I will test when I get home from work today.

Is it safe to use wireless tethering some one said it wasn't on the fascinate

johnboyjr said:
Is it safe to use wireless tethering some one said it wasn't on the fascinate
Click to expand...
Click to collapse
Not sure. It's probably just as unsafe as using wireless tethering without a contract anyway. I'll look into it though.

Thanks dude, you and Keith are awesome. I will try these ASAP.
Sent from my SCH-I500 using Tapatalk

So with this new froyo ROM (I'm so excited!) There's currently no voodoo kernel that will work with this on the mesmerize, right? I don't care, I'm flashing it as soon as I can, Im just curious.
Sent from my SCH-I500 using XDA App

davidbruington said:
So with this new froyo ROM (I'm so excited!) There's currently no voodoo kernel that will work with this on the mesmerize, right? I don't care, I'm flashing it as soon as I can, Im just curious.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
No voodoo kernel yet. That will come in time. Hopefully I'll get a ROM built today. Then we will have themes coming.

as soon as i see voodoo for this...im on it like white on rice!!!

BakedTator said:
as soon as i see voodoo for this...im on it like white on rice!!!
Click to expand...
Click to collapse
It works 100% fine without voodoo.. you're missing out. And it's not like you can't add voodoo later once we get it ready (=

rooting
are we able to root froyo yet? can we just load up z4mod?

dfgas said:
are we able to root froyo yet? can we just load up z4mod?
Click to expand...
Click to collapse
ReREAD the First POST

It comes pre-rooted Thank the sweet devs for saving you an extra headache

elijahblake said:
ReREAD the First POST
Click to expand...
Click to collapse
completely sorry about that......

dfgas said:
are we able to root froyo yet? can we just load up z4mod?
Click to expand...
Click to collapse
It's pre-rooted.
YAY!

im flashing now you can use one click lag fix for the time being it will help but i wouldnt use full time as it messes with memory

You just made my day!
Sent from my SCH-I500 using XDA App

voodoo kernel
there is a test voodoo kernel out that came with the alpha build of froyo does any one know if this will work ? im going to try it out ill report back

I have voodoo kernel will this work.just asking as this is new too me.thanks

there is a test voodoo kernel out that came with the alpha build of froyo does any one know if this will work ? im going to try it out ill report back
Click to expand...
Click to collapse
Please read the first post (= This comes with the 2.6.32.9 kernel (the 2.2 one we've been trying to get our hands on forever) No hacked up alpha kernel needed..

phidelt82 said:
No voodoo kernel yet. That will come in time. Hopefully I'll get a ROM built today. Then we will have themes coming.
Click to expand...
Click to collapse
You are awesome man, thank you so much for all your hard work and your time. I'm flashing this as soon as I get my lunch break!
Sent from my SCH-I500 using XDA App

THIS THREAD IS CLOSED Due to GTG465x's fine job removing the RAINBOWS!

Infuse Version 2 BETA 2 and BETA 3 roms - Clockworkmod Kernel Setup
(Fixes Video Problems in Beta 2 & Beta 3 and ClockworkMod Recovery too)​
#1: Download "sgs kernel flasher" (free) from market
#2: Download "CWM-community-kernel-v8.zip" from here: http://www.multiupload.com/1E3AWIQYAA
#3: Copy "CWM-community-kernel-v8.zip" into /mnt/sdcard
/sgs-kernel-flasher folder
#4: Open sgs kernel flasher and select "backup kernel" you will
see the dated filename of the saved file on bottom of screen
Now you have 2 kernels to choose from, the "CWM-community-kernel-v8.zip" and the kernel you backed up using sgs kernel flasher.
For normal operation of Infuse v2 beta 2 or beta 3 your sgs backed up kernel is what you want to select and use.
If you want to do anything like backup or restore in clockworkmod recovery simply open sgs kernel flasher and click "choose kernel".
Then click "CWM-community-kernel-v8.zip" after this step, press the power button and select "recovery".
The phone will reboot into red clockworkmod recovery menu without any rainbows so you can use all functions and features of clockworkmod recovery.
When you are done using clockworkmod recovery restart phone, open sgs kernel flasher and click "choose kernel" now click the kernel you have backed up.
Reboot the phone again and you will be in normal Infuse v2 beta 2 or beta 3 "rainbow mode" and you are back where you started from.
NOTICE: If you are stuck on a rainbow screen after trying to go into clockworkmod recovery you will need to download the "odin no rainbow" kernel and put the phone in download mode and flash the odin kernel.
Here is the link for the Odin flash no rainbow kernel you need.
http://www.multiupload.com/751NVU5V55
After flashing with Odin restart the phone then follow all the instructions above starting at #1
Have a great day,
Enjoy!
{
"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"
}
Please don't forget to give me a big THANKS if reading this was helpful to you! ​

Thats how I did it.....

You can just use odin
Sent from my SAMSUNG-SGH-I997R using XDA App

This is great. I have a mac, so odin and heimdall doesn't work. This should help me upgrade to beta 2
Sent from my SAMSUNG-SGH-I997R using XDA App

re: odin kernels
Auto-Android said:
You can just use odin
Sent from my SAMSUNG-SGH-I997R using XDA App
Click to expand...
Click to collapse
yes I know we can use odin but odin requires a computer with windows and samsung usb drivers..
A lot of people do some of these things when they do not have a computer handy, or they are not home and do not want to install usb drivers in other peoples computers or some people simply don't want to mess with the computer if they can do some of these things without one.
There has been much talk about this ever since Infuse v2 beta 1 and 2 came out and there were a lot of misunderstandings about the process.
Anyway, have a great day, Enjoy!

I find that the CWM kernel has less rainbows with daily use anyway. And video playback is borked with both anyway, so I just stick with the CWM kernel.

Will this work with the kernel being packaged with odin like it is???

kernels and rainbows
halfnelson117 said:
I find that the CWM kernel has less rainbows with daily use anyway. And video playback is borked with both anyway, so I just stick with the CWM kernel.
Click to expand...
Click to collapse
if your video playback is broke with both kernels then you have done something wrong for sure during flashing of Infuse v2 beta 1 or 2.
The only way to fix it is to go back to froyo rom be sure its rooted and has 3e recovery then go into recovery mode using power button selecting recovery then flash the infuse v2 beta 2 rom with the RED cwm recovery menu.
After its done flashing select "advanced" in cwm recovery menu and select "wipe-factory reset" when thats done simply click on "reboot" and you will see rainbows, wait until the phone completely boots and ready to use.
Then reboot the phone again and leave it alone for 15 minutes more or less and after that it will only have rainbows during boot/reboot and the video playback/preview screen/gallery and everything else in the phone will NOT have rainbows at all.
Hope this helps! if so give me a BIG THANKS!

re: working with odin
jaydawgg said:
Will this work with the kernel being packaged with odin like it is???
Click to expand...
Click to collapse
Nope, this method will not work with the odin kernels cause odin kernels are TAR files and cwm kernels are ZIP files............
Good luck!

Misterjunky said:
yes I know we can use odin but odin requires a computer with windows and samsung usb drivers..
A lot of people do some of these things when they do not have a computer handy, or they are not home and do not want to install usb drivers in other peoples computers or some people simply don't want to mess with the computer if they can do some of these things without one.
There has been much talk about this ever since Infuse v2 beta 1 and 2 came out and there were a lot of misunderstandings about the process.
Anyway, have a great day, Enjoy!
Click to expand...
Click to collapse
oh yes i see what you mean

Misterjunky said:
Nope, this method will not work with the odin kernels cause odin kernels are TAR files and cwm kernels are ZIP files............
Good luck!
Click to expand...
Click to collapse
What i mean to say is that the OP gives a kernel link witch is 15 mb and has odin in the archive i dont think that will flash.
Will it??
I thought kernels were about 7 mb

Excellent sleuthing, Watson! This method worked for me as well!
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

I don't think this will work either. It is just the file that was posted earlier. tihe the following listed inside zip:
"/zImage_for_heimdall_users/zImage"
"Odin3_v1.81.exe"
"PDA_Infused_Gingerbread_Kernel_v1_CWM.tar.md5"

yo gtg.......i just flashed this kernal.no rainbow at all after flashing.but in camera view is all black.i can take pics.but cant see what im taking pic of.
i did flash that bootloader dump from rogers infuse.if that has anything to do with it.

mintu123 said:
yo gtg.......i just flashed this kernal.no rainbow at all after flashing.but in camera view is all black.i can take pics.but cant see what im taking pic of.
i did flash that bootloader dump from rogers infuse.if that has anything to do with it.
Click to expand...
Click to collapse
Yeah if you flash the CWM kernel it fixes rainbows but breaks video and cam viewfinder. Flash other kernel and rainbows, but working video and cam viewfinder.

but netflix streams fine.what if reinstall camera apk and youtube apk. will that fix it

Question. I do not see the sgs folder anywhere. Am I supposed to create it? I downloaded the app from the market. But I do not see the folder you mention.
Sent from my rooted infuse flashed with infused!

mintu123 said:
but netflix streams fine.what if reinstall camera apk and youtube apk. will that fix it
Click to expand...
Click to collapse
Nope. Gingerbread bootloaders will fix it.

Ddot196 said:
Question. I do not see the sgs folder anywhere. Am I supposed to create it? I downloaded the app from the market. But I do not see the folder you mention.
Sent from my rooted infuse flashed with infused!
Click to expand...
Click to collapse
Just back up once and it will be created.

re: kernel size
jaydawgg said:
What i mean to say is that the OP gives a kernel link witch is 15 mb and has odin in the archive i dont think that will flash.
Will it??
I thought kernels were about 7 mb
Click to expand...
Click to collapse
They usually are about 7mb but this must have something special in it to make it that large.
You may want to ask GTG why its as large as it is........
I do know it works 100% though
Have a great day.

[Q] What do I need to get Heimdall to work? (Mac)

I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.

i dont know about the mac version but there should be a readme in there for installation. also i think the mac needs codeless kext installed. should be outlined in the readme but couldnt tell you for sure.

I followed the instructions as best as I could understand. The UI pops up but refuses to flash or even recognize my phone.

re: flashing rom
tight686 said:
I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.
Click to expand...
Click to collapse
Since you have a mac it would be a lot easier for you to flash a
clockworkmod type custom rom.
You must have clockworkmod recovery to be able to do this.
If you are running stock rom and already have clockworkmod
recovery in your phone then then you can BACKUP your stock
rom with clockworkmod and then flash a new custom rom
as long as its a clockworkmod rom zipfile.
Most all of these custom roms you see here on xda are all
clockworkmod types (zipfiles) which do NOT need ODIN
or Heimdall at all.
But you do need to have a usb card reader if your your
computer is not reconizing your samsung phone as an external
USB drive.
If your Mac computer does reconize your phone as a external
USB device then you do not need to remove the microSD card
and you do not need a card reader.
I am sure you know how to use a usb card reader so I will not
go into that now.
Here is the link to the most popular custom rom for Infuse
which is the type you need. (clockworkmod flash)
http://forum.xda-developers.com/showthread.php?t=1195571
Follow the easy step by step instructions to a "T" if you
don't want to start all over and have to do it again.
{
"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"
}
Good Luck,
Enjoy!
Please don't forget to give me a big THANKS if this post was worthwhile reading!

----------

Thanks everyone.
My main concern is that I'm running Gingerbread v2 b2. When we get the official bootloaders will I need to flash through Odin/Heimdall? Otherwise I'm fine.

tight686 said:
Thanks everyone.
My main concern is that I'm running Gingerbread v2 b2. When we get the official bootloaders will I need to flash through Odin/Heimdall? Otherwise I'm fine.
Click to expand...
Click to collapse
You are already on a rooted rom. Just get sgs lernel flasher and flash a "rainbow fix kernel." But id try to get heimdall working. it is super easy on linux. I love the debian package system.
If it doesnt see the device it sounds like an issue with that "codeless kext" which is described as being like a driver. that is unless samsung dropped the ball on the boot loaders again. the bootloaders in the odin oneclick packages for the galaxy s would prevent the device from being visable on a mac in download mode. later versions had this fixed. if i had a mac id help. i think the mac is a great system but i just dont know enough about your problem.
there is always the bootcamp or virtual machine options. if you need windows maybe i can help out if you pm me. or yu can do a quick install of mint or ubuntu which is not only more similar to mac than windows but with no need for drivers and the debian packages is easier to install heimdall on than odin is in windows.
or maybe you can contact the developers of heimdall.

tight686 said:
I have tried numerous times to get it to flash to my phone. Thankfully I don't need it yet but as of now I have no backup plan if I ever had to return to stock. The best I have got is "Failed to detect compatible device."
If someone would be kind enough to, at the least, give me a checklist or links to what all I need to get this thing running I'd really appreciate it.
Running Mac OS X Lion if it helps.
Click to expand...
Click to collapse
what version of heimdall did you download? i ask because it seems 1.3 wants a firmware.xml file that specifies compatible devices, could be an issue of it looking for that file. i still use v1.1.1, i just updated to 1.3 but dislike it and am going back, will see if 1.2 is compatable with the 1.1.1 frontend because it doesnt appear to have a frontend package.
edit:
yes v1.2.0 comandline seems to work with 1.1.1 frontend, install 1.1.1 and then you may upgrade to 1.2 (atleast that's how it works under linux)

Ok so I can use VMWare to load another OS on my Mac.
Any recommended distros to use this Debian package? So many flavors of Linux.
Lastly, can you please link me to past versions of Heimdall? I can only find the most recent.

tight686 said:
Ok so I can use VMWare to load another OS on my Mac.
Any recommended distros to use this Debian package? So many flavors of Linux.
Lastly, can you please link me to past versions of Heimdall? I can only find the most recent.
Click to expand...
Click to collapse
most use ubuntu. debian packages but there own repositories that are less likely to provide unstable updates to break your system.

[UVKF1] Back-To-Stock Heimdall One-Click

Introduction:
This package will totally reset your t959v GalaxyS 4G to UVKF1 . It is a total open-source alternative to Odin. For windows, The Open-Source libUSB Heimdall drivers are different from from the closed source and proprietary Samsung drivers, so you must install drivers if prompted. Linux and Mac are standard installs.
This package includes:
Repartitioning: Repartition to stock KF1
Reloading: IBL/PBL, PARAM, SBL, SBL2, Kernel, Recovery, FactoryFS, Data, and modem
formatting:Cache and DBdata
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
SDCard (where your pictures are stored)
You may use this code to reformat the Data and SDCard *2767*3855# There is no way to do this from Download Mode. The code will leave the EFS untouched.
Download:
Download Total Stock UVKF1
{
"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"
}
One-Click Package Size: 227.8MB
Instructions:
Get the latest version of java here: http://java.com/en/download/installed.jsp
Put your phone into "Download Mode"
Run the program once, and if it does not work, then check the "Flash Bootloaders" checkbox and flash again
Your device will end up as it came from the factory. You will be asked to set your device up again.
Please note at the time of this post it will be 25 minutes for the package to be uploaded to the server.

Great work!

thanks adam for letting them have a 1 click sollution back to stock

krylon360 said:
Adam,
The KF series contained faulty bootloaders. Were these replaced in your package?
Click to expand...
Click to collapse
It works just fine. I verified this package on a device. I dont know where you got your version, but the one on sammobile.com is verified operational by me last night.
If you do not repartition while flashing bootloaders than you can have problems. This package is designed for a total restoration. Its likely you were using a package that some guy created and he didnt know what he was doing.
Im requesting that all comments pertaining to my package having bad bootloaders except this one be removed. This package is fine.

AdamOutler said:
It works just fine. I verified this package on a device. I dont know where you got your version, but the one on sammobile.com is verified operational by me last night.
If you do not repartition while flashing bootloaders than you can have problems. This package is designed for a total restoration. Its likely you were using a package that some guy created and he didnt know what he was doing.
Im requesting that all comments pertaining to my package having bad bootloaders except this one be removed. This package is fine.
Click to expand...
Click to collapse
He acrually got it off sammy firmware awhile ago

RaverX3X said:
He acrually got it off sammy firmware awhile ago
Click to expand...
Click to collapse
And he packaged it improperly. He either forgot to package the SBL or PBL, or he forgot to repartition. This package works. The PBL and SBL were flashed sucessfully.
Not everyone knows how to properly package a firmware flash. This flash is verified.
Stop the off-topic banter.

Sorry for asking, but does this also flash gingerbread bootloaders?
Sent from my rockin' Galaxy S 4G using XDA Premium App

TheKucho said:
Sorry for asking, but does this also flash gingerbread bootloaders?
Sent from my rockin' Galaxy S 4G using XDA Premium App
Click to expand...
Click to collapse
Yes. As stated in the first post.

computer wont sd card on phone now
i used this to unbrick my phone but now it wont let my pc recognize the files on it. i plugged it into samsung mini kies and it recognized it. during installation it said it didnt work so i took out the battery and put it back in and then a screen with a phone and tiny computer popped up so i plugged it back into the heimdall program and it started working. it seems everything else is fine plus I guess it has gingerbread now but luckily i had backed up all my games 2 days before on the pc. plus the games are on the sd card but not on the phone. should I redo the heimdall program again? when i hit mass storage on the phone it makes the beep sound like the files will come up but nothing happens

robertneusch said:
i used this to unbrick my phone but now it wont let my pc recognize the files on it. i plugged it into samsung mini kies and it recognized it. during installation it said it didnt work so i took out the battery and put it back in and then a screen with a phone and tiny computer popped up so i plugged it back into the heimdall program and it started working. it seems everything else is fine plus I guess it has gingerbread now but luckily i had backed up all my games 2 days before on the pc. plus the games are on the sd card but not on the phone. should I redo the heimdall program again? when i hit mass storage on the phone it makes the beep sound like the files will come up but nothing happens
Click to expand...
Click to collapse
I'm not familiar with all aspects of this device. You may want to ask this question in Q&A.

i got it to work by hitting mass storage then plugging it in sorry

robertneusch said:
i used this to unbrick my phone but now it wont let my pc recognize the files on it. i plugged it into samsung mini kies and it recognized it. during installation it said it didnt work so i took out the battery and put it back in and then a screen with a phone and tiny computer popped up so i plugged it back into the heimdall program and it started working. it seems everything else is fine plus I guess it has gingerbread now but luckily i had backed up all my games 2 days before on the pc. plus the games are on the sd card but not on the phone. should I redo the heimdall program again? when i hit mass storage on the phone it makes the beep sound like the files will come up but nothing happens
Click to expand...
Click to collapse
Try following my gb starter pack guide. One of the issues of the earlier GB leaks (Anything earlier than KGX) was that the phone wouldn't recognize the SD card.

FBis251 said:
Try following my gb starter pack guide. One of the issues of the earlier GB leaks (Anything earlier than KGX) was that the phone wouldn't recognize the SD card.
Click to expand...
Click to collapse
He said he got it to work.

AdamOutler said:
He said he got it to work.
Click to expand...
Click to collapse
Should've clicked the "next page" link.

Now that official kj6 is out, could we update the heimdall one-click with this rom?

bhundven said:
Now that official kj6 is out, could we update the heimdall one-click with this rom?
Click to expand...
Click to collapse
Sure. Why don't you do it? All the information you need is here:
[Release] Heimdall One-Click - ROM Packaging and Distribution System

AdamOutler said:
Sure. Why don't you do it? All the information you need is here:
[Release] Heimdall One-Click - ROM Packaging and Distribution System
Click to expand...
Click to collapse
Ah, I was unaware of that page! Thanks again, Adam! I don't have time right now, but I'll get something posted soon.

THanks
Hey thanks adam this helps alot

My phone seems to be working ok except that I cant seem to be able to reboot into recovery by pressing the volume up and power buttons now. Am I doing something wrong

robertneusch said:
My phone seems to be working ok except that I cant seem to be able to reboot into recovery by pressing the volume up and power buttons now. Am I doing something wrong
Click to expand...
Click to collapse
Try removing the battery first. I don't know what's up with the Gingerbread bootloaders.

How to install January 5th patch while using custom recovery and root on Google Pixel

Okay, I am sure a lot of you already know how to do this to your Pixel. Some of us do not, and I was one of them. I am the standard noob that just followed Youtube videos to unlock previous carrier locked phones. I am now enjoying this Google Pixel that is unlocked!
So if you are reading this thread, hopefully there isn't another one just like this (yes I looked).
To start off, if you are in here reading this, you have unlocked your bootloader and installed a custom recovery such as TWRP and rooted. Now you are seeing that you need to update your phone with the latest security patch. You try and you try and you can't do it. Even when you unroot it will still fail to update, or at least it did for me. Here I will explain what I went through and did to obtain the latest update. (Warning, you will loose root and custom recovery). THIS IS INTENDED FOR THE GOOGLE STORE PURCHASED PHONES
Lets get this started finally.....
Go into your developer options and enable usb debugging.
Download the newly released package file from google that has fastboot and ADB without needing android SDK.
DOWNLOAD or read about it HERE
Now you will need to download the Factory Image for you device
Find your correct device HERE
Make sure you choose the correct device and correct update, for me I downloaded the "7.1.1 (NMF26U, Jan 2017)" for my Pixel. Also a USA phone.
So now you have the adb fastboot binary package and your factory image. You will need to extract the platform-tools-latest-windows.zip and open the folder and you will see another folder, open it and now you will see a bunch of files. Now open another window and extract your factory image. Once it is done, open the folder until you see the files. Now copy these into the Platform tools folder in the directory with the fastboot.
Once this is done your folder should look like this:
{
"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"
}
Now you will want to right click "flash-all" and click edit. It will open notepad and show the contents of the batch file. You can hit Ctrl+F and type in -w in the search and hit okay, or you can look for it without search (it is near the bottom). Once you find it, just delete the "-w" and save the file. Make sure to keep it as the batch file or this won't work.
Once this is done, in the folder that is shown above, click a blank area in the folder so no file is highlighted. Now hold shift and right click, it will come up with a dialog saying open command window here, click that.
Now we are going to reboot the phone into bootloader mode. In the command window, type everything that is underlined below
adb reboot bootloader
Now your phone should have booted into the bootloader screen or it should be asking for USB rights to use adb. If it asks for permission, hit okay and re run the code above and your phone should reboot.
Once you are in the bootloader screen you will need to do is run the flash-all.bat. It will load and go though some text on the CMD window it brings up. It will say some files are missing, which is fine. But if it fails it will tell you that it did. You can also tell by rebooting the phone or click "start" in the bootloader mode and then checking for OTA updates. It should say January 5th patch installed.
Now you can go through and install your custom recovery again and re root. Which takes no time at all and I am sure someone on here has posted before. If not, let me know and I can make a tutorial over it.
Note: I am very sorry for the bad layout and extended write up. First time ever doing this and I am hoping to help people. If there are any errors, let me know!

All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.

zelendel said:
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
Click to expand...
Click to collapse
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself

exbtlegends said:
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
Click to expand...
Click to collapse
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.

jrat69 said:
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
Click to expand...
Click to collapse
Not a problem ?

I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.

32BitWhore said:
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
Click to expand...
Click to collapse
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.

This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.

Good work. This is a very minute stuff of removing -w from the batch file. Very handy work.
Sent from my Pixel using Tapatalk

Do you need to reflash stock kernel before removing root/TWRP before flashing?

32BitWhore said:
Do you need to reflash stock kernel before removing root/TWRP before flashing?
Click to expand...
Click to collapse
Flashing the image overwrites anything you customized besides the regular user data and internal storage (with the -w removed). You don't have to remove or reflash anything else before following these instructions.

TCPDump said:
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Click to expand...
Click to collapse
I couldn't side load the update.. TWRP would not load the side load feature.

I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?

km8j said:
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
Click to expand...
Click to collapse
Even when I un rooted mine. I was still failing to get the update.

If you made any changes the the system partition then it will fail and simply unrooting doesn't make the all the changes needed. So if OTA mean anything to you then I would suggest not messing with your device as there is Jo promise that after an OTA you will be able to root again tonight away

jesssiii said:
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
Click to expand...
Click to collapse
I know the past 2 were the same for google pixel and Verizon pixel but I wouldn't assume they are always going to be. I'm sure some of them will be specific at times whenever Verizon decides they wanna mess with them

FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.

SpoiledHeeb said:
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
Click to expand...
Click to collapse
You need SuperSU 2.79 RC3