i may have missed something epically simple, type this
Code:
adb shell
su
idme print
Time and Date WAY OFF and no WIFI
- Thread starter lilmonk3
- Start date
- Status
i may have missed something epically simple, type this
C:\Users\TECH\Desktop\KFFirstAide100>adb shell
shell@android:/ $ su
su
shell@android:/ # idme print
idme print
Reading idme data ...
version: 1.2
boardid: 8030800000000000
serial: D059A0A024540EP5
mac: F0A2253D4559
sec: K0NYSPMK13IAGLUC9B93
bt: F0A225400980
pid: 00000000000000000000000000000000
pid2: 00000000000000000000000000000000
bootmode: 1
postmode: ↨
mfg:
shell@android:/ #
Yay this proves i was a moron. Now the question is, if idme can read this data, why can't the wifi module? I think i'm going to see if i can get hashcode to look at this if he's not busy because it's a bit more complex as to why it would be doing what its doing now.
Oh thought I might add you may wanna flash the original boot0 block back onto the device and see if the command works now on it as well since I made a stupid mistake. It more than likely was good considering the behavior yours is still exhibiting.
Sent from my Amazon Kindle Fire HD using Tapatalk
Sent from my Amazon Kindle Fire HD using Tapatalk
All looks about the same with the BAD boot0 except post mode..
sec: S6E6G9PQOL14PYSU3661
bt: F0A225108C62
pid: 00000000000000000000000000000000
pid2: 00000000000000000000000000000000
bootmode: 1
postmode: ▲
mfg:
shell@android:/ #
I am starting to wonder if one of the SM fuses near the wifi/gps chip is blown... I have experience in replacing and or bypassing those as I repair TVs and those blow often tvs.. If Hashcode doesnt have any other ideas, I think I will tear it apart and start testing the SM fuses and see what I find..
Link to onboard chip. http://d3nevzfk7ii3be.cloudfront.net/igi/HQpcFBgQLVfreIa1.huge
Link to onboard chip. http://d3nevzfk7ii3be.cloudfront.net/igi/HQpcFBgQLVfreIa1.huge
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1Very 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 Tapatalk1OK 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 Tapatalk1
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.
