Hello everyone
I have an ST15 and lately I've been having the overheating problem known to many.
I did several tests and modifying files config.sh others, but all without success!
I installed various firmware, including:
S51SE: FW58 & FW61
ST15: 4.0.A.2.377 / 4.0.A.2.368 / 4.0.2.A.042 & 4.0.1.A.0.283.
I've been sharing with everyone using the firmware numeral 4.0.1.A.0.283 got the perfect operation of the unit!
Before, when the temperature was 38 degrees the unit vibrating like crazy, using 4.0.1.A.0.283 reached the peak of 44 degrees not passing this temperature, running 3D games and listening to music connected to the charger, something that would never do with other firmwares!
I wonder if it works for you ...
You can flash 4.0.1.A.0.283 using wotan server like me!
Sincerely GustavoRD78
{
"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"
}
nevermind.
it didn't works for me
desperately still looking for solution...
I remember that when the unit was purchased with FW0283 and had no problems after I upgraded to FW42 came the suffering!
I come from flash FW0283 FW42, a requirement for seje may not have the problem or something!
Anyone want to test a backup of my rom nandroid?
Gustavo RD78 said:
You can flash 4.0.1.A.0.283 using wotan server like me!
Click to expand...
Click to collapse
Hi Gustavo,
I've flashed this firmware 4.0.1.A.0.283 and i have exactly the same info as on your posted image, but unfortunately my phone still has this capacitive buttons problems.
Can you please tell me, your phone it's bootloader locked or unlocked? (http://unlockbootloader.sonyericsson.com/)
Your phone it was rooted when you have flahed it using the wotan server?
What are all the firmware version you have tried?
If you want, please share a rom backup of your phone.
Thanks!
deejay4angels said:
Hi Gustavo,
I've flashed this firmware 4.0.1.A.0.283 and i have exactly the same info as on your posted image, but unfortunately my phone still has this capacitive buttons problems.
Can you please tell me, your phone it's bootloader locked or unlocked? (http://unlockbootloader.sonyericsson.com/)
Your phone it was rooted when you have flahed it using the wotan server?
What are all the firmware version you have tried?
If you want, please share a rom backup of your phone.
Thanks!
Click to expand...
Click to collapse
My phone is rooted and unlocked the bootloader!
I tried all versions of FW, and the one that was FW0283 had no problems!
We must take into account the unit load to 100% before flashing, you may have something to do with it!
When you have time I will provide a backup to the test!
Gustavo RD78 said:
My phone is rooted and unlocked the bootloader!
I tried all versions of FW, and the one that was FW0283 had no problems!
We must take into account the unit load to 100% before flashing, you may have something to do with it!
When you have time I will provide a backup to the test!
Click to expand...
Click to collapse
Flashing the firmware FW0283 using the wotan server it works just fine for me, but after 32-34 Celsius degrees the problem starts again.
Please upload a nandroid backup of your rom (on on sharing server), so i can test it on my phone.
Thanks.
My FW-0283 for testing
http://www.4shared.com/zip/uTYyYrDn/ST15_Backup_FW-0283.html?
Gustavo RD78 said:
My FW-0283 for testing
http://www.4shared.com/zip/uTYyYrDn/ST15_Backup_FW-0283.html?
Click to expand...
Click to collapse
Thank you! I will test it now, and let you know if it works.
deejay4angels said:
Thank you! I will test it now, and let you know if it works.
Click to expand...
Click to collapse
When I installed I was using FW0283 FW42.
Perhaps seje also a requirement for smooth operation
I think you should flash before flashing the FW0283 nandroid (I suppose)
Edit: It can also be a problem in the kernel, someone with knowledge of kernel could investigate it?
Gustavo RD78 said:
My FW-0283 for testing
http://www.4shared.com/zip/uTYyYrDn/ST15_Backup_FW-0283.html?
Click to expand...
Click to collapse
I tought it will be easy, but how can I flash this files? I tried to get into recovery mode using rom manager, but it didn't work...
Can you please tell me how to flash this rom backup you have provided?
deejay4angels said:
I tought it will be easy, but how can I flash this files? I tried to get into recovery mode using rom manager, but it didn't work...
Can you please tell me how to flash this rom backup you have provided?
Click to expand...
Click to collapse
Follow these steps:
1. flash fw-0283 using wotanserver
2. root
3. installing recovery CWM
4. place the backup in: sd card / ClockworkMod / backups /
5. CWM restart on the backup and restore
restart
Gustavo RD78 said:
Follow these steps:
1. flash fw-0283 using wotanserver
2. root
3. installing recovery CWM
4. I gave up putting the sd card in / ClockworkMod / backups /
5. CWM restart on the backup and restore
restart
Click to expand...
Click to collapse
How to install CWM? If i try to do this using ROM Manager, the ST15i phone it is not listed...
deejay4angels said:
How to install CWM? If i try to do this using ROM Manager, the ST15i phone it is not listed...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1345741
Gustavo RD78 said:
Follow these steps:
1. flash fw-0283 using wotanserver
2. root
3. installing recovery CWM
4. place the backup in: sd card / ClockworkMod / backups /
5. CWM restart on the backup and restore
restart
Click to expand...
Click to collapse
There is an MD5 error: "md5sum: can't open android_secure.vfat.tar':No such file or directory"
Can you please upload also this file? Thanks.
deejay4angels said:
There is an MD5 error: "md5sum: can't open android_secure.vfat.tar':No such file or directory"
Can you please upload also this file? Thanks.
Click to expand...
Click to collapse
you have to unzip the zip file and place prescribed in the directory 2011-12-21.20.39.57
Gustavo RD78 said:
you have to unzip the zip file and place prescribed in the directory 2011-12-21.20.39.57
Click to expand...
Click to collapse
Yes, i know. But there is a missing file in the archive you have provided.
And when the CWM tries to restore the backup, it does an MD5 check which fails because the file android_secure.vfat.tar it is not founded.
On your archive are just 4 files, but it must be 5. I have done a backup of my rom. and i have this android_secure.vfat.tar file.
Thanks for your help.
deejay4angels said:
Yes, i know. But there is a missing file in the archive you have provided.
And when the CWM tries to restore the backup, it does an MD5 check which fails because the file android_secure.vfat.tar it is not founded.
On your archive are just 4 files, but it must be 5. I have done a backup of my rom. and i have this android_secure.vfat.tar file.
Thanks for your help.
Click to expand...
Click to collapse
stranger, he finds himself backed up in! I'll upload it and send you
I can not load this file, it is not recognized. :O
Aaaaaah
the place. tar from your backup and blink, but before you reboot make a full wipe / factory reset ;-)
Sent from my ST15i using Tapatalk
Gustavo RD78 said:
stranger, he finds himself backed up in! I'll upload it and send you
I can not load this file, it is not recognized. :O
the place. tar from your backup and blink, but before you reboot make a full wipe / factory reset ;-)
Click to expand...
Click to collapse
It doesn't work using the .tar file from my backup, because now CWM it tells me that i have an "MD5 mismatch" for this file.
Put that file inside of an archive or rename it (just an ordinary name, like abc) so it can be uploaded.
deejay4angels said:
It doesn't work using the .tar file from my backup, because now CWM it tells me that i have an "MD5 mismatch" for this file.
Put that file inside of an archive or rename it (just an ordinary name, like abc) so it can be uploaded.
Click to expand...
Click to collapse
Note: You can not rename the file 2011-12-21.20.39.57
http://www.4shared.com/file/Z6Idwyw2/android_securevfat.html?
see now!
Related
Hello XDA
I was wondering if there possibility for me to, flash (or use an app) an kernel to my stock rom? I am rooted, but I have stock recovery.
Also to be 100% sure: There is a risk of flashing a kernel right?
TheStigx said:
Hello XDA
I was wondering if there possibility for me to, flash (or use an app) an kernel to my stock rom? I am rooted, but I have stock recovery.
Also to be 100% sure: There is a risk of flashing a kernel right?
Click to expand...
Click to collapse
You can flash kernel with CWM app or odin mobile and after you'll have custom recovery.
There is a small risk that you will softbrick the phone.
This means that you can encounter some startup problems or just plain broken phone.
But dont worry, soft bricks are almost harmless and all problems have an easy solution nowadays.
Gent.XDA said:
There is a small risk that you will softbrick the phone.
This means that you can encounter some startup problems or just plain broken phone.
But dont worry, soft bricks are almost harmless and all problems have an easy solution nowadays.
Click to expand...
Click to collapse
Yeah, I thought that too. But I have read those threads about how to recovery it from soft brick, and I think it isn't a problem.
078gregory said:
You can flash kernel with CWM app or odin mobile and after you'll have custom recovery.
Click to expand...
Click to collapse
Oh, What CWM app? You mean rom manager? That can only help me with roms
TheStigx said:
Yeah, I thought that too. But I have read those threads about how to recovery it from soft brick, and I think it isn't a problem.
Oh, What CWM app? You mean rom manager? That can only help me with roms
Click to expand...
Click to collapse
Do not use rom manager .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
from the guide in stickies .
Clockworkmod is a 'custom recovery' made by xda member koush. Every phone had a recovery partition designed so that if the user messes up a ROM installation, they can recover their phone. CWM is a modified recovery installed into the recovery partition that allows advanced control over ROM recovery, installation and much more.
Features of CWM include:
- NANDroid Backup, This allows you to completely back up your existing ROM with all its files, data and apps
- Restore Backup, Restores a previous backup (obviously...)
- ROM installation, Allows you to install a ROM contained inside a flashable .zip file
- Wipe data/Factory reset, completely erases all of your data contacts, apps etc, leaving your phone 'as new'
Amongst others...
How to install CWM
If you have already rooted your phone using the CF-root Kernel, then you already have CWM! If not, then just install the kernel linked to above in the 'how to root your phone' section
How to make a NANDroid backup using CWMBackups are important because they allow you to restore your ROM incase flashing goes wrong, or you phone starts playing up and displaying wierd bugs.
To make a backup, you need to boot into CWM recovery (done through the 'cwm' app installed onto your phone when you flash the cf-root kernel). Then, you need to navigate down to 'backup/restore' using the volume keys, and select it using the home key. From here, just click 'backup' and you are all set! Leave your phone make the backup (its takes some time) and then just reboot when it tells you its finished. To restore your backup, do the same but instead of clicking backup, click 'restore' instead. Choose which backup you would like to restore and leave the phone to do its magic. Done.
How to install a ROM using CWMInstalling a ROM using CWM is a lot less hassle then installing via Odin. The ROM developer will specify which method of installing their ROM you can use, but it is usually done by a CWM flashable .zip.
To flash:
1. Boot into CWM as described above
2. Navigate to 'install zip from sd card'
3. Select it, and then navigate to 'install zip from sdcard' again!
4. Select the ROM you downloaded from your sd card
5. Navigate down to yes
6. Let CWM install you new ROM!
jje
TheStigx said:
Oh, What CWM app? You mean rom manager? That can only help me with roms
Click to expand...
Click to collapse
Go to Chainfires thread in Original android development section and download the cf root file that match to your current rom.
Flash it with odin, You will have custom CWM
That would be a good idea!
{
"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"
}
JJEgan said:
Do not use rom manager .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
from the guide in stickies .
Clockworkmod is a 'custom recovery' made by xda member koush. Every phone had a recovery partition designed so that if the user messes up a ROM installation, they can recover their phone. CWM is a modified recovery installed into the recovery partition that allows advanced control over ROM recovery, installation and much more.
Features of CWM include:
- NANDroid Backup, This allows you to completely back up your existing ROM with all its files, data and apps
- Restore Backup, Restores a previous backup (obviously...)
- ROM installation, Allows you to install a ROM contained inside a flashable .zip file
- Wipe data/Factory reset, completely erases all of your data contacts, apps etc, leaving your phone 'as new'
Amongst others...
How to install CWM
If you have already rooted your phone using the CF-root Kernel, then you already have CWM! If not, then just install the kernel linked to above in the 'how to root your phone' section
How to make a NANDroid backup using CWMBackups are important because they allow you to restore your ROM incase flashing goes wrong, or you phone starts playing up and displaying wierd bugs.
To make a backup, you need to boot into CWM recovery (done through the 'cwm' app installed onto your phone when you flash the cf-root kernel). Then, you need to navigate down to 'backup/restore' using the volume keys, and select it using the home key. From here, just click 'backup' and you are all set! Leave your phone make the backup (its takes some time) and then just reboot when it tells you its finished. To restore your backup, do the same but instead of clicking backup, click 'restore' instead. Choose which backup you would like to restore and leave the phone to do its magic. Done.
How to install a ROM using CWMInstalling a ROM using CWM is a lot less hassle then installing via Odin. The ROM developer will specify which method of installing their ROM you can use, but it is usually done by a CWM flashable .zip.
To flash:
1. Boot into CWM as described above
2. Navigate to 'install zip from sd card'
3. Select it, and then navigate to 'install zip from sdcard' again!
4. Select the ROM you downloaded from your sd card
5. Navigate down to yes
6. Let CWM install you new ROM!
jje
Click to expand...
Click to collapse
kachrukamble said:
Go to Chainfires thread in Original android development section and download the cf root file that match to your current rom.
Flash it with odin, You will have custom CWM
Click to expand...
Click to collapse
But I wish to keep my stock recovery. Can't I use this recovery : http://forum.xda-developers.com/showthread.php?t=1501719
?
I was running the new Jellybean ROM just fine but decided to revert back to the AOKP ICS ROM. I did a backup of my JB rom in CWM and then did a restore of the backup from the AOKP ROM. But I forget to do a factory wipe. The ROM booted up fine the first time and then after a reboot it was just endlessly running the boot animation.
I could only boot into download mode so I tried to use PC Odin to flash a ROM I had but the program gets stuck at factoryfs.img. Please can anyone offer assitance?!
If you're to that point, flash back to stock first before you do anything else using creepyncrawlys guide in the dev section.
BROKKANIC said:
If you're to that point, flash back to stock first before you do anything else using creepyncrawlys guide in the dev section.
Click to expand...
Click to collapse
Sadly... I have tried this and it still gets stuck.
Using the downloads here: http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
{
"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"
}
Have you tried this:?
http://forum.xda-developers.com/showthread.php?t=1286432
benjamingdelacruz said:
Have you tried this:?
http://forum.xda-developers.com/showthread.php?t=1286432
Click to expand...
Click to collapse
I have. This is what I did first. It gets to about 30% and gets stuck.
AngelsNecropolis said:
I was running the new Jellybean ROM just fine but decided to revert back to the AOKP ICS ROM. I did a backup of my JB rom in CWM and then did a restore of the backup from the AOKP ROM. But I forget to do a factory wipe. The ROM booted up fine the first time and then after a reboot it was just endlessly running the boot animation.
I could only boot into download mode so I tried to use PC Odin to flash a ROM I had but the program gets stuck at factoryfs.img. Please can anyone offer assitance?!
Click to expand...
Click to collapse
You don't have to do a wipe when restoring a nandroid backup on our phones, since it overwrites the entire data partition anyway. I'm wondering if ClockworkMod versions could be at the root of this. You didn't say which JB you were using, and I am not up on AOKP, but did the JB rom have CWM 6.0.1.1? and AOKP have the 5.x version? I think these are supposed to be backward compatible, but I'm wondering if restoring a 5.x backup with the 6.0.1.1 version could be at fault here. Just clutching at straws for a reason.
As far as recovering, go to the Download Repository, and first try flashing the complete firmware package with bootloaders. If that doesn't work, then try flashing the critical parts individually, i.e. secondary bootloader and param.lfs. If that doesn't work, there is a pit file there also, so you can flash the stock package with repartition. I assume you understand the risks.
I was using the SuperNexus JB rom. They did have different cwm versions but not sure which they were. Luckily I found an md5 file that would load 100% using pc Odin. Any tar file I tried to use first wouldn't load. Then I was successfully able to use the gingerbread stock with root tar listed in the unbrick section and then install a kernel with cwm to do the restore again. So I'm back to the AOKP. Only took 5 hours to fix this time. Ugh.
Sent from my SGH-I777 using Tapatalk 2
AngelsNecropolis said:
I was using the SuperNexus JB rom. They did have different cwm versions but not sure which they were. Luckily I found an md5 file that would load 100% using pc Odin. Any tar file I tried to use first wouldn't Loa. Then I was successfully able to use the gingerbread stock with root tar listed in the unbrick section and then install a kernel with cwm to do the restore again. So I'm back to the AOKP. Only took 5 hours to fix this time. Ugh.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Mind posting that file? It might come in handy.
The file is 618mb. I'll try to find the site where I downloaded it from.
Sent from my Galaxy S II running AOKP Jellybean
AngelsNecropolis said:
The file is 618mb. I'll try to find the site where I downloaded it from.
Sent from my Galaxy S II running AOKP Jellybean
Click to expand...
Click to collapse
I found the file on this site: http://www.droidreader.com/2012/05/how-to-un-brick-or-fix-soft-bricked.html
It's the Recovery Package for ICS that I used: http://hotfile.com/dl/146748985/809318f/I9100XXLPH.zip.html
The zip contains an md5 file which PC Odin was successfully able to load entirely. I suppose the md5 fixed something that was screwed up which prevented the tar files from completely loading.
Then I was able to successfully flash the kernel + rooted UCKH7 system package found here. Next I flashed a gingerbread Siyah kernal found here in order to gain access to CWM and restore my previous backup.
AngelsNecropolis said:
I found the file on this site: http://www.droidreader.com/2012/05/how-to-un-brick-or-fix-soft-bricked.html
It's the Recovery Package for ICS that I used: http://hotfile.com/dl/146748985/809318f/I9100XXLPH.zip.html
The zip contains an md5 file which PC Odin was successfully able to load entirely.
Click to expand...
Click to collapse
thats all i9100 stuff. Please dont confuse the masses posting that crap here.
MotoMudder77 said:
thats all i9100 stuff. Please dont confuse the masses posting that crap here.
Click to expand...
Click to collapse
Well that crap helped unsoft brick my phone. I only had to use the md5 file in order to get the correct TAR files to work.
AngelsNecropolis said:
I found the file on this site: http://www.droidreader.com/2012/05/how-to-un-brick-or-fix-soft-bricked.html
It's the Recovery Package for ICS that I used: http://hotfile.com/dl/146748985/809318f/I9100XXLPH.zip.html
The zip contains an md5 file which PC Odin was successfully able to load entirely. I suppose the md5 fixed something that was screwed up which prevented the tar files from completely loading.
Click to expand...
Click to collapse
Which .tar.md5 file did you use? And which proceedures in the tutorial did you follow?
Then I was able to successfully flash the kernel + rooted UCKH7 system package found here. Next I flashed a gingerbread Siyah kernal found here in order to gain access to CWM and restore my previous backup.
Click to expand...
Click to collapse
I'm surprised you were able to enter download mode to complete this step, since the I9100 package you used previously contained bootloaders. The secondary bootloader for the I9100 would change the button configuration for entering download mode and recovery mode.
creepyncrawly said:
Which .tar.md5 file did you use? And which proceedures in the tutorial did you follow?
I'm surprised you were able to enter download mode to complete this step, since the I9100 package you used previously contained bootloaders. The secondary bootloader for the I9100 would change the button configuration for entering download mode and recovery mode.
Click to expand...
Click to collapse
I tried using files:
I777UCKH7 OCD With Root.exe
UCKH7_stock_root.tar
uckk6_stock_rooted.tar
ATTGalaxyS2Unroot_SGH-i777.tar
I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5
None of the tar files would complete. The md5 was located in the zip that I downloaded from the previously mentioned site. The file did load a ROM whose hard button configuration didn't match my phone model. Only the menu and home buttons worked and home was actually back. But I didn't have to do anything in the ROM. Download mode was still VOL Down + Power button.
After loading the md5 file I was able to use the exe but when the ROM loaded I wasn't able to get past the setup wizard. I would click on the android in the middle and either it wouldn't respond or different processes kept force closing. I remember one was a google framework process and there were like 2 others that popped up.
Everytime one of the other files failed I had to redo the md5 because the tars would get stuck again. So after several attempts I finally was able to use the UCKH7_stock_root.tar file to move forward with restoring my soft bricked phone.
Maybe someone can list the md5 file of the UCKH7_stock_root.tar incase PC Odin gets stuck like this for someone else? Though I'm no expert so I can't be sure if the tar vs md5 was what fixed the issue. I just know that file helped even if it wasn't the right one for my phone and, to my knowledge, caused no other issues once I used the correct tar files. I'm happily running the new AOKP JB ROM with no issues thus far.
I renamed the framework-res.apk file in my XPERIA P and my phone restarted and stuck in xperia logo..it again restart and stuck in xperia logo until the battry totally finished...please someone help me out.i have not made any backup of my device
thanks in advance
To switch of phone during bootloop
Press volume up plus power key for few seconds
For ur current problm
Now u need to flash original ftf via flashtool
Not necessary mate.. Just flash a zip containing framework-res.. Ill make it now.. It would be easier if you had specified the renamed file but nevermind. Ill post it in a minute
Edit : Uploaded here Flash with CWM and you can use the rom fine
Min3r said:
Not necessary mate.. Just flash a zip containing framework-res.. Ill make it now.. It would be easier if you had specified the renamed file but nevermind. Ill post in a minute
Click to expand...
Click to collapse
I am new here so please can u explain the steps for this process
Min3r said:
Not necessary mate.. Just flash a zip containing framework-res.. Ill make it now.. It would be easier if you had specified the renamed file but nevermind. Ill post it in a minute
Edit : Uploaded here Flash with CWM and you can use the rom fine
Click to expand...
Click to collapse
He doesn't has cwm installed
Or does he??
drsanket_xperia_u said:
He doesn't has cwm installed
Or does he??
Click to expand...
Click to collapse
no i dont have cwm installed
Looks like you'll have to install with stock FTF mate You cant install CWM without rooting and all
FTF for Xperia P Download that, then flash it with Flashtool If you have any posts, reply here
Cheers
Min3r said:
Looks like you'll have to install with stock FTF mate You cant install CWM without rooting and all
Cheers
Click to expand...
Click to collapse
my phone is rooted and bootloader unlocked also
Then just flash a custom kernel with CWM 5.5 recovery, and then flash
Thanks u both for ur response.i flasheed with stock ftf
Sent from my LT22i using xda app-developers app
Moral:NEVER EVER rename or replace framework-res when the phone is running do that only in recovery
Hit the thanks button it has more value
megablakbar said:
Moral:NEVER EVER rename or replace framework-res when the phone is running do that only in recovery
Hit the thanks button it has more value
Click to expand...
Click to collapse
hey i have the same problem but on my asus memo pad hd 7 where i renamed the framework-res.apk (while the tablet was running!) and im stuck in a boot loop. I did framaroot before so its supposed to be rooted. my computer cant see the device though any more. MTP drivers failed to install (
what can i do now?? is it perma-bricked or wut? please help!
i entered recovery mode but theres no option to "apply update from external storage" or wut not just:
reboot system now
wipe data/factory reset
wipe cache partition
backup user data
restore user data
do i have to have the the rom zip file on the sd card for this option to show up? thing is i cant find the stock firmware and asus doesnt provide it on their support page for this device like they do for other tablets i dont know why!?
i still have both original and modded framework-res.apk on the tablet just the original is renamed to framework-tres.apk
all i need to do is rename it back and delete the modded file
HELP PLEASE!! THANK YOU!!
@nycionx
You realize its a forum for Xperia P, U, Sola, and GO?
Can't you flash /system or the whole firmware if not that?
I don't know how to fix you pad but I think I know how to do it right next time.
if you want a backyp then create a second hard link to framework-res.apk.
Do not rename framework-res.apk, instead rename the moded file to framework-res.apk after you copied it and changed it's settings.
Rename operation is supposed t be atomic, meaning it either suceed and have linked to the new file, or fail and leave the link to the old file, so even if the device reboots immediately after the rename, it still has framework-res.apk after reboot. either the old one or the new one.
ChikeD said:
@nycionx
You realize its a forum for Xperia P, U, Sola, and GO?
Can't you flash /system or the whole firmware if not that?
I don't know how to fix you pad but I think I know how to do it right next time.
if you want a backyp then create a second hard link to framework-res.apk.
Do not rename framework-res.apk, instead rename the moded file to framework-res.apk after you copied it and changed it's settings.
Rename operation is supposed t be atomic, meaning it either suceed and have linked to the new file, or fail and leave the link to the old file, so even if the device reboots immediately after the rename, it still has framework-res.apk after reboot. either the old one or the new one.
Click to expand...
Click to collapse
yes sorry for the wrong forum, i just couldnt find the same problem in the asus memo pad forum
on http://www.asus.com/Tablets_Mobile/ASUS_MeMO_Pad_HD_7/#support_Download
there is no firmware download, only some source code thing wutever that is??
i hope its not bricked and totally useless now, like i dont want to have to throw in garbage i just got it yesterday (
i really hope someone has a solution to my problem. its a shame i dont have bootloader unlocked and CWM installed, but even then i still dont have the stock rom so....
nycionx said:
yes sorry for the wrong forum, i just couldnt find the same problem in the asus memo pad forum
on http://www.asus.com/Tablets_Mobile/ASUS_MeMO_Pad_HD_7/#support_Download
there is no firmware download, only some source code thing wutever that is??
i hope its not bricked and totally useless now, like i dont want to have to throw in garbage i just got it yesterday (
i really hope someone has a solution to my problem. its a shame i dont have bootloader unlocked and CWM installed, but even then i still dont have the stock rom so....
Click to expand...
Click to collapse
1. Don't panic
2. download the stock image
3. install stock rom then install any rom you want
how about you try with aroma file manager. search yourself please because I'm never attaching the zip file again. in aroma-fm, you have to go /system/framework and there you see your RENAMED FRAMEWORK-RES.apk. Then rename it back to framework-res.apk and reboot.
P.S: do that in recovery mode, aroma file mnager works well in any recovery. just install zip from sdcard and choose your aroma-fm zip and it will pop up.
War never finds answer. It just the stronger ones define the victory.
the problem is i dont have the "install from sd card" feature listed in the recovery mode so how can i possibly install aroma-fm? i downloaded it and placed it in the root of my sd card and what now? all i have is this as i said:
reboot system now
wipe data/factory reset
wipe cache partition
backup user data
restore user data (this looks only for a .backup file no zip)
does this mean a locked bootloader or something? i didnt install CWM before hand, is it too late now? what can i do? i heard about some download mode but i dont know how i would get in it. i only have volume +/- and power buttons btw.
also, i cant find the stock rom since asus for some reason isnt providing it on their site. is there any other way to get it? like what if i bought another pad and is it possible to extract the rom from it and then i can just return the new pad. ? just a guess
@nycionx
Contact ASUS support, maybe they will help.
ChikeD said:
@nycionx
Contact ASUS support, maybe they will help.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ST25i using Tapatalk 2
Little Zed said:
http://img.tapatalk.com/d/13/10/01/qa2eta4u.jpg
Sent from my ST25i using Tapatalk 2
Click to expand...
Click to collapse
Spam your own threads not others
I'm terribly sorry is this is the wrong place to post this, but I'm new to the whole 'forums' in general thing.
A while ago, a friend came to me and said his android was growing buggy, so I told him how to factory reset it and such. Then I rooted it for him to clear it of any stock apps he didn't want. Now I've currently got the device next to me, and I've tried installing a custom rom onto it for him, to help make his device a bit faster and less buggy. I tried installing PAC-ROM ( http://forum.xda-developers.com/showthread.php?t=2235446 ), but I got the same error in CWM that I got when I tried to flash my HTC Glacier, which was remedied by updating to the latest CWM. I tried updating CWM from its current 5.0.2.7 to something 6.0+, but the 5.0 version sticks, which might be due to the fact that I used ODIN to flash the CWM according to a different XDA forum, which I cannot locate right now. Now, after attempting to flash PAC-ROM, and getting said errors, I seem to be unable to remount anything from CWM (/system, /data, etc), so the device cannot boot.
Is the device bricked for good, or is there something that can help me? I'm not totally inexperienced with flashing/customizing android, but I'm not great at it either.
Thanks for the help in advanced.
uhhh, what exactly did you flash to upgrade CWM? Did you use something for another device? Because you arent supposed to do that.
I would reboot into download mode, and then flash the stock firmware. Then you can flash a either RJ's kernel (for INTL) or Entropy's kernel (US) depending on what device you have. To flash PAC, you have to first flash a cm9 rom, reboot into recovery, and then flash PAC
iurnait said:
uhhh, what exactly did you flash to upgrade CWM? Did you use something for another device? Because you arent supposed to do that.
I would reboot into download mode, and then flash the stock firmware. Then you can flash a either RJ's kernel (for INTL) or Entropy's kernel (US) depending on what device you have. To flash PAC, you have to first flash a cm9 rom, reboot into recovery, and then flash PAC
Click to expand...
Click to collapse
I've reflashed stock through ODIN, and this showed up.
{
"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"
}
Do a wipe data and see if your errors are resolved
iurnait said:
Do a wipe data and see if your errors are resolved
Click to expand...
Click to collapse
I did, it gave me the 'error can't mount /system, /data, etcetc' thing, and then rebooted, and now it's stuck in CWM.
you probably need to find the pit file and flash that via odin. just keep holding the power and volume down keys until you are in recovery. then put the pit file in odin along with the stock firmware and flash.
Pits:
http://forum.xda-developers.com/showthread.php?t=1389873
iurnait said:
you probably need to find the pit file and flash that via odin. just keep holding the power and volume down keys until you are in recovery. then put the pit file in odin along with the stock firmware and flash.
Pits:
http://forum.xda-developers.com/showthread.php?t=1389873
Click to expand...
Click to collapse
Found the stock here http://forum.xda-developers.com/showthread.php?t=2192488 , but I get errors when trying to flash everything.
TacoSeeker said:
Found the stock here http://forum.xda-developers.com/showthread.php?t=2192488 , but I get errors when trying to flash everything.
Click to expand...
Click to collapse
After trying a few more times, I end up with the same screen as I posted before, the android recovery screen.
try downloading and extracting this: http://forum.xda-developers.com/attachment.php?attachmentid=812772&d=1323614740
this contains odin version 1.81, which has always worked for me.
TacoSeeker said:
Found the stock here http://forum.xda-developers.com/showthread.php?t=2192488 , but I get errors when trying to flash everything.
Click to expand...
Click to collapse
That PIT file is invalid. It has never worked and never will. If you need the pit file then get it from Adam Outler's post that has all the PIT files for the all players 5.0.
I didn't know what I was doing when I made it. I just dumped the partition that has the pit file on it and that is what that is. NO ONE SHOULD EVER USE ueki8.pit FROM YP-G70_UEKI8_MIN !!!
Try using Heimdall.
TheKryptonite said:
Try using Heimdall.
Click to expand...
Click to collapse
Heimdall says it can't connect to the devices, libusb error -12
iurnait said:
try downloading and extracting this: http://forum.xda-developers.com/attachment.php?attachmentid=812772&d=1323614740
this contains odin version 1.81, which has always worked for me.
Click to expand...
Click to collapse
Even after flashing using that, it still returns me to either the download screen, or the recovery screen.
Now the devices is stuck in a state where it won't exit download mode.
TacoSeeker said:
Heimdall says it can't connect to the devices, libusb error -12
Click to expand...
Click to collapse
Are you drivers installed? Did you install the drivers on Zadig?
TheKryptonite said:
Are you drivers installed? Did you install the drivers on Zadig?
Click to expand...
Click to collapse
Yes, I always stay updated on drivers on my PC.
TacoSeeker said:
Yes, I always stay updated on drivers on my PC.
Click to expand...
Click to collapse
Try uninstalling the Samsung drivers and Kies. Try to find the Samsung device and replacing/installing all drivers.
TheKryptonite said:
Try uninstalling the Samsung drivers and Kies. Try to find the Samsung device and replacing/installing all drivers.
Click to expand...
Click to collapse
Same result as before.
Try the instructions here. http://forum.xda-developers.com/showthread.php?p=44192192
Meticulus said:
Try the instructions here. http://forum.xda-developers.com/showthread.php?p=44192192
Click to expand...
Click to collapse
After all that, I still get the screen showed in my previous comment,
Most of the people on xda getting error while flashing new update on YU yureka.
so i have created this thread to solve there's problems :highfive:
you just have to follow some steps.
1.you should be on stock recovery.
if you do not have stock recovery then here is LINK
************************************************************
2. now you need big data pack you have to download whole updated stock rom which is approx 643.767 MB
here is LINK.
3. now put this in internal storege(not in any folder or ext_sd card)
4. go to recovery and apply update. and choose this zip file and flash it :good:
and now very important step. Hit thanks button :laugh:
{
"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"
}
Do i need to be on stock Cm12 ROM to do this?? I am currently running Pac Rom.
Thanks!
sunny765 said:
Do i need to be on stock Cm12 ROM to do this?? I am currently running Pac Rom.
Thanks!
Click to expand...
Click to collapse
yes bro if you want update then you should be on stock if you have backup ur stock rom then just restore it.
koi yaar ye recovery ko flashable zip mai kar k dona plss. direct cwm se stock recovery flash ho esa
Rakesh251 said:
koi yaar ye recovery ko flashable zip mai kar k dona plss. direct cwm se stock recovery flash ho esa
Click to expand...
Click to collapse
have tried flishify app?
LINK
flash using this.
i have not tried yes but search.
Why is it 643 mb the update is just 130mb
thearjunraju said:
Why is it 643 mb the update is just 130mb
Click to expand...
Click to collapse
'cos it's the "whole updated stock rom", i.e., stock rom + the latest update rolled into one convenient easy-to-use package. read the op.
i was reading stock kernel was needed
i know kernel is usually in the full build
so
1. do we need the stock kernel?
2. Will TA backup work?
3. do we need to clear cache and data?
4. Will the existing 3rd party kernel and recoveries work after the update?
As far as I know from my limited flashing experience, the custom kernel will get overwritten by those present in the ROM being flashed.
Sent from my A0001 using XDA Free mobile app
oemaritradey said:
i know kernel is usually in the full build
so
1. do we need the stock kernel?
2. Will TA backup work?
3. do we need to clear cache and data?
4. Will the existing 3rd party kernel and recoveries work after the update?
Click to expand...
Click to collapse
1. you should be on stock kernel.
2.after upgrading your mobile you should take backup again. becoz why you want to revert back to older version ?
3.no need to clear cache and data.
4. yes you can flash any kernel and recovery . i had updated it and i am on TWRP.
*************************************************************************************************************************
feeroz123 said:
As far as I know from my limited flashing experience, the custom kernel will get overwritten by those present in the ROM being flashed.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
yes you are right but still there is thread on yu forum for it and they said that you should be on stock kernel by the way you can flash it on your current kernel if you see any error then you can flash stock kernel and flash this update
ashish_zarekar said:
1. you should be on stock kernel.
2.after upgrading your mobile you should take backup again. becoz why you want to revert back to older version ?
3.no need to clear cache and data.
4. yes you can flash any kernel and recovery . i had updated it and i am on TWRP.
*************************************************************************************************************************
yes you are right but still there is thread on yu forum for it and they said that you should be on stock kernel by the way you can flash it on your current kernel if you see any error then you can flash stock kernel and flash this update
Click to expand...
Click to collapse
Please flash any custom kernel to see if it works or not :3
oemaritradey said:
Please flash any custom kernel to see if it works or not :3
Click to expand...
Click to collapse
I am on thunderzap kernel
enjoy happy flashing .
best of luck
ashish_zarekar said:
1. you should be on stock kernel.
2.after upgrading your mobile you should take backup again. becoz why you want to revert back to older version ?
3.no need to clear cache and data.
4. yes you can flash any kernel and recovery . i had updated it and i am on TWRP.
*************************************************************************************************************************
yes you are right but still there is thread on yu forum for it and they said that you should be on stock kernel by the way you can flash it on your current kernel if you see any error then you can flash stock kernel and flash this update
Click to expand...
Click to collapse
LOL i tried falshing stock kernel with flashify both time i didnt get wifi signal(MAC UNKNOWN) xD Am not switching over to new update anytime soon....
Flashed this full ROM. Successful !! :highfive:
But I lost Root access and the stock recovery.
I am trying to flash it in fastboot mode, but its stuck at this message:
target reported max download size of 268435456 bytes
sending 'recovery' (8394 KB)...
Without stock recovery, I can't flash the Root.zip file to get root access.
feeroz123 said:
Flashed this full ROM. Successful !! :highfive:
But I lost Root access and the stock recovery.
I am trying to flash it in fastboot mode, but its stuck at this message:
target reported max download size of 268435456 bytes
sending 'recovery' (8394 KB)...
Without stock recovery, I can't flash the Root.zip file to get root access.
Click to expand...
Click to collapse
yes i know when you flash this rom you will lose your root.
and why are you flashing it in fastboot mode ?
this rom is flashable in stock recovery only dont do that.
and what were you doing while you got that error message ?
ashish_zarekar said:
yes i know when you flash this rom you will lose your root.
and why are you flashing it in fastboot mode ?
this rom is flashable in stock recovery only dont do that.
and what were you doing while you got that error message ?
Click to expand...
Click to collapse
I meant, I lost the stock recovery as well. SO I was trying to flash the stock recovery image file in fastboot mode as usual. But it gives me error as I mentioned earlier. My phone is connected to PC while I try to flash the recovery image file. I suspected the drivers got erased, but thats not the case.
Only when I install stock recovery, the Root.zip file can be flashed using it ( to root the phone again). Because flashing the zip files from new Cyanogen Recovery is not at all working. Some R/W or backmap/bitmap kind of issue comes when I try to flash using the updated recovery.
feeroz123 said:
I meant, I lost the stock recovery as well. SO I was trying to flash the stock recovery image file in fastboot mode as usual. But it gives me error as I mentioned earlier. My phone is connected to PC while I try to flash the recovery image file. I suspected the drivers got erased, but thats not the case.
Only when I install stock recovery, the Root.zip file can be flashed using it ( to root the phone again). Because flashing the zip files from new Cyanogen Recovery is not at all working. Some R/W or backmap/bitmap kind of issue comes when I try to flash using the updated recovery.
Click to expand...
Click to collapse
what? you lost your stock recovery ? how is it possible ? it means you dont have any recovery ?
have not face yet.
and how did you flash root.zip file using stock recovey
stock recovery does not have option to flash. it always have update option.
you can flash root.zip file using custom recovery only.
Thankyou for this post... can you please advice to update this ota
I am in stock rom with twrp recovery + sandy kernel
what are the steps to update this ota... can you tell step by step
thank you in advance
m_rajaganesh said:
Thankyou for this post... can you please advice to update this ota
I am in stock rom with twrp recovery + sandy kernel
what are the steps to update this ota... can you tell step by step
thank you in advance
Click to expand...
Click to collapse
DO NOT SPAM.
read carefully i already told the steps in my first POST
download stock kernel and flash it.
download stock recovery and flash it.
now download whole rom from my post and flash it.
ashish_zarekar said:
what? you lost your stock recovery ? how is it possible ? it means you dont have any recovery ?
have not face yet.
and how did you flash root.zip file using stock recovey
stock recovery does not have option to flash. it always have update option.
you can flash root.zip file using custom recovery only.
Click to expand...
Click to collapse
I am sorry, I put it in wrong terms.
The CWM recovery (having basic look with text in blue that can be opted only using hardware buttons and not touch) is not shown for me now. The Cyanogen Recovery it shows me now looks new (with Apply Update option that can be opted by touch as well). THis new recovery fails whenever I try to flash any zip with it. The error being R/W error or something.
With the old recovery (CWM recovery) I could/did flash the Root.zip. After flashing this full ROM (having the patch), the old recovery is lost. It shows only the new recovery. And with it the Root.zip can not be flashed as it fails, as I mentioned earlier.
May be I will get you screenshots of the new Cyanogen recovery to explain what I mean.
Old CWM Recovery:
New Cyanogen Recovery: