Related
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
EVO3D GSM ICS 1.53 DOWNGRADE BL – UNLOCK bez HTCDev!!!!!!
THX XDA user Unknownforce - this is his work, I have tested and it works!
http://forum.xda-developers.com/showthread.php?t=2124142
VŠE PROVÁDÍTE NA VLASTNÍ RIZIKO, ZA ŠKODY NENESU ŽÁDNOU ZODPOVĚDNOST. POSTUP VYZKOUŠEN NA MÉM EVO 3D BEZ PROBLÉMU.
UJISTĚTE SE ŽE JE VÁŠ PŘÍSTROJ OPRAVDU S-ON!!! POKUD PROVEDETE TENTO POSTUP NA ZAŘÍZENÍ S-OFF, DOJDE K JEHO TOTÁLNÍMU UMRTVENÍ BEZ MOŽNOSTI NÁVRATU!!!
POSTUP JE PRO ZAŘÍZENÍ KTERÉ JSOU PO ZÁRUČNÍ VÝMĚNĚ DESKY S PŮVODNÍM S.N. A NOVÝM IMEI A NELZE PROVÉST UNLOCK PŘES HTCDev.
PŘÍSTROJ MUSÍ BÝT VE STAVU *LOCKED* , *S-ON* , BOOTLOADER 1.53 !!!!
VYŽADUJE MINIMÁLNÍ ZNALOST LINUX (PRÁCE V TERMINÁLU) A JEHO LIVE NEBO INSTALOVANOU VERZI (UBUNTU)
!!!!!POZOR!!!!!! Příkaz pro zjištění aktuální misc partition:
" adb shell cat /proc/partitions "
V telefonu zapnuto USB ladění. ADB příkaz použít třeba ze složky kterou máte připravenou z pokusů o unlock HTCDev.
Příkaz zobrazí mmcblk0pxx partitions, pokud vidíte mmcblk0p32 pak je vaše misc partition 32, pokud ne, pak je 31. Pokud vidíte obě, je to ta s vyšším číslem (u mě 1022)
KROK 1
--------------------------------------------------------------------
1.) PG86IMG.ZIP vaší aktuální ROM RUU (ICS 3.28.401.1 )nakopírujte do kořenového adresáře SDCard.
2 .) S telefonem napájeným POUZE z baterie restartujte do bootloaderu, nechte detekovat zip a dostat se do bodu, kdy to chce, abyste stiskli Vol-Up - aktualizovat. NESPOUŠTĚJTE aktualizaci!!!
3.) nechte přístroj v tomto stavu a počkejte alespoň jednu nebo dvě minuty.
4.) Sejměte kryt baterie a připojte přístroj do elektrické sítě.
(POUŽIJTE ORIGINÁL HTC - DOPORUČENO, neoriginální mohou mít nižší napětí a telefon se může vypnut. K vypnutí dochází také s novějšímy typy karet SD, zkoušejte 4 -8 GB, mě to šlo z A-Data 16GB class10)
5.) Vyjměte baterii. (Zařízení by mělo zůstat zapnuté, pokud se tak nestane, začněte znovu). Baterii nevracejte dovnitř.
6.) Zde je choulostivá část.
Přečtěte si Několikrát: buďte připraveni vytáhnout síťový kabel ven v ten správný čas ...
Stiskněte tlačítko Vol-Up
Po 5 sekundách od chvíle kdy se rozbliká vedle položky BOOTLOADER hláška Aktualizace (Updating) vyrvěte nabíječku z telefonu (ne z elektriky-může ještě chvíli dávat napětí a překročíte časový limit!!)
Chvíli vyčkejte a připojte nabíječku zpět. Pokud se vše povedlo, měla by červená dioda u přední kamery velice slabě trvale svítit.
POZOR!!!!! Na mém telefonu byl UPDATE BOOTLOADER velice rychlý - cca 3sec a najel na BOOT a dále, a BRICK se povedl po hodině. Buďte trpěliví a zkoušejte to několikrát. V případě že přejedete a nestihnete vytáhnout kabel, nechte update už dojet do konce a celý postup opakujte znovu a znovu a znovu…….
Přístroj je nyní BRICK a připraven na další krok.
KROK 2 - LINUX část
--------------------------------------------------------------------
NEPŘIPOJUJTE ZATÍM TELEFON - POČKEJTE NA VYZVÁNÍ!!!
TELEFON STÁLE BEZ BATERIE!!!!
1.) Spusťte Linux
2.) Extrahujte ultimate.zip do linux PC Home složky - nejjednoduší a nejlepší umístění pro další práci
(záměrně odstraněny soubory pro CDMA,ponechány GSM)
3.) Spusťte Terminal, s právy root, (su, or sudo -s)(zadejte vaše heslo do linux) – za vlnovkou bude místo dolaru $ mřížka #
4.) přejít do složky ultimate: cd ultimate
zadejte příkaz chmod 755 ultimate
5.) zadejte ./ultimate -g -d a dejte Enter.
Uvidíte výstup:
___________________________________________________________________
==== EVO 3D Ultimate Recovery Tool v 2.5, developed by Unknownforce ====
IMPORTANT: Do not plug in device until TOLD to do so.
Is your misc partition 31 or 32?
____________________________________________________________________
Zadejte číslo partition zjištěnou v ADB.
____________________________________________________________________
Downgrade Selected, Ready to begin? (Y/N)
_____________________________________________________________________
Zadejte Y a Enter
_____________________________________________________________________
Plug in your device now...
Waiting for device...
_____________________________________________________________________
NYNÍ PŘIPOJTE TELEFON. Měli byste vidět něco podobného:
_____________________________________________________________________
Found the Correct Device!
Writing image file!
SUCCESS!
Found the Correct Device!
Writing image file!
SUCCESS!
_____________________________________________________________________
Celé to vypadalo takhle:
[email protected]:~$ sudo -s
[sudo] password for major:
[email protected]:~# cd ultimate
[email protected]:~/ultimate# chmod 755 ultimate
[email protected]:~/ultimate# ./ultimate -g -d
==== EVO 3D Ultimate Recovery Tool v 2.5.1, developed by Unknownforce ====
GSM Device selected.
!!!WARNING!!! Be sure your device is a GSM Device!!!
You will permanently damage your phone if it's NOT a GSM device!!!
IMPORTANT: Do not plug in device until TOLD to do so.
Is your misc partition 31 or 32?
32
Downgrade Selected, Ready to begin? (Y/N)
y
Plug in your device now.
Waiting for device...
Device Found!
Writing image file!
SUCCESS!
Unbricking...
Writing image file!
SUCCESS!
Cleaning up...
All requested tasks completed.
You may now put your battery back in and boot up!
[email protected]:~/ultimate#
__________________________________________________________________________
Nyní vyjměte SD kartu, vložte zpět baterii a spusťte telefon bo bootloaderu. Ověřte verzi bootloader 1.49.0007, telefon jde zapnout ale loopback na HTC splash screenu.
KROK 3.
--------------------------------------------------
Oživení telefonu
1. Do root SD karty nakopírovat GB 1.20.401.8 opět jako PG86IMG.ZIP a nechat proběhnout flash – tím je downgrade na GB proveden.
2. Zařízení je ve stavu *LOCKED*, S-ON a s GB 2.3.4
DOWNGRADE PACK .... WAIT PLEASE, UPLOADING.......
Re: DOWNGRADE-UNLOCK HB 1.53 MB REPLACED no HTCDev!!! - Tested
An english translation would be useful, indeed
Sent from my HTC EVO 3D X515m using XDA Premium HD app
ENGLISH
EVO3D GSM ICS 1.53 downgrade BL - UNLOCK without HTCDev!!!
THX XDA user Unknownforce - this is his work, I have tested and it works!
http://forum.xda-developers.com/showthread.php?t=2124142 Here you can also read, because my English is bad.
ALL MAKE AT YOUR OWN RISK, AND I DO NOT TAKE ANY GUARANTEE. PROCEDURE TESTED ON MY EVO 3D WITHOUT PROBLEM.
MAKE SURE THAT IS REALLY YOUR UNIT S-ON!! IF THIS PROCEDURE FOR S-OFF DEVICE,will be irreversibly damaged!! Maybe no way back.
PROCEDURE IS FOR DEVICES THAT ARE THE WARRANTY CHANGE MB WITH ORIGINAL SN A NEW IMEI AND CAN NOT UNLOCK VIA HTCDev.
PHONE MUST BE IN STATE * LOCKED *, * S-ON *, bootloader 1.53!!
REQUIRED MINIMUM KNOWLEDGE OF LINUX (WORK IN TERMINAL) AND ITS LIVE OR INSTALLED VERSION (UBUNTU)
!!! WARNING!!! Command to determine the current misc partition: (in Windows)
"Adb shell cat / proc / partitions"
The phone turned on USB debugging. ADB command used to be in the folder you have made with attempts to unlock HTCDev.
This command displays mmcblk0pxx partitions if you see mmcblk0p32 then your misc partition 32, if not, then is 31 If you see both, it's the one with the higher number (for me 1022)
STEP 1
-------------------------------------------------- ------------------
1) PG86IMG.ZIP your current ROM RUU (3.28.401.1 ICS), copy it to the root of SDCard.
2nd) With the phone powered on battery, reboot into the bootloader, let detect .zip and get to the point where it wants to press Vol-Up - update. DO NOT update!!
3) let the phone in this condition and wait at least one or two minutes.
4) Remove the battery cover and connect the device to the mains.
(USE ORIGINAL HTC - RECOMMENDED, unoriginal may have lower voltage and the phone can be turned off. To turn off also occurs with newer types of SD cards, try 4 -8 GB me it went from A-Data 16 gigabytes CLASS10)
5) Remove the battery. (The device should remain on, if not, start again). Do not return the battery inside.
6) Here is the tricky part.
Read a few times: be ready to pull the power cord out at the right time ...
Press Vol-Up
After 5 seconds from the moment the flash next to message Bootloader Update (Updating) snatches the charger from the phone (not the electrician may still while giving voltage and exceed the time limit!)
Wait a while back and connect the charger. If everything went well, should the red LED on the front of the camera very weakly steady.
CAUTION!! On my phone was bootloader UPDATE very fast - about 3 seconds and hit a BOOT and forth, and BRICK was good after an hour. Be patient and try it a few times. If miss dont uplug cable, let the update to finish and repeat the process again and again and again .......
The device is now BRICK and ready for the next step.
STEP 2 - LINUX part
-------------------------------------------------- ------------------
DO NOT CONNECT PHONE - WAIT FOR PROGRAM
STILL NO PHONE BATTERY!!
1) Run Linux
2) Extract the ultimate.zip to Home folder - the easiest and the best location for further work
(I deleted files for CDMA, GSM only)
3) Launch Terminal, the rights of root (su or sudo-s) (enter your password in linux) - change $ to #
4) go to your ultimate folder - cd ultimate
enter the command chmod 755 ultimate
5) type . / Ultimate-g-d and press Enter.
You will see output:
___________________________________________________________________
==== EVO 3D Ultimate Recovery Tool in 2.5, developed by Unknownforce ====
IMPORTANT: Do not plug in device until TOLD to do so.
Is your misc partition 31 or 32?
____________________________________________________________________
Enter the partition number found in the ADB.
____________________________________________________________________
Downgrade Selected, Ready to begin? (Y / N)
_____________________________________________________________________
Enter Y and Enter
_____________________________________________________________________
Plug in your device now ...
Waiting for device ...
_____________________________________________________________________
CONNECT NOW PHONE. You should see something like this:
_____________________________________________________________________
Found the Correct Device!
Writing image file!
SUCCESS!
Found the Correct Device!
Writing image file!
SUCCESS!
_____________________________________________________________________
all this is:
[email protected]:~$ sudo -s
[sudo] password for major:
[email protected]:~# cd ultimate
[email protected]:~/ultimate# chmod 755 ultimate
[email protected]:~/ultimate# ./ultimate -g -d
==== EVO 3D Ultimate Recovery Tool v 2.5.1, developed by Unknownforce ====
GSM Device selected.
!!!WARNING!!! Be sure your device is a GSM Device!!!
You will permanently damage your phone if it's NOT a GSM device!!!
IMPORTANT: Do not plug in device until TOLD to do so.
Is your misc partition 31 or 32?
32
Downgrade Selected, Ready to begin? (Y/N)
y
Plug in your device now.
Waiting for device...
Device Found!
Writing image file!
SUCCESS!
Unbricking...
Writing image file!
SUCCESS!
Cleaning up...
All requested tasks completed.
You may now put your battery back in and boot up!
[email protected]:~/ultimate#
__________________________________________________________________________
Now remove the SD card, insert the battery and start the phone bo bootloader. Verify the version 1.49.0007 bootloader, the phone is switched on but loopback on HTC splash screen.
STEP 3
--------------------------------------------------
Make phone to condition.
First To root SD card copy GB 1.20.401.8 again as PG86IMG.ZIP and execute flash Vol-UP+PWR - that is to downgrade to GB executed.
Now device is in * LOCKED * S-ON and GB 2.3.4
DOWNGRADE PACK http://www.ulozto.cz/x1i3NkS/downgrade2-rar
This is all in English in my thread in my signature below.
But the translation is helpful for some I'm sure.
Big THX to Unknownforce
I refer to your thread and I thank you again. Good work! :good: Without you this would not.Guys can read your post when something does not understand me.
I have 3.28.720.1 ICS on my MB Replaced EVO 3D instead of your 3.28.401.1 ICS.
I don't know will it work
720?
*** LOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT :1.53.0007
If yes, than must function. GSM version !!!!!
3.28.720.1 - it is Chinese (Asia) version? I do not know....
It's Indian version I am going to try it today
------------
I tried your ICS 3.28.401.1 - PG86IMG.zip it says CID incorrect.
& Yes my devices is locked & not S-OFF
*** LOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT :1.53.0007
eMMC-boot
May 22 2012, 01:06:07
ICS 3.28.720.1 Its Indian version of EVO 3D.
I guess I should change CID of my device. Please let me know what CID should I use & also how can I get my devices PG86IMG.zip
---------
I downloaded & tried
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_264110_signed.zip
but same error CID incorrect Update Failed
Can any one tell me how to change CID of Locked device I have done it before but I don't remember it now
Sent from my HTC EVO 3D X515m using Tapatalk 2
HBOOT downgraded with phone after OTA update to ICS (HBOOT 1.53) successfully . But brick it was hard until after the ninth attempt succeeded to brick with updating bootloader
Same here managed to change cid,
After that after 3 hours of trial & errors managed to get brick,
After that managed to get downgrade on Windows 7 PC with VMPlayer (Ubuntu).
Now on LOCKED 1.49.0007 Now trying to get it Unlocked Can anyone tell me whats to best method for GB Unlock without HTCDEV.com
Device now GB a HBOOT 1.49.0007,S_ON ?
->Unlock with old good Revolutionary, this make also S-OFF and when need also CWM recovery
Optional ->flash custom Touch Recovery
->after from (4EXT) Recovery flash root or any Custom rom with root build-in
Can anyone out there lend me a hand? I'm trying to remove "Tampered" via
Code:
./revone -t
I tried it manually in terminal as well as Hasoon's toolkit
I tried the -t option and receive [ error code = -2 ]
- Stock - ATT
- TWRP - 2.6.0.0
- Tampered
- Unlocked
- M7_UL PVT SHIP S-OFF RH
- CID-CWS_001
- HBOOT-1.44.0000
- RADIO-4A.14.3250.13
- OpenDSP-v26.120.274.0202
- eMMC-boot
- Android 4.1.2
- HTC Sense - 5.0
- SW 1.26.502.10
- HTC SDK API 5.1.2
- Kernel 3.4.10-g3de55a2
-
MindProbe said:
Can anyone out there lend me a hand? I'm trying to remove "Tampered" via
Code:
./revone -t
I tried it manually in terminal as well as Hasoon's toolkit
I tried the -t option and receive [ error code = -2 ]
- Stock - ATT
- TWRP - 2.6.0.0
- Tampered
- Unlocked
- M7_UL PVT SHIP S-OFF RH
- CID-CWS_001
- HBOOT-1.44.0000
- RADIO-4A.14.3250.13
- OpenDSP-v26.120.274.0202
- eMMC-boot
- Android 4.1.2
- HTC Sense - 5.0
- SW 1.26.502.10
- HTC SDK API 5.1.2
- Kernel 3.4.10-g3de55a2
-
Click to expand...
Click to collapse
...answered my own question.( -2 error ). I swapped usb cables and removed from my usb hub and it worked fine ( "tampered" is no longer showing" )
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
[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)