hi all. after flashing the new radio, and then both dasbamf 1.6 and then virusrom, with full wipes in between, my volume rocker button has no effect on the in call volume settings. it's maxed out and i'm going deaf from talking on my phone.
yes i do use my phone to talk to people.....lol
can anyone here help me out? thanks.
If you flash the rom from scratch it should eliminate the volume rocker. It sounds like you might have flashed a back up. Then try flashing the volume rocker again and see if that corrects the issue. I would also wipe everything three times.
Sent from Verizon in Phoenix, AZ, running a rooted Thunderbolt, with Das BAMF Remix 1.6.2
I think u misunderstood. My volume buttons on the outside of the phone dont work after flashing either of these 2 roms.
cmegalodon said:
I think u misunderstood. My volume buttons on the outside of the phone dont work after flashing either of these 2 roms.
Click to expand...
Click to collapse
Wow. That sucks. You'll have to use adb if the volume buttons are unresponsive. Use the command adb reboot bootloader when you have the rooted stock ruu at the root of your sd card. This should fix everything not to mention start you back at scratch.
raider3bravo said:
Wow. That sucks. You'll have to use adb if the volume buttons are unresponsive. Use the command adb reboot bootloader when you have the rooted stock ruu at the root of your sd card. This should fix everything not to mention start you back at scratch.
Click to expand...
Click to collapse
Noooooooooooooo!!!!!!!!!!!!!!!!!!!!!
It's not that bad. Lol. How did you root your phone? If you used the nine step process then you should already have adb up and running.
I rooted via adb. Cut n paste.. i guess ill try wiping everything manually then reflash the rom.
cmegalodon said:
I rooted via adb. Cut n paste.. i guess ill try wiping everything manually then reflash the rom.
Click to expand...
Click to collapse
Just remember you're doing an Hboot not CWM. So you'll want to find the unsigned stock ruu aka PGIMG05.zip file and put that on the root of your SD card. Then run the adb command. Make sure you don't have another PGIMG05 file on your root or you could end up unrooting your phone. Good luck.
**I too flashed from remix to virus and didn't experience this problem. In fact, when I flashed to virus, I didn't have the volume rocker, so I added it and still didn't have any problems. It could have been an unclean wipe which is why your volume rocker stopped working.
volume
I have used BAMF since day one of rooting. I have had the volume since I had the phone =( I updated to the 1.6.3 today... but didnt wipe anything.. just flashed it.. didnt wanna have to reload everything I have on my phone... is there a way I can fix the volume without wiping?
volume
I flashed a new kernal this morning and it fixed my volume problem!! I flashed 4.4.6 with no call recorder!!
After much searching, i found that the issue is with the call recorder. I removed it and viola! I have volume control back. Oh well.....no recorded conversations to get me into trouble. Lol.
cmegalodon said:
After much searching, i found that the issue is with the call recorder. I removed it and viola! I have volume control back. Oh well.....no recorded conversations to get me into trouble. Lol.
Click to expand...
Click to collapse
My issue was a little different than yours, but removing the call recorder fixed it! Thanks for the research.
Related
Phone is rooted and I believe Ive got a lag fix installed.
No idea what I need to do - did a quick looksie through the JI6 thread and I didnt see anything in particular about the update ****ign up anyones phone.
EDIT: The update is called JI6 right? Whatever I got automatically from tmobile is what messed it up.
I'm having the same problem. I'm thinking its because I had the lag fix before this.
If you have the voodoo lagfix then you may have to use odin to fix things. See the instructions on the first post of the thread for Simbionix for that.
With other lagfixes you may just be able to wipe the phone. Can you still access recovery?
Sent from my SGH-T959 using XDA App
I can access recovery. I really didnt want to lose things like contacts saved on my phone even though I dont give a piss about anything else. I dont think the contacts copied into SIM so I may be screwed on that.
If you had your Gmail synced, all the contacts should be on your gmail account, and it will not be wiped
Tengis said:
I can access recovery. I really didnt want to lose things like contacts saved on my phone even though I dont give a piss about anything else. I dont think the contacts copied into SIM so I may be screwed on that.
Click to expand...
Click to collapse
Your contacts should be saved on your google account unless you disabled that.
Sent from my SGH-T959 using XDA App
Sweet. I dont use Google regularly so I didnt even think about the contacts syncing to it.
What is my next step? What should I do? The ODIN thing?
It's a google phone, but u denied to use google service frequently, then you deserve the punishment
Just kidding. I think Odin is the only solution here. And don't forget to use google service after getting your phone back from death =D
Sent from my SGH-T959 using XDA App
Just flash the ji6 kernel . Should boot right up
Sent from my SGH-T959 using Tapatalk
Hi,
The same thing happened to me.
I pushed bionix 1.6 to sdcard with adb.
Then flashed it with clockwork.
I am up again.
What a tmobile nighmare.
to disable vodoo lagfix
A quick and easy way to disable voodoo lagfix, is to just create a file or a folder inside of the voodoo folder called "disable lagfix". Worked for me, hopefully this helps.
same thing happened to me. The update was waiting for me when i woke up, so i hit the damn button without thinking about it (i had one eye open!!).. now i have a nice "vibrant" screen.. oi. Simply wiping the phone does nothing, so Im going to try the 2.2 to 2.1 fix.. here goes nuthin..
Same thing here. I had a lag fix (not the voodoo one) and a GPS fix. Not sure which solution to go with. I'll wait for some more replies with simple and easy fixes to appear.
EDIT: I was able to reboot holding power and volume buttons and got it to ClockWork recovery. I guess my next step at this menu would be to "install zip from sdcard" but how would I go about getting the Bionix_6_stock.zip file onto my SD card?
you'll be fine
take out battery and hold power up/down buttonswithe buttons pressed insert battery. you should see Vibrant logo once continue to hold once it goes blank then let go of all exept down button you should be in stock recovery now if you had clockwork recovery press reinstall packages you should now by in clockwork recovery if so flash again or flash some thing else hopefully a nandroid back up... good luck but you problem does not seem that serious keep at you'll be fine
mgiusto said:
Same thing here. I had a lag fix (not the voodoo one) and a GPS fix. Not sure which solution to go with. I'll wait for some more replies with simple and easy fixes to appear.
EDIT: I was able to reboot holding power and volume buttons and got it to ClockWork recovery. I guess my next step at this menu would be to "install zip from sdcard" but how would I go about getting the Bionix_6_stock.zip file onto my SD card?
Click to expand...
Click to collapse
Do you have adb setup? If so, put the bionix ROM in the tools folder of your SDK & type:
adb push *file directory/file name* /sdcard
GL, please update.
All~G1 said:
Do you have adb setup? If so, put the bionix ROM in the tools folder of your SDK & type:
adb push *file directory/file name* /sdcard
GL, please update.
Click to expand...
Click to collapse
Hmmm I think I remember about this other way to boot up where you can push stuff to the phone. How do I do that again? I have only been able to get to the Clockwork Recovery screen and need to get the Bionix zip file from my PC to the Vibrant using ADB which yes I have and it did work a while ago. I just forgot how to boot in that mode. Thanks!
I'm stuck as well. One small difference. I DO NOT have a lag fix installed. I uninstalled the One Click Lag Fix yesterday in preparation for the update.
Well, let me rephrase. The App is installed on the phone but the fix is not applied.
Any thoughts?
Side note. My screen has some how gotten scratched recently and I'm curious if this is a possible way to get a new screen (and phone) from Tmobile. The phone is rooted and I have a GPS fix applied but that's it.
EDIT: I wanted to add, while booting, the Vibrant screen obviously comes up but after a few seconds, the TMobile jingle STARTS to play. It quickly goes quiet and then continues to sit at the Vibrant screen.
Long time lurker, first time posting.
Stuck as well, I am rooted but stock otherwise. Only items installed are:
Vibrant-JI2-GPS.zip
signed-mobileap.vibrant.zip
Any help is appreciated
EDIT:Was able to push Bionix 1.6 through ADB and Flash with Clockwork Recovery. Back Up and Going!
mdobles said:
Long time lurker, first time posting.
Stuck as well, I am rooted but stock otherwise. Only items installed are:
Vibrant-JI2-GPS.zip
signed-mobileap.vibrant.zip
Any help is appreciated
Click to expand...
Click to collapse
I'm sort of in the same boat. Rooted, but haven't installed any of the lag fixes or gps fixes. I don't have clockwork installed. Is there any way for me to download the OTA to my SD card and try flashing it that way?
This sucks
FYI. I had the same problems as the original OP, getting stuck at the boot screen after the update, due to having lag fix enabled. I finally got the true stock 2.1 firmware installed via ODIN. I've called T-Mobile requesting they push the update again and was told to do the following to send a message to google to have them push the update to my phone. It's been 30 minutes and nothing yet but I'm crossing my fingers. For the guys who haven't received the OTA update yet give this a shot.
Dial *#*#2432546#*#*6
One you complete the sequence all the numbers and characters should disappear leaving your dialer blank. Then you just sit and wait for the message to update your firmware. Hope this works!
I looked around for a while and didn't see this, so help if you can!!!
Ok, I followed the instructions to return to factory by placing the PG05IMG on the SD, because I had tried to root a couple of times and it kept messing up, and I was seeing some bad side effects.
Everything went through fine, and I setup the phone, etc. Then I turned it off, and it will NOT start up normally. It will only start with the volume down + power startup method into HBOOT. What do I need to do?
I will say I did delete the pg05IMG file from the SD after the phone went back to factory state, in case I have to trade in the phone or something, could that be it?
I am sure you did this, but did u pull the battery ans let it air for a minute?
Sent from my ADR6400L using XDA App
i tried that, but no luck
Thanks for the idea. I have messed with it some, and it won't power on with just the power button. With power and volume down it will go into hboot,and with pier and volume up,it will boot normally...
Sounds like you are back to stock... have you tried a factory reset?
yeah, i am back stock, which is what i wanted...
For some reason I couldn't get root to take, so I am going to try down the line...
And yeah, after I returned to stock I did a factory reset, but no luck. Might be worth trying again. Any other ideas?
Bad download of the software? Try redownloading it and flashing the new file.
still not working
I did ANOTHER factory reset, feels like about my 7th time setting up the phone. Geez. Still no luck. I verified the file download when I went back to stock, with he checksums, so I don't think its that. I don't fully understand hboot, is that something on the phone to start with, or something you have to add to make it accessible? This is killing me....
anyone?
Still don't have a resolution on this one, if anyone has any ideas...
miked777 said:
Still don't have a resolution on this one, if anyone has any ideas...
Click to expand...
Click to collapse
don't try flashing a stock pg05img.zip(remove it from sdcard)....download the stock RUU(see Dev forums) and plug your phone in and run that. Then reroot.
OK!~
Try this...(even though it may sound bad)
You need to do the clear storage option then re-install the update.
I just did this on my incredible because i accidentally installed an older ROM and it would do the same thing as mentioned in your post...
But now my phone is working again
Good Luck !
miked777 said:
I looked around for a while and didn't see this, so help if you can!!!
Ok, I followed the instructions to return to factory by placing the PG05IMG on the SD, because I had tried to root a couple of times and it kept messing up, and I was seeing some bad side effects.
Everything went through fine, and I setup the phone, etc. Then I turned it off, and it will NOT start up normally. It will only start with the volume down + power startup method into HBOOT. What do I need to do?
I will say I did delete the pg05IMG file from the SD after the phone went back to factory state, in case I have to trade in the phone or something, could that be it?
Click to expand...
Click to collapse
A lot of instructions say, "if the md5 does not match do not reboot, stop delete it, redownload it, check md5 and start over." Always read it through twice before you perform. Like a carpenter...measure twice cut once. I am sure one of your md5 did not match and you triggered the nasty side effect. Everyone should download md5 checker from market....and use it.
If I helped you in any way please use the thank you button
I've searched high and low for someone having a similar problem to no avail, so here it goes:
I previously rooted my phone using the one touch root method, and flashed kaosfroyo. I ran that ROM for a good while until I started having issues receiving text messages. I took my phone back to stock to see if that would fix the issue, which it did, but now I can't boot back into recovery to try to re-root. The issue I'm having is that when I try to boot into recovery using either the Vol up+end method or going through the hboot menu, it flashes the Androids on skateboards splash screen and the screen then goes black. I have to pull the battery and restart for the phone to do anything after that. Anyone have any ideas? Thanks in advance for the help!
*I do apologize if this has been covered before, but I've been looking for it for a few hours now and have not found it.*
Flashing back to stock unroots you which means you no longer have a custom recovery. Just download the 1 Click Root apk again, install, and run it. After it has worked it's magic and your phone has rebooted, you will have access to amon-ra recovery and can flash a new ROM.
MongooseHelix said:
Flashing back to stock unroots you which means you no longer have a custom recovery. Just download the 1 Click Root apk again, install, and run it. After it has worked it's magic and your phone has rebooted, you will have access to amon-ra recovery and can flash a new ROM.
Click to expand...
Click to collapse
I actually have tried that, and it doesn't work either. I forgot to mention that, sorry. I run the root, power down, but when I try to boot into recovery it does the same thing.
twiztedxtreme said:
I actually have tried that, and it doesn't work either. I forgot to mention that, sorry. I run the root, power down, but when I try to boot into recovery it does the same thing.
Click to expand...
Click to collapse
If you haven't already, maybe try the rooting method on the wiki:
How to Root Eris - XDA Wiki
Instead of the Recovery.img file they tell you to download, I'd suggest using the "1.7.1" recovery by scary alien which is a modified version of amon-ra. It allows the use of other physical buttons to navigate so if your trackball dies, you are still able to use recovery.
Amon_RA 1.6.2 Custom Recovery
If that doesn't work, I'd try following bftb0's instructions in this thread.
twiztedxtreme said:
I actually have tried that, and it doesn't work either. I forgot to mention that, sorry. I run the root, power down, but when I try to boot into recovery it does the same thing.
Click to expand...
Click to collapse
With 1-click root, you need to run the app, power down, power back up (like you wanted to make another phone call) - then power down and power up to recovery. From what you describe, you missed that intermediate power-up step.
doogald said:
With 1-click root, you need to run the app, power down, power back up (like you wanted to make another phone call) - then power down and power up to recovery. From what you describe, you missed that intermediate power-up step.
Click to expand...
Click to collapse
Yeah, that's what it sounds like to me too. The first few times I rooted my phone I missed that step too and thought I'd bricked the phone, only to realize I needed to boot back up fully and then go into the recovery.
Hello,
I too faced same problem in the initials of rooting. what i did is rooted again, but super one click doest work.
So i rooted with,
unrevoked.com/recovery/
It worked for me.
and for switching recovery, i think best way is via droid explorer. downlaod droid explorer and then download amon recovery, and flash it.
I have successfully rooted my HTC aria running android 2.2 with sense interface. Now i want to install custom ROMs. I have installed ROM manager and tried installing CM7 but i cannot boot into Clockwork recovery mode. I have tried installing clockwork several times but it doesn't work. I have checked out few other forums but none of them seem specific to my case. Please help!
Do yo phone have a fast boot feature if so uncheck it then reinstall Rom manager then try to reboot into recovery if this help hit the thanx button #)
HTC Glacier - Virtuous Unity 2.39/Kernel V9 Unity Overclocked/Beats Audio + Volume Boost App = Omg Loud
sanimagus said:
I have successfully rooted my HTC aria running android 2.2 with sense interface. Now i want to install custom ROMs. I have installed ROM manager and tried installing CM7 but i cannot boot into Clockwork recovery mode. I have tried installing clockwork several times but it doesn't work. I have checked out few other forums but none of them seem specific to my case. Please help!
Click to expand...
Click to collapse
Did you use Revolutionary on the device? Did it acknowledge that it was successful in flashing custom recovery to your device?
The proper way to reach CWM is to turn the device completely off, then hold down the volume down button and press the power button. From that screen you should select "Recovery" by using volume up/down buttons to move and power button to select. Don't use ROM Manager to install or get to Clockworkmod.
i do not have a fast boot option, thanks for replying though.
If you dont see fastboot.... Then you are not rooted. Try the process again.
You should be able to power off the phone, then hold the down volume button while powering on the phone.
Then you should see fastboot and recovery. If you don't see either, then the root process was unsuccessful.
tomtommy306 said:
If you dont see fastboot.... Then you are not rooted. Try the process again.
You should be able to power off the phone, then hold the down volume button while powering on the phone.
Then you should see fastboot and recovery. If you don't see either, then the root process was unsuccessful.
Click to expand...
Click to collapse
What are you talking about? The HBOOT screen will always list both of those options.
issue resolved. Thanks
Issue resolved. Thanks!!
drumist said:
What are you talking about? The HBOOT screen will always list both of those options.
Click to expand...
Click to collapse
Well... It looks like what I said worked.
This could have been fixed in one simple post.
Instead, the guy just got the usual runaround.
tomtommy306 said:
Well... It looks like what I said worked.
This could have been fixed in one simple post.
Instead, the guy just got the usual runaround.
Click to expand...
Click to collapse
tomtommy306 said:
If you dont see fastboot.... Then you are not rooted. Try the process again.
You should be able to power off the phone, then hold the down volume button while powering on the phone.
Then you should see fastboot and recovery. If you don't see either, then the root process was unsuccessful.
Click to expand...
Click to collapse
I'm not trying to start anything here but, I don't see how this could have helped. Fastboot and HBOOT are always in place no matter if you're rooted or not.
DOUCHE!
I havent seen a stock hboot in nearly a year. But no one here asked him to boot into it, hence "how it helped" stop trolling MOD EDIT: REMOVED OFFENSIVE
I suggest that you re-read this thread. I told him how to get to HBOOT before you even posted, yet you attack me for giving him the run around?
sure did.
Not really... If I "attacked" you, then you would be in pain.
Surely you aren't taking this **** THAT seriously.
Let it go, and move on now. I will as well.
It's FRIDAY! Go party!
.
Keep it on topic and with respect, next time some bans can be given
I pushed local.prop to my rooted .62 XM to update to ICS and root as instructed by puppet13h in this post - http://forum.xda-developers.com/showthread.php?t=1688980
After pushing local.prop i had problems affecting my Mini, which i posted here -
http://forum.xda-developers.com/showpost.php?p=27423564&postcount=99
It could get fixed by deleting local.prop as told by him.
The ICS update still has not come to PCC/SUS and i used my phone often, restarted often till now after pushing local.prop.
Now today after deleting local.prop since pushing local.prop 3-4 days ago, my phone has no sound only vibration. I restarted and factory resetted many times but the sound is not coming back.
After somany failures, i flashed/downgraded to .42 from .62. Still the phone has no sound after downgrading.
No sound when call comes, when music plays, loud speaker too not working.
I think this local.prop has killed by Mini's sound and speaker.
What will i do now?.
I bought my Mini last month and flashed 3 or 4 times for getting root..
Please will someone help.. ?..
even i had a problem using that script ..
but i updated to ics via flashtool..
now everything is working fine
sidharth.gtm said:
even i had a problem using that script ..
but i updated to ics via flashtool..
now everything is working fine
Click to expand...
Click to collapse
but there is no sound even flashing stock 62.., only vibration is working.
Also when i call, i can hear sound from call speaker, but the back loud speaker is not working..
I am afraid that the sound is gone for ever.....
Update: Opened camera. The usual beep sound(.i.e from speaker) comes before capturing pic. Played a song. Yes, sound comes from speakers. But when the screen locked, music stopped and sound is gone.
Opened camera again. The beep sound is gone too and am unlucky again. No ringtone volume sound, no music, i.e. speaker stopped working.
Cant understand why the problem is still there after flashing new firmware.
▐▬SMULTRON▬▌ said:
but there is no sound even flashing stock 62.., only vibration is working.
Also when i call, i can hear sound from call speaker, but the back loud speaker is not working..
I am afraid that the sound is gone for ever.....
Update: Opened camera. The usual beep sound(.i.e from speaker) comes before capturing pic. Played a song. Yes, sound comes from speakers. But when the screen locked, music stopped and sound is gone.
Opened camera again. The beep sound is gone too and am unlucky again. No ringtone volume sound, no music, i.e. speaker stopped working.
Cant understand why the problem is still there after flashing new firmware.
Click to expand...
Click to collapse
do u wipe data n cache while flashing rom?? if not then try to flash rom with wiping data n cache. also try flashing ICS ftf file as sidhartha did, which is available in development forum!! do wipe cache n data when u flashing i think it will surely help.....
sravan242 said:
do u wipe data n cache while flashing rom?? if not then try to flash rom with wiping data n cache. also try flashing ICS ftf file as sidhartha did, which is available in development forum!! do wipe cache n data when u flashing i think it will surely help.....
Click to expand...
Click to collapse
yes, wipe data n cache is always checked in flashtool...
i flashed 42, no sound.
then flashed stock 62, no sound.
what will happen if i write ro.kernel.qemu=0?.
I afraid there is sound problem with your phone (hardware,not software)
▐▬SMULTRON▬▌ said:
what will happen if i write ro.kernel.qemu=0?.
Click to expand...
Click to collapse
try flashing ICS it will change total kernel... may be changing kernel may help!!
UchihaDareNial said:
I afraid there is sound problem with your phone (hardware,not software)
Click to expand...
Click to collapse
had no problem before creating local.prop.
how will this script create a hardware problem?..
lets try and post what you are getting.
push/create /data/local.prop with ro.kernel.qemu=1 on rooted .42 or .62, restart, lock screen and try to unlock...
Also tell about the sound and vibration..
sravan242 said:
try flashing ICS it will change total kernel... may be changing kernel may help!!
Click to expand...
Click to collapse
will try this now...
While flashing perform a fully clean install. Clean everything (before starrting remove SD card and SIM card) using flashtool while flashing the ROM.
Report back.
Thanks,
Rick
Update: Seems like you did wipe. Remove SD Card and try to use camera. Activatre touch sonds and try taking a screenshot and see if sound is there.
Thanks,
Rick
Sent from my SK17i using XDA
I don't really understand people who don't care about continously flashing 0.42 and 0.62 ROMs but will wait for ICS update to be available on PC Companion...
That method is supposed to be used before flashing ICS. What was the sense of pushing the file if you knew you wouldn't have upgraded yet?
Anyway, let us know if flashing ICS solved the problem
Pushed local.prop and switched off. Removed sim, sdcard and flashed Generic_World_(1249-8388 R2I) ICS with wipe data unchecked. Upon start i pressed volume up button to test sound beep is there. I heard a beep sound once and upon pressing the up button again the sound is no more heard. No sound after reducing or increasing volume.
Very laggy user interface.
Inserted sim and sdcard.
Opened camera and complete darkness (will have to say camera died or is not working). Tried to take screenshot by power+vol down buttons. Showing "couldn't capture screenshot. Storage maybe"...(cant see rest in notifications. tried to rotate. it is not rotating).
My sdcard has 7.3GB space left. Opened music player and played a song. Song plays, no sound.. Sound is gone again..
I must say ICS is lagging fully on Xperia Mini now...316MB free phone memory, 220MB RAM free, but big lagginess.
Maybe a wipe could make it lag less.
WTF is this?. A local.prop file killed my phone's speaker?. Speaker is not working on ICS too...
Why are you pushing local-prop.cmd? Do not push it. Delete it. Factory reset your phone. And then flash the .62 or ICS ROM, wiping everything.
Thanks,
Rick
Anyways, according to the tutorial, you are supposed to run the 2nd cmd file soon after the update is over.
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Why are you pushing local-prop.cmd? Do not push it. Delete it. Factory reset your phone. And then flash the .62 or ICS ROM, wiping everything.
Thanks,
Rick
Anyways, according to the tutorial, you are supposed to run the 2nd cmd file soon after the update is over.
Sent from my SK17i using XDA
Click to expand...
Click to collapse
If i want rooted ICS, then when will i push local.prop?. You told in tutorial to push local.prop before updating ICS and after push root files.
Pushed root files and restarted. For surprise Lag is now low...
Update:
Camera and screenshot working after restart...........
Now am seeing super user.... But my speaker is gone for ever.....i am very sad..
▐▬SMULTRON▬▌ said:
If i want rooted ICS, then when will i push local.prop?. You told in tutorial to push local.prop before updating ICS and after push root files.
Click to expand...
Click to collapse
He's just saying that you should try to flash a clean, non rooted ICS to check if everything goes fine.
▐▬SMULTRON▬▌ said:
If i want rooted ICS, then when will i push local.prop?.
Click to expand...
Click to collapse
Very bad Smiltron. You did not read properly before doing the things.
There are two cmd files in puppet's zip.
Read my tutorial all over again. I had mentioned "after executing the first cmd of puppet's zip, go for updating the phone right away". I said "DO NOT ToUCH your PhOne after this and flash the ICS ROM".
After the flashing of ICS ROM is over run the second cmd file of puppet's thread right away soon after the phone boots. I had mentioned. You did not read that too.
Read it now. Execute the 2nd cmd now and see if something happens.
Thanks,
Rick
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Very bad Smiltron. You did not read properly before doing the things.
There are two cmd files in puppet's zip.
Read my tutorial all over again. I had mentioned "after executing the first cmd of puppet's zip, go for updating the phone right away". I said "DO NOT ToUCH your PhOne after this and flash the ICS ROM".
After the flashing of ICS ROM is over run the second cmd file of puppet's thread right away soon after the phone boots. I had mentioned. You did not read that too.
Read it now. Execute the 2nd cmd now and see if something happens.
Thanks,
Rick
Sent from my SK17i using XDA
Click to expand...
Click to collapse
"DO NOT ToUCH your PhOne after this and flash the ICS ROM". it was not clear to me whether to update ics suddenly after creating local.prop or when ics arrives. I used, restarted the mobile for some days after creating local.prop.
I came to know about the screen lock problem and sound problem then.
"after executing the first cmd of puppet's zip, go for updating the phone right away" - i did this now.
after creating local.prop, i switched off and flashed and then pushed root files. Now i am having super user rights. What is wrong there?.
see my post above
Dragonclaw, what will i do now with my speaker?.. Should i do a clean non rooted update from 62?..
▐▬SMULTRON▬▌ said:
"DO NOT ToUCH your PhOne after this and flash the ICS ROM". it was not clear to me whether to update ics suddenly after creating local.prop or when ics arrives. I used, restarted the mobile for some days after creating local.prop.
I came to know about the screen lock problem and sound problem then.
"after executing the first cmd of puppet's zip, go for updating the phone right away" - i did this now.
after creating local.prop, i switched off and flashed and then pushed root files. Now i am having super user rights. What is wrong there?.
see my post above
Dragonclaw, what will i do now with my speaker?..
Click to expand...
Click to collapse
Right. You edited your post now. Good. You did the rooting process correctly. The whole thing. Good.
Now. Coming to the sound problem. You need audio of your phone back. And you do not care about root. You will owrry about root once sound is back.
Saying that, I will tell you what to do now.
Take out the SD Card of your phone and the SIM card too. And then using flashtool, flash the ICS ROM, clearing everything. See if things are fixed or not. And report back.
Thanks,
Rick
After the update is over do not insert the SIM or the SD Card. See if sound is there for the other components. Like touch sounds. Unlock sounds. Etc etc.
Sent from my SK17i using XDA
DragonClawsAreSharp said:
Right. You edited your post now. Good. You did the rooting process correctly. The whole thing. Good.
Now. Coming to the sound problem. You need audio of your phone back. And you do not care about root. You will owrry about root once sound is back.
Saying that, I will tell you what to do now.
Take out the SD Card of your phone and the SIM card too. And then using flashtool, flash the ICS ROM, clearing everything. See if things are fixed or not. And report back.
Thanks,
Rick
After the update is over do not insert the SIM or the SD Card. See if sound is there for the other components. Like touch sounds. Unlock sounds. Etc etc.
Sent from my SK17i using XDA
Click to expand...
Click to collapse
yep.... i believe you....
should i choose MTP or MSC?.
And then using flashtool, flash the ICS ROM, clearing everything.
Click to expand...
Click to collapse
clearing everything means should i check or uncheck wipe data, wipe cache, wipe apps log?..