I'm trying to get an app to execute shortly after the tv restarts. After reading this page on androidtvnews.com, I tried "AutoStart - No Root" and "Launch on Boot" plus a couple other apps. Nothing seems to work, any advice is appreciated. (I'm using a Hisense U6G that shipped with Android 9)
Related
WARNING: This is what worked for me, on 1 device, with absolutely no ill effects.
WARNING WARNING WARNING:
My KF had Firefirefire/twrp working perfectly before this. Before doing this ALL DATA should be backed up from the kindle fire to your PC because this will COMPLETELY wipe the device to as it came of of the box brand new to you! NOTHING IS SAVED.. REPEAT BACK EVERYTHING UP BECAUSE ITS GONE AFTER THIS!
1. Download the amazon 6.2.1 update: Link is in the first reply to this post (Thanks b63), look towards the bottem of the page where it says "download the file directly to your PC."
Original instructions:
I can't post direct links so someone please link the direct link to the file in their reply.
Here is what to google: Amazon.com Help: Kindle Fire Software Update Version 6.2
The one you are looking for is the first white link at the top (not the orange one as its an advertisement). Download link is towards the bottem of the page.
2. Change the extension of the above file from .bin to .zip and copy it to your kindle.
3. Go into TWRP (reboot device and hold power button until it turns orange.) Select install, pick the update-kindle-6.2.1_D01E_3103920.zip or whatever you renamed it to and install it....
3a. Once install is finished TWRP will restart itself if you click reboot. However, if you select power off, unplug the usb/charger from your kindle and power it on, after about 2-3 minutes you will be sitting at the "select a network" portion of the kindle factory software setup.
4. Once you are at the network setup screen touch "complete setup later" in the bottem left corner. Click OK to confirm you know you have to pick a network and register the device later if you choose to.
4a. Work your way through the initial device welcome thing till you get out of it.
5. touch the settings bar and hit more. goto Device (near the bottem), and select Reset to factory defaults (last option on the device menu).
5a. Click erase everything and wait.
Congratulations. After a short process the device is in factory fresh state.
You may now safely resell/return your device.
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.2.1_D01E_3103920.bin
If you successfully use this method to go back to factory please post your experience or if you have any questions please post those as well
Thank you for these steps, I used them to unbrick my Kindle Fire.
Scenario: Was running FireFireFire with Kindle 6.21 software. The device became frozen at the FireFireFire yellow triangle at startup. I tried holding down the power button for different lengths for time but couldn't get it unstuck. Here's how I finally got it fixed:
I followed the instructions at: http://forum.xda-developers.com/showthread.php?t=1408056
to setup Kindle Fire Utilities.
1) Download v6 of the Kindle Fire Utility from here. (The forum thread can be found here)
2) Extract the files into a folder anywhere (but remember where, obviously)
3) Go into the folder, then into 'drivers' and open up adb_usb.ini in a text editor and add "0x18D1" (without the quotes) on a line underneath "0x1949"
4) Open up Device Manager and find "kindle". It should have a yellow triangle near it.
5) Updated the kindle fire driver by pointing to the Kindle_Fire_Utility_v6\Kindle Fire Utility\drivers\ folder
6) Ran the Kindle Fire Utility (run.bat)
7) Changed the boot mode to normal
8) Kindle fire still wouldn't boot, but would let me enter the recovery screen
9) Went to amazon.com, clicked on help, typed in kindle fire software update, and followed the links to download Kindle Fire Software Update v6.22
10) I renamed the file from update-kindle-6.2.2_D01E_3205220.bin to update-kindle-6.2.2_D01E_3205220.zip
11) Copied the file over to my kindle fire
12) installed update-kindle-6.2.2_D01E_3205220.zip
13) After a few minutes, my Kindle Fire was back in its factory fresh *working* state with no FireFireFire bootloader.
This might seem like common sense, but make sure you put your kernel back to stock first. Otherwise, you'll end up with a Kindle that's stuck in a crash-reboot loop that you have to reload FIREFIREFIRE and TWRP on to fix.
Don't ask me how I figured that one out.
Removing firefirefire, without twrp
I have been studying up on the process of rooting my kindle fire, and when i got down to it, the Kindle fire utility just wasn't working for me like it should. I couldn't install TWRP or root. However, i was able to install fff just fine. i reached my wits end trying to figure out what i was doing wrong, or if there was something i was missing, so i decided to reset to factory until there was a better method for me. The problem is that now, whenever i reboot, it loads fff first. not a huge deal since its the latest version that lets you select boot modes... just annoying. So now im stuck in limbo between a rooted device and factory settings. Can someone give me some advice on removing fff where i was never able to successfully install TWRP? Thanks everyone.
luminaeus said:
This might seem like common sense, but make sure you put your kernel back to stock first. Otherwise, you'll end up with a Kindle that's stuck in a crash-reboot loop that you have to reload FIREFIREFIRE and TWRP on to fix.
Don't ask me how I figured that one out.
Click to expand...
Click to collapse
Forgive me for sounding dense... but isn't the kernel part of the ROM?
Hi, I have a big problem.
I installed CM7 with TWRP and I rebooted my KF. CM7 was ok.
My second step was to install gapp, so in CM7 I rebooted the KF in recovery mode, but now I have a vicious circle.
In TWRP I press reboot in system mode or in "power off" mode, but in each cases the KF continue to entry in TWRP without I press the power button.
It's impossible to launch android system.
If I use the KF utility, this recognize KF, but if I launch some option, it's stopped to wait for device.
Please help me.
Thank you
(sorry for my english )
a small video.....
on youtube: /watch?v=hUnGTR2DQDY
you need to update divers. I installed the divers with kindle utility and they didn't work. Try searching the threads
Edit.. don't worry I've been here so many times with different things. It seems to be very hard to brick a kindle. Its stuck in boot loop and this has been covered so many times. Hope this helps. If you can't find the right thread let me know and I'll have a look for you.
Sent from my Galaxy Nexus using xda premium
airjump said:
Hi, I have a big problem.
I installed CM7 with TWRP and I rebooted my KF. CM7 was ok.
My second step was to install gapp, so in CM7 I rebooted the KF in recovery mode, but now I have a vicious circle.
In TWRP I press reboot in system mode or in "power off" mode, but in each cases the KF continue to entry in TWRP without I press the power button.
It's impossible to launch android system.
If I use the KF utility, this recognize KF, but if I launch some option, it's stopped to wait for device.
Please help me.
Thank you
(sorry for my english )
Click to expand...
Click to collapse
If you are running windows this is the easiest way to go about fixing any booting problems that you may be having
http://forum.xda-developers.com/showthread.php?t=1428428
If you are not using windows look in my guide and the fix is also in there to do it manually from a command prompt:
My guide http://forum.xda-developers.com/showthread.php?t=1417234
Remember to hit that thanks button if this helped you
Hi Everyone,
I just rooted my phone (and if your an Aussy you know what rooted means - basically it means that you have stuffed it). I was following the instructions on this page - Motorola Defy: Full Update Guide, and whilst doing so I made an error under the "Installing bootmenu & the ClockworkMod Recovery" section.
Now whilst I have the boot menu installed, none of the menu items within the boot menu actually work. Instead of seeing particular (desirable) activities on the phone I see messages along the lines of "Error in /system/bootmenu/script/xyz.sh" whenever I try any of the menu items. I have even selected the "[Uninstall Bootmenu]" option only to see the error "Error in /system/bootmenu/script/uninstall.sh"! Now I am really stuck as I cannot uninstall the boot menu and try again, and my phone simply won't boot to the ROM (CyanogenMod) that is installed.
Due to the fact that I cannot boot into the ROM / phone normally I am unable to run the ADB command from a prompt.
If anybody has any ideas on how I might be able to get around this stale mate they will be greatly appreciated.
Kind Regards,
David
Flash an sbf, root your phone, install the 2ndinit 2.3 apk(search with Google) and you shall have a working boot menu
Sent from my Nexus 7 using XDA Premium HD app
Hello XDAers,
I am a real noob at rooting or android-related, and a true one voided of any knowledge regarding anything IT- related.
So dear veterans, please go easy on me.
Due to my prior success of rooting and flashing my Nexus 4 successfully a few months back with no issues, I decided to give it a try to flash a custom ROM for my dad's LG Optimus L7 - which seemed an easy task compared to configuring my Nexus 4 - since there was no need for inputting any command lines or any dealing with the abd (using the easy shortcut, that is).
So, I followed the guide here: http://forum.xda-developers.com/showthread.php?t=1906133 ...
I first factory resettled the phone because it was bloated, then applied the "RunMe.bat" from the "What you desire!" folder. (Everything was already backed-up beforehand.) But the process didn't success until I've retried again and again by re-plugging the USB in because the application/PC couldn't detect the phone. In the same time, I was running KDZ_FW_UPD.exe in the background, so unexpectedly for me the phone shut itself and pushed itself to a vividly green emergency screen, then in a few seconds switched back to a screen of purple-white-blue glitches. I had to close KDZ_FW_UPD.exe without knowing what quite happened since it seemed to be the cause and restarted the process with RunMe.bat.
I didn't manage to "Restore" it first due to the fact that the phone stopped responding due to a lag asking for an encryption key. It was lagging so hard and I had to close the cmd around 5 tries while it was processing, but succeeded later on.
And then, to verify whether I've actually suceeded in rooting L7, I installed Root Checker from the Play Store. And again, for the first few tries the program froze on screen for a long period of time due to "system performance", but after rebooting and restarting the app a few times again, the ROOTING proves to be a success. Just to be sure, around this time I've reloaded KDZ_FW_UPD.exe and it suceeded.
So I went to install CWM and ES. CWM for recovery boot and ES for removing pre-installed system apps as the phone was lagging so badly. I've downloaded the CWM restoring(something like ~6.0.28?) first and tried fastbooting immediately right after, but instead of getting the fastboot menu I got a screen emptied in black with these words:
[5020] "Secure booting error"
[5020] "Cause: boot certification verify"
No hard keys could do anything on the presumed "fastboot", and so I had to hard boot again. I thought that it might be due to the lack of memory(checked on ES later on that it was 310~MB/2GB), and so I've used ES to uninstall a lot of system apps which I deemed uneccessary. So I've Googled a bit and it became apparent to me that that I've didn't unlock the device properly, so lurked around and found a file called L7CWM that is supposedly to resolve my problem, but I presume that it's the CWM recovery image that I've installed. So in the end, I didn't bother with it but kept it on tab just in case.
I repeated the same process with CWM again, but this time, the screen was joined with all kinds of flowery glitches. Restarted the device, and it went only downhill: now the Home launcher stayed all pitch black and nothing appeared. I waited a few minutes, but nothing there until the notification bar appeared. The home screen is apparently dead, and so are the menu keys. Switched to Nova Launcher(installed it just in case Home Launcher fails), and still dead. I couldn't access using any of the menu keys and had unusable launchers.
Hopefully I could still access to the settings from my status bar, but when I did, it started crashing immediately.
I've repeated the attempt a few times after restarting the device a few times, but nothing helped. It only got worse that the when the launcher did SEEM to work. It only showed the wallpaper without showing any of the icons/apps. And crashes again.
I could still access to the App menu via the settings, but couldn't open any of them and when I tried to uninstall them, the screen frozes immediately right after I gain access to the page (white page though) and gain this message: "Unfortunately Package Uninstaller Stopped!"
Then I convinced myself that the only thing I could do at the time was to factory reset the phone and then everything would go alright since I've just had to restore the system apps.
But then the black screen of death came right along with it:
"Secure booting error"
It seems that I'm out of luck... ... But just to check if I'm still left with resorts, I've downloaded the L7CWM file online...
... ...but it still didn't help.
So now I'm being left with no other choices other than asking for help. I never really understand what KDZ_FW_UPD.exe does since I had the LG Driver already before installing it, which I presume was for updating the phone to a newer or older version. And too complex tech articles are kind of alien for me.
EDIT(1 hour later): Okay, now I figured out the reason why L7CWM didn't work was because I didn't extract it to the right folder (after double checked via notepad that I was supposed to directly put it into the C:\ drive). Now it worked(?), but then it didn't.
After launching Flash_Bootloader.bat:
This message now appeared on the L7:
"Sorry!"
"SuperSU is not responding.
Would you like to close it?"
"Wait - Report - Close"
and a few minutes later
"Sorry!"
"Unfortunately, SuperSU has stopped."
"Report - OK"
Now I think the bugs till now happened was due to the fact that I've deleted a file that was required for me to launch apps... Now I just need the right fix.
After 5 minutes of screen inactivity the phone restarted by itself, kind of creepy... ...
Flash_Recovery.bat did nothing.
Reboot2Recovery.bat made it reboot but still struck on the same menu.
Nothing seems to be effective via the phone anymore, seems like I have to rely on abd but then again I don't know how... ... My dad is also f*cking pissed off ^ ^;...
__________________________________
I think that I explained the logs pretty precisely in case I missed something... I'll be very very very very very very thankful if someone could tell me what has caused my phone to fail though.
For references, here are the phone's specifications:
Model Number: LG-P705g
Android version: 4.0.3 (Stock)
Rooted:Yes (root checker)
Baseband version: MSM7227A-1-AA
Kernel version: 3.0.8-perf
Build number: IML74K
Software version: V10e-AUG-10-2012
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
remove the battery for 10 seconds,put it back pres VOL+ and VOL - same time and than press the power button.when you feel a vibration press for many times the button wich is down in right,try for many times and maybe it will working :}
Cydes said:
Hello XDAers,
If I don't get the phone fixed to being usable soon I think that I will get butchered real hard... ... Preferably needs a step-by-step guide made for toddlers... ...
Click to expand...
Click to collapse
simple answer for your
just download your stock rom
go to emergency mode
and flash that stock rom
Two days ago my wifes 1st generation Nexus 7 refurb started giving the "Unfortunately, NFC service has stopped" error. You click OK and the error instantly pops up again. There is a moment to click on something if you're fast and I've been able to click on settings but when settings opens it's nothing but a black screen with no options. This means that I can not enable usb debugging. I have tried quite a few different processes, ADB sideload, going through the bootloader, but they all seem to require usb debugging and the tablet is never recognized. The tablet is stock but I have no way of knowing what version of android it is currently running with the blank settings window (unless you can give me a tip on that). Have done two wipe/factory restores on it and the error comes up right at the first boot screen. I am willing to pursue any option to get this tablet in working order. Rooting, flashing, whatever but I am a novice in the world of android rooting. It was purchased off groupon (won't make that mistake again) and the 14 days are past so If I have to send it in, it's cash money out of our pockets.
Do I have any options? Thank you for your time!
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
notnorm said:
Most frustrating of all is that everything else about the tablet seems to be functioning normally. I can install apps from google play. I can't really run many of them though.
Click to expand...
Click to collapse
If the tablet has never been rooted, and the factory reset procedure seemed to complete successfully, then your symptoms suggest that something is wrong with the /system filesystem - which, for stock devices is never modified (always mounted read-only).
So that in turn suggests *perhaps* flaky hardware - probably the flash memory chip - that has gone awry and is the root cause of the problem.
It is conceivable that you could go through the process of unlocking the bootloader and re-flash a Google-provided "factory image", and that the problem will go away. But if the root cause is really a flaky flash memory chip, it will very likely return with a vengeance, and your efforts will be for naught.
There is something missing in your narrative, however - if the appearance of the "NFC Service has stopped" dialog on-screen prevents you from interacting with your (intended) foreground apps, how were you able to perform a factory reset and then follow that up with a tablet configuration? (e.g. to get Google credentials on the tablet so you could push apps to it by using a PC Web browser from the Google Play market).
If you are unfamiliar with rooting but still want to proceed with reloading the factory images, you will have to follow the Stock Recovery tutorial threads. Many users - especially those with Windows machines - seem to get stuck at this step, although truth be told that has nothing to do with Android, and everything to do with Windows Driver Installation Hell.
Note - specific to your situation.. You do not need to enable USB debugging to re-flash factory stock images. You only need to communicate with the device (booted into bootloader mode) with the "fastboot" program. For this you only need working USB hardware - not "adb".
good luck
BTW, note that you can perform a factory reset in the stock recovery without launching it from the O/S. The sequence is:
1) Turn the tablet off (not screen off, but powered completely off)
2) Boot into bootloader mode by holding Power+Vol-Down together (hold them down until android lying on its' back shows up - about 4 seconds)
3) Using the vol-up/vol-down button, select "Recovery Mode" on screen and press the power button
At this point the screen will go black. Wait about 10-13 seconds. The screen will remain black even though the stock recovery is now running. To get the screen to show the (stock) recovery menu,
4) press and release the Power & Vol-Up keys simultaneously.
The stock recovery menu should show now up. If it doesn't, try again. (After 60 seconds if you have done nothing, the tablet will reboot to the "normal" OS).
5) Use the on-screen menu to perform a factory reset (follow the directions on-screen for key usage).
Thank you so much for your response! The unanswered question is that I managed to put in the network info and what not during setup by hitting OK on the error and tapping the letter in the moment before the error popped up again. Not a fun task!
I've been trying to flash and after installing the google usb drivers it's still doing the <waiting for device> for infinity. I think I will have to bite the bullet and send it in. You saying that it might be a flash chip is kind of comforting because I think I might have bashed my skull against this issue forever before giving up!
Chris
flashed the wifi fix for the TMObile us version (from the X Note rom page)and was able to get out of the loop.