Database Develop

[Q] Stuck in CWM recovery after Doc ROM install, help?

First of all I hope this is in the right place: I did do a search but still couldn't find any help.
Here's my problem:
After getting a (delicious) taste for customisation after rooting and lagfixing, I decided to give custom ROMs a go. Hours of indecision passed and ultimately I settled on Doc and Stefunel's magical ROM. Due to currently being on 2.1, I chose to follow the set of instructions provided on the page for doing so.
All was well up until the very final step. When rebooting the phone through ClockworkMod Recovery, instead passing the Samsung boot screen into the Android system, the phone boots into CWM recovery. I've tried doing another factory reset, and reinstalling the ROM to no avail. I've also tried mounting "/mnt/sdcard" in order to place another ROM to flash from, but I keep getting a message telling me to insert a disk (what happens when you don't mount).
That's pretty much all there is to it. I'd be massively grateful for any help!
-anti

If you have made a backup of your apps then flash the JPY with Odin and then make factory reset in recovery mode. Then root with CF Root 1.3 (Or something like that) and flash CWM Recovery. That's what I would do.
Sent from my GT-I9000 using XDA App

from the recovery menu try wipe cache and dalvik, and reboot

Weird problem when flashing CM7 Help!

Hi,
I have many times tried to flash CM7, but always happens weird thing.
I have stock 2.3.5 XXJVS with Semaphore 2.5.0 kernel
1.I boot into CWM
2.I wipe cache then wipe data/factory reset then i go advanced and choose wipe Dalvik cache
3.Choose .zip from sd card
4.I choose update-cm7.1.0-GalaxyS-signed.zip
5.My phone flashes it
6.It reboots
7.Normal Galaxy S GT-i9000 then Galaxy S
Cyanogen Mod
8.It goes to recovery and posts text very fast then reboots again
9.It repeats everything what it does from section 7.
Im very confused so please help!

Have you tried flashing it again?

redo step 3 and onwards,
sometimes you just need to flash twice.

It seems like a corrupted download... Are you flashing from internal or external? Have you mounted before?

i tried to flash from internal

What version of CWM recovery do you have? Maybe flash a different ROM just to update CWM, and then flash the rom you want?

I had the same, or atleast a similar problem whilst trying to flash CM9. I fixed it by flashing the rom again.
You also might want to redownload the file incase it's corrupt.

i have CWM 5.0.2.7 and i downloaded the CyanogenMod file again so i try to flash it again

Any luck with your efforts this far?

yes, i succesfully installed CM9 about 3 months ago.
I'm not sure which build it was but it was the newest build

[SOLVED] Am I bricked? PLEASE help me :(

Hi guys. I'm quite a noob, but have a good experience on flashing without be bricked (CM9, CM10, Crash, Paranoid...), but I have a problem.
I will explain to you step-by-step what I've done with my Note, so I wish some of you could help me.
1) I was running JB Crash ROM with PhilZ kernel.
2) Some apps got Force Close too often, so I went on Rom Manager and, after a look into the "Fix permissions" description ("It will fix some force closes" or something like that), I decided to give it a try and I tapped on it.
3) After that, my homescreen became unusable, because "TouchWiz Home" got EVERY TIME force closed without reason. Everything else worked fine, so I deciced to boot into CWM recovery to restore a nandroid backup of the same ROM.
4) Instead of tapping "restore", I tapped "backup" (my fault) and it started without possibility of get back. I got something like 200 Mb of free space, so in every case it will never have had success. My Note stucked at this point, so I decided to reboot manually (vol up+home+power) into recovery. Finally I tried to "restore" but I get this message: "ERROR WHILE RESTORING /SYSTEM".
5) I tried to reboot my Note, but it stucks at "Samsung Galaxy Note GT-N7000" screen without going on.
The good news is that it can go without problems into recovery and into download mode. What can I do? Flashing from CWM, for example, CM9 can fix this?
Please help me thanks!

1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....

friedje said:
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
Click to expand...
Click to collapse
After formatting /system, can I try to restore my nandroid backup? Or I have to necessary reflash my ROM? In that case, it's the same thing make it via CWM or via ODIN PC? I'm still on PhilZ recovery, which is safe I guess!
Anyway, thanks for your help

Via CWM or Odin, depends if you have your rom in the zip or the md5.tar format.
I would reflash to be clean. It's a bit more work in restoring your apps and data
afterwards, but at least you don't restore any messed up files.

if you can still access CMW and Download Mode then you probably are not brick... try fresh install through pc odin.. safe method no need to worry about bricking by fullwiping on unsafe kernel or raising triagle or binary counter whatsoever.. if you wanna play safe then PC ODIN and after that you can root your rom

Thank you guys, now I'm on stock ICS flashed via PC Odin and everything works fine I knew I was 99% not-bricked (still recovery and download mode avaiable), but I was a little scared too.
Thank you again!

glad you solved it.. :good:

[Q] Need help flashing

Just got my Galaxy S back from my Mum today (After I bricked it and sent for repair) she got a note2 omg... Decided to flash a custom rom..
Here goes..
First I followed this guide completelyhttp://http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. After I flash the CM 10, my recovery was upgraded to v6.0.1.5 after reboot. But I cannot get pass the recovery. I will have the cm boot animation, then back to recovery again. Tried reflashing the rom, doesnt say any errors but still gets stuck at recovery.
Then I went thru the method at the wiki.cyanogenmod again and successfully flashed cwm recovery 2.5 again. Tried flashing the CM10 rom again but this time round, It shows a long error message ending with "status 7"
I am still able to go into download mode.
Was on stock unrooted 2.3.3 DXJV9.
I made the super no.1 noob mistake of not making a backup........... But, why is rooting and flashing of this phone so hard.....
Pls, any help is greatly appreciated.

Btw, I have manage to flash the stock image via odin but is still stuck in a boot loop.. after Odin completed and reboot, I am back into the stock recovery with the below error messages.

It will work
scpion said:
Btw, I have manage to flash the stock image via odin but is still stuck in a boot loop.. after Odin completed and reboot, I am back into the stock recovery with the below error messages.
Click to expand...
Click to collapse
When u see red error message in stock recovery........u just wipe cache and reboot.......it will work.....

i have wiped everything many times over. but I am still stuck in the bootloop. the red error messages looked serious though.

try this
scpion said:
i have wiped everything many times over. but I am still stuck in the bootloop. the red error messages looked serious though.
Click to expand...
Click to collapse
U just use GB jw4(your region) ROM (don't use single file like PDA).........you use files separately like this [PDA,phone,CSC,pit(512 or 513)]...............use Odin 1.85 for flashing files......,when u complete the flashing it automatically reboot to fulfill the flashing...........then also it gives red error means........ clear only wipe cache and don't clear wipe all data...........reboot your system..... I think this will work for u...........:fingers-crossed:

Thanks. Have it solved. Flashed with another rom with seperate files. I was using the the all in one previously. Got it to run CM10 nightly though till now still not too sure how... But, I m real happy now. It works great so far and I couldnt understand why Sammy refuse to roll out official ones even for 4.0..
Still trying to figure out how to root, flash SGS though.. I have done so for many other device but by far,... this phone is the most complicating....

Aj rocker root
By processor only we not getting stock ICS rom but we getting custom ROM by hacking processor.............
For rooting the ROM u want to be in stock GB ROM like 2.3.5 or 2.3.6 and then u want to download this file(http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip)............. after download u want to open Odin 1.85 and select PDA then choose the downloaded file...........select start to flash the file.........reboot and enjoy the root bosssss......if u like this press thanks:fingers-crossed:

Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?

Try to see if you can flash another custom Rom, if that works then it could be that your files are corrupted..
Have you stated your problem over at CM forums..
# Sent from my blazing slimbean SGS i9000 using Tapatalk 2 #

scpion said:
Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?
Click to expand...
Click to collapse
OK fine first u want to know something boss......... every firmware having different layout........ correct procedure of flashing is u want to go step by step for enjoy the full features of the ROM ....... u r in GB ROM means then next u want to go ICS ROM........If u r in ICS ROM means then next u want to go jellybean rom and this the correct procedure to use new ROM without the problems...........:good:

scpion said:
Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?
Click to expand...
Click to collapse
OK fine first u want to know something boss......... every firmware having different layout........ correct procedure of flashing is u want to go step by step for enjoy the full features of the ROM ....... u r in GB ROM means then next u want to go ICS ROM........If u r in ICS ROM means then next u want to go jellybean rom and this the correct procedure to use new ROM without the problems...........:good:

Most times from GB to JB u have 2 flash custom 2, 3 times. So its normal when flashing custom the first time it takes u to bootanimation and hangs (take out battery and go to recovery with 3 button combo and flash again till it says install is completed) or directly into recovery.
If u wanna flash other jb rom just full wipe and flash new custom. Make sure u make a nandroid backup so u can go back easily

CWM Recovery Won't Install

I'm following this tutorial on how to root my Orange UK GT-I9305 LTE Unlocked phone running 4.1.2.
Everything goes fine with Odin the phone reboots, then I unplug and turn off my phone, and boot into recovery mode only to find it hasn't installed and Android system recovery 3e is still there.
Any ideas what I'm doing wrong?

synthecypher said:
I'm following this tutorial on how to root my Orange UK GT-I9305 LTE Unlocked phone running 4.1.2.
Everything goes fine with Odin the phone reboots, then I unplug and turn off my phone, and boot into recovery mode only to find it hasn't installed and Android system recovery 3e is still there.
Any ideas what I'm doing wrong?
Click to expand...
Click to collapse
Not flashing as instructed is the usual .Like unzipping the file or wrong file faulty file download .
Try another recovery.
jje

JJEgan said:
Not flashing as instructed is the usual .Like unzipping the file or wrong file faulty file download .
Try another recovery.
jje
Click to expand...
Click to collapse
I did follow them to the letter, does installing CWM Recovery actually root the phone or is "rooting" the phone a different process entirely that's required for installing CWM Recovery?.
:laugh:
Phone: Samsung Galaxy S3 LTE
Model Number: GT-I9305
Build Number: JZO54K.I9305XXBMF1

synthecypher said:
I did follow them to the letter, does installing CWM Recovery actually root the phone or is "rooting" the phone a different process entirely that's required for installing CWM Recovery?.
:laugh:
Phone: Samsung Galaxy S3 LTE
Model Number: GT-I9305
Build Number: JZO54K.I9305XXBMF1
Click to expand...
Click to collapse
All depends upon the package but most CWM are root and recovery .
TRYhttp://forum.xda-developers.com/showthread.php?t=2002953

Ended up using Auto-Root which seemed to work no problem.

synthecypher said:
Ended up using Auto-Root which seemed to work no problem.
Click to expand...
Click to collapse
I initially had a rooted stock ROM that i was using for ages then upgraded to a custome ROM but for personal reasons decided to go back to stock.
Loaded stock ROM with intention of rooting only to get rid of bloatware, but not one of the ODIN Flash recoveries work at all, not one, so like you ended up using CF Auto and that worked but now im still stuck with Stock Recovery. I dont understand why none of the recoveries flash when they did before.
Cheers

trouble with cwm/ twrp
Hi all. Yes I'm a noob and I wouldn't ask If hadn't tried a plethora of ways to install either cwm or twrp.
It took me a good hour to find this thread so hope I'm in the right place.
Ok I used odin to root and cwm didn't stick so still on stock rec. However I used framaroot to get super su working and titanium says I'm all rooted up. Other apps only for root also work.
I've since tried using goo manager and Rom manager to install cwm or twrp and both say unsupported.
I've searched these here threads and found a few with same problem namely when using odin cwm wont stick and android reinstalls stock recovery.
So I'm a bit stuck, I'm rooted but have no cwm or twrp.
Any help would he much appreciated.

Try Philz recovery .

I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone. untick the reboot option. then when odin is done flashing and says pass shut down the phone . dont let it boot up.once phone is off you can boot into recovery by vol up+hom+power Here is the tricky part. as soon as you see the white samsung start to load aka bootloader screen release the power button but continue to press volume up and home. you should see the circle with the hat symbol. and enter into clockworkmod once in clockwork mod you will need to wipe data cache and dalvick DO NOT WIPE SYSTEM then flash a custom rom zip that you have previously copied to either your extsdcard or sdcard0 at the same time you probably will want to flash gapps as well. the thing is if you boot up before entering recovery . the default native recovery from samsung will take its place back. maybe it is easier to just flash rom manager in the play store. flash clockworkmod and then boot into recovery from the app itself. I9300 is supported . dont know about I9305

thanks !
ashraf sharif said:
I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone. untick the reboot option. then when odin is done flashing and says pass shut down the phone . dont let it boot up.once phone is off you can boot into recovery by vol up+hom+power Here is the tricky part. as soon as you see the white samsung start to load aka bootloader screen release the power button but continue to press volume up and home. you should see the circle with the hat symbol. and enter into clockworkmod once in clockwork mod you will need to wipe data cache and dalvick DO NOT WIPE SYSTEM then flash a custom rom zip that you have previously copied to either your extsdcard or sdcard0 at the same time you probably will want to flash gapps as well. the thing is if you boot up before entering recovery . the default native recovery from samsung will take its place back. maybe it is easier to just flash rom manager in the play store. flash clockworkmod and then boot into recovery from the app itself. I9300 is supported . dont know about I9305
Click to expand...
Click to collapse
Thats exactly how I understood the cwm not sticking problem. I have tried rom manager and said not compatable with my device as did goo manager for twrp. I think odin is the only way I get it to stick. So il flash in odin and il try to get into cwm as it boots and wipe those two files you mentioned.
But then can I just boot up as normal ? or will android try to reflash its stock rom ? Damn my phone for being so difficult
I only ask because I haven't decided what CR to use yet (or even looked for any). I was gonna get it all ready first then learn how to install a CR - 1 thing at a time i thought.
Anyway thanks for your help :good:
JJEgan I found Philz thread to be helpful but something I feel Im just not ready for. Im new to this and although the updated cwm looked cool there were just to much going on, maybe for a later day.
Thanks all the same :good:

wiping data plus cache plus dalvick cache is done to prepare your phone for the custom rom that you are going to flash. the wiping is to clean those partitions because if they are not erased you will have problems. especially if you go from one android version to another or touchwiz to aosp. it is done so you get a clean install with minimal issues. if it is not done you will most likely bootloop. effectively it is a factory reset. all of your apps and app data will be gone so you do not want to do that unless you have backed up your apps . however sometimes google automatically installs them after you sign in.
I am not sure why clockwork mod does not stick but if you copy the rom you want to your phone install clockworkmod with odin and then use clockwork mod to flas the rom and gapps package then factory reset you will not have the stock recovery anymore. but this has to be done without booting into android stock . PLEASE FOLLOW THE FLASHING INSTRUCTIONS TO THE BEST OF YOUR ABILITY. AND UNDERSTAND ANYTIME YOU FLASH OR MODIFY YOUR PHONE YOU VOID YOUR WARRANTY AND POSSIBLY CAN CAUSE IRREPARABLE DAMAGE. BEST OF LUCK!
---------- Post added at 04:28 PM ---------- Previous post was at 04:24 PM ----------
Also philz recovery is highly recommended
HERE IS SOME VERY GOOD READING http://forum.xda-developers.com/showthread.php?t=2362743&highlight=philz+recovery http://forum.xda-developers.com/showthread.php?t=2344125

think I got it lol
Ok that's sounds good. However I've just read the threads you linked and now I've got to back up my imei and NV files first or il loose them when flashing. The procedure is all there and seems doable for a noob but i read some peeps are having trouble just doing that. I really wanted to root/install a CR regardless of the troubles cos I want full access and more importantly want to learn all the ins and outs so I can get the best use from my phone so glad I found this forum cause I'm sure I would have bricked my phone otherwise.
Might I ask if I've got this right tho?
1: backup imei/NV files
2: use odin to get cwm to stick using your method
3: boot into cwm to wipe data/dalvick cache and gapps
4:use cwm to flash a CR
5:factory reset
I think that's right?

CLOSE
1 BACKUP EFS FOLDER(IT CONTAINS imeiAND SERIAL NUMBER AND OTHER NETWORK SETTINGS) MAKE AT LEAST 2 BACKUPS ONE FOR EXTERNAL SDCARD AND ONE TO KEEP ON YOUR PC
2 INSTALL CWM RECOVERY USING ANY WORKING METHOD. byTHE WAY PHILZ CAN BACKUP EFS.
3 IN CWM RECOVERY MAKE A NANDROID BACKUP OF YOU CURRENT ROM. I FORGOT TO TELL YOU THAT ,THIS IS IN CASE YOUR FLASH FAILS YOU CAN RESTORE CURRENT ROM FROM BACKUP. ALWAYS BACKUP BEFORE A FLASH
4 IN CWM RECOVERY WIPE DATA, CACHE , AND DALVIK CACHE
5 IN CWM RECOVERY FLASH ZIP FOR ROM AND FLASH ZIP FOR GAPPS "GOOGLE APPS"
6 BOOT ANDROID THIS MAY TAKE UP TO 10 MINUTES FOR THE INITIAL BOOT. BE PATIENT. IF IT BOOTS YOU ARE DONE
7 IF PHONE DOES NOT BOOT THEN IN RECOVERY WIPE DATA AND CACHE AND DALVIK AGAIN
8 STILL NOT BOOTING FLASH ROM ANG GAPPS AGAIN
NOT BOOTING? RESTORE NANDROID
FACTORY RESET=WIPE DATA AND CACHE
DONT EVER WIPE SYSTEM UNLESS YOU HAVE A RECENT NANDROID. NANDROID IS GOOD BUT THE OLDER IT IS THE MORE LIKELY IT IS TO GET CORRUPTED
ALSO IF YOU GET FORCE CLOSES FIXING PERMISSIONS USUALLY WORKS FOR THAT.
SOME ROMS ARE FLASHED IN DIFFERENT WAYS .ALWAYS FOLLOW THE DEVELOPERS INSTRUCTIONS

i had the same Problem before.
I Just disassembled the battery after a full-wipe for few minutes and it works... i don't know y, but that was the only way... ?!

brilliant thanks!
ashraf sharif said:
CLOSE
1 BACKUP EFS FOLDER(IT CONTAINS imeiAND SERIAL NUMBER AND OTHER NETWORK SETTINGS) MAKE AT LEAST 2 BACKUPS ONE FOR EXTERNAL SDCARD AND ONE TO KEEP ON YOUR PC
2 INSTALL CWM RECOVERY USING ANY WORKING METHOD. byTHE WAY PHILZ CAN BACKUP EFS.
3 IN CWM RECOVERY MAKE A NANDROID BACKUP OF YOU CURRENT ROM. I FORGOT TO TELL YOU THAT ,THIS IS IN CASE YOUR FLASH FAILS YOU CAN RESTORE CURRENT ROM FROM BACKUP. ALWAYS BACKUP BEFORE A FLASH
Am I backing up to ext SD card?
4 IN CWM RECOVERY WIPE DATA, CACHE , AND DALVIK CACHE
5 IN CWM RECOVERY FLASH ZIP FOR ROM AND FLASH ZIP FOR GAPPS "GOOGLE APPS"
Are these seperate zips?
6 BOOT ANDROID THIS MAY TAKE UP TO 10 MINUTES FOR THE INITIAL BOOT. BE PATIENT. IF IT BOOTS YOU ARE DONE
7 IF PHONE DOES NOT BOOT THEN IN RECOVERY WIPE DATA AND CACHE AND DALVIK AGAIN
8 STILL NOT BOOTING FLASH ROM ANG GAPPS AGAIN
NOT BOOTING? RESTORE NANDROID
FACTORY RESET=WIPE DATA AND CACHE
DONT EVER WIPE SYSTEM UNLESS YOU HAVE A RECENT NANDROID. NANDROID IS GOOD BUT THE OLDER IT IS THE MORE LIKELY IT IS TO GET CORRUPTED
ALSO IF YOU GET FORCE CLOSES FIXING PERMISSIONS USUALLY WORKS FOR THAT.
SOME ROMS ARE FLASHED IN DIFFERENT WAYS .ALWAYS FOLLOW THE DEVELOPERS INSTRUCTIONS
Click to expand...
Click to collapse
Thank-you for all that,I really appreciate it.
Can I ask the difference between the apps nandroid manager and titanium? I've backed up with both and wondered if i really needed to? The nandroid backup was nearly 3gb!
Also I was gona backup with qpst for imei and NV files but then read its only for US versions? Will the backup of efs folder include those?

honestly i really dont know what the differences are. l do not use custom recoveries or custom roms. i dont use titanium backup .Any rom I flash i get from sammobile.com. one reason i do not use custom roms is that none can support mhl. I use a monitor and bluetooth mouse and keyboard . without mhl I cant mirror my screen so i always stay with stock roms. i use Xposed framework for modifications.

ashraf sharif said:
I have never used a custom recovery on this phone but i think i read somewhere that when flashing by odin the thing to do is not let odin reboot the phone......
Click to expand...
Click to collapse
thx you so much. this was the secound s3 that had this issue. deactivating auto reboot did the job!!!!