Hello.
We are trying something out and we need help from someone with Engineering SPL or HTC Google Holiday Device. Please contact me and we will give you instructions.
We just need a few images and system dumps from your device. The process will not harm your device in any way shape or form.
Mods: Once we get a helping hand, we can delete this thread.
Yes a fully unlocked (S-OFF) device would help our efforts no end .... maybe more than just relocking the loader ;-)
as stated above the commands run would not harm the device what so ever, but will benifit the andorid community no-end.
Any Volenteers ?
**** anyone willing to lend a hand join this irc channel ****
I thought there was a guy that was more than willing to help in the "relocking bootloader" thread...?
How i can check, what kind of N1 i've?
to check :-
1) power off device
2) hold power + trackball untill the spl loads
3) read a line near the top u will see S-ON or S-OFF
we are looking for someone with S-OFF
I have the holiday phone........instructions please.
1) can you boot into SPL and run
"fastboot getvar all"
2) reboot AS SOON as the phone gets to android run adb shell then "dmesg", near the top of the output it will give u something like
<5>[ 10.611511] 0x000003ee0000-0x000003fc0000 : "misc"
<5>[ 10.613494] 0x000004240000-0x000004740000 : "recovery"
<5>[ 10.619995] 0x000004740000-0x0000049c0000 : "boot"
<5>[ 10.623596] 0x0000049c0000-0x00000dac0000 : "system"
<5>[ 10.791290] 0x00000dac0000-0x0000139c0000 : "cache"
<5>[ 10.901733] 0x0000139c0000-0x00001fe00000 : "userdata"
can u post the results of both please
THIS WILL IN NO WAY CANGE ANY OF THE PHONES DATA !
INFOversion: 0.5
INFOversion-bootloader: 0.33.2012
INFOversion-baseband: 4.02.02.14
INFOversion-cpld: None
INFOversion-microp: 0a15
INFOversion-main: 0.87.0.C3
INFOserialno: XXXXXXXXXXX
INFOproduct: nexusone
INFOplatform: HBOOT-8x50
INFOmodelid: PB9910000
INFOcidnum: GOOGL001
INFObattery-status: good
INFObattery-voltage: 3986mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: ENG
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: c3f18dd3
INFOhbootpreupdate: 11
all: Done!
Here is the first part.....still kinda confused on #2 instructions o.0??
Ah cheers
Right the second bit needs to be ran as soon as u can after the android system boots.
1)run ADB SHELL
2)run #dmesg
3)will give a really long output the part u want will be at the top and look like the example i posted
hope it helps
and many thanks
May I have your email? This thing is to long to fit in this or a PM.
yep ill pm it to u
Ok information sent hope it helps
@twiggy114 use pastebin.Com website like this way everybody can show result
Tips: let your device plug in with usb and you will see notification on windows when you reboot so you can launch ADB AS SOON as you can
http://pastebin.com/f410dc4f8 Ok posted there =]
Can someone please edit his post to remove the serial number, just a thought.
ok no more serial number XD
thanks @twiggy114 i hope seraph1024 have got all is wanted, and can use this results
I still read serial number in pastebin ....
I edit your post with a new pastebin where i remove 2 times your serial number
Nevermind.
oh crap HAHA ummmm how do you delete those pastebin things?
twiggy114
cheers man this has helped no end :-D thats all we need for now, can i get in touch via PM or email when we have more for u to test ?
Again Thankyou
Related
Hi All,
I have been running the gingerbread rom for 2 days (rc2) and i was very happy with it. Untill yesterday evening out of the blue my sdcard was bricked.
Ofcource my phone cant finish booting anymore because some parts of the system are actualy on the sdcard.
fastboot works.
fastboot oem enableqxdm 0
fastboot oem eraseconfig
both return OK but it doesnt help. Tried different SDCARD same result.
I am not in panic because i know this must be solvable.
I have been searching for hours but no luck for me in finding the solution yet.
There is a lot of information to find, but most of it regards a combined USB/SDCARD brick. My USB is perfect.
any help would be much appreciated.
btw, recovery works, but does not see the sdcard as well.
i have S-OFF (alpharef)
fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21F04
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is VODAPE17
INFOsetting->cid::VODAPE17
INFOserial number: SH07CPL00582
INFOcommandline from head: no_console_suspend=1 msmsdcc_sdioirq=
INFO1 wire.search_count=5
INFOcommand line length =469
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.09.05.30_2 androidboot.cid
INFO=VODAPE17 androidboot.carrier=VODA-Netherland androidboot.mi
INFOd=PB9920000 androidboot.keycaps=qwerty androidboot.mode=norm
INFOal androidboot.serialno=SH07CPL00582 androidboot.bootloader=
INFO0.93.0001 no_console_suspend=1 msmsdcc_sdioirq=1 wire.search
INFO_count=5
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:116987 msec
FAILED (status read failed (Timer expired))
in recovery adb works!
Zobat said:
in recovery adb works!
Click to expand...
Click to collapse
just use Pocket Mechanic Professional v2.98 able to format and return the SD Card which is not recognized by the device (SDCard RAW)
Hakim Rahman said:
just use Pocket Mechanic Professional v2.98 able to format and return the SD Card which is not recognized by the device (SDCard RAW)
Click to expand...
Click to collapse
Thnx for the reply but i dont use windows on any of my systems. I dont like the idea of programes "magicly" fixing my problem. I wanna understand stuff.
anyway, i am a lot further now. I have to confess i cant reproduce my fix, i have more than a dozen open browserwindows as a result of my search for resolving this issue. Its probably not even an oxygen issue, but i am not sure of that.
I have my sdcard mounted now again and currently transfering a clockwork mod backup dir to it.
gonna try to use regular recoverymode with these files when i'm done
regards
fixed, sorry for the cluttering up of this board.
I donated 25 dollars.
kind regards
Zobat said:
fixed, sorry for the cluttering up of this board.
I donated 25 dollars.
kind regards
Click to expand...
Click to collapse
You try Hard Reset, or reupload ROM SHIP??
I just flashed TWRP v2.7 on my One. Tried making a backup but it keeps failing while backing up the data partition. It doesn't give any sort of error code or indication why. It just stops and says "Backup Failed". I flashed back to v2.6.3.4 and the backup completes fine. I noticed that w/ v2.6.3.4 it breaks up each partition into multiple files. It doesn't appear that v2.7 does that. Not sure if that would matter. Also, I'm still running stock 4.3. Does v2.7 only work with KitKat ROMs? I know v2.7 just released & there could be some bugs, but wondered if anyone else is experiencing this. Here's my getvar all just in case.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4211mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a85199f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
2.7.0.0 does split the archives, so it's not that.
cschmitt said:
2.7.0.0 does split the archives, so it's not that.
Click to expand...
Click to collapse
Okay. I guess it just didn't explicitly say it's doing so like v2.6.3.4 does. Didn't actually look at the /system backup that did complete in v2.7.
sharksfan7 said:
Okay. I guess it just didn't explicitly say it's doing so like v2.6.3.4 does. Didn't actually look at the /system backup that did complete in v2.7.
Click to expand...
Click to collapse
Grab the log from /cache/recovery/last_log, should tell why it's failing.
Thanks. I've already went back to 2.6.3.4 and ran a backup. I'll have to reflash 2.7 and try again. I'll try to do that later tonight.
So I reflashed TWRP 2.7 and tried to create a backup. Once again it failed. I grabbed the last_log and took a look at it. But it have no idea what the errors mean. Here are the last few lines of the log. Anyone care to shed some light on what this means?
Splitting thread ID 0 into archive 2
E:tar_open error opening ''
E:Error creating tar '' for thread 0
I:ERROR tarList for thread ID 0
E:Error creating backup.
I:createTarFork() process ended with ERROR=255
I:Set page: 'action_complete'
I:Set page: 'rebootcheck'
I:Root permissions appear to be lost... fixing. (This will always happen on 4.3+ ROMs with SELinux.
I:Copying file /cache/recovery/log to /cache/recovery/last_log
Rebooting...
I went back to the Techerrata page and realized that v2.7 is available for the m7 but not m7_ul. I assume that there is a distinct difference between these versions if they need to be listed separately. My AT&T device is a m7_ul, so I guess the reason the backup fails has something to do with that. But from the TeamWin page, if you search for HTC One, it doesn't list the m7_ul variant at all. I only found the image for the m7_ul by browsing the list of all the devices that TWRP is available for. And the only version listed under m7_ul is 2.6.3.4.
Then again, this is just speculation on my part. I really don't know all the technical aspects of how all this works. I just follow the instructions on how to use it. If anyone who knows for sure why backups would be failing in v2.7, I would love to hear an explanation.
I just ran a nandroid backup with twrp 2.7.0.0 and worked fine
I'm kinda in the same boat as the OP. If anyone can help us out that would be awesome!
Me too...hope someone has a working solution. Thanks!
Sent from my HTC One using xda app-developers app
wildboyz322 said:
I'm kinda in the same boat as the OP. If anyone can help us out that would be awesome!
Click to expand...
Click to collapse
z3atl said:
Me too...hope someone has a working solution. Thanks!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The working solution is stay with TWRP 2.6.3.3 or 2.6.3.4
I'm in a similar boat. I'm getting the same error:
Splitting thread ID 0 into archive 2
E:tar_open error opening ''
E:Error creating tar '' for thread 0
I:ERROR tarList for thread ID 0
E:Error creating backup.
I:createTarFork() process ended with ERROR=255
I:Set page: 'action_complete'
I:Set page: 'rebootcheck'
I:Root permissions appear to be lost... fixing. (This will always happen on 4.3+ ROMs with SELinux.
I:Copying file /cache/recovery/log to /cache/recovery/last_log
Rebooting...
However, I'm using a Samsung Galaxy S3 TMO..... and I successfully used TWRP 2.7 / Nandroid to backup my system before.... but now it just gives me this error. Currently trying to backup a rooted stock rom that I used ODIN to put on the device.
EDIT: SOLUTION! I just checked Enable Compression and it seems to be working.....FYI.
EDIT: SOLUTION! I just checked Enable Compression and it seems to be working.....FYI.
Click to expand...
Click to collapse
Fixed it for me too - thanks for that! :good:
I've got a problem with TWRP failing on a backup with E:createTarFork() process ended with ERROR=255.
The is part of the log
* MD5 Created.
Backing up System...
E:Error opening '/system/app/AntHalService/oat' -- error: Not a directory
E:Error in Generate_TarList!
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FA54CYJ11099/2016-01-29--23-52-55_MRA58K_release-keys/system.info'
E:createTarFork() process ended with ERROR=255
Backup Failed.
Cleaning Backup Folder
blocka said:
I've got a problem with TWRP failing on a backup with E:createTarFork() process ended with ERROR=255.
The is part of the log
* MD5 Created.
Backing up System...
E:Error opening '/system/app/AntHalService/oat' -- error: Not a directory
E:Error in Generate_TarList!
I:InfoManager saving '/external_sd/TWRP/BACKUPS/FA54CYJ11099/2016-01-29--23-52-55_MRA58K_release-keys/system.info'
E:createTarFork() process ended with ERROR=255
Backup Failed.
Cleaning Backup Folder
Click to expand...
Click to collapse
I had the same problem. I think the only solution is full wipe
Ryder. said:
I had the same problem. I think the only solution is full wipe
Click to expand...
Click to collapse
Thanks, yeah I thought that might be the case.
Can you tell me why is it that when we do a TWRP restore that system needs to be read only? Because I think I may have forgotten to select this option after I did a restore and that's screwed some stuff up.
blocka said:
Thanks, yeah I thought that might be the case.
Can you tell me why is it that when we do a TWRP restore that system needs to be read only? Because I think I may have forgotten to select this option after I did a restore and that's screwed some stuff up.
Click to expand...
Click to collapse
Go to "mount" in twrp and uncheck mount system partition read-only option. Then it should restore your backup successfully
I am trying to unlock my HTC Incredible 4G on Verizon to load a new ROM onto it. All of my attempts have failed up to this point, by using the WinDroid v2.3 automated tool. I get the following output during the process:
Code:
Task:
1) WINDROID USERS CHOOSE THIS OPTION!
2) Set CID to SuperCID (11111111) - Requires Root
3) Revert CID to original state (VZW__001) - Requires Root
4) Re-lock the bootloader
5) Install recovery
6) Put phone into temp-root mode
10) Exit
Choose a task: 1
========================
= Step 1: Temp-Root =
========================
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA************ device
Under "List of devices attached" above, you should see your device
listed (looks like HTXXXXXXXXXX).
Do you see your device (Y/N)? y
Now unlock your device and confirm the restore operation.
By the time you are done reading this sentence, it should be safe to
accept the restore prompt on your device. You should not have a backup
password set on your phone, so leave both password fields empty.
If this process is successful, the script will continue. If not, this
shell will run forever and you must exit by closing this window.
When you see this message, the restore is complete. Your phone will
now reboot to what looks like an unusable state (be patient!). A
status bar will show across the top, but there will be no ring unlock.
This is good! Wait for the script to begin step 2: SuperCID.
========================
= Step 2: SuperCID =
========================
Your phone's CID is being modified to SuperCID. Once complete, your
phone will reboot to the bootloader.
2+0 records in
2+0 records out
1024 bytes transferred in 0.025 secs (40960 bytes/sec)
142 KB/s (1024 bytes in 0.007s)
31 KB/s (1024 bytes in 0.032s)
2+0 records in
2+0 records out
1024 bytes transferred in 0.035 secs (29257 bytes/sec)
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.011s]
finished. total time: 0.012s
Just above, you should see (bootloader) cid: 11111111
1) Yes, my cid is 11111111. Keep going.
2) No, my cid is VZW__001. Factory reset and try again.
3) No, my cid is VZW__001. Exit the script.
There are two things I notice here:
1) My phone is not identified as "HTxxxxxxxxxx" but rather "FA**********".
2) It appears to work, with the reading and writing of the files, but then it doesn't work.
One thing that I noticed was that when I go into the bootloader when this does not work, I get the first attachment.
When I go to the "Recovery" option, then I get the second attachment.
It appears that I originally put a ROM or S-off'd and unlocked my phone, but somehow lost the unlock and can't figure out how to fix it.
Any help in figure it out would be appreciated.
Do you know which OTA is currently on the phone? The unlock method depends greatly on which one is installed. Assuming you're on the latest, try this method: http://forum.xda-developers.com/showthread.php?t=2664460 The script looks slightly different than what you've posted above.
junkmail9 said:
Do you know which OTA is currently on the phone? The unlock method depends greatly on which one is installed. Assuming you're on the latest, try this method: http://forum.xda-developers.com/showthread.php?t=2664460 The script looks slightly different than what you've posted above.
Click to expand...
Click to collapse
Thanks for the input.
My device is at the most current OTA: 2.19.605.2 710RD
Android: 4.0.4
Kernel:
3.0.8-01625-g9d06ef9
[email protected] #1
SMP PREEMPT
I tried the link that you pointed to with no success. I got the following error messages:
Code:
/sdcard/cid: cannot open for write: Read-only file system
remote object '/sdcard/cid' does not exist
The system cannot find the file specified.
cannot stat 'cid': No such file or directory
/sdcard/cid: cannot open for read: No such file or directory
rm failed for /sdcard/cid, No such file or directory
Could Not Find C:\Users\Keith\Downloads\cid
I've tried just the straight-forward process of a number of different scripts. I think there is something specific that I am missing.
keithsmessina said:
Thanks for the input.
My device is at the most current OTA: 2.19.605.2 710RD
Android: 4.0.4
Kernel:
3.0.8-01625-g9d06ef9
[email protected] #1
SMP PREEMPT
I tried the link that you pointed to with no success. I got the following error messages:
Code:
/sdcard/cid: cannot open for write: Read-only file system
remote object '/sdcard/cid' does not exist
The system cannot find the file specified.
cannot stat 'cid': No such file or directory
/sdcard/cid: cannot open for read: No such file or directory
rm failed for /sdcard/cid, No such file or directory
Could Not Find C:\Users\Keith\Downloads\cid
I've tried just the straight-forward process of a number of different scripts. I think there is something specific that I am missing.
Click to expand...
Click to collapse
Sorry for the delay in response. Looking again at your screenshot in the OP, you are indeed missing the CID. It should appear between "FIREBALL" and "HBOOT":
I have not dealt directly with that one before, but I would imaging that during temproot, you'll need to recreate the directory. I vaguely recall in a post in this forum on how to manually push a different CID via memory chunk. That might be the best approach to rebuild that area so that you can get going again.
Two questions for the general community:
1. Does anyone know if flashing the RUU will restore the CID?
@keithsmessina - It probably wouldn't hurt to try this anyway. I am guessing it will fail due to lack of CID.
2. Will sending the following command work while phone is in bootloader if the phone is not s-off and the \sdcard\CID directory is missing? What, if any other damage could occur if the \sdcard\CID directory is missing?
Code:
fastboot oem writecid VZW__001
junkmail9 said:
Two questions for the general community:
1. Does anyone know if flashing the RUU will restore the CID?
@keithsmessina - It probably wouldn't hurt to try this anyway. I am guessing it will fail due to lack of CID.
2. Will sending the following command work while phone is in bootloader if the phone is not s-off and the \sdcard\CID directory is missing? What, if any other damage could occur if the \sdcard\CID directory is missing?
Code:
fastboot oem writecid VZW__001
Click to expand...
Click to collapse
Thank you for the suggestions.
1. I tried this, but got the message: "Main version is older." I think I can only do that if my version is lower than the current RUU.
2. I tried the fastboot write, but I got:
Code:
(bootloader) fighter_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) sdcc_init_memory_device done
(bootloader) SD clock freq = 19MHz....
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.172s]
finished. total time: 0.174s
When I tried: adb devices with the phone at "fastboot USB", I didn't see anything, so I think it failed for that reason. I tried killing adb, removing and reinserting the USB, adn then running adb devices, but still comes up empty.
I'm really at a loss, but appreciate the help from you guys.
I managed to figure out the read-inly access. HTC Sync Manager started each time and grabbed the SD card before the script could do anything. I renamed the HTC Sync Manager to stop it from running. Then I re-ran the script and got:
Code:
2+0 records in
2+0 records out
1024 bytes transferred in 0.002 secs (512000 bytes/sec)
333 KB/s (1024 bytes in 0.003s)
71 KB/s (1024 bytes in 0.014s)
2+0 records in
2+0 records out
1024 bytes transferred in 0.002 secs (512000 bytes/sec)
< waiting for device >
...
(bootloader) cid: VZW__001
OKAY [ 0.010s]
finished. total time: 0.012s
So, I am still not getting the right CID, but progress nonetheless.
Try uninstalling all HTC software rather than renaming it. Also I believe
http://forum.xda-developers.com/showthread.php?t=2664460 does not require the super cid.
From my Chroma Flo
wmuflyer said:
Try uninstalling all HTC software rather than renaming it. Also I believe
http://forum.xda-developers.com/showthread.php?t=2664460 does not require the super cid.
From my Chroma Flo
Click to expand...
Click to collapse
Thank you for that. I don't know how many times I've gone through it, but I finally got that you just have to do step 6 rather than step 1 to get S-Off. I now have S-Off with TWRP.
The next problem that I am running into is getting an error message when trying to flash the pacman fireball ROM:
Code:
This package is for device: fireballx; this device is .
Really appreciate all the help in getting me to this point.
Need to use the modified TWRP. Read the OP carefully it takes a bit of work, it swaps partitions so you have more space for apps.
Edit: OP in the PAC thread.
Sent from my Nexus 5 using XDA Free mobile app
wmuflyer said:
Need to use the modified TWRP. Read the OP carefully it takes a bit of work, it swaps partitions so you have more space for apps.
Edit: OP in the PAC thread.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I realize that I kept running into an issue changing one of the file systems during that first process which meant that only one of them changed: the "Data" filesystem.
The "Internal Storage" filesystem gave me an MTP error, but then said it finished successfully. It stayed as a vFAT filesystem.
I did get Liquidsmooth up and running with PaGapps, but am now looking for a way to resize my partitions, as there isn't much room left to install apps.
People have looked at resizing the partitions but nobody has had any luck. The partition change seems to be the best bet it was set up by MDMower for his CM builds http://mdmower.cmphys.com/cyanogenmod-fireball/ it might give you more information to make the swap. Beeko has stopped work on Liquid Smooth so for current Android 5.x PAC or CM are the choices and they only work with the partition swap. I have PAC on my Fireball but will probably try CM 12.1 soon.
keithsmessina said:
Thank you for that. I don't know how many times I've gone through it, but I finally got that you just have to do step 6 rather than step 1 to get S-Off. I now have S-Off with TWRP.
Click to expand...
Click to collapse
Excellent! Glad you got it done.
junkmail9 said:
Excellent! Glad you got it done.
Click to expand...
Click to collapse
I've managed to swap the partitions and get the Pacman ROM installed, thanks to the instructions you sent me, wmuflyer. No hiccups with the Pacman ROM, it seems to be polished and working flawlessly. Thanks again for all the help, guys! Really appreciate it.
Heya guys,
So Huami, a sub-company by Xiaomi, gave birth to their watch, and started to sell it in the states as well.
there are two flavors to this watch:
1. the Chinese UI version - Amazefit Smartwatch, with Mifit support and Chinese apps for monitoring activities.
2. the English UI version - called Amazefit Pace, with playstore Mifit version with Google support and Strava sync.
both of the watches are identical by hardware, what distinguish them is the firmware: current Chinese version is 1.2.2a and the English one is 1.3.0n.
the functionality is the same, everything is the same.
the watch itself is based on a Xburst chip, as the w808 ingenic, with the same specs.
the biggest issue is that the manufacturer telling stories and misleading the end users who has bought the Chinese version, and telling us that maybe we'll have a English version for the Chinese one sometime during 2017, if we'll get it at all.
so ... there's a lot of global users with the Chinese version who want to convert their watch to be fully English or support hebrew or what ever they want to do.
is it possible to create a working recovery for the Xburst MIPS chip in this watch?
the bootloader is unlockable, whats next ?
Code:
C:\adb>fastboot getvar all
(bootloader) version-bootloader: U-Boot 2013.07-00094-g03785ac
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 0123456789abcdef
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
all:
finished. total time: 0.280s
Thanks!
1immortal said:
Heya guys,
So Huami, a sub-company by Xiaomi, gave birth to their watch, and started to sell it in the states as well.
there are two flavors to this watch:
1. the Chinese UI version - Amazefit Smartwatch, with Mifit support and Chinese apps for monitoring activities.
2. the English UI version - called Amazefit Pace, with playstore Mifit version with Google support and Strava sync.
both of the watches are identical by hardware, what distinguish them is the firmware: current Chinese version is 1.2.2a and the English one is 1.3.0n.
the functionality is the same, everything is the same.
the watch itself is based on a Xburst chip, as the w808 ingenic, with the same specs.
the biggest issue is that the manufacturer telling stories and misleading the end users who has bought the Chinese version, and telling us that maybe we'll have a English version for the Chinese one sometime during 2017, if we'll get it at all.
so ... there's a lot of global users with the Chinese version who want to convert their watch to be fully English or support hebrew or what ever they want to do.
is it possible to create a working recovery for the Xburst MIPS chip in this watch?
the bootloader is unlockable, whats next ?
Code:
C:\adb>fastboot getvar all
(bootloader) version-bootloader: U-Boot 2013.07-00094-g03785ac
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 0123456789abcdef
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
all:
finished. total time: 0.280s
Thanks!
Click to expand...
Click to collapse
Log shows '[bootloader]unlocked=yes' does it means it's unlocked?
Yes, as far as I know
Sent from my MI 3W using Tapatalk
bump ?
also, any help with porting a twrp recovery to mips platform will be great!
more information that i've dig up from the SoC manufacturer site:
Source code download
Download REPO
$ Mkdir
$ Cd
$ Wget http://git.ingenic.cn:8082/bj/repo
$ Chmod + x repo
Get the complete source code (including toolchain)
$ ./repo init -u http://git.ingenic.cn:8082/gerrit/AOSP/platform/manifest -b android-4.4.4_r2-ingenic
$ ./repo sync
this will provide the source for the M200 SoC.
really waiting for this development
I'm not a dev and sure cant help for dev's things either, but I really appreciate your helpful efforts, guys.
Novedades???
Enviado desde mi MI MAX mediante Tapatalk
No ensure but...
I'm working on the source of the watch and maybe there is some possibility for the root or just translate it... I don't ensure anything but maybe. There is only a problem, since i don't have the watch still i cant test myself and try so is there someone that can try do this for me? with the watch in ADB MODE write this:
Code:
adb backup -apk -all -f backup.ab
Maybe there is some possibility to just translate the launcher
Does this work?
If yes please upload the result here!
Thanks!
Yes it's possible . And possible to install apk or extract apk on the watch.
Look my post on en miui forum.
But wait official translate in next week .... or i wait a Link to download rom 1.3 (official english ) to install in the watch with adb.
Eric
Ericmo said:
Yes it's possible . And possible to install apk or extract apk on the watch.
Look my post on en miui forum.
But wait official translate in next week .... or i wait a Link to download rom 1.3 (official english ) to install in the watch with adb.
Eric
Click to expand...
Click to collapse
You have been telling since weeks that an English update will be coming soon. Where do you take that knowledge from? Or is this just wishful thinking?
I'm afraid just waiting is not enough. We should try to do something on our own, as proposed in this thread.
Neuer_User said:
You have been telling since weeks that an English update will be coming soon. Where do you take that knowledge from? Or is this just wishful thinking?
I'm afraid just waiting is not enough. We should try to do something on our own, as proposed in this thread.
Click to expand...
Click to collapse
yes, I agree with you. I think this is possible but not simple to follow the weekly updates.
For translation in early 2017, this comes from support. Many people have had the same information with support of other languages.
But I still do not understand why there are 2 different firmware ....
Ericmo said:
yes, I agree with you. I think this is possible but not simple to follow the weekly updates.
For translation in early 2017, this comes from support. Many people have had the same information with support of other languages.
But I still do not understand why there are 2 different firmware ....
Click to expand...
Click to collapse
Support only told us that "there might be a possibility to switch the Chinese watch to other languages in 2017'. Interpreting that this means next week there will be an update to English is very, very far fetched.
There are two firmwares because xiaomi wants to have it this way. They do the same for their other products (at least the action cams). This is pure marketing and sales strategy, no technical reasons.
---------- Post added at 07:39 AM ---------- Previous post was at 07:32 AM ----------
I tried to enter bootloader via adb (adb reboot bootlosder), but that did not work. I read somewhere that there is no fastboot on the watch.
What did work was "adb reboot recovery", but of course not much help for us.
You need to type:
adb shell reboot fastboot
Sent from my MI 3W using Tapatalk
Waiting update today.....
Wait and see
striker4709 said:
I'm working on the source of the watch and maybe there is some possibility for the root or just translate it... I don't ensure anything but maybe. There is only a problem, since i don't have the watch still i cant test myself and try so is there someone that can try do this for me? with the watch in ADB MODE write this:
Code:
adb backup -apk -all -f backup.ab
Maybe there is some possibility to just translate the launcher
Does this work?
If yes please upload the result here!
Thanks!
Click to expand...
Click to collapse
Where will be stored the backup file?
Edit: find it!
Inviato dal mio D6633 utilizzando Tapatalk
Pi3rluigi said:
Where will be stored the backup file?
Inviato dal mio D6633 utilizzando Tapatalk
Click to expand...
Click to collapse
It should be in your adb folder.
If you cant find it just use this instead
Code:
adb backup -apk -all -f C:\backup.ab
striker4709 said:
It should be in your adb folder.
If you cant find it just use this instead
Code:
adb backup -apk -all -f C:\backup.ab
Click to expand...
Click to collapse
I'm a Mac user, it was in my account root folder.
Uploading to Mega
Inviato dal mio D6633 utilizzando Tapatalk
1immortal said:
You need to type:
adb shell reboot fastboot
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
Does only a normal reboot for me. Just the same as it I type "adb shell reboot to-heaven" or similar 😀.
Do you really get into a fastboot mode there? What am I doing wrong?
Neuer_User said:
Does only a normal reboot for me. Just the same as it I type "adb shell reboot to-heaven" or similar 😀.
Do you really get into a fastboot mode there? What am I doing wrong?
Click to expand...
Click to collapse
I had tested, for me worked!
The watch restarted and stopped at the Amazfit logo
Inviato dal mio D6633 utilizzando Tapatalk
Pi3rluigi said:
I had tested, for me worked!
The watch restarted and stopped at the Amazfit logo
Click to expand...
Click to collapse
Strange, my watch does not stop at the logo but continues with the normal boot.
What adb version are you using? I have "Android Debug Bridge version 1.0.32".
[GUIDE] Restore Null SN and locked Bootloader|Wrong ROM flash|Amazfit Pace & Stratos
DON'T INSTALL ANY STOCK ROMWhat is this?
It is guide/tutorial for restoring the serial number and unlocking the bootloader on your Amazfit Pace or Stratos watch.
If you have installed a Pace ROM on your Stratos watch, or a Stratos ROM on your Pace, you lost your serial number and locked the bootloader. If this is your case. you will probably note:
- Null serial number
- Locked bootloader
- Touchscreen not working
- Button/keys not working
- Bootloop
Supported devices
- Amazfit Pace watch: A1602 and A1612 models
- Amazfit 2 Stratos watch: A1609 and A16019 models
Can it be fixed?
Yes, it can. At least if your watch can gain root access over adb.
Requirements
1. Property installed adb drivers
How to check this: Open a CMD.exe or any command window on your PC and type:
Code:
adb devices
Output (or similar)
Code:
List of devices attached
9dee1d33 device
2. Property installed fastboot drivers
How to check this: Open a CMD.exe or any command window on your PC and type:
Code:
adb shell reboot bootloader
fastboot devices
Output (or similar)
Code:
0123456789 fastboot
Reboot with:
Code:
fastboot reboot
3. Root access over adb
How to check this: Open a CMD.exe or any command window on your PC and type:
Code:
adb root
Output (or similar)
Code:
adbd is already running as root
Another way to check root:
Code:
adb root
adb shell
Output (or similar)
Code:
[email protected]:/ #
In both cases, you gained root access over adb, you are good to go.
But if you get something like this:
Code:
adb cannot run as root in production builds
Or
Code:
[email protected]:/ $
You don't have root access over adb which means you can't restore your watch check this post: https://forum.xda-developers.com/t/...fit-pace-stratos.3775998/page-3#post-84352471 by matrixios01
How to restore the watch
In few words:
- Meet the requirements
- Get some data from your watch
- Edit a file which i will provide (misc.img) with previous data
- Restore the edited file (misc.img) to your watch
- Use your original unlock code for unlocking again the bootloader (this step may vary)
- Check that you managed to restore the SN and unlocked the bootloader (this step may vary)
- Install a custom ROM for your device (Pace ROM for Pace watch or Stratos ROM for Stratos watch)
- Check that your watch works fine again
I will post whole method in the next post with all needed steps and commands.
Credits
To this people:
@S3V3N for original backup & restore script
@Neuer_User for all his stuff for Amazfit Pace and Stratos
@Cracklydisc (Nicola Sagliano) for all his stuff for Amazfit Pace and Stratos
@1immortal for all his stuff and support for Amazfit Pace and Stratos
Those two guys that tested first this method with different result
If you like my work, buy me a beer.
Restore method
Restore method
1. Get some data form your watch
Turn on your watch, connect the watch to PC, and open a CMD.exe or any command window.
Code:
adb shell getprop
Output (or similar)
Code:
[dalvik.vm.dex2oat-Xms]: [64m]
[dalvik.vm.dex2oat-Xmx]: [512m]
[dalvik.vm.heapgrowthlimit]: [64m]
.
.
.
[wifi.supplicant_scan_interval]: [360]
[windowsmgr.max_events_per_sec]: [500]
[wlan.driver.status]: [unloaded]
You will get a list with a lot of properties, you may find these properties marked in blue, or use individual command for each parameter:
adb shell getprop ro.bt.bdaddr
Output=A1:B2:C3:00:E5:F6 = This is Bluetooth MAC address. 6 pairs of digits.
adb shell getprop ro.sn.serial_numbers
Output=123456789ABCDE = This is the Serial Number (SN) of your watch, and may be corrupted, but you can find it in the back of your watch as SN xxx.... 14 digits.
adb shell getprop ro.sn.serial_numbers_factory
Output=123456789AB = This is the factory serial number, and may be corrupted also, there is no way to get original one AFAIK and I don't know if it is relevant. 11 digits.
adb shell getprop ro.wifi.wifiaddr
Output=A1:B2:C3:00:E5:FF = This is WiFi MAC address. 6 pairs of digits, and different from Bluetooth address.
Click to expand...
Click to collapse
All the data marked in red, is the data we will use to edit misc.img file in next step.
2. Edit misc.img file
To do this, you will need to install an hexadecimal text editor that works on your PC. As I use a Windows PC, I will use HxD to edit misc.img file. You can download HxD text editor for Windows and the dummy misc.img file from here. A dummy misc.img file is a file which has random data on it.
2.1 Unzip the file, install HxD text editor and run it.
2.2 Chose Open, go to the path where misc.img is, select it and open the file:
{
"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"
}
2.3 Ensure that you are using hexadecimal (hex) address visualization:
3. Edit misc.img file with your data
3.1 Serial Number (SN)
Go to memory address 600, and enter your SN on Decoded Text section:
3.2 Bluetooth MAC
Go to memory address 800, and enter your Bluetooth MAC address on Decoded Text section:
3.3 WiFi MAC
Go to memory address A00, and enter your WiFi MAC address on Decoded Text section:
3.4 Factory serial nuember
Go to memory address C00, and enter your factory serial number on Decoded Text section. If you don't have this data, just leave it as it is.
3.5 Save edited misc.img file
Click on Save icon:
4. Now in the unzipped folder you will have the edited misc.img file and a new file named as misc.img.bak which is a backup of misc.img. If you want, you can open misc.img again and check if all your data is correct.
5. Copy misc.img to watch and restore it
Open a CMD.exe or any command window, and go to the path where misc.img is, and copy it to your watch:
Code:
adb push misc.img /sdcard/
Output (or similar)
Code:
1950 KB/s (16777216 bytes in 8.398s)
Restore misc.img on your watch (this is where root is needed):
Code:
adb root
adb shell dd if=/sdcard/misc.img of=/dev/block/platform/jzmmc_v1.2.0/by-name/misc
Output (or similar)
Code:
8193+0 records in
8192+0 records out
4194304 bytes transferred in 0.870 secs (4821039 bytes/sec)
Reboot your watch:
Code:
adb reboot
6. Check the SN
Reboot into fastboot mode:
Code:
adb shell reboot bootloader
Get all data from bootloader:
Code:
fastboot getvar all
Output (or similar)
Code:
.
.
.
(bootloader) serialno: 123456789ABCEF
.
.
(bootloader) unlocked: no
.
.
.
If you get your SN back ((bootloader) serialno: 123456789ABCEF), restoration was successful. But you may get unlocked bootloader result ((bootloader) unlocked: no), and here is where you will use your original unlock code, or request it again using the unlock service you already know.
Code:
fastboot oem unlock your_unlock_code
Output (or similar)
Code:
...
OKAY [ 0.047s]
finished. total time: 0.048s
And check again your bootloader status:
Code:
fastboot getvar all
Output (or similar)
Code:
.
.
.
(bootloader) serialno: 123456789ABCEF
.
.
(bootloader) unlocked: yes
.
.
.
If you get (bootloader) unlocked: yes your bootloader is unlocked again. If you get (bootloader) unlocked: no result, don't worry, it may be unlocked after installing any ROM for your device (this happened to me).
Exit from fastboot mode:
Code:
fastboot reboot
8. Install a ROM for your device
- If you own an Amazfit Pace watch, I suggest you to install any PACEfied ROM (1.2.50h for example) but 1.2.51 version (remember that this version is causing some issues for some users).
- If you own an Amazfit Stratos watch, I suggest you to install any STRATOSfied ROM.
9. Factory Reset
When the ROM is installed, probably it will not boot and will stay in a bootloop in the bootanimation, so you MUST do a Factory Reser in order to make it boot.
Reboot to fastboot mode:
Code:
adb shell reboot bootloader
Erase cache (It will take around 8s):
Code:
fastboot erase cache
Erase data (It will take around 210s):
Code:
fastboot erase data
10. When the Factory Reset finish, check again the status of your bootloader
Code:
fastboot getvar all
Now you should get unlocked bootloader result. If not, use again the unlock code and command.
Exit from fastboot mode:
Code:
fastboot reboot
11. Your watch may be operative now
If everything went right, you managed to recover your bricked/****ed watch. Be ready to pair the watch with Amazfit app and enjoy your watch again!
Thanks for reading.
MIO2
MIO2
MIO3
MIO3
MIO4
MIO4
Hi, Saratoga79
I get the message in point 3:
adb cannot run as root in production builds
and
[email protected]:/ $
No way to recover it
:crying::crying::crying:
Thanks a bunch for doing that mate!
aromanos_76 said:
Hi, Saratoga79
I get the message in point 3:
adb cannot run as root in production builds
and
[email protected]:/ $
No way to recover it
:crying::crying::crying:
Click to expand...
Click to collapse
And how is your bootloader? If you have locked bootloader, there is nothing to do, AFAIK.
What was your problem?
Saratoga79 said:
And how is your bootloader? If you have locked bootloader, there is nothing to do, AFAIK.
What was your problem?
Click to expand...
Click to collapse
I can access to the device (adb devices) and start the fastboot mode.
The strange thing is.... that even the serial no is null, the watch is locked and I've no root permissions...
The watch still working!!! :laugh:
Sorry, I still can't attache images: hxxxs://ibb.co/iDg4zx
Great job Saratoga, I hope this means you got your PACE back up and running!
Great, I just used the info to save my misc.img partition in case something goes wrong.
nhedgehog said:
Great, I just used the info to save my misc.img partition in case something goes wrong.
Click to expand...
Click to collapse
You could also get your own misc.img from watch.
Guess I wasn't specific enought. Thats what I did, saving my own misc.img from watch.
I had a null serial number in my Stratos, then I followed all steps
Now I have a serial number back, however the bottons and touch screen is not working
What do you think could be the problem ?
RENEMX said:
I had a null serial number in my Stratos, then I followed all steps
Now I have a serial number back, however the bottons and touch screen is not working
What do you think could be the problem ?
Click to expand...
Click to collapse
What ROM did you install after restoring your SN?
Thanks Saratoga79 for replying
This is the info: My watch is the Stratos A1609
Smartwatch is connected to Amazfit app, running version: 1.2.44
Something I saw trying to update the version is Using ROM Stratos Everest 2.0.15.0 Multilanguage , Installer V.06 by Saratoga is after checking the unlock is YES
I have tried to change the language BUT after clicking for the installation the message is “I have not installed ROM V0.6
So the problem today is that the touch screen
Below additional information, I hope it helps, any question please let me know.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version-bootloader: U-Boot 2013.07-00101-g96591b8
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 16091814071027
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
all:
finished. total time: 0.313s
RENEMX said:
Thanks Saratoga79 for replying
This is the info: My watch is the Stratos A1609
Smartwatch is connected to Amazfit app, running version: 1.2.44
Something I saw trying to update the version is Using ROM Stratos Everest 2.0.15.0 Multilanguage , Installer V.06 by Saratoga is after checking the unlock is YES
I have tried to change the language BUT after clicking for the installation the message is “I have not installed ROM V0.6
So the problem today is that the touch screen
Below additional information, I hope it helps, any question please let me know.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version-bootloader: U-Boot 2013.07-00101-g96591b8
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 16091814071027
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
all:
finished. total time: 0.313s
Click to expand...
Click to collapse
So you already installed my ROM for your Stratos? Did you get any error? Did you do the Factory reset?
If you still face same issue, maybe you can try installing STRATOSfied.
Otherwise this method, I want to go back to stock, lock my bootloader and use it as a new (I bought as used and the ex-owner installed a ROM and unlock the bootloader), how can i do that?
Thanks
After i fixed the issue of null serial number using your procedure
Then
I used the tool: ROM Everest 2.0.15.0 to change the language however the program cannot recognize my watch as A1609, please see:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The message is the following:
Model detected: A1602 - Amazfit Sports Watch
Version Installed ROM: huanghe -1.2.44
China ROM PACEfied found
ONLY FOR AMAZFIT 2 STRATOS WATCH
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
My watch is stratos A1609 but inside it has running Android PACEfied
So, I have tried to install flash Chinese/English ROM using your tool "Huawmi AMAZFIT Tool" and
Firmware_CN_STRATOS_2.0.7.5.zip
After that there are three options:
a) I want to use already stracted files
b) I want to delete already extracted files and re unpack it
c) I want to stop this process
doing option a) and b) againg I still have Android Pacified and touch screen is not working
Saratoga79 said:
So you already installed my ROM for your Stratos? Did you get any error? Did you do the Factory reset?
If you still face same issue, maybe you can try installing STRATOSfied.
Click to expand...
Click to collapse
I cannot do factory reset becuase touch screen not working
I tried Startosfied but it did not work, and also I tried installing Stratos ROM but it did not work
I think the problem is the hardware is for Stratos but software is Paciefied, what do you think ?
Please read the latest info I sent (previous to this one)