530 replies to this topic

[boutsism]

and i dont think that it works again...the install is becoming correct but after booting it doesnt start...it stucks at android icon...

[kallt_kaffe]

boutsism, on May 29 2011, 13:05, said:

What do u mean when u say "run this: dmesg |grep 0.22" cause i didnt understand it...

It was meant for Sebastian so that he can make sure that the new kernel has been flashed. It will not work with the currently available Clockwork versions but hopefully it will work when Sebastian release the new version.

[Sebastian404]

kallt_kaffe, on May 29 2011, 11:15, said:

First install CM7 and after booting run this: dmesg |grep 0.22
You should now see the frequency table.

Now install the attached update and after boot, do the same thing again.

The AHB bus frequency should now have changed from 160000 to 240000 for the 480000kHz level and from 200000 to 300000 for the 600000kHz level.

Yeah, tested that and it seems to of worked

download here...

Edited by Sebastian404, 29 May 2011 - 03:11 PM.

[boutsism]

could u please tell me the steps so as to install the new cm7 update? i cant make it even when i flashed the new recovery sebestian uploaded today...it stucks at android icon on restart after the install in recovery mode...

[kallt_kaffe]

boutsism, on May 29 2011, 19:05, said:

could u please tell me the steps so as to install the new cm7 update? i cant make it even when i flashed the new recovery sebestian uploaded today...it stucks at android icon on restart after the install in recovery mode...

It seems something has changed in the install script. It starts with backing up all the installed google apps to /tmp and then runs out of space so when it's time to exctract and flash the kernel it fails.

I hate to say this, but we propably could do with even more space on /tmp in Clockwork Recovery. I'm sorry I did not realize this erlier. Google apps needs about ~20Mb so I suppose it wouldn't harm to make /tmp 32Mb.

[forforum]

Sebastian404, on May 30 2011, 00:41, said:

Yeah, tested that and it seems to of worked

Thanks Sebastian and KK, just installed the patched kernel and checked the dmsg messages.  AHB is overclocked!!  Will play around a bit more to see the real effect.

[sneakytoiletroll]

Can one of you smart people help me out? I have a Telecom New Zealand ZTE V9 which operated on the UTMS 850 MHz frequency, with 2100 MHz infill in the major cities. After updating to the generic I lost the 850mhz and I was hoping that I might gain it again after updating onto the 2.3.4 version, but no luck. Any ideas?

[bubbdamadaussie]

Hi guys thanks for all your hard work putting this together but now I have a problem.
I downloaded all the nessasary files and flashed my optus tab using causic sodas instructions but now all I gaet is the android logo on the spinning skate board.
I have downloaded the files that are suggested to use in the thread to flash back to original but I can't seem to get it to do what the instructions say.
Any help would be really appreciated thanks.

[boutsism]

it doesnt work even now...are we doing anything wrong?it still stucks...

[CTFunkmonkey]

Ive followed various steps myself, and have ended up with a couple of serious problems.

I first tried the latest build cm7 available, and that went into the install for a little bit then failed. Running the official optus 2.2 update fixed that back to standard. I then tried an older version, the '20' one. That appeared to install fine, but then bootlooped at the skateboard. A subsequent run of the official updater has done the same.

Any ideas guys? I dont want to junk an awesome tablet days after ive bought it!

[garfin]

Hi Guys, (those having install problems)

not sure why some succeed where others fail..

did you follow CS's steps to the letter , in particular ..

- New rom will be installed, and device will remain in recovery
5. Clear caches
- click "Go Back" twice
- select "wipe data/factory reset", and confirm when prompted
- click "advanced"
- click "wipe dalvik cache", and confirm when prompted
- click "fix permissions"
6. Restart
- select "reboot" option (and cross your fingers)



eg  No rebooting inbetween the install of CM7 and the subsequent "wipes" , permission fix ?

[garfin]

CTFunkmonkey, on May 30 2011, 22:13, said:

bootlooped at the skateboard. A subsequent run of the official updater has done the same.

Try getting your MyTab going again by using KK's repackaged updater ... post #169

http://android.modac...p...t&p=1697683

[boutsism]

garfin, on May 30 2011, 12:29, said:

Hi Guys, (those having install problems)

not sure why some succeed where others fail..

did you follow CS's steps to the letter , in particular ..

- New rom will be installed, and device will remain in recovery
5. Clear caches
- click "Go Back" twice
- select "wipe data/factory reset", and confirm when prompted
- click "advanced"
- click "wipe dalvik cache", and confirm when prompted
- click "fix permissions"
6. Restart
- select "reboot" option (and cross your fingers)
eg  No rebooting inbetween the install of CM7 and the subsequent "wipes" , permission fix ?

garfin,did u use the latest "2011-05-29" update and dd all these you mentioned and it worked?are u sure???cause i did them too from the latest recovery sebastian added and it doesnt...do i need to do anything else?

[garfin]

boutsism, on May 30 2011, 23:00, said:

garfin,did u use the latest "2011-05-29" update and dd all these you mentioned and it worked?are u sure???cause i did them too from the latest recovery sebastian added and it doesnt...do i need to do anything else?

No  i used 20110525 , as that was the latest at the time..havent seen a need to step forward from that version, as yet ..  (refer my post #48 , Pg3 of this thread)  , I'm pretty sure CS was also installing that same version on his Tab , when he detailed the steps..

Edited by garfin, 30 May 2011 - 01:19 PM.

[boutsism]

garfin, on May 30 2011, 13:17, said:

No  i used 20110525 , as that was the latest at the time..havent seen a need to step forward from that version, as yet ..  (refer my post #48 , Pg3 of this thread)  , I'm pretty sure CS was also installing that same version on his Tab , when he detailed the steps..

oh thats ok then cause 20110525 worked on me too...but i wantto put the new one...thats why im asking...the new one has the problem probably...

[CTFunkmonkey]

Morning all,

Yep i followed all the instructions several times closely, however i have found a way to unbrick them using a generic er.. update thing involving something called Sales_MultiDL and a generic update. Gets it running again. Tried to do a CM7 update install with that 28 build, same again, no joy.

[CTFunkmonkey]

CTFunkmonkey, on May 30 2011, 17:22, said:

Morning all,

Yep i followed all the instructions several times closely, however i have found a way to unbrick them using a generic er.. update thing involving something called Sales_MultiDL and a generic update. Gets it running again. Tried to do a CM7 update install with that 28 build, same again, no joy.

Oh and thanks all for the replies, i managed to get it going before i found them!

[Bohdans]

Hi,
First time poster here
With LOTS of messing around I found some things out,
FIRST:
For Optus users you MUST flash the GENERIC Firmware FIRST! I am assuming the Optus firmware has some sort of lock which causes CM7 to boot loop.

SECOND:
I could not get date29 firmware to work straight from GENERIC 2.2

THIRD:
You can flash GENERIC 2.2 using patched tool, install recovery, reboot then flash date25, then date29, then GAPPS, then Overclock pack. Then WIPE!!!! Then boot. You will have date29 with overclock working

[kallt_kaffe]

Sebastian404, on May 29 2011, 16:41, said:

Yeah, tested that and it seems to of worked

download here...

Can you make the next version have even larger /tmp. I noticed the CM7 install backs up the Google apps to /tmp and restores them after an install when you upgrade CM7 from one nightly to another.

I changed your latest version to have 64Mb /tmp and the install went fine and I didn't need to reinstall the google apps package.

[boutsism]

this time with Bohdans tips,it worked...i havent found any problems till now in 29 version... we will see!!!great work from ll of you!!!