I was trying to root my main driver, a Google Pixel 3 running the most recent version of Android. Initially I was going to flash TWRP and then install Magisk, but TWRP for some reason wouldn't flash, so instead I went about trying to go about the Magisk Canary route. I patched the boot image of the most recent Pixel 3 update and proceeded to flash that in the bootloader. That is when everything went wrong. When the phone rebooted, I found that my touchscreen was no longer working. I tried flashing the boot image using platform tools in the bootloader, but I deleted the -w line in flash_all.bat to prevent a full reset; however this did not solve the issue as I had hoped. I then went into device recovery mode and tried the factory reset option there, but that did not work either. The phone booted and I was in the setup screen with no way to press the buttons using the screen, so I connected an OTG USB device to set the device up only to find that the WiFi is not turning on. I believe there are issues with the mobile network as well as I put in a SIM card but it wan't able to connect to the network; however it did read the SIM card successfully as I was able to "turn on" mobile data. I cannot enable USB debugging to flash anything because I cannot allow the computer's USB debugging request; I either have the computer or my OTG device plugged in. Any ideas on what to do? Thank you in advance!
i have almost the exact problem.
could someone please help
Sounds like the option is, factory image flash-all with the wipe. I believe the OP did not disable/remove modules from magisk before updating. That is something that we all should be aware of at this point. Cost me two bootloops and complete resets, but I learned my lesson. Also backup your stuff. I lost a few pictures, but most of my data and such were restored through Tibu.
Related
I purchased an HP Slate Pro 21 off of ebay that was freezing on boot, and it definitely is. My thought was if I could unlock it and load a different ROM, etc. that the problem may go away. Here is what I have done/figured out so far.
First power on, the device freezes at the first HP logo.
wiping the data (factory reset) allowed me to get into the O/S after several reboots
I was able to enable developer mode and USB debugging, at which point the device forces a reboot.
From this point, no matter what I do I cannot get the device to boot up all the way without freezing.
I can however, reload the factory image from HP's site (tried via SD card, and ADB just in case) and eventually through a multitude of reboots and freezes in different places (i.e. Boot Logo, Animated Boot Logo, Optimizing Apps) it will boot into the setup menus.
Problem is, at this point USB debugging has been factory reset to disabled. If I enable it, I'm back at square one and can't get the device to fully boot up.
There is a menu option to deploy image via ADB, and I can connect to it from my PC but it's (I believe, since I'm a noob) that it's a restricted mode for sideloading only.. Since I can see the device in the device list but it says (sideload) next it and the only adb command that I can run is to transfer an image. Problem is, I only have the HP image.
Are there any other steps to determine if this is a hardware problem? Further things I can do to try and get the device to boot? Other images I can try from ADB or SD Restore that will pass the signature check? (Since I can't load TWRP yet, because it's still locked).
Thanks for any help you can offer!
I've come across a problem that's frustrating me to no end. I've been rooting phones for a few years now, usually older models. A friend asked me to root his newly aquired S6 (canadian model, eh), shouldn't be an isssue. I do the standard issue Enable Developer, wipe data/cache, install root and rom, and call it a day. I go to reboot it, and it's in a boot loop for the Samsung screen. I've had boot loops occur before, I'll take care of it.
I've been at this all day (10+ hours), and still don't have a way to escape this boot loop. Problem is that I didn't know about the Reactivation Lock that was still active when I attempted to root. Here' what I've attempted:
- Uninstall/Reinstall USB drivers several times and different versions. Phone will still not show up under ADB Devices and not detected by windows or toolkits (but will still register via Odin).
- Restore from backup: will only boot into stock recovery mode, no option for restore.
- Reinstall Firmware via USB OTG - "USB access is disabled"
- Install other roms, always fail or are denied access
- Update/Change kernel , see above
I could list on and on all the little tricks and toips i've tried from the internet, but what it essentially comes down to is I can't install anything onto the device due to the device not being recognized or being blocked by a permission, and yet I can't get into the actual Android OS to disable/Enable any permissions. Factory reset does not fix this loop, nor does clearing caches. I've tried sideloading, pushing, and various other means to get into Android, but nothing is working. Help?
Urgent help reqd
randomly my nexus 5 restarted
google came on screen and now only those four animated circles are showing up and the phone doesnt go further
went in bootloader but cant wipe cache, cant format, or anything else from there.
usb debuggng must be off as far as i remember
trying to flash through sdk manager. have downloaded image. but stops at "waiting for device" in cmd and it doesnt go any further than that. even tried doing it manually through cmd.
when the phone is connected it is showing the drivers but it isnt installng and can see the yellow exclamation.
manually downloaded the drivers and tried installing manually but shows drivers are up to date.
uninstalled driver and reinstalled but same issue. it is connected to usb 2.0.
now how do i get it to work?
I have tried all the options i could search for on this forum but none of them solved my issue.
Is the bootloader unlocked?
How do i check that?
Ok got it
It is locked
How do i unlock?
I checked some unlocking bootloader threads but they all require usb debugging to be on.
My phone is not starting at all so i cannot do that
How do i go about it now
Tried nexus root toolkit. It isnt detecting the device.
Unlocking will wipe you device.
Google themselves have a guide on how to flash, not sure why you are using toolkits.
Also, you will wipe your device, if you haven't already. Make sure you have the right drivers, make sure you get the device to come up under "fastboot devices"
Already tried all methods mentioned by google or xda.
If you read my initial post my phone is not getting detected as well but shows installing drivers when connected but the installation fails.
Manually install the correct drivers.
Tried that but i get the error that you already have latest drivers. But its not detecting the phone
Try removing the drivers and reinstalling
Also, try different USB ports and cables.
Did all of that a number of times. Still no luck
Other phones are getting connected and detected just fine.
useruser12 said:
Urgent help reqd
randomly my nexus 5 restarted
google came on screen and now only those four animated circles are showing up and the phone doesnt go further
.
Click to expand...
Click to collapse
Hi all, i have a similar problem
this morning my n5 boots into "optimizing apps", but stops when reach around 15/20 apps and reboot (3 or 4 times)...
Now, only keeps in android animation like useruser12.
I can see my data in TWRP, battery 95%...
I wipe cache/dalvik... nothing
I reflash the kernel (ElementalX 6.17), still nothing
Any ideas?
PS: latest news. After make a backup, I made a factory reset and restore a system-boot-cache partition from old backup. Now the phone boots but i hate lose all my data xD. I want try to solve my problem using my "corrupted" backup for avoid losing data. If that fails, I can always restore this functional backup. Any ideas again?
Used the nexus root toolkit.managed to unlock bootloader but immediately the device reboots and goes into the bootloop again.
Tried the flash stock + unroot function as well which detected my factory image and everything went smooth till it came back to unlocking the bootloader and rebooting the device after that and again went into the bootloop
Though i have installed the drivers, on reboot windows 7 automatically starts installing the mtp usb device driver but fails. Manually downloaded the drivers and installed as well.
Still its not worked and whatever i do it comes back and get stuck at the bootloop.
Any expert can give a solution? Thanks
After unlocking the bootloader, does the bootloader relock when the phone is rebooted? If it does, the memory chip is defective.
Phone doesnt reboot completely.goes into a loop after the google logo and doesnt go further.
If i switch off the phone midway here without it booting up and then restart the bootloader then its locked again.
But what i read was that the process of complete reboot needs to finish and i need to turn on usb debugging. So is it because of that the bootloader locks again?
Anyways, this what im facing
Dalamar666 said:
Hi all, i have a similar problem
this morning my n5 boots into "optimizing apps", but stops when reach around 15/20 apps and reboot (3 or 4 times)...
Now, only keeps in android animation like useruser12.
I can see my data in TWRP, battery 95%...
I wipe cache/dalvik... nothing
I reflash the kernel (ElementalX 6.17), still nothing
Any ideas?
PS: latest news. After make a backup, I made a factory reset and restore a system-boot-cache partition from old backup. Now the phone boots but i hate lose all my data xD. I want try to solve my problem using my "corrupted" backup for avoid losing data. If that fails, I can always restore this functional backup. Any ideas again?
Click to expand...
Click to collapse
Lucky that you could do a factory reset. I wasnt even able to do that from the bootloader.
useruser12 said:
Lucky that you could do a factory reset. I wasnt even able to do that from the bootloader.
Click to expand...
Click to collapse
Sorry, i did it via TWRP.
If the bootloader relocks itself upon reboot, it's the memory chip that is damaged.
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.
MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...
You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.
We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask
What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.
shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6
Helium is a great alternative to titanium.
hello, recently i bought myself a new op6, as it was good for modding and such. unlocked the bootloader, flashed twrp, and rooted it the day after, used it for a couple of days, before I installed elementalX. was happy with that for some days. then I decided I wanted to try out lineageOS, in order to de-google my self, in my quest for privacy.
TL;TR:
mtp is not working after flashing, neither is twrp, cant even access it through fastboot with booting the .img file.
does this have something to do with the a/b partition thing on these phones, perhaps?
I would guess that I flashed lineageOS the wrong way, and that is the issue, but since I cant access twrp, I cant restore and reflash the correct way.
more detailes below
--------------------------------------
backed up before installing elementalX, to have something to go back to, in case of failure
rebooted into twrp, and wiped everything, exept internal storage (i looked this up several places, prior to flashing, that this was the way to do it, so assumed this was the correct way)
flashed lineageOS 15.1
wiped dalvik and rebooted
took ages to boot, so figured id reboot again a couple of times, with no succsess
tried to boot to twrp, to restore back state prior to flashing, but ended up in lineageOS' own recovery.
tried to boot from fastboot, and reflash twrp
goes out of bootloader and screen turns black, led turns on, and nothing. tried waiting for a bit, but nothing seems to happen
have to manually turn of phone, and reboot. tried this several times, but same result.
after reboot i turned to the recovery to look after any solutions there, but nothing
started adb, just to check, and it says "device unauthorized"
sortof gave up, so figured I could atleast get going installing apks, but after downloading f-droid, I couldnt get it to install
found out this was some sort of permission issue, so had to move it to internal storage to get it to install
after installing some apks, I was going to transfer my contacts from my pc, but cant get mtp working..
if someone know a soulution to this, I would be really greatfull, as Im at a loss. cant seem to find anyone who has had a simillar issue..
You can always use EDL and MsmDownloadTool. Check that thread
thanks, will definetly check that out.
now it apears that I have another issue, the key for adb is no longer valid. i did get the prompt when I connected the usb, but that didnt appear to do anything. have tried to revoke it, reanable, reboot both phone and pc, also delete the keys on my pc. I have no root access anymore, so cant really enter the root on my phone, to pull out the keys there, neither can i push my own keys, as it seems atleast. I may be doing it wrong too, for all i know..
If you can enable debugging and see your phone with adb devices, you can adb push /sdcard/<romfile>.zip
I am able to enable debugging mode, yes. Will this enable me to push my own key, or any other existing key for that matter, to remove the unauthorized label?
Id also like to at that i done goofed when flashing lineageOS. Ive come to and understanding that I have to flash OOS 1.5.1 (i think that was it) on both slots, before then flashing the custom rom onto the device, and reflashing twrp after that. Which i did not do. I also were running pie at that time, so theres another mistake I made to begin with. Neither was I really aware of the concept of a/b partition system at hand..
Can i switch slots in fastboot, and then boot inton twrp, and reflash back to OOS 1.5.1, on both slots, and then reflash LOS 15.1? And ofcource reflash twrp and root afterwards, which totally slipped my mind..