Database Users

[SOLVED] Boot logo and screen calibration issue

Hello all,
I've got an issue after using CM ¬B^¬N rom and kholk kernel.
After wipe data/cache, installing CM ¬B^¬N rom, kholk kernel and , by error, using partionning SD card in clockword recovery , i've lost the startup motorola logo (i get somme text instead of), and my screen calibration is bad, all screen touch is up for 1cm, and my home/search/back button desn't work because of screen calibration...
I've try to flash back all kernel, rom, or restore all my backup, i can't get back my motorola startup logo, and more important, the right screen calibration
I've unlocked my atrix and flash clockword recovery. I know how using fastboot if need.
I thing i need to flash sbf to solve it, but what's kind of sbf using to prevent brike ?
Can someone help me to solve it ?
EDIT :
SOLVED = http://forum.xda-developers.com/showthread.php?t=1131649

Im gonna guess you have accidentally corrupted/ wiped the PDS partition. For the text, you have accidentally wiped the 'logo partition' of your phone. I would suggest you to read VERY carefully the next time you decide to flash your phone. As for what sbf file is safe to flash, if you have ever OTA to 2.3 or flashed a sbf file to gingerbread, you CANNOT use a 2.2 sbf. The simplest way is to fix your PDS partition.

Hello,
Don't worry, i usually know what i'm doing. And in this case, there was a flash problem, and not a user problem
So now i've retreive boot logo, unlocking note, etc... BUT CALIBRATION ISSUE STAY !!!
It work like this = i can use menu/home/back/search button.... and all touch screen is resize without button...
Can someone help me please ?

That's OK, i've solve it :
http://forum.xda-developers.com/showthread.php?t=1131649

Man, I wish I had seen this before.. I did a warranty claim for this exact problem as my touchpad calibration was all FUBAR from doing the exact same thing in CWM.
Good stuff to know now, thanks.

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

Vegacomb - drawing is useless

Not sure if this is hardware or software, if it's software, is there a way to fix this?
when I draw anything on the Vega (Vegacomb latest version) in DrawSomething or any drawing app (big canvas), my lines look like I'm on a vibrating plate, it's completely unusable, occasionally vertical lines look OK, but anything else is unrecognisable
any ideas?

Its probably the touchscreen causing the problem as most roms fail to calibrate the screen correctly because of a flaw in the it7620 driver.
Try installing this shuttle test rom.
http://dl.dropbox.com/u/37483979/P10_image_20110411_v1.10.4_std_dev.exe
It was posted over on modaco by a guy called alex zhou.
Install the test rom with NVflash, it will calibrate the screen correctly on first boot (press the back button).
Then install recovery boot
http://dl.dropbox.com/u/37483979/com.modaco.vegarecoveryboot_c2.apk
and boot to CWM recovery.
format data, cache, boot and system then turn off.
Now NVflash the test rom again, run it and calibrate the screen again.
Now install what ever rom you want and your problem should be gone
Good luck
Thanks to Ged over on modaco for the dropbox upload for the files.
The next release of vegaics should contain an improved driver that will enable proper calibration. The same driver can be used for vegacomb but would require someone building a rom with the driver included. As far as I know no one has done this yet and I dont think anyone is working on Vegacomb (I may be wrong) as ICS is getting all the love.

richardmlea said:
Its probably the touchscreen causing the problem as most roms fail to calibrate the screen correctly because of a flaw in the it7620 driver.
Try installing this shuttle test rom.
http://dl.dropbox.com/u/37483979/P10_image_20110411_v1.10.4_std_dev.exe
It was posted over on modaco by a guy called alex zhou.
Install the test rom with NVflash, it will calibrate the screen correctly on first boot (press the back button).
Then install recovery boot
http://dl.dropbox.com/u/37483979/com.modaco.vegarecoveryboot_c2.apk
and boot to CWM recovery.
format data, cache, boot and system then turn off.
Now NVflash the test rom again, run it and calibrate the screen again.
Now install what ever rom you want and your problem should be gone
Good luck
Thanks to Ged over on modaco for the dropbox upload for the files.
The next release of vegaics should contain an improved driver that will enable proper calibration. The same driver can be used for vegacomb but would require someone building a rom with the driver included. As far as I know no one has done this yet and I dont think anyone is working on Vegacomb (I may be wrong) as ICS is getting all the love.
Click to expand...
Click to collapse
tried VegaICS, got the same, run calibrate in shuttle tools, got the same, did as you suggested above, installed the ROM, calibrated, formatted etc, installed ROM again, calibrated, then installed VegaICS again, got the same, rant calibrate in shuttle tools, got the same
it's not just me either, a work colleague has the same issue

Vega screen is unresponsive when cold

Hi all, hope someone can help me.
I've recently bought a refurbished Advent Vega from Curry/PC World Ebay outlet. I've installed ICS Custom rom onto it but am having a problem with the screen being unresponsive when the tablet is cold.
I know its not an issue with the rom as the same issue occurs with other roms including the vega's stock rom.
I believe it is some sort of heat problem, that when the device is cold (when it has been off all night) the screen is really unresponsive, to the point that the unlock slider won't move without pressing extremely hard on the screen, this still doesn't unlock but it does move around a little.
After a while the screen will gradually become more reponsive but still a bit jittery and then after a bit longer once it has warmed up a bit the screem works perfectly. If I charge the tablet it seems to fix it quicker but I believe this is due to the heat again as the battery charging heats the tablet up quite quickly.
I've read a couple of other articles about squeezing the left hand or right hand side of the tablet and many people say that this works but it doesn't for me.
Does anyone else have any other suggestions on how this can be fixed.
Thanks for any help you can provide.

Try this shuttle test rom.
http://dl.dropbox.com/u/37483979/P10_image_20110411_v1.10.4_std_dev.exe
It was posted over on modaco by a guy called alex zhou.
Install the test rom with NVflash, it will calibrate the screen correctly on first boot (press the back button).
Then install recovery boot
http://dl.dropbox.com/u/37483979/com.modaco.vegarecoveryboot_c2.apk
and boot to CWM recovery.
format data, cache, boot and system then turn off.
Now NVflash the test rom again, run it and calibrate the screen again.
Now install what ever rom you want and your problem should be gone
Good luck
Thanks to Ged over on modaco for the dropbox upload for the files.

Thanks so much for your help. Works perfectly well now thanks even when it is cold.

Your welcome, glad it fixed it.
The next release of vegaice will include a improved touchscreen driver that will correctly calibrate the screen but if the problem returns again just redo the above fix.
Richard

Hi Richard - I registered with XDA (after months of lurking) just so I could thank you for this same advice when you gave it to mmace. I now gather I can't thank anyone till I've posted at least once, so this is it - if I now can I'll thank you on both threads, FWIW.
Anyhoos, to make this more than just a "thank you note" I'll explain - I bought a Vega with an "unresponsive screen" very cheaply on eBay hoping I could at least make a cheap netbook of it with a keyboard/mouse - my Tosh Folio100 permits this more easily than the Vega, it transpires, as it defaults to USB host status. When it arrived I found an otherwise tidy tablet stuck in language selection and tried various roms in the hope that the USB could be enabled. ICS b1, unlike the others, showed some vestigial responsiveness on the screen itself so I started looking for a way to calibrate it - I didn't find Alex's posting on Modaco but when I found mmace's here I followed your instructions (resisting the temptation to just stick with Alex's rom once it fixed the screen completely!) and now (fingers crossed) have a fully working Vega for peanuts....
Please let me stress - when it arrived this Vega's touch screen was totally non-functioning, no amount of pressure or flexing of the case made any difference. In ICS the language selection would scroll but not select. After running Alex's rom the problem disappeared completely.
Two questions now occur to me -
1. Why the load/clear/reload/load regime? I followed it religiously but can't help wondering whether I couldn't have just skipped the clear and reload.
2. Why isn't it possible to run a standalone version of the recalibrator on an adhoc basis when required? - If the touch screen fails again once the tablet's been in use for a while this procedure will be far more of a nuisance.
Anyway, Richard, I thank you for the sage advice and my wife thanks you for her now having a tablet instead of a netbook. Only thing is, I was going to buy a new touch screen for my Tosh (which is 'starred') but since it would cost more than this now-perfect Vega I can no longer justify it.....

Thank you indeed.
My Vega has suffered from random screen badness since I first went to vegacomb.
I had to live with it by treating it like it was a baby not to be upset!! Otherwise the screen and the dummy went outta the pram.
Could anyone provide some more download links? as Richards dropbox is creating too much traffic and has been disabled for a while.
Sent from my Advent Vega with a screen like a slapped ass!

recovery boot problem with this method
hello
i have exactly the same issue as cboard with a vega probably bought at the same time!
i have followed richardmlea's post but seem to be having trouble with the vega recovery boot. I have installed it into the test rom with the file manager but when i run it it boots to recovery (android man with the orange arrow) but hangs here, if i eventually then press the power button it shows the vega recovery options but none of them work and just send me back to the android/orange arrow recovery screen. in the bottom of the recovery page it says something like
formatting: ... misc
i'm sure this will also solve my 'cold' vega problem so would be grateful of any help
thanks
keith

kiffmoore said:
hello
i have exactly the same issue as cboard with a vega probably bought at the same time!
i have followed richardmlea's post but seem to be having trouble with the vega recovery boot. I have installed it into the test rom with the file manager but when i run it it boots to recovery (android man with the orange arrow) but hangs here, if i eventually then press the power button it shows the vega recovery options but none of them work and just send me back to the android/orange arrow recovery screen. in the bottom of the recovery page it says something like
formatting: ... misc
i'm sure this will also solve my 'cold' vega problem so would be grateful of any help
thanks
keith
Click to expand...
Click to collapse
Same issue here,
Also, tried to install CWM from Rom Manager but unable to gain root access?
Any suggestions to install CWM rather than the stock vega recovery?

Bad nand blocks
Glad it helped you all.
More Vega’s saved from the scrap heap; I can feel the ozone layer growing back as I type. I think I may burn a tree to celebrate.
x5starguerillaa said:
Same issue here,
Also, tried to install CWM from Rom Manager but unable to gain root access?
Any suggestions to install CWM rather than the stock vega recovery?
Click to expand...
Click to collapse
This Issue is caused by block in the bad nand ram. The bad blocks you have are in the boot partition so recovery is not flashing correctly to the ram. If the bad nand where elsewhere (everyone has them to some degree) they would be causing a different problem.
The solution is to install a rom that re-partitions the nand differently (effectively moving the physical locations of the recovery and other partitions on the nand)
This was the reason 2 versions of Moddedstock were created. Moddedstock re-partitions Nand to make more space for larger versions of android (originally Vegacomb). Newbe5 discovered that altering the location and size of the boot and recovery partition fixed the problem for some but created the same problems for others. He created Moddedstock version 2 so there was a second version so people could have a second roll of the dice, so to speak.
All versions of VegaICS have the same partition layout as moddedstock version 2 (I think) but of regardless which is one now being used, there is only one base. This is why some people get stuck at the boot logo after installing Vegaics and others cant boot recovery.
Ideally we need 2 partition layouts again.
The solution for both of you above is not to install or boot CWM recovery after calibration on the factory test rom. Instead turn it off, put it in nvflash mode (back/power button thing) flash moddedstock and when booted select boot to recovery. If this fails any point (installing, booting or recovery) get the other version of moddedstock and try that one, one of them should work for you.
Good luck
Richard

I tried the shuttle test rom in my viewpad 10s with totally unresponsive touchscreen, but it didn't work. After hitting "back" button to start screen calibration, it jumped to setup screen and the touchscreen is still not working at all. Already tried to reflash the shuttle rom few times.
Any idea how to fix it? Thanks.

Answered on modaco thread
http://android.modaco.com/topic/352220-how-to-fix-touch-problemadvent-vega-p10-10s/
rchoi999 said:
I tried the shuttle test rom in my viewpad 10s with totally unresponsive touchscreen, but it didn't work. After hitting "back" button to start screen calibration, it jumped to setup screen and the touchscreen is still not working at all. Already tried to reflash the shuttle rom few times.
Any idea how to fix it? Thanks.
Click to expand...
Click to collapse

Is it possible to restore a cwm backup after doing this or will that simply undo what this process fixes?
Edit: I'm running VegaICS Beta1 btw
Sent from my Vega using XDA

Thanks for advice on bad nand blocks Richard. I will give that a whirl later this evening.
Sent from my HTC One X using XDA

fubofo said:
Is it possible to restore a cwm backup after doing this or will that simply undo what this process fixes?
Edit: I'm running VegaICS Beta1 btw
Sent from my Vega using XDA
Click to expand...
Click to collapse
It depends on what you are referring to.
Restoring the CWM will not undo the touchscreen fix. However, most roms that are not android 2.2 (everything useful except corvus5) will fail to calibrate the screen properly*, so over time heat (and probably other things) cause the calibration to go off. Using the shuttle tools calibration app wont work properly.
Eduardo's new touchscreen driver fixes this problem so the calibration works correctly. Unfortunately this driver was made after Vegacomb beta 1 was released. There are a couple of updates that I know of (*one by Scanno one by Areo) that include the new touchscreen driver.
If your CWM backup contained this new Touchscreen driver, after you restore your backup you shouldn't have any further problems. You may occasionally loose calibration but the screen calibration app (in shuttle tools) will work correctly and the touchscreen will work again after calibration (so no need flash another rom).
If it’s the partition layout and the nand issue you are referring to.
A cwm backup won’t change the partition layout but will restore the contents of the recovery and boot partitions. The bad nand will still be there but in a different place (relative to the old partition layout). If the errors are somewhere critical the tablet may not boot after restoring the backup or boot to recovery may not work. If the errors are somewhere less critical it may not affect you at all. The bad blocks are common to all nand, as long as there are not too many they won’t cause any problems.

Thanks for getting back richard.
I do have the latest VegaICS beta1 installed along with the UpdatedApps patch and Kernel supplied by scanno. No my concern was not about the recovery partition issue, it was reference a full system backup from CWM.
So just to confirm:
I should be able to create a complete system backup (nandroid) then apply this fix? A nandroid restore should not undo the fix so long as I have the latest kernel installed (I believe I do), would that sound about right?
Sent from my Vega using XDA

Exactly right.
Fingers crossed anyway.
I only had to do the fix once, a few days later the new driver was released and I used it immediately. The only touchscreen related issue I have had since was a slight loss of calibration after I had been playing a game for about 4 hours. The screen had got very hot and started to loose accuracy. The screen calibration in shuttle tools restored normality in seconds and it hasn't happened since.
I have since put a sheet of Mylar between the LCD and the motherboard to deflect heat away from the touchscreen. This may have helped, its defiantly cooler.
http://forum.xda-developers.com/showthread.php?t=1585071

Great, thanks for that. I'll have a go and get back with any success. My screen has random sensitivity issues and regularly hits keys multiple times, gets a bit annoying after a while lol.
I take it the Vega tools you refer to is the shuttle tools app?
Sent from my Vega using XDA

fubofo said:
I take it the Vega tools you refer to is the shuttle tools app?
Sent from my Vega using XDA
Click to expand...
Click to collapse
Doh!
Yes, do. I will change it to avoid confusion for anyone else.

richard's advice if you can't boot to recovery
hi richard
thanks for your further advice on bad nand blocks and booting into recovery, followed you further method and at present (touch wood!) the unresponsive 'cold' screen issue has been solved
appreciate your help saves me sending it back to currys ebay!
keith

Ive got a problem where after installing the P10_image_20110411_v1.10.4_std_dev rom, and rebooting into recovery. Im presented with this screen:
Code:
Android system recovery <3e>
Android system recovery utility
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
_______________________________________________________
Formatting MISC.....
Now im able to highlight the options using the up/down volume keys but i cant select anything. The power button just hides all the options and the back button seems to do nothing.
Has anyone else come across this or got a resolution?

[Q] CM10 first rolling recovery now scrambled lock screen!!!

Hey guys,
this is my first post and my problem is as follows:
I had ICS 4.0.x on my galaxy tab 10,1 P7500, I then installed CWM 5.5.0.4. but had a rolling window. I then continued to install a bootloader (here: http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41) with the appropriate bootloader for the p4. This fixed the rolling recovery and allowed me to install CM10 using CWM.
But my current problem is when the device goes on sleep mode and I wake the device up the screen is scrambled, can anyone tell me how to fix this?
Thank you in advance

The only fix i found is for HC
http://forum.xda-developers.com/showthread.php?t=1680738
Edit:
I fixed the rolling screen issue after screen unlock with pershoot's help, thanks again pershoot!
Maybe it will also work for you , here we go:
If you have installed the latest cm10 build, there is only one issue for the p4wifi , you must be on the US ICS Bootloader .
So download the recovery.tar.md5 from here:
http://droidbasement.com/galaxy/roms/cm10/p4wifi/recovery.tar.md5
Than go into download mode and flash this recovery using ODIN, (select pda and look for this file where you safed it, than click start)
Than, download the right US ICS Bootloader here:
http://droidbasement.com/galaxy/roms/cm10/p4wifi/US_LPL_4.0.4_bootloader.zip
Flash this also via ODIN in the PDA section, this may take a little longer, don't panic...
After that, the tablet will reboot and it should work... don't blame me if it didn't, but i had this rolling screen on almost every rom, and everything is fixed now...
I wish you good luck because i know it IS very annoying..

Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
DefQoN_BE said:
I have EXACT the same issue, i'm running the latest cm10 build from droidbasement.com, if anyone can please help us???
The only fix i found is for HC
http://forum.xda-developers.com/showthread.php?t=1680738
I wish you good luck because i know it IS very annoying..
Click to expand...
Click to collapse
I have tried this method and works perfectly!
Thank you sooo much!!!

I am afraid to put a rom on my 10.1, i love it though!

blacks10 said:
I am afraid to put a rom on my 10.1, i love it though!
Click to expand...
Click to collapse
There's nothing you should be afraid of there is a fix for everything, and if you can't find it? There are nice poeple out there who wants to solve your problrm on xda developers forum
@drefcom: you're welcome

Please help - When turning off the Screen Android 4.1.1 will not come back on
I have the following problem.
When I install one of the latest rom e.g.
[ROM] [JB] [P4--P4WIFI--P4VZW]
4.1.2 AOKP for the Galaxy Tab 10.1
or
[ROM][JB][CM10] Android 4.1.1 - CyanogenMod 10 Preview
then I have this problem:
When I turn off with the "Power"-Hardbutton, then it turns off, but it does not turn back on. The screen stays black.
With the Rom ...
[ROM][JB][CM10] Android 4.1.1 - CyanogenMod 10 Preview "cm-10-20120814-EXPERIMENTAL-p4.zip" from August everything works fine.
Since I had this flickering problem I flashed the bootloader before I installed all these Roms.
But one works and all new ones don't.
Anyone has a idea what to do?
thx

drefcom said:
Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
I have tried this method and works perfectly!
Thank you sooo much!!!
Click to expand...
Click to collapse
:good:
Thanks this helped me fix a mates Galaxy Tab 10.1
I was starting to pull my hair out and this worked so well.
Takes no time to do and no need to reflash the rom.

Hi guys.
speersie said:
:good:
Thanks this helped me fix a mates Galaxy Tab 10.1
I was starting to pull my hair out and this worked so well.
Takes no time to do and no need to reflash the rom.
Click to expand...
Click to collapse
i tried this method, but at second flashing (bootloader.zip) i get "0 succeed/0 failed" and still i get that scramble, and have to reboot all the time.
Any ideas?
Thanks in advance.
Cheers!:good:

Problems solved
I solved my problems. I installed the "custom" bootloader for each Rom and the "black screen" problem is now gone.
Thanx anyway.

drefcom said:
Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
I have tried this method and works perfectly!
Thank you sooo much!!!
Click to expand...
Click to collapse
I have tested the fix for weeks now and it worked great.
Except, this afternoon my tablet randomly restarted and now won't go past CM 10 boot screen.
Any idea whether reflashing the ROM without wyping, purely just installing (as is) CM10 M2 from CWM? Or any other ideas?
I have tried clearing the cache and the dalvik cache. I then tried doing a factory reset but it doesn't seem to proress. I thought if I can do a factory reset then reinstall the ROM I might get it to work but I can't install the ROM as it says "Error (Status 7)?
I have tried formatting the /data in attempt to get the factory reset to work but this also freezes.
Currently, my tablet is in an infinite loop cycle and I cannot change the ROM or do a factory reset.
Thanks, you guys have really been helpful!

drefcom said:
I have tested the fix for weeks now and it worked great.
Except, this afternoon my tablet randomly restarted and now won't go past CM 10 boot screen.
Any idea whether reflashing the ROM without wyping, purely just installing (as is) CM10 M2 from CWM? Or any other ideas?
I have tried clearing the cache and the dalvik cache. I then tried doing a factory reset but it doesn't seem to proress. I thought if I can do a factory reset then reinstall the ROM I might get it to work but I can't install the ROM as it says "Error (Status 7)?
I have tried formatting the /data in attempt to get the factory reset to work but this also freezes.
Currently, my tablet is in an infinite loop cycle and I cannot change the ROM or do a factory reset.
Thanks, you guys have really been helpful!
Click to expand...
Click to collapse
After hours of trying I have found a solution.
I previously had done backups. I tried each one until one started restoring. It completed quite a lot till it froze and I restarted into recovery.
I did a cache wipe and dalvik cache wipe and could then complete a factory reset.
It has now booted completely into ICS where I can now flash CM10 again.
The tablet works normally as you would expect on ICS. I booted into recovery and tried to flash CM10 M2 for the GT-P7500 but I still get a error, status 7.
Anyone experienced this?

drefcom said:
After hours of trying I have found a solution.
I previously had done backups. I tried each one until one started restoring. It completed quite a lot till it froze and I restarted into recovery.
I did a cache wipe and dalvik cache wipe and could then complete a factory reset.
It has now booted completely into ICS where I can now flash CM10 again.
The tablet works normally as you would expect on ICS. I booted into recovery and tried to flash CM10 M2 for the GT-P7500 but I still get a error, status 7.
Anyone experienced this?
Click to expand...
Click to collapse
Status 7 usually indicates the wrong update file, are you sure you are flashing the right ROM for the 7500?
Perhaps try to flash the recovery and bootloader first and then the right ROM and see what happens?

DefQoN_BE said:
Status 7 usually indicates the wrong update file, are you sure you are flashing the right ROM for the 7500?
Perhaps try to flash the recovery and bootloader first and then the right ROM and see what happens?
Click to expand...
Click to collapse
The thing is it is the exact same file I used to flash the previous time.. I first updated my recovery and bootloader before flashing and still get the error. Thanx for the thought though.