Database Users

Rom Install Error...

I keep getting this error:
opening update package...
verifying update package...
installing update...
formatting BOOT...
formatting SYSTEM...
copying files...
E:can't chown/mod /system/xbin
(no such file or directory)
E:failure at line 19: set_perm_recursive 0 22000 0755 0 6755 SYSTEM:xbin
installation aborted
I have tried almost every ROM in this forum, but i get this error, except when i use CyanogenMod.
I have updated the latest spl and radio.
Any help?

is your phone rooted?

help!
I am getting the same error when attempting to update to the SuperHero V2 Rom.

Of course it is

maybe it's a sign

cyanogen said:
maybe it's a sign
Click to expand...
Click to collapse
Cue Ace of Base song...

LOL, i was thinking the same thing to, Cyanogen

but seriously, can anyone help?

temporizer said:
but seriously, can anyone help?
Click to expand...
Click to collapse
Did you wipe and reformat your SD card first?

temporizer said:
but seriously, can anyone help?
Click to expand...
Click to collapse
Try installing a different recovery.

Breakthecycle2 said:
Did you wipe and reformat your SD card first?
Click to expand...
Click to collapse
yes, I did

jashsu said:
Try installing a different recovery.
Click to expand...
Click to collapse
Thanks, i'll try that. i'll repost when i'm done.

temporizer said:
yes, I did
Click to expand...
Click to collapse
My suggestion would be to download the ROM again and reflash it.

Most likely you are trying to flash a ROM that requires Haykuro's SPL (which changes the MTD partition sizes), and it's running out of space during the installation.

cyanogen said:
Most likely you are trying to flash a ROM that requires Haykuro's SPL (which changes the MTD partition sizes), and it's running out of space during the installation.
Click to expand...
Click to collapse
Thanks. I'll try his then.

I tried to install JACHero's rom, and it says here http://forum.xda-developers.com/showthread.php?t=522076 that he recommends Cyanogen's 1.2 recovery, which i have currently, and it still didn't work, same error, except instead of line 19, it was line 12.
What am i doing wrong if i used the correct SPL from the post and the recovery...?

Give this a shot, we'll just double check everything, and try again, so as to rule out these possibilities. Don't skip any of these steps!
1st - Shut off your phone. Boot it back on, but into the SPL (camera+power buttons). Read the second line from the top, and the fourth line from the top. They will be your SPL and radio image, respectively. The second line should read "HBOOT-1.33.2005 (DREA10000)" and the fourth "RADIO-2.22.19.26I". Just to double check you have the ones needed if you are trying to install any hero rom and a few others too.
2nd - Delete the update.zip off of your sdcard (and computer, if it's there too) and re-download it. Put it back on your sdcard and rename to "update.zip". Make sure you have your file extensions un-hidden, so that its not actually "update.zip.zip".
3rd - Make sure you are wiping (alt+w) from inside your recovery loader, before you are applying the new update.zip (alt+s).

Unsolved Mystery, Case Closed.
Thanks for the help everyone. I have all the updated stuff, i guess my G1 just doesn't like the other roms.
I have no complaints with Cyanogens Rom, in fact, i like it very much. I think i will just keep it how it is.
Again, thanks everyone for your help.

Mods, Please close this thread

[ROOT] Root JB

This is a much simpler and hasslefree process.
Download the root file from : here.
Instructions :
Put the downloaded root.zip in external sdcard.
Go to the stock recovery.
Select apply update from sdcard.
Select root.zip
Flash
Reboot
Please let me know if there are any problems!
Proof : forum.xda-developers.com/showpost.php?p=37976783&postcount=9
Credits :
Phil for finding the method..
I do not respond to tech support via PM

Stock recovery? How does it pass if not signed by samsung?

tys0n said:
Stock recovery? How does it pass if not signed by samsung?
Click to expand...
Click to collapse
This zip is made for stock.
Its been signed..
I do not respond to tech support via PM

Shaaan said:
This zip is made for stock.
Its been signed..
I do not respond to tech support via PM
Click to expand...
Click to collapse
A question i was about to ask...
But the answer and the /wink really rocks!
Thanks!

Root failed
Rebooted to recovery via ADB.
Started root.zip, result is following:
E:failed to verify whole-file signature
E:signature verification failed

I wonder what is wrong with this device! Nothing normal works on this.!
I do not respond to tech support via PM

Sv: [ROOT] Root JB
ladislav.heller said:
Rebooted to recovery via ADB.
Started root.zip, result is following:
E:failed to verify whole-file signature
E:signature verification failed
Click to expand...
Click to collapse
Ok, just as every other "signed". Zip's made for this model :-\
Sent thru time and space from my s3mini.

It doesnt work for me.
E:failed to verify whole-file signature
E: signature verification failed
I have stock Official 4.1.1 android version si stock recovery
XXALJL build.

tys0n said:
Ok, just as every other "signed". Zip's made for this model :-\
Sent thru time and space from my s3mini.
Click to expand...
Click to collapse
This zip is signed using Google developer keys. These keys get past Samsungs signature verification!
We have been using this zip on various 4.0+ devices..
I do not respond to tech support via PM

Shaaan said:
This zip is signed using Google developer keys. These keys get past Samsungs signature verification!
We have been using this zip on various 4.0+ devices..
I do not respond to tech support via PM
Click to expand...
Click to collapse
Maybe Samsung has its own signing key? Or the verification method was modified...

Our device has some kind of next generation security. So I've read somewhere on this forum, and all of bypass security mods and hacks that worked on other devices don't work on this device. Like triangle away and other stuff..
Sent from my GT-I8190 using Tapatalk 2

ladislav.heller said:
Maybe Samsung has its own signing key? Or the verification method was modified...
Click to expand...
Click to collapse
Yep, although it was worth trying. Older Samsung devices could be rooted this way (the Galaxy Y for example).

tested and not work faile signature verification and after tested with signing your zip with md5sum only signe and not work some message faile signature verification

spawk said:
tested and not work faile signature verification and after tested with signing your zip with md5sum only signe and not work some message faile signature verification
Click to expand...
Click to collapse
same for me! its not working... :crying:

Samsung digital certificate
Attached is the original Samsung digital certificate extracted from sec_csc.zip. You can open it in Windows and import if you want (just remove the .txt extension). But unfortunately it has no private key so we can't create signing hash for script files, etc.

ladislav.heller said:
Attached is the original Samsung digital certificate extracted from sec_csc.zip. You can open it in Windows and import if you want (just remove the .txt extension). But unfortunately it has no private key so we can't create signing hash for script files, etc.
Click to expand...
Click to collapse
Have you considered contacted Samsung to obtain their private key? I see no reason why they wouldn't give it to an unknown third party.

xd.bx said:
Have you considered contacted Samsung to obtain their private key? I see no reason why they wouldn't give it to an unknown third party.
Click to expand...
Click to collapse
Not yet
Actually I don't know their contact address.
Maybe I should write to [email protected] which is in the certificate?

ladislav.heller said:
Not yet
Actually I don't know their contact address.
Maybe I should write to [email protected] which is in the certificate?
Click to expand...
Click to collapse
I think that xd.bx has been 100% ironic in his post.

Would anyone with official 4.1.2 has been successful with this method make a confirmation here please? Thx!
Shaaan said:
This is a much simpler and hasslefree process.
Download the root file from : here.
Instructions :
Put the downloaded root.zip in external sdcard.
Go to the stock recovery.
Select apply update from sdcard.
Select root.zip
Flash
Reboot
Please let me know if there are any problems!
Proof : forum.xda-developers.com/showpost.php?p=37976783&postcount=9
Credits :
Phil for finding the method..
I do not respond to tech support via PM
Click to expand...
Click to collapse

benjaminv said:
Would anyone with official 4.1.2 has been successful with this method make a confirmation here please? Thx!
Click to expand...
Click to collapse
No it's not working with stock recovery.

[fix] easy fix for balong issue

Hi!
i create a software to fix Balong issue after flashing a ROM.
Download the zip, extract the folder then only need to follow the steps in software!
Check the pictures bellow!
If fails check if cust image is properly installed before execute the software again.
Tell me if worked for you!
.

Thanks.

I've installed TWRP 3.1.1-0, but when I use your software it says "error: no devices/emulators found", even if I put the correct cust path

persona78 said:
Hi!
i create a software to fix Balong issue after flashing a ROM.
Download the zip, extract the folder then only need to follow the steps in software!
Check the pictures bellow!
If fails check if cust image is properly installed before execute the software again.
Tell me if worked for you!
.
Click to expand...
Click to collapse
Hi
After an update (official!) I re-encountered BALONG. After using your marvelous tool, it worked again, but there's no need to reset device (as written on CMD).
In addition, for the ones that get the error "no device attached" or something similar, you've only to reboot to TWRP, connect the phone to Windows and press Win+X, click on "device manager", look for "android device" or something similar. Right click on it and select "update driver", click the second option and than select that you already have the CD driver. You'll see a list: select "ADB composite device" and than finish: you've done!
Ah, I was about to forget: thank you!
Regards,
F

fixed
Hi.
Thanks for fast answer. I could fix the problem.
I downloaded the EMUI 3.1 as Magyar Telekom firmware from an arabic server cause ru huawei servers doesnt work lol. So I downloaded it I extracted boot, recovery, system, cust img files from UPDATE.APP with Huawei AppImage Extractor application. I flashed these with fastboot (Not TWRP, not huawei recovery). Fastboot from computer. Ok. But at the moment SIM does not work. I upgraded the system from Huawei update from settings (not recovery, system settings). After update the ROM and SIM is work perfectly.
Btw thanks your answer, topices too. This is a big help from you.
Have a nice day, Balázs.

How Can i use it for Meanaf Localization ????
How Can i use it for Meanaf Localization ????
@persona78
can you provide me Tool To fix Balong
Countryakistan
Mobile:ALE-L21
ROM:C185

Hello thanks for creating such tool
I've tried to use it but i get this error after TWRP boot :
mount: No such file or directory
mkdir: '/cust/hw': No such file or directory
ln: cannot create symbolic link from '/cust/hw/eu' to '/cust/hw/meafnaf': No such file or directory
Is there any solution for this?

-Mouhammad said:
Hello thanks for creating such tool
I've tried to use it but i get this error after TWRP boot :
mount: No such file or directory
mkdir: '/cust/hw': No such file or directory
ln: cannot create symbolic link from '/cust/hw/eu' to '/cust/hw/meafnaf': No such file or directory
Is there any solution for this?
Click to expand...
Click to collapse
Which Cust Path Do you Want?
hw/meafnaf?

MohmmadUzairKhan said:
Which Cust Path Do you Want?
hw/meafnaf?
Click to expand...
Click to collapse
The program detected this path : cust/hw/meanfaf
Is this what you mean?

-Mouhammad said:
The program detected this path : cust/hw/meanfaf
Is this what you mean?
Click to expand...
Click to collapse
What Do You Want?
hw/eu?

MohmmadUzairKhan said:
What Do You Want?
hw/eu?
Click to expand...
Click to collapse
Do you know what cuases this error?

Thank you its working excellent . And wipe is not needed. Tnx again ?

pls say me
how can i fix it with opened bootloader? must i flash cast?

Doesn't work. Did everything by the instructions. Twice.

Thread Closed

Thread Closed

Thread Closed

What is the difference between the version treble and the treble cust ?
Good work sir

Junier120 said:
What is the difference between the version treble and the treble cust ?
Good work sir
Click to expand...
Click to collapse
First of all Do Not Quote Whole -OP- and few users uses Redwolf recovery and few uses standard TWRP Recovery. sometimes you can't mount /vendor or /cust partition in recovery. You were ended up with "unable to mount vendor partition and so on". So i made two zips for same partition comes with two names in your twrp recovery shows "Vendor" or "Cust" when mounting.
In reality the folder name is vendor and the block device name is cust. You can fix this by editing the recovery.fstab file.

Can i skip the google account when i first boot?

SFSoFar said:
Can i skip the google account when i first boot?
Click to expand...
Click to collapse
Yes. You can.
It doesn't have Google Launcher app. So you won't get it on the first boot.

TheHitMan said:
Yes. You can.
It doesn't have Google Launcher app. So you won't get it on the first boot.
Click to expand...
Click to collapse
Emmmm,I mean the setupwizard.
Just forget its name.

SFSoFar said:
Emmmm,I mean the setupwizard.
Just forget its name.
Click to expand...
Click to collapse
It does not contain any setupwizard app.

TheHitMan said:
It does not contain any setupwizard app.
Click to expand...
Click to collapse
Thanks for the great work!
Next time I will try this gapp pack.

Good one. I used open gapps pico. This is even smaller than pico. Very minimal install. no setup wizard, also can enable battery optimization on play services.

When i trying to flashthis for treble rom. I got this message i can't flash the gapps? Both i already tried treble vendor and treble cust gapps...?

Wishh09 said:
When i trying to flashthis for treble rom. I got this message i can't flash the gapps? Both i already tried treble vendor and treble cust gapps...?
Click to expand...
Click to collapse
Me too

Wishh09 said:
When i trying to flashthis for treble rom. I got this message i can't flash the gapps? Both i already tried treble vendor and treble cust gapps...?
Click to expand...
Click to collapse
A log file would be a better option.
Get it from here "/cache/recovery/log or last_log" whatever the name is. Some permissions are failed to set. Vendor or cust partition error.

sokolataki said:
Me too
Click to expand...
Click to collapse
Get log file from here /cache/recovery/log or last_log.

TheHitMan said:
Get log file from here /cache/recovery/log or last_log.
Click to expand...
Click to collapse
After that I install opengapps but check it

Wishh09 said:
When i trying to flashthis for treble rom. I got this message i can't flash the gapps? Both i already tried treble vendor and treble cust gapps...?
Click to expand...
Click to collapse
me too..but is working dude..

sokolataki said:
After that I install opengapps but check it
Click to expand...
Click to collapse
Cust Partition Error. I am fixing this problem right now.
package_extract_file: can't open /cust/lib/libfrsdk.so for write: No such file or directory
package_extract_file: can't open /cust/lib64/libfrsdk.so for write: No such file or directory
- Set Permission
set_perm: chown of /cust/lib/libfrsdk.so to 0 0 failed: No such file or directory
set_perm: chmod of /cust/lib/libfrsdk.so to 644 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed

Wishh09 said:
When i trying to flashthis for treble rom. I got this message i can't flash the gapps? Both i already tried treble vendor and treble cust gapps...?
Click to expand...
Click to collapse
Thread Updated.

BiTGApps Update :
- Fix Failed to install Vendor or Cust files.
- Check OP

TheHitMan said:
Thread Updated.
Click to expand...
Click to collapse
Okay thanks, i check it again. Btw, the none treble gapps is working fine on non treble rom. Working perfectly no more google setup wizard automatic homescreen show up after first boot.

Magisk won't work on treble

Hey!
Whenever I install any Treble ROM on my Axon 7 Magisk won't be able to mount the system mirror. I already followed many instructions and ideas, none worked.
Model: A2017G
Treble: speedy
Kernel: baddar
Magiksk log says:
Code:
mount /sbin/.magisk/block/system->/sbin/.magisk/mirror/system failed with 16: Device or resource busy
Thx for any help!
Edit: Every file operation inside /system results in I/O error

tuxifan said:
Hey!
Whenever I install any Treble ROM on my Axon 7 Magisk won't be able to mount the system mirror. I already followed many instructions and ideas, none worked.
Model: A2017G
Treble: speedy
Kernel: baddar
Magiksk log says:
Thx for any help!
Edit: Every file operation inside /system results in I/O error
Click to expand...
Click to collapse
to conclude this it was a simple bootstack problem

Choose an username... said:
to conclude this it was a simple bootstack problem
Click to expand...
Click to collapse
exactly