Related
I have downloaded the RAR file, but after taking a look at it I can see that it is not like any ROM updates provided by Bell. Can anyon some instruction or point me to another thread that explains this??
Thanks
1)after you download it just extract the file in a new folder
2) Then goto that folder and u will "ROMUpdateUtility" double click on that.
3) just follow the instructions that appears on your computer screen after.
I'm thinking he probably doesn't have WinRAR.
loll thenn ill add another step:
4) download WINRAR and extract the files.
then follow my other other steps.
Do the CDMA Roms require a HARDSPL to flash them? I want to flash a CMDA NSFAN Rom to my friends Vogue and I dont see an stickies for flashing a CDMA rom. I normally spend most of my time in the Kaiser/Raphael Forums.
Any help is greatly appreciated.
Thanks,
Daniel
So I just did a ton of research on the web because the wiki is useless and might as well not exist.
I am using a Sprint HTC Touch with the official Sprint WM6.1 ROM from HTC.
So after my research, this is what I got (Please correct me if I am wrong):
1. Run 2.31.Coke and unlock the phone via USB/ActiveSync
2. Download NSFAN's latest Sprint WM6.1 Rom and extract to desktop
3. Rename ROMFILE.nbh to voguimg.nbh
4. Copy voguimg.nbh to MicroSD card that has been formatted to FAT32
5. Insert MicroSD card in phone, and enter bootloader via holding down the Power/Camera/Reset buttons all together.
6. Flash ROM
7. Hard Reset Phone
8. Enjoy
So to the everyday flasher here on the Vogue forum, are these steps correct? And if so, why dont you take the time to update the wiki so people dont have to ask the same repetitive question 1000 times?
I just cant believe that this forum has zero ROM flashing stickies, or and updated wiki.
Either way, any help would be greatly appreciated.
Thanks again,
Daniel
atomixpaintball said:
So I just did a ton of research on the web because the wiki is useless and might as well not exist.
I am using a Sprint HTC Touch with the official Sprint WM6.1 ROM from HTC.
So after my research, this is what I got (Please correct me if I am wrong):
1. Run 2.31.Coke and unlock the phone via USB/ActiveSync
2. Download NSFAN's latest Sprint WM6.1 Rom and extract to desktop
3. Rename ROMFILE.nbh to voguimg.nbh
4. Copy voguimg.nbh to MicroSD card that has been formatted to FAT32
5. Insert MicroSD card in phone, and enter bootloader via holding down the Power/Camera/Reset buttons all together.
6. Flash ROM
7. Hard Reset Phone
8. Enjoy
So to the everyday flasher here on the Vogue forum, are these steps correct? And if so, why dont you take the time to update the wiki so people dont have to ask the same repetitive question 1000 times?
I just cant believe that this forum has zero ROM flashing stickies, or and updated wiki.
Either way, any help would be greatly appreciated.
Thanks again,
Daniel
Click to expand...
Click to collapse
You are correct, but you do not need to do steps 3 thru 5. After you extract the ROM on your desktop simply doubleclick the RUU utility and it will update your ROM. (you must still be connected via USB to computer) If you want to flash from your storage card instead then do steps 3 thru 7.
I have a bell phone,
and the color screen says .36 and Security Unlocked.
do i have to unlock the phone still ?
its a bell phone, and it was like that when i got it.
does this mean its unlocked?
latinjig said:
I have downloaded the RAR file, but after taking a look at it I can see that it is not like any ROM updates provided by Bell. Can anyon some instruction or point me to another thread that explains this??
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=3680838&postcount=2
Detroit Doug
By the way, who needs WinRAR when you can get 7-Zip, the best all-around file compression/decompression tool around! And it's free. Opens almost anything out there all in one program.
http://7-zip.org/
hey..
i just had a quick question.. is it possible to switch back to the original BELL rom after you upgrade to NFS rom? i know a lot you might think why would you even wanna do that? But I was just wondering just incase..
Absolutely very easy just flash it like the instruction of a stock rom would require you too
Because of my stupid mistakes of making my SD card failed the first time, I found a way to actually downgrade the system using HBoot mode even if you have a new HBoot system (i.e. Official Chinese version, Carrier Locked version, etc).
First thing to do, is to download the 2.73.405.5 official WWE RUU package (the exe);
Then, run that wizard, and while the wizard's program is running, search in your PC's %userprofile% folder, and look for "rom.zip"
Rename that rom.zip to HEROIMG.zip.
Put that file into your MicroSD card's root folder. Do not modify its contents.
put that SD card into your phone.
While the card is in, hboot the device (vol down + power).
it will pop up the HBOOT mode of the device. It will now check for a few files if they exist on your SD card. (HERODIAG.zip, etc)
in the last check, it will look for HEROIMG.zip, and tries to load it. Once the loading bar is complete on the top right side of the device, it will ask you to press home to continue the upgrade, or press other key to escape it. (i am not 100% sure if those are the keys, but you can read english so figure that part out).
Once the flashing is done (remember, this method will wipe everything. including radio, recovery, system, data, cache), you will now have a complete original ROM on your system. From there, use InstantRoot or any other rooting exploit, to root your device, put Cyanogen's recovery there, and start upgrading into custom roms!
Let me know if this method works or not. it worked on 3 of my friend's HTCs.
/* p.s. however i still have my unresolved issue about the SD card slot and USB device not recognized issue. */
Nope, I tried that before and it fails the CID check.
Guiness in a can? BRILLIANT!
yea, everyone has been jumping through their butts trying to figure out how to make goldcards and bypasses... why not just use hboot like htc probally uses it? Duh! Thanks for this!
edit..... oh snap....
does not work for me!
Once the loading bar is complete on the top right side of the device
go back to hboot...
and nothing to do
this won't work because the SPL is still checking the CID of the rom.zip you renamed to HEROIMG
for some people the flash will work, but thats because they have a hero with a CID thats in the range of the cid numbers (open the .zip file and check the android-info.txt to see the list.
changing topic is this is confusing people
nice try though
Otiginal IMG
Confirm ...works for me.After rooting...... and flashing couple images i try reflash back original rom - official ruu not want work ...stop on bootloader .....extracted rom not be a flashable trough sd card and amon ra loader....this way work like charm.Thnx.
Original IMG
Confirm ...works for me.After rooting...... and flashing couple images i try reflash back original rom - official ruu not want work ...stop on bootloader .....extracted rom not be a flashable trough sd card and amon ra loader....this way work like charm.Thnx.
Thank you, you are the man!
Thank you so much, i was about to eat my phone. it is htc hero and it worked. thank you so much...
since we have this thread i can ask as well...
is HEROIMG.ZIP signed, or why wouldn't one just alter the CID values in android-info.txt?
kendong2 said:
since we have this thread i can ask as well...
is HEROIMG.ZIP signed, or why wouldn't one just alter the CID values in android-info.txt?
Click to expand...
Click to collapse
I believe it is signed using HTC's own personal keys, preventing us changing the RUU extract.
anon2122 said:
I believe it is signed using HTC's own personal keys, preventing us changing the RUU extract.
Click to expand...
Click to collapse
Might be worth a test to do self signed ?
Jesterz said:
this won't work because the SPL is still checking the CID of the rom.zip you renamed to HEROIMG
for some people the flash will work, but thats because they have a hero with a CID thats in the range of the cid numbers (open the .zip file and check the android-info.txt to see the list.
changing topic is this is confusing people
nice try though
Click to expand...
Click to collapse
hi, i have the same problem and my cid is in in the list.
what could be the problem?
How the hell did you came up with that?
It worked perfectly! Cannot thank you enough.
You're the man.
been looking for this for nearly a week.
got my wife a new phone and want to store it original, but couldnt get back to stock,all cid fails.
with this version no cid fail and stock htc hero again.
thanks, you tha man.
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.
Thanks... a very useful guide. Bookmarked
WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!
I keep getting "md5sum: not found"
Put this in the general android section as it works across most devices. ..
Sent from my One V
Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.
I fixed it in adb
Sent from my SPH-L710 using xda premium
Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!
thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
CWM showing different versions
-Delete-
maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out
Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app
Thank you so much. You saved my phone.
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)
plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz
Hello,
I recently uninstalled some (system / T-Mobile) apps with Titanium Backup. And I did not make a backup first. The phone still runs fine but the OTA fails.
I tried so far:
- RUU 1.28 -> does not work, because system is already 1.29
- find rom.zip and unpack -> Ok, but cannot unpack system.img, unyafs fails.
The file which the OTA misses, according to logfile is named: 4661_TMODE_Music_One.odex
If someone could sent me this file or upload it somewhere I would be thankful.
There is a good chance that there are more files missing, but the log stops after the first fail.
I see in the system.img that there are at least 4 files with similar names:
4661_TMODE_Music_One.odex
4661_TMODE_Music_One.apk
4662_TMDE_Games_One.odex
4662_TMDE_Games_One.apk
If anyone knows how to unpack these, this would also helpful.
deleted
I think the best way to get all your bloatware back is to lock the bootloader and then flash the 129 RUU. Here is the link for the RUU if its T-mobile uk.
http://www.filefactory.com/file/6y1...Radio_1.1204.105.14_release_260731_signed.exe
Once your back to stock you can unlock again with your unlock token, flash cwm and make a stock nandroid backup.
If you need a file factory password pm me.
No, it's T-Mobile Germany, so I guess this will not help.
At the moment I'm trying to unpack the files from the system.img, but none of the methods described in the forums are working.
It is almost crazy, I can see the filenames and contents (lots of "PK" headers for instance) within the system.img but I've no idea how to extract them.
Get in touch with football. He might be able to get the RUU for you.
ghori1989 said:
Get in touch with football. He might be able to get the RUU for you.
Click to expand...
Click to collapse
Ok, tried that, waiting for the reply.
Meanwhile I'm able to mount the system image with some modifications as ext4 image and copy the contents. If there is an interest for this, I propably could write some tool to make this automatic.
Anyway, it did not help me, because the versions of the files in the image do not match the ones expected from the OTA.
See my other thread about the upgrade message when I connect to HTC sync manager. (Even though the phone reboots and goes thru several flash screens, nothing is changed)
Phone is HTC Desire 526 Verizon prepaid.
This time, I let it run again, but I opened the program temp folder in explorer and grabbed the files.
It has a 1.2GB file that I'm guessing is system image and a 10MB file labeled boot image.
I uploaded it to my Google drive in the hopes that someone here can find a way to use it to get us a custom ROM, or at least root, going.
Here's the files:
https://drive.google.com/folder/d/0B_Sgf7j8WktiM0pmcDJveVBFWUU/edit
Cheers.
Are those files for the US or the Europe version?
Ynlord said:
Are those files for the US or the Europe version?
Click to expand...
Click to collapse
USA, Verizon prepaid
ericpeacock79 said:
USA, Verizon prepaid
Click to expand...
Click to collapse
Which one is exactly the temp directory of the program?
Ynlord said:
Are those files for the US or the Europe version?
Click to expand...
Click to collapse
Ynlord said:
Which one is exactly the temp directory of the program?
Click to expand...
Click to collapse
I pulled those files from the temporary download location of the HTC program on Windows, just after it downloaded the update, while it was copying the files to the phone.
It was in the Program Files directory of the HTC desktop program, instead of the windows user profile temp folder like most programs.
The files uploaded are the update files.
ericpeacock79 said:
I pulled those files from the temporary download location of the HTC program on Windows, just after it downloaded the update, while it was copying the files to the phone.
It was in the Program Files directory of the HTC desktop program, instead of the windows user profile temp folder like most programs.
The files uploaded are the update files.
Click to expand...
Click to collapse
I was having trouble downloading the one that you posted, i downloaded again with the htc sync manager and got it on this location C:\Users\<your_user_name>\AppData\Local\HTC MediaHub\FOTA.
Should i go to recovery and fast it or should i use adb for it?
Ynlord said:
I was having trouble downloading the one that you posted, i downloaded again with the htc sync manager and got it on this location C:\Users\<your_user_name>\AppData\Local\HTC MediaHub\FOTA.
Should i go to recovery and fast it or should i use adb for it?
Click to expand...
Click to collapse
I do not know if it would work like that. If I had to guess, I would say fastboot, but I really don't know.
I will try it tomorrow and let you know. I still have the phone, but I don't use it and can't seem to sell it on Craigslist...
Is it possible to unpack an image of the non branded version and compare the differences.. see what we can change to possibly allow hot-spot or root?
hemanolio said:
Is it possible to unpack an image of the non branded version and compare the differences.. see what we can change to possibly allow hot-spot or root?
Click to expand...
Click to collapse
That might be difficult, given that the US-market 526 was only sold by Verizon and doesn't seem to be too popular of a phone. I never found a way to order it unlocked straight from HTC.
Does the boot.img have an unlocked bootloader?I need one thats unlocked
there is no unlocked bootloader for the Vreizon prepaid Desire 526.
I posted these files in the hopes that someone could use them to get us unlocked.
Thank You for the files.
I will take a look and let you guys know how to flash it.
It will help the bootloader issue.
I need these files to keep working on this.
Thanks again
---------- Post added at 05:54 PM ---------- Previous post was at 05:46 PM ----------
To flash the rom. Whichever of the 2 downloads it is ???
rename the file to
Code:
0PM3IMG.zip
Copy 0PM3IMG.zip to the external sd card.
Boot the phone into the bootloader / download mode.
It should find the file on the sdcard and ask you if you want to install it.
I will test it out later.
Basically if you mess something up in the phone by deleting files or whatnot this should be useable to flash back to stock.
I know I'm just an amateur with programming but couldn't you/we just "Frankencode" it? Like have two/three of the same file and keep one original, have another be the successful edit, and have another be the experimental editing?
To some extent that is what i'm working on.
The Desire 626s is the same chipset and the boot-loader is unlockable.
These RUU files / ( Factory Rom ) ruu = rom update utility come packed with some goodies.
The bootloader is in the packages for the 526 and the 626.
The question is how to flash the files from the 626 to the 526.
The ruu uses a couple different security measures to make sure the files aren't tampered with.
The main zip file is signed with keys and verified to be signed against the public half of the keypair.
It's a file called keys in the /res folder of the recovery.img ramdisk.
By generating a pair of keys ( Private and Publick ) .pk8 and .pem and dumping the public key with dumppublickeys it is possible to change the key in the /res/key of the ramdisk. This means we can modify the main zip file and sign it with our own keys and it will pass the signature test.
But the zip files inside of the main zip are also signed / encrypted.
We can decrypt the inner zip files with bruuveal. So that can extract the zip files and not get errors.
Or use the HTC Decrypt tool found on this forum.
The interesting thing here is that prior to the ruu flashing the phone it flashes the HOSD.
That's the smaller zip file.
The only reason for HTC to do that i'm thinking is because the hosd / hboot that is on the phone to begin with blocks writing of the necessary partitions by some means.
So the hosd is pre-updated to allow the main ruu to flash.
This is not the case on the 626s. The other interesting thing is that the hosd flashes by itself in the main zip not a sub zip and like I said I can get around the first file signature.
If I can get the 626s firmware to flash to the 526 then we can unlock the boot-loader.
If we can find a way to get around the inner file signing ( If I can figure out where the public half of the key is)
You can flash the software using fastboot...
fastboot flash zip <name 1st zip>
fastboot flash zip <name 2nd zip>
If the second file will not be able to - use htc_fastboot
where to take - when unpacking (executing)standart RUU file
Anyone find a solution to this problem? I have the desire 526 and it froze during upgrading with the htc sync, now it doesn't go past the boot screen and I've searched for a solution to this problem everywhere.
Is it safe to say that none of the forums have a solution to the Desire 526 vzw prepaid problem? I've searched multiple forums, youtube videos, and no one either answer the problem or the answers do not work. However most of us are just looking for the original boot & recovery, but that seems to be an impossible mission. Hopefully, someone in some forum will come up with a solution that actually works, or someone will actually respond to some of our questions.
ericpeacock79 said:
See my other thread about the upgrade message when I connect to HTC sync manager. (Even though the phone reboots and goes thru several flash screens, nothing is changed)
Phone is HTC Desire 526 Verizon prepaid.
This time, I let it run again, but I opened the program temp folder in explorer and grabbed the files.
It has a 1.2GB file that I'm guessing is system image and a 10MB file labeled boot image.
I uploaded it to my Google drive in the hopes that someone here can find a way to use it to get us a custom ROM, or at least root, going.
Here's the files:
https://drive.google.com/folder/d/0B_Sgf7j8WktiM0pmcDJveVBFWUU/edit
Cheers.
Click to expand...
Click to collapse
curious to know what file are we suppose to use?
badHTC526 said:
curious to know what file are we suppose to use?
Click to expand...
Click to collapse
No idea. I just put these up in the hopes that someone would be able to put them to good use. I'm not a dev, sorry.
I was able to find quite a few RUU's for HTCD100LVW after excavaing into the mythical 2nd & later pages of Google search. I can't remember how bad my soft brick was, but I spend somewhere near 40 hours ****ing this phone up before finally pulling the right bootable sd image on BigCountry's BL/root/TWRP method
Sent from my Desire 526 using XDA Labs