ok im sending my phone back to Samsung, (wifis now working it just says error) and the internet has no answer for it.. i bought this phone used, i wanna send it back with factory settings, but i nocticed when i flashed the basic rom to it, the kernal was the same as well it didnt change the radio.. can someone show me wich to use so it looks like i havent modded it at all?? (after that i will relock the bootloader)
thanks
j
wifi error ? probably kernel's fault , i have been same situation with WIFI error after i flashed new kernel
hmmmm
you didn't say which model , so , if it is i9023 , KF1 radio.
maybe format /system and /boot before you flash ROM could help
i have tried 5 different kernals, no help, i have teh i9020t thanks
have you tried whole new rom with everything and anything be wiped and formated ?
qtwrk said:
have you tried whole new rom with everything and anything be wiped and formated ?
Click to expand...
Click to collapse
sure have, i have tried at least 3 roms, 3 kernals, and 3 radios.
Flash your initial nandroid back.
polobunny said:
Flash your initial nandroid back.
Click to expand...
Click to collapse
yeah, its not working,
{
"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"
}
is there a way if i can mount the SD that if i have my cmw backup folder, i can just copy and paste?
how the heck do i fix my cache partition??
Update Clockworkmod Recovery, then try again.
same with me(i9023),open WIFI lead to crash or sometimes reboot itself.I've tried 12 roms and 4 basebands.Still couldn't be fixed.
Wish you can solve this problem,and share with me,thank you!
polobunny said:
Update Clockworkmod Recovery, then try again.
Click to expand...
Click to collapse
ive tried that, other versions as well, im having issues,, with the cache partition, ive been able to restore my backup, but the phone is running super slow, still giving me the same error above.
jerkwagon said:
ive tried that, other versions as well, im having issues,, with the cache partition, ive been able to restore my backup, but the phone is running super slow, still giving me the same error above.
Click to expand...
Click to collapse
You should be fine with 5.0.2.0 to restore your backup. That cache error happened back with 3.0.0.5 and 3.0.24 as far as I'm aware.
it did help! but the phone is crapped out, reboots, overheats and is mega slow.
Related
Hi everyone, I've searched everywhere and can't find an answer to this question.
I received a Nexus S with the bootloader already unlocked. I used fastboot to push the CWM recovery to it, and with it used .zip file to flash superuser to gain root.
I can boot the phone and use it without issue, but when I go into the Recovery menu, several error messages regarding its inability to mount the /cache partition comes up.
This means that I cannot backup, restore or flash anything, and I don't want to mess around with partitions in GParted until I know what to do.
Any suggestions here? Your help is greatly appreciated!
{
"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"
}
If you go to the "mounts and storage" menu, are you able to "format cache"? Give that a try and reboot to recovery and see what happens.
Hey thanks for the response. Unfortunately since I can't mount the /cache partition I can't format it. That was one of the first things I tried.
Here's what it looks like when I try to format /cache:
Code:
Formatting /cache
E:format_volumeL no MTD partition "cache"
Error formatting /cache!
Sent from my HTC Vision using XDA Premium App
When you boot the phone normally, you're able to go to /cache with Root Explorer or another file explorer type app or not?
Maybe try an older version of Clockwork, or even stock recovery to see if you can format/mount/wipe from one of them.
have the same problem but i can't boot in android either it just hangs at google logo and if i boot in recovery i get this error (didn't flash any roms yet it happend after i flashed clockworkmode
i was able to boot andriod again with odin but clockwork still gives the cache error so i still can't flash anything else on it
I have the exact same problem and I cannot flash any roms in my Nexus S at all.
@awryter : Is your nexus S the new "i9023"? Because mine is the new Nexus S, it might be the reason why our phones are different from others. And have this error :S
mine is alsof the Europeanen model i9023
Sent from my Nexus S using XDA Premium App
I just bought my Nexus S yesterday, and I seem to be having the same issue. I was able to unlock the bootloader just fine, as well as flashing ClockWorkMod, but as soon as I tried to install the netarchy kernel I noticed it wouldn't work.
I'm also using the I9023 if it makes any difference.
A new insight to this problem.
Most people, or even all the people, who have this problem. Are using the new i9023 Nexus S.
There are people who are using the i9023 Nexus S and have their phones rooted without problems. But their phones come with GRI40 instead of GRI54.
So I'm guessing it might be a problem of GRI54 i9023 Nexus S
navlem said:
A new insight to this problem.
Most people, or even all the people, who have this problem. Are using the new i9023 Nexus S.
There are people who are using the i9023 Nexus S and have their phones rooted without problems. But their phones come with GRI40 instead of GRI54.
So I'm guessing it might be a problem of GRI54 i9023 Nexus S
Click to expand...
Click to collapse
I have GRI54, and have it rooted just fine. It's just the cache partition that's not working for me.
rooting worked also for me, it's just that cache problem asswell
Maybe i used the wrong term. Installing custom firmware didn't work due to cache problems. Rooting on stock works fine for me, though titanium backup said its not rooted at all, even when superuser permissions are granted. Maybe you guys wanna try titanium backup and see if you are having the same problems as me?
navlem said:
Maybe i used the wrong term. Installing custom firmware didn't work due to cache problems. Rooting on stock works fine for me, though titanium backup said its not rooted at all, even when superuser permissions are granted. Maybe you guys wanna try titanium backup and see if you are having the same problems as me?
Click to expand...
Click to collapse
Looks like you're right. Titanium Root installed fine, asked me for super user permissions, which I gave it, and then it told me it didn't have root acces.
grwn6 said:
Looks like you're right. Titanium Root installed fine, asked me for super user permissions, which I gave it, and then it told me it didn't have root acces.
Click to expand...
Click to collapse
yep same over here
Yup, which brings me to why i used "Unable to root" as a term for our problems. Because we are not fully rooted in some sense yet.
But of cos the source of the problem comes from the cache which seemed to be 'non-existant' or 'non-writable'
And only GRI54 i9023 users have this problem.
after installing busy box , TI backup says it's rooted
suboxide said:
after installing busy box , TI backup says it's rooted
Click to expand...
Click to collapse
I can confirm this.
Rebooting after installing busybox removes the root rights again. I'm not sure if this is intended, but from what I've seen so far, I'd guess not.
I flash something new daily, I always flash back to my clean rooted backup before flashing something new. Lately it seems like it's running really glitchy. Is there a certain point where you just need to sbf back to stock or what ?
kickenwing13 said:
I flash something new daily, I always flash back to my clean rooted backup before flashing something new. Lately it seems like it's running really glitchy. Is there a certain point where you just need to sbf back to stock or what ?
Click to expand...
Click to collapse
thats usually a good indication to wipe data, format system, then flash rom of choice.
droidstyle said:
thats usually a good indication to wipe data, format system, then flash rom of choice.
Click to expand...
Click to collapse
I do that before each rom change, but I installed CM10 and it's much better.. Thanks
I've Flashed LIquid and for some reason I keep running like 1.5k and it'll get laggy and freeze up. I've cleared the rom, cache, system format, everything before I flashed both times but it still persists. I have a task manager that says there arn't any processes other than play store and swiftkey but its running into the red.. Any help?
jesseag7 said:
I've Flashed LIquid and for some reason I keep running like 1.5k and it'll get laggy and freeze up. I've cleared the rom, cache, system format, everything before I flashed both times but it still persists. I have a task manager that says there arn't any processes other than play store and swiftkey but its running into the red.. Any help?
Click to expand...
Click to collapse
Back in the day of my droid x I would flash stock, reroot, and unlock just to get a clean base .. it seems fine now for me.. but im getting a lot of data drops on cm10
This is Crazy I've flashed a Different rom and did the wipe factory reset and everything before hand and its still running High. After being Idle for about 3 hours it is burning hot and is running with like .05mb free out of 1.6 mb. I think I'm going back to Stock root
jesseag7 said:
This is Crazy I've flashed a Different rom and did the wipe factory reset and everything before hand and its still running High. After being Idle for about 3 hours it is burning hot and is running with like .05mb free out of 1.6 mb. I think I'm going back to Stock root
Click to expand...
Click to collapse
I had good luck using ODIN to flash a fresh base. I then rerooted and unlocked. I then created a backup, installed beans rom and it's sweet, smooth, good battery life... It may be worth trying.
kickenwing13 said:
I had good luck using ODIN to flash a fresh base. I then rerooted and unlocked. I then created a backup, installed beans rom and it's sweet, smooth, good battery life... It may be worth trying.
Click to expand...
Click to collapse
Maybe i'll try that then becuase this is getting unbearable. I'm running 3 system processes and its at 91% capacity..
{
"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"
}
Okay so apperently its the Media Storage Process that is killing my memory. for most people it just kills thier battery but mine has been having an adverse affect on my processing power and RAM. But glad its figured out incase anyone else has the same problem as me. They should really post that somewhere on the OP of the Jellybean ROMs because its kind of a big deal...
I have been trying to fix this problem and browsing threads with similar issues all night for about 6 hours and nothing seems to work.
I have been running on stock ICS 4.0.4 which I rooted and unlocked awhile back with no problems. I finally had the time to attempt to flash cm10 and I wanted to give it a shot, so I backed everything up, wiped data, wiped cache, wiped davlik, format /system. The ROM I attempted to flash was the newest version of cm10 nightlies 12-28 and gapps. After flashing everything went well and the phone booted up in cm10, but it is stuck on roaming. I tried everything that I could find in the forums and nothing seems to be working. I wiped again and tried to restore from my backup and the problem is still there, so I even went a step further and used Odin to flash fully stock unrooted/locked ICS 4.0.4 again and still have the same issue. The IMEI numbers matched up both times after flashing and I also made a backup before and even restored it to my phone as well, so I know that's not the issue.
Most of the threads I read said people were having success with "reprovisioning" their phone, but when I dial *2767*3855# nothing happens on my phone at all. Am I doing something wrong? Are there any other solutions out there that I might have missed?
Please help me so I don't have to return to the Verizon store when they open.
Thanks in advance!
You have to change to ruim/sim in mobile network settings
Should be under cdma subscription settings. Flashing to cm 10.1 changes it to Nv.
{
"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"
}
Also system select you should change to automatic, not home.
I can't find any of those settings in my settings menu. I am back on stock ROM unrooted and locked with everything reverted to factory settings.
Ahh no idea on stock rom or tw. This is for cm.
It's strange to me because after wiping everything and restoring to factory locked settings, you would think it would go back to what it's automatically set to...
I got it!!!
Basically I used Odin to port a stock ROM that was already rooted and went through the flashing procedures as usual. Then I used what you gave me above and it is now working. Thanks so much for your help it's really appreciated!
And to think after all the trouble I went through reflashing everything that was all I had to do :laugh:
Thanks a lot!
xNali said:
I got it!!!
Basically I used Odin to port a stock ROM that was already rooted and went through the flashing procedures as usual. Then I used what you gave me above and it is now working. Thanks so much for your help it's really appreciated!
And to think after all the trouble I went through reflashing everything that was all I had to do :laugh:
Thanks a lot!
Click to expand...
Click to collapse
I'm new to odin and am having the same problem you are having. How did you unlock the bootloader and put cwm or twrp without data. I can't get the ez tools because wifi doesn't even work.
Ok. I was wrong wifi does work. In all my panic I did the wifi password wrong. How embarassing... And it's fixed!
Glad to see you sorted it out. Was going to suggest flashing back to cm 10.1 to access the settings.
Don't let this experience turn you off. Cyanogen mod is really great.
If you don't want to deal with the roaming problem I'd recommend flashing cm 10 12/16 nightly. Everything works peachy with the exception of the Bluetooth bass bug. You can fix it by making a call though.
Cm10.1 has low call volume but it runs really smooth. When you flash it you have to either not flash gapps so you can change the settings I mentioned in previous post, bypassing getting stuck on activation, and then flash gapps OR use the four corner trick to bypass activation (if you flashed gapps). After you change the mobile network settings, reboot and data should be fine.
It's really not that hard of a process. I got stuck in roaming the first time I flashed 10.1 but I understood what the problem was before hand. I flashed 10.1 and gapps immediately, like I always do with cm, and was stuck on the activation screen. I forgot the four corner code to bypass the activation process also. When I tried to restore a nandroid I couldn't cause it moved all the files around.
To make an already long story short, I had to download 10.1 to my SD card to flash without gapps and make the settings change.
On 1.55 firmware and S-off with OTA ROM. Running xposed.
My phone decided to restart on its own... Then stuck on Verizon logo, decided to hold volume down/-. Phone goes to "safe mode", which I've never heard of, till I google it... Thought to myself, I'll just reset n go back to my rom.... Nothing.... No more safe mode on bottom left. All the verizon junk apps r back from frozen. And to top it off my 64gb sd card was totally wiped out! All data gone.. Luckily I backup occasionally so it wasn't exactly end of world.
I decided to run my nandroid n find that it's corrupt or not installing right... Give up n totally start over... Hard reset phone... Wiped everything cept internal memory. Installed cleanrom ...
Everything worked cept gps n wifi.... Reinstalled cleanrom again over w/o wiping n gps is working again cept wifi. I can tether but can't get on wifi...
So....
1. Watch out for safe mode... N backup often
2. Is there anyway I can get wifi back?
3. Is there another recovery that does backup rom well on m8?
Kensai said:
On 1.55 firmware and S-off with OTA ROM. Running xposed.
My phone decided to restart on its own... Then stuck on Verizon logo, decided to hold volume down/-. Phone goes to "safe mode", which I've never heard of, till I google it... Thought to myself, I'll just reset n go back to my rom.... Nothing.... No more safe mode on bottom left. All the verizon junk apps r back from frozen. And to top it off my 64gb sd card was totally wiped out! All data gone.. Luckily I backup occasionally so it wasn't exactly end of world.
I decided to run my nandroid n find that it's corrupt or not installing right... Give up n totally start over... Hard reset phone... Wiped everything cept internal memory. Installed cleanrom ...
Everything worked cept gps n wifi.... Reinstalled cleanrom again over w/o wiping n gps is working again cept wifi. I can tether but can't get on wifi...
So....
1. Watch out for safe mode... N backup often
2. Is there anyway I can get wifi back?
3. Is there another recovery that does backup rom well on m8?
Click to expand...
Click to collapse
Sounds to me like your kernel doesn't match your rom. . You can try flashing the stock kernel or the stock rom over top to see if that fixes it.
Thanks, I'll look around for a stock kernel. :thumbup:
http://forum.xda-developers.com/showthread.php?p=51703075
I actually found this... It's one of your posting. Would this work as stock kernel?
Kensai said:
http://forum.xda-developers.com/showthread.php?p=51703075
I actually found this... It's one of your posting. Would this work as stock kernel?
Click to expand...
Click to collapse
I literally just removed that from afh last night. Lol.
Any of the stock rom or firmware update zips posted would have a stock boot.img you could flash with flashify or fastboot.
Here's one for 1.12.605.11
http://forum.xda-developers.com/showthread.php?t=2712793
I flashed the suggested kernel. I backed up my current one before flashing n found its the same one I currently use. I tried dirty flashing cleanrom again. Still no wifi n battery drain more now. Dunno if xposed may be a culprit?
My next move is to just try the stock ruu that you made. I just have to manually install the tethers n power settings...
{
"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 got the Nov. update;
{
"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"
}
But, as soon as it starts installing, it fails. Doesn't even reboot. Almost doesn't even try.
Now, I do have an unlocked bootloader, which would be suspect number one to me, IF the bloody thing even rebooted. It's not even rooted.
Anybody else having this issue? I've tried re-downloading the update from a different WiFi access point, to no luck. I seriously wouldn't want to have to reset the whole thing to factory settings.
UPDATE: I formatted the whole device, after backing up everything manually, I erased the full device from the settings menu; once it was back up, I tried the update again. Same result. Can't update. So I went to download, from google Servers (https://developers.google.com/android/ota), the OTA corresponding to the version I currently have (NDE63L) and applied a "Rescue OTA", which is to adb sideload the full zip from google onto the device. Which would/will clean any and all software issues or incoherences that might be in my device.
Here's a guide to this process: https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view
That did the trick. And it didn't wipe my data. I alone did that. I could've just sideloaded the OTA and that's it, saving myself from the full wipe I did.
So is root preserved after sideloading the OTA?
Thanks!
suquet.paul said:
I got the Nov. update;
But, as soon as it starts installing, it fails. Doesn't even reboot. Almost doesn't even try.
Now, I do have an unlocked bootloader, which would be suspect number one to me, IF the bloody thing even rebooted. It's not even rooted.
Anybody else having this issue? I've tried re-downloading the update from a different WiFi access point, to no luck. I seriously wouldn't want to have to reset the whole thing to factory settings.
UPDATE: I formatted the whole device, after backing up everything manually, I erased the full device from the settings menu; once it was back up, I tried the update again. Same result. Can't update. So I went to download, from google Servers (https://developers.google.com/android/ota), the OTA corresponding to the version I currently have (NDE63L) and applied a "Rescue OTA", which is to adb sideload the full zip from google onto the device. Which would/will clean any and all software issues or incoherences that might be in my device.
Here's a guide to this process: https://drive.google.com/file/d/0Bz6x7k-VkpUJMlZ1aEliVnhMOHM/view
That did the trick. And it didn't wipe my data. I alone did that. I could've just sideloaded the OTA and that's it, saving myself from the full wipe I did.
Click to expand...
Click to collapse
I meeting the same issue on Pixel 128GB ROW ver. with 63H factory image shipped with it, FAIL to install OTA update. even I relock the bootloader again...!
I have never root, unbox and just unlocked bootloader, end-up with adb sideload latest OTA image.
still not clear next mouth, I will fail to OTA update again or not, hope someone clarify it