Database Info

[Q] Can't install TWRP recovery

Can anyone tell me how I flash a recovery to the device from a zip file? Going into CWM and flashing the TWRP recovery initially seems to work, but if I then interrupt the reboot and go straight into recovery, I still see CWM, not TWRP. I'm stuck on the CWM recovery and need TWRP to try to install the Kitkat upgrade.
Should I unzip the components first and then flash the image using fastboot, or is there another way? I'm wary of fastboot as I've already (temporarily) "bricked" the Xoom by flashing a zip instead of an image that way. None of the instructions I've read has much advice on getting round installation problems.
I'm guessing the persistent CWM was caused by my selecting (at an earlier stage) the CWM option to fix the problem of the stock recovery being reinstated at each reboot. Can this be undone? Although I've installed Xoom-Universal-Root, apps that require root access - including GooManager - also fail with an access error. It's hard to tell whether the device is now rooted or not, so if there's any method of getting further without root access, that would be great.
====================
Edit: it looks as if the instructions I saw online, which mentioned two separate TWRP recoveries, were incorrect. To get Android Kitkat 4.4 onto my Xoom I didn't need the initial TWRP recovery, only the BigPart version. Once I skipped to the BigPart recovery, the problem described above did not recur.

[Q] Lost ROOT after manually updating last OTA via TWRP

As title says... I had unlocked bootloader and flashed TWRP then SuperSU and ROOT was working fine.
- Last OTA I got which was yesterday (as only just got the phone) was XNPH33R.
- I used TWRP to install the update which went fine except I lost ROOT access.
- Went back to TWRP and reinstalled SuperSU which shows as installed on my phone - however no apps that require ROOT can get ROOT access and RootChecker shows that the phone is not rooted.
- Rebooted to System / Tried to Fix Permissions / Tried to reinstall newest SuperSU - nothing works
Does anyone have any suggestions as to how I can regain ROOT or is not possible on XNPH33R?
Further issues I have now got no ADB access in Fastboot no matter what drivers I install... don't know if this is all linked!!!
Jesus christ
Any help appreciated.
Thanks in advance

Too much work if you do a full wipe and re rooted ?
Also try to put zip file with airdroid and flash it in download mode

So I've found out that although adb was telling me that it couldn't recognise any devices in fastboot mode - all the actual commands from the OnePlus One toolbox were actually getting through as I relocked my Bootloader to see what would happen and then tried to Flash Recovery and it told me Bootloader was locked - so that confirmed adb commands were working.
To solve my ROOT problem I did the following:
1) Flashed CM XNPH22R
2) Installed all OTA updates
3) Unlocked Bootloader
4) Installed TWRP - then chose REBOOT TO SYSTEM (this told me I wasn't rooted and then followed prompts)
5) I chose to install SuperSU from Play Store
6) Opened SuperSU and updated binaries
7) Turned off Update CM Recovery in Developer Options
8) Rebooted and installed and ran Root Checker....
9) Success!

Remove the respect CM root settings from the SU settings menu and your root will come back i had the same problem until i found this out.

Cholerabob said:
Remove the respect CM root settings from the SU settings menu and your root will come back i had the same problem until i found this out.
Click to expand...
Click to collapse
Thanks - wish you told me that earlier!!
I assumed it should be on because it's CM right!!! Doh!
Oh well - this might help someone else...

[Completed] [Q] Z Ultra 6833 CWM Help

So I was trying to install cyanogenmod on my phone as I was tired of waiting for Sony to update it to lollipop. I've done this on all of my older Samsung phones. So this is what I did:
1: Tried to install CWM using XZU recovery. It restarted my phone but would not boot into recovery mode.
2: Realized I need to root my phone so I rooted it. I have root access in apps except I can't install the binarys in supersu because the stock recovery option does not work and CWM doesn't either.
3. I then thought maybe I need to unlock the bootloader so I unlocked it and tried step 1 again but with the same outcome.
So essentially I am at a point where I can't install the binary in SuperSU due to the recovery being corrupt. I also can't install CWM due to not having the binarys for root installed. Is there away for me to get out of this mess?
Yes I realize I shouldn't have did it in the order that I did but I did it based on a few documentations that I saw that did not state I needed any of that and on past experience on different phones I was able to go straight to CWM.

gizmo1992 said:
So I was trying to install cyanogenmod on my phone as I was tired of waiting for Sony to update it to lollipop. I've done this on all of my older Samsung phones. So this is what I did:
1: Tried to install CWM using XZU recovery. It restarted my phone but would not boot into recovery mode.
2: Realized I need to root my phone so I rooted it. I have root access in apps except I can't install the binarys in supersu because the stock recovery option does not work and CWM doesn't either.
3. I then thought maybe I need to unlock the bootloader so I unlocked it and tried step 1 again but with the same outcome.
So essentially I am at a point where I can't install the binary in SuperSU due to the recovery being corrupt. I also can't install CWM due to not having the binarys for root installed. Is there away for me to get out of this mess?
Yes I realize I shouldn't have did it in the order that I did but I did it based on a few documentations that I saw that did not state I needed any of that and on past experience on different phones I was able to go straight to CWM.
Click to expand...
Click to collapse
Hello,
You need to do the following.
1. Root Your Device.
2. Unlock Boot loader.
3. Download CM12.
4. Open Its Zip And Extract Kernel.
5. Download Flashtool.
6. Use Flashtool To Flash Kernel.
7. Reboot Into Recovery And Flash ROM
Sent from my AO5510 using XDA Premium 4 mobile app

Men_in_black007 said:
Hello,
You need to do the following.
1. Root Your Device.
2. Unlock Boot loader.
3. Download CM12.
4. Open Its Zip And Extract Kernel.
5. Download Flashtool.
6. Use Flashtool To Flash Kernel.
7. Reboot Into Recovery And Flash ROM
Sent from my AO5510 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashtool doesn't see my phone. I know that I have my phone in the right mode because it has the blue LED and I know I have the correct drivers because it shows them in Device Manager as well as I had to put it in this mode to unlock the boot loader in the first place.
Nevermind flashtool randomly saw my phone. Going to try and install the new kernal. Will update
So here is what I finally did to get CM12.
1 I used Sony's flashtool to install the stock image and start over.
2 I then used the SP flashtool to install CWM kernel
3 I then installed CM12 in CWM and all is good

[Completed] Help with reinstalling bootloader

Hi.
I am relatively experienced user who has rooted and installed custom roms on samsung galaxy and HTC desire phones before.
I have now attempted to root my alcatel onetouch pixi 4 (4034X) using instructions from this thread :- https://forum.xda-developers.com/android/general/alcatel-one-touch-pixi-4-t3376597
I got as far as flashing twrp recovery and now the phone is stuck in constant reboot. I downloaded alcatels mobile upgrade tool in hopes of reflashing the stock rom but it seems to be looking for a later rom than the one I have installed and keeps telling me I have the lastest and so wont flash.
So can I recover from this at all or have I just bricked my phone? Is there a way to FORCE the mobile upgrade tool to reflash the current rom rather than looking for an upgrade?
It seems that everything except the bootloader is intact so is there another tool I can use to restore the bootloader?
Any help would be greatly appreciated.

Looks like I managed to unbrick using a combination of SP Flash tool and an SPFT rom for the 4034X I found on the internet. will now try reflashing a different recovery tool.

O.K. so I think what is happening is an issue when unlocking the bootloader and not when flashing recovery.
This is what I did:-
1. Enabled developer mode.
2. Turned on usb debugging and unlocked bootloader oem
3. Rebooted phone, plugged in cable and accepted connection authorisation.
4. From windows typed adb reboot bootloader. Went into to fastboot.
5. Typed fastboot oem unlock, Pressed volume up on phone.
At this point I was put back in fastboot but none of the buttons worked and the phone looked like it had frozen. Was It wiping data at this point? There was no indication that it was doing anything.
I removed the battery and reinserted but when I restarted I got the same boot loop problem. Had to restore stock firmware AGAIN.
Am I doing something wrong?

Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?

nyarlathotep_uk said:
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
Click to expand...
Click to collapse
Hi & welcome to xda-assist,
you can try to force the installation of supersu systemless by this step, chances are good that this will make it boot properly.
boot into twrp >go to the terminal > and type:
echo SYSTEMLESS=false>>/data/.supersu
Don't know if the recovery you use has this terminal option but it's very likely.
You can do additional a Google search on "force SuperSU systemless" to get more information / background information..
Good luck
Sent from my OnePlus 2 using XDA Labs

Thanks for your reply Sam.
I only read that after I had found a copy of a CM13 Rom that worked with The 4034X. I basically flashed superSU first then did a wipe, then installed the custom rom and google apps nano before downloading the supersu apk from google play and reinstalling. Now I have a rooted phone with a custom rom and am somewhat happier. The reason I wanted to root was to remove the bloatware that was taking up 1.5 GB of my already measly 2GB internal memory and this new ROM only takes up .5 GB.
I still have some pain. For example many of the Rom Toolbox Pro functions don't work and I think its because the system image seems protected and refuses to mount rw no matter what I do. Even issuing a remount command using the device name from cat /proc/mounts tells me the block device is read only. I also seem to be unable to verify if I have busybox or install it due to the same reason.
It also took me some time to work out that the boot animations weren't stored in /data/local or /system/media but to /data/system/theme.
This used to be so much easier in the days of ice cream sandwich and lollipop. Ah well!

Update:- Managed to flash busybox 1.26 using a flashable zip via adb sideload in Caliv Recovery (Caliv can't see my adopted storage for some reason).
I'm happy now! Would still like to have a rw system so I can remove some system apps I don't use but its no biggie.

How to finish rooting unlocked Blu J1 Marsh 6.0 phone with Adb

Okay, happy post Vday. :good:
So, Im trying to root an unlocked Blu J1, running Marsh. 6.0.
I recently reset it, due to perf. issues & now trying to root.
My setup is Win7, w/ the latest Usb drivers through Sdk & UniversalAdb. I have Usb debugging active on the phone & the device shows at command level with Adb devices & in Fastboot mode**Ive unlocked the bootloader on the phone itself, & then xferred the Twrp.img files different times.
The twrp files were the latest 2 off the site Twrp.me as of 02/15. Its a successful transfer on fastboot, which is good. but when I go to restart, it shows as stock recovery studio_j1_6.0/user/release-keys but not the touch responsive Twrp. ..
I eventually want to use Su or Magisk zip to gain root. The phone remains bootloader unlocked which is good. I've tried the Adb command, adb root, and then went through these steps, -still nothing. Im on the hunt for recent clockwork mod, to try that way, only ones are like '11 or'12.
So, is the stock recovery hard coded. -it doesnt have 2 separate partit-I ran a partit check just in case. I also went to grab the omnirom androidrecovery 6.0 off Github at github.com/omnirom/android_bootable_recovery/tree/android-6.0, but its .zip. And when I apply updates through Sd card update in stock recovery, I get install aborted across the board on any .zips.. Im on the waiting list for Kingroot to add my device. so thats good.
Either way Android SU shows as not rooted once fully on.
Any feedback greatly appreciated.