I have a problem, I flashed one of Morfic's new kernels that allow EXT4 without flashing the CWM that supports it.
Now the phone doesn't dial, doesn't connect to wifi, won't read my SD cards and CWM cannot see the SD card either. The phone won't connect or be read using ADB so I am really confused as to what to try next.
Related
Just bought a new sd card and when I try to flash a ROM or Kernel it doesn't go through. I have formatted it and it still doesn't work. Can anyone say what the problem may be?
and what data format did you used ? FAT or NTFS ? phone recognize your new card ?
I used FAT 32 format. Yes I can access stuff via the phone from the SD card its just that every time I go to flash a ROM or kernel it hangs up
Goldbatt said:
I used FAT 32 format. Yes I can access stuff via the phone from the SD card its just that every time I go to flash a ROM or kernel it hangs up
Click to expand...
Click to collapse
What app or procedure are you using to flash it? Does it hang right away after it starts or does it look like it is flashing and hanging mid way through?
I was using rom manager. It attempts to boot in recovery then gets hung up and I have to do a power volume up to reboot. There is usaully a triangle and the android logo when it hangs up.
If I switch to my old 8gb card it flashes successfully.
did you use the phone to format the card. I never have problems with SD cards as long as I let android, or clockworkmod format them
Yes I did I used ROM manager to format and I also re booted in recovery and formatted it that way
Sent from my LG-P999 using XDA App
Hello so, my first question is , i have the RED CWM installed on my infuse and the roms run great. However im stumped why whenever i am in red recovery i am unable to mount the USB Storage and see both of my partitions in Windows. I have installed drivers already and its worked long time ago. No missing drivers appear in Device Manager either. So yes, anyone can guide me to fix USB mount in red recovery.
Second question is..
EXT4!
Ive read and read about how wonderful it is, just curious if theres something im supposed to do in order to make my partitions EXT4 so that my phone runs quicker? I havent found a way to figure this out yet and would be nice if i can be pointed in the right direction.
I have the internal memory and a 2 GB microSD card.
USB mounting never worked for me in CWM on the Infuse, I assumed it was broken (it's only ever worked for me on my Captivate using kernels that specifically mentioned it was fixed). I just use adb to push and pull files while in the recovery menu.
As for ext4, it depends on the ROM/kernel you are running. If you flash an AOSP/CM/MIUI ROM, the phone will be using ext4. If you flash a Samsung ROM and you're running an ext4-compatible kernel, you can check the status of your filesystem and convert between rfs and ext4 using the voodoo option in CWM (or, if the kernel supports it, the Voodoo Control app).
USB mass storage mode has never worked in any CWM implementation I've ever seen.
Use ADB push/pull
So ive been at this for 2 days. I finally got the micro sd card with both files to install rom but in clockworkmod recovery i cant mount sd card nor format or anything. I can mount and unmount in the normal settings of the device and see it in root explorer but thats it. Its formatted to fat32. also on rom manager where it says to install from sdcard it only takes u to the internal sdcard which makes no sense because i was told u cant install a rom from the internal sdcard.
PS. This is my first Android Device!!!!
yeah
I am in the exact same situation. I am rooted on 4.0.3 and I wanted to install 4.0.4 or one of the custom ROM's. This is not my first android device but I am at a loss. I can not enter fastboot, can't load anything from the SD card in CWM recovery (get the message E:Can't mount /sdcard/), can not connect via ADB on my PC.
I feel that I have enough skill to do all of this because I have done it in the past. My ADB works fine with my Galaxy Nexus (just updated that and installed new kernel) so I don't know what is causing the problem. I have tried different SD cards(3) as well and nothing.
The biggest problem is I can not get into fastboot and SBF if I wanted to. I have been having issues with drivers even though I have installed motohelper like 6 million times.
I have tried factory resets and wipes and everything. I tried to do the factory update that is being pushed to me and I get an error. Any help would be greatly appreciated.
Sorry if this is stealing your thread but I think we are having the same problems.
check out my thread at xoomforums:
I PM'd it to u cus it dont let me put it here
Read all 3 pages. I think it will help u. posted same question there and a guy suggested to install the rogue cwm 1.5 recory via adb fastboot or whatever. he says that will read your sdcards. if i were u id try and fastboot on a different pc cus it looks like thats what we both have to do unfortunately. it looks like a pain!!! u have a xoom?
anyone figured out how to sort this?? really frustrating it just sayin E:can't mount sd card.. any help will be appreciated!!
platt said:
anyone figured out how to sort this?? really frustrating it just sayin E:can't mount sd card.. any help will be appreciated!!
Click to expand...
Click to collapse
If you are using CWM recovery from Rom Manager (not recommended for Xoom) it does only read your internal flash memory (called sdcard) but not your external microsd card (called external1???). So you need to flash a different custom recovery using adb/fastboot to flash a recovery.image file or, if you can flash through cwm (from internal sdcard) a recovery.zip file (either EOS or Rogue, depending on the ROM you will flash afterwards), Actually, any custom recovery is supposed to work for any rom, but in reality Eos works best for Eos and Rogue works best for the CM9 Kang.
Please, just remember, never flash a .zip file through fastboot, only an .image file!
+1 i agree with the above, fixed this last night. I download a couple recovery images, which were blank for some reason, so i downloaded the zips and extracted the recovery image folder. Then opened the command window from the folder with the recovery image and flashed it with fastboot. Now it works perfect.
Sent from my MB855 using xda premium
Fastboot
I had to use fastboot to flash an entire stock config when I got stuck in this loop.
TheAv8tor said:
I had to use fastboot to flash an entire stock config when I got stuck in this loop.
Click to expand...
Click to collapse
Atleast you got it out, mines been acting up since i flashed cm9. I think i might have to do that
Sent from my MB855 using xda premium
okantomi said:
If you are using CWM recovery from Rom Manager (not recommended for Xoom) it does only read your internal flash memory (called sdcard) but not your external microsd card (called external1???). So you need to flash a different custom recovery using adb/fastboot to flash a recovery.image file or, if you can flash through cwm (from internal sdcard) a recovery.zip file (either EOS or Rogue, depending on the ROM you will flash afterwards), Actually, any custom recovery is supposed to work for any rom, but in reality Eos works best for Eos and Rogue works best for the CM9 Kang.
Please, just remember, never flash a .zip file through fastboot, only an .image file!
Click to expand...
Click to collapse
Thanks for saving the last half of my hair which I hadn't pulled out yet.
Got the backup on SD ONLY after flashing the EOS recovery 1.5.0 (i tried the latest to begin with, did not work, made it worse flashing recovery from ROM Mgr)
http://www.xoomforums.com/forum/mot...ing-flashing-unrooting-under-one-roof-59.html has this particular recovery listed.
I still cannot boot in recovery using power+volUP...i have to get at least adb running. Any suggestion would be golden.
error mounting /internal_sdcard!
error mounting /internal_sdcard! pls help me it got stuck in boot loop tried to wipe cache and user data bt cwm says error mounting /internal_sdcard!
Ipse_Tase said:
Thanks for saving the last half of my hair which I hadn't pulled out yet.
Got the backup on SD ONLY after flashing the EOS recovery 1.5.0 (i tried the latest to begin with, did not work, made it worse flashing recovery from ROM Mgr)
http://www.xoomforums.com/forum/mot...ing-flashing-unrooting-under-one-roof-59.html has this particular recovery listed.
I still cannot boot in recovery using power+volUP...i have to get at least adb running. Any suggestion would be golden.
Click to expand...
Click to collapse
Delete any zip files or IMG files from sdcard and reboot it this helped me ............ Hit thanks if helped
Sent from my HTC Desire C using XDA Premium 4 mobile app
This is my first attempt at unlocking and rooting. So far I did manage to get unlocked. Now I am stuck at: Can't mount/sdcard . . . . .
I have been following the thread: [HOW] Rookie Rooting, Flashing And UnRooting Under One Roof
It seems to be layed out quite well and well, I'd never have gotten this far if it weren't for following those directions. I'm not discouraged because I know this is just a stumbling block. I can't wait to kill the bloatware and see if I can O/C this beast just a little.
Good luck to the folks who posted above me. I will post my results here.
Mike P.
I think the solution is much more simple...
The recovery uses normally e: an external sd card , you just trying by d: internal sd card , so take another sd card and dun let it be internal sd card...
And the recovery back on working with you
ok here is my problem i flashed custom roms trying to see what they were like on the tf101, after flashing cyanogenmod my sd card no longer mounted so that was kind of a deal breaker so i flashed the stock rom back to the device and my sd card still doesn't mount unless i use paragon NTFS +HFS and format it as NTFS and then mount via the app. (NTFS and fat32 worked fine by default with no app in the stock rom)
then i tried the ubuntu touch os for phones and tablets, keyboard freaked out and closed every time i went to type so again back to the stock rom now wifi doesnt work right and it wont get on the internet half the time or see other computers on the network. anyone know a fix for these issues?
both of these things worked fine before using custom roms/os's.
nvflash it back to total stock, since there is probably leftover junk from when you flashed your device that is causing things to not work.
Wheelie (NvFlash)
androidroot.mobi
Images
xdafileserver.nl
This will be a long post as i have tried many solutions and i am really stuck. After xda search and google searches, i still have not found an appropriate guide/answer to my problem. Any help is much appreciated!
Ok so to the background:
I have a sm-n920t (tmobile note 5), unlocked, with twrp touch, skyhigh kernel, and teksodus hybrid rom for n5. Doesnt have sd card slot!
(this is the device im having issues with)
I also have a zte awe n800, rooted, nothing else custom. Has sd card slot with 7gb card!
I currently have no pc on hand
I also have a usb otg cable, a micro sd card reader (to use sd with n5), and a UNFORMATTED usb flash drive with about 4gb
My problem:
I frequently flash roms to my n5 (last stable: twrp touch 2.8.7.1 by manhit, skyhigh kernel, tekxodus n5 hybrid). Upon attempting to flashing a new release of tekxodus, i accidentally erased EVERYTHING. As in when preflash wiping, i checked all boxes (including system and data). So at this point i have a n5 in twrp with no OS. The copy of my rom was on the device. I have copies, but not on the device. So basically the phone doesnt have anything except the skyhigh kernel, recovery, and bootloader. Again (because i saw this alot) i have no sd slot on the n5, no nandroid backup, and no copy of rom on device
Ok so now on to
What i have tried (in order):
Searching ENTIRE n5 filesystem (using twrp file manager) for rom/nandroid
Adb push (when i had a pc) RESULT cannot find device, no matter what state phone/pc was in (restart, safe mode, admin, etc.)
Adb sideload (via twrp when i had a pc) RESULT same as above
Odin flash (when i had a pc) RESULT reflashed kernel successfully, could not find rom in tar.md5, would not flash a custom tarball or custom tar.md5 (odin force closes, typical for flash error)
Mtp via pc RESULT pc wont recognize pphone
Usb otg (via mirco sd adapter with my sd card with my rom stored on it) RESULT n5 would not mount/read sd card
Usb otg(via usb flash drive) RESULT wouldnt mount on n5, zte awe doesnt support otg, friends s6 edge load flash via otg fine. I know the drive is not formatted using ext4, which i hear n5 otg uses
What i want to avoid:
Flashing stock rom via Odin
Ive been stuck on this for 2 weeks now, any help guidance of anything is so greatly appreciated
I did the same thing. I had to flash the team win recovery then odin to stock.
U should download a new custom rom via PC and copy that ROM to ur otg flash drive.
If twrp can read that external otg flash drive then just flash that ROM to ur phone
If you have a copy of the rom on your USB drive just get to a PC and flash CWM as it has OTG support and you can flash from the USB drive.