Related
Ok I just need a little help and advice so if you one of you out there in XDAland can help I’ll be truly grateful…
I’ve got the 32gb Nexus 7 which I rooted via the Wugfresh method and added I CWM for my recovery and did the OTA update to Jelly Bean 4.2.1. The last 6 months life have been peachy. Even the misses and her iDevices are jealous of my little corner of Android heaven.
So last night pick up the 7 and notice it’s running a tad sluggish and I also notice the battery is low and flashing red, so I plug in the power cable and attempted to shut it down and it just hangs… I give it 5 minutes and still not shut down so I hold power & volume down and get in to the Bootloader from here I select start and the tablet just hangs on the Google cross (red, blue, yellow, green). This now happens every time I power down even though there has been a good charge (6 hours) done. If I now go back in the Bootloader and try selecting the Recovery Mode I get the Android robot with the red warning triangle and the words “No Command” and that’s it. If I try the factory reset of power button & volume up from recovery mode I get nothing.
From the bootloader I see
Fastboot Mode
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.13
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx
Signing - not defined yet
LOCK STATE - UNLOCKED
Can someone advise what the best thing I can do to revive the 7? I don’t mind losing the data but I’m just unsure what to do next. I’ve read a few threads but none pointed me in the direction I think I need to be in…
Thanks in advance for any help given.
That's funny as I put my 16gig nexus 7 on charge a couple of hours ago and just went to pick it up and it was on the bootloader screen, but I managed to reboot and everything is fine, its funny cos I've had similar experience with galaxy s3 but that was dead after a night on charge. I've sent the s3 of for repair under warranty thinking it was the sudden death syndrome on the s3, but now I'm worried the charger might be at fault.
Has anyone heard of a charger frying an android phone or putting nexus 7 in bootloader mode? Or is it just a coincidence?
Sent from my Nexus 7 using xda premium
@OP
The recovery you describe is the stock recovery. If you used an OTA process after rooting, probably that is what overwrote the CWM install you did previously - so that explains why you see what you do when you boot to recovery via the bootloader menu.
When you use the "reset by holding the power button down for 30 seconds" you are crashed the running OS and potentially corrupted any filesystems which are mounted "rw" (read-write). So, that might explain the bootloops that occurred thereafter.
You have a couple options, but before you try any of them, I would suggest that you observe the "power state animation" that occurs for about 10 seconds when you plug the tablet in to the charger with the tablet turned off: it shows you graphically how much charged the battery has. If the animation starts with a nearly all black battery, and then "fills up", the battery is still deeply discharged; if it is all white, or mostly all white, and the animation only "tops off" the battery, it has a good charge.
If that animation shows a battery which is still discharged, I would try to solve that problem before doing anything further. It was a low battery condition that got you into trouble in the first place; no point in making things even worse.
OK. Well, if you weren't a toolkit user, I would suggest a couple things that could be done manually using a custom recovery to attempt a repair of the /data filesystem, or rescuing your raw data for a later data recovery effort. But they involve command-line stuff, so me mentioning it is a waste of time. Suffice it to say that if you still have an unlocked bootloader and functioning drivers on your PC, you can re-install whatever custom recovery you want (using either fastboot or Wugfresh) and then use the capabilities of that custom recovery. Given that you didn't even realize that your custom recovery went missing until now, that's probably also a waste of time too - I probably can safely assume you don't know what its' full capabilities are.
So, flash a custom recovery and perform a reformat of the userdata partition ("Wipe Data" in TWRP, don't know what it is in CWM). You could even try taking a Nandroid backup before doing this, but the problem with doing this is that by default it will try writing to /data - so under the presumption that your userdata partition is hosed up, writing a whole lot of stuff to it (the backup) may not create a reliable backup image(s). With TWRP you could write backups to an external device, though.
That leaves a factory reset. If you do it with the stock recovery (simultaneously press power and vol-up for about 1 second after the recovery splash screen shows up to get the menu), it will erase EVERYTHING in the /data partition - including your everything in the psuedo-SD card.
Without any further learning on your part (abandonment of toolkits), it seems like the stock recovery factory reset is the least-effort solution for you. As I said, this will destroy ALL of your data on the device, but your device should return to a bootable condition. If you made any Nandroid backups and got them off the tablet, you could restore them after installing the custom recovery which made those same backups.
good luck
As last user said, if you have any nandroids you could restore them. And honestly it'd be so much easier to just boot an img. Not that hard.
Sent from my Motorola XPRT
Defibrillator...
Sent from my Nexus 7 using xda app-developers app
@bftb0
Thanks for the response and I’m going to follow your advice… I have done the command line root method twice with this my phones the HTC Desire and the then Sensation so I have experience in the dark art… it was just I couldn’t see a way of enabling the ADB drivers so my PC and 7 could look at/see each other but I have found the following http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
and this goes over what I need to do so I’ll give this a try and see how it goes. Like I say I don’t really need the data, I only used the 7 as a media hub and social media tool so I don’t mind putting the music and films back on it and the few apps and games is no big deal.
@FitAmp if this don’t work I may be taking your advice hahahahahaha!!!
bricked
slybunda said:
bricked
Click to expand...
Click to collapse
@slybunda May I ask why you say bricked?
Another case where the N7 seems to overly discharge the battery and not be able to recharge it. I've heard of this several times, it just won't charge the battery once it gets too low.
I bet if you can get the battery to charge it'll be fine. Or failing all else, this place has the battery for $30.
http://www.portatronics.com/product...oogle-Asus-Nexus-7-Original-Battery-Part.html
It is NOT bricked.
Dr Asqueroso said:
@slybunda May I ask why you say bricked?
Click to expand...
Click to collapse
Hi, Dr Asqueroso...
'Bricked' is a certainly a bit pre-emptive... if the BOOTLOADER is still good (and from your description, it sounds like it still is), then you have a very good chance of resurrecting your tablet.
The thing is, from your description, you're only 'bootlooping'... which is trivial to get out of... if you have a recent NANDROID backup (or for that matter, a flashable ROM .zip), on your internel storage and you know how to FASTBOOT FLASH a CUSTOM RECOVERY.
Your options are threefold...
----------------------
1) Use the STOCK FACTORY recovery to perform a factory reset. (As detailed by bftb0, earlier).
2) FASTBOOT FLASH a custom recovery (CWM or TWRP).
-- http://www.teamw.in/project/twrp2/103
-- http://www.clockworkmod.com/rommanager
I note you used CWM previously, so fastboot flash this recovery, and restore your last NANDROID backup. If you didn't make any NANDROIDs, then flash some other CUSTOM ROM. Or better still, use the 'wipe data' option in your Custom Recovery. I've had 'bootloops' and other weird egregious behavior myself, and this usually fixes it. (Sometimes, even wiping 'CACHE' and 'DALVIK' can make mysterious problems vanish!.)
3) Restore back to FACTORY stock.
-- http://developers.google.com/android/nexus/images
(You need the 'nakasi' version for your 'grouper' tablet).
This last option carries some risk, because it reflashes the BOOTLOADER, which is always a risky procedure (a corrupt flash will hardbrick the tablet). So, ABSOLUTELY make sure your tablet is fully charged AND you have a good USB connection to your PC.
I note you're still on bootloader v4.13, so you could edit the 'flash-all.*' script from Factory Stock JellyBean 4.1.2 (JZO54K) to remove the command to flash the bootloader. Flash as normal (by running the script), and then take the OTA update to 4.2.2 (JDQ39) over WiFi... this will still update the bootloader (to v4.18), but because of the way OTAs work, the risk is significantly reduced.
----------------------
But before you contemplate doing any of this... you need to ascertain if your battery is in good shape.
Here's what I would recommend if the battery is failing to charge correctly...
1. Plug the Nexus 7 into a wall charger.
2. Immediately press Volume Down and Power at the same time to reach the Bootloader
3. From the Bootloader menu, press Volume Down until you see “Power Off Device.”
4. Press the Power button to select the "Power Off Device" option.
5. Once your device is off, unplug the charger and then plug it back into the device.
If you see a large white battery shaped logo, that is flashing nearly all white, then you have a good level of charge... if it's flashing nearly all black (with only a bit of white), then the charge level is low... and fastboot flashing anything is not recommended.
Good luck... and hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, Dr Asqueroso...
'Bricked' is a certainly a bit pre-emptive... if the BOOTLOADER is still good (and from your description, it sounds like it still is), then you have a very good chance of resurrecting your tablet.
The thing is, from your description, you're only 'bootlooping'... which is trivial to get out of... if you have a recent NANDROID backup (or for that matter, a flashable ROM .zip), on your internel storage and you know how to FASTBOOT FLASH a CUSTOM RECOVERY.
Your options are threefold...
----------------------
1) Use the STOCK FACTORY recovery to perform a factory reset. (As detailed by bftb0, earlier).
2) FASTBOOT FLASH a custom recovery (CWM or TWRP).
-- http://www.teamw.in/project/twrp2/103
-- http://www.clockworkmod.com/rommanager
I note you used CWM previously, so fastboot flash this recovery, and restore your last NANDROID backup. If you didn't make any NANDROIDs, then flash some other CUSTOM ROM. Or better still, use the 'wipe data' option in your Custom Recovery. I've had 'bootloops' and other weird egregious behavior myself, and this usually fixes it. (Sometimes, even wiping 'CACHE' and 'DALVIK' can make mysterious problems vanish!.)
3) Restore back to FACTORY stock.
-- http://developers.google.com/android/nexus/images
(You need the 'nakasi' version for your 'grouper' tablet).
This last option carries some risk, because it reflashes the BOOTLOADER, which is always a risky procedure (a corrupt flash will hardbrick the tablet). So, ABSOLUTELY make sure your tablet is fully charged AND you have a good USB connection to your PC.
I note you're still on bootloader v4.13, so you could edit the 'flash-all.*' script from Factory Stock JellyBean 4.1.2 (JZO54K) to remove the command to flash the bootloader. Flash as normal (by running the script), and then take the OTA update to 4.2.2 (JDQ39) over WiFi... this will still update the bootloader (to v4.18), but because of the way OTAs work, the risk is significantly reduced.
----------------------
But before you contemplate doing any of this... you need to ascertain if your battery is in good shape.
Here's what I would recommend if the battery is failing to charge correctly...
1. Plug the Nexus 7 into a wall charger.
2. Immediately press Volume Down and Power at the same time to reach the Bootloader
3. From the Bootloader menu, press Volume Down until you see “Power Off Device.”
4. Press the Power button to select the "Power Off Device" option.
5. Once your device is off, unplug the charger and then plug it back into the device.
If you see a large white battery shaped logo, that is flashing nearly all white, then you have a good level of charge... if it's flashing nearly all black (with only a bit of white), then the charge level is low... and fastboot flashing anything is not recommended.
Good luck... and hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
First of all a massive Thank You all so much for the advice...
I think I've got it in the respects of each step but I'm just stuck with getting the drivers to work. I've installed the Java Dev Kit, the latest SDK from the Android site and successfully installed both the Tools and the Google USB Drivers. I also got the Asus drivers for the 7 and I have unziped the stock recovery JZO54K which ready to go. However can't get my 7 to show up in CMD Prompt via ADB devices string but if add my sensation it pops up everytime...
I've tried this process on a Windows 8 machine and a XP install too and the 7 is never picked up.
Does this mean the 7 is dead and stuck in the factory boot menu? What am I doing wrong?
This is killing me... :crying:
Dr Asqueroso said:
First of all a massive Thank You all so much for the advice...
I think I've got it in the respects of each step but I'm just stuck with getting the drivers to work. I've installed the Java Dev Kit, the latest SDK from the Android site and successfully installed both the Tools and the Google USB Drivers. I also got the Asus drivers for the 7 and I have unziped the stock recovery JZO54K which ready to go. However can't get my 7 to show up in CMD Prompt via ADB devices string but if add my sensation it pops up everytime...
I've tried this process on a Windows 8 machine and a XP install too and the 7 is never picked up.
Does this mean the 7 is dead and stuck in the factory boot menu? What am I doing wrong?
This is killing me... :crying:
Click to expand...
Click to collapse
No... it just means you're stuck in what is ubiquitously called 'driver hell'. Windows has always been a pain in the arse when it comes to drivers.
If you have a Windows XP box, you could try the following...
Download my copy of the FASTBOOT/ADB files for XP...
http://dl.dropboxusercontent.com/u/...orXP-MD5_8e02ab9b4b8463b9ee5c2063477b01ec.zip
Unzip to a folder on the Windows Desktop.
Unzip and copy the files from nakasi-jzo54k into the same folder.
You should now have a folder with the following files in it...
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...
Code:
fastboot flash bootloader bootloader-grouper-3.41.img.
This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.
-----
Boot your Nexus 7 into BOOTLOADER mode, by pressing Vol. Down (& hold) and the Power Button.
Connect your Nexus 7 to your Windows XP PC, via a USB cable (preferably the one that shipped with the N7 originally).
Open a command prompt window on the folder into which you have copied all of the aforementioned files, and type...
Code:
fastboot devices
It should return a SERIAL NUMBER... if it does, you have a working FASTBOOT connection, and you're free to run flash-all.bat
This should restore JellyBean 4.1.2... and upon a successful reboot and a WiFi connection, an OTA upgrade will be proffered.
Allow this, and your Nexus will be upgraded to JellyBean 4.2.2 (JDQ39).
Good luck.
Rgrds,
Ged.
Okay so I have a folder with the following
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
But I'm stuck on the edit line?? sorry for being a pain can you explain this bit.. how do you edit the flash-all.bat??
Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...
Code:
fastboot flash bootloader bootloader-grouper-3.41.img.
This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.
Open the bat file in notepad.
Sent from my Galaxy Nexus
Done the edit and ran the flash-all.bat... The serial number has appeared after the fastboot command but now I seem stuck on the sending system command of 446268 been like this for 20+ minutes and somehow my bootloader is showing 3.41 on the tablet.
What next?
Dr Asqueroso said:
Okay so I have a folder with the following
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
But I'm stuck on the edit line?? sorry for being a pain can you explain this bit.. how do you edit the flash-all.bat??
Click to expand...
Click to collapse
Sometimes it's easier to 'just do' than explain 'how to do'...
Here is the modified 'flash-all.bat' script, with the line removed.
http://dl.dropboxusercontent.com/u/37483979/flash-all-MD5_ a687082ef3179feb40ba108436dc5768.zip
------
Maybe I'm just being overcautious when it comes to BOOTLOADER stuff...
It's entirely possible you could just run the original 'flash-all.bat' as is... without problems... as many people do, and as Google intended.
So, it's not critical you delete bootloader-grouper-3.41.img or run the modified .bat file... just ensure you have a damn good USB connection and power to both devices before you do.
Rgrds,
Ged.
---------- Post added at 12:55 AM ---------- Previous post was at 12:41 AM ----------
Dr Asqueroso said:
Done the edit and ran the flash-all.bat... The serial number has appeared after the fastboot command but now I seem stuck on the sending system command of 446268 been like this for 20+ minutes and somehow my bootloader is showing 3.41 on the tablet.
What next?
Click to expand...
Click to collapse
Sending /system has always been problematic for me as well... you need to change to a different USB port on your PC.
Using the Vol. Keys navigate to RESTART BOOTLOADER... disconnect and reconnect to a different USB port, and try again.
If you're BOOTLOADER is showing 3.41, don't worry about it. The issue was never about the version, but about flashing it.
This will be taken care of later, with the OTA upgrade.
Rgrds.
Ged.
There must be something else going wrong as every step I've taken thus far has worked but the final sending bit... currently on my machine see the following... it's been like this for 2 hours...
Dr Asqueroso said:
There must be something else going wrong as every step I've taken thus far has worked but the final sending bit... currently on my machine see the following... it's been like this for 2 hours...
Click to expand...
Click to collapse
2 hours is way too long... it should take less than 5 minutes to flash back to stock.
I suspect a USB connectivity issue... open another command prompt window, and type
Code:
fastboot devices
If you don't see a SERIAL NUMBER, then your FASTBOOT connection has died...
Try again, from a different USB port... and maybe a different USB cable.
----
You are actually getting somewhere though... your screenshot indicates that 'boot' went over successfully.
Don't give up hope - persevere!
Rgrds,
Ged.
Ok I'll try it again when I get home from work...
Okay followed all the steps but I think the tablet is not going to play nice... I just can't get past the sending system bit.
The 7 is now showing
Fastboot Mode (in red)
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.18
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx (now showing my number)
Signing - not defined yet
LOCK STATE - UNLOCKED
My CMD prompt window is yet again just showing sending system and nothing. Been like this for the past 30 mins or so... I've swapped my USB ports over tried and the process a few times and still no joy. I think I've been defeated.
It looks like the 7 will have to go back... but can I make a warranty claim from Asus in it's current state or will I have to lock it somehow??
Failing that I'll "lose" it and claim off the house insurance.
Oooops the CMD window is doing something different...
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4944 KB)...
OKAY [ 0.656s]
writing 'boot'...
OKAY [ 0.203s]
sending 'recovery' (5446 KB)...
OKAY [ 0.719s]
writing 'recovery'...
OKAY [ 0.219s]
erasing 'system'...
OKAY [ 0.094s]
sending 'system' (471804 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5264.891s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
< waiting for device >
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
C:\android-sdk\platform-tools>
Anyone with any suggestions as to my next move?
Hi there
@bftb0 : yet another victim of the corrupt bootloader .img ! (see thread #2573015)
bftb0 said:
The versions distributed with JWR66Y and KOT49H* Google factory images are INVALID.
Click to expand...
Click to collapse
Device : Nexus 7 2012 wifi (grouper), stock 4.4.4 KTU84P, never rooted before
Symptoms : black screen, not booting at all even to bootloader. :crying:
Only faint light of hope is that my PC is still reacting to plugging the Nexus in with USB.
Windows beeps and shows an "unknown usb device" error then fails finding a driver.
Windows Device manager shows "APX" with yellow sign below "Other devices".
Question : bricked or any hope left ? Pleeease what can I do ?
How I got there :
NRT hung when flashing bootloader while reinstalling stock 4.4.0 (nakasi-krt16s-factory-da7dee49).
The story, going from bad to worse :
It started with a sudden reboot for not appearent reason (incidentally while an Avast routine scan was running).
Then endless reboot, with the 4 color balls shaking indefinitely (power plugged in or not).
Looked at forums... Reboot into bootloader. Recovery mode, wiped cache. Got plenty of error msg "E:failed to mount /cache"
Bootloop! Sometimes showing just the white Google logo, sometimes showing the rolling colors for a few seconds.
Recovery mode, erase user data (no backup, hate this thing). Again plenty of error msg "E:failed to mount /cache"
Could the missing /cache be related to Avast since the first reboot occurred while it was running? Maybe the theft protection is overly proctective?
Installed Nexus Root Toolkit 1.8.4 (extremely well done utility btw, ***huge congrats*** :good on Win 7 64bits. Installed drivers #1.
Tried flashing a clean 4.4.4 (nakasi-ktu84p-factory-76acdbe9).
FAILED (remote: Bootloader is locked.)
Successfully unlocked bootloader with NRT. Restart with an open lock below the white Google logo. So far so good.
Try flashing 4.4.4 again, same image.
writing 'bootloader'... FAILED (remote: (InvalidState))
What the heck ?!
Found the thread #2573015 I was quoting above on corrupt bootloader .img files from Google.
As it turns out, the bootloader MD5 is also WRONG in KTU84P.
Managed somehow to restart into bootloader again in spite of the bad bootloader...
Maybe the old one was not completely replaced yet?
Quick quick, let's try flashing another bootloader that works !
This time use the latest available with a non-corrupt bootloader .img : 4.4.0 (nakasi-krt16s-factory-da7dee49)
erasing 'boot'... blahblah
sending 'bootloader' (2100 KB)... OKAY [ 0.281s]
writing 'bootloader'... *** STUCK ***
Wait and wait until lost hope
Tried rebooting but nothing happens, just black screen, I end up with the symptoms I described upfront.
When plugged into the pc, keeping power button down makes windows beep, and the "APX" unknown device comes and goes in win device manager. Adding the vol+ or vol- buttons (or both) produces identical results.
Uninstalled APX device from PC. Power button down. Windows beeps "unknown usb device". "APX" shows up again in device manager... And so on.
Screen still pitch black.
Any other USB driver I can try to regain a working connection?
Worth looking into other remedies, like nkFlash?
GedBlake said:
If you corrupt, or erase the bootloader... the Nexus 7 is dead, from which there is known recovery. Although it's been speculated that an nvFlash tool could flash a new bootloader.
Click to expand...
Click to collapse
Thanks for reading me so far, I know it's long, but if you've read to this point maybe you can help?
What a similar story
this is such a coincidence as I have also had the dreaded bad to worse stage as my story started off here http://forum.xda-developers.com/showthread.php?t=2783631 and then got much worse and it continues here http://forum.xda-developers.com/showthread.php?t=2798181 .
I have been searching on the internet for the last month and so far there does not seem to be any general solution (which does not require hardware device surgery) to this particular type of problem as it is not something Google appear to have expected. I found that a lot of people seem to say its hypothetically possible to repair this thing via software means as that is how it was rendered inoperable in the first place and they also say it is not practically possible to hard brick any device through software means although with the nexus 7 there seems to be some kind of issue with crypto-signing which makes it a nightmare to access the hardware through nvflash unless there was some blob file made before hand
I am currently discussing the situation in this thread and you could join it to keep up to date
http://forum.xda-developers.com/showthread.php?t=2798181&page=2
Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
http://forum.xda-developers.com/oneplus-2/general/guide-oneplus-2-mega-unbrick-recover-t3397257
I have tried all those methods and none of them worked for me
pankaj2m said:
I have tried all those methods and none of them worked for me
Click to expand...
Click to collapse
Go to oneplus website & download official rom zip file. Push it into sdcard using fastboot. Go to stock recovery (vol_down + power) & flash the zip file.
I can't boot into to recovery hence can't flash.. I have the official rom zip from oneplus but can't flash it as I can't boot into recovery.. That's the problem
Can anyone please help me with this?? :'(
pankaj2m said:
Hi Guys,
My OnePlus 2 has this issue where if i restart the phone it gets stuck on the Boot Screen which shows OnePlus Logo powered by Android.
I can boot my phone to Fastboot and i can only boot into the phone by using command "fastboot continue"
When i try to use command "fastboot oem unlock" the phone reboots and gets stuck on the OP logo
Fastboot oem device-info shows
... INFO Device tampered: true
INFO Device unlocked: false
INFO Device is_verified: false
INFO Charger screen enabled: false
INFO Display panel:
INFO console_locked: 1
INFO exec_console_unconsole: 0
OKAY
and if i try to install twrp recovery by using the command "fastboot flash recovery recovery.img" i get the following message
sending 'recovery' (25956 KB)... OKAY
writing 'recovery'... FAILED (remote: device is locked. Cannot flash images)
Please help
Click to expand...
Click to collapse
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
eldos777 said:
Try the first method in this page https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Its worked in my mobile, when i lost everything (even fastboot also gone). Its surely work. It will flash Oneplus 2 official recovery. You should ensure that your device is detected in your computer and Its shows as Qualcomm 9008
Click to expand...
Click to collapse
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
pankaj2m said:
I followed the all the 3 methods from the post you mentioned.
When i run MSM8994DownloadTool and START, it just stays there. I waited for 1hr for something to happen but nothing.
It Doesnot work for me.
For now, i use Fastboot Continue command in fastboot in case my devices shuts down
Click to expand...
Click to collapse
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
eldos777 said:
Thats means your device is not detected, Did you check device manager in your computer? Is is showing your mobile as Qualcomm 9008?? If it is not please follow the steps on the website, I already given. No need wait 1 hr. If your device is detected, then you can see a green line, and it will finish within 5mnts.
Click to expand...
Click to collapse
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
pankaj2m said:
Hi Eldos,
In device manager it shows as RELINK HS-USBQDLoader 9008 (COM8)
i followed your instructions but it still does not work. When i run the MSM8994DownloadTool, it does not do anything.
Anything else i can try. I am stuck in this big problem. When my phone switches off, the only way i can boot is by going to FASTBOOT and running command "fastboot continue" only then my phone boots.
Please help.
Thanks,
Pankaj
Click to expand...
Click to collapse
Can you come in Team Viewer??
eldos777 said:
Can you come in Team Viewer??
Click to expand...
Click to collapse
Yes, sure.. how do i talk to you?
pankaj2m said:
Yes, sure.. how do i talk to you?
Click to expand...
Click to collapse
Give me your Teamviewer ID and Password
eldos777 said:
Give me your Teamviewer ID and Password
Click to expand...
Click to collapse
ID: 527533613
Password: 6953
pankaj2m said:
Can anyone please help me with this?? :'(
Click to expand...
Click to collapse
PM me
Problem Solved
Deep problem
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
CharlieVasquez said:
I have gone through all the unbrick guides, even with a Oneplus technician but we weren't able to unbrick it. I'm guessing that after the oxygen 3.0.2 update, I wiped out the partition (not sure). The phone was unlocked with some TWRP version before that. I totally forgot to update it the right way. I can get use fastboot to go into the OS, but trying to flash doesn't work since it's locked. Trying to unlock it supposedly works but it remains locked. We tried the Qualcomm drivers, installed the certificates and the device is seen as Qualcomm 9800 yadda, yadda, yadda, but the MSM8994DownloadTool.exe doesn't detect the device, therefore it stays there doing nothing. Yes, we changed the developer options in the settings but nothing seems to work. The LTE doesn't work properly either...it shows an exclamation mark, so I have to switch to 3G. I'm in dire need of help, and if anyone can help me, you'd certainly qualify for a master tech support agent or something cause not even they could help me with this. Thanks in advance if any of you can help! I'm using a Windows 10 on a Mac, using Parallels VM...
Click to expand...
Click to collapse
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
CharlieVasquez said:
I finally got the MSM tool to detect the phone. While still in Qualcomm mode, I disconnected it and connected it to the to Mac usb ports and kept clicking on the tool to start. The green lights finally showed and I'm waiting to see what happens. I will keep you updated.
Click to expand...
Click to collapse
K, I finally booted normally into the OS, went back and rooted the phone. Now we're good to go again. Not even the tech support agents were able to help me with this one.
I ran into a bit of an issue and am stuck with a bootlooping G6 US997.
What got me into this pickle:
I unlocked the bootloader
I flashed TWRP successfully, by:
Running fastboot flash recovery TWRP.img
Unplugging USB and holding Vol- and Power from fastboot, then lifting and re-pressing Power when the LG logo appeared
Hitting Yes, Yes
Being in TWRP and allowing modification of System
Formatting Data (Wipe > Format Data > Yes)
I installed the DM verity and encryption file so that it would boot
I wiped Cache/Dalvik
I rebooted into System
It booted successfully so I went back to TWRP and installed Lineage OS, Open Google Apps, and the Lineage SU addon
This booted successfully, so I went and with OEM unlock disabled booted into fastboot to see if I could get rid of the annoying orange screen at the start saying that the bootloader was unlocked
To do this, I ran fastboot oem lock, not seeing/ignoring the red text at top telling me to Please check "Enable OEM unlock" in Developer options.
I then rebooted with fastboot reboot and I encountered a red warning: "Your device has failed a routine safety check and will not boot." It is now in a bootloop at that screen, cycling between black, the LG logo, and the warning.
I managed to enter recovery mode (with the key-combo) and got the stock recovery "factory reset and wipe" option, which I had been previously getting when entering TWRP, so I selected "Yes, Yes" and then it went back into the bootloop, completely avoiding TWRP.
Where I currently am:
I can get into fastboot mode (Vol- with usb plugged in) and I can get into the factory reset mode which is the gateway into TWRP. I cannot get into TWRP, and I cannot flash anything, boot into any images, or unlock the bootloader ( Please check "Enable OEM unlock" in Developer options). If I could do that I think I can get it fixed.
My questions:
How can I do the OEM unlock without access to Developer Options? (I have the unlock file to flash, just need access)
Or How can I bypass the red warning page and boot into Lineage OS?
Any help would be appreciated, I really would like to get this working.
Have you tried to boot in download mode and flash the original firmware with LGUp+Uppercut?
Killua96 said:
Have you tried to boot in download mode and flash the original firmware with LGUp+Uppercut?
Click to expand...
Click to collapse
I've been trying to, I forgot to update the post though. I found the US99715a_05_0908 KDZ, and I installed Uppercut, LGUP, and the drivers from the Uppercut thread, but whatever I do it never recognizes the device. And when I go into download mode it quickly pops back out to the warning screen after about 10 seconds. After the warning it reboots in 10 seconds, I have a pretty small window.
I was thinking of trying LG Flash Tool 2.0.1.6, yet I haven't figured out how to use it yet. I may try more with Uppercut, maybe different drivers? If there were a way to keep it in download mode longer, that would really help. Thank you for replying, I've seen your name around the forums!
mwsundberg said:
I've been trying to, I forgot to update the post though. I found the US99715a_05_0908 KDZ, and I installed Uppercut, LGUP, and the drivers from the Uppercut thread, but whatever I do it never recognizes the device. And when I go into download mode it quickly pops back out to the warning screen after about 10 seconds. It looks like it might still be in download mode, but interrupted by the warning, the way the screens flash. After the warning it reboots in 10 seconds, I have a pretty small window.
I was thinking of trying LG Flash Tool 2.0.1.6, yet I haven't figured out how to use it yet. I may try more with Uppercut, maybe different drivers? Thank you for replying, I've seen your name around the forums!
Click to expand...
Click to collapse
I know this could be a stupid question, but have you tried to run the unlock command? If yes, what does it says?
Killua96 said:
I know this could be a stupid question, but have you tried to run the unlock command? If yes, what does it says?
Click to expand...
Click to collapse
fastboot flash unlock unlock.bin gives:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.047s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.063s
I had flashed it before but forgot to reenable the option in developer tools, I can't find a way to enable it from fastboot yet.
mwsundberg said:
fastboot flash unlock unlock.bin gives:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.047s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.063s
I had flashed it before but forgot to reenable the option in developer tools, I can't find a way to enable it from fastboot yet.
Click to expand...
Click to collapse
You can't, fastboot is a mode that allows many things but it's not a God-like mode where you can do everything.
By locking the bootloader while having unsigned partions flashed you have essentially hard bricked the device, and if the only way to flash stock signed partitions (lgup+Uppercut) doesn't work it means that you have to find a way to boot the phone in qhsusb9008 (usually by hardware) and try to flash a tot file, if there is one.
Sorry but is highly unlikely that you will able to recover your G6, hope to be wrong.
Killua96 said:
You have to find a way to boot the phone in qhsusb9008 (usually by hardware) and try to flash a tot file, if there is one.
Sorry but is highly unlikely that you will able to recover your G6, hope to be wrong.
Click to expand...
Click to collapse
How might I go about doing this, or is there a chance I can actually access LGUP and have just been messing up so far? If there were a video of what using LGUP and Uppercut properly looked like, that would be really helpful.
Also, is there any hope of LG or a phone store with LGUP being able to fix this (for less than the price of a new G6)?
mwsundberg said:
Also, is there any hope of LG or a phone store with LGUP being able to fix this (for less than the price of a new G6)?
Click to expand...
Click to collapse
It depends on how much it'll cost to you a new G6, they could ask you maybe 200-250 bucks.
mwsundberg said:
How might I go about doing this, or is there a chance I can actually access LGUP and have just been messing up so far? If there were a video of what using LGUP and Uppercut properly looked like, that would be really helpful.
Click to expand...
Click to collapse
Go in fastboot with the phone connected to the PC, keep pressed vol- and power until the phones turn off in that exact moment leave those two buttons and keep pressing only the vol+ one, this should bring you in download mode, if it stuck then you could use LGUP and Uppercut, otherwise there is nothing software related that you can do, imho obviously
Killua96 said:
Go in fastboot with the phone connected to the PC, keep pressed vol- and power until the phones turn off in that exact moment leave those two buttons and keep pressing only the vol+ one, this should bring you in download mode, if it stuck then you could use LGUP and Uppercut, otherwise there is nothing software related that you can do, imho obviously
Click to expand...
Click to collapse
Managed to get a messed up G6 from a friend working again. Thanks. XDA forever
Guys, need help !!!
I have tried to install SEA oreo version on Indian phone via LGUP... Flash was successful (100%) but it got stuck on LG Logo..
Procedure followed for H870DS (IND)
1. Downloaded SEA Oreo KDZ File (H870DS20a_00_OPEN_SG_DS_OP_0518.kdz)
2. Installed LGUP... Made new Common folder inside C/Prog file/LG/Model
3. Extracted DLL file from KDZ & renamed it LGUP_Common.dll and kept in Common folder
4. Entered in download mode
5. Opened LGUP.. selected KDZ and Upgrade..
6. Boom.. 100% completed.. it has shown that phone is rebooting..
7. But then it got stuck on LG Screen
I cant access recovery now
I can open Hard Reset option (Vol down+Power) only.. Made hard reset but no use
I cant enter in download mode
I dont know if it is charging or not
It is not even switching off by pressing power button for long time
Pl help me...
---------- Post added at 08:33 PM ---------- Previous post was at 08:30 PM ----------
it has anything to do with "Enable OEM unlock" in Developer options"
There is a way to enter download mode. Just hold down button and power button. Just when you see LG logo leave power button for a second. Push power button again and hold with down button. Now press yes twiche for the hard reset prompt. Now IMPORTANT, when screen goes black immediately press and hold up button. While holding up button plug usb cable into the PC. Now use Uppercut 1.0.0.0 and flash your kdz.
Same issue, Just that I was trying downgrade to Nougat. Oreo messed up my phone to the extent that, none of the sensors (including Fingerprint are not working). The load was a success, but after 1st restart it went into boot loop.
I only had USB Debug enabled in the DO before this issue, so it might work with the OEM unlock dissabled.
Software needed...
LG Bridge
Meathod...
Please charge the phone before this is done, at least 80%, will be better.
Connect the computer with LG G6 H870DS (Indian), might work for all models. "not tested"
If the USB debug is enabled, you will hear the USB disconnection and connection notification sound during bootloop
When you hear disconnection sound, press the "volume up key" until the Firmware Update mode appears
Once you are in Firmware Update mode, the USB connection will be stable (In bootloop, it keeps disconnecting)
Disconnect the USB cable
Start LG Bridge/Software Updates, connect when App asks to connect the phone
This will update you phone to the latest official software update..
This solution can work for all phones that have a hardware based menu to get into Firmware Update mode, definitely works on all LG phones to get out of bootloop. I have tested on LG G2, G4 and G6 Indian devices.
And a suggestion to all mates is, to enable USB debugging and the OEM unlock as soon as you get hands on your new devices. Always saves the hassle of running around the LG service center, its a big issue in India at-least. I love LG for its hardware quality but sadly LG smartphones have a bad history of software issues
Hi,
Messed up badly Furious that ZTE made the phone incompatible with Daydream, decided to root the device. Tried various ROMs, but could never get the modem to work in the UK. Eventually tried to reinstall Chinese stock ROM and, to my surprise, the modem still didn't work. Attempted to restore the modem files from TWRP backup and bricked the phone completely. Can only boot into Chinese recovery where only ADB sideload enables the phone to be seen by Windows as Android ADB Interface. EDL mode cannot be seen and Axon7toolkit cannot see the phone even in ADB sideload mode. Attempts to update software result in this message: Package expects build fingerprint of ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys or ZTE/P996A03/ailsa_ii:7.1.1/NMF26F/20170224.135053:user/release-keys ; this device has ZTE/P996A03/ailsa_ii:7.1.1/NMF26V/20170912.013327:user/release-keys. Most likely, updates won't work anyway, because when the phone was running, updates resulted in a mismatch. Any feedback would be much appreciated.
tretayuga said:
Hi,
Messed up badly Furious that ZTE made the phone incompatible with Daydream, decided to root the device. Tried various ROMs, but could never get the modem to work in the UK. Eventually tried to reinstall Chinese stock ROM and, to my surprise, the modem still didn't work. Attempted to restore the modem files from TWRP backup and bricked the phone completely. Can only boot into Chinese recovery where only ADB sideload enables the phone to be seen by Windows as Android ADB Interface. EDL mode cannot be seen and Axon7toolkit cannot see the phone even in ADB sideload mode. Attempts to update software result in this message: Package expects build fingerprint of ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys or ZTE/P996A03/ailsa_ii:7.1.1/NMF26F/20170224.135053:user/release-keys ; this device has ZTE/P996A03/ailsa_ii:7.1.1/NMF26V/20170912.013327:user/release-keys. Most likely, updates won't work anyway, because when the phone was running, updates resulted in a mismatch. Any feedback would be much appreciated.
Click to expand...
Click to collapse
You messed up real bad. I assume you forgot to flash the modem files when you flashed the custom ROMs?
EDL mode cannot be seen? What do you mean by that? Keep the Device Manager open, phone disconnected; then hold both volume buttons, wait 5 seconds, connect the USB cable while you are holding them, and wait 3 seconds more before releasing them. The device manager should refresh.
The phone should appear under Ports (COM & LPT) or under USB devices as QUSB_BULK. If it is under USB devices you have to right click on it, Uninstall -> Delete driver software. After that hold all 3 buttons for a long time (both volume buttons and power) and device manager should refresh itself. It should install the Qualcomm driver then. If the driver is ZTE handset diagnostic interface, you'll have to disassemble the phone
Choose an username... said:
You messed up real bad. I assume you forgot to flash the modem files when you flashed the custom ROMs?
EDL mode cannot be seen? What do you mean by that? Keep the Device Manager open, phone disconnected; then hold both volume buttons, wait 5 seconds, connect the USB cable while you are holding them, and wait 3 seconds more before releasing them. The device manager should refresh.
The phone should appear under Ports (COM & LPT) or under USB devices as QUSB_BULK. If it is under USB devices you have to right click on it, Uninstall -> Delete driver software. After that hold all 3 buttons for a long time (both volume buttons and power) and device manager should refresh itself. It should install the Qualcomm driver then. If the driver is ZTE handset diagnostic interface, you'll have to disassemble the phone
Click to expand...
Click to collapse
Thanks. The phone is listed as ZTE Handset Diagnostic Interface(DFU) (COM10) in Ports. It is listed as Unknown USB Device in USB Controllers and following the procedure you described doesn't install the Qualcomm driver. I take it, then, that an engineer would have to disassemble the phone.
tretayuga said:
Thanks. The phone is listed as ZTE Handset Diagnostic Interface(DFU) (COM10) in Ports. It is listed as Unknown USB Device in USB Controllers and following the procedure you described doesn't install the Qualcomm driver. I take it, then, that an engineer would have to disassemble the phone.
Click to expand...
Click to collapse
Or you. Follow the 4th category brick repair manual. I'm just rewriting it but it'll take time
Where are you getting adb sideload from?
Choose an username... said:
Or you. Follow the 4th category brick repair manual. I'm just rewriting it but it'll take time
Where are you getting adb sideload from?
Click to expand...
Click to collapse
Well, with your help I may snatch victory from the jaws of defeat. I'll ask one of the local engineers to dismantle the phone according to your guide and we'll see what we can do. The adb sideload screen is in this photo.
Thanks again.
tretayuga said:
Well, with your help I may snatch victory from the jaws of defeat. I'll ask one of the local engineers to dismantle the phone according to your guide and we'll see what we can do. The adb sideload screen is in this photo.
Thanks again.
Click to expand...
Click to collapse
You still have one other option though. May save you.
Do you have an SD card? If not, get at least a 4 GB one (or one with 3gb free), download an official A2017 update package, unzip it and put the update.zip in the sd card. (If you get a bunch of folders instead of a file called update.zip just take the original zip and put it in the SD).
after that, put it in the sd card and select the option that says 'sd'.
It may work. Right now it's your best shot at not taking it apart
Choose an username... said:
You still have one other option though. May save you.
Do you have an SD card? If not, get at least a 4 GB one (or one with 3gb free), download an official A2017 update package, unzip it and put the update.zip in the sd card. (If you get a bunch of folders instead of a file called update.zip just take the original zip and put it in the SD).
after that, put it in the sd card and select the option that says 'sd'.
It may work. Right now it's your best shot at not taking it apart
Click to expand...
Click to collapse
That's forbidden. When I've tried to update from the SD card using that option, I get a message saying I don't have permission to update from the SD card. I will, however, try again because you've mentioned some things that are slight variations on what I've done before.
tretayuga said:
That's forbidden. When I've tried to update from the SD card using that option, I get a message saying I don't have permission to update from the SD card. I will, however, try again because you've mentioned some things that are slight variations on what I've done before.
Click to expand...
Click to collapse
Yeah, it's possible. But I have one more idea. Can you try one other thing?
There's a way to get to EDL if you have only DFU mode, which is by getting adb (not adb sideload, just normal adb) and issuing "adb reboot edl". If you can get adb (i think you may have adb from the main recovery screen) then you can get to EDL and flash stuff with MiFlash. Try to issue 'adb reboot edl' when you are on the main screen of the recovery mode.
The other way, which might work on your state, is turning the phone off and holding volume down + power. It might open FTM mode (it's a white rectangle in the middle of the screen with the words FTM written on it, can't miss it). If you get there just issue 'adb reboot edl' and flash with MiFlash
Choose an username... said:
Yeah, it's possible. But I have one more idea. Can you try one other thing?
There's a way to get to EDL if you have only DFU mode, which is by getting adb (not adb sideload, just normal adb) and issuing "adb reboot edl". If you can get adb (i think you may have adb from the main recovery screen) then you can get to EDL and flash stuff with MiFlash. Try to issue 'adb reboot edl' when you are on the main screen of the recovery mode.
The other way, which might work on your state, is turning the phone off and holding volume down + power. It might open FTM mode (it's a white rectangle in the middle of the screen with the words FTM written on it, can't miss it). If you get there just issue 'adb reboot edl' and flash with MiFlash
Click to expand...
Click to collapse
Thanks, but I've already tried it. The phone only communicates with the computer in adb sideload mode, so trying adb reboot edl results in an "error:closed" message. If not in sideload mode, adb cannot even register a device. Occasionally, I've seen a small Linux penguin in the middle of the screen and today it hung on the MiFavor logo for some time. If those are significant, I don't know how to get them back. The ZTE engineers have been very thorough. It's frustratiing because the adb sideload thing might work with the right software package, and I can clear the cache and wipe the system; but then I'm back to square one. Your suggestion about dismantling the phone sounds like the most promising path forward and I will have a go tomorrow.
tretayuga said:
Thanks, but I've already tried it. The phone only communicates with the computer in adb sideload mode, so trying adb reboot edl results in an "error:closed" message. If not in sideload mode, adb cannot even register a device. Occasionally, I've seen a small Linux penguin in the middle of the screen and today it hung on the MiFavor logo for some time. If those are significant, I don't know how to get them back. The ZTE engineers have been very thorough. It's frustratiing because the adb sideload thing might work with the right software package, and I can clear the cache and wipe the system; but then I'm back to square one. Your suggestion about dismantling the phone sounds like the most promising path forward and I will have a go tomorrow.
Click to expand...
Click to collapse
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Choose an username... said:
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Click to expand...
Click to collapse
I do indeed get the 5 seconds screen, but the reason I didn't mention it is that it does nothing from what I can see. The phone "boots" after five seconds, but if I press the volume buttons to enter options, Bootloader is not one of them. The Fastboot option just makes the phone reboot and the Recovery option sends me to the screen in the photo upthread. Like I say, they've been very thorough.
Choose an username... said:
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Click to expand...
Click to collapse
Curioser and curioser. I went through the steps to short circuit the test point on the motherboard and MiFlash successfully flashed the Unbrick ROM which you advised. Obviously, the Qualcomm drivers were recognised e.t.c. The state of the phone now is that it is caught in a boot loop. It shows the ZTE screen and the 5-second screen. Going into recovery on the 5-second screen causes the ZTE logo to appear again, then the battery icon keeps showing, switching off and showing again. The Fastboot mode on the 5-second screen now takes me to the Fastboot screen, but entering recovery causes the same battery loop. Did I make a mistake reassembling the phone perhaps? Should I try to flash a different ROM from the test point?
tretayuga said:
Curioser and curioser. I went through the steps to short circuit the test point on the motherboard and MiFlash successfully flashed the Unbrick ROM which you advised. Obviously, the Qualcomm drivers were recognised e.t.c. The state of the phone now is that it is caught in a boot loop. It shows the ZTE screen and the 5-second screen. Going into recovery on the 5-second screen causes the ZTE logo to appear again, then the battery icon keeps showing, switching off and showing again. The Fastboot mode on the 5-second screen now takes me to the Fastboot screen, but entering recovery causes the same battery loop. Did I make a mistake reassembling the phone perhaps? Should I try to flash a different ROM from the test point?
Click to expand...
Click to collapse
So now you have fastboot? Put the TWRP-3.2.1-0.img on the adb folder, then open CMD, navigate to that folder, write 'fastboot boot TW" and press Tab, the filename should appear, if it does hit Enter
If you get to TWRP don't turn the phone off, and flash the universal bootloader, Lineage, the A2017 modem, and Magisk 15.2
Choose an username... said:
So now you have fastboot? Put the TWRP-3.2.1-0.img on the adb folder, then open CMD, navigate to that folder, write 'fastboot boot TW" and press Tab, the filename should appear, if it does hit Enter
If you get to TWRP don't turn the phone off, and flash the universal bootloader, Lineage, the A2017 modem, and Magisk 15.2
Click to expand...
Click to collapse
Sorry, I didn't make that clear. The 5-second screen directs me to Fastboot, but there are only four options there: Start (doesn't work, obviously), Restart Bootloader (brings you back to the same place), Shut down and Recovery (goes to battery icon). Don't know what went wrong--maybe a connection got damaged when the phone was dismantled--but I discover I can't repeat the short circuiting thing and, even though the phone is seen on the system as Qualcomm 90.., MiFlash cannot flash anything different. I despair. I'll send the phone for recycling. Making the Axon 7 incompatible with Daydream was the last straw. I very much appreciate your help just the same.
tretayuga said:
Sorry, I didn't make that clear. The 5-second screen directs me to Fastboot, but there are only four options there: Start (doesn't work, obviously), Restart Bootloader (brings you back to the same place), Shut down and Recovery (goes to battery icon). Don't know what went wrong--maybe a connection got damaged when the phone was dismantled--but I discover I can't repeat the short circuiting thing and, even though the phone is seen on the system as Qualcomm 90.., MiFlash cannot flash anything different. I despair. I'll send the phone for recycling. Making the Axon 7 incompatible with Daydream was the last straw. I very much appreciate your help just the same.
Click to expand...
Click to collapse
No, when you are on the screen with the 4 options you have Fastboot. That is the bootloader mode. Get there and issue 'fastboot devices' and you'll see that you got fastboot from there.
Don't repeat the 4th category manual, just turn the phone off and hold volume up and down, then connect the USB. If it appears as Qualcomm HS-USB QDLoader 9008 you're in EDL.
What's the name of the package that you flashed?
Choose an username... said:
No, when you are on the screen with the 4 options you have Fastboot. That is the bootloader mode. Get there and issue 'fastboot devices' and you'll see that you got fastboot from there.
Don't repeat the 4th category manual, just turn the phone off and hold volume up and down, then connect the USB. If it appears as Qualcomm HS-USB QDLoader 9008 you're in EDL.
What's the name of the package that you flashed?
Click to expand...
Click to collapse
You star! I've followed your advice and now it is exactly the phone I was looking for. (I had made a mistake and forgotten to reconnect something in the internals, but the ROM worked just fine once that was sorted and I've flashed all the things you recommended.) Your name will be sung down the ages in my household, Choose an username. Many thanks