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.
Related
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.
More and more people keep having this problem. Your phone suddenly has tons of force closes, and becomes unfunctional. Well we seem to have a problem with our recovery, possibly causing a corrupt partition. There is a solution .......use odin to flash the stock recovery tar found in development. Boot into stock recovery.. wipe data, and cache 3 times each ,and boot the rom back up. Then use rom manager to flash the tmobile gs2 cwm recovery. This does work. And has been proven numerous times.
Here is the stock recovery http://forum.xda-developers.com/showthread.php?t=1360943.
If for some reason you still have this issue after following my advice. Use odin to flash the stock firmware tar found here http://forum.xda-developers.com/showthread.php?t=1342348. After your done. Let it boot. If u get the force closes. Then proceed to power off, boot into stock recovery, and then wipe your data/cache, and reboot
{
"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"
}
Excellent post... Thx
another good one Silver Thanks....im curious as well to see how many are really having this issue<<<
Is there a difference between the TMobile GS2 CWM recovery and the CWM recovery flashed using this method (http://forum.xda-developers.com/showthread.php?t=1340526)?
I had the described problem, but wiping and reloading the intended ROM in CWM recovery fixed it.
That is good but alot of times that does not work. It can actually get to the point where it will not read the internal sd card
How are you guys flashing....and what are you flashing that is giving you these issues.
I have yet to experience these issues on T-Mobile or skyrocket roms.
What are the exact steps you follow when flashing a from to begin with?
Sent from my SAMSUNG-SGH-I727 using XDA App
I have experienced this on stock, and custom roms. And im not the only one. Alot of people have had this issue
Lets put it this way enough people have had this problem, and more will to the point where i made this thread, and asked a mod (jayharper08) to sticky it.
yes ALOT have......they may not have known it was a known issue and solved it. but it is there.
I am not saying you guys are not having issues...there has to be a reason I am not which is why I ask.....What steps exactly do you guys use to flash a rom and what roms. The process to fix it is great but if we could prevent it in the first place wouldn't that be better????.
silver03wrx said:
I have experienced this on stock, and custom roms. And im not the only one. Alot of people have had this issue
Lets put it this way enough people have had this problem, and more will to the point where i made this thread, and asked a mod (jayharper08) to sticky it.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using XDA App
Silver,
Question...based on several of your other posts in threads, if we have 2.3.6 and use http://forum.xda-developers.com/showthread.php?t=1340526 to root/install recovery, are things ok?
Or should we still follow this thread to update CWM via ROM Manager?
Thanks.
^^^
That was my question too. What's the difference between the two recovery's?
I was having the issue too. I had the issue on stock(pure from store) as well as stock rooted, skyrocketeer, and cm7.
One thing I have tied it to, which I am not sure is the true reason but I was too impatient to test it thoroughly, is excessive SMS messages.
I have over 32k messages currently stored on my HTC Inspire. These have been moved from my G1, to Nexus One, to Inspire with no issue at all. When importing to my Skyrocket, the messages will import fine for a while. Afterwards, I would get random FCs, screen freezes up(can't do anything, not even turn off the screen), and network disconnects. I can force a reboot by holding the power button and it will work for about 5 minutes and then repeat the issues as before.
At first I thought it was the specific device having radio issues so I exchanged it for a new unit at Best Buy. I was still having the same issues with the new unit so I just figured I could cut my losses (on screen protectors and phone case) by just returning the until outright. I figure I will wait for the ICS update for this phone, hoping it will be more stable. Maybe at that point I can compare with other phones available as well.
I have had this problem repeating several times even after flashing the Rom and repeating steps as mentioned. I think it does it with a certain number of apps that downloaded from the market.
silver03wrx said:
More and more people keep having this problem. Your phone suddenly has tons of force closes, and becomes unfunctional. Well we seem to have a problem with our recovery, possibly causing a corrupt partition. There is a solution .......use odin to flash the stock recovery tar found in development. Boot into stock recovery.. wipe data, and cache 3 times each ,and boot the rom back up. Then use rom manager to flash the tmobile gs2 cwm recovery. This does work. And has been proven numerous times...
Click to expand...
Click to collapse
Is this a problem that develops as you start flashing more and more ROMs? Is there a known cause?
I'm new at this stuff - just rooted and tried my first ROM this week. I'm tempted to try others but if chances are good that I'll run into problems/issues even if I'm going about things the right way - I might hold off on making a change given that the phone is stable right now.
Thoughts?
NO rom does not cauz this issues. What causes issue is when you restore data from ur backups. Plus there is problem with cwm it does not fully wipe data because cwm was not particularly made for our phone. That being said you do not have to worry about a thing. I am flashaholic and i used to flash every other day since i m with Sky ice cream rom by Sean i don't flash a lot. Don't worry just try out all the roms you won't have problem by roms at all. There was only one rom that had problem Alien the first or second build.
Locoman_ said:
Is this a problem that develops as you start flashing more and more ROMs? Is there a known cause?
I'm new at this stuff - just rooted and tried my first ROM this week. I'm tempted to try others but if chances are good that I'll run into problems/issues even if I'm going about things the right way - I might hold off on making a change given that the phone is stable right now.
Thoughts?
Click to expand...
Click to collapse
Thank for the reply.
BTW, I'm using Sean's Sky IC too. Sooo nice.
Do you need to go into download mode to flash the recovery in ODIN? Or do you do it when the phone is just turned on regularly?
You have to go to dload mode in order to flash recovery. and use odin.
nutsngum said:
Do you need to go into download mode to flash the recovery in ODIN? Or do you do it when the phone is just turned on regularly?
Click to expand...
Click to collapse
I tried this process and I wanted to flash a new ROM. But in recovery mode it wouldn't read my SD card, and when I transferred the .zip to my internal memory and I tried to install it said I had no space.
Any ideas?
Apologies for not actually being a helpful contributor to the actual problem of unlocking the Verizon Galaxy S3 bootloader, but I came across this one time after booting my phone after replacing the battery
{
"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"
}
The Samsung logo, with an icon of an unlocked padlock, and the word "Custom" (this is the very first boot screen, before the boot animation and the Galaxy S3 logo), so it's the bootloader screen.
The only way I can replicate this is by taking out the battery and replacing it. Simply rebooting the phone does not show the icon. I suppose this could have been due to one of three things:
(all as directed by http://forum.xda-developers.com/showthread.php?t=1756885 for reference )
flashing the rooted boot image using Odin
installed custom Clockworkmod recovery
flashed custom boot image
Everything still boots properly, I don't have a brick. Is anyone else experiencing this that perhaps didn't follow these three steps?
A lot of people have been reporting this. Sometimes its completely random, sometimes can be replicated. Seems to be related to recovery image afaik, however some have reported being 100% bone stock and getting it. Its absolutely nothing to worry about.
Sent from my Galaxy S3 using Tapatalk 2
I wasn't worrying about it, as I said, the phone still boots completely fine, I was wondering if it was indicative of something unusual with the bootloader (such as the impossible chance of it actually being unlocked) or if it was reported by a large number of users.
I literally just saw that on my phone for the first time about 2 hours ago..... im having major issues right now from deleting busybox i guess the "wrong way"... this is my first time posting on this site, though i have read it for years, anyones help or advice would be appreciated......
I came across this image when i would hold the power button then hit restart and that image came up.... only after i attemped to install chainfire 3D and deleting busybox...
Please help me out my brothers n sisters
http://forum.xda-developers.com/showthread.php?t=1830457
RealMuphukkinG said:
I came across this image when i would hold the power button then hit restart and that image came up.... only after i attemped to install chainfire 3D and deleting busybox...
Click to expand...
Click to collapse
Mm, if you're having issues booting, then I think that's something different. I wouldn't know exactly how to fix that.
I have it also.
- Installing VRALG1 rooted alone won't trigger it--in fact, I wipe, flash that, reboot to clear the "Custom" tripwire
- Installing NoSympathy VRALG1 deodexed triggered it for me, twice
- Installing blueui with metamorph triggered it (cf. http://forum.xda-developers.com/showthread.php?p=30085423)
- Installing BlueICSFull.zip (http://forum.xda-developers.com/showthread.php?t=1775235) plus some other action (like configuring/using e-mail, not sure, installing some normal app) triggered it for me
Other than giving VZW an [illegal] excuse to void your warranty, I haven't seen an issue with it.
I just started getting this last night during a reboot .
My device showed this screen right out of the box!
I've seen this after a battery pulls. I'm on my 2nd GSIII and I was worried they wouldn't refund the amount to me if that showed up.
I rooted and flashed the Synergy Rom on my GSIII, as well as my fiancee's and my brothers. My phone was the only one to display this custom lock icon (randomly). I'm pretty sure it had something to do with flashing the cwm touch, then the cwm6. To fix it, I read users gained success just by wiping cache and dalvik, but it didn't work. So I tried flashing the stock recovery instead (hearing it's a recovery issue that 'throws' some sort of flag). It didn't fix the issue. I even ODIN'd back to stock, and it still didn't fix the issue. Everything I tried didn't work.
However, after I went ahead and re-rooted using the root66 method, then installing cwm touch, and then booting into recovery, wiping system, data, cache, dalvik, performing a factor data reset, and then installing the Synergy rom (I used 1.6), (ASSUMING I was just going to have to deal with the custom lock icon forever).... it somehow magically fixed itself.
Hope that helps. Ever since then, it's worked just fine, no custom lock icon. Since then, I've booted into cwm touch, wipe cache/dalvik, and have even updated to the newest Synergy (1.7), and it's remained just fine.
Hope this helps.
I froze the SysScope process. I don't get the custom padlock at boot, but because that process can no longer communicate with the phone I do have phone status as modified.
Sent from my SCH-I535 using xda app-developers app
I found that I triggered it by changing cpu settings, doing a recovery or basically changing any system setting. I cured it by flashing stock recovery, wiping data and cache. Then I rooted again but didn't change anything and still no padlock.:thumbup:
Sent from my SCH-I535 using xda app-developers app
Broadley1 said:
I found that I triggered it by changing cpu settings, doing a recovery or basically changing any system setting. I cured it by flashing stock recovery, wiping data and cache. Then I rooted again but didn't change anything and still no padlock.:thumbup:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem as well. By any chance was everyone here with the problem running TWRP as their recovery?
I'm bone stock and have gotten that, from time to time during reboots since release day.
Apologies for bumping an old thread....
I never had this screen before until I bought an extended battery from Gorilla Gadgets and as soon as I started using it I started getting that screen...
I did flash the Verizon stock (with root) but even then it never showed this screen until the moment I used the battery.
Does this void the warranty?
Casual root
I just did the casual ver. 795b root last night so I could stay on 4.1.2 for right now and I have this custom and unlock pic on the Samsung screen not sheer if I should do something or not?????? help if you have any ideas
Broadley1 said:
I found that I triggered it by changing cpu settings, doing a recovery or basically changing any system setting. I cured it by flashing stock recovery, wiping data and cache. Then I rooted again but didn't change anything and still no padlock.:thumbup:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How did you flash stock recovery?
Sent from my SCH-I535 using XDA Premium 4 mobile app
XXDroidZillaXX said:
How did you flash stock recovery?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Seems like he have to root again so he probably used ODIN.
I get this and then my phone has a yellow triangle of death... I still can't figure out how to fix this as I've tried JOdin on my macbook pro with stock flash's and pit files that are corrupt apparently. Anyone else know what I can do to debrick this? I've checked the other brick posts and nothing ;\
I believe this is caused by KNOX Security being triggered - which is irreparable
I think this indicates KNOX security was triggered and therefore your phone is no longer "pure". I don't know exactly what KNOX does, but I believe it burns a fuse in your phone that locks to either a 1 or a 0 - and once it's triggered, it can't be undone.
All of this is speculation though, I suggest looking up KNOX security and see what the experts say. This happened to me a few years ago and at the time, there was no fix. I'm sure someone found a way around it by now - or at least a way to prevent or remove it completely.
Okay, so my phone is running the old Froyo 2.2.2 which I restored. I wanted to go back to Froyo since ive been with CyanogenMod 7 (Gingerbread) ever since it came out and i like Froyo a little better. The main reason for Froyo was testing my apps which I hate using the Emulator and would rather test my apps on my own phone for the same experiance.
My phone is running the old baseband which is the one from July 15, 2011
{
"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"
}
Now, I heard there is a March 12, 2012 baseband update which makes your phone faster which id like. The problem is, if i update, I have to go to Gingerbread.
If i update, will I not be able to ever go back to Froyo (2.2.2)?
You wrote a lot just to ask, "I want to use Froyo, but I'm on the old July baseband, if I upgrade to the March one, I can still use Froyo?"
I want to say that it's possible. Just make a nandroid, update baseband, restore nandroid, flash the new_baseband.zip (use Google to find it).
Tell us how it goes!
No gaurantees.
1. Root your phone if it isn't.
2. Install CWM if it isn't installed.
3. Boot into CWM.
4. Make a backup of the Froyo installation you've got installed now to the external flash memory card in your phone, not the internal memory.
5. Install the newest LG USB drivers for the phone onto your computer then install the V21Y .kdz firmware file with the offline install method which, along with installing the newest baseband and GB, will wipe CWM off the phone.
6. Boot phone normally.
7. Root your phone again.
8. Install CWM.
9. Boot into CWM.
10. Restore the Froyo backup.
Report back about your experience.
buru898 said:
You wrote a lot just to ask, "I want to use Froyo, but I'm on the old July baseband, if I upgrade to the March one, I can still use Froyo?"
I want to say that it's possible. Just make a nandroid, update baseband, restore nandroid, flash the old_baseband.zip (use Google to find it).
Tell us how it goes!
Click to expand...
Click to collapse
Do you flash the old baseband or the new_baseband.zip? The clicking noises in calls stopped when I flashed new_baseband after restoring a froyo nandroid.
buru898 said:
You wrote a lot just to ask, "I want to use Froyo, but I'm on the old July baseband, if I upgrade to the March one, I can still use Froyo?"
I want to say that it's possible. Just make a nandroid, update baseband, restore nandroid, flash the old_baseband.zip (use Google to find it).
Tell us how it goes!
Click to expand...
Click to collapse
Core Memory said:
No gaurantees.
1. Root your phone if it isn't.
2. Install CWM if it isn't installed.
3. Boot into CWM.
4. Make a backup of the Froyo installation you've got installed now to the external flash memory card in your phone, not the internal memory.
5. Install the newest LG USB drivers for the phone onto your computer then install the V21Y .kdz firmware file with the offline install method which, along with installing the newest baseband and GB, will wipe CWM off the phone.
6. Boot phone normally.
7. Root your phone again.
8. Install CWM.
9. Boot into CWM.
10. Restore the Froyo backup.
Report back about your experience.
Click to expand...
Click to collapse
Baseband said:
Do you flash the old baseband or the new_baseband.zip? The clicking noises in calls stopped when I flashed new_baseband after restoring a froyo nandroid.
Click to expand...
Click to collapse
Buru898: Yea i know. I thought if i write too little, people may just post a question and never come back
Core Memory: When I had CM7, i couldnt flash Froyo because it would fail, i had to "restore" it back, hope it works...
Baseband: Clicking noises? Never heard of them.
I will do this now since I dont got much too do... This should not take long, wish me luck!
Dude, you won't want to go back to froyo. Trust me. I'm a stranger on the internet.
Sent from my Nexus 7 using xda app-developers app
Baseband said:
Do you flash the old baseband or the new_baseband.zip? The clicking noises in calls stopped when I flashed new_baseband after restoring a froyo nandroid.
Click to expand...
Click to collapse
Ah yes I meant new_baseband... I corrected my post thank you .
Well, im not sure if its bye bye froyo or an error.
I decided to do the same way I did it last time, by restoring, but clockworkmod gave an error saying I need to verify im on the latest version of ROM Manager (which i am, downloaded straight from the Market)
It also said it dropped a .txt file on my phone containing the error information, this is what it dropped:
http://pastebin.com/raw.php?i=LHnP3nuz
Anyone can help me understand this?
Party of the problem might be using ROM Manager to flash CWM. You need to use NVflash to avoid problems
Sent from my LG-P999 using xda premium
MasterMRZ said:
Well, im not sure if its bye bye froyo or an error.
I decided to do the same way I did it last time, by restoring, but clockworkmod gave an error saying I need to verify im on the latest version of ROM Manager (which i am, downloaded straight from the Market)
It also said it dropped a .txt file on my phone containing the error information, this is what it dropped:
http://pastebin.com/raw.php?i=LHnP3nuz
Anyone can help me understand this?
Click to expand...
Click to collapse
ROM manager?
ONLY ever use ROM manager JUST to rename your backups. NEVER use it for anything else.
Now go flash clockwork via nvflash. Don't even risk using ROM manager to boot to recovery, do that manually.
buru898 said:
ROM manager?
ONLY ever use ROM manager JUST to rename your backups. NEVER use it for anything else.
Now go flash clockwork via nvflash. Don't even risk using ROM manager to boot to recovery, do that manually.
Click to expand...
Click to collapse
Well, something extremely weird just happened to me.
I decided to use ROM Manager to boot into Recovery (Yes, i rerooted the phone using SuperOneClick) so i can do it manually. The first problem I see is that i cannot go up or down using the Volume buttons, I have to press it 2 times and it will skip one.
For example, pretend this is the options:
---------------------------------
Reboot Device<-- (Im here)
Back up and Restore
Install from SD card
------------------------------------
When i press the Vol. Down button once, nothing happens. When I press 2x fast, instead of going down to the "Backup and Restore", it skips it into "Install from SDcard"
On top of that, i cannot use the power button to actually select an option. Im just stuck in the options screen. Also, randomly, a message saying 'The Back button is disabled" or something along those lines pops up when im going through the options repeatly.
I flashed ClockworkMod (using ROM Manager with a stable WiFi) again to see if that fix it and the problem is still present.
I NEVER had this problem before so im quite scared. Anyone know whats going on?
Again, use NVflash to flash CWM. ROM Manager doesn't work on a low enough level
Sent from my LG-P999 using xda premium
rtotheichie said:
Again, use NVflash to flash CWM. ROM Manager doesn't work on a low enough level
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Ill try but my phones cable is very bad, if i move it a little, it could disconnect.
Also, i dont know how long i have to hold it
EDIT: Worked successfully! I was able to flash CWM using NVflash. Also, instead of booting to recovery from ROM Manager, i booted it manually (Power + Vol Down) and was able to restore to Froyo.
Thanks! this thread can get locked!
When i flash CM based roms i lose my baseband and imei, i have tried flashing a lot of roms and every rom makes my baseband and imei unknown. I used to flash roms all the time and this would never happen, but one time before flashing omni rom i accidentally wiped /system in CWM, and after that every rom has the same problem. I have tried flashing stock via odin and that brings back the imei and baseband every time, but i don't wan't to use stock. Can anyone help me?
One more thing. I have tried backing up both efs and modemfs while on stock and then recovering them on CM but it doesn't work, Also I have noticed that the efs folder is not empty when the baseband and imei are unknown.
[email protected] said:
One more thing. I have tried backing up both efs and modemfs while on stock and then recovering them on CM but it doesn't work, Also I have noticed that the efs folder is not empty when the baseband and imei are unknown.
Click to expand...
Click to collapse
Try with this http://forum.xda-developers.com/showthread.php?t=2165344&page=4
shut_down said:
Try with this http://forum.xda-developers.com/showthread.php?t=2165344&page=4
Click to expand...
Click to collapse
the user in that thread is on ginger bread, wouldn't the process be different in jelly bean?
It won't be a problem since you're issuing commands through ADB. Just have rooted JB + cocore + working busybox and give it a try.
here is what i did in terminal emulator:
$su
#busybox mke2fs /dev/block/mmcblk0p7
mke2fs: can't format mounted filesystem
it seems that /efs is mounted but android isn't recognizing it, I'm on CM11
I've read in other threads that nv_data.bin is my imei, but when I went to /efs to see if I have a nv_dada.bin I noticed I only have a nv_data.bin.md5 and a nv.log, this is what the nv.log had inside:
Sun Jan 1 00:00:03 2012: NV data back-up begin.
Sun Jan 1 00:00:03 2012: nv_data.bin does not exist.
Sun Jan 1 00:00:03 2012: NV data backup stopped due to NV data size.
Sun Jan 1 00:00:03 2012: MD5 is turned on.
Also I have noticed that nv_data.bin.md5 is 0B
bump
[email protected] said:
bump
Click to expand...
Click to collapse
Better try searching about that problem, on our sections. Do not use other phones fix because we can have differend partitions, so you can mess up even more...
I have searched and tried almost everything, nobody has experienced this problem
[email protected] said:
I have searched and tried almost everything, nobody has experienced this problem
Click to expand...
Click to collapse
On what baseband is your phone? The one from Hong Kong make this problem, and no one solved it.
I'm on the latest Italy Firmware, and I have been able to flash roms before without experiencing these problems.
I found a thread where there was an Odin flashable modem/baseband so now I'm going to try to flash that on TC CM 11 and report back... good luck to me
still baseband unknown
Some additional things I have noticed...
When I flash the Italy Firmware, which the CSC is I9070ITVLQ5, after the flashing process finishes ODIN shows the blue "RESET!" and even if I wait it doesn't show "PASS!" and my phone goes in a bootloop, so i have to go to recovery to wipe data/factory reset, and only then it will boot, now every thing seems to work good, but, when I go to setting the baseband should be I9070ITVLQ5 but it shows I9070XXLQ4. I've flashed one other firmware and the same happens, bootloop and the baseband doesn't change.
What I'm going to try is revert back to gingerbread and then update it via Kies... maybe then i could flash CM roms... good luck to me!
[email protected] said:
Some additional things I have noticed...
When I flash the Italy Firmware, which the CSC is I9070ITVLQ5, after the flashing process finishes ODIN shows the blue "RESET!" and even if I wait it doesn't show "PASS!" and my phone goes in a bootloop, so i have to go to recovery to wipe data/factory reset, and only then it will boot, now every thing seems to work good, but, when I go to setting the baseband should be I9070ITVLQ5 but it shows I9070XXLQ4. I've flashed one other firmware and the same happens, bootloop and the baseband doesn't change.
What I'm going to try is revert back to gingerbread and then update it via Kies... maybe then i could flash CM roms... good luck to me!
Click to expand...
Click to collapse
well, that pass/reset in odin doesn't matter. just wiping data and cache will solve it and i too experienced it many times, afik in our device imei is in efs and you may have want to search about it. i found a thread somewhere for this problem and solution is clearly written there, if i get that thread i will say
PradeepMurugan said:
well, that pass/reset in odin doesn't matter. just wiping data and cache will solve it and i too experienced it many times, afik in our device imei is in efs and you may have want to search about it. i found a thread somewhere for this problem and solution is clearly written there, if i get that thread i will say
Click to expand...
Click to collapse
believe me I have tried wiping data/factory reset and also wiping the cache many times, my problem is still there
M0shi said:
believe me I have tried wiping data/factory reset and also wiping the cache many times, my problem is still there
Click to expand...
Click to collapse
I read in another forums, for another devices, if you flash another modem.bin in the rom, it works, i don't try this but you don't loose anithing triying
Sorry for my bad english, hope you undestand me
shompy said:
I read in another forums, for another devices, if you flash another modem.bin in the rom, it works, i don't try this but you don't loose anithing triying
Sorry for my bad english, hope you undestand me
Click to expand...
Click to collapse
Thanks, I will try that after i go back to jb...
Right now I'm on GB, used this tutorial http://forum.xda-developers.com/showthread.php?t=2100642 , network is working but my baseband is still LQ4, everything stock i flash my baseband stays LQ4... weird :/
{
"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 I got back to Jelly Bean LQL, my baseband is still LQ4, I tried flashing the LQL modem.bin via ODIN (on a tar file) and via CWM with a script someone made, still no change