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
Related
I tried using superboot to root my nexus s, but ended up with having a stuck google screen upon reboot.
Is there anyway I can recover my phone to the original state. I can get into the boot screen by pressing up volume and the power button and I have downloaded an original rom; however, I don't know how to upload this rom
into the phone.
I unlocked the bootloader, and have the android SDK installed. I do have a response when I use the command "fastboot devices"
Is there any possible way to save my phone? Please help, Thanks in advance
is there a recovery image saved under the recovery option?
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
ri ch said:
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
Click to expand...
Click to collapse
You have to flash CWM using fastboot, not adb.
fastboot flash recovery recovery.img
Once you have the custom recovery flashed you can flash superuser in CWM to get root back or just flash one of the custom ROMs that include superuser.
Yes, I did exactly that.
I really have no idea what I'm doing so I'm extremely grateful for people who do.
Thanks
I am in the same boat as these other chaps. After installing the 2.3.6 OTA update I tried to root with Superboot and now my Nexus S just sits on the Google screen with the open padlock.
I've tried installing CWM recovery, as well as the boot.recovery.img that comes with Superboot, and it seems to install successfully. After rebooting my phone still sits on the Google screen, however.
Am I doing something wrong here (I'd previously rooted with few problems)?
EDIT: I should mention that after flashing the .img I'm trying to boot into recovery - at this point it just sits on the Google screen.
EDIT 2: Never mind, I sorted it. I tried using a different recovery.img (from this thread) and I was then able to get into recovery and restore a backup.
I had kitkat 4.4.4 stock rom with CWM and root. I messed with skinning apps and lost navigation and status bars so i was able restore to 4.4.4 stock rom but phone wont re-root nor load cwm / twrp recoveries. Every time i try pushing recovery via Moto tool or fast boot the phone reboots. same thing with root.
I was able to install and old version of TWRP but that caused a boot loop.
Is there a low level format or linux command line / DFS guide i can use to restore it to "new out of box state"?
Did you locked your bootloader again?
Some tutorial to restore stock ROM include command to lock bootloader
Check that.
I pushed an old version of chainfire SU via fastboot and flashed newest version CWM recovery through Flashify app.
Removing the boot animation gave time to side load kernal / radio and wipe dalvik cache.
Is this to state there is a way to root the CDMA Verizon with 4.4.4 ?
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Martynhsmith said:
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Click to expand...
Click to collapse
I've come across this today (my OPO was rooted and I had TWRP installed), I was able to install the OTA via returning the OPO back to an unrooted stock build. You can easily do this via getting the 'Fastboot' zipped version of your current .....1NO build.
Once you have this, you only need to fastboot flash the following: - boot.img, recovery.img and system.img
After flashing just these three images, yes you'll loose root but you'll be able to OTA update to the ......2QL build via the normal phone method - hten if you want, you could then reflash a TWRP recovery and re-install a supersu.zip
One thing I forgot to add, which maybe helpful to others as it took me a moment to realise, both boot.img and recovery.img flash without issue, but due to it's size to flash the large system.img you'll probably need to brake it down into flashable chunks, notice the change in fastboot commands: -
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot -S 512M flash system system.img
Martynhsmith said:
I have a one plus one that is rooted and twrp v2.8.5.1 installed
In about phone it says I'm running 12.1-YOG4PAS1NO
The phone started telling me I have a system upgrade
I have been round the install update booting to twrp path twice
So I downloaded the .....1NO to ...2QL ota
Boot into TWRP and try to install the zip file and it says it can't do it as this device has one plus/bacon/A0001.44.2/KVT49L/XNPH2SR: User/release keys
What can I do?
Click to expand...
Click to collapse
OTAs can only be flashed through stock recovery..applicable to all devices
Hello,
on the same subject, I am looking for explanations on how to create twrp flashable files for ota updates. Do you know where I could find any resources?
Thx
I had the same issue while installing the incremental update (I got root and TWRP); I solved it simply installing the signed zip of ...2QL version which was pulled out yesterday afternoon. My only concern was about root that could be wipe away with the new installation, so I directly installed SuperSU via zip. Everything works fine till now
Sent from my A0001
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.