Database Info

[C2304] Installing TWRP or CWM recovery in the Xperia C

Well, I just purchased this device and came here after that to look at what we had and I'm disgusted.
And there are several reasons for that, being:
1 - Locked Bootloader...
2 - This forum seems somewhat abandoned, which leads it to be somewhat disorganized.
EdiT:
Thanks to our friend repey6 > http://forum.xda-developers.com/member.php?u=5704037
TWRP 2.8.7.0 is now included, and it works just ok, with all functionality.
I strongly recommend you to use it instead of any other recovery. Just make sure to backup your ROM again after installing it, as CWM or Carliv backups won't work in TWRP.
I replaced the old TWRP included in the attachments with the new one provided by repey6, but the installation process remains the same.
Plus, this was not created by me and it's mad old (2014). But still it works better than the Carliv Recovery we have available here...
So Let's go. The proccess is the same for both, just choose the recovery image you want in the end of the topic.
(almost forgot to say that if your phone bricks it's you responsibility, I tested it in mine and it is working fine)
STEPS:
STEP1- Root your phone (if it's not rooted yet).
To root your phone you'll need to:
a-Download the framaroot APK provided in the attachments
b-Install it then click in the Boromir option and the su binary will be installed.
c-Download SuperSU from google play store.
That's all, simple like that.
STEP2- Check your bootloader's S1 Version
a-Open your dialer and input *#*#7378423#*#* , then go to Service Info>Software Info> S1 Boot Version.
b- Check if yours is 2.14.J.2.6 or 2.14.J.2.13 or 2.14.J.2.16 . If yours is one of these go ahead, it should work just fine and you can proceed.
If yours is 2.14.J.0.68 do not proceed, as it will 100% brick your phone.
c- My phone has S1 Boot Version 2.14.J.1.15 and in spite of the developer having not mentioned anything about it, I risked it all and my phone flashed the recovery normally, so if your version is also 2.14.J.1.15, it should work just fine and you can proceed.
STEP3 - Install the recovery
NOW, BE EXTREMELY CAREFUL HERE, OTHERWISE YOU WILL HARD BRICK YOUR PHONE:
a-Download the mobileuncle.apk file provided in the attachments and install it.
b-Download the twrp_xperia_C.img file provided below and put it in your internal memory (not on the external). Rename it to recovery.img, otherwise mobile uncle won't see it.
Now, here's the part you have to mind, so you won't brick your phone.
Mobile uncle can install a recovery using one of two methods. One is by installing the image from your internal memory (which we'll be doing). Other is installing it from the internet.
Now, YOU DON'T WANT to install a recovery from the internet, as mobile uncle doesn't provide any image for your device. So if you flash any of these recoveries, you'll never be able to make your phone boot again.
See in the image below and you'll get what I mean:
{
"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"
}
c - So, before proceeding TURN OFF YOUR WIFI AND DATA CONNECTIONS so that mobile uncle won't show any recovery from internet
d-Open mobile uncle.
e-Grant Super User
f-Press "Recovery Update"
g- With wifi turned off, you'll see only your recovery in the screen
h- Click it, the file size of the file I'm posting must be around 6MB ( 6210KB for CWM), if it's different cancel and download file again.
i- press ok and restart.
DONE
:good:
EDIT:
I just noticed that after flashing the recovery you might get your phone stuck in the SONY logo after it.
In fact it happened to me, but just once.
If that happens don't panick. Recove the cover of your phone and besides the SIM-2 slot you'll see a tiny role with the word "reset". Insert a needle in there and your phone will restart normally.
CREDITS FOR CWM
Prashanth Jraj
Credits for posting it on the net and for the original tutorial:
informationlord.com
credits for TWRP 2.8.7.0
Miha_xXx
Original Post (for TWRP - in Russian): Click Here
credits for this tutorial:
me
ATTACHMENTS BELOW

Thanks for the guide! Does this also work on the C2305 model, or is it strictly for C2304?

Syd_M said:
Thanks for the guide! Does this also work on the C2305 model, or is it strictly for C2304?
Click to expand...
Click to collapse
It should work in both, I'm using a recovery for C2305 in my C2304.
Just don't try flashing a C2305 ROM on your C2304. It will not hardbrick your phonw, but the SIM cards will not work and you will get a mad functioning phones.
Some custom ROM's based on stock firmware work in both though.

Hey anyone tried for xc 2305???

So my S1 bootloader version is: 2.14.J.0.68. Is it for sure there is nothing that can be done?

SMIT120 said:
Hey anyone tried for xc 2305???
Click to expand...
Click to collapse
sid4913 said:
So my S1 bootloader version is: 2.14.J.0.68. Is it for sure there is nothing that can be done?
Click to expand...
Click to collapse
Sorry for the late reply! Haven't been able to test this until recently due to an issue getting my PC to work properly with my phone. Anyway, I would like to confirm that I was able to flash this on my Xperia C2305 that had S1 Boot Version 2.14.J.0.68. The photo below is proof of CWM running on my Xperia C2305:
Things you will need:
WMShua SuperFlash: http://soft.flushrom.com/WMShuaSetup.exe (after installing, you can change the language to English by renaming Program Files/wmshua/language to Program Files/wmshua/language_x)
Xperia C 16.0.B.2.16 FTF: C2305_16.0.B.2.16_TacoNikky.ftf or C2305_16.0.B.2.16_Congngheviet.ftf (pick one; I used TacoNikky's version)
Procedure:
1. Open WMShua, then click on Flash (not Super Flash). Browse to the FTF file you downloaded. You can choose to backup system before flash (I unchecked it on mine). Follow the screenshot below for guidance:
2. Turn off your phone. Next, hold down the Vol- (volume down) button on your phone. While holding down, plug in the micro USB cable. The LED will flash red. When it changes to green, release the Vol- button. WMShua should automatically try to install the needed drivers. After installing drivers, it will begin the flashing process. If your phone turns on instead, simply unplug it from the USB, turn it off, then try again.
The flash process may take a long time (it took 30+ minutes for me), and sometimes it may look like it hanged, but it's actually working. Just be patient. Once it reaches 100%, your phone will automatically boot up. Check your S1 Boot Version—it should now be 2.14.J.2.16. You may find that you've lost root, so you will need to root it again (I use KingoRoot). After rooting, follow the instructions on the first post to install CWM or TWRP. Good luck!

[Completed] [OP3] After couple ROM change test my phone is unusable, HELP PLEASE !

Hello everyone,
I currently have a Oneplus 3 which is completly unusable and I'm asking for your help to make it working again.
Until yesterday I used OxygenOs 4.0.2 ROM and it was about a moment I was thinking about changing my OS for the LineageOS ROM on Android 7.1.1 .I already did in the past this kind of changement on my nexus 5 for CM 13.0 .
So, I prepared all the files I needed (TWRP, ROM, Gapps etc...) and compared a lot of similar tutorial for being able to do it perfectly and being sure everything will work fine.
Firstly, I unlocked my bootloader though my PC and installed TWRP whithout any problems.
After that, I started the flash of the ROM and the Gapps zip packs. Everything worked and I launched the OS for checking if everything work.
I also wanted to ROOT my phone so I rebooted it and went to recovery again for flashing the ROOT zip from the LineageOS website and I picked the ARM64 one because I saw on internet it was the one needed.
After that, when I reboot the phone onto the system I have to make a "reconfiguration process" on this kind of way : Choose language --> Restore from zero --> Choose network --> Google account.
But, after filed my google account information I was normally able to receive a text for the double checked of my account but never it never came and the configuration is finally unsuccessfull because IMPOSSIBLE to skip the "network" or "google account" step.
I also tried to connect my phone on an other google account without the double checked option and it doesn't work too with this king of alert : " The process doesn't work due to an unknow error. Try again in 24 hours " .
I concluded that the problem come from the ROOT ZIP file, so I put my phone again in recovery and I do a " wipe / factory reset " for doing the exact same process from the begining (installing ROM) until root with this time the ARM ROOT ZIP.
Finally, I got the exact same result with the Google Account problem.
I choosed to do the complete process a third time with this time the SuperSu v2.79 ZIP file .... Result still the same.
Finally, I stoped trying to root my phone and I did again a "Wipe / factory reset" for just installing LineageOS and the Gapps pack. And I was suprised to see that the same problem continue to happen ! I wipe the phone and did again and again and again.
But, after all of that I choosed to do it on an other way. I saw on internet that " format data" through TWRP could be a solution for cleaning everything and start from zero. I did it and the process failed ....
From this point, I am with a phone which can't do anything and which saying that's impossible for it to "mount data" and other but I prefer to show that part on pictures. I think it'll be better for understanding (Excuse me for the pink because my HTC One M7 spare phone) :
Above there are the information that TWRP give me when I start it :
{
"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"
}
On an other hand, the phone is recognize by the computer just as a multimedia device and it's impossible to write on its memory or just having access on it :
I hope I was the most clear as I could and hoping as well for an existing solution for my issue (in better case with LineageOS on it with root working ! But I don't want to ask to much !).
Also, I am french and I apologize for my english if it can be weak sometimes.
Thank you in advance. I'll allways available if you need further information.
PS: Since my bootloader is unlocked I have these both pages when the phone boot (Picture 1 and 2) which normally permit me to boot onto the system, recovery, fastboot etc .... (Picture 3) but in reality there is NOTHING happening and I always have to do it on the classic way if I want to boot on recovery or fastboot (hold power button + ..... etc...) :

Up

Daftnap said:
Up
Click to expand...
Click to collapse
Hi !
Please don`t bump up the threads , we will answer according to our availability , thank you
Here the thread you need to follow
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Good luck !

Guide to Test Android 13 DP1 (lvm600am)

This restore process is intended for the AT&T V60 (lmv600am) model and will most likely WIPE your data so back it up if you want to keep it!
This process will restore the lmv600am to Pixel P4a a13 dp1. I’ve dumped all the required partitions from my lmv600am which has been running this rom for about a week now. I have yet to find any problem at all. To me it seems smooth and fast. This process uses the Qfil utility and assumes you already have a working knowledge of Qfil and that you have already installed it on your Windows PC. If you don’t have that knowledge start reading. The internet is full of Qfil guides.
You can’t damage or fix your existing imei relevant partitions from this restore because they aren’t included in this download.
You are responsible for backing up your existing phone partitions. I’m not liable for you using my work product and you do so at your own risk. If you’re unsure of what you’re doing then read more about Qfil and what is does. Again, if you are a newby go slow. Taking your time will save you a lot of aggravation.
This process will not fix your erased or damage imei number problem. There are process out there for that but they are usually reserved for people with an expert level of knowledge on the subject.
This guide is for anyone who’s presently wanting to try Google’ new Android a13 dp1 release. I have only this when my phone was already on an Android 11 rom. That’s not to say it won’t work coming from an Android 10 rom but I haven’t tried it.
I strongly suggest that you run the “reset option” option from Settings>System>. This will completely reformat and wipe your userdata when completed. No need to go thru the setup process just put phone in edl (9008) mode.
Steps
Download “Lmv600am a13 dp1 P4a Restore Partitions.7z” file from here and unzip. Remember the unzipped restore directory path.
Plug your phone into PC with USB cable and put you phone in EDL (9008) mode. Again, there are guides on how to do this everywhere.
Start Qfil and select the port of your phone’ connection. (See Windows device manager)
Select the v60 firehose (.elf) which is included in the unzipped directory.
Select storage type = ulf which is located at the bottom right of the Qfil dialog screen. I’m using Qfil 2.0.3.5 version. The correct version of Qfil is important as there have been problems with older versions.
Next click on the “load XML” button and group select “rawprogram0” thru “rawprogram6” which are also in the unzipped directory, then hit OK. Next it will ask for the Patch0.xml file, hit cancel as we’re not patching anything.
Wait a few seconds and then click on the “Download” button. Qfil will now resolve all the names of the partitions to be restore and then start the download process to the phone.
When complete phone reboots as I recall.
If you wish you can Qfil load both the eng alb file to abl_a – abl_b which will give you Flashboot mode and your magisk modified boot.img to boot_a – boot_b to give you root. I have both.

When I click download it just gets stuck. There is no ulf storage type on my qfil. Maybe I have the wrong one? I only get ufs and a few others.
edit I guess I bricked it, my other lg v60 works fine lol
nvm again used my laptop. that fixed it. Nice build

does the qdac works?

I update Android 13.How can I restore to origin lg system? It can't work as update steps.
{
"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"
}

ck5524209 said:
I update Android 13.How can I restore to origin lg system? It can't work as update steps.
View attachment 5562119
Click to expand...
Click to collapse
If you wish to restore to the original AT&T a11 system for lmv600am go to the guide in this forum which I provided. It is meant for this exact circumstance, to enable those that wish to test what they like when they like and then return to a stock a11 environment when they wish.

"Alcatel A30 Fierce" ROOTED/On-Going

Hello, I'm new to this- all of it, I've only just recently got into rooting and such things, but I'm progressing and that's what matters, no?
Anyway, I've successfully managed to root this phone via Magisk, that no one probably cares for anymore through trial and error and I'll do my very best to explain my method, and give updates as this is very on-going, there are certain issues and things I need to work out, but I appreciate any help, pointers, and such as before mentioned, I am new.
{
"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"
}
ALCATEL A30 FIERCE - Specs, and Specifications.
This phone was released in August, 2017.
Display - 5.5inches, 1280 x 720
Camera - 13 MP (Single Camera)
Hardware - MediaTek, 2GB RAM
Storage - 32GB, microSDXC
Battery - 3000mAh
OS - Android 7.0 Nougat
My own notes about this device.
Lots of MetroPCS Bloatware, can be a bit janky, but it's manageable.
It does not have a traditionally accessed Bootloader, no "adb reboot bootloader", this command just restarts the device to system.
Fastboot is odd, I managed to access Fastboot by some way I don't entirely understand, I'll go about what I did to get there later on in this post and try to recreate it later on as this post updates.
This device has colour states (if that's commonology), meaning, once the Bootloader is "unlocked", you will get an "Orange State" message before starting your phone that gets in the way of some things, I have yet to fix this, but I imagine we will if this gains traction, there will be a quicker fix!
No TWRP yet, as of posting, flashing a ported twrp.img through MTK_TWRP, or the TWRP_Port has not worked, and after flashing, neither will flashing the stock recovery but I've a quickfire way of getting around to fix this, if I can.
MTKCLIENT - https://github.com/bkerler/mtkclient
My Process, in the system, press the build number seven times to enable developer options - enable OEM Unlocking.
Then enable USB Debugging, and make sure you've installed adb and fastboot, as well as the correct drivers.
Through that link, follow the instructions specific to your operating system (I use POP OS and WINDOWS 11, YOU DON'T HAVE TO USE THE SAME AS ME), you may use the mtkclient_gui for an easier experience.
To unlock the bootloader, which will trigger "Orange State", open your terminal in the directory of the mtkclient and run python "mtk e metadata,userdata,md_udc", then, with your powered off device, and it will say something along the lines of "Preloader - Waiting for Device", with your USB Cable, and your wits about you, hold the volume down button (if this doesn't work for you, hold both volume buttons in" and plug your device into your PC with that command running. If the command completes, then run "python mtk da seccfg unlock", and this will unlock your bootloader.
WARNING: Unlocking the bootloader wipes the data of your device!
After this, dump your boot vbmeta with the commands in the mtkclient instructions, if this does not work for you with python or python3, I will provide the required files below.
Then, power your device back up, and install the patched magisk-app and push it to your sd card through adb, or traditional file transfer.
If you have your boot.img, push it to your sd card and patch it with magisk, then retrieve it from your phone - this is where my tutorial and mtk's tutorial take a bit of a turn!
I had a problem with the "reconnecting to preloader" phase, as it would not go through, or an error labeled [Unpack Requires A Buffer Of 12 Bytes] would crop up which prevented me from flashing the required files through "python mtk w boot,vbmeta boot.patched,vbmeta.img.empty". Let's go through some cautionary steps, what I did to achieve perma-root.
Create a funny-named file in the mtkclient directory labeled "DUMPY", do "python/python3 mtk_gui" and connect your powered off phone through the previously mentioned volume holding until it connects you in BROM mode. Under "read partitions", select all partitions, then "read partitions" and make sure the output is that "DUMPY" folder. This process will take awhile!
Once it finishes, rename your patched magisk-boot from [magisk.img name] to "boot.patched.bin" and under "write partitions", select the boot partition and write the boot.patched.bin to the boot partition! Once finished, start your device and install a root checker! It should be working!
If there are any errors, I will do my best to try and help you but keep in mind, I am very new to this, I hope it works for you too!

Question Unbrick Nokia 2.2

Good night everyone.
I have a Nokia 2.2 TA-1188 to which I recently unlocked the bootloader successfully using the method from this guide:
[GUIDE] How to unlock the bootloader for Nokia 2.2
To content farms: DO NOT COPY AND PASTE THE ENTIRE GUIDE! Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World. After I read his procedure, I decided to...
forum.xda-developers.com
However, when I tried to flash the latest TWRP (v3.6.2) over stock Android 9 (the ROM used to unlock the bootloader from the guide above) following the exact procedure shown on TWRP's site, using both the recovery IMG and the vbmeta linked within the instructions (the vbmeta apparently comes direct from Google), the phone became bricked and totally unresponsive apart from periodic short vibrations whenever I try to boot in any way (system, fastboot, recovery, etc.).
What can I do to try revive it?

kevriveroc said:
Good night everyone.
I have a Nokia 2.2 TA-1188 to which I recently unlocked the bootloader successfully using the method from this guide:
[GUIDE] How to unlock the bootloader for Nokia 2.2
To content farms: DO NOT COPY AND PASTE THE ENTIRE GUIDE! Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World. After I read his procedure, I decided to...
forum.xda-developers.com
However, when I tried to flash the latest TWRP (v3.6.2) over stock Android 9 (the ROM used to unlock the bootloader from the guide above) following the exact procedure shown on TWRP's site, using both the recovery IMG and the vbmeta linked within the instructions (the vbmeta apparently comes direct from Google), the phone became bricked and totally unresponsive apart from periodic short vibrations whenever I try to boot in any way (system, fastboot, recovery, etc.).
What can I do to try revive it?
Click to expand...
Click to collapse
If you can connect to the phone with SP Flash Tool you should be able to flash it with Android 9 again and start over. Just download though, not format + download, because then you'll need to restore your IMEI and serial numbers.

djinc91 said:
If you can connect to the phone with SP Flash Tool you should be able to flash it with Android 9 again and start over. Just download though, not format + download, because then you'll need to restore your IMEI and serial numbers.
Click to expand...
Click to collapse
I have just tried to do so, but to to no avail. I keep getting the following error message:
STATUS_STOR_LIFE_EXHAUST (0xC003001D)
The storage on your device has reached end of life, please change to use new device to do operations
I used the DA bundled with SP Flash Tool and drivers linked in one of the folders, apparently MTK ones.
Here's a screenshot of the error message:
{
"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 was able to download the firmware again after unchecking the Storage Life Cycle Check box within SP Flash Tool's options, and the phone is now up and running, no troubles up so far.
Thank you very much for your help djinc91!

Uhm Ur phones storage chip is literally dying
Thats emmc for u

areallydumbperson said:
Uhm Ur phones storage chip is literally dying
Thats emmc for u
Click to expand...
Click to collapse
I've had no trouble with my storage during all the years I've owned this phone. Never experienced slowdown, errors, loss of data, etc, not now, not before.
Even so, this is just a backup/2nd device used for nothing important, so it doesn't bother or worry me in the slightest. I'll just keep it using it as is until it dies or I just can't make it usable anymore.
Thank you for your heads up, though.