I was using the AOSP ICS build posted by jt1134 (at rootzwiki dot com/topic/11697-rom-cdma-aosp-ics-cm9-build101-0418/) for the Galaxy Tab CDMA. The first couple of nightlies worked OK on the tablet, but the camera never worked right. Someone else insisted that the camera works correctly on new builds, so they suggested I use CWM to wipe system, and I took it to mean wipe everything so as to start from scratch, and I wiped /data too. Apparently this triggered the emmc erase bug or something, so now my internal SD is useless.
Nobody over in that thread appears to be willing to make a build that works around the issue. I've already tried partitioning my SD card and editing vold.fstab and updater.rc inside the ROM, but these are apparently useless unless init.rc in the boot image (zimage I guess) is changed. A person attempted that but seems to have gotten the filesystem type wrong in the build (ext2 instead of ext4), and is unwilling to make another attempt. I don't know anything about compiling a custom ROM myself. I've looked into decompressing/recompressing the zimage, but it's too much for me.
What I'm asking here is, can anyone help get a build of ICS to me that I can flash, that will ignore the internal SD and use the external? This site is awash with reports and fixes for Encryption Unsuccessful for other phones and tablets, so I'm hoping somene here can understand my frustration. I haven't been able to use the tablet for over a month now, I think, and I'm not getting anywhere on my own. TIA
Why not ask this great forums section for your device...
http://forum.xda-developers.com/forumdisplay.php?f=1081
And which thread are you referring to...the thread at the other site....? I bet if you present your question or request here at the XDA for your device you will get an answer. Thank you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hi all,
You may need to bare with me a little with all of this, I'm extremely new to it all.
I picked up my Nexus S on Monday after previously owning an iPhone and then a Windows Phone 7 handset, firstly I have to say that I can't believe I didn't get an Android phone sooner - they're leaps and bounds ahead of the competition in my opinion and offer a much better!
With the help of a set of instructions I was able to unlock the bootloader and flash the recovery to use Clockwork 3.0.0.5, from there I was able to install Superuser from the ZIP to root the device.
Everything is working and rooted but whenever I try and get into the Clockwork recovery it keeps chucking me into the standard recovery, I've tried from the bootloader and from ROM manager.
The problem I have is that I can't backup my ROM because it just takes me to the standard recovery and sits there.
I had a look around but couldn't find anything relating to this on the forum.
There was mention of something called 'sgs kernel flasher' but it states it wont run on Gingerbread which I'm running.
Any ideas?
If you have any questions of something I may have missed out I can answer those!
Sosmething very similar to me recently. I just reflashed the clockwork recovery via adb/fastboot and works like a champ now.
Sent from my Nexus S
Cod Ball said:
I had a look around but couldn't find anything relating to this on the forum.
Click to expand...
Click to collapse
Good heavens.
http://forum.xda-developers.com/showthread.php?p=11080161#post11080161
http://forum.xda-developers.com/showthread.php?p=10238348#post10238348
http://forum.xda-developers.com/showthread.php?t=740748
shrivelfig said:
Good heavens.
http://forum.xda-developers.com/showthread.php?p=11080161#post11080161
http://forum.xda-developers.com/showthread.php?p=10238348#post10238348
http://forum.xda-developers.com/showthread.php?t=740748
Click to expand...
Click to collapse
LMAO! i agree with you
Thanks for pointing them all out
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for the help guys, as I said I'm quite new to all this so sadly the thread title:
"Q about cwm 3.0+ and 2.3.2"
Didn't quite stick out to me!
Problem sorted now though, all backed up and new ROM installed - happy days!
I'm getting an error when I try and ugprade my Android version. I'll start with the history and spec first:
Google Nexus One, bought in April 2010, it had Eclair (2.1) on it. I wanted Froyo 2.2 (for the hotspot/tethering) but the update delays being what they were I ended up rooting it, getting clockworkmod, and installing CyanogenMod 6 (based on 2.2). It's been the same ever since and I've been happy with it. It's only because a month or two ago it stopped being able to update any of the apps that I'm even wanting to upgrade, otherwise I'd be happy with CM6. I can no longer update or even search for apps. If I can't go back to plain Android because I've gone CyanogenMod, that's fine, I'll just go for a newer version of it.
I'm not wanting to live on the bleeding edge with ICS4 on this old-timer (yes I've heard it runs but with bugs), so if I can, I'll go for a plain vanilla Gingerbread 2.3.3.
I downloaded 2.3.3 from here and renamed it update.zip and put it in the root of my SD card. I shut the phone down and then followed the instructions I found here.
It seemed like it would be easy, but I'm getting this error after choosing "Apply sdcard: update.zip". After the error I show two screenshots of how I got to that point.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Feel free to delete this thread mods. I got an answer in another forum. For anyone else with the same issue, checkout androidforums.com
d4005 said:
Feel free to delete this thread mods. I got an answer in another forum. For anyone else with the same issue, checkout androidforums.com
Click to expand...
Click to collapse
For anyone with the same issue, you could have posted the solution here.Dont promote other sites.
I think the problem was with the file.
Sometimes the browsers get bugged and they dont download the whole package.
I have had this error a couple of times and re-downloading the rom fixed the solution.
Im getting graphic glitches on all of the ROM (Sense or Cm9). This has been happening after i installed the cm10 8/22 build.
Can anybody please help? Sometimes the screen goes upside down quickly.
p.s its hard to get screenshots of the glitch because they happen so quickly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I notice you are on Viper's new ROM. I am too and I never got this, not on any Sense ROM or AOSP. My suggestion to you is to start from scratch. Wipe everything, reformat your sdcard (which requires more wiping, so back up on computer), and install a fresh ROM. If you cannot access your sdcard at all, check the dev section; there is a thread to recover bricked devices and undetectable sdcards. Be ware, you may loose everything on the card, pics and all.
Closed Source Project said:
I notice you are on Viper's new ROM. I am too and I never got this, not on any Sense ROM or AOSP. My suggestion to you is to start from scratch. Wipe everything, reformat your sdcard (which requires more wiping, so back up on computer), and install a fresh ROM. If you cannot access your sdcard at all, check the dev section; there is a thread to recover bricked devices and undetectable sdcards. Be ware, you may loose everything on the card, pics and all.
Click to expand...
Click to collapse
after a reboot my sd card came back. wtf? I tried all of that I'm still getting random graphic glitches. I think the cm10 ROM messed up my graphic driver?
sherry478 said:
after a reboot my sd card came back. wtf? I tried all of that I'm still getting random graphic glitches. I think the cm10 ROM messed up my graphic driver?
Click to expand...
Click to collapse
No chance unless you installed without a wipe, and then it's slim. Maybe your accelerometer is busted.
Sent from my HTC One S using xda app-developers app
I've bought this Coolpad 7295 phone for less than three days from China.
It seems that I couldn't flash my phone back to the state where I could get the service for calling the first day.
After the second rom flashing with my flash tool. I kind of formated the Yl-parames and NVRAM section of the phone.
I don't know these two mean! Could someone explain how they work? Are they related to the hardware or the motherboard of the phone?
After the wrong formatting action, my phone could not make any calls. (But everything works, and network works also. And later I flashed many roms, all of them work, just no signal)
So the third picture shows that this device has a different partition compared to the most smartphones in the hardware called "YL-parames".
My friend who is good at making custom roms in Taiwan said I might accidentally screw up with the hardware partition.
I just want to know with this problem appearing, is there any other way that I could get my signal back?
I've tried several methods like rewriting IMEIs, reinstalling the official roms, but none of them work.
Or should I just send it back to the dealer to get it fixed? (I'm doing it right now...)
Just want to know in case the phone is back, how should I operate this flashing tool because I'm really a tech-savy
1) The first picture represents what i chose for the outcome of no signals later on.
2) The next one is its interface
3) The next one is the official flashing tool, but I still can not flash the CPB provided by the official since my hardware seems to be broken.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would really like somebody to develop the custom rom in the English version for this device, this device is pretty good!
Or is there anybody using this phone as well? It's nice to have someone to exchange info with!!
Threads I've gone through before posting:
http://forum.xda-developers.com/showthread.php?t=1931900
I'm really sorry to bother the admins here. I've searched a lot over the internet but couldn't find anything that would help me. Please take some time out and guide me. Sorry for the inconvenience.
I'm having this trouble of low internal space [130 MB] in my Qmobile X6. [I've pasted screen caps of the phone HW/SW configurations].
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't exactly remember how I solved this issue a few years back with my HTC WFS, but I do know that it was solved.
So I searched the internet and saw a video on YouTube about "External 2 internal"
I installed the app and while it prompted me for root, I accidentally tapped on the External to Internal button without setting the app as instructed. :crying:
This has resulted in restructuring of the entire storage space and I can't seem to fix any of that. All i remember was that it showed SDC as this:
But now it shows this:
I know that it has swapped the address, but IDK what the original one was to restore in the first place.
It has created these weird partitions and I can't seem to understand what's wrong with it.
I tried deleting the block folder in root/dev/ but it comes back after boot.
The files inside block are as follows:
I tried factory reset but no help.
Also, it has automatically removed all my linked apps. The link2sd now shows 2 partitions of the same storage space but after every reboot, the l2sd app disappears, and so does all those who get linked to SD.
Hi @sulayemaan. Since you messed up your partitions a factory reset won't help. You might have to flash the stock firmware again. There's no dedicated forum for your device here so try posting your query in:
> Android Development and Hacking > Android Q&A,Help and Troubleshooting.
Experts there may be able to help you.
Good luck