I accidentally deleted the stock rom for it, thinking CWM backed it up, and the phone won't boot into recovery mode, so I can't flash the OpenZio custom rom onto it. Any ideas?
Lt Sorrow said:
I accidentally deleted the stock rom for it, thinking CWM backed it up, and the phone won't boot into recovery mode, so I can't flash the OpenZio custom rom onto it. Any ideas?
Click to expand...
Click to collapse
You don't need a rom on your phone to go into recovery, please give some more info. How did you delete your stock rom? What issues are you having when trying to go into recovery? Etc.
Sent from my LG-P509 using xda premium
Hi. Would be great if anyone could help as I bricked[?] my phone earlier today.
So here's what happened.
I was on SweetRomV1 JB previously and wanted to flash back to ICS RRv12.
So I stupidly flashed Abyss Kernel from my recovery forgetting that it doesn't support JB rom.
So the CWM started refreshing itself, stopping me from surfing the menu up and down.
I pulled out the battery, place it back in. The phone started up, but the screen was empty/blank/black.
Searched on the net then I realized Abyss Kernel doesn't support JB.
So under some forumer advice, I flashed a Stock ICS Rom using PC odin.
This time, I can access recovery with no problem. However I'm still stuck, the phone is not rebooting.
I'm stuck at the Samsung logo.
So I decided to flash a new kernel using PC odin and a new rom.
I flashed SpeedMod K3-15 using Pc odin and in recovery, I flashed the RRv12 rom.
Now it's still loading the boot animation.
I'm really at a loss now. Can anyone help?
I can access download mode and recovery. But I can't place files into my ext_sd because I can't boot up my phone.
Can anyone help me to get my phone working again?
Thanks in advance.
Flash stock gb via pc odin and work from there. The problem is you flashed incompatible kernels. The flash back to original should be fine.
Sent from my GT-N7000 using xda premium
are you on rr now? what do you see in recovery? is it cwm philz? if yes do a factory reset, wipe data, wipe dalvik and reboot
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
are you on rr now? what do you see in recovery? is it cwm philz? if yes do a factory reset, wipe data, wipe dalvik and reboot
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Nope. CWM-base recovery.
if you are on a safe kernel ek do a factory reset
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
if you are on a safe kernel ek do a factory reset
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I did it last night. I'm able to boot up now and I'm in RRv12 now. However, what just happened was, I changed to a fresh battery to charge it.
When I boot up, it shows that battery is disconnected. So I did a power off, and pulled out the battery. Used the method online, dropped the battery from around 2 feet high.
When I place the battery in again, I'm stuck AGAIN at the boot animation.
Any help?
Hi xda community. I'll try to explain exactly what I did and what's happening.
I flashed Cyanogenmod and everything went fine. As the latest Nighty became available, I downloaded it and tried to apply the update. I'm using Philz Touch as recovery. The update process started as usual, but then it stopped when it was almost done. I rebooted recovery and it begun again to install the update without success at all.
I've opened Odin and tried to re flash the recovery, hopping that I would be able to get to the normal Philz Touch recovery and it started (again) the update process.
I've ticked NANDROID full wipe and flashed the recovery again and I got the recovery menu. I performed a Nandroid restore, and recovery couldn't mount the /data partition.
I've realized that the /efs partition wasn't mounted. I manually mounted it and Nandroid backup successfully restored everything.
Ripper ROM (Samsung Based) booted up well, and I had to flash a modem since I didn't have signal. I thought everything was fine. But now as soon as I install a new ROM (either Sammy Based or AOSP) I lose my IMEI and get in Factory Mode.
I've tried restoring efs from backup and it didn't work. The only way I get it to work is restoring from Nandroid backup.
Can anybody help me please?
Sent from my GT-I9305 using xda premium
jjpro45 said:
Hi xda community. I'll try to explain exactly what I did and what's happening.
I flashed Cyanogenmod and everything went fine. As the latest Nighty became available, I downloaded it and tried to apply the update. I'm using Philz Touch as recovery. The update process started as usual, but then it stopped when it was almost done. I rebooted recovery and it begun again to install the update without success at all.
I've opened Odin and tried to re flash the recovery, hopping that I would be able to get to the normal Philz Touch recovery and it started (again) the update process.
I've ticked NANDROID full wipe and flashed the recovery again and I got the recovery menu. I performed a Nandroid restore, and recovery couldn't mount the /data partition.
I've realized that the /efs partition wasn't mounted. I manually mounted it and Nandroid backup successfully restored everything.
Ripper ROM (Samsung Based) booted up well, and I had to flash a modem since I didn't have signal. I thought everything was fine. But now as soon as I install a new ROM (either Sammy Based or AOSP) I lose my IMEI and get in Factory Mode.
I've tried restoring efs from backup and it didn't work. The only way I get it to work is restoring from Nandroid backup.
Can anybody help me please?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Does Ripper Rom use Perseus kernel perhaps? If so, join us over here.
AW: Strange IMEI behavior
Rekoil said:
Does Ripper Rom use Perseus kernel perhaps? If so, join us over here.
Click to expand...
Click to collapse
Yeah, I'm running that kernel...is that perhaps what's causing the problem with the /efs partition?
Edit: tried to flash another kernel and got no signal but as long as I flash Perseus it works!
Why is this happening???
Sent from my GT-I9305 using xda premium
jjpro45 said:
Yeah, I'm running that kernel...is that perhaps what's causing the problem with the /efs partition?
Edit: tried to flash another kernel and got no signal but as long as I flash Perseus it works!
Why is this happening???
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Beats me mate, myself along with a couple others are having the same exact problem. We have no idea what is going on. Discuss possible solutions in the thread I linked.
AW: Strange IMEI behavior
Does that means that I'm now stuck on that kernel?
Sent from my GT-I9305 using xda premium
jjpro45 said:
Does that means that I'm now stuck on that kernel?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Yes, join the club.
So, does this mean those of us haven't got this error should stay away from the Perseus kernel?
Sent from my GT-I9305 using xda premium
Cundis said:
So, does this mean those of us haven't got this error should stay away from the Perseus kernel?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Not at all. I have been using it from the start. Will choose it every day over stock kernel
nateboi81 said:
Not at all. I have been using it from the start. Will choose it every day over stock kernel
Click to expand...
Click to collapse
Just out of curiosity, what happens if you install a non-Perseus kernel?
With the new boot loader unlock it comes time to use a recovery other than safe strap. The easiest way to flash a custom recovery, in this case, clockwordmod recovery, is to simply download ROM Manager and use it to flash the Motorola Photon Q version of CWM Recovery. I flashed it and booted into it and haven't experienced any problems as of yet so for those looking for a custom recovery straight out of the gate, this is for you.
Sent from my MB886 using xda premium
Nice i don't know if i should try it or wait for an official one for our device. In the mean time back to my nexus 4
Sent from my MB886 using xda premium
If you really want to give it a spin you can always flash the Photon Q version otherwise I'm sure there will be an official version ported soon
Sent from my MB886 using xda premium
Dumb question...... if I uninstall ss and install cwm will I lose the current ROM im using?
Sent from my MB886 using xda app-developers app
You'll have to reinstall yes.
Sent from my JokerMATRIX HD MAXX
Dumb question part 2..... uninstall ss first and then install cwm? Also erase all ROM slots before uninstalling? Thanks!
Sent from my MB886 using xda app-developers app
Yea make sure to erase the rom slots. I forgot to and uninstalled then was missing quite a bit of space lol.
Sent from my JokerMATRIX HD MAXX
I was thinking it might be a good idea lol. Thanks!
Sent from my MB886 using xda app-developers app
it actually works. lol
freshlycutlawn said:
With the new boot loader unlock it comes time to use a recovery other than safe strap. The easiest way to flash a custom recovery, in this case, clockwordmod recovery, is to simply download ROM Manager and use it to flash the Motorola Photon Q version of CWM Recovery. I flashed it and booted into it and haven't experienced any problems as of yet so for those looking for a custom recovery straight out of the gate, this is for you.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Have you flashed anything with it?
I haven't actually tried yet flashing a ROM but since I'm on stock and don't want to flash white yet I haven't had the opportunity, as long as its flashing to the device it should work with no problems
Sent from my MB886 using xda premium
freshlycutlawn said:
I haven't actually tried yet flashing a ROM but since I'm on stock and don't want to flash white yet I haven't had the opportunity, as long as its flashing to the device it should work with no problems
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
So far, i have installed the cwm for the photon q like you, and made a back up through it. Im going to see if it will restore from it as well. ill keep everyone updated.:good:
:edit: I sucessfully backed up my stock JB rom, wiped everything, and restored everything back and everythings perfect... I dont know what else to try before attempting to flash using the photon CWM. any ideas?
I uses the photon q recovery to backup & restore, and haven't had any issues yet. No ROM flashing for the time being, just haven't tried it yet.
Sent from my MB886 using xda premium
I Flashes AOSPizza and was getting a bootloop, had to start the phone in DB Mode from the Fastboot menu to get it to start up, charging my battery and will be restoring original at&t firmware as soon as possible....Dont need a brick just bought this!
I'm on aosp pizza but I reverted to the stock jelly bean system. Mounted system installed the aosp ROM the Mexico firmware was giving me hell except with cm 10
Sent from my Nexus 4 using xda app-developers app
DaveNavy said:
I Flashes AOSPizza and was getting a bootloop, had to start the phone in DB Mode from the Fastboot menu to get it to start up, charging my battery and will be restoring original at&t firmware as soon as possible....Dont need a brick just bought this!
Click to expand...
Click to collapse
Did you try to go back into CWM and wipe everything again after the boot loops? That sometimes helps when it is boot looping after an install.
bconcio said:
Did you try to go back into CWM and wipe everything again after the boot loops? That sometimes helps when it is boot looping after an install.
Click to expand...
Click to collapse
I tried the same thing with cm10, i tried 3 times and got bootloops on each, in the end, at least we know the back up and restore function works well.:good:
jbatacan said:
I tried the same thing with cm10, i tried 3 times and got bootloops on each, in the end, at least we know the back up and restore function works well.:good:
Click to expand...
Click to collapse
I'm Stock Again, Restart always sent me to fastboot with a failed flash error, I could back out of it to the pizza ROM each time however I don't want to depend on my phone booting incorrectly so I used RSD and I'm stock again, I'm going to give it another try tonight.
UPDATE...Reflashed everything started over and everything works PERFECT Yippie!!! I'm very pleased!!!!
Running AOSPizza and Loving it!
DaveNavy said:
I'm Stock Again, Restart always sent me to fastboot with a failed flash error, I could back out of it to the pizza ROM each time however I don't want to depend on my phone booting incorrectly so I used RSD and I'm stock again, I'm going to give it another try tonight.
UPDATE...Reflashed everything started over and everything works PERFECT Yippie!!! I'm very pleased!!!!
Running AOSPizza and Loving it!
Click to expand...
Click to collapse
So what was your full procedure? I want to try this and try to install CM10 later.
From what I read, you installed the Photon Q CWM, installed Pizza through that, got boot loops, flashed back to stock, then installed Pizza again?
bconcio said:
So what was your full procedure? I want to try this and try to install CM10 later.
From what I read, you installed the Photon Q CWM, installed Pizza through that, got boot loops, flashed back to stock, then installed Pizza again?
Click to expand...
Click to collapse
Fastboot was kicking errors and was boot looping into fastboot with firmware flash fail, I found however I could start into AOSPizza in DB mode (Safe Mode) , so I did that, charged up the phone 100% then used RSDLite and Reflashed Stock current firmware, it however does not re-lock the bootloader as some have mentioned might be the case in other post's, from there I started up the phone,turned on usb debug, used "motochopper" to root it, then installed Rom Manager from the market, flashed clockwork to device with the Photo Q CWM , copied AOSPixxaV1.zip ( The ROM ) and GappizzaV1.zip to the Phones internal storage not on the external SD memory card, from there went to clockwork mod on my atrix opened up the program and selected to reboot into recovery, went to the mounts and storage then select Mount System then go back then install zip from sd card then choose zip from sd card, then scroll to your rom and select it and it will flash when its complete you will go back and go to reboot system now, it will ask you if you want to bypass stock recovery on boot select it and your phone will reboot into AOSPizza......Have Fun!
Hello, I was playing around with installing some ROMs and I think I might've wiped my clockworkmod recovery from within the recovery menu itself... The phone boots into AOSP and everything works as it should, but I can't access the recovery menu anymore, which I need to flash other ROMs and such. Would downloading the uvlg3.odin.zip from the ROMs, Kernels and Recoveries thread and flashing it with ODIN return it to stock AND install the stock Samsung recovery?
Yeah it would if you flash back to stock via odin
Sent from my SGH-T679 using xda app-developers app