Related
I tried manualy updating my I9000 to gingerbread through odin. the update fail however and now kies wont reccognise my phone. when i try to boot the phone it show a picture with a phone, a pc and an exclamation mark. what should i do?
Since u can see that pc icon means u can get into download mode also... Ie volume down + home + power... Now see that biggest file frm ur download ie pda/code......tar has the boot.bin and sbl.bin files... If yes just reflash it again... If now download sme othr gingerbread version with those two files and flash... just search for ramads thread in this section...
I mean this thread...
http://forum.xda-developers.com/showthread.php?t=1102881
thank you. i was trying to find that thread lol. Is going from eclair to gingerbread going to work or not? trying to find what the problem was.
If you're going between major versions you should do a factory reset (clear the /data section) as your apps may work differently and take advantage of new features. Not doing a factory reset may cause certain apps to FC.
Should work going straight from E to G though.
cheers guys. got everything working now.
Hi, may i know what happen if i can't go into download mode? But i still have the pc image.
Any solution?
fuuuuuuuuuuuuuuuuuuu. i think i have finaly ****ed up my phone. my dad accidently turned off my pc while i was flashing a galnet miui build with heimdall. i got into download mode but had to go out. when i came back my battery was dead and i cant charde the phone or get it into download mode. Any suggestions ?
edit: got it into download mode but odin doesnt recognise it
Try this:
prerequisite : the tools I used will only work on linux, so get yourself a ubuntu, or run one using virtual machine on windows, also install java (running sudo apt-get install openjdk-7-jre should be enough).
download UnBrickable Ressurector, code . google . com/p/hummingbird-hibl/downloads/list -> this is the reason for ubuntu only
run the downloaded jar file using sudo (it need root permission to run properly).
remove your phone battery, plug the usb cable in (connected to your computer), then reinsert your phone battery
now you have about 2s windows of opportunity to click that "Perform Ressurection" button.
wait and your phone should now be in download mode.
now this download mode is a bit weird.. if you unplug the usb cable, the phone will go straight back to the blank screen, and you have to do the whole process all over again.. which is why, we're going to reflash and fixed the phone using heimdall. the flashing process is a bit different with odin, here's how :
download heimdall www glassechidna com au/products/heimdall/ and the frontend
open it using sudo (sudo heimdall-frontend)
extract the rar files you got here, and you will get 3 tar.md5 files.
extract all those files, BUT make sure that you extract the csc files LAST, also choose OK when you're asked to overwrite. you will get 8 files
now we're going to download the correct pit file : in heimdall choose the "utilities" tab, click on "detect", and it should print out "device detected". click save as, choose a name (don't need to put .pit as part of its name), and click download
switch to "flash" tab, then browse for the created pit file. the "add" button should be enabled now.
now you need to add all the extracted files one by one and it has to be in the correct partition name, here's the list :
kernel -> zImage
IBL + PBL -> boot.bin
CACHE -> cache.rfs
dbdatafs -> dbdata.rfs
factoryfs -> factoryfs.rfs
modem -> modem.bin
param -> param.lfs
SBL -> Sbl.bin
hit start, and the flashing should start. if all goes well, your phone should boot normally now
stef.t97 said:
edit: got it into download mode but odin doesnt recognise it
Click to expand...
Click to collapse
Gadget serial at Devica Manager - missing driver files, install SAMSUNG_USB_Driver_for_Mobile_Phones
Heimdall is an open-source alternative to flashing firmware to devices. It claims to be safer and a better alternative to Odin pretty much.
Although Heimdall is safer, it is still a firmware flashing tool, and like all firmware flashing tools, there could be dire consequences for not following instructions. I take no responsibility for what unexpected results or damage that may happen when following this guide. (I followed this guide on my tab though and it worked great)
- You should probably backup all important data prior to using Heimdall
First, you'll have to acquire Heimdall. You can find Heimdall releases and information here: http://www.glassechidna.com.au/products/heimdall/
- Heimdall is for Windows, OS X, and Linux
- I recommend using the command-line version over the GUI
zImage Guide
Note: For flashing of just the kernel to your device
- Command for flashing zImage
Code:
heimdall flash --kernel zImage --verbose
Files Needed:
zImage
ROM, Kernel, Modem, etc. Guide
Note: For flashing a ROM, Kernel, and Modem to your device, or for "re-stocking"
- Command for flashing complete ROM, Kernel, and Modem
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
Files Needed for Command Above:
gt-p1000_mr.pit (partitioning)
modem.bin (modem)
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs (file-system or ROM?)
param.lfs
Sbl.bin
zImage (kernel)
From this point on, this will mostly be a Windows-based guide. I'll use a Samsung Galaxy Tab 7" P1000 GSM and I'll re-stock using files from Overcome, and then flash the Overcome kernel afterwards. You may have to modify parts of the guide for different devices, kernels, ROMs, Operating Systems, etc.
Windows Driver Preparation
1. Install Samsung's Drivers (SAMSUNG_USB_Driver_for_Mobile_Phones.msi either from Kies or SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe from GB-Stock-Safe-v5.zip)
Note: You should reboot your computer after installing, even if it doesn't tell you to. Drivers wouldn't initialize until I rebooted.
2. Connect your Tab to your computer at least once in Normal, Recovery, and Download mode so that all drivers initialize
3. Reboot your tab to Download mode
4. Run zadig.exe
5. Go to Options > List All Devices
6. Select Samsung USB Composite Device from the dropdown box
7. Click Install Driver (accept any unsigned driver prompts you get)
8. Once Zadig says the drivers are installed successfully, close it
Windows Flashing Preparation
1. Make a folder specifically for Heimdall someplace safe
2. Copy heimdall.exe and libusb-1.0.dll to the Heimdall folder
3. Acquire GB-Stock-Safe-v5.zip, and Overcome_Kernel_v4.0.0.tar
4. Extract the contents of GB-Stock-Safe-v5.zip in a folder somewhere
Note: In the GB-Stock-Safe-v5.zip extracted folder should at least be modem folders, gt-p1000_mr.pit, and GB_Stock_Safe_v5.tar
5. Take the modem.bin from the modem of your choosing and throw it in the Heimdall folder
6. Take gt-p1000_mr.pit and throw it in the Heimdall folder
7. Extract the contents of GB_Stock_Safe_v5.tar into the Heimdall folder
Note: You should have 13 files total equaling around 391MB
Windows Flashing (Re-stocking)
1. Reboot your tab into Download mode
2. Connect it to your PC with the same USB port you used to prepare drivers
3. Open Command Prompt
4. cd into the Heimdall folder
5. Type (or copy/paste)
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
and press Enter
Note: This will take maybe 2 minutes, but quicker then Odin
Note: When flashing is complete, tab will automatically reboot
Note: You will have to manually wipe caches and factory reset from Recovery if you see it fails to mount /data on initial boot (if you see red text, then it failed)
6. When tab finishes booting, complete the Setup Wizard
Note: If you are going to flash another ROM (such as icedBOCA, CM9, etc), then just press Next through all of setup. Language will be Italian, but this does not matter for now
Note: If you just want to return to a pure factory state, this is as far as you should go
Note: This does not seem to wipe the internal SD card. For the cleanest experience possible, I recommend manually formatting the internal SD card right after the Setup Wizard
Windows Flashing (Overcome Kernel)
Note: This will convert partitions to ext4 and give you CWM recovery
Note: This is to be done after you have re-stocked
1. Acquire Overcome_Kernel_v4.0.0.tar
Note: You should have this already if you followed Windows Flashing Preparation
2. Copy heimdall.exe and libusb-1.0.dll to a new Heimdall folder
Note: Or use the same Heimdall folder you had previously
Note: I'll refer to the new folder as Heimdall2
3. Extract the zImage file from Overcome_Kernel_v4.0.0.tar to the Heimdall2 folder
4. Reboot your tab into Download mode
5. Connect it to your PC with the same USB port you used to prepare drivers
6. Open Command Prompt
7. cd into the Heimdall2 folder
8. Type (or copy/paste)
Code:
heimdall flash --kernel zImage --verbose
Note: This should take less then 5 seconds
Note: Your tab should automatically reboot when completed
9. Your tab should now convert partitions to ext4
Note: This is known as the Voodoo lagfix
Note: You will be stuck on the SGT bootscreen until this process is done
Note: You will hear a "sexy" voice telling you the steps of the ext4 process
Note: This process should take maybe 3-5 minutes
Note: Your tab will automatically reboot when complete, so you can walk away if needed
10. You are now on Gingerbread with Overcome kernel
- From this point on, you can now proceed to install (most, if not all) any compatible ROM/Kernel you want
- You should not need Heimdall from this point on also, as most ROM's and Kernels offer .zip packages that can be flashed from CWM/Recovery
Note: For any new ROM you flash, I recommend doing a data wipe afterwards, that way, you can gain access to the Setup Wizard and properly setup your Google Account, Market Sync, etc.
Windows Troubleshooting and Q&A
Q: I get a libusb error when trying to flash anything with Heimdall
A: This is due to either improper driver installation or using another USB port then the one you used to install the drivers
Note: You have to use zadig
Note: I would recommend uninstalling all previous USB filter drivers as well if you have problems
Q: Is it possible to use both Heimdall and Odin?
A: Yes, but it is recommended to have two USB ports. Do the zadig driver install on one USB port, and that port will be for Heimdall, and the second USB port will be untouched, and you'll be able to use Odin on it
Note: You cannot use Heimdall and Odin on the same port without uninstalling/installing the libusb filter driver from zadig that Heimdall needs
Q: Is Heimdall really faster then Odin?
A: Indeed. It's faster to start the flashing process, and faster to flash in-general. For instance, to re-stock my tab, I simply plug it into my Heimdall USB port, run a batch file (simply containing the command used above), and it's re-stocked in about 1 minute. With Odin, you have to manually select the files, and then flashing itself takes 2-3 minutes.
it would appear Heimdall does not work on Windows Consumer Preview (zadig fails, saying the OS rejects unsigned drivers)
Good tutorial, thanks.
Is this tool only feasible for Samsung devices, or also for most other Android ones?
Two annoyances from this tool:
1. It does not have some facility (like a specific command line option) to reveal to the user that the connection to a "download mode" device (i.e., no way to tell if the driver is working)
2. After the --print-pit option (I used this to confirm that the communication is setup properly) will reboot the device, I think just printing something will cause a device reboot is extremely unexpected...
By the way, your title seems to misspelled the keyword "heimdall".
factoryfs.rfs is the Factory installed filesystem and its the main rom
I have data.img... where I put it? datafs?
I am using heimdall frontend 1.3.1
what to do if wipe cache and recovery fail, the red text mount data? I followed all your steps but still stuck at samsung screen.
How to flash hidden.rfs by heimdall?
Sent from my GT-P1000
goofey2012 said:
How to flash hidden.rfs by heimdall?
Sent from my GT-P1000
Click to expand...
Click to collapse
--hidden hidden.rfs
zeroxia said:
annoyances from this tool:
1. It does not have some facility (like a specific command line option) to reveal to the user that the connection to a "download mode" device (i.e., no way to tell if the driver is working)
By the way, your title seems to misspelled the keyword "heimdall".
Click to expand...
Click to collapse
heimdall detect
zeroxia said:
2. After the --print-pit option (I used this to confirm that the communication is setup properly) will reboot the device, I think just printing something will cause a device reboot is extremely unexpected...
Click to expand...
Click to collapse
heimdall print-pit --no-reboot
Thanks!!!
heimdall syntax / files confusion
Hello all.
I imagine this is a noob question but I am stuck and reluctant to flash random files in hopes of getting it right.
I have these files from an extracted tar.md5 (T999UVDLJA_T999TMBDLJA_T999UVDLJA_HOME.tar.md5).
I'm trying to use heimdall to restore a SGS3 (d2tmo/T999) with a Stock ROM without bumping the flash counter. I only use Linux, so...
aboot.mbn
boot.img
cache.img.ext4
NON-HLOS.bin
recovery.img
rpm.mbn
sbl2.mbn
sbl3.mbn
SS_DL.dll (not needed, eh?)
system.img.ext4
tz.mbn
But I do not know what to do with the "*.mbn" files or the "NON-HLOS.bin"
I'm guessing the syntax is something like:
heimdall flash --primary-boot boot.img --cache cache.img.ext4 --recovery recovery.img --factoryfs system.img.ext4 ...
But I have a lot of files left over. Would someone kindly confirm that part is correct and fill in the rest of the blanks?
$ heimdall version
v1.4 RC1
Thank you for your time,
this is actually a Galaxy Tab 7" forum.
But anyway, your questions was answered (somewhat) by the heimdall author
https://github.com/Benjamin-Dobell/Heimdall/issues/82
look for the last comment
Thank you
priyana said:
this is actually a Galaxy Tab 7" forum.
But anyway, your questions was answered (somewhat) by the heimdall author
look for the last comment
Click to expand...
Click to collapse
Thank you -- and sorry about that.
I just saw the title and didn't pay attention to the device model.
My bad.
Jesus is a prophet
GoSooners345 said:
factoryfs.rfs is the Factory installed filesystem and its the main rom
Click to expand...
Click to collapse
Thanks alot will try
What will happen if in heimdall i choose the 512.pit file with re-partition ticked and flash my SGS?
Will i have to install a stock rom, then a GB and lastely the latest rom of my preference?
Send me link for zadig file .thqnkx in advance
Sent from my GT-P1000 using xda app-developers app
CM 10.1 flashing feedback
espionage724 said:
Heimdall is an open-source alternative to flashing firmware to devices. It claims to be safer and a better alternative to Odin pretty much.
Although Heimdall is safer, it is still a firmware flashing tool, and like all firmware flashing tools, there could be dire consequences for not following instructions. I take no responsibility for what unexpected results or damage that may happen when following this guide. (I followed this guide on my tab though and it worked great)
- You should probably backup all important data prior to using Heimdall
First, you'll have to acquire Heimdall. You can find Heimdall releases and information here: http://www.glassechidna.com.au/products/heimdall/
- Heimdall is for Windows, OS X, and Linux
- I recommend using the command-line version over the GUI
zImage Guide
Note: For flashing of just the kernel to your device
- Command for flashing zImage
Code:
heimdall flash --kernel zImage --verbose
Files Needed:
zImage
ROM, Kernel, Modem, etc. Guide
Note: For flashing a ROM, Kernel, and Modem to your device, or for "re-stocking"
- Command for flashing complete ROM, Kernel, and Modem
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
Files Needed for Command Above:
gt-p1000_mr.pit (partitioning)
modem.bin (modem)
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs (file-system or ROM?)
param.lfs
Sbl.bin
zImage (kernel)
From this point on, this will mostly be a Windows-based guide. I'll use a Samsung Galaxy Tab 7" P1000 GSM and I'll re-stock using files from Overcome, and then flash the Overcome kernel afterwards. You may have to modify parts of the guide for different devices, kernels, ROMs, Operating Systems, etc.
Windows Driver Preparation
1. Install Samsung's Drivers (SAMSUNG_USB_Driver_for_Mobile_Phones.msi either from Kies or SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe from GB-Stock-Safe-v5.zip)
Note: You should reboot your computer after installing, even if it doesn't tell you to. Drivers wouldn't initialize until I rebooted.
2. Connect your Tab to your computer at least once in Normal, Recovery, and Download mode so that all drivers initialize
3. Reboot your tab to Download mode
4. Run zadig.exe
5. Go to Options > List All Devices
6. Select Samsung USB Composite Device from the dropdown box
7. Click Install Driver (accept any unsigned driver prompts you get)
8. Once Zadig says the drivers are installed successfully, close it
Windows Flashing Preparation
1. Make a folder specifically for Heimdall someplace safe
2. Copy heimdall.exe and libusb-1.0.dll to the Heimdall folder
3. Acquire GB-Stock-Safe-v5.zip, and Overcome_Kernel_v4.0.0.tar
4. Extract the contents of GB-Stock-Safe-v5.zip in a folder somewhere
Note: In the GB-Stock-Safe-v5.zip extracted folder should at least be modem folders, gt-p1000_mr.pit, and GB_Stock_Safe_v5.tar
5. Take the modem.bin from the modem of your choosing and throw it in the Heimdall folder
6. Take gt-p1000_mr.pit and throw it in the Heimdall folder
7. Extract the contents of GB_Stock_Safe_v5.tar into the Heimdall folder
Note: You should have 13 files total equaling around 391MB
Windows Flashing (Re-stocking)
1. Reboot your tab into Download mode
2. Connect it to your PC with the same USB port you used to prepare drivers
3. Open Command Prompt
4. cd into the Heimdall folder
5. Type (or copy/paste)
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
and press Enter
Note: This will take maybe 2 minutes, but quicker then Odin
Note: When flashing is complete, tab will automatically reboot
Note: You will have to manually wipe caches and factory reset from Recovery if you see it fails to mount /data on initial boot (if you see red text, then it failed)
6. When tab finishes booting, complete the Setup Wizard
Note: If you are going to flash another ROM (such as icedBOCA, CM9, etc), then just press Next through all of setup. Language will be Italian, but this does not matter for now
Note: If you just want to return to a pure factory state, this is as far as you should go
Note: This does not seem to wipe the internal SD card. For the cleanest experience possible, I recommend manually formatting the internal SD card right after the Setup Wizard
Windows Flashing (Overcome Kernel)
Note: This will convert partitions to ext4 and give you CWM recovery
Note: This is to be done after you have re-stocked
1. Acquire Overcome_Kernel_v4.0.0.tar
Note: You should have this already if you followed Windows Flashing Preparation
2. Copy heimdall.exe and libusb-1.0.dll to a new Heimdall folder
Note: Or use the same Heimdall folder you had previously
Note: I'll refer to the new folder as Heimdall2
3. Extract the zImage file from Overcome_Kernel_v4.0.0.tar to the Heimdall2 folder
4. Reboot your tab into Download mode
5. Connect it to your PC with the same USB port you used to prepare drivers
6. Open Command Prompt
7. cd into the Heimdall2 folder
8. Type (or copy/paste)
Code:
heimdall flash --kernel zImage --verbose
Note: This should take less then 5 seconds
Note: Your tab should automatically reboot when completed
9. Your tab should now convert partitions to ext4
Note: This is known as the Voodoo lagfix
Note: You will be stuck on the SGT bootscreen until this process is done
Note: You will hear a "sexy" voice telling you the steps of the ext4 process
Note: This process should take maybe 3-5 minutes
Note: Your tab will automatically reboot when complete, so you can walk away if needed
10. You are now on Gingerbread with Overcome kernel
- From this point on, you can now proceed to install (most, if not all) any compatible ROM/Kernel you want
- You should not need Heimdall from this point on also, as most ROM's and Kernels offer .zip packages that can be flashed from CWM/Recovery
Note: For any new ROM you flash, I recommend doing a data wipe afterwards, that way, you can gain access to the Setup Wizard and properly setup your Google Account, Market Sync, etc.
Windows Troubleshooting and Q&A
Q: I get a libusb error when trying to flash anything with Heimdall
A: This is due to either improper driver installation or using another USB port then the one you used to install the drivers
Note: You have to use zadig
Note: I would recommend uninstalling all previous USB filter drivers as well if you have problems
Q: Is it possible to use both Heimdall and Odin?
A: Yes, but it is recommended to have two USB ports. Do the zadig driver install on one USB port, and that port will be for Heimdall, and the second USB port will be untouched, and you'll be able to use Odin on it
Note: You cannot use Heimdall and Odin on the same port without uninstalling/installing the libusb filter driver from zadig that Heimdall needs
Q: Is Heimdall really faster then Odin?
A: Indeed. It's faster to start the flashing process, and faster to flash in-general. For instance, to re-stock my tab, I simply plug it into my Heimdall USB port, run a batch file (simply containing the command used above), and it's re-stocked in about 1 minute. With Odin, you have to manually select the files, and then flashing itself takes 2-3 minutes.
Click to expand...
Click to collapse
I flashed GT p1000 GSM through this method. CM10.1 4.2.2 worked really well. No bugs yet. Will feedback further.soon.
Mensreaorder out!
Great
Sent from my GT-I9300 using xda premium
please post a link to the required files
Hi...i downloaded heimdall, but was unable to find all the required files like dbdata.rfs, param etc... Please post a link containing the full package.
But you need to say which tab model/variant is yours,
Sent from my GT-P1000 using xda app-developers app
Details on the problem
priyana said:
But you need to say which tab model/variant is yours,
Sent from my GT-P1000 using xda app-developers app[/QUOTE
Hi Priyana. I'm using the Galaxy tab p1000 asian version. I was running cm 9.1 on it for the last 6 months without any problems, but recently tried out the bluetooth tethering and the software went into an infinite bootloop. I tried recovery by trying a full wipe, but when i tried to restore one of the old backups it all crashed again. My device is now able to go into download mode with power+vol down button combo. Also when the power button is long pressed, i get the Samsung galaxy tab frozen splash screen and on connecting the charger there is a battery icon but no charging progress.
Odin did not recognize the device despite waiting and watching as recommended, hence i tried flashing with heimdall 1.4 version and the GB stock safe rom by following the instructions. Device drivers get installed and heimdall detects my device.Was able to figure out the files and run Heimdall (my previous question is hence irrelevant), but to no avail. Am attaching the log after the Heimdall run. Please help.
Click to expand...
Click to collapse
I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me
Hi!
is everything works fine after you did this?
I have live demo unit, I'm afraid bricking it.
there is the possibility of making a video demo?
there is the possibility of making a video demo?
QUOTE=Sirus2012;43240081]I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me [/QUOTE]
Pics pleas??
Verstuurd van mijn GT-I9505
Every thing is working fine for me only one prob.
when i reboot it . it stuck into the first logo. i have waited for more than 10 min.
than if i got recvoery and format the data. it boot than normally once.
Again if i had to reboot it. i have to goto recovery and format the data to boot the phone.
how to get rid of this?
br
s4 demo unit
Deduxma said:
there is the possibility of making a video demo?
QUOTE=Sirus2012;43240081]I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me
Click to expand...
Click to collapse
[/QUOTE]
please dose it mean my live s4 live demo unit will now behave like a normal phone and make or receive calls? after intalling this rom?
Help!
Just picked up a i9505x live demo unit.....does this process still work??
Demos don't have imeis do they I know our 3 s4s don't so calls can't be made
Sent from my GT-I9505 using xda app-developers app
s4sajii said:
Every thing is working fine for me only one prob.
when i reboot it . it stuck into the first logo. i have waited for more than 10 min.
than if i got recvoery and format the data. it boot than normally once.
Again if i had to reboot it. i have to goto recovery and format the data to boot the phone.
how to get rid of this?
br
Click to expand...
Click to collapse
Flash edited stock rom
Yes
Already did that. As described in the first post.
Br
Works but...
Everything works as it should but no WiFi.When flash Adam Kernel just get a black screen and that's it
I follow all the steps from the first post but at the end of odin flash i get FAIL . Any ideas?
Sirus2012 said:
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
Click to expand...
Click to collapse
i did it but i got this
Dj [email protected]ib ~
$ tar --delete --file=samrom.tar NON-HLOS.bin
tar: NON-HLOS.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
$ tar --delete --file=samrom.tar modem.bin
tar: modem.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
so sir what to do ???
mastro:° said:
i did it but i got this
Dj [email protected] ~
$ tar --delete --file=samrom.tar NON-HLOS.bin
tar: NON-HLOS.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
$ tar --delete --file=samrom.tar modem.bin
tar: modem.bin: Not found in archive
tar: Exiting with failure status due to previous errors
Dj [email protected] ~
so sir what to do ???
Click to expand...
Click to collapse
same problem here.....seems like the command is not written in the right way
EDIT: I noticedd that when you start the program, it creates a folder inside 'cygwin-home' which is your user name and you have to place the samrom.tar in there in order to delete the two files!
btw the command lines are correct! cheers!!
stergios89 said:
same problem here.....seems like the command is not written in the right way
EDIT: I noticedd that when you start the program, it creates a folder inside 'cygwin-home' which is your user name and you have to place the samrom.tar in there in order to delete the two files!
btw the command lines are correct! cheers!!
Click to expand...
Click to collapse
So what`s the status of your phone, I was given an S4 LDU and I`d love to get rid of the demo all together, I`m not to bothered that I won`t be able to use it as a phone.
mloc33 said:
So what`s the status of your phone, I was given an S4 LDU and I`d love to get rid of the demo all together, I`m not to bothered that I won`t be able to use it as a phone.
Click to expand...
Click to collapse
Well, based on the stock ROM I downloaded it (I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5),I deleted the the files sirus2012 was referring to and I am stuck at a point were the Odin says fail while flashing the ROM....
Trying to figure out if I need to delete another more file from the .TAR
After the FAIL status in Odin, I disconnected the phone, removed battery and placed it again and I had an error saying 'Firmware needs to be recovered via Kies'
I, once then, flashed again the stock ROM(without the deleted files) and noticed there was no WiFi....
So I either have a phone with no WIFI, or an error and phone can't boot
Hope I can find a way out of this!
stergios89 said:
Well, based on the stock ROM I downloaded it (I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5),I deleted the the files sirus2012 was referring to and I am stuck at a point were the Odin says fail while flashing the ROM....
Trying to figure out if I need to delete another more file from the .TAR
After the FAIL status in Odin, I disconnected the phone, removed battery and placed it again and I had an error saying 'Firmware needs to be recovered via Kies'
I, once then, flashed again the stock ROM(without the deleted files) and noticed there was no WiFi....
So I either have a phone with no WIFI, or an error and phone can't boot
Hope I can find a way out of this!
Click to expand...
Click to collapse
Seems that there`s no real method or solution, pity, it`s a waste of a phone the way it is..
mloc33 said:
Seems that there`s no real method or solution, pity, it`s a waste of a phone the way it is..
Click to expand...
Click to collapse
Don't give up on that.....I think there will be a solution sooner or later....(I'll try to find it asap) because this 'phone' is really good
Or it could be something really small that we can't see and do it wrong.
stergios89 said:
Don't give up on that.....I think there will be a solution sooner or later....(I'll try to find it asap) because this 'phone' is really good
Or it could be something really small that we can't see and do it wrong.
Click to expand...
Click to collapse
True man, fingers crossed I suppose
mloc33 said:
Seems that there`s no real method or solution, pity, it`s a waste of a phone the way it is..
Click to expand...
Click to collapse
Sirus2012 said:
I decided to make this post to help people bring life back to the I9505X live demo unit. I know how conflicting some some sites are so I just wanted to write something all can follow step for step. Hope it helps like it helped me
1 Download rom from www.sammobile.com
2 Once file is downloaded you will have something looking like this I9505XXUAMDM_I9505OXXAMDB_BTU.zip (this is one i used) http://www.sammobile.com/firmwares/?page=1&model=GT-I9505&pcode=0#firmware
3 Extract the zip file
4 You will now have somthing like this I9505XXUAMDM_I9505OXXAMDB_I9505XXUAMDM_HOME.tar.md5
5 Rename file to samrom.tar
6 Place this file on your desktop (this will be the tar file we want to edit)
7 Download cygwin from here http://cygwin.com/setup.exe and install
8 Move the tar file to C:\cygwin\home
10 Open cygwin
11 We need to delete some files from the tar file. to do so i will list the commands below and files that need deleting. after typing each line command please wait while the action completes as it will look like its doing nothing. commands as follows
$ tar --delete --file=samrom.tar NON-HLOS.bin
$ tar --delete --file=samrom.tar modem.bin
12 Once the last command is done just close cygwin (depending on the rom you download there maybe other files that need deleting)
the files remaining should be
boot.img
cache.img.ext4
hidden.img.ext4
recovery.img
system.img.ext4
(you can check this by opening the samrom.tar file with winrar)
13 Download odin and install from http://www.android.gs/download-odin-3-07/
14 Make sure samsung drivers are installed if they are not download em from http://www.mediafire.com/download/d2h54mx7kt4uupt/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
15 Open odin and connect your S4
16 Click on PDA and place the samrom.tar file in there and click start (it will flash)
17 after it has flashed install TWRP and install adams kernel explained here http://forum.xda-developers.com/showthread.php?t=2256252&page=14
i hope this helps people who are having trouble installing roms on there S4 live demo unit. if you would like to know anything or having trouble message me im happy to try help.
Thanks to marian_86 for helping me sort out this problem for me
If this helped you please hit thank me
Click to expand...
Click to collapse
Well I think I figured it out with my S4 demo unit to make WiFi work.
All the steps were followed BUT...
I DIDN'T delete the two files(modem and NON-hlos) and continued with the procedure
The most important step was .17 which redirects you to another thread about TWRP and Adams Kernel...
Following the steps there where enough to solve my issue.
And now my WiFi works pretty good(so far so good at least for the last 2-3 hours )
Let me know if it worked for you too!
Cheers!
Heimdall for Linux and mac - this is a program that is used on Linux that's similar to Odin for windows. It is capable of flashing extracted tar firmware AP,CP,CSC,and BL using download mode for Samsung devices.
This is not my program.
Also I am limited to Linux for heimdall so testing Mac I can not do but Instructions to install will also be posted using a link
I am testing how to flash the s7 for others limited to Linux or mac.
Linux install of Heimdall on Linux:
Go to the official website here: http://goo.gl/PQC1RN
Scroll down and click on Download(for Linux)
Click to download the Heimdall version for your Linux version (EX. ubuntu13.04-heimdall_1.4.0-0_amd64.deb will work with 14.04 & 13.04 64bit)
Click and download the frontend if you don't like to work inside the terminal
Open your Downloads folder and click to install the files you downloaded
Remember to open Heimdall as Admin(sudo) so it works correctly
Mac install:
http://rootmygalaxy.net/install-odin-jdoin3-for-mac-osx/
Steps to flashing frimware on linux:
1. open terminal and type sudo heimdall-frontend
2. look for flash tab
3. extract firmware zip to a folder then create 4 more folders named AP,BL,CP,and CSC
4. Rename AP,BL,CP,CSC by removing the .md5 part of the file name leaving only the .tar at the end
5. Extract each tar to its specific folder
6. Under the flash tab look for pit file and click browse, goto CSC folder and click the pit file
7. Now look for add and from the list under partition details choose which file to add then click browse under it should have the file name you are looking for under partition details if unsure what to put, go through each folder you made and keep adding each file
8. then click start
This is capable of flashing the firmware , as in the pictures it shows it works and fails, i am thinking because i am flashing all at once instead of each folder separate, or in the wrong order
there are forums on xda on how to use heimdall more extensivly but im just doing this for the s7 so productive comments are welcomed
Also this is being tested on a sprint version of the s7 g930p that has been flashed to g930u firmware, in the pictures im flashing a firmware i already have installed just incase i mess up
Capable of flashing everything but system.img
miko12312 said:
Capable of flashing everything but system.img
Click to expand...
Click to collapse
Should I give up on using Heimdall to flash my S7 active?
rabbiporkchop said:
Should I give up on using Heimdall to flash my S7 active?
Click to expand...
Click to collapse
Depends if you know how to use , I still haven't but also haven't used it,to flash ,there has been successful attempts at flashing samsung devices , you just need to put it in the correct order I believe but it does work there is a full forum on the program in xda
Hi,
I would like install at the Samsung SM-A515F the Lineage OS and the TWRP. I found only TWRP for the SM-A50. And the flashing dose not work for this phone.
I has try it with Heimdall and Odin.
The recovery I had downloaed from this Page:
https://www.droidthunder.com/install-twrp-recovery-on-galaxy-a51/
Need help or better information, if there exist an TWRP and lineage for this device.
Regards tiptel170
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
s 10 page? which one is that? can u please provide the link?
Go here for odin flash method without twrp
sankhauaa said:
No need to flash twrp,u can flash aosp rom or even gsi with the help of odin only.Go to s10 page
Click to expand...
Click to collapse
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
so does this method work for lineage os on A515F too?
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
Don't pay.Its fake
tiptel170 said:
After the long searching in the web, I found this:
A515F-TWRP
Link: https://firmware.gem-flash.com
After paying, you can download this TRWP. No idea, if this works. Maybe some one, will be use it.
Click to expand...
Click to collapse
of course it would be fake
How can I open the img-files in the Linux desktop?
Found here this link, for the Magisk in the A515F:
https://forum.xda-developers.com/ga...w-to-root-samsung-a51-sm-a515f-t4032389/page2
I'll found this:
1. https://www.androlite.com/2020/01/twrp-root-samsung-galaxy-a51.html
2. https://appslova.com/install-twrp-on-samsung-galaxy-a51/
This links look likes good, because, my phone will not start or the heimdall goes into the error (likes in de page one, the screenshots ).
I found this, and I used basic from this page: https://forum.xda-developers.com/showpost.php?p=82241115&postcount=70
My first steps to install the lineage os 17 on the SM-A515F
Lineage: https://sourceforge.net/projects/andyyan-gsi/
All commands in the linux terminal, the path please use your own paths you like it!
Unpack lineage****.xz:
unxz lineage*.xz
1) Extract the AP_file.tar.md5 from your firmware.zip file using 7zip
2) Extract the super.img.lz4 file from the AP_file.tar.md5 file using 7zip
3) Put super.img.lz4 file in LZ4 folder and run in CMD the command
lz4 -d super.img.lz4 superLZ4.img
4) Put superLZ4.img file in Simg2img folder and run in CMD the command
chmod 777 ~/bin/otatools/bin/simg2img
~/bin/otatools/bin/simg2img superLZ4.img superSIMG.img
In Linux OR Bash shell:
1) Put superSIMG.img in otatools/bin folder and extract it in Linux terminal using the command
chomd 777 ~/bin/otatools/bin/lpunpack
~/bin/otatools/bin/lpunpack --slot=0 superSIMG.img ~/1
2) Put, in the folder where you extracted superSIMG.img, the GSI file you downloaded and rename it to system.img. Now you should have odm.img, system.img, vendor.img and product.img files in the same folder.
You may also need to delete/remane the original system.img file before renaming the GSI file.
3) Now you’re going to make a brand new super.img file containing all 4 files of the previous step. This is a critical and tricky step. Run Linux terminal and type:
chomd 777 ~/bin/otatools/bin/lpmake
~/bin/otatools/bin/lpmake ~/bin/otatools/bin/lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:4294967296 --group main:4293513600 --partition system:readonly:1959841792:main --image system=./system.img --partition vendor:readonly:680239104:main --image vendor=./vendor.img --partition odm:readonly:4349952:main --image odm=./odm.img --sparse --output ./super.img
4) Make an tar file:
tar -H ustar -c super.img > lineageos17.1_SMA515F.tar
5) Goto Windows -> Odin -> AP, put the file lineageos17.1_SMA515F.tar in to the AP-slot -> Start
This is what I has done:
But, by the compiling, I got this error:
Code:
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition system will resize from 0 bytes to 1959841792 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition vendor will resize from 0 bytes to 680239104 bytes
lpmake I 07-15 20:18:20 92568 92568 builder.cpp:1012] [liblp]Partition odm will resize from 0 bytes to 4349952 bytes
Invalid sparse file format at header magic
Invalid sparse file format at header magic
And the phone is into the boot-loop, it will not starting the system.
Any help please...
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
tiptel170 said:
Update:
System requirements:
- Fedora 32 with current kernel
- VirtualBox 6.1 with USB support
- Windows 7
- ODIN 3.14
Enable Root:
I) On mobile phone
1. carry out firmware update
1.1 Set up device, WITHOUT Google Accounts, WITHOUT security settings, set up WLAN only
1.2 Settings -> Phone info -> Software information -> Build number (press 7x )
1.3 Settings -> developer option -> enable OEM unlocking and USB debugging
2. copy the files from the root directory to the external SD card
2.1 Install MagiskManager
2.2 Starting MagiskManager
2.3 Installing Magisk Select
II) In the Fedora area
3. unpack the boot.img from the AP***.tar, on the PC
3.1 lz4 -d boot.img.lz4 boot.img
3.2 Copy the boot.img to the SD card from the phone
4. patching the boot.img in MagikMager
4.1 Select the boot.img, wait until "Done" appears.
4.2 Then copy the magisk_patch.img to the workstation (Fedora)
5.1 Rename the original boot.img to boot_original.img
5.2 renaming magisk_patch.img to boot.img
5.3 Transfer the new boot.img to the PC for the ODIN or HEIMDALL
5.4 Convert the boot.img to boot.tar: tar -H ustar -c boot.img > boot.tar (here for ODIN)
III) Virtual environment Win7
6.1 Copy the boot.tar from the Fedora workstation to the Odin directory of Win7
6.2 Open the boot.tar in the AP slot, Auto Reboot must be off
6.3 Press Vol + & Vol - simultaneously and plug in the USB cable (On SM-A515F), then click on "Start" in the ODIN.
IV) On the Mobile Phone
7.1 If ready, restart with Vol - & Hold PWR for more than 7 sec
7.2 Putting the device into recovery mode (switch off, press vol up and pwr simultaneously, Samsunglog appears, release pwr again)
7.3 Wipe your data: Wiped data/factury reset
Note: Device makes a boot loop for the first time - is normal. The first start takes quite long, be patient!
7.4 Settings -> Phone info -> Software information -> Build number (press 7x )
7.5 Settings -> Developer option -> Enable OEM unlock, USB debugging and system auto update to OFF
7.6 Installing and starting MagiskManger
The device will restart once!
Check it: Whether root is present
Fedora workstation:
Call Terminal, enter adb shell followed by su
If everything went well, the MagiskManager should answer the phone and ask for authorization.
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
Click to expand...
Click to collapse
It is work ???
GreggBorowski said:
It is work ???
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------
These steps works well with the firmware: SM-A515F R58N60BLPAZ
Where are the exactly steps for installing the TWRP?
I has installed the TWRP-10.0(A51).zip with the heimdall and the phone will not booting. And I'm not entering the TWRP. And finally I has reinstalled the revcovery.img (heimdall) from the APxxxx.zip file, and the phone starting normally.
All things with the AOSP10 etc, I has tried and the other steps for an alternative system will not work on this phone.
Thanks God, the root is now working. And I have to work with the ugly Samsung system.
sankhauaa said:
I m not tried. But someone in this a51 group tried.Its working. But not so easy .
---------- Post added at 09:11 AM ---------- Previous post was at 09:09 AM ----------
Don't pay.Its fake
Click to expand...
Click to collapse
sar please send me a51 group
Mehran` said:
sar please send me a51 group
Click to expand...
Click to collapse
Go to s10 page
sankhauaa said:
Go here for odin flash method without twrp
Click to expand...
Click to collapse
Not working. I has done step by step in this guide.
ibtsam3301 said:
so does this method work for lineage os on A515F too?
Click to expand...
Click to collapse
No. Withe manipulation from the vbmeta.img, the system is unwilling to start. It gos in to the bootloader, with error-codes. Like in first thread I describe. Olny the SAMSUNG original system works with the kernel modification for the MagiskManager.
I saw black for the future, there will be exist an custom rom for this device.
I have no idea, what can I do for this device. But I use and spend a lot of time for modification, without an good result. Has anyone an idea what can I do? But it look likes, it has an great secure system intern for not using an customer rom. This is my intention.