Hi,
I need help with my one m9, recently i paid someone too root and install custom rom to my phone and phone was installed with lineageos everything was great about 2 weeks. Than without reason first bluetooth started stop working, than wifi did the same thing. Than ı made a something very very stupid and wiped the system. After hard struggling, i was able to reinstall lineage os 16(by tempering with updater-script file via notepad++), but wifi and bluetooth are still not working. I can enter dowload mode, bootloader mode and trwp but i can not install another rom or update twrp. when I tried to install Lineage os 17 i get error "error creating fstab" when ı try to update twrp i get "failed to boot to recovery mode" error ( i tried installing image via twrp and tried flashing via bootloader). I need any solution to make bluetooth and wifi work again. thanks for any help
any one?
Related
Hello! Im using HTC M8, yesterday i decided to root it so I used this guide to do bootloader activation, flashing recovery and rooting it (h t t p :/ / theunlockr.com/2014/04/19/root-htc-one-m8-all-in-one-toolkit-method-video/).
Everything was fine till i done everything and started my phone. I tried to run Supersu, and i got message that Supersu binary is not installed, i tryed to update it from googleplay, but nothing. Than i decided to flash updated version found on internet, now i get strange things like, x application failed to run , report this to HTC, my phone storage is not recognized or shown in any file menager or when i connect it to pc, i cant download anything from chrome, to my phone... Help please. What to do?
I tryed factory reset, reflashing recovery, but nothing happend. I have plan to instal newest version of super su but i cant put it in phone root to instal it from recovery boot...
Somebody?! Anything?
Hello everyone, first post here and I really hope you can help me. I have installed TWRP in my device and I have used it to make backups and install custom roms, in this case cyanogenmod, but after actualizing cyanogenmod, it enter in some kind of bootloop, it turns on normally but stays initializing the rom and after literally hours the device restart itself. I tried then to enter TWRP and use the backup, but it enter odin mode instead, that pretty much burn my plan B, so... Someone can help me?
Are you flashing the correct version of TWRP and CM for your phone?
Boot into download to confirm your phone's model # and make sure it is running the latest bootloader and modem.
Hi everyone, I manage to solve the problem, I reinstall TWRP with Odin and use it to wipe all, incluing the system files, and reinstall cyanogenmod. Bow everything is working perfectly. If someone is having the same problemI hope this can help.
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
[SOLVED]
went back to stock recovery and side loaded the full 1.4 gb rom i will leave a link for tutorial that i used, i wanted to get back to complete stock and this was the one use
"https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/"
When you have TWRP you have to install full zip, not simply the eval OTA zip
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
Flash the stock recovery.
Get stock recovery from downloads.oneplus.net
I cant seem to flash the stock recovery. The device is not visible in adb devices or fastboot devices. im facing the same issue.
If you are using TWRP 3.0.4-0 - try a hard boot...hold down the power button for 20s...wait 20s, power it back on.
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
easy solution. Boot into fastboot
download this tool.
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
if newest version isnt working, download an older version with older twrp
than unzip the tool and run the .bat file and install twrp.
Thats it
There are many posts on Nougat not working with official TWRP (based on 6.0 build). Try booting into stock recovery. performing a system settings reset, then booting into fastboot and run the adb command, <fastboot boot TWRP-3.0.2-1.28.img>. From there you can do virtually anything you need to do. I recommend at least using a modified version of TWRP (such as 1.28). This has been posted many times before, please try and do a search for the answers first, it will help tremendously. Thanks
recovery
i had the same problem on my rooted OP3 when i used TWRP 3.0.2-1 , it worked to flash the full 4.0.1 rom but failed for everything else, flashing latest verion of twrp fixed it for me
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Aislandas said:
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Click to expand...
Click to collapse
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Noted that you solved your issue, but this post is about the new version of TWRP. Version 3.0.3 is available on twrp.me and it works with Nougat.
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Gave up trying and booked a session with OP technicians Will see how it goes in a week.
So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.
Czechball said:
So. Recently, I got CyanogenMod 13 on my Gpad. Everything was just fine. Then I installed the Magisk Manager, which, for some reason, disabled the root access on the device. When I uninstalled it, my recovery (TWRP) asked me, if I want to install SuperSU. I selected yes. And that's the moment when everything fcked up. After SuperSU installation, my tablet went into bootloop, and I wasnt't even able to enter recovery via button combination. I tried to flash the stock rom via LG Flash Tool, but failed miserably. I tried multiple stock roms, but the result is till the same: I can't access the Factory Reset via buttons, the system keeps rebooting, and even if it boots for few seconds, the touchscreen isn't responding. I even tried connecting mouse via USB otg, but no success. Is my tablet dead? Is there any chance of repairing it?
Thank you for your help.
EDIT: It's v500 European version.
Click to expand...
Click to collapse
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers
dirlan2001 said:
nope, it's not death (yet)... The buttoncombo to enter might be a problem, but keep trying. If really nothing goes, try connecting to your PC and open a commandline. Type : adb reboot recovery (preferably from a linuxbox). However, make sure you got a ROM, GApps and SU system 2.78 or 2.79 ready on the SD. Personally I recommend @adrianom AOSP 7.1.1, OpenGApps micro and SU 2.79 SR2'systemmode.
Cheers
Click to expand...
Click to collapse
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.
Czechball said:
Thank you for your reply.
However:
I am not able to stay in the system.
I am not able to enter the recovery. (because of the brick)
I am not able to enter ADB, because there's just no way how. I have USB debugging disabled by default (because I tried to reset the system using LG Flash Tool) and I can't use ADB in the download mode.
Actually, download mode is the only thing that hasn't broke yet. I still hope that someone that has experienced similar problems help me.
But again, thanks for your (and the only) reply.
Click to expand...
Click to collapse
If you can get into download, you could connect to a PC and start the LG-tools.Use that to restore to the original ROM and start allover again with latedt software (TWRP, ROM, SU)
Cheers
Hey everyone, so I saw that there was a new update for MIUI Developer ROM (9.3.28) and I decided to download it. After I downloaded it, i opened twrp and flashed it with lazyflasher as I always do. After the phone boots normally, i realised that the phone had been upgraded to android pie, so I went to check google camera to see if it was working still, but it didnt. So I went back to TWRP to try to enable HAL3 via adb shell, but when i opened TWRP i saw a strange message. It asked for a password in order to decrypt my data. this was the first time i saw it and after searching a bit I tried to use my phones password, but it didnt work. I decided to ignore the message and just open adb shell and enable HAL3. The thing is that when I tried to open it said device not found, which is really strange ( im using the same computer as i was before, adb is installed of course ). I had no choice but to downgrade to stable, so I tried to downgrade to stable rom. Downloaded the rom, but when i chose "choose package" it wouldnt let me install the stable one because it was an older version of android....
So long story short, Android Pie has left me with a non-working Google Camera, TWRP and no ability to downgrade or flash and ROMs.
Any help would be appreciated
https://www.youtube.com/watch?v=bsbZ3kG88Dw
Same problem with me. I tried everything but no luck and now I am unable to use camera2api. So i thought to root my phone and edit build prop manually but when I flashed magisk my phone stuck at boot logo. I lost all my data and I had to flash with mi flash tool. Luckily my bootloader was unlocked.
After flashing Pie, you have to flash a TWRP recover for MIUI Pie. This will allow to decrypt your device (data will be erased).
If you want to rollback to stable (as I did), download fastboot ROM via MIUI official site, boot to bootloader and flash it via flash_all.bat file included in the ROM (assuming you have fastboot on your PC).