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.
Related
Hello,
I tried searching but the results all seemed like they were people who have rooted and have alternate ROM's.
I am completely stock with 3588, no clockwork, not rooted, nothing else.
A couple of days ago I turned it on and it went through it's normal routine until it got the point that it should have loaded the home screen. Instead it flashed something for a brief moment and the only thing I caught was 'Android System' in the top left, then it shut down. Prior to this I wasn't having any issues.
Now when I turn it on it shows the birds, then gtablet, then the tap'n'tap and peacock but instead of of then loading home screen it goes black for a moment then the tap'n'tap comes up again. It will do this 4 or 5 times then simply goes black.
I connect the USB to my PC but of course I can't access the tablet.
I opened it up and tried using the reset button, no help.
Disconnected the battery for a minute, no help.
So no clockwork or nvflash, can't copy files to it. Am I boned? Any suggestions on what I might try?
Thanks for any suggestions,
Neudle
Try a data wipe using Method I from this: http://forum.xda-developers.com/showthread.php?t=1030915
It will delete any apps you've downloaded and installed but it just might get you going again.
Up and running.
First off thank you very much for that help. The tablet is working again.
I didn't realize it would run a recovery from sdcard2 without the command file pointing to it specifically. I thought it only defaulted to the internal sdcard.
Does anyone have any idea how or why this might have happened and any advice on how I might avoid it in the future?
Thank you again,
Neudle
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?
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.
I was rooted using ViperMod. I took the JB OTA, thinking rootkeeper would work. Wound up with the partial root issue (some apps worked, i.e. Anti, Network Spoofer, Root Explorer, but root checker and the Linux Installer for Backtrack gave no root errors), so I tried the method here: http://forum.xda-developers.com/showthread.php?t=1911261
I got through step 3. Step 4 gave me a permission denied error, so I used Root Explorer to turn on all permissions for /data/local/tmp. At that point, adb push claimed to have worked through step 6, but I noticed my Prime had frozen. Before I went any further, I decided to hard reboot (hold down power button), to be sure everything was running proper before I started in with shell commands.
Upon reboot, it now sticks at the initial splash screen. I can vol-down & get to the bootloader there, giving me the 4 standard options. Recovery gives me the dead-looking Andy with exclamation mark (I assume because I don't have a backup image, which yes, I know, was stupid not to have. Hindsight.). The OS option says it's starting from a cold boot, but freezes there and does nothing else. I can access fastboot, and at least the reboot command seems to work, but I haven't tried anything else, as I'm not familiar with fastboot, and have no idea where to go from there. I'm hoping against hope I don't have to use the wipe action, as I have a lot of time and data invested in the thing.
I'm also able to vol-up and have APX recognized on my Win7 machine, but I admittedly have no idea what to do with that.
If anyone could help me here, especially if it would include NOT wiping my Prime, I would be forever grateful. Thank you in advance for any advice.
Please, I'm begging the community for help. I have no idea where to go from here. From my view, I don't know what went wrong. I simply changed permissions for one folder and pushed three files.
I don't have anyone else to help with this. This community has always been amazing when someone needed help, and I'm asking, as a man who seems to have screwed himself, for that help for me.
Again, I offer thanks in advance for any advice.
Hi, everyone.
I'll keep the introduction short: I'm a computer science student that's fairly far from home in the middle of all of these particular recent events. I've been cooped up at home for the past eight days, and I recently decided that I was unhappy with the maximum volume of my phone (OnePlus 7 Pro), so I went ahead and updated Magisk and installed Viper4Android. It instructed me to reboot my phone, and so I did. I make a backup here.
I then noticed that I could no longer boot into my phone. That's okay, I have recovery mode and a backup. I tried to reboot from the backup, and then rebooted.
Now, I'm stuck in Fastboot. The Start button returns me to Fastboot. The Recovery button, too, returns me to Fastboot. ADB refuses to recognize my device's existence, and I feel so ultimately boned, because recovery mode and ADB constitute for ninety-nine percent of the online advice for what to do when you've ****ed up your phone. I've spent the past few hours looking though guides for an alternative that doesn't use these two methods, and have failed repeatedly.
I'm sure my old files and photos are nice, but honestly, I don't care about those. I just need to get my phone working again (even if as a factory reset) before my folks start to worry. Please help me.
TL;DR: Start/Recovery buttons in Fastboot return me to Fastboot. ADB refuses to recognize device. Will do whatever needed to get phone back into working shape.
Okay, couldn't find a non-destructive solution. Flashed w/ a new copy of Oxygen.
To whoever finds this thread in the future, I wish you best of luck. <3