yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] empthollow:
Here is the output you are looking for

major minor #blocks name

7 0 5229 loop0
7 1 2111 loop1
253 0 409600 zram0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 20480 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 10219520 mmcblk0p29
179 32 15632384 mmcblk1
179 33 15631360 mmcblk1p1
254 0 5229 dm-0
254 1 2110 dm-1

---------- Post added at 02:55 AM ---------- Previous post was at 02:27 AM ----------

I have another question, how do i figure out which block ther kernel is. On my last phone it was /dev/block/bml7 but that doesn't exist here.
[Verizon Samsung Galaxy S 4] Surge1223:
Here are your partitions. As I thought, they are the same as those of MDK and ME7 users. The kernel is at /dev/block/mmcblk0p20 but if you didn't know that, it would probably be easier and safer to find/retrieve it using the by-name method so it would be "/dev/block/platform/msm_sdcc.1/by-name/boot"

major minor #blocks name

7 0 5229 loop0
7 1 2111 loop1
253 0 409600 zram0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1 apnhlos
179 2 52764 mmcblk0p2 mdm
179 3 128 mmcblk0p3 sbl1
179 4 256 mmcblk0p4 sbl2
179 5 512 mmcblk0p5 sbl3
179 6 2048 mmcblk0p6 aboot
179 7 512 mmcblk0p7 rpm
179 8 512 mmcblk0p8 tz
179 9 16896 mmcblk0p9 pad
179 10 13952 mmcblk0p10 efs
179 11 3072 mmcblk0p11 modemst1
179 12 3072 mmcblk0p12 modemst2
179 13 780 mmcblk0p13 m9kefs1
179 14 780 mmcblk0p14 m9kefs2
179 15 780 mmcblk0p15 m9kefs3
179 16 2826240 mmcblk0p16 system
179 17 8192 mmcblk0p17 persist
179 18 2119680 mmcblk0p18 cache
179 19 6144 mmcblk0p19 param
179 20 10240 mmcblk0p20 boot
179 21 10240 mmcblk0p21 recovery
179 22 10240 mmcblk0p22 fota
179 23 6144 mmcblk0p23 backup
179 24 3072 mmcblk0p24 fsg
179 25 8 mmcblk0p25 ssd
179 26 9216 mmcblk0p26 persdata
179 27 20480 mmcblk0p27 hidden
179 28 20480 mmcblk0p28 carrier
179 29 10219520 mmcblk0p29 userdata
179 32 15632384 mmcblk1
179 33 15631360 mmcblk1p1
254 0 5229 dm-0
254 1 2110 dm-1
[Verizon Samsung Galaxy S 4] empthollow:
still no love with dd

$ adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/kernel bs=4096
/dev/block/platform/msm_sdcc.1/by-name/boot: cannot open for read: Permission denied
$ adb shell ls -l /dev/block/platform/msm_sdcc.1/by-name/boot
lrwxrwxrwx root root 1970-01-16 14:58 boot -> /dev/block/mmcblk0p20
[Verizon Samsung Galaxy S 4] Surge1223:
Root first using the same method as described for me7 should work
[Verizon Samsung Galaxy S 4] evilryry:
so that would work.. i wish i could verify the kernel posted works perfectly so i could go ahead and do it and not brick/break my phone
[Verizon Samsung Galaxy S 4] Surge1223:
Using the me7 root method doesn't involve using the kernel. Its just the extSdCard commands. It takes five minutes to root.
[Verizon Samsung Galaxy S 4] exeterx:
I've tried the me7 root on mine and it did not work. It gives some permission errors when running the ./pwn command and yes my SD card is formatted in exfat.
[Verizon Samsung Galaxy S 4] empthollow:
I have tried that root method and formatted my card several times. It did not work for me either. My errors were about permissions as well. I am on linux so I used the linux exFat tools. I wondered if i did something wrong but if it didn't work for you either then they probably patched it.
[Verizon Samsung Galaxy S 4] k1mu:
On your phone, bring up a terminal and type "mount".

Look for the line containing "/storage/extSdcard". What are the mount options? If it says "noexec" then either it's not exFAT or the hole that's being used to run the root exploit (exFAT devices aren't mounted with noexec) has been fixed.

When the disk is mounted with "noexec", that means that you can't execute programs from that device, hence the "permission denied".
[Verizon Samsung Galaxy S 4] Surge1223:
Post the output from terminal
[Verizon Samsung Galaxy S 4] Surge1223:
Mine looks like this

storage/extSdCard exfat rw,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=utf8,namecase=0,errors=remount-ro 0 0
[Verizon Samsung Galaxy S 4] empthollow:
The things I would question are the nosuid tag and the fact that I don't see an exec tag
[Verizon Samsung Galaxy S 4] hilltopper06:
It also looks like our devices are not registering the exfat filesystem like the 545 does. I will try formatting again, I did switch to a different microsd card last night and I don't remember what I formatted this one too (I know the previous was exfat and it didn't work on it).
[Verizon Samsung Galaxy S 4] evilryry:
getting the same thing here. permission error. sdcard formatted to exFAT. any other methods anyone think could work? im not super dev-savvy but i would think the mdk method and reflash stock kernel wouldnt work either.
[Verizon Samsung Galaxy S 4] setharterburn:
Excited to see the outcome. The bloated Samsung software is killing me. craving some stock rom action. thanks guys. btw, are you guys local ky guys?
[Verizon Samsung Galaxy S 4] empthollow:
I'm in WI, I have cellcom which is the rural carrier here.
[Verizon Samsung Galaxy S 4] empthollow:
Does anyone know for SURE if the bootloader is locked on this phone? I assume because there is some connection to VZW that it is but i don't know how to test that. If we could get CWM or TWRP on here that would be the easiest way to get root.
[Verizon Samsung Galaxy S 4] setharterburn:
I work for bluegrass cellular. I have ties to top level management and technical support. If I can be of any assistance please let me know.
[Verizon Samsung Galaxy S 4] empthollow:
Can you get a copy of the stock software? It would be easier for us to try different kernels and roms if we could be assured that we could return to stock. The file would be something like I545L-stock.tar.md5. I built a kernel but but I'm not sure if it will work because no one has tried it.
[Verizon Samsung Galaxy S 4] Surge1223:
Actually the file would say something similar to 1545nnnnnn_xxxxxx_REV06_user_low_ship_MULTI_CERT.tar.md5. Where the n's=build and the x's=string of numbers. Just saying.
[Verizon Samsung Galaxy S 4] empthollow:
Interesting,I was not aware of that. ....whatever it's called though, I would like to be able to sow load it . Lol
[Verizon Samsung Galaxy S 4] setharterburn:
Just let me know what you want me to do. I have access to every smartphone we have. Including the htc one we just got in yesterday
[Verizon Samsung Galaxy S 4] empthollow:
What kind of access do you have? The file we are looking for would likely be available in your service department. You would need to get it on a flash drive or something and then upload it to a site like minus.com so we can download it. One we have it we can try different kernels and roms without running the risk of being left with a soft bricked phone for a couple days. Odin is the program that they would be using to flash the file if that helps you locate it.
[Verizon Samsung Galaxy S 4] setharterburn:
I do repairs for the company. I also work in sales and service. I can get access to some files. Would it be easier to get the files from hq or get the software off of the phone itself? I just recently moved from iphone to android. Im new here. I do hardware repairs so this is new. Enlighten me however you can. Thank you in advance.
[Verizon Samsung Galaxy S 4] evilryry:
Software from hq would already be compiled perfect for the device. It would be the best option, if you can in any way get it to us. I'm a bluegrass customer and I would love to root this mug lol.
[Verizon Samsung Galaxy S 4] empthollow:
Agreed, HQ would be perfect!
[Verizon Samsung Galaxy S 4] setharterburn:
I will call tier 3 tomorrow and see what I can get. If they give it to me, do I just need the rom? Or do I need kernel and other software as well?
[Verizon Samsung Galaxy S 4] evilryry:
Firmware would be ok. Rom may help. And Idk if they will be able to give the kernel alone. If so, cool beans. The kernel would probably help the most but we can probably figure something out.
[Verizon Samsung Galaxy S 4] empthollow:
it will be a file ending in tar.md5 like surge1225 said it will be named something like this 1545nnnnnn_xxxxxx_REV06_user_low_ship_MULTI_CERT.tar.md5. This is an archive that will contain the kernel and radio and system partition and, well, everything that you need to make the phone work. If you want to check it rename the file so that the end is '.tar' instead of '.tar.md5' The open it with an archive manager like 7zip if you are on windows. You will see a bunch of files including 'zImage' which is the kernel, 'factoryfs.rfs' which is the system partition as well as 'boot.bin' 'cache.rfs' and some others. Some of the names may vary, I'm basing this on the stock for my i500.
[Verizon Samsung Galaxy S 4] setharterburn:
Okay cool. If it helps at all. Any 4g LTE verizon phone works great on bluegrass. Phone calls work. Internet works. The only thing that doesnt is messaging. If that worked. Id have a note 3.. lol
[Verizon Samsung Galaxy S 4] hilltopper06:
That is what I noticed recently with one of my coworkers here using a Verzion LTE phone on bluegrass (but her messaging doesn't work quite right, like you mentioned)

I am really hoping you can help get us rooted/romed. Thanks!
[Verizon Samsung Galaxy S 4] empthollow:
I have bever found a rom for my provider sobi have used verizon roms. Txt works in all of thwm but mms is no good. I know there is a way to fix it by changing the apns but b ibhave not been successful. However, it may be because I was trying tobuse a gingerbread apns.conf with jellybean. I am hoping to figure it out with this phone when i get root.
[Verizon Samsung Galaxy S 4] setharterburn:
What would cause the messaging error??? You guys dont understand. I want a note 3 so bad. If I can make it work. Ill send you whatever you want!
[Verizon Samsung Galaxy S 4] empthollow:
First of all you need root to fix it. Once we get root on this I will be trying to figure it out because I am a sucker for cyanogenmod and I have to use a vzw rom in order to use it. Which means by default mms is wrong for my carrier.
[Verizon Samsung Galaxy S 4] setharterburn:
Sounds like a winner
[Verizon Samsung Galaxy S 4] setharterburn:
Called tier 2. He understood our needs but let me know that they flash all of the phones in the store. Im not sure which store theyre speaking of because we dont do that. Im gonna do more research and let you guys know
[Verizon Samsung Galaxy S 4] evilryry:
im still unsure as to how we are actually going to root these things first.. lol. wish we had one of those awesome, skilled android developer help.
[Verizon Samsung Galaxy S 4] empthollow:
Yeah I hear ya. Im hoping the me7 pre release kernel allows the motochopper exploit to work.

Meanwhile, i have an i500 aka galaxy s / showcase I am going to flash back to stock and then flash a kernel built from it's source. If that works it's a good bet my i545l kernel will work.
[Verizon Samsung Galaxy S 4] setharterburn:
Guys keep in mind I have an unlimited source to these phones. I can send a dev a phone to work on
[Verizon Samsung Galaxy S 4] hilltopper06:
Tier 2 was feeding you a line. Unless things have changed for the S4 in particular, the store could not do anything for my X2 when it needed to be factory flashed. They said it would have to be shipped to Bowling Green. Bowling Green shipped it back unflashed (meaning they couldn't do it either). I finally got my corporate rep to give me a loaner and take mine. He brought mine back in a few days (it was definitely my device), but it had been flashed. The stores have not historically had the recovery images for the phones. They have software to provision phones, but not factory restore a phone that is not working at all (cannot boot to recovery or android). I would try someone at corporate if you have a contact there.
[Verizon Samsung Galaxy S 4] setharterburn:
I have contacts everywhere. Go to church with the vp. I just dont know who would know
[Verizon Samsung Galaxy S 4] k1mu:
If you're willing to loan a phone, there's a pretty good chance that I could hack the ME7 root exploit to work. PM if you're interested.
[Verizon Samsung Galaxy S 4] evilryry:
Is there any way you could help us with out a loaner..? By system and partition info etc. I want the me7 to work too. But I can't loan the phone.
[Verizon Samsung Galaxy S 4] setharterburn:
is it necessary that I loan the phone? Im not that loaded to shell out 680 bucks to a guy who I dont know who will do god knows what. I want to get this done along with figure out the issues with the verizon phones on bluegrass. But you must understand how difficult it would be to just hand someone this phone
[Verizon Samsung Galaxy S 4] kmg90:
Having a supply to a loaner device would allow developers to crack the phone a little more aggressively since there is no personal value to the device (getting a new phone and trying to root it bricks the device leaves you in a potentially costly situation)
[Verizon Samsung Galaxy S 4] setharterburn:
I would love to get this going. But if a dev breaks it I gotta pay 680 because im responsible
[Verizon Samsung Galaxy S 4] k1mu:
Hacking the i545 ME7 root to recognize your phone is possible and fairly safe and wouldn't require you to send a phone anywhere.

If that doesn't work, then it's going to need to be in the hands of a seasoned root hacker (which I am not by any means).
[Verizon Samsung Galaxy S 4] evilryry:
Can you make any modifications to the me7 and post it for us to try first?
[Verizon Samsung Galaxy S 4] k1mu:
The change is quite simple. There's an exploit for ME7 - http://xdaforums.com/showthread.php?t=2380325

That's been reported to work with MI1, which is a newer release than your phones, so it should work for your devices.

The problem is that the exploit in that package only gets tried if your phone has version JDQ39.I545VRUAME7

So, the simple thing to do is to patch the exploit so it'll run on whatever version your phone has.

Settings/About Phone. What's in the "Build number" field?

I can change the ME7 root exploit to try on that version and post a copy to test.
[Verizon Samsung Galaxy S 4] hilltopper06:
JDQ39.I545LWWUAMG6

Please and Thank You!
[Verizon Samsung Galaxy S 4] k1mu:
Another question - what's the "Model number" on that same Settings/About Device page?
[Verizon Samsung Galaxy S 4] hilltopper06:
SCH-I545L
[Verizon Samsung Galaxy S 4] k1mu:
OK, that's what I thought. PM sent with a copy of the hopeful root hack.
[Verizon Samsung Galaxy S 4] hilltopper06:
Tried it, no go.

"Attemp fb_mem exploit...

Failed to open /dev/graphics/fb0 due to Permission denied

You need to manage to get remap_pfn_range adresses.

Failed to get prepare_kernel_cred addresses.

Failed to get comit_creds addresses.

Failed to get ptmx_fops addresses.

(JDQ39.I545LWWUAMG6) is not supported.

Failed to setup variables."
[Verizon Samsung Galaxy S 4] k1mu:
OK, one last try - grab the updated zip file and see if that's any better. The " (JDQ39.I545LWWUAMG6) is not supported." message means that the first edit I tried failed.
[Verizon Samsung Galaxy S 4] hilltopper06:
segmentation fault when I run ./pwn
[Verizon Samsung Galaxy S 4] k1mu:
Crap. I can see why - the version string is longer (it starts with I545L, not I545) so editing that in the pwn binary failed.

If I had the source code for the exploit, it'd be an easy fix. Apparently, however, I can't use a binary editor to hack this. Sorry, but I thought it worth a try.
[Verizon Samsung Galaxy S 4] hilltopper06:
Thanks for trying!
[Verizon Samsung Galaxy S 4] k1mu:
I've found the source for the exploit, but it needs to be tailored for each kernel build for a given device.

I've built a new 'pwn' with the same addresses as the standard I545 if you want to give it a try. Same web server as before, file 'pwn'.

It's not likely to work without customization; I'd need a copy of the boot.img from your device, or a stock rom ODIN file for it, to figure out the necessary changes.
[Verizon Samsung Galaxy S 4] hilltopper06:
I will try it in the morning. My 2gb SD card I set aside for testing is sitting on my desk.
[Verizon Samsung Galaxy S 4] evilryry:
heres a kernel to try, built from source by a fellow poster on this forum.
[Verizon Samsung Galaxy S 4] evilryry:
also open source available if that doesnt work
[Verizon Samsung Galaxy S 4] k1mu:
Thanks, I'll pull this and see if I can rebuild the exploit for that specific kernel.

It might not work as the offsets to the required kernel symbols may change when rebuilt from source, but it's worth trying.
[Verizon Samsung Galaxy S 4] hilltopper06:
Tried it, it made it further (past the build check) but still failed at running some exploits with permission denied.
[Verizon Samsung Galaxy S 4] k1mu:
So, that means one of two things - either the kernel you're running has the exploit fixed, or the kernel that you posted isn't identical to the one on your phone. What's the kernel revision on your phone? (Settings/About phone/Kernel version).

Here's what that kernel has for a rev level:

Linux version 3.4.0 (empthollow@archam) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Oct 5 17:03:02 CDT 2013

This is frustrating. I think this is close, but the phone won't let you pull the running kernel without root.
[Verizon Samsung Galaxy S 4] lumpy973:
Mine is also i545l but with pioneer.

Kernal version

3.4..0-1218139

se.infra@SEI-33 #1

Fri Jul 26 20:08:25 KST 2013

Hope this helps the cause.
[Verizon Samsung Galaxy S 4] k1mu:
OK,so the kernel is basically the same version where the exploit for ME7 works, so it should still work.

I've made another change to the 'pwn' program as I've found another file that needed to be edited to add the 545L. Please download and give it another try.

If it fails, I'd appreciate a screen-shot of what happens so I can look further. Thanks!
[Verizon Samsung Galaxy S 4] evilryry:
Wat?
[Verizon Samsung Galaxy S 4] k1mu:
Sorry, quoted the wrong person.

I've built a version of the SCH-I545 root exploit for the 545L and sent a pointer to a couple of people via PMs. Unfortunately,

it's not yet working.
[Verizon Samsung Galaxy S 4] evilryry:
You sent it to me too, it spams the errors that's it
[Verizon Samsung Galaxy S 4] evilryry:
Any progress on this buddy?
[Verizon Samsung Galaxy S 4] lumpy973:
evilryry is your kernel version same as mine? Posted earlier. Sorry for interrupting earlier. Looking for root also. New to droids
[Verizon Samsung Galaxy S 4] lumpy973:
I type "mount" as you said and im not getting the "noexec" so how can I use me7 exploit. How to reconfigure.
[Verizon Samsung Galaxy S 4] evilryry:
Yeah, same deal. Appears so far all the 545L's have the same kernel
[Verizon Samsung Galaxy S 4] k1mu:
Nope, I've sent a PM to the author of the ME7 exploit but no response yet.

It's a pretty easy change to that now that folks have supplied the proper kernel, but I haven't been able to get the code necessary to build it.

I'll post here if there's any progress.
[Verizon Samsung Galaxy S 4] Surge1223:
k1mu, can you pm the exploit you made (the modified pwn, etc)? I would've pmed you and asked but I cant select individuals to quote or pm, etc. on the xda app on my razr.
[Verizon Samsung Galaxy S 4] evilryry:
forwarded his link he sent me pm
[Verizon Samsung Galaxy S 4] k1mu:
There's nothing working at the moment, so there's no point in passing the current attempt around.
[Verizon Samsung Galaxy S 4] Surge1223:
Just attempting to help. But your file, your choice. Also to the others reading please remember to ask permission from the owner of content before posting/sharing
[Verizon Samsung Galaxy S 4] lumpy973:
When I mount its coming. Back exactly like surge1223 post his said. I rally appreciate and admire the help and working together people use on the form. Thanx.
[Verizon Samsung Galaxy S 4] evilryry:
My bad surge and k1mu, was just trying to help out. Not

---------- Post added at 09:43 PM ---------- Previous post was at 09:43 PM ----------

Not trying to rush *
[Verizon Samsung Galaxy S 4] k1mu:
No worries. Patience. :fingers-crossed:
[Verizon Samsung Galaxy S 4] lumpy973:
Was wanting to mess with universal de la vega but cant find stock firmware. I enabled secrete phone key pad codes to get

AP: I545LWWUAMG6

CP: I545LWWUAMG6

CSC: I545LLRAAMG6

RF CAL: 2013.08.24

HW Rev.: I545L.00

Dont know what good itll do but here it is. Goodnight all
[Verizon Samsung Galaxy S 4] empthollow:
So far I haven't seen stock firmware for any of the rural carriers which are the only ones who have this build. None of us want to lose our stock option;) otherwise I think a rooted vzw build could be flashed for root.
[Verizon Samsung Galaxy S 4] k1mu:
My latest attempt at rooting this phone sadly failed. I'm forced to assume that the exploit has been patched for this model, so we'll need something else.

Root de la Vega is a good possibility if we can get the stock firmware. Until then, we're stuck.
[Verizon Samsung Galaxy S 4] lumpy973:
Bare n mind im new to droids. Is it possible to use kies, or simular to download my stock firmware? Kinda like using itunes and putting fone in dfu mode so it would give firmwares?
[Verizon Samsung Galaxy S 4] empthollow:
Kies is an update utility. There is dowload mode which is similar to dfu but you need Odin or heimdall. Odin is leaked and heimdall is open source. Kies is the updater utility but it contacts a server and gets the latest software forbyou r carrier. If you don't have stock software it will not recognize your phone. Kies is not used in download mode. Hope that helps.
[Verizon Samsung Galaxy S 4] k1mu:
One way we might be able to get a ROM image for you phones is to use the "VZ Software Upgrade Assistant" on your phone.

For the Verizon model, when you plug it into your PC, a virtual CD-rom appears as a disk drive that allows you to install the assistant.

If you tell it to repair your phone, it'll download the stock rom - for VZ, that download goes to %AppData%\Verizon

(i.e. C:\Users\{username}\AppData\Roaming on Windows 7 and later.)

You can navigate to that folder using the "%AppData%" address in Windows Explorer. A new folder will get created to hold the download. You just need to copy that file off before the installer starts to install it.

If you can try this it might just get us the ROM image that I need. BE VERY CAREFUL, however - running this WILL WIPE YOUR PHONE.
[Verizon Samsung Galaxy S 4] evilryry:
So I can try to download the assistant and see if it can recognize my phone

---------- Post added at 06:03 PM ---------- Previous post was at 06:02 PM ----------

Also is there any way to build a stock rom image and stuff from the open source?
[Verizon Samsung Galaxy S 4] k1mu:
You can build a stock ROM, but you can't sign it, and it needs to be signed with the Samsung key to be considered valid by the bootloader.
[Verizon Samsung Galaxy S 4] evilryry:
wondering too, any thoughts if our phones will get the 4.3 update eventually? i cant find any information on any releases other than the 4 major carriers. samsung did say "all US models" will get it, but only 4 dated so far. at that point it may be possible to get a firmware file too?
[Verizon Samsung Galaxy S 4] evilryry:
bumping for potential
[Verizon Samsung Galaxy S 4] lumpy973:
A very smart and helpful member here pointed me in the right direction. Kingo app worked on my i545l. Its a windoze program. And I had to stop everthing else. From running. It took quite awhile for it to download install and connect to device. 1st few times even failed downloading drivers. But after kept rebooting pc and. Phone it finally worked. Im rooted. Now what is out there for me lol