My phone was bricked yesterday. Then I used SMF to recover, so I turned back to v10a. (from smart flash tool)
Installed Rom manager rooted and installed marvel rom.
Then I tried miui 2.1 rom.
Then i tried to restore my backup(marvel) what i did with rom manager. Phone bricked again.(Blue screen on android)
Then I used SMF to recover again. --> v10a.
Now in rom manager pressin flash cwm button in menu but nothing happens. I rooted phone. Root is workin well in other programs like Titanum. Tried reboot into recovery causes factory reset bcs of cwm i think.
Any way to solve this problem? Or can I install zipaligned rom like marvel, zeus without cwm? Like S/E tool. Power + volumeUp...
Did you do all the wipes before flashing the rom?
Didn't you missed any step?
I cant see even recovery menu. To wipe data/dalvik.
I coulnt flas cwm, so when Im trying to do reboot into recovery via Rom Manager, skips that menu(controlled with volume and power buttons dont know the name) and v10 is booting with factory reset.
Do you have an internet connection when trying to flash cwm?
Trolling in the deep
Just root it again, reboot, install busybox, reboot, install cwm and all should work just fine
Sent from my LG-P970 using Tapatalk
Yes I had internet. I installed Rom Manager from market.
I will follow this link. It gives you offical 20o Rom rooted and touch version of cwm. Hope it will work for me.
And I realized that I really missed LG's UI.
http://forum.xda-developers.com/showthread.php?t=1480392&page=20
You probably forgot "wiping" before restoring your nandroid. Any this shall be a lesson. From now on you won't forget.
had the same problem before, i always had a bug installing CWM, caused factory reset everytime , but when i downloaded it again it works well..
Pondera said:
You probably forgot "wiping" before restoring your nandroid. Any this shall be a lesson. From now on you won't forget.
Click to expand...
Click to collapse
I've never wiped before restoring a nandroid, and believe me I've flashed my OB a lot while i was debuting my Lezo mod.
Trolling in the deep
I solved the problem. Now I have offical 20o ROM offical and rooted. Happy with that. Until stable CM7 or MIUI release I will stop trying ROMS.
Related
Hi,
I recently flashed a new rom (ultimate galaxy s v.7) from xda, and I flashed it via clockwork.
clockwork installed it and I rebooted, and it seemed to hang on the lockscreen for an abnormally long amount of time.
when i take the battery out and try to boot into recovery mode, it flashes to black then shows the galaxy s boot again.
previous to flashing this rom i have cleared the cache and all data on the phone. i have a nandroid backup so if i could get back to clockwork recovery this would be helpful.
also previous to flashing this rom i had a 3 UK rom which i installed by accident via kies, running 2.1...this rom seemed to be quite resistant to installing another rom from kies.
help would be MUCH appreciated...
thanks in advance
so recovery mode isnt an option then ?
What about Download mode ?
Hi,
Download mode worked before.
I have now managed by some miracle to get into recovery mode and now have gained options about a speedmod universal lagfix.
Is this associated with clockwork / ultimate 7.0 rom / a sign that the rom has installed in some form, and should i reboot, or should i now do a nandroid back to the rom i had before?
I believe speedmod uses CWM, so you can just do the rollback to your previous rom
nwsk said:
I believe speedmod uses CWM, so you can just do the rollback to your previous rom
Click to expand...
Click to collapse
however would it be safe to reboot, as i'm currently in recovery mode and considering to do a nandroid OR alternatively reboot and see if the new rom starts up..
well u cant leave it in recovery mode forever lol, reboot it, if it doesnt come on, try recovery mode again or just flash another ROM thru ODIN
ok. how long do you think is a reasonable time to wait before concluding that the rom doesn't work and I should nandroid back to my old rom...?
Half an hour gives plenty of time .
jje
what would be the reason that it hangs on the galaxy s bootscreen?
could be anything.... installing process not completed properly. best to just re flash .
azzledazzle said:
could be anything.... installing process not completed properly. best to just re flash .
Click to expand...
Click to collapse
do you mean recover via nandroid or reflash the same rom, then leave it?
choice is yours, ive never restored using nandroid so dunno what its like. but try it first, if no success re flash using odin. u will lose all your data
What i did before installing a custom rom:
I rooted my phone using superoneclick method.
Then installed xrecovery V0.1. (with busybox and charm*something)
Made a backup of the original room using Xrecovery
How did i install the custom roms and what happend:
Renamde gingerxd v13 to update.zip and place it on sdcard.
Wiped cache and factory reset(fullwipe).
Install update.zip with Xrecovery.
(after my first attemp failed, i tried to wipe cache and factory reset after installing the room too)
Reboot phone.
Phone goes into reboot loop. First sony ericsoon, then the logo of whatever custom room i'm trying to install.
I tried the MiniCM7-2.0.7 (source)
Then i tought, what if i downloader a back from another phone? i got Floyo 2.2.5 (source)
Restoring this backup too got me into a reboot loop.
Final question(and probably the supidest one if the answer is yes)
Do i need to unlock the bootloader to install a custom room? The guides i used didn't mention it at all, and since it may brick my device beyong xrecovery's help i'd like a straight answer before attempting it.
I tried to make this post as clear as possible and maybe someone can point out if im missing something.
Very important thing: Did your baseband end with 015? If no, that's why you are having these problems.
And no, you don't need to unlock the Bootloader to install Custom Roms.
It ends in 006. Thanks ill be reading on flashing a baseband and report back. PCcompanion says my phone is up do date so i'll be using this. If you have a better alternative let me know.
^^
Edit: Is there a way to configure pcc to make the update for me? Like say im from another country were the update is available?
Use Flashtool, go here
Thanks Chris95X8. my phone is now running 2.3.5 gingerdx rom. everything works. The only thing that's driving me nuts is the notification i get when i lose signal. Any way to fix this?
Sadly it didnt work for me... I have tried out flashing basebands but it wont work. still looping around. makes me crazy.
Kiwiii97 said:
Sadly it didnt work for me... I have tried out flashing basebands but it wont work. still looping around. makes me crazy.
Click to expand...
Click to collapse
Are you sure that you flashed the right baseband?
If you have, maybe try to boot phone without the SD card in it..
Hello All,
I rooted for the first time my Note 2 weeks ago, just with the Basic CMW and proper root to my kernel. It worked fine, but I wanted more, so I decided to try RR by Eybee.
Downloaded the RR v20, passed it to my SD Card.
I wiped the phone through CMW.
Flashed the .zip file.
I'm now stuck on the initial loading screen of Rocket Rom, it just keeps restarting.
I know I ****ed up someway, and would really appreciate someone's help...
Ty
I hope you did a nandroid back up in recovery before you flashed? Because if you didn't you are indeed up creek without a paddle. It is always recommended to do a backup before you flash anything through recovery. If you didnt then go on you're computer download another rom to you're ad card go into recovery and flash it or get the original ruu rom and flash that.
Sent from my Inspire 4G using xda premium
No I have not.. I did full sys+data recovery through Titanium backup. I can't access CMW , to be honest I only did it through the phone itself... I can only access the Download Mode and tried to flash back the ROM I used to root the phone, which was useless.
Am I missing some really obvious way to access CMW without being able to initialize the phone?
...
Edited:
Found it:
Going to wipe, resintall root that worked and go from there ty.
Edited:
Reinstalled Rocket Rom through CMW (Up Vol+Power Button+Menu)
Wiped.
Reinstalled.
Working
I wanted to flash CyanogenMod 7.1 on my Samsung Galaxy S.
I flashed before a Froyo Bootloader (because I had Firmware 2.3.3) on it, copied the CM7.1 Rom on internal storage and tried to flash through Recovery.
While updating it shows me the install process till:
Checking state of BML/MTD
then it interruptes the install process and restarts the phone. But then it just shows me the Samsung logo and nothing happens (=freeze).
No chance to start the phone, altough I restart it several times.
Then I can flash again with Odin to the starting state again. The files for that I found here (german):
http://www.giga.de/smartphones/samsung-galaxy-s-i9000/tipps/samsung-galaxy-s-cyanogenmod-7-flashen/
EZodin
EZbase-CSC-XXJV1.tar.md5
EZbase-PDA-XWJS3.tar.md5
EZbase-PHONE-XXJVE.tar.md5
Ezbase.pit
How can I flash CM7.1 now..?
Sometimes the cm7 rom will need flashed twice....you should be able to flash from any gingerbread rom also as cm7 was updated a while back to allow this. Try again, and if the phone starts bootlooping-pull the battery, replace and get into recovery-then reflash rom.
Unfortunately i cant enter recovery after unsuccessful flash. I have to use odin and flash back to old froyo... then i tried to reflash again to cm7.1 but it was always the same.
Thx anyway for ur answer...!
Hmmmmm ;(
Gesendet von meinem HTC Desire mit Tapatalk
no ideas? it is urgent.. ;(
it's really strange. it happened to me and I solved like this:
I removed the battery
volume up key + power button + home button
in recovery,I wipe everything and reflash of the rom
If recovery doesn't work, you need to reflash a stock rom, and a kernel with root and CWM
puuhh, at least another one who had this issue...
ok i understood that if i cant flash to cm7.1 then i have to chosse another rom, maybe just a stock rom.
but can anybody recommend a custom rom which will work? it is just a file system problem here, isnt it?
Done it!
Trying to flash the stable Rom didnt work.
Then i tried the nightly (181) and it took a while then it restarted. but when it was starting for the first time i got a loop while booting.
but this time i could enter the recovery (after stable installation it wasnt possible anymore) and i could reflash it (nightly again). and this time it worked!!! yeah finally after over 8 hours of work....
i hope i could help somebody who has got same issues
Glad you got it -and cm9 is now an easy upgrade from the latest nightly
Hi guys, I'm having trouble with new ROM installation. I've been using Gingercruzt ROM since last spring with stock kernel. Bootloader is not unlocked, I've only rooted the phone. It's been working fine until I decided that I want to try something new today. I downloaded the GingerDX rom and installed it with CWM. Everything went fine and I rebooted the system. The phone didn't start, it got stuck on the SE logo. I couldn't enter CWM or xRecovery anymore. It bricked. Using SEUS I brought back the stock rom. I rooted the phone again, installed newer version of CWM from the toolkit, etc. I downloaded the zip again, installed it again - it bricked the phone the same way. Then I tried with two different roms - FroyoPro and Free Dom experience with full wipes on everything before installing - same thing, doesn't start. I was able to enter xRecovery with FroyoPro but no CWM and it get stuck at rom's loading screen.
Help please, what happened to my phone Why doesn't it load a ROM like it did yesterday?
Thanks in advance!
vgaBG said:
Hi guys, I'm having trouble with new ROM installation. I've been using Gingercruzt ROM since last spring with stock kernel. Bootloader is not unlocked, I've only rooted the phone. It's been working fine until I decided that I want to try something new today. I downloaded the GingerDX rom and installed it with CWM. Everything went fine and I rebooted the system. The phone didn't start, it got stuck on the SE logo. I couldn't enter CWM or xRecovery anymore. It bricked. Using SEUS I brought back the stock rom. I rooted the phone again, installed newer version of CWM from the toolkit, etc. I downloaded the zip again, installed it again - it bricked the phone the same way. Then I tried with two different roms - FroyoPro and Free Dom experience with full wipes on everything before installing - same thing, doesn't start. I was able to enter xRecovery with FroyoPro but no CWM and it get stuck at rom's loading screen.
Help please, what happened to my phone Why doesn't it load a ROM like it did yesterday?
Thanks in advance!
Click to expand...
Click to collapse
Did u cleared 'dalvik-cache' in case of froyopro & when u are stuck at 'Sony Ericsson' logo did u checked that u have downloaded thi Rom zip for 'stock kernel' I think this the problem download zip for stock kernel
Hit thanks if this helped u
sent from my W8 using client-server technology
Yes, I cleared all the possible caches, system and other folders. I even formated my sd card, just in case...
I downloaded all the right roms for stock kernel, all three of them. As I said, I've done this before and it worked from first try.
Thanks for trying to help me!
vgaBG said:
Yes, I cleared all the possible caches, system and other folders. I even formated my sd card, just in case...
I downloaded all the right roms for stock kernel, all three of them. As I said, I've done this before and it worked from first try.
Thanks for trying to help me!
Click to expand...
Click to collapse
You should not format /system, cause you are actually removing recovery+rom
& are you sure that froyopro supports stock kernel?
Sent from my ULTIMATE using Tapatalk 2
jay-z-s said:
You should not format /system, cause you are actually removing recovery+rom
& are you sure that froyopro supports stock kernel?
Sent from my ULTIMATE using Tapatalk 2
Click to expand...
Click to collapse
yup froyopro support stock
vgaBG said:
Yes, I cleared all the possible caches, system and other folders. I even formated my sd card, just in case...
I downloaded all the right roms for stock kernel, all three of them. As I said, I've done this before and it worked from first try.
Thanks for trying to help me!
Click to expand...
Click to collapse
Then don't format /system
sent from my W8 using client-server technology
try to redownload the rom. flash it again after a full wipe, then reboot.
signature under repair
I cleared the system folder before flashing a new ROM just to make sure I have deleted the stock ROM.
I tried with three different new ROMs, none of them started. Strange thing... everything goes well with the install and then it just won't turn on.
Do you think it's going to be different If I try to unlock the bootloader and flash nAa's kernel? I don't really want to do that but the phone is manufactured before the 29th week so it's capable.
are you sure it doesnt turn on?,first boot may take some minutes...
Yeah, I know, I've left it for more than 15 minutes with any of the tried roms.
I think I should write down the steps I'm taking after the flash back to stock rom with SEUS.
1. Activating debugging mode and unknown applications.
2. I already have the Android SDK, adb server and drivers from before so I open SuperOneClick and root the phone. Busybox is installed and Superuser is on. Everything goes smoothly during the process.
3. Using x8toolkit I install xRecovery and CWM via Dualrecovery.
4. Reset and entering CWM. Full wipe, install from zip, installation goes without problems and says - Go on buddy, restart and start using
5. Reset, Sony Ericsson logo and that's it. Nothing more happens. With GingerDX and Free Dom experience I can't enter recovery any more. FroyoPro's starting screen shows up after the SE logo but that's all it does - it never goes any further. I can enter xRecovery but no CWM.
I tried installing roms with both xRecovery and CWM - all the same. Could it be some physical damage even though the stock rom runs perfectly well? I don't know, I'm a bit desperate as the battery lasts half a day with the stock rom.
Just to end this thread, nothing worked for me so I unlocked the bootloader, flashed nAa's kernel and got a new ROM compatible with it - it works like a charm now. Thanks for your support guys!