Develop Bugs

Sorry, just a mess

But thank all you guys to point it out

Very kind, hope it helps many.

Should we format /system qheb installing rom? When is the best time to wipe battery stat?
Sent from my GT-I8150 using Tapatalk

FelixAusChina said:
[HOW TO]root, flash custom recovery ClockworkMod v5.5.0.4 and ROM Customized 1.8Ghz ROM (now with experiment EUR OC ROM) without odin step by step from offical ROM 2.3.6
1. Root your phone
Rooting via Recovery mode(SD card)
a. Download this Zip-file http://dl.dropbox.com/u/47601401/update.zip copy this into the internal SD card.
b. While switched off, keep the following buttons pressed. Release the power-button once the Samsung Galaxy W(I8150) is switched on. At last press the menu button quickly while pressing the other two buttons.
Note: This instructions is written for the stock recovery. Custom recoverys should work very similiar.
{
"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"
}
c. Navigate with the volume up and down to apply sdcard:update.zip in Recovery Menu. Use the home-button to confirm your selection.
d. Choose (with volume buttons) the update.zip file on your internal sd card and confirm again with Home-button. You will have to wait for several seconds.
e. Now choose reboot system now and confirm with home button.
Now you device should be rooted.
The link: http://forum.xda-developers.com/showthread.php?t=1317394
2. Enable recovery ClockworkMod v5.5.0.4 with flashing in adb shell.
Don't flash the zip file, but extract and flash the img file
a. Root your devece(look above)
b. Copy downloaded recovery ClockworkMod v5.5.0.4http://www.multiupload.com/KTNBHX6JBG on internal sdcard
c. Disconect phone from copmuter and make sure that USB debugging is on
d. Connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer)
e. Download the adb shellhttps://rapidshare.com/files/1061144422/android-sdk-windows.zip
note:If you just want to obtain and perform adb command, rather than to develop Android software, in fact, there are many adb streamline packets in internet, don't need the full Android SDK.
As the android-sdk version started from r08, adb wasn't contained in the downloaded files from the beginning, but was downloaeded by SDK Manager after that, and adb wasn't under the original tools directory. To maintain the text of the description of teaching would continue to apply the screen, I made ​​out of adb streamlined package from the r07 version.
f. Extract the file android-sdk-windows.zip into the root directory of C for teaching easily
g. open command prompt
windows 7: start-all programs-accessories-command prompt or search cmd
h. Then in the "Command Prompt" window, type the following command to switch to the adb directory
c:
cd c:\android-sdk-windows\tools
i. Enter the "adb shell", enter the phone to start the next command (think of it as the phone has a similar "command prompt" environment)
go on with this code:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip
j. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded.
3. Download which ROM you like
4. Put the zip into Internal SD
5. Boot into ClockWorkMod, backup your current ROM using nandroid (just in case) then, use Install menu to Wipe data/cache and to install it from the SD card.
By the way, when you enter into the ClockWorkMod recovery, press the volume up-down-up for 3 times, you will see the option "go back" in the recovery menu.
Click to expand...
Click to collapse
By this method, is our bootloader is still locked?

Man, with all due respects, your post, and instructions are a mess, and particularly where you show adb commands to flash RzRecovery, then tell ppl here to do this:
go on with this code:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
Click to expand...
Click to collapse
but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip
Click to expand...
Click to collapse
That is a total mess, and you make complicated particularly for noobs, something which is not complicated........
don't you know you have to be careful with "dd".....as it is called sometimes Data Destroyer:
http://www.softpanorama.org/Tools/dd.shtml
Just be careful ppl !!!

i just bought the new phone in germany, and updated to 2.3.6 by kies, then i decided to flash the custom rom, from root to recovery and to rom, so i checked all the trreads here, so i did it like i just said above, and it has worked for 3 days perfectly, so i wanna share my way to do that. because my phone is a new one, so i didnt' need to backup anything...
by the way, have u checked the thread [RECOVERY]Samsung Galaxy W i8150 RZRecovery by qzem??? it's here http://forum.xda-developers.com/showthread.php?t=1376196 i just followed that way...

irishpancake said:
Man, with all due respects, your post, and instructions are a mess, and particularly where you show adb commands to flash RzRecovery, then tell ppl here to do this:
That is a total mess, and you make complicated particularly for noobs, something which is not complicated........
don't you know you have to be careful with "dd".....as it is called sometimes Data Destroyer:
http://www.softpanorama.org/Tools/dd.shtml
Just be careful ppl !!!
Click to expand...
Click to collapse
i just bought the new phone in germany, and updated to 2.3.6 by kies, then i decided to flash the custom rom, from root to recovery and to rom, so i checked all the trreads here, so i did it like i just said above, and it has worked for 3 days perfectly, so i wanna share my way to do that. because my phone is a new one, so i didnt' need to backup anything...
by the way, have u checked the thread [RECOVERY]Samsung Galaxy W i8150 RZRecovery by qzem??? it's here http://forum.xda-developers.com/show....php?t=1376196 i just followed that way...

OK, Felix, it's not really a problem.......
but writing or copy/paste stuff in a Admin Command Prompt is hard enough, without having to modify the text you are quoting.
How hard could it be to post this:
adb shell
$su
#dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Click to expand...
Click to collapse
This is what ppl will have to write into the dd command
if = input file.....of = output file
Use dd cautiously, improperly entering the wrong values could inadvertently wipe, destroy, or overwrite the data on the hard disk drive or device memory
Click to expand...
Click to collapse
BTW, me and qzem were probably two of the first on these forums, before we had dedicated forum......

irishpancake said:
OK, Felix, it's not really a problem.......
but writing or copy/paste stuff in a Admin Command Prompt is hard enough, without having to modify the text you are quoting.
How hard could it be to post this:
This is what ppl will have to write into the dd command
if = input file.....of = output file
BTW, me and qzem were probably two of the first on these forums, before we had dedicated forum......
Click to expand...
Click to collapse
but i have written "but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip" in my first post, haven't u seen that? I am gonna highlight it...but thanks for your remind and works for our SGW

Felix, I give up....but thanks for taking on board my suggestion....it may just save someone from a major catastrophe.
thanx again
ATB

FelixAusChina said:
but i have written "but change the file name RZR-2.1.4-ancora-rec.img to recovery.img from recovery-clockwork-5.5.0.4-ancora.zip" in my first post, haven't u seen that? I am gonna highlight it...but thanks for your remind and works for our SGW
Click to expand...
Click to collapse
The point is - why include the first (i.e. incorrect) version of the command at all? It would be much clearer just to include the correct version, after the change you mention. Including the incorrect version just makes the instructions more confusing.

FelixAusChina said:
But thank all you guys to point it out
Click to expand...
Click to collapse
Man, don't cry!!!!
sorry for being so blunt, but it's important, especially when using adb, and commands like dd to get it exactly right/correct......
we don't wanna brick anyone's phone
But, thanks anyway, the guide is basically good!!!
cheers, OK

FelixAusChina said:
But thank all you guys to point it out
Click to expand...
Click to collapse
Don't mistake directness for hostility.
We didn't want you to remove your guide completely - we're just trying to help improve the quality of it, for everyone's sake. Collaboration is what this forum is all about.
Restore the guide, make the suggested improvements, and let's see if we can make it even better.

[RECOVERY][Xperia S] DooMRecovery (CWM-based recovery){GB}[Rel:v05]{Dt:21/MAY}

------[ UPDATE ]-------
DooMRecovery v05 released! changelog here
------[ UPDATE ]-------
DooMRecovery for Sony Xperia S is based on ClockworkMod recovery source (GB 5.0.2.x).
Credits and special thanks to Koush and everyone else involved in Cyanogenmod project!
{
"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 video is a bit older one from my Xperia Play but gives u an idea how it will work on device)​
[ info ]
firstly i want to thank all the users of this community who donated the device to me! thanks everyone!
so friends i present to u DooMRecovery! its based on CWM 5.0.2.x sources... i have done some additions which i feel makes the recovery a lot smarter... i am still working on the recovery and will be actively maintaining it, so there will be updates as and when i get things working/add new features...
Touch capabilities are added by my teammate (Team UtterChaos) Napstar....
For posting BUGS/issues related to my kernel post them in kernel thread:
http://forum.xda-developers.com/showthread.php?t=1557452
For posting BUGS/issues related to my recovery post them in recovery thread:
http://forum.xda-developers.com/showthread.php?t=1594828
For general discussion regarding my kernel/recovery OR if u want to request for new features, post them in discussion thread:
http://forum.xda-developers.com/showthread.php?t=1596041
RECOVERY IS CURRENTLY AVAILABLE AS PART OF DooMKernel & Advanced Stock Kernel
THE RECOVERY IS STILL WORK IN PROGRESS AND I AM WORKING TO IMPROVE IT!!!
THE RECOVERY IS COMPATIBLE WITH ROM MANAGER!
Start the ROM Manager APP
Click on Menu
Select Manual Flash Override
Click OK at the next prompt
Confirm phone model as "LT26i"
Confirm version as "ClockworkMod 3.x+"
Click OK at the next prompt
thats it ROM Manager is now configured to use this recovery
[ disabled for this device ]
Advanced Menu -> Partition SDcard
[ credits / special thanks ]
Koush - for the brilliant work & coding on CWM recovery
Napstar - for doing most of the work on Touch capabilities for CWM recovery (not fully implemented it)
Frosty666 for the Vibration triggers
FreeXperia Team (Bin4ry & jerpelea) - for tooo many things!!
[ features ]
added a new menu "More Options"
AROMA File Manager is NOW directly accessible via this new menu
current ROM details can be retrieved via this new menu
fixed some internal sdcard (/emmc) related bugs
fixed advanced backup option
fixed this bug
fixed display of "build timestamp" and battery level
some more changes in font color to make it more readable
replaced background with my old favorite (thanks to Soheil)
implemented detection of internal sdcard as /emmc (if required)
slight changes in font color to make it more readable
now features larger XHDPI fonts (thanks to koush)
replaced the bottom "on-screen navigation buttons" with bigger buttons
fixed SDCARD mounting to PC as mass-storage
now recovery can backup/restore kernels and users can flash kernels (kernel.elf)
FULL TOUCH interface
swipe gesture support!!! - the hotspot for this is across full screen
swipe left to GO BACK/ Scroll UP
swipe right to Scroll Down
Honeycomb themed
haptic feedback
incase the recovery "hangs" or incase some unwanted event starts u can press the POWER button to restart the recovery (the device wont reboot, only recovery will restart)
shows current time (time when the recovery was entered/started)
shows the current battery percentage (CURRENTLY BUGGY)
uses new Roboto FONT (from latest CWM repo)
new "select update.zip menu": it will give u a new option - "show file details" - which will display the size (in bytes) and the MD5SUM of the selected file
when any update.zip is selected its complete file name will now be displayed (right at the top) and full path to that file will be printed before flashing begins
added prompt to display the "backup folder name" when user starts restoring a backup
added a warning and option to abort backup if space on sdcard is < 150 MB
removed Wipe cache partition from main menu (u can format /cache from "Mounts & Storage" menu)
removed those tons of "No"s
add confirmation to "backup" option in Nandroid menu... it used to keep getting pressed by mistake and start making backups immediately... now it will ask u before starting backup
replaced "reboot system now" with new menu "reboot options"... now with this new menu u can:
reboot sytem
reboot into recovery
reboot into fastboot mode
Power Off
added "advanced backup" menu (based on amit.bagaria implementations for his CF-Root kernel for SGS-SL)
now u can selectively choose which partitions to backup
its like a toggle
once u have finished choosing which partitions u want just click on "perform backup" and only those partitions will be backed up!!!
revamped layout for recovery menu (to improve navigation) [renamed few options and changed their order]
changed "wipe data/factory reset" option to just "factory reset", and detailed the partitions which will be wiped
changed text of most menus to fit the new honeycomb inspired design
the Nandroid backups & restore now show/displays which files were used to restore/what the backup is called (folder name)
[ known bugs ]
all backups are done get time stamp of year 1970 dont know why this happens but i am trying to sort it out some how
the recovery sometimes hangs - just press power button it will restart recovery without rebooting device
there are some graphics glitches
backups created with v01 recovery might give errors while restoring using v02 recovery... work around is posted here
if you encounter any other bugs/issues DO LET ME KNOW ASAP by posting them in THIS THREAD
[ requirements ]
UNLOCKED BOOTLOADER
fastboot binaries
[ how to install? ]
The recovery in integrated into the kernel! so when u flash the kernel it will contain the recovery!
[ how to enter recovery? ]
the recovery entry key is VOLUME UP button... so when you see the bootlogo watch out for the following notification which will tell u when u press the entry key (VOL UP):
the LED will turn BLUE
the device will vibrate for short duration
the bottom strip will be illuminated
if u press the entry key within this timeframe of the notifications (3 seconds) the device will enter into recovery
[ how to use recovery? ]
hardware keys
VOL UP/VOL DOWN key to move Up/Down in menu
HOME key to SELECT item
BACK key to GO BACK
OR
On-screen Navigation buttons
OR
Full Touch capibility!
[ donations ]
if u feel that this work has helped u OR u think that the work i put into making this is worthy of donations, then click on the following link for buying me some coffee/beer/etc
PAYPAL DONATION LINK
ENJOY!!

DooMRecovery v01 released!
details, changelog at first post!!!
DooMRecovery is currently available ONLY as a part of DooMKernel!
please test out and let me know if u have any bugs/issues in THIS THREAD...
for general discussions use the following thread:
http://forum.xda-developers.com/showthread.php?t=1596041

I have just made an very old recovery backup as it says
Current Time:
12:03:27 GMT Mon 23 Feb 1970
but it feels good to have recory backup back again, thanks.

Hi Doom,
One quick question - is it possible to disable vibration in the recovery?

harfot said:
I have just made an very old recovery backup as it says
Current Time:
12:03:27 GMT Mon 23 Feb 1970
but it feels good to have recory backup back again, thanks.
Click to expand...
Click to collapse
ya i know
its like back to the future
kazuni said:
Hi Doom,
One quick question - is it possible to disable vibration in the recovery?
Click to expand...
Click to collapse
nope i have implemented it as a feature so its easier to check if the "touch response" was registered...

@DooMLoRD
Have you considered to get your CWM based recovery actually on CWM ROM Manager?
Auto Installation would be sweet for something like this for allready rooted users. and much easier to update aswell.
Might be a consideration. I would certainly donate for that to happen. ;D

Just flashed this. Runs good, su works as expected, overclocking is good to have, but I'll probably stick to default or even underclock a bit.
Sent from my LT26i using XDA
Edit: wrong thread, derp.

How about make console runs in recovery mode? With console, we can browse and delete apps in recovery!
The OpenRecovery for Motorola Milestone has this feature!
Thank!

juzz|NOR said:
@DooMLoRD
Have you considered to get your CWM based recovery actually on CWM ROM Manager?
Auto Installation would be sweet for something like this for allready rooted users. and much easier to update aswell.
Might be a consideration. I would certainly donate for that to happen. ;D
Click to expand...
Click to collapse
we dont have dedicated recovery partition... so we cant use any app to flash it...
also only officially supported devices get official CWM from ROM Manager (its limited only to releases by Koush)...
K900 said:
Just flashed this. Runs good, su works as expected, overclocking is good to have, but I'll probably stick to default or even underclock a bit.
Sent from my LT26i using XDA
Edit: wrong thread, derp.
Click to expand...
Click to collapse
yes even i underclock to max 1Ghz
keunhuvac said:
How about make console runs in recovery mode? With console, we can browse and delete apps in recovery!
The OpenRecovery for Motorola Milestone has this feature!
Thank!
Click to expand...
Click to collapse
interesting can u share some details?
PLEASE KEEP THIS THREAD FOR REPORTING ISSUES/BUGS
FOR GENERAL DISCUSSION/FEATURE REQUEST USE THIS THREAD

DooMLoRD said:
we dont have dedicated recovery partition... so we cant use any app to flash it...
also only officially supported devices get official CWM from ROM Manager (its limited only to releases by Koush)...
Click to expand...
Click to collapse
Something I came up with the other day: maybe put the recovery fs in a separate file? Then we can change the ramdisk to either load android normally or mount the recovery image like a ramdisk and boot it. This way any kernel (as long as it supports this method) can coexist with any recovery. Also means we could probably use recovery to flash kernels because it runs from RAM so there's no risk of breaking the recovery.
Sent from my Transformer TF101 using XDA

__ delete

K900 said:
Something I came up with the other day: maybe put the recovery fs in a separate file? Then we can change the ramdisk to either load android normally or mount the recovery image like a ramdisk and boot it. This way any kernel (as long as it supports this method) can coexist with any recovery. Also means we could probably use recovery to flash kernels because it runs from RAM so there's no risk of breaking the recovery.
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
we already did those things for X10, ARC... point is where will u keep the recovery file? if u keep it on /system then its not a true recovery as formatting /system will remove it... and in case of "bad flash" u will be left with no access to recovery...
so we have done the next best thing... integrated recovery into kernel... we use this for all xperia devices...

If I install the recovery with ROM Manager, also install automatically the Kernel?
Are there any requirements to install it?
Thank you!!

treoking said:
If I install the recovery with ROM Manager, also install automatically the Kernel?
Are there any requirements to install it?
Thank you!!
Click to expand...
Click to collapse
installing recovery from ROM Manager is ONLY supported for devices which have dedicated recovery partition and the ones which officially supported by Koush...
only way to get recovery is to flash kernel containing recovery via fastboot

DooMLoRD said:
we already did those things for X10, ARC... point is where will u keep the recovery file? if u keep it on /system then its not a true recovery as formatting /system will remove it... and in case of "bad flash" u will be left with no access to recovery...
so we have done the next best thing... integrated recovery into kernel... we use this for all xperia devices...
Click to expand...
Click to collapse
The idea is to keep the recovery on /boot, but make it possible to run a custom image from /system.
Sent from my Transformer TF101 using XDA

K900 said:
The idea is to keep the recovery on /boot, but make it possible to run a custom image from /system.
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
/boot is the kernel partition, which is not accessible... so essentially its going to be in kernel ramdisk

DooMLoRD said:
/boot is the kernel partition, which is not accessible... so essentially its going to be in kernel ramdisk
Click to expand...
Click to collapse
That's what I meant. I still getting used to the Xperias' internals after three years of HTC/Samsung
Sent from my Transformer TF101 using XDA

K900 said:
That's what I meant. I still getting used to the Xperias' internals after three years of HTC/Samsung
Sent from my Transformer TF101 using XDA
Click to expand...
Click to collapse
hehe...
Xperia are a bit of a pain in the a**...
anyways u all will be happy to know that we can finally flash kernels from recovery/OS to boot partition of this device (Xperia S)...
i have tested and it works well!!

Creating a new file called .hidenandroidprogress in the clockworkmod folder should speed up the nandroid backups eg:
/sdcard/clockworkmod/.hidenandroidprogress
-smc

DooMLoRD said:
hehe...
Xperia are a bit of a pain in the a**...
anyways u all will be happy to know that we can finally flash kernels from recovery/OS to boot partition of this device (Xperia S)...
i have tested and it works well!!
Click to expand...
Click to collapse
Great news Also HTCs can sometimes be even more pain, especially locked ones
Sent from my Transformer TF101 using XDA

[Root, CWM] Micromax A58-- android version 4.2.2

HOW TO ROOT YOUR MICROMAX A58
1. go to settings-> Security-> enable Unknown sources.
2. go to about phone in in settings -> About phone -> tap on the build number several times to enable developer options
3. in settings-> Developer options -> enable Usb Debugging
4. Now download framaroot 1.8.1 apk. download link attached. (Thanks to "alephzain" for this awesome app)
(link to his thread http://forum.xda-developers.com/showthread.php?t=2130276 )
5. install it
6. open and click Boromir exploit
7. voila ur phone is rooted.
8. now reboot to see super su in app drawer
7. check it using root checker app from play store.
{
"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"
}
click thanks if i helped..
CUSTOM RECOVERY SEE BELOW POST

Ctr , twrp, gravity box, link2sd
CUSTOM RECOVERY​
Guys this has been developed by @yuweng @dhinesh77 and @carliv (Master Shifu)
Hats off to the guys for their awesome work.
Dont flash cwm recovery only flash CTR or TWRP recovery because our system format is UBIFS..
just download the CTR auto porting tool from the below thread
http://forum.xda-developers.com/showthread.php?t=1825722
Click to expand...
Click to collapse
(see for "Added on Jan 17, 2014
CTR v2.1 for MTK devices with ubifs ONLY " in the thread)
extract and run the program.
don't forget to install adb drivers before using the above tool. you can find the drivers here.. select other option in phone model.
http://www.mediafire.com/download/seg916ycv20cxj7/drivers.rar
ctr recovery is fully functional....
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
sorry TWRP recovery not working in this method
Hi here is the fully working TWRP recovery for Micromax A58
Quote:
DOWNLOAD recovery from
http://www.mediafire.com/download/9zpdq057829ltbj/recovery.img
Click to expand...
Click to collapse
OR
from the attachment below
STEPS TO INSTALL:
TO FLASH USING MOBILE
Click to expand...
Click to collapse
Flash using Mobileuncle tools (need a rooted phone)
-->Download the recovery and Put it in root of your SDCARD (ROOT OF SDCARD MEANS DON'T PUT THE FILE IN ANY FOLDER)
-->Open Mobile uncle tools and select Recovery Update
-->Flash recovery file
-->Done
Now reboot to recovery to check.....
Credits:
christiantroy
@yuweng
@Dees_Troy
@carliv
@dhinesh77
@dhinesh77
Source
https://github.com/dhinesh77/Team-Win-Recovery-Project
Click to expand...
Click to collapse
link to @dhinesh77 thread
http://forum.xda-developers.com/showthread.php?t=2615386
Click to expand...
Click to collapse
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
STEPS FOR REBOOTING INTO RECOVERY
1. switch of the mobile
2. remove the battery
3. replace the battery
4. hold the power button and volume up button until you see an android robot
5. now press the power button again to go into recovery.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Steps for installing Gravity box
download the xposed module apk from the attachment or from
http://repo.xposed.info/module/de.robv.android.xposed.installer
Click to expand...
Click to collapse
1. After installing apk reboot the phone
2. open the app and select download option
3. now browse to find gravity box[JB] (i mean for jelly bean os)
4. download the latest version
5. install it
6.now go back to modules menu in xposed installer app and tick the gravity box option
7. now reboot your phone
8. enjoy using gravity box
https://www.youtube.com/watch?v=O7p2kW8-nnw
STEPS FOR MAKING LINK2SD WORK
Thanks to @abi.z for the scripts
Steps
1. Partition your sd card to have an ext4 2nd partition. 1 gb partiton max (adviceable) (ext3,ext4 fat32 confirmed working)
2. Install Link2sd from playstore. (dont open it)
3. Copy attached install-recovery.sh to /etc/ using any file manager with root access.
4. open terminal emulator app. and type the following command without quotes
"su" (press enter)
"mkdir /data/sdext2" (press enter)
"chmod 777 /etc/install-recovery.sh" (press enter)
5.Done!! Reboot your system and check link2sd->Storage info to see the mounted partition details.
For people who want to use other partitions
Make the following changes in the mount command in case you are using a different partition/filesystem
Open your install-recovery.sh and
Replace ext4 with ext2/ext3/vfat depending on you second partition.
If using a partition other than 2nd partition, Replace either mmcblk0p2 with mmcblk0p3 OR 179:2 with 179:3 or so on depending on your partition number
then EXECUTE the script or REBOOT for the changes to take place.
INSTALLING VIPER EQUALIZER FOR QUALITY SOUNDS
I HAVE TESTED VIPER FOR ANDROID FX NOT XHiFI AND IS WORKING GR8 IN OUR PHONES
1. Download, extract and copy ViPER4Android_FX.apk (FX version v2.3.2.2 )to your device.
2. Install the apk as USER app or SYSTEM app is up to you.
3. Run FX app from app drawer, allow root access if asked.
4. When driver installation prompted, choose Yes.
5. V4A auto detects your CPU and show available driver modes
6. Choose your desired selection.
7. After installation done, Reboot device.
8. now open the app and select compatibility mode for audio to work.
TO DOWNLOAD THE APP GO TO THE BELOW FORUM
FORUM LINK:
http://vipersaudio.com/blog/?page_id=48
All stock items for micromax A58
< STOCK ITEMS
DRIVERS : http://www.4shared.com/rar/sWXxgEmM/Mobistel_Cynus_T1_Drivers_x86.html
STOCK ROM : https://drive.google.com/uc?id=0B6-h6iUVgfhJbWRIYW9MNmV0UzQ
STOCK BOOT.IMG : http://www.mediafire.com/view/id21q1m9a34b5dr/boot.img
STOCK RECOVERY : http://www.mediafire.com/view/g8tkf2a7qqv0zpu/recovery.img
SP_Flash_Tool : http://www.4shared.com/zip/xsHShvMw/SP_Flash_Tool_exe_v313320187.html/>
DONT FORGET TO CLICK THANKS IF I HELPED
Click to expand...
Click to collapse

confused!!!!
@dhinesh77 bro link2sd app is not working on my phone what about yours??
Do you know any way to fix it. it says mount script cannot be created, no such file or directory
Can we change ubifs to ext4 format.. Or is there any custom roms possible.
I have installed gravity box via xposed module and its really awesome on our phone.
Waiting for ur reply!!!!!:fingers-crossed:

alanvmathew said:
@dhinesh77 bro link2sd app is not working on my phone what about yours??
Do you know any way to fix it. it says mount script cannot be created, no such file or directory
Can we change ubifs to ext4 format.. Or is there any custom roms possible.
I have installed gravity box via xposed module and its really awesome on our phone.
Waiting for ur reply!!!!!:fingers-crossed:
Click to expand...
Click to collapse
I didnt used link2sd so far,
We cant change ubifs to ext4 unless got kernel sources
still custom roms are distant dream because of low system partition memory

dhinesh77 said:
I didnt used link2sd so far,
We cant change ubifs to ext4 unless got kernel sources
still custom roms are distant dream because of low system partition memory
Click to expand...
Click to collapse
Oh it hurtz.
Can we flash recovery using mobile uncle tools??? Or we can't? If we can then I all make a tutorial for it here.

alanvmathew said:
Oh it hurtz.
Can we flash recovery using mobile uncle tools??? Or we can't? If we can then I all make a tutorial for it here.
Click to expand...
Click to collapse
I tried with recovery manager it worked, didnt tried with mobileuncle app

dhinesh77 said:
I tried with recovery manager it worked, didnt tried with mobileuncle app
Click to expand...
Click to collapse
kewl ll make one then...... what happened to link2sd bro?? did u try?
or is there any other script that can work for us?

alanvmathew said:
kewl ll make one then...... what happened to link2sd bro?? did u try?
or is there any other script that can work for us?
Click to expand...
Click to collapse
@dhinesh77 bro link to sd any news?????

Rooted but Cannot enter Recovery mode
Hi
I rooted my a 58 using FramRoot, installed gravity toolbox also.
However i try, Iam not able to get into recovery.
#Tried flashing using Mobile Uncle, it flashes and asks to reboot to recovery.But again boots into normal os.
On powering on with vol+ and power button it shows only new Bolt logo(white letters in green trapezium) and no android
I tried rebooting into recover with different tools but all same result.
# Tried running the CTRv2.1-ubifs.exe a no of times.
It detects my MT6572 SoC and asks for root rights on phone, but fails after issueing dd commands with the following message on pc screen "Error detected, cannot unpack recovery.img"
I had around 90mb free space in data partition.
#
This is what I could observe, if iam trying to get into recovery it shows bolt logo as said above, then black screen and again comes to bolt logo and continues a normal boot.
Tried vol- and power button. Took me to some chinese factory testing menu.I could test my device hardware and also could do a factory reset from that menu.But not idea how to get into recovery from there.
I have all the drivers installed and I am not a newbiew, has flashed a lot of recoveries and custom roms on diff devices.
I followed @dhinesh77 thread and the cat /proc/mtd command screenshot is attached.
I have no idea what iam missing here, If you need any details i can provide the same.Please help me

abi.z said:
Hi
I rooted my a 58 using FramRoot, installed gravity toolbox also.
However i try, Iam not able to get into recovery.
#Tried flashing using Mobile Uncle, it flashes and asks to reboot to recovery.But again boots into normal os.
On powering on with vol+ and power button it shows only new Bolt logo(white letters in green trapezium) and no android
I tried rebooting into recover with different tools but all same result.
# Tried running the CTRv2.1-ubifs.exe a no of times.
It detects my MT6572 SoC and asks for root rights on phone, but fails after issueing dd commands with the following message on pc screen "Error detected, cannot unpack recovery.img"
I had around 90mb free space in data partition.
#
This is what I could observe, if iam trying to get into recovery it shows bolt logo as said above, then black screen and again comes to bolt logo and continues a normal boot.
Tried vol- and power button. Took me to some chinese factory testing menu.I could test my device hardware and also could do a factory reset from that menu.But not idea how to get into recovery from there.
I have all the drivers installed and I am not a newbiew, has flashed a lot of recoveries and custom roms on diff devices.
I followed @dhinesh77 thread and the cat /proc/mtd command screenshot is attached.
I have no idea what iam missing here, If you need any details i can provide the same.Please help me
Click to expand...
Click to collapse
I have even tried dd ing the recovery image provided to the recovery partition manually.write was successfull. But no hope.I doesnt come to recovery menu.VolUp+power comes to bolt logo ans then restarts and continue normal boot
Need your help !

abi.z said:
I have even tried dd ing the recovery image provided to the recovery partition manually.write was successfull. But no hope.I doesnt come to recovery menu.VolUp+power comes to bolt logo ans then restarts and continue normal boot
Need your help !
Click to expand...
Click to collapse
thanks guys it seemes uploaded is corrupted i will check this weekend , meanwhile try ctr recovery its expected to work 100%
---------- Post added at 06:31 AM ---------- Previous post was at 06:30 AM ----------
abi.z said:
I have even tried dd ing the recovery image provided to the recovery partition manually.write was successfull. But no hope.I doesnt come to recovery menu.VolUp+power comes to bolt logo ans then restarts and continue normal boot
Need your help !
Click to expand...
Click to collapse
alanvmathew said:
@dhinesh77 bro link to sd any news?????
Click to expand...
Click to collapse
Sry bro i dont have enugh space to make ext parttion on sdcard , so i cant able to check

@dhinesh77
Thnx dude..I was wondering wats wrong with my phone s recovery mode..
As mentioned in my prev post that ctr auto porting tool fails in last step too.tried on winxp.
Waiting for or next upload bro.thanks for your works
BTW will try ctr again toninght
Sent from my Micromax A58 using xda app-developers app

abi.z said:
Hi
I rooted my a 58 using FramRoot, installed gravity toolbox also.
However i try, Iam not able to get into recovery.
#Tried flashing using Mobile Uncle, it flashes and asks to reboot to recovery.But again boots into normal os.
On powering on with vol+ and power button it shows only new Bolt logo(white letters in green trapezium) and no android
I tried rebooting into recover with different tools but all same result.
# Tried running the CTRv2.1-ubifs.exe a no of times.
It detects my MT6572 SoC and asks for root rights on phone, but fails after issueing dd commands with the following message on pc screen "Error detected, cannot unpack recovery.img"
I had around 90mb free space in data partition.
#
This is what I could observe, if iam trying to get into recovery it shows bolt logo as said above, then black screen and again comes to bolt logo and continues a normal boot.
Tried vol- and power button. Took me to some chinese factory testing menu.I could test my device hardware and also could do a factory reset from that menu.But not idea how to get into recovery from there.
I have all the drivers installed and I am not a newbiew, has flashed a lot of recoveries and custom roms on diff devices.
I followed @dhinesh77 thread and the cat /proc/mtd command screenshot is attached.
I have no idea what iam missing here, If you need any details i can provide the same.Please help me
Click to expand...
Click to collapse
Did u install busy box in phone before proceeding. Try installing busy box. Then in ctr try manual porting option and use the stock recovery.IMG. if u did not take back up of stock.IMG I can share it with u. It will work I too had this problem... If u have any doubt ask me.
i am gonna share two roms with you u can use it.
T-09 version rom
http://www.adrive.com/public/RYVRp2.html
T-07 version rom
http://www.4shared.com/zip/wB64yz-vce/A58_T07_2_.html
extract the correct version of rom for your phone and use the recovery.img . you can see the version in about phone option or by removing the battery.

alanvmathew said:
Did u install busy box in phone before proceeding. Try installing busy box. Then in ctr try manual porting option and use the stock recovery.IMG. if u did not take back up of stock.IMG I can share it with u. It will work I too had this problem... If u have any doubt ask me.
i am gonna share two roms with you u can use it.
T-09 version rom
http://www.adrive.com/public/RYVRp2.html
T-07 version rom
http://www.4shared.com/zip/wB64yz-vce/A58_T07_2_.html
extract the correct version of rom for your phone and use the recovery.img . you can see the version in about phone option or by removing the battery.
Click to expand...
Click to collapse
Thanks dude.
 @dinesh77 s post helped me to conclude the issue.
Your post led me back on track and thanks for uploading the roms. Although i dint download because of my limited conn speed, itll be of help to someone.
Here's how i solved the issue.
I checked unpacking my existing recovery image and it was corrupted.
I was having a problem since i flashed the corrupted recovery initially, and lateron ctr porting tool was not able extract the existing recovery details for porting.
So i got twrp recovery from your the mediafire link in the first post did a porting and then everything worked fine with ctr recovery.
twrp recovery was running, but backup functionality wasnt working.
Iam not able to use advanced restore from ctr recovery.
All othr functions works from ctr..
---------- Post added at 12:53 PM ---------- Previous post was at 12:46 PM ----------
dhinesh77 said:
I didnt used link2sd so far,
We cant change ubifs to ext4 unless got kernel sources
still custom roms are distant dream because of low system partition memory
Click to expand...
Click to collapse
@alanvmathew
Good News bro, I have somehow managed to get link2sd working with fat32.Had to do a lot of trial and error with manual mounting and reformating and reformating..
Was after link2sd till 3:00am
In office now. Will try to reproduce the issues and soon come up with the correct solution for link2sd after iam home.

link2sd
abi.z said:
Thanks dude.
@dinesh77 s post helped me to conclude the issue.
Your post led me back on track and thanks for uploading the roms. Although i dint download because of my limited conn speed, itll be of help to someone.
Here's how i solved the issue.
I checked unpacking my existing recovery image and it was corrupted.
I was having a problem since i flashed the corrupted recovery initially, and lateron ctr porting tool was not able extract the existing recovery details for porting.
So i got twrp recovery from your the mediafire link in the first post did a porting and then everything worked fine with ctr recovery.
twrp recovery was running, but backup functionality wasnt working.
Iam not able to use advanced restore from ctr recovery.
All othr functions works from ctr..
---------- Post added at 12:53 PM ---------- Previous post was at 12:46 PM ----------
@alanvmathew
Good News bro, I have somehow managed to get link2sd working with fat32.Had to do a lot of trial and error with manual mounting and reformating and reformating..
Was after link2sd till 3:00am
In office now. Will try to reproduce the issues and soon come up with the correct solution for link2sd after iam home.
Click to expand...
Click to collapse
Congratulation bro! And please share the procedure here so we can also get benefit of it. Thanks in advance.

Increase internal Memory !! Link2sd Working !! [Use Manual mount Script]
Steps
1. Partition your sd card to have an ext4 2nd partition. I used a second primary partition of 512mb (ext3,ext4 fat32 confirmed working)
2. Install Link2sd from playstore.
3. Mount /system read-write and Copy attached install-recovery.sh to /etc/ using any file manager with root access.
4. Using filemanager(root) goto /data and create directory sdext2. or mkdir /data/sdext2 using root terminal
5. Set permissions on the copied file using filemanager(root) as in screenshot or chmod 777 /etc/install-recovery.sh using root terminal.
6. Done!! Reboot your system and check link2sd->Storage info to see the mounted partition details.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Incase you want to test if link2sd will work or not with your current sdcard 2nd partition, issue the commands in terminal
su
mkdir /data/sdext2
mount -t ext4-o rw /dev/block/mmcblk0p2 /data/sdext2
or
mount -t ext4 -o rw /dev/block/vold/179:2 /data/sdext2
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Make the following changes in the mount command in case you are using a different partition/filesystem
Open your install-recovery.sh and
Replace ext4 with ext2/ext3/vfat depending on you second partition.
If using a partition other than 2nd partition, Replace either mmcblk0p2 with mmcblk0p3 OR 179:2 with 179:3 or so on depending on your partition no.
!!eNJOY!!

abi.z said:
@dhinesh77
Thnx dude..I was wondering wats wrong with my phone s recovery mode..
As mentioned in my prev post that ctr auto porting tool fails in last step too.tried on winxp.
Waiting for or next upload bro.thanks for your works
BTW will try ctr again toninght
Sent from my Micromax A58 using xda app-developers app
Click to expand...
Click to collapse
It seems root access was denied for ctr auto port tool, hence why you failed, reinsure that you have running auto port tool under c:/ ; anyhow I will upload ctr compiled recovery too on this weekend sry or delay

dhinesh77 said:
It seems root access was denied for ctr auto port tool, hence why you failed, reinsure that you have running auto port tool under c:/ ; anyhow I will upload ctr compiled recovery too on this weekend sry or delay
Click to expand...
Click to collapse
@dhinesh77 Ya please upload so that others can use it.. If you want i can upload ported ctr recovery.
It was not root access causing problems,I had flahed the corrupted download to phone initially and then the recovery.img which ctr was reading from my phone was corrupted for autoporting tool to work on, and was failing while extracting the .img..
1 week old Bolt A58 with Root+Gravity+CTR+Link2sd
Everything is fixed now, and i will be gifting it to my father this weekend.
Thanks for help everyone

abi.z said:
Steps
1. Partition your sd card to have an ext4 2nd partition. I used a second primary partition of 512mb (ext3,ext4 fat32 confirmed working)
2. Install Link2sd from playstore.
3. Mount /system read-write and Copy attached install-recovery.sh to /etc/ using any file manager with root access.
4. Using filemanager(root) goto /data and create directory sdext2. or mkdir /data/sdext2 using root terminal
5. Set permissions on the copied file using filemanager(root) as in screenshot or chmod 777 /etc/install-recovery.sh using root terminal.
6. Done!! Reboot your system and check link2sd->Storage info to see the mounted partition details.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Incase you want to test if link2sd will work or not with your current sdcard 2nd partition, issue the commands in terminal
su
mkdir /data/sdext2
mount -t ext4-o rw /dev/block/mmcblk0p2 /data/sdext2
or
mount -t ext4 -o rw /dev/block/vold/179:2 /data/sdext2
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Make the following changes in the mount command in case you are using a different partition/filesystem
Open your install-recovery.sh and
Replace ext4 with ext2/ext3/vfat depending on you second partition.
If using a partition other than 2nd partition, Replace either mmcblk0p2 with mmcblk0p3 OR 179:2 with 179:3 or so on depending on your partition no.
!!eNJOY!!
Click to expand...
Click to collapse
WORKED.......!!!!!!! :laugh::laugh::laugh:

abi.z said:
@dhinesh77 Ya please upload so that others can use it.. If you want i can upload ported ctr recovery.
It was not root access causing problems,I had flahed the corrupted download to phone initially and then the recovery.img which ctr was reading from my phone was corrupted for autoporting tool to work on, and was failing while extracting the .img..
1 week old Bolt A58 with Root+Gravity+CTR+Link2sd
Everything is fixed now, and i will be gifting it to my father this weekend.
Thanks for help everyone
Click to expand...
Click to collapse
Mr.Carliv has updated his recovery version to 2.2 , ported just now and updated in main post , all bugs fixed in ctr recovery too :good:

[WinApp][v2.4-Beta][+RemixOS] Android-x86 Installer UEFI Version

Code:
*** Disclaimer
Use this software at your own Risk,I am not responsible for any damage that may be caused by this software.
I have tested it on all machines i have, don't know if you have any special cases.
Description
This Installer will let you install Android x86 on your PC like any other application, no risk to Damage HDD Partitions, Boot Data or User Data. After installation you will got an option at boot to select Windows or Android.
This Installer is currently targets only Windows 8 / UEFI-Enabled Devices​
System Requirements
UEFI-Enabled x86 PC
Secure Boot Disabled
Bitlocker disabled on target drive
Windows 8/8.1/10
.Net Framework 4.5
Android System image with UEFI Support
Screenshot
{
"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"
}
Change log
v2.4
Update Detection of RemixOS image [Use RemixOS ver: B2016012301 or higher]
Fix UEFI Init Fail with Surface Pro devices
v2.3
Add support for RemixOS
v2.2
Fix reading large UEFI entries
Fix using img file from path with spaces
Trial period Removed
Add GPU Options to GRUB Bootlist
v2.1
User-defined Data size
Responsive UI
Installation Status update
Support Devices with 32-bit firmware
Support booting from NTFS with compression enabled
log includes more info about Device BIOS
v2.0
Initial Version
Features
Install/Uninstall Android directly from Windows
Support UEFI-Enabled devices
Support legacy BIOS devices [not available in Alpha version]
Install to Any FAT32/NTFS partitions
Instructions
Install
Download Android EFI Enabled img file from: [LINK]
Launch the Installer
Select the downloaded IMG file
Select "Data Size" for file which will be used to store downloaded Apps and User Settings
Select the partition which Android will be installed to.
Click Install and wait ... The installation will take about 5 min. or less, it is based on your hard drive speed.
How to Enter Android
Go to Windows power menu and Click on "Restart" while holding shift [Screenshot]
Select "Use a device"
Select "Android-OS"
Now your PC will reboot to Android
Uninstall
Launch the Installer
Select "Cleanup Android"
Under the hood
The installer will verify the system requirements on launch
directory: "<TargetPartition>AndroidOS" will be used for installation
Extract the IMG file
Create user data partition
Install grubx64 to UEFI partition
Install new UEFI boot entry for Android
Downloads:
For UEFI-Enabled PCs: [UEFIInstallerv24-5800.exe]
For Legacy-BIOS PCs: [Old Thread]
Important notes (Read it carefully)
This version for testers only, not for end users
Please don't redistribute this version of the installer
Please please report your device model and if installation was successful or not
Any bug/problem/issue reported shall have installer log (which can be found in your C: ) attached and a screenshot
you can read the log before sending it if you have any privacy concerns
The installer will not allow installation on non-UEFI Devices for now
Verify that you downloaded .IMG file not .ISO file
if you have found a bug inside Android you should contact android-x86 team not to post here
Your feedback is highly appreciated
XDA:DevDB Information
Android-x86 Installer for Windows, Tool/Utility for the Windows 8 General
Contributors
ExtremeGTX
Version Information
Status: Beta
Current Beta Version: V2.4
Beta Release Date: 2016-02-05
Created 2015-10-15
Last Updated 2016-02-13

Looks amazing, gonna try it for sure, thanks for this tool!
EDIT: Tried it (ASUS T100TAM, Windows 10 x86), installation failed unfourtunately. Adding log from installation:
================Installer Info================
Installer Directory:C:\Users\****\AppData\Local\Temp\droidinst_efi
Installer Version:2.0.5761.39882
Secure Boot ... Disabled
Manufacturer: ASUSTeK COMPUTER INC.
Model: T100TAM
Product: T100TAM
BIOS Version: T100TAM.204
Available GPU(s):
GPU: Intel(R) HD Graphics
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
OS Type: ... fail
==========================================
====Install Started on 18.10.2015 10:52:53====
-ISO File: C:\Downloads\android-x86-4.4-r3.iso
-TargetDrive: C
-UserData: 1000k
-Setup Directories...
-Folder Created: C:\AndroidOS
-Extract ISO
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\7z.exex C:\Downloads\android-x86-4.4-r3.iso "kernel" "ramdisk.img" "initrd.img" "system.sfs" -oC:\AndroidOS
-Extract SFS
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\7z.exe x C:\AndroidOS\system.sfs "system.img" -oC:\AndroidOS
-Create Data.img
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\dd.exeif=/dev/zero of=C:\AndroidOS\data.img ibs=1k count=1000k
-Initialize Data.img
#Launch:C:\Users\****\AppData\Local\Temp\droidinst_efi\mke2fs.exe-F -t ext4 "C:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Setup Boot Directory...
-Boot Folder Created: Z:\EFI\Android\
-Copy Boot files
-Add UEFI Entry
UEFI Init Fail
==============Revert Installation==============
-Cleaning up Android Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
Folder is not empty.
-UEFI Init ... fail
-Cleaning up Android Directory ... Z:\EFI\Android\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
Click to expand...
Click to collapse

Check the New version
v2.1
User-defined Data size
Responsive UI
Installation Status update
Support Devices with 32-bit firmware
Support booting from NTFS with compression enabled
log includes more info about Device BIOS

ExtremeGTX said:
Code:
*** Disclaimer
Use this software at your own Risk,I am not responsible for any damage that may be caused by this software.
I have tested it on all machines i have, don't know if you have any special cases.
Click to expand...
Click to collapse
I get an error saying no kernel is installed
error no such device /AndroidOS/system.sfs
error file /AndroidOS/kernel not found
error you need to load the kernel first
EDIT: Also as a note both those files exist in C:\AndroidOS\system.sfs and C:\AndroidOS\kernel

ChrisJ951 said:
I get an error saying no kernel is installed
error no such device /AndroidOS/system.sfs
error file /AndroidOS/kernel not found
error you need to load the kernel first
EDIT: Also as a note both those files exist in C:\AndroidOS\system.sfs and C:\AndroidOS\kernel
Click to expand...
Click to collapse
it seems like bootloader can't access your Disk!
can you please post a screenshot of "Disk Management" :
- Open run and type: diskmgmt.msc then take screenshot like this [LINK]
- OR open start menu and type Disk Management

New version works perfectly! No problems at all, just tried Android x86 4.4 and Android x86_64 5.1 aswell on ASUS T100TAM (32GB version), both worked without any trouble - thanks a lot for this amazing tool!
Anyway a small question here - is it possible to create a shortcut in Windows, that could restart device directly into Android? Just a quick guess

spenat said:
New version works perfectly! No problems at all, just tried Android x86 4.4 and Android x86_64 5.1 aswell on ASUS T100TAM (32GB version), both worked without any trouble - thanks a lot for this amazing tool!
Anyway a small question here - is it possible to create a shortcut in Windows, that could restart device directly into Android? Just a quick guess
Click to expand...
Click to collapse
Thanks , kindly post the installation log found at C:\AndroidInstall_XXX.log as this give me info about conditions where installation is successful/unsuccessful
For booting to Android we may have 2 options:
- Desktop shortcut "Reboot to Android"
- Set GRUB as default bootloader

ExtremeGTX said:
Thanks , kindly post the installation log found at C:\AndroidInstall_XXX.log as this give me info about conditions where installation is successful/unsuccessful
For booting to Android we may have 2 options:
- Desktop shortcut "Reboot to Android"
- Set GRUB as default bootloader
Click to expand...
Click to collapse
I think, that setting GRUB as default bootloader would be definitely great way to do this. But, of course, whatever you think it's better and/or easier to do
Anyway, my device is (as stated before) ASUS T100TAM (Intel Atom z3775, 2GB RAM, UEFI device), running Windows 10 Home x86. Secure boot, of course, disabled. Adding install log as an attachment.

So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk

dokie80 said:
So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am not the creator of this app, but since I used it succesfully, I can definitely answer these questions:
1. No, you don't need to worry about that.
2. Yes, exactly - all data will be in this folder (as it is on my TF100)
3. It creates "data.img" file inside the "C:\androidos" folder and you can select how big that .img file should be (for storing your Android data). No partitioning - basically everything happens inside the "androidos" folder.

Thanks for the reply.
Whats the benefit of this method over the magic stick one anyway ?
I'm going to try this tomorrow
Thanks
Sent from my Nexus 5 using Tapatalk

dokie80 said:
Thanks for the reply.
Whats the benefit of this method over the magic stick one anyway ?
I'm going to try this tomorrow
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The biggest benefit is (obviously) that you don't need any flash drive for this - everything is done from your tablet's memory (basically a dualboot) and it's very, very easy to do this.

AFAIK, you can install the android x86 to via magic stick, although I haven't try it yet. I'm using it for Ubuntu. Did you use it daily? How about battery life and performance? Can't wait to try
Sent from my Nexus 5 using Tapatalk

Well yeah, you can, but AFAIK you would have to do repartitioning as if you were installing regular dualboot system - that's something you don't have to do here.
Performance is great as expected, very snappy, I've been running KitKat 4.4-r3, Lollipop 5.1 was very unstable for me. Battery life seems great, too, not exactly sure though, since I've been playing with it for two days now

spenat said:
I think, that setting GRUB as default bootloader would be definitely great way to do this. But, of course, whatever you think it's better and/or easier to do
Anyway, my device is (as stated before) ASUS T100TAM (Intel Atom z3775, 2GB RAM, UEFI device), running Windows 10 Home x86. Secure boot, of course, disabled. Adding install log as an attachment.
Click to expand...
Click to collapse
Thanks for posting the log.
My only concern with setting GRUB as default bootloader if GRUB has a problem running on the device the user may think that the device is bricked and no longer usable, anyway we will check back on that.
dokie80 said:
So to make it clear,
1. I don't have to re partition the SSD, right?
2. The android will be installed in c:/androidos?
3. What you mean about "create user data partition"? Is it going to change disk partition and create dedicated one for it?
Thanks
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
exactly as @spenat told you.
the Advantage of this installer is you will not mess up anythings, no re-partitioning at all or corrupting the current installation of windows. All of the magic just live in <Drive:>\AndroidOS
and if you don't like it you can launch the installer and click on "Cleanup Android" you can check all installation steps in log if you have any concerns.
Thanks
spenat said:
I am not the creator of this app, but since I used it succesfully, I can definitely answer these questions:
1. No, you don't need to worry about that.
2. Yes, exactly - all data will be in this folder (as it is on my TF100)
3. It creates "data.img" file inside the "C:\androidos" folder and you can select how big that .img file should be (for storing your Android data). No partitioning - basically everything happens inside the "androidos" folder.
Click to expand...
Click to collapse
spenat said:
Well yeah, you can, but AFAIK you would have to do repartitioning as if you were installing regular dualboot system - that's something you don't have to do here.
Performance is great as expected, very snappy, I've been running KitKat 4.4-r3, Lollipop 5.1 was very unstable for me. Battery life seems great, too, not exactly sure though, since I've been playing with it for two days now
Click to expand...
Click to collapse
Thanks for your clear answers, appreciate your help

installing now. will I be able to change data size later?

dokie80 said:
installing now. will I be able to change data size later?
Click to expand...
Click to collapse
You can only change data size before you actually install the Android. If you wanna change it later, you need to remove Android and install it again with different data size, AFAIK.

working fine here T100TA, well.. the installation that is.
on android x86, I got a freeze on wifi setting... force close and re-set works fine..
if you dont mind me asking questions:
1. what method are you using for this to work? I dont need it to be detailed, I just curious what's it called, and how AndroidOS listed on device option on advanced boot
2. how to do nandroid backup? I assume for "dirty flash" : I backup data.img and put back after new installation? with the downside is data size is from previous setup?
3. I see that sdcard is mounted, but havent try to see it with file explorer, I assume the whole C: is mounted or probably only AndroidOS folder? so I can do Titanium Backup saved there?
4. for now, I have to boot to windows and boot to android using advanced boot? so without keyboard attached, I have to choose settings - recovery - advanced startup? will it be possible to boot using grub bootloader? I'm planning to dual boot with linux later. just realize that it also show up on boot selection.
many thanks for this. attached is the log found at C:

dokie80 said:
working fine here T100TA, well.. the installation that is.
on android x86, I got a freeze on wifi setting... force close and re-set works fine..
if you dont mind me asking questions:
1. what method are you using for this to work? I dont need it to be detailed, I just curious what's it called, and how AndroidOS listed on device option on advanced boot
2. how to do nandroid backup? I assume for "dirty flash" : I backup data.img and put back after new installation? with the downside is data size is from previous setup?
3. I see that sdcard is mounted, but havent try to see it with file explorer, I assume the whole C: is mounted or probably only AndroidOS folder? so I can do Titanium Backup saved there?
4. for now, I have to boot to windows and boot to android using advanced boot? so without keyboard attached, I have to choose settings - recovery - advanced startup? will it be possible to boot using grub bootloader? I'm planning to dual boot with linux later. just realize that it also show up on boot selection.
many thanks for this. attached is the log found at C:
Click to expand...
Click to collapse
Thanks for testing and posting the install log
Answers:
1. Check section "Under the hood" in the first post or check the installer log you have posted, it will give you an idea about the magic
2. This is an old request from a few users to allow reinstall/update android without removing userdata. Till now your workaround is valid, I think you will see message like this one [LINK] at the first boot after upgrade.
3. I 'm not sure right now.
4. here are 2 solutions to access Android:
a Shortcut on Desktop "Reboot to Android"
Set GRUB as default Bootloader, I can't do this right now as the app still in alpha stage and a lot of testing is needed. i don't want to mess up devices with something not ready yet, so currently i just add GRUB to UEFI Boot options but don't make it the default one.
Thanks for your feedback and questions

Just a quick tip to make dual-booting even easier:
Set the "Boot Option #1" in BIOS to Android-OS (instead of Windows Boot Manager), this way it will always boot to GRUB. Just one catch: You will need a keyboard to move in GRUB, or you will always boot to Android But, of course, you can anytime switch back to Windows Boot Manager as default, as long as you can access BIOS
Anyway, just tried this app on my brother's tablet (Lenovo Miix 3 10"), will add installation log ASAP.

Workarounds for low internal memory

I bought the XZ1C from USA to India as it is not available at all in Indian markets (and never will be - because no compact devices were launched in India). I love this device except for one thing. Low internal memory - and I bet others might also be annoyed by this. There's two workarounds that I could immediately think of but can't be implemented with this Device.
1. Adoptable storage : Adopt external SD card as internal storage - this is one of the coolest features Oreo has to offer, but can't be used in this device. I went through a lot of blog posts and followed the steps, also read about the adoptable storage leading to no solution. I have a Samsung 128GB EVO SD card and I tried to adopt it as an internal storage in more than one ways with no success.
2. Move apps to SD : I thought I could move at least some apps if not all to external SD but this feature that was introduced in Android 2.2 (I remember using it on my Samsung Galaxy Apollo i5801) and re-introduced in 5.0. But this is also not working. I also tried enabling 'Force allow apps on external' under developer options which didn't work.
As I don't have this phone officially supported in my country, I want to check if someone can contact Sony support in their country (US, UK, Germany) to help fix this through an update maybe?
Another purpose of this thread is to discuss alternate workarounds if anyone has tried any and worked for them.

Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.

mhaha said:
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
Click to expand...
Click to collapse
I agree with you. I am going to wait for a while and see if Sony pushes an update that provides move apps to SD option (which I highly doubt they will). But if there comes a point where I desperately need space, I will root the phone. Out of 6 phones that I've used in past 6 years, this is the first one I haven't rooted and ain't planning to.

Possible Solution
I've looked at a thread from the sony forums. Some people were able to get the microSD card to work by factory resetting the phone with the SD card inside. Hope this helps.
What I've done now is to factory reset the phone with the sd card inserted and boot and setup the phone with the sd card in place this time. Then format it again thru the phone (I have not activated sd card encryption yet) and all of a sudden spotify, netflix, ... work with the sd card just as expected.
So perhaps one of you, who experience the same thing, might want try out if this is reproduceable.
Keep the sd card in the phone
Factory reset (I did it via the Xperia companion desktop software)
Boot it up again
Format SD Card
Click to expand...
Click to collapse

Antilogy said:
I've looked at a thread from the sony forums. Some people were able to get the microSD card to work by factory resetting the phone with the SD card inside. Hope this helps.
Click to expand...
Click to collapse
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...

Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disable by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
That means the TC should be able to do that.

Antilogy said:
That means the TC should be able to do that.
Click to expand...
Click to collapse
What r u referring to?
( and "tc" =?... This ain't Twitter u know.. U can write as long as u can ?)

Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
Dany XP said:
What r u referring to?
( and "tc" =?... This ain't Twitter u know.. U can write as long as u can )
Click to expand...
Click to collapse
Sorry. I meant to say topic creator. In this case that would be @kaustubhg123.

You can actually use a little neat trick:
Unlock your bootloader
Install XperiFix ( https://www.xperifix.com ) - XDA Thread to restore camera and X-R,BionZ functions (thanks a lot Sony, for nothing)
Xperifix auto install Magisk 16
Use [Magisk Module] Magic Folder Binder (fbind) module to "join" your internal folders with SDCARD and bind folders like Downloads, DCIM, .android
For example if you download a file, even if the phone downloads it to the internal memory it will be actually on the SDCARD. fbind also moves the old data to sdcard when you configure fbind.

mhaha said:
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
Click to expand...
Click to collapse
I'm still very very green to android and to using Xperia Android phones ... what consequences and compromises are to be faced wtih rooting bootloader? From looking at former threads from over 4yrs ago it seemed that rooting was THE holy grail and raison de T'etre for having an Android (reason for being/having).

Supa_Fly said:
I'm still very very green to android and to using Xperia Android phones ... what consequences and compromises are to be faced wtih rooting bootloader? From looking at former threads from over 4yrs ago it seemed that rooting was THE holy grail and raison de T'etre for having an Android (reason for being/having).
Click to expand...
Click to collapse
Sony have given developers and java enthusiasts the finger with this latest bootloader. There isn't a way to save the encrypted keys (unique to your phone) before unlocking it. So you can unlock it to do development, but it's a one way step, which breaks the camera and a few other functions.
In the past my two main reasons for rooting were to theme the phone a different colour and to save battery. Theming can be done without root now and my battery lasts three days anyway.
Having said that, I have just flashed sToRm//'s TWRP + KERNEL + ROOT + DRM fix/restore (because there’s a rooting enthusiast inside every android owner) and everything is working perfectly. The camera is working and all the software functions correctly.
But rooting the phone to get you control over moving apps to the SD card is a bit extreme and a lot of work for a very minor inconvenience. What are you doing with a small compact phone if you want to use two or three hundred apps?

Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
What good reasons?
I have enabled all apps to save their things on SD card (The camera app stores all photos on SD by default but the stupid Album app stores its thumbnails data on internal memory for no reason). My main big issue is with WhatsApp which stores its data on internal memory and provides no option to store it on SD card. WhatsApp is almost 11GB on my phone now.

mhaha said:
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that..
Click to expand...
Click to collapse
The Xperia V & Z1c both allowed apps to store their data on SD (Spotify, Audible, etc.) but can't do it on this phone :/ Apparently, Oreo blocks us from using our SD card in this way.

luminoso said:
You can actually use a little neat trick:
Unlock your bootloader
Install XperiFix ( https://www.xperifix.com ) - XDA Thread to restore camera and X-R,BionZ functions (thanks a lot Sony, for nothing)
Xperifix auto install Magisk 16
Use [Magisk Module] Magic Folder Binder (fbind) module to "join" your internal folders with SDCARD and bind folders like Downloads, DCIM, .android
For example if you download a file, even if the phone downloads it to the internal memory it will be actually on the SDCARD. fbind also moves the old data to sdcard when you configure fbind.
Click to expand...
Click to collapse
so, luminoso, in that case, can i transfer apps from phone to sd card?
because you are talking about bind the download folder, but having 10gb on my whatsaap i was really interested in move this ffrom phone storage to sd card

reckfield said:
so, luminoso, in that case, can i transfer apps from phone to sd card?
because you are talking about bind the download folder, but having 10gb on my whatsaap i was really interested in move this ffrom phone storage to sd card
Click to expand...
Click to collapse
You can bind whatsapp folder in that case

luminoso said:
You can bind whatsapp folder in that case
Click to expand...
Click to collapse
I decided to go ahead with xperifix, i have g441 compact xz1 european version, last firmware a.12a.179. i tried several times , but its not working with xperifix 2.5 last version
i attached some logs
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
06-6-2018_18-14-51 ===> List /system
Luminoso, do you have any idea¨?

reckfield said:
I decided to go ahead with xperifix, i have g441 compact xz1 european version, last firmware a.12a.179. i tried several times , but its not working with xperifix 2.5 last version
i attached some logs
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
06-6-2018_18-14-51 ===> List /system
Luminoso, do you have any idea¨?
Click to expand...
Click to collapse
Patching of your twrp recovey is needed.
I had to patch it with the last recovery (26. May) https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
if you do it your twrp is not safe !
At first download Android kitchen, extract it.
Copy your twrp file into the folder and open unpackimgbat
After finish you have a folder called "ramdisk", open it.
Inside you open the file "prop.default" with your texteditor.
find the following two parameter and set them to 0:
ro.secure=1
ro.adb.secure=1
save the file, go one folder up and click on repackimg.bat.
You have a "new-recovery.img" file.
Boot your device into fastboot:
fastboot flash recovery <path of your new recovery.img>
The solution works, but device security is in danger.
You can use it, or wait for a new twrp.

Raz0Rfail said:
Patching of your twrp recovey is needed.
I had to patch it with the last recovery (26. May) https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
if you do it your twrp is not safe !
At first download Android kitchen, extract it.
Copy your twrp file into the folder and open unpackimgbat
After finish you have a folder called "ramdisk", open it.
Inside you open the file "prop.default" with your texteditor.
find the following two parameter and set them to 0:
ro.secure=1
ro.adb.secure=1
save the file, go one folder up and click on repackimg.bat.
You have a "new-recovery.img" file.
Boot your device into fastboot:
fastboot flash recovery <path of your new recovery.img>
The solution works, but device security is in danger.
You can use it, or wait for a new twrp.
Click to expand...
Click to collapse
Thanks raz0rfail, it seems that has a solution in this.
three considerations allow me to ask you.
1. firstly, im encouraged to follow your instructions, but im entering a completely new field, Idont know whats android kitchen , how to copy "my twrp file into the folder", and after carrying out this instructions, should I open again xperifix, and launch the rooting process? if so, There is any risk xperfix overwrite the "previous patched" twrp as you told me in the last post?
2. when will the new twrp launch? because the last update on twrp's website was december 2017
3. Storm's xperifix 3.0 it is worth it to wait its release? because maybe waiting one month more, probably my twrp problem could be solved?
I'm confused, but thank you for you reply, at least you give me a little of chance of fix this problem

reckfield said:
Thanks raz0rfail, it seems that has a solution in this.
three considerations allow me to ask you.
1. firstly, im encouraged to follow your instructions, but im entering a completely new field, Idont know whats android kitchen , how to copy "my twrp file into the folder", and after carrying out this instructions, should I open again xperifix, and launch the rooting process? if so, There is any risk xperfix overwrite the "previous patched" twrp as you told me in the last post?
Xperifix will always download the twrp image from his servers, you have to go a little around to use your twrp file, or he updates his img-file on his server.
2. when will the new twrp launch? because the last update on twrp's website was december 2017
Your device twrp has nothing to do with the generic release from twrp. Read the text below your qoute.
3. Storm's xperifix 3.0 it is worth it to wait its release? because maybe waiting one month more, probably my twrp problem could be solved?
I don't know what he will change, but if he always redownload the twrp file from his server, he has to update the img-file.
I'm confused, but thank you for you reply, at least you give me a little of chance of fix this problem
Click to expand...
Click to collapse
OK I will start from scratch with explaining:
TWRP (TeamWin Recovery Project) brought a TWRP version out called 3.2.1 or so, but released twrp version is generic for all android devices.
So some devices have special requirements for a working twrp recovery and a Device Developer patch the generic twrp version to get it working on this device.
It needs time but on many devices it's mandatory.
So i meant in the last thread entry not the generic twrp version from TWRP creator, i meant the modificated version from our device developer which creates our twrp version.
Currently he hasn't released a version which works with the last XZ1 compact firmware 47.1.A.12.205.
And if you use a different twrp which not works on your new firmware, you will get the message $ADB_VENDOR_KEYS is not set or the message adb device is unauthorized.
My tutorial shows you how to modificate your twrp version which you get from Xperifix to get it working with the new firmware.
But if you use my twrp, your device isn't secured as you used a the correct twrp recovery from our device developer.
So you can decide if you want to use the new firmware and magisk and my cam and stay a little unsecure or you wait if the device has created a working twrp for the firmware and xperifix has updated the img-file on his server.
Execution steps for patching your twrp recovery image and get cam and magisk working again on new firmware.
At first download Android Image kitchen from here:
https://forum.xda-developers.com/showthread.php?t=2073775
Download minimal adb and fastboot from here:
https://androidfilehost.com/?fid=962187416754459552
Extract both Zip-Files on a place you want.
Then you have under C:\Xperifix\DATA\TWRP an .img-File called xz1c-twrp.img if Storm didn't change the paths.
Copy this file into the folder where you extracted Android Image Kitchen.
Execute Unpackimg.bat and change parameter in the file as described. Then execute repackimg.bat.
Open cmd.exe with windows-key + r-key. Enter cmd.exe and execute it.
Open the folder where you have extracted minimal adb and fastboot and copy the filepath of it.
switch back to cmd and enter the command cd + your path and press enter.
You should now be inside your folder inside cmd.
Then open the folder where you have extracted android Image Kitchen and right click on the new-recovery.img and in contextmenu click copy path.
switch back to cmd and enter the following command:
fastboot flash recovery and right click and click on insert to insert the image path. But don't execute it!
Next step have to do with Xperiix:
Reboot your phone into fastboot and start executing XperiFix.
if You got the message in XperiFix that the recovery is flashed unplug your phone and boot it again into fastboot.
Now execute the command inside cmd.exe
click up on your keyboard to get the last command inside cmd and replace the word "flash" with "boot" and your phone start booting into correct twrp image.
Now let Xperifix work until it's finished and you should have a working cam and magisk.

Raz0Rfail said:
OK I will start from scratch with explaining:
TWRP (TeamWin Recovery Project) brought a TWRP version out called 3.2.1 or so, but released twrp version is generic for all android devices.
So some devices have special requirements for a working twrp recovery and a Device Developer patch the generic twrp version to get it working on this device.
It needs time but on many devices it's mandatory.
So i meant in the last thread entry not the generic twrp version from TWRP creator, i meant the modificated version from our device developer which creates our twrp version.
Currently he hasn't released a version which works with the last XZ1 compact firmware 47.1.A.12.205.
And if you use a different twrp which not works on your new firmware, you will get the message $ADB_VENDOR_KEYS is not set or the message adb device is unauthorized.
My tutorial shows you how to modificate your twrp version which you get from Xperifix to get it working with the new firmware.
But if you use my twrp, your device isn't secured as you used a the correct twrp recovery from our device developer.
So you can decide if you want to use the new firmware and magisk and my cam and stay a little unsecure or you wait if the device has created a working twrp for the firmware and xperifix has updated the img-file on his server.
Execution steps for patching your twrp recovery image and get cam and magisk working again on new firmware.
At first download Android Image kitchen from here:
https://forum.xda-developers.com/showthread.php?t=2073775
Download minimal adb and fastboot from here:
https://androidfilehost.com/?fid=962187416754459552
Extract both Zip-Files on a place you want.
Then you have under C:\Xperifix\DATA\TWRP an .img-File called xz1c-twrp.img if Storm didn't change the paths.
Copy this file into the folder where you extracted Android Image Kitchen.
Execute Unpackimg.bat and change parameter in the file as described. Then execute repackimg.bat.
Open cmd.exe with windows-key + r-key. Enter cmd.exe and execute it.
Open the folder where you have extracted minimal adb and fastboot and copy the filepath of it.
switch back to cmd and enter the command cd + your path and press enter.
You should now be inside your folder inside cmd.
Then open the folder where you have extracted android Image Kitchen and right click on the new-recovery.img and in contextmenu click copy path.
switch back to cmd and enter the following command:
fastboot flash recovery and right click and click on insert to insert the image path. But don't execute it!
Next step have to do with Xperiix:
Reboot your phone into fastboot and start executing XperiFix.
if You got the message in XperiFix that the recovery is flashed unplug your phone and boot it again into fastboot.
Now execute the command inside cmd.exe
click up on your keyboard to get the last command inside cmd and replace the word "flash" with "boot" and your phone start booting into correct twrp image.
Now let Xperifix work until it's finished and you should have a working cam and magisk.
Click to expand...
Click to collapse
the descriptions are absolutely precise to follow and thanks you,
in the folder data, according your description there must be this directory C:\Xperifix\DATA\TWRP an .img-File.
on my xperifix there is not such folder. attach you some images, (I also reinstall xperfix 2.5 ruling out if I lost some folders)
{
"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"
}