Related
Can I root z1 on kitkat??anyone can help me?
Yes,
First, ask QUESTIONS in the Question and answer section.
Now, read the several guides in the general and/or development section on how to root.
In brief
Either, unlock your bootloader and flash an insecure kernel
or
flash stock 4.2, root, install recovery and flash a prerooted 4.4 rom.
Alll instructions are in their relevant threads so I will not reproduce them here.
Eigth time and counting I have written this today
Anyone can explain why there is not an straight forward method to root Z1 directly on kitKat and we need to downgrade to do it ?
SrMoure said:
Anyone can explain why there is not an straight forward method to root Z1 directly on kitKat and we need to downgrade to do it ?
Click to expand...
Click to collapse
Because sony has patched the known exploits and made it hard for the devs to find any expoit.
avveMeetU said:
Can I root z1 on kitkat??anyone can help me?
Click to expand...
Click to collapse
Best way to do is it to downgrade to 534 using flashtool, grab the FTF file needed from the mega collection thread.
Use vroot to root the device, install a custom recovery, flash the rom that you want to install (Monx, ihacker, romaur) then don't reboot, but re-enter flashmode and flash everything (without wipe) from an FTF of the same base, do not flash TA and System.
Reboot and youre done.
I wrote a more in depth tutorial which can be found in this thread, second post.
http://forum.xda-developers.com/showthread.php?t=2709585
dladz said:
Best way to do is it to downgrade to 534 using flashtool, grab the FTF file needed from the mega collection thread.
Use vroot to root the device, install a custom recovery, flash the rom that you want to install (Monx, ihacker, romaur) then don't reboot, but re-enter flashmode and flash everything (without wipe) from an FTF of the same base, do not flash TA and System.
Reboot and youre done.
I wrote a more in depth tutorial which can be found in this thread, second post.
http://forum.xda-developers.com/showthread.php?t=2709585
Click to expand...
Click to collapse
No that's not the best way
1) Vroot sends your IMEI number to china for no known reason. They have been asked to change this but gave no response to XDA about it.
2) The point of downgrading to a .534 FTF is that you can install recovery without rooting first. So install dualrecovery, then flash SuperSU.zip from chainfire, then flash a 4.4 rom of your choice.
avveMeetU said:
Can I root z1 on kitkat??anyone can help me?
Click to expand...
Click to collapse
It's real easy to relock the bootloader using Flashtool, so don't sweat unlocking it to root.
KarimSalloum said:
It's real easy to relock the bootloader using Flashtool, so don't sweat unlocking it to root.
Click to expand...
Click to collapse
But how do you backup your TA that way.
You need to root first then backup TA. Relocking with flashtool does not restore your TA.
Once you have your backup then that is always possible, but not for a first time root.
gregbradley said:
No that's not the best way
1) Vroot sends your IMEI number to china for no known reason. They have been asked to change this but gave no response to XDA about it.
2) The point of downgrading to a .534 FTF is that you can install recovery without rooting first. So install dualrecovery, then flash SuperSU.zip from chainfire, then flash a 4.4 rom of your choice.
Click to expand...
Click to collapse
I didn't know you could do it that way, the way that i've mentioned is what was written on all the tutorials that i've seen so i'm literally going from what other people have said, including monx.
The IMEI thing is a bit creepy but I wasn't aware of that either.
another one bricked...sigh how to fix?
Hey all,
Successfully unlocked my c9603 with latest kitkat and installed cwm 6 with these instructions
How to Install CWM 6 Recovery on Xperia Z1:
Download Doomlord’s Advanced Stock Kernel with CWM Recovery
Copy the downloaded.zip file to your phone’s sd card.
Extract the downloaded .zip folder on your PC, you will get a Boot.img file.
Place the extracted Boot.img file in the Minimal ADB & Fastboot folder that you created using our ADB & Fastboot Quick Setup Guide.
If you are using Android ADB & Fastboot full package, you can place the downloaded Recovery.img file in the Fastboot folder or in the Platform-tools folder.
Open the folder where you placed the Boot.img file. E.g Minimal ADB & Fastbootor Fastboot or Platform Tools.
Press and hold the shift key and right click on an empty area within the folder, and click on “Open Command Window Here”.
Turn off your Xperia Z1 completely.
Now press the Volume Up Key and while keeping it pressed plug in the USB cable.
You should see a blue light in the notification light of your phone, that means your device is now connected in Fastboot mode.
Now type the following command: Fastboot Flash boot Boot.img
Hit Enter and it will quickly flash CWM 6.0.4.6 recovery in your Xperia Z1
Once recovery is flashed, now issue this command “Fastboot Reboot”
Your device will reboot now, as soon as you see the Sony logo, and the pink LED, press Volume Up key to enter recovery.
Congrats! You should now see the custom recovery.
Once in CWM recovery, flash the zip file you copied to your phone in step 2. To do so, select “install zip > choose zip from sd card > doomlord advanced stock kernel.zip > yes” and flash it.
Once flashed the zip file, reboot your device.
That’s all.
ok so I did all of the with success now when I turn my phone on I get what I think is a bootloop mode...it gives me the sony logo and the pink led to boot in cwm then re loops over and over.
I can get into cwm but thats it.
So how do I go about fixing my bricked phone now? Kinda need it lol
appreciated guys
WOW, I misread that...
If you flash doomkernel you already have recovery.
Please link to where you found those instructions, they seem way out of date.
and have you unlocked your bootloader?
96329992 144
gregbradley said:
WOW, I misread that...
If you flash doomkernel you already have recovery.
Please link to where you found those instructions, they seem way out of date.
and have you unlocked your bootloader?
Click to expand...
Click to collapse
http://techbeasts.com/2014/02/19/in...ng-latest-14-2-a-1-136-firmware-how-to-guide/
thats the link I used.
and yes I unlocked the bootloader via adb and fastboot using this guide
http://techbeasts.com/2013/12/18/how-to-unlock-bootloader-of-sony-xperia-devices-guide/
and I think I just maybe spotted my mistake, I probably should hvae used this link instead but due to sleep deprivation I didnt
http://techbeasts.com/2014/03/20/install-cwm-6-recovery-xperia-z1-android-4-4-2-kitkat-681/
anyway I went ahead and download that boot.img file, renamed it copied it across and tried to flash and I get this error
error: cannot load 'boot.img': No error
antiskeptic said:
http://techbeasts.com/2014/02/19/in...ng-latest-14-2-a-1-136-firmware-how-to-guide/
thats the link I used.
and yes I unlocked the bootloader via adb and fastboot using this guide
http://techbeasts.com/2013/12/18/how-to-unlock-bootloader-of-sony-xperia-devices-guide/
and I think I just maybe spotted my mistake, I probably should hvae used this link instead but due to sleep deprivation I didnt
http://techbeasts.com/2014/03/20/install-cwm-6-recovery-xperia-z1-android-4-4-2-kitkat-681/
anyway I went ahead and download that boot.img file, renamed it copied it across and tried to flash and I get this error
error: cannot load 'boot.img': No error
Click to expand...
Click to collapse
Those non xda guides are crap...
If you have unlocked your bootloader (Did you make a TA backup first?) then just flash doomkernel
Doomkernel has recovery in it.
Once you have done that you are rooted and have recovery
gregbradley said:
Those non xda guides are crap...
If you have unlocked your bootloader (Did you make a TA backup first?) then just flash doomkernel
Doomkernel has recovery in it.
Once you have done that you are rooted and have recovery
Click to expand...
Click to collapse
No, I didnt back up the ta as I didnt have root in the first place.
I have doom kernal installed and can access cwm.
It is stuck in bootloop mode...how do I just get my phone to boot normally for now instead of bootlooping?
---------- Post added at 06:51 PM ---------- Previous post was at 06:39 PM ----------
i just tried all of this from xda university, still no luck at all, still boot looping
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
antiskeptic said:
No, I didnt back up the ta as I didnt have root in the first place.
I have doom kernal installed and can access cwm.
It is stuck in bootloop mode...how do I just get my phone to boot normally for now instead of bootlooping?
---------- Post added at 06:51 PM ---------- Previous post was at 06:39 PM ----------
i just tried all of this from xda university, still no luck at all, still boot looping
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Click to expand...
Click to collapse
Ok, flash SuperSU.zip from chainfires website (Google it)
Then flash a new rom of your choice.
gregbradley said:
Ok, flash SuperSU.zip from chainfires website (Google it)
Then flash a new rom of your choice.
Click to expand...
Click to collapse
Cool, ill get onto that. Ive noticed a cpl of roms floating around xda. Any suggestions on a good one or run with the
http://forum.xda-developers.com/showthread.php?t=2687275&page=8
option?
lol....might as well pick a good rom since i have stuffed my stock one.
I still will achieve my root! haha
thanks for the help so far, its always appreciated!
You do not need root to flash that.
Its a stock FTF, just flash it in flash tool
gregbradley said:
You do not need root to flash that.
Its a stock FTF, just flash it in flash tool
Click to expand...
Click to collapse
sorry I wasnt saying do i need root for this? i know i currently dont have root and can flash ftf anyway.
what i was saying was, once i have my phone back up, I will achieve root status on it...
so if I am correct flash the phone with supersu from sdcard via cwm6 then flash
[FTF] Xperia Z1 C6903 14.3.A.0.681 Commercial&Journalist
which I am downloading from http://forum.xda-developers.com/showthread.php?t=2687275
My phone should boot up now with root access, but I am only trying to fix it currently.
Cant see why I wouldnt have a working phone with root following these steps?
thanks , ill keep posting updates, might even help someone else in the process
But why are you insistent on backing up a system that is in bootloop? Why would you ever want to restore a bootlooping system?
I would just do a fresh system install and forget about backing up a non working system
Just flash the FTF of your choice, then the appropriate DooMKerneL version.
Then you are rooted and have CMW installed. 2 easy steps, I really don't understand your need to backup first, especially when your phone is bootlooping.
---------- Post added at 11:13 AM ---------- Previous post was at 11:07 AM ----------
antiskeptic said:
then flash
[FTF] Xperia Z1 C6903 14.3.A.0.681 Commercial&Journalist
which I am downloading from http://forum.xda-developers.com/showthread.php?t=2687275
My phone should boot up now with root access,
Click to expand...
Click to collapse
No, once you flash a FTF you lose root. You will need to reflash the appropriate DooMKerneL again
but I am only trying to fix it currently.
Cant see why I wouldnt have a working phone with root following these steps?
Click to expand...
Click to collapse
Because once you flash a FTF you lose root
thanks , ill keep posting updates, might even help someone else in the process
Click to expand...
Click to collapse
gregbradley said:
But why are you insistent on backing up a system that is in bootloop? Why would you ever want to restore a bootlooping system?
I would just do a fresh system install and forget about backing up a non working system
Just flash the FTF of your choice, then the appropriate DooMKerneL version.
Then you are rooted and have CMW installed. 2 easy steps, I really don't understand your need to backup first, especially when your phone is bootlooping.
---------- Post added at 11:13 AM ---------- Previous post was at 11:07 AM ----------
No, once you flash a FTF you lose root. You will need to reflash the appropriate DooMKerneL again Because once you flash a FTF you lose root
Click to expand...
Click to collapse
im not trying to backup the bootloop, i just want to fix my phone. I did not realise you were saying fresh install then start from scratch with the root process.
So I will flash the NEW ftf to my phone. Once phone is working I will flash doomlord kernel and supersu. thanks for the help. do you happen to know a link for the correct instructions for this, so I get it right this time.
So I got my Z1 yesterday, was on 4.4.2 stock unrooted. I unlocked the bootloader using Sony's official website and fastboot, then I went on destroying the phone by flashing Philz touch recovery.img through fastboot.
And since then the phone has been bricked, I can only enter Fastboot through the blue led, while Flash mode doesn't show up any LED light and my PC sees the phone when on flashmode as n "S1 device with a parameter error".
I've tried all drivers, none worked, and the flashtool keeps suggesting I should update my drivers when connecting the phone on flash mode:
02/042/2014 22:42:11 - INFO - Device connected in flash mode
02/042/2014 22:42:30 - ERROR - Drivers need to be installed for connected device.
02/042/2014 22:42:30 - ERROR - You can find them in the drivers folder of Flashtool.
Click to expand...
Click to collapse
Is there any way I can recover from this through fastboot instead of the flashtool? I can still flash system.img and recovery.img through fastboot. I'd really appreciate any help right now.
Abu-7abash said:
So I got my Z1 yesterday, was on 4.4.2 stock unrooted. I unlocked the bootloader using Sony's official website and fastboot, then I went on destroying the phone by flashing Philz touch recovery.img through fastboot.
And since then the phone has been bricked, I can only enter Fastboot through the blue led, while Flash mode doesn't show up any LED light and my PC sees the phone when on flashmode as n "S1 device with a parameter error".
I've tried all drivers, none worked, and the flashtool keeps suggesting I should update my drivers when connecting the phone on flash mode:
Is there any way I can recover from this through fastboot instead of the flashtool? I can still flash system.img and recovery.img through fastboot. I'd really appreciate any help right now.
Click to expand...
Click to collapse
Xperia phones do not have a recovery partition to flash recovery to via fastboot.
If you can enter fastboot, then flash a stock kernel.elf with flashtool (In fastboot mode).
Then you can use flashtool to relock your boot (I imagine you have not even taken a TA backup and you are new to xperia devices, your post suggests so)
then you should be able to use pccompanion to repair, or flashtool to flash a FTF
However, by flashing a recovery image you may have bricked the phone. try what I have said, if it does not work get back in touch. (Do you have access to jtag and setool?)
gregbradley said:
Xperia phones do not have a recovery partition to flash recovery to via fastboot.
If you can enter fastboot, then flash a stock kernel.elf with flashtool (In fastboot mode).
Then you can use flashtool to relock your boot (I imagine you have not even taken a TA backup and you are new to xperia devices, your post suggests so)
then you should be able to use pccompanion to repair, or flashtool to flash a FTF
However, by flashing a recovery image you may have bricked the phone. try what I have said, if it does not work get back in touch. (Do you have access to jtag and setool?)
Click to expand...
Click to collapse
Can you link me to the files you suggested I try? There seems to be a truckload of them laying around the forum.
Also, yes, I am new to xperia phones. Didnt think they were this complicated to flash but I shouldnt have played with fastboot anyway. And no, sadly I dont have a jtag. Never needed one before.
Thanks for the help btw, I greatly appreciate this.
i dont think you have 100% installed the drivers, on windows 7 upwards you need to disable driver signature to allow any unsigned drivers to be installed
Look in the mega collection thread in the general section for a 442 ftf file. The kernel.elf will be in it
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Look in the mega collection thread in the general section for a 442 ftf file. The kernel.elf will be in it
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, but how do I extract it from the TFT file?
gregbradley said:
Look in the mega collection thread in the general section for a 442 ftf file. The kernel.elf will be in it
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
C6903_14.3.A.0.757_Global 1277-2880.ftf
Is this 4.4.2?
Ok here is an update; after messing with fastboot for so long and a couple of kernel flashes, I managed to boot the phone But now its stuck on the Sony logo.
A sign of hope though lies with the fact that I managed to enter recovery mode and found CWM hanging there. So now Im probably going to try ADB push a rom file to the SD and try to flash it through recovery instead.
@gregbradley
Sounds good. The reason forth hang at the sony logo will be that you have wiped the system partition. Flashing a rom based on the kernel you have will enable the phone to boot
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Sounds good. The reason forth hang at the sony logo will be that you have wiped the system partition. Flashing a rom based on the kernel you have will enable the phone to boot
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Would flashing a custom rom zip from the CWM recovery, fix the bootloop? Or could it also be a baseband/firmware issue too?
Im not really familiar with Sony's bootloader unlock process, does it allow kernel flash from recovery or only through fastboot ala Htc style?
Abu-7abash said:
Would flashing a custom rom zip from the CWM recovery, fix the bootloop? Or could it also be a baseband/firmware issue too?
Im not really familiar with Sony's bootloader unlock process, does it allow kernel flash from recovery or only through fastboot ala Htc style?
Click to expand...
Click to collapse
first flash original stock rom, than root your phone and install dualrecovery... and if u relock your bootloader unlock it again... don't try custom rom before this steps
Abu-7abash said:
Would flashing a custom rom zip from the CWM recovery, fix the bootloop? Or could it also be a baseband/firmware issue too?
Click to expand...
Click to collapse
Yes, as long as the .zip contains a kernel, or id based on the same kernel you have installed now
Im not really familiar with Sony's bootloader unlock process, does it allow kernel flash from recovery or only through fastboot ala Htc style?
Click to expand...
Click to collapse
Yes, if you have an unlocked bootloader
gregbradley said:
Yes, as long as the .zip contains a kernel, or id based on the same kernel you have installed nowYes, if you have an unlocked bootloader
Click to expand...
Click to collapse
Alright thanks, gonna give it a go once im home. And yes, I already unlocked the bootloader through Sony's website and fastboot before this happened.
Vuja1 said:
first flash original stock rom, than root your phone and install dualrecovery... and if u relock your bootloader unlock it again... don't try custom rom before this steps
Click to expand...
Click to collapse
It already has the dual recovery on it but for some reason its stuck in a bootloop.
Abu-7abash said:
It already has the dual recovery on it but for some reason its stuck in a bootloop.
Click to expand...
Click to collapse
do u have any rom on it or u just have bootloop? i u can't access to rom, u need with flashtool to flash stock rom, when u do that u loose your root and lose your dualrecovery... u need to root it again and install dualrecovery
second is
if u can access to rom instal ndr utility and reboot in clockwork mod recovery...
third option si to install via fastboot advanced doomloader kernel which has clockwork mod and has root... after that to flash custom rom but stock version of custom rom
Any of you guys know of a Stock rooted 4.4.4 rom that comes with the stock kernel in a flashable zip? I have looked everywhere for one but I cant find any.
@gregbradley @Vuja1
Abu-7abash said:
Any of you guys know of a Stock rooted 4.4.4 rom that comes with the stock kernel in a flashable zip? I have looked everywhere for one but I cant find any.
@gregbradley @Vuja1
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2761614
try this one
Vuja1 said:
http://forum.xda-developers.com/showthread.php?t=2761614
try this one
Click to expand...
Click to collapse
Already did, not really what Im looking for. I want the stock rom but only rooted and in a flashable zip, can't believe there aint any around.
Abu-7abash said:
Already did, not really what Im looking for. I want the stock rom but only rooted and in a flashable zip, can't believe there aint any around.
Click to expand...
Click to collapse
I can think of at least 3 in the development section off the top of my head...
gregbradley said:
I can think of at least 3 in the development section off the top of my head...
Click to expand...
Click to collapse
You can? Link me Greg..link me
Xperia sp First root, flash and... crash!
Hi all,
at last I got my first root.... Warranty was ended on my Xperia SP so I decided to give a chance to Lollipop.
Started with root (veeery smooth, towelroot and superSU), then CWM to have a good parachute, and after all, CM12 (plus googleApps and a couple more fixes found in this site).
Let's say... almost eveerything ok when I realized that a CM 12.1 was issued and wanted to give a chance to this too.
And now the real troubles started, mainly because of CWM.
The phone didn't boot anymore in recovery mode, so I even wasn't able to recover my backup, trying to reinstall CWM, the batch stated that version was unknown. So, it deleted the existing files.
I was able to reinstall them modifying a line checking version (added || IS_CM12)
This was the only way to take back my deart recovery menu.
But seems it waqsn't a good idea.... bricked. Jumping up&down the net to pick back the previous release of android via Flashtool, at last seems I found it.
Of course, as soon as restored, I'll try again, nut I think that there's a basilar problem: CMW is not done to work with CM12, is it? And if so, which other solutions will I have, should I need again a recover or a new version?
Thank you all for reading till here
Cheers
Raff
Use TWRP from now on no matter what ROM you use.
Install Rashr from here: https://mega.nz/#!lxVHjBZR!24FtZk7h8vp07TML489hujJsTYOzUzGWXLoDwWlEHMw
Then flash recovery from here: http://forum.xda-developers.com/xpe...-twrp-f2fs-support-xperia-sp-huashan-t3150230
I prefer philz touch
So both of you prefer other than CWM? Just askling since almost all update tutorials moention CWM as the first option...
Thank you!
Actually yeah!
and CWM is outdated, it can be used with JB/KK I guess, but almost all Lollipop devs recommend using TWRP/Philz.
Bootloader unlocked?
How could I check if bootloader is already unlocked since it's one of the prereqs for TWRP?
I verified that unlock is allowed, but before going ahead asking Sony the code, maybe it's useless? It's already rooted...
Thanks guys!
Raf3000 said:
How could I check if bootloader is already unlocked since it's one of the prereqs for TWRP?
I verified that unlock is allowed, but before going ahead asking Sony the code, maybe it's useless? It's already rooted...
Thanks guys!
Click to expand...
Click to collapse
Why would it be useless?
Go ahead and ask for the code,
and it should say something like "Bootloader unlocked: Yes" or "Bootloader Unlock: Done" on the service menu after you unlock it.
and don't forget to backup TA Partition before Unlocking.
Zenith said:
Why would it be useless?
Click to expand...
Click to collapse
I'm sorry, I didn't explain, I mean IF the phone is already unlocked it's useless asking the code.
From service menu -> configuration -> rooting status I have Bootolader Unlock allowed: yes
and don't forget to backup TA Partition before Unlocking.
Click to expand...
Click to collapse
Ok... How could I backup it if I still don't have TWRP installed?
Sorry if silly questions...
Thanks
"Bootloader Unlock allowed: yes" means that your bootloader is still locked, and you can unlock it if you want.
..and about TA Backup, read this thread: http://forum.xda-developers.com/showthread.php?t=2292598
and it's okay, everyone is a noob at the beginning
Hit thanks if I helped!
I did it!
Great! Unlocked and TA backupped. Now, TWRP.
Now, I know, I'm going to be boring... to be honest I'd like the graphics of Sony, but I'd like to upgrade to 5 too, so, I could proceed with CM12.1, and I'll have 5.1.1 but not "Sony style", or I could try smthg like customized ROM (don't remember the name, should retrieve my browsing history) based on CM12.1 but keeping Xperia Z series style...
What's your advice?
Thanks a lot
uhm... no... no TWRP...
rashr says that flash went ok, but when I ask to restart in recovery, it rtats as usual. And I can't see TWRP logo in the home page of rashr...
If you want Xperia styled appearance and a stable ROM,
Try any CM12.1 based ROM like AICP and use Xperia Z4 Theme
or 'StryFlex' if you want Sony's Official Xperia Lollipop UI, but it's not 100% stable yet, so I'd suggest you to use AICP.
---------- Post added at 11:47 PM ---------- Previous post was at 11:45 PM ----------
Raf3000 said:
uhm... no... no TWRP...
rashr says that flash went ok, but when I ask to restart in recovery, it rtats as usual. And I can't see TWRP logo in the home page of rashr...
Click to expand...
Click to collapse
did you install Rashr from playstore? or from the link I posted?
Zenith said:
If you want Xperia styled appearance and a stable ROM,
Try any CM12.1 based ROM like AICP and use Xperia Z4 Theme
or 'StryFlex' if you want Sony's Official Xperia Lollipop UI, but it's not 100% stable yet, so I'd suggest you to use AICP.
Click to expand...
Click to collapse
I agree, I prefer more stable so I think I'll go with the first option
did you install Rashr from playstore? or from the link I posted?
Click to expand...
Click to collapse
Actually, no, I used playstore. Removed and installed the link's one. Flash took some seconds more, it seemed a real flash, but at reboot notihing changed, non recovery boot.
But... I can see a fraction of second before the logo Sony a kind of menu, I can imagine it's TWRP, but I don't understand why it doesn't stop there...
Raf3000 said:
I agree, I prefer more stable so I think I'll go with the first option
Actually, no, I used playstore. Removed and installed the link's one. Flash took some seconds more, it seemed a real flash, but at reboot notihing changed, non recovery boot.
But... I can see a fraction of second before the logo Sony a kind of menu, I can imagine it's TWRP, but I don't understand why it doesn't stop there...
Click to expand...
Click to collapse
When you see the sony logo, or watch the LED light up, press volume down button to Enter TWRP.
and try a few times if you can't get into it the first time.
Zenith said:
When you see the sony logo, or watch the LED light up, press volume down button to Enter TWRP.
and try a few times if you can't get into it the first time.
Click to expand...
Click to collapse
Ok, I'll try, strange is that I donwloaded "quick boot" exactly to avoid this rush against the time, and reboot in recovery mode has this behaviour. I'll try in simple way now.
Raf3000 said:
Ok, I'll try, strange is that I donwloaded "quick boot" exactly to avoid this rush against the time, and reboot in recovery mode has this behaviour. I'll try in simple way now.
Click to expand...
Click to collapse
Whichever suits you
Do a full wipe and flash tangerine after flashing the ROM,
Don't reboot before flashing tangerine as you'll be stuck with the Cyanogen recovery.
Zenith said:
Whichever suits you
Do a full wipe and flash tangerine after flashing the ROM,
Don't reboot before flashing tangerine as you'll be stuck with the Cyanogen recovery.
Click to expand...
Click to collapse
Nope... I'm still stuck at recovery point, I cannot access, I can't stop the boot... i hate it!!
You're stuck in a bootloop?
---------- Post added at 02:12 AM ---------- Previous post was at 02:02 AM ----------
Raf3000 said:
Nope... I'm still stuck at recovery point, I cannot access, I can't stop the boot... i hate it!!
Click to expand...
Click to collapse
If you're stuck in a bootloop, then turn off your phone (using the button on the back)
Download and flash this via 'fastboot mode' on Flashtool,
Your phone won't boot, but you'll be able to get in recovery by pressing the vol down.
and if your phone doesn't have much charge left, then leave it on charge for sometime after flashing the .elf file.
Nono thank's God.
I'm stuck because I can't update, since I have no chance to access the recovery menu: it brings me directly to original phone. No Rashr (store or linked), no dd ... nothing seems to work for recovery. I'm afraid that if I'll execute the batch for CWM_SP_4.4.1 it will work, but I'll be again at the very bad point of 2 days ago after flashed...
Raf3000 said:
Nono thank's God.
I'm stuck because I can't update, since I have no chance to access the recovery menu: it brings me directly to original phone. No Rashr (store or linked), no dd ... nothing seems to work for recovery. I'm afraid that if I'll execute the batch for CWM_SP_4.4.1 it will work, but I'll be again at the very bad point of 2 days ago after flashed...
Click to expand...
Click to collapse
That will work too, and I think that will be easier for you to install and enter recovery.
Install that, reboot, press vol. down button when you see the fourth light (probably blue).
this is retarded and i dont know how else to describe it.
failed to validate boot image. ret=-1
this phone has the latest aosip build 3.3 on it and i have not done anything to it since i flashed that build when the dev posted it A MONTH AGO. everything has been fine, normal, didnt even mess around with xposed on this flash....
i am browsing reddit, when an app downloads in the background. which app? i have no god damn idea. google play services stops, reddit stops, phone reboots and is stuck on fastboot. went to recovery. what do you know i cant access a backup even though i ALWAYS have one. what the bloody hell.
if i lose my data. somebody please help me.
Use fastboot to flash system and boot.
And if you are going to keep flashing stuff instead of just running stock, you should probably learn the basic methods of recovery BEFORE hand so you don't freak out and make long winded posts about how things are "retarded" because you don't know the basics of fixing problems.
so you relocked you're bootloader? what version of android is the phone on?
simms22 said:
so you relocked you're bootloader? what version of android is the phone on?
Click to expand...
Click to collapse
the bootloader is still unlocked....
6.0.1.
scryan said:
Use fastboot to flash system and boot.
And if you are going to keep flashing stuff instead of just running stock, you should probably learn the basic methods of recovery BEFORE hand so you don't freak out and make long winded posts about how things are "retarded" because you don't know the basics of fixing problems.
Click to expand...
Click to collapse
lol.
scottshebs said:
the bootloader is still unlocked....
6.0.1.
Click to expand...
Click to collapse
you can reflash your ROM, dirty, and won't lose any data. by dirty, I mean don't wipe a single thing. just reflash your ROM, gapps, SuperSU, and reboot.
simms22 said:
you can reflash your ROM, dirty, and won't lose any data. by dirty, I mean don't wipe a single thing. just reflash your ROM, gapps, SuperSU, and reboot.
Click to expand...
Click to collapse
well, theres no data when i boot into recovery mode. nothing anywhere. unable to mount to storage.
anyone?
scottshebs said:
anyone?
Click to expand...
Click to collapse
twrp does have an option to mount, whichever partition you want. but it sounds as your bootloader is locked(I hope not), as recovery acts like yours is doing when the bootloader is locked. boot into your bootloader and see if it says locked or unlocked. also, you can use twrp to find that storage location if it just isn't showing properly.
simms22 said:
twrp does have an option to mount, whichever partition you want. but it sounds as your bootloader is locked(I hope not), as recovery acts like yours is doing when the bootloader is locked. boot into your bootloader and see if it says locked or unlocked. also, you can use twrp to find that storage location if it just isn't showing properly.
Click to expand...
Click to collapse
device is unlocked, status code 3.
scottshebs said:
device is unlocked, status code 3.
Click to expand...
Click to collapse
then you do not own a brick, you just need to do some work and research to get your phone back. flashing a factory image would help, if you can't figure out what's wrong with twrp, you might even try fastboot flashing twrp again.
simms22 said:
then you do not own a brick, you just need to do some work and research to get your phone back. flashing a factory image would help, if you can't figure out what's wrong with twrp, you might even try fastboot flashing twrp again.
Click to expand...
Click to collapse
trying not to lose my data, what would be the safest thing to try first?
scottshebs said:
trying not to lose my data, what would be the safest thing to try first?
Click to expand...
Click to collapse
a dirty flash of your current ROM, but you need to figure out twrp first. or you can try fastboot flashing only the system.img from a factory.img.
simms22 said:
a dirty flash of your current ROM, but you need to figure out twrp first. or you can try fastboot flashing only the system.img from a factory.img.
Click to expand...
Click to collapse
wont even boot into recovery now.
Will it boot into fastboot? That is all you need, and you have been told several times you can just flash system.IMG with that, or reflash recovery... I'd flash the system.IMG of what ever version you last updated your bootloader to, or if your up to date just flash the most recent system to repair the os and boot to repair any kernel issues...
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
scottshebs said:
lol.
Click to expand...
Click to collapse
Why do you quote the solution to your problems, respond with "lol" then go back to asking how to fix it?
Try reflashing your recovery or booting into it to see if that works
scottshebs said:
wont even boot into recovery now.
Click to expand...
Click to collapse
try fastboot flashing twrp again.. fastboot flash recovery recoveryname.img
simms22 said:
try fastboot flashing twrp again.. fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
sending 'recovery' (12004 KB)...
OKAY [ 0.378s]
writing 'recovery'...
(bootloader) Failed to flash partition recovery
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 11.415s
holeindalip said:
Try reflashing your recovery or booting into it to see if that works
Click to expand...
Click to collapse
neither boot.img or recovery will flash. both failed.
scryan said:
Will it boot into fastboot? That is all you need, and you have been told several times you can just flash system.IMG with that, or reflash recovery... I'd flash the system.IMG of what ever version you last updated your bootloader to, or if your up to date just flash the most recent system to repair the os and boot to repair any kernel issues...
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
Why do you quote the solution to your problems, respond with "lol" then go back to asking how to fix it?
Click to expand...
Click to collapse
tried to flash both, neither worked.
I rooted my phone 2 weeks ago. While backing up and restoring Dem keys, I broke something I don't kno. Now every custom rom I install boots and gets stuck at Phone is starting and then reboots. Tried LOS 16, 17.1 and Pixel experience rom. But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?
GOrMHATRe said:
But result is the same. Sony firmware boots perfectly, Twrp works, but custom roms don't.
Click to expand...
Click to collapse
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
GOrMHATRe said:
Is it possible to wipe everything , all partitions and repair them using TWRP? I kno that option exists in Twrp and I have drm keys backed up. But woud that solve the problem I face with custom roms?
Click to expand...
Click to collapse
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.
SXUsr said:
Are you missing a step in the instructions, like flashing the boot.img for the roms you're trying to install?
To start over use the Flashtool, Newflasher, or even PC Companion. There is even Sony EMMA when something really messes up.
Click to expand...
Click to collapse
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
I have already use flashtool and newflasher. That's how I rooted my phone. Both of them are successful in flashing stock sony firmware. But the custom roms are in zip file. Don't kno of its possible to flash those using flashtool.
GOrMHATRe said:
Boot.img is part of rom zip file. With all 3 roms I tried, there was no instruction to flash boot separately. It's always flash recovery and then flash rom using recovery.
Click to expand...
Click to collapse
Steps :
Remove your screen lock (set it to swipe up or none) and remove all your fingerprints registered.
Download the zip above and extract the boot, system and vendor images
Make sure you have Android 10 TWRP as mentioned above with link
Go to recovery > wipe and wipe system, cache and data nothing else.
Then go to install and flash boot.img as boot image, system.img as system image and vendor.img as vendor image.
Click to expand...
Click to collapse
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.
SXUsr said:
- [ROM] Pixel Experience 10.0 Plus
Always extract the boot.img and flash it with fastboot. If there is no instructions then still do it.
Click to expand...
Click to collapse
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.
GOrMHATRe said:
Latest file of PE rom is in zip format. Boot.img is in zip . But vendor and system are not img files.
Click to expand...
Click to collapse
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.
SXUsr said:
Then extract the boot.img and flash it using fastboot, along with TWRP, then flash the rom. That should work flashing any custom rom.
Click to expand...
Click to collapse
I tried this but the result was same. Rom boots upto the lock screen. Then when I swipe it shows: phone is starting and goes into bootloop. I even tried an older version of PE Rom whic contain s only img files but again same result.
You kno initially, after I unlocked the bootloader I just installed stock rom and installed LOS on top of it as per guide. It worked well. I coud go into menu and see apps.
But I panicked that I had forgotten to restore drm keys. Instead of first checking camera, I went back and restored the Ta partition and repeated the steps after it upto installation of rom and since then I have faced problems . Restoring ta partition and flashing stock rom after it is where I have made a mistake and broken something. Can this be fixed with twrp. I kno there are options in twrp to format & repair partitions. Coud that help to repair what ever that was broken?
GOrMHATRe said:
Coud that help to repair what ever that was broken?
Click to expand...
Click to collapse
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?
SXUsr said:
No more than the Flashtool, Newflasher or PC Companion, so I wouldn't even consider using TWRP. Check your service menu for the status of your DRM keys, flashing them is a one time process so if they have been successfully restored there is no need to flash them again.
Use Sonys Flashtool to repair, and start over. If you're still having issues, then user error is at play here. What command in fastboot did you use to flash the kernel?
Click to expand...
Click to collapse
Which kernel are you speaking about? I had backed up Ta image using renoroot exploit and restored it using:
adb pull /data/local//tmp/TA-unlocked.img
adb push TA-locked.img /data/local/tmp
Then in window with temp root prompt:
cd /data/local/tmp
de if=TA-locked.img of=/dev/block/bootdevice/by-name/TA
sync
sync
Reboot phone
But actually, when I checked my phone just now and that tmp directory seems empty. So, does that mean TA didn't get restored properly? Is that why I am facing problems? Stock roms seem to be working fine.
As for sony's own flashtool, I have it installed. But thought it doesn't offer any different functionality than newflasher or old flashtool? Woud sony flashtool help me go back to square 1 and make my phone as it was before rooting so that I can do everything again properly?
GOrMHATRe said:
Which kernel are you speaking about?
Click to expand...
Click to collapse
The kernel of the rom. Check your service menu for drm status.
SXUsr said:
The kernel of the rom. Check your service menu for drm status.
Click to expand...
Click to collapse
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.
GOrMHATRe said:
The keys are there. The rooting status is shown not done because I have used that hide root unlock patch after going back to stock rom.
Click to expand...
Click to collapse
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.
Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).
SXUsr said:
So, now forget your drm keys for a minute, and do the following.
1. Use Sonys flashtool to reset your phone. Make sure you've backed up what you need to.
2. Using fastboot, flash both the kernel of whatever rom you wish to use, and TWRP.
3. Following the instructions of the rom you want to flash, install the rom using twrp. You may want to read them first to ensure you're using the required stock firmware that you will be flashing over.
Click to expand...
Click to collapse
I will try this but after some time. I have experimented on my phone a lot in recently. Need it to be stable for work for some time now. My secondary phone is not setup to work with gmail etc. Thanks for all the advice you have provided though.
On another note, now that Android 11 is out, do you think we will get a rom based on it for Xz1 compact? I even had a thought of skipping 10 and going for 11 based rom.
thefelineofaveb said:
Have you tried NOT restoring TA partition? It isn't needed with custom ROMs (as far as I know).
Click to expand...
Click to collapse
I have not touched drm keys after I backed up and restored them for the 1st time.