Alright, so I downloaded that KDZ, and unpacked it all and merged the system file. I believe this is yes, a working KDZ file and safe to use after examining boot.img and some other partitions. So ya, safe to flash. We got root on Lolipop by simply injecting SuperSU into the TOT, but that will not work. We need Systemless root by flashing a modified boot.img. How one creates a modified boot.img for it I will look into. Good luck flashing!
This also came from LG's website so it's official.
Here's the link to the download. https://drive.google.com/open?id=0B7FrzLAFlRrvd2N2bU5BSjljRGs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for the kdz. Can't wait for the modified boot.img. Keep up the good work!
yeah.. i too successfully upgraded my ATT h900 from the same kdz.. though downloaded it from another link
http://www.mylgphones.com/att-lg-v1...tock-kdz-firmware-available-for-download.html
everything went smooth & error free although my phone was rooted on 5.1. i used LG UP & used the "Upgrade" option..
nothing was deleted or overwrite either.. everything remained intact.. i say go for it..
sadly.. no change in interface at all..ditto same as 5.1.1... all behind the scene upgrades apart from Wifi calling
Should we not try this if already on MM?
Never mind this question, I found the answer in the TOT thread started by tung
P05TMAN said:
Should we not try this if already on MM?
Never mind this question, I found the answer in the TOT thread started by tung
Click to expand...
Click to collapse
It won't matter. Since it's marshmallow the tot rollback values remain the same
Flash at will
This might be a dumb question but does it have all the at&t bloatware? If not it would still be worth flashing just to rid my phone of at&t.
serdoch said:
This might be a dumb question but does it have all the at&t bloatware? If not it would still be worth flashing just to rid my phone of at&t.
Click to expand...
Click to collapse
Yes it will still have the AT&T bloat.
serdoch said:
This might be a dumb question but does it have all the at&t bloatware? If not it would still be worth flashing just to rid my phone of at&t.
Click to expand...
Click to collapse
ZVNexus said:
Yes it will still have the AT&T bloat.
Click to expand...
Click to collapse
@serdoch I think at this stage, the main test-point is to validate that we can flash and run a kdz file. If it's good (which so far it is) then we can move forward in trying to root by modifying the boot.img (or some other wizardry...)
P05TMAN said:
@serdoch I think at this stage, the main test-point is to validate that we can flash and run a kdz file. If it's good (which so far it is) then we can move forward in trying to root by modifying the boot.img (or some other wizardry...)
Click to expand...
Click to collapse
Ok thank you. Hopefully it goes well.
P05TMAN said:
@serdoch I think at this stage, the main test-point is to validate that we can flash and run a kdz file. If it's good (which so far it is) then we can move forward in trying to root by modifying the boot.img (or some other wizardry...)
Click to expand...
Click to collapse
I flashed it. Success. KDZ now OFFICIALY works. Anyone who wants to, feel free to flash it, we finally have a working firmware image on our hands .
ZVNexus said:
I flashed it. Success. KDZ now OFFICIALY works. Anyone who wants to, feel free to flash it, we finally have a working firmware image on our hands .
Click to expand...
Click to collapse
Works for me as well
What can I do to help?
P05TMAN said:
Works for me as well
What can I do to help?
Click to expand...
Click to collapse
Grab a beer? idk. I don't usually go this far in depth, I used to just hunt for system firmware on the internet and once I did I would inject supersu and flash, but thats not how it works with 6.0 sadly. I do know that it requires a modified boot.img, which I also, do not know how to do lol. Being the crafty person I am, I will research more. Not quite sure you want something though from someone who hasn't got the first clue of what to do, so I assume you would want a more trusted Dev such as... Chainfire? I will try to contact him. Doubt hes intrested.
P05TMAN said:
Works for me as well
What can I do to help?
Click to expand...
Click to collapse
And what version did you come off when you flashed? 6.0.1 as well?
P05TMAN said:
@serdoch I think at this stage, the main test-point is to validate that we can flash and run a kdz file. If it's good (which so far it is) then we can move forward in trying to root by modifying the boot.img (or some other wizardry...)
Click to expand...
Click to collapse
Oh heres something else thats important, as to my knowledge, we have a way to unpack a KDZ, but not reassemble. If you find anything, let me know.
ZVNexus said:
And what version did you come off when you flashed? 6.0.1 as well?
Click to expand...
Click to collapse
6.0
ZVNexus said:
Oh heres something else thats important, as to my knowledge, we have a way to unpack a KDZ, but not reassemble. If you find anything, let me know.
Click to expand...
Click to collapse
Researching
P05TMAN said:
6.0
Researching
Click to expand...
Click to collapse
Hm. It should work for my version though, since I am on H90021w. I think Anti-TOT rollback is just for rolling back, I think you can still flash your current version or upgrade. This firmware is also GREAT news for people who want to upgrade to 6.1 from 5.1.1 (Why would you want to tho root <3) lets say you have a other carrier phone that runs through AT&T, but its prepaid. This is GREAT for those people. The purposes are limitless.
ZVNexus said:
Oh heres something else thats important, as to my knowledge, we have a way to unpack a KDZ, but not reassemble. If you find anything, let me know.
Click to expand...
Click to collapse
The more I'm researching, the more unsure how a systemless root can be achieved without first being able to unlock the bootloader of the device first on marshmallow. How was this done on Lollipop? @tungkick do you have any info that may help?
P05TMAN said:
The more I'm researching, the more unsure how a systemless root can be achieved without first being able to unlock the bootloader of the device first on marshmallow. How was this done on Lollipop? @tungkick do you have any info that may help?
Click to expand...
Click to collapse
That is what I was saying. We need to modify the boot.img to unlock the bootloader, and obtain systemless root.
ZVNexus said:
That is what I was saying. We need to modify the boot.img to unlock the bootloader, and obtain systemless root.
Click to expand...
Click to collapse
<snip>
found this: http://forum.xda-developers.com/showthread.php?t=2600575
Maybe it can be used to compress again
---------- Post added at 05:50 PM ---------- Previous post was at 04:55 PM ----------
P05TMAN said:
<snip>
found this: http://forum.xda-developers.com/showthread.php?t=2600575
Maybe it can be used to compress again
Click to expand...
Click to collapse
Extraction doesn't really work well with that.
P05TMAN said:
<snip>
found this: http://forum.xda-developers.com/showthread.php?t=2600575
Maybe it can be used to compress again
---------- Post added at 05:50 PM ---------- Previous post was at 04:55 PM ----------
Extraction doesn't really work well with that.
Click to expand...
Click to collapse
Thats the tool I used to extract the KDZ, and DZ file, and to merge the system partition into one .img.
Great tool for extraction, 10/10, dont know if its capable of patching it back up.
Related
No, I do not have a full I535VRUCML1 firmware package for you.
Yes, I somewhat lied in the title of this thread. But I did it for a good reason: to get your attention.
Mods - I'm sure you'll understand.
You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well. Even if you manage to flash an ENTIRE old bootchain over VRUCML1, you'll brick because they trip a qfuse that prevents it from working. More info about qfuse by djrbliss here: http://t.co/myb0LIrN6e
Just stick with VRUBMF1, trust me.
These firmware updates have, up until now, consisted of several partitions that we update:
- tz (trustzone)
- rpm (resource/power management)
- sbl[1,2,3] (secure bootloaders)
- NON-HLOS (modem/baseband)
Due to the way Samsung and Verizon have chosen to proceed with future updates (following what they do for the Galaxy S4) we cannot flash all these partitions anymore (see above) and retain our unlocked bootloader. We CAN, however, update the baseband as it's not signed.
Latest firmware: NE1 modem with MF1 firmware: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
This will be the final zip I make. MF1 was the last firmware that allowed us to use the old bootloader, and NE1 is likely to be the last modem we'll ever receive.
How would we measure objectively, coverage/speed differences between what we have the old and new radios?
I guess bandwidth speed test app? Anything else?
Sweet. Maybe I'll get better signal. My voice/1x reception has been worse than my old dx. I'm dropping calls left and right. I also live in the middle of BFE.
how is baseband/radio affected when we flash something else with cwm or with Odin? I mean, I have stock rooted w. b00stedv.002, but if I flash aokp or cm, will it replace this new radio with whatever one is included with them?
Slightly OT, I remember on the dx, if you wanted to sbf without the radio you did it with Linux, otherwise with moto's rsdlite.
Will this wipe data/swap us back to a stockish rom?
invisiblek said:
I've always liked having a thread dedicated to keeping links for the most updated modems for a device. Just easier to find that way.
These are packaged for flashing with Odin. Flash in the PDA section.
I will not promise anything as far as faster speeds or better coverage.
IMPORTANT:
Do not unplug while this is happening, unless you are in dire need of a paperweight.
Odin tends to seem like it hangs for a short bit toward the end of the flash. Be patient, it will finish and automatically reboot.
Latest one on top.
VRLG1 - http://goo.im/devs/invisiblek/i535/VRLG1.modem.tar.md5
This is the first OTA
VRLF2 - http://goo.im/devs/invisiblek/i535/VRLF2.modem.tar.md5
This is the original shipped modem
Click to expand...
Click to collapse
very good idea these are amaazing.. any idea if the new radio plays nicer with installs etc.. as the old one has more or less everyone with no service here and there.. or globally roaming :/
beanstown106 said:
very good idea these are amaazing.. any idea if the new radio plays nicer with installs etc.. as the old one has more or less everyone with no service here and there.. or globally roaming :/
Click to expand...
Click to collapse
no idea, i'm still rocking a stock rom
would be nice though if this fixed some of the aosp problems
MOD: please sticky this thread
invisiblek said:
no idea, i'm still rocking a stock rom
would be nice though if this fixed some of the aosp problems
MOD: please sticky this thread
Click to expand...
Click to collapse
im on cm10 after all the audio commits etc it seems like the most stable rom other than stock, beats aokp or cm9 right now imho, no data drops etc
So...This is just the new baseband right?
So should be able to flash with custom recovery/rom etc?
this is my first samsung device so not looking for a brick.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?
burkett375 said:
I'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?
Click to expand...
Click to collapse
Did you verify the MD5 before flashing?
nosympathy said:
Did you verify the MD5 before flashing?
Click to expand...
Click to collapse
doesn't it get verified in odin?
burkett375 said:
doesn't it get verified in odin?
Click to expand...
Click to collapse
I don't have any idea. I have always had HTC phones which are very different.
I have built the habit to check MD5 always, regardless of what it is, just so as to not have something happen where I can't say I did everything I could to prevent it.
burkett375 said:
I'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?
Click to expand...
Click to collapse
yes, if its stuck on SetupConnection unplug and replug
this goes for more than just flashing modems
invisiblek said:
yes, if its stuck on SetupConnection unplug and replug
this goes for more than just flashing modems
Click to expand...
Click to collapse
hmmm...no matter what I do, I can't get past that part
burkett375 said:
hmmm...no matter what I do, I can't get past that part
Click to expand...
Click to collapse
you have the drivers installed?
burkett375 said:
hmmm...no matter what I do, I can't get past that part
Click to expand...
Click to collapse
You are in download mode correct? I literally just flashed this first try.
invisiblek said:
you have the drivers installed?
Click to expand...
Click to collapse
yup, i'm running CM10 right now and working good.
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
nosympathy said:
You are in download mode correct? I literally just flashed this first try.
Click to expand...
Click to collapse
Nope, didn't know it was supposed to be in download mode...i'm a dummy
Edit: all set now...Thanks!
burkett375 said:
yup, i'm running CM10 right now and working good.
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
Nope, didn't know it was supposed to be in download mode...i'm a dummy
Edit: all set now...Thanks!
Click to expand...
Click to collapse
haha no biggie. It happens.
nosympathy said:
I don't have any idea. I have always had HTC phones which are very different.
I have built the habit to check MD5 always, regardless of what it is, just so as to not have something happen where I can't say I did everything I could to prevent it.
Click to expand...
Click to collapse
tar.md5 files have the md5 appended to the end, and I think Odin checks before flashing. Not 100% sure on that though. Checking it yourself is never a bad idea of course.
This newer modem might of improved data throughput. Not entirely sure though, seems like I'm getting faster speed on Speedtest.net but that could be entirely subjective. Thank you invisiblek as always, for your awesome work!
Hey guys,
Using a guide for the g3 by @topet2k12001 i was able to get permanent recovery working for our d801's running the new 30b Lollipop. I compiled the necessary files into a flashable zip for you all. The zip contains bump'd lollipop boot.img, kk aboot.img, and twrp 2.8.6.1 recovery.
as always... FLASH AT YOUR OWN RISK
Prerequisites:
- Running Stock D80130b
- Rooted
- Autorec installed
Getting Started:
- Copy TWRP-2.8.6.1_D80130b.zip to your phones storage
- Run Autorec and flash TWRP (2.7)
- Reboot to recovery
- Flash TWRP-2.8.6.1_D80130b.zip
- Enjoy!
You should now have a permanent recovery.
DOWNLOAD:
Twrp for d80130b:
https://mega.co.nz/#!qFUDWC4a!nHj3R-gPAEqvZ-yLcQMZxXvTN8eFJg99vWfopnCjR_w
Stock d80130b bootstack + recovery: (flashes stock recovery in case anything goes wrong)
https://mega.co.nz/#!KI9k1YxT!HDJEDSd0X1MEsdr5oiNdutg0aADuqB3A1XrNQUjsqrQ
Credits to @blastagator for the Recovery and @Cloudyfa for Autorec
Great work man...i had a feeling you would bring us a working fix
Was going to try this and got this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nalanotae said:
Was going to try this and got thisView attachment 3241785
Click to expand...
Click to collapse
If i remember correctly, that means you are not currently rooted - or Autorec doesnt have root permissions
Done!..you're awesome man. By the way, my lollipop charges so slowly like in 4-5 hours. Any help you can offer me?
Thanks very much!! Works great
Sent from my LG-D801 using XDA Free mobile app
snowlin said:
If i remember correctly, that means you are not currently rooted - or Autorec doesnt have root permissions
Click to expand...
Click to collapse
I am rooted and autorec had been granted root permisions........... I may try a fresh install of everything and start over tonight after work...... Thanks for your response
Messip3 said:
Done!..you're awesome man. By the way, my lollipop charges so slowly like in 4-5 hours. Any help you can offer me?
Click to expand...
Click to collapse
Just let it cycle a few days. It will improve.
Same happened for me with 30a and 30b. Of anything i reccomend using "amplify" xposed module.
nalanotae said:
I am rooted and autorec had been granted root permisions........... I may try a fresh install of everything and start over tonight after work...... Thanks for your response
Click to expand...
Click to collapse
maybe you need busybox?
I had that problem once but it was in the middle of me re-flashing the kdz a bunch of times and it didn't happen again. Start fresh if you can
KDZ > Root > Recovery
Great work man!
I knew when I saw you working on it in the other thread that you'd find something!
May I ask what you did to fix this?
snowlin said:
Just let it cycle a few days. It will improve.
Same happened for me with 30a and 30b. Of anything i reccomend using "amplify" xposed module.
Click to expand...
Click to collapse
Alright man...thank you.
mjoecarroll said:
Great work man!
I knew when I saw you working on it in the other thread that you'd find something!
May I ask what you did to fix this?
Click to expand...
Click to collapse
I pulled the aboot.img and laf.img from 20e , bumped the stock lollipop boot.img using a guide i found in the g3 forums and packaged it with twrp 2.8.6.1.
I'm not super experienced or anything but this kind of stuff interests me so i learn as i go
That's pretty awesome. I was gonna try something similar, but I was afraid I was gonna brick my phone... I didn't think about bumping the boot.img at all, that was smart haha.
mjoecarroll said:
That's pretty awesome. I was gonna try something similar, but I was afraid I was gonna brick my phone... I didn't think about bumping the boot.img at all, that was smart haha.
Click to expand...
Click to collapse
It took me a ton of trial and error haha, luckily i had the stock recovery already zip'd so if anything went wrong i could usually just flash that in order to be able to boot again and start over.
snowlin said:
It took me a ton of trial and error haha, luckily i had the stock recovery already zip'd so if anything went wrong i could usually just flash that in order to be able to boot again and start over.
Click to expand...
Click to collapse
Worked just great, thanks a million.
snowlin said:
maybe you need busybox?
I had that problem once but it was in the middle of me re-flashing the kdz a bunch of times and it didn't happen again. Start fresh if you can
KDZ > Root > Recovery
Click to expand...
Click to collapse
That was my plan....... When i first flashed this rom i had no problem with installing autorec but then i got the security error.. So i just flashed kdz then rooted and set the phone up...... Can't wait to get all this going.... Really untested to see how sins if these custom roms run with new radio
Screen goes crazy when recovery tries to dim screen...looks like back when lgd jdi screen issues used to be a problem
jamesd1085 said:
Screen goes crazy when recovery tries to dim screen...looks like back when lgd jdi screen issues used to be a problem
Click to expand...
Click to collapse
hmmm i'm not experiencing this at all, i included the panelfix script from the twrp package too. perhaps its not running correctly.
anyone else having this problem?
snowlin said:
hmmm i'm not experiencing this at all, i included the panelfix script from the twrp package too. perhaps its not running correctly.
anyone else having this problem?
Click to expand...
Click to collapse
So far it happened twice while i was testing...while attemting to back up it did it but was fine as long as i kept screen active...also on restore same issue...if no one else has issue then idk
jamesd1085 said:
So far it happened twice while i was testing...while attemting to back up it did it but was fine as long as i kept screen active...also on restore same issue...if no one else has issue then idk
Click to expand...
Click to collapse
maybe try flashing blastagators twrp package for the 801 : http://blastagator.ddns.net/twrp/2-8-6-1.php
even though this is what i used in mine anyways, it's worth a shot. You will still be able to boot after flashing this since it is only recovery.
I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.
chetqwerty said:
I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.
Click to expand...
Click to collapse
Upload it to android file host if you have dev status but if not you can upload it to google drive or any other hosting site.
EDIT: If you can get it uploaded somewhere, I'm sure @muniz_ri wouldn't mind looking at it and since it sounds like it prevents downgrading, we may be able to make a ROM out of it using the OD5 bootloader like what was done with the VZW S4 Lollipop update.
No not a dev, uploaded it to a free service http://www.fileconvoy.com/dfl.php?id=g71d4dc928ae33b36999687091905b660934562bab don't know why eset said it was unsafe, it downloaded fine when i allowed it. so just allow its fine.
Tried another service, FileDropper for those who have a problem
http://www.filedropper.com/update_3
ESET Antivirus didn't have a problem with this one
Shotty the first release @muniz_ri LOL
This is a OC4 to OE1 update.
timeToy said:
This is a OC4 to OE1 update.
Click to expand...
Click to collapse
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app
aholeinthewor1d said:
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I personally have a Dev. Ed. S5, so I don't mind, as long as I don't flash the bootloader (aboot.mbn), so I am still interested in this.
It's been confirmed by muniz_ri that the qfuse counter was updated. If you update to OE1, there's no going back.
Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
Awesome. Downloading now.
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks
I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
awesome, Thanks !
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
Sorry it's taken so long to reply. I was at a party when I replied and downloaded the ROMs and didn't want to test them without having my computer in case of an Odin emergency. lol.
I'll be testing them shortly.
timeToy said:
I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
awesome, Thanks !
Click to expand...
Click to collapse
Thanks, which ROM did you test or both?
muniz_ri said:
Thanks, which ROM did you test or both?
Click to expand...
Click to collapse
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW. I also modified your script to avoid wiping. All good
timeToy said:
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW
Click to expand...
Click to collapse
Thanks, created new thread for the ROM's here: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
---------- Post added at 11:56 PM ---------- Previous post was at 11:24 PM ----------
chetqwerty said:
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks
Click to expand...
Click to collapse
After reviewing the ota zip I have confirmed that it checks for stock /bin/ddexe which is modified when a device is rooted, therefore the official OC4-to-OE1 ota will fail on all rooted devices. I have not seen an OD5-to-OE1 ota update.zip in order to review.
chetqwerty said:
Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.
Click to expand...
Click to collapse
Confirming, if I'm not rooted, there's no way to disable the annoying update nag? I'm on BOC4 and I can't use the phone without the stupid msg popping up!
I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?
equazcion said:
I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?
Click to expand...
Click to collapse
No
Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.
Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse
Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse
First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.
Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.
The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
This root works on all Marshmallow versions on Android on the T-Mobile S7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
method
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?
dantehalo said:
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?
Click to expand...
Click to collapse
Yes I am planning to make a video tutorial.
Also I used the method provided here (this is Max Lee's website)
And for now here is great video tutorial (also created by Max Lee) The Video
So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.
revulv said:
So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.
Click to expand...
Click to collapse
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.
Month later
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
KillerClaw321 said:
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.
Click to expand...
Click to collapse
djdubyah said:
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
Click to expand...
Click to collapse
It is the only root method so far. It is not required but you can unencrypt before rooting. Rooting while already encrypted won't cause any harm since /data is encrypted not /system . But I still recommend unencrypting so you don't run into any issues.
Does this work for the latest November 1st update APK1?
Hello, I too would like to know if this is still the current root method and if there have been any changes?
GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.
i cant root my sm9307
KillerClaw321 said:
The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
Click to expand...
Click to collapse
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me
seattlestexan said:
GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.
Click to expand...
Click to collapse
Did the attempt trip your Knox counter?
GeorgeNYer said:
Did the attempt trip your Knox counter?
Click to expand...
Click to collapse
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.
seattlestexan said:
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.
Click to expand...
Click to collapse
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
---------- Post added at 09:55 PM ---------- Previous post was at 09:52 PM ----------
GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
I would try it myself but I'd hate to start over from scratch, I just wanna know if you tried all that is in the video, if not then I would try
Sent from my SM-G930T using Tapatalk
GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
What I listed is what I was able to do. I'm not certain it ever had root access. When it showed "custom" at boot, I couldn't grant anything root access. When it acted more laggy, like was described, the lag was so bad, it wasn't usable. Mind you, these instructions were written prior to the APK1 firmware that was on my G930T from new.
jveewee said:
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me
Click to expand...
Click to collapse
It's smg930t, just search smg930t root max lee
I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.
troby86 said:
I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.
Click to expand...
Click to collapse
And Knox counter wasn't tripped??
GeorgeNYer said:
And Knox counter wasn't tripped??
Click to expand...
Click to collapse
Nope.