I got the fire hd6 so I could use my own apps on it, only to my discovery it uses the horrendous amazon store, and so I wanted to root it and done so using some root junky thing. It worked fully rooted for a day, but the next time I started it up, I got the infinite "Optimizing system storage and applications" loader.
This is where things get funky,
Factory reset using volume up+ power allows the hd 6 to work once (It boots to setup, but when I turn it off and back on, its stuck on optimizing system storage loader). Once I boot it up, the home screen is blank, and will freeze the tablet. However, if I push the power button off and back on the lock screen works fine, and from the lock screen I can open settings and turn on developer mode and enable adb debugging.
I did all the steps with android studio and got my drivers working for when the tablet is turned on (its on the list of adb devices), however when I volume up+power and try to boot with new firmware, my pc suddenly can't recognize it.
It's a shame because it's barely been used, and there are no guides online that could help me with this, the closest is root junky's guide, but his seems aimed towards later generations, and he doesn't have the issue of the pc not recognizing the adb device when its in the boot mode. I really don't want to trash it, but it's not like there are too many options.
Related
YUP. I "soft bricked" my t-mobile galaxy s (vibrant here in the us) or so I hope. The phone was rooted via z4 on the latest android t959uvji6 from t-mobile.
How did i do it? Brick my phone that is...
The 3d gallery was pissing me off by picking up everything on the phone. I tried clearing the default setting via the manage app but nothing changed so I decided to delete it. First backing up the apk and odex file from the system folder with titanium backup then deleted them from the system folder via root explorer. Rebooted the phone, pulled out the battery, waited for 30 seconds or so, popped in the battery and booted up the phone w/o any issues.
I tried installing the backup 3d gallery apk file and got the "app not installed" error on numerous attempts. Then tried simply copying it over again with ti backup and nothing happens. Gave up and said the heck with and went the factory restore route, got all the relevant apps installed and tried reinstalling the 3d gallery apk but resulting in the same "app not installed" error prompt. So I again copied over the apk and odex file into the system folder. Rebooted and nothing... phone does not boot into the home screen.
At this point here is what the phone is able to do.
It will boot up and display the default galaxy s animation, goes through it's array of colors then comes to a stop at all white letters then the screen goes blank and nothing happens - zip. nadda. i left it on for 12hrs like that - blank screen w/all the hard keys lit up.
What i did notice was win7x64 recognizes the phone after it gets into the blank screen of death as mass storage units.
So far i've tried booting into the recovery screen via the three button method and none of them works.
Did the karma-volume up-home-power twist - nothing
Did the karma-volume down-home-power roll - nothing
Did the karma-volume up and down-power jiggy - nothing
I tried the key combos for about 2hrs without any success then jumped into adb. After reading for a bit I realized that the phone was still rooted and the debug mode was enabled the last time i shutdown the phone (good'ol ti-backup)
For a while there adb did not recognize the phone at all but with an odd power cycling while spamming "adb reboot recovery" it was able to finally nab hold of the phone and jump into the recovery console. At first I thought it was pure luck so unplugged everything and tried it again - works every time if i did the odd out of sequence power cycle while spamming the adb console with "adb reboot recovery".
In the reboot recovery - deleted the user data and did the restore.
Here's where I think I really screwed up - now the phone is no longer in debug mode.
Long story short - is there a way to get into the recovery screen w/o debug mode on?
**quickly pulls on flack jacket**
but seriously any suggestions would be great
Wrong section bro. You probably won't get an answer here.
To answer your question. Yes, Remove Battery, Plug your phone to USB, Press and hold the volume down and the power button Put the batter back on. This should get you into download mode. Use ODIN to restore.
the usb jig trick did the work - now i have two phones!!!! (bought the nexus s yesterday) lol
Time to ODIN.
To access Download mode.
Unplug. press volume up and down togheter, and connect USB. VOILA!
If ODIN does not recognize it, plug and unplug again
chichu_9 said:
To answer your question. Yes, Remove Battery, Plug your phone to USB, Press and hold the volume down and the power button Put the batter back on. This should get you into download mode. Use ODIN to restore.
Click to expand...
Click to collapse
no!
Why the hell are people giving others ideas on how to get into download when their doing it wrong.
its JUST THE VOLUME BUTTONS, NOT THE POWER BUTTON ALONG WITH IT.
volume + power = Recovery, which in this case you probably cant get into
Volume - Power = Download mode, which everyone can get into unless if they somehow hard bricked, if its possible.
Thanks in advance for reading this and for any suggestions you might have!
I have a Archos Home Connect 35 Gen 8 device. I had it rooted on 2.4.82 firmware just fine. I wanted to update to 2.8.83 to get rid of the update notification I kept getting. I wanted to do it from a fresh clean slate as I wanted to reset my device anyway. First I used the Recovery Menu (White Menu) to restore back to default, then removed the SDE menu via the option to remove it in the SDE menu.
I then followed the guide that chrulri posted that I followed last time, but with 2.8.83 files. http://forum.xda-developers.com/showthread.php?t=930197 (Note for Archos 35's you have to hold the power button for ~6 seconds, then double tap it to get to recovery instead of holding Volume Down like on other Gen8's). I was doing this on my MacBook Air at the time. (I rooted it before from my Windows PC). I went to 'Update Firmware" on the recovery menu, then took the SDE firmware file, and copied it over USB to the drive and safely removed the drive, then hit "OK" on the device. It proceeded to do the update it seems but only took 2-3 seconds so I'm fairly sure something didn't go right as it usually takes longer. It then said press ok to Reboot so I did.
After the reboot from that, the device turns on but I get a White screen. No Archos logo or anything. Usually this white screen comes on for a few seconds, then I would get the Archos Logo even if I was booting recovery. No luck. I tried resetting the device by holding power button for 20 seconds, waiting 10 seconds and turning it on, same issue. Recovery will not work either, I tried two dozen times to try and get it to load by doing the usual ~6 seconds holding power button then double tapping and no luck.
I tried hooking the device up USB and in Windows all I get "Unknown Device" in device manager, with DeviceId of USB\Unknown. I attempted to force both Archos' ADB driver and the Universal ADB drive onto it with no success. (I'm pretty sure its my device since normally when a device shows up and its capable of ADB you will get a difference device ID in Device manager like USB\ADBDEV1 or something. On my Mac, when I plug it in, all USB devices (Multitouch pad mouse included) will lock up for ~5 seconds, then in dmesg I can see it has a error on USB device and it disabled the device.
So something weird is going on with my Home Connect for sure. Any suggestions on what to try? I'm thinking somehow the filesystem or firmware on it got screwed up during the SDE flash and it can't boot anything even the recovery now. I have a MicroSD card I can use if there's some recovery feature built into it to get it to boot from the MicroSD slot or something to do a firmware recovery.
My only other option if there is no way to try and get it back would be to try and send it back to Archos for repair simply stating it was updating firmware and this happened. (No actual modified firmware is on it now as well, and i was flashing the Archos approved SDE firmware, so they should be okay with it).
Also the battery was fully charged when doing this. It seems different that the White Screen bug the Archos 101 and others get when the battery accidentally runs too low with older firmware.
Thank you again for your replied!
If you can't get into recovery anymore, then it is over. I would suggest to RMA the device.
divx118
From all my searches through Archos forums and here that seems right.
I'm shocked there's no failsafe recovery mode for Archos. My Asus Transformer TF101 had one, where even if the firmware was screwed and you couldn't get to recovery, a special key combo would boot it up and you'd load some special recovery driver for it (Not adb something with nVidia in it, has to do with Tegra2 chipset i suppose) and upload the firmware to it and it recovered. Even iPhone's have DFU fallback mode as well for when things are totally forked and iTunes will restore the firmware.
Just an update. I did RMA the unit and Archos sent me a brand new boxed up one back. (I have an extra charger and cable now since they said not to include them ). Have my new 35 setup rooted with .83 now.
I think I figured out what happened. After I installed the SDE, before I flashed the new kernel and such, if I booted the Developer Edition option from recovery, it would get stuck at a blank white screen until I power cycled. On my old 35 I had removed the option to boot regular so it booted the Developer Edition that was rooted every time. I think when I restored the original firmware, it of course removes the Developer Edition kernel I had flashed before, but it somehow didn't set the menu back and was trying to boot Developer Edition every time, which it lacked the kernel for, and went to the white screen. Not sure if it explains recovery not working though.
To make sure it doesn't happen again i've left the options all in tact and left it so I manually have to go to recovery if I reboot the system to boot the developer kernel for root. Since the device goes weeks and months without the need to reboot since it's just an Alarm Clock really that's fine with me.
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon's wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Leav320 said:
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon''s wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Click to expand...
Click to collapse
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Davey126 said:
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
Click to expand...
Click to collapse
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
lekofraggle said:
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Leav320 said:
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Click to expand...
Click to collapse
Given the delivery date and age of device I STRONGLY recommend you reach out to Amazon for a replacement vs trying to resolve on your own. A new version of Fire OS is currently rolling out which MAY have triggered the behavior you are seeing. Bit of a bummer given your son's course plans but a worthwhile delay IMHO.
I agree with Davey.
Sent from my KFTHWI using Tapatalk
So my tablet's model is Bluewave 8 HD + (Rockchip 33GT or something like that) and I decided to update my system through wireless update. So I downloaded it, and clicked update now. By that time I had 35% of battery left.
However, it says that it was an error. I think there were "Installation aborted" and "Error 7" and that stuff. It was on fastboot/recovery mode.
Now, I obviously couldn't select other options apart from reboot system now since my tablet doesn't have volume buttons. The buttons are on the screen. So my option is to reboot and go to the same process again— system update (Android is loading something like an object or stuff), error, and reboot.
I watched a video where clicking the reset button with the power button will move the selection down, so that it won't be reboot system now but it doesn't work for me. Whenever I do that (and as well as holding power and reset button {it is the little hole on the back where I need to poke it inside with a bent paperclip}, it just turns the screen off like a hard reset.
I can't also connect to a computer. Although my computer detects it as an "Android Phone and the Android Boot blah blah", software's doesn't detect the device.
I can't remove battery either because the back is inseparable.
Any fix? I really need to get it running well ASAP.
Thanks!
Ps: My tablet is Rooted.
halseynth said:
So my tablet's model is Bluewave 8 HD + (Rockchip 33GT or something like that) and I decided to update my system through wireless update. So I downloaded it, and clicked update now. By that time I had 35% of battery left.
However, it says that it was an error. I think there were "Installation aborted" and "Error 7" and that stuff. It was on fastboot/recovery mode.
Now, I obviously couldn't select other options apart from reboot system now since my tablet doesn't have volume buttons. The buttons are on the screen. So my option is to reboot and go to the same process againâ?? system update (Android is loading something like an object or stuff), error, and reboot.
I watched a video where clicking the reset button with the power button will move the selection down, so that it won't be reboot system now but it doesn't work for me. Whenever I do that (and as well as holding power and reset button {it is the little hole on the back where I need to poke it inside with a bent paperclip}, it just turns the screen off like a hard reset.
I can't also connect to a computer. Although my computer detects it as an "Android Phone and the Android Boot blah blah", software's doesn't detect the device.
I can't remove battery either because the back is inseparable.
Any fix? I really need to get it running well ASAP.
Thanks!
Ps: My tablet is Rooted.
Click to expand...
Click to collapse
Hey how did you enter recovery mode can you please tell me and are there custom recoveries available?
PS: you can scroll through the recovery mode by pressing the little button in the tiniest hole in your tablet so use a paper clip or something.
This is the Fusion5 in question
https://www.amazon.co.uk/gp/product/B01CCYEIW2/ref=oh_aui_detailpage_o05_s01?ie=UTF8&psc=1
I tried rooting the tablet using kingoroot - both the Android app & the PC program..All 'failed' - but tablet was still running ok, so I'm guessing it's not possible to root it with these programs
Anyway, I accidentally left the battery to drain out, causing it to turn off - so started recharging it.
Once I thought it had enough charge I tried turned on the tablet, saw the White 'Fusion5' title screen followed by the black 'android' text screen... but now it's stuck on the android screen
So I've tried:-
> Turning off/on by power switch - same thing (White Fusion5/Black android screens)
> Press the small 'reset' hole on the back - same thing
> Tired different combo's of Power button/ vol +/vol - buttons - same thing
Have I bricked it ??
Is there a way to get the thing to boot up into recovery.. if so what's the button combo's ? or is there some other way using PC
IS there a recovery mode for this tablet or did kingoroot wipe it/corrupt it somehow ??
Any help greatly appreciated
EDIT: btw further searching seems to show theres a 'kingroot' and a 'kingoroot'
- but 'kingroot' website [https://kingroot.net] doesn't exist but a google search shows kingroot [https://king-root.net/] however the download is being picked up by Virus checker as malware
Has it booted far enough to retrieve a logcat?
If ADB is responding, adb reboot recovery is another hope.
qeexo said:
Has it booted far enough to retrieve a logcat?
If ADB is responding, adb reboot recovery is another hope.
Click to expand...
Click to collapse
Thanks for the quick reply however the main reason I went 'kingoroot' was for simplicity since I don't know anything about ADB
(I know of it, just not how to use it)
Anyway,tried following one of the many guides (this one in fact)
but when I do 'adb devices' it's not showing anything, although it's possible something is conflicting because even though my Samsung phone shows up when I plug it in, doing 'adb devices' shows nothing - I would've expected the Samsung to show up at least
I'll have more time during weekend to try & figure out why phone not showing in ADB & experiment with ADB a bit more