Database Info

[AT&T][2.3.6]Heimdall One-Click Back-To-Stock UCKJ4 + Easy CWM install

Introduction
This package will totally reset your Infuse 4G to UCKJ4 . This package is intended for use on AT&T, however it will work with any device if you reset APN.
This package includes:
Repartitioning: Repartition to stock KJ4
Reloading: IBL/PBL, PARAM, SBL, SBL2, Kernel, Recovery, FactoryFS and modem
formatting:Cache and DBdata
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
You may use this code to reformat the Data and SDCard *2767*3855# There is no way to do this from Download Mode. The code will leave the EFS untouched.
Download:
Download Total Stock UCKJ4
{
"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"
}
Instructions:
Get the latest version of java here: http://java.com/en/download/installed.jsp
Put your phone into "Download Mode"
Run the program once, and if it does not work, then check the "Flash Bootloaders" checkbox and flash again
Your device will end up as it came from the factory. You will be asked to set your device up again.
If you would like to install CWM on your device to restore or flash a custom ROM, I have prepared LinuxBozo's Defuse 1.5 kernel in a One-Click package here:
Download Defuse 1.5
To flash this package, follow the directions above.
Please note, this may not boot your device, but it will allow you to use CWM recovery. Hold the 3 button combo without USB plugged in to activate CWM mode.
How I created these package:
I obtained the stock 2.3 bootloader from a link LinuxBozo gave me
The stock part.pit came from my device using Heimdall(Download Pit option)
Uploaded the UCKJ4 firmware to my device
Performed "wipe data" in recovery mode
Exploited the root prompt at the battery charge sequence using UART and grabbed the stock, wiped dbdata/cache partitions and params.lfs partition
Created a Heimdall tar.gz package using Heimdall 1.3
Finally, I used my Heimdall One-Click *BETA* packager to generate these one-clicks
This procedure can be reproduced for any custom ROM in the future by using the dd command to obtain the factoryfs and kernels from any device. Bootloaders may be obtained from within this package as it is an executable JAR file which can be unzipped.

Thanks
Cranky...

Nice, I'll be using this when needed.
Also, you have a typo in your title, it's 2.3.6. :]
Sent from my phone. :3

AdamOutler said:
This is the current version pushed out on new Captivate devices today.
Click to expand...
Click to collapse
Wait, Captivate devices got an official update today? Wow.

Any downsides we should be worried about?

I copied the first paragraph from another post I made. That was a typo.

You might want to put the defuse kernel in another thread. Don't want people flashing 2.2.1 kernels on 2.3.6
Also might want to make a Hellraiser kernel version for people that Odin'd the leak or Rogers users that want a quick root/cwm without Odin

Dani897 said:
You might want to put the defuse kernel in another thread. Don't want people flashing 2.2.1 kernels on 2.3.6
Also might want to make a Hellraiser kernel version for people that Odin'd the leak or Rogers users that want a quick root/cwm without Odin
Click to expand...
Click to collapse
This package is posted as a method to get your phone back to stock and the defuse kernel provides easy access to cwm.. I had it around and it works. I tested before posting. Its there because it will give CWM. I will probly post a new one later with a 2.3.6 kernel but for now, this is how you get CWM on your device from Linux or Mac with one click.

I needed to flash the bootloader in order to get mine to boot up, but its been running for ~1 hour now and looks pretty nice. Offhand, do you know if HDMI is working for you? I'll go ahead and test after posting and I'll include my results here.
Edit: Nevermind, found cross-post with the results I needed. Stock kernel, HDMI works, rooted kernel (Entropy, etc.) breaks HDMI as they're based on Rogers roms.

HOw TO ROOT THIS ROM

cookieboy said:
HOw TO ROOT THIS ROM
Click to expand...
Click to collapse
Use defuse kernel, boot into CWM, then flash a rooted CWM zip. This ROM is very new.

nice work!

Only thing i noticed is that their is no stock ringtones with this rom.
Sent from my SAMSUNG-SGH-I997 using XDA App

Also want to add when you open facebook newsfeed, it wont let you select news, status updates, photos and etc. If you refresh the page while in app it will show you the list. Small bug i came acrossed. Let ya know if i find more.
Sent from my SAMSUNG-SGH-I997 using XDA App

After running stock UCKJ4 for a few hours, I seem to be having an issue where I get an error message saying my Google Talk authentication is not working, to make sure Chat is enabled on my account, as well as returning errors any time I try to install things from the Market. Anyone else running into this? Going to try removing and re-adding my Google account.
Edit: Crap, apparently you can't remove it without factory resetting. Damnsauce.

After factory resetting, things appear to be fixed. Thanks again for this package!
Sent from my SAMSUNG-SGH-I997 using xda premium

adalgiso said:
After factory resetting, things appear to be fixed. Thanks again for this package!
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
I had a similar problem. Downloading apps from market told me I had Insufficient space on the device. Clearing cache and Factory reset fixed the issue, Incase any others run into this.

Axiomkid said:
I had a similar problem. Downloading apps from market told me I had Insufficient space on the device. Clearing cache and Factory reset fixed the issue, Incase any others run into this.
Click to expand...
Click to collapse
Just to clarify, I was not receiving the insufficient space issue, I don't remember the exact wordage. 'There was an error' and nothing else.
---------- Post added at 12:30 PM ---------- Previous post was at 11:35 AM ----------
Attempting to root using zergRush exploit from here: http://forum.xda-developers.com/showthread.php?t=1321582
Will post results.
Edit: Check my thread here: http://forum.xda-developers.com/showthread.php?t=1332656

i was trying this everything seemed to work then it wouldnt boot so i did the flash bootloaders like it said, now nothing will work, not even the screen please help, im in dire need

steezinstangl said:
i was trying this everything seemed to work then it wouldnt boot so i did the flash bootloaders like it said, now nothing will work, not even the screen please help, im in dire need
Click to expand...
Click to collapse
oh boy, there is always a risk of permabricking when flashing bootloaders, (unless you did the unbrickable mod or have a jtag)
ok to start to see if you are actually permabricked;
1 pull your battery out
2 get a good micro usb cable, try this with more than one if you have to, if you had a problem flashing it may have been caused by the cable.
3 insert the cable into the usb port and into the computer.
4 hold both volumes with the phone face down, while the volumes are held slide the battery into position. see if the phone enters the download warning screen, it will ask you if you are sure you want to flash custom firmware, hit volume up. it may also go into a phone + computer screen or strait into download mode. all are good signs.
if you end up in download mode congrats! reflash!
if the screen is still black id recommend sending the device to connexion for jtag flashing or to adam if he is willing to repair it, these methods will void the warranty do to hardware modification (the repair may require soldering) . you may also atempt a warranty repair with samsung or insurance replacement with att but if they find that you are responsible samsung will charge you for the repair and im not sure what the insurance company will do.

[GUIDE] [HOW-TO] [N00b Friendly] Install OFFICIAL CM10 Nightlies NO KEXEC (8-18-12)

UPDATE 8-18-12: OFFICIAL CYANOGENMOD NIGHTLIES ARE UP.
Hey Guys, I haven't seen anyone post this yet so I figured I'd give it a shot. First and foremost, I take ABSOLUTELY NO CREDIT FOR ANYTHING IN THIS POST. Let it be known that none of this is my work and the purpose of this post is to consolidate information into an easy-to-follow guide. Also, I take no responsibility for any damage you do to your own phone. It's your responsibility to understand the risks involved and do your research before you make ANY modifications. If you'd like to use this guide for a project you're working on or another thread, that's fine with me. All I ask is that you give credit where it's due.
BEFORE WE START. If you cannot follow detailed instructions, please don't bother using this guide as you're only going to waste your own time as well as mine. I won't be answering any questions or providing support for problems that are clearly covered in the guide.
Now that we've achieved an unlocked bootloader, Cyanogenmod's team is already at work and has a build of CM10 up and running. (It's technically an alpha, but for me EVERYTHING works perfectly: data, wifi, bluetooth, GPS, MMS, camera, camcorder, the whole nine. The only thing I've found to NOT be working is NFC). The post can be found on both Cyanogenmod and Austen Dicken's Google+ page. Those can be found here:
https://plus.google.com/117962666888533781522/posts
A word of caution:
Since I'm not a Cyanogenmod developer, I have no control on the stability of their posted builds. So if you go through the guide and your MMS isn't working, there's not a whole lot I or anybody else can do for you at the moment considering these are still alpha builds. Although I mentioned everything works currently for me, I can neither guarantee this nor help you troubleshoot technical issues as I am not the developer of the ROM itself. On the other hand, if you have any questions or problems following the guide, I'm happy to help you out to the best of my ability.
For this to work, you must be ROOTED and have an UNLOCKED bootloader. I'm not going to make a super-detailed write up on how to achieve both of these, but here's a general outline of steps for those that are new here. If you're already rooted and have your bootloader unlocked, you can skip straight to step 4.
Pre-install:
First, BACKUP EVERYTHING. Do a nandroid backup and backup your apps and data in Titanium if desired.
Install the latest Samsung USB drivers so your phone and your computer don't have any connection problems. Those can be found here:
http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
on the bottom under Manuals/Downloads and then Software.
I highly recommend backing up your IMEI incase something goes wrong. I'm not going to cover that here, all info can be found in this post:
http://forum.xda-developers.com/showthread.php?t=1791291&highlight=backup
You have been warned.
You need to have your SD Card formatted to FAT32. exFAT WILL NOT WORK. So if you're like me and have a 64GB SD card, neither Android nor windows will let you format to FAT32 natively, so you have a few options.
Using command prompt within windows:
http://www.xoomforums.com/forum/mot...-format-sd-card-especially-64gb-fat-32-a.html
Use a disk management program like Acronis Disk Director (I think they may have a free trial but don't quote me on that).
http://www.acronis.com/homecomputing/products/diskdirector/
Then, you may want to Odin back to stock using the latest Samsung firmware. Now, you DO NOT need to Odin back to stock for the rest of this guide to work. But it should fix any 4G/3G data problems you may have been having on custom k-exec ROMs and I thought it was a good idea to start completely fresh now that we have total freedom. So if you were having bad experience on any custom ROMs with a flaky data connection or GPS taking a long time to lock, give it a try and see if it fixes things for you.
If you're going to give it a try, both the Odin program and stock Odin firmware can be found in this post:
http://forum.xda-developers.com/showthread.php?t=1755386
Download the latest version of Odin and the latest stock firmware version. Extract the Odin zip and load it up. Click the PDA button, find the stock firmware you just downloaded. Boot into download mode on your phone by powering down, then powering back up while holding the home and volume down buttons. Click start in the odin window. This process should take a while. After your phone reboots, get through the setup and dial *2767*3855#. Your phone will reset and you'll be COMPLETELY back to stock and any radio/hardware connection issues should be fixed. If you're still having problems let me know.
Now, to the fun part.
1. Root your phone.
NoxiousNinja's GS3DebugFSRoot Tool is the easiest and most foolproof way I've found. Read the directions in the post and follow the instructions in the command prompt window. Very easy and lightweight.
http://forum.xda-developers.com/showthread.php?t=1792342
As you continue throughout this process, pay careful attention to the prompts as it will ask you for [y/n] responses that you must confirm. After finishing, go into the newly installed Superuser app and on the far left panel, click where it says "tap to check for updates." Then click "update" on the bottom EVEN IF YOU HAVE THE NEWEST VERSION. I don't know why it works, but it does.
2. Flash a custom recovery.
Download mmmeff's EZ Recovery flashing app from the play store. Just search for "EZ Recovery" and you'll find it. Once installed, make sure you allow root access, then select "CWM 6.0.1.0" from the dropdown (NOT THE TOUCH VERSION AND NOT TWRP . It just makes it easier on everyone if something goes wrong. I can personally confirm that the touch version is incompatible. Some users are reporting TWRP is working fine, so you can try that at your own risk but I can't provide any support if it doesn't work for you since I haven't tried it myself.), make sure you have the "Recovery" toggle selected on the left, and click "flash recovery". Don't worry about rebooting yet as we still have a few things to do. The thread for the app can be found at:
http://rootzwiki.com/topic/29698-72...-recovery-flashing-app-ya-dingus/page__st__10
3. Unlock your bootloader.
I've also chosen to use mmmeff's Bootloader unlocking app from the play store for this guide as it is universally acceptable no matter what operating system everyone is running. In the play store, search for "GS3 EZ Unlock". Once installed, again make sure you allow root access and then click the HUGE button in the middle. It only takes a few seconds and then you're done. Thread is here:
http://rootzwiki.com/topic/32456-app-ez-unlock-easiest-way-to-unlock-your-bootloader/
4. Flash Cyanogenmod.
First, you'll need some downloads. You can use the Cyanogenmod 10 Alpha build or a nightly CM10 build.
Cyanogenmod 10 ALPHA build:
http://goo.gl/RYzHT
MD5: 3662de3c8942f19dc95ca911207b1602
CM10 Nightlies can be found at:
http://get.cm/?device=d2vzw
Jellybean GAPPS:
http://goo.im/gapps/gapps-jb-20120726-signed.zip
Mirror:
http://www.mediafire.com/?63l7wtwlc09923c
MD5: f62cfe4a827202899919fd932d5246d7
Put both of these zips on the root of your SD card.
Before you get all trigger happy, we need to do some things first.
For those of you who are new at this, I'll say it again, BACKUP EVERYTHING. This next step will wipe everything on your phone.
INSTRUCTIONS FOR FLASHING A NEW INSTALL OF CYANOGENMOD:
Now, boot into recovery (power off and then power back on while holding the home and volume up buttons) and wipe SYSTEM, DATA, CACHE (all can be found in Mounts/Storage menu), and DALVIK CACHE (can be found in advanced menu). A system wipe is not technically necessary but I did it just to make sure I didn't have any problems. Then, go into "install zip from SD card," then "choose zip from SD card". First, flash the Cyanogenmod zip, and after that finishes flash the Gapps zip. Go back a couple levels, click "reboot system now," and you're done!
INSTRUCTIONS FOR FLASHING AN UPDATED BUILD OF CYANOGENMOD
Now that you have a working install of Cyanogenmod, it gets a lot easier. If you're currently on the Alpha build and are switching to the new nightly builds, I would HIGHLY recommend you perform a FULL wipe including system, data, and both caches. Some people moved from the alpha to nightlies and were having problems so if you do a full wipe the first time you'll be fine. If you want to update from a nightly build to a newer nightly, all you should need to do is wipe both caches.
I hope this helped at least a few people, I tried to arrange it into as easy of a guide as I could. Please let me know if you see any problems or necessary changes and I'll try to keep this thread updated as new builds are upped. TO EVERYONE THAT IS NEW HERE, PLEASE DO NOT BUG DEVELOPERS WITH STUPID QUESTIONS REGARDING RELEASE DATES OR PROGRESS. I can assure you that they're working hard, we got a full release the day after our bootloader got unlocked. So be patient, nightlies and beta versions of CM and AOKP will come soon enough.
If you're interested, after you're done you can try flashing a new radio and/or kernel. Unless you're having problems, I wouldn't recommend you try this unless you know what you're doing because you could make things worse. Consider yourselves warned. Radios and instructions can be found in Invisiblek's thread here:
http://forum.xda-developers.com/showthread.php?t=1788313
Do some research on kernels, but at the time of writing I can recommend imoseyon's Leankernel. That and instructions are here:
http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-v05-beta-81612/
N00bs, Both of ^these^ steps above are completely optional and if you do choose to try them THIS THREAD is NOT the place to ask for support. Realize that before you start messing with stuff you don't understand.
If this guide helped you out, please consider hitting the thanks button.
Thanks
As per request, here's some initial screenshots:
{
"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"
}

Are you shure nothing will go wrong if we follow the steps you described. By the way its a great step by step description to get cm10. Can you post some screenshots of your phone. Thank you
I am itching to try it lol
Sent from my SCH-I535 using xda premium

I tried the 8/15 yesterday but flashed back to stock mainly because the phone wasn't seeing my ext SD card. Also it died on me I had to do a battery pull to get it back. I may have to try this out. Also I could not get WiFi tether to work or the built in portable hotspot. It sucks too because I actually pay for the service
Sent from my SCH-I535 using Tapatalk

majmuni said:
Are you shure nothing will go wrong if we follow the steps you described. By the way its a great step by step description to get cm10. Can you post some screenshots of your phone. Thank you
I am itching to try it lol
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'm in the process of getting some screenshots up, and I can't 100 percent confirm that it will work for you but if you follow the instructions I think theres a great chance
cell128 said:
I tried the 8/15 yesterday but flashed back to stock mainly because the phone wasn't seeing my ext SD card. Also it died on me I had to do a battery pull to get it back. I may have to try this out
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
What do you mean it "wasn't seeing it"? Didn't it show up in certain apps or recovery or what?

snoshreddax21 said:
I'm in the process of getting some screenshots up, and I can't 100 percent confirm that it will work for you but if you follow the instructions I think theres a great chance
What do you mean it "wasn't seeing it"? Didn't it show up in certain apps or recovery or what?
Click to expand...
Click to collapse
I think it was the music app and a bunch of photos
Sent from my Nexus 7 using Tapatalk

Do have a md5 for cm10 file please
Sent from my SCH-I535 using xda premium

Flashed and currently booting hopefully I keep it for a whole day lol. Do love the stock experience better than touchwiz
Sent from my Nexus 7 using Tapatalk

cell128 said:
I think it was the music app and a bunch of photos
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
You might try reformatting your card in your computer, but if that doesnt work I had a similar problem a while ago. For me I had to dig around in the preferences of my music player to direct it to the right folder (it would be mnt/extsdcard/[music folder]). It might be trying to find your music/pictures in the phone's internal memory rather than its SD card.
majmuni said:
Do have a md5 for cm10 file please
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It was in the post on Cyanogenmod's Google+ page, OP updated. Sorry about that

hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha

digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
I'm almost postive TWRP is your problem. I first tried it with the CWM touch version and that didn't work for me either. I think CM10/CM9 are very picky about which recoveries are compatible. Let me know how it goes for you.

digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk

cell128 said:
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
i used the unlock that was mentioned in the guide as people were reporting it was successful unlocks on the forums so i went ahead and used that.....im making my initial backup right now thru CWM non-touch and im gonna drop the zips for CM10 and gapps and will flash in the morn, im tired lol
one thing i did notice though is that for some reason my drivers are saying hardware id missing, and that only happened after root......i kept my imei but lost my hardware id lmao, i can still drag/drop files onto my phone but i have to switch from MTP to PTP mode for usb settings then switch it back to MTP to get access to the card/phone drives

digitalsynner85 said:
hmmm idk if i did something wrong the first time but i got the big yellow ! saying to bring my phone to big red about unofficial software going on it and i had to odin back to rooted stock to have access to my phone.....ill try using CWR instead of TWRP in hopes that i didn't screw something up in TWRP since im so familiar w/ CWR
note: i did that before finding this guide, im following this guide to a T and will follow up results tomorrow on it, so not trying to scare anyone from trying it, just saying i used my own method compiled from a few guides on here which consisted of using the root method listed in this guide, TWRP recovery from the unofficial cm10 guide, the cm10 files from cyanogenmods g+, and the gapps file from the cm10 guide haha
Click to expand...
Click to collapse
cell128 said:
Make sure you use the non touch recovery 6.something and that you are unlocked. It was probably because you were not unlocked properly
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Cell is correct, make sure you are using the "CWM 6.0.1.0" version. I'll update the OP so others don't get confused.

Thank you for your efforts OP.
Some friendly advice to you newer enthusiasts; be aware of bugs. If the CM team says this is an alpha build, you will more than likely hit some bugs regardless of what you read elsewhere.
Sent from my SCH-I535 using xda premium

jaj6503 said:
Thank you for your efforts OP.
Some friendly advice to you newer enthusiasts; be aware of bugs. If the CM team says this is an alpha build, you will more than likely hit some bugs regardless of what you read elsewhere.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
That's a very good point, and let's just clarify right now, I'm not a cyanogenmod developer and I don't have any control over how stable these builds come out. So if you flash and all is well except your MMS isn't working, I can't do anything for you and you're in the same boat as the rest of us. Thanks for bringing that up, jaj.
Sent from my SCH-I535 using xda app-developers app

I decided to flash tonight.....almost had a heart attack them woke everyone else up when i screamed when it flashed over lol.....great write-up man
Sent from my SCH-I535 using xda premium

digitalsynner85 said:
I decided to flash tonight.....almost had a heart attack them woke everyone else up when i screamed when it flashed over lol.....great write-up man
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Glad to hear it worked out for you
Sent from my SCH-I535 using xda app-developers app

since I have TWRP, how can I change it to CWM? I want to be able to flash this using CWM.

slick_shoes said:
since I have TWRP, how can I change it to CWM? I want to be able to flash this using CWM.
Click to expand...
Click to collapse
If you download the EZ Recovery app from the play store and flash CWM as mentioned in the guide, it will just overwrite the preexisting TWRP image and you can continue on from there.

I'm not understanding why the version or type of recovery matters. What does 6.0.1.0 do that twrp doesn't do except for supporting kexec?
Maybe I misunderstood what recoveries are all about. I had 6.0.1.0 for kexec support. Now that the bootloader is unlocked I'm thinking of going back to twrp.
Flashing the cm10 build should write to system and place a boot.img with the kernel on the phone. I don't see how a recovery would make a difference in doing this.
Forgive me if I missed something. I'm not questioning your intelligence or anything, just a curiosity as I only switched to cwm to use lean kernel with kexec.
Perhaps I missed even more, I see there is an alpha build of cwm that explicitly states it's for unlocked phones. Color me confused.
Sent from my SCH-I535 using xda app-developers app

Comparison of Clockworkmod recovery and TWRP

If you are a root user, you probably know what recoveries are, and you probably know what CWM and TWRP are. If you don't, please Google it, since this thread isn't about what recovery is...
I've been using CWM since my first Android device, Nexus S. However, after I switched to Galaxy Nexus, I've noticed this new recovery, which was TWRP, Team Win Recovery Project (Correct me if I'm wrong ).
Since I've used both as my daily recovery, I thought it'll be helpful for people to create a thread that compares these two
TWRP:
{
"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"
}
CWM:
These are version of recovery that I'm going to compare:
CWM version 6.0.1.0 Touch version for Galaxy Nexus
TWRP 2.2 for Galaxy Nexus
UI
Let's start with User Interface of these two recoveries. TWRP offers this fresh look that is not only easy to use, but also very intuitive. It has these big, yet polished buttons that makes using it a pleasure. I personally think that the UI is one of the strongest points of TWRP. CWM, on the other hand is just simple. It is just lines of options. For some, this might be great, but for a lot of people, including myself, it just not polished.
Navigation
Navigation is probably one of the most important elements of recoveries. TWRP offers really great navigation. Its "Swipe to Confirm" is one of my favorite, since this reduces the chance of flashing or wiping by mistake. It also offers this Back and Home button, which looks very familiar. CWM offers just easy-to-use navigation. That's it. Nothing too complicated. I find CWM to be just pick-it-up and flash kind of recovery.
Features
Now this is where TWRP shines big time. It offers soooooo many to the table than CWM. It has built in keyboard for naming backups and such. It has built in terminal, which can be pretty useful. It has built-in battery indicator and time, which is really handy. It also has built in file manager. It does all that with "basic features" such as flashing zip, factory resetting, mounting, and backup and restore. CWM just offers basic featues, nothing more. Of course, not a lot of people are gonna use terminal or file manager on recovery, but it is good to have a choice.
Compatibility
This is where CWM shines big time. Since, CWM was the only recovery until TWRP showed up, every mod and ROM is designed for CWM. Of course, since I am comparing Touch version, I have to mention that handful of mods doesn't work on CWM touch and only works on non-touch. This doesn't mean TWRP is only compatible with handful of mods. TWRP also works on most of the mods, but if there's a mod that you really want but only works on CWM, that can be a real pain in the rear end. Also I don't know if this also happens on other devices, but for Galaxy Nexus, if you want to flash stock ROM from Google developer site, TWRP won't let you.
Verdict
So which one is better? That's your personal opinion. Plus, I didn't create this thread to say which one is the best. I only created this thread so you guys know what each recoveries is right for you. I personally find CWM to be a little more stable and I find that CWM just works. However, TWRP offers these new and fresh features that advanced, and even just basic users and appreciate, but I still find that TWRP needs to work on some parts.
So which recovery do you use? I would like to know

I use TWRP for pretty much one reason only, it can mount through USB, which cwm can't do on the one s. Other than that I don't really find much difference in use, except that naming backups directly from recovery is nice
Sent from my HTC One S using xda app-developers app

Habarug said:
I use TWRP for pretty much one reason only, it can mount through USB, which cwm can't do on the one s. Other than that I don't really find much difference in use, except that naming backups directly from recovery is nice
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Oh there's no mount option on one s? You positive? Clockworkmod touch on galaxy nexus has that feature under mount I think. I can use adb to push files to the sdcard directory
Swyped on my Galaxy Nexus running AOKP nightly with Franco Kernel, overclocked to 1.4GHz

kyokeun1234 said:
Oh there's no mount option on one s? You positive? Clockworkmod touch on galaxy nexus has that feature under mount I think. I can use adb to push files to the sdcard directory
Swyped on my Galaxy Nexus running AOKP nightly with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
It's there, it's just that it does not work at least it did not work. I switched to twrp because of this and have never found a reason to switch back. On some units twrp also makes you able to flash boot through recovery (we don't have s off) but that doesn't work on mine.
Sent from my HTC One S using xda app-developers app

Habarug said:
It's there, it's just that it does not work at least it did not work. I switched to twrp because of this and have never found a reason to switch back. On some units twrp also makes you able to flash boot through recovery (we don't have s off) but that doesn't work on mine.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Haha ok
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

kyokeun1234 said:
I only created this thread so you guys know what each recoveries is right for you.
Click to expand...
Click to collapse
Should you not include 4EXT Recovery then also? That could be the right recovery for somebody.
kyokeun1234 said:
So which recovery do you use? I would like to know
Click to expand...
Click to collapse
Currently on 4EXT but wondering if I should go back to CWM.

Kavrocks said:
Should you not include 4EXT Recovery then also? That could be the right recovery for somebody.
Currently on 4EXT but wondering if I should go back to CWM.
Click to expand...
Click to collapse
Oops, I forgot 4ext :/ my apologies, but I never tried it, so I really can't give my opinion on it.
Swyped on my Galaxy Nexus running AOKP nightly with Franco Kernel, overclocked to 1.4GHz

Hello there !
I got question which could be silly for most of you but I really appreciate if someone would be nice to clear that for me.
When I want to do nandroid backup in clockworkmode recovery, everything is clean and simple. And backup folder is quite small. e.g. For Haier w910 that folder is about 25mb. And everything is saved. I can do wipe data formating and when I want back my earlier rom he is there with all settings and customisations.
When I try same thing to do through TWRP (on Huawei g510) I get few options for backuping. But if I want to backup all system and data and rom, TWRP shows me about 850mb.
Is there any options in TWRP to do nandroid backup of all system like in CWM Recovery ?
Thanks infront !

Good comparison.Anyway I love TWRP:laugh:

Another big plus for TWRP : its abitity to charge the battery.

MrAzerty said:
Another big plus for TWRP : its abitity to charge the battery.
Click to expand...
Click to collapse
Doesn't CWM do this as well? At least I've never noticed any battery drain when plugged in.

MattKneale said:
Doesn't CWM do this as well? At least I've never noticed any battery drain when plugged in.
Click to expand...
Click to collapse
Yup cwm also let the phone charge. Twrp just shows the battery percentage
Sent from my Nexus 4 using Tapatalk

Photon Q RSD Compatible FXZ

Thanks to Shabbypenguin for his fastbootable partitions of the Photon Q and thanks to mhous for modifying parts of the Atrix HD .xml file into the Photon Q.
This RSD Package contains 2 xmls for use, one standard one named after the build number, and one that does not flash the stock bootloader and is named as such. Put the one you want for use into RSD Lite and fire away. Have plenty of battery power (or use a Motorola Factory-Style cable or converter from Team Black Hat and you don't have to worry about that) and ALWAYS have your email from Motorola including the unlock code (UNIQUE_KEY) for your device backed up or saved somewhere. Just in case the fastboot locks it without you wanting it do, you'll have that code.
Use this file with Motorola's RSD Lite 5.7 or higher, and with the latest Motorola USB drivers.
Photon Q RSD Files / FXZ files: http://crackflasher.com/dev/mattlgroff/PhotonQ/7.7.1Q-6_SPR-89_ASA-36_SIGNED_CFC.zip
MD5: D864AB70881AF86EB225F0BF1D0A911B
RSD Lite 5.7: http://rootingmydroid.com/FILESYSTEM/DEVELOPMENT/UDPATES/-RSD-LITE/RSDLite57.zip
32 Bit Drivers (5.9): http://rootingmydroid.com/FILESYSTE..._End_User_Driver_Installation_5.9.0_32bit.msi
64 Bit Drivers (5.9): http://rootingmydroid.com/FILESYSTE..._End_User_Driver_Installation_5.9.0_64bit.msi
Happy flashing!

oh if you needed the xml i have that too. in fact i need to talk with you privately about some of the files. i posted up enough to fix anyones phone, but not everything in the zip

Do not flash this, it has bricked my phone... the MD5 for the system image is wrong, and even if you update that in the XML, it still fails to flash and remains stuck at fastboot flash failure. :crying:
Does anyone have the correct system image? I have sent shabbypenquin a PM trying to figure this out.

Gave this a try w the newest drivers & can't get past the system img. Tried several times, decrompressing new each time with no success. Even tried different cables & ports, still no luck.
Anybody have any thoughts on this?

bump...

thats teh word on the street. unfortunately the system.img is pulled from sprints files i dont know what else i could do to fix it

fallnSaint said:
Gave this a try w the newest drivers & can't get past the system img. Tried several times, decrompressing new each time with no success. Even tried different cables & ports, still no luck.
Anybody have any thoughts on this?
Click to expand...
Click to collapse
What state is your phone in? I can try to replicate as long as you're not soft-bricked.

shabbypenguin said:
thats teh word on the street. unfortunately the system.img is pulled from sprints files i dont know what else i could do to fix it
Click to expand...
Click to collapse
Well... $hit...
KitsunePaws said:
What state is your phone in? I can try to replicate as long as you're not soft-bricked.
Click to expand...
Click to collapse
Thanks KP, I'm not bricked; this is how I got into my "sticky" situation (pun totally intended). After system img failed, I was left in fastboot I flashed my recovery & restored. Other than the sticky fastboot, running fine. Well, I still haven't fixed my original problem but, that's for another thread.

Is this the same issue we are having w system.img?
http://www.xda-developers.com/android/swing-and-miss-motorola-razr-i-kernel-source-almost-here/
-Saint

any updates on a working rsd file?

Maxpowersxp said:
any updates on a working rsd file?
Click to expand...
Click to collapse
hopefully Motorola will release one. they said in the FAQs that they are choosing not to at this time, but hopefully they will at some point.
in the meantime, i wish we could make one. at this moment it seems we don't have any way of downgrading back to the original modem? (it was mentioned that there was a new modem in the update?)

Modified FXZ file
yogi2010 said:
hopefully Motorola will release one. they said in the FAQs that they are choosing not to at this time, but hopefully they will at some point.
in the meantime, i wish we could make one. at this moment it seems we don't have any way of downgrading back to the original modem? (it was mentioned that there was a new modem in the update?)
Click to expand...
Click to collapse
This package does not contain system.img!
This is here in case you break something that recovery does not touch.
If anyone has a problem with this being posted, let me know and I will pull the link. Props to mattlgroff for the original.
I edited the original file so that the broken system.img does not flash, everything else is unchanged. I tested this and it works fine.
I offer no support for this & it will wipe your internal sd card, you have been warned.
Modified 7.7.1Q-6_SPR-89_ASA-36_SIGNED_CFC.zip
md5: 851D8157D2A5ADE91E60ACCA0F04EA15

No problems whatsoever. I wanted to personally thank everyone on this forum for all of the dev help. When I unlocked my bootloader, I couldn't get CWM to flash properly, and I wound up erasing my ROM (don't ask lmao) and after 2 frustrating hours the posted boot.img & system.img files saved my phone. I am in everyone's debt, and I am willing to try out anything experimental for y'all now that I have TWRP and two good Nandroids. Thank u again for all of your help and hard work.
Sent from my XT897 using xda premium

I do have an issue each time i install the moto/sprint 77 update, my phone does nothing but reboot. I have a nandroid that is pre-update, but am I missing out on anything by not installing it? I rooted, installed arrgh's kernel and deodexed system before the update. Should i do an odexed system, stock kernel then update?
Sent from my XT897 using xda premium

I encourage all of you to
Sent from my XT897 using xda premium

drakeheart77 said:
I do have an issue each time i install the moto/sprint 77 update, my phone does nothing but reboot. I have a nandroid that is pre-update, but am I missing out on anything by not installing it? I rooted, installed arrgh's kernel and deodexed system before the update. Should i do an odexed system, stock kernel then update?
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
That's what I hear... You would probably get a better response and more help if you posted in the correct thread tho. The update thread is here: http://forum.xda-developers.com/showthread.php?t=1966998
-Saint

Ooops sorry thanks for the correction!
Sent from my XT897 using xda premium

fallnSaint said:
If anyone has a problem with this being posted, let me know and I will pull the link. Props to mattlgroff for the original.
I edited the original file so that the broken system.img does not flash, everything else is unchanged. I tested this and it works fine.
I offer no support for this & it will wipe your internal sd card, you have been warned.
Modified 7.7.1Q-6_SPR-89_ASA-36_SIGNED_CFC.zip
md5: 851D8157D2A5ADE91E60ACCA0F04EA15
Click to expand...
Click to collapse
This kind of worked for me. I was able to get out of the bootloader screen, but now it's stuck on the initial screen with just the red Motorola circle.
Any ideas on what I'm doing wrong?

Stefenatefun said:
This kind of worked for me. I was able to get out of the bootloader screen, but now it's stuck on the initial screen with just the red Motorola circle.
Any ideas on what I'm doing wrong?
Click to expand...
Click to collapse
Without more details as to what caused your problems originally I am kinda in the dark. I would guess that you have a problem with your system img, this RSD package should revert everything except system to stock. The bad news here is that if you did have a custom recovery, you don't anymore. If you have a good backup you will have to fastboot flash recovery again before you can use it. If you don't have a backup see here: http://forum.xda-developers.com/showpost.php?p=33391825&postcount=9
-Saint

fallnSaint said:
Without more details as to what caused your problems originally I am kinda in the dark. I would guess that you have a problem with your system img, this RSD package should revert everything except system to stock. The bad news here is that if you did have a custom recovery, you don't anymore. If you have a good backup you will have to fastboot flash recovery again before you can use it. If you don't have a backup see here: http://forum.xda-developers.com/showpost.php?p=33391825&postcount=9
-Saint
Click to expand...
Click to collapse
What I did was I went into the bootloader, flashed the zip, and rebooted after it finished. Now I am unable to access the bootloader, as the phone won't boot. By now, the battery's dead, anyways. Whenever I turn the device off, it turns on a couple seconds later. I would rather not take it apart, but if I have to, I'll do it.
The only thing I can access is the recovery, which just results in this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[q] urgent need help

Hi guys,
My phone now currently running android 2.3.4. My phone originate from Hong Kong and already unlock by the seller.
I received an update which include security fix by HTC.
I download the update and it require me to reboot to complete update. While installing, the error signal show up and i was stuck over there.
I tried factory reset and also hard reset, but the result still the same.
Below are the picture, please have a look :
{
"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"
}
Thank you

Do you have a custom recovery (like Clockwork Mod or 4ext) installed and if so have you tried rebooting the phone in recovery?
Sent from my HTC Sensation 4G using xda premium

Vaporizers said:
Do you have a custom recovery (like Clockwork Mod or 4ext) installed and if so have you tried rebooting the phone in recovery?
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Nop, any idea how to format this phone with official ROM ? because i think the current ROM got problem.

Not sure it will work or not
Remove battery , insert battery ,press volume down + power button at same time... And from bootloader select factory reset . And then reboot
Btw r u sure u dont have custom recovery ????
Sent from my HTC Sensation using xda app-developers app

Itsakash said:
Not sure it will work or not
Remove battery , insert battery ,press volume down + power button at same time... And from bootloader select factory reset . And then reboot
Btw r u sure u dont have custom recovery ????
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
Thank you for the reply. I did that before. The problem still the same.
I'm pretty sure for that, it's because the device i just brought it few days.

Have you tried downloading the ruu you need and trying that? I've had to ruu back to stock a couple times....doesn't hurt to try.
Sent from my HTC Sensation using Tapatalk 2

MunkyButt said:
Have you tried downloading the ruu you need and trying that? I've had to ruu back to stock a couple times....doesn't hurt to try.
Sent from my HTC Sensation using Tapatalk 2
Click to expand...
Click to collapse
Actually i not really know how to do. Can you provide me a link for RUU?an official ROM link for me to download perhaps.
I did try to ask the repairing shop, they not dare to help me to reformat, the reason is, they say my phone originate from Hong Kong and i currently now in Malaysia.They do not want to take the risk. I'm so Helpless =(

Before you do any more flashing of anything, go back to the bootloader (pull battery, then power button + volume down) and post here EXACTLY what you see on the screen. If possible just take a picture of the screen.
It makes me nervous that you got your phone from Hong Kong and then an update didn't work. There are a lot of fake Sensations coming out of China. They look like the real ones, but the hardware is different and firmware/roms/radios made for the Sensation won't work on them.
If you have a fake one, trying to flash an RRU on it will deffiantely kill it and kill it badly.

Skipjacks said:
Before you do any more flashing of anything, go back to the bootloader (pull battery, then power button + volume down) and post here EXACTLY what you see on the screen. If possible just take a picture of the screen.
It makes me nervous that you got your phone from Hong Kong and then an update didn't work. There are a lot of fake Sensations coming out of China. They look like the real ones, but the hardware is different and firmware/roms/radios made for the Sensation won't work on them.
If you have a fake one, trying to flash an RRU on it will deffiantely kill it and kill it badly.
Click to expand...
Click to collapse
I check from HTC already. They asking me provide them my IMEI, after they check, they told me my phone was originate from Hong Kong.
I think should be original..haha..hopefully..
and here is my screenshot

fookelvin said:
I check from HTC already. They asking me provide them my IMEI, after they check, they told me my phone was originate from Hong Kong.
I think should be original..haha..hopefully..
and here is my screenshot
Click to expand...
Click to collapse
Yeah that looks all legit.
I didn't mean to scare you. But that's been happening lately where someone buys a knock off, tries to install Sensation software, and bricks the phone.
To fix your problem you may have to use ADB to install a custom recovery. Or you should be able to do it using a PM58IMG file. I'm pretty sure there's a PM58IMG file for flashing 4EXT in the 4EXT thread in the dev section. Just put the file on your SD card (using a computer, obviously since the phone doesn't work) boot into bootloader, and let it run. You should then have 4EXT
You can also upgrade the firmware the same way if you want to get ICS or Jelly Bean.
I think your problem is a lot more fixable than it seems. So don't stress. You should have this up and running oon.

Skipjacks said:
Yeah that looks all legit.
I didn't mean to scare you. But that's been happening lately where someone buys a knock off, tries to install Sensation software, and bricks the phone.
To fix your problem you may have to use ADB to install a custom recovery. Or you should be able to do it using a PM58IMG file. I'm pretty sure there's a PM58IMG file for flashing 4EXT in the 4EXT thread in the dev section. Just put the file on your SD card (using a computer, obviously since the phone doesn't work) boot into bootloader, and let it run. You should then have 4EXT
You can also upgrade the firmware the same way if you want to get ICS or Jelly Bean.
I think your problem is a lot more fixable than it seems. So don't stress. You should have this up and running oon.
Click to expand...
Click to collapse
=) you seriously scare me T_T..haha..! By the way, can u show me the steps and link maybe or require software? I will really really appreciate you~

Use this guide, follow the steps exactly!! for installing 4ext second method, and the remainder of the document for firmware and the arhd rom. Your phone is already s-off.
http://forum.xda-developers.com/showthread.php?t=1472298&highlight=4ext

mb_guy said:
Use this guide, follow the steps exactly!! for installing 4ext second method, and the remainder of the document for firmware and the arhd rom. Your phone is already s-off.
http://forum.xda-developers.com/showthread.php?t=1472298&highlight=4ext
Click to expand...
Click to collapse
my kernel version is 2.6.35, there is nothing with kernel in order to do that right?
everything is official ROM? follow exactly step 1-step 5?

fookelvin said:
my kernel version is 2.6.35, there is nothing with kernel in order to do that right?
everything is official ROM? follow exactly step 1-step 5?
Click to expand...
Click to collapse
Yes if you want ics ARHD rom.. Follow both the first post and second post
Edit: wait you just want to do an official ota update?
Then maybe you are rooted..
Did you have any superuser or supersu app?
Otherwise might be recovery... From the bootloader (screen shot one).. Select recovery and the tell me what it shows
Sent from my HTC Sensation using xda premium

ganeshp said:
Yes if you want ics ARHD rom.. Follow both the first post and second post
Edit: wait you just want to do an official ota update?
Then maybe you are rooted..
Did you have any superuser or supersu app?
Otherwise might be recovery... From the bootloader (screen shot one).. Select recovery and the tell me what it shows
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Nop, i pretty sure i do not have superuser app inside my devices. Because once i get my phone, first thing i do is,
search for the update.
then i failed to update. So i think the current android version have problem. I wanted to fix it with official rom

fookelvin said:
Nop, i pretty sure i do not have superuser app inside my devices. Because once i get my phone, first thing i do is,
search for the update.
then i failed to update. So i think the current android version have problem. I wanted to fix it with official rom
Click to expand...
Click to collapse
anyway, how can I install "OTA_Pyramid_LE_hTC_Asia_HK_1.73.708.3-1.73.708.2_release_220041l8r0sjvypo1sal7n" this zip file VIA PC?

ganeshp said:
Yes if you want ics ARHD rom.. Follow both the first post and second post
Edit: wait you just want to do an official ota update?
Then maybe you are rooted..
Did you have any superuser or supersu app?
Otherwise might be recovery... From the bootloader (screen shot one).. Select recovery and the tell me what it shows
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
anyway, how can I install "OTA_Pyramid_LE_hTC_Asia_HK_1.73.708.3-1.73.708.2_release_220041l8r0sjvypo1sal7n" this zip file VIA PC?

Hey guys, i have new discover. I found Status(7) and installation aborted. What error is' it actually? i was trying to install the official update manually.
[/IMG]

fookelvin said:
Hey guys, i have new discover. I found Status(7) and installation aborted. What error is' it actually? i was trying to install the official update manually.
[/IMG]
Click to expand...
Click to collapse
It seems md5 mismatch.. The update is probably not for this phone or might have missed a intermediate update or the downloaded zip is corrupted
Sent from my HTC Sensation using xda premium

ganeshp said:
It seems md5 mismatch.. The update is probably not for this phone or might have missed a intermediate update or the downloaded zip is corrupted
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
so what should i do know ? T__T sad~~