Corrupted build.prob, now can't factor reset - AT&T LG G3

I ran the att factory reset instructions once and it ran perfectly. Later I tried to use the mod to have all the apps run in splitview and corrupted the build.prob file and now I can't return to factory reset.
I changed the build.prob file on my mac and forgot to change the name to build.pro.bak when I copied it into the system folder. Needless to say, when I rebooted the phone it went into a black screen after the lg logo.
Now I am trying to flash the file once again and it tells me the device model is different, to check the phone or dll.
I am not sure how this could be since I am using the same DLL and TOT file I used previously and it worked fine before.
Do you guys think there is a workaround for this?
Would a hard reset ( power + volume down) make things worst?
Thanks,

May have to return to stock.
cookie29 said:
I ran the att factory reset instructions once and it ran perfectly. Later I tried to use the mod to have all the apps run in splitview and corrupted the build.prob file and now I can't return to factory reset.
I changed the build.prob file on my mac and forgot to change the name to build.pro.bak when I copied it into the system folder. Needless to say, when I rebooted the phone it went into a black screen after the lg logo.
Now I am trying to flash the file once again and it tells me the device model is different, to check the phone or dll.
I am not sure how this could be since I am using the same DLL and TOT file I used previously and it worked fine before.
Do you guys think there is a workaround for this?
Would a hard reset ( power + volume down) make things worst?
Thanks,
Click to expand...
Click to collapse
Try returning to stock. http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827 . Hope this helps. Use a win 7 computer if you can is much faster than win 8 at flashing this phone.

hi
cookie29 said:
I ran the att factory reset instructions once and it ran perfectly. Later I tried to use the mod to have all the apps run in splitview and corrupted the build.prob file and now I can't return to factory reset.
I changed the build.prob file on my mac and forgot to change the name to build.pro.bak when I copied it into the system folder. Needless to say, when I rebooted the phone it went into a black screen after the lg logo.
Now I am trying to flash the file once again and it tells me the device model is different, to check the phone or dll.
I am not sure how this could be since I am using the same DLL and TOT file I used previously and it worked fine before.
Do you guys think there is a workaround for this?
Would a hard reset ( power + volume down) make things worst?
Thanks,
Click to expand...
Click to collapse
i have same problem if you can find the Solution tell me please

anasmilan said:
i have same problem if you can find the Solution tell me please
Click to expand...
Click to collapse
Follow this link.*http://forum.xda-developers.com/showthread.php?t=2771401
Download all the tot files and see which one works for you. One of the 400L or the F400 worked for me.

cookie29 said:
I ran the att factory reset instructions once and it ran perfectly. Later I tried to use the mod to have all the apps run in splitview and corrupted the build.prob file and now I can't return to factory reset.
I changed the build.prob file on my mac and forgot to change the name to build.pro.bak when I copied it into the system folder. Needless to say, when I rebooted the phone it went into a black screen after the lg logo.
Now I am trying to flash the file once again and it tells me the device model is different, to check the phone or dll.
I am not sure how this could be since I am using the same DLL and TOT file I used previously and it worked fine before.
Do you guys think there is a workaround for this?
Would a hard reset ( power + volume down) make things worst?
Thanks,
Click to expand...
Click to collapse
I did the same thing by forgetting to fix permissions after editing my build.prop. Follow the instructions in this link and you'll be good:
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827

techjeep said:
I did the same thing by forgetting to fix permissions after editing my build.prop. Follow the instructions in this link and you'll be good:
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
Click to expand...
Click to collapse
I have the same problem, tryed to follow those steps but it say "Wrong device model"
I have the AT&T D850 32Gb model
Please, can someone help with this?

I read somewhere that editing the build.prop with Root Explorer causes it to become corrupted. I guess the build.prop is quite large and RE doesn't open it fully so what ever is cut off st the end is saved that way after an edit. Just some food for thought.
Sent from my LG-D851 using Tapatalk

hi
Skizzy034 said:
I read somewhere that editing the build.prop with Root Explorer causes it to become corrupted. I guess the build.prop is quite large and RE doesn't open it fully so what ever is cut off st the end is saved that way after an edit. Just some food for thought.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
flash tools read
model is deffrent

Related

[Q] Recovering/Replacing the IMEI number

So I just received a replacement phone via warranty from T-Mobile.
I have upgraded to Gingerbread 2.3.6 and am rooted.
I just realized now that the IMEI number in Android is 00000000.
I'm not sure if it was like this before I started tinkering with it or if it happen as a result of the root/upgrade.
Anyways, I have the sticker that gives me the IMEI number under the battery, I just need to know if/how I can get this back into my phone. I've read something involving a HEX editor? But I don't know what or how.
Any advice and links would be greatly appreciated.
A little more information. I originally noticed that the IMEI was set at 0000000 because I tried to install Swype beta and it says cannot install on an android emulator. Further googling of this lead me to realize that swype wasn't recognizing my phone as a legit android OS because the IMEI number was missing...so yea. This is where I am now.
CoBfan1987 said:
A little more information. I originally noticed that the IMEI was set at 0000000 because I tried to install Swype beta and it says cannot install on an android emulator. Further googling of this lead me to realize that swype wasn't recognizing my phone as a legit android OS because the IMEI number was missing...so yea. This is where I am now.
Click to expand...
Click to collapse
Did you make any backups before upgrading to Gingerbread 2.3.6?
ADD: Here is a quote off another thread with this problem:
I got my IMEI back. I had my nv_data.bin.md5 and nv_data.bin backed up when I unlocked my phone after I got the new one from Samsung. I just coppied them the the efs folder and my IMEI is back."
Hope it helps! And hope you have a back up... maybe even from your other phone?? Or before you upgraded the phone you have.
Should they be in this directory?:
/efs/root/afs/settings
because those are the only ones i can find
Sent from my SGH-T959V using XDA App
CoBfan1987 said:
Should they be in this directory?:
/efs/root/afs/settings
because those are the only ones i can find
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Yes.
10char
So I have the nv_data.bin and nv_data.bin.md5 files from my old phone and from my new phone. Sorry, I wasn't thinking enough to make a backup of these files when I upgraded to Gingerbread using Samsung Kies.
So now, with these two sets of files. Do I want to take the old (and good) files from my old phone and replace the files on my new phone. Won't that transfer the old phone's IMEI though?
CoBfan1987 said:
So I have the nv_data.bin and nv_data.bin.md5 files from my old phone and from my new phone. Sorry, I wasn't thinking enough to make a backup of these files when I upgraded to Gingerbread using Samsung Kies.
So now, with these two sets of files. Do I want to take the old (and good) files from my old phone and replace the files on my new phone. Won't that transfer the old phone's IMEI though?
Click to expand...
Click to collapse
First - Is your phone working?
Second - Have you tried a factory reset if your phone is working?
Third - Try a factory reset and reflash a stock rom.
Fourth - If you phone is not working give it a shot and let us know
Yes the phone is working fine. Just with the IMEI missing, I can't get Swype beta to install (I'm assuming that is the problem)(That the only problem I've found so far). Would a factory reset restore the bin files and IMEI number then?
CoBfan1987 said:
Yes the phone is working fine. Just with the IMEI missing, I can't get Swype beta to install (I'm assuming that is the problem)(That the only problem I've found so far). Would a factory reset restore the bin files and IMEI number then?
Click to expand...
Click to collapse
What I have read is a factory reset or reflashing a ROM (or both if all else fails) should restore your IMEI. I have also read flashing the original ROM that came on the phone has worked. You may try that if the factory reset does not restore it.
Since your phone is working don't copy the files over from your other phone
Do let us know your progress.
How do I obtain the original rom, is it posted here in the forum?
CoBfan1987 said:
How do I obtain the original rom, is it posted here in the forum?
Click to expand...
Click to collapse
Did you do the factory reset yet?
resetting as we speak. Report back in a sec
okay reset is done and IMEI is still 0000000000
CoBfan1987 said:
okay reset is done and IMEI is still 0000000000
Click to expand...
Click to collapse
Try doing the factory reset again and flashing back to froyo
http://forum.xda-developers.com/showthread.php?t=1106822
assuming the was what came with the phone?
I'm hitting the same very disgruntling problem that I did in the past when I tried to use CWM. When I try apply update from sdcard and I choose my update.zip file I just get E:signature verification failed and I can't proceed from there....
CoBfan1987 said:
I'm hitting the same very disgruntling problem that I did in the past when I tried to use CWM. When I try apply update from sdcard and I choose my update.zip file I just get E:signature verification failed and I can't proceed from there....
Click to expand...
Click to collapse
What color is your recovery?
blue
"Android system recovery <3e>
Samsung Recovery Utils
- for BML -"
CoBfan1987 said:
blue
"Android system recovery <3e>
Samsung Recovery Utils
- for BML -"
Click to expand...
Click to collapse
You need a custom kernal to flash from CWM. That is why you are getting that error. Let me look for an odin flash back to froyo stock for you.
On a side note - I have read taking your battery out for 10 mins has worked for some. Since your phone is working you may try that while we continue to look for a fix.
Sucks that this kind of problem would happen from following these instructions. I figure it would all automated and such...
http://support.t-mobile.com/docs/DOC-1810
and my battery is out now.
CoBfan1987 said:
Sucks that this kind of problem would happen from following these instructions. I figure it would all automated and such...
http://support.t-mobile.com/docs/DOC-1810
and my battery is out now.
Click to expand...
Click to collapse
I say before going back to froyo try raver's ROM-ODIN-2.3.6-Gingerbread Offical Maybe a stock reflash will work. I have read a thousand ways that have work for different people now. You have done a few. Try this as it is easier than going back to froyo for now. Let your battery charge first.
Maybe kies just f-ed up your imei. And where are the big dog's when you need them? bhundven/FBis251?
Did you just root? Or did you use an app to unlock your phone as well?

issues Flashing my phone back to stock image after accidental "unroot"

So I have the h900 currently with the Xposed framework installed. it WAS rooted until I stupidly unrooted it in the SuperSU app. I have SuperSU installed as a system app. so when I factory reset and open SuperSU, it notifies me that I don't have the SU binaries... I figured this wasn't a problem, and I would just flash the stock image... NOPE! invalid TOT. nothing I have tried goes beyond 9% before I get the "invaled TOT" notification on my PC. while it was rooted I changed all sorts of stuff in the build.prop. Ex. Model number, Bluetooth address, Mac address, android version, and IMEI, device ID. all that stuff. I have come to the conclusion that, that is my problem. The model number. Does that sound feasible?
Now, none of this would be an issue if I could use snapchat... snapchat knows I have the xposed framework installed and I cannot sign in. (laugh it up). and without root... I cannot flash the .zip file to uninstall xposed framework. ive been working on this on and off for 3 weeks. ands its done pissed me off. haha.
oh, and and I still have functionality in most of the xposed modules even WITHOUT root. incase anyone was wondering wether or not you need root. I can list which xposed modules I'm currently using and wether or not they work if anyone wants.
I'm goin to attempt to flash it again right meow. ill report back when it is, once again unsuccessful
well. no success. I even deleted every single file that had anything to do with LG. then downloaded everything again and still, I got no luck.
Possibly broken tot?
Try flashing the original tot if your not already. If not, try using Kingroot to at least get you full access, if your granted root access again, change your device detail back to the original status. Especially the model number. I believe your changed model number is whats triggering your invalid tot error. If you are unable to do so, grab the tot of the model you changed your device to show, and see if you can edit any of the model number identifying entities in the tot file its self. You want to try to trick lg flash to think your flashing the tot file of the model you changed your device to. This process has not been done before nor do i know how to do it, but as far as the diagnostic i provided, i believe it to be correct.
---------- Post added 27th May 2016 at 12:05 AM ---------- Previous post was 26th May 2016 at 11:15 PM ----------
I found this on the G3 forums
sgtmedeiros said:
It seems that there is a way to fix it after all! there is a dll file for the lg g2 that skis the check of which model your phone is. I used this dll in combination with the stock .tot file and it worked!
Click to expand...
Click to collapse
If that dll will work for the v10, that might be the easy fix.
Sent from my LG-H900 using XDA-Developers mobile app
I tried Kingroot and I cant regain Root. is there anyway to install the SU binaries??
I'm gonna try the other option tonight. I've read that thread too, Only I'm unsure if i should rename the .zip file before i unzip it? then rename the .tot file that i get from the .zip?
bellcrayyy said:
I tried Kingroot and I cant regain Root. is there anyway to install the SU binaries??
I'm gonna try the other option tonight. I've read that thread too, Only I'm unsure if i should rename the .zip file before i unzip it? then rename the .tot file that i get from the .zip?
Click to expand...
Click to collapse
Better safe than sorry to rename the .dll file. But after looking into it, it was named after the processer the device that file was designed for, or at least its MSM id. So rename it to LGUP_8992.
Another thing i found, was someone talking about doing a full uninstall of super su, then sideloading it with ADB. With the goal being to re-root your device so you can reset all addresses, IDs, and the model number, i do believe the solution will come from sideloading if the dll doesnt work. BTW. I forgot to ask if you had any kind of custom recovery? And did you modify the the model number using build.prop?
Well. I can't get it to flash back. Not really an issue. I still have the xposed framework active. I just cant update to marshmallow or use Snapchat. Lol.
This the last thing I could find. After that, youll probably have to wait for a dev to crack the h900 wide open.
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
Its been awhile. Ive been super busy with work and I'm taking a course for certification in penetration testing.
Never could figure it out. Kinda sucks
I'm limited to what xposed modules I can use, as some require root access.
Does anyone know how close the devs are to unlocking the bootloader?
Sent from my Certainly not another basic ***** like Siri. Can you say Eww?! using XDA-Developers mobile app
Wait. You can flash zips from within the TWRP apk. The app requires root. I know... But what if I select the supersu apk and press "flash now" will it attempt to flash the .zip? Or will it remind me that I haven't granted root privileges.
LG V10
Tried it. Didn't work. Looks like I'm stuck with this for awhile.
LG V10
bellcrayyy said:
Tried it. Didn't work. Looks like I'm stuck with this for awhile.
LG V10
Click to expand...
Click to collapse
The few devs i know of working on the project have hit multiple road blocks but, some files that are availible need either decrypting, converting, or recompiling. Which is not so easy for some file formats that are only used with LG.
Im still working on converting and decrypting one file that is availible. It appears to be an apple file, but im running windows, so conversion is tricky.
I'm building a hackintosh.... Almost finished... I can let you use it as a designated virtual machine if that'll help. Lol
LG V10
bellcrayyy said:
I'm building a hackintosh.... Almost finished... I can let you use it as a designated virtual machine if that'll help. Lol
LG V10
Click to expand...
Click to collapse
Or would you like a crack at it? I think the main thing is that its not compatible with windows.
PM'd
LG V10
Shadow Assassin said:
And did you modify the the model number using build.prop?
Click to expand...
Click to collapse
Oh. I forgot to mention that i did change the model number using the build.prop
bellcrayyy said:
Oh. I forgot to mention that i did change the model number using the build.prop
Click to expand...
Click to collapse
I want to congratulate you. To hard brick a phone is very rare and in some cases difficult. But you might have done it! Lol, but probably not. With the right tot it can be fixed.

[FIXED] Stock HTC one M8 won't boot shows a red triangle with exclamation point.

So i have a STOCK HTC_M8Wl and a while back I tried to update it and this happened. The phone is no longer activated I've wiped data and cache from recovery mode I can also get into bootloader mode. When I attempt to power on the phone it shows the HTC boot screen for a min then turns off and back on to the same screen and after a minute or two it goes to a black screen then displays the phone with a red triangle and exclamation point in the middle then stays there.
I've looked all around the Internet and found this problem commonly with rooted devices but my problem is that mines is not rooted and is 100% stock. Is there a way to fix this problem from my position please let me know because I would love to make a thread on this problem because I only found one and they never explained how to fix it. (I belive it was the problem as mines) also I don't know much about HTC phones I have worked with rooting android before.
My solution:
Thanks to izzaeroth and the thread he provided me I was able to revive my phone. The ruu zip file kept failing saying signature verification failed do to large img file. So I decided to try the 6.0 ruu exe file instead. (My pc does have drivers to detect the phone while it's in fastboot mode) I launched the exe and it extracted the ruu I plug in my phone and started the process. It flashed all partitions it did take a while to load but after the update the phone booted it began to optimize 226 apps after that it booted and done it finally was fixed.
did u power it off while trying to update? you might be able to use one of dottats fuu/ruu files to try and bring it back to life
Sent from my m8wl using XDA-Developers mobile app
izzaeroth said:
did u power it off while trying to update? you might be able to use one of dottats fuu/ruu files to try and bring it back to life
Click to expand...
Click to collapse
Yes I belive it did turn off while updating that's what I was told. But how do I fix it with the dottat file? I have OTA update files part 1 and part 2 but I always get the status 7 error.
-spektor- said:
Yes I belive it did turn off while updating that's what I was told. But how do I fix it with the dottat file? I have OTA update files part 1 and part 2 but I always get the status 7 error.
Click to expand...
Click to collapse
you need to go here: http://forum.xda-developers.com/showthread.php?t=2883845
you will need the marshmallow 6.0 file, you might have to use the zip version, option 2. read instructions carefully etc etc
Sent from my m8wl using XDA-Developers mobile app
izzaeroth said:
you need to go here: http://forum.xda-developers.com/showthread.php?t=2883845
you will need the marshmallow 6.0 file, you might have to use the zip version, option 2. read instructions carefully etc etc
Click to expand...
Click to collapse
I've downloaded the 6.0 zip file but when using method 2 it said the file was to big n I downloaded the file again to make sure the file downloaded correctly n then it was a signature or a verification issue flashing it via HTC fastboot didn't seem to work either, I can't currently do much do to no Internet connection. So I cant keep re-downloading files to check.
-spektor- said:
I've downloaded the 6.0 zip file but when using method 2 it said the file was to big n I downloaded the file again to make sure the file downloaded correctly n then it was a signature or a verification issue flashing it via HTC fastboot didn't seem to work either, I can't currently do much do to no Internet connection. So I cant keep re-downloading files to check.
Click to expand...
Click to collapse
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
izzaeroth said:
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
Click to expand...
Click to collapse
It said it in fastboot when ever it detected the file n I think it said the same when i tried it with adb/fastboot on windows pc
izzaeroth said:
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
Click to expand...
Click to collapse
The 6.0 run exe worked it took a while to update but it worked and finally got past the same screen and it started to optimize apps that took a good 30 min ill update this thread when I get wifi again thanks for your help
-spektor- said:
The 6.0 run exe worked it took a while to update but it worked and finally got past the same screen and it started to optimize apps that took a good 30 min ill update this thread when I get wifi again thanks for your help
Click to expand...
Click to collapse
awesome! glad u got it working

[G Stylo 3 Plus] 10c stock kdz and dll for LGUP

https://androidfilehost.com/?fid=817906626617935214
Read the text file for how to put the LGUP_c.dll
mingkee said:
https://androidfilehost.com/?fid=817906626617935214
Read the text file for how to put the LGUP_c.dll
Click to expand...
Click to collapse
Thanks! Any chance you have a copy of the 5d firmware, too?
vettejock99 said:
Thanks! Any chance you have a copy of the 5d firmware, too?
Click to expand...
Click to collapse
I have the ROM downloaded, but 3 Plus has problem right now
mingkee said:
I have the ROM downloaded, but 3 Plus has problem right now
Click to expand...
Click to collapse
Thanks. I just reflashed 10d (my mistake when I said 5d) with LGUP and uppercut. I guess you can't boot to TWRP without having flashed it first or something so I'm as good as I can be for now. Hope your issue clears up.
I realized I used a wrong command to flash boot instead of recovery.
Fortunately, I saved the 10d full ROM and I just flash it with LGUP and use correct command and install Magisk again. However, I had to wipe the machine due to mistake, but I have a backup a month ago so data loss isn't that bad.
10d seems to be a bit faster.
Full ROM + dll + instruction how to copy.
https://www.androidfilehost.com/?fid=962021903579492992
Thank you Soo much. I just got my 3 plus and in less than 24 hrs managed to f it off completely. My girl was talking to me and I was only paying half attention to what I was doing and wiped everything. No OS of course and I had just gotten it flashed with twrp. Needless to say I feel like an idiot because I hadn't gotten a good backup. I have the .lbf from my PC but I couldn't get bridge to recognize my phone. Lg up would but I need .kdZ
is there a guide on how to return to stock on the LG Stylo 3?
xlegitimate said:
is there a guide on how to return to stock on the LG Stylo 3?
Click to expand...
Click to collapse
+1
hellllllllppppp metro pcs lg stylo 3 plus is frp locked I cant seem to get it unlocked was even going to flash new firmware with lg flash tool....but appearently I'm a retard and don't know how to do any of this any one have step by step instructions??????? please help
xlegitimate said:
is there a guide on how to return to stock on the LG Stylo 3?
Click to expand...
Click to collapse
x2
DLL says it's invalid. Anyone been able to use it successfully?
Edit: Nvm. I just had to reinstall UP (messing with DLLs from flashing other models screwed it up, I'm guessing). Worked great after
alright I have flashed the kdz file from multiple souces including this one, nothing changes on my end says completed but nothing changes, except an error message everytime I open up any app says App Updates has stopped it's getting annoying, my camera is not as good anymore either its more of a blur than anything, what do I have to do to restore this phone back to original settings and original software where I start completely over, this kdz did not do that it kept my apps, it kept everything and then gave me that error
LGUP I could only do upgrade not refurbish it just does not take it as a refurbish something with the file structure I think but that's the only option it would let me do
https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26View attachment LGUP_DualMode.zip
Esin8785 said:
alright I have flashed the kdz file from multiple souces including this one, nothing changes on my end says completed but nothing changes, except an error message everytime I open up any app says App Updates has stopped it's getting annoying, my camera is not as good anymore either its more of a blur than anything, what do I have to do to restore this phone back to original settings and original software where I start completely over, this kdz did not do that it kept my apps, it kept everything and then gave me that error
LGUP I could only do upgrade not refurbish it just does not take it as a refurbish something with the file structure I think but that's the only option it would let me do
Click to expand...
Click to collapse
plug in your phone, unzip this and you will see 2 lgup icons (red). right click on the developer("D" on it) icon and choose run as administrator. notice i skipped uppercut. if you do it this way it is not needed. you have many more choices. it is even possible to put the os of one model running the same hardware into another effectively changing the model. there is no device check. If lgup refuses to do something, close it and boot it up again. Sometimes it helps.

copy and paste suddenly stopped working

Hello, I'm using the stock rooted rom on my s7 and suddenly the copy and paste function stopped working, I can copy and paste things that I'm writing but I can't copy links, Tweets posts so I can share, can't cope messages sent to me, I can copy only what I'm writing, anyone has a solution?
Lipeao said:
Hello, I'm using the stock rooted rom on my s7 and suddenly the copy and paste function stopped working, I can copy and paste things that I'm writing but I can't copy links, Tweets posts so I can share, can't cope messages sent to me, I can copy only what I'm writing, anyone has a solution?
Click to expand...
Click to collapse
what happens when you long press something you want to copy? does it give you the option to copy to clipboard? have you cleared your clipboard ever?
youdoofus said:
what happens when you long press something you want to copy? does it give you the option to copy to clipboard? have you cleared your clipboard ever?
Click to expand...
Click to collapse
When I select text from the Samsung internet, Google Chrome, Samsung notes texts like that which you can select words I can copy without any problem, but I can't copy things that I can't select, for example if I'm on Instagram and I tap on the menu of a photo and select to copy the link it doesn't copy, if I go to a tweet and select to copy the link or the tweet itself I can't copy, so basically I can copy only the type of texts that I can select the words
Lipeao said:
When I select text from the Samsung internet, Google Chrome, Samsung notes texts like that which you can select words I can copy without any problem, but I can't copy things that I can't select, for example if I'm on Instagram and I tap on the menu of a photo and select to copy the link it doesn't copy, if I go to a tweet and select to copy the link or the tweet itself I can't copy, so basically I can copy only the type of texts that I can select the words
Click to expand...
Click to collapse
thats an odd symptom. can you wipe the dalvik cache in recovery? just the dalvik tho, nothing else
youdoofus said:
thats an odd symptom. can you wipe the dalvik cache in recovery? just the dalvik tho, nothing else
Click to expand...
Click to collapse
Wiped the cache using the original download mode because I didn't install the twrp yet but it didn't work
Lipeao said:
Wiped the cache using the original download mode because I didn't install the twrp yet but it didn't work
Click to expand...
Click to collapse
how are you rooted without TWRP?
youdoofus said:
how are you rooted without TWRP?
Click to expand...
Click to collapse
I did it thru Odin, I was having a problem with bootlop trying to install thru the normal method
Lipeao said:
I did it thru Odin, I was having a problem with bootlop trying to install thru the normal method
Click to expand...
Click to collapse
might be related? have you nuked it and Odin installed the factory firmware since the problem arose?
youdoofus said:
might be related? have you nuked it and Odin installed the factory firmware since the problem arose?
Click to expand...
Click to collapse
Not related because it was working everything just fine, it started to happen recently, I'm downloading the most recently firmware and will try to update thru Odin with home_csc to not lose the data
Lipeao said:
Not related because it was working everything just fine, it started to happen recently, I'm downloading the most recently firmware and will try to update thru Odin with home_csc to not lose the data
Click to expand...
Click to collapse
good deal, youre already ahead of the game then. Flash it with the HOME_CSC and let us know what happens
youdoofus said:
good deal, youre already ahead of the game then. Flash it with the HOME_CSC and let us know what happens
Click to expand...
Click to collapse
Tried to flash thru home_csc but got stuck in the Samsung logo so I had to flash it with factory reset with normal Csc, after I was pissed and restored everything I figured what the problem is, when you root you lose the secret mode on Samsung internet but I discovered a line on build.pro that you can change to have it back "r.config.knox=v30" when you change to 00 you have to function back, but after did it tried to copy again and stopped working and when I changed back to v30 it was working again, so I guess I'll stay without the secret mode
Lipeao said:
Tried to flash thru home_csc but got stuck in the Samsung logo so I had to flash it with factory reset with normal Csc, after I was pissed and restored everything I figured what the problem is, when you root you lose the secret mode on Samsung internet but I discovered a line on build.pro that you can change to have it back "r.config.knox=v30" when you change to 00 you have to function back, but after did it tried to copy again and stopped working and when I changed back to v30 it was working again, so I guess I'll stay without the secret mode
Click to expand...
Click to collapse
oh crap, sorry you had to go thru that process unnecessarily man. finding out what was causing it is awesome by itself but figuring out that modding the build.prop to get it working is very awesome! nice work!
youdoofus said:
oh crap, sorry you had to go thru that process unnecessarily man. finding out what was causing it is awesome by itself but figuring out that modding the build.prop to get it working is very awesome! nice work!
Click to expand...
Click to collapse
Yup , thanks for all the help too bro, appreciate it
Lipeao said:
Tried to flash thru home_csc but got stuck in the Samsung logo so I had to flash it with factory reset with normal Csc, after I was pissed and restored everything I figured what the problem is, when you root you lose the secret mode on Samsung internet but I discovered a line on build.pro that you can change to have it back "r.config.knox=v30" when you change to 00 you have to function back, but after did it tried to copy again and stopped working and when I changed back to v30 it was working again, so I guess I'll stay without the secret mode
Click to expand...
Click to collapse
Wow what a genius you are, i tried searching hours in internet how to fix this copy paste bug but none solution worked. I actually did that ro.config 00 to fix secret mode but ended up clipboard not storing text but finally reversing that code made clipboard working again. Thanks man

Categories

Resources