Ok not sure what i did wrong I phone OTA updated to 4.4.3 and i lost root but my boot loader was still unlocked so i reran auto root it cleared my phone.. (very anonying) My phone was encrypted i expected it to prompt me for password but it did't (also i had changed password so it was different from pin code.) was there anyway to avoid the wipe for next time?
Don't use cf-auto root. Just flash a recovery via fastboot (if recovery was replaced by the OTA) then flash a SuperSU.zip to root it.
I'm fact, if you use Philz recovery instead of CWM, You can root directly from the menus without flashing anything
Sent from my Nexus 5 using Tapatalk
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.
Basically I followed a guide on here before to root my phone with the simple procedure:-
1. Unlock bootloader at HTCDev
2. Install clockwork mod via fastboot recovery custom_recovery.img
3. Install zip from SD card using CWM (root.zip - includes all root items)
4. Update Superuser via PlayStore
These are the steps I followed when I first rooted my phone, however after a while my link2d and something else was causing my apps to crash, and eventually link2sd kept asking for root permission, and superuser would freeze. For about 7 hours last night I spend trying to fix my phone, which I did by doing a factory reset, then restored my stock ROM using CWM, then loading up a stock recovery.img file which I found on here somewhere, and then eventually I got my phone back to normal. By the way when you go through the bootloader and select recovery, when I get onto it, it justs sits there with a disk icon and a red 'X' or something, is this normal? However, want really p***ed me off was that I thought restoring a backup using CWM also restores the recovery and completely removes the CWM. My question is, instead of me going through all this hassle, is there a way I can FULLY backup my phone and then attempt a root without CWM or any other custom recovery? I have already tried the HTC super tool v3, superoneclickroot and another quick root that was advertised on here, and neither of them work.
My outcome would be to simply have root privileges on the stock ROM on my HTC Wildfire S (S-ON) 2.26.401.3, and if and have a full backup of the phone as though it was new (no root, no CWM etc.) and if a problem occurs I can simply restore everything.
Anyone know how to root without wiping all the data from the phone? my phone is completely stock/unroot/locked
rooting will not wipe the phone... unlocking the bootloader will though, which has to be done before rooting.
1.) Unlock bootloader (will wipe your phone if you didn't)
2.) Flash latest TWRP recovery
3.) Boot into recovery
4.) TWRP will prompt you to automatically root should you choose to do so.
Sent from my Nexus 5 using Tapatalk
So I did the lollipop upgrade got root and unlocked my bootloader but I think I used the wifi build to update with but it works fine. However my tablet says there is a new update out and I know it will kill root and recovery but will it matter since I unlocked the bootloader? Update has been sitting there for awhile because I keep putting it off.
If your bootloader is unlocked you can flash any recovery (Cwm, philz or TWRP) via fastboot and then use it to flash supersu zip file from it.
An unlocked bootloader lets you flash unsupported firmware; e.g., another bootloader, custom kernel, recovery or ROM. Don't worry about updating, but expect to have to reflash recovery and re-root the device after pulling down an OTA.
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.