Develop Bugs

[Q&A] Potential To Recover Note 4 Bootloader After Flashing Retail Firmware

Q&A for Potential To Recover Note 4 Bootloader After Flashing Retail Firmware
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Potential To Recover Note 4 Bootloader After Flashing Retail Firmware. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Ryanbg - note 4 DE re-unlock bootloader
Hi ryan, i was told to contact you about trying to re-unlock my note 4 developer edition bootloader. I cant post in the development section yet, so here i am. I made a huge mistake by flashing the note 4 stock rom on my note 4 DE. Before doing so i permanantly erased everything under advanced settings in TWRP. The icing on the cake is that i deleted my custom rom backup too. Can you help me? If my device becomes bricked i do have a protection plan under verizon and may be able to get a new stock note 4. Im decently tech savvy and will gladly help you out in any way.
Thanks, Adam

is it possible to flash a developer edition rom to a retail note 4 verizon
Just curious

Dale2x2 said:
Just curious
Click to expand...
Click to collapse
No. You can't flash anything on the retail Note 4. You don't have root and you don't have a custom recovery.

I guess I asked the wrong question
Is it possible to flash stock de firmware on retail note 4 after hearing of de editions being turned into retail it had me curious

Dale2x2 said:
Is it possible to flash stock de firmware on retail note 4 after hearing of de editions being turned into retail it had me curious
Click to expand...
Click to collapse
No there are device specific aboot and other individual phone markers that prevent you from flashing a RE and making it a DE. It sure would be nice to have someone on the inside able to help us with this or get our devs a specific program allowing this type of thing though

Thank you, I've racked my brain to try and help this retail root situation and like everyone else I'm coming up short.

thanks
Thanks

Flashing aboot
I have my aboot and I have tried to make it flashable but it fails. I have stripped all the zeroes from the last bit of data to the very end of the mbn file using HxD. I then used 7-zip to tar the aboot.mbn to aboot.tar. I then flash it. What I see on my phone is:
Product Name: SM-N910V
Current Binary: Samsung Official
System Status: Official
Reactivation Lock(KK): Off
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
SECURE CHECK FAIL: aboot
This is a devloper edition phone that was flashed with retail stock firmware in order to get Samsung Gear VR up and running. The aboot was saved using EFS pro beta before hand by itself and then all partitions were backed up. I can share aboot if needed. I dont have linux so I cant md5 the tar if that is required. I can send the aboot if needed.

I think I locked my bootloader
I have purposely steered clear of advanced operations as I can't wrap my head around many of those concepts. I've been safely rooting for the last 7 years until now. I just got my DE a few days ago and was having random reboots. I made recovery backups like I've always done before and thought that was enough since I don't do anything passed a few Xposed modules (tethering, ad removal) which is what I think was causing the reboots. I decided to start from scratch and applied SM-910V (I'm certain) firmware to find it will not root now. From the hours of reading I've done, I think my bootloader is locked.
I continue reading here now, but it seems I was supposed to backup aboot and Samsung can't help either? Since the device is 4-5 months old, I was hoping to find more positive information.
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
QUALCOM SECURE BOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START

bagery77 said:
I have purposely steered clear of advanced operations as I can't wrap my head around many of those concepts. I've been safely rooting for the last 7 years until now. I just got my DE a few days ago and was having random reboots. I made recovery backups like I've always done before and thought that was enough since I don't do anything passed a few Xposed modules (tethering, ad removal) which is what I think was causing the reboots. I decided to start from scratch and applied SM-910V (I'm certain) firmware to find it will not root now. From the hours of reading I've done, I think my bootloader is locked.
I continue reading here now, but it seems I was supposed to backup aboot and Samsung can't help either? Since the device is 4-5 months old, I was hoping to find more positive information.
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
QUALCOM SECURE BOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
Click to expand...
Click to collapse
Where did you get the "SM-910V firmware? If you got it from here xda: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937 and used the "Full Firmware" then you have locked your bootloader. Go to post #2, the OP offers two sets of downloads-one for retail versions of the Note 4 and one set for Developer Edition Note 4s. If you downloaded and installed a file from the retail set then you've locked your bootloader. However, you should be able to restore with your backed up aboot as you have tried. I'm not sure what you have to do to create a flashable aboot. Hopefully someone will chime in here and help you out. You can try PMing ryanbg to solicit his help.

jpcalhoun said:
Where did you get the "SM-910V firmware? If you got it from here xda: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937 and used the "Full Firmware" then you have locked your bootloader. Go to post #2, the OP offers two sets of downloads-one for retail versions of the Note 4 and one set for Developer Edition Note 4s. If you downloaded and installed a file from the retail set then you've locked your bootloader. However, you should be able to restore with your backed up aboot as you have tried. I'm not sure what you have to do to create a flashable aboot. Hopefully someone will chime in here and help you out. You can try PMing ryanbg to solicit his help.
Click to expand...
Click to collapse
Thank you for the reply. I got the firmware from Sammobile which I thought was reputable. I didn't get it from here because I wanted to unroot completely and go back to stock in case an Xposed setting was not the culprit for reboots. The firmwares I found here confused me as they seemed to specify rooted and retail versions. I guess it was dumb to assume Sammobile SM-910V firmware was actually for SM-910V device. I thought I was being careful.
From what I've been reading, normal backups don't appear to include aboot. So I think I'm effed.

bagery77 said:
Thank you for the reply. I got the firmware from Sammobile which I thought was reputable. I didn't get it from here because I wanted to unroot completely and go back to stock in case an Xposed setting was not the culprit for reboots. The firmwares I found here confused me as they seemed to specify rooted and retail versions. I guess it was dumb to assume Sammobile SM-910V firmware was actually for SM-910V device. I thought I was being careful.
From what I've been reading, normal backups don't appear to include aboot. So I think I'm effed.
Click to expand...
Click to collapse
Yeah, the file you got from Sammobile was retail firmware which will lock your bootloader, they don't understand the difference between a Developer phone and a retail phone. But, if you backed up your aboot as you say then all is not lost. Try giving ryanbg a PM to see if he can take the back up you have and create a flashable file for you. He has done that for some other users. Also, there are a few active members here on this forum that may be able to help. Manbat and EMSPilot may be able to help you. Give them a PM also. Good luck.

Locked Note 4 DE
I don't think that bagery77 backed up his aboot or at least he hasn't said he has in any of his posts. Samsung will be of no help either, I was told by tech support that if the phone is 100% stock and the download screen says Official that the phone has a one year warranty against failure. Note that the unlocked bootloader or Developer warranty is only 30 days. I was told (and have not confirmed) that if the phone suffers from a defect that is not related to flashing the phone or any physical damage that Samsung would replace the phone with another Developer Edition phone. I have sent a PM to Ryan with my aboot and will flash it to my phone as soon as I get it back to confirm a bootloader unlock from a full retail flash. If it works and does unlock my bootloader I will either be donating to Ryan or pledging to a cause of his choice. I just find it hard to believe that Samsung would say here is a developer device and then hoard the software to allow a 100% clean flash file like Motorola does. This is my first Samsung device but I have had several Motorola Developer devices. Side note, Gear VR works great!!!

Juxto2010 said:
I don't think that bagery77 backed up his aboot or at least he hasn't said he has in any of his posts. Samsung will be of no help either, I was told by tech support that if the phone is 100% stock and the download screen says Official that the phone has a one year warranty against failure. Note that the unlocked bootloader or Developer warranty is only 30 days. I was told (and have not confirmed) that if the phone suffers from a defect that is not related to flashing the phone or any physical damage that Samsung would replace the phone with another Developer Edition phone. I have sent a PM to Ryan with my aboot and will flash it to my phone as soon as I get it back to confirm a bootloader unlock from a full retail flash. If it works and does unlock my bootloader I will either be donating to Ryan or pledging to a cause of his choice. I just find it hard to believe that Samsung would say here is a developer device and then hoard the software to allow a 100% clean flash file like Motorola does. This is my first Samsung device but I have had several Motorola Developer devices. Side note, Gear VR works great!!!
Click to expand...
Click to collapse
You're right. You stated that you backed up your aboot, he did not. I got the two post confused. Not hard for me to do, lol. I hope ryanbg comes through for you.

Locked Note 4 DE
So I have been following the threads for root on the retail versions and I was wondering that if once root is obtained will that increase my chances of restoring my locked Dev edition device or am I kinda boned. I have other blocks backed up besides the aboot as well but I am not having any luck with flashing my backed up aboot back to my device. I haven't heard back from Ryan yet but I am hopeful that one way or another I will regain an unlocked bootloader.

Juxto2010 said:
I have my aboot and I have tried to make it flashable but it fails. I have stripped all the zeroes from the last bit of data to the very end of the mbn file using HxD. I then used 7-zip to tar the aboot.mbn to aboot.tar. I then flash it. What I see on my phone is:
Product Name: SM-N910V
Current Binary: Samsung Official
System Status: Official
Reactivation Lock(KK): Off
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
SECURE CHECK FAIL: aboot
This is a devloper edition phone that was flashed with retail stock firmware in order to get Samsung Gear VR up and running. The aboot was saved using EFS pro beta before hand by itself and then all partitions were backed up. I can share aboot if needed. I dont have linux so I cant md5 the tar if that is required. I can send the aboot if needed.
Click to expand...
Click to collapse
You forgot to trim off some of the junk data at the end of the aboot, and the 00's padding.
{
"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"
}
Open your aboot backup with a hex editor. You'll want to delete everything AFTER the highlighted data, but don't delete the highlighted data. Only then can you tar it and flash.

ryanbg said:
You forgot to trim off some of the junk data at the end of the aboot, and the 00's padding.
Open your aboot backup with a hex editor. You'll want to delete everything AFTER the highlighted data, but don't delete the highlighted data. Only then can you tar it and flash.
Click to expand...
Click to collapse
I'm confused. How do you tell what is junk data and what is good? I tried to help him and would like to know how to edit mine as well. From the way you said before it sounded like we just needed to remove the zeros at the end. I'm lost. At least I know EFS Pro will restore it lol. But a flashable would be much better.

Misterxtc said:
I'm confused. How do you tell what is junk data and what is good? I tried to help him and would like to know how to edit mine as well. From the way you said before it sounded like we just needed to remove the zeros at the end. I'm lost. At least I know EFS Pro will restore it lol. But a flashable would be much better.
Click to expand...
Click to collapse
Well before the S5/N4 all you needed to do was get rid of the 00s but there's actually a memory leak in the S5/N4 bootloader which copies a portion of a function in the bootloader to just after the second signature, which needs to be removed in order to pass signature verification. I'd thought they'd have fixed it by now, but I guess they haven't patched it yet.
---------- Post added at 09:55 PM ---------- Previous post was at 09:42 PM ----------
Juxto2010 said:
I don't think that bagery77 backed up his aboot or at least he hasn't said he has in any of his posts. Samsung will be of no help either, I was told by tech support that if the phone is 100% stock and the download screen says Official that the phone has a one year warranty against failure. Note that the unlocked bootloader or Developer warranty is only 30 days. I was told (and have not confirmed) that if the phone suffers from a defect that is not related to flashing the phone or any physical damage that Samsung would replace the phone with another Developer Edition phone. I have sent a PM to Ryan with my aboot and will flash it to my phone as soon as I get it back to confirm a bootloader unlock from a full retail flash. If it works and does unlock my bootloader I will either be donating to Ryan or pledging to a cause of his choice. I just find it hard to believe that Samsung would say here is a developer device and then hoard the software to allow a 100% clean flash file like Motorola does. This is my first Samsung device but I have had several Motorola Developer devices. Side note, Gear VR works great!!!
Click to expand...
Click to collapse
If you did happen to have an old S3/S4/N3 or any HTC/Motorola device based on Qualcomm chipsets that you can part ways with, I'd certainly appreciate it and pay for shipping. Even if it has a broken screen or parts, as long as it powers on, it'd be useful to me. They'd be used for research and development. That's only if it's lying around and collecting dust and you have no use for it. Otherwise a simple thank you is more than sufficient. It's really unfair how Samsung uses such a poor method for unlocking the bootloader and will refuse to service or repair such a device. If they aren't going to help anyone, who will? If anything, I'm protecting their Developer edition consumers from disaster.

ryanbg said:
Well before the S5/N4 all you needed to do was get rid of the 00s but there's actually a memory leak in the S5/N4 bootloader which copies a portion of a function in the bootloader to just after the second signature, which needs to be removed in order to pass signature verification. I'd thought they'd have fixed it by now, but I guess they haven't patched it yet.
Click to expand...
Click to collapse
So if I'm understanding this right I need to do the same to my bootloader? I have the same lines after what you highlighted. Just delete below the highlighted area along with the zeros at the end?

Should we wait to see if it is rooted ?

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.

AOSP on Sprint $$$

$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?

Help my Pixel XL,got bootloop,bootloader still locked

Please help my pixel xl
Condition now is bootloop with lock bootloader
Only can enter fastboot,cannot enter into recovery mode
Just try to flash with adb n fastboot but no luck 'cos bootloader still locked
{
"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"
}

andixxx81 said:
Please help my pixel xl
Condition now is bootloop with lock bootloader
Only can enter fastboot,cannot enter into recovery mode
Just try to flash with adb n fastboot but no luck 'cos bootloader still locked
Click to expand...
Click to collapse
That's a brick. Call Google with that one. They should replace that. Anytime I've seen the n/a for bootloader and baseband it's toast.

How did you brick with bootloader locked? Best bet is to RMA it for a replacement it's done unless there is a tool to save it but I doubt it

andixxx81 said:
Please help my pixel xl
Condition now is bootloop with lock bootloader
Only can enter fastboot,cannot enter into recovery mode
Just try to flash with adb n fastboot but no luck 'cos bootloader still locked
View attachment 4287902
Click to expand...
Click to collapse
Have you tried a newer RUU version from Google, or was it already on the newest?

toknitup420 said:
That's a brick. Call Google with that one. They should replace that. Anytime I've seen the n/a for bootloader and baseband it's toast.
Click to expand...
Click to collapse
Theres no other way to make this back normal?

liam_davenport said:
How did you brick with bootloader locked? Best bet is to RMA it for a replacement it's done unless there is a tool to save it but I doubt it
Click to expand...
Click to collapse
I just take picture and video,after that suddenly restarted and boot into this,i try to choose start,recovery mode,no luck..
Yes,i did twit google and they said must go to google store

michaelbsheldon said:
Have you tried a newer RUU version from Google, or was it already on the newest?
Click to expand...
Click to collapse
I dont know whats RUU version,i'm nubie about this sir:silly:

andixxx81 said:
I just take picture and video,after that suddenly restarted and boot into this,i try to choose start,recovery mode,no luck..
Yes,i did twit google and they said must go to google store
Click to expand...
Click to collapse
andixxx81 said:
I dont know whats RUU version,i'm nubie about this sir:silly:
Click to expand...
Click to collapse
Yeah RMA it then probably some hardware issue. He means Factory Image from here But I doubt you'll be able to flash one since locked and no fastboot

liam_davenport said:
Yeah RMA it then probably some hardware issue. He means Factory Image from here But I doubt you'll be able to flash one since locked and no fastboot
Click to expand...
Click to collapse
His only option is RMA. Locked bl so he can't do anything on his end. But this is clearly a hardware or software failure that is not his fault. Google will replace it.

Are there any News on this issue?
Got my Pixel Bootlooping with locked Bootloader, disabled OEM-Unlock Option.
Do i have any options other than RMA?

I had this problem too, except I could get into the recovery after many tries. I tried sideloading the ota with adb to fix it. But it didn't help. Any way to get replacement after this many years?

andixxx81 said:
Please help my pixel xl
cannot enter into recovery mode
Click to expand...
Click to collapse
You can get into recovery mode , by (in my case): leave the phone in Power Off mode for an hour or more - Start with power + volume down - recovery... and sometimes it works. But no, it does not help. I sideloaded the OTA multiple times, still no luck

ferydaboss said:
You can get into recovery mode , by (in my case): leave the phone in Power Off mode for an hour or more - Start with power + volume down - recovery... and sometimes it works. But no, it does not help. I sideloaded the OTA multiple times, still no luck
Click to expand...
Click to collapse
I confirm to that as I have the exact problem. I did manage to boot into system a few times after it started bootlooping but it always froze and restarted before I enabled oem unlocking.

iloveoreos said:
I confirm to that as I have the exact problem. I did manage to boot into system a few times after it started bootlooping but it always froze and restarted before I enabled oem unlocking.
Click to expand...
Click to collapse
exactly the same here i just talked to google support, hey redirected me to the UK google support, but i am from Romania, don't really know if they will RMA it or not.. but anyways i will have to pay shipping cost via DHL or something like that. maybe it's not worth it.

ferydaboss said:
exactly the same here i just talked to google support, hey redirected me to the UK google support, but i am from Romania, don't really know if they will RMA it or not.. but anyways i will have to pay shipping cost via DHL or something like that. maybe it's not worth it.
Click to expand...
Click to collapse
I read that replacing the battery sometimes fixes it. I might try that, but it sounds sketchy.

iloveoreos said:
I read that replacing the battery sometimes fixes it. I might try that, but it sounds sketchy.
Click to expand...
Click to collapse
I went to a local repair shop, they said the the "EEMC memory" is bad... meaning that i would have to replace the whole motherboard + there are no spare pieces in my country. Luckily i managed to talk to Google Support, and they will RMA it, i just need to clarify the details of shipping, packaging etc. we'll see HOw it works out. Also i just bought a used pixel 2 XL, so i'm good for the moment. Will sell the pixel XL they send me.

ferydaboss said:
I went to a local repair shop, they said the the "EEMC memory" is bad... meaning that i would have to replace the whole motherboard + there are no spare pieces in my country. Luckily i managed to talk to Google Support, and they will RMA it, i just need to clarify the details of shipping, packaging etc. we'll see HOw it works out. Also i just bought a used pixel 2 XL, so i'm good for the moment. Will sell the pixel XL they send me.
Click to expand...
Click to collapse
Was yours still on warranty?

iloveoreos said:
Was yours still on warranty?
Click to expand...
Click to collapse
It seems so, yes. I bought it last year, from someone, in my country who said it was bought from the UK. I contacted google for fun, and they said that based on the IMEI it is under warranty.

ferydaboss said:
It seems so, yes. I bought it last year, from someone, in my country who said it was bought from the UK. I contacted google for fun, and they said that based on the IMEI it is under warranty.
Click to expand...
Click to collapse
Ok, so I replaced the battery and it booted! Except I broke the screen taking it apart so I couldn't go on it.

NEXUS 5X bootloop, POSSIBLE to fix or PIECE OF trash?

hELLo,
All of a sudden this bootloop happens:
{
"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"
}
Is it possible to fix this nexus 5x? 16gb
0. Bootlooping.
1- Bootloader locked.
2- Can not Get into phone.
3- Can get into fastboot
4. Can get into recovery
5. ADB SIDE LOAD FAILED, sometimes at 11%, sometimes at 48%,
Tried following:-

Anyone?

Administr4tor said:
Anyone?
Click to expand...
Click to collapse
If it's bootlooping then that's what ended up happening to all the devices up until this point. The bootloop issue does not load beyond the recovery partition. It's not a software issue, it's hardware related. You can contact LG and see what they say, but it may be the end of it.

mikeprius said:
If it's bootlooping then that's what ended up happening to all the devices up until this point. The bootloop issue does not load beyond the recovery partition. It's not a software issue, it's hardware related. You can contact LG and see what they say, but it may be the end of it.
Click to expand...
Click to collapse
Thanks for confirming that LG is piece of trash.

My phone was working fine today till evening, suddenly it restarted and this boot loop started. I was on PixelRom (Oreo 8.0)
I tried flashing Factory image of 8.1 final release via fastboot. Its still not booting. Keeps restarting.
Any help?

Administr4tor said:
Thanks for confirming that LG is piece of trash.
Click to expand...
Click to collapse
Danish Fayaz said:
My phone was working fine today till evening, suddenly it restarted and this boot loop started. I was on PixelRom (Oreo 8.0)
I tried flashing Factory image of 8.1 final release via fastboot. Its still not booting. Keeps restarting.
Any help?
Click to expand...
Click to collapse
Contact LG. They're fixing these even if they're out of warranty.

My Nexus 5x bootlooping also. I try to sideload the latest ota and make an Factory Reset but did not help. Bootloader is locked and oem Unlock is disabled. What can I do?

-Happy Feet- said:
My Nexus 5x bootlooping also. I try to sideload the latest ota and make an Factory Reset but did not help. Bootloader is locked and oem Unlock is disabled. What can I do?
Click to expand...
Click to collapse
Throw it in garbage and never buy LG phones.

the fact you can enter recovery, heck even adb/fastboot means you can 99% fix it (the 1% being hardware failure, which i really doubt, due to overheating, but thats fixable with the cooper plate mod), there's tons of guides in the q&a forum section, search it up.

LG replaced my MOBO and CPU for free, even though I had bought used on eBay. I just used the confirmation email from eBay and PayPal as proof of purchase.
Assuming you have called LG and confirmed your trashy assumption take matters into your own hands.
Did you try "fastboot flashing unlock" command from command prompt while n5x is on the bootloader?
Then proceed to https://forum.xda-developers.com/nexus-5x/general/nexus-5x-bootloop-death-blod-andorid-t3683926
To fix BLOD

derrickl1990 said:
LG replaced my MOBO and CPU for free, even though I had bought used on eBay. I just used the confirmation email from eBay and PayPal as proof of purchase.
Assuming you have called LG and confirmed your trashy assumption take matters into your own hands.
Did you try "fastboot flashing unlock" command from command prompt while n5x is on the bootloader?
Then proceed to https://forum.xda-developers.com/nexus-5x/general/nexus-5x-bootloop-death-blod-andorid-t3683926
To fix BLOD
Click to expand...
Click to collapse
As I said, BOOTLOADER IS LOCKED, OEM IS LOCKED, CAN NOT ENTER into PHONE, so there is NO POINT IN trying FASTBOOT FLASHING UNLOCK, it will not do anything good.
tHis is not first time i have had ISSUES WITH NEXUS LG TRASH CANS, check these posts too :
Nexus6p-how-to-flash-stock-factory-rom
How-to-flash-NEXUS6 rom
Thx

Administr4tor said:
As I said, BOOTLOADER IS LOCKED, OEM IS LOCKED, CAN NOT ENTER into PHONE, so there is NO POINT IN trying FASTBOOT FLASHING UNLOCK, it will not do anything good.
tHis is not first time i have had ISSUES WITH NEXUS LG TRASH CANS, check these posts too :
Nexus6p-how-to-flash-stock-factory-rom
How-to-flash-NEXUS6 rom
Thx
Click to expand...
Click to collapse
Got it. Check with LG

Administr4tor said:
Thanks for confirming that LG is piece of trash.
Click to expand...
Click to collapse
Do what everyone is telling you to do: contact LG.
My Nexus 5X was overheating a lot and I sent it back to LG telling them about the bootloop issue and they offered me a complete refund for the phone.
It's a hardware issue, so you can't do anything related to software (ADB, fastboot, etc. nothing will work).

two questions
Carball0 said:
Do what everyone is telling you to do: contact LG.
My Nexus 5X was overheating a lot and I sent it back to LG telling them about the bootloop issue and they offered me a complete refund for the phone.
It's a hardware issue, so you can't do anything related to software (ADB, fastboot, etc. nothing will work).
Click to expand...
Click to collapse
1. Is/Was your phone under warranty?
2. Did they do for free? how long did it take? Please share their contact information, how you initiated this all process.
Thanks

Administr4tor said:
1. Is/Was your phone under warranty?
2. Did they do for free? how long did it take? Please share their contact information, how you initiated this all process.
Thanks
Click to expand...
Click to collapse
I bought my Nexus on Amazon and they kindly offered me a complete refund of the phone (it was under warranty, it had three months left).
I just opened a chat with Amazon support and they offered me the refund (completely free, I returned the phone to Amazon and then I bought a Pixel XL
If your warranty period has ended, try contacting your seller and see if they offer you any solution. I've read that because of the bootloop problem the warranty period has been extended to 30 months:
https://www.reddit.com/r/ProjectFi/comments/86kuvq/lg_extends_bootlooping_nexus_5x_warranty_to_30/ but I don't know if it applies to every retailer.

Carball0 said:
I bought my Nexus on Amazon and they kindly offered me a complete refund of the phone (it was under warranty, it had three months left).
I just opened a chat with Amazon support and they offered me the refund (completely free, I returned the phone to Amazon and then I bought a Pixel XL
If your warranty period has ended, try contacting your seller and see if they offer you any solution. I've read that because of the bootloop problem the warranty period has been extended to 30 months:
https://www.reddit.com/r/ProjectFi/comments/86kuvq/lg_extends_bootlooping_nexus_5x_warranty_to_30/ but I don't know if it applies to every retailer.
Click to expand...
Click to collapse
So, its Amazon who were kind NOT LG because I have had hard time with LG replacing phones.
Thanks for all information

Administr4tor said:
So, its Amazon who were kind NOT LG because I have had hard time with LG replacing phones.
Thanks for all information
Click to expand...
Click to collapse
But have you tried requesting an RMA on LG's webpage? I once did and they fixed it in one week for free before my overheating/bootloop problems started.
Even so, some people on XDA claims to have their NX5X repaired out of warranty with LG service because of the bootloop: https://forum.xda-developers.com/nexus-5x/help/lg-usa-doing-warranty-repairs-5x-t3687497