Bit of a silly question - I'm still on an old version of Jasmine (4.0, KitKat), and I'm getting the itch to move to xdabbeb's v47a. While I believe I'm fine to simply update my TWRP and go from there with the standard wipe/bootstack/flash, I want to ensure I have all my ducks in a row in case of emergency and I need to drop back to 10B.
I'm aware of the relevant threads that explain the .tot method, but looking through my archives I've discovered that I did a full 10B TWRP nandroid backup (system, boot, data, and efs) immediately after first rooting/installing TWRP a couple of years ago.
So the question is, how "clean" would my restore be going to this backup, vs. going through the full .tot method? Obviously, this wouldn't be true stock as I assume it would retain root and recovery but for the moment I'm not aiming for pristine (ie., warranty return), just clean enough to not affect a new ROM install.
daagar said:
Bit of a silly question - I'm still on an old version of Jasmine (4.0, KitKat), and I'm getting the itch to move to xdabbeb's v47a. While I believe I'm fine to simply update my TWRP and go from there with the standard wipe/bootstack/flash, I want to ensure I have all my ducks in a row in case of emergency and I need to drop back to 10B.
I'm aware of the relevant threads that explain the .tot method, but looking through my archives I've discovered that I did a full 10B TWRP nandroid backup (system, boot, data, and efs) immediately after first rooting/installing TWRP a couple of years ago.
So the question is, how "clean" would my restore be going to this backup, vs. going through the full .tot method? Obviously, this wouldn't be true stock as I assume it would retain root and recovery but for the moment I'm not aiming for pristine (ie., warranty return), just clean enough to not affect a new ROM install.
Click to expand...
Click to collapse
Restoring the TWRP backup shouldn't be any cleaner than just updating TWRP, wiping Cache, Dalvik, and Data and flashing @xdabbeb 's 47A firmware ROM and appropriate Bootstack (35B).
Nothing is as clean as actually flashing the TOT. KDZs and TWRP backups don't contain all the partitions that TOTs do. Root is easy to be regained on 10B worth the Stump app and then use TWRP Manager from the Play Store to put TWRP on, if you decide to go that route. Root is more complicated after 10B, and putting TWRP on is more complicated after 12B.
---------- Post added at 11:10 PM ---------- Previous post was at 10:40 PM ----------
In the future, please post questions in the Q&A section. I'll ask a moderator to move this thread.
Thanks, sir. I wasn't sure just how "complete" a TWRP backup was, and that answers it.
Updating TWRP via TWRP Manager was a piece of cake, now I merely have to backup and/or clean up two years worth of apps and crap so I can do this! I truly had no intention of bothering to upgrade again, but your posts and help all over XDA LG G3-land have eased things considerably.
EDIT: Doh, and apologies for misplacing the thread Dangit.
Related
A friend of mibe wanted me to update my phone so i could have advanced calling. But its an update and do notwont to risk losing root and recovery or worst face brick. I would love to have this update so im hoping is there a work around. Is there a way to root the phone again if it does wipe it out. Is there a way to download it and have my custom recovery install it. Please and thank you
If you're already on 12b, you already have advanced calling. Otherwise, go here
http://forum.xda-developers.com/showthread.php?p=57360121
It's like the second sticky down in the general section. Read, read, and read again before attempting to update your G3. Although it's pretty easy to fix if you mess something up, it's also pretty easy to softbrick.
Sent from my VS985 4G using Tapatalk 2
Johneedoe said:
If you're already on 12b, you already have advanced calling. Otherwise, go here
http://forum.xda-developers.com/showthread.php?p=57360121
It's like the second sticky down in the general section. Read, read, and read again before attempting to update your G3. Although it's pretty easy to fix if you mess something up, it's also pretty easy to softbrick.
Sent from my VS985 4G using Tapatalk 2
Click to expand...
Click to collapse
I hope i did the quote right. I got more info to what i have this is whati have
Hope u see the pic
LASERWOLF452 said:
I hope i did the quote right. I got more info to what i have this is whati have
Hope u see the pic
Click to expand...
Click to collapse
The number at the end of the build number is 10B. You need to be on 12B or higher in order to use Advanced Calling. Also would have to enable it on your Verizon account. MIght be under "HD Calling".
roirraW "edor" ehT said:
The number at the end of the build number is 10B. You need to be on 12B or higher in order to use Advanced Calling. Also would have to enable it on your Verizon account. MIght be under "HD Calling".
Click to expand...
Click to collapse
Thanks but one thing. I hate to sound like a noob but doing this ive never done before. Is there a guide that can walk me threw it to get to 12b
LASERWOLF452 said:
Thanks but one thing. I hate to sound like a noob but doing this ive never done before. Is there a guide that can walk me threw it to get to 12b
Click to expand...
Click to collapse
If you're wanting to be rooted and update to 12B...
1. Root using Stump apk brute force method. Reboot.
2. Install SuperSU from Play Store, reboot, launch SuperSU, update binary, reboot again.
3. Install TWRP Manager from the Play Store, launch it and grant it root permissions.
4. Use TWRP Manager's option in the upper right corner to download and install the latest TWRP custom recovery for the VS985. It's already bump'd, I've verified.
5. Use the link @Johneedoe provided, download the 12B boot, modem and system.img files. Extract system.img from the system.zip.
6. There's a link in that first post, after all the download links to @autoprime 's Flash2 method. Use that through TWRP with the 12B img files you downloaded.
Sent from my VK810 4G
You can just take the OTA to 11c and then 12b. You won't lose root on the way.
siriusgamer said:
You can just take the OTA to 11c and then 12b. You won't lose root on the way.
Click to expand...
Click to collapse
he has custom recovery installed. do not take ota's or it will not boot until you flush the fota folder, and the ota wont install.
bweN diorD said:
he has custom recovery installed. do not take ota's or it will not boot until you flush the fota folder, and the ota wont install.
Click to expand...
Click to collapse
Thanks for letting them know. I was already told not to update with custom recovery by a friend. I have not done the update a friend is going to help me threw it cause i dont wont to take a chance and mess it up if i cone access sonthing i dont u derstand. Im more in learning stages of rooting. And new with ota updates as im new to that lol
update failed. need help to 12b
Me and my friend was working on my phone but we had an issue.
I'm running twrp latest version, and we followed this post as is
http://forum.xda-developers.com/showpost.php?p=56100153&postcount=1
And I,ended up with an error . all,passes and succeeds but I get
E: Unable to mount ' /system'
just wanted to put this but i found my error, i had no computer at the time and was using on my cellphone to extract the files, i got my laptop fixed and was able to get 12b installed thanks for the help
bweN diorD said:
he has custom recovery installed. do not take ota's or it will not boot until you flush the fota folder, and the ota wont install.
Click to expand...
Click to collapse
so.. i've made this mistake. where can i find info on flushing the fota folder? and the steps to take after that..? plz and thank you in advance
killerskincanoe said:
so.. i've made this mistake. where can i find info on flushing the fota folder? and the steps to take after that..? plz and thank you in advance
Click to expand...
Click to collapse
I'm not in a position to grab the link right now. Check my Reference post in general, or look for the original post by autoprime. It's a twrp flashable zip.
Sent from my N6
Ok, ive bricked and started fresh all over again, the problems with the file rhat im suppose to rename and take out the number, well when i down loaded that file it reads system 12B rar. If i change the name i brick, if i leave it as is i get error on system dwnload??, 1st two times was an error, 3rd time i changed the name and bricked it. Took me 3 hrs to get back to 19b,little help here!!!
Sent from my VS985 4G using XDA-Developers mobile app
jlb1959.01 said:
Ok, ive bricked and started fresh all over again, the problems with the file rhat im suppose to rename and take out the number, well when i down loaded that file it reads system 12B rar. If i change the name i brick, if i leave it as is i get error on system dwnload??, 1st two times was an error, 3rd time i changed the name and bricked it. Took me 3 hrs to get back to 19b,little help here!!!
Click to expand...
Click to collapse
I'm not positive what you want your end result to be, but if you want root and TWRP on any version of the stock ROM, the easiest method is to use the built in LG Backup to backup your user apps, user data and limited system data to your MicroSD card, move anything else you want to keep from your internal storage, flash the 10B TOT using the .DLL that's extracted from the 35B KDZ, root using the Stump app on XDA, put TWRP on with TWRP Manager from the Play Store, reboot to TWRP, wipe Cache, Dalvik/ART and Data, flash whatever ROM you want and appropriate Bootstack. Bootstacks are in @xdabbeb 's VS985 v2.0 ROM thread in the Development (non-original) section. 12B Bootstack for KitKat, 24B for Lollipop 5.0.x and 35B for Lollipop 5.1.x and Marshmallow 6.0.
If you flashed a stock-based ROM, then you can use the built-in LG Backup to restore your backup from previously. Not much, if any (depending on what version of the stock ROM you come from, and what you flash) system data will be restored.
Sorry road warrior, you helped me a ton, don't know if you remember me, I had 5.1 but did an Ota to 6.0, I wanted to start fresh do I followed you and laser wolf, I downgraded to 10b,now when trying to follow laser wolf a
---------- Post added at 05:08 PM ---------- Previous post was at 05:02 PM ----------
Sorry got cut off on the above, so when I downloaded the files and made flash folder for the files, on flash it came up error on system imaging, that's file read system 12B rar now when I changed the name by removing the number, as directed, I bricked on flashing. So it has to do with that file.??im at a loss. I thank you a ton for the downgrade to 10b tho.
---------- Post added at 05:09 PM ---------- Previous post was at 05:08 PM ----------
And yes I'm rooted etc as direct with your downgrade.
---------- Post added at 05:13 PM ---------- Previous post was at 05:09 PM ----------
I have since unbridled by returning to stock, which is 10b again. Just don't want to mess up again, so trying to figure out why that system file(System12B rar) cannot or will not work. If left alone, that files flashes as an error, if I change the name, by taking out the number(12B) it bricks.
Correct spell is killing me, after I bricked trying to flash I dug around xda and managed to replace to 10b exactly like laser wolf has in this post(his picture matches my phone exactly), my problem now is not the zipped files, the other files are the problem, there all suppose to go into a file named flash, however on the download the system file had system12b. rar... According to the direction it should read system12b I'm, and directions say rename to system.img,,thats what I changed the name of the file to and it bricked, if I leave it as downloaded it flashes error on system img, I don't want to trial and error as I'm new to flashing files etc. Was wandering if anyone else downloads those files and gets a file named system12b. rar instead of system12b. img , and if so what am I suppose to do. Again sorry roadway warrior for not posting in the proper place, however this was where people were trying to go from 10b to 12b...ang help is appreciated!!!!
I didn't read all that. Sorry. I guess I don't understand what the purpose of a 12B rar is. If you want to be on 12B, root and put TWRP on 10B, then wipe and flash a 12B-based ROM like JasmineROM I think v2 or v3, or SkyDragon - probably the same, v2 or so.
By your description it sounds like this is some more difficult method.
Ok, thanks mate, been driving me crazy because that particular file means changing the name etc, but I will try your way.... Greatly appreciated my friend... Thanx
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
Dang it, where will I find those rooms?, under your work??
Update, [email protected] guided thru the process step by step, much thanks to [email protected] and a special thanks to roadwarrior, used your method and guidance from laserwolf452, thanks guys I'm now on 12b and rooted
Hi there, I'm not entirely sure if this is the right place to post this.. I'm kind of a noob at this as I have just joined the XDA community.
I have a rooted Verizon LG G3 VS985 running android 5.1.1. Software version VS98535B
I have been recently trying new root apps, but I have noticed that some require busybox. I downloaded the installer, but was hesitant to install because of hearing rumors of soft-bricks and bootloops after installing BusyBox. I am curious if anyone has installed busybox with a similar phone and if they installed BusyBox successfully. I don't know if this a dumb question or not. I am just a bit hesitant to install busybox because my LG G3 is my daily driver, and if it gets screwed up, I'm screwed.
Please help me....
P.S. Sorry again if this is the wrong place to post this thread...
I never had a problem installing it on any device. That said, it's always wise to make a TWRP backup to the MicroSD card before any major changes especially root related.
roirraW "edor" ehT said:
I never had a problem installing it on any device. That said, it's always wise to make a TWRP backup to the MicroSD card before any major changes especially root related.
Click to expand...
Click to collapse
The thing is, I don't want to risk bricking by installing TWRP
zebereeh7 said:
The thing is, I don't want to risk bricking by installing TWRP
Click to expand...
Click to collapse
I don't know what to tell you then.
When we root, and what we do with our phones after we root, is not according to how the manufacturer meant for us to use our devices. There's always some chance of something not going according to plan. The chance of that is usually somewhat slim when following (reliable) directions exactly, but there's always going to be a chance. You can brick your device without even rooting. No one can give you any 100% assurances, although some may try, but nothing is ever 100%, you know what I mean?
No matter what you're likely to do, there's hardly any chance that you won't be able to recover your phone. If you have your Android O/S and apps configured just right for you, at least use the built-in LG Backup in Settings/Backup. Backup to MicroSD and copy anything you don't want to lose from your internal storage to your MicroSD card. If you ever have to Factory Reset or reflash the completely stock unrooted ROM in a way that'll cause your internal storage to be wiped, then you'll be happy you made that backup.
There are both unofficial and official tools to recover your phone to complete stock just like from the factory.
If you weren't at least open to some kind of possibility of bricking, you probably wouldn't have rooted to begin with. Or at least, I should say, if you're going to root you have to be prepared for the possibility of things happening in a way you didn't mean to.
Using a custom recovery like TWRP is the easiest way to get your phone back to a known good state while keeping root.
I'm not trying to convince you to put TWRP on your device, but I will always recommend making a backup in TWRP before making major changes. If you don't and things go wrong enough, then you have to accept the fact that you'll effectively do the work you would've had to do to put TWRP on in the first place, to recover your phone to a usable state.
Sorry if this sounds like a rant, I don't intend it that way.
roirraW "edor" ehT said:
I don't know what to tell you then.
When we root, and what we do with our phones after we root, is not according to how the manufacturer meant for us to use our devices. There's always some chance of something not going according to plan. The chance of that is usually somewhat slim when following (reliable) directions exactly, but there's always going to be a chance. You can brick your device without even rooting. No one can give you any 100% assurances, although some may try, but nothing is ever 100%, you know what I mean?
No matter what you're likely to do, there's hardly any chance that you won't be able to recover your phone. If you have your Android O/S and apps configured just right for you, at least use the built-in LG Backup in Settings/Backup. Backup to MicroSD and copy anything you don't want to lose from your internal storage to your MicroSD card. If you ever have to Factory Reset or reflash the completely stock unrooted ROM in a way that'll cause your internal storage to be wiped, then you'll be happy you made that backup.
There are both unofficial and official tools to recover your phone to complete stock just like from the factory.
If you weren't at least open to some kind of possibility of bricking, you probably wouldn't have rooted to begin with. Or at least, I should say, if you're going to root you have to be prepared for the possibility of things happening in a way you didn't mean to.
Using a custom recovery like TWRP is the easiest way to get your phone back to a known good state while keeping root.
I'm not trying to convince you to put TWRP on your device, but I will always recommend making a backup in TWRP before making major changes. If you don't and things go wrong enough, then you have to accept the fact that you'll effectively do the work you would've had to do to put TWRP on in the first place, to recover your phone to a usable state.
Sorry if this sounds like a rant, I don't intend it that way.
Click to expand...
Click to collapse
Thank you. It didn't sound like a rant at all, more like an honest answer. Now, my question is.. is TWRP or CWM even compatible with my phone? I've heard rumors of TWRP not working on 35B
zebereeh7 said:
Thank you. It didn't sound like a rant at all, more like an honest answer. Now, my question is.. is TWRP or CWM even compatible with my phone? I've heard rumors of TWRP not working on 35B
Click to expand...
Click to collapse
You're welcome!
Yes. As far as I know, TWRP is the only one actively maintained for the VS985. The way I recommend installing it is downgrading to 10B temporarily. Since you're on 35B you'll likely have to use the TOT method with the new .DLL gotten from the 35B KDZ, which you can find toward the bottom of a post in the General section by @hokiealumnus.
There are instructions multiple places, one is here http://lgflashtool.net/index.php/tot-method/, with the exception of using the new .DLL I mentioned instead.
After downgrading to 10B, which will wipe all user data and your internal storage, root with the Stump app, then use TWRP Manager from the Play Store to install the latest TWRP. Both rooting and putting TWRP get more complicated after 10B.
There may be other ways of getting TWRP working on 35B but this is the way I recommend and in my opinion is most foolproof and easiest.
If you do this just remember that you can use the built in LG Backup on what you have now, then you can restore it when you're back on 35B, or if you choose to flash the 46A ROM.
I'm sure it's possible to put TWRP directly on 35B by flashing the right partitions - the 12B aboot.img (bootloader) and laf.img (Download mode). If you would rather use a terminal emulator with superuser permissions and use the commands and partitions found in @bweN diorD 's stickied thread in the General section, you can go about it that way instead. I copy/paste the commands from a text file. If you type them manually and you type something wrong there's a greater chance something will be flashed wrong.
The way people temporarily brick their device on 35B trying to put TWRP on is using Flashify or TWRP Manager or terminal commands without having downgraded the bootloader and download partitions. Or I've seen users use @bender_007 's autorec TWRP app made for either 23C or 24B on 35B.
The fortune is - it´s easy fixable
I´ll work on one for 35b for sure
I acquired an lg g3 on 24b. I figured I would make it as a spare incase I lost or damaged my original and use it to test newer versions like marshmallow or nouget.
Here's what I did
1. I I restored factory image using lg flash tool .tot version back to 10b
2. stump rooted it.
3. installed earliey twrp from 2014 with flashify
4. installed twrp 3.0.0
5. did a twrp back up including EFS
6. restored my jasmine9.1 -35b image to it. with EFS checked
7. Noticed my modem/baseband version was "Unknown"
I was going to flash the 35b modem but before that I had some questions.
Questions.
1. what exactly is EFS? ( am asking because I included it when I went from 10b to jasmine9.1 35b I need to know if that's something you dont flash from one phone to another)
2. if I flash my modem file to 35b wil I be able to flip flop back and forth and upwith modem files.?
3. how high can I go with revsions keeping twrp and modem/baseband without have to restore original with .tot if I want to get back to 35b.
I know enough to be dangerous so I'm asking cause I don't know enough! lol
thanks.
EFS is or includes your IMEI. If your 35B backup was from another phone, you don't want to restore EFS from your old phone. Restore your EFS from your 24B backup. You don't normally want to restore your EFS every time you restore a TWRP Backup. I personally do a TWRP back up of just my EFS and save it to Google Drive since sometimes flashing a TOT, KDZ or ROM will wipe the IMEI and without having an EFS backup handy, it's a bigger pain to restore using proprietory Windows software.
Just in case you don't know, never flash a Bootstack BEFORE flashing either JasmineROM 9.x or SkyDragon 6.x. After flashing either ROM, either flash the 24B or 35B Bootstack from @xdabbeb 's VS985 v2.0 ROM thread in the Development (non-original) section. Don't just flash the modem.
If you flash the 35B Bootstack you can certainly flash the 24B Bootstack later if you wish. The Bootstacks contain more than just the modems, but they include the modem too. The modem sometimes requires a newer sbl1 partition which is included, which is why you should flash the entire Bootstack and not just the modem, because the Bootstacks contain the appropriate sbl1. Not having the correct modem/sbl1 combination (for instance, 35B modem but 24B sbl1, or when using an older completely incompatible modem/sbl1 with a newer stock ROM) *might* cause the Settings / About / Status menu to show no IMEI too, but it shows back up after flashing the entire correct Bootstack.
The 35B Bootstack is the highest you can flash no matter what ROM you use on 35B or higher (46A or 47A). I'm not clear on what you were asking "how high can I go with revsions keeping twrp and modem/baseband without have to restore original with .tot if I want to get back to 35b" so if that doesn't answer that, please reword that question. You can flash @xdabbeb 's stock 47A (pre-rooted) firmware if you want to be on the 47A ROM; albeit you still have to use the 35B Bootstack.
I'm glad I saved the EFS from 24b now. (just incase I sell the phone I will restore it... doubt I will though but it's good to have. I don't mind flashing EFS to the second phone cause I will only use one at any given time with my sim card. I flashed xdabeb bootstack-35bmodem file already but I used the orignal not the non-orginal... so I guess I'm lucky cause it works. Thanks. I can't wait to try marshmallow! I got some reading ahead of me cause I want to get all the features I prefer working on marshmallow
like
xposed
wifi tethering with native app.
g3 tweak box (auto call recording feature is nice when your wife says "no I diddn't say that" lol
rp201 said:
I flashed xdabeb bootstack-35bmodem file already but I used the orignal not the non-orginal...
Click to expand...
Click to collapse
There's only one @xdabbeb VS985 v2.0 thread - in the regular Development section (what I call non-original), not the Original Development section. That's what I meant.
Hey folks. I'm in need of some help, but need to provide some background info as it seems there might be a few ways to correct this.
Background
I had a recent bad Nandroid mess up a restore process which somehow led to me losing root. I was on XDABBEB's 47A stock rooted ROM for months, then went to try the 3.1.1 ROM recently. I found that I wanted to go back, then BOOM! Bad restore from my data NANDROID. Then I:
Got stuck in a boot loop.
Rebooted into recovery
Saw the LG Recovery
(Stupidly?) chose to wipe cache
Continued to boot from LG Recovery
Went immediately to TWRP
Wiped Data and caches
Rebooted
At this point, I got back into 47A, but obviously without any data. I soon found that, though SuperSU was installed, it wasn't working:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-rot - consult the relevant forums for your device!
Click to expand...
Click to collapse
At this point, I checked Root Checker app and, surely enough, it says I wasn't rooted.
I checked ADB and tried to su from the prompt ($) and
Code:
su: notfound
However, adb reboot recovery brings me to TWRP
I tried TOT'ing on my Windows 10 (x64) machine, but it wasn't working:
PID: FAIL
IMEI: Unknown
[23:59: 0] CrossDL [Unknown] to [VS985].SW ***The text on this line continues, but I can't read it***
00000064
Error: [23:59: 0] CrossDL [Unknown] to [VS985].
Click to expand...
Click to collapse
I'm lucky in that my phone is currently working fine. I'm on 47a with everything working fine ... just not rooted, which I would really like to be.
So, my question is, what should I do next? I know some options that I have, I just don't know what options I should try or in what order I should try them...I understand some of the jargon and background info, but I don't understand the true inner workings of rooting and therefore don't feel comfortable making these choices on my own.
So, to all of you people that are way more intelligent at this than I am...
Should I try restoring my rooted 49A backup from TWRP?
Should I try to flash SU binaries in TWRP?
Should I TOT from my work machine that is Windows 7?
Should I KDZ on Windows 10?
Thanks in advance for your collective help.
This inquiring mind wants to know!
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone. In that case, you must flash back to 10B via the TOT method. That way, you can then root with Stump and then install TWRP, flash the correct boot images, and then reflash XDEBs ROM.
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method. It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
iBolski said:
I'm assuming that since you were running XDEBs ROM, then you do NOT have a K model of the phone
Click to expand...
Click to collapse
Correct. xdebbeb's stock 47A on a non-K model
Stock 47A is only rootable by Kingroot and there is NO way to install TWRP with pure stock 47A, which is why you must downgrade via the 10B TOT method.
Click to expand...
Click to collapse
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
It's the boot partition that is incompatible with TWRP and they have not found a way to "bump" it to work with the stock 47/48/49A versions.
Click to expand...
Click to collapse
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
my.ads0 said:
Correct. xdebbeb's stock 47A on a non-K model
That's why I'm confused a bit about my options. I already HAVE TWRP installed. Is having TWRP not helpful to regain root? This is causing me to feel like I'm in a weird limbo state (of options) with the phone.
Since I have TWRP already, does that mean that my boot partition was/is/has been "bumped"?
Sorry for so many questions. I do like making sense of things that I'm told and understanding them.
Since I'm failing on the TOT method at home, is that possibly because of the Windows 10 machine? Should I try Windows 7 on a different machine?
Thanks a lot for the help, iBolski.
Click to expand...
Click to collapse
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
iBolski said:
You're best bet is to either flash a full 47A KDZ but you won't be able to root and TWRP will be removed and you won't be able to flash custom ROMs, like XDEBB.
Your other option is to flash to 10B via TOT method, root, reinstall TWRP Then, based on the custom ROM's instructions, you may have to flash 35B bootstack, but you'll be in a position to flash custom ROMs again.
Either flash WILL erase everything on your phone as it's like a factory data reset. Those are your only options unfortunately. TWRP cannot work under 47A as you're finding out. You will be unable to flash root, any custom roms, etc.
Click to expand...
Click to collapse
I just want to make sure that you're aware that I am NOT on pure stock 47A. I'm on xdabbeb_stock_vs98547a.zip from here.
When I flashed back from his 3.1.1 ROM, I flashed to my backup of the above ROM, which had Root. The SYSTEM flash from my nandroid back to his version of 47A worked without incident, but the DATA flash of my nandroid failed, left me in a bootloop, after which I performed the actions outlined in my original post. That squarely left where I am now, with no root, but on his version of 47A (I never had the stock 47A on my device before) with TWRP as my recovery.
In the end, I'm game for trying different things, but ideally, I'd like to try the least invasive method (trying to flash SuperSU in TWRP?; trying to flash my xdabebb 3.1.1 version?) ) before trying any other method or going to the extreme method (TOT'ing). I just am trying to avoid TOT'ing since my phone IS working AND the fact that I would have to do that at work. It would suck to go from a working phone to a broken phone without being able to fix it without knowing that I tried all of the least invasive methods first. I just need guidance from people like you as to what will or won't work in my situation.
The reason for this post is that I wasn't sure that you were aware I wasn't on pure stock 47A, but on xdabebb's version, which maybe you had overlooked and offered me more options? If you were aware of that and everything above is irrelevant, then I'm cool with that. Just tell me so. I just didn't want that fact overlooked.
Thanks again for entertaining my inquisitiveness, iBolski.
Well, trying to install the SuperSU binary zip from TWRP didn't work. That got me flashing blue & red lights. I tried restoring my XDABEBB 49A 3.1.1 install and that didn't help either. Both TOT & KDZ methods are failing on my PC (Windows 10) with both not able to read the phone properly (can't see imei). I will maybe try to uninstall the drivers or just wait until Monday to try my windows 7 machine at work.
Oops.
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
my.ads0 said:
So I took up the cause again this morning and loaded all of the tools for the KDZ method on another PC. I installed the most up to date LG drivers, rebooted, made the PC recognize my phone in every mode (Download Mode, Bulk Mode [flashing lights], and while in TWRP). The tool still wasn't working properly and not reading my phone's info. Though I had run it a few other times, I had been following instructions and hadn't changed the language to English. The last couple of times, I changed the language to English. This time, when it stopped working (not connecting to LG servers) it offered me the option to retry. I took them up on the offer ... unplugged the phone, pulled the batter, put the battery back in, entered Download mode (volume up + connect USB), reconnected and BAM!!! It did the upgrade!
So I'm back on 10B. Crisis averted.
Thanks once again for putting up with me, iBlonksi.
Click to expand...
Click to collapse
Awesome. I saw your earlier post about being on XDEBB but that didn't matter. You were at a point that flashing back to 10b was your best option to get back to XDEB. That's why I kept saying you needed to flash back to 10B if you wanted to get back on XDEBB because where you were at that point was messed up, so it was just best to flash to 10b clean.
Glad you got it all worked out!
Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
animenote said:
Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
Click to expand...
Click to collapse
I am just getting back to messing around with phones after about 5 years. So many things have changed and I am trying to get answers here as well.
I used TWRP and Magisk to root my phone. Installing TWRP will not wipe your data as it is flashed to a different partition but to install TWRP you have to unlock the bootloader and that will wipe your userdata. And no, I don't believe there is any possibility of rooting without unlocking the bootloader. If you decide you want to go back to stock, there are stock roms available and you can re-lock the bootloader on the N10 so you should be able to set it back to just like it was when you first bought it. I say should because I have never done it, just read that it can be done when I unlocked and flashed mine.
I wish I could be of more help but so many things have changed in the years since I've been away from doing this stuff I feel like a total noob again.
animenote said:
Alright, I've received the email as the title implies but here are the questions I have before I proceed into the whole process
Is there a way to backup the stock image without TWRP? if so how do you get the stock image backed up if it's impossible how to back up the stock bootlover/recovery before installing TWRP if I were to get rid of TWRP one day?
also is it possible to just root the system without flashing anything to avoid data loss? this would be the preferred option actually, thanks! (Using the be2028 t-mobile version, if there's a premade backup that'll be cool too.)
Click to expand...
Click to collapse
No I do not believe there's a way to gain root without flashing anything. There's no need to backup anything you can always use the MSM download tool to restore your device. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ You should be able to find most of the stock imgs on here already if you'd really need to flash back. I'm no expert either, just my experience with this phone in particular has been pretty straightforward. I never backed up anything lol.
Twrp is iffy i made a backup I'll never use, check out the post about flashing international rom to tmo and metro devices, that's my backup. Also you can run 11.0.3/2 firmware and boot 11 gsi's the post about lir rom has the info. Flash the product_gsi.img referenced there, I have never deleted my product partition and I only leave oos ten installed long enough to take ota's. There are more roms in the source forge page referenced with lir rom post. Flash magisk via recovery, either side load or twrp, pay attention that it flashes partition sda14(super image) or wifi breaks.