Database Users

AOSP rom built - question on removing recovery

So I have the asop 4.2.1 built with make otapackage but every time I try to install it using TWRP I get an error 7
What I did:
- built the ota
- deleted recovery folder
- flashed rom - got an error 7
Any tips on this? Thanks.

up?

try not deleting anything and flash again, there might be something in the install script that relies on it. for anything it tries to do there and wont find it will throw an exception and break the install. after you have your cause you can still worry about the recovery.

vomer said:
So I have the asop 4.2.1 built with make otapackage but every time I try to install it using TWRP I get an error 7
What I did:
- built the ota
- deleted recovery folder
- flashed rom - got an error 7
Any tips on this? Thanks.
Click to expand...
Click to collapse
vomer,
You have to remove these lines from '/META-INF/com/google/android/updater-script' file (in your ota zip).
Code:
package_extract_dir("recovery", "/system");
set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");
i.e, search 'recovery' in 'updater-script' and remove that line.

[6045*] [TWRP] custom recovery 2.8.7.0

TWRP 2.8.7.0 custom recovery
thanx to user @Unjustified Dev we have TWRP custom recovery for our phone.
download HERE
So anyone who download the TWRP should send him a dollar for beer or at least thank him!
Of course you do everything on your own!
To test before installation (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img
To install (linux users need sudo before fastboot):
Code:
fastboot -i 0x1bbb flash recovery twrp-2.8.7.0-idol3.img
!BEFORE YOU START, PLEASE READ THIS!
And don´t forget to thank Famewolf for the tutorial, because this could save your phone when something go bad!​

Thanks, tried it. It worked.
I also just installed SU directly, bypassing the previous root thread.
1. Download the .zip package from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
2. Put it on the root of my SD card.
3. In TWRP click install and find the .zip.

Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?

Gynoid said:
Wonderful. Just a question: is this recovery for Idol 3 4.7 (6039) or 5.5 (6045) ?
Click to expand...
Click to collapse
It's for 6045. For 4.7 TWRP, see this post: http://forum.xda-developers.com/showpost.php?p=61976520&postcount=18

Thanks!

is it functional for backing up our system in TWRP?

@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk

gecko702 said:
is it functional for backing up our system in TWRP?
Click to expand...
Click to collapse
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.

famewolf said:
Yes although to my knowledge noone has actually done a restore yet. He's fixing some minor bugs and will be releasing a new version at some point.
Click to expand...
Click to collapse
i am in touch with the dev and allready downloading the new build..will be soon on my google drive

Unjustified Dev said:
@DallasCZ could you please provide the original link to TWRP. That was a bit unfair to upload it elsewhere as I tend to track the number of downloads.
Sent from my LGMS395 using Tapatalk
Click to expand...
Click to collapse
sorry, i corrected the link...

Convert TWRP Backup into flashable rom zip
I found these instructions that explain how to take a TWRP backup and turn it into a flashable zip file. This would allow someone to create a "factory" rom pre-rooted to be flashed.
For TWRP Backup
Transfer the TWRP backup from Phone to PC.
You’ll see a file named system.ext4.win which is the System partition backup of your device. Rename it to system.ext4.tar (Changing its extension from .win to .tar)
Extract the system.ext4.tar using an archive software like Winrar or 7zip.
If your TWRP backup is not in compression mode, you will directly get the system folder, else you will get a file named system.ext4, which should be renamed again to system.ext4.tar and extract it to get the system folder.
Take the boot.emmc.win file and rename it to boot.img.
Now collect a META-INF folder from any custom ROM which is made for your device. Make sure you get the correct Meta-Inf folder, else the Zip won’t work and might worsen the condition of your device.
Select the META-INF, System folders and the boot.img and right click your mouse and select add to Archive.
In the Archive settings, choose the extension of the compressed file as Zip (Make sure of this part)
Now you can use this Zip file to flash it on your Custom recovery.

we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).

DallasCZ said:
we dont have the meta-inf folder...there is one in the update i got, but i dont know if this id the right one.
and we dont have custom rom to get meta-inf from.
also the main thing is, that i cannot unpack the system win file when renamed to .tar i dunno why (i got latest 7-zip app).
Click to expand...
Click to collapse
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex

famewolf said:
What they primarily want is the "update-binary" which is device specific. I don't remember if the update had one....I did take apart an update-supersu.zip and it uses a script as it's update binary...thought about trying to convert that. Theoretically you could take a meta-inf for another device's rom...and use it's meta-inf making sure to replace the update-binary. It also has an installer script that tells it to mount system and data....extract files from the zip and where to put them. I learned a bit when I was trying to make an update.zip to fix my build.prop.
It untar'd fine for me on my linux pc:
[email protected]:/workarea/android/idol3/TWRP/BACKUPS/408adcbe/1970-01-01--22-28-53_LRX22G_release-keys/work > tar -xvf ../system.ext4.win000
tar: Removing leading `/' from member names
/system/app/
/system/app/AntHalService/
/system/app/AntHalService/AntHalService.apk
/system/app/AntHalService/arm64/
/system/app/AntHalService/arm64/AntHalService.odex
/system/app/BasicDreams/
/system/app/BasicDreams/BasicDreams.apk
/system/app/BasicDreams/arm64/
/system/app/BasicDreams/arm64/BasicDreams.odex
/system/app/Bluetooth/
/system/app/Bluetooth/Bluetooth.apk
/system/app/Bluetooth/arm/
/system/app/Bluetooth/arm/Bluetooth.odex
Click to expand...
Click to collapse
i allready build some roms for my older device, so i know what it is about.
For the proper rom zip you have to make the updater script with all the simlinks and metadata ...in the latest update there were no simlinks in the updater script...
without them you can brick your phone.
for example simlinks from 4.4.2 Os from zte V5
Code:
symlink("/data/misc/audio/mbhc.bin", "/system/etc/firmware/wcd9306/wcd9306_mbhc.bin");
symlink("/data/misc/audio/wcd9320_anc.bin", "/system/etc/firmware/wcd9306/wcd9306_anc.bin");
symlink("/persist/WCNSS_qcom_cfg.ini", "/system/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini");
symlink("/persist/WCNSS_qcom_wlan_nv.bin", "/system/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin");
symlink("/system/lib/modules/pronto/pronto_wlan.ko", "/system/lib/modules/wlan.ko");
symlink("Roboto-Bold.ttf", "/system/fonts/DroidSans-Bold.ttf");
symlink("Roboto-Regular.ttf", "/system/fonts/DroidSans.ttf");
symlink("libGLESv2.so", "/system/lib/libGLESv3.so");
symlink("mksh", "/system/bin/sh");
this you cannot copy from another device....

Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?

Acreo Aeneas said:
Never mind. I installed the second build.
How do I boot into the custom recovery? Is it power up + power button on the Idol 3?
Click to expand...
Click to collapse
Reboot or power on till you see the alcatel screen pop up....right away hold down up arrow and it should go into recovery.

Thank you so much...been waiting for this....
so now let ROM's start pouring in )))))))

Hmm odd. I had to reflash it. For some reason it didn't take the first time I flashed the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?

Acreo Aeneas said:
Hmm odd. I had to reflash it. For some reason it didn't take the first time I flash the second build TWRP to my Idol 3.
What partitions should I backup using TWRP? I'd assume: Boot, System, and Data? Should I include System Image too?
Click to expand...
Click to collapse
The default of boot, system and data should be fine for personal use however if you have not yet rooted please read here first! http://forum.xda-developers.com/idol-3/help/want-to-able-to-install-ota-updates-t3163745

So Awesome! best looking twrp Ive seen yet xD. Also, works well too. I havent tested backing up data, but I did a successful restore of the system and boot So far so good!

Huawei Y625-U43 "soft" bricked

Hi xda-developers before read my long story sorry for my bad english and I hope you can help me…
I bought this phone recently and because I don't feel comfortable with EMUI I decided to do some modding. I rooted the phone successfully, remove some apps, install a new launcher and at this point everything was fine then i decided to install XPOSED FRAMEWORK.
I didn´t know that Huawei phones has so many problems with Xposed but I took the risk to follow Xposed installation instructions of another Huawei model. I'll write the instructions that I followed.
I changed ro.config.hwtheme in build.prop to 0, reboot and everything was fine
Then I installed a console app to use this commands:
Code:
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
But when i used lsattr and chattr the console display COMMAND NOT FOUND then I read an alternative to that commands.
Code:
chmod –R –i *
I have a little experience with Linux but I had never seen the “-i” modificator on chmod and the console too xD it displays
Code:
“bad mode not valid –i command”
or something similar.
Finally in a moment of stupidity I executed this command
Code:
chmod –R 777 *
I Reboot, Huawei logo then black screen, I remove the baterry, reboot and the same…
Well I only have the default Android recovery on the phone…
I found a ROM but that ROM is for the Huawei Y625-U32 I tried to modify this ROM removing the getprop lines on update-script and resinging the rom with APK SIGN but always trying to flash the signature verification fails.
Finally i read apart of the 3 files that generates APK SIGN in the META-INF folder (cert.rsa, cert.sf and manifest.mf) inside com/android exists other certificates files (otacert and metadata) and this files are related with the file /security/etc/otacerts.zip inside the phone but with Android recovery everything is complicated.
Well after my long story anybody can help me? I thought of these possible solutions:
Anybody can share me a backup ROM (update.App file) of this model (I know is a bit heavy to upload 700MB aprox.)
Help me modifying the Y265-U32 ROM to pass the frustrating signature check of Android Recovery (of course if at the end would be safe to mod that ROM or not )
Or any other suggestion please XDA Friends and thanks in advance.
P.D. I want to try all possibilities before send to technical service besides that the model was released recently (April 2015) and I dont know if they can flash it and sorry for my bad english again.

I'm on Colombia and I have the same model, original firmware can be found here: http://consumer.huawei.com/co/support/downloads/detail/index.htm?id=66735&key4=Y625
This is stock ROM. I recommend you NOT modify your system if you don't know too much.
Hope this helps

Hello guys I have a Huawei Y625-U13 from Mexico. My device is Softbricked, it wont boot up, its stucked at HUAWEI's Logo. I found the firmware to make an update via SD card (dload file). But I can't install it on my device, somebody knows how to?

Pre Root

Hello, i wanted to know if anyone can help me. I am trying to include a pre rooted magisk but it gives me an error like this:
Failed to unmount /system: No such volume script aborted (no error message)
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Bootleggers Edited.zip'
my code (which i found online) to include magisk is this:
ui_print(" Installing Magisk Root...");
package_extract_dir("magisk", "/tmp/magisk");
run_program("/sbin/busybox", "unzip", "/tmp/magisk/Magisk-v18.1.zip", "META-INF/com/google/android/*", "-d", "/tmp/magisk");
run_program("sbin/busybox", "sh", "tmp/magisk/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/magisk/Magisk-v18.zip");
unmount("/system");
I personally think it's because of the busybox, i want to fix this. Just to confirm, I am editing the Bootlegger NOT to post online, it is just for me because i have to much spare time haha
Thanks in advance

RyzoModding said:
Hello, i wanted to know if anyone can help me. I am trying to include a pre rooted magisk but it gives me an error like this:
Failed to unmount /system: No such volume script aborted (no error message)
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/Bootleggers Edited.zip'
my code (which i found online) to include magisk is this:
ui_print(" Installing Magisk Root...");
package_extract_dir("magisk", "/tmp/magisk");
run_program("/sbin/busybox", "unzip", "/tmp/magisk/Magisk-v18.1.zip", "META-INF/com/google/android/*", "-d", "/tmp/magisk");
run_program("sbin/busybox", "sh", "tmp/magisk/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/magisk/Magisk-v18.zip");
unmount("/system");
I personally think it's because of the busybox, i want to fix this. Just to confirm, I am editing the Bootlegger NOT to post online, it is just for me because i have to much spare time haha
Thanks in advance
Click to expand...
Click to collapse
I fixed the error by now but it doesn't root. So it completed flashing and after launching and installing magisk manager, it said it isn't rooted

RyzoModding said:
I fixed the error by now but it doesn't root. So it completed flashing and after launching and installing magisk manager, it said it isn't rooted
Click to expand...
Click to collapse
Why are you doing this exactly?
Is it not just easier to flash a Magisk zip than going through all this trouble?
Or is this something you are merely interested in trying out because you are interested?

garylawwd said:
Why are you doing this exactly?
Is it not just easier to flash a Magisk zip than going through all this trouble?
Or is this something you are merely interested in trying out because you are interested?
Click to expand...
Click to collapse
Yeah it is indeed because i'm intrested haha i make apps die pc with c# and stuff and wanted tot try this as Well, i always rooted the wat you said forum 3 years, nut i just wanted tot start editing Roms with pre root and edited apps and stuff haha

No idea... Go ahead ?

I need bin/sh to flash it twrp bcz..

i Accidently deleted system/bin/sh/
What can i do please root not work now
My phone Huawei p9lite vnc-l31c185b360 emui 5
Android 7

nadjibbb said:
i Accidently deleted system/bin/sh/
What can i do please root not work now
My phone Huawei p9lite vnc-l31c185b360 emui 5
Android 7
Click to expand...
Click to collapse
Hey, it's all ok dude..
I bet you didn't make a nandroid backup, if yes just restore it !
Not made a backup and rooted with superSU ?
Here on XDA find and try to use 'unSU.zip' file or simply click here. Flash it in recovery,
then if will work re-root the device with your favorite superuser app.
Hope your device will be newly usable.
Let the community know if all gone well...
P.S.: PM are ok but a post can be read by everyone, well done !
P.S.2: THX to @osm0sis for unSU script.
Cheers

Not work :crying: i want the file sh in system/bin/sh i accidentally delated i dont know what i do now
Wifi not work Bluetooth too i need just the file named < sh >

nadjibbb said:
Not work :crying: i want the file sh in system/bin/sh i accidentally delated i dont know what i do now
Wifi not work Bluetooth too i need just the file named < sh >
Click to expand...
Click to collapse
I believe / sh is recoverable only with a backup made previously.
Now you probably need to re-install, even to prevent other possible problems, the entire system.
Save all your files you want to keep and
keep your bootloader unlock code handy (maybe you don't need it).
I can suggest which files to use...
You can still expect some tips from more experienced users ..
You decide.
Cheers