Related
Hello,
I cannot managed to use Flashtool on my W7 64bit, cause all drivers I have found are refused
I followed for instance this, but it says there are no 64 bit driver !?
( Hopefully I got an old XP PC )
Can someone help me on that ?
Cheers.
ChefChaudart said:
I followed for instance this, but it says there are no 64 bit driver !?
Click to expand...
Click to collapse
Why on Earth, especially when you're a member of xda, would you look anywhere else.
lollylost100 said:
Quick tutorial for unlocking new Xperia devices. Although there is one on the SE developer website, this thread can be used for users to discuss their problems during unlocking etc.
Warning! This procedure will wipe the /data partition of your phone.
1. Download:
-fastboot package: http://www.multiupload.com/BMJ24IL6XY
-32/64bit drivers: http://www.multiupload.com/0XZV1LXRVA
2. Go to: http://unlockbootloader.sonyericsson.com/instructions
3. At the bottom click 'Continue' and enter your IMEI (type *#06# to find out), name and email address
4. You should now receive your unique unlock key
5. Extract fastboot.rar and open fastboot folder
6. Hold SHIFT and right click on the background of the folder
7. Select 'Open command window here'
8. Connect your phone in fastboot mode (turn phone off, hold menu button and plug in USB Cable)
9. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
10. If a value is returned, it means the phone is correctly connected
11. Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key provided in step 4.
12. You're device should now be bootloader unlocked
If this tutorial is too much for you then itskapil wrote a step-by-step guide (and recorded a video also):
-Instructions: http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/
-Video: http://www.youtube.com/watch?v=LRH3pC7MhEA
Click to expand...
Click to collapse
Very funny
I know this procedure, as I mentioned it myself earlier to someone over here !
If I post a question here, it´s because i did not work for me
( -> Point 1 & 2 )
You said it said there was no x64 driver, I quoted a post that provides one. The problem isn't Windows 7 x64. I assume you've uninstalled the device and started from scratch?
ChefChaudart said:
Very funny
I know this procedure, as I mentioned it myself earlier to someone over here !
If I post a question here, it´s because i did not work for me
( -> Point 1 & 2 )
Click to expand...
Click to collapse
Can you give more details about what didn't work for you? please be specific and give maximum details so we can help you more...
I'm on W7 x64 and it worked for me without any problem at all so i guess it's not a 64 bit driver problem. if you insist i can give you the drivers from my OS, maybe your's corrupt or something.
cheers
Oooh I get an idea
I unchecked "Show only compatible materials", then I was able to see want I wanted and installed it.
I think now it´s ok, but in fact, I have nothing to flash
what does it mean when it says "it will delete the partition"??
Xperia ray fast boot driver
XperienceD said:
Why on Earth, especially when you're a member of xda, would you look anywhere else.
Click to expand...
Click to collapse
The links that you have given to download the drivers don't work they either force you to download ilivid.exe or another zoom downloader. I have tried downloading and installing both but both don't give me the drivers. Something is wrong can you please point me to a decent URL for downloading the 64bit drivers for Windows 7.
ikshf143 said:
The links that you have given to download the drivers don't work they either force you to download ilivid.exe or another zoom downloader. I have tried downloading and installing both but both don't give me the drivers. Something is wrong can you please point me to a decent URL for downloading the 64bit drivers for Windows 7.
Click to expand...
Click to collapse
I installed Flashtool, from Flashtool folder I installed drivers for fastboot and my device and that's all I needed to do.
Not helping much
It's all very well getting all snotty and telling people to use the search, but PLEASE keep your links up to date.
I have a problem with my Arc LT15i and am trying to unlock the boot loader. I have x64 Windows 8 and cannot get Windows to see the phone. ALL of the links I have found on the internet, here, at Sony Ericsson and any other place I have found are ALL dead links or try to foist some crapware on you.
I get the blue light on the phone indicating it is trying to enter Fastboot, but Windows will not see it, it appears as S1 Boot Fastboot in Device Manager, but no driver that I've found will work.
Flashtool may be very good, but it only works if you have an unlocked boot loader (according to Sony Ericsson).
If anyone has a Windows 8 64bit driver I'd really appreciate it if they'd pass on where to get it.
TimKing.ie said:
It's all very well getting all snotty and telling people to use the search, but PLEASE keep your links up to date.
Click to expand...
Click to collapse
XperienceD said:
References:
[TOOL] Fastboot and ADB helper v1.0
[4Noobs] Flashing a Custom Rom & Kernel Using Fastboot
[How-To] Install custom kernel/rom on 2011 xperia device
[HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
How to Flash boot.img / kernel.elf / kernel.sin using flashtool
[TOOL][FASTBOOT] QuikIMG - A frontend for fastboot [0.2 beta]
[Tutorial] How to install CyanogenMod 9.0 on xperia 2011 devices
[TOOL] RecoverX - Recovery installer for almost all android devices
[RECOVERY] TWRP 2.3 for all your Xperias. (downloads + DIY howto)
Fastboot & Flashboot ADB Driver installation on Windows 8 Guide for Sony Xperia Users
How to Install CyanogenMod on your Xperia (bootloader unlock, fastboot, Google Apps, etc.)
Click to expand...
Click to collapse
TimKing.ie said:
If anyone has a Windows 8 64bit driver I'd really appreciate it if they'd pass on where to get it.
Click to expand...
Click to collapse
See above for why you should read the stickys, and if you've not found it by searching, then god knows what you were searching for. - fastboot windows 8 xperia arc
links are not working for drivers
could you please send me the links for s1boot fastboot drivers for xperia mini st15i....
thnx in advance
sumitrohilla1991 said:
could you please send me the links for s1boot fastboot drivers for xperia mini st15i....
thnx in advance
Click to expand...
Click to collapse
Install Flashtool, then look in Flashtool folder (by default C:\Flashtool\drivers) and start and Flashtool-drivers.exe. Choose fastboot drivers.
that is the main problem they are not installing sucessfully...
after installation it shows
Google, Inc. (win USB) install failed
sony ericsson mobile comm. sucesssfull
due to which i'm not being able to unlock my bootloder and also unable to install recovery and custom roms in my xperia mini..
sumitrohilla1991 said:
that is the main problem they are not installing sucessfully...
after installation it shows
Google, Inc. (win USB) install failed
sony ericsson mobile comm. sucesssfull
due to which i'm not being able to unlock my bootloder and also unable to install recovery and custom roms in my xperia mini..
Click to expand...
Click to collapse
Did you run it as administrator?
sumitrohilla1991 said:
that is the main problem they are not installing sucessfully...
after installation it shows
Google, Inc. (win USB) install failed
sony ericsson mobile comm. sucesssfull
due to which i'm not being able to unlock my bootloder and also unable to install recovery and custom roms in my xperia mini..
Click to expand...
Click to collapse
Here they are - mediafire.com/download/rg75cze0aa8yzm7/Adb+%26+Flashtool-drivers.exe
Found here - xperiaray.wordpress.com/2012/10/27/flashing-tool/
solved
www,omniuslogs,net/download,php
change the "," to "." follow th steps and install omnius v3.0.0.1
gd luck
new members cant post links thts y i used th commas
sumitrohilla1991 said:
that is the main problem they are not installing sucessfully...
after installation it shows
Google, Inc. (win USB) install failed
sony ericsson mobile comm. sucesssfull
due to which i'm not being able to unlock my bootloder and also unable to install recovery and custom roms in my xperia mini..
Click to expand...
Click to collapse
I have the same issue, running as admin but drivers won't install!
Symphony W25 device Finally Rooted !
{
"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"
}
All credits go to jason_cheng
Procedure given below:
1. First of all, you need Drivers For your symphony W25 (Smphony.W25/Karbonn.A7/Mobistar.S01/Ktouch.W650 All are the same phone)
Driver for winXP
Get them here (uploaded by prasad12ka4) Or Here uploaded by rainwalker
Click to expand...
Click to collapse
Drivers for Win 7 / Win 8
Get them here
Click to expand...
Click to collapse
64-Bit Win 7 Drivers
Get them here
Click to expand...
Click to collapse
Install them while connecting your phone on "USB debugging mode", and going to "device manager > other devices" on your pc. After installation disconnect the phone.
(I believe some of you are having problems installing the drivers. I recommend you install the drivers on a freshly installed winXP pc. I faced a lot of trouble doing it on my Win8 pc)
2. Download Android software development kit (SDK) from Here and install in pc. Default installation Directory should be C:\Program Files\Android\android-sdk
3. Android SDK may need Java development kit (JDK) installed in pc. If you need jdk, go here or go to their Website to download
3. Download Fastboot From Android Central and keep it inside
C:\Program Files\Android\android-sdk\platform-tools folder
4. Download Clockwork Mod Recovery for w25 from Link #1 or Link #2, unzip and copy to the same folder. replace duplicate (if prompted).
5 hook your phone up with pc in USB debugging mode and go to C:\Program Files\Android\android-sdk\platform-tools folder, Press Shift+right click inside that folder and select "open cmd window here". It opens a cmd window for that folder.
In the cmd window, type
Code:
adb devices
If the driver installations are correct, you'll see your device connected as w650 (as symphony is re-branded from k-touch w650)
6. Disconnect phone from pc and reboot it into the bootloader, by turning it off and holding [vol-up]+[power]
Till screen turns green and says fastboot:recovery ?, Like below
7. Plug your phone into your computer. On cmd window, type:
Code:
fastboot devices
Reply should be "???????????? fastboot" Meanng fastboot detected the device.
8. In the cmd line, type
Code:
fastboot boot recovery-english.img
And that's it. You'll have booted into the custom recovery (cwmr), and from there you can do a full backup, or restore a backup, or wipe the phone. Use vol up/down to navigate through screen and Power to select an item.
9. Use CWMr to backup your ROM. (It will be saved in: "SD card/clockwork mod/backup" on phone.) and reboot. Copy the backup into pc for further use.
Step 8 was to make sure cwmr works on the phone. It's a temporary port of cwmr on your device.
if problem occurs (less likely to occur), let us know in a comment and don't proceed further.
Otherwise, Proceed below for permanent port..
10. Repeat step 6 and 7. Go to C:\Program Files\Android\android-sdk\platform-tools folder and click on recovery.bat file. Click on it and in the next window, Press any key
Permanent port will be completed
reboot phone if not rebooted automatically.
11. To check cwmr, Repeat step 6 but keep pressing the two buttons even if the screen turns green (fastboot). Continue until.....
screen is red (recovery). after that you'll see Clockwork mod recovery page.
You'll need it to restore your original rom if you mess up anything.
12 In CWMr,
a)]Go to Advanced
b) Choose "Wipe dalvik-cache"
c) Now go to "Mounts & Storage"
d) Choose "Format /cache"
e) Shutdown your phone
13. Download and unzip bootrepack from this post (by jason_cheng). Copy the "boot.img" file from "rootrepack" folder and paste to C:\Program Files\Android\android-sdk\platform-tools folder
14. Repeat steps 6 & 7 (green screen)
15. In cmd window type
Code:
fastboot flash boot boot.img
and
Code:
fastboot reboot
see image below if you have any confusion.
16. After the phone is restarted, type in cmd window:
Code:
adb shell id
which should result "uid=0(root) gid=0(root)"
Rooting is now Unofficially completed
17. To verify, Type each line in cmd window, and press enter
Code:
adb shell
Code:
echo "1" > /system/pwned
Code:
cat /system/pwned
If the Reply to the last line is "1", Congrats ! you have root access to your phone!!
Now remove that test file you created just now. Type:
Code:
rm /system/pwned
What now?
18. Install "Superuser" from Play store
It does not come with su binary. For that, Go to this post and download only the attachment. Unzip it and put the files in C:\Program Files\Android\android-sdk\platform-tools folder.
19. Now open cmd window, type each line and enter.
Code:
adb remount
Code:
adb push su /system/xbin/su
Code:
adb shell
Code:
chmod 4755 /system/xbin/su
now open superuser and check for su binary. I don't recommend su update.
20. Install "Busybox free" from Play store (optional)
Rooting Officially Complete.
If you face problems at any step, please let us know in comments. We'll try to help.you out.
Also feel free to try out the IceCream Sandwitch based roms & the upcoming Jelybean rom for Symphony W25 on the second post of this thread.
If any of you come across a new rom for w25. Please do share.
If you come across dead links on my thread, plz let me know by posting comments, or PM me.
If you find this post useful, then plz hit the thanks button and share it with people who have this phone and waiting for root
End of tutorial.
.usefull links:
Karbonn Mobile A5 & A7 (Android 2.3.6)
Link2sd tuorial in bangla: সহজেই বাড়িয়ে নিন অ্যান্ড্রয়েডের ইন্টারনাল মেমোরি
How To Solve Internal Memory Problem(Great Post)
Custom Roms for Symphony W25 / Mobistar s01 / KTouch W650 / Karbonn A7
Custom Roms for Symphony W25 / Mobistar s01 / KTouch W650 / Karbonn A7
Here you'll find Custom ROM For Karbon A7 device. Which might also be campatible for Symphony w25. Read the respective posts/ comments carefully before downloading and installing.
(first of all back up your existing ROM with cwmr before any change you do to it.)
1) ICS ROM v1 for Symphony W25, Created By rainwalker
Click to expand...
Click to collapse
2) ICS ROM v2 for Symphony W25, Created By rainwalker
Click to expand...
Click to collapse
3) MIUI Gingerbread 2.3.7 ROM (update.zip file), moded By rainwalker
Click to expand...
Click to collapse
4) Rooted Stock ROM of Symphony W25 (update.zip file), uploaded By rainwalker
Click to expand...
Click to collapse
5) Stock Google android gingerbread for a7 by meosuper
Click to expand...
Click to collapse
6) ICS Huawei For Karbonn A7 / S01 by meosuper, Uploaded by ItsmezakiR
Click to expand...
Click to collapse
7) Official ICS ROM for Karbonn A7/Symphony W25 Uploaded by The Droid Master
Click to expand...
Click to collapse
8) Walton Primo ROM modified for A7 Uploaded by vinodkbishnoi
Click to expand...
Click to collapse
9) XION ROM FOR A5/A7 Uploaded by deadlyindian
Click to expand...
Click to collapse
10) ICS refresh V3 Uploaded by meosuper
Click to expand...
Click to collapse
11) CyanogenMod 10 (Karbonn A7) Beta Posted by prasad12ka4
Click to expand...
Click to collapse
12) Backstreet MOD™ v4.1.1 created by The Droid Master
Click to expand...
Click to collapse
13) Lithium 7 for Karbonn a7, symphony w25 and Mobiistar s01 Created by rainwalker
Click to expand...
Click to collapse
14) XINIX 8 for Symphony w25 Created by rainwalker (Recommended)
Click to expand...
Click to collapse
15) CyanogenMod 10 rom for W25 [Beta]
Click to expand...
Click to collapse
16) JELLYBEAN rom for W25 [Beta]
Click to expand...
Click to collapse
Maybe is needed to extract the "boot.img" to remove the restrictions on it, and make it rootable... Have you tried with generic "rooters"?
ICS Baseband Versions For Karbonn A7
ICS Baseband Versions For Karbonn A7 (= Symphony W25)
ItsmezakiR said:
1. 591369_8379_WCDMA_V000001
2. 591357_8376_WCDMA_V0005
3. 591352_8376_WCDMA_V0007
4. 591347_8376_WCDMA_V3070
Click to expand...
Click to collapse
ICS Search Key to Power Key (for Symphony W25)
vinodkbishnoi said:
Hi,
Karbonn A7 ICS. Now you can use search key of your A7 as power key.
Follow the procedure...
1. Download 7x27a_kp.kl.zip file and extract it.
2. Open terminal/Command prompt.
3. Connect your phone to PC via USB.
4. Run following commands.
c:/> adb devices
c:/> adb pull /system/usr/keylayout/7x27a_kp.kl
now copy this file on a safe place. So that if anything goes wrong you could be able to restore it.
now open folder where you have extracted the zip file. The extracted file will be of same name as "7x27a_kp.kl"
c:/> adb push <path to file 7x27a_kp.kl> /system/usr/keylayout/
Now reboot your phone. You will be able to use your search key as power key.
Click to expand...
Click to collapse
Change partition size on A7/W25
Part1:
Anil_Sharma said:
To begin with, you need a hex editor, HxD - Freeware Hex Editor is a great editor and it is very small(less than an MB). Then you need a baseband to edit, you need to locate the file named ' appsboot.mbn '.
That file contains the partition tables, remember this tutorial is about editing the partition tables not extending your physical memory.
So, lets get cracking. Open HxD from programs and open the appsboot.mbn file, now press F3 and search for ' cache ' and press F3 until you see something like this
.
As you can see the highlighted section of the picture
,
there are a few repetitions of ' F0 F0 F0 F0 xx ' multiple times, you are concerned with only the first two /system and /cache partitions respectively.
Remember, you don't need to specify the partition size for /data as it is done automatically when you flash the baseband.
Now back to the hex editing part, once you've decided how much space(in MBs only) you wanna allocate to /system and /cache use this link to Convert hex/dec and select the two digits after the F0 F0 F0 F0 like in this pic
and type the hex number for example in the screenshot B4 in hex equals 180 in decimal, which means /system is allocated 180 MB of space and do the same with Cache, I would recommend allocating 10 MB to it as you hardly ever use it. Then flash the baseband like you normally do through Fastboot.
If you have any doubts ask me and I will do my best to clear things to you. Click Thanks if I helped you, doesn't cost anything
Click to expand...
Click to collapse
Part2:
vinodkbishnoi said:
Hi,
I am attaching a file named "appsboot.mbn". This is used to determine partition size on android system.
There are two ways you could use it.
1. Replace appsboot.mbn file in any baseband update BP folder.
2. If you are handy with fastboot commands there is very simple method. Just boot your phone in fastboot mode (green screen mode) and use
following command....
C:\>fastboot flash APPSBL <path to appsboot.mbn>
And you are done.
You will find following changes.
1. Your partition size will be as shown in screenshot.
2. When you run command adb devices you will no more find S01 there, it will be A7
Download file here...
Download
Thanks
Click to expand...
Click to collapse
no one for help??
ahmed.zunaid said:
no one for help??
Click to expand...
Click to collapse
Your phone is the same with mobiistar s01 and karbonn a7, maybe the developer of symphony keep the original cpu clock(1ghz) and s01, a7 was underclocked to 800 to save battery. Now if you want to root.you must install fastboot driver and install cwm recovery for a7 first.then backup your current rom... when done, install rooted rom for s01 and you will have root, but your cpu will be underclocked to 800ghz.
And can you send me the link to download your backup rom??? I need the 1ghz kernel to mod my rom... thanks.
(If install drivers on w7 pc fail, try to use another pc with wXP-32bit).
These phones aren't - or shouldn't be - that difficult to root. I have just rooted an Xplorer W10 from W7 x64 (and reproduced on Linux), and it went without a hitch. Just a number of gotchas to watch out for (from here on I actually refer to W10 and all other models since they are of the same series):
1. Uninstall any kind of driver you have installed. Symphony does not provide drivers for their Android phones, as far as the website is concerned. You get what you pay for, and this is a relatively remote brand, so don't expect much. In fact, don't expect anything at all.
2. Download and run SuperOneClick. Click on the other tab and choose to check for drivers. You should be prompted to install a driver. Do it.
3. Unplug and replug the USB. Go into the ADB folder and shift-right-click, open a command prompt here. Type 'adb devices' and press ENTER. There should be at least one device listed (in the form of an alphanumeric serial).
4. If there is no device listed by ADB, use Linux to root. There is no need to install any driver on Linux, and SuperOneClick is multi-platform. You will need the mono package on Linux instead of .NET.
5. The phone is actually partially rooted. Whether by intention or by mistake, I am not sure. SuperOneClick will warn of this, so just choose to continue with the rooting process.
6. You should now be rooted.
Background:
There is no exotic bootloader locking going on with these phones, as far as I can tell. The manufacturers/vendors are really just trying to capture a certain segment of the market, so I doubt they'd go through extensive efforts to lock you in. Just find any exploit (right now psneuter and zergRush), put them on the phone along with the su and busybox binaries, execute the exploit, and you'll be good to go with the Superuser app.
ok ...
jason_cheng said:
These phones aren't - or shouldn't be - that difficult to root. I have just rooted an Xplorer W10 from W7 x64 (and reproduced on Linux), and it went without a hitch. Just a number of gotchas to watch out for (from here on I actually refer to W10 and all other models since they are of the same series):
1. Uninstall any kind of driver you have installed. Symphony does not provide drivers for their Android phones, as far as the website is concerned. You get what you pay for, and this is a relatively remote brand, so don't expect much. In fact, don't expect anything at all.
2. Download and run SuperOneClick. Click on the other tab and choose to check for drivers. You should be prompted to install a driver. Do it.
3. Unplug and replug the USB. Go into the ADB folder and shift-right-click, open a command prompt here. Type 'adb devices' and press ENTER. There should be at least one device listed (in the form of an alphanumeric serial).
4. If there is no device listed by ADB, use Linux to root. There is no need to install any driver on Linux, and SuperOneClick is multi-platform. You will need the mono package on Linux instead of .NET.
5. The phone is actually partially rooted. Whether by intention or by mistake, I am not sure. SuperOneClick will warn of this, so just choose to continue with the rooting process.
6. You should now be rooted.
Background:
There is no exotic bootloader locking going on with these phones, as far as I can tell. The manufacturers/vendors are really just trying to capture a certain segment of the market, so I doubt they'd go through extensive efforts to lock you in. Just find any exploit (right now psneuter and zergRush), put them on the phone along with the su and busybox binaries, execute the exploit, and you'll be good to go with the Superuser app.
Click to expand...
Click to collapse
I've used SuperOneClick before. In both 7 and XP machines. It gets stuck at "step 7".
Ok i'll try to do it again following your steps. I'll upload the screenshots
thanks for helping btw ...
No use ....
Nope. It didn't work. Hangs at step 7 (Pic Attached). tried on XP and 7.
Drivers install this time. and cmd>adb shell shows attached device, just like you said. but nothing happens after step7: waiting for device
I guess this process in not for me
can you provide link or tell me the process on how to add cwm recovery and backup the stock rom from the phone?
So that I can upload for you guys to check it out.
Note: my phone goes to recovery mode using the same method described in Karbonn Mobile A5 & A7 (Android 2.3.6
I checked.
ahmed.zunaid said:
Nope. It didn't work. Hangs at step 7 (Pic Attached). tried on XP and 7.
Drivers install this time. and cmd>adb shell shows attached device, just like you said. but nothing happens after step7: waiting for device
I guess this process in not for me
can you provide link or tell me the process on how to add cwm recovery and backup the stock rom from the phone?
So that I can upload for you guys to check it out.
Note: my phone goes to recovery mode using the same method described in Karbonn Mobile A5 & A7 (Android 2.3.6
I checked.
Click to expand...
Click to collapse
Unfortunately, CWMR needs to be built for your hardware in order for it to work. I think CWMR for the Karbonn should work without modification if it has the same hardware, so see if you can find info on getting CWMR onto the Karbonn. If the bootloader is really locked then you'll have to find some way to unlock first.
Backup the recovery partition [1] before doing anything, although I cannot verify whether it's the same partition across all phones. If anything goes wrong you will lose the ability to boot into recovery mode, but your phone will work. With a backup of the partition you can just bit-copy and rewrite the partition exactly as it was.
Because you already have the drivers installed using SuperOneClick, you may like to see now if Unlock Root works [2]. Else, go ahead and root the phone using the manual method. First, run the exploit [3]. Tell us how this goes, then we'll continue (basically upload the su binary and optionally the Superuser app). Otherwise we need to see what other exploit works.
[1] http://forum.xda-developers.com/showthread.php?t=1160213
[2] http://lifehacker.com/5873745/unlock-root-roots-nearly-250-android-devices-in-one-click
[3] http://forum.xda-developers.com/showthread.php?t=1296916
Could you please also report back with some files after running the following commands (you will find them prefixed with w25_ from the folder you're running ADB):
Code:
adb shell cat /proc/cpuinfo > w25_cpuinfo.txt
adb shell getprop > w25_propinfo.txt
Thanks. I suspect the W25 does not have the Karbonn A7 hardware. If the Karbonn is a rebranded Mobilstar S01 then it has a Qualcomm ARMv7 processor. The Symphony phones (hypothesis based on the only one phone I have, that is a W10) are rebranded Tinno [1] phones, with MediaTek processors.
My W10 is ARMv6, so it depends on whether the W25 has an SoC based on the latest MTK proc (which is ARMv7) [2]. That is highly unlikely because it (the proc) would be too powerful for the model number. As you may or may not know, binaries are not portable across ARM cores.
The phones do indeed have the same chassis and general specs, but any attempt to port and/or copy files/ROMs must be taken with great care and precautionary steps. There is, of course, no rule that each model must depend on the same manufacturer, but it's better to be safe than sorry.
[1] tinno.com (i'm not allowed to post links, funny, did so in the previous post)
[2] mediatek.com
jason_cheng said:
Could you please also report back with some files after running the following commands (you will find them prefixed with w25_ from the folder you're running ADB):
Code:
adb shell cat /proc/cpuinfo > w25_cpuinfo.txt
adb shell getprop > w25_propinfo.txt
Thanks.
...... ...... ......
Click to expand...
Click to collapse
#1 cpuinfo Attached
#2 Prop info Attached
It says ARMv7 processor. So what should I do now?
[off topic. rooted my friends Xperia arc today. Was very easy, like : DL kernel>click some stuffs>plug out>turn off>press n hold button>plug in>done
they should've made it simple for this one. just sayin .. :/ ]
ahmed.zunaid said:
#1 cpuinfo Attached
#2 Prop info Attached
It says ARMv7 processor. So what should I do now?
[off topic. rooted my friends Xperia arc today. Was very easy, like : DL kernel>click some stuffs>plug out>turn off>press n hold button>plug in>done
they should've made it simple for this one. just sayin .. :/ ]
Click to expand...
Click to collapse
Well, popular devices have more people tinkering with them and hence more results I suppose for budget devices we are on our own. After all, I believe these phones are pretty value for money and the effort to tinker is worth it.
Anyway, my suspicions are wrong. Symphony (or whoever they rely on) hand-pick reference models and do not depend on any particular vendor. The W25 is ARMv7 from Qualcomm, rebranded from K-Touch W650 [1] with modest hardware upgrades, almost similar to the Mobiistar and Karbonn:
Mobiistar Touch S01: Qualcomm MSM7225A
Symphony Xplorer W25: MSM7627A or MSM7625a (but because of 1GHz clock more likely the former) [2]
Either way the differences are minor I presume. Clock speeds are different and on-chip options vary slightly depending on what the manufacturer opts for. So with a bit of work someone could port existing recoveries and ROMs from similar devices. See [2] for a list of such devices in the respective row for MSM7627A.
You can worry about this when you come to recovery. The first hurdle to get through is root, so have you proceeded to run an exploit?
Also, if you haven't done anything, I would suggest doing a factory reset and then backing up the entire ROM simply with the cat command [3]. The homemade unsigned backup may come in handy later as there is no official ROM update.
[1] 123.chinatronic.com/products.php/K-Touch-W650 [replace 123 with www]
[2] en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
[3] android-dls.com/wiki/index.php?title=HOWTO%3a_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
jason_cheng said:
..... Symphony (or whoever they rely on) hand-pick reference models and do not depend on any particular vendor. The W25 is ARMv7 from Qualcomm, rebranded from K-Touch W650 [1] with modest hardware upgrades, almost similar to the Mobiistar and Karbonn:
Mobiistar Touch S01: Qualcomm MSM7225A
Symphony Xplorer W25: MSM7627A or MSM7625a (but because of 1GHz clock more likely the former) [2]
Either way the differences are minor I presume. Clock speeds are different and on-chip options vary slightly depending on what the manufacturer opts for. So with a bit of work someone could port existing recoveries and ROMs from similar devices. See [2] for a list of such devices in the respective row for MSM7627A. ....
Click to expand...
Click to collapse
it says HTC Desire VC T328d, Huawei Ascend C8812 ...
jason_cheng said:
............
You can worry about this when you come to recovery. The first hurdle to get through is root, so have you proceeded to run an exploit?
Also, if you haven't done anything, I would suggest doing a factory reset and then backing up the entire ROM simply with the cat command [3]. The homemade unsigned backup may come in handy later as there is no official ROM update.
[1] 123.chinatronic.com/products.php/K-Touch-W650 [replace 123 with www]
[2] en.wikipedia.org/wiki/Snapdragon_(system_on_chip)
[3] android-dls.com/wiki/index.php?title=HOWTO%3a_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
Click to expand...
Click to collapse
Not sure how to use these commands. It says that the phone needs to be rooted to use these.
I'm trying to install clockworkmod.
meanwhile, If you have time, plz provide a simplified tutorial.
The zergrush in http://forum.xda-developers.com/showthread.php?t=1296916 doesn't download btw
Sorry, yes, that needs root. You must do everything you can to get root on the phone, because whatever you do you must have a backup. For CWMR, you must back up your recovery partition, else if your CWMR image does not happen to be compatible with your device you risk losing recovery mode.
For MTK devices like the W10, there is a method for non-rooted phones to carry out the backup [1], but I'm not sure about Qualcomm. So in the end, root is unavoidable.
1. Just get zergrush binary from the SuperOneClick archive (it is in another folder along with psneuter).
2. Copy the zergrush binary to the ADB folder.
3. Open a cmd window in the ADB folder just as you would normally type adb commands, then:
Code:
adb push zergrush /data/local/tmp/
adb shell chmod 755 /data/local/tmp/zergrush
adb shell /data/local/tmp/zergrush
Report back with the output.
[1] bm-smartphone-reviews.blogspot.com/2012/04/creating-rom-dump-of-your-mt65x3-device.html
jason_cheng said:
1. Just get zergrush binary from the SuperOneClick archive (it is in another folder along with psneuter).
2. Copy the zergrush binary to the ADB folder.
3. Open a cmd window in the ADB folder just as you would normally type adb commands, then:
Code:
adb push zergrush /data/local/tmp/
adb shell chmod 755 /data/local/tmp/zergrush
adb shell /data/local/tmp/zergrush
Report back with the output.
Click to expand...
Click to collapse
Hellions with blue flames !
See The attached pic
I have the same phone It's original model is ktouch w650
i evem tried to use update.zip method but it says sd storage not found
how do i know if my bootloder is unlocked or locked
tried unlock root with driver installed it says failed to aquire root access\
in adb shell it shows $ sign and if i try to get root acess it says acess denied
Oh boy, it looks like the vulnerability has been patched in your version of Android. Either that, or there is some hardware peculiarity (buffer size being reported wrongly - that's also when this zergrush error comes up) which I do not yet know how to deal with. There is another exploit called 'tacoroot' but I do not prefer going that route as it's not as foolproof/universal as zergrush.
Update zips need to be signed. When your recovery tries to verify the signature it fails, as it is not the signature of the manufacturer that made the update.zip.
Have you guys tried ALL the rooting methods posted in the A5/A7 thread? In the meantime I'll take a look at how Qualcomm ROMs can be dumped.
edit: I'm pretty sure your device has a fastboot mode. If so, you can "hot" boot any cwmr image without flashing it using "fastboot boot theimage.img" as far as I can recall. Having fastboot is a blessing (which the MTK devices do not have) so follow the first few pages of the A7 thread.
thanks
thanks for your hard work....
can you tell me how to acess fastboot?
and also when i press and hold vlo up and power button its displayes" Ap fastboot:recovery " and screen becomes green and then if i keep pressing it goes red into recovery mood
but if i let go at green screen it stays that way
and when i pressed vol down+ power key it said im black screen and yello text " ENTRY QPST DOWNLOAD "
shaon121 said:
thanks for your hard work....
can you tell me how to acess fastboot?
and also when i press and hold vlo up and power button its displayes" Ap fastboot:recovery " and screen becomes green and then if i keep pressing it goes red into recovery mood
but if i let go at green screen it stays that way
and when i pressed vol down+ power key it said im black screen and yello text " ENTRY QPST DOWNLOAD "
Click to expand...
Click to collapse
Sorry, the W10 is my first ever experience with Android (I was looking for a cheap way to find out how the stuff works), and as it does not even have a bootloader mode I have no idea about fastboot. I have only been with this phone/Android for about a month, so there's still a lot more to learn.
But as far as I can tell "AP Fastboot" already implies that you are in fastboot mode. You need the fastboot drivers installed on your PC, and then when you are at the green screen the phone will accept fastboot commands. [1]
If you guys manage to do this, what I would suggest is hot-loading a Karbonn A7, Mobiistar S01 or any other potential compatible CWMR image, then immediately making a full ROM backup. You can then upload recovery.img and I'll see if I can port it, and after that boot.img so we can at least get you root adb shell if by then rooting is still a problem.
And btw, if it was not clear in my previous post, rooting using current "standard" methods is not going to work as the latest gingerbread vulnerability (which zergrush exploits and many of the tools use zergrush) has been patched since December 2011. Unfortunately, it looks like the build of 2.3.6 that the W25 has is from a period after that, so zergrush on the W25 is a no-go. If you want to try, just follow the adb steps above which was posted for ahmed.zunaid.
[1] http://www.androidcentral.com/how-i-back-my-stock-unrooted-galaxy-nexus
ok i followed vital and androplus guide to root my z5 premium but i already face trouble
i already read through about the unlock bootloader n i think everything is ok
but
when i did the command boot image, it said command not allowed
i read somewhere that it might be the problem with my device driver and previouly i installed driver for samsung note 5, now i tried to install sony z5 prem drivers but it still said command not allowed
deleted every adb driver etc n i finally got it working
are you writing commands from the directory your files are downloaded in? If the files are in "Downloads" you need to change the directory in command so the files can be found.
Have u checked on the service menu that bootloader unlock is allowed?
Some networks (O2 in the UK is one) lock their phones so they can't unlock the bootloader.
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"
}
Hey guys, so I have been trying to root and install a custom ROM on my MetrobyTmobile Moto G7 power (XT1955-2 Ocean) Pie 9.0 and the latest updates have been installed.
So i finally figured out how to unlock the bootloader with help from Motorola's unlocking website and unusually long string of numbers and letters to enter into their website. Pho ne is unlocked. I had downloaded the latest versions off all these including:
-TWRP 3.3.1-ocean.img
-Copy AB partiotion file zip
-Open_gapps-x86_64-9.0-stock-20200612
-RR-P-v7.0.2-20191103-ocean-Unofficial-signed
-XT1955-5_OCEAN_TMO_9.0_PCOS29.114-134-14_cid21_subsidy-MPCS_RSU_QCOM_regulatory-DEFAULT_CFC.xml
-ADB minimal 1.4.3
(I also made a backup with the Lenovo rescue and smart assistant
I've tried following directions on several write ups of certain custom ROM installs but when i get to CMD line (DOS) I can kind of get ADB to pull up menus, but I can't get any further. I cant find any detailed step by step with info like where do the downloaded folders of the above programs and Rom's go while still in Windows 10. Nor I can find exact write up of what to type in the CMD line (i am not a coder or went to school for any computer programing.
So I have all the unzipped folders above moved into my C:\ drive with the other main o.s. system folders such as Windows, Program files(x86), Programdata, Users, Perflogs.
Please, anyone who can get me pointed in the right direction, especially with the A+B Partitions and how to type this all into the Command Line, I will be very appreciative. Using cracked apks and MicroG and such just isn't how I want to be using my phones potential with.
This is my first time posting here, I usually am on auto mechanic forums so let me know I i missed something or said to much bla bla. LOL
Thanks!
DerekLindvall said:
Hey guys, so I have been trying to root and install a custom ROM on my MetrobyTmobile Moto G7 power (XT1955-2 Ocean) Pie 9.0 and the latest updates have been installed.
So i finally figured out how to unlock the bootloader with help from Motorola's unlocking website and unusually long string of numbers and letters to enter into their website. Pho ne is unlocked. I had downloaded the latest versions off all these including:
-TWRP 3.3.1-ocean.img
-Copy AB partiotion file zip
-Open_gapps-x86_64-9.0-stock-20200612
-RR-P-v7.0.2-20191103-ocean-Unofficial-signed
-XT1955-5_OCEAN_TMO_9.0_PCOS29.114-134-14_cid21_subsidy-MPCS_RSU_QCOM_regulatory-DEFAULT_CFC.xml
-ADB minimal 1.4.3
(I also made a backup with the Lenovo rescue and smart assistant
I've tried following directions on several write ups of certain custom ROM installs but when i get to CMD line (DOS) I can kind of get ADB to pull up menus, but I can't get any further. I cant find any detailed step by step with info like where do the downloaded folders of the above programs and Rom's go while still in Windows 10. Nor I can find exact write up of what to type in the CMD line (i am not a coder or went to school for any computer programing.
So I have all the unzipped folders above moved into my C:\ drive with the other main o.s. system folders such as Windows, Program files(x86), Programdata, Users, Perflogs.
Please, anyone who can get me pointed in the right direction, especially with the A+B Partitions and how to type this all into the Command Line, I will be very appreciative. Using cracked apks and MicroG and such just isn't how I want to be using my phones potential with.
This is my first time posting here, I usually am on auto mechanic forums so let me know I i missed something or said to much bla bla. LOL
Thanks!
Click to expand...
Click to collapse
To make things easy in windows 10 make sure the driver thing is off first.Then make sure you install adb program to the root of your c drive.Then make sure your a b partion zip is in the adb folder.Then go to computer on ur menue to c drive open up adb folder inside the folder u should see a comand prompt icon or go to search typ cmd and it will bring up windo with c:/adb prompt somi liky that then typ fastboot device it should bring up some numbers.And make sure I have USB debug turned on in phone and have phone in bootloader mode by holding power and volume buttons till a screen comes up use volume bootons to scroll throy to u see restart bootloader .then typ fastboot devices again should get some numbers.now if u got the a b partion zip in your adb folder typ fastboot flash a b partion zip .I renamed mine to shorter name like adpart.zip.on Soo machines u need to just typ abpart then it goes sometimes u have to put the .zip after the abpart then should go.google on how to flash the A B partion zip and also get ur twrp IMG in ur adb folder if things go right the partion zip should flashed with no eorrs then typ fastboot boot recovy or what u saved name is then phone boot up to twrp.to make it easier before u get this far u can put in ext sdcard and u can put ur rom of choice on it .u can I stall twrp but sometimes they touch won't work but I can always boot into twrp from the adb comands.i tryed to make it simple but Google all this before doing anything more and get the comands saved in note pad then u can copy and paste.i try to find the link that details all of of this .there is an tellagram group that might b helpful I use them and here to get mine done
roadkill42 said:
To make things easy in windows 10 make sure the driver thing is off first.Then make sure you install adb program to the root of your c drive.Then make sure your a b partion zip is in the adb folder.Then go to computer on ur menue to c drive open up adb folder inside the folder u should see a comand prompt icon or go to search typ cmd and it will bring up windo with c:/adb prompt somi liky that then typ fastboot device it should bring up some numbers.And make sure I have USB debug turned on in phone and have phone in bootloader mode by holding power and volume buttons till a screen comes up use volume bootons to scroll throy to u see restart bootloader .then typ fastboot devices again should get some numbers.now if u got the a b partion zip in your adb folder typ fastboot flash a b partion zip .I renamed mine to shorter name like adpart.zip.on Soo machines u need to just typ abpart then it goes sometimes u have to put the .zip after the abpart then should go.google on how to flash the A B partion zip and also get ur twrp IMG in ur adb folder if things go right the partion zip should flashed with no eorrs then typ fastboot boot recovy or what u saved name is then phone boot up to twrp.to make it easier before u get this far u can put in ext sdcard and u can put ur rom of choice on it .u can I stall twrp but sometimes they touch won't work but I can always boot into twrp from the adb comands.i tryed to make it simple but Google all this before doing anything more and get the comands saved in note pad then u can copy and paste.i try to find the link that details all of of this .there is an tellagram group that might b helpful I use them and here to get mine done
Click to expand...
Click to collapse
You should use paragraphs or anything like that!
WoKoschekk said:
You should use paragraphs or anything like that!
Click to expand...
Click to collapse
Sorry I'm looking for the format that I did
Adb fastboot was a big problem. Use newest platform tools instead. World of difference with them commands...