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.

Eris msm_pm_wait_state reboot syndrome?

Hi folks,
Long time since I popped in here.
I'm wondering if you've seen behavior similar to this before:
Spontaneous reboots during suspend/resumes (that is, an app running but the screen is off) which *sometimes* result in output like this at the tail end of /proc/last_kmsg
Code:
[ 2331.773132] msm_pm_wait_state(80, 0, 0, 0) failed 10d29
[ 2331.773132] msm_sleep(): msm_pm_wait_state failed, 10d29
[ 2331.929382] msm_pm_wait_state(80, 0, 0, 0) failed 10d29
[ 2331.929382] msm_sleep(): msm_pm_wait_state failed, 10d29
No errors detected
I can manage to run logcat as a background process (the syndrome seems to involve the kernel PM (Power Management) suspend/resume function, as it refuses to occur when plugged in to USB); sometimes I also see
Code:
09-01 21:07:58.371 273 416 E RPC : error writing RPC packet: 22 (Invalid argument)
as the last line in the logcat. I don't know what is lost in the logcat output after that due to buffering, but the "No errors detected" in /proc/last_kmsg seems to point away from a kernel panic. And yet the phone reboots in a decidedly ungraceful fashion... if all filesystems were flushed I would expect to see something in the logcat about a reboot.
Test conditions:
Kernel: 2.6.29-DecaFuctCFS-dirty-9ff84b92 ([email protected]) (gcc version 4.4.0 (GCC) ) #5 PREEMPT Thu Jan 27 22:14:44 EST 2011
ROM: Condemned Soul's CCM7-V21 Vanilla
CM CPU min/max: 245/729 (* I don't think this matters)
Governor: ondemand
Other: Screen must be off and phone disconnected from external (USB) power for this reboot to occur; my test condition also includes the phone in Airplane mode. (I do not know if the latter is necessary for bug expression).
I can add more detail, but I didn't want my post to get too long. I can cause this to happen deterministically (a delay of one to several minutes before the phone reboots). The app involved uses the GPS hardware...
Anyhow... does this syndrome sound familiar at all?
bftb0
PS Yes this is a real-world scenario - I want to do GPS track recording in areas without cell/wifi service, so... running without USB power and no radios (for battery conservation) is a priority.

[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

[Q] Errors when attempting to SBF reset

So I Found my old Droid X earlier this week the battery was bad so I got a new one and I attempted to restore the device using tomsgt123's (RootJunky) video (I can't post links ) and RSDlite must have froze on me because it got stuck and 98% of something to do with ram (I can't find a log so I can't rely be more specific) and then I let it sit thinking it was just taking a while and I came back nothing was on the program and my device just says code corrupted battery low cannot program.
So what I am wondering is if I can retry If i can manage to get the battery charged or if this thing just became a brick
I should also mention that when I pressed start on RSDlite my battery was fully charged
Thank You in advance if you can help me.
Edit I found a log actually
2014/07/04 10:51:29 | -- | ERROR: AP Die ID: 1e300210fa903a0a0000d8ff0100
2014/07/04 10:51:29 | -- | ERROR: BP Die ID: 0000000000000000b55432890485
2014/07/04 10:51:29 | -- | ERROR: AP Public ID: 2469367a1407acd048a3f1e89f054bd90523fa08
2014/07/04 10:51:29 | -- | ERROR: BP Public ID: 040000000500000002000000ffff00002d003289
2014/07/04 11:14:29 | 0 | ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x156000 Command: ADDR ->(970)RDLOp
2014/07/04 11:14:29 | 0 | ERROR: Phone[0000]: Flash failed. ->(1195)PST_FP_FlashThread
2014/07/04 11:14:31 | 0 | ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x156000 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257 ->(625)FlashHdlr

Motorola Drivers are not installed on windows.
Install drivers or use DX (MB810) ezSBF & Root 2.3.4/4.5.621

Ill Try
Ok, Thanks I thought I had the drivers installed already though as Ive already done some work on other motorola devices this week. But I'm ordering a battery charger should be here in a couple days and I'm going to try the live CD method Ive already burned the CD so Thanks

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