I've been searching for hours here but can't find a solution that works...
My wife's Wi-Fi Nexus 7 (running stock, unrooted) suddenly got stuck in a boot loop during the white Google logo (never gets to the Nexus "X" animation). I figured I'd simply restore to stock through fastboot/adb.
The problem is when I try to unlock the bootloader (which is needed to be able to flash the factory image) I get this error message:
Code:
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
[COLOR="Red"][B]FAILED (remote: ()[/B][/COLOR]
finished. total time: 2.736s
Because of this, I can't go any further. I can't flash anything because it tells me I need to unlock the bootloader. I tried a couple of different toolkits with the same results.
I get fastboot access, and the device is listed when I type "fastboot devices" but I don't get adb access. When I type "adb devices" I simply see:
Code:
>adb devices
List of devices attached
...and nothing else. No devices listed. If I try other adb commands, I get "error: device not found".
I've tried installing the Google drivers as well as other USB drivers from toolkits. No change. But I can send it commands through fastboot fine.
{
"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"
}
I can get into recovery, but can't flash anything. I am able to factory reset from recovery, but it doesn't help. The tablet just keeps boot-looping.
Am I screwed? Any ideas? Thanks in advance to anyone who responds
I had to put mine in PTP mode to get it recognized. I also had a heck of of time getting the drivers installed correctly. I had to un-install and re-install several times before it worked correctly
bigdaddy619 said:
I had to put mine in PTP mode to get it recognized. I also had a heck of of time getting the drivers installed correctly. I had to un-install and re-install several times before it worked correctly
Click to expand...
Click to collapse
What's PTP mode? Were you having the same issue I'm having?
The thing is my tablet is getting recognized, at least in fastboot. Just not in adb but I'm thinking that's because it never had debugging turned on.
Wrong input.
grisoxxl said:
If you can acces recovery make full wipe.
Click to expand...
Click to collapse
Already did that several times. Doesn't help Still stuck in a boot loop and still can't unlock the bootloader to try to flash stock image.
ecaggiani said:
Already did that several times. Doesn't help Still stuck in a boot loop and still can't unlock the bootloader to try to flash stock image.
Click to expand...
Click to collapse
Why don't you flash the Google stock firmware?
Edit: i don't think unlock is necessary for flashing Google stock image
Sent from my Nexus 7 using xda premium
ganeshp said:
Why don't you flash the Google stock firmware?
Edit: i don't think unlock is necessary for flashing Google stock image
Click to expand...
Click to collapse
That's what I'm trying to do! The guides I've seen have me unlock the bootloader to be able to flash stock firmware. Can you point me to a guide? Is there an RUU maybe?
ecaggiani said:
Am I screwed?
Click to expand...
Click to collapse
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip.
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
bftb0 said:
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip.
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
Click to expand...
Click to collapse
Yeah I was afraid of that. Thanks for the response. I'll be contacting either Google or ASUS soon.
ecaggiani said:
Yeah I was afraid of that. Thanks for the response. I'll be contacting either Google or ASUS soon.
Click to expand...
Click to collapse
Hi, im having the exact problem you're having, did you end up contacting ASUS? how was your experience like? Did you get it resolved? I think I voided my warranty by trying to pull the battery ):
Hi all,
I've also got what seems to be a similar problem.
I've tried many (all?) the options to get this thing unlocked.
All I get is:
Code:
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 4.753s
or if I try a factory flash:
Code:
fastboot flash bootloader bootloader-tilapia-4.13.img
sending 'bootloader' (2096 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.013s
Also a "restart bootloader" from the recovery screen or
Code:
fastboot reboot-bootloader
takes me to a blank screen.
Holding the power button to reset the Nexus then the power + Vol Down takes me back to recovery with no change.
(I'm looking at this for a friend so not sure exactly what he did, but I doubt it was anything major!)
the machine vars are:
Code:
fastboot getvar all
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000700f00000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.161s
your help please?
regards
Ricey
Ricey_uk said:
Hi all,
I've also got what seems to be a similar problem.
I've tried many (all?) the options to get this thing unlocked.
All I get is:
Code:
fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 4.753s
or if I try a factory flash:
Code:
fastboot flash bootloader bootloader-tilapia-4.13.img
sending 'bootloader' (2096 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.013s
Also a "restart bootloader" from the recovery screen or
Code:
fastboot reboot-bootloader
takes me to a blank screen.
Holding the power button to reset the Nexus then the power + Vol Down takes me back to recovery with no change.
(I'm looking at this for a friend so not sure exactly what he did, but I doubt it was anything major!)
the machine vars are:
Code:
fastboot getvar all
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000700f00000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.161s.
your help please?
regards
Ricey
Click to expand...
Click to collapse
Hi, Ricey_uk...
Mmm... not sure, but I think you're trying to flash the wrong factory image for your device...
Reason being, is because (QUOTE: fastboot flash bootloader bootloader-tilapia-4.13.img) 'tilapia' refers to the 3G/GSM variant of the Nexus 7.
But you appear to have a (QUOTE: (bootloader) product: grouper) 'grouper' device. Which is WiFi only... this seems to be supported by the two lines in your output...
(bootloader) version-baseband: N/A
(bootloader) version-cdma: N/A
... which suggests your N7 has no 'radio' capability.
You need the factory stock image for "nakasi" for Nexus 7 Wi-Fi only (device board "grouper").... NOT "nakasig" for Wi-Fi & Mobile (device board "tilapia").
(See my sig for download links).
-----------
In short, there is an incongruity/contradiction in your reported outputs.... the device is either 'grouper' or it's 'tilapia'
It can't be both.
If it has a SIM card (like a mobile phone), or a space for a SIM card, then it's 'tilapia'... if it doesn't, then it's 'grouper'.
Ensure you are flashing the correct factory stock for your device.
-----------
But having said all of that... (and if there is confusion, it needs to be cleared up)... it doesn't explain why something as straightforward and innocuous as...
Code:
fastboot oem unlock
...isn't working.
Two possibilities occur to me...
1) A bad USB connection. Try a different USB port on your PC... Or, maybe, a different USB cable.
Once the fastboot oem unlock command is issued at the PC end, it will need to be confirmed at the Nexus 7 end (see attached thumbnail). Use either of the two VOL buttons to choose YES and confirm by pressing the POWER button.
2) It's possible there could be a hardware failure... some problem with the EMMC flash memory chip. As alluded to by a previous poster...
bftb0 said:
Most likely. Is it still in Warranty? (The tab should be less than 1 year old)
The whole narrative smells like some kind of failure with the EMMC flash memory chip
There's no point in fooling with adb. It only exists in the booted OS or a custom recovery, and you have neither.
Sorry... but you should probably be contacting Asus at this point.
Click to expand...
Click to collapse
Whilst I don't discount the possibility that it COULD be EMMC chip failure, I'm not inclined to think that this is a likely possbility. More prosaic explanations need to be explored first.
First... check the integrity of of your USB connections - at both ends; change to different USB ports on your PC; if you can, try a different PC; try a different USB cable. And confirm at the Nexus 7 end, once the unlock command has been issued. (again, see attached thumbnail).
Second... if you are going to try to fastboot flash back to Android factory stock... make sure you do so with correct version for your device. If you're device is Wi-Fi only, you need the 'grouper' version... if not, the 'tilapia' version.
Hope this helps.... and good luck.
Rgrds,
Ged.
Hi Ged,
thanks for the info, I was wondering about the .img versions - but I can't seem to find the 'grouper' version of 4.13 anywhere. It's not on the factory downloads page (google)
As for the unlock, it does indeed come up with the screen as you showed, and pressing the power button for 'yes' says that it is unlocking. When it then reboots itself it just stays blank. A hard power cycle back to recovery states that it is still locked.
thought?
cheers
Ricey_uk said:
Hi Ged,
thanks for the info, I was wondering about the .img versions - but I can't seem to find the 'grouper' version of 4.13 anywhere. It's not on the factory downloads page (google)
As for the unlock, it does indeed come up with the screen as you showed, and pressing the power button for 'yes' says that it is unlocking. When it then reboots itself it just stays blank. A hard power cycle back to recovery states that it is still locked.
thought?
cheers
Click to expand...
Click to collapse
Hi, Ricey_uk...
Yeah... that, unfortunately, does not sound good at all. Unlocking the bootloader just sets some 'flag state' on the internal EMMC flash chip. Specifically, somewhere in the mmcblk0boot0 partition, where the bootloader lives.
There's some technical info here... http://forum.xda-developers.com/showthread.php?t=2068207
If fastboot oem unlock is performing as you describe, then it strongly suggests some sort of hardware failure. It just shouldn't behave that way... once you have confirmed the oem unlock request on the Nexus 7, the PC should display (if I remember correctly), the following...
Unlocking....
The device is unlocked now...
The whole procedure should take no more than a few seconds. Blank screens and forced reboots have happened many times on my Nexus 7... but never whilst unlocking the bootloader (and yes, I have locked and relocked several times, when I was experimenting with the 'motochopper' root exploit).
----------------------------------
Incidentally, you won't find 4.13 on the factory downloads page, as that number refers to the bootloader version for JellyBean 4.2 and 4.2.1. (It's not always the case that with each new version of JellyBean the bootloader is updated).
Anyway... looking through my collection of system images on my laptop, I find the following...
JellyBean 4.1.2 -> bootloader-grouper-3.41.img
JellyBean 4.2.0 -> bootloader-grouper-4.13.img
JellyBean 4.2.1 -> bootloader-grouper-4.13.img
JellyBean 4.2.2 -> bootloader-grouper-4.18.img
JellyBean 4.3.0 -> bootloader-grouper-4.23.img
With JellyBean 4.3 being the latest, and it updating the bootloader to 4.23.
If you're still stuck on bootloader version 4.13, then that means it was last updated with the rollout of JellyBean 4.2, sometime around November 2012.
----------------------------------
All of which is technically interesting... but probably doesn't help you.
I think there is a hardware problem on your Nexus 7, that is preventing the bootloader-lock-state flag from being correctly set.
Wish I could be of more assistance.
Rgrds,
Ged.
Thanks Ged,
great info - I was looking for the factory image for JB 4.2.0 to get the bootloader image out of, but that version of JB isn't on the factory page
my theory being if I re-flash the same version it might fix the bootloader?? But it being locked it would need the exact same version?
perhaps if you could mail me the .img file I could try it? I can pm you my address??
cheers!
Ricey_uk said:
Thanks Ged,
great info - I was looking for the factory image for JB 4.2.0 to get the bootloader image out of, but that version of JB isn't on the factory page
my theory being if I re-flash the same version it might fix the bootloader?? But it being locked it would need the exact same version?
perhaps if you could mail me the .img file I could try it? I can pm you my address??
cheers!
Click to expand...
Click to collapse
Give me half an hour or so, and I'll upload it to my dropbox and I'll post a link. Gotta get it of my laptop first.
Although I'm not convinced it will solve your problem... but I suppose you have nothing to loose by trying.
Rgrds,
Ged.
---------- Post added at 12:53 PM ---------- Previous post was at 12:21 PM ----------
OK... here is the bootloader .img file - v4.13... extracted from nakasi-jp40d-factory-6ac58a1a.tar... or in English, Jellybean 4.2.1.
https://dl.dropboxusercontent.com/u/37483979/bootloader-grouper-4.13.img
Code:
File size: 2.05 MiB (2,146,892 bytes)
MD5: a119629c89ad06c7e49bebd260df9cf3
SHA-1: fd60a0d9da5c814e2c1ee049f537700cbbe2c3cc
Flash as follows....
Code:
fastboot flash bootloader bootloader-grouper-4.13.img
---------------
Be careful with this.
Flashing a bootloader is the riskiest single operation you can undertake on the Nexus 7.
All it takes is one false step, and you have a hardbrick.
The device will never boot again.
Make sure you have good USB connections at both ends... and before flashing... type...
Code:
fastboot devices
If you don't see a serial number, you have either a driver problem OR a possible dodgy USB connection.
Do not proceed with this flash until you see a serial number.
Normally, I would suggest test flashing something innocuous first, like a recovery, for example.... but since your bootloader is locked, that's not possible.
I'm not even sure flashing a bootloader is possible with a locked bootloader... but then, I've never directly flashed a bootloader before.
Very best of luck - really hope this fixes your problem.
Rgrds,
Ged.
Many thanks Ged,
tried it to no avail - still getting the 'Bootloader is locked'
It won't even re-flash the existing
I checked all the cables and used a different USB port.
thanks for your help
Ricey
Ricey_uk said:
Many thanks Ged,
tried it to no avail - still getting the 'Bootloader is locked'
It won't even re-flash the existing
I checked all the cables and used a different USB port.
thanks for your help
Ricey
Click to expand...
Click to collapse
Damn... thought that might happen... but wasn't 100% sure.
You can't use fastboot with a locked bootloader, even to flash a bootloader... and you can't unlock it because - well, who the hell knows why (but I suspect a problem with the internal EMMC).
What is the precise current status of your Nexus 7?
Android version?
Rooted?
Stock or Custom ROM/kernel?
Custom recovery (CWM/TWRP) installed?
Did you receive any OTA notifications regarding the recent release of Android 4.3? and if so did you allow the OTA update to proceed? What happened?
Rgrds,
Ged.
I know! I'm stuck in a loop!
I don't know the exact Android version, but it's fairly new and the owner hasn't updated it as far as I know.
Apart from that, completely stock and unrooted!
The last thing to happen was that it was left for a while to go flat (battery) then when re-started it got stuck at the Google logo and no further.
All I can get apart from the Google logo is the recovery with the andoid on his back with his tummy open
cheers
Ricey_uk said:
I know! I'm stuck in a loop!
I don't know the exact Android version, but it's fairly new and the owner hasn't updated it as far as I know.
Apart from that, completely stock and unrooted!
The last thing to happen was that it was left for a while to go flat (battery) then when re-started it got stuck at the Google logo and no further.
All I can get apart from the Google logo is the recovery with the andoid on his back with his tummy open
cheers
Click to expand...
Click to collapse
You can get the Android version info by going to SETTINGS>>ABOUT TABLET.
Without further details, what is odd about your predicament is this...
If your bootloader is v4.13, then that means the device hasn't been updated since November of last year. Since then, there have been, I think, 3 official updates from Google... the most recent being JellyBean 4.3 about a couple of weeks ago
Normally, when an OTA update is pending, you get pestered endlessly with an endless stream of notifications.
Upon the user accepting the lastest update (whatever that might be - but is currently JellyBean 4.3)... the device downloads the OTA, runs a checksum test on the current files in /system... and then'patches' them, meaning it brings them up to date.
The very last thing the OTA does is update the bootloader, by dropping BOOTLOADER.RAW into the USP(staging) partition. Upon automatic reboot, the new bootloader is then copied (from the USP/staging partition) into the bootloader partition proper... thus obviating the risks associated with flashing the bootloader partition directly.
Since November, the bootloader has been updated by this means twice... 4.13->4.18 (in, I think February, when JellyBean 4.22 was rolled out) and just recently 4.18->4.23 when JellyBean 4.3 was rolled out.
It's odd you haven't received any notifications of any OTA updates.
----------------------------------
Anyway.... A possible workaround...
A slightly rhetorical question... why do you want to unlock the bootloader anyway?
I assume it's because you want to root... or maybe flash a custom ROM...
That 'might' still be possible...if you're running a version of Android THAT ISN'T JellyBean 4.3, you can root via 'exploit'.
Details here - http://forum.xda-developers.com/showthread.php?t=2233852
This requires no fastboot commands and thus, no need for an unlocked bootloader.
It's really simple to implement. Indeed, I ran my Nexus 7 for several month BOOTLOADER locked, but rooted.
(But with the advent of JellyBean 4.3, root exploits no longer work.... so I've had to root the old fashioned way).
But it might be useful to you...
Anyway... once you are rooted, you can then flash a Custom Recovery... like CWM or TWRP.
Normally this would be done via fastboot. But there are two great apps available that will 'write' a recovery partition... directly from the Nexus 7.
These are Flash Image GUI and Flashify.
Both will request root access.
It doesn't matter which one you use, as they essentially do the same job... but IMHO, Flashify is the better of the two.
Once you have a Custom Recovery installed, the metaphorical gateway is open to whatever Custom ROMs or Custom Kernels you like.
----------------------------------
It's possible none of the above will work... maybe for the same reason why you can't unlock the bootloader. A suspected fault with the internal EMMC chip.
But it just might... and it's gotta be worth a shot.
To summarize
Root via 'exploit'
Use Flashify or Flash Image GUI to install a Custom Recovery
Good luck.
Rgrds,
Ged.
Hi, hope this is the right place to post this.
So my Nexus 7 (2012) was stuck in a boot loop, Google logo followed the little splash thing and repeat wihtout actually loading up. All I could open was the fast boot menu and the four options: wipe data/clear cache etc. I downloaded the relevant drivers, Android SDK, the factory image etc.
I was following these instructions to unlock the bootloader so I could flash the tablet:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This all worked fine.
fastboot oem unlock was typed next and the bootloader unlocked fine.
I then went to typed **fastboot flash bootloader bootloader-grouper-4.23.img**. Apparently what's meant to happen is:
sending 'bootloader' <2100KB>...
OKAY [ 0.123s]
writing 'bootloader' ...
OKAY [ 9.876s]
finished. total time: 9.999s
However mine just got stuck at the "writing 'bootloader' ..." stage. It was like this for quite a few minutes when it's supposedly meant to take a few seconds. "Signature match" showed up in the top left corner of the tablet however it is unresponsive, you can't move the buttons to show the Recovery mode/Power Off options.
I foolishly closed the command window and opened a new one. I tried to do the next stage "fastboot reboot-bootloader" however it just says "FAILED (command write failed (unknown error))" You get basically the same for all the other commands either unknown error. If you try to flash the bootloader again it fails and says invalid argument. My tablet was still recognised by the PC, showing the fastboot screen with Start in the top right and signature match in the top left. However any other prompts would fail. Eventually I unplugged the tablet and was able to turn it off with the power button.
Previously I had had trouble opening the fastboot menu or even getting to load to the boot loop (not responding to the button presses very well) however so far the display hasn't powered on at all. The only response you get is when it's plugged in you hear to device connected and disconnected sounds, and it is recognised as APX in the Windows device manager.
So what should I do? Is it fully bricked? My tablet is out of the 1 year warranty (This probably voided it anyway). Greatly appreciate any help anyone can give me
Normally flashing of a bootloader with a signature mismatch should not work, there are some protections build in, so I see two possible situations for you:
Either you are stucked in APX-mode, but the old bootloader is still working: in that case hold down the power button for at least 20 seconds to turn it off completely and then try to restart the tablet again
or flashing of the bootloader started, but failed during writing the new image. In that case the probability that you have a brick is very high ...
Update : It is solved now.
Here's what exactly happened to my Oneplus2 -
I had successfully unlocked the Bootloader and flashed TWRP using Fastboot.
Using TWRP, I flashed SU Binary and got root privileges.
STUPID Step : I enabled ENCRYPTION on the device.
Which made it impossible for TWRP to mount the encrypted drives. But even after that I was able to boot into Recovery.
Everything was fine (obviously, I wasn't able to flash through TWRP though, due to encryption)
After some days, when I tried to boot into TWRP, the device got powered off promptly just after the boot animation flashed on screen (which hardly lasted for a second)
I don't know what happened. I was not able to reboot device into system either. It just flashes the boot screen for a second and then completely goes blank. Same is the case if I try to boot into Recovery (using Power button + Vol button)
[Currently] I am able to power off my device and boot into Fastboot Mode (using Vol Up + Power)
I tried flashing TWRP again but it fails giving the following error.
Command - fastboot flash recovery TWRP.img
target reported max download size of 536870912 bytes
sending 'recovery' (25956 KB)...
OKAY [ 0.859s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.875s
Click to expand...
Click to collapse
So I checked whether the Bootloader is still unlocked? (And unfortunately it is locked, I have no idea how)
Command - fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.078s]
finished. total time: 0.078s
Click to expand...
Click to collapse
I tried to unlock the bootloader again but still the same result.
Command - fastboot oem unlock
(I'm sure that OEM unlocking was checked and even USB debugging was enabled last time I was booted into the system)
...
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
The bootanimation flashed for a second and then again nothing happened. I again checked the bootloader status. It is still same as quoted above.
I rattled a lot around many forums to get a way to boot into the system.
So what tried was to use this command.
Command - fastboot continue
resuming boot...
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Only a charging screen appears. And on removing USB same thing happens. Device gets powered off and on trying to boot again bootanimation comes up for a second and then blank screen.
I really have no idea what to do? Any help would be appreciated.
Thanks!
Follow this
https://www.youtube.com/watch?v=R4SVSovw4Jo
Nothing to worry about, i was on MM(beta) when this happen... I try to revert back to LP but the oem is locked.. I cnt even boot my phone... But at least fastboot was ok though.. http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543 this one
Flash Stock Recovery & Flash OxygenOS Zip
muk12 said:
Follow this
https://www.youtube.com/watch?v=R4SVSovw4Jo
Click to expand...
Click to collapse
This Video is awesome saved my life...thanks a ton......
SOLVED
The Chinese recovery tool did worked in my second attempt.
Just followed the video.
First time it didn't worked but second time it did.
In my first attempt it failed with some error. I uninstalled the device from the Device Manager. Reconnected it and updated the drivers again. Installed ADB. And then just followed as done in the video and it worked in this attempt.
After the recovery process was complete the device booted normally (And didn't went into Stock Recovery as I was expecting)
I rebooted the device into recovery mode(Stock Recovery)
Then I wiped the data to remove Encryption.
Thanks for the help. Cheers !!!
Need some help if someone can do that
- I have oem unlocked my b/l with unlock code, install twrp, try some polished rom but i don't like it and try to go back to oem locked state to flash an RUU file through ADB...
When i go to download/fastboot mode and type a "fastboot oem lock" command i have a message
"C:\adb>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
OKAY [ 0.028s]
finished. total time: 0.029s"
to my PC and on my phone i have a question "Yes to OEM lock and hard reset or No to live..."
I point to Yes and when confirm that my phone rebooted to a loop rebooting and blinking display with HTC logo and red words text...
Whatever i try to do it's always blinking/rebooting
Is there any way to normallise my phone and turn to any normal state?!
TNX
I moved out from previous state!!!
What a luck!
Dont know how but pressed VolUp+VolDown+Power and gone to bootloader state. After that have to unlock b/l again and after that when gone to Recovery, my TWRP is still there what a sweetness....
When enter to TWRP just some quick tex "Decrypting phone" and immediately rebooting to a normal state with all working phone states!
Is there any way to lock b/l again, turn to OEM state and to do a normal/regular HTC updating???
My last HTC update was 1.64.401.10 and European version...
Any advice?
TNX
Flash stock recovery: https://forum.xda-developers.com/u-ultra/development/unlocked-model-stock-recovery-t3585622 and you should be able to lock your bootloader successfully.
Never update with a third-party recovery. After you are done updating, install custom recovery again.
Ok.
I didn't know that
Tnx
Folks,
I have a ZF2L aka ZE551KL which is currently in a bootloop. Why that happened I have no idea as I have not dinked with the stock rom or for that matter even unlocked the bootloader.
A little bit of history, over the weekend, I had plugged in my phone to charge it and then when it completed charging I unplugged it and then tried to reboot it. That was the last time I had it working. After the reboot the phone has been in a bootloop ever since.
In order to try to recover from the above, I started reading a bit on what to do and I came across the postings that mentioned the bootloader has to be dropped to the Lollipop level so that it can be unlocked and then the recovery can be upgraded to Marshmallow. While trying to get all of that done, I have ended up here.
I "think" I have unlocked the bootloader using the command
echo -ne "\x01" | dd obs=1 count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo
I ran the above command directly on the phone via the terminal in TWRP. I booted into TWRP using the following fastboot command
fastboot boot twrp-3.2.3-0-Z00T.img
Running the fastboot command, fastboot oem device-info gives me the following output
C:\Users\home\android\platform-tools\images>fastboot oem device-info
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
Finished. Total time: 0.016s
However when I try to flash a new recovery TWRP-3.2.3-0-Z00T I get the following error
C:\Users\home\android\platform-tools\images>fastboot flash recovery twrp-3.2.3-0-Z00T.img
Sending 'recovery' (29856 KB) OKAY [ 1.342s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
Finished. Total time: 1.388s
I'm a little lost on what's going on. The device-info tells me the bootloader is unlocked, however it appears that something else is still locked which is not allowing the recovery to get flashed.
The stock recovery I was on before this all started was asus/WW_Z00T/ASUS_Z00T/6.0.1/MMB29P/WW_user_21.40.1220.2181_20170805. The recovery I currently have is LRX22G.WW_user_1.16.40.763_20151201
Any pointers on what I could do to get this resolved would be helpful?
hi if ur bootloader is unlocked, u an do a fresh flash of all d partitions as sometimes things get messed up on its own.
download firmware from https://drive.google.com/file/d/0B43Ue6xY9MmdN0UzWVRFcno4N0U/view and extract, then run flashall.cmd (in fastboot mode i.e. pwr and vol up)
u should finish without any hiccups. u will lose twrp though
tried on mine it woks. but google frp may be active so keep ur email n pass handy. m not responsible for any damages though ...