Ok, I refuse to give up
a K900 phone has nothing on it. No system recovery, no backups, no real file system. I refuse to give up on this phone, there must be a way to push the k900 operating system to it. I have tried to create a sdfuse directory by adp push, but so far, fails saying something about permissions after taking forever to transfer the .inb file.
Suggestions? (Newb to android, not terminal scared)
viper359 said:
Ok, I refuse to give up
a K900 phone has nothing on it. No system recovery, no backups, no real file system. I refuse to give up on this phone, there must be a way to push the k900 operating system to it. I have tried to create a sdfuse directory by adp push, but so far, fails saying something about permissions after taking forever to transfer the .inb file.
Suggestions? (Newb to android, not terminal scared)
Click to expand...
Click to collapse
Did you try the intel flashing tool?
Sent from my Lenovo K900_ROW using xda app-developers app
mikey199 said:
Did you try the intel flashing tool?
Sent from my Lenovo K900_ROW using xda app-developers app
Click to expand...
Click to collapse
If you mean the manufacturing flash tool, I tried that method, installed all the drivers etc, but, it always fails the flash at the part that deals with the tlv file extention. If I remove that from the xml, it flashes properly, but, the device doesn't get past the final splash screen before loading into the phone.
09/02/13 00:16:52.281 INFO : Port 0/0/1 #0: XFSTK-PROGRESS SN: 35F4362CB55D4CD2 100
09/02/13 00:16:52.281 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 OS: Bytes left to send: 0
09/02/13 00:16:52.281 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 sending data to USB...
09/02/13 00:16:52.281 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::WriteOutPipe __BINARY__
09/02/13 00:16:52.281 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::WriteOutPipe 1
09/02/13 00:16:52.283 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusWdUsb20Device::Write --->__BINARY__
09/02/13 00:16:52.884 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusOS::ReleaseOsImageDataChunk
09/02/13 00:16:52.885 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 End of RIMG
09/02/13 00:16:52.885 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::GetOpCode
09/02/13 00:16:52.885 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::ReadInAck
09/02/13 00:16:52.887 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusWdUsb20Device::GetAck
09/02/13 00:16:53.420 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusWdUsb20Device::GetAck - EOIU(0x4)
09/02/13 00:16:53.420 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 EOIU Received...
09/02/13 00:16:53.420 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 sending DFN...
09/02/13 00:16:53.420 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::WriteOutPipe DFN
09/02/13 00:16:53.420 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::WriteOutPipe 1
09/02/13 00:16:53.422 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusWdUsb20Device::Write --->DFN
09/02/13 00:16:53.423 INFO : Port 0/0/1 #0: XFSTK-PROGRESS SN: 35F4362CB55D4CD2 100
09/02/13 00:16:53.423 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 OS: Operating system download completed.
09/02/13 00:16:55.424 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 ClvpDldrState::LogError
09/02/13 00:16:55.424 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: 35F4362CB55D4CD2 Error Code: 0 - Success
09/02/13 00:16:55.424 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusDownloader::do_abort
09/02/13 00:16:55.424 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 CloverviewPlusWdUsb20Device::Abort
09/02/13 00:16:55.424 DEBUG : Port 0/0/1 #0: XFSTK-LOG SN: 35F4362CB55D4CD2 L:/K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full/IFWI_vF9.4B_CLAK_DEV_WW12_0426_LE_DVT3_PVT_2G_B1_SOS_ARB11.bin size:2031420 bytes
09/02/13 00:16:55.424 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: 35F4362CB55D4CD2 PASS
09/02/13 00:16:55.424 INFO : Port 0/0/1 #0: XFSTK-STATUS SN: 35F4362CB55D4CD2 Firmware and OS download completed.
09/02/13 00:16:56.526 DEBUG : XFSTK SN: 35F4362CB55D4CD 2 -- Success: Transfer Completed Successfully
09/02/13 00:16:56.526 INFO : Port 0/0/1 #0: IFW flash success - SN : 35F4362CB55D4CD2
09/02/13 00:16:56.526 DEBUG : Port 0/0/1 #0: IFW flash success on device 35F4362CB55D4CD2 with state IFWI successfully flashed... REBOOT
09/02/13 00:17:04.657 DEBUG : Port 0/0/1 #0: SOC Device is disconnected - state:2 - status - IFWI successfully flashed... REBOOT
09/02/13 00:17:04.657 DEBUG : SOC device lost on port 1
09/02/13 00:17:26.042 DEBUG : Port 0/0/1 #0: Start Runnable : Medfield632B7AFE
09/02/13 00:17:26.042 INFO : Port 0/0/1 #0: Flashing OS
09/02/13 00:17:26.042 DEBUG : New Android device -> serial: Medfield632B7AFE status: 0 port: 1
09/02/13 00:17:26.042 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase factory
09/02/13 00:17:26.836 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:26.836 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:26.836 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase factory" returns:
erasing 'factory'...
OKAY [ 0.228s]
finished. total time: 0.228s
09/02/13 00:17:28.837 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase cache
09/02/13 00:17:29.579 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:29.579 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:29.579 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase cache" returns:
erasing 'cache'...
OKAY [ 0.721s]
finished. total time: 0.721s
09/02/13 00:17:31.579 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase config
09/02/13 00:17:31.900 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:31.900 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:31.900 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase config" returns:
erasing 'config'...
OKAY [ 0.302s]
finished. total time: 0.302s
09/02/13 00:17:33.902 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase data
09/02/13 00:17:35.663 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:35.663 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:35.663 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase data" returns:
erasing 'data'...
OKAY [ 1.741s]
finished. total time: 1.741s
09/02/13 00:17:37.664 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase spare
09/02/13 00:17:37.972 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:37.972 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:37.972 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase spare" returns:
erasing 'spare'...
OKAY [ 0.288s]
finished. total time: 0.288s
09/02/13 00:17:39.973 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE erase system
09/02/13 00:17:41.144 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:17:41.144 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:17:41.144 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE erase system" returns:
erasing 'system'...
OKAY [ 1.150s]
finished. total time: 1.150s
09/02/13 00:17:43.146 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE flash radio "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\radio_firmware_6360.bin"
09/02/13 00:18:08.425 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:08.425 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:08.425 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE flash radio "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\radio_firmware_6360.bin"" returns:
sending 'radio' (11310 KB)
fname=L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\radio_firmware_6360.bin...
OKAY [ 0.849s]
writing 'radio'...
OKAY [ 24.409s]
finished. total time: 25.257s
09/02/13 00:18:10.426 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE flash /tmp/NV_130119_MiddleEast.tlv "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\NV_130119_MiddleEast.tlv"
09/02/13 00:18:10.471 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:10.471 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:10.471 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE flash /tmp/NV_130119_MiddleEast.tlv "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\NV_130119_MiddleEast.tlv"" returns:
sending '/tmp/NV_130119_MiddleEast.tlv' (1 KB)
fname=L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\NV_130119_MiddleEast.tlv...
OKAY [ 0.013s]
writing '/tmp/NV_130119_MiddleEast.tlv'...
OKAY [ 0.012s]
finished. total time: 0.025s
09/02/13 00:18:12.472 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE flash splashscreen "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\rocket_start_logo-1080,480-2.bmp.stitched.signed.bin"
09/02/13 00:18:12.694 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:12.694 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:12.694 DEBUG : Port 0/0/1 #0: "fastboot -s Medfield632B7AFE flash splashscreen "L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\rocket_start_logo-1080,480-2.bmp.stitched.signed.bin"" returns:
sending 'splashscreen' (1520 KB)
fname=L:\K900_ROW_1_S_2_009_0081_130620_MiddleEast_DVT3_CPUsign_full\rocket_start_logo-1080,480-2.bmp.stitched.signed.bin...
OKAY [ 0.125s]
writing 'splashscreen'...
OKAY [ 0.077s]
finished. total time: 0.201s
09/02/13 00:18:14.695 INFO : Port 0/0/1 #0: fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv
09/02/13 00:18:25.749 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:25.749 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:25.749 WARNING: Port 0/0/1 #0: Failed to execute "fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv":
...
Sending NVM config to the modem...
Send NVM config failed. Error 2
FAILED (remote: nvm)
finished. total time: 11.033s
09/02/13 00:18:27.750 WARNING: Port 0/0/1 #0: Retry to execute fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv
09/02/13 00:18:38.766 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:38.766 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:38.766 WARNING: Port 0/0/1 #0: Failed to execute "fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv":
...
Sending NVM config to the modem...
Send NVM config failed. Error 2
FAILED (remote: nvm)
finished. total time: 10.997s
09/02/13 00:18:40.767 WARNING: Port 0/0/1 #0: Retry to execute fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv
09/02/13 00:18:51.787 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:18:51.787 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:18:51.787 WARNING: Port 0/0/1 #0: Failed to execute "fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv":
...
Sending NVM config to the modem...
Send NVM config failed. Error 2
FAILED (remote: nvm)
finished. total time: 10.999s
09/02/13 00:18:53.788 WARNING: Port 0/0/1 #0: Retry to execute fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv
09/02/13 00:19:04.807 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:19:04.807 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:19:04.807 WARNING: Port 0/0/1 #0: Failed to execute "fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv":
...
Sending NVM config to the modem...
Send NVM config failed. Error 2
FAILED (remote: nvm)
finished. total time: 11.000s
09/02/13 00:19:06.808 WARNING: Port 0/0/1 #0: Retry to execute fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv
09/02/13 00:19:17.828 DEBUG : Port 0/0/1 #0: Process terminated, start reading output
09/02/13 00:19:17.828 DEBUG : Port 0/0/1 #0: Output OK
09/02/13 00:19:17.828 WARNING: Port 0/0/1 #0: Failed to execute "fastboot -s Medfield632B7AFE oem nvm apply /tmp/NV_130119_MiddleEast.tlv":
...
Sending NVM config to the modem...
Send NVM config failed. Error 2
FAILED (remote: nvm)
finished. total time: 10.999s
09/02/13 00:19:19.829 ERROR : Port 0/0/1 #0: Flash failure
So if anyone has any clue how to deal with that error, it would help. If I remove the tvl commands from the xml sheet, for any build, it installs fully, but the phone doesn't boot past the last splash screen.
anyone?
viper359 said:
anyone?
Click to expand...
Click to collapse
I am having the same problem. I went into the .XML file and removed the command to apply the NV file. and retried and the flash completed but the device keeps rebooting itself. I am still digging into this and as soon as I get anywhere I will let you know.
I had the same problem. I used the default xml file it failed then i tried the latinamerica xml and it flashed fine. Not sure why quick glance at the xml files looked the same. Good luck hope this helps.
Sent from my
Non-chinese Lenovo K900.
Related
Finally I found the correct forum...
Hello, I need help with my Samsung Galaxy SGH-727 skyrocket..Got stuck on the Odin mode...
That happen when i try to root my phone
I got this message:
Firmware upgrade encountered an issue.Please select recovery mode in Kies & try again.
Nothing is working, Vol -, Vol + usb, getting Download Mode, Vol + and I stuck in Odin Mode again...... Very frustrated
How can i get out of the Odin Mode? This is a Hard Brick.?
Kies failed to connect and Odin Failed to flash....
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Complete(Write) operation failed.
<ID:0/008> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Please help ..Thanks in advance....
Are you sure you have the right Version of Odin and are using it correctly. Are you sure you have the correct tar file for your phone? Have you read Vincoms sticky on the whole odin/flash/recovery process?
Are you using the stock USB cable?
It made a difference for me.
Not bricked. Use different USB port and try flashing the firmware again. Preferably use one of the back usb ports that are on the PC main board.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
rushi.1986 said:
Not bricked. Use different USB port and try flashing the firmware again. Preferably use one of the back usb ports that are on the PC main board.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
read the odin troubleshooting section in the "restoring to stock" link in my sig
Galaxy S2 SGH-I727 stuck on Odin Mode, Bricked ? Help Please
vincom said:
read the odin troubleshooting section in the "restoring to stock" link in my sig
Click to expand...
Click to collapse
Thank You Vincom, Yes I did, I read all the post, but the problem is I can´t enter in Dowloading Mode....
Nothing is working, Up and Volume Down keys simultaneously + usb, getting Warning, Volume up Continue, Volume down Cancel, Restart phone, and then I press Vol + and I stuck in Odin Mode again.....
Check the picture.
Kies failed to connect and Odin Failed to flash...
Cindor said:
Thank You Vincom, Yes I did, I read all the post, but the problem is I can´t enter in Dowloading Mode....
Nothing is working, Up and Volume Down keys simultaneously + usb, getting Warning, Volume up Continue, Volume down Cancel, Restart phone, and then I press Vol + and I stuck in Odin Mode again.....
Check the picture.
Kies failed to connect and Odin Failed to flash...
Click to expand...
Click to collapse
It's already in download mode bro. Get Odin fired up and flash it
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yeah, that image is download mode.
Sent via the Skyrocket
Quando Omni Flunkus Moritati
Galaxy S2 SGH-I727 stuck on Odin Mode, Bricked ? Help Please
liquidzoo said:
Yeah, that image is download mode.
Sent via the Skyrocket
Quando Omni Flunkus Moritati
Click to expand...
Click to collapse
Thanks, liquidzoo and xcrazydx, so if this is a Download mode, I flashing a wrong file probably...
I´m using Odin3 V3.04, and trying Flashing: I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5, and recovery.tar.md5 but they are not working....
I used 3 different USB cable already with out luck.
Can some one address me to the correct procedure please, Thank You...
Try Odin v1.85 I never liked the one you're using.
Sent from my SGH-I727 using xda app-developers app
jd1639 said:
Try Odin v1.85 I never liked the one you're using.
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
That seems like the right file, but yes 1.85 is the recommended version (download in vincom's thread).
Also, make sure that you're using the cable that came with the phone. I had issues on other ones, but that one worked perfectly.
Stuck on "Complete(Write) operation failed."
Hi guys. This is my story. Few days ago i wanted to view fotos. Suddenly phone switched off. Phone couldn't switch on again. Samsung logo appeared than disappeared and nothing happend. I decided to clean cache. Rebooted to CWMR, selected clean cache and system showed me message "/cache cannot be mounted". I've decided to reinstall my ROM. Reinstallation failed. On next reboot I couldn't enter CWMR. Holding Up and Down buttons hanged phone on Samsung logo. On normal reboot again Samsung logo appeared than disappeared and nothing happend.
Used Odin 1.85 to factory reset my SGS II i727. Got this picture on the screen https://dl.dropboxusercontent.com/u/84573385/preodinmode.jpg and than this one https://dl.dropboxusercontent.com/u/84573385/odinmode.jpg.
First got "Getting PIT for mapping" error. Used solution from vincom's thread from section 3.
Now it stucks on write operation (screenshot attached):
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried two different cables on all USB ports of my two laptops on Windows 7 and XP. Rebooted PCs few times after driver installation.
ROM installed before crash: Avatar ROM 4.2.2
Version of CWMRTouch installed before crash: 6.0.4.3
Samsung drivers installed on PC: SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail (w/ version v1_3_2200_0 Odin stucked on Initialisation or SetupConnection stage)
Please, help. What else can I do with my problem?
dLuck said:
Hi guys. This is my story. Few days ago i wanted to view fotos. Suddenly phone switched off. Phone couldn't switch on again. Samsung logo appeared than disappeared and nothing happend. I decided to clean cache. Rebooted to CWMR, selected clean cache and system showed me message "/cache cannot be mounted". I've decided to reinstall my ROM. Reinstallation failed. On next reboot I couldn't enter CWMR. Holding Up and Down buttons hanged phone on Samsung logo. On normal reboot again Samsung logo appeared than disappeared and nothing happend.
Used Odin 1.85 to factory reset my SGS II i727. Got this picture on the screen https://dl.dropboxusercontent.com/u/84573385/preodinmode.jpg and than this one https://dl.dropboxusercontent.com/u/84573385/odinmode.jpg.
First got "Getting PIT for mapping" error. Used solution from vincom's thread from section 3.
Now it stucks on write operation (screenshot attached):
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried two different cables on all USB ports of my two laptops on Windows 7 and XP. Rebooted PCs few times after driver installation.
ROM installed before crash: Avatar ROM 4.2.2
Version of CWMRTouch installed before crash: 6.0.4.3
Samsung drivers installed on PC: SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail (w/ version v1_3_2200_0 Odin stucked on Initialisation or SetupConnection stage)
Please, help. What else can I do with my problem?
Click to expand...
Click to collapse
try the celox pit file again, but remember to use the "pit" option in odin and not pda, idk if it will work but u got nothing to loose, the emmc(memory) could be screwed up or dead, unbricking it might also help
vincom said:
try the celox pit file again, but remember to use the "pit" option in odin and not pda, idk if it will work but u got nothing to loose, the emmc(memory) could be screwed up or dead, unbricking it might also help
Click to expand...
Click to collapse
tried celox.pit again and now it is write error (screenshot attached). I did it by default w/o unchecking Re-partition option.
Sorry for asking but what do you mean "unbricking it" ? How can I repair internal memory if it is dead?
dLuck said:
tried celox.pit again and now it is write error (screenshot attached). I did it by default w/o unchecking Re-partition option.
Sorry for asking but what do you mean "unbricking it" ? How can I repair internal memory if it is dead?
Click to expand...
Click to collapse
i said might if its corrupted, jtag(unbrick) might fix it but unless tried who knows for sure
vincom said:
i said might if its corrupted, jtag(unbrick) might fix it but unless tried who knows for sure
Click to expand...
Click to collapse
So for this moment w/o JTAG option you can say that my phone is dead? Like you said I have nothing to loose. What else can I do maybe to fix my problem? If nothing :crying: - is there any way to get data (fotos) from internal SDcard?
I tried Heimdall on Linux machine.
Executed two commands:
1. sudo heimdall detect --verbose --stdout-errors --usb-log-level debug (Description: Indicates whether or not a download mode device can be detected.)
Result:
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.003046] [00000c57] libusbx: debug [libusb_get_device_list]
[ 0.003115] [00000c57] libusbx: debug [discovered_devs_append] need to increase capacity
[ 0.003143] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003156] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003171] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003186] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003200] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003212] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003226] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003240] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003253] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003266] [00000c57] libusbx: debug [libusb_get_device_descriptor]
[ 0.003280] [00000c57] libusbx: debug [libusb_get_device_descriptor]
Device detected
[ 0.003320] [00000c57] libusbx: debug [libusb_exit]
[ 0.003335] [00000c57] libusbx: debug [libusb_exit] destroying default context
2. sudo heimdall print-pit --verbose --stdout-errors --usb-log-level debug (Description: Prints the contents of a PIT file in a human readable format. If a filename is not provided then Heimdall retrieves the PIT file from the connected device.)
Result:
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...
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.005876] [00000c5b] libusbx: debug [libusb_get_device_list]
[ 0.005970] [00000c5b] libusbx: debug [discovered_devs_append] need to increase capacity
[ 0.006011] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006038] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006066] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006096] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006123] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006149] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006176] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006202] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006232] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006260] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006287] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006317] [00000c5b] libusbx: debug [libusb_open] open 5.2
[ 0.006380] [00000c5b] libusbx: debug [usbi_add_pollfd] add fd 11 events 4
[ 0.006444] [00000c5b] libusbx: debug [libusb_get_device_descriptor]
[ 0.006481] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.006532] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.006561] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.007328] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.007377] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=0 transferred=4
[ 0.007388] [00000c5b] libusbx: debug [handle_control_completion] handling completion status 0
[ 0.007399] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.007412] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x16681f8 has callback 0x7fbb5a5c97f0
[ 0.007422] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=4
[ 0.007451] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.007480] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.007491] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.008323] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.008371] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=0 transferred=18
[ 0.008383] [00000c5b] libusbx: debug [handle_control_completion] handling completion status 0
[ 0.008395] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.008407] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x16681f8 has callback 0x7fbb5a5c97f0
[ 0.008418] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=18
Manufacturer: "Sasmsung"
[ 0.008446] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.008473] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.008484] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.009174] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.009197] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=0 transferred=4
[ 0.009207] [00000c5b] libusbx: debug [handle_control_completion] handling completion status 0
[ 0.009216] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.009226] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x16681f8 has callback 0x7fbb5a5c97f0
[ 0.009236] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=4
[ 0.009249] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.009268] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.009278] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.010077] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.010126] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=0 transferred=16
[ 0.010138] [00000c5b] libusbx: debug [handle_control_completion] handling completion status 0
[ 0.010149] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.010162] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x16681f8 has callback 0x7fbb5a5c97f0
[ 0.010172] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=16
Product: "MSM8x60"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
[ 0.010239] [00000c5b] libusbx: debug [libusb_get_config_descriptor] index 0
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...
[ 0.010341] [00000c5b] libusbx: debug [libusb_claim_interface] interface 1
Setting up interface...
[ 0.010389] [00000c5b] libusbx: debug [libusb_set_interface_alt_setting] interface 1 altsetting 0
Initialising protocol...
[ 0.013097] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.013156] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.013185] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.013858] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.013932] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.013962] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.013990] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.014019] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.014048] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.014077] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #1 failed. Result: 0
[ 0.014209] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.014253] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.014282] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.014857] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.014933] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.014962] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.014990] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.015019] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.015049] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.015077] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #2 failed. Result: 0
[ 0.015185] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.015229] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.015258] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.015785] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.015860] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.015889] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.015918] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.015946] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.015976] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.016014] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #3 failed. Result: 0
[ 0.016134] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.016178] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.016207] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.016765] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.016858] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.016887] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.016916] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.016944] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.016974] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.017001] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #4 failed. Result: 0
[ 0.017105] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.017150] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.017179] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.017769] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.017846] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.017874] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.017903] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.017931] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.017961] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.017988] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #5 failed. Result: 0
[ 0.018092] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.018137] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.018165] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.018648] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 0.018731] [00000c5b] libusbx: debug [reap_for_handle] urb type=2 status=-32 transferred=0
[ 0.018766] [00000c5b] libusbx: debug [handle_control_completion] handling completion status -32
[ 0.018801] [00000c5b] libusbx: debug [handle_control_completion] unsupported control request
[ 0.018836] [00000c5b] libusbx: debug [disarm_timerfd]
[ 0.018872] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 0.018901] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
WARNING: Control transfer #6 failed. Result: -9
WARNING: Control transfer #6 failed. Result: 0
[ 0.019008] [00000c5b] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.019037] [00000c5b] libusbx: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 4
[ 0.019084] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.019112] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 1.019126] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 1.019166] [00000c5b] libusbx: debug [handle_events] timerfd triggered
[ 1.019177] [00000c5b] libusbx: debug [libusb_cancel_transfer]
[ 1.019365] [00000c5b] libusbx: debug [disarm_timerfd]
[ 1.019411] [00000c5b] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 1.019425] [00000c5b] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 1.019445] [00000c5b] libusbx: debug [handle_events] poll() returned 1
[ 1.019464] [00000c5b] libusbx: debug [reap_for_handle] urb type=3 status=-2 transferred=0
[ 1.019477] [00000c5b] libusbx: debug [handle_bulk_completion] handling completion status -2 of bulk urb 1/1
[ 1.019490] [00000c5b] libusbx: debug [handle_bulk_completion] abnormal reap: urb status -2
[ 1.019501] [00000c5b] libusbx: debug [handle_bulk_completion] abnormal reap: last URB handled, reporting
[ 1.019511] [00000c5b] libusbx: debug [usbi_handle_transfer_cancellation] detected timeout cancellation
[ 1.019520] [00000c5b] libusbx: debug [disarm_timerfd]
[ 1.019531] [00000c5b] libusbx: debug [usbi_handle_transfer_completion] transfer 0x1668288 has callback 0x7fbb5a5c97f0
[ 1.019540] [00000c5b] libusbx: debug [sync_transfer_cb] actual_length=0
ERROR: Failed to send data: "ODIN"
ERROR: Failed to send data: "(null)"
Releasing device interface...
[ 1.019581] [00000c5b] libusbx: debug [libusb_release_interface] interface 1
[ 1.019618] [00000c5b] libusbx: debug [libusb_close]
[ 1.019640] [00000c5b] libusbx: debug [usbi_remove_pollfd] remove fd 11
[ 1.019679] [00000c5b] libusbx: debug [libusb_exit]
[ 1.019689] [00000c5b] libusbx: debug [libusb_exit] destroying default context
Will this help to find out whether emmc memory is dead?
Hello, I have a Moto G first generation, and when I was upgrading to kitkat he hung up and did not call more when put to load it flashes the LED and not out place and not enter into fastboot can help me?
Result MotoFlasher Tool
SYSTEM: Device Selected: Moto G v1, Android 4.4.2
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: < waiting for device >
OUTPUT: opening device: \\.\COM14
OUTPUT: OKAY [ 0.020s]
OUTPUT: greeting device for command mode
OUTPUT: OKAY [ 0.001s]
OUTPUT: identifying device
OUTPUT: ...serial = 0x236D843
OUTPUT: ...chip-id = 0x800 (MSM8226)
OUTPUT: ...chip-rev = 0x0
OUTPUT: ...sv-sbl = 0x0
OUTPUT: OKAY [ 0.006s]
OUTPUT: finding files
OUTPUT: ...programmer = programmer.mbn
OUTPUT: ...singleimage = singleimage.bin
OUTPUT: OKAY [ 0.017s]
OUTPUT: validating files
OUTPUT: OKAY [ 0.026s]
OUTPUT: switching to download mode
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for image downloading
OUTPUT: OKAY [ 0.002s]
OUTPUT: sending programmer
OUTPUT: OKAY [ 0.042s]
OUTPUT: flashing singleimage
OUTPUT: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT:
OUTPUT:
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
Motorola Moto G
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Moto G Q&A, Help & Troubleshooting
Good luck!
KaHJonas said:
Hello, I have a Moto G first generation, and when I was upgrading to kitkat he hung up and did not call more when put to load it flashes the LED and not out place and not enter into fastboot can help me?
Result MotoFlasher Tool
SYSTEM: Device Selected: Moto G v1, Android 4.4.2
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: < waiting for device >
OUTPUT: opening device: \\.\COM14
OUTPUT: OKAY [ 0.020s]
OUTPUT: greeting device for command mode
OUTPUT: OKAY [ 0.001s]
OUTPUT: identifying device
OUTPUT: ...serial = 0x236D843
OUTPUT: ...chip-id = 0x800 (MSM8226)
OUTPUT: ...chip-rev = 0x0
OUTPUT: ...sv-sbl = 0x0
OUTPUT: OKAY [ 0.006s]
OUTPUT: finding files
OUTPUT: ...programmer = programmer.mbn
OUTPUT: ...singleimage = singleimage.bin
OUTPUT: OKAY [ 0.017s]
OUTPUT: validating files
OUTPUT: OKAY [ 0.026s]
OUTPUT: switching to download mode
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for image downloading
OUTPUT: OKAY [ 0.002s]
OUTPUT: sending programmer
OUTPUT: OKAY [ 0.042s]
OUTPUT: flashing singleimage
OUTPUT: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT:
OUTPUT:
Click to expand...
Click to collapse
You can't enter fastboot? Can you enter bootloader mode?
...
itouchables said:
You can't enter fastboot? Can you enter bootloader mode?
Click to expand...
Click to collapse
No!:crying:
Hello friends , I saw that forum several people are crying for MOTO G with hard brick , plus my MOTO G xt1033 different happened I was in 4.3 GPE and updated it to 4.4 and eventually bricked already tried every way to refresh it more up now nothing .
Sorry My English , im Brazillian
This is the error I get after trying flasher the bootloader already tried with 4.3 and 4.4 more is always the same mistake
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM6
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: FAILED (blank-flash:greet-device:error reading packet)
I have got around 60+ Redmi note 5 pro unlocked log file. Interested person can download from the link bellow
drive_google_com#open?id=1eWcXn-QidkdlFazaOjOSyacF94_YU6Oe (replace _ with . and # with / )
Sample
INFO <11:09:37.088,T:5188> : to login by name:XXX pwd:verify:XXX sec_token:EMPTY
INFO <11:09:37.089,T:5188> : LoginStep1
DEBUG <11:09:38.408,T:5188> : Login success and get user detail
DEBUG <11:09:39.461,T:3588> : account logged in
DEBUG <11:09:39.462,T:3588> : account login succeed
DEBUG <11:09:39.462,T:3588> : get set_check_page msg
DEBUG <11:09:39.469,T:3588> : longin page switch to check page
DEBUG <11:09:39.469,T:3460> : check right function start
DEBUG <11:09:39.504,T:3460> : Begin login unlockApi
DEBUG <11:09:42.979,T:3460> : End login unlockApi
DEBUG <11:09:42.984,T:3460> : joinedStr = POST
/api/v2/nonce
r=hcvwngkaxmtppgzr&sid=miui_unlocktool_client
DEBUG <11:09:45.387,T:3460> : joinedStr = POST
/api/v2/unlock/userinfo
data=ewogICAiY2xpZW50SWQiIDogIjEiLAogICAiY2xpZW50VmVyc2lvbiIgOiAiMi4yLjYyNC4xNCIsCiAgICJsYW5ndWFnZSIgOiAiZW4iLAogICAicGNJZCIgOiAiMThhNTg2ZWEwMDc0ODRhYWM3ZjYzZDhjZGMyNzA0ZjgiLAogICAicmVnaW9uIiA6ICIiLAogICAidWlkIiA6ICI1MTU2NDY0ODI5Igp9Cg==&nonce=eyJzIjoiZThlOGVlOTNlYjFiNWE3N2Q4YWE2ZDJkMzVmZTAyOWVmMWU5ZmZiMiIsInQiOjE1MjgzNDk5ODc5ODMsInIiOiJPV1IzNiJ9&sid=miui_unlocktool_client
INFO <11:09:47.578,T:3460> : status result: {
"applyStatus" : 2,
"code" : 0,
"description" : null,
"shouldApply" : false,
"uid" : 5156464829
}
WARNING<11:09:47.580,T:3460> : missing uid in unlock status json
DEBUG <11:09:47.581,T:3460> : unlock status: 2
DEBUG <11:09:47.582,T:3460> : should apply:false
DEBUG <11:09:47.587,T:1716> : getvar token -s 14b06a44
DEBUG <11:09:47.758,T:1716> : token: vM0kXsPeclxzHPlvd/+kEa2q6K8=
finished. total time: 0.001s
DEBUG <11:09:47.759,T:1716> : to check erase feature for 14b06a44
DEBUG <11:09:47.800,T:1716> : joinedStr = POST
/api/v2/nonce
r=nnxnvngybxwixsvv&sid=miui_unlocktool_client
DEBUG <11:09:49.995,T:1716> : joinedStr = POST
/api/v1/unlock/device/clear
appId=1&data=ewogICAiY2xpZW50SWQiIDogIjEiLAogICAiY2xpZW50VmVyc2lvbiIgOiAiMi4yLjYyNC4xNCIsCiAgICJsYW5ndWFnZSIgOiAiZW4iLAogICAicGNJZCIgOiAiMThhNTg2ZWEwMDc0ODRhYWM3ZjYzZDhjZGMyNzA0ZjgiLAogICAicHJvZHVjdCIgOiAid2h5cmVkIiwKICAgInJlZ2lvbiIgOiAiIgp9Cg==&nonce=eyJzIjoiNDllYTc1OGRlMTNjZmIwNWVmZjE0OTZhZTZlNTNlNDJkMWU0Yjc3MCIsInQiOjE1MjgzNDk5OTI1ODYsInIiOiJYNndXTiJ9&sid=miui_unlocktool_client
DEBUG <11:09:54.698,T:3588> : 5
DEBUG <11:09:54.699,T:1716> : getvar token -s 14b06a44
DEBUG <11:09:54.871,T:1716> : token: vM0kXsPeclxzHPlvd/+kEa2q6K8=
finished. total time: 0.001s
DEBUG <11:09:54.872,T:1716> : -s 14b06a44 oem device-info
DEBUG <11:09:55.042,T:1716> : ...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.002s]
finished. total time: 0.002s
DEBUG <11:09:55.198,T:3588> : 10
DEBUG <11:09:55.699,T:3588> : 15
DEBUG <11:09:56.199,T:3588> : 20
DEBUG <11:09:56.700,T:3588> : 25
DEBUG <11:09:57.200,T:3588> : 30
DEBUG <11:09:57.699,T:3588> : 35
DEBUG <11:09:58.200,T:3588> : 40
DEBUG <11:09:58.700,T:3588> : 45
DEBUG <11:09:59.201,T:3588> : 50
DEBUG <11:09:59.699,T:3588> : 55
DEBUG <11:09:59.700,T:1716> : VerifyDeviceInfo
INFO <11:09:59.700,T:1716> : product:whyred
DEBUG <11:09:59.702,T:1716> : getvar token -s 14b06a44
DEBUG <11:09:59.876,T:1716> : token: vM0kXsPeclxzHPlvd/+kEa2q6K8=
finished. total time: 0.001s
DEBUG <11:09:59.878,T:1716> : to sign token with key for device:whyred
DEBUG <11:09:59.922,T:1716> : joinedStr = POST
/api/v2/nonce
r=idlaefpqhxlmwjjr&sid=miui_unlocktool_client
DEBUG <11:10:00.200,T:3588> : 60
DEBUG <11:10:00.701,T:3588> : 65
DEBUG <11:10:01.201,T:3588> : 70
DEBUG <11:10:01.701,T:3588> : 75
DEBUG <11:10:02.201,T:3588> : 80
DEBUG <11:10:02.420,T:1716> : joinedStr = POST
/api/v2/ahaUnlock
appId=1&data=ewogICAiY2xpZW50SWQiIDogIjIiLAogICAiY2xpZW50VmVyc2lvbiIgOiAiMi4yLjYyNC4xNCIsCiAgICJkZXZpY2VJbmZvIiA6IHsKICAgICAgImJvYXJkVmVyc2lvbiIgOiAiIiwKICAgICAgImRldmljZU5hbWUiIDogIiIsCiAgICAgICJwcm9kdWN0IiA6ICJ3aHlyZWQiLAogICAgICAic29jSWQiIDogIiIKICAgfSwKICAgImRldmljZVRva2VuIiA6ICJ2TTBrWHNQZWNseHpIUGx2ZC8ra0VhMnE2Szg9IiwKICAgImxhbmd1YWdlIiA6ICJlbiIsCiAgICJvcGVyYXRlIiA6ICJ1bmxvY2siLAogICAicGNJZCIgOiAiMThhNTg2ZWEwMDc0ODRhYWM3ZjYzZDhjZGMyNzA0ZjgiLAogICAicmVnaW9uIiA6ICIiLAogICAidWlkIiA6ICI1MTU2NDY0ODI5Igp9Cg==&nonce=eyJzIjoiMzk1MzM2MTA3YTZmNDE4MzQxM2ZjM2UyNWVhNTU1OTE1ZDM4M2MzNyIsInQiOjE1MjgzNTAwMDQ5NDgsInIiOiJhZ29OQSJ9&sid=miui_unlocktool_client
DEBUG <11:10:02.701,T:3588> : 85
DEBUG <11:10:03.201,T:3588> : 90
DEBUG <11:10:03.701,T:3588> : 95
DEBUG <11:10:04.201,T:3588> : 99
DEBUG <11:10:14.264,T:1716> : sign result:{
"code" : 0,
"description" : "私钥签名成功",
"encryptData" : "94F683C63AD692DEEC91403100D0003D31DB8DCEB45104BFE03540F35D16E98F87745101F1D228D41DF0F6D99B52C6D0EEBC3C98F20EF56C3B01E50E0F36A6BC29FB751898A641346857E3A8B94BD6B8CAEA6ED043EDD3B2D39D9ADFAC9E0948A0C512EA8901F58CAB863011D715CB56EE18CC427486EFD9BB84EBCB2AE2C5CFE51726BDA1A73CB700D4FECB18AD09ECC3203F7DD4669C68E0AF61DC742FEF3D06590089C7F1CD818A9885E819B3036928A9F2C0B52579F9E7EE65F0B7EEB4F6369AC6AC307770C605DFF4106CFE113711813B004EB572642935FEF05F1212BA3284C13A197FE1723A85F81B1BD134A347279852BB603F3057EC2D2F62C86E68",
"uid" : 5156464829
}
DEBUG <11:10:14.268,T:1716> : unlock return:0 msg:私钥签名成功
DEBUG <11:10:14.269,T:1716> : UnlockBootloader
DEBUG <11:10:14.274,T:1716> : -s 14b06a44 oem unlock "14b06a44_sig.data"
DEBUG <11:10:14.619,T:1716> : argc is 3
downloading 'signature'...
OKAY [ 0.010s]
...
OKAY [ 0.130s]
finished. total time: 0.141s
DEBUG <11:10:14.643,T:1716> : getvar token -s 14b06a44
DEBUG <11:10:14.754,T:2780> : auto refresh device list
DEBUG <11:10:14.870,T:2780> : remove sn:14b06a44
INFO <11:10:14.870,T:2780> : fastboot devices
DEBUG <11:10:16.660,T:1716> :
DEBUG <11:10:30.459,T:2780> : auto refresh device list
DEBUG <11:10:30.511,T:2780> : use desp:Android ADB Interface instead of Android
INFO <11:10:30.620,T:2780> : fastboot devices
DEBUG <11:10:30.825,T:2780> : getvar token -s 14b06a44
DEBUG <11:10:30.830,T:3436> : getvar token -s 14b06a44
DEBUG <11:10:31.150,T:3436> : token: IyCsTcQuIvXln5XcL8AVtq2q6K8=
finished. total time: 0.001s
DEBUG <11:10:31.151,T:3436> : -s 14b06a44 oem device-info
DEBUG <11:10:31.370,T:3436> : ...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.003s]
finished. total time: 0.003s
Yesterday I wanted to flash my new Nairo / xt2075-3 / moto G5G plus with LineageOS. But unfortunately it doesn't boot anymore.
Only the EDL boot works. This blankfile works not:
https://mirrors.lolinet.com/firmware/motorola/nairo/blankflash/blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip
https://mirrors.lolinet.com/firmware/moto/nairo/blankflash/blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip
I downloaded a full TWRP backup (befor i bricket the device) and the latest stock ROM (using Motorola Rescuetool, but this requires fastboot)
This guide doesn't work either:
https://www.reddit.com/r/MotoG/comments/k73n66
I use the Image-Files from the Stock ROM this are the extrcted files:
27.05.2022 18:57 339968 abl.elf
27.05.2022 18:57 519296 aop.mbn
14.12.2020 02:09 35 blank-flash.bat
14.12.2020 02:09 38 blank-flash.sh
02.03.2022 15:59 13107456 bootloader.img
27.05.2022 18:50 708 default.xml
27.05.2022 18:57 126080 devcfg.mbn
02.03.2022 15:59 211712 gpt.bin
27.05.2022 18:57 519296 hyp.mbn
27.05.2022 18:50 134 index.xml
27.05.2022 18:57 519296 keymaster.mbn
27.05.2022 18:50 80 pkg.xml
27.05.2022 18:44 682968 programmer.elf
27.05.2022 18:57 257152 prov64.mbn
14.12.2020 02:09 181144 qboot
14.12.2020 02:09 229106 qboot.dll
14.12.2020 02:09 134292 qboot.exe
27.05.2022 18:57 76928 qupfw.elf
27.05.2022 19:03 7721216 singleimage.bin
31.10.2019 05:35 93624 star
31.10.2019 05:35 194682 star.exe
27.05.2022 18:57 126080 storsec.mbn
27.05.2022 18:50 4189312 tz.mbn
27.05.2022 18:50 2092160 uefi_sec.mbn
27.05.2022 18:57 4189312 xbl.elf
27.05.2022 18:57 126080 xbl_config.elf
Does somebody has any idea?
No ideas, also i never managed to get the moto downoad mode tool work
Iam now in Fastboot Mode, i hope i can boot twrp and i can flash my backup from stockfw or lineageos or the newest stock fw. What is the best way?
I use the blankflash from the racer, that phone has the same SM7250
(I have thw XT2075-3/nairo):
E:\Motorola_nairo\download\racer\blankflash_racer_RPD31.Q4U-39-26-17>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM4
[ 0.031] Detecting device
[ 0.047] ...cpu.id = 286 (0x11e)
[ 0.047] ...cpu.sn = +++++++++
[ 0.054] Opening singleimage
[ 0.058] Loading package
[ 0.067] ...filename = pkg.xml
[ 0.070] Loading programmer
[ 0.073] ...filename = programmer.elf
[ 0.077] Sending programmer
[ 0.251] Handling things over to programmer
[ 0.251] Identifying CPU version
[ 0.251] Waiting for firehose to get ready
[ 3.314] ...SM_SAIPAN 2.0
[ 3.314] Determining target secure state
[ 3.329] ...secure = yes
[ 3.392] Configuring device...
[ 3.392] Skipping UFS provsioning as target is secure
[ 3.392] Configuring device...
[ 3.548] Flashing GPT...
[ 3.548] Flashing partition with gpt.bin
[ 3.548] Initializing storage
[ 3.626] ...blksz = 4096
[ 4.111] Re-initializing storage...
[ 4.111] Initializing storage
[ 4.548] Flashing bootloader...
[ 4.548] Wiping ddr
[ 4.579] Flashing abl_a with abl.elf
[ 4.626] Flashing aop_a with aop.mbn
[ 4.673] Flashing qupfw_a with qupfw.elf
[ 4.704] Flashing tz_a with tz.mbn
[ 4.939] Flashing hyp_a with hyp.mbn
[ 4.986] Flashing devcfg_a with devcfg.mbn
[ 5.017] Flashing keymaster_a with keymaster.mbn
[ 5.064] Flashing storsec_a with storsec.mbn
[ 5.095] Flashing uefisecapp_a with uefi_sec.mbn
[ 5.236] Flashing prov_a with prov64.mbn
[ 5.267] Flashing xbl_config_a with xbl_config.elf
[ 5.298] Flashing xbl_a with xbl.elf
[ 5.564] Rebooting to fastboot
[ 5.564] Total time: 5.564s
1.692 / 5.000
Hello, I was successful now I have a working phone again. But it didn't work with the Motorola Rescue Tool. I used this to download the latest firmware. Then I flashed this firmware with Fastboot and the script from (https://kfhost.net/flashfile):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
echo -----------------------------------------------------------------------------------------------
echo English - Process concluded!
echo Português - Processo concluído!
echo English - Press any key to restart the phone!
echo Português - Pressione qualquer tecla para reiniciar o celular!
echo -----------------------------------------------------------------------------------------------
pause
fastboot reboot
exit
I hope someone else can use it ;-).
Germanandroidplayer said:
Iam now in Fastboot Mode, i hope i can boot twrp and i can flash my backup from stockfw or lineageos or the newest stock fw. What is the best way?
I use the blankflash from the racer, that phone has the same SM7250
(I have thw XT2075-3/nairo):
E:\Motorola_nairo\download\racer\blankflash_racer_RPD31.Q4U-39-26-17>.\qboot.exe blank-flash
< waiting for device >
Motorola qboot utility version 3.86
[ 0.000] Opening device: \\.\COM4
[ 0.031] Detecting device
[ 0.047] ...cpu.id = 286 (0x11e)
[ 0.047] ...cpu.sn = +++++++++
[ 0.054] Opening singleimage
[ 0.058] Loading package
[ 0.067] ...filename = pkg.xml
[ 0.070] Loading programmer
[ 0.073] ...filename = programmer.elf
[ 0.077] Sending programmer
[ 0.251] Handling things over to programmer
[ 0.251] Identifying CPU version
[ 0.251] Waiting for firehose to get ready
[ 3.314] ...SM_SAIPAN 2.0
[ 3.314] Determining target secure state
[ 3.329] ...secure = yes
[ 3.392] Configuring device...
[ 3.392] Skipping UFS provsioning as target is secure
[ 3.392] Configuring device...
[ 3.548] Flashing GPT...
[ 3.548] Flashing partition with gpt.bin
[ 3.548] Initializing storage
[ 3.626] ...blksz = 4096
[ 4.111] Re-initializing storage...
[ 4.111] Initializing storage
[ 4.548] Flashing bootloader...
[ 4.548] Wiping ddr
[ 4.579] Flashing abl_a with abl.elf
[ 4.626] Flashing aop_a with aop.mbn
[ 4.673] Flashing qupfw_a with qupfw.elf
[ 4.704] Flashing tz_a with tz.mbn
[ 4.939] Flashing hyp_a with hyp.mbn
[ 4.986] Flashing devcfg_a with devcfg.mbn
[ 5.017] Flashing keymaster_a with keymaster.mbn
[ 5.064] Flashing storsec_a with storsec.mbn
[ 5.095] Flashing uefisecapp_a with uefi_sec.mbn
[ 5.236] Flashing prov_a with prov64.mbn
[ 5.267] Flashing xbl_config_a with xbl_config.elf
[ 5.298] Flashing xbl_a with xbl.elf
[ 5.564] Rebooting to fastboot
[ 5.564] Total time: 5.564s
Click to expand...
Click to collapse
Hey, can I ask you how did you manage to unbrick it? My phone doesn't get recognized via fastboot. It seems dead but when I connect it to the pc, it gets recognized as "Qualcomm HS-USB QDLoader 9008"
Ok I cannot believe it was so stupid, it didn't work because I had to long press power button + volume down while executing the blank flash file, as said in this post (I put the screenshot below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OK, I hope your problem is solved and your phone is working again? It's been some time now. I don't remember having to hold down any keys. My problem with the blank flash file was that the signatures were probably wrong. So I grabbed an empty flash file from the other phone that has the same processor.
I have the same problem but with XT2075-5 (US retail).
Hard bricked it after flashing Lineage OS 19.1, which is Android 12. (Brick was not the fault of Lineage, I flashed the radio from the stock ROM and it bricked the device - very stupid - did this because the device did not work with Verizon after flashing Lineage, but obviously did not know wtf I was doing)
I have tried both of the blankflash files that are currently available on lolinet for nairo, uploaded on 7-20-2022, as well as "blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip" which I found on androidfilehost (https://androidfilehost.com/?fid=14655340768118479195)
All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot. I suspect the blankflash files are from an Android 11 stock ROM, and that I am now screwed.
If anyone else has this situation and figures it out, please share.
officerplonk said:
I have the same problem but with XT2075-5 (US retail).
Hard bricked it after flashing Lineage OS 19.1, which is Android 12. (Brick was not the fault of Lineage, I flashed the radio from the stock ROM and it bricked the device - very stupid - did this because the device did not work with Verizon after flashing Lineage, but obviously did not know wtf I was doing)
I have tried both of the blankflash files that are currently available on lolinet for nairo, uploaded on 7-20-2022, as well as "blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip" which I found on androidfilehost (https://androidfilehost.com/?fid=14655340768118479195)
All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot. I suspect the blankflash files are from an Android 11 stock ROM, and that I am now screwed.
If anyone else has this situation and figures it out, please share.
Click to expand...
Click to collapse
Hi,
Did you read my post from 05/29/2022?
officerplonk said:
I have the same problem but with XT2075-5 (US retail).
Hard bricked it after flashing Lineage OS 19.1, which is Android 12. (Brick was not the fault of Lineage, I flashed the radio from the stock ROM and it bricked the device - very stupid - did this because the device did not work with Verizon after flashing Lineage, but obviously did not know wtf I was doing)
I have tried both of the blankflash files that are currently available on lolinet for nairo, uploaded on 7-20-2022, as well as "blankflash_nairo_from_QPNS30.37-Q3-42-51-2.zip" which I found on androidfilehost (https://androidfilehost.com/?fid=14655340768118479195)
All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot. I suspect the blankflash files are from an Android 11 stock ROM, and that I am now screwed.
If anyone else has this situation and figures it out, please share.
Click to expand...
Click to collapse
I have the same problem with XT2075-3(GB retail with Android 11), I flashed the radio from the US stock ROM and it bricked the device after a restart... So this may not be caused by Android 12. I flashed US radio cause there's no 5G NR reception in China. 'All my attempts appear to be successful, and the device LED goes on for about 10 secs, then it turns off. The phone does not enter fastboot.' - That makes two of us. Now waiting for a solution, too.
Still cannot access fastboot, any one can provide the firehose file, please?
[email protected] said:
Still cannot access fastboot, any one can provide the firehose file, please?
Click to expand...
Click to collapse
See Post #3 and #4 or if this dont work #6
Here is the link again: https://mirrors.lolinet.com/firmware/motorola/nairo
This didn't work on my Nairo. I'm using this (see below) because Nairo and Racer should contain the same CPU/SOC.
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
After loading blankfile you have to create new partitons and flash the stock ROM
you can use the script from here (https://kfhost.net/flashfile). The Stock ROM you can get with the Motorola Rescue Tool.