Related
Hi there i have a rotted kindle fire with burrito root.
I rooted it yesterday and everything was fine, then i turned it off and back on later it worked fine.
the next day it hangs on the boot logo (it is animated no triangle)
adb recognizes it yet i cant access adb root, remount etc Permission denied.
I cant install TWRP
What i wanted to do was go to the /sdcard directory and push the update.zip there. but i cant because it read-only. How do i change any of these? Ive read 6 other posts on possible fixes none of which work.
Have you tried pressing the power button for 20 seconds and then restarting it?
nope
Yes i did that does not help.
adb says it cannot be root in production builds. I looked up how to do it but its either vague or makes no sense or does not work. why is it a production buold? it didnt do that when i rooted my fire in the first place so why is it doing it now?
What i believed happened is that when i went to past the andoid market's vending.apk into the system/app folder it deleted all of the things in the folder and nothing worked not even the GUI. I hard reset and then i got stuck at the logo. Dont know if that would clarify anything
that clariefys a lot - if you messed up your /system this should help you:
http://forum.xda-developers.com/showthread.php?t=1414832
then you should be able to install twrp
hopefully ...
Thanks but that did not help. It isnt recognized in adb like that.
Can you get into recovery? When you boot it up do you see FireFireFire at all?
No it says KindeFire and its animated.
sorry but i think you'll need a factory cable to get in fastboot mode
you'r not the first one ...
I have a micro usb and it works to connect (well until i followed that link and followed the instructions )
melmantheman said:
No it says KindeFire and its animated.
Click to expand...
Click to collapse
Hi,
Did you have a look at this too:
http://forum.xda-developers.com/showthread.php?t=1356257
I had quite the same issue with mine ...Device was not recognizable at all on Windows (unknown drivers)
I used this guide and it just worked like a charm.
regards
mjay
melmantheman said:
I have a micro usb and it works to connect (well until i followed that link and followed the instructions )
Click to expand...
Click to collapse
i think you did'nt understand what a factory cable is
it's a special cable which forces the kf in fastboot mode
you can build or buy one
make a search for "factory cable" and you'll know ...
http://forum.xda-developers.com/showpost.php?p=21151545&postcount=118
***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.
Alright, so I'm stuck in boot loop, the only recovery I can boot into is stock, which doesn't help obviously. I can't get into download mode, and my computer doesn't detect it. Just tell me the bad news.
Have you removed the LG drivers completely and reinstalled them? How did you get into the bootloop in the first place?
Sent from my LG-D800 using XDA Premium 4 mobile app
whynottry said:
Alright, so I'm stuck in boot loop, the only recovery I can boot into is stock, which doesn't help obviously. I can't get into download mode, and my computer doesn't detect it. Just tell me the bad news.
Click to expand...
Click to collapse
Let me see.. If by download mode you mean the blue dots(circles) then - no, you're not in download mode. But if you can enter teh real download mode (it should go past the circles) then you can flash it ( you should be able to flash it).
More info please.
bender_007 said:
Let me see.. If by download mode you mean the blue dots(circles) then - no, you're not in download mode. But if you can enter teh real download mode (it should go past the circles) then you can flash it ( you should be able to flash it).
More info please.
Click to expand...
Click to collapse
There's a lot of info in his previous posts. We went through hell and back trying to fix it. Hopefully you can give some better guidance.
Art Vanderlay said:
There's a lot of info in his previous posts. We went through hell and back trying to fix it. Hopefully you can give some better guidance.
Click to expand...
Click to collapse
Damn. I've read "I CAN get into download mode and ...." :/
will look into it to help out
one question : how did you brick it ?
Let me copy paste my previous three posts.
"When I originally tried to install TWRP, I was rooted in a stock rom, or whatever you call it when you're rooted and haven't installed a rom yet. When I tried originally, I went through CWM and installed it through that, but whenever I rebooted into recovery, I got the android with the caution sign in its chest. I kept trying to install it, and eventually I believe I used the flashify app to install it(the version I believe was 2.6.3.3) and I tried to boot again and it went into a boot loop, and began making a bunch of drives. I used this http://forum.xda-developers.com/show....php?t=2582142to get me into TWRP, and it worked. Problem is, I have no roms, no backups, no download mode, and my computer only recognizes my phone as 'g2'. I tried to install adb drivers manually so that the computer would recognize it as an adb device, but it gave me error:closed, and that's where we are right now. Quite a hole I have dug myself into, huh?"
"Ok, so I went back into linux -- I have dual boot for windows 7 and ubuntu -- and for some reason adb worked there, so I was able to adb sideload a cwm .img. But of course, I got excited because I thought it would just fix it but now I'm stuck in fastboot mode, and still can't get into download mode."
"I tried it, and now it is stuck in a bootloop and isn't detected by my computer. Only thing I can boot into is stock recovery. Looks like this is the end of my G2.."
I truly do think there's nothing that can be done, just from a logical standpoint. It isn't detected by anything on the computer and can only boot stock recovery which doesn't help at all. I do appreciate the help, though.
bender_007 said:
Damn. I've read "I CAN get into download mode and ...." :/
will look into it to help out
one question : how did you brick it ?
Click to expand...
Click to collapse
Ugh..so no fastboot either :/
fastboot was good.
Hello XDA,
I stupidly put my G2 in bootloop. It is 802, 20h, stock rom/recovery and rooted with ioroot.
I managed to break it by removing the LGweather.apk and LGslideaside.apk from system app because I was tired of seeing them taking memory for no reason. After a reboot, it is blocked at LG logo.
I have made a nandroid backup some time ago through an app so I have those APK on my computer, I just need to put them back with adb.
I can get it to download mode (picture here http://forum.xda-developers.com/showpost.php?p=58181792&postcount=4), but I can't get adb to detect the device although I tried many drivers.
My question are: Am I losing my time by trying to have adb work or it is a driver problem and it will eventually be able to push the file if I can have the phone recognised by adb?
Should I try the hard reset offered through the keys combination? I am very much afraid it would make it worse as I changed many things in the phone through xposed.
Thanks a lot in advance for your help.
Flash the SAME rom via lg flash tool (choose normal mode because it doesn't touch your files)
bender_007 said:
Flash the SAME rom via lg flash tool (choose normal mode because it doesn't touch your files)
Click to expand...
Click to collapse
Well I would have prefered not to, but as I couldn't get adb to work and the hard reset only brought me back LG sound when bootlooping, I had to.
It worked wonderfully, thanks. I have to try to get root back now (even if it shows as rooted in download mode).
The rooted is more like cosmetic
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?