I've spent a good 50 hours trying to install scott.hart.bti's unofficial CyanogenMod 10.1 (JellyBean 4.2.1) on my Samsung Infuse 4G (SGH-I997), and have come up against nearly every conceivable problem. Today's problem is the fact that, after going through the scores of steps to finally get to the point to install CM10.1, my phone only boots into ClockworkMod Recovery whenever I turn it on. I've scoured these and other forums for hours trying to solve this, and I've had no luck. Any help would be greeeeatly appreciated.
Here's what I've done so far, if I remember correctly. I started out with stock Froyo on the Infuse.
I successfully rooted my phone with SuperOneClick.
I found out I have to install Gingerbread first. After having no luck with Heimdall (not exactly "one click"), I installed jscott30's UCLB3, option D using ODIN. It comes with Entropy's Daily Driver kernel and red CWM Recovery. I installed the corresponding gapps too.
Before I could install a JellyBean ROM, I had to install an ICS one. Entropy512's unofficial CM9 was recommended, so I installed the latest build of that, following the instructions for installing from Gingerbread with red CWM. I installed the recommended gapps along with it. I also did the recommended wipes before this installation.
I ended up with the scrambled rainbow start screen or whatever people call it. Apparently I have to have Gingerbread bootloaders and those didn't come with the GB ROM, so I installed those via ODIN.
I got CM9 to work.
I transferred over the zip files for the CM10.1 ROM and put them in /sdcard/.
Lots of wipes: wipe data/factory reset, wipe cache partition, format /system, wipe dalvik.
I installed the CM10.1 ROM, and then scott.hart.bti's modified gapps, using CWM.
I tried to reboot the phone. It rebooted into CWM, the same CWM I used to supposedly install CM10.1. Now, whenever I reboot or turn the phone on (by whatever method - removing battery, USB cord, holding power button, selecting "reboot system now" in CWM), it goes directly to CWM.
One, of many, points of confusion is the different CWMs. How do I tell what's a red CWM and a blue CWM? When I Google that, all that comes up is posts from this and other forums of people yelling at the poster to Google it. See the problem here? The CWM Recovery that I used to install CM10.1, is titled "CWM-based Recovery v6.0.2.7". It has a blue menu with a grey background.
Where did I go wrong? Anything remotely applicable that I read seems to be for a different phone, so I'm unsure what to believe. Here are some of the explanations / solutions recommended for similar problems on other phones.
Install a different type of recovery (recommended here, as well as several other places). But everything I find about installing different recovery software involves using ROM Manager (which I can't access and which doesn't work anyway), using Heimdall (which I couldn't get to work), or installing one of the ROMs I already installed. TWRP was recommended, but not for my phone specifically, plus I read here that it doesn't work with MTD JellyBean, which I think is what CM10.1 is. Everything seems to require going back to stock Gingerbread, which is where I started, so I'd still end up having to then install CM9 and run into the same problems. Is it this? Which recovery should I install, and how?
Someone else said here that "The ICS ROMS were built for safestrap now bootstrap (CWM). It does that because it was flashed using CWM." Is this just referring to some other ROM? Everything/everyone else says to do everything with CWM.
A couple posts (here and here) recommend some shell commands involving /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4, respectively. I'm hesitant to try these because they're for different phones, they themselves refer to different blocks, and it seems like the type of thing that could really mess up my phone.
I just flashed with a Heimdall One-Click ICS Recovery found here. My phone is still only booting into recovery, but this time it's "CWM-based Recovery v5.5.0.4" with a blue menu and a black background. At the bottom of the screen, it shows the following errors, which I suspect are just because I cleared the cache before, but I'll include for completeness:
Code:
E:Can't mount /cache/recovery/command
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
I'm clearly quite the noob, especially in comparison to all of you, so please save me with your endless expertise! Do I install a new recovery? If so, how? I have a new recovery now (just a different version of CWM). Is there some problem with a boot file or bootloader? Is it a kernel issue? Insert other clueless jargon-filled question here? Endless thanks in advance.
Before you flash 10.1, flash CM 10. Sometimes the phones can be finicky. I solved a similar problem by using this method.
Sent from my SGH-I997 using xda app-developers app
What CM10?
trej3k said:
Before you flash 10.1, flash CM 10. Sometimes the phones can be finicky. I solved a similar problem by using this method.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Okay, so I've started again from stock Gingerbread. What CM 10 are you talking about, though? I was only able to find CM 10.1 for Infuse. What CM 10 did you install? Are you referring to scott.hart.bti's BeanStalk build?
Fixed, I think
I think I have it working now. I have no idea what the problem was. I just started over again from the beginning. Jesus Christ was this complicated. I don't know how you guys make this stuff; it's hard enough to just install! Thanks for your help.
Glad you got it working. I try to always flash
In order ( stock, cm9, cm10, cm10.1) cm10 is right under the cm10.1 link in the 10.1 thread. Again, glad you got it up & running! :thumbup:
Sent from my SGH-I997 using xda app-developers app
Related
I am lost.
I had FireFly 2.05 on my SGS (ATT US version) and was going to update to 2.1. I followed the procedure as I aways do; ODIN 1 click to stock rom, master clear, copy update.zip and rom file and reboot into recovery. This time however I get the following error
E:Can't symlink /system/xbin/su SYSTEM:bin/su
E:Failure at line 14
I checked some notes on this and found out that it might be a currupt file. So I re-downloaded FireFly2.1 again and transfered the file to the internal SD card. The outcome was the same.
Then I copied the original 2.05 version back which I know was fine and I still get the same error. Even after a full stock 1-click and master clear the above error will not go away.
Is my internal SD card messed up? Or am I missing something else?
It's running stock right now and all seems to work fine, but I cannot stand all the bloatware and other crap ATT puts on the phone and really want to try FireFly2.1.
Any help is greatly appreciated.
Thanks.
Did you flash clockwork recovery
Did you root the phone after you flashed back to stock?
Sent from my SAMSUNG-SGH-I897 using XDA App
Agree with DaveyBB - sounds like you are not rooted.
Sent from my SAMSUNG-SGH-I897 using XDA App
You do not need to root on stock just flash clockwork with update zip
The update.zip i use is the current clockwork recovery.
I boot into the stock e2 recovery, then apply cw recovery and update the rom. Never had to root stock before when i update via cw recovery.
I will try to root stock first this time and then apply rom via recovery.
Thx
Sent from my SAMSUNG-SGH-I897 using XDA App
anosis said:
The update.zip i use is the current clockwork recovery.
I boot into the stock e2 recovery, then apply cw recovery and update the rom. Never had to root stock before when i update via cw recovery.
I will try to root stock first this time and then apply rom via recovery.
Thx
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
To install clockwork select reinstall packages twice
The issue is not with cw recovery. I am already in it, but the error that i get is after i click "yes apply this zip"... The script starts to format the system, data, datadata, etc. And then this error shows up after files ate copied
Sent from my SAMSUNG-SGH-I897 using XDA App
Have you tried re download of rom package?
My only guess is that clockwork and the rom are not working well. I would try downloading a different clockwork
Sent from my SAMSUNG-SGH-I897 using XDA App
mcord11758 said:
Have you tried re download of rom package?
Click to expand...
Click to collapse
Done that too.
So just to reiterate...
I had FireFly2.05 running and many other cooked Android 2.1 and 2.2 roms before this. I follow the instrution of the cooks to the 't' on how to update to the newest rom and never had any issue.
This time I downloaded FireFly2.1 and also Phoenix4.5 from the respective cooks and followed the instructions as usual. The issues does not show up until the 'copy files' part of the script is running (formating of the filesystem already passed).
All I can imagine are these:
1) The transfer from the PC to the Phone is corrupt (ruled out the download from the net as even the existing FireFly2.05 rom no longer loads)
2) The internal SD card is messes up
3) There is some configuration change I am not aware off that prevents the install of the cooked rom.
Maybe try to reformat sd through clockwork
Problem solved, kind of.
My desktop PC, which I always use to transfer the files is somehow responsible for the error I get in CWM recovery. I ended up using my laptop to transfer the ROM to the phone and it worked again.
Something is messing up the USB transfer? That seems very odd but I am glad it's not the phone that caused the issue.
If I find out what the issue is with my Desktop I will post again just in case this rather rare issue might happen to someone else.
anosis said:
Done that too.
So just to reiterate...
I had FireFly2.05 running and many other cooked Android 2.1 and 2.2 roms before this. I follow the instrution of the cooks to the 't' on how to update to the newest rom and never had any issue.
This time I downloaded FireFly2.1 and also Phoenix4.5 from the respective cooks and followed the instructions as usual. The issues does not show up until the 'copy files' part of the script is running (formating of the filesystem already passed).
All I can imagine are these:
1) The transfer from the PC to the Phone is corrupt (ruled out the download from the net as even the existing FireFly2.05 rom no longer loads)
2) The internal SD card is messes up
3) There is some configuration change I am not aware off that prevents the install of the cooked rom.
Click to expand...
Click to collapse
One Question:
What method are you using to enter recovery method when you attempt to flash the rom? And what color is your recovery menu (should be green)?
(Don't go into recovery via rom manager. Try entering recovery via your advanced power menu)
bames said:
One Question:
What method are you using to enter recovery method when you attempt to flash the rom? And what color is your recovery menu (should be green)?
(Don't go into recovery via rom manager. Try entering recovery via your advanced power menu)
Click to expand...
Click to collapse
I don't think he's getting into Clockwork via ROM Manager, as he's said multiple times he's using the CWM update.zip; reinstalling packages in 2e recovery to get to CWM.
He's also said he doesn't believe this to be an issue with Clockwork (and I don't either). And I'm also pretty sure we're not dealing with newbie mistakes of Android Recovery vs. Clockwork Recovery.
any chance you're leaving your usb plugged into your cappy while you're trying to flash it?
I can flash clockworks recovery through adb and can get in but I'm getting some errors:
E: Can't find misc
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
And a bunch few more which seem to repeat
I also tried to run the restore to stock from here but get an error right when I have to click to write the image.
When I just boot all I see is the unlocked lock and google. It used to boot into storage so I can mount it but not anymore. The only thing I have on the SD is the super user app, Netarchy kernel for 4G, CM7 latest stable for NS and thats it.
Need help
I can push something to the phone through the sdk but I don't know how to mount the sd card to do it.
ufff.... nevermind. I tried the factory restore one more time on another machine 32 bit and it works. It's restoring the image again. Will be locked again so I'll have to try again tomorrow. But the steps on rooting the NS4G don't really work well.
There is a bunch of stuff missing. Like the recovery gets overwritten each time. There are some links missing and dead.
Someone should fix that before we brick some phones.
OK, it restored but only gave me the sd card mount thing. I tried going back to fastboot and unlocked was still there. So I flashed recovery again and wanted to see if I can put the stock rom for 4G from here on it.
No go. I get:
assert failed: write_raw_image("/tmp/netharchy.img", "boot")
Installation aborted.
Help
ok, I'm not sure what ROM I have but I unplugged the cable and bam... sign in screen came in so I'm sighing in. Once I can get to the main menu I'll check versions and kernel but it looks like I have root. It's just that recover is not working well. I have 3.0.0.5. should I get a different one?
OK, I restored again because wifi didn't work. I think it was because I was trying to flash after the first restore and it wouldn't take. So now I checked and the lock when I boot showes up as unlocked but none of the root apps work so I don't think I have root. Not sure.
I also have to figure out what's up with that recovery. I know I need to rename the original so it doesn't flash it every time on boot but I think I need a new version. Anyone know which one is the latest and which one works on NS4G?
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
I think that's backwards. Roms might be compatible but kernels which these roms come with are not. So I believe that it I just flash netarchys kernel which now supports NS4G all should work ok.
Like I said, I'm back to stock and all looks like exactly like it was before ie. no root but the weird part is that fast boot menu says "unlocked". And I also get the lock which looks unlocked with the google sign during boot.
So how is that possible? Anyone?
When trying any app with root it tels me it has no access or it failed. Ie, su cmd says access denied.
BTW, why you attached two files? What is the difference between the two?
herbthehammer said:
3005 is the problem. Use 3024. I don't know for sure but are you absolutely sure cm7 is compatible with the ns4g? Isn't a lot of stuff still not working? Isn't 4g still not working? If flashing the wrong rom is what happened here then this problem isn't going away. Many people are doing this and almost bricking their phones. I read one post recently that pointed to a doc that said the gsm and cdma are two separate versions of the same os. I thought I read something that said kernels might be cross compatible but roms aren't yet.
Here are the correct recovery files for the ns4g
I think I remember seeing recovery ***** about cache when I was nandroid for the first time. I think after that I chose factory reset and clear dalvik and some other cache and might have rebooted then came back and flashed cwm again and tried nandroid and it worked that time. This was the very last step for me after I had managed to get the su file to the root of the card, flashed it in cwm, rebooted and changed the filename of the script to check and reinstall stock recovery in system/etc. I forget the name but it was a .sh file. It's name was in the guides somewhere...
Click to expand...
Click to collapse
Thanks for your help. I'm rooted and recovery is sticking ok. It was the old recovery. As soon as I flashed it all was good.
One is stock and the other is cwm that works with the ns4g. It wouldn't hurt to have the stock laying around. There might be a time when you need it.
Thanks for the stock recovery.
Sent from my Nexus S 4G using XDA App
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
Hi,
On my TF300T I flashed the CWM 5.5.0.4 using fastboot and installed CM 9.1 with the CWM - boots & works fine
I want to install CM10 or 10.1 (using the steps I found in the CM Wiki) but the TF300T always stops on "The Device is unlocked".
Now I found a new CWM (6.0.2.3, recovery-jb.img) for using with JB here at xda-developers - finally to install CM10 or 10.1.
But after flashing the recovery-jb.img with fastboot I want to boot into recovery mode, but the TF300T stops on "booting recovery kernel image".
A boot into the previous installed CM9.1 is still possible.
How can I upgrade to CM10 or CM10.1?
Thank you for any help!
cyaneo said:
Hi,
On my TF300T I flashed the CWM 5.5.0.4 using fastboot and installed CM 9.1 with the CWM - boots & works fine
I want to install CM10 or 10.1 (using the steps I found in the CM Wiki) but the TF300T always stops on "The Device is unlocked".
Now I found a new CWM (6.0.2.3, recovery-jb.img) for using with JB here at xda-developers - finally to install CM10 or 10.1.
But after flashing the recovery-jb.img with fastboot I want to boot into recovery mode, but the TF300T stops on "booting recovery kernel image".
A boot into the previous installed CM9.1 is still possible.
How can I upgrade to CM10 or CM10.1?
Thank you for any help!
Click to expand...
Click to collapse
What is your bootloader version? Si it fresh enough?
Bootloader...(!)
I was using ww_epad-9.4.3.30-20120604 - so I upgraded to stock ww_epad-user-10.4.2.20 (using CWM 5.5.0.4), after this I flas the recovery-jb.img (6.0.2.3) - now I can boot into CWM 6.0.2.3 recovery and install CM10. :laugh:
Thank you!
cyaneo said:
Bootloader...(!)
I was using ww_epad-9.4.3.30-20120604 - so I upgraded to stock ww_epad-user-10.4.2.20 (using CWM 5.5.0.4), after this I flas the recovery-jb.img (6.0.2.3) - now I can boot into CWM 6.0.2.3 recovery and install CM10. :laugh:
Thank you!
Click to expand...
Click to collapse
Yeap,.. Bloody bootloader
No problem
Sorry for reopening but - I's crazy!
Heres what I've tried (using Bootloader 1.00e (ww_epad-10.4.2.20-20121226 A03):
First flashing cm 6.0.2.3 and install cm10 and also tried the cm10.1 nightly. Installation works without errors, but on reboot the tf300 freeze on "the device is unlocked"
So I try it with twrp (2.4 jb). The installation of cm10 and also cm10.1 failed with the error "assert failed: getprop"
I also cannot mount /data, no matter what I try.
I've wiped data, cache and dalvik cache every time before I try to install one of the ROMs.
At this time I can do nothing with my TF300, only boot to cwm or twrp!
What the heck is wrong?
cyaneo said:
Sorry for reopening but - I's crazy!
Heres what I've tried (using Bootloader 1.00e (ww_epad-10.4.2.20-20121226 A03):
First flashing cm 6.0.2.3 and install cm10 and also tried the cm10.1 nightly. Installation works without errors, but on reboot the tf300 freeze on "the device is unlocked"
So I try it with twrp (2.4 jb). The installation of cm10 and also cm10.1 failed with the error "assert failed: getprop"
I also cannot mount /data, no matter what I try.
I've wiped data, cache and dalvik cache every time before I try to install one of the ROMs.
At this time I can do nothing with my TF300, only boot to cwm or twrp!
What the heck is wrong?
Click to expand...
Click to collapse
But U probably haven't format /system, right? It's another mandatory thing to do when switching roms.
If it fails, using fastboot try to flash system with original blob file (get it from archive of latest official release) - it will fix /data problem - been there, done that
U can also try to install official rom from zip... IF it fails, try fastboot method.
Let system boot, reboot into recovery again and do full wipe with /system format and install newest cm10.1
szulco said:
But U probably haven't format /system, right? It's another mandatory thing to do when switching roms.
If it fails, using fastboot try to flash system with original blob file (get it from archive of latest official release) - it will fix /data problem - been there, done that
U can also try to install official rom from zip... IF it fails, try fastboot method.
Let system boot, reboot into recovery again and do full wipe with /system format and install newest cm10.1
Click to expand...
Click to collapse
- now I formatted data and system and also wiped all possible parts
- flashing cwm 6.0.2.3 and installing asus stock ROM (ww_epad-user-10.4.2.20), reboot
- cannot access cwm recovery, so I reeflash it with fastboot method
- access cwm recovery and install latest 10.1 nightly, reboot, done.
Thank you so much!
I'm having the same issue.
I bought my TF300T when if first came out. I finally decided to play around with it.
I unlocked it with the Google Play app.
Used fastboot to push the latest ASUS JB4.2 firmware (US_V10.6.1.8)
My bootloader says: (1.00 e) released by "US_epad-10.6.1.8-20130225" A03
I rooted and installed TWRP v2.4.4.0
Everything is working fine for me and I have taken a solid backup, so I'm able to restore back to that when things fail.
I loved using CM7 on my phone, so I wanted to try CM10 on my tablet.
I have tried installing the stable CM 10.0, and I've tried all of the CM 10.1 Nightlies.
Every single time, the install goes perfectly fine, but when I reboot I just get the plain white Asus screen and then it freezes.
I have tried installing with and without installing the gapps.
Every time I install I do a Factory Reset, wipe the Cache, Dalvik Cache, and System. The only thing I didn't do is wipe Data as I'd prefer not to lose my files. (is that the problem, is the data-wipe required?)
Is there something obvious that I'm missing or a step I left out?
Any help would be greatly appreciated.
I tried doing it again with wiping all my data too...that didn't make a difference either. Still freezes on the white asus screen.
Hi, I just registered to reply, as seems noone did. And Ive been there myself, also with the 10.6.1.8 bootloader. Thats the issue. Cyanogenmod isnt compatible yet with the newest bootloader 10.6.1.8.
I hope it will in the future, Im awaiting it too. Until then I just rooted the stock rom, and using it that way. You could try the CROMI-X rom, but its also stock based, I havent tried it yet, maybe ill give the newest update a try (4.3) which will be available in a couple of days, as I really love their newest boot animation(wich I believe isnt included in the 4.2 version)
Till then, no Cyanogenmod for us with the newest bootloader.....also downgrading is not worth the risk if you ask me,,, even if its possible. So Ill wait for the Cyanogenmod team to update their version to ours.
Advice: dont mess with the bootloader nor the recovery img files. Always read carefully if you wanna change recovery if its compatible with your bootloader. If its not, and you flash it...tada....youre the owner of a cool and expensive brick. Dont wipe data in the bootloader, cuz as I understood reading posts here at xda, it will wipe your entire device, including bootloader...then your kinda screwed. So stick to what you have and let the devs do their work to update their roms for the 10.6.1.8 bootloader...MOST importantly, DONT store your device with the keyboard dock closed...(like a laptop)...your screen will crack eventually.I gathered this info on youtube as well as here, and Ive a friend, who was using the device with the dock till last month like that, had it from last august...result, screen cracked 3 weeks ago...its a design flaw in the transformers, the screen is under heavy pressure while in the keydock..I just got my dock last week,, Im storing it separately, and I never close it, only use it for typing, battery and usb.
im writing all this as I think I wont find this post again to reply if you read it.
So I rooted my brother's infuse 4G because it was slow as sin and needed A. a data/cache wipe and B, I wanted to give him Jellybean
I followed all the instructions I could; rooted, installed the modded 3e (or thought I did), got a CWM installed afterwards, and then set about installing first CM9 (as the Jellybean ROM post says I should) followed by the actual ROM and its Gapps. Well, I installed CM9 (although it seemed to take all of 30 seconds, rather fast...) when I tried to wipe data/factory reset, CWM froze. I rebooted and from then on I had it softbricked. Stuck booting at the samsung logo, and when I tried to return to the recovery, the recovery was a garbled mess that looked like a scrambled TV channel. I used Heimdall and did the one-click reset to stock, and here I am. The phone boots to stock just fine, but my recovery is still completely boned.
Do I re-root? How do I install CWM again without being able to install 3e? (can't install 3e without a working recovery in the first place, after all..)
One anomaly of note - when I was going about all this, booting the phone into recovery always got me 3e, even after installing CWM. I had to manually install CWM by using an update.zip and "reinstall packages" every time I wanted to use CWM. ROM manager would boot me to CWM, but it took several reboots and a flashable CWM zip before I could even get CWM installed in the first place - ROM manager refused to do it the easy way.
What did I do wrong, and more importantly, how do I get back on track? What do I do to put a fixed recovery back on this thing? Odin? ADB?
Today was the first time I ever used Heimdall, I've been a fair weather flasher since the beginning, I've never had to ADB or Odin.
It sounds like you didn't install cwm recovery properly, but I'm not sure I've never ran into this problem before. If you go here
http://forum.xda-developers.com/showthread.php?t=1524081 and carefully read over the first and second post you should end up with gb and red cwm recovery. The way I've done it was to put the phone in dl mode and flash the first package (the stock gingerbread att rom). After it is installed and booted up, I then power it off and go back into dl mode. Then flash the second package, which is just the kernel and red cwm recovery, (be patient because it takes awhile). Once that is done then go into recovery and wipe data/factory reset, wipe dalvik cache, wipe system, and install cm9. I think it only installs the kernel and recovery the first installation after formatting and creating the partitions, but after its done you have to go through the menus and tell it to reboot. After it reboots it will be stuck at the cyanogenmod galaxy s logo, so you will have to go into recovery once more. When you're there you should have blue cwm (only continue if you do) and install jb, without actually having to install the full cm9. When you navigate to which ever jb rom you want to install, a prompt will appear stating that there is incompatible partition layout and to confirm installation you will have to reselect the jb zip again to install. It will flash pretty quick because at this point its doing the same thing as when you went from gb to cm9 and only installs the kernel, recovery, and reformat/creates the partitions, (I think). It will reboot on its own but it will take you back into recovery. At this point all you have to do is navigate to the same jb zip you want to install and flash it, followed by gapps, and then reboot system. This process has worked for me but I highly recommend reading and following the instructions given in the post above.
Use goo.I'm app. Also you need to flash GB bootloaders in Odin . is recovery all colorful? If you see recovery fine just get goo app on play store and install a recovery
Sent from my SAMSUNG-SGH-I317 using Tapatalk
I would go the ODIN route, I have bricked so many times because i try to make the impossible possible. Just search for a already rooted pda,mdr file. I skipped the cm9 part idk if that would make things better or not but as my post says im a risk-taker
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
UnhoIy said:
One thing I'd like to point out, flashing to ICS from GB requires 2 flashes. First flash sets the new partitions. You reboot and pull the battery, then boot back into recovery and reflash with the gapps.
That was the first problem I saw, and now commenting while on the Nexus I can't see the OP so that's all I'll comment on.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
but if don't have any problems i'm good right or should i go back and do it
MajorLeagueROM said:
but if don't have any problems i'm good right or should i go back and do it
Click to expand...
Click to collapse
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
UnhoIy said:
I've never skipped ICS and gone straight to JB like you, that's risk I've yet taken. I guess if you've had no problem then you're good, but I've gone back to stock and to JB at least 12 times now and used the same process every time without a hitch. In the case of OPs problem, I would just go back to stock and try again. Although I always go back to 2.2 stock...
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
MajorLeagueROM said:
I'll just do it tonight then maybe my phone will run better, i thought i'd be a waste of time. thanks for the info
Click to expand...
Click to collapse
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
UnhoIy said:
Lucky me, I get to go back to stock tonight for soft-bricking for the first time having this phone. It's what I get for trying to port a ROM with only a nights worth of research.
Oh well.
Click to expand...
Click to collapse
lol it happens to the best of us