Related
Hi
So yesterday I was trying to install TWRP recovery in order to install Cyanogenmod 11 on Xperia S , I followed a tutorial on techglen, the problem is that now I only have the recovery on my phone , it boots instead of the system , the system files are still there but I can't boot on it , If i connect my phone to my computer I can't access the storage even if I mount it using TWRP
So i have some questions
Is my phone broken?
Instead of flashing a .elf file i flashed the .img instead , is that the source of the problem? ( i didn't do it on purpose , but i didn't pay attention :/ )
can i flash the boot.img of the old system to get it back on booting ?
If there's a way of pushing the CM11 into my phone and installing it would that fix my problem?
Can i use flash tool to flash my old system back ?
Hi,
do you have the zip file of your custom rom on internal stockage ?
(browse file with 'Install" on TWPR)
If yes, you just have to flash it with TWPR.
Here's what I did (will do a clean install and delete previous setting, contact, app data ...) :
- Download ROM + Gapps and copy to sdcard (internal stockage)
- Flash boot.img with FlashTool
- Reboot on recovery (TWPR)
- Factory Reset (Wipe --> "Switch to Factory Reset")
- Format System (Wipe --> Advanced Wipe --> Select System)
- Install New ROM (Install and choose Zip)
- Reboot on ROM to set basic settings
- Reboot on recovery to Flash Gapps
- Wipe Cache (Wipe --> Advanced Wipe --> Select Cache)
- Reboot on System
If you don't have zip file on internal stockage, you may go back first on Stock Rom with FlashTool.
Flash stock ftf(6.2.b.1.96), you can easily find it using search function.
Then you can do like I explained.
jeremux said:
Hi,
If you don't have zip file on internal stockage, you may go back first on Stock Rom with FlashTool.
Flash stock ftf(6.2.b.1.96), you can easily find it using search function.
Then you can do like I explained.
Click to expand...
Click to collapse
Well thanks a lot for your answer man !
when i put on flash mode and try to flash it with flashtool , the phone leaves flash mode after like 40 seconds
I tried installing the drivers ( from flashtool/drivers ) but it didn't change anything :/
Do not confused Fastboot and Flashmode.
Normaly you just have to :
(I guess your tft is already in "firmwares" folder of FlashTool)
- start FlashTool (with Administrator Rights on Windows)
- clic on "Flash device"
- select "Flashmode"
- select all file in "Content"
- clic on "Flash"
- your xperia s must be poweroff and unpluged
- Press the back button (still powered off)
- Then plug the USB cable
After that your phone boot in Flashmode and flashing start.
If they don't work, what is the error ?
ImSoFresh said:
Well thanks a lot for your answer man !
when i put on flash mode and try to flash it with flashtool , the phone leaves flash mode after like 40 seconds
I tried installing the drivers ( from flashtool/drivers ) but it didn't change anything :/
Click to expand...
Click to collapse
Don't put your device on flashmode until flashtool tell you because flashtool takes about 1 minute and 20 seconds to finish extract ftf file
Sent from my LT26ii using XDA Premium 4 mobile app
ImSoFresh said:
Hi
So yesterday I was trying to install TWRP recovery in order to install Cyanogenmod 11 on Xperia S , I followed a tutorial on techglen, the problem is that now I only have the recovery on my phone , it boots instead of the system , the system files are still there but I can't boot on it , If i connect my phone to my computer I can't access the storage even if I mount it using TWRP
So i have some questions
Is my phone broken?
Instead of flashing a .elf file i flashed the .img instead , is that the source of the problem? ( i didn't do it on purpose , but i didn't pay attention :/ )
can i flash the boot.img of the old system to get it back on booting ?
If there's a way of pushing the CM11 into my phone and installing it would that fix my problem?
Can i use flash tool to flash my old system back ?
Click to expand...
Click to collapse
You can simply try pushing the CM11 zip to Your phone when You are in twrp and Your phone is detected on the PC. You won't be able to see it as mounted storage. You will see the device when You run:
Code:
adb devices
Then Use the command to push:
Code:
adb push path/to/rom /sdcard
And then flash the ROM.
Mirhawk said:
You can simply try pushing the CM11 zip to Your phone when You are in twrp and Your phone is detected on the PC. You won't be able to see it as mounted storage. You will see the device when You run:
Code:
adb devices
Then Use the command to push:
Code:
adb push path/to/rom /sdcard
And then flash the ROM.
Click to expand...
Click to collapse
That's exactly what i did , but it still didn't work , i flashed the recovery.elf ( at first i flashed it .img ) and then installed the rom , now it works perfect , thanks a lot guys for your help , if some people are having trouble this video helped me a lot
youtube.com/watch?v=Hn4E3fKX7WM
Hi,
Good news if it works now.
So enjoy yourself with custom rom
IT IS POSSSSIIIIIBBBBLLLLLE!
I am rewriting this tutorial from RDS www.yuplaygod.com member's post
This is only meant for users who had rooted their device, in lollipop, have cwm or twrp recovery installed. IF not rooted find guides for it. (Hint: Google it)
I suggest to not use fastboot for flashing roms... It may brick you device (I meant hard brick)
So here is what we are going to do!
STEPS (VERY SIMPLE)
1) Download Back_to_cm11-signed by Abhiram.zip https://drive.google.com/file/d/0B4etFrzyEA01UklKR3N5T2JYeGc/view?usp=sharing
2)Download recovery-yu.img https://drive.google.com/file/d/0B4etFrzyEA01d2VGRXNuY2I1MGs/view?usp=sharing
3)Copy Back_to_cm11-signed by Abhiram.zip to SDCARD
4)Open recovery and flash it
5)Open fastboot mode.
6)Connect to your computer and flash recovery-yu.img
7)Open recovery by pressing "vol+"+"vol-"+"pwr"
8)Flash stock rom zip. Go to this guide to get it http://forum.xda-developers.com/yureka/orig-development/rom-t3042384
9) Rock with it!.
********FOR THOSE WHO ARE NOT GOOD WITH FASTBOOT**********
So yureka is something different. So you have to specify the device id for the fastboot to find it.
Install adb-setup.1****.exe https://drive.google.com/file/d/0B4etFrzyEA01SE9NTVNRWTl4Y0E/view?usp=sharing
Open CMD
Type fastboot -i 0x1ebf devices
If any device is detected you r good to go
Close CMD
Open the place where you have downloaded recovery-yu.img
By pressing shift, right click the folder (in which you have downloaded recovery-yu.img) click open command window here
and type fastboot -i 0x1ebf boot recovery-yu.img
That's it
Have you tried that and didn't face any hardbricks?
Yes
I risked my own device to prove that. Go ahead 10000% sure that this will work. Because my device did not brick at all
Please hit tanks if you got it working! It is working..
Abhiram Shibu said:
I risked my own device to prove that. Go ahead 10000% sure that this will work. Because my device did not brick at all
Please hit tanks if you got it working! It is working..
Click to expand...
Click to collapse
tank you
The OP suggest not to use fastboot mode as it may hard brick device & the steps tht follow are based on fastboot option... I'm confused, Is it safe to use fastboot mode thn?
ujilraj their is nothing to be confused. You can use fastboot mode. But if you flash system.img and data.img via fastboot, which has different partition styles, then you will end up with hard bricked phone... That's why!
Flashing recovery is very safe! GO for it!
I have tested it
For further clarification i'm asking this, pardon me...
First i boot into CM12 recovery & flash Back_to_cm11-signed by Abhiram.zip
Then,
Enter fastboot mode & install recovery-yu.img tht belongs to CM11.
Then,
I boot into CM11 recovery & flash any CM11 rom... Rite???
A bit confuse
Abhiram Shibu said:
I suggest to not use fastboot for flashing roms... It may brick you device (I meant hard brick)
That's it
Click to expand...
Click to collapse
I am a bit confuse here. Could you explain to me what is the different between:
Code:
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
AND
Code:
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash modem NON-HLOS.bin
ujilraj said:
For further clarification i'm asking this, pardon me...
First i boot into CM12 recovery & flash Back_to_cm11-signed by Abhiram.zip
Then,
Enter fastboot mode & install recovery-yu.img tht belongs to CM11.
Then,
I boot into CM11 recovery & flash any CM11 rom... Rite???
Click to expand...
Click to collapse
Ujilraj That is absolutely correct ! You got it man.:good:
tirta.agung said:
I am a bit confuse here. Could you explain to me what is the different between:
Code:
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
AND
Code:
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash modem NON-HLOS.bin
Click to expand...
Click to collapse
That is good question, I appreciate that.
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!
Abhiram Shibu said:
That is good question, I appreciate that.
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!
Click to expand...
Click to collapse
Rather than flashing your zip via recovery, can I not use fastboot to flash the following in the order mentioned:
modem, sbl1, aboot, rpm, tz, hyp, recovery. The files that would be used are a part of cm11 fastboot package. After flashing all of these, boot to recovery and then flash the cm11 zip. I'll be essentially doing the same like you did. But I'll be using fastboot to flash firmware specific stuff. I strongly believe that these would not cause the infamous brick.
Thanks,
Sanjay
Abhiram Shibu said:
That is good question, I appreciate that.
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!
Click to expand...
Click to collapse
2 questions :-
1. ) As you said that do not use the fastboot method to flash kitkat rom. My question is, Can i use fastboot method to flash the lollipop 64bit zip file (that is basically the same OTA update file), using same method which was used to flash kitkat (by extracting the zip file contents to a common folder containing flash-all.bat, if u remmeber?). Basically i want to know a method to re-flash lollipop 64 bit , if any1 knows?
2.) Once i suceed to get kitkat rom back , from the lollipop 64 bit. Can i use FASTBOOT method in FUTURE flashes to flash kitkat based custom roms or should i permanently DISCONTINUE flashing through fastboot, even after getting kitkat rom back by your method?
thanks in advance .... :good:
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
Also i want to know. is there something like 32bit and 64 bit recovery. I hv heard that flashing incoatiable recovery can also lead to hard brick.
which recovery to flash when.??
could be great if any1 has positive information and can guide....
coolboyforeva said:
2 questions :-
1. ) As you said that do not use the fastboot method to flash kitkat rom. My question is, Can i use fastboot method to flash the lollipop 64bit zip file (that is basically the same OTA update file), using same method which was used to flash kitkat (by extracting the zip file contents to a common folder containing flash-all.bat, if u remmeber?). Basically i want to know a method to re-flash lollipop 64 bit , if any1 knows?
2.) Once i suceed to get kitkat rom back , from the lollipop 64 bit. Can i use FASTBOOT method in FUTURE flashes to flash kitkat based custom roms or should i permanently DISCONTINUE flashing through fastboot, even after getting kitkat rom back by your method?
thanks in advance .... :good:
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
Also i want to know. is there something like 32bit and 64 bit recovery. I hv heard that flashing incoatiable recovery can also lead to hard brick.
which recovery to flash when.??
could be great if any1 has positive information and can guide....
Click to expand...
Click to collapse
There is nothing to be confused. there are 32 bit and 64 bit recoveries. Flashing wrong recovery will only softbrick your phone. I did it ones accidentally
32bit recovery https://drive.google.com/open?id=0B4etFrzyEA01d2VGRXNuY2I1MGs&authuser=0
64bit recovery https://drive.google.com/open?id=0B4etFrzyEA01NnZBWHcxWlVHTW8&authuser=0
If you want to flash lollipop then download lollipop flash-able zip file click here for zip file
There are some good working fastboot upgrade packages. So if you have one of them ( Tried it yourself to upgrade and worked earlier) Then use that package it will work!. Flashing with zip file with recovery reduces risk!:good:
Abhiram Shibu said:
There is nothing to be confused. there are 32 bit and 64 bit recoveries. Flashing wrong recovery will only softbrick your phone. I did it ones accidentally
32bit recovery https://drive.google.com/open?id=0B4etFrzyEA01d2VGRXNuY2I1MGs&authuser=0
64bit recovery https://drive.google.com/open?id=0B4etFrzyEA01NnZBWHcxWlVHTW8&authuser=0
If you want to flash lollipop then download lollipop flash-able zip file click here for zip file
There are some good working fastboot upgrade packages. So if you have one of them ( Tried it yourself to upgrade and worked earlier) Then use that package it will work!. Flashing with zip file with recovery reduces risk!:good:
Click to expand...
Click to collapse
ok . m not gonna use fastboot. But how will i flash signed lollipop zip file on custom recovery and unlocked bootloader. it wont boot. I would need an unsigned lollipop 64 bit zip file or rather a locked bootloader + stock 64 bit recovery . Any link for stock 64 bit recovery ? is above link for stock or custom recovery?
coolboyforeva said:
ok . m not gonna use fastboot. But how will i flash signed lollipop zip file on custom recovery and unlocked bootloader. it wont boot. I would need an unsigned lollipop 64 bit zip file or rather a locked bootloader + stock 64 bit recovery . Any link for stock 64 bit recovery ? is above link for stock or custom recovery?
Click to expand...
Click to collapse
Yes it will boot.
Link above is for custom CWM recovery.
Warning ******** Boring Story Ahead*********
So i purchased my yureka from Amazon. When i got it, I unlocked boot loader, installed cwm recovery right away. When the lollipop upgrade showed up I tried to download it via system upgrade. It downloaded but wont flash because of a custom recovery. So... I downloaded a signed zip file from xda attachment which i gave you. I cleared cache and tried installing the zip file.... It actually works.
Why it worked?
Stock rom looks for signed zips and it should be signed my their developer. But custom recoveries installs any zip file which is flashable regardless they are signed or unsigned. The only thing it looks for is the scripts and device compactability.
So try flashing the lollipop signed zip file. It will surely work...
So... What will the zip file do?
It will wipe system, modem, recovery etc exept data. Resize them and copy files in.
So ... What will you end up with.
Obviously,
A locked bootloader ( Which when unlocked wipes data)
A stock old cyanogen recovery.
Non rooted CM12.....
So this means that if you want to be a power user you have to start form beginning. So... consider taking a nandroid backup before you upgrade.....
STEPS TO BACKUP DATA ON CYANOGEN 11
So... Abhiram I cant find my backup on sdcard
answer to this question is very simple. You know that your sdcard and app memory are same. So they created a new folder 0 and mounted as your sdcard.
So... How do you get that out....
There are 2 methords
Common step boot into recovery and connect your mobile to your computer. Make sure that ADB drivers are installed
Methord 1
Type
"adb shell
cp -r /sdcard/clockworkmod/ /sdcard/0/android/
adb reboot"
So after the phone rebooted. Open file manage ( anyone ) Browse into android folder in your sdcard, you will find your backup there. If you cant find your whole backup , the chances are you r running out of memory.
Methord 2
type
"adb pull /sdcard/clockworkmod/ %UserProfile%/documents/backup_from_nandroid/ "
Your backup can be found in c:/users/<your user name here>/documents/backup_from_nandroid/
So that is it....
So when you unlock boot loader you can copy this backup into your phone by....
1) Copy backup to adb folder
2) Type adb push <Directory name> /sdcard/clockworkmod/
Then do a advanced restore. Select data and restore
done!
Abhiram Shibu said:
Yes it will boot.
Link above is for custom CWM recovery.
Warning ******** Boring Story Ahead*********
So i purchased my yureka from Amazon. When i got it, I unlocked boot loader, installed cwm recovery right away. When the lollipop upgrade showed up I tried to download it via system upgrade. It downloaded but wont flash because of a custom recovery. So... I downloaded a signed zip file from xda attachment which i gave you. I cleared cache and tried installing the zip file.... It actually works.
Why it worked?
Stock rom looks for signed zips and it should be signed my their developer. But custom recoveries installs any zip file which is flashable regardless they are signed or unsigned. The only thing it looks for is the scripts and device compactability.
So try flashing the lollipop signed zip file. It will surely work...
So... What will the zip file do?
It will wipe system, modem, recovery etc exept data. Resize them and copy files in.
So ... What will you end up with.
Obviously,
A locked bootloader ( Which when unlocked wipes data)
A stock old cyanogen recovery.
Non rooted CM12.....
So this means that if you want to be a power user you have to start form beginning. So... consider taking a nandroid backup before you upgrade.....
STEPS TO BACKUP DATA ON CYANOGEN 11
So... Abhiram I cant find my backup on sdcard
answer to this question is very simple. You know that your sdcard and app memory are same. So they created a new folder 0 and mounted as your sdcard.
So... How do you get that out....
There are 2 methords
Common step boot into recovery and connect your mobile to your computer. Make sure that ADB drivers are installed
Methord 1
Type
"adb shell
cp -r /sdcard/cyanogenmod/ /sdcard/0/android/
adb reboot"
So after the phone rebooted. Open file manage ( anyone ) Browse into android folder in your sdcard, you will find your backup there. If you cant find your whole backup , the chances are you r running out of memory.
Methord 2
type
"adb pull /sdcard/clockworkmod/ %UserProfile%/documents/backup_from_nandroid/ "
Your backup can be found in c:/users/<your user name here>/documents/backup_from_nandroid/
So that is it....
So when you unlock boot loader you can copy this backup into your phone by....
1) Copy backup to adb folder
2) Type adb push <Directory name> /sdcard/clockworkmod/
Then do a advanced restore. Select data and restore
done!
Click to expand...
Click to collapse
Ok.. I want to revert back to kitkat. i wont be using fastboot to flash rom(only to flash recovery image). Is there anything else which i should avoid and keep in mind in order to prevent hard brick?? please suggest
coolboyforeva said:
Ok.. I want to revert back to kitkat. i wont be using fastboot to flash rom(only to flash recovery image). Is there anything else which i should avoid and keep in mind in order to prevent hard brick?? please suggest
Click to expand...
Click to collapse
Tips to avoid hardbrick.
Don't flash ROM via fastboot
Don't Format partition using fast boot
You can flash boot and recovery via fastboot.
You can do anything in recovery.
Advice backup ROM before you install kernel, or any zip files. That will help you if you soft brick your phone.
Hit thanks if I help you in anyway till now.
On reading the OP's comments another doubt occurred, Do i need to unlock bootloader all the time when switching between KK & LP? (Will the internal SD memory gets wiped all the time... Do i need to backup every data on the internal SD memory onto PC before switching from KK to LP & vice-versa?)
Yes, but in case of upgrading and unlocking boot loader
Nice Question
When you downgrade from CM12 to CM11 your data will be safe. Unlocking boot loader will not do anything with your data:angel:
But When you are upgrading from CM11 to CM12 your data will be also safe, but the problem occurs when you try to unlock boot loader It will wipe all of your data.:crying:
When we unlock boot loader in kitkat CM11 by using command fastboot -i 0x1ebf oem unlock
It doesn't ask for any confirmations.
But in case of CM12 when you unlock boot loader by using the same command, before wiping data, it asks for confirmation. ie It tells to push vol+ to confirm or push vol - to stop.
If you see like this. Fastboot is going to erase your sdcard.
Its a good practice to backup your data when you r playing with your phones firmware, It will help you get back your memorable moments, favorite music etc.
If you have an otg cable. Keep a pendrive for backup
So concluding in unlocking CM11 no data loss unlocking in CM12 there is data loss.
Good luck:good:
One more doubt, suppose i'm on KK & want to upgrade to some custom CM12.x rom, do i need to go through the process of installing stock cm12 all the time, or do u suggest any other simple way to directly do the same?
I saw this in facebook group "xperia t3 - india".. it seems we just need the camera to work
and 4G, and sdcard1...
vmlc said:
I saw this in facebook group "xperia t3 - india".. it seems we just need the camera to work
Click to expand...
Click to collapse
Hi i'm the guy how have cyanogen on my T3 , I just wanted to warn you for the rom, select the FXP-cm12-20150412...
And not the FXP-cm12.1 ...
otherwise your phone will bootloop, and when you make the first start of the phone , don't worry if after the bootanimation there's a black screen just wait 2-3 minutes for the update
So enjoy Cyanogen Xperia Users
fastbooking said:
Hi i'm the guy how have cyanogen on my T3 , I just wanted to warn you for the rom, select the FXP-cm12-20150412...
And not the FXP-cm12.1 ...
otherwise your phone will bootloop, and when you make the first start of the phone , don't worry if after the bootanimation there's a black screen just wait 2-3 minutes for the update
So enjoy Cyanogen Xperia Users
Click to expand...
Click to collapse
so, you confirm no 4g and camera working?
vmlc said:
so, you confirm no 4g and camera working?
Click to expand...
Click to collapse
yes no camera and 3G/4G
fastbooking said:
yes no camera and 3G/4G
Click to expand...
Click to collapse
also, you should do a detailed tutorial how to try the seagull build, i tried it the other day, but I couldnt do it....
vmlc said:
also, you should do a detailed tutorial how to try the seagull build, i tried it the other day, but I couldnt do it....
Click to expand...
Click to collapse
I will try tomorow there's a french tutorial about that here's the link for the one's who speak french
phonandroid.com/forum/post1800321.html (www . before its just because i can't now)
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
ok, the part I dont get is: "once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot"
how do you do this?
dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
I don't install cyanogen like that,
First I update my phone with EMMA with the Open devices TA
-After I open the zip of the rom and i extract it somewhere you can find it
-take the zip AND THE GAPPS and connect your phone on usb for sending the zip on THE ROOT of your sdcard
-Enter in fastboot, and open flashtool (not emma the other)
-Flash the kernel called : boot.img
-Once Flashed reboot your phone in recovery (up button when the led is purple or violet)
-The led became gold color
- You now are (normaly) in cyanogen recovery
-Wipe data/Factory reset
-Wipe Cache for avoid bugs
-Now the fun part
-Apply update select the ROM and after the GAPPS
-Reboot and enjoy !
If the screen is black for a while after boot it's normal it's the system update
I also recommand you to take the
FXP-cm-12-20150412-UNOFFICIAL-seagull.zip
file because the other in cm12.1 are bootlooping
Now you can enjoy properly without camera and 3G/4G cyanogen
Sorry for my english I'm just a 14 french kid
btw, is this for 5102 or 5103? also, what do I have to be installed on my computer so I can flash boot for fastboot?
vmlc said:
btw, is this for 5102 or 5103? also, what do I have to be installed on my computer so I can flash boot for fastboot?
Click to expand...
Click to collapse
This is for D5103 the D5102 isn't the seagull this name is ONLY for the D5103
For the manipulation you will need emma (called flashtool by sony,for updating the bootloader)
And flashtool by Androxyde (this only is for flash kernel)
:highfive: now you're ready
Enjoy cyanogen on our t3 :laugh:
fastbooking said:
This is for D5103 the D5102 isn't the seagull this name is ONLY for the D5103
For the manipulation you will need emma (called flashtool by sony,for updating the bootloader)
And flashtool by Androxyde (this only is for flash kernel)
:highfive: now you're ready
Enjoy cyanogen on our t3 :laugh:
Click to expand...
Click to collapse
Im having problems flashing the kernel. I cant find my device in fastboot, and when I use flashtool to go ADB mode it says I dont have usb debugging on because I installed zip from recovery, the seagull file...
vmlc said:
Im having problems flashing the kernel. I cant find my device in fastboot, and when I use flashtool to go ADB mode it says I dont have usb debugging on because I installed zip from recovery, the seagull file...
Click to expand...
Click to collapse
Ok let's start off zero
you installed the zip via the philz recovery and after you wanted to flash the kernel ?
dan15 said:
Cyanogen ROM are distributed in zip format, so you have to :
- push the zip file to your sdcard
- you need a kernel with recovery (for the time being, the Philz one)
- you enter in recovery mode
- you select "install zip" and the zip file.
once it's finished, install the right kernel
for that, on your PC, extract the boot.img file from the ROM zip file and flash it with flashtool or fastboot
reboot and enjoy
Click to expand...
Click to collapse
thats what it says...
vmlc said:
thats what it says...
Click to expand...
Click to collapse
follow my tutorial it's the steps i followed and it works for me :good:
fastbooking said:
follow my tutorial it's the steps i followed and it works for me :good:
Click to expand...
Click to collapse
I got bricked meanwhile. Battery problem I think, not the first time...
ok, i think there is a missunderstanding.
in order to flash the kernel, you need to be in fastboot mode (with the blue light). so, once you have installed the zip file, shut down the phone (in recovery mode, select "power options/power off" , disconnect the phone and reconnect it in fastboot (maintain the vol up before and during the USB connection ).
you can now use "flashtool" (the Androxyde's one. to avoid confusion, the Sony's one is called EMMA or if it is more easy for you fastboot.exe
to use fastboot, you open a command line (Windows+R + type "cmd") , you go to the folder where the boot.img is and you enter the comand "fastboot flash boot boot.img". after ~2s the kernel is flashed, you can disconnect the phone and restart.
the first time, the boot time is about 5 min with a black screen after the animated screen, so wait a moment.
it's for that it's very important to have a well charged phone (min 40%) because the first start use a lot of battery, and you can't see anything.
I want to restore, I just installed the zip. Why cant I enter recovery?
edit: ok, I entered cyanogen recovery. will try to boot now. but I dont have backup/restore option....
edit2: ok, It booted but I still want to know how to back to previous version...
vmlc said:
I want to restore, I just installed the zip. Why cant I enter recovery?
edit: ok, I entered cyanogen recovery. will try to boot now. but I dont have backup/restore option....
edit2: ok, It booted but I still want to know how to back to previous version...
Click to expand...
Click to collapse
go on emma and select the android 4.4.4 update KK in the services line under open devices TA
It will restore the like the 1 st day but you will loose your data, but after you can install the philz recovery and restore the backup
Hello guys,
I have rooted 2 days ago my phone with TWRP and Magisk; everything worked fine until I tried to change somethin in /system/ folder. It always said I dont have write rights. So I decided to go back to stock rom. I have downloaded the stock rom for my phone (gauguin, Global 12.0.8.0 , Android 10.) Now I have the following problem. My device is soft bricked.
So i decided to google and try to flash another Rom for my phone. I found one here.
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
How Can I flash that file? its .tgz
I have stock rom installed and I cant flash TWRP
Thanks in advance
Francesco
here is what comes when I try to flash. It fails aftter Flashing super :
error hosted at ImgBB
Image error hosted in ImgBB
ibb.co
Francescohub said:
here is what comes when I try to flash. It fails aftter Flashing super :
Click to expand...
Click to collapse
Unpack TGZ archive, then untar TAR file again. You will see folder with images and script files. Run "flash_all_except_storage.bat".
Francescohub said:
here is what comes when I try to flash. It fails aftter Flashing super :
error hosted at ImgBB
Image error hosted in ImgBB
ibb.co
Click to expand...
Click to collapse
Get it too work ?
_mysiak_ said:
Unpack TGZ archive, then untar TAR file again. You will see folder with images and script files. Run "flash_all_except_storage.bat".
Click to expand...
Click to collapse
For the love of god, I just spent 3 hours to install fastboot ROM and did not succeed. No idea what went wrong, but at the end I finally restored my device..
1. download recovery ROM and transfer it to internal SD
2. download fastboot ROM, unpack it
3. modify flash_all_except_storage.bat and delete lines with CRCLIST and SPARCECRCLIST
4. run the script
5. phone will keep rebooting on MI logo
6. boot to TWRP "fastboot boot twrp.img"
7. install recovery ROM from TWRP
8. (install Magisk), reboot phone to system
For some reason fastboot flashing doesn't install /odm partition correctly. I have the latest drivers, android tools, tried 2 PCs, 2 different USB cables, different USB ports, using Mi Flash, nothing helped. The only solution was to flash recovery rom from TWRP. Fortunately no data has been lost.
Francescohub said:
Hello guys,
I have rooted 2 days ago my phone with TWRP and Magisk; everything worked fine until I tried to change somethin in /system/ folder. It always said I dont have write rights. So I decided to go back to stock rom. I have downloaded the stock rom for my phone (gauguin, Global 12.0.8.0 , Android 10.) Now I have the following problem. My device is soft bricked.
So i decided to google and try to flash another Rom for my phone. I found one here.
https://xiaomirom.com/en/rom/mi-10t-lite-gauguin-global-fastboot-recovery-rom/
How Can I flash that file? its .tgz
I have stock rom installed and I cant flash TWRP
Thanks in advance
Francesco
Click to expand...
Click to collapse
Can you boot into fastboot? You said it's soft bricked so I imagine you can. Reply and I'll get back to you, I soft bricked mine and fixed it fine.
Hey guys, I was finally able to flash the Rom.
I used to flash a Rom with Xiaomi Flash, accidentaly it was a wrong rom, which I saw later on.
So I installed TWRP recovery with fastboot commands and downloaded the right rom. I used to download the EEA Rom instead of Global Rom. So I transfered the EU Rom to micro SD Card and flashed it with TWRP.
Everything is working now, except the access to /system folder, after I rooted with magisk 20.4. Even with the newest Version it does not work.
So I tried in the terminal the following command while I was in /system folder: mount -o rw,remount/ But this does also not work. How can I get acess to it?
Sorry for my english again
Francescohub said:
Hey guys, I was finally able to flash the Rom.
I used to flash a Rom with Xiaomi Flash, accidentaly it was a wrong rom, which I saw later on.
So I installed TWRP recovery with fastboot commands and downloaded the right rom. I used to download the EEA Rom instead of Global Rom. So I transfered the EU Rom to micro SD Card and flashed it with TWRP.
Everything is working now, except the access to /system folder, after I rooted with magisk 20.4. Even with the newest Version it does not work.
So I tried in the terminal the following command while I was in /system folder: mount -o rw,remount/ But this does also not work. How can I get acess to it?
Sorry for my english again
Click to expand...
Click to collapse
Think you storage is corrupted what I did was download the ROM for my phone open the tar ROM to you see a file says images flash all and other stuff play rom folder in mi flash tool folders and open CMD use flash all in ROM folder
Make sure your phone is in fastboot before you use the flash all file it will return your phone to stock ROM
Hey guys can someone please upload the boot.img from the FW V13.0.5.0.SKOEUXM?
I did a big mistake and thought that android 12 can boot in twrp (recovery). Flashed a wrong boot.img and cant get my phone working now. Only Fastboot is working - the normal Recovery didnt boot so i cant even install the Update through the orignal system recovery.
Cause theres only a Recovery zip of it online i cant use the MiFlash Tool, since a downgrade to Android 11 isnt possible
thanks a lot!
You can download the OTA zip file from Xiaomi firmware updater or by using the app MiuiDownloader from Playstore
Unzip, you will find payload.bin inside - use the PC tool (there is a thread on XDA) Payload_Dumper to dump boot.img and other images
Anyway, here is the link to the boot-stock-lisa_EEA_V13.0.5.0.SKOEUXM_12.0.img
I had extracted and renamed (name does not matter):
File on MEGA
mega.nz
oh god! thank you very much!
will test it in few minutes
edit: It worked instantly! you made my day
Can someone please upload the boot.img from V13.0.2.0(SKOMIXM) to root?