$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?
Related
Okay my phone has been working fine till now.
My IMEI is intact still displays *#06# the correct no. It has been unlocked. I have rooted installed a custom ROM all was working okay till yesterday. When I turn the phone on emergency calls only is displayed. When I try to make a call it pops up with not registered on network. My data works okay though so I know am not blacklisted. Has anybody got a fix. Been searching but can seem to find a solution. Please help.
you have a backup of your efs folder?
Try a data clear.
Make sure you already have a backup of efs.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Try a data clear.
Make sure you already have a backup of efs.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I have tried it already. It's seems like my phine has locked itself in emergency mode and doesnt want to come out of it
Sent from my GT-I9305 using xda app-developers app
MrCeez said:
I have tried it already. It's seems like my phine has locked itself in emergency mode and doesnt want to come out of it
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Gonna have to bump this, since I have the same issue.
Phone was working fine until I tried this rom. Now every rom I try, including flashing stock using odin, leaves the phone as "emergency calls only". I've tried different modems etc, nothing.
Current baseband N71000NEDLK1.
Even flashing the proper UK 3 network stock rom, nothing.
Have you tried with another sim card? Maybe you have a damage sim.
zabumba said:
Have you tried with another sim card? Maybe you have a damage sim.
Click to expand...
Click to collapse
Ive tried my mrs' o2 card, same issue there.
It feels like a rom has changed everything, my modem even. I've tried to flash one recommended for Three UK, but it didn't seem to stick in recovery.
X82X said:
Ive tried my mrs' o2 card, same issue there.
It feels like a rom has changed everything, my modem even. I've tried to flash one recommended for Three UK, but it didn't seem to stick in recovery.
Click to expand...
Click to collapse
Try to restore the stock Firmware or a different custom rom
aukhan said:
Try to restore the stock Firmware or a different custom rom
Click to expand...
Click to collapse
I fear for the worst. I've read a few entries from people saying when this happened to them (some never rooted or on any custom rom) they had a paperweight.
I've tried about 6 different stock roms, many custom. Many modems. Nothing will get it working.
The phone has full signal, can scan for networks, but will not allow calls or connect to data.
I've tried the sim elsewhere and it's fine.
Since this is my only means of communication, I'm extra worried.
Any help on this matter, is greatly appreciated!
X82X said:
I fear for the worst. I've read a few entries from people saying when this happened to them (some never rooted or on any custom rom) they had a paperweight.
I've tried about 6 different stock roms, many custom. Many modems. Nothing will get it working.
The phone has full signal, can scan for networks, but will not allow calls or connect to data.
I've tried the sim elsewhere and it's fine.
Since this is my only means of communication, I'm extra worried.
Any help on this matter, is greatly appreciated!
Click to expand...
Click to collapse
Is your IMEI number intact as shown on the box ?
Which device is this i mean model ?
N7100 or N7105 or some other is this a Carrier specific device ?.
aukhan said:
Is your IMEI number intact as shown on the box ?
Which device is this i mean model ?
N7100 or N7105 or some other is this a Carrier specific device ?.
Click to expand...
Click to collapse
The IMEI is 004XXX010640000 / 01
Model N7100.
{
"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"
}
X82X said:
The IMEI is 004XXX010640000 / 01
Model N7100.
Click to expand...
Click to collapse
Is IMEI matching on the box ?
aukhan said:
Is IMEI matching on the box ?
Click to expand...
Click to collapse
Sorry, I never had a box. My dad has been using it great for 6 months, I have it a day, stick a rom on it and boom. But I'm smelling something with the kernel. I changed the kernel and now there is no signal at all. I need to find the right one for this UK model.
I've got the same exact problem as well, my N7100 bought it from china ( not copy) and after install Hong Kong version of stock rom via Odin,I have the same exact problem.
1. I can search for all the available network.
2. Under settings-about-status, it shows my phone number, my carrier, HSDPA mode...all looks normal except "emergency call"
3. I tried calling the sim that was in the N7100 and text message, the line works,text message shows as delivered, but nothing turns up on the N7100.
I've tried custom,stock,per-rooted from many versions of the world but the problem is still there.
X82X said:
Sorry, I never had a box. My dad has been using it great for 6 months, I have it a day, stick a rom on it and boom. But I'm smelling something with the kernel. I changed the kernel and now there is no signal at all. I need to find the right one for this UK model.
Click to expand...
Click to collapse
i think your the victim of IMEI corrupt or EFS Folder corrupted
as the IMEI 004XXX010640000 / 01 this is what you posted it looks suspcious to me
pull the battery there is sticker match the IMEI showing on the sticker and from phone see it they matches if they dont they your in deep trouble where you may have to get it serviced
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
pixellized said:
I've got the same exact problem as well, my N7100 bought it from china ( not copy) and after install Hong Kong version of stock rom via Odin,I have the same exact problem.
1. I can search for all the available network.
2. Under settings-about-status, it shows my phone number, my carrier, HSDPA mode...all looks normal except "emergency call"
3. I tried calling the sim that was in the N7100 and text message, the line works,text message shows as delivered, but nothing turns up on the N7100.
I've tried custom,stock,per-rooted from many versions of the world but the problem is still there.
Click to expand...
Click to collapse
suggest you to try this and check #15
aukhan said:
i think your the victim of IMEI corrupt or EFS Folder corrupted
as the IMEI 004XXX010640000 / 01 this is what you posted it looks suspcious to me
pull the battery there is sticker match the IMEI showing on the sticker and from phone see it they matches if they dont they your in deep trouble where you may have to get it serviced
Click to expand...
Click to collapse
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.
X82X said:
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.
Click to expand...
Click to collapse
always remember option number when rooting device always make a backup of Efs folder or backup you rom
aukhan said:
always remember option number when rooting device always make a backup of Efs folder or backup you rom
Click to expand...
Click to collapse
But, for me, the IMEI number is still the same as my original number,from the back of the phone sticker & also the box, could my phone's problem be any different?
pixellized said:
But, for me, the IMEI number is still the same as my original number,from the back of the phone sticker & also the box, could my phone's problem be any different?
Click to expand...
Click to collapse
First thing before you try anything else make a backup of EFS folder search for the thread you will find specific to Note 2.
then try to make a ROM backup
then Flash the stock Firmware see if this works.
X82X said:
Correct. The IMEI is totally different. But as I said, I am not going to fix it. I'll just sell it on cheap for someone else to. It's a shame and annoying that something like this can go wrong and potentially brick a phone. I know theres risks to all rooting/custom roms, which I accept, but it still doesn't stop it stinging when it does go wrong, which to my knowledge, wasn't my fault.
Click to expand...
Click to collapse
Don't be paniced mate. The problem is easy to solve. With a root explorer find the folder efs_Backup, location of the folder varies from rom to rom. If you are in a custom stock rom, you'll find it under sd card. It also may locate on root/media. Every time you flash a new rom the efs backed up automatically in zip. After finding the folder, open it, you'll find many zip files mentioned dates. Extract the one you remember when your phone was fine. Then copy the whole content of the extracted folder and paste to the root/efs.
Before pasting, erase the existing contents of the efs folder.
DONE!
Sent from my GT-N7100 using xda premium
This is the first carrier unlocked phone I've purchased. It's brand new and I bought it because I'm an M8 fanboy and my first M8 is dying. I'm on AT&T. I just got the phone and installed my SIM and setup my google accounts and all that stuff. I want to update Android but when I go to setting/about/software updates all it says is "checking". It's been checking for over an hour. Did I do something wrong? Is there a way to get the latest OTA Android for an AT&T M8?
My plan is to get to MM then unlock the bootloader and flash TWRP so I can start flashing custom ROM's. I never did anything to my original M8 but have done rooting etc on my old HTC Vivid and both my ASUS tablets.
Thanks in advance for your help.
Post fastboot getvar all result (remove serial & imei no.)
If it is a EU variant, then you can install RUU to update it to Marshmallow.
ckpv5 said:
Post fastboot getvar all result (remove serial & imei no.)
If it is a EU variant, then you can install RUU to update it to Marshmallow.
Click to expand...
Click to collapse
First, thanks for your reply ckpv5.
Second, not sure I'm following you. I can connect via ADB and it show this when I use the devices command:
device product:htc_europe model:HTC_One_M8 device:htc_m8
Is that the correct ADB command or am I just doing it wrong. Could you please provide more information. I'd really appreciate it. This is my first carrier unlocked phone so I'm a noob at this.
theandies said:
First, thanks for your reply ckpv5.
Second, not sure I'm following you. I can connect via ADB and it show this when I use the devices command:
device product:htc_europe model:HTC_One_M8 device:htc_m8
Is that the correct ADB command or am I just doing it wrong. Could you please provide more information. I'd really appreciate it. This is my first carrier unlocked phone so I'm a noob at this.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot getvar all
Thanks for everyone's replies so far.
Here is what I get when doing the adb commands suggested.
{
"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"
}
Now help me continue with getting this phone updated to at least MM.
:good:
theandies said:
Thanks for everyone's replies so far.
Here is what I get when doing the adb commands suggested.
Now help me continue with getting this phone updated to at least MM.
:good:
Click to expand...
Click to collapse
Download this RUU.zip
Rename it by deleting everything in name of the .zip except for 0P6BIMG (and .zip of course)
Place the renamed .zip onto your extSD card and put it into your phone. (the card must be formatted to FAT32 for this, and if it is 32gb or less, it probably already is)
Boot to bootloader and follow the prompts (vol up to confirm the flash ~ power button to reboot after it's flashed)
And that's it, super easy.
Make sure to delete the renamed .zip after the flash, or every time you boot to bootloader it'll try to update again
Good luck!
Awesome. Trying it now.
Can you school me on the information that I posted? I'm used to messing with WiFi only tablets and this is my first time messing this deep into a phone. I don't want to brick my brand new M8 so I'm going real slow.
Here is some more info if needed. I see it says s-off, is that correct? Also, once I update can I then proceed to flash TWRP and custom ROM's?
Thanks. Updated to Android 6!!! Now beware I'll have a lot more questions.
theandies said:
Thanks. Updated to Android 6!!! Now beware I'll have a lot more questions.
Click to expand...
Click to collapse
Cool! glad I could help.
A little info: since you are S-Off you shouldn't need to unlock the bootloader before you flash TWRP and ROMs, S-Off is all you'll need.
So it IS s-off! Cool. Any way you could tell me how you knew what RUU to use? Just trying to learn.
theandies said:
So it IS s-off! Cool. Any way you could tell me how you knew what RUU to use? Just trying to learn.
Click to expand...
Click to collapse
Your version-main in your getvar/ OS in your bootloader is your current firmware version. To find what you need for updating, the third series of numbers is what is important to match. In your case that was 401 which = WWE/Interanational
But that won't matter with your M8, only if you get a newer HTC device. The RUU I linked you to is not only the latest, but also the last firmware/ROM update for the M8. It won't be updated anymore and hasn't been for almost a year. In general, manufacturers and carriers will only update a device for two years.
xunholyx said:
Your version-main in your getvar/ OS in your bootloader is your current firmware version. To find what you need for updating, the third series of numbers is what is important to match. In your case that was 401 which = WWE/Interanational
But that won't matter with your M8, only if you get a newer HTC device. The RUU I linked you to is not only the latest, but also the last firmware/ROM update for the M8. It won't be updated anymore and hasn't been for almost a year. In general, manufacturers and carriers will only update a device for two years.
Click to expand...
Click to collapse
Understood. I have one more problem. My mobile data is not working. I checked all the APN settings and all of them are grayed out. Any ideas on what to do? I'll post a screenshot in a while. Just got to work.
I also tried *#*#4636#*#* but I really don't want to do anything with that yet as I really don't know what to do there and don't want to make things worse.
Texting and phone calls are working just fine.
Well snooping around the internet at work tonight I was able to figure out that I need to set my APN setting. More snooping and I found an APN setting that works......kind of. It will not go 4G LTE only HSPA. Here is a screen shot and the APN settings that get me HSPA.
I will try and duplicate the APN settings from my old phone in the mean time does anyone have a known good 4G (or 4G LTE) AT&T APN that will work with this phone? Hopefully I've posted enough information for the experts to help me get back up to speed.
Either of those APNs should work fine. Literally, the grayed out one (nextgenphone) is the one I'm on now, and it works flawlessly for me (3G, LTE, MMS, etc.). The one you entered (ATT Phone) I believe is actually the new/current one being used as default on most newer ATT phones, and should work fine as well. Your problem isn't APN, I think it's the RUU you used.
I would suggest using the AT&T RUU 6.20.502.5 from here (see RUU section): https://forum.xda-developers.com/showthread.php?t=2751432
Note the red text below the RUU. If you get Error 155 installing the RUU, you'll need to fastboot flash the firmware, before the RUU will install properly (peculiarity of US Marshmallow RUUs).
Reason you need the AT&T RUU, is that by flashing the Euro RUU, you installed the Euro radio, which is only intended to support LTE bands 3, 7, 8, 20. AT&T uses LTE bands 2, 4, 5, and 17. Therefore, you are missing support for every LTE band used by AT&T (the band or bands used by AT&T in you local area being the most important), and explains why everything works but LTE.
Great information redpoint73. I'll flash the other RUU this weekend.
Please bear with me, when you say flash via. fastboot you mean using ADB and pushing it though USB from my computer? Forgive me but as I said this is my first phone I've messed with this deep. My experience has been on ASUS tablets and most of the custom stuff done on them is usually flashed via SD card (or internal storage) 99% of the time. I can do it with the help of XDA I just don't want to render my new M8 inoperable.
theandies said:
when you say flash via. fastboot you mean using ADB and pushing it though USB from my computer?
Click to expand...
Click to collapse
If you read the red colored note regarding Error 155, under the RUUs in my Index thread (which I linked) you will see another link there, to a separate post/thread that will tell you exactly how to flash the firmware (if needed). Follow those instructions, and you will be good.
Flash via fastboot uses your computer and USB. But keep in mind that adb and fastboot are similar, but not exactly the same.
I see the RUU you suggested is an .exe file. Just connect via ADB and run that file? Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Thanks
theandies said:
I see the RUU you suggested is an .exe file. Just connect via ADB and run that file? Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Thanks
Click to expand...
Click to collapse
Just hook up your phone and double click on the download. The .exe will install a lot like software for your PC
If it fails to install booting to bootloader first before starting the RUU.exe sometimes helps.
On HTC's US website, there are both manual update instructions and a download for the RUU
I'm not sure if you'll need to flash the firmware first since you are already on Android 6, but it couldn't hurt to do so, and you might actually need to.
Awesome, this place is full of great people willing to help. I just wish I could reciprocate more.
theandies said:
Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Click to expand...
Click to collapse
It wouldn't hurt to flash firmware first. Only reason I would suggest folks to run the RUU first (and see if it works) is because not everyone is comfortable using fastboot commands to flash the firmware (and therefore may avoid having to learn how to do that). But if you are comfortable with the process to flash the firmware (it's not hard), then go ahead and do so before running the RUU.
Like xunholyx, I'm not sure if you need to flash the firmware first, or not. If you were coming from Lollipop, you definitely would need to. I have a feeling that you will indeed need to flash the US firmware before the RUU will install. Even though you are on Marshmallow firmware, it's the Euro one, so I think (but not sure) the RUU will still fail until you flash the US MM firmware.
EDIT - Forget it I found it........duh.
Thanks redpoint73. I'm going to flash the firmware first because of what you said (Euro phone vs. US).
I can't seem to find your post on how to do that again in the sea of posts. I thought I bookmarked it but it's not there. Can you be so kind as to link it up.
:good:
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.
Hello all, So I have been flashing for years but I am a complete nOOb. Ive just spent 4 hours looking around the internet and XDA for a solution to this issue... Any thoughts or help would be greatly appreciate it!
First off when I received this phone I waited the 7 days for Samsung's new security feature (I came from a S5 so this was a shock). Flashed TWRP with no issues. Proceeded over a few weeks to flash Lineage, Resurrection remix, and then tried to flash Light ROM for the s9. Had some issues with that so I flashed back to Stock Firmware no issue and have been using the past month. Now that I am not busy again I wanted to get twrp back on my phone but OEM unlock was not available. Thought that was weird seeing as the up time was well over the 168 hour marker so I decided to factory reset just to see if that would reset it. I waited the 7 days again and still wasnt there. So I wanted to Flash Stock rom again but now whenever I do it this pops up on the download screen:
sw rev. check fail (bootloader) device 2, binary 1
and Odin is stuck on the recovery.img protion.
Please let me know if you an help or if more info is needed!
Check you're not trying to downgrade the bootloader as shown here
G960FXXU2BRGA << Version 2
Check which version it says in Download mode (B:1 or B:2)
Either match it or flash a higher version
*Detection* said:
Check you're not trying to downgrade the bootloader as shown here
G960FXXU2BRGA << Version 2
Check which version it says in Download mode (B:1 or B:2)
Either match it or flash a higher version
Click to expand...
Click to collapse
{
"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"
}
Picture is of my download screen and ,
Great call! Just dug into it some more and thats the issue. Since the PAK CSC isnt on U2 yet im going to flash one from another country. I know you can but ive never heard of the downsides of flashing another countries firmware... is there one? Also have you heard of the issue with the oem unlock not appearing after 7 days?
Edit: Also what is the proper way to give you credit for answering the question as well as pointing out a good answer for people in the future who are confused? Just the thanks button?
Update: I tried again with a swiss one with Version 2 but it still failed. Ill download a few and try them as well just to be sure.
drowsy_fish said:
Picture is of my download screen and ,
Great call! Just dug into it some more and thats the issue. Since the PAK CSC isnt on U2 yet im going to flash one from another country. I know you can but ive never heard of the downsides of flashing another countries firmware... is there one? Also have you heard of the issue with the oem unlock not appearing after 7 days?
Edit: Also what is the proper way to give you credit for answering the question as well as pointing out a good answer for people in the future who are confused? Just the thanks button?
Update: I tried again with a swiss one with Version 2 but it still failed. Ill download a few and try them as well just to be sure.
Click to expand...
Click to collapse
Yea just hit the thanks button if someone helped (I don't see your image)
Only real downsides I've heard of are things like VoLTE and WiFi calling not being active on certain CSCs
Check the "Repartition" option in ODIN 3.13.1 settings too, possible the custom ROM messed them up
OEM unlock does seem to be hit and miss for some people, some get it immediately (I did), some wait 7 days, others wait 7 days and nothing, not seen a solution other than just keep waiting yet
*Detection* said:
Yea just hit the thanks button if someone helped (I don't see your image)
Only real downsides I've heard of are things like VoLTE and WiFi calling not being active on certain CSCs
Check the "Repartition" option in ODIN 3.13.1 settings too, possible the custom ROM messed them up
OEM unlock does seem to be hit and miss for some people, some get it immediately (I did), some wait 7 days, others wait 7 days and nothing, not seen a solution other than just keep waiting yet
Click to expand...
Click to collapse
Eh im not to worried about VoLTE or WifiCalling so thats good but I was under the impression you needed a PIT file to re-partition your phone without bricking it? (No clue whata PIT file is , just remember reading that about 5 years ago)
Hmm thats annoying.... the idea for this security is nice but it is sure a hassle for people who want custom binaries.
drowsy_fish said:
Eh im not to worried about VoLTE or WifiCalling so thats good but I was under the impression you needed a PIT file to re-partition your phone without bricking it? (No clue whata PIT file is , just remember reading that about 5 years ago)
Hmm thats annoying.... the idea for this security is nice but it is sure a hassle for people who want custom binaries.
Click to expand...
Click to collapse
PIT file is now included in the CSC part of the firmware (Partition Information Table)
Yea Samsung have really gone to town on locking down devices lately, I haven't even bothered rooting a phone since my S5, had an S7 and now S9 since then, just left them stock
*Detection* said:
PIT file is now included in the CSC part of the firmware (Partition Information Table)
Yea Samsung have really gone to town on locking down devices lately, I haven't even bothered rooting a phone since my S5, had an S7 and now S9 since then, just left them stock
Click to expand...
Click to collapse
God, I loved the S5... solid phone. Had it up to just 3 months ago when I got the s9.
I had just tried to flash the firmware I just used and failed with. But I clicked to fast and forgot to check the box for it to re-partition with. Weirdly enough it flashed with no issue... I have no clue what happened but it must have just been those 1s and 0s being finicky. Thanks for the info about the bootloader ect though.... you have been a huge help brother
drowsy_fish said:
God, I loved the S5... solid phone. Had it up to just 3 months ago when I got the s9.
I had just tried to flash the firmware I just used and failed with. But I clicked to fast and forgot to check the box for it to re-partition with. Weirdly enough it flashed with no issue... I have no clue what happened but it must have just been those 1s and 0s being finicky. Thanks for the info about the bootloader ect though.... you have been a huge help brother
Click to expand...
Click to collapse
Nice one, just a glitch in the matrix no probs :good:
*Detection* said:
Check you're not trying to downgrade the bootloader as shown here
G960FXXU2BRGA << Version 2
Click to expand...
Click to collapse
I am also stuck at recovery.img in Odin, while downgrading to a 6 months older stock firmware. The long story short - I want the older firmware because I have a TWRP backup done while this older stock rom was installed on my phone. When upgraded to the new stock firmware, I lost root and restored the TWRP backup (incl. boot) but in the end it the phone doesn't start up. So I want to install the older stock rom in order to be able to restore the TWRP backup. Any ideas how to do that? My only wish is to have a phone that boots and to which I can restore the TWRP backup (where all my apps and settings are).
Update: managed to flash the new firmare, I obviously cannot flash the older firmware because of the older bootloader. So, any ideas how to restore the TWRP backup (made when the old firmware was installed) while the new firmware is currently installed?
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