After installing openscript recovery TWRP 2.2.1 via goo manager and then realize the recovery could not mount system or install any zip. I then try to revert back to team rogue xm recovery 1.5.0 with sucess by installing the recovery zip in TWRP (although some error due to system unable to mount). Got pretty happy that I'm able to revert back to rogue recovery but now faces this STUCK in automatic rebooting to recovery everytime I've try to reboot. I wipes everything completed 3x and install new rom but can't ever boot pass the recovery. I have yet to revert back to stock via softbrick method and figure I should ask for help first before unroot and unlock to start from scratch. below is an image of when ever I booted my xoom. Thanks for any help.
Oh, I've search first but noon seem to have the same problem as mine.
Hello people!Yesterday i wanted to remove my old 4.0.4 old custom rom from my p500 and install a new...i didnt know if my phone was rooted so i checked it..and my phone was rooted..i installed the ClockworkMod rom manager and i downloaded the rom put it in the sd card all ok until this part...when the Aroma Menu was finished the phone rebooted and got a fastboot mode...i said to my self its ok i will revive the phone(it was bricked) when i did that and all was working fine and the stock rom too i wanted to try it again...to install the new rom i mean...but when i try to get into ClockworkMod menu from boot it always getting me into Android system recovery <3e>...how can i fix that? thanks!
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.
I am a beginner to this Android platform and it's been more than a year since the purchase of moto xt1602. I have tried rooting the phone and was successfull in the first attempt itself by flashing stock recovery over two and installing superuser. But I have downloaded the ota for nougat and tried to install so I unrooted the superuser and tried but was getting errors so tried to replace twrp over stock recovery but I can't able to remove the twrp I even tried with the flashify apk but it displayed no memory partition found and I can't able to flash the twrp and I'm stuck in half way. I would be glad to receive help from experienced personnel and add the link to stock recovery for moto g4 play xt1602
I have Tecno W3LTE-H356D1-M-161216V55 with Android Mashmallow 6.0. I'm trying to install TWRP recovery so i can root my phone with SuperSU, but when i flash the correct version of the custom recovery i want, it gives out an error "PMT changed for the ROM, it must be downloaded". I tried to search the solution online, but it suggested that i should format my phone. After i format my phone, it deletes everything including the ROM installed which requires installation of it again so i can flash anything on it (including the custom recovery), and after that, i get the same PMT error when i flash TWRP again. Is there any way i can root my phone, or install TWRP on it? If not, how can i successfully flash TWRP on this phone?
Hey bro, first u need to unlock bootoader then flash that twrp image using fastboot it wont work when using sp tool