Hello, in desperate need of help, I will sum up my problem, and after I'll give a detailed outline of everything I've done.
The main issue is: Custom binary blocked by FRP lock
I'm flashing stock firmware that I downloaded from sammobile with heimdall, using this command:
Code:
~/Heimdall/build/bin/heimdall flash --BOOTLOADER sboot.bin --CM cm.bin --RECOVERY recovery.img --RADIO modem.bin --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img
After this finishes, the phone reboots, Android logo appears and it says "Installing system updates", bar fills up very quickly, and then it says "erasing".
After that, it reboots again and The FRP message appears again.
----
That is the current problem, how I got here is the following:
1. In order to install LineageOS I disabled FRP lock by removing the device from "manage devices", and removing the google account from the phone itself.
2. Installed LineageOS SUCCESSFULLY, I was very happy. I turned off my phone at some point.
3. When I turned it back on, the boot screen displayed the dreaded FRP message. I concluded I had to install stock firmware in order to disable FRP again, which apparently enabled itself again.
4. Since I'm on linux, I'm using heimdall, and initially I could not flash the firmware, so I have to use a patch (can't paste the URL because I'm new, but it shows up in gitlab if you search for "ERROR: Failed to receive file part response!")
5. I downloaded this firmware: "This firmware has version number PDA A510MUBS7CSD9 and CSC A510MPSN7CSD4." and extracted it.
6. Used the command explained above:
Code:
~/Heimdall/build/bin/heimdall flash --BOOTLOADER sboot.bin --CM cm.bin --RECOVERY recovery.img --RADIO modem.bin --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img
7. The output is littered by "ERROR: Failed to receive file part response!" but it keeps going, session ends, and phone reboots.
I've been googling for hours now. The last thing I tried was the steps from another post here, saying to first flash all the files except hidden.img, and then flash that separately. That did not work either.
Have I bricked it? What can I do?
I just made a windows VM to use Odin3, followed the steps and I got a FAIL!
Coming from linux, I'm used to error messages and logs but this doesn't seem to have anything of the sort.
Help please!
Not that anyone's reading, but I managed to flash stock firmware with odin3 by flashing hidden.img separately, but now it is stuck on the samsung logo forever.
Related
My nexus S does'nt boot up, it doesn't pass the google logo screen, so i tried to unlock the bootloader, and when i choose yes it stucks there, so I searched here on the forum and tried everything
i tried to flash recovery
to flash another stock rom
to flash kernels
to wipe cache and factory reset
to boot it up with hairdrayer
i manged to boot it into CWM recovery via fastboot, i tried to mound usb but nothing happen, i tried to flash rom and i get an eror E:Can't mount /sdcard/
it probably was on 4.0.3 before he died..
anyone? i need my phone :crying:
Is your bootloader up to date? I had issues with CWM and all I did to resolve the issue was updating the bootloader.
To do this, grab the firmware image from google: https://developers.google.com/android/nexus/images
Download that to your pc, extract the boot image from the file.
Now put your nexus s into fastboot mode, and connect it to your pc.
Using adb flash the boot image to your phone.
Hope that helps.
SkyandDirt said:
Is your bootloader up to date? I had issues with CWM and all I did to resolve the issue was updating the bootloader.
To do this, grab the firmware image from google: https://developers.google.com/android/nexus/images
Download that to your pc, extract the boot image from the file.
Now put your nexus s into fastboot mode, and connect it to your pc.
Using adb flash the boot image to your phone.
Hope that helps.
Click to expand...
Click to collapse
how do i flash it? (sorry about the nooby question)
xplosi said:
how do i flash it? (sorry about the nooby question)
Click to expand...
Click to collapse
Once you extracted the boot image to your pc and connected your phone in fastboot mode, use the following command to flash the boot image:
Code:
fastboot flash bootloader C:\location\of\file\bootloader.img
You will need to point it to the location of where you extracted your boot image file.
SkyandDirt said:
Once you extracted the boot image to your pc and connected your phone in fastboot mode, use the following command to flash the boot image:
Code:
fastboot flash bootloader C:\location\of\file\bootloader.img
You will need to point it to the location of where you extracted your boot image file.
Click to expand...
Click to collapse
wich one is it?
What version of CWM are you using?
Versions after 6.0.1.0 have issues mounting SD.
polobunny said:
What version of CWM are you using?
Versions after 6.0.1.0 have issues mounting SD.
Click to expand...
Click to collapse
even im 6.0.1.0 it doesn't mount
anyone? what sould i do?
can someone help me?
xplosi said:
can someone help me?
Click to expand...
Click to collapse
try to flash stock GB with odin and download mod
Scorpoid said:
try to flash stock GB with odin and download mod
Click to expand...
Click to collapse
Download mod doesn't work either it shows half the unlock bootloader screen and half blank screen
xplosi said:
wich one is it?
Click to expand...
Click to collapse
The way to install fastboot:
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
The way to use fastboot:
http://forum.xda-developers.com/showthread.php?t=1752270
Seems like flashing stock in odin would be the only sure fire way. That didn't work?
it stucked on this :
<ID:0/013> Added!!
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> bootloader.img
Click to expand...
Click to collapse
and on phone screen
"Verify Image (IPBL) ... Success"
http://oi49.tinypic.com/16jfrcy.jpg
how to boot in cmw...nexus s hangs on google logo..i think i flashed wrong stock rom...bootloader was in locked state..when i try to unlock it through fastboot with the command "fastboot oem unlock" the result is "FAIL <REMOTE: ERASE FAIL>"...im totally disappoinnted with all sulation i tried from forum...plzzz someone help me...
Flash Stock Rom using ADB
xplosi said:
My nexus S does'nt boot up, it doesn't pass the google logo screen, so i tried to unlock the bootloader, and when i choose yes it stucks there, so I searched here on the forum and tried everything
i tried to flash recovery
to flash another stock rom
to flash kernels
to wipe cache and factory reset
to boot it up with hairdrayer
i manged to boot it into CWM recovery via fastboot, i tried to mound usb but nothing happen, i tried to flash rom and i get an eror E:Can't mount /sdcard/
it probably was on 4.0.3 before he died..
anyone? i need my phone :crying:
Click to expand...
Click to collapse
try to flash stock rom using adb in fastboot mode
SkyandDirt said:
Once you extracted the boot image to your pc and connected your phone in fastboot mode, use the following command to flash the boot image:
Code:
fastboot flash bootloader C:\location\of\file\bootloader.img
You will need to point it to the location of where you extracted your boot image file.
Click to expand...
Click to collapse
This doesn't work if the bootloader is locked. Mine is locked and cannot be unlocked like OP describes.
I m Here to Help U
Bro i too had met the same problem but i managed to solve it.
If u try to mount your sd card in CWM it wont work.
All you need to do is to Flash twrp v2.7 on your nexus using fastboot , after doing that connect a usb cable to your device inorder to connect it with your pc,after that go to recovery and try to mount USB DISK DRIVE over there , i have personally tried it ,, after it MOunts your device will connent to Your PC and then just copy over the New Rom Custom Or Stock whatever you like and flash It...it will fix the problem
Why not just fastboot the rom?
Sent from my One A0001 using XDA Premium 4 mobile app
If you loaded the MJ6 leak, the OTA MJ9 update isn't going to work. Here's how to get it to work.
THIS WILL PROBABLY WIPE YOUR DEVICE!!
IF YOU HAD ROOT ON MJ6 YOU"LL ALMOST CERTAINLY LOSE IT!!
Read the entire instructions before you start. If you don't feel comfortable following them, don't try!
Download the OTA update file from here http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
Thank the user who posted the file.
Rename the downloaded file (2400258..cfg) to update-mf3-mj9.zip for convenience.
You can also download the update file from here... https://drive.google.com/folderview?id=0B1DGsUzId7AHTjlIbklXeTYyS2c&usp=sharing
Thanks to user bigfdaddy2.
Now the fun part...
If you're flashing with Odin, skip down to the "Flashing with Odin" section.
Flashing with heimdall...
Download the MF3 tar files from here http://forum.xda-developers.com/showthread.php?t=2502003
Thank the user who posted the file.
Do NOT flash this file directly. It won't work because the MJ6 bootloader won't let you go back.
Extract all the files...
Code:
unrar x MF3\ TARs.rar
cd JellyBean
ls *.md5 | xargs -n1 tar -xf
You should now have all the flash files for MF3. Don't flash any files other than the ones in the command below.
Put your phone in Download mode.
Now flash...
Code:
heimdall flash \
--SYSTEM system.img.ext4 \
--MDM modem.bin \
--APNHLOS NON-HLOS.bin \
--CACHE cache.img.ext4
If the flash fails STOP and post in this thread. What to do next depends on exactly what failed, what you've retried and where you wound up.
If the flash was successful, the phone will reboot into recovery and apply a small update from cache. That update MUST succeed or the MJ9 update will fail. If the update applied successfully, the phone will reboot and stick on a black screen. The notification LED will pulse blue for a few minutes then stop. That's normal! Proceed with the Sideload instructions below.
Flashing with Odin.
Thanks again to bigfdaddy2, you can download an Odin file here...
https://drive.google.com/folderview?id=0B1DGsUzId7AHTjlIbklXeTYyS2c&usp=sharing
Put your phone in Download mode and flash the file in the PDA section of Odin.
If the flash fails STOP and post in this thread. What to do next depends on exactly what failed, what you've retried and where you wound up.
If the flash was successful, the phone will reboot into recovery and apply a small update from cache. That update MUST succeed or the MJ9 update will fail. If the update applied successfully, the phone will reboot and stick on a black screen. The notification LED will pulse blue for a few minutes then stop. That's normal! Proceed with the Sideload instructions below.
Sideloading update.
Boot to recovery mode now and select Apply update from ADB.
Back on your workstation...
Code:
adb sideload update-mf3-mj9.zip
You CAN apply the update from an external SD Card but the phone will reboot on its own even if the update fails and you'll miss the error messages. Applying from SD Card will also CERTAINLY do a factory reset. You have a chance of saving your data if you do the sideload.
If the update was successful, reboot the phone and you'll be at stock MJ9.
If the update fails STOP and post in this thread.
Background.
Like most OTA updates, the update.zip file contains mostly patch files which are the differences between the old version of a file and the new version. Because of this, the old version has to be exactly what is expected. This OTA update expects the existing files to be the MF3 versions. Anything else will cause the verification process to fail.
Everything that the update checks is in the system filesystem (system.img.ext4), and the modem (modem.bin and NON-HLOS.bin) so to fake the updater out, we flash those partitions at a minimum. The cache filesystem (cache.img.ext4) contains a small update to system which is also required and so we flash that as well. That's the intermediate recovery step that happens automatically after the flash completes. Once that happens, the phone isn't usable but it has enough of the MF3 files to allow the update script to complete successfully. The script patches all the system and modem files to MJ9 and writes it's own new bootloader (aboot.mbn) and kernel (boot.img).
Don't panic if something goes wrong. Just post in the thread. I've recovered mine from certain death about a dozen times since I first posted this guide yesterday morning.
ty i am know gonna do this and report back.. do ned to heimdall and odin or either one fine ?
bigfdaddy2 said:
ty i am know gonna do this and report back.. for heimdall is that a program i need or just adb it command?
Click to expand...
Click to collapse
You either need heimdall OR odin. Not both.
gtj0 said:
You either need heimdall OR odin. Not both.
Click to expand...
Click to collapse
ok ty well i answered my own question aout heimdall ... so i can just odin then i thought i needed to do both since it doesnt really say or i just didnt open my eyes enough lol either way ty again for this ...
bigfdaddy2 said:
ok ty well i answered my own question aout heimdall ... so i can just odin then i thought i needed to do both since it doesnt really say or i just didnt open my eyes enough lol either way ty again for this ...
Click to expand...
Click to collapse
Sorry, I just clarified it a little.
This is all a bit past me any way someone could post a link to a recombined .md5 to flash using odin?
phone reaads this know in red at top: secure fail:kernel.......then below with yellow triangle reads : system software not authorized by samsung has been found on your phone !
this what heimdall reads out :
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading SBL1
0%
100%
SBL1 upload successful
Uploading SBL2
0%
100%
SBL2 upload successful
Uploading SBL3
0%
100%
SBL3 upload successful
Uploading RPM
0%
100%
RPM upload successful
Uploading TZ
0%
100%
TZ upload successful
Uploading BOOT
0%
12%
25%
37%
50%
63%
75%
88%
100%
BOOT upload successful
Uploading RECOVERY
0%
10%
21%
32%
43%
53%
64%
75%
86%
97%
100%
RECOVERY upload successful
Uploading PERSDATA
0%
23%
47%
71%
95%
100%
PERSDATA upload successful
Uploading SYSTEM
0%
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
Rebooting device...
Releasing device interface..
EDIT: After reflashing boot and recovery im still on mj6 system....
gtj0 said:
If you loaded the MJ6 leak, the OTA MJ9 update isn't going to work. Here's how to get it to work.
THIS WILL WIPE YOUR DEVICE!!
IF YOU HAD ROOT ON MJ6 YOU"LL PROBABLY LOSE IT!!
You need to be command-line perficient.
Download the OTA update file from here http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
Thank the user who posted the file.
Rename the downloaded file (2400258..cfg) to update-mf3-mj9.zip for convenience.
Download the MF3 tar files from here http://forum.xda-developers.com/showthread.php?t=2502003
Thank the user who posted the file.
Now the fun part...
Code:
unrar x MF3\ TARs.rar
cd JellyBean
ls *.md5 | xargs -n1 tar -xf
You should now have all the flash files for MF3. You have to flash all EXCEPT aboot boot and recovery since they're locked at MJ6.
Put your phone in Download mode.
If you're going to flash with heimdall, you can flash the files directly...
Code:
heimdall flash \
--SBL1 sbl1.mbn \
--SBL2 sbl2.mbn \
--SBL3 sbl3.mbn \
--RPM rpm.mbn \
--TZ tz.mbn \
--BOOT boot.img \
--RECOVERY recovery.img \
--PERSDATA persdata.img.ext4 \
--SYSTEM system.img.ext4 \
--MDM modem.bin \
--APNHLOS NON-HLOS.bin \
--CACHE cache.img.ext4 \
--HIDDEN hidden.img.ext4
The phone will reboot a few times and finally hang with the notification led pulsing. That's OK. Skip the next step.
If you're going to flash with Odin, you need to recombine the files into a tar.md5 file...
Code:
export files="sbl1.mbn sbl2.mbn sbl3.mbn rpm.mbn tz.mbn persdata.img.ext4 system.img.ext4 modem.bin NON-HLOS.bin cache.img.ext4 hidden.img.ext4"
export tarfile=mf3_partial.tar
tar -cf $tarfile $files
cp $tarfile $tarfile.md5
md5sum -t $tarfile >> $tarfile.md5
Now use Odin to flash the md5 file. The phone will reboot a few times and finally hang with the notification led pulsing. That's OK.
The phone's not runnable in this state so now it's time to apply the update...
Boot to recovery mode and select Apply update from ADB.
Back on your workstation...
Code:
cd ..
adb sideload update-mf3-mj9.zip
Wait for it to reboot and you'll have a completely stock MJ9.
Click to expand...
Click to collapse
WIll this method work for MF3 users? I would rather flash through odin than take the OTA.
colbur87 said:
WIll this method work for MF3 users? I would rather flash through odin than take the OTA.
Click to expand...
Click to collapse
yes, just do the adb sideload method at the very bottom
dahlem said:
This is all a bit past me any way someone could post a link to a recombined .md5 to flash using odin?
Click to expand...
Click to collapse
I second this.
Could you do a video guide for us by any chance?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
MJ9 stock?
Andrew149 said:
yes, just do the adb sideload method at the very bottom
Click to expand...
Click to collapse
So if you're on mf3 all you have to do is download the mj9 conf file, change the name, then adb sideload to get stock mj9?
I unrooted today and am back to "official". I've downloaded the ota several times, but when it reboots to install it stops at 30% and says update failed, reboots, then tells me Install Interrupted.
bigfdaddy2 said:
phone reaads this know in red at top: secure fail:kernel.......then below with yellow triangle reads : system software not authorized by samsung has been found on your phone !
this what heimdall reads out :
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading SBL1
0%
100%
SBL1 upload successful
Uploading SBL2
0%
100%
SBL2 upload successful
Uploading SBL3
0%
100%
SBL3 upload successful
Uploading RPM
0%
100%
RPM upload successful
Uploading TZ
0%
100%
TZ upload successful
Uploading BOOT
0%
12%
25%
37%
50%
63%
75%
88%
100%
BOOT upload successful
Uploading RECOVERY
0%
10%
21%
32%
43%
53%
64%
75%
86%
97%
100%
RECOVERY upload successful
Uploading PERSDATA
0%
23%
47%
71%
95%
100%
PERSDATA upload successful
Uploading SYSTEM
0%
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
Rebooting device...
Releasing device interface..
EDIT: After reflashing boot and recovery im still on mj6 system....
Click to expand...
Click to collapse
It failed because you tried to flash aboot and recovery. You cannot downgrade either of those after installing MJ6. He has us flashing everything except aboot and recovery and that does work. I just successfully used this method to upgrade from the leaked MJ6 to MJ9. I did have to use a linux machine to unpack and repack the files because I couldn't get heimdall to work on my windows 8.1 machine but it worked.
bigfdaddy2 said:
phone reaads this know in red at top: secure fail:kernel.......then below with yellow triangle reads : system software not authorized by samsung has been found on your phone !
EDIT: After reflashing boot and recovery im still on mj6 system....
Click to expand...
Click to collapse
My fault. When I pasted the heimdall command in to the post, it still had recovery and boot. Just remove those 2 files and you should be good to go.
dahlem said:
This is all a bit past me any way someone could post a link to a recombined .md5 to flash using odin?
Click to expand...
Click to collapse
some_douchebag said:
I second this.
Click to expand...
Click to collapse
Give me 30 minutes and I'll post one.
AWESOME
gtj0 said:
Give me 30 minutes and I'll post one.
Click to expand...
Click to collapse
Thanks SO much!
my windows machine is failing to upload to ststem
gtj0 said:
Give me 30 minutes and I'll post one.
Click to expand...
Click to collapse
dahlem said:
Thanks SO much!
Click to expand...
Click to collapse
I updated the first post with a link to the Odin ready file. This file doesn't (and can't) flash the update. It only preps the phone with enough of MF3 so you can sideload the update.
Andrew149 said:
my windows machine is failing to upload to ststem
Click to expand...
Click to collapse
A little more info?
Which method, what error, when?
gtj0 said:
I updated the first post with a link to the Odin ready file. This file doesn't (and can't) flash the update. It only preps the phone with enough of MF3 so you can sideload the update.
Click to expand...
Click to collapse
So we flash this: Download this intermediate file. It has enough MF3 files to allow the MJ9 update to apply.
http://www.androidfilehost.com/?fid=23212708291677430
Using Odin then if we do a Check for Software Update it will download?
I started looking at this issue in another thread HERE. I started thinking about this and knew there were others with more info that might help.
Everyone says you can't downgrade the Knox Boot Loader once it's been loaded. I want to try and understand why/how we can modify the system to overcome that.
Here's what I know and I've done:
After MF9, the Knox Bootloader was included in the update. Unknownforce has a great thread that has the modems with or without the boot loader. What I did first was unzip the tar files for MF9 (with and without the boot loader.)
Both files have:
modem.bin
NON-HLOS.bin
rpm.mbn
tz.mbn
When I compare the files in both, they seem identical. Same creation date, same size, ect. They may or may not be the same? But the boot loader version has some extra files.
Boot Loader Version has these files:
aboot.mbn
sbl2.mbn
sbl3.mbn
Process of elimination indicates that these have the Knox Boot loader encoded in some way. The sbl files are placed in the root directory /firmware-mdm/image/ . Try as I might, I can't find aboot.mbn. I did a nandroid backup of my system, then I deleted sbl2.mbn and sbl3.mbn using ES File Explorer. When I rebooted the phone, the files were back in the directory.
Another thing I did was a nand erase and re-partition of my phone using Odin. (Don't attempt this unless you have the pit file! You can easily brick your phone. On second thought, don't attempt this at all. I just got lucky I was able to bring it back up. As it was my Data partition was corrupted because of this but I was able to fix it.) I think I did everything right in re-installing. I put a knox free boot loader and recover with Odin first. Then booted into recovery and installed a Knox free rom. Knox boot loader was still there. I was hoping re-partitioning would wipe everything out but it was a no go. Anyone else have experience in this?
Here's my questions:
If we delete those three files and can keep them from reloading, will Knox Boot Loader be disabled?
What partition is aboot.mbn located in or stored in the system? Can it be assessed with adb commands and renamed or deleted?
Where are the sbl files being reloaded from?
Does anyone know if the similar files are the exact same files? If not how do we replace them with non-boot loader versions if the system regenerates them at each boot?
Is there a way to do a nand erase and re-partitioning in order to get rid of the bootloader?
Thoughts?
My hard brick says aboot is in partition 6
Aboot is in partition 6. You can find this out by using a # heimdall print-pit command and
examining the output.
If you dd a different version of aboot.mbn atop that partition it will hard-brick the device,
meaning the screen won't come on and all it wants is a primitive USB serial connect
to some software I'm sure only Samsung has.
How do I know? I have three Dev S4s (VZW) and none of them will let me flash TWRP.
In order to try getting a "less locked aboot" I dd'd an older version (VRUAMDK) onto
that partition (mmcblk0p6). The device is now good to send back to Samsung or to
keep papers from flying -- unless someone knows the secret serial port protocol.
Sigh.
Ehud
perezmarka said:
I started looking at this issue in another thread HERE. I started thinking about this and knew there were others with more info that might help.
Everyone says you can't downgrade the Knox Boot Loader once it's been loaded. I want to try and understand why/how we can modify the system to overcome that.
Here's what I know and I've done:
After MF9, the Knox Bootloader was included in the update. Unknownforce has a great thread that has the modems with or without the boot loader. What I did first was unzip the tar files for MF9 (with and without the boot loader.)
Both files have:
modem.bin
NON-HLOS.bin
rpm.mbn
tz.mbn
When I compare the files in both, they seem identical. Same creation date, same size, ect. They may or may not be the same? But the boot loader version has some extra files.
Boot Loader Version has these files:
aboot.mbn
sbl2.mbn
sbl3.mbn
Process of elimination indicates that these have the Knox Boot loader encoded in some way. The sbl files are placed in the root directory /firmware-mdm/image/ . Try as I might, I can't find aboot.mbn. I did a nandroid backup of my system, then I deleted sbl2.mbn and sbl3.mbn using ES File Explorer. When I rebooted the phone, the files were back in the directory.
Another thing I did was a nand erase and re-partition of my phone using Odin. (Don't attempt this unless you have the pit file! You can easily brick your phone. On second thought, don't attempt this at all. I just got lucky I was able to bring it back up. As it was my Data partition was corrupted because of this but I was able to fix it.) I think I did everything right in re-installing. I put a knox free boot loader and recover with Odin first. Then booted into recovery and installed a Knox free rom. Knox boot loader was still there. I was hoping re-partitioning would wipe everything out but it was a no go. Anyone else have experience in this?
Here's my questions:
If we delete those three files and can keep them from reloading, will Knox Boot Loader be disabled?
What partition is aboot.mbn located in or stored in the system? Can it be assessed with adb commands and renamed or deleted?
Where are the sbl files being reloaded from?
Does anyone know if the similar files are the exact same files? If not how do we replace them with non-boot loader versions if the system regenerates them at each boot?
Is there a way to do a nand erase and re-partitioning in order to get rid of the bootloader?
Thoughts?
Click to expand...
Click to collapse
perezmarka said:
I started looking at this issue in another thread HERE. I started thinking about this and knew there were others with more info that might help.
Everyone says you can't downgrade the Knox Boot Loader once it's been loaded. I want to try and understand why/how we can modify the system to overcome that.
Here's what I know and I've done:
After MF9, the Knox Bootloader was included in the update. Unknownforce has a great thread that has the modems with or without the boot loader. What I did first was unzip the tar files for MF9 (with and without the boot loader.)
Both files have:
modem.bin
NON-HLOS.bin
rpm.mbn
tz.mbn
When I compare the files in both, they seem identical. Same creation date, same size, ect. They may or may not be the same? But the boot loader version has some extra files.
Boot Loader Version has these files:
aboot.mbn
sbl2.mbn
sbl3.mbn
Process of elimination indicates that these have the Knox Boot loader encoded in some way. The sbl files are placed in the root directory /firmware-mdm/image/ . Try as I might, I can't find aboot.mbn. I did a nandroid backup of my system, then I deleted sbl2.mbn and sbl3.mbn using ES File Explorer. When I rebooted the phone, the files were back in the directory.
Another thing I did was a nand erase and re-partition of my phone using Odin. (Don't attempt this unless you have the pit file! You can easily brick your phone. On second thought, don't attempt this at all. I just got lucky I was able to bring it back up. As it was my Data partition was corrupted because of this but I was able to fix it.) I think I did everything right in re-installing. I put a knox free boot loader and recover with Odin first. Then booted into recovery and installed a Knox free rom. Knox boot loader was still there. I was hoping re-partitioning would wipe everything out but it was a no go. Anyone else have experience in this?
Here's my questions:
If we delete those three files and can keep them from reloading, will Knox Boot Loader be disabled?
What partition is aboot.mbn located in or stored in the system? Can it be assessed with adb commands and renamed or deleted?
Where are the sbl files being reloaded from?
Does anyone know if the similar files are the exact same files? If not how do we replace them with non-boot loader versions if the system regenerates them at each boot?
Is there a way to do a nand erase and re-partitioning in order to get rid of the bootloader?
Thoughts?
Click to expand...
Click to collapse
you can find aboot.mbn as aboot on /dev/blocks/...
gavron said:
Aboot is in partition 6. You can find this out by using a # heimdall print-pit command and
examining the output.
If you dd a different version of aboot.mbn atop that partition it will hard-brick the device,
meaning the screen won't come on and all it wants is a primitive USB serial connect
to some software I'm sure only Samsung has.
How do I know? I have three Dev S4s (VZW) and none of them will let me flash TWRP.
In order to try getting a "less locked aboot" I dd'd an older version (VRUAMDK) onto
that partition (mmcblk0p6). The device is now good to send back to Samsung or to
keep papers from flying -- unless someone knows the secret serial port protocol.
Sigh.
Ehud
Click to expand...
Click to collapse
I have also tried overwriting a pre-Knox aboot using DD and got the same result. I found a piece of software called QPST which is a Qualcomm developer tool, that can be used to reflash the bootloader and unbrick the phone. The only problem is you need a data file for your specific model, although this possibly can be extracted from a firmware (probably in boot.img). I haven't gotten to look inside those images yet, but that tool could possibly be able to flash an older bootloader...
Hello,
I have been updating my cyanogenmod 12s using the nightlies for a while now.
While I was updating with the update on the 18th, my phone got stuck at the 'upgrading apps' step and keeps repeating the upgrade for hours.
I accidentally then wiped the phone completely in TWRP while trying to restore the phone.
I lost the backups and OS. The warning saying 'No OS installed' shows up when I try rebooting.
My PC does not show the phone when I connect it via USB. I have nothing on TWRP to install either.
Can anyone please suggest how I should proceed?
Thank you,
Abhi2488
1. If you can boot into fastboot, just download stock CM11S fastboot package (you wont have trouble find it, just search forum) and simply flash it with fastboot, one by one partition.
I will just qoute some instructions from oneplus forum:
"Once you're on ColorOS and want to go to Cyanogenmod 11S, you have a few options. The easiest way if to use a toolkit from http://forum.xda-developers.com/onep...9-gui-t2807418, or you can download an image manually from: http://forum.xda-developers.com/onep...stock-t2826541 and run the following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
Make sure you have the proper image. I accidentally installed the 16GB version on my 64GB OPO first time and obviously didn't get 64GB of space.
That's about it. I think if people are still having problems then it's likely due to drivers, or Windows 7/8 issue. If you're still getting stuck, let me know, I'll see if I can help."
2. If you allready have custom recovery installed, you can try to flash any custom rom from OTG USB disc (you need OTG cable or OTG adapter and USB fat32 formatted disc where you will copy some custom firmware).
Hey there I got a Samsung Galaxy J7 Prime G610M on Android 8.1.0 Stock Rom, I recently tried to root the device and installed a custom recovery such as TWRP and then Unofficial Lineage OS with success, and some other roms like TRR treble edition and pure edition, I didn't liked because it had some deal breaker bugs that make me go back to Stock Rom.
Downloaded Odin and a firmware for my device from sammobile site, flashed just AP, BL, CP and CSC (no HOME_CSC), device booted fine and everything on device is working good, as long as I can tell. But today, I booted into recovery just to wipe cache like I always do every once in a while but I noticed something different. At the bottom of the recovery I am getting the following text:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery_Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
I don't remember the device having this error before so I think it may be something that needs attention, but I can't find a solution for this since every post I found was about users having a boot loop and my device is working fine. Does anyone know how can I fix this? Thanks in advance!
Extract the stock recovery.tar and flash it via Odin. Or flash TWRP, whatever.
Thanks for the reply, I don't want to use a custom recovery anymore so I would choose to flash the stock recovery.tar but the rom I downloaded from sammobile doesn't have a recovery.tar file, before I google and download some potential files that could damage my device, do you know any official site to download this recovery.tar file? Thanks!
Attached a screenshot of the files I downloaded from sammobile
Edit: Nevermind, I found it on the AP file, I got the recovery.img.lz4 convert it into recovery.tar using 7zip, flash it with Odin but sadly I still get the same error.
Convert to tar? Just extract the recovery.img out of the lz4 file. Compress it with tar, flash it. Or flash TWRP, then flash recovery.img from it.
Mohamedkam000 said:
Convert to tar? Just extract the recovery.img out of the lz4 file. Compress it with tar, flash it. Or flash TWRP, then flash recovery.img from it.
Click to expand...
Click to collapse
Yeah, I followed this guide https://forum.xda-developers.com/t/convert-twrp-img-to-tar-for-odin-easy.3355944/ and I flashed the recovery.tar successfully with odin but didn't worked, I will try to flash TWRP again and then flash recovery.img from TWRP directly, hope this method do something different. thanks for your time!
Tried installing TWRP flashed recovery.img with success but still the same error, I will continue to look into this, hopefully someone else got a new solution. Thanks anyways for your time!