Thanks to agentdr8! He made a Linux version for you guys! Download link below!
Like every developer says:
I AM NOT HELD RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE!
Click to expand...
Click to collapse
What is FFW?
FFW is a script written in batch that will automatically wipe your phone, leaving no traces of the past install.
Click to expand...
Click to collapse
What does it do?
I'll pretty much sum it up like this, it erases the boot, system, userdata, cache, webtop, preinstall, and reboots the phone.
Click to expand...
Click to collapse
Notice:
There are two versions, Fastboot & Moto-Fastboot, I don't know the difference but I made a script for each version. The whole package is there, just download, extract, and run the batch file!
Click to expand...
Click to collapse
Instructions:
1. Download any of the two versions.
2. Boot into recovery.
3. Wipe the Dalvik cache.
4. Wipe the cache.
5. Factory reset/data your phone.
6. Boot into fastboot.
7. Run the script.
8. Your done!
You can now install any ROM you choose! Be carefull for hard/soft bricks, installing the wrong ROM can ruin your phone!
Click to expand...
Click to collapse
Screenshots:
Fastboot Full Wipe
{
"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"
}
Moto-Fastboot Full Wipe
Download:
Multiupload is now useless! Download everything from Mediafire!
Newest!
FFW Linux: 3.2
New-
FB Full Wipe: 2.1
MFB Full Wipe: 2.0
Older-
FB Full Wipe: 1.1
MFB Full Wipe: 1.0
Click to expand...
Click to collapse
Mini key
x.0 Moto-Fastboot (Windows)
x.1 Fastboot (Windows)
x.2 Fastboot (Linux)
Click to expand...
Click to collapse
Who helped make it?
Alaq - Me - The script.
CaelanT -This.
agentdr8 - The Linux version of the script!
Click to expand...
Click to collapse
Build 2.0/2.1:
Code:
-Fixed devices check
--Now there is a pause to allow you to see if your phone is connected correctly or not
Build 1.0/1.1:
Code:
-Full Wipe text logo added
-Echo used to give info
-Pause used to give user a last minute choice to wipe or not
-Pause used to give user a choice to reboot phone or not
-Formats:
--boot
--system
--userdata
--cache
--webtop
--preinstall
Thread Edits/Revisions:
12/31/11- OP Created
12/31/11- Pictures added
Script Edits/Revisions:
12/29/11- Fastboot Full Wipe Created
12/30/11- Moto-Fastboot Full Wipe Created
Alaq said:
What is FFW?
What does it do?
Notice:
Instructions:
Screenshots:
Fastboot Full Wipe
Moto-Fastboot Full Wipe
Download:
Who helped make it?
Click to expand...
Click to collapse
Thanks for the script.
Sent from my MB860 using Tapatalk
Alaq said:
There are two versions, Fastboot & Moto-Fastboot, I don't know the difference but I made a script for each version. The whole package is there, just download, extract, and run the batch file!
Click to expand...
Click to collapse
Moto-Fastboot is just like Fastboot except that it can handle larger flash image files, such as the webtop image (which is too big for Fastboot to handle).
MJPollard said:
Moto-Fastboot is just like Fastboot except that it can handle larger flash image files, such as the webtop image (which is too big for Fastboot to handle).
Click to expand...
Click to collapse
Alright, thanks for the info. I guess Moto-Fastboot is better, but I'll keep both versions up for the people that want them...
Thanks! Great script.
Why not rebooting into the recovery at the finish ? (you want to flash roms at the end ..)
Thank you ! looks great !
PakaPakaxz said:
Why not rebooting into the recovery at the finish ? (you want to flash roms at the end ..)
Thank you ! looks great !
Click to expand...
Click to collapse
You know I thought of that... But in all of my searching I haven't found any command that would do it... I tried "moto-fastboot reboot recovery"... Thanks for the idea though, I'll figure it out eventually!
I think you'd have to use the following arguments:
boot your_recovery.img
I can't remember exactly, but i think that's it.
itsonlym3 said:
I think you'd have to use the following arguments:
boot your_recovery.img
I can't remember exactly, but i think that's it.
Click to expand...
Click to collapse
That would be kinda hard since this doesn't flash a recovery...
Alaq said:
That would be kinda hard since this doesn't flash a recovery...
Click to expand...
Click to collapse
i tried it with one i had, it doesn't reboot. i thought it would, my bad.
It's alright, thanks for trying though!
Build 2 now out! Not much upgraded, just added a confirmation screen so you can make sure your phone is connected properly.
Alaq said:
Build 2 now out! Not much upgraded, just added a confirmation screen so you can make sure your phone is connected properly.
Click to expand...
Click to collapse
dropbox barfing saying too much traffic
dicksteele said:
dropbox barfing saying too much traffic
Click to expand...
Click to collapse
Uploaded to Multiupload! Go check the OP for new download links.
Posting so I can use this later and refer people to this as well.
Excellent!!!
Thanks.
Perfect !!
Sent from my MB860 using xda premium
Alaq, hope you don't mind but I modded your script for linux users. See attached.
Linux fastboot binary included as well.
agentdr8 said:
Alaq, hope you don't mind but I modded your script for linux users. See attached.
Linux fastboot binary included as well.
Click to expand...
Click to collapse
Nice! I'll add it to the op!
Related
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!
Originally posted by Koushik Dutta on Google+:
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes: update from 09.05.11
Fix the fact that some users were loosing root access with 5.0.1.0
Fix menu bug Even if you select no during wipe dalvik cache, it still says it wipes it (it is not actually wiping it, it is just a display bug)
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
Click to expand...
Click to collapse
To flash recovery for Nexus S, download recovery and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
ill try
Sent from my Google Nexus S using XDA Premium App
I'm on it!
Or you can directly flash it from Rom Manager
You can also just put it on SD and flash from terminal then reboot.
Edit- before someone asks
su(press enter)
flash_image recovery /sdcard/5014cw.img(press enter)
reboot recovery(press enter)
Obviously the sdcard/* is whatever you rename the file
sent from my nexus s on a kang from simms
zadnica said:
Originally posted by Koushik Dutta on Google+:
To flash recovery for Nexus S, download recovery and place it into your sdk tools folder. Reboot into bootloader and execute:
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
I wish I would have seen this BEFORE I updated. It kept taking me to bootloader screen!!!!! But I unistalled and installed and finally got it to work!
Sent from my Nexus S using Tapatalk
Hey guys,
Everytime I restore from a backup through Rom Manager with the new recovery, I lose root. Right now, I'm stuck at work and cannot flash a rom, theme, battery mod, etc. I'll go back to 4.0.1.4 as soon as I go home
Am I the only one?
Edit: Found a solution==> Reboot into Recovery, flash su.zip again, and it's all good now!
f.
suhas_sm said:
Or you can directly flash it from Rom Manager
Click to expand...
Click to collapse
doesn't work for me..
I always recommend not using rom manager for anything flashing related, most problems occur for people when they're using rom manager and get fixed when done through recovery or in this case terminal/adb
RevengeITA said:
doesn't work for me..
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
sinik420 said:
I always recommend not using rom manager for anything flashing related, most problems occur for people when they're using rom manager and get fixed when done through recovery or in this case terminal/adb
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
I prefer my previous post using terminal
zadnica said:
Code:
fastboot flash recovery recovery-clockwork-5.0.1.0-crespo.img
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
It took me two or three tries through terminal
Robin_216 said:
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
Click to expand...
Click to collapse
sent from my nexus s on a kang from simms
Robin_216 said:
When i try to flash this through android terminal i get a whole bunch of errors saying that its out of memory. Any solutions? I also tried using rom manager and ended up with no recovery instead of a new version
Click to expand...
Click to collapse
What the errors?
Worked like a charm thanks
Backups are significantly faster, thanks. (Flashed using fastboot)
zadnica said:
What the errors?
Click to expand...
Click to collapse
{
"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"
}
These are the errors that appear. I however managed to flash it with rom manager after some tries so it works now.
Sent from my Nexus S using XDA App
Robin_216 said:
These are the errors that appear. I however managed to flash it with rom manager after some tries so it works now.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I had the same issue. What helped for me was (in Terminal) :
su
mount -o rw,remount /dev/block/mtdblock3 /system
chmod 755 /system/bin/flash_image (wait for a minute)
(Reboot if the next step didn't work)
flash_image recovery /sdcard/RECOVERY.img
Click to expand...
Click to collapse
If I use the latest one, can I boot into recovery by using Rom manager? Will Rom manager detect my latest clockworkmod?
Accidentally sent from my Nexus S using XDA Premium App
Strangely, *immediately* after flashing the new recovery, I have begun to experience the Nexus S Google Voice Search bug. In the two months I've had the phone, this never happened - not even once.
This was with a two week old CM nightly, and a Matrix kernel.
Regardless - I'm hoping we'll start to see 2.3.6 kernels/roms come out soon which will fix it permanently. I'm just shocked that this issue popped up immediately after flashing the updated Clockwork.
{
"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.
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?
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.