whene im typing *#*#7378423#*#* to verify the network statut it gives me that following signes/
[ ] Network 0
[ ] Network subset 0
[ ] Service Provider 0
[ ] Corporate 0
[ ] Sim 0
is it locked ?? ist unlocked ?? Hardlocked ???
and if it was locked any chances to unlock it by ordering an unlocking code?????
corel159 said:
whene im typing *#*#7378423#*#* to verify the network statut it gives me that following signes/
[ ] Network 0
[ ] Network subset 0
[ ] Service Provider 0
[ ] Corporate 0
[ ] Sim 0
is it locked ?? ist unlocked ?? Hardlocked ???
and if it was locked any chances to unlock it by ordering an unlocking code?????
Click to expand...
Click to collapse
SIM Free I think ( Mine is SIM Free and i have same numbers)
corel159 said:
whene im typing *#*#7378423#*#* to verify the network statut it gives me that following signes/
[ ] Network 0
[ ] Network subset 0
[ ] Service Provider 0
[ ] Corporate 0
[ ] Sim 0
is it locked ?? ist unlocked ?? Hardlocked ???
and if it was locked any chances to unlock it by ordering an unlocking code?????
Click to expand...
Click to collapse
I think it is unlocked Best way is to insert a different SIM card and try making a call/msg, if it goes then you can be sure
and if it is locked then yes it can be unlocked! All you would need is a unlocking code. PM me if it is locked and I will help you out
It's unlocked. If it was locked you'd see a [x] a a number meaning the amount of unlock attempts remaining. Like this:
Sent from my C5303 using Tapatalk 4
Using trusty branch of ubuntutouch with teamhydra kernel from https://github.com/Team-Hydra/android_kernel_htc_msm8660
No problems during compiling but whilst booting i get direct panic after mounting /data
Code:
[ 2.373443] Warning: unable to open an initial console.
[ 2.373657] Freeing init memory: 208K
[ 2.553283] systemd-udevd[132]: starting version 204
[ 4.405456] [USBH] ac_detect_expired: count = 0, connect_type = -1
[ 4.709136] initrd: mounting /dev/mmcblk0p23
[ 4.723815] EXT4-fs (mmcblk0p23): couldn't mount as ext3 due to feature incompatibilities
[ 4.758453] EXT4-fs (mmcblk0p23): couldn't mount as ext2 due to feature incompatibilities
[ 4.823120] EXT4-fs (mmcblk0p23): recovery complete
[ 4.823852] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mode. Opts: discard
[ 5.081878] [K] Kernel panic - not syncing: Attempted to kill init!
[ 5.082061] [<c010bf14>] (unwind_backtrace+0x0/0xf8) from [<c076cd2c>] (panic+0x74/0x1a4)
[ 5.082244] [<c076cd2c>] (panic+0x74/0x1a4) from [<c018e26c>] (do_exit+0x804/0x8a4)
[ 5.082336] [<c018e26c>] (do_exit+0x804/0x8a4) from [<c018e374>] (do_group_exit+0x3c/0xb0)
[ 5.082489] [<c018e374>] (do_group_exit+0x3c/0xb0) from [<c018e3f8>] (__wake_up_parent+0x0/0x18)
[ 5.082672] CPU1: stopping
[ 5.083099] [<c010bf14>] (unwind_backtrace+0x0/0xf8) from [<c010ae60>] (handle_IPI+0x128/0x154)
[ 5.083801] [<c010ae60>] (handle_IPI+0x128/0x154) from [<c01063cc>] (__irq_svc+0x4c/0xe4)
[ 5.084472] [<c01063cc>] (__irq_svc+0x4c/0xe4) from [<c0107500>] (cpu_idle+0x88/0xfc)
[ 5.084869] [<c0107500>] (cpu_idle+0x88/0xfc) from [<48768c14>] (0x48768c14)
[ 5.185821] subsystem-fatal-8x60: Q6 NMI was sent.
[ 5.190948] [K] Rebooting in 5 seconds..
[ 9.415405] [USBH] ac_detect_expired: count = 1, connect_type = -1
[ 10.198364] [K] Going down for restart now
[ 10.198516] [K] arch_reset: mode 104
[ 10.198608] [K] arch_reset: no command restart.
[ 10.198699] [K] from arch_reset
[ 10.198852] [K] back arch_reset
[ 10.299224] subsystem-fatal-8x60: Q6 NMI was sent.
[ 10.299346] [K] arch_reset: wait for modem flushing caches.
[ 19.435424] [USBH] ac_detect_expired: count = 2, connect_type = -1
[ 19.445404] [USBH] ac_detect_expired: count = 3, connect_type = -1
[ 20.314056] [K] arch_reset: modem flushes cache timeout.
[ 20.314117]
[ 20.314270] [K] Restarting Linux version 3.0.101-UbuntuTouch-Sensation-g886cfa4 ([email protected]) (gcc version 4.7.4 20131207 (prerelease) (Linaro GCC 4.7-2013.12) ) #3 SMP PREEMPT Sat Jan 25 16:55:58 EST 2014
[ 20.314300]
[ 20.364593] [K] restart: Console was locked!
Kernel config:
https://gist.github.com/cwxda/8624363
Someone can help me on this?
Try to disable VT_CONSOLE. I had a similar issue and that fixed it.
Sent from my TF300T using Tapatalk
Tried different combinations with VT_CONSOLE and HW_CONSOLE stuff, all didn't help :c
CoreWolf said:
Tried different combinations with VT_CONSOLE and HW_CONSOLE stuff, all didn't help :c
Click to expand...
Click to collapse
You need to turn all those CONSOLE settings off, did you try that?
Do you have console= in the command line? Remove that too.
Seems Ubuntu Touch does not like a console; I have not yet investigated deeper. Possible reason is that tty0 is used to communicate with the Android container. Then it might help to define a different tty for the kernel console, but I have not tried. Disabling all CONSOLE configs "N" fixed it for me and I have more urgent issues.
Sent from my TF300T using Tapatalk
Hi, i think that there is a network-related bug in stock kernel.
Phone reboots very often, when in stamina mode is on
Here is part oflast_kmsg:
Code:
[ 440.537078] active wake lock mmc1_detect
[ 440.537475] active wake lock msm_hsic_host
[ 440.537689] active wake lock alarm, time left 497
[ 440.589263] [B][COLOR="Red"]skb_under_panic: text:c04dd4e8 len:66 put:6 head:cd3af000 data:cd3aeffa tail:0xcd3af03c end:0xcd3af140 [U]dev:rmnet_usb0[/U][/COLOR][/B]
[ 440.589874] ------------[ cut here ]------------
[ 440.590332] kernel BUG at /home/hudsonslave/root/workspace/offbuild_lagan-1.3_android_matrix/HUDSON_PRODUCT/yuga/HUDSON_VARIANT/user/label/CM-12/kernel/net/core/skbuff.c:146!
[ 440.590789] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[ 440.591247] Modules linked in: wlan(O) texfat(PO) cfg80211
[ 440.592376] CPU: 0 Tainted: P W O (3.4.0-perf-g32ce454 #1)
[ 440.592803] PC is at skb_push+0x6c/0x80
[ 440.593017] LR is at skb_push+0x6c/0x80
"head:cd3af000 data:cd3aeffa" - data before head ??? What might cause that???
I am using QFIL to try and revive my X4, but I have no idea how to get into EDL mode when I cannot do anything with the device. Computer recognizes it when I plug it in as Quectel QDLoader 9008 in Ports, but that's it.
Any suggestions would be appreciated. I don't want to have to pay MOTO to fix it if possible.
I've exhausted every resource I have.
Thank you anyone that can help or at least point me in the right direction.\
EDIT: When I was eMMC Software Download app, phone shows in COM3 Download mode, but I need an XML file to flash with that tool and don't know how to get that.
I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?
Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?
DustArma said:
Knowing previous Moto phones you'll need a blankflash file that only Lenovo/Motorola has and may or may not get leaked in the future. Just to make sure, you really can't enter into fastboot mode.?
Click to expand...
Click to collapse
No, my power went out in the middle of fastboot flashing and screwed up all the partitions. I am stuck without the blankflash.. Thank you for replying to try to help.
christopher68369 said:
I have never heard of this method. I've never hard bricked my device either. How did this happen was it by a bad flash or corrupt update? I found this https://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Maybe it will help. Their may be a way to do it instead of xml. Either way it goes xml is just acompressed file with the ROM in it. Is it possible to find a file compressor with .xml format?
Click to expand...
Click to collapse
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.
johnjingle said:
Yes, already read all of that, doesn't help. Unfortunately, I am at ground zero still.
Click to expand...
Click to collapse
you can not take it to the Moto warranty? you do not have to know how the phone went blank...
bookworth said:
you can not take it to the Moto warranty? you do not have to know how the phone went blank...
Click to expand...
Click to collapse
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Bro! It's works! Thanks for blank-flash for my soft bricked moto x4.
O link não funciona
LazyCountry said:
u can try this blankflash.zip , run the script blank-flash.bat when you connect to PC have the 9008 port.
https ://drive.google.com/open?id=1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS (please delete the blank after https)
Click to expand...
Click to collapse
Please guy, this link not work! Help me Please. Thanks
silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
It does, if you follow his instructions stated after the link.
Consegui agora!
jhedfors said:
It does, if you follow his instructions stated after the link.
Click to expand...
Click to collapse
Thanks Very much! work perfectly
Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error:
**** Log buffer [000001] 2018-07-26_14:55:02 ****
[ 0.000] Opening device: \\.\COM6
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 172 (0xac)
[ 0.004] ...cpu.sn = 2293722822 (0x88b76ec6)
[ 0.004] Opening singleimage
[ 0.005] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.007] Loading programmer
[ 0.008] ...filename = programmer.elf
[ 0.008] Sending programmer
[ 0.196] Handling things over to programmer
[ 0.197] Identifying CPU version
[ 0.197] Waiting for firehose to get ready
[ 3.212] ...SDM630 1.0
[ 3.213] Determining target secure state
[ 3.215] ...secure = yes
[ 3.238] Configuring device...
[ 3.243] Flashing GPT...
[ 3.243] Flashing partition with gpt.bin
[ 3.247] Initializing storage
[ 4.421] Target NAK!
[ 4.421] ...ERROR: Failed to open the SDCC Device slot 0 partition 0
[ 4.422] ...ERROR: Failed to open the device 1 slot 0 partition 0
[ 4.423] ...INFO: Device type 1, slot 0, partition 0, error 0
[ 4.423] ...WARN: Get Info failed to open 1 slot 0, partition 0, error 0
[ 4.424] ...ERROR: Failed to get device info slot:0artition:0
[ 4.424] ...GetStorageInfo Failed - storage_device_get_info() returned FALSE
[ 4.424] ...ERROR 14: Line 1283: HANDLE_STORAGE_INFO_FAILURE
[ 4.424] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 4.424] Check qboot_log.txt for more details
[ 4.425] Total time: 4.426s
[ 4.425]
[ 4.425] qboot version 3.86
[ 4.425]
[ 4.425] DEVICE {
[ 4.425] name = "\\.\COM6",
[ 4.425] flags = "0x144",
[ 4.425] addr = "0x62FD64",
[ 4.425] sahara.current_mode = "0",
[ 4.425] api.buffer = "0x2B15020",
[ 4.425] cpu.serial = "2293722822",
[ 4.425] cpu.id = "172",
[ 4.425] cpu.sv_sbl = "1",
[ 4.425] cpu.name = "SDM630",
[ 4.425] storage.type = "eMMC",
[ 4.425] sahara.programmer = "programmer.elf",
[ 4.425] module.firehose = "0x2A51630",
[ 4.425] api.firehose = "0xF2EF68",
[ 4.425] cpu.ver = "256",
[ 4.425] cpu.vername = "1.0",
[ 4.425] fh.max_packet_sz = "1048576",
[ 4.425] fh.storage_inited = "1",
[ 4.425] provisioning_may_hang = "true",
[ 4.425] }
[ 4.425]
silvamatta said:
Please guy, this link not work! Help me Please. Thanks
Click to expand...
Click to collapse
You mean you can't download ?
waltwittman1 said:
Hi. I have a similar issue where all I have is the Qualcomm QD Loader 9008 and I attempted to use the blank flash to resolve it but I got the following error: (log text omitted)
Click to expand...
Click to collapse
I got a similar error when I tried the blank-flash on my bricked Moto X4. @waltwittman1 please let me know if you find a solution.
serial_write() Error
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB1
[ 0.000] Detecting device
[ 21.382] ...cpu.id = 172 (0xac)
[ 21.382] ...cpu.sn = 4247084357 (0xfd255d45)
[ 21.382] Opening singleimage
[ 21.382] Loading package
[ 21.384] ...filename = pkg.xml
[ 21.385] Loading programmer
[ 21.385] ...filename = programmer.elf
[ 21.385] Sending programmer
[ 21.570] Handling things over to programmer
[ 21.570] Identifying CPU version
[ 21.570] Waiting for firehose to get ready
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error
ttyUSB Permissions Linux
mistryous said:
After running blank-flash.sh with the phone connected and VolDown+Power held, I only can get this error. Anyone have any ideas or a singleimage.bin file for a Moto X4 XT1900-1 (Android One)?
[ 24.570] serial_write(), line 280: Input/output error
[104.005] Waiting for firehose to get ready
[107.005] serial_write(), line 280: Input/output error
Click to expand...
Click to collapse
While I was running as root on my Linux system, this was solved as an issue between the device showing up on /dev/ttyUSB0 initially. I set permissions correctly there, but it reconnects with VolDown+Power on /dev/ttyUSB1 which had limited permissions. While udev rules could solve it, I was lucky to catch the device correctly in time to manually change the permissions and have blankflash progress all the way through. [Upon further thought root should have solved this, so it is likely just an issue with how devices/permissions are set up on my system].
Owner trashed the blankflash file. Can anyone hook me up please?
Here you go.
luvcustom said:
Owner trashed the blankflash file. Can anyone hook me up please?
Click to expand...
Click to collapse
This is the one I use. This is my first post to the XDA forums so they prevented me from linking to my dropbox. So, replace the [dot] with a . and you should be good.
.dropbox [dot] com/s/3xi85sy207x3vs6/blankflash.zip?dl=0[/url]
Win 10 waiting for device message and nothing more.
and no 9008 port
moved
can you please point US to a " best thread or post " we can read and finally fully understand those differences we should consider, while evaluating most appropriate and suitable software/firmware ?
- OFFICIAL STOCK firmware: [ miIUI china - CN ] [ miUI EEA rom ] [ miUI global rom ]
- CUSTOM FIRMWARE/ROM: [ miUI EU rom ] [ xiaomi.EU rom ]
take care,
marc
EDIT : those pages with hypertext and web application [ MiFirm ] won't highlight differences from one firmware version to another and among those five [ 5 ] different aforementioned firmware versions and yet available for same mi-device model, we want to understand whether any isn't requiring boot loader unlocking and to then switch to a firmware version in the list above.
[ reason for asking: we tested some official and stock firmware features also found in ' settings >> about phone >> system update >> ... >> download latest update ' , we gathered a zip file is placed in a folder [ downloaded\rom ] and firmware is then updated on subsequent restart. stock and original firmware built-in feature and a official firmware switch process won't require boot loader unlocking. ]
where to read about differences between [ mi-device unlocking ] ; [ mi unlocking ] ; [ unlocking boot loader ] and yet [ OEM unlocking ] also found in DEV settings ?