Bricked AFTV1 - Is repair possible with hardware mod? - Fire TV Q&A, Help & Troubleshooting

I feel like a bonehead cuz I bricked my FireTV by getting ahead of myself. This FTV came shipped with 51.1.3.0 and I have always had updates blocked in my router. I purchased a SD-card adapter and was able to gain root by injecting su into /system/xbin, Installed busybox, and all that fun stuff. Everything was going along just fine, until i tried to install RBox's boot menu/Recovery without fully understanding everything. Following a guide, I ran the full bootloader unlock script and it seemed to complete fine and FTV would still boot normally with root access. What I did next is the following, trying to install recovery I download the bootmenu.img file, uploaded it to my sd card and issued the following commands:
mount -o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
exit
exit
adb reboot​My FTV restarted and has been stuck at the FireTV Logo every since. Not exactly sure where I went wrong. Did I have to downgrade before trying to install the boot menu? I did to the checksum test on the file before using it and it matched. Anyways, I tried factory reseting by holding the back/right remote control keys....no joy, tried the alt+prtsc+i keyboard procedure....nothing, tried a fastboot cable recovery.......got the drivers installed, firetv listed in devices using kindle usb driver, but although fastboot would connect and communicate to the FTV, it wouldn't respond to any fastboot commands.
I have the ability to gain direct access to the FTV's file system, but although my electronic skills are superb, my linux/android skills are quite lacking. When I disable the CPU and connect the flash to my Ubuntu 15 VMWare system via usb, I am able to mount up 6 linux partitions from the FTV. I explored around them, but don't want to go plowing through anything like a bull in a china shop until I have a direction to take from someone who actually knows what they are doing to get my beloved Firetv booting again. Any suggestions would be GREATLY appreciated. Thanks in advance.

Plug in the fire TV with a USB to USB to your PC. If the boot loader is fully unlocked you should be able to fastboot boot clockwork recovery and flash the rom that doesn't require boot menu.

{ParanoiA} said:
Plug in the fire TV with a USB to USB to your PC. If the boot loader is fully unlocked you should be able to fastboot boot clockwork recovery and flash the rom that doesn't require boot menu.
Click to expand...
Click to collapse
I mentioned in my OP that I have already tried this and although the fastboot drivers install correctly, the "fastboot devices" command returns nothing, and the "fastboot reboot recovery" command waits for about 10 seconds, then returns "no reply received by device". So this is a dead end and I guess the problem lies in the fact that my bootloader failed to unlock. I was also guessing that the solution would be to put the stock bootloader back onto the FireTV, but cannot figure out where it goes on the fire's 6 mounted partitions in linux using the soldered-in USB flash device. I can access the /system directory, but cannot locate the /dev/block/platform/msm_sdcc.1/by-name/boot folder where the bootmenu.img file was written to which caused the bricking. Any other ideas?

No I'm not that familiar with the partitions. @rbox would probably be the best one to answer this

Adaptel said:
I mentioned in my OP that I have already tried this and although the fastboot drivers install correctly, the "fastboot devices" command returns nothing, and the "fastboot reboot recovery" command waits for about 10 seconds, then returns "no reply received by device". So this is a dead end and I guess the problem lies in the fact that my bootloader failed to unlock. I was also guessing that the solution would be to put the stock bootloader back onto the FireTV, but cannot figure out where it goes on the fire's 6 mounted partitions in linux using the soldered-in USB flash device. I can access the /system directory, but cannot locate the /dev/block/platform/msm_sdcc.1/by-name/boot folder where the bootmenu.img file was written to which caused the bricking. Any other ideas?
Click to expand...
Click to collapse
boot is partition 10. You should be able to use gdisk on the mmc device to see the partition table with the partition labels.

rbox said:
boot is partition 10. You should be able to use gdisk on the mmc device to see the partition table with the partition labels.
Click to expand...
Click to collapse
Thank you for chiming in Rbox. I am in awe of your amazing work with FireTV and keep up the spectacular work!!!
Anyways, I wanted to attach a screenshot of my dead fireTV1's MMC partition layout, but becasue I am new here, the forum won't let me add a screenshot jpg. I used gparted because as I said before, I am a linux novice and couldn't get gdisk to show me what I wanted to. Partition 10 is labeled "boot", is 10MB in size, and shows up as having a file system type "Unknown". Should I dd the stock recovery file to this partition, or what do I need to do to undo these commands which bricked my device. (Which I am pretty sure due to the fact that I didn't get the bootloader unlocked correctly).
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot​Thank you so much for your help in advance!

Adaptel said:
Thank you for chiming in Rbox. I am in awe of your amazing work with FireTV and keep up the spectacular work!!!
Anyways, I wanted to attach a screenshot of my dead fireTV1's MMC partition layout, but becasue I am new here, the forum won't let me add a screenshot jpg. I used gparted because as I said before, I am a linux novice and couldn't get gdisk to show me what I wanted to. Partition 10 is labeled "boot", is 10MB in size, and shows up as having a file system type "Unknown". Should I dd the stock recovery file to this partition, or what do I need to do to undo these commands which bricked my device. (Which I am pretty sure due to the fact that I didn't get the bootloader unlocked correctly).
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot​Thank you so much for your help in advance!
Click to expand...
Click to collapse
You can just dd that boot.img in /system/boot back to the partition to undo what you did.

rbox said:
You can just dd that boot.img in /system/boot back to the partition to undo what you did.
Click to expand...
Click to collapse
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Should I not even try to install boot menu/recovery? I thought i was on 51.1.3.0, but I just now checked and I am actually on 51.1.4.0. I ran the full bootloader unlock script right before I reflashed the recovery partition which bricked my fire. Is it because 51.1.40 is the version-of-no-return for installing recovery, should I have ran the partial bootloader unlock, or something else? Any advice? I am happy to have my Fire TV working again, but half the fun of this is learning and understanding what goes on inside and how it works. THANKS AGAIN!!!!!

Adaptel said:
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Should I not even try to install boot menu/recovery? I thought i was on 51.1.3.0, but I just now checked and I am actually on 51.1.4.0. I ran the full bootloader unlock script right before I reflashed the recovery partition which bricked my fire. Is it because 51.1.40 is the version-of-no-return for installing recovery, should I have ran the partial bootloader unlock, or something else? Any advice? I am happy to have my Fire TV working again, but half the fun of this is learning and understanding what goes on inside and how it works. THANKS AGAIN!!!!!
Click to expand...
Click to collapse
You can't unlock that version. You should block updates and wait until I release TWRP and prerooted fireos5 roms.

hey rbox, quick question: once you release the prerooted fireos5 is it possible to dd recovey.img through hardware mmc to get the unlocked bootloader?
my firetv got bricked using supersu me and now i wonder what the best way is to bring it back alive..

Adaptel said:
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Click to expand...
Click to collapse
Can you tell me the command wich give you finally the success ?
Another question by me is how to create a system.img from the bin files.
I know that there is folder in the bin-zip but how to create from them a system.img or how to create a valid stuck-recovery.img
Greetings by Idijt

I_did_it_just_tmrrow said:
Can you tell me the command wich give you finally the success ?
Click to expand...
Click to collapse
Certainly. The process I went through (using Ubuntu Linux 15 with Fire's eMMC chip connected via USB via hardware mod) is as follows (keep in mind I'm not a Linux genius but know enough to get by:
When eMMC is successfully connected, Ubuntu auto-mounted 6 partitions with partition names/ids that consisted of a long string of hex digits.
By looking around these ext4 partitions, I noticed that one of them was obviously the entire contents of the Fire's /system folder.
I navigated to /system/boot/ and saw that the boot.img file was in there. I right clicked on it, selected Properties to gain a full path of the files location and copied it
I installed and ran gparted partition editor to view the partition layout of the eMMC. There are a total of 20 partitions on fire's disk, (/dev/sdb1 through /dev/sdb20 on my system) but most of them aren't mounted because they use a non-linux standard file format).and as Rbox said. Partition 10 was 10.00MB in size, type=unknown, name=boot, and was located at /dev/sdb10 (on my system).
Now all I had to do was issue this command: sudo dd if=/<long string of hex digits described abouve>/system/boot/boot.img of=/dev/sdb10
Remove 4 wires soldered to Firetv, Solder CPU oscillator pads together, Reboot and Cheer​The fire tv rebooted fine and everything was good....but I do have an update with even more good news. I felt emboldened having access to my MMC ao since my software was on version 51.1.40, I was able to then follow the guide (EXACTLY) at http://solderwiresandplastic.com/20...the-amazon-firetv-to-achieve-root-privileges/​starting at "Step 2", and was able to successfully install the latest clockworkmod recovery, RBox's AWESOME boot menu, and install RBox's latest prerooted rom. This worked because I was on version 51.1.4.0 and the bootloader eFuse freeze occurred on 51.1.4.1 (so don't even think of trying the steps in this link if your box has 51.1.4.1 or higher on it. Hope this makes sense and helps in some way.

mrchrister said:
hey rbox, quick question: once you release the prerooted fireos5 is it possible to dd recovey.img through hardware mmc to get the unlocked bootloader?
my firetv got bricked using supersu me and now i wonder what the best way is to bring it back alive..
Click to expand...
Click to collapse
No. To unlock your bootloader you need an old version of the aboot partition. But if you're on the latest software, you will brick if you attempt to flash that old version.

thanks, good to know!
Sent from my iPhone using Tapatalk

Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?

where did you find the 5.0.5 image i need it also , mines bricked also from super sume just waiting for EEMC chip to come in..

geist_patrick said:
Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?
Click to expand...
Click to collapse
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
[/COLOR]
geist_patrick said:
Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?
Click to expand...
Click to collapse
think you could send me your img file thanks. as im on 5.0.5 firmware bricked also. thanks

Rootet system.img
https://drive.google.com/open?id=0B8P7DODeSgf8cmk5UUx4UUFXYkk

Related

G-Slate root

There's no G-Slate forum yet, so this goes here.
How to root your T-Mobile G-Slate
This process works under Linux. The hard part under Windows would be mounting a file as an ext4 filesystem, but if you can do that you win.
You need:
The four files in the gslate_root.zip archive attached to this post.
To root:
Put those four files in a directory and open a terminal to there.
Shut down your G-Slate and plug it into your computer via USB.
Hold down both volume buttons and press the power button. The G-Slate will not appear to turn on, but it'll go into APX mode.
Running "lsusb" should show an entry "0955:7820 NVidia Corp."
Run the command "sudo su" to get a root shell. Running "ls" should still show the four files.
./nvflash --bl bootloader.bin --getpartitiontable ptable.txt
./nvflash -r --read 8 system-orig.img
Wait while 400 meg of data copies.
cp system-orig.img system.img
mkdir system
mount -o loop system.img system
cp su system/bin
chmod 4755 system/bin/su
cp Superuser.apk system/app
umount system
./nvflash -r --download 8 system.img
Wait while it copies back.
./nvflash -r --sync
Press the reset button under the sim cover to reboot.
There's your rooted G-Slate. Making that process "one click" is going to suck.
Troubleshooting:
You may need to install the package libstdc++6 or lib32stdc++6 to get nvflash to run.
You may need to use "sudo" on the nvflash commands.
If you want to try to make this work on Windows, the nvflash.exe binary and the APX USB drivers are are available from nvidia.com
This is unbelievable! Can't wait to give it a shot.
EDIT: For future reference, DO NOT use Virtual Box to try and root your device. There are issues getting the drivers to work properly. Lsusb will not work. The following methods have been tested and work:
1. Wubi install of Ubuntu Linux
2. VMware install of Ubuntu Linux
3. Dual-boot install of ""
4. Dedicated Linux box (duh)
And remember: If at first you don't succeed, try try again. Then visit our IRC channel.
Trying this on Windows 7 is gonna be a trip. Never workt with ext4 before.
Install Ubuntu and you can dual boot into Windows or Ubuntu. That's what I do.
Sent from my LG-V909 using XDA Premium App
This method is confirmed working. Thank you so much for the hard work Chandon. It wasn't very hard to complete on Linux. I can't believe my G-Slate is rooted!!!! Hell yes! Oh and the device is not wiped during the process either just to let everyone know!
Some More Help
Would it be possible to pull the recovery partition off now?
Why I ask. I am in a bit of a pickle. My slate will get to the first LG boot screen and then freeze. It does not even go to the boot animation. I can still get into fastboot and APX mode and it is seen by my computer.
How did i get here. While poking around in fastboot I am pretty sure i wiped they recovery partition D'OH.
I was able to complete the steps listed (for root) with out issue but still cannot get past the boot screen since this is only modifying the system partition.
I am thinking that if that could be pulled from the device i could flash it to mine and bring my slate back to life?
Am I way off on this one?
SmellyTunic -
Attached are all the reasonably small partitions that I could pull off my device with nvflash. This should be everything except /system, /cache, and /data.
I suggest backing everything up before flashing any of these, on the off chance that there's some difference between devices.
Thanks so much for this! Is there a good linux live cd(or bootable usb flash drive) someone could suggest where this could be accomplished easily? Not ready to take the plunge actually installing linux on my system yet >.>
Here you go
shinkinrui
Info and steps can be found here http://www.ubuntu.com/download
Pretty easy to set up a dual boot machine.
Chandon,
Any chance you know off hand which one of those partitions is the recovery?
I suggest doing a Wubi install [1], where Ubuntu pretends to be a Windows app (which you can then uninstall like any other app later). Alternatively you could try using VirtualBox [2], but that's less guaranteed to work.
The only reason I wouldn't do this with a Live CD is that you'd risk losing your backup of the stock /system partition when you reboot. It would also make losing power in the middle of the flash really annoying.
[1] https://wiki.ubuntu.com/WubiGuide
[2] (edit: virtual box doesn't easily see the USB device)
Thanks guys, reading about that Wubi solution looks like the simplest way to have a dual-boot system. I like it! I'll be getting my root on later tonight
i prefer Ubuntu just cause you can install it in windows then simply restart and boot into Linux or Windows. This way you don't need to worry about not having Linux again.
SmellyTunic said:
Any chance you know off hand which one of those partitions is the recovery?
Click to expand...
Click to collapse
I'm sure that /system is 8 and the kernel is 13, but don't know about anything else. You might be able to figure it out by reading the ptable.txt file generated by the --getpartitiontable command - it's pretty clear except for the part where it uses 3 letter partition names.
Thanks. I will take a look when i get home from work.
Sent from my GT-I9000 using XDA App
While we are on the topic of development, we really need a forum over here at XDA for the G-Slate!
deez1234 said:
While we are on the topic of development, we really need a forum over here at XDA for the G-Slate!
Click to expand...
Click to collapse
I definitely concur.
thengkiu so much
works like a charm
I have no idea why I'd ever need/want to root my G Slate, I'm fairly simple in my desires for my device - but I have to say I'm delighted to see it is possible and am ever so grateful for folks who figure this stuff out because it keeps moving G Slate towards legitimacy.
Thank you!!
The hard part under Windows would be mounting a file as an ext4 filesystem, but if you can do that you win.
Click to expand...
Click to collapse
No kidding. Since the linux method failed miserably for me, I've decided to press forward with trying to do it on Windows. Problem is, I have yet to find any way to mount an ext4 filesystem on Windows. There are several options out there that will allow you to read ext4 filesystems on Windows, but not write. Any suggestions?
my friend will be happy to see that this is possible.

[Q]How to fsck /data or /system?

Does anybody know of a way to fsck the system or data partitions? I've run into a few times where I had data errors on /data, and the only way I could think of to fix them was to do a backup and restore. I was worried about losing data during the backup process, as the filesystem was already questionable.
I have e2fsck in my rom, but I can't run it from a normal shell as the filesystems are already mounted. Is there a way to make a rom automatically check and repair the filesystems on boot, and if so, how can I control the options it passes to fsck? Are there other ways to get to an unmounted system or data partition? Does clockworkmod have any kind of shell or fsck utilities built in? Are there other recovery programs that may have something like that?
You should be able to boot into CWM, unmount the partitions, connect with adb and run it from there. At least if your version of CWM has fsck in it.
Sent from my SPH-D700 using xda premium
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
toadlife said:
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
Click to expand...
Click to collapse
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
EDIT: Forgot to mention also that unmount should actually be umount. Or you could just use the CWR menus to unmount partitions.
zman0900 said:
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
Click to expand...
Click to collapse
How bout mtd?
sent from my always aosp epic
Please consider posting questions in Q&A next time. Thank you.
Sorry for the "newbie spam"! But that worked perfectly - I didn't realize that adb shell worked when booted from cwm. That's exactly what I was looking for.
zman0900 said:
Just tried this out myself. Here's the correct syntax for the fsck command:
Code:
e2fsck -fv /dev/block/stl10
EDIT: Forgot to mention also that unmount should actually be umount. Or you could just use the CWR menus to unmount partitions.
Click to expand...
Click to collapse
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
If you run mount with no arguments, it will show a list of mounted partitions like "xxx on /system".
Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
Better to do /dev/block/platform/(your processor)/by-name/xxxx. Less chance of error
Colliebudz said:
Thanks for this, this is why i love xda!
I have e2fsck in my /bin
On a samsung galaxy s2 i9100
How do i identify my /system & /data blocks
I cant remember how to find out!
So mine would be
e2fsck -fv /dev/block/????
Thanks
Click to expand...
Click to collapse
the easiest was to find what /system and /data mount points actually are
cat /etc/fstab
to see a list of mount points.
toadlife said:
You should be able to do it while booted into recovery through ADB.
Boot to recovery
connect usb cable to PC
run `adb shell`
Code:
unmount /data
unmount /system
fsck /dev/block/stl9
fsck /dev/block/stl10
syntax for above commands needs to be checked.
Click to expand...
Click to collapse
How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.
rod.gui said:
How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.
Click to expand...
Click to collapse
Flash a custom recovery first. (CWM/TWRP)
Sent from Motorola Photon Q 4G LTE @ CM11
My phone is Huawei G525. It doesn't have CWM or any custom stuff, just rooted.
My problem is that it reports an imagic flagged inode and it recommends to fsck the partition (/system). The logs are saved in sdcard folder.
I can use adb and fastboot, but fastboot shell doesn't work and /system is mounted when i can use adb.
Is there any solution for me to run e2fsck on /system partition?
Or is there the case to worry about that error? The phone works fine...no random reboots, no crashes, no force closes.
Another thing...I've tried to make a romdump and system archive is damaged. Cannot be opened even with 7-zip.
mandgeo said:
My phone is Huawei G525. It doesn't have CWM or any custom stuff, just rooted.
My problem is that it reports an imagic flagged inode and it recommends to fsck the partition (/system). The logs are saved in sdcard folder.
I can use adb and fastboot, but fastboot shell doesn't work and /system is mounted when i can use adb.
Is there any solution for me to run e2fsck on /system partition?
Or is there the case to worry about that error? The phone works fine...no random reboots, no crashes, no force closes.
Another thing...I've tried to make a romdump and system archive is damaged. Cannot be opened even with 7-zip.
Click to expand...
Click to collapse
G525 DOES have CWM recovery available, find and install one so that you can fsck from recovery using adb.
Sent from Google Nexus 4 @ CM11
AndyYan said:
G525 DOES have CWM recovery available, find and install one so that you can fsck from recovery using adb.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
As far as I understand from here... http://bbs.dospy.com/thread-16432606-1-823-1.html , the bootloader needs to be unlocked. I've submitted for an update code and i'll wait. The chinese guy talks about U8950, but there are five different types. I've selected the first one, U8950-1. Maybe i'm lucky.
I've also tried to boot directly into the recovery found here... http://www.needrom.com/mobile/huawei-g525-u00/ , but that command is not allowed, maybe because the bootloader is locked. That was the only recovery i found that seems to be in english.
I'll try the same procedure to boot into recovery (fastboot boot recovery.img) because i don't want to mess things more that they are. I didn't found any tutorial in english and google translate is confusing.
Thanks!
LE. Does anybody know if Huawei rewrites the custom recovery if it's not the stock one.
mandgeo said:
As far as I understand from here... http://bbs.dospy.com/thread-16432606-1-823-1.html , the bootloader needs to be unlocked. I've submitted for an update code and i'll wait. The chinese guy talks about U8950, but there are five different types. I've selected the first one, U8950-1. Maybe i'm lucky.
I've also tried to boot directly into the recovery found here... http://www.needrom.com/mobile/huawei-g525-u00/ , but that command is not allowed, maybe because the bootloader is locked. That was the only recovery i found that seems to be in english.
I'll try the same procedure to boot into recovery (fastboot boot recovery.img) because i don't want to mess things more that they are. I didn't found any tutorial in english and google translate is confusing.
Thanks!
LE. Does anybody know if Huawei rewrites the custom recovery if it's not the stock one.
Click to expand...
Click to collapse
Well, you know this forum is dedicated for discussion about Samsung Epic 4G, not Huawei G525... But to help you out I might be able to dig in a bit more later this week when I have time. I'm a Chinese myself and can (hopefully) understand these procedures.
Sent from Google Nexus 4 @ CM11
AndyYan said:
Well, you know this forum is dedicated for discussion about Samsung Epic 4G, not Huawei G525... But to help you out I might be able to dig in a bit more later this week when I have time. I'm a Chinese myself and can (hopefully) understand these procedures.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
My phone is a Note 2 LTE N7105 - I realise not the same as this thread, but this is the only thread I have found that is discussing this. My /data partition needs an fsck, however, while I can adb to the phone when it is booted, I can't when it is in recovery.
I have TWRP 2.7.1.0 installed, and everything else works fine. When the phone is booted, I get the GT-N7105 driver appearing in portable devices in device manager, but when recovery is booted, I just get t0lte in "other devices".
Seems like the Samsung USB driver only works when the phone is properly booted, and doesn't match when booted to recovery.
Any ideas how to work around this?
paulkoan said:
My phone is a Note 2 LTE N7105 - I realise not the same as this thread, but this is the only thread I have found that is discussing this. My /data partition needs an fsck, however, while I can adb to the phone when it is booted, I can't when it is in recovery.
I have TWRP 2.7.1.0 installed, and everything else works fine. When the phone is booted, I get the GT-N7105 driver appearing in portable devices in device manager, but when recovery is booted, I just get t0lte in "other devices".
Seems like the Samsung USB driver only works when the phone is properly booted, and doesn't match when booted to recovery.
Any ideas how to work around this?
Click to expand...
Click to collapse
Yes, the workaround is to not use stupid Windows.
Works fine on linux.
run terminal app:
su
touch /forcefsck
Then reboot. It might depend on your ROM, but give it a go.

can't get into settings after root

Hi, I rooted with KFF and now i can't swip from the top of the screen and i have no back arrow or home button. i was trying to remove root with KFF and bin4ry but no luck. Can somebody give me some instructions? Thanks
Rooting alone will not cause the type of problems you are describing. Have you installed a custom ROM, custom launcher, or any other alterations to /system that would require root privileges?
No 2nd bootloader. just root and i can't enable adb
Adb was required for root, it should still be enabled if you never were able to get into settings after root. Weird... If worst comes to worst u might have to reflash the system image, which on the bright side is prerooted. But I just don't see how rooting it could cause such a weird error, sounds like something got messed up with the systemui apk, and root doesn't modify that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
cubiche said:
No 2nd bootloader. just root and i can't enable adb
Click to expand...
Click to collapse
To remove "root", simply enter the following commands in a terminal emulator:
Code:
su
mount -o remount,rw /system
rm /system/app/Superuser.apk
rm /system/xbin/su
mount -o remount,ro /system
exit
But, be warned. If having "root" is not the source of your problem, as I suspect, and you have some additional changes to your /system directory that you've failed to mention, you will not only be stuck with the problem you had to begin with, but you will also not have root permissions or the adb connection you would need to fix your device.
He should be able to get it in fastboot though with the fastboot getvar product command if he plugs in his kindle when off after running it since a 8.9" model right? That would be useful even if adb is disabled.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I can get into fastboot with kff, but I don't know where go from there.
You can restore a saved system.img, but it will still be rooted when it's finished.
I have a saved image from another kindle HD 8.9. I think it was 8.3.0. Will that work? Can someone will me through the process?
cubiche said:
I have a saved image from another kindle HD 8.9. I think it was 8.3.0. Will that work? Can someone will me through the process?
Click to expand...
Click to collapse
Code:
fastboot -i 0x1949 flash system system.img
Hey soupmagnet, thanks for the help. Is there a risk of bricking the tablet?
The risk is considerably lower than installing the 2nd bootloader.
How do I enter that line. From adb?
ok, i'm done but i'm stuck on the kindle fire screen.
Where did you get your system.img?
[Edit:] Nevermind. I forgot you already told us. Is it safe to assume you have a boot.img as well?
it was saved on my computer from a different hd 8.9. i saved it before frashing 2nd bootloader and twrp. should i also flash the recovery and boot?
yes i have boot and recovery.img
fastboot -i 0x1949 flash boot boot.img
That should fix it.
i flashed recovery, boot and system and still don't have the navigation buttons. system is still rooted, i assume because i flash a rooted system.img. i also have the stock-system, recovery and boot. do you think that will fix it?
I guess I assumed that's what you meant when you said you had saved images.
Unless you unpack, unroot and repack your system.img, it's going to be rooted either way because you have to have root permissions to save your system.img. But it seems beyond all logic and reasoning to think that having "root", which consists of two files that are completely independent of the systemui.apk and framework-res.apk, would have any effect on the navbar at all.
By all means, restore your stock images. I'm very interested to see if it has any effect.

[Q] Were can I get original Stock Firmware for H815?

as file for download?
Thank you.
Best regards.
I've managed to kill mine worse than that, I cant get it to boot now after installing xposed framework 64bit, I can still get into TWRP recovery... Can't believe I didn't do a nandroid before I really started to play around. Oh well I'll live and learn!
I've gone through the steps to remove the xposed files but still having the same issues.
had to mount system with adb shell
mount /system/ to do the manual file deletions and renames
Same reason.
Nandroid will not help you.
I've made a Nandroid-Backup, but restore fails.
Please tell, if you have a solution.
Just wondering if your nandroid restore is failing because system is not mounted RW, have you tried mounting it whilst connected to a pc and issuing the following
adb shell
mount /system/
system should be now mounted rw in TWRP as well
What have I exactly to write, please?
mystery007 said:
What have I exactly to write, please?
Click to expand...
Click to collapse
In ADB Sideload mode, you need to write as above...
Mine is also dead, but Recovery is still there.
My battery is empty
Loading this is difficult, while the phone is on and can not get off.
Always after connecting the phone reboots and is very hot, so charging is very slowly.
DarthEwok said:
I've managed to kill mine worse than that, I cant get it to boot now after installing xposed framework 64bit, I can still get into TWRP recovery... Can't believe I didn't do a nandroid before I really started to play around. Oh well I'll live and learn!
I've gone through the steps to remove the xposed files but still having the same issues.
had to mount system with adb shell
mount /system/ to do the manual file deletions and renames
Click to expand...
Click to collapse
Find someone who hasn't yet flashed xpos ed and ask them to pull the system partition. Then have them upload it so you can download and flash via fastboot
macdaddie87 said:
Find someone who hasn't yet flashed xpos ed and ask them to pull the system partition. Then have them upload it so you can download and flash via fastboot
Click to expand...
Click to collapse
If anyone is willing, it would be appreciated.
DarthEwok said:
If anyone is willing, it would be appreciated.
Click to expand...
Click to collapse
If I had one I would.. Post something in the h815 boot loader unlock thread and ask them to pull their system. It would be beneficial to everyone who has a h815 until the kdz comes out
I'm not able to establish a connection between PC and Cellphone.
ADB: "error - device not found"
LGMobile Support Tool: Device is found but no further action (writes that all is right).
LG Brigde: Device not found
Windows 8.1 64bit
Drivers all changed from new to old and vice versa - now 3.13.2

2x AFTV1 with Recovery dead after September 3, 2016 - 5.2.1.1_r1

I have the rbox recovery on my AFTV1 and updated the rom into the usual /sdcard (September 3, 2016 - 5.2.1.1_r1 ) folder and ran through the update on two of the firetv's.
Both of them are dead in the exact same way. No lights. no boot, no screen.
After the update I noticed this behavior. The update goes through fine and on boot loads directly onto the the dashboard and does not popup the Rbox recovery window. After a few seconds post booth, the network goes off and if you try to reboot, the firetv is permanently dead.
At first I thought it might be my one firetv which died coincidentally, however when I upgraded my parent's firetv the same way, the firetv was gone in as well in the same pattern.
Is there a way to recover. ? Both the firetv's were rooted and nothing special done on it. The automatic updates were disabled on both as well.
What recovery did you had installed? OS3 or OS5?
bula1ca said:
What recovery did you had installed? OS3 or OS5?
Click to expand...
Click to collapse
I believe it was the OS3. The first one,. I haven't been following and thought the recovery was meant to work. Is there a way around making it come back to life?
Well there is your problem. You installed an OS5 prerooted image without having upgraded your recovery to support it.
bula1ca said:
Well there is your problem. You installed an OS5 prerooted image without having upgraded your recovery to support it.
Click to expand...
Click to collapse
Is there a way to recover it in any way? I have two devices. Did I blow the efuse? as I see no signs of life.
navigates said:
Is there a way to recover it in any way? I have two devices. Did I blow the efuse? as I see no signs of life.
Click to expand...
Click to collapse
Hi All. I connected the firetv to my PC and I see a drive but the drive is not writable. And I don't see any folders to put the firmware on. Are there any recovery instructions please? I've tried looking alot for this and cannot find a definitive fix for this.
Are there any recovery chances?
I think you have made the exactly same mistake as mine.
I followed this instruction to get the LED back. But the net result is actually worse with LED back, because I cannot see the drives any more and adb is not working either.
tomprc said:
I think you have made the exactly same mistake as mine.
I followed this instruction to get the LED back. But the net result is actually worse with LED back, because I cannot see the drives any more and adb is not working either.
Click to expand...
Click to collapse
Awesome. I'm gonna try it out and see if I can do something.
tomprc said:
I think you have made the exactly same mistake as mine.
I followed this instruction to get the LED back. But the net result is actually worse with LED back, because I cannot see the drives any more and adb is not working either.
Click to expand...
Click to collapse
Can you please help with the instructions. How do you terminal into your firetv. This is what I've tried.
Tried conencting with putty on windows 10 on serial and the terminal opens but does not respond to any commands.
I installed bash and tried to connect and that too did not work.
I opened disk manager and deleted all the partitions and unmounted the read only drive on one firetv.
On the second firetv I left it with the original partitions.
I cannot figure out how to connect to the firetv through serial. There must be a native recovery. No display on the screen. Would appreciate some help please.
I have two dead boxes. One with my own cleaned up partitions and other left as is. Both don't have the light.
The instructions are for Linux.
You can't use it under Windows.
In remember I used a Fedora live CD.
tomprc said:
The instructions are for Linux.
You can't use it under Windows.
In remember I used a Fedora live CD.
Click to expand...
Click to collapse
I thought putty would do the trick through serial connection. Isin't it?
navigates said:
I thought putty would do the trick through serial connection. Isin't it?
Click to expand...
Click to collapse
don't think so... but i am not sure. Live Linux CD is easy.
tomprc said:
don't think so... but i am not sure. Live Linux CD is easy.
Click to expand...
Click to collapse
Can I recover if I've deleted the partition as well.? I'll try the live linux cd for usb and check.
navigates said:
Can I recover if I've deleted the partition as well.? I'll try the live linux cd for usb and check.
Click to expand...
Click to collapse
You need to flash the images, not just delete.
navigates said:
Can I recover if I've deleted the partition as well.? I'll try the live linux cd for usb and check.
Click to expand...
Click to collapse
I don't know what happened to yours, I just throw this out there just in case it helps. Mine had a blown efuse and I recovered with this one, courtesy of member Kramar111, YMMV:
http://forum.xda-developers.com/fir...ock-images-t2882337/post56987752#post56987752
cd2022 said:
I don't know what happened to yours, I just throw this out there just in case it helps. Mine had a blown efuse and I recovered with this one, courtesy of member Kramar111, YMMV:
http://forum.xda-developers.com/fir...ock-images-t2882337/post56987752#post56987752
Click to expand...
Click to collapse
I played around with the same instructions. I tried the linux ubuntu yesterday and no luck at all. The drive is not detected to unmount. no sign at all. i don't know how to look for the partition. When I connect the usb there aren't any new partitions to see. just the local hard drive of samsung ssd
tomprc said:
You need to flash the images, not just delete.
Click to expand...
Click to collapse
Are there any other instructions? Where do I flash it. using emmc raw etc?
navigates said:
Are there any other instructions? Where do I flash it. using emmc raw etc?
Click to expand...
Click to collapse
Everything in the link I provided is about flashing images:
dd if=/tmp/123/boot.img of=/dev/sdc10
dd if=/tmp/123/sbl3.mbn of=/dev/sdc6
dd if=/tmp/123/sbl2.mbn of=/dev/sdc5
dd if=/tmp/123/sbl1.mbn of=/dev/sdc4
dd if=/tmp/123/tz.mbn of=/dev/sdc7
dd if=/tmp/123/splash480p.img of=/dev/sdc13
dd if=/tmp/123/splash1080p.img of=/dev/sdc15
dd if=/tmp/123/emmc_appsboot.mbn of=/dev/sdc9
dd if=/tmp/123/splash720p.img of=/dev/sdc14
dd if=/tmp/123/NON-HLOS.bin of=/dev/sdc3
dd if=/tmp/123/rpm.mbn of=/dev/sdc8
dd if=/tmp/123/recovery-stock-51.1.3.0.img of=/dev/sdc11
tomprc said:
Everything in the link I provided is about flashing images:
dd if=/tmp/123/boot.img of=/dev/sdc10
dd if=/tmp/123/sbl3.mbn of=/dev/sdc6
dd if=/tmp/123/sbl2.mbn of=/dev/sdc5
dd if=/tmp/123/sbl1.mbn of=/dev/sdc4
dd if=/tmp/123/tz.mbn of=/dev/sdc7
dd if=/tmp/123/splash480p.img of=/dev/sdc13
dd if=/tmp/123/splash1080p.img of=/dev/sdc15
dd if=/tmp/123/emmc_appsboot.mbn of=/dev/sdc9
dd if=/tmp/123/splash720p.img of=/dev/sdc14
dd if=/tmp/123/NON-HLOS.bin of=/dev/sdc3
dd if=/tmp/123/rpm.mbn of=/dev/sdc8
dd if=/tmp/123/recovery-stock-51.1.3.0.img of=/dev/sdc11
Click to expand...
Click to collapse
I will try this tonight. How do I know it will write to the firetv and not on my laptop hard drive.? Where in the above instructions does it show the write to the usb? becauuse when I type in the command ls-l /dev/sd* I don't know which folder to point to? Should I go blindly and type in the above commands?
much appreciated.
3. Run terminal and execute
ls -l /dev/sd*
find which of sd* have 20 partitions and substitute sdc to sd"your letter" in dd commands

Categories

Resources