Once upon a time I did a very stupid thing: after flashing repartition and installing ROM I restored using a CWM backup made before repartition. The phone was soft-bricked (no recovery, no ROM, only pink screen and that's all) but I successfully made the phone work at last.
The problem starts from now on: now I can't use MTP on any ROM except stock gingerbread and Aurora-based ICS roms. When I press "Turn on USB storage" the sd dismounts and the "usb screen" hangs. Also it's ironic that in fact I have access to both internal and external storages at that moment, but the phone thinks they're dismounted. Also since that "restore" I've lost my IMEI, both bluetooth and wi-fi mac's, serial, etc.
Does anyone have an idea of why is it not working? This problem 100% occurs on some versions of MIUI (don't exactly know which, .35 and ICS based), stock .32 ROMs and CM7.2 by ezet (also .32 kernel).
Thanks in advance and sorry for my bad English.
Related
Yesterday I needed to take a picture and used my Galaxy S. for it. After that I connected my phone to my laptop USB port and got an unknown device error. Assuming it was a driver problem I re-installed them keeping the same error.
I also got telephony problems before, after some minutes calling the other side couldn't hear me anymore and I needed to put the call on wait and back to continue the call.
Both problems together made me decide to update my Darky 10.1 Extreme edition to the latest 10.2 Extreme edition. I took my sd card out and copied the darky 10.2 zip to it using my laptop. Put it back in and used Astro filemanager to copy it to the internal sd. Because I can't use the usb port this was the only way.
Rebooted to recovery and flashed 10.2. After reboot the screen stayed at the boot screen with green Darky text for half an hour without doing anything. No vibrate or anything. I did read some info about 10.2 before i downloaded it but missed the lagfix point. Tried to get into recovery and luckily that worked. Turned on the lagfix, did hear the computer voice 2 or 3 times and last time it said lagfix was enabled. Rebooted to recovery again, checked lagfix was on, also for next boot, and flashed 10.2 again. Same problem, hangs at bootscreen.
Turned lagfix off again and flashed the old 10.1 again. Same problem again, this time only bootscreen with white SG text and both button lights on. Nothing for the rest. Flashed back, after lagfix enabled, to 10.2 again without luck. Again bootscreen only.
Someone knows how to fix this? Because of the usb problem I can't use Odin. I did read somewhere now there might be a cable problem or a dirty usb connector on the phone. Checked the connector visually and can't see any dirt, I also keep it closed when not using it.It does load the battery also when connected to my laptop. At least it did when I first got the unknown device error.
1) USB Error
I am not sure you have Only installed the USB driver alone or Kies it self. Anyway, try this http://support.microsoft.com/kb/315265. Scandisk with delete currupted file on your disk drive and replace with default window file. You can reinstall your driver/Kies on your laptop after scandisk complete.
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
from.insider said:
2) First, you must come from JVP or JVQ base rom. JVO and older rom have older bootloader. What you need to do is to flash JVP or JVQ stock rom with bootloader into your phone. Then, flash over Darky 10.2 over the phone. Take note that Darky still have many problem and it is not that stable yet. I've run it over a week and decided to dump it. The rom is too big at 215MB where else others rom only 195MB. The startup is too slow, take 5-10min after reboot the phone. The initial start up takes nearly 15min after flash.
Click to expand...
Click to collapse
If your boot takes so long, you doing something wrong
First boot, yes... it takes some time. But then, the animation isn't finished yet and I'm already good to go (after media bla bla bla)
@OoZic
For darkys rom... i had the same problem.
First flash Ficetos resurection 10.2, then make shure lagfix is ON (full lagfix - check in voodoo control app) and then flash 10.2 extreme edition
For details go to
http://www.darkyrom.com/community/index.php?threads/v10-2-final-what-are-you-waiting-for.4253/
I had the problem too
Thank you for your reply from.insider
Problem is the phone can only do bootscreen and recovery. The device isn't recognized in any way. Tried it on 2 computers (laptop/PC) with different multiboots (Win7 X64 and Vista X86 on both). Maybe that is because the OS isn't loaded and can't go to MTP?
Is there a way to copy something from external SD to internal SD within recovery menu? Because that way I can copy a JVP or JVQ image to internal. Now there are only the 10.1 and 10.2 zips from Darky.
FSCK didn't find any problems btw.
Thanks again.
Problem solved, my Galaxy is unbricked and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
OoZic said:
Problem solved, my Galaxyd and working again. Very happy now
Can't post a link because of low post count but the answer is on post-87372 on Darky.com.
The USB problem also went away, but after using Titanium to put my backup back the problem was here again. something in my settings or a service is screwing something up with the mtp I think. Used Android Booster to kill some things and it works again. As soon as I know what exactly is screwing up my mtp I will let you all know.
Click to expand...
Click to collapse
Can you copy and paste the the answer and post it here man, i cant find the post your talking about and my phone has the exact same problem.
Hello members.
I just found a strange issue that I have started facing lately whenever I try to flash a custom ROM on my Defy.
Current stock ROM was 2.2.2
I rooted it and tried This ROM. After flashing I realized that the ROM is slowly slowly eating up my space on my sd card. I checked my sd and it showed an ANDROID folder with all app backed up.
I tried playing with the Install location in Cynogenmod settings but still no help.
Tried Internal, Auto , External options but still nothing
Then I changed the ROM to 2.3.7 posted by Quarx hoping it would solve my issue but I had same issue again.
Please tell me what do I do ?
I want to use custom ROMs real bad :3
Still waiting for a response. :/
After installing DUALBOOT + RECOVERY and ICS 4.0.3/FLEXREAPER-RF1-V5.1 i am unable to turn my wifi on if anyone could please help i would be very grateful thx.
Its ok I just restored my backup and it working now dont know why it didnt work on the rom.
Same issue; tried three different ICS roms and none will allow me to turn wifi on.
Just guessing, but I would say
1. You didn't do complete wipes/formats in Recovery before installing the rom. This is usually the primary reason as sometimes code from the previous rom, is still there.
2. You installed an HC bootloader version? And not the one for ICS (although I heard the devs mostly dropped support for the HC bootloaders and ICS.
But, if you have the ICS patched V8 bootloader, I would go with option 1 And make sure the rom you are installing, is for the bootloader you currently have.
MD
Hi,
I'm trying to use Multiboot on my defy (Red lenses and GB kernel). My original rom is the latest CM9 by Quarx.
Every ROM I installed (I tried MIUI V4, XIUI and CM10, all for Defy+) I get com.android.phone FC and, I think its because of this error, i cannot find network (yes, I tried to switch my baseband to the correct one).
I tried Multiboot v0.6.1 and v0.5.1 and get the same error. I tried v0.7 with TWRP, but with this I stuck at Motorola logo.
Its the firist time i'm trying to use multiboot, I did all the steps of more than 1 tutorial and give me the same error. Anyone know something I may have missed? I'll keep trying and if I got something i'll post here.
Thanks.
did you get multiboot working?
if not, what error does it gave??
and what steps did you followed???
Basically I instaled multiboot V0.6.1, then installed Multiboot Manager Free and created an image with cache: 150Mb, data 250Mb, and system: 350Mb. Then I flashed one of the ROMs tha I mentioned.
I get it working, I can load the system, conect via wifi, navigate and etc, but after startup I get com.android.phone FC and get no signal. This happened with all the ROMs tha I've installed.
EDIT:
It seems that I could solve it, I uninstalled Multi Boot Manager and installed Vibhinna, deleted the old system image and did everything again. Now I get no errors.
Thanks.
You should also be aware that if you have a GB base ROM you should download the Defy+ versions of the ROMs you want to use in multiboot.
Hi
I have regular defy with red lens.
I have flashed some time ago new Quarx rom with custom kernel from WIUI JB rom.
After that I am unable to flash any non custom kernel builds. Even when I did a full wipe and flashed Froyo kernel with CM7, I got stucked in boot-loop. I even can't go to Stock recovery.
Now I am running recent Quarx build, but during the boot my led light is red. Also the rom is quite unstable, and crashes quite lot whitch I think is not the problem of the rom, but problem with the phone.
I also tried to use different custom kernel with no success. Also I searched this forum for some answer with the same result.
I have never flashed any SBF to my phone, I have ever used nandroid backup.
(I got my phone with Eclair, but after I got my phone from warranty repair I got Froyo)
I'll probably try to solve this problem by flashing Froyo SBF and try it again.
Thank you for help.
EDIT:
When I tried to flash WIUI JB again, strange thing happen. It flashed normally but ROM did not see internal memory and crashed after RAM got full. Also recovery had listed some errors.
Another custom kernel roms also work, but with the same problem as CM10.
I have also set correct setting for rom in bootmenu (2nd boot or 2nd init).