Time and Date WAY OFF and no WIFI

lilmonk3 · Mar 2, 2014

Ok, I picked up a KFHD 7 cheap because it wouldnt connect to wifi.. Figured it would be a simple deal .. NOPE.. I have thrown everything at this thing from KFHD Img recovery , KFFA, Twrp and 2nd boot with and when I flashed kitkat roms it would just freeze at the blue KINDLE FIRE screen.. Nothing I have thrown at it has helped one bit.. It says my date is jan 22nd 2000 and wont let me turn on the wifi...I hit turn on wifi and it wont turn on, and date and time setting is greyed out and wont let me change.. Any have any ideas, this is driving me NUTS..

stunts513 · Mar 2, 2014

Something bad in the nvram? Think its also called the boot0block. That's just a guess, I know the Mac address for WiFi is stored there and it wouldn't be able to turn on if the address went corrupt, but I'm not so sure about how the kindles stores time, I know PC's store it in the cmos, not sure about a kindle, but I do know odd things are stored in nvram so Idk. If it were your boot0block I would have thought flashing to another ROM would have fixed it because I thought cm didn't grab the Mac address and made its own, but I could be mistaken. If you want more info try turning WiFi on/setting the time, and depending on if you are on amazon os make sure you are rooted, if your on cm I wouldn't worry it has root built in, connect kindle to PC and run a "adb shell su -c dmesg", right click in the command prompt, hit mark, highlight everything it posted and hit copy then paste it here in code brackets, depending on how big it is you may have to post it on pastebin. These instructions I gave you suck because I'm assuming your on windows, and windows doesn't have an unlimited number of lines you can scroll back in a command prompt like in Linux, you can set it to max out to either 99 or 999 lines but usually dmesg will exceed that I would think. If you know your way around a command prompt, try redirecting its output into a text file, I'm to lazy to put code brackets down so I can show you how with the right quotation right now, but here's a final tip if you do this, do it right after the device has booted go so there's not as much on the dmesg. Might also try a adb log cat at somepoint, but if there's some kinda hardware failure I would think dmesg would do the trick. Man this post was a bit more complicated and long than I intended, if you have any questions about what I said feel free to ask away.

Sent from my Amazon Kindle Fire HD using Tapatalk

lilmonk3 · Mar 2, 2014

I can not turn on or off the wifi. If I hit wifi it wont switch to on. I it would seem to me , that the time/date and wifi problem would be connected.. I was hoping that I would be able to get the time un greyed out and change it and everything else would fall into place.. Going to twrp, 2nd boot then kit kat today and see what happens... I have only tried custom rom once so far on this KFHD and it got stuck in KINDLE FIRE boot loop.. But I can get it to recovery to just about any amaazon OS.. Today is a new fresh day with new fresh eyes and mind , let the fun begin. One would have thought I would have bricked it by now with all the crap I have thrown at this KFHD, but hell I cant even accomplish that LOL

lilmonk3 · Mar 2, 2014

http://xdaforums.com/showthread.php?t=2274338

Well well there is my same problem.. Time to read until my eyes bleed again..

lilmonk3 · Mar 2, 2014

Code:

>[    6.264434] omap_rpmsg_mbox_callback: received echo reply from ipu !
>[    6.272186] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sam
ddr 0x32
>[    6.281555] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sam
ddr 0x33
>[    6.290863] virtio_rpmsg_bus virtio0: creating channel rpmsg-omx0 addr

>[    6.299530] rpmsg_omx rpmsg-omx0: new OMX connection srv channel: 1024
!
>[    6.386230] virtio_rpmsg_bus virtio1: creating channel rpmsg-omx1 addr

>[    6.394989] rpmsg_omx rpmsg-omx1: new OMX connection srv channel: 1024
!
>[   10.175415] wm8962 3-001a: bootup time wm8962_mic_detect_boot_work is c
!!!!!!!!!!!!!!!!!!
>[   10.433227] wm8962 3-001a: Detected removal
>[   10.438079] wm8962 3-001a: Iphone report 0
>[   11.936309] EXT4-fs (mmcblk0p13): recovery complete
>[   11.942260] EXT4-fs (mmcblk0p13): mounted filesystem with ordered data
 Opts: nomblk_io_submit,commit=20
>[   11.963226] EXT4-fs (mmcblk0p12): recovery complete
>[   11.969116] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data
 Opts: nomblk_io_submit,commit=20
>[   11.997528] EXT4-fs (mmcblk0p8): recovery complete
>[   12.003326] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data m
Opts: (null)
>[   12.033050] init: cannot find '/system/bin/uim-sysfs', disabling 'uim'
>[   12.081939] HDCP: **** hdcp_load_keys_cb ****
>[   12.086700] HDCP: loaded keys
>[   12.093322] ===========ATMEL TOUCH SENSOR DETECT================
>[   12.190643] boardIdCheck: *** board type: 803, revision: 8, variant: 0
>[   12.197753] boardIdCheck: capable of wifi OOB
>[   12.202758] ## wifi_probe
>[   12.205627] wifi_set_power = 1
>[   12.212432] bowser_wifi_power: Powering on wifi
>[   12.218811] Atmel touch sensor vendor gpadc value: 650
>[   12.225677] CPU1: shutdown
>[   12.231048] Atmel touch sensor is CMI.
>[   12.241699] loading atmel touch driver
>[   12.278594] warning: `bluetoothd' uses 32-bit capabilities (legacy supp
n use)
>[   12.367553] atmel_mxt_ts 2-004c: atmel touch driver version: 1.19
>[   12.378570] wifi_set_carddetect = 1
>[   12.389251]
>[   12.389251] Dongle Host Driver, version 5.90.195.34
>[   12.389251] Compiled in drivers/net/wireless/bcmdhd on Oct 18 2012 at 0
48
>[   12.431182] mmc1: unrecognised CCCR structure version 3
>[   12.436737] mmc1: Reverting CCCR structure version to 2
>[   12.465881] mmc1: new high speed SDIO card at address 0001
>[   12.472106] wifi_get_irq_number: irq number = 204 (we will be using OOB
rrupt ...)
>[   12.480926] F1 signature read @0x18000000=0x1680a8e7
>[   12.510375] dhdsdio_probe_attach: module maker = -1
>[   12.515563] dhdsdio_probe_attach: module maker name = (default: semco)
>[   12.522460] dhdsdio_probe_attach: nv_path was /system/etc/wifi/bcmdhd.c
>[   12.529663] dhdsdio_probe_attach: nv_path set to /system/etc/wifi/nvram
_semco.txt
>[   12.538909] dhdsdio_probe_attach: si_attach failed!
>[   12.544128] dhdsdio_probe: dhdsdio_probe_attach failed
>[   12.549591] wifi_set_power = 0
>[   12.552856] bowser_wifi_power: Powering off wifi
>[   12.557769] =========== WLAN placed in RESET ========
>[   12.564239] android_usb: already disabled
>[   12.568756] adb_bind_config
>[   12.572204] adb_bind_config
>[   12.576599] adb_open
>[   12.666168] PVR: Installing MISR with cookie c0867278
>[   12.692047] sr_class1p5_calib_work: core: Calibration complete: Voltage
nal=1250000Calib=1025500 margin=13000
>[   12.728424] SMC: SecureCRC=0xBC7458DC
>[   12.742797] Disabling non-boot CPUs ...
>[   12.748901] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie e
00
>[   12.856994] PVR: OSUnMapPhysToLin: unmapping 65535 bytes from e8da0000
>[   12.865844] PVR: SysFinalise: Version string: SGX revision = 1.2.0
>[   12.890533] android_work: sent uevent USB_STATE=CONNECTED
>[   12.902069] android_work: sent uevent USB_STATE=DISCONNECTED
>[   12.912933] SMC PA: INFO 00000001 00:00:00.000 ------ ------  ---------
- Booting... (t=17:24:29.520) SMCXG01.06p5.36479     /PlayReady Integration
>[   12.954345] SMC PA: INFO 00000002 00:00:00.037 ------ ------  ---------
- Booted
>[   13.029998] HDCP: hdcp_ioctl() - ENABLE 3489373951
>[   13.035491] HDCP: hdcp_work_queue() - START - 3489373959 hdmi=0 hdcp=1
0 evt= 1 0 hdcp_ctrl=00
>[   13.046020] HDCP: hdcp_ioctl() - WAIT 3489373967 0
>[   13.051971] HDCP: hdcp_work_queue() - END - 3489373974 hdmi=0 hdcp=1 au
evt=1 0
>[   13.068939] CPU1: Booted secondary processor
>[   13.073852] Switched to NOHz mode on CPU #1
>[   13.077484] android_work: sent uevent USB_STATE=CONNECTED
>[   13.091247] android_usb gadget: high speed config #1: android
>[   13.091308] android_work: sent uevent USB_STATE=CONFIGURED
>[   13.269714] atmel_mxt_ts 2-004c: Family ID: 161 Variant ID: 2 Version:
A Object Num: 23
>[   13.282440] atmel_mxt_ts 2-004c: configured max finger (32) is too larg
>[   13.289642] atmel_mxt_ts 2-004c: T53, start:148 size:5 instances:1 min_
tid:0 max_reportid:0
>[   13.298980] atmel_mxt_ts 2-004c: T37, start:153 size:130 instances:1 mi
ortid:0 max_reportid:0
>[   13.308502] atmel_mxt_ts 2-004c: T44, start:283 size:1 instances:1 min_
tid:0 max_reportid:0
>[   13.317810] atmel_mxt_ts 2-004c: T5, start:284 size:9 instances:1 min_r
id:0 max_reportid:0
>[   13.327056] atmel_mxt_ts 2-004c: T6, start:293 size:6 instances:1 min_r
id:1 max_reportid:1
>[   13.336303] atmel_mxt_ts 2-004c: T38, start:299 size:64 instances:1 min
rtid:0 max_reportid:0
>[   13.345703] atmel_mxt_ts 2-004c: T7, start:363 size:3 instances:1 min_r
id:0 max_reportid:0
>[   13.354919] atmel_mxt_ts 2-004c: T8, start:366 size:10 instances:1 min_
tid:0 max_reportid:0
>[   13.364288] atmel_mxt_ts 2-004c: T9, start:376 size:35 instances:2 min_
tid:2 max_reportid:33
>[   13.373687] atmel_mxt_ts 2-004c: T15, start:446 size:11 instances:2 min
rtid:34 max_reportid:35
>[   13.383300] atmel_mxt_ts 2-004c: T18, start:468 size:2 instances:1 min_
tid:0 max_reportid:0
>[   13.392639] atmel_mxt_ts 2-004c: T19, start:470 size:16 instances:1 min
rtid:36 max_reportid:36
>[   13.402221] atmel_mxt_ts 2-004c: T25, start:486 size:26 instances:1 min
rtid:37 max_reportid:37
>[   13.411834] atmel_mxt_ts 2-004c: T40, start:512 size:5 instances:2 min_
tid:0 max_reportid:0
>[   13.421142] atmel_mxt_ts 2-004c: T42, start:522 size:10 instances:2 min
rtid:38 max_reportid:39
>[   13.430725] atmel_mxt_ts 2-004c: T43, start:542 size:7 instances:1 min_
tid:0 max_reportid:0
>[   13.440063] atmel_mxt_ts 2-004c: T46, start:549 size:10 instances:1 min
rtid:40 max_reportid:40
>[   13.449645] atmel_mxt_ts 2-004c: T47, start:559 size:10 instances:2 min
rtid:0 max_reportid:0
>[   13.459075] atmel_mxt_ts 2-004c: T48, start:579 size:74 instances:1 min
rtid:41 max_reportid:41
>[   13.468658] atmel_mxt_ts 2-004c: T52, start:653 size:15 instances:2 min
rtid:42 max_reportid:43
>[   13.478271] atmel_mxt_ts 2-004c: T55, start:683 size:6 instances:2 min_
tid:0 max_reportid:0
>[   13.487579] atmel_mxt_ts 2-004c: T56, start:695 size:34 instances:1 min
rtid:44 max_reportid:44
>[   13.497192] atmel_mxt_ts 2-004c: T57, start:729 size:3 instances:2 min_
tid:45 max_reportid:46
>[   13.571716] atmel_mxt_ts 2-004c: status = 90
>[   13.580413] atmel_mxt_ts 2-004c: status = 0
>[   13.587493] atmel_mxt_ts 2-004c: Config CRC 0x56184F: OK
>[   13.593353] atmel_mxt_ts 2-004c: Resetting chip
>[   14.014556] atmel_mxt_ts 2-004c: Matrix Size X24Y32 Touchscreen size X7
79
>[   14.022644] atmel_mxt_ts 2-004c: Noise threshold is 30
>[   14.028686] atmel_mxt_ts 2-004c: Noise level report enabled
>[   14.040588] atmel_mxt_ts 2-004c: status = 0
>[   14.074401] input: AtmelTouch as /devices/platform/omap/omap_i2c.2/i2c-
04c/input/input6
>[   14.093841] atmel_mxt_ts 2-004c: mxt_start begin
>[   14.099334] atmel_mxt_ts 2-004c: mxt_start end
>[   14.118957] atmel_mxt_ts 2-004c: status = 10
>[   14.171295] atmel_mxt_ts 2-004c: status = 0
>[   14.197174] atmel_mxt_ts 2-004c: status = 40
>[   15.072448] atmel_mxt_ts 2-004c: status = 0
>[   15.108398] atmel chown of sysfs entry
>[   15.207427] Setting up thermal policy
>[   15.211517] Setting up thermal threshold for backlight_cooling device
>[   15.218750] Setting up thermal threshold for charger_cooling device
>[   15.953521] EXT4-fs (mmcblk0p13): re-mounted. Opts: discard
>[   16.046173] EXT4-fs (mmcblk0p12): re-mounted. Opts: discard
>[   16.144744] omap-iommu omap-iommu.0: iommu_get: ducati qos_request
>[   16.166656] omap_hwmod: ipu: failed to hardreset
>[   16.171569] omap-iommu omap-iommu.0: ducati: version 2.1
>[   16.179321] EXT4-fs (mmcblk0p8): re-mounted. Opts: discard
>[   16.695922] misc dsscomp: [e59c8400] ignoring set failure -22
>[   16.695983] mgr_blank while GO is set
>[   29.828186] request_suspend_state: wakeup (3->0) at 29824676516 (2000-0
17:24:46.436462404 UTC)
>[   29.886901] <6>MPL-accODR : 28571 mHz
>[   29.910430] <6>MPL-accODR : 5000 mHz
>[   29.933807] <6>MPL-accODR : 14285 mHz
>[   29.965576] bcm2076_bt_rfkill_set_power(On)
>[   30.041564] init: no such service 'dhcpcd_:-h kindle-658e19dc9 '
>[   30.075531] binder: 93:93 BC_REQUEST_DEATH_NOTIFICATION death notificat
lready set
>[   30.132598] acc_open
>[   30.135162] acc_release
>[   33.076751] atmel_mxt_ts 2-004c: atmel plug in value 1
>[   33.085601] atmel_mxt_ts 2-004c: atmel set charger bit 1, regval 210
>[   33.096740] atmel_mxt_ts 2-004c: status = 10
>[   33.113952] atmel_mxt_ts 2-004c: status = 0
>[   33.135894] atmel_mxt_ts 2-004c: status = 10
>[   33.159027] atmel_mxt_ts 2-004c: status = 0
>[   39.434936] init: cannot find '/system/bin/auto_shutdown', disabling 'c
shutdown'
>[   56.311859] binder: release proc 703, transaction 16260, not freed
>[   56.318817] binder: release proc 703, transaction 16415, not freed
>[   56.325439] binder: release proc 703, transaction 16419, not freed
>[   56.332122] binder: release proc 703, transaction 16627, not freed
>[   56.338775] binder: release proc 703, transaction 16696, not freed
>[   73.470336] binder: release 1105:1130 transaction 16311 out, still acti
>[   96.022827] binder: 1135:1146 transaction failed 29189, size 32-4
>[   96.029357] binder: send failed reply for transaction 16311, target dea
>[  106.144622] binder: release 1583:1583 transaction 19931 out, still acti
>[  107.385406] binder: 199:396 transaction failed 29189, size 8-0
>[  107.392028] binder: send failed reply for transaction 19931, target dea
>[  109.815032] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[  109.832336] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[  109.842926] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[  114.747283] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[  114.990295] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[  115.016479] EXT4-fs (mmcblk0p11): re-mounted. Opts: (null)
>[  116.162933] init: untracked pid 1155 exited
>[  116.167510] init: untracked pid 1156 exited
>[  116.213989] binder: 924:952 transaction failed 29189, size 0-0
>[  130.198883] bcm2076_bt_rfkill_set_power(Off)
>[  339.558746] request_suspend_state: sleep (0->3) at 339555236820 (2000-0
17:29:56.167022708 UTC)
>[  339.568603] atmel_mxt_ts 2-004c: set antitouch 2 30 8 176
>[  339.576965] atmel_mxt_ts 2-004c: mxt_stop begin
>[  339.583892] atmel_mxt_ts 2-004c: mxt_stop end
>[  339.593963] DSSCOMP: dsscomp_early_suspend
>[  339.606018] DSSCOMP: blanked screen
>[  339.699127] sr_class1p5_calib_work: core: Calibration complete: Voltage
nal=962000Calib=886240 margin=38000
>[  339.745849] sr_class1p5_calib_work: mpu Stop sampling: Voltage Nominal=
00 samples=11
>[  339.746002] sr_class1p5_calib_work: mpu: Calibration complete: Voltage
al=1025000Calib=848260 margin=10000
>[  341.081726] sr_class1p5_calib_work: mpu: Calibration complete: Voltage
al=1317000Calib=1076140 margin=0
>[  734.148132] request_suspend_state: wakeup (3->0) at 734144592289 (2000-
 17:36:30.756378177 UTC)
>[  734.177398] <6>MPL-accODR : 14285 mHz
>[  734.200805] <6>MPL-accODR : 5000 mHz
>[  734.223297] <6>MPL-accODR : 14285 mHz
>[  734.426513] bq27541 3-0055: Screen off drainage: -1 % over 394812 msecs
>[  734.433959] DSSCOMP: dsscomp_late_resume
>[  734.444915] atmel_mxt_ts 2-004c: mxt_start begin
>[  734.469940] atmel_mxt_ts 2-004c: mxt_start end
>[  734.475402] atmel_mxt_ts 2-004c: status = 10
>[  734.490356] atmel_mxt_ts 2-004c: status = 0
>[  735.517974] atmel_mxt_ts 2-004c: got action code 1
>[  735.676116] wm8962 3-001a: mutex locked wm8962_irq
>[  735.681549] wm8962 3-001a: FLL locked now disable FLL lock irq
>[  735.688293] wm8962 3-001a: mutex unlocked wm8962_irq
>[  737.829040] smb347 3-005f: USB disconnected
>[  737.833740] adb_release
>[  737.836730] android_work: sent uevent USB_STATE=DISCONNECTED
>[  737.842864] adb_open
>[  737.862396] atmel_mxt_ts 2-004c: atmel plug in value 0
>[  737.869018] atmel_mxt_ts 2-004c: atmel set charger bit 0, regval 242
>[  737.876464] atmel_mxt_ts 2-004c: status = 10
>[  737.887115] atmel_mxt_ts 2-004c: set antitouch 2 30 8 176
>[  737.893646] atmel_mxt_ts 2-004c: status = 0
>[  737.898925] atmel_mxt_ts 2-004c: status = 10
>[  737.968627] atmel_mxt_ts 2-004c: status = 0
>[  739.712158] smb347 3-005f: Spurious APSD IRQ!
>[  740.226715] smb347 3-005f: Detected charger: SDP
>[  740.238433] smb347 3-005f: Switching to USB5 mode
>[  740.247619] atmel_mxt_ts 2-004c: atmel plug in value 1
>[  740.254455] atmel_mxt_ts 2-004c: atmel set charger bit 1, regval 210
>[  740.261932] atmel_mxt_ts 2-004c: status = 10
>[  740.269409] atmel_mxt_ts 2-004c: set antitouch 2 30 8 176
>[  740.289581] atmel_mxt_ts 2-004c: status = 0
>[  740.311614] atmel_mxt_ts 2-004c: status = 10
>[  740.334686] atmel_mxt_ts 2-004c: status = 0
>[  740.893341] android_work: sent uevent USB_STATE=CONNECTED
>[  740.900238] android_work: sent uevent USB_STATE=DISCONNECTED
>[  741.076934] android_work: sent uevent USB_STATE=CONNECTED
>[  741.090118] android_usb gadget: high speed config #1: android
>[  741.096405] android_work: sent uevent USB_STATE=CONFIGURED
>[  750.316772] atmel_mxt_ts 2-004c: set antitouch 20 1 0 0
>[  918.487579] smb347 3-005f: USB disconnected
>[  918.494598] adb_release
>[  918.497589] android_work: sent uevent USB_STATE=DISCONNECTED
>[  918.504699] adb_open
>[  918.528198] atmel_mxt_ts 2-004c: atmel plug in value 0
>[  918.537322] atmel_mxt_ts 2-004c: atmel set charger bit 0, regval 242
>[  918.545104] atmel_mxt_ts 2-004c: status = 10
>[  918.550598] atmel_mxt_ts 2-004c: set antitouch 2 30 8 176
>[  918.573608] atmel_mxt_ts 2-004c: status = 0
>[  918.598999] atmel_mxt_ts 2-004c: status = 10
>[  918.627227] atmel_mxt_ts 2-004c: status = 0
>[  920.938079] atmel_mxt_ts 2-004c: status = 10
>[  920.957153] atmel_mxt_ts 2-004c: status = 0
>[  926.690368] smb347 3-005f: Spurious APSD IRQ!
>[  927.203369] smb347 3-005f: Detected charger: SDP
>[  927.223205] atmel_mxt_ts 2-004c: atmel plug in value 1
>[  927.231536] atmel_mxt_ts 2-004c: atmel set charger bit 1, regval 210
>[  927.238769] smb347 3-005f: Switching to USB5 mode
>[  927.243804] atmel_mxt_ts 2-004c: status = 10
>[  927.254821] atmel_mxt_ts 2-004c: status = 0
>[  927.269409] atmel_mxt_ts 2-004c: set antitouch 2 30 8 176
>[  927.275787] atmel_mxt_ts 2-004c: status = 10
>[  927.326721] atmel_mxt_ts 2-004c: status = 0
>[  927.747619] android_work: did not send uevent (0 0   (null))
>[  927.904907] android_work: sent uevent USB_STATE=CONNECTED
>[  927.912109] android_work: sent uevent USB_STATE=DISCONNECTED
>[  928.089782] android_work: sent uevent USB_STATE=CONNECTED
>[  928.125274] android_usb gadget: high speed config #1: android
>[  928.131622] android_work: sent uevent USB_STATE=CONFIGURED
>[  937.316070] atmel_mxt_ts 2-004c: set antitouch 20 1 0 0

stunts513 · Mar 2, 2014

Very interesting, i'm guessing it's the boot0block, I see it turned WiFi on, ran a process where I think it checked the nvram and then failed or something because it looked like the process unloaded a module or something, then WiFi powered off. I''ll look more into it when I get back home and can look at my kindles dmesg and compare it.

Edit: o wait that was a text file, and I was half asleep.
Sent from my LG-P769 using Tapatalk

lilmonk3 · Mar 2, 2014

Also when I do a wipe data and cache, it takes an extremely LONG time... About an Hour

dacetys · Mar 3, 2014

Had the exact same problem with the greyed out wifi and searched for a solution on and off for months, tried completely wiping it and restoring it to factory a couple times. It's not worth it. Ended up just sending it back to Amazon for a replacement.

lilmonk3 · Mar 3, 2014

dacetys said:
Had the exact same problem with the greyed out wifi and searched for a solution on and off for months, tried completely wiping it and restoring it to factory a couple times. It's not worth it. Ended up just sending it back to Amazon for a replacement.

Thats not an option as I am not the org. owner and I have never had it registered under my name

stunts513 · Mar 3, 2014

I'm going to see if hashcode has anymore info on this, I compared it to mine and I don't see it doing what yours is doing so I'm still guessing its the boot0, but he should know more. Also misread that line and typo'd what I was trying to say because I was sleepy.

Sent from my Amazon Kindle Fire HD using Tapatalk

lilmonk3 · Mar 3, 2014

stunts513 said:
I'm going to see if hashcode has anymore info on this, I compared it to mine and I don't see it doing what yours is doing so I'm still guessing its the boot0, but he should know more. Also misread that line and typo'd what I was trying to say because I was sleepy.

Sent from my Amazon Kindle Fire HD using Tapatalk

I have another KFHD .. If the Boot0 is screwed on this one and there is no way to repair, can I pull the one off my other one and use it on this one.. I will be putting a rom on this one and have no intentions of using it as a KINDLE with amazon

stunts513 · Mar 3, 2014

OK yes you could, assuming that I understand how it works, you might ha be issues if you attempt to use both on the same router at the same time, also as long as it is the same version kindle (7") you should be fine with pulling it and flashing it over the current boot0block, however I don't recommend doing this yet until I find out the name to flash it to in fastboot mode, also recommend backing up your own boot0block just in case, hey you might get lucky and still have a partially bad boot0block with some data intact you could overwrite on the other like serial number and such. Like I said lemme talk to hashcode first, I talk to him on the Irc a bit but he doesn't always respond immediately so maybe I'll have an answer sometime tomorrow.

Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 · Mar 5, 2014

Wait i don't think i noticed this, you are still running a stock rooted amazon os? you never got cm working, it always bootlooped? If so you did wipe data correct(factory reset)? I asked hashcode about it and he said some of the wifi data is stored in the cache and to try that first off. So try a factory reset and see what happens, wouldnt mind seeing what happens on cm as well, but i would have to help you figure out whats with the bootloop you get on it if its not related to you needing to do a factory reset.

lilmonk3 · Mar 5, 2014

stunts513 said:
Wait i don't think i noticed this, you are still running a stock rooted amazon os? you never got cm working, it always bootlooped? If so you did wipe data correct(factory reset)? I asked hashcode about it and he said some of the wifi data is stored in the cache and to try that first off. So try a factory reset and see what happens, wouldnt mind seeing what happens on cm as well, but i would have to help you figure out whats with the bootloop you get on it if its not related to you needing to do a factory reset.

Yes I cant ever get a ROM to load..It always goes to the KINDLE FIRE screen and hangs or hangs awhile then will go into twrp.. Yes I have did factory reset many times. I have wiped the user data and cache in TWRP , KFFA and KF recovery programs... Driving me Batty.. Oh my other KFHD it had a temporary issue with the wifi and it all straighened out when I reflashed it.. And it never showed this crazy ass date... I am going to give twrp and 2nd BL another try tomorrow.. I really can not believe I have not bricked this thing yet..

stunts513 · Mar 5, 2014

lilmonk3 said:
Yes I cant ever get a ROM to load..It always goes to the KINDLE FIRE screen and hangs or hangs awhile then will go into twrp.. Yes I have did factory reset many times. I have wiped the user data and cache in TWRP , KFFA and KF recovery programs... Driving me Batty.. Oh my other KFHD it had a temporary issue with the wifi and it all straighened out when I reflashed it.. And it never showed this crazy ass date... I am going to give twrp and 2nd BL another try tomorrow.. I really can not believe I have not bricked this thing yet..

As long as you don't flash a bad bootloader or thew wrong bootloader, or maybe the wrong kernel, it should not brick to the point it won't turn on. So right now you are in stock amazon os right? i cant think of a reason why you would be going into twrp recovery when trying to boot up without having a bad system flash or something, the only time that tends to ever occur is when you flash twrp + 2nd bootloader and your amazon os isn't the same as the freedomboot image version. Give me some more info and such and i'll see what i can do.

lilmonk3 · Mar 5, 2014

stunts513 said:
As long as you don't flash a bad bootloader or thew wrong bootloader, or maybe the wrong kernel, it should not brick to the point it won't turn on. So right now you are in stock amazon os right? i cant think of a reason why you would be going into twrp recovery when trying to boot up without having a bad system flash or something, the only time that tends to ever occur is when you flash twrp + 2nd bootloader and your amazon os isn't the same as the freedomboot image version. Give me some more info and such and i'll see what i can do.

my amazon OS is 7.2.3 and following is the files I have been working with using fire flash
kfhd7-twrp-2.6.3.1-recovery.img
kfhd7-freedom-boot-7.2.3.img

lilmonk3 · Mar 5, 2014

lilmonk3 said:
my amazon OS is 7.2.3 and following is the files I have been working with using fire flash
kfhd7-twrp-2.6.3.1-recovery.img
kfhd7-freedom-boot-7.2.3.img

And tried the hashcodes kitkat.. Not sure of the file name, because I am not at home to look

lilmonk3 · Mar 5, 2014

Also when I go to wipe data and cache let say in KFFA, it takes close to an hour to do so... That seems jacked up

lilmonk3 · Mar 5, 2014

heres the rom I have been trying cm-11-20131126-UNOFFICIAL-tate.zip

wire55 · Mar 5, 2014

Use cm-11-20140117-UNOFFICIAL-tate.zip

Sent from my Kindle Fire HD 7 using XDA Premium 4 mobile app

Time and Date WAY OFF and no WIFI

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts