Database Info

Accidentally deleted data folder

Hello,
Couldn't find any solution in the forum.
My friend accidentally deleted data folder on sd card on his HTC Incredible. Now his phone is not going to boot at all. Are there easy ways to resolve this?
I have a little experience in rooting, flashing roms on my Desire Z. But feeling a bit scary to perform this with another phone.
Would appreciate any help.
UPDATE : I asked him again, now I'm not sure what exactly he has deleted. He is far from IT person, and unlikely that he has rooted phone or made something like that, that is why I guessed that he just deleted something from sd card. Let me try to explain behaviour of the phone:
When the phone is starting to boot, it at first shows htc screen, then screens on the pictures, then phone just freezes.
Holding Volume Down button with Power button allows to see menu, but then trying to boot recovery or just boot makes same thing as above, Trying to make Factory reset just freezes phone on the menu window.
ANY GUESS WHAT IT MIGHT BE? OR WHAT IS THE BEST THING I CAN DO?
UPD2: My friend deleted some apps (processes with names starting com...) from All applications menu in Settings in HTC Sense.

NoorBall said:
Hello,
Couldn't find any solution in the forum.
My friend accidentally deleted data folder on sd card on his HTC Incredible. Now his phone is not going to boot at all. Are there easy ways to resolve this?
I have a little experience in rooting, flashing roms on my Desire Z. But feeling a bit scary to perform this with another phone.
Would appreciate any help.
Click to expand...
Click to collapse
If he has a recent Nandroid backup then he can just flash that and let it rebuild what it needs to. Otherwise you can S-Off and root his phone, then install a custom or stock ROM as you like.
You will find more help in the HTC Incredible or HTC Incredible S forums, depending on exactly what model phone your friend has.

I think deleting any folder on sd card never cause this type of serious problem...
Unless and unless you screw in system files or boot files of your device this happens..
And as we all know that all these critical files stored in device memory so deleting anything on memory card never do this..
Just inquire him he must screwed up something in root directory of device..
we all should be polite enough to press thanks for anyone who helped US.

maybe your friend deletes data folder in which is in the internal storage.
maybo you can access you phone after a full wipe.

My suggestion is to restore with a NANDROID or flash a ROM.
Sent from my DROID2 using xda premium

gagdude said:
My suggestion is to restore with a NANDROID or flash a ROM.
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
Just full wipe! The data partition doesn't affect the rom, because rom is in system partition. The only problems are mismatches of data. Full wipe to assure the system "knows about your forced data wipe".
Sent from my iPad using Tapatalk HD

just updated the post
Thanks for reply to everyone!
I've updated the post. You can find more details now. I cannot perform anything because I cannot boot anything.
Hope you can help, will wait for your kind replies before making any radical steps.

In that case, I would recommend flashing your kernel anew.
If it doesn't help, you could try to flash a stock firmware. If this didn't help, I would probably visit a repair shop.
Hope it helped, best of luck
Sent from my E15i using xda premium
---------- Post added at 01:26 PM ---------- Previous post was at 01:19 PM ----------
Actually, this happened to me once before. Reflashing kernel worked for me: it restored my recovery.
Sent from my E15i using xda premium

Cannot boot into recovery
Gantar said:
In that case, I would recommend flashing your kernel anew.
If it doesn't help, you could try to flash a stock firmware. If this didn't help, I would probably visit a repair shop.
Hope it helped, best of luck
Sent from my E15i using xda premium
---------- Post added at 01:26 PM ---------- Previous post was at 01:19 PM ----------
Actually, this happened to me once before. Reflashing kernel worked for me: it restored my recovery.
Sent from my E15i using xda premium
Click to expand...
Click to collapse
As I wrote I cannot boot into recovery.
Can I flash kernel or rom using my laptop if the phone is not going to boot into recovery mode?
Repair shop is asking too much. I want to know could I do it by myself, with your help, of course.

NoorBall said:
As I wrote I cannot boot into recovery.
Can I flash kernel or rom using my laptop if the phone is not going to boot into recovery mode?
Repair shop is asking too much. I want to know could I do it by myself, with your help, of course.
Click to expand...
Click to collapse
Now that clarified it all. Of course you can flash it anew... Even in the worst situation your phone could be in, you can always flash kernels and firmwares!!!

Assuming the rooting process is same or simillar to Desire HD u could use hack ace tool to downgrade to stock rom, root and install cwm recovery.
After that you can flash any custom rom.
You can find a third party site link in this thread (marvin02's post):
http://forum.xda-developers.com/showthread.php?t=1791819&page=2

In what way? or what link?
Gantar said:
Now that clarified it all. Of course you can flash it anew... Even in the worst situation your phone could be in, you can always flash kernels and firmwares!!!
Click to expand...
Click to collapse
Thanks, Gantar.
But, your post would be a little more informative and useful if you you could explain how can I do that or give a link to this .

QUOTE=NoorBall;31362969]Thanks, Gantar.
But, your post would be a little more informative and useful if you you could explain how can I do that or give a link to this .[/QUOTE]
Excuse me? Did you check my post?
I just gave you a link to the thread and which user posted the link in that thread "to this".
Just go there, follow ALL,the instructions and you'll be flashing a fresh custom rom in no time.
EDIT: Ok since you seem not to have read my post, here's the direct link as posted by marvin02 in the thread:
Look here
Link found on attn1's twitter.
Upper link get's you directly to a guide and tool site. From then on,please read and follow all procedures step by step.

You need to clarify the model. Is it Incredible or Incredible S?
In case of Incredible S, look here:http://forum.gsmhosting.com/vbb/f475/medusa-box-flasher-v1-0-6-more-htc-via-usb-added-1469331/ Try in both cases, there's nothing you can lose!
You probably know this, but anyway...http://www.droidforums.net/forum/droid-incredible-faq/42039-how-hard-reset-htc-droid-incredible.html
Hope I helped you. I'll keep my fingers crossed for you
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
bobix86 said:
QUOTE=NoorBall;31362969]Thanks, Gantar.
But, your post would be a little more informative and useful if you you could explain how can I do that or give a link to this .
Click to expand...
Click to collapse
Excuse me? Did you check my post?
I just gave you a link to the thread and which user posted the link in that thread "to this".
Just go there, follow ALL,the instructions and you'll be flashing a fresh custom rom in no time.
EDIT: Ok since you seem not to have read my post, here's the direct link as posted by marvin02 in the thread:
Look here
Link found on attn1's twitter.
Upper link get's you directly to a guide and tool site. From then on,please read and follow all procedures step by step.[/QUOTE]
I'm not sure about this, bobix. The site explicitly mentions the supported devices and there's no Incredible...

Gantar said:
I'm not sure about this, bobix. The site explicitly mentions the supported devices and there's no Incredible...
Click to expand...
Click to collapse
Big whoops for meh,sorry looks like i was the one not reading (at least not paying attention when reading), mixed up incredible with inspire. Appologies.

bobix86 said:
Big whoops for meh,sorry looks like i was the one not reading (at least not paying attention when reading), mixed up incredible with inspire. Appologies.
Click to expand...
Click to collapse
Hehehe, whatever...

bobix86 said:
Big whoops for meh,sorry looks like i was the one not reading (at least not paying attention when reading), mixed up incredible with inspire. Appologies.
Click to expand...
Click to collapse
Hehe, I've even tried this method . Anyway I couldn't do anything because I can't turn on usb debugging mode
Tomorrow will try second method.
Sent from my HTC Vision using xda app-developers app

NoorBall said:
Hehe, I've even tried this method . Anyway I couldn't do anything because I can't turn on usb debugging mode
Tomorrow will try second method.
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Note: In fact, you don't need the debugging on. You need flash drivers instead! Kernels may be flashed even if you don't have debugging on! I write from experience

[Q] System Software not Authorized by Verzion...

I was running CM10 and reboot to recovery to flash latest and now I see:
Yellow Triangle with exclamation point.
System software not authorized by Verizon Wireless has been found on your found.
Please turn off your phone and go to nearest Verizon Wireless store for help.
Any suggestions would be GREATLY appreciated!
Anthony

awmobjects said:
I was running CM10 and reboot to recovery to flash latest and now I see:
Yellow Triangle with exclamation point.
System software not authorized by Verizon Wireless has been found on your found.
Please turn off your phone and go to nearest Verizon Wireless store for help.
Any suggestions would be GREATLY appreciated!
Anthony
Click to expand...
Click to collapse
Well I Odin'd stock.vzw_root66...waiting now for it to finish.

awmobjects said:
Well I Odin'd stock.vzw_root66...waiting now for it to finish.
Click to expand...
Click to collapse
It rebooted and stuck for over 5 minutes....I stopped and now repeating the Odin.

Looks like you got it figured out. They call that a soft brick. It happened to me.

its called not unlocking your bootloader before flashing custom firmware on your device. my suggestion is to read the guides stickied around here before your soft brick turns into a hard brick!

Are you saying that the Rom runs ok but when you goto recovery you get the triangle? i was reading something about how the stock recovery can be re flashed by accident in some situation, try odin recovery again?

jmclaren7 said:
Are you saying that the Rom runs ok but when you goto recovery you get the triangle? i was reading something about how the stock recovery can be re flashed by accident in some situation, try odin recovery again?
Click to expand...
Click to collapse
Nope. What he did is exactly what droidstyle said. He didn't unlock his bootloader which is the first step you should take after rooting your phone if you are going to be playing with any ROMs.

Brian Gove said:
Nope. What he did is exactly what droidstyle said. He didn't unlock his bootloader which is the first step you should take after rooting your phone if you are going to be playing with any ROMs.
Click to expand...
Click to collapse
I think he had to have his bootloader unlocked to flash the Rom in the first place. My guess would be that he relocked it at some point.
Sent from my SCH-I535 using xda premium

HHF2 said:
I think he had to have his bootloader unlocked to flash the Rom in the first place. My guess would be that he relocked it at some point.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
its a possibility, but the point is the bootloader was locked when updating.

HHF2 said:
I think he had to have his bootloader unlocked to flash the Rom in the first place. My guess would be that he relocked it at some point.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
If CM10 is anything like Synergy it does a check for the bootloader being unlocked and if it is locked still it skips installing the kernel. The rest of it goes along fine.

Brian Gove said:
If CM10 is anything like Synergy it does a check for the bootloader being unlocked and if it is locked still it skips installing the kernel. The rest of it goes along fine.
Click to expand...
Click to collapse
That is exclusive to Synergy. You can thank Eschelon for that..
Sent from my SCH-I535 using xda premium
---------- Post added at 04:38 PM ---------- Previous post was at 04:35 PM ----------
Be careful. The Ez unlock app on the market is not working properly. It will unlock you but it wont stick. Revert to version 1.2 until 1.3 and 1.4 are fixed. He has posted a link under the app description to 1.2.
Sent from my SCH-I535 using xda premium

drbveb88 said:
That is exclusive to Synergy. You can thank Eschelon for that..
Sent from my SCH-I535 using xda premium
---------- Post added at 04:38 PM ---------- Previous post was at 04:35 PM ----------
Be careful. The Ez unlock app on the market is not working properly. It will unlock you but it wont stick. Revert to version 1.2 until 1.3 and 1.4 are fixed. He has posted a link under the app description to 1.2.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
this is also noted in my guide

how do i get un soft brick it than i stuck in this to.....

MLGxHEMANx said:
how do i get un soft brick it than i stuck in this to.....
Click to expand...
Click to collapse
Section 6 of my guide.

what happens if it does work ???
---------- Post added at 02:28 PM ---------- Previous post was at 01:50 PM ----------
ok so it worked and thank you so much for the help but i want to know how to just root my phone and tweak my opts. u have a step by step let me know i do have the samsung galaxy s3

MLGxHEMANx said:
what happens if it does work ???
---------- Post added at 02:28 PM ---------- Previous post was at 01:50 PM ----------
ok so it worked and thank you so much for the help but i want to know how to just root my phone and tweak my opts. u have a step by step let me know i do have the samsung galaxy s3
Click to expand...
Click to collapse
Section2 of my guide.

droidstyle said:
Section2 of my guide.
Click to expand...
Click to collapse
Man. Don't they teach these kids how to read these days. You can lead them to water but can't get them to drink. :laugh:

softbrick Note 2
fearjego said:
Looks like you got it figured out. They call that a soft brick. It happened to me.
Click to expand...
Click to collapse
Okay I am a NUBE. I ran casual and then odin everything worked good. ThenI started getting errors when i was opening apps. So I was going to go back to stock. I ran oden again, this time using the bootloaderbaseline.tar 1,030K file. Now I am getting system software not authorized by verizon wireless found on your phone.
Now when I hook up to the usb cable it will not recognize to try and reload the bootloader.
any suggestions... Thanks again.

Try the Note 2 forums here: http://forum.xda-developers.com/forumdisplay.php?f=1886, they will probably be a lot more helpful. This is the Verizon Galaxy S3 forum.

Only stock boot.img works

Hey people, you brainiacs seem to be my last hope.
Been flashing Saturn III on my SV with TWRP and flashed, as the dev stated to do, the boot.img in fastboot.
After rebooting, it stucked on the HTC-Logo with white background till i removed the battery.
Then I tried flashing back the stock boot.img Link: ht tp://fs1.d-h.st/download/00084/DMf/boot.img
With that one it boots n all works fine but the WLAN.
So yeah.. all devs tell to flash the boot.img to get WLAN to work, but if I do so, the whole phone wont start anymore.
Already tried with Saturn III and "my slim rom" from this site.
Here are my phone specs:
K2_U PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.18.40a.00.05
OpenDSP-v13.2.0268.0620
OS- (with the stock boot.img it shows the OSrev)
eMMc-boot 1024
What I would need is a 4.1.2 OS, stock or slightly modded
Has somebody got any solution for me?
Alot thanks in advance

Strange, as you are S-On, you must flash the boot.img.
You can try to use the boot.img, you will find in this thread.

Thanks for the fast reply.
Yeah, pretty strange..
Tried that boot.img - same effect.
want me to flash that kernel's .zip too?
forgot to tell you: Ofc I'm HTCDev unlocked.

fwaqo said:
Thanks for the fast reply.
Yeah, pretty strange..
Tried that boot.img - same effect.
want me to flash that kernel's .zip too?
forgot to tell you: Ofc I'm HTCDev unlocked.
Click to expand...
Click to collapse
You fastboot flashed the boot.img?
!#quote my post if you want to get my attention more quickly

russellvone said:
You fastboot flashed the boot.img?
Click to expand...
Click to collapse
yeah i did.

And explain in a little more detail of what the exact issues are, we will be able to assist you better.
Just so I can get a better grasp(visualization) of what's going on.
!#quote my post if you want to get my attention more quickly

You already did the OTA to 422, as i see on your hboot.
Maybe there is the problem.
But if stock kernel boots, but only wifi not working, try to flash this zip from recovery (boot.img for fastboot).
It's stock k2u kernel and the needed libs for Wifi.

russellvone said:
And explain in a little more detail
Click to expand...
Click to collapse
hmmm.. what else could i tell you..
Flashing works all fine, i get success when i'm flashing a ROM and sucess when flashing the boot.img via fastboot.
The only thing is when I'm flashing the boot.img of the ROMs, the device won't boot and only show the HTC-logo on white background and never boot (waited a hour already).
The boot.img that i linked to seems to be the only one thats working.. (maybe someone could have a look on what makes that one so special?)
Result in usint that working boot.img on the ROMS is a non-working WLAN.
Please tell me if there is any other specific thing you need to know, as I dont know anything else to write atm.

You flashed a 4.2 rom? Or a 4.1?
!#quote my post if you want to get my attention more quickly
---------- Post added at 02:54 PM ---------- Previous post was at 02:45 PM ----------
Do me a favor
Go into twrp recovery and wipe
System
Cache
Data
Dalvik cache
Then flash rom again
Then reboot bootloader
Then flash the boot.img from inside the ROM
fastboot flash boot boot.img
and reboot....
!#quote my post if you want to get my attention more quickly

Isn't Saturn III based on 4.1.2??? Wouldnt that cause a conflict with 4.2.2 since the kernel is found in the boot.img? Like trying to crossbreed a dog and a cat?
Sent from my C525c using XDA Premium 4 mobile app

russellvone said:
You flashed a 4.2 rom? Or a 4.1?
Click to expand...
Click to collapse
I'm running old.splatterhand's Saturn III ROM which is 4.1.2 afaik.
Tried the kernel + boot.img you linked me, old.splatterhand. Still stuck on the HTC logo...
I'm at the end of my ideas..

I'm skimming through these right now cuz I'm at work still ha!
Sent from my C525c using XDA Premium 4 mobile app

---------- Post added at 02:54 PM ---------- Previous post was at 02:45 PM ----------
Do me a favor
Go into twrp recovery and wipe
System
Cache
Data
Dalvik cache
Then flash rom again
Then reboot bootloader
Then flash the boot.img from inside the ROM
fastboot flash boot boot.img
and reboot....
!#quote my post if you want to get my attention more quickly

Just do what is wrote in post 7, od use fm to copy modules from the zip.

Modding.MyMind said:
I'm skimming through these right now cuz I'm at work still ha!
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm at work too! Lol
!#quote my post if you want to get my attention more quickly

russellvone said:
do me favor
Click to expand...
Click to collapse
Did that now.. still hangs at the HTC-Logo.
I already tried the kernel of post #7.

@russellvone @old.splatterhand
Correct me if I am wrong. Just going on a hunch. Saturn III is based on 4.1.2. @fwaqo is currently on 4.2.2. So would he not need to downgrade in a sense as far as the necessary partitions (images) would be needed in order for this Rom to comply without complications? Mainly, thinking on the matter of the kernel which is found in the boot.img which is technically a build for the 4.1.2 and not 4.2.2...... Just throwing something up in the air. Take it or bash it. Either way, I still love you guys HAHA!
Sent from my C525c using XDA Premium 4 mobile app

It may be possible that you received an updated radio with 4.2.2?
The radio may not be compatible?
Why not stay on 4.2.2 rom?
!#quote my post if you want to get my attention more quickly
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
Modding.MyMind said:
@russellvone @old.splatterhand
Correct me if I am wrong. Just going on a hunch. Saturn III is based on 4.1.2. @fwaqo is currently on 4.2.2. So would he not need to downgrade in a sense as far as the necessary partitions (images) would be needed in order for this Rom to comply without complications? Mainly, thinking on the matter of the kernel which is found in the boot.img which is technically a build for the 4.1.2 and not 4.2.2...... Just throwing something up in the air. Take it or bash it. Either way, I still love you guys HAHA!
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've updated(we all have) with OTA and are still able to flash "downgraded" ROMs with out issue, as long as we flash the correct boot.img.
I think it's possible that maybe he received an updated radio that might interfere with the booting process???
!#quote my post if you want to get my attention more quickly

Well, then the solution to the radio would be to grab his previous one from his previous ota and flashed that radio and redue the process...
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 05:18 PM ---------- Previous post was at 05:16 PM ----------
If he doesnt have it them I'm sure somebody has to..... I have mine
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 05:20 PM ---------- Previous post was at 05:18 PM ----------
russellvone said:
It may be possible that you received an updated radio with 4.2.2?
The radio may not be compatible?
Why not stay on 4.2.2 rom?
!#quote my post if you want to get my attention more quickly
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
I've updated(we all have) with OTA and are still able to flash "downgraded" ROMs with out issue, as long as we flash the correct boot.img.
I think it's possible that maybe he received an updated radio that might interfere with the booting process???
!#quote my post if you want to get my attention more quickly
Click to expand...
Click to collapse
Now that I think about it.... My previous question was illogical since I have done this myself.... Guess work jumbled me up some lol. Oh well. Can't win them all.
Sent from my C525c using XDA Premium 4 mobile app

I flashed back from 4.2.2 to 4.1.2 cause I like the design of 4.1.2 alot more. But I can try if it works with a 4.2.2 custom rom and it's boot.img. Is there any stable rom already?

[ROM][4.4.3][KTU84L][FLO] Stock ROM with Root *Odexed and DeOdexed*

Due to mine having issues with flashing in TWRP I encourage you all to grab @scrosler update from here:
http://forum.xda-developers.com/showthread.php?t=2771012

Nice work sir.
Thanks for this.
Sent from my VS980 4G using Tapatalk

PSA: somewhere along the line I was smart enough to derp up the root part. I tested via adb shell and it worked so I must have missed something when integrating it.
I'll fix the whole thing soon. in the mean time just flash SuperSU after you flash the ROM: http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip

Installing now..thank you!
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 02:29 AM ---------- Previous post was at 02:00 AM ----------
Bootloop... Even after flashing SuperSU, clean install
Sent from my Nexus 7 using XDA Premium 4 mobile app

Nice. Flash this on both mine & my wife's N7's
Sent from my XT1060 using Tapatalk

Anyone flashed this in twrp?
Sent from my Nexus 7 using Tapatalk

matt4321 said:
I'm sure we are all aware that 4.4.3 hit only a few hours ago!
I've been spending the past hour or so getting into an update zip and rooted and well, here it is!
IMPORTANT:
TWRP my recovery of choice did not work when flashing this, I cannot work out why (I think it's a TWRP issue with the new Android)
However I swapped over to Philz recovery and it flashes flawlessly. Please report if this works with CWM or other recoveries.
This odexed! de-odexed is coming
Download: http://d-h.st/c6J
I may have derped root it worked for me but when testing another flash it failed, if you have problems flash this: http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip
Enjoy
Click to expand...
Click to collapse
FYI: TWRP has nothing to do with what issue you may be having in regards to flashing. I have no problem with my stock rooted ROMS. Will flash on TWRP just fine. If you have an issue post the error and I can help you troubleshoot it. More than likely its bad binaries or something. Some recoveries are certainly more picky than others.
Also, you should post the device type so people dont try to flash this on the wrong version of Nexus 7 2013. There are a couple models.

scrosler said:
FYI: TWRP has nothing to do with what issue you may be having in regards to flashing. I have no problem with my stock rooted ROMS. Will flash on TWRP just fine. If you have an issue post the error and I can help you troubleshoot it. More than likely its bad binaries or something. Some recoveries are certainly more picky than others.
Also, you should post the device type so people dont try to flash this on the wrong version of Nexus 7 2013. There are a couple models.
Click to expand...
Click to collapse
hey bro
weird, when I flash in TWRP it leads to a recovery reboot, never had the issue before when making any mod/rom
I've clarified it's for FLO
If you wanna upload yours that are working in TWRP I can add them to the OP or close this thread and encourage users to move over
EDIT: just noticed your thread, I'll close this, thanks for your offer to help anyway

matt4321 said:
hey bro
weird, when I flash in TWRP it leads to a recovery reboot, never had the issue before when making any mod/rom
I've clarified it's for FLO
If you wanna upload yours that are working in TWRP I can add them to the OP or close this thread and encourage users to move over
Click to expand...
Click to collapse
I will download yours and take a look. I have some free time. I bet its binary related or some oddity in the script.
No need to add mine to the OP. I uploaded and started a thread of my own. Sorry, hope I didint offend But when I saw that yours had issues I figured I would just upload what I had. I also have no issues with root.
You can certainly link to my thread in your OP if you want. Dont feel like you have to close your thread. Its up to you.

Installing Official LineageOS on SM-G900V

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