i found these tools in Synaptic:
fastboot
ddms (sdk)
&
adb
Can i use these to unlock the bootloader instead of downloading a bunch of stuff from websites? i found the device using fastboot and the unlock code from sony but thats about as far as i got.
Sure, you also need the linux version of flashtool, which you can get from the site (no need to install), and you are good to go. :thumbup:
Sent from my E2303 using XDA Free mobile app
would anyone mind guiding me through the steps?
xinjian said:
would anyone mind guiding me through the steps?
Click to expand...
Click to collapse
There is a linux version of Flashtool and its an sh script so the command would be
sudo bash LocationOfFlashtool/Flashtool
Click to expand...
Click to collapse
And then when the bootloader is unlocked and you want to flash recovery
sudo fastboot flash recovery LocationOfRecovery/recovery.img
Click to expand...
Click to collapse
xinjian said:
i found these tools in Synaptic:
fastboot
ddms (sdk)
&
adb
Can i use these to unlock the bootloader instead of downloading a bunch of stuff from websites? i found the device using fastboot and the unlock code from sony but thats about as far as i got.
Click to expand...
Click to collapse
I just rooted my phone under Gentoo using adb commands from install.bat file which I downloaded from here: http://www.mediafire.com/download/awrsi78ddjl0x2r/rootkitXperia_E23xx_26.1.X.3.xxx.zip
Just unpack this zip, change directory to where you unzipped it and run:
Code:
adb push files/getroot /data/local/tmp/
adb push files/su /data/local/tmp/
adb push files/supolicy /data/local/tmp/
adb push files/libsupol.so /data/local/tmp/
adb push files/Superuser.apk /data/local/tmp/
adb push files/busybox /data/local/tmp/
adb push files/99SuperSUDaemon /data/local/tmp/
adb push files/install-recovery.sh /data/local/tmp/
adb push files/install_tool.sh /data/local/tmp/
adb shell "chmod 0755 /data/local/tmp/getroot"
adb shell "chmod 0755 /data/local/tmp/busybox"
adb shell "chmod 0755 /data/local/tmp/install_tool.sh"
adb shell "/data/local/tmp/getroot /data/local/tmp/install_tool.sh"
After last command you should get something like this:
Code:
Patching address 0xffffffc00112a9d0
Start map/unmap thread.
Start write thread.
Spraying kernel heap.
100 200 300 400 500 600 700 800 900 1000
Start read thread.
Done.
Patching address 0xffffffc058b34008
Start map/unmap thread.
Start write thread.
Spraying kernel heap.
100 200 300 400 500 600 700 800 900 1000
Start read thread.
10000
Done.
2047+1 records in
2047+1 records out
1048328 bytes transferred in 0.057 secs (18391719 bytes/sec)
203+1 records in
203+1 records out
104368 bytes transferred in 0.009 secs (11596444 bytes/sec)
203+1 records in
203+1 records out
104368 bytes transferred in 0.004 secs (26092000 bytes/sec)
203+1 records in
203+1 records out
104368 bytes transferred in 0.004 secs (26092000 bytes/sec)
203+1 records in
203+1 records out
104368 bytes transferred in 0.004 secs (26092000 bytes/sec)
58+1 records in
58+1 records out
30168 bytes transferred in 0.005 secs (6033600 bytes/sec)
613+1 records in
613+1 records out
314232 bytes transferred in 0.016 secs (19639500 bytes/sec)
11948+1 records in
11948+1 records out
6117378 bytes transferred in 0.189 secs (32367079 bytes/sec)
1+1 records in
1+1 records out
629 bytes transferred in 0.003 secs (209666 bytes/sec)
0+1 records in
0+1 records out
55 bytes transferred in 0.001 secs (55000 bytes/sec)
Actually you don't need to have Flashtool to unlock the bootloader since the device is officially supported by Sony
Just follow the instructions in its webpage
Related
On an Atrix I am doing:
"adb push operaariak.m3u /sdcard-ext/playlists"
getting 337 kb/s (5377 bytes in 0.015s)
next i do
"adb ls /sdcard-ext/playlists/"
getting the list of existing m3u files without the new file.
What am I doing wrong?
SDcard is 32 G 16 G available.
Having successfully semi-rooting my device through pauls root i was trying to install the SDE, i followed all steps correctly and ran the batch file but when rebooting into recovery mode no such menu appeared, i have confirmed root shell access so now i'm wondering if anyone else has had a problem? really would want to get the menu installed. It just seems not to work at all and i've ran the script from both my pc and from the internal device memory but this seems not to have worked, any ideas? Thanks
I followed all paul's instruction but I can't root my 101, I tried SDE script too but I can't see any differcence in recovery
Nadrian,
could you try this for me:
start a cmd.exe, and launch the script from this cmd window.
Do a copy/paste of the execution log and post it here please ?
(to copy paste from cmd, do Alt+space, select "edit", "mark", then select text with mouse, press enter then do a paste here)
Moskiller, you problem is different if you don't have the # prompt when doing Paul's root, could you show me the log of the adb session ?
@letama i'll pm you those tomorrow and thanks for the help!
letama said:
Nadrian,
could you try this for me:
start a cmd.exe, and launch the script from this cmd window.
Do a copy/paste of the execution log and post it here please ?
(to copy paste from cmd, do Alt+space, select "edit", "mark", then select text with mouse, press enter then do a paste here)
Moskiller, you problem is different if you don't have the # prompt when doing Paul's root, could you show me the log of the adb session ?
Click to expand...
Click to collapse
If u explain to me how do it, with pleasure
Sent from my ARCHOS 101G9 using Tapatalk
Moskiller said:
If u explain to me how do it, with pleasure
Click to expand...
Click to collapse
I need all the text in the cmd window with the adb commands and the results.
you can do the copy/paste the same way I explained to Nadrian.
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>enable_sde
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push zimage /data/
local/tmp
306 KB/s (2655004 bytes in 8.450s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push initrd.cpio.l
zma /data/local/tmp
314 KB/s (398045 bytes in 1.236s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push abcbox /data/
local/tmp
323 KB/s (277204 bytes in 0.838s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell chmod 755 /d
ata/local/tmp/abcbox
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell /data/local/
tmp/abcbox kd_flasher -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.l
zma
Generating KD...
Updating KD (3053305 bytes)...
0
100
It worked when i executed the script through command prompt, but here's the execution log anyway, thanks for the tool and for all help!
My log (Windows XP SP3):
C:\android-sdk-windows\platform-tools>enable_sde.bat
C:\android-sdk-windows\platform-tools>adb push zimage /data/local/tmp
1999 KB/s (2655004 bytes in 1.296s)
C:\android-sdk-windows\platform-tools>adb push initrd.cpio.lzma /data/local/tmp
1776 KB/s (398045 bytes in 0.218s)
C:\android-sdk-windows\platform-tools>adb push abcbox /data/local/tmp
1925 KB/s (277204 bytes in 0.140s)
C:\android-sdk-windows\platform-tools>adb shell chmod 755 /data/local/tmp/abcbox
C:\android-sdk-windows\platform-tools>adb shell /data/local/tmp/abcbox kd_flashe
r -k /data/local/tmp/zimage -i /data/local/tmp/initrd.cpio.lzma
Generating KD...
Updating KD (3053305 bytes)...
0
100
C:\android-sdk-windows\platform-tools>
Even for me, SDE doesn't work (archos 101 G9 8gb)
EDIT: WORKS!
at the fourth attempt it worked (ext4 firmware)! After removing the root and before reboot, the only thing I changed was disconnect the USB cable from tablet (???). ciao
hitman72 said:
at the fourth attempt it worked (ext4 firmware)! After removing the root and before reboot, the only thing I changed was disconnect the USB cable from tablet (???). ciao
Click to expand...
Click to collapse
Weird!
I guess a couple of md5sum could help pinpointing adb push or flash issue.
I'll add that someday.
Thanks for the report!
My htc evo 4glte is on hboot 1.19 and its software says 2.13.651.1 710RD and Im currently trying to do the facepalm s-off method but im stuck with this. Im not sure what to do or what im doing wrong. :,(
C:\adb\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT256S400039 device
C:\adb\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.003 secs (2666 bytes/sec)
[email protected]:/ # adb reboot bootloader
adb reboot bootloader
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ # adb reboot bootloader
adb reboot bootloader
error: device not found
1|[email protected]:/ #
After this part type
C:\adb\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.003 secs (2666 bytes/sec)
Code:
exit
Code:
exit
These 2 exit commands will bring you out of adb shell and back to the regular command prompt.
**Note** if the cmd window closes on the second exit command then only 1 exit command is needed. (it's been a while so don't really remember)
Then type reboot-bootloader
uh well it looks like i got to the black htc screen but it said unkown error data failure does that mean i need to redownload something and redo it? im going to do that i guess an try again it seems it didnt hurt anything to mess that up..
welp now its hanging at sending 'zip' step 3.. :did i screw it up? how long is it supposed to take? :,(
I hate life heres a copy of my dumb scribble and please save me from my stupidness. ^^
F:\4glte\Evo4GLTERoot2>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT256S400039 device
F:\4glte\Evo4GLTERoot2>adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
ev/block/mmcblk0p5 bs=1 seek=20 <
8+0 records in
8+0 records out
8 bytes transferred in 0.006 secs (1333 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
F:\4glte\Evo4GLTERoot2>adb reboot bootloader
F:\4glte\Evo4GLTERoot2>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.080s]
finished. total time: 0.080s
F:\4glte\Evo4GLTERoot2>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
woo thank you for your help! looks like after i switched usb ports (both are 2.0) it stopped with the data failure and it seems to be s-off. so how should i update the software on it now? can I just flash a rom? I really need to flash a new rom/update it because the person who owned it before me somehow delete alot of stuff and left a partition of trash that wasn't delete when the guy sold it to me and some things don't work right.(IE sound as in ringtone and music doesn't work) but it vibrates and it seems to work on the sprint network just fine and I can text and call and hear people just fine.
Kannz2 said:
woo thank you for your help! looks like after i switched usb ports (both are 2.0) it stopped with the data failure and it seems to be s-off. so how should i update the software on it now? can I just flash a rom? I really need to flash a new rom/update it because the person who owned it before me somehow delete alot of stuff and left a partition of trash that wasn't delete when the guy sold it to me and some things don't work right.(IE sound as in ringtone and music doesn't work) but it vibrates and it seems to work on the sprint network just fine and I can text and call and hear people just fine.
Click to expand...
Click to collapse
Honestly now that you're S-off I would consider running the RUU for the Android 4.3 update. Click the top link in my sig and read the RUU section, which includes instructions on how to install the RUU. The link to the 4.3 update can be found at the bottom of the first post.
the one that says 4.13.651.4 RUU or is it the second to the bottom on the androidruu link?
looks like it updated it to 4.3 thank you for the link and for having all that stuff in one spot! ^^ what should I do now? can I installed a rom now? I dont need to update it anymore right?
could I get some help finding a usable rom? none of the ones ive downloaded want to flash they keep saying updater failed.. :/ i keep getting error executing updater binary in zip when installing rom.
Try V20 of this ROM:
http://forum.xda-developers.com/showthread.php?t=2528953
would that rom work with this kernel? http://forum.xda-developers.com/showthread.php?t=2181243 or this one? http://forum.xda-developers.com/showthread.php?t=2075542
No & no. There are no custom kernels for 4.3 for the EVO LTE.
dang owells thanks a bunch for the working rom. ^^ looks like the sound somehow doesn't work at all even with the fresh rom install. I guess the person who sold it to me ripped me off.. at least the sound works through the headphones and everything else works okay..you know any really good roms I can try out or is it limited for roms aswell? also the airplane mode widget is kinda weird in v20 in that its not actually a widget its just a shortcut to the settings. :,(
EDIT:
um would you happen to know the version of rom that they changed the airplane mode an if I can go back to it without messing up the phone? is seems a minor annoyance to some but it is much less annoying to toggle a widget than constantly going in and out of the settings. thanks for all the help.
I just got a fresh Fire HD 7 with 4.1.1, and updated it first to 4.5.3, and then to 5.2.2u2 with 5.2.0 bootloaders. While doing so, I kept track of the state of all the internal partitions that the updates do not seemingly touch (see this post for partitions http://forum.xda-developers.com/fire-hd/help/internal-memory-structure-hidden-t3122246 )
I've been using a simple script pasted from adb window on the PC side (needs root access):
Code:
adb shell
su
dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/
I can now compare 2 different Fires (old & new), and also the new Fire on the path from 4.1.1 to 4.5.3 to 5.2.0
Between the 2 different Fires, the only partition that has the same md5 is :
72fe4bd35179bc299674c781033ae1f7 10_misc.img
The other dark partitions differ between the 2 Fires (pro_info, pmt, kb, dkb)
Now, on the new Fire, partition that always changes between boots is :
8c72758dff50208f74b7bbc12725e46a 11_persisbackup.img
(so this is probably the boot counter lives and so on)
Finally, when the new Fire went from 4.1.1 to 4.5.3, (pro_info, pmt, kb, dkb) all stayed the same. But when I updated it to 5.2.0 bootloaders, dkb changed md5. The other 3 are still the same.
It'd be nice to run this script on a Fire with 5.2.2u2 bootloaders, and see if persisbackup is the same.
It could be possible to replace some of these dark partitions, and convert the Fire into an "unbricking" state.
Just to confirm: One can copy your whole script and paste it into the CMD window. It runs and doesn't do anything to the Fire HD. It just gets info that can help you, right? Whoever does this can drag the mouse over all the output to select it and hit ENTER to copy to clipboard, then paste it into a post for you.
I ask because my guide doesn't install the 5.2.0 bootloaders, so anyone who used it in the last month or so will have 5.2.2.u2 bootloaders. If no one else jumps in, perhaps @comapro or @benyaki or @sunilzs would have the time to run it for you.
If time permits tomorrow, I'll run that for you. (And if I remember!)
benyaki said:
If time permits tomorrow, I'll run that for you. (And if I remember!)
Click to expand...
Click to collapse
Here you go. Hope I did it correctly. If you need anything else, let me know.
Code:
C:\adb>adb shell
su
dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/[email protected]:/ $ su
dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/[email protected]:/ # dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
256+0 records in
256+0 records out
131072 bytes transferred in 0.105 secs (1248304 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
8192+0 records in
8192+0 records out
4194304 bytes transferred in 1.357 secs (3090865 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
10240+0 records in
10240+0 records out
5242880 bytes transferred in 2.069 secs (2534016 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
10240+0 records in
10240+0 records out
5242880 bytes transferred in 1.930 secs (2716518 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.128 secs (4096000 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 2.146 secs (3908950 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 2.113 secs (3969999 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.323 secs (3246365 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.265 secs (3956890 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.131 secs (4002198 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 4.256 secs (3942015 bytes/sec)
[email protected]:/ # cd /sdcard/
[email protected]:/sdcard # md5 *.img
40ab8a444a6bb38a77c8b023c8c28498 01_pro_info.img
976b7613ac6ccd0f8221b5dc13d01676 02_pmt.img
a25016f54a524f93e0c1225539273404 03_tee1.img
eb83b62828a361f33c6ed0ac62c872e7 04_tee2.img
233387047f6eb2e5e9f760cfc3adb5c7 05_uboot.img
e9a0260c940a03510662c74ee269c72e 06_boot.img
7082205b20052ae93c9215460de8f891 07_recovery.img
96b0de56e2e022e07e6dbaa0df49fcae 08_kb.img
32dadf8d79d0749dd054b11bd34051bf 09_dkb.img
72fe4bd35179bc299674c781033ae1f7 10_misc.img
ef16264f4b03b8879441e49478587528 11_persisbackup.img
[email protected]:/sdcard # rm *.img
[email protected]:/sdcard # cd /sdcard/
[email protected]:/sdcard #
benyaki said:
Here you go. Hope I did it correctly. If you need anything else, let me know.
Code:
[email protected]:/sdcard # md5 *.img
40ab8a444a6bb38a77c8b023c8c28498 01_pro_info.img
976b7613ac6ccd0f8221b5dc13d01676 02_pmt.img
a25016f54a524f93e0c1225539273404 03_tee1.img
eb83b62828a361f33c6ed0ac62c872e7 04_tee2.img
233387047f6eb2e5e9f760cfc3adb5c7 05_uboot.img
e9a0260c940a03510662c74ee269c72e 06_boot.img
7082205b20052ae93c9215460de8f891 07_recovery.img
96b0de56e2e022e07e6dbaa0df49fcae 08_kb.img
32dadf8d79d0749dd054b11bd34051bf 09_dkb.img
72fe4bd35179bc299674c781033ae1f7 10_misc.img
ef16264f4b03b8879441e49478587528 11_persisbackup.img
[email protected]:/sdcard # rm *.img
[email protected]:/sdcard # cd /sdcard/
[email protected]:/sdcard #
Click to expand...
Click to collapse
I think the issue is pretty tough. KB and DKB look like candidates to have clues for bricking. Most of "dark" partitions are non-trivially different between the 2 Fires I have, so overwriting them with different copies is probably not advisable
Actually, what would really help is to run md5 before running 5.2.2u2 bootloaders for the 1st time, and then after to see if it's just DKB that changed. One could back up these partitions before playing with the device, so if 5.2.2u2 bootloaders get accidentally loaded, there could be a way to go back.
Fire 7 2015 has similar bricking phenomenon (5.0.1 to 5.1.1 transition). So it might be safer to attempt to explore it with Fire 2015. One just captures all the partitions under 5.0.1, loads up the 5.1.1 bootloaders, captures all the partitions again. Then the 5.1.1 bootloaders and the relevant partitions (those that changed) is overwritten by 5.0.1 copies, to see if that allows 5.0.1 to boot again. If not, at least those Fires are still under warranty.
{
"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"
}
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
THIS WILL NOT WORK ON AMAZFIT PACE, VERGE OR STRATOS
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please make sure you read and understand everything written in the post before flashing it! YOU are choosing to make these modifications and must be sure of what it does.
Click to expand...
Click to collapse
Only for unlocked Bootloader
Supported devices: A1928 (Chinese) and A1929 (English)
Property installed ADB and Fastboot drivers as system wide
Watch battery +40% (50% recommended)
Click to expand...
Click to collapse
For anyone interested on installing Stock/Original Chinese Firmware
Click to expand...
Click to collapse
OTA updates
Click to expand...
Click to collapse
@Neur_User for STRATOSfied Rom and other stuff
@Cracklydisc for original script and other stuff
@1immortal for his support
@Jaz, contributors and collaborators in Telegram group.
Click to expand...
Click to collapse
1. Connect the watch to your PC
2. Unzip the the folder
3. Run flash_US.bat file for English interface (Don't do it as Administrator since is known to cause issues).
4. Wait to the end of the process and don't touch anything.
Installation output
*************************************************************
Stratos 3 CN 4.0.13.0 Stock Firmware Installer by Saratoga
*************************************************************
0. Restarting adb server
***************************
**********************************
1. Connect the watch to the PC
**********************************
**********************************
2. Rebooting to Fastboot mode
**********************************
******************************
3. Checking the connection
******************************
*******************************
4. Booting modded recovery
*******************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.450s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.678s
***************************************
5. Waiting for connection in Recovery
***************************************
******************
6. Copying files
******************
boot.img: 1 file pushed. 7.1 MB/s (9437184 bytes in 1.264s)
system.img.gz: 1 file pushed. 5.0 MB/s (438606404 bytes in 84.087s)
md5s.txt: 1 file pushed. 0.0 MB/s (91 bytes in 0.003s)
flash_rom.sh: 1 file pushed. 0.1 MB/s (458 bytes in 0.006s)
**************************
7. Firmware installation
**************************
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 1.836843 seconds, 4.9MB/s
Flashing system.img
287744+0 records in
287744+0 records out
1178599424 bytes (1.1GB) copied, 156.970842 seconds, 7.2MB/s
Finished
*******************
8. Removing files
*******************
**************
9. Rebooting
**************
**********************************
10. Changing language to Chinese
**********************************
****************************************************
Stock Recovery and Bootloader installation process
****************************************************
********************************
11. Rebooting to Fastboot mode
********************************
****************************
12. Booting temporal root
****************************
< waiting for any device >
Downloading 'boot.img' OKAY [ 0.368s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.572s
*******************
13. Copying files
*******************
install_recovery.sh: 1 file pushed. 0.1 MB/s (687 bytes in 0.009s)
recovery.img: 1 file pushed. 1.6 MB/s (16777216 bytes in 10.082s)
u-boot-with-spl-mbr-gpt.bin: 1 file pushed. 2.2 MB/s (894764 bytes in 0.387s)
*****************************
14. Flashing Stock recovery
*****************************
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 1.908566 seconds, 8.4MB/s
Done. OTA updates should now work.
*************************
15. Flashing Bootloader
*************************
1747+1 records in
1747+1 records out
894764 bytes (873.8KB) copied, 0.695597 seconds, 1.2MB/s
*******************
16. Removing files
*******************
***************
17. Rebooting
***************
************
18. Finish
************
Presione una tecla para continuar . . .
Click to expand...
Click to collapse
VERY IMPORTANT:
Don't do a factory reset in fastboot or you will brick the watch. Just run FCT_RST_STOCK.bat or use these commands instead.
Method 1:
Code:
adb reboot wipe
Method 2 (Only if watch is fully booted and you have root):
Code:
adb shell am broadcast -a android.intent.action.MASTER_CLEAR
Click to expand...
Click to collapse
Latest version
Stock CN/Chinese 4.0.22.0 Firmware Installer with OTA updates (Bugged Ultra Mode strings)
Click to expand...
Click to collapse
Previous versions
Stock CN/Chinese 4.0.19.5 Firmware Installer with OTA updates
Stock CN/Chinese 4.0.13.0 Firmware Installer with OTA updates
Click to expand...
Click to collapse
If you like my work you can buy me a beer here
Click to expand...
Click to collapse
Manual installation method
Manual installation method
Introduction
Here I will explain how to install the firmware using a command window or any other terminal.
The requirements are the ones stated in first post.
On your terminal, go to the path where all the files were unzipped, or if you are running a Windows OS, just run terminal_cmd.bat and you are good to go.
OTA Installation
Download OTA installer from Post #1 and if you are running a Windows PC, run terminal_cmd.bat, or any other command/terminal window on your PC in the root of the unzipped folder.
Copy the update to the watch
Code:
[COLOR="Blue"]adb push update.zip /sdcard
[/COLOR]
And launch the update
Code:
[COLOR="blue"]adb reboot update[/COLOR]
Wait to the end of the update, and when the watch reboots delete the update file
Code:
[COLOR="blue"]adb shell rm /sdcard/update.zip[/COLOR]
Firmware installation
On your terminal, go to the path where all the Firmware files were unzipped.
You can copy and paste all needed commands.
1. Connect the watch to the PC and check the connection with the watch
Code:
[COLOR="Blue"]adb devices[/COLOR]
Output (or similar)
Code:
List of devices attached
9dee1d33 device
2. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
3. When the watch reboots in fastboot mode, check the connection with the watch
Code:
[COLOR="blue"]fastboot devices[/COLOR]
Output (or similar)
Code:
0123456789 fastboot
4. Boot the modded recovery
Code:
[COLOR="blue"]fastboot boot recovery_mod.img[/COLOR]
Output (or similar)
Code:
Downloading 'boot.img' OKAY [ 0.450s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.678s
5. Wait until you get a triangle with an exclamation mark in your watch
6. Copy the files to the watch (it may take up to a minute)
Code:
[COLOR="blue"]adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/[/COLOR]
Output (or similar)
Code:
boot.img: 1 file pushed. 7.1 MB/s (9437184 bytes in 1.264s)
system.img.gz: 1 file pushed. 5.0 MB/s (438606404 bytes in 84.087s)
md5s.txt: 1 file pushed. 0.0 MB/s (91 bytes in 0.003s)
flash_rom.sh: 1 file pushed. 0.1 MB/s (458 bytes in 0.006s)
7. Start Firmware installation (it may take up to 4 minutes)
Code:
[COLOR="blue"]adb shell sh /data/media/0/flash_rom.sh[/COLOR]
Output (or similar)
Code:
Validating images
boot.img: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 1.836843 seconds, 4.9MB/s
Flashing system.img
287744+0 records in
287744+0 records out
1178599424 bytes (1.1GB) copied, 156.970842 seconds, 7.2MB/s
Finished
8. We have already installed the firmware, now delete installation files form the watch
Code:
[COLOR="blue"]adb shell rm /data/media/0/boot.img
adb shell rm /data/media/0/system.img.gz
adb shell rm /data/media/0/md5s.txt
adb shell rm /data/media/0/flash_rom.sh[/COLOR]
9. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
10. When the splash screen is passed and the bootanimation starts, set your watch to English language
Code:
[COLOR="blue"]adb shell setprop persist.sys.language zh
adb shell setprop persist.sys.country CN[/COLOR]
Stock Recovery and Bootloader installation process
11. Reboot in fastboot mode
Code:
[COLOR="blue"]adb shell reboot bootloader[/COLOR]
12. Boot temporal root
Code:
[COLOR="blue"]fastboot boot boot-CN-adb-root.img[/COLOR]
Output (or similar)
Code:
Downloading 'boot.img' OKAY [ 0.368s]
booting FAILED (status read failed (Too many links))
Finished. Total time: 1.572s
13. Copy stock Recovery and Bootloader files to the watch
Code:
[COLOR="blue"]adb push install_recovery.sh /data/media/0/
adb push recovery.img /data/media/0/
adb push u-boot-with-spl-mbr-gpt.bin /data/media/0/[/COLOR]
Output (or similar)
Code:
install_recovery.sh: 1 file pushed. 0.1 MB/s (687 bytes in 0.009s)
recovery.img: 1 file pushed. 1.6 MB/s (16777216 bytes in 10.082s)
u-boot-with-spl-mbr-gpt.bin: 1 file pushed. 2.2 MB/s (894764 bytes in 0.387s)
14. Run the recovery installation script
Code:
[COLOR="blue"]adb shell cd /data/media/0/; sh install_recovery.sh[/COLOR]
Output (or similar)
Code:
============= STOCK Installer ===============
Flashing recovery...
4096+0 records in
4096+0 records out
16777216 bytes (16.0MB) copied, 1.908566 seconds, 8.4MB/s
Done. OTA updates should now work.
15. Flash Bootloader
Code:
[COLOR="blue"]adb shell busybox dd if=/data/media/0/u-boot-with-spl-mbr-gpt.bin of=/dev/block/mmcblk0[/COLOR]
Output (or similar)
Code:
1747+1 records in
1747+1 records out
894764 bytes (873.8KB) copied, 0.695597 seconds, 1.2MB/s
16 . Delete stock recovery and Bootloader installation files
Code:
[COLOR="blue"]adb shell rm /data/media/0/install_recovery.sh
adb shell rm /data/media/0/recovery.img
adb shell rm /data/media/0/u-boot-with-spl-mbr-gpt.bin
[/COLOR]
17. Reboot the watch
Code:
[COLOR="blue"]adb reboot[/COLOR]
18. Finish.
Go to Amazfit app and update to latest version.
Some extra useful commands
Factory Reset
VERY IMPORTANT:
Don't do a factory reset in fastboot or you will brick the watch
You can factory reset your watch by:
Code:
[COLOR="Blue"]adb reboot wipe[/COLOR]
When it's done, the watch will turn off.
Launch pairing QR code
You can use:
Code:
[COLOR="Blue"]adb shell am start -n com.huami.watch.setupwizard/.InitPairQRActivity[/COLOR]
Reboot into Ultra mode
You can reboot into Ultra mode by:
Code:
[COLOR="blue"]adb reboot mcu[/COLOR]
Mio1
Mio2
Thanks for your job !
Multi language (french) ?
Hi can you share multi language had which languages
Can someone confirm if Chinese Rom has English included by default?
Sent from my VOG-L29 using Tapatalk
tipu2185 said:
Can someone confirm if Chinese Rom has English included by default?
Sent from my VOG-L29 using Tapatalk
Click to expand...
Click to collapse
Only Chinese. However, you can change language to English using adb commands but you may face some bugs probably.
If you want official English language and others, check Stock/US/International thread for Stratos 3.
where can I find the update.zip?
thanks