Hey guys,
First off I am the newbiest of the noobs. And I think I stumbled into bricking my asus tf101. I was wondering if you incredibly amazing developers would have a work around for me
I had rooted the TF101 a while back it worked everything was fine, I was frustrated with the poor video performance and thought maybe upgraded to jellybean may improve some speed issues with the tablet. So I ran off did some fast googling and found a forum that posted the nightlies. (Team EOS from this site)
I downloaded the first one (right to the tablet) booted into the root bootloader thing (yea im so noob I don't even know the proper wordage) and installed from that.
Now when it boots it sits at a 4 colored square logo that rotates a pules. each little piece glows (like it's loading) but it just sits there forever. i have waiting 10-15-30-45 minutes nothing.
I was wondering if there was a way I could download a new jellybean file on a SD card, and somehow install over with that?
Could really use the help and need it explained to me like im 2 ..
Really sorry to have to ask guys. Save me!
It's a very well discussed issue here and in the teameos thread.
Did you do a full cache, dalvik, system and factory reset of the device through recovery?
Which recovery are you using? (you probably need a newer one)
If you can still boot in recovery (you should) then wipe cache, dalvik, system, do a factory reset (does not wipe sdcard but you will lose all other data) and finally reflash the rom.
If you can't boot in recovery for whatever reason, you can use easyflasher to go back to stock then start over. Frederuco made an awesome post detailing the entire procedure on transformerforums.
Related
I've tried a lot of things.
Long and short of it, I was dumb. I was playing around with kernels and installed one I shouldn't have. Reason being as I wanted to go back to stock and they stock kernel on hydra-kernels.net(?) was good but it had an error for me. The error was involving phone storage.
So, I went and downloaded a stock D'inc kernel but this as it turns out was from 2.1 or so. Naturally this didn't work and broke my phone or at least really ticked me off.
I tried the downgrade but the bootloader won't see the image (formatted sd to FAT32 both in windows and OS X)
tried to hard reset: nothing
clearing cache nothing
Is there any hope?
any suggestions would be appreciated
Bump.
I need a working phone
Can you get into recovery? (Clockwork or Amon Ra)
If so, just flash a backup. If you do not have a backup (shame on you), wipe everything and flash your ROM of choice. You will of course have to start from scratch this way, but your phone will be working once again.
I was thinking of this. When i boot into recovery and select "wipe data/factory reset" it does it's thing and upon reboot I'm still stuck at the white screen
For some reason it won't install any roms either
Spoke with a Verizon tech and they're sending me a new phone
Should I be worried if they perform tests on it? The phone itself is S-Off because of root. Will they charge me for the new phone?
I have to send the one I have back to Verizon.
I've had a great experience so far with my xoom! I had it rooted and overclocked since the first day I had it!
Its starting to get sluggish and things are beginning to go a little wonky, so I'd like to reflash to either the stock honeycomb 3.1 installation, or one of the roms that I've seen floating around.
The trouble is that the minute I saw the 'encryption' feature, I used it. I did that before ever rooting or overclocking it.
I am now unable to reset to factory defaults. Here is what I've tried:
- using the menu option from inside of the settings area to reset the tablet to factory defaults: When I do this, it reboots and gets to a screen with a little android logo and a progress indicator - however within several seconds the progress indicator goes away and is replaced by that nasty little triangle with the exclamation point saying something isn't right.
- Booting into clockwork mod and formatting everything available to be formatted from CWM: This actually broke the tablet and I had to reflash things to get it working properly. However all of my user stuff and all the settings remained intact.
Does anybody know how to reset the tablet to factory default after its been encrypted? You guys know 50x more than Verizons support team will.
My only other option is to back up all of my data, "break" the tablet, then go use my warranty at the store to get another one. I'd really like to avoid that if at all possible.
What version CWM do you have? Flash the newest recovery if you flashed the recovery from ROM manager. If that doesn't work then flash stock software.
What version Xoom do you have? This is for 3g http://www.xoomforums.com/forum/motorola-xoom-hacking-guides/2788-how-return-stock-3g-4g-hr166.html
You don't have to do the last step of locking if you want to reroot. That should also remove encryption. If it doesn't do a factory reset from settings. And verify CWM works as well.
(Just wrote a detailed post and when I went to post, it said I wasn't logged in and erased it...will give a quick run down and can supply more detail where needed as I work through fixing my phone)
Stuck on the white htc splash screen is my most recent problem. Sometimes it gets by that but then boots into recovery. I think bananagranola has the solution in their sig to flash a boot.img. and think I'm comfortable with how to do that, just need to find that file (in the ROM zip?)
What led up to this.
Successfully unlocked and flashed to CM7 back in late Jan/early Feb.
Started experiencing random freezing about two weeks ago.
A week later (last weekend) flashed Jellybean (R10). Worked great for a couple hours then started having the same random freezes.
If things froze I'd have to remove the battery and reboot. After a day or two of this though it'd get to the point that even that would leave me on a frozen jellybean boot animation. So I'd go and factory/data reset in CWM Recovery, wipe cache, wipe Dalvik then reflash the ROM. and I'd be good for a little while more.
Tried flashing back to CM7 but Recovery didn't like the file (it has a good MD5 when checked) Had tried my restore point from early Feb before to no avail, so decided this morning to try other restore points from the last few weeks, right before and after switching to JellyBean. They got further, the first step is something with boot then something with system. It failed on the system part. OK...so I wiped and reflashed jellybean again, and now I am to my splash screen freezes.
I should have asked for help much earlier (lesson learned!) but here I am asking now...what's the first step.
Do I test out and see if I hang on the splash screen again. I haven't turned the phone on in about an hour. Worried of screwing it up more.
Thanks all.
TL;DR Believe I'm stuck on splash screen and know solution to that. Have had phone flashed with new ROM with no prob for months, recently freezing, regardless of ROM. Hoping for advice on getting things working again, starting with whether fixing the splash screen thing first is where to start
splash screen issue seems fixed
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
irishpanther said:
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
Click to expand...
Click to collapse
That doesn't sound like an sdcard problem. Are you full wiping?
bananagranola said:
That doesn't sound like an sdcard problem. Are you full wiping?
Click to expand...
Click to collapse
I'm wiping data/factory reset and cache as well as the dalvik cache.
The steps to flashing a ROM by sashank at link mention to format /boot and /system. I didn't specifically do those...but don't see the option for /boot in any menus I've checked.
A week or so ago I was beginning to suspect there was an issue with the memory but I never found the right search terms to find out how to do a memtest if that's what would have found any problems. Yesterday I did come across some discussion of a corrupt partition/bad chips in some HTC devices. I followed the directions there and through adb ran dmesg | grep mmc0 and the output was similar to the 'normal' one given and showed none of the messages they claimed to indicate a bad chip.
I'm not too concerned with any data from the phone...I backed all that up long ago and the rest restores from my google account. So if I getting things running would normally raise concerns of lost data, that's not an issue for me.
Thanks for taking the time to read. I try to be brief...but don't want to leave anything out.
Wanted to update here before trying to start a new thread and clogging up the board. The title of this thread is not up to date though.
I can hboot just fine and boot into recovery just fine. My phone is unlocked and rooted, ENG S-OFF from when I used AAHK quite a while ago.
When trying to navigate from menu to menu in Recovery I will get the following error messages (best I remember from last time I was in there, I've let the phone be for the last 2-3 days now)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
This doesn't show up at first though, only after I do a Wipe Data/Factory Reset. And if I understand correctly, that wipes /cache so maybe that's causing these errors?
Anyway, after wiping the dalvik cache I can flash a ROM, I've been using Jellytime, I haven't been able to rollback to CM7, not sure why not.
Jellytime will run though...at first! the first couple of boots I can get in and get through registering my google account and have it begin restoring apps if i make that selection. The time I have to work on the phone before it freezes gets shorter and shorter though. I have to remove the battery to get it to reboot. Eventually I am left with the phone hung during the boot animation. I've left it for over an hour before...it's definitely hung there.
So my reading leads me to believe corrupt partitions. I'm not finding a lot on what I should do to reformat and maybe repartition or whatever I may need to do to recover a functioning phone. I don't care about any data on the phone. I just want to get things working again. I ended up getting a new SD card during all this that arrived earlier. If I can get my phone working, I'd prefer to use that from here on out too. I can use the adb in recovery mode just fine if that's necessary to rejigger things to work.
Can anyone help reset my partitions, if that's what this issue seems to be? If not...any ideas?
Thanks.
Recovery and version?
bananagranola said:
Recovery and version?
Click to expand...
Click to collapse
ClockworkMod Recovery v5.0.2.0
Full wipe?
bananagranola said:
Full wipe?
Click to expand...
Click to collapse
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
irishpanther said:
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
Click to expand...
Click to collapse
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
OK, I'll give this a try. The issue with the freezing is why I moved from CM7 though (which had been stable for four months) so it's reproduced itself in different ROMS. I'll post back once I give this a try. Thanks.
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
I gave Android Revolution a shot. During the flash it gave a message which might also be why I wasn't able to flash back to CM7. The MD5 did verify.
Code:
assert failed:write_raw_image("/tmp/boot.img","boot")
When I went to reboot, I ended up in Jellytime. Of course I had to sign back in to google apps and those things were reset from the dalvik wipe. Shortly there after the phone froze.
On reboot I tried a logcat. Didn't get it right from the start (you can send the command during the boot animation if I read correctly) but captured the failure of things. It's back around the 09:02 portion of the log. To my eyes it looks similar to others I've collected. Especially the message
Code:
Fatal signal 7 (SIGBUS)
though I haven't been able to figure out much about that, or identify what it is before that that could give another clue as to what is screwy since that's maybe (Probably?) related to the flashing issues.
Hi, everyone, I have a Nexus S and I am new to roms and stuff and by far I was using the latest Cyanogen mod, because the installation was easy. I decided to try this custom rom http://forum.xda-developers.com/showthread.php?t=2410844. And after a lot of reading, I figured that i have to install the latest Clockwork mod, so I did, then transferred the rom .zip file to my storage, rebooted in recovery and installed the zip. Then I rebooted again and all that is happening now is - an android text with highlights moving over it is standing in the center of my screen, but nothing loads... I waited like 30-40 minutes but it just stays there... Can somebody tell me if I was wrong with the instructions somewhere or this can be a problem with my device? Thanks a lot and sorry for posting a new thread about it, since I'm new, I'm not allowed to ask in the Developers Section.
I didn't Wipe/Factory reset. Could this be the problem?
It seems you got stuck in the boot loop itself.!! From next time on when you are about to install a new rom, make sure you do a full factory/data wipe.!!
Now that you are stuck in boot loop, just remove batter, insert it, hold simultaneously your volume up+power buttons. From the menu choose recovery. Then
1.data wipe/factory reset.
2. Wipe cache.
3. mounts and storage --> format system.!!
Now you are good to go. Make a clean install of your new ROM. I guess your device by now should work normally.!!
Sent from my Nexus S
Hit thanks if I helped you.!!
Yes, I already did it, right after I asked, with the factory/reset function (I thought this is the problem, so I did it), everithing is ok now, but thanks for answering!
It's ok for the admins to delete that thread, thanks!
I also have a problem with same ROM.
Every once and a while after making a call or doing anything with Dialer he freezes and after that system just reboots. I've installed last version of CWM, updated SuperSu, installed Pa full version of GAPPS.
Hello to everyone, posting this here as I don't have access to ask in the forum post for BlissPop - I.E fresh user
I'm having issues with my "recalled" shield tablet (wifi), I had it flashed to BlissPop successfully previously but when I tried reflashing it the other day I was met with a major roadbump: It just won't load the ROM.
The tablet freezes at the screen following the installing and optimization of each application - basically my screen is stuck at a small wall of text saying the following:
"BlissPop is starting...
Powered by Team Bliss
Starting apps.
Please wait for the optimization process to finish."
And before you ask, yes I have waited long enough (left it on through the night just to be sure - this thing won't load).
My procedure is as follows.
Bootloader is CWM and it is rooted beforehand.
1st off going into recovery mode.
#2 Wipe data/cache/dalvik cache - done
#3 Installed BlissPop via sideload, then gapps_pico afterwards (I've tried wiping cache+dalvik before installing gapps to no help.)
#4 Rebooting from CWM, here I've tried both allowing and denying CWM to "fix" root settings.
I've tried the first ROM I installed (when wifi/lte versions were available) and the newer releases - same problem with both.
After this I am met with this screen that won't budge, anyone got a possible solution to this issue?
Hey I just received my replacement tablet and was going through this process too. I did some digging around and found / remembered that having an external SD card socketed can cause this problem. So I powered my device off, removed the card and then rebooted without major issue.
Hope this helps.
I don't have any SD card in my tablet though, thanks anyways.
Did you format system?
If not then do format system/data/cache
Sent from my P4S using Tapatalk
Tried doing a format of system as well as data/cache/dalvik, still getting same result :/
Not sure its still helpful or not...i saw the xda thread regarding to this thread and whoever tried to flash the last zip got stuck at boot. So I'm guessing if you will flash a different one (by this time maybe they upload a new one) maybe you could get rid of it..
Sent from my P4S using Tapatalk
When I switched to BlissPop I had to format /data because TWRP was unable to wipe it. TWRP offers that option unter "advanced wipe". Might be the same with CWM.
any help my phone stuck on this boot loop and i dont know what to do now , any fix ? i dont wanna have broken phone i did everything that u guys said nothing works