Related
I have trouble with my first vb.net program.
The program have to wirite the gps stream into a listbox and a file,too.
i have opened com9 on my trinity for the gps
(on a tytn->bluetooth->com9, too) but the app crash with "ioexception".
can someone pleade help me.
i dont know what i can do now.
Here's the complete Code:
an IO Exception occurs when there are errors while interacting with files.
Instead of posting your solution over here would it be better to learn how to debug.
- Look for additional information. An Exception contains more information than just 'ioexception'.
- Step through your application to find the line where the error occurs.
- Do you close your file properly? (after writing the GPS stream)
Only with files?
I think it crashed at: "SerialPort1.Open()"
Yes i close the File. But there ist no Stream. I get no information from the port,
cause at the opening the program crashed :-(
sorry for my bad english. i give my best.
here's the edited version:
http://rapidshare.com/files/62896996/GPRSGPS.ZIP.html
IO = Input Output, so basically files but indeed also with serial ports. Can you provide us additional information about the error?
Sorry only the complete german Error Message:
Unerwarteter Fehler in GPRSGPS.exe,
klicken Sie auf "Beenden", und starten Sie das Programm neu.
Weitere Informationen zu diesem Fehler erhalten Sie, indem Sie Details Klicken.
Es kann keine Fehlermeldung angezeigt werden, da
die optionale Ressource der Assebly,
die die Fehlermeldung enthält, nicht gefunden wurde.
IOEXCEPTION
Click to expand...
Click to collapse
Here is an example
Code:
Try
For nVar = 0 To 5 Step 1
Response.Write(arTest(nVar))
Next
Catch e As Exception
messagebox(e.toString)
End Try
(source: http://www.aspheute.com/artikel/20001024.htm)
build something like this around your SerialPort1.open()
e.g.
Code:
Try
SerialPort1.open()
Catch e As Exception
MsgBox(e.toString)
End Try
thank you for yours strive but it still don't work.
I do not have any ideas.
why don't you just set a breakpoint and start in in debug mode?
Because the "FakeGPS"Tool out of the WM6 SDK wouldnt work.
So cant emulate a GPS Stream and i have to test it on my htc trinity.
even when i set a break point, the application crashed bevor i reached the point.
just set your pda as target device and not the emulator, you CAN debug on real devices!
even when i set a break point, the application crashed bevor i reached the point.
Click to expand...
Click to collapse
Then move your Breakpoint!!!
thanks. yes the debug on real device works now.
Ohho....
the error ist not the "Serial1.Open"
else this function
Code:
Private Sub ListAdd(ByVal Ttext As String, Optional ByVal Write2File As Boolean = False)
'Den Focus auf den zuletzt inder Lisbox hinzugefügten Datensatz legen
'ebenfalls die Zeile in die oben deklarierte Datei speichern.
If Ttext <> "" And Len(Ttext) > 0 Then
'Versuch mit Messagebox = ok
'MsgBox(Ttext)
'Verusch mit einfach Listbox = absturz
'ListBox1.Items.Add(Ttext)
'Versuch mit Textbox= absturz
'TextBox1.Text = Ttext + vbNewLine + TextBox1.Text
'Versuch mit Listbox die automatisch den Fokus auf den zuletzt
'hinzugefügten Datensatz legt
'With ListBox1
'.Items.Add(Ttext)
'If .Items.Count > 0 Then
'.SelectedIndex = .Items.Count - 1
'End With
'Wenn Write2File=True dann soll er den TText ins File schreiben
If Write2File = True Then txt.WriteLine(Ttext)
End If
End Sub
i have re-edited the function once again:
Code:
Private Sub ListAdd(ByVal Ttext As String, Optional ByVal Write2File As Boolean = False)
'Versuch mit Listbox die automatisch den Fokus auf den zuletzt
'hinzugefügten Datensatz legt
Try
With ListBox1
.Items.Add(Ttext)
If .Items.Count > 0 Then
.SelectedIndex = .Items.Count - 1
End If
End With
'Wenn Write2File=True dann soll er den TText ins File schreiben
If Write2File = True Then txt.WriteLine(Ttext)
Catch e As Exception
'MsgBox(e.ToString)
txt.WriteLine(e.ToString)
If X = 10 Then 'Bei 10 Fehlern Text File speichern.
txt.Close()
Application.Exit()
End If
End Try
End If
End Sub
So it logged 10 Errors in a File:
Code:
System.NotSupportedException: Es kann keine Fehlermeldung angezeigt werden, da die optionale Ressource der Assembly, die die Fehlermeldung enthält, nicht gefunden wurde.
bei Microsoft.AGL.Common.MISC.HandleAr()
bei System.Windows.Forms.ListBox._NativeAdd()
at ObjectCollection.Add()
bei DeviceApplication1.Form1.ListAdd()
bei DeviceApplication1.Form1.SerialPort1_DataReceived()
bei System.IO.Ports.SerialPort.CatchReceivedEvents()
at EventLoopRunner.CallReceiveEvents()
at WorkItem.doWork()
bei System.Threading.Timer.ring()
System.NotSupportedException: Es kann keine Fehlermeldung angezeigt werden, da die optionale Ressource der Assembly, die die Fehlermeldung enthält, nicht gefunden wurde.
bei Microsoft.AGL.Common.MISC.HandleAr()
bei System.Windows.Forms.ListBox._NativeAdd()
at ObjectCollection.Add()
bei DeviceApplication1.Form1.ListAdd()
bei DeviceApplication1.Form1.GetGSM_STATUS()
bei DeviceApplication1.Form1.SerialPort1_DataReceived()
bei System.IO.Ports.SerialPort.CatchReceivedEvents()
at EventLoopRunner.CallReceiveEvents()
at WorkItem.doWork()
bei System.Threading.Timer.ring()
System.NotSupportedException: Es kann keine Fehlermeldung angezeigt werden, da die optionale Ressource der Assembly, die die Fehlermeldung enthält, nicht gefunden wurde.
bei Microsoft.AGL.Common.MISC.HandleAr()
bei System.Windows.Forms.ListBox._NativeAdd()
at ObjectCollection.Add()
bei DeviceApplication1.Form1.ListAdd()
bei DeviceApplication1.Form1.SerialPort1_DataReceived()
bei System.IO.Ports.SerialPort.CatchReceivedEvents()
at EventLoopRunner.CallReceiveEvents()
at WorkItem.doWork()
bei System.Threading.Timer.ring()
System.NotSupportedException: Es kann keine Fehlermeldung angezeigt werden, da die optionale Ressource der Assembly, die die Fehlermeldung enthält, nicht gefunden wurde.
bei Microsoft.AGL.Common.MISC.HandleAr()
bei System.Windows.Forms.ListBox._NativeAdd()
at ObjectCollection.Add()
bei DeviceApplication1.Form1.ListAdd()
bei DeviceApplication1.Form1.GetGSM_STATUS()
bei DeviceApplication1.Form1.SerialPort1_DataReceived()
bei System.IO.Ports.SerialPort.CatchReceivedEvents()
at EventLoopRunner.CallReceiveEvents()
at WorkItem.doWork()
bei System.Threading.Timer.ring()
System.NotSupportedException: Es kann keine Fehlermeldung angezeigt werden, da die optionale Ressource der Assembly, die die Fehlermeldung enthält, nicht gefunden wurde.
bei Microsoft.AGL.Common.MISC.HandleAr()
bei System.Windows.Forms.ListBox._NativeAdd()
at ObjectCollection.Add()
bei DeviceApplication1.Form1.ListAdd()
bei DeviceApplication1.Form1.SerialPort1_DataReceived()
bei System.IO.Ports.SerialPort.CatchReceivedEvents()
at EventLoopRunner.CallReceiveEvents()
at WorkItem.doWork()
bei System.Threading.Timer.ring()
System.NotSupportedException: Es kann keine Fehlermeldung angezeigt werden, da die optionale Ressource der Assembly, die die Fehlermeldung enthält, nicht gefunden wurde.
bei Microsoft.AGL.Common.MISC.HandleAr()
bei System.Windows.Forms.ListBox._NativeAdd()
at ObjectCollection.Add()
bei DeviceApplication1.Form1.ListAdd()
bei DeviceApplication1.Form1.GetGSM_STATUS()
bei DeviceApplication1.Form1.SerialPort1_DataReceived()
bei System.IO.Ports.SerialPort.CatchReceivedEvents()
at EventLoopRunner.CallReceiveEvents()
at WorkItem.doWork()
bei System.Threading.Timer.ring()
System.NotSupportedException: Es kann keine Fehlermeldung angezeigt werden, da die optionale Ressource der Assembly, die die Fehlermeldung enthält, nicht gefunden wurde.
bei Microsoft.AGL.Common.MISC.HandleAr()
bei System.Windows.Forms.ListBox._NativeAdd()
at ObjectCollection.Add()
bei DeviceApplication1.Form1.ListAdd()
bei DeviceApplication1.Form1.SerialPort1_DataReceived()
bei System.IO.Ports.SerialPort.CatchReceivedEvents()
at EventLoopRunner.CallReceiveEvents()
at WorkItem.doWork()
bei System.Threading.Timer.ring()
System.NotSupportedException: Es kann keine Fehlermeldung angezeigt werden, da die optionale Ressource der Assembly, die die Fehlermeldung enthält, nicht gefunden wurde.
bei Microsoft.AGL.Common.MISC.HandleAr()
bei System.Windows.Forms.ListBox._NativeAdd()
at ObjectCollection.Add()
bei DeviceApplication1.Form1.ListAdd()
bei DeviceApplication1.Form1.GetGSM_STATUS()
bei DeviceApplication1.Form1.SerialPort1_DataReceived()
bei System.IO.Ports.SerialPort.CatchReceivedEvents()
at EventLoopRunner.CallReceiveEvents()
at WorkItem.doWork()
bei System.Threading.Timer.ring()
System.NotSupportedException: Es kann keine Fehlermeldung angezeigt werden, da die optionale Ressource der Assembly, die die Fehlermeldung enthält, nicht gefunden wurde.
bei Microsoft.AGL.Common.MISC.HandleAr()
bei System.Windows.Forms.ListBox._NativeAdd()
at ObjectCollection.Add()
bei DeviceApplication1.Form1.ListAdd()
bei DeviceApplication1.Form1.SerialPort1_DataReceived()
bei System.IO.Ports.SerialPort.CatchReceivedEvents()
at EventLoopRunner.CallReceiveEvents()
at WorkItem.doWork()
bei System.Threading.Timer.ring()
Last but not least the complete project:
http://rapidshare.com/files/63389284/GPRSGPS.ZIP.html
IT WORKS
Now it works. (thx to "Useless User" from "PPC-Welt")
SUPER SUPER SUPER.
Here's the right code:
Code:
Imports System.IO
Public Class Form1
Dim X As Integer
Dim APPPATH As String
Dim GlobalGPSSTREAM As String
Dim txt As IO.StreamWriter
Private Delegate Sub SetGlobalGPSStreamDgt(ByVal text As String)
Private Sub SetGlobalGPSSTREAM(ByVal text As String)
ListAdd(text, True)
End Sub
Private Sub ShowVerNumber()
'App.Path und App.Minor etc Test
APPPATH = System.IO.Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().GetModules(0).FullyQualifiedName) & "\"
txt = New IO.StreamWriter(APPPATH + "testfile.txt", True)
ListAdd("Datenfile: " + APPPATH + "testfile.txt", False)
Me.Text = "GPRSGPS V" + GetType(Form1).Assembly.GetName.Version.ToString()
'ListAdd("Progfile: " + Me.Text, False)
'Me.Text = Path.GetDirectoryName(Assembly.GetExecutingAssembl y().GetModules(0).FullyQualifiedName) & "/"
'App.Path & IIf(Right(App.Path, 1) = "\", "", "\") & App.EXEName
End Sub
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
Listbox1.Items.Clear()
'TextBox1.Items.Clear()
ShowVerNumber()
SerialPort1.Encoding = System.Text.Encoding.Default
'SerialPort1.Encoding = System.Text.Encoding.ASCII
End Sub
Private Sub ListAdd(ByVal Ttext As String, Optional ByVal Write2File As Boolean = False)
'Den Focus auf den zuletzt inder Lisbox hinzugefügten Datensatz legen
'ebenfalls die Zeile in die oben deklarierte Datei speichern.
If Ttext <> "" And Len(Ttext) > 0 Then
Try
With ListBox1
.Items.Add(Ttext)
If .Items.Count > 0 Then
.SelectedIndex = .Items.Count - 1
End If
End With
'Wenn Write2File=True dann soll er den TText ins File schreiben
If Write2File = True Then txt.WriteLine(Ttext)
Catch e As Exception
'MsgBox(e.ToString)
txt.WriteLine(e.ToString)
If X = 10 Then 'Bei 10 Fehlern Text File speichern.
txt.Close()
Application.Exit()
End If
End Try
End If
End Sub
Private Sub GetGSM_STATUS()
'Anzeigen der aktuellen Mobilfunk-Signal-Stärke
X = X + 1 'Zeilenzähler
ListAdd(Microsoft.WindowsMobile.Status.SystemState.PhoneSignalStrength, True)
End Sub
Private Sub SerialPort1_DataReceived(ByVal sender As Object, ByVal e As System.IO.Ports.SerialDataReceivedEventArgs) Handles SerialPort1.DataReceived
Dim newLine As String = SerialPort1.ReadLine
Me.Invoke(New SetGlobalGPSStreamDgt(AddressOf SetGlobalGPSSTREAM), New Object() {newLine})
End Sub
Private Sub BTN_STOP_Click_1(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles BTN_STOP.Click
txt.Close()
Application.Exit()
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
'Dim txt As IO.StreamWriter = New IO.StreamWriter("datei.txt"), False, System.Text.Encoding.Default)
'txt.WriteLine("blablabla")
'txt.WriteLine("")
'txt.Close()
End Sub
Private Sub BTN_COM_OPEN_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles BTN_COM_OPEN.Click
If SerialPort1.IsOpen = True Then SerialPort1.Close()
'SerialPort1.PortName = Trim("COM" + Trim(Str(NumericUpDown1.Value)) + ":")
SerialPort1.PortName = Trim("COM" + Trim(Str(NumericUpDown1.Value)))
'ListAdd("COMPORT Setting: " + SerialPort1.PortName, False)
Try
SerialPort1.Open()
Catch Ausnahme As IOException
MsgBox(Ausnahme.Message, MsgBoxStyle.Critical, "Fehler !")
End Try
'MsgBox(SerialPort1.PortName)
End Sub
Private Sub BTN_COM_CLOSE_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles BTN_COM_CLOSE.Click
If SerialPort1.IsOpen = True Then SerialPort1.Close()
'ListAdd("COMPORT geschlossen", False)
End Sub
Private Sub Timer1_Tick(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Timer1.Tick
If SerialPort1.IsOpen = True Then
Label1.BackColor = Color.Green
Else
Label1.BackColor = Color.Red
End If
End Sub
Private Sub BTN_WriteHallo_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles BTN_WriteHallo.Click
'ListAdd("Hallo", False)
End Sub
End Class
, i hope you understand where you made mistakes .
not really. its a hard way from vb6 to .net
modified/pached hpRUU.exe?
--------------------------------------------------------------------------------
i would like to know if somebody here already have patched or modified the original hpRUU.exe for the ipaq hw69xx series in order to allow uploading a different ROM-image(e.g different language etc.) to the device.
as far as i know it would be enough to disable the pre-check and jump directly to the start of the flashing routine itself.
i tried In each method this already by myself, but it seems it isn't as easy as i thought.
any help is appreciated...
In the appendix has HP iPAQ hw6900 Mobile Messenger Series ROM Update
BIOS from that link:
http://h20000.www2.hp.com/bizsuppor...18&mode=2&taskId=135&swItem=PSG_I23843-109104
1.download GSM BIOS from that link:
http://h20000.www2.hp.com/bizsuppor...sId=1822489&swLang=8&taskId=135&swEnvOID=2067
2.download all ROM BIOS from that link:
http://h20000.www2.hp.com/bizsuppor...18&mode=2&taskId=135&swItem=PSG_I23843-109104
best regards,
Caoxt
my icq:381-821-742
my msn:[email protected]
Now,my ipaq hw6915 reatar On demonstrates NO GSM underneath the screen !
Under the picture was I has attempted a method, is not all good .
NO GSM error
matrix21 said:
Anyone here could come up with a solution for the NO GSM error?
Pls help..
Click to expand...
Click to collapse
Let us try to find solution together.
Ipaq HW69XX ENGLISH_UPDATE_UNIT.rar
This is primitive ENGLISH_UPDATE_UNIT downloading link :
http://rapidshare.com/files/46350136/Ipaq_HW69XX_ENG_ROM.rar.html
caoxt said:
This is primitive ENGLISH_UPDATE_UNIT downloading link :
http://rapidshare.com/files/46350136/Ipaq_HW69XX_ENG_ROM.rar.html
Click to expand...
Click to collapse
Sorry, could you please explain a bit more what this is?
What means do some people know to be possible backup GSM RADIO?
What means do some people know to be possible backup GSM RADIO?
It is nothing more than hp rom updater and german rom in package called Ipaq...ENG_ROM.rar.
For those, who want patched HPruu.exe to flash any laguage CEOS.nbf there is attached hpruu.exe. It will NOT flash RADIO!!!.
you can help me?
Thanks you to be able to provide this procedure, I use him to be possible to flash OS, I have the discovery, may flash the RADIO HPRUU.EXE size is 984KB, the edition number is 3.4.0.6, it comes from: http://h20000.www2.hp.com/bizsuppor...swLang=13&mode=2&taskId=135&swItem=ip-51988-1, you can help me?
karol_ said:
It is nothing more than hp rom updater and german rom in package called Ipaq...ENG_ROM.rar.
For those, who want patched HPruu.exe to flash any laguage CEOS.nbf there is attached hpruu.exe. It will NOT flash RADIO!!!.
Click to expand...
Click to collapse
Specially orders reads to flash RADIO has the help,Recent clue, Similarly passes
Recent clue, Similarly passes on 6915
Specially orders reads to flash RADIO has the help:
password
set
erase
task
lw
rtask
The HP IPAQ 6515 uses the boot loader2 password to unlock the full help menu in the serial console interface. It does not allow access to more commands than before and simply shows help for more commands.
If you are interested in viewing the commands there are a couple of passwords that would unlock it depending on your exact 6515 model.
• BOOTLOADER
• BEETLES
• 0000000000000000 - (16 x 0s) password for level 1 which unlocks additional RUU functions
Personally, both BOOTLOADER and 0000000000000000 worked fine for me on a HP IPAQ 6515e and you can enter level 1 directly with 0000000000000000
USB>password BOOTLOADER
HTCSPass.<Y-HTCEUSB>password 0000000000000000
HTCSPass1.CM^EHTCEUSB>
If you typed the wrong password, you will get
USB>password 0000000000000000
HTCSInvalid password
Similarly passes on 6915 !
This is a use MTTY Connection of me exploring the IPAQ 6515e’s bootloader firmware
USB>? full
Available monitor commands are:
? [command] [full]
h [command] [full]
r [[register] [[=] [hex_value]]]
eb Addr
eh Addr
ew Addr
mb [StartAddr [Count [Filler]]]
mh [StartAddr [Count [Filler]]]
mw [StartAddr [Count [Filler]]]
string [Type [String]]
info [Type [Value]]
password [string]
l [path_name [startAddr offset ["cp"]]]
lnb nb-file [StartAddr [Length [SkipOffset ["cp"]]]]
ppdl [startAddr offset["cp"]]
s StartAddr Count Pattern...
map
cp reg# OPC_2 CRm [value]
stress [Type [Count(Hex)]]
d2s [StartAddr [Len [Type [Append[SkipStartAddr SkipLen]]]]]
s2d
set [Type [Value]]
task [Type [Value [Value1]]]
shmsg [Row [Col ["String"]]]
rbmc [FileName [StartAddr [Len]]]
erase [StartAddr [Len]]
wdata [StartAddr [Len]]
checksum [StartAddr [Len]]
prouter [PortID1[Baud1[PortID2[Baud2]]]]
lw [path_name [startAddr offset ["cp"]]]
rtask [Type [Value]]
rroute [UART Path1[Baud Rate1[UART Path2[Baud Rate2]]]]
USB>? set
Usage:
set [Type [Value]]
Set control flags.
Type(hex) : Control function types.
Value(hex) : Setting values for types.
If value is not given, default is 0.
Type 0(Echo on/off): 1(on) and 0(off).
Type 1(Operation mode): 1(auto) and 0(user).
Type 2(Back color on/off): 1(on) and 0(off).
Type 3(Inverse on/off): 1(on) and 0(off).
Type 4(Front color value): 16 bits data
Type 5(Background color value): 16 bits data
Type 6(Set color of screen): Fill color to whole screen one time.
Type 8(COMM queue flag): 0(TX_RX disable),1(RX enable),2(TX enable) and 3(TX_RX enable).
Type 1E(RUU command read/write flag): 1(unlock) and 0(lock).
Current flag settings:
Type 0(Echo flag): cEchoFlag=(0x1).
Type 1(Operation mode flag): cOpModeFlag=(0x0).
Type 2(Back color flag): cBackColorShowFlag=(0x1).
Type 3(Inverse flag): cShowInverseFlag=(0x0).
Type 4(Front color): g_wFColor=(0x0).
Type 5(Background color): g_wBColor=(0xFFFF).
Type 6(Set color of screen): None.
Type 8(COMM queue flag): g_cCommQueueFlag=(0x0).
Type 1E(RUU command read/write flag): g_cRUUCommandRWFlag=(0x0).
USB>? info
Usage:
info [Type [Value]]
Type(hex) 0: Get platform name(16 bytes) and [value](hex) is ignore.
Type(hex) 1: Get bootloader version(16 bytes) and [value](hex) is ignore.
Type(hex) 2: Get device CID(8 bytes CID with 8 bytes dummy data(0x20)) and [value](hex) is ignore.
USB>info 4
HTCS L?3?HTCE
USB>info 5
USB>info 0
BEETLES
USB>info 1
0.21
USB>info 2
USB>info 8
USB>? rtask
Usage:
rtask [Type [Value]]
Type(hex) 0: Reset radio and [value](hex) is ignore.
Type(hex) 1: Turn on radio, lease use type 3 and 4 instead.
Type(hex) 2: Turn off radio and [value](hex) is ignore.
Type(hex) 3: Run radio image and [value](hex) is ignore.
Type(hex) 4: Run radio bootloader and [value](hex) is ignore.
Type(hex) 7: Radio AT Command Debug.
Type(hex) 8: GSM trace route.
Type(hex) 9: Run radio external bootloader and [value](hex) is ignore.
Type(hex) A: Radio image flash by external bootloader and [value](hex) is ignore.
Type(hex) C: Select debug path.
Type(hex) D: Radio AT Command with GSM trace route.
Type(hex) 10: Set radio external boot UART mode(fast(1)/normal(0)).
USB>? task
Usage:
task [Type [Value [Value1]]]
Type,Value and Value1 are both DWORD(hex).
Value and Value1 are ignore in some case.
Type(hex) 0: Do hardware clear boot with delay time and [value](hex) is a delay time(unit is ms).
Type(hex) 7: Do flash ROM lock/unlock and [value]: 1(lock) and 0(unlock).
Type(hex) 8: Software reset with delay time and [value](hex) is a delay time(unit is ms).
Type(hex) 3C: Set terminal COM port baud rate.
Type(hex) 46: Force BT enter test mode.
USB>? lnbs
Usage:
lnbs nb-file [StartAddr [Length [SkipOffset ["cp"]]]]
Download nb file to ROM.
StartAddr : Start address for downloading(default=80000000).
Length : Length for downloading(default=FFFFFFFF).
SkipOffset : SkipOffset for downloading(default=00040000).
cp : Compare image with file data only.
USB>? d2s
Usage:
d2s [StartAddr [Len [Type [Append[SkipStartAddr SkipLen]]]]]
Backup memory to storage.
StartAddr : Start address for backup(0xA0040000).
Len : Length of memory will be backup. And if not given value, it will be
Total ROM size on board - ((StartAddress & 0x0FFFFFFF) - (ROM base address(0) & 0x0FFFFFFF)).
Type : Which storage(cf/sd) type will be selected(cf).
Append : Backup methods(a/).
SkipStartAddr : Start address of skip area(0x0).
SkipLen : Skip length(0x0).
Skip area must be less than or equal to one block size of flash.
Skip area must not over two blocks, must inside one block.
Nand flash: Skip area size need be page boundary.
Nor flash: Skip area size need be DWORD boundary.
DOC flash: Skip area size need equal to MBLOCKLEN(32kB).
USB>? s2d
Usage:
s2d
Restore memory from storage.
USB>? lw
The same as "l" command, but download to radio flash memory.
Usage:
lw [path_name [startAddr offset ["cp"]]]
Download BIN file across from serial/USB port.
Startaddr offset(MSB bit is a sign bit): Start address offset of every packet in bin file.
When 'cp' is given, it will just compare data of file with ROM image.
When path_name is not given, the file to be downloaded is determined
by ppfs on the host.
Otherwise, path_name on the host is downloaded regardless the ppfs setting.
The file must be in the format of BIN (preprocessed SRE).
USB>? password
Usage:
password [string]
Enter the password string to enable full help and command functions.
Enter the password string1 to enable some command functions related to RUU.
USB>rtask 8
GSM Trace Route.
Wait 2413 ms
USB>rtask 1
Please use type 3 and 4 instead.
USB>? task 32
Syntax error!
Usage:
? [command] [full]
Helps on command.
When no command is given, output a list of normal commands.
If "full" option used, display all commands(need password enable).
But if one command is given, It will show the command usage method.
USB>? erase
Usage:
erase [StartAddr [Len]]
Erase the contain of flash ROM.
StartAddr : Start address of ROM(default(hex)=A0040000).
Len : How many bytes will be erased(default(hex)=40000).
USB>rtask a
Radio image flash by external bootloader.
HTCS??6ú??HTCE
The IPAQ froze and I had to reboot the IPAQ before I could reconnect.
USB>password 0000000000000000
HTCSPass1.CM??HTCEUSB>? rtask
Usage:
rtask [Type [Value]]
Type(hex) 0: Reset radio and [value](hex) is ignore.
Type(hex) 1: Turn on radio, lease use type 3 and 4 instead.
Type(hex) 2: Turn off radio and [value](hex) is ignore.
Type(hex) 3: Run radio image and [value](hex) is ignore.
Type(hex) 4: Run radio bootloader and [value](hex) is ignore.
Type(hex) 7: Radio AT Command Debug.
Type(hex) 8: GSM trace route.
Type(hex) 9: Run radio external bootloader and [value](hex) is ignore.
Type(hex) A: Radio image flash by external bootloader and [value](hex) is ignore.
Type(hex) C: Select debug path.
Type(hex) D: Radio AT Command with GSM trace route.
Type(hex) 10: Set radio external boot UART mode(fast(1)/normal(0)).
USB>rtask a
Radio image flash by external bootloader.
2.12.00484830000EF23CB887AC20E08199E335&HTCE
Links
• HOWTO: Change serial number and model number for HP IPAQ 6515
• HP IPAQ 6515 Bootloader password
• HP IPAQ 6510 / 6515 dead GSM after failed Firmware upgrade
http://blogs.unbolt.net/index.php/brinley/2007/07/09/howto_change_serial_number_and_model_num_6515
http://blogs.unbolt.net/index.php/brinley/2007/08/12/hp_ipaq_6515_bootloader_password
http://blogs.unbolt.net/index.php/brinley/2007/07/31/ipaq_6515_dead_gsm_after_failed_firmware
Continuation ...................................
caoxt,
What are you trying to explain?
We do not understand..'wo men bu ming pai'
Can you just post information that really works and not all those informations that do not work.
Thanks..
http://forum.xda-developers.com/showthread.php?t=326439
caoxt
Here:http://forum.xda-developers.com/showthread.php?t=337975&page=10#91
http://forum.xda-developers.com/showthread.php?t=337975&page=10#99
Member Join Date: Apr 2004
Posts: 39
--------------------------------------------------------------------------------
Quote:
Originally Posted by matrix21
Anyone here could come up with a solution for the NO GSM error?
Pls help..
I also am NO GSM!
:
matrix21 said:
caoxt,
What are you trying to explain?
We do not understand..'wo men bu ming pai'
Can you just post information that really works and not all those informations that do not work.
Thanks..
Click to expand...
Click to collapse
NO GSM
Hallo Caoxt
Ich habe auch vor 2 Tagen
Sable_RUU.exe von diesem Forum geladet und mein hp6915 von uk2.1 aug germ geändert.
Jetzt funktioniert mein Telefon nicht mehr(NO GSM)
Ich kann nicht wissen was ich machen soll!
Für diese Forum habe ich nicht genügend englisch.
Danke für eine lösung
Gruss cinar
Hello the friend
I write with difficulty in English, I make my possible, thank you
You would have the French ROM for Ipaq HW 6915
I have just downloaded the English Rom on Rapidshare, thank you
Thank you for devotion
JO [email protected]
matrix21 said:
wo men bu ming pai
Click to expand...
Click to collapse
its means we don't understand in chinese.
hope it helps.
cinar22 said:
Hallo Caoxt
Ich habe auch vor 2 Tagen
Sable_RUU.exe von diesem Forum geladet und mein hp6915 von uk2.1 aug germ geändert.
Jetzt funktioniert mein Telefon nicht mehr(NO GSM)
Ich kann nicht wissen was ich machen soll!
Für diese Forum habe ich nicht genügend englisch.
Danke für eine lösung
Gruss cinar
Click to expand...
Click to collapse
du kannst google translate versuchen, wirkt wunder !
FOR EVERYBODY ELSE :
if there are complicated solutions to change the device languges on this forum, but you just think you know better -> there u got yourself with a NO GSM device wich u cant almost throw away
THE THING IS : microsoft hast problems with licensing towords hp, in conclusion the protection is pretty good to not change languages on hp ipaq device 6915
so, this way, please search the forum and USE the instructions to change the language instead of this homemade solutions, else you all will get a NO GSM device, and then don't come here complaining and searching for a solution.
good luck !
bump bump bump
NO GSM FIX FOR SOME hw6500 / hw6900 Series
NO GSM FIX FOR SOME hw6500 / hw6900 Series
http://forum.xda-developers.com/showthread.php?t=377495&page=6
POST #56
no GSM for hw6915
Hello coaxt,
i have used the procedure from this forum to upgrade the Radio.nba for my hw6915... I belive this procedure is wrong as soon the upload procedure stuck with error 201. The device remain in the bricked mode. After upgrading the OS only then the device is able to boot again, of course with no GSM problem.
Any advise in how to recover the GSM on the device it will be usefull.
Thanx.
---------------------------------------------------------------------------
Smile modified/pached hpRUU.exe for ipaq hw6915.
modified/pached hpRUU.exe?
--------------------------------------------------------------------------------
i would like to know if somebody here already have patched or modified the original hpRUU.exe for the ipaq hw69xx series in order to allow uploading a different ROM-image(e.g different language etc.) to the device.
as far as i know it would be enough to disable the pre-check and jump directly to the start of the flashing routine itself.
i tried In each method this already by myself, but it seems it isn't as easy as i thought.
any help is appreciated...
In the appendix has HP iPAQ hw6900 Mobile Messenger Series ROM Update
BIOS from that link:
http://h20000.www2.hp.com/bizsupport..._I23843-109104
1.download GSM BIOS from that link:
http://h20000.www2.hp.com/bizsupport...&swEnvOID=2067
2.download all ROM BIOS from that link:
http://h20000.www2.hp.com/bizsupport..._I23843-109104
best regards,
Caoxt
Hello,
I try to build my own CM9 ROM for the Motorola Defy.
I get the Defy device files with the following command:
Code:
. build/envsetup.sh && breakfast jordan
After this i would build the ROM by execute
Code:
. build/envsetup.sh && brunch jordan
At first the building process ends up with this error:
Code:
build/core/base_rules.mk:166: *** vendor/cm/audio: MODULE.TARGET.SHARED_LIBRARIES.audio_policy.jordan already defined by device/motorola/jordan/audio_policy.
So I delte the audio directory in vendor/cm
But now I get a new error:
Code:
make: *** Keine Regel vorhanden, um das Target »system/core/toolbox/../../../external/bootmenu/libreboot/reboot.c«,
benötigt von »out/target/product/jordan/obj/EXECUTABLES/toolbox_intermediates/../../../external/bootmenu/libreboot/reboot.o«, zu erstellen. Schluss.
make: *** Warte auf noch nicht beendete Prozesse...
system/core/toolbox/r.c: In function 'r_main':
system/core/toolbox/r.c:87: warning: 'value' may be used uninitialized in this function
Is this a known error?
Can anyone help me?
regards,
Nico-X
Hi..
I have a decompile Problem, only with SecSetting.apk (it is Stock ME2)
framework is installed as 1.apk in data/apktool
click to see log file...
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) Client VM (build 23.21-b01, mixed mode, sharing)
C:\android-sdk\Apk_Manager_jb\place-apk-here-for-modding\../place-apk-here-for-modding/signedSecSettings.apk konnte nicht gefunden werden
C:\android-sdk\Apk_Manager_jb\place-apk-here-for-modding\../place-apk-here-for-modding/unsignedSecSettings.apk konnte nicht gefunden werden
I: Baksmaling...
I: Loading resource table...
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at java.util.regex.Pattern.compile(Pattern.java:1655)
at java.util.regex.Pattern.<init>(Pattern.java:1337)
at java.util.regex.Pattern.compile(Pattern.java:1047)
at java.lang.String.replace(String.java:2180)
at brut.androlib.res.xml.ResXmlEncoders.escapeXmlChars(ResXmlEncoders.java:29)
at brut.androlib.res.decoder.StringBlock.getHTML(StringBlock.java:133)
at brut.androlib.res.decoder.ARSCDecoder.readValue(ARSCDecoder.java:227)
at brut.androlib.res.decoder.ARSCDecoder.readEntry(ARSCDecoder.java:182)
at brut.androlib.res.decoder.ARSCDecoder.readConfig(ARSCDecoder.java:170)
at brut.androlib.res.decoder.ARSCDecoder.readType(ARSCDecoder.java:135)
at brut.androlib.res.decoder.ARSCDecoder.readPackage(ARSCDecoder.java:110)
at brut.androlib.res.decoder.ARSCDecoder.readTable(ARSCDecoder.java:83)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:49)
at brut.androlib.res.AndrolibResources.getResPackagesFromApk(AndrolibResources.java:491)
at brut.androlib.res.AndrolibResources.loadMainPkg(AndrolibResources.java:74)
at brut.androlib.res.AndrolibResources.getResTable(AndrolibResources.java:66)
any idee??
Thx for reply
I received my LeEco Le Pro3 Elite (X722) this Thursday. It came with a ROM shop. I tested it, but I wanted to switch to Stock.
First I boot the TWRP of the X720 version without installing it through the "fastboot boot " command. I installed SuperSu and rebooted to the system. So I used the Shell through ADB to take a nandroid copy of the original recovery, boot, system and firmwares for security.
So far so good. So I installed TWRP replacing the original recovery.
I entered recovery mode and installed the stock ROM zl0 v026s. Everything went well. Then I installed the GApps. When in the middle of the process the smartphone suddenly turns off and tries to start the system.
The smartphone was stuck on the home screen. I tried to enter recovery mode and immediately it turns off the screen.
And worst: the bootloader that was unlocked is now locked and does not allow unlocking!
I do not know what to do! Without the recovery I can not recover the bootloader and without the bootloader I can not recover the recovery!
As far as I know the only way now is to use Qfil to flash the required files. But I did not find the necessary files.
I am still having all the backup needed to make it work, but I do not know how to flash it. Anyone have any idea how to solve this!
Please! Help me!
Up!
Excuse my English
Try downloading this and running as it is in the image.
They are recovery files if you do tell us how it was-----fastboot mode
乐 视 Pro3 乐 视 X720 X722 X728 通用 版 机 教程 完美 完美 救 救 刷 刷 机
http://2.shuajibbs.com:8083/LE1/乐视Pro3-乐视X720 X722 X728.zip
http://imgur.com/LtSHbL7
I have the same problem with X720! I flash stock rom fastboot with flashtool one2.
shinji_x19 said:
Excuse my English
Try downloading this and running as it is in the image.
They are recovery files if you do tell us how it was-----fastboot mode
乐 视 Pro3 乐 视 X720 X722 X728 通用 版 机 教程 完美 完美 救 救 刷 刷 机
http://2.shuajibbs.com:8083/LE1/乐视Pro3-乐视X720 X722 X728.zip
http://imgur.com/LtSHbL7
Click to expand...
Click to collapse
The bootloader is locked. I have already tried it.
Thank you
bahuy2003 said:
I have the same problem with X720! I flash stock rom fastboot with flashtool one2.
Click to expand...
Click to collapse
I have already tried this too. It always gives this error:
15:47:28: ERROR: function: rx_data:247 Error occurred while reading from COM port
15:47:28: ERROR: function: sahara_main:924 Sahara protocol error
15:47:28: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Click to expand...
Click to collapse
You rename rom to 1.zip before flashing.
DK Boneco said:
I received my LeEco Le Pro3 Elite (X722) this Thursday. It came with a ROM shop. I tested it, but I wanted to switch to Stock.
First I boot the TWRP of the X720 version without installing it through the "fastboot boot " command. I installed SuperSu and rebooted to the system. So I used the Shell through ADB to take a nandroid copy of the original recovery, boot, system and firmwares for security.
So far so good. So I installed TWRP replacing the original recovery.
I entered recovery mode and installed the stock ROM zl0 v026s. Everything went well. Then I installed the GApps. When in the middle of the process the smartphone suddenly turns off and tries to start the system.
The smartphone was stuck on the home screen. I tried to enter recovery mode and immediately it turns off the screen.
And worst: the bootloader that was unlocked is now locked and does not allow unlocking!
I do not know what to do! Without the recovery I can not recover the bootloader and without the bootloader I can not recover the recovery!
As far as I know the only way now is to use Qfil to flash the required files. But I did not find the necessary files.
I am still having all the backup needed to make it work, but I do not know how to flash it. Anyone have any idea how to solve this!
Please! Help me![/QUOTE]
Can you access the backup files on the PC or other device? Pack all files (except personal ones, such as photos, contacts, videos ...) into a zip file and copy it into the "8675_W00" folder without any other .zip files on it and run the Qfil.
I, although I am in the same situation, I can not prove this because I do not have any type of backup.
Click to expand...
Click to collapse
Unbrick lex722
Hello i search fireheose 8996 for lex722 elite. Unfortunately i can't find suitable firehose.
How is it built up? Is it signed?
Best regards
ologoo
Can you share the backup of stock recovery x722? Thanks
Wait, did it come bootloader unlocked or did you unlock it? How? And how on earth did the bootloader relock itself in TWRP. I've never heard of that happening....
Edit: does 26s force a locked bootloader?
sk8223 said:
Wait, did it come bootloader unlocked or did you unlock it? How? And how on earth did the bootloader relock itself in TWRP. I've never heard of that happening....
Edit: does 26s force a locked bootloader?
Click to expand...
Click to collapse
I'm in the same situation.x722 dead.
did you solve it?
Leeco Elite mit 26s
Wer sein LEeco Elite x722 mit TWRP den Bootloader 26s „Firmware WIXCNFN5902005041S EUI 5.9.020S“ installiert hat,
wird mit Sicherheit es nicht mehr starten können. Das habe ich aus mehreren Foren gelesen.
Es gibt viele die ihr lex722 nicht mehr nutzen können. Ich war einfach zu naiv zu glauben das ein sich als Pro 3 Elite bezeichneten Telefon auch so einfach mit einer neueren Firmware flashen lässt wie mit einem Pro 3. Zu schnell ausgepackt nicht gründlich alle Foren gelesen und schon ist es passiert.
Leider gibt es keine Möglichkeit das Telefon wieder zu beleben. Jedenfalls im Moment nicht.
Das liegt zum einem daran wenn:
1. Der Fastboot noch möglich ist zu starten aber kein Recovery, TWRP mehr vorhanden ist und der Bootloader nicht zu entsperren ist.
2. Das Sahara Protokoll nicht funktioniert. Egal ob mit kompilierten Qsahara oder oh-my-tools unter Linux. Oder Qfil mit Windows.
3. Es gibt noch keine passende prog_emmc_firehose_8996_ddr.elf
Ich weiß das ich bei den Huaweimodellen mit fastboot oem unlock „XXXXXXXXXXXXXXXXXXXX"
den gesperrten Bootloader aufmachen kann.
Ich habe 2 Wochen nahezu alle Themen über das Wiederbeleben des leeco x722 gelesen und mich damit beschäftigt. Aber 90 % sind nur bloße Raterei. Egal in welchem Forum für lex722 unbrick man landet. Es sind immer die gleichen Links die zu den chinesischen Seiten führen. Dann verliert sich das eigentliche Thema.
Daher schlage ich vor hier ab nur bei diesem Gerät zu bleiben und sich mit dem Unbrick zu beschäftigen.
Hier bei xda-developers.com gibt es gute Ansätze über die Funktionsweise des Sahara und Firehose Protokoll.
Was ich bis jetzt in anderen Foren gelesen habe über unbrick x722 FUNKTIONIERT nicht. Die tollen „Links“ derjenigen die sich danach auf die Schulter klopfen, und da bin ich mir sicher, haben niemals ein leeco722 wiederbelebt. Jedenfalls nicht wenn es richtig gebrickt ist.
Also ohne Bootloader SBL oder Recovery.
Scheinbar sind die Könner die sich wirklich auskennen sehr selten geworden.
Die Firmware WIXCNFN5902005041S EUI 5.9.020S ist 26s Bootloader. Dieser Bootloader ist gesperrt. EU version 026s ist EUI 5.9. Diese habe ich über TWRP installiert.
Jetzt startet es nicht mehr.
Original war da WIXCNF5802001232S drauf.
Danach ein WIXCNFN5800106140D
D = Developer Version
S = Stock Rom
Dann bin ich wieder zurück auf WIXCNF5802001232S.
Von dieser habe ich fast alle Partitionen als Image gespeichert und zurück gespielt.
Dann das Desaster mit WIXCNFN5902005041S.
Ich habe aus den anderen Foren diese Firmware x722-5-8.020S-60 by Batyan geladen.
Diese und alle anderen Firmwaren sind wohlmöglich alle die WIXCNFN5800106140S. Das Update darin ist die Developer Version.
Die QPST und FlashOne 1.9 oder 2 Miflash machen es nicht wie auch es gibt keine Qfil für lex722.
Die Vorschläge Lexma2Qfill, 910-Le max2 oder LeMax2_820_qfil zu verwenden sind ausgedacht. Sie haben ein anderes Partitionsschema und Firmware.
Zuerst muss mal geklärt werden ob die obrigen Methoden überhaupt funktionieren.
Die Firehosemethode, geht die überhaupt mit dem Telefon?
Wenn ja was macht sie im Detail genau, wo kommt sie her und warum gibt es denn keine für lex722? Ist da ein Sicherheitszertifikat enthalten?
Secureboot wenn ja welche Version läuft bei lex722.
Ich habe spannende versprechende fastboot.bat gefunden. Aber ist immer wieder das gleiche fastboot oem unlock.
Dieser unlock Befehl funktioniert nicht mit 26s Bootloader !!!!!!!!!!!!!!
Jeder Hersteller hat weitere geheime Fastbootbefehle, bestimmt auch für den 26s Bootloader.
Oder geht nur das Öffnen des Telefons und dann mit Testpoint oder JTAG ran?
Wichtig wäre doch eine Methode die auch geht. Kein herum raten mach mal dies oder das.
Ich lege mein Telefon zu Seite und warte mal ab. Evntl. Erbarmt sich mal ein Leeco Profi und klärt auf. Die Hoffnung stirbt zuletzt.
Mit freundlichen Grüßen
Ologoo
Hier einige Infos zum Anfang vom Leeco leTV 722 Pro3.
Please use the online Translator, i write in german language. Has to be too
---------- Post added at 04:47 PM ---------- Previous post was at 04:18 PM ----------
[email protected]_zl0:/ $ cat /proc/partitions
major minor #blocks name
8 16 4096 sdb
8 17 4052 sdb1
8 48 131072 sdd
8 49 32 sdd1
8 50 4 sdd2
8 51 1024 sdd3
8 0 25833472 sda
8 1 8 sda1
8 2 32768 sda2
8 3 262144 sda3
8 4 1024 sda4
8 5 512 sda5
8 6 128 sda6
8 7 128 sda7
8 8 512 sda8
8 9 4096 sda9
8 10 25532108 sda10
8 32 4096 sdc
8 33 4052 sdc1
8 64 5242880 sde
8 65 512 sde1
8 66 512 sde2
8 67 2048 sde3
8 68 2048 sde4
8 69 512 sde5
8 70 512 sde6
8 71 2048 sde7
8 72 1024 sde8
8 73 16 sde9
8 74 512 sde10
8 75 512 sde11
8 76 112640 sde12
8 77 16384 sde13
8 78 1024 sde14
8 79 32768 sde15
259 0 1024 sde16
259 1 1024 sde17
259 2 65536 sde18
259 3 4194304 sde19
259 4 65536 sde20
259 5 4 sde21
259 6 1024 sde22
259 7 512 sde23
259 8 512 sde24
259 9 256 sde25
259 10 256 sde26
259 11 256 sde27
259 12 256 sde28
259 13 256 sde29
259 14 256 sde30
259 15 4 sde31
259 16 102400 sde32
259 17 2048 sde33
8 80 32768 sdf
8 81 2048 sdf1
8 82 1024 sdf2
8 83 2048 sdf3
8 84 1024 sdf4
8 85 4 sdf5
8 86 4 sdf6
8 87 4 sdf7
8 88 4 sdf8
8 89 4 sdf9
8 90 512 sdf10
8 91 512 sdf11
8 92 512 sdf12
8 93 512 sdf13
8 94 10240 sdf14
[email protected]_zl0:/ $
[email protected]_zl0:/ $ cat /proc/cpuinfo
Processor : AArch64 Processor rev 2 (aarch64)
processor : 0
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x51
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x211
CPU revision : 2
processor : 1
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x51
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x211
CPU revision : 2
processor : 2
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x51
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x205
CPU revision : 2
processor : 3
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x51
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x205
CPU revision : 2
Hardware : Qualcomm Technologies, Inc MSM8996
ls -al /dev/block/platform/soc/by-name/
drwxr-xr-x 2 root root 1280 Jul 16 00:13 .
drwxr-xr-x 4 root root 1460 Jul 16 00:13 ..
lrwxrwxrwx 1 root root 16 Jul 16 00:13 aboot -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 Jul 16 00:13 abootbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 Jul 16 00:13 apdp -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 Jul 16 00:13 bluetooth -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 Jul 16 00:13 boot -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 Jul 16 00:13 bootconfig -> /dev/block/sdf7
lrwxrwxrwx 1 root root 15 Jul 16 00:13 cache -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 Jul 16 00:13 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 Jul 16 00:13 cmnlib -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 Jul 16 00:13 cmnlib64 -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 Jul 16 00:13 cmnlib64bak -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 Jul 16 00:13 cmnlibbak -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 Jul 16 00:13 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 Jul 16 00:13 devcfg -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 Jul 16 00:13 devcfgbak -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Jul 16 00:13 devinfo -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 Jul 16 00:13 dip -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 Jul 16 00:13 dpo -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 Jul 16 00:13 dsp -> /dev/block/sde13
lrwxrwxrwx 1 root root 15 Jul 16 00:13 factory -> /dev/block/sdf6
lrwxrwxrwx 1 root root 15 Jul 16 00:13 frp -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Jul 16 00:13 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 Jul 16 00:13 fsg -> /dev/block/sde7
lrwxrwxrwx 1 root root 15 Jul 16 00:13 fsg_gap -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 Jul 16 00:13 hyp -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 Jul 16 00:13 hypbak -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 Jul 16 00:13 kernellog -> /dev/block/sdf14
lrwxrwxrwx 1 root root 16 Jul 16 00:13 keymaster -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 Jul 16 00:13 keymasterbak -> /dev/block/sde24
lrwxrwxrwx 1 root root 15 Jul 16 00:13 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Jul 16 00:13 letvconfig -> /dev/block/sdf10
lrwxrwxrwx 1 root root 16 Jul 16 00:13 letveui -> /dev/block/sdf11
lrwxrwxrwx 1 root root 16 Jul 16 00:13 letvreserve -> /dev/block/sdf13
lrwxrwxrwx 1 root root 16 Jul 16 00:13 letvsecure -> /dev/block/sdf12
lrwxrwxrwx 1 root root 16 Jul 16 00:13 mdtp -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 Jul 16 00:13 misc -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Jul 16 00:13 modem -> /dev/block/sde12
lrwxrwxrwx 1 root root 15 Jul 16 00:13 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 Jul 16 00:13 modemst1_gap -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 Jul 16 00:13 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 Jul 16 00:13 modemst2_gap -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 Jul 16 00:13 msadp -> /dev/block/sde30
lrwxrwxrwx 1 root root 15 Jul 16 00:13 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 Jul 16 00:13 pmic -> /dev/block/sde10 →
lrwxrwxrwx 1 root root 16 Jul 16 00:13 pmicbak -> /dev/block/sde11
lrwxrwxrwx 1 root root 15 Jul 16 00:13 ramdump -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 Jul 16 00:13 recovery -> /dev/block/sde20
lrwxrwxrwx 1 root root 15 Jul 16 00:13 recoveryconfig -> /dev/block/sdf9
lrwxrwxrwx 1 root root 15 Jul 16 00:13 reserve -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 Jul 16 00:13 rootconfig -> /dev/block/sdf8
lrwxrwxrwx 1 root root 15 Jul 16 00:13 rpm -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 Jul 16 00:13 rpmbak -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 Jul 16 00:13 sec -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 Jul 16 00:13 splash -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 Jul 16 00:13 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 Jul 16 00:13 sti -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 Jul 16 00:13 system -> /dev/block/sde19
lrwxrwxrwx 1 root root 15 Jul 16 00:13 tz -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 Jul 16 00:13 tzbak -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 Jul 16 00:13 userdata -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 Jul 16 00:13 xbl -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 Jul 16 00:13 xblbak -> /dev/block/sdc1
# fdisk -l /dev/block/sda
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sda: 51666944 sectors, 1120M
Logical sector size: 4096
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 12 entries
First usable sector is 6, last usable sector is 6458362
Number Start (sector) End (sector) Size Code Name
1 6 7 8192 0700 ssd
2 8 8199 32.0M 0700 persist
3 8200 73735 256M 0700 cache
4 73736 73991 1024K 0700 misc
5 73992 74119 512K 0700 keystore
6 74120 74151 128K 0700 devcfg
7 74152 74183 128K 0700 devcfgbak
8 74184 74311 512K 0700 frp
9 74312 75335 4096K 0700 ramdump
10 75336 6458362 24.3G 0700 userdata
~ # fdisk -l /dev/block/sdb
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdb: 8192 sectors, 32.0M
Logical sector size: 4096
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 4 entries
First usable sector is 6, last usable sector is 1018
Number Start (sector) End (sector) Size Code Name
1 6 1018 4052K 0700 xbl
~ # fdisk -l /dev/block/sdc
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdc: 8192 sectors, 32.0M
Logical sector size: 4096
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 4 entries
First usable sector is 6, last usable sector is 1018
Number Start (sector) End (sector) Size Code Name
1 6 1018 4052K 0700 xblbak
~ # fdisk -l /dev/block/sde
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sde: 10485760 sectors, 0
Logical sector size: 4096
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 36 entries
First usable sector is 6, last usable sector is 1310714
Number Start (sector) End (sector) Size Code Name
1 6 133 512K 0700 rpm
2 134 261 512K 0700 rpmbak
3 262 773 2048K 0700 tz
4 774 1285 2048K 0700 tzbak
5 1286 1413 512K 0700 hyp
6 1414 1541 512K 0700 hypbak
7 1542 2053 2048K 0700 fsg
8 2054 2309 1024K 0700 fsg_gap
9 2310 2313 16384 0700 sec
10 2314 2441 512K 0700 pmic
11 2442 2569 512K 0700 pmicbak
12 2570 30729 110M 0700 modem
13 30730 34825 16.0M 0700 dsp
14 34826 35081 1024K 0700 dip
15 35082 43273 32.0M 0700 mdtp
16 43274 43529 1024K 0700 aboot
17 43530 43785 1024K 0700 abootbak
18 43786 60169 64.0M 0700 boot
19 60170 1108745 4096M 0700 system
20 1108746 1125129 64.0M 0700 recovery
21 1125130 1125130 4096 0700 devinfo
22 1125131 1125386 1024K 0700 bluetooth
23 1125387 1125514 512K 0700 keymaster
24 1125515 1125642 512K 0700 keymasterbak
25 1125643 1125706 256K 0700 cmnlib
26 1125707 1125770 256K 0700 cmnlibbak
27 1125771 1125834 256K 0700 cmnlib64
28 1125835 1125898 256K 0700 cmnlib64bak
29 1125899 1125962 256K 0700 apdp
30 1125963 1126026 256K 0700 msadp
31 1126027 1126027 4096 0700 dpo
32 1126028 1151627 100M 0700 splash
33 1151628 1152139 2048K 0700 sti
34 1152140 1310714 619M 0700 last_parti
~ #
~ # fdisk -l /dev/block/sdf
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdf: 65536 sectors, 256M
Logical sector size: 4096
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 16 entries
First usable sector is 6, last usable sector is 8186
Number Start (sector) End (sector) Size Code Name
1 6 517 2048K 0700 modemst1
2 518 773 1024K 0700 modemst1_gap
3 774 1285 2048K 0700 modemst2
4 1286 1541 1024K 0700 modemst2_gap
5 1542 1542 4096 0700 fsc
6 1543 1543 4096 0700 factory
7 1544 1544 4096 0700 bootconfig
8 1545 1545 4096 0700 rootconfig
9 1546 1546 4096 0700 recoveryconfig
10 1547 1674 512K 0700 letvconfig
11 1675 1802 512K 0700 letveui
12 1803 1930 512K 0700 letvsecure
13 1931 2058 512K 0700 letvreserve
14 2059 4618 10.0M 0700 kernellog
15 4619 8186 13.9M 0700 last_parti
~ #
And no solution?
And if you copy the original ROM by ADB push "rom" /sdcard/
then install from TWRP?
ologoo said:
Leeco Elite mit 26s
Wer sein LEeco Elite x722 mit TWRP den Bootloader 26s „Firmware WIXCNFN5902005041S EUI 5.9.020S“ installiert hat,
wird mit Sicherheit es nicht mehr starten können. Das habe ich aus mehreren Foren gelesen.
Es gibt viele die ihr lex722 nicht mehr nutzen können. Ich war einfach zu naiv zu glauben das ein sich als Pro 3 Elite bezeichneten Telefon auch so einfach mit einer neueren Firmware flashen lässt wie mit einem Pro 3. Zu schnell ausgepackt nicht gründlich alle Foren gelesen und schon ist es passiert.
Leider gibt es keine Möglichkeit das Telefon wieder zu beleben. Jedenfalls im Moment nicht.
Das liegt zum einem daran wenn:
1. Der Fastboot noch möglich ist zu starten aber kein Recovery, TWRP mehr vorhanden ist und der Bootloader nicht zu entsperren ist.
2. Das Sahara Protokoll nicht funktioniert. Egal ob mit kompilierten Qsahara oder oh-my-tools unter Linux. Oder Qfil mit Windows.
3. Es gibt noch keine passende prog_emmc_firehose_8996_ddr.elf
Ich weiß das ich bei den Huaweimodellen mit fastboot oem unlock „XXXXXXXXXXXXXXXXXXXX"
den gesperrten Bootloader aufmachen kann.
Ich habe 2 Wochen nahezu alle Themen über das Wiederbeleben des leeco x722 gelesen und mich damit beschäftigt. Aber 90 % sind nur bloße Raterei. Egal in welchem Forum für lex722 unbrick man landet. Es sind immer die gleichen Links die zu den chinesischen Seiten führen. Dann verliert sich das eigentliche Thema.
Daher schlage ich vor hier ab nur bei diesem Gerät zu bleiben und sich mit dem Unbrick zu beschäftigen.
Hier bei xda-developers.com gibt es gute Ansätze über die Funktionsweise des Sahara und Firehose Protokoll.
Was ich bis jetzt in anderen Foren gelesen habe über unbrick x722 FUNKTIONIERT nicht. Die tollen „Links“ derjenigen die sich danach auf die Schulter klopfen, und da bin ich mir sicher, haben niemals ein leeco722 wiederbelebt. Jedenfalls nicht wenn es richtig gebrickt ist.
Also ohne Bootloader SBL oder Recovery.
Scheinbar sind die Könner die sich wirklich auskennen sehr selten geworden.
Die Firmware WIXCNFN5902005041S EUI 5.9.020S ist 26s Bootloader. Dieser Bootloader ist gesperrt. EU version 026s ist EUI 5.9. Diese habe ich über TWRP installiert.
Jetzt startet es nicht mehr.
Original war da WIXCNF5802001232S drauf.
Danach ein WIXCNFN5800106140D
D = Developer Version
S = Stock Rom
Dann bin ich wieder zurück auf WIXCNF5802001232S.
Von dieser habe ich fast alle Partitionen als Image gespeichert und zurück gespielt.
Dann das Desaster mit WIXCNFN5902005041S.
Ich habe aus den anderen Foren diese Firmware x722-5-8.020S-60 by Batyan geladen.
Diese und alle anderen Firmwaren sind wohlmöglich alle die WIXCNFN5800106140S. Das Update darin ist die Developer Version.
Die QPST und FlashOne 1.9 oder 2 Miflash machen es nicht wie auch es gibt keine Qfil für lex722.
Die Vorschläge Lexma2Qfill, 910-Le max2 oder LeMax2_820_qfil zu verwenden sind ausgedacht. Sie haben ein anderes Partitionsschema und Firmware.
Zuerst muss mal geklärt werden ob die obrigen Methoden überhaupt funktionieren.
Die Firehosemethode, geht die überhaupt mit dem Telefon?
Wenn ja was macht sie im Detail genau, wo kommt sie her und warum gibt es denn keine für lex722? Ist da ein Sicherheitszertifikat enthalten?
Secureboot wenn ja welche Version läuft bei lex722.
Ich habe spannende versprechende fastboot.bat gefunden. Aber ist immer wieder das gleiche fastboot oem unlock.
Dieser unlock Befehl funktioniert nicht mit 26s Bootloader !!!!!!!!!!!!!!
Jeder Hersteller hat weitere geheime Fastbootbefehle, bestimmt auch für den 26s Bootloader.
Oder geht nur das Öffnen des Telefons und dann mit Testpoint oder JTAG ran?
Wichtig wäre doch eine Methode die auch geht. Kein herum raten mach mal dies oder das.
Ich lege mein Telefon zu Seite und warte mal ab. Evntl. Erbarmt sich mal ein Leeco Profi und klärt auf. Die Hoffnung stirbt zuletzt.
Mit freundlichen Grüßen
Ologoo
Hier einige Infos zum Anfang vom Leeco leTV 722 Pro3.
Please use the online Translator, i write in german language. Has to be too
---------- Post added at 04:47 PM ---------- Previous post was at 04:18 PM ----------
[email protected]_zl0:/ $ cat /proc/partitions
major minor #blocks name
8 16 4096 sdb
8 17 4052 sdb1
8 48 131072 sdd
8 49 32 sdd1
8 50 4 sdd2
8 51 1024 sdd3
8 0 25833472 sda
8 1 8 sda1
8 2 32768 sda2
8 3 262144 sda3
8 4 1024 sda4
8 5 512 sda5
8 6 128 sda6
8 7 128 sda7
8 8 512 sda8
8 9 4096 sda9
8 10 25532108 sda10
8 32 4096 sdc
8 33 4052 sdc1
8 64 5242880 sde
8 65 512 sde1
8 66 512 sde2
8 67 2048 sde3
8 68 2048 sde4
8 69 512 sde5
8 70 512 sde6
8 71 2048 sde7
8 72 1024 sde8
8 73 16 sde9
8 74 512 sde10
8 75 512 sde11
8 76 112640 sde12
8 77 16384 sde13
8 78 1024 sde14
8 79 32768 sde15
259 0 1024 sde16
259 1 1024 sde17
259 2 65536 sde18
259 3 4194304 sde19
259 4 65536 sde20
259 5 4 sde21
259 6 1024 sde22
259 7 512 sde23
259 8 512 sde24
259 9 256 sde25
259 10 256 sde26
259 11 256 sde27
259 12 256 sde28
259 13 256 sde29
259 14 256 sde30
259 15 4 sde31
259 16 102400 sde32
259 17 2048 sde33
8 80 32768 sdf
8 81 2048 sdf1
8 82 1024 sdf2
8 83 2048 sdf3
8 84 1024 sdf4
8 85 4 sdf5
8 86 4 sdf6
8 87 4 sdf7
8 88 4 sdf8
8 89 4 sdf9
8 90 512 sdf10
8 91 512 sdf11
8 92 512 sdf12
8 93 512 sdf13
8 94 10240 sdf14
[email protected]_zl0:/ $
[email protected]_zl0:/ $ cat /proc/cpuinfo
Processor : AArch64 Processor rev 2 (aarch64)
processor : 0
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x51
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x211
CPU revision : 2
processor : 1
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x51
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x211
CPU revision : 2
processor : 2
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x51
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x205
CPU revision : 2
processor : 3
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU implementer : 0x51
CPU architecture: 8
CPU variant : 0x1
CPU part : 0x205
CPU revision : 2
Hardware : Qualcomm Technologies, Inc MSM8996
ls -al /dev/block/platform/soc/by-name/
drwxr-xr-x 2 root root 1280 Jul 16 00:13 .
drwxr-xr-x 4 root root 1460 Jul 16 00:13 ..
lrwxrwxrwx 1 root root 16 Jul 16 00:13 aboot -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 Jul 16 00:13 abootbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 Jul 16 00:13 apdp -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 Jul 16 00:13 bluetooth -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 Jul 16 00:13 boot -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 Jul 16 00:13 bootconfig -> /dev/block/sdf7
lrwxrwxrwx 1 root root 15 Jul 16 00:13 cache -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 Jul 16 00:13 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 Jul 16 00:13 cmnlib -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 Jul 16 00:13 cmnlib64 -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 Jul 16 00:13 cmnlib64bak -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 Jul 16 00:13 cmnlibbak -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 Jul 16 00:13 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 Jul 16 00:13 devcfg -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 Jul 16 00:13 devcfgbak -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Jul 16 00:13 devinfo -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 Jul 16 00:13 dip -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 Jul 16 00:13 dpo -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 Jul 16 00:13 dsp -> /dev/block/sde13
lrwxrwxrwx 1 root root 15 Jul 16 00:13 factory -> /dev/block/sdf6
lrwxrwxrwx 1 root root 15 Jul 16 00:13 frp -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Jul 16 00:13 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 Jul 16 00:13 fsg -> /dev/block/sde7
lrwxrwxrwx 1 root root 15 Jul 16 00:13 fsg_gap -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 Jul 16 00:13 hyp -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 Jul 16 00:13 hypbak -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 Jul 16 00:13 kernellog -> /dev/block/sdf14
lrwxrwxrwx 1 root root 16 Jul 16 00:13 keymaster -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 Jul 16 00:13 keymasterbak -> /dev/block/sde24
lrwxrwxrwx 1 root root 15 Jul 16 00:13 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Jul 16 00:13 letvconfig -> /dev/block/sdf10
lrwxrwxrwx 1 root root 16 Jul 16 00:13 letveui -> /dev/block/sdf11
lrwxrwxrwx 1 root root 16 Jul 16 00:13 letvreserve -> /dev/block/sdf13
lrwxrwxrwx 1 root root 16 Jul 16 00:13 letvsecure -> /dev/block/sdf12
lrwxrwxrwx 1 root root 16 Jul 16 00:13 mdtp -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 Jul 16 00:13 misc -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Jul 16 00:13 modem -> /dev/block/sde12
lrwxrwxrwx 1 root root 15 Jul 16 00:13 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 Jul 16 00:13 modemst1_gap -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 Jul 16 00:13 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 Jul 16 00:13 modemst2_gap -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 Jul 16 00:13 msadp -> /dev/block/sde30
lrwxrwxrwx 1 root root 15 Jul 16 00:13 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 Jul 16 00:13 pmic -> /dev/block/sde10 →
lrwxrwxrwx 1 root root 16 Jul 16 00:13 pmicbak -> /dev/block/sde11
lrwxrwxrwx 1 root root 15 Jul 16 00:13 ramdump -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 Jul 16 00:13 recovery -> /dev/block/sde20
lrwxrwxrwx 1 root root 15 Jul 16 00:13 recoveryconfig -> /dev/block/sdf9
lrwxrwxrwx 1 root root 15 Jul 16 00:13 reserve -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 Jul 16 00:13 rootconfig -> /dev/block/sdf8
lrwxrwxrwx 1 root root 15 Jul 16 00:13 rpm -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 Jul 16 00:13 rpmbak -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 Jul 16 00:13 sec -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 Jul 16 00:13 splash -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 Jul 16 00:13 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 Jul 16 00:13 sti -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 Jul 16 00:13 system -> /dev/block/sde19
lrwxrwxrwx 1 root root 15 Jul 16 00:13 tz -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 Jul 16 00:13 tzbak -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 Jul 16 00:13 userdata -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 Jul 16 00:13 xbl -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 Jul 16 00:13 xblbak -> /dev/block/sdc1
# fdisk -l /dev/block/sda
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sda: 51666944 sectors, 1120M
Logical sector size: 4096
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 12 entries
First usable sector is 6, last usable sector is 6458362
Number Start (sector) End (sector) Size Code Name
1 6 7 8192 0700 ssd
2 8 8199 32.0M 0700 persist
3 8200 73735 256M 0700 cache
4 73736 73991 1024K 0700 misc
5 73992 74119 512K 0700 keystore
6 74120 74151 128K 0700 devcfg
7 74152 74183 128K 0700 devcfgbak
8 74184 74311 512K 0700 frp
9 74312 75335 4096K 0700 ramdump
10 75336 6458362 24.3G 0700 userdata
~ # fdisk -l /dev/block/sdb
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdb: 8192 sectors, 32.0M
Logical sector size: 4096
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 4 entries
First usable sector is 6, last usable sector is 1018
Number Start (sector) End (sector) Size Code Name
1 6 1018 4052K 0700 xbl
~ # fdisk -l /dev/block/sdc
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdc: 8192 sectors, 32.0M
Logical sector size: 4096
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 4 entries
First usable sector is 6, last usable sector is 1018
Number Start (sector) End (sector) Size Code Name
1 6 1018 4052K 0700 xblbak
~ # fdisk -l /dev/block/sde
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sde: 10485760 sectors, 0
Logical sector size: 4096
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 36 entries
First usable sector is 6, last usable sector is 1310714
Number Start (sector) End (sector) Size Code Name
1 6 133 512K 0700 rpm
2 134 261 512K 0700 rpmbak
3 262 773 2048K 0700 tz
4 774 1285 2048K 0700 tzbak
5 1286 1413 512K 0700 hyp
6 1414 1541 512K 0700 hypbak
7 1542 2053 2048K 0700 fsg
8 2054 2309 1024K 0700 fsg_gap
9 2310 2313 16384 0700 sec
10 2314 2441 512K 0700 pmic
11 2442 2569 512K 0700 pmicbak
12 2570 30729 110M 0700 modem
13 30730 34825 16.0M 0700 dsp
14 34826 35081 1024K 0700 dip
15 35082 43273 32.0M 0700 mdtp
16 43274 43529 1024K 0700 aboot
17 43530 43785 1024K 0700 abootbak
18 43786 60169 64.0M 0700 boot
19 60170 1108745 4096M 0700 system
20 1108746 1125129 64.0M 0700 recovery
21 1125130 1125130 4096 0700 devinfo
22 1125131 1125386 1024K 0700 bluetooth
23 1125387 1125514 512K 0700 keymaster
24 1125515 1125642 512K 0700 keymasterbak
25 1125643 1125706 256K 0700 cmnlib
26 1125707 1125770 256K 0700 cmnlibbak
27 1125771 1125834 256K 0700 cmnlib64
28 1125835 1125898 256K 0700 cmnlib64bak
29 1125899 1125962 256K 0700 apdp
30 1125963 1126026 256K 0700 msadp
31 1126027 1126027 4096 0700 dpo
32 1126028 1151627 100M 0700 splash
33 1151628 1152139 2048K 0700 sti
34 1152140 1310714 619M 0700 last_parti
~ #
~ # fdisk -l /dev/block/sdf
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sdf: 65536 sectors, 256M
Logical sector size: 4096
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 16 entries
First usable sector is 6, last usable sector is 8186
Number Start (sector) End (sector) Size Code Name
1 6 517 2048K 0700 modemst1
2 518 773 1024K 0700 modemst1_gap
3 774 1285 2048K 0700 modemst2
4 1286 1541 1024K 0700 modemst2_gap
5 1542 1542 4096 0700 fsc
6 1543 1543 4096 0700 factory
7 1544 1544 4096 0700 bootconfig
8 1545 1545 4096 0700 rootconfig
9 1546 1546 4096 0700 recoveryconfig
10 1547 1674 512K 0700 letvconfig
11 1675 1802 512K 0700 letveui
12 1803 1930 512K 0700 letvsecure
13 1931 2058 512K 0700 letvreserve
14 2059 4618 10.0M 0700 kernellog
15 4619 8186 13.9M 0700 last_parti
~ #
Click to expand...
Click to collapse
I translated it, basically he is saying there is no method available to unbrick x26.. lol
same situation..i flash a chinese stock rom thru twrp and got stuck in bootlogo cant access the twrp now,i can access the fastboot but the bootloader is lock i cant flash twrp
kielpogi28 said:
same situation..i flash a chinese stock rom thru twrp and got stuck in bootlogo cant access the twrp now,i can access the fastboot but the bootloader is lock i cant flash twrp
Click to expand...
Click to collapse
your can go to recovery ? if can , you can try install the stock 20S . see the link
https://www.needrom.com/download/le...728-multilanguage-rom-unbrick-phone-fastboot/
DK Boneco said:
I received my LeEco Le Pro3 Elite (X722) this Thursday. It came with a ROM shop. I tested it, but I wanted to switch to Stock.
First I boot the TWRP of the X720 version without installing it through the "fastboot boot " command. I installed SuperSu and rebooted to the system. So I used the Shell through ADB to take a nandroid copy of the original recovery, boot, system and firmwares for security.
So far so good. So I installed TWRP replacing the original recovery.
I entered recovery mode and installed the stock ROM zl0 v026s. Everything went well. Then I installed the GApps. When in the middle of the process the smartphone suddenly turns off and tries to start the system.
The smartphone was stuck on the home screen. I tried to enter recovery mode and immediately it turns off the screen.
And worst: the bootloader that was unlocked is now locked and does not allow unlocking!
I do not know what to do! Without the recovery I can not recover the bootloader and without the bootloader I can not recover the recovery!
As far as I know the only way now is to use Qfil to flash the required files. But I did not find the necessary files.
I am still having all the backup needed to make it work, but I do not know how to flash it. Anyone have any idea how to solve this!
Please! Help me![/QUOTE]
Unfortunate you are bricked know if bootloader locked their is no fastboot.
Your mistake was flashing stock with twrp you should have flash with stock recovery
Their is no unbricking solution for your 722.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
mchlbenner said:
Unfortunate you are bricked know if bootloader locked their is no fastboot.
Your mistake was flashing stock with twrp you should have flash with stock recovery
Their is no unbricking solution for your 722.
Click to expand...
Click to collapse
If you entry to recovery, it will save
tony770101 said:
If you entry to recovery, it will save
Click to expand...
Click to collapse
If you read his thread no recovery and locked bootloader their is no fix for 722.
Sent from my LEX727 using xda premium