I made sure the drivers are google drivers. I have done this before millions of times.
I swapped cables.
I tried everything.
I always get an OKAY, but no erases. I read that new Android Bootloaders need stock recovery to erase the data and other partitions after an oem unlock, in order to complete successfully.
Only issue is, stock recovery is broken with a red triangle and a dead android robot.
Bootloader version is MAKOZ30f.
'fastboot oem unlock' results in OKAY (as mentioned earlier) then I reboot boot loader and get it back on locked status again! Like NOTHING ever happened.
Is Debugging enabled? No. Because it was fully stock before this (friend's phone). Is that the issue? If so? How can I fix it when I can't get into recovery or even the system!
Hmm... What else?
That's mostly it.
I've tried NRT with no luck. It booted a modified boot.img and attempted to flash stock recovery 5.1.1 to no avail. The phone rebooted back into a bootloop, I shortly saw the unlocked white lock with the Google logo splash, but that was it then bootloooooop.
I have a fair bit of experience with android devices over the years. I am not a newbie, so I do have an intermediate level of knowledge with rooting, recoveries, Custom ROMs and the like.
Thank you guys in advance, I hope this is solvable! Because this is the first bootloop device that has actually gotten to me!
Tl;dr: Nexus 4 stuck in a bootloop. Recovery is broken (red triangle). Bootloader will not unlock (resets to 'locked' after bootloader reboot). Restarting after a bootloader unlock attempts just results in system bootloop again.
Help is gravely needed.
andezzat said:
I made sure the drivers are google drivers. I have done this before millions of times.
I swapped cables.
I tried everything.
I always get an OKAY, but no erases. I read that new Android Bootloaders need stock recovery to erase the data and other partitions after an oem unlock, in order to complete successfully.
Only issue is, stock recovery is broken with a red triangle and a dead android robot.
Bootloader version is MAKOZ30f.
'fastboot oem unlock' results in OKAY (as mentioned earlier) then I reboot boot loader and get it back on locked status again! Like NOTHING ever happened.
Is Debugging enabled? No. Because it was fully stock before this (friend's phone). Is that the issue? If so? How can I fix it when I can't get into recovery or even the system!
Hmm... What else?
That's mostly it.
I've tried NRT with no luck. It booted a modified boot.img and attempted to flash stock recovery 5.1.1 to no avail. The phone rebooted back into a bootloop, I shortly saw the unlocked white lock with the Google logo splash, but that was it then bootloooooop.
I have a fair bit of experience with android devices over the years. I am not a newbie, so I do have an intermediate level of knowledge with rooting, recoveries, Custom ROMs and the like.
Thank you guys in advance, I hope this is solvable! Because this is the first bootloop device that has actually gotten to me!
Tl;dr: Nexus 4 stuck in a bootloop. Recovery is broken (red triangle). Bootloader will not unlock (resets to 'locked' after bootloader reboot). Restarting after a bootloader unlock attempts just results in system bootloop again.
Help is gravely needed.
Click to expand...
Click to collapse
Stock recovery will give you the laying down Android with a red exclamation, once it times out press PWR+VOL UP to get to the recovery menu.
The bootloader probably won't unlock because it can't wipe (a requirement with the fastboot command), or it is locked in the Security settings of the latest stock image. Beginning with Lollipoop, if you are locked you have to tell Android it can be unlocked before doing it, it is a security measure.
You will need to reflash the full stock image, if NRT is failing do it manually, and do it from Linux if possible (no driver issues like Windows), you can get the images here: https://developers.google.com/android/nexus/images
And remember, first boot on Lollipop on the N4 can take 10-15 minutes or more well caches are being built and the OS is settings up (easily 5 times longer than a boot on KitKat), give it time, unless it restarts (a true bootloop) just let it sit. Patience is a real virtue here...
Note, you could have a corrupt or defective flash RAM chip, if that is the case, a full factory flash -MAY- fix it, but no guarantee... If the flash ram is bad, they you might be SOL.
Oh my god. Thank you so much. I am so stupid. I thought stock recovery is broken. But it's not. That's the normal way it should display. And you are right. Holding power then tapping vol up will show the menu
I am such a fool, I've always used custom recoveries, and forgot totally how stock recoveries work ^_^
I am now trying an adb sideload (the factory reset from recovery isn't working, lots of errors).
Gonna try a couple things.
And no I can't flash the images, cause I need to unlock the bootloader (if done through fastboot). Which is my main issue.
Hoping sideload really works!
BUT THANK YOU AGAIN SO MUCH ^_^
Okay. Now I am getting failure to mount /cache and stuff. Lots of problems with the cache partition.
I attempted 2 factory resets. I am now restarting and will report on how it goes. Gonna let the phone take its sweet sweet time booting.
If nothing else works, it really might be a hardware defect, and I really might be SOL @acejavelin
*sigh*
Oh well, all phones come to an end :/
Oh and great work Google on your 'extra precaution' with the whole bootloader unlock thing. Really? Nexuses/Nexii were MADE to be easily unlock-able. If this wasn't a problem... I might have actually been able to format the /cache/ partition, or try something with custom recovery that'd fix this phone quickly. *sigh*
andezzat said:
And no I can't flash the images, cause I need to unlock the bootloader (if done through fastboot). Which is my main issue.
Hoping sideload really works!
BUT THANK YOU AGAIN SO MUCH ^_^
Click to expand...
Click to collapse
When you do "fastboot oem unlock" are you getting a confirmation screen on the device and selecting Yes, or does that screen never pop-up?
Also, for the cache issue, in fastboot try "fastboot format cache" instead of the erase command.
And be aware that on first boot, I have had several Nexus/GPE Lollipop devices not show the setup screen or launcher (just a blank wallpaper) even after waiting 10-15 minutes, a simple reboot and more patience usually corrects this.
I did confirm, and it says unlocked on the phone. After restarting the bootloader it goes back to locked.
Cache: not supported in locked device.
I really cannot do a thing without unlocking the bootloader
Phone is still bootlooping. I gave it lots of time *sigh*
andezzat said:
I did confirm, and it says unlocked on the phone. After restarting the bootloader it goes back to locked.
Cache: not supported in locked device.
I really cannot do a thing without unlocking the bootloader
Phone is still bootlooping. I gave it lots of time *sigh*
Click to expand...
Click to collapse
I forget if unlocking the bootloader forces a reboot or not... If it doesn't, unlock and without rebooting try formatting cache or "fastboot boot recovery.img"" of latest twrp image.
Sent from my Nexus 4 using Tapatalk
That usually just says the device is locked, and that cannot be done on a locked device.
No it doesn't force a reboot!
I will try formatting cache partition again directly after unlocking bootloader (at least attempting). I'll report back if anything is successful.
I've tried flashing recovery as well, but just says cannot do while phone is locked. Will also try again.
Thank you for your help. I appreciate it.
acejavelin said:
I forget if unlocking the bootloader forces a reboot or not... If it doesn't, unlock and without rebooting try formatting cache or "fastboot boot recovery.img"" of latest twrp image.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
{
"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"
}
andezzat said:
Click to expand...
Click to collapse
After you unlock, do NOT try to FLASH recovery, try to boot it...
fastboot boot <path\recovery.img>
If the bootloader is unlocked, you should be able to push the recovery image over and boot it (not flash it), this will run a temporary copy that you can use to try to format the cache partitions, it doesn't write to the flash partitions to boot it, it all happens in RAM, so even if the flash is corrupt, you -MIGHT- be able to get TWRP loaded and format things to get them working again.
But to be honest, if you can't write recovery, or any other partition (or so it appears), this one might be done... but I don't stick a fork in it until there is nothing more to try.
I didn't notice the boot it part. Okay I am in TWRP now. I can't wipe cache. It is unable to mount cache, data usb-otg, and storage.
Where do I go to format not wipe?
Sideload gives me error: protocol fault (no status).
andezzat said:
I didn't notice the boot it part. Okay I am in TWRP now. I can't wipe cache. It is unable to mount cache, data usb-otg, and storage.
Where do I go to format not wipe?
Click to expand...
Click to collapse
Wipe in TWRP formats, except internal storage and data since internal storage is actually /data/media.
This is bad, if you can't mount cache or internal storage, your flash ram is likely bad.
andezzat said:
Sideload gives me error: protocol fault (no status).
Click to expand...
Click to collapse
Most likely you need a newer adb to use sideload in TWRP... There is a minimum revision of adb required, version 1.0.32 or higher.
Sent from my Nexus 4 using Tapatalk
That was useful! I got adb 1.0.32 but now instead, I get total xfer: 0.00x
Is that it? EOL for this phone? :'(
I don't know if this will help you, OP but here goes - try selecting the partition in TWRP, changing the partition type to something else and then changing it back to ext4. See if that works.
PS: I remember that my N4 refused to boot up to system after I flashed a factory image - it only booted up to recovery which I promptly restarted. Turns out you have to wait till the recovery reboots itself.
Nothing is working right now. I tried changing formats and everything. It's just unable to mount any of the partitions. And now they're all stuck on 0mb size.
I have an otg usb. It won't even detect or mount it at all. I can't even choose it instead of internal storage. This phone is beyond gone :/
I get constant ERROR=8 from e2fsck whenever I try to resize or repair. Probably has something to do with the phone not being REALLY unlocked.
I'm starting to wonder if this might be a corrupt image of your radio or the bootloader... Flashing it (if it's possible) might be risky in your situation but at this point in time I don't know if you can do much else than try.
Related
I stupidly flashed a recovery.img as a bootloader because I used an .img flasher app without reading it all the way. I normally use fastboot and I'd never make a mistake when doing it this way... Needless to say, I've learned my lesson.
My device now boots up, but it behaves strangely. When I now flash a bootloader or a recovery, it changes the typical boot-up procedure.
When flashing a bootloader and rebooting, I see the google logo of the normal boot, but suddenly in the top-right, the green arrow selector from the bootloader appears and can be interacted with, all while the white google logo still shows in the center
When flashing a recovery, my device will reboot straight into recovery no matter what, until I flash a rom with a boot.img (at the time, CM11). From this point on, when booting the device will display logos in an atypical order: google>recovery logo (twrp) will flash for a second or two>standard boot animation>done
Even after doing a standard-procedure restore to stock 4.4.2, the device will flash the recovery screen for a second before going to the boot animation.
Am I wrong in thinking that there may be files left over from the accidental recovery flash into the bootloader partition? Does updating a bootloader only replace existing files and leave whatever extra may be in there?
Though the device successfully boots, it's driving me crazy and makes me nervous that it may go wrong someday, should I decide to flash a new rom or bootloader update (if one come with 4.4.3)
The only solution I can think of is going through the effort of retrieving my device blobs, deliberately running "fastboot erase bootloader" to clean it out and flash a clean bootloader with nvflash. I made sure I downloaded an uncorrupted 4.23 .img that i'd use for this.
Suggestions before I do anything more to my tablet?
Currently I'm on stock rooted 4.4.2, 4.23 bootloader unlocked with TWRP 2.7.0.0 (these same issues happened whilst completely stock too)
Here is a video slowed down 8x of what happens, it shows the last command run in recovery (in this case, fixing permissions - I'm literally trying everything I can think of)
Freezeframe of this happening
{
"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"
}
ReaperManHK said:
I stupidly flashed a recovery.img as a bootloader because I used an .img flasher app without reading it all the way. I normally use fastboot and I'd never make a mistake when doing it this way... Needless to say, I've learned my lesson.
My device now boots up, but it behaves strangely. When I now flash a bootloader or a recovery, it changes the typical boot-up procedure.
When flashing a bootloader and rebooting, I see the google logo of the normal boot, but suddenly in the top-right, the green arrow selector from the bootloader appears and can be interacted with, all while the white google logo still shows in the center
When flashing a recovery, my device will reboot straight into recovery no matter what, until I flash a rom with a boot.img (at the time, CM11). From this point on, when booting the device will display logos in an atypical order: google>recovery logo (twrp) will flash for a second or two>standard boot animation>done
Even after doing a standard-procedure restore to stock 4.4.2, the device will flash the recovery screen for a second before going to the boot animation.
Am I wrong in thinking that there may be files left over from the accidental recovery flash into the bootloader partition? Does updating a bootloader only replace existing files and leave whatever extra may be in there?
Though the device successfully boots, it's driving me crazy and makes me nervous that it may go wrong someday, should I decide to flash a new rom or bootloader update (if one come with 4.4.3)
The only solution I can think of is going through the effort of retrieving my device blobs, deliberately running "fastboot erase bootloader" to clean it out and flash a clean bootloader with nvflash. I made sure I downloaded an uncorrupted 4.23 .img that i'd use for this.
Suggestions before I do anything more to my tablet?
Currently I'm on stock rooted 4.4.2, 4.23 bootloader unlocked with TWRP 2.7.0.0 (these same issues happened whilst completely stock too)
Here is a video slowed down 8x of what happens, it shows the last command run in recovery (in this case, fixing permissions - I'm literally trying everything I can think of)
Freezeframe of this happening
Click to expand...
Click to collapse
Hi, ReaperManHK...
I can't be 100% sure, because you don't explicitly state it in your post, but I suspect you've been using either Flashify (for root users) or Flash Image GUI.
Whichever app you've used, I'm pretty sure your bootloader is fine...(If it were otherwise, your Nexus 7 simply wouldn't boot... EVER! - it would be HARDBRICKED).
Both apps (Flashify and Flash Image GUI) do essentially the same thing... which primarily is to provide an easy way of...
-------------------------------------------------
*** flashing a recovery.img to the recovery partition ***
...and/or...
*** flashing a boot.img to the boot partition ***
-------------------------------------------------
Neither Flashify or Flash Image GUI go anywhere near the bootloader itself.
NOTE: The boot partition is NOT THE SAME THING as the bootloader partition.
I suspect you've accidentally used either the Flashify app or the Flash Image GUI app to flash a recovery.img to the boot partition (and NOT to the bootloader partition... which I know is actually impossible using Flashify, and I also suspect to be equally impossible using Flash Image GUI).
It's not a difficult mistake to make... I know I've done it myself in the past (using Flashify to accidentally flash a recovery.img to the boot partition, instead of the recovery partition). This was easily fixed, by simply fastboot flashing a correct boot image to the boot partition.
ReaperManHK said:
The only solution I can think of is going through the effort of retrieving my device blobs, deliberately running "fastboot erase bootloader" to clean it out and flash a clean bootloader with nvflash. I made sure I downloaded an uncorrupted 4.23 .img that i'd use for this
Click to expand...
Click to collapse
Whilst generating your own device specific 'wheelie' blobs is a relatively straightforward task (though absolute care is required and the instructions MUST be followed to the letter), actually using them in the event of HARDBRICK/APX mode, seems to be less straightforward. The instructions on using them on the flatline web page seem a little ambiguous.
I strongly recommend YOU DO NOT run fastboot erase bootloader. This is a VERY HIGH RISK command, that may well permanently hardbrick your Nexus 7. If you must fastboot flash a bootloader, do it 'over' the top of the current one.. ie., without erasing the old one.
And, anyway...I honestly don't think you have a bootloader related problem.
ReaperManHK said:
Even after doing a standard-procedure restore to stock 4.4.2, the device will flash the recovery screen for a second before going to the boot animation.
Click to expand...
Click to collapse
With regard to the strange 'glimpse' of the recovery on boot... this, I think, is quite common. I see it frequently myself... particularly if I've just been messing around in TWRP. I think the cause of the problem actually lies with the KitKat bootanimation (colored spinning circles) itself, as I never used it see with the Jellybean boot animation (pulsing luminescent X logo), that was for quite a while the stock Nexus 7 boot animation. The KitKat bootanimation starts ever-so slighty latter then the original boot animation, and consequently, it doesn't mask/hide the last screen you saw in TWRP. Anyway, whatever the precise cause, it has nothing to do with the bootloader.
In conclusion...
Both Flashify & Flash Image GUI apps can flash two partitions, as follows...
a boot.img-->>boot partition
a recovery.img-->>recovery partition
What I suspect you inadvertently did...
a recovery.img-->>boot partition
(Overwriting the boot partition(kernel+ramdisk) and NOT THE BOOTLOADER partition)
Solution...
Use fastboot to flash a correct boot.img, with...
Code:
fastboot flash boot correct_boot.img
One final point... if you really had accidentally flashed a recovery.img to the bootloader partition, you would have wiped the bootloader itself, and which is absolutely critical to the Nexus 7... and your device would now be totally HARDBRICKED. An expensive paperweight.
There are no gradations of bootloader corruption... it either works, or it doesn't. And if it doesn't, well... ... HARDBRICK!
So, If you're device is now running fine... as you seem to suggest it is... I wouldn't worry about it. I certainly wouldn't be inclined to start messing about with esoteric bootloader related stuff like 'blobs' and flatline.
A bootloader is something to be flashed as infrequently as possible... and then forgotten about... until and/or unless you really, really have unavoidable cause to do otherwise.
'boot.img to boot partition' and 'recovery.img to recovery partition' flashes, however, are relatively safe and innocuous... but just make sure you flash the right kind of .img file to it's appropriate partition.
Hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, ReaperManHK...
I can't be 100% sure, because you don't explicitly state it in your post, but I suspect you've been using either Flashify (for root users) or Flash Image GUI.
Whichever app you've used, I'm pretty sure your bootloader is fine...(If it were otherwise, your Nexus 7 simply wouldn't boot... EVER! - it would be HARDBRICKED).
Both apps (Flashify and Flash Image GUI) do essentially the same thing... which primarily is to provide an easy way of...
-------------------------------------------------
*** flashing a recovery.img to the recovery partition ***
...and/or...
*** flashing a boot.img to the boot partition ***
-------------------------------------------------
Neither Flashify or Flash Image GUI go anywhere near the bootloader itself.
NOTE: The boot partition is NOT THE SAME THING as the bootloader partition.
I suspect you've accidentally used either the Flashify app or the Flash Image GUI app to flash a recovery.img to the boot partition (and NOT to the bootloader partition... which I know is actually impossible using Flashify, and I also suspect to be equally impossible using Flash Image GUI).
It's not a difficult mistake to make... I know I've done it myself in the past (using Flashify to accidentally flash a recovery.img to the boot partition, instead of the recovery partition). This was easily fixed, by simply fastboot flashing a correct boot image to the boot partition.
Whilst generating your own device specific 'wheelie' blobs is a relatively straightforward task (though absolute care is required and the instructions MUST be followed to the letter), actually using them in the event of HARDBRICK/APX mode, seems to be less straightforward. The instructions on using them on the flatline web page seem a little ambiguous.
I strongly recommend YOU DO NOT run fastboot erase bootloader. This is a VERY HIGH RISK command, that may well permanently hardbrick your Nexus 7. If you must fastboot flash a bootloader, do it 'over' the top of the current one.. ie., without erasing the old one.
And, anyway...I honestly don't think you have a bootloader related problem.
With regard to the strange 'glimpse' of the recovery on boot... this, I think, is quite common. I see it frequently myself... particularly if I've just been messing around in TWRP. I think the cause of the problem actually lies with the KitKat bootanimation (colored spinning circles) itself, as I never used it see with the Jellybean boot animation (pulsing luminescent X logo), that was for quite a while the stock Nexus 7 boot animation. The KitKat bootanimation starts ever-so slighty latter then the original boot animation, and consequently, it doesn't mask/hide the last screen you saw in TWRP. Anyway, whatever the precise cause, it has nothing to do with the bootloader.
In conclusion...
Both Flashify & Flash Image GUI apps can flash two partitions, as follows...
a boot.img-->>boot partition
a recovery.img-->>recovery partition
What I suspect you inadvertently did...
a recovery.img-->>boot partition
(Overwriting the boot partition(kernel+ramdisk) and NOT THE BOOTLOADER partition)
Solution...
Use fastboot to flash a correct boot.img, with...
Code:
fastboot flash boot correct_boot.img
One final point... if you really had accidentally flashed a recovery.img to the bootloader partition, you would have wiped the bootloader itself, and which is absolutely critical to the Nexus 7... and your device would now be totally HARDBRICKED. An expensive paperweight.
There are no gradations of bootloader corruption... it either works, or it doesn't. And if it doesn't, well... ... HARDBRICK!
So, If you're device is now running fine... as you seem to suggest it is... I wouldn't worry about it. I certainly wouldn't be inclined to start messing about with esoteric bootloader related stuff like 'blobs' and flatline.
A bootloader is something to be flashed as infrequently as possible... and then forgotten about... until and/or unless you really, really have unavoidable cause to do otherwise.
'boot.img to boot partition' and 'recovery.img to recovery partition' flashes, however, are relatively safe and innocuous... but just make sure you flash the right kind of .img file to it's appropriate partition.
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
You are exactly right, I used flashify. I freaked out over the flashing image because I've never seen it before.
Firstly, thank you for the very detailed response.
I'm still a little confused, because I've since flashed the stock boot.img in fastboot several times (I've also wiped the boot partition beforehand). I wish I had a screenshot of the bootloader appearing in the corner of the boot animation, but I'm assuming it's gone since I wiped and reflashed the boot partition.
As for the flickering being something to do with the KK boot animation, I'm not so sure - it did the same thing with CM11.
All this started because I wanted to install the holofied TWRP here http://forum.xda-developers.com/showthread.php?t=2393881
ReaperManHK said:
You are exactly right, I used flashify. I freaked out over the flashing image because I've never seen it before.
Firstly, thank you for the very detailed response.
I'm still a little confused, because I've since flashed the stock boot.img in fastboot several times (I've also wiped the boot partition beforehand). I wish I had a screenshot of the bootloader appearing in the corner of the boot animation, but I'm assuming it's gone since I wiped and reflashed the boot partition.
As for the flickering being something to do with the KK boot animation, I'm not so sure - it did the same thing with CM11.
All this started because I wanted to install the holofied TWRP here http://forum.xda-developers.com/showthread.php?t=2393881[/QUOideas.ey I tried the guide. Every thing goes through fine but when tab reboots it still has old omni ROM on it. 4.4.2. I also tried to update twrp to v. 2.8 from 2.7 in fastboot but no joy. It stays on 2.7 on reboot even though fastboot flashes it and says OK done. Also I cannot relock the boot loader. I give the command in fastboot OEM lock its says OK button reboot its still unlocked. But I can boot into a new version of twrp or cwm touch temporarily using wgh tool and click boot custom recovery temporarily and it does it. But can't flash it permanently. What shall I do. Feel like smashing the tablet with a hammer. I am pissed because my son has no tablet any more. I was the one who put omni ROM on it. So I take the blame for ruining it. It was working fine but suddenly it rebooted on it'd own after few weeks and since then nothing works on it. Just the stuff that was on it. Can't install anything new. I wonder why I can't even change custom recovery from twrp permanently to a new version. Please give me your guidance.
GED do you have any ideas
Click to expand...
Click to collapse
I fixed it by reflashing the bootloader, then a recovery, both through ADB.
Otherwise, just restore a factory image.
Hey can you tell me which version of boot loader you flashed and which recovery.
---------- Post added at 04:17 PM ---------- Previous post was at 04:15 PM ----------
Also , I am stuck at twrp 2.7 and 4.23 boot loader. Thanks. Please help .
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
Hey this is the issue I have[quote name="ReaperManHK" post=52626493]You are exactly right, I used flashify. I freaked out over the flashing image because I've never seen it before.
Firstly, thank you for the very detailed response.
I'm still a little confused, because I've since flashed the stock boot.img in fastboot several times (I've also wiped the boot partition beforehand). I wish I had a screenshot of the bootloader appearing in the corner of the boot animation, but I'm assuming it's gone since I wiped and reflashed the boot partition.
As for the flickering being something to do with the KK boot animation, I'm not so sure - it did the same thing with CM11.
All this started because I wanted to install the holofied TWRP here http://forum.xda-developers.com/showthread.php?t=2393881[/QUOideas.ey I tried the guide. Every thing goes through fine but when tab reboots it still has old omni ROM on it. 4.4.2. I also tried to update twrp to v. 2.8 from 2.7 in fastboot but no joy. It stays on 2.7 on reboot even though fastboot flashes it and says OK done. Also I cannot relock the boot loader. I give the command in fastboot OEM lock its says OK button reboot its still unlocked. But I can boot into a new version of twrp or cwm touch temporarily using wgh tool and click boot custom recovery temporarily and it does it. But can't flash it permanently. What shall I do. Feel like smashing the tablet with a hammer. I am pissed because my son has no tablet any more. I was the one who put omni ROM on it. So I take the blame for ruining it. It was working fine but suddenly it rebooted on it'd own after few weeks and since then nothing works on it. Just the stuff that was on it. Can't install anything new. I wonder why I can't even change custom recovery from twrp permanently to a new version. Please give me your guidance.
GED do you have any ideas
I followed Heisenberg's How-To Guide For Beginners and unlocked the bootloader, then installed TWRP.
It was fine yesterday, rebooted it several different times and no issues. Had the normal warning about the bootloader being unlocked. Today, I powered the phone on, not to bootloader, just to android, and got the "Your device is corrupt. It can't be trusted and may not work properly." See image below.
What do I need to do? Do I just do a factory reset? Or should I try re-flashing TWRP?
Thanks for any help you guys can offer, I appreciate it.
{
"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"
}
Just wait 10 seconds and your device will boot. This is normal warning after making changes to OS.
Try to use search. This issue has few threads going on.
http://forum.xda-developers.com/search.php?searchid=396007182
This message will appear until u will lock it bootloadet again
emiwonder said:
This message will appear until u will lock it bootloadet again
Click to expand...
Click to collapse
Message for unlocked bootlader is orange.
https://support.google.com/nexus/answer/6185381?p=verified_boot&rd=1
Witek_M said:
Just wait 10 seconds and your device will boot. This is normal warning after making changes to OS.
Try to use search. This issue has few threads going on.
http://forum.xda-developers.com/search.php?searchid=396007182
Click to expand...
Click to collapse
I apologize, I should have mentioned that I have not rooted the phone. The farthest I went was to unlock the bootloader and then install TWRP.
I did search the XDA Nexus 6P Q&A, Help & Troubleshooting forum and found this thread. However, the OP already had his phone rooted, but my phone is not rooted, so I did not want to mess the phone up any further. I am very new at this. This is the first time I have unlocked a bootloader and installed a custom recovery.
Also, the OP's phone would not go past the google logo, however, my phone will boot all the way up and it operates normally. Another reason I didn't follow what he did (performing part 9 of Heisenberg's guide).
j.r.pitcher said:
I apologize, I should have mentioned that I have not rooted the phone. The farthest I went was to unlock the bootloader and then install TWRP.
I did search the XDA Nexus 6P Q&A, Help & Troubleshooting forum and found this thread. However, the OP already had his phone rooted, but my phone is not rooted, so I did not want to mess the phone up any further. I am very new at this. This is the first time I have unlocked a bootloader and installed a custom recovery.
Also, the OP's phone would not go past the google logo, however, my phone will boot all the way up and it operates normally. Another reason I didn't follow what he did (performing part 9 of Heisenberg's guide).
Click to expand...
Click to collapse
Does that warning impair in any form or fashion usability of your device? Unable to browse? Unable to text? Unable to call or receive calls?:cyclops:
Did you forget to flash the modded boot image or something? I would just flash everything back to stock and start over if I were you
Witek_M said:
Does that warning impair in any form or fashion usability of your device? Unable to browse? Unable to text? Unable to call or receive calls?:cyclops:
Click to expand...
Click to collapse
It does not impair anything so far as I've seen. I've used most of my apps with no problems. I can make and receive calls and texts just fine. I am also able to browse the web just fine as well. Everything seems to be working normally. I just get that red triangle (Your device is corrupt...) warning whenever I boot the phone.
Here is what happens in order of booting first into the bootloader:
I boot into the bootloader and it comes up normally.
I go down and select recovery mode, it comes up with the normal orangish-yellow triangle (bootloader unlocked) warning, then the Google logo with the unlocked padlock, then the TWRP splash screen, then into TWRP.
Within TWRP, if I select "Reboot", then "System" I get the screen asking if I want to install SuperSU now, I tap "Do not Install" (per Heisenberg's guide), the screen goes blank, the normal orangish-yellow triangle (bootloader unlocked) warning comes up, then the Google logo with the unlocked padlock, then blank again, then the red triangle (Your device is corrupt...) warning, then the Google logo with the unlocked padlock then the animated circles that finally morph into "android", then the phone is on and I can use it normally.
Does that help in diagnosing the problem at all?
In my limited experience the corrupt screen but able to boot means that something on the phone is the wrong version. Flash the vendor image, radio, and boot img that is made for your rom.
Systemless root is the likely the cause because the boot img is from an earlier build.
btort1 said:
Did you forget to flash the modded boot image or something? I would just flash everything back to stock and start over if I were you
Click to expand...
Click to collapse
I didn't flash anything other than TWRP 2.8.7.2. As far as I know, everything is stock.
The only thing I can think of is when installing TWRP it comes up with a screen asking if you want it to be "read only" or "swipe to allow modifications". If you select "read only", then the next time you reboot the device, android overwrites the custom recovery with the stock recovery. If you "swipe to allow modifications", TWRP changes something to keep android from overwriting the custom recovery with the stock recovery. I chose to "swipe to allow modifications". That is the only thing that I can think of that was changed in the system.
Thanks for the suggestions.
siegesoldier said:
In my limited experience the corrupt screen but able to boot means that something on the phone is the wrong version. Flash the vendor image, radio, and boot img that is made for your rom.
Systemless root is the likely the cause because the boot img is from an earlier build.
Click to expand...
Click to collapse
I didn't flash anything other than TWRP 2.8.7.2. As far as I know, everything is stock.
The only thing I can think of is when installing TWRP it comes up with a screen asking if you want it to be "read only" or "swipe to allow modifications". If you select "read only", then the next time you reboot the device, android overwrites the custom recovery with the stock recovery. If you "swipe to allow modifications", TWRP changes something to keep android from overwriting the custom recovery with the stock recovery. I chose to "swipe to allow modifications". That is the only thing that I can think of that was changed in the system.
Thanks for the suggestions.
j.r.pitcher said:
I didn't flash anything other than TWRP 2.8.7.2. As far as I know, everything is stock.
The only thing I can think of is when installing TWRP it comes up with a screen asking if you want it to be "read only" or "swipe to allow modifications". If you select "read only", then the next time you reboot the device, android overwrites the custom recovery with the stock recovery. If you "swipe to allow modifications", TWRP changes something to keep android from overwriting the custom recovery with the stock recovery. I chose to "swipe to allow modifications". That is the only thing that I can think of that was changed in the system.
Thanks for the suggestions.
Click to expand...
Click to collapse
I did not realize you did not change the boot img. Without flashing a boot img with verity checks disabled, (basically everyone besides stock) you'll get the corrupt warning if ANYTHING in the system partition gets modified. which is likely what happened when you swiped.
The warning means nothing, nothing is effected and if you flash one without verity checks you just get the yellow warning instead.
siegesoldier said:
I did not realize you did not change the boot img. Without flashing a boot img with verity checks disabled, (basically everyone besides stock) you'll get the corrupt warning if ANYTHING in the system partition gets modified. which is likely what happened when you swiped.
The warning means nothing, nothing is effected and if you flash one without verity checks you just get the yellow warning instead.
Click to expand...
Click to collapse
I forgot to mention that after doing the "swipe to allow modifications" and TWRP installed, I rebooted the phone multiple times that day, Monday (11/30), and did not get the red triangle (Your device is corrupt...) warning at all. The following day, Tuesday (12/1), I rebooted the phone and got the red triangle (Your device is corrupt...) warning. Between installing TWRP (with swiping to allow modifications) and getting the red triangle (Your device is corrupt...) warning the following day, I did nothing else other than normal use of the phone. That is what is confusing to me.
Help
I tried to relock my bootloader but when the device restarted it went straight to error mode.
I managed to boot straight back to full system but whenever I restart it goes back to error mode. I cant enter fastboot or recovery mode.
I sont know what to do now any help
Screenshot
{
"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"
}
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
How can I unlock bootloader without fastboot? If I attempt to enter fastboot or anything that requires reboot I end up on that screen.
Hmm....
Have you tried rebooting to fastboot using adb?
Johnny TDN said:
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
Click to expand...
Click to collapse
Johnny TDN said:
Hmm....
Have you tried rebooting to fastboot using adb?
Click to expand...
Click to collapse
I tried but still get to error mode.....I have tried many times
Then i don't know anymore dude. Have you tried reinstalling the firmware using the 3 button method?
elliotn said:
I tried but still get to error mode.....I have tried many times
Click to expand...
Click to collapse
Hello
tested with the toolkit 0.0.0.12.
to see if he recognizes the phone.
he should at least write your serial number.
if that is the case.
you can use DC-unlocker. to open FRP and can be the bootloader.
just an idea.
Dc unlocker needs cash and it doesn t always work.
I am doubting buying DC,unlocker in case,it doesn't work and I will lose money.... I will try toolkit.
3 button upgrade doesn't work either.
I have the same problem after I tried to relock my bootloader using SRKToolHuawei-STABLE-V1.3-20160619 with my bootloader code.
Have you found a solution?
I can boot back into os b394 after I let the battery run out to 0%
I haven't found a way to repair my recovery and fastboot yet because rebooting into fastboot always get's me back to that first error
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Then I have to wait for my battery to run out again
Any help to get fast boot and a working recovery back would be appreciated.
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
shankarjdhv125 said:
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
Click to expand...
Click to collapse
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Same problem for me
No way to shutdown the phone, someone have solved?
Now I'm waiting for the battery to full drain
Hi guys i ve made mistake because i wanted to update to latest release media pad m3 but i could not be able to boot to stock recovery after i flash recovery img extracted from update.app and second time i flash recovery2.img to erecovery partition and i got the same issue error Func No 11(recovery image) and Error NO 2 (load failed) . I also put the update.app to dload folder on sd card but update system is not starting i press volume up and down and power button at same time but is not working.I tried also with huawei multitool but is not working is not recognize my device. Please guys is any other solution to fix this ?Thank You!
I just fixed after power off device and then press volume down and plug the usb cable to pc and i was able to recognize my device and i have use huawei multiTool to unbrick my tablet media pad m3 and has work.
Almost the same problem, help please!!!
Hi guys someone can help me? I have a Honor 9 lite(LLD-L31). Android version 8.0
I apologize but I'm a new user and i don't have much practice with modding in general.
I tried to install root permission in my device. I get bootloader unlock code by DC-unlocker and installed TWPR on my device.
When i went in recovery the error " Failed to unmount '/system'(Device or resource busy)" rushed, so I tried to format data in order to give partition available. I tried again to flash file.zip but the search was empty so I downloaded a most recent version(3.2.3) of TWPR in recovery ramdisk.
Now if i try to log into recovery mode appear the same error (Error! func NO 11 / NO 2).
I can do everything aside going in recovery mode. How can I resolve it? Is it possible to reset to factory settings and try again?
I hope I have explained well the problem.
elliotn said:
3 button upgrade doesn't work either.
Click to expand...
Click to collapse
how about this 3 button method??
Astarothkun said:
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Click to expand...
Click to collapse
Could you write down the steps you took to get back in fastboot for me? I'm having troule geting there myself after draining battery.
I fixed it after nothing else here worked.
So this is mostly so I dont ever forget the solution again, but also to possibly help others.
I also have to say that I had the problem with an P8 Lite, but all my problems matched almost exaclty, so It might help you too.
And a third disclaimer: I have no idea if you can flash the stock firmware without having the bootloader unlocked.
If you dont have it unlocked, try this wonderful updated guide: [Links are disabled for me so google this: "Droidhunter unlock huawei bootloader" and pick the article by droithunter.com]
And yes DC-Unlocker, suprisingly actually works (at least for me) and buying their bootloader unlock code was worth the 4 bucks.
So here is the solution:
1. Somehow, however needed get into fastboot. As I couldn't use the volume/power key combo myself, I somehow force reset the phone, pressing various buttons until I managed to boot into it again. I then used the adb bridge to boot into fastboot (google how to connect adb, then use "adb reboot bootloader" to get into the fastboot menu).
2. Download your phone models default stock rom/Update.app (also google that).
3. Extract the Update.app file.
4. Download and use the HuaweiUpdateExtractor tool and open the Update.app file (google again helps).
5. Select the "09.recovery.img" entry (the one with the green arrow on the left), rightclick and select "extract selected" and save it somewhere where you can find it.
6. Open your Fastboot console on PC (its often the same as the ADB console used before, especially if you use Minimal Fastboot and ADB, which I would recommend).
7. Make sure your phone is in Fastboot mode (not recovery) and connected to the pc.
7.1 Make sure your bootloader is unlocked. It might work with a locked one because youre just flashing stock firmware but eh might break more. Its worth the 4 bucks to unlock the bootloader first. (and yes DC unlocker looks super sketchy but somehow it actually worked for me and wasnt a scam).
8. Flash a custom recovery onto the phone (pretty much the same way you flash twrp, but instead of the twrp image you use the .img file you just extracted from the Update.app; Also dont try flashing twrp directly, it will probably not work).
The command to do so is: "fastboot flash recovery [filepath to the .img file without the brackets]".
9. Use the command "fastboot reboot".
10. If your phone doesnt boot normally, use the key combinations to get into the normal recovery screen and recover from a file or whatever (other guides should work from here).
Extra Steps:
As my recovery image was obviously so broken that even flashing twrp on top of it didnt work until I flashed the original reovery image, I went into my phones settings and did a factory reset. Directly after I installed twrps (see google) and set it up so it had full control. Afterwards I rooted and installed LinageOS cause frick EMUI rn).
Hope this helps anyone. If you have any questions feel free to ask me.
{
"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"
}
DISCLAIMER:
I'm not responsible for any damaged watches or other broken things! All of this is still heavily in development and mainly a developer release, not at all recommended for normal usage!
The following tutorial CAN brick your watch if you're not careful enough! Once again I'm not taking any responsibility!
This has only been tested on Android N so far, Android O is not yet fully tested!
---------------------------------------------------------
Please read before doing anything:
This is a port of TWRP for the Ticwatch E. Currently we're not able to boot it via fastboot (well, it technically does but there's an issue with the video driver) and when trying to flash it the watch will instantly flash the stock recovery over it upon reboot.
To avoid this we have to do a little workaround! Once you reboot your watch it'll restore the stock recovery again! After following these steps your watch will be stuck in a bootloop which we'll fix too tho.
Please keep the Changelog below in mind and read what's working and what's not before asking. We may or may not have seen this issue before already.
Files you'll need:
v003 of "TWRP for Ticwatch E" (and most likely S) - OneDrive Mirror
Stock Recovery for Ticwatch E (and most likely S) - OneDrive Mirror
ADB and Fastboot drivers installed (I recommend "15 Seconds ADB Installer")
Changelog:
Updated Instructions:
Slightly updated the instructions so you won't lose any data if you're already on an bootloader unlocked watch!
v003 (OneDrive Mirror):
Managed to make TWRP persistent! Check Instructions on how to.
v002 (OneDrive Mirror):
Now includes systemless root package inside the TWRP image so you're able to root your watch!
v001 (OneDrive Mirror):
Initial release, no ADB so far. Can't be booted from fastboot directly either due to weird fastboot behavior and has to be flashed first. However upon normal reboot Mobvoi decided to flash over the stock recovery again so we have to do a workaround.
Instructions:
The new Instructions by Luxios require a few less steps AND if you've already unlocked your watch before you won't even lose data!
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you [font=Verdana, Arial, Helvetica, sans-serif]can skip this[/font])
Follow the on-screen instructions on your watch to unlock it (if you already have an unlocked bootloader you can skip this)
Reboot via "fastboot reboot" and wait until Android Wear fully starts up
One started reboot to the bootloader via the same command as above
Once the bootloader shows up again type "fastboot flash recovery TWRP_TicwatchE_v003.img"
After that type "fastboot oem reboot-recovery" to reboot to the TWRP recovery
In order to make TWRP persistent you need to go to "Install" > "Install ZIP" > "supersu" > "TicwatchE_TWRP_keeper.zip" and flash it
Upon rebooting you may notice it'll get stuck in an infinite TWRP bootloop. To fix this boot into TWRP, then choose "Reboot" > "Bootloader", back in fastboot type "fastboot boot StockRecovery_TicwatchE.img" and wait a few seconds, a few reboots later Android Wear should start right up again.
If you want to root your watch reboot it once again with "adb reboot recovery" and go to the same folder as above, tho this time flash "SuperSU-2.79-wear_systemless.zip"
Unroot/Remove TWRP for Android O Update:
Go to this thread to also update directly to the last Android O update and revert all customizations: https://forum.xda-developers.com/sm...es/android-o-super-easy-ticwatch-e-s-t3789835
Have fun!
You're the best! I'm gonna try as soon as I can, and let you know.
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Piereligio said:
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Click to expand...
Click to collapse
If your bootloader is (or was) already unlocked you have to lock and then unlock it again for it to work.
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Piereligio said:
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Click to expand...
Click to collapse
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Sadly it looks like SuperSU failed to root. It gave a data partition mounting error at the end of the script, don't know if it is normal. TWRP isn't able to mount data either.
EDIT: Looks like I found a way to boot TWRP without having to lock/unlock bootloader.
Doing this, I managed to boot TWRP after setting the watch up, and in this way, it didn't fail to mount /data. Let's see...
EDIT2: now SuperSU still fails, but for a different reason. I'm gonna ensure that it failed though.
EDIT3: su command responded, so seems that root works. I'll do some more tests.
TWRP is now persistent! Check the updated guide
Rooting succeeded!
Seems like I managed to root the smartwatch using the version 2. For the moment I'm happy like this, next times I'll indeed use new procedures.
EDIT: Yes, I rooted it.
My steps (the ones on OP are the recommended ones):
-Bootloader unlock;
-Boot in Android Wear to enable ADB from Settings;
-Reboot in bootloader with "adb reboot bootloader";
-Flashed this TWRP v2;
-"fastboot reboot", then "adb reboot recovery" as soon as adb was detected while booting.
In this way I managed to avoid the system to flash stock recovery over TWRP.
By the way, I don't recommend my way of rooting it, it's less safe, just follow the updated instructions in OP.
Huge thanks to @EpicLPer
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
You can flash again the stock recovery with spflash tool.
EpicLPer said:
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
Click to expand...
Click to collapse
I really wish I knew what. All I did was flash a bad recovery, pretty sure something was was wrong with the ram disk. All I get is the splash logo for 3 seconds and a brief vibrate.
Luxios said:
You can flash again the stock recovery with spflash tool.
Click to expand...
Click to collapse
I think I need a scatter file to even get started. I've never used the tool so any other instructions would be greatly appreciated.
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
elios93 said:
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
Click to expand...
Click to collapse
I have the same problem...
EDIT: I have a Ticwatch S.
Niktendo said:
I have the same problem...
EDIT: I have a Ticwatch S.
Click to expand...
Click to collapse
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
elios93 said:
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
Click to expand...
Click to collapse
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
EpicLPer said:
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Click to expand...
Click to collapse
Can you get me the device tree or at least BoardConfig.mk used for this? I have a working watch (still working on recovering the old one) and I think I can get the rest of the partitions working but I would really like to avoid any more mistakes.
Luxios said:
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
Click to expand...
Click to collapse
That 'fastboot oem reboot-recovery' command sure is a nice find!
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
hassanabid94 said:
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
Click to expand...
Click to collapse
Maybe it's a specific developer unit. Don't do anything with it yet, we could loom further into this if it is something special.
I have A2017G, came with MM. I unlocked the bootloader, flashed TWRP and rooted, then flashed Nougat B04 and the corresponding B04 boot.img (was that necessary?)...
IIRC, TWRP came up once, but was then replaced with the stock recovery. I went to flash TWRP again, but the bootloader seems screwy. I get this screen for a few seconds:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I touch the volume in time, this comes up:
But if I select fastboot, it just goes back to the first screen, then boots up after a few seconds. ADB shows no fastboot device on either of these screens. Hours of googling has gotten me nowhere...
The stock recovery will let me sideload a zip, but I gather it's no help with a img. OEM unlocking in developer options is greyed out; stuck on.
Select Fastboot and if the first screen comes again press the power button to continue and it wait it should boot itself to fastboot.
Or activate adb in the developers settings and type ADB reboot fastboot in ADB on Windows or Linux
I ended up with this too after trying to flash a custom rom, my just kept cycling around and around. I could not access any recovery.
I rescued mine from this point using the Miflash app and an edl package.
"DM verity enforcing" is what you need disable if you can get back to twrp. (Nfound has a twrp with all your needs covered)
Or try Voenix suggestion
I hope this helps
Edit: this is my rescue guide
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
Kimmoth said:
I have A2017G, came with MM. I unlocked the bootloader, flashed TWRP and rooted, then flashed Nougat B04 and the corresponding B04 boot.img (was that necessary?)...
IIRC, TWRP came up once, but was then replaced with the stock recovery. I went to flash TWRP again, but the bootloader seems screwy. I get this screen for a few seconds:
If I touch the volume in time, this comes up:
But if I select fastboot, it just goes back to the first screen, then boots up after a few seconds. ADB shows no fastboot device on either of these screens. Hours of googling has gotten me nowhere...
The stock recovery will let me sideload a zip, but I gather it's no help with a img. OEM unlocking in developer options is greyed out; stuck on.
Click to expand...
Click to collapse
I'll make it quick: No fastboot, but you don't need it really. Just use EDL. You can install TWRP via EDL Tool or axon7tool.exe
axon7tool is finicky and hasn't got a GUI so you should try with edl tool first.
Download EDL Tool and TWRP, follow instructions on how to set up edl tool, put the twrp .img on Flash - Recovery (rename it to recovery.img just in case [BE SURE that show file name extensions is enabled]) then flash. Then reboot the phone, AND ENTER TWRP (otherwise it'll get replaced). simply reboot the phone after twrp is flashed and select "recovery" from the 5 seconds screen on boot.
Once you're in TWRP you simply have to flash Magisk to avoid losing it again, if you are on stock N firmware you should flash Magisk 16.7 (17.1 will bootloop). But I recommend that you format data (Wipe - Format data) and THEN flash magisk, so that you unencrypt the internal storage and don't lose it if you change your ROM or whatever
Choose an username... said:
Download EDL Tool and TWRP, follow instructions on how to set up edl tool, put the twrp .img on Flash - Recovery (rename it to recovery.img just in case [BE SURE that show file name extensions is enabled]) then flash. Then reboot the phone, AND ENTER TWRP (otherwise it'll get replaced). simply reboot the phone after twrp is flashed and select "recovery" from the 5 seconds screen on boot.
Click to expand...
Click to collapse
Sweet! This worked (after giving up on my desktop, showing hidden devices and uninstalling a couple of dozen drivers from my laptop's device manager)
Once you're in TWRP you simply have to flash Magisk to avoid losing it again, if you are on stock N firmware you should flash Magisk 16.7 (17.1 will bootloop). But I recommend that you format data (Wipe - Format data) and THEN flash magisk, so that you unencrypt the internal storage and don't lose it if you change your ROM or whatever
Click to expand...
Click to collapse
Dammit, I got ahead of myself and went through this paragraph stepwise despite having already read it. Went to wipe - format data after installing Magisk, and hit error 255.
And, upon rebooting my phone, it's asking for a password I never entered...?
PS. How do I bugger off the 'your device software can't be verified for corruption' crap?
You need to enter,
"DM verity enforcing" in twrp advanced settings.
To remove corruption message.
NFound has a twrp with a specific advanced setting for this.
Kimmoth said:
Sweet! This worked (after giving up on my desktop, showing hidden devices and uninstalling a couple of dozen drivers from my laptop's device manager)
Dammit, I got ahead of myself and went through this paragraph stepwise despite having already read it. Went to wipe - format data after installing Magisk, and hit error 255.
And, upon rebooting my phone, it's asking for a password I never entered...?
PS. How do I bugger off the 'your device software can't be verified for corruption' crap?
Click to expand...
Click to collapse
The password is because data is corrupted - the system tries to unencrypt it but it isn't encrypted. You just have to format data again (If you have the error, it might be hard - try unmounting and mounting data, or changing its filesystem, it might work. If it doesn't, you'll have to install Fastboot (if it is a G, you can use Raystef's zip from the bottom of this post) and go to it, then do "fastboot erase userdata", it usually works.
And that screen is the 5 seconds screen, you should leave it there, it's useful. Only way to enter Fastboot without commands, plus you can also enter recovery and stuff
also, flash magisk AFTER formatting. I think Magisk Manager is installed in /data so you are essentially removing it
https://www.google.com.ar/url?sa=t&...FjAAegQIBhAB&usg=AOvVaw0mLcRna7wHd0MBSXcBI3sr
So I installed Nfound's TWRP, allowed it to modify the system, disabled DM verity enforcing, and that damn message still comes up (it also shows up instead of fastboot, and choosing fastboot gets me no fastboot), and what's more, now I just get a little linux penguin instead of the boot animation, which just sits there forever, even after re-flashing the ROM...
Check the comments here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214
I'm not sure which ROM you are installing, this one is Lineage Os 15.1.
Check this twrp
https://forum.xda-developers.com/axon-7/development/twrp-3-1-0-2-t3591075
You may have to "delete inscription" too
I hope this helps.
I've flashed this rom: A2017G-N-B04 (australian) from here: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
Is it it necessary to flash the boot.img that's listed with it, or is that included in the rom zip, or can you run a different one?
I tried adb reboot "dm-verity enforcing" from the pc, and typing reboot "dm-verity enforcing" straight into the terminal on twrp, and the phone rebooted both times but the same 'your device software can't be checked for corruption' thing still comes up...
Is there some way I can wipe the slate clean and start fresh? Something seems a bit off. I'm trying to install Xposed (I have the right one, sdk25-arm64), but when I flash it the phone just hangs at the end of the boot animation.
I could really use a comprehensive primer on all this business... I kind of half get the hang of it, then it's a year or so until I need to do it again, and I've forgotten most of what I learned the last time, with some portion of it that's become obsolete anyway... I feel like I'm groping in the dark here.
Check this post
https://forum.xda-developers.com/axon-7/help/encryption-password-boot-t3667446
Here flashing the ROM and doing a factory reset.
I'm in Australia too (running A2017G) and if you use the wrong software it can cause grief.
Did you flash all 3 files recovery, boot and firmware
From Raysteffs post? If not, you should.
I soft bricked mine by accident and recovered it with a stock edl package.
Edl has all the IMG files needed
Recovery (stock) fast boot, splash, firmware (usually 3 IMG files) and all associated.
I'm currently running B15 Oreo Chinese global (switched modem files to work here in Oz)
I would go back to as stock as possible to restart then use the Axon7 tool kit
Toolkit is here
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
If you mix and match recovery, boot and ROMs this can lead you too bootloop or system hangs because its looking for associated files that aren't there.
Sometimes 1 file can make all the difference.
Good luck, I hope you get it sorted
Kimmoth said:
Sweet! This worked (after giving up on my desktop, showing hidden devices and uninstalling a couple of dozen drivers from my laptop's device manager)
Dammit, I got ahead of myself and went through this paragraph stepwise despite having already read it. Went to wipe - format data after installing Magisk, and hit error 255.
And, upon rebooting my phone, it's asking for a password I never entered...?
PS. How do I bugger off the 'your device software can't be verified for corruption' crap?
Click to expand...
Click to collapse
This just worked for me too!