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

[Q] Is my phone unable to run ICS?

Since about a week I'm having the following problems:
It is extremely difficult to get my phone running ICS. I tried like 10 different ROMs, the only one currently working is Dark Knight. In between I managed to run CM9 Nighlty (2 days) and Infinitum 2.2 (3 days)
Why is it so difficult? Well - I believe, I'm doing all the correct steps: Flashing JVZ with Odin, rebooting, flashing CF Root, rebooting. Enter CWM, wipe data, cache, dalvik, format system -> Install any ICS rom
Currently, CM9 doens't work at all, I get boot loops after the initial reboot and can't enter recovery
Well, when I finally manage to install any rom (method: install Dark Knight - 5.5 atm - install any rom afterwards - my phone boots up correctly and is perfectly usable
But: Whenever I reboot, I keep getting boot loops with no chance of entering recovery. None of the usual methods work.
Stupid thing: I don't need to reboot. But every other day the phone tends to reboot itself (at least that is what I experienced and sorta guess)
Result: I take it out of my pocket or look at it on my desk and see boot loops after 2 or 3 days
What can I do, why is that? I don't want to run Gingerbread
I am not a noob - I have been running any rom before for one and a half years without problems and flashed mostly without any problems
Believe me - I have tried everything for several days. Flashing the recovery fix with Odin doens't help either. Afterwards I am a able to boot intro recovery but can't install any rom due to build.prop errors. However, I can flash a kernel... Result: boot loop. Solution: Start over with Gingerbread and Odin
The more I think about it, the more I belive there could be an underlying hardware problem. Maybe something with the internal NAND?
I am greatful for any help or new ideas which I haven't tried so far... Thanks a lot in advance!

I know it's a long shot, but maybe you have issues with datadata folder? Use root explorer and see how much free space you have there...
Maybe try this:
After Odin, When in CWM, flash first a new kernel (try devil.072). Make sure to mount folders with CWM before. After flushing, go to advanced and reboot recovery. Now you have a new version of CWM (which supports screen tuch...). Now, from mounts and storage, format everything. Now flush the rom you want - in this case, I recommend Slim 3.4. Don't install anything yet - just let it run after flushing. Just login to your google account.
See if it works.. hope it helps

Thanks a lot! Unfortunately, it didn't work.
I tried your method which didn't even end up in a bootloop but in recovery after every flash/try to reboot.
/edit: Speaking of reboots - I tried to install CM9 afterwards/instead -> boot loop

Hmmm u have a interesting problem. Do u wipe everything and have u tried starting from a different stock gb
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!

Yes, I wipe everything and tried JVZ and JVU as a starting point. Are there any other recommendations?

which firmware are you odining? maybe bad download?

Bara2 said:
Thanks a lot! Unfortunately, it didn't work.
I tried your method which didn't even end up in a bootloop but in recovery after every flash/try to reboot.
/edit: Speaking of reboots - I tried to install CM9 afterwards/instead -> boot loop
Click to expand...
Click to collapse
Just try it again but do NOT select reboot recovery. It is a common bug that you won't be able to leave recovery again. Just reboot the phone and be sure to quickly press 3 button combo again to get into recovery again. You should then be able to format / reflash and so on. Just make sure you never select reboot recovery when you just came the long way from odin. In doubt just do as I stated: normal reboot and press 3 button combo quickly.
Good luck!

shaharofir said:
which firmware are you odining? maybe bad download?
Click to expand...
Click to collapse
I agree many try a firmware from stock firmware from xda
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!

swent said:
Just try it again but do NOT select reboot recovery. It is a common bug that you won't be able to leave recovery again. Just reboot the phone and be sure to quickly press 3 button combo again to get into recovery again. You should then be able to format / reflash and so on. Just make sure you never select reboot recovery when you just came the long way from odin. In doubt just do as I stated: normal reboot and press 3 button combo quickly.
Good luck!
Click to expand...
Click to collapse
Ok, That shall be my next try Btw: Another strange effect: I flashed Dark Knight 5.5, did nothing but click through the setup assistant rebooted - and voilà - boot loop.
Will report back in a few minutes Thanks a lot, guys!
/Edit: Well - a litte success... I was able to boot into the system. First thing I did was change lcd density and rebooted - everything was fine. As I didn't have wifi or data connection I wanted to flash another kernel (devil) and hit reboot recovery from the power menu.
--> Boot loop again.
To the other guys: I tried JVU and JVZ with different downloads and two different laptops. Which starting base should I try next?
/Edit2: I'm going to stay on Gingerbread for the day. I need my phone and intend to enjoy the fantastic weather for the rest of the day... Will be back this evening. I am glad for further feedback and ideas

Bara2 said:
Ok, That shall be my next try Btw: Another strange effect: I flashed Dark Knight 5.5, did nothing but click through the setup assistant rebooted - and voilà - boot loop.
Will report back in a few minutes Thanks a lot, guys!
/Edit: Well - a litte success... I was able to boot into the system. First thing I did was change lcd density and rebooted - everything was fine. As I didn't have wifi or data connection I wanted to flash another kernel (devil) and hit reboot recovery from the power menu.
--> Boot loop again.
To the other guys: I tried JVU and JVZ with different downloads and two different laptops. Which starting base should I try next?
Click to expand...
Click to collapse
Umm well I use jvu and have no problems. This might sound stupid but when I had a similar prob (I flashed a kernel on dark knight 4 and got into a bootloop and couldn't enter recovery) I did a factory restset after backing up my SD card data and flashing jvu, then I reflashed jvu. Rooted, wiped rebooted recovery, wiped again, rebooted recovery again, then I flashed dk 3 then dk 4 without a wipe, the restored my apps and copyed my SD data back - I hadn't been able to flash a rom since the bootloop I got it working with dk 3 but then I got no boot animation and I just stopped there, the above process worked for me I know u on dk 5.5 but try dk 3 you should find the link in the dk thread around April 12-16 this year.
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!

You may flash the new kernel right away after flashing the desired rom. Maybe that would stabilize everything... can't make any more sense of it right now, sorry :/ Maybe you could try to use the ultimate kernel cleaning script AFTER flashing the rom and BEFORE flashing the new kernel (with no reboot in between).
Script is somewhere out there, I'm gonna search it right now...
/EDIT: Wasn't really hard to find after all, there you go: Ultimate Kernel Cleaning Script

try this firmware for odin:
https://www.sugarsync.com/pf/D6246658_3937073_82911

[Q] (Yet Another) Boot Loop Problem in Installing CM7 on GalaxyS I9000 [SOLVED]

YABLP (Yet Another Boot Loop Problem)
Hi,
I'm having a devil of a time installing CM7 on my GalaxyS I9000. Description of my procedure and problem below.
I've been beating my head against a wall for a week so any help GREATLY appreciated.
-John
Phone: Galaxy S "I9000"
Trying to Flash: CM7.2.0 using CWM Recovery
What I did:
Flash stock ROM w/ODIN v1.85 - OK
Wipe Data/Wipe Cache
Flash ChainFire (CF-Root-XX_OVA_JVU_2.3.6-v4.3-XWM3RFS.tar) w/ODIN v1.85
Wipe Data/Wipe Cache
Phone now rooted OK
Boot to CWM Recovery
Install zip from sdcard
Select update on SDCard (cm-7.2.0-galaxysmtd.zip from CM site)
Flash completes in just a few seconds - much too quick!
Phone reboots automatically
Now stuck in boot loop
Screens in boot loop:
1. GalaxyS/GTI9000/Samsung
2. GalaxyS/Cyanogen(mod)
3. CWM menu scrolls by too quickly to read
Back to 1.
Tried Heimdall but complained about missing XML file
Tried installing "Datafix". Would not install (says not compatible with device)
Tried STFW: many reports of same problem but no solutions seemed relevant & appropriate
Clues:
After CF flash, disk use as follows
/system: used 27.3M, free 9.4M (97%) (seems pretty full)
/data: used 47M, free 1916M (2%) (seems pretty empty)
Me thinks maybe /system is too small/full to accept update?
This is the 3rd I9000 I've flashed. First 2 went Ok but this time it failed although identical files/procedures used (I think).
HELP!

I've seen a similar problem on my I9000 - I think the CWM scroll complains about "can't mount /data".
I'm in a similar position, I can't get anything to flash and boot though : http://forum.xda-developers.com/showthread.php?t=1967982

This happens pretty much every time you flash any kind of CM rom from stock. All you need to do is flash CM7, it will go in to bootloop with various text scrolling through thats too fast to read. You just pull battery while in the bootloop. Then replace battery, three button combo to recovery and flash the same CM7 zip again. This time the install will take a while longer. Afterwards flash gapps and reboot and you should be good to go.

I tried this - but same result, just spins round on the CM boot screen
Where do the wipe data and wipe cache commands fit in to this? Before/after both installs?
I don't normally bother with gapps - just trying to get it loaded. Does that make a difference?
Also, no SIM card in at all during all this...

IT WORKED!
Bless you BandiBp!
I'll be sending my first-born by return mail (please don't tell my wife

Yeah that happens because its flashes a kernel with a new partition system. Dunno why only a few roms warn people about this.
Sent from my GT-I9000 using xda premium

You're welcome mate, yeah the reasons are the new partition changes on different roms. I agree that rom flashers should be warned in advance about this. Would reduce problems A LOT. My general rule is if a Rom installs in under 5 secs, then you should always flash again.
Anyways have fun.

[Q] xperia z stuck at boot screen

Hello,
I own an Xperia Z C6603 and i was running the latest oficially available firmware before
i m quite new to all the stuff regarding flashing/rooting/unlocking etc
so today i decided to give it a shot.
now my phone is in a state that i cant use it any more.
Basically what i wanted to do is install this [BeanStalk-4.4015] custom rom. Now its stuck on the loadscreen forever.
I started with rooting the device following the description in one of the posts i found here (flashing the previous kernel with flashtool then rooting it and flashing the original latest kernel again) which worked out very well.
After that i unlocked the bootloader following another guide here in forums which went ok without any problems aswell.
As it seemed like it reset all my settings after unlocking the bootloader i reenabled the developer mode to set the USB debugging and security options for unofficial software aswell.
All went fine and i was preparing to install the custom rom so i put the zip file on my sd card entered the recovery mode and flashed the rom zip file.
It seemed all ok and the phone was restarting and its stuck in the boot screen ever since that. I tried to get it back in order by trying out various stuff i could find here on forums.
when i tried to reset the delvik cache initially i did not see any error messages or anything so i assumed that its done correctly also cleared the other caches which were listed. I was getting a bunch of errors but i assumed its because the folders could be empty as it seemed like the phone was completely reset after the bootloader unlock.
I could not get anywhere with the CWM recovery mode so i flashed MOEW kernel through flashtool. The meow kernel was mentioned in the post regarding the custom rom as viable and it included TWRP recovery so i wanted to give it a try.
First exactly the same happened when i tried to boot it normally... Stuck...
So after that i tried to mess around with the TWRP recovery which seemed a bit more complicated than CWM.
First that came to my eye was that i could not enable all the partitions (system was constantly disabled) i managed to enable it after hitting the fix permissions button a bunch of times also i started to get some error messages while trying to reset dalvik cache but none of this changed the main problem at all.
Also i m unable to access the SD card from my computer for some reason even if i enable USB teathering in CWM or TWRP.
any suggestions how to get the phone back to work ?

druvisk said:
Hello,
I own an Xperia Z C6603 and i was running the latest oficially available firmware before
i m quite new to all the stuff regarding flashing/rooting/unlocking etc
so today i decided to give it a shot.
now my phone is in a state that i cant use it any more.
Basically what i wanted to do is install this [BeanStalk-4.4015] custom rom. Now its stuck on the loadscreen forever.
I started with rooting the device following the description in one of the posts i found here (flashing the previous kernel with flashtool then rooting it and flashing the original latest kernel again) which worked out very well.
After that i unlocked the bootloader following another guide here in forums which went ok without any problems aswell.
As it seemed like it reset all my settings after unlocking the bootloader i reenabled the developer mode to set the USB debugging and security options for unofficial software aswell.
All went fine and i was preparing to install the custom rom so i put the zip file on my sd card entered the recovery mode and flashed the rom zip file.
It seemed all ok and the phone was restarting and its stuck in the boot screen ever since that. I tried to get it back in order by trying out various stuff i could find here on forums.
when i tried to reset the delvik cache initially i did not see any error messages or anything so i assumed that its done correctly also cleared the other caches which were listed. I was getting a bunch of errors but i assumed its because the folders could be empty as it seemed like the phone was completely reset after the bootloader unlock.
I could not get anywhere with the CWM recovery mode so i flashed MOEW kernel through flashtool. The meow kernel was mentioned in the post regarding the custom rom as viable and it included TWRP recovery so i wanted to give it a try.
First exactly the same happened when i tried to boot it normally... Stuck...
So after that i tried to mess around with the TWRP recovery which seemed a bit more complicated than CWM.
First that came to my eye was that i could not enable all the partitions (system was constantly disabled) i managed to enable it after hitting the fix permissions button a bunch of times also i started to get some error messages while trying to reset dalvik cache but none of this changed the main problem at all.
Also i m unable to access the SD card from my computer for some reason even if i enable USB teathering in CWM or TWRP.
any suggestions how to get the phone back to work ?
Click to expand...
Click to collapse
hey if you wana go back to stock rom follow this post forum.xda-developers.com/showthread.php?t=2240614
i think u have to fastboot and flash boot.img
try pacman rom which is better and bug free rom

Hi, are you still able to connect to flashtool in flashmode? If so have you tried to flash back to stock rom?
Check this thread out, it contains good stuff.... 3rd video show how to flash stock ....
http://forum.xda-developers.com/showthread.php?t=2275632
Good luck !!

Hello,
thx for your replies i m still able to access all the modes it just does not load up if i dont do anything
after i unlock the bootloader to i need to reroot the phone ?
as it seems right now to me it simply doesnt write anything when i try to flash the rom also some partitions are not available

Hello,
i managed to unbrick the phone using this tutorial http://forum.xda-developers.com/showthread.php?t=2458530
however i tried to redo all the steps following the guide to install the beanstalk rom and noticed that i m getting an error about updater package when i try to execute the installation from TWRP any ideas ?
would you suggest trying another 4.4 based rom ?

Hello again,
ok so i gave up on the beanstalk 4.4 rom and decided to try my luck with pac rom mtayabkk suggested
so now the problem is not as big as it was.
Able to get the rom to run however i m unable to import my contacts/sms/call log using titan backup
The restore seems to work but after that i m getting com.android phone has stopped error everywhere i go on my phone (the contacts/etc are actually restored in this process tho and work fine apart from the errors)
i did restore a bunch of other settings together with the contacts aswell which i found as safe to back up in a guide i found
so can you give me an advice how to properly restore this to the newest pac man rom and avoiding various errors after that ?
ps
i moved all my media to sd card so it does not concern me the only thing i cant seem to be able to move over apart from contacts/sms/call log are the APN settings which is bothering me a bit aswell as i can not receive the configuration messages from carrier but i found them on the internet and i will add them manually
trying to restore the stock backup from PC companion right now to export them again as i lost the backup in process of trying to deal with the error i was getting
would you suggest trying again with titan backup or any other tools ?

[Q] Phone fails to start installing ROM

Okay so, I'm not exactly sure if this is the right place but I'll ask here anyway.
I took my old i9000 out of the closet and started playing around with it as I want to use it on my upcoming travel. To make long story short, I used to have a custom ROM on the phone all those years ago, but I am by no means an expert on the subject.
So what I have done so far today:
1. Returned the phone to stock ROM with Odin (XWJW1 or something, most recent anyway)
2. Rooted with Semaphore 2.7.4.
3. Installed Rom Manager and Superuser to check for CWM updates (which caused some sort of a verification error when I tried to boot to CWM through the app).
4. Downloaded the appopriate Slimkat and gapps and moved them into the internal storage.
But after the last step (and after wipe cache, format system etc) when I try to install the ROM, the bar on the screen progresses only slightly and after "Installing update..." it crashes (just goes black without any error messages) and gets stuck with just "Semaphore" on the screen.
I wish to update the phone to Slimkat 4.4.2. But what causes this problem, any ideas? Am I doing something wrong? If anyone can give any help that would be much appreciated!
PS. If I wanted to install for example Philz recovery, how am I supposed to do it when the file is .img?

Anyone?

I guess no one is using this phone anymore?

Yes, you are doing many things bit wrong.... (and many people use this phone still). I hope following will help you:
*recovery and kernel are sharing the same partition on the i9000 what means that you can't flash recovery separately
*make sure to backup your IMEI if still there
*flash first CM10.2 to get updated recovery for KitKat roms and to resize the system and data partitions to those used by all KitKat roms and reboot once into the system. You will need to flash trice to make it work (1. only warning of resizing to come and data lost- and status 7 abort, 2. only recovery update, 3. successful flashing)
*flash SlimKat and latest SlimGapps (addons) for 4.4.4
*PhilZ touch screen isn't yet working well on the i9000 but if you flash Mackay KK kernel, you can get beautiful TWRP touch recovery
tetakpatalked from Nexus 7 flo