Database Users

Flashing Rom always ends in boot loop?

I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.

By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app

redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm

could that be the problem? that my cwm is just outdated already?

No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium

CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.

Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7

am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?

crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.

simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?

I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?

spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?

Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.

dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?

If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2

Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!

my A501 seems write protected

hi all,
I have a strange and very painfull problem : I can't modify anything into my ACER A501
wipe system/cache/etc said success but seems doing othing
reset factory same
try to install new ROM (thor JB) the installation start and go to the end successfully but when i reboot I am yet on my old ROM.
install new application ok but when i reboot application are gone.
I have
bootloader Skrilax V8
twrp 2.1.3
FLexreaper ICS ROM
What can I do?
thanks

gerardpuducul said:
hi all,
I have a strange and very painfull problem : I can't modify anything into my ACER A501
wipe system/cache/etc said success but seems doing othing
reset factory same
try to install new ROM (thor JB) the installation start and go to the end successfully but when i reboot I am yet on my old ROM.
install new application ok but when i reboot application are gone.
I have
bootloader Skrilax V8
twrp 2.1.3
FLexreaper ICS ROM
What can I do?
thanks
Click to expand...
Click to collapse
Try installing CWM recovery. Either 1.7.2 or 1.7.3. Then do your wipes and formats.
MD

Moscow Desire said:
Try installing CWM recovery. Either 1.7.2 or 1.7.3. Then do your wipes and formats.
MD
Click to expand...
Click to collapse
Thanks
i have try to install CMW recovery :
with TWRP from zip : process seems ok but when i reboot i am still under twrp
with acer recovery installer v3.03 : process said ok too but same issue. Just a remark it don't success to retrieve information about my installed recovery
thks

[Q] What to do after a brick?

Hello everyone.
I hope you can help me.
I had an A500 bricked spontaneously (I was checking Twitter, the screen frozen, I turned off the tablet and when I turned it on again, it stucked on Acer logo) so I used the guide to recover recovery (this: http://forum.xda-developers.com/showthread.php?t=1751978, because I rooted my tablet but I didn't install recovery).
Everything was ok, I flashed the V7-Thor v1.7.3 but when I tried to install stock ROM of ICS (wipe data and cache), the tablet got "re-bricked" and only enter in APX mode.
Then I reflashed and installed V8-Thor_1.7.3_recovery and I tried to install Acer_AV041_A500_1.054.00_WW_GEN1-DEODEXED-FULLROOT through update.zip (turned on the tablet in recovery --> Install from zip file --> Install zip file from SD card --> update.zip, then it said "Installed" and I rebooted the tablet, but it stuck on "Booting primary kernel image"...
What I'm missing or doing wrong? :/
What should I do to run ICS in my tablet again?
I'm not familiarized with the ROMs, Recoverys or flash... sorry if my question is stupid or something, but before this I never moved anything to my tablet (except for root it).
And sorry too for my bad English.

Mafvtapatio said:
Hello everyone.
I hope you can help me.
I had an A500 bricked spontaneously (I was checking Twitter, the screen frozen, I turned off the tablet and when I turned it on again, it stucked on Acer logo) so I used the guide to recover recovery (this: http://forum.xda-developers.com/showthread.php?t=1751978, because I rooted my tablet but I didn't install recovery).
Everything was ok, I flashed the V7-Thor v1.7.3 but when I tried to install stock ROM of ICS (wipe data and cache), the tablet got "re-bricked" and only enter in APX mode.
Then I reflashed and installed V8-Thor_1.7.3_recovery and I tried to install through update.zip (turned on the tablet in recovery --> Install from zip file --> Install zip file from SD card --> update.zip, then it said "Installed" and I rebooted the tablet, but it stuck on "Booting primary kernel image"...
What I'm missing or doing wrong? :/
What should I do to run ICS in my tablet again?
I'm not familiarized with the ROMs, Recoverys or flash... sorry if my question is stupid or something, but before this I never moved anything to my tablet (except for root it).
And sorry too for my bad English.
Click to expand...
Click to collapse
I think where you went wrong was choosing "install zip file from sdcard >update.zip"
Go back into recovery again > install from zip file > Choose zip from SD card (
if the file is on your micro sd card)
You should see a list of all your files and choose your rom file:
Acer_AV041_A500_1.054.00_WW_GEN1-DEODEXED-FULLROOT.zip
Once its done, Stay in recovery and go to: Wipe Menu and do all the wipes there
Data -cache and dalvi-cache then reboot
Once you're all set up and before you reboot again, make sure there is not an "update.zip" on your sdcard - if you boot to recovery it may flash automatically and you will end up "stuck" again
good luck
dibb

dibb_nz said:
I think where you went wrong was choosing "install zip file from sdcard >update.zip"
Go back into recovery again > install from zip file > Choose zip from SD card (
if the file is on your micro sd card)
You should see a list of all your files and choose your rom file:
Acer_AV041_A500_1.054.00_WW_GEN1-DEODEXED-FULLROOT.zip
Once its done, Stay in recovery and go to: Wipe Menu and do all the wipes there
Data -cache and dalvi-cache then reboot
Once you're all set up and before you reboot again, make sure there is not an "update.zip" on your sdcard - if you boot to recovery it may flash automatically and you will end up "stuck" again
good luck
dibb
Click to expand...
Click to collapse
Thanks! I did it and it worked, but after the reboot the tablet only shows the animated android logo... what's the problem? The ROM?
When I did the "Wipe data" it said "Formatting data" and after "Skipping erase of /data/media". I checked with the "Mount and Storage" menu in recovery and seems like my data before the brick's still in the internal storage of the tablet... is that normal?

EDIT: what version of cwm to have now? If its not 1.7.3 then go ahead and reflash the v8
Mafvtapatio said:
Thanks! I did it and it worked, but after the reboot the tablet only shows the animated android logo... what's the problem? The ROM?
When I did the "Wipe data" it said "Formatting data" and after "Skipping erase of /data/media". I checked with the "Mount and Storage" menu in recovery and seems like my data before the brick's still in the internal storage of the tablet... is that normal?
Click to expand...
Click to collapse
Yes it is - keeps your data intact but 'resets' the rom to like it is when you first flash, there is an option to wipe data/media if you wish to - theres a toggle to enable it but on every boot to recovery it will be disabled again...
You can try another flash of the rom itself otherwise reflash the v8 bootloader.
Do you have access to "fastboot mode" power vol down - just wondering
dibb

dibb_nz said:
EDIT: what version of cwm to have now? If its not 1.7.3 then go ahead and reflash the v8
Yes it is - keeps your data intact but 'resets' the rom to like it is when you first flash, there is an option to wipe data/media if you wish to - theres a toggle to enable it but on every boot to recovery it will be disabled again...
You can try another flash of the rom itself otherwise reflash the v8 bootloader.
Do you have access to "fastboot mode" power vol down - just wondering
dibb
Click to expand...
Click to collapse
I tried to reflash the same ROM, but this time nothing happened, again only says "Booting primary kernel image"... a question, if I try to flash a stock ROM (like Acer_A500_1.031.00_WW_GEN1.zip from the post of stock roms)... it will let my tablet again only in APX mode when I turn on it, right?
And I see the option "Fastboot mode" when I turn on the tablet holding Vol +.
About your question I don't know how to answer, I flashed V8-Thor_1.7.3_recovery... is that a CWM?
In the top it says CWM Recovery v5.5.0.x(thor2002ro/digetx rev 1.7.3) Iconia A50x...

Mafvtapatio said:
a question, if I try to flash a stock ROM (like Acer_A500_1.031.00_WW_GEN1.zip from the post of stock roms)... it will let my tablet again only in APX mode when I turn on it, right?
Click to expand...
Click to collapse
sorry, not sure I understand your question...are you saying you're now stuck in apx mode - black screen power light on?
There are 2 types of stock rom on here....
1) Official Acer EUU or OTA roms
2) Official Stock roms which are Custom - pre-rooted and able to flash CWM etc -
If you flash one of the Acer EUU or OTA roms you will lose CWM and Root
To be honest - with your tab "spontaneously" booting and being stuck on the acer logo and the issues that have followed - its sounding more and more like a faulty chip - this is something that only acer can fix...I could be wrong about this and I hope I am...but something is just not feeling right...
- you still have cwm and access to fastboot - thats a bonus - maybe do a complete format thru CWM of data/media, system (and flexrom if its there) then try to flash a rom again - if it still won't flash AND if you're not stuck in apx mode then I think you'd be best to download an official update.zip - from Blackthund3rs thread here this one -
Acer_AV041_1.054.00_WW_GEN1:
Once you've d/l'ed it...try opening it if you can't then it will need decrypting the instructions for this are in the OP..
Once you have extracted the "update.zip" and have it on your sdcard - flash via CWM
good luck
dibb

dibb_nz said:
EDIT: what version of cwm to have now? If its not 1.7.3 then go ahead and reflash the v8
Yes it is - keeps your data intact but 'resets' the rom to like it is when you first flash, there is an option to wipe data/media if you wish to - theres a toggle to enable it but on every boot to recovery it will be disabled again...
You can try another flash of the rom itself otherwise reflash the v8 bootloader.
Do you have access to "fastboot mode" power vol down - just wondering
dibb
Click to expand...
Click to collapse
What do you mean "If if its not 1.7.3"? Are there problems with flashing the bootloader with 1.7.3?

no, no, not at all, i meant if he didnt have that version to reflash v8 to get it
oops clicked wrong button
he said he flashed stock rom and ended up with dead android = stock recovery

A500 V8 booting primary kernel image
dibb_nz said:
no, no, not at all, i meant if he didnt have that version to reflash v8 to get it
oops clicked wrong button
he said he flashed stock rom and ended up with dead android = stock recovery
Click to expand...
Click to collapse
Hello everyone!
I have a similar issue whith my a500. but i can restore the backup i did of my honeycomb sistem in cwm (i have acess)
aftter making the backup i have flashed V8-Thor_1.7.3_recovery.a500apx in apxflashtool in order to get ics boot loader and install ICS roms.
so far so good after the flash i had already a ICS rom in my sd card redy to flash so imediatly after V8 flash entered cwm and did clean format and wipe all. Next installed the rom (aroma instalation) no problems what so ever. After instalation is finished reboted and now im stuck on skilax v8 bootloader boting primary kernel image
i tried the folowing
- chage kernel multiboot fix partitions redo clean format etc etc etc (ALL THE STEPS)
-many other ics jellybean rooms (all of the install but dont boot)
- honey comb rooms install and BOOT normaly.
at this point thought maybe it was a bad V8 flash and decided to reflash the V8-Thor_1.7.3_recovery.a500apx
Now the flash tool can get pass uploading image phase.
i have correct sbk and cpuuid since i had to recover last week from boot verified failed error and use the flash tool whith correct sbk to recover the tablet with sucess.
So basicly im stuck wit
h my honeycomb rom backup or other HC roms
any news on this subject?

cybersaicho said:
Hello everyone!
I have a similar issue whith my a500. but i can restore the backup i did of my honeycomb sistem in cwm (i have acess)
aftter making the backup i have flashed V8-Thor_1.7.3_recovery.a500apx in apxflashtool in order to get ics boot loader and install ICS roms.
so far so good after the flash i had already a ICS rom in my sd card redy to flash so imediatly after V8 flash entered cwm and did clean format and wipe all. Next installed the rom (aroma instalation) no problems what so ever. After instalation is finished reboted and now im stuck on skilax v8 bootloader boting primary kernel image
i tried the folowing
- chage kernel multiboot fix partitions redo clean format etc etc etc (ALL THE STEPS)
-many other ics jellybean rooms (all of the install but dont boot)
- honey comb rooms install and BOOT normaly.
at this point thought maybe it was a bad V8 flash and decided to reflash the V8-Thor_1.7.3_recovery.a500apx
Now the flash tool can get pass uploading image phase.
i have correct sbk and cpuuid since i had to recover last week from boot verified failed error and use the flash tool whith correct sbk to recover the tablet with sucess.
So basicly im stuck wit
h my honeycomb rom backup or other HC roms
any news on this subject?
Click to expand...
Click to collapse
Yes just one question what is - " chage kernel multiboot "???? Sounds dodgy
You can boot to fastboot mode then do an erase of data and cache, see if that helps for a start....
Do you stil have recovery and can you still restore your HC backup?
I have seen a post or two where tabs can only boot HC Roms and no ICS
It "maybe" the dreaded hardware fault - you might be best to d/l the babsector.rar and run that - it will give you a proper error if theres something wrong - can get it from the root guide in my sig. Give me a minute or two and I'll post some steps in using it
---------- Post added at 09:12 AM ---------- Previous post was at 08:53 AM ----------
How to use babsector.rar
Download and extract the babsector.rar to a folder on your PC
Turn your tab off and put it in apx mode manually. Press and hold reset button, hold power for 3 secs after the light comes on and release it, after another second release the reset button. Your screen is black and the power light is on.
Connect your tab to your PC
Navigate to the babsector folder and click on 501 A.bat, when its done
Reboot into recovery
Go to Mounts and Storage and Format System twice and Power Off
Go back into apx mode and run 501 B.bat
Reboot into recovery and do the wipes and flash your rom
Reboot

Can't flash any rom

Any reason why no ROM works since I flashed 4.3? It will flash, but won't go past boot screen, tried 10.2 infamous, slim bean, and pa. Wtf?
Sent from my Nexus 7 using xda app-developers app

What steps are you taking when you are flashing these roms? I haven't had an issue yet.
Sent from my Nexus 7 using xda app-developers app

wipe wipe wipe..
if youre coming from stock, you must wipe data/factory reset before flashing the rom. aosp and stock are different at this point.

For the 4.3 rom flash, did you also flash the new radio and bootloader. Also, be sure that the md5 of the rom you downloaded is correct; happened to me a couple of times.

i also have trouble in flashing ROM. It won't installed and on the recovery mode it said, "no command".
Helppp!

farraas said:
i also have trouble in flashing ROM. It won't installed and on the recovery mode it said, "no command".
Helppp!
Click to expand...
Click to collapse
To Flash any rom
Steps:
1.Download latest bootloader and radio.(If you came from stock 4.3,Skip this step)
2.Donwload your Rom and latest GAAPS.
3.Save all the downloaded .zip files in a folder on your nexus 4.(Any folder)
3.Reboot your cell in CWM or TWRP recovery..That is switch off your cell and then press Vol up(+) Vol down(-) and power button all at the same time for 5 sec (you can flash CWN or TWRP through nexus 4 toolkits)
4.Do factory reset and clear Dalvik cache
5.Flash bootloader and radio (Skip if you came from stock 4.3)
5.Flash your downloaded rom (.zip file)(Go to Install .zip from SD card option and go to the folder where you have downloaded the rom)
6.Flash GAPPS (.zip file)(Go to Install .zip from SD card option and go to the folder where you have downloaded the GAAPS)
7.Wipe cache and dalvik cache
8.Done.Enjoy your Rom

Thanks brother. I wasn't factory restoring and that was my prob.

SGY bricked while flashing ROM help plz

Hlo. I was recently trying to install new Custom ROM(ROM thread in link) I did these steps.
1. Boots into stock recovery
2. Boots into CWM recovery via .zip file.
3. Cleared Data Factory reset, Clear dalvik cache and clear battery stats.
4. Flashed ROM file(it was successfull)
Then I reboot the device and it is stuck on Samsung Galaxy Y logo screen.
I dont know what happened wrong(also i followed steps said by rom owner)
Hele plzz.http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=39672880
Sent from my GT-S5660

mjobanjatt said:
Hlo. I was recently trying to install new Custom ROM(ROM thread in link) I did these steps.
1. Boots into stock recovery
2. Boots into CWM recovery via .zip file.
3. Cleared Data Factory reset, Clear dalvik cache and clear battery stats.
4. Flashed ROM file(it was successfull)
Then I reboot the device and it is stuck on Samsung Galaxy Y logo screen.
I dont know what happened wrong(also i followed steps said by rom owner)
Hele plzz.http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=39672880
Sent from my GT-S5660
Click to expand...
Click to collapse
The rom mentioned is cm7 based
you need to be on percys cm#2 kernel - search dev section for his cm7 thread and it's on the 1st page

it was a kernel problem i think....
try hells fusion just after flashing
JUST PRESS THANKS IF I HELPED...

CHK IT HERE:
ESPECIALLY FR BRICKED DEVICES:
http://forum.xda-developers.com/showthread.php?t=1600373

mjobanjatt said:
Hlo. I was recently trying to install new Custom ROM(ROM thread in link) I did these steps.
1. Boots into stock recovery
2. Boots into CWM recovery via .zip file.
3. Cleared Data Factory reset, Clear dalvik cache and clear battery stats.
4. Flashed ROM file(it was successfull)
Then I reboot the device and it is stuck on Samsung Galaxy Y logo screen.
I dont know what happened wrong(also i followed steps said by rom owner)
Hele plzz.http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=39672880
Sent from my GT-S5660
Click to expand...
Click to collapse
To this procedure:
Flash stock rom via odin
Go to cwm
Mount all system,data,cache
Flash cyanogenmod#2/Jarvis-CM v1.2 #2 kernel
GO to advance Reboot recovery
You will see small fonts
Go to mount and storage
Format system,data,cache
Mount all of them again
Flash cm7 based rom
Wipe data
Reboot system
Press thanks if i helped:good:

You forgot to mount "/system"
Sent from from from from, PSHHHHHGHGHGHGGGGGGGGHHHHH , AIOOOOOOOOooooo0

Reply
mjobanjatt said:
Hlo. I was recently trying to install new Custom ROM(ROM thread in link) I did these steps.
1. Boots into stock recovery
2. Boots into CWM recovery via .zip file.
3. Cleared Data Factory reset, Clear dalvik cache and clear battery stats.
4. Flashed ROM file(it was successfull)
Then I reboot the device and it is stuck on Samsung Galaxy Y logo screen.
I dont know what happened wrong(also i followed steps said by rom owner)
Hele plzz.http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=39672880
Sent from my GT-S5660
Click to expand...
Click to collapse
First fLASH cwm then wipe data wipe cahe and mount everythings then flash the kernal the mount everything the flash the rom
.If i help u pls give thanks:good:

Try Flashing Stock Rom via Odin then flash ur custom rom again..
To flash stock rom via odin ..please search it in google Im sure theres more responding sites to help..
Please Press Thanks if I helped
Sent from my GT-S5360

Like
markjerald said:
To this procedure:
Flash stock rom via odin
Go to cwm
Mount all system,data,cache
Flash cyanogenmod#2/Jarvis-CM v1.2 #2 kernel
GO to advance Reboot recovery
You will see small fonts
Go to mount and storage
Format system,data,cache
Mount all of them again
Flash cm7 based rom
Wipe data
Reboot system
Press thanks if i helped:good:
Click to expand...
Click to collapse
this is the right procedure ,i perceive just follow this