Related
My friend Rooted my phone using TWRP 2.4. I need to sed the phone back to T-Mobile and need to return it to stock but have no Idea what I need to do and all the info I find is just confusing can someone help me find the RUU I need and some instructions I can follow to return the phone to stock. Thank in advanced
imfocused said:
My friend Rooted my phone using TWRP 2.4. I need to sed the phone back to T-Mobile and need to return it to stock but have no Idea what I need to do and all the info I find is just confusing can someone help me find the RUU I need and some instructions I can follow to return the phone to stock. Thank in advanced
Click to expand...
Click to collapse
is yours T-Mobile US?
if so, Try This RUU.
khan.orak said:
is yours T-Mobile US?
if so, Try This RUU.
Click to expand...
Click to collapse
Thanks man now I have a bigger problem because I may have Soft bricked my phone loading a JBsmooth ROM
imfocused said:
Thanks man now I have a bigger problem because I may have Soft bricked my phone loading a JBsmooth ROM
Click to expand...
Click to collapse
The RUU I prescribed above will take you to stock IF your phone is from T-MO US.
Just go to bootloader then select Fastboot, connect your phone to PC and run this RUU.
khan.orak said:
The RUU I prescribed above will take you to stock IF your phone is from T-MO US.
Just go to bootloader then select Fastboot, connect your phone to PC and run this RUU.
Click to expand...
Click to collapse
I am doing what you said but I never see the RUU even though I copied it to my phone or am I running it from my PC?
imfocused said:
I am doing what you said but I never see the RUU even though I copied it to my phone or am I running it from my PC?
Click to expand...
Click to collapse
You have to run it from your PC, it's an executable file with an extension .exe ... so it will work on PC and not the phone
khan.orak said:
You have to run it from your PC, it's an executable file with an extension .exe ... so it will work on PC and not the phone
Click to expand...
Click to collapse
Ok I id that but I keep getting a usb connection error even though it shows up in my computer.
imfocused said:
Ok I id that but I keep getting a usb connection error even though it shows up in my computer.
Click to expand...
Click to collapse
- USB Drivers
- Plug it into USB 2.0 ports and not 3.0
- faulty cable
khan.orak said:
- USB Drivers
- Plug it into USB 2.0 ports and not 3.0
- faulty cable
Click to expand...
Click to collapse
Ok thanks man so I installed the USB driver and that fixed my issue but after running the RUU that you gave me I received a "Signature error" so do I need a different RUU?
imfocused said:
Ok thanks man so I installed the USB driver and that fixed my issue but after running the RUU that you gave me I received a "Signature error" so do I need a different RUU?
Click to expand...
Click to collapse
Yeah that usually means different RUU needed.
Do you know what your phone's CID is?
If you don't know, go to fastboot from bootloader on your phone.
Open a Command window and navigate to the directory where your adb+fastboot files are located and enter this command.
Code:
fastboot getvar cid
It'll help me narrow down the usable RUUs.
khan.orak said:
Yeah that usually means different RUU needed.
Do you know what your phone's CID is?
If you don't know, go to fastboot from bootloader on your phone.
Open a Command window and navigate to the directory where your adb+fastboot files are located and enter this command.
Code:
fastboot getvar cid
It'll help me narrow down the usable RUUs.
Click to expand...
Click to collapse
It says TMOB010
imfocused said:
It says TMOB010
Click to expand...
Click to collapse
Okay then the RUU is correct.
You may have left your bootloader unlocked.
You need to relock it.
Go to Fastboot on your phone and enter this command to lock bootloader from your PC:
Code:
fastboot oem lock
Boot into fastboot again and run the RUU.exe
THANK YOU SO MUCH!!! This fixed y phone now I can return my phone. But I don't think I will ever root or Flash my ROM again lol. Things have changed since I was flashing ROMS.
imfocused said:
THANK YOU SO MUCH!!! This fixed y phone now I can return my phone. But I don't think I will ever root or Flash my ROM again lol. Things have changed since I was flashing ROMS.
Click to expand...
Click to collapse
No problem bud, Flashing is fun. you might get tempted again .. HOPEFULLY
khan.orak said:
No problem bud, Flashing is fun. you might get tempted again .. HOPEFULLY
Click to expand...
Click to collapse
I Sure I will because I hate all the Bloat that gets loaded on the phone. I just cant find clear cut instructions for loading ROMs these days.
imfocused said:
I Sure I will because I hate all the Bloat that gets loaded on the phone. I just cant find clear cut instructions for loading ROMs these days.
Click to expand...
Click to collapse
If you need any help just ask, pm anything.
Sent from my HTC One S using Tapatalk 4 Beta
thanks khan.orak , it was helpful for me too for getting back to stock rom .
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Colday96 said:
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Click to expand...
Click to collapse
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
phaino00 said:
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
Click to expand...
Click to collapse
I bought the phone on ebay. Could i still get a RMA replacement ?
Colday96 said:
I bought the phone on ebay. Could i still get a RMA replacement ?
Click to expand...
Click to collapse
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
If you bl locked the phone w modified software ur boned. I believe that RMA availability is transferrable from owner to owner, however, I also believe that they will refuse to RMA a phone which technically broke because AVB is doing its job properly. You can try but I'd say your chances are slim. Sorry mate. Also future reference: if you don't have any reason in particular to relock your phone, just don't. You'll save yourself the hassle of having to do it again and it wiping the phone everytime any software thing goes wrong or anytime u want to upgrade custom ROM or kernel or anything of the sort. This goes for any phone not just those with android verified boot.
phaino00 said:
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
Click to expand...
Click to collapse
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Assume they will.
Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Yes they will know but they have proprietary software to forcefully unlock/reformat the phone properly if they so choose to actually accept the phone
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Click to expand...
Click to collapse
You can still sell it for around 150 for parts on ebay
Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400
Click to expand...
Click to collapse
Can't you restore using the stock zips from google?
Poebat said:
Can't you restore using the stock zips from google?
Click to expand...
Click to collapse
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Nandolkz said:
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Click to expand...
Click to collapse
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Poebat said:
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Click to expand...
Click to collapse
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Nandolkz said:
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Click to expand...
Click to collapse
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Poebat said:
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Click to expand...
Click to collapse
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Colday96 said:
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Click to expand...
Click to collapse
He doesn't have a working OS so I doubt it
Here is what is happening to me... Any ideason how to fix it? ?
Nandolkz said:
Here is what is happening to me... Any ideason how to fix it? ?
Click to expand...
Click to collapse
Try flashing the stock rom with fastboot
Poebat said:
Try flashing the stock rom with fastboot
Click to expand...
Click to collapse
Here
Followed the same instructions here: https://www.the***********.com/unlock-bootloader-google-pixel-3-xl-guide/
and it worked. I know this is probably obvious to everyone on this forum, but just in case anyone was wondering if the version from google was easily unlock able out of the box, it is. I was able to get the device early as a product advocate. Being that not a lot of people on XDA have the device yet, I may be the first person to unlock their Pixel 4 XL? :angel:
elsamuraiguapo said:
Followed the same instructions here: https://www.the***********.com/unlock-bootloader-google-pixel-3-xl-guide/
and it worked. I know this is probably obvious to everyone on this forum, but just in case anyone was wondering if the version from google was easily unlock able out of the box, it is. I was able to get the device early as a product advocate. Being that not a lot of people on XDA have the device yet, I may be the first person to unlock their Pixel 4 XL? :angel:
Click to expand...
Click to collapse
Thanks for the info, excellent news for Verizon subscribers with Pixel 4!
Not from THAT link....
Sent from my Pixel 2 XL using Tapatalk
I don't understand what you need a link for. Isn't it like every other device? Turn it on fastboot mode, hook up to your PC, check to make sure it's read, type in fastboot oem unlock, boom. Am I missing something?
ZeroKool76 said:
I don't understand what you need a link for. Isn't it like every other device? Turn it on fastboot mode, hook up to your PC, check to make sure it's read, type in fastboot oem unlock, boom. Am I missing something?
Click to expand...
Click to collapse
Sometimes it's about the peace of mind to make sure it's being done properly
ZeroKool76 said:
I don't understand what you need a link for. Isn't it like every other device? Turn it on fastboot mode, hook up to your PC, check to make sure it's read, type in fastboot oem unlock, boom. Am I missing something?
Click to expand...
Click to collapse
Why put the link in there if it's not a valid link?
Sent from my Pixel 2 XL using Tapatalk
samteeee said:
Thanks for the info, excellent news for Verizon subscribers with Pixel 4!
Click to expand...
Click to collapse
The Verizon version will be locked.
Have you tried booting Magisk on it yet?
Did you have to turn it on and enable OEM unlocking in Developer options first or nah?
did you try root it ?
mine is coming today
it shipped last night before i went to bed lol
please system dump
brownkid said:
Did you have to turn it on and enable OEM unlocking in Developer options first or nah?
Click to expand...
Click to collapse
You need to turn it on and enable it
I just got my Pixel 4 XL. I want to root, but without the system image how can I get the boot image to patch?
---------- Post added at 07:53 PM ---------- Previous post was at 07:52 PM ----------
MishaalRahman said:
Have you tried booting Magisk on it yet?
Click to expand...
Click to collapse
What do you mean by booting Magisk?
MicroMod777 said:
The Verizon version will be locked.
Click to expand...
Click to collapse
Most likely.
MishaalRahman said:
Have you tried booting Magisk on it yet?
Click to expand...
Click to collapse
What do you mean by booting Magisk? @MishaalRahman
Followed the same steps as OP. Unlocked my 4XL the same way I unlocked my 3XL
northmendo said:
What do you mean by booting Magisk? @MishaalRahman
Click to expand...
Click to collapse
I think he means patching the boot image with magisk
northmendo said:
What do you mean by booting Magisk? @MishaalRahman
Click to expand...
Click to collapse
ZeroKool76 said:
I think he means patching the boot image with magisk
Click to expand...
Click to collapse
And then fastbooting the image that magisk patched :good:
For those asking, no I haven't tried to root it yet. I just wanted to start playing with the device and signing in to all my stuff. No point in doing that first without unlocking the bootloader cause just like with any other phone that will factory reset everything. Better to unlock the device first before you start customizing it to you liking. Most likely root can be achieved without wiping again.
What command are you using? I tried fastboot flashing unlock and it just shows the help menu and fastboot oem unlock gives an error. On win 10 here. That link is incomplete?
ETA: I ended up using a tool and setting it to pixel/ pixel xl and it worked but its all for not, I think I'm returning the phone. I just am not happy with the way the face unlock works with ambient display, it ends up unlocking the phone when I just want to check my notifications lol. C'est la vie!
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
vlc_marcos said:
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
Click to expand...
Click to collapse
No duplicated thread are permitted
Please help us to keep the forums neat
Thanks
vlc_marcos said:
I downloaded the wrong Firmware for the Pixel 5
Click to expand...
Click to collapse
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
l7777 said:
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
Click to expand...
Click to collapse
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
vlc_marcos said:
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
Click to expand...
Click to collapse
when its plugged into a computer does the computer see it at all?
thewraith420 said:
when its plugged into a computer does the computer see it at all?
Click to expand...
Click to collapse
not at all is there some kind of hard unbrick??
vlc_marcos said:
not at all is there some kind of hard unbrick??
Click to expand...
Click to collapse
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
thewraith420 said:
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
Click to expand...
Click to collapse
Mine bricked about a month ago and Google suggested uBreakiFix. They tried to do a force flash on it but it didn't work. They ended up replacing the motherboard which fixed it, but now my proximity sensor is always on. I don't know if they can fix that or if it will require another motherboard.
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
p_a_r_s_a7 said:
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
Click to expand...
Click to collapse
Did you use any special way to even turn on the phone or reach the bootloader?
vlc_marcos said:
Did you use any special way to even turn on the phone or reach the bootloader?
Click to expand...
Click to collapse
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
p_a_r_s_a7 said:
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
Click to expand...
Click to collapse
how did you end up with it like that with bootloader locked? what caused it?
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
But you could reach fastboot right?
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
speo said:
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
Click to expand...
Click to collapse
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
speo said:
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
Click to expand...
Click to collapse
I send back to Google, i couldn't fix it
Cj719 said:
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
Click to expand...
Click to collapse
thank you anyway, it was a little light on the horizon at least ;-)
p_a_r_s_a7 said:
I send back to Google, i couldn't fix it
Click to expand...
Click to collapse
have you been charged ?
Mine is from another dealer, will see..
Laptop is in for repairs so all I have is my old rooted 8T. Is it possible to unlock the bootloader and root my new phone with the 8t? If so how?
Yes using Termux + ADB/Fastboot for Android on the device you are using in place of a pc/laptop. Not worth the trouble if you have other options..
Andrologic said:
Yes using Termux + ADB/Fastboot for Android on the device you are using in place of a pc/laptop. Not worth the trouble if you have other options..
Click to expand...
Click to collapse
No other options. Too impatient to wait the couple weeks for my laptop to be fixed. Thanks though! I'll look into it.
If anyone cares, I did it. Unlocked the bootloader and got root no problem. No PC in sight. 5 minute job including downloads.
shadowofdeth said:
If anyone cares, I did it. Unlocked the bootloader and got root no problem. No PC in sight. 5 minute job including downloads.
Click to expand...
Click to collapse
Great!
And it would help others who are interested in this if you described how you did it.
Downloaded Msgisk ADB and fastboot
BillGoss said:
Great!
And it would help others who are interested in this if you described how you did it.
Click to expand...
Click to collapse
Exactly the same steps as if it was done on a computer only needing to download the adb fastboot Msgisk module like suggested earlier. That's it. That's all I did.
Was also able to fully wipe my old phone and relock the bootloader without issue too.