Hey everyone, so I'm trying to figure out if there is anythiNg I can do...
Every time I reboot my phone with any TW based Ron I get the following message
{
"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"
}
Many, many flashes ago I lost my efs files, I know very noob move... I have read that this is most likely the cause, but I can't find much on the problem, my phone is otherwise usable but I feel like it lags and that's the only thing I might think is the culprit.
Whenever I flash Cyonagenmod LP rom, it runs smooth as butter, but for every TW based rom it lags like a MF...
Is there anyway of getting out of this mode, or since I lost my EFS folder, I'm now F*&×?
If u lost efs and didn't back up in twrp ur done.. Sorry
BAD ASS NOTE 4
You can try Kies emergency recovery. I am not sure it works on a Note4 but it worked on my note 2 in the past.
Sent from my SM-N910T using XDA Free mobile app
Thanks for answering guys, now which functionalities would be lost without the EFS?? Also what I don't get is why when I'm on LP bases Rom there are no issues...
As far as warranty is concerned, I'm not worried I have Jump coming up in a few months so I'll be moving on anyways.
Have you Odin'd to stock ank or anj + Factory reset?
Yes, I just did... I was on LP and Odin to stock, the message started coming up, then I rooted and flashed firekatv11x and still... I have had this issue since the first time I flashed a custom rom...
Yeah the same happened to me it shows factory mode on wifi is turning off ....efs folder empty but imei is showing up network is working too and etc... I've tried restore the efs with twrp but still empty even thou its says successfully restored .... in stock recover show failed to mount efs.... I've tried efs pro with samsung tools just to get out of factory mode but no success .... it is actually not a big deal its just lagging sooo much now when i type something i feel like throwing the phone through the window everything is lagging and so slow.... is there actually a solution to fix this or buying a new phone its perhaps the best thing to do I'm tired of this stuck for 4 days .....
lamartino said:
Yeah the same happened to me it shows factory mode on wifi is turning off ....efs folder empty but imei is showing up network is working too and etc... I've tried restore the efs with twrp but still empty even thou its says successfully restored .... in stock recover show failed to mount efs.... I've tried efs pro with samsung tools just to get out of factory mode but no success .... it is actually not a big deal its just lagging sooo much now when i type something i feel like throwing the phone through the window everything is lagging and so slow.... is there actually a solution to fix this or buying a new phone its perhaps the best thing to do I'm tired of this stuck for 4 days .....
Click to expand...
Click to collapse
From what I was told in the past. When u first root phone u should do a twrp of efs only. Save to a location that u won't touch. Next you should download a efs back up tool and make a back up and save it to pc just in case. Then flash away and you should not have to do a efs back up in twrp again.
BAD ASS NOTE 4
obiaquino said:
Hey everyone, so I'm trying to figure out if there is anythiNg I can do...
Every time I reboot my phone with any TW based Ron I get the following message
Many, many flashes ago I lost my efs files, I know very noob move... I have read that this is most likely the cause, but I can't find much on the problem, my phone is otherwise usable but I feel like it lags and that's the only thing I might think is the culprit.
Whenever I flash Cyonagenmod LP rom, it runs smooth as butter, but for every TW based rom it lags like a MF...
Is there anyway of getting out of this mode, or since I lost my EFS folder, I'm now F*&×?
Click to expand...
Click to collapse
*1
---------- Post added at 12:41 AM ---------- Previous post was at 12:31 AM ----------
obiaquino said:
Hey everyone, so I'm trying to figure out if there is anythiNg I can do...
Every time I reboot my phone with any TW based Ron I get the following message
Many, many flashes ago I lost my efs files, I know very noob move... I have read that this is most likely the cause, but I can't find much on the problem, my phone is otherwise usable but I feel like it lags and that's the only thing I might think is the culprit.
Whenever I flash Cyonagenmod LP rom, it runs smooth as butter, but for every TW based rom it lags like a MF...
Is there anyway of getting out of this mode, or since I lost my EFS folder, I'm now F*&×?
Click to expand...
Click to collapse
Hi Mate, i have same problem. IN addition, s health freezes, fingerprint not working, lagging when typing, video freezing, wifi memory loss ( have to enter pass key after every reboot).
I guess the only solution now is to avoid stuck rom since LP based roms works flawlessly. Till official LP is out..
nunclud said:
*1
---------- Post added at 12:41 AM ---------- Previous post was at 12:31 AM ----------
Hi Mate, i have same problem. IN addition, s health freezes, fingerprint not working, lagging when typing, video freezing, wifi memory loss ( have to enter pass key after every reboot).
I guess the only solution now is to avoid stuck rom since LP based roms works flawlessly. Till official LP is out..
Click to expand...
Click to collapse
Yeah as far as I'm concerned we all have the same problem
You cant lose your efs just flashing roms.
Something else form the story is missing. Your efs just doesn't erase unless you accidentally deleted the folder...or you were trying to unlock and you did not back up your original efs first.
But no, trust me it doesn't work that way. You specifically have to back up the EFS for reasons. The only way to get the efs back is to use a similar efs. Which is not exactly a good idea.
bvzxa3 said:
You cant lose your efs just flashing roms.
Something else form the story is missing. Your efs just doesn't erase unless you accidentally deleted the folder...or you were trying to unlock and you did not back up your original efs first.
But no, trust me it doesn't work that way. You specifically have to back up the EFS for reasons. The only way to get the efs back is to use a similar efs. Which is not exactly a good idea.
Click to expand...
Click to collapse
Yeah well I thought the same maybe I didn't something I didn't realize but all I did was flashing a rom right after flashing all my carrier bloatwares changed to bloatwares from another carrier I thought it isnt a big deal csc code will do but not after many tries to get my csc code back still didn't work so I thought maybe because rogers (the carrier my phone is within) didn't had lollipop realesed back then its maybe that after couple days I realized the rom is slow lagging too much still didn't know about the problem… so I went back to stock trying again the csc code and then I realized something is wrong in recovery showed failed to mount efs so I did little research tried wipe out everything includes internal storage with twrp before that restoring my back up I did before I flashed the rom the weird ing is I can restore everything expect system data chaches and even after restoring efs the folder is empty… I thouth first my efs was corupted but in that case I would have blank imei no access to making calls or so but everything is working its just laggy wifi after reboot turns off guves this pop up notification about factory mode on and the empty efs folder with thaf failed to mount efs in stock recovery notice
I just lost the EFS and have no idea how, it had to be while flashing, I came from LG and HTC, never never had issues with flashing roms... i never had to back up EFS, as a matter of fact, i had no idea what it was before this whole problem... so I thought it would be the same process, just flash away....
In the beginning everything was all good, but then I flashed the unofficial LP rom, played around with it for a while... I couldn't deal with the heating problems, so decided to go back TW and that's when everything went haywire.
As soon as LP got picked up by CM I went to that, because the lag on TW is horrible I couldn't deal... now just this week I was like well let me try TW for better battery life...
But I'm about to go back to LP, I can't even watch a video without constant lag, can't go through a sentence without lag... horrible and the only thing I can think off that's causing it, is the freaking Factory Mode!!
Sorry for the long as post, but I see that many ppl are on the same boat... there has to be a way to fix it.
Ps. I'm on Firekat v11x so I know it's not the rom that causes the lag.
Sent from my SM-N910T using XDA Free mobile app
Unfortunately I have tried out almost everything expect the adb shell over writing of mmcblk0p3 or 1 not sure now which one is it but 4 some resone I was unable to get it run… so I might keep trying make it work and if that wont fix it I think its worthless to try anything else… because whatevery you try I think I already tried it but still a little help would be great
Flash back to a stockish rom and exchange with Samsung.
Or
Odin to stock + Factory reset and exchange with Samsung.
Ok Ill take my post back...this happened with my Sprint S2 coming from CM9 and going back to stock android. With the Sprint S2 there was the eeprom issue with the bug inside the Exynos processor (been a while) and it messes up the efs and eeprom and now it's dead. TW performance varies, however I have gotten over stock android since I occasionally get my hands on a nexus device to run. since I have had my Note 2 I just stick with TW roms. It's just lately in my line of work I get a lot of people who mess up their efs trying to unlock or fix imei problems. Pleas forgive my rashness.
No EFS Folder
Hi
I had the same issue with my note 3. You just lose wifi. That was the only noticeable thing which wouldnt work. But my note 3 used to work on some AOSP roms (Wifi too).. Try loading an AOSP rom and see if that helps with the wifi.
There are online postsdetailing the steps to repair this (for Note 3) . Never worked for me, but a lot of people replied it worked for them. I also saw an online repair service which would fix that for 60 bucks
bvzxa3 said:
You cant lose your efs just flashing roms.
Something else form the story is missing. Your efs just doesn't erase unless you accidentally deleted the folder...or you were trying to unlock and you did not back up your original efs first.
But no, trust me it doesn't work that way. You specifically have to back up the EFS for reasons. The only way to get the efs back is to use a similar efs. Which is not exactly a good idea.
Click to expand...
Click to collapse
I have lost EFS just by flashing. It can happen when going from AOSP to TW if you don't get a good clean wipe, or if either of the ROMs was not compiled correctly, or if you get a bad download.
Has anyone tried using Kies. When this happened on my Note 2 there was an "emergency recovery" feture in Kies that allowed you to restore the stock firmware. If you can't do it in Kies youself I believe the Samsung rep at Best Buy should be able to Emergency recover your device. It basically flashes it back to the stock software that came on it when it was built.
How to Unbrick or Restore your Samsung Firmware with Kies, Universal Met...: https://youtu.be/LqoX7wNhotk
Fixed my Note 2 no problem. I had to re-root it and do some ODIN flashing to get it back to the firmware I wanted but it fixed the phone.
Also just curious, in TWRP it defaults to making a backup of your EFS when you backup your ROM, Is there a reason why you would have unchecked that box. You should ALWAYS keep a backup of the stock ROM or a minimal the EFS from it.
Sent from my SM-T900 using XDA Free mobile app
ShrekOpher said:
I have lost EFS just by flashing. It can happen when going from AOSP to TW if you don't get a good clean wipe, or if either of the ROMs was not compiled correctly, or if you get a bad download.
Has anyone tried using Kies. When this happened on my Note 2 there was an "emergency recovery" feture in Kies that allowed you to restore the stock firmware. If you can't do it in Kies youself I believe the Samsung rep at Best Buy should be able to Emergency recover your device. It basically flashes it back to the stock software that came on it when it was built.
How to Unbrick or Restore your Samsung Firmware with Kies, Universal Met...: https://youtu.be/LqoX7wNhotk
Fixed my Note 2 no problem. I had to re-root it and do some ODIN flashing to get it back to the firmware I wanted but it fixed the phone.
Also just curious, in TWRP it defaults to making a backup of your EFS when you backup your ROM, Is there a reason why you would have unchecked that box. You should ALWAYS keep a backup of the stock ROM or a minimal the EFS from it.
Sent from my SM-T900 using XDA Free mobile app
Click to expand...
Click to collapse
Will give this a trial
have you guys tried this fix http://zidroid.com/how-to-exit-factory-mode-for-samsung-galaxy-devices/
Related
Hey guys,
I'm fairly new to the modding of Android phones (my previous phone was a TYTN II) and I'm having some problems restoring my backups via Clockwork mod (which is a bit of a pain in the ass for me, as I think you understand).
Ive tried to flash my phone and stuff, but I can't download apps from market/start google talk (I know this is related to eachother) when I have a mdc rom installed. This is not really the problem I'm asking a solution for, but the real problem is, that I can't go back to my old rom and stuff. I have rooted my phone, installed CWM, made a backup, but somehow it keeps freezing at the loading screen of the phone whenever I have restored a backup and reboot the phone.
Atm I have resetted my phone with NVFlash, I have not yet innstalled anything but I still have a backup which I'd like to restore. This is my situation:
LG-P990: Android 2.2.2, Baseband 1035.21_20110315 (I updated this with Paul's update), Kernel 2.6.32.9, Build: FRG83G, LGE version: v10b.
Anyone has an idea what I'm doing wrong? Did I miss a step in the process? Please help me out!
I'm no expert, so you should probably wait for one of them, but I had a similar problem and it's important to do a wipe before installing the ROM. (There's two wipe options, run them both)
novackus said:
Hey guys,
I'm fairly new to the modding of Android phones (my previous phone was a TYTN II) and I'm having some problems restoring my backups via Clockwork mod (which is a bit of a pain in the ass for me, as I think you understand).
Ive tried to flash my phone and stuff, but I can't download apps from market/start google talk (I know this is related to eachother) when I have a mdc rom installed. This is not really the problem I'm asking a solution for, but the real problem is, that I can't go back to my old rom and stuff. I have rooted my phone, installed CWM, made a backup, but somehow it keeps freezing at the loading screen of the phone whenever I have restored a backup and reboot the phone.
Atm I have resetted my phone with NVFlash, I have not yet innstalled anything but I still have a backup which I'd like to restore. This is my situation:
LG-P990: Android 2.2.2, Baseband 1035.21_20110315 (I updated this with Paul's update), Kernel 2.6.32.9, Build: FRG83G, LGE version: v10b.
Anyone has an idea what I'm doing wrong? Did I miss a step in the process? Please help me out!
Click to expand...
Click to collapse
please check if the DATE in your settings is correct. the rom I had previously installed was set to MAY and this made it impossible to use gtalk and download roms.
yeah sounds silly, but worth checking
ah well since you have reset already. but maybe you get back in the same situation at one time.
Thanks for the quick replies.
@Marco_ch: I already tried the date problem, literally went thru 100 of pages to find out what the issue was with the gtalk, but nothing helped, so I'm guessing I made a mistake with the rooting or something...
I already reset, but this is the third time I've reset, I've already tried flashing my device 3 times and each time I end up not being able download apps.
@Jakkelomme: As far as I know there is only 1 wipe option? Reset factory settings? I always do that before I install a rom yes.
well I had the same problem (gtalk, market) but I gave it another shot with this:
http://romkitchen.org/lg/?s=generator
its running brilliantly on my device. have you tried that one yet?
Tried it a few days ago, when it was anotehr version, might try it again now, thanks. Which options do you suggest (I'm not that much of an expert )
Edit: Though i wish someone had a solution for me not being able to restore via CWM!
oh you dont want suggestions from me - I have that device for a couple of days only and dont even know how to properly make a backup
but I chose the following:
EXT 4
Pauls Kernel
Left out all the LG Stuff as I find it kinda useless and laggy
good luck!
marco_ch said:
oh you dont want suggestions from me - I have that device for a couple of days only and dont even know how to properly make a backup
but I chose the following:
EXT 4
Pauls Kernel
Left out all the LG Stuff as I find it kinda useless and laggy
good luck!
Click to expand...
Click to collapse
Did everything you asked, installed new version of Romkitchen with the stuff you suggested... Still doesnt download appss. Still stuck at "Starting download...". Help, anyone?
Nevermind guys, I fixed it. Turned out the problem WAS with date & time. My provider made the date 12/05/'11 instead of 12/04/'11. It was why I couldnt download from the market. Thank you all for helping out anyway
After upgrading from V4.0.3 to V4.0.4 (from kies), the main scheen shows the annoying box (only on the 7 main screes, not elsewhere) with some H/W info as screen shot below, I tried to manually download the ROM, perform double wipe and reload the ROM agian, the issue remains, has any one encountered the same problem, any one has any ideas can help me with this ? :crying:
{
"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 didn't experience this to my DXLR5 4.0.4.
Sent from my GT-N7000 using Tapatalk 2
ryn888 said:
I didn't experience this to my DXLR5 4.0.4.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I did surf the internet for a while but not able to find any similar problem as I have, that's why I post here to seek some expert support ...
:crying:
I need some help.
These should be someone/expert can sort this out ..
HELP / HELP !!
This is due to broken EFS
If you have EFS backup, restore it.
Otherwise Reflash GB ROM, someone reported it worked by flashing GB ROM with wipe cache and data.
dr.ketan said:
This is due to broken EFS
If you have EFS backup, restore it.
Otherwise Reflash GB ROM, someone reported it worked by flashing GB ROM with wipe cache and data.
Click to expand...
Click to collapse
Thanks, Ketan,
I don't have EFs backup,,,
But when I read some other articles, it says the lost of EFS will have some symptoms , ie: IMEI gone (I can check my IMEI by "*#06#"), no signal (I am OK to make/receive the call)... etc, it seems I may not have EFS issue ??
Also, I did try to downgrade to V4.0.3 when I encountered the issue on V4.0.4, everything is fine
At first I thought there is something wrong with the V4.0.4 ROM (my first upgrade was from Kies directly), so I manually download the ROM (actually I've compared the ROM from Kies and the one I downloaded, they are identical),,,anyway, I used Odin to upgrade again, and the problem comes up again..
that is to say, with V4.0.3, the phone has no any issues, with V4.0.4, the only issue is the annoying H/W info box shown on the 7 main screens....
Any more ideas or detail instruction would be very much appreciated ...
As i said its just broken efs, where still you dont lose imei. But you can try this
Downgrade to lower version where there is no issue, take efs backup.
Then update to newer version and restore backup when issue appear back.
Sent from my GT-N7000 using xda premium
am getting annoyed by another problem. The WiFi switches off automatically and gets connected when i touch the screen..
This is annoying me as all the updates happen while the display is off and it is getting those using 3G and not the WiFi...
Is it just me ?
I did not install any app after the upgrade form 4.0.3 to 4.0.4
Just go to.setting - wifi -advance - keep wifi on during sleep - Change to 'always.'
Then wifi.wont.auto off.
Sent from my GT-N7000 using xda premium
cool.. almost forgot that .. How the Heck did it change to Never.. does the update change the settings ??
One more thing .. now my Apex launcher restarts everytime .. i remember there was a place where we can change the no.of apps running in the background .. Can you tell me where this is ?
You mean
Setting -development -restrict number of background process?
Sent from my GT-N7000 using xda premium
any option like that in Stock ROM which might have been changed by the upgrade ?
As said above?.i have edited
Sent from my GT-N7000 using xda premium
just checked and it is set to default ... no changes there .. humm.. Thanks Again Ketan.. will look for alternate Launchers.. Any suggestions ?
or should i just take the jump and go for Paranoid Android
dr.ketan said:
As i said its just broken efs, where still you dont lose imei. But you can try this
Downgrade to lower version where there is no issue, take efs backup.
Then update to newer version and restore backup when issue appear back.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Hello, Ketan,
I followed your suggestion to downgrade to V4.0.3, of course, it is problem free menaing no annoying box shown on main screen
Then I root to install HC-Ktool and backup efs
and then unroot and upgrade to V4.0.4 again, the annoying box come up ...
Then I root again to run HC-Ktool and restore EFS, and restart
without luck ,,, the annoying box is still there,.,,, any thoughts ?
easternpig said:
Hello, Ketan,
I followed your suggestion to downgrade to V4.0.3, of course, it is problem free menaing no annoying box shown on main screen
Then I root to install HC-Ktool and backup efs
and then unroot and upgrade to V4.0.4 again, the annoying box come up ...
Then I root again to run HC-Ktool and restore EFS, and restart
without luck ,,, the annoying box is still there,.,,, any thoughts ?
Click to expand...
Click to collapse
tell me the procedure you are following in flashing the roms and please try to downgrade to a safe gingerbread rom then root it or use pre-rooted gb rom from DR.KETAN'S GUIDE.
easternpig said:
Hello, Ketan,
I followed your suggestion to downgrade to V4.0.3, of course, it is problem free menaing no annoying box shown on main screen
Then I root to install HC-Ktool and backup efs
and then unroot and upgrade to V4.0.4 again, the annoying box come up ...
Then I root again to run HC-Ktool and restore EFS, and restart
without luck ,,, the annoying box is still there,.,,, any thoughts ?
Click to expand...
Click to collapse
I read some other user's experience on S2 too. But sorry nothing found that works 100%,
It not happens to everyone, so may be it should have relation with previous ROM(even on OTA update it can happen). May be just try to downgrade to GB ROM, root it , wipe cache, data,delvic cache, and use Mobile odin to update 4.0.4. Thouh this is just speculation on basis of clean install. I dont have review that this will work.
shivg86 said:
tell me the procedure you are following in flashing the roms and please try to downgrade to a safe gingerbread rom then root it or use pre-rooted gb rom from DR.KETAN'S GUIDE.
Click to expand...
Click to collapse
I used PC Odlin to flash the PDA only, the ROM was official ROM from http://samsung-updates.com/device/?id=GT-N7000.
note that I upgraded the version through Kies firstly, previously I was on V4.0.3 official rom (rooted) - without this issue
the issue was appeared after the official (kies) 4.0.4 upgrade
I tried to downgrade to V4.0.3 (obtain the ROM from the link said above), the problem gone ...
then I upgrade to V4.0.4 again (as mentioned in my last note, EFS is not a matter here) - problem back again
during several trials, I aslo tried to reset the phone, (try on double wipe as well al reset to syatem default from system setting menu) and redo all those steps, but still unlucky .. None of any actions can help ...
btw : I read other articals saying to refresh kernal and double wipe ,,, no help as well ...
it drives me crazy ...
easternpig said:
I used PC Odlin to flash the PDA only, the ROM was official ROM from http://samsung-updates.com/device/?id=GT-N7000.
note that I upgraded the version through Kies firstly, previously I was on V4.0.3 official rom (rooted) - without this issue
the issue was appeared after the official (kies) 4.0.4 upgrade
I tried to downgrade to V4.0.3 (obtain the ROM from the link said above), the problem gone ...
then I upgrade to V4.0.4 again (as mentioned in my last note, EFS is not a matter here) - problem back again
during several trials, I aslo tried to reset the phone, (try on double wipe as well al reset to syatem default from system setting menu) and redo all those steps, but still unlucky .. None of any actions can help ...
btw : I read other articals saying to refresh kernal and double wipe ,,, no help as well ...
it drives me crazy ...
Click to expand...
Click to collapse
dr.ketan said:
I read some other user's experience on S2 too. But sorry nothing found that works 100%,
It not happens to everyone, so may be it should have relation with previous ROM(even on OTA update it can happen). May be just try to downgrade to GB ROM, root it , wipe cache, data,delvic cache, and use Mobile odin to update 4.0.4. Thouh this is just speculation on basis of clean install. I dont have review that this will work.
Click to expand...
Click to collapse
Tried on this ROM SGN_XX_OXA_KJ1_FACTORYFS, no issue, then follow the instruction ,,, root it , wipe cache, data,delvic cache, and use Mobile odin to update 4.0.4,, that annoying box still happens ... My Goooooood ....
I had talk with samsung service centre guy(who is really noob, and owner sending his device to me to root ), he said he had email regarding this. I am planning to go to SSC to read mail what exactly he got information, really here in my town very small service centre. he couldn't even find out what set of instruction exactly there on mail
Lets see if anything special. This is likely ROM bug, b'coz some one who have updated from OTA, also get this.
The title pretty much says it all. I've been reading for days and my eyes are burning yet I still haven't found anything exactly like what I'm asking...and I don't want to keep asking stupid questions in the dev section.....
I was on a custom Froyo ROM for a long time and finally got around to trying out SlimICS 4.2 a couple of weeks ago. The instructions called for a CM9 flash first, then SlimICS. It all worked perfectly and I love the ROM.
I've never tried GB and am still on Froyo bootloaders. I would like to switch to GB bootloaders, maybe for no good reason at all. I figure in the long run it will be a good idea. (different rom, kernel, JB, whatever)
I was told that trying to use Odin to simply flash GB bootloaders over an ICS rom and kernel might be a bad idea. I'm hoping someone has successfully done this but most of my reading has got me feeling a bit cautious about bootloaders...
I'm looking for a simple, logical sequence to get me back exactly where I am (ICS) but with GB bootloaders. Perhaps back to a custom Froyo rom/kernel then flash GB bootloaders then back to ICS? I'm guessing that cwm will be able to restore the state of my current rom after all that. I'm so sick of setting up everything from scratch and Titanium can only do so much....
Thanks
Here ya go...
U cannot flash the GB Bootloaders while you are running a Rom that has the mtd/yaffs or yaffs2 partition, that is, a CM, MIUI, ICS, JellyBean and such like. U will need to be on a bml/rfs partition, that is, a Stock Rom or at least a Dev Rom based from a stock firmware.
Do an Nandroid Backup on what you are running currently.
Backup everything you do want to save...apps, contacts, messages, emails, pics, efs folder, etc.
Then you will need to flash back to Stock GB Firmware with Bootloaders included. The i897ucKK4 is the latest official. Here is Stock I897UCKK4 Android 2.3.5 One Clicks. Use the Odin or Heimdall version that includes the GB Bootloaders. If you have a newer Captivate that does not like using the One Clicks, then see this thread for the .tar package of the i897ucKK4... [ROM] I897UCKK4 [17.11.2011][Android 2.3.5]. With this you will probably have to wipedata/factory reset first. Then use regular Odinv3 1.83 or similar to flash it. **Note: Flashing Bootloaders is risky. So be sure you have a trust worthy micro usb/usb cable, constant power source, etc. You don't want to loose power or connection during the few seconds that the bootloaders are being flashed. Bad bootloader flash = hard brick.
Once you are successfully back on Stock KK4, then go to this thread... [KERNEL][KK4][1/28/11] Corn Kernel and use the regular Odin to flash the .tar 7.0A version of this kernel. This will give you the CWM Recovery that you need.
Then reboot into CWM and reinstall the ICS Rom you were on before per that Rom's install instructions.
Once you are booted up on that ICS Rom, reboot into the Recovery of that Rom and then you can Restore your backup that you did at the beginning of this process.
You should be good now.
For issues along the way with connections to the pc, download mode, etc. please see this thread... Captivate Connection Issues and Download Mode Help
The most direct route would be to flash a Gingerbread-based Stock rom with bootloaders from your current setup. This will put you back at stock (including your partitioning), so you'll have to flash as if you're going to CM-based roms for the first time when you go back to ICS/JB.
Obviously, there's all the normal cautions of backing up, bootloader dangers, etc.
@ jmtheiss... I Ninja'd ya by a few minutes. Lol
{
"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"
}
They both said it better than I could have but what it comes down to is there is no "simple" way to go about what you are wanting to do...
Sent from my SGH-I897 using xda app-developers app
I don't think a lousy "thanks" even begins to cover it. I really appreciate when someone puts that much effort into helping somebody out. Cheers!
And that definitely qualifies as "simple" enough...better than something requiring rooting again and getting a functional recovery, etc. A couple of Odin sessions and a couple of cwm flashes are fine.
Thanks again guys.
bcflyfisher said:
I was told that trying to use Odin to simply flash GB bootloaders over an ICS rom and kernel might be a bad idea. I'm hoping someone has successfully done this but most of my reading has got me feeling a bit cautious about bootloaders...
Thanks
Click to expand...
Click to collapse
I have done it successfully a couple of times without any issues. I have only done it when absolutely necessary since they do say there's some risk there.
What I don't understand is how you *could* run ICS without GB bootloaders? I didn't think that was possible.
I'm living proof. I was hesitant but their instructions said if coming from Froyo flash CM9 first then SlimICS. I flipped a coin and it worked fine. The developer of Slim (krarvind) knows I'm on Froyo bootloaders and didn't seem too phased by it. Whether or not I'd be able to jump to JB with whatever kernel is unknown so I'm going to backtrack a little and do what I probably should have in the first place.
Here's an update of what I did just in case it's helpful to someone else down the road.......
I did my best to follow the suggestions given by 4-2ndtwin in the 2nd post. I generally have pretty good backups of everything done but I did new ones just for kicks. Nandroid, Titanium Backup, efs, SMS, call log, APN, and a few other things. I downloaded all the necessary files, and laid them all out sequentially on my screen so I wouldn't get distracted and screw up. In the end I'm pretty much exactly where I wanted to be but of course there were a few unexpected issues.
- The Heimdall One-Click of stock GB with bootloaders was very easy. I had Samsung drivers on the computer already but Heimdall insisted on installing new ones. After that it did its thing and I was on official KK4 with GB bootloaders.
- Next up was regular Odin flash of the Corn Kernel. When I connected the phone in download mode Odin didn't give me a yellow light. If I connected the phone while it was NOT in download mode Odin recognized it. I wasted at least an hour to discover that it was just a driver issue. The drivers that Heimdall wanted weren't "good enough" for Odin. Interestingly, neither was the original package I had on the computer. The one that worked was called "Samsung_USB_Driver_for_Mobile_Phones.zip" from the Samsung website. After installing that Odin saw my phone in download mode and I was able to install the Corn Kernel. Rebooting into recovery gave an option to root the phone.
- At this point everyone in the world decided they needed something from me so between work and phone calls/texts I ended up using the phone on GB for a while.
- My boot screens had been a total mess since my first custom rom so I decided to do the boot screen fix next - http://forum.xda-developers.com/showthread.php?t=1065743 - TRusselo added a bunch of good info to the thread and there's a good post on page 10 from irishvandal that explains the whole sequence of boot screens and what you can and cannot change.
- So the next step should have been to flash CM9 on my way back to SlimICS just like I did a month ago. I figured since I had been using the phone for a couple of hours I should wipe everything ... so I did the cache, data, format system, dalvik cache, and then I went to flash CM9 and noticed that for some reason I didn't have the zip file on the phone any more. I must have deleted it myself because nothing else spontaneously disappeared. When I rebooted normally to plug the phone in and transfer files I discovered that in wiping/formatting I messed something up and I kept getting stuck on the Corn Kernel boot screen. I could get into recovery or download mode just fine, just no normal boot. I was able to mount storage in recovery but when I tried to copy over the CM9 zip it kept hanging. After numerous attempts I decided to just go right back to the beginning.....
- Heimdall once again wanted its own drivers. No problem, I did that, then uninstalled them and reinstalled the drivers Odin likes, then got Corn again, did the boot screen fix again just to try a different image, then downloaded a new CM9 Nightly and copied it to the SD, flashed it with no issues, then flashed SlimICS (which actually has 2 zips plus addon packages) and I was back to ICS with GB bootloaders. It's amazing how fast things can be done when there are no more surprises!
- When the phone was rebooting into Slim ICS I got a message I don't remember seeing before - "Android is upgrading" or something similar. Weird. The next time I booted to recovery to try to restore the nandroid backup I ended up in CWMR Touch v5.5.0.4, which is weird looking and makes me feel strange. When I tried to do a full restore it encountered a few issues such as not being able to restore data normally. I don't recall the details but when I reinstalled Titanium Backup it would just FC so I couldn't restore any of my other apps. The "solution" was to reflash the Slim zips and do a restore of the system only. This set up all the tedious stuff for me. I got TiBu again and restored apps+data and that worked. Chose my launcher and it was back almost the way I wanted it. Interestingly, I had to replace the widgets but the shortcuts were all there in the right places.
- Voice search force closed. Slim doesn't include it in the base rom but it's available as an add-on and I had the zip on the sd from last time but flashing it didn't fix the problem (it had worked the first time I installed Slim). Some random sequence of freezing the Voice Search app, wiping its data, reflashing the Voice zip, unfreezing the app and it worked. In the process I noticed that in TiBu it was originally listed as Voice Search 2.x.x but then it was suddenly 3.x.x with a different icon. Then an hour later after all kinds of restoring (SMS, call log, etc) voice was force closing again. It was also listed as 2.x.x. This time it took me twice as long to randomly do things until it started working again (and at the same time it turned back into 3.x.x. It's been fine since...
So again a huge thanks for the advice! I got to spend the better part of a day fighting my way through minor issues but I learned a lot about my phone and got over my aversion to Odin for the last time. Hopefully someone else can benefit from something I've gone through. If nothing else, I feel a renewed sense of accomplishment.
^
If all ur ics and jb roms have run well...then i see no need to flash the bootloaders.
Sent from my SAMSUNG-SGH-I897 using xda premium
Hello, I'm using Semaphore + CM10 JB for few weeks (installed with your support).
However I have a problem. The stability. My phone likes to resets byself, even few times per day. It happens irregularly. What's interesting, sometimes phone resets to the CWM. Sometimes resets and backs to work, sometimes totally offs the phone (and i need to pull out the battery) or freeze on cyanogenmod start screen (but not on normal start, only when resets)
Sometimes it happens when i'm using the phone, sometimes not. He likes to do that when i'm sleeping (for example, goes to the CWM and discharge the battery by whole night on full bright).
And much smaller, but maybe important issue: when the phone starts, shows the message Warning! A problem was detected with your device. Your device IMEI number is invalid. And invalid IMEI number could cause network issues including the inability to call emergency numbers.
Firstly I installed CM10, i had the problems with the network, but after @xsenman's help (reinstall with older ROM before flashing CM10) everything works correctly and i can see IMEI too. I made an EFS backup in that old ROM, should i use that? This message doesn't intrude me, but i'm just thinking if this could be connected with reseting problems. My SGS works really nice, but that one issue is really annoying.
100 views and really no one can help?
Come on, i feel so lonely
I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color
thanks for your answer. However, maybe it's not a ROM problem? Maybe some application makes an issue. Is there any log where i can check that?
That IMEI stuff definitely isn't app-caused. I can only repeat my statement above. Don't worry about data, you can backup everything using Titanium Backup and SMS Backup+.
Btw: What ROM are you on?
Best regards
Sent from my Gameboy Color
True, IMEI not, but it's not a real issue for me. Actually, i'm absolutely satisfied of my i9000 (maybe flashlight absence, but it's hardware). Everything works fine, but reseting problem makes me nervous when I use the phone as car dvr or for endomondo ect.
I use Cyanogenmod 10, one of october's nightly versions.
So basically you don't want to change anything but you want us to help you? Sorry, that's not the way a community works.
You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.
przemek211 said:
You didn't understand me. My problem is phone reseting. I want to find the reason of the issue. Because without it, i can install new software and still have the same problem.
Click to expand...
Click to collapse
Since when has this problem occurred? I doubt an app makes a phone reset itself.
Edit: I looked around your post history and you seem to have posted in the semaphore thread. Maybe something is wrong with the kernel?
Sent from my GT-I9000
Thanks for your answer. It's hard to say because I've flash a ROM and out of hand I installed the applications. It's the worst type of problems, because it doesn't happen instantly or regularly. Actually since i wrote the topic, i didn't see the problem, however i saw two-three times the attention about IMEI, so i think, the phone resets, but not seen.
/// amerkiller: you are using i9000 too, could you recommend me any other ROM? Probably I will need to install a ROM and wait, two-three days and check if the ROM makes any issues.
/// maybe, but how can i check it? It looks like work nice, my question in Semaphore's thread was about the features
I use Remics-JB, you can try it out if you want a Samsung touchwiz feel, and apps from the S3.
Slimbean if you want a minimalist ROM.
Hopefully, the problem will disappear.
Powodzenia
Edit: regarding the kernel, you can flash Devil and see if the problem persists.
Sent from my GT-I9000
So I will try Devil + Slimbean, thank you
amerkiller1995 said:
Powodzenia
Click to expand...
Click to collapse
Poles everywhere?
pozdrawiam
BlueFlame4 said:
I'd recommend flashing a clean GB stock, restoring your IMEI, flashing CM9 twice and then flashing CM10 ROMs (if you want them lol). Always be sure that you wipe your phone after installs.
Sent from my Gameboy Color
Click to expand...
Click to collapse
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?
przemek211 said:
Ok, so i want to reflash my i9000. So - i have JVU's gingerbread ROM, is that correct stock ROM? Should i make the WIPE here? I'm not sure about restoring IMEI. Should i do that in GB's temporary ROM or (as I think) later in JB's? Of course, earlier I need to backup the efs folder with IMEI so i think i should do that in GB's and restore it in CM10 (or in Slimbean which I want to test). And one more doubt. You said flashing CM9 twice. Why is that? And how can I do that if i'm installing the ROM in CWM?
Click to expand...
Click to collapse
You can find tutorials about flashing to stock.
http://forum.xda-developers.com/showthread.php?t=1102881
Flashing the stock ROM will recover your IMEI number if you currently don't have it and will wipe your personal files. Backup your IMEI while you're on GB and if you lose it, then restore it. Fyi I never lost my IMEI, it's not common. You should flash JB / cm10 twice, ICS/cm9 should be okay after one flash. Remember to wipe if the instructions say so.
When you'll attempt to flash cm10 in recovery, you'll get a warning about partition change. You'll have to chose to flash second time, this time it should work and the phone will reboot into a bootloop. Pull out the battery and enter recovery and flash cm10 again. This time it well install and reboot successfully.
Sent from my GT-I9000
It's everything working nicely? Asking out of curiosity.
Sent from my GT-I9000
Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.
przemek211 said:
Hi, thanks for your interest
Two days ago I made a re-flash Stock > CWM > CM9 (twice) > CM10
Attention about IMEI doesn't longer appear
I've installed apps. The phone has resets for a one time when I was using some app. It is not a big problem for me if SGS makes that from time to time (maybe some apps are not adapted to the JB very well). However today I used him to record my drive (dailyroads voyager) and when i tried to stop the recording, he doesn't backs to life (just I needed to pull the battery out) and video file was corrupted. But when I was getting back to home it worked correctly. I have no idea why that's happen.
Click to expand...
Click to collapse
Restarts shouldn't happen that was some unusual circumstance. The video problem is weird, post here if it happens again, lets hope its just bad luck.
Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.
przemek211 said:
Ok, I'll look on it.
I have one other question and maybe you will know.
Call recording. There are two options for use this feature. Simple MIC recording apps and 'two-way call recording' which is much better, however it needs kernel with handle of it. I didn't find anyone for SGS, so I want to use MIC recording. There are many apps in Google Play. However any of them makes 0kB files of record on JB's CM10. When I was using gingerbread it didn't worked too however files were good, but the second side of call didn't hear me.
Click to expand...
Click to collapse
In regards to two way recording, i don't think it's solved...
http://forum.xda-developers.com/showthread.php?t=863074&page=38
I never needed that feature, so i won't be much help, try different apps and remember some apps are on XDA, not only the play store.
Sent from my GT-I9000
I saw that, but it is only for Froyo, when i installed it into gingerbread i needed to re-flash my SGS
I tried a lot of apps, however it looks like being locked (if worked they made 0kB files)
Long story shorter. Phone stolen. Phone had nandroid stored on my computer. Phone replaced by another Note 4 (PS, thief go pound sand). Didn't mess around, stock rom to Note 4 (ANK). Root. Recovery. Old image from lost phone used as recovery. (Yeah I didn't make a backup of original from new phone). Flashed over. Everything works fine. Now ready to put finger prints in. Error page pops up saying fingerprint scanner error. 72 hours of scouring this forum, internet, MULTIPLE stock rom flashes from the oldest to NJK to ANK and COG6. Clean flash, dirty flash NOTHING works. Makes no difference what I do, cannot get the fingerprint scanner to perform. Common problem, complaints all over the internet about it but NO SOLUTIONS. I have tried everything down to deleting directories and I cannot get the damn thing to work. Seriously doubt hardware issue. *#0*# sensor heading shows finger print scanner as Null and 0.0.0.0. Deleted cache. Deleted data from TIBU and now after three days I give up. Seems everyone has the problem but nobody knows why and when they do you get a half assed or worse answer as to how to fix it. Does anybody know how to get this thing working again. Do I need to flash an apk. Where can I find it. Do I need to rebuild. ? Can anyone flash that section fingerprint free and send it to me. I am just guessing. I know crap about how stuff works, I just know how to follow directions but this one has got me stumped.
Any help would be GREATLY APPRECIATED!
Regards,
Freddie did not get fingered but he needs it.
You need to flash stock firmware and verify that all is stock, sometimes after returning to stock you may have a miss matching error like bootloader or modem.
After running stock run smartswitch.
Pp.
PanchoPlanet said:
You need to flash stock firmware and verify that all is stock, sometimes after returning to stock you may have a miss matching error like bootloader or modem.
After running stock run smartswitch.
Pp.
Click to expand...
Click to collapse
Ok forgive me for my ignorance but if I run a stock firmware straight from Sammy shouldn't the bootloader and modem be part of the rom? It seems to me that doing a wipe should be like reinstalling windows, you format the drive and install the OS. There is nothing left and a complete rebuild of the file system occurs. Is this not what happens when you do a wipe in the recovery and then Odin the stock firmware? How can I be sure that when I install a stock rom everything is wiped and there is no hangers and the OS on the phone is rebuilt completely? When you say smartswitch I assume you mean the Sammy program.
jackler1 said:
Ok forgive me for my ignorance but if I run a stock firmware straight from Sammy shouldn't the bootloader and modem be part of the rom? It seems to me that doing a wipe should be like reinstalling windows, you format the drive and install the OS. There is nothing left and a complete rebuild of the file system occurs. Is this not what happens when you do a wipe in the recovery and then Odin the stock firmware? How can I be sure that when I install a stock rom everything is wiped and there is no hangers and the OS on the phone is rebuilt completely? When you say smartswitch I assume you mean the Sammy program.
Click to expand...
Click to collapse
Ok, I think I have found it but now I need to know how to fix it. Currently I have as follows in the about device screen:
Model SN-N910T
AHHA ------!!!!! - ANDROID VERSION 5.0
Baseband - N910TU1ANK4
Kernal version - 3.10.0-2796035 [email protected] #1 Thu Nov 13 18:01:07 KST 2014
Build number - KTU84P.N910TUVU1ANK4
So it seems the android version is wrong. Again forgive my stupidity but what exactly IS the android version. Meaning is that the baseband, the modem, what part of the stock rom is flashed wrong and where do I find that part to flash it correctly. I think I am making some progress just need input. Thanks Pp for getting me on track, now I just need a little shove to get this train rolling and maybe learn something in the process. If I fix it I then intend to write a proper write up for those lost souls out there who don't have to spend days....
So why does it say my android version is 5.0 when it should say 4.4.4?
Thank,
Freddy is getting nervous
First verify what version of the note 4 you have, Sm-N910T or Sm-N910T3 and flash proper firmware. Look under your battery.
Once you root you jumble up the phones ability to install firmware properly, and flashing stock firmware once with odin does not always secure components thus leaving you with unofficial status, "custom" and you think you went back to stock with no root but not official yet.
You need to make sure everything flashes and sticks, Model nunber, Android version, Basedand version, Kernel version, Build number.
Any of the modified components can stick and not be overwritten by stock odin flash.
Sometimes multiple flashes, or individual component flashes are required to go back to "official" stock form.
At this point you can verify that your fingerprint scanner works properly and leave it alone or proceed cautiously if root is really required ??? .
I only run stock and save myself all the headaches, I used to root back when Samsung phones where simple and less complicated without kernel security from Samsung.
I suggest latest 5.1.1 lollipop update, kitkat is primitive and outdated, you will be amazed at how well your note will run with latest firmware (with junk apps disabled).
Pp.
Here's a sample of my stock Note 4 running latest update.
Pp.
PanchoPlanet said:
Here's a sample of my stock Note 4 running latest update.
Pp.
Click to expand...
Click to collapse
Nope, I have wiped this phone a million times, reinstalled factory rom over the top of itself a dozen times, installed the baseband and bootloader separately after that and NOTHING changes it still will not work. I have read the complete internet from front to back and it seems nobody knows but the shadow.....Thanks for taking the time for trying to help me out though...
When you say wipe, do you mean factory reset?
Several resets in a row should wipe it clean. Something is stuck, could be the kernel, that will prevent a clean install.
You need to find a way to wipe partitions individually using ADB on the PC, that should allow for a clean install.
Pp.
jackler1 said:
Long story shorter. Phone stolen. Phone had nandroid stored on my computer. Phone replaced by another Note 4 (PS, thief go pound sand). Didn't mess around, stock rom to Note 4 (ANK). Root. Recovery. Old image from lost phone used as recovery. (Yeah I didn't make a backup of original from new phone). Flashed over. Everything works fine. Now ready to put finger prints in. Error page pops up saying fingerprint scanner error. 72 hours of scouring this forum, internet, MULTIPLE stock rom flashes from the oldest to NJK to ANK and COG6. Clean flash, dirty flash NOTHING works. Makes no difference what I do, cannot get the fingerprint scanner to perform. Common problem, complaints all over the internet about it but NO SOLUTIONS. I have tried everything down to deleting directories and I cannot get the damn thing to work. Seriously doubt hardware issue. *#0*# sensor heading shows finger print scanner as Null and 0.0.0.0. Deleted cache. Deleted data from TIBU and now after three days I give up. Seems everyone has the problem but nobody knows why and when they do you get a half assed or worse answer as to how to fix it. Does anybody know how to get this thing working again. Do I need to flash an apk. Where can I find it. Do I need to rebuild. ? Can anyone flash that section fingerprint free and send it to me. I am just guessing. I know crap about how stuff works, I just know how to follow directions but this one has got me stumped.
Any help would be GREATLY APPRECIATED!
Regards,
Freddie did not get fingered but he needs it.
Click to expand...
Click to collapse
try doing this...
1st - run chainfire triangle away v3.26
2nd - boot into recovery and wipe everything 3 times except external sdcard.. especially data...
3rd - boot in download mode and ODIN whatever firmware u wanna use... 2 times...
happened to me when the note 4 first came out... I had to exchange to a new note 4...
also whenever u do a nandroid.. U MUST REMOVE ANY SAVED FINGERPRINTS... so u can use that backup again..
if u restore a nandroid with a saved frintprints, it won't work, u must delete data and start fresh..
I don't know if u messed it up by restoring a nandroid from a previous phone and with saved fingerprints stored...
will do thanks for the advice will advise
Nope, nothing I do including stock or otherwise works. When you hit +#0*# it says null and 0.0.0.0 unless someone knows something I don't, it's borked. The thing is even if I used a nandroid and it overwrote my fingerprints where the ones in the nandroid so you would think it would work. Chalk it up to who knows....thanks anyway. Still looking if anyone finds solution....