yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] AdamOutler:
Ah... Yep... another one of those guys in our presence... Didn't bother to read/comprehend the thread... Wants to try to shoot holes in it before it's even come to fruitation..

This may not be the case. In fact there's alot of pressure to lock the bootloaders because of problems in the past. Galaxy devices have been becoming more and more locked down lately if you havn't noticed. According to rumors of those who are close to the source this device will have a locked bootloader.

Did you read the thread? The guy was asking if using the fastboot would work. No, if the fastboot is gone, then there is no chance it will work.

If the bootloader is locked, than replacing it will happen eventually, but it will lead to problems with bricking.

You should know that every modern SoC is capable of booting from USB. Most manufacturers do not allow it in the name of security so they can keep you locked into their services and carriers.

2 months ago 1/3 of the threads in GalaxyS Captivate Q&A and Captivate General were "Black screen brick". They were getting bricked left and right by users who wanted to try to get something extra from their device. The Captivate UnBrickable Mod provided a way for users to get out of this sticky situation on their own. This mod cleaned up that problem.

Trust me, this isn't my first rodeo. http://xdaforums.com/showthread.php?t=1236273 Now get out unless you have something to contribute.
[Samsung Galaxy Nexus] jbrinkley:
I have no business here, but.

There's no way this phone won't be fastboot oem unlock - able.

****, I'll buy you one to tear down if there's an encrypted boot.. There's my contribution to the thread.
[Samsung Galaxy Nexus] jay_993:
HA! that's how confident you are that it won't be locked eh? :)
[Samsung Galaxy Nexus] jbrinkley:
yes I am. I'm confident that it's in the agreement to be a nexus manufacturer. It just wouldn't be a nexus if it was encrypted. Consider all the hype and speculation, people calling it the next dev phone that it should be. And ICS.

Plus, guy's in louisiana.

Maybe I'm wrong and meet the guy, give him a phone and buy him a beer.

If I'm wrong then the nexus name is all shot to hell. No one would care about this phone if so.

I sure wouldn't.

Think about it for a minute, google unveils ICS on a nexus phone. All the hype, the speculation.

Absurd to think they wouldn't follow protocol.
[Samsung Galaxy Nexus] Rebellos:
Then I'm waiting for the GN device from Adam soon. Thanks in advance. :p
[Samsung Galaxy Nexus] jbrinkley:
pass the pipe

far be it from me to say I told you so, but hell, it's the internet, I told you so.
[Samsung Galaxy Nexus] Nitro_123:
Omg. Here as well.........

Adam, you are all over XDA

And, I seriously LIKE IT :D :D
[Samsung Galaxy Nexus] ydaraishy:
Then why is it called an "unbrickable mod" if you can't recover from bootloader issues? OMAP is more than capable of reflashing bootloaders, which is why this Nexus is exciting in that respect.

Of course. But not every SoC provides you with open docs about how to provide the hardware with the correctly formatted bootloader image ...*cough*Qualcomm*cough*...

Gee, if you can't or don't really want to speak about the technical issues here, which, by the way I'm interested in -- which is why the hell I'm asking -- you're right, maybe I won't bother. :rolleyes:
[Samsung Galaxy Nexus] AdamOutler:
Its called unbrickable mod because you don't need to have bootloaders on the device to boot it up. Seriously... GTFO you... you didn't even bother to comprehend what I was telling you in relation to your own words. I quoted your post for a reason.

Right now we have 0 recovery options. Not even JTAG. We don't know if the bootloader will be locked. If it is, and we can figure out enough about the OMAP 4 processor, we can circumvent security measures put in place. If the bootloaders are unlocked, we can recover devices which have damaged fastboot. It happens quite a bit

If you want more information, go start a new thread... but please read the 12 other threads I've started for various devices FIRST. I don't know you, but your lack of reading and disrespect for legitimate research is pissing me off. Go do some reading before you post this crap in here again or go troll another thread. Don't come in here posting that we don't need this. Don't try to explain why it wont work. GTFO until you have something g constructive to add otherwise you're adding difficulty to the already difficult task of hacking a closed source microprocessor.

For all reading this... I don't care if you think it can't be done or have reasons why you wont need it ever... devices which are touted as unbrickable are bricked daily for various reasons. I gaurantee that omeone reading this in the future has a bricked galaxy nexus in their hand and are looking for information and the last thing they want to hear is that it can't be done or its worthless to try. Locked bootloaders or not, this device will be bricked by more than a dozen people who find a way to flash some crazy bootloader. Those people are coming here for theory. They will go to the development platform thread for the hardware mod and they will go to the how-to from then on out.

We may be lucky on this device and the only thing we have to do is figure out in this thread a safe way to dual boot from external sdcard.
[Samsung Galaxy Nexus] ydaraishy:
What are you going to do when you have bootloaders -- that you don't have the source code to -- that may perform hardware-specific initialization that the kernel and levels above that _won't_ do?

Who is saying we don't need this? I'm wondering why we need a hardware specific modification, and what benefits that give us over what is already understood about the hardware and platform?

Gee, I thought people who are interested in mods like this _like_ talking and answering questions about their work.
[Samsung Galaxy Nexus] AdamOutler:
Pleae go do some reading and quit trolling my thread. I've asked you thrice now and I answered your question in my last post.
[Samsung Galaxy Nexus] DontJoinTheDarkSide:
Sounds good, look forward to seeing progress.
[Samsung Galaxy Nexus] hailmary:
bootloader

talking about locked boot loaders--

motorola is one tough bootloader-monger...they say its impossible,but we defied that crap by letting it lock itself off & bypass it by exploiting the 2nd init & make own way of booting the custom rom w/ it.

nothing is impossible to the open mind... locked or unlocked.

i support this project.
[Samsung Galaxy Nexus] AdamOutler:
Grab the GalaxyS2 hack pack here. http://xdaforums.com/showthread.php?t=1316501

This is a compilation of this generations documentation and other materials
[Samsung Galaxy Nexus] Rebellos:
Here is where I come in. We already have 5k OMAP4460 SFRs description. It is all I need (and a lot of time of course) to analyze any low-level code written for that SoC.

When we finally get some test device, believe me or not, but any low-level modification won't be impossible deal. Not like in Exynos4 based devices where few months after release we still don't have CPU manual full SFRs description. (Shame on Samsung)

Nothing is impossible in modding when reverse engineering comes in. It is mainly matter of time, which does often block modding ideas.
[Samsung Galaxy Nexus] Indirect:
Ah Rebellos, you gotta love low level languages. :p Makes reverse engineering fun and challenging. :p
[Samsung Galaxy Nexus] spitefulcheerio:
Seeing how I recently acquired an Infuse to play around with before the release of the Prime and bricked it in the process of Modding for MIUI, I really appreciated having an unbrickable mod. Saved my ass.

I'll contribute however necessary to help this cause
[Samsung Galaxy Nexus] AdamOutler:
Wrong thread. Infuse is a sgs1 style device. The UBM for that device may be ready this week.
[Samsung Galaxy Nexus] Egan:
Hold your horses m8. He was talking how nice it would be to have UBM on the Galaxy Nexus.

Thanks for the effort so far.
[Samsung Galaxy Nexus] AdamOutler:
well, UBM for Infuse 4G is now ready. Just made the plans. http://xdaforums.com/showthread.php?t=1318386
[Samsung Galaxy Nexus] jay_993:
Just out of interest. Why are the devices ie cappy which have ubm don't have ports of wp7 and other oses? Nobody interested in doing it or is it cuz xda don't allow?
[Samsung Galaxy Nexus] AdamOutler:
It would be quite a bit of work to port those OS'. I don't think XDA policy would forbid that, but it would take weeks of work in pure assembly language. Mostly bootloader remapping, some kernel work as well. I do not have the skills to do this.

However, we do have a lot of active development in those forums. They are still booming but approaching end of lifecycle. It would help to get an early start on it. The development cycle of most devices is about 1-2 years. The i9100 is about 6 months old now. Someone send me a device to work with and I can get UBM rocking on the i9100.

I have collected all necessary information. I just need a device to work with. It can be bricked. I have JTAG to recover it. Ill unbrick your device if its dead.
[Samsung Galaxy Nexus] ryohazuki:
Cotulla and DFT did this with the HD2 in terms of making a bootloader that can load wp7 and android

Walking and writing isn't my thing lol
[Samsung Galaxy Nexus] AdamOutler:
They did no such thing. They made an open source OS work on a device. That means you get to work with source code. Each line of source is 10-10000 lines of assembly language. If we had source for wp7 or ios it would not be a ton of work in assembly language. Those guys had android source to work with. Its like the difference between typing the dictionary and typing a dictionary that has been cut, separated and stacked into individual letters.
[Samsung Galaxy Nexus] ryohazuki:
I'm not saying I'm a genius but I kind of know that android is an open source OS and makes porting a bit easier, considering the fact the hardware on the HD2 is very similar to the Nexus One thus making drivers and what not easier to port over. You completely neglected the fact that I said they also have WP7 running on the HD2. So if thats the case...whats the answer to that one? And what is Magldr then? cause as far as I know, Magldr is a custom bootloader.
[Samsung Galaxy Nexus] AdamOutler:
You're telling me they put wp7 on a device designed for wp6? Impossiblé.
[Samsung Galaxy Nexus] synaesthetic:
I think the only reason that WP7 works on the HD2 is because the HD7 is pretty much exactly the same phone.
[Samsung Galaxy Nexus] ryohazuki:
uh...its not impossible. it's been out for awhile now. It's running both WP7 and Android.

That's exactly why. I was just saying in general.
[Samsung Galaxy Nexus] streetster:
The HD2 has had two custom bootloaders written for it: MAGLDR and cLK.

MAGLDR is more advanced as allows Android/WP7, whereas cLK is just for booting Android from NAND but still has some advantages if that's what you want to do.

I imagine having an unbrickable phone when trying to write a custom bootloader would be like running with godmode on your phone :)
[Samsung Galaxy Nexus] ryohazuki:
Yeah i used CLK back on my HD2, ,my fav boot loader
[Samsung Galaxy Nexus] mstrk242:
Keep in mind the hd2 was originally a windows mobile device. There were already drivers to work with. Cotulla made a bootloader that allowed the phone to boot android without loading haret first. Plus they created a kernel and ril-wrapper with no source to reference. Great achievements for sure, but not the same as bringing wp7 to an Android device

Sent from my LG-P999
[Samsung Galaxy Nexus] DontJoinTheDarkSide:
You're all being trolled he was being sarcastic.
[Samsung Galaxy Nexus] streetster:
Hmm I disagree... In response to saying that DFT made a custom bootloader for the HD2:

Doesnt sound very Troll-like, but unless you have a HD2 / follow it's development closely then it's understandable to think they just allowed booting of Android w/o Haret.

... but this is all very off topic! I hope that Adam & Co can get access to a couple of SGN phones and work their collective magic :)
[Samsung Galaxy Nexus] borce_razor:
Gays, this is development thread for Galaxy Nexus - Android phone, based on TI OMAP cpu. If you want wp7, buy wp7 phone and don't spam this thread !!!
[Samsung Galaxy Nexus] sucker4pa1n:
FTFY

The idea of a (hopefully) simple hardware mod that will enable perma-unbricking is astounding. I'm fascinated by the idea, and although it's out of my league for full comprehension (for now) I plan on following this rather closely. It seems posts on XDA rarely contain the level of information like the OP - Congratulations, AdamOutler you are the 1% of XDA. :P
[Samsung Galaxy Nexus] Sleuth255:
@Adam: PM me if the spam doesn't stop and I'll hand out some XDA vacation time to the purps...

Development thread folks. No OT/trolling/hijacking. Mods are watching....
[Samsung Galaxy Nexus] borce_razor:
SwiftModule-4460: Tiny Production Ready Module based on TI OMAP4460 http://www.directinsight.co.uk/products/swiftmodule/SwiftModule-omap-4460.html

expensive + no free schematic diagram
[Samsung Galaxy Nexus] AdamOutler:
The problem is its proprietary. They give only the pinouys for their board and nothing on the board is described in their design.
[Samsung Galaxy Nexus] borce_razor:
omap4460 data manual not provided (only 4430 Data Manual which describes the electrical and mechanical specifications of the OMAP4430 rocessor)

http://www.ti.com/general/docs/wtbu/wtbudocumentcenter.tsp?templateId=6123&navigationId=12037#62

http://omappedia.org/wiki/Main_Page
[Samsung Galaxy Nexus] AdamOutler:
I need hands on a bricked Galaxy Nexus

Using this overlay, the pins can be located fairly easily without destruction to a device.
[Samsung Galaxy Nexus] Loglud:
Adam,

I have been working alot on the OMAP44xx series TI devices, and I can tell you that if it is locked, it will be done through M-Shield, TI's new proprietary crap (That's been giving me the biggest migraine ever).

Now from what I have been reading, Verizon has not allowed for any of their phones for the last 3 months to be sold with unlocked bootloader. HTC, Motorola (usually locked), have been locked recently, so i would not be surprised in the least if they decided to lock it for "contractual obligations".

With all that being said however, I have a firm belief that you and Rebellos will work your magic, as you have time and time again. Please let me know if you figure out any thing with the omap44xx, i would love to get cracking on the beast that is known as the Nook Tablet, which uses the same'ish chip. Please let me know if there is any way that myself (soon to be a Prime) or any of the other guys working on the Nook Tablet can help you out.
[Samsung Galaxy Nexus] AdamOutler:
I need someone with a rooted device to get a memory dump for me please. This will be a snapshot of the live memory running on the device.

in order to do this:

place this binary on your internal storage http://blog.maurus.be/wp-content/uploads/viewmem

use market app "Mount /system (rw/ro)" https://market.android.com/details?id=com.beansoft.mount_system to mount your system folder RW

use market app "terminal emulator" https://market.android.com/details?id=jackpal.androidterm and type the following

su
cat /sdcard/viewmem > /system/bin/viewmem
chmod 1777 /system/bin/viewmem

exit terminal and restart terminal app

Now Viewmem is setup.

run this to get a dump

su
viewmem 0x40030000 0xC000>/sdcard/40030000Dump

and

viewmem 0x40028000 0xC000>/sdcard/40028000Dump

This will place two 48kb (or 0xC000 in hexidecimal length) files on your sdcard called ########Dump. Put these files onto your desktop into a zip form and upload them here.

I need both of these dumps because the processor manual has an obvious error in it... So I'm asking for the values for the 4460 processor as documented and the 4430 processor which may be the same.

These are Internal ROM boot dumps. They are important to figure out what is going on inside a Galaxy Nexus on boot up and may reveal secrets.
[Samsung Galaxy Nexus] RMatt1992:
Does it have to be done on a stock ROM or does it matter?
[Samsung Galaxy Nexus] AdamOutler:
This does not deal with the ROM. This is the device GP registers we are reading. Any device with any ROM will work.
[Samsung Galaxy Nexus] elsif1:
Posted at: http://dl.dropbox.com/u/13966140/Archive.zip

I couldn't collect the 40020... one fully. Bus error about half-way through. So that one is a partial dump.
[Samsung Galaxy Nexus] Flawd:
Do you still need these dumps?
[Samsung Galaxy Nexus] biglipps66:
Same I can provide if need be.

Vzw Nexus rooted stock rom
[Samsung Galaxy Nexus] AdamOutler:
I finally got a reply

so, the CONTROL_STATUS register is 10000101.. Thats

sys_boot_5:0

sys_boot_4:0

sys_boot_3:0

sys_boot_2:1

sys_boot_1:0

sys_boot_0:1

or Boot USB>MMC1.

Someone with Linux, please turn off your device, then plug in USB while repeatedly running the "lsusb" command. I want the USBID of the Galaxy Nexus for comparison to other OMAP devices. It should say Texas Instruments as the identifer.
[Samsung Galaxy Nexus] oc3rulz:
is this simply run through Terminal on Linux, or run through ADB? I have linux and I know how to use the terminal and ADB very well, I also have a GNEX.
[Samsung Galaxy Nexus] CouttsPhotog:
This has been a very interesting read, as I'm somebody interested in low level stuff. I'm curious if I could help at all with this, I'm fairly good at reading ARM assembly code from working with canon dslr cameras for the past 8 months. i understand memory, pointers, structures, etc all from the assembly code level.

I was the main developer for Magic Lantern on the Rebel T1i for a while this year, learned lots. I've spent hours staring at assembly code to understand how the camera works. I agree with the reverse engineering comment you made earlier, it's just a matter of time for anything to be worked out ;)

Will be reading to stay updated! I'll be getting my g nexus either tomorrow or thursday :)
[Samsung Galaxy Nexus] David 617:
i got the samsung drivers, adb, fastboot,

but when i boot to bootloader (vol up+down +power) adb doesnt find any device. is that normal? fastboot oem unlock doesnt work, i presume b/c adb isnt recognizing my phone.

Some help please. Thanks
[Samsung Galaxy Nexus] madj42:
ADB will not find the phone in bootloader mode. If you type fastboot devices, it should show your phone. Check device manager and see if you have an unrecognized device showing. If you do, try manually installing the drivers by clicking the update driver button under the unrecognized device's properties window.
[Samsung Galaxy Nexus] droidstyle:
try reinstalling the drivers...or you may need to use the google drivers in the sdk/adb package instead. Also when you plug the device into pc, go into device manager and see if shows up as android device. If it comes up unkown, then manually push the driver update.

^Ninja'd lol
[Samsung Galaxy Nexus] David 617:
fastboot devices comes up blank.

in device manager my phone comes up as other devices - android 1.0

i guess my driver is bad. where can i get a good one?

(i just installed the one from samsung.. same thing.)

what have you used
[Samsung Galaxy Nexus] Randroidran:
Make sure to download the software from sdk that is for the newest update of android. I think it is 4.0.3 there is like 5 things in that folder. You will need all of them, and after they download type "adb devices" in the command window and it should show the serial #.
[Samsung Galaxy Nexus] David 617:
did that. i dont have any issues untill i am in the bootloader. adb works fine before i reboot.
[Samsung Galaxy Nexus] madj42:
I'm assuming your driver is not loaded properly. Download this driver and unzip it. Install it by using the update driver wizard in device manager. I used this same driver on my work laptop (windows 7) and have had zero issues.
[Samsung Galaxy Nexus] David 617:
thx ill try now

.

.

.

works!

thx a million
[Samsung Infuse 4G] ksteele15:
I recently flashed my Samsung Infuse with SGH_I997_UCKK4[Rooted, Deodexed, and Busybox..

Love it, everything works smooth, even video after I flashed the stock kernel and everything.

The ONLY bug I have encountered thus far is I can't for the life of me get it to send a darn MMS msg.

I have exhausted all options after scouring this site and the interwebs.

I have:

(1) Changed all of my numbers to the +1yyyzzzzzzz

(2) Cleared Messenger Data and Restored to Default Settings

(3) Sent MMS by first attaching the file instead of using the "Share" option in my pictures

(4) Manually entered in new APN settings for AT&T

(5) Tried using both Handscent and GO SMS Pro

Nothing I have tried has worked, any other ideas?
[Samsung Infuse 4G] qkster:
After entering the manual APN, did you save it?

After you save it, did you select it as the one you want?

At the APN settings, are there several APN's to choose from? and the one you want is highlighted?
[Samsung Infuse 4G] Erik_T:
#1 Textfree.. sends it from a different number but whatever.

#2 Flash a different rom (recommend Mitra, Caty.. there are many others)

#3 Email!!! :D You can email people's numbers.. Not sure if it works with pictures....

#4 Try someone else's suggestion...

#5 Why are you still reading... :D

PS. I evidently love smileys.. :D
[Kindle Fire General] adbirdie:
EDIT: Please delete thread, problem solved.

Does anyone have any information on installing twrp from a mac? I have adb installed, but I haven't read anywhere about how to install it using a mac.
[Kindle Fire General] mlhope:
I installed TWRP using my Mac with the official Android SDK and platform-tools for Android 2.3 and Android 4.0 installed.

Basically just followed the instructions on the RootzWiki, as recommended by one of the devs: http://rootzwiki.com/topic/12343-how-to-install-twrp-20-linux/
[Kindle Fire General] adbirdie:
did you install usb drivers (even though they aren't supported by mac osx)? and did you do anything differently because you were using a mac?

thanks for the link.
[Kindle Fire General] mlhope:
Sorry man, I don't remember whether or not I installed any USB drivers. If they're not supported, I imagine that I didn't.

But, I don't want to give you misleading info -- so, if you're not sure, I'd say hold off until someone who really knows what they're talking about chimes in. I'm pretty reckless when it comes to this stuff, and I'd hate for you to do something you regret on account of my mouth, ha!
[Kindle Fire General] adbirdie:
sorry, another question, did the kindle automatically show up in adb with no tinkering, hate to pester you, im just planning everything before i give it a go.

also, did you plug it in while it was on with usb storage enabled?
[Kindle Fire General] ttabbal:
You don't need any drivers. Adb and fastboot should both work just fine. You might need to edit the ini file though.
[Kindle Fire General] adbirdie:
Did you have to edit the usb_ini file? if so, how would i go about doing it?
[Kindle Fire General] ttabbal:
Same as on linux... I changed it, but i'm not sure i needed to.
[Kindle Fire General] adbirdie:
ok, one final thing ( i promise) http://rootzwiki.com/topic/12343-how-to-install-twrp-20-linux/ is that similar to what you did?
[Kindle Fire General] adbirdie:
Edit: I've ****ed up and now i'm stuck in fastboot. do you have any ideas how to fix that?
[Samsung Galaxy Nexus] Hussainally:
Hey bro.tks for this but need some clarification if you don't mind

1.if I flash a new rom in cwm from stock rom,and I do a superwipe,will all my data like music etc from internal storage get wiped as well?

2.you mentioned above about using restoring data option under advanced in cwm,when do I do this?right after I flash or after I have booted to android and go back to cwm and click restore data?

Please advice