Related
AOSP 2.1 Bug List - by FreeX10 (jerpelea and zdzihu)
THE DEV THREAD IS NOT A DISCUSSION THREAD!!!
Because the main DEV thread has become so cluttered with useless posts, i will try to condense all the Bugs and Fixes into the one post here. The DEV thread is not a thread to discuss what you would like to see in the next version, or a thread to ask why something was not included in the ROM. I do not have anything to do with the development of these ROMS but am trying to make life easier for Jerpelea and Zdzihu. If you have questions, answers, bugs or fixes, this is the place to post them.
AOSP 2.1 Changelog (Features that are working, and when they were resolved)
Changelog is here - http://forum.xda-developers.com/attachment.php?attachmentid=464170&d=1292341044
Current Issues and the Corresponding ROM version
** 007a
- Rom is in final release and is quite stable. Few users reporting reboot issues but seem to be related to individual users settings.
- Left button unlocking screen when in lock mode - workaround is to enable pattern unlock feature
- unable to get straight back into xrecovery menu without reinstalling - some users reporting this (myself included) - Fix is to manually reinstall menu using zdzihu's instructions here => http://forum.xda-developers.com/showpost.php?p=9561575&postcount=1
-
** 007
- sorry, been a bit slack updating this list - PM me if you want anything listed.
** b006
- wifi not coming back after turning it off - http://forum.xda-developers.com/showpost.php?p=9707776&postcount=4291
- Launcher Pro Plus FC after removing ADW - http://forum.xda-developers.com/showpost.php?p=9708084&postcount=4296
- [FIX FOUND] Vignette image garbled - http://forum.xda-developers.com/showpost.php?p=9712316&postcount=4340
make sure you have latest version of Vignette installed - seems to work ok.
- 2G Connection is not constant - http://forum.xda-developers.com/showpost.php?p=9713159&postcount=4345
- [FIX FOUND]3G not connecting - no APN's - http://forum.xda-developers.com/showpost.php?p=9713110&postcount=4344 and http://forum.xda-developers.com/showpost.php?p=9782564&postcount=34
Some users are saying if you manually enter your APN details, it all works
This is a work in progress so please PM me with the problem or post the specific issue here. Over the next few days i will be attempting to compile a list of all the bugs for the various versions of 2.1 AOSP Roms.
Lets keep the dev thread for what it is supposed to be - where the Devs can bounce ideas and list fixes and version releases.
Tim.
Installation Guides
What do you need...
- X10
- Root access (can be obtained many ways - z4root is probably the easiest - download z4root from market)
- ROM file (see below)
- USB cable to connect phone to pc
- zdzihu's Recovery menu needs to be installed also, and for this you need to be on 2.1 - does not work with 1.6 - http://forum.xda-developers.com/showpost.php?p=9561575&postcount=1 or installation guide below.
- patience!
AOSP 2.1 - Black Freedom
- Download ROM file from here => http://hotfile.com/dl/89981020/d198ed1/BlackFreedom_signed_007a.rar.html
- connect phone to pc and mount the SD card.
- Within the .RAR file is a .ZIP file - extract this to your phones SD card and rename it to Update.zip
- reboot phone and enter recovery menu (repeatedly pressing BACK as soon as the Sony Ericsson logo appears)
- a good idea is to take a backup of your phone before going any further - Backup and Restore, and then choose Backup. This will create a folder on your SD Card called XRecovery/Backups and will create a sub-folder for each backup. I have tested renaming these sub-folders to something usefull with no issues!
- Once backup is complete, zdzihu recommends running a "full wipe" - make sure you choose the correct option here, it is on the main screen and says "Factory Reset (full wipe)" - THIS IS AN OPTIONAL STEP
- once wipe is complete, click "Install update.zip from SD Card" - this is why we renamed the .zip file earlier.
- phone will install rom and bring you back to menu when completed. simply reboot and it will launch the AOSP 2.1 ROM
Let me know if these steps are not clear and i will edit them. i did them in 5 minutes before leaving to go away for the weekend
Installation Guide for zdzihu's xrecovery menu
{
"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"
}
There are 3 main ways to install this menu. The main method is via the .APK file that zoz33 created.
Other methods are a manual file copy using root explorer or using the old gscript file (outdated method).
I guess you could also ADB but i wont go into that method.
What you need...
- 2.1 ROM on your phone, this will not work with 1.6 Android.
- The files for the install are here - xRecovery 0.2-release
- Phone must have ROOT access and have busybox installed from the market (this is crucial)
Method 1 - APK File
1. Download the APK file and copy it to your phone (attached to this post)
2. Install the APK file and run it.
3. Click on the "Install xRecovery" button. In most cases, this will simply install the menu and you are done!
If you get errors, you may need to try the manual method below.
Method 2 - Manual installation
1. Download the APK file again and rename it to a .zip file (replace .apk with .zip)
2. open the new .zip file and extract the /res/raw folder inside. It should contain 3 files (chargemon, busybox, xrecovery.tar)
3. Using root explorer (and make sure R/W mode is enabled) copy the 3 files listed about directly into /system/bin
4. reboot phone and tap back button until recovery menu appears.
As usual, PM me or post a reply if the instructions are not clear.
Cheers.
Cannot Enter Service Menu
Tried At the lock screen, press home, back, back, home, back, home, home, back (both Home and Menu)
Service Menu.apk does not work, error message flashes to quick to read
I cant install the ASOP using the recovery menu. When I select "Install update.zip from SD Card"
It say " E:Cant open /sdcard/update.zip (No such file or directory)."
Do i have to extract the ERD79_Update_signed_b006.rar? or edit the name? Help needed ASAP!
gohwh1 said:
I cant install the ASOP using the recovery menu. When I select "Install update.zip from SD Card"
It say " E:Cant open /sdcard/update.zip (No such file or directory)."
Do i have to extract the ERD79_Update_signed_b006.rar? or edit the name? Help needed ASAP!
Click to expand...
Click to collapse
1. extract ERD79_Update_signed_b006.rar
youcan see 2 folder(apps and HTC_IME) and ERD79_Update_signed_b006.zip
2. copy ERD79_Update_signed_b006.zip to sdcard
3. reboot to recovery mode
4. select Install custom zip
5. select Choose custom zip from sdcard
6. find ERD79_Update_signed_b006.zip in sdcard
7. select ERD79_Update_signed_b006.zip
8. select - yes - install ERD79_Update_signed_b006.zip
9. Wait a few minutes
10. if done. go back to main menu
11. reboot your phone
sory for my english, i want to help.
_______________________________________________
x10i ROOTED JIT002
Great now it working! Really thanks. If I decide to go back to Original Sony ROM, how do I go back?
Titanium backup is not picking up root tried z4root but still not working.
i used ConvertTool Decrypted branded ROM list (For unroot or rebrand purpose) (flashtools method) to extract my Original ROM from C:\Program Files (x86)\Sony Ericsson\Update Service\db\13740270 (My os is windows 7 64bit)
and i used X10Flash-2.1 X10 Flash Tool - Always newest Version (14.11.2010) for recovery my x10 to original rom
KamalKhattak said:
Titanium backup is not picking up root tried z4root but still not working.
Click to expand...
Click to collapse
tried install busybox from market and run Titanium backup again
standvision said:
tried install busybox from market and run Titanium backup again
Click to expand...
Click to collapse
Did but no luck it force closes. Tried to issue su command in terminal emulator it said no root
May be you root again by z4root
and install busybox
Now my rom is original ROOTED+JIT
i can't solve your Problem
the build 2.1 b006 is not rooted just the su installed without the binary files ,but reroot with z4 is working without any problem
Tony_C said:
Tried At the lock screen, press home, back, back, home, back, home, home, back (both Home and Menu)
Service Menu.apk does not work, error message flashes to quick to read
Click to expand...
Click to collapse
Tony, what ROM are you using? Is anyone else having this issue?
gohwh1 said:
I cant install the ASOP using the recovery menu. When I select "Install update.zip from SD Card"
It say " E:Cant open /sdcard/update.zip (No such file or directory)."
Do i have to extract the ERD79_Update_signed_b006.rar? or edit the name? Help needed ASAP!
Click to expand...
Click to collapse
to help with these posts, i have included an installation guide in the 2nd post now. looks like you have it sorted already but it will help someone else.
original SE camera app?
Hi! i´m really impressed so far, but i love my camera too much.. is there any way we could use the original camera app for 2.1? if there is, that might solve the errors + give us better settings...
thanks
mrtim123 said:
Tony, what ROM are you using? Is anyone else having this issue?
Click to expand...
Click to collapse
ASOP 2.1 b006
I'm glad after redoing everything my contact list shows up. Man was it a hassle without it..
last installation it wouldn't appear on my screen. blah lol. All good
mrtim123 said:
to help with these posts, i have included an installation guide in the 2nd post now. looks like you have it sorted already but it will help someone else.
Click to expand...
Click to collapse
Thanks but after I backup my stuff, I just install the ASOP ROM without doing a full wipe, will it affect anything? I thought by installing new ROM, all stuff will automatically being wiped?
Now i install AOSP 2.1 build b006 again
i can't access internet 2g from gsm
how to setup for internet acces
Hello,
i wish to create an update.zip to copy fonts from the zip into the system/fonts/ folder because i delete them and kept one font but it seems android doesn't boot with one font only need other fonts to be there (or atleast matching the names) to be able to boot.
adb push doesn't work giving me permission denied because /system is not mounted R/W (which i do using Super Manager for example)
i read other update.zip files and it seems i need to create CERT.SF and MANIFEST.MF files in META-INF , but it seems there are some SHA1-Digest: below each file (is this a md5checksum?) so i can't just replace file names and apply it
any ideas how can i do it without Wipe data/factory reset ? (and if factory reset is my last option would fonts be returned or factory reset doesn't get fonts back? i feel not)
Thanks
The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'
l0st.prophet said:
The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'
Click to expand...
Click to collapse
Thank you , any chance there i a Linux version out there? i'm using adb on ubuntu
and for CERT.SF and MANIFEST.MF i just create them manually based on any update.zip file i download earlier?
I'm on windows now and i've signed the file, when i try to apply it from recovery i get
E:signature verification filed
Installation aborted
what i'm missing?
attached my signed update.zip
it seems i had a folder update inside the zip
i have re-created one and signed it and still same error
attached the file
btw as i'm rooted and i used to su from adb shell and terminal emulator earier, any idea why su not working now?
$ su
[1] + Stopped (signal) su
$
[1] Segmentation fault su
$
is it because i'm on the HeRO logo boot screen ? it didnt get in yet?
btw for linux/ubuntu users who want to sign on linux you can use this:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 update.zip update_signed.zip
inside the Auto Sign folder
after signing on linux i get the following:
E: failed to read footer from / sdcard/update.zip (I/O error)
E:signature verification failed.
Installation aborted
First of all, please use the edit button, posting 6 times in a row is very hard to read, and is considered bumping your own thread which is a quick way to lose friends.
Secondly, the autoSign program creates a file called update_signed.zip which is the file you need to flash, the cert and manifest files are created by the process, you don't need to touch them. I have attached a signed version of your zip
I resigned it for you, see attachment. I use "androsign" I found here somewhere on XDA, maybe go look for it. It is a very easy tool edit: Too late
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.
First of all , sorry for the multiple posts
second i've tried both update-signed.zip and update_signed.zip and both of them gave me the same error
{
"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"
}
*P.S: sorry if i'm not allowed to put an image ill delete it
EDIT:
riemervdzee said:
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.
Click to expand...
Click to collapse
i tried to the help i didn't find how to set su in the right roots?
Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.
riemervdzee said:
Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.
Click to expand...
Click to collapse
yeah i tried the adb root already but getting "adbd cannot run as root in production builds"
yes i'm rooted and everything is fine
btw why deleting fonts prevents the phone from booting although there is one font there "not the default one"
what i want is to push the font files into the phone but getting the error i mentioned earlier that its not mounted as as R/W:
[email protected]:~/linux_adb_fastboot/hero_fonts$ for i in `cat list`; do adb push $i /system/fonts/$i ; done
failed to copy 'DroidSerif-Bold.ttf' to '/system/fonts/DroidSerif-Bold.ttf': Read-only file system
failed to copy 'DroidSerif-Regular.ttf' to '/system/fonts/DroidSerif-Regular.ttf': Read-only file system
failed to copy 'DroidSerif-Italic.ttf' to '/system/fonts/DroidSerif-Italic.ttf': Read-only file system
failed to copy 'DroidSansMono.ttf' to '/system/fonts/DroidSansMono.ttf': Read-only file system
failed to copy 'DroidSansFallback.ttf' to '/system/fonts/DroidSansFallback.ttf': Read-only file system
failed to copy 'DroidSerif-BoldItalic.ttf' to '/system/fonts/DroidSerif-BoldItalic.ttf': Read-only file system
failed to copy 'DroidSans-Bold.ttf' to '/system/fonts/DroidSans-Bold.ttf': Read-only file system
failed to copy 'Clockopia.ttf' to '/system/fonts/Clockopia.ttf': Read-only file system
failed to copy 'DroidSans.ttf' to '/system/fonts/DroidSans.ttf': Read-only file system
and yes adb remount doesn't work
[email protected]:~/linux_adb_fastboot/hero_fonts$ adb remount
remount failed: Operation not permitted
You have "rooted" your phone but you can't get adb root? That is contradictory
But since I'm in a good mood. Try to boot up the phone on your ROM, so not in recovery or bootloader. Then try to remount.
If remount is still failing, you don't have root.
Maybe you should also read your stuff a bit in before attempting anything. You are kinda screwing up your phone here.
Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?
Bashar . said:
Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?
Click to expand...
Click to collapse
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.
riemervdzee said:
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.
Click to expand...
Click to collapse
I did put one font there, but my mistake is not renaming it as the default font names that was there, i thought it would scan the fonts folder and use ANY font listed there
but seems not...
catlog shows im missing the fonts: http://dpaste.org/ADyJ/
dmesg output: http://dpaste.org/8IGw/
i never thought the recover it had won't let met flash the fonts
EDIT: i tried the mv command as linux user but my main problem is that its a read only system
[email protected]:~$ adb shell
$ cd system
$ cd fonts
$ ls
DroidSansArabic.ttf
$ mv
USAGE: mv <source...> <destination>
$ mv DroidSansArabic.ttf DroidSans.ttf
failed on 'DroidSansArabic.ttf' - Read-only file system
$
You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.
riemervdzee said:
You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.
Click to expand...
Click to collapse
yeah it seems thats my only option
I was hoping to learn by fixing, i'll flash it tomorrow then
now back to the question, why the update.zip that we were trying to sign is not flashable or signable ? what might be the reason? is it because i didn't root the recovery ?
i tried an stock Hero rom and still gives me invalid signature, i can't apply any rom at all now or what?
While flashing a rom, sometimes we get a "status 7 error". This Guide helps you to get out from it, and flash your favourite rom. Let's get started.
Move to META_INF > COM > GOOGLE > ANDROID by extracting the rom.
Here you will find a file "updater-script". Rename this file as updater-script.doc (microsoft word format) or use notepad++ (preferably)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.
Double click to open it( microsoft word preferred)
delete text, starting from "assert ....... till the semicolon ( of the last getprop command).
(See the image in the attached file for carefully deleting the lines. Click this link.)
Save the file now.
Again rename the file, and delete the .doc extention
Now go back and zip these files again. and you will get a zipped rom.
And the status 7 error has now been removed!
---
Siddharth121 said:
hey!
while flashing roms, many times we get a "status 7 error". while searching in many threads, we do not get how to resolve it. i will tell you each and every thing step by step
so i made a NOOB FRIENDLY WAY TO RESOLVE STATUS 7 ERROR
make sure that the rom you have downloaded matches your phone model, if you flashed some other rom, you may hard brick your device.
1. First extract your rom (for example using 7-zip)
2. Go to the folder META_INF > COM > GOOGLE > ANDROID
3. Here you will find a file "updater-script"
4. Rename this file as updater-script.doc (microsoft word format)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.
5. Double click to open it( microsoft word preferred)
6. delete text, starting from "assert ....... till the semicolon( of the last getprop command. (see image in attached file-lines to delete)
7. Now save the file
8. Again rename the file, and delete the .doc extention
9. now go back to the main rom folder where you extracted the 3 files. zip these files again. and you will get a zipped rom.
and the status 7 error has now been removed!:good:
happy flashing :victory::victory:
at last, as you read in every post, i am not responsible for any bricked device.
Click to expand...
Click to collapse
have you already try to cook rom using android kitchen?
I saw android kitchen. But it didn't supported my p3100. Ive rooted my htc day before yesterday. I'll try that surely :thumbup:
But why?..
Sent from my HTC One X+ using xda premium
Siddharth121 said:
I saw android kitchen. But it didn't supported my p3100. Ive rooted my htc day before yesterday. I'll try that surely :thumbup:
But why?..
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
because every time i use that to cook rom for my samsung galaxy gio the installation is aborted and error status 7 when i am flashing it
Do the above mentioned, actually the recovery checjs for the device version and all before flashing.
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Do the above mentioned, actually the recovery checjs for the device version and all before flashing.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
yeah maybe that is the main problem dude it is really hard to work with kitchen
Yepp. It is, but it reduces your harwork.
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Yepp. It is, but it reduces your harwork.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
maybe in deodexing a stock rom should the first one that really helps
flash the zip ,go to advanced option "show logs"
delete the lines which shows error like no file or directory in updater script
simple way
percy_g2 said:
flash the zip ,go to advanced option "show logs"
delete the lines which shows error like no file or directory in updater script
simple way
Click to expand...
Click to collapse
is that method is tested and proven?
badagila said:
is that method is tested and proven?
Click to expand...
Click to collapse
Yeah
Sent from my LT22i using Tapatalk 2
percy_g2 said:
Yeah
Sent from my LT22i using Tapatalk 2
Click to expand...
Click to collapse
have you try to cook rom using dsixda kitchen?
so the advice is to remove the device check?
How about a tip on how to use the proper device id or name?
So where do I look in the device to use the name that works?
That would be better imho.
I did try to use the values in the build.prop file from the running device, but that did not work eiter.
Now i'm getting status 4 error
i was getting status 7 error. Searched the forum and found this thread. I followed the directions to take off the lines from updated script files, but now i'm getting status 4 update. Can anyone recommend me how i can take care of status 4 error?
I can't flash any custom rom from recovery. Please help.
nulfinis said:
Hi,
I still get status 7 after using this guide.
any advice?
Click to expand...
Click to collapse
My Android Solutions
[27] Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong Radio etc
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"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"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Error 7
xsenman said:
My Android Solutions
[27] Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong Radio etc
I have had Error 7 due to delete many apps and unnecessary files in the rom. I resolved my problem flashing again the rom (previous rom) that I was removing apps and files. Then, I flash the new rom and problem resolved. Regards.
P.D. I have FXP238 CM10 installed and running ok.
Click to expand...
Click to collapse
Siddharth121 said:
1. First extract your rom (for example using 7-zip)
2. Go to the folder META_INF > COM > GOOGLE > ANDROID
3. Here you will find a file "updater-script"
4. Rename this file as updater-script.doc (microsoft word format)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.
5. Double click to open it( microsoft word preferred)
6. delete text, starting from "assert ....... till the semicolon( of the last getprop command. (see image in attached file-lines to delete)
7. Now save the file
8. Again rename the file, and delete the .doc extention
9. now go back to the main rom folder where you extracted the 3 files. zip these files again. and you will get a zipped rom.
Click to expand...
Click to collapse
hi, i follow all the instruction, but im still getting error, this time its "status 6"
wrong thread lol
thx for good work
Hi. Got my A40 rooted and wasen't happy about the look of the boot logo & warning text, so I did some changes to it.
WARNING:
THIS WILL TRIP KNOX SO DON'T FLASH UNLESS YOU KNOW WHAT YOU'RE DOING.
THIS IS MEANT FOR USERS THAT UNLOCKED BOOTLOADER AND GOT KNOX WARRANTY BIT BLOWN ALREADY
UPDATE, TWRP METHOD
----------------------------------------------------------------------------------------------------------------------------------------------
Now with warning (booting_warning.jpg) completly removed so that we can use full screen custom logos.
1/ Flash "View attachment A405-red_warn_remover.zip".
2/ Reboot to recovery.
3/ Flash "View attachment A405_logo_leafes.zip"
{
"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"
}
----------------------------------------------------------------------------------------------------------------------------------------------
Wanna make your own logo mod?
Make sure that the images you're doing has the same characteristics as the original files.
Raplace the images in "A405_logo_leafes.zip" and rename the zip to whatever fits.
Edit the "ui_print" in the update-binary if you wish, but please keep the credit to @moluntic for this awesome script.
(Original thread):[Tutorial][Boot Logo Changer]
read the info there as you can easily brick your phone if it's done wrong.
Remember that param partition acts as an image cache for bootloader and is indeed part of the bootloader partitions.
With that said, please don't share files unless you've tested it yourself first.
----------------------------------------------------------------------------------------------------------------------------------------------
OLDER METHOD:
Original ---> Changed to:
Original---> Changed to:
This blacked out so that it won't show on the black logo background.
Unzip View attachment SM-A405FN-param_mod.tar.zip and put the tar.md5 in AP slot in Odin. Connect phone in download mode and start flash.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Hi
To flash this do we need to reset/wipe after? I spent already too much time customizing this device, don't wanna do everything all over again
The warning that warns about booloader and asks to press power couldn't also be blackened or even replaced it with something nicer ((maybe text in black "Custom firmware initializing" ))? If I don't press power device continues boot anyway after a few seconds.
Can you give any tips, or any special care when creating/modified bootlogo? Or, if you have time to make more versions it will be appreciated
Many thanks.
Please do for TWRP
Got no feedback, so I decided to create my own bootlogo and sucessfully flashed it using Odin.
Even put the Magisk logo on it :laugh:
A quick how-to using Windows:
You know the drill, if you manage to damage your device when doing this, it's your own fault!
1. Download the firmware for your device from your preferred server (samfrew updato , select region, version), alternatively jump to the end for faster approach, but you may need knowledge described in next steps anyway
2. Have installed 7zs
3. Right-click the firmware file > 7Zip ZS > Open Archive > then double-click (dc) file that starts "BL.." > again dc param.bin.lz4 > again dc param.bin > extract all files
4. Files to customize are:
booting_warning.jpg
logo.jpg
svb_orange.jpg
Use favorite image editor (Paint works!)
Make sure you keep the default resolution and do not create much bigger files than the originals, a little bit smaller or bigger it's okay, but not too much.
5. Again using 7zs create a tar archive format with the files you edited and the rest you have extracted before, name the archive param.bin (literal, NOT param.bin.tar)
(7Zip ZS > Add to Archive > Archive Format: tar > Archive (name): param.bin)
6. And then again, create another tar file with the param.bin in it (archive name may be anything)
7. Using Odin, load the tar file you created on the previous step to the AP slot, connect the phone in download mode and flash
Alternatively, to save data and time download bootlogo mod from first post, just extract files, edit and repack again using similar manner as described above
(in the end you should have a file with tar extension instead of MD5 because archive does not have MD5 checksum attached, so Odin will not check data integrity)
I tried to load file but says error binary is invalid
Sparko612 said:
I tried to load file but says error binary is invalid
Click to expand...
Click to collapse
What are you trying to do? Flashing bootlogo mod from first post or creating your own?
pomaxa said:
Please do for TWRP
Click to expand...
Click to collapse
I've been working some more on this "project" and twrp flashable is working. I will upload tomorrow hopefully.
I managed to remove the black warning as well so that we can have full screen custom logos, like this:
There will be two zip's to flash the first time.
One with stock param, but witout the "red warning" and one zip to finally change the logo / svb_orange by unpacking param in device and replace the images inside.
This will be easier, as we from there on only have to replace two images in a zip to get new flashable logo.
Have already done
pomaxa said:
Have already done
Click to expand...
Click to collapse
Guess I was late then
Anyway, I've updated OP with new method, files and instructions.
tys0n said:
I managed to remove the black warning as well so that we can have full screen custom logos, like this:
View attachment 4846485 View attachment 4846487
Click to expand...
Click to collapse
Couldn't we had 'fullscreen custom logos' before?
Why did you choose to leave the message of the "svb_orange"? We all know bootloader is unlocked, message is useless and undesirable since boot continues anyway after a few secs (no need to press power).
Anyway, that's what I've done on mine, replaced it with a nice screen, acting as second (boot)logo.
Tony il Capo said:
Couldn't we had 'fullscreen custom logos' before?
Why did you choose to leave the message of the "svb_orange"? We all know bootloader is unlocked, message is useless and undesirable since boot continues anyway after a few secs (no need to press power).
Anyway, that's what I've done on mine, replaced it with a nice screen, acting as second (boot)logo.
Click to expand...
Click to collapse
That message doesn't really bother me so I just kept it.
We could have used full screen, but it would have looked like this cause the image is still there, just blacked out.
tys0n said:
We could have used full screen, but it would have looked like this cause the image is still there, just blacked out.
View attachment 4847521
Click to expand...
Click to collapse
Yes, of course, I forgot that it just gets overlayed on top of logo image, because my logo is mainly black and booting_warning is black too, it's there but invisible.
Tony il Capo said:
What are you trying to do? Flashing bootlogo mod from first post or creating your own?
Click to expand...
Click to collapse
Sorry I was trying to flash mod from first post
Thanks
Sent from my SM-A305GT using XDA Labs
Tony il Capo said:
Got no feedback, so I decided to create my own bootlogo and sucessfully flashed it using Odin.
Even put the Magisk logo on it :laugh:
A quick how-to using Windows:
You know the drill, if you manage to damage your device when doing this, it's your own fault!
1. Download the firmware for your device from your preferred server (samfrew updato , select region, version), alternatively jump to the end for faster approach, but you may need knowledge described in next steps anyway
2. Have installed 7zs
3. Right-click the firmware file > 7Zip ZS > Open Archive > then double-click (dc) file that starts "BL.." > again dc param.bin.lz4 > again dc param.bin > extract all files
4. Files to customize are:
booting_warning.jpg
logo.jpg
svb_orange.jpg
Use favorite image editor (Paint works!)
Make sure you keep the default resolution and do not create much bigger files than the originals, a little bit smaller or bigger it's okay, but not too much.
5. Again using 7zs create a tar archive format with the files you edited and the rest you have extracted before, name the archive param.bin (literal, NOT param.bin.tar)
(7Zip ZS > Add to Archive > Archive Format: tar > Archive (name): param.bin)
6. And then again, create another tar file with the param.bin in it (archive name may be anything)
7. Using Odin, load the tar file you created on the previous step to the AP slot, connect the phone in download mode and flash
Alternatively, to save data and time download bootlogo mod from first post, just extract files, edit and repack again using similar manner as described above
(in the end you should have a file with tar extension instead of MD5 because archive does not have MD5 checksum attached, so Odin will not check data integrity)
Click to expand...
Click to collapse
Thank you Bro !!
It works like a charm.
Very happy with this mod
Fred.
i know how to make it work with Odin but i was wondering if with the stock recovery it's possible to sign an update.zip containing this mod....
i tried an old zip signer with no luck ( probably it was with an old Android version).
tys0n said:
OLDER METHOD:
View attachment 4790669 Original ---> Changed to: View attachment 4790670
View attachment 4790672 Original---> Changed to: View attachment 4790673
View attachment 4790671
This blacked out so that it won't show on the black logo background.
Unzip View attachment 4790675 and put the tar.md5 in AP slot in Odin. Connect phone in download mode and start flash.
Click to expand...
Click to collapse
Hello. I installed this patch last july (release without leaves):
- is that version (no-leaves) still available / usable with ASJ firmware ?
- in general, how could I revert mod to the original ? Flashing full stock firmware doesn't affect bootloader area, it seems
I don't have TWRP so I'm talking about Odin releases
Thanks a lot for your work
tys0n said:
[...]
Click to expand...
Click to collapse
Hi tys0n, nice work!! Could that procedure (or something similar) also work for a A70 (SM-705FN/DS) with TWRP?
Swordfishx86 said:
Hi tys0n, nice work!! Could that procedure (or something similar) also work for a A70 (SM-705FN/DS) with TWRP?
Click to expand...
Click to collapse
Twrp with an update.zip style
Or flash with Odin
Perhaps files and directories are différents...
Envoyé de mon SM-A405FN en utilisant Tapatalk
fredapied said:
Perhaps files and directories are différents...
Click to expand...
Click to collapse
There is no param.bin in the BL-file of A70s firmware ...
Hi all,
At my work we are using an android tablet and I need to install root on it. The tablet is a SkyDroid H16. The weird thing is that "adb root" works fine and I can remount /system and add files, but apps cannot see that there is root.
How can I install su and use it.
There is no TWRP for it and the stock image is also not public.
Senna-chan said:
Hi all,
At my work we are using an android tablet and I need to install root on it. The tablet is a SkyDroid H16. The weird thing is that "adb root" works fine and I can remount /system and add files, but apps cannot see that there is root.
How can I install su and use it.
There is no TWRP for it and the stock image is also not public.
Click to expand...
Click to collapse
Root Android Devices without TWRP RecoveryTo root your device without TWRP Recovery, you need to perform two steps. Firstly, the device needs to be booted using the patched boot image file. In the next step, this boot image file will be permanently flashed using the Magisk Manager app. Don’t forget to have a look at the ‘Prerequisites’ section below, before beginning with the process. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.
Prerequisites
Download and install the Magisk Manager APK file on your device: Magisk App [from version 22 onwards, it is known as Magisk App and has both the Magisk ZIP and Manager APK file bundled together].
Next up, check if your device has ramdisk or not. For that, launch the Magisk app and refer to the section under Magisk, if it says YES, then you are good to proceed ahead (see below image). On the other hand, if it says NO, then you will have to head over to our alternative guide: Install Magisk in Recovery and Root Android [No Ramdisk].
{
"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"
}
The bootloader of your device should be unlocked. Have a look at our guide on how to do so.
Enable the ‘USB Debugging’ option. Go to ‘Settings’ -> ‘About Phone -> Tap on Build Number 7 times -> Go back to Settings -> Developer Options -> Toggle on the USB Debugging’ switch.
Although rooting is going to wipe your data, still, it is recommended to make a complete backup of all your data.
Keep your device appropriately charged, at least to a minimum recommended level of 50%
Install ADB and Fastboot Tool for entering Fastboot commands.
Also, download and install the USB Drivers for your device. This helps in successfully connecting your device to the PC.
STEP 1: Get Stock Boot.img File from Stock ROM
To begin with, you will have to extract the stock boot.img file. And as opposed to earlier times, the process is a little bit more complicated nowadays. You cannot simply extract the firmware and get the required partition files (such as vbmeta.img, system.img, boot.img, etc). The reason is that many OEMs packs the ROM’s IMG files inside an encrypted package. For example, OnePlus has these files inside payload.bin, Realme, and Oppo have their files inside the OZIP format, and so on. In that case, you may refer to our below guides to get the stock boot.img file:
Now that you have got hold of the stock boot image file, it’s time to patch it via Magisk and flash it via Fastboot Commands. We have listed the steps for both the older as well as the newer build of Magisk Manager. As far as the difference between them goes, it’s just some UI tweaks here and there, the underlying functionality remains the same. The below update is only for devices running Android 11. If your device isn’t running that version, then you may directly head on to STEP 2A/2B.
UPDATE 1 [FOR ANDROID 11 USERS ONLY]: Quite a few Android 11 users are facing issues while patching the stock boot.img file via Magisk manager. Well, I have found the fix to this issue, please refer to our detailed guide on the same: Fix Magisk patched boot.img issue while Rooting Android 11. If you wish to save a click, then here’s the explanation in short:
You have to install the Magisk Canary build instead of the stable and then change the update channel to Canary from within the app itself. Once you have done the said change, you may then proceed with the below steps to patch the stock boot image file using Magisk and flash it via Fastboot commands. [END OF UPDATE 1]
STEP 2A- Patch the Stock Boot Image File using Older Magisk
Download the stock firmware for your device.
Extract the boot.img file from it.
Transfer it to the device’s internal storage.
Install the Magisk Manager App on your device.
Open it. Tap on the first ‘Install‘ button, next to Magisk status.
In the next menu, again chose ‘Install‘.
Now select ‘Select and Patch a File‘.
Navigate to internal storage and select the stock boot.img file that you extracted earlier.
Let Magisk do the patching process. When it’s done, copy this patched boot.img file, named as magisk_patched.img, from your device (will be present under Internal Storage > Downloads) to PC where you have installed the ADB and Fastboot Tools (inside the platform-tools folder).
How to Update Magisk ZIP and Magisk Manager (without TWRP)
Disable DM-Verity or Android Verified Boot without TWRP
Fix Magisk Module Bootloop without TWRP Recovery
How to Root Android Devices Without TWRP Recovery
STEP 2B: Patch Stock Boot Image File using Newer Magisk
Launch the Magisk Manager app on your Pixel device.
Then tap on the Install button situated next to Magisk.
From the Method section, choose Select and Patch a file.
Browse to the extracted boot.img file and select it.
Then tap on the Let’s Go option situated at the top right.
Magisk will now load the boot.img file and will patch it accordingly. Once that is done, you would get the Download Complete message.
The patched boot image file will be saved in Internal Storage > Downloads. The name of the file will be magisk_patched.img.
Now that you have patched the stock boot.img file, it’s time to flash it onto your device and hence obtain root without TWRP. There are two different methods through which you could do this. This patched boot.img file could either be flashed via Fastboot or through Magisk. It is highly recommended that you proceed with the Fastboot Method. Only in case, if you face any issues, then you should proceed with the Magisk Method. The reason being the fact via the Magisk method, we will be using the DIrect Install feature, which seems to be absent in most devices. Hence to avoid any confusion, you should try the Fastboot Method. If you face any error, then only proceed with the Magisk method to root your Android device without TWRP.
STEP 3A- Install the Patched Boot Image using Fastboot
Connect the device to the PC via USB Cable.
Now transfer the patched boot file from your device to the platform-tools folder on your PC.
Inside the same folder, right-click on an empty area while pressing the ‘Shift’ key.
Select the option ‘Open PowerShell window here’.
Or you could also head over to the platform-tools folder on your PC, type in CMD in the address bar, and hit Enter. This will launch the Command Prompt.
Type in the below code to make sure the device is successfully connected (an alpha-numeric code suggests successful connection):adb devices
Now type in the below code to boot your device to fastboot/bootloader mode:adb reboot bootloader
Next, type the below code to flash the patched boot image file:fastboot flash boot magisk_patched.img
If you get the fastboot: error: Couldn’t parse partition size ‘0x’ issue, as some users have mentioned in the comments, then please refer to our detailed guide: How to Fix fastboot: error: Couldn’t parse partition size ‘0x’.
For devices with an A/B partition, you need to flash the patched boot file to both partitions. Type the below code for the same:fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Now you may Reboot the device by typing the below code:fastboot reboot
If your device is rooted, then you should stop here only. However, if the Fastboot Command method didn’t work out in your case, then only proceed with the next method to install patched boot.img.
If this post is good please thumbs up.
@Senna-chan
Because adb root & adb remount works here is a code example that adds su
Code:
adb root & adb remount & adb disable-verify & adb shell "setenforce 0"
adb push su /system/bin/
adb push superuser.apk /system/app/
adb reboot
jwoegerbauer said:
@Senna-chan
Because adb root & adb remount works here is a code example that adds su
Code:
adb root & adb remount & adb disable-verify & adb shell "setenforce 0"
adb push su /system/bin/
adb push superuser.apk /system/app/
adb reboot
Click to expand...
Click to collapse
So I tried this with a few version of supersu but it didn't work. I tried version 2.76 2.82 and 2.79 and it didn't work. Everytime I get the error no su binary found. The version I uploaded was the arm64 version since I have a ARMv8.
What could be wrong?
Thats great in all but after I flash the boot.img from any version of magisk from v22 onward and the latest canary, it doesn't give me magisk app when i boot back into the os.