Hi, I picked up this phone through a private sale and, while it works fine, I noticed a couple of things during boot up. This first flashed on the screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then it went away and the following flashed on the screen:
Then it went to the main screen. Does this mean that something has been loaded onto the phone? What should I do to get it back to factory?
Thanks in advance.
vik123 said:
Hi, I picked up this phone through a private sale and, while it works fine, I noticed a couple of things during boot up. This first flashed on the screen:
Then it went away and the following flashed on the screen:
Then it went to the main screen. Does this mean that something has been loaded onto the phone? What should I do to get it back to factory?
Thanks in advance.
Click to expand...
Click to collapse
The first screen indicates the bootloader is unlocked.
The second means you are not stock but running a custom ROM.
Back to stock -> https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Thank you for the link. I checked it but I am not sure which file to download. Sorry, I am not very familiar with all of this and I am nervous about bricking my phone.
vik123 said:
Thank you for the link. I checked it but I am not sure which file to download. Sorry, I am not very familiar with all of this and I am nervous about bricking my phone.
Click to expand...
Click to collapse
Plug your phone into your PC using a good USB 3.0 cable after you reboot into the bootloader (do this by holding down volume down and power button at once. Also, use a type a to c cable, the essential phone stock USB c to c cable doesn't work that well for flashing stuff).
Then install the drivers for this phone from here on a windows system: https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
Then install minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=745425885120698566
Then, download the latest back to stock zip from here:
https://www.androidfilehost.com/?fid=745425885120698566
Unzip into the folder you installed minimal adb and fastboot into, and then open minimal adb and fastboot. In the command window that pops up, type "flash-all.bat && fastboot -w" and then hit enter. This will reflash all the stock partitions and wipe all data.
After you get the stock essential phone firmware booting, you can reboot into the bootloader and run "fastboot -w" and then "fastboot flashing lock" to relock the boatloader if you plan on keeping the stock unmodified firmware.
Credit goes to @aer0zer0 for the dump of the latest firmware.
Thank you so much. I followed the instructions and, while there were some nervous moments, managed to get it back to stock.
I can't believe the previous owner was such a jerk. I always return phones to full stock and relock the bootloader if I plan to sell a phone.
vik123 said:
Thank you so much. I followed the instructions and, while there were some nervous moments, managed to get it back to stock.
Click to expand...
Click to collapse
Hey no problem, always glad to help, especially since the situation you were in was caused by the previous owner not caring to flash stock and relock the bootloader before he sold you the phone. Seems like a careless thing to do, especially since he could've sold the phone to someone who wouldn't be tech savvy enough to restore stock.
The seller was really nice so I have a hard time calling him a jerk, but yeah, it was a careless thing to do. If it wasn't for this community I would probably have been screwed.
Thanks again everybody.
Related
Hi All,
if you want an easy way to reset to stock, this is it. Works like a dream, for that squeeky clean, out of the packet install feeling.
This method uses a full 38R factory image from cyanogenmod.
I take no glory for this as our hero @MooDeeY has done the hard work.
You can find the original cyanogenmod files here
http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip
MD5: 01e7fc376c13614d38f5c4201310a1bb
http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-boot-debuggable.img
MD5: 88209189b99ffb7a6bf2534c3b03ab80
No ota baggage here!
"Step 1: Download full XNPH38R rom from here, with adb files & extract it.
https://mega.co.nz/#!NtUxwbBQ!YyOIreiqfJKCC6ZKNwlxi5ubskTLSGKH-DwR39hF_IM
Step 2: Make sure that your phone isn't connected to your PC via USB, because its some times prevent phone from entering fastboot mode correctly.
Step 3: Press VOL+ & Power Button. until you see Fastboot logo. it should be like this picture.
{
"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"
}
Note: Some times it ask to confirm if it's your first time to unlock it if you came from Color OS version.
you can use volume buttons to choose between menus and choose yes & Power button for confirm.
Step 4: Connect your phone to pc.
Step 5: In folder that you downloaded in first step you will find a file called Bootloader Unlock just press it & press any key on your keyboard to begin unlock your boot loader.
Step 6: Your phone will restart after unlock. Power it off again & Do Steps 2,3,4 again.
WHY I SHOULD USE THIS WAY !!
- if you have chinese version (Color OS) & want to make it 100% Original cyanogen.
- if you device is bricked or boot loop and can't make it work again.
- if you facing errors after OTA update.
- if your version is too old & want to install latest one without install any previous update.
- if you facing wi-fi issue or connection problem.
** this way install a complete rom from A-Z including stock recovery, modem, boot image, etc.....
Step 7: You will Notice that there is others two files in folder:
Install Rom 16GB = for 16gb phone.
Install Rom 64GB = for 64gb phone.
just open it, press any key, it will start installing new rom for you & lock your bootloader again.
Notice: When downloading using google chrome, maybe a warning message appears to you, this because folder contain .bat files. it's completely safe."
I have been running this since about 10:30 ths morning and it has been problem free. I also got the best antutu score I ever got for this rom on the oneplus with this method, so its cool in my book. I also noticed a big reduction in battery usage, but theres no stats behind this claim.
One last point, this does use the latest images. Its just that cyanogenmod have not updated their website yet.
Why lock the bootloader on the end?
Finally, there's some legit 38R factory images! Why do they still have 33R on https://cyngn.com/products/oneplusone? Thanks for the link! :laugh: :good:
Schrotty35 said:
Why lock the bootloader on the end?
Click to expand...
Click to collapse
Because it returns to stock. You can edit this out in the script if you want it left unlocked.
There's no need to relock the bootloader. In fact, in several cases locking the bootloader has resulted in not being able to unlock it again.
Transmitted via Bacon
the link in step one dosent work, could u put up the link again
thanks, i bricked my phone
I'm not an Android rooting noob (my rooting goes back to OG Moto Droid in late 2009) and I'm sure it's something ridiculously simple I'm missing but I can't get my bootloader to unlock. I've tried ADB/Fastboot, WUG's Nexus Root Toolkit, and Chevy's Android Job Box. Nothing works.
I got my 6P today, SIM'ed it up, booted up, logged in, enabled USB debugging, installed the drivers, and let it update. When I opened WUG's NRT, I saw that I had an Android build one step later than the NRT. Mine's MD80BL and K is the latest in the NRT. I thought that shouldn't be a problem and selected the "any build" option with the Nexus 6P. I went through the installing drivers process and can access the file structure of the phone through W10.
I then went to the unlock bootloader option, clicked through the prompts until the phone rebooted into the bootloader and clicked the OK button to unlock the bootloader. About two seconds later a window popped up on my desktop telling me my bootloader was unlocked, my data was wiped, and I would have to go through the setup process on the phone. Excellent, except my phone booted right back to my stock homepage. I tried again with the same result.
I then tried it manually using ADB/Fastboot. The "fastboot devices" showed a connected device which I assume is my 6P since I have nothing else Android connected. When I type in "fastboot flashing unlock" I get all the fastboot commands/options as if I typed an unknown command. "Fastboot oem unlock" didn't work either. I went and downloaded the latest SDK and retried everything with the same result.
Here's my Build Number.
{
"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"
}
Here's what I get when I try to use fastboot to unlock the bootloader.
Any help will be much appreciated. I expect I'm going to feel stupid when my mistake is pointed out but I'm here to learn.
Upgrade your adb/flashboot setup. Probably too old.
You must allow the option to unlock, then go to fastboot, the run the command, with an updated version of fastboot command.
Ah, I see. The SDK Manager is not installing into my SDK directory. I'll copy/paste, retry, and report back. Thank you!
Now I get this message that unlocking the bootloader isn't allowed.
Narsil007 said:
Now I get this message that unlocking the bootloader isn't allowed.
Click to expand...
Click to collapse
Go to developer options & turn on the option that says enable bootloader unlock and retry.
Ha! I do feel stupid.
Thank you very much!!
You are very welcome!!!
Hello there.
I am writing because I need your help on unbricking my Nexus 7 3G (2012). Yesterday night I was trying to upgrade it from 5.1.0 to 5.1.1 (from the OTA) and I couldn't because I had an error produced by Stickmount. It changed a file on system/bin which I tried to push manually (following some thread's intructions on XDA) and it didn't work, showing error Status 7 (unexpected content on file debuggerd).
Because of that, I decided to flash the 5.1.1 system image using Nexus Toolkit. I set it up so it'd download and install it automatically (using the "Flash stock + Unroot" option). Everything went okay and started the flashing process until the command prop window force closed mid flash, thing that never happened to me before (as I had tried many times flashing from zero my N7 before).
I tried to start the Toolkit again and the command prop window says it flashes bootloader and radio img's successfully, but then a line of code appears and the cmd window force closes again (it says "No se esperaba ( en este momento" or roughly translated as "The ( was not expected at this moment" into English) and my N7 turns off.
Next, I try to turn it on and it shows the Google logo and a green arrow saying "start". I press it and the N7 reboots to the same screen, saying "booting failed" at the top of the screen. If I choose recovery, the same thing 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"
}
I just can make it to boot to bootloader mode but I cannot flash the firmw (even when this mode must be selected in order to the Toolkit to start flashing). It shows the same line of unexpected code as above.
I tried pushing the files manually using ADB and I cannot may it work either.
What can I do to solve this? I've read that as long as you can get to bootloader mode you can unbrick a device.
I hope you could help me out. Thanks in advance.
Anyone?
Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!
wombat3 said:
Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!
Click to expand...
Click to collapse
Thanks wombat. Actually, the N7 is listed under adb devices. It starts the flashing process but ends automatically without finishing the installation.
Happened when I was updating twrp:
I downloaded the .img from their website, booted into my older version of twrp, went to flashing pressed the butting in the bottom right corner, selected the file and selected 'recovery'
Said it was successful, so I rebooted, then it wouldn't do anything anymore except for fastboot.
1. Can't boot into recovery
2. Can't boot normally
3. USB debugging disabled
4. oem locked
Only thing I can enter is fastboot.
I followed this guide, but no luck on my end.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
passion8059 said:
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
Click to expand...
Click to collapse
It's no use because oem is locked. That means I can't flash anything.
toolbox should still help you unlock bootloader again
Just use the Qualcomm factory restore image to return the phone to original shape of things.
passion8059 said:
toolbox should still help you unlock bootloader again
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"
}
pitrus- said:
Just use the Qualcomm factory restore image to return the phone to original shape of things.
Click to expand...
Click to collapse
I have no idea how I would do this without being able to flash anything.
Do you mean that the Qualcomm download program also crashes like fastboot? Sounds like you either have some problems with your windows installation or perhaps you haven't searched for and downloaded the Qualcomm restore if your still trying to flash the ordinary way instead of the emergency way.
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Theevilsocks said:
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Click to expand...
Click to collapse
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Redjax said:
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Click to expand...
Click to collapse
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Theevilsocks said:
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Click to expand...
Click to collapse
Literally JUST finished with this guide, and my OP2 is alive again! I was going to come back and post. Thanks for the link.
Anyone trying to use this guide without success:
There's one very important step I somehow missed. You MUST disconnect your phone, hold the power button for ~15-20 seconds until it's off, and hold the Volume+ button, THEN plug it back in. Your computer will make the "device connected" sound, but the screen will stay black. THIS IS OK! That means you're in a special recovery, which is where you need to be for the tool.
I also installed the certificate file in the folder I downloaded, then rebooted (it did not work before a reboot, but did work after).
So, the steps:
1. Download the files, make sure your signature signing for drivers is off.
2. Install the trusted certificate, then the driver.
3. Reboot PC
4. Power off phone (hold power for 15-20 secs), hold volume+, then connect through USB (wait for device connected sound, screen on phone will still be black)
5. Run the tool (I ran as admin, not sure if that's required)
6. Weep with joy that you finally found a solution that works.
Howdy everyone...
OnePlus 7t Pro McLaren edition (International Edition **NOT T-MOBILE**)
Model: HD1913
Current Software Build: Oxygen OS 10.0.5.HD01AA (OTA update when I first unboxed).
I am having issues trying to return to stock. I rooted the phone with a combination of a couple guides found here (https://forum.xda-developers.com/7t-pro/how-to/10-0-3-patched-boot-image-oneplus-7t-pro-t3986351 and . I noticed after doing that I was missing the stock Oxygen apps and my build information was missing data. Not a huge deal, but I need to wipe the phone and start from scratch anyway, for other reasons. I decided to go back to stock if I have to redo everything anywhere.
First thing I tried, I got the stock firmwares (https://forum.xda-developers.com/7t-pro/how-to/oneplus-7t-pro-repo-oxygen-os-builds-t4003455). And this is where my issues started. My software build is weird... I have the HD1913, however my software build is HD01AA. Per that post, I should have HD01BA. I grabbed both of them for giggles, put them on my storage and booted into TWRP. Tried to flash the HD01AA (since that was what I have now), and it failed. Tried the other one, same issue. I'm getting a bunch of errors while trying to mount the system ("System unable to mount: invalid argument").
Second thing I tried, was to use the built in software update that OnePlus says to use (through the system update). It wouldn't install them (surprise).
Third attempt... Using the MsmDownloadTool (https://forum.xda-developers.com/7t-pro/how-to/op7tpro-unbrick-tool-to-restore-device-t4002909) I downloaded both versions cause I don't know which to use, and followed the instructions to get the phone into the mode. Turn the phone off, hold the vol up button and plug the cable in (very simple). It shows up connected in the software. Exactly 5 seconds later, the phone reboots and boots normally... I repeat this process aprox. 2.3 million more times. It does not matter what USB-C cable I use, the port on my computer, or how long I hold the buttons. The phone will boot into the download mode (or whatever it's called) show up as connected in MsmDownload and then reboot.
The phone works. I am still able to boot it up.... All I want to do is get this phone back to stock. I don't HAVE to, but now that it's fighting me, I have to beat it...
imgur.com/a/KhBGwao
{
"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"
}
Okay - After sacrificing an iPhone to the Android God, I got it.
Instead of using the button combination to get into EDL Mode, I found an article that gave an adb command (adb reboot edl) to get to it. It did not reboot this time, and I was able to flash HD01BA to it, which matches what the phone should have...