As we are lacking other sections like Q/A forum, General forum, so I created this thread which will be a all in one general thread. So now onwards don't create a thread for your problem, help or advice instead post within this thread.
Only we are supposed to keep our forum clean and tidy.
Let the discussions begin! :silly:
Recovery mode not working
Hi all,
I have a question about recovery mode. Here is the whole history step by step, that also might help new people:
Yesterday, I rooted my Samsung Galaxy GT-I8160L. The successful procedure used was the one described here.
Then I wanted to do a backup using Clockworkmod (known as CWM) method, so I downloaded and installed the kernel I8160XXLD8 with CWM recovery support, also successfully, because I read somewhere that there is no way to install CWM with other method for this phone, was it right? This is the link.
To here, everything so far, so good. Now I wanted to install a custom ROM, and I know I did something wrong because path problems started to appear, mainly no /cache directory found, and then doing the Odin procedure for a factory ROM, I think I messed it up even more deeply: now the phone can not enter to recovery mode. But the download mode works, using Odin mode, and even the flash count is working.
From there, I started reading and trying things, but nothing worked: flashing the original ROM, using Samsung KIES to restore factory settings... flashing the rom, from an original one to a modified, nothing happens more than the counter to add one each time; KIES goes to the firmware emergency procedure, downloads something but only one time advices me to remove the battery, and at last nothing happened.
Also tried adb tools from command line, and the tool recognises the phone. When I issue: ./adb devices, the only attached device ID is shown, but when I issue some shell comand, like: ./adb shell "ls", the following error is shown: exec '/system/bin/sh' failed: I/O error (5)
Any advices? I think there is something related with the system partition. Maybe in one of those desperate tries I did check the re-partition checkbox in Odin and messed it up.
I'm writing my question here hoping this is the rigth place :laugh:
---------- Post added at 06:45 PM ---------- Previous post was at 06:11 PM ----------
munrolazar said:
Hi all,
I have a question about recovery mode. Here is the whole history step by step, that also might help new people:
Yesterday, I rooted my Samsung Galaxy GT-I8160L. The successful procedure used was the one described here.
Then I wanted to do a backup using Clockworkmod (known as CWM) method, so I downloaded and installed the kernel I8160XXLD8 with CWM recovery support, also successfully, because I read somewhere that there is no way to install CWM with other method for this phone, was it right? This is the link.
To here, everything so far, so good. Now I wanted to install a custom ROM, and I know I did something wrong because path problems started to appear, mainly no /cache directory found, and then doing the Odin procedure for a factory ROM, I think I messed it up even more deeply: now the phone can not enter to recovery mode. But the download mode works, using Odin mode, and even the flash count is working.
From there, I started reading and trying things, but nothing worked: flashing the original ROM, using Samsung KIES to restore factory settings... flashing the rom, from an original one to a modified, nothing happens more than the counter to add one each time; KIES goes to the firmware emergency procedure, downloads something but only one time advices me to remove the battery, and at last nothing happened.
Also tried adb tools from command line, and the tool recognises the phone. When I issue: ./adb devices, the only attached device ID is shown, but when I issue some shell comand, like: ./adb shell "ls", the following error is shown: exec '/system/bin/sh' failed: I/O error (5)
Any advices? I think there is something related with the system partition. Maybe in one of those desperate tries I did check the re-partition checkbox in Odin and messed it up.
I'm writing my question here hoping this is the rigth place :laugh:
Click to expand...
Click to collapse
Seems to be that in my desperation I kept pressed vol up + home + power, so it never entered the mode. I just released the power button once the phone vibrates and now enters recovery mode as explained here. Now I think the errors are clear. The following error messages are shown below the CWM-based Recovery:
E:failed to open /etc/recovery.fstab (I/O error)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
This error messages keep showing. For example, if I try to do a backup restore from the external sd card, I choose backup and restore menu, and then Backup, this is what is shown:
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
What can I do?
.Thanks
Samsung Galaxy Ace 2 I-8160L default ROM with PIT file download
I solved the problem myself. But I'm going to describe the steps of what I did ok, what crashed everything and how I solved.
Smart Phone Model: Samsung Galaxy Ace 2 I-8160L
How to root it http://forum.xda-developers.com/showpost.php?p=27610432&postcount=31
Add Clockworkmod (also known as CWM) to recovery mode to create backups http://forum.xda-developers.com/showthread.php?p=30792392#post30792392
What I did wrong
Now I wanted to install a custom ROM, and I know I did something wrong because path problems started to appear, mainly no /cache directory found, and then doing the Odin procedure for a factory ROM, I think I messed it up even more deeply: now the phone can not enter to recovery mode. But the download mode works, using Odin mode, and even the flash count is working.
From there, I started reading and trying things, but nothing worked: flashing the original ROM, using Samsung KIES to restore factory settings... flashing the rom, from an original one to a modified, nothing happens more than the counter to add one each time; KIES goes to the firmware emergency procedure, downloads something but only one time advices me to remove the battery, and at last nothing happened.
Also tried adb tools from command line, and the tool recognises the phone. When I issue: ./adb devices, the only attached device ID is shown, but when I issue some shell comand, like: ./adb shell "ls", the following error is shown: exec '/system/bin/sh' failed: I/O error (5)
Seems to be that in my desperation I kept pressed vol up + home + power, so it never entered the mode. I just released the power button once the phone vibrates and now enters recovery mode as explained here. Now I think the errors are clear. The following error messages are shown below the CWM-based Recovery:
E:failed to open /etc/recovery.fstab (I/O error)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
This error messages keep showing. For example, if I try to do a backup restore from the external sd card, I choose backup and restore menu, and then Backup, this is what is shown:
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
How to fix it
Well, this might be just one way to fix it. I downloaded a lot of firmware files from SamMobile (nice guys, by te way) but none of these worked.
A very nice guy posted a very useful backup of the I-8160L that can be downloaded from here (this is the forum entry in spanish). This download is worth the time, and even the subscription to the site because it contains:
CODE_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY_LH1_4G.tar.md5
CSC_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY-CSC-MULTI-UUB_LH1_4G.tar.md5
GT-I8160L_LA_UB_4G.pit
Odin3_v1.84.exe
Odin3.ini
Click to expand...
Click to collapse
Yes! This file contains the PIT file for the Samsung Galaxy Ace 2 I-8160L. But Wait! Do not install it yet. I'm not an expert in root development, but I used to fail installing the original ROM. I flashed my phone again with this file in the PDA field:
CODE_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY_LH1_4G.tar.md5
Click to expand...
Click to collapse
Of ODIN and it worked! No PIT file needed!
======
Resolví el problema solo. Pero voy a describir los pasos de lo que hice bien, lo que dañó todo y cómo lo resolví.
Modelo del Smart Phone: Samsung Galaxy Ace 2 I-8160L
Cómo hacerle el proceso de Root (en inglés) http://forum.xda-developers.com/showpost.php?p=27610432&postcount=31
Agregar Clockworkmod (también conocido como CWM) en modo Recovery para crear copias de seguridad (en inglés) http://forum.xda-developers.com/showthread.php?p=30792392#post30792392
¿Qué hice mal?
Quise instalar un ROM personalizado, y sé que hice algo mal porque los problemas de rutas de archivo empezaron a aparecer, principalmente con el error "no /cache directory found", y luego haciendo el procedimiento con una ROM de fábrica desde Odin, pienso que eso dañó todo más profundamente: ahora el teléfono ni siquiera podía entrar en modo de recuperación. Pero el modo de descarga funcionaba, con el modo Odin, e incluso el contador de flash seguía operando.
Desde ahí, empecé a leer y probar cosas, pero nada funcionó: hacer el flash de la ROM original, usar Samsung Kies para restaurar las condiciones de fábrica... nada funcionaba, y el contador seguía corriendo; Kies fallaba cada vez, llegaba hasta el procedimiento de firmware de emergencia, descargaba algo, pero luego se cerraba.
Incluso intenté con las herramientas de adb tools desde la línea de comando, en la cual el teléfono era reconocido, con el comando ./adb devices. Cuando intentaba hacer un shell al teléfono, se mostraba el error: exec '/system/bin/sh' failed: I/O error (5)
Parece que en mi desesperación mantuve presionado volúmen arriba + botón home + botón encendido, así que nunca entraba al modo que quería. Una vez uno siente que el teléfono vibra, suelta el botón de encendido y entra al modo de recuperación como se explica aquí. Ahora creo que el error es claro. Estos son los mensajes que aparecen abajo de la consola de recuperación basada en CWM:
E:failed to open /etc/recovery.fstab (I/O error)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
Estos errores se muestran cada vez. Por ejemplo, si intento hacer restauración de un backup desde una tarjeta SD externa, escojo el menú "backup and restore", y luego "Backup" y esto es lo que sale:
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard
E:unknown volume for path [/cache/recovery/log]
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:Unknown volume for path [/cache/recovery/last_log]
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:Unknown volume for path [/cache/recovery/command]
Click to expand...
Click to collapse
Cómo lo arreglé
Bien, este puede ser solo una manera de arreglar el problema. Descargué muchos archivos de firmware de SamMobile (unos chicos muy organizados, por cierto) pero nada de esto funcionó.
Un muchacho muy generoso subió un backup muy útil del I-8160L que puede ser descargado desde aquí (esta es la URL del hilo del foro). Esta descarga vale la pena, incluso la subscripción al sitio, ya que contiene:
CODE_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY_LH1_4G.tar.md5
CSC_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY-CSC-MULTI-UUB_LH1_4G.tar.md5
GT-I8160L_LA_UB_4G.pit
Odin3_v1.84.exe
Odin3.ini
Click to expand...
Click to collapse
¡Sí! Este archivo tiene el archifamoso y archi buscado archivo PIT para el Samsung Galaxy Ace 2 I-8160L. ¡Pero espera! No lo instales todavía. Aunque yo no sea un experto en hacer ROOT ni en los MOD ROM de Android, hice el procedimiento flash de nuevo, utilizando el campo PDA de Odin con el siguiente archivo:
CODE_GT-I8160L_I8160LUBLH1_CL1180407_REV00_user_SEC_KEY_LH1_4G.tar.md5
Click to expand...
Click to collapse
¡Y funcionó! Sin necesidad de usar el archivo PIT.
custom ROM definition?
Hi,
I'm new to Android and semi-experienced at modding in general, I just wanted someone to clarify, what qualifies as a "custom ROM"? I've been picking up info here and there on the forums and as far as I can tell flashing a stock ROM does not increase the counter when flashed using the correct procedure (as I have seen since I'm using a pre-rooted stock), but will flashing something like the "stock lite" ROM increase the counter? Or does these kind of modifications to a ROM not make it custom? As I understand it as long as the kernel remains in its original state any modification to a ROM still qualifies it as a stock ROM, is this information correct?
hi
i have mu galaxy ace 2 simlock i want to unlock it.
please help?
@xenex1
yep, every rom that you flash with odin and have custom kernel.bin in it will increase the counter. so flashing prerooted roms (stock lite included) will not change the counter. also when you have rooted phone, you can flash kernel.bin by dd command through adb or directly from the phone without increasing the counter. so.. you can root the phone, flash (by dd) custom kernel with cwm/twrp recovery and then you're free to install any ROM 'cause flashing through recovery don't increase the counter (even when rom has a custom kernel).
damn, that was long..
@kira95
samsung phones don't have locked boot loaders so there's no need to UNLOCK it.
if you mean ROOT, then there are two options:
- flash prerooted rom through ODIN (doesn't increase the counter),
- flash custom kernel through ODIN (changes the counter and flash status).
and i just wanna say.. HAPPY NEW YEAR TO ALL!!!
5:30 AM, gotta go to bed
@up
Yes, you must be very tired, kira wrote about simlock...
Wysyłane z mojego GT-I8160 za pomocą Tapatalk 2
I have a problem. I edited framework.jar and after I put it in /system/framework/ the phone does not start (it stuck on Samsung Galaxy Ace 2 first screen) and if I close the phone, it reboot itself.
At first, I thought I did something wrong when I edited framework.jar, but then I tried only with framework.jar deodexed (without modification) and the same thing happend.
I tried to put android.policy.jar deodex in /system/framework/ and again the phone is stuck on Samsung Galaxy Ace 2 screen.
What is the problem with deodex files in /system/framework/? In /system/app I have bought deodex and odex files and there is no problem.
I wiped the cache partition and dalvik cache before I flash the update.zip that contains framework.jar (before restart in recovery I deleted framework.odex).
Update: I deodexted all file in /system/framework/ and a flash them in CWM Recovery ( before restart in recovery I deleted all .odex files from framework folder). The result is that the phone restart after the second Samsung screen.
Aflter I reflash odex files, I had to reenter samsung account.
Sorry for my english
don't mix odex files with deodexed ones. use only one 'type'.
@up up
oh, that occured to me also.. when i turned off my pc
simlock:
don't have a clue
@WiCiO_MeDi
Thanks for clarifying, seems i've hit on a problem while flashing a custom kernel though, I tried to use the dd comands in the terminal and all looked well up until the reboot now my device is stuck on the screen that displays the phone and model.
I was using the pre-rooted stock ROM using this method here http://forum.xda-developers.com/showthread.php?t=1881964, which worked fine.
Then I tried to get adventurous and tried to add this kernel to the mix http://forum.xda-developers.com/showthread.php?t=1962100.
Any suggestions for this confused noob?
Sorry nevermind the above, the answer on how to fix the issue was quite simple, just re-flash the original ROM, I must have messed up the recovery mode when installing the kernel.
you mean the bootanimation?
try again 'cause it works for others then it should work for you.
write down all steps that you did, maybe you've mistyped something or just did something wrong
Yeah you're right, I must have done something stupid the first time round, works now though cheers.
Sent from my GT-I8160 using xda app-developers app
Hi everyone, i have one question regarding the fisplay turn off animation. Where are located those files and hiw ti change them?
Sent from my GT-I8160 using xda app-developers app
hello,
my question is : Can i put a om of GT-I8160 in my GT-I8160P or i can brick my mobie phone?
i have the nfc mobile phone can you put here a link of roms to this mobile GT-I8160P.
and finally i want to whrere i can find a post of how do a rom ??
@sersik
Firstly, yes there is always a chance of bricking a phone when flashing any ROM.
As for your NFC enabled device if all goes well it should work fine but you will lose the NFC functionality unless you flash with the proper ROM for that hardware.
You can get your stock ROM from this site if someone has uploaded it (signup is required to download).
And use this threads instructions to build a pre-rooted ROM that doesn't increase the counter.
Hope this helps.
thanks to you xenex1
but if i put a rom of GT-I8160 in my GT-I8160P is the same risk of pu a rom of GT-I8160 in a GT-I8160, no??
and in the roms i say a rom that is created by another person
thanks
Yes the ROM for the GT-I8160 will work on the GT-I8160P but you will lose the NFC function since the GT-I8160 does not have it.
Also yes you can use a ROM that was created by someone else, if it is a pre-rooted ROM then simple flash it using ODIN (counter does not increase) but if it is a custom ROM then flashing with ODIN WILL increase the counter, and in turn you will lose your warranty on the device.
If you want to install a custom ROM without increasing the counter you must first use a pre-rooted stock ROM then install the custom ROM using either CWM, TWRP, Through Terminal or ADB.
OTAVALO said:
Hi everyone, i have one question regarding the fisplay turn off animation. Where are located those files and hiw ti change them?
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
They are found inside framework-res.apk. But you have to decompile it first. By the way, why do you want to change it? Do you have the default animation or the CRT animation?
Sent from my GT-I8160 running Holo Bean Beta
I've been having a weird problem lately. After booting up my Ace 2 all my apps force closes, including system apps.
This happened after I installed Suppresed ROM and rebooted. After that I returned to stock ROM rooted with SuperSU, and it happened again. After that I changed to SuperUser and it works fine after a while but if I install some "risky" software, such as BusyBox Installer, it seems to happen again, I made a CWM backup everyday just in case this happened again. It happened to me almost 5 times already.
Just wondering, are any of you having a similiar problem?
Just now I installed Jelly Cream and it won't mount anything on boot and recovery. I hope a quick flash will fix this or Lord help me.. -___-"
uchihakurtz said:
I've been having a weird problem lately. After booting up my Ace 2 all my apps force closes, including system apps.
This happened after I installed Suppresed ROM and rebooted. After that I returned to stock ROM rooted with SuperSU, and it happened again. After that I changed to SuperUser and it works fine after a while but if I install some "risky" software, such as BusyBox Installer, it seems to happen again, I made a CWM backup everyday just in case this happened again. It happened to me almost 5 times already.
Just wondering, are any of you having a similiar problem?
Just now I installed Jelly Cream and it won't mount anything on boot and recovery. I hope a quick flash will fix this or Lord help me.. -___-"
Click to expand...
Click to collapse
the problem is in the firmware i think , so new firmwares doesnt have that problem
Settings
About watch
Build number
Click on the build number
Developer options enabled
Back
System
Developer options
OEM unlocking
USB debugging
Open Minimal ADB and Fastboot folder
Paste the boot.img and vbmeta.img files inside the Minimal ADB and Fastboot folder
Zeblaze Thor 6 V1.3 ROOT
Thor 6 root.zip
drive.google.com
Zeblaze Thor 6 V1.4 ROOT
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Minimal ADB Fastboot v1.4.3
Minimal ADB Fastboot v1.4.3
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Open Minimal ADB and Fastboot
commands
adb reboot bootloader
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
You can open Magisk.
Note: The watch will be reset after the procedure. Please don't forget to take your backups.
how to root thor 5 pro ? :/ was looking so bad for that , i have the rom but can't patch the boot with magisk on the watch , any solution ?
mhd 12 said:
how to root thor 5 pro ? :/ was looking so bad for that , i have the rom but can't patch the boot with magisk on the watch , any solution ?
Click to expand...
Click to collapse
Every setup poses a problem. I need to have the watch to know how to overcome problems. I do not have Zeblaze Thor 5 pro. So I can't say anything for sure. Share the stock rom please. Your watch can be hard brick. What solutions have you tried?
AYALTUN said:
Every setup poses a problem. I need to have the watch to know how to overcome problems. I do not have Zeblaze Thor 5 pro. So I can't say anything for sure. Share the stock rom please. Your watch can be hard brick. What solutions have you tried?
Click to expand...
Click to collapse
no no the watch is working fine except there isn't a patched img of boot i found , i got the stock rom and everything , installed magisk on the watch tried to patch the boot img but i couldn't because the file manager will not detect any file in img format.. so i was kind of stuck how to find a patched boot img to flash
mhd 12 said:
no no the watch is working fine except there isn't a patched img of boot i found , i got the stock rom and everything , installed magisk on the watch tried to patch the boot img but i couldn't because the file manager will not detect any file in img format.. so i was kind of stuck how to find a patched boot img to flash
Click to expand...
Click to collapse
Use your phone to patch boot.img. You do not need to use your watch for this process. After getting the patched boot.img install it on your watch with fastboot. If you still have problems, upload the boot.img file. I will not patch the boot.img file for you.
AYALTUN said:
Use your phone to patch boot.img. You do not need to use your watch for this process. After getting the patched boot.img install it on your watch with fastboot. If you still have problems, upload the boot.img file. I will not patch the boot.img file for you.
Click to expand...
Click to collapse
Hocam selamlar,
Daha önce Türkçe yorumlarınızı gördüm ve sanırım Türksünüz. Zeblaze Thor 6 almayı düşünüyorum fakat çok kararsızım çünkü Zeblaze markası kafamı kurcalıyor. Saat hakkında neler söyleyebilirsiniz, almalı mıyım?
tunaykr said:
Hocam selamlar,
Daha önce Türkçe yorumlarınızı gördüm ve sanırım Türksünüz. Zeblaze Thor 6 almayı düşünüyorum fakat çok kararsızım çünkü Zeblaze markası kafamı kurcalıyor. Saat hakkında neler söyleyebilirsiniz, almalı mıyım?
Click to expand...
Click to collapse
Öncelikle bu saat aslında bir akıllı telefon. Saat görünümlü bir telefon diyebiliriz. Yani bu saati bluetooth ile telefona sekronize edeyim kullanayım diyorsam bu bir hata olur. Çünkü bu şekilde şarjı en fazla 3 gün gider. 15-30 gün şarının gitmesini bekleme. Bu saaati alacaksan eğer ona bir hat takacaksın ve telefonun gibi 2 günde bir şarj edeceksin. Bunu bir akıllı saat yada bileklik gibi düşünme. İnternette yeteri kadar tanıtım videosu izlediğini ve özelleklerini bildiğine eminim. Bu yüzden sana saatin özellikleri ve tanıtımını yapmayacağım. Ama internetteki ürün inceleme videolarında bulamayacağın bazı durumları anlatayım. Senin için böylesi daha iyi olur. Öncelikle Zeblaze markası kalite olarak fena değil. Zeblaze Thor 6'ya gelecek olursak, daha önce Zeblaze Thor 3G kullandım. Zeblaze Thor 6 ekran parlaklığı biraz düşük. Zeblaze Thor 3G bu konuda çok iyiydi. Zeblaze Thor 6 biraz büyük bir saat ve biraz kaba vede su geçiriyor. Kameraları iyi değil. Olumsuz özellikleri bunlar. Performans ve diğer özellikleri bakımından gayet iyi. Android olmayan akıllı saatler, Zeblaze Thor 6 yanında oyuncak gibi kalıyor. Zeblaze Thor 3G'yi ilk aldığımda görenlerin ağzı açık kalıyordu.
AYALTUN said:
Öncelikle bu saat aslında bir akıllı telefon. Saat görünümlü bir telefon diyebiliriz. Yani bu saati bluetooth ile telefona sekronize edeyim kullanayım diyorsam bu bir hata olur. Çünkü bu şekilde şarjı en fazla 3 gün gider. 15-30 gün şarının gitmesini bekleme. Bu saaati alacaksan eğer ona bir hat takacaksın ve telefonun gibi 2 günde bir şarj edeceksin. Bunu bir akıllı saat yada bileklik gibi düşünme. İnternette yeteri kadar tanıtım videosu izlediğini ve özelleklerini bildiğine eminim. Bu yüzden sana saatin özellikleri ve tanıtımını yapmayacağım. Ama internetteki ürün inceleme videolarında bulamayacağın bazı durumları anlatayım. Senin için böylesi daha iyi olur. Öncelikle Zeblaze markası kalite olarak fena değil. Zeblaze Thor 6'ya gelecek olursak, daha önce Zeblaze Thor 3G kullandım. Zeblaze Thor 6 ekran parlaklığı biraz düşük. Zeblaze Thor 3G bu konuda çok iyiydi. Zeblaze Thor 6 biraz büyük bir saat ve biraz kaba vede su geçiriyor. Kameraları iyi değil. Olumsuz özellikleri bunlar. Performans ve diğer özellikleri bakımından gayet iyi. Android olmayan akıllı saatler, Zeblaze Thor 6 yanında oyuncak gibi kalıyor. Zeblaze Thor 3G'yi ilk aldığımda görenlerin ağzı açık kalıyordu.
Click to expand...
Click to collapse
Çok teşekkür ederim. Aklımda takılan birkaç ufak soru işareti var. Birisi şarjı tabii ki de. Normal kullanımda 2 gün dayanıyorsa çok iyi. Bir diğeri de yağmurlu havada vs. su geçiriyor mu yoksa sadece duş ve yüzme gibi durumlarda mı sıkıntı yaratır?
Google Play'den indirilen uygulamalarda hiç sıkıntı yaşadığınız oldu mu ve titiz bir kullanımda bu saat tahmini kaç sene götürür?
Biraz çok soru sordum kusura bakmayın, saati alma arifesindeyim de. Son olarak da Thor 6'yı önerir misiniz yoksa belirttiğiniz sıkıntılardan dolayı bunu alma Thor 7'yi bekle mi dersiniz?
tunaykr said:
Çok teşekkür ederim. Aklımda takılan birkaç ufak soru işareti var. Birisi şarjı tabii ki de. Normal kullanımda 2 gün dayanıyorsa çok iyi. Bir diğeri de yağmurlu havada vs. su geçiriyor mu yoksa sadece duş ve yüzme gibi durumlarda mı sıkıntı yaratır?
Google Play'den indirilen uygulamalarda hiç sıkıntı yaşadığınız oldu mu ve titiz bir kullanımda bu saat tahmini kaç sene götürür?
Biraz çok soru sordum kusura bakmayın, saati alma arifesindeyim de. Son olarak da Thor 6'yı önerir misiniz yoksa belirttiğiniz sıkıntılardan dolayı bunu alma Thor 7'yi bekle mi dersiniz?
Click to expand...
Click to collapse
Yamurlu havalarda su geçirir mi bilemem, hiç denemedim. Fakat saatin alt kapağını sökünce alt kapakta jonta olduğunu gördüm. Google play uygulamarı ile ilgili bir sıkıntı yaşamadım. Fakat dairesel ekran yerine kare ekran seçince, ekrana sığaması gereken menü tam tersi bir şekilde ekrana sıçmadı. Bu da nadiren oldu. Bu saatin 2-3 yıl götüreceğini düşünüyorum. Thor 7 çıksa mevcut sıkıntıları giderilmiş bir şekilde mi çıkar bilemeyiz.
AYALTUN said:
Use your phone to patch boot.img. You do not need to use your watch for this process. After getting the patched boot.img install it on your watch with fastboot. If you still have problems, upload the boot.img file. I will not patch the boot.img file for you.
Click to expand...
Click to collapse
hhhhh the thing is my phone is iphone :’) is there any other way ?!
AYALTUN said:
Use your phone to patch boot.img. You do not need to use your watch for this process. After getting the patched boot.img install it on your watch with fastboot. If you still have problems, upload the boot.img file. I will not patch the boot.img file for you.
Click to expand...
Click to collapse
tbh i was using it for quiet months , found out it’s a good way to use it instead of a second android phone bcz after all i love open sources systemes not like ios that is too closed even with jealbreak, but in some cases i think it’s better to have an actual android phone , this watch need a moded soft , may be hovac os ported to it would be great
mhd 12 said:
hhhhh the thing is my phone is iphone :’) is there any other way ?!
Click to expand...
Click to collapse
I will patch the boot.img file for you. Send the boot.img file to me. I've said this before. Now I realized that I had mistyped before. Sorry.
AYALTUN said:
Settings
About watch
Build number
Click on the build number
Developer options enabled
Back
System
Developer options
OEM unlocking
USB debugging
Open Minimal ADB and Fastboot folder
Paste the boot.img and vbmeta.img files inside the Minimal ADB and Fastboot folder
Thor 6 root.zip
drive.google.com
Open Minimal ADB and Fastboot
commands
adb reboot bootloader
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
You can open Magisk.
Note: The watch will be reset after the procedure. Please don't forget to take your backups.
Zeblaze Thor 6 Stock ROM coming soon (SP flash tool version).
Click to expand...
Click to collapse
Whenever i hit the second command, the command prompts as waiting device for too long. Is there any video tutorial regarding this.. I searched on youtube but could not find it. And also got confused on the third command because i am a noobie..please help
AYALTUN said:
Settings
About watch
Build number
Click on the build number
Developer options enabled
Back
System
Developer options
OEM unlocking
USB debugging
Open Minimal ADB and Fastboot folder
Paste the boot.img and vbmeta.img files inside the Minimal ADB and Fastboot folder
Thor 6 root.zip
drive.google.com
Open Minimal ADB and Fastboot
commands
adb reboot bootloader
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
You can open Magisk.
Note: The watch will be reset after the procedure. Please don't forget to take your backups.
Zeblaze Thor 6 Stock ROM coming soon (SP flash tool version)just download the bugjaeggar app, download vbmetadisabled.img and magiskpatchedboot.img...hit it from the bugjaeggar
Click to expand...
Click to collapse
V
AYALTUN said:
Settings
About watch
Build number
Click on the build number
Developer options enabled
Back
System
Developer options
OEM unlocking
USB debugging
Open Minimal ADB and Fastboot folder
Paste the boot.img and vbmeta.img files inside the Minimal ADB and Fastboot folder
Thor 6 root.zip
drive.google.com
Open Minimal ADB and Fastboot
commands
adb reboot bootloader
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
You can open Magisk.
Note: The watch will be reset after the procedure. Please don't forget to take your backups.
Zeblaze Thor 6 Stock ROM coming soon (SP flash tool version).
Click to expand...
Click to collapse
AYALTUN said:
Settings
About watch
Build number
Click on the build number
Developer options enabled
Back
System
Developer options
OEM unlocking
USB debugging
Open Minimal ADB and Fastboot folder
Paste the boot.img and vbmeta.img files inside the Minimal ADB and Fastboot folder
Thor 6 root.zip
drive.google.com
Open Minimal ADB and Fastboot
commands
adb reboot bootloader
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
You can open Magisk.
Note: The watch will be reset after the procedure. Please don't forget to take your backups.
Zeblaze Thor 6 Stock ROM coming soon (SP flash tool version).
Click to expand...
Click to collapse
thanks to your post. I have flashed zeblaze thor 6 stock rom using spflash tool. After this flashed vbmetadisabled.img and magisk patched boot.img using bugjaeggar...successfully rooted zeblaze thor 6 watching various tutorials..still in confusion regarding how i did.
AYALTUN said:
Settings
About watch
Build number
Click on the build number
Developer options enabled
Back
System
Developer options
OEM unlocking
USB debugging
Open Minimal ADB and Fastboot folder
Paste the boot.img and vbmeta.img files inside the Minimal ADB and Fastboot folder
Thor 6 root.zip
drive.google.com
Open Minimal ADB and Fastboot
commands
adb reboot bootloader
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot reboot
You can open Magisk.
Note: The watch will be reset after the procedure. Please don't forget to take your backups.
Zeblaze Thor 6 Stock ROM coming soon (SP flash tool version).
Click to expand...
Click to collapse
can you share the stock ROM of this device?
PetiaWarzel said:
can you share the stock ROM of this device?
Click to expand...
Click to collapse
1 week later at the earliest.
dxwolverine said:
Whenever i hit the second command, the command prompts as waiting device for too long. Is there any video tutorial regarding this.. I searched on youtube but could not find it. And also got confused on the third command because i am a noobie..please help
Click to expand...
Click to collapse
My PC is out of order now. I will try to answer as soon as possible. Pls wait.
PetiaWarzel said:
can you share the stock ROM of this device?
Click to expand...
Click to collapse
File on MEGA
mega.nz
dxwolverine said:
File on MEGA
mega.nz
Click to expand...
Click to collapse
Thanks man. This rom version 1.2. I have version 1.3. I will share it very soon.
AYALTUN said:
Спасибо чувак. Это ром версии 1.2. У меня версия 1.3. Я поделюсь этим очень скоро.
Click to expand...
Click to collapse
wait for you, bro
I want so much to install GSI, but when I was going to flash I saw that my device "doesn't have System" Partition. It's called Super Partition there. Does anyone knows how can I install it? I tried some video tutorials, but it always get an Error message.
To flash a ROM on Android devices with Dynamic Partition Layout you have to flash it by means of fastbootd
Code:
fastboot devices
fastboot reboot fastboot
fastboot flash <PARTITION> <FILENAME>.
Look also inside here:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
jwoegerbauer said:
To flash a ROM on Android devices with Dynamic Partition Layout you have to flash it by means of fastbootd
Code:
fastboot devices
fastboot reboot fastboot
fastboot flash <PARTITION> <FILENAME>.
Look also inside here:
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
I forgot to tell, I don't have Fastboot (I think), cause I have a Samsung device. It could work on TWRP Fastboot mode?
IDK. Never used TWRP. And I never owned a Samsung phone.
ferreraiury05 said:
Tengo muchas ganas de instalar GSI, pero cuando iba a flashear vi que mi dispositivo "no tiene la partición del sistema". Allí se llama Super Partition. ¿Alguien sabe cómo puedo instalarlo? Probé algunos tutoriales en video, pero siempre aparece un mensaje de error.
Click to expand...
Click to collapse
hello, first flash stock then enter fastbootd mode and put. fastboot erase system and then give fastboot flash system and the name of your gsi. If you get a space error put this command fastboot delete-logical-partition product_a you give enter and re-enter the command fastboot system and name of your gsi and voila it will be installed