Related
I'm looking for any ROM to work on the Hero i deleted the fonts from.
any rom that has valid signature and i can flash it and get the fonts back?
Thanks
Bashar . said:
I'm looking for any ROM to work on the Hero i deleted the fonts from.
any rom that has valid signature and i can flash it and get the fonts back?
Thanks
Click to expand...
Click to collapse
take a rom, open it with winrar or any extractor and take /system/fonts out of the zip..
(if you need sense fonts, use a flashable zip sense rom, otherwise AOSP)
AOSP fonts do also work on sense, the names are the same
root your phone..
then set up adb , some good guides here on the board..
connect phone with usb, no sdcard mounting
now:
Code:
adb remount
adb push yourfont.ttf /system/fonts
(repeat as long as you have ttf files: might work if you use *.ttf)
adb reboot
if you don't want to root, i don't know how to do it
EDIT: hope you are already rooted because with no fonts, how would you root your phone,
or install the necessairy files.. didn't notice it yet
grtz
that was not possible
i had to downlaod last rom at http://www.htc.com/uk/supportdownloadlist.aspx?p_id=283&act=sd&cat=all , install it back to 1.5, then upgrade all the way OTA till latest version for it (a.k.a 2.1) , now back to normal
unfortunately had todo it via windows
Bashar . said:
unfortunately had todo it via windows
Click to expand...
Click to collapse
you can setup adb in windows..
He used the RUU
@Bashar, if you root it again and want to experiment. Make sure you got a custom recovery. Easier to solve mess I guess You can create back-ups of your normal ROM in it as well. Anyway, glad it is back to normal.
riemervdzee said:
He used the RUU
@Bashar, if you root it again and want to experiment. Make sure you got a custom recovery. Easier to solve mess I guess You can create back-ups of your normal ROM in it as well. Anyway, glad it is back to normal.
Click to expand...
Click to collapse
Thank you
i installed rom manager and trying to get clockworkMod installed but doesn't seem gets there when i reboot, any idea why ?
EDIT: everytime i reboot into recovery even if manually using the ClockworkMod i get Android System recovery <2e>
I keep getting status 7 errors when I try to update my CM install on my i9505 international, (i'm using latest philz recovery). So far I have solved the problem by doing a full wipe and a ROM prep wipe. This is obviously not great because I have to set up the phone from scratch.
For various reasons I do not have access to a computer so cannot do the unzip / modify / rezip solutions referred to in many posts.
Is there another way i can update to the latest nightly builds? And what is causing this problem?
Thanks for help
as far as i know this is because the rom is build for us t-mobile edition.
you need to delete one line ... otherwise it won't work. so you need a computer for this.
also full wipe isn't enough. also delete preload and system.
hope this helps
birdr said:
I keep getting status 7 errors when I try to update my CM install on my i9505 international, (i'm using latest philz recovery). So far I have solved the problem by doing a full wipe and a ROM prep wipe. This is obviously not great because I have to set up the phone from scratch.
For various reasons I do not have access to a computer so cannot do the unzip / modify / rezip solutions referred to in many posts.
Is there another way i can update to the latest nightly builds? And what is causing this problem?
Thanks for help
Click to expand...
Click to collapse
You can do everything you need on your phone. I use Root Explorer to unzip, delete the format line and zip. Works fine if you do that and it's pretty easy to do.
chrisknife said:
as far as i know this is because the rom is build for us t-mobile edition.
you need to delete one line ... otherwise it won't work. so you need a computer for this.
also full wipe isn't enough. also delete preload and system.
hope this helps
Click to expand...
Click to collapse
That's not true and it's not why anyway. It's a problem with the recovery.
do you have any nfo ( workaround) how the update procedure can be done?
3bs11 said:
You can do everything you need on your phone. I use Root Explorer to unzip, delete the format line and zip. Works fine if you do that and it's pretty easy to do.
That's not true and it's not why anyway. It's a problem with the recovery.
Click to expand...
Click to collapse
ok sorry then...
i thought it's the same like on aokp nightlies.
for me it helped to delete preload and system...
had this error before too. after formating this it worked.
Thanks all. I got this working based on the advice given.
Precisely:
1. I extracted the nightly using ES file explorer.
2. I used a text editor to remove the line
format("ext4", "EMMC", "/dev/block/mmcblk0p16", "0", "/system");
from
/META-INF/com/google/android/updater-script
3. Then I re-zipped using ES file explorer.
4. Then i flashed as normal with philz recovery, wiped cache and rebooted.
Worked first time and everything upgraded as expected.
Thanks again for the help.
Hello,
Sorry, I have to post this workaround here because I'm new on xda and I can't post an answer on the development forums. So if someone see that, please post a link to this thread on PAC ROM or pink kernel topic
It seems there is a new file in the modules directory which is a symbolic link named wlan.ko. As an easy workaround, simply replace this file (/system/lib/modules/wlan.ko) by this one: /system/lib/modules/pronto/pronto_wlan.ko (move this file to the parent directory and rename it). Then reboot, you should have the WiFi working now
PS: I guess it's maybe better to modify the symlink or load the correct module but it's harder to write command lines with a smartphone
According to some people, this bug should be fixed now.
Doesn't work!
Sadly, doesn't work on PA/C-RoM.
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.
Mycroft-Dev said:
Sadly, doesn't work on PA/C-RoM.
Click to expand...
Click to collapse
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko
matttbe said:
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko
Click to expand...
Click to collapse
Well, Wi-Fi still refuses to work after removing the symlink!
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Cheers, mate!
Mycroft-Dev said:
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Click to expand...
Click to collapse
No :-/
Maybe you can try to reinstall the latest nightly version of your rom (released after March 20th -- I think it's the case for C-RoM), reboot and check if the WiFi is working. If yes, don't disable it now then reinstall the latest version of Pink kernel.
But if the WiFi is still not working, it's annoying... You can reformat /system where kernel modules are installed but I think it's automatically done when installing a rom. Maybe they are not using the latest version of the kernel?
Mycroft-Dev said:
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.
Click to expand...
Click to collapse
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").
Clarification
matttbe said:
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").
Click to expand...
Click to collapse
As in, I repacked the kernel, and then flashed it.
I'll try tweaking a bit here and there, and let you know how it goes.
And yes, I flashed the latest C-RoM.
So after lots of flashing of different roms on my Moto G 2nd gen (XT1068) I ended up unable to turn WIFI on in any rom, including stock!
Thing is, after days of breaking my head with this, I figured out I was missing the WCNSS_qcom_wlan_factory_nv.bin file from the /Persist folder.
How did that file go missing and why it was not restored when restoring to stock or flashing roms? Dam good question, I don't have an answer to that yet, BUT, I have a fix.
Simply download the attached .rar, unzip it, and manually put the WCNSS_qcom_wlan_factory_nv.bin file in your /Persist folder using any root explorer / file manager on your device and reboot!
Such a simple little thing gave me so much trouble, hope this will help future users who might face the same problem, as I already saw around that other people are also having the same issue.
This should work for any Moto G version, even the 2013 model, XT1063, XT1064, XT1068, XT1069, all share the same WIFI file.
Happy surfing on your now working WIFI!
Nice Work!
I have that file in /persists but still no WiFi.
Obagleyfreer said:
I have that file in /persists but still no WiFi.
Click to expand...
Click to collapse
Most likely its the perms issue. If you have 'adb' and can connect to the phone using adb, do this:
adb logcat -d -v time | grep "avc: denied"
right after a fresh start. If the file shows up in that grep, it means that you are running into permissions issue. And it can be fixed if you have root.
Where cn i find persist folder... ??? I m using CM12
Sent from my Moto G 2014 using XDA Premium 4 mobile app
immy8796 said:
Where cn i find persist folder... ??? I m using CM12
Sent from my Moto G 2014 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Root of your device,
/persist
Exelios said:
Root of your device,
/persist
Click to expand...
Click to collapse
Found it... Thanx.. bt which permission i hv to give that .bin file.. ???
Sent from my Moto G 2014 using XDA Premium 4 mobile app
immy8796 said:
Found it... Thanx.. bt which permission i hv to give that .bin file.. ???
Sent from my Moto G 2014 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine is 777, read write execute to everyone, probably not the right cmod, but it works
after try like 5 kernels and almost start to crying i found this post
AND WORKS!!!!
Thanks you so much!!
ZenKeep said:
after try like 5 kernels and almost start to crying i found this post
AND WORKS!!!!
Thanks you so much!!
Click to expand...
Click to collapse
O yeah I know the feeling, went trough the same, glad I helped!
Also pressing the tnx button on my post would help me!
I already have persist folder and file in root directory and overwrite it with rw-r-r permission but still not working plz help.
HELP!
I have restored to stock firmware, and my wifi just turns off when i turn it on. I think i am missing this file but as im on stock I dont have root access. How can i install this file if i dont have root access.
A quick reply would be amazing!
Thanks
mrangryoven said:
I have restored to stock firmware, and my wifi just turns off when i turn it on. I think i am missing this file but as im on stock I dont have root access. How can i install this file if i dont have root access.
A quick reply would be amazing!
Thanks
Click to expand...
Click to collapse
You could just root again. Using super su you can unroot using the super su app after you finish the fix.
Sent from my XT1064 using Tapatalk
still have the same issue. stock rom and stellar kernel
Thank you man, this really worked!!! You saved my ass!
PS: I have another problem similar to this one. I can' t acces to my mobile network, I have them turned on, but when I press on Network operators, a message pops up saying "Error while searching for networks ". Have you ever encountered this problem? Because I can' t find an answer
sumit227 said:
I already have persist folder and file in root directory and overwrite it with rw-r-r permission but still not working plz help.
Click to expand...
Click to collapse
I also tried to reload the stock boot.iso but that did not help me in this case. In the end what fixed this issue for me was to wipe the phone and load cyanogen mod 12.1.
I downloaded the following files to my phones SDCARD before starting the process below.
cm-12.1-20150816-NIGHTLY-titan-recovery.img
cm-12.1-20150816-NIGHTLY-titan.zip
gapps-5.1-arm-2015-07-17-13-29.zip
0) reboot into fastboot
1) fastboot flash recovery cm-12.1-20150816-NIGHTLY-titan-recovery.img (this was done from the command line on my Mac, and that file was on my Mac at the time)
2) reboot into recovery
3) choose "Wipe data / Factory Reset"
4) choose "Apply Update" -> "Choose From SDCARD1 -> "cm-12.1-20150816-NIGHTLY-titan.zip"
at this point I rebooted but could have probably installed GAPPS right away. The wifi was working again at this point!
5) choose "Apply Update" -> "Choose From SDCARD1 -> "gapps-5.1-arm-2015-07-17-13-29.zip"
I think I will stick with CM for now. I've used it in the past and it was fine.
jreeve0805 said:
I also tried to reload the stock boot.iso but that did not help me in this case. In the end what fixed this issue for me was to wipe the phone and load cyanogen mod 12.1.
I downloaded the following files to my phones SDCARD before starting the process below.
cm-12.1-20150816-NIGHTLY-titan-recovery.img
cm-12.1-20150816-NIGHTLY-titan.zip
gapps-5.1-arm-2015-07-17-13-29.zip
0) reboot into fastboot
1) fastboot flash recovery cm-12.1-20150816-NIGHTLY-titan-recovery.img (this was done from the command line on my Mac, and that file was on my Mac at the time)
2) reboot into recovery
3) choose "Wipe data / Factory Reset"
4) choose "Apply Update" -> "Choose From SDCARD1 -> "cm-12.1-20150816-NIGHTLY-titan.zip"
at this point I rebooted but could have probably installed GAPPS right away. The wifi was working again at this point!
5) choose "Apply Update" -> "Choose From SDCARD1 -> "gapps-5.1-arm-2015-07-17-13-29.zip"
I think I will stick with CM for now. I've used it in the past and it was fine.
Click to expand...
Click to collapse
This also worked for me, loaded the latest CM nightly and Wifi came back. Previous steps outlined in this thread did not work.
Had issues with Moto G2 wifi after rooting.. wotks fine after Blisspop
Tom flash
Sent from my SM-T231 using XDA Free mobile app
pls help
persist folder gets removed every time i put it there using root explorer... when i click add new folder into the / (persist is not there) and type in persist it creates a folder with the files already there then i quit the explorer and come back only to find out the the folder is not shown there anymore but if i created again is gets in there and has all the files but again when i quit it disappears...
---------- Post added at 08:48 PM ---------- Previous post was at 08:25 PM ----------
Tel864 said:
You could just root again. Using super su you can unroot using the super su app after you finish the fix.
Sent from my XT1064 using Tapatalk
Click to expand...
Click to collapse
pls help me i have the folder but its not shown in the explorer it only shows when i add new folder and name it persist but then it disappears again
WiFi turns off instantly I try to turn it on
I have the same issue like you guys, and i've already try to copy the file to the /persist folder, with all the permissions... and nothing but error message pop ups (I can't modify the files in the folder, but accidently I erase one of the WCNSS files. It doesn't make any sense)
I've also tried to install the stock firmware to my XT1068, several ROMs with LP 5.0.2, 5.1, etc (everytime doing wipe cache and data); and the issue is still going.
What can I do? Downgrade to KK can restore all the missing files?
Maybe I can copy a /persist folder entirely with all the files... I don't know.
I'm running out of ideas! And I don't want to live with the idea of 'no-wifi' in such an excellent phone! :crying:
Thanks for your time, guys!
I'm proud to present the first dual boot project for the all Exynos7870 and Exynos7880-based Samsung devices. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Here is the latest build : https://www.androidfilehost.com/?fid=962021903579496224
XDA:DevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
lzzy12
Source Code: https://github.com/Mysteryagr/DualBootPatcher
Version Information
Status: Beta
Created 2017-12-03
Last Updated 2017-12-03
thanks bro ,Great Work
Wow Good Work Bro It Will Be Very Useful For Us Bro
??
Great
got error 1 when flashing lineage as second rom
Tried it. It works if I flash the ROM from recovery but if I want to switch to primary using DualBoot utilities it doesn't work. Fortunately I had made a buk up...
One more thing : The secondary ROM detects the SD card as corrupted and needs formatting if installed to external storage :/
Can anybody help my?
I want to install second ROM on sd card, it will be perfect on ext4 separete partition.
I'v tried it.
I install second ROM on sd card (now it have only one partition vfat), but it cycle rebooting. Helps only restore from TWRP recovery.
DualBootUtilities..zip dont work and have an ERROR 1 in TWRP both 3.2.1.0 and 3.1.1.0.
My primary ROM is last oficial Android 6.0.1. , second ROM is [ROM] Stockrom Lite SM-A520F
Primary ROM rooted SuperSu, CSC - BTU, bootloader - A520FXXU4BRC4, PDA - A520FXXS2AQH1, Radio - A520FXXU4BRC1, ROM - A520FXXS4CRE1/A520FOXA4CRD3/A520FXXU4CRD3, Kernel 3.18.14-10911830 [email protected] #1 32-bit
Here is recovery log file
---------- Post added at 12:02 PM ---------- Previous post was at 11:56 AM ----------
May be it is the reason?:
I:Legacy property environment initialized.
mount: mounting /dev/block/mmcblk0p20 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p25 on /data failed: Device or resource busy
Click to expand...
Click to collapse
I have this problem when I go to roms. Anybody know what's wrong?
iloveoreos said:
I have this problem when I go to roms. Anybody know what's wrong?
Click to expand...
Click to collapse
You need root for this to work. Do you have that?
sheepkill15 said:
You need root for this to work. Do you have that?
Click to expand...
Click to collapse
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
iloveoreos said:
Yes, I'm rooted with magisk. I wonder if it matters what version I am running. I am running stock 8.0 on an A520W.
Click to expand...
Click to collapse
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
sheepkill15 said:
Oh right. I don't know if op patched something about this, but originally touchwiz roms don't work with DualBoot, not even Hades.
Or, at least, I couldn't get it to work.
Click to expand...
Click to collapse
Ok, that makes sense, I tried a different version on my note5 and it didn't work either. The OP said to set Tw rom as primary though, is there a way to do that?
Edit: Would it work to flash lineage os, install dualboot, and then flash touchwiz as primary?
Do ROMs boot normally from an SD card? Or are they a bit slow?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Depends on the SD Card ;p
But, in my experience, SD is slower than internal memory
Where to get the DualBootUtilities? Cant find them in this thread. Can I use the official ones from the website? Or can I just install the App and im fine?
iloveoreos said:
Do ROMs boot normally from an SD card? Or are they a bit slow?
Click to expand...
Click to collapse
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
simon151102 said:
Did you fixed the error when going to ROMs? Im having the same error and I dont know what to do. Im rooted with magisk on Stock ROM 8.0
Click to expand...
Click to collapse
Try a custom ROM like lineage os and it should fix that error. However, when I updated ramdisk through dual boot on lineage os 16, my internal storage would quit showing up in stock file manager and downloads would fail. Haven't tried on any other ROM s though.
DualBootUtilities.zip?
lzzy12 said:
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
Click to expand...
Click to collapse
Great job ,thanks. I did'nt find the download link "DualBootUtilities.zip"
I am getting an error 1 while flashing a patched ROM. It looks like the ROMs aren't compatible by looking at the logs. Don't know if that is the correct verdict though.