Develop Bugs

[ROM][12/7/10] Stock w/root, odex and deodex post-OTA, *updated instructions (v1.1)

ya ya, this should have been first. but we all wanted to play. but anyway here it is now.
this is the stock rom post OTA. added root (su and superuser.apk) as well as modified ramdisk (ro.secure=0) and busybox. Also zip aligned apps to optimize ram usage. there is odex (stock) and de-odex versions.
*i no longer see the reason for needing the pre-OTA rom. if you have a reason post up and we'll see what happens...
if you are upgrading from previous version of THIS rom you should not have to wipe, however you will still need to redo any system changes you have made, i.e. trackpad wake or notification lights.
Stock OTA kernel is now INCLUDED in rom flash. however if you want to flash an oc/uv/whatever kernel follow that post's instructions after this rom is up and running. i suggest pershoots kernels. been using his since the g1, awesome work. his g2 one has great performance AND battery life.(for me anyway)
These roms are g2 and dz compatible.
Cwm recovery recomended for ease and function.
1. Place stock rom of your choice on root of sdcard.
2. Boot into recovery
3. Do a nandroid backup.
4. Do a full wipe. (if coming from different rom)
5. Select flash zip from sd and select stock rom.
6. Once its finished, reboot and enjoy.
OTA odex: http://www.4shared.com/file/XlIDy7SV/ota_odex_V11.html
OTA de-odex: http://www.4shared.com/file/vi77pxvT/ota_deodex_v11.html
OTA bootv2 (kernel): http://www.4shared.com/file/y2NVlbJm/ota_boot_v2.html
*(only needed if you flashed a different kernel after the version 1.1 rom and want to go back to stock kernel. includes wifi module.)
pershoots's kernel:
http://forum.xda-developers.com/showthread.php?t=847672
theme template: http://www.4shared.com/file/VwINHT_r/theme_template.html
*theme template is for theme dev's only. it should be universal for any rom. just place the themed framework and/or apps in corresponding folders. i have a .txt file in the folders as a place holder, delete it after you add your themed stuff. take a look at the update script to see how it works, and to add or remove anything you need to...
change log:
v1.1:
fixed permissions and mismatched symlink issue w/busybox. (thanks to Mikey1022 for bringing this prob to my attn.)
v1.0:
initial release

Awesome thanks!! Do we have to flash a separate kernel if coming from Sense, and if so, do you have the stock kernel in a flashable .zip? Thank you in advance,
Russ

Nice work! good to have a base Rom to fall back on but why do we need three Roms for stock? why not just deodex the stock Rom with the OTA applied and be done with it? less work for you, right? I know this is quicker and will help folks who have boot looped/ soft bricked their phones. either way, good job and thanks!

Can I just remove the odex files along with the bloatware apk files from my current rom? I know they are both located in the systems/app folder.
Sent from DynamikD's R00t3d & OC G2

rUsTyRuSs said:
Awesome thanks!! Do we have to flash a separate kernel if coming from Sense, and if so, do you have the stock kernel in a flashable .zip? Thank you in advance,
Russ
Click to expand...
Click to collapse
question 1: yes.
question 2: damn im an idiot and half asleep. its gonna give u same error at end of flashing as others. ignore and take boot img from zip and flash with fastboot. "fastboot flash boot boot.img"
ill have to update later on to updater-script. i have to get up for work in 1hr 45min!!!!!

rUsTyRuSs said:
Awesome thanks!! Do we have to flash a separate kernel if coming from Sense, and if so, do you have the stock kernel in a flashable .zip? Thank you in advance,
Russ
Click to expand...
Click to collapse
Yes, just flash Coolbho3000s OCed kernel.

fastludeh22 said:
question 1: yes.
question 2: damn im an idiot and half asleep. its gonna give u same error at end of flashing as others. ignore and take boot img from zip and flash with fastboot. "fastboot flash boot boot.img"
ill have to update later on to updater-script. i have to get up for work in 1hr 45min!!!!!
Click to expand...
Click to collapse
Lol! dude, slow down... get some sleep! you're as crazy as I am going to work the next day with only 2 hours of sleep! Good work though!

sino8r said:
Nice work! good to have a base Rom to fall back on but why do we need three Roms for stock? why not just deodex the stock Rom with the OTA applied and be done with it? less work for you, right? I know this is quicker and will help folks who have boot looped/ soft bricked their phones. either way, good job and thanks!
Click to expand...
Click to collapse
we dont need 3, but this is what i had to work with right now. i did odex cause thats true stock, and de-odex as a base for theamers. after patching the ota in ill update this post, not gonna make a new one.
dynamikd said:
Can I just remove the odex files along with the bloatware apk files from my current rom? I know they are both located in the systems/app folder.
Sent from DynamikD's R00t3d & OC G2
Click to expand...
Click to collapse
NOOOOO! nothing will work! the odex file is part of the apk. de-odex'ing act joins them...
edit: wait if u mean just the ones that you are compleatly removing, yes, just dont go removing all the odex files, lol

sino8r said:
Yes, just flash Coolbho3000s OCed kernel.
Click to expand...
Click to collapse
yes, this or bacon bits SHOULD work till i have a chance to fix op...

Im viewing this with xda app an I dont see a m5d is there one?
Sent from my T-Mobile G2 using XDA App

I must be doing something wrong... I flashed the boot img in fastboot, then went into clockwork recovery to write the deodexed rom, but keep getting
"E:Can't find BOOT...
E:Failure at line 334:
Write_raw_image PACKAGE:boot.img
BOOT:Installation aborted
I'mma keep trying and hopefully update this before anyone has slap me...

HELP PLS!!
I have a G2 which is S-off'd
Loaded the HTC Sense ROM on it yesterday but it kept messing up my SMSs (any SMS app incl. stock would freeze when sending SMSs)
Wanted to come back to the stock ROM and found this post
Flashed the ROM but now am stuck in the "HTC Quietly Brilliant" booting loop (i.e. phone won't progress past that splash screen)
Can someone pls help me in figuring out how to get out of this mess
I used to have Open Recovery but that's gone now. Have to rely on the stock recovery
I am not a pro at ADB etc so would appreciate step-by-step instructions pls
Thanks a million!! Appreciate it

i think u can download the stock rom, rename it to PC10IMG.ZIP, and reboot into hboot, but iono, i cant get anything right this morning

tommyxd said:
I must be doing something wrong... I flashed the boot img in fastboot, then went into clockwork recovery to write the deodexed rom, but keep getting
"E:Can't find BOOT...
E:Failure at line 334:
Write_raw_image PACKAGE:boot.img
BOOT:Installation aborted
I'mma keep trying and hopefully update this before anyone has slap me...
Click to expand...
Click to collapse
Did you try booting? Ignore error, till i can get home from work and fix it. I usually do it in differeent order though. Full wipe, flash rom, get error, ignore. Reboot into fastboot and flash boot.img OR flash one of the aosp flashable kernel zip.
adp21 said:
HELP PLS!!
I have a G2 which is S-off'd
Loaded the HTC Sense ROM on it yesterday but it kept messing up my SMSs (any SMS app incl. stock would freeze when sending SMSs)
Wanted to come back to the stock ROM and found this post
Flashed the ROM but now am stuck in the "HTC Quietly Brilliant" booting loop (i.e. phone won't progress past that splash screen)
Can someone pls help me in figuring out how to get out of this mess
I used to have Open Recovery but that's gone now. Have to rely on the stock recovery
I am not a pro at ADB etc so would appreciate step-by-step instructions pls
Thanks a million!! Appreciate it
Click to expand...
Click to collapse
You need to wipe when going from rom to rom. Get cwm recovery and follow my instructions above.

lmao, i think i did that, just in reverse order. Don't worry man, I think you need to get some rest when you get home. Thanks for the quick response btw

fastludeh22 said:
Did you try booting? Ignore error, till i can get home from work and fix it. I usually do it in differeent order though. Full wipe, flash rom, get error, ignore. Reboot into fastboot and flash boot.img OR flash one of the aosp flashable kernel zip.
You need to wipe when going from rom to rom. Get cwm recovery and follow my instructions above.
Click to expand...
Click to collapse
Thanks for the quick reply
I have already wiped via stock recovery - both data/ settings and cache
I can't boot into the phone (ie the part where u have the home screen etc). Keep getting stuck at the htc quietly brilliant screen. Phone will keep looping here
Can I still install clockwork recoverY (cwm)? If yes, how? If no, what can I do to get my phone back to normal
I'm goin' crazy here lol

I need clearer instructions. What do I rename this file to? When I go into hboot how do I load said file up?
I renamed it pc10img.zip, didn't work.
Sent from my T-Mobile G2 using XDA App

adp21 said:
Thanks for the quick reply
I have already wiped via stock recovery - both data/ settings and cache
I can't boot into the phone (ie the part where u have the home screen etc). Keep getting stuck at the htc quietly brilliant screen. Phone will keep looping here
Can I still install clockwork recoverY (cwm)? If yes, how? If no, what can I do to get my phone back to normal
I'm goin' crazy here lol
Click to expand...
Click to collapse
Also I tried to flash boot.img from fast boot but no cigar. Am I trying to flash from the wrong place?
Should I be naming the file something else? I think I left the name as is and/ or may have tried to flash by calling it PC10IMG

Thanks buddy, got it figured out, iono why but I was using "fastboot flash..." instead of "fastboot boot..." all good now.

J
tommyxd said:
Thanks buddy, got it figured out, iono why but I was using "fastboot flash..." instead of "fastboot boot..." all good now.
Click to expand...
Click to collapse
Wait so it worked for you? What did you rename the file to and how did you load it in recovery?
Sent from my T-Mobile G2 using XDA App

Help! Stuck at "Welcome to PC36100"

Ok so, I was flashing CM7-GX4...everything was going fine until I flashed GAPPS, now I'm stuck at two screens alternating between the CM7 boot animation and the screen that says "Welcome to PC36100", upon this screen loading it quickly restarts the CM7 boot animation, so on and so forth. I am able to get into CWM recovery. Please help.
Thank you in advance.

thats a boot loop, looks like you want to wipe everything and try again

elegantai said:
thats a boot loop, looks like you want to wipe everything and try again
Click to expand...
Click to collapse
What if the PC36IMG file is renamed? I changed the name previously per the instructions of some thread I saw somewhere. Could this be the problem?

well you lost me at the hboot image. The only time i have ever had to use a file like that is when i was rooting my phone.
I also do not use cwm, so i am kinda limited in the help i can provide. Did you wipe your system/data/cache before you flashed cm7?

I wiped everything. I've put the SD card in another phone and renamed it back to PC36IMG...lets see what happens LOL

Renamed file back to PC36IMG...still stuck in boot loop

What exactly are you using the pc36img for?

elegantai said:
What exactly are you using the pc36img for?
Click to expand...
Click to collapse
I'm not using it for anything. It's just there from back when I rooted the phone. I had renamed it a while ago. Everything was going fine, install CM7 GX4 ROM, rebooted, attempted to install GAPPS and thats when I got stuck going back and forth between the two screens. I have put the SD card in another phone and renamed it to the original PC36IMG (figuring since I was stuck at a screen saying Welcome to PC36100 it couldnt find the file or something), and I'm still having the same problems. I've wiped and wiped and wiped using CWM and reinstalled CM7-GX4 several times and am still getting the same bootloop.

I'm running a restore from CWM...hopefully that will take me back to a point where I can do something.

yeah, you dont need the pc36img after you root so that is not the problem. My only guess is that cwm is not wiping everything properly or you are missing a step in the install process. I guess you can try a few things:
See if your cwm recovery is up to date (i know earlier versions had issues clearing out properly, but that has since been fixed)
Start back from the beginning of the install process with that rom. Make sure to wipe data, system, and cache, and go back through step by step (sometimes it is easy to overlook a step). Also i noticed in the rom you are using it says to make sure to flash the wi-max kernel, so make sure you do that.
Lastly, I have never used that rom, but if you do not need 4g you can try flashing the actual cyanogenmod nightlies. They are very stable (its what i am running now), and you can grab the latest nightly from:http://mirror.teamdouche.net and grab the gapps from: http://goo-inside.me (universal package)
Sorry to lay a crap load of info on you, but i just don't know what would cause it. A bootloop (which is what you are experiencing with the going back and forth between screens) basically means something did not install right and is making your phone restart over and over.

elegantai said:
yeah, you dont need the pc36img after you root so that is not the problem. My only guess is that cwm is not wiping everything properly or you are missing a step in the install process. I guess you can try a few things:
See if your cwm recovery is up to date (i know earlier versions had issues clearing out properly, but that has since been fixed)
Start back from the beginning of the install process with that rom. Make sure to wipe data, system, and cache, and go back through step by step (sometimes it is easy to overlook a step). Also i noticed in the rom you are using it says to make sure to flash the wi-max kernel, so make sure you do that.
Lastly, I have never used that rom, but if you do not need 4g you can try flashing the actual cyanogenmod nightlies. They are very stable (its what i am running now), and you can grab the latest nightly from: mirror.teamdouche.net and grab the gapps from: goo-inside.me (universal package)
Sorry to lay a crap load of info on you, but i just don't know what would cause it. A bootloop (which is what you are experiencing with the going back and forth between screens) basically means something did not install right and is making your phone restart over and over.
Click to expand...
Click to collapse
I ran the recovery and got back to an old point. I guess I'll try again! Weird that it happened after flashing GAPPS as everything was fine up until that point. I'll grab the gapps from your source. Thanks!

nooomoto said:
I ran the recovery and got back to an old point. I guess I'll try again! Weird that it happened after flashing GAPPS as everything was fine up until that point. I'll grab the gapps from your source. Thanks!
Click to expand...
Click to collapse
Well, i would only use the gapps from the link i provided if you are going to flash the official cm7 nightlies. I wouldnt mix and match! i surely don't want to cause further problems for you! lol. I was reading over that rom and I am not sure why you would need to reboot between installing the rom and the gapps. But again, not familiar with that version!
Sorry i couldnt help more hope you get it!

elegantai said:
Well, i would only use the gapps from the link i provided if you are going to flash the official cm7 nightlies. I wouldnt mix and match! i surely don't want to cause further problems for you! lol. I was reading over that rom and I am not sure why you would need to reboot between installing the rom and the gapps. But again, not familiar with that version!
Sorry i couldnt help more hope you get it!
Click to expand...
Click to collapse
I used the gapps from your source and everything went fine. Thanks again for the help!

no problemo, glad you got it working!

I will pay for a moto expert

To PM me and please help me with my Defy mess.... PLEASE

I'm assuming you are referring to being stuck in your bootloop now? Once I get home I'll write you an entire guide on how to unfubar it.

runeblade said:
I'm assuming you are referring to being stuck in your bootloop now? Once I get home I'll write you an entire guide on how to unfubar it.
Click to expand...
Click to collapse
Lol post it too... I would like to know how to combat bootloop aswell...

The fastest way, assuming that you have an external SD card reader and can put this file on your SD from your computer is the following:
Download This : TMobile Update Thanks to BeachHead for modifying it.
Once downloaded rename it to Update.zip.
Place in root of SDCard.
Hold the volume down button and turn the phone on. Press in the corner to get into the recovery mode. On the options select the update.zip. Let the process begin. The file is modified to not check for things. This will reload all of the firmware as well as the system. After that is done, do a factory reset. Your phone should now boot to 2.2 . If this does not work let me know and I'll do the more involved guide.

runeblade said:
The fastest way, assuming that you have an external SD card reader and can put this file on your SD from your computer is the following:
Download This : TMobile Update Thanks to BeachHead for modifying it.
Once downloaded rename it to Update.zip.
Place in root of SDCard.
Hold the volume down button and turn the phone on. Press in the corner to get into the recovery mode. On the options select the update.zip. Let the process begin. The file is modified to not check for things. This will reload all of the firmware as well as the system. After that is done, do a factory reset. Your phone should now boot to 2.2 . If this does not work let me know and I'll do the more involved guide.
Click to expand...
Click to collapse
I get:
"E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
Argh - HELP

I flashed the SBF 2.2 BOOT and it booted to the T-Mo screen which is where it is currently stuck. I'll give it a few minutes.

I got where you are at now. Download this SBF and flash it. http://www.multiupload.com/ZZ4TU8W7UQ
Its is the earlier leaked TMobile build. Once you have flashed this root your phone and install clockwork. Let me know when all of that is done. I should be done with dinner by then and can help the rest of the way. You will need the zip file I posted earlier as well as the 2.2 nandroid backup. Leave the Update.zip in the root of your sdcard, and put the nandroid backup in the apkrev folder on the sdcard. Once those are in place, boot into clockworkmod. Wipe system and cache. Then do a restore of the 2.2 Nandroid. Do not reboot yet. Now apply the update.zip. Do not reboot yet. Now do another system wipe. Now reboot the phone. You should be all set to go.

Dude it was actually fine. It loaded up and worked perfectly, I have FroYo and you are the man! Now I have a camera problem.
runeblade said:
I got where you are at now. Download this SBF and flash it. http://www.multiupload.com/ZZ4TU8W7UQ
Its is the earlier leaked TMobile build. Once you have flashed this root your phone and install clockwork. Let me know when all of that is done. I should be done with dinner by then and can help the rest of the way. You will need the zip file I posted earlier as well as the 2.2 nandroid backup. Leave the Update.zip in the root of your sdcard, and put the nandroid backup in the apkrev folder on the sdcard. Once those are in place, boot into clockworkmod. Wipe system and cache. Then do a restore of the 2.2 Nandroid. Do not reboot yet. Now apply the update.zip. Do not reboot yet. Now do another system wipe. Now reboot the phone. You should be all set to go.
Click to expand...
Click to collapse

I would try a reset to fix it. Many have had camera issues and that seems to be the fix.

Nothing.... What were the camera issues others had? I just get black, no matter what.

hah2110 said:
Dude it was actually fine. It loaded up and worked perfectly, I have FroYo and you are the man! Now I have a camera problem.
Click to expand...
Click to collapse
Woooah hold up you got it to load up by flashing what?? You said it was the 2.2 boot sbf? the one I told you to flash earlier?

ketonkss4 said:
Woooah hold up you got it to load up by flashing what?? You said it was the 2.2 boot sbf? the one I told you to flash earlier?
Click to expand...
Click to collapse
YES!!!!!!!!!!

You have to boot the right firmware. I realized that last night. You need to get that update.zip file to run and bring the proper firmware inline with the system image. I was screwing around last night playing with the different combos, and discovered that it wasn't mapping resources right. I lost use of my SD card.

hah2110 said:
YES!!!!!!!!!!
Click to expand...
Click to collapse
Awesome! I think im gonna go ahead and take credit for this one guys lol
And no you dont have to pay me your happy exclamation marks are pay enough!
^^

LOL!
Nice one ketonkss4!
ketonkss4 said:
Awesome! I think im gonna go ahead and take credit for this one guys lol
And no you dont have to pay me your happy exclamation marks are pay enough!
^^
Click to expand...
Click to collapse

Now someone fix my camera
Sent from my Nexus S using Tapatalk

Did you see my post about firmwares......the 2.2SBF is slightly older than the new rom. I suspect mappings have changed...update and see if that fixes it.

runeblade said:
Did you see my post about firmwares......the 2.2SBF is slightly older than the new rom. I suspect mappings have changed...update and see if that fixes it.
Click to expand...
Click to collapse
Ahhh yes that sounds like a legit fix... So he should just go into stock recovery and do the update.zip? well beach-head's update.zip

Yup. See earlier post. LOL

That update.zip from Beach never worked for me and still doesn't.... I don't understand. I still get verification failed.

flashing error

i didnt see anyone having this problem but got my gn and unlocked it yest, i came fr evo3d and we used to wiping everything n cache n dalvik so i tried to flash my first rom and im getting error " error in /sdcard/toro_aokp_b8.zip(status7) installation aborted assert failed:getprop(ro.product.device==toroII
i thought it was that rom but i tried flashing another rom and getting same message , if someone can help i appreciate it, i came fr the evo3d left sprint after 11yrs and woow what a difference in network, awesome network but im spoiled with rooting my ogevo n evo3d lol i love this phone hope i can fix this issue

Could you let us know what roms you've tried and the exact process you used please. Also are you using CWM?

RTContent said:
Could you let us know what roms you've tried and the exact process you used please. Also are you using CWM?
Click to expand...
Click to collapse
k first rom i tried AOSP 4.0.3ANDROID OPEN KANG PROJECT-TORO BUILD8 so i wiped data factory reset and cache n dalvik and flashed the rom, it looks like it starts to flash but aborts with the message above, then i restored my nan backup rebooted and went back to cwm to reflash the second time around i only wipe data factory reset cuz thats what the op says to do on his thread so i only wipe data factory n flash the rom still same error, so i went to try another rom GUMMYNEX 0.2.3 and i did the same process with both im following the steps their stating in the op in have cwm

From what the error sounds like is that it doesn't think you have the correct device. You have a CDMA phone and not a GSM?

RTContent said:
From what the error sounds like is that it doesn't think you have the correct device. You have a CDMA phone and not a GSM?
Click to expand...
Click to collapse
ui
yup, i got it fr verizon cdma, im starting to stress man, ive been so used the rooting world n having custom roms i dont know how i could do without it lol, i hope i can get this issue resolve

Flip35 said:
ui
yup, i got it fr verizon cdma, im starting to stress man, ive been so used the rooting world n having custom roms i dont know how i could do without it lol, i hope i can get this issue resolve
Click to expand...
Click to collapse
sure you are using the lastest CWM???
sure you are rooted??
did you try downloading the files from another puter??

i think i might know what the problem is my cwm says 5.5.0.2 and im looking here at somebody posted in the development section for a cdma cwm and it says 5.5.0.4 could that be the problem? if so how do i redo my recovery, follow the same steps i did my first one, i downloaded and extracted the files to my c drive and opened cmd and typed the commands, can i do that again while having already cwm to flash the new cwm on top of the old one? if thats the problem

Download rom manager. Then you can flash it while your booted in android.

RTContent said:
Download rom manager. Then you can flash it while your booted in android.
Click to expand...
Click to collapse
how ive never flashed cwm using rom manager, u meand download the file of cwm5.5.0.4 putting in the root like i do any rom and go into rom manager and install?

No just download the app Rom Manager. It will download the latest version and flash it with a single click within this app!

RTContent said:
Download rom manager. Then you can flash it while your booted in android.
Click to expand...
Click to collapse
wooooord, aight RTcontent good looking out, i guess when u said it looks like it sound it was reading my phone wrong was right, i had a gms cwm, thanx man used rom manager and since i put the new cwm in my root of sdcard when i press install cwm it automatically update it without even booting into recovery but just finished intalling a rom and IT WORKED!!!! UR DA MAN im excited thanx

Bell GT-S5660M Bricked

Trying to install CM9 ICS on two Gio GT-S5660M from Bell, one is working but the other just boot/flash SAMSUNG (not the Samsung GIO) screen, therefor i can not go back into the CWM (recovery) ... i only can go to download mode; Emergency Download.
I have flashed all ROM i know and read all the unbrick (One-click-Unbrick do not detect it) and still not able to reflash it ... do you thing it is a done deal and need to be services?
Thanks
Oh! the other one that run CM9-ICS, how do you get back to stock since the files systems is now difference, and flash stock via Odin only get it to boot loop.

After flashing with odin, you need to wipe data too.
For your brick, install ADB, search xda how.
Then do
Adb reboot recovery
Or
Adb reboot download
Sent from my GT-S5660 using xda premium

voetbalremco said:
After flashing with odin, you need to wipe data too.
Click to expand...
Click to collapse
I already did that, but i think the Stock do not reformat the Files system?
For your brick, install ADB, search xda how.
Then do
Adb reboot recovery
Or
Adb reboot download
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
adb cannot find the device (adb devices)
Thanks

y2k-inc said:
I already did that, but i think the Stock do not reformat the Files system?
adb cannot find the device (adb devices)
Thanks
Click to expand...
Click to collapse
Ohhhhh that's right! When you come from the new roms these days, it formats your device to EXT4. So if you try to go back to RFS (Stock), the phone bootloops.
ADB needs the phone to be turned on and running for it to work.
Darkshado, any help here?

Sure, here's a really quick reply:
If you want to reformat your /data and /cache partitions to RFS, here are empty RFS images you can dd into place.
http://www.mediafire.com/?mfa671ly79w0zc6
(I'll have to make an update zip out of those someday.)
Good luck,
Darkshado

Darkshado said:
Sure, here's a really quick reply:
If you want to reformat your /data and /cache partitions to RFS, here are empty RFS images you can dd into place.
http://www.mediafire.com/?mfa671ly79w0zc6
(I'll have to make an update zip out of those someday.)
Good luck,
Darkshado
Click to expand...
Click to collapse
Thanks Darkshado & Peteragent5, i will try out to DD it over my ICS one, but for the Bricked one, anyone have any ideal how to fix it? lock like ODIN flash to rom, but the memory inside these phone is protected, therefore it won't write any update to it ... i got one Xoom doing to samething, wondering if the write cycle of the ROM/WRAM has been reached?
I have also tried to use Odin Debug and PDA format but Odin crashed!
Thanks

gioM is diffrent from gio so it has diffrent chip

Using Darkshado empty RFS images just fine, but cannot restore to the stock firmware for Unlock All other firmware than the GalaxyICS-UNOFFICIAL-beta8 rom it's all end up in boot loop
For the other Gio, i just bring it to the Samsung center in MTL and they said it's under warranty and will fix it.

Can you get Odin to work on the "first" Gio?
If so, once you've restored the RFS data and cache partitions, flash the stock backup ROM with Odin. I don't see any obvious reason this should leave you boot-looping. (ddms should give some clues if i does...)
Otherwise, and maybe easier even, just dd system.rfs and boot.img back into place from recovery.
ArpegGioMod, even the ext4 0.9 version, allows SIM unlocking as it is a stock-based ROM. A factory reset with it might even perform the unlock due to the modified CSC files.

Thanks Darkshado, but every time i installed a ROM (other than the GalaxyICS), my efs folder is blank ... wondering if i can restore a NAND from another GIO to this one
Thx

Some stuff you're not telling us here then...
What did you do, SIM unlock-wise?

Darkshado said:
Some stuff you're not telling us here then...
What did you do, SIM unlock-wise?
Click to expand...
Click to collapse
Not much that i have not mentioned, but here is how it's get started; it was my father phone, brand new from Solo, got it to root it, but got into boot loop, so saw a new version 2.3.6 and updating it, just to find out it not for the "M" version, so what the heck, since it's already got a wrong version on it, why not flash it with the GalaxyICS ... yeah, it's great working, but i got No Service, oh! sh!t no problem, going to flash back to the stock "M" version, cannot, only got boot loop ... ok ... flashed to your version? still boot loop ... now flashed back to ICS ... working just fine but got "no service" ... there it's at GalaxyICS right now and cannot go back ...
for the other that i will pickup today, same thing happened, but this time i won't play with it, since i need at least a working phone so sent it to service and its ready to pickup today, look like that replacing it with a new one. So i was wondering if i backup the NAND from that replacing one and flash it to this one will i got it back?
I just want to keep one for playing/learning the Android, so it's OK if i f$xk up this one, warranty it's still good until Nov. 2012
Thanks

y2k-inc said:
Not much that i have not mentioned, but here is how it's get started; it was my father phone, brand new from Solo, got it to root it, but got into boot loop, so saw a new version 2.3.6 and updating it, just to find out it not for the "M" version, so what the heck, since it's already got a wrong version on it, why not flash it with the GalaxyICS ... yeah, it's great working, but i got No Service, oh! sh!t no problem, going to flash back to the stock "M" version, cannot, only got boot loop ... ok ... flashed to your version? still boot loop ... now flashed back to ICS ... working just fine but got "no service" ... there it's at GalaxyICS right now and cannot go back ...
for the other that i will pickup today, same thing happened, but this time i won't play with it, since i need at least a working phone so sent it to service and its ready to pickup today, look like that replacing it with a new one. So i was wondering if i backup the NAND from that replacing one and flash it to this one will i got it back?
I just want to keep one for playing/learning the Android, so it's OK if i f$xk up this one, warranty it's still good until Nov. 2012
Thanks
Click to expand...
Click to collapse
Did you wipe after flashing stock?
Verstuurd van mijn GT-S5660 met Tapatalk

lemmymet said:
Did you wipe after flashing stock?
Verstuurd van mijn GT-S5660 met Tapatalk
Click to expand...
Click to collapse
Of cause i did, event before and then after flash all other firmware
Thanks