Root and recovery for the latest nougat?! - Xperia Z4 Tablet Q&A, Help & Troubleshooting

Hello everybody, i'm new in this forum! I'm really disappointed because i can't root my tablet after many procedures, downgrades, updates, flashing!
Actually, there isn't a kernel and a recovery for the latest nougat version, and with the latest twrp the touch doesn't work. Even if i have unlocked bootloader i can't do nothing... I really appreciate if everyone has a solution for this!
I've tried root kernel but with the latest kernel the os doesn't boot, it stops with the boot animation.
I've tried downgrading with lollipop and marshmallow too, installed respectively twrp 2.8.0 and twrp 3.0 and then flashed a prerooted nougat zip created with prf creator, but after flashing it stucks with sony logo.

Can't help with TWRP but you can patch up boot.img of newest kernel (32.4.A.1.54, right ?) https://forum.xda-developers.com/xp...ot-automatic-repack-stock-kernel-dm-t3301605

zacharias.maladroit said:
Can't help with TWRP but you can patch up boot.img of newest kernel (32.4.A.1.54, right ?) https://forum.xda-developers.com/xp...ot-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse
Yes, i've tried this method. I can patch the boot.img of the newest kernel, but when i flash it to the tablet and then i boot in android, the touch doesn't work. it boots up, but i can't go over the lockscreen cause of the touch issue.

Related

Change of custom kernel and installation of new recovery

Hi xda!
I have a Z5C and i was tired of sonys laggy version of Android so I decided to install zombie kernel with twrp as backup.
The kernel works brilliant but I can only boot to recovery with help from fastboot. I would like to be able to boot to recovery directly from my phone without the use of fastboot/PC..
I also have a z4 tablet with Androplus kernel with twrp recovery.. And I am able to boot directly from the tablet to recovery.
So I decided to install Androplus and twrp for my z5c. I tried to install twrp through twrp and it looked like it was installed... However still not able to boot to recovery without fastboot. Then I tried to install with fastboot and I got an error - picture attached.
When I look under "about phone" the phone tells me that I'm still using the old zombiekernel??
How do I get Androplus kernel and working twrp installed on my z5c?
Thanks in advance
asl0501 said:
Hi xda!
I have a Z5C and i was tired of sonys laggy version of Android so I decided to install zombie kernel with twrp as backup.
The kernel works brilliant but I can only boot to recovery with help from fastboot. I would like to be able to boot to recovery directly from my phone without the use of fastboot/PC..
I also have a z4 tablet with Androplus kernel with twrp recovery.. And I am able to boot directly from the tablet to recovery.
So I decided to install Androplus and twrp for my z5c. I tried to install twrp through twrp and it looked like it was installed... However still not able to boot to recovery without fastboot. Then I tried to install with fastboot and I got an error - picture attached.
When I look under "about phone" the phone tells me that I'm still using the old zombiekernel??
How do I get Androplus kernel and working twrp installed on my z5c?
Thanks in advance
Click to expand...
Click to collapse
To boot to recovery in the z5c you gotta pudg the volume up while booting over and over until you see the notification LED go red-yellow-orange
Once you're in recovery you could restore your old kernal if you made s bsckup
I know... But that is not working. The only way i can get it to boot is with fastboot. What to do?
asl0501 said:
I know... But that is not working. The only way i can get it to boot is with fastboot. What to do?
Click to expand...
Click to collapse
Try flash tool to push anew kernel maybe.I've never done it but from what j have read, download your firmware from xperia firmware and use flash tool to only flash kernel.
You need to use fastboot to flash the boot.img to the phone and then do the same for recovery.img. It will then work with androplus kernel and twrp.
Thats my setup currently.
spikeyhair said:
You need to use fastboot to flash the boot.img to the phone and then do the same for recovery.img. It will then work with androplus kernel and twrp.
Thats my setup currently.
Click to expand...
Click to collapse
Sorry to resurect this old thread. Can you or anyone provide a boot.img or how to go about creating one? I am in same situation (stuck at boot screen) and only have access to fastboot. Thanks.
For which version of rom? I can give you 32.0.A.200 boot.img and twrp recovery.
Are you sure you're clicking volume up when booting? It doesn't work when you hold the volume up button down.
If y'all go to the twrp thread there is a modified boot.IMG that allows booting to recovery now.

TWRP doesn't boot after flashing latest build of H2OS

I flashed Oxygen Recovery and then installed the latest build of H2OS. After the ROM booted up, I flashed TWRP 3.0.2, 3.0.1 and 3.0.0 but none of these boot, i.e., my phone doesn't boot to recovery. What can I do now?
P.S.: Bootloader is unlocked
Found a remedy, flashing the BluSpark's modded version worked. Someone please tell me how to delete this thread :3

Revert from OSS 3.1.2 back to Cyanogenmod

I am on OOS 3.1.2 flashed with TWRP by Eng.stk v41 works fine , but i want revert do Cyanogenmod 13, if i flash Cyanogenmod via TWRP and do a Reboot, my device Stuck on Oneplus Logo and nothing happens.
Reboot to Recovery and flash OOS 3.1.2 again and boot into OOS works fine, but Cyanogenmod doesnt boot.
If i downgrad twrp version it doesnt boot anymore into Recovery
Some help pls
I am having exactly the same problem, and would also like to know the answer.
Also, the eng.stk TWRP is the only one I can find that works.
TECCC said:
I am on OOS 3.1.2 flashed with TWRP by Eng.stk v41 works fine , but i want revert do Cyanogenmod 13, if i flash Cyanogenmod via TWRP and do a Reboot, my device Stuck on Oneplus Logo and nothing happens.
Reboot to Recovery and flash OOS 3.1.2 again and boot into OOS works fine, but Cyanogenmod doesnt boot.
If i downgrad twrp version it doesnt boot anymore into Recovery
Some help pls
Click to expand...
Click to collapse
nickmcg said:
I am having exactly the same problem, and would also like to know the answer.
Also, the eng.stk TWRP is the only one I can find that works.
Click to expand...
Click to collapse
For future, i advise you to search before posting. I have posted this exact same reply on 3 threads. but anyway.
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, Hence it works as you're on the MM bootloader too.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
- Reboot to fast boot
- Flash Unofficial MM TWRP
- Boot into recovery
- Wipe everything except SD Card
- Flash OOS2 zip
- Boot into it
- Goto settings, unlock dev options, enable advanced reboot
- Then reboot to bootloader
- Install official TWRP, Done
Flash any ROM you want now.
Joshwin Aranha said:
For future, i advise you to search before posting. I have posted this exact same reply on 3 threads. but anyway.
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, Hence it works as you're on the MM bootloader too.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
- Reboot to fast boot
- Flash Unofficial MM TWRP
- Boot into recovery
- Wipe everything except SD Card
- Flash OOS2 zip
- Boot into it
- Goto settings, unlock dev options, enable advanced reboot
- Then reboot to bootloader
- Install official TWRP, Done
Flash any ROM you want now.
Click to expand...
Click to collapse
Many thanks, I'll give it a try
nickmcg said:
Many thanks, I'll give it a try
Click to expand...
Click to collapse
Look at cm13 thread, because now is possible to flash cm13 on new bootloader (from today's nightly I suppose)

Cant Flash Recovery or ROM

I am using TWRP 3.0.2.0 It is giving me problems as shown in images below.
I tried flashing new recovery but it also couldn't get flashed. While flashing new CM 13/CM14.1 ROMs it is giving errors, but it flashes older CM 13 ROMs fine.
dvaibhavd said:
I am using TWRP 3.0.2.0 It is giving me problems as shown in images below.
I tried flashing new recovery but it also couldn't get flashed. While flashing new CM 13/CM14.1 ROMs it is giving errors, but it flashes older CM 13 ROMs fine.
Click to expand...
Click to collapse
Bro wait....!!!
Is this real?
You are using too old recovery(as your ss says 2.8.7)+old boot loader..you need some work on your phone to be able to flash new cm 13/14.1.
Just head over to general thread and find how to upgrade boot loader and install latest twrp.
After that you can flash all latest available ROM.
Boot logo Problem
Hey I have used this method http://forum.xda-developers.com/one...update-bootloader-firmware-to-t3478917/page20 and updated the BL.However after flashing CM14 I am stuck on 1+ logo.
I was able to flash stock Oxygen Rom .I want to flash CM 14 please help
Same
utkhirodka said:
Hey I have used this method http://forum.xda-developers.com/one...update-bootloader-firmware-to-t3478917/page20 and updated the BL.However after flashing CM14 I am stuck on 1+ logo.
I was able to flash stock Oxygen Rom .I want to flash CM 14 please help
Click to expand...
Click to collapse
Same here with the TZ issues. As for the recovery, the TWRP version 3.0.2-0 is the most latest one that I can flash & boot into successfully. If I flash anything newer than 3.0.0-1 my OPX is stuck on OP logo as well.
My phone is stuck at one plus boot logo when i tried to go into recovery mode or tried to start it the oneplus logo popped and goes out again and again and when i tried to flash twrp through fastboot mode it say the device is locked cant change or erase the recovery what should i do please guide me
The only recovery that will flash on mine is 3.0.2-0. I've tried flashing through Fastboot. I've even tried to use the dd command for both 3.0.3-0 official and blu sparkz v41 and it gets stuck at the OnePlus logo.
Phone still boots into OOS just fine and 3.0.2-0 flashes through the old JMZ TWRP app just fine. It's just any other method that doesn't work.
The latest recoverys for new bootloader is 3.0.3, bluesparks 3.0.2-1 V41 or Sultans updated TWRP. 3.0.2 and under us for old bootloader.
Exodusche said:
The latest recoverys for new bootloader is 3.0.3, bluesparks 3.0.2-1 V41 or Sultans updated TWRP. 3.0.2 and under us for old bootloader.
Click to expand...
Click to collapse
Again, I tried flashing 3.0.3 and it wouldn't stick.
blackknightavalon said:
Again, I tried flashing 3.0.3 and it wouldn't stick.
Click to expand...
Click to collapse
After flashing recovery you have to boot right into it with fastboot command then swipe to allow modifications?
Exodusche said:
After flashing recovery you have to boot right into it with fastboot command then swipe to allow modifications?
Click to expand...
Click to collapse
As stated above, all it does is hang at the OnePlus logo.
Also...
fastboot boot drive:\path\to\twrp-3.0.3-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.507s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.540s
Click to expand...
Click to collapse
blackknightavalon said:
As stated above, all it does is hang at the OnePlus logo.
Click to expand...
Click to collapse
Ok sorry what I did was keep it simple. Reflash original stock recovery, flash 2.2.3 then flash 3.1.4 and boot. Just skip everything and reboot back to bootloader mode. Now you can flash latest TWRP and should boot latest ROMs without any issues.
Exodusche said:
Ok sorry what I did was keep it simple. Reflash original stock recovery, flash 2.2.3 then flash 3.1.4 and boot. Just skip everything and reboot back to bootloader mode. Now you can flash latest TWRP and should boot latest ROMs without any issues.
Click to expand...
Click to collapse
2.2.3 flashed successfully. I already know 3.1.4 will work. I'll post again if your plan completely works.
...and I'm still getting the same errors after flashing 3.1.4 through stock recovery. o.0
I'm going to start from the earliest firmware available and flash progressively from there and see if that works.

Error Code 7 while flashing new ROM or twrp and Remote dtb not found

Here is the Solution watch this video
https://www.youtube.com/watch?v=kTdKmceC5xU
am not able to update twrp
twrp-3.1.0-0-onyx.img
twrp-3.0.3-0-onyx.img
twrp-3.0.2-1-onyx.img
when i flashed these files using twrp and rebooted my device i was stuck in one plus logo.
Even i cant flash any of above 3 twrp files using fastboot adb method i am getting an error "remote dtb not found" pls check screenshot
then i reinstalled twrp-3.0.2-0-onyx.img using adb fastboot method , but i cant not install or update version above 3.0.2.0 plz help
Hi guys if anyone facing same problem Read this
PROBLEM
1)Error Code 7 while flashing new ROM (like Nogut ROMS ).
2)Remote dtb not found while updating old twrp to new (eg. twrp 2.8 to twrp 3.1.0.0)
Cause of problem
Users who have already flashed and rooted their phone and using custom ROMs like CM12 CM 13 or any other from past year will likely to face this problem
while updating twrp recovery or while updating to new custom ROM Nogut cm14 .
Because new custom ROMs have bootloader in diffrent partition (something like this) so you wont be able to flash your phone with new ROMs i.e cm14 or nogut or you wont be able to flash new twrp recovery which is 3.1.0.0
Please keep in mind if you are using following twrp version then you should flash your phone with old twrp 2.8.7.0
twrp-3.0.2-0-onyx.img 14.4M 2016-04-04 23:04:23 EDT
twrp-3.0.1-0-onyx.img 14.5M 2016-04-01 04:24:54 EDT
twrp-3.0.0-1-onyx.img 14.5M 2016-02-15 23:17:25 EST
twrp-3.0.0-0-onyx.img 14.4M 2016-02-06 09:18:41 EST
above point is important look at the solution now
Solution
Step
1)flash your phone with old twrp version TWRP 2.8.7.0 using fastboot method(because we are going to install stock recovery in my case stock recovery of oneplus X lollipop version)
2)after installing stock recovery install 2.14 ver of stock ROM of oneplus X (for oneplus x devices) (for other brands eg samsung look for ur old stock recov and ROM)
3)install old Stock ROM in ur device
4)now again boot into stock recovery and install latest stock ROM (for oneplus X i installed latest oneplus X oxygen OS 3.1.4).
5)after doing above step you can install latest twrp-3.1.0-0-onyx.img without any "remote dte not found error" using fastboot.
6)once you flash twrp-3.1.0-0-onyx.img flash your phone with latest CM14 or any latest android N or nogut ROM without any problem
Note : For error code 7 some people suggested to edit udatescrip file which is not good solution and it is temporary and it wont work for all so do it as i suggested
Comman ERRORS :
1) if you are on twrp 3.x.x.x you will face Remote dte not found while booting your phone in stock recovery using fastboot
so first of all flash your phone with old twrp 2.8.7.0.
2)Do not wipe your internal storage in frustration it will create more problems because you wont be able to transfer files into your phone to flash it (Use OTG cable or SD card if u did it already).P.S you can do it afterwards
Do i need to install stock recovery of stock ROM ? some help would really be appreciated
i can install all twrp upto "twrp3020 " version
but if i try to flash greater version like twrp3021 or twrp3100 m getting same error
i need new twrp because i am not able to flash Android N custome roms i am getting an error code 7 when i am installing ROM
Follow the mega unbrick guide, then update your bootloader then flash latest twrp.
@Joshwin Aranha
CheckYourScreen said:
Follow the mega unbrick guide, then update your bootloader then flash latest twrp.
@Joshwin Aranha
Click to expand...
Click to collapse
thanx for replay but i found solution
Hi guys if anyone facing same problem Read this
PROBLEM
1)Error Code 7 while flashing new ROM (like Nogut ROMS ).
2)Remote dtb not found while updating old twrp to new (eg. twrp 2.8 to twrp 3.1.0.0)
Cause of problem
Users who have already flashed and rooted their phone and using custom ROMs like CM12 CM 13 or any other from past year will likely to face this problem
while updating twrp recovery or while updating to new custom ROM Nogut cm14 .
Because new custom ROMs have bootloader is diffrent partition (something like this) so you wont be able to flash your phone with new ROMs i.e cm14 or nogut or you wont be able to flash new twrp recovery which is 3.1.0.0
Please keep in mind if you are using following twrp version then you should flash your phone with old twrp 2.8.7.0
twrp-3.0.2-0-onyx.img 14.4M 2016-04-04 23:04:23 EDT
twrp-3.0.1-0-onyx.img 14.5M 2016-04-01 04:24:54 EDT
twrp-3.0.0-1-onyx.img 14.5M 2016-02-15 23:17:25 EST
twrp-3.0.0-0-onyx.img 14.4M 2016-02-06 09:18:41 EST
above point is important look at the solution now
Solution
Step
1)flash your phone with old twrp version TWRP 2.8.7.0 using fastboot method(because we aree going to install stock recovery in my case stock recovery of oneplus X lollipop version)
2)after installing stock recovery install 2.14 ver of stock ROM of oneplus X (for oneplus x devices) (for other brands eg samsung look for ur old stock recov and ROM)
3)install old Stock ROM in ur device
4)now again boot into stock recovery and install latest stock ROM (for oneplus X i installed latest oneplus X oxygen OS 3.1.4).
5)after doing above step you can install latest twrp-3.1.0-0-onyx.img without any "remote dte not found error" using fastboot.
6)once you flash twrp-3.1.0-0-onyx.img flash your phone with latest CM14 or any latest android N or nogut ROM without any problem
Note : For error code 7 some people suggested to edit udatescrip file which is not good solution and it is temporary and it wont work for all so do it as i suggested
Comman ERRORS :
1) if you are on twrp 3.x.x.x you will face Remote dte not found while booting your phone in stock recovery using flashboot
so first of all flash your phone with old twrp 2.8.7.0.
2)Do not wipe your internal storage in frustration it will create more problems because you wont be able to transfer files into your phone to flash it (Use OTG cable or SD card if u did it already).P.S you can do it afterwards
mhmm.. the unbrick guid dosnt help.. followd the guidé - now my bootloader is locked and stuck locked so no 2.8.7.0 flashing.. Ideas? i`m working now 24h this issue..
Wagner.B said:
mhmm.. the unbrick guid dosnt help.. followd the guidé - now my bootloader is locked and stuck locked so no 2.8.7.0 flashing.. Ideas? i`m working now 24h this issue..
Click to expand...
Click to collapse
are you on stock recovery right now ?
Finaly the Lv.2 support got it back working via "our" msm unbrick tool (Still got it on my drive =D)
but learned nothing - trying to get lineageOS again.
The recovery is now TWRP v3.1.0-0 for E1003_15_161107 (it works for now on a backup..)
But... i must say - I'm very worried that i cant flash lineage again..
I dont know what the trick is...
Here is the Solution watch this video
https://www.youtube.com/watch?v=kTdKmceC5xU
Yes!!
I ve been looking for a solution the past days since i got stuck in older twrp versions and could only upgrade to android 6.
Thanks man!! You rock!!

Categories

Resources