Related
Hi Guys,
I've been flashing for a few years (Desire HD, Sensation XE, One X) and now I have a One X+
I've been treading water carefully and I've managed unlock the bootloader, flash TWRP and rooted the device (via TWRP)
I did all this the manual way as I'm skeptical of the all in one (I'm old fashioned like that)
However I have some questions:good:
1. Does having TWRP, the bootloader unlocked affect my ability to receive OWA updates? (I'm still running stock ROM)
2. All that's left now is to do a backup, get a ROM , copy the ROM over, go into recovery, flash the boot.img, wipe the phone then flash the new ROM?
Cheers guys
If you are old fashioned, then why do you go for TWRP not the CWM?
1. This should not affect the ability for the OTA, but I'm not 100% sure.
2. Yes, you do a backup, flash the boot.img, wipe the phone and flash the new rom. Or first you can wipe and install ROM, then reboot in to bootloader and flash boot.img. You can do both ways in TWRP, does not matter. But to not reboot in to rom before you flash both.
Synoptex said:
If you are old fashioned, then why do you go for TWRP not the CWM?
Click to expand...
Click to collapse
Why should he go for an untested, unreliable, unsupported and outdated recovery?
TWRP was again updated couple days ago, I strongly suggest to stick with the TWRP recovery.
I don't know... if he is as he call himself "old fashioned" - CMW if far older recovery, that TWRP. I don't know about the updates, may be there is nothing to update, so they stopped? And TWRP still has some bugs, so everyone waiting for updates. I don't know... all about old fashioned, that was my point.
Synoptex said:
I don't know... if he is as he call himself "old fashioned" - CMW if far older recovery, that TWRP. I don't know about the updates, may be there is nothing to update, so they stopped? And TWRP still has some bugs, so everyone waiting for updates. I don't know... all about old fashioned, that was my point.
Click to expand...
Click to collapse
I went with TWRP because it seems it's the more popular choice, I didn't vouch for the all in one tool kit because I like to do this the manual way.
Currently got a stock ROM, with ROOT + TWRP. I haven't flahsed yet due to the number of issues I see appearing on this forum with so called 'bricked' devices, there was never this many for the desire hd/sensation/One x.
I'm pretty sure the way to flash from this point would be
1. Download ROM and place it on the phone
2. Take a backup via recovery
3. Flash boot.img
4. Wipe phone
5. Install ROM
6 Reboot
Does this sound correct?
just remember NEVER wipe "internal storage" or "format data" within recovery
ratcom said:
just remember NEVER wipe "internal storage" or "format data" within recovery
Click to expand...
Click to collapse
Cheers Ratcom, I'm currently waiting on CM 4.2.2 to be uploaded, they currently only have the 4.2.1 build.
Sounds good.
Sent from my HTC One X+ using xda premium
clarkey02 said:
I went with TWRP because it seems it's the more popular choice, I didn't vouch for the all in one tool kit because I like to do this the manual way...
... I haven't flahsed yet due to the number of issues I see appearing on this forum with so called 'bricked' devices, there was never this many for the desire hd/sensation/One x.
Click to expand...
Click to collapse
This is assuredly in direct relation with the majority of those cases.
People want to root and customize with a Swiss knife tool and I can assure you that something is wrong to do it with this tool. If you read all the so called "bricked my..." threads, they all were using this all in one tool, then something wen't wrong and they can't figure out what could be the cause simply because they haven't read, they don't know the basics of those procedures or they don't have any king of prerequisite installed in their computer. The tool is supposedly "doing all for them". Except debugging the procedure when everything goes bad.
It is so simple and rewarding to do all this -the old fashioned way- also if something suddenly goes bonk, it's so easy to know exactly where the procedure is failing.
----
As for your procedure it is all good, in Recovery when you have a backup of your actual ROM, in the Wipe menu select Factory Reset, then after select System. You're all good to flash your new ROM after that.
Don't forget to : fastboot erase cache after your boot.img flashing.
Have fun!
Lucky Thirteen said:
----As for your procedure it is all good, in Recovery when you have a backup of your actual ROM, in the Wipe menu select Factory Reset, then after select System. You're all good to flash your new ROM after that.
Don't forget to : fastboot erase cache after your boot.img flashing.
Have fun!
Click to expand...
Click to collapse
I've got to the point now where I've got CM10 on the phone (not installed) and I've got the boot.img in the same folder as the fastboot.
If memory servers me correctly:
I should boot into recovery
hit fastboot
flash the boot.img via command line
go into recovery
factory reset/wipe cache
install ROM
reboot
Apologies if I'm being very tentative, I'm just making sure. I have done a backup while in TWRP (If the flash goes wrong can I simply restore from recovery using that backup?)
I'm into two minds to do this, I miss installing custom ROM's but I don't want to ruin the phone. If only there was a video tutorial !!!!!
You should have all you need in this tutorial watch the last section of it.
Lucky Thirteen said:
You should have all you need in this tutorial watch the last section of it.
Click to expand...
Click to collapse
I attempted and successfully flashed today, currently running CM10 unofficial (Is there an official version? for X+?)
Cheers again for all the pointers!
clarkey02 said:
I attempted and successfully flashed today, currently running CM10 unofficial (Is there an official version? for X+?)
Cheers again for all the pointers!
Click to expand...
Click to collapse
if you want official go ahead and make it official..
Lloir said:
if you want official go ahead and make it official..
Click to expand...
Click to collapse
Thanks
I just wiped internal storage and formatted data...!!
ratcom said:
just remember NEVER wipe "internal storage" or "format data" within recovery
Click to expand...
Click to collapse
I didn't know that I can't wipe internal storage and format data... I was trying install a SlimBean Rom. It tells me to "wipe data, format system (in mounts and storage). I clearly misunderstood it. What should I do now? PLEASE HELP ME!! I have to install zip files from my sdcard, but now I can't find any of them! :crying: Is my phone bricked yet? Is there anything I can do to get my phone back? Please, please help me. I'm new at this. I just bought this HTC One X+ not long ago... :crying:
Narakera said:
I didn't know that I can't wipe internal storage and format data... I was trying install a SlimBean Rom. It tells me to "wipe data, format system (in mounts and storage). I clearly misunderstood it. What should I do now? PLEASE HELP ME!! I have to install zip files from my sdcard, but now I can't find any of them! :crying: Is my phone bricked yet? Is there anything I can do to get my phone back? Please, please help me. I'm new at this. I just bought this HTC One X+ not long ago... :crying:
Click to expand...
Click to collapse
Hi Narakera, I have answered that issue in this thread, have a read and if something is not clear ask in that thread I will try to help you.
Lately i'm experiencing problems with flashing custom roms (i.e. UltimaROM , Xperianze, whatever)
What i did is:
1: flash the latest CWM , touch and non -touch with Odin
2: download ROM of choice , copy to internal SD-card
3: reboot recovery, fact-reset, wipe cache + dalvik
4: flash rom ( with aroma installer )
5: boot phone
with booting it keeps hanging on the Samsung i9300 logo txt. It doesnt matter which rom i flash. it always keeps hanging.
I've tried alternative methods like flashing TWRP and do the same as above but again, no success. I also tried factory-reset after flash, cache wipe etc. no success.
The weirdest thing is: when i try to flash CM or MIUI ( current running MIUI ) , it works like a charm, but normal "custom" roms are not approved it seems.
does anyone have a suggestion for me what to do? or explain what i am doing wrong , or even better, can explain why CM-based ROMS work?
Have you checked the MD5 of your downloaded ROMs when they are on your SD card? Format system, data and pre-load before flashing? Tried flashing an alternative kernel/radio before you boot the first time?
If only stock based ROMs are a problem then it maybe something that is unique to them, probably a direct hardware hit via the kernel.
Try returning completely to stock to test, flashing Samsung's vanilla EMB5 via Odin - including stock recovery and full wipe. If that doesn't work then you may have a hardware issue that CM or MIUI doesn't use.
yeah good idea to return to stock and try all over again.
to your other questions: no i didnt flash another kernel after i flashed the custom rom. i've tried with several kernels which options were given to me in aroma installer ( boeffla, syah, stock )
md5: did that
format system and data: nope. kinda relied on the fact-reset + cache/dalvik
what do u mean with pre-load?
if I were you I would format data & system again manually after the fac. reset thing, or even more clean use the mega wipe flashable zip to have a clean slate to start from (it will format anything but the ext. sd-card). Then flash the rom from your ext. sd-card and see how it goes.
additional possibly helpful hints
hi there,
i'm not entirely sure if this will help you but generally speaking i came made a few observations about the fact that some people, mostly repeatingly the same users, encounter problems with their custom roms and/or flashing them, while others don't, albeit they are using the same devices.
i my selfe use 3 different devices, all rooted and running on pac 4.3, always lates nightly, as there are GT-N7100 - GT-I9100 - Nexus 4
not to the point
a) other than most other users i usually clean cache and dalvik cache as well before and after flashing the new rom and/or new nightly
and never encountrer any problems except those which everybody, using the same rom and nightly encounters.
b) whenever i flash an totally different rom and/or upgrade and/or downgrade to another level of android os, i.e. from 4.2.2 to 4.3, i perform
a clean install, including not only a factory reset, but as well a format sd-card, format cache and format system etc., again i cannot proof
which of these steps make a or the differnce but however, i never have problems others than thosw which everyone has with a version.
c) when using cusome kernels and due to the fact that some roms come with a kernel included, as well as with a custom recovery included,
it is strongly recommended not to forget to flas the kernel again after each flashing the new rom. one good example ist dorimanx kernel
for GT-I9100 which will not boot into recovery and reluctantly boot at all after a new flash of a pac nightly without reflashing the kernel.
d) try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
why that should, but however, sometimes it's better to be on the safe sid.
e) try to run whether the lastes version of custom recovery for your device, and or the use the included custom recovery of the rom or the
kernel. this again is one thing that can help to avoid some unexpected and hard to explain bootproblems and/or fc's etc.
hope that i could give you some new ideas how to avoid trouble while using custom roms and other hacks
magnamentis said:
try to fix permissions on reboot instead of doing it from recovery. one reason is that not every recovery has this option and further i
found that when fixing permissions before the first boot after flashing a new rom, there might be bootloops, albeit i cannot explain exactly
Click to expand...
Click to collapse
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
rootSU said:
Fix permissions was removed because its useless. All permissions are set when flashing by way of updater-script. Fix permissions via recovery "guesses" the permissions which causes issues...
If permissions need fixing, then the updater-script is poor which means you should probably avoid flashing it.
Sent from my GT-I9300 using Tapatalk 4
Click to expand...
Click to collapse
thanks for the explanation which makes totally sense, so my feeling which i could not explain was right always better to learn exactly why than just guessing
no thanks button found in your post however, so i want to thank you this way.
regards
I try to install Lineage 14.1 but I can't because It says wrong bootloader, and that my bootloader is unknown. I installed lollipop by flashing the system.img image and the boot.img image because I had no ROM installed because my internal storage and SD card got corrupt or something. Can anyone help me by supplying a Lineage 14.1 backup or a LineageOS system.img and boot.img file? Thanks in advance...
Wrong bootloader . . .?????
I think the issue you are having is what I was having, and that is that you are not COMPLETELY wiping the previous operating system. Use TWRP's advanced features to make sure you do a complete wipe.
Can someone tell me if you use the advance wipe and wipe the system if that solved the bootloader error, I am concerned because once you wipe the system you have nothing to go back to if it doesnt work
Billc47 said:
Can someone tell me if you use the advance wipe and wipe the system if that solved the bootloader error, I am concerned because once you wipe the system you have nothing to go back to if it doesnt work
Click to expand...
Click to collapse
I was getting the same error the user above was until I used TWRP's advanced wipe and got rid of everything. Of course make sure you do a backup of whatever you currently have working just in case, but once I did an advance wipe I was able to installed Cyanogen. I however still cannot get Lineage 14.1 to work, it simply gets into an install loop. But since your question was about the boot loader, once I did the complete wipe the error message you are referring to went away for me.
thank you for your reply
hi i am from india and huge fan of huawei i got this phone from usa(mt2-l03) i rooted the phone using some one click root tool and tried to flash twrp which ended in saying recovery image failed,please update to the authorized images.however as there was was root i changed the dpi(think 420) now the phone screen is blank(only in the system ui not the boot image or vendor image(huawei)) i am having the imei and s/n at the battery but i dont have the product id so is there any way i can get the product id and unlock the bootloader of my phone or is there any way to repair my phone
In the general area, in the stickies there are many options you might try. This one https://forum.xda-developers.com/as...to-fix-soft-bricked-phone-using-twrp-t2886630. Seems like it might be the way out for you but I'm not a dev or an expert, just someone who's screwed up his phone alot and found fixes in that section
Sent from my MT2L03 using XDA-Developers Legacy app
Here's a quick guide to some of the basics.
Which recovery.
----------------------------
Use the latest from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
Do not use Orange Fox unless you intend to stick with stock MIUI. Orange Fox has extra features, which are almost all aimed at MIUI, but it often causes issues flashing custom ROMs, so it's a long way from the best option if you want to use custom ROMs. Orange Fox, along with other TWRP derivatives, allow complete access to virtually all of the phone, so it is very easy to accidentally hard brick the phone if you don't fully understand what your doing.
Ignore anyone who tells you to use Orange Fox when using custom ROMs.
Do I need to permanently disable encryption
-------------------------------------------------------------------------
No.
There is not a single reason to permanently remove encryption, other than personal preference.
It is recommended to have encryption removed when flashing, but this is easily done by temporarily removing lock screen security before flashing and adding it back after.
Ignore anyone who tells you that you need to flash a DFE (disable force encrypt) script.
Should I wipe all my partitions when flashing
------------------------------------------------------------------------------
No.
When clean flashing you only need to do a factory reset in TWRP.
There is absolutely no need to wipe system or vendor partitions. Ordinarily, when flashing, there is no need to go into the advanced wipe menu. I've had this phone 15 months and have never used the advanced wipe menu and have never had any issues.
When you flash a custom ROM, it will automatically wipe system first, so you don't need to do this yourself.
When you flash a vendor file, it will automatically wipe vendor first, so you don't need to do this yourself.
Even though almost all (it may actually be all) ROM flashing instruction tell you to wipe system, it is not needed.
Ignore anyone who tells you to wipe anything more than data, cache and dalvik.
Do I need to update my vendor and firmware when flashing a new ROM
-----------------------------------------------------------------------------------------------
Probably not.
If you currently have MIUI installed and it's up to date, then you will have the latest firmware and vendor and won't need to flash them.
If you're moving from one custom ROM to another, then it depends on how up to date your current ROM is. If the vendor and firmware requirements of the new ROM match the requirements of your current ROM, then will have the current vendor and firmware already installed and so do not need to flash them again.
Only when the new ROM needs a later version of vendor and firmware than you have currently installed will you need to flash them. This isn't such a common occurrence, so you'll not need to flash vendor and firmware often.
How to install a custom ROM over MIUI and remain encrypted
-------------------------------------------------------------------------------------------------
Assuming you have already unlocked the bootloader.
1 Boot into fastboot
2 Flash TWRP (fastboot flash recovery <path to TWRP file>
3 Immediately boot to TWRP (fastboot oem reboot-recovery)
4 Select Wipe Menu and Factory Reset
5 Return to Wipe Menu and Format Data
6 Return to Main Menu, then select Boot Menu
7 Select Boot to Recovery (this reboots TWRP to ensure the data partition is properly mounted after formatting)
8 Copy ROM and extras over to phone and flash them.
9 Reboot and enjoy.
Do not add any extra steps, do not miss any steps out
How to dirty flash a custom ROM update when encrypted
---------------------------------------------------------------------------------------------
1 Remove lockscreen security (this removes encryption)
2 Boot to TWRP
3 Flash the ROM update (plus vendor and firmware if the requirements for these have changed in the updated ROM)
4 Select to wipe cache and dalvik when the update finishes.
5 Reboot the ROM
6 Restore lockscreen security
How to clean flash a new custom ROM over another custom ROM
--------------------------------------------------------------------------------------------------------
1 Remove lockscreen security
2 Boot to TWRP
3 Select Wipe Menu and Factory Reset
4 Flash the ROM plus the extras you want (this includes new vendor and firmware if the requirements are different to your current ROM)
5 Reboot the ROM
6 Add lockscreen security
Thank you
Thank you very much for this. I just bought the device last week . Since i am upgrading from a lenovo vibe k5 plus (which also had a decent amountt of development support) i have a few questions. With the vibe k5 plus, installing a custom rom was very simple. flash cutsom recovery-factory reset (i used to wipe the internal storage too)-flash custom rom-flash magisk and you're done. My question(s) are 1) What is this "Force encryption" that we have to disable/keep enabled. 2) what are vendors and firmwares. I'm currently on MIUI10 (Got a Nov 2019 unit), it's pretty decent for now.
AkashNP said:
Thank you very much for this. I just bought the device last week . Since i am upgrading from a lenovo vibe k5 plus (which also had a decent amountt of development support) i have a few questions. With the vibe k5 plus, installing a custom rom was very simple. flash cutsom recovery-factory reset (i used to wipe the internal storage too)-flash custom rom-flash magisk and you're done. My question(s) are 1) What is this "Force encryption" that we have to disable/keep enabled. 2) what are vendors and firmwares. I'm currently on MIUI10 (Got a Nov 2019 unit), it's pretty decent for now.
Click to expand...
Click to collapse
Since, I think, Android Marshmallow, Google have added forced encryption. Before this you had the security menu option to encrypt your phone storage, which required a separate password to be entered on every reboot. Now encryption is done as standard and uses your lockscreen security PIN/password as the key.
Initially your phone will be unencrypted, but as soon as you first set-up lockscreen security the phone will be automatically encrypted.
Many people see this as a good thing. Should you lose the phone, you data is secure and cannot be accessed without the lockscreen PIN/password. Other people don't care about this and so prefer to disable encryption, as it makes life a little easier when flashing custom ROMs.
Some people, incorrectly, believe that disabling encryption is necessary when flashing custom ROMs, or that disabling encryption is the only solution to problems seen when flashing. This is not true and disabling encryption should only be about a users personal choice to be unencrypted.
Think of vendor and firmware as the equivalent to device drivers for PC components. They are a collection of compiled code files, provided by component manufacturers and the phone manufacturer, to allow Android to communicate with the hardware components in a standard way. Occasionally these files might get updated, as part of a MIUI update, to fix a bug or to add extra functionality. When these files are updated, custom ROM devs will include them so that they get the bug fixes or extra functionality. When this happens they will update the minimum vendor and firmware version requirements for their custom ROM - the version will be the actual MIUI version in which the vendor and firmware files were updated.
Thanks that was a really good explanation. I have one last question, so right now I'm on MIUI10 I've got the MIUI12 update notification but I want to try MIUI11 first. I've got the ROM file from the xiaomifirmwareupdater website, how do I flash it?
AkashNP said:
Thanks that was a really good explanation. I have one last question, so right now I'm on MIUI10 I've got the MIUI12 update notification but I want to try MIUI11 first. I've got the ROM file from the xiaomifirmwareupdater website, how do I flash it?
Click to expand...
Click to collapse
Follow this guide, assuming you've downloaded the recovery ROM.
https://c.mi.com/oc/miuidownload/detail?guide=1
If you view this on a mobile, it might be a blank page. In this case, you need to change the mobile browser to desktop mode when viewing this page.
The most simplest and right guide on the xda forum, well done! Thank You
Noob here
Are decrypted devices faster? Also please suggest stable roms. Also has anyone used 81hz extensively? Does it damage screen? Does it drain more battery?
jaydeep0712 said:
Are decrypted devices faster? Also please suggest stable roms. Also has anyone used 81hz extensively? Does it damage screen? Does it drain more battery?
Click to expand...
Click to collapse
As far as I'm aware, there shouldn't be any noticeable difference in speed. The whole data partition is encrypted as a block, so, in use, accessing files is done on an already unencrypted partition. The individual files are not encrypted/decrypted on demand on an individual basis.
All of the popular ROMs will be stable enough for daily use. Which one to go for depends on what you prefer - more AOSP, more Pixel Phone, more heavily customisable, etc., etc.
I've never gone for the screen refresh rate mods, so can't comment on them.
Thanks for replying.
Robbo.5000 said:
All of the popular ROMs will be stable enough for daily use. Which one to go for depends on what you prefer - more AOSP, more Pixel Phone, more heavily customisable, etc., etc.
Click to expand...
Click to collapse
Which custom rom do you use? Does it have any bugs (Like under screen fingerprint not working)?
jaydeep0712 said:
Which custom rom do you use? Does it have any bugs (Like under screen fingerprint not working)?
Click to expand...
Click to collapse
I'm currently using LOS. It's mostly bug free. There seems to be a current issue with wired headphones - on calls it is using the phone mic instead of the headphone mic. For my use, I don't see any other issues, but there could be other things around functionality I don't use.
Fingerprint recognition is about as good as it gets on custom ROMs. Not quite as good as MIUI, but good enough.
Thank you so much for busting so many myths, I was dying for someone to speak up but couldn't muster the courage myself. Hats off, and I support everything you said 100%.
Robbo.5000 said:
With the latest Flipkart sale, there have been a number of new owners asking a lot of old questions.
Here's a quick guide to some of the basics.
Which recovery.
----------------------------
Use the latest from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
Do not use Orange Fox unless you intend to stick with stock MIUI. Orange Fox has extra features, which are almost all aimed at MIUI, but it often causes issues flashing custom ROMs, so it's a long way from the best option if you want to use custom ROMs.
Ignore anyone who tells you to use Orange Fox when using custom ROMs.
Do I need to permanently disable encryption
-------------------------------------------------------------------------
No.
There is not a single reason to permanently remove encryption, other than personal preference.
Ignore anyone who tells you that you need to flash a DFE (disable force encrypt) script.
Should I wipe all my partitions when flashing
------------------------------------------------------------------------------
No.
When clean flashing you only need to do a factory reset in TWRP.
There is absolutely no need to wipe system or vendor partitions. Ordinarily, when flashing, there is no need to go into the advanced wipe menu. I've had this phone 15 months and have never used the advanced wipe menu and have never had any issues.
When you flash a custom ROM, it will automatically wipe system first, so you don't need to do this yourself.
When you flash a vendor file, it will automatically wipe vendor first, so you don't need to do this yourself.
Even though almost all (it may actually be all) ROM flashing instruction tell you to wipe system, it is not needed.
Ignore anyone who tells you to wipe anything more than data, cache and dalvik.
How to install a custom ROM over MIUI and remain encrypted
-------------------------------------------------------------------------------------------------
Assuming you have already unlocked the bootloader.
1 Boot into fastboot
2 Flash TWRP (fastboot flash recovery <path to TWRP file>
3 Immediately boot to TWRP (fastboot oem reboot-recovery)
4 Select Wipe Menu and Factory Reset
5 Return to Wipe Menu and Format Data
6 Return to Main Menu, then select Boot Menu
7 Select Boot to Recovery (this reboots TWRP to ensure the data partition is properly mounted after formatting)
8 Copy ROM and extras over to phone and flash them.
9 Reboot and enjoy.
Do not add any extra steps, do not miss any steps out
How to dirty flash a custom ROM update when encrypted
---------------------------------------------------------------------------------------------
1 Remove lockscreen security (this removes encryption)
2 Boot to TWRP
3 Flash the ROM update (plus vendor and firmware if the requirements for these have changed in the updated ROM)
4 Select to wipe cache and dalvik when the update finishes.
5 Reboot the ROM
6 Restore lockscreen security
How to clean flash a new custom ROM over another custom ROM
--------------------------------------------------------------------------------------------------------
1 Remove lockscreen security
2 Boot to TWRP
3 Select Wipe Menu and Factory Reset
4 Flash the ROM plus the extras you want (this includes new vendor and firmware if the requirements are different to your current ROM)
5 Reboot the ROM
6 Add lockscreen security
Click to expand...
Click to collapse
Good Day!
I installed Pixel Experience over MIUI and its stuck on Loading with Google Logo in it, it has been 30mins aprox after i first booted the device, any suggestion?
Or should i continue waiting?
Thanks in advance
XXXLR8 said:
Good Day!
I installed Pixel Experience over MIUI and its stuck on Loading with Google Logo in it, it has been 30mins aprox after i first booted the device, any suggestion?
Or should i continue waiting?
Thanks in advance
Click to expand...
Click to collapse
The first boot will take a bit longer, but only a minute or 2 at most. Something has gone wrong. Make sure you follow the guide exactly.
The most common issue is not formatting the data partition. This is not the same as wiping the partition. When formatting TWRP will ask you to type 'yes' to continue. When flashing over MIUI this is necessary to fully remove encryption before flashing.
Another common problem is wiping partitions unnecessarily. There is no need to wipe anything. Just do the factory reset, this wipes what's needed and nothing more, then format data.
Robbo.5000 said:
The first boot will take a bit longer, but only a minute or 2 at most. Something has gone wrong. Make sure you follow the guide exactly.
The most common issue is not formatting the data partition. This is not the same as wiping the partition. When formatting TWRP will ask you to type 'yes' to continue. When flashing over MIUI this is necessary to fully remove encryption before flashing.
Another common problem is wiping partitions unnecessarily. There is no need to wipe anything. Just do the factory reset, this wipes what's needed and nothing more, then format data.
Click to expand...
Click to collapse
I did the TWRP format (which prompted me to type yes to continue) and wipe data partition,but didnt wipe the partition itself, rebooted, installed pixel experience, and still same, i even got into a boot loop, which i got out to, by forcing my way out by fastboot, and reinstalled MIUI,
Im currently at MIUI, currently stable.
So Im going to try again some other time about this, when i have another available device to use while i reinstall pixel experience in Mi9T Pro
But, your guide is helpful, it failed on me probably because of a mistake I made.
Thanks anyways!
Best Regards.
hi,
in your guide, you do not have added a step for flashing the vendor.
is this intended ?
FuriousFrodo said:
hi,
in your guide, you do not have added a step for flashing the vendor.
is this intended ?
Click to expand...
Click to collapse
Flashing over MIUI, I've made the assumption that you'll be on the latest version of MIUI and the original region, which should therefore already have an appropriate vendor and firmware for the new ROM.
If you've not kept MIUI up to date or have flashed a different region of MIUI, then you may need to flash the correct vendor and firmware file(s)
Robbo.5000 said:
Flashing over MIUI, I've made the assumption that you'll be on the latest version of MIUI and the original region, which should therefore already have an appropriate vendor and firmware for the new ROM.
If you've not kept MIUI up to date or have flashed a different region of MIUI, then you may need to flash the correct vendor and firmware file(s)
Click to expand...
Click to collapse
thanks for that. i followed as you said and i was able to flash Evolution X
however, while flashing i got a warning in TWRP E:Unable to decrypt FBE device. The ROM booted fine but I think I have made a mistake. Additionally the folder I had created to transfer the ROM is gone after the phone booted.
What could be the issue ? and how to resolve this ?
FYI, I'm using Mauroonofrio's TWRP
FuriousFrodo said:
thanks for that. i followed as you said and i was able to flash Evolution X
however, while flashing i got a warning in TWRP E:Unable to decrypt FBE device. The ROM booted fine but I think I have made a mistake. Additionally the folder I had created to transfer the ROM is gone after the phone booted.
What could be the issue ? and how to resolve this ?
FYI, I'm using Mauroonofrio's TWRP
Click to expand...
Click to collapse
I've had that error a few times. It's normally from when your first boot into TWRP. All output from TWRP gets written to the same output screen, so when it is shown you are not seeing output from just the last command but for the whole session. If you had looked in more detail, you would have probably realised that the error was from before you started flashing.
With the ROM files going missing, that is a known problem. Actually anything copied before flashing gets lost. The first time it happened to me I had copied all my backed up data at the same time as the ROMs and it all got wiped. I can't remember exactly the details now, it's just something I've got used to. But if I remember correctly, the data disappears when you first boot into the new ROM. After it happened the first time, I checked in TWRP the next time, after flashing, but before booting the new ROM and the files were still there. It was only after booting to the ROM that they disappeared. (My memory is a bit vague now as it was over a year ago, but I think it might actually happen when you set up lockscreen security and the phone is encrypted in the new ROM for the first time). Maybe someone else can confirm or give the correct explanation.
Robbo.5000 said:
I've had that error a few times. It's normally from when your first boot into TWRP. All output from TWRP gets written to the same output screen, so when it is shown you are not seeing output from just the last command but for the whole session. If you had looked in more detail, you would have probably realised that the error was from before you started flashing.
With the ROM files going missing, that is a known problem. Actually anything copied before flashing gets lost. The first time it happened to me I had copied all my backed up data at the same time as the ROMs and it all got wiped. I can't remember exactly the details now, it's just something I've got used to. But if I remember correctly, the data disappears when you first boot into the new ROM. After it happened the first time, I checked in TWRP the next time, after flashing, but before booting the new ROM and the files were still there. It was only after booting to the ROM that they disappeared. (My memory is a bit vague now as it was over a year ago, but I think it might actually happen when you set up lockscreen security and the phone is encrypted in the new ROM for the first time). Maybe someone else can confirm or give the correct explanation.
Click to expand...
Click to collapse
So what you are saying is its quite normal, is it?
fearing I may have to do the whole process again, I haven't set anything up.[emoji3]
Sent from my [device_name] using XDA-Developers Legacy app
FuriousFrodo said:
So what you are saying is its quite normal, is it?
fearing I may have to do the whole process again, I haven't set anything up.[emoji3]
Click to expand...
Click to collapse
Yes, both things are normal. You should be good to go with your new ROM. No need to reinstall it.
I have a Sony Xperia XZ Premium and i decided to enter the world of tinkering with my device. I successfully unlocked by bootloader, installed TWRP but as i was figuring out how it all worked something went wrong. i can no longer boot into my device (its stuck on the sony/carrier boot screen) and i belive that i may have completely removed by OS from my device. A website told me that i should to something with changing the file system and i think that has something to do with it. I have tries re-installing a stock rom but i cant seem to get it to work (I am noob). When i try to flash the zip it says 'invalid zip file format!' i really dont know what to do. Any help would be grealty appreciated as this is my only phone. I dont care if it has to be reset to factory settings.
THANK YOU.
jakessavage said:
I have a Sony Xperia XZ Premium and i decided to enter the world of tinkering with my device. I successfully unlocked by bootloader, installed TWRP but as i was figuring out how it all worked something went wrong. i can no longer boot into my device (its stuck on the sony/carrier boot screen) and i belive that i may have completely removed by OS from my device. A website told me that i should to something with changing the file system and i think that has something to do with it. I have tries re-installing a stock rom but i cant seem to get it to work (I am noob). When i try to flash the zip it says 'invalid zip file format!' i really dont know what to do. Any help would be grealty appreciated as this is my only phone. I dont care if it has to be reset to factory settings.
THANK YOU.
Click to expand...
Click to collapse
First, let's start with the small stuff, just in case. Try booting into TWRP and select the Wipe option, then select advanced wipes, then choose only the cache partition and the dalvik cache partition, DO NOT choose any other partitions, after choosing cache and dalvik cache, swipe the slidee at the bottom to run the wipes, then reboot the device.
The stock .zip that you tried to flash probably isn't made for flashing via TWRP. It is probably meant for extracting the .zip to get the flashable form of your stock firmware and then flashing that firmware using your device's specific flashing tool on PC. Flashing the firmware will remove TWRP. After you get the firmware flashed and you get the device working again, you will have to reinstall TWRP the same way you did the first time. When you get TWRP reinstalled, immediately use the Backup option in TWRP to create a backup of everything on your device(do not include internal storage in the backup). Store that backup on your external sdcard and/or on your PC. Do this BEFORE you attempt any kind of modification ms to the device. This backup can be used to restore your device if you mess it up again.
After creating the backup and storing it in a safe place, then you can try making the modifications that you were originally trying to do.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
First, let's start with the small stuff, just in case. Try booting into TWRP and select the Wipe option, then select advanced wipes, then choose only the cache partition and the dalvik cache partition, DO NOT choose any other partitions, after choosing cache and dalvik cache, swipe the slidee at the bottom to run the wipes, then reboot the device.
The stock .zip that you tried to flash probably isn't made for flashing via TWRP. It is probably meant for extracting the .zip to get the flashable form of your stock firmware and then flashing that firmware using your device's specific flashing tool on PC. Flashing the firmware will remove TWRP. After you get the firmware flashed and you get the device working again, you will have to reinstall TWRP the same way you did the first time. When you get TWRP reinstalled, immediately use the Backup option in TWRP to create a backup of everything on your device(do not include internal storage in the backup). Store that backup on your external sdcard and/or on your PC. Do this BEFORE you attempt any kind of modification ms to the device. This backup can be used to restore your device if you mess it up again.
After creating the backup and storing it in a safe place, then you can try making the modifications that you were originally trying to do.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
After clearing the 2 caches the phone is still stuck on the boot screen. I will try to figure out how to flash the ROM with flash tools now...
jakessavage said:
After clearing the 2 caches the phone is still stuck on the boot screen.
Click to expand...
Click to collapse
Your phone's Android 7 has neither a Dalvik cache nor an ART cache. TWRP is misleading in this respect.
Try to re-flash phone's Stock ROM ( Android 7 ) by means of Sony Xperia Flash Tool.
jwoegerbauer said:
Your phone's Android 7 has neither a Dalvik cache nor an ART cache. TWRP is misleading in this respect.
Try to re-flash phone's Stock ROM ( Android 7 ) by means of Sony Xperia Flash Tool.
Click to expand...
Click to collapse
Yes I managed to do this. The only problem now is that my phone is on Android 7. Before it was on Android 9. I've went to the software update section on the phone but there's no update available. Will I have to flash an android 9 ROM to get the update or will it eventually come to my phone
Thanks
@jakessavage
Moving from one Android version ( e.g. 7 ) to another one ( e.g. 9 ) istn't an update but an upgrade.
Don't think your phone's OEM/Carrier automatically supply an upgrade, but only updates if recognized to be necessary.
IMHO in case of Android 9 for your phone is not provided by OEM/Carrier, you have to flash a Custom ROM based on Android 9.
jakessavage said:
Yes I managed to do this. The only problem now is that my phone is on Android 7. Before it was on Android 9. I've went to the software update section on the phone but there's no update available. Will I have to flash an android 9 ROM to get the update or will it eventually come to my phone
Thanks
Click to expand...
Click to collapse
Find the android 9 firmware for your device and flash it via flashtool.
Sent from my SM-S767VL using Tapatalk