Related
how to make a flashable rom/firmware from the images from romdump.
need it for my rk3188 tablet.
thanks
th3f33 said:
how to make a flashable rom/firmware from the images from romdump.
need it for my rk3188 tablet.
thanks
Click to expand...
Click to collapse
Depends
Whats The Main Device
Screen DPI
Kernel
Droid Version
Pranto Roy said:
Depends
Whats The Main Device
Screen DPI
Kernel
Droid Version
Click to expand...
Click to collapse
Device is:
Skyworth skypad x7010 , rk3188 quad, 2gb ram, 8gb storage
DPI - 160
Kernel - i dont know, still using the stock...
running on jellybean 4.1.1
th3f33 said:
Device is:
Skyworth skypad x7010 , rk3188 quad, 2gb ram, 8gb storage
DPI - 160
Kernel - i dont know, still using the stock...
running on jellybean 4.1.1
Click to expand...
Click to collapse
Is It The main device's or your's??
Pranto Roy said:
Is It The main device's or your's??
Click to expand...
Click to collapse
its mine,
i have stock images from rom dump
but it is soft bricked as of now.. due to some build.prop errors or maybe when i set the cpu minimum frequency state...
.
th3f33 said:
its mine,
i have stock images from rom dump
but it is soft bricked as of now.. due to some build.prop errors or maybe when i set the cpu minimum frequency state...
.
Click to expand...
Click to collapse
If Both Build.prop 's are of same droid version replace it with your phone's
cpu won't Matter
thanks for the replys
Pranto Roy said:
If Both Build.prop 's are of same droid version replace it with your phone's
cpu won't Matter
Click to expand...
Click to collapse
yeah i would really like to do that, to keep my save files in some rpgs i played, but i had this problem where i cant access the tablet thru adb, although i am rooted, usb debugging is on, and have installed the right / working/ correct adb drivers for my device although i was supposed to be able to do it before, i dunno what had happened to it,
maybe it happened somewhere during my initial setup of factory restore - root - clear bloat apps - clear cache - factory restore,
but i can access the tablet with adb when it is turned off, but even though i can access it with adb, cant seem to push any file anywhere, and cant use SU command, it just goes blank, and adb root / adb remount not working too, adb root says cannot run in production build and remount is not having permission.
i also checked the default.prop and it says
ro.secure=1
ro.debuggable= 1
when i check the adb devices when the tablet is off, it says
name - device
no access to recovery mode anymore, can only access the device in off state and flash state, (rkbatchtool flash state - green)
whenever i try to push the recovery button (Power + Volume Up, used to be working before i flashed the incorrect recovery) it ends up in the flash mode.
when the device is turned on and stuck in grey screen after logo, it can be detected in the windows as android adb interface but adb devices doesnt detect the tablet, even after i restart the adb thru adb kill-server adb start-srver
th3f33 said:
yeah i would really like to do that, to keep my save files in some rpgs i played, but i had this problem where i cant access the tablet thru adb, although i am rooted, usb debugging is on, and have installed the right / working/ correct adb drivers for my device although i was supposed to be able to do it before, i dunno what had happened to it,
maybe it happened somewhere during my initial setup of factory restore - root - clear bloat apps - clear cache - factory restore,
but i can access the tablet with adb when it is turned off, but even though i can access it with adb, cant seem to push any file anywhere, and cant use SU command, it just goes blank, and adb root / adb remount not working too, adb root says cannot run in production build and remount is not having permission.
i also checked the default.prop and it says
ro.secure=1
ro.debuggable= 1
when i check the adb devices when the tablet is off, it says
name - device
no access to recovery mode anymore, can only access the device in off state and flash state, (rkbatchtool flash state - green)
whenever i try to push the recovery button (Power + Volume Up, used to be working before i flashed the incorrect recovery) it ends up in the flash mode.
when the device is turned on and stuck in grey screen after logo, it can be detected in the windows as android adb interface but adb devices doesnt detect the tablet, even after i restart the adb thru adb kill-server adb start-srver
Click to expand...
Click to collapse
Complex Problems
Don't Think Can Be Solved At Home
Contact Customers Care
RE:
well i dont think i can do that because
skyworth is a chinese company, and they dont have a good support for the tablets they've released, i cant understand chinese/cantonese/mandarin too
in our local provider, i also have used the most of my warranty,
rooting/flashing the tablet voids the warranty
even though i had sucessfully made them replace my first tablet due to soft-bricking it, all i did is made the tablet bootable only to flashmode, and they didn't even understand/tracked what i had done, all they did was mark the device as faulty mobo then replaced it with a new one,
so right now i am asking for the online community in some help on how to restore it,
oh btw i have the stock romdump images of it. during the state where it is 100% working.
Pranto Roy said:
Complex Problems
Don't Think Can Be Solved At Home
Contact Customers Care
Click to expand...
Click to collapse
can you instruct me on how to make an update.zip that will replace the build.prop with my default build.prop from what ive learned, it is possible to make one right?
th3f33 said:
can you instruct me on how to make an update.zip that will replace the build.prop with my default build.prop from what ive learned, it is possible to make one right?
Click to expand...
Click to collapse
Possible But Can't Say If It Will Work.
Upload Your Build.prop
I'll Be Quite Late Though
Pranto Roy said:
Possible But Can't Say If It Will Work.
Upload Your Build.prop
I'll Be Quite Late Though
Click to expand...
Click to collapse
here it is.. oh i forgot to rename it to build.prop, it is a backup made weeks ago..
'well i've tried adding an update.zip and I dont think i can use it anyways, i think i need to find a way to flash the romdumps that i have.'
th3f33 said:
here it is.. oh i forgot to rename it to build.prop, it is a backup made weeks ago..
'well i've tried adding an update.zip and I dont think i can use it anyways, i think i need to find a way to flash the romdumps that i have.'
Click to expand...
Click to collapse
Allow Me 24 Hours
As Its Mid-Night In My Country I'll Do It Tomorrow
Pranto Roy said:
Allow Me 24 Hours
As Its Mid-Night In My Country I'll Do It Tomorrow
Click to expand...
Click to collapse
ok its already 2:51 am here, cant sleep without my tab running
still reading a lots of forum topics related to my problem...
RE:
I got my access back to the device thru adb
what i did was added the dev id of my device in the adb_usb.ini
now i can push files back to it
now i need to it to the working state
So you want to keep (knox) warranty and still use root?
Well there is RDLV and the "forbidden" Tool for that, BUT you will still have SELinux on enforcing mode, which means you don't have full control even with root. While technically most things still do work, they might work a lil different or need a different approach.
Lets collect our findings here...
---
First of all, remounting system with apps like solid explorer does not seem to work.
A workaround for this is to run the following command in terminal or through quick terminal etc:
Code:
/system/bin/mount -o rw,remount /dev/block/mmcblk0p2 /system
This command gets through where other methods fail. Once you have mounted the system writable like this, you can go back to your root explorer app to delete things etc on system partition. Solid explorer gives me error messages still when I delete apps from /system/app/, but they still disappear / get deleted.
---
This also brings me to my next workaround:
To delete system apps and not just freeze them with Titanium, you need to remount system like above and then delete the apks from the /system/app/ directory. A reboot should then remove everything else related to that app afaik. (like the /data/data/ of the app etc.)
Titanium on the other hand gives me an error when I try to delete a system app, even after remounting system to rw.
---
If you want to edit things from your system partition, like build.prop etc. Copy them to your sd first and edit them there. Then mount system rw, and create a backup of the file you are editing. (make a copy and just append "_bak" or smth to the file name) And finally copy the sd file over the corresponding file in system. Make sure you check permissions before and after you copied everything and edit them if they do not match up.
---
My final Tip for now:
I noticed that most root methods on SELinux (this includes RDLV and the forbidden one) use install-recovery.sh to start su as a system daemon which handles all the su requests. (as far as I understood it at least).
Well we can also use this file (or create an install-recovery-2.sh in /etc/ which gets called by the first one by default when you got the root) to run init.d scripts or other stuff.
I don't have tested it yet but I will put the code below once it works...
Code:
tbd
..
hopefully we find a way to turn off this selinux enforcing mode while keeping knox warranty at some point.. - xposed framework might be the answer but not sure - in theory its able to overwrite all methods used by apps. (but I guess selinux above xposed still in system rights and therefore cannot be affected by it?)
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Glad to see you still at it homie. Kingoapp is great. "Google kingoapp" anyone needing help. Just don't post any links please.
Sent from Heaven.
dallastx said:
Glad to see you still at it homie. Kingoapp is great. "Google kingoapp" anyone needing help. Just don't post any links please.
Sent from Heaven.
Click to expand...
Click to collapse
Definitely try out at least the dpi change to 360 or 400, that one is golden =). (nothing special but still..)
--
so far I haven't found anything that does not work at least with a workaround. Some apps do not work as supposed, but thats because they havent adapted yet to the new environment as far as I can tell. And yea, you cannot edit the selinux stuff or turn it off (at least not easy) but thats it. What I did not yet try, which is for risk-friendly people only anyway, is to mess with the efs folder. (you can change your devices mac there, good for privacy concerns hehe). Could be that selinux blocks that one as well, but other than that most things work alright. Just no custom recovery yet, but this could maybe be made possible through the install-recovery.sh file, telling it to start up a custom recovery but not actually flashing it hard onto the device.
Reboot apps I can't get to work. You know the apps that restart phone, bootloader etc... Even through the side 4 button mod. I can only reboot through factory restart. Pressing the power button and using the default restart button.
Sent from Heaven.
---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------
Yea I always do DPI changes for Gmail , browser, settings, and few other apps
Sent from Heaven.
aww yea youre right - I havent got any app to reboot the phone yet, only the normal reboot through the stock power menu works for me. Didnt try terminal yet.
Maybe not "reboot" but "shutdown -r now"
dallastx said:
Reboot apps I can't get to work. You know the apps that restart phone, bootloader etc... Even through the side 4 button mod. I can only reboot through factory restart. Pressing the power button and using the default restart button.
Click to expand...
Click to collapse
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
TheAvatar said:
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
Click to expand...
Click to collapse
Yea i tried it but didnt work... It may of been conflicting with other apps. But what root method are you using?
---------- Post added at 07:16 PM ---------- Previous post was at 07:11 PM ----------
JohnnyRebel said:
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yea i have always got out of download mode on Note 3 by just holding power button.
---------- Post added at 07:20 PM ---------- Previous post was at 07:16 PM ----------
zroice said:
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Click to expand...
Click to collapse
Only reason i wouldn't change the DPI for everything because some apps will look crazy. Then you will have apps also like the play store that may not work correctly.
JohnnyRebel said:
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
good finding! (lol i couldve came up with this myself lol - holding power long enough always does a forced reboot).
I noticed too that when you pull the battery that sometimes you get lines on the screen - really scary, thought I messed up my device but after like 10 seconds or so they disappeared. But definitely something you want to avoid!
Holding down power to exit the download mode instead of pulling battery from now on.
I use Rootr Browser Pro... I can delete things out of the system partition and write into the system partition (after setting it for root privelege in settings and supersu) however I can''t just overwrite files.... The file I wish to overwrite must 1st be deleted or renamed,usually with .bak. Haven't had to use terminal.
Another handy tip, in the CSC folder, rename the customer.xls to customer.xls.bak and then a new option will be available in the settings/device/lock screen menu to add app shortcuts to the lock screen
if you add this code to the others.xml file AFTER <FeatureSet> and BEFORE </FeatureSet>
<CscFeature_Sip_UseSymbolInCMKey>true</CscFeature_Sip_UseSymbolInCMKey>
<CscFeature_Sip_EnableSymbolInSecondary>en_GB;en_U S;de;fr;es;it</CscFeature_Sip_EnableSymbolInSecondary>
You will then enable sub symbols on the default keyboard.
Works a dream...
TheAvatar said:
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
Click to expand...
Click to collapse
wait a minute - the 4 way reboot does work for you? Are you on Knox 0x0 still? And SELinux status enforcing? For me no "reboot" apps seem to work. They all just try to reboot (and SELinux denies it then most likely)
---
one other problem occured: when using xprivacy and deinstalling an app the system locks up. Can someone confirm this?
Why do people insist on DELETING apps from system? Just use pm disable, sheesh.
khaytsus said:
Why do people insist on DELETING apps from system? Just use pm disable, sheesh.
Click to expand...
Click to collapse
The xprivacy lockup also happens with user apps deinstallation. Just want to make sure its not me or my setup but xprivacy thats causing this. I turned it off and it works, turn it on, device hangs on deinstallations.
zroice said:
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Click to expand...
Click to collapse
Yeah, thanks for the tip. I used xpose app setting to set my nova launcher to be about 400. I will try modify the build.prop then.
Ok so what i did to quickly update to mj4 since it is now live. "you will lose root and everything on internal storage so back it up"
Be sure make COPY of backup of your titanium folder if use NOVA be sure to do a backup of your current layout. Copy these folders to your EXTsd. Remove card afterwards.
I was rooted so i kept getting "Cant up dated Modded system". Even unrooting i cant getting Modded system. I use almost the same root method as OP uses called kingoapp "cant provide links so google is your friend"
Anyhow.. i wanted to make sure i didnt trip KNOX and grew impatient for an update.zip. I didnt want to flash anything through ODIN, so i figured would use Kies.
Kies will see your phone as already updated. At the top of the app if you click tools then "firmware and initialization" Kies will override whatever is on your phone and update to mI5. This will take about 30 min but much quicker then trying to download the entire stock firmware from hotfile.
Once your phone is up go ahead and go to to settings on you phone and system update. Update will run and restart your phone. You are now on the latest firmware mj4.
Reroot and reinstall SD card. You are now rooted on latest update.
Notes - I tried everything to try to trick system to thinking its not modded including unrooting. Nothing worked reasoning i resorted to flashing through Kies.
dallastx said:
Ok so what i did to quickly update to mj4 since it is now live. "you will lose root and everything on internal storage so back it up"
....
Click to expand...
Click to collapse
Ohh theres an update? Well I bought a 2nd note today - couldnt resist it was 500€ only (they usually go for about 550 here). And mine had some display issues... gonna sell the first one and keep second - screen is better. Anyway, I got to redo everything now and restore the "old one" to stock.
To restore stock safely I would always suggest using Kies and doing a forced firmware update like dallas described. I read that flashing the same firmware twice with odin can already trip knox. (at least if you were tempering with the system)
But note that this will most likely update the bootloader of your phone as well.
---
Now I got the old bootloader on my new and still branded n3 - can someone explain what the difference actually is to the new bootloader? I mean both don't allow SELinux permissive, and both can be rooted (at least with the "tool")?
On S4 etc I understand that new firmware version introduced knox, and that there was firmware out without knox, but if you upgraded once you couldnt go back. But there are no knox free firmwares for the n3 are there? (I mean stock ones)
zroice said:
Ohh theres an update? Well I bought a 2nd note today - couldnt resist it was 500€ only (they usually go for about 550 here). And mine had some display issues... gonna sell the first one and keep second - screen is better. Anyway, I got to redo everything now and restore the "old one" to stock.
To restore stock safely I would always suggest using Kies and doing a forced firmware update like dallas described. I read that flashing the same firmware twice with odin can already trip knox. (at least if you were tempering with the system)
But note that this will most likely update the bootloader of your phone as well.
---
Now I got the old bootloader on my new and still branded n3 - can someone explain what the difference actually is to the new bootloader? I mean both don't allow SELinux permissive, and both can be rooted (at least with the "tool")?
On S4 etc I understand that new firmware version introduced knox, and that there was firmware out without knox, but if you upgraded once you couldnt go back. But there are no knox free firmwares for the n3 are there? (I mean stock ones)
Click to expand...
Click to collapse
Yea go ahead and do all your updates then root. I think the update may me just for Sprint N900p.
so there is still no way to get rid of "enforcing selinux" without tripping knox counter?
need this only to get my OTG cable to USB OBD working, seems SELinux is blocking serial usb communication :/
zroice said:
wait a minute - the 4 way reboot does work for you? Are you on Knox 0x0 still? And SELinux status enforcing? For me no "reboot" apps seem to work. They all just try to reboot (and SELinux denies it then most likely)
Click to expand...
Click to collapse
Sorry for the late reply. I was Knox 0x0, used Root De La Vega, installed xposed framework then grabbed wanam from the play store. Just had to enable it and it was all good.
Hello Guys,
Today I was training to put my DPI higher, so my grandfather could see the screen.
Sadly when I booted with a DPI of 720, the process 'Trebuchet' stops.
The message of it, will continue again and again.
Do you guys maybe know how I can change my DPI back? (Using Recovery or bootloader)?
Thanks!
Try all winner apk. Not sure but might be it can help u.
vipsy6 said:
Try all winner apk. Not sure but might be it can help u.
Click to expand...
Click to collapse
I cannot boot my phone, so using an app is not a option.
The only thing I can do is use Bootloader and TWRP (recovery).
martijn.v said:
I cannot boot my phone, so using an app is not a option.
The only thing I can do is use Bootloader and TWRP (recovery).
Click to expand...
Click to collapse
Use adb, connect device to computer, adb shell, cd/system, open build.prop by using nano build.prop change DPI back to required value Ctrl x saves the file. Exit to get out of adb shell and reboot phone.
robt77 said:
Use adb, connect device to computer, adb shell, cd/system, open build.prop by using nano build.prop change DPI back to required value Ctrl x saves the file. Exit to get out of adb shell and reboot phone.
Click to expand...
Click to collapse
At his moment, I got another problem.
All the adb commands return: "error: device not found".
The USB Debugging is on, to do that, I used "setprop persist.service.adb.enable 1".
But now it still does not find the device.
martijn.v said:
At his moment, I got another problem.
All the adb commands return: "error: device not found".
The USB Debugging is on, to do that, I used "setprop persist.service.adb.enable 1".
But now it still does not find the device.
Click to expand...
Click to collapse
That is not good. can you boot into recovery? if so you can dirty flash ROM and it will change the DPI
robt77 said:
That is not good. can you boot into recovery? if so you can dirty flash ROM and it will change the DPI
Click to expand...
Click to collapse
Yes, I can boot into recovery. Right now im trying to change build.prop using the terminal. But that doesn't work out yet.
try this: https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi
aboicu said:
try this:
Click to expand...
Click to collapse
If you read my post, you could've seen that I cannot boot my phone.
So using that app will not help.
Extremely sorry that i have ignored that
Sent from my MT11i using XDA Premium 4 mobile app
171
Could somebody upload his/her build.prop?
I think that would do the job.
Sorry for my answer to your problem... I want to say that next time when you want to modify the DPI use the above app. Anyway, whatever...
I fixed it, with flashing a new rom.
After 20 tries, I could copy the .zip to my /sdcard/ folder and I could flash it.
Thanks for trying to/the help.
How can I disable soft keys backlight without power saving? Is no longer in the settings of the Galaxy s6.
I don't believe theres a setting for it, I've looked and looked, I like to set it to 6 seconds but its nowhere to be found.
Yeah I think you need to root and install a custom Rom or xposed (if that's possible yet)
Please refer to my earlier post at http://forum.xda-developers.com/showpost.php?p=60009456&postcount=12 and/or use the search function.
The ATT version has this setting under Display. It's weird that the other versions don't have that setting.
How can I run adb for this fix? Can some one help me to run adb..
The post above has instructions on how to to that
I just ran terminal emulator from my phone and entered "settings put system button_key_light 0" and they are disable for good.
Capacitive Lights Off
Two ways ,
1. The observe the power saving mode turns it off by default.
2. This message is from the user/developer @Averix in one of the S6 thread,
"That thread covers the ADB method. I wrote an app that doesn't require root to set the values to whatever you want from .5 - 10 seconds on, off/on all the time."
Galaxy Button Lights
Hope this helps
nappent said:
I just ran terminal emulator from my phone and entered "settings put system button_key_light 0" and they are disable for good.
Click to expand...
Click to collapse
Are you rooted? Doesn't work for me.
knitler said:
Are you rooted? Doesn't work for me.
Click to expand...
Click to collapse
Does the app not work on your device?
knitler said:
Are you rooted? Doesn't work for me.
Click to expand...
Click to collapse
Use the app in the post above yours, I'm not rooted and it worked fine for me
Sent from my Verizon S6,
formerly abdel12345
Is it possible using adb?
bump! Some mobiles like my Oneplus can use an adb command? Is it possible with z5?
varun.gid said:
bump! Some mobiles like my Oneplus can use an adb command? Is it possible with z5?
Click to expand...
Click to collapse
Yes, it is possible. I did that myself (however on a Xperia Z5 Compact, but I think it doesn't matter). Use "adb shell wm density xxx".
If you don't like the density from the cmd atlantix1 provided then u can use "adb shell wm density reset" which takes it back to default. You also need to know that by using this method of changing dpi isn't supported with all aps so some things will look funny such as contacts app and if u use swiftkey. The best way to change dpi is still with root in the build.prop file.