hi
please help me
i have cyanogen 7.0.3, but it can't find my wifi home network and also it didn't solve the problem of app2sd
i can't partition my sd, always get errors
so i want to go back to the original froyo rom of desire, i can't, it says waiting for bootloader and the error 171, usb connection error
what is the solution please????
thanks in advance
Extract the PB99IMG.zip from the RUU, copy it to your SD card, boot into HBOOT and it'll ask you to install it. Follow this guide I did a while back if you don't know how to do it:
http://forum.xda-developers.com/showpost.php?p=10509780&postcount=102
thank you very much
i did it
take this :
http://forum.xda-developers.com/showthread.php?p=11392713
Hi,
I need serious help.
I tried to install Vanilla RootBox rom on my Ace 2 NFC (i8160P) CZ.
So i did wipe data, cache, dalvik.
Then i add my Tee folder into rom (tee hack for P version) and i deleted the device model verification from updater-script because it is for non P version.
But when i try to flash the rom via cwm temporary, i stuck at this errors:
cant format unknown volume: /external_sd
cant partition unsafe device: /dev/block/mmcblk0p8
Click to expand...
Click to collapse
But my sdcard is working good (adata microsdhc class10 32GB)
Any solutions?
EDIT: I am using this http://forum.xda-developers.com/showthread.php?t=2389395 patch but not Version 2, but V1 flashed from CWM. This could be the problem. Or not?
EDIT2: I am doing downgrade with repartition to GB an then flash JB... Nicely Done.. but when i try to flash other ROM, still gets the error. OMFG.
EDIT3: So it looks like i need to repartition or do something with mmcblk0p8 partition but what? OMFG, help me please!!!
...
it seem great problem ask from rom creater i thinck they can help you
majid92 said:
it seem great problem ask from rom creater i thinck they can help you
Click to expand...
Click to collapse
Supposedly the mmcblk0p8p partition is the internal storage, named UMS --> Usb Mass Storage
So best check if that reads properly in android (file explorer) and/or when u connect it to your computer.
Seeing as your external SD works good and it complains about that too tho, I don't expect your internal SD to be faulty either.
As for the memory fix you flashed, when u reverted back to GB and then re upgraded to JB, was there a param.lfs.md5 file present in the package (assuming u used odin, u should be able to verify this by opening the tar.md5 in 7zip or winrar)
If yes, then any harm caused by the memory fix will have been undone and that isn't the cause either.
Carpe-Dimi said:
Supposedly the mmcblk0p8p partition is the internal storage, named UMS --> Usb Mass Storage
So best check if that reads properly in android (file explorer) and/or when u connect it to your computer.
Seeing as your external SD works good and it complains about that too tho, I don't expect your internal SD to be faulty either.
As for the memory fix you flashed, when u reverted back to GB and then re upgraded to JB, was there a param.lfs.md5 file present in the package (assuming u used odin, u should be able to verify this by opening the tar.md5 in 7zip or winrar)
If yes, then any harm caused by the memory fix will have been undone and that isn't the cause either.
Click to expand...
Click to collapse
So, yes it is the USB storage, and its working well too. param.lfs.md5 was there. I dont know what to do now.
you are using the temporary CWM tho right? which needs to be flashed via stock recovery? and stock recovery doesn't complain about your mmcblk0p8 partition?
if this is the case, then you can root the stock rom via stock recovery --> http://forum.xda-developers.com/showthread.php?t=2139263
download this kernel for stock rom --> http://forum.xda-developers.com/showthread.php?t=2171054 -extract the zip and place the kernel.bin.md5 file on the root of your internal sdcard
install any terminal emulator, open it and and enter/type su -click accept when prompted for superuser permissions
with that all done enter "dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15" make no typo's on that one, it's lethal.
If done right, it will replace stock kernel with D kernel. which will contain the same version of cwm as in the temporary cwm zip, but with a bit of luck it will not return the error anymore then
if the problem does persist tho, you can also try both touch and regular versions of this kernel -> http://forum.xda-developers.com/showthread.php?t=2424964
extract and rename to kernel.bin.md5, place on internal sd and flash them the same way again via terminal emulator.
there is more hope for this kernel as both versions run different versions of cwm than D-kernel (and eachother), but if this does not solve the problem, you will not be able to boot as that kernel is incompatible with stock rom and you will have to reflash via odin.
Carpe-Dimi said:
you are using the temporary CWM tho right? which needs to be flashed via stock recovery? and stock recovery doesn't complain about your mmcblk0p8 partition?
if this is the case, then you can root the stock rom via stock recovery --> http://forum.xda-developers.com/showthread.php?t=2139263
download this kernel for stock rom --> http://forum.xda-developers.com/showthread.php?t=2171054 -extract the zip and place the kernel.bin.md5 file on the root of your internal sdcard
install any terminal emulator, open it and and enter/type su -click accept when prompted for superuser permissions
with that all done enter "dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15" make no typo's on that one, it's lethal.
If done right, it will replace stock kernel with D kernel. which will contain the same version of cwm as in the temporary cwm zip, but with a bit of luck it will not return the error anymore then
if the problem does persist tho, you can also try both touch and regular versions of this kernel -> http://forum.xda-developers.com/showthread.php?t=2424964
extract and rename to kernel.bin.md5, place on internal sd and flash them the same way again via terminal emulator.
there is more hope for this kernel as both versions run different versions of cwm than D-kernel (and eachother), but if this does not solve the problem, you will not be able to boot as that kernel is incompatible with stock rom and you will have to reflash via odin.
Click to expand...
Click to collapse
Ok, Yes I have rooted stock ROM and temporary CWM, so i am going to try the D-kernel. Hope is compatible with P version.
EDIT:I did the steps, and now, succesfully hardbricked Lol Checksum was ok, command too. OMFG
PC is showing "U8500 USB ROM" in device manager when I connect the USB cable so.. thanks
mybe there is problem that the kernel is build on the me7 or mf1 software.
Guys for everyone who has P version Never flash normal version officiel fw like me7 mf1 via odin on P version of ace 2 it will hardbrick you device that they have to change the motherboard so be carefully
Click to expand...
Click to collapse
EDIT2: LOL i putted battery out for a while and now can go to download mode. But i am at school so now i´ll go home and try odin... AGAIN
EDIT3: I am online again, phone is running well on the stock rooted JB again.. still cannot flash roms, but whatever...
Heya, sorry for the lack of response I've been a lil busy.
I thought that kernel would work on P version as well tho, sorry about that :crying:
Glad to see that you recovered your phone from that atleast.
Last thing i can think of then is to use this kernel --> http://forum.xda-developers.com/showthread.php?t=2072872
It's built for gingerbread, so your phone will again not boot after flashing, but the 8160Pxxlk3 version will for sure be compatible with your phone, and it has yet another version of CWM you might be able to use for flashing
If that doesn't work tho, I really am out of options
gapps-jb-20131011
Hi. I am using Sony Xperia NEO L and managed to upgrade to JB. I followed the steps until i hot a noticed saying that the Installation aborted. What went wrong? Please help! I'm stuck here and cannot going anywhere :crying:
Hi
So yesterday I was trying to install TWRP recovery in order to install Cyanogenmod 11 on Xperia S , I followed a tutorial on techglen, the problem is that now I only have the recovery on my phone , it boots instead of the system , the system files are still there but I can't boot on it , If i connect my phone to my computer I can't access the storage even if I mount it using TWRP
So i have some questions
Is my phone broken?
Instead of flashing a .elf file i flashed the .img instead , is that the source of the problem? ( i didn't do it on purpose , but i didn't pay attention :/ )
can i flash the boot.img of the old system to get it back on booting ?
If there's a way of pushing the CM11 into my phone and installing it would that fix my problem?
Can i use flash tool to flash my old system back ?
i have tried many roms .
some roms dont give any error and get installed but does not boot up stucks on sony logo
after installing i saw in twrp file manager no files are copied
i think system is not getting extracted
can anyone help me out...
Hello. I have ported TWRP from Redmi Note 3 for Xperia M5. But it's some issues in it.
1. I can't wipe cache, because I can't umount it. It writes that device or resource busy.
2. I can't mount usb-otg. It nothink happens when I trying check it.
Mb somebody faced with this problem and can give me advice how to fix it.
May be I forgot to put some files from boot.img to recovery.img when ported? Can somebody say which files I have to change?
Hi dude, Facing the same problem here. Also, after I installed TWRP, I got stuck in the logo screen so I have to flash my entire system and data partitions again.
Why are you trying to port, we already ported it.