Database Users

Free 50 GB Box Account HELP

I followed the instructions according to mdalacu
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.
Was able to create a bunch of accounts, then deleted the build.prop file and renamed the build.prop.bak back to build.prop, rebooted the phone, and I get to the Samsung Galaxy Note N7000 screen, then it goes black. I cannot boot up the device now.
Any suggestions?

yeahmon said:
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?

bnapalm said:
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.

bnapalm said:
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
It worked, and I was able to reboot back into the Note with these settings.
jayshah said:
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
Click to expand...
Click to collapse
I think you're right about losing the build.prop file. Fortunately, I backed it up. I am trying to access the device now. I have no GUI on the Note. I am hoping it is just a blank screen and the device is still functioning in the background. I'll be back momentarily with an answer to accessing it.

ok...I can access the Note's file system. However, when I try to copy the backup build.prop file into the system directory via Android Commander, it says I need root access to do this permission.
The Note IS rooted. I don't get it.

This appears to be a problem with Android Commander. There are threads about this same problem, but rather than the software creator place a link to his FAQ that he ridicules everyone for not reading, he lambasts them instead. Thats a real good way to get a donation.
Anybody got any other suggestions for a root file explorer, preferably for Mac, but PC will work too.

be careful, backup buid.prop and restore it after creating Box account.

amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse

I am having no luck finding a way to get root access from a computer.

deleted post
user error

The tumbleweeds are big around here

There's an app for that
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/

But is there an app to copy my file over from my computer?

amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
vcespon said:
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
Click to expand...
Click to collapse
Please read the OP before posting.
--
The fact that you are using Android Commander implies you have adb access, this is good.
Here's what I would do to fix your problem, it definitely isn't the only way, but it will work.
#1: Get ADB installed on your PC/Mac/Linux
#2: Open a command line and run
Code:
adb devices
as a test, you should get output that one device is connected via cable, if you don't abort here, nothing else will work
#3: run
Code:
adb remount
This will make your /system writeable
#3: I'll put this as a windows instruction because I don't know the Mac filesystem, but it's almost identical
Code:
adb push C:\build.prop /system/
This will push C:\build.prop (please put your backup copy here) into /system/ of your Note. If you're on a mac, you will need to find another place to put it, e.g. if it's /users/bob/build.prop the command just becomes
Code:
adb push /users/bob/build.prop /system/
I hope this helps
Edit: Paste a copy of output here if it doesn't work so I can help debug

I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.

yeahmon said:
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You'll need to download/install adb first.

jayshah said:
You'll need to download/install adb first.
Click to expand...
Click to collapse
standby...

its taking forever to install SDK

This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
I should have stuck with Dropbox.

yeahmon said:
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
Click to expand...
Click to collapse
You're really going to have to paste the error messages here for any of us to help you further
Alternatively, can't you just reflash your current ROM on top?

How to disable OTA updates (rooted ICS)

Any know how to disable the OTA updates from messing with my root now that I have it the way I like it?
I have the stock OTA ICS upgrade rooted and enabled adhoc for use tethering to my phone while travelling (which is the only reason I rooted it).
TIA!

BBAHunter said:
Any know how to disable the OTA updates from messing with my root now that I have it the way I like it?
I have the stock OTA ICS upgrade rooted and enabled adhoc for use tethering to my phone while travelling (which is the only reason I rooted it).
TIA!
Click to expand...
Click to collapse
Delete either FDUpdater.apk (with odex file) or FWUpdateService.apk (with odex file) and reboot. This should effectively kill that service if I'm not mistaken. You will find them in /System/app.
I typically remove both before compiling a rom. You may or may not get an error when you reboot. Maybe. Mine are usually deodex'd. So might be best to cut and paste them to SD Card. Just in case

Moscow Desire said:
Delete either FDUpdater.apk (with odex file) or FWUpdateService.apk (with odex file) and reboot. This should effectively kill that service if I'm not mistaken. You will find them in /System/app.
I typically remove both before compiling a rom. You may or may not get an error when you reboot. Maybe. Mine are usually deodex'd. So might be best to cut and paste them to SD Card. Just in case
Click to expand...
Click to collapse
Unfortunately I am unable to make any changes to these two files. Using either ES File Manager or Root Manager, any file options returns a FAILED. Even chmod in Android Terminal Emulator says files are read only.
Any help on how to get rid of these annoying files would be greatly appreciated.
Thanks.
Cole

Settings- About Tablet- Update system -uncheck the box

Wifi password stores in encrypted from

Since, I am rooted and I have several wifi password connected with it but later when I tried to see the pass from several wifi password apps and from the ES file explorer- data/misc/wifi- WPA_supplicant.conf it shows the long digit as password. Its in encrypted form and Now I am unable to read it out and connect to another device. Plz help me to decrypt or fix this issue!! Currently I am in Android 4.4.2 kitkat baseband XXUGNH6. -Thank you!!

I think it is impossible to decrypt passwords that are already stored in the wpa_supplicant.conf file. But you can edit your build.prop file (located in system folder) and change
Code:
ro.securestorage.support=true
to
Code:
ro.securestorage.support=false
Then reboot your device. By doing this, all stored passwords will be cleared and you will have to connect to Wi-Fi networks again. Therefore, you will be able to see passwords decrypted in your wpa_supplicant.conf file.

No sir! It didn't worked.. the password still SHOWING= 7a141b181315013c8684cbacfe71362d :'(

I tried it too. It didnt work.i have a galaxy j5 prime.

[OREO] How to install Oreo Beta 3 on Samsung S8+ and not lose your data!

This is an updated guide for the Samsung S8+ (G955F) version for the new beta 3.
I thought I would put this guide out there as this was the easiest I found and the bonus is that you keep your data and just upgrade over the top.
All credit to jaron vdb from Telegram. This is his backup and he has given me permission to use it. He is the brains – I am just good at writing easy to use guides!
Pre-requisite:
-you need to have a working TWRP
-you need an external sd card
Steps:
1. Get into TWRP and backup your current rom to your external SD card. We will need this later to restore the data and importantly: if things go wrong you can always restore back again to what you have now.
Once it has been backed up you will have a folder on your external sd card that looks something like this:
Name of your External SD card/TWRP/BACKUPS/ce04873839487e8383/[the name of the file you just backed up in step 1]
2. Download this file and save it to your External SD CARD:
https://drive.google.com/open?id=1wOl1fPK_9ffSxOcGg6IHvytCrHZ7yL-X
This is your TWRP restore file kindly provided by jaron vdb.
3. Once you have downloaded that file then you will need to unzip this file. Use something like 7zip from Playstore and extract that file you downloaded to this location you just created with Step 1 – something like:
External SD CARD/TWRP/BACKUPS/ce04873839487e8383/[the name of the file you just unzipped]
This is a very important step – you must extract the file you downloaded to this EXACT location.
4. Go here and download supersu 2.82SR5 to your external SD Card:
https://androidfilebox.com/app/supersu-root/
This is the only root version working at the moment – magisk does not work as of now. It is Supersu which works perfectly. It also has dm-verity on it so will allow you access to data in TWRP.
5. Ok we are ready to flash the Beta 2! Get into TWRP again
6. Hit the restore button and then go to your external SD Card and restore the file that you downloaded and had to extract. You will also see your other restore in there. Don’t touch that just yet.
7. Stay in TWRP and now go to Wipe and then go to Format Data and then type in yes
8. Stay in TWRP and now go to Restore and choose the first file you backed up in Step 1 – your original backed up ROM. Choose this file and then ONLY TICK data to install. Restore data.
9. Stay in TWRP and flash the supersu file you downloaded.
10. Reboot!
11. You now should be rebooted back into your original rom with the very smooth Beta 3 installed!
12. Now you have to make the fix so you don’t get a buttload of random reboots and Knox nonsense. Download Root Explorer or any build prop editor program from Playstore and change:
ro.config.tima=1 to ro.config.tima=0
and change Knox thingo to v30 like this:
ro.config.knox=v30
Mine was already on v30 but YMMV
13. Have a cup of tea.

Can confirm working on G955F
Did exactly as instructed and all is well so far
Thank you

Will these steps work if I'm on 7.0
Or are these only for people who have already upgraded to oreo b1 / b2?
Thanks in advance.
One more question, can I use it on G955FD?

wkdurrani said:
Will these steps work if I'm on 7.0
Or are these only for people who have already upgraded to oreo b1 / b2?
Thanks in advance.
One more question, can I use it on G955FD?
Click to expand...
Click to collapse
yes this will work if you come from 7.0 too yes
i didnt testet it on g955F cuz i dont have one
greeetings

wkdurrani said:
Will these steps work if I'm on 7.0
Or are these only for people who have already upgraded to oreo b1 / b2?
Thanks in advance.
One more question, can I use it on G955FD?
Click to expand...
Click to collapse
Yes works if coming from 7.0

poczynek said:
Yes works if coming from 7.0
Click to expand...
Click to collapse
Thanks. What about G955FD? Will it work on FD? Or do I have to test it myself?

wkdurrani said:
Thanks. What about G955FD? Will it work on FD? Or do I have to test it myself?
Click to expand...
Click to collapse
Not sure. Just back up in twrp and try.

Not for the 955U???

matthewd769 said:
Not for the 955U???
Click to expand...
Click to collapse
Same as above. As long as you have a TWRP backup on the external sd then give it a try.

poczynek said:
Same as above. As long as you have a TWRP backup on the external sd then give it a try.
Click to expand...
Click to collapse
We currently cant use TWRP ... we only have flashify.

matthewd769 said:
We currently cant use TWRP ... we only have flashify.
Click to expand...
Click to collapse
Ah tricky. You'd need a back up to be safe. Doesn't flashify have a backup option?

Yes.... who cares if i have to re root then beta 2 oreo

I tried with 955U, flashfire cant find the backup file for oreo beta. Only shows my own backup

253simon said:
I tried with 955U, flashfire cant find the backup file for oreo beta. Only shows my own backup
Click to expand...
Click to collapse
Pretty sure you'll need twrp.

Confirm working on G955FD.
Toggle Network Type was not working but is OK after reboot.
However, AdAway is unable to download host files. Searching for solutions, will update if am successful in resolving the problem.
All other root apps I have are working perfectly.

wkdurrani said:
Confirm working on G955FD.
Toggle Network Type was not working but is OK after reboot.
However, AdAway is unable to download host files. Searching for solutions, will update if am successful in resolving the problem.
All other root apps I have are working perfectly.
Click to expand...
Click to collapse
change adaway hosts location to data\ and download and symlink it

SOGKush420 said:
change adaway hosts location to data\ and download and symlink it
Click to expand...
Click to collapse
Thanks for the suggestion.
hosts file location is still system/etc
Just needed to change hosts file permissions to rw-rw-rw- in root explorer and now its working fine.

What about beta 3 for the s8 (not plus)?

Will this trip the knox counter?

azcamm27 said:
Will this trip the knox counter?
Click to expand...
Click to collapse
Installing TWRP will trip it

I need bin/sh to flash it twrp bcz..

i Accidently deleted system/bin/sh/
What can i do please root not work now
My phone Huawei p9lite vnc-l31c185b360 emui 5
Android 7

nadjibbb said:
i Accidently deleted system/bin/sh/
What can i do please root not work now
My phone Huawei p9lite vnc-l31c185b360 emui 5
Android 7
Click to expand...
Click to collapse
Hey, it's all ok dude..
I bet you didn't make a nandroid backup, if yes just restore it !
Not made a backup and rooted with superSU ?
Here on XDA find and try to use 'unSU.zip' file or simply click here. Flash it in recovery,
then if will work re-root the device with your favorite superuser app.
Hope your device will be newly usable.
Let the community know if all gone well...
P.S.: PM are ok but a post can be read by everyone, well done !
P.S.2: THX to @osm0sis for unSU script.
Cheers

Not work :crying: i want the file sh in system/bin/sh i accidentally delated i dont know what i do now
Wifi not work Bluetooth too i need just the file named < sh >

nadjibbb said:
Not work :crying: i want the file sh in system/bin/sh i accidentally delated i dont know what i do now
Wifi not work Bluetooth too i need just the file named < sh >
Click to expand...
Click to collapse
I believe / sh is recoverable only with a backup made previously.
Now you probably need to re-install, even to prevent other possible problems, the entire system.
Save all your files you want to keep and
keep your bootloader unlock code handy (maybe you don't need it).
I can suggest which files to use...
You can still expect some tips from more experienced users ..
You decide.
Cheers