I've been reading through dozens of "bricked" threads for the last day, trying to figure this out, as I've been rooting/flashing android since the Hero and have managed not to brick anything in all those years. This is an unlocked Pixel 2XL bought from Google Store.
I unlocked the bootloader probably a year ago. I'd been rooted at one point, but after installing a security update around September I ended up leaving it stock.
Picked up a Pixel 3 and wanted to sell the Pixel 2. Confirmed I was all stock everything, and locked the bootloader. When trying to reboot after locking, I now get the "Can't find valid operating system. The device will not start" error.
I can access the fastboot menu, and my device is detected with fastboot devices. However, when I try "fastboot flashing unlock" or "unlock_critical" I get:
"FAILED (remote: 'Flashing Unlock is not allowed')"
I've tried Deuce's script, same errors.
Saw a suggestion regarding switching to the other partition, this errors out as well due to device being locked.
Tried booting into recovery from the Fastboot screen; it just goes to the "Can't find valid operating system" error screen with the only option being press power to power off so apparently my recovery partition is wiped as well. Also tried booting from the TWRP recovery image, this errors out due to device being in Lock State.
I have tried multiple PC's, USB cables, and USB slots. All have the same issue. Confirmed that I was using latest Platform Tools from Google as well.
My assumption is that I missed something and my device was not fully stock when I re-locked the bootloader. Before I give up hope and throw myself at the mercy of Google, I just thought I'd throw this up here to see if I missed something in one of the threads or if someone has any other ideas. Thanks!
So many cases from relocking the bootloader, guess i just leave it unlock then., care to share with us the method you use to return to stock ? did you use the Deuce script ?
Unfortunately I did not use the Deuce script. I just factory reset, flashed the December factory image with ADB, and then locked the bootloader (also with ADB).
I have exactly the same problem; have you found any solution? And will Google accept the device if it's under warranty knowing that the device was once unlocked?
ASMstudent said:
...will Google accept the device if it's under warranty knowing that the device was once unlocked?
Click to expand...
Click to collapse
Yes. Google is rather lenient in that regard.
That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Sent from my PLK using Tapatalk
ASMstudent said:
That's good news!
Do they require a proof of purchase or a warranty card because I don't have either of them.
Click to expand...
Click to collapse
No proof of purchase means Google is not obligated to help you. You'll need to talk to them. On a side note, run the IMEI through imeipro.net's LG IMEI search engine so you know when the phone was manufactured, as that may be useful information in dealing with Google.
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
{
"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"
}
Sent from my PLK using Tapatalk
ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.
Click to expand...
Click to collapse
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?
Badger50 said:
If your wanting to get into bootloader mode, with the phone off, hold power + volume down until you get to the bootloader screen. Or, were you trying to do something else?
Click to expand...
Click to collapse
I was playing around hoping for some thing to change. I searched around and found out that LG ( the original ODM of pixel 2 xl) has a way to unbrick using download mode ( accessed by pressing and holding power button+ volume up) which is similar to what is happening to me. The problem is that you can only flash KDZ updates with LG flash tool. This works for hard bricked devices when nothing else worked. I was thinking to connect the device in this way and update drivers using LG drivers instead of pixel's but still I can't get an update in kdz format.
ASMstudent said:
...but still I can't get an update in kdz format.
Click to expand...
Click to collapse
And you won't either. Google doesn't offer them, so you'll have to hope a developer creates one or one gets leaked by someone at Google.
Just installed LG mobile drivers and connected my device in download mode. In manage devices, it's now shown as an LG mobile connected, so theoretically it could work.
Sent from my PLK using Tapatalk
I downloaded a patched LGUP flash tool from LG v30 forums that could allow cross flashing between different variants and it detected my pixel 2 XL. Still it needs a kdz or tot file to flash, but when I chose boot.img from Google factory image, it gave me an error on the LGUP but also on my device which means there is a connection between my PC and my device which means this might actually work .View attachment 4719702
Sent from my PLK using Tapatalk
ASMstudent said:
I found out that this happen when I press volume up while the device Boots up.
First it says download mode then it goes to the second screen. On this state, the device is detected by the PC, but when I type adb or fastboot devices I don't get any connected device.View attachment 4718679View attachment 4718680
Sent from my PLK using Tapatalk
Click to expand...
Click to collapse
were you able to find a good solution to your problem, am in the same situation.?
Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.
ASMstudent said:
Nope
I found out that this is EDL or Qualcomm emergency download mode and you need Google proprietary programmer firehouse file, blank flash files and rawprogram0.xml file; last two can be extracted from a working device. I contacted Google support forum and they told me that they wouldn't release these files to anyone as they may be used to find software vulnerabilities in the device. I contacted software repair center known for dealing with these problems, he told me that they have the programmer firehouse for the pixel 2xl ( not sure if they actually do or it's just a scam) but they would need time to extract the other needed files. I paid a sponsorship fee ( only 21$ ) and gave them 2-3 months, but they provided no updates so I requested a refund and sold the device as spare parts. EDL mode is theoretically your best bet to fix the device, but without the appropriate files ( which may never be available) it's useless.
You can look up EDL mode, QFIL, QPST tools and the store's name is aryktech.
Click to expand...
Click to collapse
How sure its not your device that i bought of ebay?:laugh:
0x0null said:
How sure its not your device that i bought of ebay?[emoji23]
Click to expand...
Click to collapse
Lol
Actually I sold it locally in my country.
You can contact aryktech if they made any progress just don't pay upfront
Sent from my PLK using Tapatalk
Aiit.tnx
@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.
SimFox3 said:
@ASMstudent or @0x0null - any other progress? Exact same situation with Taimen (Pixel 2 XL). Dunno if I should make this my month-long side project, or just chuck the phone.
Click to expand...
Click to collapse
Nah, i got a new board.
Related
I'm starting to lose all hope in this device...
I bought my phone from, what I thought, was an official Xiaomi online store, my mistake, buyer beware, lesson learned. However. I have the phone, I like the form factor and all that, and the thought of trying to get a return from a Chinese company sounds like the kind of hassle I don't want to deal with. I'm well experienced in rooting/flashing devices (Nexus 5, OnePlus 2, OnePlus X, Xperia Z5c). I've done it a thousand times on these devices.
My new Mi5S came with "MIUI Global 8.6 | Stable 8.6.10.0(RM1100)" preinstalled.
I only found out after I bought it that the reseller installed this version. They apparently did this so they can make it a global rom. They installed Google play services, Play Store, removed chinese apps and made English the default language. That's great and all, but they also have the Locale setting locked in as China. It's unchangeable. And installing Google Launcher from the Play Store doesn't work (yet Pixel Launcher, downloaded from the web, works fine). Not a huge deal I guess.
Anyway, long story longer, I'm trying to unlock the bootloader.
I got permission, downloaded the Unlocker, VolDown+Power into Fastboot and ran the MiFlash unlocker.
It goes to 50% and then says "Couldn't verify device". That's where I'm stuck.
I've tried everything I can think of, and I just can't unlock the Bootloader.
Is anyone else having this same issue? Has anyone found a way to get TWRP on here?
Had the same issue when unlocking mine - two things worth checking: firstly, make sure the phone is signed in to the same Mi account that you have permission on (you can check it's "properly" linked by going to i.mi.com and clicking Find Device - if it shows as online, you're good). You don't need to use the Mi account at all after this, so once it's unlocked you can unlink and delete the account if you like.
Secondly, make sure the PC you're using has compatible ADB drivers on it - when it's linked by USB in FastBoot mode, make sure that it shows correctly in device manager. I had some weirdness with the previous global driver (still don't know why) and only ended up succeeding when I reinstalled straight from device manager.
MoonBuggy said:
Had the same issue when unlocking mine - two things worth checking: firstly, make sure the phone is signed in to the same Mi account that you have permission on (you can check it's "properly" linked by going to i.mi.com and clicking Find Device - if it shows as online, you're good). You don't need to use the Mi account at all after this, so once it's unlocked you can unlink and delete the account if you like.
Secondly, make sure the PC you're using has compatible ADB drivers on it - when it's linked by USB in FastBoot mode, make sure that it shows correctly in device manager. I had some weirdness with the previous global driver (still don't know why) and only ended up succeeding when I reinstalled straight from device manager.
Click to expand...
Click to collapse
I have verified that I'm using the proper account and that Mi Cloud sees my device as online.
Could you clarify which driver you ended up using?
You cannot unlock bootlader that easy. (Ive own mi5)... my english is not very good so i cannot describe all steps. Just find how to unlock mi5 bootloader. You have to request from xiaomi to let you unlock it. !!! AND I SEE NO PROBLEM HERE.
lummujaj said:
You cannot unlock bootlader that easy. (Ive own mi5)... my english is not very good so i cannot describe all steps. Just find how to unlock mi5 bootloader. You have to request from xiaomi to let you unlock it. !!! AND I SEE NO PROBLEM HERE.
Click to expand...
Click to collapse
I already have permission. Still doesn't work.
I used the driver from here: http://www.xiaomi.cn/content-19-6735-1.html - direct file link is http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
So, check this out. I loaded up the Mi PC software and instead of just clicking on R.Flash, I held shift then clicked R.Flash. It popped up a file select box and I was able to choose the official chinese ROM. It then installed it! No issues or anything. Once it was finished and it booted, I did a factory reset. The initial setup screen ran and I got in to the phone. I installed the Google Play Installer from the Mi Store and that was that.
I now have 8.0.10.0.
Didn't need to unlock the bootloader or anything.
*phew*
dgrasley said:
So, check this out. I loaded up the Mi PC software and instead of just clicking on R.Flash, I held shift then clicked R.Flash. It popped up a file select box and I was able to choose the official chinese ROM. It then installed it! No issues or anything. Once it was finished and it booted, I did a factory reset. The initial setup screen ran and I got in to the phone. I installed the Google Play Installer from the Mi Store and that was that.
I now have 8.0.10.0.
Didn't need to unlock the bootloader or anything.
*phew*
Click to expand...
Click to collapse
You've actually completed the first step in unlocking your bootloader - you need to make sure you are using an official ROM and not a so called "Vendor ROM".
I am still waiting patiently for my Mi5s to get here...
If "fastboot devices" shows your mi5s in fastboot mode right before unlocking - then you have the right driver and the 50% problem should be solved.
CL0SeY said:
You've actually completed the first step in unlocking your bootloader - you need to make sure you are using an official ROM and not a so called "Vendor ROM".
You can unlock in vendor rom..
Without unlocking you should be able to flash official rom using miflash/fastboot
Vendor rom updater/recovery may not word (did not work for me) to update to official chinese rom..
Click to expand...
Click to collapse
MoonBuggy said:
I used the driver from here: http://www.xiaomi.cn/content-19-6735-1.html - direct file link is http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
Click to expand...
Click to collapse
any funky method you have to install the driver? i am struggling here. adb is fine, but fastboot shows no devices. have tried every driver i can find including above!
edit - for the record i disabled driver signature verification in win10 and installed the above drivers, and still no luck. here is my cmd output
{
"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"
}
when it reboot into fastboot a new driver installed on windows and i can see the android bootloader interface in device manager but still no fastboot. weird? also miflash is showing the device when the phone is in fastboot.
---------- Post added 28th October 2016 at 00:33 ---------- Previous post was 27th October 2016 at 23:37 ----------
ok fixed the driver problem. for anyone else stumbling across this:
reboot to fastboot mode, then in device manager update the bootloader interface driver with the google driver that comes inside the C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver folder. (you need to have miflash installed obviously)
note that windows10 you may have to disable driver signature verification for this.
:good:
I got my phone today and had the same problem but i solved it at last, i installed the chinese dev rom and then it worked to unlock the bootloader and i have installed xiaomi.eu rom and works great.
I had the same issue, for me it was indeed the fastboot driver.
The solution for me was to put phone in fastboot, connected usb.
In device manager you have to look android bootloader interface, deinstall, and let windows install driver itself.
For me that was the solution...
From what i have read everywhere, using a windows 7 machine instead off windows 10 will solve the issue for sure
marcel112 said:
I had the same issue, for me it was indeed the fastboot driver.
The solution for me was to put phone in fastboot, connected usb.
In device manager you have to look android bootloader interface, deinstall, and let windows install driver itself.
For me that was the solution...
From what i have read everywhere, using a windows 7 machine instead off windows 10 will solve the issue for sure
Click to expand...
Click to collapse
What OS did you use when you successfully did this? Windows 10 or Windows 7 or other?
dgrasley said:
What OS did you use when you successfully did this? Windows 10 or Windows 7 or other?
Click to expand...
Click to collapse
I was using a windows 10 machine, but i didnt succeed severall times.
The thing i did was trying to unlock, 50% error, then boot the phone, turned off find Mi phone, rebooted, tried again still no go, rebooted again, tunred on find Mi phone again, then tried unlocking again...: Eureka!!
That was the solution, so i tried that on a different machine with no drives installed at all!!
I was just using the phone normally for browsing when it rebooted and after the LG boot splash the phone died (no screen, no lights). I have to take the battery out in order to boot it again but it goes to black screen after splash screen - its not in a boot loop however. I can get into LG's recovery but the only option is to factory reset which I don't want to try yet in case I can recover my data. After searching around for other things to try, I found I can get into Download Mode, however its not detected by LG Mobile Support Tool at this point. When the phone appears dead it actually shows up in windows as 'qualcomm hs-usb qdloader 9008' (not much I can do with this as far as I can tell).
There are lots of threads about the bootloop problem that affected 505xxx serial number devices but mine is 512xxx - only about a year old, so I'm not sure this will be the same thing.
If anyone thinks there is anything I can try to recover files please reply back. I'm going to get in touch with LG support and put the phone in the freezer in the mean time to see if I can boot it after...
Its a hardware issue. They all are.
Every one is its own story but in the end she just wont boot
zeroid said:
I was just using the phone normally for browsing when it rebooted and after the LG boot splash the phone died (no screen, no lights). I have to take the battery out in order to boot it again but it goes to black screen after splash screen - its not in a boot loop however. I can get into LG's recovery but the only option is to factory reset which I don't want to try yet in case I can recover my data. After searching around for other things to try, I found I can get into Download Mode, however its not detected by LG Mobile Support Tool at this point. When the phone appears dead it actually shows up in windows as 'qualcomm hs-usb qdloader 9008' (not much I can do with this as far as I can tell).
There are lots of threads about the bootloop problem that affected 505xxx serial number devices but mine is 512xxx - only about a year old, so I'm not sure this will be the same thing.
If anyone thinks there is anything I can try to recover files please reply back. I'm going to get in touch with LG support and put the phone in the freezer in the mean time to see if I can boot it after...
Click to expand...
Click to collapse
If you like give this test a try. I don't know if it works with a defective mainboard but testing costs nothing..
Download FWUL and boot it (https://tinyurl.com/FWULatXDA).
Then go into the download mode on your g4.
Then open the folder LG in FWUL and open a LGlaf shell.
If you see the prompt in a black terminal ok. If not use the other shortcut with auth in its name. You may have to start the LG laf shell 2 or 3 times sometimes...
If you see the black terminal prompt type in the command:
ls
It should give you a list of files and folders. If not there's something wrong.
If you have luck you can then backup your data.
You need an external SD card to store your data.
I have no access to download mode atm but if you want to test this let me know and I can prepare the rest in a day or 2.
.
Sent from my LG-H815 using XDA Labs
Ok thanks for the offer. I should be able to have a go later today. After I froze the phone for 20 mins it got a bit further - the jingle you get at boot occurred but unfortunately it all died before it got anywhere near my homescreen. Its back in the freezer now.
I'm amazed it can go from working perfectly to a brick instantly, but I guess ifs its a physical connection that is broken on the motherboard...
zeroid said:
Ok thanks for the offer. I should be able to have a go later today. After I froze the phone for 20 mins it got a bit further - the jingle you get at boot occurred but unfortunately it all died before it got anywhere near my homescreen. Its back in the freezer now.
I'm amazed it can go from working perfectly to a brick instantly, but I guess ifs its a physical connection that is broken on the motherboard...
Click to expand...
Click to collapse
You can't fix the mainboard issue by your own. The only chance is getting a replacement by LG.
The freezer method is good for a last backup of your files but don't do it often it is not good for your phone.
.
Sent from my LG-H815 using XDA Labs
Yeah I know, was just hoping to backup a fews things I don't have, SMS messages, some apps configuration that don't sync settings online already....
zeroid said:
Yeah I know, was just hoping to backup a fews things I don't have, SMS messages, some apps configuration that don't sync settings online already....
Click to expand...
Click to collapse
Well then try it with FWUL.
I just need to test the right commands first..
.
Sent from my LG-H815 using XDA Labs
So I got FWUL booted but can't find an LG folder nor LGlaf Shell?
adb devices is working in a terminal.
zeroid said:
So I got FWUL booted but can't find an LG folder nor LGlaf Shell?
adb devices is working in a terminal.
Click to expand...
Click to collapse
Do you have downloaded the latest version? Directly on the desktop?!
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Do you have downloaded the latest version? Directly on the desktop?!
Click to expand...
Click to collapse
I downloaded from the main Androidfilehost link.
Here's the desktop when I boot:
{
"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"
}
Sorry but you haven't downloaded the latest version.
Tbh the sort order by AFH is really misleading and irritating.. so I have just re-ordered the androidfilehost structure so you may find the latest release better now.
The latest one is v1.3 btw.
Go to: https://www.androidfilehost.com/?w=files&flid=142115
Find the folder LATEST
Download FWUL from there
.
OK tried that version, no luck getting the LG LAF terminal window up for the short time the phone stayed in download mode. Even download mode is not stable any more, and just after that it wasn't switching on at all so kind of lost all hope of recovering anything from it now.
Thanks for the link to FWUL - could prove useful in the future.
Hello guys,
I have cedric, bootloader unlocked, rooted, etc.. I used some SDcard format app and selected wrong storage to format emmcblk0, so i formated entire phone, now in device manager its detected as "Quectel QDLoader 9008
" cannot power it on as well i think bootloader is bricked, i tryed to flash but cant find anything related to this phone, also cant find blankflash.
Do you guys have any info on how to unbrick this hard-brick, or its just paper weight? I don't get how did moto/lenovo allow bootloader erase option from system, even with root...
Regards
Perhaps search for some driver that enables the transfer of the bootloader for "Quectel QDLoader 9008"?
I've found some results relating to unbricking this, and according to some of them it refers to a chipset, use this search perhaps https://www.google.co.uk/search?q=Q...rome..69i57.2111j0j7&sourceid=chrome&ie=UTF-8
---------- Post added at 11:30 PM ---------- Previous post was at 11:28 PM ----------
found this, it may help http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
Tryed, not applicable for this mode, i need blankflash or some other method, i still have yet to try sdcard flash, but i am loosing hope here, might just accept that its totally bricked and thats it, oh well moving on i guess.
Guys i am trying to make unbrick method for Cedric, does anyone have 5 minutes of time to make loader.img, all you have to do is to be on firmware .93, bl unlocked and rooted.
Type in terminal emulator dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
And upload me that file, it will be around 160mb, i will try to test it and if it works upload the tutorial. The command above just reads your mmmcblk0 so there is no chance of bricking your device.
No one willing to give away five minutes to help? I will make it worthwhile since my phone is dead i am sure there is a change to fix it with this, and will make tutorial for community
magix01 said:
No one willing to give away five minutes to help? I will make it worthwhile since my phone is dead i am sure there is a change to fix it with this, and will make tutorial for community
Click to expand...
Click to collapse
Hey Mate i would help you if i could, but i'm on -72, if this would help you tell me, and i will upload the file asap.
@Cubico
We can try, but i don't think it will work tho. Please upload and we will see i guess
Ok guys new update, @Cubico provided me with Loader.img -73 firmware, so far tried nothing changed, device still showing no sign of life except Qualcomm 9008... not booting or anything, if someone have 93 bootloader Loader.img dump i can try that too, if not i will take it to shop to someone with JTAG and update you on status.
I have got a similar issue with an X4 that's hard bricked.
I know wrong forum, but I can't find anyone to help.
Trying to use QFIL I get "Download Fail: Switch To EDL Fail: Failed to Switch to Emergency Download mode"
ANY ideas? Thank you anyone that may be able to help!
Try installing this driver, then transfer/flash the bootloader, I can't help you with the actual img though.
http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/#
magix01 said:
Ok guys new update, @Cubico provided me with Loader.img -73 firmware, so far tried nothing changed, device still showing no sign of life except Qualcomm 9008... not booting or anything, if someone have 93 bootloader Loader.img dump i can try that too, if not i will take it to shop to someone with JTAG and update you on status.
Click to expand...
Click to collapse
Hi, just saw this - I'm on NP25.137-93
Do you still need this dump?
Let me know and I'll get on it
Edit - aww crap!
Really sorry to get your hopes up! Just remembered, my phone's not unlocked or rooted! This is the first phone I've had in years that I've kept unrooted, so I didn't initially realise.
?
Np, i took the phone to service center for JTAG, hopefully they will manage to fix it somehow
Exanneon said:
Try installing this driver, then transfer/flash the bootloader, I can't help you with the actual img though.
http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/#
Click to expand...
Click to collapse
This is not related to driver, bot Qualcomm and Quectel 9008 drivers work and allow communication with the phone, patch level is too high so blankflash files dont pass and dont allow bootloader to be flashed. Only solution is JTAG or motherboard replacement if patch level is higher than one in april 2017 i think.
Rip another cedric.
{
"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"
}
This has happened to me and I'm lucky had the assistance replaced the motherboard of the device. Your bootloader was not deleted, it was moved to a temporary partition that the boot script cannot find after pressing to start.
The problem with the manufacture is of the appliance was to have the bootloader on the same chip as the other partitions, causing the device to be easily hardbroken.
Solution? None so far.
I saw a guy who unbricked a potter (G5 Plus), but I've seen nothing from the G5.
Heh, another G5 killer here. A bad attempt at downgrading due to IMEI 0 left it as QLoader 9008. I guess I'll have to go back to my old Nexus 4.
Motorola sucks bad, Google and Xiaomi for instance have tools to recover dead bootloader eg. "Mi Flash", motorola gave developers easy bootloader unlock but no way to recover it, whats the point then, either make it recoverable or make it non erasable easily.
magix01 said:
Guys i am trying to make unbrick method for Cedric, does anyone have 5 minutes of time to make loader.img, all you have to do is to be on firmware .93, bl unlocked and rooted.
Type in terminal emulator dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
And upload me that file, it will be around 160mb, i will try to test it and if it works upload the tutorial. The command above just reads your mmmcblk0 so there is no chance of bricking your device.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1H2Qkc1XKbr7Is46n5xdCFlgiuIH1m-vE/view?usp=sharing
abhimanyuk said:
https://drive.google.com/file/d/1H2Qkc1XKbr7Is46n5xdCFlgiuIH1m-vE/view?usp=sharing
Click to expand...
Click to collapse
It doesn't seem to work for me. It might be because I had the latest January update when I killed my Cedric.
These .img files should boot bootloader directly from SDCard but it seems thar Cedric does not support this feature, so only way is JTAG and non updated blank-flash file.
magix01 said:
These .img files should boot bootloader directly from SDCard but it seems thar Cedric does not support this feature, so only way is JTAG and non updated blank-flash file.
Click to expand...
Click to collapse
Yeah, I tried with two different SD*cards, but the device would only blink the notification light while being recognised as Qualcomm Loader.
Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
{
"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"
}
If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.
This is exactly what I needed; not necessarily a hand-holding or step by step, but a path forward to investigate. Thanks!
So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
41rw4lk said:
If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.
Click to expand...
Click to collapse
westec2 said:
So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
Click to expand...
Click to collapse
With a locked bootloader you can flash an official firmware that is the same revision or newer. So in short, yes.
Hello! I ended up using the smart tool; it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool; it was the easiest way without root to get updated. Once I had the right drivers installed and it recognized bootloader mode, LMSA was really easy to use.
despree said:
it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool.
Click to expand...
Click to collapse
How did you get the "right drivers" and how did you install them? Does the PC download them automatically when you attach the phone or did you need to find them and manually install them?
Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.
New to updating here
despree said:
Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.
Click to expand...
Click to collapse
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot
omiCar said:
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot
Click to expand...
Click to collapse
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.
despree said:
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.
Click to expand...
Click to collapse
Hi, thank you for your quick response, I will be attempting to do this tonight or tomorrow, I will circle back with an update, again thank you !
Backup phone first with LMSA
That's what I had to do so it would stop hanging at 51%. Use LMSA backup feature first then upgrade
I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.
Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...
bdizzle1686 said:
Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...
Click to expand...
Click to collapse
You can take any flashing all, use a tool to merge the sparsed system images and mount the system img and pull it that way if you really need it
wrenhal said:
I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.
Click to expand...
Click to collapse
Answered my own question. The flash worked fine. I switched over to the log at 51% and watched it copying files and eventually it finished up and the phone rebooted to Oreo. All in all, if say it took only fifteen to twenty minutes.
Sent from my KIW-L24 using Tapatalk
despree said:
Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/help/how-to-manually-update-att-motorola-z2-t3879143
Hello guys,
I received the following unbrick tool from my supplier in Shenzhen - China and wanted to share it with you since I noticed that many people are desperate to fix their RM6 and swap it to EU.
The process is super easy:
1) Download & extract the following .zip
https://mega.nz/file/ntBSxDKa#h9vUPGoWVyqtyDYWYmSgz8bE1_vNimBMAqTp9csvv-w
2) Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)
3) Open the MiTool application
4) in MiTool, select the folder images
5) Put your phone in EDL mode
6) Once connected, Click flash - the brushing process will start automatically.
7) Once done, force reset and Voilà!
There's an alternative as well: MultiportQLoader
I haven't tried it myself, feel free to try it and share the steps.
Im sorry if any details aren't clear, but I'm typing this while driving xD
Good luck and would appreciate a shout-out on insta @Out.Geeked ^^
THANK YOU SIR
To ask a dumb question, but is this only the 6 or for the pro as well?
Works for both
Thank you so much, it work after someone help me erase flash
Outgeeked.net said:
Works for both
Click to expand...
Click to collapse
Yeah I checked the model number against the box it came in and gave it a shot, now it shows the RM logo and then reboots to the bootloader lmao this phone legit hates me
*edit*
So I think either I'm doing something wrong or this phone is actually messed up. Checked the drivers, tried 2 other cables, all my USB ports and still all it does is briefly show the white "System Rebooting" screen and then the RM logo for about 20 seconds and then reboots to fastboot/bootloader.
MiFlash shows "couldn't find flash script" but otherwise looks like it goes through the reflash process completely but QLoader always fails with an error "Unknown chunk type cac2"
Does this unbrick method require the bl to be unlocked?
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Nocturne Seigneur said:
anyone lost their imei after doing this? hahahha
i did lost my imei, but manage to repair it but... it still doesnt detect mobile network idk what to do now lol
Click to expand...
Click to collapse
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
CyberWolf92 said:
Did you ever find a way to recover your IMEI? Turns out that I'm in the same situation as you with a lost IMEI
Click to expand...
Click to collapse
loool welcome to the club xD, I didn't found any solution yet, i will tell u once confirmed, for now i can write imei but mobile network still not functioning
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
cannon3025 said:
Does it actually work?
According to the file name, it's EU V3.10.
I thought we should apply the NA/Asia version.
Click to expand...
Click to collapse
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Nocturne Seigneur said:
yes it does work, some ppl lose imei some not idk why, mine lose imei and cant connect to any mobile network right now T^T
after u unbrick it, u can flash via local update to v4.13 i did that working fine
Click to expand...
Click to collapse
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
cannon3025 said:
After you update to V4.13, your phone still no IMEI right?
How about flashing it again?
Click to expand...
Click to collapse
its gone, forever lol
i just gave my phone to someone else to fix this, if he can.
[Guide] Restore Lost IMEIs / Repair Network or Radio Issues
I accidentally restored TWRP backup of another Zuk Z2 phone on my new pgone and in this process over-wrote the EFS partition. This left me with a phone having no IMEI, no mac for Wifi and Bluetooth. Effectively No Network on phone. Worried, I...
forum.xda-developers.com
this maybe work, havent test it out
Since we have the partition layout & the correct firehose, it should actually be a good practice by anyone wanting to play with their phone (BL unlock, root, dev, etc) to first dump the critical partitions.
That way, you can always restore. Example: EFS, misc, persist, etc.
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Same issue for @CyberWolf92
Alaryani said:
Thanks for your help
When I use MiFlash shows "couldn't find flash script"
Can you please help
My RM6pro restarting all time to fastboot mode after I tried to relock bootloader and oem
Now I need to solve this issue by using this tools
I am beginner
Thanks
Click to expand...
Click to collapse
Select the images folder and then hit flash.
Mine is alive again, no more problems.
I think I know why a lot of people have probably bricked their device after flash from CN to Global. If you do a local update, let the device REboot until the end. After the restart it uses the update.zip again. I think a lot of people did a factory reset immediately after the reboot (like me in Recovery) and the system can no longer find the update.zip.
Therefore, let the update run through, reboot until you are back in the system. Then you can do a factory reset.
Outgeeked.net said:
Select the images folder and then hit flash.
Click to expand...
Click to collapse
When I selected images folder shows "couldn't find flash script"
{
"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"
}
And when I go to edl mode my phone disappeard from list devices in MiFlash.
but still showing in driver manger
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
Alaryani said:
When I selected images folder shows "couldn't find flash script"
View attachment 5329645
And when I go to edl mode my phone disappeard from list devices in MiFlash.
View attachment 5329643
but still showing in driver manger
View attachment 5329647
What driver needs for this issue "Make sure all the drivers are installed correctly (Qualcomm, EDL etc...)" what else I need?
also when i did it on fastboot mode i face this massge
View attachment 5329661
Click to expand...
Click to collapse
you must be in edload mode not fastboot