Related
So I have TWRP installed on my rooted Galaxy S3 (I535), and the 4.3 update just came out and was available to me.
I downloaded it, and tried to install it (I know that it will remove root), and when it finished downloading, it opened the TWRP boot menu.
Does anyone else who uses TWRP know how to install the new update? I couldn't find it and it wouldn't automatically install....
Carousser said:
So I have TWRP installed on my rooted Galaxy S3 (I535), and the 4.3 update just came out and was available to me.
I downloaded it, and tried to install it (I know that it will remove root), and when it finished downloading, it opened the TWRP boot menu.
Does anyone else who uses TWRP know how to install the new update? I couldn't find it and it wouldn't automatically install....
Click to expand...
Click to collapse
If your OK with the locked bootloder (no more twrp) that comes with 4.3 flash the Odin file. If you want to ota there are links some place on this forum to flash stock recovery
ThePagel said:
If your OK with the locked bootloder (no more twrp) that comes with 4.3 flash the Odin file. If you want to ota there are links some place on this forum to flash stock recovery
Click to expand...
Click to collapse
Well I don't plan on using a custom ROM, I was using just the stock ROM + root. How do I do this?
Carousser said:
Well I don't plan on using a custom ROM, I was using just the stock ROM + root. How do I do this?
Click to expand...
Click to collapse
What way do you want to go Odin firmware will wipe internal sd card but it will be a nice clean install. Or ota after the stock recovery has been flashed through Odin but you might have weird bugs with ota... Might
ThePagel said:
What way do you want to go Odin firmware will wipe internal sd card but it will be a nice clean install. Or ota after the stock recovery has been flashed through Odin but you might have weird bugs with ota... Might
Click to expand...
Click to collapse
I'd rather not wipe the internal SD card.. Isn't there just a way to install the update without all the hassle? I don't remember doing all this for rooting it... I'm fine with losing the root upon installing the new update as I can just root it again with safe root
Carousser said:
I'd rather not wipe the internal SD card.. Isn't there just a way to install the update without all the hassle? I don't remember doing all this for rooting it... I'm fine with losing the root upon installing the new update as I can just root it again with safe root
Click to expand...
Click to collapse
Find the. Stock recovery download it and flash through Odin. there are ways to do it through terminal but odin is the fastest to explain. After that you should beable to ota and keep your setup as is. It is odd that you cant ota I had twrp when i took the ota.
ThePagel said:
Find the. Stock recovery download it and flash through Odin. there are ways to do it through terminal but odin is the fastest to explain. After that you should beable to ota and keep your setup as is. It is odd that you cant ota I had twrp when i took the ota.
Click to expand...
Click to collapse
Well it just directs me to TWRP, and I have no idea where to go from there. I don't care about ever having TWRP again and I don't care about having a locked bootstrap, as I only need stock with root.
Never mind I was on stock recovery I forgot I was recovering from a soft brick when I decided to give it a shot.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Carousser said:
Well it just directs me to TWRP, and I have no idea where to go from there. I don't care about ever having TWRP again and I don't care about having a locked bootstrap, as I only need stock with root.
Click to expand...
Click to collapse
Oh your stuck on twrp can't boot up to usable state?
ThePagel said:
Never mind I was on stock recovery I forgot I was recovering from a soft brick when I decided to give it a shot.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Oh your stuck on twrp can't boot up to usable state?
Click to expand...
Click to collapse
It goes to a screen with options such as Install, Wipe, Backup, Restore, etc....
I don't know where the ota is downloaded and thus cannot install it
Carousser said:
It goes to a screen with options such as Install, Wipe, Backup, Restore, etc....
I don't know where the ota is downloaded and thus cannot install it
Click to expand...
Click to collapse
You kind of only have 2 options now. Attempt a "dirty" flash of a ROM so you can save your internal SD files then odin or do the full Odin wipe and forget about keeping the files. Either way unless anyone else has a idea you lose your current setup.
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
I forgot the obvious. If you made a backup in twrp you can just recover with that.
ThePagel said:
You kind of only have 2 options now. Attempt a "dirty" flash of a ROM so you can save your internal SD files then odin or do the full Odin wipe and forget about keeping the files. Either way unless anyone else has a idea you lose your current setup.
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
I forgot the obvious. If you made a backup in twrp you can just recover with that.
Click to expand...
Click to collapse
So let me get this straight.
There's no way for me to install the update unless I flash to another ROM? I don't see why I can;t just update and lose odin and TWRP or whatever
Edit-----
I found the zip file while browsing TWRP. Can I just install it?
Carousser said:
So let me get this straight.
There's no way for me to install the update unless I flash to another ROM? I don't see why I can;t just update and lose odin and TWRP or whatever
Click to expand...
Click to collapse
OK I'll explain what I think went bad.when you downloaded the update it was expecting factory stock recovery to finish the install. Since you had twrp it failed. FYI Odin is a program on the PC to communicate with the phone in download mode (Odin mode). try to do a factory reset before you go crazy with my other suggestions. I have a feeling one of the 3 options I gave you are your only options.
ThePagel said:
OK I'll explain what I think went bad.when you downloaded the update it was expecting factory stock recovery to finish the install. Since you had twrp it failed. FYI Odin is a program on the PC to communicate with the phone in download mode (Odin mode). try to do a factory reset before you go crazy with my other suggestions. I have a feeling one of thoughs 3 options are your only options.
Click to expand...
Click to collapse
I found the zip file while browsing TWRP. Can I just install it? It said it was a flash and that it may be incompatible
Carousser said:
I found the zip file while browsing TWRP. Can I just install it? It said it was a flash and that it may be incompatible
Click to expand...
Click to collapse
Sure you can try tell me if it works
ThePagel said:
Sure you can try tell me if it works
Click to expand...
Click to collapse
Is there a chance of me bricking my phone?
Carousser said:
Is there a chance of me bricking my phone?
Click to expand...
Click to collapse
Yeah but you already soft bricked it. Any brick you do you should be able to fix. just so you know you backed yourself into a corner. No matter what you do you have a chance of bricking. Its all part of being a power user. If your uncomfortable with that after you are on 4.3 you might not want to root.
ThePagel said:
Yeah but you already soft bricked it. Any brick you do you should be able to fix. just so you know you backed yourself into a corner. No matter what you do you have a chance of bricking. Its all part of being a power user. If your uncomfortable with that after you are on 4.3 you might not want to root.
Click to expand...
Click to collapse
Yeah I know there's always the chance of bricking, just wanted to know if that specific thing would do it. I've been into rooting since my Droid 1, Droid 2, and Droid X. But I'm always cautious.
If I do a factory reset and back up all my data, will it get rid of odin and TWRP and everything? Then just install the 4.3 update and root using safe root? Would that work?
Carousser said:
Yeah I know there's always the chance of bricking, just wanted to know if that specific thing would do it. I've been into rooting since my Droid 1, Droid 2, and Droid X. But I'm always cautious.
If I do a factory reset and back up all my data, will it get rid of odin and TWRP and everything? Then just install the 4.3 update and root using safe root? Would that work?
Click to expand...
Click to collapse
You would need to flash stock recovery completely replacing twrp. so if factory reset works and you can boot you should beable to flash stock recovery then redo the ota.
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
If you have backups of stuff on your internal sd it would be much faster to just Odin to 4.3 right now.
ThePagel said:
You would need to flash stock recovery completely replacing twrp. so if factory reset works and you can boot you should beable to flash stock recovery then redo the ota.
Click to expand...
Click to collapse
Is there a chance that doing a factory reset wouldn't flash it back? What else would I have to do? Sorry I haven't dealt with flashing since i had my droid x
Carousser said:
Is there a chance that doing a factory reset wouldn't flash it back? What else would I have to do? Sorry I haven't dealt with flashing since i had my droid x
Click to expand...
Click to collapse
Factory reset deals with the rom. So no it will stay twrp.
---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------
Using Odin is a lot like SBF'ing on the droid x (that was my last phone also). So if you can remember installing cyanogen mod 6 or 7 you probably always did a factory reset before first boot. Custom recovery stays intact the only way to get rid of it was to flash stock recovery with terminal emulator or sbf back to pure stock. Luckily Odin let's us flash the recover by its self so we have more options with Samsung.
The original update OTA can be obtained here: WWE_4.07.1700.4-3.62.1700.1_KTU84L.H4_release_377648
This cannot be flashed unless your device meets all requirements. Wait for a ROM otherwise.
Can someone with the latest version of the stock 4.4.2 GPE help me out! Need one file to update to 4.4.3!
http://forum.xda-developers.com/showthread.php?t=2772266
Thanks!
Orginator said:
Can someone with the latest version of the stock 4.4.2 GPE help me out! Need one file to update to 4.4.3!
http://forum.xda-developers.com/showthread.php?t=2772266
Thanks!
Click to expand...
Click to collapse
Googling for this MD5 first gives me your postings (scattered across XDA ) as well as this link: http://rghost.net/53665485
EDIT: file has been deleted.
sanderg said:
Googling for this MD5 first gives me your postings (scattered across XDA ) as well as this link: http://rghost.net/53665485
EDIT: file has been deleted.
Click to expand...
Click to collapse
Trust me, the first thing I do is google.. been there, done that! Yeah sadly deleted and I'm still stuck at 4.4.2, so many must have made a CWM backup before updating to 4.4.3, yet so hard to get that file :/
Orginator said:
Trust me, the first thing I do is google.. been there, done that! Yeah sadly deleted and I'm still stuck at 4.4.2, so many must have made a CWM backup before updating to 4.4.3, yet so hard to get that file :/
Click to expand...
Click to collapse
What if you manually edit updater-script to not patch Youtube?
I could do that, but then I'll have the same issue on next OTA! I'd rather have a 100% clean update, if you know what I mean!
Could you make a ROM GPE with Sense camera ?
Orginator said:
I could do that, but then I'll have the same issue on next OTA! I'd rather have a 100% clean update, if you know what I mean!
Click to expand...
Click to collapse
Mine fails as well - on basicDreams.apk. It doesn't look like it can be applied to every device, e.g. when integrating apps into the ROM using Titanium Backup it will most likely fail. Will be taken care of by the ROM devs though.
sanderg said:
Mine fails as well - on basicDreams.apk. It doesn't look like it can be applied to every device, e.g. when integrating apps into the ROM using Titanium Backup it will most likely fail. Will be taken care of by the ROM devs though.
Click to expand...
Click to collapse
I don't use Titanium Backup or anything alike.
Can we flash this OTA.zip from stock recovery after we returned back to Google Edition ?
HAAANG ON!! hang on......
this....is a 4.xx.xxxx.x update
previous was 3.62.xxxx.x
....I may assume that is like a....major release or something...?
I expect a good improvement, even in performance (that on sense roms is always 2 times better, dunno why)
Can we flash this?
Sent from my HTC One using Tapatalk
gaja22 said:
Could you make a ROM GPE with Sense camera ?
Click to expand...
Click to collapse
No
---------- Post added at 06:13 AM ---------- Previous post was at 06:12 AM ----------
throcker said:
HAAANG ON!! hang on......
this....is a 4.xx.xxxx.x update
previous was 3.62.xxxx.x
....I may assume that is like a....major release or something...?
I expect a good improvement, even in performance (that on sense roms is always 2 times better, dunno why)
Click to expand...
Click to collapse
Stick to your sense ROM then because performance hasn't changed much between 4.4.2 and 4.4.3
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
mrgwap said:
Can we flash this?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Don't think so, it's an OTA file that needs to be installed by the stock recovery, not a custom recovery.
Nic2112 said:
No
---------- Post added at 06:13 AM ---------- Previous post was at 06:12 AM ----------
Stick to your sense ROM then because performance hasn't changed much between 4.4.2 and 4.4.3
---------- Post added at 06:13 AM ---------- Previous post was at 06:13 AM ----------
Don't think so, it's an OTA file that needs to be installed by the stock recovery, not a custom recovery.
Click to expand...
Click to collapse
About to RUU back to 4.4.2 with stock recovery.
What do I do afterwards. I have the file in the OP downloaded. Do I just place it in root storage and look for a update than root afterwards.
charlieb620 said:
About to RUU back to 4.4.2 with stock recovery.
What do I do afterwards. I have the file in the OP downloaded. Do I just place it in root storage and look for a update than root afterwards.
Click to expand...
Click to collapse
All I had to do was RUU to 4.4.0 because that's the one I had handy, let the phone OTA to 4.4.2, and when it booted all I had to do was hit the "check for update" button 2-3 times and then it prompted me to download the OTA and voila, 4.4.3
Nic2112 said:
All I had to do was RUU to 4.4.0 because that's the one I had handy, let the phone OTA to 4.4.2, and when it booted all I had to do was hit the "check for update" button 2-3 times and then it prompted me to download the OTA and voila, 4.4.3
Click to expand...
Click to collapse
Alright I will do the RUU and just check for Update.
charlieb620 said:
Alright I will do the RUU and just check for Update.
Click to expand...
Click to collapse
You would have to put the OTA at the right location and name it exactly what the recovery expects and I don't know how to do that.
Thing is with stock recovery, there are no options, it either updates or resets to factory default.
can someone make a flashable zip of the rom? Wouldn't really want to go thru all the trouble of converting back to stock recovery and rom to update since im on a custom rom now? A flashable zip would mean a lot!
ace-user said:
can someone make a flashable zip of the rom? Wouldn't really want to go thru all the trouble of converting back to stock recovery and rom to update since im on a custom rom now? A flashable zip would mean a lot!
Click to expand...
Click to collapse
Just wait a day or two.
I haven't really noticed a performance increase or decrease tbh after flashing the new firmware. It says "5.11.401.10" because I edited the android-info.txt file. But the date is 5/16/2014, to confirm that it is the newer v1.54 hboot. How would I go about making a deodex system dump into a flashable rom.zip? I have the system dump if someone can help me with the procedure.
SU4TL-44 Stock Image for XT1254: https://mega.nz/#!v4QWiITb!_0jWWzE4KWCEgT__C36rYe0vaTzGKcEFsZm0vvBtLBg
Flash with TWRP.
This package will flash every image in the SU4TL-44 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, revert to stock by following section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Thanks to @firstEncounter for letting me incorporate his flashable zip into this package.
Will have to download this later. Looked to go back to stock and wait for mm to come out.
Sent from my XT1254 using Tapatalk
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
No it won't relock boot loader just installed it you will not be rooted and twrp will ask you if you want to root before reboot if you click no and want to at a later point just go back into boot loader by doing vol down power combo from power off and select open boot loader and when you click to reboot it will ask you again if you want to root then you can just slide to install
schwinn8 said:
Just to be clear, this doesn't flash re-lock the bootloader, right? So it's just the ROM... correct?
Click to expand...
Click to collapse
Correct
Can I install viper and su along with this?
MazinDLX said:
Can I install viper and su along with this?
Click to expand...
Click to collapse
Sure. Just flash the rom first and the mods second.
TheSt33v said:
Sure. Just flash the rom first and the mods second.
Click to expand...
Click to collapse
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
MazinDLX said:
Ok last night I tried this in this order.
TWRP Backup & ADB Pulled Back-up folder
I then went into TWRP and wiped everything
ADB Pushed the image onto the phone
Installed, wiped dalvik & rebooted into a bootloop of the Motorola Symbol
Click to expand...
Click to collapse
I've never tried to install an image via ADB before. Did you mount the image elsewhere and extract the system folder, and then ADB-pushed that? If not, your bootloop is probably because there's just a big, unextracted system.img on your system partition, and not the actual files within it. Why not just flash it with TWRP? When I tested it, I flashed it via TWRP and it worked.
If you really don't want to flash it via TWRP for some reason, you can extract the system.img from the zip and flash it using fastboot (fastboot flash system system.img).
EDIT: Oh wait, I think I understand now. You just used ADB to put the zip on your phone, and then you installed it with TWRP. Got it. Well my next question is why use ADB at all? Why not just plug in your phone while it's booted into TWRP and use the native MTP to transfer files?
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
This package only flashes /system. CM flashes its own boot.img, which is why this isn't working for you. I'll try to find some time tonight to add in the other images in the stock firmware to this package. Sorry about that.
firstEncounter said:
The boot.img should probably be included as well for people flashing this from a custom ROM, otherwise they will experience a boot loop.
Click to expand...
Click to collapse
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
TheSt33v said:
Great minds think alike. Do you know if boot.img will cover it, or are there other partitions that are flashed by CM that need to be included as well?
Click to expand...
Click to collapse
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
MazinDLX said:
Its chromeos ****, and I'm just a fan of cmd line.
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
I'm going to try again later, after wiping everything X5 and reinstalling CM12.1.
Its flawless.
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
CM12.1 is flawless that is.
Click to expand...
Click to collapse
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
firstEncounter said:
Nope, just boot and system.
Feel free to include the bootloader/radio package from my thread into your zip if you'd like to make this equivalent to flashing a full stock firmware.
Click to expand...
Click to collapse
I'm not entirely sure how to write a script to flash those in TWRP. For boot and system, it's easy because the devices that they are flashed to match the names used by fastboot. Bootloader and radio seem to be a little different though. When I list the contents of /dev/block/bootdevice/by-name, there is no "motoboot" or "radio," which is what fastboot uses when you flash these. I do see "aboot" and "modem," and I'm pretty sure those are the targets I'm looking for, but I don't want to go flashing things unless I'm 100% sure. Since there's not a huge demand for figuring that out, and boot + system is all people will need in 99% of cases, I'll leave them out. Thanks though!
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
MazinDLX said:
Downloading, my XDA hasn't been functioning right lately and I don't get get notified of the 3778328 threads I'm subscribed too lol
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Thanks for the quick responses, you got a tip jar link?
Click to expand...
Click to collapse
No, but I appreciate the thought. Donate to this guy instead. He does way more than me and also needs it way more than me: http://forum.xda-developers.com/droid-turbo/development/computerfreekunlocked1-0-t3255945
TheSt33v said:
I updated the link. It now flashes boot.img in addition to system.img. It should work for you now.
Click to expand...
Click to collapse
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
bigv5150 said:
Thus really helped for whatever reason after altering the fxz xml so I wouldn't lose data rsd lite said the xml files didn't match. I have done this before with no issues. I couldn't take the recent Ota because somehow the system was modified. I am guessing it was something from sunshine. I never rooted the phone just unlocked so I don't know how anything was modified. This made it so much easier flashed it flashed stock recovery and took ota thanks.
Click to expand...
Click to collapse
Awesome! That's why we do this
Hi everyone,
Here i bring a quick way to FULL Restore/Update Stock to v20b (Marshmallow) as promise , no matter from which version you are coming from. (E.g...v10e,v10d,v10i,v10j,v10l)
- Base on Metro PCS user (MS631) you can use this Flashable Update files to update to Marshmallow, but don't quote me on that. -
- I have a report about Metro user who is stuck in LG Logo after flashing this so this mean any METRO PCS USERS DON'T Flash this till further notice. -
This will restore or update your phone to full stock v20b (Marshmallow) deleting all trace of root and TWRP Custom Recovery (you can reflash if needed), your internal storage will be untouch.
but if you Unlock the Bootloader via Fastboot to get root again your Internal Storage is going to get WIPE / FACTORY RESET.
READ AND UNDERSTAND BEFORE PROCEEDING , YOU HAVE BEEN WARNED
DON'T BLAME YOUR DEVICE OR OP IF SOMETHING GOES WRONG AND YOU CREATE A ATOMIC EXPLOSION INSTEAD OF UPDATE A SIMPLE DEVICE :cyclops:
- YOU KNOW THE DRILL - I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE
- FINAL NOTE ....... THIS IS UNTESTED, REASON " I DON'T OWN A STYLO ANYMORE -
--------------------------------------------------------------------------------------------------------
STEPS :
---------
1- Download BootStack zip (- Click Here for H63120b_Marshmallow_Bootstack.zip -)
(Thank you for the fix stack @TURBO2012 )
2- Download Return2Stock zip (Click Here for H63120b_Marshmallow_Return2Stock.zip)
3- Reboot to TWRP (Custom Recovery)
4. Flash LG G STYLO BOOTSTACK Zip file
5. Flash LG G STYLO Return 2 Stock Zip file
6. Wipe CACHE and DALVIK
7. Reboot (at this point you no longer have Root and TWRP and if were in LP, well you are in Marhmallow now -EVERYTHING WILL BE RESET BACK TO STOCK-)
-------------------------------------------------------------------------------
Thanks to @asialove2013 for posting/finding the H63120b KDZ which is the source for my Flashable Zip files
-------------------------------------------------------------------------------
* Unlocking Bootloader and Root Guide By @T-Macgnolia
if that is little complicated to understand lemme know and i'll post my LG G4 Guide which is the same Steps for this Device, i just need to modified it a little , you know different files and such of course
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Reserve for something else
Reserve if need after my last reserve
I have a metro pcs stylo on the stock 10j. Metro rom
Based on what i read i need to root and install twrp on my 10j 5.1.1 rom and then download the files you specified and flash as you instructed us to do?
If yes what root and twrp method do you recommend?
And THANK YOU!
xyourxhighnessx said:
I have a metro pcs stylo on the stock 10j. Metro rom
Based on what i read i need to root and install twrp on my 10j 5.1.1 rom and then download the files you specified and flash as you instructed us to do?
If yes what root and twrp method do you recommend?
And THANK YOU!
Click to expand...
Click to collapse
i recommend you going for the KDZ process, instead of Rooting and TWRP....
you can find the KDZ here and download the LG UP Tool to flashed and just follow the Unlock Bootloader / Root Guide from the link in the OP.
EDIT : I'll hold my self on this, someone using metro try my flashable zip and got stuck in LG Logo, just hold on there till we figure out what is going on.
EDIT 2 : anyone who have downloaded the Bootstack please Redownload the new file it say FIX at the end and DON'T use the old one cuz won't work ...sorry about that.
I am rooting as i write this then will install twrp and try with the Fix u posted , will report back shortly..
thanks!
Louie
---------- Post added at 10:07 PM ---------- Previous post was at 09:59 PM ----------
gives me an error when i try and flas the *,fix file.
it says Error executing updater binary in zip '/external_sd/ H63120b_Marshmallow_BootstackFIX.zip
error flashing zip
Louie
lmarisy said:
I am rooting as i write this then will install twrp and try with the Fix u posted , will report back shortly..
thanks!
Louie
---------- Post added at 10:07 PM ---------- Previous post was at 09:59 PM ----------
gives me an error when i try and flas the *,fix file.
it says Error executing updater binary in zip '/external_sd/ H63120b_Marshmallow_BootstackFIX.zip
error flashing zip
Louie
Click to expand...
Click to collapse
So your saying the latest bootstack fixed zip is not working as well ? I cant afford right now to be a guinea ? thats why im asking
xxbabiboi228xx said:
So your saying the latest bootstack fixed zip is not working as well ? I cant afford right now to be a guinea ? thats why im asking
Click to expand...
Click to collapse
No it's giving me an error whenever i try and flash it, i downloaded it 3 times incase i had a bad download but that was not the problem.
Louie
lmarisy said:
No it's giving me an error whenever i try and flash it, i downloaded it 3 times incase i had a bad download but that was not the problem.
Louie
Click to expand...
Click to collapse
What your saying its saying is there is something wrong with the binary file in the meta-inf folder of the flashable zip should be a easy fix for draken
xxbabiboi228xx said:
What your saying its saying is there is something wrong with the binary file in the meta-inf folder of the flashable zip should be a easy fix for draken
Click to expand...
Click to collapse
yes something is wrong with the actual *.Zip file...
Louie
Womp womp womp. Glad i kept my pants on. I was so ready to jump right in and flash it but i dont have a backup phone in the event i brick so I'll be waiting to see what comes of this.
I just got a note 3 and gave my son my stylo. It is the 10j version (new screen, more mp camera, ect.) I rooted with kingroot way back when I first got the stylo. Glad to see someone doing this. I want to update his phone to MM. But l learned from past mistakes not to just trust the kingroot "unroot" tool. So I knew I couldn't OTA anymore. I will be watching this thread to keep up with how this progresses.
Thanks for making this even though you don't have the device anymore.
Also glad I checked over here. Seems development has died on this device on Androidforums.com where I had to get my info about my Zmax.
Sent from my SM-N900T using Tapatalk
---------- Post added at 07:35 AM ---------- Previous post was at 07:12 AM ----------
DrakenFX said:
Hi everyone,
Here i bring a quick way to FULL Restore/Update Stock to v20b (Marshmallow) as promise , no matter from which version you are coming from. (E.g...v10e,v10d,v10i,v10j,v10l)
- Base on Metro PCS user (MS631) you can use this Flashable Update files to update to Marshmallow, but don't quote me on that. -
- I have a report about Metro user who is stuck in LG Logo after flashing this so this mean any METRO PCS USERS DON'T Flash this till further notice. -
This will restore or update your phone to full stock v20b (Marshmallow) deleting all trace of root and TWRP Custom Recovery (you can reflash if needed), your internal storage will be untouch.
but if you Unlock the Bootloader via Fastboot to get root again your Internal Storage is going to get WIPE / FACTORY RESET.
READ AND UNDERSTAND BEFORE PROCEEDING , YOU HAVE BEEN WARNED
DON'T BLAME YOUR DEVICE OR OP IF SOMETHING GOES WRONG AND YOU CREATE A ATOMIC EXPLOSION INSTEAD OF UPDATE A SIMPLE DEVICE :cyclops:
- YOU KNOW THE DRILL - I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE
- FINAL NOTE ....... THIS IS UNTESTED, REASON " I DON'T OWN A STYLO ANYMORE -
--------------------------------------------------------------------------------------------------------
STEPS :
---------
1- Download BootStack zip (- Click Here for H63120b_Marshmallow_BootstackFIX.zip -)
2- Download Return2Stock zip (Click Here for H63120b_Marshmallow_Return2Stock.zip)
3- Reboot to TWRP (Custom Recovery)
4. Flash LG G STYLO BOOTSTACK Zip file
5. Flash LG G STYLO Return 2 Stock Zip file
6. Wipe CACHE and DALVIK
7. Reboot (at this point you no longer have Root and TWRP and if were in LP, well you are in Marhmallow now -EVERYTHING WILL BE RESET BACK TO STOCK-)
-------------------------------------------------------------------------------
Thanks to @asialove2013 for posting/finding the H63120b KDZ which is the source for my Flashable Zip files
-------------------------------------------------------------------------------
* Unlocking Bootloader and Root Guide By @T-Macgnolia
if that is little complicated to understand lemme know and i'll post my LG G4 Guide which is the same Steps for this Device, i just need to modified it a little , you know different files and such of course[emoji14]
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Click to expand...
Click to collapse
Forgot to ask, is there anyway you could you please post md5 checks in your OP? Better to be safe than sorry when it comes to flashing files.
Again, thank you so much for this, especially since you no longer have the device.
Sent from my SM-N900T using Tapatalk
lmarisy said:
yes something is wrong with the actual *.Zip file...
Louie
Click to expand...
Click to collapse
xxbabiboi228xx said:
What your saying its saying is there is something wrong with the binary file in the meta-inf folder of the flashable zip should be a easy fix for draken
Click to expand...
Click to collapse
xxbabiboi228xx said:
So your saying the latest bootstack fixed zip is not working as well ? I cant afford right now to be a guinea thats why im asking
Click to expand...
Click to collapse
ok i updated the Binary on the zip file should work now, This is why i don't like posting without having Device for testing :crying:
auburn2eugene said:
I just got a note 3 and gave my son my stylo. It is the 10j version (new screen, more mp camera, ect.) I rooted with kingroot way back when I first got the stylo. Glad to see someone doing this. I want to update his phone to MM. But l learned from past mistakes not to just trust the kingroot "unroot" tool. So I knew I couldn't OTA anymore. I will be watching this thread to keep up with how this progresses.
Thanks for making this even though you don't have the device anymore.
Also glad I checked over here. Seems development has died on this device on Androidforums.com where I had to get my info about my Zmax.
Sent from my SM-N900T using Tapatalk
---------- Post added at 07:35 AM ---------- Previous post was at 07:12 AM ----------
Forgot to ask, is there anyway you could you please post md5 checks in your OP? Better to be safe than sorry when it comes to flashing files.
Again, thank you so much for this, especially since you no longer have the device.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
md5 is located in the download page, right next to where it say " Begin Download " check image
DrakenFX said:
ok i updated the Binary on the zip file should work now, This is why i don't like posting without having Device for testing :crying:
Click to expand...
Click to collapse
Any info on if it will work on the metro version yet?
Sent from my LGMS631 using Tapatalk
DrakenFX said:
md5 are the download link, right next to where it say " Begin Download " check image
Click to expand...
Click to collapse
Lol, sorry man. When I saw that it wasn't quite working yet, I didn't even click on them. Thanks a ton!
Sent from my SM-N900T using Tapatalk
---------- Post added at 08:21 AM ---------- Previous post was at 08:18 AM ----------
lmarisy said:
I am rooting as i write this then will install twrp and try with the Fix u posted , will report back shortly..
thanks!
Louie
---------- Post added at 10:07 PM ---------- Previous post was at 09:59 PM ----------
gives me an error when i try and flas the *,fix file.
it says Error executing updater binary in zip '/external_sd/ H63120b_Marshmallow_BootstackFIX.zip
error flashing zip
Louie
Click to expand...
Click to collapse
I can't afford to test, but am anxiously awaiting your test. Please report back after trying the new files!
Thanks to everyone working on this!
Sent from my SM-N900T using Tapatalk
Binary still wrong
Boot stack wont flash. Binary still wrong
Idk if this is against the rules or not (and if it is remove the link. And i apologize) but in the event its not someone may want to try this method if they are impatient about getting marshmallow on their metro stylo.
http://androidforums.com/threads/metro-pcs-lg-g-stylo-users-update-to-marshmallow.1011917/
I take no credit for this. Wasnt my work or idea. (Credit is given in op by the original poster)
Its many extra steps but supposedly works. Let me know what your experience was
I got my Metro Stylo up running 6.0 root and everything?
Using which method?
Hi all,
Tried searching, got nowhere.
I've received the OTA 1.53.401.5.
I have S-ON, Magisk root, stock recovery, stock system, custom Kernel
What would happen if I attempt to install the OTA without returning boot.img to stock? (Apart from overwriting the kernel with stock kernel).
Has anyone attempted? - Magisk should be able to persist root on the B partition since v14.1
Last, but not least, if the OTA fails....will my device bootloop? Or will it abort the update before making any changes?
The idea here, is it safe to attempt despite not being near to a PC to recover the device? Or will I need to be prepared to RUU my device in case of failure?
Kyuubi10 said:
Hi all,
Tried searching, got nowhere.
I've received the OTA 1.53.401.5.
I have S-ON, Magisk root, stock recovery, stock system, custom Kernel
What would happen if I attempt to install the OTA without returning boot.img to stock? (Apart from overwriting the kernel with stock kernel).
Has anyone attempted? - Magisk should be able to persist root on the B partition since v14.1
Last, but not least, if the OTA fails....will my device bootloop? Or will it abort the update before making any changes?
The idea here, is it safe to attempt despite not being near to a PC to recover the device? Or will I need to be prepared to RUU my device in case of failure?
Click to expand...
Click to collapse
I think it will fail if it doesn't pass its checks before rebooting.
(mine did as I had booted to twrp, but then I am used to backing up my data and RUUing these days)
Electronic Punk said:
I think it will fail if it doesn't pass its checks before rebooting.
(mine did as I had booted to twrp, but then I am used to backing up my data and RUUing these days)
Click to expand...
Click to collapse
Yeah, due to some tests I've been doing with Dolby Atmos I've gotten used to RUUing too... But it still is such a pain in the ass.
So can you confirm if it is a bootloop when OTA fails?
Kyuubi10 said:
Yeah, due to some tests I've been doing with Dolby Atmos I've gotten used to RUUing too... But it still is such a pain in the ass.
So can you confirm if it is a bootloop when OTA fails?
Click to expand...
Click to collapse
I didn't get as far as rebooting. The OTA started then failed without making any changes.
Kyuubi10 said:
Yeah, due to some tests I've been doing with Dolby Atmos I've gotten used to RUUing too... But it still is such a pain in the ass.
So can you confirm if it is a bootloop when OTA fails?
Click to expand...
Click to collapse
hey mate!
it won't bootloop, because it won't reach that far xD it will just fail. you need stock boot, system and vendor. if you've messed with system/vendor it will fail anyway
In another thread @Freak07 responded me that it could work only if some file in boot or vendor image had a certain value. It hadn't for me but I am sorry I forgot what it was exactly.
I believe it was either on @Freak07 recovery thread or in his kernel thread.
---------- Post added at 09:36 PM ---------- Previous post was at 08:38 PM ----------
EMJI79 said:
I am proposed OTA by the system but I can't do it, right?
We always have to RUU-OTA-ROOT then install the kernel?
I thought I had read that somewhere but I can't find it, so if someone could confirm?
Click to expand...
Click to collapse
It depends. Check the lifetime_kb_writes file like it’s mentioned in the second post of the twrp thread. If it doesn’t show 0 for system or vendor OTA will fail and you have to RUU.
Hi,
It is imperative to be in stock and not root.Sans this office error and the OTA does not settle.Je got to have version 1.30.401.2 on the A and version 1.53.401.5 on the B.Version on the A custom and root, the version on the B just root.
But not easy to get there!
DeeZZ_NuuZZ said:
hey mate!
it won't bootloop, because it won't reach that far xD it will just fail. you need stock boot, system and vendor. if you've messed with system/vendor it will fail anyway
Click to expand...
Click to collapse
Hey DeeZZ! Long time! XD I keep saying I'll come back but I never do.
Good to know that it won't bootloop... What I want to try tbh is follow the steps by Magisk dev to take OTA.
In theory if I flash back a clean system.img and vendor.img I should successfully be able to uninstall magisk take OTA and root the new update through Magisk Manager.
EMJI79 said:
In another thread @Freak07 responded me that it could work only if some file in boot or vendor image had a certain value. It hadn't for me but I am sorry I forgot what it was exactly.
I believe it was either on @Freak07 recovery thread or in his kernel thread.
---------- Post added at 09:36 PM ---------- Previous post was at 08:38 PM ----------
It depends. Check the lifetime_kb_writes file like it’s mentioned in the second post of the twrp thread. If it doesn’t show 0 for system or vendor OTA will fail and you have to RUU.
Click to expand...
Click to collapse
Thanks for this link! It was very useful.
But I do have one complaint about it... Surely the file would not be 0 while Magisk mods are active.
I have no system mods, and all mods I have are Magisk systemless mods.
So for the file to have a value greater than 0 it must be because while Magisk is active the file "believes" there are system modifications, due to following the sym-links created by Magisk.
This being said I couldn't find the vendor "sda#" on my sys/fs.
Additionally could I possibly change the file to have a "0" value? Thus fooling the OTA mechanism?
So many theories! I hope one of them works... I'm tired of RUU and losing my data.
I don't think you can change it manually, it would be too easy.
EMJI79 said:
I don't think you can change it manually, it would be too easy.
Click to expand...
Click to collapse
Lol true