I managed to successfully root my Xperia M2 with KitKat 4.4.4 without unlocking the bootloader. Since the procedure is quite generic (and straightforward) I thought it would be useful for people with other Xperia devices if I post it here. Please take it as a guideline, since it may vary slightly between different Xperia devices. I suspect it will work also for the phones that will upgrade to Lollipop (as long as they had a Jelly Bean ROM available), maybe changing the rooting binaries in the rootkitXperia tool.
One can find the full procedure with all steps detailed and links to the SW needed in my original thread for the Xperia M2:
[Q&A][Root]Rooting with Locked Bootloader - NO OTA Method
In order to be able to apply this method the Xperia device must have an older ROM available, vulnerable to the "Towelroot" exploit .
Without it as far as I am aware no rooting is possible in a Kitkat 4.4.4 device with the locked bootloader.
GENERAL GUIDELINES:
Be sure to have the full FTF for the stock ROM you are currently running
Flash with Flashtool only the kernel from a Jelly Bean FTF for your phone unchecking the wipe checkboxes
Reboot the phone:
The phone should bootloop, but it doesn't matter. The Linux kernel and adb are alive and thus the "Towelroot" vulnerability is exploitable by rootkitXperia
Run rootkitXperia. After the rooting it should get stuck when trying to reboot the phone(*). Interrupt it with CTRL-C
Flash back the kernel for the ROM in your phone
Reboot the phone
Manually run the command to have the RIC permanently disabled:
Code:
adb shell "su -c /data/local/tmp/install_tool.sh"
Reboot and enjoy your rooted phone!
(*) In some phones (Xperia Z?) rootkitXperia may not get stuck. If the phone reboots the rooting should be complete. Just flash back your original kernel and it should be done (untested).
Please note that this guideline covers some already known rooting methods. The difference is that it also covers the cases when the ROM bootloops and/or rootkitXperia gets stuck at the reboot, making it quite generic for all Xperia devices. It doesn't pretend to be a new guide for all Xperia, just a general one.
Xperia Phones confirmed working:
if you manage to root the phone using the kernel of a similar Xperia (like in the case of the Xperia M2 Aqua below) please report the phone name/model of your phone and of the phone you used the kernel from.
Xperia M2 D2303
Xperia M2 Aqua D2403 - With the M2 D2303 kernel
(to be expanded)
That's the well known method we are using since Xperia U.
As long as you have older fw (JB) you'll be able to root your device.
But...
I wouldn't bet on rooting L with this method.
Lollipop is new, fresh written firmware with a new kernel.
Code was updated on JB and new features were added when Google built KK...
L is something totally different...but we'll see soon..
Miche1asso said:
I managed to successfully..
Click to expand...
Click to collapse
Any help for Xperia E3 with lock bootloader..
funky0308 said:
That's the well known method we are using since Xperia U.
As long as you have older fw (JB) you'll be able to root your device.
.
Click to expand...
Click to collapse
I don't know if it was used already on Xperia U. I checked all around and I couldn't find this particular solution where the rooting is done with the hone bootlooping and one of rootkitXperia scripts must be run manually after restoring the KK kernel.
Particularly on Xperia M2 the suggested solution was to downgrade both kernel and system, root it and then upgrade via OTA. Which was something I didn't fancy at all. Still now I see people trying to apply rootkitXperia on any Xperia KK 4.4.4 (which will never work, as I discovered myself). So I made it available in the general section as well for people with less popular Xperias who are banging their heads like I did for a couple of weeks (honest):
But sure, the downgrade is a requirement. At the moment 4.4.4 seems unbreakable.
.
But...
I wouldn't bet on rooting L with this method.
Lollipop is new, fresh written firmware with a new kernel.
Code was updated on JB and new features were added when Google built KK...
L is something totally different...but we'll see soon..
Click to expand...
Click to collapse
It's still Linux. With the bleeding SELinux fully enabled, though. It may take some tampering, but I suspect it will be a matter of replacing/adding the rooting binaries in rootkitXperia. Chainfire already has them available I understood. If it will be possible to inject them flashing the JB kernel half of the job has done. Still, I'll rephrase it in my first post, it could be be too optimistic.
imElectronica said:
Any help for Xperia E3 with lock bootloader..
Click to expand...
Click to collapse
Since it came with 4.4.4 and the HW is similar to the one of the M2 (same CPU at least) you may try this method flashing the M2 kernel attached in my first thread. In case it goes all wrong you should be able to flash back the original kernel. At least so I've read people "unbricked" their phones after fashing a wrong kernel.
But I am not sure about it. I take no responsibility. Do it at your own risk
I thought that ADB wouldn't work if the phone didn't boot completely or at least it didn't go past booting the kernel. That's quite a suprise for me and I'll surely test it on the next xperia I'd have to root. You just made my concerns about rooting 5.0 Sony firmwares on LB gone, thanks a ton mate!
BTW. That's literally the fastest written news I ever seen on the xda portal, like seriously, it was posted the very same day, just a few minutes ago.
olokos said:
I thought that ADB wouldn't work if the phone didn't boot completely or at least it didn't go past booting the kernel. That's quite a suprise for me and I'll surely test it on the next xperia I'd have to root. You just made my concerns about rooting 5.0 Sony firmwares on LB gone, thanks a ton mate!
Click to expand...
Click to collapse
You're very welcome!
BTW. That's literally the fastest written news I ever seen on the xda portal, like seriously, it was posted the very same day, just a few minutes ago.
Click to expand...
Click to collapse
Why, did I make the portal? Oh, i see it now. In the bottom right section. That's cool! Now I am happy. Thanks.
Does this mean I can root my Xperia Z3 d6616 on 4.4.4? You may have just won all the internets.
Known method and it works. I used it on the Xperia NovaThor line
Also you can add this. If your phone is working weird (buggy or sudden battery drops) just wipe the cache. It is known problem when flashing older version of android (ROM/kernel) and then flashing back the new one. In this case you are doing exactly that. Right now there are no recoveries for locked bootloader but you can use the ADB command or some terminal application on your android.
Option 1. Using the ADB (easiest):
Code:
adb shell
su
cd /data/dalvik-cache
rm *
exit
adb reboot
Option 2. Using terminal
Code:
su
cd /data/dalvik-cache
rm *
exit
After that reboot your device. It will take longer than normal but it's ok
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
HORiZUN said:
Does this mean I can root my Xperia Z3 d6616 on 4.4.4? You may have just won all the internets.
Click to expand...
Click to collapse
No because Z3 doesn't have a jellybean ROM/kernel so you can't use this on your device
Similar method when rooting Xperia Tablet Z and a bit similar when rooting my Xperia neo V before.. I don't encountered boot loop....
DavidMKD said:
Known method and it works. I used it on the Xperia NovaThor line
Also you can add this. If your phone is working weird (buggy or sudden battery drops) just wipe the cache. It is known problem when flashing older version of android (ROM/kernel) and then flashing back the new one. In this case you are doing exactly that.
Click to expand...
Click to collapse
I think the dalvik caches get modified when a new /system (with a different version of the apps in /system/app) gets installed.. Just changing the kernel shouldn't really affect the dalvik caches.
Right now there are no recoveries for locked bootloader but you can use the ADB command or some terminal application on your android.
Option 1. Using the ADB (easiest):
[...]
Option 2. Using terminal
[...]
After that reboot your device. It will take longer than normal but it's ok
Click to expand...
Click to collapse
or you can just type from the terminal:
Code:
adb shell su -c "rm -r /data/dalvik-cache; reboot"
Otherwise what I usually do is to remove the /data/dalvik-cache folder from a root file manager. /data/dalvik.-cache gets re-created at boot time. Not that I've ever really seen any benefit on doing that. Especially in Kitkat any time the system apps get modified Android should rebuild all of them at boot time. But yeah, one never knows. Hopefully ART in Lollipop will end this crap.
donedos said:
Similar method when rooting Xperia Tablet Z and a bit similar when rooting my Xperia neo V before.. I don't encountered boot loop....
Click to expand...
Click to collapse
Yeah, I know. The guide is more specific for when the ROM bootloops and/or rootkitXperia gets stuck at the reboot, like it happens in the Xperia M2. In that case people where getting stuck, or at least I couldn't find any guide telling what to do. I'll specify it in the main post.
Delete
tRippinthehead said:
Delete
Click to expand...
Click to collapse
Sorry to ask in here but its impossible to get a reply in the Z2 Tablet forum. Any idea where I can download a Jellybean FTF for my device and then the 4.4.4 FTF its running atm?
Would be greatly appreciated!
Dowloading the FTF from: http://xperiafirmware.com/8-firmware/50-sony-xperia-z2-tablet-wi-fi-sgp511, anyone know if SGP511 is compatible with SGP512 (I know they're both WiFi international versions)
I found this: http://forum.xda-developers.com/showthread.php?t=2768951 But its only a 7mb download? Is the system.img the kernal?
GalaxyWhy said:
Sorry to ask in here but its impossible to get a reply in the Z2 Tablet forum. Any idea where I can download a Jellybean FTF for my device and then the 4.4.4 FTF its running atm?
Would be greatly appreciated!
Dowloading the FTF from: http://xperiafirmware.com/8-firmware/50-sony-xperia-z2-tablet-wi-fi-sgp511, anyone know if SGP511 is compatible with SGP512 (I know they're both WiFi international versions)
I found this: http://forum.xda-developers.com/showthread.php?t=2768951 But its only a 7mb download? Is the system.img the kernal?
Click to expand...
Click to collapse
First of all, use XperiFirm (google it) and download the program. Find your device and download the necessary firmwares. The second link you posted is just a kernel
What about phones without JB roms released, ex: Xperia C3? It was released on KK 4.4.1 and I think that no kernels are available for this phone. I'm asking 'cause I want to root my phone but is almost impossible using all known methods .
Dominator_666 said:
What about phones without JB roms released, ex: Xperia C3? It was released on KK 4.4.1 and I think that no kernels are available for this phone. I'm asking 'cause I want to root my phone but is almost impossible using all known methods .
Click to expand...
Click to collapse
Ok, this is the situation: if the phone has a "brother" with the same identical SoC which came with a JB ROM flashing the kernel (and only the kernel) from the JB FTF of that ROM may do the job. It officially worked on the Xperia M2 Aqua D2403 using the D2303 kernel. As long as the phone manages to boot the kernel and abd is alive (with all relevant Unix commands) the rooting should be possible (and the phone won't be bricked at all. It just has the kernel not matching the modules, libraries and else in the ROM).
This may apply for example to the Sony Z3 using the Z2 JB kernel for the rooting (although the SoC in this case are slightly different). Or the Xperia E3 using the M2 kernel. But no one tested these scenarios yet, so I take no responsibility if anything goes wrong. It is at your own risk.
Still, my experience with the Samsung has been that after flashing the wrong kernel was always possible to recover the phone flashing back the official ROM (with Odin in that case). I have no experience of "soft bricked" phones with the Xperia, so I can't bring my personal experience on this.
Miche1asso said:
Ok, this is the situation: if the phone has a "brother" with the same identical SoC which came with a JB ROM flashing the kernel (and only the kernel) from the JB FTF of that ROM may do the job. It officially worked on the Xperia M2 Aqua D2403 using the D2303 kernel. As long as the phone manages to boot the kernel and abd is alive (with all relevant Unix commands) the rooting should be possible (and the phone won't be bricked at all. It just has the kernel not matching the modules, libraries and else in the ROM).
This may apply for example to the Sony Z3 using the Z2 JB kernel for the rooting (although the SoC in this case are slightly different). Or the Xperia E3 using the M2 kernel. But no one tested these scenarios yet, so I take no responsibility if anything goes wrong. It is at your own risk.
Still, my experience with the Samsung has been that after flashing the wrong kernel was always possible to recover the phone flashing back the official ROM (with Odin in that case). I have no experience of "soft bricked" phones with the Xperia, so I can't bring my personal experience on this.
Click to expand...
Click to collapse
Anyone willing to try this? Maybe we can set up a donation thread for someone to try it?
Dominator_666 said:
What about phones without JB roms released, ex: Xperia C3? It was released on KK 4.4.1 and I think that no kernels are available for this phone. I'm asking 'cause I want to root my phone but is almost impossible using all known methods .
Click to expand...
Click to collapse
It's not about Jelly Bean firmware availability for the device. Towel root even works directly with KitKat, provided the kernel build date should be before 3rd June, 2014.
Mmm i tried many times with towelroot but isn't working. However as you said is better to have a non rooted device than a hard bricked one hahaha
Moist said:
Anyone willing to try this? Maybe we can set up a donation thread for someone to try it?
Click to expand...
Click to collapse
Don't ever flash wrong kernels which isn't meant for your device. It might hard brick. 'No root' is better than 'hard brick'ed device.
Related
Hi,
Some of you may recognise my name from around the forums, especially if you have had an Xperia device before. I started my first android developments on the Xperia Play and then continued onto the Xperia U. I then lost mass interest in development due to joining college and being overloaded with work due to a computing course. I was no longer able to contribute to any developments.
Now, I am in the second year of college and have dropped a subject I am finding myself with more free time so I have decided to start developing again, only this time I have an Xperia SP.
There's only one catch, the device I have is network locked to O2 and therefore I cannot unlock my boot loader, so most if not all of my work will be for those with a locked bootloader. I am mostly interested in creating custom ROMs based on stock and also creating my own applications and embedding them into the stock ROM.
And the flashy bar at the bottom, yeah I have ideas for that.
Developments for Xperia SP:
illumination app
~Keiran
Sent from my C5303 using Tapatalk
Thank you!
Sent from my C5303 using XDA Premium 4 mobile app
Thank you!
Thank you guy!
You have locked bootloader and you don't use fastboot
You should sell branded phone and buy no-branded
MrZender said:
Thank you guy!
You have locked bootloader and you don't use fastboot
You should sell branded phone and buy no-branded
Click to expand...
Click to collapse
I can't, it just means that I will only be able to developed for locked bootloader which is no problem really. All it means is that I cannot change the kernel image, using scripts I can mess about with the ramdisk though and may be able to boot CM on a locked boot loader if the stock kernel allows it.
Sent from my C5303 using Tapatalk
Glad to see you back in the game mate ! Too bad that you can't unlock your bootloader. Although I know that would not be a problem for you.
Sent from my C5303 using Tapatalk
Hi @KeiranFTW welcome to Xperia SP development!
I hope we can work together on a project I want to try when we get the Android 4.3 update, I'm not sure if it will be successful and I'm not sure if anyone else tried this on other devices, but I want to try.
Basically I want to build Android 4.3 that works with the stock Sony 4.3 bootloader. I already have my fork of CodeAurora up and running here, I call it recaf, it will 'simply' be a matter of satisfying the extra dependencies and other Sony changes.
Come chat on freenode IRC, I'm in #freexperia, or on my own at #recaf. (If I don't reply immediately it mean's I'm afk, but my irc bouncer keeps me logged in.)
adfad666 said:
Hi @KeiranFTW welcome to Xperia SP development!
I hope we can work together on a project I want to try when we get the Android 4.3 update, I'm not sure if it will be successful and I'm not sure if anyone else tried this on other devices, but I want to try.
Basically I want to build Android 4.3 that works with the stock Sony 4.3 bootloader. I already have my fork of CodeAurora up and running here, I call it recaf, it will 'simply' be a matter of satisfying the extra dependencies and other Sony changes.
Come chat on freenode IRC, I'm in #freexperia, or on my own at #recaf. (If I don't reply immediately it mean's I'm afk, but my irc bouncer keeps me logged in.)
Click to expand...
Click to collapse
I'm sure it is very possible, as there is a way that could work really, I could probably set it up as a dual boot. You would need the AOSP ramdisk in tar format somewhere on your phone and at boot time if you wish to boot AOSP then it would delete everything at / and extract that ramdisk to / and then continue boot process with that ramdisk.. as long as stock kernel is compatible.
Sent from my C5303 using Tapatalk
Welcome in SP section
Happy to see more real dev here
Well, maybe you could port kexec to our locked SP's? The main part of the module and binary is done, there is only one thing left - implementing proper hardboot and finally porting to our phones. I think some Xperia SP devs might help you. There's a thread in Z1 forums where delewer tries to get last parts of the job done. If you decide to start working on it, I want to be a alpha or beta tester
http://forum.xda-developers.com/showthread.php?t=2495152
Welcome mate, glad you are here can't wait to see your work I also had an xperia play and I'm pretty sure I had a few of your roms and mods installed at some point.
Sent from my C5303 using XDA Premium HD app
I have a few projects in mind at the moment:
1. Getting the 4.3 leak to boot on locked bootloader
2. When 4.3 is released get AOSP 4.3 to run also on locked boot loader - I will be working with @adfad666 on this - most priority
3. Maybe a stock based custom ROM - least priority.
Sent from my C5303 using Tapatalk
Maybe after booting AOSP 4.3 on locked BL you could try booting 4.4? Because it was possible in Xperia X8 "age of glory"(some devs booted 2.2 on 2.1 kernel if I'm not mistaken).
MrSteve555 said:
Maybe after booting AOSP 4.3 on locked BL you could try booting 4.4? Because it was possible in Xperia X8 "age of glory"(some devs booted 2.2 on 2.1 kernel if I'm not mistaken).
Click to expand...
Click to collapse
We could try.
The way I'm going to do it is hijack pre_hw_config.sh and then launch a script from there to determine whether to extract recovery ramdisk or AOSP ramdisk, then this will be extracted to /, and then everything will be unmounted and init will be started again to restart the boot process.
Sent from my C5303 using Tapatalk
I think I'll try to boot 4.3 today, with the method described in this thread: http://forum.xda-developers.com/showthread.php?t=2593806
I'll post my results later.
KeiranFTW said:
We could try.
The way I'm going to do it is hijack pre_hw_config.sh and then launch a script from there to determine whether to extract recovery ramdisk or AOSP ramdisk, then this will be extracted to /, and then everything will be unmounted and init will be started again to restart the boot process.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Unfortunately pre_hw_config.sh doesn't exist in the 4.3 leak, so assuming that doesn't change when we receive the official update, we won't be able to use that.
adfad666 said:
Unfortunately pre_hw_config.sh doesn't exist in the 4.3 leak, so assuming that doesn't change when we receive the official update, we won't be able to use that.
Click to expand...
Click to collapse
then /system/bin/charger
Sent from my C5303 using Tapatalk
Well, pre_hw_config.sh doesn't exist even in stock 4.1.2. I think we should try with chargemon, not charger(because it's executed earlier). I tried booting DooMLord's DoomKernel ramdisk on stock kernel. Absolutely no luck. I don't even know what's wrong - after loading ramdisk, kernel panic occurs. Maybe someone more clever will figure it out.:silly:
I think I'm nearly there at hijacking the boot process to inject new ramdisk, I just have a little test that I will have to do later as I need to go out now.
What I'm going to do is use the same ramdisk as that's in the kernel but inject it again after removing anything, this way I don't need to change my ROM and I know that I can inject a new ramdisk. I'll upload my work to github later too so people can contribute
~Keiran
Sent from my C5303 using Tapatalk
Okay, so I've been successful in booting a custom RAMdisk, only problem I am experiencing is that the data partition is not being remounted when the new ramdisk is loaded, no idea why though.
Okay, done and fixed, sources are at https://github.com/keiranFTW/hijack-ramdisk-huashan
Get ready for exciting things coming now
KeiranFTW said:
Okay, so I've been successful in booting a custom RAMdisk, only problem I am experiencing is that the data partition is not being remounted when the new ramdisk is loaded, no idea why though.
Okay, done and fixed, sources are at https://github.com/keiranFTW/hijack-ramdisk-huashan
Get ready for exciting things coming now
Click to expand...
Click to collapse
I tried your method, but it has one bug - it doesn't symlink /data/media to /storage/sdcard0, so the data from internal memory isn't accesible through that path. Still amazing work, but I suggest you to change the format of ramdisk read by the script to .cpio, because it's easier to get from kernels. :good:
Hello everyone,
After seeing the high amount of people that still use this device...
I realized how much it was still in developpement.
This website still exist http://rootgalaxynote.com/
Android 4.4.4 is up-to-date on it
The ease of use, the facility of installing a custom rom, custom recovery, overclocking, etc...
Guys, don't change your device, keep it, protect it, mine has a broken screen... I got the lazyness to repair it because I already failed before to replace a scratched one, I even replaced the micro usb port and ordered a new usb cable, now I have an xperia z ultra, it's awesome, but the developpers sucks to explain how to and nobody helps me, I want AOKP, never used it on my note, I was all the time on the CM 10.2 RC 1030
DIGITALIZOR said:
Hello everyone,
After seeing the high amount of people that still use this device...
I realized how much it was still in developpement.
This website still exist http://rootgalaxynote.com/
Android 4.4.4 is up-to-date on it
The ease of use, the facility of installing a custom rom, custom recovery, overclocking, etc...
Guys, don't change your device, keep it, protect it, mine has a broken screen... I got the lazyness to repair it because I already failed before to replace a scratched one, I even replaced the micro usb port and ordered a new usb cable, now I have an xperia z ultra, it's awesome, but the developpers sucks to explain how to and nobody helps me, I want AOKP, never used it on my note, I was all the time on the CM 10.2 RC 1030
Click to expand...
Click to collapse
It certainly looks more complicated, yes. Have you seen this thread for the Xperia? http://forum.xda-developers.com/showthread.php?t=2569904
Zhuinden said:
It certainly looks more complicated, yes. Have you seen this thread for the Xperia? http://forum.xda-developers.com/showthread.php?t=2569904
Click to expand...
Click to collapse
That's what I was looking for and couldn't find out
Thank you dude
I have nearly bricked my device today when I tried to install twrp by flashtool...
DIGITALIZOR said:
That's what I was looking for and couldn't find out
Thank you dude
I have nearly bricked my device today when I tried to install twrp by flashtool...
Click to expand...
Click to collapse
You are welcome
There is a gigantic warning that tells you to back up the TA partition, so make sure you look into http://forum.xda-developers.com/showthread.php?t=2428590 first
edit: I've just noticed the last two posts in that thread are yours asking for help, disregard that I guess
Zhuinden said:
You are welcome
There is a gigantic warning that tells you to back up the TA partition, so make sure you look into http://forum.xda-developers.com/showthread.php?t=2428590 first
Click to expand...
Click to collapse
Thanks, I have already backed up my TA Partition (DRM Keys for x-reality bravia engine)
I have rooted my device before, and, updated the SuperSU binary.
And... I tried to flash a recovery 108_DualRec_Jackie099.img via flashtool but my phone couldn't boot.
Then the device was still on flashmod or fast boot, can't remember and I flashed the latest rom on it.
I have huge difficulties to install a recovery on it.
I even tried this http://forum.xda-developers.com/showthread.php?t=2647492 and it didn't worked at all...
Dude, I have created a thread here where I ask for help http://forum.xda-developers.com/xperia-z-ultra/help/seek-thread-complete-explanations-t2816189
if you know someone that understands the working process of any xperia phones I hope that someone would explain there something
Because every tutorial writes, flash boot.img on your phone, (and, I'm here... okay... with what ? wich option to choose on flashtool, wich mode to put on my phone ? fast boot or flashmode etc etc...)
DIGITALIZOR said:
Thanks, I have already backed up my TA Partition (DRM Keys for x-reality bravia engine)
I have rooted my device before, and, updated the SuperSU binary.
And... I tried to flash a recovery 108_DualRec_Jackie099.img via flashtool but my phone couldn't boot.
Then the device was still on flashmod or fast boot, can't remember and I flashed the latest rom on it.
I have huge difficulties to install a recovery on it.
I even tried this http://forum.xda-developers.com/showthread.php?t=2647492 and it didn't worked at all...
Dude, I have created a thread here where I ask for help http://forum.xda-developers.com/xperia-z-ultra/help/seek-thread-complete-explanations-t2816189
if you know someone that understands the working process of any xperia phones I hope that someone would explain there something
Because every tutorial writes, flash boot.img on your phone, (and, I'm here... okay... with what ? wich option to choose on flashtool, wich mode to put on my phone ? fast boot or flashmode etc etc...)
Click to expand...
Click to collapse
Unfortunately I do not know anyone with modded Xperia Z Ultra
However based on searches it seems to me that what you must do is unlock the bootloader then use this kernel http://forum.xda-developers.com/showthread.php?t=2426736 for the CWM needed for other custom ROMs
I saw some other threads too but this one seems to be most stable based on what I found
Zhuinden said:
Unfortunately I do not know anyone with modded Xperia Z Ultra
However based on searches it seems to me that what you must do is unlock the bootloader then use this kernel http://forum.xda-developers.com/showthread.php?t=2426736 for the CWM needed for other custom ROMs
I saw some other threads too but this one seems to be most stable based on what I found
Click to expand...
Click to collapse
Thanks again, but, in fact, there's a lot of versions of the firmware, for example,
I have the 14.4.A.0.108
the .108 is compatible with some of their kernels/recoveries
and the post that you gave me is old of
Old 30th August 2013, 11:21 PM (Last edited by krabappel2548; 11th September 2013 at 12:42 PM.)
Click to expand...
Click to collapse
in fact, I have to be updated for each recovery, or be downgraded, before installing any ROMs, I have to have a fully functional Recovery, but none of them works with my .108
gonna need to downgrade later...
DIGITALIZOR said:
Thanks again, but, in fact, there's a lot of versions of the firmware, for example,
I have the 14.4.A.0.108
the .108 is compatible with some of their kernels/recoveries
and the post that you gave me is old of
in fact, I have to be updated for each recovery, or be downgraded, before installing any ROMs, I have to have a fully functional Recovery, but none of them works with my .108
gonna need to downgrade later...
Click to expand...
Click to collapse
The main goal is to install a kernel with custom recovery of twrp or cwm. I was doing my best to search, but I couldn't really find anything newer. Right now I am from phone so I cannot really look into it further, I will later I think. I admit, having a download mode and stuff certainly makes the G note much more user friendly in this aspect.
Zhuinden said:
The main goal is to install a kernel with custom recovery of twrp or cwm. I was doing my best to search, but I couldn't really find anything newer. Right now I am from phone so I cannot really look into it further, I will later I think. I admit, having a download mode and stuff certainly makes the G note much more user friendly in this aspect.
Click to expand...
Click to collapse
yeah buddy... you see... try to buy him a new genuine battery... an expensive cover flip... keep it dude... there's a lot of updates for him
DIGITALIZOR said:
Hello everyone,
After seeing the high amount of people that still use this device...
I realized how much it was still in developpement.
This website still exist http://rootgalaxynote.com/
Android 4.4.4 is up-to-date on it
The ease of use, the facility of installing a custom rom, custom recovery, overclocking, etc...
Guys, don't change your device, keep it, protect it, mine has a broken screen... I got the lazyness to repair it because I already failed before to replace a scratched one, I even replaced the micro usb port and ordered a new usb cable, now I have an xperia z ultra, it's awesome, but the developpers sucks to explain how to and nobody helps me, I want AOKP, never used it on my note, I was all the time on the CM 10.2 RC 1030
Click to expand...
Click to collapse
Yeah back to this device once again
And i'm trying to make it SUPER, but don't know what to do :laugh:
I'm trying to MOD it with AryaMod :victory:
This sure is :fingers-crossed:
I dont want it to die but our Note is getting old
thnaks bro..will check the website soon
DIGITALIZOR said:
Hello everyone,
After seeing the high amount of people that still use this device...
I realized how much it was still in developpement.
This website still exist http://rootgalaxynote.com/
Android 4.4.4 is up-to-date on it
The ease of use, the facility of installing a custom rom, custom recovery, overclocking, etc...
Guys, don't change your device, keep it, protect it, mine has a broken screen... I got the lazyness to repair it because I already failed before to replace a scratched one, I even replaced the micro usb port and ordered a new usb cable, now I have an xperia z ultra, it's awesome, but the developpers sucks to explain how to and nobody helps me, I want AOKP, never used it on my note, I was all the time on the CM 10.2 RC 1030
Click to expand...
Click to collapse
Dirty Unicorns v7.8 n7000
Speaking of 4.4.4, I made a video of Dirty Unicorns v7.8 n7000.
Dirty Unicorns v7.8 for galaxy note GT-N7000: http://youtu.be/fzq8vkHX-MM
qmscreatives said:
thnaks bro..will check the website soon
Click to expand...
Click to collapse
yeah... but that was just to share my feelings about our device... it's still alive and in developpement since so much years...
even the first galaxy S is in developpement
i have checked the website. the website is really good. thanks for sharing.
This phone is for sure a legend just like the S2.
Enjoying RR Remix on this device
Sent through my Galaxy Note using Tapatalk 4
At the moment there seem to be problems to compile new cm nightly updates. No update since 08.13.2014
Only changelogs that get longer every day. Anybody knows the reason?
gesendet mit Tapatalk
help me!
Plz. Whatsapp me (+917845145751).Plz. Hi guys. I'm noob XD. Plz teach me how to install cwm (latest) to install a custom Rom. Plz.
As even the Z have the 4.4.4 Android,i think Sony is shaming their prev. "Flagship" phone , with all the deffects, gaps,uncetered camera ,etc. Now even models 1 year older then ours has the new update, incl Z1 , z1 compact, and the tablets...i am more and more dissapointed from that phone each day, changed it 2 times cos of deffects..now somebody will say its because of my problems with the deffects i am crying like a MOD EDIT Please do not swear. But guys come on, all the prevoius models got it allready and we even dont hear rumors about it..
Sent from my D6503 using XDA Premium 4 mobile app
Which features of 4.4 are you desperate for? I'd rather that any updates where done well rather than rushed just so we can have it. As for the defects, gaps don't matter as long as device integrity is maintained I haven't seen anyone suggesting they are affecting this? Uncentered camera again as long as it doesn’t affect function I couldn't care less.
I'll go out on a limb here and say maybe Sony's just waiting for Android 5 to update?
ice_lander said:
As even the Z have the 4.4.4 Android,i think Sony is shaming their prev. "Flagship" phone , with all the deffects, gaps,uncetered camera ,etc. Now even models 1 year older then ours has the new update, incl Z1 , z1 compact, and the tablets...i am more and more dissapointed from that phone each day, changed it 2 times cos of deffects..now somebody will say its because of my problems with the deffects i am crying like a *****. But guys come on, all the prevoius models got it allready and we even dont hear rumors about it..
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
They most probably plan to update the z2 to the same 4.4.4 software on the recently unveiled z3 army. That's why it's later than the 4.4.4 software released for older devices. They wanted to showcase it with the z3. Hopefully it'll hit the z2 soon.
That would be bad news for Z1 and z1 compact users because the software on the z3 has improvements for the camera.
Sent from my D6503 using XDA Free mobile app
Hope they improve ours also
Sent from my D6503 using XDA Premium 4 mobile app
zodiac100 said:
They most probably plan to update the z2 to the same 4.4.4 software on the recently unveiled z3 army. That's why it's later than the 4.4.4 software released for older devices. They wanted to showcase it with the z3. Hopefully it'll hit the z2 soon.
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
I hope so .... :angel:
I hope that Sony will add hi-res audio playback for z2 in 4.4.4
Be Calm. 4.4.4 might bring some stuffs from the Z3.
stanley08 said:
Be Calm. 4.4.4 might bring some stuffs from the Z3.
Click to expand...
Click to collapse
Just like it brought from Z2 to Z1
I really doubt that'll happen, at least not officially.
Ported apps, camera apps and, probably, features will be soon here.
As soon as we get system dump XDA community (Xperia community) will start working and porting apps and features.
- Maybe someone already uploaded system dump -
Sent from my D6503 using Tapatalk
funky0308 said:
Just like it brought from Z2 to Z1
I really doubt that'll happen, at least not officially.
Ported apps, camera apps and, probably, features will be soon here.
As soon as we get system dump XDA community (Xperia community) will start working and porting apps and features.
- Maybe someone already uploaded system dump -
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Yep! System Dumps already uploaded and some apps working on the Z2 already... I'm rocking the new home and messaging app (conversations.apk). See attachment below.
stanley08 said:
Yep! System Dumps already uploaded and some apps working on the Z2 already... I'm rocking the new home and messaging app (conversations.apk). See attachment below.
Click to expand...
Click to collapse
Can we just install the apks from the system dump? Thanks
Sent from my D6503 using XDA Free mobile app
No actually, but here is a thread containing a flashable zip - http://forum.xda-developers.com/crossdevice-dev/sony/mod-one-xperia-z3-apps-v1-t2867992
stanley08 said:
No actually, but here is a thread containing a flashable zip - http://forum.xda-developers.com/crossdevice-dev/sony/mod-one-xperia-z3-apps-v1-t2867992
Click to expand...
Click to collapse
But is there something for us who have only root and stock rom?
[kEkA] said:
But is there something for us who have only root and stock rom?
Click to expand...
Click to collapse
All I can say is... Sit tight. As long as you don't have an iPhone, you will be fine. This is Android BABY!
[kEkA] said:
But is there something for us who have only root and stock rom?
Click to expand...
Click to collapse
There will be but don't expect to much.
Deodex your firmware and install superuser MOD.
That's two mins task and you won't even notice you deodex it...
What you'll see is great new MODs and APPs.
On older device there were "problems" when you were deodexing firmware.
Simply, without dex files for system to cache process, many devices become slower after deodexing.
All that doesn't apply on devices strong like Z1/Z2/Z3.
So there's no reason for you not to deodex your firmware.
Especially if you are already rooted...
Why to stop there?
Sent from my D6503 using Tapatalk
stanley08 said:
All I can say is... Sit tight. As long as you don't have an iPhone, you will be fine. This is Android BABY!
Click to expand...
Click to collapse
That's all I can do
funky0308 said:
There will be but don't expect to much.
Deodex your firmware and install superuser MOD.
That's two mins task and you won't even notice you deodex it...
What you'll see is great new MODs and APPs.
On older device there were "problems" when you were deodexing firmware.
Simply, without dex files for system to cache process, many devices become slower after deodexing.
All that doesn't apply on devices strong like Z1/Z2/Z3.
So there's no reason for you not to deodex your firmware.
Especially if you are already rooted...
Why to stop there?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
You're right, there is no, but I was happy with stock rom, only rooted cause its 10 secs job and to install some stuff that needs root,
I'm not very good when it comes to android, especially when it comes to deodexing and odexing. I know what's what, but there's lots of questions, for example which recovery should I use, can I delete recovery later on if I plan on selling it in favor to z3, and I suppose once I get deodex rom, ota updates are out of the question, right?
[kEkA] said:
That's all I can do
You're right, there is no, but I was happy with stock rom, only rooted cause its 10 secs job and to install some stuff that needs root,
I'm not very good when it comes to android, especially when it comes to deodexing and odexing. I know what's what, but there's lots of questions, for example which recovery should I use, can I delete recovery later on if I plan on selling it in favor to z3, and I suppose once I get deodex rom, ota updates are out of the question, right?
Click to expand...
Click to collapse
Once you root device you can forget on OTA (at least on stock, existenz have its own OTA).
It's very simple to deodex ROM.
Just check which firmware are you using.
Download deodex patch for that firmware and flash it from recovery.
Your data will stay intact and nothing will change (of course, don't wipe data from recovery after or before flashing deodex patch, cache and dalvik wipe is what you need to do after flashing.
You can remove recovery, root and restore dex files, that's not problem.
Simply flash stock ftf using flashtool or if you have problems with your device flash stock firmware using PC Companion (repair function) and everything will be "stock"
After that, take your sdCard out of device and delete XZDR folder and files (there's remover, tool from NUT, to remove recovery but you can do that this way as well)
If your carrier will check your device for warranty purpose, they could reject your device because it's rooted as well so deodexing isn't something that could make more problems.
It's up to you but there's only one way to use, system (signed), Z3 apps and/or apps from other devices.
- Superuser MOD on deodexed and rooted device -
Sent from my D6503 using Tapatalk
funky0308 said:
Once you root device you can forget on OTA (at least on stock, existenz have its own OTA).
It's very simple to deodex ROM.
Just check which firmware are you using.
Download deodex patch for that firmware and flash it from recovery.
Your data will stay intact and nothing will change (of course, don't wipe data from recovery after or before flashing deodex patch, cache and dalvik wipe is what you need to do after flashing.
You can remove recovery, root and restore dex files, that's not problem.
Simply flash stock ftf using flashtool or if you have problems with your device flash stock firmware using PC Companion (repair function) and everything will be "stock"
After that, take your sdCard out of device and delete XZDR folder and files (there's remover, tool from NUT, to remove recovery but you can do that this way as well)
If your carrier will check your device for warranty purpose, they could reject your device because it's rooted as well so deodexing isn't something that could make more problems.
It's up to you but there's only one way to use, system (signed), Z3 apps and/or apps from other devices.
- Superuser MOD on deodexed and rooted device -
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Thank you very much mate, I forgot that I can have recovery even if I have locked bootloader, its uncommon for me since I've never have had Sony device before, I guess it's easy later to restore everything later if I need to claim warranty, but just one thing,
few days ago I did software repair via PC companion, after that I had root BUT w/o permission to write, just to read system files, how's that possible?
Thanks again for the big answer,
regards mate!
I'd prefer getting Android 5, rather than getting 4.4.4 update for my Z2. So, if I'm waiting to get Android 5, it's all good.
[kEkA] said:
Thank you very much mate, I forgot that I can have recovery even if I have locked bootloader, its uncommon for me since I've never have had Sony device before, I guess it's easy later to restore everything later if I need to claim warranty, but just one thing,
few days ago I did software repair via PC companion, after that I had root BUT w/o permission to write, just to read system files, how's that possible?
Thanks again for the big answer,
regards mate!
Click to expand...
Click to collapse
Hmm...that shouldn't be the case after you root device.
Did you updated supersu binaries?
Download this and flash through recovery
https://app.box.com/s/knwvu1jfzs1vec9n6vr0
That will update supersu binaries.
Then try...
Sure, no problem, I'm glad if I helped..
Sent from my D6503 using Tapatalk
This thread is for the development for a Moto X(2013) port for Android Lollipop.
http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
2nd test build in the works
Everyone who wants to test builds needs to add [email protected] to hangouts
WARNING! tests builds,if they work, will be very unstable. Please remember to backup your system before flashing
In order to flash your phone must
-Have an Unlocked bootloader
- TWRP Recovery installed
If you meet those requirements then add him to hangouts and join the development process
Android 5.0 will come to the 2013 Moto X before the end of november , if not early december, so the amount of work that i believe is required, i dont really think its worth it.
^^^^^agreed. This has already been discussed in the GENERAL section. Mods should move this to general. No development here.
---------- Post added at 05:39 AM ---------- Previous post was at 05:37 AM ----------
And after putting android L on my N7 all locked devices will not have root anymore or safestrap. Currently only way to root is with a custom rooted kernel.
Does TWRP still work with 5.0? What about SuperSU?
lowvolt1 said:
Does TWRP still work with 5.0? What about SuperSU?
Click to expand...
Click to collapse
TWRP still works with L. However only way at this time to get root is with a custom rooted kernel by chainfire. Which means root and safestrap will be dead on L if you are on a locked bootloader.
Ha! I'm unlocked. So Flashing TWRP and installing SuperSU the traditional way no longer works? Am I understanding?
lowvolt1 said:
Ha! I'm unlocked. So Flashing TWRP and installing SuperSU the traditional way no longer works? Am I understanding?
Click to expand...
Click to collapse
Correct, now to root you will need to flash a rooted kernel.
Any word on xposed and L?
Xposed use davilk not art. So with Android Like you can't use xposed mod
Porting is difficult ..why dont u build aosp 5.0 from source using cm device tree ?
Travisdroidx2 said:
TWRP still works with L. However only way at this time to get root is with a custom rooted kernel by chainfire. Which means root and safestrap will be dead on L if you are on a locked bootloader.
Click to expand...
Click to collapse
That's not right.. with the SuperSU betas you can flash them with any kernel from my experience so far. I have flashed the betas on the stock kernel on my N7 and N5 and so far I haven't had any problems. But I just opened FKU and that was it, so I might have the app and no root..
Vekhez said:
That's not right.. with the SuperSU betas you can flash them with any kernel from my experience so far. I have flashed the betas on the stock kernel on my N7 and N5 and so far I haven't had any problems. But I just opened FKU and that was it, so I might have the app and no root..
Click to expand...
Click to collapse
So you did not have to fastboot the boot.img on your N7? That is what I had to do. Not sure if you can just flash root to your kernel. Even instructions from chainfire shows you have to be unlocked to get the rooted kernel. https://plus.google.com/113517319477420052449/posts/fw659MWRewE
But if flashing SuperSU beta works then that would be easy. However, my searches did not point me in that direction on N7 threads.
Also even if flashing SuperSU beta works it still modifies the kernel correct? In this case locked phones will not get root since they can not have mod kernels right? You mention your N7 and N5 which both probably have a unlocked bootloader. We shall see what happens when L is dropped for retail devices.
I just searched more and even on the N5 to flash the SuperSU beta you need a unlocked bootloader. Please link something that shows a locked phone will get root with L please. Since you did say I was wrong. And that was my point. Looks like only way to root L is with a modified kernel which locked bootloader can not use. Besides you mention flashing it in TWRP. Locked bootloaders can not even use TWRP.
In my understanding if Selinux is set to permissive when the ROM is compiled, you would then be able to have root access and flash superuser. Correct me if I'm wrong though.
perfoliate said:
In my understanding if Selinux is set to permissive when the ROM is compiled, you would then be able to have root access and flash superuser. Correct me if I'm wrong though.
Click to expand...
Click to collapse
I hope you are correct. Last night was my first time flashing and rooting L. I hope root is not lost for locked phones. But you still need to be unlocked to have a custom recovery to flash root. So time will tell I guess.
---------- Post added at 05:49 PM ---------- Previous post was at 05:42 PM ----------
Looks like I am still correct: straight from chain fire:
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Posted 1 hour ago. https://plus.google.com/113517319477420052449/posts/EC5MhqFFqMK
Another example of the 14' X just got root and it has to be unlocked boot loader.
http://forum.xda-developers.com/moto-x-2014/general/lollipop-root-achieved-t2937154
Seriously!!! I do agree beggars cannot be choosers... But... The attitude of Moto X owners is Why do it when eventually we will get it!! But isn't it the same condition of other phones like Xperia Z, Nexus 4, Nexus 7, One Plus One? They know they will all eventually get it... But still people ported the ROMs without the binaries or the kernel!! I personally feel the whole point of XDA was to be independent! Not depending on an OEM for what u want! But lack of development makes me really sad, cuz the Moto X was Motorola's baby! It almost brought them back from the dead!!! Its got such brilliant hardware, just enough to be awesome n give a smooth experience! Anyways... All wanna enjoy their Motorola Goodies I guess... Let's just see what people think about development for this phone once its no longer supported By Motorola! Anyways at this point according to Motorola's time line its Droid Turbo next n then the Moto X.... Hoping to see lollipop soooon!
I am learning android programming right now... Just started playing around with codes.... I was messing with stock rom with few mods but no luck.... Let's see how it goes with AoSP source code.. ?
Sent from my XT1053 using XDA Premium 4 mobile app
Megatron007 said:
Porting is difficult ..why dont u build aosp 5.0 from source using cm device tree ?
Click to expand...
Click to collapse
Porting is actually really simple. Ive ported many roms. I am locked so i cant test anything but if anybody wants to test for me then ill give it a go. Pm me if interested
Travisdroidx2 said:
So you did not have to fastboot the boot.img on your N7? That is what I had to do. Not sure if you can just flash root to your kernel. Even instructions from chainfire shows you have to be unlocked to get the rooted kernel. https://plus.google.com/113517319477420052449/posts/fw659MWRewE
But if flashing SuperSU beta works then that would be easy. However, my searches did not point me in that direction on N7 threads.
Also even if flashing SuperSU beta works it still modifies the kernel correct? In this case locked phones will not get root since they can not have mod kernels right? You mention your N7 and N5 which both probably have a unlocked bootloader. We shall see what happens when L is dropped for retail devices.
I just searched more and even on the N5 to flash the SuperSU beta you need a unlocked bootloader. Please link something that shows a locked phone will get root with L please. Since you did say I was wrong. And that was my point. Looks like only way to root L is with a modified kernel which locked bootloader can not use. Besides you mention flashing it in TWRP. Locked bootloaders can not even use TWRP.
Click to expand...
Click to collapse
Yeah that's the thing you need to have an unlocked bootloader. That's the reason for L being such a pain to get root on. You need to either have an unlocked bootloader so that you can flash a custom recovery and flash the SuperSU Beta.zip, or you need an unlocked bootloader so you can flash an insecure boot.img which allows for root. But with a locked bootloader, I can see that getting root, is going to be somewhat of a difficult task, especially with some parts of Android becoming closed source.
atrix2man said:
Porting is actually really simple. Ive ported many roms. I am locked so i cant test anything but if anybody wants to test for me then ill give it a go. Pm me if interested
Click to expand...
Click to collapse
I am interested in testing
flipm00de said:
I am interested in testing
Click to expand...
Click to collapse
Ill pm u when its ready. Make sure u have a backup of your rom incase it doesnt boot lol
More details in the Verizon Note 4 forum here.
XDA:DevDB Information
EFIDroid, Kernel for the T-Mobile Samsung Galaxy Note 4
Contributors
abraha2d, m11kkaa
Source Code: https://github.com/efidroid
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2017-03-18
Created 2017-03-20
Last Updated 2017-03-31
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
vegoja said:
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
Click to expand...
Click to collapse
Believe me, I didn't do much work. You can donate to @m11kkaa, though. He's the developer of EFIDroid (if you didn't already know that...). I believe he has a donation link in his profile...
Sent from my Samsung Galaxy Note 4 using XDA Labs
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Mtotallywired said:
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Click to expand...
Click to collapse
EFIDroid is what you would call a "second-stage bootloader". The main advantage over Dual Boot Patcher (at least for me) is that you no longer have to patch zip files before installing. Also, EFIDroid is more than just a multi-boot solution. Quoting @m11kkaa:
efidroid tries to focus on simplicity, and doesn't require any kernel modifications etc.
in general: well having such a powerful bootloader in your boot stage gives you lots of possibilities, like multiboot, replacements/additions for kernels/ramdisk/cmdline.
This project has a lot more potential than what's currently implemented. i.e. you can give samsung devices fastboot and sony devices a standalone recovery. Also you can natively boot GNU GRUB if you're into booting linux kernel's the desktop way.
Click to expand...
Click to collapse
The two solutions are similar enough that you can migrate your setup from Dual Boot Patcher to EFIDroid without losing any data. I'll try to post a guide later this week.
I was I under the impression dual boot required multiple ROMs running the same kernel... If that is the case a huge advantage efi has is each ROM having their own boot img. I'm currently running 3 ROMs a lollipop a marshmallow and of course a nougat. I really just wanted to see all 3 latest android os running flawlessly on 1 device. And I did just that hats off to the developer for this.
baharvey7817 said:
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
Click to expand...
Click to collapse
There's an uninstall button in the app. Or, you could just flash the original boot.img via TWRP (basically what the uninstall button does).
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
mlock420 said:
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
Click to expand...
Click to collapse
you can look at their website, and then decide if you want this level of control over your phone.
http://efidroid.org/
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
1freedude said:
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
Click to expand...
Click to collapse
There's no way to have two different bootloaders. EFIDroid comes between the bootloader and the boot.img, so it has no control over the bootloader.
EDIT: EFIDroid may be able to emulate the behavior of another bootloader... you would have to ask @m11kkaa for details...
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
CousinMikeyP said:
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
Click to expand...
Click to collapse
Here is the LINK. You can see more info HERE
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
I will have to look into it... The EFIDroid app error messages are not exactly the most helpful kind. (Good thing the app is being phased out soon). That particular error message could mean many things, but most likely it's a connection issue. We will continue this in Slack.
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
RaySCLA said:
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
Click to expand...
Click to collapse
Tried what you suggested but it didn't work either. So, I chose the 'nuclear option': I wiped the phone completely then reinstalled the stock Marshmallow ROM. using Odin. After that i installed TWRP v3.0.2 (trltetmo) and Supersu v2.79 as well as Busybox v1.26. Only then was I able to install EFIDroid successfully. Now, I'm able to boot the stock rom as well as Resurrection Remix.
It seems that if your going to install EFIDroid you must have the phone rooted using SuperSU. Using Magisk to root your phone instead of SuperSu won't work (at least it didn't work in my case).
lowkeyst4tus said:
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Click to expand...
Click to collapse
This should work anywhere, regardless of ROM... But btw, it's a stretch to say TW is just a skin on top of AOSP. In fact, TW is probably the farthest you can get from AOSP... There's a lot of significant differences that make AOSP kernels incompatible with TW ROMs...