hi,everyone.
i've just tried to install cm11 in my galaxy nexus and it cannot boot on now
its installation is fail because status 7 in the cwm recovery
i still cant boot on my phone
can anyone help me
What version of CWM Recovery are you on? An update of the recovery to a newer build might help.
Break me off a piece of that Kit-Kat ROM!
What version of Android are you coming from? Anytime you are switching to a different ROM, especially from a JellyBean (4.3 or other) to a KitKat 4.4 ROM, you must do a clean wipe of your phone prior to installation. It sounds like you tried to do a dirty flash. Boot into recovery, and format data, cache, and dalvik cache, then try flashing the CM11 and Gapps.
If that doesn't work...try this thread. http://forum.xda-developers.com/showthread.php?t=2302599
tonykunyin said:
hi,everyone.
i've just tried to install cm11 in my galaxy nexus and it cannot boot on now
its installation is fail because status 7 in the cwm recovery
i still cant boot on my phone
can anyone help me
Click to expand...
Click to collapse
dwoods1983 said:
What version of Android are you coming from? Anytime you are switching to a different ROM, especially from a JellyBean (4.3 or other) to a KitKat 4.4 ROM, you must do a clean wipe of your phone prior to installation. It sounds like you tried to do a dirty flash. Boot into recovery, and format data, cache, and dalvik cache, then try flashing the CM11 and Gapps.
If that doesn't work...try this thread. http://forum.xda-developers.com/showthread.php?t=2302599
Click to expand...
Click to collapse
i am coming from the stock android 4.3 rom. I've tried wipe the data,wipe cache and dalvik cache.However,it just keeps saying installation error in the cwm touch recovery because of the status 7.
That method doesnt work for me. i still even cannot boot on my phone.how can i send it in again
OK, first you need to manually boot into your recovery by holding the volume up and down buttons at the same time and then pressing the power button. You should get into your bootloader and then be able choose recovery. I assume you have a backup...so just flash back to your stock android 4.3. Then once you are able to get back into your phone see if you can update your cwm. If updating you cwm turns out not to be the issue then go watch a YouTube video on how to fix the status 7 error. It basically involves copying the zip file you are trying to flash over to your computer and editing one of the files. Goodluck...let me know if this works.
tonykunyin said:
i am coming from the stock android 4.3 rom. I've tried wipe the data,wipe cache and dalvik cache.However,it just keeps saying installation error in the cwm touch recovery because of the status 7.
That method doesnt work for me. i still even cannot boot on my phone.how can i send it in again
Click to expand...
Click to collapse
check your baseband..you should be in the latest radio..mine is XXLH1..other rom required latest baseband..
Pretty sure it sounds like he is on an outdated version of cwm, status 7 errors can be signs of old recovery version. Fastboot flash the latest cwm.
Related
I have a Samsung Galaxy Nexus GSM and have been trying to install the Paranoid Android flavor custom ROM, I had 2.22 installed not long ago but managed to screw it up when I updated it without clearing my security settings (I had a 4x4 pattern swipe which I couldn't enter with the update which restored it to 3x3 pattern) so I wiped and restored to stock 4.2. I'm now trying to re-install with any custom ROM but it's not working.
Whenever I install a ROM it seems to install ok but when I get to the boot screen it just hangs on the nexus/PA logo.
I've tried with:
Goo Manager
TWRP 2.2
TWRP 2.3
CWM 6.0.1.5
and with
PA 2.22
PA 2.99.1
PA 2.99.5
PA 2.99.6
PA 2.99.7
and I always get the same error, I've tried wiping all options within TWRP and CWM and going from there but that doesn't seem to work, the strange thing for me though is that if I re-install a stock Google ROM it works perfectly fine.
I'm fairly new so please be gentle.
flash the latest twrp and move the rom and gapps to your sdcard then follow this..
1. factory reset
2. wipe system
3. wipe cache
4. wipe dalvik
5. flash rom
6. flash gapps
7. reboot
if it still freezes at boot animation pull battery reboot to recovery wipe cache/dalvik and reboot
Thanks for the suggestion but that didn't work.
Any other suggestions?
When you say TWRP 2.3 do you mean 2.3.2.1? http://teamw.in/project/twrp2/90
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
zephiK said:
When you say TWRP 2.3 do you mean 2.3.2.1?
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
Click to expand...
Click to collapse
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Using TWRP, wiping cache, dalvik, and system should wipe everything except the sdcard contents. So doing these wipes should make your phone "bare stock" again as you described
Why don't you try downloading another custom ROM or download the same ROM again because maybe it is corrupted or something
osiris231 said:
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Click to expand...
Click to collapse
RANT: huh..... seriously? you couldn't have browsed around, searching for this COMMON issue (which usually comes down to user "error"), read the STICKIES, before posting?
first, internal storage = /data/media aka /storage/sdcard0/ aka /sdcard/
Please read all of this
http://forum.xda-developers.com/showthread.php?t=1626895
Hey guys,
I was installing the synergy rom r484 onto my galaxy s3 att variant and in the aroma installer it says that my device is d2spr but my device is actually d2att and I think that is why when I install the synergy rom it doesn't let me use my data and 4g. Can anyone help with this?
update your recovery with a d2att one. are you cwm or twrp?
I'm using cwm. Can you please guide me how to update the recovery to the d2att one? haha sorry I'm kind of a noob
let's see if this gets you straightened out. flash this in recovery, go to advanced and select reboot recovery. once back in, give synergy a shot again. do you know what version you're on now and where you got your current cwm from? just curious
xBeerdroiDx said:
let's see if this gets you straightened out. flash this in recovery, go to advanced and select reboot recovery. once back in, give synergy a shot again. do you know what version you're on now and where you got your current cwm from? just curious
Click to expand...
Click to collapse
When I tried to flash that file it started and then said "Installation aborted"
I've attached a picture
Oh and I'm not sure what version I'm running
can you boot into your device? if so, use Rom Manager to update your recovery.
if not, here is the previous version of CWM if you want to see if this takes care of you.
also, twrp is recommended for aroma installers. i'll attach a recovery flashable twrp zip. let me know if either flashes. if not, you may have to restore a backup (if you cant boot in now) and update your recovery that way.
xBeerdroiDx said:
can you boot into your device? if so, use Rom Manager to update your recovery.
if not, here is the previous version of CWM if you want to see if this takes care of you.
also, twrp is recommended for aroma installers. i'll attach a recovery flashable twrp zip. let me know if either flashes. if not, you may have to restore a backup (if you cant boot in now) and update your recovery that way.
Click to expand...
Click to collapse
I flashed the twrp.zip and then I tried installing synergy again and it finished and started rebooting and now it's in a continuous loop of rebooting
get it fixed?
if not, wipe cache and dalvik in recovery and reboot. if you're still looping, boot into recovery and wipe data/factory reset and reboot. report back, buddy
xBeerdroiDx said:
get it fixed?
if not, wipe cache and dalvik in recovery and reboot. if you're still looping, boot into recovery and wipe data/factory reset and reboot. report back, buddy
Click to expand...
Click to collapse
I've tried rebooting into recovery multiple times but it goes to the Team Win recovery screen and then goes back into the boot loop :crying:
odin back to stock, buddy. thats what i would do.
here's a link to the stock firmware with root already injected: http://forum.xda-developers.com/show....php?t=1739426
flash the tar in odin. make sure the auto reboot box is unticked. if you get a PASS after flashing, unplug the device, pull the battery, replace it and press the recovery button combo. once in recovery, wipe data and wipe cache. reboot.
you will be on rooted stock. you can install cwm or twrp from rom manager or goo manager from there.
otherwise, your other option is to flash recovery from odin via this link: http://forum.xda-developers.com/showthread.php?t=2042775
download the root kit and flash the recovery.tar from odin. boot into recovery and flash that cwm 6.0.3.1 update i linked you to earlier. reboot recovery (under advanced) and proceed with flashing synergy or flash this recovery-flashable stock rom to get you started. you can decide where you want to go from there.
xBeerdroiDx said:
odin back to stock, buddy. thats what i would do.
here's a link to the stock firmware with root already injected: http://forum.xda-developers.com/show....php?t=1739426
flash the tar in odin. make sure the auto reboot box is unticked. if you get a PASS after flashing, unplug the device, pull the battery, replace it and press the recovery button combo. once in recovery, wipe data and wipe cache. reboot.
you will be on rooted stock. you can install cwm or twrp from rom manager or goo manager from there.
otherwise, your other option is to flash recovery from odin via this link: http://forum.xda-developers.com/showthread.php?t=2042775
download the root kit and flash the recovery.tar from odin. boot into recovery and flash that cwm 6.0.3.1 update i linked you to earlier. reboot recovery (under advanced) and proceed with flashing synergy or flash this recovery-flashable stock rom to get you started. you can decide where you want to go from there.
Click to expand...
Click to collapse
If I odin back to stock will it delete all my music and pictures and etc.?
Okay I'll try the second thing and I'll report back in a bit. Thank you so much for taking the time to help me.
Okay so I got that recovery that you gave me earlier installed (the cwm 6.0.1.3) after using odin and the att gs3 root and then flashing after that. Then when I went back into recovery and tried to install the synergy rom it started and then the aroma installer froze and my phone went back into the loop. I can get into recovery now though but I don't know how I should install synergy
Honestly? This is a picky rom. I would abandon it for a more stable install and operational rom, whether that be a touchwiz base or aosp. It doesn't seem to be working with you at all.
Okay I installed the cyanogen mod stable build and now I'm just waiting for it to finish booting up. Thank you so much for all your help!!!
That's what we're all here for. Lemme know if that did/didn't boot up for ya :good:
Okay it's still at the same booting screen where it says CyanogenMod and the blue circle is spinning around it.
Wipe data/factory reset, wipe cache and dalvik. Reflash rom and gapps. Wipe data and cache again. Reboot and give it a few minutes.
That's my suggestion.
Routed by Galaxy S3
xBeerdroiDx said:
Wipe data/factory reset, wipe cache and dalvik. Reflash rom and gapps. Wipe data and cache again. Reboot and give it a few minutes.
That's my suggestion.
Click to expand...
Click to collapse
My Galaxy at&t phone had the same problem after flashing with Synergy (my first flash on my new Galaxy S3 phone). It lost its identity and though it was a Sprint phone. Next I tried installing a different custom ROM, but I couldn't install CM10.1 (and still can't now) because it thinks it was not a d2att.
There were only two ROMs I was able to do installed since then. They were the Serenity 1.2 and its predecessor. I had to restored phone back to stock, root, and flash ROM. For a while, it was pretty grim as my phone had gotten very unresponsive and lethargic with all the fixes I tried during the time my phone thought it was a d2sp (no data).
After going back to stock using Odin, the phone finally could accessed the data network again and showing SGH-I747 instead of the Sprint version. I tried flashing CM10.1, but it still didn't think it is a d2att since it aborted when it did the check for d2att.
Nest, I flashed the DrewGaren's JellyBean747 version 1. Then I flashed DrewGaren's Serenity 1.2. Both were mostly working OK, but there are still some bugs.
Unfortunately, the DrewGaren's series seem to be dead projects since he didn't seem to be doing anymore improvement since Jan 2013.
Samsung S3 had me routed. My previous phone was HTC Inspired, and I rooted it instead of it routing me
Hello,
I have a unique issue. I'm having a problem installing any custom rom on my t999 (tmobile). I have been using a custom rom for over a year. Always used TWRP. Started with Paranoid Android and for the last few months I've been using PAC-Man (nightly) roms. I was having gps lock issues, I decided to upgrade the modem to a leaked UVUEMJC, this fixed the gps lock issue. But after the reboot, I was stuck on bootloader screen. The only way I could get the rom to work was to backup the rom, flash the system and data, and after that, the rom would work until reboot. I did this a few times until it stopped working. My efs was corrupted, IMEI missing, To recover it, I went into download mode, and noticed in red Warranty bit =1. I used odin to flashed a rooted cf 4.3 samsung touchwiz rom (root66_TMO_T999UVUEMJC). All imei/efs issues were fixed. I decided to try installing a custom rom again, PAC-Man rom, it installed just fine, all EFS/IMEI info was intact, but at reboot, I got stuck on the CM bootlogo. This happens everytime. IF I recover a backup, it gets stuck on the boot logo. I'm using TWRP v2.6.3.
Anybody have any suggestions on how to fix this issue?
Thanks!
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Perseus71 said:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Click to expand...
Click to collapse
Thanks for the reply Perseus71. I'll give it a shot!
acedik said:
Thanks for the reply Perseus71. I'll give it a shot!
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Donny Orbit said:
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Click to expand...
Click to collapse
You need to post info about the error
Sent from my SGH-M919 using Tapatalk
It says
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I tried flashing the Rom that doc fixed specifically for the T999LTE for the CM10.1.2 also with no avail.
Same problem.
D
wipe Dalvik and Cache before trying the rom again. If
Hi, I'm on the 4.4.2 version of the Sickness, with the MDL bootloader. I've updated the modem to NH7.
Do I need to go through the whole process of updating the firmware, re-rooting, etc., or can I just do a full wipe and update to the Sickness' 4.4.4 V3?
I tried a full wipe and installing it today, but I ran into bootloops/other failures.
its better to use the latest recovery like twrp becuz in twrp 2.8.0.1 which is the latest recovery you can choose wipe and then advance wipe and choose dalvik cache,system,data and cache then wipe and that normally takes care of the boot loops
rblckmnjr84 said:
its better to use the latest recovery like twrp becuz in twrp 2.8.0.1 which is the latest recovery you can choose wipe and then advance wipe and choose dalvik cache,system,data and cache then wipe and that normally takes care of the boot loops
Click to expand...
Click to collapse
CWM and Philz also allow you to wipe system, data, cache, and even the non-existent Dalvik cache partition.... Your post makes it sound like TWRP is the only recovery that does that Just saying..
jonnyboy2040 said:
Hi, I'm on the 4.4.2 version of the Sickness, with the MDL bootloader. I've updated the modem to NH7.
Do I need to go through the whole process of updating the firmware, re-rooting, etc., or can I just do a full wipe and update to the Sickness' 4.4.4 V3?
I tried a full wipe and installing it today, but I ran into bootloops/other failures.
Click to expand...
Click to collapse
As to your question; you should be able to do a full wipe (system/data/cache and even though it literally does nothing because the partition doesn't exist, dalvik) and then flash with no problems. I would say that since you're still one of us few lucky ones still with MDL bootloaders, try to keep an official update as a very last option!
Were you trying to flash a kernel or any other mods along with the ROM? If so, flash only the ROM itself and see how it works.
You say bootloops/other failures... that means you bootloop a lot, and when you don't bootloop something else happens. Could you be more specific on the "other failures?" Any error messages? Were you able to pull a logcat? Did you compare the MD5's? Doesn't sound like a bad download, but you never know...
i understand what you saying however i ran into the same problem using philz touch and got the latest twrp and havent got stuck in boot loops since i read a forum on this and using older recovery to flash kitkat roms has been having people phones stuck in a boot loop and throwing errors after flashing and they updated the recovery to fix it
Sh*t, I have TWRP 2.6 and never have a problem. IMO (and some others) newer versions don't seem to play well with others. That goes for all Recoveries.
As for your issue, you might have a bad DO. Try re downloading the ROM, full wipe and then flash.
well my phone didn't like philz touch it works better with the latest twrp recovery
I actually ran into this last night with philz.. I tried flashing insane 4.4.4 v3 and got stuck in a bootlooop I couldn't recover from. It flashed v1 just fine, but it just wasn't having any of v3. I had to use Odin to flash the latest TWRP and have had no problems.... :/
lordcheeto03 said:
I actually ran into this last night with philz.. I tried flashing insane 4.4.4 v3 and got stuck in a bootlooop I couldn't recover from. It flashed v1 just fine, but it just wasn't having any of v3. I had to use Odin to flash the latest TWRP and have had no problems.... :/
Click to expand...
Click to collapse
Sickness mentioned something about a script that was causing bootlegs when flashing
I'm having some issues flashing any ROM. TWRP will not wipe data, or internal SD
For some reason, when I go to wipe data and factory reset, TWRP will say it was successful, but nothing ever gets wiped. It will only wipe system if I choose to. I've gotten a ROM to flash but when it boots up, all of the old apps and user data are still there and it makes everything crash. I've gotten into settings to do a reset, it reboots into recovery, runs the script, and still nothing wipes.
What I have tried:
Old TWRP, newest TWRP
CWM (seems to wipe but it won't get past the note 2 screen after flashing anything)
Wiping with CWM, flashing TWRP, then flashing a ROM (still loops after the note 2 screen)
Is there a terminal command I can use in TWRP to manually wipe things?
Thanks for any help I can get, I've flashed so many phones I can't remember but I've never had this issue
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
audit13 said:
Maybe flash back to a stock ROM, factory wipe using stock recovery, then flash TWRP?
Click to expand...
Click to collapse
Well when it bootloops t the Note 2 screen, I have to flash a ROM with Odin to get it working again. I've flashed a stock ROM with Odin, flashed TWRP with Odin, tried the wipes and it never wipes anything... I'm lost...
Isn't there a format function in TWRP that is seperate from the factory reset or advanced wipes? I was also trying to find a terminal command to type in the terminal in TWRP... I'm a little stumped...
I'm sorry, I read that too fast... That may actually work, wipe it in the stock recovery, and just don't let it boot into the system before flashing other stuff... I'm gonna try that out... Thanks man, I'll post back about it...
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
audit13 said:
Since you are flashing the phone with Odin, is it a stock 4.1.1 ROM you're flashing? Which custom ROM are you flashing to the phone?
Click to expand...
Click to collapse
The stock ROM I used is I317-ODIN-UCUCNJ1-Stock without the booloader packaged in, I'm still on the old bootloader. It's 4.4.2
The ROMS I've tried to flash was
Cyanide (Error 7, says incompatible data, please wipe the phone)
Resurrection Remix (Error 7, says incompatible data, please wipe the phone)
Latest CM10 Nightly
I got CM10 and Resurrection Remix to flash a couple times, but the phone boots and all the old apps and data, including the AT&T ones are still there, and the system keeps crashing. Then I change the recovery to CWM because it seems to wipe, change back to TWRP, flash the ROM and gapps again, but it bootloops at the Note 2 screen.
Should I try the 4.1.1 ROM and CWM? Whenever I'm going from a stock TW to non-TW I like to format everything, data, cache, system, and internal SD, but of course TWRP won't wipe the data or the internal SD.
It's probably because the bootloader and modem are too old for the roms. Recent roms will need updated bootloaders.
Ok, I had some more time to mess around with this today and figured it out. I feel kind of dumb but oh well, I got it.
TWRP was already loaded on, so I went to messing with it again. The 'Swipe to factory reset' was not wiping the data, and there was the 'Format Data' button right there in front of me. I did the factory reset, format data, rebooted recovery, wiped dalvik, cache, and system, then flashed the ROM and everything booted up just fine.
Thanks for all of the help!