Related
Hey Guys,
Being a new person on this forum, I was not able to post on the original thread, so posting here.
I have been on IceColdJelly421 - 1.6 - JellyBean 4.2.1_r1 for last 2 weeks and have found it to be an excellent ROM. However I noticed something very weird today.
My HTC ONE X's (international tegra) SDCARD is gone! when I connect to mac, I can only see my 2.11 GB internal phone storage, same from Settings -> Storage. I tried formatting the SDCARD (~27 GB) from TWN and mac (as FAT) but still it doesnt show up anywhere.
I also tried formatting the SDCARD from settings -> storage page, but that just keeps loading, nothing happens.
Any idea whats wrong here? I tried searching on the forum, but either didnt do a good job on it / didnt get anything
Please help / provide some input.
Update:
1) When I mount USB storage from TWN, i get a message on MAC that disk is not initialized. I format it as FAT from disk utility it works fine but then on reboot, I dont see in Android
2) Again from TWN when I try to format the SDCARD by using Wipe -> External Storage. The log says couldnt load SDCARD or something.
3) when "adb shell", I see my phone internal storage under /sdcard folder. Also I dont see any "0" folder inside my sdcard folder. As I understood from the IceColdJelly421 thread, 4.2.1 onwards, the SDCARD is mounted under 0 folder. But I dont see any.
-Rockingturtle.
Bump ! Any one ?
Have you flashed boot.img between different ROM versions? Because the boot.img in a particular version was bad and it was reverted in the following versions. Can't remember which though.
Try flashing boot from 1.6 for example, or 1.3.1.
I have the following files which I used.
$ md5 boot.img
MD5 (boot.img) = 77b5e63109c54aacca5e783d50cfece4
$ md5 aokp_ICJ421-V1.6.zip
MD5 (aokp_ICJ421-V1.6.zip) = a342a97d8cdbbe3f8f465aa9de809fd5
blackice.omca.co.uk/download/icecoldsandwich/IceColdJelly421 is not opening for me currently, will download again and check.
-Rock
rockingturtle said:
I have the following files which I used.
$ md5 boot.img
MD5 (boot.img) = 77b5e63109c54aacca5e783d50cfece4
$ md5 aokp_ICJ421-V1.6.zip
MD5 (aokp_ICJ421-V1.6.zip) = a342a97d8cdbbe3f8f465aa9de809fd5
blackice.omca.co.uk/download/icecoldsandwich/IceColdJelly421 is not opening for me currently, will download again and check.
-Rock
Click to expand...
Click to collapse
Flashed to another ROM and the problem is gone. Will download the ICJ again / wait for next release and try again.
-Rock
rockingturtle said:
Flashed to another ROM and the problem is gone. Will download the ICJ again / wait for next release and try again.
-Rock
Click to expand...
Click to collapse
Just re install the original recovery and do a factory reset in the bootloader page will erase every thing , then the sd will back again , then flash any recovery you wont.
samooorje said:
Just re install the original recovery and do a factory reset in the bootloader page will erase every thing , then the sd will back again , then flash any recovery you wont.
Click to expand...
Click to collapse
I tried that, but didnt work, the factory reset in TWR failed saying cannot mount /sdcard
When I flashed a different boot.img, TWR was able to mount and format the sdcard. Now I did a re-install of a different ROM (ARHD 18.1) and everything is working fine. Will try with ICJ again shortly. Seems like a lot of folks are reporting issues with 1.7.1.
-Rock
Just installed ICJ 1.7.2 by flashing the ROM from SDCARD, worked like a charm this time, both SDCARD and internal phone memory coming. Facing the following issues with the ROM currently.
1) The battery is draining faster, will let it settle for 1-2 days and then re-check. Will also adjust the brightness level, that helped a lot with 1.6
2) The rotation of home screen is still not working, I dont use that anyways , so no problemo !
3) Noted some disturbance / noise when doing a call in speaker mode. In earphone mode, it was crystal clear.
Thanks "Lord" and all the other team members for this !!
mputeop New
Just installed the 2.0 version from Lord...so far so good Thanks Lord !!
-Rock
Also trouble...
Hi, I'm also having some trouble trying to get to the 2.0.. - looking forward to it, Lord
(btw I have searched, but it's too much info to comprehend)
**1**
AFAIK I need to update my hboot (currently 0.95) and I installed the original backup (clean One X from HTC) and was trying the OTA update, but I get an error where recovery can't find the path ( "[E:...]")
Does it need original recovery?
**2**
Also when I'm trying to use the mv * ../ commands I get this:
mv can't rename '.': Device or resource busy
I'm not that experienced with the cmd/terminal stuff, so I can't really debug on my own yet :/
What does this error mean and how to fix it?
Thanks!
bjornops said:
Hi, I'm also having some trouble trying to get to the 2.0.. - looking forward to it, Lord
(btw I have searched, but it's too much info to comprehend)
**1**
AFAIK I need to update my hboot (currently 0.95) and I installed the original backup (clean One X from HTC) and was trying the OTA update, but I get an error where recovery can't find the path ( "[E:...]")
Does it need original recovery?
**2**
Also when I'm trying to use the mv * ../ commands I get this:
mv can't rename '.': Device or resource busy
I'm not that experienced with the cmd/terminal stuff, so I can't really debug on my own yet :/
What does this error mean and how to fix it?
Thanks!
Click to expand...
Click to collapse
#1 Yes, I have also faced this problem, the best is to restore HTC's stock ROM and recovery (this is important, as custom recoveries dont work) and then update. You can find the orignal recovery in the threads. People have posted them
#2 Did you follow the exact steps of booting into fastboot, adb shell and execute the commands from there? You might want to try a different boot.img for this. I used ARHD boot.img to do the changes and then got back to ICJ. I had to change my boot.img, because the ICJ was not showing my SDCARD at all.
Let me know if this helped.
-Rock
BTW on 2.1 ICJ now and loving it. I am facing some wifi, GPS issues. But that might be just because of my router (for wifi, as I had trouble connecting to my wifi even from mac, restart of router did the trick), for GPS / Signal, I noted low signal from carrier, so will wait for few more days.
Also noted that my soft keys are often skipping. The home button needs to be clicked twice at times. But in general and overall a very good ROM.
Thanks L0rd !!!
-Rock
Facing the following issues with 2.1:
1) The GPS fixing is taking a lot of time. I remember at office, I usually get a fix very quickly, but taking time now.
2) Post playing games (subway surfer), the device gets heated a lot specially around the camera area. This is draining the battery a bit.
3) Still loosing battery a bit faster than it did earlier.
4) The home button / associated vibrations dont register at times and I need to try them again. Also noted in subway surfer that game play is a bit jerky and some of my swipes are not registered. This might be due to any off: ROM, Kernel, Game, a poor screen guard.
Trying to get some data (logs etc) to substantiate the above observations. Might shift to ARHD for sometime to compare the data and provide better inputs.
-Rock
Installed ARHD, details captured here:
http://forum.xda-developers.com/showpost.php?p=38487569&postcount=39640
Yeah, I troubled the guys in their main thread after the HTC RUU exe surpriced me by erasing my SDcard, and mattoffshore gave me this link to a simple flashing tool: http://www.mediafire.com/?oik6tjvo28r9d
it worked out nicely, hboot 1.39 on .401. HTC__Y13 (tags for other unfortunate searchers)
ICJ 2.1 :good: until the next release any day now haven't had any big issues except a few camera FC and random hot reboots
-bjornops
Notes
I just got a nexus 7 2013 and was using it for 3 weeks (after root + cyanogen 10.2 installation).
I tried to flash a kernel which I thought could solve an issue with cifs support, and after that trouble began:
After reboot, the device is only works in portrait mode - no matter what I did.
I tried to hard reset the device, formatting it completely, and installing the 2013 original rom which I downloaded from here (the wifi version):
htt ps://developers.google.com/android/nexus/images#razorjss15r
The device is starting (still - only portrait) but I got errors for google play and other apps.
At this point I tried to "adb restore" a full backup image which I did before all these troubles began - the image was restored successfully more or less, but I do not have the sdcard mounted (I can see a FILE named /sdcard on the root using root explorer but no folder).
I have no Idea what to do next - I cannot seem to make the device work with the SD mounted and therefore cannot copy files to the device at all (I always get read only filesystem/permission denied messages when I try to adb push). The portrait stays the same - no landscape and because no sd available, I am getting errors for almost every operation I do.
I cannot even make it back to the original factory state (boot works, but I cannot start google play or copy files to the device).
Any help will be appreciated.
-----
Some progress - I've managed to flash the recovery image, cyanogen 10.2 + google apps and after that latest SuperSU.
The device boots ok, but immediately I get the error of google play store - "unfortunetley, google play store has stopped". Trying to run the camera app gives "Unfortunately, Gallery has stopped". Gallery application gives "No external storage available".
I do not know if this is related, but when I am in recovery mode, I am able to use the file browser and see the content of /sdcard (which contains the files I pushed using "adb push" in order to flash the device), but if I boot into android, using adb to /sdcard (as root -> terminal + su) shows an empty folder.
liran corleone said:
Notes
I just got a nexus 7 2013 and was using it for 3 weeks (after root + cyanogen 10.2 installation).
I tried to flash a kernel which I thought could solve an issue with cifs support, and after that trouble began:
After reboot, the device is only works in portrait mode - no matter what I did.
I tried to hard reset the device, formatting it completely, and installing the 2013 original rom which I downloaded from here (the wifi version):
htt ps://developers.google.com/android/nexus/images#razorjss15r
The device is starting (still - only portrait) but I got errors for google play and other apps.
At this point I tried to "adb restore" a full backup image which I did before all these troubles began - the image was restored successfully more or less, but I do not have the sdcard mounted (I can see a FILE named /sdcard on the root using root explorer but no folder).
I have no Idea what to do next - I cannot seem to make the device work with the SD mounted and therefore cannot copy files to the device at all (I always get read only filesystem/permission denied messages when I try to adb push). The portrait stays the same - no landscape and because no sd available, I am getting errors for almost every operation I do.
I cannot even make it back to the original factory state (boot works, but I cannot start google play or copy files to the device).
Any help will be appreciated.
-----
Some progress - I've managed to flash the recovery image, cyanogen 10.2 + google apps and after that latest SuperSU.
The device boots ok, but immediately I get the error of google play store - "unfortunetley, google play store has stopped". Trying to run the camera app gives "Unfortunately, Gallery has stopped". Gallery application gives "No external storage available".
I do not know if this is related, but when I am in recovery mode, I am able to use the file browser and see the content of /sdcard (which contains the files I pushed using "adb push" in order to flash the device), but if I boot into android, using adb to /sdcard (as root -> terminal + su) shows an empty folder.
Click to expand...
Click to collapse
By factory state you mean...?
Well on a side note, I tried using a CM10.2 with both their kernel and glitch's and based on my 1 month experience, battery issues are big time with this ROM and not the kernel itself. That is why I avoid CM10.2 based roms. If you're, however, satisfied with their features despite the battery drain then I guess you're good there. The custom ROMs have great stuff to offer.
MartCLEANRFr said:
By factory state you mean...?
Well on a side note, I tried using a CM10.2 with both their kernel and glitch's and based on my 1 month experience, battery issues are big time with this ROM and not the kernel itself. That is why I avoid CM10.2 based roms. If you're, however, satisfied with their features despite the battery drain then I guess you're good there. The custom ROMs have great stuff to offer.
Click to expand...
Click to collapse
well, at this point - i just want to make the device work...
Hello,
In the process of rooting and trying to install CWM Recovery in preparation to flash Cyanogenmod, I seem to have denied myself access to the phone's internal storage. In the "File Manager" app, I get the following screen:
Local: /storage
No files
No search results
In addition, any app that requires access to internal memory will not work, instead showing messages such as "Try again after scanning media files" or "Not enough storage". If I plug in the USB cable and set it to "Media sync (MTP)" mode, Windows Explorer will show the device but list the internal storage as having "0 bytes" and no files.
I already tried the following:
- Factory reset
- Flashing the official ROM through the Windows Enabler / UpTestEX tools
In both tries the phone was "reset", as in it returned to the initial Android welcome screen where you set up your Google account, but in each case I still didn't have access to internal storage.
This is what I have in the "About phone -> Software information" option:
Android version: 4.1.2
Baseband version: APQ8064T/MDM9x15M
Kernel version: 3.4.0
Build number: JZO54K
Software version: E98810b
The phone does not have Wi-Fi access either, which is why I was tinkering around with custom ROMs in the first place, so I won't be able to download anything to it as part of the solution.
Is there anything else I can try?
I'm guessing you used FreeGee to install CWM? Perhaps try restoring?
If that didn't work... Id move the EFS backups to my computer. I'd make a NAND backup in CWM. Then I'd get CM and gapps on a micro SD. I'd do a format of system, data, and cache. Then I'd install CM and gapps. Then I'd cross my fingers.
Sent from my LG-E980 using Tapatalk
ackliph,
Since I didn't have Wi-Fi access on the phone, and at the time I didn't know how to reverse tether it to the computer, I was looking for a procedure to install CWM Recovery that didn't involve downloading files directly within the phone (only transfering via USB). Right now I can't find the exact instructions I used, but it was similar to what is described by hkfriends in this thread: http://forum.xda-developers.com/showthread.php?t=2361941, the only difference being that the image I downloaded was not that one.
I rooted the phone with Universal Root, then followed those instructions to install CWM Recovery. It seemed to have worked, but when I rebooted... nothing happened! The phone booted normally, and if I tried entering recovery mode all I got was the stock LG recovery.
I continued looking for another way to install a custom recovery, but instead came upon instructions to flash KDZ files with UpTestEx. Since the immediate problem I was trying to solve was the lack of Wi-Fi access (and not really the custom ROM), I thought it couldn't hurt to try updating the stock ROM. The procedure did update my ROM, but I ended up in my current predicament: no access to internal storage, and still no Wi-Fi access! It even managed to unroot the phone.
So your suggestion would be to try installing CM via a microSD card. OK, I can get a microSD and try that. However, I do believe I will need root access to do anything of the sort. I tried Universal Root again, and got the following messages:
Beginning Root Process
/system/bin/sh: can't create /sdcard/G_security: Permission denied
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
1955 KB/s (1085140 bytes in 0.542s)
mount: permission denied (are you root?)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
Unable to chown /system/xbin/su: No such file or directory
You are now properly Rooted.
Click to expand...
Click to collapse
Evidently, that didn't work.
I guess I will need some other method of rooting it.
hi!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.
fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/
_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.
hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?
see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...
jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.
Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse
Hi All,
I have a LG G3 (European d855) that was previously running CyanogenMod 13, a long time ago it refused to install future updates either over the air or flashing, I left it a long time as it was only a secondary phone I used for work.
I have since decided to flash a fresh OS (Lineage and also tried AOSCP) as the only important thing on this phone was my contacts. At first TWRP was giving me an error 7 no matter what ROM I downloaded, I read to change the script in META-INF to bypass the security feature to remove the "Asserts" re-package and try again. So I used the adb push command to add the new packaged file to the device and attempted to flash. I now get a new error "could not find META-INF/com/google/android/update-binary" in the zip file (the binary file was never edited).
Also as a side note I can no longer connect with adb when I had no issues before. The phone currently has no OS and refuses to install any package.
Could I possibly have corrupt partitions?
Any help will be much appreciated