Troubles started when trying to upgrade to 23.5.A.0.575 shown here. The ROM simply got itself unrooted and ate my recovery. So I downgrade to 17.1.2.A.0.314 in order to root, successfully root, and then try every goddamn way to install a recovery but it just does not work. I've used the Nut's dual recovery here, the install script reports everything's peachy, it installs NDRUtils, but when I ask to reboot to recovery it just reboots normally. Also uring one of my attempts, the final ROM stayed rooted but /system became readonly, rendering it useless.
What do I do? If I flash the older firmware, shouldn't it wipe everything and make it possible to install the recovery normally - a recovery claimed to work with locked bootloaders? (I'm not unlocking my bootloader).
I lost my root (when updating to 575 from 570)three four days back, I installed lollipop ftf,rooted and installed recovery.
Didnt have any issues.
I installed .28 lp
http://www.ibtimes.co.uk/how-root-xperia-z3-z2-android-5-0-2-firmware-build-23-1-28-1509398
Related
I have a rooted GT 10.1 LTE with the EH04 update. I have tried flashing via CWM which results in the obvious breakage. I have also tried installing via Recovery and Odin with the attached files and in various combinations with no luck.
Any suggestions or ideas on what I am mucking up to not be able to get CWM only my tablet?
To note: It was working prior to the EH04 update.
Bump.
Any ideas?
try the cwm here:
http://forum.xda-developers.com/showthread.php?t=1090289
to a certain degree it is a lot of trial and error as to what parts of the various 10.1 models are common and which are distinct -- at this juncture what is to loose from flashing a different cwm?
Try this recovery ( flash zip)
http://www.mediafire.com/?w45j8i0fcj0wck0
Then try this rom
http://forum.xda-developers.com/showthread.php?t=1277045
Its been working very well for me.
Mr.Jester said:
I have a rooted GT 10.1 LTE with the EH04 update. I have tried flashing via CWM which results in the obvious breakage. I have also tried installing via Recovery and Odin with the attached files and in various combinations with no luck.
Any suggestions or ideas on what I am mucking up to not be able to get CWM only my tablet?
To note: It was working prior to the EH04 update.
Click to expand...
Click to collapse
I unrooted to get the EH04 updated using this: http://rootzwiki.com/topic/7718-romleakodineg01-factory-stock-odin-image-vzw-lte-tab-101/ , waited for the EH04 update, then re-rooted using this (which I used to root initially): http://rootzwiki.com/topic/2242-root-recovery-galaxy-tab-101-lte/ .
Perhaps you should unroot per the above, take the update, then re-root as above--worked for me.
i ota'd EH04, lost root. downloaded kernel.zip, applied it, got root back, installed cwmod, clicked to reboot into recovery and it's looping since, i can't do anything but get into ODIN but the PC wont recognize it, although i get a pop up saying android.. installed, adb devices doesn't pick up either. can't get into recovery.
---
update
http://forum.xda-developers.com/showpost.php?p=18121666&postcount=53
someone warned in the forums and i didn't read it before i did it, used odin to put recovery.zip, now i'm back in action.
The recovery you provided is the same that I attached. What I discovered however is that if I booted into recovery right after installing the CWM recovery, CWM would load. If I booted into stock EH04 then back into recovery, the stock recovery would load. It seems as if the ROM was restoring stock recovery when it loaded. After installing Lightspeed, CWM recovery stayed in place.
Either way, thank you for the assistance. I hope this thread ends up helping someone else.
My steps to install Lightspeed from Stock ROM EH04:
1. reboot recovery, install either recovery.zips above.
2. When the system automatically reboots, hold volume up to boot into recovery again. This time it should be CWM.
3. Wipe cache and factory reset
4. Install Lightspeed ROM
I
Mr.Jester said:
The recovery you provided is the same that I attached. What I discovered however is that if I booted into recovery right after installing the CWM recovery, CWM would load. If I booted into stock EH04 then back into recovery, the stock recovery would load. It seems as if the ROM was restoring stock recovery when it loaded. After installing Lightspeed, CWM recovery stayed in place.
Either way, thank you for the assistance. I hope this thread ends up helping someone else.
My steps to install Lightspeed from Stock ROM EH04:
1. reboot recovery, install either recovery.zips above.
2. When the system automatically reboots, hold volume up to boot into recovery again. This time it should be CWM.
3. Wipe cache and factory reset
4. Install Lightspeed ROM
Click to expand...
Click to collapse
Thank you. Everytime I tried flashing cwm recovery, I would always end up back at stock recovery. Your fix worked perfect.
I have received the OTA update for my stock rooted 4.3 device. When I tell the system to update, it reboots into recovery, which for me is TWRP. If I go to "install" it defaults to the sdcard/downloads folder and there is a file there called: ota_M7_UL_SENSE55-MR_TMOUS_4.19.531.10-3.24.531.3_release_351678 If I choose to "install" this, there's a bunch of error messages, first with "unable to locate zip" (references a specific file), followed by an "assert failed" and the "error executing update binary..."
I will assume that this is because of the fact that I'm rooted and have TWRP.
It's important for me to be stock (I need the TM WiFi calling) and I want to retain root. Given that, how can I update to Kit Kat?
You'll have to flash back to stock recovery and redo the OTA (or, if you know where the OTA file is on your device, boot into stock recovery and select that file for the update).
You will most likely loose root, but it's easy enough to reflash TWRP and superuser to get root back, I would imagine.
knytphal said:
You'll have to flash back to stock recovery and redo the OTA (or, if you know where the OTA file is on your device, boot into stock recovery and select that file for the update).
You will most likely loose root, but it's easy enough to reflash TWRP and superuser to get root back, I would imagine.
Click to expand...
Click to collapse
I found and flashed a stock recovery and then reran the OTA update. It appeared to have gone all the way through the process. When I reboot the device I get a pink screen that blinks with white dashes, and it does get to an HTC One splash screen with a blue beats audio icon (different than in 4.3). It never gets passed there.
I am able to adb and fastboot at that screen, so I was able to reflash TWRP, and tried rebooting, but get stuck at the same spot. I had done a TWRP backup a couple weeks ago, so I restored that so that at least I'm functional again.
Any advice on how to get 4.4 on this device?
When I was unlocked and rooted on 4.3 I relocked the bootloader, ran the 4.3 RUU and was able to get the OTA update then re-unlock and re-root
Basically, I did the same thing gwingzero said he did in this post
Hi so after updating from the stock zv6 to lollipop update my phone won't install a custom ROM. Every time I try to turn it on it goes straight to TWRP and went I install a ROM or try to load a backup as soon as I hit reboot it goes back to the TWRP page. Amy ideas?
You must flash back, using Flashtool, to zv4, then reroot, then flash newest TWRP. OTA software not included, because they flash every partition of the phone, including the boot loader. Stock roms like zv6 and zv8(lollipop)or AOSP, must be flashed from xda from here on out, because they've been modified to work correctly on zv4 boot loader. TWRP and root access only work correctly with zv4 boot loader.
sent from my LG G3
It sounds like there is no OS installed or it is stuck a reboot-loop. Try pulling the battery out for 10 seconds and if it still goes into twrp you know that it isn't a reboot-loop. When you go to restore a rom and it has the bar that shows the amount of storage does it say "0 MB"? If it does it means that twrp can't mount the storage on the phone thus causing it to not install/reboot. Have you tried side loading a rom via adb? Are you trying to install a rom off of a sdcard? I have seen many issues in the past sdcard related.
If you can please answer the following:
1) What is the message you are getting from twrp (if there is any)?
2) Have you installed a custom kernel and if so witch one?
3) What twrp are you running (the bumped one from xda or from the official twrp site) and what version is it?
4) Have you tried adb and pulling the battery?
If you answer these questions they should be able to tell us all that we need to know in order to help you out.
My SM-G900T is running Lollipop 5.1.1 rooted by installed twrp-3.0.2-2-klte + SuperSU using odin.
I am planning to update it to Marshmallow 6.0.1 (G900TUVS1GPK3) using odin. After the update, I believe the phone will be unrooted. Should I install twrp-3.0.2-2-klte + SuperSU again in order to bring back the root?
Yes, is the short answer. It's a pretty simple process, just flash the update, boot back to Download, flash TWRP, boot to recovery, then flash SU. However, after some experimentation, I'd recommend an extra step, especially if you're planning to run Xposed. After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
I'm not sure if you'll also need to wipe or not, all the updates I've done have been MM->MM. You can flash those without any wiping or restoring because they don't touch /data. I've found that switching between stock & modified MM roms without wiping appears to work but later causes severe performance problems. Between stock updates, I've had no problems even without wiping.
invisiblewave said:
Yes, is the short answer.
Click to expand...
Click to collapse
Thank you Invisiblewave. I understand that I need to reflash twrp, but since I installed SuperSU already and I think the update would not delete/uninstall it, if I flash SuperSu again, will there be a problem?
The update will remove your previous SuperSU install, so yes, you have to flash it again if you want root.
invisiblewave said:
After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
Click to expand...
Click to collapse
Thanks for the tips! I just did the same upgrade and wanted to make sure everything worked afterwards.
use this guide
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190
That guide is incomplete. It needs an additional step after flashing the update to let the phone boot once normally, otherwise WiFi calling doesn't work. Flash update, reboot (stock recovery runs and does stuff), reboot to Download, then flash TWRP, SU, Xposed, etc.
My TWRP suddenly went to "that state". And now System is ReadOnly. What I did - I used Super SU-app to take root temporarily "away" because I needed to use bank app. Then I enabled root again. Worked just great. But I think after that recovery is "dirty" I cannot find any other reason. Before root off / root on it TWRP was OK. Any idea how to fix? I have tried to flash same and previous version from Bootloader, cannot do - fastboot flash it OK but when I boot to recovery, nothing has changed. My root is working OK while on OS (I am still rooted).
I also tried to fix it flashing Asgard kernel. Kernel flash was OK and now I am on Asgard but TWRP is still the same even after flashing it again after Kernel.
I am on stock (Android 7.0) which I have debloated (everything worked just great before that switch root on / off)
File System is ext4.
Any ideas or do I just have to go back to original stock and then TWRP and root again? (Just do not want to do that too much work)
Thank You