Related
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
Hello, I got the Huawei 651F watch yesterday (bought from amazon.de) and I wonder which is the latest software version?
I'm running on Android Wear 1.3.0.2421912, Google Play Services 9.4.52, Android OS 5.1.1 . I think there is a new version out (which supports speaker and keyboard), but when I click on "System Update" it says my system is up-to-date!
Any ideas?
Mine is running on Android Wear 1.5.0.xxxxx, Google play services 9.4.52 and Android OS 6.0.1
I've had some trouble to get it updated when I bought it, but it was just a matter of time (I guess until the phone wear app downloaded the wear update)
But, for the keyboard it's only available in Android Wear 2 developer preview...
Thanks for your reply. It seems that I run an older version.
So you just waited until the update? How long?
I don't have to do anything and the watch will update itself? No wi-fi on, no other setting etc?
Make sure watch is fully charged and better put watch on charger when checking for updates and have WiFi enabled
That worked for me...
Thanks for your reply.
Tried it and didn't work for me. It still says system is up to date.
No idea if there is meaning in just waiting. It's an old update right?
Be patient, it will come.
Sent from my Nexus 10 using Tapatalk
Other solution if you don't want to wait is to flash the latest stock version with adb/fastboot
I just wanted to know if there's a meaning in waiting.
In addition after I restart my phone the watch loses the recent contacts list (2 swipes right). How can I get it back?
EDIT: Nevermind, I turned on Bluetooth debugging on the phone only (not in the watch) and restarted the phone and contacts are back. I'm not sure I understand what Bluetooth debugging is or if it had anything to do with it.
I've tried restoring to factory defaults in order to get the 1.5 update with no luck. How can I update from 1.3 to 1.5 manually? Any link would be appreciated.
Here you can find the preview image (android wear 2.0 developer preview) and the original image (named : Non-preview image (for after testing)). Make sure you download Huawei watch image and not the LG one : https://developer.android.com/wear/preview/downloads.html
You'll have to flash the "non-preview image" with adb/fastboot
Still no update, despite checking while charging etc. Is there meaning in waiting?
Could you give me the latest "stable" version, with a detailed guide? I remind you that I have version 1.3, so I need a full version to 1.5, not incremental. Right? I think I need to make changes in the phone too, not only download the version and toolkits.
Don't know why you still don't have the update...
For the latest stable version, it's the one I gave you in my last post. The guide to flash it is detailed under the links. Don't worry, it's a full 1.5 version.
You need to have SDK manager (in order to install and use adb/fastboot), but nothing have to be done on your phone (just unpair the watch) : everything else is done from the charger connected to your computer
Thanks.
I meant the watch, not the phone.
So I download the non preview image? The links you provided are for some version 2.0 of wear, not 1.5?
Yes the non-preview is wear 1.5 : Google give this image as a way to revert back to a stable release after testing the wear 2.0 developer preview. In your case, you can just flash it to manually update to official wear 1.5
Sorry for my persistance but I have no experience with android wear plus flashing a watch. Could you check the versions in the screenshots and tell me if it's ok to proceed?
I have to download and flash the following image?
sturgeon-mec23l-factory-48003078.tgz
MD5: 417b5cbddb29a2262bce133e283d2732
SHA-1: 4800307843580f818557dd7c43d8ba2161e289b2
I believe the guide is missing some instructions, in example it says to download and unzip the image, but it doesn't say copy the file in the watch. Don't I have to download the file in my computer, unzip it there, then transfer it to the root directory of the watch? Or like in the phones, you have to transfer the zip file to the device you want to upgrade?
Thanks again.
No problem, but you'll see that in fact, phone or watch, it's very similar !
Yes, this is the good one to download : sturgeon-mec23l-factory-48003078.tgz
About your screenshots, it's ok : it's not an update, it's a full system image which will wipe everything during install (so you could install it on the top of every wear version). I just read again the guide, there is nothing missing : the "flash-all" script is in fact composed of several "adb" commands which will push and install bootloader, rom, recovery, ... as you would had done with a nexus device (exactly the same process).
I think you was thinking about installing it with TWRP, but it's not a zip file as a custom rom.
So I download the file and unzip it in the watch or in my pc?
Furthermore, I don't undestand the following:
"Confirm installation of the fastboot tool
To flash a device using one of the system images, confirm that you have the fastboot tool in the platform-tools/ directory of the Android SDK. Be sure that you have the latest version of the Android SDK Platform-tools from the SDK Manager.
After you confirm that you have the fastboot tool, add the tool to your PATH environment variable so the tool can be found when you flash the watch."
I've download ANDROID STUDIO 2.1.3, but can't find where the platform-tools/directory is? I clicked on Configure -> SDK Manager and installed Android 7, 6, 5.1, 5. I don't know if it was needed...
The part that you don't understand is about adb/fastboot utility which are needed to push the file and install them on your watch. Anyway, you said that you installed Android Studio (it was not really needed) but adb/fastboot is automaticaly installed with it ! So it's a good point.
First, you'll have to search for your sdk folder. Usually it's located in : "C:\Users\<--user name-->\AppData\Local\Android\sdk". There is inside a folder "platform-tool" which contain among all the files adb.exe and fastboot.exe
Then, unzip the tarball (sturgeon-mec23l-factory-48003078.tgz) in this folder. Then Shift + Right-click in the background of the folder and select "open a command window there" (or something like that, my computer is not in english).
Finaly, follow the guide :
2. Attach the watch charger to the watch and plug the USB cord (from the charger) into your computer.
3. Use the following adb command to confirm that the watch is available for flashing: adb devices
4. Use the following adb command to start the device in fastboot mode: adb reboot bootloader
5. Unlock the device's bootloader. This step erases all data on the device: fastboot oem unlock
On the watch, select the Unlock option.
6. Issue the command: flash-all.bat
7. Optionaly, you can lock again your bootloader by the command: fastboot oem lock
Found it thanks.
Frixx_x said:
The part that you don't understand is about adb/fastboot utility which are needed to push the file and install them on your watch. Anyway, you said that you installed Android Studio (it was not really needed) but adb/fastboot is automaticaly installed with it ! So it's a good point.
First, you'll have to search for your sdk folder. Usually it's located in : "C:\Users\<--user name-->\AppData\Local\Android\sdk". There is inside a folder "platform-tool" which contain among all the files adb.exe and fastboot.exe
Then, unzip the tarball (sturgeon-mec23l-factory-48003078.tgz) in this folder. Then Shift + Right-click in the background of the folder and select "open a command window there" (or something like that, my computer is not in english).
Finaly, follow the guide :
2. Attach the watch charger to the watch and plug the USB cord (from the charger) into your computer.
3. Use the following adb command to confirm that the watch is available for flashing: adb devices
4. Use the following adb command to start the device in fastboot mode: adb reboot bootloader
5. Unlock the device's bootloader. This step erases all data on the device: fastboot oem unlock
On the watch, select the Unlock option.
6. Issue the command: flash-all.bat
7. Optionaly, you can lock again your bootloader by the command: fastboot oem lock
Click to expand...
Click to collapse
Frixx_x thanks a lot mate, I've updated the phone as described. Still the version in the link you gave me is Android Wear 1.4 (6.0.1 Android), not 1.5. If I don't see it updating in the next days is there a way for 1.5?
As i promise to one of member here then i will post it and i have it.
I can't help you with any of problems related do to i don't have S6E+ .
For all with March 4CQB2 baseband update for Nougat. SS-G928AUCS4CQB2-to-U4EQC6-UP - link is UP
MD5 :7a55165ce2b9d3ffe6170491813c44ac
Nougat update if you are on 4CQA1 baseband SS-G928AUCS4CQA1-to-U4EQC6-UP.zip - link is up
MD5 checksum : c74d9106d59dcb0411f9a1e4e23ca797
Make sure you know how to ADB sideload. I'm not responsible for any damage to your phone.
Steps:
0. Make sure you are on G928AUCS4CQA1 or March update G928AUCS4CQB2 Baseband. Check this 3 times
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-G928AUCS4CQA1-to-U4EQC6-UP.zip or after March 20 update SS-G928AUCS4CQB2-to-U4EQC6-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update SS-G928AUCS4CQA1-to-U4EQC6-UP.zip or after March 20 update SS-G928AUCS4CQB2-to-U4EQC6-UP.zip
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-G928AUCS4CQA1-to-U4EQC6-UP.zip or after March 20 update SS-G928AUCS4CQB2-to-U4EQC6-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
Thanks again. Will try it as soon as available.
Please be reminded to upload the qa1 update. I don't think it's available anywhere
vista1984 said:
Thanks again. Will try it as soon as available.
Please be reminded to upload the qa1 update. I don't think it's available anywhere
Click to expand...
Click to collapse
nougat is uploaded i just downloading to check if file is OK after upload.
vista1984 said:
Thanks again. Will try it as soon as available.
Please be reminded to upload the qa1 update. I don't think it's available anywhere
Click to expand...
Click to collapse
Link is UP.. Enjoy !!
norbarb said:
Link is UP.. Enjoy !!
Click to expand...
Click to collapse
Downloading...
could you upload the adb sideload from PJ1 to QA1 please.
vista1984 said:
Downloading...
could you upload the adb sideload from PJ1 to QA1 please.
Click to expand...
Click to collapse
10 min away
updating. will report back later. it's getting late here. so i will probably report back early tomorrow.
Thank you again norbarb for all the hard works to our devices.
norbarb said:
As i promise to one of member here then i will post it and i have it.
I can't help you with any of problems related do to i don't have S6E+ .
Nougat Update Here - link is up
MD5 checksum : 9970ef8f7ba21ea499cd977775f68d88
Make sure you know how to ADB sideload. I'm not responsible for any damage to your phone.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-G928AUCS4CQB2-to-U4EQC5-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-G928AUCS4CQA1-to-U4EQC5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-G928AUCS4CQA1-to-U4EQC5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
Click to expand...
Click to collapse
After 3 updates, I am confirming that the updates work like a charm. 7.0 has lots of new tweaks after first 15 mins use. And stable so far.
Thanks again!!
thanks for share
I am having lots of issue installing this update.
first status 7 error.
Sorted with editing binary file and than signature not verified error and failed on 50% tried again failed on 92% .
Any help?
fysaldar said:
I am having lots of issue installing this update.
first status 7 error.
Sorted with editing binary file and than signature not verified error and failed on 50% tried again failed on 92% .
Any help?
Click to expand...
Click to collapse
Odin back to older avalable version and update gradually. Looks like your recovery is corrupted
Clicking from Edge of Galaxy
norbarb said:
Odin back to older avalable version and update gradually. Looks like your recovery is corrupted
Clicking from Edge of Galaxy
Click to expand...
Click to collapse
Just realised that update is AUCS4CQA1-to-U4EQC. And my build is UCU2BPE6 have you got firmware for this build by chance?
Here is donwload links to all the Odin file. Credit to the member who uploaded it. Which should bring you to pj1 directly
https://forum.xda-developers.com/at...neral/g928a-odin-restore-files-t3214359/page9
fysaldar said:
Just realised that update is AUCS4CQA1-to-U4EQC. And my build is UCU2BPE6 have you got firmware for this build by chance?
Click to expand...
Click to collapse
I can look for it tomorrow. I'm not familiar with S6E+ at all, i just find update because one of the member ask me if i can. I have no idea what is ladest available firmware for your devices. But like i said i can look for it.
Clicking from Edge of Galaxy
Seems edge+ (and probably note 5) got huge upgrade in Android 7 update. Including performance mode which is not available to gs6.
So far I noticed and worth to mention.
Camera UI renewal
Performance mode
New function from nougat, notification panel and night mode
All the Samsung app seems all redesigned
Display render resolution can be changed between 720p, fhd and wqhd
Battery is better especially for standby time
Great job from Samsung this time
norbarb said:
As i promise to one of member here then i will post it and i have it.
I can't help you with any of problems related do to i don't have S6E+ .
Nougat Update Here - link is up
MD5 checksum : 9970ef8f7ba21ea499cd977775f68d88
Make sure you know how to ADB sideload. I'm not responsible for any damage to your phone.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and file is ready for ADB as you download SS-G928AUCS4CQB2-to-U4EQC5-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Norbarb\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-G928AUCS4CQA1-to-U4EQC5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Norbarb\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-G928AUCS4CQA1-to-U4EQC5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Nougat
EDIT: Please post mirrors if you can. Thanks
Click to expand...
Click to collapse
first of all thanks alot.
so my current version is G928AUCS3CPJ1.
will there be any issue if i tried to sideload from this version or should i do the other updates?
if i need to do the other updates,by any chance do you have odin files for this G928AUCS4CQA1 version?
i was on bpe6 and odin to cpj1
rahulje9 said:
first of all thanks alot.
so my current version is G928AUCS3CPJ1.
will there be any issue if i tried to sideload from this version or should i do the other updates?
if i need to do the other updates,by any chance do you have odin files for this G928AUCS4CQA1 version?
i was on bpe6 and odin to cpj1
Click to expand...
Click to collapse
They are here : https://forum.xda-developers.com/att-galaxy-s6-edge-plus/general/g928a-adb-updates-t3575021
norbarb said:
They are here : https://forum.xda-developers.com/att-galaxy-s6-edge-plus/general/g928a-adb-updates-t3575021
Click to expand...
Click to collapse
thanks alot.
all should be sideloaded right?
rahulje9 said:
thanks alot.
all should be sideloaded right?
Click to expand...
Click to collapse
Yes
Hi can please find update to nougat from UCU3CPHA?
Edit: nvm thanks so much norbarb on 7.0 now. 1 odin and 4 sideloads lol
Sent from my SAMSUNG-SM-G928A using Tapatalk
This guide is made based on my experience and based on the other thread: "[Tutorial] Install Windows 10 for ARM32 on your Surface 2".
It is not complete yet. I will be adding files and more clear instructions slowly.
Do this at your own risk. Your device may be bricked. I am still not sure if the SecureBoot fix should be executed on 8.0 or 8.1
# How to Install Windows 10 on the Surface RT #
2020/02/16 kephax
Download complete tools: [will upload]
Download temporary link in attachments
## 0. Restore Windows 8.1
1. Turn the Surface Off
2. Insert this USB stick in the Surface
3. Press Volume Down and Power
4. The Recovery menu will start
5. Troubleshoot > Advanced Options > Command Prompt
6. Type: "restore.cmd" (this will whipe the whole disk, repartition it and install the Windows 8.1 image) (this will take a while)
## 1. Unlock Secure boot ##
1. Run Disable_UAC.reg
2. Start > Regedit > HKEY_LOCAL_MACHINE\BCD00000000" > Select "BCD00000000" > Click on file and select "unload hive"
3. Copy SecureBoot to Desktop > Open it > Run "InstallPolicy.cmd"
4. Restart
5. Start > cmd (as Adminstrator) > PostInstallPolicy.cmd
6. Restart
## 2. Install Windows 10 ##
If you don't have a message "Secure boot" in the bottom right corner then retry step 1
1. Turn the Surface Off
2. Insert this USB stick in the Surface
3. Press Volume Down and Power
4. The Recovery menu will start
5. Troubleshoot > Advanced Options > Command Prompt
6. Type: "script.cmd" (this will whipe the whole disk, repartition it and install the Windows 10 image) (this will take a while)
7. When restarting you will get an error popup: Press SHIFT+F10
8. Type Regedit and go to KEY_Local machine/SYSTEM/Setup/Status/ChildCompletion > setup.exe > Modify the value to "3"
9. Restart
### 2.1. How to activate Windows
1. Powershell
slmgr.vbs /upk
slmgr /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43
slmgr /skms kms.03k.org
slmgr /ato
slmgr /skms zhang.yt
### 2.2 Install runtime
1. Copy APPX1 from Recovery USB to Desktop
2. Desktop\APPX1\APPX1.ps1 > Right click > Run as Administrator
3. Restart
4. Desktop\APPX1\AppxBundle.ps1 > Right click > Run as Administrator
5. Restart
6. Install:
Microsoft.windowsStore.appxbundle
Microsoft.NET.Native.Framework.1.1.appx
Microsoft.NET.Native.Runtime.1.1.appx
## 3. After installation ##
### How to remove Expired version popup ###
1. Go to C:\Windows\System32
2. Right click on LogonUI.exe > Properties > Security > Advanced
3. Ower > Change
4. Enter your username > Check Names
5. Close all dialog boxes
6. Now rename the file to LogonUIbak.exe
### How to change the language to English (and remove chinese) ###
Start > Settings > Time & Language > Region & Language
Remove chinese and set English as Default
### How to install uBlock Origin on Edge ###
1. Download this:
2. Edge > about:flags
3. Select: "Enable extensions developer features"
4. Select the "..." > Extensions > Load Extension
5. Select the folder with uBlock Origin (this should be on the Surface itself)
### How to install UWP applications ###
1. Find your application here:
https://www.microsoft.com/en-us/store/b/home
2. Copy the URL and copy it here:
https://store.rg-adguard.net/7
3. You will need to find here the .appxbundle ARM and sometimes also the dependencies. Sometimes when you download the file it does not have the extension, so rename the file to .appx in the end.
4. Install first the dependencies then the application on the Surface RT
## 4. Pictures
Dumb question......I been reading the other post in regards to installing Windows 10 on the other surface 2..... Would I have to follow this tutorial or the one for the surface 2 if I have a surface 2 running rt? Also it says I need a keyboard..... Does it mean a USB keyboard or can I use my Microsoft soft keyboard?
This will work on rt 8.1 ??
Hey I see you've got a trick to install ublock on edge but the download link is missing, can you give it to us please, it's one of the last things I really need for my tablet to be totally functionnal
I finally managed to install Windows 10 on my Surface RT, and for now it's great! It's a shame that Microsoft didn't update the tablet officially, and that this version is so old that many newer apps don't work, but it's better than nothing!
Some useful informations I learned through the process:
1) Initially I used the recovery image for my language downloaded from Microsoft, and with this image I wasn't able to enable test mode after installing the secure boot policy. I tried the chinese image provided on Yandex (links are in other threads on this forum) and it worked on first try, so use that!
2) Even after enabling Test Mode, if you run the command Confirm-SecureBootUEFI in powershell, it still gives you True as result. I was worried that Secure Boot wasn't really disabled but I was wrong. To confirm that secure boot is disabled you have to enter the command prompt via recovery image and check the right corner of the screen if it says "secure boot is not configured correctly" or something like that. In that case, you can install W10 safely.
3) Some guides are wrong about the file you have to rename to remove the warning about the expiration of the build. The right file is LicensingUI.exe, not LogonUI.exe! LogonUI.exe is responsible for the login interface, if you rename it you won't be able to login on the next reboot, so pay attention!
4) Office 2013 is not activated for me, I tried to install the provided licences many times, but nothing. It seems to work anyway though. There's something I missed?
To be completely satisfied I need:
- a working version of the Crunchyroll app, the one in the store requires a newer build, anyone know how to find it?
- MSN Weather for W10, the one provided is the old W8 app.
- Ad blocker for Edge, someone wrote about sideloading uBlock but didn't share the files.
Does the office 2013 work? I installed it on my Surface RT with the Windows 10 build but it says that it only works on qualifying versions on windows and editing is disabled...
alexenferman said:
Does the office 2013 work? I installed it on my Surface RT with the Windows 10 build but it says that it only works on qualifying versions on windows and editing is disabled...
Click to expand...
Click to collapse
I was able to install it and getting working 100%...... there's another tread that's for installing windows 10 on surface 2 tablet and there's a link in the OP for a mega folder that contains the office 360 files and in it a file that edits the registry
Hello. I can also confirm that it works. I have installed Win 10RT and very happy with it. It really brings a lot of new experience to our tablet as same as a bit faster response.
If you want to use an adblock for Edge, the only one that works is Adblock, directly from the Store. However, adblock support in this build of Edge is very buggy, it eats a lot of ram (sometimes leading to crashes) and some sites fail to load with adblock enabled. So I suggest to install it and to manually acrivate/deactivate it when needed.
Speaking of the Store, I found a bug, at least for me: the install button works only for the apps you already own. So, if you want to install an app you never downloaded, you have to acquire it first on another PC and then on the Surface RT.
Does someone know how to make the the newer Microsoft store (Provided by @_CNR_)to work?
I installed it but however, it won't install any app because of a licence problem probably...
(The older store worked but it does not include all of the apps for example myTube)
If everything goes wrong can I just download a recovery image for 8.1 and install it again?
Winroque said:
If everything goes wrong can I just download a recovery image for 8.1 and install it again?
Click to expand...
Click to collapse
If everything goes wrong. Just boot from the recovery USB stick and reimage the Windows 8.1 using the same dism apply image method.
Does someone have the uBlock archive? There's no link in the OP
nar001 said:
Does someone have the uBlock archive? There's no link in the OP
Click to expand...
Click to collapse
There you go! https://drive.google.com/open?id=18pyeDlRMpB0jF_36DJqdhF_Ybmy0eeRD
If you want to sideload more apps manually you can check my application I made recently: https://forum.xda-developers.com/windows-8-rt/rt-general/arm-rt-app-store-windows-10-rt-t4067813
Ok so I'm attempting to follow this tutorial and the other one for my original surface rt. Where is the wim for windows 10? Those instructions don't seem clear to me, or am I supposed to use the surface 2 image?
kmccmk9 said:
Ok so I'm attempting to follow this tutorial and the other one for my original surface rt. Where is the wim for windows 10? Those instructions don't seem clear to me, or am I supposed to use the surface 2 image?
Click to expand...
Click to collapse
The wim is in that folder https://yadi.sk/d/mnCUeGKWm1XTXA
nar001 said:
The wim is in that folder https://yadi.sk/d/mnCUeGKWm1XTXA
Click to expand...
Click to collapse
Ok I see. I ran into a different issue. I went to do the Windows 10 install today but to my surprise, I couldn't boot up. Luckily I still had my Windows 8.1 Full Recovery USB. But, for for some reason from the advanced troubleshooter, it tells me my USB device is invalid. Has anyone run into this before?
Can be updated to Windows 10 version 1909?
AmznUser444 Dev said:
Can be updated to Windows 10 version 1909?
Click to expand...
Click to collapse
Of course not, the only build of ARM32 Windows 10 we have is this one, and it's leaked.
Wow, really cool!
I would like to know if the cameras work in windows 10? Thanks so much!
Updated with more compatible adb link!
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then follow the guide to install adb https://www.xda-developers.com/install-adb-windows-macos-linux/
7. Follow the XDA adb install guide and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"
Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?
shadi90 said:
Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?
Click to expand...
Click to collapse
This is for US Fold 3 models f926U/1. Sorry brotha. Basically you need to change the beta file you downloaded to this http://fota-secure-dn.ospserver.net...48:16&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA== as well as flash AUJ7 firmware first. I hear UK with CSC BTE works fine. Get it at https://samfw.com/firmware/SM-F926B/BTE/F926BXXU1AUJ7 . After you replaced those files, just follow the instructions again
Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.
Haven't logged in to XDA in years. Just wanted to say THANK YOU.
mha1021 said:
Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.
Click to expand...
Click to collapse
Don't rename the file.
What I always do with adb related stuff is put it in the root of my C drive. So it would be
Code:
C:\adb\platform-tools\
Then put the .bin file in here as well.
After that open cmd and do
Code:
cd C:\adb\platform-tools\
and hit enter.
After that do adb sideload 94 and hit tab so it should autofill the name of the update file.
Let me know if you have any questions.
Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!
AlexMartin00 said:
Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!
Click to expand...
Click to collapse
The baseband is just something that gets updated, so ZUJH is the Android 12 beta firmware. Every time you update your firmware the baseband gets updated as well.
More technical: Baseband is firmware that controls all radio devices on the phone, including GPS, Wi-Fi, Bluetooth, NFC, cellular data, and more.
Will this work on att Galaxy fold 3 since I can't get update cause att blocks it.
Hero_is_Over said:
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then download the "15 Second ADB Installer" HERE
7. Install the 15 second adb installer and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"
Click to expand...
Click to collapse
hi I'm getting a status 1 error with my sideload
erneyone said:
hi I'm getting a status 1 error with my sideload
Click to expand...
Click to collapse
What does the error say?
I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop
zimgir124 said:
What does the error say?
Click to expand...
Click to collapse
Status 1
Is there a mirror for the beta download anywhere? It looks like the link isn't working for me.
ElGuyarc said:
I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop
Click to expand...
Click to collapse
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Dick_Stickitinski said:
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
thank you so much...
I updated my SM-F926U1 with the Beta 4 its really buggy for me
Just want to get my facts straight. Can I just flash back to non-beta ?
What will happen to my Beta status will I still be able to OTA update when the next beta comes out ?
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
Is it a good idea to wipe my data when doing an downgrade like this ?
Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
I thought you can't flash a previous version of Android once you're on the higher version?