So I was trying to install cyanogenmod on my phone as I was tired of waiting for Sony to update it to lollipop. I've done this on all of my older Samsung phones. So this is what I did:
1: Tried to install CWM using XZU recovery. It restarted my phone but would not boot into recovery mode.
2: Realized I need to root my phone so I rooted it. I have root access in apps except I can't install the binarys in supersu because the stock recovery option does not work and CWM doesn't either.
3. I then thought maybe I need to unlock the bootloader so I unlocked it and tried step 1 again but with the same outcome.
So essentially I am at a point where I can't install the binary in SuperSU due to the recovery being corrupt. I also can't install CWM due to not having the binarys for root installed. Is there away for me to get out of this mess?
Yes I realize I shouldn't have did it in the order that I did but I did it based on a few documentations that I saw that did not state I needed any of that and on past experience on different phones I was able to go straight to CWM.
gizmo1992 said:
So I was trying to install cyanogenmod on my phone as I was tired of waiting for Sony to update it to lollipop. I've done this on all of my older Samsung phones. So this is what I did:
1: Tried to install CWM using XZU recovery. It restarted my phone but would not boot into recovery mode.
2: Realized I need to root my phone so I rooted it. I have root access in apps except I can't install the binarys in supersu because the stock recovery option does not work and CWM doesn't either.
3. I then thought maybe I need to unlock the bootloader so I unlocked it and tried step 1 again but with the same outcome.
So essentially I am at a point where I can't install the binary in SuperSU due to the recovery being corrupt. I also can't install CWM due to not having the binarys for root installed. Is there away for me to get out of this mess?
Yes I realize I shouldn't have did it in the order that I did but I did it based on a few documentations that I saw that did not state I needed any of that and on past experience on different phones I was able to go straight to CWM.
Click to expand...
Click to collapse
Hello,
You need to do the following.
1. Root Your Device.
2. Unlock Boot loader.
3. Download CM12.
4. Open Its Zip And Extract Kernel.
5. Download Flashtool.
6. Use Flashtool To Flash Kernel.
7. Reboot Into Recovery And Flash ROM
Sent from my AO5510 using XDA Premium 4 mobile app
Men_in_black007 said:
Hello,
You need to do the following.
1. Root Your Device.
2. Unlock Boot loader.
3. Download CM12.
4. Open Its Zip And Extract Kernel.
5. Download Flashtool.
6. Use Flashtool To Flash Kernel.
7. Reboot Into Recovery And Flash ROM
Sent from my AO5510 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashtool doesn't see my phone. I know that I have my phone in the right mode because it has the blue LED and I know I have the correct drivers because it shows them in Device Manager as well as I had to put it in this mode to unlock the boot loader in the first place.
Nevermind flashtool randomly saw my phone. Going to try and install the new kernal. Will update
So here is what I finally did to get CM12.
1 I used Sony's flashtool to install the stock image and start over.
2 I then used the SP flashtool to install CWM kernel
3 I then installed CM12 in CWM and all is good
Related
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
benjmiester said:
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
Click to expand...
Click to collapse
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
LetMeKnow said:
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
Click to expand...
Click to collapse
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
benjmiester said:
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
Click to expand...
Click to collapse
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Unlocked bootloader is allowed you to install the custom recovery so you can install the custom ROM, I believed..... You can check this guide out to see if you can setup your fastboot/adb. It is very easy to follow for the beginners, good luck....:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2688891
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Once you unlocked the bootloader you can flash a custom recovery and after that - the sky's the limit.
Flashify works great, and it is a wonderful tool as long as you're able to boot into Android.
My problem with Flashify and Goomanager and TwrpManger is that it saves users from setting up a proper ADB/fastboot connection from PC to tablet.
As long as you can boot Android, these apps are great. But what if you can't? Once the tablet doesn't boot it's so much harder (and often too late) to get the correct drivers installed for ADB and fastboot.
So if you flash your recovery with any of those apps still make sure you have access with ADB and fastboot from your PC.
You will regret it if you don't - I (almost) guarantee it.
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
benjmiester said:
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
Click to expand...
Click to collapse
The instructions in the OP actually say that you have to do a full wipe (Factory Wipe) in TWRP coming from a different rom base. Which would be you unless you had a version of CROMBi-KK installed prior to this.
It's the default selection under the Wipe menu in TWRP. Just do that and then flash the rom and your ok.
Do not use the Factory Reset option from Settings or the Wipe Data option from the BL menu! Do this in TWRP only!
Cool thanks. I figured so because that's the norm with roms on all my phones. Thanks a lot for the help guys. So happy to be get KK running on my new toy!
Just wanted to update. KK 4.4.3 rom flashed and booted in. It's much nicer. The stock was a little laggy, and KK breathed a lot of new life into my ancient single core 1.0 ghz Galaxy S that I use as a music player so I figured it would help make the tab real nice and snappy too. Gotta go now, much fun to be had!!
I decided to root my mom's Xperia E and put CM10 in it. So I began. I first rooted with cydia impactor and put supersu manually and installed binaries. It was successfully rooted. Now when I unlocked my bootloader I faced a bootloop, so I flashed stock ftf and then rooted again. So now I have a rooted and bootloader unlocked xperia e. Then I decided to install cwm. I tried to do it using cmd prompt but everytime it would show <waiting for device> and then nothing happens (I booted in fastboot mode). After that I decided to put zeus kernel. In the download section, confusion started as there were 2 versions, for cwm and TWRP respctively, I tried the cwm one and flashed it using flashtool but then my phone's UI was like gone. I was only able to open settings app. So I decided to flash stock FTF and keep it in stable state for now. So what do I need to do to install cm10?
Thanks in advance
When it says <waiting for device> just follow these steps:
1.Turn off the phone
2.power off button + volume UP
3.wait to finish flash
If it dosn't work reinstall drivers.
AvinabaDalal said:
I decided to root my mom's Xperia E and put CM10 in it. So I began. I first rooted with cydia impactor and put supersu manually and installed binaries. It was successfully rooted. Now when I unlocked my bootloader I faced a bootloop, so I flashed stock ftf and then rooted again. So now I have a rooted and bootloader unlocked xperia e. Then I decided to install cwm. I tried to do it using cmd prompt but everytime it would show <waiting for device> and then nothing happens (I booted in fastboot mode). After that I decided to put zeus kernel. In the download section, confusion started as there were 2 versions, for cwm and TWRP respctively, I tried the cwm one and flashed it using flashtool but then my phone's UI was like gone. I was only able to open settings app. So I decided to flash stock FTF and keep it in stable state for now. So what do I need to do to install cm10?
Thanks in advance
Click to expand...
Click to collapse
Nothing much if you flashed Stock FTF recently then just flash Zues Kernel the CWM one, make sure you have the proper drivers to flash using flashtool.
Then boot up and go into recovery and flash the CM10.zip. Then you will need to flash the CM10 kernel. Its usually inside the ZIP named "boot.img"
I have a Asus ZenFone 2(Z00A)
I was followed [ROM][5.1.1][OFFICIAL]Paranoid Android-L[08/13/2015][Z00A][ZE551ML] to install Paranoid Android-L on my phone. I did it without unlocking the bootloader and I used Tethered Recovery to get into CWM. I did not know that unlocking the bootloader and UN-Tethered Recovery was a must (I'm a noob).
After bricking the phone I tried to unlock the bootloader and then installing TWRP(from http://daritoca.appspot.com/forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547 and here)
But instead I erased the stock recovery.
Now I don't have an OS installed in my phone(since I formatted /system), I have no recovery. On Booting the phone starts fastboot.
I Googled a lot and found this How to Recover a Bricked Asus Zenfone 2 Smartphone. Will I be able to recover my phone by following these steps? i.e.
1) Download the latest Stock ROM from the Asus website for my phone.
2) Copy the downloaded Stock ROM to the folder where I installed ADB.
3) Do a Tethered Recovery to get into CWM(Since I don't have any recovery on my phone) and Apply update from ADB.
4) Reboot
Will this work. I'm currently downloading the latest Stock ROM from the Asus website.
Help Please!
SLOVED
Monget said:
For the recovery you just put your phone into Fastboot ! After you open a cmd in the folder) where is your twrp.img(With shift + right click . And you run the command "fastboot flash recovery twrp.img " Your phone should normally react
Click to expand...
Click to collapse
Problem Solved! I downloaded the StockRom, put it into my memory card and flashed it with Temporary CWM Recovery. Thats it!
Then I rooted my phone using Temporary CWM. Installed Busy Box, Xposed and Restored my backed up apps & system settings via Titanium Backup.
My phone is back to normal.
But I Flashed firmware version 2.20.40.59(latest) which currently doesn't support unlocking of bootloader. I'll just wait then flash Paranoid.
Thanks for your help!:good:
Bootloader of 2.20.40.59 Unlocked
Actually, I just unlocked the bootloader of 2.20.40.59 using One-Click bootloader unlock(http://forum.xda-developers.com/zenfone2/general/tool-one-click-bootloader-unlock-root-t3155884/page1)
sammorrison said:
I have a Asus ZenFone 2(Z00A)
I was followed [ROM][5.1.1][OFFICIAL]Paranoid Android-L[08/13/2015][Z00A][ZE551ML] to install Paranoid Android-L on my phone. I did it without unlocking the bootloader and I used Tethered Recovery to get into CWM. I did not know that unlocking the bootloader and UN-Tethered Recovery was a must (I'm a noob).
After bricking the phone I tried to unlock the bootloader and then installing TWRP(from http://daritoca.appspot.com/forum.x...eral/congrats-to-bootlocker-unlocked-t3138547 and here)
But instead I erased the stock recovery.
Now I don't have an OS installed in my phone(since I formatted /system), I have no recovery. On Booting the phone starts fastboot.
I Googled a lot and found this How to Recover a Bricked Asus Zenfone 2 Smartphone. Will I be able to recover my phone by following these steps? i.e.
1) Download the latest Stock ROM from the Asus website for my phone.
2) Copy the downloaded Stock ROM to the folder where I installed ADB.
3) Do a Tethered Recovery to get into CWM(Since I don't have any recovery on my phone) and Apply update from ADB.
4) Reboot
Will this work. I'm currently downloading the latest Stock ROM from the Asus website.
Help Please!
Click to expand...
Click to collapse
Hello, thank you for using XDA Assist.
For best results, please post your question here:
http://forum.xda-developers.com/zenfone2/help/help-post-questions-instead-making-t2997779
That's a help thread specifically for your device.
You'll receive expert advice there.
Good luck!
Hi,
I'm using lollipop previously and tried to root my device. I tried to follow the instructions on how to root it by unlocking Boot Loader. I accidentally deleted all the system files in recovery mode. Unfortunately, I don't have any back ups. Now my device is just restarting and stuck in Sony logo. I can still boot to recovery mode. I tried to flash the latest ftf but flashing always fail. Is there any way where I can install the OS since in recovery it says that OS is not installed. I'm using TWRP recovery. Many thanks for those who will help. I will really appreciate it.
Cliff0rd said:
Hi,
I'm using lollipop previously and tried to root my device. I tried to follow the instructions on how to root it by unlocking Boot Loader. I accidentally deleted all the system files in recovery mode. Unfortunately, I don't have any back ups. Now my device is just restarting and stuck in Sony logo. I can still boot to recovery mode. I tried to flash the latest ftf but flashing always fail. Is there any way where I can install the OS since in recovery it says that OS is not installed. I'm using TWRP recovery. Many thanks for those who will help. I will really appreciate it.
Click to expand...
Click to collapse
just flash via flashtool
FTF can only be flashed via Flashtools as far as I'm aware it also restores the original stock recovery so you lose your recovery too
Just install Flashmode, Fastboot, and phone drivers (Phone driver can be installed using Sony PC Companion or going to device manager and manually doing it)
Then put your phone into flashmode and then open flashtools select flashmode and then put the ftf file in your directory where it can detect the file usually in documents .flashtool / firmware and then select the file to flash and wait
Don't untick/tick any wipe or not wipe box and just keep pressing yes unless you have a reason to press no
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.