with very little activity lately for the LGV20, specifically the H918 T-Mobile variant, I created a TWRP flashable package for the recent H91810q release. this zip flash every partition included in the latest KDZ package with the exception of recovery to keep TWRP. standard disclaimer applies, you do all of this at YOUR OWN risk! because 10q is not rootable, you need to be root'd before flashing this! failure to do so will probably cause you to lose root and/or lose TWRP! and worst of all, because 10q can't be downgraded to 10j (last version where you can still obtain root via dirtycow) because of Anti-RollBack, you're fscked!
NOTE1: you can find the partitions that will be flashed in the updater-script. to be extra cautious you can back up all of the partitions that will be overwritten with the following: dd if=/dev/block/bootdevice/by-name/{partition} of=/external_sd/backup/{partition}.img.
NOTE2: boot partition has been modified only to remove rctd, nothing else so I consider this to still be stock
Instructions:
download H91810u.zip file listed below and put on microSD card
download your choice of root and put on microSD card, choose from either Magisk or SuperSU *Note: v12.0 of Magisk does not work with the LGV20 device in general and v14.0 is recommended.
backup any data from internal "SD card"
boot into TWRP (requires TWRP recovery to already be installed)
create a TWRP backup of the device
flash zip from microSD card by using "Install"
FLASH YOUR CHOICE OF ROOT - Flashing root is VERY IMPORTANT BEFORE REBOOTING!
reboot
profit!
Download:
H91810q.zip
old 10q md5sum: 8c2e76ded9759a63b1ffac86f3941649
new 10q md5sum: c7d4086b3a0a786d1501ef7e4ce22f32 - re-zipped in Linux for proper alignment
H91810r.zip
wrong 10r md5sum: 9e2e1f8c56079d7bf629ce5e375d7551 (this is actually the md5sum for the KDZ)
correct 10r md5sum: 194b2bc41aa6dbdd7b9a371392f7b930
H91810s.zip
10s md5sum: f187fdefe4c3612c5811e9fbeb0748c5
H91810t.zip - rctd and triton both disabled, previous versions only removed rctd
10t md5sum: b00c2f644b15eb15e459c48830caa5da
H91810u.zip - rctd and triton both disabled, previous versions only removed rctd
10u md5sum: f51b2b11a30dc448b0da0edc750bb587
Flashing Process (what flashing this zip does):
flash necessary partition images with the exception of recovery (to keep TWRP) from the KDZ
rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak to prevent stock recovery from being installed on boot
wipes dalvik-cache and cache
BIG thanks to @McNutnut on guidance, as well as his script to put all of this together!
also thanks to @bullghost for the KDZ extractor (https://forum.xda-developers.com/showthread.php?t=2600575)
@Tilde88 for the original updater-script template w/root (https://forum.xda-developers.com/v20/development/us996-nrd90m-modded-notsostock-rom-v5-1-t3526542)
Awesome thanks.. I'm on it!
---------- Post added at 12:50 AM ---------- Previous post was at 12:07 AM ----------
Didn't work... Still shows 10p. I noticed the flash process was rather fast also.
storm68 said:
Awesome thanks.. I'm on it!
---------- Post added at 12:50 AM ---------- Previous post was at 12:07 AM ----------
Didn't work... Still shows 10p. I noticed the flash process was rather fast also.
Click to expand...
Click to collapse
Dude, thanks for whipping this out so fast! (TWSS) I will get right on making a debloated rom from this. Is it ARB 1?
So I HAVE to flash root? Sometimes I don't flash root because of my gear S3 watch.
I just flashed but still showing 10p. But the kernel info shows Sept 12. So the kernel is updated but wondering on why it still shows 10p on software info @ about phone.
storm68 said:
Awesome thanks.. I'm on it!
---------- Post added at 12:50 AM ---------- Previous post was at 12:07 AM ----------
Didn't work... Still shows 10p. I noticed the flash process was rather fast also.
Click to expand...
Click to collapse
hold on, let me re-zip and re-upload. I had used two different methods to add the files to the archive so I'm going to re-do it all with one method
texasaggie1 said:
Dude, thanks for whipping this out so fast! (TWSS) I will get right on making a debloated rom from this. Is it ARB 1?
So I HAVE to flash root? Sometimes I don't flash root because of my gear S3 watch.
Click to expand...
Click to collapse
yes, this is ARB1 and yes, root is needed if you want to stay root'd
As you can see the updater script shows install 10p.
storm68 said:
As you can see the updater script shows install 10p.
Click to expand...
Click to collapse
yep, for some reason using Windows to create zip files causes inconsistencies. I've zipped up everything in Linux this time and double checked the updater script to make sure everything is good to go and am uploading it as I type... I've already updated the OP with the new md5sum and the link should remain the same. I'll give a heads up once it's live
Ok thanks for your time. Appreciate it. ?
storm68 said:
Ok thanks for your time. Appreciate it.
Click to expand...
Click to collapse
done! uploaded and downloaded myself to verify everything is the correct one. this should bring you to 10q for everything... sorry for the troubles of flashing again. don't forget to flash root just in case lol
No problem. No apology needed being you really don't have to do this for the community. Thanks again.
Sorry if I'm asking an obvious question but when did t mobile release a new update? I thought the latest version was 10p???
Flashed... All good!
---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------
Still_living714 said:
Sorry if I'm asking an obvious question but when did t mobile release a new update? I thought the latest version was 10p???
Click to expand...
Click to collapse
Mine came yesterday. Updater to 10q. If you haven't gotten it yet you will..
storm68 said:
Flashed... All good!
---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------
Mine came yesterday. Updater to 10q. If you haven't gotten it yet you will..
Click to expand...
Click to collapse
Any big improvements that you can see?
i flashed and once i unlocked my phone, it kept saying process.android keeps stopping repeatedly. booted back into twrp to restore the backup i made in twrp and now the keeps rebooting to the lg screen. Can anybdoy help me out please. i was ww kernel and 10k
Still_living714 said:
Any big improvements that you can see?
Click to expand...
Click to collapse
I would have to wait and see. But first hand it's about the same as 10p no rctd.
---------- Post added at 04:02 AM ---------- Previous post was at 03:26 AM ----------
Lgv20user said:
i flashed and once i unlocked my phone, it kept saying process.android keeps stopping repeatedly. booted back into twrp to restore the backup i made in twrp and now the keeps rebooting to the lg screen. Can anybdoy help me out please. i was ww kernel and 10k
Click to expand...
Click to collapse
First of be advised that this is anti roll back. Once on it you can't go backwards to other older roms. In reference to your problem you'll have to do a battery pull. Put battery back in. Now hold down volume down and power button at the same time, when you see LG screen release power button for two seconds then push again holding down power. During all this never release volume down. Now you'll get a reset screen with yes and no option. Use volume key to choose yes, twice..... This will get you back to TWRP. In your case I wouldn't even bother with back up but you can try again if want. What I would do is flash something else that I know works. Then decide from there what to do... Maybe redownload again. May be corrupt some how. I assume your on h918. Hope so! Good luck.
storm68 said:
I would have to wait and see. But first hand it's about the same as 10p no rctd.
---------- Post added at 04:02 AM ---------- Previous post was at 03:26 AM ----------
First of be advised that this is anti roll back. Once on it you can't go backwards to other older roms. In reference to your problem you'll have to do a battery pull. Put battery back in. Now hold down volume down and power button at the same time, when you see LG screen release power button for two seconds then push again holding down power. During all this never release volume down. Now you'll get a reset screen with yes and no option. Use volume key to choose yes, twice..... This will get you back to TWRP. In your case I wouldn't even bother with back up but you can try again if want. What I would do is flash something else that I know works. Then decide from there what to do... Maybe redownload again. May be corrupt some how. I assume your on h918. Hope so! Good luck.
Click to expand...
Click to collapse
what do you recommend i flash
Lgv20user said:
what do you recommend i flash
Click to expand...
Click to collapse
Well we really don't know if your system went to 10q now, so........ You can try again. On both, the backup or 10q. Since you know now how to get to TWRP with battery pull you can try both, see what works. Try backup first. If it doesn't work you may have system in 10q now being you backed up a 10k system may not work now. If it doesn't try q again. If that doesn't work then download 10p or redownload 10q and side load on TWRP from computer. Then flash again. These are steps I would do.. if someone tells you different then it's your choice. Different ways for different things.
storm68 said:
Well we really don't know if your system went to 10q now, so........ You can try again. On both, the backup or 10q. Since you know now how to get to TWRP with battery pull you can try both, see what works. Try backup first. If it doesn't work you may have system in 10q now being you backed up a 10k system may not work now. If it doesn't try q again. If that doesn't work then download 10p or redownload 10q and side load on TWRP from computer. Then flash again. These are steps I would do.. if someone tells you different then it's your choice. Different ways for different things.
Click to expand...
Click to collapse
so 10q is showing up. i am having issues with the modem i believe because i dont get tmobile recepetion and as soon as i put into airplane mode, the error message stops.
I haven't tried the 10p weta kernel yet but it may not work being this stock kernel on 10q is updated to the September security patch. May try later today.
First off, thanks for keeping my beloved H918 alive!. Thought all future dev for the V20 was dead.
Now a question. Any timeframe on a debloated version? Not in a hurry mind you, just curious.
Related
Hey all i accidentally hit the OTA update "OK" button when it popped up on my screen. I've been deferring it for the past few months but my finger slipped and hit the "OK" instead of the "defer" and choosing a date to ask again.
I have a looping "Teamwin" logo and it keeps looping.. Cant seem to do anything. I've taken out the battery and then start it up but it still does the same thing.
Any advice, step by step to get out of this loop?
Thanks!
David
you can not OTA update with a custom recovery...time for a date with Odin.
Historical coodsen
droidstyle said:
you can not OTA update with a custom recovery...time for a date with Odin.
Click to expand...
Click to collapse
Would you care to give me a link to do this with a note 2, droidstyle?
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
droidstyle said:
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
Click to expand...
Click to collapse
Whats the key combo to see if i can boot into recovery and ill try it
droidstyle said:
yep click the link in my sig...refer to section 1b. you can probably get away with using root66 so you do not have to reroot and unlock BL.
Also when you get back up and running I would recommend freezing SDM1.0 apk with a App such as Titanium back up pro and you will no longer get prompted for OTA updates.
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
hold on a sec, can you boot into recovery? If so you can probably wipe data and re flash the rom you were on.
Click to expand...
Click to collapse
I just did the Power+home button+volume up and i get a "WARNING!!!!"
a custom os can cause critical problems......
If you want to download a custom OS, etc etc..
stealthrt said:
I just did the Power+home button+volume up and i get a "WARNING!!!!"
a custom os can cause critical problems......
If you want to download a custom OS, etc etc..
Click to expand...
Click to collapse
That's download mode...pull battery and start over.
pwer+home+volume down gets you into recovery.
droidstyle said:
That's download mode...pull battery and start over.
pwer+home+volume down gets you into recovery.
Click to expand...
Click to collapse
Well i just started flashing in odin.... will update when its done.
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
stealthrt said:
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
Click to expand...
Click to collapse
And doing the volume down+home+power sends me to the same screen (WARNING!!!... custom os.. etc etc)
Any other advice?
stealthrt said:
Any other advice?
Click to expand...
Click to collapse
he accidentally told you to hit the same button combo. its volume UP home and power. probably still wont boot into recovery though
B_I_N_G_E said:
he accidentally told you to hit the same button combo. its volume UP home and power. probably still wont boot into recovery though
Click to expand...
Click to collapse
Yeah it still does the same teamwin loop doing it that way.
What else can i try?
stealthrt said:
Yeah it still does the same teamwin loop doing it that way.
I tried again to flash and it still is at the loop after a restart...
and also...
What else can i try?
Click to expand...
Click to collapse
did you have the right pda file? for instance was your phone updated to vrall4 or vramc3 and you chose the vraljb file?
B_I_N_G_E said:
did you have the right pda file? for instance was your phone updated to vrall4 or vramc3 and you chose the vraljb file?
Click to expand...
Click to collapse
ive only tried the root66 rom.
stealthrt said:
ive only tried the root66 rom.
Click to expand...
Click to collapse
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
B_I_N_G_E said:
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
Click to expand...
Click to collapse
Alright i flashed the bootloader and all seems to be fine. I got 2 tutorials mixed up so i though one was using bootloader as the ROM.
All is good now thanks droidstyle and B_I_N_G_E.
B_I_N_G_E said:
if you had an updated firmware then that file wouldnt work for you. i also noticed though you put that file in the bootloader field instead of the pda field when you tried flashing it one of those times. that may have been a bad thing. you could try to flash the other file marked vramc from that thread.
Click to expand...
Click to collapse
root66 works on all devices with the current firmware since it does not contain a bootloader, recovery, or wipe data. Sometimes it will cause a bootloop which all that is needed is to wipe data in recovery.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
stealthrt said:
Doesnt look like obin did anything. after it finished it just rebooted and i still have the teamwin loop.
Click to expand...
Click to collapse
you need to boot into recovery and wipe data...if you can get into recovery the a full odin package will need to be flashed such as stock VRAMC3. However it looks like you figured it out.
Galaxy S5 Sport SM-G860P Stock Roms
OH1 stock Lollipop Kernel added to the bottom of this post!
Kitkat 4.4.2 NG3 Stock Deodexed ROM
This is a base test version.
Someone please backup, flash with custom recovery and let me know how it goes in case I need to make some further changes.
Download Link -- > SM-G860P_NG3_ROOTED_DEODEXED.TEST.zip
Deodexed Rom Features (so far):
- root included
- busybox
- init.d support/repacked kernel
Full Stock Tar Recovery
Restore the phone back to stock.
Download Link -- > G860PVPU1ANG3_G860PSPT1ANG3_SPR.zip
Custom Recovery:
Flash custom roms and mods.
[RECOVERY] CWM S5 Sport SM-G860P
Instructions to Install Tar Files with Odin
• The full tar does not wipe Data or internal SD.
You may want to do a full wipe in custom recovery before flashing full tar if you have issues with data apps.
• Extract (unzip) the firmware file
• Extract Odin -- Odin v3.09 Download Link
• Power down the phone (or pull the battery, it is important to flash the OTA from a powered off state)
• Open Odin v3.09
• Boot the phone in Download Mode (press and hold Home + Power + Volume Down buttons)
• Connect phone and wait until you get a blue sign in Odin
• Add the firmware/recovery file to AP / PDA (depending on version of Odin)
• For modems, add the file to CP / PHONE (depending on version of Odin)
• Make sure re-partition is NOT ticked
• Click the start button, sit back and wait a few minutes
I think its possible to flash a Sprint SM-G900P 4.4.2 rom on this phone if you follow the following steps:
1. Have custom recovery already installed and a backup in place in case you need to flash back.
2. Place the rom and stock kernel on phone SD
3. Boot into custom recovery, do a full wipe
4. Install the SM-G900P touchwiz based rom, do not reboot yet
5. Flash the stock SM-G860P _NG3_Stock_Kernel.zip provided in Post #1.
6. Restart the phone
@SeanRinVA and @wolfleatherworks :
You guys have showed interest in getting MOAR on your SM-G860P phones, so I thought I'd mention you here to help you find this thread. Make sure to have a nanoid backup beforehand and let everyone know how it went.
I'd watched the MOAR thread for a while, but it wasn't compatible with the SM-G860P (hung boot).
Sent from my SM-G860P using Tapatalk
SeanRinVA said:
I'd watched the MOAR thread for a while, but it wasn't compatible with the SM-G860P (hung boot).
Sent from my SM-G860P using Tapatalk
Click to expand...
Click to collapse
@tdunham just posted this yesterday and the second post this morning, but yes, he's looking for someone to test it (neither of us have the G860). If you have the time, could you give this a try and post back success or failure? Especially if you can get MOAR installed.
Ramer said:
@tdunham just posted this yesterday and the second post this morning, but yes, he's looking for someone to test it (neither of us have the G860). If you have the time, could you give this a try and post back success or failure? Especially if you can get MOAR installed.
Click to expand...
Click to collapse
I can test it tonight. I've downloaded the Kernel...now to download the latest MOAR.
I've got an S5 Sport, just picked up today. Will be testing the kernel with MOAR.
---------- Post added at 08:32 PM ---------- Previous post was at 07:58 PM ----------
Well it doesn't seem to be boot looping, I'll let it sit and cook for a bit longer. Currently it's just flashing the android white text and disappearing, not sure how long it should normally be on 1st boot.
---------- Post added at 08:46 PM ---------- Previous post was at 08:32 PM ----------
Doesn't seem to have worked, I waited a good while but it didn't go any further. Attempted downloading your Rooted Deodexed test but it downloads as a 0kb file.
EDIT: Tried another mirror, seems to be downloading properly now.
---------- Post added at 09:34 PM ---------- Previous post was at 08:46 PM ----------
Got it downloaded, copied over via adb -- attempted install, getting (bad) - installation aborted.
---------- Post added at 09:42 PM ---------- Previous post was at 09:34 PM ----------
Confirmed MD5 match. Ideas?
KrimsonStarfly said:
Doesn't seem to have worked, I waited a good while but it didn't go any further. Attempted downloading your Rooted Deodexed test but it downloads as a 0kb file.
EDIT: Tried another mirror, seems to be downloading properly now
Got it downloaded, copied over via adb -- attempted install, getting (bad) - installation aborted.
Click to expand...
Click to collapse
I'm not sure what adb was for. You don't have drivers installed with a running rom so you can copy everything over to the phone?
Did you download the stock rom last night because the stock rom last night had a problem and has since been replaced. The one you should have the same name as the link in the OP. I even flashed it to make sure it would at least run.
tdunham said:
I'm not sure what adb was for. You don't have drivers installed with a running rom so you can copy everything over to the phone?
Did you download the stock rom last night because the stock rom last night had a problem and has since been replaced. The one you should have the same name as the link in the OP. I even flashed it to make sure it would at least run.
Click to expand...
Click to collapse
I was using ADB since I didn't want to restore from backup until I was done testing. I'll try re-downloading and doing it over again to see if I can get it working, I'm off work today so now is the perfect time to try it further.
So this has me stumped -- For some unknown reason, I seem to be unable to copy over SM-G860P_NG3_ROOTED_DEODEXED.TEST.zip using MTP. I fiddled with drivers for the last hour and i'm at a loss -- it doesn't seem to be a driver problem, I can copy over MOAR and other files, but it won't let me copy over your test at all.
tdunham said:
I think its possible to flash a Sprint SM-G900P 4.4.2 rom on this phone if you follow the following steps:
1. Have custom recovery already installed and a backup in place in case you need to flash back.
2. Place the rom and stock kernel on phone SD
3. Boot into custom recovery, do a full wipe
4. Install the SM-G900P touchwiz based rom, do not reboot yet
5. Flash the stock SM-G860P _NG3_Stock_Kernel.zip provided in Post #1.
6. Restart the phone
Click to expand...
Click to collapse
Ramer said:
@tdunham just posted this yesterday and the second post this morning, but yes, he's looking for someone to test it (neither of us have the G860). If you have the time, could you give this a try and post back success or failure? Especially if you can get MOAR installed.
Click to expand...
Click to collapse
works booted up with moar rom :good:
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
tdunham said:
Galaxy S5 Sport SM-G860P Stock Roms
Kitkat 4.4.2 NG3 Stock Deodexed ROM
This is a base test version.
Someone please backup, flash with custom recovery and let me know how it goes in case I need to make some further changes.
Download Link -- > SM-G860P_NG3_ROOTED_DEODEXED.TEST.zip
Deodexed Rom Features (so far):
- root included
- busybox
- init.d support/repacked kernel
Full Stock Tar Recovery
Restore the phone back to stock.
Download Link -- > G860PVPU1ANG3_G860PSPT1ANG3_SPR.zip
Custom Recovery:
Flash custom roms and mods.
[RECOVERY] CWM S5 Sport SM-G860P
Instructions to Install Tar Files with Odin
• The full tar does not wipe Data or internal SD.
You may want to do a full wipe in custom recovery before flashing full tar if you have issues with data apps.
• Extract (unzip) the firmware file
• Extract Odin -- Odin v3.09 Download Link
• Power down the phone (or pull the battery, it is important to flash the OTA from a powered off state)
• Open Odin v3.09
• Boot the phone in Download Mode (press and hold Home + Power + Volume Down buttons)
• Connect phone and wait until you get a blue sign in Odin
• Add the firmware/recovery file to AP / PDA (depending on version of Odin)
• For modems, add the file to CP / PHONE (depending on version of Odin)
• Make sure re-partition is NOT ticked
• Click the start button, sit back and wait a few minutes
Click to expand...
Click to collapse
i tried SM-G860P_NG3_ROOTED_DEODEXED.TEST.zip but it aborted and said bad could be the . between DEODEXED and TEXT i try to rename but then it wouldnt let me put it on my phone. just a though
1991mustang50 said:
works booted up with moar rom :good:
---------- Post added at 09:39 PM ---------- Previous post was at 09:33 PM ----------
i tried SM-G860P_NG3_ROOTED_DEODEXED.TEST.zip but it aborted and said bad could be the . between DEODEXED and TEXT i try to rename but then it wouldnt let me put it on my phone. just a though
Click to expand...
Click to collapse
I accidentally added a space in the filename. I did flash it to test but now I think I removed the space in the name before doing so. If possible, try downloading to pc first and let me know how it goes in case I need to reupload it to the hosting site with a corrected filename.
1991mustang50 said:
works booted up with moar rom :good:
Click to expand...
Click to collapse
So, I'm not attempting to be dumb here, but it might be inevitable.
G900 stock roms boot with G860 kernel?
I use MOAR ROM(havent tried any other roms yet) for 900P and the the kernel zip in post #1 and using steps in post #2 I am running on it now
Great. Being a stock-based ROM, I would imagine that all stock Roms work with G860 kernel. Consequently, all AOSP ROMs should work with a kernel compiled for G860. There are 2 new G860s in the house and my intent was to compile CM11/12 for the Sport; however, if all that is necessary is the kernel&modules I won't bother pulling blobs.
Thanks. The phones aren't entirely at my disposal or I would do more testing.
tdunham said:
I accidentally added a space in the filename. I did flash it to test but now I think I removed the space in the name before doing so. If possible, try downloading to pc first and let me know how it goes in case I need to reupload it to the hosting site with a corrected filename.
Click to expand...
Click to collapse
Redownloaded still a no go it just go to opening update and then fails sorry for bad news thanks for trying
It works!
I used the instructions here to install the rom for the G900P as linked to below. I've messed with it only for about 20 minutes but it worked perfectly fine! So much bloatware though, and I'm coming from the S3 scene and am not too familiar with what the G900P had to offer in terms of custom ROMs. If anyone knows a good lightweight one with powerful customization options please let me know so I can try it. I am doing my first backup of this ROM as I type this and will also be doing a restore of my previous ROM (stock with the bloatware removed manually) for now and will probably tweak the MOAR ROM more later this week. Just want to say thank you to everyone in this thread, you guys are amazing!
http://forum.xda-developers.com/showthread.php?t=2790808
I'm going to give the MOAR of try with the kernel from post one.. I really do hope that more development comes to this phone..
doubledragon5 said:
I'm going to give the MOAR of try with the kernel from post one.. I really do hope that more development comes to this phone..
Click to expand...
Click to collapse
Well, at least you guys can run a custom rom now.
I wish I could be more help but I have the SM-G900P but thought I'd take a shot at getting the Sport a little help.
tdunham said:
Well, at least you guys can run a custom rom now.
I wish I could be more help but I have the SM-G900P but thought I'd take a shot at getting the Sport a little help.
Click to expand...
Click to collapse
I saw a couple of links in the recovery thread for the sport full resotore.. One link the files are over a gig, the other one is for about 848mb.. I wounder which is the real deal... The first link I could not download crap, but the second one I did. BTW is the modem included in your file for your rom?I was woundering because if I flash MOAR were can I find the modem or does it matter
Hey folks. I've tried every search here & via Google that I can think of and the answer won't come to me. Here's the weird, surreal, but I assure you very current problem. I screwed around trying to install Jasmine 5.0 and it has bitten me in the rear-end. In order to fix a problem I had with it, I wanted to KDZ back to stock and start over. Unfortunately it won't let me do that. When I try to go into Download mode, it gives me a secure boot error, turns the screen black and flashes the LED at me multicolor-style. The only way to get out of that is a battery pull.
I can boot into Recovery just fine. I'm back on SkyDragon 4.4 as we speak, but not being able to get into download mode is what I'd consider a BIG PROBLEM, considering that's how you fix soft bricks. If I ever have a problem, I'm toast. Thus, my flashing days are pretty well over unless I can get this fixed.
I did find this from @bweN diorD :
bweN diorD said:
well it should be the aboot then. while testing, the only things that gave me a secure boot error were boot (which i just gave you) and aboot.
im not sure how you would install aboot, i dont have a flashable zip. maybe using terminal in twrp, but i have little experience to give advice on that.
Click to expand...
Click to collapse
Does that mean I need to figure out how to get 12B aboot & boot properly restored from the img thread? If so, does anybody know HOW one might do that? I apologize, but I'm VERY much at my wit's end here and can't figure it out right now. Any help at all would be greatly appreciated.
EDIT - FIXED!
annoyingduck said:
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
Click to expand...
Click to collapse
From what I've seen told to other people in the same situation, you need to flash the laf.img, but you'll have to look up how to do that. Probably via adb connected through TWRP? Shrug. Good luck dude, sorry to hear.
Sent from my VK810 4G
There may be a kind person that has a solution. If whatever it is works (he's busy right now), I'll definitely post it here and make it as searchable as possible!
roirraW "edor" ehT said:
From what I've seen told to other people in the same situation, you need to flash the laf.img, but you'll have to look up how to do that. Probably via adb connected through TWRP? Shrug. Good luck dude, sorry to hear.
Sent from my VK810 4G
Click to expand...
Click to collapse
My thoughts exactly, I'll go over that with him, just want to check a few things first.
hokiealumnus said:
There may be a kind person that has a solution. If whatever it is works (he's busy right now), I'll definitely post it here and make it as searchable as possible!
Click to expand...
Click to collapse
How are you going about booting into download mode?
annoyingduck said:
How are you going about booting into download mode?
Click to expand...
Click to collapse
Power off, hold volume up & plug in USB cable.
hokiealumnus said:
Power off, hold volume up & plug in USB cable.
Click to expand...
Click to collapse
Ok, I'm showing the same symptom. Let me test on my device first. give me a few min
annoyingduck said:
Ok, I'm showing the same symptom. Let me test on my device first. give me a few min
Click to expand...
Click to collapse
I've a possible fix... hangouts
just checked to see if i have that issue...ive got everything working fine here...running JasmineROM v5.0 and never had a boot signature error...until...just for the heck of it tried download mode and low and behold my download mode give me that error...
+1 on the secure boot error in download mode. Much appreciated when you guys develop a fix if you could post it here.
jdgesmlls said:
+1 on the secure boot error in download mode. Much appreciated when you guys develop a fix if you could post it here.
Click to expand...
Click to collapse
Working on it with the man himself, just need some testing time...
annoyingduck said:
Working on it with the man himself, just need some testing time...
Click to expand...
Click to collapse
Let me know if you need anyone to test stuff, I am up and running, can get into recovery and restore but again as stated if .tot is required I am in the same boat....
No worries, take all the time you need. Thankfully our devices are working.
We should probably just hold off on our flashing addiction until it's fixed.
hokiealumnus said:
No worries, take all the time you need. Thankfully our devices are working.
We should probably just hold off on our flashing addiction until it's fixed.
Click to expand...
Click to collapse
Yes, definitely... I am fully functional, can make calls and such so your work and expertise is much appreciated!
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
annoyingduck said:
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
Click to expand...
Click to collapse
So I have already restored back to Illusion, and I did that because I was getting an LGSmartCover FC in J-5 once I booted up. Can I flash this in recovery and keep my current setup or do I have to go through the install of J-5 again.
Again, thanks for the quick turnaround on this...
EDIT*** I think nevermind, I thought about it for a minute and just use the same install instructions but replace the contents of FixDownloadMode.zip??
annoyingduck said:
Download mode fixed, @hsbadr will be along momentarily with a file to flash the same way you did J-5
---------- Post added at 11:14 PM ---------- Previous post was at 11:07 PM ----------
Go here for download mode fix: http://forum.xda-developers.com/showpost.php?p=59357420&postcount=2237
Don't forget to delete the previous images from your internal sd
Works perfectly, just tested
Click to expand...
Click to collapse
Works like a charm! Thanks to you both - @hsbadr & @annoyingduck !!!! We would have been in a heck of a bind without your help.
you can flash this on anything....when we were testing J-5 we got a little over protective and decided to upgrade what the new download mode fix script installs to 23b images, which conflict with bumped recoveries. It didn't need to be done, so you should do this repair if you flashed J-5 either way - no matter what current rom your on, it won't effect anything other than download mode. Next J-5 will fix it for everyone. Basically bump requires KK aboot. Download mode requires aboot to match rpm,tz,and laf. Once those get upgraded to LP, download mode fails because of the bumped aboot. Turns out, we didn't need those images to get LP booting, so fixes are in the future.
annoyingduck said:
you can flash this on anything....when we were testing J-5 we got a little over protective and decided to upgrade what the new download mode fix script installs to 23b images, which conflict with bumped recoveries. It didn't need to be done, so you should do this repair if you flashed J-5 either way - no matter what current rom your on, it won't effect anything other than download mode. Next J-5 will fix it for everyone. Basically bump requires KK aboot. Download mode requires aboot to match rpm,tz,and laf. Once those get upgraded to LP, download mode fails because of the bumped aboot. Turns out, we didn't need those images to get LP booting, so fixes are in the future.
Click to expand...
Click to collapse
That worked perfect!
Thanks @hsbadr, @annoyingduck!! as always, great work!!
annoyingduck said:
you can flash this on anything....when we were testing J-5 we got a little over protective and decided to upgrade what the new download mode fix script installs to 23b images, which conflict with bumped recoveries. It didn't need to be done, so you should do this repair if you flashed J-5 either way - no matter what current rom your on, it won't effect anything other than download mode. Next J-5 will fix it for everyone. Basically bump requires KK aboot. Download mode requires aboot to match rpm,tz,and laf. Once those get upgraded to LP, download mode fails because of the bumped aboot. Turns out, we didn't need those images to get LP booting, so fixes are in the future.
Click to expand...
Click to collapse
ok do i have to do a clean flash of jamison5.0 before i flash the fix or can i do a factory reset nd then flash the fix via twrp adb?
nevermind...i just rebooted to recovery and flash...download mode work and didnt have to reflash rom thanks @annoyingduck @hsbadr i was scared here because flashings an addiction
For the download mode fix you shouldn't need to factory reset. Heh, when I used it I was back on KK, booted into recovery, flashed the fix and rebooted straight back into the ROM.
Just got an update on my watch and, as always, pulled the update.zip for you guys!
If you're having troubles installing this ZIP please refer to this post here: http://forum.xda-developers.com/showpost.php?p=67403296&postcount=19
----------
Quick Install "Guide" if it's still failing for you:
1) Install TWRP from THIS THREAD HERE
2) Reboot into fastboot mode by turning the watch off and on again and while the black screen shows up constantly swipe from the left upper corner to the lower right corner.
3) Flash the TWRP provided above and reboot into recovery, then push the unpacked TWRP backup into "/sdcard/TWRP/BACKUPS/xxxxxxxxxxx/" (to get the last folder simply make a backup of only your boot partition first, it's the fastest)
4) Restore the backup provided IN THIS POST HERE onto your watch via the in 1 flashed TWRP
1) MUCH EASIER: Flash these instead the TWRP way, far far easier!
2) Let the OTA update install automatically
----------
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
>> OneDrive <<
EpicLPer said:
Just got an update on my watch and, as always, pulled the update.zip for you guys!
ZIP MD5: 6844d45bf6d4a1e1d6b15e908579d354
>> DROPBOX <<
>> GOOGLE DRIVE <<
Click to expand...
Click to collapse
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
Code:
Unable to statfs '/system/.'.
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
kokesh said:
I've got TWRP 3.0.?? on the watch and it refuses to flash, error is
I've flashed the stock recovery in LG G Watch tools. It went fine, so I've proceeded to install the update the standard way. It seemed to be fine, but than it stopped, with the "Dead Android" image. After using the reset button the built in recovery is dead, but the watch boots. Any ideas?
EDIT: TWRP won't mount /system for some reason, you tap the checkbox and nothing happens. Not even as RO.
Click to expand...
Click to collapse
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Xmaster24 said:
You have to use the edited one on my '' how to root guide'' as the official TWRP those not support squashfs
Click to expand...
Click to collapse
Thank you. Your recovery mounts /system, but I am still getting the same error.
kokesh said:
Thank you. Your recovery mounts /system, but I am still getting the same error.
Click to expand...
Click to collapse
yeah it can't write to it, you have to use the stock recovery for that. You are able to write to it but you must first format the partition as writable and then flash your system image/ backup. I'm getting the usual "old keys" error of TWRP not error you mentioned, just means The TWRP is too old base
---------- Post added at 11:13 AM ---------- Previous post was at 11:02 AM ----------
Those anyone have a link to the 6.0.1 stock recovery?
Those anyone have a link to the 6.0.1 stock recovery?
Click to expand...
Click to collapse
Isn't it possible to get it from the 6.0.1 OTA?
kokesh said:
Isn't it possible to get it from the 6.0.1 OTA?
Click to expand...
Click to collapse
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Xmaster24 said:
No, its stored in a propietary .dat file so good luck with that. Hopefully someone wasn't as foolish as me and deleted their recovery backup
Click to expand...
Click to collapse
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Xmaster24 said:
Nope I found it thank god. I had kept a backup of the awful stock kernel just in case when I was initially testing invisiblek's kernel. Luckily its still there in all its awful glory and I will share it here as when you boot up with the stock kernel the system auto flashes the stock recovery because thats how stock is for everything
Click to expand...
Click to collapse
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
EpicLPer said:
Btw. I tried going back to stock yesterday (without locking the bootloader tho) but I may have used a wrong or too old stock recovery version.
Also the only reason why the OTA is reporting an issue while flashing the package with the squashfs enabled TWRP is because the script gets a string back that's not identical with the one it expects. Maybe someone could "hack out" that check and make it TWRP flashable.
Click to expand...
Click to collapse
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that. I don't think the 6.0.1 source has been released yet so I don't think a recovery could be built with a 6.0.1 base of the lg g watch.
Xmaster24 said:
No the problem is the TWRP was built on an old base of the LG G watch specifically the last 5.1.1 update so the zip thinks the whole system is still on 5.1.1 as TWRP is still on that.
Click to expand...
Click to collapse
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
EpicLPer said:
That's exactly what I mean with the check and the "wrong" string it gets back I have no clue on how to disable this check inside the ZIP-script tho.
Click to expand...
Click to collapse
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
xmaster24 said:
it's not worth it, just flash the stock boot.img once i upload it, waiting for the art cache to build now
Click to expand...
Click to collapse
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Xmaster24 said:
it's not worth it, just flash the stock boot.img once I upload it, waiting for the ART cache to build now
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
omfg the new kernel actually has a hotplug!!!!!!!!!!!!!!!!!! Finally more than 1 core on stock!!!!!!!!!!!!!
Click to expand...
Click to collapse
You mean the new OTA kernel or the 6.X kernels?
EpicLPer said:
You mean the new OTA kernel or the 6.X kernels?
Click to expand...
Click to collapse
the stock kernel and nvm it was just AIDA64 glitching out, actually thought more than one core was in use The upside it thought the reboot button is back! don't know why they ever removed it but collio
Xmaster24 said:
nvm it was just AIDA64 glitching out, actually thought more than one core was in use ;-(
Click to expand...
Click to collapse
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
EpicLPer said:
I actually think there are more than 1 cores activate at a time now, the watch has gotten pretty fast with the latest updates and so on, I don't even feel the need for a custom kernel anymore since that.
Click to expand...
Click to collapse
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
EpicLPer said:
We could try flashing an older version of Android Wear (the one provided with the one Toolbox someone made here) and let it update to the latest version again.
Click to expand...
Click to collapse
Tried, didn't work. My guess is that it didn't handle squash FS. I was left with dead Android guy on the screen
For everyone to enjoy HERE is the stock kernel, @EpicLPer add this to the op to save everyone some trouble. NOTE: you have to boot to system once before the stock recovery is restored. Also it is a twrp backup so you have to adb push it to /sdcard/TWRP/BACKUPS/ to use it. If someone could just get the boot.img raw that would be great, I was too lazy to do it lel.
Xmaster24 said:
Nope after about 1 minute after boot the phone locks to 787mhz with userspace governor and I can confirm there is no CPU hotplug aswell. I don't know how you survive with the abysmal lag but ok cool. During the first minute of boot for whatever reason it uses 2 cores and ondemand, would rather have that always lol.
Click to expand...
Click to collapse
Actually... mine's running pretty well, no lag, no freezing animations, apps take 1 second to open and scrolling is smooth too.
Either I have some leftovers of an old kernel (which I don't think, or, hope) or I'm having a magic LG Watch
We need captures of the OTA payload, URL, metadata, etc. Anything we can get. We also need to study how our partitions change and which have changed. We also need a sound method to accept OTA when rooted (Temp Magisk revert, accept OTA, reinstall Magisk to other slot, reboot?) or revert to stock (restore both sets of boot and dtbo slots?).
Only lead I have is from our NSG friends. Action happens in /data/ota_package. Not sure if anything ends up in /cache.
This OTA includes fixes for GPS, December security level, and "general bugs fixed". n41 5G does not appear to be included, but recent FCC filings suggest that it's at least being tested.
https://fccid.io/2ABZ2-EE143/Test-Report/I19Z62071-WMD01-Part27-NR-Rev0-4569370
https://fccid.io/2ABZ2-EE143/Letter/FCC-cover-letter-C2PC-letter-template-rev1-4569357
It would be a really good time to bring back a Telegram or Discord channel.
Edit: OTA package snagged! https://android.googleapis.com/pack.../aa21536ec572b3c15ab76c49160441f041cf6a27.zip
Credit to xian from the NSG Telegram
<Mod edit>
Can I take this update if I was once rooted but have now flashed back to original boot.img? Obviously once updated I'll run the partition script to pull new partitions so I have virgin partitions on the new build.
OTA Direct Link
Not sure if it will take for me because of my haxing about.
---------- Post added at 12:13 ---------- Previous post was at 12:06 ----------
ntzrmtthihu777 said:
OTA Direct Link
Not sure if it will take for me because of my haxing about.
Click to expand...
Click to collapse
Didn't take. Investigating.
---------- Post added at 13:05 ---------- Previous post was at 12:13 ----------
Bad vbmeta_a hash.
---------- Post added at 13:07 ---------- Previous post was at 13:05 ----------
kirschdog1 said:
Can I take this update if I was once rooted but have now flashed back to original boot.img? Obviously once updated I'll run the partition script to pull new partitions so I have virgin partitions on the new build.
Click to expand...
Click to collapse
apparently you need all stock partition. I need a good vbmeta_a apparently
ntzrmtthihu777 said:
OTA Direct Link
Not sure if it will take for me because of my haxing about.
---------- Post added at 12:13 ---------- Previous post was at 12:06 ----------
Didn't take. Investigating.
---------- Post added at 13:05 ---------- Previous post was at 12:13 ----------
Bad vbmeta_a hash.
---------- Post added at 13:07 ---------- Previous post was at 13:05 ----------
apparently you need all stock partition. I need a good vbmeta_a apparently
Click to expand...
Click to collapse
U want mine from the read back so i can upload
omariscal1019 said:
U want mine from the read back so i can upload
Click to expand...
Click to collapse
Vbmeta_a? Sure. At class so I can't do anything with it yet.
Good news guys, Looks like we will be getting our MSM Tool in about a week
By creating our own ops or the kindness of OnePlus and leakers?
I'm not sure how that would change our situation with the new protections OnePlus is using on MSM tools. We'd have a good rescue method at the very least, but likely not a conversion method.
The only undisclosed exploit I know of is for the Sprint OnePlus 7 Pro 5G and that's purely for a bootloader and/or SIM unlock.
Edit: Saw your post in the other thread. I really hope the tech isn't full of crap like the others promising remote sessions that they never follow up on or provide the wrong files.
ntzrmtthihu777 said:
Vbmeta_a? Sure. At class so I can't do anything with it yet.
Click to expand...
Click to collapse
In a bit ill upload
So i shouldn't accept this update if rooted then?
omariscal1019 said:
In a bit ill upload
Click to expand...
Click to collapse
Cool. Looks like both sides have to be how TMobile
expects them to be in order for the update to work.
ntzrmtthihu777 said:
Cool. Looks like both sides have to be how TMobile
expects them to be in order for the update to work.
Click to expand...
Click to collapse
Yeah that **** happ n on the moto z2f back like two years ago couldnt update if u werent stock on both slots
Bildo41383 said:
So i shouldn't accept this update if rooted then?
Click to expand...
Click to collapse
Think it won't work anyway. It checks hashes of the
other side before applying, and if they don't match
it can't apply the update (brotli diff format, not a
full update.zip style update which just replaces
everything).
But what's the end state of the slots after an update?
A on 16, B on 19? Is 13/14 gone?
LLStarks said:
But what's the end state of the slots after an update?
A on 16, B on 19? Is 13/14 gone?
Click to expand...
Click to collapse
Yeah. My understanding is that 19 installs over 13. I'm
not one hindered percent sure though.
Partition hashes are going to be important. I think we still have our backups and whatever was documented in TEK's thread.
LLStarks said:
Partition hashes are going to be important. I think we still have our backups and whatever was documented in TEK's thread.
Click to expand...
Click to collapse
Note that these hashes may be deep dm-verity
hashes not plain sha256 and so on.
i know i can't get the update to actually update it fails i have tried going back to stock from my backed-up images locked the bootloader seems i cant get it to update
Yeah I'm having the same problem. All I did was root by flashing Magisk. I have since uninstalled the root/Magisk etc and I still get install problem at the very end of the OTA install . Thoughts?
I haven't updated to the new OTA yet, because I now have to restore from a backup so that it doesn't error again. I was curious how many partitions changed since January 2nd, 2020, and since rooting and using the phone for two weeks from the time of that 02 JAN backup the SHA-1 checksum of 43 different partitions have changed. I'll have to look at logs to where the error is from (i.e., because it happened even after I flashed back original unmodified boot_b), or I could just restore everything back.
adb sideload says it flashed it but phone stays the same...