So I have a Sony Xperia Z1 C6902
And I've been messing around with ROMs, since I didn't know what exactly I wanted I've been installing a lot of different ROMs for about two-three days. I ended up using Slimroms as the ROM and RockZ1 as the kernel. I specifically used that version in particular since I wanted to use KitKat instead of Lolipop.
So after a while of using it, I found out it somehow became not rooted, and I couldn't install SuperSU properly (what with updating binaries and such) and this phone had a previous owner who had the bootloader unlocked and everything unlocked previously with this ROM
So I decided to try to root it using this method then when I went to flash C690X_14.4.A.0.108_KernelOnly.ftf as part of instructions, my phone ended up being stuck on a Blank Screen somehow?
The thing about the Blank Screen is that upon booting, the Sony screen shows up, and then nothing else. However, I can lock the phone, and when I unlock the Sony logo dissapears and I get a completely blank screen. I could touch certain areas and get some kind of feedback on what I assume is the PIN screen. So I just assumed that means the ROM isn't compatible with this kernel, so I flashed C690X_14.4.A.0.157_KernelOnly.ftf ahead of instruction since I couldn't normally access the phone to use Debugging because of the lock PIN.
On boot again, it still didn't show anything, so I just tried a Hard Factory Reset using the red button on the phone. That didn't resolve my problem whatsoever, but when I booted it again and touched the blank screen, I get Phone Dial noises?
Help?? The phone isn't bricked as far as I'm aware, since it can still boot and such, but I can't get into recovery to flash other roms or kernels, and I don't know what to do.
Update, I suppose. I tried the Sony PC Companion method, with repair phone/tablet, and it just gave me an error saying I have modified software and it didn't do anything about it.
Unecessary post, apologies
Unecessary post, apologies
Related
Hey guys,
as I did not find any matching solutions to my problem (and due to the fact that I can't post within developer forums yet), I opened a new thread. If there has been similar questions like mine with working solutions, then I am sorry to doublepost the problem.
I have a Sony Xperia Z1, model number C6903. I rooted it today, following this method
http://www.youtube.com/watch?v=1aq9YTlfCgc
taken from this original post
http://forum.xda-developers.com/showthread.php?t=2572988
I followed the tutorial step by step, rooted the device properly (worked fine, checked with the root basic app checker or whatever its called), and then wiped all data from it using dualrecovery. After that, i put the .290 software onto my sd card and flashed my phone using dualrecovery - as the tutorial said. Finally, I used Flashtool to flash the C6903_14.2.A.0.290_Stripped.ftf onto my phone.
After this process finished, I wanted to boot my phone.
That was when things got weird: The sony logo appeared for a short time, and then it powered off / rebooted itself. Sony logo appeared again, switched off again and rebooted for another time. But it would not do any more than that... seems like its catched within an endless loop or something.
What I tried to solve this problem:
- enter dual recovery: this worked at the beginning, I could switch my phone off and get it out of the loop
- flashed it again (first with dualrecovery, then with flashtool)
- after that I could not even get into dual recovery mode
- then I tried to flash the .534 ftf firmware onto my device, because with that it worked properly after root. But every time I connected my phone within flashmode to my pc and started the flashprocess, my phone disconnected after a short time and booted into the endless loop again
I don't know what else to try, so I ask you guys for help. Should I leave the phone within the loop for a couple of hours hoping that it starts eventually? Should I try to flash again? Is there any other possibility to enter dual recovery? Should I maybe flash an original sony firmware on it?
Thanks in advantage for your help and time,
flamingo
It sound slike you did everything right, I would repair using pccompanion and start again. Make sure you do every step correctly and in order and don't miss anything
Let us know how you get on
gregbradley said:
It sound slike you did everything right, I would repair using pccompanion and start again. Make sure you do every step correctly and in order and don't miss anything
Let us know how you get on
Click to expand...
Click to collapse
Thanks for the very quick reply. I've just done that, and all went properly! I am now back on .136, and the device works perfect. Think I'll continue with the 4.4 Kitkat instead of the .290, as this did not work out all to well...
Thanks again for your quick and very good advice!
flamingo
Hello,
I think I did something really wrong with my Xperia Z. I rooted it a month ago, I have the latest stock rom. Yesterday, I downloaded an app called Flashify on the play store who claimed to be able to flash recoveries and zips directly from phone, as long as it was rooted. I tried to flash the purexaudio mod to my phone, and since then it has become unusable. It first started to be very hot, then laggy, which forced me to shut it down. Now everytime I turn it on, it is usable for barely two minutes, before it becomes really laggy and nothing works or it freezes. Some actions directly crash my phone, such as opening the developers settings. I looked at the RAM usage on the phone's settings and the RAM is filling up progressively until the total 1.8GB of RAM is used and my phone freezes. I really don't know what is causing this.
It gets even worse, as I've managed to factory reset my phone with the sony PC companion, but the problem is still there. I can't access reccovery but I can access fastboot mode. However, neither Flashtool or fastboot command shell will flash a recovery for me (I get an "access denied" error). I can't flash the stock kerne with Flashtooll, I have the message : "Processing of loader.sin finished with errors." (I had this problem when I rooted it but I really can't remember how I fixed it).
I'm really anxious about what I've done with my phone, I hope someone could help me recover my phone as I honestly don't know what to do at this point...
Thank you so much in advance.
williaam said:
Hello,
I think I did something really wrong with my Xperia Z. I rooted it a month ago, I have the latest stock rom. Yesterday, I downloaded an app called Flashify on the play store who claimed to be able to flash recoveries and zips directly from phone, as long as it was rooted. I tried to flash the purexaudio mod to my phone, and since then it has become unusable. It first started to be very hot, then laggy, which forced me to shut it down. Now everytime I turn it on, it is usable for barely two minutes, before it becomes really laggy and nothing works or it freezes. Some actions directly crash my phone, such as opening the developers settings. I looked at the RAM usage on the phone's settings and the RAM is filling up progressively until the total 1.8GB of RAM is used and my phone freezes. I really don't know what is causing this.
It gets even worse, as I've managed to factory reset my phone with the sony PC companion, but the problem is still there. I can't access reccovery but I can access fastboot mode. However, neither Flashtool or fastboot command shell will flash a recovery for me (I get an "access denied" error). I can't flash the stock kerne with Flashtooll, I have the message : "Processing of loader.sin finished with errors." (I had this problem when I rooted it but I really can't remember how I fixed it).
I'm really anxious about what I've done with my phone, I hope someone could help me recover my phone as I honestly don't know what to do at this point...
Thank you so much in advance.
Click to expand...
Click to collapse
Well, that's not weird at all that you're getting "access denied" via fastboot. You said you've rooted your device, but did you unlock your phone's bootloader?
LaurynasVP said:
Well, that's not weird at all that you're getting "access denied" via fastboot. You said you've rooted your device, but did you unlock your phone's bootloader?
Click to expand...
Click to collapse
No, I guess I didn't... My bootloader status in Flashtool is : ROOTABLE I'm going to try doing that first. Thank you so much for your fast answer
I have a big problem actually now, as repairing my firmware with the sony software removed the USB debugging option. And opening the "developers settigns" to turn it back on still makes the settings crash. So I have no way of unlocking the bootloader now have I?
EDIT : Okay, nevermind. I managed to unlock the bootloader and flash a custom recovery (Cyanogen recovery). But now I'm on a boot loop (Sony message then Xperia then phone restarts)
What should I do now?
EDIT 2 : Solved the problem by simply wiping all caches/data from my recovery (ended up setting up the more traditional CW recovery) + sideloading a custom ROM (Ultimate PureZ). Now everything's working perfectly.
Thank you again for suggesting to unlock the bootloader, I couldn't have flashed the recovery otherwise. Have a nice day!
williaam said:
I have a big problem actually now, as repairing my firmware with the sony software removed the USB debugging option. And opening the "developers settigns" to turn it back on still makes the settings crash. So I have no way of unlocking the bootloader now have I?
EDIT : Okay, nevermind. I managed to unlock the bootloader and flash a custom recovery (Cyanogen recovery). But now I'm on a boot loop (Sony message then Xperia then phone restarts)
What should I do now?
EDIT 2 : Solved the problem by simply wiping all caches/data from my recovery (ended up setting up the more traditional CW recovery) + sideloading a custom ROM (Ultimate PureZ). Now everything's working perfectly.
Thank you again for suggesting to unlock the bootloader, I couldn't have flashed the recovery otherwise. Have a nice day!
Click to expand...
Click to collapse
You're welcome, but in this case you've made a major mistake - you didn't take TA Partition backup in which all DRM keys are being kept. Now you've erased them permanently, this will cause some stock applications to won't work (camera stabilization and etc.,).
Have a nice day you too
LaurynasVP said:
You're welcome, but in this case you've made a major mistake - you didn't take TA Partition backup in which all DRM keys are being kept. Now you've erased them permanently, this will cause some stock applications to won't work (camera stabilization and etc.,).
Have a nice day you too
Click to expand...
Click to collapse
Really? :/ What won't work exactly.?. I bootloaded my phone the official way though...
And BTW that's strange but when I put my SDCard back into my phone it crashed just like before? I guess I should format it?
williaam said:
Really? :/ What won't work exactly.?. I bootloaded my phone the official way though...
And BTW that's strange but when I put my SDCard back into my phone it crashed just like before? I guess I should format it?
Click to expand...
Click to collapse
Guess so. If even will update to earlier version (4.4.x) or later BE2 won't work, as well as camera stabilization (focus, well, it works, but photos are a bit like blured) and some other functions that I don't remember at the moment. It doesn't matter how did you unlock your bootloader, the fact that you've unlocked your bootloader is the most important. I'm sorry, but there's nothing we can do about it (DRM keys recover) at the moment. Maybe in a future there will be found a solution for this, but then our phone, I suppose will be like a nokia 3310 in nowadays.
Btw, you can still get some functions working, just surf this forum for unlocked bootloader functions "Get back" or sth., don't remember thread name either.. :|
So here's my story: my phone was JellyBean. I didn't tinker with it, didn't root, just used some launchers. It upgraded to KitKat. I kept using it, even though I liked JellyBean better. Then one month ago it froze and stopped responding even to physical buttons. I managed to restart it, but it wouldn't go past the intel logo. Somehow I got it to go past it and give me like two seconds on before it would freeze and become unresponsive again, so I got to enter safe mode (all following instructions on the internet, which buttons to hold to manage to get into safe mode). Once in safe mode, I deleted every app that had been recently updated or installed, one at a time, trying to turn my phone on each time, until I finally deleted facebook (that enourmous blue monstrosity taking all that internal space), and the phone seemed normal. I re-installed the other apps I had uninstalled, then one day later, it froze again. Now it wouldn't go past the intel logo. Only then I gave up and used RSDLite to re-install the firmware - BUT! The firmware I managed to find was JB, but I had been wanting to downgrade for some time, anyway, so I unlocked the bootloader and flashed JellyBean. And it worked. I was proud. Then one month later, today, it froze again. I can do the same procedure, and lose all my data again, but I fear the problem will remain unsolved and it will freeze/crash/explode one month from now. Can someone help me figure out what my problem is, or give an alternate solution to try?
TL;DR:
my razr i was stuck on the intel logo screen, I unlocked the bootloader and flashed JB, it worked, one month later it is now stuck on the WARNING BOOTLOADER UNLOCKED screen. Please help thank you.
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/google-nexus-5/development/fix-bypassing-pie-security-check-t2797731/page1
AgusC said:
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/goo...x-bypassing-pie-security-check-t2797731/page1
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. For the best available help, I'm going to move your question to your device's Q&A forum. Good luck!
AgusC said:
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option (...)
Click to expand...
Click to collapse
I do not know if finally you fixed the problem with your moto, but you can do a clean install of a stock rom, or maybe cm12/cm12.1...
How to, and link with the rom: http://forum.xda-developers.com/moto-x-2014/general/img-5-0-reteuall-xt1092-lxe22-46-19-t2997745
cyker31 said:
I do not know if finally you fixed the problem with your moto, but you can do a clean install of a stock rom, or maybe cm12/cm12.1...
How to, and link with the rom: http://forum.xda-developers.com/moto-x-2014/general/img-5-0-reteuall-xt1092-lxe22-46-19-t2997745
Click to expand...
Click to collapse
Hey! Thanks a lot for the advice, ill try to do what you said, although im not sure how to use fastboot. Ill tell you if it worked.
So ive just recieved an s3 8190 mini not an n or l model labled as sapres repairs, i have some experiecne flashing phones including a s3 mini-n so thought i'd grab this one to fix it and sell on...boy was i wrong
many hours later of various flash attmepts and reading troublshooting methods on the problems this phone does little else but restart a lot!
it wont accept anything ive flashed, i cant boot into recovery or root it sucessfully, however it will boot into download mode (a ray of hope perhaps?) after flashing various recoveries and trying to boot into it the bottom leds flash and it restarts again and it just wants to boot up normally no matter what, ive tried the 3 buttons then releasing only the power after i see the logo as ireads that worked for a few
the phone requires a pin to be entered at start which was in the box on a piece of paper, once in the time i get varies before it resets again and any settings i changed are restored things like wifi mode etc are all back...wtf is this? also apps cant be uninstalled!! and more importanly i cant factory reset, i press the first few buttons and then the final one does nothing....there is a missed call dated last year some time that shows up in the notifications area...
im currently flashing official firmware via link on this site that matches the baseband so hoping that might do something, but that seems like bind mans hope in hell, ive tried a few things from this site like a flash that makes the 3 buttons "work" which it did for some, thought not done anyhting with adb/fastboot being new to it, the phone wasnt recognised the few times i tried it.
where now then just what is wrong wiht this phone and can i get it up & running?