I have a moto e4 plus (owens) that had a custom rom flashed on it. After a few days of checking it out i decided to flash my stock backup. Upon doing this it got stock on a loop with (BAD KEY) at the top right, and no boot. Even after half an hour nothing happened.
I tried wiping cache after flashing the backup but still nothing. So i returned to the custom rom.
Again after a few days i really wanted to go back to stock, repeat previous process and still no progress. I decided to flash stock again.
I found directions and firmware, i double checked the version and it matched. I even found posts of successful flashing.
I went ahead and attempted but was greeted by a FAILED notice after attempting to start the process.
It failed to flash gpt.bin.
I looked up solutions but most said to just keep going, stupidly i did. Flashed everything, and everything else said PASS.
Rebooted the phone and......nothing. No boot sequence. No bootloader, No recovery. My computer detects it when i plug it in, but i can't access anything. At the moment im stuck using my Wife's ZTE Zmax 2, and my god i already miss my phone.
Does anyone have any sort of advice that could help, i believe there may be a chance since it does get detected by my phone, but im not to sure at the moment.
And i have succesfully flashed stock roms on my previous 3 phones, so i thought this time would be no issue.
Thanks in advance.
PV.Srg said:
Does anyone have any sort of advice that could help, i believe there may be a chance since it does get detected by my phone, but im not to sure at the moment.
Thanks in advance.
Click to expand...
Click to collapse
Just a thought, try using RSDLIte (http://rsdlite.com/rsd-lite-download/) instead of Fastboot. At least one other user on XDA said that was the only way that he could get to write. Not sure why this would be, but what have you got to lose?
Try letting the battery run down and then charging to get into Fastboot mode on your phone.
koop1955 said:
Just a thought, try using RSDLIte (http://rsdlite.com/rsd-lite-download/) instead of Fastboot. At least one other user on XDA said that was the only way that he could get to write. Not sure why this would be, but what have you got to lose?
Try letting the battery run down and then charging to get into Fastboot mode on your phone.
Click to expand...
Click to collapse
same problem with e4 plus and is now hard bricked. computer recognizes it but says I need some driver is cant find and wont power up or read. downloading rsd lite and still no luck I need help
I have the same issue. We messed with the boot partition, so our computer will not recognize the device in fastboot mode. My PC will detect it as 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"
}
Battery died and everything, and tried to boot to fastboot but it wouldn't let me do it. @koop1955, RSD Lite won't detect the phone either.
Josh'sDroid said:
I have the same issue. We messed with the boot partition, so our computer will not recognize the device in fastboot mode. My PC will detect it as this:
Battery died and everything, and tried to boot to fastboot but it wouldn't let me do it. @koop1955, RSD Lite won't detect the phone either.
Click to expand...
Click to collapse
Dude.. @Funisillegal fixed his!! Be on the lookout for his thread to the fix
@Funisillegal hasn't posted his solution yet
But, if it helps... I had this issue a few years ago with my LG L70. I used Linux to fix it, but since it was a frequent issue with L70's users I had the stock aboot.img for my device.
@bcrichster could you please get the stock aboot.img for us?
@Funisillegal, is this what you did to fix your problem?
Josh'sDroid said:
@Funisillegal hasn't posted his solution yet
But, if it helps... I had this issue a few years ago with my LG L70. I used Linux to fix it, but since it was a frequent issue with L70's users I had the stock aboot.img for my device.
@bcrichster could you please get the stock aboot.img for us?
@Funisillegal, is this what you did to fix your problem?
Click to expand...
Click to collapse
aboot.img.. Isn't that part of the modem images? All available images are in the stock FW
Sent from my Moto E (4) Plus using Tapatalk
bcrichster said:
aboot.img.. Isn't that part of the modem images? All available images are in the stock FW
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
I completely bricked my device lol.
I used a virtual machine, plugged my device to the computer, then selected the device in the virtual machine. Then the command
Code:
sudo gdisk -l /dev/sdb
wouldn't work so I closed VMWare abruptly. Now Windows will "recognize" the device as this:
:crying:
EDIT:
Followed @BoBo Rich's thread and my PC will recognize the device now.
Why'd tf did you close a terminal abruptly? NEVER DO THAT, just wait for the error closing and finish.. Aww chit.. Did ya try to do my fastboot list I posted in AF, with the proper firmware pkg before that gdisk cmd thing??
Josh'sDroid said:
I completely bricked my device lol.
I used a virtual machine, plugged my device to the computer, then selected the device in the virtual machine. Then the command
Code:
sudo gdisk -l /dev/sdb
wouldn't work so I closed VMWare abruptly. Now Windows will "recognize" the device as this:
:crying:
EDIT:
Followed @boborich's thread and my PC will recognize the device now.
Click to expand...
Click to collapse
I'm sorry man, but I can't read Spanish well, Lol.
Sent from my Moto E (4) Plus using Tapatalk
bcrichster said:
Why'd tf did you close a terminal abruptly? NEVER DO THAT, just wait for the error closing and finish..
Click to expand...
Click to collapse
I'm a noob lol
bcrichster said:
Aww chit.. Did ya try to do my fastboot list I posted in AF, with the proper firmware pkg before that gdisk cmd thing??
Click to expand...
Click to collapse
Nope. Phone won't boot on fastboot mode. So, Windows won't detect it as a fastboot device.
bcrichster said:
I'm sorry man, but I can't read Spanish well, Lol.
Click to expand...
Click to collapse
Don't worry. Sometimes my English won't be perfect as I'd wish it was lol.
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20170425
Rsdlite will not work download xiaomiflashtool for communication to boot sector on hard bricked (device that doesn't power on). Brichster has links up to download factory image for our devices. Now this was done on an XT1776 Qualcomm Owens device from boost Mobile. I have been out of town and will not return to my PC where I have location for USB Bulk drivers that will allow your Windows based PC to communicate to you dead device. My wife is currently uploading drivers to my Google drive and once completed I'll update with those. Second is a USB cable you can sacrifice because the next step with be to cut open shielding and jump power wire. That will allow you communication with PC once drivers are installed. It will the start showing which comm your phone is connected to. That's the hardest part. Once your phone is showing logo in middle of screen you have officially connected to deep boot section. Take zip. File you aquirred from brichster and miflashtool will install sorry I could provide drivers at this moment but Microsoft will not find them not will you be able to install them give me a couple of hours to out together tutorial once I receive drivers her in a couple hours
Attaching the blankflash zip file for the board_id=134, and it uses the latest bootloader from june update : "MBM-NG-VBD.40-0-g7ba36". It will work only for board_id=134 (which is the owens platform).
Please search for blankflash to see the exact process involved. This will get you only upto fastboot. After that you need to know how to use fastboot to restore stock (search forums).
In the latest versions of qboot the "programmer.mbn" is inside the "singleimage.bin". You can extract it for use with other tools from "singleimage.bin" if you are familiar with these files.
morchu said:
Attaching the blankflash zip file for the board_id=134, and it uses the latest bootloader from june update : "MBM-NG-VBD.40-0-g7ba36". It will work only for board_id=134 (which is the owens platform).
Please search for blankflash to see the exact process involved. This will get you only upto fastboot. After that you need to know how to use fastboot to restore stock (search forums).
In the latest versions of qboot the "programmer.mbn" is inside the "singleimage.bin". You can extract it for use with other tools from "singleimage.bin" if you are familiar with these files.
Click to expand...
Click to collapse
Where tf you just come from?! Lol, nice find! And thank you greatly for sharing, this should be a great help for ppl
morchu said:
Attaching the blankflash zip file for the board_id=134, and it uses the latest bootloader from june update : "MBM-NG-VBD.40-0-g7ba36". It will work only for board_id=134 (which is the owens platform).
Please search for blankflash to see the exact process involved. This will get you only upto fastboot. After that you need to know how to use fastboot to restore stock (search forums).
In the latest versions of qboot the "programmer.mbn" is inside the "singleimage.bin". You can extract it for use with other tools from "singleimage.bin" if you are familiar with these files.
Click to expand...
Click to collapse
you wouldnt happen to have one of these for a moto e4 plus with msm 8920 would you? i bricked my phone as well.
I keep receiving the following error from the qboot utility. Any suggestions, @morchu?
Code:
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM3
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 134 (0x86)
[ 0.002] ...cpu.sn = 4150985471 (0xf76b02ff)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.008] Loading programmer
[ 0.008] ...filename = programmer.mbn
[ 0.009] Sending programmer
[ 1.011] ERROR: sahara_download()->IO error
[ 1.011] Check qboot_log.txt for more details
[ 1.012] Total time: 1.013s
[ 1.013]
[ 1.013] qboot version 3.40
[ 1.013]
[ 1.013] DEVICE {
[ 1.014] name = "\\.\COM3",
[ 1.014] flags = "0x64",
[ 1.014] addr = "0x61FE5C",
[ 1.014] sahara.current_mode = "0",
[ 1.014] api.buffer = "0xFA6020",
[ 1.014] cpu.serial = "4150985471",
[ 1.014] cpu.id = "134",
[ 1.014] cpu.sv_sbl = "1",
[ 1.014] cpu.name = "MSM8917",
[ 1.014] storage.type = "eMMC",
[ 1.014] sahara.programmer = "programmer.mbn",
[ 1.014] api.bnr = "0x6F6000",
[ 1.014] }
[ 1.014]
[ 1.014]
[ 1.014] Backup & Restore {
[ 1.014] num_entries = 0,
[ 1.014] restoring = "false",
[ 1.014] backup_error = "not started",
[ 1.014] restore_error = "not started",
[ 1.014] }
FAILED: qb_flash_singleimage()->sahara_download()->IO error
lowrck said:
you wouldnt happen to have one of these for a moto e4 plus with msm 8920 would you? i bricked my phone as well.
Click to expand...
Click to collapse
Umm.. That IS for our Moto E4 Plus 'owens' devices
bcrichster said:
Umm.. That IS for our Moto E4 Plus 'owens' devices
Click to expand...
Click to collapse
So which devices have chipset 8917 and which have 8920? I was under the impression all variants of the e4 plus were 8920... However, It appears the blankflash file posted is to service 8917
---------- Post added at 07:08 PM ---------- Previous post was at 07:00 PM ----------
As far as the qualcomm variants that is
wswjw said:
So which devices have chipset 8917 and which have 8920? I was under the impression all variants of the e4 plus were 8920... However, It appears the blankflash file posted is to service 8917
---------- Post added at 07:08 PM ---------- Previous post was at 07:00 PM ----------
As far as the qualcomm variants that is
Click to expand...
Click to collapse
You won't likely find stuff for 8920 because our 8920 is built on an 8937 chip anyways.. Yeah I know, this is strange as hell to me too and I been in Android for a good minute.. Lol. But the program is worth trying because it'll either work or won't.. But is ya do some crazy math.. 8937-8920=8917.. May be weird but still worth a shot cuz it won't brick it further.. You're already in a heap of trouble if you need that tool so, why not? I know someone who used a Xiaomi flashtool to fix his when he flashed a nicklaus FW (MediaTek) on his owens (Qcom).. He had nothing more to lose so it was worth the effort
bcrichster said:
You won't likely find stuff for 8920 because our 8920 is built on an 8937 chip anyways.. Yeah I know, this is strange as hell to me too and I been in Android for a good minute.. Lol. But the program is worth trying because it'll either work or won't.. But is ya do some crazy math.. 8937-8920=8917.. May be weird but still worth a shot cuz it won't brick it further.. You're already in a heap of trouble if you need that tool so, why not? I know someone who used a Xiaomi flashtool to fix his when he flashed a nicklaus FW (MediaTek) on his owens (Qcom).. He had nothing more to lose so it was worth the effort
Click to expand...
Click to collapse
Yeah I will try anything.. I keep getting Sahara download error when I run the qboot blankflash. Ive tried holding vol + and power when executing the bat or just vol + or clicking the bat file continuously as I read in some other moto bricked device threads, but to no avail.
I also tried the mi flash tool but kept getting an error it couldn't find programmer within the firmware path. Which was one I'd downloaded from a post of yours on another forum I believe. I've heard altering the flash cable might b necessary in order to get it to work, but im not certain in what way.
So it's looking pretty bleek at this point but I'm not giving up hope yet lol
wswjw said:
Yeah I will try anything.. I keep getting Sahara download error when I run the qboot blankflash. Ive tried holding vol + and power when executing the bat or just vol + or clicking the bat file continuously as I read in some other moto bricked device threads, but to no avail.
I also tried the mi flash tool but kept getting an error it couldn't find programmer within the firmware path. Which was one I'd downloaded from a post of yours on another forum I believe. I've heard altering the flash cable might b necessary in order to get it to work, but im not certain in what way.
So it's looking pretty bleek at this point but I'm not giving up hope yet lol
Click to expand...
Click to collapse
Sahara?! OMG, get rid of that iCrap and use something better for Android, like Linux.. Since Android is actually MADE from Linux, it's ur best bet. All hate/bias aside tho, Mac is near useless with Android stuff, basically night vs day in comparison. Some stuff works but most won't for Android. Oh, and only use MS Windows for programs that have no Linux equivalent..
Edit: the mi flash tool needs a modified USB cord and Windows OS..
Sent from my Moto E (4) Plus using Tapatalk
Related
So long story short: tried upgrading ICS to JB - fail(missing system apps), tried flashing ICS via fastboot - fail(several images didn't copy due to signature check).
So I have a phone with more files missing than before, causing radio/wireless/bt/camera to fail, and root access only in SS.
I still have use of adb, fastboot, SS, and external-sd.
Q: Requesting data from a functioning ICS to compare with what I have left to discern what was lost. Namely a directory tree with filenames/sizes, output of dmesg and df.
If anyone has a solid lead as how to extract missing files from system.img.ext4, I'm all ears.
t1nk_2 said:
So long story short: tried upgrading ICS to JB - fail(missing system apps), tried flashing ICS via fastboot - fail(several images didn't copy due to signature check).
So I have a phone with more files missing than before, causing radio/wireless/bt/camera to fail, and root access only in SS.
I still have use of adb, fastboot, SS, and external-sd.
Q: Requesting data from a functioning ICS to compare with what I have left to discern what was lost. Namely a directory tree with filenames/sizes, output of dmesg and df.
If anyone has a solid lead as how to extract missing files from system.img.ext4, I'm all ears.
Click to expand...
Click to collapse
Just use rsd lite? It should blow all that away.
Sent from my MotoAHD Maxx
Youngunn2008 said:
Just use rsd lite? It should blow all that away.
Click to expand...
Click to collapse
You would think. However, it doesn't matter whether I use command-line tools or rsdlite5.6/5.7 - there seems to be either a sig check that fails (rsdlite) or file transfer error (command-line). I'm suspecting has something to do with the locked bootloader. It's hard to tell for lack of error code interpretation or lower-level debugging output. It won't even let me install gapps-ics: invalid signature.
I managed to recover root in the OS(cp su to /system/bin), so I can at least modify things outside SS. It may come to the point of manually copying/deleting individual files in /system, as I noticed the official JB update script merely patches what is there and deletes what is deprecated (verifying sigs for everything).
There could be an issue with my linux usb driver, but I never had any problems while taking my mb520 to CM10.
I saw someone offering stock files for those who deleted them, but I also noticed everyone else is nervous about hosting such content anywhere.
I keep noticing a /modem mount, and yet never noticed it while parsing fs. Can anyone verify this exists?
Okay, so just tried fastboot on cmdline again, the max-download-size variable is 31457280 bytes~30Mb. I guess this could be the underlying cause of this mess, since the three files cdrom/system/NON-HLOS are all over that threshold...
I'm going to do some more digging.
...
Here's what led me to the original conclusion:
OKAY [ 2.402s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.677s
Click to expand...
Click to collapse
[Solved] Broken ICS
Tedious procedure averted! :laugh:
rsd 6.1.4 is the only way to go. 5.6/5.7 are almost worthless with this phone. Back to stock, camera/bt/wireless/radio working!
Going to work on consolidating everything I've learned in the last three weeks...
t1nk_2 said:
Tedious procedure averted! :laugh:
rsd 6.1.4 is the only way to go. 5.6/5.7 are almost worthless with this phone. Back to stock, camera/bt/wireless/radio working!
Going to work on consolidating everything I've learned in the last three weeks...
Click to expand...
Click to collapse
Oh yeah that didn't even register. Yeah have to use 6.1.4
Sent from my MotoAHD Maxx
Fix Modem / Baseband JB AT&T ONLY... Sure did fix my problem!
Diagnosis for: (Random) no sound; no phone connectivity such as: WIFI; BLUETOOTH; GSM.
Can happen: Flashing wrong fw; Flash failure.
NOTE: Android SDK is required, go to your OS below and view "prerequisites" for more information...
Windows 7 methodPrerequisites: Android SDK - Tools and SDK! (install here.)
Instructions:
(1. Make a folder in the directory "C:/" and name it "qinara."
(2. Download the following attachment below: "NON-HLOS.bin" (In the attachments / downloads section)
(3. Place "NON-HLOS.bin" in the "C:/qinara/" folder.
(4. Open a cmd prompt.
(5. Change Directory (CD) the cmd to your install location of Android SDK's Platform Tools (type it in to the command prompt.) to make
a command like the following example. Example: CD C:/users/YOUR-USERNAME/android/sdk/platform-tools
(6. Type the following command in...
Code:
fastboot flash modem C:/qinara/NON-HLOS.bin
(7. Wait for the modem to be sent and installed.
(8. Type the following command in...
Code:
fastboot reboot
(9. When the phone boots everything but gsm will be working, to fix it go to settings. From the main settings menu, go to mobile network. It
will freeze, press the home button. Once you press the home button open up recent apps by pressing the multi-tasking button.
it freezes.
(10. Open up your multi-tasking menu and open settings.
(11. Set "select network" to "automatic," then your done.
Ubuntu / Other Linux-distro methodPrerequisites: Android SDK - Tools only! (to install type the following cmds in terminal...)
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Instructions:
(1. Make a folder in the directory "/home/USERNAME/" and name it "qinara."
(2. Download the following attachment below: "NON-HLOS.bin" (In the attachments / downloads section)
(3. Place "NON-HLOS.bin" in the "/home/USERNAME/qinara/" folder.
(4. Open a terminal.
(5. Type the following command in...
Code:
fastboot flash modem /home/USERNAME/qinara/NON-HLOS.bin
(6. Wait for the modem to be sent and installed.
(7. Type the following command in...
Code:
fastboot reboot
(8. When the phone boots everything but gsm will be working, to fix it go to settings. From the main settings menu, go to mobile network. It
will freeze, press the home button. Once you press the home button open up recent apps by pressing the multi-tasking button.
it freezes.
(9. Open up your multi-tasking menu and open settings.
(10. Set "select network" to "automatic," then your done.
Downloads
-NON-HLOS.bin
Ask any questions below... :fingers-crossed:
Kinda feels that way...but on the Linux instructions just use ~/qinara/NON-HLOS.bin instead of /home/USERNAME/qinara/NON-HLOS.bin
~/ means the users home directory
Also, and I'm gonna add this to my faq, but download the fastboot I linked, rename to moto-fastboot, place it in ~/bin and add that to $PATH in ~/.bashrc (or where ever your preferred disto prefers it to be)
My actual path line in .bashrc (the part above I'm referring to is in bold)
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/share/android/bin:/share/android/adt/sdk/tools:/share/android/adt/eclipse:/share/android/adt/sdk/platform-tools:$HOME/bin:"
For the curious, I keep all my Android stuff on its own partition (/share/android) so all I have to do is add those directories to my $PATH if I decide to disto hop. If you dualboot, you can do the same thing only set the partition as NTFS or ext2 (there's an windows ext2 driver). I disto hop about once a month.
Don't have access to my desktop right now trying to install my new ssd and put Linux mint on it. (Noticed your a Linux guy, do you like mint?) Anyways I'll be sure to add that in later. Thanks.
Sent from my MB886 using xda premium
Mints OK. I prefer Mint Debian, but I'm not a fan of Ubuntu. Pure Debian Stable and Testing is also a good choice.
Arch Linux and its derivatives are nice but aren't noob friendly and are prone to breakage due to being so bleeding edge. Manjaro is a noob friendly distro based on Arch repo snapshots with bug fixes.
About to hop to Slackware 14 myself. Gonna be my first time using it.
All the other distros I've used -- too long ago to be fair and relevant to what's out now.
help...
can you tell me its working or not cause i have some gsm problem no signal due to band change
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28172 KB)...
OKAY [ 2.430s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.720s
Oooooh Cool.....now after trying to find how to get out of the mess that created. I still dont have signal lol
i really need my signal back ...anyone could help me ,,,i am afraid this method does brick my phone ..and another question is if i install the stock rom from RSD lite , will i lost my root access???
yashrab said:
i really need my signal back ...anyone could help me ,,,i am afraid this method does brick my phone ..and another question is if i install the stock rom from RSD lite , will i lost my root access???
Click to expand...
Click to collapse
Yeah this method bricked my phone. I had to go back to stock through RSD, and lost root access. The good news is it was so easy to reacquire root thanks to Dan Rosenberg's programs.
Can I install stock though myth tool.. I think it does work just like RSD?.. Plz tell me cause I am totally noob in this part.. And I don't want to brick my phone..
Sent from my MB886 using xda premium
Moto Atrix work on any GSM carrier or.. ?
skeevydude said:
Mints OK. I prefer Mint Debian, but I'm not a fan of Ubuntu. Pure Debian Stable and Testing is also a good choice.
Arch Linux and its derivatives are nice but aren't noob friendly and are prone to breakage due to being so bleeding edge. Manjaro is a noob friendly distro based on Arch repo snapshots with bug fixes.
About to hop to Slackware 14 myself. Gonna be my first time using it.
All the other distros I've used -- too long ago to be fair and relevant to what's out now.
Click to expand...
Click to collapse
I have question. If I buy Moto Atrix HD will it possible to make it carrier-unlocked so I can use it here in Saudi Arabia where 90% devices are not carrier-locked?
lonesomedove said:
I have question. If I buy Moto Atrix HD will it possible to make it carrier-unlocked so I can use it here in Saudi Arabia where 90% devices are not carrier-locked?
Click to expand...
Click to collapse
You should be able to, but I'll tell ya that some users have gone through multiple places to get it unlocked since not all the unlock services have the updated unlock codes we need.
Nope
Code:
C:\Program Files\Android SDK\sdk\platform-tools>fastboot flash modem C:/qinara/NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28164 KB)...
OKAY [ 2.185s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.429s
Yup. Didn't work.
Any ideas?
BackDoorNoBaby said:
Code:
C:\Program Files\Android SDK\sdk\platform-tools>fastboot flash modem C:/qinara/NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
sending sparse 'modem' (28164 KB)...
OKAY [ 2.185s]
writing 'modem'...
(bootloader) Unknown chunk type
FAILED (remote failure)
finished. total time: 3.429s
Yup. Didn't work.
Any ideas?
Click to expand...
Click to collapse
You didn't use OUR fastboot. I have a link in our fastboot guide, and a direct link here.
/Thank you for posting the full terminal output, command and all.
//It helps
///Most just post "Help, Help, Help" X doesn't work.
Thanks
skeevydude said:
You didn't use OUR fastboot. I have a link in our fastboot guide, and a direct link here.
/Thank you for posting the full terminal output, command and all.
//It helps
///Most just post "Help, Help, Help" X doesn't work.
Click to expand...
Click to collapse
Got it. Thanks.
I'll check it out after my classes tonight and give an update.
Yup
Yup. That did it. Fixed the issue.
Back to my 4G!
Thanks again.
Anyone tried with CM10.2?
Nope. I know Cyanogenmod has issues at the moment, but I don't know if this will fix it.
Best I can say is to try it. Worst case: you reinstall the ROM. Or you can wait for a release version of CM 10 instead of a nightly.
I can say this didn't brick my phone, so you shouldn't have to worry about it. (but as always - no guarantee)
Sent from my Atrix HD using xda app-developers app
I really need help, I need something like this but for a company in Mexico. I tried this but it didn't worked.
Question if i reflash back to stock eith RSD LITE or myth tools will that fix my baseband i delete my baseband by accident
Dumb me
wcdma and lte network problem
i happen to own the mb886 the lte and wcdma used to work then i mistakenly went to change my base band to cellular (800-mhz) then the network went off so i changed it to (aus2 band (gsm-900/ dcs-1900/wcdma-850/wcdma-pcs-1900) but now am only able to get 2g or edge networks but am also in a 3g coverd area. can you guys please help me out
How To UnBrick A Hard Bricked Moto X
Hii , First of all I wanna thanks to this awesome scrpit by @s5610 who brought my phone from dead to alive , I think i am the first guy to unbricked the hardbricked phone using this script lol , My phone was hardbricked because i was testing my kernel and entered wrong path in partition due to which i got hard bricked i was worried for my phone , Service Center was asking for 7k in Indian Rupees , i was hopeless then i gave a try to this method , followed all steps written here and then finally i entered to fastboot menu of 30.B7 Kitkat As i was using 30.B7 Bootloader earlier and then i flashed My gpt.bin and S-partition and flashed my stock rom voilla !! and my phone booted the aim was to share this post was this method was on page 42 and only less guys have seen this post , so i created a new thread regarding this
All Credits Goes to - @s5610
s5610 said:
Unbricking Guide for any Moto X Gen 1 (wire trick)
Download, and unpack supplied zip to any disk, C: or D:, in root folder. Install driver by launching Qusb.drv.inst.msi, then open Windows' Device Manager, and see if you got "Qualcomm HS-USB QDLoader 9008" device (it is "QHSUSB_DLOAD" without driver installed) located in "COM & LPT ports" section.
If yes, you see it, go to software part below. If it's not there, a full disassemble of the phone is needed to get close to back side of motherboard (google for "iFixit Teardown Moto X Guide" for step-by-step instruction).
So, when you are inside, disconnect the battery first. No need to pull it out, it's glued. Now get to back side of motherboard, and very very gently gain access to the lower left corner of ARM+DRAM shield (see picture). I've done it with Stanley knife. Also you can use miniature nippers - but very carefuly! Once you get access to inner space of shield, use tiny wire to short special pin to the ground (see picture), then connect USB cable, and in the moment when you see "QHSUSB_DLOAD" device (or "Qualcomm HS-USB QDLoader 9008" if driver is installed) pop out in Windows' Device Manager, quickly remove the wire. The goal is to have "Qualcomm HS-USB QDLoader 9008" in "COM & LPT ports" section of Device Manager. If it is achieved, we are done with hardware, and move on to soft part.
Now software part. Go to unzipped C:\Python27 folder, launch bat-file, and wait until finish:
RUN_blank_bootloader_flash.bat
(if you got error like "No data read from USB..." etc, just skip to next step)
Next launch either
- .Boot_KK_4.4.2_B4.exe,
or .Boot_KK_4.4.4_B7.exe,
or .Boot_LP_5.0.2_BC.exe,
or .Boot_LP_5.1.0_BD.exe,
or .Boot_LP_5.1.0_BE.exe
- depends on Android version your phone has last time. If you don't know what you need, begin with first one.
Wait 10 seconds, then launch next bat-file, and wait until finish:
RUN_moto_x_bootloader_flash.bat
Phone should go into fastboot mode! If it doesn't, repeat previous step trying higher version. But don't try to flash BC, BD, and BE, if you didn't install Lollipop on this phone!
OK. Disconnect the USB cable, connect the battery, connect again USB cable (fastboot don't work, if don't see battery). Launch next bat-file:
RUN_gpt.bin_flash.bat
The phone will get in fastboot, ready to be flashed by appropriate firmware. If it is official RSD (SBF), delete from xml strings consisting gpt.bin and motoboot.img for safe flashing.
...
Download link: http://www.mediafire.com/download/3e38rr3wy28s071/Moto.X.Unbrick.zip
This guide was brought to you by s5610
Links that this guide is based on (where I took files and general idea):
http://forum.xda-developers.com/droid-ultra/general/droid-ultra-maxx-brick-recovery-t2830806
http://forum.xda-developers.com/mot...-moto-x-t2629057[/url[/QUOTE][/QUOTE][/QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Not sure if additional thread is necessary )
UPDATED
The best resurrection method for Moto X is here.
Can Someone re-upload that file? Thanx!
Please upload the mediafire link...
Plz plz.. I have bricked my phone. It seems that this procedure will work for me. Please upload and save my life.
even i have bricked my moto x...need a working download link..please.
https://drive.google.com/file/d/0B3EDzuzDCakzdWxHa2RWVDJhRXc/view?usp=sharing
Cannot install qsub.drv.inst.msi on my windows 10...says failed to attribute and failed to delete qcusbser.sys.
Thanks
Can we write the full firmware through Qload 9008 mode ???
HI I have a question. I bricked my gf's phone while trying to unlock the bootloader and I am not able to turn the phone on. Only positive feedback is that when I plug it in to the computer, I can hear a notification on my computer. I followed your guide. I can see the "Qualcomm HS-USB QDLoader 9008" device (it is "QHSUSB_DLOAD" without driver installed) located in "COM & LPT ports" section.
Then I followed your software instructions. When I run the RUN_blank_bootloader_flash.bat, I get the following
Code:
Starting qflash!
Executing command qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloa
der_singleimage.bin -v -o
Motorola qflash Utility version 1.3
qflash - com3 is an invalid port
Invalid COM port enteredBlank flashing successful
Device will now enumerate in fastboot mode
Then, I followed the rest of the instructions by trying each .Boot .exe and waitng 10 seconds and finally with RUN_moto_x_bootloader_flash
but I am getting the following error.
Code:
C:\Users\cxx\Desktop\Python27>python qdload.py MPRG8960.bin -ptf _boot\partiti
ons.txt -pt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com3
Traceback (most recent call last):
File "qdload.py", line 815, in <module>
main()
File "qdload.py", line 762, in main
tty = openTTY(args.ttyPort)
File "qdload.py", line 174, in openTTY
tty = serial.Serial(port=tty_path, baudrate=115200)
File "C:\Python27\lib\site-packages\serial\serialwin32.py", line 38, in __init
__
SerialBase.__init__(self, *args, **kwargs)
File "C:\Python27\lib\site-packages\serial\serialutil.py", line 282, in __init
__
self.open()
File "C:\Python27\lib\site-packages\serial\serialwin32.py", line 66, in open
raise SerialException("could not open port %r: %r" % (self.portstr, ctypes.W
inError()))
serial.serialutil.SerialException: could not open port 'com3': WindowsError(2, '
The system cannot find the file specified.')
C:\Users\cxx\Desktop\Python27>pause
Press any key to continue . . .
please help.
Thanks.
Device Shows As USB Input
Hey all,
I'm having trouble getting my Windows 7 machine to recognize my XT862 as a QHSUSB device. Windows does recognize it, just as a "USB Input Device" -- very generic, I know -- so I don't think I have to do any motherboard hacks (and I sure hope not!). However, as it won't let me update the driver either, so I can't do anything. Also, when I plug it into my Mac, it does pop up as a Qualcomm Composite Device. Since something's obviously still ticking, where did I go wrong?
Thanks
shengslogar said:
Hey all,
I'm having trouble getting my Windows 7 machine to recognize my XT862 as a QHSUSB device. Windows does recognize it, just as a "USB Input Device" -- very generic, I know -- so I don't think I have to do any motherboard hacks (and I sure hope not!). However, as it won't let me update the driver either, so I can't do anything. Also, when I plug it into my Mac, it does pop up as a Qualcomm Composite Device. Since something's obviously still ticking, where did I go wrong?
Thanks
Click to expand...
Click to collapse
Put it on a charger for 5-6 hrs and see if that will help.I had this same problem but on a Moto G and charging it up helped.
liveroy said:
Put it on a charger for 5-6 hrs and see if that will help.I had this same problem but on a Moto G and charging it up helped.
Click to expand...
Click to collapse
Will do! I think I did try charging it awhile ago, but I'll give it another shot.
can my phone be unbricked?? here is the error log:
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
sdl_hello() - Invalid response: 7e030003331b7e
sdl_hello() - This is a NAK response from ROM code, which means the device has
een reset back to blank flash mode. Usually this is caused by power supply issu
s. Please try again with battery eliminator if it persists
Unexpected target reset, bailing out after 2 retries
I am trying to install the drivers and it will show up as qhsusb_dload for about 5 seconds then reverts back to Relink HS USB QDloader 9008. Should i try the wire trick? It will say that the Qhsusb drivers are installed but always changes.
I've updated to android 10 thinking it was gonna be fun but now I can't receive updates from the play store, my saftetynet is not valid (does not pass), I can't use my bank account apps and chrome cannot download any files (ending with download error)
Is there anyway to return to android 9 or am I doomed until I spend another 800$ cad?
Phone: WW_17.0210.1912.22_0
Tencent 8gb/128gb
Converted from CN to WW with guides from here
I've tried following this:
https://forum.xda-developers.com/rog-phone-2/how-to/rom-asus-rog-phone-ii-zs660kl-ww-t3971059
But get the following:
target reported max download size of 536870912 bytes
sending 'abl' (420 KB)...
OKAY [ 0.020s]
writing 'abl'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.031s
Send help
SirGoldenTaco said:
I've updated to android 10 thinking it was gonna be fun but now I can't receive updates from the play store, my saftetynet is not valid (does not pass), I can't use my bank account apps and chrome cannot download any files (ending with download error)
Is there anyway to return to android 9 or am I doomed until I spend another 800$ cad?
Phone: WW_17.0210.1912.22_0
Tencent 8gb/128gb
Converted from CN to WW with guides from here
I've tried following this:
https://forum.xda-developers.com/rog-phone-2/how-to/rom-asus-rog-phone-ii-zs660kl-ww-t3971059
But get the following:
target reported max download size of 536870912 bytes
sending 'abl' (420 KB)...
OKAY [ 0.020s]
writing 'abl'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.031s
Send help
Click to expand...
Click to collapse
If you want to go back to Android 9, flash the latest RAW
Welp it ended better than I thought, followed this guide:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042
And was saved by cyber Jesus: JazonX
Thanks for the assistance!
SirGoldenTaco said:
Welp it ended better than I thought, followed this guide:
https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042
And was saved by cyber Jesus: JazonX
Thanks for the assistance!
Click to expand...
Click to collapse
Hey, when you ran the flashall_AFT.cmd did it run forvere? Did you ever get a complete message or your phone to reboot? I am trying to downgrade just the same, and I cannot ever get that raw file to flash over. Now my image is corrupt and I cant boot the phone, thank goodness I made backups, but still I cannot seem to flash the phone no matter what.
MrKioFLow said:
Hey, when you ran the flashall_AFT.cmd did it run forvere? Did you ever get a complete message or your phone to reboot? I am trying to downgrade just the same, and I cannot ever get that raw file to flash over. Now my image is corrupt and I cant boot the phone, thank goodness I made backups, but still I cannot seem to flash the phone no matter what.
Click to expand...
Click to collapse
My phone was at android 10 beta when I did these steps:
Tried running the bootloader unlocker and it gave me an error (I ignored it and continued)
I activated devmode for usb debugging (tapping 5 times on build #)
Made sure I allowed my pc to use debug mode (by tapping the always allow porompt)
I already had the google drives installed
I downloaded this file (which is linked in the post)
https://drive.google.com/file/d/1Y1ey0TOWq0pW1Qid7yqy83i0TqLYgwKR/view
Extracted it on my pc desktop (anywhere in a fresh document)
Rebooted my phone in bootloader
Connected my rog 2 to my pc using the side usb (***Important to do not plug it in the bottom usb***)
Ran flashall_aft.cmd and after about 8m - 10m it rebooted, forced me to do a factory reset
Then the phone was all good
If you did all the steps above and it's still not working then sorry I'm more of a "follow guides" kinda guy so my knoledge on the matter is pretty limited
SirGoldenTaco said:
My phone was at android 10 beta when I did these steps:
Tried running the bootloader unlocker and it gave me an error (I ignored it and continued)
I activated devmode for usb debugging (tapping 5 times on build #)
Made sure I allowed my pc to use debug mode (by tapping the always allow porompt)
I already had the google drives installed
I downloaded this file (which is linked in the post)
https://drive.google.com/file/d/1Y1ey0TOWq0pW1Qid7yqy83i0TqLYgwKR/view
Extracted it on my pc desktop (anywhere in a fresh document)
Rebooted my phone in bootloader
Connected my rog 2 to my pc using the side usb (***Important to do not plug it in the bottom usb***)
Ran flashall_aft.cmd and after about 8m - 10m it rebooted, forced me to do a factory reset
Then the phone was all good
If you did all the steps above and it's still not working then sorry I'm more of a "follow guides" kinda guy so my knoledge on the matter is pretty limited
Click to expand...
Click to collapse
Thank you for your help, apparently the USB hub I was using was had horrible transfer rates, and so even in 45 minutes nothing was finished copying over. Went directly to the USB on my pc and everything ran wonderfully! Thank you again!
MrKioFLow said:
Thank you for your help, apparently the USB hub I was using was had horrible transfer rates, and so even in 45 minutes nothing was finished copying over. Went directly to the USB on my pc and everything ran wonderfully! Thank you again!
Click to expand...
Click to collapse
You should be really careful about using USB hubs, for anything flashing related or if you are transferring a file without a checksum I would highly recommend going direct to a normal USB port.
View attachment 5357205
oneplus 6/6t 都可用
警告！不当操作可能会导致手机变砖！
-
20210822 updata
-
project address : https://github.com/edk2-porting
and
Tool download :https://drive.google.com/drive/folders/1GrX9JTVpKwo3WNshqIljPRc9Q6dPJDJJ?usp=sharing
boot download : https://github.com/edk2-porting/edk2-sdm845/releases
drives download : https://github.com/edk2-porting/WOA-Drivers/archive/refs/heads/main.zip
-
Installation tutorial
new tutorial!(English) https://forum.renegade-project.org/t/faq/95
-
article(Chinese) : https://forum.renegade-project.org/t/6-windows/194
-
Device support status
Renegade Project
Renegade Project
renegade-project.org
-
The drive is gradually improving
有问题我会不定期来看的，欢迎提问。
Questions are welcome
It seems better to be merged with the post https://forum.xda-developers.com/t/os-windows-on-arm-polaris.4325377/
la0pe0Ue said:
It seems better to be merged with the post https://forum.xda-developers.com/t/os-windows-on-arm-polaris.4325377/
Click to expand...
Click to collapse
and that thread is locked-moment someone comes up with something groundbreaking or unique it gets shut down-no wonder so much less now on xda (x stands for cut or reduced)
I installed Windows according to this guide and it works.
Mazoch said:
I installed Windows according to this guide and it works.
Click to expand...
Click to collapse
hiow did u do it im keep getting stuck at were u have to enable test mode for divers but the uefi drive dose not let me acces it and help would be greatful thanks my phone is mix2s
Chris3445 said:
hiow did u do it im keep getting stuck at were u have to enable test mode for divers but the uefi drive dose not let me acces it and help would be greatful thanks my phone is mix2s
Click to expand...
Click to collapse
It's been a while since my installation, and frankly I don't remember much about it. Describe your problem in more detail. Rather, you've definitely made a mistake.
Mazoch said:
It's been a while since my installation, and frankly I don't remember much about it. Describe your problem in more detail. Rather, you've definitely made a mistake.
Click to expand...
Click to collapse
So my problem is i do all the steps in the guide were I get stuck is at the part were u have to do the bcdedit for the test mode to trun its one of the last steps be for u can boot up windows like i made the esp partition correctly like I use parted on the computer format both like resized the partition the user data partition made the windows partition and then the ESP partition and then after that part I do the Windows installation where you you know do the install that when thing then the drivers and then before the drivers you have to do that BCD edit for the for the boot files and then like every time I try to open the EFI partition like double click on it with a mouse it says something about security that I don't have permissions and then I try to left click go to properties and then there's no security Tab the uefi partition just wont let me acces it at all I just dint now what step im doing wrong thanks for the reply
Did touch screen work on mi mix 2s cuz i got windows to load but touch dose not work I installed all the divers i dont if its cuz i didnt flash that devcfg file i just did now im redeploying window's and its drivers
I was able to get it I have it fully working
Chris3445 said:
I was able to get it I have it fully working
Click to expand...
Click to collapse
Cool, sorry I didn't help, but I completely forgot about your problem. I'm glad it worked out for you
Mazoch said:
Cool, sorry I didn't help, but I completely forgot about your problem. I'm glad it worked out for you
Click to expand...
Click to collapse
Thanks man the only thing I have a issues with is pluging usb mouse and key bord do u now if there is any way to fix that. Its ok it tought me alot wen trying to install windows on it tho
Chris3445 said:
Thanks man the only thing I have a issues with is pluging usb mouse and key bord do u now if there is any way to fix that. Its ok it tought me alot wen trying to install windows on it tho
Click to expand...
Click to collapse
Unfortunately there is no OTG support for our phone, for the time being you can forget about it. It's also impossible to transfer video with a USB-C cable. Currently, this Windows is such more of a curiosity than a useful system
Do u have usb working I think i was useing tue wrong boot loader or something cuz the newer bootloader works really well with usb there is a way to get usb c to displayed to a monitor i seen. It on telegram and I did fet usb to work its pretty usable for now just not sound yet this project is really dope tho u have to say
I also was wondering if there was a way to flash the boatloader to the phone so i dont have to keep pluging it in the computer
Question,
When trying to reboot to Windows it will eventually blue screen with the message : Stop Code: Driver PNP WATCHDOG. I read thats because I have not flashed the file : http://files.renegade-project.org/devcfg-polaris_FixTS.img
When I try I get the below:
Warning: skip copying devcfg_ab image avb footer (devcfg_ab partition size: 0, devcfg_ab image size: 38444).
Sending 'devcfg_ab' (37 KB) OKAY [ 0.008s]
Writing 'devcfg_ab' OKAY [ 0.004s]
Finished. Total time: 0.031s
Assume the Warning is the problem, I tried resetting everything to stock with the mi flash tool. This was great for my Chinese language skills but the warning still shows when I try to flash.
other laptop, different cable, same thing.
Any advice ?