Develop Bugs

Customer ID error while rooting?

Every time I run the root update utility, it gets to a point where it says something along the lines of Customer ID error. I don't know what the problem is!? Can anyone help me out please?

Hmmm... might be related to the GoldCard. Did you mange to create one successfully? (It shouldn't have given any 'do you want to format the drive?' messages when connecting the phone in Windows, in USB Disk Drive mode.

That's what I thought might've happened, but I'm pretty sure that it didn't, and unlike in the past the HXD Editor successfully wrote the goldcard.

Tiny Linux
Hi guys, trying to load the Tiny Linux ISO referred to on Paul's page, however my pc boots up, recognises the disk, starts to load Linux then black screen......anyone else had this? Not sure what to do next, desperately want to root my phone......help.............

ummm... silly question, I know, but... you did press enter at the first prompt, didn't you? (it will hang a bit, then start the actual boot process)
alternatively, you might want to try the 'rooting from windows' method posted here in another thread, instead:
http://forum.xda-developers.com/showthread.php?t=673277

cezarL said:
ummm... silly question, I know, but... you did press enter at the first prompt, didn't you? (it will hang a bit, then start the actual boot process)
alternatively, you might want to try the 'rooting from windows' method posted here in another thread, instead.
Click to expand...
Click to collapse
LOL......yeah did that.........i get some text appear about installing ADB etc, but then immediately after the screen goes black. How long does it take before you get the desktop on normally? Cheers Andy

I've even tried reformatting the SD card and reconverting it into a Goldcard, and the update utility still gives me error 131, Customer ID error, use correct utility.

about 20-30secs after pressing enter. are you booting it in a vm, or did you burn it to a cd and use it on the computer? (vm's might be buggy)

ipodtouch, what bootloader version do you have? if it's 0.80, then you can't root the device. not yet, at least.

No I'm using the guide for Windows.

cezarL said:
ipodtouch, what bootloader version do you have? if it's 0.80, then you can't root the device. not yet, at least.
Click to expand...
Click to collapse
It's definitely at 0.75 when In check it after booting with back held down.

cezarL said:
about 20-30secs after pressing enter. are you booting it in a vm, or did you burn it to a cd and use it on the computer? (vm's might be buggy)
Click to expand...
Click to collapse
Hi, thanks for your replies. Burnt to a CD, booted via the cd. I get past the press enter bit, I have about 10 lines of text, it says "DONE" then the screen goes black....I dont suppose it matters that I am running a digital connector from my graphics card does it??????? Attached a photo of where it gets to, immediately after the last line of text appears as "DONE", the screen goes blank and stays like it....

murdoch1 said:
Hi, thanks for your replies. Burnt to a CD, booted via the cd. I get past the press enter bit, I have about 10 lines of text, it says "DONE" then the screen goes black....I dont suppose it matters that I am running a digital connector from my graphics card does it??????? Attached a photo of where it gets to, immediately after the last line of text appears as "DONE", the screen goes blank and stays like it....
Click to expand...
Click to collapse
Ok.......I think I may be getting somewhere......I tried pressing F2 when asked to press Enter. I get a load of options. I have tried TINYCORE and then used the setting to switch on text mode only. This resulted in the following command prompt being dsiplayed:-
[email protected]: ~$
Is this what would appear within the terminal window? Would I then be able to use the following commands?
SUDO MKDIR /NMT/cdrom
etc etc etc???????

Yes, that should be a good text prompt.

The Professor said:
Yes, that should be a good text prompt.
Click to expand...
Click to collapse
Thanks.....so.....just want to re-cap the process. I have made the goldcard..On it I have the rootedupdate.zip file.. do i just follow the steps below? Is there anything missing from the steps below as initially Paul had supplied a testRUU.exe file?
# Turn off your HTC desire, then turn it back on with the 'back' button held down. You'll see 'FASTBOOT' written on the screen in a red box. Connect the phone to the computer.
# In the terminal window, enter the following commands:
CODE
sudo mkdir /mnt/cdrom
sudo mount /dev/cdrom /mnt/cdrom
cd /mnt/cdrom/root
sudo ./step1.sh
# When this step has completed, using the optical trackball, navigate to the 'BOOTLOADER' and then 'RECOVERY' option on the menu, using the volume buttons to move and the power button to select. Then, again in the terminal window, enter the following commands:
CODE
sudo ./step2.sh
# When this has completed, your device should be at the 'recovery' screen. Select the 'wipe' option, then select the option to apply an update zip from sdcard, and select 'rootedupdate.zip'. This will take a little while, so go make a nice cup of tea. When the flash has finished, reboot, and you are DONE!

That's all correct if you've burned it to CD-ROM and you only have the one drive in the system. If it's on USB (as I did it) or you have multiple drives, you may have to hunt for the right one. If you do need to hunt, try using the fdisk command to show all drives; then you should be able to use mount /dev/whatever (cdrom1,flash,sdc1, etc).
Try the cdrom option first, then come back if that doesn't work.
To clarify, step1 pushes the new RUU, flashes what it needs to, then step2 puts you in recovery so you can flash the new ROM.

The Professor said:
That's all correct if you've burned it to CD-ROM and you only have the one drive in the system. If it's on USB (as I did it) or you have multiple drives, you may have to hunt for the right one. If you do need to hunt, try using the fdisk command to show all drives; then you should be able to use mount /dev/whatever (cdrom1,flash,sdc1, etc).
Try the cdrom option first, then come back if that doesn't work.
To clarify, step1 pushes the new RUU, flashes what it needs to, then step2 puts you in recovery so you can flash the new ROM.
Click to expand...
Click to collapse
Sorry Professor. I am confused now. Do I need to have the testRUU anywhere or do I not need this?
What are you referring to when you said "if you've burnt it to cd-rom?"......are you referring to tinylinux or the testRUU? As you can tell I am a little nervous and want to be sure I have everything needed to root the phone....

If you took Paul's tinylinux iso, it contains the Testruu file in one of the directories already on there. In other words, if you took the iso he linked and burned it to CD, you should be able to follow the directions word for word once you get to the TL command prompt, which you have. His step1 and step2 scripts will take care of everything, there's nothing extra besides the rootedupdate.zip that you need to worry about.

You don't need testruu with the .iso, it's included in the 'step1' phase (downgrades your rom to an unrooted 504.3 versio). 'step2' will push the required files for entering recovery mode, and also the rooted version of the current stock rom (504.4 - which is what you'll end up with after flashing).

Has anyone got any ideas about my problem please?

[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

Data Recovery via Download Mode

Afternoon all,
My G4 has hit the bootloop for the last few days. Periodically, it has powered up to the main screen, but not for long enough for me to recover data.
I just spoke to a data recovery place that told me that if I can put my phone into download mode, they can recover the data. Lo and behold, my phone is currently next to me in download mode!
I'm quite keen to avoid dropping that amount of money if possible, so does anyone know of a way to recover the internal memory of the phone via download mode?
Apologies if I'm duplicating a previous thread - I had a quick look, but couldn't see any with the same issue.

Probably when the phone is in download mode they can copy the partitions bit by bit then try to do data recovery from those partition images.
So if the phone doesn't boot, it doesn't mean the data partition is corrupted so in theory you could try to copy the data partition and mount it and see what files you can recover.
I do not know the exact commands to dump the data partition but I think that's the way it can be done.
Anyone else willing to give a hand here?

Thanks for the help so far. I believe the data is intact - when the phone starts up, the data is all there. It's just accessing it that is the issue.
Sent from my Nexus 5 using Tapatalk

something similar to
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/mnt/media_rw/external_SD/data.img
OR
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk1/data.img
don't quote me on that but in theory this should work...
make SURE you have a 32gb SDCard in the phone first

Where would that command be entered mate? Sorry, only ever used my phone stock before.
Sent from my Nexus 5 using Tapatalk

I thought the OP title said download mode?
Use the LG Root method as if you were going to root..
I'm mobile ATM but if I remember correctly...
Send_Command \\.\Com# [# meaning your com port number]
Then insert that command.
Tomorrow at work I can get a common list of partition names and the command to back it up with.

je2854 said:
I thought the OP title said download mode?
Use the LG Root method as if you were going to root..
I'm mobile ATM but if I remember correctly...
Send_Command \\.\Com# [# meaning your com port number]
Then insert that command.
Tomorrow at work I can get a common list of partition names and the command to back it up with.
Click to expand...
Click to collapse
You need to mount the partition first.
Also, you could mount data if it is not encrypted (is it?)
Do this:
Code:
mkdir /temp
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/

A little tip that should work :
Take the battery off your phone
Put both phone and battery in the fridge
Wait till the phone is cold and boot the device.
The bootloop trouble is due to an abnormal warm so this way you can have a one shot normal boot to backup your data before send for warranty.

terisse said:
A little tip that should work :
Take the battery off your phone
Put both phone and battery in the fridge
Wait till the phone is cold and boot the device.
The bootloop trouble is due to an abnormal warm so this way you can have a one shot normal boot to backup your data before send for warranty.
Click to expand...
Click to collapse
If you try this, please put the phone in a ziploc bag 1st and seal it so humidity won't get inside the phone while in the fridge.

nagalun said:
You need to mount the partition first.
Also, you could mount data if it is not encrypted (is it?)
Do this:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
Click to expand...
Click to collapse
just a question though... How can you use this command if it will not boot?
---------- Post added at 08:59 AM ---------- Previous post was at 08:50 AM ----------
to get into download mode do the following...
Pull Battery
Hold Volume Up
Plug in USB Cable (make sure it's plugged in the computer)
Release button after 5 seconds
follow the link to grab the files needed for "Send_Command"
Grab LG Root here
once you are in the mode and you followed directions you can copy the command I wrote
above to copy your data partition. The reason you must have a 32gb+ SDCard is you will
be making an exact copy of the /data partition where you can remove the SDCard and recover
whatever is needed.

je2854 said:
just a question though... How can you use this command if it will not boot?
Click to expand...
Click to collapse
Hmm... With the Send_Command.............? dd is a command too :silly:

nagalun said:
Hmm... With the Send_Command.............? dd is a command too :silly:
Click to expand...
Click to collapse
there is no need to mount the partition first..
the dd command will copy the partition as a RAW image.
you must then take it to a computer and mount it as an EXT4 or use it with ext2explore

je2854 said:
there is no need to mount the partition first..
the dd command will copy the partition as a RAW image.
you must then take it to a computer and mount it as an EXT4 or use it with ext2explore
Click to expand...
Click to collapse
in that case the command you have given him will copy 4492 mb only.
Here is why:
Code:
dd if=/dev/block/mmcblk0p55 bs=8192 skip=65536 count=548352 of=/dev/block/mmcblk1/data.img
input_file=(some partition) block_size=8192 skip_this_much_data=65536 how_many_data=548352 output_file=(somewhere)
actual data copied is 8192 * 548352 = 4492099584 bytes, and you are skipping some data from the beggining with 'skip'
you do still need to mount the sdcard, the "mmcblk1" is not treated as a directory, and it is very unlikely the sd card is mounted automatically in download mode.

nagalun said:
in that case the command you have given him will copy 4492 mb only.
Click to expand...
Click to collapse
remember me saying (if you read) above that I said "something similar to"

Hi all. Firstly, thanks for all your responses!
I've not got much of a clue what I'm doing unfortunately, I've never really messed with Android before - I'm typically fairly computer literate, but I've steered clear of messing with and rooting phones for the most part.
So to clarify, I've downloaded LG Root, Running either of the exes just leads to a cmd box that's open for about a second before closing, so I'm presuming I've missed a step. Is there a guide already in existence on how to use it?
But once in, ensure there's a sizeable Micro SD card in (it's a 64gb so I should be okay!) and use the send_command exe to send:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
And then the entire image should be on the Micro SD card.
How would I then mount the data image to be readable? I've only used .iso for mounting before.
Apologies for my ignorance - I'm probably making helping me quite difficult!

Sorry all, correction to my previous:- Do I basically follow http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
And replace step 10 with the above command?

Shift+Right Click the folder you extracted "open command prompt here" for starters...
Run ports.bat first...
It'll tell you your DIAG and communication port...
The second com port is the one you are looking for.
Send_Command \\.\Com"#" (don't insert quotes, # being the number you found)

je2854 said:
Shift+Right Click the folder you extracted "open command prompt here" for starters...
Run ports.bat first...
It'll tell you your DIAG and communication port...
The second com port is the one you are looking for.
Send_Command \\.\Com"#" (don't insert quotes, # being the number you found)
Click to expand...
Click to collapse
I'm having the same issue and actually tried this earlier today. Ports.bat didn't show a DIAG communication port even when I had the phone stably sitting in Download Mode.
Going to try the freezer trick. I already bought a Nexus 6P, just want to unlock the locked content on my SD card. lol.
EDIT: Holy crap! It worked. I chilled it in a baggie, then stood in front of the freezer as I unlocked all of my locked gallery files (1,411 files totaling 900MB). As soon as I was done, 30 seconds after stepping away from the freezer, it started to bootloop again.
Got the only information I needed off my phone...nice! I might give it another go tomorrow and see if I can't run ROM Toolbox and backup all my apps so it'll be easier to push to my N6P.
Awesome suggestion!

IlyaKol said:
I'm having the same issue and actually tried this earlier today. Ports.bat didn't show a DIAG communication port even when I had the phone stably sitting in Download Mode.
Going to try the freezer trick. I already bought a Nexus 6P, just want to unlock the locked content on my SD card. lol.
EDIT: Holy crap! It worked. I chilled it in a baggie, then stood in front of the freezer as I unlocked all of my locked gallery files (1,411 files totaling 900MB). As soon as I was done, 30 seconds after stepping away from the freezer, it started to bootloop again.
Got the only information I needed off my phone...nice! I might give it another go tomorrow and see if I can't run ROM Toolbox and backup all my apps so it'll be easier to push to my N6P.
Awesome suggestion!
Click to expand...
Click to collapse
Mine will only get to optimising Apps, even if still in the freezer.
Sent from my Nexus 5 using Tapatalk

Hi all, sorry for the double posting, but just to make certain before I do something that will accidentally brick my phone. I'm intending to do the following:
Put phone in download mode and connect device.
Open LG_Root folder
Run a command window in LG_Root
Code:
Send_Command.exe \\.\Com4
Then, line by line, command:
Code:
mkdir /temp/sd /temp/data
mount /dev/block/mmcblk1p1 /temp/sd
mount /dev/block/bootdevice/by-name/userdata /temp/data
mkdir /temp/sd/recoverydata
cp -R /temp/data/media/ /temp/sd/recoverydata/
Once I've done all this, what happens next? Will I see responses on the screen etc?
Again, I apologise for the probably stupid questions. I don't want to brick my phone and lose all of the data, but I'm going away with work so would like to square it before I go if I can.
Many thanks to you all so far.

Bricked AFTV1 - Is repair possible with hardware mod?

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

Nexus 7 (2013) Stuck on boot loop: Android is starting - Optimizing apps.

I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.

corabict said:
I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.
Click to expand...
Click to collapse
if ok connect to computer then you can move files to computer

jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.

corabict said:
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.
Click to expand...
Click to collapse
reboot recovery and adb pull sdcard

corabict said:
No root or custom recovery.
Click to expand...
Click to collapse
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."

jjgvv said:
reboot recovery and adb pull sdcard
Click to expand...
Click to collapse
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
k23m said:
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."
Click to expand...
Click to collapse
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.

corabict said:
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.
Click to expand...
Click to collapse
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course

jjgvv said:
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course
Click to expand...
Click to collapse
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.

corabict said:
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.
Click to expand...
Click to collapse
adb pull /
and see What happened
avoid adb shell as it needs root.

jjgvv said:
adb pull /
and see What happened
avoid adb shell as it needs root.
Click to expand...
Click to collapse
Yes I tried that and returns this
>>c:\Adb>adb pull /
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: warning: stat failed for path /proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/222/task/1208/fd/15: Protocol not available