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
Related
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???
Hey all,
Has anyone tried rooting the new OTA firmware B560? If so, can you post which versions of TWRP and SuperSU were used? And if you happen to have the links to the downloads that would be great too!
T.I.A.
Hi, for twrp I've used the version from this thread http://forum.xda-developers.com/showthread.php?t=3156779 for supersu used the version 2.62 from chainfire website. Installed twrp through fastboot, then in twrp installed supersu. I believe newer versions of supersu works too.
Stuck on Huawei Logo
Bonnie1977 said:
Hey all,
Has anyone tried rooting the new OTA firmware B560? If so, can you post which versions of TWRP and SuperSU were used? And if you happen to have the links to the downloads that would be great too!
T.I.A.
Click to expand...
Click to collapse
Okay so I flashed TWRP with no problem, then rebooted normally. Powered off and entered TWRP recovery to flash SuperSU. It installs fine but then when I reboot it just stays stuck on Huawei Logo.
Please help!
Bonnie1977 said:
Okay so I flashed TWRP with no problem, then rebooted normally. Powered off and entered TWRP recovery to flash SuperSU. It installs fine but then when I reboot it just stays stuck on Huawei Logo.
Please help!
Click to expand...
Click to collapse
i am quoting myself here
qkrusty said:
does anybody know which supersu root is working with this latest B560?
Click to expand...
Click to collapse
SuperSU_v2.64_Pro and BETA-SuperSU-v2.52
what i did after upgrading to B560 ( from rooted B522)and loosing root is, flash twrp ,boot into twrp then flash superSu 2.64 pro zip in twrp , rebooted the phone but there was no superSu icon , i then went and install superSu 2.52 beta apk , rebooted the phone , then i opened superSu , it automatically updated the binaries and voila
ps: i reflashed the B522 stock recovery before upating to B560 with a full rom zip from http://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
edit : i used twrp from @somboons app ,it is twrp 2.8.7.0 here's the link http://forum.xda-developers.com/mate-7/development/tool-srk-tool-huawei-beta-02-20160501-t3369990
touns_j said:
i am quoting myself here
SuperSU_v2.64_Pro and BETA-SuperSU-v2.52
what i did after upgrading to B560 ( from rooted B522)and loosing root is, flash twrp ,boot into twrp then flash superSu 2.64 pro zip in twrp , rebooted the phone but there was no superSu icon , i then went and install superSu 2.52 beta apk , rebooted the phone , then i opened superSu , it automatically updated the binaries and voila
ps: i reflashed the B522 stock recovery before upating to B560 with a full rom zip from http://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
Click to expand...
Click to collapse
My problem is I never make it past the Huawei Logo. So I have no idea if SuperSU actually installs. I have reflashed stock recovery for B560, but that still doesn't seem to help. The next step I'm going to take now is to reinstall the update package for B560 and then if I'm able to boot up I'll try your method. Wish me luck!
Bonnie1977 said:
My problem is I never make it past the Huawei Logo. So I have no idea if SuperSU actually installs. I have reflashed stock recovery for B560, but that still doesn't seem to help. The next step I'm going to take now is to reinstall the update package for B560 and then if I'm able to boot up I'll try your method. Wish me luck!
Click to expand...
Click to collapse
good luck mate , you will sort it out
ps: once you've manually flashed SuperSu , and click on reboot , Twrp will throw a message saying " you don't have root bla bla bla " , and offer to " root " , never accept that , ignore the request
touns_j said:
good luck mate , you will sort it out
ps: once you've manually flashed SuperSu , and click on reboot , Twrp will throw a message saying " you don't have root bla bla bla " , and offer to " root " , never accept that , ignore the request
Click to expand...
Click to collapse
actually I never got that message when I clicked on reboot. Can you tell me which TWRP version you used?
Bonnie1977 said:
actually I never got that message when I clicked on reboot. Can you tell me which TWRP version you used?
Click to expand...
Click to collapse
i used twrp from @somboons app ,it is twrp 2.8.7.0 here's the link http://forum.xda-developers.com/mate...60501-t3369990
I used TWRP 3.0.2.0 from the package that Churdy linked in the main thread with all the different versions of software.
mega:///#!9kBWnY7T!ybhARn5UNXAyxrdQZ1ytKks24eCyzxkgdVhEza6zwFQ
I just had bricks from using genuine Chainfire SuperSU until I used the forum SuperSU Pro 2.64 which also comes with an unroot file.
mega:///#!0wITxJLR!S2iIVNjveSDMdne5QMNqd6so41vbTEK9tSJXJkOJJnw
I have not got Xposed to run properly yet though.
I'm freaking out!!! I can't get any USB debugging recognition, so I have no way of reinstalling the B560 firmware update. I have stock recovery now and my phone just keeps staying on the Huawei logo. Please somebody HELP!!!!
RobboW said:
I used TWRP 3.0.2.0 from the package that Churdy linked in the main thread with all the different versions of software.
mega:///#!9kBWnY7T!ybhARn5UNXAyxrdQZ1ytKks24eCyzxkgdVhEza6zwFQ
I just had bricks from using genuine Chainfire SuperSU until I used the forum SuperSU Pro 2.64 which also comes with an unroot file.
mega:///#!0wITxJLR!S2iIVNjveSDMdne5QMNqd6so41vbTEK9tSJXJkOJJnw
I have not got Xposed to run properly yet though.
Click to expand...
Click to collapse
i use the above and it doesnt work. still no root eventhough it manage to install
i noticed during installation
it says
remounting system r/w
is this mean it fail to mount??
ok now this work.
before install supersu
go to mount menu and enable system mount
then only install supersu
--------------------
sorry to say i still cannot get full root. cannot go copy paste to system. it still read only. supersu not responding at all!!!?
i disable supersu ( the uncheck button) and exit. then launch again supersu, it update the binary successfully, and reboot. after reboot, i launch and re-enable supersu ( check button) then try to cut/past to system ...unfortunately unsuccessful
ahhl said:
i use the above and it doesnt work. still no root eventhough it manage to install
i noticed during installation
it says
remounting system r/w
is this mean it fail to mount??
ok now this work.
before install supersu
go to mount menu and enable system mount
then only install supersu
--------------------
sorry to say i still cannot get full root. cannot go copy paste to system. it still read only. supersu not responding at all!!!?
Click to expand...
Click to collapse
Maybe Huawei security software is blocking it from running?
Did you wipe dalvik/cache?
RobboW said:
Maybe Huawei security software is blocking it from running?
Did you wipe dalvik/cache?
Click to expand...
Click to collapse
i did try to wipe dalvik/cache but it freeze. luckily i able to reboot successfully
---------- Post added at 10:24 AM ---------- Previous post was at 10:12 AM ----------
RobboW said:
Maybe Huawei security software is blocking it from running?
Did you wipe dalvik/cache?
Click to expand...
Click to collapse
ok i go to phone manager and allow supersu to autolunch
now supersu works.
I just used the unroot zip and it worked. This is good as I can root, make changes then unroot.
Edit:
It seems removing root has allowed my file manager to still do root operations, possibly as it was already allowed root access prior to uninstalling SU. Other user apps cannot access root. I just put the Huawei Notepad app back into system/priv-app from backups folder in Storage. Permissions were ok without altering. All I needed was a wipe dalvik/cache in TWRP and reboot.
Unfortunately I reflashed the Stock Recovery and now I'm not able to do anything. I've tried adding the dload folder with the B560 update to reinstall the firmware, but it fails at 5%, with both the OTA update and the Full versions. I'm soooo scared that I have bricked my device. When I reboot into the stock recovery I get 3 options, Reboot System, Wipe data/factory reset and Wipe cache partition. And when I manually force it into fastboot/rescue mode the computer doesn't recognize the phone.
Please someone tell me that my device can be saved somehow! I don't know what else to do :*(
Bonnie1977 said:
Unfortunately I reflashed the Stock Recovery and now I'm not able to do anything. I've tried adding the dload folder with the B560 update to reinstall the firmware, but it fails at 5%, with both the OTA update and the Full versions. I'm soooo scared that I have bricked my device. When I reboot into the stock recovery I get 3 options, Reboot System, Wipe data/factory reset and Wipe cache partition. And when I manually force it into fastboot/rescue mode the computer doesn't recognize the phone.
Please someone tell me that my device can be saved somehow! I don't know what else to do :*(
Click to expand...
Click to collapse
Which stock recovery did you use though? It must be the right one to work.
I found a flash fail at 5% was when there is no update in the /System/dload folder if you're trying to force it to do OTA. I did that by accident. Thought I bricked it but it re-booted ok.
If you use the dload folder in SD card, Marshmallow prefers to kick off the update from the dialler app.
If you used the wrong recovery, maybe it will flash from SD ok with a different ROM but we need to know exactly what recovery you flashed to it. That controls partitioning which you probably messed up.
See if you can re-install a driver and see it with ADB somehow.
RobboW said:
Which stock recovery did you use though? It must be the right one to work.
I found a flash fail at 5% was when there is no update in the /System/dload folder if you're trying to force it to do OTA. I did that by accident. Thought I bricked it but it re-booted ok.
If you use the dload folder in SD card, Marshmallow prefers to kick off the update from the dialler app.
If you used the wrong recovery, maybe it will flash from SD ok with a different ROM.
Click to expand...
Click to collapse
I used this one... So it should have worked properly. How can I flash it from the SD card? I'm willing to try anything right now. Because I'm about to go crazy!
Bonnie1977 said:
I used this one... So it should have worked properly. How can I flash it from the SD card? I'm willing to try anything right now. Because I'm about to go crazy!
Click to expand...
Click to collapse
this recovery works fine from me , i extracted it from B560 update.app.. hmm try and give B522 recovery a try then , put the update.app file in the dload folder and put it on your sd card root folder, then flash the stock recovery using recovery mate7 mobopx v2.1 http://depositfiles.com/files/dkok9h43y then use the 3 buttons trick to force install the firmware
edit : when updating with the full update , you only put the update.app file in the dload folder, nothing else
touns_j said:
this recovery works fine from me , i extracted it from B560 update.app.. hmm try and give B522 recovery a try then , put the update.app file in the dload folder and put it on your sd card root folder, then flash the stock recovery using recovery mate7 mobopx v2.1 http://depositfiles.com/files/dkok9h43y then use the 3 buttons trick to force install the firmware
edit : when updating with the full update , you only put the update.app file in the dload folder, nothing else
Click to expand...
Click to collapse
Yesssss!!! I finally got it fixed... I added the full B522 update to my sd and forced the update and it WORKED!!! The B560's wouldn't but that one did... I don't understand why seeing that I had B560 when I tried rooting my device. I'm just glad that I have my phone back!! :good::laugh:
Bonnie1977 said:
Yesssss!!! I finally got it fixed... I added the full B522 update to my sd and forced the update and it WORKED!!! The B560's wouldn't but that one did... I don't understand why seeing that I had B560 when I tried rooting my device. I'm just glad that I have my phone back!! :good::laugh:
Click to expand...
Click to collapse
i'm glad it worked (i should probably remove that recovery though , maybe the file got corrupted while i was uploading it who knows , but it works fine for me )
Heres the latest update from LG.
Must be at least 20f with TWRP to flash this.
To get TWRP go here: (Kdz to 20f if on 20g)
https://forum.xda-developers.com/showthread.php?t=3533338
Do NOT wipe system or you might get stuck in twrp bootloop.
**********************
FLASHING INSTRUCTIONS
**********************
1. MUST BE IN 20F.
2. DO NOT FORMAT SYSTEM.
2. TWRP BACKUP FIRST
3. Flash from TWRP.
DOWNLOAD
LG-V521-20G-Stock-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705254
LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
***********************************
LG-V521-TWRP.ZIP (Thanks to shabbypenguin)
***Also adds flashing TWRP to recoverybak so if an error comes up your stock recovery doesn't get reflashed.
https://www.androidfilehost.com/?fid=673368273298934005
***********************************************
COMING FROM ANOTHER ROM FLASHING INSTRUCTIONS
***********************************************
1. TWRP BACKUP FIRST
2. PLACE ROM IN INTERNAL STORAGE
3. WIPE DATA, CACHE, DALVIK/ART CACHE, SYSTEM
4. FLASH ROM FROM INTERNAL STORAGE.
*****IF IT REBOOTS BEFORE FINISHING FLASH, PRESS AND HOLD VOLUME DOWN AND POWER TILL OFF.
*****THEN ON REBOOT WITH VOLUME DOWN AND POWER PRESS, LET GO OF POWER ONLY FOR A SLIT SECOND AND *****REPRESS TO GO INTO FACTORY RESET MODE. THEN SAY YET, AND IT WILL GET YOU BACK TO TWRP.
*****IN TWRP, GO TO REBOOT AND SELECT POWER OFF. THEN GO TO STEP 4.
**************
ERROR???
**************
If you wipe system then flash a rom you might get stuck in twrp bootloop.
Here's a fix by ralphwiggum1:
https://forum.xda-developers.com/showpost.php?p=70851933&postcount=39
If that fix fails, then flashing stock recovery is another option. Then you'll have to reroot and get twrp again. If your on 20g, you'll have to kdz 20f and start over.
LG-V521-STOCK-RECOVERY.zip
https://www.androidfilehost.com/?fid=745425885120710531
Sent from my LG-H811 using Tapatalk
Thank you!, working 100%
LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
Sent from my LG-V521 using Tapatalk
MicroMod777 said:
LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
Sent from my LG-V521 using Tapatalk
Click to expand...
Click to collapse
what was debloated?
SiNJiN76 said:
what was debloated?
Click to expand...
Click to collapse
Most gapps and tmo bloat.
Sent from my LG-V521 using Tapatalk
SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?
rbadh91 said:
SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?
Click to expand...
Click to collapse
Odd. Flash just SuperSU then:
https://forum.xda-developers.com/showthread.php?t=3452703
Sent from my LG-H872 using Tapatalk
MicroMod777 said:
Odd. Flash just SuperSU then:
https://forum.xda-developers.com/showthread.php?t=3452703
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
It went back to stock recovery after flashing the zip. adb reboot recovery takes me to stock recovery.
Vol Down + Power to boot, and letting go of Power holding down Vol Down, then pressing Power & Vol Up takes me to the "hard reset" prompt, and it actually wipes device when selecting yes. I'm thinking the recovery has changed in 20G and it wipes the device instead of taking you to recovery.
Joey's Root Checker shows "Sorry! Root access is not properly installed on this device". SuperSU shows "There's no SU binary installed and SuperSU cannot install it. This is a problem."
I have a feeling I'll have to downgrade to 20F using KDZ.
EDIT: Weird...FlashFire shows "Root was found, but access could not be acquired! Supported roots: SuperSU, Magisk, CM SU (SELinux/Permissive)) Found root: (null)".
Installed SuperSU app, no luck. Tried Superuser app, no luck.
rbadh91 said:
SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?
Click to expand...
Click to collapse
I had the same issue. Lost root and twrp. Had to downgrade and start from scratch.
NoMoreBackdoors said:
I had the same issue. Lost root and twrp. Had to downgrade and start from scratch.
Click to expand...
Click to collapse
Yea I've had this happen multiple times now. Twrp is somewhat buggy where if theres a crash during flashing, or if you format the system partition, somehow theres a failsafe feature that restores the stock recovery.
I thought I had it figured out and made a flashable zip for twrp that also flashes it to the recoverybak partition. But it happened aga7n.
Sent from my LG-V521 using Tapatalk
MicroMod777 said:
Yea I've had this happen multiple times now. Twrp is somewhat buggy where if theres a crash during flashing, or if you format the system partition, somehow theres a failsafe feature that restores the stock recovery.
I thought I had it figured out and made a flashable zip for twrp that also flashes it to the recoverybak partition. But it happened aga7n.
Sent from my LG-V521 using Tapatalk
Click to expand...
Click to collapse
There's another update on my tablet...(after flashing your zip from 2-22). Will you be doing another zip with this new update?
New update is 95.22MB. I'm guessing security update. I would be wary, as the 20g update patches dirty cow, but still allows downgrade to 20f. This could block downgrade. Any brave souls out there want to confirm?
LvDisturbed1 said:
New update is 95.22MB. I'm guessing security update. I would be wary, as the 20g update patches dirty cow, but still allows downgrade to 20f. This could block downgrade. Any brave souls out there want to confirm?
Click to expand...
Click to collapse
I know I'm late, but I just picked one of these tablets up this week. I didn't think much about what I was doing, and did all OTA updates that where available. This was on 10/25/2017 or so. I was able to then use Uppercut and LGUP to flash backwards to V52120i_00_0619.kdz and successfully root, and install TWRP.
I didn't keep stock long, I jumped over to Lineage OS 14.1.
Be warned though, on Lineage OS the weekly on 10/27/2017 will cause a bootloop in TWRP. At least it did for me. After install, and while stuck in bootloop it is pretty easy to fix:
1. Open ADB Shell and run the following 2 commands:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Then reboot and all will be well.
sgrant said:
I know I'm late, but I just picked one of these tablets up this week. I didn't think much about what I was doing, and did all OTA updates that where available. This was on 10/25/2017 or so. I was able to then use Uppercut and LGUP to flash backwards to V52120i_00_0619.kdz and successfully root, and install TWRP.
I didn't keep stock long, I jumped over to Lineage OS 14.1.
Be warned though, on Lineage OS the weekly on 10/27/2017 will cause a bootloop in TWRP. At least it did for me. After install, and while stuck in bootloop it is pretty easy to fix:
1. Open ADB Shell and run the following 2 commands:
Then reboot and all will be well.
Click to expand...
Click to collapse
QUOTE
I've been running stock for a while and had this in a drawer for a year. I decided I'd start using it in my kitchen to pull up recipes on chrome. I decided to do a "factory reset" to start "clean" forgetting the warning not to do it. Now I'm stuck in a TWRP bootloop.
How can I get out of this?
Or should I switch to lineage?
Why there is no LG-V521-20N version?
After carrier unlocking Japanese S7 edge SCV33 model, the firmware changes to SC-02H.
To root the device ( Nougat )
First enable OEM unlocking from the developers options.
Flash this TWRP via odin v3.12.5
https://www.androidfilehost.com/?fid=817550096634747128
After installing, Please backup the whole rom to your SD card.
If you have any problem backing up. You can flash the stock recovery image in the link below and your device will boot up fine.
If the TWRP backup is a success,
First make sure your device boots up with this Twrp installed before rooting.
If the device boots up, then flash the SuperSu. If the device doesnot boots up, flash the stock recovery.
Workaround:
If the device fails to boot up with this twrp, Flash the super su. Turn off the device, then flash the Stock recovery via odin and bootup the phone. See if Super Su is installed.
Flash this flashable SuperSu v2.82.zip
http://www.supersu.com/download
You will loose root after a factory reset. Flash again!!!!
DONOT DO ANYTHING WITHOUT BACKING UP.
First boot will loop for few times.
YOUR SIM CARD WILL RUN FINE
After rooting, incase you want your stock recovery, or your device doesnot boots up. Flash this via odin.
S7 edge SC-02H Stock recovery image
All credit goes to the rightful owners.
If this doesnt help and you fail to boot up the device or you messed up the device..... just restore from twrp and flash the stock recovery. You will have your device back to normal like it was before.
Hit thanks if this helped.
Below are some screenshots with SuperSu and all japanese apps removed!
You can also change the boot animation of this device by replacing corresponding botanimation files.
Backup the stock bootanimation files first.
Navigate to ;
root/system/media and replace the boot animation files.
Link is below.
And dont forget to set their permissons to ( r-w-r-r )
UPDATE:
Xposed also working....
download link below.
Xposed installer from PurifyOs....
So, i found a new rom for our device
Found a new rom for our device... anybody would like to test it???
Flash the rom via ODIN....
Caution: I have experienced loosing my imei number if i perform a factory reset after installing this rom. Because of the previous nandroid backup, i was able to bring back device to previous working state. DO IT ON YOUR OWN RISK..
My advice is that you backup your current rom and then only FLASH.
You get the idea.
Lot of work needed in this rom.
However it is stable...
Anybody who would like to modify????
All credit goes to the rightful owner....
Features like:
inbuilt fingerprint app lock
new launcher
all japanese bloats removed
no requirement of japanese docomo country code while dialing certain numbers
samsung keyboard
many device languages
New launcher etc
DOWNLOAD HERE
Reserved
Reserved
Im a newbee and i just bought s7edge android 6.0.1
how to unlock carreer?
and what should i know please help me?
thanujas said:
Im a newbee and i just bought s7edge android 6.0.1
how to unlock carreer?
and what should i know please help me?
Click to expand...
Click to collapse
if you are from my area, i think i can help u
Following this thread. I have an SCV33 device with SC-02H software. Tried to install TWRP, backup and wipe functions not working. I get the error "failed to mount /data invalid argument"
Anything I can test other than this method?
deodatss said:
Following this thread. I have an SCV33 device with SC-02H software. Tried to install TWRP, backup and wipe functions not working. I get the error "failed to mount /data invalid argument"
Anything I can test other than this method?
Click to expand...
Click to collapse
go to wipe and format data..... itll run fine...
but remember to backup...
did twrp cause your nfc not working? im use twrp 3.1 but it cause my nfc cant work, lead i cant use clear cover.
OFz said:
did twrp cause your nfc not working? im use twrp 3.1 but it cause my nfc cant work, lead i cant use clear cover.
Click to expand...
Click to collapse
yes nfc wont work on this root method.
deodatss said:
yes nfc wont work on this root method.
Click to expand...
Click to collapse
I realize that is due to twrp, if you have rooted, try to flash stock recovery (not test yet @@)
P/S Hix, cant fix with stock recovery, sr. Why? AAAAAaaaaa
---------- Post added at 03:51 AM ---------- Previous post was at 03:22 AM ----------
everyonesweird said:
...
UPDATE:
Xposed also working....
download link below.
Xposed installer from PurifyOs....
Click to expand...
Click to collapse
Wow is amplify module work? Can you write a tut to install and unistall?
OFz said:
I realize that is due to twrp, if you have rooted, try to flash stock recovery (not test yet @@)
P/S Hix, cant fix with stock recovery, sr. Why? AAAAAaaaaa
---------- Post added at 03:51 AM ---------- Previous post was at 03:22 AM ----------
Wow is amplify module work? Can you write a tut to install and unistall?
Click to expand...
Click to collapse
Yes....
Inorder to solve the failed to mount data.... you will have to boot into twrp and then go to wipe. At the bottom left.. you will see fomat data....
You will loose all the phone memory data so first its better you backup....
Then you will have no problem.. you can boot up all ok.
to install xposed..... Flash the xposed installer from twrp and the reboot. Install the xposed apk file and there you go.. you have your Xposed.
To uninstall xposed if incase you dont like it... Uninstall the xposed apk... reboot to twrp and flash the xposed uninstaller.zip
Hey, I was just wondering, can we change our CSC codes so we can avoid getting carrier bloatware?
deodatss said:
Hey, I was just wondering, can we change our CSC codes so we can avoid getting carrier bloatware?
Click to expand...
Click to collapse
you can manually delete the carrier bloats using any root explorer after rooting. you can then make and save a debloated nandroid backups..
or
you can go ahead and try whatever you are feeling like to... Life is an experiment my friend.
everyonesweird said:
Yes....
Inorder to solve the failed to mount data.... you will have to boot into twrp and then go to wipe. At the bottom left.. you will see fomat data....
You will loose all the phone memory data so first its better you backup....
Then you will have no problem.. you can boot up all ok.
to install xposed..... Flash the xposed installer from twrp and the reboot. Install the xposed apk file and there you go.. you have your Xposed.
To uninstall xposed if incase you dont like it... Uninstall the xposed apk... reboot to twrp and flash the xposed uninstaller.zip
Click to expand...
Click to collapse
About root, yes, i can root my phone, but the problem is nfc has been disable, i dont know why, i cant find the reason. I tried like this:
cook rom - nfc ok
flash twrp - nfc not working
re-flash stock recovery - then nfc ok
so im try by re-flash twrp and install su to root (nfc not working) then im re-flash stock recovery: result nfc not working
BTW, thank you for your tut to install xposed
The link for TWRP is dead. Any chance to get a new one?
So I have this TWRP backup that i restored through.
I install SUPERSU zip from TWRP, all the scripts run fine, no issues or interruptions.
However, once I boot up normally, go through the setup process of Android's first boot and install the Super User app, it does not detect root X(
I have tried flashing the latest BETA & stable SuperSU zips (2.82)
I have tried older SuperSU zips (2.79)
None of the above have worked for me,
I have a European HTC U11+
S-ON, Unlocked Bootloader, Build 1.24.400.3
Any help would be great
Found the FIX
So every guide i've tried for my u11+ has been leading me to a debacle.
However, after days of restoring and resetting and reflashing and backing up, I have finally got my phone to root properly
Turns out none of the latest or typical Supersu zips worked for me.
So I went to this thread : https://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Downloaded this supersu zip : https://devfiles.co/download/wJDOxFEm/SR3-SuperSU-v2.82-SR3-20170813133244.zip
DO NOT BOOT THE RECOVERY IN THE GIVEN LINK, just flash the supersu
I hope this helps out other people as well
usmantahir said:
So every guide i've tried for my u11+ has been leading me to a debacle.
However, after days of restoring and resetting and reflashing and backing up, I have finally got my phone to root properly
Turns out none of the latest or typical Supersu zips worked for me.
So I went to this thread : https://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Downloaded this supersu zip : https://devfiles.co/download/wJDOxFEm/SR3-SuperSU-v2.82-SR3-20170813133244.zip
DO NOT BOOT THE RECOVERY IN THE GIVEN LINK, just flash the supersu
I hope this helps out other people as well
Click to expand...
Click to collapse
Why you didn't just use magisk? It is so simple...
Because I'm facing another issue, whenever I go to recovery after i setup my phone through normal boot, the password works at twrp but when I try to boot up, the device decryption password turns up invalid and I lose access to everything. It's a vicious cycle ?
Maybe it's cz I flashed a different build onto my phone
(Originally: 1.24.401.12, flashed: 1.24.400.3)
usmantahir said:
Because I'm facing another issue, whenever I go to recovery after i setup my phone through normal boot, the password works at twrp but when I try to boot up, the device decryption password turns up invalid and I lose access to everything. It's a vicious cycle ?
Maybe it's cz I flashed a different build onto my phone
(Originally: 1.24.401.12, flashed: 1.24.400.3)
Click to expand...
Click to collapse
Try to flash 1.24.401.7 ruu via sdcard method and after that flash corresponding recovery. You can find it in recovery thread
skodann said:
Try to flash 1.24.401.7 ruu via sdcard method and after that flash corresponding recovery. You can find it in recovery thread
Click to expand...
Click to collapse
It won't flash.. shows some sort of incompatibility
Also, i tried flashing the system.img of 1.24.401.12, it still reads 1.24.401.3 when i boot up
usmantahir said:
It won't flash.. shows some sort of incompatibility
Also, i tried flashing the system.img of 1.24.401.12, it still reads 1.24.401.3 when i boot up
Click to expand...
Click to collapse
It wouldnt flash but it did successfully install the full RUU zip of 1.24.401.7 using the SDCard method
And later, I was able to take the OTA to the latest build 1.24.401.12