Related
Hey guys! So I haven't updated my device since like...November? It's running 4.1.2 with the XenonHD-11-03-12 ROM, Build number JZO54K. I honestly have NO idea why I haven't upgraded my device, I stopped using it every day and honestly the current ROM runs fine but I want to upgrade it finally! My question is that I don't know if I can just flash a new rom, or do I have to do anything else to it? Obviously the bootloader is unlocked, but idk what the steps are for flashing a new rom, idk if I need to update any of the drivers etc. If you guys could help me out here I'd appreciate it!
I'm guessing you are on bootloader v3.41, and probably an older TWRP or CWM recovery.
Highlights of things you should know:
(a) there have been TWO bootloader updates since v3.41 - v4.13 and v4.18
(b) the 4.2 Android introduction of multi-user support caused a bit of a hiccup with the way custom recoveries store & find their backups, so if you move to a 4.2.x-based ROM, for sure you will want a recent version of CWM or TWRP. Same goes for flashable SuperSU or Superuser packages - you ought to upgrade to a recent version if you flash those yourself.
(c) the latest release (4.2.2 JDQ39) has extra security features revolving around the use of ADB; most users report that they needed to update the Google SDK to the most current version to be able to use adb with the booted OS. Whether or not a given ROM dev turns this stuff off (e.g. in /default.prop) I suppose depends on the whims of the ROM developer.
Since the bootloaders are proprietary, nobody has any clue whether there are important bug-fixes involved; OTOH, some kernel devs reported that their newer kernels would not behave correctly with the older v3.41 bootloader - so that should give you some motivation to flash a replacement bootloader. (Note that flashing a bootloader is the most dangerous thing you can do - make sure that you are doing it from a setup that is not flakey, and double-check the bootloader file length before you begin).
So - in a nutshell, that's a few more things that you probably will want to do IF you decide to upgrade - in addition to making backups and flashing a new ROM. If you used a toolkit, I suppose you will need to also upgrade that either before or after flashing a 4.2.2 ROM.
I see that there is a 4.2.2-based (JDQ39) version of [ROM] XenonHD Stable-5.0 (23.02.13). Don't know anything about it though. Since you are on a 4.1.x version of that ROM, I doubt that doing a dirty-flash is an advisable plan of action. Probably safer to use TiBu for market apps & their data, and "start over" with the new ROM and use TiBu to restore your market apps.
good luck
So I am new to the whole Root and ROM Android arena. And I came up with a few questions that hopefully you guys can help me with.
1. I read people saying they lost their ROOT after an update from 4.1 to 4.2 or 4.2.1 to 4.2.2? How did this happen for them?
Do you have to Un-root and flash to stock before updating to a different build (Such as 4.1 to 4.2 or 4.2.1 to 4.2.2)?
2. Right now I am using a custom ROM on Android Version 4.2.2.... if a new Custom ROM with a new android version released (Let's say 4.2.3) can I flash from one Rom to the other with just wiping Cache/Factory wipe and Dalvik Cahce or is there something else I would need to do because of the Android version update?
Sorry those two questions above are very similar but I wanted to ask them both ways.
3. If I were to get bored of the Custom ROM I am currently on. Are there any Best Practices "rules" I should know about when switching from one custom ROM to another?
4. Last if I am on a custom ROM with a nightly build..... is it more common to update to every nightly build that releases? Or is it more common people to only pick and choose choice nightly build versions. And if people do update to every new Nightly build.... can you update too much and destroy your device?
Sorry guys I know these seem like very basic questions..... and Yes I did search the forums. However while I found some very basic answers nothing went into great depth in explanation. All the answers seemed to be very vague.
does anyone have some suggestions on where to find these answers?
1. If you are on stock, rooted, and you update versions of the OS, you are essentially UPDATING the /system partition. That is how you lose 'root' when upgrading. If you modify any system files while rooted, you have to either revert to stock or change those modified files back to the original before running the update.
2. Just run FACTORY RESET in your custom recovery and flash the new custom rom. No need to wipe any caches (/cache is wiped during a factory reset anyway). It doesnt matter what version to what version. Sometimes new versions might require new bootloaders, but you will be bombarded with that information here if that becomes the case.
3. See number 2. Its the same thing. backup your apps with Titanium Backup, do a Factory Reset in custom recovery and flash new rom....done.
4. doesnt matter. you can update as much or as little as you like. some people prefer stability over new shiny, but then others are just crack-flashers....and will literally flash ANYTHING posted to see what happens
Pirateghost said:
1. If you are on stock, rooted, and you update versions of the OS, you are essentially UPDATING the /system partition. That is how you lose 'root' when upgrading. If you modify any system files while rooted, you have to either revert to stock or change those modified files back to the original before running the update.
2. Just run FACTORY RESET in your custom recovery and flash the new custom rom. No need to wipe any caches (/cache is wiped during a factory reset anyway). It doesnt matter what version to what version. Sometimes new versions might require new bootloaders, but you will be bombarded with that information here if that becomes the case.
3. See number 2. Its the same thing. backup your apps with Titanium Backup, do a Factory Reset in custom recovery and flash new rom....done.
4. doesnt matter. you can update as much or as little as you like. some people prefer stability over new shiny, but then others are just crack-flashers....and will literally flash ANYTHING posted to see what happens
Click to expand...
Click to collapse
Thanks I really appreciate the response. :good: You'd be surprised how many "Tiny Parts" of answers you get from searching. Very rarely the whole answer you need.
I am glade to hear that Question 2 only requires you to just factory rest. From the misinformation gathered on other forums... I was starting to think you had to flash back to stock before updating to another Custom ROM Build.
@20mmrain
You've probably looked at a number of posts by confused newbs. For better or worse, this site is nothing like a moderated wiki, so you find treasure mixed in with trash.
Rooters fall into four broad classes:
(a) Those that "root & modify" stock ROMs
(b) Those that abandon stock and use custom ROMs and kernels
For each of the above cases, there are diligent and careful users who make full (nandroid) backups... and lazy idiots who do not. It is almost always the lazy idiots you observe coming in here in a panic, independent of whether they are in class (a) or (b).
Beyond that, newbs taking approach (a) seem to perpetually labor under the false impression that their modified versions of a stock ROM should be able to be upgraded by the OTA process - when in fact that there is absolutely no reason to believe that. The OTAs carefully check hundreds of different files before they perform any changes; if even a single one of them has been altered, the OTA aborts without making any changes.
It is *possible* that if none of those hundreds of files are changed that an OTA will succeed on a "nearly stock" ROM. When this happens though, it is quite typical that:
- the "su" binary (part of a root kit) in either /system/bin or /system/xbin gets its' setuid permissions reset by a recursive permission-setting command in the OTA
- the custom recovery can possibly be overwritten by the new stock recovery.
Folks tend to refer to either of the above as "losing root". True in principle, but they are trivially fixed up - if the user actually understands how Android rooting works. (With fastboot, you simply reflash the custom recovery, boot into that and reflash the same root kit originally used).
It's too bad that folks who put together rooting guides seem to neglect putting an emphasis on making backups. They give you both security and freedom.
Bottom line: whatever you choose to do, make nandroid backups. You don't need to keep them all on the tablet - but for convenience reasons, you should have at least one known good ROM as a backup available to be restored.
good luck
Wow that is a really in-depth explanation and that is exactly what was looking for! Since I have been working in the IT world for years I will say with pride that I am an individual who believes in safety first and always back up any important project I am working on! So I am happy to hear I made the right decision there.
I guess a great deal of my questions also stem from working in a windows based world for so long ....that I am still learning Linux/android.
Right now I do keep a nandroid backup on my nexus 7 but only one. How backups do you have? And do you just keep the rest on a thumb drive?
Sent from my Nexus 7 using xda app-developers app
20mmrain said:
Right now I do keep a nandroid backup on my nexus 7 but only one. How backups do you have? And do you just keep the rest on a thumb drive?
Click to expand...
Click to collapse
At the moment I have 6 on the tablet - all generated in the last 60 days. Two in the last two days (one a rooted stock/jdq39, another a cm10.1 nightly). Plus recent TiBu market app & data backups. 32 GB model, so I have plenty of room.
That doesn't reflect any particular strategy or goal. I hook it up to a PC every once in a while and at that time either copy off any backups worth saving or delete them. Most of the those I have on the PC will eventually be deleted as well without ever being used. You could use a USB key if you want to. Really you only need to keep one on the tablet - mostly as a convenience in case you wedge your daily driver ROM with some random mod: you can restore a working ROM right from your tablet rather than having to find a USB key or return to your PC to get the tablet booting again.
There is one type of ROM backup that I think is very useful to keep a permanent copy of - a pure stock ROM. The reason for that is that any radio images (tilapia) or bootloader upgrades that are *sometimes* delivered by OTA can be trivially installed by:
- make a backup of the current ROM
- restore a pure stock ROM backup (including the stock recovery! ***)
- take the OTA
- ***soft-boot a custom recovery and make a backup of the NEW stock ROM (including its' recovery!)
- hard-flash the custom recovery to the tablet
- restore the backup from the first step above.
Doing things this way is the safest possible way to install either a bootloader or a radio image. Not only that, but for folks that prefer to mod stock ROMs, it gives them a backup archive of /system to recover arbitrary (stock) files from.
*** soft-booting a recovery is the most convenient way to capture a stock recovery as part of a nandroid backup. I.E.
Code:
fastboot boot recoveryimagefile.img
If you hard-flash a custom recovery before you make a nandroid backup of a stock ROM, you lose the opportunity to get a copy of the stock recovery along with the rest of the stock ROM.
good luck
@mods May I request that you pin this thread? Thanks
To the XDA Community and readers alike,
Welcome to the Xperia Z3 reference guide aimed at compiling all of the most useful and most effective methods and tips to guide you through using you Xperia Z3. In this guide, I will try my best to cover all of the topics needed to get you started with your Xperia Z3 endeavors both Advanced and Basics. If you feel you want to contribute, then please place what you feel should be added in the thread. I will ensure you’re properly credited for your contribution . This guide utilizes the same format in this guide by XDA Recognized Developer @DooMLoRD and has been modified to suit the Xperia Z3 community.
To start off, let me introduce myself. People refer to me as Furrydaus and I am a developer, contributor and a person whom people look for if they have queries for their Xperia SP who's 15 Years old. (Yep you heard that right!). (I do not have the Recognized Contributor Tag but I don't actually bother much. The community is far more important than those tags ) I help out projects and also create projects for the community. I mainly develop for the Xperia series and the Xperia SP is my third device that I owned under the Xperia Series. The Xperia Z3 is my fourth device that I own. I help with creating Firefox OS, CyanogenMod 11s, Z3Perience and other mini mods for the Xperia SP. So with that silly introduction of myself out of the way :silly:, let’s get started with the guide shall we?
The Contents Covered in this guide:
The Basics
• BootModes
• Information Concerning your device
Advanced Information
• FlashTool
• Root
• Bootloader Unlock
• Recovery
• Flashing Custom Kernels
• Flashing Custom ROMs
Click to expand...
Click to collapse
>> The Basics
[Boot Modes]
Every new mobile device released under SONY has access to various boot modes that is able to handle different things. The 'Boot mode' is a form of interacting with higher level functions on your device such as the hardware
• Standard Boot Mode – This is the standard boot method used to start you device to its normal state. You are able to access the standard boot mode by pressing the power button on your device. (If you don't know this, then I have nothing else to say )
• Flash Mode – This is the mode used to flash official firmware to your device by using an .ftf file (Will cover more about .ftf's later). This mode is similar to what you use to flash firmwares in Samsung Devices through ODIN. To access Flash Mode, Press the volume down button while inserting the Micro USB Cable into your device
• Fastboot mode –This is the mdoe used to flash an official/custom kernel and system images. To access Fastboot, press the volume up button while inserting the Micro USB Cable into your device. This mode requires you to unlock your bootloader (Unlocking The bootloader is covered in the later parts of the guide)
>> The Basics
[Information that concerns your device]
Kernel:
A kernel is used as an interface to talk to your hardware and software. This can be reffered to as the MIDDLE MAN and plays a very important role in making your device function. It is VERY important to not flash the wrong kernel into your device.
Model numbers:
The Xperia Z3 is shipped worldwide in three different variants namely,
• D6653 (TD-LTE)
• D6603 (LTE-A)
• D6633 (Dual LTE-A)
The devices are equipped with everything from hardware to software but they differ in the network type each utilizes due to country specific radio
Android version: http://en.wikipedia.org/wiki/Android_(operating_system)
The Android Version determines whether your device is running the latest features and implementation in design and functionality by Google. It is recommended to always upgrade your android version officially to get the most out of your device. The Xperia Z3 is shipped with Android 4.4.4 Kitkat
Baseband version:
The Baseband is the software interface that communicates your radio to the networks available. A missing baseband=no network. This isn’t the full description but gives you the basic understanding to its use.
Build number:
The Build number is used to identify the firmware version for your device. For example, the Xperia Z3 is shipped with official firmware that is denoted as 23.0.A.2.93. The Firmware version determines whether you device is Up-To-Date. The build.prop in your device can also be tweaked to change the Build Number but we recommend that you do not do so to ensure you device gets the latest updates officially. Official Build Numbers and Firmware Versions can be found here
Firmware:
The firmware is a package containing all the official software for a particular build. It contains system, kernel and baseband files. Firmware is supplied mainly via the forums in an FTF package (a container file ending with .ftf) which can be flashed via FlashTool. Official Build Numbers and Firmware Versions can be found here
Here's the largest and the only .ftf thread containing all of the .ftfs for most devices: http://forum.xda-developers.com/z3/general/ftf-stock-firmwares-xperia-z3-models-t2886061
(I will be helping out the OP soon by providing 100's of ftf's for you guys )
What are the ways to update/repair firmware?
SEUS (Sony Ericsson Update Service) / PCC (PC Companion) / EMMA are all official ways to update to new or repair existing firmware on your device. SEUS/PCC are available to all users (consumers), EMMA is special and is only available to select individuals. This requires you to connect device to PC and then the software will check for updates and download them over the internet.
Updates can also be sent as FOTA (Firmware over-the-air)/OTA (over-the-air) updates where you can download and install the updates without the need to connect to PC/any software.
>> Advanced Information
FlashTool
Flashtool is an unofficial utility supplied by the community namely, AndroXyde. It is the most EASIEST way to flash official firmwares, kernels, custom kernels on both locked and unlocked bootloader devices to your needs. Firmwares that can be flashed via FlashTool is denoted with a .ftf at the end of the file. FlashTool can be used to flash both locked and unlocked bootloaders devices.
For Everything Flashtool,(download links, release notes, FAQ) Head right down to the Flashtool Homepage
Flashtool is also available on GitHub
~ [FLASHTOOL GUIDE] HOW TO for n00bies
Sony also provides an official FlashTool but it can be used only with unlocked bootloader devices.
>> Advanced Information
ROOT
The term root is defined as the way to indicate that your phone has access to higher privileges than standard mobile phones. It can be referred to as the Administrator Mode for Windows but on android instead. Obtaining root requires you to be extra careful as a certain tweak you do to your device might result in a faulty/non-working Z3 that you bought . But with root, you are able to do a world of things from changing the aesthetic look of your device to affecting the performance of your device by overclocking
To obtain root, we recommend you to read this;
CWM-Based Recovery 6.0.4.7 Recovery for Xperia Z3! [DooMLoRD]
>> Advanced Information
Bootloader Unlocking
SONY, Carriers and even other companies tend to lock their bootloaders as a way to force a user to stay with the current state of the device as a way to make sure that their hardwork isn't being replaced. SONY allows the bootloader to be unlocked but it comes with a hefty result for the Z3. Read on to find out why,
Before unlocking your bootloader, You might want to read this:
Extracted from Official SONY unlock bootlaoder site:
Code:
What is this?
By unlocking the boot loader, it’s possible to put custom ROMs on your Xperia™ device. However, we recommend standard users not to unlock the boot loader, as it is not needed. We are proud to deliver great software experiences through our rigorously tested and official software releases. If you are not familiar with the risks involved, you should not proceed further.
Voiding the warranty
If you unlock the boot loader, you may void the warranty of your device and/or any warranty from your operator. See your device’s warranty statement for details. Additionally, due to the modified device software, Sony’s repair network will likely have to replace key components before it can properly test, repair and verify your device using our repair tools and software. Consequently, if Sony performs a warranty repair, Sony will likely charge you a significant service fee for the additional costs caused by your modification of the software.
Risks
Please be aware that Sony cannot guarantee the full functionality, and will not be responsible, for any unsigned custom ROM being flashed to your device after the boot loader is unlocked. An unsigned custom ROM may not have gone through the thorough tests that we run for each device and software version that we release.
Also, a custom ROM might not work properly on your device, and certain functions and offerings may cease to work. The performance of the device might also be affected, and you may damage your device permanently. In worst case, unlocking the boot loader will cause physical injuries or material damage, for example, due to the device overheating.
Certain pre-loaded content on your device may also be inaccessible due to the removal of DRM security keys. For high-end devices running recent software versions, for instance Xperia Z3, the removal of DRM security keys may affect advanced camera functionality. For example, noise reduction algorithms might be removed, and performance when taking photos in low-light conditions might be affected. The secure user data partition may also become inaccessible, and you will not be able to get any more official software upgrades if you unlock the boot loader.
Click to expand...
Click to collapse
If you are sure you want to unlock, the we recommend you read this;
Guide [for beginners] – How to Unlock Bootloader via Flashtool [sid.8491]
>> Advanced Information
Recovery Mode
To learn more about recovery mode, we recommend you read this guide from addictive tips:
Complete Guide to CWM Recovery [Addictive Tips]
To obtain recovery, follow this guide we recommended earlier to obtain root;
CWM-Based Recovery 6.0.4.7 Recovery for Xperia Z3! [DooMLoRD]
>> Advanced Information
Flashing a Custom Kernel
Custom Kernels are mainly specific to the ROM that is being used, stock or custom and you must use the specified kernel with the specified rom to ensure things go smoother for you.
To flash a custom kernel, you can,
1. Flash via Flashtool using FastBoot Mode >>LINK TO GUIDE BY ANDROIDIZER
2. Flash via Recovery in an update.zip file (or in the rom zip itself)
>> Advanced Information
Flashing a Custom ROM
Custom ROMs provide you with possibly enhanced, more or better features than a stock ROM and it depends on the user itself if they want to flash a custom ROM. Most custom ROMs developers provie a .zip which can be used to flash through recovery as means to install the ROM. Usually ROM developers will place the specified steps to flashing the ROM so follow that instead. But if they don’t, this what you generally do,
1. Download the ZIP file and Save it on ur PC (you can also save it to your mobile)
2. Connect your device to the computer and save the .ZIP file on the SDCARD of your device
3. Disconnect the device from the computer upon completion of file transferreboot into recovery
4. Boot into your Custom Recovery and navigate through the menus to find and clear the Dalvik Cache, Cache Partition and System (Factory Reset)
5. Navigate around the recovery menu again to find for the .zip file transferred earlier and flash the .Zip file
6. After flashing is over, reboot device and you will be able to boot on the custom ROM. If not, contact the developer via PM or the Thread.
Click to expand...
Click to collapse
>> Changelog
The Changelog goes from the oldest to the newest changes (Bottom-> Top)
Code:
5 October 2014: Improved Thread, Added Changelog, Added new up-to-date information
5 October 2014: Release of the Guide
Any information you feel you want to add in?
Feel you should have been credited for something?
Then PM me or reply to the thread so I can handle the request! :good:
Updated the guide with many new pieces of information and also added a changelog to show what has been updated
[emoji1]
Nice guide you have there... Applies mostly to all xperia devices... =)
Hi
In deed i very nice work but for a newbee like my with a unlocked Z3... what do i need to have root in order to remove bloatware?
Regards
Mod, please sticky this!
Indeed a nice guide for newbees
bernardix said:
Hi
In deed i very nice work but for a newbee like my with a unlocked Z3... what do i need to have root in order to remove bloatware?
Regards
Click to expand...
Click to collapse
System App Uninstaller from the Google play store
Sent from my C5303 using XDA Premium 4 mobile app
Looks like great guide, i am going to read it tomorrow when my phone arrives.
Nice guide for newbies. Nice work!
Hi.. Im new here with this device i read almost every single post here but there are quite a few things that I don't get it..
What is bootloader? Should i unlock it before rooting the device? And recovery here is in Chinese so shall i get TWRP instead? Also about the flashing Roms issue that erase imei and SN.. why would that happen? And How can i take a backup for these in case i lose them.. Some people mentioned SN writing tools but some people says its not working so im abit confused.. And has anyone noticed that the flashlight of the mobile is actually yellow that affects camera's captures? I would be really grateful if someone helps
1. What is a Bootloader?
Hboot, or we may call it Boot-loader, is like BIOS to windows. It is the first thing that runs when you boot up your Android device. It packages the instructions to boot operating system kernel and most of them are specifically designed to run their own debugging or modification environment.
Every Android phone has a boot-loader that instructs the operating system kernel to boot normally. But you need to understand one thing here that as Android OS is an open source OS and is available on a variety of different hardware, every manufacturer has their own version of bootloader specific for the hardware present in it’s environment.
2. Should you unlock it before rooting the device?
It solely depends on you whether you want to unlock it or not. Unlocking bootloader will give you access to installing custom recoveries on your phone and also you can use custom kernels to boost up phone's performance or simply get more battery juice. Since our K4 note doesn't have any custom kernels so good luck with that.
Warning: Unlocking Boot-loader voids phone's warranty
3. Why does IMEI/SN erases while flashing ROM's
People don't read the tutorial properly. They blame the OP instead when they do something wrong and loose their IMEI/SN.
What basically happens is, when flashing ROM's through SP flash tools, They should flash it in "DOWNLOAD" mode only and not in "Format ALL" mode. People who all lost their IMEI basically did this mistake.
4. How to Backup and Restore your IMEI/SN (NVRAM)
All the device specific details such as IMEI, SN, MAC addresses are stored in a partition called as NVRAM. So backing it up will indirectly be referring to backing up your IMEI/SN. Here is how you can do it.. LINK
5. How to install Recovery?
if you are on Marshmallow then you will be able to install recovery through this thread. LINK
6. Yellow Flashilight problem?
This bug is introduced in Android V6.0 that is marshmallow. Actually this is not truly a bug. Unlike on Lollipop which had only one LED light enabled during Camera operations, Lenovo decided to enable both of the LED's (That is white and yellow) to give the images a more true LIVELY appeal.
But terming this as bug here because nobody liked it and users were pissed off straightaway. Hopefully, Lenovo will fix it soon.
Hit Thanks if i helped..
Krishnas096 said:
1. What is a Bootloader?
Hboot, or we may call it Boot-loader, is like BIOS to windows. It is the first thing that runs when you boot up your Android device. It packages the instructions to boot operating system kernel and most of them are specifically designed to run their own debugging or modification environment.
Every Android phone has a boot-loader that instructs the operating system kernel to boot normally. But you need to understand one thing here that as Android OS is an open source OS and is available on a variety of different hardware, every manufacturer has their own version of bootloader specific for the hardware present in it’s environment.
2. Should you unlock it before rooting the device?
It solely depends on you whether you want to unlock it or not. Unlocking bootloader will give you access to installing custom recoveries on your phone and also you can use custom kernels to boost up phone's performance or simply get more battery juice. Since our K4 note doesn't have any custom kernels so good luck with that.
Warning: Unlocking Boot-loader voids phone's warranty
3. Why does IMEI/SN erases while flashing ROM's
People don't read the tutorial properly. They blame the OP instead when they do something wrong and loose their IMEI/SN.
What basically happens is, when flashing ROM's through SP flash tools, They should flash it in "DOWNLOAD" mode only and not in "Format ALL" mode. People who all lost their IMEI basically did this mistake.
4. How to Backup and Restore your IMEI/SN (NVRAM)
All the device specific details such as IMEI, SN, MAC addresses are stored in a partition called as NVRAM. So backing it up will indirectly be referring to backing up your IMEI/SN. Here is how you can do it.. LINK
5. How to install Recovery?
if you are on Marshmallow then you will be able to install recovery through this thread. LINK
6. Yellow Flashilight problem?
This bug is introduced in Android V6.0 that is marshmallow. Actually this is not truly a bug. Unlike on Lollipop which had only one LED light enabled during Camera operations, Lenovo decided to enable both of the LED's (That is white and yellow) to give the images a more true LIVELY appeal.
But terming this as bug here because nobody liked it and users were pissed off straightaway. Hopefully, Lenovo will fix it soon.
Hit Thanks if i helped..
Click to expand...
Click to collapse
Ahaaaaa Thanks Alot now it get it all.. Hope they fix that soon.. And i read that some devs here is willing to make a custom kernel i guess.. thanks again and sorry for wasting ur time.. Btw have u noticed that the sound on headset and Bluetooth is also abit lower than other devices?
Lenovo A7010 - CM13.0 Android 6.0 on lenovo-forums.ru
Here's my understanding of getting custom ROMS for your device by doing little to no work.
If SHARP isn't releasing the source code, can't we just go and flash a ported ROM zip?
First, you find a device with exactly the same specs as yours: Easiest way to do this is googling phones with the same processor.
https://www.kimovil.com/en/list-smartphones-by-processor/qualcomm-snapdragon-400-msm8926
Now, we press "Compare" and see if we can find a phone that has exactly the same camera and/or other components.
Let's assume that our cameras are going to work out-of-the-box, and sort it down.
https://forum.xda-developers.com/leon
Oh, lookie! A phone with pretty much exactly the same specs, and a community that is making/porting ROMS for it?
https://forum.xda-developers.com/leon/development/aosp-5-1-1-lg-leon-ms345-t3611883
Hey, an Android 5.0 ROM?
Now, knowing the information we know now. Can't we logically go into the (aosp-5-1-1-lg-leon.zip) and change around the MANIFEST values to make sure they point to the correct places? Can't we change around the configuration so it will install?
I don't know all too much about porting ROMS, but if it's as truly as easy as I'm explaining it, why haven't we done it yet?
(Feel free to correct me if I have any details wrong! I'm open to criticism!)
Quick Update:
To begin porting other ROMs, I am compiling an actual flashable ZIP (Stock ROM Image) to use as a base for the other images. I am getting my sources from here: http://www.sharpusa.com/Home/CustomerSupport/SharpCareCenter/MobileSupport/OpenSourceCode.aspx
And compiling them using AnyKernel. I will post flashable ROM.zip here when I am done.
updates
Rhioun said:
Quick Update:
To begin porting other ROMs, I am compiling an actual flashable ZIP (Stock ROM Image) to use as a base for the other images. I will post flashable ROM.zip here when I am done.
Click to expand...
Click to collapse
any progress?
Yes, I managed to make a flashable Aquos Sharp zip, based off Kernel Version S4081.
Currently, I'm attempting to get a ported ROM over.
I'll post the flashable Stock ROM though:
https://drive.google.com/file/d/0B0Fuy6MV4s8RU0NUMzRvLVp5WjA/view?usp=sharing
hi thanks for all very good news
can i flash with 305sh factory unlocked and rooted ?
No, that is a ROM for the 306SH.
The 305SH files are on a Japanese version of the Sharp website.. the links on these forums somewhere.
I can't test 305SH files, since I only own a 306SH.
If you could find the links for the 305SH system.img and boot.img, I could compile a flash able ROM for you.
Else, search around for a TWRP backup for the 305SH that you could restore on your phone.
Rhioun said:
Yes, I managed to make a flashable Aquos Sharp zip, based off Kernel Version S4081.
Currently, I'm attempting to get a ported ROM over.
I'll post the flashable Stock ROM though:
https://drive.google.com/file/d/0B0Fuy6MV4s8RU0NUMzRvLVp5WjA/view?usp=sharing
Click to expand...
Click to collapse
Can you paste a few pictures? THX
This seems like a cool idea. I'm willing to help with some testing if I can catch up. I remember getting this phone a few years back and due its low popularity I never thought it would get rooted. Now that it is I am at a loss of what to do. (I think I may have messed up a few things during my previous attempts at rooting, I can no longer access my security tab and my phone no longer detects the sim card.)
Any tips on how to get it safely backed up? (not that it's in great shape) I tried the TWRP tool and that gave me the option to backup "recovery" and "boot" (not that I really know what those are). I am not sure if it's actually making the files or where I should be storing them or how I would recover from them. I can see the files with ES file explorer but not with windows.
I really need to figure out what I'm doing XD
A TWRP Backup is a nandroid backup, in essential, it took a backup of the whole partitions. The partitions include names that identify them, such as boot, recovery, cache, system, etc.
It is just asking you to restore what partitions you want from your nandroid backup.
Let's say, you updated to a new TWRP version, but it is buggy or something, and you wish to switch back. Simply click "Restore" and select only "recovery" and it should flash your nandroid backup of the recovery partition to your existing recovery partition, and you'll have your old TWRP again.
Since you messed a few things up already, I'd suggest you go with the full nandroid backup, leave everything selected, and click "Restore".
Hopefully you made the backup before you began fiddling too much with your phone!
Rhioun
Any progress at work?
I've tried porting multiple ROMs, looking for compatibility. I've had zero success in getting one to boot up. Either the device goes to a black screen after the primary Sharp Boot Logo, or it boots up TWRP immediately after the Sharp Logo.
I saw how another guy on these forums also made a flashable room for the Sharp Aquos Crystal using Superr's Android Kitchen, so I believe my next trial-and-error phase will lie there. However, before I do that, I plan to use his flashable ROM as a base to port other ROMs, and see if I have any more luck.
Maybe my flashable ROM was invalid somehow.
Anywho, I highly recommend anyone who's interested in porting ROMs for this phone to begin to do so. We have plenty of materials scattered about, and DuckDuckGo is your friend.
Don't hesitate to try.
Thanks, and I'll hopefully keep this thread updated about my progress.
I've working on an Android 5.1 RR ROM from the LG Leon. I've (so far) replaced a majority of firmware files and updated symlinks, dumped vendor files, replaced a few .ko files, edited the build.prop and updater-script, configured the fstab from the ramdisk, copied over the kernel built for the Sharp Aquos Crystal, and rebuilt the boot.img. I customized the updater-script to include chameleon.img, modem.img, and persist.img (partitions that assist with connecting to Sharp, and some kernel configurations).
This has been a lot of tweaking to the ROM, and I tested it and was thoroughly disappointed when my device began to bootloop. (Goes to Sharp 1st boot screen, and reboot, go to 1st boot screen, reboot, etc.). TWRP won't boot when this happens, and holding Volume Down+Power will yield nothing. You can't even power off the device, troubling because the battery is (nigh impossible to remove) not meant to be removed. No matter, although, holding Power Up+Power puts the device in fastboot more (the led will hold solid white) and from there you can successfully power off the device and start up TWRP. Luckily, I made a TWRP backup before I tried flashing the ROM, so I was able to restore back to that. However, I edited a good deal of things, so I just need to know what is causing the bootloop, or maybe then ROM, even ported, is simply incompatible with our Crystals.
I looked around, and found XDA Forums that promote the use of logcat to figure out why a device isn't booting. I am going to try this next, and if it yield nothing, I will find another phone to try porting a ROM from. (We have a good deal with the same processor, shouldn't be too hard.)
Sent from my Aquos Crystal
Still patiently waiting for a ROM. I'm still holding on to this device just because i have been watching this thread and i have hope it will have run custom ROM one day.
Geodripp said:
This seems like a cool idea. I'm willing to help with some testing if I can catch up. I remember getting this phone a few years back and due its low popularity I never thought it would get rooted. Now that it is I am at a loss of what to do. (I think I may have messed up a few things during my previous attempts at rooting, I can no longer access my security tab and my phone no longer detects the sim card.)
Any tips on how to get it safely backed up? (not that it's in great shape) I tried the TWRP tool and that gave me the option to backup "recovery" and "boot" (not that I really know what those are). I am not sure if it's actually making the files or where I should be storing them or how I would recover from them. I can see the files with ES file explorer but not with windows.
I really need to figure out what I'm doing XD
Click to expand...
Click to collapse
Sorry for my reply earlier, I skimmed your post and thought you were trying to RESTORE a backup since your phone was in such terrible condition.
Just to be clear, unless the 306SH gets a new recovery, there is usually no reason to backup "recovery" as that is just backing up your current TWRP.
(Usually used in case a new TWRP version is buggy and you want to restore back to your old one)
However, certainly backup boot as that contains all kernel files and ramdisk settings, and without it, the phone would not 'boot'.
Just backup everything. Leave everything checked. (Unless you're a stickler for space.)
I recently made a flashable Aquos Crystal Stock ROM (seems camera and data and everything work fine) with no carrier-specific apps installed.
I can supply you with that, or, if you'd prefer, I can make a TWRP backup of a factory default 306SH phone and send it your way,
for either of them, just put one on your SD Card and if TWRP Backup, press "restore" and select the backup I provided you with, or for flashable ROM, press "flash" and navigate to it.
There is really no difference between them.
However, some things to note if you do want me to supply you with a backup.
It has SUPERSU preset installed. (I can't change this. It made its way into about everything.) So, if you want to use apps like (Android Pay, Applike), you will have to open SuperSU, and click "UNRoot" and take it off.
I have fixed Kitkat 3rd Party SD Card write privileges, (bug in android 4), and that fix has also seemingly worked itself into my factory default as well. (No disadvantages to it, although..)
Both of these files will fix your issues and supply you with a factory default environment.
If you, or anyone else in this forum would like a factory default TWRP backup, or flashable zip, feel free to say so.
I'm at a standstill. I've gotten my hands on a niche version of CyanogenMod 11, and replacing some vital files, I got it to boot on Sharp Aquos Crystal.
However, files I replaced were apk's, system ui, libs, and breaks some (most) functionality of Cyan 11.
I need a boot log tool of sorts so I can replace files, do a boot log, figure out what is causing a boot loop, or forever boot, and fix it.
I looked online, and everyone is all about the logcat. However, I tried this and it says "waiting for device".
So the device does not reach booting adb daemon.
I need a tool that will save a boot log.txt to the SD card at boot, (I imagine init.rc ) so that I may debug the ROM and then use the working ROM (and logging tool) to port more recent ROMs.
Anyone know of any such logging facility/tool?
keep it up
Does anyone know of a boot debugging/logging tool? There must be one. Please reply to this forum or PM me about one, as I do need one.
It is vital to building a ROM, rather than stupidly copy-pasting and blind guessing playing at Roulette trying to get the ROM to work.
Please. I need one.