Develop Bugs

[Error 270] 6.1 ROM Upgrade Problem. What did i do wrong?

Hi,
I think i followed all the steps, application unlock, hardspl, and then tried to do the 6.1 upgrade... unfortunately each time i do the phone goes sucessfully into bootloader, then starts the update. At 1% is gives me Error 270 - corrupted image...
Anyone know what i might be doing wrong?
Please help. I really want to get this running.
Thanks in advance.

salmon said:
Hi,
I think i followed all the steps, application unlock, hardspl, and then tried to do the 6.1 upgrade... unfortunately each time i do the phone goes sucessfully into bootloader, then starts the update. At 1% is gives me Error 270 - corrupted image...
Anyone know what i might be doing wrong?
Please help. I really want to get this running.
Thanks in advance.
Click to expand...
Click to collapse
maybe u have to download the rom again? if still the same, then i think u can try to flash it using the sd method
1. rename ruu_signed.nbh to cavaimg.nbh
2. copy to mini sd
3. go to bootloader mode (press camera+recorder+power)
4. follow instruction on screen
regards

Hey, thanks cruzzmz, unfortunately that didn't work either...
i've downloaded the file twice now, the two different variants in fact... i'll try once more... any other suggestions...?
i'll be seriously gutted if i can't get this to work...

Disappointingly, downloading for a 3rd time (from the mirror site this time) still didn't work...
Could i have done something wrong before this step?

Try Mtty as you could have bad blocks. Check Cruzzms post on the WM6.1 rom how to do it. After you finish with Mtty try the SD method.
Cheers

ibeqa said:
Try Mtty as you could have bad blocks. Check Cruzzms post on the WM6.1 rom how to do it. After you finish with Mtty try the SD method.
Cheers
Click to expand...
Click to collapse
if this is the case, try doing THIS first then flash.

Hey guys,
First, thanks a lot for the support! Really appreciate it... i've been following the instructions for mtty and it doesn't appear to be helping (although i could be doing something wrong)
when i do CMD>task 2a it doesn't appear to be doing anything... it just immediately brings up the next CMD> again
here's the output, just in case it's useful in diagnosing the issue... please let me know your thougts, i now don't seem able to boot up, it just gets stuck at the green windows screen.
>>>
Cmd>task 32
Level = FF
Cmd>info 8
Block 0x0(0) is Reversed block
Block 0x1(1) is Reversed block
Block 0x2(2) is Reversed block
Block 0x3(3) is Reversed block
Block 0x4(4) is Reversed block
Block 0x5(5) is Reversed block
Block 0x6(6) is Reversed block
Block 0x7(7) is Reversed block
Block 0x8(8) is Reversed block
Block 0x9(9) is Reversed block
Block 0xA(10) is Reversed block
Block 0xB(11) is Reversed block
Block 0xC(12) is Reversed block
Partition[0], type=0x20, start=0x2, total=0x18FE
Partition[1], type=0x23, start=0x1900, total=0x1300
Partition[2], type=0x25, start=0x2C00, total=0x1ED00
Partition[3], type=0x4, start=0x21900, total=0x1E700
CE Total Length(with sector info) = 0x442C800
CE CheckSum Length(without sector info) = 0x4320000
Cmd>task 32
Level = FF
Cmd>task 2a
Cmd>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 537
Storage Total block: 487
Total Bad Block in CE: 0
NeedToEraseBlockStart: 550
NeedToEraseBlockEnd: 1024
Storage format success

salmon said:
Cmd>task 32
Level = FF
Click to expand...
Click to collapse
FF is not super CID ...
Type(hex) 32: Checks your security level. Unpriviledged: "Level=0xFF", SuperCID: "Level=0"
Click to expand...
Click to collapse
that is why u cant flash it, pls do the hard spl and after u have done it, mtty task 32 again if u get as below, u r set to go
CMD>task 32
Level=0 (Super CID)
Click to expand...
Click to collapse

hey,
thanks. can i do the hard spl (which i thought i'd done) from bootloader, cos i can't fully boot the device up...

salmon said:
hey,
thanks. can i do the hard spl (which i thought i'd done) from bootloader, cos i can't fully boot the device up...
Click to expand...
Click to collapse
sad to say no, cos in ur case u have to unlock ur dev 1st, then do the hard SPL ... pls see the other thread on the how to
but then ..... u can always try

An advice for all of you who want to upgrade your Cavaliers to WM6.1:
Before you start flashing check your device via Mtty if it is CID unlocked (remember it shows "level ff" that means it is locked, if it shows "level 0" that means CID unlocked.
For more info regarding Mtty and the meaning of codes that are being used, please check Hermes thread or Hermes Wiki as there is a lot of info.
Cheers

cruzzmz said:
FF is not super CID ...
that is why u cant flash it, pls do the hard spl and after u have done it, mtty task 32 again if u get as below, u r set to go
Click to expand...
Click to collapse
are you sure the device must be SuperCID for task 2a to do it's thing?

Yes, good point...
Luckily there is a very happy ending to my story. Through some magic of clicking random buttons i managed to get the device to come out from the green windows 6 screen. I was then able to do the full super cid, check with mtty and then flash the rom...
What a nice surprise it's been too. Very stable so far. Only issue has been the symbols, which i see is being addressed in the other thread.
Thanks to everyone for their help. Where would we all be without xda-developers?
(bow)(bow)(bow)

jockyw2001 said:
are you sure the device must be SuperCID for task 2a to do it's thing?
Click to expand...
Click to collapse
i am not sure bot that though ...
salmon said:
Yes, good point...
Luckily there is a very happy ending to my story. Through some magic of clicking random buttons i managed to get the device to come out from the green windows 6 screen. I was then able to do the full super cid, check with mtty and then flash the rom...
What a nice surprise it's been too. Very stable so far. Only issue has been the symbols, which i see is being addressed in the other thread.
Thanks to everyone for their help. Where would we all be without xda-developers?
(bow)(bow)(bow)
Click to expand...
Click to collapse
Good 4 u then

how about HTC touch viva..??
some1 teach me how to solve the error 270....

alchemist89 said:
how about HTC touch viva..??
some1 teach me how to solve the error 270....
Click to expand...
Click to collapse
You should post on viva forums. Anyway did you do hardspl? and try PC with XP not Vista/7.
Cheers

Don't forget ...
And if your using the SD card method remember the system only supports SD cards not SDHC cards out of the box so you will need to use a 2G card or less if you are going to flash from the SD card ... (I think)

Rom problem after resurrection

hello to all. I hope that here I will find a solution to my problem. In fact I bought a verizon htc touch pro 2 second hand for months, I tried to do a hard spl but I was wrong to hspls. my phone was then brig. I resurrected with a riff box and now I can put it into bootloader (tricolor screen) but when I install a rom, the phone restarts and gets stuck on the touch pro 2 logo then restarts and vibrates, and gymnastics without even access the menu. also on the boot screen, I see marked Unlocked security
Rhod400 SS 32M BC
RIFFBOX Resurrected
....
Gold is a rhod500
What should I do? I have a chance to see him walk?
Thank you in advance

plasco said:
hello to all. I hope that here I will find a solution to my problem. In fact I bought a verizon htc touch pro 2 second hand for months, I tried to do a hard spl but I was wrong to hspls. my phone was then brig. I resurrected with a riff box and now I can put it into bootloader (tricolor screen) but when I install a rom, the phone restarts and gets stuck on the touch pro 2 logo then restarts and vibrates, and gymnastics without even access the menu. also on the boot screen, I see marked Unlocked security
Rhod400 SS 32M BC
RIFFBOX Resurrected
....
Gold is a rhod500
What should I do? I have a chance to see him walk?
Thank you in advance
Click to expand...
Click to collapse
Does the Rom finish installing? Which Rom did you install?

I'm not even sure what RIFFBOX is, but perhaps this saved your device after the back HSPL??
Quite often, phones are dead - completely dead - after a bad HSPL. Surprising you got it back even partially.
Now, have you tried flashing the stock ROM back? So long as you don't relock, you will be able to flash another ROM back.

plasco said:
hello to all. I hope that here I will find a solution to my problem. In fact I bought a verizon htc touch pro 2 second hand for months, I tried to do a hard spl but I was wrong to hspls. my phone was then brig. I resurrected with a riff box and now I can put it into bootloader (tricolor screen) but when I install a rom, the phone restarts and gets stuck on the touch pro 2 logo then restarts and vibrates, and gymnastics without even access the menu. also on the boot screen, I see marked Unlocked security
Rhod400 SS 32M BC
RIFFBOX Resurrected
....
Gold is a rhod500
What should I do? I have a chance to see him walk?
Thank you in advance
Click to expand...
Click to collapse
Post here what your Bootloader screen says.

thanks you all for your responses. I used the verizon official rom for htc touch pro 2 but nothing.
on the bootloader screen i see:
RHOD400 32M SS-BC
RIFFBOX RESURRECTED!
MicroP(LED) 0x0A
MicroP (KEY) 0x04
TURBO WW/ TURBO SW
TP MFG DATA
.....

here is what there is on the boot screen
RHOD40 32M SS-BC
RIFFBOX RESURRECTED!
MicroP(LED) 0X0A
MicroP(KEY) 0X04
TP MFG DATA
512,523 805,860
802,193 233,194
229,858 Calibrated
when I install the rom, the process goes to 100% and after the phone redemmarre and remains on the block logo "Touch Pro 2" and only vibrates, then restarts and the same thing.

please help me
hi everybody, yesterday i've tried to install sprint rom, verizon, rom , energy rom and mightyrom but nothing doing. the phone starts, stuck on the dark screen where it's written "touch pro 2" and vibrates for a minute and restarts. it's the same thing.
Please help me to repair my phone.

plasco said:
hi everybody, yesterday i've tried to install sprint rom, verizon, rom , energy rom and mightyrom but nothing doing. the phone starts, stuck on the dark screen where it's written "touch pro 2" and vibrates for a minute and restarts. it's the same thing.
Please help me to repair my phone.
Click to expand...
Click to collapse
Last person that did a RIFFBOX recovery made their phone unrecognizable. They had a ton of issues, and their RHOD400 kept showing up as a RHOD100. Bad bad bad...
Why are you flashing things that are not designed for your phone? I guess I didn't see any explicit GSM ROM's in there, but why are you flashing Sprint's ROM on a VZ device... That shouldn't cause any damage, but it's also not a good idea - kinda like flashing the wrong HSPL..?
Perhaps you should try to get your phone back to a 'regular' HSPL state. I'm not sure if you can reflash HSPL, but if you relock you'll certainly have issues unlocking again.

plasco said:
hi everybody, yesterday i've tried to install sprint rom, verizon, rom , energy rom and mightyrom but nothing doing. the phone starts, stuck on the dark screen where it's written "touch pro 2" and vibrates for a minute and restarts. it's the same thing.
Please help me to repair my phone.
Click to expand...
Click to collapse
Based on what you posted here as to what it says in bootloader on tge screen I don't understand why there is no spl version or info listed. I guess because you used that riffbox thing.
Your device won't function without an spl so I think that's what you need first, then a radio, then a rom.
I'm not sure how you are going to install an spl considering that you already tried to flash the shipped rom and the Hard SPL that is available is so "protected" that it will only flash to these devices under perfect circumstances.
Maybe try running task29 with just a bootscreen then flash the shipped rom again.
It really sounds like you need to find a different device or at least a different rhodium to replace this one.

hi
thank you for yours answers, but i don't have yet a solution for my phone. please tell me if my phone can well, if yes what i have to do? where can i find the original spl for my htc tps cdma (verizon)?
please help me

plasco said:
thank you for yours answers, but i don't have yet a solution for my phone. please tell me if my phone can well, if yes what i have to do? where can i find the original spl for my htc tps cdma (verizon)?
please help me
Click to expand...
Click to collapse
So you tried the task29 and reflash of stock? There's not a whole lot of other options other than rinse & repeat.

I've tried task 28, task 29 and task 32 many times but always the same thing. Asyou said i'll try again and i hope it will resolve my problem.
thank you for your answer.

plasco said:
I've tried task 28, task 29 and task 32 many times but always the same thing. Asyou said i'll try again and i hope it will resolve my problem.
thank you for your answer.
Click to expand...
Click to collapse
I think the only way you may be able to fix this particular device is to use JTAG and then flash the shipped rom but I have only heard of others doing this and I have no personal experience doing this.
You'll have to decide for yourself if it's worth doing.

hi men, i have always my problem. today i've tried to reflash spl relocker and after hardspl, i had an error: flash write. please what can i do.
help me please.

help
i have not yet find a solution for my phone. this is what i obtain when i make some mtty commands. please tell me what is wrong and what am i to do?

help
i have not yet find a solution for my phone. this is what i obtain when i make some mtty commands. please tell me what is wrong and what am i to do?
Cmd>info 2
Card inserted
SD clk rate 19MHz
Cmd5 CMD_TIMEOUT
SD clk rate 144KHZ
SD 2.0 TURBO mode : SD Clk rate 24 MHz
SD Init OK
Card inserted
SD clk rate 19MHz
Cmd5 CMD_TIMEOUT
SD clk rate 144KHZ
SD 2.0 TURBO mode : SD Clk rate 24 MHz
SD Init OK
HTCSSuperCIDHTCE
Cmd>info 3
HTCSRHOD40000
Cmd>info 4
HTCSSuperCIDHTCE
Cmd>info 5
Cmd>info 6
HTCST ÚÈÒHTCE
Cmd>info 7
HTC Integrated Re-Flash Utility, Common Base Version : 1.51d
Device Name: Rhodium_W, Bootloader Version : BOX RESURRECTED!
Built at: Jul 16 2009 21:25:07
Copyright (c) 1998-2006 High Tech Computer Corporation
Board ID=0x4
CPU ID=0x4117B362
TURBO HW =1
TURBO SW =1
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_kby00n00hm
DEVICE ID=0xBC
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 4 (0x4) is reversed block
BLOCK 5 (0x5) is reversed block
BLOCK 7 (0x7) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 9 (0x9) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 16 (0x10) is reversed block
BLOCK 17 (0x11) is reversed block
BLOCK 18 (0x12) is reversed block
BLOCK 19 (0x13) is reversed block
BLOCK 20 (0x14) is reversed block
BLOCK 21 (0x15) is reversed block
BLOCK 22 (0x16) is reversed block
BLOCK 23 (0x17) is reversed block
BLOCK 24 (0x18) is reversed block
BLOCK 25 (0x19) is reversed block
BLOCK 26 (0x1A) is reversed block
BLOCK 27 (0x1B) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
BLOCK 32 (0x20) is reversed block
OS NOT FOUND !!!
Cmd>info 9
NO user storage
Cmd>task 28
Format start
Fill RSVD information for block 351 to 384
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
Format end
Cmd>task 29
Format BINFS start
CE start start block=384, total block=3712
Write 0xFF start page=0x6000, total page=0x3A000
Format BINFS end
Cmd>task 32
Card inserted
SD clk rate 19MHz
Cmd5 CMD_TIMEOUT
SD clk rate 144KHZ
SD 2.0 TURBO mode : SD Clk rate 24 MHz
SD Init OK
Card inserted
SD clk rate 19MHz
Cmd5 CMD_TIMEOUT
SD clk rate 144KHZ
SD 2.0 TURBO mode : SD Clk rate 24 MHz
SD Init OK
Level = 0
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSRHOD4000HTCE
Cmd>task 2a
Cmd>set 14 0
HTCST ÚÈÒHTCE
Cmd>emapiINIT
Command error !!!
Cmd>ruurun
Command error !!!
Cmd>checksum
Cmd>

Code:
Bootloader Version : BOX RESURRECTED!
This is really the disturbing part. You don't have a bootloader?!? You said flashing stock failed, there's not a whole lot else you can try. I see you've tried all the mtty commands you could find, which other than task29 I'm not sure what would do you any good.
The fact that the bootloader is hosed is really troublesome. If you can get back to a "normal" bootloader, then you might be OK. That bootloader is causing you these issues, I can pretty much guarantee it.

plasco said:
i have not yet find a solution for my phone. this is what i obtain when i make some mtty commands. please tell me what is wrong and what am i to do?
Click to expand...
Click to collapse
I read the thread quickly but did not notice that you tried to Hardlsp your phone with teh correct version of HSPL. You mention SPL relocker. Did you try to flash the CDMA HSPL after you resurrected the phone?

hi
thanks for your answers.
i've tried the three versions of Rhodiumwhardspl but at 100% it tells me ERROR[226] FLASH WRITE and the phone returns on bootloader with ROM CODE update error, please try again.I'm trying it everyday but nothing do.

No help
i don t know if there is someone to help me.nobody in the all forums i ve written.ok i will through it because i m very desapointed,nobody can t repair it.

[Q] Amazon Fire Tv

as some of you may know by now amazon has released its Amazon fire Tv witch is like apple tv.... so what i want to know is this an android OS because its uses the app store and has games like Minecraft or Need For Speed... if theres aonther forum for plases let me know
because after i know its andorid then comes the race for ROOT access

gregcavaretta said:
as some of you may know by now amazon has released its Amazon fire Tv witch is like apple tv.... so what i want to know is this an android OS because its uses the app store and has games like Minecraft or Need For Speed... if theres aonther forum for plases let me know
because after i know its andorid then comes the race for ROOT access
Click to expand...
Click to collapse
The Amazon Fire TV like the Kindle Fire series of devices runs a heavily modified version of the Android operating system. As far root access goes, I'm sure in due time the development community will root the device and allow you to install Google apps that include the framework files necessary for the Play Store to work properly.

shimp208 said:
The Amazon Fire TV like the Kindle Fire series of devices runs a heavily modified version of the Android operating system. As far root access goes, I'm sure in due time the development community will root the device and allow you to install Google apps that include the framework files necessary for the Play Store to work properly.
Click to expand...
Click to collapse
well i do know you can plug it into a computer with adb so getting root won't be that hard...if you brick i wonder if you can use something like fastboot

gregcavaretta said:
well i do know you can plug it into a computer with adb so getting root won't be that hard...if you brick i wonder if you can use something like fastboot
Click to expand...
Click to collapse
They may have taken a different attitude then with the kindle fire devices which came with locked bootloaders. Out of curiosity can you pull the build.prop and upload it. Additionally try running the command:
Code:
adb reboot bootloader
Then in fastboot:
Code:
fastboot devices
And seeing what it says as this will give insight into a possible root method.
Sent from my SCH-I535 using XDA Premium 4 mobile app

shimp208 said:
They may have taken a different attitude then with the kindle fire devices which came with locked bootloaders. Out of curiosity can you pull the build.prop and upload it. Additionally try running the command:
Code:
adb reboot bootloader
Then in fastboot:
Code:
fastboot devices
And seeing what it says as this will give insight into a possible root method.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll post when mine comes in two days i was at a my buddy's house when i tested it out.....as I recall to access /system/ on the kindle Fire HD , HDX
and any other android you don't need root permissions to access to build.prop how ever you would need root access to edit it (duh) that is if apps like es file explore Or Astro File manager work.
I don't about fastboot yet i'll try a few things.
For those who want to buy this they can at
http://www.amazon.com/Amazon-CL1130-Fire-TV/dp/B00CX5P8FC

gregcavaretta said:
well i do know you can plug it into a computer with adb so getting root won't be that hard...if you brick i wonder if you can use something like fastboot
Click to expand...
Click to collapse
ADB is done via IP on this one
https://developer.amazon.com/sdk/asb/connect-adb.html

It is hackable!
daweeze02 said:
ADB is done via IP on this one
https://developer.amazon.com/sdk/asb/connect-adb.html
Click to expand...
Click to collapse
If you take it apart, there are easily accessible UART and JTAG ports. If I have time, I'll dig further over the weekend. Somebody, please beat me to this.
"adb reboot bootloader" puts it into the bootloader. Power led blinks and HDMI display only shows amazon's logo, need to check serial port.
"adb reboot recovery" also works (displays Amazon "System Update")

Determined said:
If you take it apart, there are easily accessible UART and JTAG ports. If I have time, I'll dig further over the weekend. Somebody, please beat me to this.
"adb reboot bootloader" puts it into the bootloader. Power led blinks and HDMI display only shows amazon's logo, need to check serial port.
"adb reboot recovery" also works (displays Amazon "System Update")
Click to expand...
Click to collapse
Does fastboot devices in the bootloader show anything?
Sent from my SCH-I535 using XDA Premium 4 mobile app

shimp208 said:
Does fastboot devices in the bootloader show anything?
Click to expand...
Click to collapse
The problem is that adb is accessible over IP only (or at least I have not yet found other way) and I cannot do fastboot.
build.prop attached. Also, here is a (mostly useless) boot log from the internal serial port (115200-8N1)
Code:
Android Bootloader - UART_DM Initialized!!!
[0] welcome to lk: current version is lk_rel_3.0.1_02272014
[10] platform_init()
[10] target_init(): platform_id 109
[10] Its BUELLER. revision 3
[70] display_init(),target_id=7337.
[70] hdmi_msm_panel_init: default format=4
[2730] splash_screen_mmc :235, 67
[2750] Config HDMI PANEL.
[2750] Turn on HDMI PANEL.
[2760] EDID: no DTD or non-DTD data present
[2760] EDID: no DTD or non-DTD data present
[2760] hdmi_edid_get_audio_data: No adb found
[2770] hdmi_audio_playback: 48KHz not supported by TV
[2770] hdmi_msm_audio_acr_setup: video format 0 not supported
[2780] aboot_init: calling idme_initialize
[2780] Idme version is 2.0 and set related function to V2.0
[2790] IDME INFO: checking for new items to add (stored items:12 specified items:12)
[2790] serial num from idme: XXXXXXXXXXXXXXXXXX
[2800] Reboot -- restart_reason=427810811 (0x197fdffb)
[2800] aboot_init: IDME - device boot up info
[2810] idme items number:12
[2810] name: board_id, size: 16, exportable: 1, permission: 292, data= XXXXXXXXXXXXXXXXXX
[2820] name: serial, size: 16, exportable: 1, permission: 292, data= XXXXXXXXXXXXXXXXXX
[2830] name: mac_addr, size: 16, exportable: 1, permission: 292, data= XXXXXXXXXXXXXXXXXX
[2830] name: bt_mac_addr, size: 16, exportable: 1, permission: 292, data= XXXXXXXXXXXXXXXXXX
[2840] name: productid, size: 32, exportable: 1, permission: 292, data= 00000000000000000000000000000000
[2850] name: productid2, size: 32, exportable: 1, permission: 292, data= 00000000000000000000000000000000
[2860] name: bootmode, size: 4, exportable: 1, permission: 292, data= 1
[2860] name: postmode, size: 4, exportable: 1, permission: 292, data= 2
[2870] name: bootcount, size: 8, exportable: 1, permission: 292, data= 32
[2880] name: eth_mac_addr, size: 16, exportable: 1, permission: 292, data= XXXXXXXXXXXXXXXXXX
[2890] bootcount = 33
[3080] aboot_init: Boot linux from MMC
[3090] boot_into_recovery=0 idme_bootmode=1 (NORMAL)
[3090] use_signed_kernel=1, is_unlocked=0, is_tampered=0.
[3100] Loading boot image (6344704): start
[3340] Loading boot image (6344704): done
[3340] Authenticating boot image (6344704): start
[3350] Attempting to enable ce3_src_clk before setting its rate.[3360] TZ channel swith returned 0
[5070] TZ channel swith returned 0
[5070] Authenticating boot image: done return value = 1
[5090] cmdline = 'androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 maxcpus=2'
[5100] Power on reason 1
[5100] Its bueller again 3.
[5100] cmdline_length=170, n=172, n1=45
[5110] IDME: idme atag init (export to kernel), atag_size=514
[5110] name: board_id, size: 16, exportable: 1, permission: 292, data: XXXXXXXXXXXXXXXXXX
[5120] name: serial, size: 16, exportable: 1, permission: 292, data: XXXXXXXXXXXXXXXXXX
[5130] name: mac_addr, size: 16, exportable: 1, permission: 292, data: XXXXXXXXXXXXXXXXXX
[5140] name: bt_mac_addr, size: 16, exportable: 1, permission: 292, data: XXXXXXXXXXXXXXXXXX
[5140] name: productid, size: 32, exportable: 1, permission: 292, data: 00000000000000000000000000000000
[5150] name: productid2, size: 32, exportable: 1, permission: 292, data: 00000000000000000000000000000000
[5160] name: bootmode, size: 4, exportable: 1, permission: 292, data: 1
[5170] name: postmode, size: 4, exportable: 1, permission: 292, data: 2
[5180] name: bootcount, size: 8, exportable: 1, permission: 292, data: 33
[5180] name: eth_mac_addr, size: 16, exportable: 1, permission: 292, data: XXXXXXXXXXXXXXXXXX
[5190] The atag idme items number:11
booting linux @ 0x80208000, ramdisk @ 0x82200000 (368957)

If you look in the back there's a usb port I'm going to try using usb to usb from it to my computer...
I know this is for a thumb drive or keyboard but you never know

gregcavaretta said:
If you look in the back there's a usb port I'm going to try using usb to usb from it to my computer...
Click to expand...
Click to collapse
Yeah, try that, and if it does not work, also try plugging that port into your electrical outlet. Result will be more or less the same, but the latter is more spectacular.
P.S.: That USB port is a host.

It doesn't necessarily have to be such a spectacular view I recall USB on one of the Android dongles being host and if small reset button was held while plugging it into a computer, it was possible to rewrite the flash of the device.

thought i would throw in here that my Fire TV arrived yesterday and so i plugged it in, did mandatory immediate software update, watch mandatory 5 minute unskippable tutorial video, and then experienced constant reboots on everything i tried to do with it.
i thought well it just did an update and i dont have any real data on it so lets try a factory reset which i did. after that i had to watch the mandatory video again since i did a reset ughh!
so now it fires up and IF it allows me to move the menu option without a reboot then it will either wait until i hit play to reboot or if all of that actauly works and i get a video to start playing then within 15 minutes i will be presented with a loud constant beep followed by (you guessed it) a reboot.
i have called and they are replacing it but i am not sure that is going to help and i usually wait for the first round to go out before i buy something but i was about to buy another Roku when this was announced so i jumped.

Determined said:
Yeah, try that, and if it does not work, also try plugging that port into your electrical outlet. Result will be more or less the same, but the latter is more spectacular.
P.S.: That USB port is a host.
Click to expand...
Click to collapse
mines coming Monday (2 days) dam amazon lied to me .....
anyway have you tried plugging an lan ethernet cable from it to the computer hey you never know. if not i'm going to try messing with the UART and JTAG ports but i don't have mine yet so i'll have to wait....

nice..... is it a software root?
jcase said:
Click to expand...
Click to collapse

bosewicht said:
nice..... is it a software root?
Click to expand...
Click to collapse
yes

Nicely done as always Justin! Anyone know if this comes with a locked bootloader (I'm assuming it does)?

shimp208 said:
Nicely done as always Justin! Anyone know if this comes with a locked bootloader (I'm assuming it does)?
Click to expand...
Click to collapse
so now we have root, does this mean it gets its own sub forum?
I haven't been this excited about something in a long time, I can't wait to get mine and root it

shimp208 said:
Nicely done as always Justin! Anyone know if this comes with a locked bootloader (I'm assuming it does)?
Click to expand...
Click to collapse
Yes it does
Sent from my Nexus 5 using XDA Premium 4 mobile app

[Solved... kind of] Folders showing as binary via MTP?

I just got Google's official USB Type-C to USB A cable today. Weirdly, upon plugging my N5X into my computer for the first time, the file system did not come up as expected. What show as folders locally on my device, show up as binary files in Nautilus on Ubuntu 15.10. Never seen this behaviour before in any Android device. Using an MTP connection.
Screenshot attached helps to explain the issue a little bit better.
Additionally:
Code:
$ pwd
/run/user/1000/gvfs/mtp:host=%5Busb%3A001%2C014%5D/Internal storage
$ ls -la
total 29
drwx------ 1 sec sec 0 Dec 31 1969 .
dr-x------ 1 sec sec 0 Dec 31 1969 ..
drwx------ 1 sec sec 0 Jan 29 1970 Alarms
drwx------ 1 sec sec 0 Nov 21 16:38 Android
-rw------- 1 sec sec 4096 Nov 21 20:40 APG
-rw------- 1 sec sec 4096 Nov 21 20:40 data
drwx------ 1 sec sec 0 Nov 21 20:54 DCIM
drwx------ 1 sec sec 0 Nov 21 20:41 Download
-rw------- 1 sec sec 4096 Nov 21 20:40 Kik
drwx------ 1 sec sec 0 Jan 29 1970 Movies
drwx------ 1 sec sec 0 Jan 29 1970 Music
-rw------- 1 sec sec 11 Nov 21 20:38 .nds
drwx------ 1 sec sec 0 Jan 29 1970 Notifications
drwx------ 1 sec sec 0 Nov 21 20:30 owncloud
-rw------- 1 sec sec 63 Nov 21 20:46 pia vpn.txt
drwx------ 1 sec sec 0 Nov 21 20:45 Pictures
drwx------ 1 sec sec 0 Jan 29 1970 Podcasts
drwx------ 1 sec sec 0 Jan 29 1970 Ringtones
-rw------- 1 sec sec 4096 Nov 21 20:40 .secure
-rw------- 1 sec sec 4096 Nov 21 20:40 Snapseed
-rw------- 1 sec sec 8192 Nov 21 20:40 Tumblr
drwx------ 1 sec sec 0 Nov 21 21:41 yahoo
Notice that `APG`, `data`, `Kik`, `.secure`, `Snapseed`, and `Tumblr` all show as -rw------- files and not as regular directories. What gives? Anyone have a similar problem / solution?

Saw the same thing with that version of Ubuntu. It is known to have issues with android

zelendel said:
Saw the same thing with that version of Ubuntu. It is known to have issues with android
Click to expand...
Click to collapse
Strange. I had no issues with my old Moto G (on 5.1.x) on the same machine running 15.10. Do you have any more information? Can you point to a source that says this is true? 15.10 is a stable release and I can't think of a reason why a broken version of gvfs would be shipped with it.

Narwhal73 said:
Strange. I had no issues with my old Moto G (on 5.1.x) on the same machine running 15.10. Do you have any more information? Can you point to a source that says this is true? 15.10 is a stable release and I can't think of a reason why a broken version of gvfs would be shipped with it.
Click to expand...
Click to collapse
2 very different devices and very different OS versions. 15.10 has its own issues and many android developers have advised against using it. Even Google developers don't advise it.
You can have a look in the Ubuntu forums. I came across it awhile ago when android M first came out.

zelendel said:
2 very different devices and very different OS versions. 15.10 has its own issues and many android developers have advised against using it. Even Google developers don't advise it.
You can have a look in the Ubuntu forums. I came across it awhile ago when android M first came out.
Click to expand...
Click to collapse
I've done a lot of searching through the Ubuntu forums as you've mentioned and come up with nothing. I asked this same question on AskUbuntu, but no one else seems to know what's going on...
I have however determined it's not an issue with Ubuntu. I tested on a recent Arch Linux installation, and I got my hands on a Windows computer to test the issue, and its the same thing. Those folders still show up as files over MTP, which is really annoying and kind of concerning. Any leads on what I can do to fix it?

Narwhal73 said:
I have however determined it's not an issue with Ubuntu. I tested on a recent Arch Linux installation, and I got my hands on a Windows computer to test the issue, and its the same thing. Those folders still show up as files over MTP, which is really annoying and kind of concerning. Any leads on what I can do to fix it?
Click to expand...
Click to collapse
So it was definitely an issue with the Android file system. No idea what, why or how it happened, but obviously something went funky with some the folders on my device (still really curious as to what though).
Issue was fixed by painstakingly recreating the folder structures and moving files via Amaze File Manager from the old [corrupt?] folders to the new ones on my Nexus 5X. Hard problem to explain, easy enough to solve though I guess.
Thankfully data integrity was kept and I've yet to encounter any further issues with MTP on Ubuntu 15.10, Arch Linux, nor Windows 8.1. :good:

@Narwhal73. Just experienced the same folder problem. Occurred when Titanium Backup created it's backup folder. It was normal with ES or Root Explorer on the device, but on the computer (USB/MTB) it was a 4K file. Deleted it on the device, created the backup folder on the computer, ran TiBu and it's all normal now. Some crazy stuff going on. (Win7, 5X 6.0.1 Pure Nexus)
Update 1/18/16: (Found this -possible- solution on reddit)
Figured it out. Just in case anyone else is having the same problem, what you need to do is go to Settings>Apps> click on the three dots and "show system apps". Then delete the data from the External Storage and Media Storage apps. After a restart, everything should show up again once you are plugged in.
Click to expand...
Click to collapse

Mesmurized said:
@Narwhal73. Just experienced the same folder problem. Occurred when Titanium Backup created it's backup folder. It was normal with ES or Root Explorer on the device, but on the computer (USB/MTB) it was a 4K file. Deleted it on the device, created the backup folder on the computer, ran TiBu and it's all normal now. Some crazy stuff going on. (Win7, 5X 6.0.1 Pure Nexus)
Click to expand...
Click to collapse
I wish I knew of a way to reliably reproduce this issue... This happened for me on the stock ROM, but if it's happening on Pure Nexus too then it's definitely an issue in AOSP. A bug report should probably be made. I'll get around to that sometime soon, though I don't know how useful the report would be without instructions to reproduce it. :\

Nvidia Shield TV PRO 2015 brick to update 8.0 -> 8.0.1

Hello
I have a shield tv 2015 with nvidia experience 8.1 (android 9) - last October 2, I upgraded to 8.0.1, installed and when it was to restart, turned off and did not turn on.
Turns on the 2 sec green light and turns it off and the disc works (it seems to be in standby).
I opened a ticket (on nvidia) but it is being useless because the procedures that give me do not work.
I found that underneath is a snap-in cover. so i turned off the hard drive it always turns on the green light but i can't get into fastboot / recovery mode.
At the moment when I connect the usb cable to the pc I have an APX device. does anyone know anything about APX?
Thanks help me please i´m a nood

Your only bet is to get help from nvidia costumer support since it's not a pro version.
Apx mode = your device is bricked.

Mine is the 500GB version I suppose is the PRO version.
I've been reading here in the forum ... in the PRO version the
All software is on the hard drive. So I was trying to create the hard drive with a 500GB disk but to no avail.

parfuar said:
Mine is the 500GB version I suppose is the PRO version.
I've been reading here in the forum ... in the PRO version the
All software is on the hard drive. So I was trying to create the hard drive with a 500GB disk but to no avail.
Click to expand...
Click to collapse
You can try what has been done in this thread https://forum.xda-developers.com/shield-tv/general/bricked-shield-tv-pro-2015-version-t3841024
Or something like this https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195

Hi,
One question.
My original hard drive
Info:
[email protected]:/home/ubuntu# hdparm -i /dev/sda
Model=ST500LM000-1EJ162, FwRev=SM16, SerialNo=W763XDYH
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: Reserved: ATA/ATAPI-4,5,6,7
* signifies the current active mode
-------------------------------------------------------------------------------------------------------------------------------------
fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xb22c3a15
my new hard drive
info:
[email protected]:/home/ubuntu# hdparm -i /dev/sda
Model=HGST HTS545050A7E380, FwRev=GG2OACD0, SerialNo=TE85113R0Y5TPK
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=976773168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: mode=0x01 (1) WriteCache=enabled
Drive conforms to: unknown: ATA/ATAPI-2,3,4,5,6,7
* signifies the current active mode
----------------------------------------------------------------------------------------------------------------------
--->> fdisk -l
Disk /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x4ca778fd
Hard drives are the same, I should with the tutorial, be able to get the shield to work without major problems.
what is wrong?
commands used:
dd if=start.bin of=/dev/sdX bs=4M
dd if=end_976574630.bin of=/dev/sdX seek=976574630
with these files:
https://forum.xda-developers.com/sho...2&postcount=23

My shield(2015 pro) was also bricked by the update reboot loop at nvidia logo and factory reset did not help and fastboot couldn't flash anything, so used this opportunity however to put a ssd in.
Used beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Just booted it up and its gotten past nvidia logo atleast so far

First time it bricked was updating to 8.0, after recovery it was able to get the updates up to 8.0, when i did the 8.0.1 update i also got the same error as those above where turns on then off and does not even wake the display.

HellToupee_nz said:
My shield(2015 pro) was also bricked by the update reboot loop at nvidia logo and factory reset did not help and fastboot couldn't flash anything, so used this opportunity however to put a ssd in.
Used beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Just booted it up and its gotten past nvidia logo atleast so far
Click to expand...
Click to collapse
It worked?
what version of android is it?
on mine it didn't work. only worked with the first part (firstpart.bin which is like this) and with the 5kb file that speak at the end of this thread.

parfuar said:
It worked?
what version of android is it?
on mine it didn't work. only worked with the first part (firstpart.bin which is like this) and with the 5kb file that speak at the end of this thread.
Click to expand...
Click to collapse
In my case, I have the fastboot. but this is difficult because we don't have active developer mode.

Yes, i had done a factory reset also, u can get stuck at the spinning android logo forever without that i find. For the end part of the disk i used my own from my disks image, i've just done it all again and updated back to 7.2.3 stopped there and copied my widevine key off my orginal image so got L1 support and going to make backup of its current state.

parfuar You don't use "sdX" you change the "X" to the letter your drive is from fdisk -l , looks like you need to use "sda", after after you write the two bin files reboot directly into bootloader and select boot recovery kernel which will bring up t wrp recovery and you need to perform a factory reset wipe then reboot and Android should boot up and you will have Nvidia experience 3.3 and you have to do a couple updates to get up to 8.0 just make sure you turn off automatic updates cuz mine automatically updated to 8.0.1 and crashed my hard drive a second time. I used my original hard drive

also posting here that my 2015 500gb gets bricked with 8.0.1. hdd swapped out for crucial mx500. i think the guy here said it happened on his stock 500 sshd?

OK... This is how I got it to work.
Using "DD for Windows"... since I don't have a Linux PC (tested working perfectly on Windows 10 x64)
Download link:
http://www.chrysocome.net/downloads/dd-0.6beta3.zip
Unzip the "dd.exe" file and copy it to:
%USERPROFILE%\AppData\Local\Microsoft\WindowsApps
This gives you the ability to use DD system wide.
Use the beginning disk image from here:
https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Connect your drive. I highly suggest using a Desktop PC because it is much faster than a USB to Sata cable.
If you don't have any open Sata slots, just disconnect your CD-rom drive temporarily and use the connectors.
Now:
1) Put the "start.bin" file in the root directory of drive C (example C:\start.bin)
2) Open a command prompt as Administrator and change directory to C: (command: cd C:\ )
3) Type command dd --list to determine the correct disk you want to write to.
4) Use command dd if=start.bin of=\\?\Device\HarddiskX\Partition0 --progress
whereas X is the drive number you determined earlier with the dd --list command
(replace the X with the drive number you want to write to)
5) Watch the write progress and stop the process at about 6GB (around byte 6,500,000,000)
(you can actually see the write counter running)
There is no need to write the "end file". Shut down the PC once finished and remove the drive.
6) Install the drive back into your Shield Pro and start. The green NVIDIA logo should show up soon.
Wait for about 10 minutes and if nothing happens unplug the Shield and do a restart.
Now wait patiently.... it will eventually boot past the green logo and the Android colors.
Now let your Shield self-update to whatever version you desire. It starts with version 3.0
That's it! You just successfully de-bricked your Shield Pro
Enjoy!