Database Info

[Q] Nexus S stuck on Google logo and Unlock bootloader

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

[Q] Knox Boot Loader Exploration On Samsung Galaxy S4 SPH-L720

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...

Issue rooting after update

I just updated to the latest Pixel 3 image (blueline-qq2a.200405.005). Removed the -w from the .bat file and had no issue with the update. Now trying to root and I can't boot TWRP from the bootloader. See below output.
C:\adb>adb reboot bootloader
C:\adb>fastboot boot twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 1.551s]
Booting FAILED (Status read failed (Too many open files in system))
fastboot: error: Command failed
I have updated google drivers, downloaded latest fastboot and adb files. Any idea's what I am doing wrong?

I don't think TWRP is working for our phone right now. You have to extract the boot.img from the factory image you downloaded and patch it with Magisk. Then flash the patched boot.img using fastboot.

robocuff said:
I don't think TWRP is working for our phone right now. You have to extract the boot.img from the factory image you downloaded and patch it with Magisk. Then flash the patched boot.img using fastboot.
Click to expand...
Click to collapse
Thank you for that, so I opened Magisk app and downloaded the latest. I copied boot.img from inside image-blueline-qq2a.200405.005.zip and copied it to the phones storage. I used the app to patch the boot.img then copied that to the phones storage. adb reboot bootloader then ran the command fastboot flash boot boot.img. My phone then wouldn't boot . I reran the flash-all.bat to get back in. What did I do wrong?

Nevermind, I got it. It's always an adventure when I update my phone for some reason . Thank you so much for your input!

Shawn haz root said:
Nevermind, I got it. It's always an adventure when I update my phone for some reason . Thank you so much for your input!
Click to expand...
Click to collapse
Not sure what you did wrong but the next time you flash a patched boot image and it won't boot, there's no need to flash the whole system image again. All you need to do is flash the boot.img that comes with the system image using fastboot. I've run into the same problem a couple times in the past and flashing the factory boot.img always got me going again.

Samsung A510M - Stuck on FRP loop

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.

Galaxy J7 Prime G610M fail to open recovery_cause

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!