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.
Related
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.
I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But the latest version CWM cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
ANYWAY TO WIPE EVeRUTHING INCLUDES SYSTEM thROUGH BOOTLOADER?
sorry for my bad english
Have you tried to install Full Recovery Mode ?
First Enable USB Debugging and watch if your Device is correctly recognized on you Device Manager .
Search and install the software , for first use i suggest to search some Tutorials about this.
Then you can use the Full Recovery Mode and format / wipe cache and system .
Hey Guys!
I have rooted 3 other GS3's using the method listed here:
http://theunlockr.com/2013/04/02/how-to-root-the-verizon-samsung-galaxy-s-iii-running-android-4-1-2/
All other roots worked great! I was able to flash TWRP (I realize that the specific tutorial above calls for CWM instead of TWRP) and then install a CyanogenMod ROM. However, this time it did not go well.
I forgot to enable USB debugging before flashing VRALEC the first time, and when I went to run TWRP (2.7.0 for d2vzw) I realized that it did not mount the file system I thought that this was unusual and then realized that I need to enable USB debugging. I completely unrooted the phone and installed stock recovery and rom (VRBMF1, Android 4.1.2) once this was done I figured that I would go back to a personally tried and true version of TWRP (2.5.0 for d2vzw). At this point I was careful to ensure that I enabled USB debugging before proceeding with the root process.
With TWRP 2.5.0 I was prompted with a password. This befuddled me and upon some reading on the forums I came across a solution that worked for others but NOT ME. (Essentially you clear the cache and to a factory reset 3x in TWRP recovery and it will stop prompting you for the password and mount your file system correctly). For me I was unable to mount the cache for dalvic-cache to wipe it and factory reset does nothing.
I have rooted and unrooted my phone approx seven times trying different versions of TWRP, CWM, and even trying to use a seperately downloaded VRALEC file just in case if mine had an error.
I also came across this thread (below) and it did look somewhat promising however it is for android 4.2.1 and I don't want to mess up my phone any more than it already was. I am getting similar (not exactly the same) errors in my TWRP. I also made sure to use the same bootloader that I used on other 4.1.2 android systems in addition to using the d2vzw version of TWRP (It is for this reason that I am not sure that flumpster's comment applies to me). I figured that I would include this information just in case it was helpful:
http://forum.xda-developers.com/showthread.php?t=2228447
Any Ideas? I am really looking forward to trying Liquid Smooth 3.0!
Just a quick addition: I was able to use Casual's root method however I am still running into the password prompt in recovery and 3 wipes is not getting rid of that password prompt..
Thanks in advance for any help!
Last night i tried to root my phone. I installed twrp, supersu, and everything needed, but supersu was not working and put my phone in a bootloop. I got out of that and tried to restore my phone to before i did anything, but it wouldnt let me. I then stupidly installed crDroid, which worked, but now i cant get any cellular service, which defeats the purpose of having a cell phone. I wiped my phone and tried to install a stock firmware multiple times that was correct for my phone, but that didnt seem to work in twrp either. I tried to adb sideload, but i'm too stupid to even get the right file name for the stock firmware? i need seirous help so i can have my phone back. I dont even want to root anymore.
https://www.youtube.com/watch?v=bMan9cIuPWM
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
follow this or
http://forum.xda-developers.com/201...m-stock-motorola-6-0-1-rom-optimized-t3355938
bwrona91 said:
Last night i tried to root my phone. I installed twrp, supersu, and everything needed, but supersu was not working and put my phone in a bootloop. I got out of that and tried to restore my phone to before i did anything, but it wouldnt let me. I then stupidly installed crDroid, which worked, but now i cant get any cellular service, which defeats the purpose of having a cell phone. I wiped my phone and tried to install a stock firmware multiple times that was correct for my phone, but that didnt seem to work in twrp either. I tried to adb sideload, but i'm too stupid to even get the right file name for the stock firmware? i need seirous help so i can have my phone back. I dont even want to root anymore.
Click to expand...
Click to collapse
When you're rooting stock, remember do not wipe cache and dalvick partitions after root and before first boot
bwrona91 said:
Last night i tried to root my phone. I installed twrp, supersu, and everything needed, but supersu was not working and put my phone in a bootloop. I got out of that and tried to restore my phone to before i did anything, but it wouldnt let me. I then stupidly installed crDroid, which worked, but now i cant get any cellular service, which defeats the purpose of having a cell phone. I wiped my phone and tried to install a stock firmware multiple times that was correct for my phone, but that didnt seem to work in twrp either. I tried to adb sideload, but i'm too stupid to even get the right file name for the stock firmware? i need seirous help so i can have my phone back. I dont even want to root anymore.
Click to expand...
Click to collapse
For resetting to stock goto
1)recovery
wipe menu --> advanced tick all the options except sdcard
Then reboot to bootloader
Flashing Firmware
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
here you can find the firmware and download it(size will vary but greater than 600Mb).If you cannot find firmware just pm me and i will give you the correct link.
Procedure for flashing -->
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
will installing super su use version
https://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip?retrieve_file=1
You cannot just flash SuperSU on stock marshmallow, it will boot loop you. What you need to do is, go into advanced tab in twrp and enter the terminal and write this before flashing SuperSU zip
echo SYSTEMLESS=true>> /data/.supersu
This will move root to data and avoid the boot loop
http://forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113
Use the supersu version attached in this link.
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.