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 ..
So I have rooted and installed roms on several devices in the past but typically using how-to guides and such rather than just knowing how to do it. I got a little too confident with my note and decided to go ahead with a rom (Carbon) that didn't install (error 7). I, of course, deleted my cache and data and did a very dumb thing by not backing up before doing so. Yes, I know.
I am able to use Odin to switch from the stock boot screen (is it a bootloader just out of curiosity?) and cwm. I believe that if I could get a stock version of the N5110 Android rom I could switch from CWM to stock boot, and then sideload the stock rom.
As a sidenote, I am able to sideload with the stock boot however when using CWM, adb doesn't detect the device. Odin functions with both.
Just based on my past experience this seems salvagable to me. I have searched extensively for information but cannot find my specific situation with my specific hardware (gt-n5110) and, as always, the devil is in the details. I am also unable to find the stock N5110 firmware online except through Terafile which will not allow access without giving them $.
Can I utilize the fact that Odin functions in both settings (CWM and stock)?
I don't need to be chastised for how dumb not backing up is...lesson learned believe me.
Hope I haven't exposed my ignorance. Any constructive input would be appreciated.
Edit: I tried http://forum.xda-developers.com/showthread.php?t=2450005 and it said the signature was incorrect
Rom for note 8.0
Rom for note 8.0
jallenusn said:
So I have rooted and installed roms on several devices in the past but typically using how-to guides and such rather than just knowing how to do it. I got a little too confident with my note and decided to go ahead with a rom (Carbon) that didn't install (error 7). I, of course, deleted my cache and data and did a very dumb thing by not backing up before doing so. Yes, I know.
I am able to use Odin to switch from the stock boot screen (is it a bootloader just out of curiosity?) and cwm. I believe that if I could get a stock version of the N5110 Android rom I could switch from CWM to stock boot, and then sideload the stock rom.
As a sidenote, I am able to sideload with the stock boot however when using CWM, adb doesn't detect the device. Odin functions with both.
Just based on my past experience this seems salvagable to me. I have searched extensively for information but cannot find my specific situation with my specific hardware (gt-n5110) and, as always, the devil is in the details. I am also unable to find the stock N5110 firmware online except through Terafile which will not allow access without giving them $.
Can I utilize the fact that Odin functions in both settings (CWM and stock)?
I don't need to be chastised for how dumb not backing up is...lesson learned believe me.
Hope I haven't exposed my ignorance. Any constructive input would be appreciated.
Edit: I tried http://forum.xda-developers.com/showthread.php?t=2450005 and it said the signature was incorrect
Click to expand...
Click to collapse
Well friend, do never install a custom rom without making a backup
Here you can find the stock 4.2.2 for your Note 8:https://drive.google.com/file/d/0B9QvmNs9dpD-M21DaF95NWdNUW8/edit?usp=sharing
And also, I use to install custom roms and I always use this recovery:http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n5110/philz_touch_6.12.8-n5110.tar.md5
I really appreciate the upload. Whenever I sideload I am getting this error:
E: Signature Verification Failed
Any additional information I can provide?
Edit: Disregard. I installed phils touch wiz and now i'm attempting to sideload again. Keep getting a protocol fault (no status). Just a total shot in the dark but is this due to the pc-tablet connection dropping?
Edit 2: Dude. You are the man. Installed the touch wiz which, imo, far superior to CWM considering it allowed me sideload access and cwm didn't. Then turned off signature verification. Piece of cake.
Thanks so much.
jallenusn said:
I really appreciate the upload. Whenever I sideload I am getting this error:
E: Signature Verification Failed
Any additional information I can provide?
Edit: Disregard. I installed phils touch wiz and now i'm attempting to sideload again. Keep getting a protocol fault (no status). Just a total shot in the dark but is this due to the pc-tablet connection dropping?
Edit 2: Dude. You are the man. Installed the touch wiz which, imo, far superior to CWM considering it allowed me sideload access and cwm didn't. Then turned off signature verification. Piece of cake.
Thanks so much.
Click to expand...
Click to collapse
You're Welcome friend :laugh:
and by the way, next time you install a custom rom, make a backup first, you wont regret it
Greetings,
I really don't want this to be a repeat post, so I have spent many days now searching for this answer, not just here on XDA if I was honest, I have links to prove it
The aim is to give a little new life to my old phone, and get off the 4.1 build it is on.
With that said, in summary, I have tried a few different custom ROMs; Cyanogenmod 11 - 13, stable to nightly. PAC MAN ROM for Lollipop, some other roms for KitKat I found else where, but in all these I have not been able to get 4G to work. I understand about updating the Modem, and got the latest version from DocHoliday77's post for the Galaxy S3, in point of fact I tried every modem version for 4.3+ on there
But for all this, and it's been time consuming I never managed to actually get 4G to work as stated
I tried playing with settings in Test Mode (*#*#4636#*#*), changed preferred settings, added APN's, rebooting during certain phases of the moon ... but somehow it all avails me diddly.
Finally I have genuinely tried searching for info on if this just isn't going to happen and that's how it is, but somehow I found lots of posts about other models or networks that made it work more than something saying this won't work (putting aside the info on CM 11 that states it's a known issue and won't work on some build I forget).
Which leads me to this post: I wondered if anyone could point me in either the direction of a 4.4+ custom ROM or other ROM, compatible for SGH-T999 (T-Mobile Galaxy S3), that has working 4G. Or how I can get 4G to work on one of the ROMs I have already tried, kind of partial to a nice CM but I am willing to venture.
Also happy to just hear other input about giving new life to the phone so any feedback welcome
Thanks for your time!
NOTES
======
Using TWRP 3.x for flashing
Phone is rooted
IMEI is visible & fine on custom ROM
4G works on stock ROM
not experienced at this but willing to read
Edit: something I had not noticed before, I install Gapps for most of my tests but never use it. I just tried to download from Play Store, it acts as though I have no connection; waiting to download appears, then eventually it says waiting for network. Yet I am able to browse the net fine with the phone floating between 3G & H+. I don't know if that might help, so figured I should add it.
Is the phone running the latest bootloader and modem? Maybe both are needed to properly get 4g on all Roms?
audit13 said:
Is the phone running the latest bootloader and modem? Maybe both are needed to properly get 4g on all Roms?
Click to expand...
Click to collapse
That's a really good question, let me see if I can find out how to get my bootloader info and I'll get back to you.
May I ask what the latest bootlader is for the SGH-T999, or where I could find this so I can compare it? I couldn't seem to find it, though the most resourceful post I did find related was T999 UVDMD5 Firmware / Bootloader by mnasledov, though it is also a little outdated it appears, I haven't read my entire way through it yet sorry, I also know the phone is a little outdated too .
So that wasn't too bad to find out
I don't have the latest bootloader if that should match the baseband I install.
Where after a ROM install I get my baseband to T999UVUEOH1, but the bootloader stays on T999UVDLJA.
I haven't quite found where to get the latest bootloader just yet, though I did really spend the last few minutes discovering about the bootloader; if you or someone could find the time to point me in that direction that would be awesome
Simplest way to make sure you have the latest would be to flash the most recent stock rom from sammobile.com in Odin.
Thank you very much @audit13, I do appreciate the time you took out to help me and I also appreciate the point in the direction of what next.
I'll go dig into that for a while and see what to do to be sure, before I start
Looks like this is the latest one, so I will give this a shot : PDA T999UVUEOH1 & CSC T999TMBEOH1, version 4.3.
So just as a quick question, since I've never upgraded the bootloader in this fashion etc., from what I have read this is a one way street correct? And since I am upgrading to stock, then I guess will I lose root, which I will have to go back down the path of for a reinstall, or could I flash my old back up over this from TWRP and in that fashion have the latest bootloader, but keep everything I have for the moment as I investigate a ROM that will offer 4G.
I guess what I am getting at is even if having the latest bootloader and some other ROM with the latest baseband doesn't give me 4G still, can I go back in terms of the OS version to my 4.1.1 and keep things as is with a newer bootloader?
I will investigate this myself too, I just always preferred some additional input when discovering things where possible.
I do appreciate your time, thanks again!
No, you cannot run stock 4.1.1 on a 4.3 bootloader unless it is a custom 4.1.1 rom based on a stock touch wiz rom.
I do not think it is a problem to run the latest bootloader and modem as the latest custom ROMs often require an updated bootloader and modem.
Once on a 4.3 bootloader, you can't downgrade to something older.
Thanks again @audit13, that matches what I have read, I appreciate the confirmation!
Looks like I will be undergoing a re-root etc. so I'll get my information together, have a little more read, see what I need to back up and then jump down the rabbit hole
I'm grateful for your time and help.
If you decide to run a custom rom, just flash a stock rom, then immediately flash twrp via Odin, then install the rom and gapps. No need to root before hand.
Ahh ok, that would have made the most sense. However I didn't have an opportunity to check back on this thread until now so even though you had awesome speedy reply I missed it.
I did manager to successfully flash the stock ROM from Sam's. It did also update the bootloader so THANK YOU very much for that.
I had to fiddle a little to get Odin to recognize the my Galaxy S3 in the end it was simple: after I installed Kies to get the drivers on, I disabled WI-Fi (I use it for my dev work, and then it didn't try to spend time getting other drivers and it all went great. But that's just a note incase maybe one day someone else reads the thread and wonders how, this might help.
I'm just actually restoring a couple f things on the stock ROM, I figured I would have it ready in the event a custom ROM doesn't suit immediately, as I find one I like, then I have a back up of the stock ROM on 4.3 to revert to. Incidentally I just used TWRP manager from Google play store to install TWRP, hopefully it's the same as the flash, except now I know I rooted when I didn't have to
@audit13 Thanks, I know I keep saying that but I appreciate your time the same way I would hope someone else appreciated mine.
Incidentally once ready I will post an update here about the success of getting 4G on Cyanogenmod 12 or even 13 maybe, or someone of the other custom ROM I try, to share that info.
So just an update, I can confirm even with both an updated bootloader and matching updated baseband there is still no 4G on Lollipop Cyanogenmod 12, haven't quite tried any other yet, that was the one I liked the most but I will carry on and get a list as I have time then update here.
If there are any further suggestions I'm all open to them
Thanks [email protected]
Do you get 4G on a stock ROM? You have an LTE capabale sim? You get 4G on another phone with the same sim card?
Right, this SIM gets 4G on 2 other phones it's been in, on this phone on stock ROM it gets 4G too. Reverting back to stock backup in TWRP, from CM12 looks like it tripped knox I think it is, so now the warranty bit is 1 oops. But I managed to Odin back to 4.3 stock, so now I also need to see if I can try to flash maybe to CM 11, which is 4.4.x, or if maybe I'm stuck here. If I can find out I certainly will update the result of 4G testing.
You've been really patient & helpful thanks!
First let me say I'm a noob. I've rooted and jailbroken devices but I admit it's all from falling instructions. I rooted my s3 a while ago and installed twrp 1.0.8.7 yesterday. I did a full wipe including system and all catches and installed the latest nightly of cm13. Everything is running great. I don't know if this helps but maybe it's your process. Good luck!
Sent from my Amazon Jem using Tapatalk
Shack70 said:
First let me say I'm a noob. I've rooted and jailbroken devices but I admit it's all from falling instructions. I rooted my s3 a while ago and installed twrp 1.0.8.7 yesterday. I did a full wipe including system and all catches and installed the latest nightly of cm13. Everything is running great. I don't know if this helps but maybe it's your process. Good luck!
Sent from my Amazon Jem using Tapatalk
Click to expand...
Click to collapse
That's really helpful thanks @Shack70, since updating to 4.3 I have only tried CM 12, I can certainly give 13 a shot, & you have 4G working then please?
incidentally I have actually recorded every step I performed, in the event I repeat this again or I had to explain it. But my process maybe at fault I agree; I rooted my phone with towelroot. Installed TWERP manager (3.0.2 something, maybe I should try 1.0.8?), rebooted into recovery & first thing was take a full backup on stock. Then I did a factory wipe, & advanced wipe. Then installed the ROM, wiped dalvik/cache. Installed Apps, wipe dalvik/cache, reboot
Hopefully that's not too much? I just wonder if any of those steps raise alarm?
Edit: mind if I throw a few questions on here at you please @Shack70?
what do you wipe from the options please?
after the install, do you run any other wipes please?
how did you get TWRP on your phone? Not sure if that or version matters but I'm willing to try
Morrigon said:
That's really helpful thanks @Shack70, since updating to 4.3 I have only tried CM 12, I can certainly give 13 a shot, & you have 4G working then please?
incidentally I have actually recorded every step I performed, in the event I repeat this again or I had to explain it. But my process maybe at fault I agree; I rooted my phone with towelroot. Installed TWERP manager (3.0.2 something, maybe I should try 1.0.8?), rebooted into recovery & first thing was take a full backup on stock. Then I did a factory wipe, & advanced wipe. Then installed the ROM, wiped dalvik/cache. Installed Apps, wipe dalvik/cache, reboot
Hopefully that's not too much? I just wonder if any of those steps raise alarm?
Edit: mind if I throw a few questions on here at you please @Shack70?
what do you wipe from the options please?
after the install, do you run any other wipes please?
how did you get TWRP on your phone? Not sure if that or version matters but I'm willing to try
Click to expand...
Click to collapse
In twrp I wiped system and all caches before installing the rom and gapps. I installed an older version of twrp using Odin and updated it to 2.0.8.7 using the twrp app in the play store. Yes I have 4g/lte. I've seen it switch from lte to h+ to 3g depending on my location so I'm sure it's working correctly. The camera and Bluetooth also work fine. I hope this helps, I'm still learning and most of what I've done is just by following others instructions here at XDA.
Sent from my Amazon Jem using Tapatalk
I definitely appreciate the reply thanks!
I gave the latest nightly CM 13 a shot just now, 7/31/16 version essentially. Not finding any issues with the ROM, can't get 4G to show up no matter what though , even with changes and attempts to APN settings etc. None the less maybe to give my phone a rest I'll just stick with this a while and decide if a newer nightly comes out I want to try, or better yet a stable version at some point. Then I can verify how much I really miss my 4G I guess.
All the previous attempts, including this one always results in 3G to H+ network with no issue, it's just that 4G that never shows up for me.
Incidentally without a serious search around I couldn't even find TWRP 2.0.8.7, it's not on the TWRP manager version I have so curious, I ended up just going with 2.8.0.7, thinking maybe it was a typo?
Otherwise I basically run the same type of install you mention, I also clean dalvik, cache, system & data in my case. Just to confirm that.
I have a slightly off topic question here, if I decide to go back to to stock I was wondering, if i went from UVUEOH1 4.3 JB build, to the previous UVUENC2 4.3 JB build; because I've seen this available as a clean route 66 version, is this still considered a downgrade and a bad idea? I'd be flashing with Odin from @DocHoliday77 post here.
@Shack70, thanks for the input, thanks for the guide on your steps, glad I've confirmed I'm doing the same even if I can't get my 4G, hopefully someone on a Galaxy S3 T-Mobile, went through this found a solution, and maybe will let me know what they did too, not sure if you are on T-Mobile or not.
@audit13, also thanks, you've been replying plenty too and I appreciate that also!
One small thing I just came across looking over the logs of the install.
When flashing CM 13 with TWRP, I noticed it said the Target: samsung/d2tmo/d2tmo:4.3/JSS15J/T999UVUEMJC:user/release-keys.
Is it normal and OK for it the be referencing a different baseband/bootloader than what I actually have on my phone?
UVUEMJC vs the UVUEOH1? Where the one as named by TWRP flash is 2 versions older than what I have installed? Not necessarily stating this is an issue, just asking please if this is normal, and I also understand it could be something I have overlooked in my reading, it's been a lot of reading
I would not worry about the referenced baseband as flashing CM13 does not change the bootloader or baseband during the flash process.
audit13 said:
I would not worry about the referenced baseband as flashing CM13 does not change the bootloader or baseband during the flash process.
Click to expand...
Click to collapse
That makes sense thanks @audit13, just a few of the questions I had building up.
So that my previous question doesn't get lost, and although I know it's a dying phone for users hopefully this might get some visual
if I decide to go back to to stock I was wondering, if i went from UVUEOH1 4.3 JB build, to the previous UVUENC2 4.3 JB build; because I've seen this available as a clean route 66 version, is this still considered a downgrade and a bad idea? I'd be flashing with Odin from @DocHoliday77 post here.
Click to expand...
Click to collapse
Greetings,
Firstly, sorry for the noob question, but I recall that the snapshot versions of CM had their own custom recovery (CM Recovery) that could be updated via OTA together with the ROM itself for stability reasons. I haven't seen this on any other ROM and I'd like to ask if Lineage will have it's own recovery the same way CM did or not.
I particularly liked the feature because it allowed me to factory reset the phone without needing twrp (even though i'm not sure that the rom having it's own recovery has to do with being able to factory reset the same way stock roms do).
Once again, sorry for my "noobishness" and thank you to all who took their time to read this
Why not TWRP ?
We learn by asking - welcome to the club. Anyway, if there is a TWRP or Philz or an existing CM recovery for your device, why not just load one of them? I've never had a problem with the interaction between TWRP and CM, so I assume that will hold for the Lineage build(s) as well. That even includes my clumsy hacks of TWRP to get it onto unsupported devices. It seems to be remarkably robust and forgiving, and since a recovery really doesn't do a whole lot in comparison to a complete ROM, difficult to go far wrong. If there's no TWRP for you device, as long as you have the same processor there are VERY useful guides out here for porting it. The more the hardware you've got is similar to something that already works, the easier it is to do this. I frankly assumed I would brick everything I tried but so far I've been 100% successful - proof of blind luck. Oh yeah, it REALLY helps to have a stable working ROM image to revert to if your efforts to do this go South. That 100% success rate is after a few: "whew, glad I had this to go back to" moments along the way. :cyclops:
Good Luck !!
nezlek said:
We learn by asking - welcome to the club. Anyway, if there is a TWRP or Philz or an existing CM recovery for your device, why not just load one of them? I've never had a problem with the interaction between TWRP and CM, so I assume that will hold for the Lineage build(s) as well. That even includes my clumsy hacks of TWRP to get it onto unsupported devices. It seems to be remarkably robust and forgiving, and since a recovery really doesn't do a whole lot in comparison to a complete ROM, difficult to go far wrong. If there's no TWRP for you device, as long as you have the same processor there are VERY useful guides out here for porting it. The more the hardware you've got is similar to something that already works, the easier it is to do this. I frankly assumed I would brick everything I tried but so far I've been 100% successful - proof of blind luck. Oh yeah, it REALLY helps to have a stable working ROM image to revert to if your efforts to do this go South. That 100% success rate is after a few: "whew, glad I had this to go back to" moments along the way. :cyclops:
Good Luck !!
Click to expand...
Click to collapse
Actually, i have twrp on my phone and i love it, but i'm aiming to pass along this device to my elders that are not as tech sawy as i am. Só i wanted to give'em something functional, and there's where CM recovery saved me - everytime they need to factory reset their CM flashed phone they won't even need to enter bootloader to do it! I just hope it will be possible to do the same with LineageOS.
PS: i tried to do a factory reset from the settings menu with twrp on my phone and it didn't work. The phone remained exactly the same, just as if i hadn't done anything.
PS2: i know that twrp offers a factory reset option on it's menu but it would be hard to teach them how to use the recovery.
Or, if the devs intend to make a "Lineage Recovery" for whatever other reasons, i'd be curious to know them as well :good:
Thanks for the answer ?
well .....
"Actually, i have twrp on my phone and i love it, but i'm aiming to pass along this device to my elders that are not as tech sawy as i am. Só i wanted to give'em something functional, and there's where CM recovery saved me - everytime they need to factory reset their CM flashed phone they won't even need to enter bootloader to do it! I just hope it will be possible to do the same with LineageOS. "
I guess the magic question would be "how often are they going to be using it?" In the case of TWRP, the periodic (weekly or monthly) backup is about as blind simple as it can get - even I can do it without too much concentration
As for points of entry, CM / Lineage can easily be set to reboot to the recovery mode, whatever you use. It's down there in Developer Settings - piece of cake. Once done, tell TWRP to reboot to the System. a second piece, a la mode.
Good Luck.
It will be nice if Lineage produce their own recovery as CM .
In my case with Oppo R5 there isnt any recovery availaible yet to flash LineageOS
Existing TWRP and CM recoveries are useless
NO, but there are lots of options for the Honor 5X which seems to be very similar. Maybe you could port one of those? WHY, specifically, are they "useless" ?? If you would care to itemize what you tried and how they failed, maybe we could help.
nezlek said:
NO, but there are lots of options for the Honor 5X which seems to be very similar. Maybe you could port one of those? WHY, specifically, are they "useless" ?? If you would care to itemize what you tried and how they failed, maybe we could help.
Click to expand...
Click to collapse
Thanks for your response. With cm recovery we are getting signature verification failure. When we flash existing twrp recovery for our devise the phone stuck in oppo logo. Furthermore I don't have the knowledge to port recovery and our community is short of developers
Sent from my R5 using XDA-Developers Legacy app
mermigas said:
Thanks for your response. With cm recovery we are getting signature verification failure. When we flash existing twrp recovery for our devise the phone stuck in oppo logo. Furthermore I don't have the knowledge to port recovery and our community is short of developers
Sent from my R5 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Seems to be a somewhat common occurrence among octa-core devices, although I have more experience with MTK chipsets. In many cases they are still using the quad-core versions of code in their stock recoveries. Curiosity question: do you also find that the stock recovery mysteriously replaces the TWRP you just installed after it fails? Some MTK devices appear to stash a hidden copy of the stock recovery away and do this for (to) you. Not fun. :crying:
Does anyone know a custom ROM that has it's own recovery? I've been searching but haven't found anything yet.
I'm in doutbt that such rom even exists after CM got out of the picture since it was the only one that had it's own recovery..
A lineageOS specific custom recovery would be good, mainly because TWRP versions greater than 2.8 cause several banking and security apps to fail because they think the device is rooted even if its not. Many of these apps, like blackberry uem client (formerly known as GFE) falsely detect root simply because of something that TWRP has done in versions after 2.8 and this has nothing to do with unlocked bootloader flags. While lineageOS without the root addon passes safteynet now, in future it will be good if lineage has its own recovery rather than a third party recovery like TWRP.
Plus it would be nice to have one integrated system without the need to maintain/update two different pieces of software. It would just be cleaner, but that is a matter of taste.
Sent from my Nexus 9 using Tapatalk
I saw somewhere that they had plans for this but, after they've completed most/all the ROM releases.
I can't remember where I read it but, i do know that their still working on releases for more devices.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************
It is literally necessary, because recoveries depend on kernels, and currently TWRP use binary kernels in the repository (github:TeamWin/android_device_xiaomi_lithium) which may render it unusable due to kernel mismatch. Why not compile our own kernel when we have source code, and why not use the same kernel in the recovery? The best solution is to collect them together, under an unified organization.
test123321123123213 said:
It is literally necessary, because recoveries depend on kernels, and currently TWRP use binary kernels in the repository (github:TeamWin/android_device_xiaomi_lithium) which may render it unusable due to kernel mismatch. Why not compile our own kernel when we have source code, and why not use the same kernel in the recovery? The best solution is to collect them together, under an unified organization.
Click to expand...
Click to collapse
That is the dumbest thing you could imagine. Mainly when soo many different things effect the kernel. Also the kernel that you flash for the OS is not the same as what is needed in recovery.
Also cm recovery was the cause for many bricked devices. They have become more of a laughing g stock to android the miui, which is saying a lot. Many thing Los and Xiaomi should Tema up to make the ultimate joke device.
nezlek said:
We learn by asking - welcome to the club. Anyway, if there is a TWRP or Philz or an existing CM recovery for your device, why not just load one of them? I've never had a problem with the interaction between TWRP and CM, so I assume that will hold for the Lineage build(s) as well. That even includes my clumsy hacks of TWRP to get it onto unsupported devices. It seems to be remarkably robust and forgiving, and since a recovery really doesn't do a whole lot in comparison to a complete ROM, difficult to go far wrong. If there's no TWRP for you device, as long as you have the same processor there are VERY useful guides out here for porting it. The more the hardware you've got is similar to something that already works, the easier it is to do this. I frankly assumed I would brick everything I tried but so far I've been 100% successful - proof of blind luck. Oh yeah, it REALLY helps to have a stable working ROM image to revert to if your efforts to do this go South. That 100% success rate is after a few: "whew, glad I had this to go back to" moments along the way. :cyclops:
Good Luck !!
Click to expand...
Click to collapse
It sounds like you have a lot of luck in this area, I spent ages looking for a TWRP porting guide but couldn't quite find one that worked. Would you be able to get me a link to a good TWRP porting guide for a octa-core Samsung?
Cheers
So I had rooted my Tab S back in 2016 or so (if you check the forums here you'll see my posts for this...). Have had that working for a while now. It tripped the Knox (I didn't personally care about this) except now I want to install a couple streaming apps on the tablet and the OS is too old to handle it
I had loaded TWRP onto the Tab S and rooted it with Lollipop stock ROM and loaded it with SuperSU. It has worked like a charm up till now, issues with Link2SD notwithstanding (I have ZERO intentions of going back to that app).
My question is: what do I need to do to install the newest possible version of Android that the tablet can take? I know it's an older tablet now but I still use it for reading and other stuff, and I'd like to keep it alive a bit longer by installing a new Android OS and ROM on it.
(aside: I did remove a bunch of stuff once I rooted it, so I am not sure how much this may interfere with any attempt to update it to a newer version of Android)
(aside #2: I never updated SuperSU through the app store as I was afraid it would break the root process, so I left that app alone and eventually it stopped showing up in my update list on google play. I'd have to check the tablet to see what version of it I have installed at present)
Funny, I just updated my Tab S this weekend. Same as you, was running into apps that no longer support older OS. I updated mine to Lineage 14.1 version. So far working fine. I know there is a newer version but after reading the threads, this version seemed to be reported as working better. Just follow the instructions in the thread to upgrade.
cbb77 said:
Funny, I just updated my Tab S this weekend. Same as you, was running into apps that no longer support older OS. I updated mine to Lineage 14.1 version. So far working fine. I know there is a newer version but after reading the threads, this version seemed to be reported as working better. Just follow the instructions in the thread to upgrade.
Click to expand...
Click to collapse
Hey thanks for your reply!
Do you need to update the android version to get Lineage OS installed?
No you do not. You just have to update the bootloader. Instructions are in the thread on how to as well as to have to confirm.
Hi again,
Sorry could you point me in the direction of said thread?
cbb77 said:
No you do not. You just have to update the bootloader. Instructions are in the thread on how to as well as to have to confirm.
Click to expand...
Click to collapse
Wait I think I found it. Was this it?
https://forum.xda-developers.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t800-t3545080
bsquared938 said:
Wait I think I found it. Was this it?
https://forum.xda-developers.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t800-t3545080
Click to expand...
Click to collapse
Yes, that is the correct thread.
cbb77 said:
Yes, that is the correct thread.
Click to expand...
Click to collapse
Perfect. Will also update this table to give it a further lease on life .
Thanks man!
cbb77 said:
Yes, that is the correct thread.
Click to expand...
Click to collapse
@cbb77
Cannot find the Lineage OS ROM image, I think it may have been removed from their site given the age.
Do you have a working download link for this?
Edit: please ignore post, I found it as soon as I posted this -.-
T800 https://download.exynos5420.com/LineageOS-14.1-Deathly/chagallwifi/
Pretty bood performance and battery,also GPU OC.Load this with Gapps.
Trung Gs said:
T800 https://download.exynos5420.com/LineageOS-14.1-Deathly/chagallwifi/
Pretty bood performance and battery,also GPU OC.Load this with Gapps.
Click to expand...
Click to collapse
I assume I have to load the marshmallow bootloader before I do anything?
bsquared938 said:
I assume I have to load the marshmallow bootloader before I do anything?
Click to expand...
Click to collapse
Personally I like the Resurrection Remix rom. https://forum.xda-developers.com/ga...om-resurrection-remix-n-sm-t800-wifi-t3606243
Just do the standard stuff. You've got TWRP installed, so you're most of the way there. Back up whatever you want to back up, and then:
1. Wipe System, Data, Cache, and Dalvik Cache.
2. Install OS.
3. Install Magisk (if you want to use Magisk for your rooting needs. It seems to be the popular root tool now. It's pretty boss.)
4. Reboot into system, then back into recovery, and:
5. Install GApps or whatever. I like NanoDroid myself. It's the alternative to GAPPS. There are a few odd programs that just plain won't work with it yet, but the official Google apps have an annoying habit of wasting processing power on pointless background nonsense, so I prefer the alternative. Also there's an Xposed module that improves compatibility. https://nanolx.org/nanolx/nanodroid
Hmm I'll take a look at this other ROM
Currently, I have a rooted stock ROM (SuperSU ad root manager), and interested in moving to a custom ROM that is well supported
My only 2 concerns before starting are:
1) Do I need to update SuperSu
2) Do I need to update the bootloader before doing anything else (even the ROM that you suggested @FailSafeNow ? )
Anyone who was wondering what happened:
Process I used (done 2 days ago as of this post):
0) transferred all relevant files to device for the operation, backed up stuff I wanted
1) Updated bootloader to marshmallow via ODIN
2) Updated TWRP to 3.x (forgot exact version) from within TWRP
3) Wiped system + data + cache (I could have probably wiped internal memory but there wasn't much there anyways)
4) Installed Lineage OS 14.1 and Nano Gapps from within TWRP (in that order)
( full disclosure: I had wrong Gapps .zip file the first time and had to get the right one afterwards)
While I had the superSU package, I decided not to root the tablet again. I don't think I need the customization that root offers this time around especially since Lineage OS is already so lightweight compared to the stock ROM I just replaced...
Thanks all for your help!!
Over and out
Thanks all! Nice super fast tablet with amazing battery life now
bsquared938 said:
Anyone who was wondering what happened:
Process I used (done 2 days ago as of this post):
0) transferred all relevant files to device for the operation, backed up stuff I wanted
1) Updated bootloader to marshmallow via ODIN
2) Updated TWRP to 3.x (forgot exact version) from within TWRP
3) Wiped system + data + cache (I could have probably wiped internal memory but there wasn't much there anyways)
4) Installed Lineage OS 14.1 and Nano Gapps from within TWRP (in that order)
( full disclosure: I had wrong Gapps .zip file the first time and had to get the right one afterwards)
While I had the superSU package, I decided not to root the tablet again. I don't think I need the customization that root offers this time around especially since Lineage OS is already so lightweight compared to the stock ROM I just replaced...
Thanks all for your help!!
Over and out
Thanks all! Nice super fast tablet with amazing battery life now
Click to expand...
Click to collapse
I know this is a somewhat old thread. I have a T800 myself and am looking for a ROM. Want to try Lineage OS 14.1 like you have tried. Was curious as to whether you still have it and if you still liked it? If so, what version are you running now and how is your battery life compared to stock? Thanks so much! :good: