Related
Ok. I unlocked my phone using the HTC method. Flashed a working recovery. Flashed synergy ROM and everything went smoothly. Now when I tried to flash miui and steel ROM, I can't get past the lockscreen. Can someone help?
Sent from my PG86100 using XDA App
bleichtman said:
Ok. I unlocked my phone using the HTC method. Flashed a working recovery. Flashed synergy ROM and everything went smoothly. Now when I tried to flash miui and steel ROM, I can't get past the lockscreen. Can someone help?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Problems occur sometimes when something is missed when delating i.e deleting cache, dalvik cache or factory reset etc is missed. Did you do all?
Also i once had a problem because i was using a download manager and partially paused the download. When i switched my laptop back on to resume the download ...it did resume and it did download the entire ROM but somewhere something got corrupted and i couldn't get past the boot screen.
Above is just my personal opinion. No harm in trying to re download a new ROM.
elevation_2 said:
Problems occur sometimes when something is missed when delating i.e deleting cache, dalvik cache or factory reset etc is missed. Did you do all?
Also i once had a problem because i was using a download manager and partially paused the download. When i switched my laptop back on to resume the download ...it did resume and it did download the entire ROM but somewhere something got corrupted and i couldn't get past the boot screen.
Above is just my personal opinion. No harm in trying to re download a new ROM.
Click to expand...
Click to collapse
I actually redownliaded, wiped numerous times. Tried infected and that worked. Could the kernel be a reason?
Sent from my PG86100 using XDA App
Hey guys, I continually get this error message upon manually forcing my phone into recovery. I'm on UCLF5 ICS OBJECTION from btw with the latest version of cwm. I would appreciate some help with regard to what exactly it means and how I can fix it.
Also my phone won't shut down properly. The lights on the bottom buttons stay on and I have to manually force it to reboot like I do to get it into recovery. The shortcuts in the rom aren't working for me.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
tmb993 said:
Hey guys, I continually get this error message upon manually forcing my phone into recovery. I'm on UCLF5 ICS OBJECTION from btw with the latest version of cwm. I would appreciate some help with regard to what exactly it means and how I can fix it.
Also my phone won't shut down properly. The lights on the bottom buttons stay on and I have to manually force it to reboot like I do to get it into recovery. The shortcuts in the rom aren't working for me.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
I would put it into download mode and run odin or the Off ics to redo/repack your folders, then put CWM back on....idk
Just putting some ideas in, maybe the guru's will jump in on the thread...
Before nuking it like that... try going to mounts and storage and formatting cache
Although I'm not even sure that error is anything to worry about honestly...but i don't do nandroids personally so Idk for sure.
And Joe....stop quoting the op, please?
Does this error have anything to do with the CWM version being used? Its calling for the external sd card isn't it?
No it's calling on the /cache partition which is in the phone...
But it could be the cwm version, it's looking for a recovery log that it can't open.
I can't do anything with the cache. Its like it doesn't even recognize it. I noticed this when I went to throw another rom on and clear out my caches and it would just freeze. I left it for a half hour once just for the heck of it but it didn't do anything. I had to reboot the phone into recovery again.
Sent from my SAMSUNG-SGH-I717 using xda premium
And I have the latest version of cmw installed.
Sent from my SAMSUNG-SGH-I717 using xda premium
What will "fix permissions" do?
I would downgrade cwm, I've been using brawway's touch version since he released his latest, without issue and i think that was in April or may
And fixing permissions, makes the permissions of all apps and .jars be what they should be.
Example: apps in /system/app need rw-r-r permissions, sometimes pasting some of those in will not set them correctly, and if you're doing a bunch at a time is a real pain to go through individually and change them, so that option makes sure everything everywhere matches the permissions needed. So, not applicable in this case.
Well I managed to get another rom on anyway so I don't think its big deal now. I think I might just leave my phone alone now
The collectives 4.04 aocp rom is pretty freaking sweet lol.
Sent from my SAMSUNG-SGH-I717 using xda premium
studacris said:
And fixing permissions, makes the permissions of all apps and .jars be what they should be.
Click to expand...
Click to collapse
Thanks for the explanation.
What is the equivalent of the chkdisk dos command to make the android system rebuild the directory structure? Can you do that through a terminal emulator?
i dunno if there is one other than just reflashing
So basically just flash a new cwm over the one I have now?
Sent from my SAMSUNG-SGH-I717 using xda premium
Yes
this is the version I've been using for months
If u could get it to boot. And manually set permissions for android.policy.jar that would fix the shutdown issue.
silver03wrx said:
If u could get it to boot. And manually set permissions for android.policy.jar that would fix the shutdown issue.
Click to expand...
Click to collapse
Thanks, I decided to switched roms and the problem went away completely. So thats one down
studacris said:
Yes
this is the version I've been using for months
Click to expand...
Click to collapse
Awesome. Ok, last question. I'm assuming I can just load this onto my phone via Odin like I did my original version of cmw?
Sent from my SAMSUNG-SGH-I717 using xda premium
Yeah, That or there is also a .zip that can be flashed from your current version of cwm.
If doing it that way after it flashes go to advanced option and reboot recovery, then once in the new one, clear caches and see if that fixes the issue.
Or, just use Odin then boot into recovery and wipe, either way is up to you, but seeing as how it's cwm that's the issue, i might lean towards using Odin myself... Just note that will increase your flash counter iirc, if you care.
studacris said:
Yeah, That or there is also a .zip that can be flashed from your current version of cwm.
If doing it that way after it flashes go to advanced option and reboot recovery, then once in the new one, clear caches and see if that fixes the issue.
Or, just use Odin then boot into recovery and wipe, either way is up to you, but seeing as how it's cwm that's the issue, i might mean towards using Odin myself... Just note that will increase your flash counter iirc, if you care.
Click to expand...
Click to collapse
Ok great. Thanks guys!
Sent from my SAMSUNG-SGH-I717 using xda premium
Samsung SCHi717 OnlyOne Goldie SMS error
Has anyone else ran into the issue of the stock SMS notifications not going away? When I get a txt message, regardless of how many, it always says I have an unread message. This happened with OnlyOne HYFR and then With Goldie also. Is this a known issue, or is there a way I can just quickly correct this?
Also, I can't find anything that says how to diable the scrolling wallpapers. I wanted static wallpapers for each home/menu screen.
Any advice is appreciated.
-Bugz
bugzinc said:
Has anyone else ran into the issue of the stock SMS notifications not going away? When I get a txt message, regardless of how many, it always says I have an unread message. This happened with OnlyOne HYFR and then With Goldie also. Is this a known issue, or is there a way I can just quickly correct this?
Also, I can't find anything that says how to diable the scrolling wallpapers. I wanted static wallpapers for each home/menu screen.
Any advice is appreciated.
-Bugz
Click to expand...
Click to collapse
Wrong thread.
Sent from my SAMSUNG-SGH-I717 using xda premium
K I'm using boot manager to install a cm9 Rom and it keeps failing at creating boot.img. I don't know what I'm doing wrong since I've herd of others installing cm9 roms sucessfully using boot manager. Maybe it's something in my settings? Tried making a thread at init2winit forums but have not gotten any response over there. Anyone here willing to help me out? I would greatly appreciate it.
Sent from my ADR6425LVW using Tapatalk 2
that usually means you dont have enough space
Thanks for the advice. I did check my SD storage and it said that I only had 1.16GBs left. So I thought that this could be true I suppose. So I switched to int. Storage as the install location(which I have 9.67GBs available on) and its causing my phone to lock up and freeze. Happened right at the part "extracting Rom please wait..." Weird...
Sent from my ADR6425LVW using Tapatalk 2
boot manager doesnt surport rexound officially,maybe thats the final answer. i encounterred the same issue too,but when i reinstall the app,it works just fine.
Sent from my ADR6425LVW using xda premium
anubis2k3 said:
Thanks for the advice. I did check my SD storage and it said that I only had 1.16GBs left. So I thought that this could be true I suppose. So I switched to int. Storage as the install location(which I have 9.67GBs available on) and its causing my phone to lock up and freeze. Happened right at the part "extracting Rom please wait..." Weird...
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Remember to disable logging in Superuser. That also causes some major issues. Just open superuser hit settings icon, and where it says logging set it to off. You should have much better luck that way
Cool, I will try that. I've uninstalled and reinstalled multiple times, with no luck. I'm interested though. What do you guys have setup in settings?
Sent from my ADR6425LVW using Tapatalk 2
live2die said:
boot manager doesnt surport rexound officially,maybe thats the final answer. i encounterred the same issue too,but when i reinstall the app,it works just fine.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
The Rezound is supported by bootmanager.
I've never been able to get boot manager to work correctly since I've started using it back on my dinc2. Had issues installing some roms on that phone too. Which is why I think my problem may be the settings I am using. Is there specific settings I need to use for the rezound?
EDIT: After I changed the settings SU I tried again at work and it froze still and even rebooted during the install.
Sent from my ADR6425LVW using Tapatalk 2
Ok, so I finally got cm9 roms to install correctly and now when I try to boot to them it just shows the splash screen for a couple seconds and my display turns off and it never boots. I've tried with kang and paranoid with the same results. I've tried going into recovery and manually flashing the update zip for rom 1, didnt work. Can't think of what could be the problem....
Sent from a galaxy far..far..away....
anubis2k3 said:
Ok, so I finally got cm9 roms to install correctly and now when I try to boot to them it just shows the splash screen for a couple seconds and my display turns off and it never boots. I've tried with kang and paranoid with the same results. I've tried going into recovery and manually flashing the update zip for rom 1, didnt work. Can't think of what could be the problem....
Sent from a galaxy far..far..away....
Click to expand...
Click to collapse
Doesnt look like anyone has asked you this, but are you S-Off?? You need to be S-off for this to work. Also make sure when installing you wipe system/data/cache. You should be able to use the ext.4/2 either one will work. I use the ext.4 since it installs faster....alot faster.
dalvear88 said:
Doesnt look like anyone has asked you this, but are you S-Off?? You need to be S-off for this to work. Also make sure when installing you wipe system/data/cache. You should be able to use the ext.4/2 either one will work. I use the ext.4 since it installs faster....alot faster.
Click to expand...
Click to collapse
He can be HTC unlocked and s-on it will still work bootmanager still hasn't updated since the rezound got s-off... His problem sound like the boot.img does not have the right kernel installed or something
Sent from my Dinc... I mean Rezound
yojoe600 said:
He can be HTC unlocked and s-on it will still work bootmanager still hasn't updated since the rezound got s-off... His problem sound like the boot.img does not have the right kernel installed or something
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
only mentioning that because in the instructions for the app. If he doesnt have to be S-Off then thats strange. Only thing i could suggest after that would be redownload ROM and check MD5
dalvear88 said:
only mentioning that because in the instructions for the app. If he doesnt have to be S-Off then thats strange. Only thing i could suggest after that would be redownload ROM and check MD5
Click to expand...
Click to collapse
i understand... he could probably do a dirty install of the same rom over top and make sure it has a boot.img in the zip that is not in any of the folders
Hey guys...
I use boot manager to boot between ROMs. My main ROM is Gingeritis3D v1.2 and I was going to set my other ROM as the new AOKP ICS ROM, but when I go to install it, I am prompted to select a boot.img to install from.
Which one should I choose?
My options are boot.img and _MACOSX/._boot.img
Sent from my ADR6400L using xda premium
I would think that it would be boot.img but I don't use boot manager so I don't know anything about it.
Sent from my ADR6400L using Tapatalk 2
That's what I was thinking... but Idk.
Oh well, I'm going for it anyways. Haha.
Sent from my ADR6400L using xda premium
So I chose boot.img anyways and it worked just fine.
Flashed right into the AOKP ROM and it ran perfectly.
Scared me once I got into the ROM because boot manager didn't want to work since I wasn't signed into my Gmail.. and I couldn't find out how to sign in. And without signing in and getting the app to work, I couldn't get back to my main ROM.
And then my brain started working for once.
Anyways, on a side note, if anyone chooses to dual boot to the AOKP ROM....
Once you've booted into the AOKP ROM from boot manager, you cannot sign into Gmail account... or at least I couldn't. This kept the boot manager app from being accessible.
So if this happens to you and you also cannot find a way to sign into your Gmail account, don't panic and don't bother wasting time wiping or restoring a nandroid.
Just reboot into recovery, install zip from sd card, choose zip from sd card, navigate down the the boot manager folder, navigate to phone ROM, select update.zip, and flash it. Press the back soft key button and then reboot system now.
You should then be back on your main ROM.
I want to try this rom normally but it keeps rebooting. Im not using boot manager. Any ideas?
crackedvenom2 said:
I want to try this rom normally but it keeps rebooting. Im not using boot manager. Any ideas?
Click to expand...
Click to collapse
If you're not using 4ext to flash then try that.
Sent from my Thunderbolt using Tapatalk 2
I have a MoPho with unlocked bootloader running 2.3.4 and everytime I try to flash back to my saved stock backup from any custom rom I keep getting an "error while flashing boot image" I tried to do an advanced restore and picked the files one at a time but I keep getting the same result. Can someone please help, thank you in advance...
Sent from my MB855 using xda app-developers app
Are you restoring using the same utility you did the nandroid backup with? Joker recovery vs twrp vs cwm recovery
Sent from my MB855 using Tapatalk 2
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Are you using a working recovery? Jokers? Twrp? Photon3? Or the ROM manager one? ROM manager version does not work.
Sent from my MB853 using XDA
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
as mentioned previously the ROM Manager one DOES NOT WORK. 5.0.2.8 DOES NOT WORK! you NEED to user Jokers, TWRP or the 5.0.2.7-photon3 recoveries ONLY. you can find the working recoveries on my site. choose which one suits you best! don't use Jokers V4 because it won't flash google apps properly.
http://www.motosunfire.com/clockworkmod-recovery/
Ok thanks a lot, I will try the two you just recommended...
Sent from my MB855 using xda app-developers app
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
na7q said:
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
Click to expand...
Click to collapse
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Stray2thaB said:
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
Click to expand...
Click to collapse
Stray2thaB said:
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Click to expand...
Click to collapse
hmmm... CDMA user? or GSM? i remember that bug being around in the very early builds of CM7. are you on the latest nightly or stable release?
i might also recommend changing some build prop info (which could be causing this?) to make sure it tells the radio to operate in the correct mode. gsm or cdma. if you look for ro.telophony.default_network=? the ? should be a 4 for CDMA or a 7 for GSM. change to your liking. then reboot. this was an issue in CM9 for the longest time and this is how it was resolved. it's possible it could be the same for CM7.
another option is to of course start over. wipe the cache,data,system partitions, possibly even twice. flash cm7. twice to be safe. then gapps. twice to be safe. then give it another shot.
other than that it might be a bad download or a bad build. so try another if it doesn't work. hope this helps you!
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Stray2thaB said:
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
there will never be any officials releases unless somehow Motorola decides they want to give us drivers/source for ICS or JB. which is never. unless we get a leak.