My kindle fire is rooted and TWRP installed.
All has been fine since this was done, almost a month ago.
Suddenly, the fire keeps rebooting. Further, everytime it reboots, it gets stuck at the yellow triangle with the orange colored button.
I then have to turn it off and on and during the green button phase:
fastboot oem idme bootmode 4000
and then
fastboot reboot
Work fine. The fire reboots and goes to the "Kindle Fire" logo.
But immediately when the lock screen appears, the fire powers down again. To add insult to injury, it always reboots and gets stuck at the triangle.
I can only connect to the fire during the very limitted time it comes up from a hard power down and the light is green. About 10 seconds. Enough time for the fastboot commands above, but little else.
I cannot enter TWRP recovery mode, either. If I push the green button and it turns to orange, trying to go into recovery, it just hangs with the yellow triangle.
I don't think TWRP is responsible for the reboots, however. Nothing has changed with it since I installed it a few weeks ago. I never managed to get it into recovery mode, but I let it be for a while since it was booting into the system. (I was waiting for CM9 to be ready before I tackled it)
This may have been a mistake as now I have no way to interface with the device, but that's the situation.
The only thing I changed recently was intsall Titanium Backup, but I can't imagine how that would case the reboot problem? I did set it to auto backup, could that be it? (not that I can do anything about it if it was)
I also saw around that some people were having problems with constant reboots in Dec. due to WiFi issues, but supposedly update 6.2.1, which I have, fixed the issue.
Anyway, I'm quite ready to chuck stock for CM7 if that will fix it, but I don't know how to get there from here. Any help would be appreciated.
Oh, and I should mention that I am running linux, not windows, so utilities for windows won't help. Has to be a manual solution.
Tom
sound like a battery issue - tried to charge with the wall-charger for an hour or so to get it stable ?
if it will help you there is also a kfu for mac/linux:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
b63 said:
sound like a battery issue - tried to charge with the wall-charger for an hour or so to get it stable ?
Click to expand...
Click to collapse
I thought of that! I did leave it plugged in overnight, last night, but I am not wholly sure the KF will recharge when not turned on.
if it will help you there is also a kfu for mac/linux:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
Click to expand...
Click to collapse
I can't believe I missed that! Thanks so much. Maybe it will help, I'll let you know.
Tom
I cannot explain this, but I reinstalled TWRP with the utility and now all is well.
The battery is, in fact, fully charged, so that wasn't the issue.
Seems to have been connected to my boched instillation of TWRP, thought I can't imagine how or why it would take almost a month ot manifest itself.
Strange, but I'm glad it's working. Thanks for pointing out the KFU for linux!
Tom
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Ha! I believe I figured it out.
Amazon pushed out 6.2.2 and that broke root again. Working on the fix...
Damn, I thought I had it set up not to update.
Will fix OP with solved, thanks.
Related
Following the video walk thoughs of rooting and installed TWRP.
I got the KF rooted successfully without issue, but the issue came when I went to install TWRP.
I got to the point where I ran the run.bat and then chose option 5 to install recovery. It download the recovery, and pushed it to the device. I watched it restart which it hung on the yellow triangle.
At this point the tutorial said to reinstall the drivers by running the .bat provided - that worked and it continued. I tapped "Reboot" on the KF. The script continued a bit further and the device rebooted and now it's stuck on the yellow triangle AGAIN. ADB refuses to respond and the drivers seem installed properly. I closed out the command prompt from the script because it was just hanging there.
Edit:
Device Manager shows Android Debug Bridge with an exclamation on it, claiming "This device cannot start".
Any idea what I should do at this juncture?
Thanks!
Ok, think I fixed it.
I found this trick:
"If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution "
Now, it booted back up.
At this stage, is TWRP installed??? I don't want this happen again LOL.
Had a similar problem as you, my drivers messed up going into fastboot on the Kindle Fire Utility and it hanged on boot.
If your fire displays the triangle on bootup that means Kindle Fire Utility has replaced the bootloader, which it does anyway before installing TWRP, so my guess is you're fine...
I'd wait for someone more experienced to answer as well though just to make sure.
Mwa exp. is definite not. So for mental ease I use only cmd prompt to do just the essential [ie.] adb device+ rtn key, and the like. God forbid I hit something that means solder a cable pin for connectivity after removing case rear enclosure on chasis, locate the ;X' chips, AND use extreme caution at this point. ...Still works don't fix it. Use alternate route.
I got it fixed as I stated above guys. Currently running ice cream sandwich!!
I rooted my Kindle Fire and installed CM9 on it using TWRP 2.0. I updated CM9 to CM9 Alpha but realized that I liked CM9 better. I then tried to flash MIUI 4.0.3 to my Kindle to see how that would work and got it to work but didn't like that either. I booted back into TWRP and then attempted to restore. Once I my restored it I hit the reboot system button and my Kindle got stuck on the yellow triangle. I unplugged and plugged it and attempted most if not all the suggestions by various threads. The problem is that every time I plug my Kindle into my computer while it is off it displays the yellow triangle and is only recognized for 10 seconds. After it disappears it reappears for 5 more seconds and then completely disappears. I attempted to use KFU to reboot it in normal 4000 by having KFU open plugging in my Kindle and quickly hitting the reboot in normal 4000 mode. KFU said that it told the Kindle to reboot in normal mode but when it started up again it stayed on the yellow triangle. I am really frantic as I love and use this tablet every day! Any help is appreciated!
bricked?
it seems like i keep finding people with the same problem as me that noone wants to help ;; this is madness
When you were connected to KFU and attempted to put it in normal bootmode did you attempt a hard reset when it said "Waiting for device...."? Sometimes the KF hangs and needs a 20 second hard reset
Try this using Ubuntu linux booted from a stick. Worked for me when nothing else would.
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
b63 said:
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
Click to expand...
Click to collapse
This worked for me after hours working on it last night. Follow all those steps as they make the most sense and actually work compared to all the other threads I've read
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
After having problems with my amazon app, and all my google apps, I figured it was a good time to try and learn how to put a new rom in. So I picked CM9 and tried to no avail. I was getting the same problem as alot of guys on here where it said something about /media. But unlike the others, mine wouldn't load like the others. I also was unable to go back to CM7. I was stuck in TWRP. So I tried my back-up and still nothing. Then thinking maybe I had a bad download I tried another CM9 and nothing. Then I tried MUIU. All three said failure to install. Then after trying the MUIU, my computer quit recognizing my KF and it stopped loading into TWRP and just went straight into yellow triangle. I followed the other threads and added the line under the 1949 in .bit file. I reinstalled the drivers in my newly downloaded KFU. Then tried the adb and nothing works because my computer won't recognize the KFU.
Had the same problem as the op. This solution also worked for me.
Sent from my Transformer TF101 using Tapatalk
[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!
KF won't start, charge, or connect to PC
Absurd1 said:
[FYI: I don't a thing about tech stuff, but I can follow directions well enough if they're spelled out for me.]
I rooted my KF the day I got it using KF Utility. I don't remember what I did, and I certainly didn't understand much of it; I just followed the steps. That was several months ago (in December), and I haven't messed around with anything since. Everything worked fine, no problems. Haven't made any significant changes in months.
Then today, I tried to turn it on; the power light went on and the words "kindle fire" flashed for a second -- and then both disappeared. I connected it to a charger, and the same thing happened -- both, even the power light, disappeared after a second.
Same thing happens when I tried to connect it to my computer -- and my computer won't even recognize that it's there.
[It's now been connected to a wall charge for several hours, but the power light's not even glowing.]
What do I do? Is it "bricked"? And if so, how do I "unbrick" it, especially if my computer can't even recognize it?
Thank you in advance!
Click to expand...
Click to collapse
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex
JohninLex said:
If you have the FIREFIREFIRE logo I hope this will help.
1. Make sure you still have the driver installed for you KF from KindleFireUtitly.
2. Open command prompt
3. change directory
cd C:\KindleADB
4. Check and see if adb services are running
adb devices
It will not come back with any device running and that is ok.
5. Look in the KINDLEFIREUTITLY folder for a bat file named Run.bat
double click and hit run and it will open a red command prompt.
After it has ran just a few short seconds it will give you a few number prompts. Chose number 5. and reboot Kindle and it will reinstall TWRP for you. These steps will also help if you ever get stuck in FIREFIREFIRE logo again.
I really hope this helps.
Thanks,
JohninLex
Click to expand...
Click to collapse
Well, like I said, I don't know much about any of this stuff, but here's what I can tell you:
I don't have FIREFIREFIRE. Not really sure what that is, but it's certainly never been on my Kindle.
What I did try doing was following those steps in Kindle Fire Utility anyway. I can get it to the point where it says:
ADB Status: Online
ADB Rooted: No
Boot Status Unknown
If from there I hit 5 (to "install latets TWRP recovery"), I get a whole bunch of
"The system cannot find the path specified." for each step it goes through, until finally it gets here:
"If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait..."
To reiterate again -- I don't know what any of this ADB stuff is, where to find it, etc.
We are in the same boat. Was messing around w/ someone's Bare Bones CM7, and as per instructions, clicked wipe SYSTEM, and since then my device has been with screen "on" but black; non response to power button weather plugged on AC adapter or USB. Will have to research the forums tomorrow (cant find search function now) and let you know if I find a fix and please do the same if you find something first.
Sincerely,
-RM
---------- Post added at 08:49 AM ---------- Previous post was at 08:37 AM ----------
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.
theartofbone said:
Actually --- I've just resolved the issue.
I had it plugged into the computer (still unresponsive), held down the power button for about 25 seconds, heard the computer do the "tuh-rup" sound, prayed, could finally stop seeing the "black screen" while on, it was pure black due to it powering off. After it was off, I powered back up and was able to get back into TWRP. Restored, did not wipe system and presto... hopefully you can get yours fixed.
Click to expand...
Click to collapse
Nope, that's not doing anything for me. My kindle won't power on. All it does is display "Kindle Fire" for one second, then go dead.
Does anyone have ANY advice?
oundsde good
Try a different charger and plug into the wall for a little while.
_Justin said:
Try a different charger and plug into the wall for a little while.
Click to expand...
Click to collapse
Tried that. No luck.
Do you have a chat program, or google talk? I'll help you out.
_Justin said:
Do you have a chat program, or google talk? I'll help you out.
Click to expand...
Click to collapse
..........
My device has the same issue, it powers down as soon as I connect it to a PC or charger. The interesting thing, that it is charging, but the led is dark. When I take it off the charger the next day, it boots up and fully charged. (when I connect a cable again it shuts down immediately)
If you find out something I would be also interester. (I've also rooted before 6.2, than I've lost root, than after I while I've faced these issues)
Alright, unless any folks have any other advice, I'm gonna go ahead and contact Amazon for a return.
try to charge it with the wall charger for some hours - check the charger - should have ~1.8A - maybe the orange light is showing up after half an hour
try to power it off by holding pwr ~20sec to allow better charging - if you can't let it on the charger - try to power it off later (eg after an hour)
look here about charger spec and contact problems:
http://forum.xda-developers.com/showthread.php?p=23035482#post23035482
some had success with a factory cable:
http://forum.xda-developers.com/showthread.php?p=23034046#post23034046
installed MIUI on my KF using TWRP a few days back. went well, played around with it, then decided to go back to stock.
Wiped caches and flashed update.zip (stock rom for KF) and all appeared to have gone well..... BUT..... the battery was/is apparently too low for the device to charge (but wait, it gets better)...
when the device fires up I get the white/orange kf logo animation, then when boots I see the homescreen (without the notification/toolbar at top (just bookshelves,standard icons and bottom row of icons).... as soon as that appears I get forceclose messages for
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but the device (after just a couple of seconds) just goes back to the white/orange logo animation and starts the boot process all over... whether I click force close or not it just restarts the nasty process).
in the brief time Im able to have it on I cant get the kindle fire utility to recognize it so I can get TWRP back on the device to try to re-flash stock.
probably just a paper weight now Im guessing, so I'll either take over my wifes KF or get a new one, but thought I'd mention my experience here to see if anyone has seen/heard of this before and as a warning to other noobs who know just enough to be dangerous like me!
Thanks all.
Have you tried charging it? Just plug it in with the stock charger and let it sit overnight. Then try the re-flash.
Let it charge, then just flash a new rom.
left plugged in with AC charger all night... the force closes just happen over and over and because it doesnt fully boot (Im guessing) I cant get to point where I can use kf utility to get twrp back on to handle boot. i think trying to flash with such a low battery made the flash go horribly wrong and thats the cause of the force closes??? I wish it had hardware buttons like my galaxy s!
Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP
The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.
vbdss said:
Your device is not bricked alright?
Now that the device is fully charged, just go to KFU, on the option 1 (bootmode), choose recovery (5001).
Then turn off the device completely holding the power button for 15 secs or more.
Then plug it to USB and let the KFU set your device to recovery.
Then it will restart and go directly to TWRP
Click to expand...
Click to collapse
Thanks... KFU doesnt recognize the device at all during the 'boot loop-like' process it runs through before the 2 force closes and the eventual automatic reboot..... I followed your steps and it just kept showing waiting for device and the KF goes through the boot > force close > restart process.... its like ground hog day.
Thanks though, I appreciate the response/help.
shobon said:
The fact that it boots at all goes to show you didn't brick it.
A few months ago I couldn't get passed the splash screen.
Click to expand...
Click to collapse
Yeah, I see your point... but the force closes and the fact that it never shows the menus / top notification bar and icons, etc. and that seemingly, the KF os never loads fully keeps me from getting to a point where the windows drivers recognize the device and then allows me to get KFU to work with the device.
sort of stuck but not technically a brick I guess.
There is no such thing like KF never loads fully.
Or it loads or not. FCs is something that happened on the install of the rom
You have TWRP and cant fastboot?
Try to redo the steps to install TWRP and install FFF 1.4a by hashcode
He doesn't have FFF or TWRP anymore, as he flashed Amazon's stock update.zip
Your only solutions are either the USB trick (cracking open the KF's case and shorting specific pins) or getting a factory cable (recommended) to force the KF into fastboot mode, from which you can flash FFF and TWRP, then boot into TWRP and fix the mess.
Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.
Thanks, Dasanko, I'll do a search for the cable and see where to buy it and will go that route. Thanks again all.
FastBoot
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)
vbdss said:
Sorry, after i went from stock to custom roms, i never tried to go back to stock, didnt know that we lost fff and twrp when doing it.
Click to expand...
Click to collapse
Np, it's just it doesn't flash just over the system, but also overwrites the recovery and bootloader with their crappy stock ones.
darkjz said:
Something similar happened to me and I did this:
Even though your Kindle Fire isn't recognized by KFU you can run it and select the option #5 (Install Latest FireFireFire).
When you do it'll probably error out attempting to get your device into fastboot but you'll get the prompt "( waiting for device )". Once that happens let your fire loop again and this time the window will be big enough for FireFireFire to be flashed into your device and leave the device in FastBoot...
After FireFireFire gets installed run KFU again to install TWRP and you'll be able to boot into recovery by poking the power button repeatedly in the new boot logo.
Hope that helps! (That's how I un-looped mine)
Click to expand...
Click to collapse
I like this approach and think it MIGHT yield some results (but what do I know- I caused this afterall!).... Im going to let it stay in its little reboot / force close loop and have KFU sitting at FFF (waiting for device).... then if it looks like this works (how will I know exactly? the boot process will change how exactly (what should I look for, basically)) then I will do same with KFU and TWRP installation option do its thing. Thanks.
Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app
freefaling said:
Something similar happened to me too. I was reverting my CM9 modded Kindle to a stock one. After flashing the 6.3.1 update, I was getting weird FCs whenever I would boot into the stock OS. I finally managed to get to the Factory reset option in the menu and that fixed the issue for me.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Encouraging!.... what exactly did you do to get it to work for you - if you recall... i've just had it spinning through the loop with KFU sitting at waiting for device -- no results though... so seems pointless for me so far.
Little bit of info as to why/what is causing the issues discussed here:
The stock bin backs up data during the restore process and than restores it back along with the ROM (those of you familiar will already see the issue here but I'll continue); problem of course being there that if you restore data from a ROM like CM9 to the gingerbread based/neutered stock OS (or even to CM7 for that matter), it is going to cause all sorts of headaches with force closes and stuff just plain not working.
In short, for those considering trying to return to stock please remember to wipe data before attempting to flash the bin (at least until someone decides there's enough of a demand to make a cleaner return to stock method).
As for the OP, do what was suggested with the factory cable and you should be set; good luck.
Edit: the above posts regarding factory reset might work to as that will delete data but you would have to be able to get to that part of the settings menu, which depending on what's force closing may or may not be possible.
Your exactly right Sblood86 many are slipping on this bannana peel here lately trying to revert back to stock some with even more dire consequences not just a literal shock to it completely changing systems but also how data is rehandled. Could be a better option for some to do full wipes and flash something near stock like modaco to prevent this mishap.
This entire thread is ridiculous.
Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.
Dopius_Fishius said:
Hi all,
I thought I'd consult the brains trust to see if anyone thinks this is salvageable. Was using my A500 about 2 hours ago, suddenly the screen powered off. Thinking nothing of it, I held down the power button to restart it. When powering back on, nothing appears to happen except for the power button lighting up. No screen on, no vibe, nothing except the power light on.
Tried power cycling a few times to no avail. Tried the reset button. Tried the Vol+ Power and Rotation switch reset. Nothing.
Out of morbid curiousity, I plugged it into the PC and switched it on and I get an APX driver being installed. So, clearly something is happening here.
It has done this once before and came back to life of its own accord very shortly afterwards, this time it's been dead for quite some time.
Any suggestions? It's well out of warranty now, so I doubt Acer would be interested in it at all.
Click to expand...
Click to collapse
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD
Moscow Desire said:
In the Dev threads, or possibly Q&A, there is a thread called "stuck in APX mode". In there I believe are some steps to see if you can recover.
But, if you're in APX mode, you could probably try NVFlashing the bootloader and recovery the old fashioned way manually.
But look up that APX thread first. Will probably have the answer. I'll see if I can find it in a little while, if you don't find it first.
MD
Click to expand...
Click to collapse
Thanks MD. I looked up the threads you suggested, and after a lot of screwing around I have installed the APX drivers and used blackthund3r's APX Flash Util 0.3 (The link is broken to the current version) to attempt a recovery of my tab.
Its now sitting at an Acer screen, "Entering Acer Download Mode" while the flash util is sitting at:
Nvflash started
[resume mode]
It's been there for about 10 minutes now, no progress to report. Is it worth just sitting it out, or now that the damn tab shows SOME signs of life, can I just restart it and reset to factory?
And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...
Dopius_Fishius said:
And then most bizarre of all. I declared no progress, rebooted it. It went back to APX mode.
Re-ran the blackthund3r tool, it didnt do much so I bailed that. Restarted tab and attempted to load recovery (vol + and power) and it booted normally.
What the hell...
Click to expand...
Click to collapse
erm for now i would make sure you have all backups of data, cpud etc,.. just incase. you can just sit em on your computer i always try to keep a nandroid of all 3 of my devices each month or so.:good:
edit: and of course keep the link for the thread MD recommended.
Gee. Sounds exactly like mine....
The only thing I haven't tried is an update .zip, but I don't hold out much hope.
Considering parting out at this point....
Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.
Dopius_Fishius said:
Yeah, I dont have high hopes that it will last a whole lot longer. Up to this point it has been running Acer OTA updates only, no custom ROMs and no root.
I restarted the tab a little while ago and it went back into APX mode again and stayed there. Some more furious button mashing and attempted restore-mode boots, and it booted normally.
I made the point of wiping it this time using the Vol+ & Power & Rotation Lock trick and its been ok so far.
Click to expand...
Click to collapse
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD
Moscow Desire said:
I have a cousin in Jamaica. She might possibly help (chicken foot and some frogs blood...voodoo you know)
Here's What I think.
You got some corrupt data or a partially bad devblock. This might explain the strange behavior on boot.
Like the tab really doesn't know how to boot.
Personally I would do 1 of 2 things at this point. Either;
1. Root that thing, and try running Timmy Deans root back to 3.2. This should reset your partitions back to normal. Then work your way back to an ICS rooted, Bootloader, and custom rom.
2. Leave it alone, and don;t turn the tab off. Clearly some partitions are messed up at this point. The toggle of the lock usually wipes user data. But the core issue is still there.
If it were me, I would pull out the nuclear missile and go for it all.
MD
Click to expand...
Click to collapse
Tried the update.zip - nada
Tried timmiedean yesterday, went into Acer Download mode OK, failed....
If dolps is like mien, the first time he tries to go into recovery, it will crash again...
It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....
tennessee_titan said:
It's baaaack!
Tried blackthunder flash again, failed.
Went to turn off to get out of APX, and it booted!
Now boots, boots to recovery and boots to primary.
I have no explanation.
We will see.
I am suspicious....
Click to expand...
Click to collapse
I told you maaaannnn, go see me cousin in Jamaica maaaannnnn. She do some good things you see
Glad it's running again.
MD
First, is this a SOD?
I can kill it by booting into recovery and get it back by using Blackthunder flash tool to go into APX and letting it sit for 20 minutes or so. Close the program, unplug, reboot and it is back. I would like to use timmiedean (td) and go back to square 1, but it fails at the image detect ( displays ICS 4.0.3 Civato as the current image, a red X for the new image). Has td been proven to work reverting from ICS? Will a boot recovery reflash and a new ROM flash solve this? Is there another way to get out of ICS back to HC?
Any suggestions/comments welcome!
EDIT: I flashed FLEXxx V4. Shut it off, problem still there....
Really frustrated. Trying to use the timmiedean tool, but it requires that the unit be shut off in the middle of the process, which kills it. Does anyone know the whereabouts of the blackthund3r revert tool, or the .apx package for his flash tool. I can't find it...
I'm done with this one. On Ebay for parts.... GONE!!!
Have an A100 now, rooted, unlocked,. on Relix
1 more A500 coming next week