hi,
my phone freezed the other time after wiping (becasue I had a screen issue ) and glevitan helpfully flashed an unbranded rom back ( with the hack kit or something ) .
I fixed my screen so there shouldn't be any issues now and just wasn't too sure about flashing to get back my previous rom.
details of phone now
{
"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 checked my SD card and there's a clockworkmod folder with the files .android_secure.vfat (357,525 KB RAR) ,cache.ext4 ( 5KB RAR) , data.ext4 ( 489,783 RAR) , system.ext4 ( 424,852 KB RAR) , boot.img ( 4,096 KB IMG file) , fsinfo (1 KB file), nandroid.md5 (1 KB MD5 file) , recovery.img ( 8,701KB IMG file ) . anything i can do with them? they were the backup I did prior to my wiping disaster earlier.
I also have an ARHD 6.3.3 rom zip on my SD card too.
my volume button is spoilt. I installed 4Ext touch recovery , wanted to update it and it mentioned it needs busybox box from google play , which in turn requires root. So I can just download that , update the 4Ext touch recovery for use ?
thanks !
this too if it's of any use
I'm assuming you flashed 4ext from fastboot? You could restore your CWM backup from 4ext (I'm assuming that your 4ext isn't so old that the backup isn't compatible). Then you would have a rooted ROM. Or clean flash your ARHD.
no, I didnt flash the 4Ext from fastboot. I installed the 4Ext apk as per normal on my SD card after I got my screen repaired. It wasn't really outdated ( probably last month), but actually I can uninstall this and get a new copy from the site and install that too. Do I still have to download busybox or SuperSu , then clean flash the ARHD copy on my SD card ?
If you still have a custom recovery, go ahead and try to restore the backup. Or if you flash ARHD it is already rooted with busy box.
oh, so if I'm doing a clean flash of that arhd , I can use the 4ext recovery to wipe and then flash that without needing to download anything else ? thanks
whateheck said:
oh, so if I'm doing a clean flash of that arhd , I can use the 4ext recovery to wipe and then flash that without needing to download anything else ? thanks
Click to expand...
Click to collapse
Yes.
Here's how you install 4ext: http://www.youtube.com/watch?v=Ih5orslc-4M
If you want you can install a CWM touch recovery instead and do everything as before on the original CWM only no need for the volume keys.
You can install CWM with this app form the market very easily: https://play.google.com/store/apps/details?id=com.simran.recmanager&feature=search_result
After doing that when you want to install a new ROM do a full wipe and flash on! Good luck!
i think it'll ask me to install busybox too if I click on update etc.
So I should be good to go from there ?
otherwise I'll have to have a go at the CWM. you mean to install by flashing cwm touch recovery from the Recovery Manage app, ilans93 ? I haven't used this before - just looked at the page and it's last updated was Feb last year.
I'm not sure if you still have a custom recovery. You could check by connecting your phone to your computer and using adb: adb reboot recovery.
If you don't, you need to fastboot flash a recovery first. Check the DHD General forums, Ace Think Tank guide, bottom of page 9, the section "S-Off no custom recovery." If you want 4ext download the image from their website and use that instead of the CWM image. Then flash ARHD from the recovery.
bananagranola said:
I'm not sure if you still have a custom recovery. You could check by connecting your phone to your computer and using adb: adb reboot recovery.
If you don't, you need to fastboot flash a recovery first. Check the DHD General forums, Ace Think Tank guide, bottom of page 9, the section "S-Off no custom recovery." If you want 4ext download the image from their website and use that instead of the CWM image. Then flash ARHD from the recovery.
Click to expand...
Click to collapse
yes, I should have the custom recovery. as mentioned in 1st post , I have a folder on my SD card "clockworkmod" with the files .android_secure.vfat (357,525 KB RAR) ,cache.ext4 ( 5KB RAR) , data.ext4 ( 489,783 RAR) , system.ext4 ( 424,852 KB RAR) , boot.img ( 4,096 KB IMG file) , fsinfo (1 KB file), nandroid.md5 (1 KB MD5 file) , recovery.img ( 8,701KB IMG file ). that's the backup my previous 4ext did before I wiped and got stuck that time.
So i have to copy the recovery.img file to the PC adb folder and flash it ?
whateheck said:
yes, I should have the custom recovery. as mentioned in 1st post , I have a folder on my SD card "clockworkmod" with the files .android_secure.vfat (357,525 KB RAR) ,cache.ext4 ( 5KB RAR) , data.ext4 ( 489,783 RAR) , system.ext4 ( 424,852 KB RAR) , boot.img ( 4,096 KB IMG file) , fsinfo (1 KB file), nandroid.md5 (1 KB MD5 file) , recovery.img ( 8,701KB IMG file ). that's the backup my previous 4ext did before I wiped and got stuck that time.
So i have to copy the recovery.img file to the PC adb folder and flash it ?
Click to expand...
Click to collapse
Thats the backup file, and it is located at /sdcard/clockworkmod/backup, but in order for you to be able to restore the backup, you must have recovery.. like bananagranola said, you need to flash the recovery first if you didnt have it, or just go to the recovery ( ext4 recovery or cwm depends on what you have installed) and restore the backup..
whateheck said:
otherwise I'll have to have a go at the CWM. you mean to install by flashing cwm touch recovery from the Recovery Manage app, ilans93 ? I haven't used this before - just looked at the page and it's last updated was Feb last year.
Click to expand...
Click to collapse
Exactly. The app does everything for you. There is no need to update the market app because it works perfectly, he only updates the online databases. Trust me, everything is up to date.
Note that the CWM touch can't install the new ViperDHD 2.0.0 ROM. For that you'll need 4ext or TWRP. I switched to TWRP and it's pretty good. I recommend you install it.
The way you install TWRP as easily as possible is to download GooManager from the Play Store (https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5zMHVwLmdvb21hbmFnZXIiXQ..) , run the app, hit menu and select "Install OpenRecoveryScript".
ilans93 said:
Exactly. The app does everything for you. There is no need to update the market app because it works perfectly, he only updates the online databases. Trust me, everything is up to date.
Note that the CWM touch can't install the new ViperDHD 2.0.0 ROM. For that you'll need 4ext or TWRP. I switched to TWRP and it's pretty good. I recommend you install it.
The way you install TWRP as easily as possible is to download GooManager from the Play Store (https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5zMHVwLmdvb21hbmFnZXIiXQ..) , run the app, hit menu and select "Install OpenRecoveryScript".
Click to expand...
Click to collapse
does that recovery manager require root ? i'm only S-off i suppose. (and without volume button )
yumm91 said:
Thats the backup file, and it is located at /sdcard/clockworkmod/backup, but in order for you to be able to restore the backup, you must have recovery.. like bananagranola said, you need to flash the recovery first if you didnt have it, or just go to the recovery ( ext4 recovery or cwm depends on what you have installed) and restore the backup..
Click to expand...
Click to collapse
oh , realised my mistake
bananagranola said:
I'm not sure if you still have a custom recovery. You could check by connecting your phone to your computer and using adb: adb reboot recovery.
If you don't, you need to fastboot flash a recovery first. Check the DHD General forums, Ace Think Tank guide, bottom of page 9, the section "S-Off no custom recovery." If you want 4ext download the image from their website and use that instead of the CWM image. Then flash ARHD from the recovery.
Click to expand...
Click to collapse
tried adb reboot recovery and I indeed didnt have custom recovery. it rebooted and I got a factory reset phone back - had to relog google market etc.
you mean to look at gevitan's ace guide , isn't it - i was looking at the pg 9 thread for a while and saw nothing related ( default forum number of posts per page ) , then realised gevitan's guide on pg 9 for "14. Stuck in the splash screen " seemed more probable .
"
S-OFF with custom recovery: Get a custom rom in your sdcard and flash it.
S-OFF no custom recovery: You need to re flash a custom recovery to be able to flash a custom rom again. Follow these steps:
1) Boot in hboot and choose fastboot.
2) Plug the phone to the pc (you have to see fastboot usb in red in the phone)
3) Open a cmd as admin or terminal as root in the PC.
4) Type (case sensitive):
5) wget http://db.tt/YV7fTEx7 --no-check-certificate (wait until the download is ready)
6) Fastboot oem rebootRUU (that will put your phone in RUU mode, with a black screen with silver HTC)
7) Fastboot flash zipcwm-5.0.2.7-ace.zip (it will send the file first and then flash it)
8) When you see OKAY. Finished (near the bottom in the cmd session even if the green bar in the phone is at half way)
9) Fastboot reboot-bootloader.
10) VOILÁ…check and you should have CWM again.
"
the DB link expired , but in any case, I need a touch recovery since my volume button can't work.
I looked around and saw this thread on CWM touch recovery : http://forum.xda-developers.com/showthread.php?t=1474490
then again, the steps are slightly different too - I'm not too sure about the ENG s-off and whatnot.
but if i follow gevitan's guide, I should need a CWM touch in "zip" file format ? i looked at the CWM site and it only has the img file - do i need to change anything ?
thanks!
Edit: I was wrong. See the link below for the correct way.
http://forum.xda-developers.com/showthread.php?p=37630169
Related
{
"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"
}
All credit for this software goes to the dev (Koushik Dutta and anyone else on his team).
** Nandroid backups made on previous versions of CWM cannot be restored in CWM 5.0.x.x. So if you have backups made in versions 2.5.x.x or 3.0.x.x, you will not be able to restore them once you've upgraded. **
HOMEPAGE
ClockworkMod.com
DOWNLOAD
Standard recovery
Link: recovery-clockwork-5.0.2.0-glacier.img - Rename to "recovery.img" for easier CLI entry
MD5: a5aea82ec2ad7b836c9c179fce0d520d - To verify, use ManD5 or the below ADB commands:
Touch recovery
Link: recovery-clockwork-touch-5.8.1.0-glacier.img - Rename to "recovery.img" for easier CLI entry
MD5: 687998d5093878147256c10ae9e98e5a - To verify, use ManD5 or these ADB commands:
Code:
adb push recovery.img /sdcard/recovery.img
adb shell md5sum /sdcard/recovery.img
INSTALLATION
- Via the ROM Manager app (version 4.4.0.3 or newer required)
- Via terminal emulator:
Code:
Move recovery.img to the root of your sdcard
Start the terminal app
su (press enter)
flash_image recovery /sdcard/recovery.img (press enter)
reboot recovery (press enter)
- Via fastboot (ADB installation and engineering bootloader version 0.85.2007 required):
Code:
Move recovery.img to a location where fastboot can find it.
Boot your phone into fastboot mode
Connect your phone via USB to your computer
fastboot devices
fastboot flash recovery recovery.img
CHANGE-LOG
5.0.0.1 through 5.0.1.0
Backups now use tar over yaffs for everything except mtd partitions. Backup speed improved.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type.
New color scheme
Status bar when backing up working again
Backing up of .android_secure working again
5.0.2.0
Bug-fix: root no longer lost on rom restore
5.8.0.9
Touch version - initial release (beta stage)
5.8.1.0
Major bug fixed (recovery.fstab malformed)
I'm not in any way responsible if something happens to your device. I'm simply posting this as a courtesy to the community.
I still don't know how this flew over our heads.
Either way, glad you provided every possible method to upgrade.
mackster248 said:
I still don't know how this flew over our heads.
Either way, glad you provided every possible method to upgrade.
Click to expand...
Click to collapse
Was there a 4.0? I was still on 3.0.24 still, and now I find out about this version. does anyone know its new features?
Ace42 said:
Was there a 4.0? I was still on 3.0.24 still, and now I find out about this version. does anyone know its new features?
Click to expand...
Click to collapse
As far as I know, the jump was made straight from 3.0.2.4 to 5.0.0.1. I have yet to see a changelog, but if anyone finds one, I'll add it to the OP. After poking through the menus, nothing obvious stood out, so it seems to be a bug fix and "behind the scenes" release.
-From Mr.Dutta via G+
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
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!
Thanks for the heads up. Just flashed via rom manager without any issues.
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
epolaris said:
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
Click to expand...
Click to collapse
I'm not quite sure if that's a bug. Since there's a lot of internal changes, I'm assuming the path it takes from Android to CWM has changed. So maybe that's why we're stuck at the splash screen.
But that's not too big of a problem. So far it's much faster than the previous versions.
WOW! I just did a backup of my current Rom and it literally took like 1 minute! It's WAY faster now.
epolaris said:
I decided to flash the upgrade. The flash went perfectly. However, I can't boot into recovery while within Android. I have to power off and boot into the bootloader and then select recovery... Whenever I try to reboot to recovery via the Android UI, it reboots and hangs at the boot splash screen.. It doesn't even work if you select the option from the ROM Manager itself just hangs... I rolled back to previous version and its working again...
Possible bug??...
Click to expand...
Click to collapse
I'm not having that issue at all. I can reboot into recovery using the power menu within Faux's 1.3.1 rom and it works perfectly. I can't speak about other roms, but just letting you all know that Faux's latest works fine.
<EDIT EDIT>
lol wrong forum.
updated to 5.0.0.1. seems pretty neat.
This new recovery backs up roms really fast. With the old version it used to take my phone 2 to 3 minutes to back up. Now about a minute. Its actually kind of scaring me. I don't know if its backing it up correctly. I'm affraid to restore lol.
Sent from my HTC Glacier using xda premium
coupetastic-droid said:
This new recovery backs up roms really fast. With the old version it used to take my phone 2 to 3 minutes to back up. Now about a minute. Its actually kind of scaring me. I don't know if its backing it up correctly. I'm affraid to restore lol.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I posted the changelog on the 1st page.
"I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
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!"
I also added the info from his Google+ page to the OP.
Any information on whether other built in tools such as sdparted were updated too? I have been having a lot of trouble with my SD card (I couldn't get it to format through sdparted because of some error I can't remember) and the option to partition your SD card through ClockWorkMod Recovery 3.x didn't allow to set EXT to a size of 0. I was able to partition my card the way I wanted through sdparted after flashing the new 5.0.0.1 recovery, but was curious as to whether there was a change within the recovery img that allowed me to finally partition the way I wanted or if the change was something else that caused my SD card to start functioning correctly.
bstapley said:
I'm not having that issue at all. I can reboot into recovery using the power menu within Faux's 1.3.1 rom and it works perfectly. I can't speak about other roms, but just letting you all know that Faux's latest works fine.
Click to expand...
Click to collapse
+1 Same here
Sent from my HTC Glacier using XDA Premium App
Ace42 said:
I posted the changelog on the 1st page.
"I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
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
just did a restore and everything went perfectly fine. thanx.
I was just wondering that when I flash a rom and it calls for 3.0.2.4 recovery do I still use that or can I use the new recovery..I know it's a dumb question but just want to make sure
Sent from my virtuous doubleshot glacier using XDA App
darksoul0013 said:
I was just wondering that when I flash a rom and it calls for 3.0.2.4 recovery do I still use that or can I use the new recovery..I know it's a dumb question but just want to make sure
Click to expand...
Click to collapse
Shouldn't be a problem. Nothing was changed that would make affect how a ROM is flashed.
WARNING!
THIS NO LONGER WORKS FOR VERSIONS 4.8.184 and up.
It will continue to work as long as you don't mess with it or reflash your recovery if it's already working for you but for newer versions or ROM Manager it's even easier!
Alquez now has Unofficial Official Support!!!
For newer versions simply do the following to allow full functionality in ROM Manager and ROM Manager Premium:
1/ Flash Alquez's Unoffical 5.0.2.6 ClockworkMod recovery
2/ Install ROM Manage from the marketplace
3/ Click on Option 1 to flash CWM recovery in ROM Manager
4/ Choose "Upsupported Device"
5/ Choose "3.x"
6/ You're done!
Video Tutorial And Proof it works here.
First off. Some warnings!
*This generally works but you COULD possibly have to do a nandroid restore of your system so BACK up before you attempt!
*This DOES NOT allow you to flash downloadable ROM's from within Rom Manager!!! There are no downloadable roms for the Wildfire S. The one's you see will be for the HTC Aria!!!
*This does not allow you to use the experimental and other CWM Recoveries available from within Rom Manager!!!
What this does do:
*Allows you to make PROPER format Nandroid backups that will work in programs like Titanium Backup, etc (Although TBP now has support for "exotic" CWM files like CWMU 5.0.2.6.
*Allows the following features in Rom Manager:
-Reboot Into Recovery (Will boot into 5.0.2.7 though)
-Install ROM from SD Card
-Manage And Restore Backups
-Backup Current ROM (The most important as this method creates a by the book Nandroid backup unlike creating one from inside Unofficial 5.0.2.6)
-Fix Permissions
-Partition SD Card
How to achieve this trick and where it came from:
*Credit for the this trick goes to Insink72 and myself. Insink72 played around in Rom Manager and it started working for him. He managed to remember at one point he flashed the HTC Aria image so I figured out what he did and made it a confirmed process that can be replicated if instructions are followed.
What you are going to do is to install Unofficial CWM Recovery via hboot, install ROM Manager, then through ROM Manager leave some HTC Aria ghost code in place that enables some functions lost in the ported Unofficial version while keeping the majority of your recovery as Alquez's Unofficial 5.0.2.6
ROM Manager is going to think, and in a way it's right, that you actually have 5.0.2.7 installed.
Ready?
1/ Download Alquez's Unofficial ClockWorkMod Recovery 5.0.2.6
2/ Place the PG76IMG.zip file on your SD card's root folder
3/ Power down.
4/ Remove and replace battery
5/ Press Volume Down and Power at the same time to boot into hboot
6/ When it finds the PG76IMG.zip press volume up to flash it and reboot the phone.
7/ Boot to the OS and download Rom Manager from the Android Market and install it.
8/ Run ROM Manager
9/ Choose the first option "Flash ClockworkMod Recovery"
{
"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"
}
10/ From the list choose "HTC Aria"
11/ When done power down again
12/ Remove and replace battery
13/ Press Volume Down and Power to boot into Hboot
14/ Press Volume Up to AGAIN flash Unofficial 5.0.2.6 recovery
15/ Reboot phone and go into operating system (At this point look at troubleshooting below if it doesn't boot)
16/ Rename or remove the PG76IMG.zip from your SD card's root folder (I rename mine to CWMPG76IMG.zip and leave it there)
17/ Go to Rom Manager. It should say you now have 5.0.2.7 installed
That's it! You inserted the remaining code required to backup your rom from ROM Manager!
To verify it choose "Backup Current ROM then click ok. it should reboot to the ghosted bit of 5.0.2.7 code in ugly green and pink and start making a NANDROID backup followed by an auto reboot.
If you reboot into recovery it should boot to the nicely coloured 5.0.2.6
Troubleshooting:
If your OS gets stuck on the boot splash screen (not very likely but can happen):
1/ Power Down
2/ Remove the PG76IMG.zip from your SD card using a card reader and and computer or via fastboot USB in the phone
3/ Replace SD card and replace battery
4/ Volume down and Power to get to Hboot then enter recovery 5.0.2.6
5/ Wipe Data/Factory Reset
6/ Mounts and Storage/Format System
7/ Advanced/Wipe Dalvik Cache
8/ Backup and restore/Restore your last backup made before the freeze.
9/ Reinstall ClockworkMod Rom Manager from Android Market
Good to go!
PLEASE CLICK THANKS IF THIS HELPED YOU!
Hi there. Tried this trick and it works...but...when i select Reboot to recovery in ROM Manager it boots 2.5.0.7 by CWM and when via Bootlader 2.5.0.6 by alquez. Is it normal?
UPD
I've readed tutorial carefully and found an answer
morozzkin said:
Hi there. Tried this trick and it works...but...when i select Reboot to recovery in ROM Manager it boots 2.5.0.7 by CWM and when via Bootlader 2.5.0.6 by alquez. Is it normal?
Click to expand...
Click to collapse
Says that right in the tutorial. Yes it's normal.
*Allows the following features in Rom Manager:
-Reboot Into Recovery (Will boot into 5.0.2.7 though)
Click to expand...
Click to collapse
If you liked it please click thanks.
Thanks, worked like a charm
Nice tut. Correct me if I'm wrong, but if you have the unofficial installed, can't you just hit settings in ROM manager and manually override as an aria?
Sent from my HTC_A510c using Tapatalk
I put the PG76IMG.zip on Sd card, but didnt work.
"Main version is older
Update faild
Press power button to reboot."
I put the PG76IMG.zip on the SD card, remove-insert the battery, start-vol_down
but on the screen there are the error:
C I D incorrect!
Update Fail!
Press <POWER> to reboot.
My phone is S-On, unlocked by HTC-dev, and rooted with supertool v3
how i can install the recovery?!?!
thx for answer
Nice tutorial man! Ty
ares7610 said:
I put the PG76IMG.zip on the SD card, remove-insert the battery, start-vol_down
but on the screen there are the error:
C I D incorrect!
Update Fail!
Press <POWER> to reboot.
My phone is S-On, unlocked by HTC-dev, and rooted with supertool v3
how i can install the recovery?!?!
thx for answer
Click to expand...
Click to collapse
s-on means its locked, u didn't unlock it properly ... thets why u get cid error...
b02 said:
s-on means its locked, u didn't unlock it properly ... thets why u get cid error...
Click to expand...
Click to collapse
Uh, s-on is still there after unlocking. Bootloader unlock does NOT give S-OFF.
via HTC Wildfire S powered by CM7.2
ah, my bad then... then its not fully unlocked if u cant put recovery ?
b02 said:
ah, my bad then... then its not fully unlocked if u cant put recovery ?
Click to expand...
Click to collapse
You CAN put recovery, roms and obv root. Only sim lock is there and u cant flash radio if u have unlocked by htcdev.
via HTC Wildfire S powered by CM7.2
Sorry for my misunderstanding.
I'm really confused, and maybe this reply is OT, but i don't have understand if
i can use Clockwork on WFS ( in the market version i don't see the WildFire S phone)
and,
the real problem, i don't know how i can FULL DUMP the actual original rom present in my phone.
If i have understand well, i can't install the recovery because my phone have S-ON, but i can install other rom.
In this case i can install a new rom, but i can't make a full dump.
It's correct?
Sorry again for OT reply, and thank you very much for your patience
ares7610 said:
Sorry for my misunderstanding.
I'm really confused, and maybe this reply is OT, but i don't have understand if
i can use Clockwork on WFS ( in the market version i don't see the WildFire S phone)
and,
the real problem, i don't know how i can FULL DUMP the actual original rom present in my phone.
If i have understand well, i can't install the recovery because my phone have S-ON, but i can install other rom.
In this case i can install a new rom, but i can't make a full dump.
It's correct?
Sorry again for OT reply, and thank you very much for your patience
Click to expand...
Click to collapse
You can use clockworkmod with htcdev unlock, you only need to download the one from alquez and flash it in bootloader or with fastboot.
If you got it you can backup yours and flash new roms with it.
This tut here is just a little hack to get rommanager and clockworkmod work together even if it's not officially supported.
Swyped from my desire s far away from my pc
I put the PG76IMG.zip on Sd card
"Main version is older
Press power button to reboot."
Update faild
New tutorial and video tutorial and proof of the new Rom Manager full support working in first post...
d33ps1x said:
New tutorial and video tutorial and proof of the new Rom Manager full support working in first post...
Click to expand...
Click to collapse
Cool update from clockworkmod.
*se-nsei. said:
Cool update from clockworkmod.
Click to expand...
Click to collapse
I tested backup , reboot to, restore, install zip from, and they all work great.
This is definitely cool.
superuserx said:
I put the PG76IMG.zip on Sd card, but didnt work.
"Main version is older
Update faild
Press power button to reboot."
Click to expand...
Click to collapse
Extract the recovery from the zip file ans flash it via fastboot flash recovery recovery.img
I have the ROM Manager with CM7, but I don't really get why it's here... Sounds like the recovery mode? Will I keep my settings/apps/etc if I install a new update or a new ROM?
{
"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"
}
Disclaimer:
By flashing this recovery you take full responsibility to whatever happens on your device. The developer will NOT be held responsible to whatever happens on your device. Ofcourse, the recovery has been tested but whatever happens on your device will not be held against the developer.
What Is CWM Recovery ?
CWM recovery is a way that enables you to falsh a custom rom , customize your rom and can save you from bad situations. To Be fully in controll of your android device you need a recovery and this is one of them.How To Install CWM Recovery ?
There are 2 methods for installing CWM
1.Method (dd method)
You need root before you continue.
now copy recovery.img from second post to your sd card and :
1.On PC :
Make shure that device is on usb debugging mode.
Plug device and open Terminal/command prompt.
Copy Pasta the Following Commands :
PHP:
adb shell
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6
make shure that partion is mmcblk0p6 or you will brick device !
now you can reboot to recovery (volume up + home +power) and enjoy CWM 6.0.4.4
2.On Phone :
First Download Terminal Emulator From Play Store.
Plug device and open Terminal apk
Right the Following Commands :
PHP:
su (you need root acess for it )
Then
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6
make shure that partion is mmcblk0p6 or you will brick device !(guys with fat fingers stay away !)
now you can reboot to recovery (volume up + home +power) and enjoy CWM 6.0.3.3
Second Method Is Via ODIN.
First Download ODIN
Now Download the N8000/N8013-CWM-6.0.4.4.tar From Second Post and put it in same directory as odin.
Go To Download Mod (Volume Down +Home+Power) and plug device.
Now in Odin You Will see {added} and a light blue figure on top that means that device has been recognized if you dont get them uninstall devices drivers and retry.
Now click PDA and select N8000/N8013-CWM-6.0.4.4.tar And Then Click Start .
After Device reboots Your Done and CWM Is Flashed.Thanks To :
CM Team For CWM recovery .
@Dees_Troy @bigbiff @anders3408 @cybojenix @invisiblek {These Guys Are The Best And I Thank Them for helping me every step in the way and not thinking that i am a nut job }
Please Hit The Thanks Button If You Like My Work
Follow Me On Twitter SamerDKingCobra
If You Have Any Kind Of Trouble Feel Free To PM Me As I Am Here Almost 19 Hours A Day.
Downloads And Q&A
Downloads :
1.IMAGES
N8000-CWM-6.0.4.4.img {For dd Method , Please rename to recovery.img }
N8013-CWM-6.0.4.4.img {For dd Method , Please rename to recovery.img }
2.TAR FILES
N8000-CWM-6.0.4.4.tar Build #1 {For Odin}
N8013-CWM-6.0.4.4.tar Build #1 {For Odin}
Change Log :
Build #1 Fully Working.Whats To Do In Future Build ?
Enable Touch .
Add OTG Support.FAQ:{Please Read Before Posting}
Q: OMG ! Recovey Not Booting What To Do ?
Alease Dont try entering recovery first time from advanced power menu just do it the hard way
Q:My Device is not getting read by windows ?
A:Uninstall all drivers that you installed for the device .Please Hit The Thanks Button If You Like My Work
Follow Me On Twitter SamerDKingCobra
If You Have Any Kind Of Trouble Feel Free To PM Me As I Am Here Almost 19 Hours A Day.
For Later Use
it can't mount the external sd
iRoNX said:
it can't mount the external sd
Click to expand...
Click to collapse
seriously i did not notice such error, i will see what i can do tomrrow Thanks
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Shmong said:
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Click to expand...
Click to collapse
Well thats odd :/ are you sure you have n8000 build not n8013 as i am recovery fine
Yes, i'm pretty sure. I've tried to do this few times via both terminal and odin. Now will try one more time...
UPD: I've repacked the img file with the tar archiver+ put md5 checksum (tar.md5) and flashed it with odin successfully.
And like iRoNX said it can't mount extSD: "error mounting /storage/sdcard1"
UPD2: The recovery from similar thread have another issue: cannot format "/data" and cannot explore internal flash )))
Shmong said:
First, PC odin couldn't flash the device with this recovery (Odin 3.7, PC Win 8.1 x64, Odin works fine with it, checked many times).
After flashing this recovery from terminal it cannot boot by some reasons, and i'm rebooted the device with terminal command "reboot recovery", and i get the bootloop with the orange styled frame of "CWM-based recovery 6.0.4.4", then i reflashed the old version with odin.
P.S. My ROM is ARHD. Device: N8000.
Click to expand...
Click to collapse
+1.
The Odin tar file is not OK. Although I did not get a bootloop, the indicator on phone in download mode goes to the end and then stays there at "NAND write". I has to disconnect the phone and reboot manually, and my old version of CWM was still there (phew!). The .img files and dd worked fine.
Thanks anyways for this update !!!! It worked to get me on JB 4.4 !
Update: When phone is powered off and charger connected, upon starting there is a garbled green image that comes on for several seconds - most likely the battery charging icon - and then the phone will start up. It was not there before flashing 6.0.4.4. Anyways my phone does start up........
Tar file not working.. gets stuck at "Nandwrite"
Thanks for the recovery, I made it into CWM zip files so you can flash in CWM or TWRP here:
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8000-CWM-Recovery-v6.0.4.4.zip
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8013-CWM-Recovery-v6.0.4.4.zip
zedomax said:
Thanks for the recovery, I made it into CWM zip files so you can flash in CWM or TWRP here:
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8000-CWM-Recovery-v6.0.4.4.zip
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/GT-N8013-CWM-Recovery-v6.0.4.4.zip
Click to expand...
Click to collapse
Way to go, champion !!
Flashed but the external SD card doesn't work
Sent from my GT_N8000
ODIN Image file attached.
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
SD cards problem
Hello again,
Within this version of CWM, the SD card problem seems to be only for the 64g cards as tested on my N8013. However, after you flash the Rom you'll using, there is no problem with 64g cards outside of CWM recovery mode.
Smaller sized cards 32g and less will mount fine while you are in CWM recovery mode.
Cheers,
L
lobo25 said:
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
Click to expand...
Click to collapse
Not working for me... says img. file is invalid. then ends.
Love it. Thanks.
lobo25 said:
Hello,
The N8013 Odin file in the 1st post does not work as some mentioned in comments. I went ahead and created a proper Odin package from the other images which I am attaching for anyone who needs it. Please unrar and you'll find the .tar.md5 file to use with Odin.
Cheers,
L
Click to expand...
Click to collapse
Anyone confirm this as working?
Edit: Not working. Odin says invalid.
missing file
I seem to have lost my \efs folder, and in searching for a solution one of the steps I'm told to take is to flash "N8000-CWM-6.0.4.4.tar". However, it doesn't seem to exist anywhere (now that goo is gone), other than in this thread and the version here seems to be broken. Does anyone have the N8000 version of the .tar file?
Boot-loop, can't wipe device.
Hey everyone. I'm not exactly sure what happened, but it seems that my GT-N8000 is on the fritz again. The device was screen-off this morning (I left home) and when I came home it was in a reboot loop.
I jumped into recovery (CWM v6.0.4.4) to try to wipe both cache and dalvik (both successful) and rebooted. Same bootloop.
So then I decided to wipe the storage and reinstall the ROM (Gnabo v8 is what I had been running). When I attempt to "wipe data/factory reset", it says "formatting data . . ." and then reboots into the bootloop again.
Then I thought that maybe it was wiped, so I attempted to flash Gnabo. It installs successfully (Installing update, blue bar goes across, "Enjoy!" and "Install from sdcard complete."), however, when the installation starts, I get the first box and then it sits for almost 2 minutes before the blue bar appears, fills in just a few quick seconds, and then displays the completed message. It seems to me that the installation and the blue bar should be taking longer, but what do I know. Anyway, I rebooted (No, don't fix ROM flasing stock recovery on reboot), then back into the bootloop. So I'm still losing.
I don't know if it's related, but some months ago I had something similar happen in that the device was in a bootloop and it turned out that it had somehow lost the /efs folder. I had restored that (thanks XDA forums!) and it had been working fine since about June 2015.
I'm starting to think that my memory has gone bad, and that I basically have a 10.1 inch paperweight. Suggestions? Thanks for any help you can provide.
Hi there,
I've been working on rooting my htc one X bought in Australia locked to vodafone and now unlocked and used for a while.
I had been planning on rooting the phone for a while and after reading up multiple posts I chose to use the XDA developers video to root the phone. As the video is not very clear towards the end on the processes. But I completed the process somehow with reference to other videos and processes. However, after reading up on the best available ROMs I chose the CM11 with a basic process explained here (unable to post link)- however, that didnt help me much as there's just a basic description of what's to be done (helpful for advanced users).
But as this is my first attempt to rooting my device, I had to look up youtube on videos describing the rooting process for HTC one X. And found another video by the same author -
The author uses another ROM for the process but said this was a universal process. And I ended up copying only the CM11 zip folder of the ROM and not the Gapps zip file. Then his process didn't allow me to boot into recovery as my phone would get to the 'HTC - quietly brilliant' screen and get hang. Then I figured that the recovery image he had in the onexroot folder was an old one so I replace it with the latest image of recovery - recovery-clockwork-touch-6.0.4.8-endeavoru. And tried again, but with no luck.
Then I went in to the HBOOT menu and selected recovery and followed the process of installing from zip file and completed the entire installation process but the phone would go in to a boot loop when I rebooted. I followed some other processes to resolve this and ended up messing up the rom image on the phone. So now i'm unable to do anything with the phone as the stock rom is wiped out and so is the custom rom. I've tried the process of sideloading the zip files but I keep getting an error message of 'device not found'. I tried using the TWRP recovery as well for pushing files, but the the phone is non responsive on the main menu screen of TWRP itself. So I've flashed back to CWM recovery but am out of ideas on how to recover the phone.
Current status of the phone:
Bootloader - Unlocked
CMW - recovery-clockwork-touch-6.0.4.8-endeavoru
Sorry for the long description, but any help will be highly appreciated.
Thanks!
rubendayal said:
Hi there,
I've been working on rooting my htc one X bought in Australia locked to vodafone and now unlocked and used for a while.
I had been planning on rooting the phone for a while and after reading up multiple posts I chose to use the XDA developers video to root the phone. As the video is not very clear towards the end on the processes. But I completed the process somehow with reference to other videos and processes. However, after reading up on the best available ROMs I chose the CM11 with a basic process explained here (unable to post link)- however, that didnt help me much as there's just a basic description of what's to be done (helpful for advanced users).
But as this is my first attempt to rooting my device, I had to look up youtube on videos describing the rooting process for HTC one X. And found another video by the same author -
The author uses another ROM for the process but said this was a universal process. And I ended up copying only the CM11 zip folder of the ROM and not the Gapps zip file. Then his process didn't allow me to boot into recovery as my phone would get to the 'HTC - quietly brilliant' screen and get hang. Then I figured that the recovery image he had in the onexroot folder was an old one so I replace it with the latest image of recovery - recovery-clockwork-touch-6.0.4.8-endeavoru. And tried again, but with no luck.
Then I went in to the HBOOT menu and selected recovery and followed the process of installing from zip file and completed the entire installation process but the phone would go in to a boot loop when I rebooted. I followed some other processes to resolve this and ended up messing up the rom image on the phone. So now i'm unable to do anything with the phone as the stock rom is wiped out and so is the custom rom. I've tried the process of sideloading the zip files but I keep getting an error message of 'device not found'. I tried using the TWRP recovery as well for pushing files, but the the phone is non responsive on the main menu screen of TWRP itself. So I've flashed back to CWM recovery but am out of ideas on how to recover the phone.
Current status of the phone:
Bootloader - Unlocked
CMW - recovery-clockwork-touch-6.0.4.8-endeavoru
Sorry for the long description, but any help will be highly appreciated.
Thanks!
Click to expand...
Click to collapse
flash Philz recovery 5.15.9 mount sd card copy gaps.zip to your folder after this flash again CWM latest version go in recovery install rom.zip after this gapps.zip after this go in fastboot and flash the boot.img from rom.zip via fastboot with the command fastboot flash boot boot.img
Thant said:
flash Philz recovery 5.15.9 mount sd card copy gaps.zip to your folder after this flash again CWM latest version go in recovery install rom.zip after this gapps.zip after this go in fastboot and flash the boot.img from rom.zip via fastboot with the command fastboot flash boot boot.img
Click to expand...
Click to collapse
Hi,
Thanks for your reply. Philz recovery has an updated version available however, in its download screen it is not clear which version corresponds to the One X. There are versions of the software for One V and One S. Could you suggest which one would be the right one?
Thanks.
rubendayal said:
Hi,
Thanks for your reply. Philz recovery has an updated version available however, in its download screen it is not clear which version corresponds to the One X. There are versions of the software for One V and One S. Could you suggest which one would be the right one?
Thanks.
Click to expand...
Click to collapse
Nevermind that. I found the right one after a little more search philz_touch_6.19.3-endeavoru.zip
hope that's okay.
rubendayal said:
Nevermind that. I found the right one after a little more search philz_touch_6.19.3-endeavoru.zip
hope that's okay.
Click to expand...
Click to collapse
The lastest Philz have problem with mounting sd card like CWM and TWRP for this I say to install 5.15.9
rubendayal said:
Nevermind that. I found the right one after a little more search philz_touch_6.19.3-endeavoru.zip
hope that's okay.
Click to expand...
Click to collapse
Hi Thant,
I was able to mount the sd card in Philz, but not sure how to copy the data. Unable to find information on that online.
Any suggestions?
rubendayal said:
Hi Thant,
I was able to mount the sd card in Philz, but not sure how to copy the data. Unable to find information on that online.
Any suggestions?
Click to expand...
Click to collapse
you must to see the device to your computer but on latest Philz sd mount not working install 5.15.9
Thant said:
you must to see the device to your computer but on latest Philz sd mount not working install 5.15.9
Click to expand...
Click to collapse
Hi Thant,
Thank you so much for your help. You were completely right. I downloaded the 5.15.9 version and that let me connect the phone as a usb device and I mounted the device as usb in recovery and copied the gapps. however, there was an issue with the latest CWM that didnt let me install the ROM but philz recovery did the trick. Then again I installed the latest cwm and installed the gapps..wiped the factory data and went back to the fastboot menu, flashed the boot.img from the Rom's folder and rebooted. And now I have the android 4.4.4 working just fine!
Thank you once again for all your help! really appreciate it.
{
"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"
}
Hi Guys - I installed this twrp via fastboot flash recovery, I am on china dev version MIUI 10 8.8.3 Beta, rebooted to system, powered down, and then volume up & power button to go to recovery - I am greeted by china recovery 3.0 in chinese. It appears twrp does not stick. Device is unlocked bootloader (from vendor), Just flashed over from the fake ROM, this is the 128 GB / 6 GB version phone. What am I doing wrong
Lol, dont understand why you typed "revocery" in your pic but it still understood
badrsj said:
Hi Guys - I installed this twrp via fastboot flash recovery, I am on china dev version MIUI 10 8.8.3 Beta, rebooted to system, powered down, and then volume up & power button to go to recovery - I am greeted by china recovery 3.0 in chinese. It appears twrp does not stick. Device is unlocked bootloader (from vendor), Just flashed over from the fake ROM, this is the 128 GB / 6 GB version phone. What am I doing wrong
Click to expand...
Click to collapse
After flashing china rom, need to boot to fastboot then execute the following commands in adb:
1. fastboot format userdata
2. fastboot flash recovery twrp.......
3. fasboot boot recovery twrp...... so the phone can boot into recovery then follow the rest of the guide if you want to flash xiaomi.eu rom
That's strange, but Orange recovery also reverted
You're right it shouldn't have installed but it did. The Orange recovery also installed, neither stuck tho
Awesome
martin.burgas said:
After flashing china rom, need to boot to fastboot then execute the following commands in adb:
1. fastboot format userdata
2. fastboot flash recovery twrp.......
3. fasboot boot recovery twrp...... so the phone can boot into recovery then follow the rest of the guide if you want to flash xiaomi.eu rom
Click to expand...
Click to collapse
Will try
Thanks
Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights out
{
"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"
}
Sent from my SM-N950U1 using Tapatalk
badrsj said:
Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights outView attachment 4591035
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
I'm straggling with Chinese like most of us here. There is an android app you can install on your other phone which would use your cam to translate Chinese. Try that see if it helps...
What I am getting from this (cannot read chinese) but phone goes into fastboot - So I have formated, deleted the eu rom I had on the internal - so start again install the fastboot rom, twrp into it reboot twrp, have eu rom on SD Card and go from there.
badrsj said:
Folks I've hosed it
What's this
Booted to twrp, couldn't find the rom, booted to system.
Lights out
Click to expand...
Click to collapse
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.
martin.burgas said:
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.
Click to expand...
Click to collapse
Change phone file system
How?
Currently it states reset device and loops off and on.
It's a mess
Sent from my SM-N950U1 using Tapatalk
badrsj said:
Change phone file system
How?
Currently it states reset device and loops off and on.
It's a mess
Click to expand...
Click to collapse
From TWRP Wipe->Advanced wipe->Repair or change file system. Reboot TWRP from within TWRP -> Reboot recovery.
Can I flash this instead
Hi, I'd also flashed miui_MIMAX3Global_V9.6.6.0.OEDMIFD_091e94a919_8.1
Can I flash this rom on top of the above?
Fastboot ROM: http://bigota.d.miui.com/V9.6.7.0.O...EDCNFD_20180705.0000.00_8.1_cn_7c9a1a57f8.tgz
Located here
https://xiaomi.eu/community/threads...-and-recovery-rom-9-6-7-0-for-mi-max-3.45198/
Thanks, I'm afraid I'll brick the device?
Also struggled with twrp, switched back to miui's.
Look the twrp official site, find your device and follow step by step the fastboot method till the end. Worked.
I have solved the TWRP issue, the problem now is that when I flash a ROM it does not seem to work and crashes.
I am worried this is going to get bricked in this process. Maybe just wait for the official Global to come out
Which Partitions Change to F2FS
martin.burgas said:
From TWRP Wipe->Advanced wipe->Repair or change file system. Reboot TWRP from within TWRP -> Reboot recovery.
Click to expand...
Click to collapse
Hi, Which partitions to change to F2FS, If we change the Data Partition that would need to reflash Miui Chinese again?
Many Many Thanks - I am up and running
martin.burgas said:
After flashing TWRP you need to change file system from ext4 to f2fs, then reboot recovery, from within twrp, wipe cache,dalvic, data and internal recovery ( do NOT wipe system), mount all possible options ( pc will recognize phone, transfer xiaomi.eu rom from pc to internal memory, go to install and flash rom and wait to boot.
Click to expand...
Click to collapse
Thanks Martin you're very helpful I am now up and running. I am going to list a list of mistakes
1. I should have used CMD, not Powershell (type CMD in the address bar of the folder where your recovery is)
2. I did not know the sequence of flashing (change to F2FS, reboot recovery from within, Wipe Dalvic, Cache, Data) Then flash
3. I did not know how to boot recovery from fastboot (fastboot boot "recovery.img" "name of your recovery")
4. I did not know to change file system for data, (From TWRP Wipe->Advanced wipe->Repair or change file system. Select Data partition, select F2FS) change it then reboot recovery = see step 2 above.
Thanks Very Much
I am listing these for reference, and for those who help others to know what other errors may be committed.
Twrp supposedly installed -- twice -- but i got nothin'
Hi all,
I love this forum -- despite having a bunch of learning disabilities, I've managed to root a half dozen devices over the years thanks to your patience. This time I'm stumped.
Can't install TWRP. It says it is installed successfully with ADB (see screenshot). I used
twrp-3.3.1-0-nitrogen.img and I'm on I'm on Miui Global 10.3.5 Stable (Android 9PKQ1.181007.001).
Command line confirms installation. MM3 reboots when I enter the fastboot reboot to recovery command but it boots into the main system. I can boot into recovery using power/volume up method but it boots to the stock Mi recovery.
Should I try OrangeFox? Does this have anything to do with dm-verity? Is there anything else I can try to get root?
Originally, I wanted to install LineageOS, but what with locked bootloaders, anti-rollback, DM Verity, etc. , I'm guessing that's over my head and would happily settle for rooted stock.
Best,
Amy
Twrp supposedly installed -- twice -- but i got nothin'
EUREKA!!! I found a simple solution to install TWRP no worries about verity etc and I am rooted!
Genius idea came from Youtuber. Here is the link but I will still describe it in case the video gets removed for some reason.
You do it the regular stuff:
adb reboot bootloader
fastboot flash recovery "twrp filename"
But then while you're still in fastboot enter "fastboot recovery" into the command line and before you hit enter, press and hold volume up on the phone.
It boots into TWRP!
Note that you will keep getting Mi Recovery using volume down/power combo until after you use TWRP install (accessing TWRP with above method) to flash magisk.
Then, TWRP seems to stick. (Although just in case it gets unstuck, I installed the official twrp app from the Play store, since it has a 'boot into recovery' option.