Hello dear Friends,
I've got a problem and I don't know how to solve it. I want to install the latest CM12 on my S5 but TWRP always gives me this error
Code:
Symlinks: some symlinks failed
E: Error executing updater binary in zip (FILENAME)
I don't know how to solve this. Even Philz Recovery gives me
Code:
Some symlinks failed
Status 7
I checked the md5 sum, downloaded everything at least eight times. Flashed almost every recovery I found, including old TWRP and Philz versions. Unmounted cache as I read it helped some Note 3 users. I tried nearly everything. I hope you can help me.
Pozdrav
Croatia1
Anyone?
Same problem here...
---------- Post added at 01:28 PM ---------- Previous post was at 01:19 PM ----------
Update: If you do a wipe data/factory reset from twrp before flash the rom it will work to flash!
Related
I'm trying to flash BlissPop for A500F. But i keep getting an error in TWRP 3 after /system starts to get formatted. I have tried multiple times to reinstall twrp but no luck :crying:
I keep getting the message: Updater Process ended with signal:6
Plz help!
Post the recovery log on pastebin
Hey everyone.
I have an Asus Zenfone 2 Laser ZE551KL and I tried using this method to root it but my phone is now stuck on the boot screen. Not looping per se, but the little circle just keeps going around and around after I got to booting the boot_200007.img file and the phone restarted. I can still boot into TWRP and access the internal storage and SD from my PC so I tried loading the CM13 files onto the SD and flashing them using TWRP, but to no avail . Tried rebooting into fastboot mode but this doesn't work either. Does anyone have a stock boot img file for this model... or know what's going on and can help?
yo man! i can tell you if you can got into the twrp there is no need to do anything..but if you got stuck into start screen like rotating asus logo and can go further..it can happen if you have not unlocked your bootloader before rooting procedure, so you can not go with cm kernel, now you have yo do this procedure...
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
first you try another time with cyanigenmod. first boot into twrp and go to WIPE.
now go to advanced wipe
now tick on data, system, dalvik-cache, cache, internal storage.
only tick what above described.
now wipe...
after that go to mount and untick all except sdcard where your cyanogenmod zip is.
now go to install cyanogenmod...
now reboot and see, it takes some time about 15 minutes. if your cyanogenmod not going to boot then you have to unlock bootloader. then it will boot surely.
for unlocking procedure i will tell you more first you try this and reply me...
[email protected]
wait for the reply cuz i have exams right now..so....you can understand
---------- Post added at 05:36 AM ---------- Previous post was at 05:35 AM ----------
you can download the official firmwa
---------- Post added at 05:37 AM ---------- Previous post was at 05:36 AM ----------
you can download official formware from asus.com for your phone model which contains stock boot image.
crossmanx said:
yo man! i can tell you if you can got into the twrp there is no need to do anything..but if you got stuck into start screen like rotating asus logo and can go further..it can happen if you have not unlocked your bootloader before rooting procedure, so you can not go with cm kernel, now you have yo do this procedure...
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
first you try another time with cyanigenmod. first boot into twrp and go to WIPE.
now go to advanced wipe
now tick on data, system, dalvik-cache, cache, internal storage.
only tick what above described.
now wipe...
after that go to mount and untick all except sdcard where your cyanogenmod zip is.
now go to install cyanogenmod...
now reboot and see, it takes some time about 15 minutes. if your cyanogenmod not going to boot then you have to unlock bootloader. then it will boot surely.
for unlocking procedure i will tell you more first you try this and reply me...
[email protected]
wait for the reply cuz i have exams right now..so....you can understand
---------- Post added at 05:36 AM ---------- Previous post was at 05:35 AM ----------
you can download the official firmwa
---------- Post added at 05:37 AM ---------- Previous post was at 05:36 AM ----------
you can download official formware from asus.com for your phone model which contains stock boot image.
Click to expand...
Click to collapse
Unfortunately, no matter what I try to flash TWRP just gives me an error. I tried using back2stock and it says it couldn't find META-INF/com/google/android/update-binary in the folder, but when I look in the folder it's there and in the proper location.
unlock bootloaer and flash twrp using fastboot.
:/ I already have unlocked the boot loader and flashed TWRP. My issue comes with flashing the firmware.
Was using an CM13 unofficial build for months... then i decided i needed SPen and Heartbeat sensor
so i was hoping to try Erobots rom ( did full wipe ) , after successfull install... got boot loop... just keeps restarting on the Note 4 Logo
so i tried reflashstock rom(s) with both odin and kies 3 , after every flash , i always get the installing system update... erasing... and then boot loops
i though i got a perma soft brick.. till i tried using Cm13 again.... and it works ??
so what's causing this ? me not being able to use TouchWiz based roms ? both stock at custom
up
Try going to Recovery via the 3-button combo. Then wipe cache and data/factory reset.
If it didn't help, flash the official stock rom via odin. Then do the wipe cache/factory reset again in Recovery after flashing the stock rom.
yup tried those... i always ended up.. installing system update... then erasing... then boot loops
I have the exact same issue, I was stupid enough to not backup my system with TWRP when I had first rooted the device, so I cant just 'restore' my backup. I would like to use another rom but cannot due to this issue.
---------- Post added at 08:36 AM ---------- Previous post was at 08:24 AM ----------
try this: http://forum.xda-developers.com/note-4/help/n910c-stuck-frustrating-bootloop-t3301750
Slaid_ said:
I have the exact same issue, I was stupid enough to not backup my system with TWRP when I had first rooted the device, so I cant just 'restore' my backup. I would like to use another rom but cannot due to this issue.
---------- Post added at 08:36 AM ---------- Previous post was at 08:24 AM ----------
try this: http://forum.xda-developers.com/note-4/help/n910c-stuck-frustrating-bootloop-t3301750
Click to expand...
Click to collapse
have edited my original post ,
I've had something similar when I tried CM. It uses a not so generic recovery.
Try to flash a different recover with Odin - TWRP for example.
So things I have done:
Installed TWRP (fully)
Installed no varify
tried to get root, couldn't for some odd reason followed a guide that told me to wipe everything under advanced in twrp and did.
Now this is where my problem lies, I can't boot my phone up at all, got a black screen that says N/A. I can't find a flashable Perry for the Moto E4 that's unlocked, the links I get are here for the stock images, but I can't flash them on an SD card through TWRP.
As I am poking around I am seeing this when I do use "adb install OS.zip (a zip file I found that's not flashable) C:\Users\kevin>adb install OS.zip
7757 KB/s (1416168049 bytes in 178.276s)
/sbin/sh: pm: not found
You did it wrong, you're supposed to go to wipe in twrp and format data, then reboot back into recovery flash no verity and then your su and then the phone will boot. It will still show n/a after doing this but should boot back up.
---------- Post added at 06:05 AM ---------- Previous post was at 06:03 AM ----------
I don't think you wiped your system because it would tell you if you did. Go to twrp format data and then reboot back into recovery, once you've done that then flash no verity then your su of choice, reboot the device and it should work.
KyleBryant said:
You did it wrong, you're supposed to go to wipe in twrp and format data, then reboot back into recovery flash no verity and then your su and then the phone will boot. It will still show n/a after doing this but should boot back up.
---------- Post added at 06:05 AM ---------- Previous post was at 06:03 AM ----------
I don't think you wiped your system because it would tell you if you did. Go to twrp format data and then reboot back into recovery, once you've done that then flash no verity then your su of choice, reboot the device and it should work.
Click to expand...
Click to collapse
I actually just got done with that, but I can't root the phone it seems, have SU on my SD flashed it after doing the Verity, still no root access.
Also I have "retail services have stopped" error as well.
Hmm I'm not exactly sure then I haven't had that happen before.
KevinDel said:
So things I have done:
Installed TWRP (fully)
Installed no varify
tried to get root, couldn't for some odd reason followed a guide that told me to wipe everything under advanced in twrp and did.
Now this is where my problem lies, I can't boot my phone up at all, got a black screen that says N/A. I can't find a flashable Perry for the Moto E4 that's unlocked, the links I get are here for the stock images, but I can't flash them on an SD card through TWRP.
As I am poking around I am seeing this when I do use "adb install OS.zip (a zip file I found that's not flashable) C:\Users\kevin>adb install OS.zip
7757 KB/s (1416168049 bytes in 178.276s)
/sbin/sh: pm: not found
Click to expand...
Click to collapse
The files that you have linked to are firmware files, and are only flashed through fastboot or RSD Lite. See if you could find a guide here in this forum. If not, I created [THIS] guide a few years back that should help, follow #4 but don't use the posted links.
Thanks bud! I actually got it up and running. Had to reflash a few things, but she's up now haha! I am human bookmark that though! (I'll mess up again)
hi, i have two questions:
when i open recovery mode i have a message "installing system update" and after "no command"
is it normal?
in recovery mode (after an earlier "error") i have a message (at the bottom screen) "E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory"
it is something important? what does it mean?
my phone is j5(2016), sm-j510fn with official android 7.1.1 XEO (update installed via odin same as stock samsung rom 6.0.1)
the phone works fine, but i want to know what these "error" messages mean in the recovery mode
i have one more question:
after installing nougat update via odin (one file rom) my phone didn't back to factory settings, that's good?
I observed that too...
I observed that too, when i tryed to do a hard reset,but i got a different problem my phone officialy updated this night and since it updated it keeps giving me the error: "Unfortunetly com.android.phone has stopped" and it does not receve any service :crying:, i wiped the cache partiton, i did a factory reset, but it keeps giving me this error, did this happen to anyone else?
cichy. said:
hi, i have two questions:
when i open recovery mode i have a message "installing system update" and after "no command"
is it normal?
in recovery mode (after an earlier "error") i have a message (at the bottom screen) "E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory"
it is something important? what does it mean?
my phone is j5(2016), sm-j510fn with official android 7.1.1 XEO (update installed via odin same as stock samsung rom 6.0.1)
the phone works fine, but i want to know what these "error" messages mean in the recovery mode
i have one more question:
after installing nougat update via odin (one file rom) my phone didn't back to factory settings, that's good?
Click to expand...
Click to collapse
That is normal for the stock android recovery.
I would reccomend to clean flash the new nougat if you are comming from a custom ROM. But if you just installed it over stock 6.0.1 than it is ok if its not wiped. It would be the same that you installed nougat OTA.
---------- Post added at 02:57 PM ---------- Previous post was at 02:54 PM ----------
Ticsy said:
I observed that too, when i tryed to do a hard reset,but i got a different problem my phone officialy updated this night and since it updated it keeps giving me the error: "Unfortunetly com.android.phone has stopped" and it does not receve any service :crying:, i wiped the cache partiton, i did a factory reset, but it keeps giving me this error, did this happen to anyone else?
Click to expand...
Click to collapse
If you did a factory reset and the problem persists, you should install nougat manualy over odin.
Haxomen said:
That is normal for the stock android recovery.
I would reccomend to clean flash the new nougat if you are comming from a custom ROM. But if you just installed it over stock 6.0.1 than it is ok if its not wiped. It would be the same that you installed nougat OTA.
---------- Post added at 02:57 PM ---------- Previous post was at 02:54 PM ----------
If you did a factory reset and the problem persists, you should install nougat manualy over odin.
Click to expand...
Click to collapse
Thanks for the answer i went to a service and they fixed the problem for me as i am still afraid of bricking my phone but i will try to learn how to root and change roms on a phone i got at home that i do not need... btw they said it had a problem with the IMEI number and that it had 50/50 chance of bricking but they managed to repair it... anyway thanks for the answer ^_^
cichy. said:
hi, i have two questions:
when i open recovery mode i have a message "installing system update" and after "no command"
is it normal?
in recovery mode (after an earlier "error") i have a message (at the bottom screen) "E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory"
it is something important? what does it mean?
my phone is j5(2016), sm-j510fn with official android 7.1.1 XEO (update installed via odin same as stock samsung rom 6.0.1)
the phone works fine, but i want to know what these "error" messages mean in the recovery mode
i have one more question:
after installing nougat update via odin (one file rom) my phone didn't back to factory settings, that's good?
Click to expand...
Click to collapse
"E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory"
My phone also had this problem. after I download latest stock ROM "J510FNXXU2BRL1_J510FNODD2BRL2_SLK" (SLK is my region) from sammobile and flashed it using Odin.
But it was make new problem. now phone looping on Samsung logo. I looked at screen about 15min. not start android. I tried different different method to solve.
finally download TWRP from XDA ,after flash it and booted to twrp.
after did these steps.
1. Wipe > Advanced Wipe
2. select 'Data' (partition)
3. Now tap 'Repair or Change file system'
4. Now tap on 'Repair file system'. If it is done, it say done.
( In my case it not complete and say has some mounting errors. and I tap on 'Change file System' next select 'EXT4' and swiped to change.
now repeat step no 4. )
5. Now flash latest stock ROM using Odin and re boot.
done!
after about 5-8 min phone start correctly.
after I checked the error "E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory" in recovery mod. oh! it has gone. :laugh:
I'm sure it will work to you also.
Ranasinghe said:
"E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory"
My phone also had this problem. after I download latest stock ROM "J510FNXXU2BRL1_J510FNODD2BRL2_SLK" (SLK is my region) from sammobile and flashed it using Odin.
But it was make new problem. now phone looping on Samsung logo. I looked at screen about 15min. not start android. I tried different different method to solve.
finally download TWRP from XDA ,after flash it and booted to twrp.
after did these steps.
1. Wipe > Advanced Wipe
2. select 'Data' (partition)
3. Now tap 'Repair or Change file system'
4. Now tap on 'Repair file system'. If it is done, it say done.
( In my case it not complete and say has some mounting errors. and I tap on 'Change file System' next select 'EXT4' and swiped to change.
now repeat step no 4. )
5. Now flash latest stock ROM using Odin and re boot.
done!
after about 5-8 min phone start correctly.
after I checked the error "E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory" in recovery mod. oh! it has gone. :laugh:
I'm sure it will work to you also.
Click to expand...
Click to collapse
same error, trying to do but cant get twrp installed as I have frp lock on, any ideas how to get it off without being able to get into developer options?
Someone has resolved this problem?