Database Users

Flashing failes everytime I try to flash. Rsdlite error included

This was my first time.
I did all what was required.
But when I started the flash through RSD lite after just 1 min it showed me FAIL
It went from 1% to 100% once, and then it showed FAIL
Now when I unplugged the USB and remove the battery and insert it back again it automaticaly goes into bootloader and then I tried to flash again which gave me same result.
This is my phone status.
The screen shows
Code Corrupt
Battery OK
OK to Program
Trasnfer Mode:
USB
This is what the Rsdlite Error log file has.
22:32:29, May 13, 2012
Line: 537
ERROR: AP Die ID: 1140010e560368010000dcff0200
22:32:29, May 13, 2012
Line: 544
ERROR: BP Die ID: 0000000000000000000000000000
22:32:29, May 13, 2012
Line: 551
ERROR: AP Public ID: 785fdd0a961a8e4b1e6a0497d703ee271d20c5c0
22:32:29, May 13, 2012
Line: 558
ERROR: BP Public ID: 0000000000000000000000000000000000000000
22:32:29, May 13, 2012
Line: 709
ERROR: Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE0030040 Command: ERASE
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\ErasingOp.cpp
Device ID: 0
22:32:29, May 13, 2012
Line: 1195
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
22:32:29, May 13, 2012
Line: 610
ERROR: Flash failure: Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE0030040 Command: ERASE (Error Code: e0030040),
Detailed Error Details: Direction of the Error=2000, Command Value=100000, Code Group Number=No Codegroup
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Click to expand...
Click to collapse
Please someone reply asap.

use the recommened rsdlite version...i have seen many other version of rsdlite gives such errors..i actually dont remember the exact version ..haven't used it for a while..
do a search in this forum..
All the best

I have read few other places and it said to use RSDLITE 4.9, which I did.

try version 3.4.8 if m not wrong..

Which one do you used for flashing?

i think the above version only..i have recommended the same version to many people and it works like a charm in past..search this forum for rsdlite stable version by experience of people..

I did successfully flash my Defy+ with RSDLite v5.6 (search the forum or google)
Maybe there's something wrong with your sbf-file? Just a wild guess, don't know if the error message tells actually something different...

Thanks for your time guys. I was trying to flash on my Desktop with no avail.
Tried on my lappy and Bingo its all done perfectly.
Happy I have finally upgraded to CM7 its really nice and fast.

[Q] ppp widget not working

Dear friends,
I have rooted nexus 7 2012, and installed PPP widget. I have configured the APN. It says "connected", but the internet is not working. Here is the PPP widget log, please help me:
PPP Widget version 1.3.3
USB_ModeSwitch log from Mon Dec 23 15:00:41 IST 2013
Raw args from udev: 2-1/2-1:1.0
Using top device dir /sys/bus/usb/devices/2-1
----------------
USB values from sysfs:
manufacturer USB Modem
product USB Modem
serial 1234567890ABCDEF
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/1c9e.f000
! matched. Reading config data
devList 1:
config: TargetVendor set to 1c9e
config: TargetProductList set to 9000,9603,9605,9607
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 2 -g 2 -v 1c9e -p f000 -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.7 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1c9e
DefaultProduct= 0xf000
TargetVendor= 0x1c9e
TargetProduct= not set
TargetClass= not set
TargetProductList="9000,9603,9605,9607"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
QuantaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
BlackberryMode=0
PantechMode=0
MessageEndpoint= not set
MessageContent="55534243123456788000000080000606f50402527000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 002/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 1c9e:f000
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: USB Modem
Product: USB Modem
Serial No.: 1234567890ABCDEF
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Resetting response endpoint 0x81
Resetting message endpoint 0x01
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Reading attributes ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 1c9e:9605 (USB Modem: USB Modem)
Device class of first interface is ff
Now checking for bound driver ...
Driver has bound, device is known
All done, exiting

Droid RAZR M: Qflash Utility Help

QFLASH Problem
What the hell .. squint emoticon
"No data read from USB. This may not be an error. Trying again..."
if anyone knw about it so Guide me .i am very close :|
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>python 8960_blankflash.py
Emergency download enumeration detected on port - com3
Starting qflash!
Executing command qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloa
der_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM3
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
dmss_go : failed to receive ACK
Error loading MPRG8960.hex into device
Blank flashing successful
Device will now enumerate in fastboot mode
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>pause
Press any key to continue . .

lumia 520 help to recover

today morning my lumia 520 just hang up and rebooted and shown me no bootable options press any key to reboot..but i cant recover it with WDRT ,WPI or any...any my observations are say its partition are converted GPT to MBR .
can anyone help me to give instruction to part it..
attachment are given below.
thanks

Hi,
you might try:
if your mobile still is in mass storage mode, try to mount ffu file with IMGMOUNT utility, then try to repartition MSM and copy single partitions. I do not know much about MSM partitioning, so please verify my advise with someone more experienced!
Alternatively:
SFFU programming and Full NVI update:
thor2 -mode uefiflash -ffufile "your ffu file name" -do_full_nvi_update -do_factory_reset
I had a case where it worked to recover from flight mode & no IMEI issue.
You have to localize thor2.exe in a command line window, preferable as administrator.
You will find thor2.exe in C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
When ffu file is not accepted, try to drop ffu file statement
Best whishes!

JoachimP said:
Hi,
you might try:
if your mobile still is in mass storage mode, try to mount ffu file with IMGMOUNT utility, then try to repartition MSM and copy single partitions. I do not know much about MSM partitioning, so please verify my advise with someone more experienced!
Alternatively:
SFFU programming and Full NVI update:
thor2 -mode uefiflash -ffufile "your ffu file name" -do_full_nvi_update -do_factory_reset
I had a case where it worked to recover from flight mode & no IMEI issue.
You have to localize thor2.exe in a command line window, preferable as administrator.
You will find thor2.exe in C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
When ffu file is not accepted, try to drop ffu file statement
Best whishes!
Click to expand...
Click to collapse
Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>cd C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile "F:\LumiaDeviceRecovery\RM-914\1.ffu" -do_full_nvi_update -do_factory_reset
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -ffufile F:\LumiaDeviceRecovery\RM-914\1.ffu -do_full_nvi_update -do_factory_reset
Process started Tue May 23 11:25:55 2017
Logging to file C:\Users\AMBALI~1\AppData\Local\Temp\thor2_win_20170523112555_ThreadId-7928.log
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Get flashing parameters
Lumia Boot Manager detected
Check status of battery
State of charge 3, charging current 0
Warning: Battery level low. Charge battery to 10 % of max charge.
Protocol version 1.1 Implementation version 1.16
Detecting UEFI responder
HELLO success
Lumia Boot Manager detected
Check status of battery
State of charge 3, charging current 0
Warning: Battery level low. Charge battery to 10 % of max charge.
Protocol version 1.1 Implementation version 1.16
Booting to FlashApp
Reboot to FlashApp command sent successfully.
DetachFrom connection
Verifying that device is online
Device is online
Detecting UEFI responder
HELLO success
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Disable timeouts
Get flashing parameters
Lumia Flash detected
Protocol version 1.15 Implementation version 1.28
Size of one transfer is 2363392
Size of buffer is 2359296
Number of eMMC sectors: 0
Platform ID of device: Nokia.MSM8227.P6036.1.2
Async protocol version: 01
Security info:
Platform secure boot disabled
Secure FFU disabled
JTAG eFuse blown
RDC not found
Authentication not done
UEFI secure boot enabled
SHK enabled
Device supports FFU protocols: 0019
[THOR2_flash_state] Device programming started
Using secure flash method
CoreProgrammer version 2015.06.10.001.
Start programming signed ffu file F:\LumiaDeviceRecovery\RM-914\1.ffu
FfuReader version is 2015061501
Send FlashApp write parameter: 0x4d544f00
Perform handshake with UEFI...
Flash app: Protocol Version 1.15 Implementation Version 1.28
DevicePlatformInfo: Nokia.MSM8227.P6036.1.2
Unknown sub block detected. Skip...
Unknown sub block detected. Skip...
Supported protocol versions bitmap is 19
Secure FFU sync version 1 supported.
Secure FFU async version 1 supported.
Secure FFU async version 3 supported.
Get CID of the device...
Get EMMC size of the device...
Emmc size in sectors: 0
CID: Unknown ManId: 0
Start charging...
Requested write param 0x43485247 is not supported by this flash app version.
Start charging... DONE. Status = 0
Unable to send ECHO REQ or ECHO REQ not supported
Get security Status...
Security Status:
Platform secure boot is disabled.
Secure eFUSE is disabled.
JTAG is disabled.
RDC is missing from the device.
Authentication is not done.
UEFI secure boot is enabled.
Secondary HW key exists.
Get ISSW Version...
Get ISSW Version, SKIPPED!
Get system memory size...
Size of system mem: 524288 KB
Read antitheft status...
Requested read param 0x41545250 is not supported by this flash app version.
Send backup to RAM req...
UEFI returned error: 0xfa000006
Do backup to the RAM of device failed!
0xFA000006: Backup failed. Reason(s): FlashApp cannot find partition.
Operation took about 42.00 seconds.
THOR2_ERROR_FA_ERR_PARTITION_NOT_FOUND
THOR2 1.8.2.18 exited with error code -100663290 (0xFA000006)
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool>

So if your device still goes to MSM (e.g. using WPInternals or a thor2 command) try to repartition it and copy the partitions from mounted ffu file.
Otherwise the only way is JTAG programming.
Best whishes!

JoachimP said:
So if your device still goes to MSM (e.g. using WPInternals or a thor2 command) try to repartition it and copy the partitions from mounted ffu file.
Otherwise the only way is JTAG programming.
Best whishes!
Click to expand...
Click to collapse
doesen't switch to mass storage mode

Hi,
please have a look at this thread: look for a developer ROM for your model and try. Unfortunately I sold my bricked device, so I cant. I had a look at Lumia Firmware, but found no developer ROM, so I guess, you could give these PWBASSY ROMs a try?
Regards,
Joachim

Unable to reflash ROM or install custom ROM

I've been screwing around with this for three weeks and I'm unable to make ANY headway no matter how much I search.
I had rooted my s7 edge when I first got it 6 months ago and followed a guide on here which I'm unable to locate. My phone started acting super crazy and losing running apps and apps closing unexpectedly. For example while watching Netflix, the card with the netflix controls in the dropdown would disappear after only a few minutes and netflix would forget it was connected to a chromecast, among other things.
I performed a factory reset. Upon reset and reinstalling my apps I went to try a system update in Settings. Clicking on it immediately results in "Unfortunately Settings has Stopped" and crashing out to the home screen. I recall the root method had some sort of add-on you could flash that disabled/removed many bloatwares and certain "features" and things on the phone including system update.
As I can't find the instructions I used I decided to simply flash the latest firmware using Odin 3.10.7 and 3.11.1 and this method: https://forum.xda-developers.com/verizon-s7-edge/how-to/odin-stock-nougat-firmware-t3570156
Odin checks the files just fine. When the start button is pressed odin sits for 3minutes attempting to set up the connection, then fails out with a red FAIL.
Attempting to install TWRP using heimdall on windows results in:
Code:
C:\Users\pl\Desktop\Heimdall Suite>heimdall flash --RECOVERY twrp-3.1.1-0-hero2lte.img --no-reboot --verbose
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8996"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
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: 82
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: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
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 RECOVERY
0%
...
100%
RECOVERY upload successful
Ending session...
ERROR: Failed to unpack received packet.
ERROR: Failed to receive session end confirmation!
Releasing device interface...
A similar attempt on linux using Heimdall 1.4.1 results in dozens of warnings throughout
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway..."
On the phone itself the little progress bar starts moving across the screen, but immediately stops and a red error appears
SECURE CHECK FAIL : recovery
The full text of the information on the screen is as follows
Code:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE
AP SWREV: B2(2, 1, 1, 1, 1) K1 S1
SECURE DOWNLOAD : ENABLE
I have attempted to perform this on 3 separate machines, one each of windows, mac and linux, using all sorts of various versions of odin, and heimdall and I've been unable to get anything working. Any help is appreciated.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

might seem like a stupid question but do you have the proper drivers installed and are you using the factory cable? You can also try a different Odin I know some people have luck with different ones.
I cant provide much input other than unplug replug see if your computer will recognize the phone as being attached...or try a different odin.

We can't install twrp on the s7 with the snapdragon processor. The bootloaders are locked tight.

Correct, the moment I read TWRP, I had a moment of silence for the OP's phone.

TWRP is a no go due to locked bootloader. The reason system update crashes is because the apps needed for the updater are removed during the root fix process. You can flash back to stock with Odin. Marshmallow and Nougat can both be rooted, so take your pick. As for Netflix, I have issues with it forgetting that it's connected to my Chromecast all the time. I'm currently on a non-rooted ROM, but I've had this issue when the phone was stock or rooted.

tacticalone said:
Code:
C:\Users\pl\Desktop\Heimdall Suite>heimdall flash --RECOVERY wrp-3.1.1-0-hero2lte.img t --no-reboot --verbose
Click to expand...
Click to collapse
Bit of a dredge, I realise, as I've just dug out an old 310F as a spare handset and had a similar problem
I fixed it by renaming the recovery image as recovery.img (as opposed to wrp-3.1.1-0-hero2lte.img, for example)
Code:
heimdall flash --RECOVERY recovery.img t --no-reboot --verbose