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

Root [Virgin Mobile] [VMOBI][RECOVERY] ClockworkMod v6.0.2.8 [6.25.2013]

FatalIll said:
What do you mean "clone", are you using software to clone it, or are you just copying data onto the sd-card?
Click to expand...

format via pc then via Recovery then copy just the file giving the error and test in recovery. if it still gives error i would think the file or the recovery is to blame not Card. if it works then copy the rest of your files over via MTP in a booted rom.

the files coding may need adjusted to match your actual mount name for the card.

E:/ Cannot Mount external_sd means that it is looking for external_sd.
some mount point names are Ext_SdCard or extSdCard for example. i would contact the Dev of the file for assistance.
 
lordmage said:
format via pc then via Recovery then copy just the file giving the error and test in recovery. if it still gives error i would think the file or the recovery is to blame not Card. if it works then copy the rest of your files over via MTP in a booted rom.

the files coding may need adjusted to match your actual mount name for the card.

E:/ Cannot Mount external_sd means that it is looking for external_sd.
some mount point names are Ext_SdCard or extSdCard for example. i would contact the Dev of the file for assistance.
Click to expand...

I'm using this recovery so I don't know what is the problem. I will format the card but to my knowledge there is not specific file giving me an issue it's the recovery not backing up to the sdcard.
 
if formatting in recovery does not address the issue/ does it happen with another sdcard.
if it does then it could be the phone it's self
if not it was the card for some reason.

i would hold off till g60 weights in thou
 
lordmage said:
if formatting in recovery does not address the issue/ does it happen with another sdcard.
if it does then it could be the phone it's self
if not it was the card for some reason.

i would hold off till g60 weights in thou
Click to expand...

I'll try my old SD card and see if has the same issue.
 
redrunner1985 said:
Had the same issue. CWM wouldn't mount or even register that my 64gb sdcard was there. Reads ny 32gb card just fine.Switched to TWRP and haven't had a problem with the 64 yet.
Click to expand...

Flashed TWRP it Mounted :D btw g60 you may wanna look into the mounting of a 64gb SD I think they don't work with CWM because TWRP mounted it.
 
Okay so heads up...Just bricked my SECOND GS3 trying to flash a kernel using this recovery >.< Ugh

Has something to do with how zip's install the kernel.


http://forum.xda-developers.com/showthread.php?p=42596356 <- used this one as an example



DO NOT FLASH ANY, AND I MEAN ANY KERNEL IN RECOVERY RIGHT NOW THAT HASN'T SPECIFICALLY BEEN TESTED OUT UNTIL THIS IS FIXED

Also, note to OP, if you want to test this (Which I wouldn't, unless you could somehow re partition from inside CWM) , it won't immediately brick your phone. You will stay in recovery. Only when you reboot will the phone not turn on, and you get the "QHSUSB_DLOAD" error when plugging into a pc.




*edit*
I think I might of found out what is happening (atleast partly).
I went through the install script of a few third party kernels, which should of worked on the phone for the most part...(atleast to the point of not totally bricking it), and it seems to do with how they write the boot.img

In all kernel install scripts I have found/gone through, the write line is as follows
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p5")
Click to expand...
Where as on the Virgin Mobile varient, it should be the following...
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p7")
Click to expand...
 
xthedakmanx said:
Okay so heads up...Just bricked my SECOND GS3 trying to flash a kernel using this recovery >.< Ugh

Has something to do with how zip's install the kernel.


http://forum.xda-developers.com/showthread.php?p=42596356 <- used this one as an example



DO NOT FLASH ANY, AND I MEAN ANY KERNEL IN RECOVERY RIGHT NOW THAT HASN'T SPECIFICALLY BEEN TESTED OUT UNTIL THIS IS FIXED

Also, note to OP, if you want to test this (Which I wouldn't, unless you could somehow re partition from inside CWM) , it won't immediately brick your phone. You will stay in recovery. Only when you reboot will the phone not turn on, and you get the "QHSUSB_DLOAD" error when plugging into a pc.




*edit*
I think I might of found out what is happening (atleast partly).
I went through the install script of a few third party kernels, which should of worked on the phone for the most part...(atleast to the point of not totally bricking it), and it seems to do with how they write the boot.img

In all kernel install scripts I have found/gone through, the write line is as follows

Where as on the Virgin Mobile varient, it should be the following...
Click to expand...

Thanks for testing and for the heads up!
 
You must log in or register to reply here.
Back
Top Bottom