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.
Related
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 rooted mah Prime (TY Viperboy and contributing dev's!) and finally installed Font Changer. After I selected the font I wanted, obviously I re-booted....and re-booted..and etc. My TFP won't get past the ASUS boot animation, the circle just keeps spinning and spinning. I tried wiping user data and still nothing. Does anyone have a similar experience or advice? I didn't change the density or anything else, just the font.
I also tried the reset button a few times just in case and still the same thing. Android Commander doesn't see it when I connect either, Windows tried to install drivers for it(which i've obviously already installed) and kept getting an error.
98 views...am I the only one who has used Font Changer on the TFP? Do any of you vets on here have an idea how I might be able to boot the device or at least completely revert it to all factory settings/apps? I apologize for having a one sided conversation, but I really would like to use mah Prime again. Thanks!
Sent from my SPH-M900 using XDA App
I use Font Changer and haven't had a problem yet.
Hmm...Well I opted to re-boot from Font Changer after I changed fonts. Did you do the same?
pappasquirrel said:
Hmm...Well I opted to re-boot from Font Changer after I changed fonts. Did you do the same?
Click to expand...
Click to collapse
Yes. I don't know what to tell you.
Anyone know if there is a file I could put on my sd card that the TFP would boot from, like how PG86IMG works w fastboot?
not sure, but i would suggest you to get the newest update from their site, then pop it on a micro sd, (or sd if you have the dock) and try holding power and vol up .... or maybe power vol down, dont remember..
now when you download the zip from asus site, make sure to unextract and copy the zip after you unextract. It's a zip in a zip.
Then try with the zip as its labeled, maybe it'll work or rename to update.zip.... that seems to be the norm on other devices.
good luck, i hope it works so we can have another solution for those that this happens to. Can't wait for unlocker tool, so we can get a recovery on this and if that ever happens we can just do a restore. good luck!
Good idea, thanks! I will give that a go and report back soon. I know I had this problem once or twice on my EVO3D and Moment, I would have to do something similar and try again. I'm hoping for good news to report
keep us updated, I am sort of in the same boat. Mine wont boot up after last firnware update and I have been searching to see if I can make it read the update file from SD
btw, try volume up with power, then hit volume down.... maybe it'll just do a recovery with the image it already has
damn i dont know if its volume up or down.... anyone ever tried this? i dont have my tab with me...to test
Its vol dwn+power for recovery. it will ask to press vol up within 5 sec to enter RCK, I've done that and "andy" just lays there on his back w an exclamation mark coming out of his chest.
If you wait, you get a screen with 10 seconds to select one of two options, User Data Wipe and linex cold boot. I've tried both with no avail. One more thing I found out is since my Prime just stays at the loading screen, everytime I hold power or reset button it would just reboot and hang there again. Aside from letting the battery die the only option I've found to shut down is hold vol up+power till it vibrates, keep em dwn for 2 more seconds and it will shut down.
Sent from my SPH-M900 using XDA App
Font Changer, now TFP won't boot.
My Asus Prime is in the same situation as yours. A rooted it and install Font Changer, after reboot my TFP won't get past the ASUS boot animation. I tryed all the things you do, but Android doesen´t start.
I install APX driver in Windows 7, and when i connect the USB cable, the device is reconized in Windows Device Manager, but a can not acess the tablet.
I don´t know a method the acess the Tablet from microSD, do you know ?
May be BOOTLOADER UNLOCK release from ASUS solve it.
Good luck for us.
Still nada. Windows will reconize that its plugged in, but I get a code 43 or code 10 and can't access the TFP in anyway (that I know of). I asked the same question over on Transformerforums.com and member leeshor has been really helpful. Most of the idea's I was given I had already tried or I could not get to work for my specific problem, but I'm sure that the info will be helpful for a lot of you guys. Here's a link to my thread, check leeshor's sig for some helpful tips. http://www.transformerforums.com/forum/transformer-prime-help/15428-font-changer-now-wont-boot.html
I'm still workin' on it and I'll post if I am able to make any progress, good luck!
Data wipe will definitely not work in this situation as it does nothing to the /System which is where the font's are stored. My best guess is that the font was changed but the permission was not correctly written, had this problem in the early days of my Desire HD.
The only solution that will work, is if you can get into an ADB shell and either put the original fonts back or change the permissions to the correct permissions.
Doktaphex said:
Data wipe will definitely not work in this situation as it does nothing to the /System which is where the font's are stored. My best guess is that the font was changed but the permission was not correctly written, had this problem in the early days of my Desire HD.
The only solution that will work, is if you can get into an ADB shell and either put the original fonts back or change the permissions to the correct permissions.
Click to expand...
Click to collapse
That's what I figured, I just can't get windows to recognize it. When I connect via USB and the device is off, windows sees it as an unknown device(obviously) and that the drivers are fine. After I power it up, windows will either recognize it as an MTP device and when I try to access the tab or re-install the drivers I get a code 10. Or it will still show up as an unknown device with an "!" giving me a code 43. Is there any other way I can gain root access?
It's been awhile (or seems so) and I still haven't had any success. Has anyone else made progress getting back to a usable device??
Ok, so before I send my prime in...do any of you smarty pants know (guess is fine) if this lil problem some of us are having will have a solution when ASUS unlocks the bootloader? Unless there is some kind of boot.zip err something that will load up from stock recovery, I don't think it will change anything. Thoughts? Advice? Bueller?? Thank you in advance
Sent from my SPH-M900 using XDA App
Unlock-bootloader.apk....I guess that answers my question to whether i'd be able to fix permissions from recovery :/ What am I not seeing? There has to be a way to get these Primes w no adb access and a stuck boot screen to fire up...?
Sent from my SPH-M900 using XDA App
Have you tried the blob file from SDcard trick. I believe you rename the update to EP201_SDUPDATE.zip and it should be able to run from the RCK. It has to be on a micro sdcard though otherwise it doesn't work apparently.
As outlined here:
http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119
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.
So I just soft-bricked my Kindle Fire HDX 7. It does not boot any more but I still have ADB access.
I just tried to follow the steps as described here: http://forum.xda-developers.com/showpost.php?p=60307966&postcount=187
I successfully updated to 3.2.5 and now was about to downgrade to 3.1.0 when I used the .bat from this thread to apply the downgrade: http://forum.xda-developers.com/showpost.php?p=53382929&postcount=1
Even though I tried it several times, I could not downgrade because it said the requested version is lower than the one currently installed.
So le stupid me went on and found out which files the bat was generating/pushing on my HDX, and then manually replaced the /system/build.prop with the one generated by the batch.
I'm not doing this for the first time, so I made a backup of the old build.prop naming it build.prop.backup [afaik].
I then shut down the kindle (to go for a reboot) but apparently it doesn't work and the screen stays black.
Still, it seems like a pretty stupid move afterwards because otherwise it wouldn't cause a brick, right^^ Anyways, I unfortunately have no recovery installed atm.
I rooted the 3.2.5 with towelroot before btw...
However, if I try to copy/replace the build.prop backup it just can't find that file. I tried rebooting/pressing the power button but it doesn't help either.
Can anyone please help me to repair it -.-?
Edit: Turns out that I was accessing my blueStacks emulator with adb, which, even though it wasn't running at the time, caused the commands to not work.
The bluestacks service in windows was responsible for it. Charging the kindle atm and hope to be able to get adb :S
FINAL EDIT: So I messaged amazon Support, told them that it was bricked during an update and got a new kindle without any problems. Didn't mention the downgrade obviously^^
I followed this tutorial and was able to upgrade, downgrade, install TWRP and unlock my bootloader successfully: http://forum.xda-developers.com/showpost.php?p=60186871&postcount=82
For everyone: Just keep in mind that if you are running BlueStacks on your computer you will need to stop all bluestack services in order to make the tools work properly and not end up with a bricked device!
Otherwise some adb commands will fail because it doesn't know which device to use.
Tersus said:
So I just soft-bricked my Kindle Fire HDX 7. It does not boot any more but I still have ADB access.
I just tried to follow the steps as described here: http://forum.xda-developers.com/showpost.php?p=60307966&postcount=187
I successfully updated to 3.2.5 and now was about to downgrade to 3.1.0 when I used the .bat from this thread to apply the downgrade: http://forum.xda-developers.com/showpost.php?p=53382929&postcount=1
Even though I tried it several times, I could not downgrade because it said the requested version is lower than the one currently installed.
So le stupid me went on and found out which files the bat was generating/pushing on my HDX, and then manually replaced the /system/build.prop with the one generated by the batch.
I'm not doing this for the first time, so I made a backup of the old build.prop naming it build.prop.backup [afaik].
I then shut down the kindle (to go for a reboot) but apparently it doesn't work and the screen stays black.
Still, it seems like a pretty stupid move afterwards because otherwise it wouldn't cause a brick, right^^ Anyways, I unfortunately have no recovery installed atm.
I rooted the 3.2.5 with towelroot before btw...
However, if I try to copy/replace the build.prop backup it just can't find that file. I tried rebooting/pressing the power button but it doesn't help either.
Can anyone please help me to repair it -.-?
Edit: I might bricked it completely, because I can not gain w permissions on /system *__*
Click to expand...
Click to collapse
** NEVER MESS WITH BUILD.PROP **
(unless you are an expert and have robust recovery options)
Well, you had the right idea as the modified build.prop never made it to your Kindle which is why you were getting the version mismatch message. It saw 13.1.x was lower than 13.2.5 and bailed. The modified build.prop tricks your Kindle into thinking it is at 13.0.0 so processes the 13.1.x .bin as an upgrade.
None of that really matters as I'm guessing permissions are messed on one or more files that were copied to your device. Options are few if you can not gain write access (obviously bootloader remains locked). You can try a system restore from stock recovery (if working) which can be accessed by pressing the power and volume-up buttons simultaneously from a cold start. I don't hold out much hope that will fix your problem. Fastboot cables are ineffective.
There are several unbrick threads you may want to explore. I have no direct experience with a device in that condition so can't offer much guidance. Perhaps someone will jump in with a better answer ...
I just noticed that if I press power for about 20 secs I get the first boot screen.
But it never reaches the one with the golden kf logo...
I can get to the stock recovery, but a factory reset doesn't change it either.
Any way to get into fastboot from ADB?
Tersus said:
I just noticed that if I press power for about 20 secs I get the first boot screen.
But it never reaches the one with the golden kf logo...
I can get to the stock recovery, but a factory reset doesn't change it either.
Any way to get into fastboot from ADB?
Click to expand...
Click to collapse
After you shutdown your kindle, you can get into fastboot mode by holding "volume -" button while pressing shortly power button (2-3 sec) ... Unfortunately that will not help you, because fastboot mode on HDX tablets is only usable with unlocked bootloader...
I am watching several unbrick threads here over time, some people claims they do not need root for restoring system, some failed because of no root, hard to tell, what will work in your case, but from what you are describing, seems to me, that you are very close to permanent brick, sorry...
But I strongly suggest you, that you at least try this unbrick method or this one, maybe luck will be on your side...
if you somehow lost root access, try this: http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
Turns out that it was accessing my blueStacks emulator with adb, which, even though it wasn't running at the time, caused the commands to not work.
The bluestacks service in windows was responsible for it. Charging the kindle atm and hope to be able to get adb :S
I will try to get root and restore the build.prop backup, fix permissions and it should reboot... still need adb for it-.-
So I messaged amazon Support, told them that it was bricked during an update and got a new kindle without any problems. Didn't mention the downgrade obviously^^
I followed this tutorial and was able to upgrade, downgrade, install TWRP and unlock my bootloader successfully: http://forum.xda-developers.com/showpost.php?p=60186871&postcount=82
Big thanks to anyone who helped me! You can close this thread...