Database Users

[Q] [Help Please] LG g2 d802 No ROM / Boot Issue

see post 4

see post 4

see post 4

d802 int
Ok, so i made a rookie mistake and completely wiped my phone ready for a new install, without moving the files for the install across 1st. So now I cannot get the PC to recognise a device is plugged in to send across the cludyflexg3 rom files. I have twrp installed and can get to that with the power off/down combo on boot but this doesnt help a great deal without the files being accessible.
I can also load the updater with up and power but as the device was rooted this is picked up and it doesn't progress.
I tried IOroot and this doesnt seem to do anything either, window just closes when I hit enter. Any idea how I can flash across the rom somehow?
[as a quick update, IOroot will get to the point where it enables daemon but it just sits there waiting for the phone to respond, which it obviously won't. Is there anything I can do from within twrp to get a version of android installed? There are no recovery files I can find on the device after the wipe.
Is there really nothing I can do? I have now installed and set up adb. But my device doesnt show up with adb from any menu I use... (when using command line adb devices) and also when using adb usb command, I get "device not found"
Any help at all guys? this has been up 2 hours, I've always found this forum very helpful, but I really need my phone up and running asap as I use it for work, it is essential. Even the smallest bit of advice to at least get me to the next step would be really great. Thanks.
Could I possibly get a micro usb storage device, put the rom file on there and load it using twrp? If this is possible I may be without my phone a few days but at least it would work eventually.
Im sorry about the above posts, I tried to tidy the question and delete the previous posts but this isn't possible. Could an admin do this please, but I still need help with this issue. Please, anyone!

kye1987 said:
Ok, so i made a rookie mistake and completely wiped my phone ready for a new install, without moving the files for the install across 1st. So now I cannot get the PC to recognise a device is plugged in to send across the cludyflexg3 rom files. I have twrp installed and can get to that with the power off/down combo on boot but this doesnt help a great deal without the files being accessible.
I can also load the updater with up and power but as the device was rooted this is picked up and it doesn't progress.
I tried IOroot and this doesnt seem to do anything either, window just closes when I hit enter. Any idea how I can flash across the rom somehow?
[as a quick update, IOroot will get to the point where it enables daemon but it just sits there waiting for the phone to respond, which it obviously won't. Is there anything I can do from within twrp to get a version of android installed? There are no recovery files I can find on the device after the wipe.
Is there really nothing I can do? I have now installed and set up adb. But my device doesnt show up with adb from any menu I use... (when using command line adb devices) and also when using adb usb command, I get "device not found"
Any help at all guys? this has been up 2 hours, I've always found this forum very helpful, but I really need my phone up and running asap as I use it for work, it is essential. Even the smallest bit of advice to at least get me to the next step would be really great. Thanks.
Could I possibly get a micro usb storage device, put the rom file on there and load it using twrp? If this is possible I may be without my phone a few days but at least it would work eventually.
Im sorry about the above posts, I tried to tidy the question and delete the previous posts but this isn't possible. Could an admin do this please, but I still need help with this issue. Please, anyone!
Click to expand...
Click to collapse
if adb is not working then a usb otg would be the solution, they are used to connect usb devices(mouse/keyboard/usb drives/etc) into our phones; here is a link for reference so you know what to look for

XxZombiePikachu said:
if adb is not working then a usb otg would be the solution, they are used to connect usb devices(mouse/keyboard/usb drives/etc) into our phones; here is a link for reference so you know what to look for
Click to expand...
Click to collapse
Cheers I'll see if the supermarket has them at a half reasonable price, otherwise ebay has them for £1 delivered and I'll have to wait. Thanks for the reply and confirmation that would work though.

Can you ADB push build.prop from a stock recovery? If not I'm in trouble.

Hey all,
Long story short. I made a backup copy of my build.prop to my internal SD. I edited one line in the /system/build.prop. I rebooted. It was fine. I decided the change I made to build.prop was not necessary so I copied the backup I had on my SDCard of the original file back to /system/. My phone hangs on the "Samsung GALAXY S5 powered by Android" screen during boot.
I'm not experienced with ADB but I am technically inclined so please point out if I'm doing something wrong. I have installed the universal ADB drivers on my computer. I have installed the "Samsung USB drivers". I boot into recovery. I go to "apply update from ADB" (not sure if that is correct). I then run the command "adb devices" in Windows and it lists my device with "sideload" next to it.
I then run "adb pull /system/build.prop" and I get "error: closed". That is as far as I can get.
Any help is greatly appreciated.

taboo_ said:
Hey all,
Long story short. I made a backup copy of my build.prop to my internal SD. I edited one line in the /system/build.prop. I rebooted. It was fine. I decided the change I made to build.prop was not necessary so I copied the backup I had on my SDCard of the original file back to /system/. My phone hangs on the "Samsung GALAXY S5 powered by Android" screen during boot.
I'm not experienced with ADB but I am technically inclined so please point out if I'm doing something wrong. I have installed the universal ADB drivers on my computer. I have installed the "Samsung USB drivers". I boot into recovery. I go to "apply update from ADB" (not sure if that is correct). I then run the command "adb devices" in Windows and it lists my device with "sideload" next to it.
I then run "adb pull /system/build.prop" and I get "error: closed". That is as far as I can get.
Any help is greatly appreciated.
Click to expand...
Click to collapse
I would flash a stock rom to get the phone running again, and next time make a nandroid backup that you can restore with a custom recovery before you mess with system files.

I'm currently downloading a stock rom from a very slow source. In the 3hrs or so it's going to take to download I thought I would absolutely confirm I was buggered as it would be nice if a few ADB commands could save me.
gee2012 said:
next time make a nandroid backup with a custom recovery before you mess with system files.
Click to expand...
Click to collapse
I do certainly know better. But Samsung in their power have decided to Knox flag your device if you install a custom recovery. As such creating a nandroid backup was not an option for as long as I want my warranty. I do have Titanium backups, and I thought I was doing the right thing by making a copy of build.prop before doing anything... turns out I was wrong. But really, thanks for your concern and advice.

..

fffft said:
Three hours huh? You should talk to Santa about a faster net connection.
Click to expand...
Click to collapse
I live in Australia. We asked our government and they said yes.... then we got a new government. But in this case it's the speed of the host that was hindering. It's all elementary now anyway as the download finished. No one had replied. I flashed it. It failed. And the long and short of it is adb is now useless to me.
fffft said:
You should know this already though as a five minute search on how to use ADB would have pulled up numerous tutorials.
Click to expand...
Click to collapse
I appreciate the help. But I'd spent all day reading tutorials. Trying commands. Failing. Googling the error. Trying new commands. Failing. Googling those errors. After doing that for some time I thought it would just be more sensible to ask people that have actually had experience.
fffft said:
You're also on the wrong site if you are obsessing over the Knox flag. Yeah, it might affect your warranty. Probably not, but I'll grant that it could. So simply decide up front it you want to modify your phone or wait out your risk free warranty period.
Click to expand...
Click to collapse
So here's the thing. I don't want my cake and eat it. I will absolutely be blowing away knox. I just didn't see a point in doing it preemptively. The phone is only a couple weeks old so I decide it would be wise to at least keep my warranty until I'm happy it's rock solid and I have a good reason to lose it - nice stable Cyanogenmod I'm looking at you. Plus anything I wanted to do up to now I was able to with Towelroot and xposed. I just couldn't Nandroid.
Really. Thanks for listing the commands. As of this morning I hadn't needed to use ADB at all. I appreciate you spelling it out. I just wish I had of seen it mere minutes earlier as I would have been able to let you know if it worked. Unfortunately I didn't. But I appreciate the effort.

..

fffft said:
And you say that your firmware download speed was host limited. I just did a search for half a dozen S5 firmware builds. Found all of them widely disseminated. And as one might expect, not all of the hosts were slow..
Click to expand...
Click to collapse
I was using sammobile.com on a free account. I'm sure I could have found a faster host but I've used sammobile.com many times in the past and they've always been reliable. I'd rather wait longer and get something I trust when I'm not in a hurry than download a file that has the right name but is just from a random "megaupload" link or something.
Now regarding adb I got a lot of the information I needed through google searches. I also watched a number of videos. But here's the thing. If I were just taking the opportunity to learn about adb google-ing around would have been fine. But as the circumstances were a little dire in this situation and I've expressed that I've never used adb before and was not confident. I didn't know what I was doing or have the experience to know the implications of what I was doing. As such 1) I didn't want to take the chances of getting it wrong and screwing myself over further and 2) I seemed to have a fairly unique issue (can't boot, stock recovery, "error: close" issue).
It wasn't just about knowing the commands to use, it was about finding out whether I was even able to do what I was hoping to do from a stock recovery on an S5 (hence the title of the thread).
You're getting a little judgey, which is fine you're entitled to your opinions. But I'd ask you read my title and first post again. It wasn't about just getting the commands outright coz I was too lazy to look, it was about getting a number of questions that I didn't know the answer to due to lack of experience, and that I hadn't had directly answered through google searches. Also I never implied an urgency, it was simply a case of "I had a contingency plan in place (downloading a stock rom) but I thought I may as well ask for some advice in the time I had while waiting for it to download".
It's not as though my case was a dime-a-dozen, "answered directly a million times". It was a little more unique and I had answered many of the general questions myself and decided that my remaining hesitations are best answered by those with experience. I'm sorry that bothers you.

Plus the reason you were able to have so much success is because you have experience and knew what to look for and understood the compounding factors. I had figured your first and third command out for myself. I was missing your second and I don't know if that was my problem, but the error I was getting "error: closed" seems to have a massive lack of documentation on the internet. Not many people are talking about it and those that are pretty much just say "update abd" - I was running the latest version. That is where I was coming undone.
But if you're STILL feeling disconcerted at my efforts here is my session from yesterday right before I made this thread. This is literally only a few of the tabs I had gone through: http://i.imgur.com/WDB3qIg.png

..

I just can not understand why you're being like this man. I've been nothing but polite. But I came on here to learn. If I was doing something blatantly against the community I'd expect to hear about it, but I just wanted help. You gave me help which was awesome but every time I took it or added something to explain my reasoning for my actions you added a lecture with it.
All I was trying to put across to you was that you don't know what I did or my reasoning for asking questions. I was just hoping you could see that your initial assumption about my laziness may not have been correct. Again, I'm not trying to be a **** about this and I really was thankful for the help you gave. But it seems you're more than willing to dish out the criticism but as soon as I defend myself or talk back you in turn get your back up. But I just don't understand why you seemed so interested in making assumptions about my efforts, my internet speeds and then telling me how I should be doing everything differently.

[Hardbrick] Oneplus 2 Only fastboot, OEM and device locked.

So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
Nevertheless, i will state my problem here:
Right now, my phone and my limited knowledge about it have come to an dead end. with the help of online tutorials and so on, (I have downloaded almost 40 gigabytes worth of space to do stuff to my phone), i was able to only get the fastboot mode to work again.
It started with me uninstalling a system app from google (I don't know which one exactly, but i had the resurrection remix 5.69 or something like it, and in that ones system app remover it was one of the lowest google apps). I don't know if this is important, but at the time i did that i was in plane mode.
After some time i ran into some loading issues with games and restarted my phone. the first time i got in, i booted up normally and could do my pattern normally, but then there was only a black screen and i could pull that info bar thing down. as soon as i wanted to open the settings, everything froze and i decided to restart the phone. Once it was shut down i then got greeted by a bootloop which i aborted by shutting down after about 3 minutes. then nothing was working anymore, so i wanted to see if the fastboot mode was still available. it was, but after shutting down from that and trying again ( just to be sure) even that was gone.
so i went online and downloaded basically everything you can find online to recover a harbricked op2.
turns out, after i got my fastboot working again, the OEM and the device were locked (still not sure if those are different things or the same) and because i couldnt get in the android system, i could not enable it.
the ADB commands do not work at all because there is no device detected for it, though it is detected for fastboot. the command fastboot OEM unlock does not work because OEM unlocking is disabled...
so far i have been able to connect my phone in 3 modes and names for those, them being:
Android Bootloader interface (Fastboot)
Qualcomm HS-USB Diagnostics 900E (Connected while holding VolUp)
RELINK HS-USB QDLoader 9008 (Connected while holding VolUp + VolDown)
I am also unable to flash anything on the phone because the OEM is locked
I will not be able to answer for some time (probably 2-3 weeks) but i wanted to start this thread so I could already have an answer when i come back home again (traveling with fam, and its somewhat hard to take a PC tower with you on trips)
Thanks for helping me! :fingers-crossed:

I'm having the exact same issue as OP.
I'm not sure exactly what I did, but I can only boot to fastboot. Typing fastboot continue does not work, I can't flash ANYTHING or use any of the recovery tools, because my device is locked, and there's no system to boot to so I can run fastboot oem unlock (have to turn on debugging, which I can't do). I have read just about every guide there is, and also downloaded a boatload of purported "fix" tools/drivers/packages. My phone remains able to boot only into fastboot, and I can't get anything working.
Installing the device drivers did work for me, so I'm about half a step ahead of some other people with this issue, but none of the tools or scripts I've found, or manual methods, have brought my OP2 back to life.
I'm really, really hoping someone here is able to help with this.

Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk

Coolmfarshard said:
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.

http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449

Lonemaster said:
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
Click to expand...
Click to collapse
Its working bro tried several phones with this tool
You cant know its working or not without trying

Coolmfarshard said:
Its working bro tried several phones with this tool
You cant know its working or not without trying
Click to expand...
Click to collapse
Ok, Thanks. Don't know what i was thinking back then.
I will reply again when i am Home and tried it. (Currently i am just using Internet cafes.)

MickyFoley said:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
Oh, it is that one. I had already tried this one, in all listed modes posted above. The problem with that one is that everytime I hit the start button, the green progress bar does not show up and it does not a single thing... because I am staying at a place with a internet café for 3 days, I can download some stuff and try it again.
EDIT: I don't know if that was the reason It didn't work, but I may or may not have forgotten to install the driver because it was deleted off the onedrive page and I just forgot about it afterwards. if I can find a replacement for it, I will ink it here for future users with the same problem. otherwise, I would be GLaD if someone would do that for me...

Have you tried flashing a stock ROM with the qcom download tool

abdur10567 said:
Have you tried flashing a stock ROM with the qcom download tool
Click to expand...
Click to collapse
I am not sure if it is that one (it gets pretty messy wehen you have downloaded 50 gigs), but i think it wouldn't let Me because of the locked OEM.

Lonemaster said:
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
etc. etc.
Thanks for helping me! :fingers-crossed:
Click to expand...
Click to collapse
For some reason, after doing it for the what felt like the billionth time whith the restore tool it finally worked (I have NO ****ING IDEA why tho.)
Thanks for everybody who helped me.

[ASK] Oppo A37f (neo9) problem

Hi, im new here with no knowledge about android system.
my phone is oppo a37f running coloros 5.1.1 and 1 week ago i was downgraded it bcs i want to get root access. but i think something is crashed everytime. my screen freeze or hang and then restarted everything like rebooted.
now i want to unlock bootloader and try TWRP recovery so i can try custom rom for my phone.
i've tried many ways to unlock bootloader (with/without pc) and i still cant get into it
edit: because i think my phone cant load fastboot or even dont have fastboot mode. only recovery mode exist. tried with adb reboot-bootloader or adb reboot bootloader and nothing changed, normally startup, then if i type fastboot devices and nothing shown in my powershell, and if fastboot device without 's' then show waiting for device and stuck. tried also to fix this under devmgmt.msc because i think its a driver problem but still nothing.
yesterday i was tried for using oppotools but bootunlocker is not working for no reason, clicked unlock and tamper but nothing happened. and yesterday i accidentally deleted my stock recovery but everything is back now.
i have tried many ways until download QFIL but still not working. please help :crying:
sorry for my english

vlentzz said:
Hi, im new here with no knowledge about android system...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3631737
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Ibuprophen said:
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3631737
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
I've seen that thread also but still nothing happened with my phone
because i've seen many tutorial from xda about my phone thats why i make this thread. tired of googling and even search on youtube. :crying:
ok sorry, will do it later. thankyou bro.

SM-S727VL Root and Recovery

I cannot for the life of me get this phone rooted or a recovery installed. Odin always fails and ADB doesn't recognize the device. Does anyone have any info on rooting this device? I really just want to at least be able to update this thing to nougat.

Nobody knows much about this device since it's not that popular. Some team named TWRP builder built a twrp for the SM-S727VL but it cannot be flashed even when converting to .tar.md5 or .tar.
Also I believe the bootloader on this phone is locked and CROM service does not function (if I am correct) on this device. CROM service will show it being unlocked but it seems to be lying to you.

djared704 said:
Nobody knows much about this device since it's not that popular. Some team named TWRP builder built a twrp for the SM-S727VL but it cannot be flashed even when converting to .tar.md5 or .tar.
Also I believe the bootloader on this phone is locked and CROM service does not function (if I am correct) on this device. CROM service will show it being unlocked but it seems to be lying to you.
Click to expand...
Click to collapse
Well that figures, im willing to use my device to work at it if anyone knows where to start.

I have 3 of these... not a noob but not an expert...say Pre-elite lol. I'm wanting to learn how to go further than use everybody else's solutions to root my phone's if somebody can give me some advice as to where to start as in I know how to root put it that way I was one of the people back in the day with the Evo when it was actually difficult no worries most of them were fine but these files we keep flashing these ROMs these kernels these firmwares where does one start when a phone like this 727 VL is obscure supposedly and nobody is doing anything to be able to root them I have everything that I need I'm sure and if I don't get it. It's somebody point me to a person or in the right direction to get started on what I need to due to learn how to write for I mean what where's the first step on these I've always just use everybody else's files. If that even makes any sense to anybody and anybody can give me a hand or show me the right way I'd be willing to do the work from there on I just need somebody to stick up a finger and say go there.... I mean if we have a twrp written, and we have OEM unlock, then why can't one of us do this I've been around long enough I've read long enough I've never once posted in these forms but I've read them daily... I know I got the skills I just need to know which ones to use. Odin fails like he said, fastboot for some reason still won't recognize, I actually made it one step with one of mine but it has to be a little incorrect because the only thing noticeable is it pops up with vo LTE at the top instead of just regular LTE like this one I'm on now. I was able to flash it with Odin believe it or not with what seems to be possibly just stock S727VLUDU2AQG1_ENG_boot_boxwares.tar
BUT the point is I was able to flash it with Odin and also it did change something because my phone now says there's been unauthorized changes and it wants me to restart it all the time so it can correct itself however it does not, it stays whatever it is, yes I know this is pretty vague however I got to the point where I just started trying anything on one of these phones to see if I could get any kind of anything to work and it did.. kind of.
I will say the USB drivers that's you find every where now do not work you have to go back to looks like version 1.5.5 1.0 SAMSUNG-USB-Driver-for-Mobile-Phones-15510.
With these drivers fast boots if I remember correctly will recognize it when you do fastboot devices however it still hangs on waiting on device. I'm sure I got more information my brains just a little foggy at the moment it is like 3 in the morning and I hope I didn't break any rules posting.
I did try flashing from SD card with no success yet nothing at all just error after error. I have tried twrp however it's supposed to be for this 727 VL I'm sure it's the same one everybody's got because it's only in one place that I've found but it comes up twrp-3.2.1-j7popqltefnvzw-201 and it will not flash.
I realize I have been pretty obscure however there's no reason why if all 5 of us with this VL stick together we can't get it rooted because I'm not going to give up LOL

Keep up the good work
I to have a j7 sky Pro, we need to figure out how to get this bootloader unlocked I would love the links to any from builds or twerp builds you have for this j7POPQLTEFNVZW

twrp
[email protected] said:
I to have a j7 sky Pro, we need to figure out how to get this bootloader unlocked I would love the links to any from builds or twerp builds you have for this j7POPQLTEFNVZW
Click to expand...
Click to collapse
I have a twrp that I managed to find on the internet but i have heard that it was for an older version of the phone. meaning it has to be updated somehow. I do know that the phone had a security patch update on June 1, 2018. I am currently trying to figure out if how to update the twrp or something, but I think I might need a little assistance. Because I am no expert ROM developer or anything of the sort but I am trying to learn, so I can eventually build a custom ROM for this phone.

Masterx4020 said:
I have a twrp that I managed to find on the internet but i have heard that it was for an older version of the phone. meaning it has to be updated somehow. I do know that the phone had a security patch update on June 1, 2018. I am currently trying to figure out if how to update the twrp or something, but I think I might need a little assistance. Because I am no expert ROM developer or anything of the sort but I am trying to learn, so I can eventually build a custom ROM for this phone.
Click to expand...
Click to collapse
Like I said in another thread about this issue, We are not to that bridge yet. The bootloader is locked and we cannot flash it yet.

Justin1198 said:
Like I said in another thread about this issue, We are not to that bridge yet. The bootloader is locked and we cannot flash it yet.
Click to expand...
Click to collapse
Okay, have you tried anything to unlock it. If so can you tell me what you have tried so I can see what doesn't work.

Masterx4020 said:
Okay, have you tried anything to unlock it. If so can you tell me what you have tried so I can see what doesn't work.
Click to expand...
Click to collapse
See post #11 on thread https://forum.xda-developers.com/galaxy-j7/how-to/sm-s727vl-analysis-partition-table-t3858632

Justin1198 said:
See post #11 on thread https://forum.xda-developers.com/galaxy-j7/how-to/sm-s727vl-analysis-partition-table-t3858632
Click to expand...
Click to collapse
Is there a way to tell if the bootloader is locked? (Sorry if I am asking noobish questions. I am just trying to learn.)

You can tell the Bootloader is locked because you get “Secure Check Failed” if you try to flash anything that has been modified. For example; The TWRP recovery file. We need root to bypass the Bootloader.

Allow

allow what
I feel like you're telling me to do something that's way over my head cuz I do not understand what do you mean by allow

I have read write access to root files now !!
I can now access all files on my 2nd of 3 J7s. I am attaching pics. When I try to duplicate and copy on my other J7 ,the factory ones, I get check file permissions access denied. However I've passed it on this one particularly. It also now gives me a security notice on the lock screen of unauthorised actions have been detected please restart phone to correct them. However even when you restart the phone it stays so it isnt temporary. I have actually even going to factory reset to see believe it or not it stays. So the next step would be one in which I need some input to know which files I need to modify to be able to install BusyBox Superuser and from their custom recovery excetra and we're in I believe correct me if I'm wrong.
Can't post pics yet so someone get at me here and I will send them to you to post. Or on my FB at Mighty.Whity.Titan

You can send them to me if you like.

No problem how do I not familiar with these forms
josh0426 said:
You can send them to me if you like.
Click to expand...
Click to collapse
One b a d d a d d i e i o and that said the old Google Mail you know if you want to send me an email I can forward them all to you cuz I can't post them and that's about the best I can do

Pre-Elite said:
One b a d d a d d i e i o and that said the old Google Mail you know if you want to send me an email I can forward them all to you cuz I can't post them and that's about the best I can do
Click to expand...
Click to collapse
[email protected]

Pre-Elite said:
I can now access all files on my 2nd of 3 J7s. I am attaching pics. When I try to duplicate and copy on my other J7 ,the factory ones, I get check file permissions access denied. However I've passed it on this one particularly. It also now gives me a security notice on the lock screen of unauthorised actions have been detected please restart phone to correct them. However even when you restart the phone it stays so it isnt temporary. I have actually even going to factory reset to see believe it or not it stays. So the next step would be one in which I need some input to know which files I need to modify to be able to install BusyBox Superuser and from their custom recovery excetra and we're in I believe correct me if I'm wrong.
Can't post pics yet so someone get at me here and I will send them to you to post. Or on my FB at Mighty.Whity.Titan
Click to expand...
Click to collapse
Can you please share the method that you used to gain read/write access? If you indeed have temp access, I can make it permanent also what firmware build are you on?

Absolutely
I'm not home right now but I'm headed there I'll be there in a couple hours I can if somebody wants to give you their email or email me because I can't post links or anyting I have the file that I used the wrong and I have the driver for Samsung for Odin that I used which I think I've mentioned in my original or previous post and by the way it is not temporary. This is permanent. I did a factory reset and it stays. I just need to know which permissions which file to go to to get my Superuser installed because it's still will not let me install that. But email me or tell me how to send it on here or something that way I can let you guys know or give you guys what I got. I'll tell you this I did not flash it with a v l ROM. I flashed it using a Verizon ROM the only thing that didn't work was my wife I which I think I originally and said back when I made my first comment on this thread I haven't done anything else I set my phone down and it was done clear back there I just didn't realize it. But it is not a VL ROM it's a Verizon ROM a v not a straight talk and my wife I would not which turned out to be something unrelated. I'm in no way trying to keep this from anybody because I know just how much we all want these damn things. But I would sure love to finish the job that I started but I do not mind handing over what I've got.
---------- Post added at 02:53 AM ---------- Previous post was at 02:40 AM ----------
Josh I just emailed you six pictures I just now seen your email in your post and Justin as soon as I get home if you can shoot me an email or get in contact somehow or I can send you everything I got so far once I get there

Here are the pictures