Develop Bugs

[Q] HELP!! Have I bricked my new device!? SO WORRIED!!

Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<

first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.

redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted

esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.

redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?

I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.

Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.

hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.

esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".

I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.

EFS Professional does restore aboot

EFS Professional works. Restored my aboot today, as a test, and it does in fact work, at least the restore of it did.
No, I did not lock my device with a retail rom, nor did I do any other kind of brick. All I did was a backup and restore of the aboot.
Device is a Note 4 Developer Edition on the NJ5 rom
If, there is a "better" test, like complete loss of phone - e.g. brick etc. flash of retail rom (not sure I'm willing to do that... so easy)
but in other threads regarding EFS (unless they are really old, old threads) which state recovery of the aboot has not really been tried - a theory, yet the suggestion was to wait till something does go wrong rather than just try it for the heck of it. Well, I did not head warning, and tested it anyway...
any comments?

Where can I get that cause I messed up me efs trying to unlock my phone.

anticloud said:
EFS Professional works. Restored my aboot today, as a test, and it does in fact work, at least the restore of it did.
No, I did not lock my device with a retail rom, nor did I do any other kind of brick. All I did was a backup and restore of the aboot.
Device is a Note 4 Developer Edition on the NJ5 rom
If, there is a "better" test, like complete loss of phone - e.g. brick etc. flash of retail rom (not sure I'm willing to do that... so easy)
but in other threads regarding EFS (unless they are really old, old threads) which state recovery of the aboot has not really been tried - a theory, yet the suggestion was to wait till something does go wrong rather than just try it for the heck of it. Well, I did not head warning, and tested it anyway...
any comments?
Click to expand...
Click to collapse
I'm glad it worked. You are brave.
What version EFSPro? Did you just restore aboot.mbn.tar.gz?
Thanks

can root be achived in retail Note 4? is this a workaround?
radionerd said:
I'm glad it worked. You are brave.
What version EFSPro? Did you just restore aboot.mbn.tar.gz?
Thanks
Click to expand...
Click to collapse
EFS_Professional_2.1.80_BETA.zip; and yes, it was just the aboot. The phone did not even flinch, just works flawlessly.
For some reason I trusted it, right?
What I do not know is, could I have flashed my way to a retail version, locked my device, and reflashed using this utility, back to developer's edition, that'd be the idea, right? But I assume it'd not just be the aboot but all the backed up partitions.
Comment - I tried backing up the userdata partition, and it bombed during md5 verification - I will take a guess that the user data partition changed maybe as a result of the backup itself, maybe, do not know...
but here is what I want to know - and this could be the clincher... follow me on this...
could I not take a developer edition and root it, right? Then, use EFS Professional to back it up - just the system partition, is that not where root resides, yes? then push the backup file to androidfilehost with the instructions in XDA to use EFS Professional to reflash the system partition onto a retail edition, right? would that be a way to flash a rooted system partition in a crude way - on a retail device? how would the phone know? Then, once root is achieved, could a programmer who knows better than I get to the solution of finding a weakness once inside the unit. Is that possible...
What I could do, is take the phone back to absolute stock, with odexed files etc. root it, and save the system partition with root, but stock otherwise... save off the backup like I stated above. I just may do that - what would the worst that could happen, the user community would have to use odin to reflash the system partition and boom, back to stock, right?
I say it's worth a shot -
and, if it worked, would I be eligible for a bounty?

anticloud said:
EFS_Professional_2.1.80_BETA.zip; and yes, it was just the aboot. The phone did not even flinch, just works flawlessly.
For some reason I trusted it, right?
Click to expand...
Click to collapse
I will have to change my aboot backup guide From theory to confirmed I don't plan to flash aboot unless something tragic happens. "I am once bitten, twice shy". Last spring I corrupted my Note-3 DE. It was hard bricked for 6 weeks before I figured out what partitions were corrupt, and how to restore them.
anticloud said:
What I do not know is, could I have flashed my way to a retail version, locked my device, and reflashed using this utility, back to developer's edition, that'd be the idea, right? But I assume it'd not just be the aboot but all the backed up partitions.
Click to expand...
Click to collapse
I'm afraid to say "in theory yes", you might take it as a challenge, please don't, careful If aboot had gotten corrupted the phone then wouldn't boot. Other DE owners flashed Oden stock retail Tars, and some were able recovered to a stock locked device. But here is the hitch, EFS Pro needs root, and busybox. So from a locked device you would need to make and modify an oden tar of your saved aboot.mbn.tar.md5. Then flash via Oden, Fingers and toes crossed, aboot is restored, hopefully.
The PIT has aboot mapped, so it can be flashed via oden once the saved aboot is modified; stripped, and TAR'ed with md5. It then could be flashed. Some other partitions aren't mapped, and can't be flashed like this.
anticloud said:
Comment - I tried backing up the userdata partition, and it bombed during md5 verification - I will take a guess that the user data partition changed maybe as a result of the backup itself, maybe, do not know...
Click to expand...
Click to collapse
Userdata is huge, I backed mine up as soon as I had root and busybox. Before it grew too big, compressing and writing a single file @ +2.5gb to SD and computer is a tall order.
anticloud said:
but here is what I want to know - and this could be the clincher... follow me on this...
could I not take a developer edition and root it, right? Then, use EFS Professional to back it up - just the system partition, is that not where root resides, yes? then push the backup file to androidfilehost with the instructions in XDA to use EFS Professional to reflash the system partition onto a retail edition, right? would that be a way to flash a rooted system partition in a crude way - on a retail device? how would the phone know? Then, once root is achieved, could a programmer who knows better than I get to the solution of finding a weakness once inside the unit. Is that possible...
Click to expand...
Click to collapse
Designed security measures won't allow an easy solution, signed partitions, locked boot loaders... stuffs that makes my head hurt thinking aboot
anticloud said:
What I could do, is take the phone back to absolute stock, with odexed files etc. root it, and save the system partition with root, but stock otherwise... save off the backup like I stated above. I just may do that - what would the worst that could happen, the user community would have to use odin to reflash the system partition and boom, back to stock, right?
I say it's worth a shot -
and, if it worked, would I be eligible for a bounty?
Click to expand...
Click to collapse
Your enthusiasm is refreshing, you are reading, and thinking. Continue to dig into the forums. Search, study, and Be Careful man
If you want to continue this discussion, We should probably skedaddle out of the Developer only forum before we get hollered at. We can move over here

thanks
radionerd said:
I will have to change my aboot backup guide From theory to confirmed I don't plan to flash aboot unless something tragic happens. "I am once bitten, twice shy". Last spring I corrupted my Note-3 DE. It was hard bricked for 6 weeks before I figured out what partitions were corrupt, and how to restore them.
I'm afraid to say "in theory yes", you might take it as a challenge, please don't, careful If aboot had gotten corrupted the phone then wouldn't boot. Other DE owners flashed Oden stock retail Tars, and some were able recovered to a stock locked device. But here is the hitch, EFS Pro needs root, and busybox. So from a locked device you would need to make and modify an oden tar of your saved aboot.mbn.tar.md5. Then flash via Oden, Fingers and toes crossed, aboot is restored, hopefully.
The PIT has aboot mapped, so it can be flashed via oden once the saved aboot is modified; stripped, and TAR'ed with md5. It then could be flashed. Some other partitions aren't mapped, and can't be flashed like this.
Userdata is huge, I backed mine up as soon as I had root and busybox. Before it grew too big, compressing and writing a single file @ +2.5gb to SD and computer is a tall order.
Designed security measures won't allow an easy solution, signed partitions, locked boot loaders... stuffs that makes my head hurt thinking aboot
Your enthusiasm is refreshing, you are reading, and thinking. Continue to dig into the forums. Search, study, and Be Careful man
If you want to continue this discussion, We should probably skedaddle out of the Developer only forum before we get hollered at. We can move over here
Click to expand...
Click to collapse
I think I just did - posted a thread here...
thanks
rob

@yhenks
You can't. This is talking about dev edition devices which have an unlocked aboot partition to start. It is not possible to create your own such version of the partition as dev edition aboot's are tied directly to the device they come on. This is just how to restore a previously unlocked device if you accidentally lock it. Not how to unlock an initially locked device.

[Q]Need help flashing CM12 on XM SS

After countless hours of searching over all related posts I am still confused and pretty much intimidated on the flashing aspect. From all my searching expeditions till now I managed to outline some of the points but I don't know how to move forward with them. Also I am concerned with the possibilities of getting the device unresponsive just because of my stupidity, want to gain full knowledge before going forward with the process.
So as per my findings, for installing a CFW like CM12, I require the following things,
1. Unlocked Bootloader.
The Bootloader on my XM SS can be unlocked, I did a check on that but the thing that's bugging me is the occurrence of bootloop.
Question for this point: What is the proper method to unlock the bootloader?
2. Rooted phone.
This is the step that has confused me from the beginning. Some posts mention that rooting is essential requirement to get a fully functional CFW and in some posts there is a not a single mention for the requirement of a rooted phone.
Question for this point: Is rooting essential? What is the best step by step method that you use to root your device?
3. Back up data.
I read somewhere that unlocking the bootloader erases some of the important information like the IMEI number, DRM keys and other important stuff? Also the importance of backing up data like contacts and other stuff externally.
Question for this point: How to do a proper backup? How to go on backing up contacts, whatsapp databases etc?
4. Installing a custom recovery?
Honestly I am totally confused with this topic. What does custom recovery actually do? Best custom recover for CM12?
Question for this point: How to select and install a custom recovery?
5. Adb, Fastboot drivers.
Is it essential to actually download the full adb package that google provides to develop android apps? And are fastboot drivers available for windows 8.1? Will the phone management software provided by Sony work as a driver?
Question for this point: ADB, Fastboot driver installation?
6. Flashing the CM12.
The most important step in the whole process? How to go on with this step so as to successfully flash the firmware? Restoring the backed up data?
Question for this point: Steps to properly flash the CM12?
7. Link2SD, App2SD?
Which one will you suggest and how to go on installing it?
I know that most of you will find it bothersome to answer so many questions in a single go but I intend this topic to be a guiding thread for noobs like me who are beginners that want to flash some CFW on their devices.
So all the posts that you make are really appreciated! Please link in the posts that you think will answer the questions in layman terms for everyone to understand.
Thanks for taking your time to read this thread
Have a good day! :fingers-crossed:

Can anyone please help? :crying:

1. http://forum.xda-developers.com/showthread.php?t=2484622 Follow everything he said, while using some common sense. Just to avoid you in doing so much research on some common problems I faced, :
i) If any errors occur, just close flashtool and re-open it, even if the errors continue to happen, just close and open flashtool again.
ii) You will experience bootloop and the end of the procedure, so just flash the tft http://forum.xda-developers.com/showthread.php?t=2779412
2. Just stay rooted, better safe than sorry Here's the guide: http://forum.xda-developers.com/xperia-m/general/towel-root-steps-to-root-t2789990 Understand the procedure first then continue.
3. You can export your contacts into your sim card tho, just open up the telephony app and go to contacts and open up the option or menu thingy in it (I think the icon was a 3 dot to access the options menu) and you'll see the Export/Import tab on it. You know what to do after this After root, I suggest getting the app Titanium Backup, really helpful. If possible, after the backup, move the folder to the sdcard, so it will never be lost (or to your pc, much safer).
4. Custom recovery.. well, I'm no expert but just think it this way, you're life saver when you do something wrong to your phone (and that it can still turn on, but couldn't get pass the boot animation) and provided that you had made a Nandroid backup before(a system backup). It can restore your phone back to the last time you've backuped it. This one for Stock 4.3 http://forum.xda-developers.com/xperia-m/development/recovery-philz-touch-6-41-6-xm-dual-t2795778 and this one for afteryou've installed CM12 http://forum.xda-developers.com/xpe...very-cwm-twrp-recoveries-custom-roms-t3016507
5. I'm not sure on this one, sorry:crying: ADB drivers and the fastboot drivers installed automatically for me:silly:
6. I think this video would be a bit helpful https://www.youtube.com/watch?v=DkNu0tiNro8
7. I don't know on this, I never used them. Soz :C
All the best:fingers-crossed: though my advice would be to stay Rooted for awhile before unlocking the bootloader, so you'd at least familiarize yourself with the terms that'll you'll most probably face.

The fastboot driver from google didnt work for me, use the ones from the sony bootloader unlock site. For win8.1 you need to disable signature verification to install them.

Thank you so much @AndyPhoenix9879
You are a lifesaver! I was finally able to flash CM2.1 on my Xperia M

Recovery + Root basics, requirements. Someone explain it to me pls.

Hi there.
I am sorry, I know this is really easy for some people.
I have read a lot, but when I start to do something with my phone I always find myself stuck at some point.
Please tell me a bit detailed, what are the requirements of a recovery. If I want to install it on my phone, how should I search for CWM or TWRP?
So the questions are:
1. Do I need a different recovery for every version of android for my phone?
2. Do I need a different kernel for every recovery?
3. Also about root, do I need a different method, files for every version of the ROM I use?
Phone: Sony Xperia Z1 Compact - Stock 5.0.2 - 14.5.A.0.270
I hope you understand my problem, thank you for your help.

Skateout said:
Hi there.
I am sorry, I know this is really easy for some people.
I have read a lot, but when I start to do something with my phone I always find myself stuck at some point.
Please tell me a bit detailed, what are the requirements of a recovery. If I want to install it on my phone, how should I search for CWM or TWRP?
So the questions are:
1. Do I need a different recovery for every version of android for my phone?
2. Do I need a different kernel for every recovery?
3. Also about root, do I need a different method, files for every version of the ROM I use?
Phone: Sony Xperia Z1 Compact - Stock 5.0.2 - 14.5.A.0.270
I hope you understand my problem, thank you for your help.
Click to expand...
Click to collapse
The simple answer to your 3 questions is 'no'. Are you currently rooted? If so, just download the installer package for Z1c from NUT here - http://nut.xperia-files.com/ and run the bat file on your computer. If not, then best way to root depends on bl status - locked or unlocked?

levone1 said:
The simple answer to your 3 questions is 'no'. Are you currently rooted? If so, just download the installer package for Z1c from NUT here - http://nut.xperia-files.com/ and run the bat file on your computer. If not, then best way to root depends on bl status - locked or unlocked?
Click to expand...
Click to collapse
Hi, sorry, didn't state that in my post.
The BL is Unlocked by default, unbranded and I ROOT-ed it today.
I will try what you suggested.
But still, I don't understand than why there are threads that tell me, I have to be sure my firmware is this version or that one when I tried to install a recovery.
I thought that is a requirement and I would brick the phone (softbrick I think).

Skateout said:
Hi, sorry, didn't state that in my post.
The BL is Unlocked by default, unbranded and I ROOT-ed it today.
I will try what you suggested.
But still, I don't understand than why there are threads that tell me, I have to be sure my firmware is this version or that one when I tried to install a recovery.
I thought that is a requirement and I would brick the phone (softbrick I think).
Click to expand...
Click to collapse
What I see is that development is very fluid and regularly changing and progressing. It's hard to make one program and blanket apply it to something that is changing. It's true that the recovery I linked above probably won't work on every manifestation of our phone software / firmware, but it will work on stock .270, and any other stock fw since then. There are also other options and the best thing to do is keep backups and try things out. Devs are always doing their best to keep up, and new solutions and options are always around the corner.

levone1 said:
What I see is that development is very fluid and regularly changing and progressing. It's hard to make one program and blanket apply it to something that is changing. It's true that the recovery I linked above probably won't work on every manifestation of our phone software / firmware, but it will work on stock .270, and any other stock fw since then. There are also other options and the best thing to do is keep backups and try things out. Devs are always doing their best to keep up, and new solutions and options are always around the corner.
Click to expand...
Click to collapse
Yeah, I get that totally.
Btw, I did it, I have the recovery, made a complete backup, now messing around and trying things.
Thank you for your answers.

To clarify:
The recovery.img you flash is an android boot image, containing a kernel, ramdisk and configuration for your device: Typically, a stand-alone system for your phone, capable of creating backups & restoring them.
You then tell your bootloader to boot from the partition containing that boot image, and you're in your recovery!
On the Z1C some things are different though: The devices uses the FOTA kernel partition(The partition where the Over-The-Air-Updater boot image should lay), and puts it's recovery there. The normal boot.img then waits for a key press and decides on the outcome of that which initrd it loads after that.
This is because the bootloader doesn't boot from any other partition on the Z1C(AFAIK).
I uploaded the init.sh from CM12.1 on my amami, if you're interested: pastebin.com/xnAuZL5w (Sorry, not allowed to poste links yet )
(Don't worry, the code is commented and only 74 lines)
As you can see, when it decides to boot the recovery, it executes
Code:
extract_elf_ramdisk -i ${BOOTREC_FOTA} -o /sbin/ramdisk-recovery.cpio -t / -c
$BOOTREC_FOTA points to /dev/block/mmcblk0p16
Code:
[email protected]:/ # ls /dev/block/platform/msm_sdcc.1/by-name/ -la | grep 16
lrwxrwxrwx root root 1970-01-10 18:51 FOTAKernel -> /dev/block/mmcblk0p16
the reveals that it's actually the FOTAKernel partition the ramdisk is loaded from.
Edit: Just read "developer.sonymobile.com/2015/05/18/recovery-mode-now-available-for-a-range-of-unlocked-xperia-devices-video/"
Seems like you can update your bootloader to support booting via the normal method I mentioned at the beginning! You'll most likely need to fully reset your phone for that, though! (New partition scheme)
Hope this helped to clarify the sittuation a little

Help Tech-Savvy NOOB get started

I have an old Sony Xperia M C1905 that I want to root/load a custom, cut-down ROM to free up space for the Apps that seem to be growing with every update. I am a NOOB (as you say) to installing custom F/W on my phone, BUT I am tech-savvy. What I need is access to a set of instructions/tools that I can use with my phone and PC combination. I realise that this is an old phone and you are trying to help, but for me it is frustrating when all the links to tools from the threads seem to be dead or don't work. Please can someone have a read and let me know a way to do this that has a set of working tools. Thanks
My PC is a MS Windows 10 laptop – If necessary, I could resurrect an old laptop and install Linux on it, if that is a simpler approach.
I have had a look at what is available and will probably load the ROM from:
https://forum.xda-developers.com/xperia-m/orig-development/rom-slim6-marshmallow-t3418258
What I think I need to do (and have tried to start) is:
1. Root the phone.
2. Backup the current ROM.
3. Unlock the boot-loader.
4. Load the Slim6 ROM.
To do 1. I have tried two methods, the first recommended from the backup thread and a second found by searching.
i. Easy Rooting toolkit: https://forum.xda-developers.com/showthread.php?t=2292598 but the download link for DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit.zip. The Download site for this tool tells me (eventually) that the file has expired or has been deleted by the owner - so i can't get this tool. Any Ideas How to get this?
ii. Also tried: https://forum.xda-developers.com/showthread.php?t=2529561 but for me, the cydia impactor tool does not see my phone or have any options. Yes, I have enabled - and allowed USB debug mode, before you ask. And yes the PC can see the phone so the connection is good.
To do 2. I am proposing to use the instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2292598 Please confirm this is still valid.
iii. [Update] Also tried rooting by using this thread: https://forum.xda-developers.com/showthread.php?t=2457174 but this requires Framaroot 1.5.3, When I try and download this, the download site says: "The file link that you requested is not valid. Please contact link publisher or try to make a search."
Update 2. Managed to get a download of Framaroot, installed, but does not work for Xperia M with Android 4.3. Any idea of a way forward?
To do 3. I am proposing to use: https://forum.xda-developers.com/showthread.php?t=2484622 Please confirm this thread is still valid - and the best approach.
To do 4. https://forum.xda-developers.com/xperia-m/orig-development/rom-slim6-marshmallow-t3418258 - Please let me know if there is a more appropriate ROM to install to free up some space.

You can follow this link :
And for root, I think slim6 is pre rooted. Means in Developer options, select root for adb and apps.

What about backing up the current ROME?
Thanks for your reply, but to my understanding this just does 2. & 3. from my list. Most of the ROM installation guides say to take a backup of the current ROM so that you can restore the original system.
To do this I need to get root access with the current build. Is this now impossible?
Maybe I just need to bite the bullet and just not bother with the backup.

You should definitely take a backup.
This is because of the TA partition. As soon as you unlock the bootloader of your phone it will format the TA partition, so without the backup you won't be able to restore it which might be needed. Using a TA backup from another phone will NOT work.
So you are right about the steps, you need to root the phone, backup, unlock the boot loader and flash the new ROM. I didn't check all of the links you posted now, but if Framearoot is not working for you you might want to try out iovyroot. Also check that you downloaded the right tool to root for your Android version.
If it's still relevant and you need any additional help I'll post some instructions for you another day.

Thanks for the confirmation of the process.
Iovyroot is not a root method I have tried. I will Investigate tomorrow.
I will post back here when I have tried it.
I have tried a couple of versions of Framaroot, one recommended version for the phone, and the latest version I could find. Neither worked.

Maninfrontofpc said:
Thanks for your reply, but to my understanding this just does 2. & 3. from my list. Most of the ROM installation guides say to take a backup of the current ROM so that you can restore the original system.
To do this I need to get root access with the current build. Is this now impossible?
Maybe I just need to bite the bullet and just not bother with the backup.
Click to expand...
Click to collapse
You don't need to get root access to have a backup. Just unlock your bootloader and install cwm or twrp through fastboot and take backup with help of it. Now if you are on stock rom and you need root anyway, you can use towelroot. And then install supersu from playstore. OR flash superSU through cwm. In that case no need to install towelroot.

Is nidhoegg mistaken?
Please can you confirm that the TA partition will Be NOT be formatted when I unlock the boot loader?

Maninfrontofpc said:
Please can you confirm that the TA partition will Be NOT be formatted when I unlock the boot loader?
Click to expand...
Click to collapse
Why are you so much worried about TA partition?

My understanding is that this contains various sets of system data including: S/W signatures for the Sony Apps (if I want to restore the Sony ROM to the phone); calibration data of the various devices on the phone - accelerometer etc. So surely, even if just for the calibration data, I would not want to lose this data even if I loaded a custom ROM - I have no way of re-calibrating the devices, so would need the factory acceptance calibration values.
Am I mistaken?

TA backup for our device isn't necessary. Actually I don't know anyone from xda taking TA backup. TA backup is for newer sony devices and z series devices. In those devices, somethings like sony camera wouldn't work if you lose drm keys. It's not the case with our mobile.

Are you saying that all the threads from when this was the current phone are wrong, and I don't need to backup this partition?
TA = Trim Area; as well as holding the DRM Keys/S/W signatures, my understanding is that at contains Trim data to adjust the various sensors on the phone to read accurately. I have been led to believe that these are written during the automated Factory Acceptance Testing to adjust for small differences in the components on the phone, and are unique to the device. Surely if I lose this data the sensors will not read accurately.
Is this wrong?