I have a question. I went to oneclickroot.com to get the Pixel rooted.
Is it normal when i reboot or shut down the phone, that the phone keeps saying that the phone bootloader is unlocked then it says press power button to continue, is it normal for that to keep popping up, when u restart and power on the phone.
Dasin said:
I have a question. I went to oneclickroot.com to get the Pixel rooted.
Is it normal when i reboot or shut down the phone, that the phone keeps saying that the phone bootloader is unlocked then it says press power button to continue, is it normal for that to keep popping up, when u restart and power on the phone.
Click to expand...
Click to collapse
Did it actually root the phone? You may have corrupted your device with that root method. If it even worked
Badger50 said:
Did it actually root the phone? You may have corrupted your device with that root method. If it even worked
Click to expand...
Click to collapse
So your saying that it is not suppose to do that. agghhh i used the site oneclickroot.com and i had to pay them 99.99 dollars to root the phone, because the instructions is detailed enough there is always a small part that is missing. Is there a way i can wipe the phone and make it brand new so i can start from scratch because clearly as u stated they messed up my device with there corny root process.
Dasin said:
So your saying that it is not suppose to do that. agghhh i used the site oneclickroot.com and i had to pay them 99.99 dollars to root the phone, because the instructions is detailed enough there is always a small part that is missing. Is there a way i can wipe the phone and make it brand new so i can start from scratch because clearly as u stated they messed up my device with there corny root process.
Click to expand...
Click to collapse
Yeah, your phone shouldn't do that. Does it actually boot up to the OS outa curiosity? If your bootloader is unlocked, and you have OEM unlocking and USB debugging enabled, then you can fastboot the factory image and wipe your device to start over. There are great guides in these forums for that purpose :good:
Unlocking the bootloader will induce a warning every time the phone is rebooted. That would be normal. Without seeing exactly what the warning says, it's hard to say if what you are seeing is the same message or is normal.
That said, I would probably reflash the factory images and use a different root method. It's not terribly hard to do on your own so I would avoid any one click type solutions because it's just asking for trouble.
this is the normal bootloader unlocked screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes that screen is normal in a phone that had the bootloader unlocked on every boot
Badger50 said:
Yeah, your phone shouldn't do that. Does it actually boot up to the OS outa curiosity? If your bootloader is unlocked, and you have OEM unlocking and USB debugging enabled, then you can fastboot the factory image and wipe your device to start over. There are great guides in these forums for that purpose :good:
Click to expand...
Click to collapse
Yeah it goes into the OS.
fury683 said:
Unlocking the bootloader will induce a warning every time the phone is rebooted. That would be normal. Without seeing exactly what the warning says, it's hard to say if what you are seeing is the same message or is normal.
That said, I would probably reflash the factory images and use a different root method. It's not terribly hard to do on your own so I would avoid any one click type solutions because it's just asking for trouble.
Click to expand...
Click to collapse
When i reboot the phone it says this (Press power button to resume)
Right below that with a yellow triangle, it says.
The bootloader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers, Do not store any sensitive data on the device.
Visit this link on another device
then it shows an ID
Dasin said:
Yeah it goes into the OS.
When i reboot the phone it says this (Press power button to resume)
Right below that with a yellow triangle, it says.
The bootloader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers, Do not store any sensitive data on the device.
Visit this link on another device
then it shows an ID
Click to expand...
Click to collapse
The bootloader message is normal, you just shouldn't have to press to continue every time. Since your in the OS, have you checked if it's rooted?
Badger50 said:
The bootloader message is normal, you just shouldn't have to press to continue every time. Since your in the OS, have you checked if it's rooted?
Click to expand...
Click to collapse
No, i dont have to go to continue, when i boot up my phone that message pops up and it automatically boots into my OS unless i tap the power button, as it says in the message. I just wanted to know if thats normal because im getting conflicting information, like does it mean that the jailbreak method done was the wrong one or its not a proper root.
Also how do i check to see if it is rooted?
Dasin said:
No, i dont have to go to continue, when i boot up my phone that message pops up and it automatically boots into my OS unless i tap the power button, as it says in the message. I just wanted to know if thats normal because im getting conflicting information, like does it mean that the jailbreak method done was the wrong one or its not a proper root.
Also how do i check to see if it is rooted?
Click to expand...
Click to collapse
That message is normal for all of us with bootloader unlocked pixel devices. You can check root status with an app like this one :good:
https://play.google.com/store/apps/details?id=technarcs.rootchecker
And my question is you paid $100.00 to root when devs have root included with a rom? That's probably the more important issue lol
dipstik said:
this is the normal bootloader unlocked screen:
View attachment 4667879
Click to expand...
Click to collapse
Right ok thats what i see on my screen then higher up on the screen it says press power to pause, thats it, ok so if that normal that i think im good then if im not mistaken.
Ill make another forum on questions about root, and what can i do with it to make my phone better, as everyone says.
biggiesmalls657 said:
And my question is you paid $100.00 to root when devs have root included with a rom? That's probably the more important issue lol
Click to expand...
Click to collapse
I did not know, people put up tutorials and they seem detailed but small things are missing from it that you guys expect some people to know but they dont, im coming from iPhone so certain things, i dont get. i just got tired of trying and went to onclickroot.com
Dasin said:
I did not know, people put up tutorials and they seem detailed but small things are missing from it that you guys expect some people to know but they dont, im coming from iPhone so certain things, i dont get. i just got tired of trying and went to onclickroot.com
Click to expand...
Click to collapse
It's understandable but 100.00 dollars to me for something software related seems to good to be true unless it's a big name like Microsoft. Lol at least you know for next time
Badger50 said:
That message is normal for all of us with bootloader unlocked pixel devices. You can check root status with an app like this one :good:
https://play.google.com/store/apps/details?id=technarcs.rootchecker
Click to expand...
Click to collapse
Yeah i checked it, im rooted, so i guess everything is fine, thanks for the help with that i was beginning to worry.
biggiesmalls657 said:
It's understandable but 100.00 dollars to me for something software related seems to good to be true unless it's a big name like Microsoft. Lol at least you know for next time
Click to expand...
Click to collapse
I just wanted to root it and get it over with. Now i have to figure if there are root apps like IOS like backgrounder that leaves apps open in the background, or a rooted app that can tell me what tower im on and the band etc... I already posted a thread about my questions, i dont want to misguide this thread, thanks to you all.
Dasin said:
Yeah i checked it, im rooted, so i guess everything is fine, thanks for the help with that i was beginning to worry.
I just wanted to root it and get it over with. Now i have to figure if there are root apps like IOS like backgrounder that leaves apps open in the background, or a rooted app that can tell me what tower im on and the band etc... I already posted a thread about my questions, i dont want to misguide this thread, thanks to you all.
Click to expand...
Click to collapse
No worries man, you are gonna have fun! Pixels are way more fun than iPhone. Androids allow you to modify deep in the hardware, CPU speed, governor's, and kernels. Apple won't let you touch that stuff because it is closed source code. Google is obviously open source. Just don't Kang lol. I helped these forums for years until I made the mistake of buying a Verizon pixel 2 which was factory locked by Verizon. Greenify is a good root app. Macrodroid is another. If you do decide to modify, know that there are risks with all of these tweaks. You could potientally set your CPU or GPU on fire or your wife will tell at you! Lol Lots of experienced people including myself are here to help you at any point.
---------- Post added at 09:31 PM ---------- Previous post was at 09:31 PM ----------
Great app for cell towers is LTE Discovery as well
Dasin said:
Yeah i checked it, im rooted, so i guess everything is fine, thanks for the help with that i was beginning to worry.
I just wanted to root it and get it over with. Now i have to figure if there are root apps like IOS like backgrounder that leaves apps open in the background, or a rooted app that can tell me what tower im on and the band etc... I already posted a thread about my questions, i dont want to misguide this thread, thanks to you all.
Click to expand...
Click to collapse
Cool beans bruh. Now don't forget to hit that TANKS button to all those that help you on your way! :good
Dasin said:
I did not know, people put up tutorials and they seem detailed but small things are missing from it that you guys expect some people to know but they dont, im coming from iPhone so certain things, i dont get. i just got tired of trying and went to onclickroot.com
Click to expand...
Click to collapse
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + December 2018 Security Patch
Welcome to the family @Dasin. If you're willing to learn you'll have a lot more fun with andriod phone than you ever will work an iPhone. There's lots of good guides and better yet, lots of good people to help you. You've already met some of the best in this forum. Good luck and have fun.
Sent from my [device_name] using XDA-Developers Legacy app
Related
I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?
AstroDigital said:
I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?
Click to expand...
Click to collapse
Not even ordering until I am sure that is all in place.
Can anyone buy the pixel for me and send it to me in Zimbabwe, I cannot order it for now.
I'm waiting for a method of gaining root access to be achieved before placing my order. The phone I have now (Nexus 6) still works fine so I'm in no rush. Also, I am kind of interested in seeing what kind of reviews the XL gets anyways. Mainly regarding the volume of the speaker.
cmzizi said:
Can anyone buy the pixel for me and send it to me in Zimbabwe, I cannot order it for now.
Click to expand...
Click to collapse
How do you plan on paying for it? I can bring it with me on my trip to Zimbabwe 10/17/16.
I can do payment via PayPal.
Sent from my SM-N930F using Tapatalk
You will almost certainly have root access on this device. The bootloader looks to be unlockable unless you get the Verizon branded version.
Remember, root doesn't mean supersu, or even the su binary. Root means the ability to run commands in the superuser context. You will have that at the very least. From there a new solution to give root access to normal android applications may need to be developed, but that is only a matter of time. As long as your bootloader is unlockable, you can build whatever you need into the kernel as a module, or run a service from init (like daemonsu).
grneyez said:
How do you plan on paying for it? I can bring it with me on my trip to Zimbabwe 10/17/16.
Click to expand...
Click to collapse
The phone doesnt come out until after this date. This is impossible
cmzizi said:
Can anyone buy the pixel for me and send it to me in Zimbabwe, I cannot order it for now.
Click to expand...
Click to collapse
cmzizi said:
I can do payment via PayPal.
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
I'll PM you.
---------- Post added at 03:54 PM ---------- Previous post was at 03:49 PM ----------
KnownDominance said:
The phone doesnt come out until after this date. This is impossible
Click to expand...
Click to collapse
For you yes that is correct, for me I get it sooner. Thanks
tigercranestyle said:
in the past only unlocking the bootloader erased data... not the actual rooting. why not just unlock the bootloader before setting it up, continue to use the device as you please, and then just wait until a root method is released?
Click to expand...
Click to collapse
That is what I normally do...... unlock the bootloader right out of the box (it wipes the phone then before you set it up) then you have the option to root later on if you like.
ill keep my s7. the phone looks smooth And fluid but i hate the design. its also way overpriced.
How could you wait? Buy it. If for some wild reason we couldn't get root. I'm sure it would still be returnable. If you wait, the phone will already have root and a custom ROM before one ever shows up on your doorstep.lol
Sent from my Nexus 6P using XDA-Developers mobile app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
charlieb620 said:
Click to expand...
Click to collapse
I don't do that.... I usually buy Verizon and purposely get at least 3 phones and return them as defective when I dont have root to my own device. Just as a little F-U to them. Then I finally hack my own phone and go with it. But I'll return as many as I can as defective first until they wise up and stop sending them to me.
You simply should not have to pay extra when hardware and software shouldn't be tied together in the first place. Why would I pay extra for an unlocked device that is exactly the same hardware as the locked one.
That is definitely the most immature thing I've heard all week.
You don't like their policies so you are 'showing them'? Give me a break. My 11 year old grew out of that behavior 5 years ago...
Sent from my Nexus 6P using Tapatalk
AstroDigital said:
I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?
Click to expand...
Click to collapse
Dude its not hard to completely re set your phone quit being lazy I do it like 30 + times in 2 months, and install many themes apps widgets and configurations. I also use Nova launcher back up where you just have to install widget apps etc. But re setting a phone is nothing and do not expect root on this phone. Just google search root pixel phones. Many sources say its going to be impossible. Hope you didnt get it for root purposes. lol
AstroDigital said:
I have in the past setup my new devices, spent hours then somebody finally roots the device.
This usually means wiping the device, unlocking the bootloader, rooting and reinstalling everything again.
It is much easier if the first thing I do is unlock the bootloader and then root.
I then set up my device, and back up everything using Titanium Backup.
What do you do keep using the old device for a few weeks and wait for news and a procedure to unlock the bootloader and root ?
Click to expand...
Click to collapse
I even already wait 3rd year cause I skip ugliest nexus 6p and now pixel xl which has no unlocked bootloader and no root, and on top of that it has NOT wireless charging AGAIN !!!
I'm incredibly disappointed because Pixel XL seems good even it has HUGE, gigantic bezels on top and bottom.
For now Nexus 6 is the best and hope not the last google phone.
BaconSeeds said:
Dude its not hard to completely re set your phone quit being lazy I do it like 30 + times in 2 months, and install many themes apps widgets and configurations. I also use Nova launcher back up where you just have to install widget apps etc. But re setting a phone is nothing and do not expect root on this phone. Just google search root pixel phones. Many sources say its going to be impossible. Hope you didnt get it for root purposes. lol
Click to expand...
Click to collapse
Not one source says impossible...stop spreading false propaganda, phones will be rooted within days
I can assure you this thing will be rooted, I will see to it myself
DespairFactor said:
I can assure you this thing will be rooted, I will see to it myself
Click to expand...
Click to collapse
I hope so I want it to be rooted just the articles I've read made it seem doubtful. Especially b/c I pre ordered one.
$20 to the dev who gets AOSP to work on Sprint's latest 1.80.651.30, WITHOUT using foreign firmware.
We're about a year into this device, and apparently we have no developers on the Sprint side working on this.
Not sure if that price is worth it to anyone, but I'm a man of my word.
mcwups1 said:
$20 to the dev who gets AOSP to work on Sprint's latest 1.80.651.30, WITHOUT using foreign firmware.
We're about a year into this device, and apparently we have no developers on the Sprint side working on this.
Not sure if that price is worth it to anyone, but I'm a man of my word.
Click to expand...
Click to collapse
You contacted me multiple times about editing the Verizon guide for Sprint.. I took my free time to respond.. and now you post this.. A bit of a slap in the face, no? :silly:
I would contact the Devs working on AOSP personally, however with N already here (and coming soon to the rest of the carriers), I personally don't see anyone taking their time on MM (just an opinion).
I do hope you get it working. :good:
andybones said:
You contacted me multiple times about editing the Verizon guide for Sprint.. I took my free time to respond.. and now you post this.. A bit of a slap in the face, no? :silly:
I would contact the Devs working on AOSP personally, however with N already here (and coming soon to the rest of the carriers), I personally don't see anyone taking their time on MM (just an opinion).
I do hope you get it working. :good:
Click to expand...
Click to collapse
No, you never got back with my question!
I have your zip, but haven't flashed it, because I'm not sure if it needs "modified" for Sprint.
Plus, I am looking for it to work with Sprint firmware first.
mcwups1 said:
No, you never got back with my question!
I have your zip, but haven't flashed it, because I'm not sure if it needs "modified" for Sprint.
Plus, I am looking for it to work with Sprint firmware first.
Click to expand...
Click to collapse
"No, you never got back with my question!"
I responded last night, and I quoted you so you'd get a notification to see it.
http://forum.xda-developers.com/showpost.php?p=70256059&postcount=15
The whole point of this method is to get back to stock Verizon/Sprint.
If you do my method you will be back on 100% Sprint (Since you are flashing the Sprint RUU AFTER the modified firmware) AND AOSP ROMs working. I don't know why, but it works. It's been confirmed on a number of Verizon users AND Sprint.
"Plus, I am looking for it to work with Sprint firmware first"
Then why did you contact me multiple times? I am not going to apologize for taking longer than you'd like to respond.. I wrote the guide for Verizon, so excuse me for not wanting to brick your device with rushed info..
Like I said, I hope you get it working.. I did respond in the thread, and as I said if you need help editing the android.info.txt, let me know. :good:
I didn't get it. Responded to the linked thread /post.
Thank you.
I understood your instructions for the firmware and RUU, but didn't think your zip would work with my Sprint device. Thank you so much for the deeper explanation.
Will report back here....
mcwups1 said:
I didn't get it. Responded to the linked thread /post.
Thank you.
I understood your instructions for the firmware and RUU, but didn't think your zip would work with my Sprint device. Thank you so much for the deeper explanation.
Will report back here....
Click to expand...
Click to collapse
You are very welcome my friend!
AOSP/CM ROMs are a great way to change up the device so I understand the want to use them, hence how this method was found.
andybones said:
You are very welcome my friend!
AOSP/CM ROMs are a great way to change up the device so I understand the want to use them, hence how this method was found.
Click to expand...
Click to collapse
@andybones
Just to make sure (on both threads, sorry), my CID is 11111111.
I don't use the Sprint CID, I change the android text to the Super CID number, right?
Okay.
Everything done and I didn't brick.
New problem.
I only have 3G, even after the RUU.
Something tells me I shouldn't have GSM options?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mcwups1 said:
Okay.
Everything done and I didn't brick.
New problem.
I only have 3G, even after the RUU.
Something tells me I shouldn't have GSM options?
Click to expand...
Click to collapse
In bootloader run these cmds
fastboot erase modemst1
fastboot erase modemst2
Okay. It appears I have LTE, but now I can't make calls.
Edit: Now, since I woke up this morning, I have no data. I can boot up, but I cannot make calls or message anyone.
Says my device is not activated, and I need to call customer service.
Or, you are not authorized to call this account (calling my wife), if you would like more services, contact customer service.
Showing all zeros for a phone number.
000-000-0000
@andybones
Check your Gmail.
mcwups1 said:
@andybones
Check your Gmail.
Click to expand...
Click to collapse
Thank you kindly my friend! Very much appreciated.
andybones said:
Thank you kindly my friend! Very much appreciated.
Click to expand...
Click to collapse
I can flash CM, but I can't use it.
I cannot make calls or message anyone.
If I restore my Sense backup, then I have no data. I have to erase modems again, just to get messaging back and to get my Sprint ID to return and give me my phone number again.
This has been a major headache, and I don't think this will actually work fully on my device.
Curious to know if you know why I had to input a PIN after flashing that modified firmware zip after reboot?
mcwups1 said:
I can flash CM, but I can't use it.
I cannot make calls or message anyone.
If I restore my Sense backup, then I have no data. I have to erase modems again, just to get messaging back and to get my Sprint ID to return and give me my phone number again.
This has been a major headache, and I don't think this will actually work fully on my device.
Curious to know if you know why I had to input a PIN after flashing that modified firmware zip after reboot?
Click to expand...
Click to collapse
Can't say about Sprint usage and AOSP ROMs or sprint anything really so can't comment on that.
After flashing the firmware it wiped my system so it had no ROM to boot to, so I had to hold volume buttons and power to get into bootloader and then ran the VZW RUU.
I have been using multirom personally since this method as well.
I still wish someone would find a way to get AOSP working on Sprint firmware.
After wiping modems, updating PRL and Profile, I have a working phone again on Sense.
I'm not sure what flashing that zip did, but I'm thinking it changes the internal partitions of firmware, and that Sprint either blocks partitions or doesn't have them, and the zip modded them, or added them.
But WTF do I know?
mcwups1 said:
I still wish someone would find a way to get AOSP working on Sprint firmware.
After wiping modems, updating PRL and Profile, I have a working phone again on Sense.
I'm not sure what flashing that zip did, but I'm thinking it changes the internal partitions of firmware, and that Sprint either blocks partitions or doesn't have them, and the zip modded them, or added them.
But WTF do I know?
Click to expand...
Click to collapse
As I. It seems once/if theres a fix for Sprint, it should also hopefully be the same for Verizon.
Your input is as good as the rest of us.
I've gotten CM/Lineage to work on my Sprint HTC 10. I did have to flash an international firmware zip to get it to get past the boot logo but now it's fine. Note though that I did delete the modems, radio, cache and recovery out of the firmware package before I flashed it. This is likely why you have issues with data now if you didn't do so.
That said, data is still iffy at times on AOSP without toggling some settings after rebooting so it might be worth it for some people to wait until that's fixed before proceeding.
ssmercurys said:
I've gotten CM/Lineage to work on my Sprint HTC 10. I did have to flash an international firmware zip to get it to get past the boot logo but now it's fine. Note though that I did delete the modems, radio, cache and recovery out of the firmware package before I flashed it. This is likely why you have issues with data now if you didn't do so.
That said, data is still iffy at times on AOSP without toggling some settings after rebooting so it might be worth it for some people to wait until that's fixed before proceeding.
Click to expand...
Click to collapse
You should do a write up on the Sprint forums for others.
Their are builds that are out now for sprint that doesn't require a custom firmware
trev23sks said:
Their are builds that are out now for sprint that doesn't require a custom firmware
Click to expand...
Click to collapse
How?
I'm not an expert but I'm not new to this either. I just don't have enough technical experience to figure this out. I had the Phone working and everything was amazing!
A few Days ago due to flashing the phone came up with a message 'No service' and i cannot get the phone to connect to my network at all. The phone cannot make emergency calls yet it cannot connect to any of the networks. When i turn off the Airplane mode it just get stuck on it and it never gets off even if you leave it for a day.(Check screenshot attached) When i dial this code *#*#4636#*#* nothing happens. I don't get the information although The code just vanish away from the dialing screen.
So far, Ive checked both covers on the back ensuring the pins connect properly for the aerial and there is no damage to either panel.
Hard reset did nothing to help, it booted straight up with the same limited service message.
I have tried my SIM card in another phone and it works perfectly, so i know its a problem with the phone.
I've had the IMEI number checked and the phone is not blocked.
The SIM card appears to be detected as you can see in the screenshot i attatched.
If the phone had been dropped, gotten wet or experienced any other form of potential damage, then I would assume it was a hardware repair issue. But because nothing has happened to obviously explain the issue I am experiencing, I am unsure.
Any thoughts would be greatly appreciated!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
shysoul64 said:
A few Days ago due to flashing the phone came up with a message 'No service' and i cannot get the phone to connect to my network at all.
Click to expand...
Click to collapse
What exactly did you flash (include file name, any version number, etc.)?
If the "no service" occurred right after flashing something, than that is mostly likely the cause, and the road you should pursue. Not things like checking IMEI, etc.
Tell us exactly what you did, exact sequence of events, etc.
First of all i want to Thank you for replying. Actually one of my friend Flashed it i have no idea what he has done even though he don't get it but he flashed it somehow and made my device in this Position.
redpoint73 said:
What exactly did you flash (include file name, any version number, etc.)?
If the "no service" occurred right after flashing something, than that is mostly likely the cause, and the road you should pursue. Not things like checking IMEI, etc.
Tell us exactly what you did, exact sequence of events, etc.
Click to expand...
Click to collapse
shysoul64 said:
First of all i want to Thank you for replying. Actually one of my friend Flashed it i have no idea what he has done even though he don't get it but he flashed it somehow and made my device in this Position.
Click to expand...
Click to collapse
You need to ask your friend what he flashed. It's extremely important. Ask him what file, with the exact file name, version number, and source (whatever of those he can give you, all of them if possible).
It sounds like he doesn't really know what he is doing? Why did he even flash anything at all? What was he trying to do? He shouldn't be doing anything to your phone, unless he intend on buying you a new one when he messes up (and it looks like he did).
Seeing as the phone is s-off, it's very possible he flashing the wrong file, and damaged the radio. The damage might be permanent (we've seen it happen before).
Also, we need more info about the phone. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
You need to ask your friend what he flashed. It's extremely important. Ask him what file, with the exact file name, version number, and source (whatever of those he can give you, all of them if possible).
It sounds like he doesn't really know what he is doing? Why did he even flash anything at all? What was he trying to do? He shouldn't be doing anything to your phone, unless he intend on buying you a new one when he messes up (and it looks like he did).
Seeing as the phone is s-off, it's very possible he flashing the wrong file, and damaged the radio. The damage might be permanent (we've seen it happen before).
Also, we need more info about the phone. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
He is a complete noob but act like if he is a Pro ( I came to know after he did this to my phone and when i forwarded him the Questions you asked)
Actually my Phone was a bit laggy which made me pissed off and my bad luck was that he was sitting right next to me. He told me to leave my Phone for a day and he would fix it up at the end result is in front of you.
He have no idea what he has flashed i.e. (exact file name, version number, and source). He said i downloaded from a random site by searching it from google. LOL!
I will give you the info whatever you want to know.
How to fastboot getvar all?
I'm kind of new to these Android Flashing so i might sound stupid.
redpoint73 said:
You need to ask your friend what he flashed. It's extremely important. Ask him what file, with the exact file name, version number, and source (whatever of those he can give you, all of them if possible).
It sounds like he doesn't really know what he is doing? Why did he even flash anything at all? What was he trying to do? He shouldn't be doing anything to your phone, unless he intend on buying you a new one when he messes up (and it looks like he did).
Seeing as the phone is s-off, it's very possible he flashing the wrong file, and damaged the radio. The damage might be permanent (we've seen it happen before).
Also, we need more info about the phone. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
shysoul64 said:
He have no idea what he has flashed i.e. (exact file name, version number, and source). He said i downloaded from a random site by searching it from google. LOL!
Click to expand...
Click to collapse
That type of behavior is extremely careless, and my opinion, that person should not be messing with yours or anyone else's phone.
If he had truly "no idea" what he was flashing, then he had no business flashing it! Him having "no idea" what he flashed to me says he had little or no understanding of what he was doing. And best practice is to fully understand what you are installing to the phone, and also keep track of exactly what those files were, steps performed, etc.
The file (or files) that he flashed still aren't on his computer in a folder somewhere, or even in the PC's recycle bin? Another best practice, I always keep files (I've flashed) on my PC for a while "just in case" I need to use them again or reference them.
Really hard to troubleshoot the problem, without knowing what he did. One thing I can suggest, is to flash the RUU, which is a complete factory image, and will hopefully clear up the "no network" problem. See the following post for files and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
redpoint73 said:
That type of behavior is extremely careless, and my opinion, that person should not be messing with yours or anyone else's phone.
If he had truly "no idea" what he was flashing, then he had no business flashing it! Him having "no idea" what he flashed to me says he had little or no understanding of what he was doing. And best practice is to not only fully understand what you are installing to the phone, but also keep track of exactly what those files were, steps performed, etc.
The file (or files) that he flashed still aren't on his computer in a folder somewhere, or even in the PC's recycle bin? Another best practice, I always keep files (I've flashed) on my PC for a while "just in case" I need to use them again or reference them.
Click to expand...
Click to collapse
I'm forwarding all of your Messages to him. He is ignoring them he ain't answering my calls either. I cannot contact him right now. I don't think whether he have the files anymore.
Anyways, apart from that is there any other way to Flash it back to the normal state?
redpoint73 said:
That type of behavior is extremely careless, and my opinion, that person should not be messing with yours or anyone else's phone.
If he had truly "no idea" what he was flashing, then he had no business flashing it! Him having "no idea" what he flashed to me says he had little or no understanding of what he was doing. And best practice is to fully understand what you are installing to the phone, and also keep track of exactly what those files were, steps performed, etc.
The file (or files) that he flashed still aren't on his computer in a folder somewhere, or even in the PC's recycle bin? Another best practice, I always keep files (I've flashed) on my PC for a while "just in case" I need to use them again or reference them.
Really hard to troubleshoot the problem, without knowing what he did. One thing I can suggest, is to flash the RUU, which is a complete factory image, and will hopefully clear up the "no network" problem. See the following post for files and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Should i leave the S-Off or Turn it ON?!
shysoul64 said:
Should i leave the S-Off or Turn it ON?!
Click to expand...
Click to collapse
Have you tried manually entering an APN into your phone?
Sent from my HTC One M9 using Tapatalk
shysoul64 said:
Should i leave the S-Off or Turn it ON?!
Click to expand...
Click to collapse
Leave it S-Off till (if) you get it up and running. Then its entirely up to you.
Looking at the bootloader screen. It appears as though it is a faux bootloader as the status is official.. Cid is 11111111 which is supercid, so be careful.
shysoul64 said:
I'm not an expert but I'm not new to this either. I just don't have enough technical experience to figure this out. I had the Phone working and everything was amazing!
A few Days ago due to flashing the phone came up with a message 'No service' and i cannot get the phone to connect to my network at all. The phone cannot make emergency calls yet it cannot connect to any of the networks. When i turn off the Airplane mode it just get stuck on it and it never gets off even if you leave it for a day.(Check screenshot attached) When i dial this code *#*#4636#*#* nothing happens. I don't get the information although The code just vanish away from the dialing screen.
So far, Ive checked both covers on the back ensuring the pins connect properly for the aerial and there is no damage to either panel.
Hard reset did nothing to help, it booted straight up with the same limited service message.
I have tried my SIM card in another phone and it works perfectly, so i know its a problem with the phone.
I've had the IMEI number checked and the phone is not blocked.
The SIM card appears to be detected as you can see in the screenshot i attatched.
If the phone had been dropped, gotten wet or experienced any other form of potential damage, then I would assume it was a hardware repair issue. But because nothing has happened to obviously explain the issue I am experiencing, I am unsure.
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
cool bro..... jst flash the stock rom for htc one m8
miffymiffy said:
Leave it S-Off till (if) you get it up and running. Then its entirely up to you.
Looking at the bootloader screen. It appears as though it is a faux bootloader as the status is official.. Cid is 11111111 which is supercid, so be careful.
Click to expand...
Click to collapse
I flashed the Stock software but it didn't worked for me. I'm still having the same issue as i mentioned. Any other way?
redpoint73 said:
That type of behavior is extremely careless, and my opinion, that person should not be messing with yours or anyone else's phone.
Really hard to troubleshoot the problem, without knowing what he did. One thing I can suggest, is to flash the RUU, which is a complete factory image, and will hopefully clear up the "no network" problem. See the following post for files and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
I did exactly what you said last night but my Phone is still in the same state. Do you have any other way to suggest?
shysoul64 said:
I did exactly what you said last night but my Phone is still in the same state. Do you have any other way to suggest?
Click to expand...
Click to collapse
Which ruu did you try?
maultasche said:
Which ruu did you try?
Click to expand...
Click to collapse
This RUU https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Suggested by redpoint73
shysoul64 said:
This RUU https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Suggested by redpoint73
Click to expand...
Click to collapse
That's the correct RUU for your phone. But since we don't know what was flashed it's hard to help. Seems like radio is bricked permanently. I'm sorry but I think your issue can't be fixed by just flashing software.
maultasche said:
That's the correct RUU for your phone. But since we don't know what was flashed it's hard to help. Seems like radio is bricked permanently. I'm sorry but I think your issue can't be fixed by just flashing software.
Click to expand...
Click to collapse
Awwww! RIP M8
maultasche said:
That's the correct RUU for your phone. But since we don't know what was flashed it's hard to help. Seems like radio is bricked permanently. I'm sorry but I think your issue can't be fixed by just flashing software.
Click to expand...
Click to collapse
Just another thought by a Noob. LOL!
If flashing can damage M8 radio files then there might be a file that can fix it also. What do you say?
shysoul64 said:
Just another thought by a Noob. LOL!
If flashing can damage M8 radio files then there might be a file that can fix it also. What do you say?
Click to expand...
Click to collapse
If there was such a file maybe. But such a file does not exist (not that I know of) or it's not available for the general public.
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
GunnermanBill said:
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
Click to expand...
Click to collapse
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
v12xke said:
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
Click to expand...
Click to collapse
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
GunnermanBill said:
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
Click to expand...
Click to collapse
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
v12xke said:
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
Click to expand...
Click to collapse
Well that's new as far as google phones go
GunnermanBill said:
Well that's new as far as google phones go
Click to expand...
Click to collapse
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
v12xke said:
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
Click to expand...
Click to collapse
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
GunnermanBill said:
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
Click to expand...
Click to collapse
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
xunholyx said:
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
Click to expand...
Click to collapse
i mean it only happened for the regular pixels in 2016. I'm in no rush, like i said NBD
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
kickenwing13 said:
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
Click to expand...
Click to collapse
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
v12xke said:
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
Click to expand...
Click to collapse
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
kickenwing13 said:
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
Click to expand...
Click to collapse
I would encourage you to just "install" adb/fastboot. It is literally opening a zip file and extracting everything into a new folder. Then adding that folder to your path statement (Windows) means you can use the command from anywhere. For example I created a folder c:\adb and just dumped the files in there. I see you already have opened the flash-all.bat script and are poking around ... so in the beginning you can just cut and paste those commands if you want to do things manually -or- just run the script. You can always get the latest standalone binaries direct from Google. Ditch the toolkits and you will be glad you did. It is just not that hard, and you will know how to get yourself out of a jam later. :good:
I DID IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It was cake. Thanks for the awesome directions. I just opened up through cmd insead of your second step, but dude! clutch . I relocked it.. took 2 seconds once my buddy helped me tpye my first command. But thank you again! Now debating getting more into it. This is the first phone i haven't installed a custom ROM on because the unlock and root stuff absolutely failed...
hi guys please help me i get this error on the screen ". The device will not start." and i can't use my phone, i can't enter the recovery mode (i get the same error) and the device state locked ! please help me
19 views no reply ! Up
Chouiyekh said:
19 views no reply ! Up
Click to expand...
Click to collapse
Tried reflashing stock?
djcrystals said:
Tried reflashing stock?
Click to expand...
Click to collapse
i can't because the bootloader is locked, please help to find a way to revive my mobile (i don't know i there is a box or something else to install the os even the bootloader locked)
the problem happened when i tried to relock the bootloader, unfortunately i don't know the place of purchase because i'm a second hand and i don't know the person who sold me the phone where to live we just met through the internet and we don't have google support in Morocco
Chouiyekh said:
i can't because the bootloader is locked, please help to find a way to revive my mobile (i don't know i there is a box or something else to install the os even the bootloader locked)
the problem happened when i tried to relock the bootloader, unfortunately i don't know the place of purchase because i'm a second hand and i don't know the person who sold me the phone where to live we just met through the internet and we don't have google support in Morocco
Click to expand...
Click to collapse
If you were not on full stock rom without root, or anything custom, and you turned off OEM unlocking and USB debugging, then locked the bootloader, you are basically hosed my friend
Look at this point it just needs to be said... PEOPLE STOP RE-LOCKING THE DARN BOOTLOADER!!
PERIOD!!
There are literally a half dozen posts this week with probably bricked phones and a good amount of them are this same root cause.
CyberpodS2 said:
Look at this point it just needs to be said... PEOPLE STOP RE-LOCKING THE DARN BOOTLOADER!!
PERIOD!!
There are literally a half dozen posts this week with probably bricked phones and a good amount of them are this same root cause.
Click to expand...
Click to collapse
Your preaching to the choir ol friend! While I agree with you 100%, some things are best learned the hard, and expensive way! I've done it twice myself.
The carpenters rule should apply to these phones as well...."measure twice, cut once" :good:
I remember and I'm sure that i left USB debugging enabled, and the bootloader locked, so is there any hope ?
Chouiyekh said:
I remember and I'm sure that i left USB debugging enabled, and the bootloader locked, so is there any hope ?
Click to expand...
Click to collapse
Did you leave OEM unlocking on as well? And, were you on full stock, non rooted rom?
Badger50 said:
Did you leave OEM unlocking on as well? And, were you on full stock, non rooted rom?
Click to expand...
Click to collapse
i left it in this case, OEM unlocking OFF and USB debugging ON, and i was on full stock, rooted rom , the problem happened when i tried to unroot and relock the bootloader
any hopes please please guys, i'm ready to donate for the one who will help i promise
Chouiyekh said:
any hopes please please guys, i'm ready to donate for the one who will help i promise
Click to expand...
Click to collapse
My friend.....you could give me or anybody else 10 thousand bucks, and it's still not going to solve your problem I'm sorry to say. You should have unrooted the phone first, then fastbooted the factory image, or do a factory reset, and made sure that OEM unlocking & USB debugging were left on until you were done locking the bootloader. Sorry man, but there's not much you can do without at least a stock recovery, so....accept the loss, learn from your mistake, and move on. Many of us here, including myself, have been there as well. What you choose to learn from it is up to you
Badger50 said:
My friend.....you could give me or anybody else 10 thousand bucks, and it's still not going to solve your problem I'm sorry to say. You should have unrooted the phone first, then fastbooted the factory image, or do a factory reset, and made sure that OEM unlocking & USB debugging were left on until you were done locking the bootloader. Sorry man, but there's not much you can do without at least a stock recovery, so....accept the loss, learn from your mistake, and move on. Many of us here, including myself, have been there as well. What you choose to learn from it is up to you
Click to expand...
Click to collapse
Thank you so much, i will accept this loss as you said and absolutely i will learn from it. Tupac was right " that which does not kill me can only make me stronger "
Chouiyekh said:
Thank you so much, i will accept this loss as you said and absolutely i will learn from it. Tupac was right " that which does not kill me can only make me stronger "
Click to expand...
Click to collapse
No problem my friend. As they say "s#*t happens"
And your quote isn't from Tupac, it's from the philosopher Frederick Nietzsche in 1888. :laugh:
Badger50 said:
No problem my friend. As they say "s#*t happens"
And your quote isn't from Tupac, it's from the philosopher Frederick Nietzsche in 1888. :laugh:
Click to expand...
Click to collapse
Easy to mistake the two...
Badger50 said:
No problem my friend. As they say "s#*t happens"
And your quote isn't from Tupac, it's from the philosopher Frederick Nietzsche in 1888. :laugh:
Click to expand...
Click to collapse
hahaha, what a big mustache he has
CyberpodS2 said:
Easy to mistake the two...
Click to expand...
Click to collapse
Oh absolutely it is! Almost like twins! ???
Badger50 said:
Oh absolutely it is! Almost like twins!
Click to expand...
Click to collapse
:laugh::laugh::laugh:
Chouiyekh said:
:laugh::laugh::laugh:
Click to expand...
Click to collapse
have you tried flashing the official ota image as that doesnt require an unlocked bootloader so it coud be worth a shot
kevtrysmoddin said:
have you tried flashing the official ota image as that doesnt require an unlocked bootloader so it coud be worth a shot
Click to expand...
Click to collapse
You are correct. Unfortunately, he has no stock recovery anymore