Database Users

Nexus 7 Stuck in Boot Animation Loop--Please Help

***TL;DR AT THE BOTTOM***
*^*EDIT 2!!*^*
Utilizing Cerberus, I was able to get passed the boot animation into the lock screen, though the Launcher is, for all intents and purposes, nonexistent. However, I was able to install Nova Launcher and can go to a home screen just fine. THIS IS NOT SATISFACTORY. I want to get back to STOCK Launcher, but it apparently does not exist anymore. I've managed to copy over my backup of Launcher2.apk, but it still refuses to acknowledge its existence. Can I get an update.zip that'll reinstall the default launcher from someone? I can boot into recovery via ROM Manager now I suppose!
+++EDIT!+++
+++~~~I have discovered that my problem is not the device being stuck in boot up, but that the boot animation will not cease--as +in the device is actually powered on, just displaying the boot animation like a screen saver. I cannot boot into recovery as I get +the Google splash screen and it never goes anywhere, my bootloader is freezing every time I plug it into my computer, and the +drivers will not install. My computer cannot detect fastboot and I can't connect to the Nexus via adb either. I CAN access internal +storage but that's about the extent of what I can do.+++~~~
Long version:
I decided I wanted to change the App Drawer icon from stock to a Nexus X that inverted its colours when pressed. I found the icon, converted it to png, inverted the colours and everything was going fine.
After a while I finally managed to find the right icons to replace in the system apk file "launcher2.apk". "ic_allapps.png" and "ic_allapps_pressed.png" or something very similar. I simply replaced them with my two icons, installed my modified launcher2.apk, and that was it.
Immediately, my home wouldn't open at all, no matter how many times I pressed the home button. It just would not exit the app I had up. So I started backing and ended up in an infinite back loop. I powered off the device, waited a minute, and powered it back on.
It came to the usual "Google" screen with the unlocked symbol at the bottom, no problems. However, then it started playing the boot animation. The boot animation never stopped. It looped infinitely. I tried resetting the tablet a few times for the same result. It was after 3 am and I had to get up for work in 4 and a half hours. I thought that maybe it was gonna take a while. So I flipped the Nexus over while it was "booting up" and went to sleep.
When I woke up and checked the tablet at 7:30, it was STILL booting up. Obviously I had screwed something up.
Now, stupid me, I had never flashed CWM recovery on my Nexus 7 (haven't had it that long), so all I'm stuck with is STOCK Recovery. I'm pretty sure I can rescue the Nexus by factory resetting it or something similar, but I'd rather try to save it first. All I modified was a LAUNCHER application, so I'm pretty sure the current state of the Nexus itself shouldn't be too far gone. Is there any way to save the Nexus WITHOUT a data wipe? And if the data wipe DOESN'T fix my problem, is it possible to somehow flash a stock ROM through stock Android Recovery?
***TL;DR***
I modified launcher2.apk and replaced "ic_allapps.png" and "ic_allapps_pressed.png" with two customized .png files (which I renamed to their appropriate file names). Now my Nexus is stuck on the boot animation indefinitely. I would like to save all of my data, as a data wipe would be inconvenient, but if I must do one I shall. I am on a stock ROM and a stock Recovery. If a data wipe/factory reset will not save my device, is it possible to flash a stock ROM through regular Android Recovery?
===Related but irrelevant to the problem===
Is it completely impossible to change the stock App Drawer icon to something different? I'd rather not have to get a different launcher app just to create a Nexus theme! I did a little more research and found that I should've modified the "all_apps_button_icon.xml" file as well, but I have NO idea how to do that.
Many thanks,
VonDerThWood.

As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here

NeoMagus said:
As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here
Click to expand...
Click to collapse
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.

simms22 said:
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.
Click to expand...
Click to collapse
How can I reflash the ROM on stock Android recovery? Googling that returns CWM results.

He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine

NeoMagus said:
He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine
Click to expand...
Click to collapse
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data

If you don't have fastboot set up you might want to give this post a look he describes how to get it set up.
simms22 said:
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data
Click to expand...
Click to collapse
I don't use custom recoveries and backup my data regularly with Titanium, so restoring after a reflash is really just an afterthought here, to each there own

The problem is not as it seems.
When I plug the Nexus into the computer when in Fastboot mode, it freezes the Recovery. I cannot select anything OR move the selection to anything else. The hell?
I noticed that when the Nexus attempts to boot up, the boot animation gets brighter.
__
Wait, when it attempted to boot up when plugged into my PC, AutoPlay recognized the device as Nexus 7. There is nothing on my screen but the boot animation, however I can browse internal storage.
I cannot, however, connect to it via adb apparently. ADB devices returns nothing.
____
Okay, the problem is NOWHERE near what I thought it was. The boot animation is replacing the lock screen/home screen/everything. I just received an email (I could tell because of the notification noise the tablet made). It is booting up, just not displaying anything passed the boot animation and ADB cannot detect the device. I KNOW it has USB Debugging mode activated and all, but what can I do now?
===
I usually make backups and nandroids but I've barely owned this device. ;P

Does fastboot detect the device?

janedoesmith said:
Does fastboot detect the device?
Click to expand...
Click to collapse
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?

Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in

the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.

VonDerThWood said:
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?
Click to expand...
Click to collapse
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.

NeoMagus said:
Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in
Click to expand...
Click to collapse
Fastboot has the "Recovery mode" option but it just gives me the Google logo with the unlocked icon at the bottom indefinitely...which means I cannot access recovery either? Why didn't I notice this before? >_<
simms22 said:
the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.
Click to expand...
Click to collapse
Tried 10 times by booting into bootloader first, then 10 times by plugging it in and booting into it while it's plugged in. This is a very...odd bug.
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.

it is an odd bug. i think every n7 owner who likes to flash roms/kernels has had to deal with it at least once.

VonDerThWood said:
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.
Click to expand...
Click to collapse
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.

janedoesmith said:
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.
Click to expand...
Click to collapse
Now that I think about it, it DID say something about failing to install an unknown driver the first time I plugged it in. Let me uninstall/reinstall the drivers.
____
After reinstalling the drivers (and removing both of the Nexus7 specific ones), I also removed one named "Android", which, coincidentally, is the driver that the tablet is trying to install upon being plugged in. I have tried to reinstall it several times, but it fails each time, AND I just reinstalled the real Nexus 7 drivers.
___
The Nexus drivers won't reinstall now. I even went to Asus's website and downloaded them, but I have no clue how to install it in this format.
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?

Whoa! Stroke of GENIUS!
I have Cerberus installed on my tablet. Since I know the tablet is booting up, just not displaying passed the boot animation, I decided to give it a try.
I started an alarm, which forced the tablet to the lock screen...I can open apps through the Play Store (as I got an update notification) and the like, but I can NOT get to the home screen.
I opened Total Commander via Play Store, but I can't do anything with it. The app that I used was NinjaMorph and I'm pretty sure the only way I can correct my mistake is through that app. What do I do?
Found NinjaMorph in the Play Store, it couldn't fix my problem. Oh hell.
I tried to copy/replace the launcher2.apk file I screwed up with a backed up one but TotalCommander couldn't do it. It was even granted SuperUser permissions. Attempting with Root Explorer.
Success! I have copied the original Launcher2.apk back into the /system/app folder. HOWEVER, I can NOT install it.
Managed to connect via adb! Things are looking up! Now, how to install this stuff...?
When trying to reinstall the launcher2.apk, it gives me the following error:
INSTALL_FAILED_UID_CHANGED
So I tried uninstalling it to no avail. Troubling.
SO! Now what? I am into the device, and any app I have downloaded through the Play Store is available to me, but I cannot go to the home screen. I need to reinstall the original Launcher2.apk!
Retrying NinjaMorph. It supposedly installed my Launcher2.apk. However, I still cannot return to the Home screen. WTF.
I'm going to install a different Launcher. Hope that works!
Success. I can now return home to Nova Launcher. HOWEVER...
This is not satisfactory. I want my STOCK launcher. Anybody know how I can fix this? The stock launcher is acting like it doesn't exist anymore. Is there a way to just wipe THAT data and keep all the other data on my device?? (Though I admit, I do like how I already was able to change my App drawer icon to my Nexus X <3.)

Edit: I see you resolved it. Good job! I'll just leave this here... :good:
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?
Click to expand...
Click to collapse
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk

comminus said:
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk
Click to expand...
Click to collapse
I managed to get ADB working (via adbWireless) after the above post I made, however I cannot get launcher2.apk to install. This time I got the "INSTALL_FAILED_DEXOPT" error instead of the "INSTALL_FAILED_UID_CHANGED" one.

Nexus 4 Problem: Wont boot into system or recovery, but fastboot and able to flash?!!

Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?

zroice said:
Very weird behaviour:
1. Phone does not boot up at all - neither system nor recovery (tried 5.1 and 4.4.4 factory images and 2.8.3.0 TWRP as recovery).
2. Can start in fastboot mode and flash factory image but after flashing modem the device is "stuck" in QHSUSB_DLOAD mode.. when I restart into fastboot it continues to flash and finishes the flashing process apparently.
3. When the device is off and plugged in its recognized as "unkown device" or QHSUSB_DLOAD again - no signs of charging at all.
Phone got to me in "bricked" state - would not boot and was only showing red light when plugging in - after loading it for a while (it showed the battery with a lighning inside on screen during charge attempt, but no percentages at all) i flashed latest factory image but that did not help it seems.. =(
Tried "fastboot erase cache" as well...
Any ideas?
Click to expand...
Click to collapse
u flashed stock doing fastboot -w update?

C4SCA said:
u flashed stock doing fastboot -w update?
Click to expand...
Click to collapse
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?

zroice said:
downloaded the stock factory images (tried 4.4.4 and 5.1 so far) from google and used the "flash-all.bat". Should I do it manually instead?
What you mean "-w update" is that a parameter for the fastboot flash command?
Click to expand...
Click to collapse
He is asking if you wiped the device after flashing. You flashed the image using the flash-all.bat, which wipes the device. And you even erased the cache. So from the flashing point of view, it seems you did everything right. Do you have the wall charger to load the battery (for some hours)? I would try this. Besides, here is another thread, which seems to be related: http://forum.xda-developers.com/nexus-4/help/qhsusbdload-problem-t2253874
cheers

Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.

now its gettin recognized only as "unknown device" not even QHSUSB_DLOAD anymore.. weird

zroice said:
Had it charging for hours before flashing, so battery cant be the problem..
But when I now put the device on PC (or Charger) nothing seems to happen - not showing the charging symbols and PC recognizes the device as QHSUSB_DLOAD.
Fastboot mode is working, Boot to system and recovery show the google logo but thats it, not even a boot animation.
Click to expand...
Click to collapse
dont do fastboot erase cache. Do fastboot format cache.
reinstall the correct google usb drivers manually (http://forum.xda-developers.com/nexus-s/general/tutorial-n00bs-install-drivers-windows-t1901617)
try to flash 4.2.2 and see if it boots up using the flash all bat.
that QHSUSB_DLOAD mode i think its teh qualcomm recovery mode or something like that, there is a thread on xda about it.

Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?

zroice said:
Yea good idea gonna try and flash older firmware - although there was 5.0 or 5.1 on it when the phone got to me..
Starting to believe its a hardware issue or the bootloader is fked up somehow - the thing wasnt even rooted when it wouldnt start anymore ...
Are there any ready to use packages to flash bootloader again with qpst? Dont have much time for this thing anymore - so I cant assemble my own files - unless thats a quick process.. but from what ive seen its a bit difficult, right?
Click to expand...
Click to collapse
no luck with 4.2.2 either - same behaviour.. flash is alright but then it wont boot or go into recovery.. argh

I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ

halloga said:
I had the same issue and this worked for me
https://productforums.google.com/forum/#!searchin/nexus/QHSUSB_DLOAD$20nexus$204/nexus/4Z5Sntc7u2c/HIyGuAVz8EQJ
Click to expand...
Click to collapse
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)

zroice said:
thanks man, tried that but no help. Phone isnt really stuck in the qhsusb_dload mode but it just won't boot neither the normal kernel nor the recovery system. All I can get this thing to boot is the fastboot mode and sometimes after flashing and rebooting from there the phone will be recognized as QHSUSB_DLOAD. When I plug it in while its off (either PC or wall charger) the Google Logo comes up, just as if its trying to boot, but no charging symbols.
In this state (google logo stuck) the pc does not recognize it at ALL - after a while the pc says "unknown device" has been attached but it has no hardware id or anything.
So the booting process is broken most likely. Question is if that is fixable with QPST or something else? Don't wanna invest any more time if its not likely to suceed though.. Already spent hours on this damn thing.. =)
Click to expand...
Click to collapse
I know this situation man, I spent many hours too and finally solution came out that simple Hope you solve it soon

well i tried that - but i only get a "red" light when holding volume down and power while on wall charger.
This resets the QHSUSB_DLOAD mode, but still wont make the phone boot for me. Tried that combo several times - only "red" light no orange or smth.
When i do that combo when the phone is plugged in to the pc and its in qhsusb_dload mode the red light will flash instead of beeing on all the time.
So I think ill give up unless someone can point me to a good QPST guide to rewrite bootloader for the nexus 4...
Must be bootloader or hardware issue im quite sure..

[HELP] LG Spirit H440N cannot access to Download mode

Hi everyone, i have a big problem. Today i was trying to help a firend of mine by unlocking his bootloader on this phone but i got a strange message when i was trying to boot in Download mode. The message was:
"fastboot init( )
loading keystore failed status 5 usb init ept @ 0x8f20700
udc_start( )
fastboot: processing commands"
Basically it doesn't allowed me to enter in Download mode, so no reverting to v10f software, no pushing aboot, no twrp and no Marshmallow zip. Nothing at all, i could do nothing. In the following lines i will tell you what i did and tried:
1) Using different PC usb ports, no way to make it work
2) Using different cables, no way to make it work
3) Trying to boot in Download mode by removing battery and try without it, desperate, obviously no way to make it work
I spent two hours trying to find a way to make it work but i failed miserably...so i'm here hoping someone better than me can help me.
NOTES:
The phone was on original Lollipop firmware v10e (Italy) but rooted.
Basically i did nothing, just tried to put it in download mode (Vol - and plug usb in), tried also other ways but nothing showed up
When the phone is connected to pc (when it's on) it charges only, don't show the option to use mtp so... i think adb won't work
Hope it can help and hope you can help! XD

I had same error, cause of flashing the wron zip basically i needed to get into repair mode and use adb while its trying to repair use adb commands to reboot to recovery
Sent from my LG-H440 using Tapatalk

MadjijaHacker said:
I had same error, cause of flashing the wron zip basically i needed to get into repair mode and use adb while its trying to repair use adb commands to reboot to recovery
Sent from my LG-H440 using Tapatalk
Click to expand...
Click to collapse
But i need Download mode, not recovery. With adb i can access it?
P.S i didn't flash anything

Well, that's what helped me, i don't know was that helpful, you can still try repair mode
Giuskiller said:
But i need Download mode, not recovery. With adb i can access it?
P.S i didn't flash anything
Click to expand...
Click to collapse
Sent from my LG-H440 using Tapatalk

Giuskiller said:
Hi everyone, i have a big problem. Today i was trying to help a firend of mine by unlocking his bootloader on this phone but i got a strange message when i was trying to boot in Download mode. The message was:
"fastboot init( )
loading keystore failed status 5 usb init ept @ 0x8f20700
udc_start( )
fastboot: processing commands"
...
NOTES:
The phone was on original Lollipop firmware v10e (Italy) but rooted.
Basically i did nothing, just tried to put it in download mode (Vol - and plug usb in), tried also other ways but nothing showed up
...
Hope it can help and hope you can help! XD
Click to expand...
Click to collapse
Upload mode is phone off, press VOL+ and then plug the USB.
---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------
MadjijaHacker said:
I had same error, cause of flashing the wron zip basically i needed to get into repair mode and use adb while its trying to repair use adb commands to reboot to recovery
Sent from my LG-H440 using Tapatalk
Click to expand...
Click to collapse
Can you give more details? How can I access that repair mode and how to use adb commands on it? I have a bricked board that I want to put back on use.

jorlando said:
Upload mode is phone off, press VOL+ and then plug the USB
Click to expand...
Click to collapse
Hi, i tried vol + but the phone just boots... i will try again and let you know in the evening

When device is off hold Vol- and power key until LG logo appear, then release the keys and hold them again, its really hard to time it correctly, but if you do you will get a factory reset option, on that screen you navigate using Vol+ and - buttons and power button is ok
Sent from my LG-H440 using Tapatalk

MadjijaHacker said:
When device is off hold Vol- and power key until LG logo appear, then release the keys and hold them again, its really hard to time it correctly, but if you do you will get a factory reset option, on that screen you navigate using Vol+ and - buttons and power button is ok
Sent from my LG-H440 using Tapatalk
Click to expand...
Click to collapse
Thank you, after the factory reset the combination Vol+ and USB worked (after a few try) and i was able to boot in Download mode, then i flashev v10f, rooted and pushed modified aboot, flashed twrp 1.1.0 with flashify (twrp official app failed many times) and finally installed v20b and supersu. Everything works as expected =)

Giuskiller said:
Thank you, after the factory reset the combination Vol+ and USB worked (after a few try) and i was able to boot in Download mode, then i flashev v10f, rooted and pushed modified aboot, flashed twrp 1.1.0 with flashify (twrp official app failed many times) and finally installed v20b and supersu. Everything works as expected =)
Click to expand...
Click to collapse
I am glad i could help [emoji2]
Sent from my LG-H440 using Tapatalk

oh man same problem if u fix this let me now how plzzzzzzz

Silentsx1 said:
oh man same problem if u fix this let me now how plzzzzzzz
Click to expand...
Click to collapse
Is there anything you can do on your phone or is it completely dead ?

I can enter the hardrester but itis not helping and in fastboot itis saying FAILED (remote: unknown command)

Silentsx1 said:
I can enter the hardrester but itis not helping and in fastboot itis saying FAILED (remote: unknown command)
Click to expand...
Click to collapse
Try to boot into download mode, if you can. Turn off your device then press and hold vol. Up and plug in the cable.

i cant turn off my device legit after i put battery fastboot show up :crying::crying::crying::crying:

Silentsx1 said:
i cant turn off my device legit after i put battery fastboot show up :crying::crying::crying::crying:
Click to expand...
Click to collapse
Can you post a screenshot here ?

here i cant do anything plz help
https://ibb.co/kmZCmG
https://ibb.co/eMB3tw
https://ibb.co/mQsMfb
https://ibb.co/dpf7Lb

Silentsx1 said:
here i cant do anything plz help
https://ibb.co/kmZCmG
https://ibb.co/eMB3tw
https://ibb.co/mQsMfb
https://ibb.co/dpf7Lb
Click to expand...
Click to collapse
Do you have twrp installed on your phone ? If, yes try to boot into it.

I have a similar problem with my LG Spirit. When it tries to boot, it shows an error message: Boot Verification Fail, DIFFERENT_HASH... After that it just restarts endlessly... I can't enter download mode, because the computer doesn't recognize it when I plug it in via usb cable... The only thing I can do is to get to the hard reset screen, but that is useless because it just restarts and shows the same error mentioned above... I'm out of ideas, the only thing that comes to my mind is to try and see if Ubuntu recognizes it, but then again, there's no LG Flash Tool made for Linux, or is there?
Sorry for mistakes, english is not my native language.

Hrastostit said:
I have a similar problem with my LG Spirit. When it tries to boot, it shows an error message: Boot Verification Fail, DIFFERENT_HASH... After that it just restarts endlessly... I can't enter download mode, because the computer doesn't recognize it when I plug it in via usb cable... The only thing I can do is to get to the hard reset screen, but that is useless because it just restarts and shows the same error mentioned above... I'm out of ideas, the only thing that comes to my mind is to try and see if Ubuntu recognizes it, but then again, there's no LG Flash Tool made for Linux, or is there?
Sorry for mistakes, english is not my native language.
Click to expand...
Click to collapse
If your pc doesn't recognise it, try to find an another computer that you can try it on .

mayankjet said:
If your pc doesn't recognise it, try to find an another computer that you can try it on .
Click to expand...
Click to collapse
Thank's for your reply. I did just that, but without success... I also tried to do what MadjijaHacker wrote, but I can't get it right. I mean, I can enter in hard reset, but can't get to download mode. It seems that my phone is dead...

Big problem with my htc U Ultra :(

Hello, I've a problem with my htc U Ultra (ocedugl). In fact, I upgraded supersu and when the phone was supposed to restart, I was stuck at the htc logo. I then had a backup of the boot and the system in reserve on my SD card, but when I wanted to restore them, I had the error 255. Only during the restoration of the system.
I do not know what to do, this phone is a real mystery to me. I have an internship tomorrow, not very practical suddenly. :/
The most problematic in all this is that twrp asks me for a password to decrypt the data at startup and I have the impression that I have only worsened the case. If anyone could help me quickly enough please.
PS: Me who I usually do alone, I must admit that I dry.
PS 2: I installed root switch for snapchat just before too, I do not know if that affects.

SofianeLasri said:
Hello, I've a problem with my htc U Ultra (ocedugl). In fact, I upgraded supersu and when the phone was supposed to restart, I was stuck at the htc logo. I then had a backup of the boot and the system in reserve on my SD card, but when I wanted to restore them, I had the error 255. Only during the restoration of the system.
I do not know what to do, this phone is a real mystery to me. I have an internship tomorrow, not very practical suddenly. :/
The most problematic in all this is that twrp asks me for a password to decrypt the data at startup and I have the impression that I have only worsened the case. If anyone could help me quickly enough please.
PS: Me who I usually do alone, I must admit that I dry.
PS 2: I installed root switch for snapchat just before too, I do not know if that affects.
Click to expand...
Click to collapse
Try TWRP 3.2.1-1

minhnewpro said:
Try TWRP 3.2.1-1
Click to expand...
Click to collapse
Ho to install without an accessible system?

SofianeLasri said:
Ho to install without an accessible system?
Click to expand...
Click to collapse
Turn off your phone. Press Power and volume down at the same time to boot in to download mode. connect to PC and flash TWRP
Install via ADB
Open the folder where your TWRP Recovery .img file is saved.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
Once your device boots into download mode, type this into the command line.
fastboot flash recovery twrp-3.2.1-1.img
Once TWRP is successfully flashed on your device, you can use TWRP now

minhnewpro said:
Turn off your phone. Press Power and volume down at the same time to boot in to download mode. connect to PC and flash TWRP
Install via ADB
Open the folder where your TWRP Recovery .img file is saved.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
Once your device boots into download mode, type this into the command line.
fastboot flash recovery twrp-3.2.1-1.img
Once TWRP is successfully flashed on your device, you can use TWRP now
Click to expand...
Click to collapse
thanks, i have now the twrp-3.2.1-1-oce but it still asks me for a password at startup and my restore still fails with error 255.

SofianeLasri said:
thanks, i have now the twrp-3.2.1-1-oce but it still asks me for a password at startup and my restore still fails with error 255.
Click to expand...
Click to collapse
Maybe you need flash a new rom. Viper, Ledroid,...

minhnewpro said:
Maybe you need flash a new rom. Viper, Ledroid,...
Click to expand...
Click to collapse
Okay, I was saying that too. I try your custom rom then.
PS : Ah, I just saw that the post requests the latest version of the system, except that I do not have access ...

unmout data in internal storage and retore

SofianeLasri said:
Okay, I was saying that too. I try your custom rom then.
PS : Ah, I just saw that the post requests the latest version of the system, except that I do not have access ...
Click to expand...
Click to collapse
You can try flash rom without have same firmware. I'm using Oreo on Nougat firmware

Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD

SofianeLasri said:
Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD
Click to expand...
Click to collapse
Oh it's good, it was really my card sd the problem.

SofianeLasri said:
Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD
Click to expand...
Click to collapse
i don't know what extractly happened with your phone. You can access your storage by connect to PC when your phone in TWRP Recovery. Backup your personal data. Choose wipe => format data => type "yes" => copy Rom into your internal storage or SD Card and flash

minhnewpro said:
i don't know what extractly happened with your phone. You can access your storage by connect to PC when your phone in TWRP Recovery. Backup your personal data. Choose wipe => format data => type "yes" => copy Rom into your internal storage or SD Card and flash
Click to expand...
Click to collapse
No, in fact my sd card is dead. I can't write anymore on. I have save mys backup and restore my system. Thanks for the help!

HTC u ultra Oreo messed up my phone and now I need help.
My story:
Bought a HTC U Ultra European.
I was kind of satisfied with it. The device didn't really live up to my expectations. But when it was upgraded to Oreo the screen start to flash when opening apps and Bluetooth sound went bad. It looks like the app opens twice. After a while it went even worse with the flashing.
Anyways I unlocked the bootloader and flashed TWRP 3.2. That process went fine then I wanted to flash leedroid to test something else (yes I saved a recovery file).
The result is now my device is working but I'm unable to flash twrp again. Since Oreo still sucks to u ultra and I want to downgrade to nougat since it works.
My adb (Linux) detects my device but when I start my HTC in download mode I'm unable to flash to since my PC says:
<waiting for device>
When I try to start it in recovery mode it sticks in a reboot loop.
And BTW I can't restore factory settings.
So if anyone can give me any answers it would be great.

ibringthemadness said:
My story:
Bought a HTC U Ultra European.
I was kind of satisfied with it. The device didn't really live up to my expectations. But when it was upgraded to Oreo the screen start to flash when opening apps and Bluetooth sound went bad. It looks like the app opens twice. After a while it went even worse with the flashing.
Anyways I unlocked the bootloader and flashed TWRP 3.2. That process went fine then I wanted to flash leedroid to test something else (yes I saved a recovery file).
The result is now my device is working but I'm unable to flash twrp again. Since Oreo still sucks to u ultra and I want to downgrade to nougat since it works.
My adb (Linux) detects my device but when I start my HTC in download mode I'm unable to flash to since my PC says:
<waiting for device>
When I try to start it in recovery mode it sticks in a reboot loop.
And BTW I can't restore factory settings.
So if anyone can give me any answers it would be great.
Click to expand...
Click to collapse
Try reinstall driver, buy or borrow an other usb-c cable.

minhnewpro said:
Try reinstall driver, buy or borrow an other usb-c cable.
Click to expand...
Click to collapse
I already installed drivers and tried other cables. Did the procedure again bit with no results.
I think the big problem actually is that since the phone can't boot into recovery mode it get messed up.
I try to do a hard reset but every time I either get stuck in a bootloop or the phone boots into regular mode. So I literally can't do anything to fix this problem as far as I know.
Getting a little bit of frustrated over here.

Why you need reflash TWRP after used Leedroid's rom?

minhnewpro said:
Why you need reflash TWRP after used Leedroid's rom?
Click to expand...
Click to collapse
Because I can't boot to recovery mode. Either I get stuck in a boot loop or the device boots just like I rebooted it. So I can't get to twrp and I can't flash anything. I can't hard reset either. All I can do is reboot, enter bootloader and enter download mode.
So I guess I'm stuck with Oreo that's a mess on my device.

ibringthemadness said:
Because I can't boot to recovery mode. Either I get stuck in a boot loop or the device boots just like I rebooted it. So I can't get to twrp and I can't flash anything. I can't hard reset either. All I can do is reboot, enter bootloader and enter download mode.
So I guess I'm stuck with Oreo that's a mess on my device.
Click to expand...
Click to collapse
Try boot into Download mode and Flash new TWRP https://dl.twrp.me/oce/twrp-3.2.2-0-oce.img.html
If your PC can not recognize your phone, try another PC.

minhnewpro said:
Try boot into Download mode and Flash new TWRP https://dl.twrp.me/oce/twrp-3.2.2-0-oce.img.html
If your PC can not recognize your phone, try another PC.
Click to expand...
Click to collapse
Already tried to flash twrp-3.2.2...
Same result. None.
My PC finds my phone with no problem until I boot into download mode then it doesn't find it anymore.
Still another PC?

boots to google logo

hi; rank amateur here. i unlocked my 6p which went with no problems and then installed trwp, now it just boots to the google logo. i can get to fastboot and twrp but my linux pc no longer sees the phone. i suspect the phone is in charge mode. can i use recovery, > terminal to turn on data transfer so i can load and flash a new os? i was looking at loading a zip to a sd card but i had to order an adapter from c to type a usb. thanks

@dr1445 Have you tried a factory reset? I'm not how Linux works but if I'm remembering correctly I think Windows installed additional drivers after I unlocked the bootloader. This is a bit old but looks like people are still using might find something useful.

yes i did try a factory reset but the same result. as for the the linux pc i used it to unlock the 6p and other phones, i just need to toggle off the the charge function and click on transfer. i have a widows machine, i will give it a try, never know.

fastboot says connect cable but it also reports download mode disabled, is there away to turn it on in fastboot?

dr1445 said:
fastboot says connect cable but it also reports download mode disabled, is there away to turn it on in fastboot?
Click to expand...
Click to collapse
Make sure your fastboot is the latest and maybe try a different cable if you can.
---------- Post added at 01:39 PM ---------- Previous post was at 12:54 PM ----------
dr1445 said:
fastboot says connect cable but it also reports download mode disabled, is there away to turn it on in fastboot?
Click to expand...
Click to collapse
Mine also says download mode disabled and I can still use fastboot. So I don't think its the problem.

dr1445 said:
hi; rank amateur here. i unlocked my 6p which went with no problems and then installed trwp, now it just boots to the google logo. i can get to fastboot and twrp but my linux pc no longer sees the phone. i suspect the phone is in charge mode. can i use recovery, > terminal to turn on data transfer so i can load and flash a new os? i was looking at loading a zip to a sd card but i had to order an adapter from c to type a usb. thanks
Click to expand...
Click to collapse
You're best bet is to just flash a factory image from Google and start over, link

let's see my pc still doesn't have commo with fastboot. i found that "sideloader" works between the pc and fastboot. i was able to install lineageos 15.1 but with out the gapps at the moment. odd thing is i can not get the "developer option" with 7 taps of the build #. working on new post now. thanks all.

dr1445 said:
let's see my pc still doesn't have commo with fastboot. i found that "sideloader" works between the pc and fastboot. i was able to install lineageos 15.1 but with out the gapps at the moment. odd thing is i can not get the "developer option" with 7 taps of the build #. working on new post now. thanks all.
Click to expand...
Click to collapse
Make sure your on the latest bootloader (3.79) I know that was a must after March update for most ROMs. Also make sure fastboot is the latest here.I think your best option is written above with reflashing latest stock image from March and starting over.

happy to check the bootloader version. i get bl: angler-03.79, baseband: angler-03.85. should be good?