Related
Hey everyone,
My problem is that is have no network signal.
I'm from Europe/Austria.
First what i have done:
I got a couble days ago my new nexus 5x and everything worked fine, since i have pt in the dialer *#*#4636#*#* --> Phone information --> clicked on the menu button on right top corner --> Select frequenz range --> USA Band
After that i have no networ signal anymore.
I've tried hard and soft factory reset but it did not work.
Thanks for answers.
I know it's my mistake, but its very frustrating.
Sorry if my english is not very good, I am german.
Try to reflash the stock ROM. I m not sure whether it will work or not.
BTW what's ur phone model?
tra_dax
tra_dax said:
Try to reflash the stock ROM. I m not sure whether it will work or not.
BTW what's ur phone model?
tra_dax
Click to expand...
Click to collapse
Model: H791 (32GB)
Must I unlock the bootloader to flash the stock rom?
this may help you https://developers.google.com/android/nexus/images?hl=en
I have now flashed the factory image, using this
instructions: androidforums com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533
It have not worked, still no signal.
androidlover5842 said:
this may help you [...]
Click to expand...
Click to collapse
I also would try the original instructions from Google, but how do I excecute the flash-all script? And wich one must I use the flash-all.sh or flash-all.bat ?
xRenex said:
I have now flashed the factory image, using this
instructions: androidforums com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533
It have not worked, still no signal.
I also would try the original instructions from Google, but how do I excecute the flash-all script? And wich one must I use the flash-all.sh or flash-all.bat ?
Click to expand...
Click to collapse
flash-all.bat and flash-all.sh is for linux users
androidlover5842 said:
flash-all.bat and flash-all.sh is for linux users
Click to expand...
Click to collapse
Ok thanks and how look the command I must type in? Then I give it a second chance.
xRenex said:
Ok thanks and how look the command I must type in? Then I give it a second chance.
Click to expand...
Click to collapse
i don't know i am linux user for my childhood i don't know how to use windows you may need to right click on file.bat and run as administrator
Now I have flashed the factory image using flash-all.bat. It also have not worked.
this thread may help.
http://forum.xda-developers.com/showthread.php?t=3238867
I'm going to be exchanging my pixel and getting another one. Just curious so I know for the future.. if I flash the full factory image via fastboot does that relock the bootloader? I'm gonna guess that it doesn't but just wanna make sure.
New to adb and fastboot so I've been reading around like crazy trying to learn. Is the only way to lock again to use the actual lock command in fastboot?
Edit: I'm referring to using the flash-all.bat script
Yes, you will have to re-lock the bootloader. Do it with fastboot in the bootloader.
Although, you don't have to re-lock the bootloader before sending your phone back... Especially since it will have the stock image flashed to it.
aholeinthewor1d said:
if I flash the full factory image via fastboot does that relock the bootloader?
Click to expand...
Click to collapse
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
cam30era said:
No. Flashing the factory image does not relock the bootloader. After you have successfully rebooted, return to the bootloader and use the command: fastboot oem lock
Click to expand...
Click to collapse
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
canemaxx said:
Sorry, I know this has been asked but I've been searching for days and can't find it. Trying to flash latest factory image for 7.1.1 on pixel xl without losing data and can not find a guide to do so. Any help is appreciated
Click to expand...
Click to collapse
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
cam30era said:
Right click the flash-all script, and choose edit (or something like that) from the drop down menu. In the last line where it says "fastboot -w update..." delete the "-w". Then just use this flash-all.
Click to expand...
Click to collapse
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
canemaxx said:
I'm sorry I was looking for the full guide on flashing the factory image with -w removed. But you did answer how to remove the -w so thank you ...is there a link to a guide with the correct commands to use?
Click to expand...
Click to collapse
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
cam30era said:
This is about the best right now > http://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187
Click to expand...
Click to collapse
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
canemaxx said:
Thank you!! Just to confirm there is only 1 factory image for 7.1.1 in the downloads at the google website, which will work with Verizon correct?
Click to expand...
Click to collapse
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
cam30era said:
Correct. Let me ask you, do you have any modifications to your Pixel? Root, TWRP, custom kernel? If not, you'd be better off with ADB sideload.
Click to expand...
Click to collapse
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
canemaxx said:
I have root and that's it. So if I'm understanding correctly, I would put the factory image zip in the platform tools folder and extract it there, open a command window from that folder and run this command fastboot flash-all
Is that correct?
Click to expand...
Click to collapse
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
cam30era said:
You're on Windows?
Command > fastboot flash-all.bat
Make sure you remove the "-w" first
Click to expand...
Click to collapse
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
In fact, on Windows I think you can just double click the flash-all.bat file (I'm on Linux, so I'm not 100% positive). Yes to your other questions. As long as nothing goes wrong.
canemaxx said:
Yes I am on Windows. So as long as I do as I stated I will retain data and 7.1.1 will be installed. After boot I can reroot with sr4?
Click to expand...
Click to collapse
Been here for about 4 minutes, is that normal?
canemaxx said:
Been here for about 4 minutes, is that normal?
Click to expand...
Click to collapse
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
cam30era said:
Nope. Your fastboot may be out of date. I'd suggest updating your Android SDK.
Click to expand...
Click to collapse
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
canemaxx said:
I updated sdk this morning...not sure why it hung there but everything went through and pixel is now booting. Finishing android update is in progress and seems data was retained. Thank you very much for all your help! Just in time too, Dr just decided to induce my wife's labor and my son will be here today!!
Click to expand...
Click to collapse
Very good.
You sure like living on the edge...
cam30era said:
Very good.
You sure like living on the edge...
Click to expand...
Click to collapse
Haha thanks again for all your help!! 7.1.1 installed and root is back!! This may be the last time I get to update my phone for a while lol
Was rooted on the January version but after uninstalling Magisk and trying to flash the Feb factory image I get theses errors. Platform tools are updated.
Solved: Always unlock_critical when unlocking your bootloader! Some say it's optional but it can/will lead to problems!
rank78 said:
Was rooted on the January version but after uninstalling Magisk and trying to flash the Feb factory image I get theses errors. Platform tools are updated.
Click to expand...
Click to collapse
Did you extract the factory image? And then place all those files in the platform-tools folder?
Badger50 said:
Did you extract the factory image? And then place all those files in the platform-tools folder?
Click to expand...
Click to collapse
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
rank78 said:
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
Click to expand...
Click to collapse
That's odd for sure! Looks just like my files when I updated to the February build. I'm assuming you get the proper response when you type in fastboot devices as well?? Maybe try fastbooting the January image again, and then try the February one. Almost sounds like something got corrupted when you tried to unroot. Are you clean or dirty flashing the update? ?
rank78 said:
Yep, this is what I had after extracting.
The bootloader is tmz12bb so no idea why the cmd is saying I'm trying to flash tmz12b.
Click to expand...
Click to collapse
Shouldn't all those files be in the platform tools folder?
You didn't unlock critical. So it can't flash the bootloader. You need to do that, and it's going to wipe your phone again.
rickysidhu_ said:
Shouldn't all those files be in the platform tools folder?
Click to expand...
Click to collapse
I agree as well. Isn't those files suppose to be in the root folder of platforms tools folder
Put those files in that folder and do the commands again. Should work
Badger50 said:
That's odd for sure! Looks just like my files when I updated to the February build. I'm assuming you get the proper response when you type in fastboot devices as well?? Maybe try fastbooting the January image again, and then try the February one. Almost sounds like something got corrupted when you tried to unroot. Are you clean or dirty flashing the update? ?
Click to expand...
Click to collapse
Dirty. I'll try doing that in the morning.
rickysidhu_ said:
Shouldn't all those files be in the platform tools folder?
Click to expand...
Click to collapse
Yes but kept them in a folder so you guys can see.
TonikJDK said:
You didn't unlock critical. So it can't flash the bootloader. You need to do that, and it's going to wipe your phone again.
Click to expand...
Click to collapse
Are you sure? Can't I skip flashing the bootloader? I looked in the next zip but no recovery.img but I have the other 5 necessary imgs. If I'm keeping TWRP can't I skip recovery anyway?
Nevermind, wrong thread. Sorry
rank78 said:
Dirty. I'll try doing that in the morning.
It won't matter, if you haven't done the command...fastboot flashing unlock_critical
Your not going to be upgrading everything with the factory image unless you try to flash them individually. Which probably still won't work without the updated bootloader.
Yes but kept them in a folder so you guys can see.
Yep, they'll need to go in the platform-tools folder.
Are you sure? Can't I skip flashing the bootloader? I looked in the next zip but no recovery.img but I have the other 5 necessary imgs. If I'm keeping TWRP can't I skip recovery anyway?
Click to expand...
Click to collapse
There is no recovery.img anymore on the P2XL. The recovery now resides in the boot.img. If you want to save yourself some headaches further down the road, unlock the critical, wipe the phone, and start over. Then updating every month will be a piece of cake :good:
Badger50 said:
There is no recovery.img anymore on the P2XL. The recovery now resides in the boot.img. If you want to save yourself some headaches further down the road, unlock the critical, wipe the phone, and start over. Then updating every month will be a piece of cake :good:
Click to expand...
Click to collapse
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
CyberpodS2 said:
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
Click to expand...
Click to collapse
Amen to that bro! ????
CyberpodS2 said:
Lol dude sometimes I wish we could mass edit this entire device threads and remove every post that advocates against unlock critical and add "must unlock critical" to every thread. :good:
But to the OP, yes unlock critical and bite the bullet once then forget about it.
Click to expand...
Click to collapse
This. When I first unlocked my bootloader I didn't see to unlock critical, and when I saw afterward it was said to be unnecessary. I'll start from scratch and report back. Sigh.
Flashed critical and was in a bootloop with TWRP but managed to adb flash-all. Still showed missing files but it kept going and now all up to date. Thanks guys!
Side note: Since Google backs up and restores practically everything, do you guys bother with TiB anymore? I haven't in years and just did a backup before all this but doesn't seem like it offers much more.
rank78 said:
Flashed critical and was in a bootloop with TWRP but managed to adb flash-all. Still showed missing files but it kept going and now all up to date. Thanks guys!
Side note: Since Google backs up and restores practically everything, do you guys bother with TiB anymore? I haven't in years and just did a backup before all this but doesn't seem like it offers much more.
Click to expand...
Click to collapse
I still use TiBu to restore the data on all my user apps. Google just doesn't quite do all of that just yet
Hi
How do I know if I'm critical or not bootloader unlocked?
Thanks
dd66 said:
Hi
How do I know if I'm critical or not bootloader unlocked?
Thanks
Click to expand...
Click to collapse
Did you run the command yourself, or purchase it from someone else with it already unlocked???
Badger50 said:
Did you run the command yourself, or purchase it from someone else with it already unlocked???
Click to expand...
Click to collapse
Solved. (ran fastboot oem-info)
Thanks anyway
I unlocked the bootloader of my Zuk Z2 in AUG 2017 and I was enjoying the world of custom roms on it and a treble build just ruined everything and I soft bricked the device and I took it to the nearest Lenovo service center and they managaed to fix it after 4 days and now I tried to unlock the boot loader and it fails again and again...and again I tried every thing even ALL IN ONE TOOL.Is there any solution for this?Please reply ASAP
Thank you in Adv
They may have changed something which changed the serial no. I think. So the image file isn't matching up.
Install stock ROM and check the serial number. Then request for new unlocking bootloader image file as per that serial no.
Just a guess. Not sure about it.
NaXal said:
They may have changed something which changed the serial no. I think. So the image file isn't matching up.
Install stock ROM and check the serial number. Then request for new unlocking bootloader image file as per that serial no.
Just a guess. Not sure about it.
Click to expand...
Click to collapse
I tried it sir but no luck :crying:
Which method unlocking are you following?
NaXal said:
Which method unlocking are you following?
Click to expand...
Click to collapse
Flashing the unlock_bootloader.img and I even tried the all in one tool sir
@sreek995 said:
Flashing the unlock_bootloader.img and I even tried the all in one tool sir
Click to expand...
Click to collapse
The CMD command must be giving some output message. Can you copy that here. As what is the message it is generating ?
NaXal said:
The CMD command must be giving some output message. Can you copy that here. As what is the message it is generating ?
Click to expand...
Click to collapse
sure sir please wait a second
@sreek995 said:
sure sir please wait a second
Click to expand...
Click to collapse
This was not my pc but same error
https://drive.google.com/file/d/0B9n...w?usp=drivesdk
@sreek995 said:
This was not my pc but same error
https://drive.google.com/file/d/0B9n...w?usp=drivesdk
Click to expand...
Click to collapse
Your link isn't working.
Code:
Sorry, the file you have requested does not exist.
Try to run the bootloader image flashing command of that adb cmd (remember to run adb under admin mode of windows) and post that error message or what ever output it is generating after that command is run.
Thanks.
NaXal said:
Your link isn't working.
Code:
Sorry, the file you have requested does not exist.
Try to run the bootloader image flashing command of that adb cmd (remember to run adb under admin mode of windows) and post that error message or what ever output it is generating after that command is run.
Thanks.
Click to expand...
Click to collapse
sorry sir my fault Im on it now:laugh:
Sorry again im late
@sreek995 said:
sorry sir my fault I on it now:laugh:
Click to expand...
Click to collapse
https://twitter.com/sreek995/status/994642330719170560
https://twitter.com/sreek995/status/994642330719170560?s=19
I think you should revert back to 1.9 Stock ROM via QPST. Try with that ROM. not sure, but Service center guys may have got a corrupt ROM or something.
Flash the 1.9 stock ROM via QPST try unlocking with that.
NaXal said:
I think you should revert back to 1.9 Stock ROM via QPST. Try with that ROM. not sure, but Service center guys may have got a corrupt ROM or something.
Flash the 1.9 stock ROM via QPST try unlocking with that.
Click to expand...
Click to collapse
Yeah may be I'll try and inform you later sir
Hi XDA Community,
I soft-bricked my phone, it gets stuck on fastboot even after flashing my backup. The only thing I didn't backup is my userdata partition. Does anyone have the T-mobile firmware so I can unbrick?
Thanks
MSM doesn't exist for T-Mobile yet. Did you try fastboot -w to erase all userdata?
Yes, nothing so far. However someone out there can probably dump their tmb firmware and I can use fastboot flash.
I fixed it!
Looks like the vm-bootsys file was responsible, so flashed that and good to go!
Nvm, now stuck on wiping
EDIT: It's doing the same thing again
Unfortunately, TMO MSM doesn't exist currently, and full OTAs are not available, so there is no good way to extract /system, /system_ext, /vendor, /product, and /odm from super. It sounds like you backed up everything though, so what happens if you just flash everything back?
Hey I might be able to help you dude? I pulled my tmo firmware as back up. I mean I pulled every partition and made a flashall.bat if I knew how to put it on a site or share with my drive it's 20gb.
craznazn said:
Unfortunately, TMO MSM doesn't exist currently, and full OTAs are not available, so there is no good way to extract /system, /system_ext, /vendor, /product, and /odm from super. It sounds like you backed up everything though, so what happens if you just flash everything back?
Click to expand...
Click to collapse
I extracted all that even vbmeta_vendor all partitions. If you can tell me how to send it to you I will let u look over everything and I can see if it will help ppl. I used it to get my 9 pro unbricked. I got the convert to us OnePlus os in. I just can't update yet.
Yes I would very much appreciate it. @craznazn I will convert to EU as a last resort, that's what I was actually attempting in the first place! Thanks!
You can zip it using something like 7-zip and put it on anonfile, they have 20GB limit but compression makes the folder size smaller. Thanks a ton!
Or you could use gofile, unlimited storage space.
amaroney55 said:
Hey I might be able to help you dude? I pulled my tmo firmware as back up. I mean I pulled every partition and made a flashall.bat if I knew how to put it on a site or share with my drive it's 20gb.
Click to expand...
Click to collapse
Did you get this backed up online yet by chance?
I want to flash Global myself but waiting till there is at least something to attempt to flash to fix if it breaks.
I flashed EU, am A-OK apart from maybe downgrade to L3, still working that out.
Also, you can back it up yourself using Partitions backup and restore on the Play Store. Just make sure you are rooted, otherwise it won't work.
razercortex said:
Also, you can back it up yourself using Partitions backup and restore on the Play Store. Just make sure you are rooted, otherwise it won't work.
Click to expand...
Click to collapse
What partitions did you backup using that app and were you able to successfully restore using that app as well? Does the BL remain unlocked after restore?
TheKnux said:
What partitions did you backup using that app and were you able to successfully restore using that app as well? Does the BL remain unlocked after restore?
Click to expand...
Click to collapse
He's running an experimental MSM conversion I built, it's not public yet. It does not touch the BL unlock. The process is not stable and it's not ready for public use.
That, and it's no longer the TMO ROM, and there is no good way back w/o an official LE2127 MSM
I am gonna try to write a guide my first one if I am not breaking any rules. Anyone can tweak or down it? But like I say messing with android is trail and error. I am gonna put the. Rom I pulled and used to unbrick while y'all are waiting on the msm. To me. This is just an easy fast fix so look out for it on the guides.
I backed up everything except for userdata. Make sure you manually dd the super partition to a super.img, otherwise it stays a tar. That's the mistake I made. I'm sure I can convert it but prob not worth the hassle.