Related
Hi Everyone
I have a Telstra HTC One XL which is unlocked, rooted and running Viper 3.2.7 - it has been working perfectly for a year.
On Friday it reported that the SD card was mounted read only - I did some forum searches and have tried mounting & scanning the SD card which didn't resolve anything. I have a backup of my data so thought that I'd wipe the device and upgrade to the latest ROM (v4.2.0)
However, the device is in permanent read only mode. I can (via Windows) apparently copy the ROM zip file to the device but it is never really there - disconnect the phone and re-connect and it's as if the copy had never happened.
I can also delete files but, after disconnecting and reconnecting, they're magically back
Deleting files via TWRP doesn't work either (same result)
Re-installing the old ROM (still on the SD card) doesn't happen either - the install says complete but even having told it to not keep my settings/data/programs everything is still there
I've tried sideloading the ROM update (says complete but actually isn't)
Wiping the system, caches etc via TWRP again reports as successful but isn't
I can't update TWRP, although it says OKAY
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.0-evita.img
sending 'recovery' (8176 KB)...
OKAY [ 1.030s]
writing 'recovery'...
OKAY [ 3.323s]
finished. total time: 4.368s
I can't manually update the boot.img, although again it says OKAY
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
sending 'boot' (6054 KB)...
OKAY [ 0.889s]
writing 'boot'...
OKAY [ 2.168s]
finished. total time: 3.073s
I've tried a couple of versions of fastboot as well.
Given that there's nothing I want on the phone and it's just not working correctly, I'm happy to do/try anything at all but have now run out of ideas - does anyone have any thoughts for me?
Many thanks in advance
David
tried to post in the venue area but got a pop up saying i had to post here. so, heres the situation.
i have a retail dell venue 7, i dont know the model as i cant boot in to it (thus the problem) i did "not" try to root the device, 1.5 years old, checked some messages, locked it, came back later, it wouldnt unlock, did a hard shut down, went to start it up and it just sits at the dell logo. so heres what ive tried so far.
1. if i power on i get a quick USB logo flash.
2. if i power on with usb cable hooked to pc the USB logo stays on the screen.
3. if i go in to droid boot and try recovery it reboots to the dell logo and just sits there.
im legally blind and am having a bit of trouble getting around here but ive tried the "IntelAndroid-FBRL-07-24-2015"
using the above, if i boot in to droid boot it shows up as "android phone" i have to install the adb driver each and every time (windows 8.1) i dont mind that. the above sees the tablet and even issues commands. the tablet reboots and i get a logo with a hat, but it goes no further. if i hold power up and connect to the pc it shows up as a "CloverviewPlus Device" under intel Soc.
this is what "IntelAndroid-FBRL-07-24-2015" shows when i try to do a "5 cwm" then a "T3"
***********************************************************************
FASTBOOT TETHERED RECOVERY LAUNCHER 07-24-2015
***********************************************************************
=======================================================================
DEVICE STATUS: FASTBOOT-ONLINE
DEVICE INFORMATION: DellVenue7000143194 fastboot
=======================================================================
copy needed files to our device
target reported max download size of 1322942464 bytes
sending '/tmp/recovery.zip' (3623 KB)...
OKAY [ 0.887s]
writing '/tmp/recovery.zip'...
OKAY [ 0.686s]
finished. total time: 1.573s
target reported max download size of 1322942464 bytes
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.604s]
writing '/tmp/recovery.launcher'...
OKAY [ 0.686s]
finished. total time: 1.291s
target reported max download size of 1322942464 bytes
sending '/sbin/partlink' (349 KB)...
OKAY [ 0.571s]
writing '/sbin/partlink'...
OKAY [ 0.687s]
finished. total time: 1.259s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
(bootloader) Stop partitioning
(bootloader) Stop partitioning
A
FAILED (unknown status code)
finished. total time: 0.635s
---------------------------------------
at which point the tablet reboots, but just sits there with that hat thing.
i dont care if i loose data, id just like to get this tablet back in working order. unfortunitly i have no idea how to do that. im comfortable with the command line but may need a bit of hand holding (i.e. step by steps, ive looked at the wiki but i cant figure it out sadly)
after digging through some emails and finding the service tag, i can now update this to say its a DELL venue 7 3770. and ive still had no luck.
so, i downloaded kernel.tar.gz from Venue_7_3730_CloverTrail_plus/ (yeah i fat fingered the model number above, my bad)
1st sign this wouldnt work? when i unzipped with 7zip i got an error about files all ready existing, not possible since it was an empty folder, but i went ahead any way. installed virtualbox, ubuntu, got that all set up. tried to run from in there and got a boat load of "read only" errors (even though other write/read tests worked fine)
so i figured, ok, lets just keep it "in the box" so to speak, made a folder with in ubuntu, redownloaded said file. used file manager to unpack it only to get an error about "no such file or directory" eh?
so i went over to terminal and tried to unzip it again, this time getting a "not a gunzip file" error, do what?
all of my googling seems to say im hosed any way as every thing i read says you need a good clean copy of /system from your "phone" (what , no one ever does this with a tablet?) to build the rom, kinda defeats the purpose of releasing the source dont it?
oh well, ive tried all i can try and with no one around here pointing me in the right direction, i guess i have a nice paper weight.
I was trying to flash stock rom in my Pixel 2 which had the march update and I am getting the error
ERROR: LoadImageAndAuth Failed: Load Error
Click to expand...
Click to collapse
Here's what happened:
I unpacked my phone, updated it to the latest OTA version available (the March version) using the OS update function. Then I followed a tutorial in YouTube to root the phone using Magisk (https://www.youtube.com/watch?v=M-0NIUUvYI4). It worked well, I had root access and I could boot into the phone as normal. All this was done using the latest platform tools, image and usb drivers
I then decided to recheck for updates. A new update appeared, the one from April. I tried to install it and I couldn't. I figured out it was because of the root. I tried to uninstall Magisk using the restore stock image (or similar, can't remember the name of the option) but said "Stock backup does not exist" So I decided to flash the factory image of this April update (I verified it was the correct one for my device. Maybe it could have been the March update, but it has been a wild ride and I can't think clearly anymore) and after that my phone won't boot back up, it is stuck in the bootloader. Sometimes if I use the flash-all of the factory image or modify the script to change the order of the flashing of images I can get to the screen with the Google words in a white background and an open padlock, but that's it. The bootloader is still unlocked
How could I troubleshoot if it is a hardware issue? How could it had damaged itself so quickly, literally I used it only for 30 min before attempting the root process. Sometimes I also do get ERROR: Slot Unbootable, but if I reflash with the script I usually end with the above error
I tried following the instruction to run the deuce script modifying the script such that:
Commented out the unlock_critical as
Code:
::fastboot flashing unlock_critical
the boot slots are as follows: https://pastebin.com/NTapvzXV
I ran getvar all if it is useful: https://pastebin.com/bKA20Jvy
But I am still getting the same error. I am desperate to fix since I haven't even used the phone at all and it is completely new.
Please, I need your help urgently
Here is the output from the flashing process: https://pastebin.com/AwiAyrWh
I think the problem seems that I am unable to mount the vendor partition:
When I try sending the command manually I get this:
Code:
fastboot flash vendor_a vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.130s]
sending 'vendor_a' (354100 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 8.012s
When I try wiping or something along those lines with TWRP it says
Failed to mount '/vendor' (Invalid argument)
Click to expand...
Click to collapse
Thank you
Be sure you have the very latest platform tools for your OS and try again. https://developer.android.com/studio/releases/platform-tools.html
westhaking said:
Be sure you have the very latest platform tools for your OS and try again. https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Unfortunately when I started all this process that was the first I did, download everything anew from the official sites.
Download the April factory image and try again. I had this same issue due to not using the most up to date platform tools and not placing the unzipped contents of the april update in the platform tools folder.
smokie75 said:
Download the April factory image and try again. I had this same issue due to not using the most up to date platform tools and not placing the unzipped contents of the april update in the platform tools folder.
Click to expand...
Click to collapse
That's exactly what I did unfortunately. The thing is I am unable to flash the vendor image.
Try a different USB port on your computer, preferably a USB 2 port instead of a USB 3 port.
Telperion said:
Try a different USB port on your computer, preferably a USB 2 port instead of a USB 3 port.
Click to expand...
Click to collapse
Would that help with problem of being unable to mount the vendor partition? I tried but the same problem persists
damnrecoverymode said:
Would that help with problem of being unable to mount the vendor partition? I tried but the same problem persists
Click to expand...
Click to collapse
Potentially, there are reports of sporadic issues with USB ports and USB cables around the forums.
Flashback the March firmware. Its gives you error because your not using the right firmware that was installed in your pixel.
Sent from my [device_name] using XDA-Developers Legacy app
Mangtas_666 said:
Flashback the March firmware. Its gives you error because your not using the right firmware that was installed in your pixel.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
By firmware do you mean the factory image? If so already tried to do that with Deuces script, that is: Download latest platforms tools and the correct factory image, then extract the first .zip and try the flash-all.bat, then when that doesn't work unzip the internal zip and try the script but to no avail. In both cases, as I said, I am unable to mount the vendor partition.
But if by firmware you mean something different, could you please point me in the right direction to download and install it?
I have seen this (https://developers.google.com/android/drivers#walleye), what is that vendor image in there?
Thank you for your help
I didn't use the deuces tool i just copy the necessary files direct to the platform tools folder then edit flashall.bat delete the -w if you dont want to wipe your device. Grab the march firmware at google site then unzip it copy all at the platform tools folder go to fastboot then click flashall.bat
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 06:18 PM ---------- Previous post was at 05:56 PM ----------
Grab it here...https://developers.google.com/android/images
Sent from my [device_name] using XDA-Developers Legacy app
Mangtas_666 said:
I didn't use the deuces tool i just copy the necessary files direct to the platform tools folder then edit flashall.bat delete the -w if you dont want to wipe your device. Grab the march firmware at google site then unzip it copy all at the platform tools folder go to fastboot then click flashall.bat
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 06:18 PM ---------- Previous post was at 05:56 PM ----------
Grab it here...https://developers.google.com/android/images
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes that's what I've been doing to no avail :crying:
damnrecoverymode said:
Yes that's what I've been doing to no avail :crying:
Click to expand...
Click to collapse
Can you go to fastboot? What does it say when you try to flash back to stock?
Sent from my [device_name] using XDA-Developers Legacy app
Mangtas_666 said:
Can you go to fastboot? What does it say when you try to flash back to stock?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
What it says is what is in the first post. You can check all the information I've been able to recompile. But I think the key problem is here:
fastboot flash vendor_a vendor.img
target reported max download size of 536870912 bytes
erasing 'vendor_a'...
OKAY [ 0.130s]
sending 'vendor_a' (354100 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 8.012s
Click to expand...
Click to collapse
damnrecoverymode said:
What it says is what is in the first post. You can check all the information I've been able to recompile. But I think the key problem is here:
Click to expand...
Click to collapse
Try different pc and cable
Sent from my [device_name] using XDA-Developers Legacy app
Try switching to system B? Could also try uninstalling your usb driver and rebooting, then reinstalling it. Also if youre using something like LibUsb, that can mess with adb sometimes.
Do not use toolkits or whatnot. Download everything yourself, from official google links.
Platform tools: https://developer.android.com/studio/releases/platform-tools.html
Firmware: https://dl.google.com/dl/android/aosp/walleye-opm2.171019.029-factory-41296266.zip
I, personally would NOT try flashing an older firmware as these phones have rollback protection. The newest firmware should work, I just used it to return to stock to get the newest security updates.
I'm 99% sure this is a port / cable / driver issue, try all of this on a different computer with USB 2 ports and a fresh driver setup.
Telperion said:
I'm 99% sure this is a port / cable / driver issue, try all of this on a different computer with USB 2 ports and a fresh driver setup.
Click to expand...
Click to collapse
Sure it was. Had to ask to a neighbor his computer and cable to test and it really worked! Thank you for your help mate!
Telperion said:
I'm 99% sure this is a port / cable / driver issue, try all of this on a different computer with USB 2 ports and a fresh driver setup.
Click to expand...
Click to collapse
I've also experienced fastboot issues with the Pixel 2.
After a few successful flashes using my laptop, I started to hit errors when flashing the system partition.
I now check for fastboot broken-ness by repeatedly running "fastboot getvar all" (say, 10 times).
If "getvar" fails, then it is time to try flashing using another machine.
Possible solution
Has the OP ever found a solution to his problems? I stumbled upon this thread with similar issues, by searching for "FAILED (Write to device failed (Unknown error))". My problem looks like this:
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 12.198s]
Writing sparse 'system_a' 1/5 OKAY [ 0.000s]
Sending sparse 'system_a' 2/5 (524284 KB) OKAY [ 14.210s]
Writing sparse 'system_a' 2/5 OKAY [ 0.000s]
Sending sparse 'system_a' 3/5 (524284 KB) OKAY [ 14.160s]
Writing sparse 'system_a' 3/5 OKAY [ 0.000s]
Sending sparse 'system_a' 4/5 (521176 KB) FAILED (Write to device failed (Unknown error))
Click to expand...
Click to collapse
After a few shots in the dark, I managed to resolve the issue by reducing the sparse file size, specifically this fastboot option:
-S SIZE[K|M|G] Break into sparse files no larger than SIZE.
Click to expand...
Click to collapse
Using -S 256M did it for me (the default was just short of 512MB). So the last line in my flash-all.sh looked like this in the end:
fastboot -S 256M update image-walleye-pq2a.190205.002.zip
Click to expand...
Click to collapse
I'm sure theres no helping me, beings how im new to this, i run linux mint, not windows, and i made bad decisions to get here. i recently got a new moto g7 power with full intentions on using it as my guinea pig while i still had my old phone working. my plan was to not even install a sim card into my g7 until i had it properly rooted. i looked through all sorts of tutorials and tried many different things and learned alot along the way. long story short, ive been using the linux command line to do everything. i got my bootloader unlocked using the code that i requested from motorola. then i downloaded the 2 g7 ocean files, zip and img. i pushed the zip file into the /data/ folder, fastbooted from the .img file, got to twrp/ from there i went to advanced, install recovery Ramdisk, navigated to data, and selected the .img file. i tried this twice with no success, it would just boot normally and the twrp app wouldnt allow me to install the zip file, says its not rooted. so the last time i tried, i dont remember exactly how i did it but within the twrp recovery menu i found a way to boot slot b, but slot a was already selected by default. my thought was that i had installed the zip on slot b and not slot a. selected slot b, my phone shut off, and now nothing. just blank, wont even light a light, even if i plug it in.
i know that i shouldnt have been messing around with stuff i dont know much about, but hey, it beats watching the news right now, and that is why i didnt buy a 1000 dollar phone. also, i bought this phone from amazon prime, but im not sure id sleep good at night sending it back knowing i damaged it myself, however that was recommended to me. Thank you for any help/ info i may get.
Blank flash
jhomolac said:
I'm sure theres no helping me, beings how im new to this, i run linux mint, not windows, and i made bad decisions to get here. i recently got a new moto g7 power with full intentions on using it as my guinea pig while i still had my old phone working. my plan was to not even install a sim card into my g7 until i had it properly rooted. i looked through all sorts of tutorials and tried many different things and learned alot along the way. long story short, ive been using the linux command line to do everything. i got my bootloader unlocked using the code that i requested from motorola. then i downloaded the 2 g7 ocean files, zip and img. i pushed the zip file into the /data/ folder, fastbooted from the .img file, got to twrp/ from there i went to advanced, install recovery Ramdisk, navigated to data, and selected the .img file. i tried this twice with no success, it would just boot normally and the twrp app wouldnt allow me to install the zip file, says its not rooted. so the last time i tried, i dont remember exactly how i did it but within the twrp recovery menu i found a way to boot slot b, but slot a was already selected by default. my thought was that i had installed the zip on slot b and not slot a. selected slot b, my phone shut off, and now nothing. just blank, wont even light a light, even if i plug it in.
i know that i shouldnt have been messing around with stuff i dont know much about, but hey, it beats watching the news right now, and that is why i didnt buy a 1000 dollar phone. also, i bought this phone from amazon prime, but im not sure id sleep good at night sending it back knowing i damaged it myself, however that was recommended to me. Thank you for any help/ info i may get.
Click to expand...
Click to collapse
Most likely it's in Emergency download mode (EDL)
You will need a blankflash, several threads on this.
There's one here, that may work.
https://mirrors.lolinet.com/firmware/moto/ocean/blankflash/
Sent from my Moto E (4) using Tapatalk
EDL mode even though there is no sign of life whatsoever?
jhomolac said:
EDL mode even though there is no sign of life whatsoever?
Click to expand...
Click to collapse
There won't be anything on the phone, just a black screen, but it should show up on a PC's list of connected devices.
Sent from my Moto E (4) using Tapatalk
jhomolac said:
EDL mode even though there is no sign of life whatsoever?
Click to expand...
Click to collapse
Some phones will display a charge light some won't like he said it's in edl mode the PC sould display it and u should hear it make sound when u plugs the phone into PC on windows in not sure on Linux machine should b perty much the same on that aspect .One thing u might have to get different blank flashes for the different updates .If don't go the first time try again good luck
Thank you guys, i appreciate your time. sounds like i have to do some more research about flashing a motorola from linux. im somewhat new to linux as well.
jhomolac said:
Thank you guys, i appreciate your time. sounds like i have to do some more research about flashing a motorola from linux. im somewhat new to linux as well.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/ocean/ here is a blank flash that should get u going dose the PC recognise ur phone when u plug it in if dose open terminal an PC type fastboot devices if it sees it your in luck I can typ fastboot boot (the name of ur recovery) if it boot into twrp then u might b able to switch it to a slot. There is comands for fastboot to switch but I don't know them
My computer does not notify me when I plug in my phone. But I don't remember it doing that even when I used it before.thank you.
You might need to charge the phone. With a blank/black screen it can appear off when it's not. Thus draining the phone completely. It widely suggested to charge phones to at least 80% before tweaking/rooting.
I will feel like a real dummy if that's the case. It is now on the factory supplies charger. Haha. Crossing my fingers. Thank you
If I use command lsusd in terminal, my phone pops up as a Qualcomm wireless router. Command fastboot devices brings up nothing
jhomolac said:
If I use command lsusd in terminal, my phone pops up as a Qualcomm wireless router. Command fastboot devices brings up nothing
Click to expand...
Click to collapse
It's in edl mode, use the blankflash
Sent from my Moto E (4) using Tapatalk
I've never done a blank flash before, I thought it was done by using: fastboot flash command. But it doesn't seem possible if: fastboot devices doesn't bring everything up. I am on linux by the way
jhomolac said:
I've never done a blank flash before, I thought it was done by using: fastboot flash command. But it doesn't seem possible if: fastboot devices doesn't bring everything up. I am on linux by the way
Click to expand...
Click to collapse
You need QPST to interface with EDL mode. I don't know if anything in here works on Linux, but it definitely works on Windows 10.
QPST Utilities
decided to give this another try. i have managed to get a little further, however this is where i am getting stuck. i wish i was more savy with this stuff. any chance anyone could help me with this?
also, is it nessecary to have an sd card in the device when i do this?
blankflash_from_QCO30.85-18]# /home/joel/Desktop/blankflash_from_QCO30.85-18/blank-flash.sh
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.005] ...cpu.id = 186 (0xba)
[ 0.005] ...cpu.sn = 2335135194 (0x8b2f55da)
[ 0.005] Opening singleimage
[ 0.005] Loading package
[ 0.013] ...filename = singleimage.pkg.xml
[ 0.018] Loading programmer
[ 0.019] ...filename = programmer.mbn
[ 0.019] Sending programmer
[ 0.318] Handling things over to programmer
[ 0.318] Identifying CPU version
[ 0.324] Waiting for firehose to get ready
[ 3.338] ...MSM8953 1.0
[ 3.338] Determining target secure state
[ 3.343] ...secure = yes
[ 3.387] Configuring device...
[ 3.394] Flashing GPT...
[ 3.394] Flashing partition with gpt.bin
[ 3.400] Initializing storage
[ 5.763] Target NAK!
[ 5.763] ...num_partition_sectors=61071360
[ 5.763] ...SECTOR_SIZE_IN_BYTES=512
[ 5.763] ...num_physical_partitions=3
[ 5.763] ...OEM_ID=74
[ 5.763] ...Product name=hB8aP>
[ 5.763] ...XML (0 bytes) not validated
[ 5.763] 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
[ 5.763] Check qboot_log.txt for more details
[ 5.763] Total time: 5.763s
FAILED: qb_flash_singleimage()->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
sd_shadow said:
There won't be anything on the phone, just a black screen, but it should show up on a PC's list of connected devices.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
What do I do if it doesn't?
I tried all the possible button combinations but still nothing.
uwucake2020 said:
What do I do if it doesn't?
I tried all the possible button combinations but still nothing.
Click to expand...
Click to collapse
Is there anything on the phone screen?
sd_shadow said:
Is there anything on the phone screen?
Click to expand...
Click to collapse
There isn't anything, and it doesn't seem to be in EDL mode. (I checked in the device manager)
uwucake2020 said:
There isn't anything, and it doesn't seem to be in EDL mode. (I checked in the device manager)
Click to expand...
Click to collapse
Spoiler: It may be hidden in Ports like this
{
"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"
}
It looks something like this: prog_emmc_firehose_8909_alc2.mbn
I don't know exactly what I did. I just flashed TWRP and booted in to it just to see if it was working, When I was done, I went to choose a partition to boot into, the first one said it had no operating system, I chose the second one which TWRP said had an OS. After that, the phone went dead and won't turn on. When I connect the phone to my PC, and go into device manager, the phone is listed as:
Qualcomm HS-USB QDLoader 9008. ADB doesn't see the phone, but QFIL does. I need the programmer file as well as a "rawprogram" file and a "patch0" file to flash the phone with QFIL.
Before I flashed TWRP, I unlocked the bootloader. I've unlocked the bootloader and flashed TWRP before and never had this happen.
Does a brand new phone only have the OS installed on one partition?
Could the programmer file be somewhere in the rom? In the sparsechunk files maybe?
Can the phone charge when its in this comatose state?
My nightmare began on Sunday night. I was waiting for a bus and a girl asked me to use the phone. While she was pretending to dial, a guy who she said was her brother(but probably wasn't) starts walking towards us. When he got close, she gave him the phone and they start running. I chased them and the guy says give me the passcode or I'll smash the phone. I said no and he smashed it on the ground and throws it over a fence. Then they ran back to the bus stop and stole my bike and ran away. I was able to recover the SD and SIM cards the next day. I have my phone backed up on the SD card.
What do you guys think their plan was? To steal my bicycle or my phone? Surely they knew the phone was useless without access to it. I could've rode away on my bike instead of chasing them. Before this all happened, they were standing across the street apparently casing me. I was doing something on my phone, so I didn't really notice them. Its not like they were professional thieves. They were just a couple of black kids around 20 years old from the ghetto. If they had a plan, it didn't make sense.
Heat84 said:
It looks something like this: prog_emmc_firehose_8909_alc2.mbn
I don't know exactly what I did. I just flashed TWRP and booted in to it just to see if it was working, When I was done, I went to choose a partition to boot into, the first one said it had no operating system, I chose the second one which TWRP said had an OS. After that, the phone went dead and won't turn on. When I connect the phone to my PC, and go into device manager, the phone is listed as:
Qualcomm HS-USB QDLoader 9008. ADB doesn't see the phone, but QFIL does. I need the programmer file as well as a "rawprogram" file and a "patch0" file to flash the phone with QFIL.
Before I flashed TWRP, I unlocked the bootloader. I've unlocked the bootloader and flashed TWRP before and never had this happen.
Does a brand new phone only have the OS installed on one partition?
Could the programmer file be somewhere in the rom? In the sparsechunk files maybe?
Can the phone charge when its in this comatose state?
My nightmare began on Sunday night. I was waiting for a bus and a girl asked me to use the phone. While she was pretending to dial, a guy who she said was her brother(but probably wasn't) starts walking towards us. When he got close, she gave him the phone and they start running. I chased them and the guy says give me the passcode or I'll smash the phone. I said no and he smashed it on the ground and throws it over a fence. Then they ran back to the bus stop and stole my bike and ran away. I was able to recover the SD and SIM cards the next day. I have my phone backed up on the SD card.
What do you guys think their plan was? To steal my bicycle or my phone? Surely they knew the phone was useless without access to it. I could've rode away on my bike instead of chasing them. Before this all happened, they were standing across the street apparently casing me. I was doing something on my phone, so I didn't really notice them. Its not like they were professional thieves. They were just a couple of black kids around 20 years old from the ghetto. If they had a plan, it didn't make sense.
Click to expand...
Click to collapse
Your device is in EDL Mode, it will charge in this state, also there is very little drain on the battery in this mode.
Motorola bundles these files as blankflash(es)
Try these
https://mirrors.lolinet.com/firmware/moto/racer/blankflash/
When you install a rom on a Moto device with a/b system you need you to follow this
Pre-install instructions
sd_shadow said:
Your device is in EDL Mode, it will charge in this state, also there is very little drain on the battery in this mode.
Motorola bundles these files as blankflash(es)
Try these
https://mirrors.lolinet.com/firmware/moto/racer/blankflash/
sd_shadow said:
Your device is in EDL Mode, it will charge in this state, also there is very little
Click to expand...
Click to collapse
Click to expand...
Click to collapse
sd_shadow said:
Your device is in EDL Mode, it will charge in this state, also there is very little drain on the battery in this mode.
Motorola bundles these files as blankflash(es)
Try these
https://mirrors.lolinet.com/firmware/moto/racer/blankflash/
Click to expand...
Click to collapse
When I run blank-flash.bat, I get:
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
I don't know how the double quote happened and I don't know how to view the raw code to delete it right.
Heat84 said:
When I run blank-flash.bat, I get:
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
I don't know how the double quote happened and I don't know how to view the raw code to delete it right.
Click to expand...
Click to collapse
Try this
Moto G6 XT1925-6 "bricked" from normal use--blankflash not working
Hi all, My girlfriend's Moto G6 XT1925-6 (purchased via Best Buy, never rooted/modded) got slow one day, I recommended rebooting and then it never came back. The only signs of life are that when plugged into a computer or charger. the white...
forum.xda-developers.com
sd_shadow said:
Try this
Moto G6 XT1925-6 "bricked" from normal use--blankflash not working
Hi all, My girlfriend's Moto G6 XT1925-6 (purchased via Best Buy, never rooted/modded) got slow one day, I recommended rebooting and then it never came back. The only signs of life are that when plugged into a computer or charger. the white...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried that and I still get: ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
I read somewhere that Windows could somehow be interfering with the process. How can I do this in Linux? How do I get Linux Mint to see the phone and how do I know that its being seen?
I never expected to get help this fast! Thanks everybody.
So nobody knows where to find the files I need for QFIL?
Here is a page that talks about Sahara protocol errors and how to fix them. I'm not exactly sure which one applies to me: https://blog.hovatek.com/how-to-fix-sahara-fail-error-in-qfil/
I have a rawprogram file and a patch0 file, but I don't know if they will work with my phone.
I figured out that you can reboot the phone by holding the power button(by watching it disappear and reappear in Device Manager). When I run blank-flash.bat right after rebooting, I get this:
Code:
[ -0.000] Opening device: \\.\COM11
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 286 (0x11e)
[ 0.002] ...cpu.sn = 1010000641 (0x3c336301)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.009] ...filename = programmer.elf
[ 0.009] Sending programmer
[ 0.131] Handling things over to programmer
[ 0.131] Identifying CPU version
[ 0.131] Waiting for firehose to get ready
[ 3.213] ...SM_SAIPAN 2.0
[ 3.214] Determining target secure state
[ 3.219] ...secure = yes
[ 3.307] Configuring device...
[ 3.317] Skipping UFS provsioning as target is secure
[ 3.317] Configuring device...
[ 3.483] Flashing GPT...
[ 3.483] Flashing partition with gpt.bin
[ 3.485] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->find_first_package()->not found
[ 3.486] Check qboot_log.txt for more details
[ 3.486] Total time: 3.487s
[ 3.487]
[ 3.487] qboot version 3.86
[ 3.487]
[ 3.487] DEVICE {
[ 3.487] name = "\\.\COM11",
[ 3.487] flags = "0x144",
[ 3.487] addr = "0x28FD74",
[ 3.487] sahara.current_mode = "0",
[ 3.487] api.buffer = "0x2570020",
[ 3.487] cpu.serial = "1010000641",
[ 3.487] cpu.id = "286",
[ 3.487] cpu.sv_sbl = "0",
[ 3.487] cpu.name = "SM_SAIPAN",
[ 3.487] storage.type = "UFS",
[ 3.487] sahara.programmer = "programmer.elf",
[ 3.487] module.firehose = "0x24D1248",
[ 3.487] api.firehose = "0x67D948",
[ 3.487] cpu.ver = "512",
[ 3.487] cpu.vername = "2.0",
[ 3.487] fh.max_packet_sz = "1048576",
[ 3.487] fh.storage_inited = "1",
[ 3.487] }
[ 3.487]
Now I get a different error which you see at 3.485.
I didn't feel like playing around anymore so I took it to Best Buy(where I bought it from).
While they wouldn't fix it, they actually allowed me to exchange it for another one. I chose an open box one (that was probably returned for a stupid reason since its in brand new condition) so I wouldn't have to wait a week for a new one. I also got a $74 refund(to make the exchange even). I never thought I would make out this good(especially since I didn't choose the tech support option when I bought it).
What's gonna happen with the one I gave them? Are they gonna send it back to Motorola? Or just recycle/scrap it? It would be really sad not to fix it since just needs a simple re-flash.