Related
ok guys here is an .apk to get cwm recovery onto the moto atrix2. make sure your rooted and then just download the .apk and install. AS USUAL USE AT YOUR OUN RISK! this is for experimental use only if you dont know what your doing plz dont use you can and most likely will brick your device!!!
Installed! No problems so far!
Sent from my mAtrix2!!
Went right into blue cwm. This is great news and a start! Thanks!
Sent from my mAtrix2!!
Quick question to the OP. Have you modified this to work with the A2? If not we've been down this road already and there will be consequences if you try to perform a recovery from a backup with this
http://forum.xda-developers.com/showthread.php?t=1329701
We have asked developer nitroglycerin33 to make us our own bootstrap that works and here is the link
http://forum.xda-developers.com/showthread.php?t=1346977
Installed no problems, went right into cwm!!!!
Sent from my MB865 using XDA Premium App
THIS IS JUST TO GET CWM RECOVERY ONTO THE ATRIX2 BOOTLOADER IS STILL LOCKED DO NOT TRY AND FLASH USING IT made a backup going to pull the files that the backup made to see if we can get the bootloader unlocked
Its still a start.
Sent from my mAtrix2!!
going to be playing with this all day today hopefully will have some good news in a little while
htcman724 said:
going to be playing with this all day today hopefully will have some good news in a little while
Click to expand...
Click to collapse
Sounds good!
Sent from my mAtrix2!!
Man I'm just trying to save you some work. Please take a look at the links I posted and we have our own bootstrap listed in the second link that was modified specifically for the A2
Take a look in the bootloader unlock post that will catch you up on where we are right now. Not trying to discourage you as we can use all the help we can get.
Glad to have you here and knowing you are willing to lend a hand I just don't wanna see some noobs using this thinking everything is working and end up bricking their phones because right now we have NO way of getting back to stock with a FXZ yet.
i'm with you i'm going to edit my post.
What is link ti new thread? Those links you provided are dated.
Sent from my mAtrix2!!
Nice! We're getting closer
holeshot77 said:
What is link ti new thread? Those links you provided are dated.
Sent from my mAtrix2!!
Click to expand...
Click to collapse
They're dated cause we're at a stand still for right now until we can get the bootloader unlocked and a working FXZ. Please read them and you will understand.
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
htcman724 said:
i'm with you i'm going to edit my post.
Click to expand...
Click to collapse
Glad we have some more help, the more the merrier!!!!
He said he started a new thread. Wanted to follow that one too.
Sent from my mAtrix2!!
Guys as JRW 28 has said.
This has been tried and done with fatal issues. Until nytroglcerin33 gets the official CWM package updated, there is not much I would try with this, we have done backups and restores, as well as attempted a flash or two with NO SUCCESS.
I am not trying to be a pain here, but there are some of us who have been working on these things for almost two months since this phone came out, try a search in the Atrix2 section next time as there is a thread already about this, and until we get the bootloader unlocked we are going to have very limited abilities on this phone to develop, if you want to help out someplace go jump in there.
Bootloader unlock thread:
http://forum.xda-developers.com/showthread.php?t=1328714
I got ahead of myself. Sorry Jim! Was excited for a minute.
Sent from my MB865 using XDA App
holeshot77 said:
I got ahead of myself. Sorry Jim! Was excited for a minute.
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
No worries, that was not aimed at anyone, it was more in genral, so that anyone who reads this sees that this is a very slippery slope right now, we have had at least 2 people that we know of, who bricked their phones using the / a similar method that was in the OP here.
jimbridgman said:
This has been tried and done with fatal issues. Until nytroglcerin33 gets the official CWM package updated, there is not much I would try with this, we have done backups and restores, as well as attempted a flash or two with NO SUCCESS.
Click to expand...
Click to collapse
I wouldn't say I have had no success... I'm able to backup and restore system and data using that atrix 2 recovery. In fact, the bionic one worked as well but I only used it a couple of times.
I've been using it to go back and forth between 55.11.16 and 55.13.16, 8 or 9 flashes so far without a brick.
inb4 next flash bricks my phone
I think we should have our moderator swoop in and sticky the important things. It seems were not getting much love from him around here. It's kind of an annoyance to me that topics fall back a page or two then are reintroduced as a new thread a week later. Just saying.
Welcome to the Official CM10.2 discussion thread for Skyrocket, Hercules and Exhilarate devices as supported by Team Chopsticks.
Please search the thread before posting, there are numerous work arounds and fixes for some sporadic issues (such as gallery crashing) that are already documented somewhere in this mess.
Please read our blog for known issues and installation instructions - make sure you have properly followed directions before posting about an issue.
Status - August 30th, 2013:
Official nighlies have begun, please be mindful that you are using a 4.3 compatible recovery when flashing. If in doubt, please ask the developer of the recovery you are using for clarification.
Skyrocket Official:
http://forum.xda-developers.com/showthread.php?t=2412651
Hercules Official:
http://forum.xda-developers.com/showthread.php?t=2412652
Known issues:
http://www.teamchopsticks.org/p/cm102-release-notes.html
car vs driver said:
The leading issue holding us back from releasing an official build (and nightlies) is the known /data & /cache corruption bug. This has been discussed heavily in may threads at this point so I'll be brief ... it appears to be recovery related, in that the filesystem is not being setup properly with recoveries build for CM10.1. At this point, we have engaged several folks from the CM team and have been hard at work to come up with a valid, complete solution. Progress is being made daily.
Click to expand...
Click to collapse
I've heard there is a TWRP 2.6.0.2 floating around somewhere. I haven't been able to find it though. I'm wondering if there might be anything in there to possibly address it?
dotnetguyaz said:
I've heard there is a TWRP 2.6.0.2 floating around somewhere. I haven't been able to find it though. I'm wondering if there might be anything in there to possibly address it?
Click to expand...
Click to collapse
Mikeyman and I are looking through their code now to see if we can build a version to solve the problem. Funny, because I was just talking to someone in IRC about us only supporting CWMR ... :angel: :silly:
Back to cwm, oh hell no. Lol
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
mtdew said:
Dave you know good and well I won't go back to cwm lol.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Oh quit yer whining... (But I'm with ya. I ABHOR CWM)
---------- Post added at 01:06 PM ---------- Previous post was at 01:00 PM ----------
car vs driver said:
Mikeyman and I are looking through their code now to see if we can build a version to solve the problem. Funny, because I was just talking to someone in IRC about us only supporting CWMR ... :angel: :silly:
Click to expand...
Click to collapse
Meh. If you can't get TWRP working then I guess if we *have* to use CWM. But, like mtdew, we WON'T be happy about it! LOL
dotnetguyaz said:
Oh quit yer whining... (But I'm with ya. I ABHOR CWM)
---------- Post added at 01:06 PM ---------- Previous post was at 01:00 PM ----------
Meh. If you can't get TWRP working then I guess if we *have* to use CWM. But, like mtdew, we WON'T be happy about it! LOL
Click to expand...
Click to collapse
+1
You guys realize we could just pm dees-troy and let him in on the situation I'm sure he'd be happy to help.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
You guys realize we could just pm dees-troy and let him in on the situation I'm sure he'd be happy to help.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
We been in touch with him on IRC today.
Sent from my SAMSUNG-SGH-I727 using XDA Premium 4 mobile app
So, i'll ask again. Which recoveries got problem with FS corruption? just TWRP?
I've tested 10.2 only with CWM but it was working...
Found bug. Lockscreen shortcuts don't save .. they are still default.
Snoop05 said:
So, i'll ask again. Which recoveries got problem with FS corruption? just TWRP?
I've tested 10.2 only with CWM but it was working...
Found bug. Lockscreen shortcuts don't save .. they are still default.
Click to expand...
Click to collapse
ALL OF THEM your taking a risk it may not have happened yet but if it does nobody wants to hear it because you were warned earlier.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Guys I'm all for wanting 4.3 and being excited, I've been compiling pa. When our device maintainers say something though I listen. I have limited knowledge in how these guys do what they do but if they say don't flash with our current recoveries then don't do it they are running this by the proper channels I'm confident it will be resolved in due time. Talk to devs like @gs2usr and see if he can at least include the recovery.IMG built with the compiles and put a quick tut on his op.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I'm just gonna hop in here and say thank you to the devs
whosgotlag said:
I'm just gonna hop in here and say thank you to the devs
Click to expand...
Click to collapse
Agreed!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
can you describe me that FS corruption problem? .... ROM will stuck on boot .... blah blah
FS corruption ---- so reformat partition with corrupted FS
or will it do more? break partition table?
what i need to do after that?
reflash with odin? or got a brick in pocket?
Snoop05 said:
can you describe me that FS corruption problem? .... ROM will stuck on boot .... blah blah
FS corruption ---- so reformat partition with corrupted FS
or will it do more? break partition table?
what i need to do after that?
reflash with odin? or got a brick in pocket?
Click to expand...
Click to collapse
When it hit me I did a factory wipe and full reset/wipe of all partitions and then reflashed and restored /data from a Nandroid backup.
Sent from my Nexus 7 using Tapatalk 4
rpr69 said:
When it hit me I did a factory wipe and full reset/wipe of all partitions and then reflashed and restored /data from a Nandroid backup.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I did this too (except internal sd) and got blank screen after the nandroid. Waited ten minutes, hard rebooted, waited another five or so and it finally sorted itself out. That was a scary fifteen minutes!
so reflash complete FW with Odin is best way? -- to hardly re-flash all partitions
right now i compiled new one, with more cherrypicking, lets try it out
Sorry, when I said wipe all partitions I meant system, data and cache/dalvik-cache, not *every* partition, I guess I should have been more clear.
Would it be safe to manually flash the latest recovery from Koushik and then use that to flash the ROM?
Sent from my Nexus 7 using Tapatalk 4
rpr69 said:
Sorry, when I said wipe all partitions I meant system, data and cache/dalvik-cache, not *every* partition, I guess I should have been more clear.
Would it be safe to manually flash the latest recovery from Koushik and then use that to flash the ROM?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
What latest recovery?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Starymari said:
What latest recovery?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Excellent question. I've been trying to find one for 2 hours with no luck...
edit: of course...it's built during the ROM build, not CWM of course, but I should be able to use it to flash CM, no?
Welcome to d2kat!
these will be weekly builds of cm11 by tvall and myself.
there isnt much to be said about these builds execpt for what is broken on CM will be broken here.
any ROM/KitKat related questions can be asked in the Q&A here:
ROM:https://mega.co.nz/#!wBRyVQQZ!IYvnu2KwJihG86115meP8EvaIQVcgoRyMKvtuMMcvHU
Gapps:http://www.mediafire.com/download/a84xzwn0w5lplhz/pa_gapps-modular-full-4.4-20131111-signed.zip
Thanks:
@tvall: builds
@LeslieAnn: build server
Cyanogenmod: everything
apparently we are starting again. taking post #2
so, this thread is apparently just for my builds. since i already made it clear that i am not committed to actively working on the d2vzw, I'm assuming its to force the other devs into making their own threads for their roms.
quick faq:
I will probably keep building these for a while to keep people satisfied until cm releases official nightlies. no promises though
my builds will be given to cammykool, untested for him to post. I do not own a d2vzw, and cannot afford to go buy one. buy me one, and I'll be able to test and fix things.
my builds will almost always be only cm code, what they have pushed to github and fixes waiting to be merged. I don't feel like fixing bugs myself. the devs that actually own this device can do that, and I'll merge it into my builds as needed.
cammy wants me to push out new builds on a weekly basis. i have no idea why he likes my builds so much, but i can handle weekly or more frequent experimental untested builds
Re-subscribed Thank you, you guys are awesome!!!
Flashing as I type this! Thank you so much!
Thanks!
SovietKommando said:
Flashing as I type this! Thank you so much!
Click to expand...
Click to collapse
Let us know how it is! I'd love to try it out but I can't mess with my phone atm
Sent from my SCH-I535 using Tapatalk
Skyrocketing said:
Let us know how it is! I'd love to try it out but I can't mess with my phone atm
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Seems that Wi-Fi is broken, at least it is for me. This is on a clean flash.
SovietKommando said:
Seems that Wi-Fi is broken, at least it is for me. This is on a clean flash.
Click to expand...
Click to collapse
anything else?
tvall said:
anything else?
Click to expand...
Click to collapse
SD card was also still broken for me (I'm thinking it might just be my SD card at this point, I'm gonna try out another one), but everything else seemed to work fine.
I thought in the other thread I saw something about CM11 not flashing with TWRP... confirm/deny with this build?
This rom really needed this fresh new start Also, what is different from this build in the op and the 2013-11-13-unofficial by sspencer? Anything fixed in it that isnt in the sspencer build? Thanks
Gonna need a lot more clarity in the OP or else this thread will be exactly the same as the last one. I'll start by adding instructions:
THESE BUILDS ARE NOT 100% OPERATIONAL.
-They boot, I flashed it last night and everything worked for me (front camera, SD card, WiFi..etc) browser FC'd on me once but that might have been something else.
-You will probably get 2 galleries, not sure why or which one to disable, I didn't get that far.
Flash instructions:
-YOU MUST USE CWM, TWRP IS BROKEN
-Factory reset
-Wipe Dalvik / Cache
-Wipe system
-Wipe Data
-Flash ROM
-Boot up, let it sit for a minute
-Reboot recovery and flash the GAPPs in OP
-Reboot and sign in
-Profit.
These were pretty much the instructions last night, and the ones I followed and everything worked fine for me.
tvall said:
anything else?
Click to expand...
Click to collapse
I literally just flashed back to 4.3.1 but I ran this build for the past 3 days including the version from yesterday and today. It is seriously close to being able to be used as a DD. TVall, it seems like you are developing this until CM releases so I thought I'd say what wasn't working for me. I did not have the SD card problem but i know many do. I did have these things not working...
1. Certain apps would not reinstall from the Play Store. When I tried it said USB Storage not found
2. When launching Google+ it says network not found retry. I can view Facebook and other apps that have to get on network just fine.
3. Unable to connect to XDA using tapatalk, although I'm not sure that one is rom related as I am now back on 4.3.1 and it is still hit or miss.
4. Overall seems kinda sluggish and i'm sure that will get ironed out as the rom gets more polished. I don't necessarily mean the OS is sluggish but apps are and opening apps takes a little longer
I will probably flash back later or tomorrow as I already miss the launcher but nothing too serious here for me. Like I said it is extremely close to DD status right now and I really liked the ROM and appreciate all of your hard work.
All in all seemed OK expect WiFi and SD card issue, that's the only things I noticed. And (beepea206) yes that is true about the not flashing it with TWRP.
Sent from my SCH-I535 using XDA Premium 4 mobile app
beepea206 said:
I thought in the other thread I saw something about CM11 not flashing with TWRP... confirm/deny with this build?
Click to expand...
Click to collapse
issue was fixed in twrp 2.6.3.1 or 2.6.3.2, i don't remember. twrp 2.6.3.3 fixed bugs in .1.
at the time of this post, i believe 2.6.3.0 is the most recent build officially available for the d2vzw. this is why i prefer the nexus line
joedajoester said:
This rom really needed this fresh new start Also, what is different from this build in the op and the 2013-11-13-unofficial by sspencer? Anything fixed in it that isnt in the sspencer build? Thanks
Click to expand...
Click to collapse
this build is made blindly by me. sspencer actually owns a d2vzw and can test and fix things. all i do is build and upload. his builds will be mostly working usually. mine will be just cm and fixes they make.
Download link not working
The download link for the ROM reads this when clicked:
"The file you are trying to download is no longer available.
This could be due to the following reasons:
The file has been removed because of a ToS/AUP violation.
Invalid URL - the link you are trying to access does not exist
The file has been deleted by the user."
I'm running the 4.4 from the older post before this one and would really like to update considering the front camera currently doesn't work on my ROM and may fix a few things. I've the link on multiple browsers and even installed the mega extension and it still doesn't work. Could you reupload?
ArcticSpyder said:
The download link for the ROM reads this when clicked:
"The file you are trying to download is no longer available.
This could be due to the following reasons:
The file has been removed because of a ToS/AUP violation.
Invalid URL - the link you are trying to access does not exist
The file has been deleted by the user."
I'm running the 4.4 from the older post before this one and would really like to update considering the front camera currently doesn't work on my ROM and may fix a few things. I've the link on multiple browsers and even installed the mega extension and it still doesn't work. Could you reupload?
Click to expand...
Click to collapse
If you read the forums this build is "dead". So yes link no longer available.
Sent from my SCH-I535 using XDA Premium 4 mobile app
I made a new build and gave it to cammy. Guess he didn't post. Ill post a link later
tvall said:
I made a new build and gave it to cammy. Guess he didn't post. Ill post a link later
Click to expand...
Click to collapse
All you guys are doing amazing eork on this. ~thumbs up~
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 09:26 PM ---------- Previous post was at 09:26 PM ----------
nickhex89 said:
All you guys are doing amazing eork on this. ~thumbs up~
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Work not eork
Sent from my SCH-I535 using XDA Premium 4 mobile app
Tvall you still gonna post your build?
Sent from my SCH-I535 using Tapatalk
AS the name implies this is a stock rooted Android 5.1 - LMY47O Lollipop ROM!
The one we have been waiting for!
Features
100% Stock
Rooted / Powered by SuperSU by @Chainfire!
Busybox
No other edits
FSTRIM on install
Notes:
Should update bootloader. It is attached as a ZIP file but is not flashable! You need to fastboot flash it. For those in windows I have batch file in there along with ADB and fastboot.
First boot is a loooooooooooong time! About 5 to 7 minutes!
You must be on Latest TWRP to enjoy this ROM. No other recoveries supported however they may work.
Troubleshooting
If you get no status bar reboot to recovery and clear all cache. If that doesnt work try flashing the factory image then flash TWRP again and then this ROM.
Getting Symlinks failed during install? Make sure /system is unchecked in TWRP mounts
Problems with internal storage? Look at THIS POST for fix by @freakzapster
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
[/CENTER]
Sharing Policy
You are free to use this ROM or any part of this ROM any way you like as long as you give proper credit!
Consider this your permission! Please do not PM me asking if its OK to build off this ROM. Permission granted!
Hit Thanks!
One for the road!
Dont forget to hit thanks :angel:
Maybe @GROGG88 will make a bootloader that can be flashed in recovery :highfive:
Is it ok to dirty flash , coming from latest CleanROM?
skn-xda said:
Is it ok to dirty flash , coming from latest CleanROM?
Click to expand...
Click to collapse
Should not be an issue... However, make a nandroid back up first!
Nice to have you back and to have my tablet back on Clean rom and 5.1 as well.
scrosler said:
Maybe GROGG88 will make a bootloader that can be flashed in recovery :highfive:
Click to expand...
Click to collapse
I'm transitioning careers, buying a new home, and moving across multiple states... So, I wouldn't count on it right now.
On the positive side. This gives everyone the motivation to learn how to use fastboot... A knowledge that should precede flashing ROMs anyways. :laugh:
Thanks for this!
Please please please could someone make a recovery flashable bootloader as I don't own a PC but need to update my bootloader thanks in advance
Sent from my Nexus 7 using XDA Free mobile app
toonarmy4life said:
Please please please could someone make a recovery flashable bootloader as I don't own a PC but need to update my bootloader thanks in advance
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
+1 please. I am too stupid to make such a file
Guys, do I need to flash ROM again if I update the bootloader? Will my data be wiped?
matcho13579 said:
Guys, do I need to flash ROM again if I update the bootloader? Will my data be wiped?
Click to expand...
Click to collapse
No. No, if nexus is unlocked.
Recently updated bootloader to 04-05 ("fastboot flash bootloader bootloader-flo-flo-04.05.img") still staying on 4.4.4 KTU84P, waiting for 5.1.1+Xposed.
GROGG88 said:
I'm transitioning careers, buying a new home, and moving across multiple states... So, I wouldn't count on it right now.
On the positive side. This gives everyone the motivation to learn how to use fastboot... A knowledge that should precede flashing ROMs anyways. :laugh:
Click to expand...
Click to collapse
Thats impressive. I am going in for major surgery on Monday! This may be my last post for a while!
Could someone tell me how I can flash that new bootloader without a PC? Sorry for being a pest lol
Sent from my Nexus 7 using XDA Free mobile app
Would I have to do anything special if I already have the paid version of Stericson's busybox installed?
Thanks so much Scott for making these ROMs and good luck on your surgery!
scrosler said:
Thats impressive. I am going in for major surgery on Monday! This may be my last post for a while!
Click to expand...
Click to collapse
I hope it goes well and gets you in a better state.
scrosler said:
Thats impressive. I am going in for major surgery on Monday! This may be my last post for a while!
Click to expand...
Click to collapse
Dont worry man, youll get well very soon and back again for Clean Rom
Best wishes Scott and Grogg !!
Thanks
So has anyone managed to do this? If u have the '15 bootloader you can get TWRP up and running through safe strap. And you can install custom roms, however when trying to install the official build you get error 7 "wrong device" even though the G900V is clearly listed as a supported model on LOS website
I've tried editing out asserts as a fix for error 7 but that results in "cannot find update binary" error
Has anyone actually managed to do this yet? We should be able to do this but just need to get around stupid status error
I'm currently on an unofficial LineageOS build which has some data connectivity issues and thats the reason I need this so badly, otherwise the rom works perfectly
If you're interested ill post links on how to install my version just in case
Do as first post in this thread but change busybox installer to the one I will link below https://forum.xda-developers.com/ve...oot-method-t3561529/post71202995#post71202995
Link to my post with LineageOS and other busybox: https://forum.xda-developers.com/showpost.php?p=78390993&postcount=862
Link to my post with busybox and link to unofficial LineageOS
I think I replied to you on reddit already, but what version of TWRP do you have? Error 7 is usually fixed by updating to the latest TWRP. Also, it can be difficult to distinguish between safestrap and TWRP. This creates confusion sometimes...but I doubt that is the issue, as you already booted a custom ROM. Can you post a complete log of the installation error? To answer your first question, I have CID 15 G900V, running lineage OS. I have flashed 14.1, 15.1 and 16.0, all flash OK, no errors.
---------- Post added at 04:08 PM ---------- Previous post was at 04:02 PM ----------
Here is a basic guide on grabbing the loghttps://rootzwiki.com/topic/24120-how-to-get-a-log-from-twrp/
---------- Post added at 04:12 PM ---------- Previous post was at 04:08 PM ----------
Oh, and one more thing. What are you wiping before flashing the new ROM?
I've had some further discussion with OP on reddit. See attached screenshot.
@swiftbones74 and @Ibuprophen OP seems to indicate that he successfully flashed lineage through safestrap with a still locked bootloader. I think it is more likely that TWRP is actually already flashed and he just doesn't realize it. Any thoughts?
Edit: Sounds like this was it.
Eklondh said:
So has anyone managed to do this?.........
Click to expand...
Click to collapse
Reverse-anastomosis said:
swiftbones74 and Ibuprophen OP seems to indicate that he successfully flashed lineage through safestrap.........
Click to expand...
Click to collapse
That's a very common misunderstanding between TWRP and SafeStrap...
TWRP is the actual Recovery...
SafeStrap just looks like TWRP for a familiar look but, it's not a Recovery.
The best way to describe it is that SafeStrap boots right after the Stock Recovery and just before the Android OS.
There's no way to flash a Custom Firmware on any device (that I know of) using SafeStrap. Only something like a TW ROM can actually be flashed using SafeStrap.
I've seen allot of individuals whose managed to Soft/Hard Brick devices by doing so.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.
Thanks for the input. It turns out that he really did have TWRP, and didn't realize it.
Reverse-anastomosis said:
@swiftbones74 and @Ibuprophen OP seems to indicate that he successfully flashed lineage through safestrap with a still locked bootloader. I think it is more likely that TWRP is actually already flashed and he just doesn't realize it. Any thoughts?
Edit: Sounds like this was it.
Click to expand...
Click to collapse
You are quoting the wrong person. kEK. I don't get drunk or high enough to say I flashed anything , number 1 with safestrap and number 2 with a locked bootloader.
Sent from my mata using XDA Labs
I wasn't quoting you, I was summoning you for input, as I see you are historically very helpful. Sorry for the misunderstanding.
Eklondh said:
So has anyone managed to do this? If u have the '15 bootloader you can get TWRP up and running through safe strap. And you can install custom roms, however when trying to install the official build you get error 7 "wrong device" even though the G900V is clearly listed as a supported model on LOS website
I've tried editing out asserts as a fix for error 7 but that results in "cannot find update binary" error
Has anyone actually managed to do this yet? We should be able to do this but just need to get around stupid status error
I'm currently on an unofficial LineageOS build which has some data connectivity issues and thats the reason I need this so badly, otherwise the rom works perfectly
If you're interested ill post links on how to install my version just in case
Do as first post in this thread but change busybox installer to the one I will link below https://forum.xda-developers.com/ve...oot-method-t3561529/post71202995#post71202995
Link to my post with LineageOS and other busybox: https://forum.xda-developers.com/showpost.php?p=78390993&postcount=862
Link to my post with busybox and link to unofficial LineageOS
Click to expand...
Click to collapse
Dude some people make life really hard on them selves. The reason for your error 7 in TWRP was because you needed to update to the latest version of TWRP. That's it and it has nothing whatsoever to to with the kltevzw, it's a klte + Android thing. Try to install Oreo or higher with all the klte unified S5's on older TWRP Version and you get that error. You are 'fixing' stuff that's ain't broken bro. TWRP works fine on the g900v and has ever since 2.7 or maybe 2.9.
Sent from my mata using XDA Labs
---------- Post added at 03:35 AM ---------- Previous post was at 03:33 AM ----------
Reverse-anastomosis said:
I wasn't quoting you, I was summoning you for input, as I see you are historically very helpful. Sorry for the misunderstanding.
Click to expand...
Click to collapse
Lol sorry for my grumpiness. I've got to remember to breathe
Sent from my mata using XDA Labs
swiftbones74 said:
Dude some people make life really hard on them selves..........
Click to expand...
Click to collapse
Don't you have that Magic Wand?
LOL!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore 64.
Thanks also thanks for all of your support on this device. You and Ibuprofen are keeping the bootloader unlock thread alive!
swiftbones74 said:
Dude some people make life really hard on them selves. The reason for your error 7 in TWRP was because you needed to update to the latest version of TWRP. That's it and it has nothing whatsoever to to with the kltevzw, it's a klte + Android thing. Try to install Oreo or higher with all the klte unified S5's on older TWRP Version and you get that error. You are 'fixing' stuff that's ain't broken bro. TWRP works fine on the g900v and has ever since 2.7 or maybe 2.9.
Sent from my mata using XDA Labs
---------- Post added at 03:35 AM ---------- Previous post was at 03:33 AM ----------
Lol sorry for my grumpiness. I've got to remember to breathe
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Yeah lol, I didn't even realize that I could update TWRP. I tried once and failed then tried a month later and succeeded. We should include that in OP that you can flash latest TWRP, maybe u should get that since thats what unlocked bootloader means but yeah I'm a retard, sorry
Ibuprophen said:
That's a very common misunderstanding between TWRP and SafeStrap...
TWRP is the actual Recovery...
SafeStrap just looks like TWRP for a familiar look but, it's not a Recovery.
The best way to describe it is that SafeStrap boots right after the Stock Recovery and just before the Android OS.
There's no way to flash a Custom Firmware on any device (that I know of) using SafeStrap. Only something like a TW ROM can actually be flashed using SafeStrap.
I've seen allot of individuals whose managed to Soft/Hard Brick devices by doing so.
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.
Click to expand...
Click to collapse
Yeah lol my post is full of lies! Lies and deceit I had TWRP installed and thought it was safestrap.. We should add to the OP tho that after following this guide u can flash latest TWRP through Odin so other people don't go full retard like me hahaha