samsung b7510 flashing problem - Android Q&A, Help & Troubleshooting

hello i am trying to flash b 7510 but its stuck here and not turning on only what its doing going into download mode here are logsDownload Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..
<1> 1/11 Finished.
<1> qcsbl download..
<1> 2/11 Finished.
<1> oemsbl download..
<1> 3/11 Finished.
<1> amss download..
<1> 4/11 Finished.
<1> arm11boot download..
<1> 5/11 Finished.
<1> boot.img download..
<1> 6/11 Finished.
<1> recovery.img download..
<1> 7/11 Finished.
<1> system.rfs download..
<1> 8/11 Finished.
<1> data.rfs download..
<1> 9/11 Finished.
<1> csc.rfs download..
<1> 10/11 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
showing pass but not working

Related

my ace is break cant flash any rom (big partition size!!)

when i flash any rom using odin
it told me
PHP:
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..
then nothing happen !!
it stuck in mibib download
so,,, any help

[imp]odin stuck on mibib

hiii guys
i was flashing ddkq7 from sammobile but it is stuck on mibib download
Code:
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..

[Q] heimdall & SHW-M440S ?

I'm trying to flash an SHW-M440S with the KIES_HOME_M440SKSALG2_M440SSKTALEE ROM using heimdall. heimdall seems to detect the phone OK, but when trying to flash, I get the following:
Code:
$ sudo heimdall flash --normal-boot boot.img --cache cache.img --hidden hidden.img --modem modem.bin --recovery recovery.img --system system.img --verbose --stdout-errors
[sudo] password for akos:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
ERROR: Partition corresponding to -modem argument could not be located
when printing the partitioning, the modem part is stored in a partition named radio:
Code:
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 114688
Partition Block Count: 65536
Unknown 2: 0
Unknown 3: 0
Partition Name: RADIO
Filename: modem.bin
I wonder what the solution is - is there a way to tell heimdall to use the above partition instead?
Akos
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

Can' flash ClockworkMod recovery on galaxy I5500

I tryed flashing clockworkmod on my galaxy 5 with odin. I do all the steps in one of the turorials and get stuck at
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
It stays here for 10+ minutes. Please help!!
Sorry for my english
Download MADManager (from Google Play) and flash the latest CWM recovery [ALL VERSIONS STABLE] (special build for the GT-I5500)
Sent from my GT-I5500 [CM7.2]

Moto x4 XT1900-1 not entering fastboot

I recently purchased a refurbished Moto X4, which shipped to me as a hard brick a month ago.
The device would not vibrate, or enter fastboot mode for a recovery option when holding down power + volume down.
After downloading the Motorolla USB drivers, I was finally getting windows to chime when the device was being plugged in. Windows did *not* recognize the device as a Qualcomm USB device. It would just chime, and nothing would show up in device manager showing a USB device. Just a chime.
Through some miracle, running a blankflash.bat file while holding down the fastboot buttons, after installing ADB eventually got me to a fastboot menu, from which I could restore the phone to factory settings and use it.
That worked for about a month.
Now the phone is hard bricked again, with the same symptoms as before (No fastboot; no recognized Qualcomm USB device), and now blankflash gives me the following errors when I try to use it to get me to fastboot:
**** Log buffer [000001] 2019-05-22_19:31:05 ****
[ 0.000] Opening device: \\.\COM5
[ 0.003] Detecting device
[ 0.006] ...cpu.id = 172 (0xac)
[ 0.006] ...cpu.sn = 518110791 (0x1ee1be47)
[ 0.006] Opening singleimage
[ 0.007] Loading package
[ 0.009] ...filename = pkg.xml
[ 0.011] Loading programmer
[ 0.011] ...filename = programmer.elf
[ 0.011] Sending programmer
[ 0.215] Handling things over to programmer
[ 0.216] Identifying CPU version
[ 0.216] Waiting for firehose to get ready
[ 3.235] ...SDM630 1.0
[ 3.235] Determining target secure state
[ 3.237] ...secure = yes
[ 3.272] Configuring device...
[ 3.279] Flashing GPT...
[ 3.279] Flashing partition with gpt.bin
[ 3.284] Initializing storage
[ 4.463] Target NAK!
[ 4.463] ...ERROR: Failed to open the SDCC Device slot 0 partition 0
[ 4.463] ...ERROR: Failed to open the device 1 slot 0 partition 0
[ 4.463] ...INFO: Device type 1, slot 0, partition 0, error 0
[ 4.463] ...WARN: Get Info failed to open 1 slot 0, partition 0, error 0
[ 4.464] ...ERROR: Failed to get device info slot:0artition:0
[ 4.464] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 4.464] ...ERROR 14: Line 1283: HANDLE_STORAGE_INFO_FAILURE
[ 4.465] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 4.465] Check qboot_log.txt for more details
[ 4.466] Total time: 4.468s
[ 4.466]
[ 4.466] qboot version 3.86
[ 4.466]
[ 4.466] DEVICE {
[ 4.466] name = "\\.\COM5",
[ 4.466] flags = "0x144",
[ 4.466] addr = "0x62FD64",
[ 4.466] sahara.current_mode = "0",
[ 4.466] api.buffer = "0xEC5020",
[ 4.466] cpu.serial = "518110791",
[ 4.466] cpu.id = "172",
[ 4.466] cpu.sv_sbl = "1",
[ 4.466] cpu.name = "SDM630",
[ 4.466] storage.type = "eMMC",
[ 4.466] sahara.programmer = "programmer.elf",
[ 4.466] module.firehose = "0xFFEAB8",
[ 4.466] api.firehose = "0xFFEF20",
[ 4.466] cpu.ver = "256",
Click to expand...
Click to collapse
Has anyone else experienced this? Or can anyone explain to me what tools to use and what they do? I am very new to this unbricking process.

Categories

Resources