Related
Hi,
it is possible to change the vodafone splash with a custom one?
Kindly Regards
Puky70
Not that I know of...
I've got a dev phone (pure chance on contract) and I tried following this:
http://gettinthru.blogspot.com/2009/04/mods-for-tmobile-g1-at-your-own-risk.html
Steps I took:
C:\Downloads\Magic\android-sdk-windows-1.5_r1\tools>adb root
restarting adbd as root
C:\Downloads\Magic\android-sdk-windows-1.5_r1\tools>adb remount
remount succeeded
C:\Downloads\Magic\android-sdk-windows-1.5_r1\tools>adb shell
# ls
ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.sapphire.rc
init.rc
init.goldfish.rc
init
default.prop
data
root
dev
# cd system
cd system
# ls
ls
lib
xbin
framework
media
bin
usr
app
fonts
lost+found
etc
build.prop
# cd media
cd media
# ls
ls
audio
I can see a folder in System/Media called Audio but neither of the files mentioned (maybe hidden though).I'm having a look as the doc probably refers to Android 1.1 on the G1.
I'm only just starting to mess about with this so not sure where to go now...
I'm new to android, but I'm going to assume it's the same as linux. Hidden files are any file that starts with a dot. in order to see them, you can just do:
# ls -a
which should show everything
The startup splash logo is logo.rle
The media folder in system only contains an audio folder for system sounds.
You'll need to get your head around GNUWin32 http://gnuwin32.sourceforge.net/ to create and package a new .rle at a guess, playing with this now to see if I can get anywhere.
Have you guys searched the dream forums, we have the ability to change splash and boot screens, now you have root you should be able to do the nessicary adb stuff. I would guess your file structure is different so don't just do this blindly.
Hi,
have anyone changed the VF splash screen with the G1 mode (Tutorial)?
with windows or linux (on wine + net framework 2):
1)download this
password "androidsocket"
2)with createG1splash create your splash (mysplash.rgb565) from a gif or png 332x498
3)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
4)boot the magic in fastboot mode (witch back+power)
5)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
(you need haykuro spl to flash splash screen!)
in this thread there are some splash jpg/gif !
Thank You! It works perfectly!!
nk02 said:
with windows or linux (on wine + net framework 2):
1)download this
password "androidsocket"
2)with createG1splash create your splash (mysplash.rgb565) from a gif o jpg 332x498
3)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
4)boot the magic in fastboot mode (witch back+power)
5)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
(you need haykuro spl to flash splash screen!)
in this thread there are some splash jpg/gif !
Click to expand...
Click to collapse
Great! I'll try that out later
any chance to put a animated splash???
A little present
I hate those horrible red vodafone splash, so i create this one. Thanks to Nk02 for the know how.The splash show a green Google droid in the background.
1)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
2)boot the magic in fastboot mode (witch back+power)
3)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
Enjoy it
Poteck
poteck said:
I hate those horrible red vodafone splash, so i create this one. Thanks to Nk02 for the know how.The splash show a green Google droid in the background.
1)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
2)boot the magic in fastboot mode (witch back+power)
3)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
Enjoy it
Poteck
Click to expand...
Click to collapse
yess ! thanks works fine very simply !!!!
Is the change of flash screen permanent or will it get overwritten with a new ROM?
poteck said:
I hate those horrible red vodafone splash, so i create this one. Thanks to Nk02 for the know how.The splash show a green Google droid in the background.
1)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
2)boot the magic in fastboot mode (witch back+power)
3)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
Enjoy it
Poteck
Click to expand...
Click to collapse
Brilliant! Thanks.
pdagenius said:
Is the change of flash screen permanent or will it get overwritten with a new ROM?
Click to expand...
Click to collapse
I think it will be permanent because when I flashed with two new build I'd always the vodafone splash
FAILED
fastboot flash splash1 mysplash.rgb565
sending 'splash1' (300 KB)... OKAY
writing 'splash1'... INFOsignature checking...
FAILED (remote: signature verify fail)
Any ideas?
moremadness2001 said:
fastboot flash splash1 mysplash.rgb565
sending 'splash1' (300 KB)... OKAY
writing 'splash1'... INFOsignature checking...
FAILED (remote: signature verify fail)
Any ideas?
Click to expand...
Click to collapse
requires you to use the new SPL. (1.33.2005)
anywho..
i'd like to make a quick notice, if you ever happen to brick your device, and you have a modded boot screen, it will make your life much more difficult to return your device! just keep this in mind!
haykuro said:
requires you to use the new SPL. (1.33.2005)
anywho..
i'd like to make a quick notice, if you ever happen to brick your device, and you have a modded boot screen, it will make your life much more difficult to return your device! just keep this in mind!
Click to expand...
Click to collapse
so it is time to ask................anyone have the original vodafone splash screen to share ??
haykuro said:
requires you to use the new SPL. (1.33.2005)
anywho..
i'd like to make a quick notice, if you ever happen to brick your device, and you have a modded boot screen, it will make your life much more difficult to return your device! just keep this in mind!
Click to expand...
Click to collapse
Where do I get this SPL Version? I only know the link in the root magic thread.
steiale said:
Where do I get this SPL Version? I only know the link in the root magic thread.
Click to expand...
Click to collapse
From here:
http://code.google.com/p/sapphire-port-dream/
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, you getting fired because the alarm app failed, or anything whatsoever.
* Please do some research if you have any concerns about things covered in this guide
* before flashing! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
(Thank you CM Team for that bit of advice)
What is a Splash1?
Splash1 is the image that shows up before recovery / your ROM's bootsplash / etc. By default, it is the white screen with green HTC lettering (if you have flashed Sprint's 2.1 release.)
How do I change it?
Follow these steps to create the image, then the steps to flash the image.
Creating a splash1, Tool method:
1. Pick your image of choice, and crop it to 320x480 (width x height). This resolution is meant for the HTC Hero and screens of similar size. If you're looking to adapt this to other phones, make sure you know your resolution. It could be 480x800 (e.g. HTC Evo), or even 480x854 (Droid X).
2. Use the attached CreateG1Splash tool to convert your image to R5G6B5 format. It should output a file named 'mysplash.rgb565'.
Creating a splash1, GIMP method:
Note: This seems to have strange results in Windows. In my personal tests, the images ended up upside down, mirrored, and shifted to the right when they were flashed. You can use Tomatosoup's Gimp Script to fix it.
1. Open your desired image in GIMP. Use the appropriate tools (e.g. Scale, Canvas Size) to edit your image to the correct size. (Again, 320x480 for HTC Hero).
2. Go to Image => Print Size and make sure it is set to 72 pixels per inch.
3. Hit Save As => Extension => BMP => Save => Advanced => R5 G6 B5 Format => Save.
Flashing a splash1, Fastboot method:
IMPORTANT! This method is for users who have an ENG SPL. Browse through the relevant forums here on XDA to find out how to achieve this. This method does not work with Unrevoked Forever.
1. Open up a command prompt / terminal / console, and type:
Code:
adb reboot bootloader
OR power your phone off, then power it back on while holding VOL UP.
2. Once you're in fastboot, make sure the phone says "FASTBOOT USB", and when you type "fastboot devices" in the console, it returns the device name. If it returns anything strange, make sure your phone's USB drivers are installed and anything else that might use the phone is closed (e.g. HTC Sync).
3. In your command line / console / terminal, and type this, replacing "path to" with the right directories:
Windows Users:
Code:
fastboot flash splash1 C:\path\to\mysplash.rgb565
Linux Users:
Code:
fastboot flash splash1 /path/to/mysplash.rgb565
You should see "Sending splash1... OK ; Flashing splash1... OK"
4. Now enter:
Code:
fastboot reboot
Your new splash1 should be visible!
Flashing a splash1, HERCIMG method:
This method is compatible with Unrevoked Forever and people getting "Remote: Not Allow" errors.
1. Download the attached HERCIMG.zip to use as an example.
2. Extract the two files: android-info.txt and splash1.nb0
This is the template for the HERCIMG you will create and flash.
3. Delete the splash1.nb0 in the zip. Take the splash1 you created, rename it splash1.nb0
4. Select your splash1.nb0, and the android-info.txt, and zip them together. Rename the zip as HERCIMG.zip
NOTE: Zip ONLY the two files, DO NOT zip the folder containing the files or anything else!
5. Put the HERCIMG.zip on the root of your sdcard:
Code:
adb push HERCIMG.zip /sdcard/HERCIMG.zip
6. Reboot into HBoot either by holding VOL DOWN while you power your phone on, or:
Code:
adb reboot bootloader
Then press VOL DOWN to enter HBoot Mode.
7. Your phone should say:
Code:
Parsing...[SD ZIP]
[1] SPLASH1
Do you want to start update?
<ACTION> Yes
<SEND> No
Press ACTION (Trackball button) to flash the HERCIMG.zip.
It should now say OK. Press ACTION again to reboot the device.
Your new splash1 should be visible!
Attached is a preview of a CM6 splash1 I converted, and a zip file containing the mysplash.rgb565 file.
The attached cyanogenmodsplash.zip is not a flashable zip!
Credits to:
CyanogenMod team for the disclaimer.
toastcfh and darchstar for the ENG SPL.
regaw_leinad and Unrevoked Team for Unrevoked Forever.
Koushik Dutta for his CreateG1Splash tool.
tomatosoup for GIMP Method.
And anyone else that deserves credit.
Koush's full CreateG1Splash tool.
didnt work for me im s off and all i got back was error: cannot load ' /path/to/mysplash.rgb565
It's not literally /path/to/mysplash.rgb565, you're supposed to replace it with the path to the file you created, like C:\Users\JimBob\Desktop\mysplash.rgb565
didnt work
tehdarkknight said:
It's not literally /path/to/mysplash.rgb565, you're supposed to replace it with the path to the file you created, like C:\Users\JimBob\Desktop\mysplash.rgb565
Click to expand...
Click to collapse
gave me same error
i placed the rgb in the desktop and i even changed users name to JimBob so the path would be the same as the one u posted
It stays on the Sending Splash.... forever. What am I doing wrong?
thegod2012 said:
gave me same error
i placed the rgb in the desktop and i even changed users name to JimBob so the path would be the same as the one u posted
Click to expand...
Click to collapse
That error means you're not using the correct path. The JimBob thing was just an example, you need to supply it with the relevant file name on your computer.
mquinn24 said:
It stays on the Sending Splash.... forever. What am I doing wrong?
Click to expand...
Click to collapse
When you plug in your phone and reboot into fastboot, double check that it's properly connected:
Code:
fastboot devices
It should return something like: "HT039HF01009 fastboot"
Also double check that your phone's screen says "FASTBOOT USB"
doesn't work
i placed the rgb565 file in desktop and i enter the fastboot flash splash1 C:\Users\oden\Desktop\mysplash.rgb565
i get back
sending 'splash1' <300KB>... FAILED <remote:not allow>
finished. total time: 0.001s
I checked all of that and I'm good. Now I get "sending ' splash' <300kb> ... Failed <remote :not allowed>
Edit: I need to find the correct path
The "Failed <remote: not allowed>" error message probably means your HBOOT won't let you flash unsigned images, in other words you're using the stock HBOOT.
Try flashing darchstar's ENG SPL or regaw_leinad's S-OFF NAND Unlock method.
interesting....
wil there be an issue if i flash both i already have s off
hboot
tehdarkknight said:
The "Failed <remote: not allowed>" error message probably means your HBOOT won't let you flash unsigned images, in other words you're using the stock HBOOT.
Try flashing darchstar's ENG SPL or regaw_leinad's S-OFF NAND Unlock method.
Click to expand...
Click to collapse
i just flashed darchstars spl i'll let u know
it worked by changing the hboot with darch SPL thanks
Attached is another splash1 I converted, created by Vigan on the CM forums.
The .png is the preview, the mysplash.rgb565 is contained in the zip.
Hope you enjoy!
I updated the first post to reflect that this method of flashing a splash1 will not currently work with Unrevoked Forever.
You should be able to safely flash darchstar's ENG SPL from recovery even if you've already flashed Unrevoked Forever.
Thanks I got it to work on Darch's
Hey everyone, I started a thread in the Themes and Apps section called
[SPLASH IMAGES] Gallery of Custom Splash Images if anyone wants to post and share their custom splash images they've created.
tehdarkknight, would you consider posting the link to it in your main OP? And please feel free to go post the couple you already have in this thread over into that gallery.
Complete noob to flashing splash images. My cmd is saying fastboot is an invalid action? I feel like a retard...
whosthat123 said:
Complete noob to flashing splash images. My cmd is saying fastboot is an invalid action? I feel like a retard...
Click to expand...
Click to collapse
Make sure the android sdk is installed, there are plenty of guides on how to do so.
Sent from my HERO200 using XDA App
I'm a retard for sure. Had sdk installed. I wasn't in adb. Works like a charm. Thanks!
There is a new downgrade option released for firmware 1.36.970.1 to 1.15.970.1.
However my Japanese is not perfect and my understanding of hacking is very weak.
If there is someone more in the know could understand what the steps to take are that would be great.
Good luck all. I hope someone can make a guide as well to help other out.
I'll try my best as well.
Here is the link.
http://htcsoku.info/htcsokudev-news/au-deluxe-136to115-downgrade/
link to RUU 1.15.970.1 is dead
I have successfully downgraded my J Butterfly based on those instructions. I have simplified it because the original instructions seems to be overly complicated. It involved tricking a system app with root privileges to run an custom command, only to use run_root_shell later anyway.
I also did not use the run_root_shell supplied by the guide, instead I compiled a newer version direct from the source: https://github.com/android-rooting-tools/android_run_root_shell
You'll need
1. revone.dna-0.2.1
http://forum.xda-developers.com/showthread.php?t=2314582
2. A newer build of run_root_shell (attached)
3. 1.15 ROM: PL99IMG_DLX_WLJ_JB_45_KDDI_JP_1.15.970.1_R_Radio_1.00.10.1127_3_NV_2.28_01C_release_signed.zip
(renamed to rom.zip in this tutorial)
https://mega.co.nz/#!jQtQ0BLS!279lf8k4sbKPTmWHTsPg6hbaGDatpq3xGGv4aE8N1h4
4. firmware.zip extracted from OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip:
http://kie.nu/1urK
5. adb and fastboot
6. An HEX editor such as XVI32
THIS WILL WIPE YOUR USER DATA, BACKUP ALL YOUR STUFF FIRST
Steps:
1. Run the following commands in command prompt to push files required by run_root_shell to device:
adb push run_root_shell /data/local/tmp/
adb push device.db /data/local/tmp/
2. Run in command prompt:
adb shell
to access the shell on your device. Run the following commands to run run_root_shell, disregard messages about HTL21 not supported. You will be returned to the command line but with a hash (#) instead of a dollar sign, that means you have temprooted.
cd /data/local/tmp/
chmod 755 *
./run_root_shell
3. Run these commands on device shell:
chmod 666 /dev/msm_acdb
dd if=/dev/block/mmcblk0p21 of=/sdcard/p21
4. Run in another command prompt:
adb pull /sdcard/p21
to pull the file p21 from device, then open it with an HEX editor. Refer to the images on the original Japanese tutorial, change the version number near "ClearAutoImage" to 1.00.000.0 and save the file as p21mod.
5. Push the modified file back to the device by running in command prompt:
adb push p21mod /sdcard/p21mod
6. Back to the device shell, run these commands to write the modifications to the device and reboot into bootloader.
dd if=/sdcard/p21mod of=/dev/block/mmcblk0p21
reboot bootloader
7. Run in command prompt:
fastboot oem rebootRUU
to boot to RUU.
8. Run in command prompt:
fastboot flash zip firmware.zip
and it willl fail with this error: "FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
9. Run in command prompt:
fastboot flash zip rom.zip
to flash 1.15 ROM. It should take around 6 minutes. This wipes your user data.
10. In command prompt, push run_root_shell to device again. Also push revone.dna-0.2.1 to device.
adb push run_root_shell /data/local/tmp/
adb push device.db /data/local/tmp/
adb push revone.dna-0.2.1 /data/local/tmp/revone.dna
11. Refer to step 2 to temproot again.
12. Run revone.dna on device shell:
./revone.dna -P
and you should see "revone successful - please reboot to continue".
13. Reboot and repeat step 12 again, this time you should see "revone successful - no need to reboot".
14. Run on device shell:
./revone.dna -s 0 -u
and you should see "revone successful".
15. ???
16. PROFIT!
You have now successfully S-OFFed and may proceed to unlocking and SuperCIDing your device as usual.
Corrupted
Phil_123 said:
3. 1.15 ROM: PL99IMG_DLX_WLJ_JB_45_KDDI_JP_1.15.970.1_R_Radio_1.00.10.1127_3_NV_2.28_01C_release_signed.zip
(renamed to rom.zip in this tutorial)
.
Click to expand...
Click to collapse
I have downloaded this file twice and found it corrupted. Can't open it so i can't uncompress and reach firmware.zip either.
:crying:
Could you reupload it?
corrupted
darky4e said:
I have downloaded this file twice and found it corrupted. Can't open it so i can't uncompress and reach firmware.zip either.
:crying:
Could you reupload it?
Click to expand...
Click to collapse
I have "fixed" it by Zip2Fix and made a zip file what can be extracted. But the two zip file size isn't match so i guess its isn't the same and there isn't any firmware.zip in the nem zip file so i guess the program extracted everything.
I have read that some people succesfully used corrupted ruu, and it's made corrupted by reason. I will read more about it and try to find a correct firmware.zip for the method. If you could help me in any means it would be great.
darky4e said:
I have "fixed" it by Zip2Fix and made a zip file what can be extracted. But the two zip file size isn't match so i guess its isn't the same and there isn't any firmware.zip in the nem zip file so i guess the program extracted everything.
I have read that some people succesfully used corrupted ruu, and it's made corrupted by reason. I will read more about it and try to find a correct firmware.zip for the method. If you could help me in any means it would be great.
Click to expand...
Click to collapse
My bad, my instructions were wrong. I wrote them only after successfully doing it myself, I must have mixed some things up while writing.
I looked at the original Japanese guide again, the firmware.zip is in OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip and can be downloaded here:
http://kie.nu/1urK
Phil_123 said:
My bad, my instructions were wrong. I wrote them only after successfully doing it myself, I must have mixed some things up while writing.
I looked at the original Japanese guide again, the firmware.zip is in OTA_DLX_WLJ_JB_45_KDDI_JP_1.36.970.1-1.29.970.1_release_330380g3nfgypcfojku8a9.zip and can be downloaded here:
http://kie.nu/1urK
Click to expand...
Click to collapse
Thank you very much! I have succesfully downgraded the phone! Thx for the instructions again!!
run_root_shell and revone.dna-0.2.1 work with HTC Butterfly kddi HTL21 with HBOOT 1.41 ? I'am stuck on run_root_shell and it say's "Error No such file or directory" when I use the command in adb "$ ./run_root_shell"
what can I do ?
dfani511 said:
run_root_shell and revone.dna-0.2.1 work with HTC Butterfly kddi HTL21 with HBOOT 1.41 ? I'am stuck on run_root_shell and it say's "Error No such file or directory" when I use the command in adb "$ ./run_root_shell"
what can I do ?
Click to expand...
Click to collapse
This method can only be used for the software version of the 1.36.970.1, I think your software version 1.39.970.1 is not SOFF
i have 1.39.970.3 ?????????????
OTA ??????????
Nice share, im succesfully unlock soff with this way
Sent from my MITO_A10 using XDA Free mobile app
"htl21 1399703 firmware" I want up because it cannot find the file.
This is a guide on rooting the new Chuwi Vi7 Phablet as a result of spending lots of hours on this proyect with the hope that others find it useful.
This is work in progress, do not attempt it if you are not ready to flash back the original rom in case you soft brick your Chuwi
PREREQUISITES:
A) For LINUX users:generally install the android-tools package so you have the adb command available.
In Manjaro linux and Arch Linux just do
Code:
sudo pacman -Sy android-tools
In Ubuntu probably
Code:
apt-get update && apt-get install android-tools
A) windows users would need to (presumibly; not tested)
For WINDOWS users:
install the intel drivers for android and user the attached adb.exe with dm-verity support
Most ADB.EXE do not have dm-verity. Try installing Java (prerequisite to install Android Studio) and installed Android Studio (download full package, but only install SDK part).
The file reported to work fine is android-studio-bundle-141.2117773-windows.exe
The ADB version is 1,011,200 bytes with date of 02/14/2015 07:12 PM.
1) (Recommended) Apply the over the air update; you know you have it when you can see the Google Playstore installed.
2) Connect your Chuwi Vi7 to your PC with a microusb cable
First we need the ability to write to the system partition so in order to do this, run these commands:
Code:
adb root
adb disable-verity
adb reboot
wait 30 seconds now we are going to do a backup of SYSTEM and DATA just in case
(if you are in Windows remove the ./ before system_068 and data_069)
This will take some minutes
Code:
adb boot recovery
Wait a few seconds until you are in the stock recovery
Code:
adb root
adb pull /dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID068 ./system_068
adb pull /dev/block/platform/soc0/e0000000.noc/by-name/ImcPartID069 ./data_069
adb reboot
3) unzip the attached file and transfer all the individual files contained to the Chuwi´s /data/local/tmp folder
Code:
adb root
# Now we are going to push the whole folder contained in the archive we just extracted
adb push RootChuwiVi7 /data/local/tmp/
4) Now from a terminal run this command:
Code:
adb shell /system/bin/sh -x /data/local/tmp/vi7root
alternatively run
Code:
./rootnow
and that´s it!
Now open Root Verifier (it´s an app) to check if your Chuwi is rooted...
If you like my work dont forget to press the THANKS button and/or donate
TIPS: If you do not get prompted to allow root access by superSU, do adb root from the command line
If you need to flash the phablet here you can download the rom and flashing tool:
https://mega.nz/#!QVFCGDCa!oz4jXrxdsE6pJ4rVt4AlbUHN-VY9NwTF7SNfeir0mSk
Password: jopasaps
You need to install the intel drivers and the flash drivers and run Flash E2, load all the rom files, click on custom order, tick all the boxes, select generic usb, click on NEXT, turn off the phablet, then click on USB1 and very very quickly plug the phablet to your PC while holding VOLUME- you will see some activity in the screen and within 1 minute it will be ready.
If it is ready within 5 seconds then you did not load all the files. Depending on why your phablet is soft bricked it may be enough to flash only some of the files.
KNOWN ISSUES: Open Source superuser by koush does not work as the su binary needs recompiling. We are therefore using SuperSU by chain, I suggest you don't update SuperSU in the Play Store.
TROUBLESHOOTING: the command adb reboot ptest_clear is reported to work with soft bricked devices (put here as a courtesy, not needed in principle)
UPDATE: Download this file to update your SYSTEM partition to the latest version of the firmware, including some debloating and with English as default language. This update is done from recovery, through an adb push command
Thanks for this! I'm trying but can't get it to work. Running the script generates errors and I've boiled it down to doing the permissions -- I can't mount /system as RW no matter what syntax I've tried. I'm in the ADB shell and running under SU (#). Also tried mounting explicit as /dev/block/dm-0 but it still only comes back as "mount: Read-only file system".
Try again from the beginning, you will be able to mount read/write system now...
ALSO VERY IMPORTANT, download the new attachment and use instead ...
Thanks, I tried to disable verity before and it didn't work. I'll try again this time.
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
Can you by any chance post your ADB.exe which has support for disable-verity command?
My adb is simple to install...
1) Install Manjaro linux
2) Run: pacman -Sy android-tools
and... that´s it! you get adb and fastboot
and no need to install android drivers
the sequence then I use to be able to write to the system partition on the Chuwi Vi7 is:
adb root
adb disable-verity (that needs to be done only once)
adb remount
Let me know whether it works in windows ...
TheAndroidGeek said:
Thanks, I tried to disable verity before and it didn't work. I'll try again this time.
---------- Post added at 11:14 AM ---------- Previous post was at 11:11 AM ----------
Can you by any chance post your ADB.exe which has support for disable-verity command?
Click to expand...
Click to collapse
casacristo said:
My adb is simple to install...
1) Install Manjaro linux
2) Run: pacman -Sy android-tools
and... that´s it! you get adb and fastboot
and no need to install android drivers
the sequence then I use to be able to write to the system partition on the Chuwi Vi7 is:
adb root
adb disable-verity (that needs to be done only once)
adb remount
Let me know whether it works in windows ...
Click to expand...
Click to collapse
For WINDOWS users:
I had various flavors of ADB.EXE and none of them had the dm-verity. Finally installed Java (prerequisite to install Android Studio) and installed Android Studio (download full package, but only install SDK part).
The file I used as android-studio-bundle-141.2117773-windows.exe
The ADB version is 1,011,200 bytes with date of 02/14/2015 07:12 PM.
Now rooted... but not sure what to do with this very low spec tablet I have so many other tablets (Onda, Teclast, Acer, etc).
Thanks casacristo!
Yeoh Master Shifu Arturo, its been awhile, how are you, only today notice your thread here, sorry for a little OT...
i own the first variance of x3(c3130), damn intel for making it so hard to root... :laugh:
Code:
[[email protected] ~]$ adb root
[COLOR="blue"]adbd cannot run as root in production builds[/COLOR]
[[email protected] ~]$ adb disable-verity
[COLOR="blue"]error: closed[/COLOR]
i was trying a different approach, root via recovery & i wonder if you have tried the FlsTool, can't figured out the correct commands to repack back ported custom recoveries...
Code:
[URL="https://github.com/android-ia/vendor_intel_build/blob/master/FlsTool/FlsTool"]FlsTool[/URL]
FlsTool v.1.21
This tool can do several different operations of FLS files.
Use the 'Action' option to select to required operation.
Actions:
-p [ --pack ] Packing multiple FLS files into one
-i [ --inject ] Inject NVM, Certificates or Security into FLS file
-x [ --extract ] Extract all image parts from the FLS file(s)
--extract-fls Extract embedded files from the FLS file(s)
--extract-prg Extract PRG file
-b [ --to-bin ] Convert a single Hex file to binary file
--hex-to-fls Create an Fls from a Prg file
--sign Formerly known as FlsSign
--to-fls2 [ arg ] Force output file format to Fls2
--to-fls3 [ arg ] Force output file format to Fls3
-d [ --dump ] Dump the meta data of an FLS file.
--sec-pack Dump all SecPack data of an FLS file.
HexToFls options:
--prg arg Choose a PRG file to create the Fls from
--psi arg Add a PSI to the Fls file (replaces if '-r' option)
--ebl arg Add an EBL to the Fls file (replaces if '-r' option)
--meta arg Inject any meta file to the Fls file (Equal to --version or -v in HexToFls)
--xml arg Add an XML file to the Fls file (replaces if '-r' option)
--zip arg Add a ZIP file to the Fls file (replaces if '-r' option)
--script arg Add a Script file to the Fls file (replaces if '-r' option)
--tag arg Specifies the memory region tag to insert the input file (replaces if '-r' option)
Inject options:
-n [ --nvm-path ] arg Path to the NVM input files
Generic Options:
-o [ --output ] arg Output path
-r [ --replace ] [ arg ] Defaults to replace when trying to add a section which is already existing
-v [ --verbose ] [ arg ] Set verbosity
--prompt [ arg ] Prompt before quitting
--version Show the version of this tool
-h [ --help ] Show command line help
Please specify an input file
@jasonx3
try this file:
https://mega.co.nz/#!UMVwTQIR!w04Pidyd2TRDLyWnqMfCL_qxXRtJmapD0UFmp0hQnx4
it is a full rom with root and gapps, with a script that flashes it (provided
you have a root shell)
@Vadim Shved
Can you be more specific?
I use link2sd without problems to convert apps to system apps.
do this:
adb root
adb remount
what is the output?
Hello Yuweng, good to see you, yes it has been a while... I don´t change hardware very frequently nowadays and not always I feel I can make a substantial contribution to the community
I have not used FlsTool but I have something to offer you....
Download this file:
https://mega.co.nz/#!UMVwTQIR!w04Pidyd2TRDLyWnqMfCL_qxXRtJmapD0UFmp0hQnx4
It is a complete dd copy of my system partition with a script that will verify the md5sum is correct and flash it.
I think this should work fine if you can be root though a recovery.
This system image has already root, busybox, google updates integrated
yuweng said:
Yeoh Master Shifu Arturo, its been awhile, how are you, only today notice your thread here, sorry for a little OT...
i own the first variance of x3(c3130), damn intel for making it so hard to root... :laugh:
Code:
[[email protected] ~]$ adb root
[COLOR="blue"]adbd cannot run as root in production builds[/COLOR]
[[email protected] ~]$ adb disable-verity
[COLOR="blue"]error: closed[/COLOR]
i was trying a different approach, root via recovery & i wonder if you have tried the FlsTool, can't figured out the correct commands to repack back ported custom recoveries...
Code:
[URL="https://github.com/android-ia/vendor_intel_build/blob/master/FlsTool/FlsTool"]FlsTool[/URL]
FlsTool v.1.21
This tool can do several different operations of FLS files.
Use the 'Action' option to select to required operation.
Actions:
-p [ --pack ] Packing multiple FLS files into one
-i [ --inject ] Inject NVM, Certificates or Security into FLS file
-x [ --extract ] Extract all image parts from the FLS file(s)
--extract-fls Extract embedded files from the FLS file(s)
--extract-prg Extract PRG file
-b [ --to-bin ] Convert a single Hex file to binary file
--hex-to-fls Create an Fls from a Prg file
--sign Formerly known as FlsSign
--to-fls2 [ arg ] Force output file format to Fls2
--to-fls3 [ arg ] Force output file format to Fls3
-d [ --dump ] Dump the meta data of an FLS file.
--sec-pack Dump all SecPack data of an FLS file.
HexToFls options:
--prg arg Choose a PRG file to create the Fls from
--psi arg Add a PSI to the Fls file (replaces if '-r' option)
--ebl arg Add an EBL to the Fls file (replaces if '-r' option)
--meta arg Inject any meta file to the Fls file (Equal to --version or -v in HexToFls)
--xml arg Add an XML file to the Fls file (replaces if '-r' option)
--zip arg Add a ZIP file to the Fls file (replaces if '-r' option)
--script arg Add a Script file to the Fls file (replaces if '-r' option)
--tag arg Specifies the memory region tag to insert the input file (replaces if '-r' option)
Inject options:
-n [ --nvm-path ] arg Path to the NVM input files
Generic Options:
-o [ --output ] arg Output path
-r [ --replace ] [ arg ] Defaults to replace when trying to add a section which is already existing
-v [ --verbose ] [ arg ] Set verbosity
--prompt [ arg ] Prompt before quitting
--version Show the version of this tool
-h [ --help ] Show command line help
Please specify an input file
Click to expand...
Click to collapse
Mine is a dual-sim c3130, ro.secure=1, ro.adb.secure=1, no adb while at stock 3e recovery, fastboot flash recovery twrp-recovery.img doesn't work, non of the existing exploit rooting software works, in fact, nothing works on this piece of sh#t but its so cheap... :laugh:
Got mine for less than a month, its a rebrand of Teclast X70, only last week the oem release the firmware, thats where i found out about FlsTool, its actually also available on Windows, i'll leave the linux copy here for everyone to explore...
Thanks! and by all means let us know if you succeed...
yuweng said:
Mine is a dual-sim c3130, ro.secure=1, ro.adb.secure=1, no adb while at stock 3e recovery, fastboot flash recovery twrp-recovery.img doesn't work, non of the existing exploit rooting software works, in fact, nothing works on this piece of sh#t but its so cheap... :laugh:
Got mine for less than a month, its a rebrand of Teclast X70, only last week the oem release the firmware, thats where i found out about FlsTool, its actually also available on Windows, i'll leave the linux copy here for everyone to explore...
Click to expand...
Click to collapse
casacristo said:
@Vadim Shved
Can you be more specific?
I use link2sd without problems to convert apps to system apps.
do this:
adb root
adb remount
what is the output?
Click to expand...
Click to collapse
I did everything from your tutorial. Root checker says that root is present. BUT! I cant do opearations with system partiotion. I tried to: 1)adb root 2)adb remount. After that in command promt I see that remount succeeded. Root checker say that root is present... But I still cant do anything. System partiotion cant be r/w
Edit: Sorry, but I thing that it is a problem of some apps that are not ready for android 5.1.x
Is there original rom available anywhere with tools to flash it? (got my vi7 in a state where it show only first "chuwi" logo, no "intel" logo - just black screen (but PC for example sees ADB interface; unfortunately "no permission"). I'm hoping that's only software problem.
Edit: CRANE_EVB firmware (seems to be some vi7 compatible device, not vi7 itself) finally worked. Required that I force (in devices manager) "intel usb driver for android devices" to be used for my detected chuwi vi7 "adb interface", then "adb.exe reboot ptest_clear" and it starts, no more black screen, no more "PTEST VER 1.41" problem etc.
Anyway still looking for original vi7 rom (not that crane_evb thing).
Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Updates - 01-Sept-2015
Huge Thanks to best98 for carrying out numerous of tests... :good:
Conclusion : No point to further develop custom recoveries, after unlocking bootloader, vi7 will refuse to boot unless you press Vol+ for 3 seconds then only it will boot up normally, no one would wanna do that...
{
"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"
}
best98 said:
Hi
So, I tried to flash stock 3e recovery..
Code:
"Warning: Chip mismatch. HW is [Sofia_3G_R] SW expects [Sofia_3G]
Device synchronized.
Using: Faster CRC, Writing all blocks , Skip data CRC , Skip protocol CRC
Start downloading item 'CUST:recovery.fls'' from file 'C:\Android\Chuwi_V7\stock-3e-recovery.fls''.
Checksum OK (0x0000)
Process time was 656 msec.
Total time was 1359 msec.
Channel 1 is succesfully closed."
Still boots with the green/red/black screen..
Did the fastboot eom lock
Code:
PS C:\> fastboot oem lock
...
(bootloader) Please confirm the device state action using the UI.
(bootloader) got key event 1
(bootloader) EV_DOWN received
(bootloader) got key event 2
(bootloader) EV_POWER received
(bootloader) Userdata erase required, this can take a while...
OKAY [ 11.506s]
finished. total time: 11.511s
Now, got the bootloop.. -> flashing the whole firmware : boots ok.
adb reboot fastboot
fastboot oem unlock
Code:
PS C:\> fastboot oem unlock
...
(bootloader) Please confirm the device state action using the UI.
(bootloader) got key event 1
(bootloader) EV_DOWN received
(bootloader) got key event 2
(bootloader) EV_POWER received
(bootloader) Userdata erase required, this can take a while...
OKAY [ 11.299s]
finished. total time: 11.300s
Black/green/red screen..
fastboot format cache + fastboot format data = same Black/green/red screen..
I hit 'Vol+' it goes forward.. shows Intel logo and boots..
Pierrick
Click to expand...
Click to collapse
fastboot oem unlock confirm
gets
< waiting for device >
and nothing else happens
yuweng said:
Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Click to expand...
Click to collapse
Is it possible to overclock this device? 900mhz.... it sucks.
Hmm.. I could try.. nothing to loose, but can't get the communication to work.
I unlocked the bootloader throug the Developer Option menu. Is it enough ?
yuweng said:
Anyone dare to flash TWRP pack with FlsTool, it should just brick the recovery only, if it doesn't work :fingers-crossed: then just flash back stock 3e recovery...
WARNING : Might brick your Vi7 but then again, you have the Firmware uploaded by OP to unbrick it... :laugh:
You might need to unlock the bootloader too...
Code:
adb reboot fastboot
fastboot oem unlock confirm
Click to expand...
Click to collapse
Thank You so much for participating in Development... :good:
Fyi, OP can't test b'cos he drop & break his vi7 while i'm having a different variance of x3...
First you need to unlock the bootloader & if you didn't then it will brick your vi7 but then again, you guys have the firmware to unbrick it...
Steps
If you're using Windows then download fastboot from here, if you're using linux then follow tips from OP
To reboot to fastboot => adb reboot fastboot -> There is no intel Droidboot, only green distorted screen but fastboot command works
To unlock bootloader -> fastboot oem unlock then follow PC on-screen for instructions & for formatting data & cache partition too. Mine have to issue the command fastboot oem unlock confirm
After this to reboot -> fastboot reboot
At PC, setup intel USB driver -> right click -> Run As Administrator
Start FlsTool -> Switch off your vi7 -> wait awhile -> Click at Next -> Click Start USB1 -> Plugin your vi7 & it'll download
After boot up Android -> adb reboot recovery & if TWRP doesn't boot then unplug USB, press & hold Power for 10 seconds & it power off then follow the same procedure to reinstall back stock 3e recovery
For more info, refer to the FlsTool attach pdf file for details
Additional info
At the Russian forum mentioned you'll need to check the option Manual (no auto start) while on my x3 with default Auto Start works fine...
Hi
Not changing the bootloader butusing a mix of the OP script and Chinese tablet -Intel Root- script worked.
One of the big deal was to have the ADB compatibility with "disable-verity" which is the last release.
Now, I will try to focus on TWRP.. but FLS with COM to USB mapping makes it a little bit complicated !
Pierrick
OK.. just tried this, and now, I have a green screen ..
Rolling back the 3e recovery worked but the result is still showing me, black/green and red lines.
Right now, tablet does not boot anymore, except those lines in green/black and red.. where no text is written - looks like locked inl in fastboot.
Willing to hear from you to get back the control of the tablet
Here are the settings I used - thumbnail !
BTW - attaching adb.exe that handles the disable-verity
yuweng said:
Thank You so much for participating in Development... :good:
Fyi, OP can't test b'cos he drop & break his vi7 while i'm having a different variance of x3...
First you need to unlock the bootloader & if you didn't then it will brick your vi7 but then again, you guys have the firmware to unbrick it...
Steps
If you're using Windows then download fastboot from here, if you're using linux then follow tips from OP
To reboot to fastboot => adb reboot fastboot -> There is no intel Droidboot, only green distorted screen but fastboot command works
To unlock bootloader -> fastboot oem unlock then follow PC on-screen for instructions & for formatting data & cache partition too. Mine have to issue the command fastboot oem unlock confirm
After this to reboot -> fastboot reboot
At PC, setup intel USB driver -> right click -> Run As Administrator
Start FlsTool -> Switch off your vi7 -> wait awhile -> Click at Next -> Click Start USB1 -> Plugin your vi7 & it'll download
After boot up Android -> adb reboot recovery & if TWRP doesn't boot then unplug USB, press & hold Power for 10 seconds & it power off then follow the same procedure to reinstall back stock 3e recovery
For more info, refer to the FlsTool attach pdf file for details
Additional info
At the Russian forum mentioned you'll need to check the option Manual (no auto start) while on my x3 with default Auto Start works fine...
Click to expand...
Click to collapse
I need to warranty a phone but I need to turn it back to stock. I am using an older version of TWRP, I am guessing here but do I just download the factory image and flash it and I am done? It seems like everything I get when searching is geared towards the Pixel XL and using ADB rather than TWRP.
Thanks in advance.
Beacuse I part time as an internet troll, I have to chastise you for not reading threw this forum, because well that's why it's there, but hey we all can't use our Brian's all the time, but yes download the factory image for your phone Marlin for Pixel XL and Sailfish for Pixel unzip the file, make sure you have lastest usb drivers installed and click the flash all.bat.
Fastboot and flash factory image.
A wonderful guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
jerryhou85 said:
Fastboot and flash factory image.
A wonderful guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
Click to expand...
Click to collapse
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
I'm not a good developer so I cannot answer you that question, but on Google official page, it is recommended to use fastboot or adb to flash factory images...
twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
Because recovery and boot are sort of intermingled now. You would be writing over twrp at the same time you are trying to use it to flash.
Use the flashall bat file. If you want to save data edit out the -w from the bat file.
twilk73 said:
why do I have to fastboot or ADB cant I just boot into twrp and flash factory image?
Click to expand...
Click to collapse
I am on linux let me just get that out of the way.
So I used adb to fastboot the factory image but nothing happens
the file is in downloads and in the fastboot file. So I type cd Downloads, cd fastboot, fastboot sailfish-nmf260 it all looks good and you can tell adm is working but nothing happens on the phone.
I am current only able to get the phone into fastboot mode I dont know what I messed up but I can no longer even boot into TWRP.
I must have succesfully removed the twrp recovery because no i get the no command screen. If I hold power and press up I can get into the stock android recovery. Is there a way to install the factory image still? Or is the process still the same and I need to adb fastboot? I might need to just do the abd fastboot on a windows computer at work tomorrow.
twilk73 said:
I must have succesfully removed the twrp recovery because no i get the no command screen. If I hold power and press up I can get into the stock android recovery. Is there a way to install the factory image still? Or is the process still the same and I need to adb fastboot? I might need to just do the abd fastboot on a windows computer at work tomorrow.
Click to expand...
Click to collapse
Download the factory image you want here. Unzip the entire contents to the same folder fastboot is located in. Then boot the phone to the bootloader, then plug it in to you computer. Then, if you're using Linux, double click the flash-all.sh file that got unzipped to your fastboot folder. If you're using a Windows computer, double click on the flash-all. bat file instead of the flash-all.sh file. Then sit back and wait. That's about all there is to it. One note. If you want to save your data, open the script you're going to use in a text editor and remove the -w toward the end of the script (remember to save your changes). If you want the phone wiped clean and like new again, just leave it as is.
robocuff said:
Download the factory image you want here. Unzip the entire contents to the same folder fastboot is located in. Then boot the phone to the bootloader, then plug it in to you computer. Then, if you're using Linux, double click the flash-all.sh file that got unzipped to your fastboot folder. If you're using a Windows computer, double click on the flash-all. bat file instead of the flash-all.sh file. Then sit back and wait. That's about all there is to it. One note. If you want to save your data, open the script you're going to use in a text editor and remove the -w toward the end of the script (remember to save your changes). If you want the phone wiped clean and like new again, just leave it as is.
Click to expand...
Click to collapse
ive done these steps but its failing to work. This is exactly what I am doing.
1. Download factory image.
2. Extract factory image into fastboot file.
the fast boot file is in the dowloads folder so I type.
cd Downloads
cd fastboot
fastboot flash-all.sh
iv also tried fastboot the sailfish-nmf260.img and boot.img and flashall. Ive tried several different ways this is what happens no mater what I type.
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
Click to expand...
Click to collapse
On the phone nothing happens. It appears that all I am getting is a list of options but none of the options seem to be working either.
I might add that the fastboot folder I am using was downloaded back when I installed twrp is it possible my fastboot file doesnt have the correct files to get the job done?
twilk73 said:
ive done these steps but its failing to work. This is exactly what I am doing.
1. Download factory image.
2. Extract factory image into fastboot file.
the fast boot file is in the dowloads folder so I type.
cd Downloads
cd fastboot
fastboot flash-all.sh
iv also tried fastboot the sailfish-nmf260.img and boot.img and flashall. Ive tried several different ways this is what happens no mater what I type.
On the phone nothing happens. It appears that all I am getting is a list of options but none of the options seem to be working either.
I might add that the fastboot folder I am using was downloaded back when I installed twrp is it possible my fastboot file doesnt have the correct files to get the job done?
Click to expand...
Click to collapse
Have you tried putting phone in fastboot mode and doubble click the flash all.sh file? That's how it is done on Windows.
Sent from my Google Pixel using XDA Labs
Sgace said:
Have you tried putting phone in fastboot mode and doubble click the flash all.sh file? That's how it is done on Windows.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.
twilk73 said:
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.
Click to expand...
Click to collapse
I don't think you can flash it with fastboot. In Windows, at the command prompt, you just type flash-all.bat and the batch file will run. It contains all the necessary fastboot commands. Perhaps that's where you're going wrong. Try just typing flash-all.sh. Leave the fastboot out.
twilk73 said:
Basically yes. But with linux you cant just double click. So in terminal I typed "cd Download, cd fastboot, fastboot flash-all.sh" that command will attempt to launch that file.
I feel like the issue is with adb on my laptop I tried making sure its updated but i got nothing so ill try to do it on a work computer when I get free time.
Its pretty crappy right now because I am without a phone but heck I pet the dog today during lunch instead of reading the news feed off my phone so I guess the dog is happy lol.
Click to expand...
Click to collapse
Try this for sailfish (fix accordingly if marlin, username of course is common sense, if still confused, you shouldn't be using linux)
I build and use debian sid
Code:
cd /home/username/Downloads
tar xvf sailfish-opr3.170623.008-factory-bb8bb3a3.zip -C /home/username
cd /home/username/sailfish-opr3.170623.008
tar xvf image-sailfish-opr3.170623.008.zip
cd /home/username/sailfish-opr3.170623.008
./flash-all.sh
If you need the latest adb/fastboot name it something like google.sh
Code:
#!/bin/bash
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
cp platform-tools/adb /usr/bin/adb
cp platform-tools/fastboot /usr/bin/fastboot
piperx said:
Try this for sailfish (fix accordingly if marlin, username of course is common sense, if still confused, you shouldn't be using linux)
I build and use debian sid
Code:
cd /home/username/Downloads
tar xvf sailfish-opr3.170623.008-factory-bb8bb3a3.zip -C /home/username
cd /home/username/sailfish-opr3.170623.008
tar xvf image-sailfish-opr3.170623.008.zip
cd /home/username/sailfish-opr3.170623.008
./flash-all.sh
If you need the latest adb/fastboot name it something like google.sh
Code:
#!/bin/bash
wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip \platform-tools-latest-linux.zip
cp platform-tools/adb /usr/bin/adb
cp platform-tools/fastboot /usr/bin/fastboot
Click to expand...
Click to collapse
Sorry I wish I could try this. I had access to a windows computer at work and I was able to get everything done. After doing it at work I have a feeling I wasnt placing the files in the correct folder together to get it to start the update. It can be hard doing this on something other than windows for a dummy like me because most of the tutorials for things like this seem to be windows oriented. Regardless its done. I couldnt lock the boot loader on the windows computer though oddly but no big deal because I can do it on my laptop.
Thanks for all the help guys.