DISCLAIMER:
Your device, your responsibility. I am happy to offer these tools but understand the risks before even considering.
Thank you.
OK, I've finally got a working OTA so I'll post this for now.
If we are able to improve on this without breaking something else I will edit this later.
IMPORTANT NOTES:
1) This has been tested and will flash TWRP to complete the OTA process.
2) At time of original post you will lose Loki exploit. I have provided suggestions in Post #2 how to get around that.
3) I had latest SuperSU and root prior to flashing this. It held without further action.
4) I highly recommend making a backup and storying a copy off your phone before starting in case TOT is required.
We had several issues in testing and that backup helped get back to a place to keep testing.
5) Do not wipe cache/dalvik between flashes of the OTA zip. You'll lose the stage counter and have to start over.
6) This ZIP will only work on a complete (odexed, bloated) stock ROM. You can be rooted but you cannot be debloated or deodexed.
If you made modifications to the stock ROM you will need to undo them. The most common, wifi tether, I've addressed in Post #2.
Link to current working OTA:
http://www.rwilco12.com/Files/Garwynn Projects/LS980/ZVAtoZVC/ZVAtoZVCTest7.zip
Instructions:
1. Download and store on phone. You do not need to store in /cache/fota.
2. Reboot to TWRP. Before flashing this ZIP you will need to turn off signature verification.
This is because I broke the signature when I modified the OTA.
You can certainly turn back on after this has been flashed.
3. Flash ZIP. This is phase 1.
It checks that everything is right for patching, flashes the modem and replaces kernel with TWRP.
When this finishes, reboot to system. This will load TWRP again but from boot partition.
4. Flash exact same ZIP again. This is phase 2 and very quick as it just flashes TWRP to recovery partition.
When this finishes, reboot back to recovery.
5. Flash exact same ZIP one more time to execute phase 3.
This is the actual patch process and will take some time.
It also undoes the aboot revert and drops the ZVC stock kernel in boot partition so TWRP is no longer there.
6. When last flash finishes, wipe cache/dalvik and reboot to system.
If the update fails on any step, stop and restore the recommended backup.
If that doesn't work use the ZV8 TOT and restore your phone.
(This is why I suggest backing everything up before update, better to be safe than sorry)
Thanks to autoprime, savoca and viperboy for bearing with on testing so far.
Thanks and hopefully we'll be able to improve on this in the coming days.
Supplement Post:
Pre-OTA Install Q/A:
1) What if I have Wifi Tether installed?
A: Use ZVAServices.zip in the post below, then flash this zip.
This rule applies for anything that fails on first part. If a patch check fails it means the file doesn't match ZVA stock and needs to be swapped out.
***WARNING***
The information below will show you how to get in and out of TWRP after OTA.
If you didn't use the OTA zip in the first post you must flash TWRP into recovery before anything else. Let's not brick any more, okay?
Please do not use these files before and understand the process before trying this.
This method of getting in and out of TWRP breaks download mode while aboot is reverted.
3 people have bricked and cannot flash a TOT already because the steps were not followed.
There are better solutions in the works now and should be posted soon.
2) What if I want to use TWRP?
A: Download this file:
http://www.rwilco12.com/Files/Garwynn Projects/LS980/ZV8_aboot.img
..and this file for later:
http://www.rwilco12.com/Files/Garwynn Projects/LS980/ZVAtoZVC/ZVCRadio_Full.zip
and from ADB shell or terminal, su then the following:
Code:
dd if=/sdcard/Download/ZV8_aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
(assumes file is in Download folder)
Note: I have assumed you already have TWRP flashed from OTA.
If you're doing this from anything else, flash TWRP in Flashify before anything else.
... then reboot into recovery.
3) Okay, but if I flash the aboot revert I break the stock kernel and download mode, right?
A: Yes, but that's why you grabbed that ZVCRadio_Full.zip.
Flash that in TWRP right before booting back to stock KitKat or to fix download mode.
4) Will there be an easier way for this?
A: Probably, but I don't like leaving loose ends. This is a workaround until a safer solution (in works by Savoca and others) are ready.
Count me in for testing. Im a trucker so battery life and gps a must. Ill test them heavily
I am currently on rooted ZV8 with twrp as the recovery, can I flash this directly or will I have to first update it to ZVA ?
Thanks garwynn for the extremely quick work. You are awesome!
Sent from the Moon using Tapatalk with my G2
Waiting for the full ROM. OTA seems a bit risky.
What is the md5 hash? I think i have a bad download. I got the following:
eb477d1d078b7bad0c7f0565d0717a31
Loki exploit
Mr: garwynn, what's the Loki exploi? And could we still keep rooting after installing this?Thanks.
yournamehere said:
What is the md5 hash? I think i have a bad download. I got the following:
eb477d1d078b7bad0c7f0565d0717a31
Click to expand...
Click to collapse
If you're trying sig check that will fail. I did not re-sign this. I'll generate md5 hash in a bit.
Sent from my LG-LS980 using Tapatalk
No sig check here it just keeps failing about half way. Also using twrp 6.2.3.3 blue
fail
yournamehere said:
No sig check here it just keeps failing about half way. Also using twrp 6.2.3.3 blue
Click to expand...
Click to collapse
as soon as I hit install it gives me error as well.
This isnt an april fools thing right?
Sent from my LG-D801 using Tapatalk
bishaarcc said:
as soon as I hit install it gives me error as well.
Click to expand...
Click to collapse
What does it show in the log? And definitely not joke.
Sent from my LG-LS980 using Tapatalk
Hmmmm never thought about that. Been on vaca last week. The size is right for the uodate as my phone has the full ota ready to install but im rooted and have wifi hotspot.
yournamehere said:
Hmmmm never thought about that. Been on vaca last week. The size is right for the uodate as my phone has the full ota ready to install but im rooted and have wifi hotspot.
Click to expand...
Click to collapse
Wifi tether is the problem. Give me 30 mins and I'll attach a zip to fix that.
Sent from my LG-LS980 using Tapatalk
Hey garwynn, do you think flashing this over stock rooted would work? Just an idea.
Edit: Stock rooted ZVA*
Sent from my LG-LS980 using XDA Premium 4 mobile app
jthein1989 said:
Hey garwynn, do you think flashing this over stock rooted would work? Just an idea.
Edit: Stock rooted ZVA*
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's what I did. But if you have the wifi tether hack installed that has to be undone first.
The attached file will do the trick. Flash this first in TWRP before trying the modified OTA.
No rush, but will we see a ZVC full, stock rooted ROM anytime soon? I am relying on the permanent sim unlock, so have to be extra careful.
Supplement Post:
1) What if I have Wifi Tether installed?
A: Use ZVAServices.zip in the post below, then flash this zip.
2) What if I want to use TWRP?
A: Download this file:
http://www.rwilco12.com/Files/Garwynn Projects/LS980/ZV8_aboot.img
..and this file for later:
http://www.rwilco12.com/Files/Garwynn Projects/LS980/ZVAtoZVC/ZVCRadio_Full.zip
and from ADB shell or terminal:
Code:
dd if=/sdcard/Download/ZV8_aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
(assumes file is in Download folder)
... then reboot into recovery.
3) Okay, but if I flash the aboot revert I break the stock kernel, right?
A: Yes, but that's why you grabbed that ZVCRadio_Full.zip.
Flash that in TWRP right before booting back to stock KitKat.
4) Will there be an easier way for this?
A: Probably, but I don't like leaving loose ends. So for now I offer a workaround.
Cleaned up instructions so there's a better understanding of what's going on.
Hopefully that resolves most questions. If not, feel free to keep asking and I'll be happy to answer.
Related
For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.
Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps
I'm having the exact same problem. I'm attaching what's appearing on TWRP.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app
^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.
newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx
mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?
I'd appreciate any help I can get guys.
So today, for the first time ever I rooted my android.
Found a simple video on how to and it worked. I then wanted to try a custom rom [Cyanogenmod 12?] On a video it was said to have a custom recovery rom first. Well, I tried Flashing TWRP. It asked to reboot. I pressed "yes Please". After that it restarted and was stuck at:
"Could not do normal boot" Odin mode (High speed)
I did a reset and now its just at:
"Odin mode(high speed)"
I saw someone on a random forum describing the same problem. He said he fixed it installing a recovery rom. Im guess from odin
since I cant do things on my phone. But I don't even know how to go about it. I just now I need a Tar. file
Please give me direction .__.
Try TWRP tar from Odin with phone in download mode; TWRP recovery tar linked below.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
If that doesn't work, you may have to Odin the stock tar.
I'm wondering if you misread the CF Auto root prompt to update the su binary? Update the su binary but don't choose the TWRP option even if you have TWRP. If you get recovery working, delete the cache and dakvik cache and reboot.
Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help
Sixgotfangs said:
Didn't work out...at least the way I did it. I'm still new to this. Id appreciate more broken down instructions if youre willing to help
Click to expand...
Click to collapse
What version of Odin do you have? Should be 3.07 with C.F. auto root. What have you flashed in Odin? Not familiar with the Odin message you gave; did anything change with the new recovery tar flash in Odin?
Won't boot or flash recovery? If so, you need to factory reset and Odin stock tar.
https://www.androidfilehost.com/?fid=95853297432265112
The instructions for stock tar are below but it's important to remember when flashing stock tars to power down first prior to going to download. You may not have any choice but power down to reach download mode; pull battery if you can't power down.
http://forum.xda-developers.com/showthread.php?p=56853325
If you can't factory reset, Odin the stock tar and see if it boots.
Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.
Sixgotfangs said:
Yes, I have the 3.07. Only thing ive done was Root. I tried the recovery rom from a mobile download. That's as far as I got. All the recovery files I get never end up showing in the pda file search. .tar or .md5 is what it calls for. If I CAN factory reset from where im at now how do I do so. If I can start ALL over with someone who is actually up to date and knows what theyre doing id feel more comfortable. right now nothings happened and my phone is still at "odin mode (hgh speed) --downloading.
Click to expand...
Click to collapse
ok, check my post above for updates.
Also, don't use the phone to download tar files unless you're using Flashify from Google Play. Download the tars on PC, move to folder that Odin resides in to find easily. You'll need to open the archive and drag the files there if zipped. The stock tar should be zipped but not sure about the recovery tar.
Cant believe I didn't see the last section on that post. Sorry about that. Anyway, I am downloading those files. Looks like its gonna take some time though. I'll go through each step you said and let you know.
Forgot to mention that you should close Odin after each flash attempt. You may have already noticed by now.
To get to CM after stock tar:
1) Root with CF Auto root, update su binary/reboot (you should wait no longer than 5 minutes for Knox prompt from supersu.
2) Odin TWRP recovery tar using same method as stock tar; Odin will only write over stock recovery on this step.
3) factory reset and flash CM in recovery. But also follow suggested instructions in the ROM you choose.
So far so good. The lil blue loading bar is filling.
got back to rooting. but I didn't do anything else. haven't even went to super user
Sixgotfangs said:
got back to rooting. but I didn't do anything else. haven't even went to super user
Click to expand...
Click to collapse
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.
samep said:
Booted? That's good news!
Can't remember if you have to open it or not. You should get a superuser update and possibly a su binary update but not so important going to another ROM. The su binary update is the one that I was suggesting not to use the TWRP option; I think the option is normal? Eventually, you should get the pop-up to disable Knox notifications; reboot if takes longer than 5 minutes.
Ready for TWRP? Use Odin. Flashify is something you could look into for updating TWRP, as needed. It's good for backing up recoveries and kernels, too. But watch those kernels for installed lib modules; Flashify won't restore those properly. Rely on flash zips for those; same applies for stock kernels, zip should include the stock modules.
It's late; you're probably done for the night. I'm out too.
Click to expand...
Click to collapse
Yeah, things are back to normal. Thanks again. As for the next steps, pretty lost. Im going to check the play store for an superuser update but the SU binary update....that's where I start getting lost. sorry for not being up to date with the terminology. But I am gonna check back on those links and look for the TWRP. and then use it like I did for those last files...{that's what Im getting from your messages} correct me if im straying from the path lol. catch ya later
I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.
samep said:
I'm confusing you a bit with the the su binary update and SuperSU update. To keep it simpler, that can wait until after you flash CM, if that's your goal. Those are prompts so don't be too concerned. Don't think you'll see Knox in CM.
So to keep it simple, you need TWRP to flash a custom ROM. I suggest the Odin tar in the link sent earlier.
After getting your custom ROM flashed in recovery, follow the prompts but if you see the su binary update prompt, don't choose the TWRP option. I think that caused your initial recovery issue but can't say for sure.
Click to expand...
Click to collapse
Hey there, Ok so. After messing around I ended up getting that TWRP package to work. I thought It was a SINGLE file, that's where I got stuck. but the whole ?.rar showed up in the pda selection In odin and I ran it. Worked fine. didn't see anything about updates ...still.
I restarted and went to recoverymode. Teamwin popped up like ive seen from other videos. Guessing im on the right track. So right now I don't need to be worrying about SuperSu or Rashr? or should I be dealing with those two apps? ALSO is Rom installer anything to pay attention to?
At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.
samep said:
At this point, you can look into a ROM installer or Flashify but I'd recommend just following the developer OP for whatever ROM you choose.
And yes, no need to worry with SuperSU or su binary update. Just follow the prompts when they appear after flashing ROM.
Click to expand...
Click to collapse
Thanks so much! The videos ive seen have been much simple-r for installing roms SO I may survive this whole experience after all...Yesterday was kind of a bad time to almost loose my phones functionality....being on the job hunt and all. need those phone calls Lol. So thanks again. Im hoping to try out cyanogenmod 12. I'll definitely shoot off a flare gun if I fail lol.
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
SUCCESS! Thanks again Sensei Lol
samep said:
No problem. Glad to be of some help. Godspeed on your journey and best of wishes for your career and rooted ventures!
Click to expand...
Click to collapse
eh...celebrated too early I guess. Ever run into camera connection errors?
Sixgotfangs said:
eh...celebrated too early I guess. Ever run into camera connection errors?
Click to expand...
Click to collapse
Is the error while still on stock or CM?
Now that you can wipe data, you can factory reset and either Odin the stock tar or flash CM.
If you prefer to take least intrusive approach, try going into recovery and delete cache and dalvik cache and reboot. If still not working, the factory reset. If still having camera issues, then decide if you want to go with stock tar in Odin again or CM a clean install; wipe user data first.
Personally, I'd wipe everything except my titanium backups and go back to Odin stock tar and make sure stock works fully before going to CM. In a situation like you were in, I would have powered down, flashed the stock tar in Odin and let it auto boot. Flash the custom recovery so I could wipe everything and then power down again and flash the stock tar in Odin just to get a clean start with root and custom ROM.
Edit- what is camera connection error? Oh, I see; lost camera. New thread. Maybe someone on CM can help you.
Thanks to everyone else for supplying the files. This is the stock 20G image, without a recovery.
Upgrades from 20E fine. Reflash SuperSu after install to regain root. Enjoy.
Download Here
alongenemylines said:
Thanks to everyone else for supplying the files. This is the stock 20G image, without a recovery.
Upgrades from 20E fine. Reflash SuperSu after install to regain root. Enjoy.
Download Here
Click to expand...
Click to collapse
How do you reflash without a recovery?
Sent from my LG-D851 using XDA Free mobile app
You still need a custom recovery, this zip just won't overwrite it.
If you flash with twrp, you'll still have twrp after the flash
That worked great. Thanks
Sent from my LG-D851 using XDA Free mobile app
alongenemylines said:
Thanks to everyone else for supplying the files. This is the stock 20G image, without a recovery.
Upgrades from 20E fine. Reflash SuperSu after install to regain root. Enjoy.
Download Here
Click to expand...
Click to collapse
Worked great, Lookout security says I'm not vulnerable. Here's a download link for SuperSu to flash after flashing 20G update https://www.androidfilehost.com/?fid=95857557620392009
Per the Zimperium app, the 20g update is still vulnerable...
sderaps said:
Unfortunately Stagefright CVE-2015-6602 is still vulnerable according to Zimperium Stagefright detector app.
Lookout Stagefright Detector will not detect the latest Version 2.0 vulnerabilities of Stagefright, and make it clear in there app description.
"This app does not support detection of Stagefright 2.0 vulnerabilities. "
Click to expand...
Click to collapse
Great
Lookin good on my Lg G3.
This is the checksum that I am getting. Anyone else can confirm this is correct?
4544093c57e9bf504b89e714523b4e9d
So does anyone have the latest 20g radio in a flashable zip? Also, this upload is VERY slow, could someone please please reup to a faster host?
alongenemylines said:
You still need a custom recovery, this zip just won't overwrite it.
If you flash with twrp, you'll still have twrp after the flash
Click to expand...
Click to collapse
Yeah... untrue for me, just deleted all my entire phone trying to get back into recovery. This update erased everything. :crying:
demoncamber said:
Yeah... untrue for me, just deleted all my entire phone trying to get back into recovery. This update erased everything. :crying:
Click to expand...
Click to collapse
Not sure what you did differently. This is just the stock update from zip from this thread (http://forum.xda-developers.com/tmobile-lg-g3/development/d85120g-stock-update-zip-d85120e-t3218287), with recovery.img removed, and the updater script modified to NOT flash the recovery.
Only way I can think of that you could have deleted everything on your phone is if you did a wipe first.
alongenemylines said:
Not sure what you did differently. This is just the stock update from zip from this thread (http://forum.xda-developers.com/tmobile-lg-g3/development/d85120g-stock-update-zip-d85120e-t3218287), with recovery.img removed, and the updater script modified to NOT flash the recovery.
Only way I can think of that you could have deleted everything on your phone is if you did a wipe first.
Click to expand...
Click to collapse
No idea here as well, did not wipe before. I flash things all the time, just the normal load zip, flash, reboot was done. Then it loaded up, saw root was lost, went to boot back into recovery, erased everything.
demoncamber said:
So does anyone have the latest 20g radio in a flashable zip? Also, this upload is VERY slow, could someone please please reup to a faster host?
Click to expand...
Click to collapse
I uploaded a modem zip for 20G
Sent from my LG-D851 using Tapatalk
---------- Post added at 04:33 AM ---------- Previous post was at 04:31 AM ----------
Link to my Google drive for all. D851 Modems
https://drive.google.com/folderview?id=0BxVKW5ov-PmLbF9LR2pvcEljemc#
Sent from my LG-D851 using Tapatalk
I'm still on 10m. Can I flash this without any problems? And what are the improvements?
Dream Reality Syndrome said:
I'm still on 10m. Can I flash this without any problems? And what are the improvements?
Click to expand...
Click to collapse
the improvements is just the stagefright bug patch
oh no i think im up a creek
so i flashed the rom and SU then as im rebooting to DL mode to reflash my recovery.img the effing cat jumps into my hands and knocks the phone out of my hands and out popped the battery. now when i hold vol up and plug usb in i get the quick blue DL mode screen as usual but no firmware screen to follow, insted a black screen with 6 tiny white lines of text in the top left corner that read as follows
[600] fastboot mode started
[690] --- reset ---
[700] --- portcharge ---
[860] --- reset ---
[860] --- portcharge ---
[1070] fastboot: processing commands
the rom still boots if i battery out and restart also have done multiple factory resets
any ideas in fixing this would be greatly appreciated
Looks like its booting to fastboot mode. You can flash proper recovery using a PC and the adb\fastboot package. Been too long for me to remember details but google will get you the answer.
Sent from my SHIELD Tablet using Tapatalk
Works like a charm for me... It does what is said...
Enviado desde mi LG-D851 mediante Tapatalk
So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.
imsuckk said:
So usually I don't have any issues with rooting my phone and all. For some unknown reason i just cant seem to root my Sprint Note 4 phone!
Information:
Phone: Sprint Note 4
Model: SM-N910P
Android Version: 6.0.1
Software Version: N910PVPU4DPE1
Build Number: MMB29M.N910PVPU4DPE1
TWRP Version: twrp-3.0.2-0-tbltespr (Which i successfully managed to install)
I used CF-Auto-Root-trltespr-trltespr-smn910p.tar
I did notice that when i flash my auto-root it says "Finding boot image.....Boot image not found, Aborting" under the Boot image patch.
Any ideas on what it means? I'm at a total loss so anything would help me at this point.
Click to expand...
Click to collapse
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!
aaron74 said:
CF-Auto Root was made to flash with odin, to keep your stock recovery in place. I don't think it works with MM roms.
Just download and flash Supersu from within TWRP. Here's the thread for SuperSu Here.
I always use the Latest version 2.74 here. But you can use the Stable version 2.65 here. They're both in the thread above.
Enjoy!
Click to expand...
Click to collapse
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.
aaron74 said:
No you don't have to wait. You can root. Cf-auto was made by the same person as supersu. It was just intended to root your phone with odin in one step. What it does is temporary installs a custom recovery that roots your phone, then puts back a stock recovery (At least something like that). But it isn't up to date to work with Marshmallow. So you just have to do it manually. I thought you said you already have Twrp recovery but I'll show you all steps. I'm assuming you have odin and know how to use it.
1. Download and install Twrp from this thread. Follow links in thread to download and install with Odin here.
2. Once you get TWRP installed. I suggest you boot into it and make a Full Backup of your phone.
3. Download onto your phone SuperSu 2.74 here.
5. Boot into Twrp and install the supersu file you downloaded.
You're now rooted.
Click to expand...
Click to collapse
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Oh. That explains it. TWRP ISN'T installed. Let me explain.
1 Download Twrp here.
2 Odin Twrp to phone. Make sure to uncheck auto reboot in odin first. After odin completes it'll say something like all operations done. Just make sure odin is done. It don't take long. Then you have to unplug usb from phone and pull out battery for 10 sec. Put battery back in and hold Vol up + Home + Power button until Twrp boots.
3 now twrp is installed and you can install root.
Also backup your phone.
Sorry I'm busy right now and can't post a good post with pics. If that all makes sense then you should be good to go. If you don't understand what I mean I can message you later with some screenshots
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
tar.img is what you should flash in Odin for TWRP. If you are already on TWRP recovery, you can use the .img file to update within TWRP. TWRP makes both these files in flash form; one for Odin flash, the other for TWRP recovery flash. No need to convert. See link below for the Odin flashable TWRP.
Your kernel must already be patched or custom. (Possibly the reason it can't be patched).
When you boot your ROM, check your kernel and bootloader using Galaxy Tools or PhoneInfo for Samsung. If they don't match your last known update, it's possible you've not successfully updated because your reactivation lock is enabled and you didn't notice you failed to update. Nonetheless, check your reactivation lock by going into Settings/Security and uncheck the option.
If failures persist, flash the stock tar in Odin and make sure it flashes.
For the record, latest update for CF AutoRoot for Note 4 does in fact work. But note, you should flash that in Odin over full stock only. Don't try to flash it if you already flashed TWRP. It's intended to back up stock recovery and stock kernel to restore if you full un-root within the SuperSU application. It's been reportedly to be an unknown or dysfunctional but I can confirm it worked for me back on PB5 leaked MM tar. I used the latest update for CF AutoRoot for Note 4 then. Can't imagine anything broke since then but when I realized it was just systemless root, I lost interest. But hey, it has its purpose for those not interested in TWRP recovery and want yo test if OTA is possible with the limited modification. I've yet to test the theory that it may allow OTA update if system ro partition is left untouched. I like sound mods too much to leave system fully stock.
I can recommend an easier way though (if uninterested in systemless root): you don't have to pre-root if flashing a custom ROM. Once you determine your issue or just Odin flash and confirm the stock PE2 tar. Flash the TWRP tar.img file and then factory reset and flash Freeza's Note 4our beta 3.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
https://androidfilehost.com/?fid=24591023225176402
Note: Thank freeza if the clean flash suggested goes as expected. His thread is in the development forum for Sprint Note 4.
Sent from my SM-N910P using Tapatalk
imsuckk said:
Same issue :/
My Steps:
1. I use a script to convert TWRP IMG file to TAR then flash to my phone. (I used twrp-2.8.7.0-trltespr.img becuause TWRP 3.0.2.0 doesn't flash onto my phone for some reason.)
2. I go onto TWRP and install SuperSu 2.74. (While flashing i see the "Boot Patch" error")
3. Boot up phone and no SU is installed so i install SuperSU from playstore and open up the app. No SU binary installed.
4. After all goes wrong I try latest CF-Root to see if it works. No luck.
5. Try to get into TWRP and receive "Android installing recovery" or something similar. Stock android recovery is installed again.
6. Repeat.
Click to expand...
Click to collapse
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
aaron74 said:
AmmO0702 said:
looking for the best way to root my sprint note 4. can you help me
Click to expand...
Click to collapse
First off some things you should do before ever flashing or rooting your phone.
1. Make sure ReActivation Lock is OFF. (Its in Settings>Security>Reactivation Lock = make sure its unchecked)
2. Turn on Developer options. (Goto Settings>About device and tap Build Number 4 to 5 times; then develepers options will be in settings menu, goto that and turn on USB Debugging)
3. You'll need Official Samsung Drivers HERE! Install this to your PC!
4. Always Backup Phone!!
Now your set to Flash and Root.
IM gonna assume your on a Stock ROM. To root your gonna need to use Odin to flash TWRP, then once thats done we'll root from there.
You'll need these files :
Odin3.11 from Here. , Thanks to @LMMT, Thank him here. You'll install this to your Windows PC.
TWRP 3.0.2.0 from Here. This file is only for the Sprint Note4 SM-N910P, So that better be the phone you have!! Download and save to PC! You can Thank @bigbiff at this Thread.
Lastly you need SuperSU Here! Thanks to @Chainfire at this Thread! Download and save to your Phones SD card or Internal memory.
Now you have the files. Make sure you dont have samsung Kies running while installing or flashing your phone. Actually Dont have any other programs running when Flashing your phone.
1st - Install Samsung Drivers to your PC.
2nd - Install Odin to your PC.
3rd - Copy SuperSU zip file to your phone.
Now unplug your phone and turn it off. And open Odin Program as Admin. Now on your phone hold down the Vol down button + Home button + Power button at same time until a screen shows a Warning.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then you'll press Volume up to continue to Download Mode.
Once in Download mode plug into usb cord to PC. Your pc should install some drivers then Odin will show your device as connected. Goto options tab in Odin and make sure all the boxes are unchecked except F. Reset Time.
Then click the log tab so we can watch the progress were gonna make. Then click the AP button and load the Twrp file you downloaded into that. If everything looks like my pic then click start. Let it do what it does, dont touch anything until it done. Once down unplug phone and take out battery for 5 seconds.
Put battery back in and press Vol up + Home + Power until phone boots into Twrp Recovery.
Once in Recovery I sugessst to do a Full Backup.
Then you can Hit Install button in Twrp and find the Super SU file you saved on phone and Install and reboot when it says. Your ROOTED!!
Hope this isnt confusing. It really isnt that hard. But Id be able to show you better in person than in writing.
Click to expand...
Click to collapse
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Hooked my phone up to Smart Watch and noticed I had a software update. Gonna update my phone then check back in here and try it out! Thanks!
Sent from my SM-N910P using Tapatalk
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk
imsuckk said:
So basically there is no CF-Root that works for MM and i just have to play the waiting game?
Wouldn't THIS CF-Root work for my ROM? Sorry for all the questions lol. Never dealt with these issues before.
Click to expand...
Click to collapse
Really do not understand why Cf-autoroot do not work for you. I rooted my device just yesterday with Odin and Cf-autoroot works just fine
Sent from my SM-N910P using XDA-Developers mobile app
aaron74 said:
Ok now I had a little time. I found an old message I made for someone else with a little better detail. I forwarded it to you. Check your private messages. Plus I'm posting it here for anyone else that it may help.
Sorry my pics won't send. Also I see @samep mentioned that system less root won't stick on an altered kernel which I didn't know. Thanks.
Click to expand...
Click to collapse
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.
samep said:
I meant to use CF AutoRoot, one should start with stock kernel and recovery.
There has been some inexplicable loss of systemless root. I don't claim to know what is causing that but prefer the system based root in freeza's ROM.
Your help has been good. I was posting as you were. Otherwise, I may not have posted that earlier.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
imsuckk said:
Man, I am still not rooted when I boot the phone up. Still am getting the same Boot Patch error and everything.
Click to expand...
Click to collapse
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?
aaron74 said:
Oh ok, I must have read too fast. My bad.
I often wondered if anyone had lost root cause Yeah I lost root app a couple times with systemless root. Especially Always after I install idones unlock app I lose it. Have to reflash stock kernel and root.
I downloaded @freeza note four Rom last week. Haven't had time to install and play with it yet. I didn't know it had system root. It looks promising. I know he has done a lot for our device. As has a bunch of devs on this site. I know Ive seen your name all through here too. Thanks for all your help.
I don't claim to be a Dev but I like to hack, mod, and figure stuff out. And I've learned most the stuff I know here on XDA. So when I see someone I can help I try to give back to the community.
---------- Post added at 07:39 PM ---------- Previous post was at 07:19 PM ----------
Ok lets get to the bottom of this. Im gonna walk you through getting a fresh stock boot image and then rooting it.
First do you mean when you start your phone it says that?
Or when you go to flash cf autoroot it shows that?
And Can you boot into TWRP recovery?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
When I flash SuperSU it says that, and yes i am able to get into TWRP still.
imsuckk said:
When I flash SuperSU it says that, and yes i am able to get into TWRP still.
Click to expand...
Click to collapse
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?
aaron74 said:
ok AWEsome. Where gonna see if a copy of your stock kernal is on your phone.
1. Boot into Recovery, Click Advanced, and then File Manager
you should now see the root of your .file system. Click on the Data folder and scroll down do you see a file that start with stock_boot_?
Click to expand...
Click to collapse
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)
imsuckk said:
I do not see that. It could be that I just did a fresh update to PE2 and have a totally fresh ROM (with TWRP installed)
Click to expand...
Click to collapse
Ok Im gonna PM you so not to fill this thread with bunch of mess
aaron74 said:
Ok Im gonna PM you so not to fill this thread with bunch of mess
Click to expand...
Click to collapse
Alright thanks man!
Sent from my SM-N910P using Tapatalk
imsuckk said:
Alright thanks man!
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Besides the stuff we disgust. If that dont work. You could install a pre rooted rom. Or if you really want to figure out why it wasnt working.
I would start with clean slate and download the PE2 tar. Wipe phone and flash it. Reinstall Twrp and Supersu.
Hope it works! Have to get off here for awhile!!
Let me know if you got it!
Will the same method work on pj1 ?
LG V30 T-Mobile H932 20r ROM
For U.S. T-mobile H932 ONLY. Do NOT install this on any other V30/V30+/V30S except U.S. T-mobile H932. You will brick your phone.
DISCLAIMER : I do not hold responsiblity for any of the following but not limited to : Bricks due to not reading, nuclear war, cat dying. I will not be held responsible for any damage of any kind due to the result of this zip. It is held under your own risk. This does not mean that i wont help in any way shape or form to recover from anything that may happen at the result of flashing this zip. PLEASE FLASH RESPONSIBLY! PS. This zip has NOT been tested by me!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. It contains almost the complete 20r firmware, but the partition table rewriting part and recovery image is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition. This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited / advanced it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Added DTS build prop
Added all lockscreen weather animations build prop
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
H93220r.zip [Download]
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20r firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20r zip, then Magisk zip when you need root, then reboot to System = you're DONE
P.S.: could be, that you first need to boot up your fresh install and set it up before you can flash magisk.
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Rom Version
Android Version: 8.0 Oreo
Android security patch level: 2019-1-1
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
#RESERVED
Please to anyone who had issues with the zip.....
We have a fix!
Flash this zip
https://www.androidfilehost.com/?fid=1395089523397908552
Then flash a rom from your SD CARD
ONLY FLASH THIS OF YOU HAD A BRICK FROM 20R!!
Zip is live! Enjoy!
your zip name is wrong.. should be h93220r* ( it doesnt matter but i was confused at first)
also, i flashed it and nothing happened. my system is still the same as i was before (20p)
and in the script, i think it says 'model=VS996' or something. since it just words, it may not matter.
but maybe you used the wrong script for h932
In any case, the zip did nothing for me. flashing only took about 10 secs in total, and flashing system barely took a second.
So seems theres an issue with the zip. Maybe upload didn't quite finish as I did it while at work via rdp to my pc at home. Will look into it when I get off work
JohnFawkes said:
So seems theres an issue with the zip. Maybe upload didn't quite finish as I did it while at work via rdp to my pc at home. Will look into it when I get off work
Click to expand...
Click to collapse
Did you remove the file?
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Did you remove the file?
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
JohnFawkes said:
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
Click to expand...
Click to collapse
Ahh ok, thought I was missing something.
Sent from my LG-H932 using XDA Labs
JohnFawkes said:
For now yes. Everyone was having issues. I'm on my way home from work right now so it'll be back online in probably an hour
Click to expand...
Click to collapse
looking forward to the fix.
I figured people might want these files.
Root-System-Media
Uploading new zip now! figured out all issues
JohnFawkes said:
Uploading new zip now! figured out all issues
Click to expand...
Click to collapse
Awesome thank you!
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
Awesome thank you!
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
no problem. should be live in about 15 minutes
zip is live!
Awesome. Woke up this morning to the system update notification. Glad there are still T-Mobile users around here that works to get this stuff out. Downloading now. Will report back after I flash it.
---------- Post added at 07:43 AM ---------- Previous post was at 07:19 AM ----------
BROKEN1981 said:
I figured people might want these files.
Root-System-Media
Click to expand...
Click to collapse
Are these new in this update?
JohnFawkes said:
zip is live!
Click to expand...
Click to collapse
At the end of the flash it looks like it flashed fine but then it tells me it failed to mount everything. When I go to reboot into the system it tells me there is no OS. I was just going to flash the 20p zip I had but then it restarted and now I can't get into TWRP again. Now it just restarts into fastboot mode
UPDATE: I was able to get back into TWRP by going through the factory reset option (Volume down + Power, etc.) I'm now flashing the 20p zip I have.
UPDATE 2: Didn't work. Got into a bootloop. Restoring an old Lineage backup I have. Should have made a backup of my current state before flashing but I wasn't thinking
UPDATE 3: That didn't work either. Everything I flash it tells me failed to mount '/persist-lg' and just boot loops. I guess the next thing to do is try and use LGUP to restore
Same here as above. Doesnt mount system persist cache.
sunmybun said:
Same here as above. Doesnt mount system persist cache.
Click to expand...
Click to collapse
Flashing anything else doesn't fix it either. My phone is chillin' in recovery mode until I can figure it out
im working on fix guys. zip is removed for now. no clue why this is happening. but a fix is being worked on
JohnFawkes said:
im working on fix guys. zip is removed for now. no clue why this is happening. but a fix is being worked on
Click to expand...
Click to collapse
Thanks. Searching around, I see there have been people having issues like this before with other devices. Something to do with the persist.img. Did the last zip include one? Also, I hope whatever it is can be fixed with a new zip. I don't know why restoring a backup or flashing an old full stock zip wouldn't fix anything.
This is basically what I'm getting
http://en.miui.com/thread-467490-1-1.html