Develop Bugs

[Q] Kindle Fire 2 - Black Screen / No LED /Brick?

HI All,
i have a major problem hoping one of you might be able to give me a little help. I looked through tons of posts and threads however have trouble finding an answer.
I rooted my Kindle fire 2. No Problem here. However I have been experiencing severe problmes in installing a bootloader or a recovery. So after clicking my way trough the internet and trying nearly every method there is i came to this one:
i executed the follwing commands over adb (yes adb was working fine)
adb shell
su
dd if=/sdcard/twrp-blaze-2.0.0RC0.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
getting the follwowing output
D:\.android>adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p5
/dev/block/mmcblk0p5: write error: No space left on device
129+0 records in
128+0 records out
65536 bytes transferred in 0.038 secs (1724631 bytes/sec)
1|[email protected]:/ # dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
422+1 records in
422+1 records out
216164 bytes transferred in 0.097 secs (2228494 bytes/sec)
[email protected]:/ # exit
exit
[email protected]:/ $ reboot
reboot
reboot: Operation not permitted
1|[email protected]:/ $ adb reboot
adb reboot
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $ exit
exit
D:\.android>adb reboot
So after rebooting nothing happens. The screen just stays black. I get no LED when i plug the device into the pc or charger. I even tried hardrestes (pressing the button for 20 sec) but nothing. Adb wont work anymore and iam slowly starting to get frustrated. I know I should not have tried a method other than the ones discussed in this forum but after trying so much even goomanager did not work i just though "**** it" lets give it a go. So here I am. Bricked device and not a clue what to do. I also tried the Kindle Fire Unbrick Utility V1.1!
I am running win XP Pro or Mac OS whatever is better to get this sorted out. I am looking forward to hearing from you.
Your desperate Androidschima

Just as a start- do you have a kindle fire TWO?
1. The recovery you flashed isn't correct
2. The kindle fire UNBRICK tool doesn't exist for this device.
3. I'm pretty sure the partition structure you are using is from a different device also.
4. No idea what u-boot.bin is... Doesnt apply to this device
5. Goomanager WONT work.... Our recovery isnt there
Essentially it looks like you flashed the wrong TWRP to the wrong partition.
As of right now.... I dont think it cam be fixed with the tools we have.
The only thing i can suggest is to use a fastboot cable and hope it goes into fastboot mode... But i have a feeling that wont work
--
Sent from my Kindle Fire 2, CM 10.1

mindmajick said:
Just as a start- do you have a kindle fire TWO?
1. The recovery you flashed isn't correct
2. The kindle fire UNBRICK tool doesn't exist for this device.
3. I'm pretty sure the partition structure you are using is from a different device also.
4. No idea what u-boot.bin is... Doesnt apply to this device
Essentially it looks like you flashed the wrong TWRP to the wrong partition.
As of right now.... I dont think it cam be fixed with the tools we have.
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
Im pretty sure it is a KF2. It was shipped at xmas 2012. I used openrecovery-twrp-2.4.1.0-blaze.img to flash.
Any chance if i get a factory cable?

androidschima said:
Im pretty sure it is a KF2. It was shipped at xmas 2012. I used openrecovery-twrp-2.4.1.0-blaze.img to flash.
Any chance if i get a factory cable?
Click to expand...
Click to collapse
WHERE did you get the recovery? Not from the kf2 forums for sure.
Maybe with a factory cable, but i think you trashed the partitions by using the wrong ones.. Maybe for the kf1? Its possible you may have overwritten fastboot
Edit: IF you get it working again there are TWO and ONLY two methods to put recovery on our device. I recommend the first one.
1. http://forum.xda-developers.com/showthread.php?t=2106463
2. http://forum.xda-developers.com/showthread.php?t=2100963
Edit2: and here is a link to others that did something's similar:
http://forum.xda-developers.com/showthread.php?t=2141914
Edit3: and HERE is the info you need to restore back to stock IF you can get in to fastboot.
http://forum.xda-developers.com/showthread.php?t=2096888
--
Sent from my Kindle Fire 2, CM 10.1

mindmajick said:
WHERE did you get the recovery? Not from the kf2 forums for sure.
Maybe with a factory cable, but i think you trashed the partitions by using the wrong ones.. Maybe for the kf1? Its possible you may have overwritten fastboot
Edit: IF you get it working again there are TWO and ONLY two methods to put recovery on our device. I recommend the first one.
1. http://forum.xda-developers.com/showthread.php?t=2106463
2. http://forum.xda-developers.com/showthread.php?t=2100963
Edit2: and here is a link to others that did something's similar:
http://forum.xda-developers.com/showthread.php?t=2141914
Edit3: and HERE is the info you need to restore back to stock IF you can get in to fastboot.
http://forum.xda-developers.com/showthread.php?t=2096888
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
Thank you ever so much for your fast reply. I will look into the mentioned links! Thanks a million!

:) Re: [Q] Kindle Fire 2 - Black Screen / No LED /Brick?
androidschima said:
Thank you ever so much for your fast reply. I will look into the mentioned links! Thanks a million!
Click to expand...
Click to collapse
Don't waste your time.
Besides not doing the appropriate amount of research before attempting to modify your device (ahem), here's where you went wrong...
androidschima said:
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
Click to expand...
Click to collapse
You flashed an unsigned bootloader on a High Security OMAP device, therefore, you are pretty much out of options.

soupmagnet said:
Don't waste your time.
Besides not doing the appropriate amount of research before attempting to modify your device (ahem), here's where you went wrong...
You flashed an unsigned bootloader on a High Security OMAP device, therefore, you are pretty much out of options.
Click to expand...
Click to collapse
That's kind of what I thought too... Glad to have an expert confirm it, but sorry dude is SOL.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Time to RMA
mindmajick said:
That's kind of what I thought too... Glad to have an expert confirm it, but sorry dude is SOL.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like it is time to send it back to Amazon. That is pretty bricked.

soupmagnet said:
Don't waste your time.
Besides not doing the appropriate amount of research before attempting to modify your device (ahem), here's where you went wrong...
You flashed an unsigned bootloader on a High Security OMAP device, therefore, you are pretty much out of options.
Click to expand...
Click to collapse
Any Chance of Amazon finding out that i acted like a noob dumb ass and bricked my device?
If no - i still could send it back could i not?

Just ship it back. usually amazon will send out a new one. Just say it doesn`t come on when you try to start it..

Help i bricked my f240k!! And my imei and model number is gone on the phone

1 ok using olleh f240k
2 flash singapore 988 rom on it
3 was ok but no network and some how my imei and model is not found in info
4 use lg support tool to do stock recovery
5 phone back to olleh stock firmware but still no network and got glish with some app
6 do 3 to 4 times of factory reset (still the same
7 try a couple of time flash stock olleh rom until the last try it stop half way and brick
8 now cant on my f240k but only can on to download mode only
9 still can be detected by pc and lg software soo try reinstall and recovery install hailf way 30% to 70% then it stop and say that lost connection on phone ect.....
Soo now my f240k lost its imei number and model number and only can on to download mode
pls helpppp
how do i recover my imei when i can get to the android os on my phone or is ther any onther way to fix this ???

boiflame said:
1 ok using olleh f240k
2 flash singapore 988 rom on it
3 was ok but no network and some how my imei and model is not found in info
4 use lg support tool to do stock recovery
5 phone back to olleh stock firmware but still no network and got glish with some app
6 do 3 to 4 times of factory reset (still the same
7 try a couple of time flash stock olleh rom until the last try it stop half way and brick
8 now cant on my f240k but only can on to download mode only
9 still can be detected by pc and lg software soo try reinstall and recovery install hailf way 30% to 70% then it stop and say that lost connection on phone ect.....
Soo now my f240k lost its imei number and model number and only can on to download mode
pls helpppp
how do i recover my imei when i can get to the android os on my phone or is ther any onther way to fix this ???
Click to expand...
Click to collapse
item 9 above, probably best is to try change your cable and reflash stock firmware.
NOTE: after you reflash and able to bootup the phone.... it probably will have 2 issue
1) imei not found and unable to connect to your mobile provider
2) your storage will show only 16GB
IMPORANT: did u do backup for the below block partition ? IF NOT, guess you can only use the phone as tablet.
adb.exe shell su -c "mkdir /sdcard/System/"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p12 of=/sdcard/System/12m9kefs1.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p13 of=/sdcard/System/13m9kefs2.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p15 of=/sdcard/System/15DRM.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p22 of=/sdcard/System/22eksst.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p21 of=/sdcard/System/21encrypt.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p26 of=/sdcard/System/26persist.img"

silentdrum said:
item 9 above, probably best is to try change your cable and reflash stock firmware.
NOTE: after you reflash and able to bootup the phone.... it probably will have 2 issue
1) imei not found and unable to connect to your mobile provider
2) your storage will show only 16GB
IMPORANT: did u do backup for the below block partition ? IF NOT, guess you can only use the phone as tablet.
adb.exe shell su -c "mkdir /sdcard/System/"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p12 of=/sdcard/System/12m9kefs1.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p13 of=/sdcard/System/13m9kefs2.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p15 of=/sdcard/System/15DRM.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p22 of=/sdcard/System/22eksst.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p21 of=/sdcard/System/21encrypt.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p26 of=/sdcard/System/26persist.img"
Click to expand...
Click to collapse
ok I got it working again soo I do not have a back up anyway to fix the network and imei?

There is an app for reinstating imei numbers in the gs3 forum but I don't know if it would work for you.
Sent from my LG-E980 using xda app-developers app

boiflame said:
ok I got it working again soo I do not have a back up anyway to fix the network and imei?
Click to expand...
Click to collapse
1) fast method
probably u can ask ppl with backup of the 240K to send u those backup files
NOTE: if restore from other ppl's backup file you will probably have the same IMEI as the person send u his backup files.
2) long tedios method
its kinda hard to explain here .. but involved using QPST, pull out or backup a .qcn file from your phone and manual edit the IMEI then push it back into your phone.
its a long shots.... but worth a try.
if your phone now still showing 16GB, u can have the 32gb back by formatting the partition.
adb shell
su
stop
/sbin/make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/userdata
reboot
NOTE: above command basically will
1) get adb shell
2) login root shell
3) stop/freeeze the system
4) formate the userdata using ext4 (note all of userdata will be gone)
5) reboot the phone
after reboot you should able to see back the 32gb storage.

merinko was
silentdrum said:
1) fast method
probably u can ask ppl with backup of the 240K to send u those backup files
NOTE: if restore from other ppl's backup file you will probably have the same IMEI as the person send u his backup files.
2) long tedios method
its kinda hard to explain here .. but involved using QPST, pull out or backup a .qcn file from your phone and manual edit the IMEI then push it back into your phone.
its a long shots.... but worth a try.
if your phone now still showing 16GB, u can have the 32gb back by formatting the partition.
adb shell
su
stop
/sbin/make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/userdata
reboot
NOTE: above command basically will
1) get adb shell
2) login root shell
3) stop/freeeze the system
4) formate the userdata using ext4 (note all of userdata will be gone)
5) reboot the phone
after reboot you should able to see back the 32gb storage.
Click to expand...
Click to collapse
my fone show 32 gb only network and imei

Broken Display

Hi,
my OnePlus 3 got crushed. Felt down while driving motorbike and then at least 3 cars did drive over it. Display splintered in thousands of pieces and digitizer is dead. Home button with fingerprint also seems to not work.
By miracle the phone itself still works. . How I can enter the phone? I tried to boot into recover and browser with ADB but I dont know where my files are.
BTW USB Debugging was not activated, not rooted and Pattern lock is activated. The phone also asks for pattern lock on boot (I am worried that this means that my files are encrypted)
What else I can do?

fxppas said:
Hi,
my OnePlus 3 got crushed. Felt down while driving motorbike and then at least 3 cars did drive over it. Display splintered in thousands of pieces and digitizer is dead. Home button with fingerprint also seems to not work.
By miracle the phone itself still works. . How I can enter the phone? I tried to boot into recover and browser with ADB but I dont know where my files are.
BTW USB Debugging was not activated, not rooted and Pattern lock is activated. The phone also asks for pattern lock on boot (I am worried that this means that my files are encrypted)
What else I can do?
Click to expand...
Click to collapse
send it back and pay money for repair or you can buy yourself a new display + digitizer
for the glass oneplus take ~100 dollar. someone in this forum had the same problem.
you can ask the support first

Without debugging and with encryption you really can't do much ...
Sent from my OnePlus 3 using Tapatalk

@panther124
I just want to have my data back.. I dont really want to fix it. The mobile phone is slightly bended and has tons of scratches on the backside and a big bump. If you see the phone you will be surprised that it is still working As far as I understand is the data lost if I send the phone back.
Isnt it possible to connect just another cheap display on the phone to just for passing the lock. So I can enable debugging.

fxppas said:
Hi,
my OnePlus 3 got crushed. Felt down while driving motorbike and then at least 3 cars did drive over it. Display splintered in thousands of pieces and digitizer is dead. Home button with fingerprint also seems to not work.
By miracle the phone itself still works. . How I can enter the phone? I tried to boot into recover and browser with ADB but I dont know where my files are.
BTW USB Debugging was not activated, not rooted and Pattern lock is activated. The phone also asks for pattern lock on boot (I am worried that this means that my files are encrypted)
What else I can do?
Click to expand...
Click to collapse
Hi
did you unlock the bootloader?
maybe you could still root it and adp push / pull stuff from it

AlexLebowski said:
Hi
did you unlock the bootloader?
maybe you could still root it and adp push / pull stuff from it
Click to expand...
Click to collapse
I can enter shell with adb if I use power+vol up to boot into bootloader. But I dont know where my files are. "/sdcard" /media / mnt" I dont find anything.

fxppas said:
I can enter shell with adb if I use power+vol up to boot into bootloader. But I dont know where my files are. "/sdcard" /media / mnt" I dont find anything.
Click to expand...
Click to collapse
try look into "/storage" or "/data", or any other directories, use "adb pull" to copy everything you can to your computer.

Internal storage is at /storage/emulated/0
Sent from my OnePlus 3 using Tapatalk

Explorer23 said:
Internal storage is at /storage/emulated/0
Click to expand...
Click to collapse
[email protected] ~/on3bu $ sudo adb shell
[email protected]:/ $ cd /storage/
[email protected]:/storage $ ls
sdcard0
[email protected]:/storage $ ls -l sdcard0
lrwxrwxrwx root root 1970-04-23 10:16 sdcard0 -> /sdcard
[email protected]:/storage $ exit
[email protected] ~/on3bu $ sudo adb pull /storage/sdcard0
failed to copy '/storage/sdcard0' to './sdcard0': No such file or directory
[email protected] ~/on3bu $ sudo adb pull /sdcard
failed to copy '/sdcard' to './sdcard': No such file or directory
[email protected] ~/on3bu $ sudo adb shell
[email protected]:/ $ ls /storage/
sdcard0
[email protected]:/ $
Not with my phone

Hey, sorry for the late reply, i've been sick the last day.
First of all a stupid question
Have you seen that all your data is there under /storage/sdcard0? or is it an empty folder
try specifying the output directory of adb pull like
Code:
adb pull /storage/sdcard0 /home/username/
I'm thinking maybe it's a linux related problem, since linux doesnt always automatically create folder structures. So if your error message changes keep me posted.
Also:
my data is directly under /sdcard
so if i
Code:
adb pull /sdcard
I get
Code:
pull: building file list...
pull: /sdcard/ViPER4Android/DDC/Custom_jmxc23.vdc -> ./ViPER4Android/DDC/Custom_jmxc23.vdc
and Last but not least
maybe the sdcard isn't mounted correctly...
try
Code:
mount -a
in adb shell and leaye the shell open, then open a new one and try pulling the stuff from it.
I'm also new to XDA so until now i only had to solve my own problems but maybe it helps just give it a try
I'm also not shure if your pattern lock has encrypting your data (/sdcard).
but there is also a solution for removing lockscreen patterns via adb shell.
Good Luck,
Alex

NEED 'mmcblk0.img' file

Can anybody give me 'mmcblk0.img' file for htc 10(2ps6500/2ps6500). if the phone is rooted and busybox installed it can be extracted using adb command.
To view partition tables :
adb shell su -c ls -al /dev/block/
After running this you can see this partition mmcblk0 in starting and make sure that the partition is available.
First you have to backup your file.
To backup into internal memory run this command:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/sdcard0/fulldump.img
or
To backup into external memory runthis command:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/sdcard1/fulldump.img
the file is supposed to be in GBs, so copy the file in pc, make a zip/winrar archive and upload it.
It would be a great help for me as I'm stuck with a bricked device. Thanks in advance

Capturing it now. I'm on the October 2017 unlocked firmware/ROM (RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.21). The command I needed to use was
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/emulated/0/fulldump.img
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=sdcard/fulldump.img
might've worked, too. I'll let you know when it's uploaded.
Edit: Filled up the 19 GB free space on internal. Let me try to external SD.
Likewise, the command for external SD on this device is:
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/ext_sd/fulldump.img
Yikes, 29GB but done. And hopefully it will compress a ton in order to upload somewhere. I'll 7-Zip it with maximum settings and see how well it compresses before I figure out where to upload it to. I don't know if I'd be able to upload something that large anywhere - I could ask AFH if it would be cool, even if it's just temporary. Guess we could always try a torrent if you're familiar with downloading torrents. I'll let you know how it compresses. It'll take at least a couple of hours to compress. Right now it's averaging 28% so it'll be less than 10 GB, I think, which is still huge.

roirraW "edor" ehT said:
Capturing it now. I'm on the October 2017 unlocked firmware/ROM (RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.21). The command I needed to use was
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/emulated/0/fulldump.img
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=sdcard/fulldump.img
might've worked, too. I'll let you know when it's uploaded.
Edit: Filled up the 19 GB free space on internal. Let me try to external SD.
Likewise, the command for external SD on this device is:
Code:
adb shell su -c dd if=/dev/block/mmcblk0 of=storage/ext_sd/fulldump.img
Yikes, 29GB but done. And hopefully it will compress a ton in order to upload somewhere. I'll 7-Zip it with maximum settings and see how well it compresses before I figure out where to upload it to. I don't know if I'd be able to upload something that large anywhere - I could ask AFH if it would be cool, even if it's just temporary. Guess we could always try a torrent if you're familiar with downloading torrents. I'll let you know how it compresses. It'll take at least a couple of hours to compress. Right now it's averaging 28% so it'll be less than 10 GB, I think, which is still huge.
Click to expand...
Click to collapse
You do realize this will give ALL of the info from every partition on your phone, correct? Including IMEI, serial#, and any and all data you have on it?

xunholyx said:
You do realize this will give ALL of the info from every partition on your phone, correct? Including IMEI, serial#, and any and all data you have on it?
Click to expand...
Click to collapse
No, I sure didn't. Thank you! I wondered but in my searches I didn't find that information. Well, forget that, then. [emoji16]
I had even considered, if I was prepared to RUU my 10 (the Pixel is my primary) (but I'm not), to only then capture it after.
Thank you very much!

Thanks for responding, I didn't know that will give all that partition details. I am new to xda. Thanks again.

anam_1285 said:
Thanks for responding, I didn't know that will give all that partition details. I am new to xda. Thanks again.
Click to expand...
Click to collapse
I hope you find another way to recover your phone. Is it out of the uh oh protection/warranty period?

roirraW "edor" ehT said:
I hope you find another way to recover your phone. Is it out of the uh oh protection/warranty period?
Click to expand...
Click to collapse
No it's not, hopefully they will fix it. Thanks anyways.

roirraW "edor" ehT said:
No, I sure didn't. Thank you! I wondered but in my searches I didn't find that information. Well, forget that, then. [emoji16]
I had even considered, if I was prepared to RUU my 10 (the Pixel is my primary) (but I'm not), to only then capture it after.
Thank you very much!
Click to expand...
Click to collapse
Can you provide any possible upload link for MMCBLK0.img of HTC 10, I accidentally delete the dump

Hello, is ther a way to send the mmcblk0 to pc? with adb shell su -c dd if=/dev/block/mmcblk0

Fire TV Gen 1 Bricked

Hi All,
First, i'd like to thank you all in advance for your help.
I have Gen 1 FIre TV that was working fine, so i thought i'd update the firmware to latest using rbox prerooted image. I was running bueller-5.2.6.7-rooted_r1 but YouTube wasn't working. So i downloaded the latest and just adb pushed into the box. Then i issued adb reboot command, and somehow the box bricked.
Now No Power Light, No HDMI signals, when i connect with Computer, it shows as Qualcomm hs-usb qdloader 9006 fire and opens the drive with files in it.
I did some research and came across, that i need to manually dd=if all 8 partitions and i need to have linux installed. I managed to download a firmware update-kindle-bueller-51.6.3.2_user_632552020 extracted it all.
Question - Can i use the update-kindle-bueller-51.6.3.2_user_632552020 to dd=if?
Second, can someone please confirm the partition layout or provide commands to view the layout.
Or Perhaps guide me to a direction which i can follow to fix this.
Thank you,

I bricked my FireTV twice and just resurrected it with the expert/relentless help from "Sus_i" using rbox's https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676.
I read thru page 55 to 110 of rbox's thread https://forum.xda-developers.com/fire-tv/development/prerooted-stock-images-t2882337 and those with unlocked bootloader and have an "Image" folder with a bunch of files inside the FireTV are most likely to bring their FireTV back but losing the unlocked bootloader in the process (mine included). https://forum.xda-developers.com/fire-tv/help/firetv-1-gen-rooted-running-pre-rooted-t4035609/page6
1st gen FireTV is built tough, don't give up and all the best to you.
Question - Can i use the update-kindle-bueller-51.6.3.2_user_632552020 to dd=if?
I used this one "update-kindle-bueller-51.6.4.8_user_648594820.bin" credit to "Sus_i"
https://d1s31zyz7dcc2d.cloudfront.n...te-kindle-bueller-51.6.4.8_user_648594820.bin

@Matt_7 when I connect to Linux box, I'm terminal
Do I just issue dd=if NON-HLOS.bin of=/dev/sda3
Or do I need to do additional commands to make sure it is connected like adb stuff.
And thank you very much for replying

nycelitemaster said:
@Matt_7 when I connect to Linux box, I'm terminal
Do I just issue dd=if NON-HLOS.bin of=/dev/sda3
Or do I need to do additional commands to make sure it is connected like adb stuff.
And thank you very much for replying
Click to expand...
Click to collapse
For mine, I entered:
Sudo su
dd if=NON-HLOS.bin of=/dev/sdb3
dd if=sbl1.mbn of=/dev/sdb4
dd if=sbl2.mbn of=/dev/sdb5
dd if=sbl3.mbn of=/dev/sdb6
dd if=tz.mbn of=/dev/sdb7
dd if=rpm.mbn of=/dev/sdb8
dd if=emmc_appsboot.mbn of=/dev/sdb9
dd if=boot.img of=/dev/sdb10
sudo eject /dev/sdb
Make sure you read rbox post https://forum.xda-developers.com/showpost.php?p=66961740&postcount=676 regarding the correct partitions (in my case /dev/sdb (sdb1 to sdb20). Details instructions provided by "Sus_i" here https://forum.xda-developers.com/fire-tv/help/firetv-1-gen-rooted-running-pre-rooted-t4035609/page5, just make sure to check and double check which partition is OK to ignore (if mounted).

Thank you very much. I'll try today.

@Matt_7; thank you so much. I used the Ubuntu Live USB.
Sudo SU did not work, so i used sudo bash which did the job
When i did df -h, it showed my fire tv as sdc1
then i ejected those, and did the commands, it did not work.
I replugged them, some drives populated and i ran the commands it worked
At the end, i issued command eject /dev/sdc, it didn't work, but i ejected by right clicking, then i powered the fire tv box and it booted.
Luckily it showed TWRP as recovery.
I ran the command in adb
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
SU prompted on fire tv to accept, which i did then it showed
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
[email protected]:/ # cat /proc/cmdline
androidboot.hardware=qcom user_debug=22 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2 androidboot.selinux=enforcing androidboot.emmc=true androidboot.serialno=709xxxxxxxx301G7 androidboot.prod=1 androidboot.baseband=apq
[email protected]:/ #
Does this mean, it is unlocked?
a) if it is not unlocked, is it possible for me to unlock bootloader again?
b) if not, can I go restore to stock w/o root?
if yes, can i follow the guide on aftvnews?
http://www.aftvnews.com/how-to-fully-unlock-the-amazon-fire-tv-bootloader/
Btw, i was able to update to 5.2.7.2 r1 latest using pre-rooted from TWRP.

Hey, great to hear that you got your FireTV back, another success story! (credit to Sus_i & rbox)
This is what Sus_i told me:
For checking bootloader status, simply run
adb shell
su
cat /proc/cmdline
Bootloader is unlocked if you see: androidboot.unlocked_kernel=true
Yes, its good to have unlocked bootloader (I've no clue if that's possible again after doing the dd). Sus_i will most likely give us an answer on this thread or mine.
Best regards.

Matt_7 said:
Hey, great to hear that you got your FireTV back, another success story! (credit to Sus_i & rbox)
This is what Sus_i told me:
For checking bootloader status, simply run
adb shell
su
cat /proc/cmdline
Bootloader is unlocked if you see: androidboot.unlocked_kernel=true
Yes, its good to have unlocked bootloader (I've no clue if that's possible again after doing the dd). Sus_i will most likely give us an answer on this thread or mine.
Best regards.
Click to expand...
Click to collapse
I can't thank you enough for guiding me into the right direction. You saved me lot of aggravation and going out and spending money on new crappy versions.
Thank you sooooo much to you and sus_i and rbox.