[Recovery] ClockworkMod - TF701T Proxy Thread - Asus Transformer TF701

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS IS A PROXY THREAD Creator and Maintainer is pershoot
This is CWM for the ASUS Transformer Pad (TF701T – Macallan).
-You must be unlocked (use ASUS’s unlock tool to perform this)
-You must be on 10.26.1.18 bootloader (updating to ASUS’s latest 4.3 release will install this)
For complete Info and Download: VISIT HERE
***Once there, check out the Recent Entries on the right side of the page for latest updates***
-Unlock your device using the ASUS Unlock tool.
-Boot in once and execute: adb reboot bootloader
Fastboot:
To boot the recovery:
fastboot boot recovery.img
To permanently flash the recovery:
fastboot flash recovery recovery.img
Source:
https://github.com/pershoot/android_device_asus_tf701t
https://github.com/pershoot/android_kernel_asus_tf701t
https://github.com/CyanogenMod/android_bootable_recovery
Creator and Maintainer:
@pershoot

Video Tutorial
Video Tutorial Thanks @wwjoshdew

Ah just saw screenies. Nice job pershoot.
Why is the version still 6.0.4.6?

CWM 6.0.4.7
OP Updated

Feb/2 OP updated

Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.

I was on 6.0.4.6 and i used flashify to update. Worked fine.

hetzbh said:
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
Click to expand...
Click to collapse
Both cromix and cm11 will require the latest bootloader to eliminate compatibility issues it is recommended to flash to the latest asus firmware
Sent from my SGH-T889 using XDA Premium 4 mobile app

@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g

wwjoshdew said:
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
Click to expand...
Click to collapse
included in the post alongside the screenshots. Thanks a lot!!!

OP updated 2/16, installation video tutorial included. Thanks to @wwjoshdew

recovery updated with baseline build and sorted dock sd card functionality and usbdisk functionality.

@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?

sbdags said:
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
Click to expand...
Click to collapse
i'll look in to it...

I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?

lortay78 said:
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
Click to expand...
Click to collapse
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.

sbdags said:
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
Click to expand...
Click to collapse
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.

lortay78 said:
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
Click to expand...
Click to collapse
Very common mistake that happens to the best of us

updated.

Hi,
I spent hours trying to get this to work before discovering there are two missing steps in the OP's instructions.
There's a shell script that calls an application that restores the stock boot loader on every boot.
You have to delete it.
Steps:
1. Root.
2. Install Root Explorer.
3. Go into /etc
4. Delete install_recovery.sh
5. Go into /system
6. Delete recovery-from-boot.p
You have to delete the files. You can't just rename them or change the extension because the system actually searches the filesystem for a file whose contents matches an MD5 hash and will find it if you rename it.
After you do this, THEN follow OP's instructions.

Related

[RECOVERY] 4/Apr: 3.0.1.4 r1 - ClockworkMod Recovery for the LG Optimus 2X

DO NOT RUN THIS ON THE G2X! The partition layout is different, doing so will do bad things to your device. I will release a G2X compatible version when I am back online in a week's time!
For the past couple of days I have been working on creating a ClockworkMod recovery image for the LG Optimus 2X. I'm pleased to announce that the first full release is available!
Some points to note - READ THESE CAREFULLY!
Use at your own risk! I have successfully used the backup and restore functionality (nandroid), and am currently testing other functions.
If you manage to break your device completely, this ROM should get you back up and running.
Download
I have packaged the recovery itself and the installation system together in one download zip.
3.0.1.4 r1 DOWNLOAD (ROMraid Load Balancing) - MD5: 7145b425f95a87dc5bde29ac4eba48ff
Installation automatically on your device
NEW: If your device is rooted, my 99p 2X Recovery Boot app (mentioned below) can now flash the recovery image for you the first time you run the app and on subsequent version updates!
Installation on Windows, Linux and OSX
- Download the zip file above and extract to a directory
- Connect your device and ensure 'USB debugging' is enabled
- WINDOWS - double click 'install-clockworkmod-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-clockworkmod-mac.sh' followed by './install-clockworkmod-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-clockworkmod-linux.sh' followed by './install-clockworkmod-linux.sh'
If you wish, you can also manually install the recovery by pushing the clockworkmod.img file to /data/local/ with adb and running 'dd if=/data/local/clockworkmod.img of=/dev/block/mmcblk0p7' from a root shell.
Launching Recovery
To boot ClockworkMod Recovery, either:
Turn the device on while holding the volume down and power buttons until recovery loads
Download the OPTIONAL 99p 'LG 2X Recovery Boot' application from the Android Market (NOTE: This app is completely optional - if you do use it, thanks for your support!)
Source / Updates
I'll be posting the device profile and source changes on my GitHub shortly, and will issue fixes / new Betas as required.
Enjoy!
P
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks Paul !
You are the best. I am wating for the crowd to test this so I can use it for my mission critical work phone but the future seems bright.
Hi Paul... first of all - Great job here
Second - if one can't get root access via SuperOneClick, like myself, is this still usable?
Inebriatef said:
Hi Paul... first of all - Great job here
Second - if one can't get root access via SuperOneClick, like myself, is this still usable?
Click to expand...
Click to collapse
Root access is not a pre-requisite.
P
mirror (if it's ok with you Paul)
http://www.mediafire.com/?udkabus35wlr2w3
Great job paul
THANKS! Installing now
Update:
If you get error in windows just change adb-windows.exe to adb.exe
First, thank you very much, Paul. Great job!
Two questions.
1) This method overwrites the standard recovery on the phone, correct?
2) To revert back to standard recovery, one have to flash the whole phone using nvflash, correct?
ULJ said:
First, thank you very much, Paul. Great job!
Two questions.
1) This method overwrites the standard recovery on the phone, correct?
2) To revert back to standard recovery, one have to flash the whole phone using nvflash, correct?
Click to expand...
Click to collapse
1) Yes
2) No, you could just dd the stock recovery.img from the NVFlash archive.
P
<- This is me "patiently" waiting for CyanogenMod and Paul's online kitchen for the 2x
GREAT work as always, Paul!
paulobrien said:
1) Yes
2) No, you could just dd the stock recovery.img from the NVFlash archive.
P
Click to expand...
Click to collapse
Okay. Thanks.
Im just curious, who supplies the NVFlash archive? And is the standard recovery image supplied by Nvidia or LG? Since it is part of the NVFlash archive.
Found out why i can get no root access... i got no adb access at all.
First time pluggin in phone after install of LG drivers, it says that the adb interface thingy can't install.
This also causes that i can't install CWM.
Any suggestions as to what is wrong?
Thank you, Paul!
Successful nandroid backup I will try to make a custom rom.
Paul its was a good idea to let clockworkmod make backup to external sd because its not possible to mount usb storage in recovery menu yet.
Inebriatef said:
Found out why i can get no root access... i got no adb access at all.
First time pluggin in phone after install of LG drivers, it says that the adb interface thingy can't install.
This also causes that i can't install CWM.
Any suggestions as to what is wrong?
Click to expand...
Click to collapse
I hade the same problems. Download the LG drivers from this site, worked for me.
www {dot} junefabrics.com/android/driver.php
(could not post links, so replace {dot} with a .)
Inebriatef said:
Hi Paul... first of all - Great job here
Second - if one can't get root access via SuperOneClick, like myself, is this still usable?
Click to expand...
Click to collapse
Tried Z4root?
Nilssonnet said:
I hade the same problems. Download the LG drivers from this site, worked for me.
www {dot} junefabrics.com/android/driver.php
(could not post links, so replace {dot} with a .)
Click to expand...
Click to collapse
thx, it works now
yipeee! now i can expect a real custom rom
Ok first backup done! Works perfect! Thanks for all the effort!
Korumera said:
Ok first backup done! Works perfect! Thanks for all the effort!
Click to expand...
Click to collapse
Same here. Thank you very much, Paul!

[TOOLKIT][FLASHER]Desire C Toolk!t v1.5(25/04/13)[Recovery/Kernel/Root/Bootloader]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Presenting to You
HTC DESIRE C TOOLK!T by TeKnoGin
DISCLAIMER
Code:
[FONT="Century Gothic"]* TheRedHunter has not only tested the tool but has confirmed that it is working. (POST 2)
So first of all a big thanks to him for taking the risk and testing the toolkit.
* I am not responsible if your device gets bricked or something
happens so I recommend that you get a stock rom ready.
* You will need an Unlocked Bootloader which means you have
already void your warranty. [URL="http://forum.xda-developers.com/showthread.php?p=40690862"]If you haven't unlocked it yet then here is a guide[/URL][/FONT]
Code:
[FONT="Century Gothic"]The toolkit provides the user (basically new users) to flash Recoveries and
Kernels (even ROMs which will be updated soon) to your DESIRE C.
# The update v1.5 will also provide users with two new features that is ***unlocking bootloader***
(giving you the oem unlock code) and ***rooting your device***
[SIZE="5"][COLOR="DarkGreen"]Desire C Toolk!t v1.0[/COLOR][/SIZE]
# Flashing Custom Recoveries:-
> ClockWorkMod Recovery 6.0.3.0 (TOUCH) by mehmehmen [URL="http://forum.xda-developers.com/showthread.php?t=2231101"]LINK HERE[/URL]
> ClockWorkMod Recovery Stable by mmmcfc [URL="http://forum.xda-developers.com/showthread.php?t=1785010"]LINK HERE[/URL]
> ClockWorkMod Recovery 5.5.0.4 (TOUCH) by munjeni [URL="http://forum.xda-developers.com/showthread.php?t=1829649"]LINK HERE[/URL]
> TWRP Recovery 2.5.0.0 by nikhil16242 [URL="http://forum.xda-developers.com/showthread.php?t=2148015"]LINK HERE[/URL]
> Your Own Recovery Whichever You Want (if you have any new one please
tell me too)
# Flashing Custom Kernels
> Prometheus Kernel by nikhil16242 [URL="http://forum.xda-developers.com/showthread.php?t=2192750"]LINK HERE[/URL]
> Your Own Desired Kernel[/FONT]
[SIZE="5"][COLOR="DarkGreen"]Desire C Toolk!t v1.5[/COLOR][/SIZE]
# Rooting your phone
> Root your Desire C with just a click. Rooting process uses [URL="http://www.modaco.com/topic/355158-r1-superboot-how-to-root-the-htc-desire-c/"]Superboot[/URL]
to get root access and then provide permanent root to the users.
> Unlock Bootloader [OPENS THE LINK] (BY THE WAY HERE IS A GUIDE TOO:-
[URL="http://forum.xda-developers.com/showthread.php?p=40690862"]http://forum.xda-developers.com/showthread.php?p=40690862[/URL])
Code:
[FONT="Century Gothic"]
# * Extract the "toolkit_desire_c.zip" to somewhere like Desktop.
* Connect your Desire C with USB Debugging Enabled.
* Run "recovery.bat".
* Select your Desired Option.
* Just wait.......
# *To Flash Your Own Desired RECOVERY or KERNEL [COLOR="Red"]
+ Make sure you rename your recovery to ****recovery.img**** (without starsigns)
and place it in the "own" folder and then select option 7.
+ Make sure you rename your kernel (img file) to ****boot.img**** (without starsigns)
and place it in the "own folder " and then select option 6.[/COLOR][/FONT]
Code:
[FONT="Century Gothic"] Mirrors will be coming soon till then no mirrors please....
[SIZE="4"][COLOR="DarkGreen"]Desire C ToolK!t v 1.0[/COLOR][/SIZE]
# Skydrive:- [URL="http://sdrv.ms/13swfZ6"]http://sdrv.ms/13swfZ6[/URL][COLOR="Red"]{COMPATIBLE with all COMPRESSION SOFTWARE
thnx to [URL="http://forum.xda-developers.com/member.php?u=5091745"]noahvt[/URL]}[/COLOR]
# Dev-Host:- [URL="http://d-h.st/cuR"]http://d-h.st/cuR[/URL]
[SIZE="4"][COLOR="DarkGreen"]Desire C ToolK!t v 1.5[/COLOR][/SIZE]
# Skydrive:- [URL="http://sdrv.ms/17Z1nTE"]http://sdrv.ms/17Z1nTE[/URL]
# Dev-Host:- [URL="http://d-h.st/N92"]http://d-h.st/N92[/URL]
[/FONT]
​
Nice tool, I'll test it as soon as I'll be home.
Edit: Your toolkit works like a charm. This is the easiest way to flash kernels/recoveries I've ever used.
Doesn't work: unknown compression method in winrar,winzip and standard windows extraction program!
TheRedHunter said:
Nice tool, I'll test it as soon as I'll be home.
Click to expand...
Click to collapse
Thnx Man Report here asap whether it is working or not??
Just try and test each one.
noahvt said:
Doesn't work: unknown compression method in winrar,winzip and standard windows extraction program!
Click to expand...
Click to collapse
Try it with 7-zip.
I compressed it using 7-zip.....
btw i'll see to make it work with winzip, winrar and other compression software.
Update
I'll update a compressed version which will be compatible with all compression software soon.
Edit: UPDATED
Huston we've got a problem. It's something wrong with my port...but what is the connection between a port and a recovery flash ?4
Problem solved, thank you.
Solution
Here is a fix to that problem.
http://themikmik.com/showthread.php?15885-ADB-Server-didn-t-Ack-Error-SOLVED
Run the batch file ....TRY IT.....
Download it here:- http://sdrv.ms/14MRGJ8
there are two reasons for this error:-
1. when no device is connected
2. when HTCSyncManager.exe is already using adb servers
Worked like a charm, thank you very much! :good:
FusionX3 said:
Worked like a charm, thank you very much! :good:
Click to expand...
Click to collapse
Happy to Help
I tried to install the Prometheus kernel too now. It wrote Writing Successful but when the phone tries to boot it's stuck at the white HTC screen with the red text (This build is for development purposes only ...). What should I do?
EDIT: I tried to restore to a previous backup, I tried to install a custom ROM I had on my SD Card, none of that worked.
FusionX3 said:
I tried to install the Prometheus kernel too now. It wrote Writing Successful but when the phone tries to boot it's stuck at the white HTC screen with the red text (This build is for development purposes only ...). What should I do?
EDIT: I tried to restore to a previous backup, I tried to install a custom ROM I had on my SD Card, none of that worked.
Click to expand...
Click to collapse
But thats working with my phone......
I tried installing Prometheus Kernel and it was successful....
Try installing the kernel manually.
1. Switch Off your phone and then boot into fastboot mode.
2. Connect your phone to the computer.
3. Open a command prompt in the "tools" folder.
4. Run the following command
"fastboot flash boot boot.img" (without quotes)
5. restart your phone with this command
"fastboot restart"
Tell me whether that worked or not.
Taking the case of the backup or flashing the ROM which recovery did you flashed???
I would recommend you to flash the CWM 6.0.3.0 TOUCH recovery which doesn't till now has a bug.
For this repeat the steps in this post and instead of step 4 just run the following command:
"fastboot flash recovery recovery_touch_6_0_3_0.img"
Then try to flash the ROM.
If it says "Install from sdcard failed" or something like that then retry downloading the ROM.
If nothing works then try FLASHING STOCK ROM...
Edit: How can a restore fail ? What error does it show? Did you change the recovery? Are the recoveries different i.e. the one with which you backed up and the one which you are trying to restore????
TeKnoGin said:
But thats working with my phone......
I tried installing Prometheus Kernel and it was successful....
Try installing the kernel manually.
1. Switch Off your phone and then boot into fastboot mode.
2. Connect your phone to the computer.
3. Open a command prompt in the "tools" folder.
4. Run the following command
"fastboot flash boot boot.img" (without quotes)
5. restart your phone with this command
"fastboot restart"
Tell me whether that worked or not.
Taking the case of the backup or flashing the ROM which recovery did you flashed???
I would recommend you to flash the CWM 6.0.3.0 TOUCH recovery which doesn't till now has a bug.
For this repeat the steps in this post and instead of step 4 just run the following command:
"fastboot flash recovery recovery_touch_6_0_3_0.img"
Then try to flash the ROM.
If it says "Install from sdcard failed" or something like that then retry downloading the ROM.
If nothing works then try FLASHING STOCK ROM...
Edit: How can a restore fail ? What error does it show? Did you change the recovery? Are the recoveries different i.e. the one with which you backed up and the one which you are trying to restore????
Click to expand...
Click to collapse
I resolved the problem. I installed the smallest version (700) of the Prometheus kernel, and that worked.

SOLVED [Q] Serious Bootloop issue using cwm

Hello everyone,
I recently rooted my phone ( http://theunlockr.com/2013/03/16/how-to-root-the-motorola-razr-i/ ) and everything was ok. But while setting up a new ROM, my system got stuck in a bootloop.
I can't figure out what is wrong, and no matter what rom i install, the device manages to boot up, but then crashes when loading GUIs and third party apps.
What i have tried so far:
wipe everything there is to wipe using CWM and formating folders also using cwm
press factory settings on fastboot
using bp tools on fastboot (though i don't know what it is used for) it managed to boot up the phone ONCE but with no wi fi nor mac adress available (the rom i used http://www.argendroid.com/topic-ROM...u-Control-Smart-Battery-21-08-2013-ArgenDroid )
mess up with different roms, all of them crashed at the same point
The Roms i tried:
Pillama 1.6 http://www.argendroid.com/topic-ROM...u-Control-Smart-Battery-21-08-2013-ArgenDroid
Atom CFW http://www.argendroid.com/topic-ROM-Atom-CFW-CustomFirmWare-Final
The tutorial's rom mentioned before which worked well
Progress and hints
at first i would just wipe data/factory , cache partition and dalvik, and the booting could not go further than displaying the unlock warning
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
once i formated /system, /cache, /data, /pds, /sdcard(which is actually the phone internal storage, there is another folder named /external-sd)
only then the boot process would go further and display the nice loading animations, but still crashing in the end before i could do anything.
Aditionally i can't manage to use ADB because somehow, my Barcode managed to dissapear. ADB won't recognize my device.. i'll try to find a ROM with usb debugging enabled by default but who knows...
So please help, what can i do?
I think there is something inside the internal storage that is not quite erased and is jamming when installing other roms. It is still pretty bizarre, and my phone is no more than a month old so...
Thanks beforehand.
How you installed CWM? Was using this? Which CWM version are you using? Tried to flash to stock?
well, you need to find pi-llama 1.4
download it, enter fastboot and flash the system.ext4 image. type
fastboot flash system (name of the file)
then look forward the omar-avelar kernel img and type
fastboot flash boot (name of the kernel img)
SOLVED
sky0165 said:
well, you need to find pi-llama 1.4
download it, enter fastboot and flash the system.ext4 image. type
fastboot flash system (name of the file)
then look forward the omar-avelar kernel img and type
fastboot flash boot (name of the kernel img)
Click to expand...
Click to collapse
Surprisingly enough, pi-llama 1.4 solved it.
https://mega.co.nz/#!wFpjhLrA!ODHD6DKRN-DFTGUhNPTTgzrzcIE_aG2lgWDp4gBgXHY
i just had to modify the .bat file so it wouldn't search for fix.zip in the phone memory.
It succesfully flashed system.img, boot and cwm 6.0.9 (not sure didn't check)
then i wiped data on phone, and installed fix.zip flash with cwm
once i got to restart it, i got it on fastboot mode and used bp tools and.... IT BOOTED UP!!
i think the boot included is omar's already, because wlan issues were solved (device has got a MAC adress)
thank you so much!
i won't turn off my phone again just to be sure
thiagomtl said:
How you installed CWM? Was using this? Which CWM version are you using? Tried to flash to stock?
Click to expand...
Click to collapse
Hi, it got solved thanks to @sky0165 advice,
i just used fastboot recovery <cwm image>
<cwm image> being the file downloaded from this thread
http://forum.xda-developers.com/showthread.php?t=1974097
6.+ version i didn't check
i tried to flash to stock yes but since adb didn't work it was kind of pointless i think.. it just didn't work
Thanks for your concern
I should mention that my PC is not able to recognize the usb storage.
I don't mind since Airdroid exists, but it's still kind of a bummer.
ADB recognizes it, though it displays Medfield<hex number>
ymer92 said:
Surprisingly enough, pi-llama 1.4 solved it.
https://mega.co.nz/#!wFpjhLrA!ODHD6DKRN-DFTGUhNPTTgzrzcIE_aG2lgWDp4gBgXHY
i just had to modify the .bat file so it wouldn't search for fix.zip in the phone memory.
It succesfully flashed system.img, boot and cwm 6.0.9 (not sure didn't check)
then i wiped data on phone, and installed fix.zip flash with cwm
once i got to restart it, i got it on fastboot mode and used bp tools and.... IT BOOTED UP!!
i think the boot included is omar's already, because wlan issues were solved (device has got a MAC adress)
thank you so much!
i won't turn off my phone again just to be sure
Hi, it got solved thanks to @sky0165 advice,
i just used fastboot recovery <cwm image>
<cwm image> being the file downloaded from this thread
http://forum.xda-developers.com/showthread.php?t=1974097
6.+ version i didn't check
i tried to flash to stock yes but since adb didn't work it was kind of pointless i think.. it just didn't work
Thanks for your concern
Click to expand...
Click to collapse
It's nice to hear that. You can flash other roms(Omar for example) in case you got bootloops with clean installs. You just need to do the pi-llama method (flash the system.img & kernel) and then install the rom you want on top of the pi-llama 1.4

[MAGISK][Android 10]Patched Boot Image For OnePlus 7 Pro

Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk.
Recommended to patch your own image read this
Grab the latest Platform Tools HERE
Code:
1. Download a stock Oxygen OS ROM Zip from [URL="https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156267635"]Here[/URL] Or the general section of XDA many users post links to the latest builds.
2. Download [URL="https://androidfilehost.com/?fid=818070582850510260"]payload_dumper-win64.zip[/URL] And extract/copy it to Desktop.
3. Extract your payload.bin from the stock rom zip and copy it into the payload_input folder.
4. Run the payload_dumper exe.
5. When it's finished open the payload_output folder and copy the boot.img to Desktop keep it there as a backup.
6. Copy the same boot.img to your internal storage on your phone.
7. Install the magisk manager APK from here: [URL="https://github.com/topjohnwu/Magisk"]Magisk Manager[/URL]
8. Open Magisk Manager choose install and select "Select and Patch a file" Or if you wish to use beta release go to settings > Update Channel and switch to beta and then back to Install "Select And Patch A File"
9. Navigate to where you copied your boot.img on the phone.
10. Once it's patched you'll have an magisk_patched.img on your phone in the the Downloads folder.
11. Copy that image to your fastboot folder on your PC and flash it with fastboot flash boot magisk_patched.img
Done!
As always I'm not responsible for any issues your device might have or if your cat sets on fire.
Credits:
topjohnwu for Magisk/Manger
geminids14 for payload_dumper-win64
Nice, that is what we need .. Thanks Liam
How can i load twrp? Fastboot boot command, didnt work
DevrimSeven60 said:
How can i load twrp? Fastboot boot command, didnt work
Click to expand...
Click to collapse
Ask in the TWRP thread
Not working for me get a error file is to large to download when try to flash
dajumper said:
Not working for me get a error file is to large to download when try to flash
Click to expand...
Click to collapse
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
liam_davenport said:
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Still the same
Im already rooted with bootimg having lat pie release. Is it possible to flash Android Q on top of last pie release and be rooted? Again I am rooted with magisk, not having twrp.
To update I always flash full updat from local, not reboot, install magisk to other slot and I was ready to go.
Will this work with Q update?
Not working for me. Both sims dissapear and phone keeps FC.
pister said:
Not working for me. Both sims dissapear and phone keeps FC.
Click to expand...
Click to collapse
Issue is on your end, I've flashed this multiple times no issue.
Working perfectly here I've clean flashed and redownloaded from the link and flashed. I've noticed sometime magisk causes sims to not show on boot before reboot the device and they should show again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I see that when I root, both IMEIs disappears. Very strange
Sent from my [device_name] using XDA-Developers Legacy app
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
pister said:
I see that when I root, both IMEIs disappears. Very strange
Click to expand...
Click to collapse
Mine both show. Not sure why yours have disappeared
liam_davenport said:
Mine both show. Not sure why yours have disappeared
Click to expand...
Click to collapse
Don't know. Tried to root by myself and the same happened
Sent from my [device_name] using XDA-Developers Legacy app
NateDev said:
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
Click to expand...
Click to collapse
If you have twrp already you don't need this I posted this for people that want root without using twrp, Just flash magisk 19.4 in twrp
There is a few guides in this forum section with all info you need on how to flash etc
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
mgear356 said:
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
Click to expand...
Click to collapse
You flashed it on Open beta 1?
liam_davenport said:
You flashed it on Open beta 1?
Click to expand...
Click to collapse
Yup open beta 1
Great thanks!
But can we update OTA to B2 with this?
@liam_davenport I'm sorry for the noob question, I just got my OP 7 Pro and never used one before, also, I've been away from everything root related for a long time.
Do I need to unlock the bootloader first in order to do this?

Question Hi friends!

Hi, sorry but I don't know English well, I was wondering if you could give me the download link of the TWRP for this phone, thanks ......
Redmi Note10 5G EEA
Frankie1975 said:
Hi, sorry but I don't know English well, I was wondering if you could give me the download link of the TWRP for this phone, thanks ......
Redmi Note10 5G EEA
Click to expand...
Click to collapse
Here:
https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
sorry not run....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Frankie1975 said:
sorry not run....
Click to expand...
Click to collapse
Why install the twrp since there is currently no flashed custom rom and there won't be any soon because of the mediatek soc which is little or not developed.
Have you unlocked the bootloader?
Frankie1975 said:
sorry not run....
Click to expand...
Click to collapse
There is no [recovery] partition on this phone.
yes i unlocked it, how do i recover the partition?
Frankie1975 said:
yes i unlocked it, how do i recover the partition?
Click to expand...
Click to collapse
this is A/B device it doesn't have recovery partition
Frankie1975 said:
yes i unlocked it, how do i recover the partition?
Click to expand...
Click to collapse
Reboot the phone to fastboot (Power + Vol Down)
Connect the phone to the computer using an USB cable (Preferred to use original cable that came with the phone)
Extract the fastboot files and open CMD/Terminal there.
Paste the twrp.img in the same folder.
Type' fastboot boot twrp.img' without the apostrophes.
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP.
But why?(Again).
If it is to change rom version use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
not running
Frankie1975 said:
not running
View attachment 5609485
Click to expand...
Click to collapse
https://www.droidwin.com/fix-status-read-failed-too-many-links/
changed drivers
changed cable
but it gives me the same two errors as before, even if I only write to the boot partition ....
Frankie1975 said:
changed drivers
changed cable
but it gives me the same two errors as before, even if I only write to the boot partition ....
Click to expand...
Click to collapse
Again why would you want to install the TWRP?
I am Italian and know little English I have no reference guides for your procedure ....
Frankie1975 said:
I am Italian and know little English I have no reference guides for your procedure ....
Click to expand...
Click to collapse
use google trad https://translate.google.fr/?sl=it&tl=en&op=translate
too dangerous .... with the twrp I finished the job, only the magicsk is missing, and I finished the root ..
Frankie1975 said:
too dangerous .... with the twrp I finished the job, only the magicsk is missing, and I finished the root ..
Click to expand...
Click to collapse
No need Twrp to root
and how do you install the magisk?
Frankie1975 said:
and how do you install the magisk?
Click to expand...
Click to collapse
1. Find or redownload the TGZ file for your current ROM
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
thanks for the support, but I have ascertained that I have problems with USB 3.0 I think that's all the problem, I'm very close to the solution, sorry but I leave your guide alone, if I have problems I will opt for your advice. Now I try the "fastboot boot twrp.img" with USB 2.0, then I say hello
Frankie1975 said:
thanks for the support, but I have ascertained that I have problems with USB 3.0 I think that's all the problem, I'm very close to the solution, sorry but I leave your guide alone, if I have problems I will opt for your advice. Now I try the "fastboot boot twrp.img" with USB 2.0, then I say hello
Click to expand...
Click to collapse
Usb 3 is not recommended, I already told you on a previous post.

Categories

Resources