• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Help! Serious Problem with Desire

Hi Guys,

Yesterday I was having trouble with "E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)" error, I managed to solve this problem but ever since my calls keep dropping, oddly enough the call seems to stay connected the other end.

When I make a call it connects then drops looking at the screen for a few moments the signal has completely gone but then mysteriously comes back almost immediately, if I call my partners phone the call drops after 10-20 seconds, and if I call again the first call to her stays connected at her end, if she picks up the second call the other call goes on hold and the second call drops exactly the same.

Following the cant mount error I flashed back to Reflex 2.0.1, I didnt have the problem earlier with Reflex 2.0.0 which I did a nand with even restoring this the problem remains, I've tried insertcoin rom problems remains and also tried apps2d+ rom instead of cm7 and still problem remains.

Can anyone help?

Should flash a rooted stock froyo rom and start s-off again?
 
Ok I have managed to flash an old backup, miui rom I had, and made a phone call for over 2min without the call droppong at all, can anyone help explain why I cannot use any other rom without calls dropping?
 
Odd. dev/block/mmcblk0p1 is your FAT 32 partition of your SD card. mmcblk0 is the SD card as a whole. Why that would drop calls is beyond me.
 
usb bricks have a tendency to bork radio from what ive learned in the recent threads SU
i didnt realise this before but each one of them reported their signal being fixed when usb brick was fixed

this is wierd tho as restoring miui fixed it???

not being funny but it could all be coincidence and you were actually having network problems with your provider

could of been an VLR/HLR problem or GGSN.

flash redux back and see if its working again. if it is then it was a network issue right?
 
usb bricks have a tendency to bork radio from what ive learned in the recent threads SU
i didnt realise this before but each one of them reported their signal being fixed when usb brick was fixed

this is wierd tho as restoring miui fixed it???

not being funny but it could all be coincidence and you were actually having network problems with your provider

could of been an VLR/HLR problem or GGSN.

flash redux back and see if its working again. if it is then it was a network issue right?

Your not gonna believe this but when I reflashed reflex s 2.0.1 I tried a few things, first I made a call to tmobile automated service and left it on speaker, it did not disconnect I left it on for about 3mins, then I tried it without the speaker on and it stayed connected and I have tried a few times but when I put the phone to my ear it disconnects everytime,

So for some reason maybe usb brick, it is disconnecting when I put the phone to my ear, I wll persevere with the usb thing and report back if I get that fixed
 
so it disconnects when the screen turns off. Did you restore any apps or settings?

hmm that is odd, does the device get picked up via usb when booted?

if so then its not a usb brick i just thought it could be related

thats wierd tho, check what SU says
 
usb bricks have a tendency to bork radio from what ive learned in the recent threads SU
i didnt realise this before but each one of them reported their signal being fixed when usb brick was fixed

this is wierd tho as restoring miui fixed it???

not being funny but it could all be coincidence and you were actually having network problems with your provider

could of been an VLR/HLR problem or GGSN.

flash redux back and see if its working again. if it is then it was a network issue right?

Thanks Rasta, seems you were right all the problems were immediately solved without the need to reflash just by simply fixing the usb brick, many thanks to you oh great one.
 
Back
Top Bottom