What is working: same as CM
What isn't working: same as CM
Credits:
Mozilla, lissyx
Download:
Code:
http://support.intwebsrv.pl/eagle-build.tar.xz
733cb86ad4c0d666da8c4c4cee6fca08563655d2 eagle-build.tar.xz
Updates:
Code:
http://support.intwebsrv.pl/updates/eagle-b2g-0001.zip
Please report bug at http://support.intwebsrv.pl/
Installation guide:
1. Update TA with Emma
2. Flash device:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
3. Flash recovery with CM Recovery
4. Apply updates via CMR
Updates naming convention:
1. eagle-b2g-[0-9]{4}.zip - incredimental (delta) update
2. eagle-b2g-[0-9]{4}p.zip - full update (include all prev. updates)
Already known bugs:
- volume up button doesn't work - fixed in eagle-b2g-0001
- after reboot device goes to bootloop - fixed in 733cb86ad4c0d666da8c4c4cee6fca08563655d2
I've have some time at begining of next week i'll try to fix some bugs.
PS. Please do not use it if u had to has be always available under phone - it may break when you least expect.
wow new family of rom M2, give us screenshot for this rom
Screenshots added.
Please remember it's still under development.
Url not correct..
Sent from my D2303 using XDA Free mobile app
There is a Xperia m2 group on g+ you may want to post it on there aswell.
D2303,18.3.1.C.1.15 kk, deodexed, debloated, rooted, philz touch recovery, bravia engine 2+x-reality+z3 super vivid, viper audio, xposed mods.
AssoDiPicche said:
Url not correct..
Sent from my D2303 using XDA Free mobile app
Click to expand...
Click to collapse
URL fixed.
boot.img and userdata.img flashed fine but got this error: "FAILED (remote: Command not allowed)" when trying to flash system.img
[EDIT]
Sorry, its ok now. I reflashed the TA update with Emma and system.img got flashed fine, too. Its booting now....with a pic. of a boot
quake73 said:
boot.img and userdata.img flashed fine but got this error: "FAILED (remote: Command not allowed)" when trying to flash system.img
[EDIT]
Sorry, its ok now. I reflashed the TA update with Emma and system.img got flashed fine, too. Its booting now....with a pic. of a boot
Click to expand...
Click to collapse
I use it on my device too so I find some bugs already, but if You find something please report it (http://support.intwebsrv.pl). At this night i'll try to fix some of them and tomorrow i will upload new release.
Volume up doesn't work and after reboot or power off i've stuck bootloop!
Would be nice if someone compile Ubuntu for M2.
lozohcum said:
Would be nice if someone compile Ubuntu for M2.
Click to expand...
Click to collapse
I've always wanted fxOS - first time i've built it for wt19i but wasnt useable without ril.
lozohcum said:
Would be nice if someone compile Ubuntu for M2.
Click to expand...
Click to collapse
Agreed. I would like to try Ubuntu
As i remember Ubuntu Touch (like Sailfish) uses libhybris and at this moment no one start porting it to Xperia devices.
New build?
Sent from my D2303 using XDA Free mobile app
Yes, i'll upload it to server, but once i got bootloop again and i'm not sure what happend.
Believe me , I begin to love this rom!!, is a serious problem unfortunately... On which device tree you based? FxOS have a beautiful graphics, and the battery draining is great.
At this moment i remove one bootloop reason. With second i know how to temp fix problem (clean /data/property/* then reboot) but i don't want to put dirty fixes to ROM.
Is a permission problem?
Sent from my D2303 using XDA Free mobile app
Rights looks correct.
Code:
root root 0700 /data/property
root root 0600 /data/property/*
Nothing in logcat but i detect those directory by checking directories timestamp.
How i fix bootloop??
Sent from my D2303 using XDA Free mobile app
Related
Root status: Permission Denied
Lets keep this thread reserved only for discussion related to rooting this phone. We haven't achieved root yet but I know the way to do it.
You need to follow this guide in order to root your device: http://whiteboard.ping.se/Android/Rooting
So till now I have been able to:
-Build a new kernel
-Unpacked the kernel using kernel kitchen by championswimmer and flashtool(for the sin file)
-.Made the changes in ramdisk
But the next step requires packing it back again. And for doing that you need the cmdline from the kernel.
Its located in /proc/cmdline.
I tried to view it via adb but obviously the system denied the permission because of no root.
Usually you can easily obtain cmdline parameters from the boot.img itself, but in this case, Sony has done some shizz so that you cant obtain it directly. Plus this is my first Sony device so I dont have much knowledge regarding this..
I wont get much time to work on it becuz of my exams.. that's why this thread is here
If you can help/contribute in any way then you are surely welcome. But no noob posts here.
@InfinityShooter use archi's kitchen for unpacking boot.img
first convert stock kernel.sin file to boot.img(by just renaming it)
archi's kitchen will give you the cmdline and other parameters to pack the kernel..
k2wl said:
@InfinityShooter use archi's kitchen for unpacking boot.img
first convert stock kernel.sin file to boot.img(by just renaming it)
archi's kitchen will give you the cmdline and other parameters to pack the kernel..
Click to expand...
Click to collapse
It doesn't work. Sony uses a different kind of boot.img. I have tried dsixda kitchen also, it didnt work out.
InfinityShooter said:
It doesn't work. Sony uses a different kind of boot.img. I have tried dsixda kitchen also, it didnt work out.
Click to expand...
Click to collapse
oh !!! my old sony xperia m used have kernel .sin which used to convert to boot.img by renaming....
Hmmm... how about using a dd command to extract boot.img to sdcard and then unpack it in archi's kitchen????
k2wl said:
oh !!! my old sony xperia m used have kernel .sin which used to convert to boot.img by renaming....
Hmmm... how about using a dd command to extract boot.img to sdcard and then unpack it in archi's kitchen????
Click to expand...
Click to collapse
I don't know if this can help at all: http://forum.xda-developers.com/showthread.php?t=1659584.
It's been ages since I gave up on linux, even as an amateur, so my knowledge is quite limited and, to be honest, a lot of hunch is involved. That's why I am so hesitant at trying this myself.
Anyway I hope this helps a bit.
Also you can get the latest firmware for D2203 (18.4.C.2.12) from here: https://mega.co.nz/#!bMBg1Rqa!aqGcTv6ved0ifh867pbnVVsc-4t55lR9OOij1iSiNLA, which means that one can probably try without unlocking the bootloader...
I have already made the kernel but needs testing. Anyone here with unlocked bootloader and d2202 can try hotboot this using flash tool.
http://d-h.st/rx7e
Try at your own risk.
There is 0% chance of bricking if you hotboot it.
DO NOT FLASH IT
I've tried the kernel. But I do not know how to enter CWM, whether the kernel already include CWM?
No it is not cwm you have to use adb to mount /system as read/write then push su to /system/bin and you will get root. All you need is get superuser from playstore.
Sent from my D2212 using XDA Free mobile app
Report!
The boot.img which I had posted has been confirmed working.
We now have the correct command for packing the boot.img thanks to @jerpelea
I'll be looking forward to making a recovery from source.
If it works then root is not far away
InfinityShooter said:
The boot.img which I had posted has been confirmed working.
We now have the correct command for packing the boot.img thanks to @jerpelea
I'll be looking forward to making a recovery from source.
If it works then root is not far away
Click to expand...
Click to collapse
will, it work on xperia e3 d2212
android-vinay said:
will, it work on xperia e3 d2212
Click to expand...
Click to collapse
Not now.. only for d2202.
I don't know if this a noob question: in the tutorial InfinityShooter posted earlier it says that the phone must have an unlocked bootloader. Thing is that I am a bit confused in terms of whether the bootloader must be unlocked to obtain the system image or in order to fastboot the insecure image. If it is just to obtain the image then wouldn't it be possible to cook the insecure image using the ROM image that Sony distributed to developers, leading to a solution that doesn't interfere with the bootloader?
after I try the kernel, no bugs are found, everything works fine, like wifi and the other no problem, just given cwm to facilitate root...
CWM
Ok this is the second build of the cwm kernel
You can get it here: https://www.androidfilehost.com/?fid=95832962473396055 Doesnt work
You have to HOTBOOT this kernel
Tell me if it works or not.
Troubleshooting:
If you are stuck at black screen then dont worry. Just press and hold power+vol up keys together for 20 seconds to reboot it.
On rebooting the system will automatically revert to stock kernel which you were using earlier.
Congrats! Your phone is working again!
i must have unlock bl?
Wysyłane z mojego WT19i za pomocą Tapatalk 2
Unfortunately yes. Bad thing is that when we unlock the bootloader the TA partition is formatted leading to various problems with Sony apps.
Okay I need help here. My testers report this kernel as working but it fails to work on my device. Please let me know what happens with you..
Link: http://d-h.st/NFR
Here are the EXACT things I do to flash it:
1. Open flashtool
2. Connect my phone
3. I click on thunder icon in flashtool and choose fastboot mode.
4.I click on "Reboot into fastboot mode[adb]"
5.I click on "Select kernel to hotboot" and open the boot.img inside it.
I look at my phone,its all dark. The blue light goes away
6.I click on check current device status and it shows adb connected
7.Orange led comes up as my phone is connected to pc
I see no sony logo or anything like that.
The screen is still BLACK! One thing I notice is that whenever I press the power key, the screen backlight turns on little bit enough for me to notice the varaiation.
Please post your intruction set if it works out for u.
I can't test it myself since I have locked bootloader but did you try to get a working adb shell at this state? If shell works then you might be able to push su and supersu to the device.
cnagr said:
I can't test it myself since I have locked bootloader but did you try to get a working adb shell at this state? If shell works then you might be able to push su and supersu to the device.
Click to expand...
Click to collapse
Dude I cant see anything on screen and you are talking about pushing files -.-
Dude you said that the phone appears to be connected to the pc in adb state, regardless of the phone screen state. That's where that big if of my suggestion came from.
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
drunken monkey said:
Hey group mates please help me
I'm currently using a nexus 5 and thought of sideloading the ota zip through nexus root toolkit so i first flashed stock recovery and then when i tried to sideload it, it started flashing till it reached 61% and which my phone said installation aborted for no reason.. Tried this more than 3-4 times but the result were all the same
I'm not sure what seems to be the issue here so it would be great if any one could help me solve this issue
Thanks in advance
Click to expand...
Click to collapse
Are you rooted or having custom kernel?
kaushikd said:
Are you rooted or having custom kernel?
Click to expand...
Click to collapse
I'm currently running stock recovery, stock os rooted and unlocked bootloader
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
drunken monkey said:
I'm currently running stock recovery, stock os rooted and unlocked bootloader
Click to expand...
Click to collapse
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
So while sideloading it should I unroot as well?
jsgraphicart said:
You can't be rooted to use the OTA. Anything that is modified in the system will cause this.
Click to expand...
Click to collapse
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
drunken monkey said:
So to sideload I have to be in complete stock without even SuperSU.. Is that correct?
Click to expand...
Click to collapse
That correct
Sent from my Nexus 5 using XDA Free mobile app
pauleyc said:
I downloaded the full image and extracted just the radio, system and boot image files. Then just a few fastboot commands with bootloader reboots inbetween and 5.0.1 works.
For reference, I used the following:
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
jrronimo said:
I was thinking about doing this, too... but am I correct to assume that this would cause data loss? I have TWRP and SuperSU installed at the moment.
Or, if there's an easy way to ditch these and do the OTA, I'd be okay with that, too.
Click to expand...
Click to collapse
It won't cause any data loss. It's about the only way to get the ota to work. But in your case, since you have twrp you should also flash the stock recovery.img
Sent from my Nexus 5 using XDA Free mobile app
No data loss (well, apart from root) if you flash just the radio, system and boot images. Worked great for me.
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
jrronimo said:
Thanks for the tips, guys. After extracting the full 5.0.1 firmware from the Factory Images page, there are system and boot .img files, but no radio. Is this normal?
Click to expand...
Click to collapse
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
There's a radio. It's in the first file you extracted, not the zip you also had to extract
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Good thing I didn't get past this step -- I had downloaded the wrong factory image. D: That'll explain things a bit...
---------- Post added at 02:13 PM ---------- Previous post was at 01:54 PM ----------
Alrighty! New problem: After the phone boots, I get the battery and signal icons in the top right, but a black screen otherwise. If I hit the power button to put it in sleep mode and then hit the power button again, I get a quick flash of the "Welcome to Android, select your language" screen. Any pro-tips?
If I have to set up from scratch, it's no big deal. Most of the important stuff should be backed up; it'd just be annoying. All that Desert Golfing progress!!!
Finally managed to get around it. Ended up updating TWRP and re-flashing most of the .imgs a bunch, then using TWRP to first let me back up data to my computer and then wipe partitions. I'm on 5.0.1 again.
Welp, that was painful, haha. I'm sure I did something wrong leading into this, but I'm not sure what that was...
If i just flash the whole Firmware that i downloaded from Google, will i be able to flash it and loose root?
I am OK with loosing root and beeing back to stock.
At this moment i have Lolipop 5.0 that is rooted with Chainfire.
I was running rooted stock 5.0 with TWRP and had already flashed the 5.0.1 radio, so I just fastboot flashed the 5.0.1 system.img and rerooted. All is well so far.
jd1639 said:
That correct
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So if I unroot and then sideload it will I loose all my data ?
P.s I'll be rooting it back immediately after I get 5.1
So is there any way which can avoid a data loss?
I still have a doubt, I saw rootjunky's video in which he sideload 5.1 to his nexus 7 using nrt..
Even I followed the same method but it didn't succeed for me
pauleyc said:
I have the exact same problem. The sideload gets to 61%, then shows the following message:
"/system/bin/install-recovery.sh" has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
I have a stock recovery, was rooted using Chainfire's first method for Lollipop (patched kernel) but flashed the stock kernel (fastboot flash boot boot.img) from the N5 5.0 image before the sideload.
Click to expand...
Click to collapse
So after flashing your stock kernal and stock recovery did the sideload work.. I mean that it didn't get stuck at the 61% mark?
Hello, I am trying to flash and install custom rom into my Xperia L for the last two days and I am getting really desperate and tired now. I get boot loop almost after everything and can't get it running, so at the end I end up flashing it again to OFW with flashtool to try it again.
I had Xperia X8 before and I wanted to get my new phone rooted too because it was slow and boring.
Phone is Sony Xperia L C2105, I have tried those builds:
15.0.A.1.36
15.0.A.2.17
15.3.A.0.26
15.3.A.1.14
I have boot loop unlocked and I have tried Thunderzap 4.14 kernel and also new Phantom kernel to get my phone rooted. Only way to get it rooted was using Extended stock kernel which I also found on this thread.. both ThunderZap and Phantom was stuck in bootloop, I could only get to the recovery (wiping phone or flashing kernel didn't help). I flashed the boot.img found in Extended stock with flash tool, than went to recovery and installed super user zip. This has Rooted my phone.
But now.. every time I try to flash new kernel trough recovery, it get installed but stuck in bootloop again. But actually I through that at this point I should be able to flash custom ROMs with recovery am I right? So there are two ROMs I tried. First was CM12 and the second was Resurrection Remix. But When I start installing its zip through recovery, at both times I got stuck at the second paragraph.
This is my recovery:
- - Installing: /storage/sd.............NIGHTLY-taoshan.zip
Finding update package...
Opening update package...
Installing update...
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/userdata
At the background there is green android in animation so it isn't frozen, but it is stuck in the last line I wrote for like 20 minutes now and nothing is happening. So. . . . . . I have to put battery out again, flash it into stock, probably into 4.2.2 and try it again and hope I will find something. But it is like the twentieth time I am flashing this phone with flashtool to stock and I don't really know what to do anymore. I found so much tutorials in there but the boot loop is there most of the time without access to recovery.
Also I am working on Mac OSX and I don't have windows, I was trying it on borrowed windows notebook yesterday but with same results, but most of the programs and scripts didnt work because I have read something like in my phone is different driver than in pc and I need whole SDK for changing that, so it has written something like bad server or something and that it is killing it, so every proces was much much longer.
Please, please someone help me do something with my phone, thank you very much
nrksrs said:
Hello, I am trying to flash and install custom rom into my Xperia L for the last two days and I am getting really desperate and tired now. I get boot loop almost after everything and can't get it running, so at the end I end up flashing it again to OFW with flashtool to try it again.
I had Xperia X8 before and I wanted to get my new phone rooted too because it was slow and boring.
Phone is Sony Xperia L C2105, I have tried those builds:
15.0.A.1.36
15.0.A.2.17
15.3.A.0.26
15.3.A.1.14
I have boot loop unlocked and I have tried Thunderzap 4.14 kernel and also new Phantom kernel to get my phone rooted. Only way to get it rooted was using Extended stock kernel which I also found on this thread.. both ThunderZap and Phantom was stuck in bootloop, I could only get to the recovery (wiping phone or flashing kernel didn't help). I flashed the boot.img found in Extended stock with flash tool, than went to recovery and installed super user zip. This has Rooted my phone.
But now.. every time I try to flash new kernel trough recovery, it get installed but stuck in bootloop again. But actually I through that at this point I should be able to flash custom ROMs with recovery am I right? So there are two ROMs I tried. First was CM12 and the second was Resurrection Remix. But When I start installing its zip through recovery, at both times I got stuck at the second paragraph.
This is my recovery:
- - Installing: /storage/sd.............NIGHTLY-taoshan.zip
Finding update package...
Opening update package...
Installing update...
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/userdata
At the background there is green android in animation so it isn't frozen, but it is stuck in the last line I wrote for like 20 minutes now and nothing is happening. So. . . . . . I have to put battery out again, flash it into stock, probably into 4.2.2 and try it again and hope I will find something. But it is like the twentieth time I am flashing this phone with flashtool to stock and I don't really know what to do anymore. I found so much tutorials in there but the boot loop is there most of the time without access to recovery.
Also I am working on Mac OSX and I don't have windows, I was trying it on borrowed windows notebook yesterday but with same results, but most of the programs and scripts didnt work because I have read something like in my phone is different driver than in pc and I need whole SDK for changing that, so it has written something like bad server or something and that it is killing it, so every proces was much much longer.
Please, please someone help me do something with my phone, thank you very much
Click to expand...
Click to collapse
omfg NEVER pull out battery while flashing oO
you will need stock 15.3.A.?.17 to flash custom roms.... also you will need to do a factory reset before flash....
and a "bootloop" after fresh rom....you know it needs 30min to boot up?(rewriting cache)
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
omfg NEVER pull out battery while flashing oO
you will need stock 15.3.A.?.17 to flash custom roms.... also you will need to do a factory reset before flash....
and a "bootloop" after fresh rom....you know it needs 30min to boot up?(rewriting cache)
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Hey thanks for answer, right now i am at 15.3.A.1.14 rooted and on Extended stock kernel found there: http://forum.xda-developers.com/xperia-l/development/kernel-extended-stock-kernel-v6-t2321550
I just wanted to try flashing Glade ROM, should I try it?
Also, At most kernels and roms there is not said which build I should use so I really dont know why it should be ?.17.. but what should I do with it when its stuck? Yesterday I went to sleep and left the Xperia installing CM12, I woke up after several hours and it was still on the second line.. I didnt ever said i have bootloop after successful fresh rom installing because I have never successfully flashed any rom because i got stuck.
But thank you wery much, I will try it on different build
nrksrs said:
Hey thanks for answer, right now i am at 15.3.A.1.14 rooted and on Extended stock kernel found there: http://forum.xda-developers.com/xperia-l/development/kernel-extended-stock-kernel-v6-t2321550
I just wanted to try flashing Glade ROM, should I try it?
Also, At most kernels and roms there is not said which build I should use so I really dont know why it should be ?.17.. but what should I do with it when its stuck? Yesterday I went to sleep and left the Xperia installing CM12, I woke up after several hours and it was still on the second line.. I didnt ever said i have bootloop after successful fresh rom installing because I have never successfully flashed any rom because i got stuck.
But thank you wery much, I will try it on different build
Click to expand...
Click to collapse
? was because i didnt remember the number....i guess its one ahead of your version (so ? = 1 ) you will DEFINITLY need LATEST stock to get a lollipop rom running without errors
SdtBarbarossa said:
? was because i didnt remember the number....i guess its one ahead of your version (so ? = 1 ) you will DEFINITLY need LATEST stock to get a lollipop rom running without errors
Click to expand...
Click to collapse
Ok, I will now download and flash 15.3.A.1.17, than flash kernel to get root and than I will try to flash Glade through recovery with instructions in its thread, thanks you so far, it will take me some time to download it and do everything but after that i will reply how I ended, really thank you
nrksrs said:
Ok, I will now download and flash 15.3.A.1.17, than flash kernel to get root and than I will try to flash Glade through recovery with instructions in its thread, thanks you so far, it will take me some time to download it and do everything but after that i will reply how I ended, really thank you
Click to expand...
Click to collapse
ok good luck bro....maybe i will be Glad(e) on you x)
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
ok good luck bro....maybe i will be Glad(e) on you x)
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
ok so I am on the newest build right now, rebooting into recovery
choosing wipe data/factory reset, wipe cache partition, wipe dalvik cache
now going to install Glade zip.. after confirmation this is the script:
Finding update package...
Opening update package...
Installing update...
Patching system image unconditionally...
Flashing SuperSU...
unmout of /system failed; no such volume
script succeeded: result was [ ]
Install from sdcard complete.
What the hell? I stayed in recovery, i am not sure if I can go out or what, how to properly flash it? What is Wrong?
nrksrs said:
ok so I am on the newest build right now, rebooting into recovery
choosing wipe data/factory reset, wipe cache partition, wipe dalvik cache
now going to install Glade zip.. after confirmation this is the script:
Finding update package...
Opening update package...
Installing update...
Patching system image unconditionally...
Flashing SuperSU...
unmout of /system failed; no such volume
script succeeded: result was [ ]
Install from sdcard complete.
What the hell? I stayed in recovery, i am not sure if I can go out or what, how to properly flash it? What is Wrong?
Click to expand...
Click to collapse
looks like the recovery you use is way to old...try to boot
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
looks like the recovery you use is way to old...try to boot
Click to expand...
Click to collapse
it said root access possibly lost and if I want to root again, I choose I want to and it started rebooting, now after sony logo there is animated green Glade logo going again and again, I will se if it will start, I will give it some time
EDIT: i have that app on card that can install recovery directly from system, if it wont strat i will propably have to flash to stock again and try the app
nrksrs said:
it said root access possibly lost and if I want to root again, I choose I want to and it started rebooting, now after sony logo there is animated green Glade logo going again and again, I will se if it will start, I will give it some time
EDIT: i have that app on card that can install recovery directly from system, if it wont strat i will propably have to flash to stock again and try the app
Click to expand...
Click to collapse
if it dont start....
download thunderzap4.14 from varuns site
then extract the boot.img from the zip...
and flash that boot.img...
then you will have a good recovery... factory reset...
flash glade
that should work
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
if it dont start....
download thunderzap4.14 from varuns site
then extract the boot.img from the zip...
and flash that boot.img...
then you will have a good recovery... factory reset...
flash glade
that should work
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Did it. The first time phone got stuck at thunderzap logo, second time I got into recovery, fastory reset + wipe cache, than flashed rom and got exactly the same script as before.. I am really starting to give up, any ideas?
nrksrs said:
Did it. The first time phone got stuck at thunderzap logo, second time I got into recovery, fastory reset + wipe cache, than flashed rom and got exactly the same script as before.. I am really starting to give up, any ideas?
Click to expand...
Click to collapse
ok....try another rom...maybe its the rom or your download
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
ok....try another rom...maybe its the rom or your download
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
will try that, buti am just wondering, when I wipe something I can see at most of the scripts this line:
E:unknown volume for path [/sd-ext] ..this is the only error i am getting but every other thing is all right, does it mean something?
EDIT: tried to flash cm12 after wiping and I got stuck at the same line again:
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/userdata
android in background is animated but I dont think it will get somewhere
nrksrs said:
will try that, buti am just wondering, when I wipe something I can see at most of the scripts this line:
E:unknown volume for path [/sd-ext] ..this is the only error i am getting but every other thing is all right, does it mean something?
Click to expand...
Click to collapse
lol that is the error you will get if you dont have a micro-sd (sd-ext) in phone
if you have no sd-ext....thats logic you can ignore
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
lol that is the error you will get if you dont have a micro-sd (sd-ext) in phone
if you have no sd-ext....thats logic you can ignore
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
but everything i am intalling is on my sd card so i have card inside, that doesn't make sense
also I have to put the battery out again during the rom instalation to abort
EDIT: Maybe different kernel could fix it but every other kernel I have found will bootloop it. Is there a way to exit boot loop after installing thunderzap or something?
nrksrs said:
but everything i am intalling is on my sd card so i have card inside, that doesn't make sense
also I have to put the battery out again during the rom instalation to abort
Click to expand...
Click to collapse
important: tested just on CM.
You must be on the latest stock firmware.
I want you to go to this link " http://forum.xda-developers.com/xperia-l/help/how-to-recover-xperia-l-t3129724/page5 " .
And to replay number #46 and download the attached file.
Extract the the file in your computer and open the cmd in the folder by pressing shift+LMB and write the code:
Code:
fastboot flash boot boot.img
important:connect your phone to the computer in fastboot before holding the vol+ and connect it.
Now you can press entre you have now CWM recovery .
Boot to recovery and flash CM12 then make a factory reset and boot to system .
If you want to flash the gapps don't flash directly after flashing CM12 just wait until your phone boot and contact me and I will guide you.
n78 shadow said:
important: tested just on CM.
You must be on the latest stock firmware.
I want you to go to this link " http://forum.xda-developers.com/xperia-l/help/how-to-recover-xperia-l-t3129724/page5 " .
And to replay number #46 and download the attached file.
Extract the the file in your computer and open the cmd in the folder by pressing shift+LMB and write the code:
Code:
fastboot flash boot boot.img
important:connect your phone to the computer in fastboot before holding the vol+ and connect it.
Now you can press entre you have now CWM recovery .
Boot to recovery and flash CM12 then make a factory reset and boot to system .
If you want to flash the gapps don't flash directly after flashing CM12 just wait until your phone boot and contact me and I will guide you.
Click to expand...
Click to collapse
As I have said in the very first post, I am on mac and cant do it in windows, but still i should be able to do it, I will just edit the code, will the boot.img root this phone? because if I am starting with stock firmwere do you mean rooted stock?
nrksrs said:
As I have said in the very first post, I am on mac and cant do it in windows, but still i should be able to do it, I will just edit the code, will the boot.img root this phone? because if I am starting with stock firmwere do you mean rooted stock?
Click to expand...
Click to collapse
No it will not just reboot to recovery after you flash it there's no need to boot to system becuse if you reboot to stock the WiFi will not work so just flash CM12 directly after flashing the boot.img .
That how I install CM12 in my phone and the WiFi and everything works fine.
And about the root: if you installed CM12 you can have a root in the developers option
Good luck bro.
n78 shadow said:
No it will not just reboot to recovery after you flash it there's no need to boot to system becuse if you reboot to stock the WiFi will not work so just flash CM12 directly after flashing the boot.img .
That how I install CM12 in my phone and the WiFi and everything works fine.
And about the root: if you installed CM12 you can have a root in the developers option
Good luck bro.
Click to expand...
Click to collapse
This is really weird, in a second I got stuck at the same line as before but it than continued and finished. As I chodes reboot to system it said it will root the phone or something, now there is blue robot head (probably cm12 animation), now it really looks like it will work,
I will say later if it booted into system, also good to say, for this one try I switched the sd card from which I were installing before, maybe it was card
wait, now there are some optimalisations or upgrades
nrksrs said:
This is really weird, in a second I got stuck at the same line as before but it than continued and finished. As I chodes reboot to system it said it will root the phone or something, now there is blue robot head (probably cm12 animation), now it really looks like it will work,
I will say later if it booted into system, also good to say, for this one try I switched the sd card from which I were installing before, maybe it was card
wait, now there are some optimalisations or upgrades
Click to expand...
Click to collapse
What for it .
It would take some time
It says " upgrading android apps " right???
I created TWRP and custom kernel for Z5 Premium E6853.
I won't update this kernel since I don't have Z5P.
NOTE: This kernel is not for people who don't read official instruction at Sony Developer World!
This note is ridiculous, but some people don't read long instruction even if it has risk.
Download:
https://dl.androplus.org/Xperia Z5 Premium_E6853/
NOTE: You should search how to setup adb and fastboot.
You can find how to for unlocking bootloader on Sony Developer World.
1. Download Z5P_AndroPlusKernel_v4a.zip and twrp-2.8.7.0-E6853-20151122_material.img
You also need SuperSU from this thread
2. Enter into fastboot mode and run these commands in same folder you downloaded 1.
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp-2.8.7.0-E6853-20151122_material.img
fastboot reboot
3. Press volume key when LED is on
4. Install SuperSU zip
5. Reboot and rooting is done
If TWRP didn't work, you can alternatively do this:
Code:
adb shell
rootsh +p
./SuperSU_files/install_SuperSU.sh
reboot
Source:
Kernel -
https://github.com/AndroPlus-org/android_kernel_sony_msm8994_kitakami_r2
Device tree -
https://github.com/AndroPlus-org/android_device_sony_kitakami
https://github.com/AndroPlus-org/device-sony-satsuki
AndroPlus said:
I created TWRP and custom kernel for Z5 Premium E6853.
I won't update this kernel or create one for Dual since I don't have Z5P.
Download:
https://dl.androplus.org/Xperia Z5 Premium_E6853/
NOTE: You should search how to setup adb and fastboot.
You can find how to for unlocking bootloader on Sony Developer World.
1. Download Z5P_AndroPlusKernel_v4a.zip and twrp-2.8.7.0-E6853-20151122_material.img
You also need SuperSU from this thread
2. Enter into fastboot mode and run these commands in same folder you downloaded 1.
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp-2.8.7.0-E6853-20151122_material.img
fastboot reboot
3. Press volume key when LED is on
4. Install SuperSU zip
5. Reboot and rooting is done
If TWRP didn't work, you can alternatively do this:
Code:
adb shell
rootsh +p
./SuperSU_files/install_SuperSU.sh
reboot
Source:
Kernel -
https://github.com/AndroPlus-org/android_kernel_sony_msm8994_kitakami_r2
Device tree -
https://github.com/AndroPlus-org/android_device_sony_kitakami
https://github.com/AndroPlus-org/device-sony-satsuki
Click to expand...
Click to collapse
Hi androplus
You do awesome work I have used your kernel on the z3 before. So happy to see you helping us out. Is there any changes or things you have added to this kernel or is it just rooted?
Thanks
Sent from my E6853 using XDA Free mobile app
rx7boy22 said:
Hi androplus
You do awesome work I have used your kernel on the z3 before. So happy to see you helping us out. Is there any changes or things you have added to this kernel or is it just rooted?
Thanks
Sent from my E6853 using XDA Free mobile app
Click to expand...
Click to collapse
Some changes are added, see changelog:
https://kernel.andro.plus/kitakami_r2.html
AndroPlus said:
Some changes are added, see changelog:
https://kernel.andro.plus/kitakami_r2.html
Click to expand...
Click to collapse
Thanks, yeah I should have guessed it will be based off the z5 changlog cause basically the same except for the screen.
Sent from my E6853 using XDA Free mobile app
Thanks again
WIth the newest files worked like a charm. Thanks!
I get this
FAILD (remote: Command not allowed)
What does that mean??
Thanks for the great job, did you have any side-effect ?
Have anyone guys the S1 Fastboot driver for my Z5P and me
---------- Post added at 03:09 PM ---------- Previous post was at 02:49 PM ----------
Ok, i Found the S1 driver and download it, but when i will install the driver, aborts the installation( installtion error)
My Os is Windows 10 64 bit
Jacob_Bentzen said:
I get this
FAILD (remote: Command not allowed)
What does that mean??
Click to expand...
Click to collapse
you have to unlock your bootloader first
I really need that first? I didn't need that with my LG G4
Ok i have install S1 driver, but i have the same problem as Jacob_Bentzen(FAILD (remote: Command not allowed))
You really should read instruction on Sony developer world...
If you don't read carefully, your device will be bricked.
Please don't use my kernel and TWRP if you don't want to read long instruction.
Great stuff - Followed Exactly and I have an unlocked BL, am rooted with TWRP! Yes, hopefully some development occurs...
Works great! Thanks!
Amazing been waiting to root for so long
This is cool thanks a massive bunch
I will be rooting and flashing the recovery after work.
One question, will I still get Xperia updates for the sony rom after I have rooted and will my phone be wiped after u locking bootloader and flashing recovery ?
Unlock
Hi
to unlock Sony Z5 bootloader go to: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Follow ALL instructions carefully!
Cheers
Aussie
Is there a way with closed BL to root??
I will not lost my DRM Keys
get2easy said:
Is there a way with closed BL to root??
I will not lost my DRM Keys
Click to expand...
Click to collapse
Not yet
Gentle Jesus said:
This is cool thanks a massive bunch
I will be rooting and flashing the recovery after work.
One question, will I still get Xperia updates for the sony rom after I have rooted and will my phone be wiped after u locking bootloader and flashing recovery ?
Click to expand...
Click to collapse
Any one know ?
Hey guys, just compiled a rootable kernel for the Z5P (E6883) 6.0.1 dual sim version, FW 224.
Features:
1. Sony RIC is disabled.
2. TWRP recovery - press volume up while booting.
3. Busybox.
4. DRM fix.
Code:
fastboot boot boot.img
fastboot reboot
IMPORTANT:
1. Please don't flash any recovery after flashing this kernel as recovery is already present in it.
2. Press volume up to enter recovery, pressing volume down won't work and the phone will reboot.
The first version was having some root permission issues. Flash the new kernel and then flash SuperSU 2.65 via recovery.
Reboot to system and manually install SuperSU 2.74 beta. Update the binary and reboot.
Thanks to tobias.waldvogel for his resources and tutorials.
Please don't flash it on any other device.
I'll not be responsible if you damage your device, just make sure your bootloader is unlocked and you know how to flash using fastboot.
Is it runs E6853 ?
edit ...
jarnsaxa said:
Is it runs E683 ?
Click to expand...
Click to collapse
Its only for the E6883 dual sim variant..
arjun.arora said:
Its only for the E6883 dual sim variant..
Click to expand...
Click to collapse
Hey man,
I've already put up the kernel for e6883 in the general section in the proper thread no offence
It work on e6833 it is the same kernel??
jarnsaxa said:
Is it runs E6853 ?
edit ...
Click to expand...
Click to collapse
karrouma said:
It work on e6833 it is the same kernel??
Click to expand...
Click to collapse
Well, in theory is should. You can give it a shot. If it doesn't, flash the stock kernel with flashtool to revert back. Don't flash it on single sim variants of the Z5P.
arjun.arora said:
Well, in theory is should. You can give it a shot. If it doesn't, flash the stock kernel with flashtool to revert back. Don't flash it on single sim variants of the Z5P.
Click to expand...
Click to collapse
I flashed it over custom rom RomAUR v4.0.1, on E6833. Unfortunately it says Baseband version Unknown and thus doesn't recognise the sim - plus the brightness slider doesn't function.
slayerz said:
I flashed it over custom rom RomAUR v4.0.1, on E6833. Unfortunately it says Baseband version Unknown and thus doesn't recognise the sim - plus the brightness slider doesn't function.
Click to expand...
Click to collapse
This is for stock firmwares buddy.. RomAur already has a modded kernel..
arjun.arora said:
This is for stock firmwares buddy.. RomAur already has a modded kernel..
Click to expand...
Click to collapse
It work with e6833??
Same kernel
what about E6653 ?
arjun.arora said:
Hey guys, just compiled a rootable kernel for the Z5P (E6883) 6.0.1 dual sim version, FW 224.
Features:
1. Sony RIC is disabled.
2. TWRP recovery - press volume up while booting.
3. Busybox.
4. DRM fix.
Code:
fastboot boot boot.img
fastboot reboot
The first version was having some root permission issues. Flash the new kernel and then flash SuperSU 2.65 via recovery.
Reboot to system and manually install SuperSU 2.74 beta. Update the binary and reboot.
Thanks to tobias.waldvogel for his resources and tutorials.
Please don't flash it on any other device.
I'll not be responsible if you damage your device, just make sure your bootloader is unlocked and you know how to flash using fastboot.
Click to expand...
Click to collapse
Thanks. I'll try it later tonight.. I've had a pretty ****ty time this far with other boots. Nothing has worked with 6.0.1 224 for me, but I'm willing to try.
In sitting on the 6.0 Hong Kong 1.185 atm
Sent from my E6883 using XDA-Developers mobile app
slayerz said:
I flashed it over custom rom RomAUR v4.0.1, on E6833. Unfortunately it says Baseband version Unknown and thus doesn't recognise the sim - plus the brightness slider doesn't function.
Click to expand...
Click to collapse
korom42 said:
what about E6653 ?
Click to expand...
Click to collapse
I don't own a 6653 buddy. Do one thing, please share the kernel.sin of your fw, open the firmware in winrar and extract it.
giz02 said:
Thanks. I'll try it later tonight.. I've had a pretty ****ty time this far with other boots. Nothing has worked with 6.0.1 224 for me, but I'm willing to try.
In sitting on the 6.0 Hong Kong 1.185 atm
Sent from my E6883 using XDA-Developers mobile app
Click to expand...
Click to collapse
FAILED!
Attempt 1:
Procedure -
Flashed Customised MY 32.2.A.0.224
Dropped to fastboot flashed boot and recovery (twrp-3.0.2-0-E6653-20160417.img)
Rebooted.. to system
Couldn't update SU from OS. (Installation Failed)
Tried dropping recovery again so I could load su manually, but no file systems were mountable.
Attempt 2:
Procedure
Flashed Stock Customized IN 32.2.A.0.224
Rebooted to system
Dropped to fastboot
Flashed boot
Rebooted to System
Launched SU, couldn't update from OS (Installation Failed)
Dropped to fastboot
Flashed recovery (twrp-3.0.2-0-E6653-20160417.img)
rebooted to recovery so I could load su manually,
but no file systems were mountable. (Same as attempt 1)
You've wasted my time - NO workable root...
At least Xreality/DRM appears to have worked.
Going back to 6.0
giz02 said:
FAILED!
Attempt 1:
Procedure -
Flashed Customised MY 32.2.A.0.224
Dropped to fastboot flashed boot and recovery (twrp-3.0.2-0-E6653-20160417.img)
Rebooted.. to system
Couldn't update SU from OS. (Installation Failed)
Tried dropping recovery again so I could load su manually, but no file systems were mountable.
Attempt 2:
Procedure
Flashed Stock Customized IN 32.2.A.0.224
Rebooted to system
Dropped to fastboot
Flashed boot
Rebooted to System
Launched SU, couldn't update from OS (Installation Failed)
Dropped to fastboot
Flashed recovery (twrp-3.0.2-0-E6653-20160417.img)
rebooted to recovery so I could load su manually,
but no file systems were mountable. (Same as attempt 1)
You've wasted my time - NO workable root...
At least Xreality/DRM appears to have worked.
Going back to 6.0
Click to expand...
Click to collapse
You don't have to flash recovery after flashing this. It already has TWRP. Read the instructions carefully.
arjun.arora said:
You don't have to flash recovery after flashing this. It already has TWRP. Read the instructions carefully.
Click to expand...
Click to collapse
Bro. Read beyond attempt 1 procedure.. Carefully
I tried su binary upgrade os.. FAILED
Recovery didn't after this attempt .. held vol down after yellow LED but was greeted by flashing red LED, followed by black screen and reboot.
Flashed recover at this point.. permissions trashed.
Couldn't mount any fs..
Failed.
What are you saying anyway, that u can't flash recovery with your kernel?
I regardless, i recommend as a e6883 owner with device in hands to other e6883 owners that this kernel be avoided until fixed .
I'm guessing you guys didn't rebuild from scratch after your ran into your 2.65 su issues. The jump to 2.74 isn't working for me with your kernel fix
giz02 said:
Bro. Read beyond attempt 1 procedure.. Carefully
I tried su binary upgrade os.. FAILED
Recovery didn't after this attempt .. held vol down after yellow LED but was greeted by flashing red LED, followed by black screen and reboot.
Flashed recover at this point.. permissions trashed.
Couldn't mount any fs..
Failed.
What are you saying anyway, that u can't flash recovery with your kernel?
I regardless, i recommend as a e6883 owner with device in hands to other e6883 owners that this kernel be avoided until fixed .
I'm guessing you guys didn't rebuild from scratch after your ran into your 2.65 su issues. The jump to 2.74 isn't working for me with your kernel fix
Click to expand...
Click to collapse
You need to press volume up after flashing the kernel..
Working perfect for me..no issue at all..e6883
Sent from my E6883 using XDA-Developers mobile app
zams85 said:
Working perfect for me..no issue at all..e6883
Sent from my E6883 using XDA-Developers mobile app
Click to expand...
Click to collapse
Great
arjun.arora said:
You need to press volume up after flashing the kernel..
Click to expand...
Click to collapse
Yes..
flash using flashtool.
drop to fastboot (vol up)
flash boot image... reboot
I get into OS, and su tries to update from 265 to 274.. fails in os
reboot to recovery (vol down when yellow led comes on)
try installing su zip from but can't see file system.. can't mount.. busted permissions everywhere
to recover I revert to 6.0
flashtool (using customized HK .185 load)
after flash, drop to fast boot (vol up)
flash older 6883MM bin
flash recovery (3.0.2)
boot to os.
reboot to recovery
install SU (file systems mount without issue).
everything works normally at 6.0 again
---------- Post added at 09:22 AM ---------- Previous post was at 09:18 AM ----------
zams85 said:
Working perfect for me..no issue at all..e6883
Sent from my E6883 using XDA-Developers mobile app
Click to expand...
Click to collapse
When you say "Works perfectly" have you gone into recovery mode and attempted file system mount, OR;
did you flashtool, then flash boot and then use phone?
I'll say that the phone booted to OS fine with this kernel, and I was able to access xreality settings, HOWEVER I was not able to use recovery mode due to numerous permissions errors. (could not mount FS.)
you (ZAM): have you tested recovery mode? specifically mounting fs and and installing zips?
giz02 said:
Yes..
flash using flashtool.
drop to fastboot (vol up)
flash boot image... reboot
I get into OS, and su tries to update from 265 to 274.. fails in os
reboot to recovery (vol down when yellow led comes on)
try installing su zip from but can't see file system.. can't mount.. busted permissions everywhere
to recover I revert to 6.0
flashtool (using customized HK .185 load)
after flash, drop to fast boot (vol up)
flash older 6883MM bin
flash recovery (3.0.2)
boot to os.
reboot to recovery
install SU (file systems mount without issue).
everything works normally at 6.0 again
---------- Post added at 09:22 AM ---------- Previous post was at 09:18 AM ----------
When you say "Works perfectly" have you gone into recovery mode and attempted file system mount, OR;
did you flashtool, then flash boot and then use phone?
I'll say that the phone booted to OS fine with this kernel, and I was able to access xreality settings, HOWEVER I was not able to use recovery mode due to numerous permissions errors. (could not mount FS.)
you (ZAM): have you tested recovery mode? specifically mounting fs and and installing zips?
Click to expand...
Click to collapse
Yep no problem..before this i stay with stock rom..then decide to root and i use this kernel..flash using flashtool and go to recovery for backup stock rom because i want to use custom rom..so no problem with mount or unmount..stock rom backup perfectly..no issue
Sent from my E6883 using XDA-Developers mobile app