Database Users

[Tutorial] Unbrick bricked (unlocked bootloader) Phones

This tutorial will fix your unlocked Phones which got bricked through OTA update and are dead now!
I have Xperia neo v i unlocked its bootloader unofficially from s1tools,
When i updated the phone through wifi, it wont start then i made this
trick to unbrick the phone..!​
Step 1: Download s1tools here and extract.
Step 2: Remove your phones battery and reinsert it.
Step 3:Open s1tool and click on identify now connect your phone and follow the instruction
(For NEO V press and hold back button and u will see the following message as shown in screenshot)
{
"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"
}
Step 4: When u got above message click on 'RESTORE' when the restore process completes remove the cable and reinsert your phone battery.
Step 5: Downlaod flashtool here and 4.0.2.A.0.62 Firmware here and extract it.
(Note:for flashtool tutorial click here)
Step 6: Flash the .tft file according to the tutorial and restart your phone, your phone will definitely start
(Note: After restoring, your phones bootloader will be locked, again u have to unlock to install custom kernels or roms.)

Weird the only thing that shows up are the two boxes, (left,right). as far as buttons go you only get "Do Job, stop, quit". Looks nothing like what you have posted..

the flashtools is aborting.. stating to turn on usbdebugging and unknown sources

Simpler...
FXP said:
Hi,
This will fix your unlocked Phones which got bricked through OTA update and are dead now!
Please download this package:
http://www.multiupload.com/Q103V01CV1
Let it extract to a destination of your choice.
After that run Flashtool.exe.
Now hit the button FLASH and select the package which is included.
Follow the steps and connect your phone in flashmode. This is the same mode Pc Companion and SEUS uses to flash your phone to newer firmare (Indicated by green LED), if you got BLUE LED you are in the wrong mode!
Flashtool will now detect your phone and start the repair.
After all is done your phone should be up and running again.
ADVICE:
PLEASE DO NOT ACCEPT ANY OTA'S ! If you receive a OTA message just decline, if you accept it you will end with a brick AGAIN! So please do NOT accept them until SonyEricsson provides a OTA solution for unlocked Bootloaders!
Best Regards
Team FreeXperia
Click to expand...
Click to collapse

S1tools no longer there
vikramam said:
This tutorial will fix your unlocked Phones which got bricked through OTA update and are dead now!
I have Xperia neo v i unlocked its bootloader unofficially from s1tools,
When i updated the phone through wifi, it wont start then i made this
trick to unbrick the phone..!​
Step 1: Download s1tools here and extract.
Click to expand...
Click to collapse
Hi vikramam,
Could you upload the S1tools again please.
I tried to download, but were not there anymore.
Thanks.

[OTA] 5.07.651.1 Update (ZIP DOWNLOAD INSIDE!)

I only started a new thread on this because I figure the post I made in the other thread with the file might end up getting lost.
This OTA is interesting. Though it includes no firmware update (i.e. radio, PRI, NV, WiMax), it does include Sprint's new "Connections Optimizer" which is supposed to help with battery.
Something else it includes (which I found unexpectedly) is the patent-abiding new App Associations screen (anyone that pre-ordered an EVO 4G LTE knows all about this). So it does appear that HTC is rolling out an update to all devices to "correct" this issue.
First off, keep in mind this is the straight OTA file - it has not been rooted or otherwise touched. If you're running stock, unrooted, and want to apply it, you can save it to the root of your SD card, and rename it "update.zip". Then boot into Recovery from the bootloader (disable "Fast boot" under "Applications", power device all the way off, and then hold volume down button while powering on until HBOOT appears. then choose "RECOVERY" option). When you see the phone with the red triangle & exclamation point, press both volume buttons and the power button at the same time. Some yellow error text should appear first (ignore that), and wait a few seconds until the menu appears. Use the volume buttons to select the apply update zip option, and then navigate to the file. Press the Power button to apply.
NOTE: I've only been using this OTA for a few minutes, and my phone keeps hot rebooting. I wonder what's up with that?
EDIT: If you want the full ROM, stock & rooted, based on this OTA, get it here.
EDIT 2: If you want the new kernel from this OTA, get it here.
DOWNLOAD (Dev-host)
Screenshots:
{
"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"
}

Thank You x1000.
OTA Installation failed. Tried this from revolutionary recovery. Bada Bing/Boom. upon reboot system tells u to do the update since i guess it didn't detect the installation.
EVO 4G(not really) Rooted with 5.07.651.1

click.mine said:
OTA Installation failed. Tried this from revolutionary recovery. Bada Bing/Boom. upon reboot system tells u to do the update since i guess it didn't detect the installation.
EVO 4G(not really) Rooted with 5.07.651.1
Click to expand...
Click to collapse
Revolutionary is a Clockwork Mod recovery. You need to be using a RA-based recovery (otherwise the firmware won't flash). And this will only work if you're running an unmodified stock ROM based on the 4.67 OTA (the release keys and /system content must match).

Is there any advantage in using this over y5 battery saver?
sent from my Supersonic on Digital Karma v7.7 w/ Tapatalk 2

Nooblet - Need help with my 1+2

Hi,
I bought my phone from Aliexpress. I am very happy with it, but I am facing some issues:
It was pre installed with some diffrent kinds of bloatware.
- Baidu Browser
- DU Battery Saver
- DU Speed Booster
And more see 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"
}
From time to time it tries to download some kinds of files. Seems to be Bloatware aswell. See picture -
In addition to this, the phone also fails to install update: OxygenOS 2.1.1.
I get a message after the reboot, that the install failed, click to reboot.
I've tried to follow this guide "youtube . com/watch?v=-IGDZxeFHAc" with out hope. Most likely something that I am doing wrong.
I have managed to:
Click the RunMe bat file
Install USB drivers
Unlock bootloader
When I try step 4 Flash TWRP Recovery I get to the following message: " Did you see the "okay", then congratulations you have flashed in the recovery "
I did not see the Okay message, and when I press THE any key to quit and boot to recovery, nothing happend its just stuck on Fastboot mode.
Please if anyone could help me I would be very greatful!
Kind regards ..
Kissfiss

kissfiss said:
Hi,
I bought my phone from Aliexpress. I am very happy with it, but I am facing some issues:
It was pre installed with some diffrent kinds of bloatware.
- Baidu Browser
- DU Battery Saver
- DU Speed Booster
And more see picture -
From time to time it tries to download some kinds of files. Seems to be Bloatware aswell. See picture -
In addition to this, the phone also fails to install update: OxygenOS 2.1.1.
I get a message after the reboot, that the install failed, click to reboot.
I've tried to follow this guide "youtube . com/watch?v=-IGDZxeFHAc" with out hope. Most likely something that I am doing wrong.
I have managed to:
Click the RunMe bat file
Install USB drivers
Unlock bootloader
When I try step 4 Flash TWRP Recovery I get to the following message: " Did you see the "okay", then congratulations you have flashed in the recovery "
I did not see the Okay message, and when I press THE any key to quit and boot to recovery, nothing happend its just stuck on Fastboot mode.
Please if anyone could help me I would be very greatful!
Kind regards ..
Kissfiss
Click to expand...
Click to collapse
Download the latest stock firmware from http://forum.xda-developers.com/one...rs-official-oxygen-os-roms-ota-t3209863/page9 and flash that using TWRP. Accessing TWRP after flashing it using fastboot is volume down and power. There flash the stock rom, and it should give you a fresh new OP2

N7 (3G, 2012) bricked? Boot mode, no recovery. N Toolkit doesn't flash.

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.

Issues returning to stock

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...