Title says it all.
I no longer had the "+" on top in Access Point Names to add a new one?
I have a fresh install of Nougat and a factory reset.
Not rooted and bootloader locked.
Anyone else see this problem?
Steve
I don't have that problem. I'm on NRD90U, everything stock. What's your build number?
Same build number as you.
Are you on Verizon?
{
"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"
}
I can also add APN fine. Same build, AT&T. Can you edit that one?
1. Unlock your bootloader
2. See #1
dratsablive said:
1. Unlock your bootloader
2. See #1
Click to expand...
Click to collapse
I was able to add a new APN before Nougat without being bootloader unlocked?
What do you mean by "See #1"?
BackInA88 said:
I was able to add a new APN before Nougat without being bootloader unlocked?
What do you mean by "See #1"?
Click to expand...
Click to collapse
What I meant is just Unlock your bootloader and leave it that way. You'll be thankful when you run into trouble flashing updates and or custom roms, etc.
dratsablive said:
What I meant is just Unlock your bootloader and leave it that way. You'll be thankful when you run into trouble flashing updates and or custom roms, etc.
Click to expand...
Click to collapse
I use to flash ROM's all the time.
But I have been happy with stock and use Android Pay all the time and would rather not have to deal with the problems that goes with getting it to work with root.
I may unlock and flash the new Nougat factory imgs as I ADB'd the OTA.
Maybe that has something to do with my problem?
I also installed the Pixel Launcher but I don't see how that come have effected my problem?
You can be on stock without root and still keep an unlocked bootloader.
Unlocked the bootloader and fastboot flashed everything, no joy!
Thinking about giving this a try?
*2767*3855# - Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
I just looked at my wife's 5X with Nougat is it doesn't have the "+" either on the APN?
Maybe it has something to do with Verizon?
So iirc google now downloads the apns for your carrier on first boot, and I know some carriers lock out apn editing. Not sure if that happens with this device though.
Related
So I'm not new to flashing roms, bootloaders, recoveries, or rooting. Ive had a wing, a G1, a Behold II, a G2, and a mytouch 3g slide. All rooted, re-rom'ed, etc. Not to mention various friends and family phones I've worked with.
Anyway, I'm about to send my G2 in for warranty so I figured I need to at least unroot it if not S-on. Unfortunately I don't remember what exact method I used to reach Root and S-off, which is probably one of my problems, But it didnt have anything to do with Gfree. It was way before that and quite a while ago.
I've been over the G2 unroot thread here over and over again, as well as other forums and they all seem almost exact to what is posted here. I've tried this method over and over and I'm not getting anywhere. I have a few problems that I'm sure are what is keeping this from progressing. I cant seem to flash the PC10IMG - I get a no image or bad image error. I can't flash the stock_root rom via clockwork recovery due to some sort of scripting error. I have no Idea where to head from here, I can't seem to find any different methods to remove perm. root. Also that thread mentions using the hex editor to change the version number. When I open my misc.img it already shows the 1.19.531.1.
I'll include a few hopefully helpful images, Any help would be GREATLY appreciated. I should be getting my new one today, maybe tomorrow (I haven't been tracking it), and need to send my old G2 back in before too long.
{
"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"
}
flash a stock 1.19 rom through bootloader or fastboot RUU.
If you have fake s-off, then it will be straight to stock.
otherwise just run gfree with -s on switch after flashing a stock rom.
-Nipqer
Do you have any idea, preferably a link, to find a stock 1.19 rom? I feel like ive been looking all day and nothings turned up.
http://www.shipped-roms.com/download.php?category=android&model=Vision&file=PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
md5: 531c08dc402e15577b947bf4cd22aec2
-Nipqer
Thanks man! I really appreciate it. I don't know why but I just could not find it yesterday. I'm not usually this slow =x lol.
I went through the same thing last week....After receiving the replacement G2, and using ADB to use the recommended gfree method and did a CLEAN PERFECT root I went about removing root from the old phone....No matter what I did I could not get the old root removed, so I did the unthinkable.....I creatively changed the dd command and was able to brick the phone.....Hopefully that will prevent any notice of previous rooting....(I couldn't boot, bootloader, etc...)
Mod Edit: content removed.
i have a problem after unlock bootloader with this procedure...when i try to flash "twrp recovery 2.8.7.0" and "boot image modded for root MM" from fastboot i see always this error..."remote:image verification error"
{
"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"
}
i have seen this error on internet and says that the cause is the bootloader locked! but if i test from fastboot my bootloader state says that is unlocked
This website is a SCAM? is not that only the text that says "unlocked" has been changed but the phone is locked?
Same Issue on Honor 7
I have exactly the same behaviour on my Honor 7 - tried several recovery firmwares, none worked
smilemak said:
I have exactly the same behaviour on my Honor 7 - tried several recovery firmwares, none worked
Click to expand...
Click to collapse
i can change firmware but when i want flash a image from fastboot take this error. You have a different problem.
fosseperme said:
i can change firmware but when i want flash a image from fastboot take this error. You have a different problem.
Click to expand...
Click to collapse
I think this thread is about unlocking the bootloader on the Honor 7? You wrote
when i try to flash "twrp recovery 2.8.7.0" and "boot image modded for root MM" from fastboot i see always this error..."remote:image verification error"
Click to expand...
Click to collapse
So were you able to flash recovery and boot to TWRP?
I open a dispute PayPal vs Dc Unlocker and they immediately lock my account on website! SCAM
Of course it's a scam that sort of thing supposedly paying this kind of thing exists for all.
I understand why people still pay.
Remove immediately !!!!
fosseperme said:
I open a dispute PayPal vs Dc Unlocker and they immediately lock my account on website! SCAM
Click to expand...
Click to collapse
If it is a scam and doesn't work 100%, can you change the subject in the OP?
people will read the first post and spend money on something that doesn't work :silly:
After unlock with this method, i have upgrade to mm beta rom. Can an upgrade relock the bootloader?
fosseperme said:
After unlock with this method, i have upgrade to mm beta rom. Can an upgrade relock the bootloader?
Click to expand...
Click to collapse
I've never seen
What can you read after rebooting into "Fastboot" mode? Unloocked; Locked; Relocked?
@fosseperme
If you discovered this was a scam, why not remove the info from the opening post and say so, so others aren't hooked into this?
I have done it for you, and will close this thread.
Darth
Forum Moderator
[SOLVED] I have rooted my 1050L to fix sharpness. After some weeks I received an OTA and installed. Stupid me. Tried to flash stock rom from temp TWRP, no luck.
Tried some suggestions from here and there, and now i have only DNX mode left. PhoneFlashTool says I'm in wrong mode.
HELP! Am I hardbricked?
{
"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"
}
SOLVED
daverob79 said:
I have rooted my 1050L to fix sharpness. After some weeks I received an OTA and installed. Stupid me. Tried to flash stock rom from temp TWRP, no luck.
Tried some suggestions from here and there, and no i have only DNX mode left. PhoneFlashTool says I'm in wrong mode.
HELP! Am I hardbricked?
Screenshot on imgur.com/gnUBeXS
Click to expand...
Click to collapse
Installed YT2-1050L_USR_S000225_1504220451_WW21_ROW.zip with PhoneFlashTool Lite 5.3.4.1
Then everything worked. Dont know what i did wrong, or if only this version vorked???
daverob79 said:
Installed YT2-1050L_USR_S000225_1504220451_WW21_ROW.zip with PhoneFlashTool Lite 5.3.4.1
Then everything worked. Dont know what i did wrong, or if only this version vorked???
Click to expand...
Click to collapse
Ok, so I was able to flash this rom and boot the tablet. But when i get the OTA the tablet crashes...
The OTA was YT2-1050L_USR_S100192_1511191319_WW52_ROW
Now trying YT2-1050L_USR_S100081_1507241439_WW52_ROW, will update with results
Can it be that the OTA did not have all the right files. Or did the root process do something so that I can only flash stock roms?
I am really not getting any wiser on this intel world. Only been playing with Samsung, Nexus(LG/ASUS) and HTC
Any thoughts? Anyone??
And I can't post images, sorry for that :c
forgot this,
Thanks ionioni
after you flash remember to set your region code before taking any ota's (on the first Android boot go to Contacts and in the search contacts box input ####59930# and if it shows a two letter country code then you're good to go, if it shows 'unknown' then you need to set a country code, input in the same box ####6020# and chose a country, yours or a close one, tablet will reboot)
Click to expand...
Click to collapse
After you flashed the from,did you go to contacts and enter your Country code, without this code it will not take updates.
Sorry missed your last post.
corasman said:
After you flashed the from,did you go to contacts and enter your Country code, without this code it will not take updates.
Sorry missed your last post.
Click to expand...
Click to collapse
I did
Now I have my tablet back!
Seems like there is a big difference between the ROM's (the YT2_1050L_USR* files)
Maybe we should have a tread with all the different ROM's?
I found this on Androidfilehost: Link to downloads for Lenovo Yoga Tablet 2 by ionioni
But how do you see the difference between different roms. Many are big files even if they are not stock roms (with radio, droidboot, bootloader, bios etc)
Now I have 1050L_S100255_160113
Is this the latest ROM?
I think the differences are in the file names...after YT2 it tells you which file is for which model.
Hello,
Back in August of 2015 I bought a FreedomPop Samsung Galaxy S4 which I used with FreedomPop up until just recently when I signed up with RingPlus, ported my old FreedomPop number to my R+ account and then deactivated my FreedomPop account. OK, so.. my problem is is that now I can't use R+ because it requires me to update my PRL, but I can't. I get this error: "The PRL update could not be completed. Please try again later. If the problem persists, you may need to contact Customer Service. Error: Connection Error (6)"
Now, in the past when I was trying to root my phone I really screwed things up and ended up having to install new Firmware. You can find more information about that here: http://forum.xda-developers.com/galaxy-s4-sprint/help/caught-boot-loop-rooting-t3304144
Any help would be greatly appreciated, especially since my phone is practically useless at the moment.
-Chuck
Try dialing ###72786#
{
"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"
}
bilgerryan said:
Try dialing ###72786#
Click to expand...
Click to collapse
When I tried that, the number disappeared when I added the last #. And it still won't let me update the PRL.
I think I know why that didn't work. I'm suppose to dial ##72786#, not ###72786#. I'm assuming you meant for me to reprovision my phone?
Anyway, I did that and seemed to be working fine, but then when I tried to update the PRL it, took me to hands free activation. Same when I tried to update my profile as well. How do I go about avoiding this?
I could really use some help here please.
Chuck38 said:
I could really use some help here please.
Click to expand...
Click to collapse
With what? If it updated profile and PRL them you are done. You only have to do this about once a month, not every day.
Alright. I should probably contact Ringplus directly about my other problem here.
Sorry for bothering you and thanks for the help.
Chuck38 said:
Alright. I should probably contact Ringplus directly about my other problem here.
Sorry for bothering you and thanks for the help.
Click to expand...
Click to collapse
Sorry, I missed that. I recommend Odining TWRP and then flashing the SuperSU zip in recovery for rooting.
bilgerryan said:
Sorry, I missed that. I recommend Odining TWRP and then flashing the SuperSU zip in recovery for rooting.
Click to expand...
Click to collapse
How would I go about Odining TWRP?
I've only used Odin to re-install my Firmware.
Chuck38 said:
How would I go about Odining TWRP?
I've only used Odin to re-install my Firmware.
Click to expand...
Click to collapse
Download TWRP and run it in the PDA slot.. Make sure to uncheck Auto Reboot.
bilgerryan said:
Download TWRP and run it in the PDA slot.. Make sure to uncheck Auto Reboot.
Click to expand...
Click to collapse
Alright. TWRP has been installed, as well as SuperUS. Just checked with Root Checker and my phone has been properly rooted.
However.. the problem still persists. I still am unable to get RingPlus to work with my phone. Perhaps because I can't update the PRL, it keeps taking me to hands free activation, or perhaps there's something else going on. I will see if I can contact RingPlus and see if they know what's wrong.
Thank-you for your assistance, I will report back if I get this figured out.
I read through the similar thread from yesterday, but this is a different issue...
I had unlocked, installed TWRP, and had been running a custom ROM (BadBoyz 1.2). This morning I re-locked so I could flash the updated firmware (v1.80) and now I am unable to re-unlock.
When I issue the command fastboot flash unlocktoken Unlock_code.bin, it works without errors, and the phone goes to the "Are you sure you want to unlock your bootloader?" screen.
However, at that screen, the volume buttons do nothing. I can't select yes OR no, it just sits there. Eventually it times out and just shows the battery charging on a black 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"
}
When I flashed the firmware, it removed TWRP, and with a locked bootloader, I can't re-flash it.
I was able to get a fully stock rom up and running, so I'm not in brickville anymore (had a few hours of panic earlier today), and I've been able to confirm that the OEM Unlock option is checked. I've even unchecked and re-checked to be sure. Everything works except the ability to confirm my choice and move on. I'm kind of afraid that it's a glitch in the new firmware, at this point...
Anyone got any ideas?
Thanks!!
deleted
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
have you tried running RUU.exe? i took that route and was able to unlock my bootloader again, flash twrp and upgrade to bb 2.0 with no problems
I had the same problem and had to flash a stock rom back on the phone before the unlocker would work.
I figured it out! I can't explain WHY it worked, but it worked...
I had re-flashed several times using the official RUU, and the results never changed...
Then yesterday I went through a mental checklist of what was different when I unlocked the first time... and the only thing, was that I hadn't put my SD Card in the phone yet when I unlocked the first time. So I went through the motions again to verify that it still didn't work, and it didn't. Then I ejected the SD Card and tried it - and BOOM, I was able to unlock!
The only thing I can think of is that the SD Card did have the Firmware .zip on it, which the phone auto-detected and asked if I wanted to install... even though I said no. As soon as I tried it without the card, it worked like it always had, I'm back to unlocked, and back to the custom ROM I had been enjoying so much...
Thanks for the tips, everyone, and I hope this thread helps someone else who finds themselves in the same boat!
scottspa74 said:
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, that is EXACTLY where I was at. However, finally found the way out of the mess.. (see above post)