I was contacted by a user who discovered a 'secret code' that applies to the FireOS search bar (Unified Search). When you type it into the search bar, you enter retail demo mode.
Code:
;demo
There are several major problems with this once you enter it. One: you can't get out. You can resell the device when you're done, but one of two things happen: On the fire 7: it powers off your device, reboots it and erases it. Then it reboots...into a logo loop. Fire HD 10: When you resell, your screen is blocked by an amazon logo overlay. It just sits there. You can reboot and the overlay remains. You can't disable it through ADB on either of them it doesn't do you any good, because you stay in demo mode. I forgot to mention the countless demo apps it tries to download. This code also worked on the HD 8, but I didn't go past the splash screen. Only way out is a factory reset via recovery.
I got a screen cap of the debugging menu. There is an application version have never seen before. Is this the retail mode application version? If not, what is it? No the device is not registered.
Code:
1.1.906.0-tablet_424010
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DragonFire1024 said:
I was contacted by a user who discovered a 'secret code' that applies to the FireOS search bar (Unified Search). When you type it into the search bar, you enter retail demo mode.
Code:
;demo
There are several major problems with this once you enter it. One: you can't get out. You can resell the device when you're done, but one of two things happen: On the fire 7: it powers off your device, reboots it and erases it. Then it reboots...into a logo loop. Fire HD 10: When you resell, your screen is blocked by an amazon logo overlay. It just sits there. You can reboot and the overlay remains. You can't disable it through ADB on either of them it doesn't do you any good, because you stay in demo mode. I forgot to mention the countless demo apps it tries to download. This code also worked on the HD 8, but I didn't go past the splash screen. Only way out is a factory reset via recovery.
I got a screen cap of the debugging menu. There is an application version have never seen before. Is this the retail mode application version? If not, what is it? No the device is not registered.
Code:
1.1.906.0-tablet_424010
Click to expand...
Click to collapse
Huh, I guess Amazon is really bad at making demos, which probably explains why Best Buys always throw out the old Demo Amazon devices. Now, how is the issue different on different devices?
Sent from my KFAUWI using Tapatalk
Related
So that is pretty much the story. I am about to purchase the fastboot factory cable off of ebay. After some further reading on people having similar problems, I see that using adb is good, but it is required that the machine is in developer mode (as far as I understand). http://androidcowboy.com/2013/07/how-to-recover-bricked-kindle-fire-hd/
I got this KDH for free because it is "broke", I figured I would try to fix it for fun. Just wondering what all the experienced people have to say about it being worth it. I know I cannot know anything without the cable, but that being said... If I get the cable I am 99.9% sure it is not in developer mode, so am I even going to be able to do anything?
Thanks!
Ryan
You can repair most problems by getting into fastboot and flashing the system images again.
Could you give a better description of the Kindle Fire (camera on front, hdmi port, etc) and what state the device is in. You say hard brick, but does it turn on?
No response to power button, even holding down for the "20 seconds". Also I cannot get it to boot by holding power and volume down or up. I determined the model and "version" by the serial number given to me by the previous owner. The first 4 digits I have are D025.
Found here: http://glyde.com/glydecast/how-to/which-kindle-do-you-have/
Check the Serial Number
You can find this sixteen digit code in the box your Kindle came in or when you click on Settings and go to Device Info. Find your specific generation or type based on the first four characters.
Kindle 2: B002, B003
Kindle DX: B004, B005, B009
Kindle 4: B00E, B023, 9023
Kindle 5: B012
Kindle Keyboard: B006, B008, B00A
Kindle Paperwhite (2012): B024, B01B, B01C, B01D, B01F
Kindle Paperwhite (2013): B0D4 or 90D4
Kindle Touch: B00F, B010, B011
Kindle Fire (2011): D01E
Kindle Fire (2012): D026
Kindle Fire HD 7(2012): D025 and D059
Kindle Fire HD 7(2013): 00D3 and 00D2
Kindle Fire HD 8.9: B0C9, B0CA, B0CB, and B0CC
Kindle Fire HDX 7: D0FB, 00FB, 00FC, 0072, 00FD, 00FE, 0073, 006C, 006D, 006E
Kindle Fire HDX 8.9: 0018, 0057, 005E, 00F3, 0019, 0058, 007D, 007E, 007F
Click to expand...
Click to collapse
I did follow this flow chart, but I ended up with two possibilities, KFHD 7" Gen 1, and KFHDX 7". Because I cannot turn it on, I cannot tell what the lock screen looks like.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So you are confident that with the cable I can at least get to a fastboot, knowing that the developer mode was never turned on?
Thanks for your input
EDIT: On the back of the Kindle Fire, it has a Model No. of X43Z60. I have not taken the time to look that up, as I just found it.
If it doesn't power on it is definitely a hard brick and a fastboot cable won't help
So, because there is no power on reaction, you believe this is a lost cause?
Just making sure...
There are ways to recover, but I don't know them. I believe you have to solder and access the SD through Linux.
Hey Guys, this one is a doozie. My fire 7 screen has mirrored itself. The touch panel is regestering the correct locations and a screenshot sent to the computer looks fine, but the screen is mirrored on the tablet (as in it reads correctly when held to a mirror. This is not the RTL layout in the developers options. Even the Amazon logo during startup is mirrored. It happened randomly when I turned on my tablet from sleep mode, and it hasn't been the same since. Also, no, this is not a rotation error as not matter what the screen is rotated to, it is displayed wrong.
I have restored to stock and installed TWRP and a custom rom to see if any of those would fix the issue to no avail. I also took the tablet apart, inspected the logic board, ad disconnected/reconnected all internal connections, but that didn't make a difference either.
Is there any way to fix this? Amazon won't fix it without me paying, but a new Fire is cheaper than a repair (although the new ones are locked down). It seems to be a kernal/boot/weird bit that got flipped somewhere, but I haven't been able to track it down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JM0535 said:
Hey Guys, this one is a doozie. My fire 7 screen has mirrored itself. The touch panel is regestering the correct locations and a screenshot sent to the computer looks fine, but the screen is mirrored on the tablet (as in it reads correctly when held to a mirror. This is not the RTL layout in the developers options. Even the Amazon logo during startup is mirrored. It happened randomly when I turned on my tablet from sleep mode, and it hasn't been the same since. Also, no, this is not a rotation error as not matter what the screen is rotated to, it is displayed wrong.
I have restored to stock and installed TWRP and a custom rom to see if any of those would fix the issue to no avail. I also took the tablet apart, inspected the logic board, ad disconnected/reconnected all internal connections, but that didn't make a difference either.
Is there any way to fix this? Amazon won't fix it without me paying, but a new Fire is cheaper than a repair (although the new ones are locked down). It seems to be a kernal/boot/weird bit that got flipped somewhere, but I haven't been able to track it down.
Click to expand...
Click to collapse
Sure you have the right forum (5th gen Fire)? I assume device has the 5.0.x bootloader as you referenced TWRP which can be booted but not installed. You could try reflashing the bootloader from this thread. Beyond that there may be a hardware or low level firmware glitch that can not be repaired.
I have scoured the internet for answers on why my developer options won't turn on. I'm running a note 8.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Some reason images not wanting to show.
Has a exynos5 as a chip the deviceis a sm-n950f. Phone says developer mode is enabled, but never shows up.
It be nice to root my note 8 one day lol.
Thanks,
Tim
Timsundead said:
I have scoured the internet for answers on why my developer options won't turn on. I'm running a note 8.
Some reason images not wanting to show.
Has a exynos5 as a chip the deviceis a sm-n950f. Phone says developer mode is enabled, but never shows up.
It be nice to root my note 8 one day lol.
Thanks,
Tim
Click to expand...
Click to collapse
Hate to ask such an obvious question but, are you aware the developers option shows up at the bottom of the main settings page, just under "about phone"?
Failing that, if you download this app from the Play Store, it should hopefully give you access to developers options menu, seeing as you have already enabled it by clicking on the build number 7 times
https://play.google.com/store/apps/details?id=options.developer.com.developeroptions
I know where developer options should be, it's not there.
Also the app is telling me to turn it on
Timsundead said:
I know where developer options should be, it's not there.
Also the app is telling me to turn it on
Click to expand...
Click to collapse
Did you tap on "Build Number" more then 7 times in about phone/software info.?
Keep on tapping it you'll see a toast message at bottom of screen counting down to 0 the it will say developers options enabled. Then back out of settings and reopen settings and scroll down to bottom. Might try rebooting the phone.
Worst case scenario is to do a BACKUP and factory reset. Not necessarily needed but who knows.
Hi
I know mykindle is old but my autistic son uses it and he cannot handle change thus still using it.
I have no idea how this has happened at all. BUt now it seems when I reboot the device, the notifications bit has a notice saying "tap to access launcher debug settings".
When I tap this it takes me to those settings (which I have never seen before in any of the settings area) and I can quit out of it.
Why is this happening and is it a sign of a bigger problem?
Just to be clear, while I do have ADB enabled (in case I brick it and need to use kindle-unbrick in the future) nothing else is unusual. It is not rooted and I have never put a custom rom/system/launcher on it at all.
I can only guess that this change has accurred because either a game I have installed has tweaked something, or, a particular tablet-crash has pushed this into being.
So is it a problem? Can I stop it? Why has it happened?
Any thoughts would be massively appreciated please.
Thank you.
Alex
Hello. Sorry for the late reply. Anyways, I'm happy to help you. I also use a Kindle Fire HD 7 2012, so you can expect the best results. IDK the reason of the problem, it appeared in the same way as yours. But the fix is so simple, take a closer look at it:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Long-tap at the notification (some program appeared at the top, don't pay attention to it):
Tap "Manage Notification", as the arrow above suggests.
So, you must have the same screen, applications may differ. Tap the "Off" toggle in the right corner after the "Launcher", as arrow suggests, and go to the home screen. When you will look at notifications, a message must disappear.
If you experience any further problems, let me know. I'll try to respond in my free time.
And thank you for posting the question, without it I couldn't solve it (really).
Have a nice day!
HTH,
Anonymous
Hello,
I've successfully managed to install OnePlus3T_28_A.86_191104_repack through MsmDownloadTool V4.0.71 where the Status of Communication is "Download Complete".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After this, when the phone boots, the OnePlus logo shows up for a little while – and after that, a black screen. I can only access fastboot – and that's about it. The phone is locked, etcetera, so I can't flash via adb/fastboot. When I try to access recovery mode through the fastboot menu, the screen becomes black too.
Worth mentioning I've also successfully installed through an older version of MSM before this. But same results. The version is the following OnePlus3T_28_A.23_161027 and the MsmDownloadTool V3.0.6.
What are the alternatives? Is it good game? If someone could pinpoint me what to do next would be glorious. The hard-brick guides seem to always point to the MSM way of things.
Thanks in advance!
Alright so I've been digging a bit deeper.
Stumbled upon a bunch of different YouTube videos that had similar solutions.
Most of them were squeezing, tapping and doing different motions onto the phone. Like pressing down the screen at different angles with some pressure, etc. Also from the back, the buttons to loosen them, etc. I'm sure I've missed some of the methods mentioned in the video.
However, the squeezing on the screen and the back actually made the phone go past the black OnePlus logo into the boot animation -- and I thought that was it. Apparently, it hung up half-way through.
The last method they mentioned was to put the phone in the freezer in a zipper bag and TRUTHFULLY it worked after being in there for 10 minutes. The phone booted up, went through the installation setup and it worked for a while... until it didn't.
Apparently, my battery does not charge and it's stuck at 0% all the time. Seems a bit suspect. Will dig further into it.