It's been years since I've installed a custom ROM, so I'm rusty on the process and trying not to brick my phone. I have a Verizon Galaxy S5 running OptimalROM 13.1, and I want to upgrade to LineageOS (KLTE) 14.1. I went to this page and tried to follow the instructions:
https://wiki.lineageos.org/devices/klte/install
However, it gave me errors just trying to prepare for the install using Heimdall, at step 5 where you're supposed to enter "heimdall print-pit". It tries to download something and fails. I don't have my usual assortment of microUSB cables so it is possible the one I'm using is suspect. It also occurs to me that the instructions could be assuming I'm upgrading from stock rather than another custom ROM.
Like I said, it's been ages since I've tried doing this, so I appreciate the help on these newbie-looking questions.
TIA
thread closed as duplicated on https://forum.xda-developers.com/galaxy-s5/help/problem-installing-lineageos-verizon-t3694592
Related
Hey all,
I apologize if there is a thread for this already. I have the Sprint GS3 that I made the terrible, terrible mistake of upgrading to the stock 4.3 to give it a try and see if I like it.
After some scary moments trying to go back to the beloved CyanogenMod and bricking the device, I found I could install Cyanogenmod using their self-installer after restoring the phone to stock in Kies.
I'm running Cyanogenmod now, but there is an update available and when I try to let it update, it reboots into recovery, gives the sad broken android graphic, and reboots. I've not been able to install anything ROM related since.
Is Knox preventing the update, and is there a workaround to get the update to install without wiping the device back to stock?
emike09 said:
Hey all,
I apologize if there is a thread for this already. I have the Sprint GS3 that I made the terrible, terrible mistake of upgrading to the stock 4.3 to give it a try and see if I like it.
After some scary moments trying to go back to the beloved CyanogenMod and bricking the device, I found I could install Cyanogenmod using their self-installer after restoring the phone to stock in Kies.
I'm running Cyanogenmod now, but there is an update available and when I try to let it update, it reboots into recovery, gives the sad broken android graphic, and reboots. I've not been able to install anything ROM related since.
Is Knox preventing the update, and is there a workaround to get the update to install without wiping the device back to stock?
Click to expand...
Click to collapse
I will give you my two cents. First, rooting and installing custom ROM's should not be done using magical wonderful "one click" processes or apps that will do it for you. The Cyanogen Installer was a huge disservice to the rooted community in my opinion. Users need to get their hands dirty when rooting, so that they know how to work through problems forwards and backwards. That being said, I would highly recommend following this procedure to make sure your phone is rooted properly and running the correct recovery (Philz Touch, which is unbelievably awesome); my friend @goku2778 did a very nice job putting this tutorial together:
http://forum.xda-developers.com/showthread.php?t=2596697
After that, just download the ROM (or ROM's, I like to run various ones at any given time) from the proper sources, and flash them yourself.
I'm against one-click stuff myself. I've been rooting and running custom roms since my original Evo 4g.
If bricking my device after trying to roll back to a custom rom after Knox did it's business, and then recovering back isn't getting my hands dirty, then I don't know what is. I've spent plenty of time in adb. This issue though has me boggled. Why can the installer put a custom rom on when attempts to flash a custom rom (usually run nightlies) brick the device?
Thanks for the link, I'm taking a look into it now.
emike09 said:
I'm against one-click stuff myself. I've been rooting and running custom roms since my original Evo 4g.
If bricking my device after trying to roll back to a custom rom after Knox did it's business, and then recovering back isn't getting my hands dirty, then I don't know what is. I've spent plenty of time in adb. This issue though has me boggled. Why can the installer put a custom rom on when attempts to flash a custom rom (usually run nightlies) brick the device?
Thanks for the link, I'm taking a look into it now.
Click to expand...
Click to collapse
Didn't mean to imply that you weren't getting your hands dirty in general, just the way I word that rant every time I give it! My understanding is that there are compatibility issues between the CM installer and Knox, so yes, that is probably the basis of your problem. The combination of Philz Touch recovery and SuperSU that @goku2778 uses in his tutorial should solve your problems, it is the combination I have been recommending to VM and Boost users on Android Forums for a while now, with great success.
Mr. Struck said:
Didn't mean to imply that you weren't getting your hands dirty in general, just the way I word that rant every time I give it! My understanding is that there are compatibility issues between the CM installer and Knox, so yes, that is probably the basis of your problem. The combination of Philz Touch recovery and SuperSU that @goku2778 uses in his tutorial should solve your problems, it is the combination I have been recommending to VM and Boost users on Android Forums for a while now, with great success.
Click to expand...
Click to collapse
If memory serves there is a zip out there somewhere that flashes Knox apps away. Furthermore if it's a Boost or VM device you have to edit the updater script to make a Sprint ROM flash successfully.
Deucalion29710 said:
If memory serves there is a zip out there somewhere that flashes Knox apps away. Furthermore if it's a Boost or VM device you have to edit the updater script to make a Sprint ROM flash successfully.
Click to expand...
Click to collapse
The DeSamsungnizer zip is part of the tutorial by @goku2778, but keep in mind that this just takes care of the Knox apps, the actual bootloader is never ever going away unfortunately. And yes, for any users of VM or Boost who are reading this, there is extra work involved once the custom recovery has been installed and root has been successfully achieved.
Galaxy s3 on Virgin Mobile running cm11
I recently upgraded my s2 which was running cyanogenmod 11. I rooted and flashed everything myself with no difficulty. But after I switched that phone to an s3 I have had a ton of issues. My s3 was for Virgin Mobile (sgh-I747M) and nothing supported it. I was able to root and install clockworkmod with a little bit of difficulty. It wasn't until I tried installing cyanogenmod that it got really tough. Flashing would fail and at that point I didn't have an os so I thought I downloaded stock but was wrong when I hard bricked my phone. Anyways to the point. I ended up using the cyanogenmod installer which worked perfectly fine but now I can't update or download any nightlys. I'm not sure if it is because cyanogen had to install a custom kernel or not. When I go into system updates it says "your system is up to date. There is only one button that just checks for updates. Does anyone know how to fix this and allow me to install nightlys?
- Eric
Will CM installer work on S3-i9300(Int) version with 4.3 already installed?
Hi,
I am using the International version of SGS3- GT i9300. I dont know any of the process of rooting or installing a new version of android. But recently i have come across the cyangonmod installer app which i heard does all the work for us. I want to ask this doubt is that will the installation cause any problem if my S3 is already updated to 4.3 version? I am hearing people saying the KNOX might cause error. Should i wait for the CM 11 stable version or just give it a try ?
Thanks.
ericandbailey said:
I recently upgraded my s2 which was running cyanogenmod 11. I rooted and flashed everything myself with no difficulty. But after I switched that phone to an s3 I have had a ton of issues. My s3 was for Virgin Mobile (sgh-I747M) and nothing supported it. I was able to root and install clockworkmod with a little bit of difficulty. It wasn't until I tried installing cyanogenmod that it got really tough. Flashing would fail and at that point I didn't have an os so I thought I downloaded stock but was wrong when I hard bricked my phone. Anyways to the point. I ended up using the cyanogenmod installer which worked perfectly fine but now I can't update or download any nightlys. I'm not sure if it is because cyanogen had to install a custom kernel or not. When I go into system updates it says "your system is up to date. There is only one button that just checks for updates. Does anyone know how to fix this and allow me to install nightlys?
- Eric
Click to expand...
Click to collapse
did you figure out how to get nightly updates, from cyanogenmod installer ? I want to try the cyanogen installer to get cm 11 on my gs2 and gs3 (my specific devices are not on the cyanogenmod devices list, so i'm hesitant ) .. please respond .. anyone who can help ..
Hello, everybody. I just wanted to pass something on that more knowledgeable folks might already know, but I didn't know until now, so maybe someone else doesnt know and might benefit from something I just found out. I was under the impression that you couldn't use heimdall to install a custom recovery on a sammsung galaxy note 3 sm-n900t (tmo model) but had to use Odin instead. Well, what a PITA to borrow a windows puter for flashing and rooting when you are a ubuntu user! Yeah odin probably runs under vmware just fine and possibly wine too, but do I really want to try to make my linux laptop more windows-like? Nevertheless that is how I had been doing it until today.
last week I took my old tab 2 for a spin and decided it could use a more modern recovery and OS. I followed instructions (darn... i cant post the url! but just google for the title, "How to Install CyanogenMod on the Samsung Galaxy Tab 2 7.0 (GSM) ("p3100")") on the CyanogenMod Wiki for installing recovery using heimdall and it went off swimmingly. I already had 3 sm-n900t devices all on CM12 and just got another one for trying other ROMs. Well, that meant I had a totally expendable note 3 to experiment with, so I thought I would give heimdall a stab at it even though I was doubtful of the outcome.
I had just bought this phone on a certain popular auction site, and rushed into flashing it without doing my homework. I stuck a TWRP 4.4 recovery in it and it took just fine, but the stupid phone wouldn't boot into recovery. Okayyyyyy... looked in About Phone and noticed the android version was 4.3. The 4.4 TWRP couldnt boot with the 4.3 bootloader onboard. So I downloaded a 4.3 TWRP, flashed, and wa lah! Now it boots right up into TWRP recovery! Just to kind of check it out and make sure it was fully functional, I flashed a CM12 nightly, a GApps package, and the most recent SuperSU straight from the sd card using TWRP and it works just fine! And it all started with flashing TWRP to the Note 3 with Heimdall on Linux instead of the usual Odin on Windohs.
So fellow linux users, don't despair. Apparently heimdall v1.4.0 will work with the Note 3. At least it did for me.
I would be most interested in anybody's results, or lack of results, of attempting to install custom recovery on the Note4 or Note5, or the latest S phones., using Heimdall/Linux.
Hi there,
GrowleyMonster said:
I was under the impression that you couldn't use heimdall to install a custom recovery on a sammsung galaxy note 3 sm-n900t (tmo model) but had to use Odin instead.
...
last week I took my old tab 2 for a spin and decided it could use a more modern recovery and OS. I followed instructions (darn... i cant post the url! but just google for the title, "How to Install CyanogenMod on the Samsung Galaxy Tab 2 7.0 (GSM) ("p3100")") on the CyanogenMod Wiki for installing recovery using heimdall and it went off swimmingly.
...
And it all started with flashing TWRP to the Note 3 with Heimdall on Linux instead of the usual Odin on Windohs.
Click to expand...
Click to collapse
I know this is a long time ago, but I am exactly searching for what you did, and - unfortunately I can't find the wiki entry you mention and I did not find so far information how to put a twrp recovery on a phone using heimdall.
If you read this: how did you do it?
EDIT: I did not succeed using heimdall with the very first "download", where I used odin. Now heimdall seems to work as well. See here: https://forum.xda-developers.com/an...unlock-bootloader-using-t4136645#post83117731
Hi all, I posted a question in the giant general "ask question here" thread but I'm thinking this might be more nuanced than I realize after I saw that thread about downgrading=brick.
I've got Z00A, I bought it new a month or two ago--'just tested' seller said but it looks like it was used up until october of last year. It was running android 5 and CM 12.1 (I think) and had TWRP 2.7 (I think). When setting it up I saw update about an update "CM13... nightly". Installed it, booted phone and it had no gapps and tried too many half assed solutions so I started over and installed TWRP 3, got Open Gapps and CM13-0522 and started over. Seemed to work great but then I noticed stuff like the camera would freeze or take pics that would come out a blank green screen and the mobile data connection almost never worked (though I'm on new carrier) and a few other problems. Is it possible that since I went from CM12 (and presumably no updates since october) straight to CM13-0522-nightly that I missed or somehow 'skipped' a bunch of firmware updates? Does the latest version not include the updates from previous versions?
I was going to try rolling back to stock via one of the ASUS ROMS but I have no idea what version to get because I cannot determine what I currently have or what the phone had to begin with (version as in "V2.20.##.###"). Also, I don't think I installed any ASUS rom before----I just installed CM13 and OpenGapps. Then I see posts about sideloading the ASUS firmware roms in regard to users trying to revert/reinstall firmware: is this what I should be doing?
I read the FAQ thread and searched what I could but it has only left me more confused. I'm fairly technically apt but cell phones are not at all my usual foray so any help is greatly appreciated.
ohituna said:
Hi all, I posted a question in the giant general "ask question here" thread but I'm thinking this might be more nuanced than I realize after I saw that thread about downgrading=brick.
I've got Z00A, I bought it new a month or two ago--'just tested' seller said but it looks like it was used up until october of last year. It was running android 5 and CM 12.1 (I think) and had TWRP 2.7 (I think). When setting it up I saw update about an update "CM13... nightly". Installed it, booted phone and it had no gapps and tried too many half assed solutions so I started over and installed TWRP 3, got Open Gapps and CM13-0522 and started over. Seemed to work great but then I noticed stuff like the camera would freeze or take pics that would come out a blank green screen and the mobile data connection almost never worked (though I'm on new carrier) and a few other problems. Is it possible that since I went from CM12 (and presumably no updates since october) straight to CM13-0522-nightly that I missed or somehow 'skipped' a bunch of firmware updates? Does the latest version not include the updates from previous versions?
I was going to try rolling back to stock via one of the ASUS ROMS but I have no idea what version to get because I cannot determine what I currently have or what the phone had to begin with (version as in "V2.20.##.###"). Also, I don't think I installed any ASUS rom before----I just installed CM13 and OpenGapps. Then I see posts about sideloading the ASUS firmware roms in regard to users trying to revert/reinstall firmware: is this what I should be doing?
I read the FAQ thread and searched what I could but it has only left me more confused. I'm fairly technically apt but cell phones are not at all my usual foray so any help is greatly appreciated.
Click to expand...
Click to collapse
You can flash mr gouravs work here via twrp
download all his files to phone ... follow his flashing procedure and you will be on the latest stock via twrp ..
http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Hi folks,
I'm after some information. My Nexus 4 is about kaput now with the battery lasting about 4 hours or so with a full charge so I am looking to move over to my S4 mini for a while before buying an upgrade.
However i don't fancy rolling back to 4.4.2 from 5.1.1 as have got accustomed to it now. so there for I am looking to upgrade/flash it or whatever.
I am quite the novice and have not done this on any phone before so I am looking for a bit of help,
I have looked over xda and read some bits but think someone just telling me would be better, i'm not a tech dunce but I am not 100% confident in this at the moment as there seems to be more than one way of doing this.
What do i need to do first and foremost to make the process go as planned?
I take it I need to "root" the phone first (what does this do ? give me access to the firmware level? is that it?) using a "recovery tool" as they are called (is that right?)
Then after I have done that I can install a fresh ROM onto the phone and basic app's etc.
I have seen these guides:
http://forum.xda-developers.com/showthread.php?t=2364980
and
http://forum.xda-developers.com/gal...i9190-i9195-cyanogenmod-13-0-s4-mini-t3276141
Is it just a matter of following them or are there other things I need to do first, in between or after?
I am not bothered about anything being saved on the s4 mini it can be wiped clean and start a fresh, I don't need any of my data on it backed up
A quick bullet guide or acknowledgement of the two threads above or pointing me towards some better ones would be great and any pointers or descriptions of the acronyms or places in menu's which may have had their names changed or have been moved.
Many thanks Everyone,
Dahools
Hi!, you dont need to worry about anything, the only thing that you need is follow these guides, but make sure if you have the correct variant.
First Install Kies and connect your phone to it( For correct phone drivers). And after phone connect wells, Close kies from task manager.
You Need Odin to install a recovery software in your phone(TWRP, Clock Recovery, Philip). I only used twrp now.
Here is link below with instruction. Download recovery for your variant(i9190,i9192 or i9195 base on your model).
http://forum.xda-developers.com/showthread.php?t=2678420
Suppose if you install TWRP. Boot into recovery, And click Wipe, Do a factory reset , Clear Devil cache, Then go back and install your Firmware(cm12.1 or cm13 for your intended model). And flash Gapps as well. Then reboot. And you are done.
I have tried TWRP for both i9190 and i9192 model. and installed custom roms. Work fine.
Good Luck.
thanks fellas
I went for it with the original links and it worked. (eventually) A bit of user error on my part missing recovery mode on reboot first time and thinking it was done when it wasn't. Only putting the first bit in (root kit v2) then not realising how to flash the next parts. A bit of persistence paid off.
I have a I9195 model and rooting with that clockwork worked then loading the CM13 and then the Gapps. All one after the other in one go finally worked for me! so so far so good, just getting used to Android 6 now I think everything is working though, not put my sim in yet. will do that tomorrow.
If anyone was to follow what I did the big tip I would say is copy everything onto the SD card before you start anything, not as I did at first just putting the first bit on then thinking I can copy the next bit on later . . .
I was trying to update the OS on my Nexus 7 2013. I was able to connect it to my PC and unlock it and erase user data using adb commands. But after that it will not go past the Google logo in Recovery or regular Start mode. When I run "adb devices" it does not show up, though my computer does see it since I can run the lock/unlock adb commands and they work. I have uninstalled/reinstalled different adb drivers for the devices. I've tried using 2 different PCs. I can not get adb to fully recognize the device. I tried the Skipsoft Android Toolkit, and it too reports "no device detected".
Have I completed bricked the device? Or is there some way out of this that I haven't though of/found on the internet yet?
I hope someone here can help me!
Thanks!
Assuming you're on stock, try flashing a factory image from Google themselves. This reflashes everything, like stock OS, recovery, bootloader, etc. I'd choose the latest version found here: https://developers.google.com/android/images#razor As long as you understand that this wipes data, then give this a shot and let us know the results!
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
adamwsh said:
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
Click to expand...
Click to collapse
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
NTGDeveloper said:
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
Click to expand...
Click to collapse
Thank you! I did manage to get 18.1 to flash and load, after using a repartiion tool I found. However, I can't get GAspps to load, saying there isn't enough room on the partition. Now, I'm trying to use NRT to get back to stock (like I was able to do earlier) but now it is getting stuck at the Android 6 startup animation (4 round icons). I'm wondering if it is because I ran the partition update and somehow have to put that back to get the stock ROM to work.
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
NTGDeveloper said:
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
Click to expand...
Click to collapse
I wound up flashing Stock Android 5.0 and it worked. Now I'm updating to 6 via the software upgrade in the OS itself. I feel like this thing is just too old and not large enough memory to handle a custom OS.