I'm potentially just unaware, but I came across EXE files that are like a modified version of ODIN, look completely different from ODIN and google has provided zero information on even the title of the program. I believe it just straight up compiles the steady.bin from nothing but the DID and flashes it to the device unlocking it. It's an S908U. There is no option to insert TARs or anything. Attached is an image.
hello
i think it's another version of ThorOneClick for linux ( tizen )
yakapa40 said:
hello
i think it's another version of ThorOneClick for linux ( tizen )
View attachment 5638187
Click to expand...
Click to collapse
But this one unlocked bootloader on a S908U for a publicly locked carrier, thats gotta be significant for someone.. i tried decompiling the exe but got nowhere.. I saw snippets of "steady" in the disassembly so i know its built in i just dont know if its some sort of universal key i suppose for unlocking these phones
throwaway1258 said:
But this one unlocked bootloader on a S908U for a publicly locked carrier, thats gotta be significant for someone.. i tried decompiling the exe but got nowhere.. I saw snippets of "steady" in the disassembly so i know its built in i just dont know if its some sort of universal key i suppose for unlocking these phones
Click to expand...
Click to collapse
Where's the file?
wolfu11 said:
Where's the file?
Click to expand...
Click to collapse
Bit skeptical on uploading due to where/how it was obtained, because Samsung will likely not enjoy it being public. But I just used one up, the odin logs are attached. Id prefer to send it to the guys that work on the unlocking for the public and not for a shady pay site.
Also I think it's an ENG token
anyway you can DM me the file location?
apatcas said:
anyway you can DM me the file location?
Click to expand...
Click to collapse
I'm combing through the assembly in Ghidra and there's too much PII in there, and confirmed it is an engineering token. Can't risk it. Maybe I can extract the disassembly/decompile and upload the functions that handle the imaging and encryption, unless someone reputable in unlocking hops in the thread and can help me out.
This is just an exe combine odin and your token and it will flash the token that was generated for your device only.
So its not a token generator.
afaneh92 said:
This is just an exe combine odin and your token and it will flash the token that was generated for your device only.
So its not a token generator.
Click to expand...
Click to collapse
Yes I know it generates the token, but I want to know if it can be reverse engineered to change the DID and other device specific variables
throwaway1258 said:
Yes I know it generates the token, but I want to know if it can be reverse engineered to change the DID and other device specific variables
Click to expand...
Click to collapse
Contact me
throwaway1258 said:
Yes I know it generates the token, but I want to know if it can be reverse engineered to change the DID and other device specific variables
Click to expand...
Click to collapse
The guy you need too contact is @afaneh92
He is trustworthy and one of the most knowledgeable people around plus. I work with him all the time.
jrkruse said:
The guy you need too contact is @afaneh92
He is trustworthy and one of the most knowledgeable people around plus. I work with him all the time.
Click to expand...
Click to collapse
Confirmed. Knows his stuff and built Twrp for my device S22U Exy
Totally trustworthy
Following. Hopefully something comes of this...
oncestruck said:
Following. Hopefully something comes of this...
Click to expand...
Click to collapse
It might, but once @afaneh92 gets ahold of it, it's gonna cost us all a sht ton of $ to use it.
bs3pro said:
It might, but once @afaneh92 gets ahold of it, it's gonna cost us all a sht ton of $ to use it.
Click to expand...
Click to collapse
I'd pay for someone's work. I don't know what you mean by assuming one would charge an exorbitant fee.
phr0zen said:
I'd pay for someone's work. I don't know what you mean by assuming one would charge an exorbitant fee.
Click to expand...
Click to collapse
Someone should release it for free, and people should be able to donate. Not everyone has $ laying around.
bs3pro said:
Someone should release it for free, and people should be able to donate. Not everyone has $ laying around.
Click to expand...
Click to collapse
Be that as it may, you assumed there would be an inherent inflated cost based solely on the possibility of one particular individual's work. Who knows if it's even possible? I sure as hell don't. But I am saying that I would donate to the cause. I'm sure @afaneh92, along with anyone else would like a coffee, or a beer or 3.
If anyone knows how to decrypt hex signature, feel free to have a crack at it
Upload it I'll give it a go
Related
Hi folks!
My desire should arrive within a week or so. The past days i tried to collect as much data about getting full root-access with r/w access to /system.
We probably need a modified SSPL and a HardSPL. So far i've tried to contact cmonex, gauner1986 and haykuro to help us here.
So there is the first question to you (desire owners): Do we have jtag on the desire? Haykuro asked me; jtag is required otherwise testing is impossible.
Haykuro said:
you guys got jtag on it? If not it'd be brick heaven as we work on that
Click to expand...
Click to collapse
UPDATE 1:
We found one device with r/w-access to /system, but we don't know where the security flag is set, so we can't set it to "normal" phones.
Adam235 is currently analyzing the dumped files.
UPDATE 2:
ahmgsk provided his recovery. Playtime.
http://www.multiupload.com/XTRBWD6ML2
Update 3:
Nand was unlocked for the EVO 4G. Maybe this helps us.
Update 4:
New root method, which should work with any new 2.1 HTC Phone, but we still don't have full write access to /system:
http://forum.androidspin.com/showthread.php?p=13939#post13939
Well first off, good luck.
Don't we need schematics to know that or at the very least to rip apart the Desire to access motherboard and possibly find JTAG pins ?
Any less barbaric way? :<
sruon said:
Well first off, good luck.
Don't we need schematics to know that or at the very least to rip apart the Desire to access motherboard and possibly find JTAG pins ?
Any less barbaric way? :<
Click to expand...
Click to collapse
It seems this is the only way...
Anyone has high res picture of the desire MB ?
i6bazar said:
Anyone has high res picture of the desire MB ?
Click to expand...
Click to collapse
some one have posted it on modaco irc channel, but u need a full working xda-china account, after register i still have problem
http://www.xda-china.net/thread-52190-1-1.html
Here's some pictures of the Desire. Credits to original poster(百事可乐) of Xda-china !
Judging by the usb bricking showing the phones as qualcomm devices, and further by the mention of some Qualcomm development/debug tools mentioned on XDA, i'd say if anything, the JTAG connection is obtained via the USB port, and is activated by somehow switching the device to the debug mode.
alias_neo said:
Judging by the usb bricking showing the phones as qualcomm devices, and further by the mention of some Qualcomm development/debug tools mentioned on XDA, i'd say if anything, the JTAG connection is obtained via the USB port, and is activated by somehow switching the device to the debug mode.
Click to expand...
Click to collapse
It think also that this can be a possibility
Ahem...I think you mean joint first JD.
Thanks for the input so far.
Over at modaco someone got a phone with full r/w access to system.
Anyone got an idea which addresses we need to dump the spl with pmemdump?
Here is the link to modaco. The user is called maddoxus.
http://android.modaco.com/content-page/309939/usb-brick-rickrolled-b0rked-fixed/page/120/#
Kubino is working on dumping the spl!
allla said:
Here is the link to modaco. The user is called maddoxus.
http://android.modaco.com/content-page/309939/usb-brick-rickrolled-b0rked-fixed/page/120/#
Kubino is working on dumping the spl!
Click to expand...
Click to collapse
We have dumped hidden part (containing radio, spl, splash ....), Adam235 is analyzing the dump.
kubino99 said:
We have dumped hidden part (containing radio, spl, splash ....), Adam235 is analyzing the dump.
Click to expand...
Click to collapse
This is fantastic news, a proper root may be possible now
DocRambone said:
This is fantastic news, a proper root may be possible now
Click to expand...
Click to collapse
We don't know yet if we are able to write to hidden part, assuming it would be not that easy. ;-)
kubino99 said:
We don't know yet if we are able to write to hidden part, assuming it would be not that easy. ;-)
Click to expand...
Click to collapse
Maybe Adam235 or you should also try to contact haykuro or cmonex.
allla said:
Maybe Adam235 or you should also try to contact haykuro or cmonex.
Click to expand...
Click to collapse
We have found yesterday that superCID can be achieved by setting 2 flags in NAND. One we have successfully set, the other one seems like it's in radio section.
kubino99 said:
We have found yesterday that superCID can be achieved by setting 2 flags in NAND. One we have successfully set, the other one seems like it's in radio section.
Click to expand...
Click to collapse
And the second flag is not changeable?
brilliant news..would be good if info could be found as and when its happening-is ther an Irc channel floating about where announcements and info is shared?
dread123 said:
brilliant news..would be good if info could be found as and when its happening-is ther an Irc channel floating about where announcements and info is shared?
Click to expand...
Click to collapse
irc.freenode.org #modaco
allla said:
And the second flag is not changeable?
Click to expand...
Click to collapse
we don't know yet where it's exactly, it's not so easy to find. you can connect to modaco IRC and involve in development.
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.
swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera. Is there an alternate recovery available anywhere for this device? TWRP or CWM? I have posted the update here I am hoping it includes the remote viewfinder functionality that was originally missing from this version.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Update: I had changed the GmsCore.apk file...luckily i had backed it up. After restoring the original file the update applied is applying....Hopefully Root will remain will post update as soon as it completes.
Update: SuperSU says it was able to restore Root Access whoohoo!
Last Update: This does finally bring the Remote Viewfinder capability to the stock camera app.
Click to expand...
Click to collapse
I give up. How did you root this device in the first place?
perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.
Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app
perlmane said:
Where does one find 4.1.1
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.
swjpilot said:
I would try installing Kies and having it restore the firmware. It will most likely put you back on the original firmware but i don't know that for sure. Worst thing that could happen is a factory reset of your device and you stay on your current code level.
Click to expand...
Click to collapse
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.
perlmane said:
VZW products do not support Kies firmware updates. 4.1.1 does not seem to be available anywhere for this device.
Click to expand...
Click to collapse
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......
swjpilot said:
Well i saw this post as well not sure if you have been through it or not..... but this is the last thing i got for you. I have not been able to find the original firmware anywhere either myself.
http://forum.xda-developers.com/showthread.php?t=2086636
Sorry......
Click to expand...
Click to collapse
Since VZW does not support Kies firmware updates, I am afraid to try it. I will have to wait until someone finds the 4.1.1 release of this device and ODIN it.
Anyone still have the boot.img for the latest verizon? Even the full update will work to extract it. This is the only missing piece to extending the custom kernel to all variants.
perlmane said:
I give up. How did you root this device in the first place?
Click to expand...
Click to collapse
swjpilot said:
ExynosAbuseAPK before the first update. You may be able to ODIN back to 4.1.1, run that tool then keep your root through the subsequent OTA's.
Click to expand...
Click to collapse
If you are still around can you confirm you used the "Exynos" Abuse apk to root your Verizon GC120. The Samsung specs page for it aren't clear about whether it's an Exynos quad core using a qualcomm board or an entire qualcomm chipset/board. Thanks!
And if anyone Verizon has found a way to root the current Verizon version and/or the odin file for 4.1.1 please reply here or let me know! Thanks!
swjpilot said:
I have been notified of an update for my EK-GC120 (6ca5626c77cd.update_EK-GC120_GC120VRALL2_To_GC120VRAMC4_FWD-1.zip) is the file i pulled from the cache folder but it refuses to apply to my camera.
http://d-h.st/users/swjpilot/?fld_id=16995#files
Click to expand...
Click to collapse
That link is dead end. Can you please repost that firmware update?
Another thing I learned while I had my ATT galaxy tab 8.9 was that Samsung likes to use the same hardware in their South Korean version of their devices with cellular and in their US devices with cellular. It's almost certainly because of the LTE requirement. Wouldn't you know that such is the case with the Galaxy Camera. The South Korean version of the camera has a Qualcomm board just like the Verizon one. Maybe the firmware for it, which can be found on Sammobile at the link below, can be helpful.
http://www.sammobile.com/firmwares/1/?model=EK-KC120S&pcode=0
EDIT: To clarify more, the Korean version uses a Qualcomm 9215 baseband board with Exynos 4412 while the Verizon version (based on Samsung own specs page) uses a Qualcomm 9615 which has it's own applications processor.
CPU Z says the Verizon GC120 DOES use the Exynos 4412 (smdk4x12). It makes no mention of the Qualcomm board on Samsungs' own specs page. They don't make this easy...
Still need any Verizon build anyone has (original 4.1.1 or 4.1.2 update which should be found in /cache).
Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update
twistedumbrella said:
Newest JZO54K.GC120VRAMC4
Previous JZO54K.GC120VRALL2
The one in the op should then be the 4.1.2 update
Click to expand...
Click to collapse
I know you think no one else could possibly know better than you but the link in the op leads to nothing.
Jiggity Janx said:
I know you think no one else could possibly know better than you but the link in the op leads to nothing.
Click to expand...
Click to collapse
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Edit: Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
twistedumbrella said:
E:V:A said that a few posts up. I dunno what your problem is, but the more specific the file name, the better chance of finding the right file. If this section were labelled "Jiggity Janx" and not "Galaxy Camera Android Development" I would be directing every post to you. It isn't, and I'm not.
Click to expand...
Click to collapse
edited out...
You can still likely see what was written in your thread quote notification but it doesnt need to be hashed out here.
Jiggity Janx said:
My problem here starts and ends with you. You cant expect to come across the way you do belittleing or correcting everyone every chance you get and then wonder why someone responds that way to something that appears to be a comment directed at the very last thing stated in the post immediately before yours. You dont get to have it both ways and then act innocent and deflect when you are called out on it.
Click to expand...
Click to collapse
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
twistedumbrella said:
It isn't about feelings, its about development.
Did you try editing the build.prop with the values for the old version and attempting to do a system update? I have not researched how FOTA determines eligibility, but if it is like any normal system app, it uses the system properties.
Click to expand...
Click to collapse
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.
Jiggity Janx said:
Github/Sourcforge - post technical information for development, no interaction or FEELINGS required
XDA - development FORUM that requires HUMAN interaction
Now....
I appreciate the robotic side of you not taking anything to heart and continuing to want to assist. Unfortunately I have to return the model I received as I immediately noticed it had the vzw demo app on it and that the screen wouldn't time out. That means it was a verizon floor model and is unusable as intended. I am returning that one for a full refund but already have another on the way that I have been guaranteed does not have that problem (for $25 less even).
So long story short I am only willing to mess with the files so much. I know one wrong move with the build.prop could cause it not to boot and without a way to restore am not willing to take that chance with one I have to return. I will be able to do more than pull files from the other one once I receive it (and have time).
Thank you again for assisting us all with development on this device.
Click to expand...
Click to collapse
Look at the number of developers who have left xda butt-hurt about some comment a nameless, faceless text blob made about them because of how they read it. The device suffers, the users suffer, and some kid is up in his room crying about a hobby gone wrong.
As for the rollback, it was only theory anyway so if there is any doubt about what to change its better to find an alternative. If you could get images of the partitions from stock condition, it is possible to build the install. At least that is all done off the device where it won't corrupt anything. You could root, get the system, data, cache, and boot then merge those with the Korean release to fill in the missing parts. To the best of my knowledge, the bootloader and such are not region specific. That should be verified first, though, because you can't go back later.
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
this seems more like a user made htc dev, not what true s-off "bootloader unlocked" would be. non the less it should work fine. this probably wont touch the write enabled protection on the device. the only issues i see is until we are truly unlocked we will always have that "samsung custom" on out bootscreens.
spyz88 said:
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
Click to expand...
Click to collapse
He released his source code and such so we need to have someone compile it into a .bat or .exe so we can flash a custom recovery/rom
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
shabbypenguin said:
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
Click to expand...
Click to collapse
well i cant use it as i don't use linux lol.
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
fix-this! said:
well i cant use it as i don't use linux lol.
Click to expand...
Click to collapse
well if you dont use linux you cant make kernels or recoveries
luckily the loki_flash utility that is used to actually put the patched img onto the device works on android so it doenst matter what kind of computer you have
alacrify said:
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
Click to expand...
Click to collapse
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
just means soon we will have bootloader unlocked.... patience
lorijuan1024 said:
just means soon we will have bootloader unlocked.... patience
Click to expand...
Click to collapse
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Bjray said:
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
Click to expand...
Click to collapse
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Update: nand backup was successful. Good start for us, just need the perm fix, but for now, it rocks, it was so nice to see the recovery screen. SWEET
TheAxman said:
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Click to expand...
Click to collapse
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
fix-this! said:
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Click to expand...
Click to collapse
what i meant was a tool that us people that aren't good with the programming language can use.
fix-this! said:
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
Click to expand...
Click to collapse
Agreed, but I do have a jtag box here in hand, and there is no fix for that either, I might have one phone down soon..:
Incoming update from Samsung in 3....2....1.....
I flashed what shabbypenguin provided in his recovery thread and now have a working recovery on my ATT i337!!! :laugh::good::highfive::fingers-crossed:
Thanks to djrbliss for his awesome work!
mr_blanket said:
Incoming update from Samsung in 3....2....1.....
Click to expand...
Click to collapse
simple solution is to not take the OTA. but yes, i see one coming to.
fix-this! said:
simple solution is to not take the OTA. but yes, i see one coming to.
Click to expand...
Click to collapse
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
mattdm said:
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
Click to expand...
Click to collapse
hopefully adam can get us a more permanent solution. but props to dan for his tool.
Couldn't be happier after I get home from watching the hangover I get to unlock this bad boy
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
All right you losers and screwups! Everyone who sucked hard at rooting has reason to rejoice!
Soft-bricking your phone may have been the best thing to happen to you.
Luck smiles on the unfortunate and the stupid today!
Use a download manager to get these files, and check the MD5 of your downloaded file against AndroidFileHost.
Here's the latest rooted version from @diedemus
Here's the original rooted image for the H810PRa-310-410.
Know what you are doing before attempting to flash these files! Flashing the H810PR firmware is done mostly as a last resort for people who have bootlooping AT&T H810s.
Read all the instructions carefully, then follow the instructions in the root thread 1 through 6, except ignore the parts in step 4 where it mentions tar.gz and the filename since you have a rar file and already had to extract the image file from it and rename it to system.img.
You'll see that we have a different command to flash the H810PR compared to what was used on the H810. Here is the code to copy and paste at the # prompt in the command window:
Code:
dd if=/data/media/0/system.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
Paste the above code in the command window, then hit enter and pucker your butt.
Wait for the # prompt to reappear.
Type LEAVE and hit enter.
Prepare to crap your pants again or savor the sweet taste of victory!
Good luck!
Feel free to ask questions, but try searching for an answer first please. XDA is loaded with information, but it's squirreled away deep in various threads. Learning to search XDA is a valuable skill. Even if you don't find an answer to your specific question, you'll learn something anyway.
H810PR is much better IMO than stock AT&T except for the danger of the green blob in the camera. There's hardly any bloat (like 100 less packages on the phone, seriously!), and no CarrierIQ to have to bother disabling. All the stuff AT&T broke is working too.
Cons so far:
Big ol' green dot in the camera. I wouldn't flash this rom unless I had to because of this issue.
No VoLte (voice over LTE). The phone drops to 3G in phone calls. Follow this post to enable LTE outside of a voice call.
Voicemail settings are grayed out. To set up, put your SIM in another phone or call ATT.
Editing options in camera are overwhelming! There's too many things you can change!
Pros:
The phone comes with very little bloat. There's a huge difference in the number of packages, like 100 less.
The stuff AT&T removed or broke is not broke.
Editing options in camera are amazing! There's so many things you can change!
No CarrierIQ
Here's my H810 repository on Androidfilehost if you're looking for other H810 files.
This is pretty sweet! I always wanted to post in the dev folder, and make a reserve post. Not that I really did anything worthy of it, but I'm leaving the post here anyway.
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
It worked! It was a bumpy road, thank you for all your help! (oh sweet ad blockers, how I love you)
faizalotai said:
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
Click to expand...
Click to collapse
Yes to all your questions.
I repeated the code to flash here to make sure people noticed it was different for H810PR. It's the same in both posts.
Just noticed i no longer have volte with this image. (yes, i have lte)
faizalotai said:
Great job bud, just clearing things up...
the file must be rename to system.img and to be placed in internal memory
after follow instruction from rooting thread, we are using OP code to flash the image...right.
Click to expand...
Click to collapse
Can you help me? What code do I of/if to root my device?
Here I receive a hint, either have tried it cause of fear of do it wrong then risk or brick my device
Thanks in advance
user787 said:
Can you help me? What code do I of/if to root my device?
Here I receive a hint, either have tried it cause of fear of do it wrong then risk or brick my device
Thanks in advance
Click to expand...
Click to collapse
Copy OP's code @up..for me i follow till step 9 from THIS then follow this PAGE from 6 to 9 then paste OP code to flash image root
Please read carefully before anything bad happened
faizalotai said:
Please read carefully before anything bad happened
Click to expand...
Click to collapse
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
user787 said:
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
Click to expand...
Click to collapse
No problem bud
user787 said:
I will read again, then practice, then execute. Will report back either win or fail looking for #
Thank you
Click to expand...
Click to collapse
I edited the OP to make the instructions more clear. Hope it helps!
To be clear, this will work on an H810 US ATT that has the H810PR image on it now?
noamaniac said:
To be clear, this will work on an H810 US ATT that has the H810PR image on it now?
Click to expand...
Click to collapse
Yes.
What is the LTE icon for this build? I have the 4G icon, but not sure this means LTE.
what are the downsides to flashing this on the H810 stateside bloatware4days edition?
bobloadmire said:
what are the downsides to flashing this on the H810 stateside bloatware4days edition?
Click to expand...
Click to collapse
The main reason we're using it is because we soft bricked our phones and it was the only solution at the time. I've uploaded rooted images of H81010b and H81010g so we could go back to AT&T (I don't know why I keep thinking this is possible, it isn't, bootloader is flashed by the KDZ and not compatible with the ATT versions anymore), but I'm going to stick it out on this image for awhile.
I'm keeping an updated list of the pros and cons in the OP.
phineous said:
The main reason we're using it is because we soft bricked our phones and it was the only solution at the time. I've uploaded rooted images of H81010b and H81010g so we could go back to AT&T, but I'm going to stick it out on this image for awhile.
Cons so far:
No VoLte (voice over LTE). The phone drops to 3G in phone calls.
Possible problems with voicemail.
Pros:
The phone comes with very little bloat. There's a huge difference in the number of packages, like 150 less.
Click to expand...
Click to collapse
Would you Say the phone is snappier overall or is it mainly just to save storage?
bobloadmire said:
Would you Say the phone is snappier overall or is it mainly just to save storage?
Click to expand...
Click to collapse
I ran Debloater and blocked around 98 packages when I was on the AT&T H81010e non-root image. The phone was pretty fast, but something had a memory leak and I'd have to reboot it every morning. This image hasn't had that problem yet, but I've only been using it for a couple of days.
You might want to wait a little while for the people who had to use it to discover any more downsides. I think it'll be easy to switch back to an AT&T image, but I'm not 100% sure because I haven't tested it yet. (not possible till there's a TOT.)
In any case, I think it's a good idea to follow the instructions in the original root thread to extract an image of your working phone, name it something you'll remember, and keep it on the internal storage as an emergency recovery image.
Totes mah gotes. Thanks man.
Anyone that's on this Firmware having issues with voicemail? I can't seem to get google voice to work and when people call my regular voicemail it is saying i'm not available. I've tried entering the code into the dialer and i'm getting an error saying connection error or wrong MMI code.
I went into the forwarding settings in the phone and entered my GV # and received unexpected error from network.
Here's the stock V20 firmware for the T-mobile Variant.
Hopefully it helps other people develop a root for our phone.
LGH918AT-01-V10d-310-260-SEP-14-2016-ARB00+0.tot
DOWNLOAD
meraz9000 said:
Here's the stock V20 firmware for the T-mobile Variant.
Hopefully it helps other people develop a root for our phone.
LGH918AT-01-V10d-310-260-SEP-14-2016-ARB00+0.tot
DOWNLOAD
Click to expand...
Click to collapse
I'm a very cautious person. Have you tried flashing it and verifying that your phone still works? Have you unlocked?
meraz9000 said:
Here's the stock V20 firmware for the T-mobile Variant.
Hopefully it helps other people develop a root for our phone.
LGH918AT-01-V10d-310-260-SEP-14-2016-ARB00+0.tot
DOWNLOAD
Click to expand...
Click to collapse
Do you have a link to an extractor for this TOT file?
Thanks
I dont think there's one that will support this newer firmwares but I can upload the extracted files made from other..tools..that not allowed to discuss here.
EMSpilot said:
Do you have a link to an extractor for this TOT file?
Thanks
Click to expand...
Click to collapse
I managed to hack one up. Let me throw it up on my github.
https://github.com/androidrbox/LGBinExtractor
rbox said:
I managed to hack one up. Let me throw it up on my github.
https://github.com/androidrbox/LGBinExtractor
Click to expand...
Click to collapse
Good stuff man! and yes to answer your question it flashed just fine on my personal V20.
meraz9000 said:
Good stuff man! and yes to answer your question it flashed just fine on my personal V20.
Click to expand...
Click to collapse
So I've never used LG phones before... Is it possible to craft a TOT file that just has a single partition in it? All the stuff I seem to find is people flashing full giant TOT files.
rbox said:
So I've never used LG phones before... Is it possible to craft a TOT file that just has a single partition in it? All the stuff I seem to find is people flashing full giant TOT files.
Click to expand...
Click to collapse
it is "possible" but usally LGUP wont flash files like that.
meraz9000 said:
it is "possible" but usally LGUP wont flash files like that.
Click to expand...
Click to collapse
Hrm, well that's lame... After working on the extractor tool and figuring out the format... I can't imagine why it wouldn't work... Unless the tool does some kind of size checking or something. How do people modify these tot files generally? I can imagine just modifying the extracting image and dd'ing it back into the tot at the correct position.
rbox said:
Hrm, well that's lame... After working on the extractor tool and figuring out the format... I can't imagine why it wouldn't work... Unless the tool does some kind of size checking or something. How do people modify these tot files generally? I can imagine just modifying the extracting image and dd'ing it back into the tot at the correct position.
Click to expand...
Click to collapse
I sent you a PM
Is anyone able to examine the T-Mobile LG G5 H830 modified TOT file made by @tungkick to see how he replaced the stock recovery with TWRP? That's the last step to getting root and there seems to be a lot of interest and quite a few bright people here that seem to be capable of doing it. It involves hex editing but is beyond my abilities otherwise I'd do it myself.
arjuna_ said:
Is anyone able to examine the T-Mobile LG G5 H830 modified TOT file made by @tungkick to see how he replaced the stock recovery with TWRP? That's the last step to getting root and there seems to be a lot of interest and quite a few bright people here that seem to be capable of doing it. It involves hex editing but is beyond my abilities otherwise I'd do it myself.
Click to expand...
Click to collapse
Well, first someone would need to compile TWRP...
rbox said:
Well, first someone would need to compile TWRP...
Click to expand...
Click to collapse
You're right but I feel like that's child's play compared to doing the hex editing.
arjuna_ said:
You're right but I feel like that's child's play compared to doing the hex editing.
Click to expand...
Click to collapse
No
Ok maybe I'm wrong lol anyway we all are grateful if this stuff is figured out and will wait patiently.
Great Work !!!!
Box ?
I just contacted someone that can help compile TWRP. Is anyone able to provide a stock dump of system.img, boot.img, recovery.img?
arjuna_ said:
I just contacted someone that can help compile TWRP. Is anyone able to provide a stock dump of system.img, boot.img, recovery.img?
Click to expand...
Click to collapse
Download the TOT, download the tool from my github... profit.
arjuna_ said:
I just contacted someone that can help compile TWRP. Is anyone able to provide a stock dump of system.img, boot.img, recovery.img?
Click to expand...
Click to collapse
You should try to contact direcly Dees_Troy on irc.
He is online now there on official twrp channel and could help to compile a working one.
Need to decompile kernel on github and make public
Thanks, will use this for building TWRP, looks like the sources are up for the kernel as well so I'll get started. I do not know how to build a TOT from the image, so I'm not sure how I'll be able to find someone to test it.