Related
I have a droid incredible that I recently found out how to unlock and I would like to flash a ROM but on the offical thread that I followed I unlocked it but when I got to the recovery part when it asked me to list devices it didn't show any And I'm not able to do the rest of the stuff either thanks for the help
Sent from my SGH-T989
Trozzul said:
I have a droid incredible that I recently found out how to unlock and I would like to flash a ROM but on the offical thread that I followed I unlocked it but when I got to the recovery part when it asked me to list devices it didn't show any And I'm not able to do the rest of the stuff either thanks for the help
Sent from my SGH-T989
Click to expand...
Click to collapse
You need to install and setup the adb drivers on your pc. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
cmlusco said:
You need to install and setup the adb drivers on your pc. http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
are you talking about the sdk usb drivers?
Trozzul said:
are you talking about the sdk usb drivers?
Click to expand...
Click to collapse
Not exactly, the drivers in the link are modified from the ones in the sdk. If installed correctly with the phone plugged in, under device manager there will be an android bootloader interface entry.
i followed your guide up to the downgrading point and didnt work. i tried this thread too http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html and i get this
C:\Android>adb shell
$ su
su
# cd /data/local
chmod 0755 /data/local/flash_imagecd /data/local
#
chmod 0755 /data/local/flash_image
# cd /data/local
./flash_image misc /sdcard/mtd0.imgcd /data/local
#
./flash_image misc /sdcard/mtd0.img
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00080000
error writing misc: No space left on device
#
i have plenty of space on here. does it require more than 2gb?
Trozzul said:
i followed your guide up to the downgrading point and didnt work. i tried this thread too http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html and i get this
C:\Android>adb shell
$ su
su
# cd /data/local
chmod 0755 /data/local/flash_imagecd /data/local
#
chmod 0755 /data/local/flash_image
# cd /data/local
./flash_image misc /sdcard/mtd0.imgcd /data/local
#
./flash_image misc /sdcard/mtd0.img
mtd: read all-zero block at 0x00000000; skipping
mtd: not writing bad block at 0x00080000
error writing misc: No space left on device
#
i have plenty of space on here. does it require more than 2gb?
Click to expand...
Click to collapse
I belive what its saying is your misc partition is fubar. This means your partition tables are jacked, and the phone is essentially soft-bricked.
so what do i do? i am still able to use it
Trozzul said:
so what do i do? i am still able to use it
Click to expand...
Click to collapse
It is probably physically broken. You can try to flash an ruu and see if it takes, but im thinking a needed portion of your flash memory has been damaged or corrupted beyond repair.
I saw ruu on how to unlock the bootloader. I have tired looking it up but nothing comes up .
Trozzul said:
I saw ruu on how to unlock the bootloader. I have tired looking it up but nothing comes up .
Click to expand...
Click to collapse
Download and place this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip on your sdcard in no folders, do not rename it. Then boot to hboot (vol down + power), it should find the file and prompt you to press vol up to install. If it dosent find the file, you may need to reformat the sdcard fa32 and then try again.
Thanks I'll try this tomorrow hope it works! I just only want to flash a ROM I think the stock is very ugly
Sent from my SGH-T989
alright i have done what you asked do i try the part i was stuck on again? (and btw what did that file do?)
Trozzul said:
alright i have done what you asked do i try the part i was stuck on again? (and btw what did that file do?)
Click to expand...
Click to collapse
That was the latest ruu (rom update utility), it is ment to redo the entire phone and put it like it was fresh out of the box. If it fixed the phone you should be able to boot to the os like norrmal. Did it flash ok, any errors?
No errors worked perfectly
Trozzul said:
No errors worked perfectly
Click to expand...
Click to collapse
So the phone is working?
yes but it looks like no more root do i start over now?
Trozzul said:
yes but it looks like no more root do i start over now?
Click to expand...
Click to collapse
Yes are you s-off? If not you need to unlock the bootloader again.
I lied about it working apps wont open update or install i can open the playstore and i was unlocked befor but didnt have s-off i thought i was getting the that part in the thread
Nevermind about the apps i reset the phone and its fine. Sorry im not that bright...
Trozzul said:
Nevermind about the apps i reset the phone and its fine. Sorry im not that bright...
Click to expand...
Click to collapse
Yeah you need to unlock again by fastboot flashing the unlock_token they sent you before. You can follow this guide http://forum.xda-developers.com/showthread.php?t=1506258.
Archos 97 Root and custom recovery step by step n00b guide.
Download files
rkflashtool http://sourceforge.net/projects/rkflashtool
ARCHOS 97 Titanium HD custom recovery from http://androtab.info/clockworkmod/rockchip/rk3066/
Edit rkflashtool.c, add 0x300a line
if (!(h = libusb_open_device_with_vid_pid(c, 0x2207, 0x290a)))
if (!(h = libusb_open_device_with_vid_pid(c, 0x2207, 0x281a)))
if (!(h = libusb_open_device_with_vid_pid(c, 0x2207, 0x300a)))
fatal("cannot open device\n");
Click to expand...
Click to collapse
comile rkflashtool with libusb
sudo apt-get install libusb-1.0-0-dev
gcc -o rkflashtool rkflashtool.c -lusb-1.0 -O2 -W -Wall -s
connect tablet USB to PC
power off tablet
hold volume- and insert charging cable
release volume- after screen turns on
dump system
sudo ./rkflashtool r 0x00154000 0x00100000 > system.loop
edit system, disable install-recovery.sh
sudo mount -o loop system.loop /loop
cd /loop/etc
sudo chmod 644 install-recovery.sh
flash system back to device
sudo ./rkflashtool w 0x00154000 0x00100000 < system.loop
backup original recovery and flash CWM recovery.img
sudo ./rkflashtool r 0x00010000 0x00008000 > recovery.backup
sudo ./rkflashtool w 0x00010000 0x00008000 < recovery.img
reboot to recovery (hold volume-, connect power cable)
donwload and install SuperSU.zip
Maybe you can add to the tutorial, howto restore the original content, so that it looks like "untouched".
starbright_ said:
Maybe you can add to the tutorial, howto restore the original content, so that it looks like "untouched".
Click to expand...
Click to collapse
Flash "recovery.backup" back you made in step 8. and delete super user app, that's it.
Though nobody checks those things anyway.
Additional info on partition offsets
MACHINE_MODEL:ARCHOS 97 TITANIUMHD
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000
mtdparts=rk29xxnand:
[email protected](misc),
[email protected](kernel),
[email protected](boot),
[email protected](recovery),
[email protected](backup),
[email protected](cache),
[email protected](kpanic),
[email protected](system),
[email protected](userdata)
Click to expand...
Click to collapse
Does this work on the Familypad 2? If not, are there any known methods to achieve root on the Familypad 2?
Thanks.
Moved Files
The Repository has been removed; what do you from this point?
GIgantorFNS said:
The Repository has been removed; what do you from this point?
Click to expand...
Click to collapse
it wasn't http://sourceforge.net/p/rkflashtool/code/HEAD/tree/trunk/
GIgantorFNS said:
The Repository has been removed; what do you from this point?
Click to expand...
Click to collapse
Thank you! It's there; beit that this is my first time rooting a tablet-I have NO idea what I do after this point!
Hmm.... I can't mount system.loop !
Everything works fine. but if i try to mount system.loop i'll get no access.
If i type in:
sudo mount -o loop system.loop /loop
Ubuntu tells me /loop does not exist.
Where is the error?
Can someone help?
THX LaGra
all working file. thank you for your tuto
:laugh:
LaGra said:
sudo mount -o loop system.loop /loop
Ubuntu tells me /loop does not exist.
Click to expand...
Click to collapse
you need to create /loop folder first.
Originalas said:
you need to create /loop folder first.
Click to expand...
Click to collapse
Sorry, but still not working.
Where i have to create that folder?
Linux is not my best.
my english too......
I have put an update on the tablet from archos. Maybe is that my fail.
LaGra said:
Sorry, but still not working.
Where i have to create that folder?
Click to expand...
Click to collapse
Try
sudo mkdir -p /mnt/loop
sudo mount -o loop system.loop /mnt/loop
Originalas said:
Try
sudo mkdir -p /mnt/loop
sudo mount -o loop system.loop /mnt/loop
Click to expand...
Click to collapse
Thanks a lot for your help.
Now its working. :good:
Hi, I can't get through number 5, ie dump system with "sudo ./rkflashtool r 0x00154000 0x00100000 > system.loop".
Every time I get "rkflashtool: fatal: cannot open device". Tablet is in recover mode and connected through USB.
The only difference - I'm using Linux Mint 14. Is that the problem?
type in terminal
lsusb
does your device show up in the list? Is it under name "0x2207, 0x300a"? or something like "Google Android"?
Check drivers, try differrent USB port, if tablet doesn't show up in the list at all.
If it's under other name, not "0x2207, 0x300a", then you haven't entered flashing mode properly.
Turn off tablet, connect usb, hold volume down button and connect power supply without releasing volume down for 10s. Then try lsusb again.
Originalas said:
type in terminal
lsusb
does your device show up in the list? Is it under name "0x2207, 0x300a"? or something like "Google Android"?
Check drivers, try differrent USB port, if tablet doesn't show up in the list at all.
If it's under other name, not "0x2207, 0x300a", then you haven't entered flashing mode properly.
Turn off tablet, connect usb, hold volume down button and connect power supply without releasing volume down for 10s. Then try lsusb again.
Click to expand...
Click to collapse
Thanks a lot for your reply.
In normal mode it shows as "Bus 003 Device 008: ID 0e79:14ad Archos, Inc.", but it doesn't show at all in recovery mode.
What might be the problem?
Ok, now i can go into CWM.
Superuser is installed. But if I start the tablet it does not boot
anymore!
Everytime it goes back to recovery menu.
nyboy1 said:
Thanks a lot for your reply.
In normal mode it shows as "Bus 003 Device 008: ID 0e79:14ad Archos, Inc.", but it doesn't show at all in recovery mode.
What might be the problem?
Click to expand...
Click to collapse
you haven't set tablet to flash mode.
Originalas said:
Turn off tablet, connect usb, hold volume down button and connect power supply without releasing volume down for 10s. Then try lsusb again.
Click to expand...
Click to collapse
Originalas said:
you haven't set tablet to flash mode.
Click to expand...
Click to collapse
Hi, thanks for your reply. I managed to get to number 6 now)
[email protected]:~$ sudo mkdir -p /mnt/loop
[email protected]:~$ sudo mount -o loop system.loop /mnt/loop
mount: according to mtab /home/ubuntu/system.loop is already mounted on /mnt/loop as loop
[email protected]:~$ cd /loop/etc
bash: cd: /loop/etc: No such file or directory
Can't understand where mistake was made. I'd appreciate your help. Thank you.
Well, if you created mount in /mnt/loop, path should be like
cd /mnt/loop/etc
You can use graphical file explorer, to check directories too..
hi
i flash a system image in the boot partition using FlashTool progrem
And I changed kernel
Only now I realized I needed to use fastboot and command prompt to flash the img file to the system partition.
And when I do that it tells me "flash operation complete"
But the kernel is not replaced!!??!!
i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
what i can do?
tnx!!!
mmoti6 said:
hi
i flash a system image in the boot partition using FlashTool progrem
And I changed kernel
Only now I realized I needed to use fastboot and command prompt to flash the img file to the system partition.
And when I do that it tells me "flash operation complete"
But the kernel is not replaced!!??!!
i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
what i can do?
tnx!!!
Click to expand...
Click to collapse
Have you tried Flashing Stock Firmware?
Here is a Thread where you can download Official Stock Firmwares for the Xperia Play(Post #2):
Xperia Play Index - ROM'S, FIRMWARE, KERNEL'S, GUIDE'S, THEMES, MOD'S
mmoti6 said:
hi
i flash a system image in the boot partition using FlashTool progrem
And I changed kernel
Only now I realized I needed to use fastboot and command prompt to flash the img file to the system partition.
And when I do that it tells me "flash operation complete"
But the kernel is not replaced!!??!!
i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
what i can do?
tnx!!!
Click to expand...
Click to collapse
TheScriptKitty said:
Have you tried Flashing Stock Firmware?
Here is a Thread where you can download Official Stock Firmwares for the Xperia Play(Post #2):
Xperia Play Index - ROM'S, FIRMWARE, KERNEL'S, GUIDE'S, THEMES, MOD'S
Click to expand...
Click to collapse
i download r800a_N.A+Generic_4.0.A.2.368.rar ---- r800a stock firmware
and i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
And when I do that it tells me "flash operation complete" but still he didnt work....
in FlashTool is tell me
"FAILED (remote: Image won't fit, partition too small!)"
help plizz
mmoti6 said:
i download r800a_N.A+Generic_4.0.A.2.368.rar ---- r800a stock firmware
and i try QuikIMG-0.2-beta and the fastboot and command prompt to flash the img file to the system partition and this didnt work....
And when I do that it tells me "flash operation complete" but still he didnt work....
in FlashTool is tell me
"FAILED (remote: Image won't fit, partition too small!)"
help plizz
Click to expand...
Click to collapse
Are you trying to Flash it via Fastboot Mode?
You have to change the File Extension from .rar to .ftf , and then Flash it via FLASH MODE (NOT Fastboot Mode) in FlashTool.
pliz help
TheScriptKitty said:
Are you trying to Flash it via Fastboot Mode?
You have to change the File Extension from .rar to .ftf , and then Flash it via FLASH MODE (NOT Fastboot Mode) in FlashTool.
Click to expand...
Click to collapse
ok i change to Official Stock Firmwares for the Xperia Play (i think i chose the right one...)
but still tells me "flash operation complete"
but he didnt change the karnal
NexPlay_rk1_GSM/semc-kernel-msm7x30-jellybean
pliz help....
And model of cell phone is R800a
And he shows me "INFO - Current device : R800i - CB5A1GM5GZ - 1247-8563_R13D - 1245-8821_4.0.2.A.0.79 - VFE-1-8_4.0.2.A.0.79"
y?
mmoti6 said:
ok i change to Official Stock Firmwares for the Xperia Play (i think i chose the right one...)
but still tells me "flash operation complete"
but he didnt change the karnal
NexPlay_rk1_GSM/semc-kernel-msm7x30-jellybean
pliz help....
And model of cell phone is R800a
And he shows me "INFO - Current device : R800i - CB5A1GM5GZ - 1247-8563_R13D - 1245-8821_4.0.2.A.0.79 - VFE-1-8_4.0.2.A.0.79"
y?
Click to expand...
Click to collapse
If you Flashed the Stock Firmware for your phone and you say that the kernel has not changed how are you able to see what kernel you have if the phone should not be able to boot(Because it would be like trying to use a Costume ICS kernel on the Stock GB ROM)???
help pliz
TheScriptKitty said:
If you Flashed the Stock Firmware for your phone and you say that the kernel has not changed how are you able to see what kernel you have if the phone should not be able to boot(Because it would be like trying to use a Costume ICS kernel on the Stock GB ROM)???
Click to expand...
Click to collapse
if i Flashed the Stock Firmware for my phone the phone shows me this
(sony logo in boot screen)
and the phone is good and working
but then i Flashed a kernel like this
(LuPuS logo in boot screen)
but it still shows me this
(sony logo in boot screen)
and the phone is stuck on it
y?
mmoti6 said:
if i Flashed the Stock Firmware for my phone the phone shows me this
(sony logo in boot screen)
and the phone is good and working
but then i Flashed a kernel like this
(LuPuS logo in boot screen)
but it still shows me this
(sony logo in boot screen)
and the phone is stuck on it
y?
Click to expand...
Click to collapse
Have you flashed a Custom ROM?
If you have, please specify exactly what version of the Lupus Kernel and what ROM you are using.
And if you have not flashed a Custom ROM, as I said before trying to use a Custom Kernel on the Stock ROM will not work(it will not boot in most cases), you need to Flash a Custom ROM that is compatible with the Lupus Kernel you are using.
TheScriptKitty said:
Have you flashed a Custom ROM?
If you have, please specify exactly what version of the Lupus Kernel and what ROM you are using.
And if you have not flashed a Custom ROM, as I said before trying to use a Custom Kernel on the Stock ROM will not work(it will not boot in most cases), you need to Flash a Custom ROM that is compatible with the Lupus Kernel you are using.
Click to expand...
Click to collapse
you can recmmnded on a Firmwar?
i use to root the phone whit superonclick and this is what i get:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$
export TEMPRANDOM=65947;export PS1=END:$TEMPRANDOM;getprop ro.build.version.release
export PS1=""
$ 2.2.1
END:65947
export TEMPRANDOM=87695;export PS1=END:$TEMPRANDOM;getprop ro.product.manufacturer
export PS1=""
LGE
END:87695
export TEMPRANDOM=35445;export PS1=END:$TEMPRANDOM;getprop ro.product.model
export PS1=""
LG-P500h
END:35445
export TEMPRANDOM=50395;export PS1=END:$TEMPRANDOM;getprop ro.build.version.incremental
export PS1=""
eng.donghyun.seo.20110215.151731
END:50395
export TEMPRANDOM=25205;export PS1=END:$TEMPRANDOM;ls -l /system/xbin/su
export PS1=""
/system/xbin/su: No such file or directory
END:25205
export TEMPRANDOM=29466;export PS1=END:$TEMPRANDOM;ls -l /system/bin/su
export PS1=""
-rwsr-sr-x root root 380532 2012-08-07 13:01 su
END:29466
export TEMPRANDOM=48004;export PS1=END:$TEMPRANDOM;chmod 755 /data/local/tmp/busybox
export PS1=""
END:48004
export TEMPRANDOM=92630;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/boomsh
export PS1=""
rm failed for /data/local/tmp/boomsh, No such file or directory
END:92630
export TEMPRANDOM=17806;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/sh
export PS1=""
rm failed for /data/local/tmp/sh, No such file or directory
END:17806
export TEMPRANDOM=60041;export PS1=END:$TEMPRANDOM;chmod 700 /data/local/tmp/zergRush
export PS1=""
Unable to chmod /data/local/tmp/zergRush: No such file or directory
END:60041
export TEMPRANDOM=98014;export PS1=END:$TEMPRANDOM;cd /data/local/tmp/
export PS1=""
END:98014
export TEMPRANDOM=32459;export PS1=END:$TEMPRANDOM;./zergRush
export PS1=""
./zergRush: not found
END:32459
Click to expand...
Click to collapse
how i install the zergRush?
tnx
editing
i Flashing Stock Firmware r800i 4.0.2.A.0.62 firmware (but my phone is r800a...)
i use to root the phone whit superonclick and this is what i get:
$TEMPRANDOM;getprop ro.build.version.release
2.3.4
END:97116export PS1=""
export TEMPRANDOM=37017;export PS1=END:$TEMPRANDOM;getprop ro.product.manufacturer
Sony Ericsson
END:37017export PS1=""
export TEMPRANDOM=31785;export PS1=END:$TEMPRANDOM;getprop ro.product.model
R800i
END:31785export PS1=""
export TEMPRANDOM=65498;export PS1=END:$TEMPRANDOM;getprop ro.build.version.incremental
wf_v3w
END:65498export PS1=""
export TEMPRANDOM=13472;export PS1=END:$TEMPRANDOM;ls -l /system/xbin/su
/system/xbin/su: No such file or directory
END:13472export PS1=""
export TEMPRANDOM=80897;export PS1=END:$TEMPRANDOM;ls -l /system/bin/su
/system/bin/su: No such file or directory
END:80897export PS1=""
export TEMPRANDOM=71628;export PS1=END:$TEMPRANDOM;chmod 755 /data/local/tmp/busybox
END:71628export PS1=""
export TEMPRANDOM=96072;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/boomsh
rm failed for /data/local/tmp/boomsh, No such file or directory
END:96072export PS1=""
export TEMPRANDOM=66092;export PS1=END:$TEMPRANDOM;rm /data/local/tmp/sh
rm failed for /data/local/tmp/sh, No such file or directory
END:66092export PS1=""
export TEMPRANDOM=93376;export PS1=END:$TEMPRANDOM;chmod 700 /data/local/tmp/zergRush
Unable to chmod /data/local/tmp/zergRush: No such file or directory
END:93376export PS1=""
export TEMPRANDOM=27821;export PS1=END:$TEMPRANDOM;cd /data/local/tmp/
END:27821export PS1=""
export TEMPRANDOM=97862;export PS1=END:$TEMPRANDOM;./zergRush
./zergRush: not found
END:97862export PS1=""
Click to expand...
Click to collapse
y?
mmoti6 said:
you can recmmnded on a Firmwar?
i use to root the phone whit superonclick and this is what i get:
how i install the zergRush?
tnx
editing
i Flashing Stock Firmware r800i 4.0.2.A.0.62 firmware (but my phone is r800a...)
i use to root the phone whit superonclick and this is what i get:
y?
Click to expand...
Click to collapse
Okay first of all, I don't think you understand the difference between a ROM, Kernel, and Firmware so I'll explain that first:
A ROM (In Android) is basically like the OS, it contains all the software you see and use on the phone. The kernel would be what connects the ROM (the OS) with the phone's hardware. A firmware would be a combination of both a Kernel and a ROM and its most commonly used to describe the Original ROM and Kernel of the phone (Stock Firmware). Please confirm that you Understand.
Now, I have never used SuperOneclick to root the Xperia Play so I really can't tell you what you are doing wrong. If you want, use zergRush. You don't have to install it, here is the basic procedure:
download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
[04/Jan][ROOTING/UNROOTING] Xperia 2011 Easy Rooting Toolkit [v4.0](zergRush Exploit)
I don't think you will have any problems if you Flashed a R800i Firmware on a R800a, but just to be sure use Firmware made for your phone.
And if what you mean by "what Firmware I recommend" is what ROM do I recommend, here it is:
If you want Gingerbread(Android 2.3): Gin2KitKat
If you want ICS(Android 4.0): Xperia Play Z
If you want Jellybean(Android 4.1.2): Racing SPEED EDITION EOL or Super Lite Jelly Bean
For each ROM you have to install the Kernel it tells you to(Read instructions). I also want to add that their is no such thing as a best ROM, each ROM has its Pros and Cons, and what might appeal to me might not to you. I would recommend for you to try different ROMs and see what suits you.
And last, Please Click on the Thanks Button
.
.
TheScriptKitty said:
Okay first of all, I don't think you understand the difference between a ROM, Kernel, and Firmware so I'll explain that first:
A ROM (In Android) is basically like the OS, it contains all the software you see and use on the phone. The kernel would be what connects the ROM (the OS) with the phone's hardware. A firmware would be a combination of both a Kernel and a ROM and its most commonly used to describe the Original ROM and Kernel of the phone (Stock Firmware). Please confirm that you Understand.
Now, I have never used SuperOneclick to root the Xperia Play so I really can't tell you what you are doing wrong. If you want, use zergRush. You don't have to install it, here is the basic procedure:
download the attached file, extract it using winzip/winrar
go to the folder where its extracted and execute "RUNME.bat"
read and follow the instructions on the screen!
[04/Jan][ROOTING/UNROOTING] Xperia 2011 Easy Rooting Toolkit [v4.0](zergRush Exploit)
I don't think you will have any problems if you Flashed a R800i Firmware on a R800a, but just to be sure use Firmware made for your phone.
And if what you mean by "what Firmware I recommend" is what ROM do I recommend, here it is:
If you want Gingerbread(Android 2.3): Gin2KitKat
If you want ICS(Android 4.0): Xperia Play Z
If you want Jellybean(Android 4.1.2): Racing SPEED EDITION EOL or Super Lite Jelly Bean
For each ROM you have to install the Kernel it tells you to(Read instructions). I also want to add that their is no such thing as a best ROM, each ROM has its Pros and Cons, and what might appeal to me might not to you. I would recommend for you to try different ROMs and see what suits you.
And last, Please Click on the Thanks Button
.
.
Click to expand...
Click to collapse
ok
new i get this
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1407 KB/s (23060 bytes in 0.016s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2949 KB/s (1075144 bytes in 0.356s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
107 KB/s (439 bytes in 0.004s)
df: /mnt/secure/asec: Permission denied
export: 65964: bad variable name
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
y?
mmoti6 said:
ok
new i get this
y?
Click to expand...
Click to collapse
It look like it failed to Root the device at the beginning, so it fail to do the rest of the stuff.
Are you sure you did all this?:
Make sure u have installed adb drivers for ur device
Enable "USB DEBUGGING" from (Menu\Settings\Applications\Development)
Enable "UNKNOWN SOURCES" from (Menu\Settings\Applications)
[OPTIONAL]Increase screen timeout to 10 minutes
Connect USB cable to PHONE and then connect to PC
Skip "PC Companion Software" prompt on device
TheScriptKitty said:
It look like it failed to Root the device at the beginning, so it fail to do the rest of the stuff.
Are you sure you did all this?:
Make sure u have installed adb drivers for ur device
Enable "USB DEBUGGING" from (Menu\Settings\Applications\Development)
Enable "UNKNOWN SOURCES" from (Menu\Settings\Applications)
[OPTIONAL]Increase screen timeout to 10 minutes
Connect USB cable to PHONE and then connect to PC
Skip "PC Companion Software" prompt on device
Click to expand...
Click to collapse
yes i am wure...
Zergrush can't root .62 (and above) firmware. Only .42 and bellow
Bakisha said:
Zergrush can't root .62 (and above) firmware. Only .42 and bellow
Click to expand...
Click to collapse
but onli the North America firmware is 42 and i am not from North America...
what i can do?
mmoti6 said:
but onli the North America firmware is 42 and i am not from North America...
what i can do?
Click to expand...
Click to collapse
It doesn't matter, it works fine with it.
TheScriptKitty said:
It doesn't matter, it works fine with it.
Click to expand...
Click to collapse
i dont see the firmware in the flashtool tool
i change it to ftf and i have 2 firmware
1.R800a_2.3.4_North America Generic (1)
2.R800a_4.0.2.A.0.42_North America
i cant see them....
you can recmmnded what to do?
i must to flash anther firmware ?
or i can only to flashe rom and carnal to get 42 or bellow firmware?
mmoti6 said:
i change it to ftf and i have 2 firmware
Click to expand...
Click to collapse
I recommend unpacking those two rar files to get ftf files, not renaming them from rar to ftf
Bakisha said:
I recommend unpacking those two rar files to get ftf files, not renaming them from rar to ftf
Click to expand...
Click to collapse
i still dont show tham on the flash tool
1.R800a_2.3.4_North America Generic (1) - i unpacking to ftf file
2.R800a_4.0.2.A.0.42_North America - i renaming from rar to ftf
i cant see them....
you can recmmnded what to do?
i must to flash anther firmware ?
or i can only to flashe rom and carnal to get 42 or bellow firmware?
tnx
Use latest version of flashtool http://flashtool.net
Find ftf firmware files at http://forum.xda-developers.com/showthread.php?t=2184897
Make sure you download correct firmware for your model (r800i/a/x)
The easiest way to get root on stock r800i
1: flash .42 firmware and root it with zerg-rush
2: flash .79 firmware and flash doomlord gb kernel
Sent from my R800i using XDA Free mobile app
I am not responsible for whatever may happen to you or your device when using this, Run this at your own risk!!
Requires unlocked bootloader!
Based on SuperSU - v4.46 (the binary updates from within the app later on)
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LMY47D - root-boot
For past firmware:
LRX21V - root-boot
For past firmware:
LRX21M - root-boot
crappy video but simple demonstration :good:How to install:
Download the zip depending on your Nexus Player's firmware than extract & run root-boot.bat (Other operating system support coming soon for the installer script) Made on windows 7
Follow and read the on screen instruction carefully
Click to expand...
Click to collapse
SU app and binarys gets installed to /system/* directory's, The insecure boot.img gets installed to be able to access root adb shell and install those binarys
The root-boot boot.img is temporarily booted once during this process on the first boot of installation, it does not flash the boot.img
The previous boot.img before the installation is restored after SU is installed
Click to expand...
Click to collapse
Thanks @Chainfire for Superuser
My Donation Box
Troubleshooting:
Check to make sure your device gets picked up in adb before running the script - - - ADB Drivers
This tool uses an unlocked bootloader and i have not unlocked mine yet, does unlocking the bootloader wipe the device? - - - Yes unlocking the bootloader will wipe the device
After fastboot flashed the boot.img than rebooted to the home screen i continued the the script like the installation steps said but it returned "device not found" - - - As long as it shows transferring files a few seconds after than its fine, adb restarts at that moment which will than return "device not found" than it reconnects and transfers. if fastboot flashed than rebooted fine than adb shouldn't have an issue
Help! Something went wrong and im bootlooping but i dont want to loose all my saved data - - - Everything is fine, Download the factory zip from here for your android version than extract the zip and retrieve the system.img and copy it into a folder that contains adb/fastboot and boot your device into fastboot mode and do "fastboot flash system system.img" doing it this way wont wipe your "/data" partition leaving everything intact but will restore the system back to its defaults
(If you were to run the factory zip as an update than it would format everything)
I installed SU with this method but cant use adb commands on my device - - - Go into "Settings>About" and click on "Build" 7 times very fast and it will enable "Developer options" in the settings menu, Go back to the settings menu and open developer options (You may need to reboot if it doesnt show up immediately) and enable the "USB debugging" option
Ill be updating this as new version of lollipop get released
support for both firmwares are up, any issues let me know i tested them both though and everything looked okay
Reuploading, had a minor issue
Edit: LRX21M link back up, let me know if there's any issues
Whoa...
Let the games begin....
ftarules said:
Whoa...
Let the games begin....
Click to expand...
Click to collapse
yeup, after recovery i have a few system modification ideas for the settings apk i was considering
i do have other devices to worry about though so it may take some time
bunchies said:
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LRX21V - root-boot
Click to expand...
Click to collapse
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
mikereidis said:
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
Click to expand...
Click to collapse
Use adb shell
than type su to use root adb shell
Since running the script everything seems all good except for using voice search. Anybody else having issues where voice search just closes?
Update: Erased and manually flashed the V firmware as I was on M and now it appears to be working correctly, not sure if this is going to be a problem with people stuck on M for now but you may want to think of upgrading your fimware.
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
xReaper7x said:
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
at what point, adb will restart about half way through and it shows it cant connect to device but it really is
but if your in fastboot and it cant connect to the device than thats an issue
i should note this in the OP
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Snuzzo said:
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Click to expand...
Click to collapse
lol Snuzzo :good: recovery coming soon
Links are down. Does anyone have a mirror of 21V?
prsterero said:
Links are down. Does anyone have a mirror of 21V?
Click to expand...
Click to collapse
Links are up, hosted on android file host
Can mirror in a bit if needed
bunchies said:
Links are up, hosted on android file host
Can mirror in a bit if needed
Click to expand...
Click to collapse
Looks like it's working now. Before I was getting that the file couldn't be found. Thanks I appreciate you releasing this I just got it unlocked so time to root and have some fun expanding the storage to 128gb
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
________________________________________________________
root-boot: By Bunchies @xda
________________________________________________________
________________________________________________________
Power off/unplug the device, hold the power button while
plugging in the device until you see the google logo and
than let go to enter fastboot mode
________________________________________________________
________________________________________________________
Plugin the device to a PC using a usb cable
________________________________________________________
Press any key to continue . . .
waiting for ADB
target reported max download size of 536870912 bytes
sending 'boot' (5424 KB)...
OKAY [ 1.357s]
writing 'boot'...
OKAY [ 1.515s]
finished. total time: 2.876s
rebooting...
finished. total time: 0.602s
When boot completes
and you see the launcher
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
rm: /system/bin/install-recovery.sh: Read-only file system
mkdir failed for /system/app/SuperSU, Read-only file system
mkdir failed for /system/bin/.ext, Read-only file system
failed to copy 'SuperSU/SuperSU.apk' to '/system/app/SuperSU/': Is a directory
failed to copy 'x86/su' to '/system/xbin/su': Read-only file system
failed to copy 'x86/supolicy' to '/system/xbin/supolicy': Read-only file system
failed to copy 'x86/libsupol.so' to '/system/lib/libsupol.so': Read-only file sy
stem
failed to copy 'x86/99SuperSUDaemon' to '/system/etc/init.d/99SuperSUDaemon': Re
ad-only file system
failed to copy 'x86/install-recovery.sh' to '/system/etc/install-recovery.sh': R
ead-only file system
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: /system/xbin/sugote-mksh: Read-only file system
ln: /system/bin/su: Read-only file system
ln: /system/bin/install-recovery.sh: File exists
rm: /system/bin/app_process: Read-only file system
ln: /system/bin/app_process: File exists
mv: rename /system/bin/app_process32 to /system/bin/app_process32_original: Read
-only file system
ln: /system/bin/app_process32: File exists
cp: /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/app/SuperSU: No such file or directory
Unable to chmod /system/app/SuperSU/SuperSU.apk: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/lib/libsupol.so: No such file or directory
Unable to chmod /system/bin/.ext: No such file or directory
Unable to chmod /system/bin/.ext/.su: No such file or directory
Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chmod /system/xbin/daemonsu: No such file or directory
Unable to chmod /system/xbin/sugote: No such file or directory
Unable to chmod /system/xbin/sugote-mksh: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/xbin/supolicy: No such file or directory
Unable to chmod /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/bin/app_process_init: No such file or directory
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: No such
file or directory
chcon: Could not label /system/bin/.ext/.su with ubject_r:system_file:s0: No
such file or directory
chcon: Could not label /system/lib/libsupol.so with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/etc/init.d/99SuperSUDaemon with ubject_r:syste
m_file:s0: No such file or directory
chcon: Could not label /system/bin/sh with ubject_r:system_file:s0: Read-onl
y file system
chcon: Could not label /system/xbin/sugote with ubject_r:zygote_exec:s0: No
such file or directory
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: N
o such file or directory
chcon: Could not label /system/xbin/sugote-mksh with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/bin/app_process32_original with ubject_r:zygot
e_exec:s0: No such file or directory
chcon: Could not label /system/bin/app_process_init with ubject_r:system_file
:s0: No such file or directory
Finished, you can now exit the installer
Press any key to continue . . .
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
prsterero said:
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
Click to expand...
Click to collapse
Glad to hear that!
bunchies said:
Glad to hear that!
Click to expand...
Click to collapse
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
prsterero said:
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
Click to expand...
Click to collapse
Weird, windows 8?
Hello guys,
I'm brand new here in the forum and would like to root my Fire TV2 ( Version 5.2.7.3 ). I know about rooting and already own a Fire TV2 that I successfully rooted myself a few years ago. I haven't really found much about this latest version. Just a Pre-Rooted 5.2.7.3 ROM ( from rbox ). But this is of no use to me without the SU and TWRP installed. Has anyone successfully rooted a Fire TV2 with this version and can help me ?
Best regards
Maxidoman
Maxidoman said:
Hello guys,
I'm brand new here in the forum and would like to root my Fire TV2 ( Version 5.2.7.3 ). I know about rooting and already own a Fire TV2 that I successfully rooted myself a few years ago. I haven't really found much about this latest version. Just a Pre-Rooted 5.2.7.3 ROM ( from rbox ). But this is of no use to me without the SU and TWRP installed. Has anyone successfully rooted a Fire TV2 with this version and can help me ?
Best regards
Maxidoman
Click to expand...
Click to collapse
Yeah, root is still possible, here is the thread: Link
Hello Sus_i,
Thanks for the link. But I don't want to open the Fire TV Box for root. Isn't there an easier option for version 5.2.7.3, for example with the sideloading tool adblink for Windows? I could use it to install the SuperUser & TWRP Recovery.
Best regards
Maxidoman
Maxidoman said:
Hello Sus_i,
Thanks for the link. But I don't want to open the Fire TV Box for root. Isn't there an easier option for version 5.2.7.3, for example with the sideloading tool adblink for Windows? I could use it to install the SuperUser & TWRP Recovery.
Best regards
Maxidoman
Click to expand...
Click to collapse
No, unfortunately there isn't another (known) way to root/install TWRP at this fw.
Sus_i said:
No, unfortunately there isn't another (known) way to root/install TWRP at this fw.
Click to expand...
Click to collapse
Hello Sus_i,
I've changed my mind. There must always be a small risk with a root attempt. Otherwise the thrill is missing. Where can I find the required files ( python3, PySerial, adb, fastboot ) on the Internet? How do I get Linux to work on my Windows 7/10 Latop ?
Maxidoman said:
Hello Sus_i,
I've changed my mind. There must always be a small risk with a root attempt. Otherwise the thrill is missing. Where can I find the required files ( python3, PySerial, adb, fastboot ) on the Internet? How do I get Linux to work on my Windows 7/10 Latop ?
Click to expand...
Click to collapse
One way is to create a bootable USB drive with Linux. See https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started for Ubuntu instructions.
The link in post 2 includes instructions for installing python3 and PySerial, if they are not already installed. Adb and fastboot are in the Android Platform Tools at https://developer.android.com/studio/releases/platform-tools.
Another way would be to run Linux in a VM under Windows.
Maxidoman said:
Hello Sus_i,
I've changed my mind. There must always be a small risk with a root attempt. Otherwise the thrill is missing. Where can I find the required files ( python3, PySerial, adb, fastboot ) on the Internet? How do I get Linux to work on my Windows 7/10 Latop ?
Click to expand...
Click to collapse
That's easy. Grab rufus (from rufus.ie) and an ubuntu iso, then flash ubuntu with rufus to an usb stick.
Boot it as live version (depends on your laptop, press F2, F12 or something like that for the boot menu) and connect to the internet.
Then just do all requirements from the root OP thread.
Most critical part is the shorting! Don't damage the resistor, best is to use some fine flexible copper cable... but never use sharp tools or steel!
If the short doesn't work within 10 seconds, disconnect power and usb, then try again.
Good luck
Hello Guys,
Thanks for the information. I still have a few questions for understanding. I created a bootable usb stick with ubuntu-20.04.1-desktop-amd64 and now i can start ubuntu. I did not select Install rather l just try out and my latop is connected to my network via wifi. Then open a terminal and enter the following commands :
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot
Some downloads started automatically and the files were installed. The next command :
sudo apt remove modemmanager
Then I opened a new terminal in the amonet-sloane-v1.3 folder and entered the command :
sudo ./bootrom-step.sh
The following is now displayed on the screen
Picture
Is everything okay so far ?
I haven't opened the Fire TV box yet. Couldn't you first connect the USB cable for testing (without the short-circuit bridge between DAT0 and GND) to see if the connection works? I would then possibly expect the message :
Bus 001 Device 013: ID 0e8d: 2000 MediaTek Inc. MT65xx Preloader
Best regards
Maxidoman
Maxidoman said:
Hello Guys,
Thanks for the information. I still have a few questions for understanding. I created a bootable usb stick with ubuntu-20.04.1-desktop-amd64 and now i can start ubuntu. I did not select Install rather l just try out and my latop is connected to my network via wifi. Then open a terminal and enter the following commands :
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot
Some downloads started automatically and the files were installed. The next command :
sudo apt remove modemmanager
Then I opened a new terminal in the amonet-sloane-v1.3 folder and entered the command :
sudo ./bootrom-step.sh
The following is now displayed on the screen
Picture
Is everything okay so far ?
I haven't opened the Fire TV box yet. Couldn't you first connect the USB cable for testing (without the short-circuit bridge between DAT0 and GND) to see if the connection works? I would then possibly expect the message :
Bus 001 Device 013: ID 0e8d: 2000 MediaTek Inc. MT65xx Preloader
Best regards
Maxidoman
Click to expand...
Click to collapse
There are a couple of potential issues which may (or may not) cause problems.
1. The amonet log cannot be written due to a read-only file system. Try this command - "sudo chmod -R +w /cdrom/amonet-sloan-v1.3". That may or may not make the file system writable. If not, and if it does cause problems, do "mount | grep amonet" and let me know the output.
2. The adb and fastboot you installed using apt are probably not the latest versions. The latest versions are in the link I gave you above. You may not need the latest versions, though.
You can connect the USB cable without the short-circuit bridge. Execute the command "lsusb" and you should see the firestick. The file manager may also open, or you may be prompted to open the firestick with the file manager.
Sorry to be so vague, but I'd have to duplicate what you are doing to be more exact, and it has been a while since I have done it with my firestick 4k. Also, your Fire TV Box may produce different results than my firestick.
It actually looks like I only have read access. Or did I enter something wrong ?
[email protected]:/cdrom/amonet-sloane-v1.3$ sudo chmod -R +w /cdrom/amonet-sloane-v1.3
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bootrom-step.sh': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/gpt-fix.sh': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/boot.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/force_recovery.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/gpt-sloane.bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/lk.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/preloader.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/tz.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/unbrick.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload/build': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload/build/payload.bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/common.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/handshake.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/load_payload.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/logger.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/main.py': Read-only file system
Maxidoman said:
It actually looks like I only have read access. Or did I enter something wrong ?
[email protected]:/cdrom/amonet-sloane-v1.3$ sudo chmod -R +w /cdrom/amonet-sloane-v1.3
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bootrom-step.sh': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/gpt-fix.sh': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/boot.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/force_recovery.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/gpt-sloane.bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/lk.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/preloader.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/tz.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/unbrick.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload/build': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload/build/payload.bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/common.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/handshake.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/load_payload.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/logger.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/main.py': Read-only file system
Click to expand...
Click to collapse
do "mount | grep cdrom" and let me know the output.
also how did you install the amonet zip file, and where can I get it?
If it is actually on a cdrom, you will have to copy it to the local file system. A cdrom is read-only.
Do "cp -r /cdrom/amonet-sloane-v1.3 ~" to copy it to your home directory.
Hi dcarvil,
here is the output : [email protected]:/cdrom/amonet-sloane-v1.3$ mount | grep cdrom
/dev/sdb1 on /cdrom type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
I start Ubunto from the USB stick and select Try Ubunto. The amonet-sloane-v1.3 folder including bootrom-step.sh is also on the USB stick. I have downloaded adb and fastboot (tools_r30.0.4-linux) how do I install adb and fastboot? Unfortunately, I've never worked with Linux ...
My Fire TV is not yet connected to the laptop
Maxidoman said:
Hi dcarvil,
here is the output : [email protected]:/cdrom/amonet-sloane-v1.3$ mount | grep cdrom
/dev/sdb1 on /cdrom type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
I start Ubunto from the USB stick and select Try Ubunto. The amonet-sloane-v1.3 folder including bootrom-step.sh is also on the USB stick. I have downloaded adb and fastboot (tools_r30.0.4-linux) how do I install adb and fastboot? Unfortunately, I've never worked with Linux ...
My Fire TV is not yet connected to the laptop
Click to expand...
Click to collapse
You can try to remount cdrom as writable with this command "sudo mount -o remount,rw /cdrom". If that doesn't work, just copy /cdrom/amonet-sloane-v1.3 to your home directory using the command in post 11, and execute it from there.
I'd try the adb/fastboot you installed with apt first, as you may not need the latest version. If that doesn't work, these commands should install the zip you downloaded.
sudo apt remove adb fastboot
Change to the directory where you downloaded platform-tools_r30.0.4-linux.zip (presumably Downloads). "cd Downloads", if that is where it is. If not, also change it in the "export PATH" commands below.
unzip platform-tools_r30.0.4-linux.zip
export PATH=~/Downloads/platform-tools:$PATH
Execute "adb --version" to test.
echo "PATH=~/Downloads/platform-tools:\$PATH" >> ~/.profile
echo "export PATH >> ~/.profile
dcarvil said:
You can try to remount cdrom as writable with this command "sudo mount -o remount,rw /cdrom". If that doesn't work, just copy /cdrom/amonet-sloane-v1.3 to your home directory using the command in post 11, and execute it from there.
I'd try the adb/fastboot you installed with apt first, as you may not need the latest version. If that doesn't work, these commands should install the zip you downloaded.
sudo apt remove adb fastboot
Change to the directory where you downloaded platform-tools_r30.0.4-linux.zip (presumably Downloads). "cd Downloads", if that is where it is. If not, also change it in the "export PATH" commands below.
unzip platform-tools_r30.0.4-linux.zip
export PATH=~/Downloads/platform-tools:$PATH
Execute "adb --version" to test.
echo "PATH=~/Downloads/platform-tools:\$PATH" >> ~/.profile
echo "export PATH >> ~/.profile
Click to expand...
Click to collapse
Sorry to intrude here and I dunno if I misread .
Has he even carried out the short process???
before we get into the error and software issues?
Bertonumber1 said:
Sorry to intrude here and I dunno if I misread .
Has he even carried out the short process???
before we get into the error and software issues?
Click to expand...
Click to collapse
You are welcome to intrude. I don't have this fire tv model, and don't know what the short process is. I'm just trying to help with the Linux issues, which is the extent of my knowledge. Please feel free to jump in with additional instructions.
dcarvil said:
You are welcome to intrude. I don't have this fire tv model, and don't know what the short process is. I'm just trying to help with the Linux issues, which is the extent of my knowledge. Please feel free to jump in with additional instructions.
Click to expand...
Click to collapse
hi dcarvil, I was just scanning through there mate and seen that he is talking in a hypothetical manner without the short attached.
I was thinking the read only maybe because he hasnt carried out the short. I'm not sure though but I never actually checked if my box was ro or rw, I just went straight ahead with the short and everything was kooshty :good: anyway.
Suppose we won't know until he replies,
I got a little further but now my FireTV no longer works. First I took it from a different notebook and didn't get an error message ( when i execute sudo ./bootrom-step.sh ) . Then FireTv disassembled and soldered a thin cable to Data0. FireTV started again. Everything was fine. Then follow the instructions step by step. I get this output:
[email protected]:/media/ubuntu/Windows/amonet-sloane-v1.3$ sudo ./bootrom-step.sh
[2020-09-05 11:51:29.645048] Waiting for bootrom
[2020-09-05 11:51:43.461377] Found port = /dev/ttyACM0
[2020-09-05 11:51:43.462252] Handshake
[2020-09-05 11:51:43.462759] Disable watchdog
* * * Remove the short and press Enter * * *
[2020-09-05 11:51:44.967514] Init crypto engine
[2020-09-05 11:51:44.991475] Disable caches
[2020-09-05 11:51:44.992334] Disable bootrom range checks
[2020-09-05 11:51:45.010616] Load payload from ../brom-payload/build/payload.bin = 0x48B0 bytes
[2020-09-05 11:51:45.014370] Send payload
[2020-09-05 11:51:45.637327] Let's rock
[2020-09-05 11:51:45.638437] Wait for the payload to come online...
[2020-09-05 11:51:45.642160] all good
[2020-09-05 11:51:45.642494] Check GPT
[2020-09-05 11:51:46.754204] gpt_parsed = {'PRO_INFO': (1024, 254), 'NVRAM': (2048, 10240), 'TEE1': (12288, 10240), 'TEE2': (22528, 10240), 'lk': (32768, 2048), 'boot': (34816, 51200), 'recovery': (86016, 51200), 'KB': (137216, 2048), 'DKB': (139264, 2048), 'MISC': (141312, 1024), 'LOGO': (142336, 16384), 'EXPDB': (158720, 23296), 'system': (182016, 2477600), 'cache': (2659616, 512000), 'userdata': (3171616, 12098239), '': (0, 1)}
[2020-09-05 11:51:46.755407] Check boot0
[2020-09-05 11:51:47.013076] Check rpmb
[2020-09-05 11:51:47.222409] RPMB: b'AMZN\x01\x00\x00\x00\x04\x00\x05\x01\x02\x00Xc\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
[2020-09-05 11:51:47.223998] Clear preloader header
[8 / 8]
[2020-09-05 11:51:47.712429] Flashing TEE..
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 500, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "main.py", line 164, in <module>
main()
File "main.py", line 126, in main
flash_binary(dev, "../bin/tz.img", gpt["TEE1"][0], gpt["TEE1"][1] * 0x200)
File "main.py", line 56, in flash_binary
dev.emmc_write(start_block + x, data[x * 0x200x + 1) * 0x200])
File "/media/ubuntu/Windows/amonet-sloane-v1.3/modules/common.py", line 200, in emmc_write
code = self.dev.read(4)
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 509, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
The LED no longer flashes after the start, no picture .... Can I still do something or do I now have a fullbrick? The query with the bridge still works and if I remove it, this is also recognized.
Maxidoman said:
The LED no longer flashes after the start, no picture ....
Click to expand...
Click to collapse
You see, the pl header gets wiped, just behind the RPMB thing. That is a feature: in case the script errors out, you're able to start it again 'without shorting'...
Maxidoman said:
Can I still do something or do I now have a fullbrick?
Click to expand...
Click to collapse
Idk, there are some faulty eMMC chips out there, nobody knows which box is affected.
Just run the script again, without shorting this time...
My FireTv is running again :laugh:. Thank you very much to all of you for the numerous tips. But I still have two questions.
1. My FireTV does not always start correctly. Either it starts completely normally as if no TWRP was installed. Or the 5 seconds overlay with the blue bar for the normal start / TWRP selection appears and starts the box after that it gets stuck (black picture on TV)
2. Is it possible to flash older firmware directly with TWRP with this version (5.2.7.3)?
best regards
Maxidoman
Maxidoman said:
My FireTv is running again :laugh:. Thank you very much to all of you for the numerous tips. But I still have two questions.
1. My FireTV does not always start correctly. Either it starts completely normally as if no TWRP was installed. Or the 5 seconds overlay with the blue bar for the normal start / TWRP selection appears and starts the box after that it gets stuck (black picture on TV)
2. Is it possible to flash older firmware directly with TWRP with this version (5.2.7.3)?
best regards
Maxidoman
Click to expand...
Click to collapse
Hi @Maxidoman I've got the exact same error as your post above with the "multiple access on ports error,, demonstrates a willingness to read..... " during rpmb downgrade in amonet script
Could you be so kind and elaborate how you got past this error.
Another member said to update fireiso software through the pacman command,, this is well over my head as im using Ubuntu 18.04 Lts (dual boot) and am updating this to latest Ubuntu distro just now and will update fb that way..
Cheers in advance