Hi!
I'm trying to root my Huawei MediaPad T1-701w but am in need of help... I've tried out nearly every 'one click root' app or PC program out there, but every single one fails. Huawei has hardened the kernel/android version and patched all known exploits to date (October 2016). The issue is that the variant of the MediaTab I have is pretty uncommon (T1-701w) so there is not a lot to find about it.
{
"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"
}
However, I did find that the iovyroot might be able to root it, see https://forum.xda-developers.com/general/xda-assist/huawei-t1-701u-write-protection-t3418836 , but the current pre-compiled version of iovyroot is not compatible with my tablet (it needs new offsets).
I also tried downgrading, but I don't quite understand how to do so. I found one older ROM for my Mediatab variant which might contain more exploits according to 4PDA.ru, but how do I downgrade? The 'dload' method does not work. Also before downgrading, I want to dump my current ROM, which requires root, right?
Can anyone help me out here please?
Thank you!
If you have the most recent stock ROM of your device (oct. 2016), extract the file "boot.img" out of (UPDATE.APP) and put it here, and i'll send you back the rooted one, then follow the steps in the following thread to make it works:
https://forum.xda-developers.com/huawei-mediapad/general/root-root-mediapad-t1-10-t1-a21l-t3601136
=====
Here's the link for the stock ROM:
http://consumer.huawei.com/nl-en/support/downloads/detail/index.htm?id=80385
mann1 said:
If you have the most recent stock ROM of your device (oct. 2016), extract the file "boot.img" out of (UPDATE.APP) and put it here, and i'll send you back the rooted one, then follow the steps in the following thread to make it works:
https://forum.xda-developers.com/huawei-mediapad/general/root-root-mediapad-t1-10-t1-a21l-t3601136
=====
Here's the link for the stock ROM:
http://consumer.huawei.com/nl-en/support/downloads/detail/index.htm?id=80385
Click to expand...
Click to collapse
Many thanks for your reply! Please find the boot.img from the UPDATE.app of my ROM with header file (?) here: http://data.freek.ws/public/huawei_t1-701w/V100R001C232B009CUSTC232D001/
(It was too large to attach to this post, sorry).
Is PhilZ Touch 6 Recovery compatible with my tablet?
Many many thanks!! Kind regards.
Well, download the following zip file here
Both rooted and stock imgs are included.
I do not know if PhilZ recovery will work with your device or not, i don't have the same model.
Give it a try, you don't need full functions anyway , just the "install zip" one, BUT keep the stock "recovery.img" before you do, so you can go back to it in case philz didn't work.
Also you can try the CWM recovery fromhere, both ways are risky, but nothing serious i guess, you can go back to the stock recovery at any moment.
Tell me the results pls
GOOD LUCK
mann1 said:
Well, download the following zip file here
Both rooted and stock imgs are included.
I do not know if PhilZ recovery will work with your device or not, i don't have the same model.
Give it a try, you don't need full functions anyway , just the "install zip" one, BUT keep the stock "recovery.img" before you do, so you can go back to it in case philz didn't work.
Also you can try the CWM recovery fromhere, both ways are risky, but nothing serious i guess, you can go back to the stock recovery at any moment.
Tell me the results pls
GOOD LUCK
Click to expand...
Click to collapse
Many many thanks for your quick reply and effort
I manage dto flash the rooted boot.img without any problems, great !
Howevever, in your tutorial you write that I need to flash SuperSU in order to activate the rooting. But how can I flash it if I don't have custom recovery? PhilZ recovery sadly does not work, I tried
Stock recovery does not allow me to flash super su.
Many thanks
Kind regards.
You're very welcome
Try the following:
use command prompet and type:
adb root
if it works w/o any errors type:
adb shell
a new cm window will pop up with your device shell
[email protected]:/ $
type:
su
if the root works, the shell is gonna be:
[email protected]:/ #
If it works, download the superSu.apk file NOT the zip, restart the device,
then put SuperSU options "Default access: Grant" and check "Enable su during boot" then restart
mann1 said:
You're very welcome
Try the following:
use command prompet and type:
adb root
if it works w/o any errors type:
adb shell
a new cm window will pop up with your device shell
[email protected]:/ $
type:
su
if the root works, the shell is gonna be:
[email protected]:/ #
If it works, download the superSu.apk file NOT the zip, restart the device,
then put SuperSU options "Default access: Grant" and check "Enable su during boot" then restart
Click to expand...
Click to collapse
Once again thanks for your reply.
Hmm, the root doesnt seem to be working:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
U5MDU17327001608 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb root
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
/system/bin/sh: su: not found
But I did flash your rooted_boot.img.. What should I do?
Nope, it works very well, if it doesn't you would see an error after you type "adb root"
Just try to install superSU.apk directly like we do with any apk, then restart.
OR
If it didn't work, try this:
=========
adb devices
adb root
adb shell "mount -o remount,rw /system"
adb push su /system/bin/su
adb push superuser.apk /system/app
adb reboot
=========
put the superSu in the same folder with adb
mann1 said:
Nope, it works very well, if it doesn't you would see an error after you type "adb root"
Just try to install superSU.apk directly like we do with any apk, then restart.
OR
If it didn't work, try this:
=========
adb devices
adb root
adb shell "mount -o remount,rw /system"
adb push su /system/bin/su
adb push superuser.apk /system/app
adb reboot
=========
put the superSu in the same folder with adb
Click to expand...
Click to collapse
Thanks again for the help!
My tablet is a tough one I think. It says 'mount: Operation not permited'.
Any ideas?
Yep, your tablet comes with Spreadtrum SC7731G, and it's not easy to find a custom recovery for these chipsets.
But i'm sure the device is already rooted now, we just need a working custom recovery to flash the superSU, so pls keep the rooted boot.
===
I've googled some custom recoveries that are compatible with SC7731, so give them a try:
https://drive.google.com/file/d/0B8vhq1nCgRGdR3VmbE1RSWNRSjA/view
this is number 9 recovery img in this thread:
https://forum.xda-developers.com/showthread.php?t=2527663
=====
and here's another one:
http://www.mediafire.com/file/1j4uj3c4vk5rtcw/recovery.img
=====
BE CAREFUL,these ones are not tested on your device, so test them very carefully, one of them may work but with cranky touch function, try to use it just to flash the SuperSu ZIP file NOT apk.
mann1 said:
Yep, your tablet comes with Spreadtrum SC7731G, and it's not easy to find a custom recovery for these chipsets.
But i'm sure the device is already rooted now, we just need a working custom recovery to flash the superSU, so pls keep the rooted boot.
===
I've googled some custom recoveries that are compatible with SC7731, so give them a try:
https://drive.google.com/file/d/0B8vhq1nCgRGdR3VmbE1RSWNRSjA/view
this is number 9 recovery img in this thread:
https://forum.xda-developers.com/showthread.php?t=2527663
=====
and here's another one:
http://www.mediafire.com/file/1j4uj3c4vk5rtcw/recovery.img
=====
BE CAREFUL,these ones are not tested on your device, so test them very carefully, one of them may work but with cranky touch function, try to use it just to flash the SuperSu ZIP file NOT apk.
Click to expand...
Click to collapse
Thanks for your reply
Hmm, are you sure it's rooted? Because it keeps complaining about 'no permission' or is that caused due to incompatibility with my device?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.171s]
booting...
FAILED (remote: no permission)
finished. total time: 2.173s
Freekers1337 said:
Thanks for your reply
Hmm, are you sure it's rooted? Because it keeps complaining about 'no permission' or is that caused due to incompatibility with my device?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.171s]
booting...
FAILED (remote: no permission)
finished. total time: 2.173s
Click to expand...
Click to collapse
I guess it's compatibility issue.
1- flash the rooted boot
fastboot flash boot rooted_boot.img
===
2- flash one of the custom recoveries (don't boot them)
fastboot flash recovery recovery.img (use the right file name)
then restart
===
your device will start normally w/o any problem, there's no problem with the rooted boot.
then turn off the tablet and get into the recovery mode by (Vol. down + power buttons)
do not use the "adb reboot-bootloader" cm.
===
now the the recovery might work, and if it didn't, you will face the bootloader screen mode, type:
fastboot reboot
to restart your device, and flash the 2nd recovery img.
So sorry i don't have your device to try that myself.
mann1 said:
I guess it's compatibility issue.
1- flash the rooted boot
fastboot flash boot rooted_boot.img
===
2- flash one of the custom recoveries (don't boot them)
fastboot flash recovery recovery.img (use the right file name)
then restart
===
your device will start normally w/o any problem, there's no problem with the rooted boot.
then turn off the tablet and get into the recovery mode by (Vol. down + power buttons)
do not use the "adb reboot-bootloader" cm.
===
now the the recovery might work, and if it didn't, you will face the bootloader screen mode, type:
fastboot reboot
to restart your device, and flash the 2nd recovery img.
So sorry i don't have your device to try that myself.
Click to expand...
Click to collapse
Thanks for sticking with me
I tried both custom recoveries you sent me, but both fail with error: 'FAILED (remote: image is not a boot image)'.
I also tried creating my own recovery using these two tutorials: https://www.youtube.com/watch?v=w1Ap2YwmGVk & https://www.youtube.com/watch?v=hwMFBuCY-5k but I get the same error (image is not a boot image).
Grrrr, do you still have any ideas ?
Kind regards!
YVW, it's ok, no problem at all.
Pls do not use the command
fastboot boot recovery *.img to try the custom recovery, flash it directly with
fastboot flash recovery filename.img
usually custom recoveries even if they work fine give the same error when u try them with the "boot" command
mann1 said:
YVW, it's ok, no problem at all.
Pls do not use the command
fastboot boot recovery *.img to try the custom recovery, flash it directly with
fastboot flash recovery filename.img
usually custom recoveries even if they work fine give the same error when u try them with the "boot" command
Click to expand...
Click to collapse
I did flash it directly using: fastboot flash recovery xxxxx.img . That's when I got the 'image is not a boot image image' error
Well, we will try easy step, flash the rooted boot img then restart the device, then go to google play, and use the online install function to get superSU.apk, do not download it, just install it directly from the site
mann1 said:
Well, we will try easy step, flash the rooted boot img then restart the device, then go to google play, and use the online install function to get superSU.apk, do not download it, just install it directly from the site
Click to expand...
Click to collapse
I'm sorry, I can't find the online install function. I went to Google Play and installed SuperSU but as soon as it opens it says Device not rooter. After that it says no SU binary found and automatically closes..
Freekers1337 said:
I'm sorry, I can't find the online install function. I went to Google Play and installed SuperSU but as soon as it opens it says Device not rooter. After that it says no SU binary found and automatically closes..
Click to expand...
Click to collapse
It's ok, don't give up
Right now i run out of ideas, but give me some time to get my unrooted stock ROM back, to start the race toward rooting w/o custom recovery.
mann1 said:
It's ok, don't give up
Right now i run out of ideas, but give me some time to get my unrooted stock ROM back, to start the race toward rooting w/o custom recovery.
Click to expand...
Click to collapse
OK I'll wait for your reply.
Freekers1337 said:
OK I'll wait for your reply.
Click to expand...
Click to collapse
Hi
After long journey, i could say I've got an effective way to root your device and mine too w/o custom recovery, it works fine for me, hope it will be the same for you.
First you need to download the following files:
1- New rooted_boot img from here
2- Compressed folder mann1.zip from here
3- SuperSu.apk file from here
====
Now lets start,
1- Unzip the rooted img then flash it, (be careful it's not tested):
use the flash command NOT boot
Code:
fastboot flash boot rooted_boot.img
===
2- Unzip the file "mann1.zip" to get folder "mann1" then copy it directly into your device internal storage NOT the SD card. Put the the whole folder not the files inside.
===
3- Put SupeSU.apk into your SD card
===
If the rooted boot worked fine, restart your device in the normal mode (NOT the recovery or bootloader), and type the following commands one by one:
Code:
adb devices
adb root
adb shell
[I][COLOR="Red"]Now you supposed to see your root like that[/COLOR][/I]
[COLOR="Blue"][email protected]:/ #[/COLOR]
[COLOR="Red"]complete the commands in the shell:[/COLOR]
mount -o rw,remount /system
cat sdcard/mann1/busybox > /system/bin/busybox
cat /sdcard/mann1/su > /system/xbin/su
cat /sdcard/mann1/su > /system/xbin/daemonsu
cat /sdcard/mann1/su > /system/xbin/sugote
cat /system/bin/sh > /system/xbin/sugote-mksh
chown 0.1000 /system/bin/busybox
chmod 0755 /system/bin/busybox
chown 0.0 /system/xbin/su
chmod 0755 /system/xbin/su
chown 0.0 /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chown 0.0 /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chown 0.0 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d
pm install /sdcard/mann1/superuser.apk
am start -a android.intent.action.MAIN -n
eu.chainfire.supersu/.MainActivity >/dev/null
reboot
If everything run smoothly after rebooting you will find the SuperSu icon installed.
Do NOT run it now
Before that go to your SD card and install SuperSU.apk, from the device not via pc, then restart.
Now your device should be completely rooted , if SUperSu asked to updated via google, reinstall it OR let it updates by google play site.
Related
Mod Edit: Unstickied, placed link in wiki:http://forum.xda-developers.com/wiki/index.php?title=Nexus_One Thanks
This is an alternative approach of rooting the Nexus without touching the bootloader.
-no downgrade neccessary
-no battery modification neccessary
-no messing around with SD card slot
-you don't even have to open your phone...
Working and confirmed for ALL ROMs, including European Vodafone EPF30/FRF91, Korean FRF91, AT&T/T-Mo Stock including FRF91
-------
Credits:
-------
- The Android Exploid Crew:
http://c-skills.blogspot.com/2010/07/android-trickery.html
- Amon_RA
- cyanogen
-------
Notes:
-------
- The exploit wasn't found by me (see credits), I just implemented it as a proof of concept for the Nexus One
- Basically this method should work on all currently known ROM versions.
- I tested it on EPF30, Korean FRF91, Vodafone FRF91, US Stock FRF91.
- As usual when doing this kind of stuff: DO THIS AT YOUR OWN RISK.
- It could even work on other Android devices as long as their system partition is at
/dev/block/mtdblock3/ with yaffs2 file system and there is still some space left on the system partition (without any changes).
-------
Prerequisites:
-------
- Locked Nexus One
- Latest Android SDK incl. USB drivers
- Working ADB
- The file "freenexus.zip"
edit:
get it here:
http://multiupload.com/MVT98F5HBY
or
http://dl.dropbox.com/u/1327667/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
-------
Step-by-step guide:
-------
1. install android sdk & USB drivers
2. extract the content of the zip file into the tools directory of SDK (i.e. \android-sdk-windows\tools)
-> For all Newbies: Take care that you extract the files directly to the tools folder and don't create a new subdirectory freenexus within tools!!! If you did, delete the folder and extract again!!! Check twice that there is no FOLDER freenexus in your tools directory before you continue!!!
3. open a command prompt (Windows: Start, Run, "cmd", OK; Linux: Terminal)
4. change to SDK tools directory (i.e. cd \android-sdk-windows\tools)
5. connect Nexus to USB and check if debugging mode is activated
(Settings/Application/Development/USB Debugging)
6. run "adb devices" in shell and see if there is a device listed. if not back to step 5 or reinstall USB-drivers
7a. for Windows: run "freenexus.bat" in command shell (this copies the neccessary files to /data/local/tmp)
7b. for Linux or manual installation: run the following commands
Code:
adb push freenexus /data/local/tmp/freenexus
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb push su /data/local/tmp/su
adb push busybox /data/local/tmp/busybox
adb shell chmod 755 /data/local/tmp/freenexus
adb shell chmod 755 /data/local/tmp/busybox
8. run the following commands:
Code:
adb shell
(you should see a "$" prompt now)
cd /data/local/tmp
9. on your phone go to a screen where you can easily toggle wifi (widget or settings/wireless)
10. be prepared to toggle wifi immediately after you execute the next step
11. run
Code:
./freenexus
12. toggle wifi on
13. you should see something like that:
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by ak for HTC Nexus One
[+] Using basedir=/sqlite_stmt_journals, path=/data/local/tmp/freenexus
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
13b) if you get "permission denied" error, you have most likely not followed the big red newbie hint after point 2. check this by entering "ls -l", if you see a "drwxr-xr-x" and not "-rwxr-xr-x" in front of the line where freenexus is listed you did not follow properly. Search the posts in the thread on how to correct this.
14. run
Code:
rootshell
15. if you succeeded you will be asked for a password, if not try again from step 10
16. enter the password "freenexus"
17. now you should see a "#" as a prompt -> you are root now
18. run the following commands:
Code:
./busybox cp busybox /system/bin
chmod 4755 /system/bin/busybox
busybox cp Superuser.apk /system/app
busybox cp su /system/bin
chmod 4755 /system/bin/su
rm /system/bin/rootshell
exit
exit
19. Check if you keep root rights:
Code:
adb shell
su
20. after you executed the su command the Superuser app on your device should ask you for allowance
21. you should see the "#" prompt again, if you didn't get that try su again
22. done
-------
Comments:
-------
- General
If you are not planning to wipe your data partition (what you probably will do when installing CM6 first time) you should think about deleting all the temp files still lying in /data/local/tmp (for safety reasons and to have more space on /data):
Code:
adb shell
cd /data/local/tmp
rm busybox
rm su
rm Superuser.apk
rm freenexus
rm flash_image (will only exist if you executed the steps below in recovery section)
- Installation of Custom Recovery
If you only want root rights you are done here. If you want to install custom ROMs you have to install
a custom recovery first. Easiest way would be to download "ROM Manager" from the market. There are plenty of tutorials on how to install custom recovery/ROM at xda.
Edit: It is safer to install the recovery manually. In this case or for those of you running into problems with installing custom recovery with ROM Manager (doesn't stick) you can continue with
these steps (without remount of system partition, now tested successfully):
1) Download recovery-RA-nexus-v1.7.0.1.img to the root directory of your SD-Card
- Note: UnMount your SD-Card after copying these files, but keep your phone plugged in
- or don't mount SD-Card at all and push the file via adb to /sdcard
2) Save file "flash_image" to sdk tools directory:
3) In your terminal run
Code:
adb push flash_image /data/local/tmp/flash_image
adb shell
su
- At this point, it will hang until you choose "Allow" on your phone with the SuperUser app pop-up
- $ should now be replaced with #
5) run the following commands:
Code:
[COLOR="Red"]mount -o rw,remount /dev/block/mtdblock3 /system[/COLOR]
cd /data/local/tmp
chmod 755 flash_image
[COLOR="Red"]./flash_image recovery /sdcard/recovery-RA-nexus-v1.7.0.1.img[/COLOR]
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
(and if everything worked fine:)
rm flash_image
Alternatively you can continue with step 9 and then steps 16-24 from the old rooting method tutorial
to manually install Amon_RA's recovery. You will also need the file flash_image for that (link taken from HBOOT thread).
- HBOOT
If you rooted from a Korean Rom or have installed the latest Vodafone Rom via PASSIMG you probably have
HBOOT 0.35 which makes it currently difficult to install Cyanogenmod (there is an assertion failure in the install script, at least with CM6 RC1/2. Maybe future versions of CM6 will include HBOOT 0.35 in the script) or other custom ROMs. (You are still on 0.33 if you just installed the Vodafone OTA Update)
There is a tutorial to revert HBOOT here:
http://forum.xda-developers.com/showthread.php?t=726258
Instead of using the EPF30 image you can also use any other PASSIMG file (at least if it has HBOOT 0.33,
otherwise this step wouldn't make sense...)
Note that when flashing a PASSIMG with a different HBOOT version there is a reboot after the HBOOT has been flashed, then after reboot the PASSIMG will be loaded again and the rest of the image will be flashed.
To check HBOOT and Radio version: press and hold trackball while turning on the phone. To exit select Reboot with Vol+/- and press Power button.
Caution:
After you have reverted your HBOOT, you have lost your root rights and you are back on stock recovery.
But you can (or have to) repeat the above procedure to get root rights back.
Edit:
The downgrading also downgrades your radio!!! Before installing CM6 you have to flash a Froyo Radio!
Latest one can be found here:
http://forum.xda-developers.com/showthread.php?t=723839
-------
Troubleshooting:
-------
After trying to flash a custom ROM with ROM Manager one user wasn't able to boot the phone normally and also no longer able to boot to recovery. In this rare case try to download a compatible PASSIMG file:
For example EPF30 (Europe Vodafone 2.1)
http://shipped-roms.com/shipped/Pas...ogle_WWE_1.14.1700.1_EPF30_release_signed.zip
or FRF91 (Europe Vodafone 2.2):
http://shipped-roms.com/shipped/Pas...on_VF_2.15.151.5_R_FRF91_MFG_Shipment_ROM.zip (<-this one is currently a zip in zip. You have to extract it once to get the working PASSIMG.zip)
(Appropriate US-PASSIMGs can also be found on shipped-roms.com, most likely EPE76)
Rename the file to PASSIMG.zip (case sensitive, Windows users take care that the file isn't called PASSIMG.zip.zip hidden extension)
Copy it to main folder of SD card.
Boot phone into Bootloader mode (press and hold trackball when turning on the phone, until fastboot mode starts)
Select Bootloader mode by pressing power button.
The bootloader should then start to analyse the PASSIMG.zip and ask you afterwards to install it.
You're phone (not your SD) will be completely wiped after the procedure but should work again (and can be rooted again...)
sweet!! been waiting for this! will try it tomorrow as soon as i wake up! will report back then!
edit: i cant download freenexus.zip maybe use another hoster?
file section edited.
Great tutorial ! Waiting for some feedbacks
(file link doesn't work)
dolomiti7 said:
file section edited.
Click to expand...
Click to collapse
On the left I can see just an empty folder named "SmartDrive"
link doesn't work
dolomiti7 said:
-> after clicking on "Smartdrive Gastzugang starten" you might get an error message, but after klicking ok on the error message
you should be able to access the folder "nexus" on the left side of the window anyway
Click to expand...
Click to collapse
No way! Can't do anything even after i press ok on the error message
if you click on that there should be a subfolder "nexus" that should be clickable too. at least it works here... anyway. someone wants to upload the file to a hoster? rapidshare... contact me
for the early adaptors (will only work 10 times):
rapidshare.com/files/409266634/freenexus.zip
MD5: 947C20222056D7C070733E7FCF85CF15
multiple download sites!:
http://www.multiupload.com/MVT98F5HBY
or here:
http://dl.dropbox.com/u/1327667/freenexus.zip
thank you. added the link.
This worked flawlessly.
Massive thanks.
Hi, I have a Italian Vodafone Nexus One with FRF91, i have followed all the steps and now in my apps there is Superuser Permission with green light. It means that i have root rights? Can I install Cyanogen Mod now? Thanks, excuse my English.
Worked perfectly on a stock AT&T N1 with FRF91. Thanks!
Excellent tutorial step by step...great work!
Can i change the password at the end?
So once gaining root, I can flash a custom recovery with rom manager without braking/unlocking the boot loader?
@fc_themaster:
if the superuser app popped up at step 19/20 then you have root rights. you can try to install ROM Manager from the market and install a custom recovery with that porgram. it also needs root rights so superuser should pop up again at that point.
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
@jivemaster: yes, we can! just use ROM Manager from the market to install custom recovery.
dolomiti7 said:
@PSeeCO: you don't need to change a password. the password was only used for the temporary rootshell which you (hopefully) deletetd with the command "rm /system/bin/rootshell" in step 18. From that point on root rights are controlled via the Superuser app. If you install an already rooted custom ROM it is obsolete anyway.
Click to expand...
Click to collapse
Perfect, thank you so much!
C:\Users\Ryan>cd
C:\Users\Ryan
C:\Users\Ryan>cd\AndroidSDK\tools
C:\AndroidSDK\tools>adb devices
List of devices attached
HT02TL900527 device
C:\AndroidSDK\tools>adb shell flash_image recovery /sdcard/recov1.img
error opening /sdcard/recov1.img: No such file or directory
I keep getting this error, but the file is in the root. Any help much appreciated
Flash it via Better Terminal Emulator
Code:
$ su
# flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
Its for latest recovery .. if you flashing old one then change name .Also if you flashing the new recovery then Update.zip file is available flash it via recovery menu for more info see here: - [Recovery ROM] [15-August-2010] RA-hero-v1.7.0.1
The "official" CWM Recovery for LG Optimus L9 II (D605).
RELEASE v3 UPDATE
Changelog:
v3: Fixed problems with flashing gapps, Loki tool integration
v2: Added touchscreen swipe navigation, fixed fstab for proper kernel backup and recovery
V3 links:
Download from this link to flash from old CWM/Custom recovery:
d605_cwm_zf_v3.zip - 8.69 MB
Download from this link to flash without CWM/Custom recovery
d605_cwm_v3.zip - 8.53 MB
Old links:
v2:
flashable zip via CWM:
d605_zf_cwm_6_0_4_6_v2.zip - 7.56 MB
zip with manual install files:
d605_cwm_6_0_4_6_v2.zip - 7.40 MB
How to flash (you need adb on your PC):
1. Extract contents on your pc
2. Connect the phone with USB debugging ON (phone has to be rooted)
3. adb push loki_flash /data/local/tmp
4. adb push recovery.img /data/local/tmp
5. adb shell
6. $ su
7. # cd /data/local/tmp
8. # chmod 777 loki_flash
9. # ./loki_flash recovery recovery.img
10. # reboot recovery
Alternatively (to flash without adb directly from phone):
1. Extract contents on your PC
2. Copy loki_flash and recovery.img to you phone's SD card via MTP connection
3. Download and start Android Terminal Emulator from Play Store
4. From terminal emulator type:
$ su
5. Then type (assuming files from zip were copied to external SD card root) :
# cp /storage/external_SD/loki_flash /storage/external_SD/recovery.img /data/local/tmp
6. # cd /data/local/tmp
7. # chmod 777 loki_flash
8. # ./loki_flash recovery recovery.img
9. # reboot recovery
Done!
Varcain said:
The "official" CWM Recovery for LG Optimus L9 II (D605).
Link:
https://dl.dropboxusercontent.com/u/6714755/LG_D605/d605_cwm_6_0_4_6_v1.zip
How to flash (you need adb on your PC):
1. Extract contents on your pc
2. Connect the phone with USB debugging ON (phone has to be rooted)
3. adb push loki_flash /data/local/tmp
4. adb push recovery.lok /data/local/tmp
5. adb shell
6. $ su
7. # cd /data/local/tmp
8. # chmod 777 loki_flash
9. # ./loki_flash recovery recovery.lok
10. # reboot recovery
Alternatively (to flash without adb directly from phone):
1. Extract contents on your PC
2. Copy loki_flash and recovery.lok to you phone's SD card via MTP connection
3. Download and start Android Terminal Emulator from Play Store
4. From terminal emulator type:
$ su
5. Then type (assuming files from zip were copied to external SD card root) :
# cp /storage/external_SD/loki_flash /storage/external_SD/recovery.lok /data/local/tmp
6. # cd /data/local/tmp
7. # chmod 777 loki_flash
8. # ./loki_flash recovery recovery.lok
9. # reboot recovery
Done!
Click to expand...
Click to collapse
Good job !
hey, how to go to recovery at startup phone
lioko27 said:
hey, how to go to recovery at startup phone
Click to expand...
Click to collapse
On L9 1 combination is Volume down+home+power button.
Maybe L9 2 uses same combo?
It's tricky because LG engineers messed up timings. Anyways - technically it is done by booting with power + vol up combo pressed. The problem is when you press power button long enough the hardware reset will happen (this is where they messed up - hardware reset timer is too short). To enter recovery you have to actually practice D) to get it right.
If you reboot from a running system it's easy - just press vol up + power combo as soon as screen goes black and release quickly when white text about B&R appears, then just wait for recovery to complete booting.
When you do a cold boot (powering up device which was turned completely off) it's little harder because phone will tend to restart instead of going into recovery mode. You have to press power button first, release it, then wait 1-3 seconds and then press power + vol up so you get into B&R without restarting.
The important part is to release buttons when you get white text about B&R because if you hold them any longer the phone will restart.
Root?
Varcain said:
The "official" CWM Recovery for LG Optimus L9 II (D605).
Link:
https://dl.dropboxusercontent.com/u/6714755/LG_D605/d605_cwm_6_0_4_6_v1.zip
How to flash (you need adb on your PC):
......
$ su
.......
Click to expand...
Click to collapse
Do i need root?
cescom said:
Do i need root?
Click to expand...
Click to collapse
Yes
Sent from my LG-D605 using Tapatalk
http://forum.xda-developers.com/showthread.php?p=49983215
First flashable zip with CM 10 is now released, see the updated OP.
Hi all,
how to solve this? " [-] Failed to open aboot for reading. "
[email protected]:/data/local/tmp $ ls -l
ls -l
-rwxr-xr-x shell shell 814612 2013-11-10 07:09 busybox
-rwxrwxrwx root root 20088 2013-12-26 12:43 init.rc
-rwxrwxrwx shell shell 6376 2014-02-16 00:18 loki_flash
-rw-rw-rw- shell shell 7800832 2014-02-16 02:08 recovery.lok
[email protected]:/data/local/tmp $ ./loki_flash recovery recovery.lok
./loki_flash recovery recovery.lok
[+] loki_flash v2.0
[-] Failed to open aboot for reading.
1|[email protected]:/data/local/tmp $
you don't have root privileges in your console. Did you type "su"?
Varcain said:
you don't have root privileges in your console. Did you type "su"?
Click to expand...
Click to collapse
yeah i type "su"
i tried 2. method with success ... thx
after reboot recovery i have a opened android with a red triangle what does it mean?
like this
{
"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 is image from stock recovery, you didn't flash properly.
Ok i will retry after : )
what does the stock recovery do?
------------------------------------------------
all is working perfectly tanks
Varcain many times I tried urochomic recowery combination of keys and the only time I did which is a little embarrassing, it can be somehow improved?
---------- Post added at 07:54 PM ---------- Previous post was at 07:41 PM ----------
Junior Member
this use
http://forum.android.com.pl/f1016/cmw-v-6-0-4-5-v-6-0-4-6-a-385365/
lioko27 said:
Varcain many times I tried urochomic recowery combination of keys and the only time I did which is a little embarrassing, it can be somehow improved?
---------- Post added at 07:54 PM ---------- Previous post was at 07:41 PM ----------
Junior Member
this use
http://forum.android.com.pl/f1016/cmw-v-6-0-4-5-v-6-0-4-6-a-385365/
Click to expand...
Click to collapse
You have to be quick, it needs exact timing to enter.
Sent from my LG-D605 using Tapatalk
Avamander said:
You have to be quick, it needs exact timing to enter.
Sent from my LG-D605 using Tapatalk
Click to expand...
Click to collapse
Or install busybox and a terminal on your device.
When you did, start the terminal and then write:
$ su (Grant SU rights to the terminal)
# reboot recovery
and your phone reboots into recoverymode =)
if someone could add video startup recovery?
TaZRAge use the terminal as you can not turn the phone
if you succeed we drink cold Bolsa
I let the keys when the white text and the phone powers on, I tried all kombinace which gave Varcain and nothing, which in the end is right?
Another method of starting (works every time):
hold power and vol - on the phone turned off, the message, press power, the next message, press the power again and we are in recovery.
NOTE THIS METHOD WILL WIPE DATA, HARD RESET
Hello,
currently my Honor doesn't boot into the system anymore after trying to flash the OpenKirin's RROS v5.8.4 for Honor 9 Rom. I can boot to Bootloader but not to TWRP. When i tried to flash the Recovery via fastboot, I just get the following error message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-stf.img
target reported max download size of 471859200 bytes
sending 'recovery' (18706 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.429s
This happens with every file i tried to flash. My guess is that maybe the USB Debugging has been somehow disabled.
And when I try to boot to the system it Stuck at "Your device has failed verification and may not work properly" and restart every 2 - 3 min.
I also tried this method: https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719 but it didn't work either because i get error messages after pressing on "update.bat". Maybe because of the USB Debugging.
My device is STF - L09 Europe.
I hope you can help me. Thanks.
Is your bootloader locked? You turned OEM Unlock Off in Developer Settings?
4r44444 said:
Is your bootloader locked? You turned OEM Unlock Off in Developer Settings?
Click to expand...
Click to collapse
Bootloader is unlocked and OEM ist activated.
I finally managed to restore my device!!! I did it with DC Phoenix.
But i notice four things:
- Only the Homebutton didn't work. ( I got onscreen buttons)
- I have a completely wrong model number: generic_a15 (hi3660). Normally it called: STF - L09
- I still can't flash TWRP because of the error message which i already got before: "FAILED (remote: Command not allowed)"
- The NFC Logo in the status bar flashes all the time
Navigation buttons don't work because you probably flashed a factory version L09C432B130, in which this is a known bug. Use a rebrand guide to downgrade to B120 and then update again to B130 via OTA. That will resolve all other issues.
For TWRP you will again need to unlock bootloader because now it is locked and also disable FRP.
lsvet1 said:
Navigation buttons don't work because you probably flashed a factory version L09C432B130, in which this is a known bug. Use a rebrand guide to downgrade to B120 and then update again to B130 via OTA. That will resolve all other issues.
For TWRP you will again need to unlock bootloader because now it is locked and also disable FRP.
Click to expand...
Click to collapse
ok thanks. Where can i get the B120?
Ayeshetu said:
ok thanks. Where can i get the B120?
Click to expand...
Click to collapse
Rebrand guide.
I got this error message:
https://youtu.be/8ex2-dSl6Q8
Phone is on Fastboot mode. Bootloader and FRP are unlocked
That's something related to your computer. Do you by any chance have already installed Cygwin?
1. Check if you already have any CYGWIN_HOME variable in the environment variables. If yes delete it.
2. Run the batch file from the current folder and not from system32.
lsvet1 said:
That's something related to your computer. Do you by any chance have already installed Cygwin?
1. Check if you already have any CYGWIN_HOME variable in the environment variables. If yes delete it.
2. Run the batch file from the current folder and not from system32.
Click to expand...
Click to collapse
now it worked. I just moved it to C: \ Users.
It says that it can't access. Probably because of the wrong model number.
{
"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"
}
Ayeshetu said:
now it worked. I just moved it to C: \ Users.
It says that it can't access. Probably because of the wrong model number.
View attachment 4246735
Click to expand...
Click to collapse
The name of your phone is wrong because you installed RROS. Check all folders AND files in HWOTA folder and wherever you see 'STF' replace it with 'generic_a15'.
lsvet1 said:
The name of your phone is wrong because you installed RROS. Check all folders AND files in HWOTA folder and wherever you see 'STF' replace it with 'generic_a15'.
Click to expand...
Click to collapse
I changed all folders and files i see (STF) to generic_a15. But there is still the error message. Did it fit what I did?:
https://youtu.be/lVRm_t3n9cM
Ayeshetu said:
I changed all folders and files i see (STF) to generic_a15. But there is still the error message. Did it fit what I did?:
https://youtu.be/lVRm_t3n9cM
Click to expand...
Click to collapse
Still problems with the path. Try it first on another computer and unzip it directly to C:\ . If it still doesn't work I will send you another hwota.sh file.
lsvet1 said:
Still problems with the path. Try it first on another computer and unzip it directly to C:\ . If it still doesn't work I will send you another hwota.sh file.
Click to expand...
Click to collapse
Unfortunately I only have this one computer.
Ayeshetu said:
Unfortunately I only have this one computer.
Click to expand...
Click to collapse
In that case you'll have to do it manually. Flash first twrp recovery via fastboot, then boot into twrp and install the stock OS via ADB. If the phone is already rebranded you can skip rebranding step. Put all files in folder with adb.
Commands
Twrp installation:
Code:
fastboot flash recovery twrp.img
Reboot and boot to TWRP
Stock installation:
Code:
ADB shell "rm -fr /data/update/HWOTA > /dev/null 2>&1"
ADB shell "mkdir /data/update/HWOTA > /dev/null 2>&1"
ADB push update.zip /data/update/HWOTA/update.zip
ADB push update_data_public.zip /data/update/HWOTA/update_data_public.zip
ADB push update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
ADB push STF_RECOVERY_NoCheck.img /tmp/STF_RECOVERY_NoCheck.img
ADB push STF_RECOVERY2_NoCheck.img /tmp/STF_RECOVERY2_NoCheck.img
ADB shell "dd if=/tmp/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p37"
ADB shell "dd if=/tmp/STF_RECOVERY2_NoCheck.img of=/dev/block/mmcblk0p34"
ADB shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
ADB shell "echo --update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command"
ADB shell "echo --update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command"
ADB reboot recovery
ADB kill-server
lsvet1 said:
In that case you'll have to do it manually. Flash first twrp recovery via fastboot, then boot into twrp and install the stock OS via ADB. If the phone is already rebranded you can skip rebranding step. Put all files in folder with adb.
Commands
Twrp installation:
Code:
fastboot flash recovery twrp.img
Reboot and boot to TWRP
Stock installation:
Code:
ADB shell "rm -fr /data/update/HWOTA > /dev/null 2>&1"
ADB shell "mkdir /data/update/HWOTA > /dev/null 2>&1"
ADB push update.zip /data/update/HWOTA/update.zip
ADB push update_data_public.zip /data/update/HWOTA/update_data_public.zip
ADB push update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
ADB push STF_RECOVERY_NoCheck.img /tmp/STF_RECOVERY_NoCheck.img
ADB push STF_RECOVERY2_NoCheck.img /tmp/STF_RECOVERY2_NoCheck.img
ADB shell "dd if=/tmp/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p37"
ADB shell "dd if=/tmp/STF_RECOVERY2_NoCheck.img of=/dev/block/mmcblk0p34"
ADB shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
ADB shell "echo --update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command"
ADB shell "echo --update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command"
ADB reboot recovery
ADB kill-server
Click to expand...
Click to collapse
Thanks, I'll try it out.
lsvet1 said:
In that case you'll have to do it manually. Flash first twrp recovery via fastboot, then boot into twrp and install the stock OS via ADB. If the phone is already rebranded you can skip rebranding step. Put all files in folder with adb.
Commands
Twrp installation:
Code:
fastboot flash recovery twrp.img
Reboot and boot to TWRP
Stock installation:
Code:
ADB shell "rm -fr /data/update/HWOTA > /dev/null 2>&1"
ADB shell "mkdir /data/update/HWOTA > /dev/null 2>&1"
ADB push update.zip /data/update/HWOTA/update.zip
ADB push update_data_public.zip /data/update/HWOTA/update_data_public.zip
ADB push update_all_hw.zip /data/update/HWOTA/update_all_hw.zip
ADB push STF_RECOVERY_NoCheck.img /tmp/STF_RECOVERY_NoCheck.img
ADB push STF_RECOVERY2_NoCheck.img /tmp/STF_RECOVERY2_NoCheck.img
ADB shell "dd if=/tmp/STF_RECOVERY_NoCheck.img of=/dev/block/mmcblk0p37"
ADB shell "dd if=/tmp/STF_RECOVERY2_NoCheck.img of=/dev/block/mmcblk0p34"
ADB shell "echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command"
ADB shell "echo --update_package=/data/update/HWOTA/update_data_public.zip >> /cache/recovery/command"
ADB shell "echo --update_package=/data/update/HWOTA/update_all_hw.zip >> /cache/recovery/command"
ADB reboot recovery
ADB kill-server
Click to expand...
Click to collapse
So if I have understood correctly, then I must enter these stock installation commands exactly the same in the CMD while the phone is in the TWRP.
In principle yes, but check the file names.
lsvet1 said:
In principle yes, but check the file names.
Click to expand...
Click to collapse
I have now figured out why I was not able to flash RROS properly. I have apparently made a mistake at the vendor flashing. When i boot the phone now then appears the RROS logo but it stuck there. Will the whole thing work if I install the B130 with DC Phoenix and then flash RROS again or are there other possibilities?
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
This guide is only working on Pace 1!
This guide will give you a way to preview version 2.0.6.12 on your device. The Rom has no OTA, so you'll have to wait for a thread update.
If you like my work you can buy me a cheescake: https://www.paypal.me/JRevenge
P.S The Rom is only in Chinese or partly in English
Guide:
Requirements
Unlocked Bootloader: if you don't have the bootloader unlocked, you can apply here https://nicolasagliano.com/lo-sblocco-del-bootloader-e-arrivato/
Cables: Charging base with NOT original cable (it is very important)
Drivers: It is very important to have the adb / fastboot drivers installed, if you don't have them, follow this guide https://forum.xda-developers.com/showthread.php?t=2588979
Health: A lot of calm and experience!
Installation
1. You need to download the following package and unpack it in the adb folder (it is normally found in c: \ adb)
2. Connect the Pace to the computer using its charging base and the micro-usb cable (it is very important that the PC sees the internal memory of the device in the exploration of resources)
3. Open the Windows command terminal and enter the following command
Code:
C:\adb
4. Once you are inside the adb folder, you will need to enter the following commands
Code:
adb shell reboot bootloader
By doing this, the device will enter the fastboot mode (you will notice it from the Pace screen)
5. Now it's most important flash the recovery image, enter the following commands
Code:
fastboot boot rec.img
6. Now wait for the device to restart (it takes a few minutes)
7. Now in sequence, the following commands:
Code:
adb root
adb remount
8. Now it's time to copy data into the device, typing these commands:
Code:
adb push boot.img /data/media/0/
adb push system.img /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/
Once you have copied the files (system will take a while to copy) you will have copied all the files
9. Enable root permissions
Code:
adb shell
10. Put this command in sequence:
Code:
cd /data/media/0/
sh flash_rom.sh
11. Wait for the end of the installation and restart with the following command
Code:
adb reboot
If you want to have English as a language, partially, after the first start, you will have to give the following command:
Code:
adb shell setprop persist.sys.language en
adb reboot
Now the installation is finished! Congratulations!
I thank @Cracklydisc (Nicola) for contributing to the installation instructions.
I will try to update the post more often based on the release of updates. Also below you can download the updated version of the application (in step with the developer path)
N.B For Italians who will install it, it will be in Italian, for others in English
It is possible to download it at the following link (2.4.0 version)
Reserved
If you want to see some photos and some comparison with the Stratos, you can do it at the following link
If you want to stay up-to-date on the Amazfit world, you can follow this Telegram channel (it's currently being created)
If you want help on the international group on Facebook, follow this link
Thank you for sharing the files and the info. A few questions:
- Can it be installed over any other Pace firmware, either stock or custom?
- The only files that are flashed are the kernel and system, no other firmware files are needed, like recovery?
- What is the recommended Amazfit app to be used with it? Latest CN version, latest DEV CN or any is fine?
- Finally, the linked AmazIT 2.4.0 corresponds to what Amazfit app?
thank, i try tonight
fastboot boot rec.img error to many link ?? how to fix
Just some info, fastboot boot rec.img does not flash the rec.img, it just boots the image that you send to the device.
There are some problems with the flashing files
1. the rec.img does not work correctly, it just hangs in fastboot and doesn't restart the device as root in adb. I used a different boot image to gain root access.
2. the md5 signature for boot.img that is stored in md5s.txt does not match the real md5 signature of boot.img. I manually modified it to get past the check in flash_rom.sh.
3. the command for copying system.img in flash_rom.sh is wrong.
in the file, the command is "dd if=system.img | dd of=/dev/block/platform/jzmmc_v1.2.0/by-name/system bs=4096"
but it should be "dd if=system.img of=/dev/block/platform/jzmmc_v1.2.0/by-name/system bs=4096"
brmbjn said:
fastboot boot rec.img error to many link ?? how to fix
Click to expand...
Click to collapse
Hello
Two issues for me:
- fastbboot boot rec.img : error two many links. I used old Amazfit-mod-recovery.img from Neuer_User to boot in Recovery-
https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
- md5 sum check error with boot.img : deleting check of md5 sum in flash_rom.sh (Validating images part) - not recommanded!
Thanks JRevenge, Firmware is good, and almost everything is in English.
Armageda said:
1. the rec.img does not work correctly, it just hangs in fastboot and doesn't restart the device as root in adb. I used a different boot image to gain root access.
2. the md5 signature for boot.img that is stored in md5s.txt does not match the real md5 signature of boot.img. I manually modified it to get past the check in flash_rom.sh.
3. the command for copying system.img in flash_rom.sh is wrong.
in the file, the command is "dd if=system.img | dd of=/dev/block/platform/jzmmc_v1.2.0/by-name/system bs=4096"
but it should be "dd if=system.img of=/dev/block/platform/jzmmc_v1.2.0/by-name/system bs=4096"
Click to expand...
Click to collapse
how did you modified the md5? how did you find the right md5?
yuv78 said:
how did you modified the md5? how did you find the right md5?
Click to expand...
Click to collapse
in linux, just use md5sum <file>. this will give you the md5 hash of the file.
Fastboot boot too many links too here...
Are you sure of your instructions ? Seems strange = no recovery flashed in the process...
Good md5 : F0C9357B882C3AF11BB81815F39BDF9C boot.img (replace in md5 file)
Boot another recovery
updating/checking
Thanks for your efforts and just a quick feedback:
Running on an international ROM Stratos4Pace v0.1b2_2.3.0.8 my first step was to unpair the watch from the Playstore Amazfit app.
After changing the md5 of boot.img and adopting the flash_rom.sh as stated previously the ROM installed fine (I skipped booting rec.img since I was running a rooted rom [Stratos4Pace v0.1b2_2.3.0.8]).
Paired it with the AmazIt app afterwards, which connects to a Mifit Account I previously created.
Had some problems with setting the watch to english but after a while it worked with the following commands (which seems essentially the same like written in the first post).
adb shell
setprop persist.sys.language en
exit
adb reboot
Lost my previous tracks in the Mifit app since I was before on the international ROM (no regrets).
ROM doesn't have Root!
Edit: Settings - About is crashing my settings, otherwise English translations seem to be working fine.
nhedgehog said:
Thanks for your efforts and just a quick feedback:
Running on an international ROM Stratos4Pace v0.1b2_2.3.0.8 my first step was to unpair the watch from the Playstore Amazfit app.
After changing the md5 of boot.img and adopting the flash_rom.sh as stated previously the ROM installed fine (I skipped booting rec.img since I was running a rooted rom [Stratos4Pace v0.1b2_2.3.0.8]).
Paired it with the AmazIt app afterwards, which connects to a Mifit Account I previously created.
Had some problems with setting the watch to english but after a while it worked with the following commands (which seems essentially the same like written in the first post).
adb shell
setprop persist.sys.language en
exit
adb reboot
Lost my previous tracks in the Mifit app since I was before on the international ROM (no regrets).
ROM doesn't have Root!
Click to expand...
Click to collapse
Being an official Rom, it doesn't have root permissions. If you come from an official Rom, you need to install the temporary root of STRATOSfied
I'm a control freak - can I root it myself somehow permanently?
nhedgehog said:
I'm a control freak - can I root it myself somehow permanently?
Click to expand...
Click to collapse
Since this is an official ROM, no, unless someone find a way to hack it.
You can obtain a temporary root with a crafted boot image, and it will last until the next reboot.
Armageda said:
Since this is an official ROM, no, unless someone find a way to hack it.
You can obtain a temporary root with a crafted boot image, and it will last until the next reboot.
Click to expand...
Click to collapse
Exactly!
Just one issue, Rom version is 2.6.0.12 instead of 2.0.6.12
I switch rec.img with Amazfit-mod-recovery.img
changed md5s.txt and flash_rom.sh with the attachments and used the tutorial on the fist post all went well
adb shell reboot bootloader
fastboot boot Amazfit-mod-recovery.img
adb root
adb remount
adb push boot.img /data/media/0/
adb push system.img /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/
adb shell
cd /data/media/0/
sh flash_rom.sh
adb reboot
thanks for the rom, its great
:good::good:
Success!!!
Hernanis75 said:
I switch rec.img with Amazfit-mod-recovery.img
changed md5s.txt and flash_rom.sh with the attachments and used the tutorial on the fist post all went well
adb shell reboot bootloader
fastboot boot Amazfit-mod-recovery.img
adb root
adb remount
adb push boot.img /data/media/0/
adb push system.img /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/
adb shell
cd /data/media/0/
sh flash_rom.sh
adb reboot
thanks for the rom, its great
:good::good:
Click to expand...
Click to collapse
That was the way for me BUT not with windows 10. Linux BAM BAM!!!