Hi all,
so after I cracked my Screen I send my device to a service provicer to repair it. The device is back and the display is fine again.
Though there are certain concers on which I'd need advice. Service provider did not react to my E-Mail yet.
So my Style was bootloader unlocked before and had TWRP installed. Though never rooted. Now that the device is back, it seems that the bootloader is locked again and when I boot into Fastboot I see two entries which concern me:
1.)
AP Fastboot Flash Mode (Not Secure)
(in red)
2.)
Device is ENGINEERING
(in yellow)
As well, the IMEI number changed and my Storage doubled. 32 -> 64 gig (which is not bad though ). Not sure why that happened. Probably so much glue that they needed to exchange more.
Another consequence is, that I'm not able to unlock the bootloader again, which bothers me somewhat. I get the key from Motorola, but when I run the fastboot command it fails with a short display flash on the phone.
So, long story. Do you guys know if the two entries mentioned in Fastboot are problematic in some way? Are those keeping me from unlocking again? Can I fix those on my own if necessary?
Best regards
Simon
An Engineering Bootloader is supposed to be completely unlocked, even more so than regular "bootloader unlock" if the official Moto forums are to be believed, it cannot be changed to locked or unlocked (fails every time), but in the Moto G 3rd gen community here we have several users with an engineering bootloader status and they have very sporadic issues with ROMs. For example RR 5.7.2 works but 5.7.3 fails, CM13 older nightlies work but current ones fail, certain kernels work and others do not, it is very weird.
To my (limited) knowledge, this is the first Engineering bootloader seen on a X Style/Pure here, you are in uncharted waters so proceed with caution...
FYI... Due to the fact that several users have seen this in the Moto G community, and it's started showing up in the Moto X Pure community, I posted in the Lenovo forums for more information on this in this thread.
The response was quite clear from AlphaDog (Moto Sr Moderator):
The phones should not be showing Engineering. If you get a phone back this way, it was not flashed properly and needs to be reflashed - call customer service and make arrangements to have it reflashed.
Click to expand...
Click to collapse
If your storage doubled and IMEI changed, then one if two things happened. 1. They gave you another phone other than your own (very likely), or 2. They seriously borked it when they reinstalled the ROM (which would explain the ENGINEERING status).
aybarrap1 said:
If your storage doubled and IMEI changed, then one if two things happened. 1. They gave you another phone other than your own (very likely), or 2. They seriously borked it when they reinstalled the ROM (which would explain the ENGINEERING status).
Click to expand...
Click to collapse
Due to weird issues that Moto G have... I'm leaning towards #2, or both.
Sent from my Motorola XT1575 using XDA Labs
Thanks all for your responses. I'm very sorry for my late reply, gmail hid the subscription emails in some subfolder (=
So an indeed very weird issue. I can confirm that it is at least the original outer frame of my phone. I had one customized from Moto maker and it had some unique scratches So they probably f***** up installation / flash. I'll try to get back with that provider an see what they say about it.
The first response on my question WHY that is, and that I'm now unable to unlock my bootloader was:
"Why are you booting Fastboot instead of normal? And you loose warranty if you unlock!"
...which of course is neither an answer to one of my questions nor helpful in any way.
I also had sent my phone in for repair a few months ago (screen stopped responding to touch, they wouldn't fix it because root, replaced myself, very frustrating ordeal) and have a similar issue.
I don't have the same colored entries as you, but every single time I boot now it goes directly to the bootloader instead of starting up normally. This includes when I reboot while using the phone, as well as when specifically using the advanced reboot menu to go into recovery which basically makes the whole menu pointless.
Very annoying problem when you have to wait for the bootloader to startup and then press the button to get it to start.
Anyone have any ideas on how to fix it?
Sent from my XT1575 using XDA-Developers mobile app
black_valor said:
I also had sent my phone in for repair a few months ago (screen stopped responding to touch, they wouldn't fix it because root, replaced myself, very frustrating ordeal) and have a similar issue.
I don't have the same colored entries as you, but every single time I boot now it goes directly to the bootloader instead of starting up normally. This includes when I reboot while using the phone, as well as when specifically using the advanced reboot menu to go into recovery which basically makes the whole menu pointless.
Very annoying problem when you have to wait for the bootloader to startup and then press the button to get it to start.
Anyone have any ideas on how to fix it?
Click to expand...
Click to collapse
fastboot oem fb_mode_clear
Sent from my Motorola XT1575 using XDA Labs
hdyim said:
Hi all,
so after I cracked my Screen I send my device to a service provicer to repair it. The device is back and the display is fine again.
Though there are certain concers on which I'd need advice. Service provider did not react to my E-Mail yet.
So my Style was bootloader unlocked before and had TWRP installed. Though never rooted. Now that the device is back, it seems that the bootloader is locked again and when I boot into Fastboot I see two entries which concern me:
1.)
AP Fastboot Flash Mode (Not Secure)
(in red)
2.)
Device is ENGINEERING
(in yellow)
As well, the IMEI number changed and my Storage doubled. 32 -> 64 gig (which is not bad though ). Not sure why that happened. Probably so much glue that they needed to exchange more.
Another consequence is, that I'm not able to unlock the bootloader again, which bothers me somewhat. I get the key from Motorola, but when I run the fastboot command it fails with a short display flash on the phone.
So, long story. Do you guys know if the two entries mentioned in Fastboot are problematic in some way? Are those keeping me from unlocking again? Can I fix those on my own if necessary?
Best regards
Simon
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"
}
The two entries never gave me any problems I also have an engineering bootloader.
Sent from my XT1572 using XDA-Developers mobile app
[email protected] said:
The two entries never gave me any problems I also have an engineering bootloader.
Click to expand...
Click to collapse
It doesn't give you an problems because your still stock. Moto has officially said this shouldn't happen and anyone with this should contact customer support to get it flashed correctly.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
It doesn't give you an problems because your still stock. Moto has officially said this shouldn't happen and anyone with this should contact customer support to get it flashed correctly.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
So then for me no need to worry.. Not planning to flash anything other then stock and as long it doesn't give any problems with rooting and flashing some mods I won't return it ...
Sent from my XT1572 using XDA-Developers mobile app
Related
So, I don't mean to start a panic for the remaining Atrix faithful here, but it seems like Motorola has started to block the ability to flash SBF's, including the pudding/IHOP files, on New and replacement Atrix phones. I've been in discussions with at least three recipients of replacement devices over the last three days that all have the same issue.
Anytime any SBF file is flashed to the device it fails with the error SFV:106:1:2 Unable to reenumerate device (or something similar). It does not put you into fastboot or give you the options it used to, you simply have to battery pull and the phone boots normally as if nothing ever happened. Even the current version SBF for AT&T (4.5.141) will not flash to the phone; it ends in the same error.
Without being able to flash ANY SBFs, that means the bootloader on these new phones remains locked down for the moment. I know we have lost many of our original developers that worked to try to unlock the bootloader the first time, but I also know we have many talented devs currently with us.
Is there anyone able to provide insight as to what might have been changed by Motorola and how we might be able to overcome it?
Here are links to my discussions with them, as well as another post I just found that is similar from a Bell user:
http://www.atrixforums.com/forum/showthread.php?p=107507
http://forum.xda-developers.com/showthread.php?p=25167191 (not sure if same situation, sounds possibly similar)
Sent from my MB860 using Tapatalk 2
Can anyone confirm this has happened to them? Motorola will lose alot of loyal customers, myself included, if they pull this bull.
yes it is true. i got my atrix today, i sent it in and i tried to unlock it right away but that proved to be impossible. if you follow those links, i have the exact same symptoms.
If anyone who is experiencing this can run some tests for samcripp, it looks like he's willing to help where he can. See this post here: http://www.atrixforums.com/forum/motorola-atrix-hacks/3331-tut-unlocking-bootloader-installing-custom-roms-63.html#post108017
Thanks!
That is so lame! This was my first Motorola smartphone and I have a feeling it will be my last.
Sent from my MB860 using xda premium
Just use the automated boot loader unlock it worked for my friend
Sent from my MB860 using XDA
kufusoto said:
Just use the automated boot loader unlock it worked for my friend
Sent from my MB860 using XDA
Click to expand...
Click to collapse
So far, that has failed with the same result for the two users that have tried it under these conditions.
i replied on the other forum
kufusoto said:
Just use the automated boot loader unlock it worked for my friend
Sent from my MB860 using XDA
Click to expand...
Click to collapse
did he ever send it into moto for any repairs?
Unable to unlock BL
I have had my Atrix 4G for almost 1 year. It was purchased as a refurb directly from AT&T. It came with Froyo on it & I patiently waited for and applied the OTA to 2.3.4 and 2.3.6. I was able to successfully root it but it will not give me the Unique ID when I run "fastboot oem unlock". It says:
C:\fastboot>fastboot oem unlock
...
(bootloader) OEM unlock is not implemented
OKAY [ 0.001s]
finished. total time: 0.001s
I will get the FUSE and edit this post.
ReservedOdm: 10000000000030001000300000000
BKrenning said:
I have had my Atrix 4G for almost 1 year. It was purchased as a refurb directly from AT&T. It came with Froyo on it & I patiently waited for and applied the OTA to 2.3.4 and 2.3.6. I was able to successfully root it but it will not give me the Unique ID when I run "fastboot oem unlock". It says:
C:\fastboot>fastboot oem unlock
...
(bootloader) OEM unlock is not implemented
OKAY [ 0.001s]
finished. total time: 0.001s
I will get the FUSE and edit this post.
Click to expand...
Click to collapse
You need to flash the "pudding" SBF unlocker file before using the fastboot commands. See the Unlock/IHOP sticky post at the top of the Development section.
Sent from my MB860 using Tapatalk 2
{
"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"
}
this is what i get after trying the automatic unlock tool.
it says unlocked but its not. its not rooted either. what did you use to root? like ^^^ it never showed my unique ID and just hung there.
thegogetter- said:
this is what i get after trying the automatic unlock tool.
it says unlocked but its not. its not rooted either. what did you use to root? like ^^^ it never showed my unique ID and just hung there.
Click to expand...
Click to collapse
how is it not unlocked, if it says unlocked and starts fastboot? just fastboot flash romracers recovery onto it and thats it, than you can flash custom roms.
das8nt said:
So, I don't mean to start a panic for the remaining Atrix faithful here, but it seems like Motorola has started to block the ability to flash SBF's, including the pudding/IHOP files, on New and replacement Atrix phones. I've been in discussions with at least three recipients of replacement devices over the last three days that all have the same issue.
Anytime any SBF file is flashed to the device it fails with the error SFV:106:1:2 Unable to reenumerate device (or something similar). It does not put you into fastboot or give you the options it used to, you simply have to battery pull and the phone boots normally as if nothing ever happened. Even the current version SBF for AT&T (4.5.141) will not flash to the phone; it ends in the same error.
Without being able to flash ANY SBFs, that means the bootloader on these new phones remains locked down for the moment. I know we have lost many of our original developers that worked to try to unlock the bootloader the first time, but I also know we have many talented devs currently with us.
Is there anyone able to provide insight as to what might have been changed by Motorola and how we might be able to overcome it?
Here are links to my discussions with them, as well as another post I just found that is similar from a Bell user:
http://www.atrixforums.com/forum/showthread.php?p=107507
http://forum.xda-developers.com/showthread.php?p=25167191 (not sure if same situation, sounds possibly similar)
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
I get that error when
1. I try to flash a SBF file not meant for my phone. (Yeah... Stupid move)
2. There is a hardware problem with my phone.
---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------
thegogetter- said:
this is what i get after trying the automatic unlock tool.
it says unlocked but its not. its not rooted either. what did you use to root? like ^^^ it never showed my unique ID and just hung there.
Click to expand...
Click to collapse
If it never showed your unique ID, your phone has been unlocked before.
crnkoj said:
how is it not unlocked, if it says unlocked and starts fastboot? just fastboot flash romracers recovery onto it and thats it, than you can flash custom roms.
Click to expand...
Click to collapse
It did not start at fastboot automatically, he made it start at fastboot. =D Funny what some people do...
When I try to flash a recovery it hangs on waiting on device and doesn't do anything. I tried that already. I don't have root either
das8nt said:
You need to flash the "pudding" SBF unlocker file before using the fastboot commands. See the Unlock/IHOP sticky post at the top of the Development section.
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
That's what I figured. I was hoping someone had come up with an easier route by now or at least figured out what was in the OTA that is blocking the phone from giving out it's unique id.
There is a Samsung Note on CL calling my name. Maybe I'll answer it--LOL.
Thank you for your help!
thegogetter- said:
When I try to flash a recovery it hangs on waiting on device and doesn't do anything. I tried that already. I don't have root either
Click to expand...
Click to collapse
Have you installed the drivers for your phone? If you're trying to flash a recovery, you should be unlocked and to unlock your phone, you would need the drivers.
Off the top of my head, the error from rsd seems like one you get when you try to use a ramloader from ATT with a Bell phone. That is why there were radio sbfs for Bell and for ATT separately.
You have to realise that the sbf files with the unlockable bootloaders are mods of existing sbf files and may simply be out of date with regard to the new phones. You would need a new sbf file to hack in the replacement bootloader. So what you are really looking for is another unlockable bootloader in the wild as part of a sbf that can be stripped down to just the bootloader part.
Or Motorola could just take it's **** out of it's ***.
Cheers!
i sent my atrix to get fixed in the last 3 weeks and i got it back, the bootloader was still unlocked but it needed to be "reminded" of it if you will. it had stock 4.5.151 on it and when it booted up there was no "unlocked" text and i couldn't flash a recovery, so i all i had to do was SBF to 2.3.4 and flash the trololol.sbf and it "reminded" my phone that it was unlocked. during the flashing process it rebooted and showed up as "unlocked" in the corner without having to re "fastboot oem unlock" it and i could flash a recover from there. using the latest RSDLite and Windows XP via Bootcamp with an AT&T Atrix and all AT&T files.
i got it to work after using a different computer and loading fresh drivers. thanks guys.
Download and Install LG United Mobile Driver
Download and Install LG Mobile Support Tool
Boot your phone into download mode:
Put your G2 into download mode by switching it off, hold the Volume up button and insert the usb cable into the phone; wait for the drivers to finish loading if doing it for the first time.
Start the LG Mobile Support Tool and click on Options -> Upgrade Recovery
{
"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"
}
It should now download the firmware (about 2gb) and flash it - this may take some time.
This is needed if you stuck in a bootloop after the flash is done:
Factory reset (this wipe your data and sdcard):
1. Turn the phone off.
2. Press and hold the Power and Volume down button.
3. When the LG logo pops up let go for a second and press the combo again.
4. You'll be prompted to press the Power button 3 times to wipe the device.
I would hate to have to use this, but wow what a good find. Thanks for contributing.
Sent from my LG-D800 using Tapatalk 4
Just got my g2. About to root install twrp etc. This is exactly what I was looking for. Thanks for posting.
Sent from my LG-D801 using XDA Premium 4 mobile app
For anyone putting in dashes with the imei number, dont it wont work with em.
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
I used this method last night and it didnt mess with the storage at all. They don't even have a 16gb G2 so who knows. Also are you sure you are not mistaken cause this method doesnt wipe data.
x714x said:
I used this method last night and it didnt mess with the storage at all. They don't even have a 16gb G2 so who knows. Also are you sure you are not mistaken cause this method doesnt wipe data.
Click to expand...
Click to collapse
I know it does'nt wipe data, but it reflashes recovery, and in my case something went wrong. But Lg DO sell D802 as a 16 gb model!
Can anyone using this method please post results. Just wondering if there is more success with this method as opposed to the other method. Thanks.
Saved my bacon today!
karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
I don't understand how could this be, you downloaded the specific firmware for your device (using your serial number)...
Can't you just try to flash it again ?
Noam23 said:
I don't understand how could this be, you downloaded the specific firmware for your device (using your serial number)...
Can't you just try to flash it again ?
Click to expand...
Click to collapse
I have reflashed it 5 times The problem was that it asked for some kind of password the first time (not the pin). So I did a factory reset. Now even TWRP says that my storage is 10.66 gb :/
karstensson said:
I have reflashed it 5 times The problem was that it asked for some kind of password the first time (not the pin). So I did a factory reset. Now even TWRP says that my storage is 10.66 gb :/
Click to expand...
Click to collapse
Which password exactly ? when ? in the process of flashing ? the OP mentions no stage in which you need to give password...
What are you going to do now ? your device is not rooted, so you can replace it under warranty, no ?
Noam23 said:
Which password exactly ? when ? in the process of flashing ? the OP mentions no stage in which you need to give password...
What are you going to do now ? your device is not rooted, so you can replace it under warranty, no ?
Click to expand...
Click to collapse
It did not say what the password was for, just asked for it. It came up after the phone had booted, but before i could see the lockscreen. I will wait a couple of weeks, to check if someone else gets the same problem, or if it is fixable. Otherwise i will hand it in on the warranty since there are not traces of root.
karstensson said:
It did not say what the password was for, just asked for it. It came up after the phone had booted, but before i could see the lockscreen. I will wait a couple of weeks, to check if someone else gets the same problem, or if it is fixable. Otherwise i will hand it in on the warranty since there are not traces of root.
Click to expand...
Click to collapse
Why should a password appear at that stage ???
If you went through all of the flash process successfully, booted successfully and only then did a factory reset (when you saw that password), I see no reason to blame the factory reset that you did. This is something to do with the flash process. Maybe this is kind of a punishment that LG unleash on those who use this process ? seriously, why on earth would anyone try to flash his LG2, if it wasn't to get rid of root ? I also don't understand how the password went away after you did hard-reset, since the device was "hard-reset" when you did that flash. You said that you re-flashed about 5 times, did that password appear after each of those 5 times ?
karstensson said:
Just wanted to notify that this method made my 32gb D802 a 16 gb one!
Click to expand...
Click to collapse
Same issue here.
I also got the question after I used the software to enter my encryptionkey. Wich I didnt have.
So I had to hardreset from the recoverymenu (volume down + pwr), then I suddenly had 10.77GB left instead of 26.77GB or something similar.
Annoys me pretty darn much at the time beeing!
I did use my IMEI, not my serialnumber and model. I'll try to use the serial and model this time around, and see if there are any differences at all in doing so.
And yes, it does say 32GB on the back. So we're not mistaken it for a 16GB-model
And it does say that the model is the 32GB when I check the hardware-info on the android itself.
Maybe this has something to do with me using the adbcommand for mounting storage incorrectly?
I thought however it would be reset when I used the LG Mobile Support Tool to hardreset everything though.
Will this work with the AT&T model D800?
Also does this remove all traces of root to the point where you get your warranty back?
what was the solution to this...
Does this work with the TMO versions?
The windows application keeps getting a Windows error and closing shortly after the process begins. Any tips?
I would prob stay away from this if i was anyone else....Because it must be messing people phones up and changing the storage capacity
So I bougjt an LG G2 (international - D802) and I f***ed it up a bit.... Sadly it can not be fixed for some reason. It is stuck in fast boot mode, and I can not boot into recovery or download mode.... So I bought another LG G2 but this time an verizon. (32gb) And I'm planning on combining the 2 together because the verizon has an cracked screen and an not reacting touchscreen.So I want to replace the verizon's screen with an international one. So is there something I need to know? I just really want my g2 to work again..... It has been broken for about 3 months now....
Please help, because I don't want to break another g2
That isn't so nice that you couldnt use it for 3 months. I dont know what you should watch on since so far as i know only that there are 2 display variants lgd/jdi but there isnt an different digitizer on the phone so far as i know. The only thing that would be maybe is that the verizon logo is missing on the front if the original had one. To be sure that there aren't differences google about it and google the displays and see if you can see a difference on the display's. With that i mean differences with the cables, the parts on the digitizer/display and the pcb(greenish thing most time where the parts are on. I can't really find it out for you since i need to sleep now because its 3:02 AM, I hope that i helped you and that you can fix your problem. If i will remember it then i will make an research on it and i will post it here if you couldnt find if its possible or not. ?
wulsic said:
That isn't so nice that you couldnt use it for 3 months. I dont know what you should watch on since so far as i know only that there are 2 display variants lgd/jdi but there isnt an different digitizer on the phone so far as i know. The only thing that would be maybe is that the verizon logo is missing on the front if the original had one. To be sure that there aren't differences google about it and google the displays and see if you can see a difference on the display's. With that i mean differences with the cables, the parts on the digitizer/display and the pcb(greenish thing most time where the parts are on. I can't really find it out for you since i need to sleep now because its 3:02 AM, I hope that i helped you and that you can fix your problem. If i will remember it then i will make an research on it and i will post it here if you couldnt find if its possible or not. ?
Click to expand...
Click to collapse
Yeah, I had already googled it and I didn't found any weird corners or parts at the display that could be a problem. And I actually don't like the verizon logo at the front haha.
I will keep you posted if it works or not! Hope you had a good night rest =p
FritsPikee said:
Yeah, I had already googled it and I didn't found any weird corners or parts at the display that could be a problem. And I actually don't like the verizon logo at the front haha.
I will keep you posted if it works or not! Hope you had a good night rest =p
Click to expand...
Click to collapse
Ahh alright but i don't think its compatible those two models with the display sorry for late reaction since I can't really see where i replied before easy on desktop and thanks yes i had a good night rest till i woke up...
Compare the 2 Pictures you can also magnify it, the only difference i saw was in the small cable up in the pictures so far as i know that part is for the touchscreen to control the above half i believe. So the only difference between these 2 are the touchscreen i think, you can open and try it but i don't think it will work. Maybe you can describe more about your fastboot problem and we could fix your device?
http://www.etradesupply.com/lg-g2-vs980-lcd-screen-and-digitizer-assembly.html
http://www.etradesupply.com/lg-g2-d802-lcd-screen-and-digitizer-assembly-black-22089.html
{
"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"
}
@FritsPikee try these things to get out of fastboot mode:
The first one which is also suggested by me post #132:http://forum.xda-developers.com/showthread.php?t=2680150&page=14
Btw, Download the stock img files from here if you have d802: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware
Just execute all those things but i think that you can use TWRP instead of the original recovery or some other kind of recovery But i am not sure
so do that recovery thing at your own risk :/
or if that doesn't work try this one but its not really well explained.: see fix 4: http://forum.xda-developers.com/showthread.php?t=2694530
If you have some other fastboot mode problem then reply again to this thread or add me on Facebook:Wulsic then i can also help you maybe with it.
wulsic said:
Ahh alright but i don't think its compatible those two models with the display sorry for late reaction since I can't really see where i replied before easy on desktop and thanks yes i had a good night rest till i woke up...
Compare the 2 Pictures you can also magnify it, the only difference i saw was in the small cable up in the pictures so far as i know that part is for the touchscreen to control the above half i believe. So the only difference between these 2 are the touchscreen i think, you can open and try it but i don't think it will work. Maybe you can describe more about your fastboot problem and we could fix your device?
http://www.etradesupply.com/lg-g2-vs980-lcd-screen-and-digitizer-assembly.html
http://www.etradesupply.com/lg-g2-d802-lcd-screen-and-digitizer-assembly-black-22089.html
@FritsPikee try these things to get out of fastboot mode:
The first one which is also suggested by me post #132:http://forum.xda-developers.com/showthread.php?t=2680150&page=14
Btw, Download the stock img files from here if you have d802: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware
Just execute all those things but i think that you can use TWRP instead of the original recovery or some other kind of recovery But i am not sure
so do that recovery thing at your own risk :/
or if that doesn't work try this one but its not really well explained.: see fix 4: http://forum.xda-developers.com/showthread.php?t=2694530
If you have some other fastboot mode problem then reply again to this thread or add me on Facebook:Wulsic then i can also help you maybe with it.
Click to expand...
Click to collapse
Sorry for the late reaction, but this is what happend;
I wanted to backup my whole system just in case something would go wrong. So I installed cwm and when I booted my phone in recovery mode it was giving me a 'secure boot error'. But I accidently made a backup with the cwm error (I thought it was still the original recovery but it wasn't) then iI installed twrp 2.7 for lg g2 and that worked just great =). I made my backup. But then there was an software update from android (not google play) so I clicked on the 'install update notification' and my phone turned of and back on. but it booted in twrp instead of the original recovery (duh!) I looked it up on internet and found a command line I had to fill in in the twrp menu (something with 'dd if=/' etc). that fixed the problem but still the update wasn't installed. So I installed my old recovery back (the backup I made but what wasn't the original recovery. I installed the cwm 'secure boot error" recovery back). After I click again on the 'install update notification' my phone went in a bootloop with the 'secure boot error'
then I followed the Instructions in this tread: http://forum.xda-developers.com/showthread.php?t=2582142 And I got it out of the secure boot error thingy, but than it got in the fastboot boot loop =( And that's the whole story ...
i hope you can go something with it! Again, sorry for the late reaction!
You mean lg logo then fastboot? If so then the kernel isnt good. And you gotta replace it :/
wulsic said:
You mean lg logo then fastboot? If so then the kernel isnt good. And you gotta replace it :/
Click to expand...
Click to collapse
Yeah, first the logo and then fastboot, and i tried this tread: http://forum.xda-developers.com/showthread.php?t=2477595
But it didn't worked =( (btw I live in the netherlands to!!)
@FritsPikee ahh okay, maybe its easier if we talk with facebook or something like that my facebook is facebook.com/wulsic1, skype hangouts etc is just wulsic because facebook got bugged when i changed my username.
Because if i will talk dutch to you then it is easier and english is the language you must speak here at xda so yeah. Do you still have custom recovery or is that also gone?
wulsic said:
@FritsPikee ahh okay, maybe its easier if we talk with facebook or something like that my facebook is facebook.com/wulsic1, skype hangouts etc is just wulsic because facebook got bugged when i changed my username.
Because if i will talk dutch to you then it is easier and english is the language you must speak here at xda so yeah. Do you still have custom recovery or is that also gone?
Click to expand...
Click to collapse
I've send you an skype request! But I need to go now, so I'll be back in about 2 hours
@FritsPikee alright i will try to help you then if i dont have to eat then.
Hey guys, would really need he help of the very well knowledgeable this this particular phone and the way it works as far as the modem software and hardware wise......
Issue: my modem will not come on, so I will get no service in ANY way, shape, or form no matter what I do.
Things I have tried: go into *#*#4636#*#* menu and attempted to turn on radio, the slider does move to turn it in, but nothing happens. If I leave this menu, and come back, that slider is ticked off. If I go to settings and go to mobile data area, it tells me to "turn off airplane mode" ITS NOT EVEN ON!!!
Brief history of device.....
Was working perfectly fine, had bootloader unlocked, had a custom ROM on it for like 5 or 6 months, no issues. Until one day, the bottom mic just stopped working. No one could hear me talk. Only top mic worked for recording video. Ordered the bottom daughter board that has the mic on eBay, it was the one for my phone, A2017u, no issues at all installing it. Pretty straight forward, I've repaired many phones in my day, this worked for like 1 month. Then I suddenly had software issues, random restarts, kept getting process error so frequently I could do anything on the phone....everything Google ND Android related processes kept crashing making phone inoperable. Decided to reflash the SAME ROM I had without formatting data, I've done before, just had to update system apps of course...bad move. Less crashing, but still crashed and stopped getting service. Only wifi worked. In light of all this....I decided to just EDL back to B21, or whatever the latest one is for my phone, did it through emergency download mode, because phone was inoperable. Everything flashed fine as far as the screen prompts. Phone booted, first took way longer then usual 5-10min, like 15-20. But it booted. I set up everything....STILL NO MODEM!!! I even though the daughter board was defective, emailed the eBay store, they sent me another one, kudos to this guy, he took care of me. Changed the board again, still no MODEM........the only difference I'm noticing is Everytime I boot up the phone, I get a black warning screen saying phone is not protected or something, with the word "START>" on the top right to press volume up or down, not sure which to enter a menu or do nothing and it will start normal. I've never had this before I flashed the EDL.
Any advice or help towards the right direction would be greatly appreciated. Thank you guys in advance.
Sent from my Moto Z (2) using Tapatalk
did you flashed your correct modem for your axon model?
Predatorhaze said:
did you flashed your correct modem for your axon model?
Click to expand...
Click to collapse
I believe it did, as i mentioned, i flashed the full edl package.....doesn't it include the modem??
kevace1 said:
I believe it did, as i mentioned, i flashed the full edl package.....doesn't it include the modem??
Click to expand...
Click to collapse
What model you have and what edl package you flashed? If you flashed China edl firmware you get China modem,USA edl firmware USA modem etc...you need to flash modem seperate
I got the same problem since yesterday. My device was away for a battery replacement some days ago. After I get it back everything was fine. Yesterday the modem stopped working. In my option I changed nothing. I just get no signal anymore. I'm still on 14.1 Nougat. I have tryed to flash the modem again, made a system, EFS, bootloader and twrp recovery but nothing worked so far. I also tryped to reset network settings and tryed another sim card..
Predatorhaze said:
What model you have and what edl package you flashed? If you flashed China edl firmware you get China modem,USA edl firmware USA modem etc...you need to flash modem seperate
Click to expand...
Click to collapse
I'm pretty sure I flashed the USA edl as I have the USA model. I know I need the USA one, not new to flashing things. But your saying I would have to flash the modem as well even after the full EDL flash?
Sent from my Moto Z (2) using Tapatalk
Here is the screenshot of the phone itself. I'm on it now that I'm home. So I guess I use the edl tool from DJ and flash the modem again is the consensus?
{
"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"
}
As you can see, I can tic the mobile radio on, which I did, but if I leave it and let come back it's ticked off ...
And in the second picture you see after I insert my sim car...it'll give a prompt of a voicemail I have, but I get no service.....
Sent from my ZTE A2017U using Tapatalk
Sorry, it didn't let me attach the screenshot from the phone in my previous edited post, told I didn't have permission to post attachments....lol
Sent from my ZTE A2017U using Tapatalk
kevace1 said:
Sorry, it didn't let me attach the screenshot from the phone in my previous edited post, told I didn't have permission to post attachments....lol
Click to expand...
Click to collapse
Using two neurons was enough for me to figure out that you flashed two different U packages, i.e. did nothing wrong. These packages WILL flash a modem, which is fine.
I don't think flashing a modem will automagically fix your issue, but it's worth trying. If you have TWRP, simply get a modem file from somewhere (for example the LOS threads, 14.1 has an old one but it works, also try 16.1's modem) which of course has to be for your model, and flash it. You can also extract the non-hlos.bin from an official zte update, change its extension to .img, then either flash via Fastboot (fastboot flash modem non-hlos.img) or via TWRP (install - install image - to Modem - select the file)
If nothing works.try wiping all partitions including vendor and reflash.Your modem is included in the USA edl firmware,
Predatorhaze said:
If nothing works.try wiping all partitions including vendor and reflash.Your modem is included in the USA edl firmware,
Click to expand...
Click to collapse
Doesn't doing a EDL flash formats all partitions? I do have twrp, that is the only other think I did after flashing the EDL. In any case, I agree to try the re-format everything and try the flash again...what would be the steps to do that correctly, so I don't brick the phone, though I know it seems it's pretty hard to permanently brick this phone, I prefer not to be the first loser to do it.....
Sent from my Moto Z (2) using Tapatalk
By the way, this is the black warning I get Everytime I boot my phone..........this started to occur after I flashed the EDL package..also wanted to add I never re-locked the bootloader to do the flash....could that have to do with my issue
Sent from my Moto Z (2) using Tapatalk
kevace1 said:
By the way, this is the black warning I get Everytime I boot my phone..........this started to occur after I flashed the EDL package..also wanted to add I never re-locked the bootloader to do the flash....could that have to do with my issue
Click to expand...
Click to collapse
That warning is completely normal. It appears if you have an unlocked bootloader. I have it myself. Not gonna remove it tho as its easier to get into recovery (by pressing volume buttons a menu appears on which recovery, fastboot etc can be selected)
kevace1 said:
By the way, this is the black warning I get Everytime I boot my phone..........this started to occur after I flashed the EDL package..also wanted to add I never re-locked the bootloader to do the flash....could that have to do with my issue
Click to expand...
Click to collapse
Never relock the bootloader... Makes zero sense, and you'll brick the phone if it is not fully stock.
and yeah, the 5 second screen is just normal
Choose an username... said:
Never relock the bootloader... Makes zero sense, and you'll brick the phone if it is not fully stock.
and yeah, the 5 second screen is just normal
Click to expand...
Click to collapse
I hear what your saying. But the weird thing is I never ever has this screen until I flashed the EDL. Obviously, I've unlocked the bootloader way before I started having issues with phone. And I never got this screen.... ever. What triggered it to start popping up now??
Sent from my Moto Z (2) using Tapatalk
kevace1 said:
I hear what your saying. But the weird thing is I never ever has this screen until I flashed the EDL. Obviously, I've unlocked the bootloader way before I started having issues with phone. And I never got this screen.... ever. What triggered it to start popping up now??
Click to expand...
Click to collapse
What rom did you use before?
Edit: nvm. I just read op again.
It was because of the custom rom you had flashed before that there was no warning screen (the rom probably contained a patch to remove it).
All stock roms have have this warning. So don't worry about that
GodOfPsychos said:
That warning is completely normal. It appears if you have an unlocked bootloader. I have it myself. Not gonna remove it tho as its easier to get into recovery (by pressing volume buttons a menu appears on which recovery, fastboot etc can be selected)
Click to expand...
Click to collapse
It appears he got a modified bootstack,,this screen does not proof the bootloader is unlocked.When you flash a edl stock firmware with these new bootstacks and your bootloader is locked,you still get this screen
Predatorhaze said:
It appears he got a modified bootstack,,this screen does not proof the bootloader is unlocked.When you flash a edl stock firmware with these new bootstacks and your bootloader is locked,you still get this screen
Click to expand...
Click to collapse
The lack of it doesn't prove that it is locked, which is not the same. While I have never heard about what you said of locked BL and stock firmware (shouldn't happen at all - are you sure you had the bl locked?) he said that he had unlocked the bootloader, and usually the unlocking packages for the G and U flash the modified aboot and fbop files that give you fastboot and get rid of the 5 sec screen. That's what happened. After flashing something else, those files were replaced and the screen appeared, nothing catastrophic
Can you link to whoever said that he got the screen with a locked bootloader? or was it you who had that happen?
Choose an username... said:
The lack of it doesn't prove that it is locked, which is not the same. While I have never heard about what you said of locked BL and stock firmware (shouldn't happen at all - are you sure you had the bl locked?) he said that he had unlocked the bootloader, and usually the unlocking packages for the G and U flash the modified aboot and fbop files that give you fastboot and get rid of the 5 sec screen. That's what happened. After flashing something else, those files were replaced and the screen appeared, nothing catastrophic
Can you link to whoever said that he got the screen with a locked bootloader? or was it you who had that happen?
Click to expand...
Click to collapse
i also flashed the edl package with locked bootloader,but now i remember it was the china edl.And that screen showed up(with locked bootloader).It should not happen with the corresponding model.My mistake,lol
Predatorhaze said:
If nothing works.try wiping all partitions including vendor and reflash.Your modem is included in the USA edl firmware,
Click to expand...
Click to collapse
what would be the best way to completely wipe all partitions? i thought going through EDL does all of this already??
{
"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"
}
Hi. i was curious about the DSU loader so i installed it and rebooted. But it started bootlooping then showed the "system is corrupt" message. After that it rebooted and only went into fastboot after that, Im a bit panicked since the phone is only a couple hours old and I forgot to unlock the bootloader. if anyone knows how to fix this itd be appreciated.
I did quite a lot of flashing and rooting and as far as I know, there should be an option withing fastboot to reboot to bootloader. But I am not aware of the Nothing recovery image.
When in bootloader, you can then unlock the device with fastboot commands via command line.
Have you tried any of that?
miris83 said:
I did quite a lot of flashing and rooting and as far as I know, there should be an option withing fastboot to reboot to bootloader. But I am not aware of the Nothing recovery image.
When in bootloader, you can then unlock the device with fastboot commands via command line.
Have you tried any of that?
Click to expand...
Click to collapse
sadly doesnt work since oem unlocking is off, and i cant access the os. it seems its in slot b right now, but i cant switch slots due to a locked bootloader.
any ideas would help
why use DSU?if you are stupid in this matter? say goodbye to the phone
Curiosity got the best of me. I used DSU cause I thought I would be able to keep it locked
Seaman228 said:
why use DSU?if you are stupid in this matter? say goodbye to the phone
Click to expand...
Click to collapse
Why do you trash the topic with anything but any attempt for help? Drop the keyboard and take a walk.
Someone had to say it
miris83 said:
Why do you trash the topic with anything but any attempt for help? Drop the keyboard and take a walk.
Click to expand...
Click to collapse
Trash? I told the truth, if you're crying I'm sorry
You really forgot rule 1 in android modding.
Unlock.
The.
****ing Bootloader.
Seaman228 said:
Trash? I told the truth, if you're crying I'm sorry
Click to expand...
Click to collapse
And even more trash ... You are a waste of time, man.
gordonsosig said:
View attachment 5711879Hi. i was curious about the DSU loader so i installed it and rebooted. But it started bootlooping then showed the "system is corrupt" message. After that it rebooted and only went into fastboot after that, Im a bit panicked since the phone is only a couple hours old and I forgot to unlock the bootloader. if anyone knows how to fix this itd be appreciated.
Click to expand...
Click to collapse
As I see it now, this might be your best bet at this point: https://forum.xda-developers.com/t/...t-centre-and-staff-14-september-2022.4492645/
The staff is pretty friendly. I already reported some bugs and it was just fine.
Use "fastboot getvar current-slot" to get your current slot then switch to the other slot with "fastboot --set-active=a" or "fastboot --set-active=b" I believe those commands work even with a locked bootloader.
Seaman228 said:
why use DSU?if you are stupid in this matter? say goodbye to the phone
Click to expand...
Click to collapse
it's Nothing's fault for screwing up their DSU implementation. On a locked bootloader it should either boot the DSU image (like Pixel), or reject it and boot back to normal system. In NO CIRCUMSTANCES it should BRICK the device like this
Google didn't mention the best way to install the Android 12 Beta on Pixel phones
DSU is the best way to install the Android 12 Beta release on Pixel phones, but Google totally neglected to mention it.
www.xda-developers.com
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
nguyenlucky said:
it's Nothing's fault for screwing up their DSU implementation. On a locked bootloader it should either boot the DSU image (like Pixel), or reject it and boot back to normal system. In NO CIRCUMSTANCES it should BRICK the device like this
Google didn't mention the best way to install the Android 12 Beta on Pixel phones
DSU is the best way to install the Android 12 Beta release on Pixel phones, but Google totally neglected to mention it.
www.xda-developers.com
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
Click to expand...
Click to collapse
sadly i live in switzerland so there isnt any service center i can get to. so either we find a solution or the phone collects dust on my shelf
nguyenlucky said:
As you have locked bootloader and no OEM unlock, it's essentially a hard brick since no MSM tool is available. Take it to the service center ASAP.
Click to expand...
Click to collapse
On the other hand the MSM tool may exist only as an internal tool which they might provide on request in such situations. As you pointed out in the article, they messed up the implementation. To be honest, I wonder how this may have happened in the first place - to boot into mode which should not be available with the booloader unlocked. And given the company has a past link with OnePlus and OnePlus does have an MSM tool ...
Unless @gordonsosig asks the support, he will not know.
Have a look here : https://forum.xda-developers.com/t/nothing-phone-1-flashing-utilities.4478457/
And there : https://forum.xda-developers.com/t/help-to-developers.4484061/
I also went into this issue with disabled OEM Unlock. My phone was repaired for free in the customer care because I had an warranty. I wrote an email about this issue to the producer because I think it should not be possible to hard brick the phone by playing with developer options. I hope they will fix it.
And I think moderator should pin this thread to be always on top, because people should see the varning, this can save users from bricking their phones.
kuba3351 said:
I also went into this issue with disabled OEM Unlock. My phone was repaired for free in the customer care because I had an warranty. I wrote an email about this issue to the producer because I think it should not be possible to hard brick the phone by playing with developer options. I hope they will fix it.
Click to expand...
Click to collapse
where do i send it? is it in person or mail in? any help is appreciated
I returned my phone into the place where I buy it, and they sent it to the customer care. There is an official website: https://pl.nothing.tech/ so I think you can find an information about how to send your phone or use an Contact us link and I think they will help you.
kuba3351 said:
I returned my phone into the place where I buy it, and they sent it to the customer care. There is an official website: https://pl.nothing.tech/ so I think you can find an information about how to send your phone or use an Contact us link and I think they will help you.
Click to expand...
Click to collapse
guess im ****ed. already contacted them but i bought the phone from ebay so they said just contact ebay