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.
Related
Ok I have a massive problem here. Last night I decided to use the 1 click universal root app to root my phone and flash it to get CM.
I downloaded the app did the root, downloaded clockworkmod then did a clockworkmod recovery. After that finished i was given a pre-root option to backup my phone and wipe data/storage.
I only chose back up my phone. My nexus one then rebooted and proceeded to backup my phone then it went to install CM 6 RC2.. After this had finished it then rebooted and went to the multicoloured animation where the colours ceom from the left and right..
Here it would continuously loop and never do anythign else. With this I pulled the battery and loaded into recovery where I was in ClockworkMod. I then proceeded to use the recovery and as it was doing the recovery it just froze and the progress bar nor any words would come up.
From here I pulled the battery again did a soft/hard reset but it would hang on the loading animation again. I then did a wipe data/clean option and now it just hangs on the X logo.
On my sdcard I still have the clockworkmod folder with the backup, nandroid, system and all the other files as well. Vodafone Australia have no stock of the Nexus One at all and won't be getting anymore in since it's a finished product
I barely have any cash for a new phone and need to know asap what to do to fix this problem! If anyone can help!
When you installed Cyanogen CM6 did you install the proper baseband also or you just didn't write it down for us? If you had 2.2 on the phone before you rooted the baseband is ok for CM6.
Did you try hooking your phone with USB and try if ADB interface works? If your computer sees the phone via fastboot?
IF fastboot works, you could always restore your stock recovery and install a stock FRF91. (And then try again with CM6, this time installing the proper baseband AND WIPING like you should when installing CM6!!)
When installing custom ROMs always read the install instructions whole first then install.
http://forum.cyanogenmod.com/topic/...y-crap-its-full-of-awesome-v600-rc2-07252010/
I got my Motorola DEFY recently, and I'm new to Android, but I want to install stuff that needs root. However, I want to be able to restore everything to how the phone was when I got it, should the need arise.
I successfully rooted using z4root and installed ROM manager, at which point I did some googling and discovered that if I install ClockworkMod Recovery it's not easy to revert back to the normal recovery console. It's not that hard, but I understand it requires an image of the original recovery console. I thought that the backup option on ROM Manager would help, but it requires ClockworkMod Recovery to be installed.
So the question is, can the recovery console be backed up prior to installing ClockworkMod Recovery, or alternately can the entire phone state be backed up, including the recovery console and the rest of the ROM.
Help would be appreciated. Thanks!
If you install CWM Recovery you can do a nandroid backup of your stock ROM so that you can revert later. You don't need to worry about a stock recovery image because once you restore the backup you made, the custom recovery will be overwritten with the stock one with every reboot.
Hello
Long story short.
I rooted my Alcatel one touch Fierce 2 with Kingroot.
I swapped out the KingUser with Supersu.
I moved supersu to the system with system app mover
I used flasify to backup my kernel and my current recovery.
I test flashify today to restore my current recovery.
It worked. It did something and rebooted my phone into recovery mode.
same as power and volume up
i did select in recovery mode wipe data/factory reset
It worked different this time.
Instead of wiping data and cache partition and then loading factory backup......
My screen said
data wipe complete
cache wipe complete
and then it was finished.
it didnt continue to reload factory and reboot like before.
I selected Reboot Now.
Took a min but my phone booted back up with the flashify backup installed.
I Think it looks that way anyhow. I need to do some more test.
So heres the questions i have. and if you can answer or point me to the correct threads thanks in advance.
I have the sideload option on this phone.
My ADB works correctly and ADB Devices shows "Sideload" with my phone connected in sideload mode.
This is good. It means i can recover using ADB and sideload.
But i need a good file to actually sideload.
So how do i create a backup of my phone i can use for sideload.
Can i use the flashify boot.img and recovery.img to do that somehow.
The good thing is currently if i run system restore it works and i still have root when it comes back up.
The good thing is as long as i can run flashify i can reload my phone backups.
flashify is good cause it dont need unlocked bootloader to flash phone only root.
The bad things.
This phones bootloader is locked.
Because of that I dont think you can load CWM or TWRP.
If i fry the android system and cant run flashify how do i load my backups.
As long as i can get the phone to boot in recovery and able to use Sideload i can make ADB Sideload connection and somehow recover.
Cant we also use sideload to install CWM on this phone.
I sure wish it had CWM,
Found My own answer
I guess i found the answer to my own question.
Flashify isnt a full backup.
I ended up finding Online Nandroid tool.
Made a CWM Backup of my phone.
Now im off to make a loadable sideload from the CWM backup.
Recently i bought this device, i was able to root it using kingroot, yesterday i tried installing the xposed framework, since i didn't have custom recovery i saw a tutorial in youtube explaining how to install the framework without the need of custom recovery (it was a huge mistake), using a combo of busybox and the terminal emulator, the result was a bootloop, i am able to enter the factory recovery but even after wiping the data/cache to factory settings its still stuck on the bootloop. Since i dont have custom recovery i am kinda stuck and without pc at the moment its starting to seem like a lost case, the factory recovery as the option to enable adb, i found a tutorial online but i don't understand anything about batch files and it all seems kinda confusing to me. In the past i was able to unbrick my old phones using stock roms, using odin if i recall right, but since the device is fairly new i am unable to find a stock rom. My questions are,
can i use odin again using a 5.1.1 lollipop normal (rom)?
Is there an easier to follow tutorial on how to use the adb fuction?
Is there a way to instal cwm even in bootloop without the use of adb? Since wiping dalvik cache and fix permissions should fix the problem.
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.