Related
this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.
I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem
k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh
distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol
Where in root explorer do i need to rename
Where in root explorer do i rename it
plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.
chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.
Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways
I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol
I originally posted this method at AddictiveTips. The method I posted there is targeted at everyone including the absolute beginners and I have also included instructions there for setting up the required tools, and for reverting back to the original recovery and boot image in case anything goes wrong. All external credits should be given to that guide (it does link back to this thread). Here is the link: How To Root Nexus 4 and Install ClockworkMod Recovery on it.
To my knowledge, this is the first confirmed working rooting method for Nexus 4 posted here at XDA. Though my knowledge is limited, so please correct me if I am wrong.
UPDATE: There is an official ClockworkMod recovery for Nexus 4 now available directly by Koush, so this should all be easy as pie now and you can now safely install CWM too. I am updating the CWM method with the updated instructions.
This method requires an unlocked bootloader. You can find instructions for unlocking it at XDA, or at the AddictiveTips guide linked above (the link to the bootloader unlock guide is in the requirements section there).
UPDATE 2: If your device does NOT get wiped after unlocking the bootloader, fret not. While this isn't expected behavior, several users have experienced the same on the Nexus 4. This could be due to some error at Google's end, but unlocking still works perfectly fine.
That said, let's get on with rooting and flashing CWM.
ClockworkMod Recovery Method:
Download the latest official ClockworkMod recovery from CWM website and rename it to recovery.img
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Download the recovery flashable SuperSU package with Busybox and transfer it to your phone's internal SD card.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Enter this command in a command prompt to flash the ClockworkMod recovery (making sure you are in the directory where you downloaded the recovery file):
Code:
fastboot flash recovery recovery.img
OR
If you simply want to root without flashing a custom recovery and want to stick to your stock recovery, simply boot this recovery once using this command:
Code:
fastboot boot recovery.img
If you flashed the recovery in the previous step, you can now boot into recovery by pressing volume-up or volume-down twice to select the recovery option, and then the power button to enter it. If you simply booted into the recovery file without flashing it in the previous step, you should already be in recovery now.
Once in recovery, take a backup to be on the safe side.
Flash the downloaded SuperSU and busybox package zip file from recovery.
Clear cache and dalvik cache just in case (not required but won't hurt).
Reboot the device.
ADB and Insecure Boot Image Method:
Grab the insecure boot image from this thread.
Also download these root files. This package includes the latest SuperSU 0.98, latest su binary that comes with it, and working busybox (not sure if latest).
Extract the contents of the downloaded zip file to your computer.
Enable Android Debugging from Settings > Developer Options. (If you can't find developer options, go to 'About' and tap 'Build number' seven times.)
Connect the device to your computer via USB, and install the required drivers.
Reboot into fastboot/bootloader:
Code:
adb reboot bootloader
You can also power off the phone and then use power + volume-down key combination to get into bootloader.
Unlock the bootloader if you haven't done so already. WARNING: This command will wipe all data on your device.
Code:
fastboot oem unlock
Get back into bootloader mode and boot into the downloaded insecure boot image:
Code:
fastboot boot boot.img
Don't worry, this will not replace your existing boot image and will only boot from the insecure one once.
If it does NOT work for you and you get stuck in a boot loop, simply reboot your phone into bootloader and use the above command again. Some users had issues with booting from it the first time, but a second attempt worked.
Once booted into Android successfully using the insecure boot image, simply enter these commands one by one in command prompt (making sure you are in the directory where you downloaded the files):
Code:
adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
Reboot your device.
You will now have root access. Tested and confirmed working by Stryder5 and many others.
Credits:
Stryder5 for testing, confirming, tipping me about working CWM, providing the required drivers, and helping others on the thread. :highfive:
Harry GT-S5830 for the insecure boot image.
fkrone for his recovery revert disabler script and his unofficial working CWM before an official one became available.
Kstarz for posting this same recovery method with his own working CWM in this thread before an official one was out.
evaradar for informing about the release of official ClockworkMod recovery.
Koush for developing ClockworkMod recovery.
Chainfire for developing SuperSU.
Everyone else on this thread for testing, providing feedback and hitting the 'THANKS' button. =)
I have tried my best to give everyone the due credit but if I have missed out on anyone, please do remind me.
Yep, worked like a charm. Got Titanium running and restored all my apps
Btw, check your PM.
Checked...thanks. =) Added the links.
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
jshaw06 said:
stem/bin/sh: su: can't execute: Permission denied
that is what i always get when i put in the "su"--permision denied
Click to expand...
Click to collapse
You need to boot the unsecure boot.img first.
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
HQRaja said:
BTW can you confirm me the insecure boot.img you used? I just provided the link to the thread by Harry GT-S5830 but there were multiple ones posted in that thread, so I'm thinking of adding the direct link to the one confirmed working.
Click to expand...
Click to collapse
I'm pretty sure I used the one Harry GT-S5830 provided.
I used the one in the OP of that thread.. is there a different one I'm supposed yo use?
Sent from my SGH-T999 using Tapatalk 2
---------- Post added at 06:41 AM ---------- Previous post was at 06:23 AM ----------
It works
Sent from my SGH-T999 using Tapatalk 2
jshaw06 said:
It works
Click to expand...
Click to collapse
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Stryder5 said:
Glad to hear
Did you install the OTA before doing this? I gained root before installing the OTA.
Click to expand...
Click to collapse
No issues with installing the OTA after root?
Edit: Just noticed in your sig that you did not install the update.
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
jshaw06 said:
I installed after ota
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You mean you gained root after you installed the OTA?
---------- Post added at 01:12 AM ---------- Previous post was at 01:11 AM ----------
apzalo said:
No issues with installing the OTA after root?
Click to expand...
Click to collapse
I gained root, but haven't installed the OTA yet.
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Yes sorry gained root after OTA
Sent from my SGH-T999 using Tapatalk 2
Elemenopee said:
when I boot the boot.img. It rebooted and got stuck at the nexus boot animation for a long time. Does it suppose to do that?
Click to expand...
Click to collapse
Nope, it isn't. Try again...it's safe to try as many times as you want since we're not flashing the boot image; merely booting from it, which is temporary and doesn't last after reboot. Hope it works on the next try.
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Ngo93 said:
After step 8 we boot up the phone normally and then start running those adb commands? I'm assuming that's what you mean by "Once booted into Android successfully..." right? Sorry if it's an obvious question, just making sure!
Click to expand...
Click to collapse
Step 8 itself will boot up the phone normally into Android, just using that insecure boot image instead of the stock one. And yes, you then just start entering those adb commands. =)
0.0 said:
quick question to ease my mind: if i needed to return this device for warranty purposes, how would i revert all of this back to stock? i know its something to do with the stock factory image, or am i wrong?
Click to expand...
Click to collapse
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
HQRaja said:
Best way would be to grab a stock factory image and flashing it. I recently wrote a post on the portal with the links: http://www.xda-developers.com/android/android-4-2-images-for-galaxy-nexus-nexus-7-4-and-10/
The method can be found at the factory images download page, and is as easy as extracting the image and running the included .bat file while your phone is connected to PC in fastboot mode.
Click to expand...
Click to collapse
so i extract the "occam-jop40c-factory-cd3dc140.tgz" file, then double-click the "flash-all.bat" file?
After upgrading to 3.0, follow the steps (I recommend to use FORCE UPGRADE using Vol + + Vol - + Power. But be sure to save your important data if you are not using SDCARD):
1. Download the boot image file below, correspond to your firmware version. (I've made this boot.img unlocked. I'm not responsible for the bootloop of your phone)
2. Download and install HiSuite. (Optional for Windows 8 and above).
3. Flash the boot image file.
- Connect your device via data cable into your pc.
- Choose PC Suite (HiSuite) from your device.
- Download and extract ADB Flash Tools.
- Copy the boot image file correspond to your firmware inside ADB Flash Tools folder.
- Run cmd.exe:
- Type adb reboot bootloader
- Type fastboot flash boot BOOT_EMUI3.0_XXX_UNLOCKED.img (XXX is the number correspond to your firmware)
- Type fastboot reboot
4. Root using iRoot or Kingo Android Root.
5. Download and install busybox from playstore.
6. Remove set_immutable.list using terminal emulator.
Type in the terminal emulator:
Code:
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
lsattr
(Enter after each line...it's LASTTR with an L not a capital i)
You are fully (100%) rooted.
1. BOOT_EMUI3.0_616_UNLOCKED.img
2. BOOT_EMUI3.0_615_UNLOCKED.img
3. BOOT_EMUI3.0_613_UNLOCKED.img
4. BOOT_EMUI3.0_609_UNLOCKED.img
5. BOOT_EMUI3.0_619_UNLOCKED.img
6. BOOT_EMUI3.0_620_UNLOCKED.img
7. BOOT_EMUI3.0_621_UNLOCKED.img
8. BOOT_EMUI3.0_623_UNLOCKED.img
Good luck!
After flashing boot 608.img true adb phone won't reboot...stop at huawei logo and just blinking red,green,red...wrong boot.img
Sent from my HUAWEI P7-L10 using Tapatalk
Me too
gregysk said:
After flashing boot 608.img true adb phone won't reboot...stop at huawei logo and just blinking red,green,red...wrong boot.img
Sent from my HUAWEI P7-L10 using Tapatalk
Click to expand...
Click to collapse
mikesa said:
Me too
Click to expand...
Click to collapse
Did you flash from 133?
I came from: 133 then update B602 update.zip and B609 ota update.zip and B609 full update. (I tired anno this boot image on B602 but same problem, stop at Huawei logo and blinking led)
U guys need to flash stock boot for 609... do not use chinese boot.img
meilbox said:
U guys need to flash stock boot for 609... do not use chinese boot.img
Click to expand...
Click to collapse
Ok mate but @majcomtech explain in first post "how to.."get full root,isn`t he?He put download link to chinese b.608 img,isn`t he?I just followed his steps,no more no less...
and u have bricked ur device... isnt it... to unbrick try to flash stock boot from 609 if u r able to start fastboot...
meilbox said:
and u have bricked ur device... isnt it... to unbrick try to flash stock boot from 609 if u r able to start fastboot...
Click to expand...
Click to collapse
I didnt brick my device,i just went to some kinfd of bootloop because of bad or wrong boot.img.Shutdown phone,start phone in cwm recovery and restored backup and thats it,Im back on start,wait for better solution to get full root or how to delete immutable.list without he return back after reboot.Im not dev but I think that these problem is in ramdisk and that is not my area
gregysk said:
Ok mate but @majcomtech explain in first post "how to.."get full root,isn`t he?He put download link to chinese b.608 img,isn`t he?I just followed his steps,no more no less...
Click to expand...
Click to collapse
Hey dude do not angy!
I succesfuly flash BOOT_EMUI3.0_STOCK_B608.img but cant remove pernament set_immutable list!
But I flash boot_HRT_EMUI3.0.img and my ROM FULL (100%) ROOTED!
So:
After upgrading to 609 using the full version firmware, follow these steps:
1. Download "boot_HRT_EMUI3.0.img" - https://drive.google.com/folderview?...Tg&usp=sharing
(Credits to the Devs and to natorus87)
2. "boot_HRT_EMUI3.0.img" (fastboot flash boot boot_HRT_EMUI3.0.img)
3. Root using Root Genius (ENG/CN version).
4. Download and install busybox.
5. Remove set_immutable.list using terminal emulator, type in terminal emulator:
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
lsattr
(Enter after each line...it's LASTTR with an L not a capital i)
You are fully (100%) rooted.
Good luck!
gregysk said:
After flashing boot 608.img true adb phone won't reboot...stop at huawei logo and just blinking red,green,red...wrong boot.img
Sent from my HUAWEI P7-L10 using Tapatalk
Click to expand...
Click to collapse
did you flashed your L10 with L-07-L10 3.0 firmware? if yes, then revert back to fully 2,3 environment, not using flashing imgs.
ibeqa said:
Did you flash from 133?
Click to expand...
Click to collapse
no need to flash 133. i'm using 136 going to 609 full firmware.
mikesa said:
I came from: 133 then update B602 update.zip and B609 ota update.zip and B609 full update. (I tired anno this boot image on B602 but same problem, stop at Huawei logo and blinking led)
Click to expand...
Click to collapse
problem exists if your 2.3 is not a fully 2.3 environment. you reverted your phone back from 604 to 2.3 using flashing imgs, right?
mikesa said:
Hey dude do not angy!
I succesfuly flash BOOT_EMUI3.0_STOCK_B608.img but cant remove pernament set_immutable list!
But I flash boot_HRT_EMUI3.0.img and my ROM FULL (100%) ROOTED!
So:
After upgrading to 609 using the full version firmware, follow these steps:
1. Download "boot_HRT_EMUI3.0.img" - https://drive.google.com/folderview?...Tg&usp=sharing
(Credits to the Devs and to natorus87)
2. "boot_HRT_EMUI3.0.img" (fastboot flash boot boot_HRT_EMUI3.0.img)
3. Root using Root Genius (ENG/CN version).
4. Download and install busybox.
5. Remove set_immutable.list using terminal emulator, type in terminal emulator:
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
lsattr
(Enter after each line...it's LASTTR with an L not a capital i)
You are fully (100%) rooted.
Good luck!
Click to expand...
Click to collapse
no prob. atleast you found another option and you share it also. i was not able to try boot-hrt 'coz after using the BOOT_EMUI3.0_STOCK_B608.img it works fully rooted immediately. nice to hear that. :good:
majcomtech said:
did you flashed your L10 with L-07-L10 3.0 firmware? if yes, then revert back to fully 2,3 environment, not using flashing imgs.
Click to expand...
Click to collapse
No,I update my previus B.602 with B.609 true local update(update.app).Ok guys,I will try tomorow one more time booth metods.Regards..
Sent from my HUAWEI P7-L10 using Tapatalk
the link to "boot_HRT_EMUI3.0.img" isn't working, could you link source (thread) please? thanks.
bertolehm said:
the link to "boot_HRT_EMUI3.0.img" isn't working, could you link source (thread) please? thanks.
Click to expand...
Click to collapse
https://drive.google.com/folderview?id=0BzAbvTCMo2YbdkNFTWtycm1ybTg&usp=sharing#list
can someone proof the method by mikesa??
which version of root genius did you take?
tested and works on P7-L10 B609 full update (~1,21GB)..
it is highly recommended to keep the king user root app..
i took the root genius version 1.8.7 (en) and flashed the boot_hrt_emui3.0.img..
works like charm..
thanks mikesa for this tipp..
and thanks for the devs of the boot.img
greetz
for me also with the boot_HRT_EMUI3.0.img and lastest rootgenius cn
everything worked like a charm ;p
thanks for the link
did you go back to stock kernel after meilbox?
Q&A for [Recovery][CWM][TWRP][UB]Flashable Recovery For Xperia ZR
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Recovery][CWM][TWRP][UB]Flashable Recovery For Xperia ZR. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
NOOB here.. all the threads says just flash the recovery TWRP using recovery mode.
the thing is how do I get into recovery mode on my Xperia ZR in the first place.. rebooting using power and volume down button opens SAFE mode..
please help..
also, TWRP Manager doesn't list Xperia ZR C5502 in the device list. (It has Xperia Z C5502 though)..
can i flash TWRP for Xperia Z(yuga) on my Xperia ZR(DOGO)??
please help.. thanks in advance...
psawardekar said:
NOOB here.. all the threads says just flash the recovery TWRP using recovery mode.
the thing is how do I get into recovery mode on my Xperia ZR in the first place.. rebooting using power and volume down button opens SAFE mode..
please help..
also, TWRP Manager doesn't list Xperia ZR C5502 in the device list. (It has Xperia Z C5502 though)..
can i flash TWRP for Xperia Z(yuga) on my Xperia ZR(DOGO)??
please help.. thanks in advance...
Click to expand...
Click to collapse
If you have no recovery installed, there is no recovery mode bro.. DON"T use power button but go to general section and choose a pre-rooted ROM for your phone and recovery will/should be pre-installed.. after having recovery installed, to get to recovery, reboot phone and at the sony screen a green/pink led will show and you push VOL-UP and that will get you to recovery..
hagar006 said:
go to general section and choose a pre-rooted ROM for your phone and recovery will/should be pre-installed..
Click to expand...
Click to collapse
Okaaay... so in short, you mean to install a custom rom in the first place.. (wipe off everything :crying: )
where do i get this pre-rooted ROM?? could't find it anywhere in XDA.. and it wont require custom recovery to flash it??
basically, the thing is; Im running stock sony Lollipop 10.6.A.0.454 firmware on Xperia ZR. rooted using kingroot.
and Im missing Xposed frameworks badly.. :crying: :crying: earlier the installation was simple with kitkat. however with lollipop, xposed needs to be flashed since its a alpha release.
thats the only reason i need a recovery. I have the TWRP recovery.img for my phone but flashing it is a problem. cant use Flashify also. doesnt work.(gives error: Partition not found)
can you suggest any other simple way to tackle this? using fastboot or ADB?
Place the recovery.img to your phone internal storage and use adb or emulator commands to install to your Fota:
Su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Go to play store and get android terminal emulator (free) and run the above commands.. Press enter after su and grant root rights and then do the rest of the command and press enter again.. Of all goes well, you'll have recovery..
Sent from my Xperia Z using XDA Forums Pro
hagar006 said:
Place the recovery.img to your phone internal storage and use adb or emulator commands to install to your Fota:
Su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Go to play store and get android terminal emulator (free) and run the above commands.. Press enter after su and grant root rights and then do the rest of the command and press enter again.. Of all goes well, you'll have recovery..
Sent from my Xperia Z using XDA Forums Pro
Click to expand...
Click to collapse
Didn't work
Was typing in Terminal Emulator, Xperia ZR C5502, stock Android 5.0.2, rooted, locked bootloader
Brembol said:
Didn't work
Was typing in Terminal Emulator, Xperia ZR C5502, stock Android 5.0.2, rooted, locked bootloader
Click to expand...
Click to collapse
Try dual recovery for stock by xenius9.. Should be in his CM12 thread in general section.. Or dual recovery by NUT.. comes with installer or flashable zip.. Look in the cross device section and you will find
Sent from my ZR
hagar006 said:
Try dual recovery for stock by xenius9.. Should be in his CM12 thread in general section.. Or dual recovery by NUT.. comes with installer or flashable zip.. Look in the cross device section and you will find
Sent from my ZR
Click to expand...
Click to collapse
The problem is that I have neither computer (broken), nor recovery. Is there any other way to install recovery (CWM or TWRP) without computer?
Brembol said:
The problem is that I have neither computer (broken), nor recovery. Is there any other way to install recovery (CWM or TWRP) without computer?
Click to expand...
Click to collapse
Yes but the problem is your locked boot loader.. If un locked the emulator would do the job.. But locked, you need to get dual recovery from NUT (with computer for the installer).. But to unlock your boot loader you need computer so you can lock again.. Or a already working recovery.. Sorry mate, I know of no other way..
I've been thinking a little.. Take a look at nut's dual recovery installer and see of there is a way to download to your phone and install using emulator.. Should work.. I think
Sent from my ZR
Haven't found any instruction, which I can understand and tells how to install recovery without PC in [NUT]'s thread. I think it's easier to wait and install using computer. Still thanks for help and sorry for your time
Brembol said:
Haven't found any instruction, which I can understand and tells how to install recovery without PC in [NUT]'s thread. I think it's easier to wait and install using computer. Still thanks for help and sorry for your time
Click to expand...
Click to collapse
If you have root ... download from playstore:
Terminal Emulator
Root Browser
Download the windows recovery installer from here http://forum.xda-developers.com/showthread.php?p=46216491
Steps:
1. unzip the windows installer
2. with root browser :
- go to folder
/data/local/tmp/
-create a new folder called recovery
So you have this path: /data/local/tmp/recovery
- from the unziped windows installer put the following files into the folder you created:
-> ric , charger , chargemon.sh , dualrecovery.sh , busybox , recovery.twrp.cpio.lzma , recovery.cwm.cpio.lzma , supersu.sh
If you have all those files in the folder... Klick on them (in root browser) and change permissions of all those files to rwxrwxr-x
Then go to terminal emulator and type:
su -c /system/bin/ls -la /data/local/tmp/recovery/chargemon
And after that:
su -c /data/local/tmp/recovery/supersu.sh
And then:
su reboot recovery
Then you should have a recovery installed without pc
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
If you have root ... download from playstore:
Terminal Emulator
Root Browser
Download the windows recovery installer from here http://forum.xda-developers.com/showthread.php?p=46216491
Steps:
1. unzip the windows installer
2. with root browser :
- go to folder
/data/local/tmp/
-create a new folder called recovery
So you have this path: /data/local/tmp/recovery
- from the unziped windows installer put the following files into the folder you created:
-> ric , charger , chargemon.sh , dualrecovery.sh , busybox , recovery.twrp.cpio.lzma , recovery.cwm.cpio.lzma , supersu.sh
If you have all those files in the folder... Klick on them (in root browser) and change permissions of all those files to rwxrwxr-x
Then go to terminal emulator and type:
su -c /system/bin/ls -la /data/local/tmp/recovery/chargemon
And after that:
su -c /data/local/tmp/recovery/supersu.sh
And then:
su reboot recovery
Then you should have a recovery installed without pc
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Didn't work
After su -c ... /supersu.sh phone rebooted and worked normally. When "Sony" screen appears, LED doesn't work
Brembol said:
Didn't work
After su -c ... /supersu.sh phone rebooted and worked normally. When "Sony" screen appears, LED doesn't work
Click to expand...
Click to collapse
have you set the rights completely?
is your root working properly?
have you any log from terminal rmulator for me?
Sent from my C2105 using XDA Free mobile app
SdtBarbarossa said:
have you set the rights completely?
is your root working properly?
have you any log from terminal rmulator for me?
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
I have set the permissions, root works properly.
In "su -c ... chargemon" I wrote "chargemon.sh" instead of "chargemon", because Terminal Emulator said that there was no such directory.
After "su -c ... /supersu.sh" Terminal Emulator said something about checking recovery...
Sorry, can't say what writes Terminal Emulator after "su -c ... supersu.sh". Phone reboots too fast :banghead:
Brembol said:
I have set the permissions, root works properly.
In "su -c ... chargemon" I wrote "chargemon.sh" instead of "chargemon", because Terminal Emulator said that there was no such directory.
After "su -c ... /supersu.sh" Terminal Emulator said something about checking recovery...
Sorry, can't say what writes Terminal Emulator after "su -c ... supersu.sh". Phone reboots too fast :banghead:
Click to expand...
Click to collapse
Hm... If you want install teamviewer from playstore and i will look into it
Sent from my Xperia T using XDA Free mobile app
New to root
Hi, I'm quite new to root. Can you tell me how to flash custom recovery???
Android4Lyfeee said:
Hi, I'm quite new to root. Can you tell me how to flash custom recovery???
Click to expand...
Click to collapse
It's not really that complicated but it depends on if you have locked bootloader and already rooted or not, what firmware are you on.. If your bootloader is locked, go to cross device section and download TA backup so you can back up your keys for locking your bootloader again..if you have unlocked bootloader, things are simpler.. Let me know and I'll give you a step by step tutorial..
Sent from my ZR
hagar006 said:
It's not really that complicated but it depends on if you have locked bootloader and already rooted or not, what firmware are you on.. If your bootloader is locked, go to cross device section and download TA backup so you can back up your keys for locking your bootloader again..if you have unlocked bootloader, things are simpler.. Let me know and I'll give you a step by step tutorial..
Sent from my ZR
Click to expand...
Click to collapse
My bootloader is locked, but I am rooted. I'm also running Android 5.0.2 Lollipop right now.
Sent from my C5502 using Tapatalk
Android4Lyfeee said:
My bootloader is locked, but I am rooted. I'm also running Android 5.0.2 Lollipop right now.
Sent from my C5502 using Tapatalk
Click to expand...
Click to collapse
Ok.. Go to the cross device section and download dual recovery installer by NUT.. Extract the installer to your desk top, make sure you have debugging checked on your phone, connect your phone to pc with usb, go to dual recovery folder and click the .bat according to your root ie superuser or supersu. Follow the instructions and you have working recovery.. Please note, this will not work with kingroot.. Horrible app anyway..
Sent from my ZR
hagar006 said:
Ok.. Go to the cross device section and download dual recovery installer by NUT.. Extract the installer to your desk top, make sure you have debugging checked on your phone, connect your phone to pc with usb, go to dual recovery folder and click the .bat according to your root ie superuser or supersu. Follow the instructions and you have working recovery.. Please note, this will not work with kingroot.. Horrible app anyway..
Sent from my ZR
Click to expand...
Click to collapse
I rooted with Kingroot, but I changed it to SuperSU. Is this okay?
EDIT: Wow, thanks, it worked!
Sent from my C5502 using Tapatalk
Hello, has anyone managed to root the newest b839 version? And if so how did you do it? Sorry for the noob question.
hello I did by TWRP recovery and flashing SuperSU 49 then you delete the immutable.list
Enviado desde mi HUAWEI P7-L10 mediante Tapatalk
Honer6000 said:
Hello, has anyone managed to root the newest b839 version? And if so how did you do it? Sorry for the noob question.
Click to expand...
Click to collapse
1. Only flash TWRP 2.8.7.0 ( http://forum.xda-developers.com/asce...overy-t3160130 )
2. Install BusyBox ( https://play.google.com/store/apps/d....busybox&hl=sr )
3. flash SuperSu with TWRP ( https://download.chainfire.eu/696/Su...etrieve_file=1 )
4. install Terminal Emulator ( https://play.google.com/store/apps/d...roidterm&hl=sr)
5. Remove set_immutable.list using terminal emulator.
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
lsattr
PM: (Enter after each line...it's LASTTR with an L not a capital i)
You are fully (100%) rooted.
set_immutable can be be deleted with a file explorer with root access easily as well.
rodlane said:
set_immutable can be be deleted with a file explorer with root access easily as well.
Click to expand...
Click to collapse
That's right. I've wiped with X-plore app
To flash recovery you need the bootloader to be unlocked, don't you?
I tried several times on the huawei website to get an unlock code for the bootloader, but it keeps telling me "Sorry, you must use a phone account to submit this application."
klaudyuxxx said:
To flash recovery you need the bootloader to be unlocked, don't you?
I tried several times on the huawei website to get an unlock code for the bootloader, but it keeps telling me "Sorry, you must use a phone account to submit this application."
Click to expand...
Click to collapse
Try this
Code:
http://forum.xda-developers.com/ascend-p7/general/unlock-bootloader-huawei-ascend-p7-l10-t2830641
Maxi_69 said:
Try this
Code:
http://forum.xda-developers.com/ascend-p7/general/unlock-bootloader-huawei-ascend-p7-l10-t2830641
Click to expand...
Click to collapse
Thanx, but I'm on B839. Going way back to B121/126 is not an option....