Hello im very new to modifying android and ive started to try and root my xperia z5. So far ive unlocked the bootloader and flashed twrp, this seems to work and everything boots fine. i downloaded super su zip and tried to flash it from twrp. It didnt install the super su zip and i dont have root. Is this because i am trying to do it with a stock kernel. i am on the latest official sony firmware 7.1.1 i think. Can you please advise what i need to do and what i need to download as in if i need a kernel. also if i flash a kernel now will it delete the twrp i flashed. Thankyou and please forgive me if its been asked lots ive tried search but cant find exactly what i need. As i said im very new and its hard to get your head around how it all works
Sorry update, now I tried twrp and it booted into the recovery fine when I said reboot to system it won't boot into system, stuck on Sony screen. Can someone please help m a bit stuck now
and32 said:
Sorry update, now I tried twrp and it booted into the recovery fine when I said reboot to system it won't boot into system, stuck on Sony screen. Can someone please help m a bit stuck now
Click to expand...
Click to collapse
Try this guide: https://forum.xda-developers.com/xperia-z5/general/ftf-e66xx-patched-kernels-google-drive-t3630282
Thanks I think I'll just try first steps and flash it back to stock.
Can I just ask, in that guide, can I just use fastboot adb and flash just the patched kernel and then twrp again, could that solve my problems or will I have to use flash tool and install that rom aswell thanks
and32 said:
Can I just ask, in that guide, can I just use fastboot adb and flash just the patched kernel and then twrp again, could that solve my problems or will I have to use flash tool and install that rom aswell thanks
Click to expand...
Click to collapse
Flash stock firmware again, flash patched kernel, flash twrp, flash either newest supersu or newest magisk, and done.
Thanks for your help, I flashed just the kernel and the latest twrp and it booted straight up, thankyou
Related
Hello all. Im new to this particular forum. I own a Galaxy Nexus, but I am unlocking/rooting my buddies One S for him. I have gone through the loops already; unlocked the bootloader, rooted, and installed custom recovery (CWM) with no issues. I was pleasantly surprised to find out that it was a snap compared to his previous HTC Legend. Nightmare.
Anyway, forgive me if this has in fact been answered as I have been searching. After a custom ROM is flashed you still have to flash a boot img via fastboot? I attempted to install CM10 yesterday and get stuck at the HTC boot screen?? Luckily I made a nandroid of the stock ROM and easily reverted. Where do I find the appropriate boot img? Is it just the img that is found in the unpacked ROM? Couldn't find anything pertaining to this in the ROM write up. I know with my Nexus you flash the ROM via recovery and that is it. Strange that you need to also flash the boot img following the ROM flash.
Any help is appreciated.
brunswick000 said:
Hello all. Im new to this particular forum. I own a Galaxy Nexus, but I am unlocking/rooting my buddies One S for him. I have gone through the loops already; unlocked the bootloader, rooted, and installed custom recovery (CWM) with no issues. I was pleasantly surprised to find out that it was a snap compared to his previous HTC Legend. Nightmare.
Anyway, forgive me if this has in fact been answered as I have been searching. After a custom ROM is flashed you still have to flash a boot img via fastboot? I attempted to install CM10 yesterday and get stuck at the HTC boot screen?? Luckily I made a nandroid of the stock ROM and easily reverted. Where do I find the appropriate boot img? Is it just the img that is found in the unpacked ROM? Couldn't find anything pertaining to this in the ROM write up. I know with my Nexus you flash the ROM via recovery and that is it. Strange that you need to also flash the boot img following the ROM flash.
Any help is appreciated.
Click to expand...
Click to collapse
Hello there, since you installed cwm recovery, you have to flash the boot.img via fastboot, if you have the twrp recovery you may not need to flash it via fastboot, it does it for you if you have an hboot under 1.14 but if its over that hboot your going to have to flash the boot.img for any Rom via fastboot. It still wouldn't hurt to flash the boot.img via fastboot but that's just me, well I hope I helped you and if I did then good, and if you wanna know more just ask...
If I helped then just press the thanks button
Sent from my One S
leohdz148 said:
Hello there, since you installed cwm recovery, you have to flash the boot.img via fastboot, if you have the twrp recovery you may not need to flash it via fastboot, it does it for you if you have an hboot under 1.14 but if its over that hboot your going to have to flash the boot.img for any Rom via fastboot. It still wouldn't hurt to flash the boot.img via fastboot but that's just me, well I hope I helped you and if I did then good, and if you wanna know more just ask...
If I helped then just press the thanks button
Sent from my One S
Click to expand...
Click to collapse
Got it to work. Thank you. :good:
brunswick000 said:
Got it to work. Thank you. :good:
Click to expand...
Click to collapse
Hi,
I was using CM10 and now I want to revert back to my previously used stock ROM. However after restoring I'm still unable to boot (I'm using ClockworkMod Touch). Do I need to flash the stock boot.img too? Where I can find it?
Thanks in advance!
TnTonly said:
Hi,
I was using CM10 and now I want to revert back to my previously used stock ROM. However after restoring I'm still unable to boot (I'm using ClockworkMod Touch). Do I need to flash the stock boot.img too? Where I can find it?
Thanks in advance!
Click to expand...
Click to collapse
Its in the rom.zip just extract it. Also look for Flash Image Gui in apps section as enables you too flash a boot.img direct from your phone whilst booted in a rom and will even extract the files for you from the new rom.zip!
Edit: Link to Flash Image Gui - http://forum.xda-developers.com/showthread.php?t=1954121
shadowch31 said:
Its in the rom.zip just extract it. Also look for Flash Image Gui in apps section as enables you too flash a boot.img direct from your phone whilst booted in a rom and will even extract the files for you from the new rom.zip!
Edit: Link to Flash Image Gui - http://forum.xda-developers.com/showthread.php?t=1954121
Click to expand...
Click to collapse
I can't find the zip file for stock HTC ROM
Anyway, I found the boot.img in the nandroid backup folder and it's all good now.
Thank you for the link! ^_^
I would also switch to TWRP. Seems to have less issues, if any, for most folks
Get it thru Goo Manager from PlayStore--
Hi all,
So I've been playing around with Sabermod. Tried to install it, but had to update bootloader. Did that, everything still worked fine. Then I tried to upgrade my Kernel with Beeto's kernel, which is downloadable in that post. I did that using this guide from XDA-University with CWM. Since I did that, my phone is stuck in a boot loop.
Every few minutes I see the "bootloader unlocked"-screen, with just a black screen in between.
Ok, I have just now been able to reboot back into CWM recovery by using ADB command line tools. But I have no idea where to go from here.
Any help would be greatly appreciated.
Thanks,
Rubb
Edit: I have the XT1039, also known as Peregrine
Edit: I fixed it!
So I think the problem was that I flashed the kernel made specifically for this ROM, but tried to reboot the phone before installing the ROM. I managed to get into recovery with adb, then I flashed the kernel again, I did a full wipe, flashed the ROM, flashed Gapps, rebooted the phone. And it worked.
Thanks _that for your help!
Try "adb pull /proc/last_kmsg" to get the previous kernel log. Then install a working kernel (should be part of most ROMs).
_that said:
Try "adb pull /proc/last_kmsg" to get the previous kernel log. Then install a working kernel (should be part of most ROMs).
Click to expand...
Click to collapse
Adb can't find my device now it is in recovery mode. I'm a bit afraid to move out of recovery mode as I might not be able to get back in. What's the best way to install a kernel? Is just flashing the zip with CWM good? When I flashed the zip of Beeto's kernel. The log said: "Bricking device. Installation successful. Have fun." I suppose that was meant to be funny and not serious? I hope
Rubb001 said:
Adb can't find my device now it is in recovery mode.
Click to expand...
Click to collapse
I don't know about CWM, but TWRP enables adb by default. Maybe you need to install drivers on your PC, or use Linux.
Rubb001 said:
I'm a bit afraid to move out of recovery mode as I might not be able to get back in. What's the best way to install a kernel? Is just flashing the zip with CWM good?
Click to expand...
Click to collapse
Yes, that should work.
_that said:
I don't know about CWM, but TWRP enables adb by default. Maybe you need to install drivers on your PC, or use Linux.
Yes, that should work.
Click to expand...
Click to collapse
I just thought about something. So I flashed Beeto's Kernel, but I didn't flash his ROM, the stock ROM is still on the phone. Could this be why he's stuck in bootloop ? Would it work if I now flash SaberMOD?
Ok firstly, I do have some novice experience with rooting and such, but this is my first HTC device and it seems a little different and I'm just trying to be really cautious as I can't afford to brick this phone. If someone could assist me, I have the ATT model running build 656287. Would really appreciate assistance in being able to throw CM on here. Thanks!
unlock your device from htcdev.com
flash twrp
backup your rom and data
flash supersu
Behzad.hotknife said:
unlock your device from htcdev.com
flash twrp
backup your rom and data
flash supersu
Click to expand...
Click to collapse
Unlocked it perfectly, but when I flashed TWRP and tried to boot into it, it went back into stock recovery. Any ideas?
How are you flashing the recovery?
What command are you using?
Behzad.hotknife said:
How are you flashing the recovery?
What command are you using?
Click to expand...
Click to collapse
Fastboot flash recovery recovery.img
Try another twrp issue for your HTC one A9. Look for latest on twrp page. Then recovery will boot into twrp
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Habbz said:
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Click to expand...
Click to collapse
You unlocked your bootloader before, right?
seems the original recovery is working, and not twrp.
after boot loader unlock you flashed TWRP via fastboot?
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Habbz said:
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Click to expand...
Click to collapse
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
wiQbold said:
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
Click to expand...
Click to collapse
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Habbz said:
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Click to expand...
Click to collapse
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
wiQbold said:
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
Click to expand...
Click to collapse
I'm looking for one that can play remote play, heard it uses Magisk , i'm not too sure though, yeah it's been solved thanks.
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