Related
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?
I recently sold my Wildfire S, and because of that I wanted to wipe the phone out. So, I went to install a ROM, the same m1 mix I have been using for months, and I tried to install it again.
> Stays at HTC white screen and will forever if I let it.
> Tried installing another ROM to see if it was just corrupt. No go.
> I can get to the HBoot screen and move around but I can't get past HTC screen after installation is complete!!!
> Tried installing CWM again to see if it was an issue there, but now I get a "Install Fail" message because the ID is incorrect (I assume it has to do with the golf card)
I just want the damn thing to boot and work, I don't even care if it goes back to stock, I just need it to work. What are my options here? Any help would be great. An important factor I should mention is that I am on a Mac, and only have access to a Mac.
Thanks!
I have an evo so I'm not sure how things work on your phone but have you tried an ruu? It should help
Sent from my PC36100 using xda premium
Are you wiping data/factory reset, cache and dalvik? You need to do this in cwm
Yes, I always wipe both system and cache, as well as dalvik.
I will try a RUU, see where that gets me. Thanks. And if anyone else has suggestions please let me know!
I think you can only run an ruu under windows.
I could be wrong though.
I can't just have the ZIP on my SD Card and install it from there?
You can but I think it will give you the same issue.
Try it though, its worth a shot
I just want the easiest way to get this back to functioning. I don't need any of the data on the phone or the SD card. I just wanted it to work. Period.
Easiest and safest is ruu
Do you not know anyone that will let you run it on their windows machine?
It would take 10 mins topps and is almost guaranteed to get you back up and running.
By the way are you a GSM or cdma user?
Edit: is that rom overclocked by default? The reason I ask is a lot of people have been having issues like you when installing Rom's that are pre overclocked.
Check if there's a default clock speed kernel on his op
GSM Virgin Mobile Canada.
nootered said:
GSM Virgin Mobile Canada.
Click to expand...
Click to collapse
Also your bootloader must be locked in order for the ruu to work.
{
"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 am unlocked currently. I have been running it just fine with the m1xd ROM, all the stats are in my sig.
I just want this facking thing to function!!!!!!!!!!!! :O
nootered said:
I recently sold my Wildfire S, and because of that I wanted to wipe the phone out. So, I went to install a ROM, the same m1 mix I have been using for months, and I tried to install it again.
> Stays at HTC white screen and will forever if I let it.
> Tried installing another ROM to see if it was just corrupt. No go.
> I can get to the HBoot screen and move around but I can't get past HTC screen after installation is complete!!!
> Tried installing CWM again to see if it was an issue there, but now I get a "Install Fail" message because the ID is incorrect (I assume it has to do with the golf card)
I just want the damn thing to boot and work, I don't even care if it goes back to stock, I just need it to work. What are my options here? Any help would be great. An important factor I should mention is that I am on a Mac, and only have access to a Mac.
Thanks!
Click to expand...
Click to collapse
Hello ,
this will return your phone to stock state (means that you will no longer have CWM recovery and you will have to install it again after this. If unlocked with XTC Clip YOU WILL STAY S-OFF ,I didn`t tried it with device unlocked via HTC Dev)
STEP BY STEP instructions what you should do :
1. go to http://forum.xda-developers.com/showthread.php?t=1432474
2. download http://www.mediafire.com/?ksa9k8dmxexdkdo
3. follow the instructions from 1
4. click thanks button
credits to Gig11gs & Ping192
P.S. I`m not responsible if you do any damage to your device.
if you have a backup or something then flash it through hboot
or if you have a extracted zip file from an ruu (rom.zip file in c:/temp when you run the installer) then extract it to desktop and flash it through hboot(if the file name of system is system.yaffs2.img then change it to system.img , you require only two files boot.img and system.img so no need to extract everything just extract these two)
the codes for both are
(locate the adb files first.)
in my case i have copied fastboot file from tools folder of sdk on desktop and also adb and adbbin.dll on desktop.. if you also copy these files on desktop then run the following exact commands when you are on bootloader the fastboot option will be highligted press power buton to select it .. when you in fastboot menu connect phone to pc and then write these command in dos prompt (go to start menu , run then write cmd and press enter you will have a dos prompt open)
Code:
cd desktop
fastboot flash boot boot.img
fastboot flash system system.img
when done go to recovery and now do all format data , clear chache and dalvik chace your phone will be un rooted total stock
It worked for me.. credits to EOgan
Or you can go to this tutorial that will downgrade everything even hboot and radio at http://forum.xda-developers.com/showthread.php?t=1540952 and remember o thank me
Just a thought but have you wiped everything before flashing the ROM? I've had a weird experience once with pretty much the same issue (stuck on splash screen). Wiping everything (system, data, cache, boot AND SD Card) seemed to have resolved the issue. If you're using an already partitioned card, I'd recommend powering off after CWM flashing, unmounting the SD and then turning it on.
This should work actually (don't see a reason not to). Also, if you've modified the ROM.zip file in any way after downloading it, I'd advise flashing one which is freshly downloaded rather (would eliminate any user tweaks causing the issue).
PS. I've attached a flashable superwipe script which you can run before flashing the ROM. Let me know how it worked out for you.
Okay, so I've just rooted my Nexus 7 tablet after being told a custom ROM would fix my GPS issues with my N7v2. I'm familiar with the rooting process, having done it to my HTC One. I rooted it successfully, installed the SuperSU and TWRP. Everything went smoothly, and then I realized, only minutes later, after browsing XDA, that Google JUST released an OTA to fix the issues.
So I browsed around and found this post: http://forum.xda-developers.com/showpost.php?p=44888268&postcount=97&nocache=1&z=675614455249160
I followed the instructions. I opened a CMD in the correct folder and ran the flash-all.bat. It ran... HOWEVER it generated a few errors. The errors in CMD were that it was unable to find files that are contained within the img-razor-jss15q.zip folder that was inside the downloaded TGZ archive. When I finally figured out how to use 7zip (never had a use for it before now), I ended up with a folder that looked like this (which is where I ran the CMD):
{
"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"
}
As you can see the image-razor-jss15q.zip was still inside that folder. I did not unzip it because I didn't know if I was supposed to or not.
At any rate, the tablet SEEMS to be fine. I rebooted into the bootloader and then to recovery and got the android with an exclamation mark which is what I ASSUME I'm supposed to have. TWRP is gone, at least.
I also looked at the system information and it's showing the build number as JSS15Q.
So my questions are simple:
1. Did I do this correctly and are the errors normal?
2. If "no" to 1, what do I need to do to fix it?
Edit: It appears I've put this in the wrong section, I apologize. I'd appreciate it if a moderator moved it for me. Thanks!!
Your first error was not correct but you figured it out and the next time around it was done right. If your tablet says JSS15Q then you successfully installed it
Twrp gone means the stock recovery in the image zip flashed correctly
Seems you've already answered your own question.
The guide could have probably better explained to extract the actual image files to your ADB/Fastboot folder.
I prefer to reflash the relevant images individually with
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase system
fastboot flash system system.img
fastboot erase data
fastboot flash data data.img
fastboot erase cache
fastboot flash cache cache.img
I exclude the bootloader image when reflashing unless necessary due to the remote chance of bricking your device if it fails to flash completely.
http://forum.xda-developers.com/showthread.php?t=2404833
sfhub said:
Your first error was not correct but you figured it out and the next time around it was done right. If your tablet says JSS15Q then you successfully installed it
Twrp gone means the stock recovery in the image zip flashed correctly
Click to expand...
Click to collapse
Ah! The OP of that useful information! Thank you for that!
At any rate, regardless of the error, it still managed to work correctly. Still, though, while waiting for a response I figured "Well, I can just redo it but after extracting the relevant files to the main folder. This time it did not give me that set of errors but instead gave me these:
http://i.imgur.com/k6Mgn2I.png
I could not find those files anywhere in the included files so I'm not really worried about it because at this point the tablet seems to be working fine.
Username invalid said:
Seems you've already answered your own question.
The guide could have probably better explained to extract the actual image files to your ADB/Fastboot folder.
I prefer to reflash the relevant images individually with
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase system
fastboot flash system system.img
fastboot erase data
fastboot flash data data.img
fastboot erase cache
fastboot flash cache cache.img
I exclude the bootloader image when reflashing unless necessary due to the remote chance of bricking your device if it fails to flash completely.
Click to expand...
Click to collapse
Well I wouldn't have rooted it in the first place had I known about the OTA. Regardless, I'm not sure what you mean by "you answered your own question"...?
I really don't care about the method so long as it works. I'm not actually interested in rooting this tablet, really. I love it as-is. I'll reserve all my tweaking for my phone.
Just a heads up for anyone who has TWRP or CWM installed, you can use this flashable .zip to update to latest OTA update. Download update. Reboot to recovery. Wipe Cache/Dalvik. Flash .zip. Reboot and you're done. Worked pefectly on mine and you won't lose your recovery in the process.
Edit: Just wanted to point out, this is obviously for those running stock ROM.
railed said:
Just a heads up for anyone who has TWRP or CWM installed, you can use this flashable .zip to update to latest OTA update. Download update. Reboot to recovery. Wipe Cache/Dalvik. Flash .zip. Reboot and you're done. Worked pefectly on mine and you won't lose your recovery in the process.
Click to expand...
Click to collapse
Hey cool, thanks for that! I'm sure people will find this useful!
wolfbuck22 said:
Well I wouldn't have rooted it in the first place had I known about the OTA. Regardless, I'm not sure what you mean by "you answered your own question"...?
I really don't care about the method so long as it works. I'm not actually interested in rooting this tablet, really. I love it as-is. I'll reserve all my tweaking for my phone.
Click to expand...
Click to collapse
You can still receive OTAs with root. You just need to reflash the stock recovery which only takes a few seconds.
wolfbuck22 said:
It ran... HOWEVER it generated a few errors. The errors in CMD were that it was unable to find files that are contained within the img-razor-jss15q.zip folder that was inside the downloaded TGZ archive.
At any rate, the tablet SEEMS to be fine. I rebooted into the bootloader and then to recovery and got the android with an exclamation mark which is what I ASSUME I'm supposed to have. TWRP is gone, at least.
I also looked at the system information and it's showing the build number as JSS15Q.
So my questions are simple:
1. Did I do this correctly and are the errors normal?
Click to expand...
Click to collapse
Username invalid said:
You can still receive OTAs with root. You just need to reflash the stock recovery which only takes a few seconds.
Click to expand...
Click to collapse
I only tried the flash-all.bat once. It ran with the errors. Tablet still worked even with errors. Had regular recovery back and everything.
Though, I wasn't satisfied so I went back and unzipped those files to the main folder and re-ran the flash-all.bat again. That time it gave me a different set of errors but the tablet seems to be working just fine so I'm not exactly worried about it.
wolfbuck22 said:
Ah! The OP of that useful information! Thank you for that!
At any rate, regardless of the error, it still managed to work correctly. Still, though, while waiting for a response I figured "Well, I can just redo it but after extracting the relevant files to the main folder. This time it did not give me that set of errors but instead gave me these:
http://i.imgur.com/k6Mgn2I.png
I could not find those files anywhere in the included files so I'm not really worried about it because at this point the tablet seems to be working fine.
Click to expand...
Click to collapse
Those missing .sig files are expected. Google did not sign their factory restore images which is why you need an unlocked bootloader to flash them
sfhub said:
Those missing .sig files are expected. Google did not sign their factory restore images which is why you need an unlocked bootloader to flash them
Click to expand...
Click to collapse
Great. Thank you so much, everything appears to be working fine at this point.
I may venture into the custom ROM realm later but for now I'm quite happy with the Nexus 7's stock ROM (never had a pure Android device before).
{
"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.
I tried to install an update from HTC ( Lollipop 5.0 ) but It wasnt possible because my phone was rooted. I came with the status 7 error. Then while reading some articles, I found that in order to get rid off that error and to install a new rom or update I must wipe all data from my phone, even the system part for a clean installation so I wiped it.
After that , my phone freezes on htc white logo.
I can access to fastboot with the Power button an volume
It says
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.16.2133156.UA15G
OpenDSP-v38.2.2-00542-m8974.0311
OS-1.57.598.2
eMMC-boot 2048M
Apr 16 2014,03:20:29.0
And then the options
But when I go to recovery, the phone goes to Philz Touch ClockWorkMod screen
The version of Philz Touch is 6.57.8 and ClockWorkMod is v6.0.5.1
And when I tried to restore my phone, it says there's any backup files, so I cant restore to factory
As my phone can not be recognized by my pc because the OS can not run, I think I can not use One_M8_All-In-One_Kit_v2.0.
Is there any chance to get my HTC work again? I just dont care the Lollipop update now. I just want it to work again. I' ve been reading many articles during these 3 days but I dont know how to repair it yet.
Please help me
Pdt: I tried to add Images but the forum doesnt let me.
Read this : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
and restore that 1.57.599.1 backup
ckpv5 said:
Read this : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
and restore that 1.57.599.1 backup
Click to expand...
Click to collapse
But there is Philz-tocuh in phone. Am I not going to mess things up if I install TWRP?
You're going to mess up more when you use One_M8_All-In-One_Kit_v2.0.
Just follow the guide if you want to fix your phone
or wait for someone else to help you if you insist to keep that outdated philz recovery
Good luck ... time to bed now .. good night
Oh Thanks. I didn't meant to be unpolite. It just I am very new on this. So I must first, get rid off the Philz bootloader and then install the TWRP, right?
Just install TWRP 2.8.1.0
It will replace Philz recovery, no need to do any other thing
No uninstall is needed
Ok. I got it. But, I can not figure it out how to run command to my phone because my pc does not recognize my phone. I have installed the htc drivers; however, as my phone just shows the htc logo I dont have any option to use MTP connection. Even, I tried to find and option for running commands in the fastboot screen , but there's any.
I assumed that the quick way to install TWRP in my phone will be copying the openrecovery-twrp-2.7.0.1-m8.img into a SD CARD (an external one) and then trying to install that file through my phone. Am I right?
mikegohome said:
I have installed the htc drivers; however, as my phone just shows the htc logo I dont have any option to use MTP connection. Even, I tried to find and option for running commands in the fastboot screen , but there's any.
Click to expand...
Click to collapse
You need to be in bootloader fastboot mode, in order to run fastboot commands.
mikegohome said:
I assumed that the quick way to install TWRP in my phone will be copying the openrecovery-twrp-2.7.0.1-m8.img into a SD CARD (an external one) and then trying to install that file through my phone. Am I right?
Click to expand...
Click to collapse
The TWRP webpage only has instruction for doing that with TWRP 2.8.4 or higher; and that's not the case, is it?
redpoint73 said:
You need to be in bootloader fastboot mode, in order to run fastboot commands.
Click to expand...
Click to collapse
Now, even if I connect my phone to my pc I get this screen
{
"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"
}
And I dont find any option to run commands
Then, when I try to enter to recovery or factory reset , I get ClockWorkMod screen
and I dont any option to do that, either.
As I cannot run commands through my pc , how could I Install TWRP in my HTC and replace the ClockWorkMod ?
redpoint73 said:
The TWRP webpage only has instruction for doing that with TWRP 2.8.4 or higher; and that's not the case, is it?
Click to expand...
Click to collapse
Yes , i've seen only instructions for phones which can be connected to pc
So, how is your problem going? Managed to fix your phone?
AlcaloidedoErgot said:
So, how is your problem going? Managed to fix your phone?
Click to expand...
Click to collapse
I'm still looking for a solution. I dont know how to install TWRP in my phone because all tutorial I found say that first I must connect my phone to my pc in order to run some commands to install it. I can not do that because my phone is freezed in the HTC Logo and my pc does not recognize it.
redpoint73 said:
You need to be in bootloader fastboot mode, in order to run fastboot commands.
Click to expand...
Click to collapse
mikegohome said:
Now, even if I connect my phone to my pc I get this screen
And I dont find any option to run commands
Click to expand...
Click to collapse
He said bootloader fastboot mode .. you're on bootloader hboot mode.
Press power once when on this hboot screen .. can you see the fastboot usb highlighted in red when connect to PC ?
And for your info, Philz recovery is able to restore a TWRP backup.
You just need to put the TWRP backup in correct folder TWRP/BACKUPS/YourPhoneSerialNo./theTWRPbackupFolderHere
ckpv5 said:
He said bootloader fastboot mode .. you're on bootloader hboot mode.
Press power once when on this hboot screen .. can you see the fastboot usb highlighted in red when connect to PC ?
Click to expand...
Click to collapse
I just see FASTBOOT painted in red. There's no FASTBOOT USB , unfortunately.
ckpv5 said:
And for your info, Philz recovery is able to restore a TWRP backup.
You just need to put the TWRP backup in correct folder TWRP/BACKUPS/YourPhoneSerialNo./theTWRPbackupFolderHere
Click to expand...
Click to collapse
Sorry, but could you tell me what file do I need to use to restore TWRP?
The only way I can move files into my phone is by using an sdcard and copy/paste them with AROMA filemanager which comes with Philz
What about your PC device manager ? Do you have MyHTC under Android USB Devices ?
Check your cable, HTC USB Drivers - Download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
Install then uninstall HTC Sync Manager but leave the drivers
mikegohome said:
Sorry, but could you tell me what file do I need to use to restore TWRP?
The only way I can move files into my phone is by using an sdcard and copy/paste them with AROMA filemanager which comes with Philz
Click to expand...
Click to collapse
Use a card reader to read/write a MicroSD with a PC.
And talking about your software version no. 1.57.598.2, I found someone with your version but unfortunately he was reluctant to upload his backup due to big size of 1.4gb and he didn't have the data quota to upload it. And now I believe he remains at 1.57.598.2 instead of updating it to 4.32.598.1
And there is RUU 0P6BIMG_M8_UL_K44_SENSE60_SECURITY_HTC_LA_AMX_SPA_ 1.57.598.2_R_Radio_1.16.2133156.UA15G_20.18m.4096. 07L_release_378222_signed.zip available at IR-File but now the one that has access to it seems no more active on M8 thread .. very unfortunate.
ckpv5 said:
What about your PC device manager ? Do you have MyHTC under Android USB Devices ?
View attachment 3522626
Check your cable, HTC USB Drivers - Download HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
Install then uninstall HTC Sync Manager but leave the drivers
Click to expand...
Click to collapse
I did it! Now I see the FASTBOOT USB and MyHTC under Android USB Devices
ckpv5 said:
Use a card reader to read/write a MicroSD with a PC.
And talking about your software version no. 1.57.598.2, I found someone with your version but unfortunately he was reluctant to upload his backup due to big size of 1.4gb and he didn't have the data quota to upload it. And now I believe he remains at 1.57.598.2 instead of updating it to 4.32.598.1
And there is RUU 0P6BIMG_M8_UL_K44_SENSE60_SECURITY_HTC_LA_AMX_SPA_ 1.57.598.2_R_Radio_1.16.2133156.UA15G_20.18m.4096. 07L_release_378222_signed.zip available at IR-File but now the one that has access to it seems no more active on M8 thread .. very unfortunate.
Click to expand...
Click to collapse
Oh, snap. But what about using other similar .zip? could I use it? or is it mandatory that I use that specific .zip?
ckpv5 said:
Use a card reader to read/write a MicroSD with a PC.
And talking about your software version no. 1.57.598.2, I found someone with your version but unfortunately he was reluctant to upload his backup due to big size of 1.4gb and he didn't have the data quota to upload it. And now I believe he remains at 1.57.598.2 instead of updating it to 4.32.598.1
And there is RUU 0P6BIMG_M8_UL_K44_SENSE60_SECURITY_HTC_LA_AMX_SPA_ 1.57.598.2_R_Radio_1.16.2133156.UA15G_20.18m.4096. 07L_release_378222_signed.zip available at IR-File but now the one that has access to it seems no more active on M8 thread .. very unfortunate.
Click to expand...
Click to collapse
Now I have installed TWRP on my phone , yeei
And I found a .zip file called OTA-something. It looks like this is the lollipop room which caused all this problem. I tried to installed and then I came up with this:
It seems I messed up my phone with the root.
On the other hand I read in some articles that if I update the firmware, I could use another room. Is that true?
You can't use TWRP to do OTA update. It needs 1.57.598.2 stock ROM and stock recovery installed.
Where did you find that OTA zip ? Can you upload that for me ? I want to see what's inside it then I can give a better suggestion what the firmware update can do for you.
Is your device has a OS installed now ? Is it really that you wiped the OS before ?
Try make a backup with TWRP and see how it goes whether it manage to make backup or not.