So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
AndroidKills said:
So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
Click to expand...
Click to collapse
I would recommend to flash the stock image to get the phone running again and not use toolkits anymore.
Look here for how to flash a factory image: http://forum.xda-developers.com/showthread.php?t=2513701.
gee2012 said:
I would recommend to flash the stock image to get the phone running again and not use toolkits anymore.
Look here to flash a factory image: http://forum.xda-developers.com/showthread.php?t=2513701.
Click to expand...
Click to collapse
yeah i figured i should flash stock back, but the problem is trying to push the file or something. but ill look into that link asap!
thanks for the quick response
You'd probably do best to start from the top by reflashing the stock image... http://forum.xda-developers.com/showthread.php?t=2513701
This time don't use any toolkits or canned scripts, learn how to do each step by yourself, get familiar with all the commands, and do it yourself. You're less likely to screw anything up that way.
AndroidKills said:
So today i decided to change my stock recovery into TWRP. Somehow managed to come across a one-click twrp installer.
After i tried that, everything went downhill. Tried to wipe cache/ dalvik to try out faux kernel.
it just stood at formatting cache for a long time and didn't budge.
after 15 mins or so, i held on the power button and restarted my phone that way.
Now nothing seems to work, no service, google play crashing, and more importantly my storage isn't being detected so i can't even push files around.
Whats something i can do? im confused and stressed its 4am here
Click to expand...
Click to collapse
I had the exactly same situation before. What I did was a factory reset by using the wiping function in TWRP, Then you get a freshly-new system. Hopefully you have backed up your data.
Guys stop flashing the cache it really isn't needed and causes issues... I haven't done it since Android 4.3 and not had one problem
Sent from my Nexus 5 using Tapatalk
Related
Hi,
So I got a bootloop after wiping battery status on recovery. But first I wiped cache and dalvik cache (i dont know why i did this). Now, Im on a boot loop and I cant even turn the phone off. I take the battery out and plug it back in and it just loops. Same with taking the battery out and plugging a usb. SO I successfully got to Download mode and got ODIN to recognize the phone. I installed Clockwork
Mod Touch 5.8.1.3 Odin tar. and it says it was succesful, but no luck! Still loops. Is there another .TAR file I can install???
PS: I cant get into Recovery because phone does not turn off.
Please any input is much appreciated, this is driving me nuts.
Wiping battery stats, cache and Dalvik shouldn't cause a bootloop. Wiping Dalvik does cause a very long boot cycle, though, as it causes the system to think it's got all-new apps, and it has to re-process and re-cache them. Are you sure that's not what's going on? How long are you letting it sit for?
Also, are you sure you don't have a stuck power button? I doubt it because you were able to get into download mode and flash a recovery img, but have you tried mashing the button down over and over, even cleaning around the edges of the button with a needle?
mex2309 said:
Hi,
So I got a bootloop after wiping battery status on recovery. But first I wiped cache and dalvik cache (i dont know why i did this). Now, Im on a boot loop and I cant even turn the phone off. I take the battery out and plug it back in and it just loops. Same with taking the battery out and plugging a usb. SO I successfully got to Download mode and got ODIN to recognize the phone. I installed Clockwork
Mod Touch 5.8.1.3 Odin tar. and it says it was succesful, but no luck! Still loops. Is there another .TAR file I can install???
PS: I cant get into Recovery because phone does not turn off.
Please any input is much appreciated, this is driving me nuts.
Click to expand...
Click to collapse
U should definitely go back to stock via odin first before even trying to install cwm and flashing a custom rom.
Sent from my SGH-I727 using xda app-developers app
T.J. Bender said:
Wiping battery stats, cache and Dalvik shouldn't cause a bootloop. Wiping Dalvik does cause a very long boot cycle, though, as it causes the system to think it's got all-new apps, and it has to re-process and re-cache them. Are you sure that's not what's going on? How long are you letting it sit for?
Also, are you sure you don't have a stuck power button? I doubt it because you were able to get into download mode and flash a recovery img, but have you tried mashing the button down over and over, even cleaning around the edges of the button with a needle?
Click to expand...
Click to collapse
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
I think its a gonner...
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
mex2309 said:
I think its a gonner...
Click to expand...
Click to collapse
It's alive! Finally i got it to boot up. I don't know how or why. I tried to go to Recover mode and this time I got in and was able to cycle through the menu. I reinstalled the latest ROM I used and it booted up. Strange.... but I'm happy.
mex2309 said:
I left it on the loop for about 2:30 hours. Still nothing- I cleaned around the power button by taking the case off. Everything looked fine but it still loops. Once I was able to get to Recovery mode but I could only scroll down one line before the phone flashes and goes back to the first command line. This leads me to believe that theres something wrong with the power button, its stuck or a short. Also, I still can't turn if off, as soon as I put the battery in- it turns on w/o me pressing the power button.
It's alive! Finally i got it to boot up. I don't know how or why. I tried to go to Recover mode and this time I got in and was able to cycle through the menu. I reinstalled the latest ROM I used and it booted up. Strange.... but I'm happy.
Click to expand...
Click to collapse
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
MasterDecker said:
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
Click to expand...
Click to collapse
Sounds similar to what I just went through... Except I didnt do anything in recovery before mine started looping. Curious to know what rom you were running as well.
MasterDecker said:
Glad you got back into your phone. I am starting to see this happening a lot lately with ROMS. Which particular one were / are you on when it started the boot loop?
Click to expand...
Click to collapse
I was on the Seanscreamz' ICS ROM. I never had a problem with his ROMs before and I've been using them for about a year. They are pretty solid and I recommend them. It had to do something with me wiping caches and wiping battery stats because it happened shortly after. But I'm just guessing.
mex2309 said:
I was on the Seanscreamz' ICS ROM. I never had a problem with his ROMs before and I've been using them for about a year. They are pretty solid and I recommend them. It had to do something with me wiping caches and wiping battery stats because it happened shortly after. But I'm just guessing.
Click to expand...
Click to collapse
I'm trying to wrap my head around that, and not coming up with anything valid. Wiping the caches would cause a much longer boot time, battery stats, at most should only cause you to need to remove and reinsert the battery.
Just about the only thing I could come up with would be that when you wiped the caches, was that your phone was trying to reload all that data back into the cache and was getting brain dead.
More information is needed from others that have had the same issue, on the same ROM, or different does not matter, but detailed info as to what exactly was done prior to the boot loop issues.
If my phone gets stuck in a boot loop, usually after I flash someting in Odin or whatever, if I hit factory reset it fixes itself.
It doesn't bother me since all my stuff is backed up though.
You should Odin back to stock then flash cwm
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
just got a phone off of craigslist.. saw that it booted up, so i figured i might be able to fix it. cost me $100.
just finished ODINing it, but it just continues to bootlop. not sure what to do next.
Flash a recovery in Odin and see if you can enter recovery. Wipe data/factory reset if you get there.
hechoen said:
Flash a recovery in Odin and see if you can enter recovery. Wipe data/factory reset if you get there.
Click to expand...
Click to collapse
already did that.. flashed CWM, ran recovery and installed rom. no go. now i see the cyanogen boot screen, but it won't get past that. this is kind of strange.
i think the issue with this phone is hardware related. constantly the phone turns itself off. i eventually was able to get stock rom to work (not sure how), but it goes haywire. wifi works, but for whatever reason, i can't download from the play store.
also, when im in CWM.. it reboots randomly. sometimse pressing the power button hits twice too. my old i777 has gone haywire too.. i might have to rethink what i will be choosing for my next phone.
mistabeo said:
i think the issue with this phone is hardware related. constantly the phone turns itself off. i eventually was able to get stock rom to work (not sure how), but it goes haywire. wifi works, but for whatever reason, i can't download from the play store.
also, when im in CWM.. it reboots randomly. sometimse pressing the power button hits twice too. my old i777 has gone haywire too.. i might have to rethink what i will be choosing for my next phone.
Click to expand...
Click to collapse
I did what I could to try to replicate your situation. Which version of CWM are you installing? I went through several different versions up to the latest and found that the phone was having an issue with CWM itself. (possibly corrupted driver, but not 100% sure on that, as the phone does get recognized by the computers.)
But when I got to the latest CWM, and it started doing similar to yours, what I did was the following.
#1 : reinstall drivers
#2 : plugged the phone into the USB 2.0 slot on my laptop.
#3 : removed the battery, sim card, SD card
#4 : tried to power on the phone holding the power button for approximately 20 seconds. (nothing)
#5 : put in the battery while still plugged in, and powered on.
#6 : After phone booted up, and computer recognized the phone, I removed the battery. Phone stayed on.
#7 : waited while the computer re installed the ADB drivers, after driver install success, I unplugged the phone. Of course it powered down.
#8 : Restarted the laptop, put the battery back in the phone, and held vol + and - and power. Phone rebooted into recovery, but got into a boot loop when trying to recover.
#9 : downloaded TWRP recovery and put it on the SD card for the phone. Restarted the phone into recovery and installed TWRP recovery.
#10 : Rebooted phone into TWRP recovery. wiped all cache, installed latest STOCK ROOTED ROM.
The phone has been stable and working just fine, no wifi or blue tooth issues, calls are as normal, texting is as normal. LTE speeds as normal.
I have since switched all my devices over to TWRP recovery and have had ZERO issues.
Guys, wondering if someone could give me some direction to restoring my TF101 to working conditions.
I have a rooted TF101 that was running 9.1.2.27.
This setup has been running great since .27 (not done OTA, Found here) came out, so I haven't bothered upgrading recently.
Fast forward to this week and it seems the Tablet started locking up at some point in the last couple days I hadn't used it. This would cause a battery drain until the device turned off. Upon rebooting I could get into the OS for maybe a minute before it would freeze again.
I decided to wipe the device, I went into CWM Recovery and wiped all caches and then tried to wipe all data/factory reset. It is at this time I get the following error:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
Try starting back up and get a boot loop.
Upon reflashing the ROM, I find the TF101 in constant boot loop not making it 8 seconds into the bootup before rebooting.
I can still get into recovery so I try various kernels and roms with no success. Through searching I find CWM 6.0.1.4 and load it. Everything loads normally and I can now wipe data/factory reset, wipe all Cache even format all parts. I try to flash every ROM I can get my hands on from stock to older roms that I have ran succesfully to EOS Nighties, Every rom goes into Boot Loop after about 10 seconds.
Any Idea on where to go from here? I have been reading threads for hours now with no solution.
MODS: Putting in DEV since this is a Rooted TF, but if this should go to Q&A please move
This question should be in the QA section...
But your stock ROM was ICS and the newest EOS nightlies are based on JB which have different partitions. If you flash back and forth with ICS and JB you could be running into problems there.
Have you tried the option in CWM called "Fix Permissions"? This is supposed to reset the permissions correctly for the system apps area I believe which helped a lot of people with force close issues. It's worth a shot.
Are you installing ROM's from external SD card or the Internal SD card? That shouldn't matter but I have always stuck with the External SD card.
One thing you could also try is to wipe the big 3 several times a piece before installing the ROM. I found it had made some ROM's load better when I encountered a few issues. Also, stick with one ROM either ICS or JB. Going back and forth will cause problems.
Also, I remember that from ICS to JB, some ROM's required the ROM to be installed twice literally after it installs install it again or some ROM's may reboot themselves back into recovery to complete the install.
Try that with the ROM you pick to get things back on track.
There is also some "Super Wipe" scripts floating around but I believe they were for a specific ROM and I think it was ICS based. You should be able to search XDA for that here in the Dev section.
TomTcom said:
This question should be in the QA section...
But your stock ROM was ICS and the newest EOS nightlies are based on JB which have different partitions. If you flash back and forth with ICS and JB you could be running into problems there.
Have you tried the option in CWM called "Fix Permissions"? This is supposed to reset the permissions correctly for the system apps area I believe which helped a lot of people with force close issues. It's worth a shot.
Are you installing ROM's from external SD card or the Internal SD card? That shouldn't matter but I have always stuck with the External SD card.
One thing you could also try is to wipe the big 3 several times a piece before installing the ROM. I found it had made some ROM's load better when I encountered a few issues. Also, stick with one ROM either ICS or JB. Going back and forth will cause problems.
Also, I remember that from ICS to JB, some ROM's required the ROM to be installed twice literally after it installs install it again or some ROM's may reboot themselves back into recovery to complete the install.
Try that with the ROM you pick to get things back on track.
There is also some "Super Wipe" scripts floating around but I believe they were for a specific ROM and I think it was ICS based. You should be able to search XDA for that here in the Dev section.
Click to expand...
Click to collapse
The ICS to JB isn't the issue as the issue started happening randomly with a ICS Rom that has been working for 4+ months when it has never had anything put ICS (well HC when I got it last year). Trying the JB rom was a near last ditch effort
I tried Revolutions superwipe several times, didn't help.
I probably completely screwed it up now in frustration. Tried to load the stock rom and now Recovery is screwed and it is boot loop so I don't think I can connect it to the computer now.
Hosed you think?
So now the question is, with a Tab that won't stay on longer then 8 seconds and no longer has a recovery, is there any other hope? I'm guessing bricked.
Firehawkns said:
So now the question is, with a Tab that won't stay on longer then 8 seconds and no longer has a recovery, is there any other hope? I'm guessing bricked.
Click to expand...
Click to collapse
You held down pwr + volume down when turning on and no text appears at the top left?
If not follow this thread
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=nvflash
or http://forum.xda-developers.com/showthread.php?t=1688447&highlight=bootloop
Firehawkns said:
Guys, wondering if someone could give me some direction to restoring my TF101 to working conditions.
I have a rooted TF101 that was running 9.1.2.27.
This setup has been running great since .27 (not done OTA, Found here) came out, so I haven't bothered upgrading recently.
Fast forward to this week and it seems the Tablet started locking up at some point in the last couple days I hadn't used it. This would cause a battery drain until the device turned off. Upon rebooting I could get into the OS for maybe a minute before it would freeze again.
I decided to wipe the device, I went into CWM Recovery and wiped all caches and then tried to wipe all data/factory reset. It is at this time I get the following error:
Error removing /data/data/com.android.browser/databases/webview.db-wal!Error formatting /data!
Try starting back up and get a boot loop.
Upon reflashing the ROM, I find the TF101 in constant boot loop not making it 8 seconds into the bootup before rebooting.
I can still get into recovery so I try various kernels and roms with no success. Through searching I find CWM 6.0.1.4 and load it. Everything loads normally and I can now wipe data/factory reset, wipe all Cache even format all parts. I try to flash every ROM I can get my hands on from stock to older roms that I have ran succesfully to EOS Nighties, Every rom goes into Boot Loop after about 10 seconds.
Any Idea on where to go from here? I have been reading threads for hours now with no solution.
MODS: Putting in DEV since this is a Rooted TF, but if this should go to Q&A please move
Click to expand...
Click to collapse
Try using NV flash to go back to stock if you can get into APX mode.
Sent from my DROID RAZR HD using xda premium
morphuex said:
You held down pwr + volume down when turning on and no text appears at the top left?
If not follow this thread
http://forum.xda-developers.com/showthread.php?t=1688012&highlight=nvflash
or http://forum.xda-developers.com/showthread.php?t=1688447&highlight=bootloop
Click to expand...
Click to collapse
Yea, I can do the power + vol down and then up and get the recovery android guy, then he goes on his back and a red exclamation comes up (which I believe means no recovery mode installed
I can also do the pwr + vol down and then wait 5 seconds and get the wipe device or android options, but it won't let me choose anything, 10 seconds later it reboots.
clouse2013 said:
Try using NV flash to go back to stock if you can get into APX mode.
Sent from my DROID RAZR HD using xda premium
Click to expand...
Click to collapse
Will try tonight, but I believe all of those involve the computer having time to recognize the device, which it doesn't stay on long enough for the computer to recognize is and it won't seem to connect USB when the android guy is up.
nice rom! going to check this out tonight, thanks!
So I got into APX mode, windows shows no drivers, but it does show in devices. Trying NVFLash it says it is doing something, but nothing on the TF changes. Is there another step I am missing?
Firehawkns said:
So I got into APX mode, windows shows no drivers, but it does show in devices. Trying NVFLash it says it is doing something, but nothing on the TF changes. Is there another step I am missing?
Click to expand...
Click to collapse
Have a search for universal naked driver in the dev section, that should sort the drivers out I believe then you should be good to go.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
There you go
pops106 said:
Have a search for universal naked driver in the dev section, that should sort the drivers out I believe then you should be good to go.
---------- Post added at 10:37 PM ---------- Previous post was at 10:34 PM ----------
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked+driver
There you go
Click to expand...
Click to collapse
Thanks for the info, truly! I had searched for Drivers, but not naked.
That worked and it allowed me to use Easyflasher to get CWM back on.
Now I am back where I started, I have tried loading several Roms. Everyone hangs up about 15 seconds into first boot while the setup splash screen is on (for example the dotted circle on stock Asus rom or the simon says color circle like the JB rom or what ever it was in the ICS rom I was using. Something in the tab is stopping it from booting on up.
But I can now format everything and wipe data. I can connect APX mode. Anything else I can try from there. Starting to seem like something Hardware is busted.
Firehawkns said:
Something in the tab is stopping it from booting on up.
But I can now format everything and wipe data. I can connect APX mode. Anything else I can try from there. Starting to seem like something Hardware is busted.
Click to expand...
Click to collapse
Did you fix permissions while you were in recovery? It's a long shot but that may help. You may have a folder that's chmod'ed incorrectly. If so that'll prevent the system from being able to write or read to that folder making it impossible to install to, or run from it. Fix permissions, re-flash and reboot.
I know TomTcom mentioned it already. I don't see if you tried it in your replies though.
grgmre said:
Did you fix permissions while you were in recovery? It's a long shot but that may help. You may have a folder that's chmod'ed incorrectly. If so that'll prevent the system from being able to write or read to that folder making it impossible to install to, or run from it. Fix permissions, re-flash and reboot.
I know TomTcom mentioned it already. I don't see if you tried it in your replies though.
Click to expand...
Click to collapse
Yea, I tried that first. Sorry forgot to mention.
Are you able to flash the stock firmware using Easyflasher?
cabraswell said:
Are you able to flash the stock firmware using Easyflasher?
Click to expand...
Click to collapse
yes, I am able to flash to stock rom I got from Asus and the one I took for Rooted with stock on the forum. The flash, and it gives you the initial progress bar on first boot, then reboots at the end of the progress bar and goes to the Asus with the moving circles for about 5 seconds then keeps rebooting from there.
In a PC world I would wonder Ram issues, Over heating, or insuffecent power supply at this point. Not sure what to think here.
Is there a way to use TWOP and delete everything you see on the system and then reflash?
Firehawkns said:
yes, I am able to flash to stock rom I got from Asus and the one I took for Rooted with stock on the forum. The flash, and it gives you the initial progress bar on first boot, then reboots at the end of the progress bar and goes to the Asus with the moving circles for about 5 seconds then keeps rebooting from there.
In a PC world I would wonder Ram issues, Over heating, or insuffecent power supply at this point. Not sure what to think here.
Is there a way to use TWRP and delete everything you see on the system and then reflash?
Click to expand...
Click to collapse
In Addition, I have tried several times using TWRP to format Data and it fails. Could this be a clue?
Firehawkns said:
In Addition, I have tried several times using TWRP to format Data and it fails. Could this be a clue?
Click to expand...
Click to collapse
Have you tried using nvflash that blasts everything, takes you back to as clean as clean can be.
I am starting to think hardware though but if you can sit in recovery of adb / apx mode without issue then maybe it is a software thing.
No probs wiith the drivers by the way, its not really the right website for searching for the word naked.... dam don't can't won't imagine what you could of found with the members in here...
SUCCESS!!
I am not totally sure what finally worked as I just kept trying to reset/wipe/format/ and reflash, but this last time finally worked it seems. I have the stock Asus rom back on and going through setup.
I do find that if I try to put EOS on it just sits at the color things that show loading and never moves forward, so I just put the stock rom back on for now. Try to get Root back on for Titanium backup and enjoy the tablet again and worry about JB later maybe.
Firehawkns said:
SUCCESS!!
I am not totally sure what finally worked as I just kept trying to reset/wipe/format/ and reflash, but this last time finally worked it seems. I have the stock Asus rom back on and going through setup.
I do find that if I try to put EOS on it just sits at the color things that show loading and never moves forward, so I just put the stock rom back on for now. Try to get Root back on for Titanium backup and enjoy the tablet again and worry about JB later maybe.
Click to expand...
Click to collapse
I'm glad you finally got it fixed. I had some issues a while back (two weeks after I bought it) and I panicked and caused more trouble. Finally after stepping away from it for a day or two and a wife encouraging me I was able to get it going again...but my gut was in knots for that day or two.
Tablet after redoing the original root does not go over the system.
Not have access to ADB DEVICE or by Windows or the Linux Ubuntu, no longer accepts update totally blocked.
Ask help for those who have been through this problem.
So i was trying to install synergy rom (this one)
http://forum.xda-developers.com/showthread.php?t=1792499
So I rebooted into TWRP recovery, backed up, factory reset thrice, and went to flash it. As it was flashing, the installer popped up, and i followed the directions. I chose the middle one (medium amount of bloat) because they said that it was recommended, and I wasn't exactly sure what the three options were.
Anyways, after waiting for awhile on the loading bar, it eventually rebooted, and I assumed it was working (i hadn't been staring at my phone for the 5 minutes, so im not sure if anything popped up on the screen)
So when it started to reboot, it flashed by with the Galaxy SIII screen with Cid underneath it (i had been running cm10 before this) which i thought was a bit weird, but I figured i would let it go and see what happened
So then the screen turned completely black and just sat there. I waited for a good 10 minutes, and with nothing happening I decided to pull the battery and restore back to cm.
Now I decided that I might as well try again with CWM, to see if the issue was with TWRP.
I went through the same rom installation process and the same exact thing happened.
As it is, I'm going to keep using Cm until i can figure this out.
¿Any suggestions? Thanks in advance.
Synergy is a TW base Rom right?
CM is a AOSP base ..that might be conflicting the flash ..did u try formating Ur internal memory
99dandan99 said:
So i was trying to install synergy rom (this one)
http://forum.xda-developers.com/showthread.php?t=1792499
So I rebooted into TWRP recovery, backed up, factory reset thrice, and went to flash it. As it was flashing, the installer popped up, and i followed the directions. I chose the middle one (medium amount of bloat) because they said that it was recommended, and I wasn't exactly sure what the three options were.
Anyways, after waiting for awhile on the loading bar, it eventually rebooted, and I assumed it was working (i hadn't been staring at my phone for the 5 minutes, so im not sure if anything popped up on the screen)
So when it started to reboot, it flashed by with the Galaxy SIII screen with Cid underneath it (i had been running cm10 before this) which i thought was a bit weird, but I figured i would let it go and see what happened
So then the screen turned completely black and just sat there. I waited for a good 10 minutes, and with nothing happening I decided to pull the battery and restore back to cm.
Now I decided that I might as well try again with CWM, to see if the issue was with TWRP.
I went through the same rom installation process and the same exact thing happened.
As it is, I'm going to keep using Cm until i can figure this out.
¿Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
Try wipe cache/dalvik cache/data/system then reflash.
twistedillutions said:
Synergy is a TW base Rom right?
CM is a AOSP base ..that might be conflicting the flash ..did u try formating Ur internal memory
Click to expand...
Click to collapse
How does one go about that? I dont remember having to do that the first time i flashed from stock to cm (although that was a long time back )
And I did that when i first flashed it both with TWRP and CWM.
99dandan99 said:
How does one go about that? I dont remember having to do that the first time i flashed from stock to cm (although that was a long time back )
And I did that when i first flashed it both with TWRP and CWM.
Click to expand...
Click to collapse
im not familiar with CWM but on TWRP
FIRST back up ur internal memory on your pc or micro sd card the stuff u want save ..pics vids etc
wen u go into TWRP recovery
-click WIPE
-swipe to the right for FACTORY RESET
-after done press back
-click FORMAT DATA
-messege pops up says are you sure u wanna do it it will erase EVERYTHING on your internal memory .(remember if u save what u wanted ) type YES and your done ..
-flash rom and gapps
-boot ..first boot always takes a while
Hey Everyone. First of all I would like to say that I've had this device for about a year and a half, but it bricked? on me in only 4 months. I've tried countless methods to fix it but no go. Then as time went on I completely forgot about it. Now I don't have my sd card that I used for it any more.
The problem? One day I accidentally forgot to charge my tablet and it died on me, so I charged it right back up and turned it on. Everything went well, I got through the logo screen and everything, but then it just hangs there right before I hit the Home screen where you can do your code and everything.
Methods I've attempted:
I've tried going through CWM recovery to fix the issue but then I notice that it says near the bottom as it loads "E: Can't open/cache/recovery/log" and it has the same "E: Can't open/..." for everything. Can't mount, wipe cache, wipe data, restore, I have no backup (stupid right), can't do anything. Also, when I do attempt to wipe data through CWM I notice "E:Can't mount /dev/block/mmcblk0" if that has any special meaning.
I've tried flashing stock firmware through odin multiple times on different usb ports and different computers.
I've tried flashing PIT file (I'm not really sure if thats how you're supposed to do it but yea, I flashed the PIT file through odin by itself and with stock firmware)
Misc. Info: I did have a custom ROM installed(can't really remember which one), I also have the app2sd installed, the only thing that struck out to me when my tablet went out is that it received an OTA update for 4.1.2? and for some reason it went through even though I never intended to update.
I'm really, REALLY, open to any suggestion that could possibly help fix this tablet. On the other hand if the cold hard truth is that its gone forever or that I simply just have to take it back to Samsung (which I highly doubt I'll be able to), then please by all means let me know.
THANK YOU!!!
Bump
Help Please
Did you try flashing a different recovery again. CWM? Also after installing stock through odin try a factory wipe. It would probably help to know what your last rom was.
Sent from my GT-N8013 using XDA Premium App
I've been scouring the Googlenets for days now trying to figure out how to fix this, and nobody has either had the exact same problem I have (doubtful), or no one has posted it.
I'm currently running CM10 and Android 4.1.2. I was planning on upgrading to lollipop via http://forum.xda-developers.com/eee-pad-transformer/development/rom-t2942560, but somehow my recovery stopped working. I had TWRP 2.3 and was going to upgrade to 2.8 (as recommended), and that's where something went wrong. I'm not exactly sure what I did, or what step I was on when it happened, but I rebooted the tablet and ended up with a never ending Asus splash screen. POWER + VOLUME DOWN to access recovery didn't get me anywhere but the same splash screen with some white text promising a recovery that would never come.
I tried APX flashing with Easy Flasher to no avail. I tried POWER + VOLUME DOWN, wait, then select wipe. Nothing. When I POWER + VOLUME DOWN, and wait, I can boot into CM10 just fine and everything appears dandy. That's when I tried Factory Reset in the settings. Still nothing!
Am I being dumb? Any help or even just some empathy would be great about now. What should I do?
Thanks in advance.
bump for luck...
I'm guessing this is a new problem and the device is too old to tinker.
I would suggest returning to stock and starting over again.
barkeater said:
I would suggest returning to stock and starting over again.
Click to expand...
Click to collapse
By returning to stock do you mean factory reset? My problem is I am unable to factory reset. Do you know another way to factory reset that I didn't try? Thanks.
I had a little time to mess around with this again, but unfortunately I didn't succeed. I tried using EasyFlasher from this post: http://forum.xda-developers.com/showthread.php?t=1688012. It taught me that the difficulties continue. It would appear tat I am not able to turn on APX mode, as I get no connection after holding power and volume up for what seems like an eternity.
I also started to wonder if something is wrong with my partitions. When I look at storage in settings, it says I have 13 GB total space, but when I add up the apps, pictures, audio, downloads, and available, it only ends up at 4 GB. That's weird.
Anyone out there have any ideas? Thanks.
ZachTMartin said:
I had a little time to mess around with this again, but unfortunately I didn't succeed. I tried using EasyFlasher from this post: http://forum.xda-developers.com/showthread.php?t=1688012. It taught me that the difficulties continue. It would appear tat I am not able to turn on APX mode, as I get no connection after holding power and volume up for what seems like an eternity.
I also started to wonder if something is wrong with my partitions. When I look at storage in settings, it says I have 13 GB total space, but when I add up the apps, pictures, audio, downloads, and available, it only ends up at 4 GB. That's weird.
Anyone out there have any ideas? Thanks.
Click to expand...
Click to collapse
Sounds like your OS is still loading? If so you might try this apk. "Reboot2Recovery" if that gets you into recovery you can flash the new twrp from there.
No luck. It boots to the never ending Eee Pad splash screen, which is the same screen it hangs on if I reboot normally.
ZachTMartin said:
No luck. It boots to the never ending Eee Pad splash screen, which is the same screen it hangs on if I reboot normally.
Click to expand...
Click to collapse
Anything here help you?
http://www.transformerforums.com/fo...-recovery-kernel-need-help-desperately-2.html
or here
http://www.transformerforums.com/fo...ogo-screen-keeps-restarting-eternal-loop.html
Stock firmware is still avaialble
http://www.asus.com/ca-en/support/Download/28/1/0/1/32/
None of them had an answer to my problem. When I do the volume down + power I get the two icons, wipe and cold boot. Wipe doesn't do anything and the other option puts me back in my OS.
I really think it's something to do with my partitions, but I haven't been able to find anything to fix it. Is there a way to reset my partitions without APX? I can't seem to APX either.
ZachTMartin said:
None of them had an answer to my problem. When I do the volume down + power I get the two icons, wipe and cold boot. Wipe doesn't do anything and the other option puts me back in my OS.
I really think it's something to do with my partitions, but I haven't been able to find anything to fix it. Is there a way to reset my partitions without APX? I can't seem to APX either.
Click to expand...
Click to collapse
When I read your problem again t seems that you have CM10 installed with stock recovery? Must be due to failed install in your first post.
Did you try the firmware download from the asus link above? Wonder what happens if you copy to system and if cm10 would recognize it as a system update ans install.
http://www.asus.com/support/FAQ/1011948/
Watch out for asus's zip in a zip.
I dusted this off with the long break. Tried to install the Asus firmware and ended up hanging on the load screen again. I'm starting to think it must be something with my bootloader, but I can't seem to figure out how to get in there.
This is probably a lost cause at this point. Thanks for the help.
Happy new year!
Edit:
I decided not to give up and ended up getting recovery back! Woohoo! I'm not really sure exactly what the problem was, but I was looking here (http://blog.chazomatic.us/2013/10/27/updating-and-rooting-an-asus-transformer-tablet/) and it looks like the following fixed it:
Code:
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
I'm still not sure why, but now it boots normally and goes into recovery just fine. :good: