I'm running a B90 TF101 and I run CM9. I tried a few other ROMs and decided to go back to CM9, so I used CWM to restore one of my backups. Problem is, now my installation does not see the internal memory (the one it thinks is the sd card), so I cannot get at my backups or use ROM Manager (because it requires an SD card to be mounted).
However, my card does seem to be mounted in the usual places (/sdcard, /storage, etc.) so I cannot figure out why it's not seeing it, and I need it mounted to do anything useful on my tablet.
I did read of a bug in CM9 where we need to create certain directories (/Removable) on each boot, but the script provided didn't seem to make a difference, so I'm a little lost at the moment about how to fix this. Can anyone suggest any articles/posts/info, or give me some advice on this?
Hi,
Sorry, but it is not the bootloop issue. I've had (and solved) that problem several times before, with the exact solution you detailed below. It is something else, because I am able to boot into Android, but not able to see the internal storage memory.
guiloma said:
Hi, i think i might help you. I've just solved this issue(i think). Do you have the recovery bootloop problem?(this means the only way to get into the ROM is pressing PWR+VolDown and Cold Boot). That was my case, and i wasn't able to access de sdcard from the ROM, althought a can access it through ADB. If thats your case, next lines can be helpful.
I just applied the the fix for the recovery loop fix and i get it solved.(You can find this fix on several forums)
(Through ADB)
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
I think this may be related with "forcing" the deviced to coldbot, not exiting properly from CWM Recovery. I hope this helps you!
P.D.: I apologize for my english, i've done my best to get undestood
Click to expand...
Click to collapse
Well, if I find out, I'll post it here (unless someone else has a solution)
guiloma said:
Sorry it didn't help. That worked for me. I still think that the issue must be somehow related to a previous uncorrect dismount of the storage, or something similar. I hope you can sort it out!.
Click to expand...
Click to collapse
lingh said:
Well, if I find out, I'll post it here (unless someone else has a solution)
Click to expand...
Click to collapse
Same thing happened to me today after trying the official CM10 nightly and then trying to revert to an AOKP (ICS) nandroid. Did you try a JB ROM and then try to go back to ICS?
I read in the CM10 preview thread that nandroid backups don't include kernels (which was a surprise to me)...I'd suggest either reflashing the ROM that you're trying to use over itself (immediately after restoring your backup), or just reflashing the kernel itself (if you were using a custom one). I reflashed guevor's kernel after my nandroid restore and that fixed the problem for me. Reflashing the entire ROM should maintain your data/settings and also include the kernel.
My guess is that options or mount points for the internal storage are just not compatible between ICS and JB.
Yes, I tried CM10 preview, then tried to revert to my CM9 CWM backup. And reflashing CM9 did not work. I have had to flash Android Revolution to get my system workable again.
buck2202 said:
Same thing happened to me today after trying the official CM10 nightly and then trying to revert to an AOKP (ICS) nandroid. Did you try a JB ROM and then try to go back to ICS?
I read in the CM10 preview thread that nandroid backups don't include kernels (which was a surprise to me)...I'd suggest either reflashing the ROM that you're trying to use over itself (immediately after restoring your backup), or just reflashing the kernel itself (if you were using a custom one). I reflashed guevor's kernel after my nandroid restore and that fixed the problem for me. Reflashing the entire ROM should maintain your data/settings and also include the kernel.
My guess is that options or mount points for the internal storage are just not compatible between ICS and JB.
Click to expand...
Click to collapse
guiloma said:
Hi, i think i might help you. I've just solved this issue(i think). Do you have the recovery bootloop problem?(this means the only way to get into the ROM is pressing PWR+VolDown and Cold Boot). That was my case, and i wasn't able to access de sdcard from the ROM, althought a can access it through ADB. If thats your case, next lines can be helpful.
I just applied the the fix for the recovery loop fix and i get it solved.(You can find this fix on several forums)
(Through ADB)
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
reboot
I think this may be related with "forcing" the deviced to coldbot, not exiting properly from CWM Recovery. I hope this helps you!
P.D.: I apologize for my english, i've done my best to get undestood
Click to expand...
Click to collapse
Dude you Rock! Fixed my problem
Alright, problem fixed, but it took a lot of work.
What I did first is downloaded and flashed Android Revolution for my TF101 (link on these forums), then, after verifying it picked up my storage correctly, I downloaded and installed SuperSU, ROM Manager and ROM Manager Premium (the last I had paid for previously anyway).
I downloaded via the manager the CGM 10 Nightly for my TF101 (I guess this would also work with CGM 9 Nightly, RC or Full Release)
I opted to Backup the current rom, clear the Dalvik cache and also to wipe system and data and let it do its work. And bingo, it booted into CGM with a working internal storage, and also on JB now, since this is the CGM10 nightly which uses JB instead of ICS as base.
Related
I have tried, through Clockwork Recovery, to flash several ROMs and kernels.
I tried a Tiamat ROM. Looked promising. After flashing it and rebooting, the screen showed the proper custom boot animation and then it went into Honeycomb. Everything was the same as before. Looking in system information, it still says that I'm on stock 3.1 and using the stock kernel. I tried the Tiamat kernel and the Blue ROM, same thing, it just never changes anything except the boot animation.
Troubleshooting I've done:
Tried to flash it with older versions of CW recovery
Tried to flash it through ROM manager
Anybody know why it's doing this ****? It's rooted 3.1.
How did you root?
I used this
http://forum.xda-developers.com/showthread.php?t=1073884
I can confirm that the root is working perfectly fine.
Do you have access to your external SD card from honeycomb os?
The U.S. 3.1 doesn't work with MicroSD cards...does it?
EDIT: Nope, it doesn't work still. Just tested.
Do you have superuser? If not, you may want to reroot again. Something, may not have worked properly the first time.
cam30era said:
Do you have superuser? If not, you may want to reroot again. Something, ay not have worked properly the first time.
Click to expand...
Click to collapse
Yep, I got superuser. ROM Manager even makes Superuser ask for root privileges before rebooting to flash, so I know that the root method I know isn't the issue.
I'm having the same problem.
I tried flashing the kernel, ROM, anything - it won't work. It just boots back to stock. But now I have a problem my wifi has an error.
Arrgh! The problem is RomManager's CWM. You actually CAN get it to flash things if you go into "mounts and storage" and mount /system and /data and all of that but DON'T. It will not work out well because it can not properly wipe system and you will wind up with a wifi kernel version mismatch (which will display as "wifi error" in settings). You need to flash the Tiamat CWM recovery from fastboot. I detailed the process for another person in this thread:
http://forum.xda-developers.com/showthread.php?t=1152121
Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo
By the way, you will have to do a full wipe of ALL of your internal storage (so make a backup on your computer) and flash the ROM from an SD card.
Sent from my Xoom using Tapatalk
mikeserv said:
Arrgh! The problem is RomManager's CWM. You actually CAN get it to flash things if you go into "mounts and storage" and mount /system and /data and all of that but DON'T. It will not work out well because it can not properly wipe system and you will wind up with a wifi kernel version mismatch (which will display as "wifi error" in settings). You need to flash the Tiamat CWM recovery from fastboot. I detailed the process for another person in this thread:
http://forum.xda-developers.com/showthread.php?t=1152121
Relock US Xoom Tiamat 1.4.4 resulted in hanging at Motorola logo
By the way, you will have to do a full wipe of ALL of your internal storage (so make a backup on your computer) and flash the ROM from an SD card.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Thanks mikeserv, I'm so glad you are helping people who get snagged by that CWM recovery. It was a nightmare, and I've on a tear about it.
Hello,
I had the official version of ICS on my TF101 (the one with the locked bootloader).
I root, installed rom manager and flash recovery(5.5.0.4) -> backup performed.
Everything was perfect, however I wanted to try CM9 nightly build, I could install it without problem.
The CM9 wifi working on but the rom is not the most stable I wanted to go over the official thanks to my backup.
I ended up with the stock rom official ICS, but not enable the wifi. So I went back on the CM9, and there the WiFi working. I install the Revolution HD and the wifi does not work.
Back on my backup ICS official and still no wifi.
Have you an idea of where this might come?
Thank you in advance.
PS: After the installation of my CM9, my tf101 boot automatically on the recovery, forced to make a cold-booting android to begin.
I think the reboot into recovery thing is a bug that I've read some people have. I personally went back to the Rogue recovery after noticing that 5.5.0.4 didn't have option to access external SD.
Wifi...well...not too sure about that problem. Try to reflash the stock ICS rom back over on top of your backup. CWM is not the most reliable recovery, IMO.
Why don't you try Revolver. I bet that you'd stay on that rom. Oh...and pick up the superwipe lite script from the revolution thread if you haven't already. Good to use when you are swapping roms.
If you are restoring a nandroid, it is normal because nandroid doesn't restore the kernel, so you have to install the rom you want then restore the nandroid.
If you want to use CM9, use the one in my signature. Everything is working.
ricardopvz said:
If you are restoring a nandroid, it is normal because nandroid doesn't restore the kernel, so you have to install the rom you want then restore the nandroid.
If you want to use CM9, use the one in my signature. Everything is working.
Click to expand...
Click to collapse
is that this version of cm9 allows the AZERTY dock keyboard ?
when I install the Revolution HD and the official zip from asus there is still no wifi. there isn't kernel with this method ?
SiNJiN76 said:
I think the reboot into recovery thing is a bug that I've read some people have. I personally went back to the Rogue recovery after noticing that 5.5.0.4 didn't have option to access external SD.
Click to expand...
Click to collapse
I tried to install another recovery by the cwm recovery (flash zip), the install works, but i still have the cwm recovery.
SiNJiN76 said:
I think the reboot into recovery thing is a bug that I've read some people have. I personally went back to the Rogue recovery after noticing that 5.5.0.4 didn't have option to access external SD.
Click to expand...
Click to collapse
Reboot to recovery is a issue present in all aosp roms except mine
zulfurion said:
is that this version of cm9 allows the AZERTY dock keyboard ?
when I install the Revolution HD and the official zip from asus there is still no wifi. there isn't kernel with this method ?
Click to expand...
Click to collapse
Well, it supports more keyboard languages than english, so it should work.
If you want to go back to asus based rom, you must wipe, install the rom you want, boot it and then restore nandroid if you have one
ricardopvz said:
If you want to go back to asus based rom, you must wipe, install the rom you want, boot it and then restore nandroid if you have one
Click to expand...
Click to collapse
I think I already did. But I will still check tonight
thank you
ricardopvz said:
If you want to go back to asus based rom, you must wipe, install the rom you want, boot it and then restore nandroid if you have one
Click to expand...
Click to collapse
Still no wifi
zulfurion said:
Still no wifi
Click to expand...
Click to collapse
What is the problem? Wifi doesn't turn on? your network doesn't show up? you can't connect to your network?
You can always try other roms and see if wifi works. but if you have a dock i recommend to use my CM9 build which has working dock battery
wifi doesn't turn on. Block on "wifi activation..."
Same problem with the Revolver 4
It works with another recovery.
Sorry for my noobness, and thank you for your help.
Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab
ihabelnaccash said:
Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab
Click to expand...
Click to collapse
Hi there,
I recently experienced the same thing, and it was a hassle to fix--but I have got my phone working each time. The downside being that I /had/ to switch over to Odin. Mind you, I am not necessarily experienced with Android, so I can't really say that this is the only way.
At any rate, here's what I did to get it back to normal:
Load up Odin
Put it in download mode -- I assume you know to hold the volume keys and then plug in the USB.
Flash either the ICS leak or the stock 2.3.5 Gingerbread.
You should be back to good. I hope you backed everything up in either Kies or some other resource...else you're in for a hell of a time setting stuff up.
Oh: bad news about the 2.3.5 stock is that, as far as I can tell, you're unable to upgrade to 2.3.6. In turn, you're then unable to update to the official ICS through Kies or OTA. I assume you don't mind, considering you're trying to flash a new rom anyway.
Anyway, I do hope there is some bit of clarity on getting CM9 on the Skyrocket. As of now I have still been unable to do it. Just as you, no matter the settings I try, I end up being stuck at that screen. The only difference between your method and mine is that I completely did mine through CWM...nothing through ROM Manager. (Actually, I believe I tried a few differing methods involving the CWM touch and non-touch...followed many different guides but still no good.)
Hope you get it back to a functioning state. If you get CM9 working on the Skyrocket, I'd appreciate you sending a bit of details on how to do so.
EDIT: I am now on CM9. Through magic, ponies and friendship I have failed to accomplish this feat. But by pure science and the blood of a pony, I have successfully installed CM9.
After you've restored to 2.3.5 or the ICS leak (the one I was on), do the following:
- Grab the recovery-clockwork-touch U27 described below. Flash it.
- Download both the newest CM9 build from their website, as well as Google Apps, and then copy those to your external SD.
- Follow this guide: http://www.teamchopsticks.org/p/install-guide.html. Here's what's relevant to you:
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the CM9 zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
Click to expand...
Click to collapse
After ~10 minutes you should be fine. Mine took less, but I'd bet it could take longer. Please follow those directions above EXACTLY. I'll be happy to help you in any way I can if you reply to this thread/ send me a PM.
When I softbricked with the latest CWM I wasn't able to return back since it wouldnt detect my SDcard so I just loaded up odin and used recovery-clockwork-touch-5.8.1.3-hercules.tar and was able to read my SDcard again which had all my backups and CM9 files. I have flashed every version of CM9 every since and still using this CWM version and havent had any problems. :good:
All better now- I used ODIN to restore to stock, then used it again to put CWM (non-touch) back on, then added superuser, then just did a restore from SDcard! Muchas Gracias all!
Should I be able to then use a restore of when I had a working CM9 (and backed up with CWM)? Or would I have to do all the cache wiping/ factory reset like I did to install it the first time before using such a recovery? (and I will try that recovery- clockwork touch hercules... latrer tonight from home)
ODIN tar to restore back to factory. I got the boot loop too. Only until after I flashed CM9 then flashed dark side wipe cache only would CM9 work for me. Only on regular CWM though. Try and give that a go.
Sent from my SAMSUNG-SGH-I727
Every time I try to flash something my tablet fails, and I have to revert back my backup. It doesn't matter if I download on PC or from the tablet itself. HELP!!!!
Galaxy Tab 2 7.0
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
bill_in_mtl said:
Can you post what rom you are using right now, as well as what recovery version.
Also, what rom are you trying to flash ? You are rooted, right ?
If you can post some more details - am sure people will chime in
Good luck,
Click to expand...
Click to collapse
I'm running stock 4.0.4, Rooted, Clockworkmod recovery. I have tried to flash several different roms. Romswell, AOKP, CM nightlies thru ROM manager. all of them fail in recovery. I flash stuff all the time on my SIII so I'm not really a Noob to flashing and what not, but I can't figure this one out. Thanks for any help.
What are you using for recovery? When you say failed what is the error message? Sounds like you should prolly reflash a current official recovery. If by failing you mean it hangs on first boot then your not wiping system before flashing. Factory reset and wipe system before you flash.
Are you by chance running any scripts for sd card swap, etc ?
I am running this script, http://forum.xda-developers.com/showthread.php?t=1961097 which swaps my 32GB external sd for the internal sd, which runs great - no issues, except with rom manager and flashing from recovery.
I have to go back and de-activate the script, reboot, and then dowload - or transfer file from PC, and it flashes without issue
Otherwise, I have had no flashing issues of any kind - using CWM 6.0.1.5 for the p3113
Good luck,
Bill
I have two problems right now. First, I have an encrypted TF700t. I went through each step successfully to load this ROM:
[ROM]★★★[TF700 KitKat 4.4.4][CROMBi-kk][F2FS | DATA2SD | ROM2SD | CM11][July 19]★★★
I unlocked the bootloader, no problem. Relaoded and used stock Android. I then installed TWRP, again no problem. Again reloaded and used stock android, no issues. I could open TWRP, put in my decrypt password, and everything was going fine. I loaded up the above ROM, and got to the point where I was going to put in my Google info, and it hung at "turning on wifi." I skipped that step, and got into settings to turn it on that way, but no joy. No problem, I'll just re-flash the ROM and try again, and if that doesn't work, I'll try a different kernel. The problem is now, TWRP doesn't accept my password. So I have no access to my internal SD card. I loaded android back up and changed the encryption password, but that didnt word. I reflashed TWRP through ADB, but that didn't work either.
So, does anybody have any suggestions as to how I can either 1) get my wifi turned on, or 2) fix my encryption issue?
Thanks
Quick thought - does anybody know if I will cause any issues by flashing CWM over TWRP? I would like to try to reinstall the ROM through CWM and see if that works since I cant do it through TWRP right now.
DropKickedMurphy said:
Quick thought - does anybody know if I will cause any issues by flashing CWM over TWRP? I would like to try to reinstall the ROM through CWM and see if that works since I cant do it through TWRP right now.
Click to expand...
Click to collapse
Why would you not post this in the Q&A section for our rom ?
Because I'm blind.
Sorry about that - reposted in the correct place.
Thanks