[RECOVERY] ClockworkMod Touch v6.0.4.6 - One (M7) Original Android Development

Use Rom Manager for best results when backing/restoring...
Installation:
Inscrutions can be found here @ http://www.techgeekal.com/2013/03/1...ckworkmod-touch-recovery-v6-0-2-8-on-htc-one/(outdated)
Unlock bootloader at http://www.htcdev.com/bootloader/
Make sure fastboot is unchecked in power options and turn phone completely off
Boot into HBOOT then Fastboot
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
OR
Flash via Rom Manager(must have root already).
Video Tutorials:
How To Unlock The Bootloader EASIEST Method - https://www.youtube.com/watch?v=r0gzJdwCxX0
How To ROOT EASIEST METHOD - https://www.youtube.com/watch?v=S1KmsxO84UU
Downloads:
You can now flash in Rom Manager in rom if rooted
Classic - http://flyhalf205.com/recoveries/recovery-clockwork-6.0.4.6-m7ul.img
OR
Touch - http://flyhalf205.com/recoveries/recovery-clockwork-touch-6.0.4.6-m7ul.img
Chagenlog/Commits:
https://github.com/CyanogenMod/android_bootable_recovery/commits/cm-10.2
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia

Tips:
USB Mass Storage:
Bottom line. It will not work. http://teamw.in/DataMedia The only way to get files to your phone is adb commands or use a usbdisk using otg using AROMA filemanager below.
AROMA Filemanager:
Great way for moving files around. http://forum.xda-developers.com/showthread.php?t=1646108

Thx for compiling both recoveries for us, hopefully the devices will now fly in over the weekend :laugh:

Can I add TWRP/CWM to my toolkit? Please and thank you.

Re: [RECOVERY][3/6/2013]ClockworkMod Touch v6.0.2.8 [OFFICIAL]
hasoon2000 said:
Can I add TWRP/CWM to my toolkit? Please and thank you.
Click to expand...
Click to collapse
Yes. But not just yet. Let me add usb otg to twrp first. Should be tonight. Cwm is all ready though
Sent from my HTC6435LVW using Tapatalk 2

Re: [RECOVERY][3/6/2013]ClockworkMod Touch v6.0.2.8 [OFFICIAL]
Flyhalf205 said:
Yes. But not just yet. Let me add usb otg to twrp first. Should be tonight. Cwm is all ready though
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
Sounds good. I'll probably release it within the week!
Sent from my HTC VLE_U using Tapatalk 2

hasoon2000 said:
Sounds good. I'll probably release it within the week!
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
Alright. Just uploaded updated TWRP. Use this one http://d-h.st/3ST

Flyhalf205 said:
Alright. Just uploaded updated TWRP. Use this one http://d-h.st/3ST
Click to expand...
Click to collapse
Thanks! Just downloaded all the files. I'll have the toolkit up tomorrow!

@hasoon2000
Both Classic and Touch versions work. So you can pull those for your toolkit. Don't use TWRP. Doesn't boot yet. We have to wait till kernel source is out to make it boot.

Re: [RECOVERY][3/9/2013]ClockworkMod Touch v6.0.2.8 [OFFICIAL]
Flyhalf205 said:
@hasoon2000
Both Classic and Touch versions work. So you can pull those for your toolkit. Don't use TWRP. Doesn't boot yet. We have to wait till kernel source is out to make it boot.
Click to expand...
Click to collapse
Thanks! I'll have my toolkit uploaded by tomorrow.
Sent from my HTC VLE_U using Tapatalk 2

Thanks for your great work mate! Everything works like a charm.

Agree - so far everything worked incl. flashing a few new test mods, backup and restoring nandroids.

he_stheone64 said:
Agree - so far everything worked incl. flashing a few new test mods, backup and restoring nandroids.
Click to expand...
Click to collapse
Does adb work inside of recovery?

Yes, adb is working inside your both of your CWM recoveries.

hey mate, my bootloader is showing" tampered"
Is that an issue?

AW: [RECOVERY][3/9/2013]ClockworkMod Touch v6.0.2.8 [OFFICIAL]
No, this is normal.
Gesendet von meinem HTC One mit Tapatalk 2

Have some problems flashing recovery and rooting((( Unlocked the phone, flashed recovery using all in one kit, but when I go to recovery it boots in a normal way, not into the recovery. and one more thing, when i tried to flash recovery manualy it was "waiting for device" without proceeding to flashing((( any help please?

Re: [RECOVERY][3/9/2013]ClockworkMod Touch v6.0.2.8 [OFFICIAL]
Not sure if it's normal but when I try to enter recovery on my Stock One all I get (after waiting) is a big red triangle. Does the stock bootloader not allow you into recovery or is there no recovery to enter? I was hoping to nandroid it before cocking things up.
Sent from my HTC One using xda app-developers app

Re: [RECOVERY][3/9/2013]ClockworkMod Touch v6.0.2.8 [OFFICIAL]
ekabon said:
Have some problems flashing recovery and rooting((( Unlocked the phone, flashed recovery using all in one kit, but when I go to recovery it boots in a normal way, not into the recovery. and one more thing, when i tried to flash recovery manualy it was "waiting for device" without proceeding to flashing((( any help please?
Click to expand...
Click to collapse
Make sure your drivers are installed. Go into device manager on computer and verify its being recognized.
Tetsumi06 said:
Not sure if it's normal but when I try to enter recovery on my Stock One all I get (after waiting) is a big red triangle. Does the stock bootloader not allow you into recovery or is there no recovery to enter? I was hoping to nandroid it before cocking things up.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
You press power volume up or down on stock recovery. Have to flash cwm recovery to nandroid. Can't on stock recovery.
Sent from my ADR6425LVW using Tapatalk 2

guys, when I try to mount external sd it says error((( any ideas?

Related

[Tutorial] How To Root HTC Desire X Jelly Bean

I have seen that since the update notification for Jelly Bean has arrived, Many people (Including me) have been asking for a Tutorial to root the Jelly Bean updated HTC Desire X (HTC DX for short). In this tutorial I would like to mention the steps to root Android Jelly Bean (JB) on HTC DX.
UPDATE: Tutorial with Screenshots here : HTC Desire X Root
This was what had worked for me when I recently rooted by HTC Desire X with Jelly Bean Update, So I hope it works for you too. I am assuming you have just installed the OTA Update and are now sitting with a Stock Jelly Bean on your device.
Summary:
1. Unlock Bootloader (if not already unlocked).
2. Install Jelly Bean compatible Custom Recovery.
3. Flash Super User and Install Busy Box.
4. Enjoy.
Steps.
1. Unlocking Bootloader.
There is a fully explained thread on unlocking bootloader and rooting android ICS put up by user nlooooo, Follow that thread and unlock your bootloader.
http://forum.xda-developers.com/showthread.php?t=2076675
2. Install Jelly Bean compatible Custom Recovery.
Once you update via OTA for the JB Update, Your HBoot becomes JB Hboot instead of the old ICS Hboot so you need a JB Hboot compatible Custom Recovery to flash the Super User and Root.
Our fellow user atis112 fixed the recovery by neXus PRIME to make it work with JB. So you need to download the JB Custom Recovery from the attachment and put it in your C Drive, So the file location would be C:\recovery.img
2.1] Download JB Recovery.img from here : http://forum.xda-developers.com/showpost.php?p=39662992&postcount=66 OR You can use the TWRP Recovery Image made by Yasir. Download from here : http://d-h.st/tSc
2.2] Once you put it in C Drive you need to connect your HTC Mobile to PC and Install HTC JB Drivers, You can install the drivers from here : http://forum.xda-developers.com/showthread.php?t=2222501. Make sure you have installed the Drivers correctly.
2.3] Open your Android SDK (Download it from here if not already) and Go to the \sdk\platform-tools folder. If on Windows 7, Keep the Shift Key pressed + Right click on an empty place in the platform-tools folder > Open Command Window here.
2.4] Type in the following command and see if your device is detected.
adb devices
Click to expand...
Click to collapse
After it is detected, Type the following command.
adb reboot bootloader
Click to expand...
Click to collapse
Once you are in the bootloader, Type the following command.
fastboot flash recovery c:\recovery.img
Click to expand...
Click to collapse
followed by
fastboot reboot-bootloader
Click to expand...
Click to collapse
and
fastboot erase cache
Click to expand...
Click to collapse
2.5] Now you have installed your custom recovery. Now Reboot your Phone.
3. Install SuperUser and Busybox.
3.1] Once again connect your HTC to PC, Download the attached SuperUser.zip and copy it to your SD Card.
3.2] Open the command prompt again as said earlier by going to platform-tools folder and using the adb devices command to check if the phone is detected.
3.3] Once it is connected, Type the following command.
adb reboot recovery
Click to expand...
Click to collapse
3.4] Now you are in the recovery, Use the Volume Up and Down keys to navigate it (Use the power button to select an option).
Navigate to Install Flashable Zip. (This should be the first option and already selected.)
Press Power Button once.
Select "Choose Zip from internal SD-Card" or "external SD-Card" accordingly as to where you put the Superuser.zip.
Press Power Button once.
Scroll and select the Superuser.zip using the Volume Keys.
Press Power Button once.
Then you have flashed your Zip successfully and you are rooted.
Go back to the Main screen using the "Go back" option. Select the "Reboot System Now".
Once you are in the HTC Main screen > Go to App Drawer > Google Play Store > Search for Busy Box and Install it.
That is it, You are now on Jelly Bean and Successfully Rooted.
To Check If You Are Rooted.
1. Open Playstore and search for an app named "Terminal Emulator".
2. Install it.
3. Open it and type in su and execute it.
4. You will get a prompt from Superuser to allow or deny > Allow it.
If you get that prompt, You are successfully rooted.
I hope I have provided credits to all the users whose threads I have mentioned. If not please let me know.
Thanks for reading this.
Or you can refer to my TWRP for JB. Its much better than the fixed neXusRecovery.
Hey, I didn't check that.. Can you give a link to the recovery?
Droid.Anoop said:
Hey, I didn't check that.. Can you give a link to the recovery?
Click to expand...
Click to collapse
Here: http://d-h.st/tSc
xpirt
xpirt said:
Here: http://d-h.st/tSc
xpirt
Click to expand...
Click to collapse
Done. Added it to the post. Thanks Yasir and Xpirt
Droid.Anoop said:
Done. Added it to the post. Thanks Yasir and Xpirt
Click to expand...
Click to collapse
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
neXus PRIME said:
1 more little thing.
I think the instructions in recovery are using vol up down and power buttons. But if im not mistaken,, both my recoveries you mentioned are Touch enabled. So actually no need to bash the crappy volume buttons (i really hate these volume buttons due to bad tactile feedback)
Click to expand...
Click to collapse
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Both my recoveries are touch enabled.
1. TWRP (JB)
2. neXusRecovery. (discontinued for updates)
I'm not really a fan of buttons.
Droid.Anoop said:
Actually I used the CWM Modded Recovery using Vol rockers only assuming it wasn't touch enabled due to its User Interface. The TWRP one is touch enabled. Are you sure the fixed recovery is touch enabled? As I don't want to flash the old recovery once again to test it.
Click to expand...
Click to collapse
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
xpirt said:
Yes, also fixed recovery is touch enabled: you mean the nexus Recovery, right?
xpirt
Click to expand...
Click to collapse
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Droid.Anoop said:
Yes, Thanks for letting me know. Also is there any method to unlock the write protection in JB? I think the JB Sources are not released yet but any workaround?
Click to expand...
Click to collapse
I think ckpv5 found a way. Just think.
xpirt
xpirt said:
I think ckpv5 found a way. Just think.
xpirt
Click to expand...
Click to collapse
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Droid.Anoop said:
Wow that is cool! Wonder if he will share it soon. Or has he already shared it somewhere?
Click to expand...
Click to collapse
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
xpirt said:
Look at his ROMs: deodexed one and myOneDx+ have both hTC write permissions defeated.
xpirt
Click to expand...
Click to collapse
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
neXus PRIME said:
There is a wp_mod which has a Module file "wp_mod2.ko" and an init.d script, (credits to flar2) using which ckpv5 has made his roms.
Click to expand...
Click to collapse
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Droid.Anoop said:
Can you explain how to implement it in stock ROM? Then we can integrate it in the tutorial with proper credits.
Click to expand...
Click to collapse
Look at flar2's thread but use the files from ckpv5's ROM, but first ask him for permission.
xpirt
root JB without flashing custom recovery?
Hi!
I haven't flashed TWRP v2.5.0.0 but only boot the phone into this custom recovery, which is working perfectly. (I want to keep the stock recovery.)
I can install and use the Aroma File Manager (TWRP with Aroma File Manager did not work.)
I can mount the system partition and change / delete files.
However, with a reboot, all my changes will be undone.
Before installing Aroma File Manager for the first time, I installed SuperSu1.34.zip. No error. I installed Aroma File Manager right after it, and I think it said "rooted".
Using TWRP's SuperSu does not work (no error message, but system reboots, and it says it's not rooted.)
My question: can I root my phone while only booting into a non-stock recovery or do I have to flash TWRP and then root the phone?
Would I see the system apps e.g., after mounting /system, even if the phone was not rooted?
I am new to JB, I had 2.3.7 before, which I could root without flashing a custom recovery.
I am not sure if I have to flash the custom recovery because of the s-off problem with HTC devices?
If I flash a custom recovery and root the device, can I flash the stock recovery afterwards without loosing root again?
Would you recommend using SuperSu or Superuser? Which version?
I don't think I need busybox.
I only want to delete bloatware and change the battery symbol.
Thanks for your help!
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On. But after you rooted using a custom recovery you can flash the stock recovery again without loosing root. But keep in mind that you won't be able to change system partition. Also, you can't flash zips which aren't signed by HTC.
Sent from my HTC Desire X using xda premium
dansou901 said:
I didn't try rooting using the stock recovery, but I think it won't be possible as it won't let us change system partition due to S-On.
Click to expand...
Click to collapse
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
mary-lou said:
The question is if there is a difference if I just boot into the custom recovery vs. if it is flashed and I boot into it. Does ist need to be properly flashed to allow writing in /system?
Click to expand...
Click to collapse
How do you boot into a custom recovery without flashing it first? It has to be on recovery partition to work correctly.

[Recovery][P760/765/768][2013/11/24] TWRP 2.6.1.0 Recovery

Teamwin Recovery Project 2.6.1.0 for P760/765/768
Backup and restore work fine for me. I don't edit anything just build it from their source.
Only for phone with Unlocked bootloader!
Click to expand...
Click to collapse
How to install
Via fastboot
Download .img recovery file
Boot your phone to Bootloader mode (Fastboot mode) by Lelus' method or "adb reboot oem-unlock" or QuickBoot app
Flash it with "fastboot flash recovery p768-twrp-2.6.1-recovery.img"
Then reboot with "fastboot reboot"
Via Recovery
Download .zip recovery and put it in sdcard
Boot to your recovery
Install TWRP recovery zip file
Reboot
Download Link
2013/11/24
p760-twrp-2.6.1-recovery.img (P765 please use this) md5:dd3a2afce988d5de06538f72dac8faeb
p768-twrp-2.6.1-recovery.img md5:c24ac670c9f0ef5e4ad69b70886dd82f
Flashable p760-twrp-2.6.1-recovery.zip (P765 please use this) md5:dc793a3957d53ac803d2a16b0bafd8c5
Flashable p768-twrp-2.6.1-recovery.zip md5:5f19339ded9e8afe58807d90f0ece81c
Bugs / known issues
Internal sdcard mount at /sdcard not /data/media
There're option to select internal/external backup & restore, at the folder title. At first I confuse because default backup location is internal.
Version History
2013/11/24 - Fix Wip /data problem. TWRP don't format /data by default do /data/media is preserved. But you have an option to format /data.
2013/11/21 - Initial release
Credits
Teamwin for their recovery project
Cyanogenmod 10.2 for build platform
Dees_Troy for How to compile TWRP touch recovery
Reserved
Great Works...
Great work but can u do the same for P760/765...
love4u_nav said:
Great work but can u do the same for P760/765...
Click to expand...
Click to collapse
I will do it after I build new CM 10.2 kernel for P760.
artit said:
I will do it after I build new CM 10.2 kernel for P760.
Click to expand...
Click to collapse
Thnks in advance....
artit said:
I will do it after I build new CM 10.2 kernel for P760.
Click to expand...
Click to collapse
We need devs on this side now (P760)
PreemPalver said:
We need devs on this side now (P760)
Click to expand...
Click to collapse
love4u_nav said:
Thnks in advance....
Click to expand...
Click to collapse
TWRP 2.6.1.0 for P760 is up in OP. I test it on my phone and it can restore my P768 TWRP backup. (It should work because all files are that same except kernel)
Thanks for this recovery artit. Could you also build a CWM based recovery for the P760/P765/P768?
Thanks in advance.
Sent from my P760 using Tapatalk
noob.gamer said:
Thanks for this recovery artit. Could you also build a CWM based recovery for the P760/P765/P768?
Thanks in advance.
Sent from my P760 using Tapatalk
Click to expand...
Click to collapse
CWM non-touch version is built with every CM rom but it a little inconvenient to use. Touch CWM can be built from http://builder.clockworkmod.com/. P760 is already in its support devices.
I think TWRP is more usable and faster (without md5 check). I also use touch CWM for P768 for a long time before switch to TWRP.
artit said:
CWM non-touch version is built with every CM rom but it a little inconvenient to use. Touch CWM can be built from http://builder.clockworkmod.com/. P760 is already in its support devices.
I think TWRP is more usable and faster (without md5 check). I also use touch CWM for P768 for a long time before switch to TWRP.
Click to expand...
Click to collapse
Hmm, thanks for the info !
Thanks a lot, will try it out ASAP. I like TWRP very much
Sent from my LG-P760 using xda app-developers app
Is there an option to flash recovery from a tool like nandroid manager ? I found such option but it don't work ?
sebx_g1 said:
Is there an option to flash recovery from a tool like nandroid manager ?
Click to expand...
Click to collapse
I tried that but app says recovery will be flashed to null. I don't know if that is correct.
sebx_g1 said:
Is there an option to flash recovery from a tool like nandroid manager ? I found such option but it don't work ?
Click to expand...
Click to collapse
PreemPalver said:
I tried that but app says recovery will be flashed to null. I don't know if that is correct.
Click to expand...
Click to collapse
It's don't work in nandroid manager even if you put /dev/block/mmcblk0p4 in destination.
The safest way to flash it is via fastboot.
But I've tried another method by using dd. But you need shell access to do it, and if you make some mistake you may soft brick your phone.
sebx_g1 said:
Is there an option to flash recovery from a tool like nandroid manager ? I found such option but it don't work ?
Click to expand...
Click to collapse
PreemPalver said:
I tried that but app says recovery will be flashed to null. I don't know if that is correct.
Click to expand...
Click to collapse
OK, after test for a while I give you a flashable TWRP recovery in OP.
artit said:
OK, after test for a while I give you a flashable TWRP recovery in OP.
Click to expand...
Click to collapse
Thank you, just tested, it works.
I suppose that reboot from recovery on P760 don't work ... phone stays on LG logo ?
sebx_g1 said:
I suppose that reboot from recovery on P760 don't work ... phone stays on LG logo ?
Click to expand...
Click to collapse
I also try that but no error. Wait for more P760 tester to report back.
Didn't tested completely but its working on P760/P765 just fine....
I flashed zip verrsion for p760 and got kernel panic and restart loop,Use lelus fastboot method to revive it
Im on modded stock,so maybe thats the problem?
When i flashed old twrp 2.5 phone booted up normally

OnePlus 2 Stock Recovery

Hello
After searching the internet for good 30-40 minutes I found the Stock OnePlus 2 recovery image. I am returning my unit so needed it to be fully stock.
Download: https://www.dropbox.com/s/8np35kw71i222as/OPT Stock Recovery.7z?dl=0
Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Been searching for this for past hour!!!!!!
Hi,
Thank you very much.
I'm also returning my phone to oneplus and i had unlocked and rooted the phone like you.
May i know how you restore the stock ROM and recovery?
thank you
Why do you need stock recovery for that? I just wiped everything on mine and when I rebooted from twrp I chose not to protect twrp. Rma was approved so I guess they were satisfied with that.
Sent from my A0001 using Tapatalk
granfot said:
Why do you need stock recovery for that? I just wiped everything on mine and when I rebooted from twrp I chose not to protect twrp. Rma was approved so I guess they were satisfied with that.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
What do you means by "wipe everything"? include internal storage?
And i heard that official twrp dont have the option of "not to protect twrp".
werthechamp said:
What do you means by "wipe everything"? include internal storage?
And i heard that official twrp dont have the option of "not to protect twrp".
Click to expand...
Click to collapse
Yes, including internal storage.
That I didn't know, but you don't void warranty by installing custom recovery or rooting so it shouldn't be an issue either way.
Sent from my A0001 using Tapatalk
granfot said:
Yes, including internal storage.
That I didn't know, but you don't void warranty by installing custom recovery or rooting so it shouldn't be an issue either way.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Is this the recovery of the international version or chinese?
thx
This is not the international version but chinese . Im looking for the english version, searched everywhere but unable to find it. wtf
1. Download the latest signed flashable zip from here.
2. Press thanks for Spannaa.
3. Extract recovery.img from the zip file with 7zip.
4. Flash it from fastboot using the "flash recovery recovery.img" command.
CafeKampuchia said:
1. Download the latest signed flashable zip from here.
2. Press thanks for Spannaa.
3. Extract recovery.img from the zip file with 7zip.
4. Flash it from fastboot using the "flash recovery recovery.img" command.
Click to expand...
Click to collapse
Problem: The signed flashable zips don't contain recovery.img
Spannaa said:
Problem: The signed flashable zips don't contain recovery.img
Click to expand...
Click to collapse
Hmmmm... that would be a problem. :/ Thanks for pointing that out.
CafeKampuchia said:
Hmmmm... that would be a problem. :/ Thanks for pointing that out.
Click to expand...
Click to collapse
I Installed the 2.0 manually...then update ota...now I have stock recovery.
zat0x said:
This is not the international version but chinese . Im looking for the english version, searched everywhere but unable to find it. wtf
Click to expand...
Click to collapse
Hey, I don't know if you ever found the stock recovery but another member had posted fastboot images in the OnePlus2 Android Development section.
I haven't tested out the recovery myself, but you can check to see if it's the English one.
All Fastboot images: https://www.androidfilehost.com/?w=files&flid=40701
Stock Recovery Image: https://www.androidfilehost.com/?fid=24052804347834210
Hope this helps.
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
keshavmot2 said:
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
Click to expand...
Click to collapse
Good question! Want to know that too...
keshavmot2 said:
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
Click to expand...
Click to collapse
1:
Flash the full stock rom from OxygenOS 2.1.1: http://forum.xda-developers.com/showthread.php?t=3209863
2: Flash the OxygenOS 2.1.2 zip from the same post
3: flash the stock recovery from tgis thread
Hope I helped you
Download OP2 Stock Recovery from Official Site: https://s3.amazonaws.com/oxygenos.oneplus.net/OP2_recovery.img
It seems OnePlus uses AWS to host all of their OTA's.
E.G. https://s3.amazonaws.com/oxygenos.oneplus.net/OnePlus2Oxygen_14_OTA_012_all_1602261837.zip ( This is for OxygenOS 2.2.1 releases in 2012 26th Feb - 970MB )
Recent ROM Downloads of OP2: http://downloads.oneplus.net/devices/oneplus-2/ ( Includes Marshmallow Beta OxygenOS 3.0 , however, seems the ROM has Battery issue, major )
matrixdefalco said:
I Installed the 2.0 manually...then update ota...now I have stock recovery.
Click to expand...
Click to collapse
I did the same thing and it worked for me If somebody is still facing this issue
anyone knows how the flash the stock recovery from mac???
krishp said:
anyone knows how the flash the stock recovery from mac???
Click to expand...
Click to collapse
One "?" is enough dude..
You have to install adb for Mac (http://stackoverflow.com/questions/31374085/installing-adb-on-mac-os-x), enable USB Debugging on your phone, reboot into bootloader mode :
Code:
adb reboot-bootloader
then go into:
Code:
su
and then
Code:
fastboot devices
fastboot flash <recovery_name>.img

I think I'm already soft-bricked...

I wanted the new update so that I could move my apps to my SD card. I also wanted TWRP.
I followed this guide to install TWRP.
TWRP was successfully flashed. So I try to boot into it using 'fastboot boot recovery.img' to boot into it.
I get the 'ERROR: Remote DTB not found' message. So booting into recovery using fastboot doesn't work.
I try booting into recovery manually (volume down + power). That doesn't work either. It freezes up at the OnePlus logo.
So, since TWRP isn't working, I flash stock recovery. That worked fine, and booted into it successfully (manually).
I boot into stock recovery and followed this guide to try updating manually using stock recovery. Of course, the update fails.
I then try flashing the full dump here. I factory reset, then flashed the full dump.
"Update successful."
Now, it refuses to boot into system AND recovery.
Okay, I'll just reflash stock recovery?
ERROR: Remote DTB not found
Booting into recovery manually freezes up too, just like TWRP did earlier.
Is there something I'm doing wrong to get this error? Google tells me dtb errors are caused by corrupt IMGs, but I downloaded all the IMGs twice and from all available mirrors to try them out. I see that some other users in the OnePlus forums and in XDA are having the same problems when flashing TWRP.
I really just need to be able to boot into at least one recovery so I can flash a system dump again.
I am not sure if this is the cause of the problem, but I've noticed most OnePlus X users have the E1003 model, while I am using a E1005.
Any help is appreciated.
mechanity said:
I wanted the new update so that I could move my apps to my SD card. I also wanted TWRP.
I followed this guide to install TWRP. Like a few others in the thread, I had the problem that when I try to boot manually into recovery, the screen shows the OnePlus logo with the android logo. Then the android logo disappears, and no matter how long I hold the down button while booting, the screen freezes at the OnePlus logo.
Fine, I'll just use fastboot boot recovery.img .
Nope, I get the 'ERROR: Remote DTB not found' message. Still stuck on the fastboot screen.
Great, I'll just flash stock recovery. Cool, it worked.
I booted into stock recovery and followed this guide to try updating manually using stock recovery. Of course the update fails.
Maybe I can just flash the full dump here. I factory reset, then flashed the full dump. Now it refuses to boot into system AND recovery.
Okay, I'll just reflash stock recovery?
ERROR: Remote DTB not found
Booting into recovery manually gives me the same results as flashing TWRP did earlier. So now, I can neither flash stock recovery nor TWRP to install any OxygenOS.
Is there something I'm doing wrong to get this error? Google tells me dtb errors are caused by corrupt IMGs, but I downloaded all the IMGs twice and from all available mirrors to try them out. I really just need to be able to boot into at least one recovery so I can flash a system dump again.
I am not sure if this is the cause of the problem, but I've noticed most OnePlus X users have the E1003 model, while I am using a E1005.
Any help is appreciated.
Click to expand...
Click to collapse
When you try do go in recovery manually(volume up+power) what does it show
mohammedtabish said:
When you try do go in recovery manually(volume up+power) what does it show
Click to expand...
Click to collapse
Well, pressing volume up + power actually takes me to bootloader mode.
Volume down + power, on the other hand, shows the OnePlus logo and the Android logo for a split second. Then the android logo disappears, the OnePlus logo stays, and it freezes there.
In case my post wasn't very clear, the same thing happens even if I don't attempt to boot into recovery (as in, it does the same thing if I just press the power button to boot into the system).
In bootloader try to go in fastboot mode then flash the recovery using fastboot
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
In bootloader try to go in fastboot mode then flash the recovery using fastboot
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
That is exactly what I said I did in the OP. I have tried this multiple times.
Yes its softbrick and to solve this prob the only thing that i can think is install usb drivers again and tell me you that you have checked the debugging before getting softbricked and try f2fs recovery from eng_stk kernel thread
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
Yes its softbrick and to solve this prob the only thing that i can think is install usb drivers again and tell me you that you have checked the debugging before getting softbricked and try f2fs recovery from eng_stk kernel thread
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
I tried the f2fs recovery from blu_spark eng.stk thread just now. I am still getting the remote: dtb not found error.
Still freezing when I boot manually into the recovery.
I think change the pc you are using and start every thing from new in other thats the last hope
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
I think change the pc you are using and start every thing from new in other thats the last hope
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Tried all of these steps on two other PCs already, on both Windows 8 and Windows 7. It's not a driver issue or OS issue.
Guess I'll have to wait until the system IMGs are out, unless anyone else has any other suggestions.
System image ??? If you mean stock then its available bro
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
System image ??? If you mean stock then its available bro
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
It's available as a .zip, which means you need a working recovery to install it.
There is image also if you cant find it i can upload that i have backed up that or i will try to find that link
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
There is image also if you cant find it i can upload that i have backed up that or i will try to find that link
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
Please do find that link or upload it, I cannot find it at all.
Thank you very much.
[/COLOR]
mechanity said:
Please do find that link or upload it, I cannot find it at all.
Thank you very much.
Click to expand...
Click to collapse
There you go bro
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
Sent from my ONE E1003 using Tapatalk
Hit thanks if helped
mohammedtabish said:
[/COLOR]
There you go bro
https://drive.google.com/file/d/0B3AIip-hiOnNaTVSQXk5bUgzVnM/view?usp=sharing
Sent from my ONE E1003 using Tapatalk
Hit thanks if helped
Click to expand...
Click to collapse
Sorry, I think you misunderstood me. I stated in the original post that I already have the stock recovery img, and have already tried flashing it.
I am talking about a full system image that can be flashed via fastboot or odin.
Ooooooo i think thats not available sorry for waisting you time though
Sent from my ONE E1003 using Tapatalk
mohammedtabish said:
Ooooooo i think thats not available sorry for waisting you time though
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
It's okay, thanks for your help.
mechanity said:
Tried all of these steps on two other PCs already, on both Windows 8 and Windows 7. It's not a driver issue or OS issue.
Guess I'll have to wait until the system IMGs are out, unless anyone else has any other suggestions.
Click to expand...
Click to collapse
been having the exact issue...now people wont think im crazy.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
mechanity said:
Sorry, I think you misunderstood me. I stated in the original post that I already have the stock recovery img, and have already tried flashing it.
I am talking about a full system image that can be flashed via fastboot or odin.
Click to expand...
Click to collapse
You can boot to stock.img?
I have the same dtb error when I try any twrp image I have attempted to flash...exactly like your issue, but stock works fine.
If you can get into stock you can flash the full rom zip of 2.1.2 and then flash the ota to 2.1.3 after.
You have to flash the full zip first.
joho5 said:
been having the exact issue...now people wont think im crazy.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
You can boot to stock.img?
I have the same dtb error when I try any twrp image I have attempted to flash...exactly like your issue, but stock works fine.
If you can get into stock you can flash the full rom zip of 2.1.2 and then flash the ota to 2.1.3 after.
You have to flash the full zip first.
Click to expand...
Click to collapse
Originally, I could boot to the stock recovery. However after flashing that full 2.1.3 dump that I linked to, I can't boot to system or recovery. Flashing stock recovery now gives me the same remote:dtb not found error.
i have the same problem
i can't get into adb but can get into fastboot

Broken recovery?

Hi guys, today I booted into recovery (stock) only to see this:
http://imgur.com/a/XSIpt
and this
http://imgur.com/a/Esq2n
Once every 5 seconds or so it briefly shows the message "TFlash card is not existed"
The phone is Allview P5 Lite (MT6735M - Android 6.0 Marshmallow)
Any ideas?
Are you sure that's the recovery? Maybe try booting the phone in normal mode, then enable USB debugging, connect your device to the PC and reboot to recovery using the command *adb reboot recovery*.
Sent from my Infinix-X551 using Tapatalk
Christianihechi said:
Are you sure that's the recovery? Maybe try booting the phone in normal mode, then enable USB debugging, connect your device to the PC and reboot to recovery using the command *adb reboot recovery*.
Sent from my Infinix-X551 using Tapatalk
Click to expand...
Click to collapse
did that already, same problem
Maybe you should consider flashing the stock recovery, if you have the stock firmware.
Sent from my Infinix-X551 using Tapatalk
Christianihechi said:
Maybe you should consider flashing the stock recovery, if you have the stock firmware.
Sent from my Infinix-X551 using Tapatalk
Click to expand...
Click to collapse
I can't find it anywhere. I found here on xda a twrp for MT6735m (my cpu as well) but I don't know if it's safe to flash it, look here
https://forum.xda-developers.com/android/development/recovery-twrp-3-0-2-0-unofficial-port-t3439197
I know I first have to unlock the bootloader, I know how to, then flash the twrp using fastboot, but my only concern is that it'll brick my device somehow, because the recovery above is for ZTE Blade. Can you tell me if it's safe to flash it?
It's not only unsafe, it's also not going to work. You need your stock recovery to be able to port and use a custom recovery like TWRP.
Sent from my Infinix-X551 using Tapatalk
Christianihechi said:
It's not only unsafe, it's also not going to work. You need your stock recovery to be able to port and use a custom recovery like TWRP.
Sent from my Infinix-X551 using Tapatalk
Click to expand...
Click to collapse
Maybe I'll be able to put my hands on the stock recovery, but can you point me an useful guide on how to port (I don't know what this actually means in the context) the custom recovery?
Okay, get your stock recovery first of all, flash it and see how it goes. Installing a custom recovery(e.g TWRP) will come later.
Sent from my Infinix-X551 using Tapatalk
Christianihechi said:
Okay, get your stock recovery first of all, flash it and see how it goes. Installing a custom recovery(e.g TWRP) will come later.
Sent from my Infinix-X551 using Tapatalk
Click to expand...
Click to collapse
I'm back with fresh news. I flashed the stock recovery, but I still have the same problem. What can I do?

Categories

Resources