Related
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
brooklynchildxbc said:
os deleted and just stuck on one+ logo can boot in to twrp or fast boot what can i do?
Click to expand...
Click to collapse
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
acuicultor said:
Push a custom rom via adb and flash in recovery or flash stock images via fastboot
Click to expand...
Click to collapse
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
brooklynchildxbc said:
i tried adb won't work and fastboot not doing anything i keeping getting a error saying that bootloader locked or can't erase
what really pisses me off i didn't even brick it a dumbass friend of mine did thinking he knew what he was doing.
Click to expand...
Click to collapse
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
boober78 said:
Is fastboot working? Unlock bootloader and push custom recovery there. Go to adb sideload and that should work eventually. I had an issue with HTC One M7 - someone deleted sytem, and cyanogenmod installer helped, because it pushed CWM recovery, maybe try that one as well?
Click to expand...
Click to collapse
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
No problem. I'm glad I could help
Sent from my One using Tapatalk
brooklynchildxbc said:
thank you so much i gave up then tried what you said then all of a sudden adb connected and i sideloaded the update file and got it back
Click to expand...
Click to collapse
Don't give up.... I was in the same position like you for a couple days....and now is fix by my self..... If you unlock your bootloader try to lock back (fastboot oem lock) now try to flash via fastboot Philz Recovery ( try until is rebooting himself into recovery) .... After that put on a memory stick the new system .... You may need to mount the USB flash drive ..... That's exactly what I have done....Good Luck ...
It is damn near IMPOSSIBLE to actualy, truly "brick" these devices. There are way too many safeguards in place.
Be careful before announcing that you are "bricked". Bootlooping (which is what your device was doing) is not "bricked". As long as you have fastboot, you can always reflash recovery, and then use recovery to reflash your custom ROM (or you can bypass all of that and reflash the factory images from fastboot).
Don't panic, you know more than you think you know. Just don't get freaked out, and read. You'll be fine.
Is there a guide for rooting the Rogers Pixel on 7.1.1??
Sent from my Pixel using XDA-Developers Legacy app
christanya99 said:
Is there a guide for rooting the Rogers Pixel on 7.1.1??
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886 disregard anything about verizon as you do not have that model.
its for the XL but the exact same method applies, just make sure you get the TWRP RC1 zip and image from here
root is here 2.79 SR3
Great, thanks a ton!
Sent from my Pixel using XDA-Developers Legacy app
k.s.deviate said:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886 disregard anything about verizon as you do not have that model.
its for the XL but the exact same method applies, just make sure you get the TWRP RC1 zip and image from here
root is here 2.79 SR3
Click to expand...
Click to collapse
I just rooted successfully but didn't install TWRP. Can I just boot back in through fastboot and install it now?
christanya99 said:
I just rooted successfully but didn't install TWRP. Can I just boot back in through fastboot and install it now?
Click to expand...
Click to collapse
Yes, put the zip on your internal storage and boot into fastboot and then boot into the TWRP image and flash the zip.
k.s.deviate said:
Yes, put the zip on your internal storage and boot into fastboot and then boot into the TWRP image and flash the zip.
Click to expand...
Click to collapse
Uh oh! Just did this now it's booting straight to TWRP...
christanya99 said:
Uh oh! Just did this now it's booting straight to TWRP...
Click to expand...
Click to collapse
Put the TWRP RC1 zip on the internal storage
Fastboot boot TWRP RC1.img
*Might have to do that a couple times for TWRP to properly decrypt.
Flash TWRP RC1 zip to apply it
That's how to get TWRP.
Your saying you did this and when you reboot system from TWRP it just reboots to TWRP?
k.s.deviate said:
Put the TWRP RC1 zip on the internal storage
Fastboot boot TWRP RC1.img
*Might have to do that a couple times for TWRP to properly decrypt.
Flash TWRP RC1 zip to apply it
That's how to get TWRP.
Your saying you did this and when you reboot system from TWRP it just reboots to TWRP?
Click to expand...
Click to collapse
Exactly. I can't boot into the system anymore. Google logo pops up and then straight to TWRP every time.
christanya99 said:
Exactly. I can't boot into the system anymore. Google logo pops up and then straight to TWRP every time.
Click to expand...
Click to collapse
Almost sounds like you fastboot flashed TWRP instead of fastboot boot TWRP. Either way, I believe you will have to flash the factory image and start over. You could try fastboot flashing the stock boot image first to see if that helps.
k.s.deviate said:
Almost sounds like you fastboot flashed TWRP instead of fastboot boot TWRP. Either way, I believe you will have to flash the factory image and start over. You could try fastboot flashing the stock boot image first to see if that helps.
Click to expand...
Click to collapse
Ok, thanks! Will give it a try.
That did it. All is good now. Thanks!
I was following the directions here on how to unlock and root my new pixel, and after the fastboot boot-to-image step, it restarted a few times (as it was supposed to) and then it got stuck on the bouncing dots stage. When I attempted to restart into recovery, I instead got a "[Ramdump] writing to EXT4 file" message, and I was not able to get into recovery after several attempts. Are there any options for recovering this or did I manage to brick it beyond repair?
Thanks
Are you able to flash the factory image?
roirraW "edor" ehT said:
Are you able to flash the factory image?
Click to expand...
Click to collapse
or flash the recovery TWRP
roirraW "edor" ehT said:
Are you able to flash the factory image?
Click to expand...
Click to collapse
After the battery drained overnight, I manged to boot into recovery. Is it worth it to try and see if it starts normally or should I leave it in recovery and try the factory reflash? If the reflash, should I pick the most recent image, or do I need to pick the correct one that it came with?
henk-jan said:
or flash the recovery TWRP
Click to expand...
Click to collapse
Even though ADB recognizes my device now (I was able to boot into recovery after the battery drained overnight), I can't see it on my computer to manually transfer files, can I push the TWRP .zip file onto the device using ADB, and does it matter where on the device it gets put (the instructions just say to copy it to the device)?
cdenney said:
After the battery drained overnight, I manged to boot into recovery. Is it worth it to try and see if it starts normally or should I leave it in recovery and try the factory reflash? If the reflash, should I pick the most recent image, or do I need to pick the correct one that it came with?
Click to expand...
Click to collapse
It won't hurt anything to see if it'll boot. Most recent image.
roirraW "edor" ehT said:
It won't hurt anything to see if it'll boot. Most recent image.
Click to expand...
Click to collapse
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
cdenney said:
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
Click to expand...
Click to collapse
If you're in any way hesitant, don't touch it. I wouldn't relock the bootloader personally.
cdenney said:
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
Click to expand...
Click to collapse
You don't need anything but SuperSU zip to root. Enable developers option in settings, enable usb debugging, in fastboot mode fastboot boot TWRP IMG, if you want custom recovery, flash pixel TWRP zip, reboot recovery, flash SuperSU, reboot, otherwise skip TWRP zip and reboot recovery part. No boot to root is necessary. Just flash SuperSU. Simple.
Here is link to TWRP IMG to boot into
https://dl.twrp.me/sailfish/twrp-3.0.2-0-RC1-fastboot-sailfish.img.html
...
cdenney said:
Flashing the factory image worked. Now I just have to decide if I try it again or just relock the bootloader and leave well enough alone. Thanks!
Click to expand...
Click to collapse
I will say, I had this exact issue before. The issue was that I had inadvertently used an older version of fastboot. Worth double checking.
Tulsadiver said:
You don't need anything but SuperSU zip to root. Enable developers option in settings, enable usb debugging, in fastboot mode fastboot boot TWRP IMG, if you want custom recovery, flash pixel TWRP zip, reboot recovery, flash SuperSU, reboot, otherwise skip TWRP zip and reboot recovery part. No boot to root is necessary. Just flash SuperSU. Simple.
Here is link to TWRP IMG to boot into
https://dl.twrp.me/sailfish/twrp-3.0.2-0-RC1-fastboot-sailfish.img.html
Click to expand...
Click to collapse
Hey you mind giving me guild on how it is done, i am lost here. I read number of them but do not wish to brick my phone.
Thank you
Hey Guys,
So my idiot brain decided to mess around with substatum themes after I updated and rerooted my OP7P. I rooted with magisk but forgot to put TWRP recovery on.
Anyways, got the phone semi bricked when applying one of the overlays. The phone boots and I can see my lock screen wallpaper but the screen is just flashing on/off.
I cant use the fingerprint or pin to get it. Is there a way for me to backup my pictures and data or somehow remove substratum?
Biggest problem is that for whatever reason, the update revoked my ADB authorization so it looks like I cant do anything with ADB.
If someone has any way to salvage my situation, please reply. Factory reset is my last resort due to no backup.
Thank You
Try booting into TWRP and using ADB there.
Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go
tech_head said:
Try booting into TWRP and using ADB there.
Click to expand...
Click to collapse
pranacrockz said:
Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go
Click to expand...
Click to collapse
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen
morphius88 said:
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen
Click to expand...
Click to collapse
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool
pranacrockz said:
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool
Click to expand...
Click to collapse
Rebooted to fastboot, entered the PIN but Fastboot is a no go. Just keeps saying <waiting for any device> and nothing happens. Would that be because the authorization keys were not accepted after the update?
I am downloading the MSM Tool and will try that if I cant get it to work with fastboot. Will update if it works.
Thanks for suggestions
Ended up using the MSM tool. Did not know it wipes data and also put me back to Android 9.
Oh well, lesson learned. Gotta make monthly backups, make sure twrp is installed and working before messing around with substatrum.
Thanks for the help.
Hello, newbie here..
Need help!! My phone keeps booting to TWRP whenever I turned it on, connected it to PC, or even when I connected it to my charger.
It happened after I mistakenly uninstalled a system app (it is an app named Freeshare). I thought it was just a sharing app like MiDrop or ShareIt, but clearly that was a mistake.
Now I just can't seem to boot into the system, not even able to enter into the download mode.
I've tried a method that I found in here, like entering a code in TWRP terminal (it was "dd if blablabla", i forgot. Lol), to no avail.
Haven't tried to flash the stock rom or stock boot since I can't find any zip Stock Rom for my phone (my phone is Gome Fenmmy Note).
Does anyone have an idea or know how to fix it?
Thanks in advance
Did you flash MISC partition?
Give a try on this (plese, method #2 only): https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Or you can try to FORMAT the misc partition inside the TWRP.
Or did you flash TWRP to boot partition ??
TWRP needs to be flashed to RECOVERY partition.
If you flash TWRP to boot partition, your device will boot forever to recovery.
If yes, you need to flash the original stock boot.img
VD171 said:
Did you flash MISC partition?
Give a try on this (plese, method #2 only): https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Or you can try to FORMAT the misc partition inside the TWRP.
Click to expand...
Click to collapse
But before i mistakenly uninstalled the system app, my phone is completely fine. No twrp bootloop when i rebooting hte phone. The bootloop happened after I uninstalled a system app.
But thanks anyway. Will try this after I got home.
disegiooo said:
But before i mistakenly uninstalled the system app, my phone is completely fine. No twrp bootloop when i rebooting hte phone. The bootloop happened after I uninstalled a system app.
But thanks anyway. Will try this after I got home.
Click to expand...
Click to collapse
You don't need to uninstall a system app for disabling it completely.
If you've uninstalled a system app, you've modified your system.
1. Did you unlock bootloader?
2. Did you flash vbmeta with disabled verification?
3. Did you root your device?
4. Did you debloat your device?
You can't modify your system before the answer for all questions be YES.
Probably you need to flash the SYSTEM again.
(Only system should be enough.)
VD171 said:
You don't need to uninstall a system app for disabling it completely.
If you've uninstalled a system app, you've modified your system.
1. Did you unlock bootloader?
2. Did you flash vbmeta with disabled verification?
3. Did you root your device?
4. Did you debloat your device?
You can't modify your system before the answer for all questions be YES.
Probably you need to flash the SYSTEM again.
(Only system should be enough.)
Click to expand...
Click to collapse
For questions 1,3,4 the answer is YES. For question 2, I'm not really sure.
Okay, so I need to flash the system again. Can I just flash the system.img through TWRP? Since it won't enter fastboot or download mode. Since once I connect my turned off phone to PC, it will immediately reboot to TWRP.
Sorry, if I'm asking too much. Please be patience.
disegiooo said:
For questions 1,3,4 the answer is YES. For question 2, I'm not really sure.
Okay, so I need to flash the system again. Can I just flash the system.img through TWRP? Since it won't enter fastboot or download mode. Since once I connect my turned off phone to PC, it will immediately reboot to TWRP.
Sorry, if I'm asking too much. Please be patience.
Click to expand...
Click to collapse
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
VD171 said:
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
Click to expand...
Click to collapse
VD171 said:
Are you sure you can't enter in fastboot mode?
I'm not sure, but I think to flash system using TWRP you need to convert sparse image to regular image using simg2img first.
Click to expand...
Click to collapse
Well, I haven't tried to enter fastboot using adb yet since the phone will automatically turn on and boot into TWRP if i connect it to PC using usb cable. Is it possible to enter fastboot using adb eventhough the phone isn't turned off and in TWRP mode?
I see, so i need to convert the image into regular image first. Got it.
I'll try all of your suggestions. Hope it worked.
disegiooo said:
Well, I haven't tried to enter fastboot using adb yet since the phone will automatically turn on and boot into TWRP if i connect it to PC using usb cable. Is it possible to enter fastboot using adb eventhough the phone isn't turned off and in TWRP mode?
I see, so i need to convert the image into regular image first. Got it.
I'll try all of your suggestions. Hope it worked.
Click to expand...
Click to collapse
Yes.
Enter in twrp.
Plug usb cable.
Type "adb devices" and check your device is detected.
And then try "adb reboot bootloader"
VD171 said:
Yes.
Enter in twrp.
Plug usb cable.
Type "adb devices" and check your device is detected.
And then try "adb reboot bootloader"
Click to expand...
Click to collapse
Hello, sorry for late reply. Yes my phone now able to enter the fastboot mode. Then what should i do next to flash my stock rom? I can't turn off my phone
disegiooo said:
Hello, sorry for late reply. Yes my phone now able to enter the fastboot mode. Then what should i do next to flash my stock rom? I can't turn off my phone
Click to expand...
Click to collapse
If you can enter in fastboot mode, you can flash the rom easily.
But it requires unlocked bootloader.
If your bootloader is locked, you need to flash using SP FLASH TOOL.
Just download the stock rom, extract it and flash using any of the flashing script (if available).
Good luck
VD171 said:
If you can enter in fastboot mode, you can flash the rom easily.
But it requires unlocked bootloader.
If your bootloader is locked, you need to flash using SP FLASH TOOL.
Just download the stock rom, extract it and flash using any of the flashing script.
Good luck
Click to expand...
Click to collapse
Alright, my phone bootloader is unlocked. Then how do I flash the stock rom?
Sorry, I'm completely a noob.
disegiooo said:
Alright, my phone bootloader is unlocked. Then how do I flash the stock rom?
Sorry, I'm completely a noob.
Click to expand...
Click to collapse
I suggest you to watch some videos in youtube.
Certainly, it helps alot.
VD171 said:
It's same for all xiaomi devices.
I suggest you to watch some videos in youtube.
Certainly, it helps alot.
If you don't know how to flash manually using fastboot, try MiFlash:
Click to expand...
Click to collapse
Thank you very much. Managed to flash the stock rom safely.
Once again, thank you for your help! May God bless you
disegiooo said:
Thank you very much. Managed to flash the stock rom safely.
Once again, thank you for your help! May God bless you
Click to expand...
Click to collapse
Good job, my friend
You are welcome.
God bless you too
About disabling preinstalled apps, try to perform this in command line:
pm disable-user --user 0 com.android.chrome(Change com.android.chrome to desired package name to disable.)