Database Users

CM9/CM10 UNOFFICIAL Ice Cream Sandwich/ Jelly Bean for Legend

Check progress in DEV section http://forum.xda-developers.com/showthread.php?t=1562595

( I have posted less than 10 posts, so I can't write in the dev section. )
Stupid question : is it using Holo?
And, if it is based on CM9, it is rooted, isn't it?
If WiFi works, I'm SURELY going to try this!

I installed it yesterday. Wifi works, it uses Holo, hat root and performs better than I expected.

Thx.
I' ve put it on. It's really laggy, but it works!
It's a good start, but if this is the best performance the legend can give, I think I won't ever change definitevly to ICS. Maybe it can be optimizated for the Legend hardware to become smoother.

Thanks for testing, but it has not got hardware acceleration yet. For testing purpose, you could overclock it up to 787 MHZ safely, and the overall performance get better notably.
/=\lex said:
Thx.
I' ve put it on. It's really laggy, but it works!
It's a good start, but if this is the best performance the legend can give, I think I won't ever change definitevly to ICS. Maybe it can be optimizated for the Legend hardware to become smoother.
Click to expand...
Click to collapse

Yea is pretty smooth overall eventhough hardware aceleration is not working, this port looks really promising,

Tried it yesterday and in My view its the smoothest ics ROM ever tested.i had some fcs but will try Tor correct rights via rommanager.if GPS is working i will use this one.its a must Have for me.
Sent from my Legend using XDA

Thanks for testing, but it has not got hardware acceleration yet. For testing purpose, you could overclock it up to 787 MHZ safely, and the overall performance get better notably.
Click to expand...
Click to collapse
I'll try keeping it on for more time. By my first impression, it doesn't look so buggy, I think it is also quite stable. I'll tell you if I find anything.
Anyway, this is a great ROM, thanks for your work!
EDIT : Stupid question : to install GApps I have to flash the zip, right?
EDIT 2x : Yea, it was a very stupid question. Flashed from clockwork recovery. Works perfectly.

Its getting better and better. but still GPS not working. Hope you get it fixed soon.
Realy great job!!!!!

really good job. Just need GPS and Camera.
Hoping for 2.5 soon...also hoping based on Android 4.0.4.

How is work going?
Sent from my Legend using XDA

I have a problem with the latest 3.0 version.
After i flash gapps i keep getting boot loops.
If i dont flash it and just flash the rom it boots fine.
Dont know what the problem is. Can someone help me?

I have the exact same problem as DareFace, but I think zeubea is aware of the problem.

zeubea-cm-9.0.0-ALPHA3.0.1 and Google Apps
I tried install this ROM multiple times today, everything works until i install gapps (full or tiny). After that phone enters infinite boot-loop (HTC logo on white background).
Radio 7.13.35.05
Bootloader HBOOT-1.01 (S-ON)
ClockworkMod Recovery 5.0.2.0
Edited @ 08:31PM GMT+2
After installing gapps over gapps works as a charm. That's weird...

I had the same bootloop problem until I installed another kernel that Zeubea provided. It's till get some fc's, mainly for clock and email, but the email still works, clock is inaccessible atm.
It's even better than cm 7.2RC1, running oc'ed at 787mhz ! It's so smooth and beautiful. Let's hope that the gps and camera will get fixed soon. If I had capabilities to donate, I so would do it.
Thanks Zeubea! The Legend community loves you, keep up the wonderful work of making our ICS dreams come true when htc can't and won't deliver.

The reason for bootlooping is the clock issue.
The default clock in 3.0.0 is 806MHz - something every Legend doesn't handle, so it bootloops.
The 3.0.1 version has this "problem" fixed.

I faced another issue releted to sounds. I change both ring and notification sounds and after some time i realise that they are reverted to default!

I have this weird thing where the danish keyboard force-closes.
It's everytime i type the word "lige". It doesn't do it with the english keyboard
I've tried to turn off the spelling correction, since it's in english, and there isn't a danish one, but it doesn't help.
Other than that it's great

bootlooping after flashing cm9 gapps, possible fix
boots up normally after flashing the zip in CWM, but after flashing gapps it bootloops, and after awhile of countless flashing i discovered it bootloops even before flashing gapps, so i tried different step to flash it and finally it boots up normally, here's what i did :
1) full wipe, dalvik cache and cache partition, factory reset
2) flash the main cm9 zip
3) full wipe, dalvik cache and cache partition, factory reset (again)
4) flash gapps (not tiny version)
5) reboot, if it boots up normally thats great, if not its ok, continue to step 6
6) boot into CWM
7) dont wipe or anything*
8) flash the main cm9 zip
9) instead of rebooting device, continue by just flashing gapps (not tiny version)
this were the steps i did to fix the bootloops after flashing gapps, apparently the gapps tiny version is not compatible with cm9 on the htc legend thats why i stick to the normal gapps file, i hope this helps anyone of u experiencing the bootloops after flashing gapps

I have some kind of problem with wifi connection. If "Keep Wi-Fi on during sleep" is set to "Only when plugged in". After I wake up phone wifi is turned on it cannot find any networks.
EDIT: Logcat trimmed to "network|wifi|power|conectivity" http://pastebin.com/pdUAbfDy
And terminal emulator displays an error "Unfortunately, Terminal Emulator has stopped" when I try to open it.
EDIT: Logcat http://pastebin.com/ChRUu3jS

Constant Reboots, Hanging and Annoying Me

Okay, so first off, I'm literally about to light this fking thing on fire.
This damn phone has been the death of me. I have a Tbolt and Galaxy Tab, and NEITHER have been as much of a pain in my ass.
This seems impossible because since I got the phone, I've had nothing but problems.
1. Unlocked bootloader via fastboot. K, done.
2. Flash AmonRa Recovery (I did this before AND after using CWM recovery, having custom rom, etc, it never worked) Always sat in a loop at the google X with unlock symbol, or just reboots into normal (and yes, the MD5s are correct) 3. I've had the phone get into the rom both with SIM and without, and randomly reboot, from using anything from market, to file explorer, to hitting the lock screen.
Honestly, I'm tempted to just sell it again (since I bought it off ebay) and buy something different, though that's a pain to do, and I need it for a trip to europe in a week, so I would love to have a phone I'm not pissed off at. And yea, already got mad enough I threw it.
I've literally spent HOURS looking through Google results on all the issues. And have YET to make this lil pos stable enough for me to use like I do my tbolt. nice 100 battery pulls. Seriously. Heeelllpp on this, :-/

hkbladelawhk said:
Okay, so first off, I'm literally about to light this fking thing on fire.
This damn phone has been the death of me. I have a Tbolt and Galaxy Tab, and NEITHER have been as much of a pain in my ass.
This seems impossible because since I got the phone, I've had nothing but problems.
1. Unlocked bootloader via fastboot. K, done.
2. Flash AmonRa Recovery (I did this before AND after using CWM recovery, having custom rom, etc, it never worked) Always sat in a loop at the google X with unlock symbol, or just reboots into normal (and yes, the MD5s are correct) 3. I've had the phone get into the rom both with SIM and without, and randomly reboot, from using anything from market, to file explorer, to hitting the lock screen.
Honestly, I'm tempted to just sell it again (since I bought it off ebay) and buy something different, though that's a pain to do, and I need it for a trip to europe in a week, so I would love to have a phone I'm not pissed off at. And yea, already got mad enough I threw it.
I've literally spent HOURS looking through Google results on all the issues. And have YET to make this lil pos stable enough for me to use like I do my tbolt. nice 100 battery pulls. Seriously. Heeelllpp on this, :-/
Click to expand...
Click to collapse
try
fastboot erase cache
fastboot erase userdata
fastboot erase system
and then flash via fastboot the AmonRa recovery again.
BTW, which ROM are you trying to flash? ICS or Gingerbread? And do you have Blackrose installed?

taodan said:
try
fastboot erase cache
fastboot erase userdata
fastboot erase system
and then flash via fastboot the AmonRa recovery again.
BTW, which ROM are you trying to flash? ICS or Gingerbread? And do you have Blackrose installed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=872441 << Flashed this.
So far, I've knocked my network to 2g and it's been fine. though not really much of a fix. And I had cleared all of the above using CWM prior to the attempted flash. I'd rather not have to wipe everything again just to get AmonRa. I've wiped quite a few times. Though did get something about /sd-ext missing when erasing via CWM. Also, I tried erasing recovery, and got this: "erasing 'recovery'... FAILED (remote: not allowed)". Not sure if that matters. Just seems that flashing via Fastboot has failed everytime. I flashed CWM via fastboot and that failed too, I ended up getting it working via RomManager.

I had the same problem. After i dropped my phone on the floor everything worked fine
Sent from my GT-I9001 using Tapatalk

jojogangsta said:
I had the same problem. After i dropped my phone on the floor everything worked fine
Sent from my GT-I9001 using Tapatalk
Click to expand...
Click to collapse
Yea, though I still feel like I'm getting intermittent reboots. IT's not an everyday use phone, so I'll have to see how it fares when I'm overseas.

flash 4ext touch via 4ext recovery control app
Then install a different rom like miui or cm7 or hypersense nova
Sent from my Nexus One using XDA

joelshawdow said:
flash 4ext touch via 4ext recovery control app
Then install a different rom like miui or cm7 or hypersense nova
Sent from my Nexus One using XDA
Click to expand...
Click to collapse
Done and done. Still have a problem with boot looping. Google X with vibration, then goes black and does it again, and it loops like that indefinitely. Though this isn't new, been since I unlocked it....POS.

Deleted

Leave it in a freezer for a day no joke
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P

First of all any ROM you find here for an update is going to have bugs. So have to prepared for reboots, and/or no boots.
On the other hand, you have to verify to see if you have any hardware issues. In order to do so, you have to flash to a stock ROM to see if the issue continues. If stock ROM is just fine, then its the custom ROM that is causing grief! So try another custom ROM, until the one that suits your needs.

my sugestion 2 u - use cm7.2. use 4ext touch recov, wipe all ur stuff, flash blackrose hboot with no repartitioning, flash cm7.2 rom, finally, stop b!tching!

ai6908 said:
First of all any ROM you find here for an update is going to have bugs. So have to prepared for reboots, and/or no boots.
On the other hand, you have to verify to see if you have any hardware issues. In order to do so, you have to flash to a stock ROM to see if the issue continues. If stock ROM is just fine, then its the custom ROM that is causing grief! So try another custom ROM, until the one that suits your needs.
Click to expand...
Click to collapse
Did it when it went back to stock. And Whoever said put it in the freezer, I did, and worked on it with AC on it, and it worked better . Though for some reason, never been able to flash recoveries via fastboot. Oh well. 4ext rocks.

hkbladelawhk said:
Did it when it went back to stock. And Whoever said put it in the freezer, I did, and worked on it with AC on it, and it worked better . Though for some reason, never been able to flash recoveries via fastboot. Oh well. 4ext rocks.
Click to expand...
Click to collapse
I never had any luck flashing recovery using fastboot either. Anyhow, it sounds like a motherboard issue to me. Sorry pal!

ai6908 said:
Anyhow, it sounds like a motherboard issue to me. Sorry pal!
Click to expand...
Click to collapse
This. The description fits overheating and overly sensitive to temperature CPU.

yon can flash another rom
yon can flash another rom

Still having bootup problems
Okay, sorry to bring this back up, but I am still having an issue with the phone booting. If I get the phone on, it's fine, doesn't randomly turn off or anything. However, if I try to reboot, power off and power back on for any reason....it becomes a pain to get back up and running. I usually have to do a couple battery pulls before it comes back up. Does the same thing. Hits the X, vibrates once like it's gonna turn on. Then a few seconds to a min later, goes black, then flashes the x and vibrates once again. It loops like this until I pull the battery and try again. Sometimes it takes a couple times to work. Its not the ROM either, because this is the issue I had when I first got the phone and did fastboot oem unlock. It would hang on stock. It's done it on all 3 ROMs I've tried. I don't wanna say fully it's a CPU issue, because I don't have issues once it's on.
Any new idears?
PS. I tried CM7, and I didn't like it. Not a fan of AOSP ironically enough.

The Nexus One will give off 7 Vibrations to indicate a hardware issue, we will just have to wait and see

New Xoom owner on the way :)

Well I'm coming over to the Xoom area now. Picked up two Xoom's (32 gb/WiFi) on Amazon for a good price and looking fwd to all the development you guys have going on over here. Currently been pretty hooked on my Razr w/ the latest round of soaks and OTA's for 4.0.4 along w/ the custom roms.
Right now just reading as much as I can so when both tabs get here on Tuesday I'll be ready to go, have all my files in place, etc.
I promise I won't ask any stupid questions in your guys' section w/ out searching, searching, searching!!!
Figure I'll run one stock 4.0.4 and the other w/ CM9 or EOS. Whichever I like better I'll put on the stock 4.0.4 and give to my g/f. As you can see I've had a variety of tabs/devices and always wanted a Xoom. Thought about getting some of the latest and greatest like the Excite or TF300 but I'm a sammy and moto fanboi and just can't bring myself to do it. I'd rather Moto give up on the Xyboard and release a front runner soon since Sammy looks like they have no intentions of going for performance, and instead focusing on price (ala Galaxy Tab 2, nothing wrong with that btw).

Hey young man
Nice to see another one coming to the dark... *cof**cof*... light side of the force lol
Just kidding... Anyway, if you want root I recommend my tool (LordAIOTool), as many people it's easy and good to do that kind of stuff on Xoom, one guy even mentioned it as "The Ultimate Xoom Tool". Hope you have fun here
Sent from my 3G Xoom using XDA HD - 1st Xoom Recognized Contributor

Well the first tab arrived and let my g/f have that one. Came from Amazon Warehouse and it was a used India Tab. Therefore got it to US 3.0 and then upgraded to 4.0.4 allowing system updates to run their course. I then unlocked and used your tool to root. Worked flawlessly. Thank you for that!
Then tried adb'ing both eos recovery and team rogue recovery. Both I'm having issues with. The issue is it will go to either recovery fine immediately after flashing. However if I let the tablet boot up or reboot and try to access recovery again, it goes back to the stock recovery. Either way I got EOS 2.0 Rom installed which is a lovely piece of work. Will probably run their nightlies when my Xoom gets here.
Just wish I could figure out that issue w/ returning to stock recovery. I've searched and searched and searched and no such luck. Doesn't matter much, I suppose, as my g/f doesn't like me messing with her devices and having to factory reset so I suppose I will leave it as is, for now.

got556 said:
Well the first tab arrived and let my g/f have that one. Came from Amazon Warehouse and it was a used India Tab. Therefore got it to US 3.0 and then upgraded to 4.0.4 allowing system updates to run their course. I then unlocked and used your tool to root. Worked flawlessly. Thank you for that!
Then tried adb'ing both eos recovery and team rogue recovery. Both I'm having issues with. The issue is it will go to either recovery fine immediately after flashing. However if I let the tablet boot up or reboot and try to access recovery again, it goes back to the stock recovery. Either way I got EOS 2.0 Rom installed which is a lovely piece of work. Will probably run their nightlies when my Xoom gets here.
Just wish I could figure out that issue w/ returning to stock recovery. I've searched and searched and searched and no such luck. Doesn't matter much, I suppose, as my g/f doesn't like me messing with her devices and having to factory reset so I suppose I will leave it as is, for now.
Click to expand...
Click to collapse
You don't want stock recovery on the Xoom...can't really do anything with it.

got556 said:
Well the first tab arrived and let my g/f have that one. Came from Amazon Warehouse and it was a used India Tab. Therefore got it to US 3.0 and then upgraded to 4.0.4 allowing system updates to run their course. I then unlocked and used your tool to root. Worked flawlessly. Thank you for that!
Then tried adb'ing both eos recovery and team rogue recovery. Both I'm having issues with. The issue is it will go to either recovery fine immediately after flashing. However if I let the tablet boot up or reboot and try to access recovery again, it goes back to the stock recovery. Either way I got EOS 2.0 Rom installed which is a lovely piece of work. Will probably run their nightlies when my Xoom gets here.
Just wish I could figure out that issue w/ returning to stock recovery. I've searched and searched and searched and no such luck. Doesn't matter much, I suppose, as my g/f doesn't like me messing with her devices and having to factory reset so I suppose I will leave it as is, for now.
Click to expand...
Click to collapse
adb'ing the recovery isn't the best way to go about it. Use fastboot (fastboot flash recovery recovery.img) should work fine.

What I'm saying is guys, I have added custom recoveries (by way of fastboot flashing the .img recovery file). Tried both Rogue and EOS recoveries. They work fine the first time I flash them, but then no matter if I try to use the hard buttons or just use commands to get into recovery it always reverts back to the stock recovery. (As in, dead android, red triangle, then I have to hit power + vol up which brings up stock recovery).
It's as if the custom recoveries aren't sticking.

With stock recovery, do you have the option , "install zip from sd card"?
If you do, I will send you a recovery zip, not image, to be installed from within recovery, not adb... let me know.
Sent from my MZ601 using Tapatalk 2

There you go, http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.zip
Just boot into your existing recovery,
Choose install zip from sd card and flash this.
If it doesn't work, I am afraid you need to to unlock your bootloader again and flash the recovery image again. If that is needed, will help you with steps. Try this first and let me know.
Good luck.
Sent from my MZ601 using Tapatalk 2

We're gtg all. Don't think I did anything different but Rogue recovery works every time now.
Thanks for all the help and suggestions! W/ being on EOS 2.0 my g/f has practically streamed Netflix non stop all day starting at 71% battery life and she just plugged the charger in a little bit ago. It was one of those lazy days and she's in the middle of a season on one of her shows.
Crazy good battery life.

got556 said:
We're gtg all. Don't think I did anything different but Rogue recovery works every time now.
Thanks for all the help and suggestions! W/ being on EOS 2.0 my g/f has practically streamed Netflix non stop all day starting at 71% battery life and she just plugged the charger in a little bit ago. It was one of those lazy days and she's in the middle of a season on one of her shows.
Crazy good battery life.
Click to expand...
Click to collapse
Oh yeah, and the wifi Xoom is slated to get the jelly bean os update next month! You really made a great choice!

How I almost made a brick

My 2 cents..
I was using ICSSGS from 1st RC. But it becomes very laggy after 3-4 weeks, so factory reset every month was necessary. I decided to change ROM.
I installed DOC's v12 ( I assume is is the same Doc that was cooking ROMs for my Omnia, and I was werry pleased with those ROMs). Did wipe, cleaned cache, cleaned Dalvik, formatted /system, flashed ROM, wipe again and it was working. But after two days it was still very laggy (talking about waiting for response for 3-5 seconds) so I wanted something faster. I had choose this Openkang milestone 6.
And then the fun begins.
Downloaded, copied to sd, booted to CWM, all wipes, flashed ROM, flashed gapps and went to bootloop. 3 button combo worked only for download mode, not for entering CWM. There was no way I could access CWM. I even could not enter Android boot (don't know exactly how it is called, but it saved my TF101 more than once.)
So after 1/2 hour of unsuccessful trying to get to CWM, phone just shows logo for icyglitch kernel and went to boot again, I have seen that only option to do anything was Odin. I downloaded Odin, downloaded some 2.3.6 ROM and downloaded CWM for that rom.
First I had to find driver for phone. I remembered phone on ICS wants nexus drivers so I installed those, booted phone to download mode and flashed 2.3.6 rom with Odin.
Phone booted, boot animation was on screen, but it did not boot to working Android. I didn't care too much, just booted to download mode again, flashed CWM and now I had at least access to my sd card. Did all wipes again, flashed DOC again and went to bootloop (Icyglitch kernel logo) again.
....
So I repeated Odin procedure, and when I had working CWM I flashed good old ICSSGS 4.02. This one worked.
I had spent 4 hours to solve this problem mostly because I was not full prepared to flash.
-I had no working USB driver on PC
-I did not had Odin
-I do not have ADB installed. Even if I had it, I don't know much how to use it.
-I did not have any working 2.3.6 ROM WITH bootloader
-Nandroid backup... hmmmm... what is that? Bah, don't need it...
Luckily I flashed my phone so many times I already roughly know what to do, but I still have experienced my share of "OMGOMGOMGOMG".
My advice to new and seasoned flashers:
Don't be cocky. After million of successful flashes once will go wrong. If nothing else Murphy will kick in. And when something goes wrong, be sure that all that you need to rescue phone is on your HDD and you know WHERE it is and how to use it. And read guides. And when you finish reading read them again, then go to sleep and flash next day.
Now I'm even more satisfied with myself because I do not flash other people's phones. If it happens that I create a 400€ brick, it will be at least mine.
If this helps anyone to restore phone, click Thanks button :good:

Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!

slaphead20 said:
Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!
Click to expand...
Click to collapse
Lol you were faster .

I had the same problem today trying to flash aokp m6...
Got bootloop and then Odin was hanging at various points when I tried going back to stock GB.
I thought I was goosed but the good old SGS came through in the end!
Sent from my GT-I9000 using xda premium

Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Stratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.

I would suggest you try SlimICS the next time you get sickend of (laggy) ROM. I for one, absolutely love SlimICS, and as all, it does have some drawbacks (no lag, though) when you're pimping it out too much.

upichie said:
Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Sratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.
Click to expand...
Click to collapse
Too bad I didn't know that. Somehow I was convinced that no ICS rom or kernel is flashable via Odin. But Later when everything worked and I finally had time to breathe I thought that I didn't need to go to GB. I think maybe only to flash any GB CWM with Odin would be enough. All I needed was working CWM, not entire rom.
Anyway, I'll try Slim now, let's hope I won't need to rescue phone again.

I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.

bpp9 said:
I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.
Click to expand...
Click to collapse
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!

Always brick my phone in the past, nearly one time a day
Well some tips for flashing:
- On stock ROMs, try flashing all partition firmware (i.e. 3 files in Odin) with re-partition checked before finding for help.
- Always backup you data with apps like Titanium backup, I don't usually use nandroid because it is not so flexible.
- Get GB bootloader before going to CM based ROMs, and go back to froyo bootloader if you want to have froyo back (search EzBoot for this).
- CM based ROMs and stock ROMs use a different filesystem, so flash all partition firmware before going back from CM to stock.
- Same reason, you will mostly get bootloops when going to CM ROMs. In this case, just hold the 3-button combo to enter recovery and flash it again.
- Same reason again, don't use CWM2 recovery to flash CM.
In case that anyone don't know, CM means CyanogenMod.
Hope this helps!
Sent from my GT-I9000 using xda app-developers app

tt0204 said:
Always brick my phone in the past, nearly one time a day
Click to expand...
Click to collapse
Uauuu, and you still didn't have heart attack?
I'm not sure if the fact that I managed to rescue my phone is good. Now I still don't have reason to buy SGS II.
And yes, Slim is woking, you can see my new signature. :highfive:

Managed to flash properly before I did
Wait at least until we get a working jelly bean before getting a new phone!
Sent from my GT-I9000 using xda app-developers app

slaphead20 said:
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!
Click to expand...
Click to collapse
Ahaha, I did the exact same thing the day before yesterday!
Using GT-I9000 my sent Tapatalk 2 from.

First time i flashed my phone was a heart in mouth moment when it boot looped for the first 2 or 3 times.
Swore I'd never flash my phone again. Over a year later and my phone has gone through countless changes and still going strong.
The only other issue I've had with customizing my phone is telling my flatmate about it. Problem being that he doesn't quite understand the concept of 'rooting' or 'flashing'. At least not in the geek sense of the words.

Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi

dreamer94 said:
Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
Actually boot directly into download mode without rebooting computer/phone will work

i know but wanted to live with that action,adrenaline
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi

I think we should start a membership here. Anyone who wants to join must expirience "OMG" factor for at least 20 min. I had it 4-5 times, if I count my hassling with Omnia too.
Isn't something interesting? I mean, look at us. We flash phones, sometimes we manage to make it useless, we spend hours for rescuing them, all that time we swear to god that we will never do that again, but 5 minutes after we manage to make our phones work we are ready for next flashing. Here in Slovenia we use to say that even donkey goes on ice only once, but looks like we newer learn...

My current favorite thread, it's refreshingly honest to see people laughing at themselves, and sharing their disasters, we all do it, in fact that's why we do it! Nice to see so much humility

About not bricking other people's phones....
Right now I'm in the process of bricking my boss's phone. He wants ICS on his Dell Streak 5, even if it is only pre-alpha ... Wish me luck.

Newbie Need Help..got my TF101 rooted..now what?

Hello, Im new to this and was able to root my TF101 build .27 with oneclickrecovery V0.4, which installed SUPERUSER v3.0.7
Wanted to install the EOS 4 JB because I read this is very Fast and Stable. This is what is important to me, hence the root.
Now how do I use this and install the ROM?
Is there a youtube or link that someone can direct me to?

Have a look here:
http://www.transformerforums.com/forum/showthread.php?t=33773
You will need to update to TWRP 2.3.2.3 (highly recommended) via GooManager

THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.

hipertec said:
THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.
Click to expand...
Click to collapse
I'll alleviate some of your confusion lol, Rouge XM etc are recoveries (that are accessed via holding vol down and power) Easyflasher is a program that runs off your pc and allows you to install a recovery (like Rouge, TWRP or CWM). Easyflasher also works as an unbrick tool (if you do something wrong and mess up your tf101 easyflasher will restore it back to stock)
When using a recovery you need to place the rom on your sd card (some recoveries will only allow flashing from internal or external sd card's not both, but in the case of rouge it access both) then wipe the device (this will get rid of data etc, so if your going to make a back up this is the time) and then wipe everything except for battery stats (it isnt necessary to wipe everything but im not using the same recovery so i cant remember what the options say on rouge so just wipe everything for now) then flash the rom with "install for .zip"(and anything that goes with it i.e gapps or another kernel----- depends on the rom your using) and then just to be safe wipe the devlik cache again and reboot.

hipertec said:
THank you for the link. I tried to install easyflasher but I think when I installed oneclickrecovery, it installed Rogue XM Team which I think is my flasher (instead of easyflasher)..when I rebooted with VOL_DN & PWR, then VOL-UP, it went to Rogue XM Team instead of easyflasher.
So can I just download the ROM into my SD Card and use the menu from the Rogue "install from .zip file"?
Is this the method?
I know Im half way there but need guidence for finish the rest. thanks for your help.
Click to expand...
Click to collapse
I would STRONGLY suggest switching to TWRP. Rogue will work for now, but if you flash updates to this ROM, the new file structure for 4.2 will cause your /sdcard/ to end up in the /sdcard/0/ directory, and after another flash it will be /sdcard/0/0/. You can move the files, but IMO TWRP is much better anyway (it can flash from internal and external storage).
You can install GooManager and choose to install open recoveryscript from the menu, or you can use the dd command and a terminal emulator to install TWRP:
First, download the twrp blob from here: http://techerrata.com/browse/twrp2/tf101
Rename the 2.3.2.3 blob to TWRP.blob
Method 1
Open a terminal emulator.
Code:
$ [B]su[/B]
# [B]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/B]
# [B]reboot[/B]
It is important to just do a reboot, if you reboot to recovery immediately it WILL NOT update the recovery. Upon reboot, you should see a progress indicator at the Eee Pad screen. Feel free to reboot to recovery after this (even before it boots).​

I strongly recommend reading the post by Fredurco in the link he provided. As a matter of fact, read the first three posts. These are the most detailed instructions for any ROM I've ever seen and believe me, I've seen more than a few. Take your time and just follow those directions to the letter and you will be fine.

frederuco said:
IMO TWRP is much better anyway (it can flash from internal and external storage).
Click to expand...
Click to collapse
I agree, rogue can also flash from internal and external, but twrp is the best, I need to update PERI to include it...

Thing O Doom said:
I agree, rogue can also flash from internal and external, but twrp is the best, I need to update PERI to include it...
Click to expand...
Click to collapse
Yeah, get crackin!

Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app

hipertec said:
Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Nothing as fast, eos3 in my opinion is the stablest custom ROM I've used but I can't move away from eos4, plus when timduru release the cornerstone build my tablet is gonna get some major use.

hipertec said:
Thanks everyone for your help. Got it updated to eos4. Is there another ROM that is fast and stable?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
JoinTheRealms said:
Nothing as fast, eos3 in my opinion is the stablest custom ROM I've used but I can't move away from eos4, plus when timduru release the cornerstone build my tablet is gonna get some major use.
Click to expand...
Click to collapse
I agree! EOS 4 IMO is the most usable and stable 4.2 build. My biggest complaint with the CM10.1 build was the touchpad disable was not working. It is still a great ROM otherwise and pretty stable.
As far as 4.1 ROMs, EOS 3 is solid, and so is the CM10/PananoidAndroid hybrid.
I am definitely itching for some cornerstone love!

I use liquidsmooth currently, and it's my new favorite, since everything works. I haven't found or noticed any bugs, which is rare.
EOS4 is also good, but I just don't like the feel of it oddly. Very well built and worth a shot though.

Hi Fred! Dug my TF101 out of moth balls and put on EOS4.
Had some trouble with the drivers, So I ended up using 1 from column A, 2 from column B:silly:
end result, got my drivers, APX mode going, (cross between oneclickrecovery, easyflash, nvFlash, Universal Naked Drivers),
Finally got twrp on and flashed superuser
got twrp-goo manager to update it, Flashed EOS4- saw updated recovery did not stick, finished the flash, updated twrp again, reflashed eos4- saw twrp update did stick this time, and now get to play with the TF 101 all over again!
Everything old is new again!
Thanks Fred! Your post on the TF forum was great, and XDA supplemented what wasn't working for me!! Great teamwork:victory:

Thanks to Fred's excellent tuts, I was able to easily get TWRP installed and rooted (although it did kill my WiFi somehow, which I'm hoping will be solved with a different ROM), but have a dilemma:
Not to hijack (didn't see the point of starting a new thread about the same thing, but I will if you guys want me to) but which ROM will give the best video performance? I'm not trying to do 1080 stuff or anything naive like that, but I would at least like to be able to watch some of the lower quality 720p stuff (NPW's releases are very good) without stuttering or syncing issues.
Note: I'm not trying to do everything with this tablet and overall I'm VERY satisfied with the overall performance and wouldn't even be tinkering with it at all (I've had it for over a year on stock ICS) if I didn't travel a lot and use it to watch movies on the go. I only use this tablet for gaming, surfing, movies and lots of document viewing (PDF, MSOffice, etc). I don't care about GPS or the camera. I have a phone for that. However, I don't have the time or means to be constantly reflashing this thing because WiFi drops out every 30 minutes or something like that.
Basically, I'm looking for the ROM with the best combo of:
- Stability
- Respectable HD-ish video playback
I'm not a total Android noob. I spent many hours tinkering with my old Nook Color back in the day, so no worries there. I'm just looking for reliable video playback on the go. I've been looking at Android Revolution HD to preserve the ASUS File Manager and things like that, but really haven't seen anything definitive about video playback improvements. I'm open to moving up to JB, but its not a burning desire or anything.
Thanks!

LongbowFoSho said:
Thanks to Fred's excellent tuts, I was able to easily get TWRP installed and rooted (although it did kill my WiFi somehow, which I'm hoping will be solved with a different ROM), but have a dilemma:
Not to hijack (didn't see the point of starting a new thread about the same thing, but I will if you guys want me to) but which ROM will give the best video performance? I'm not trying to do 1080 stuff or anything naive like that, but I would at least like to be able to watch some of the lower quality 720p stuff (NPW's releases are very good) without stuttering or syncing issues.
Note: I'm not trying to do everything with this tablet and overall I'm VERY satisfied with the overall performance and wouldn't even be tinkering with it at all (I've had it for over a year on stock ICS) if I didn't travel a lot and use it to watch movies on the go. I only use this tablet for gaming, surfing, movies and lots of document viewing (PDF, MSOffice, etc). I don't care about GPS or the camera. I have a phone for that. However, I don't have the time or means to be constantly reflashing this thing because WiFi drops out every 30 minutes or something like that.
Basically, I'm looking for the ROM with the best combo of:
- Stability
- Respectable HD-ish video playback
I'm not a total Android noob. I spent many hours tinkering with my old Nook Color back in the day, so no worries there. I'm just looking for reliable video playback on the go. I've been looking at Android Revolution HD to preserve the ASUS File Manager and things like that, but really haven't seen anything definitive about video playback improvements. I'm open to moving up to JB, but its not a burning desire or anything.
Thanks!
Click to expand...
Click to collapse
I guess I am not sure what is causing your WiFi stability issues. I have no problems with the EOS 4 ROM and WiFi. It never drops out on me. It is perfectly stable, and I can play 720p H264 23.94 FPS mkv files with no issues using MX player.
Before I ran EOS 4, I was running the ParanoidAndroid/CM10 Hybrid ROM and it was just as stable and fast.
If you are having WiFi issues, did you do all the wipes (Cache, Davlik, System, Factory Reset) before flashing the ROM? If not, then that is probably where the WiFi issue is (settings from your previous ICS ROM still present on the data partition).

Disregard the bit about the WiFi. I disconnected and reconnected to my network and all is well.
It sounds like EOS4 is the only ROM that is still consistently updated. I'll give it a shot and see how it goes.
Thanks!

LongbowFoSho said:
Disregard the bit about the WiFi. I disconnected and reconnected to my network and all is well.
It sounds like EOS4 is the only ROM that is still consistently updated. I'll give it a shot and see how it goes.
Thanks!
Click to expand...
Click to collapse
EOS4 and the CM10.1 No-Name are the only ones getting regular updates.

Thanks for the quick responses. EOS 4 is installed and process of redownloading all my apps. Now I just need to test out some video. I'm testing it without the OC kernel first, just for fun.

If you wanna see more in-depth which rom is better, I recommend a little app called Antutu benchmark, it'll give your current setup a score depending on how fast it does things like 3d renderind, sd card reading and battery performance

I might be in the minority with this opinion, but after some tinkering I'm not all that convinced that EOS is any faster than the stock ROM from a general usability standpoint (even with the latest KAT kernel), but the video is definitely improved, so I'll keep it as my "daily driver".
Thanks for the help, guys!