Hi all, this is my first post in this forum.
I own a rooted Samsung Gt-N7000 with KK custom rom.
Before it was rooted, I would experience that if there was some pressure on the phone, because it was in my pocket and I bended my legs, the phone would reboot.
I checked it out manually by trying to apply pressure on the screen or trying to bend it, and the result was always that the screen would flicker for a second and right away reboot.
Now fast forward to after I rooted the phone. At that point the phone wouldn't automatically reboot anymore, but I would pull it out of my trouser pocket and the screen would be off. The only way to reset it would be to hold the power button for an extended time or remove the battery.
I tested it again the same way I did before it was rooted, and it would also give the screen flicker but not automatically reboot anymore.
Next I started to notice that after I manually rebooted, it would reboot normal but as soon as the boot image started to appear it would give the same screen error.
All small lines in different colors or a single horizontal white line which moved over the screen. I could boot into TWRP recovery and the screen would look normal and touch would work, but as soon as I the system boot image appeared the screen would go in error.
This is an example of how my phone screen looked ( this is not my phone)
{
"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 did a clean reinstall from the ROM, whereby wiping everything, but same result.
Then I went into the mount section of the recovery and noticed that EFS-System and data were not mounted. So I ticked them, reboot and everything is fine.
The following times I experienced the error it was exactly same. Rebooting or re-flashing ROM would give no positive result, only after going into the mount tab and tick EFS-system and data and reboot the problem is solved.
Any advise what is happening will be much appreciated.
basjke said:
Hi all, this is my first post in this forum.
I own a rooted Samsung Gt-N7000 with KK custom rom.
Before it was rooted, I would experience that if there was some pressure on the phone, because it was in my pocket and I bended my legs, the phone would reboot.
I checked it out manually by trying to apply pressure on the screen or trying to bend it, and the result was always that the screen would flicker for a second and right away reboot.
Now fast forward to after I rooted the phone. At that point the phone wouldn't automatically reboot anymore, but I would pull it out of my trouser pocket and the screen would be off. The only way to reset it would be to hold the power button for an extended time or remove the battery.
I tested it again the same way I did before it was rooted, and it would also give the screen flicker but not automatically reboot anymore.
Next I started to notice that after I manually rebooted, it would reboot normal but as soon as the boot image started to appear it would give the same screen error.
All small lines in different colors or a single horizontal white line which moved over the screen. I could boot into TWRP recovery and the screen would look normal and touch would work, but as soon as I the system boot image appeared the screen would go in error.
This is an example of how my phone screen looked ( this is not my phone)
I did a clean reinstall from the ROM, whereby wiping everything, but same result.
Then I went into the mount section of the recovery and noticed that EFS-System and data were not mounted. So I ticked them, reboot and everything is fine.
The following times I experienced the error it was exactly same. Rebooting or re-flashing ROM would give no positive result, only after going into the mount tab and tick EFS-system and data and reboot the problem is solved.
Any advise what is happening will be much appreciated.
Click to expand...
Click to collapse
This is a GT.i9300 or i9305, not N7000.
EDIT: I SEE, this is not your phone.
Sorry for my mistake
However, BACK UP ALL DATA Before doing anything.
Then you can root/unroot/reinstall/up or downgrade as much as you like.
I understand the OP is lengthy and since English is not my native language it may be confusing, but I think you missed the point of my question, which is that the phone is rooted already with a custom ROM installed.
I have searched a bit more in the mean time and it sounds as if the EMMC chip is the cause of my problem. I have the affected chip in my phone, but I understand that the available patch is to prevent sudden death. I don't know if the patch also resolves the screen issue.
My understanding is that I have applied the patch by installing the latest Lanchon kernel with TRIM FPBug and have the latest Slimsaber ROM installed which to my understanding has the patch integrated as well.
Please correct me if I'm wrong.
basjke said:
I understand the OP is lengthy and since English is not my native language it may be confusing, but I think you missed the point of my question, which is that the phone is rooted already with a custom ROM installed.
I have searched a bit more in the mean time and it sounds as if the EMMC chip is the cause of my problem. I have the affected chip in my phone, but I understand that the available patch is to prevent sudden death. I don't know if the patch also resolves the screen issue.
My understanding is that I have applied the patch by installing the latest Lanchon kernel with TRIM FPBug and have the latest Slimsaber ROM installed which to my understanding has the patch integrated as well.
Please correct me if I'm wrong.
Click to expand...
Click to collapse
In order to make me read your posts, please quote my message or mention me .
Thanks
Hannah Stern said:
In order to make me read your posts, please quote my message or mention me .
Thanks
Click to expand...
Click to collapse
Thanks for pointing out, but as I said I'm a very recent member, so I will have to learn.
So since you have read my post now, can you please tell me if I'm correct or not in the assumptions I made in my previous post
basjke said:
Thanks for pointing out, but as I said I'm a very recent member, so I will have to learn.
So since you have read my post now, can you please tell me if I'm correct or not in the assumptions I made in my previous post
Click to expand...
Click to collapse
That's no problem
Hannah Stern said:
That's no problem
Click to expand...
Click to collapse
So I have read up more on the issue and the eMMC chip I have installed is the VYL00M rev 0x19.
According to the Cyanogen wiki my chip may be affected with the wear leveling bug.
This problem also occurs in fwrev 0x19, but has not been observed there, and is in any event far less severe than the infamous "Superbrick" secure erase bug, as the user only needs to perform a wipe data/factory reset operation to recover.
There is a patch from Samsung which is here.
https://android.googlesource.com/kernel/omap/+/3c57a612f12b069bbc863ec0c74a26850d76a9e8^!/
Only thing is that it is Chinese to me as how to apply the patch. Can someone help me with instructions how to apply the patch?
basjke said:
So I have read up more on the issue and the eMMC chip I have installed is the VYL00M rev 0x19.
According to the Cyanogen wiki my chip may be affected with the wear leveling bug.
This problem also occurs in fwrev 0x19, but has not been observed there, and is in any event far less severe than the infamous "Superbrick" secure erase bug, as the user only needs to perform a wipe data/factory reset operation to recover.
There is a patch from Samsung which is here.
https://android.googlesource.com/kernel/omap/+/3c57a612f12b069bbc863ec0c74a26850d76a9e8^!/
Only thing is that it is Chinese to me as how to apply the patch. Can someone help me with instructions how to apply the patch?
Click to expand...
Click to collapse
If you Factory-Reset the phone, all data gets completely lost so do a backup before doing anything.
Hannah Stern said:
If you Factory-Reset the phone, all data gets completely lost so do a backup before doing anything.
Click to expand...
Click to collapse
I understand that but with the patch applied my problems should be solved, at least that is my understanding, so I would not need to factory reset the phone anymore.
Problem is that I have no idea how to apply the patch.
Also take note that factory reset and re-flash ROM doesn't solve my problem.
To solve my screen problem I have to go into the mount tab of the TWRP recovery, tick EFS - DATA _ SYSTEM, and reboot.
This works even without factory reset or reinstall the ROM.
basjke said:
I understand that but with the patch applied my problems should be solved, at least that is my understanding, so I would not need to factory reset the phone anymore.
Problem is that I have no idea how to apply the patch.
Also take note that factory reset and re-flash ROM doesn't solve my problem.
To solve my screen problem I have to go into the mount tab of the TWRP recovery, tick EFS - DATA _ SYSTEM, and reboot.
This works even without factory reset or reinstall the ROM.
Click to expand...
Click to collapse
Ok, i see.
Related
I did S-OFF/Root earlier today, but haven't really flashed any new ROM. Stock ROM works good for me now.
Well, the only things I ( and maybe some of you) would like to add to this ROM are the following:
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"
}
and that dialer...
This is pulled from:http://forum.xda-developers.com/showthread.php?t=915159
Hopefully this can be done by someone.
Thanks!
All of the ROMs out now ARE just the stock ROM with the enhancements you want. I don't understand all of this "oh, I rooted, but I want to keep my ****ty stock ROM."
Sent from my HTC Sensation 4G
wow this theme looks great!
subscribed
To make more room, I've moved the files that were here to its own post.
Please go HERE to get the mods that were listed here, and some new ones.
gilbar said:
Hey... I didn't really want to get into moding the phone.apk app (maybe I'll look into it this weekend), but i did the battery percentage one for my own use. Attached are two versions, the Sense battery with Percentages that you requested, and the Circular Battery with percentages (See attached images).
Copy to your SD card and flash in clockwork recovery.
I tried them both on my phone, and they worked fine, but I'm not responsible if they cause problems on your phone. Make sure you nandroid before trying these, just in case.
Enjoy!
Edit: If anyone has any particular requests and you can let me know where to get the necessary image files, I can compile different versions for you. I just hate doing the image work on these mods, that's what takes longer than anything else.
Thanks to Fightspit for the circular icons and xml mods, and CM for ideas on the update script.
Click to expand...
Click to collapse
I applied it, and upon reboot it works, but a wifi error pops up and the whole phone locks up. I had to use recovery to restore my phone.
Shagman68 said:
I applied it, and upon reboot it works, but a wifi error pops up and the whole phone locks up. I had to use recovery to restore my phone.
Click to expand...
Click to collapse
Usually, if it's going to lock up your phone, you'll just see a completely black screen. What do you see when "the whole phone locks up"?
Are you on the stock rom or did you install any other rom or mod prior to this?
gilbar said:
Usually, if it's going to lock up your phone, you'll just see a completely black screen. What do you see when "the whole phone locks up"?
Are you on the stock rom or did you install any other rom or mod prior to this?
Click to expand...
Click to collapse
Yeah...I had installed the Sense version (which you now removed), and the screen just turned black right before getting into the home screen. I'll try the other version now. Stock ROM
secano said:
Yeah...I had installed the Sense version (which you now removed), and the screen just turned black right before getting into the home screen. I'll try the other version now. Stock ROM
Click to expand...
Click to collapse
Hmmm... Can you try something for me? Install the Stock Version to revert, but clear Cache and Dalvik Cache after you flash it and before you reboot.
If you can boot up fine after this, then try flashing one of the other mods and clear Cache and Dalvik after flashing again.
Let me know what the results are.
BTW, the Sense Style version wasn't removed, when I uploaded the Stock version, XDA screwed something up and removed the Sense Version from my post, so I just re-uploaded it.
Thanks.
P.S. - I've just tried all three again to test, from a stock installation, and I've not had any issues. Hopefully we can figure out what your issues are.
Works well on mine with no problems. Had Crystal Pyramid ROM flashed on mine.
Sent from my HTC Sensation Z710e using XDA App
Now that we are S-Off
Why wouldnt you just use the UOT kitchen ?
prateekgujral said:
Now that we are S-Off
Why wouldnt you just use the UOT kitchen ?
Click to expand...
Click to collapse
You could, but since we've gotten root the kitchen has been down (and still is), so I decided to make my own.
its nice! thx for sharing this!
gilbar said:
You could, but since we've gotten root the kitchen has been down (and still is), so I decided to make my own.
Click to expand...
Click to collapse
Agreed...
gilbar said:
Hmmm... Can you try something for me? Install the Stock Version to revert, but clear Cache and Dalvik Cache after you flash it and before you reboot.
If you can boot up fine after this, then try flashing one of the other mods and clear Cache and Dalvik after flashing again.
Let me know what the results are.
BTW, the Sense Style version wasn't removed, when I uploaded the Stock version, XDA screwed something up and removed the Sense Version from my post, so I just re-uploaded it.
Thanks.
P.S. - I've just tried all three again to test, from a stock installation, and I've not had any issues. Hopefully we can figure out what your issues are.
Click to expand...
Click to collapse
Circle battery ulitmatly ended up working for me, I flashed it cleared dalvik-cache and booted the first time I booted it got stuck on the HTC screen. Pulled the battery and rebooted phone came on no issues tried wifi all that fun stuff and it works fine so anyone having issues try that out see how it goes. THANKS gilbar ill be sure to click the actual button when I get home and am on Chrome instead of IE6.......
prateekgujral said:
Now that we are S-Off
Why wouldnt you just use the UOT kitchen ?
Click to expand...
Click to collapse
Because their website still says kitchen is under maintenance everytime I go to it.
I just flashed your Sense mod to my stock ROM. The 1st time, I got black screened, flashed your stock zip, which worked. Then I followed your advice and wiped cache and dalvik after reflashing your sense battery, and it worked perfectly. Maybe you should edit your post to recommend wiping.
groovechild said:
I just flashed your Sense mod to my stock ROM. The 1st time, I got black screened, flashed your stock zip, which worked. Then I followed your advice and wiped cache and dalvik after reflashing your sense battery, and it worked perfectly. Maybe you should edit your post to recommend wiping.
Click to expand...
Click to collapse
Done. Thanks for the advice.
The only reason I didn't add it originally is because it shouldn't be necessary, but I guess it is for some, and is not for others. Oh well.
gilbar said:
Usually, if it's going to lock up your phone, you'll just see a completely black screen. What do you see when "the whole phone locks up"?
Are you on the stock rom or did you install any other rom or mod prior to this?
Click to expand...
Click to collapse
It does go black, then no response from it until I pull the battery. I will try the clear cache, and try again.
Shagman68 said:
It does go black, then no response from it until I pull the battery. I will try the clear cache, and try again.
Click to expand...
Click to collapse
Right, once you get the black screen, you need a battery pull to restart.
Try clearing cache and try again, but I've found that once you get the black screen, the most reliable way to fix the issue is this:
1. Install the Stock Battery Mod.
2. Clear Cache and Dalvik Cache.
3. Boot up... Should boot fine.
4. Install whatever mod you want.
5. Clear Cache and Dalvik Cache.
6. Boot up... should work now.
If you just try clearing cache after you already get the black screen, then for some reason I've found that it might not fix the issue and the above steps might be necessary.
Good luck, let me know what works.
Can someone create a flashable zip to incorporate these? Animated icons!
http://forum.xda-developers.com/showthread.php?t=1038270
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.
So, I unlocked bootloader of my N5. Flashed CWM Touch. Didn't make any kinda backup (I know I'm stupid) and flashed paranoid android. Now I'm not getting any signals on it. Please, I'm in need of desperate help. Any solutions?
EDIT:
Flashed stock image, good as new This should help people who are as stupid as me
Do the usual flash cache.img first. Failing that, reflash all stock images
Sent from my Nexus 5 using Tapatalk
Hello,
Did you wipe data/factory reset, cache, dalvic cache before flashing PA rom.zip?
IF not, then head over to recovery and wipe everything.. Now flash pa.zip and gapps.zip and finally reboot...
Just flashing the pa rom won't touch the efs...
rootSU said:
Do the usual flash cache.img first. Failing that, reflash all stock images
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Trying this
vin4yak said:
Hello,
Did you wipe data/factory reset, cache, dalvic cache before flashing PA rom.zip?
IF not, then head over to recovery and wipe everything.. Now flash pa.zip and gapps.zip and finally reboot...
Just flashing the pa rom won't touch the efs...
Click to expand...
Click to collapse
But, I did not wipe data/factory reset..I went into mounts and storage and wiped everything except sd-card
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
7alvi said:
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
Click to expand...
Click to collapse
Not yet, flash the factory image. That'll get you to a like new condition.
Sent from my Nexus 5
7alvi said:
Flashing Cache didn't work..I'm ****ed am I not? Someone please help me
Click to expand...
Click to collapse
Go to your custom recovery and wipe everything (data/cache/dalvic)... Now flash the rom.zip and gapps.zip and finally reboot and see whether you're able to get a signal or not?
OR
You could use this guide to return to full stock and check... http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
jd1639 said:
Not yet, flash the factory image. That'll get you to a like new condition.
Sent from my Nexus 5
Click to expand...
Click to collapse
I'm flashing the stock image as of now. But, how will it restore my efs partition? By wiping everything in recovery in mounts and storage, didnt i wipe it too?
7alvi said:
I'm flashing the stock image as of now. But, how will it restore my efs partition? By wiping everything in recovery in mounts and storage, didnt i wipe it too?
Click to expand...
Click to collapse
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
rootSU said:
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
7alvi said:
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
Click to expand...
Click to collapse
The 2 lines is are normaly
Try again with admin rights
7alvi said:
I'm flashing stock image but it's kinda stuck on
archive does not contain boot.sig
archive does not contain recovery.sig
It's been like 10 minutes since that. I'm on on old Pentium 4 PC so maybe it's taking time? I dunno!
Click to expand...
Click to collapse
That could be because you extracted the image-hammerhead xxxxx.zip file. dont extract it. it should be there like it is on this picture
{
"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"
}
rootSU said:
Just because the symptoms appear to indicate that you've screwed your efs partition,.doesn't mean you actually have.
Bad /cache and /data have been known to exhibit the same symptoms and flashing cache or returning to stock are known fixes if that's the case
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I officially pronounce this phone as un-brickable. Yes it's fixed. IMEI, baseband siganls everything is back... @rootSU I owe you a beer man. I can't emphasize how ****lessly scared I was...thanx a lot!
No worries
Sent from my Nexus 5 using Tapatalk
Just pumping this thread.
I've gone through a few steps but have ran into a snag.
Heres the synopsis;
My device was randomly shutting down while charging so I decided to factory reset to see if that helped.
When I did the the device entered a boot loop and when I went into recovery it would say can't mount cache etc.
I tried re flashing 5.0.1 Lrx22c but again it got stuck in a boot loop.
I managed to flash 4.4.4 and the device finally turns on.
The only problem is that the phone appears to be without any network connection. Google playstore cannot open and crash's and so does the camera and gallery applications. Adding a sim card does nothing to help.
I'm not sure how to fix this problem and I'm at a point where I need to ask for help. I'm Canadian and bought the device through one of our providers, Rogers, and am starting to think that there is a specific set of 'roger' img's that I need to flash and not the ones from the developers site.
Any input would be much appreciated.
Bump bump ^^
There is no such thing as carrier specific factory images. Did you try reflashing the radio, or a different radio? Remove and reinsert Sim? Might be hardware issue otherwise ..
Sent from my Nexus 5 using Tapatalk
At my wit's end.
I realize it's been 2 weeks since you posted but, in the hope that you are subscribed still Radioman66, I'm curious if you did ever manage to fix/reinject your IMEI; I'm Canadian too btw, though I bought my Nexus 5 through Google Play. I've tried flashing stock everything: bootloader, radio, boot, system, cache, userdata via fastboot; only then did my phone reboot properly, but it still has a habit of crashing/rebooting every so often. No IMEI & no cellular reception thus far, so I can only conclude that there is some data corruption at play here. Fortunately it was easy to find my unique IMEI via a sticker on the inside of the back cover of my Nexus 5, for those who aren't aware.
So I'm in the opinion that the issues of bootloops and my IMEI corruption (dialling *#06# on the dialer calls up a bold IMEI header but no number whatsoever) first occurred when my battery drained to zero. I was using a custom rom at the time, Optipop Dark Deodex with f2fs formatted data and cache partitions, + Multirom & multirom compatible TWRP. I'm at a loss for why the EFS partition and thus IMEI would even be accessed by the phone for writing/reading or how a corruption of the partition could even occur. Perhaps I was receiving a text message right at that very moment it turned off? Perhaps f2fs is to blame, who really knows...main thing is my IMEI is corrupted and I'm left with a smart brick, it being no longer a smart phone.
Anyway, long story short it's been like 2 days of searching around but I think this free tool "Setup DFS 15.01.17.0.zip" at cdmatool dot com (can't post link as a newbie so replace dot with a period) may be the real deal; it's possible to download it without registering i.e. demo mode ( which makes you wait tens of seconds between operations). Despite my general comfort with adb, fastboot, cmd tools in general, the CDMAtool's manual is full of stuff and acronyms I don't really know about yet, like COM Ports and what not but I'm hoping to soon understand this tool and will report back my failures/successes. If anyone would be kind enough to perhaps walk me through what I would need to do, I'd be super thankful!!!t
Welp, cheers to not even knowing about the existence of ESN/EFS/IMEI before this unfortunate juncture LMAO--I will definitely make sure to backup my EFS partitions before flashing custom roms from now on...