yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] zachf714:
this has selinux disabled
[Verizon Samsung Galaxy S III] old&slow:
Still nothing. :(
[Verizon Samsung Galaxy S III] zachf714:
our zImage in a sprint ramdisk, with the offset to the 4.3 offset. Try that

edit - here with the sprint ramdisk at the 4.3 offset
[Verizon Samsung Galaxy S III] old&slow:
Tried mine now i'll try your's.

Edit: Same.
[Verizon Samsung Galaxy S III] zachf714:
F#@#$%@#$@#%@#$@@

Does it go any farther ?

my only other thought is to take a cm ramdisk and throw the zimage in it
[Verizon Samsung Galaxy S III] old&slow:
No, same quick Samsung flash and then black screen.
[Verizon Samsung Galaxy S III] zachf714:
crap, take the full sprint selinux permissive kernel and set the ramdisk to our correct offset. See if that works
[Verizon Samsung Galaxy S III] old&slow:
Sorry, my stomach thought my throat had been cut. :p

Stock sprint kernel with our offset still doesn't boot.
[Verizon Samsung Galaxy S III] zachf714:
No problem, I assume just the same samsung flash and black screen
[Verizon Samsung Galaxy S III] old&slow:
Right.

I'm going to try the cm ramdisk here in a minute for the heck of it.

---------- Post added at 10:30 PM ---------- Previous post was at 10:10 PM ----------

Had to try it but still nothing.

Maybe a little late to ask but has anyone seen a pit for 4.4.2? Kernel is still @ /dev/block/mmcblk0p7 right?
[Verizon Samsung Galaxy S III] zachf714:
Im stumped ..... I guess I will pick up tomorrow, im about to go to sleep
[Verizon Samsung Galaxy S III] old&slow:
Same here...did you see my last question?
[Verizon Samsung Galaxy S III] zachf714:
I just saw it, let me ask beans
[Verizon Samsung Galaxy S III] CNexus:
Dang. I was sure that would help with something

I can't try this, but I *believe* that tz and rpm are parts of the firmware that can be safely updated. May or may not help to get it booting.
[Verizon Samsung Galaxy S III] old&slow:
Yeah, I had hope. Before all of the Knox bs [MENTION=2385005]invisiblek[/MENTION] was packaging up the modems and rpm for us but on this last iteration it was discovered to cause bricks. Don't remember who found out the hard way.
[Verizon Samsung Galaxy S III] BeansTown106:
no pit

nope verizon redid the signatures so if we flash any firmware other than modem we auto brick

ok so so far with stock kernel i get samsung logo then black screen

with dkp kernel i get passed samsung and to s3 screen

and with ktoonz aosp kernel i get past both screens lol and now am at a flashing led. obv display issues but so far aosp kernel gets the farthest
[Verizon Samsung Galaxy S III] old&slow:
Wish they would have made a GPe S3. That kernel would probably boot.
[Verizon Samsung Galaxy S III] CNexus:
GPE uses a touchwiz kernel
[Verizon Samsung Galaxy S III] old&slow:
Right but without the carrier ridiculousness.
[Verizon Samsung Galaxy S III] thenugdestrroyer:
Told you all cnex is a wizard
[Verizon Samsung Galaxy S III] zachf714:
I found a flag that looks awfully suspicious in the sprint source

CONFIG_PANIC_ON_DATA_CORRUPTION=y

I set that to "is not set now" and have a ghetto vzw defconfig in there being that the vzw ifdefs are there
[Verizon Samsung Galaxy S III] CNexus:
Not sure what you mean but I just meant it wouldn't be much different than the stock kernels you've been trying and not any closer to the aosp kernel that beans found got it to almost boot

Speaking of that [MENTION=4395895]BeansTown106[/MENTION] did you try that aosp ramdisk with the stock zImage? And repack with same parameters as the original aosp boot.img?
[Verizon Samsung Galaxy S III] BeansTown106:
yep just did and same result as using stock 4.4 kernel so its the zimage thats our issue it seems as i used aosp ramdisk and aosp ramdisk adress
[Verizon Samsung Galaxy S III] old&slow:
Actually, I was probably speaking out if turn. Being on vzw, the only GPe roms I've seen have been ports with custom kernels and no firmware or modem prerequisites.
[Verizon Samsung Galaxy S III] CNexus:
Looks like it, I would not be surprised if they built it with configs that check for TIMA and other nonsense

Hopefully source drops soon
[Verizon Samsung Galaxy S III] zachf714:
There are TIMA options... F@#$
[Verizon Samsung Galaxy S III] garwynn:
What are you guys doing for the dt.img?

Are you extracting out of the 4.4 zImage and repacking it? Or doing nothing with it at all?
[Verizon Samsung Galaxy S III] Scott:
Yeah, thats what I figured abour brick...

I ran my own 4.3 based kernel and ram disk and got what you got...

I think they hosed us :(
[Verizon Samsung Galaxy S III] BeansTown106:
S3 doesn't have dt.Img that's only n3 and up iirc

Mehh
[Verizon Samsung Galaxy S III] Scott:
Before stuff went all to hell on me (long story!) I was yanking zImage and dropping it in different ramdisks. Different RAM disks with stock zImage, etc...

Havent touched dtb.img, every time I do I break something, lol

For me DTB only seems to matter on Snap800+

Anyone else with thoughts on it?
[Verizon Samsung Galaxy S III] Scott:
Glad you can say mehh, lol

But I agree about dtb.img, snap800+
[Verizon Samsung Galaxy S III] garwynn:
Either of you available on a more chat-friendly channel? Got a bit while CM's churning for the S5.

Might as well give a poke at this and see if I can help.
[Verizon Samsung Galaxy S III] BeansTown106:
Lol its 4am not much to say haha.. And ya I think they hosed us as well we're gonna have to do some massive kernel hackery to get it to work
[Verizon Samsung Galaxy S III] garwynn:
[MENTION=426561]scrosler[/MENTION],

Do you still have that NE1 stock recovery available?
[Verizon Samsung Galaxy S III] Scott:
Agreed

Let me look at my collection...
[Verizon Samsung Galaxy S III] Scott:
Yes, have stock NE1 TAR

Edit: Thanks to Open!
[Verizon Samsung Galaxy S III] Scott:
Stock boot.img and recovery.img: https://dl.dropboxusercontent.com/u/31360541/SGS3/SGS3-NE1-Rec-Boot.7z
[Verizon Samsung Galaxy S III] Scott:
NE1 NON-HLOS: https://dl.dropboxusercontent.com/u/31360541/SGS3/NON-HLOS.bin
[Verizon Samsung Galaxy S III] Scott:
Rec and boot have same zImage. Other diffs...

Left = Boot, Right = Rec
[Verizon Samsung Galaxy S III] Scott:
Too late for me. About to head to bed... 3:45am here. Will be up tomorrow... will send Gtalk info...

-Scott
[Verizon Samsung Galaxy S III] garwynn:
Thx for recovery, confirmed no dt.img on this (Sorry, been working so long on S4+) so one less piece to the equation.

Let's try something simpler. Can you flash this and see if this at least gets ADB available to poke around?

This is the stock ramdisk with loglevel 8 and adbd started in init.rc.

Edit: Just saw last reply, hit me up whenever, will be around.
[Verizon Samsung Galaxy S III] LLStarks:
*points to sig*

A lot of the d2 maintainers hang out there and it's still very active
[Verizon Samsung Galaxy S III] zachf714:
If you only flashed the SBLs and not tzdata maybe you can fix it back to the LE6 bootloader with the SD card trick

---------- Post added at 03:45 PM ---------- Previous post was at 03:11 PM ----------

I think I know why its not booting, its compiled with LZO compression and I strictly remember the conversation we were having in IRC with blek when he was trying to get LZO working on d2 with our caf 3.4 kernel on d2 and it would not fit on the partition which explains why we dont get to the kernel at all

---------- Post added at 04:20 PM ---------- Previous post was at 03:45 PM ----------

This has xz compression, this could boot. http://www.androidfilehost.com/?fid=23501681358554349

It only makes sense, because the stock kernel does not extract which is why it does not boot
[Verizon Samsung Galaxy S III] zachf714:
This is the boot.img with xz , it is literally 5 mb smaller
[Verizon Samsung Galaxy S III] LLStarks:
Might need to wait a few more days for kernel source. Apparently my request didn't go through on their server like I thought.

Resubmitted for NE1 (and NC1 just for the hell of it).

"It's pretty much a clone of Sprint/USC/etc..."

I know. I know.
[Verizon Samsung Galaxy S III] prdog1:
Same. Just first splash. :cool:
[Verizon Samsung Galaxy S III] zachf714:
It has been narrowed to the zImage at this point. I am looking through these defconfigs that ship with the sprint source
[Verizon Samsung Galaxy S III] mikeman45:
Come on Scott I know you got this ? If there is anything you would like me to flash to test for you let me know.
[Verizon Samsung Galaxy S III] Scott:
As a collective we have tried lots of things.

At this point we seem to be in a holding pattern hoping to Samsung kernel source to see what is going on.

Hopefully then source will help but even them I am cautiously optimistic.
[Verizon Samsung Galaxy S III] zachf714:
I have looked through the defconfigs so many times in the sprint source it's not even funny. I can't figure out what is causing the ramdisk and kernel to not Unpack. At first when I realized it was not unpacking I thought it was too large but once I made it smaller with XZ compression it was still not extracting into ram. There has to be something that is not enable/disableable in the defconfig or I am skipping over something but I looked and anything that looked fishy was in the defconfig for cm and the 3.1.x kernel for 4.3
[Verizon Samsung Galaxy S III] n3wt:
Kernel Source

[MENTION=426561]scrosler[/MENTION] [MENTION=3074508]old&slow[/MENTION] @ etc

http://www.androidfilehost.com/?fid=23501681358555936
[Verizon Samsung Galaxy S III] prdog1:
Yea. I told Scott on chat. He asleep at the wheel. :p:cool:
[Verizon Samsung Galaxy S III] prdog1:
Well. Got by the first splash and black screen to second Galaxy S3 splash but no boot. Maybe someone that knows what they are doing can get somewhere. :cool:
[Verizon Samsung Galaxy S III] old&slow:
Are you using stock ramdisk and what ramdisk address?
[Verizon Samsung Galaxy S III] prdog1:
Stock. I just turned off SeLinux and all other security and let it default to DAC in security Kconfig. Forgot about that address. Don't know where that is. :cool:
[Verizon Samsung Galaxy S III] old&slow:
If you're using Archi I don't know where to change addresses.
[Verizon Samsung Galaxy S III] prdog1:
Should be same place if unpack. Ramdisk will be in project file after unpack. In kernel folder.
[Verizon Samsung Galaxy S III] 5ft24:
Just a quick note. Samsung released the NE1 kernel source
[Verizon Samsung Galaxy S III] prdog1:
Yea. We know. We are working with it now. :cool:
[Verizon Samsung Galaxy S III] old&slow:
Interested in seeing what happens using the ramdisk offset like 4.3.
[Verizon Samsung Galaxy S III] prdog1:
Hahaa. I don't know how to change.
[Verizon Samsung Galaxy S III] old&slow:
You would have to use repack scripts.
[Verizon Samsung Galaxy S III] prdog1:
Yea. I don't know jack about kernels. This above my paygrade. We at least have something for the bigboys to play with. :p:cool:
[Verizon Samsung Galaxy S III] old&slow:
Reading material, courtesy of [MENTION=4645794]CNexus[/MENTION]: http://xdaforums.com/showthread.php?t=2319018&nocache=1
[Verizon Samsung Galaxy S III] zachf714:
I've been afk for a few days, what did you guys get to?
[Verizon Samsung Galaxy S III] prdog1:
I just turned off security in SeLinux Kconfig and got to Galaxy S3 splash screen. No black screen. Just stuck there. :cool:
[Verizon Samsung Galaxy S III] zachf714:
I can mess with the vzw source, i know what to mess with in the defconfig security wise
[Verizon Samsung Galaxy S III] old&slow:
[MENTION=4538493]prdog1[/MENTION] got to second splash (S3) with stock ramdisk and what should be stock 4.4.2 address.

Edit: Ninja'd! :p
[Verizon Samsung Galaxy S III] prdog1:
[MENTION=3074508]old&slow[/MENTION]. I put Cnexus' files in bin but can't figure out how to run. Get permission denied. Opened full permissions on bin. :cool:
[Verizon Samsung Galaxy S III] zachf714:
Rwxr-xr-r
[Verizon Samsung Galaxy S III] prdog1:
HaHaa. I gave everybody and their mother read,write and execute priveleges. :cool:
[Verizon Samsung Galaxy S III] CNexus:
chmod 755 ~/bin/*
[Verizon Samsung Galaxy S III] prdog1:
Kewl bro. Thanx. Got it working. :cool:
[Verizon Samsung Galaxy S III] old&slow:
Well, get the kernel working!! :p:laugh:
[Verizon Samsung Galaxy S III] prdog1:
HaHaa. Still above my paygrade. :p:cool:
[Verizon Samsung Galaxy S III] zachf714:
send me what you did to the selinux kconfig, I will mess with the kernel more .
[Verizon Samsung Galaxy S III] zachf714:
[MENTION=4538493]prdog1[/MENTION] [MENTION=3074508]old&slow[/MENTION] here take this and pack it to a ramdisk but put the modules in /lib/modules

also try and set the ramdisk offset to the 4.3 and below offset

fyi - you will love what I set the local version to if it boots lolololol
[Verizon Samsung Galaxy S III] Scott:
Whats taking you people so long :p

I'll try to help tonight when I get out of work.
[Verizon Samsung Galaxy S III] zachf714:
your d2 still bricked ? what did you do to it ?
[Verizon Samsung Galaxy S III] Scott:
No no. When we first saw the no boot to second logo I was thinking brick because I could not softkey it back into recovery. But battery pull and persistence paid off. Right now I am on stock NE1 with non boot status.
[Verizon Samsung Galaxy S III] prdog1:
Looks like a good roosting spot. I'm roosting on second splash. :p:cool:
[Verizon Samsung Galaxy S III] zachf714:
Did you try what I posted?
[Verizon Samsung Galaxy S III] prdog1:
Yea. Added zimage and modules = 2nd Splash. Changed base address to 4.3 = 2nd splash. Haven't changed ramdisk address to 4.3 # yet. :cool:
[Verizon Samsung Galaxy S III] zachf714:
Man you don't get to see my surprise yet lol, I am trying to think now what would cause it to black screen now. Does the led start to flash? Maybe we need to modify the init scripts now so they don't try to call selinux
[Verizon Samsung Galaxy S III] prdog1:
Never goes black. Stuck as Galaxy S3 splash. :cool:
[Verizon Samsung Galaxy S III] zachf714:
Mhhm... I think that would be init

Edit - I bet if you set adb to insecure it will start
[Verizon Samsung Galaxy S III] golfslicer:
Will this work on this mod?

Fix Boot Loop Issue On Verizon Galaxy S3 SCH-I535

If Verizon Galaxy S3 SCH-I535 stuck at booting animation for more than 10 minutes

Go to recovery mode. To do so, press and hold the Volume Up, Home and Power buttons together.

Now perform Wipe data/Factory Reset and Wipe Cache Partition task before selecting reboot system now function. In recovery mode use Volume keys to navigate between options and Power key to select the option.

I answered my own question, no it didn't work. I tried the system dump with 4.4.2 kernels and the one from the system dump. None will boot the system.but they don't go black like the verizon kernel.
[Verizon Samsung Galaxy S III] tayswg20:
Deleted
[Verizon Samsung Galaxy S III] zachf714:
its not a bootloop, its that it does not boot at all. A firmware check is stopping the kernel from being unpacked into memory which is keeping the device from booting
[Verizon Samsung Galaxy S III] Surge1223:
Hi all, I dont know if you guys have tried patching the zImage to load on older bootloaders or not but im going to attempt to help by doing so. I talked to [MENTION=4395895]BeansTown106[/MENTION] about this a little but im just getting caught up. Im compiling the kernel from source now but im curious, we ran into a similar issue on the S4 and we had to have 2 things to boot 4.4.2;

1. Stock 4.4.2 kernel

2. Stock 4.4.2 HLOS

Has this been attempted? The HLOS (High level Operating System) is intrinsically linked to the kernel, and as much holds most if not all the AMSS for the S3. I will report back on what issues I find blocking 4.4.2 from booting on older bootloaders, and if someone has already figured this out then please let me know, as this is a time consuming task.

Thanks.
[Verizon Samsung Galaxy S III] BeansTown106:
Surgicals to the rescue ;)
[Verizon Samsung Galaxy S III] n3wt:
Scott said that he had left the HLOS in the patch when he was trying to get this to boot and he had no luck. I've been poking at it a little but I'm just learning. compiled my first kernel yesterday.
[Verizon Samsung Galaxy S III] Surge1223:
Alright, compiled the kernel from source. Now im looking at where it decompresses the zImage and what it requires to boot.

Places to start researching to help:

$KDIR/arch/arm/boot/

$KDIR/arch/arm/mach-msm

Using Objdump and ldd on the following will also yield info:

$KDIR/vmlinux.o

$KDIR/System.map

$KDIR/kernel/module.o

The below is for reference and consistency (in case any of us used different variables or settings should we need to rule them out):

etc..etc..yeilding
[Verizon Samsung Galaxy S III] CNexus:
Careful. We found out the hard way on the Sprint S3 that flashing any part of the 4.4 firmware while on a 4.3 bootloader bricks the device. It will boot up once and show no signal/network info, and then the next reboot it won't ever turn on.
[Verizon Samsung Galaxy S III] prdog1:
[MENTION=4939386]Surge1223[/MENTION]. Welcome aboard. We need all the help we can get. :cool:

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] Surge1223:
I dont plan on using any part of the 4.4.2 firmware, thanks for the heads up though. Im looking at the conditions the compressed kernel unpacks under before boot. What part of the firmware did you guys flash on the sprint s3?

P.S. maybe all in here can discuss this on hangouts?

surge1223@gmail.com

Also if someone could do the following and upload the seclog.txt produced at the end it would speed things up. (steps 1 & 2 may not be necessary)

1. Enable HiddenMenu via editing /efs/carrier/HiddenMenu from OFF to ON.

2. Dial *#9900# and make sure SecLog is enabled.

3. Download viewmem on to your phone from here

4. Open terminal emulator and copy and paste the code below

su
mount -o remount,rw /system
setenforce 0
find . -name "viewmem" -exec cp {} /data/local/tmp \;
find /data/local/tmp -name "viewmem" -type f -exec chmod 755 {} \;
./data/local/tmp/viewmem 0x88d00008 0x80000 >/sdcard/seclog.txt
exit
exit
/
[Verizon Samsung Galaxy S III] CNexus:
The modem (NON-HLOS.bin)
[Verizon Samsung Galaxy S III] RRF12:
I have been running the new modem ne1 with old an slows mostly stock an cm 11.Both run great
[Verizon Samsung Galaxy S III] brickbeats:
https://drive.google.com/file/d/0B3jOjXRZcUbmSjFDUDVpRFY3SEU/edit?usp=sharing
[Verizon Samsung Galaxy S III] CNexus:
You need to run each command individually, not all in the same line. Better yet, just copy the code into a script (blahblah.sh file) and then run the script
[Verizon Samsung Galaxy S III] dvaderx:
if no one gets this for you by tomorrow I will do it. I have a spare s3.. it's running 4.1.2 though. do you need it to be updated to 4.3?
[Verizon Samsung Galaxy S III] zachf714:
You can flash the no-hlos and modem... We found this out a long time ago
[Verizon Samsung Galaxy S III] CNexus:
Try that on a 4.3 bootloader with the 4.4 modem and I guarantee you'll brick.
[Verizon Samsung Galaxy S III] bobloblaw1:
I doubt it, but if I can run the cmds surge posted on 4.3 tw (unlocked bootloader, custom ROM) let me know and I'll go ahead and do it.
[Verizon Samsung Galaxy S III] open1your1eyes0:
The only way you can guarantee a brick is with mismatched signed bootchain versions, meaning for example unlocked aboot and 4.3+ sbls. Possibly tz and rpm might come into play as well but I personally have not seen them cause a brick (yet) when the aboot/sbls were matching. Modem and radio (NON-HLOS.bin) should never cause a brick since them, kernel, and system are usually the 3 safest files to flash not needing to match the rest. May cause booting or signal issues for other reasons but never a brick. Should always be able to go back into ODIN mode and restore whatever you need from there.
[One (M8) Q&A, Help & Troubleshooting] CALEDONIANSALTIRE:
Hi all, just received my new HTC one M8 today and glad I went for it, been an avid HTC user since they first came out and am really pleased.

Looking for a bit of advice. I have copied an image onto the front screen as a widget from the android image gallery and then one of one of my own photos, however it is tiny, any way of increasing the size????. On my previous HTC one X it was approx 3/4 centimeter square but on the new M8 it is about a 1/4 square.

Also looking for a case that will protect it from the elements as spend a lot of time in dusty conditions. Looking at the Supcase beetle defender or the Love MEI case. Both these cases have an extra glass and dust covers over the ports. Anyone any advice which to go for????. My only concern re the Love MEI one is that all of them seem to be in China or come from China so not sure of the authenticity.

Thanks again all
[One (M8) Q&A, Help & Troubleshooting] BerndM14:
For suggestions on cases for the device check this thread: One (M8) Accessories There are plenty of threads where they discuss cases.

I'm not really sure about the other point you have, are you using a specific app to make widgets of pics? If so, which? I don't see an option to do such a thing on my phone, so I can't really test it and see if I can find a solution to it. Not much help there, sorry. :(
[General Questions and Answers] pitelasssss:
Whenever I use my GPS on my phone battery runs out instantly. can explain to me why?
[Motorola Droid RAZR] p2daz:
I've just purchased a verizon razr maxx from the states to use over here in the uk.

I've got CM11 installed and running fine, the only niggle I have is the network setup, I've set it to use gsm only but it never displays the signal bars and has the R symbol for roaming permanently on even though roaming is off.

The phone seems to work ok though, I'd just like what is displayed to be correct and know the network is good..

Any ideas?
[Motorola Droid RAZR] p2daz:
I've also just noticed on the lock screen it displays no SIM card - t mobile
[Motorola Droid RAZR] neo.ank:
You will need Gsm Fix to use it on GSM networks outside US

From the E
[Motorola Droid RAZR] p2daz:
I just followed the instructions here Here and all is good...many thanks.
[Omni Features Development] berurier1:
Hello,

Is improving the pattern lock is in progress, by which I mean the possibillity to spend a grid of 3x3 to 4x4 or more?

I also find that face unlock is very slow compared to what CM11 offers such an improvement is planned?

THX
[Omni Features Development] maxwen:
Face unlock is gapps and not in the ROM. Regarding grid config please add it to jira
[Omni Features Development] evolone:
I have been looking for the same. I did not find another JIRA request so I have created one (hopefully done in proper manner)

http://jira.omnirom.org/browse/OMNI-1038
[MDA II, XDA II, 2060 ROM Development] boditza:
I have a 2020 with wm05 on it but its not too functional and i like more 03, besides the processor speed is always on 100%. I am new in this branch and i would like for someone to tell me what should i do, what programs to use, where to get the roms and everything else.
[MDA II, XDA II, 2060 ROM Development] Rudegar:
how you do it

http://wiki.xda-developers.com/index.php?pagename=HimalayaRomkitchen

where you get the stuff

http://wiki.xda-developers.com/index.php?pagename=BA_FTP_Site
[MDA II, XDA II, 2060 ROM Development] dotfred:
You definitely have to go on http://buzzdev.net, there you will find all you need about himalayas and up/downgrades

Cheers,

.Fred
[MDA II, XDA II, 2060 ROM Development] boditza:
Thank you verry much you guys.
[Xperia Z2 Q&A, Help & Troubleshooting] Hally79:
Ok I have a question, I have a really annoying bug while im in a call! The screen goes black as soon as I press the call button,the phone call is fine but when I come to end the call the screen is still black and I cant end the call because there is no response from the screen!! Is anyone else facing this problem? I hope somebody knows how to fix it.
[Xperia Z2 Q&A, Help & Troubleshooting] jeremy.shi:
I'm on .402 and I cannot duplicate the issue. What version is your phone on? Have you tried reinstall the system via sony update service?
[Xperia Z2 Q&A, Help & Troubleshooting] Hally79:
Im also on .402 im at work at the min so cant try anything until I get home. Just checked again and its ok now! But for how long I dont know. Its very annoying if its going to keep doing this!