thered closed
Doesn't install here.
Code:
Flashing SuperSU...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
unmount of /system failed; no such volume
ShyPixie said:
Doesn't install here.
Code:
Flashing SuperSU...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
unmount of /system failed; no such volume
Click to expand...
Click to collapse
Had the same error, still installed just fine apparently. Running it now. Root works fine with no problems up to now.
ShyPixie said:
Doesn't install here.
Code:
Flashing SuperSU...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
unmount of /system failed; no such volume
Click to expand...
Click to collapse
install the most current TWRP of @ squi2, you should not have problems, or downloaded zip wrong.
Carlos Arriaga said:
install the most current TWRP of @ squi2, you should not have problems, or downloaded zip wrong.
Click to expand...
Click to collapse
I'm with the last version of twrp, and the downloaded zip is not wrong. I tried to install via adb method. The cm 12 from squid have no problems. I'll put it on my SD and try again.
Why did you fork all my tipsy repos and renamed it to lenoxOs? You state in the op its slimbased, better change to TipsyOs based
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This was a project that would lead to long term. clearly she intended to bring more improvements and more changes. but I thought to bring a first build little changed ruin and break it. not with an apology his will. but I understand the error. and I have to pay.
I close the post and resigned herself to new projects. by misuse of the same.
As long as authorship is maintained and credit is given, no wrong has been committed. Still, it might have been more considerate to call this an unofficial Tipsy build rather than making it look like something entirely original by rebranding it as LenoxOS.
Carlos Arriaga said:
This was a project that would lead to long term. clearly she intended to bring more improvements and more changes. but I thought to bring a first build little changed ruin and break it. not with an apology his will. but I understand the error. and I have to pay.
Click to expand...
Click to collapse
I agree with @skynet11 that no great harm was committed. Sorry if I was a bit harsh. I don't want to discourage you from fiddling with Android. We're all in it to have fun and learn. You can can even keep the LenoxOS name if you'd like, just say that it's your unofficial Tipsy fork, and put it in the regular "Android Development" section instead of the Original Development section.
Forking is a legitimate activity.
Forking and re-branding is also a legitimate activity.
Upstream projects have trademarks. Hence ,it's one of the rules to rebrand the project as soon as it is forked.
Contribution is made upstream via pull requests.
Thread cleaned , locked and moved to general section.
@Carlos Arriaga
In case you want to re-open the thread and continue development ,report this post.
Related
An windows .net application that writes/reads to and from:
/system/media/
/system/customize/resource/
/data/local/
To change the boot screen. Very simple and easy to use.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download in attachments
v1.1.4 - Tick Box Added switch between /data/local/ and /system/media/
v1.1.5 - Tweaked GUI
v1.2.1 - Tweaked GUI again; added /system/customize/resource/ support added help via clicking android.
v1.2.2 - Test button added; launches the phones boot screen
v1.3.5 (BETA) - New UI and rearranged coding. /Glitchy
v2.1.0 - Tweaked UI and Recovery/Backup Directory Selection
V2.1.1 - Fixed Bug
v2.5.1 - /system/ mounting supported, moveable windows
Nobody taking interest?
0*_*0
I am really interested
not just that you & me sharing & developing same idea
.
I'm really happy to see someone interested write android programs
I sent you a message >>> please chick your index
thank you ...
Update
v2.5.1 - /system/ mounting supported, moveable windows.
I am very new to the android hacking community so please forgive my ignorance. But is this a program that allows you to create a boot animation for your device?
NicholasQ said:
I am very new to the android hacking community so please forgive my ignorance. But is this a program that allows you to create a boot animation for your device?
Click to expand...
Click to collapse
Assuming you've rooted your device then yes.
Works lang a charm I finally modified my bootanimation using this. One thing though I made a mistake on the command prior making it work.
adb push bootanimation.zip /system/custom/resource (should be customize) How can I remove that. Btw Thanks a lot 2 thumbs up to you.
How to use (I'm stupid so i need instructions) Please
Ill change that now :L
Depending on your phone it has different locations for the bootanimation.
If you tick all the boxes then hit backup open each file until you recognized one as the one you see at the boot screen then simply overwrite that with a custom one. Keeping a backup of course incase it doesnt work properly.
very nice idea! good job!
NicholasQ said:
I am very new to the android hacking community so please forgive my ignorance. But is this a program that allows you to create a boot animation for your device?
Click to expand...
Click to collapse
It doesn't let you create one, but it can set one recover and backup current ones etc.
please explain more
I don't understand at all how to use it ...... :'(
Ok, so I know for the Nexus S the mount point for /boot is:
/dev/block/mtdblock2
But that's only from looking at BM's rom wiper tool. I tried running "mount" under terminal emulator, but it doesn't list the /boot mount point.
I'm hoping to find the mount point on a kindle fire is why I ask. The cyanogen fastboot wiki mentions that it's mtdblock2, but I don't know if this is the case for all android devices.
Any help is appreciated, thanks!
EDIT - spoke to one dev and he said that /boot and /system should never be wiped. Now I'm confused, maybe it's differences due to it being a different device?
Have you tried to ask the question in kindle fire forum?
Sent from my Nexus S 4G using xda premium
shabgard said:
Have you tried to ask the question in kindle fire forum?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
This question isn't really device specific. The reason I haven't asked it there just yet is because there are more devs floating around in the NS forums.
That and the community there is different. Every other thread is a "bricked" thread, where it seems that a lot of users have no idea what fastboot or adb is. =p
"df" doesn't list it for me, so i doubt it is. However, if you do a fresh boot and type in "dmesg" it'll tell you where it's located right up the top (at least on the Nexus S).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Damn it looks different on the KF:
I'm not sure if that's what I need. I don't know if boot partition 2 = /dev/block/mtdblock2.
Ahh, I'm a super newb at this too.
Thanks for the help though.
Never done (or needed to do) any work with locations like this, especially with android. Sorry i can't help further, but maybe someone else around here can shed some more light for you.
Harbb said:
"df" doesn't list it for me, so i doubt it is. However, if you do a fresh boot and type in "dmesg" it'll tell you where it's located right up the top (at least on the Nexus S).
Click to expand...
Click to collapse
/factory doesn't show with df either, although it shows on GN I think...
Sent from my ice cream powered Nexus S
mount won't show the boot partition, because it's not mounted to the file system afaik.
Try
Code:
cat /proc/mtd
On the NS, it is mtd2, aka /dev/mtd/mtd2.
Boot is where the kernel and ramdisk are stored. If you erase boot, your phone will not boot (go figure).
Then I'm confused, what does the format/ boot function in CWM actually wipe?
erikikaz said:
Then I'm confused, what does the format/ boot function in CWM actually wipe?
Click to expand...
Click to collapse
The kernel
Sent from my ice cream powered Nexus S
DarkhShadow said:
The kernel
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
OH! Shoot, so is there any way to manually wipe that?
the kernel is in the boot.img
This CWM script will reodex any custom ROM.
With BOOTCLASSPATH edit in dexo.sh it can work on any ROM and phone.
Reodexing gives some people perceivable speed up. And it frees data partition from system dalvik cache. So dalvik-cache rebuild is also accelerated.
I ran it with stock kernel (root injected). And had problems with running it on any custom kernel.
http://galaxytree.net/bravomail/universalOdex.zip
Also a good example of output from shell script into CWM console.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great to see new tweaks. For me, flashing this mod went well, but it put me in an endless boot loop. I'm using a Cappy with a Jelly Bean custom rom. I know it's supposed to be "universal", but maybe some ROMs are not compatible. Any suggestions? Hope I can get it to work.
Using the android sdk you will want to try DDMS.bat and see what spew you get while the phone boot loops.
Sounds similar to what I used for all my roms.
Here are some tips I've picked up along my dev experience:
1. Make sure you have at least 50+ mb space free in /system. Else it may not complete and your /system/app and /system/framework folders may not work properly, thus causing many android core processes to force close and rendering your device unusable. If this happens, wipe, reinstall the rom, and delete more things using Root Explorer from /system. Such as unnecessary ringtones/notification sounds in /system/media and unnecessary system apps like *WallpaperChoosers.apk, stock launchers if you aren't using them, and other stuff you don't need. If you aren't sure what it is, don't delete it because it might be important for the use of your phone.
2. Also, it doesn't work on some roms, I'm not exactly sure why. But make sure you read the script's logs to ensure there are no errors. If you are getting mounting errors, make sure your phones /system partition is mounted as r/w (root explorer can do this). If it still doesn't work, try rebooting into recovery and mounting /system in mounts and storage and then try running the script.
3. Just because your phone is now odexed doesn't mean its gonna be a ton faster. In my experience, I found it to be a slight improvement from the original. In most cases it was unnoticable, so don't expect too much.
Cheers!
Sent from my SGH-I897 using xda app-developers app
Holy cow amigo. You started a bunch of threads. A little credit to original author would have been nice if you took the work and revamped it. All credit cause you didn't.
Sharing is caring. But I suggest you put where you got the script, etc, as well as the original author.
edit. upon further review, i see that you did change some things, mainly removing the original header (which is absolutely lame) and made it work with CWM. Also, you set a static BOOTCLASSPATH - which defeats the purpose of this script!!
Let me check my pms and emails. Someone contacted me a long time ago asking me review to their changes. Maybe it was you lol.
Sent from my EVO using Tapatalk 2
I just noticed Razer Dropped the NOV 2021 Build for Razer Phone 2.
macjunkie said:
I just noticed Razer Dropped the NOV 2021 Build for Razer Phone 2.
Click to expand...
Click to collapse
Its that the full update or just a patch ?
flofy22 said:
Its that the full update or just a patch ?
Click to expand...
Click to collapse
Full release.
DOPE!!
i think the kernel we have dont work for this update. i keep getting sdcard fix in notifications..im not going to reformat my sdcard again..=
--back never mind i flash the vold from arter97 and it working..blonde moment
bountyman334 said:
i think the kernel we have dont work for this update. i keep getting sdcard fix in notifications..im not going to reformat my sdcard again..=
--back never mind i flash the vold from arter97 and it working..blonde moment
Click to expand...
Click to collapse
How did you flash the file while on stock kernel?
Using arter97 kernel. it has twrp built-inside
***CORRECTION-___MR6 sdcard does work> have to flash vold.mod from art97 website
bountyman334 said:
Using arter97 kernel. it has twrp built-inside
***CORRECTION-___MR6 sdcard does work> have to flash vold.mod from art97 website
Click to expand...
Click to collapse
The arter kernel causes a boot loop on MR6 for me. Tried multiple fresh installs, too.
Reznor7 said:
The arter kernel causes a boot loop on MR6 for me. Tried multiple fresh installs, too.
Click to expand...
Click to collapse
Trinity causes bootloops for me as well on MR6.
i mood the boot img using magist the boot version mr6 but when try to flash got an error of size not permited
can someone help me with that please im new whit this phone not in the forum never seen this errror message before
so when i wanna update my phone this happens if i execute the flash_all.bat...any idea what to do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HomuraEngetsuka1995 said:
so when i wanna update my phone this happens if i execute the flash_all.bat...any idea what to do?
View attachment 5197819
Click to expand...
Click to collapse
install adb quick installer or move the adb.exe and fastboot.exe inside the folder with the imgs
clean install of mr6 the other day, no issue rooting with r12. no issue with cd card either but not using exfat
Disappointed by lack of LDAC still
It started 3 months ago, suddenly my tablet reboots while in sleep mode. And whenever i run the built in mobile manager to clean tablet, i always see in the cleaning list "system UI" im thinking maybe something wrong with that or maybe an app is doing it.
If someone suggests to reset the tablet and get into safemode, i want to avoid that because of the time and money adding apps that cost me money not to mention the gallery filled with precious images. But if that is the only option, i would need to confide to self for a lengthy timeframe
Need use wakelock app
See #206 and below in this thread
LineageOS 16.0 | 19.04.2020 | Shield blobs
LineageOS 16.0 Requirements: 1) active system1 2) merged system partition 3) BRAIN, READING SKILL and presence of basic knowledge about firmware (in the absence need learn to independently) Instruction 1) download TosForPSCI-0.1.zip...
forum.xda-developers.com
I found the app and saved in wishlist...but the app was updated in 2018 ill check it out, thx
Wakelock Revamp*
Thx, but as of now i cant access the google playstore . Its down on my end. Error message says "retry" I may have to do a hard reset to clear up problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
can anyone tell me whats going on with the playstore app?
BPF6450 said:
Thx, but as of now i cant access the google playstore . Its down on my end. Error message says "retry" I may have to do a hard reset to clear up problemView attachment 5231485 can anyone tell me whats going on with the playstore app?
Click to expand...
Click to collapse
GitHub - d4rken-org/wakelock-revamp: Rewrite of https://github.com/d4rken/wakelock
Rewrite of https://github.com/d4rken/wakelock. Contribute to d4rken-org/wakelock-revamp development by creating an account on GitHub.
github.com
Which to click on?
eu.thedarken.wldonate-v3.2.0.3020000.-RELEASE-570b9d7.apk
Or source code (zip)
BPF6450 said:
Which to click on?
eu.thedarken.wldonate-v3.2.0.3020000.-RELEASE-570b9d7.apk
Or source code (zip)
Click to expand...
Click to collapse
apk, also p.m. ed you
Thx for reply and the pm. Let us hope i can once again take control. As well as look into the other options mentioned in pm
UPDATE
the google playstore app is beyond repair. The source of the constant rebooting because it is corrupt. Luckily was able to get an apk repair app and update store apps, minus the playstore app. i used to frown using external apk/ xapk files but right now i have no choice