Related
I've gotten into the habit of running all kinds of ROMs and sometimes they just blow up. Usually a reboot suffices but the last crash caused my phone to only bootloop and I couldn't get into recovery anymore, thankfully download mode still worked. This will focus on how to get your phone back to life, provided you can access download mode.
Steps this guide will walk you through:
Calm down a bit
Get everything you need to fix your phone
Do the magic
Boot your phone
Rejoice
Step 0: Backup
I can't stress this enough. Once you've really bricked your phone there's a chance you might not be able to access the data that's on there anymore. So, if there's stuff on your phone you care about, just backup it from time to time.
Step 1: Calm down
There's a myriad of exercises you can do to calm down, meditate, go for a walk/swim/jog, go to the gym, whatever works for you. Just chill out for a second because being in a completely panicked state is not going to help you to recover your phone.
Step 2: Get the tools in place
We need a few tools to fix your phone:
Heimdall version 1.3.1. DO NOT download 1.3.2 it has issues with uploading large files
Windows: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-suite-1.3.1-win32.zip
Mac: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall-1.3.1-mac.dmg
Debian AMD64: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall_1.3.1_amd64.deb
Debian i386: https://github.com/downloads/Benjamin-Dobell/Heimdall/heimdall_1.3.1_i386.deb
Heimdall package of 2.3.6/XWJVZ: http://www.mediafire.com/?3v35chw9a8a2wmw
CFRoot for 2.3.6/XWJVZ: http://download.chainfire.eu/130/CF-Root/SGS/CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip
Once you've downloaded everything:
Install Heimdall (run the installer)
On Windows the link I provided also includes the GUI
For Mac and Linux the link I provided only includes the command line binary, we don't want to use the GUI for this
Extract the Heimdall package of 2.3.6.tar.gz to a directory, you should end up with the following files:
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs
firmware.xml << delete it, we're not going to need it
modem.bin
params.lfs
Sbl.bin
s1_odin_20100512.pit << delete it, we're not going to need it
zImage << delete it, we're not going to need it
Extract the CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip, this contains only one file: zImage, put it next to Sbl.bin
If the Heimdall installer asked you to reboot your machine but you didn't, do it now. That will make sure the drivers are loaded.
What we've done right now is set up your machine so that it's ready to flash your i9000 back to a Samsung release of Gingerbread. The astute reader might notice I'm telling you to delete the zImage (kernel) from the Heimdall package. This is true but we're replacing it with the one from CFRoot so you can flash a rooted stock instead of first flashing stock and then flashing CFRoot on top. Some people advice against this approach but it has never caused me issues.
Step 3: Do the magic
Now we're actually going to flash your phone. We're going to do this from the command line because the Heimdall GUI is a bit twitchy when it comes to flashing without a PIT-file. The command line has no such issue and will just download the PIT from your device and use that.
Windows:
Find out where Heimdall was installed (probaly %PROGRAMFILES%\Heimdall)
Copy all the files (zImage, Sbl.bin and so forth) into the directory where the heimdall executable is located
Go to the location of cmd.exe, right-click on it and select: Run as Administrator
Now cd to the directory Heimdall was installed
Issue a dir on the commandline to verify all the files (heimdall.exe and the rest) are there
Mac / Linux:
Heimdall was probably installed into /usr/bin so all you need to do is open a Terminal of your choice and see if running the heimdall command results in heimdall output or a command not found.
Open a Terminal
cd to the location of zImage, Sbl.bin and the other files from Step 2
Flashing:
Use the 3-button combo to put your phone into Download mode: Volume Down + Home + Power and connect your phone over USB to your computer.
Windows, issue the following command:
Code:
heimdall.exe flash --primary-boot boot.bin --cache cache.rfs --factoryfs factoryfs.rfs --dbdata dbdata.rfs --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage
Mac / Linux, issue the following command:
Code:
sudo heimdall flash --primary-boot boot.bin --cache cache.rfs --factoryfs factoryfs.rfs --dbdata dbdata.rfs --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage
If all went well you should get output similar to this:
Code:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading DBDATAFS
100%
DBDATAFS upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading IBL+PBL
100%
IBL+PBL upload successful
Uploading SBL
100%
SBL upload successful
Uploading PARAM
100%
PARAM upload successful
Ending session...
Rebooting device...
Your device will now reboot. If it doesn't and stays at a black screen, just pull the battery, put it back in and turn it on.
Step 4: Boot your device
Just let the phone boot but don't unlock your SIM-card / use it. Once it's is done booting for the first time just shut it down and now boot into Recovery Mode: Volume Up + Home + Power.
From here you can go into the Mounts and Storage section and then into the Mount USB menu. Now your phone will make it's storage available over USB so you can recover files you've lost or upload a zip-file to flash a new ROM.
Step 5: Rejoice
Your phone is now back into a workable state with a fully functional Recovery so you can now start flashing your fancy ROMs again.
A few pieces of advice:
Before you flash anything else: data/factory reset and wipe your cache
Before you flash anything else: flash CM 9.1.0, twice. The first time will upgrade your Recovery to 6.x but will then bootloop so you need to flash it again.
If you want to flash a JellyBean ROM, flash CM 9.1.0 first. If you don't and try to upgrade from Gingerbread (2.3.6) to JellyBean in one go you'll probably end up with an invalid IMEI (no idea why this happens, it just does)
Good luck!
Hi,
Thanks for the guide, i got 90% there and the program closed. This is what I got:
Uploading KERNEL
100%
KERNEL upload successful
Uploading MODEM
100%
MODEM upload successful
Uploading FACTORYFS
100%
FACTORYFS upload successful
Uploading DBDATAFS
100%
DBDATAFS upload successful
Uploading CACHE
100%
CACHE upload successful
Uploading IBL+PBL
100%
ERROR: Failed to confirm end of file transfer sequence!
IBL+PBL upload failed!
Ending session...
Rebooting device...
Click to expand...
Click to collapse
Please HELP me
What do I do from here??
battznz said:
Hi,
Thanks for the guide, i got 90% there and the program closed. This is what I got:
Please HELP me
What do I do from here??
Click to expand...
Click to collapse
That one is in my experience either caused because you supplied a PIT-file or because you've got a funky version of Heimdall.
how about when the phone can't get to download mode :/
usb jig?
microMXL said:
how about when the phone can't get to download mode :/
usb jig?
Click to expand...
Click to collapse
try solutions in My Android Solutions
Use only ROM and solution for your model and Wipe x3
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
(Do remember to backup your contacts, data, images etc and also your EFS folder before flashing a ROM and make sure you have more than 50% battery charge before you attempt any sort of flashing.)
The link for Heimdall version 1.3.1. (Windows) you posted has no Installer inside.
I desparetely need to unbrick my Gaaxy S. Any solutions?
SpartanWarrior said:
The link for Heimdall version 1.3.1. (Windows) you posted has no Installer inside.
I desparetely need to unbrick my Gaaxy S. Any solutions?
Click to expand...
Click to collapse
try download from My Android Collections
Phone stuck in bootloop, possible corrupt internal memory?
HI,
Thanks for your post, as a noob I find posts like yours great as they are easy to follow, and have all the info in one spot.
I have followed everything that you said to do, however, when my phone reboots after cmd successfully finishes, it boots into recovery, and says the following:
[QUOTE]--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
--Deleting files...
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
--Updating filesystem...
verifying the filesystem. please wait.
already updated filesystem. finished
Succesfully updated filesystem.
--Wiping cache...
Formatting /cache...
Cache wipe failed.
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.[/QUOTE]
If I hit "reboot system now" it comes up with the Galaxy S logo, then switches off, then repeats itself, the only way to stop it is to take the battery out. I can still access both recovery and download mode at this stage.
I bought this phone cheap off someone who had installed a custom ROM which had messed the phone. I am trying to get it working again, but I think I may only have made it worse . The phone is not recognizing any SDcard, or its own internal memory. When the phone was working, if you went into settings under memory it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"
Any help would be much appreciated.
Thanks
mars777jd said:
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
Click to expand...
Click to collapse
try to flash a Ezbase Rescue or Darky resurrection Kit from My Android Collections
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
xsenman said:
try to flash a Ezbase Rescue or Darky resurrection Kit from My Android Collections
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Click to expand...
Click to collapse
Hi,
I tried EzBase Rescue, with the following result:
-- Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
-- Wiping data...
Formatting /data...
E: format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
Data wipe failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.
Click to expand...
Click to collapse
I will try the resurrection kit...
mars777jd said:
Hi,
I tried EzBase Rescue, with the following result:
I will try the resurrection kit...
Click to expand...
Click to collapse
Couldn't seem to find a link to the resurrection kit that worked properly. All other rescue packages either result with bootloop or the above error messages in recovery mode.
mars777jd said:
Couldn't seem to find a link to the resurrection kit that worked properly. All other rescue packages either result with bootloop or the above error messages in recovery mode.
Click to expand...
Click to collapse
you can try http://depositfiles.com/files/ro6fnlr38 or http://depositfiles.com/files/zay0if5x7 for Darky and a solution from My Android Solutions for
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu>Settings>Applications>Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
well just for the record, mine didn't work neither with usb jig, now I have a pretty nice paperweight. *sighs*
microMXL said:
well just for the record, mine didn't work neither with usb jig, now I have a pretty nice paperweight. *sighs*
Click to expand...
Click to collapse
usb jig can only work when USB slot is not damaged or misaligned , check usb connection problems in My Android Solutions or read this thread
mars777jd said:
HI,
Thanks for your post, as a noob I find posts like yours great as they are easy to follow, and have all the info in one spot.
I have followed everything that you said to do, however, when my phone reboots after cmd successfully finishes, it boots into recovery, and says the following:
[QUOTE]--Installing Package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.
Media files copy failed.
--Deleting files...
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI men
u for format and reboot actions.
--Updating filesystem...
verifying the filesystem. please wait.
already updated filesystem. finished
Succesfully updated filesystem.
--Wiping cache...
Formatting /cache...
Cache wipe failed.
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/CHN/system/'.
Successfully applied multi-CSC.
Click to expand...
Click to collapse
If I hit "reboot system now" it comes up with the Galaxy S logo, then switches off, then repeats itself, the only way to stop it is to take the battery out. I can still access both recovery and download mode at this stage.
I bought this phone cheap off someone who had installed a custom ROM which had messed the phone. I am trying to get it working again, but I think I may only have made it worse . The phone is not recognizing any SDcard, or its own internal memory. When the phone was working, if you went into settings under memory it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"
Any help would be much appreciated.
Thanks[/QUOTE]
Same happens to me. Any idea on what's going on?
vindikleuk said:
it said "Internal: 0.00B free of 0.00B" and even though there was an SDcard in it, it said "Please insert SD card"?
Click to expand...
Click to collapse
explain what is your phone model, if you had lag fix applied before and what you had done and what is the exact message you are getting when you try to boot .
Need to know what is your phone model . Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
xsenman said:
explain what is your phone model, if you had lag fix applied before and what you had done and what is the exact message you are getting when you try to boot .
Need to know what is your phone model . Check Here to chose your forum/Guide by Version of your phone or you will have more problems by using wrong solutions due to different versions of Galaxy S
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
Need a guide, look into My Guides and Manuals
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
Click to expand...
Click to collapse
Well what happened is this:
I saw this phone going cheap on eBay by someone who said that they "had tried flashing a custom ROM, and now the camera won't work due to a memory error." I had successfully flashed CM7 to a Nexus One, so I wanted to see if I could fix it.
I don't know what ROM he tried to install, but at that point the phone still booted. I could use the phone and all functions that didn't need free memory (ie camera). I went into settings, and, like I mentioned, although there was a micro-SD card the phone reported "0.00B free of 0.00B Internal" and "Please insert an SD card" for external. I thought it may have been a problem with the SD card, so I formatted it on the computer. Same result.
I then proceeded to flash a known trusted stable ROM to the phone. I opted for CM9 with CWM for I9000. This is where I first ran into problems. I was using fastboot at the time, and always, after flashing anything I would get these results (see pics.) So I downloaded Odin, and after trying several different things from various wiki's and guides on xda and other sites, I believe I have successfully wiped any existing OS, and any custom recoveries.
The phone's model is GT-I9000. The SSN is I9000GSMH. I also have the IMEI and S/N. From my understanding, it was originally locked to Vodafone, and was unlocked by the previous owner.
So far I have tried flashing:
CM9
DarkyRom_10.2 Resurrection
ezbase gb
SGS_Rescue_kit-13-1-2012
plus a few different individual pda, csc, bootloader files.
I am again going to try DarkyRom_10.2 Resurrection, once I can get Odin to recognize my phone.
Is there any thing else I can try? Or should I try to sell my phone for parts?
I really appreciate everyone's help
Thank you so much
mars777jd said:
Is there any thing else I can try? Or should I try to sell my phone for parts? I really appreciate everyone's help
Thank you so much
Click to expand...
Click to collapse
you may need to repeat flash at least 3 times, first with 512 PIt and repartition, second with 803 Pit NO REPARTITIONING and finally a normal flash without PIT, use JVU or JVZ ROM
xsenman said:
you may need to repeat flash at least 3 times, first with 512 PIt and repartition, second with 803 Pit NO REPARTITIONING and finally a normal flash without PIT, use JVU or JVZ ROM
Click to expand...
Click to collapse
OK, I will try that, do you know where to find those?
mars777jd said:
OK, I will try that, do you know where to find those?
Click to expand...
Click to collapse
in My Android Collections
Hi
I have a problem i get this error : E:failed to mount /efs (Invalid argument)
and the /efs file is empty there is nothing there what do i have to do please help
and the other message i get is ( Factory mode is on )
and sometimes it register the network after some hours it got no service and after flash i got back my network it hapend many times.
Please help.
Click to expand...
Click to collapse
The Phone is Dead now !! anyone can help please
habab said:
Hi
I have a problem i get this error : E:failed to mount /efs (Invalid argument)
and the /efs file is empty there is nothing there what do i have to do please help
and the other message i get is ( Factory mode is on )
and sometimes it register the network after some hours it got no service and after flash i got back my network it hapend many times.
Please help.
Click to expand...
Click to collapse
Read this thread.
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
i didn't understand this
2- Create a file with a name 'factorymode' on the sdcard, open it, input 'ON' and then save it. Navigate to the efs folder, create the folder with a name 'FactoryApp' (case sensitive). Finally move the file 'factorymode' you have created above to that folder. Reboot the phone to see if the problem still persists?
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
i have tried that thread still have same problem .
Any help !?!?
..
fffft said:
I'm sure that you find this frustrating. However we are not psychic. Unless you tell us what led up to this and in particular, a step by step, detailed description of what you have tried, how can we discern going on?
What led up to this situation? What exactly have you tried? Step by step, in detail. What exactly is in your /efs folder? Did you create the /efs/FactoryApp/factorymode file as was suggested earlier? Do you have a backup of your /efs partition? Is reactivation lock disabled?
If you actually created the file in the manner described and it didn't succeed and barring something novel in a description of your situation the next step is probably to mount the /efs partition from recovery mode, format it, recreate the /efs folder, remount and reboot so that the efs is rebuilt. But before you do any of that, give us a better description of your situation.
.
Click to expand...
Click to collapse
Hi , i Downloaded a efs backup app and i just pressed on restore before i press on backup , after that the /efs file is empty . i tried to make ( /efs/FactoryApp/factorymode ) with this app : root browser but that didn't work...
i have tried to Flash with many stock room from sammobile but the /efs file still empty .
after reboot i have to connect to Wifi every time i reboot the phone and some time i have Network and some time nott .
..
yes i have backup of the efs ,
the app that i am using just named Root browser with black android pirate icon
.
i maked the directory ( FactoryApp ) then ( file factorymode on the root ) then moved it on FactoryApp , after reboot i find the file emptey again !
and i used this app ( http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325 ) for backup
..
1. i am sorry, my English is so bad !!
2. day 1 , i Downloaded the app Samsung tool and then maked a backup of EFS on External SD-Card ,
3. I maked restore and i had removed the SD-card
4. after that i didn't know that the efs file was damaged , i just installed an room from sammobile ( G900FXXU1ANG9_G900FNEE1ANG5_NEE ) , after the installation was done the phone started but i got an warning massage that says , FactoryMode is on and the wifi was off and only emergency call , i rebooted the phone the wifi was till of but i got back my Network after that i tried many firmware from sammobile
5. o searched on xda and find that it can be the efs but when opened the /efs it was empty.
6. i have the efs-backup on my sd i tried to restore it but nothing happened .
7. i tested that ( Opened this app : https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree ) maked /efs/FactoryApp/ and then file factorymode , ON ) but it can't be moved to FactoryApp when i move or copy it to the folder it is nott there , After rebooting the phone even the FactoryApp directory is deleted .
in my sdcard i found only this ( samsung tool/efs.img )
i tried to make this again
directory ( FactoryApp ) then ( file factorymode on the root ) then moved it on FactoryApp
Click to expand...
Click to collapse
After reastart phone screen is just black !! but the pc is finding it !!! now the phone is dead
..
No i can't boot to anything !! it is just black screen .
No i can't boot to anything !! it is just black screen .
please help me with that.
vndnguyen said:
Read this thread.
Click to expand...
Click to collapse
fffft said:
I'm sure that you find this frustrating. However we are not psychic. Unless you tell us what led up to this and in particular, a step by step, detailed description of what you have tried, how can we discern going on?
What led up to this situation? What exactly have you tried? Step by step, in detail. What exactly is in your /efs folder? Did you create the /efs/FactoryApp/factorymode file as was suggested earlier? Do you have a backup of your /efs partition? Is reactivation lock disabled?
If you actually created the file in the manner described and it didn't succeed and barring something novel in a description of your situation the next step is probably to mount the /efs partition from recovery mode, format it, recreate the /efs folder, remount and reboot so that the efs is rebuilt. But before you do any of that, give us a better description of your situation.
.
Click to expand...
Click to collapse
fffft said:
No problem and your patience is appreciated.
Nothing anomalous is showing up in those details so I think we can safely assume that accidentally pressing the restore button rather than backup button simply corrupted your efs partition. All of those questions were aimed at confirming that with certainty, but I understand that this is a lot of work and frustrating for you too. So we'll proceed on that basis.
An efs.img file is an uncompressed efs backup. So try restoring that with your efs program. I have no idea if it is a valid (working) backup, but you aren't going to cause any further harm by trying to restore it. If that works, great and you're done. If not, then we'll go on to rebuild your efs instead.
To rebuild your efs partition we need a custom recovery. So a few last questions.
You are rooted, correct?
Did you use Towel root or CF-autoroot? (I am trying to discern if you have super su /busybox installed)
Are you able to boot to recovery mode (home + power up + power)?
Do you have a custom recovery installed e.g. TWRP or CWM?
If you can answer yes to all four questions, then go ahead and run the following efs repair script. If not, then you'll need to install a custom recovery first. If you're already rooted but don't have TWRP, then it's just a matter of flashing TWRP with Odin from download mode.
In any event, once you have a custom recovery in place you can run this recovery script.
Download the script here. Copy it to your external SD card. Then boot to recovery mode and install the flashable zip file "Brick_Loop_FIX_afterRestoringBackup.zip" that you copied to your Ext SD card.
Then reboot. If you still have any issues, reboot a second time, then let us know if your phone is working properly again.
Credit to Backachu, I believe for saving me the work of having to write a script for you or describe how to enter the commands manually.
The script comes from this thread. http://forum.xda-developers.com/showthread.php?p=47014662
As an aside, there is a minor mystery there. This comes from a Note 3 thread so when I went to modify it to work with your S5, I found that it was already set up for the S5 rather than the Note 3.. so why it is that way in a Note 3 thread is a mystery. Go figure. But I did check and you can use it the way it is.
.
---------- Post added at 07:43 AM ---------- Previous post was at 07:36 AM ----------
I'm not sure what you mean by "dead". If you can boot to recovery & download mode, don't worry about it for now. Otherwise please elaborate.
.
Click to expand...
Click to collapse
..
fffft said:
Don't panic. I'm sure that we can address the new issue, whatever it is.
I need a little information to determine how to fix it.
I understood that your screen is black after you rebooted. What do you mean by the PC can find it. What message do you see on the PC.. the normal USB message when you connect your phone or something else? If something else, what is the exact message from the PC?
Also please do the following
Disconnect the USB cable and remove your battery from your phone for ten seconds. Then replace the battery.
Now press and keep holding the home button. Then press and hold the volume down button as well, then lastly the power button. Keep holding all three until the phone starts (about ten seconds).
Let me know if you do or don't get to the download mode screen when you do that.
If you don't, try it a second time, just in case you weren't continously holding all three keys to get into download mode.
If you still don't, then we want to ensure that the Kies program is not running (if you have Kies on your computer). Then try going to download mode again in the same manner as above, then plug the phone into your computer with the USB cable and start the Odin 3.09 program and tell me what you see on the Odin screen.
.
Click to expand...
Click to collapse
When i plug it in i get a news USB device named : ZUES Flash Device .
i have tried to Hold Home + Volume - + Power nothing happen.
Odin don't find it , and kies program is not running.
..
2015/10/07 The information below will be kept to help folks make backups and for linux/mac users to have some images to restore but if you have bricked your phone the recommended solution now is to install Alcatel's Mobile Q software version 4.9.2 or newer and use it to restore your phone to factory condition. Basically turn off the phone..plug it up to the pc via usb and run the software...it should prompt you from there. The link to download the software is here: http://alcatelonetouch.com/global-en/support/download/pixi_3_7_4g.html
*****Warning***** Recent updates from Alcatel have REMOVED the fastboot commands that allow root and custom recovery for some models of the 6039. Before updating read the details here: http://forum.xda-developers.com/showthread.php?t=3173598 and make sure the new update doesn't do the same!
You should also be aware that if your phone hangs on boot and you are rooted don't do a factory reset or you will lose adb access if you had it enabled which can be used to restore your phone
Table of Contents
Post #1: Intro
Post #2: Backup Instructions http://forum.xda-developers.com/showpost.php?p=62006344&postcount=2
Post #3: System Images http://forum.xda-developers.com/showpost.php?p=62006344&postcount=3
Post #4: Restore Instructions and firmware issues http://forum.xda-developers.com/showpost.php?p=62006344&postcount=4
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Folks, OTA updates for Lollipop check if your system has ever been mounted read/write (which is required to root) and if it has they do not allow the update to install. What that means is before you root you need to first go into fastboot and do a fastboot boot of TWRP (this boots twrp on your phone without installing it) then go into twrp and backup your system directory so you always have something to restore to if you want future OTA updates.
The bad news is that for folks who have already rooted, we need TWRP backups of the system partition for each model of the idol 3 BEFORE someone has rooted. 6045i, 6045k, 6045y...are there more?
If you have NOT yet rooted your phone and are willing to help out please post here with your model number(It shows in settings, about phone as Model Number). I'll add some instructions on how to take a backup then the backup needs to be uploaded online somewhere we can access it. The system partition is normally read only so it contains NONE of your personal information.
This paragraph from the TWRP documentation is taken from: https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.]
Here's an article that explains it better than I can: https://www.androidpit.com/android-5-0-lollipop-ota-update-fail
20150810 - Turns out all thats required to get updates at least for now is doing a FULL unroot. (That may not be the case with a major jump such as from 5.0.2 to 5.1.1) Failure to do a full unroot can result in boot loops after applying updates that currently DO NOT HAVE A SOLUTION because the default recovery for the 6045i and 6045Y do not have the reboot to bootloader option that IS present in the 6045K and all models of the 6039 Idol 3. Thanks Alcatel! An easier solution is to flash an already upgraded firmware if it is available. Canadian users have also found it useful to flash USA firmware (both have a 6045i) to get updates sooner than being released by the cell providers in canada.
Instructions to backup your system prior to rooting.
-Get/install Alcatel USB driver if Windows. (no need for Mac). FROM HERE: http://54.247.87.13/softwareupgrade/Driver/ALCATEL_ADB_ Driver Qualcomm_ADB.rar , or just connect your idol3 to the computer and from the phone select "cd rom" drive..it will install the drivers automatically
Windows and Mac users should have downloaded the android sdk to get adb and fastboot. [ https://developer.android.com/sdk/ ] Linux (ubuntu based) users should install packages android-tools-adb and android-tools-fastboot Windows users can try a minimal adb and fastboot install using the instructions here: http://forum.xda-developers.com/showthread.php?t=2317790 or here: http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
download twrp from here: https://www.androidfilehost.com/?fid=24052804347778862
-Set USB debugging on in Developer settings (if these are not exposed, go to Settings/About Phone/Build number, and tap 7 times.)
-Plug in USB cable to phone and computer. Tap on USB icon in notifications panel; select MTP (file transfer) mode or PTP also works fine.
-ON your pc open command prompt in the directory where you have placed twrp-2.8.7.0-idol3.img (when using windows in the directory hold shift and press the right button on the mouse, it will pop-up a window where you have to select "open command prompt here" and type "adb reboot-bootloader" to reboot into bootloader
-Then type "fastboot -i 0x1bbb devices" This should show the device
-Type "fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img" This will boot twrp on your phone without installing it.
-On your phone do a normal backup but make sure only "system image" (not system) and Boot (to keep the kernel in sync with the system) is checkmarked to be backed up. You can go into TWRP settings and have it write to the external_sd vs using internal "sdcard" before starting the backup if you have one installed
-After backup has completed it will have created a folder named TWRP on your /sdcard or /storage/sdcard1 depending on which you selected (/sdcard by default). Assuming this is your first use of twrp then copy the whole twrp folder over to your pc and zip or rar it then post a message with your model stating you have a backup and we'll work to get it uploaded. If you have previously used twrp and have multiple backups then just go one directory in "/sdcard/TWRP/" and backup only the directory with the date timestamp of your most recent backup.
When uploading to the cloud zip'ing or rar'ing the file will cut it's size by about half. (it's 3gb initially and roughly 900mb afterward) It's still a rather large file so you might look at http://www.filedropper.com/ to upload the file...they claim files allowed up to 5gb and no registration required. https://mega.co.nz is also a good alternative but can be slow. If you have suggestions for a better place to put the files please let me know.
If you are willing to contribute space that will not expire to host the system backups please contact me via pm. Make sure to hit thanks for our generous uploaders.
System Downloads Available [Each download is +- 1GB in size]
(Do not crossflash devices ie flash the 6045i image to a 6045K or 6045Y. We don't know what the results will be!):
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6045 (5.5 inch model)
From most recent back to "out of the box".
Model: 60450(USA-Cricket) Firmware: 5.0.2-010 03 Link: https://mega.nz/#!xhhy0AKC!hWhDgXCQOGt0cNHcfkkejEEBiP1pjOT5-ZK6mAY5MUU Thanks to squeakychu for the upload!
Model: 6045i(usa) Firmware: 5.0.2.7SRA-UEA2 Link: https://mega.nz/#!dRkgxA5L!z7yVmmgeUWBpAGwJW6ixnGhGBzUky1dfhKksu3yGPKg Thanks to Brian117 for the uploads! (09/28/2015)
Model: 6045i(usa) Firmware: 5.0.2.7SR4-UE40 Link: https://mega.co.nz/#!K9szRIKR!ZdjIiH2Ol0ZCNe2VTSl6cbRyQeZFtafG3Y9CM0ecCkg 20150810 md5sum: 56376824f7c10d8debaec6c3a7100e50
Model: 6045i(usa) Firmware: 5.0.2-7SQR-UER0 Link: https://mega.co.nz/#!FB0DQAhQ!rQ4H39hQR2tDhfniEej-RvsSe5OqWY42_xCsjY08o4k Thanks to buggleston for the upload!
Model: 6045i(usa) Firmware: 5.0.2-7SQ3-UE30 Link: https://mega.co.nz/#!focwnJJL!VQW3Omi3TF4iJzIyNLu73P9gb8i_WKA_fu7ZWUiIsN0 Thanks to Electriccars for the upload!
Model: 6045i(usa) Firmware: 5.0.2.7SMA-UEA1 Link: https://mega.nz/#!pdlWhQLR!D2-mEnxp2SnxH0QBDsSSZ-YrDooJC8BdKronYxziF_A Thanks to lordlittlebrooks for the upload!
Model: 6045i(canada) Firmware: 5.0.2-7SQB-UCB0 Link: https://mega.nz/#!opolxbIY!A9dEfORplfhkmuNwobKsEF2wX6yY3oLq8M9dgWpDNq8 Thanks to KryPTiCk0d3 for the upload!
Model: 6045i(canada) Firmware: 5.0.2-7SQ9-UV93 Link: http://drive.google.com/file/d/0B8Gqss1TYorTaXZrRFdBdDJ2Vnc/view Thanks to green3water5 for the upload!
Model: 6045K(Serbia, Bulgaria, Macedonia and maybe Cz) Firmware: 5.0.2-010 0101001 Link: https://mega.nz/#!L5El0QqA!IrxnA4qyXONyWehaJltc7JsE5TgaAXIdT9RQ73K0Rdw Thanks to bokaco7 and Nikola Jovanovic for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 06 Link: https://mega.nz/#!N9phSbTR!hH0bTJnHcUrwKxdpA-RKyecHNPKls7Cy0fi-Ih3BWkM Thanks to Gynoid for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 05 Link: https://mega.nz/#!pxgwXKIA!TInG7xK9Z-qObX1Cc3BObGp88zx0FCpWI3RDt_wdD0Q and https://mega.nz/#!l5xnSDrL!-y2ye27vODfNAR2qcBAQN7q0gGYA579iRzla07lFkd4 [You will need to flash both as one has the system backup and the other has the boot] Thanks to Gynoid for the upload!
Model: 6045Y(Europe) Firmware: 5.0.2-010 03 Link: http://mega.co.nz/#!CYk2mBCa!XJd1nJI1cUcTcGjwzhApcAyABQ8y54D-bATvgxxHMsE Thanks to zrkkrz for uploading this 2 times!
Model: 6045Y(Europe) Firmware: 5.0.2-010 01 Link: http://data.nettitoimisto.com/f/e308c56574/ Thanks to tommihut for the upload!
Other models not listed? NEEDED!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
All backups will eventually be mirrored to MEGA. If the file is missing I'm more than likely still trying to get it uploaded. MEGA can be slow however the files should never expire. The folder is here: https://mega.co.nz/#F!DgNhkDKR!GyJsku7nw4F6nLiT4XFRKA
If an individual download link is dead please let me know via post or pm.
Thanks to kirplunk and zrkkrz for uploading backups that ended up having to be replaced due to incorrect instructions to backup system instead of "system image" from within TWRP.
When using these backups.....
There is currently a bug in TWRP that appears to be showing 6045Y for ALL idol3 devices in the recovery.log so make SURE the system image you are flashing is meant for your device to the best of your ability.
Restoring a TWRP backup image:
If you wish to update to a newer firmware or restore an older one you can follow purple.epod's basic instructions here but use the firmware you want to restore: http://forum.xda-developers.com/showpost.php?p=62313284&postcount=1 Also make sure you restore both boot AND system image in the newer firmware's when selecting what to restore.
When restoring the UE40 firmware the first time you go into system update checker you need to delete the existing UE40 update as it kept it around...you should then be able to check updates as normal.
This was brought up in the main rooting thread, but you might also be able to unroot via SuperSU with the Full Unroot option. Haven't tried it yet but if it works, you can just unroot, install whatever OTA there may be, and re-root.
brian117 said:
This was brought up in the main rooting thread, but you might also be able to unroot via SuperSU with the Full Unroot option. Haven't tried it yet but if it works, you can just unroot, install whatever OTA there may be, and re-root.
Click to expand...
Click to collapse
Yeah, I'm the one who brought it up. I thought those about to root should be made aware.
Based on the twrp documentation it sounds like once it's been mounted once as read/write there is a way for them to check and it will kill the ota update. unrooting isn't going to fix that. We also have no good way to intercept the updates so we could alter them to install anyway. I used a squid transparent proxy to find the download url but won't do me any good if my phone can't download the update. If it lets the phone dwonload and then when it runs aborts I may still be able to grab the url and the update could be modified to apply anyway.
tried to upload stock system backup for 6045i
famewolf said:
Reserved 1
Click to expand...
Click to collapse
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
---------- Post added at 01:51 AM ---------- Previous post was at 01:34 AM ----------
famewolf said:
Folks, OTA updates for Lollipop check if your system has ever been mounted read/write (which is required to root) and if it has they do not allow the update to install. What that means is before you root you need to first go into fastboot and do a fastboot boot of TWRP (this boots twrp on your phone without installing it) then go into twrp and backup your system directory so you always have something to restore to if you want future OTA updates.
The bad news is that for folks who have already rooted, we need TWRP backups of the system partition for each model of the idol 3 BEFORE someone has rooted. 6045i, 6045k, 6045y...are there more?
If you have NOT yet rooted your phone and are willing to help out please post here with your model number(It shows in settings, about phone as Model Number). I'll add some instructions on how to take a backup then the backup needs to be uploaded online somewhere we can access it. The system partition is normally read only so it contains NONE of your personal information.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.]
Click to expand...
Click to collapse
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
kirplunk said:
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
---------- Post added at 01:51 AM ---------- Previous post was at 01:34 AM ----------
i have backed up the stock system twrp backup for 6045i zipped in folder then tried your file link to up load, after about 15 minutes it was still uploading seemed to long so i stopped the upload. do you or dallascz have another place to upload or email maybe? i still have not installed the recovery or rooted yet, trying to give back to Idol3ers.
Click to expand...
Click to collapse
kirplunk, how large is the file after you have zipped it? I'll check into some more services. I'm limited by the fact I don't have hi speed and I don't think xda rules allow me to mention any file sharing service that requires registration. If you do a google of "upload large file" and find a service that works for you let me know. If others have a suggestion also let me know. I'm reply back as soon as I find some other sites. Thanks for your assistance!
*update* In other areas of XDA they suggest https://mega.co.nz/ for large file uploads however it would require creating your own account. They give you 50GB. Let me know if this works for you please.
size reply
famewolf said:
kirplunk, how large is the file after you have zipped it? I'll check into some more services. I'm limited by the fact I don't have hi speed and I don't think xda rules allow me to mention any file sharing service that requires registration. If you do a google of "upload large file" and find a service that works for you let me know. If others have a suggestion also let me know. I'm reply back as soon as I find some other sites. Thanks for your assistance!
Click to expand...
Click to collapse
the unzipped folder with files was 2.1gb in size, the zipped folder with files that i tried to upload is 855mb in size. i do not use the cloud at all so i don't have a drop box or any thing of the type. the site you referenced said it was uploading but it seemed 15 minutes was more than enough time for that size of file. my browser kept saying it was uploading and connecting to site.
kirplunk said:
the unzipped folder with files was 2.1gb in size, the zipped folder with files that i tried to upload is 855mb in size. i do not use the cloud at all so i don't have a drop box or any thing of the type. the site you referenced said it was uploading but it seemed 15 minutes was more than enough time for that size of file. my browser kept saying it was uploading and connecting to site.
Click to expand...
Click to collapse
Can you please try https://mega.co.nz/ and see if it works better for you? It will require creating an account but they will give you 50GB and you could use a disposable email address if you prefer. I'm checking other areas of xda to see how they handle large file uploads and this is what I've seen so far.
I have no problem sharing one I've created but there will always be that one person who wants to come along and delete everything in it.
Another is http://www.filedropper.com/ which allows up to 5gb files and keeps them till 30 days of not being downloaded. No registration required.
Also is your backup after the two system updates? Just FYI your upload bandwidth is not going to be as high as your download typically so uploads of large files can take a while.
attempting the second site now, called file dropper.
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
100% uploaded,
as a junior member this is the best i can do for the link.
www dot filedropper dot com/6045itwrpstocksystembackup
hope this helps
Uploads tend to be much slower than downloads. LTE connections are an exception, but cable and DSL upstream speeds aren't fast.
kirplunk said:
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
Click to expand...
Click to collapse
Feel free to send me the link in a PM and I'll post it so others can download it in addition to me or I'm sure I can find it based on filename if they have search.
With your permission I'll put it in post #3 with your name and a thank you. I'll have to visit the local library that has rather fast internet to get these files downloaded and moved to one folder for everyone assuming others share theirs as well.
So using stock recovery to Wipe Data/Factory Reset back to new doesn't remove root or r/w status?
mk3 said:
So using stock recovery to Wipe Data/Factory Reset back to new doesn't remove root or r/w status?
Click to expand...
Click to collapse
A factory reset wipes the data and cache partitions. It does nothing to /system since it expects it to be read only.
famewolf said:
A factory reset wipes the data and cache partitions. It does nothing to /system since it expects it to be read only.
Click to expand...
Click to collapse
ahhh.... bummer. Thanks for the clarification.
So I used Hide My Root to hide su binary and the system update doesn't give me the error (like all is fine). Prior to hiding the su binary it throws the error about being rooted.
.
Is the /system partition different than the /system directory that's in the root of the device? If it's the same, we can change the read/write permissions with ES File Explorer if the device is rooted? I'm not sure if it'll offer us the chance, if we want it, to make all the contents of the dir have the same permissions we set for the dir itself. Can the same thing be done from a command line in TWRP?
Why does TWRP show "system" and "system image" as two different options and sizes to backup? I've never seen that before.
maigre said:
Is the /system partition different than the /system directory that's in the root of the device? If it's the same, we can change the read/write permissions with ES File Explorer if the device is rooted? I'm not sure if it'll offer us the chance, if we want it, to make all the contents of the dir have the same permissions we set for the dir itself. Can the same thing be done from a command line in TWRP?
Click to expand...
Click to collapse
The system partition is the same as the /system folder however it's not a file permission that's an issue and you'd never want to set all your files to the same permissions. Here is an article that explains it better than I can: https://www.androidpit.com/android-5-0-lollipop-ota-update-fail
kirplunk said:
the file folder i'm uploading is called, 6045i twrp stock system backup.7z
upload is at 10% right now
now at 20%, yes with updates firmware is 5.0.2-7sqr-uero
30% my upload speed should put this file up in 3 minutes but their server is taking it like sucking coffee up through a stir stick, slow
will update when it reaches 100%, but as a junior member i can not post links so you will have to find it at the file dropper.
100% uploaded,
as a junior member this is the best i can do for the link.
www dot filedropper dot com/6045itwrpstocksystembackup
hope this helps
Click to expand...
Click to collapse
Thanks kirplunk! I've got it downloading and will add my folder as a mirror to try to prevent the file from expiring.
1. Go to secret menu of your phone (*#546368#*850#)
2. Tap SVC menu, then Version Info.
3. In Version info find NT Code.
4. Change wbatever code you have there to "1","FFF,FFF,FFFFFFFF,FFFFFFFF,11" - that is open europe.
After pasting the above code, the NT Code should display something like code write done, or similar, instead of your old NT Code.
This info is from MrBeem, he sent to me. I have this error but it did not work for me, i get Write Error maybe because i I dont have root. If you are rooted can work for you.
I get write error too. I think you have to have root to make this work.
Talking of which, has anyone got root on 7.0 yet?
stuclark said:
I get write error too. I think you have to have root to make this work.
Talking of which, has anyone got root on 7.0 yet?
Click to expand...
Click to collapse
From Mrbeem:
Hello. Got an update on the version error you have/had.
1. yes, you do have to be rooted, to get root u must het twrp-3.2.0-1-beta1-H850.img and SuperSu2.78 SR4. You flash twrp via minimal adb and fastboot, instructions on XDA forum, after flash, pull battery out, back in and you MUST get to recovery by Vol Down+POWER combination and you only get 1 try. If you don't manage to get to recovery and your system starts booting, you must flash twrp all over again. Once in TWRP, press skip if it prompts for password, enable read/write by swiping right, and install SuperSu zip file you have to have on your external sd card. With all that done, reboot and voila, you're rooted.
2. After boot, go to hidden menu, to ntcode. In the ntcode put "1","FFF,FFF,FFFFFFFF,FFFFFFFF,FF" notice, last 2 are FF, not 11. you should get NTCODE WRITE OK
3. with root acces granted go to cust folder and enable R/W option. I recommend using root explorer 4.0.4
4. Check subfolder list in cust folder. You will have folders like VDF_OP, EUR_OP or something like that. Pick any and memorize its name. this will become your soft ver. after you finish.
5. Find file named cust_path_mapping.cfg and open it with TEXT EDITOR!
6. at the end of the document, add a following line: FFFFFF,FF=/cust/name of subfolder in cust folder you memorized in step 4
7. save file, close it and reopen to check if your added line sticks. if it doesn't you haven't pressed "mount R/W" button in root explorer. Press "mount R/W" and repeat steps 5 to 7 .
8. Reboot, and now you should get your system branded (if you chose a specific carrier subfolder in /cust) or no brand and no version error (if you chose open europe in /cust).
Error
yken said:
From Mrbeem:
Hello. Got an update on the version error you have/had.
1. yes, you do have to be rooted, to get root u must het twrp-3.2.0-1-beta1-H850.img and SuperSu2.78 SR4. You flash twrp via minimal adb and fastboot, instructions on XDA forum, after flash, pull battery out, back in and you MUST get to recovery by Vol Down+POWER combination and you only get 1 try. If you don't manage to get to recovery and your system starts booting, you must flash twrp all over again. Once in TWRP, press skip if it prompts for password, enable read/write by swiping right, and install SuperSu zip file you have to have on your external sd card. With all that done, reboot and voila, you're rooted.
2. After boot, go to hidden menu, to ntcode. In the ntcode put "1","FFF,FFF,FFFFFFFF,FFFFFFFF,FF" notice, last 2 are FF, not 11. you should get NTCODE WRITE OK
3. with root acces granted go to cust folder and enable R/W option. I recommend using root explorer 4.0.4
4. Check subfolder list in cust folder. You will have folders like VDF_OP, EUR_OP or something like that. Pick any and memorize its name. this will become your soft ver. after you finish.
5. Find file named cust_path_mapping.cfg and open it with TEXT EDITOR!
6. at the end of the document, add a following line: FFFFFF,FF=/cust/name of subfolder in cust folder you memorized in step 4
7. save file, close it and reopen to check if your added line sticks. if it doesn't you haven't pressed "mount R/W" button in root explorer. Press "mount R/W" and repeat steps 5 to 7 .
8. Reboot, and now you should get your system branded (if you chose a specific carrier subfolder in /cust) or no brand and no version error (if you chose open europe in /cust).
Click to expand...
Click to collapse
Can't pass the step 2, it gives an error.
fmartins29 said:
Can't pass the step 2, it gives an error.
Click to expand...
Click to collapse
You can flash your countries Rom, not EU
I've installed TWRP ans SuperSU as shown above, but I still get Write Error.
Looking in the SuperSU app, it says under "Install SuperSU into /system" - "Not (currently) available in system-less mode".
How can I fix the SuperSU issue, as I'm guessing that's why I haven't got write access to the NTT code?
Hi. What exactly do you get in your ntcode error? Mine was FFFFFF,FF is not a proper code or something like that. Now, if your error is something else but not '0', you can just do the following:
1. Memorize or write down your error code ( in my case it was FFFFFF,FF)
2. go to /cust folder, mount it as R/W
3. Check what carrier subfolders folders you have in your cust solder (i had OPEN_EU, P4P_PL and a couple more)
4. Open file cust_path_mapping.cfg with TEXT EDITOR
5. Change the number/letter string before = of your desired carrier in the above mentioned cfg file to whatever it says in your ntcode error (my error message said FFFFFF,FF, i wanted the P4P_PL to be my carrier so i changed 26006,06=/cust/P4P_PL to FFFFFF,FF=/cust/P4P_PL).
6. Save changes, close, reopen the cfg file to check if your changes stick (if not, make sure you've enabled the R/W option in your cust folder).
7. Reboot
This should fix your problem. I tried this on 5 different devices and always worked.
Help changing NT using SVC menu
yken said:
You can flash your countries Rom, not EU
Click to expand...
Click to collapse
The NT code showing for me on my LG G5 H850 from the SVC menu is
"3","234,30F,
28000000,FFFFFFFF,FF","234,38F,
28000000,FFFFFFFF,FF","234,33F,
28000000,FFFFFFFF,FF"
(I'm on UK Virgin I believe - 234,38) and my stock Android 7.0 Rom is H85020k_00_VMC_GB_OP_0501.kdz Now,
I want to update to Oreo using the open EU oreo kdz H85030a_00_OPEN_EU_OP_0910.kdz as an upgrade file is not yet available for my phone but I get the customer not found errors on boot even if I first flash the phone using the original stock open EU Android 7.0 file H85020a_00_OPEN_EU_OP_1030.kdz.
I have my phone unlock code so if I unlock the bootloader will that allow me to enter a new NT code in the SVC menu to stop the customer error message without me having to root the phone and edit the root CUST folder? Thanks in anticipation.
wimmerfield said:
The NT code showing for me on my LG G5 H850 from the SVC menu is
"3","234,30F,
28000000,FFFFFFFF,FF","234,38F,
28000000,FFFFFFFF,FF","234,33F,
28000000,FFFFFFFF,FF"
(I'm on UK Virgin I believe - 234,38) and my stock Android 7.0 Rom is H85020k_00_VMC_GB_OP_0501.kdz Now,
I want to update to Oreo using the open EU oreo kdz H85030a_00_OPEN_EU_OP_0910.kdz as an upgrade file is not yet available for my phone but I get the customer not found errors on boot even if I first flash the phone using the original stock open EU Android 7.0 file H85020a_00_OPEN_EU_OP_1030.kdz.
I have my phone unlock code so if I unlock the bootloader will that allow me to enter a new NT code in the SVC menu to stop the customer error message without me having to root the phone and edit the root CUST folder? Thanks in anticipation.
Click to expand...
Click to collapse
Just wondered if you got any further with this? Oreo is now released for VM branded G5, but I'm wanting to use my VM branded phone on Three with WiFi calling. I was thinking about changing 1 of the 3 NT Codes (30,33,38) to 20 for Three but not sure if that's the best path forwards.
No progress with changing NT code
cancunia said:
Just wondered if you got any further with this? Oreo is now released for VM branded G5, but I'm wanting to use my VM branded phone on Three with WiFi calling. I was thinking about changing 1 of the 3 NT Codes (30,33,38) to 20 for Three but not sure if that's the best path forwards.
Click to expand...
Click to collapse
Sorry - I wasn't able to resolve that issue but as you say the G5 has now received its Oreo upgrade which is really all I wanted. Good luck anyway
Thank you! It worked for me. I have an h850ar running Android 8.0 without root. Finally the damn sign went away every time I started my phone ...
my device 860 h GCC middle East
I FLASH OREO VERSION sg (Singapore)
everything is work but ( NTCODE) PROBLEM ? ANY solution ? your discussion work for my device?
thank you
sorry bad English ?
WARNİNG
1 - WARNİNG - Current version is not available for user. Can't find matched cust for NTCODE = (23430,02)
2- WARNİNG _ Current OP name by Buyer-code is (EEO_GB). But cannot find matched NT-code mcc/mnc (23430), subset (02)
Telefon yeniden başlatıldığında bu hatalar çıkıyor bir çözüm var mı acaba LG G5 H850 model cihaz
Did anyone work out how to change the NT Code via the hidden menu? I tried downgrading to Marshmallow but still get a write error.
Thanks
This is a solution that worked for me, on a Wind branded phone with an OPEN_EU rom (root required):
go to /cust/ folder and edit cust_path_mapping.cfg, adding a new line with the code you see in the NTCODE error (22288,FF in my case), pointing it to the OPEN_COM folder:
22288,FF=/cust/OPEN_COM
Then do the same with open_path_mapping.cfg, but here you should put OPEN_EU instead of OPEN_COM:
22288,FF=OPEN_EU
Then, after saving both files, reboot the phone, and the NTCODE error will be gone.
Hi,
I've been using some custom Lineage with my S8 SM-G950F which worked for for a while and now I'm trying to get back to stock, usually its quite simple download the firmware from Sammobile and flash it with Odin.
I did it and it seem to work perfectly, download the latest version G950FXXSADTI1_G950FOXMADTI1_ITV, my phone is from Italy and bough directly from samsung.
I flashed with Odin 3.14 pointing the 4 files, used the CSC not the HOME one, clean everything, no errors.
I started to install things and after installed most of the stuff I try to add my Credit Cards to Google Pay and it does not let me do it and tell me it is a rooted phone and I could not do add credit cards.
Netflix doesn't even appear on PlayStore to donwload.
Everything works fine, I tried to reflash a couple of times with no success
Only thing strange is when I enter into recovery, it gives me some errors as bellow:
#fail to open recovery cause (no such file or directory)# --> the cause would be me holding keys while starting the phone I believe
Supported API: 3
e: unknow voulme for path [/odm]
e: unknow voulme for path [/vendor]
e: unknow voulme for path [/odm]
e: unknow voulme for path [/vendor]
#MANUAL MODE v1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT (no such file or directory)
can't open directory /system/omc/SUP/
....some others similar lines
E:[libfs_mgr]is_dt_compatible() firmware info not valid : '/proc/device-tre/firmware/android/compatible: no such file or directory
IF someone can help me here, I appreciate
Solved, just closed the bootloader.. Silly of me to forget it
Thanks anyway.