yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] PVLMTREE:
Yes you can. In some ROMs, you can simply change it under settings. If you're using a WiFi Hotspot, in that app itself, I think you're able to change it.
[Verizon Samsung Galaxy S III] dunderball:
Sorry, I should've been clearer on what I was on. Any way to change it on a rooted stock TouchWiz Jelly Bean rom? Perhaps someone knows of a mod.
[Verizon Samsung Galaxy S III] mikeman45:
Can't you just rename it through you wireless network on your home PC. For example I have a net gear router and it has a genie application on my home PC where I can see what is connected to my Wi-Fi and I can rename things like ps3, my gs3, wife's thunderbolt, ect.....
[Verizon Samsung Galaxy S III] mikejr83:
It's been a while since I've been on stock TW, but I think the setting is the same as it is in CM10.

Go into System settings, development, and and make sure that development is enabled. In that section should be a setting called host name. You should be able to change it there.
[Android Q&A, Help & Troubleshooting] ebildude123:
>Tablet

>Connect to WiFi

>Broadcast WiFi network which uses tablet's WiFi connection

>Profit?
[AT&T Samsung Galaxy Note II] winlinmac001:
When T-Mobile Enables Support for LTE on Note 2, can it be used with AT&T LTE for full 4G LTE speeds?
[AT&T Samsung Galaxy Note II] Darkshado:
Check out this link for your answers, and this one too.
[AT&T Samsung Galaxy Note II] SurrealNetworks:
I've confirmed that an unlocked T-Mobile Note 2 works on AT&T LTE if AT&T adds an LTE capable IMEI to your account. In the case of my friend, a sales rep at the AT&T store noticed the T889 shows up on their system as a non-LTE device. That sales rep pulled the IMEI from their demo Note 2 (i317) and added it to my friends account, modifying the last digit to avoid an IMEI conflict in their system. A few moments later, the LTE icon activated on the T889. YMMV
[Galaxy Note II, Galaxy S III Developer Discussion ] AdamOutler:
Hey guys. As the title states, we need to destroy SBOOT to leave the device in an otherwise "hard-bricked" state. This would open the door to loading an insecure bootloader. Currently our option is to perform a hardware hack to brick the device which is obviously not optimal...

So, the question is, how can I write some garbage like a Justin Beiber MP3 over the SBOOT?

If you've come up with a way to hard-brick this device, it would be very helpful if you share.
[Galaxy Note II, Galaxy S III Developer Discussion ] AdamOutler:
Has anyone researched K-Exec on the VZW Galaxy Note2?

This change (Pointed out by XDA Recognized Developer Ralekdev) to Cyanogenmod by XDA Elite Recognized Developer Entropy512, implemented in a kernel, booted into a kexec, could expose the /dev/block/mmcblk0boot0. https://github.com/CyanogenMod/andr...4702bde8fb2a7ea082c5b385ee0911e3f86307#diff-0 We need access to this partition to be able to destroy it. I'm not a kernel developer though. I need some help with this.
[Galaxy Note II, Galaxy S III Developer Discussion ] BeansTown106:
i can link u to a kernel but from what i know no one has looked into kexec yet.. also did u mean to put this in international forum or verizon one :) cause were in international now not verizon
[Galaxy Note II, Galaxy S III Developer Discussion ] BlueHarford:
Add me on gtalk I have a guy on my team that's a kernel guru I'm sure he can get done anything you need, I'll reply with his gtalk info
[Galaxy Note II, Galaxy S III Developer Discussion ] garyd9:
There's currently only one dev discussion section shared among all the Note2 devices.

Adam, I haven't messed with kexec, and my schedule is a bit nightmarish until the new year... If no one has come up with something by then, I'll (try to remember to) work on it then.

take care

Gary
[Galaxy Note II, Galaxy S III Developer Discussion ] BlueHarford:
bbedward is building a kernel right now. Adam i will PM you his gtalk
[Galaxy Note II, Galaxy S III Developer Discussion ] bbedward:
http://goo.im/devs/bbedward/vzwnote2_image.zip

There's a stock note 2 kernel build, it includes this and is stock otherwise except for some gcc 4.7 fixes https://github.com/CyanogenMod/andr...4702bde8fb2a7ea082c5b385ee0911e3f86307#diff-0

Maybe it'll help somebody if they get kexec working :good:
[Galaxy Note II, Galaxy S III Developer Discussion ] iamsamiam:
/dev/block/mmcblk0boot0 <---- this is the sboot block?
[Galaxy Note II, Galaxy S III Developer Discussion ] invisiblek:
You can't flash a custom boot.img (ytod)

You can't flash a custom recovery.img (ytod)

Without either of those, I don't know that you can get kexec working.

If I remember correctly, you needed a kexec-enabled recovery in order to hardboot a different kernel (of which did NOT need to be kexec-enabled).

So you would already have to have a kexec-enabled kernel running in order to do this, and if we could do this we could just include that patch anyway.

Might be able to do some some crafty stuff with 2nd init, beyond me, I've never messed with this. Hashcode might be of some help here.

But will this allow booting a different kernel? That's your main obstacle here.

Not sure if its possible to build block as a module with that patch that adam listed and force load it on a rooted device.

(I'm pretty sure this wouldn't work since its built into the kernel already, even if you could it would probably panic, and on the off chance it did load, would mmcblk0boot0/1 even show up? doubtful...)

yes
[Galaxy Note II, Galaxy S III Developer Discussion ] droidstyle:
this was my thinking aswell...kexec will only work if we can flash a custom recovery.img, but since sboot checks the recovery partition, nothing custom can be flashed to it. aboot on the vzw s3 didnt check the recovery partition which left a hole to get in and use kexec.
[Galaxy Note II, Galaxy S III Developer Discussion ] iamsamiam:
probably out of my scope but..... sboot checks the recovery partition at STARTUP (i would guess its the first thing checked, since when i soft bricked mine it wouldnt do ANYTHING but tell me the software is not genuine, any way we could inject(probably not the right word) it after the check?
[Galaxy Note II, Galaxy S III Developer Discussion ] invisiblek:
FYI guys this didn't work

Error was something about "exports duplicate symbol....(owned by kernel)"

Found it funny I got "owned by the kernel", but w/e...

Here's the module in case anyone wants to mess around with it, dmesg is where the error appears

http://invisiblek.chickenkiller.com/mmc_block.ko

Pretty sure there is no way to get this loaded, but the steps to do so would be:

- throw it in /lib/modules (this is non-persistent)

- chmod it to at least 644

- busybox modprobe -f mmc_block
[Galaxy Note II, Galaxy S III Developer Discussion ] Entropy512:
While this is mostly specific to the Verizon variant, being able to kill SBOOT to force SD-card boot is a technique that would be usable on multiple devices in the future.

Pretty much it's that the VZW Note2 NEEDS the ability to kill SBOOT starting from a stock kernel without anything beyond root, but it may be useful on other devices too.

And if people are wondering why we're TRYING to hardbrick a device - if you hardbrick by killing SBOOT, the device falls back to booting from the SD. Samsung's "official" hardbrick recovery technique does this by shorting a resistor to disable the eMMC.

The key is whether there is some way to access mmcblk0boot0 from a stock kernel... So far, no one has ever done it without hacking the kernel itself to my knowledge.
[Galaxy Note II, Galaxy S III Developer Discussion ] kirch21:
guy posted this in the rom thread, posting it here to.. i also have no idea what it is but cant hurt right? lol
[Galaxy Note II, Galaxy S III Developer Discussion ] Loglud:
So I think people have a misconception of what kexec is.

Here

Yes there was orignally a kexec for the SGSIII that was issued in the recovery partition but this is not what kexec does. IT LOAD A KERNEL DIRECTLY ONTOP OF THE CURRENT. It does not access memory. It does not change any of the partitions, and it does not make it so that phone will not be "secure" for booting. It does not require any access to the recovery partition and does not need kexec-enabled in the kernel necessarily. When you enable kexec in the kernel, all you do is provide a handle for the actual binary so it knows where in the stack to replace the kernel. Without this you must write in your own kexec injection vectors, and this can be difficult, but has been done for devices before (see nook tablet). There's no doubt in my mind that this would be an incredibly daunting task, however if someone did it, it might prove usefull for every device in existence that has a locked bootloader.

As for the topic at hand. To what I have scene and read here it sounds like the default kernel does not allow you to access the mmcblk0, which is kinda a pain. Though it might only not allow you to do this by name. I wonder if you overloaded partition table if it would start to bleed into the first block. Or if we can write a program that references the memory by location instead of by pointer, aka 0x81000000 instead of mmcblk0. Also you might want to dump the system kernel in the recovery or any other bootable mode. It is possible that its only on the system image kernel that it blocks this. IE boot into recover mode and or download mode and see if that subspace can be accessed. As a last resort adam you might be able to boot it into panic mode with the boot pins. I havent been able to find a diagram, but it is always possable to brick the device with pins, which ones are beyond me though i found this. Unfortunately no mention of boot conditions anywhere there.
[Galaxy Note II, Galaxy S III Developer Discussion ] times_infinity:
I wonder if something like bootstrap or safe strap could be implemented to try and boot a kexec kernel with a custom recovery so that mmcblk0boot0 gets exposed.
[Galaxy Note II, Galaxy S III Developer Discussion ] chayes627:
I have recommended to Adam to talk to Hashcode as he did some creative things with the Droid 3 and kexec and custom recovery.
[Galaxy Note II, Galaxy S III Developer Discussion ] times_infinity:
Exactly who i was thinking of when i wrote that post. :P
[Galaxy Note II, Galaxy S III Developer Discussion ] kejar31:
I hit up hash on gtalk today and pointed him to this thread.. Seems at least we should be able to get a hacked recovery working like safe-strap. Then again I am no recovery nor kernel dev
[AT&T Samsung Galaxy S II SGH-I777] km3r:
I currently have ShoStock2, but am willing to switch if it lets me other ways.

I really want the group MMS feature
[AT&T Samsung Galaxy S II SGH-I777] Nick281051:
Google is your friend.

Sent from Team Pirate! Using Tapatalk 2
[Verizon HTC Droid Incredible 4G LTE] litetaker:
I am unable to connect to verizon wireless network anymore! :( This started happening after I was trying to port MIUI onto the Dinc4G. Now, I have a small triangle over the signal bars. Somehow, I managed to get 3G data, but I am unable to place or receive calls. I am unable to activate phone via *228# either. I spent over 30-35 mins on the phone with VZW customer service and they were unable to fix it as well. And I also used the bootloader unlock tool to revert my CID to VZW__001 and it still doesn't work. I factory reset and deleted all data/dalvik/cache and system partition and reinstalled ViperLTE ROM and it still doesn't work.

A screen shot of the problem.

As you can see in the image, I have a triangle above the signal. Also, in the settings page, you can see that the phone number in the device is 0000000000! WHY?

Can anyone help me fix this??? Thanks
[Verizon HTC Droid Incredible 4G LTE] Linch89:
Try the ruu that's a worst case scenario but this sounds like that...
[Verizon HTC Droid Incredible 4G LTE] Aldo101t:
i think thats a roaming symbol, check your network settings and apn, just a quess.
[Verizon HTC Droid Incredible 4G LTE] slacka-vt:
This happened to a lot of us on the Dinc2, myself included, when we flashed a chinesse RUU. We ended up having to flash a stock RUU and needed to type a number combination to update the carrier settings. Sorry, I don't have the specifics, but you will be able to fix it. Has to do with flashing the wrong radio I think. You probably inadvertently flashed a foreign radio.
[Verizon HTC Droid Incredible 4G LTE] Method320:
Ahh, I remember this issue. And a fellow Vermonter too! Also yes, the triangle over the signal bars mean you are roaming (Verizon has no idea where/what you are) If you can reflash the stock ruu and possibly specifically the stock radio, you should go back to normal.
[Verizon HTC Droid Incredible 4G LTE] litetaker:
I am unable to flash stock ruu. It is causing an error and quitting. However I didn't mess with the radio (I think) and I didn't do anything else other than flash system files while attempting to port MIUI... sad :( I am getting a CLNR from Verizon as they couldn't figure it out after 30 mins of trouble shooting on phone yesterday and some 30 mins of trouble shooting in a store today and after replacing the sim card either...

I think devs on this device should be careful while messing around as they may mess their phone like me and be unable to rectify it by flashing ruu... beware people...
[Verizon HTC Droid Incredible 4G LTE] jose51197:
Try initiating ril manually
[Verizon HTC Droid Incredible 4G LTE] nitsuj17:
did you relock before flashing the RUU? if not, thats probably why its failing
[Verizon HTC Droid Incredible 4G LTE] Linch89:
Try what nits said the ruu is like a reserve parachute it should work in the boot loader
[Verizon HTC Droid Incredible 4G LTE] litetaker:
I managed to install the RUU found at Team Unlimited IO's website. Yes, I forgot to relock.

It did not fix the issue immediately and I was bummed. I still had the same issue. I then attempted to boot into recovery only to realize the RUU wiped my TWRP recovery. Then I waited for my phone to reboot and it did and then somehow I got back access to the network!

Now, will I be guaranteed to recover access to the network the next time such an issue occurs? I dunno, because even after RUU I initially didn't get the network connection back but only after a reboot. If there was some other reason for this screw up I will be careful with my dev work. Else, if someone can verify that I can safely restore lost network connectivity with an RUU I can dev in peace.
[Verizon HTC Droid Incredible 4G LTE] Linch89:
At least you are back to stock and can soff now :)
[Verizon HTC Droid Incredible 4G LTE] litetaker:
I did S-OFF! :cool:
[Verizon HTC Droid Incredible 4G LTE] Linch89:
So it's your phone back to normal now? Did that sketch you out of devving? I wouldn't blame you...there's a lot that could go wrong and a several hundred dollar mistake isn't a good thing at all :P
[Verizon HTC Droid Incredible 4G LTE] litetaker:
Yup.. Back to normal. I will continue to work on deving, but I will take precautions from now on. I still want to get to the bottom of this and find out exactly why it happened. In any case, as long as I can flash stock RUU to go back to defaults I will not shy away too much from deving.. :)
[Verizon HTC Droid Incredible 4G LTE] Aldo101t:
glad to hear your back up and running.
[Verizon HTC Droid Incredible 4G LTE] litetaker:
Unable to flash recovery:

sending 'recovery' (7564 KB)...

OKAY [ 1.074s]

writing 'recovery'...

FAILED (remote: not allowed)

finished. total time: 1.108s

My bootloader seems to be locked again after reflashing the RUU.. I am unable to unlock it using fastboot oem unlock!

Help! Damn I shouldn't be messing with MIUI.. I will be careful next time!
[Verizon HTC Droid Incredible 4G LTE] jose51197:
Need to get new unlock tocken
[Verizon HTC Droid Incredible 4G LTE] Linch89:
If you soff why do you need to unlock your boot loader???
[Verizon HTC Droid Incredible 4G LTE] jose51197:
Forgot that detail
[Verizon HTC Droid Incredible 4G LTE] litetaker:
I don't know why but I had to re unlock the bootloader via htcdev as suggested by you even though I was already s-off.. confused but at least I am back to normal.
[Verizon HTC Droid Incredible 4G LTE] joesee:
So without having to go back to RUU stock and all that if I have 0000000000 for my phone number unlocked bootloader and soff is there anyway I can fix this without having to go through all that?

This dinc4g has been the worst phone I've ever messed with. :(
[Verizon HTC Droid Incredible 4G LTE] 24ky:
I had the same exact issue, I just followed mdmowers 2nd post in cyangenmod and it fixed my phone

In the rare event that your radio refuses to make a connection, your radio's nv may have stored some bad settings. If restoring the backup of your previous ROM does not restore the radio to working condition, then follow these instructions to get the radio working again. This method is less invasive than running the RUU followed by a factory reset, as it will not overwrite hboot.

Downloads

Stock ROM

recovery_signed.img - MD5: e9334607c52aebe2da20c53c32820391

Instructions

From your preferred recovery, run the factory reset option

Follow the directions in this thread to install the stock ROM

Boot the ROM, then turn off HTC's fast boot: Settings > Power > Fast Boot = Off

Reboot to the bootloader

Flash the stock recovery:

fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader

Factory reset from the bootloader: BOOTLOADER > FACTORY RESET

Let the phone reset and boot up

Allow network connectivity to be restored (make a test call)

Turn on all GPS location services: Settings > Location > (all three location services) = On

Turn off HTC's fast boot: Settings > Power > Fast Boot = Off

Reboot to the bootloader

Flash your preferred recovery: CWM or TWRP

(If you just want to run this stock ROM, you can stop here)

From your preferred recovery, run the factory reset option

Restore your ROM backup and wipe cache again before rebooting

[/QUOTE]
[Verizon HTC Droid Incredible 4G LTE] slezzzter:
Have you found a solution for this yet? I went through the whole re-locking, RUU flash, and reboot as described, but my number is still 0000000000.

EDIT: An additional Factory Reset after flashing with RUU seems to have fixed it. Sadly my foray into getting CM10.1 on the inc4g has left me back where I started, and a few hours poorer.
[Verizon Samsung Galaxy S III] tomster2300:
I want go back to the stock kernel but can't find it after searching the forums. Could someone point me towards a thread that contains it? Thanks!
[Verizon Samsung Galaxy S III] MG386:
Flash a cm10 ROM again, clear cache and dalvik . Reboot.
[Verizon Samsung Galaxy S III] drbveb88:
http://xdaforums.com/showthread.php?p=34841673

This is the latest touchwiz kernel.
[Verizon Samsung Galaxy S III] tomster2300:
Thanks. I just flashed it and I'm still seeing this under kernel version:

3.0.31-381038

se.infra@SEP-109 #1

SMP PREEMPT Thu Nov 15 13:36:15 KST

2012

Is that the correct kernel?
[Verizon Samsung Galaxy S III] The Archangel:
Can somebody to me how hard it is to post a Question IN THE Q&A SECTION!! This is ridiculous, you read the rules when you sign up, there's sticky clearly saying NO QUESTIONS IN DEVELOPMENT ONLY ROM , MODS AND KERNELS.why is it so hard to follow the directions?!?!?!
[Verizon Samsung Galaxy S III] tomster2300:
Sorry, somewhat new to the boards still. Thank you for being so friendly and welcoming to the new folks...

I looked up the first part of the kernel and it looks like it may have come from E-Z Recovery. Is that possible? Thanks!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
What rom are you running? Because that is the correct kernel for the latest TW JB VRBLK1 update. If you're on ICS, then you will have serious issues.
[Verizon Samsung Galaxy S III] tomster2300:
I was running PA but recovered back to CleanROM 5 to see if it improved my GPS lock. I read that the stock kernel was recommended for CleanROM, so that's why I asked.

It looks like it must have come with the rom :). Thanks everyone for the quick responses!
[HTC Droid DNA] stinkfist462:
Is this possible? I've unlocked, rooted, have recovery, all of that. Is it possible for me to simply flash a pure vanilla Jelly Bean onto my phone?
[HTC Droid DNA] Thrillhouse847:
Short answer: no. Long answer: eventually we will start seeing AOSP ROMs but a lot of work must be done first. I'm not a dev so I can't really explain everything that needs to happen before it can be done but rest assured it's being handled by top men.

Sent from my HTC6435LVW
[HTC Droid DNA] stinkfist462:
Alright. I appreciate the reply. But that's what I mean. Why does it have to be AOSP. Why can't I just slap a factory fresh Jelly Bean on this thing? It's confusing to me.
[HTC Droid DNA] MustafaHadaKing:
that just hasn't been developed for out phone yet. AOSP is stock android, which in turn is stock jelly bean
[HTC Droid DNA] crossmission:
vanilla android and AOSP is one and the same, it's what Google makes and then the companies take and modify it but when you say stock android usually (almost always) means the original ROM that came with the device as new.

As an example for HTC we say a "Sense ROM", for Samsung a "Touchwiz ROM" which in reality are both launchers (of course it's not as simple as that because the things they do go a lot deeper) but if you want a more vanilla experience try nova (my personal favorite on my One X) or apex launcher and if I remember correct there's an app to remove the bloatware to make the device even faster and release some space on your storage (all the apps that companies put but noone uses) but try not to remove any neccesary system files, ALWAYS make a backup first and if you're not sure then don't mess with it. Haven't gotten a DNA but really thinking about it.

edit: here's the mod I was talking about http://xdaforums.com/showthread.php?t=2012388

I hope I helped :)
[HTC Droid DNA] Mazer_R:
From what I've heard there are a few developers working on getting the RIL ready for AOSP ROMs, but I'm not sure how far they've gotten (I've heard rumors of them being close). After the RIL there's the camera/camcorder to work on before AOSP ROMs can be bugtested the released. So, as of now, this is not possible, but it should be here in the next few (read: we don't know when) months.
[HTC Droid DNA] TheBiles:
Once we get the RIL, there shouldn't be anything stopping them since we already have a kernel source.
[HTC Droid DNA] Bigandrewgold:
Because it has to be made for this device specifically, there is no factory fresh stock jb built for this device. You could probably get one too boot without too much hassle, but it would be buggy as all get out and have no connectivity whatsoever.

aosp is vanilla android btw
[HTC Droid DNA] aFancyTickler:
apparently someone is getting closed to s-off so we can see vanilla android (aosp) really soon, i hope :3
[HTC Droid DNA] TheBiles:
Link?
[HTC Droid DNA] werdna87:
Just so you guys know, s-off is not related to AOSP. People made this assumption with the rezound as well, but it took months to get AOSP on that, even after we had S-off. It is mostly the RIL which has to be made mostly(if not totally) from scratch.
[HTC One S] justin11141:
Which ROM do y'all think gives the best battery life? I'm on baked right now and right as I get out of school I'm down to 35% usually, thanks
[HTC One S] LalyGirl:
I use viper and it is giving me a good battery life. I don't know about aokp/cm. I think you should try everything and then you will chose whatever is good for your needs.
[HTC One S] michaeldotson817:
How is the stock Rom with battery? Just wondering if it's worth rooting and putting a custom Rom on for battery
[HTC One S] acerulz:
cm10 has nice battery life ..m using dark jelly S v20 the battery is really good works almost a day for me with me almost connected for 14-16hrs of wifi connectivity and listening music and of course auto sync always on ! u should try all once before proceeding further
[HTC One S] NRGZ28:
Energy ROM and of course.. other stock based ROMs have the best power management available, you know, engineered by HTC :)
[HTC One S] Mekuso:
For me, cm10 gives better battery life than stock Sense. I think it depends on how you use your phone.