Related
I did a factory reset on 2.3.4 official after installing alien rom and theme, and now I cannot go into settings. The icon doesn't exist in the app tray. Now I can't connect to the internet or enable debug. Also it says that I have no service. And when I try to go in android recovery and tap on the bottom right corner nothing happens. Could someone tell me what I can do please? Thank you.
sounds like a bad install... did you do a full wipe beforehand?
do a full wipe, wipe cache, wipe dalvik cache, then reinstall.
note full wipe is not just a factory reset from the OS you need to wipe from tenfar's clockwork recovery, or connect via USB and run moto-fastboot -w
I didn't because in the install instructions for the rom it didn't say I had to, and I didn't know I was supposed to. (i'm a noob).
While on a homescreen, hit the menu button, and then "settings" to get in if the icon is missing.
DK
I did that then the launcher force closes and restarts
well now you know
before installing any ROM you need to (to ensure a clean start)
go into clock recovery, wipe (alternatively, connect via USB, make sure you have correct drivers I presume so if you've been flashing and unlocking BL, go to moto-fastboot directory, start command line, and do moto-fastboot.exe -w)
then in clockwork recovery, wipe cache
then in clockwork recovery, advanced - wipe dalvik cache\
THEN flash away
obviously this wipes everything so backup your info/apps beforehand
I'll remember that for the next time I install a rom, even though when I had 4.1.83 and installed greyblur I never wiped anything, it wiped everything when I installed the rom. Now I need to know what are my options... Could I flash 4.5.91, or will it brick my phone? or is there another way to fix this?
I flashed sbf 4.5.91 and it worked. Thanks for the advice.
I was attempting to flash clockworkmod and I am now stuck in recovery. Attempting to reboot does nothing, I did a factory reset. Applying update.zip just gives me the error in the title of this thread, plus "can't mount update.zip"
I see this thread: http://forum.xda-developers.com/showthread.php?t=782204 as a last option but is there anything else I can do? If I remove my sd card and put a new update.zip on it manually, will this fix the problem?
ok a few things first.
1)which CWM did you install?
2)Which Rom are you trying to install?
if you have the rom on your sd card simply factory rest, wipe cache, and dalvik cash......
then without rebooting flash zip from sdcard [navigate to and flash your rom]
then reboot.
you shouldn't need the apply update zip
if that doesn't work odin a stock image and start all over again
xwhofarted said:
ok a few things first.
1)which CWM did you install?
2)Which Rom are you trying to install?
if you have the rom on your sd card simply factory rest, wipe cache, and dalvik cash......
then without rebooting flash zip from sdcard [navigate to and flash your rom]
then reboot.
you shouldn't need the apply update zip
if that doesn't work odin a stock image and start all over again
Click to expand...
Click to collapse
I'm not sure which version, the file only says "cwmrecovery.tar"
I'm trying to install CyanogenMod 7.1
Can you explain a little more regarding wiping cache and dalvik cache, and also how to flash the rom without using any application. I only have access to "reboot system now", "apply sdcard:update.zip", "wipe data/factory reset" and "wipe cache partition" as of right now
EDIT: Clockworkmod recovery is not functioning, if that was not clear.
Follow this guide for installing mtd roms such as cm7, aosp, miui...Just replace vgb rom with cm7.
http://forum.xda-developers.com/showthread.php?t=1212239
I am using the latest Unnamed 1.1.0 ROM and when I use the shutdown feature, the phone will shutdown, but then reboot immediately. For my install I wiped both data cache and delvik cache before installing, however, I didn't flash from a stock 2.3.4 ROM. Since the directions did not say that was needed, is that not the case, or is this a known bug with unnamed 1.1.0?
Shutdown
crimsonphire said:
I am using the latest Unnamed 1.1.0 ROM and when I use the shutdown feature, the phone will shutdown, but then reboot immediately. For my install I wiped both data cache and delvik cache before installing, however, I didn't flash from a stock 2.3.4 ROM. Since the directions did not say that was needed, is that not the case, or is this a known bug with unnamed 1.1.0?
Click to expand...
Click to collapse
If you did not flash from stock 2.3.4 rom and you did not flash from the
previous version of the UnNamed rom that means that you forgot to do a
"Wipe data/Factory Reset" in the clockworkmod recovery before flashing
the UnNamed rom.
Your best bet is to reflash the UnNamed rom but this time when you are in
the clockworkmod menu (CWM recovery) select the "Wipe Data/FActory Reset"
before you flash the rom. (you may want to do a titanium backup of your apps first)
Good Luck!
Also, if you install a theme from a different ROM, the shutdown menu may become rearranged or even nonfunctional.
Thanks Misterjunky, I'll give that a try. Coming from the Samsung Captivate I find the new ROM process a little frustrating. I have been using ODIN to flash the Clockwork (CW) Recovery kernel, then install ROMs via the CW menu. Two questions:
-Is the Wipe Data/Factory reset right there next to the devlik/cache clear on the first CW screen or hidden in advanced?
-Is there an easier way to flash ROMs other than pushing the CW kernel via ODIN?
Entropy512 said:
Also, if you install a theme from a different ROM, the shutdown menu may become rearranged or even nonfunctional.
Click to expand...
Click to collapse
Straight stock Unnamed 1.1.0 here...
Kernels
crimsonphire said:
Thanks Misterjunky, I'll give that a try. Coming from the Samsung Captivate I find the new ROM process a little frustrating. I have been using ODIN to flash the Clockwork (CW) Recovery kernel then installing ROMs from the CW menu. Two questions:
-Is the Wipe Data/Factory reset right there next to the other one on the first CW screen or hidden in advanced?
-Is there an easier way to flash ROMs other than pushing the CW kernel via ODIN?
Click to expand...
Click to collapse
The "Wipe data/factory reset" is in the default screen which you see first.
Also you only need to flash the odin3 kernel once, not everytime you flash a custom rom.
(SGH-I777_ClockworkMod-Recovery_5.0.2.3.TAR - kernel).
The reason is, that if coming from STOCK Gingerbread 2.3.4 rom we cannot flash any custom
roms without first flashing the odin flash kernel because the stock rom does not have a CWM
Recovery compatible kernel.
The other kernels you see here in XDA for our phones are CWM flash zipfiles which we can flash
since after flashing the custom odin3 kernel we now have a kernel that has CWM Recovery
built-in which is required for flashing any compatible custom roms, kernels, themes and other
modifications. (Which are all zipfiles ) - I hope this explains it.
Thanks for the info Misterjunky, that helped. Unnamed isn't rebooting on power any more either. Reinstalled, no issues, must've forgotten to clear both options prior to install.
EDIT: My phone is now working. Read at end of OP Below for the trick. Credit goes to thomascw: http://forum.xda-developers.com/showpost.php?p=21173699&postcount=69
My phone is going into a cycle that I am unable to get out of.
I followed instruction on how to fastboot flash recovery and update to whatever rom version.
My phone baseband is the 347 US stock rom. Here is the cycle my phone is getting into:
I have placed the update.pkg in the root of my sd card (At various times I tried various roms but always matched the region between recovery and rom)
I flash the recovery image using fastboot. Both my phone and my command prompt (I use linux) say OK and writing is done.
I do fastboot reboot and the phone reboots fine.
I hold the (vol+,vol-,pwr) keys to boot into recovery. When booted, it always show the correct recovery image that I just flashed. So seems OK!
I highlight the 2nd option which is the update from sd card. It goes fine and it finishes installation.
The phone boots but it gets stuck at the dell logo indefinitely. The phone is not responsive at this point and only removing battery is the option.
I replace the battery and let the phone boot but it shows me this message
Start emergency recovery copy....
Click to expand...
Click to collapse
Apparently the device is rewriting stock recovery into the recovery partition.
The phone reboots after finishing the copy into recovery mode again asking me to reset, update, ...etc.
This cycle always happen no matter what rom versions I choose. Well, stock roms only. I did not try modified ones.
I am unsure how to get out of the cycle as I tried every option, like reseting after flashing. I even flashed a backup copies of the 347 system and boot images. Always goes at the end to rewrite the stock recovery image (steps 7 and 8 above).
- SOLVED: last night, I flashed 360 as mentioned in steps 1-5 above. now, Instead of step 6 above, do these:
After streakmod recovery image flashed, fastboot reboot then vol+,vol-,pwr to go into recovery mode.
choose option 2 (upgrade from sd card) --- this will take you into another menu with more options.
Choose factory reset, wipe data, wipe cash,dalvik cash and all that.
Next get to advance option listed. From there, choose fix permissions (not sure if this is necessary but I did it anyway.)
From android back button, go back to previous menu.
Choose the reboot option.
Again hold vol+,vol-,pwr to go into recovery mode. Now choose factory reset (not sure if important, but did it anyways)
Phone will reboot into the rom you installed in step 5 above.
It worked from first time. I got encouraged and I even followed the steps again and I installed GB stock rom and also worked from first time. I am not sure I like the GB 407 rom over the 360 ROM, especially I get the annoying flashing lights every now and then because of the mismatch between the 407 region 14 and baseband region 00. But this is another issue.
Did you at some point try a Gingerbread based ROM? I have seen others have issues reverting to Froyo after that.
If you can get to recovery, for the ROM you want to run:
Make sure the pkg file for your ROM is on the root of your SD Card and is named update.pkg
Flash the amss.mbn file, dsp1.mbn file and the recovery.img with fastboot.
use the command fastboot reboot to reboot your Streak and make sure that you go directly to recovery
Now select step 2 and do the update
Since there is no pkg, recovery, amss or dsp1 files for BB 347 you will need to use a different baseband (I use 351, 360 is the latest). Use 407 if you must have Gingerbread.
ROM and related file Downloads
Flashing Guide
My take on Streak modding
Edit: the above steps should work even if you have never tried installing a Gingerbread ROM.
Thank you.
I've done all the steps you mentioned, except the second point. I never tried them. At least I have some new steps to follow. To which partition shall I flash the *.mbn files? Where do I find these files for a specific rom?
OK. Found amss and dsp1 files that are bundled with recoverySM.img (custom one), can I use these files with any ROM or are they rom and/or regional specific? I am confused because I do not see these files in the wiki page with the stock roms.
OK guy forgive my ignorance. I found the corresponfing .mbn files under manii's directory provided by your links.
I am trying them now. Crossing fingers and will let you know how it goes.
Thank you.
Back to the cycle. I added flashing both amss.mbn and dsp1.mbn to the process, but got the same pattern. I used the 360 build downloaded from mirror2.streakdroid.com/manii/360 directory. After the flash, the device hangs on dell logo screen. I remove the battery and replace it. I turn it on, and let it boot but this time it reverts to the emergency stock recovery image 347.
I will try tomorrow to get custom GB roms and see if they work.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
That's a well known issue with 347 firmware.
You should use streakflash tool to restore it to 305 lowlevel fw version, and continue from that point.
Very detailed article of using streakflash:
http://forums.whirlpool.net.au/archive/1557150
I'm experiencing exactly the same problem: I tried to update 347 to 360 and now I'm stuck at the boot logo :-(
I tried several stock images and yet no luck... Even the article mentioned above won't help me out ouf this misery.
Is there something else I could try?
ive also had this 4 or 5 times, so i replaced my inner sd with a 2gb sdhc ,think maybe the card was at fault
Dikos found an answer some where
Flash stock 360 recovery
Reboot
Hold Volume buttons
Option 2 - Recovery mode
Install stock 360 rom.
Fastboot
Flash streakmod
Hold Volume buttons
Option 2 - Recovery mode
wipe cache partitions and dalvik cache
Reboot
Hold Volume buttons
Option 1 - Factory Reset
Worked for me,now using 407 olleh, was on 360 for an hour,the key appears to be flashing back to streakmod and wipe cache partitions and dalvik cache before factory reset
I think this should be stickied
Well, whatever a "dalvik cache" is, it even works without clearing it!
Unfortunately my baseband is still at 347. Is that the reason for my leds to flash about 9 times every minute?
apirec, clear dalkic cache is under advanced options in steakmod recovery. The flashing is probably related to needing to flash the right amss and dsp1 mbn.
path to streakmod
Can anyone please confirm the link to latest streak mod.
Is it same as the link on
http://forum.xda-developers.com/showthread.php?t=840326 for
recovery-v0.3.2.8-beta.zip
-Mohan
thomascw said:
apirec, clear dalkic cache is under advanced options in steakmod recovery. The flashing is probably related to needing to flash the right amss and dsp1 mbn.
Click to expand...
Click to collapse
No, I did clear that cache, too (for the first time). But then I did the procedure again (without clearing that cache) to get the right baseband and to get rid of the flashy leds.
How would I flash the right amss and dsp1 mbn?
Mohan Nade said:
Can anyone please confirm the link to latest streak mod.
Is it same as the link on
http://forum.xda-developers.com/showthread.php?t=840326 for
recovery-v0.3.2.8-beta.zip
Click to expand...
Click to collapse
Yes, that's the correct link.
---------- Post added at 10:31 AM ---------- Previous post was at 10:02 AM ----------
apirec said:
How would I flash the right amss and dsp1 mbn?
Click to expand...
Click to collapse
Ok, found it myself: http://mirror2.streakdroid.com/manii/360/
But what are the other files for? Will it do any good, if I flash them, too?
If you have flashed recovery and gone through update, as far as I know,all you need are the amss and dsp1. I've read that the update.pkg reflashes the baseband, not true on my phone. One of the multirecoveryflasher tools has a baseband flasher built in. I havent used it, but it I think it probably just flashes the above 2 files.
thomascw said:
Dikos found an answer some where
Flash stock 360 recovery
Reboot
Hold Volume buttons
Option 2 - Recovery mode
Install stock 360 rom.
Fastboot
Flash streakmod
Hold Volume buttons
Option 2 - Recovery mode
wipe cache partitions and dalvik cache
Reboot
Hold Volume buttons
Option 1 - Factory Reset
Worked for me,now using 407 olleh, was on 360 for an hour,the key appears to be flashing back to streakmod and wipe cache partitions and dalvik cache before factory reset
I think this should be stickied
Click to expand...
Click to collapse
Thank you here again for pointing out the solution. I have updated my OP to reflect the solution to this problem.
I've recently flash Aura ROM, and it was successful. Now I want to try the Neutrino build. Do I have to flash back to my Stock Gingerbread 4.5.91.img and then flash Neutrino?
Or do I simply go ahead and flash Neutrino with these steps.
-boot to recovery
-wipe dalvik&wipe cache
-factor reset/data
-flash ROM in recovery
-wipe dalvik&wipe cache again
-reboot
Sadly I did not do a backup on CWM(Using Rom Racer's).
You don't uninstall a rom. You wipe and flash another.
Each rom's thread will give the wiping instructions that work best; I've only stuck with blur roms and have had luck with -- AFTER backing up -- booting into fastboot and issuing "fastboot -w", then reboot to recovery, wipe data, cache, & dalvik, and then flashing the rom.
Others recommend first wiping everything separately using fastboot (and someone will likely chime in here). If you want Neutrino, head over there and see what wipe procedures users have found the most success with.
sheeparecurious said:
You don't uninstall a rom. You wipe and flash another.
Each rom's thread will give the wiping instructions that work best; I've only stuck with blur roms and have had luck with -- AFTER backing up -- booting into fastboot and issuing "fastboot -w", then reboot to recovery, wipe data, cache, & dalvik, and then flashing the rom.
Others recommend first wiping everything separately using fastboot (and someone will likely chime in here). If you want Neutrino, head over there and see what wipe procedures users have found the most success with.
Click to expand...
Click to collapse
After all this time! I've always thought you'd have to go back to your stock ROM. Thanks a bunch sheeparecurious! Neurtion seems to want you to wipe everything.
Do I need to wipe dalvik and cache everytime I flash a simple mod or add on?
Depends on the rom. Does the OP in the Neutrino thread say anything specific?
I've been able to flash mods without clearing any caches. I've seen two themes "not play nicely" when flashing one after another, and others were fine to go from theme to theme.
"Wiping data may not be necessary with every update, but it's best to flash clean. However, if you regularly flash the updates, you'll most likely need to wipe data at some stage anyway."
It says to wipe when you flash updates. Does he mean updates to Neutrion updates?
Here's thread link. If you'd like to look for yourself. http://forum.xda-developers.com/showthread.php?t=1398819
Thanks in advanced. I'm headed to bed now. Very pleased as to how things went today on my phone.
Yeah, he probably means "updates to neutrino." I'd say if you successfully flashed the rom and any additional mods you wanted, and the phone is working well, make a nandroid backup so you have a good restore point.
Whenever it comes around, try the next update without wiping - either it'll work fine & life is great, or something will be screwy & you'll need to wipe clean and flash from a fresh state anyway (or restore your backup state).
Sent from my MB860 using XDA
sheeparecurious said:
booting into fastboot and issuing "fastboot -w", then reboot to recovery, wipe data, cache, & dalvik, and then flashing the rom.
Click to expand...
Click to collapse
fastboot -w does the same as wiping data and cache in recovery.
---------------------------------------------------------------------------
For the best results, when you want to flash a new ROM you should always perform a full wipe in fastboot per the following to make sure you will avoid any unforeseen complications:
reboot to recovery
wipe Dalvik
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
reboot
If you are updating an exisiting ROM, then you would normally just reboot to recovery, wipe Dalvik and cache, then flash the update unless the dev has instructed otherwise in the ROM's thread.
You should ALWAYS do a nandroid backup of your current ROM through recovery prior to wiping and flashing anything. Much easier to restore to a previous state than have to set-up completely from scratch again if something goes wrong.
See? Told ya someone would chime in.
and I knew "fastboot -w" did the same data/cache wipe as in CWM, something something placebo effect can never be too sure. Wouldn't feel right if I didn't do it anyway.
Now, I never erased the webtop when I started flashing roms -- I only did the 2.3.6 webtop fruitcake because it was an update compared to my original one. Granted, I stuck with blur roms but it didn't seem to cause any issues. I assume if I were to switch to a CM-based rom, it could cause glitches if I don't erase the webtop partition?
You guys are awesome thanks! I copied down the procedure you recommended CaelanT. This will help me a ton.
Sent from my MB860 using XDA
Thanks for that CaelanT thats also useful to know, I have only just entered the world of different roms.
I always do a CWM backup and then a factory reset, wipe the dalvik cache and then flash the new ROM and any add-ons or kernels. Don't forget to wipe your battery stats/calibrate your battery. (I turn off my phone, charge it to 100%, wait about 15 minutes to be sure and boot into recovery to wipe the battery stats)
Sent from my MB860 using XDA App