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.
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!
----- TWRP -----
What is TWRP:
Open source touch based recovery.
http://teamw.in/project/twrp2
{
"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"
}
New version of TWRP v2.1.4 (31-05-2012):
Fixed weird colors
All function are working (including adb)
As fast as it gets
Theme I made is default (see 1st screen)
Please report bugs.
Known issues:
Theming works, but you gotta press the 'advanced->reload theme' button every boot.
Place ui.zip (do not extract) here: /sdcard/TWRP/theme/ui.zip. Reboot to recovery and press reload theme.
Ill try to fix theming on boot this week.
Install
Use fastboot to flash it (like normal recovery):
fastboot flash recovery recovery.img
Themes
ICS look
ICS look by XiproX
LG theme
----- CWM Touch -----
Single touch version under development by Napstar
About
Press thanks if you like this !!!
I don't like the slow downloadsites to make money, so a little donation would be nice
thomas1991_12 said:
Hi,
I'm new to android development but I have compiled twrp v2.1.4. for our lg gt540.
So we now have touch recovery
I haven't tested everything, so please report bugs.
Use fastboot to flash it (like normal recovery):
fastboot flash recovery recovery.img
Press thanks if you like this.
I don't like the slow downloadsites to make money, so a little donation would be nice
Click to expand...
Click to collapse
Thanks so much!!! Installing now and testing!
Thanks alot man !!! Can this recovery restore CWM backups ?? And why dont you try to make touch cwm recovery ?
smileydr0id said:
Thanks alot man !!! Can this recovery restore CWM backups ?? And why dont you try to make touch cwm recovery ?
Click to expand...
Click to collapse
Dont think so.. But you could try. I tried touch cwm but couldnt get touch input working. TWRP is good too
Sent from my GT540 using XDA
Confirmed. This recovery can't restore cwm backups because backups made with this recovery are in different format.
Good thing is that:
- backup's are faster (restore's too) than cwm
- can apply compression to backups so they will weigh less (207mb with TWRP vs 350mb of Cwm)
- can reboot into fastboot (in cwm don't)
- touch!!!!!!!
- can partition SD and set ext size and format.
- same features as Cwm recovery and more organized
Thanks for compile this recovery!!!
Sent from my GT540 using xda premium
You only have to make usb mount work and it will be perfect !!!!
so someone DID see the post i posted
Thanks for making this work!
great work i am waiting for this type of recovery bcz my volume butten is almost dead.sorry for my bad english
Sent from my GT540 using xda premium
maneshvinod said:
great work i am waiting for this type of recovery bcz my volume butten is almost dead.sorry for my bad english
Sent from my GT540 using xda premium
Click to expand...
Click to collapse
True story! Only difference is that my keyes are already dead
Anyone can try aroma installer on this recovery
Wysyłane z mojego GT-S5660 za pomocą Tapatalk 2
Fastboot is the only way to install this recovery.
I already try with android terminal and root toolbox.
The terminal returns error.
After both methods and reboot to recovery the phone goes to Fastboot mode.
I'll try fastboot later, because this is very interesting alternative recovery
10x
hmm? what error? is it to do with memory?
s-u-f-f-e-r said:
Fastboot is the only way to install this recovery.
I already try with android terminal and root toolbox.
The terminal returns error.
After both methods and reboot to recovery the phone goes to Fastboot mode.
I'll try fastboot later, because this is very interesting alternative recovery
10x
Click to expand...
Click to collapse
you CAN flash this with terminal emulator / adb shell (for example):
su
flash_image recovery /sdcard/recovery.img
If you want to interact with SDcard from your computer you can do this with ADB (instead of usb mount). There is a flag to disable USB mount for TWRP (TW_NO_USB_STORAGE) but i will leave it in for now.
Iam installed this recovery by using yaffsexpert.apk.try this apk works great for me
Sent from my GT540 using xda premium
Does it work with rom manager?
Sent by tT!
Check this out (cwm touch recovery for lg p500!!!):
http://forum.xda-developers.com/showthread.php?t=1633003
Maybe you can port it to our phone.
Anyone that has tested, how is this overall compared to CWM? I would like to try it, but I don't wanna keep flashing this, and rolling back to CWM.
Also could we get some screens up please.
delsus said:
Anyone that has tested, how is this overall compared to CWM? I would like to try it, but I don't wanna keep flashing this, and rolling back to CWM.
Also could we get some screens up please.
Click to expand...
Click to collapse
About the same functions as CWM, but faster backup/restore. And it is a bit faster because you have touch and don't have to scroll trough all the 'no's' in the CWM menu.
like thomas1991_12 said it has same options as cwm but with faster backup and restore,only thing that doesnt work is usb mount...
i took 2 pictures but im sry for bad quality cause i have only 5mpx camera
I'll check it out, always nice for new things
{
"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.
ARE YOU SEARCHING TO ROOT YOUR REDMI 2 ?
DISCLAIMER:DO THIS ON YOUR OWN. I'M NOT RESPONSIBLE FOR ANYTHING HAPPENS TO YOU AND YOUR DEVICE.PLEASE DONOT MIRROR THE LINKS
CLICK HERE FOR NATIVE ROOT
IF YOU ARE GETTING STOCK RECOVERY EVEN AFTER FLASHIN CWM, SEE THIS POST
STEP 1- FLASHING CWM ON YOUR PHONE
1.At first, you'll need the "adb" and "fastboot" tools. Get them HERE
2.Extract them into a folder, let's name it "Redmi2" (You can give your own name to the folder. That doesn't matter here.)
3.Now get the CWM .img file from HERE
You can use Philz Touch recovery also. Get HERE
4.Rename cwm.img or philz.img you downloaded above and as "recovery.img" and place it in the Redmi2 folder.
Now the folder will look like this-
{
"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"
}
5.Press and hold "shift" button and right click in the blank area of the folder and click on "open command promt window here". The command prompt will open.
6.Now turn off your Redmi2. Wait until it vibrates. After it's vibrated press and hold "Volume down and Power" keys together until it boots into "fastboot mode". Now connect the Redmi2 to your PC/Laptop through USB cable in fastboot mode itself.
7.Get to the command prompt now.
Now type: " fastboot devices " (without these- " " )
Like this-
8.Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command
9.Now enter the next command: " fastboot flash recovery recovery.img "
Like this-
10. Now this ends...
Type the last command: " fastboot reboot "
Like this-
11.Now your phone will reboot with ClockWorkMod(CWM) installed. CHEERS...
STEP 2- ROOTING YOUR PHONE
1. Firstly get the SuperSU.zip from HERE
2. Now copy the downloaded zip to your sdcard (not in any folder just in sdcard)
3. Boot into CWM recovery by turning off the phone and pressing "Volume UP and Power" button together after the phone vibrates.
4. Once CWM main menu is displayed, select "Install from zip" and browse to the zip that you downloaded earlier and select it.
5. Install the zip. If you get any warning, ignore and proceed.
6. After the installation is complete, reboot your device. (I think you can do that)
7. VOILA..!!! YOU ROOTED YOUR REDMI2
PLEASE HIT THANKS
JOIN OUR FACEBOOK GROUP HERE
CREDITS:
1. I don't claim any credit for "adb and fastboot tools" and the "recovery.img" and "SuperSu.zip"
2. Thanks to @subhrajiNath on Miui english forums who wrote the original guides.
Thread link is here and here
I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here
postadelmaga said:
I cannot connect to device using adb on ubuntu.
Any Idea ?
I have opened a thread about this issue here
Click to expand...
Click to collapse
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull
? not flashing ?
noobpremium said:
I'm really sorry man..I've never used ubuntu But I wish to...
Join the FB group and ask there...Maybe it can be helpfull
Click to expand...
Click to collapse
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )
postadelmaga said:
Ok my fault, It looks I miss the notification MIUI that ask me to allow my pc to dev mode...
Now I have another issue:
After I flash the recovery with flashboot I reboot into recovery but I still have the default one ... not CWM any idea what could be wrong ?
( I have already did this procedure on another phone, same issue but after doing it a couple of time something make the difference )
Click to expand...
Click to collapse
get "Flashify" app from playstore and first take backup of stock recovery and then flash the cwm with it. Thats it..
Actually I didn't knew this method before i made this guide..
Anyway, fastboot gives us a different feel, doesn't it? :v
wait I don't know flashify but it looks it needs root to flash the recovery ... but I think I need cwm to root ... so I think this is not gonna work ...
Ok got it, this may be useful to anybody face the issue with recovery:
I discovered you can workaround the issue in this way:
Temporary boot into CWM:
HTML:
fastboot boot recovery.img
Root the device using CWM
Flash CWM using flashify
[ CWM when you log out ask you for root so maybe it is not necessary to use the zip file ( but I'm not very expert so maybe I'm wrong)]
You can install GAPPS with CWM `gapps-kk-20140606-signed .zip` but be careful, whenever you update MIUI you will look all software installed using CWM. ( superSu and GAPPS for example )
thanks
thanks!
eienkisu said:
thanks!
Click to expand...
Click to collapse
Pleasure
Okay bro :good:
I'll update the OP
I confirm #postadelmaga the CWM recovery does not stay, the only way to do access it is the fastboot boot recovery.img Here's how I succeeded with two phones now.
power on, start wifi, do Miui updates
install ADB or the files above on PC
reboot to fastboot with voldown+pwr
now comes fastboot boot recovery.img
in CWM, sideload SuperSu and Gapps
connect you preferred VPN (if in China)
install and update all Google apps needed
delete most Chinese apps
hey i m unable to flash recovery plzz help
Device version 2014818
Sent from my 2014818
Hi buddy could you plz port touchwiz from galaxy prime?
The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.
not working.
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.
godwintgn said:
I tried this method. its stuck with flashing the recovery image. always showing flashing the recovery image.... that's all.
Click to expand...
Click to collapse
Are you on win7? I got this same issue on my win7... try on win8 it works flawlessly
Please hit thanks if done
Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.
Shrihari007 said:
Hi buddy could you plz port touchwiz from galaxy prime?
Click to expand...
Click to collapse
TW sucks man.. why do you want it :/ anyways I'll try
leuk_he said:
The simpler solution is to use the xiaomi update tool and flash a developer rom that has builtin root.
http://xiaomi.eu/community/threads/5-4-10.27429/
howto & root from permissions menu:
https://watchpage.wordpress.com/201...redmi-note-4g-developers-roms-version-miui-6/
But to have the cwm running on the phone is always a safe bet for some recovery actions.
Click to expand...
Click to collapse
Thanks to you bro.. I'll update the OP for those who are facing some issues with my guide's precedure..
OP Updated
I've updated the OP with the other guide's link.. please check it out if you're having some issues with this one
godwintgn said:
Ya bro I am using Windows 7. I don't have Windows 8. Thanks for the info.
Click to expand...
Click to collapse
Try on some friend's PC or something
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?