Related
So, I did a quick search and didn't come up with anything I hadn't already seen and tried. If I missed it please send me in the right direction because this is driving me insane.
First is my SD card isn't coming up. It is only showing the internal SD card, not the external. I see the emmc area that I assume everyone is like, "Oh! There it is", but it doesn't show anything, it just says unavailable for total and available space. I've tried to fix from the alpha but everytime I try and edit the file it doesn't let me save it.
I'm also having issues with the BSR. Everytime I try and use it I get stuck at the M screen. I've installed the one provided for CM7, but no matter what I do I just get stuck at the M screen.
I've tried SPFing and just strating from scratch, I've tried to wipe data/cache in stock recovery... I've tried everything I can think of and anything I can find in the forum but nothing has helped... Maybe I'm just missing something though. So if anyone could help me out I would really appreciate it.
Nevermind, this ROM actually broke my will to live and I'm just going to SPF back to stock for now since I can't do anything other then stare at the M screen because I accidently hit Charge Mode in the BSR... And apparently that completely breaks everything in CM7... So if a mod could lock or delete this thread, I would appreciate it.
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.
People that can't get the roms beyond stock to work, are your phones activated?
Is it possible to use the Pac Man Rom or CM10 on an unactivated phone?
I'm having similar issues to others trying to flash Pac Man and CM10.2. The first boot was fine and I can access everything on the phone fine, including settings. I rebooted and the activation screen (which I skipped as this phone doesn't have service) always pops up but I would like to use it without putting it on a cell network. I can skip the screen fine (until I decide to disable it) but then have issues like the keyboard (physical and touch), systemUI or NAV Bar crashing with a constant message pop up telling me it has crashed. I have returned to stock using RSD and reflashed Pac Man and CM10.2 MANY (15+?) times, doing a clean install 99% of the time but also trying a couple dirty installs to cover my bases. I should also note that I flashed the phone to Cricket but have no plans to activate it anytime soon.
Another thing to note is that I had issues getting the custom roms to boot at all as the initial setup would take hours. One time I though it was a boot loop but I left it on all night and it had booted in the morning. I believe it has something to do with the file check at boot (with my 32GB low speed class SD card) but that seems to be resolved and I can get the custom roms to boot fine (on the first boot) even with my 32GB (witch is fine and has no errors nor is generic, before you ask.) I also have tried 2 4GB cards and a 2GB card, all different brands, with no change in behavior.
I have done everything below multiple times and in different orders.(If needed I can give a direct breakdown step by step but if you could do it with the files below, I have probably tried it)
Wipe the phone (including all storage internal and external SDs included)
Using RDS v6.15
RDS asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip (Works 100% of the time and never has issues. I keep reverting back to this if I actually need to use the phone)
RDS ClockworkMod, TWRP, and Open Recovery without TWRP (Tried different versions when available)
Then used each recovery to install Pac Man or CM10.2 (tried 10.1 once but had the same issues and I didn't see the need to troubleshoot a rom people seemed to not want to develop for. So 10.1 was only tried once but has the same issues)
Installed GApps at this point but I also tried alternate versions of GApps and not installing it at all. All have the same effect and don't seem to be contributing to the problems at all.
A few installed I tried wiping the phone again or installing each zip multiple times. I also verified the zips were good when on the device to make sure there was no corruption at transfer.
I also tried multiple (confirmed working) SD cards and installing from the internal storage.
I have tried installing arrrghhh's Kernel too.
The issue ether seems to be boot loop (if it's doing a file check) or more often it works until I get one of the said crashes after a reboot.(blame Tyler message is getting SO old...) The time I see the errors seems to be accelerated if I mess with the settings a lot but I don't believe it is directly related to the settings.
My next recourse is to try and flash it back to Sprint (maybe check my Cricket settings) and see if that helps, without it being activated.
On a separate note.
If people need help I can help get you back to stock easily. The instructions/guides on here are all but useless if you don't know what you are doing already. I have seen down to "USE RDS" or "DELETE LINE MD5" like people would just know what that means. I understand RDS Lite is a standard tool for flashing phones but it's nigh impossible to find real explanations on what stuff does in context. I understand the basics though, so if anyone has any questions I can walk you through it.
To start with if you are stuck in a loop at the start of a new rom and it loops between the 'Welcome' Screen (Select your Language) and Activation screen just skip the initial setup by tapping the corners on your screen in a clockwise manor when on the 'Welcome' screen to skip the setup there is a video to explain it here
pocketnow(can't post links )com/how-to/android-quick-tip-how-to-bypass-touch-the-android-to-begin-video
Without doing this or activating the phone it seems to loop between those 2 screens forever (might indicate part of the problem with customs roms....)
I hope this is enough info to go off of I can give you a play by play with the actual files if you need. Maybe a video if needed and I'm feeling extra fancy.
Thanks for your time.
Hey buddy,
If you're trying to make a guide, make sure you call it what it is properly - RSD Lite.
Also, maybe clean up your post a bit so it's a proper guide (as you point out, it's needed) and make a separate thread for your question.
To answer your question, the unactivated phone shouldn't be an issue in of itself - you'll just get the nag screen like you were talking about.
I know there is an issue some are having with rebooting the 4.3 ROM's. Have you tried any 4.2.2 versions of anything? Carbon, CM10.1?
I wonder if your "flash" to Cricket is causing issue, I'm not sure. Let me know about 4.2.
Edit - I missed this part on my first read of your PM. Taking hours to boot is NOT normal. Perhaps remove the SD card entirely, flash using the internal SD... I've never heard of that. Anything over say 20 minutes is probably cause for concern.
Thanks for taking time to answer me.
In no way was I trying to make a guide yet but I guess I could. I just hate posting stuff without useful content so I figured throwing that in was better than nothing. I'll clean it up and set up some links later today. It's frustrating to try and make a full guide before I can post links that would be needed for it. You are totally right though! (complain about crappy guides and kind of make one... )
Part of my point there was that I can't post out of Q and A and this wasn't really a question so I made a question out of it and that's how my post ended up.
I have flashed many phones before but like I said I'll try and put it back on Sprint later today (probably will be a few hours) as I backed up the settings the phone came with. I know it was a wall of text and not the easiest to read so you probably missed it but I also said in my first post that I tried the internal SD card many times and the taking hours to boot isn't the standard and doesn't seem to happen at 99% of the time. It seems to be related to the recovery software I use as it happened a lot more when I was testing TWRP and none when I use clockwork.
What Recovery do you recommend? I swear they aren't made equal...
I tested CM10.1 once and it had the exact same issues as CM10.2 and Pac Man so I didn't test it further but if you want me to test it I can. I just didn't want the Rom.
I don't want Carbon either but I'll test that and AOKP next. It's just annoying that the stock rom works perfect but I can't get these to function at all. I almost wish I didn't get Pac Man to work at all. I'm very particular about my settings and NEED these features after I tried them Pac Man is AMAZING.
Thank you for the help and I hope I can get this worked out.
PS I saw that you were frustrated about working on a rom you don't have a device for. I hope you don't let a little thing like that stop you as, for the little time I have used it, it's all I want. Thanks again.
Blasz said:
What Recovery do you recommend? I swear they aren't made equal...
Click to expand...
Click to collapse
Well, OpenRecovery has probably the most work done for this device specifically. I liked TWRP, but it seems lately it has been unstable - you're not the first who has reported issues lately. I don't think CWM has been updated, unfortunately - but perhaps that's a good thing, it's stable that's for sure.
Blasz- I was just about to start a thread when I found yours, and it very accurately describes the issues I've been having. Here's my progress so far.
I got my Photon Q with Sprint and used it for a few months before Sprint started finding creative ways to take my "$79.99" bill and make it more like $140 a month. Naturally, I refused to pay. So I had a Photon Q with no cell service. This is fine, as I only need it to work on WiFi, not 2G/3G and there is no 4G in the area. Anyway.
At the time, I had Ice Cream Sandwich on it, using the (latest?) ICS firmware from Motorola. This worked very well, but I later tried to use a newer firmware, and all the custom ROMs had shown up while I hadn't been looking. All of these seemed to be based on JellyBean. First off, I tried CyanogenMod 10.2. Worked amazing well! I had literally no problems at all. However, while I was experimenting with different software for the phone, and wanted to see if "Arrrgghh"(sp?)'s kernels would give me some decent overclocking capability. Turns out, the kernel I picked wasn't compatible with the JB firmwares (I probably picked an older one by mistake.) Needless to say, it now wouldn't boot. It'd go to the "Unlocked bootloader" screen and stay there all night (literally, I tried that.)
So, I went back into CWM, which is the recovery I have installed. I erased /data, /cache and /system, and also the dalvik cache and battery stats for good measure. I also formatted /pds and /modem, I believe, which was probably dumb of me since I'm not sure what those do. Then I tried re-installing CM 10.2 from CWM. The installation went fine, and it works gorgeously. However, there's two weird issues:
1) WiFi and Bluetooth don't even BEGIN to work! Neither does Cell, as far as I can tell, because where CM used to be unable to make calls or access the internet (of course, I've not been paying my bill), it now shows an empty signal bar or "No Signal" (the little red X) in the notification bar ... When I try to turn on WiFi using the slider in Settings, it moves to "ON" (stays gray) and pauses for a few secs, then goes back to OFF. Same thing for BT. If I open the WiFi menu where you select an AP, it tells me to turn on WiFi. I do, using the slider up top, and the same thing happens. WiFi and BT simply won't turn on. Tried fiddling with every setting I can find.
Before this misadventure with the kernel/reinstall, WiFi worked great. I connected to a local AP and was surfing the net and downloading apps.
2) The system takes a VERY long time to boot up. It sits at the "Unlocked Bootloader" screen for up to a whole minute. Then it goes to the Cyanogen screen for about 30 seconds. Then it gets to the homescreen. It's fine so long as you let it boot up, but this doesn't seem normal.
Next I tried other ROMs thinking that might help. I installed AOKP, PacMan, CM1.0, Carbon, SlimBean, and I think a few others without results-- they all work but WiFi and BlueTooth are dead. PacMan is the only exception-- it boots up and then endlessly gives me "Blame Tyler" errors until I force the machine to shut off.
I also tried an older ROM, since these are all JellyBean ROMs and I wanted to get back to ICS (I'm not that fond of JB's interface) anyway. I was unable to find any ZIPs I could install through CWM of the stock firmware. I found some IMGs that it looks like I could install via Fastboot, but I don't currently have a PC with admin priveleges (it's not mine) so I can't install the drivers to use Fastboot or any part of the SDK. (I can, however, put files on my SD card, that doesn't require privleges.) The closest ROM I found to stock was "TwistedAsanti" beta-1 or whatever it's called. That installs fine, but again, it takes about 2 straight minutes to boot and it's useless after that:
It gets stuck at "Starting Services..." and will sit there forever, even left there all night. Behind this, a dialog pops up saying no cell networks were found and asking if I want to switch to GSM. (i've been trying GSM and CDMA ROMs all this time, I don't need cell access so I doubt it matters which I use. I'm in the USA.) You can pull down the notification bar and get into the Settings, and even launch a couple programs, but I can't find ANY way to get to a homescreen. Task manager shows Circles is running, which is a widget on the homescreen, so where the heck is that screen? .. I try, again, to turn on WiFi or BT without success. The friggin thing just won't turn on.
Did I eff it up by erasing the "PDS" or "modem" partition? Am I missing something obvious or is my phone just possessed?
In a few days I should have access to a computer where I can hopefully use Fastboot and see about installing a stock firmware (wish me luck). Until then, does anyone have a ZIP file I can flash from CWM to get back to an ICS firmware? I managed to find a copy of the stock firmware, in the form of a dump done from TWRP (in .win files). But as far as I know the only way to install TWRP is using Fastboot, and I've explained why I can't do that. I don't know a way to install TWRP from CWM. Maybe I can do it from CM10.2, if I can put APKs or something on my SD card. I can't get it on the network, so I have to copy all the files manually. Needless to say, it's a pain.
After my frenzy of ROM installing, I got frustrated and decided to see if TwistedAsanti would do SOMETHING if I let it sit at "Starting Services" overnight. To my mistake, I left it under my pillow and the system was quite toasty, and the battery had run dead. Plugging it back into the charger, it made a few worrying clicking noises from the speaker, then the green LED came on. This LED seems to mean "I'm charging, but the battery is too dead to turn on for a while." After it sits there a while, the green LED turns off and it just goes black. Or it goes to BOOTLOADER UNLOCKED and bootloops, or goes to black untilyou fiddle with the power button some more. I can once in a blue moon get to CWM. Sometimes it gets to the homescreen. It will charge up to about 4-7% and no further (battery got damaged by the heat?) It doesn't reliably work when plugged in, it likes to shut off at random anyway.
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.
Epicenter714 said:
So now I'm stuck with a phone I can't seem to charge, or turn on reliably, and if I *do* get it to boot up, there's no way to connect it to a network.
Needless to say I'm pretty darn frustrated..
Thanks for any advice.
Click to expand...
Click to collapse
Did you try to use RSD Lite and flash the device back to stock?
arrrghhh said:
Did you try to use RSD Lite and flash the device back to stock?
Click to expand...
Click to collapse
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!
Epicenter714 said:
Currently, I have no PC to use that has Admin priveleges, so I can't install the USB drivers or RSDLite. I also can't use fastboot to install TWRP to use the TWRP .win backups I found.
I did get a roommate to let me use his laptop for 10 minutes to try RSD Lite, but I had this result: Loaded the ".xml.zip" file for the 4.0.4 and 4.1.2 firmwares (after removing the 'getvar' line that causes problems) and it says the phone reported "FAIL". No further details. MiniRSD gives no info from the phone other than the model (it all stays blank), is that supposed to happen? I have the phone in "AP Fastboot" mode so I don't see the problem.
The guy who let me use his PC momentarily is computer-illiterate and thinks anything will break it, so he only let me use it momentarily, and won't let me touch it because I accidentally left an icon on his desktop. I'll have to ask someone else, I think I may know somone..
If I do, how do I get around this error in RSD Lite? Will keep doing research on my own .. thanks!
Click to expand...
Click to collapse
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.
arrrghhh said:
Well remember - if you are on JB and you are downgrading to ICS, there are additional lines to remove.
Other than that, not sure why it would fail. Make sure 'fastboot devices' works in the command line before doing RSD perhaps.
Click to expand...
Click to collapse
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.
Epicenter714 said:
I'm trying to wipe the device clean and install ICS. Are there any other lines I need to remove? ..
As for Fastboot.. I did 'Fastboot Devices' and got no devices listed. How come it shows up in MiniRSD? .. I have the drivers installed, Windows says it installed an ADB device successfully. What are some reasons that might not work? Is there any sort of guide for this? Thank you
---------- Post added at 05:51 PM ---------- Previous post was at 05:29 PM ----------
Oh, as far as the weird booting problem, it seems the battery is fine and the charger died coincidentally at the same time as the overheating did. So my only problem is software now.. thanks.
Click to expand...
Click to collapse
I have no clue what MiniRSD is - you mean RSD Lite?
If it doesn't show up in fastboot devices, sort that out before trying to use RSD.
As I stated previously, if you were on JB and going down to ICS you have additional lines which are needed to remove.
Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
fastboot said:
target reports max download size 31457280 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!
Epicenter714 said:
Yes, RSD Lite. I don't know where I got MiniRSD from.
I got it to show up in fastboot devices, but adb devices doesn't show it. Weird. Is that OK?
I was able to flash TWRP to the phone with Fastboot. RSD Lite was unable to find the phone. However, I opened the XML file and was able to figure out the flash commands to enter from a command prompt, so I did that:
I got these results... all of the files flashed successfully to stock, except for two. I forget the first, haven't got it in front of me, but here's the big one: SYSTEM! (Important, no?) Here's the error from fastboot:
>> fastboot flash system system.img.ext4
(then, Fastboot crashes.)
Does anyone know how to fix that? Also, the system image is way bigger than 31.4 MB. What is it talking about?
Thanks!
Click to expand...
Click to collapse
I would NOT recommend entering those fastboot commands in the XML file manually unless you KNOW what you are doing.
Sort out why RSD isn't working. adb and fastboot are two different things. If fastboot devices shows the device, RSD Lite should work fine. Try again.
Hi!
I could use a little help. Following the lovely directions here, I successfully rooted my phone (XWLF2) Android 2.3.6 and was attempting to CM 10.2 to add jellybean. That went OK, I added the Gapps (which also seemed OK) but then I got stuck on the CVM recovery system. It would not reboot. Turning the phone off and back on kept me on the same screen. Finally, since I had only a /data directory to clear and not the /dbdata originally stated, I tried to clear /boot.
Well, that worked! Got me out of CVM but now my phone turns on, hits the Samsung loading screen and stays there... eventually you can make it loop but it come back to the load screen. I cant even seem to get it to go into download or recovery mode. All the files are still in the SDs but it wont get to them.
How can I re-boot it? Or start form scratch... if nothing is in there, how can I add it, say go back to original and then try again.
I'd appreciate any help you could give. I know I newb-ed it but help anyway. Thanks!
Cheers!
Craig
craigj82 said:
Hi!
I could use a little help. Following the lovely directions here, I successfully rooted my phone (XWLF2) Android 2.3.6 and was attempting to CM 10.2 to add jellybean. That went OK, I added the Gapps (which also seemed OK) but then I got stuck on the CVM recovery system. It would not reboot. Turning the phone off and back on kept me on the same screen. Finally, since I had only a /data directory to clear and not the /dbdata originally stated, I tried to clear /boot.
Well, that worked! Got me out of CVM but now my phone turns on, hits the Samsung loading screen and stays there... eventually you can make it loop but it come back to the load screen. I cant even seem to get it to go into download or recovery mode. All the files are still in the SDs but it wont get to them.
How can I re-boot it? Or start form scratch... if nothing is in there, how can I add it, say go back to original and then try again.
I'd appreciate any help you could give. I know I newb-ed it but help anyway. Thanks!
Cheers!
Craig
Click to expand...
Click to collapse
you cant get in download or recovery mode??? but you can see samsumg logo.... if you cant enter in either of the two modes that I mentioned then use JIG(a hardware device that fits in the charging/USB slot of phone,available on ebay for like $2) to enter instant download mode... flash a stock rom from ODIN and you are done .. let me know if it worked
Little better now
mh,
Reading you comment prompted me to try and get into DL or Recovery mode again and that did work. I could get into DL mode. Trying to load original ROM now. We'll see how it goes. Thanks for the suggestion. At least I figured out that it should still get into the modes.
Cheers!
C
craigj82 said:
mh,
Reading you comment prompted me to try and get into DL or Recovery mode again and that did work. I could get into DL mode. Trying to load original ROM now. We'll see how it goes. Thanks for the suggestion. At least I figured out that it should still get into the modes.
Cheers!
C
Click to expand...
Click to collapse
Goodluck
Well, it helped but not entirely. I got it into DL mode and tried to re-install XWLF2 (as originally installed). It attached to Odin successfully, took about a minute and 'passed'. However, it now goes further but still does not complete it goes past the Samsung logo screen, makes the swirly. twirling stars with sound and the hits the second small Samsung Name screen and sits there.
Should I try the re-install with the sim and SD card removed? Does that impact it in any way?
Should I start with a different base? In the end I would like to get it rooted and to jellybean before I start re-loading everything else. What is the shortest direct route to that end?
Thanks for the continued advice,
Cheers!
Craig
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: