Related
Hey guys, could you please give me a hand? I'm really new so forgive me if I don't express myself correctly!
I was trying to instal CM12, and an error ocurred during instalation and it said "instalation aborted" or something like that. After that it only stays in CWM and I can't reboot. I've wiped cache and dalvik numerous times but it's always the same. I also did factory reset and nothing. I can't seem to load another ROM because the SD drive doesn't show up in my computer even though the phone is conected. What else can I try?
Please help me get out of this, I'm a little freaked out =/
Please? I'm clueless
I'm thinking I need to try to flash the stock ROM with Odin...but I can't enter download mode because as soon as I put the battery in, it reboots to recovery mode. Any ideas?
Thanks!!
if you did nandroid backup before flashing you should be able to flash that, you would be better off using twrp for flashing this rom
I didn't do nandroid backup, it wasn't a step in the guide (http://forum.xda-developers.com/showthread.php?t=2400123)
So I hope I'll be able to flash it anyway? I'm following these steps now: http://forum.xda-developers.com/showthread.php?t=2159660
I figured the problem was using CWM and not TWRP =/
ok, let us know how you get on. always follow instructions for each rom, and do backup just incase a problem arises. what rom were you using before trying to flash this one?. dont forget cm12 is based on lollipop which isnt really meant for our phone.
Thanks! I'm downloading a stock rom, but it's taking forever. Is it normal that it downloads at 40 kbps? It's taking like 4 hours this way =/ I suppose there is nothing faster except paying for a premium account? I also tried it from other sites but download speeds are terrible. My connection is not so bad...
Anyway, I had CM 11. Once I get ti back (fingers crossed) I figure I'll try CM 12 again, this time with TWRP.
Thanks for the help!
ok, go here....http://www.sammobile.com/....and d/l the latest firmware for your region & carrier, then flash using odin, dont flash a stock-based rom, this will take ur fone back to original, then root & flash custom rom......carefully....
It worked!! Finally!! Thanks a lot, I'll do it more carefully next time, but I'll be stuck with this stock ROM for a little while. One last question, how important was it that it wasn't the one for my country? I didn't find one and I flashed a Romanian one...phone is working fine though!
Yea should be fine, glad I could help, walk before run, take it easy... Enjoy the ride....
Sent from my GT-I8190 using XDA Free mobile app
Seleuco said:
It worked!! Finally!! Thanks a lot, I'll do it more carefully next time, but I'll be stuck with this stock ROM for a little while. One last question, how important was it that it wasn't the one for my country? I didn't find one and I flashed a Romanian one...phone is working fine though!
Click to expand...
Click to collapse
All rom's are multilanguage, only difference you can see in baseband. Sometimes on different contries basebad can work more stability than others. Thats all.
If you want experiment wtih install some custom rom use twrp from novafusion site. Its bringing to use with different filesystem and give to you simple and easy manager to get backup your data and get it back when something goes wrong. Remember, Do backup your Efs/imei, boot before flash something on external memory. If you loose without backup this data, you get tablet to tap on something without calling, mobile internet, wifi.
Sent from my GT-I8190 using XDA Free mobile app
Q&A for VS980 Resources - Bootstacks/Modems/Unofficial FW/Manual OTA/etc
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for VS980 Resources - Bootstacks/Modems/Unofficial FW/Manual OTA/etc. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
MicroMod777 said:
Sweet. Did you post you tried the bumped twrp on the 39a and it didn't work. Last time I remember they had to rebuild twrp based on 26a. It might need to be rebuild on 39a sources.
Click to expand...
Click to collapse
xdabbeb said:
Nope. No idea what the point of that is.
Click to expand...
Click to collapse
Following the links, it looks like there's a new root exploit using download mode for a number of LG devices - http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Help
With these zip files. Are we able to use twrp and jump back and forth between boot loader versions or once you go past a certain boot loader you have to revert back to stock or use a special process to down grade.
protfire said:
With these zip files. Are we able to use twrp and jump back and forth between boot loader versions or once you go past a certain boot loader you have to revert back to stock or use a special process to down grade.
Click to expand...
Click to collapse
You can, but when switching between different based roms you'll often need to flash stock to get your sensors working again.
Sent from my LG-VS980 using XDA Free mobile app
Looking for some guidance
Having some issues with getting setup to flash VS982.5
Had a replacement phone sent from Verizon because of a dead digitizer. The phone shipped with 27A. I was able to get it rooted and got recovery installed, but then started running into issues. From there, I used the 11A tot. Got rooted, used Autorec for recovery and then tried flashing 28A, but am now getting a secure boot error.
Anyone have any advice?
@xdabbeb ???
noob question
Ok been flashing for a while nexus 7 - nexus 7 2013 and nexus 10 but this lg is a diiferent animal so im on broadbase 26a and can flash all cloudys roms but cant get lollipop roms to flash tried flashing the 39a and it rebooted but no data so went back to 26a broadbaseand all worked again so my question is can i flash 39a with the 26a modem and make flashing lollipop Possibly. Im on the verizon vs 980 model. Thanks in advance
Help please!
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?
---------- Post added at 04:37 AM ---------- Previous post was at 04:27 AM ----------
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?
kongo101 said:
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?
Click to expand...
Click to collapse
So, after 3 hours of fiddling around, I figured it out.
1. I was in the process of using the unbrick method where you hop onto Linux and dd those 5 files to fix the error and unbrick your phone from the loop. However, I realized that method is for folks who actually still have a ROM installed. I had just wiped to install the XDABBEB's 482.5 FW and there was no other FW installed. Stupid.
However, I still had my internal SD card stuff (photos, Titanium backups, etc) that were on the phone somewhere.
2. Somewhere along the line of frustration, I thought that the only way was to get a replacement (insurance) phone, which would mean losing all my data anyways. During that time, I somehow got into fastboot mode. Then I tried flashing the stock 11A FW. Somehow, it worked! (I lost all my internal SD data though, sadly).
3. I took all the OTA updates to 28A. Then I rooted with IOroot, installed TWRP with AutoRec. Then I flashed XDABBEB's 28A bootstack and on the restart, I got that same stupid secure boot error and black screen. I was VERY upset at that point.
4. I did the Vol Down + Power button hold to get into recovery, and when it asked me if I wanted to factory reset, I simply said yes, and it brought me back to TWRP. I flashed XDABBEB's ROM and on the reboot, everything was fine
I'm sure most of this stuff just sounds dumb. I probably could have just got into recovery from the very beginning (step 4) and just flashed XDA's Rom and all of this would have been unnecessary. However, as soon as I saw the "secure boot error" I freaked out and started browsing XDA and jumped the gun. Lesson learned.
Thanks still, for the XDA resources so that I could eventually figure this out on my own, even the long way.
Thanks,
David.
kongo101 said:
So, after 3 hours of fiddling around, I figured it out.
1. I was in the process of using the unbrick method where you hop onto Linux and dd those 5 files to fix the error and unbrick your phone from the loop. However, I realized that method is for folks who actually still have a ROM installed. I had just wiped to install the XDABBEB's 482.5 FW and there was no other FW installed. Stupid.
However, I still had my internal SD card stuff (photos, Titanium backups, etc) that were on the phone somewhere.
2. Somewhere along the line of frustration, I thought that the only way was to get a replacement (insurance) phone, which would mean losing all my data anyways. During that time, I somehow got into fastboot mode. Then I tried flashing the stock 11A FW. Somehow, it worked! (I lost all my internal SD data though, sadly).
3. I took all the OTA updates to 28A. Then I rooted with IOroot, installed TWRP with AutoRec. Then I flashed XDABBEB's 28A bootstack and on the restart, I got that same stupid secure boot error and black screen. I was VERY upset at that point.
4. I did the Vol Down + Power button hold to get into recovery, and when it asked me if I wanted to factory reset, I simply said yes, and it brought me back to TWRP. I flashed XDABBEB's ROM and on the reboot, everything was fine
I'm sure most of this stuff just sounds dumb. I probably could have just got into recovery from the very beginning (step 4) and just flashed XDA's Rom and all of this would have been unnecessary. However, as soon as I saw the "secure boot error" I freaked out and started browsing XDA and jumped the gun. Lesson learned.
Thanks still, for the XDA resources so that I could eventually figure this out on my own, even the long way.
Thanks,
David.
Click to expand...
Click to collapse
The answer was to simply rebooting into recovery after flashing the bootstack, rather that rebooting the system. That would have prevented the secure boot error. Lesson learned the hard way.
Hey, tryna get my head to stop spinning after the loads of info I just memorized trying to figure all this stuff out. I'm trying to flash a CM12 official nightly on stock 5.02 and TWRP 2.8.5.1. I just used bouchigo's little guide to get the 28A aboot and bumped boot and recovery to see if that would let me flash CM12/the updated TWRP 2.8.6.0 and neither worked (I'm assuming because it's not 12b still). So now I'm about to try to use the 39A zip in here and then flash the 12b bootloader, but I'm not sure exactly how to do it. Do I just flash both in TWRP and then do the reboot to recovery? I tried to flash the new TWRP (2.8.6.0) in TWRP and it gave me the same loki error as CM12 did so not sure it will work that way with this? Also will it mess anything up with the bouchigo images I have installed/should i flash my stock backup before I flash the 39A? And once I install the boot stack can I just flash 12b boot loader and be good to go to install CM12?
Also is there anything major to be concerned about while messing with this boot stack stuff or will it mostly be recoverable problems where you can just flash your backup? Sorry for the general question. You don't have to go into too much detail or anything, just tryna make sure there's not something you would be more likely to do (like rebooting to system instead of recovery) trying to configure the boot stack to work for your needs. Thought it may be helpful for others also as I haven't seen too many (more specific and/or general) caution tips in the threads I've visited in the last few days, especially in the OP's. No offense to any of you developers or anything, just something I thought might be helpful in future posts (especially for semi-casual's and noob's like me lol). With that said I'm very grateful for all the information on this site and the devs for their time. Keep up the amazing work. And thank you in advance for the knowledge!
I'm confused with an issue I'm facing with my Vs980 on Tmobile, so might as well ask this here before I mess up the phone any further.
After flashing 39a kdz I was able to get LTE connectivity, but battery lifetime was kinda poor. A few posts reported improvements with a factory reset ... so I did just that. Battery lifetime was even worse ... so why not another factory reset? I did just that and LTE wouldn't come back on. The phone starts, shows full network, and 4G for a second ... then network connectivity becomes glitchy going on/off constantly. The only way to get a stable network connection was to go into the settings and change the network connectivity to UMTS/HSPA instead of the LTE/3GPP .
I tried flashing 27a kdz, but the same issue keeps on happening. Now I'm debating whether I should be flashing just the 39a modem from this post after a clean 39a kdz flash ... but I can't make much sense out of this thought.
Any ideas on what could be done to resolve this problem?
It works perfectly. Congrats!!!!
I have a question.. I'm on stock rooted 39a..do I need to flash bootstacks or can I just flash roms?
Sent from my VS980 4G using Tapatalk
Kilroy245 said:
I have a question.. I'm on stock rooted 39a..do I need to flash bootstacks or can I just flash roms?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I flashed the rom without bootstacks but in twrp, if it goes into sleep, i get a dead screen with lines which I need to reset with adb command
adb reboot
On 39A rooted and twrp
vs980 39a Bootstack lollipop no cell signal or service
i have this lg g2 vs980, i was running an old xdabbeb 24a bootstack with a KK lg g2 rom on cricket service everything worked good besides bluetooth. (rooted&twrp recovery)
since then i have flashed twrp 2.8.6.3 bump-blastgator. i followed xdabbeb instructions for flashing 39a bootstack and xdabbeb_vs980_312.zip but i have no cell signal. i also tried LP-TMO-Extreme rom with a t-mobile simcard and apn and it didn’t work either. i was wondering if someone here can help, i tried flashing this rom and bootstack in every combination i could imagine, and still no signal.
i also flashed the 24a bootstack back and KK rom back and now still no signal. can someone please help me, I’m out of ideas.
thanks in advance!
Error loki-ifying
Hello, following your directions at http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560, I was trying to flash the 39a bootstack zip from CWM on a VS980 10B. After the extractions, I got this message:
Code:
Finished!
script succeeded: result was [Finished]Checki
ng if loki-fying is needed/dev/block/platform/
msm_sdcc.1/by-name/boot needs lokifying.
[-] Failed to find function to patch.
Error loki-ifying the boot image.
I'm confused because it both says the script succeeded and that there was an error.
When I rebooted, I went into a bootloop. I got back into recovery. My recovery is now TWRP. I went ahead and flashed the 38A firmware, and everything seems to have worked out just fine.
Do I need to worry about the error I got flashing the bootstack?
So i installed android M and since then, no matter which ROM i flash including radios, stock ROMs, recoveries etc. My WiFi simply is stuck on "Turning on WiFi" Cellular data works fine.
I have a funny feeling it could be the bootloader that was released with M but obviously theres no going back now...
Any suggestions?
bump
Orkane1989 said:
So i installed android M and since then, no matter which ROM i flash including radios, stock ROMs, recoveries etc. My WiFi simply is stuck on "Turning on WiFi" Cellular data works fine.
I have a funny feeling it could be the bootloader that was released with M but obviously theres no going back now...
Any suggestions?
Click to expand...
Click to collapse
You CAN go back to 5.1.1...
Yeah I worked that one out shortly after. I have now reverted back down to the 5.1 boot loader and also tried the 5.0 with no success... WiFi still won't turn on....
bump
flash the factory image manually with fastboot?
That's the only way I flash stock images... Tried using NRT to fix it also and still nothing... Very close to relocking the boot loader and sending in away for repair/swap
Orkane1989 said:
That's the only way I flash stock images... Tried using NRT to fix it also and still nothing... Very close to relocking the boot loader and sending in away for repair/swap
Click to expand...
Click to collapse
first off, your bootloader has nothing to do with your WiFi. if you want, vomer posted a twrp flashable version of the m ROM, with a twrp flashable version of the bootloader as well. I'd try wiping data and system, then try to flash that version.
Will give it a go. I did try the flashable version after a few different tries on other ROMs. Didn't try flashing the boot loader though.... Will give it a go and report back... Haven't looked into it probably enough but does the N6 have a dedicated WiFi chip? If it does I might give it a reflow attempt if every last resort is gone.... Being a mobile technician definitely has some advantages haha
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
RLBL said:
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
Click to expand...
Click to collapse
it is really rare that a bootloader flash is required, and a radio update is never required. if you dont flash them, then you just dont flash them, thats all.
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
both mm a lollipop, i never updated my bootloader. i did update it after mm though.
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
RLBL said:
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
Click to expand...
Click to collapse
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
simms22 said:
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
Click to expand...
Click to collapse
Cool... But I only used TWRP to flash the SU binaries to root. Now that I am rooted, I figured I could simply go back to stock recovery* and use flashfire going forward.
* I figured that because I had no other use for for a custom recovery presently, I may as well stay completely stock and rooted. Furthermore, from my understanding (which can be wrong) I no longer need a custom recovery to flash/install anything, as flashfire can do it all. Of course that brings one to ask "why am I rooted if I am staying stock?". I root my device so I can simulate a power button press without cancelling smart lock operations (either through tasker shell keyevent, gravity screen, or nova prime swipe gesture). I like not having to use the buttons on my phone
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
scryan said:
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
Click to expand...
Click to collapse
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
RLBL said:
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
Click to expand...
Click to collapse
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
31ken31 said:
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think that was the whole point of my post was it not? What happens if you DON'T flash a bootloader while using FF (but in the case where it did change)? And like I said, in the 1/1000 chance that something does go wrong and I did not have a backup: Flash the complete package via adb? Like I said, I have nothing to backup, thus nothing to recover. Not saying I shouldn't, just saying I don't. I only used TWRP to gain root access, nothing more (no custom ROMs, kernels, optimizations, anything on my phone...not even local app data saves - I am one of those old farts who uses their phone as a PDA with phone capabilities and that is it. All "data" is cloud based for calendar info etc.)
It was a relatively simple (general) question around some experimentation I am doing to see if it would work if one was completely stock (safe from root); did not think it would turn in an philosophical argument on whether or not one should use a stock recovery (which I have been using a custom up until yesterday, but was thinking about putting it back on this evening anyways, just because)
Anyways, got my answer... thx
simms22 said:
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
Click to expand...
Click to collapse
Thanks!... Obviously when I do venture into more with the phone I will do that. Currently it is a work and personal device so the only thing I do is flash Google stock builds instead of waiting for OTAs. Not saying I should not have a backup, but I don't. Only once after the 1st flash I re-locked the bootloader (as per instructions). What I waste of time; but it did show me that in a non-efficient disaster recovery, I can get everything back to where I was.
A restore would have been efficient, but I have found that I really have nothing to back up.. yet.
I guess a (off-topic) question I have for you is: What and Why did things not work out? In my case where I am only flashing stock loads (not waiting for OTAs), what could one anticipate going wrong that a re-flash could not recover from, but a restore could? Example a write corruption of a partition and the only thing I can do is boot into recovery as my PC cannot see the phone via adb? Can something like that happen?
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
RLBL said:
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
Click to expand...
Click to collapse
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
simms22 said:
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
Click to expand...
Click to collapse
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
RLBL said:
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
Click to expand...
Click to collapse
custom recoveries just make things easier for you, overall, to do stuff. but kernels, that could be the bomb. but you will need to learn about how to use governors/schedulers to make any kind of headways. for example, i use a completely different governor/scheduler(ondemand/deadline) than any other nexus kernel, and i feel that my way makes my phone much better/faster than any other setup. and thats whats important to me
Update: test passed (I knew it would)
With a stock recovery, I was able to use flashfire and upgrade to the latest update and re-root.
hey, i haven't rooted a phone for personal use since kitkat came out, so it was weird to see cwm and supersu outdated and crusty. anyway, i did my research and bought this phone to play with. these are the steps i took:
unlocked bootloader
flashed twrp
flashed magisk and rebooted
flashed aokp, gapps, then magisk
watched it fail to boot according to plan
wiped and flashed aosp extended, gapps, and magisk
set it up and put in a verizon sim card
so everything's good except for the random weird buggy stuff. my only problem is that i can't get service above 3g. like an idiot i didn't test the phone out before i rooted it... i'm going to try my backup then maybe different roms, but does anyone know anything? i tried search and didn't find anything helpful.
xtasquee said:
hey, i haven't rooted a phone for personal use since kitkat came out, so it was weird to see cwm and supersu outdated and crusty. anyway, i did my research and bought this phone to play with. these are the steps i took:
unlocked bootloader
flashed twrp
flashed magisk and rebooted
flashed aokp, gapps, then magisk
watched it fail to boot according to plan
wiped and flashed aosp extended, gapps, and magisk
set it up and put in a verizon sim card
so everything's good except for the random weird buggy stuff. my only problem is that i can't get service above 3g. like an idiot i didn't test the phone out before i rooted it... i'm going to try my backup then maybe different roms, but does anyone know anything? i tried search and didn't find anything helpful.
Click to expand...
Click to collapse
I use Straight Talk, which uses Verizon, all is well with mines. I never had to backup EFS or anything when I first rooted my phone but maybe that's a good Idea for you to do. Return to stock xt1806 April patch. And take OTA updates and backup efs after you reinstall twrp. Than flash your custom ROM. Is you don't have the speed you need then restore efs from twrp. Also make sure your didn't use all of your data on your plan [emoji39]
Sent from my XT1806 using Tapatalk
well i made the backup using defaults for twrp but i guess i didn't do it right and it can't boot now. any way to fix this?
edit: i mean, now i wipe and restore and the phone won't boot. i'm not bricked if i install the rom back. i don't even need anything fancy, just root access, lte data, and a 64-bit os.
i'm sorry for needing extra help. i did a week of research before i got the phone and thought i had all my ducks in a row.
xtasquee said:
well i made the backup using defaults for twrp but i guess i didn't do it right and it can't boot now. any way to fix this?
edit: i mean, now i wipe and restore and the phone won't boot. i'm not bricked if i install the rom back. i don't even need anything fancy, just root access, lte data, and a 64-bit os.
Click to expand...
Click to collapse
Just reinstall twrp and try flashing another ROM. If not return to stock and rerooted. But take backups of efs while doing it
Sent from my XT1806 using Tapatalk
xtasquee said:
hey....so everything's good except for the random weird buggy stuff. my only problem is that i can't get service above 3g. like an idiot i didn't test the phone out before i rooted it... i'm going to try my backup then maybe different roms, but does anyone know anything? i tried search and didn't find anything helpful.
Click to expand...
Click to collapse
I kinda did the exact same thing as you - unlocked bl, installed recovery, installed custom rom & then inserted Verizon sim...and I got the same result: no 4g.
You can try other ROMs and you may get lucky(I know I didn't get that lucky) but I ended up having to fastboot flash full stock(no need to relock bootloader) & let the Verizon sim register with the network. Once you boot into stock & see that lil 4g/lte icon you're good to go & can root, reflah twrp, rom, etc.
I think it's just a Verizon thing. Verizon making things difficult for custom software? No way - never - get outta here with that They do have the best service though. A lil pricey, but reliable AF.
i will try again. i found a post for the stock rom so i'm working on flashing it now. thanks very much for your advice and patiemce.
edit: ah thanks, bob. yeah, i have a habit of opening the box, glancing at the warranty, crumpling/disposing of it, and getting to rooting without much forethought.
uck, sorry but i'm searching for the stock us firmware and can't seem to find it. the one was an ad and everything i can find is for international or india. i know i messed up when i took my backup so i'm already kicking myself.
*edited out off-topic drunken rambling
*edited out off-topic drunken rambling
xtasquee said:
hey, i haven't rooted a phone for personal use since kitkat came out, so it was weird to see cwm and supersu outdated and crusty. anyway, i did my research and bought this phone to play with. these are the steps i took:
unlocked bootloader
flashed twrp
flashed magisk and rebooted
flashed aokp, gapps, then magisk
watched it fail to boot according to plan
wiped and flashed aosp extended, gapps, and magisk
set it up and put in a verizon sim card
so everything's good except for the random weird buggy stuff. my only problem is that i can't get service above 3g. like an idiot i didn't test the phone out before i rooted it... i'm going to try my backup then maybe different roms, but does anyone know anything? i tried search and didn't find anything helpful.
Click to expand...
Click to collapse
I had issues going to Verizon with custom roms. The fix was to flash stock, was all good after that. Just skip the erase modemst1 and t2 commands.