Since I personally have dealt with this issue quite a few times recently in my testing and flashing of new ROM's, I figured I'd post it up in case anyone else also had the issue.
Basically this error occurs when your phone has lagfix enabled (file system converted to EXT4) and something (possibly a flash, restore, or factory reset) brings files into the system in the stock RFS format. I.E. If you were to use odin to restore your phone to stock before converting things back to RFS.
Here is a screenshot of what this may look like if you manage to get into CWM, keep in mind sometimes you will actually revert to the stock(blue) recovery but you will see these same errors there if you're having this issue. If you bugger it up as bad as I did, you may not even get passed either recovery - you won't see the samsung logo at all as it'll go right to recovery.
NOTE: Disregard the first two errors, those errors are a result of using an older version of CWM and are normal for that version - you must have the "E: Can't mount..." errors for this to be the issue you're experiencing.
{
"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"
}
Here is the easiest fix. [This is for the Mesmerize.]
1. If you don't have a copy; download the full stock 2.2 odin package (NOT the one with custom recovery, you will need to flash that one AFTER flashing the full stock version as it won't fix the issue by itself) and of course, odin if you don't have it.
2. Load up the .pit in the .pit slot and the .tar.md5 in the PDA slot and get your phone into download mode. (I usually pull the battery, plug it in and hold volume down, there are other methods) Also check the "repartition" box.
3. Once odin see's your phone (look for a yellow COM: box) hit start and it will flash the stock files to your phone.
4. Put the battery back in and boot the phone up, we need to get the file structure converted back to RFS and you won't be able to do so through normal means.
5. Create an empty file (In windows just erase the extension) and name it "disable lagfix" no extension
6. Download QT ADB from here (or just use ADB), and move the file from your PC to the Voodoo folder on your SD card. Reboot your phone, you should hear the lagfix being disabled (robot chick voice)
7. After that is complete, all your stuff will be converted properly - but if you don't flash a clean full OS again (like you did in the first few steps) you will revert to these errors once lagfix is re-enabled. So, repeat steps 1-4, and don't forget if you want the custom recovery you can odin flash that package AFTER you use the full stock package, this is just to ensure all your files are clean and installed properly.
8. You now have a clean phone with everything in the proper format and working properly, so you know what to do from here .
help please
i flubbed...flashed before i read with odin...my phone is giving me the cant mount and i'm not sure i'm doing your directions right...tried several times and nothing...the disable lagfix and adb part has me comfused
I think when I wrote this I missed a step, right before step #5 you may need to flash a voodoo kernel so that lagfix can get disabled through the instructions in step 5 and on.
When I had this happen to me I just odined the stock 2.1 files and checked the repartition box. Fixed me right up. Going to stock 2.2 didn't fix my problem tho.My dumbass tried to odin ec10 stock with root and recovery from cm7 with ext4 (voodoo) enabled. I wanted to reset my phone you know...haha yeah thought I done ****ed myself
Sent from my SCH-I500 using XDA Premium App
The custom root and recovery one didnt work for me either, used the other. I've never gone to 2.1 but whatever works
Sent from my SCH-I500 using XDA Premium App
droidzach said:
When I had this happen to me I just odined the stock 2.1 files and checked the repartition box. Fixed me right up. Going to stock 2.2 didn't fix my problem tho.My dumbass tried to odin ec10 stock with root and recovery from cm7 with ext4 (voodoo) enabled. I wanted to reset my phone you know...haha yeah thought I done ****ed myself
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Oooh, flashing 2.1 fixed all my RFS/EXT4 issues! Thank you!
First of all let me thank you for sharing this.
I've got the same error that you listed minus the "missing bitmap" part.
My trouble started when trying to Odin back to EB11 froyo from phidelt82. (I had a copy saved) I believe I'm having this issue because I used a different version of odin than the one I usually use, and the Re-Partion box was checked. I didn't notice it was checked until it started.
Since then I haven't been able to get past the recovery.
I can however flash recoveries, kernels, and most roms,(via odin or zip) but I never even see the samsung logo on reboot. It just goes straight to the recovery.
I've created the file disable-lagfix and dropped it in voodoo folder.
At this point I can enable/disable voodoo all day long, but after disabling and flashing eb11 or ee25 stock immediately after I still get the Can't mount errors.
(they look a little different in stock recovery, but I'm pretty sure it's the same error)
I've done this several times both with Re-Partitiion checked and unchecked to no avail.
Right now the error I'm getting is "E:Can't mount /cache/recovery/command" log, log, last_log, last_log.
I've been working on this since Sunday and I'm nearly at my wits end.
If anyone out there can tell me if I'm just missing something or if there's another procedure. I would very greatly appreciate it.
PimpFinger said:
First of all let me thank you for sharing this.
I've got the same error that you listed minus the "missing bitmap" part.
My trouble started when trying to Odin back to EB11 froyo from phidelt82. (I had a copy saved) I believe I'm having this issue because I used a different version of odin than the one I usually use, and the Re-Partion box was checked. I didn't notice it was checked until it started.
Since then I haven't been able to get past the recovery.
I can however flash recoveries, kernels, and most roms,(via odin or zip) but I never even see the samsung logo on reboot. It just goes straight to the recovery.
I've created the file disable-lagfix and dropped it in voodoo folder.
At this point I can enable/disable voodoo all day long, but after disabling and flashing eb11 or ee25 stock immediately after I still get the Can't mount errors.
(they look a little different in stock recovery, but I'm pretty sure it's the same error)
I've done this several times both with Re-Partitiion checked and unchecked to no avail.
Right now the error I'm getting is "E:Can't mount /cache/recovery/command" log, log, last_log, last_log.
I've been working on this since Sunday and I'm nearly at my wits end.
If anyone out there can tell me if I'm just missing something or if there's another procedure. I would very greatly appreciate it.
Click to expand...
Click to collapse
Ok, the can't mount "log" and such errors might be a little different - were you on or are you on an MTD rom? (miui or CM7) because those errors will show if you're using the 3 button method to get into recovery while one either of those two roms. If you can, jump on IRC and get some help, we're around and more than willing to walk you through.
http://webchat.freenode.net/
channel: #samsung-mesmerize
Just wanted to say I got my problem fixed following the advice of bdemartino to flash EE23 via odin.
The other builds I was trying to flash were not full builds.
Thanks again! I was ecstatic after my phone finally rebooted!
Is it safe to say that anyone who has odined back to stock has lost all data?
I think there has to be a way to push an rom that uses the lagfix and won't go into an endless boot cycle.
Anyone else?
Thainfamous20v said:
Is it safe to say that anyone who has odined back to stock has lost all data?
I think there has to be a way to push an rom that uses the lagfix and won't go into an endless boot cycle.
Anyone else?
Click to expand...
Click to collapse
Yes you will lose all data.
If you figure it out let us know, but no it doesn't seem to be possible.
droidzach said:
When I had this happen to me I just odined the stock 2.1 files and checked the repartition box. Fixed me right up. Going to stock 2.2 didn't fix my problem tho.My dumbass tried to odin ec10 stock with root and recovery from cm7 with ext4 (voodoo) enabled. I wanted to reset my phone you know...haha yeah thought I done ****ed myself
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
going back to 2.1 was the only thing that worked for me too
I'm trying to make a clean reinstall to come back to as well
I've been running cm7. For a while now and tried to do something and caused the e can't Mont problem
I'm on a showcase from cellsouth
I can still use this adb reformatted fix right
If not I read that I can flash a full build pit and tar check repartition boot then Odin a cwm and flash an rfs reformatter zip to fix my problems
Is that true too
Related
Hello All,
I am a new SGS4g user and have had the phone for about a month now. I've been looking into flashing, and have looked over a large number of forum posts and such to help guide me through what seems to be a difficult process. the guide i've been most looking into was this one
http://forum.xda-developers.com/showthread.php?t=1122508
I'm trying to flash the ICBINB ROM onto my phone due to all the good things I've read about this particular rom.
I finally decided that I would do it today, but when I went to wipe the data in Clockwork orange, the process got stuck at a file named Android.Secure. The post above mentioned something about this, but I wasnt too sure how to avoid it. I ended up restarting the phone, finding that it had gone to stock, ran the clockwork restore and found that in the restoration it also got stuck on this same file. After several minutes of freaking out and panicking, I did another force restart and found that thankfully my phone is back to where it was.
So I was wondering if anyone could guide me to another post, or help me to find a solution to this problem. And, if you could also help me find a more detailed guide because now I'm scared to do anything to the phone at this point without further info.
Thanks for any and all help!
Did you try just following the instructions in the post for ICBINB?
http://forum.xda-developers.com/showthread.php?t=1157593
The link you posted is to the NOOB's guide, which is cool, but it specifically mentioned ROM Manager. Did you install that or anything?
It's hard to say without a bit more information as to what you were doing, what step you were on, what other changes you may have made to the phone first. Can you provide some details?
Thanks for the response stephen,
Well what I had done up to that point was just create a recovery on ROM manager. Then I booted into clockwork and began the wipe of data, as the steps in the ICBINB steps said. It was here that it got stuck.
I have an update though. I tried again flashing this time through Rom Manager. When I did it, the Rom manager did its stuff and then began a reboot, where the phone got stuck on the opening screen (where it says galaxy s 4g and has the S logo). I shut it down, and tried to restart it and when I did, a voice started says `convert system partition, system not available`` and would get stuck. I pluged into odin and selected-repartition. Now, if I reboot I go into a red Voodoo lagfix recovery v. 3.0.2. Now as far as I know, I never put in a lagfix, so I have never seen this screen before. When I select the reboot option, it just gets stuck again and the voice says the previous statment once more. So what do I do from here?
From what I've read on this forum ROM Manager doesn't seem to work well with our phone. I can't speak from any experience with it, though.
The voice you heard is Linda. That's the voice you hear when voodoo lagfix is converting your partitions from the rfs filesystem to the ext4 filesystem. It sounds like something got hosed in the process of what you were doing.
Boot into voodoo recovery, disable voodoo across the board to be safe, and see if the phone boots. If not, try following my directions above to get on a stable GB ROM.
If you're able to ODIN the ROM & boot, then you can use the phone & flash other ROMs and whatnot.
If you're able to ODIN the ROM but it gets stuck in a loop or has an error, more than likely the voodoo is still enabled and this ROM can't use ext4. You would then need to ODIN one of drhonk's kernels (http://forum.xda-developers.com/showthread.php?t=1194032). Use the KG4 one. It comes with CWM Red, voodoo, and root.
Once you flash it you should be able to utilize the voodoo menu in CWM to enable or disable voodoo.
OKAY now I think I effed up royally.
I followed the steps, but then I tried to upgrade to ICBINB GB and now clockwork wont start. The samsung galaxy s4g logo will pop up, then it will go away. Occasionally I will get a full pixelated screen. Is there any recovery from this?!!!??
and it keeps cycling through this over and over again
If u can get to download mode ur fine...get one of the Odin leaks fo gb...put file in pda..flash...then get kj1 Drhonk kernel with voodoo...follow directions to do that...flash...should hear Linda...then, any ROM u choose to flash I'd put it directly on to ur sd...do NOT get ROM manager for anything instead goto market and get qick boot..once u do that...may the phone be with u. I'm nowhere near an expert but this saved my phones more than once.
Sent from my SGH-T959V using xda premium
Ps..if an leak gives u booy loop..three button recovery, factory reset SHOULD set u right on leak ROM
Sent from my SGH-T959V using xda premium
UPDATE
I have done something (not too sure what) and have been able to get into the main phone, however I am unable to get into Clockwork because whenever I do it is just Pixelatios. I keep seeing pixelations randomly at startup. It looks like I have the ICBINB theme and stuff, but I kinda want to go back and undo this and go to my saved backup. Any advice?
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?
{
"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"
}
SILVER ROM ICS Q&A THREAD​
Please keep this thread on topic
no trolling
no complaining
no arguments
valid rom related questions and comments are welcome
Is TiBu working yet?
yes i just need to reupload . its not working in the link i have currenty posted i will change the link once i upload
silver03wrx said:
yes i just need to reupload . its not working in the link i have currently posted i will change the link once i upload
Click to expand...
Click to collapse
Thank you bro. Can I just reinstall TiBu from GP? And thanks for all your hard work..You rock..
no it wont work. i accidentally put the preload preconfg app back in wasnt paying attention coppying apps. lol it happens
but thats what causes force closes and tibu to not work
its fixed now
new link will be in op in about an hour
how do you take your screen captures? The app i normally use ShootMe takes pictures that appear to be red washed.
Never mind. Figured it out.
Good idea on the Q&A thread! Of course most people will glaze over that and post questions in the other thread, but it's a good idea.
Only problem might be that the post count will go down for the thread in the dev section if people come here instead, and you may get moved down the list onto page two--behind inferior roms...
What does the Silver Rom flashable theme consist of exactly? Is that what is in the preview pictures or does it look different?
Thank you silver
Sent from my SAMSUNG-SGH-I727 using Tapatalk
i flashed ICS3 but i cant seem to download anything no links work anywhere to download. says download starting then when i check on it says it failed. is there anything i can do?
Got collectiveics3 working
I had been having boot loop problems, and when I finally got it running the acore FC was killing me because it ground everything to a halt over and over again.
I flashed Superlite 4.5, which wiped and then ran OK but I got ambitious and flashed the UCALC5 modem and it turned into a nightmare... every touch of the screen would freeze me up for a minute or more.
I reflashed the romracer kernal and the UCALC4 modem, then reflashed collectiveics3 and that gave me a working ics, but the apex crashes were making life difficult (trying to log on to the market took me over an hour because the keyboard kept dissapearing, but I finally got there and updated Apex and TiBu and reinstalled the TiBu key... that let me restore the stuff I lost to the superlite flash... but something didn't play nice with the ROM.
Reflashed superlite, reflashed collectiveics3, re-updated Apex and TiBu, and then rloaded most of my apps from the maeket, restored data ONLY from user apps (and was picky about which ones I chose) and I can hapily say everything seems to be working properly for me...
In the interest complying with the Q&A for this thread... here's a question.
I was in a strong LTE area for a couple hours but couldn't find where to tell the phone to use it... The settings on the Rogers GB ROM are self evident... where do I find them on this one?
I am anxiously awaiting the updated link, but headed to a cottage that's off the grid and nowhere near cellular service in an hour or so, so I guess I'm in no hurry until Monday now... may as well take the pressure off so he can make it absolutely perfect.
Jamie
@Silver
Does this ROM have the option in the settings menu to turn off LTE? I think that option in your GB ROM saved me some battery life, and I would love to see it in this ROM. This ICS kernel or radio seems to really suck battery, I'm glad I have the 15 toggle to turn off data completely when I'm at work.
another Q what's the difference between the theme link on Post #4 of DEV Thread and the ROM that will be posted in OP?
Here http://www.theandroidcollective.org/i727/SilverRom/silverics.zip
Some thing i have have concluded about the ics leak. And my rom instructions
Use cwm 5.0.2.6 and only this version. It is in the dev section in a cwm recovery.tar
Works everytime for me on this cwm version
Do not use rom manager to install it. Our device is very similar to the t989 but there is something different to where the skyrockrt will always have recovery issues. Unless we get our own specific for us.
Do not wipe anything....just flash no wipes.
Wipes cause bootloops in my rom.
If u abide by these directions. You will be all good.
Enjoy
Still not finished the rom but it is a work in progress as this was built from a leak eith many bugs.
Its fast and smooth. New apex version...new live wallpapers.
Included usefull apps.
boot loop help
i installed zip from sd card and now my phone will not boot up. it shows the samsung logo and then powers off or shows logo then restarts. can someone please help me figure this out. thank you
theazad23 said:
i installed zip from sd card and now my phone will not boot up. it shows the samsung logo and then powers off or shows logo then restarts. can someone please help me figure this out. thank you
Click to expand...
Click to collapse
Boot back into cwm manualy and reflash the zip again. Did you wipe anything in cwm before you flashed?
Sent from my SAMSUNG-SGH-I727 using Tapatalk
i think it did. honestly this is my first time flashing my phone so im not surprised i screwed it up.
i just tried installing the zip again and it says it will fully wipe. it didnt give me an option to choose to wipe or not. how can i install it without wiping?
theazad23 said:
i think it did. honestly this is my first time flashing my phone so im not surprised i screwed it up.
i just tried installing the zip again and it says it will fully wipe. it didnt give me an option to choose to wipe or not. how can i install it without wiping?
Click to expand...
Click to collapse
dont wipe anything manually. Just flash silvers ics rom. It will wipe what it needs to. Do that and if it bootloops again let us know.
Did tou ever get to the bootanimation during the first boot after flash?
Sent from my SAMSUNG-SGH-I727 using Tapatalk
ok then i did it right the first time. i didnt manually wipe anything. i just went to install zip from sd card and installed it. after it was installed it went to the bootanimation and maybe completed half of it. then it restarted and started looping and then the bootanimation would not come back. just the samsung logo looping. i ended up going back to stock so at least i got my phone working again
for this rom to work do i need to be running 4.0.3? when i tried to install it i was running 2.3.5. could that have been the problem?
theazad23 said:
ok then i did it right the first time. i didnt manually wipe anything. i just went to install zip from sd card and installed it. after it was installed it went to the bootanimation and maybe completed half of it. then it restarted and started looping and then the bootanimation would not come back. just the samsung logo looping. i ended up going back to stock so at least i got my phone working again
for this rom to work do i need to be running 4.0.3? when i tried to install it i was running 2.3.5. could that have been the problem?
Click to expand...
Click to collapse
You should be able to come from gingerbread no problem. Get a fresh download of the rom and try again.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Here is the updated version. Fixed titu issue and market issue. All is well
U will get an apex fc on first boot. Just update it on market.
Sorry for the delay i changed the theme 5 times. But here os the rom.
Theme changes will be made via flashable theme from here on
http://www.theandroidcollective.org/i727/SilverRom/03silverics.zip
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!