Had my Prime 2 days, got it rooted.
After ICS install and camera update it worked for a while. Then it rebooted and it's stuck in a bootloop. I can't even power it off.
Yes, I've used the reset pinhole.
I've rebooted into Asus recovery but all I get is the "dead droid" screen. I'm assuming it's because I don't have my SD card in.
Any suggestions?
I'm thinking that if I can get my hands on the stock ICS zip direct from Asus I might be able to run that.
I suspect, from this thread that the issue might be that the Launcher has gotten corrupted.
Update:
Ran the battery till the unit shut off and didn't reboot.
Charged the battery for 4+ hours, unplugged it and tried to boot up. Same story, bootloop.
ADB sees my Prime and can issue commands.
Any suggestions? I'm getting desperate here.
Edit again: I can pull a logcat, any suggestions what I'm looking for? I'm not sure what subset of Linux commands are in Android, can I do a kill -9 if I identify a rogue process?
I'm pretty sure top won't work, and a lot of my Linux knowledge is pretty rusty.
Same here
I'm stuck in boot. I rooted it from zedo's instructions (that guy is a whoot!). Afterwards I installed "VM Heap Tool"(by martino), restarted the tab from the VM app and it got stuck in the boot screen.
I'm stuck and don't know what to do. I don't really know codes, so I'm pretty much up a creek without a paddle.
Any help would be MUCH appreciated!
Bumble-Bee has solved this issue for you on IRC but I figured we should post the solution to *your* specific problem here for others. Hopefully it helps them if they run into a simular issue.
With a boot loop try shutting down the tablet by holding power for 30 seconds. If it doesn't shut down then hold power for 30 seconds and after it vibrates hold power and volume down. This should get you into the recovery process.
The first thing to do in trying to resolve this issue (and what solved it for Col_kernel) was to do a data wipe using the recovery menu. Directions on how to perform this can be found here . this will solve the majority of bootloop issues.
The second thing to try to do is to perform a recovery using a signed zip from Asus. the ICS 9.4.2.11.1 is the latest one as of this thread and can be downloaded at the link provided there. Download that and place it on a microsd card. Load the card into your prime and boot into recovery and perform a recovery.
after that, start asking for help
I tried both solutions suggested and they didn't work for me, however I modified the services.jar in systems\framework. Looks like it tries to recover and then goes to an android on his back with an exclamation mark. I can't get adb to recognize my device either. I'm assuming my only options are to send it back to Asus or wait til I can flash at this point?
I should have said that I have already done the reset. Also, I cannot install anything on the tablet, since I cannot even access it. My PC won't even recognize it.
Update: I just spoke with Asus support. They said that if all these options are exhausted, I should return the tablet. That's what I'm going to do today. [good thing I have all my apps backed up. #TiBu!]
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
wells79 said:
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
Click to expand...
Click to collapse
Odd. I had the same issues. I started rooting mine on my mac, then finally moved to my pc. It rooted flawlessly on my pc.
So, I don't know if it was the root with a corrupted file, or the VM Heap Tool that I activated in it that caused it to get stuck in bootloop. But... I didn't restart the tablet until after the VM Heap Tool. In other words, it could have done the same thing without the VM Heap, I just wouldn't have known it, because I didn't restart it right after the root.
Make sense?
Related
Been having a lot of trouble flashing new roms. Curently running tazz froyo v1.0. Have been able to root, flash many different types of roms (2.1, froyo etc)
But lately been wanting to try out Nonsensikal v4.6 but for some reason cannot get it to load. It'll either get stuck onthe white screen or if it does make it past the boot freezes during the boot animation and will remain stuck for a long time. Have let it go for 30-40 minutes. Batt pull, both wipes reflash and same thing.
So it has to be corrupted downloads. Tried on different computers, same results. Reformatted my card (was already no partitions, fat32 for froyo).
I would like to figure this out as i really want to try nonsensikal ( ran v 3.4 and loved it)
Any ideas? Battery is always fully charged when flashing. Sd card is good.
Maybe it's a computer issue?
Appreciate any responses.
Thannks
Stephen,
Thanks for the input. No setcpu for me anymore. Its only phone but never activated. I can flash other roms. It's just certain ones won't finish booting.
I'll have to verify the md5s and focus on the corrupted download issue.
Thanks again.
ppbb = Jp50 ?
I would try wiping and flashing the ROM, and then booting it for the first time without your SD card being present. (Note this is not the same thing as attempting to boot a ROM without an SD card, where it has already been through several failed bootloops and battery pulls).
It is not possible to flash a corrupted ROM - unless the definition of "corrupted" is that the dev screwed the pooch.
If you reply back, let me know if you have ADB and the USB drivers working on your PC (and if you are familiar with using the command line).
bftb0
You did wipe. My mistake.
bftb0 said:
ppbb = Jp50 ?
I would try wiping and flashing the ROM, and then booting it for the first time without your SD card being present. (Note this is not the same thing as attempting to boot a ROM without an SD card, where it has already been through several failed bootloops and battery pulls).
It is not possible to flash a corrupted ROM - unless the definition of "corrupted" is that the dev screwed the pooch.
If you reply back, let me know if you have ADB and the USB drivers working on your PC (and if you are familiar with using the command line).
bftb0
Click to expand...
Click to collapse
yes that is me. I do have adb and usb drivers. I can get around and do some very basic stuff thru command prompt sdk. Would love to get this up and running.
Thank you so much. I look forward to hearing from you.
Jp50 said:
yes that is me. I do have adb and usb drivers. I can get around and do some very basic stuff thru command prompt sdk. Would love to get this up and running.
Thank you so much. I look forward to hearing from you.
Click to expand...
Click to collapse
Let me know if you have tried booting it without the SD card in the phone (the first time you try booting it). If you already said you did that and I missed it, then my apologies.
Some dev ROMs (not all of them) have "USB debugging" enabled in their boot scripts (some don't), so you can sometimes detect what the problem is using logcat. Maybe you do the "wipe-flash-boot without SD card" experiment and at the same time do this:
- Turn phone off
- Plug it in to the PC and bring up a command window
- in the PC, enter the command
Code:
adb wait-for-device logcat > logcat_boot.txt
The command prompt will not return - it will just sit there, waiting for the phone to start up. So, then:
- boot the phone.
Let the phone sit, even if you think it is going in to a boot loop. The "adb" command will also just sit there until you interrupt it. Wait for 10 minutes if necessary.
Hit Ctrl-C in the PC Command window. You should see the command prompt return.
If the phone booted successfully, then you can just delete the "logcat_boot.txt" file.
If the "logcat_boot.txt" file is zero length, that means that the dev did not enable the "adbd" service on bootup, so this particular technique is of no value.
If the phone went into a bootloop and you have a big "logcat_boot.txt" file, I will probably suggest you post it up to a pastebin somewhere (e.g. http://pastebin.com/ ) so we can look at it.
bftb0
ran the logcat test and it returned nothing. phone still won't boot nonsensikal. just freezes on the white screen. battery pull, reboot now its in boot loop city.
i think i've wasted enough time on this rom. I'm running cyanogen Tazz v2.0 and I was able to flash it over v 1.0 with no issues (other than the camera).
I guess nonsensikal rom doesn't like my phone. the dev was a lot of help, but i think the issue is my phone is just ****ed. I can't overclock anything over 604 without it freezing.
Time to move on and get back to having a real life and not obsessing over a phones interface. tazz's rom is more than good enough and I just have to move on. The amount of time I wasted on this is just silly. This phone took over my life and I have to lick my wounds and admit defeat.
thanks for all your help everyone. not all phones are created equal.
I installed CM7 Alpha Final (SD card version) and was working on getting the interface back to how I had it on the previous version. I used CWM to install "transparent status bar icons.zip" from this thread...
http://forum.xda-developers.com/showthread.php?t=1471066
Upon installation I went to reboot and now I'm stuck on the CyanogenMod7 boot screen and looping endlessly.
If anyone has any idea how I can fix this, I'd really appreciate some help.
Thanks!
Retcon:
I just remembered that I did NOT have this installed on the previous version on CM7. On CM7 i had a standard theme dock, so I think I installed something that just wasn't compatible with CM7 at all. What do I do now?
Thanks.
Most likely that transparent icons xip was not built for cm7 and rather was built for stock firmware. They are not compatible. Reinstall cm7.
What method can I use to reinstall? Since I'm in a bootloop I can't get to CWM. Or is there some kind of "safe mode" I can boot into?
Sent from my T-Mobile G2 using xda premium
Turn the unit on, when you get to the n screen, hold the power button until it turns off. Repeat 8 times and you will be forced into CWM.
If you have adb installed on your pc, plug it in, turn it on and check devices. If you are listed, do an adb shell reboot recovery and that will put you into recovery instantly.
I tried the 8-boot method two different ways...
1. Pressed the power button and released. When I saw the N screen, I pressed again and held until the unit powered down.
2. Pressed and HELD the button through it powering on and not releasing until it shut back down again.
Does it matter which of the above ways I do it? I wasn't able to get it to work. Does it have to be exactly 8 times? I don't think I stopped short but I might've done it more than 8...
Regarding the ADB method, I went ahead and installed the SDK but I'm not seeing my devices in ADB DEVICES. Since this is a new computer, I think I just don't have the right drivers installed. I went to Indirect's root thread to get those drivers but his dropbox link is disabled due to high traffic. Is there somewhere else I could get the appropriate driver? And once I have the correct driver and can see my device in ADB DEVICES (I'm assuming I'll be able to see it even though I'm bootlooping the whole time?), what is the code/line to get it into recovery?
Thanks for your help thus far. I really appreciate someone taking the time the time to help me out.
Oh, and a correction to my original post - I used the internal root method, not SD.
I found a working link for the drivers.
http://www.mediafire.com/?w6y5ld1jeuh65i1
I installed them and I can access my tablet now. I can see my device and its responding to commands.
So all I need now is the command to get into CWM. I tried "adb reboot [bootloader:recovery]" which I saw in the cmd window, but it just gave me a standard reboot.
Thanks!
EDIT: I tried "adb reboot recovery" and that did it. I'm back in business! Thanks for the help, Know-Fear. Although in my n00bishness, step-by-step handholding would've been nice, your replies gave me enough for me to at least know what general direction to look in. I still couldn't get the 8-boot method to work, but maybe that's just a dexterity issue. The adb method worked perfectly once I stumbled my way to the command line.
Make sure when you reinstall you do a partition wipe.
Glad you got it working thus far. Hopefully no more problems will arise after the new install.
HELP! (I used the Debugfs method: http://forum.xda-developers.com/showthread.php?t=1706588) And I do realise that this is the Prime forum, but as the original method was listed as for the Prime, I was hoping that the devs here may be able to help me here, or point me in the right direction.
I feel like an utter moron at this point, which I think is frustrating me as much or more than my inability to get my new 300T (running .30) rooted, especially as I've managed to root all my other devices with no problems! OK, I'm not terribly familiar with ADB (although I can C/P code to it and not kill things), so I chose this method to try to root. Got everything set on my 300T, downloaded/unzipped the zip, ran batch file. Selected option 1, and watched the code fly by, with lots of "adb out of date, killing". It reboots my 300T a few times, and I get to the end, and check for SU, no dice. I tried downloading it, then running Titanium Backup to test if the root had been done, no luck. AND, now I'm getting an android.process.media error. ARGH!
What am I doing wrong here? Help?
**Also, I just noticed that my computer is no longer recognizing my 300T- as in I pluc the 300T into my computer, and NOTHING happens. I've tried rebooting the computer and the tab, with no luck either way. As far as the computer is concerned (any of them, I've tried it on three computers, same result), there is nothing connected to it at all. I've also tried booting the tab into recovery (pwr + Vol down), and it gives me the dead android with the red triangle/exclamation mark. Somehow, I don't have root, but I've lost recovery.
Ok first of all Im sticking this question in general android Q&A because there in no XDA Forum for this phone. It is a Straight Talk LG Optimus Q 55c, this is my girlfriends phone its basically an optimus p500/v with a sliding keyboard Overclocked too 800mhz. I own a virgin optimus V so I have a lot of experience with this platform but Im stumped maybe im just neglecting to see something, Im hoping "another set of eyes" will help turn on a light and get my girlfriends phone working again as she cant afford another :/!
So here is what Im dealing with. I had rooted the phone for her and installed clockwork mod recovery & fastboot. Since she got the thing its had problems freezing (probably because it stock overclocked), and occasionally pulls a random reset. She asked me If I could install another ROM on it to see if it may help make the phone more stable. I went a searching and found that the Optimus Q community is very small almost nothing and her only real choice was a port of the Area51 Rom. So Installed the rom.... A few days later she had told me her phone was mega slow now and acting up way more, so I told her I would flash back to stock.
I rebooted the phone and found to my surprise CWM and fastboot seemed to be gone... what the h*ll? Im assuming when I flashed AreaRom it installed the stock Recovery and removed fastboot, I cant figure out any reason why the stock recovery would be back on the phone. Anyways I didnt feel like flashing a new recovery at the time. Well 3 days go by and her phone crashes and gets stuck in a boot loop. So she went in to recovery and wiped it. The phone then went through the process of collecting e-mail and password, asking about backing up, then asking whether or not to turn the location services on. Once you hit next Android throws an exception and says setupwizard.apk failed to initialize or something along those line. So after that the launcher does not load only the task bar at the top. When rebooted the phone enters a boot loop againg until wiped.
So heres the deal I can use adb, but when I try to get into an adb shell the prompt says error: closed. I have been able to use adb to push and pull files that is all. I tried to push setupwizard.apk to the system/apps directory but of coures it needs to be remounted to read write and I dont have any shell access to do that. So basically adb sees the phone but the shell doesnt work, when i type adb root it reports adbd is running as root on the phone, so I guess the shell service just never loads.... I do have stock recovery but the problem with that is there is no update.zip files it will except I have tried a myraid of methods to sign an update.zip but every time I try to run the update the stock recovery says verification failed. Of course LG has no official updates for this phone using there signature that I can use.
So basically my phone works recovery works android starts but cant finish setting up and never starts the adb shell service. If anyone knows how I can push setupwizard to /system/app, get adbd to initialize, or sign a 3rd party rom and have the stock recovery use it I would be very gratefull! Maybe there is a way to get fastboot back on there or enabled or something? adb reboot-fastboot just reboots like normal. I am at the point where I going to take the phone apart to find a serial uart connection and pray I can get a shell that way!!
Ive looked into a few programs like kdz update and lgmdp but they dont seem to work with this phone and I cant get into any emergency mode, maybe Im doing it wrong this is the first ive heard of emergeny mode.
Hello,
The other day I finally found a way to root my Quanta Verizon Ellipsis 8 tablet QTAQZ3 with KingRoot. It was working great for about 3-4 days. I was finally able to use apps like Apps2SD to install my games and large apps on the SD card, use chainfire3D and the like and some other useful apps that actually worked to shutdown processes I didn't want running in the background to clear up a good 300MB of extra ram. It was working great.
The day before yesterday however I was routinely using the tablet and it was in the middle of loading Fifa16. Suddenly the tablet shutitself down and rebooted all on its own. When it rebooted however it only brought up the Android Splash screen for a few seconds, after that it goes to a blank Back-Lit screen(so I know its still on) and just sits there. I have left it there for 6 hours+ hoping it would eventually miraculously boot but it just sits there until the power button is held down to shut it off.
Now since I get it to power up and show the android splash screen and also access the recovery mode by holding PowerButton+Volume down I am hoping/assuming it is only softbricked.
I have tried to putting a new Rom.zip on the SD card and accessing "Update from external storage" in recovery mode, but I keep getting Permission Denied. I have tried burning a Rom image to the sd card to try to boot from it but nothing happens. I have tried Factory Reset in the recovery mode and it does basically nothing other than delete my user data. Upon reboot the same problem persists.
ADB doesnt seem to be an option because I can only get windows to install a Generic MTP Device driver(it does show up as the model number of the device properly QTAQZ3 though) but thats all it will do. Doesnt show up in drive list to access anything, cant install adb driver because it doesnt detect the device. I have tried forcing adb driver install but it just tells me the proper driver is already installed.
I am hoping somebody might be able to help me solve the ADB driver issue so I can sideload a new rom/bootloader to the device or help me figure why it keeps saying Permission Denied when trying to update .zip from my sd card.
Please help, thanks you.
Dang
Where dod you get the rom updat.zip?
Sent from my SM-G920P using XDA-Developers mobile app
Bump
Sent from my SM-G920P using XDA-Developers mobile app
same happened to me with kingo root on the QTAQ73 model
Any new development on this? I have the same issue except mine stays on the boot animation until the power runs dead or I shut it off.
Update - I ended up taking the tablet to Verizon and luckily I still had a week left of my warranty. Sent it in Monday got one sent back Saturday running Android 5.1.1 and rooted it with KingRoot. Working on swapping King with SuperSu but that's how I got it stuck in bootloop last time so I'm a bit cautious.
I [email protected] Verizon
I also have this problem. ellipsis 8 QTAQZ3 won't boot past the Verizon screen. Repair center wouldn't do anything for me, even though it's a software issue, because I'm outside of warranty time. Verizon sucks.
All the intelligent people tinkering with droid tablets and no one has an answer on this? I've looked everywhere.
Hello guys, i realize this is an older thread but the other day i soft bricked my Quanta Ellipsis 8 QTAQZ3... Can someone help me out with a stock rom for reflashing? Willing to donate for your support! Thank you!
I have a QTAQZ3 currently running 4.2.2. I captured the OTA url and downloaded an update bin file. I'm not exactly sure how bins compare to flashable zips, nor do I know what to do with a bin file. I am hoping that by posting it, someone with the right know-how can help us fix all these bricked tablets.
https://drive.google.com/open?id=1LmyrA3eGcVL3sCMB3okBdsoqA0Gv5RZE
Hi all.
I'm wondering if anyone has a viable workaround for the pile of bloatware on the QTAQZ3, I was gifted on a few years ago and it is telling me that it is running out of room. The math for the misc junk file doesn't add up. Display counts 5.2 GB, and clicking the line often shows less than 3 MB.