I bricked my MDA compact3 (t-mobile UK) and i need this rom:
RUU_Artemis_TMO_UK_3.11.110.2_4.1.13.41_02.88.90
IPL 3.11.0001
SPL 3.11.0000
i found it but the file is corupted and i need another link from where i can get it.
please heeeeelp!!!!
iamandi said:
I bricked my MDA compact3 (t-mobile UK) and i need this rom:
RUU_Artemis_TMO_UK_3.11.110.2_4.1.13.41_02.88.90
IPL 3.11.0001
SPL 3.11.0000
i found it but the file is corupted and i need another link from where i can get it.
please heeeeelp!!!!
Click to expand...
Click to collapse
You found this one? http://www.megaupload.com/?d=S1M9EDG8
download size is 49.19 mb, which should be ok. Try redownloading it if you have another size.
If this is not the one: where did you find yours, and what error message do you get
edit: after downloading and trying to run it, I get this error message:
The contents of this file cannot be unpacked. The executable you are attempting to run has been corrupted. Please obtain another copy of the file, verify its integrity, and try again
Click to expand...
Click to collapse
I've tried unpacking it with winrar, but the I get an error message also. Looks like you have to find another (copy of the) rom
Also you have an SPL which looks original. You should run USPL before attempting to flash any non-standard rom.
yes i.ve got the same link . now i'm waiting the reply from the guy how made the upload of this ROM to see if he stiil have it
Hi everyone.
Yesterday I tried to flash a WinMob 6.5.1 ROM.
It failed. After flashing 3%, the USB disconnected and that flashing assistant told me, that the image file is corrupt.
I used different .nbh files from www.thewingster.com.
I tried this: http://forum.xda-developers.com/showthread.php?t=561086
What I did was the following.
I installed 3 .cab files (a.k.a. HardSPL I think)
I extractet that RUUKitchen Thing and put the .nbh into the Folder and started the Program (with admin rights).
Is that all I have to do, or did I forgot to do something or did something wrong?
Thank you.
PublicITI said:
Hi everyone.
Yesterday I tried to flash a WinMob 6.5.1 ROM.
It failed. After flashing 3%, the USB disconnected and that flashing assistant told me, that the image file is corrupt.
I used different .nbh files from www.thewingster.com.
I tried this: http://forum.xda-developers.com/showthread.php?t=561086
What I did was the following.
I installed 3 .cab files (a.k.a. HardSPL I think)
I extractet that RUUKitchen Thing and put the .nbh into the Folder and started the Program (with admin rights).
Is that all I have to do, or did I forgot to do something or did something wrong?
Thank you.
Click to expand...
Click to collapse
Try flash this rom:
http://forum.xda-developers.com/showthread.php?t=437630
after this hard spl try to flash wm6.5.1. I have flashing this wm6.5.1 from sd card http://forum.xda-developers.com/showthread.php?t=559307 and work gooood.
This is NOT development related. Please post on the correct section next time.
PublicITI said:
Hi everyone.
Yesterday I tried to flash a WinMob 6.5.1 ROM.
It failed. After flashing 3%, the USB disconnected and that flashing assistant told me, that the image file is corrupt.
I used different .nbh files from www.thewingster.com.
I tried this: http://forum.xda-developers.com/showthread.php?t=561086
What I did was the following.
I installed 3 .cab files (a.k.a. HardSPL I think)
I extractet that RUUKitchen Thing and put the .nbh into the Folder and started the Program (with admin rights).
Is that all I have to do, or did I forgot to do something or did something wrong?
Thank you.
Click to expand...
Click to collapse
Well you can see if you're HardSPLed by going into the bootloader, and looking at your SPL, I believe. It should be 4.7 or something.
If you're hardSPLed, then the ROM you're flashing probably requires you to flash through the storage card, NOT through USB!! You'll find instructions on how to do that on one of Mr. Ill's ROM pages. I wrote the instructions up, they should work for you.
Hi Guys,
I'm having some problems with the correct installation of CoreDroid 1.6 after updating everything else , I stuck in the part updating files from SD Card....which simply doesn't work only thing it tells me is "No files found."
Placed them several times there, zipped, unzipped, renamend, etc....always the same error....
Could someone help me in this, pls?
cheers,
Gigi
Gigi99 said:
Hi Guys,
I'm having some problems with the correct installation of CoreDroid 1.6 after updating everything else , I stuck in the part updating files from SD Card....which simply doesn't work only thing it tells me is "No files found."
Placed them several times there, zipped, unzipped, renamend, etc....always the same error....
Could someone help me in this, pls?
cheers,
Gigi
Click to expand...
Click to collapse
Hi,
Backup all data before starting anything new.
All coredroid roms come with detailed installation instructions.
Place the coredroid rom ZIP on the root of your sd card.
Flash new partition,go to CWM ,wipe data,cache partition,dalvik(advanced)>install zip from sd card>choose zip>install>reboot
Thanks....the installation description was for version 1.12....your description worked fine....thanks!
Hi, guys. First of all, thanks for all of your hard work and time you put into all of these custom ROMs.
So, I rooted my HTC Tattoo, then flashed it with CyanogenMod 7 and I am very happy how ROM works. I was wondering how can I get back to stock (for warranty reasons) since I was stupid enough to not make a backup of Stock rom with ROM Manager.
First, I tried installing RUU exe file(RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver) from Winows 7 computer, but when I connect my phone to PC, i got error message 170 saying "USB Connection Error".
When that didn't work, I downloaded and put CLICIMG.zip (I belive thats rom.zip from RUU) on root of my SD card, then rebooted to HBoot, but i got error saying something like "No images found in CLICIMG". I also tried to rename this file to CLICKIMG.zip, CLICDIAG.zip, but that didn't work either.
Hope you can help me somehow.
Thanks.
PavleSRB said:
First, I tried installing RUU exe file(RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver) from Winows 7 computer, but when I connect my phone to PC, i got error message 170 saying "USB Connection Error".
When that didn't work, I downloaded and put CLICIMG.zip (I belive thats rom.zip from RUU) on root of my SD card, then rebooted to HBoot, but i got error saying something like "No images found in CLICIMG". I also tried to rename this file to CLICKIMG.zip, CLICDIAG.zip, but that didn't work either.
Click to expand...
Click to collapse
Hope the CLICIMG.zip you have downloaded is not corrupt.
Best thing would be to copy the rom.zip form the temp folder,
Here is what you can do:
After you started RUU wait until you get the prompt to proceed or you get the usb error and don't close the application
Then you can get rom.zip file from following folder
"C:\Users\<your user name>\appdata\Local\Temp"
replace "your user name" with your account name in windows
copy the rom.zip and rename it to CLICIMG.zip
place it in root of SDCARD and proceed
Thanks for replay. I managed to resolve this, I will post little guide soon on this topic.
Received the OTA update. Click reboot and install. TWRP pops up, nothing happens.
Log:
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/BrowserProviderProxy.odex", "21a89
E:Error in /cache/094f6629314a.signed-nakasi-JOP40C-from-JZ054K.094f6629.zip
(Status 7)
Installation aborted.
Anyone know what just happened? ::crying:
I have just had a similar problem, stock rooted tried to update to 4.2 OTA when it was updating I got the android on his back with the red exclamation sign. I had no idea what was wrong until I read your post.
I am not sure how to look at the log file so I don't know if I have the same problem as up but the file you referenced I changed the extension so it was not recognised to allow Flash to work. I have now changed this back but update system in setting says that the system is up to date but I am still on 4.1.2.
sharpened_edge said:
I have just had a similar problem, stock rooted tried to update to 4.2 OTA when it was updating I got the android on his back with the red exclamation sign. I had no idea what was wrong until I read your post.
I am not sure how to look at the log file so I don't know if I have the same problem as up but the file you referenced I changed the extension so it was not recognised to allow Flash to work. I have now changed this back but update system in setting says that the system is up to date but I am still on 4.1.2.
Click to expand...
Click to collapse
Had same problem, updated manually via ROM Image from google.
penguinolog said:
Had same problem, updated manually via ROM Image from google.
Click to expand...
Click to collapse
Is this like flashing a new Rom?
Does it wipe all personal data and apps from the Nexus7 when the update completes?
When My galaxy SII upgraded from gingerbread to ICS it took me days to get it up and running how I had it before. I doing stuff like using E-mail (Oh wait all my settings are gone). Ill just have a look at my love film list and add some rentals (Oh wait the apps gone). You get the picture.
Had the same Problem yesterday.
I extracted the corrupted Files from the 4.1.2 Firmware and replaced them in the system.
Finally it worked and i am @ 4.2 now without loosing my Data.
Alex
DroidBonzai said:
Had the same Problem yesterday.
I extracted the corrupted Files from the 4.1.2 Firmware and replaced them in the system.
Finally it worked and i am @ 4.2 now without loosing my Data.
Alex
Click to expand...
Click to collapse
If you could expand on what you did? I have changed the file extension back on the file in question. My problem is that since I failed the update, the system says no update available and I am stuck on 4.1.2
I had a similar problem with zoneinfo.dat.
However, I followed this topic and it worked with keeping root
http://forum.xda-developers.com/showthread.php?t=1989943
tom1807 said:
I had a similar problem with zoneinfo.dat.
However, I followed this topic and it worked with keeping root
http://forum.xda-developers.com/showthread.php?t=1989943
Click to expand...
Click to collapse
Thanks, problem is I would lose all my user data opposed to a upgrade.
All files I saved before were not deleted, just had to reinstall my applications.
Or make an backup with Titanium
sharpened_edge said:
If you could expand on what you did? I have changed the file extension back on the file in question. My problem is that since I failed the update, the system says no update available and I am stuck on 4.1.2
Click to expand...
Click to collapse
Ok i'll try.
Sorry for my bad english
I'll do a step by step howto.
First of all you'll need to download the 4.1.2 FW from Google.
Make sure, you choose the right one.
Take your Nexus 7, go into settings---> About Tablet and look for the Build-number.
Google OS
Then you will have to download this Tool (SGStoEXT4)
(This Tool will extract the Image into a mountable (readable) Image.)
Then you download THIS
(This Tool will mount your Image and you'll get access to the orig. Systemfiles you need.)
Ok lets begin:
Once you've dowloaded the Firmware 4.1.2 (Not 4.2 !!). It should be a .tgz. Just rightclick it, and extract it into a new Folder.
In this new folder you'll see a .zip File. Extract this too by choosing "Extract here".
Now there is a File called SYSTEM.IMG. This is File you'll gonna need!
Now open the downloaded Zipfile "SGStoext4.zip" and doubleclick the .jar to start it.
You'll see a window that pops up. Drag and drop the SYSTEM.img into this window and it will extract the .img into a File called "system.ext4.img" which is built right in the same folder, the system.img is.
Now install the second Tool you've dowloaded called "Linux-Reader" and start it.
Once you startet it, choose "Mount Image" on the left hand side.
Let everything like it is and click Next.
Choose the system.ext4.img by doubleclicking it.
Now you should see the mounted Image called "Linux Ext Volume 1"
If you doubleclick it, there are all the original files from 4.1.2.
Create a new Folder on your PC and call it Systemfiles (or whatever).
Go back to Linuxreader, mark all files and folders (Strg+A) and rightclick them and hit "Save".
Now click "Next" and choose the Systemfile-Folder as the Outputfolder.
You're already done.
Copy the new created Systemfile-Folder to your Nexus7 (in the dowloadfolder threre, for instance)
Start the Updateprocess and wait till it stops with the currupted File error.
For example:
-----------------------------------------------------------------------------------------------------------------------------
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/BrowserProviderProxy.odex", "21a89
E:Error in /cache/094f6629314a.signed-nakasi-JOP40C-from-JZ054K.094f6629.zip
(Status 7)
Installation aborted.
-------------------------------------------------------------------------------------------------------------------------------
Write down the path (marked redcolor in the example) and search for it in the new Systemfile-folder.
The path in the new Systemfilefolder will be the same as it shows on the updatefailure.
Replace the corrupted File with the one of your fresh extracted ones using Rootexplorer on your Nexus 7.
Start the Updateprocess again.
If there is another corrupted File error, replace that File too.
Once you replaced all corrupted Files, you're done.
I replaced 4 Files before the update runned through properly.
I hope this helps and please let me know if it worked 4 u.
Alex
Thankyou Thankyou Thankyou. I followed your instructions with success.
I am now on 4.2 and have learnt some new stuff too
Manged to keep root with root protector..
Thanks for the in depth reply.
The other problem I was having was that I could not update again because it said I was already up to date. The way I found to overcome this was to go into apps and 'clear data' then 'force stop' the Google Services Framework
This worked like a charm.
Thanks mate.
nvertigo said:
Received the OTA update. Click reboot and install. TWRP pops up, nothing happens.
Log:
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/BrowserProviderProxy.odex", "21a89
E:Error in /cache/094f6629314a.signed-nakasi-JOP40C-from-JZ054K.094f6629.zip
(Status 7)
Installation aborted.
Anyone know what just happened? ::crying:
Click to expand...
Click to collapse
The solution by DroidBonzai is correct.
A shortcut for some people, particularly those that are rooted and sideloaded adobe flash and then the Android Browser, is that you may have renamed
system/app/BrowserProviderProxy.odex
to
system/app/BrowserProviderProxy.odex1
and similarly with
system/app/BrowserProviderProxy.apk
to
system/app/BrowserProviderProxy.apk1
as those would have caused a conflict with the sideloaded Browser.apk
Renaming those two file extensions will allow you update to 4.2 via recovery without installation error. It certainly worked for me!
http://forum.xda-developers.com/showthread.php?t=1945938 Sorry if the title of my guide was hard to search for.
DroidBonzai said:
Ok i'll try.
Sorry for my bad english
I'll do a step by step howto.
I hope this helps and please let me know if it worked 4 u.
Alex
Click to expand...
Click to collapse
Thanks Alex, you saved me from the painful upgrade! HUGE Thanks for this detailed steps! :good:
Tried it, still having problems
DroidBonzai said:
Ok i'll try.
Sorry for my bad english
I'll do a step by step howto.
First of all you'll need to download the 4.1.2 FW from Google.
Make sure, you choose the right one.
Take your Nexus 7, go into settings---> About Tablet and look for the Build-number.
Google OS
Then you will have to download this Tool (SGStoEXT4)
(This Tool will extract the Image into a mountable (readable) Image.)
Then you download THIS
(This Tool will mount your Image and you'll get access to the orig. Systemfiles you need.)
Ok lets begin:
Once you've dowloaded the Firmware 4.1.2 (Not 4.2 !!). It should be a .tgz. Just rightclick it, and extract it into a new Folder.
In this new folder you'll see a .zip File. Extract this too by choosing "Extract here".
Now there is a File called SYSTEM.IMG. This is File you'll gonna need!
Now open the downloaded Zipfile "SGStoext4.zip" and doubleclick the .jar to start it.
You'll see a window that pops up. Drag and drop the SYSTEM.img into this window and it will extract the .img into a File called "system.ext4.img" which is built right in the same folder, the system.img is.
Now install the second Tool you've dowloaded called "Linux-Reader" and start it.
Once you startet it, choose "Mount Image" on the left hand side.
Let everything like it is and click Next.
Choose the system.ext4.img by doubleclicking it.
Now you should see the mounted Image called "Linux Ext Volume 1"
If you doubleclick it, there are all the original files from 4.1.2.
Create a new Folder on your PC and call it Systemfiles (or whatever).
Go back to Linuxreader, mark all files and folders (Strg+A) and rightclick them and hit "Save".
Now click "Next" and choose the Systemfile-Folder as the Outputfolder.
You're already done.
Copy the new created Systemfile-Folder to your Nexus7 (in the dowloadfolder threre, for instance)
Start the Updateprocess and wait till it stops with the currupted File error.
For example:
-----------------------------------------------------------------------------------------------------------------------------
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/BrowserProviderProxy.odex", "21a89
E:Error in /cache/094f6629314a.signed-nakasi-JOP40C-from-JZ054K.094f6629.zip
(Status 7)
Installation aborted.
-------------------------------------------------------------------------------------------------------------------------------
Write down the path (marked redcolor in the example) and search for it in the new Systemfile-folder.
The path in the new Systemfilefolder will be the same as it shows on the updatefailure.
Replace the corrupted File with the one of your fresh extracted ones using Rootexplorer on your Nexus 7.
Start the Updateprocess again.
If there is another corrupted File error, replace that File too.
Once you replaced all corrupted Files, you're done.
I replaced 4 Files before the update runned through properly.
I hope this helps and please let me know if it worked 4 u.
Alex
Click to expand...
Click to collapse
I really have to appreciate the effort u have taken to help with this thing, and its a genius idea u have discovered to replace the faulty .apk
Anyhow, i did follow everything you said, like i replaced the GooglePinYinIME.apk which was having problem, but somehow the error persisted.
I am attaching an image along with this post. I have been trying to update my nexus 7 (4.1.2) to (4.2) for so long, getting problems in it.
I'd very much appreciate your help.
{
"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"
}
Tried it all, with NO LUCK
DroidBonzai said:
Ok i'll try.
Sorry for my bad english
I'll do a step by step howto.
First of all you'll need to download the 4.1.2 FW from Google.
Make sure, you choose the right one.
Take your Nexus 7, go into settings---> About Tablet and look for the Build-number.
Google OS
Then you will have to download this Tool (SGStoEXT4)
(This Tool will extract the Image into a mountable (readable) Image.)
Then you download THIS
(This Tool will mount your Image and you'll get access to the orig. Systemfiles you need.)
Ok lets begin:
Once you've dowloaded the Firmware 4.1.2 (Not 4.2 !!). It should be a .tgz. Just rightclick it, and extract it into a new Folder.
In this new folder you'll see a .zip File. Extract this too by choosing "Extract here".
Now there is a File called SYSTEM.IMG. This is File you'll gonna need!
Now open the downloaded Zipfile "SGStoext4.zip" and doubleclick the .jar to start it.
You'll see a window that pops up. Drag and drop the SYSTEM.img into this window and it will extract the .img into a File called "system.ext4.img" which is built right in the same folder, the system.img is.
Now install the second Tool you've dowloaded called "Linux-Reader" and start it.
Once you startet it, choose "Mount Image" on the left hand side.
Let everything like it is and click Next.
Choose the system.ext4.img by doubleclicking it.
Now you should see the mounted Image called "Linux Ext Volume 1"
If you doubleclick it, there are all the original files from 4.1.2.
Create a new Folder on your PC and call it Systemfiles (or whatever).
Go back to Linuxreader, mark all files and folders (Strg+A) and rightclick them and hit "Save".
Now click "Next" and choose the Systemfile-Folder as the Outputfolder.
You're already done.
Copy the new created Systemfile-Folder to your Nexus7 (in the dowloadfolder threre, for instance)
Start the Updateprocess and wait till it stops with the currupted File error.
For example:
-----------------------------------------------------------------------------------------------------------------------------
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/BrowserProviderProxy.odex", "21a89
E:Error in /cache/094f6629314a.signed-nakasi-JOP40C-from-JZ054K.094f6629.zip
(Status 7)
Installation aborted.
-------------------------------------------------------------------------------------------------------------------------------
Write down the path (marked redcolor in the example) and search for it in the new Systemfile-folder.
The path in the new Systemfilefolder will be the same as it shows on the updatefailure.
Replace the corrupted File with the one of your fresh extracted ones using Rootexplorer on your Nexus 7.
Start the Updateprocess again.
If there is another corrupted File error, replace that File too.
Once you replaced all corrupted Files, you're done.
I replaced 4 Files before the update runned through properly.
I hope this helps and please let me know if it worked 4 u.
Alex
Click to expand...
Click to collapse
Hey Alex,
I tried everything you said above, downloaded the 4.1.2 from google, then extracted it, then fount the file which was giving me problems in System.img (GooglePinYinIME.apk)
Then i replaced that file on the tablet using root explorer.
Even after doing all this, the error persisted, WITH THE SAME FILE..
I tried it 3-4 times, but no luck.
I also installed the GooglePinYinIME.apk in nexus 7 to see if it works, but it went in vain.
What would u suggest now?
Regards,
Ashutosh
That worked perfectly! Thanks so much!!