Greetings,
I have performed the following:
from .370 SGP311AB 16GB wifi
1. backup TA partition
2. OEM unlock
3. Doomlord rooted
4. install Phil XZ recovery
5. boot clockword recovery
6. format system and factory restore 3 times, clear cache and davik
attempts to install cm11 pollex result in status 7 errors - tried other nighties from different built date without success
tries pollex-windy - can't install kept saying this device is not pollex.
any input is appreciated
cheers
Sent from my Galaxy Nexus using Tapatalk
Related
Hey Guys
I have FXP132-cm9 installed on my device. But since I installed this, none of the new FXP 133-cm9/cm10 nor FXP 134-cm9/10.
I flashed the ROM from recovery, flashed gapps, wipped the caches. Then rebooted into fastboot and flashed the kernal. Then on reboot it just gets stuck FreeXperia logo and never goes past that.
Then if I reboot into recovery again and try to flash the ROM again, it gives me an error 7. assert failed. L26a, L26i, nozomi. Then none of the ROMS work. I have to restore from previous backup in order to get my device working again.
Any ideas on what I can do?
Thanks
Assert fails because you may format /system. It causes product name to be removed. Next time avoid doing this.
For this time, extract updater-script from the zip, remove the assert command and then replace the old updater-script.
Sent from my LT26i using xda premium
tot_anusak said:
Assert fails because you may format /system. It causes product name to be removed. Next time avoid doing this.
For this time, extract updater-script from the zip, remove the assert command and then replace the old updater-script.
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Ah ok. That makes sense. Thanks for the feedback.
I did manage to get it working. I first flashed the boot.img, then installed the rom and cleared dalvik cache, then it working perfectly fine.
NightStalkerDNS said:
Ah ok. That makes sense. Thanks for the feedback.
I did manage to get it working. I first flashed the boot.img, then installed the rom and cleared dalvik cache, then it working perfectly fine.
Click to expand...
Click to collapse
Hello, could you please post the steps you took when updating? I've tried tons of methods now and always get stuck on the FXP logo...
Gorestav said:
Hello, could you please post the steps you took when updating? I've tried tons of methods now and always get stuck on the FXP logo...
Click to expand...
Click to collapse
> First make a nandroid! IMPORTANT
> Flash Bin4ry's recovery image <here> (Instructions in thread)
> Reboot phone and it will automatically boot into recovery
> Format /system
> Wipe data/factory reset
> Wipe Dalvik Cache
> Flash ROM
> Flash GApps
> Reboot and let the initial setup take place (Not sure whether this is necessary but just do it to be safe)
> Reboot into recovery
> Go into backup and restore, choose advanced restore, select your backup and select restore /data
> Finally reboot and you should be upgraded with all your data preserved
Click thanks if I helped, if it goes wrong just restore from your nandroid backup
At the step from the guide above where i'm about to restore my /data I get an error message like this:
Code:
E:format_volume: make_extf4fs failed on /dev/block/
Anyone have a solution?
THANKS
CM & FXP = lost radio signal
Gorestav said:
Hello, could you please post the steps you took when updating? I've tried tons of methods now and always get stuck on the FXP logo...
Click to expand...
Click to collapse
The steps I did to upgrade is this:
- Download the FXP version you want. (If on Xperia S, make sure its the nozomi one)
- Extract the zip file to any directory on your PC and also copy the zip file to your SDcard
- Shut down your device
- Boot into fastboot (Hold the volume up key while putting usb cable in. Blue LED will come on and nothing else
- Open command prompt or terminal and navigate to the adb directory
- Flash boot.img via fastboot: fastboot flash boot ~/Path/To/boot.img
- Then disconnect the device from the host machine and boot into recovery
- Flash zip from SDCard, select zip put on above
- Flash gapps
- Wipe dalvik cache and nothing else
You should be able to reboot the device now without any issues. And all your existing apps and settings will still exist as you had it before if you are upgrading from previous FXP version.
Good luck
fareeed said:
> First make a nandroid! IMPORTANT
> Flash Bin4ry's recovery image <here> (Instructions in thread)
> Reboot phone and it will automatically boot into recovery
> Format /system
> Wipe data/factory reset
> Wipe Dalvik Cache
> Flash ROM
> Flash GApps
> Reboot and let the initial setup take place (Not sure whether this is necessary but just do it to be safe)
> Reboot into recovery
> Go into backup and restore, choose advanced restore, select your backup and select restore /data
> Finally reboot and you should be upgraded with all your data preserved
Click thanks if I helped, if it goes wrong just restore from your nandroid backup
Click to expand...
Click to collapse
Here to confirm that this method works for me after trying so many different ways to get it to boot. Thanks!
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
geon106 said:
I wanted to install a custom ROM for my TF201. So I downloaded the Energy ROM and placed it within the SD Card as update.zip
I flashed CWM and ran the Asus Bootloader Unlocker.
Then using Rom Manager rebooted into CWM, following on screen prompts I installed from SD Card the ROM. The install completeted successfully, the tablet restarted and showed the Eee Pad logo, but got stuck. I've tried cold booting from recovery mode, tried reinstalling the ROM but nothing is working. It is refusing to boot up properly.
Have I bricked the tablet, if so how do I fix it if at all possible?
Click to expand...
Click to collapse
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
McJesus15 said:
Did you do an MD5sum check on your download? Also have you tried flashing another rom? And my third and final question did you wipe Dalvik cache, cache, and factory reset before you installed?
And this is more of a preference thing but I'd suggest TWRP over CWM. I've had issues on other devices with CWM but TWRP on the Prime is perfect.
Click to expand...
Click to collapse
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
geon106 said:
I did a factory reset, then selected wipe Dalvik cache and cache.
How would I flash another ROM? I'm not sure how I can get another ROM onto the device as CWM cannot search external storage, only internal?
I was going to use TWRP but wasn't sure how to get it flashed onto the device, where as CWM was simpler. I didn't do an MD5 check on the ROM
EDIT:
Just tried using Fastboot USB to flash the official ASUS ROM(Tried latest JB and ICS 4.0.3), both write to the device okay but both fail
It says "FAILED <Remote: <>"
On the device it shows: Failed to process command flash:system error(0x170003)
Click to expand...
Click to collapse
IT LIVES!!!
Don't know how I did it, but I managed to get TWRP installed on it. Using Fastboot somehow or ADB. It booted into TWRP and mounted external SD card, then flashed an official JB ROM(the Prime was on ICS before) and it has now booted up fine
I will now try and re-flash a custom ROM again(a different one) using TWRP but it is all looking superb
I was worried i'd have to claim on the extended insurance I took out with the retailer
Please help!! I have searched all over this forum but i still can't find a solution to my problem
First of all, I'm still new in android modding so please forgive me if I don't have sufficient information regarding this question.
I have an Xperia neo, with the original ICS firmware (4.1.B.0.587), locked bootloader, rooted with this method http://talk.sonymobile.com/thread/97327
and I use the CWM Recovery 5.0.2.7-nAa-r2 from this thread http://forum.xda-developers.com/showthread.php?t=1364509 because my phone won't go to the recovery mode if I use the x-parts CMW package
I have tried installing the Zelly Cream v1.20 custom rom by following the exact instruction for locked bootloader, which is :
Installation instruction for Zelly Cream FULL ROM
Before installing this rom, make sure you have a complete nandroid backup and you
have performed all the necessary steps, otherwise you may get bootloop. I will not be
responsible for any kind of damage or loss to your phone, do this at your own risk. Read
carefully and follow the steps to install the rom.
1. Reboot to cwm.
2. Wipe data/factory reset.
3. Wipe cache partition.
4. Wipe dalvic cache under advanced menu.
5. Wipe battery stats under advanced menu.
6. Format data under mount and storage menu.
7. Format system under mount and storage menu.
8. Format cache under mount and storage menu.
9. Install zip from sd card.
10. Follow the steps in aroma installer to install the rom.
11. Uncheck "Reboot device" after installation completed and click on next to go
back to CWM.
12. Now reboot your phone..
Click to expand...
Click to collapse
But my phone keeps rebooting (boot loops) so i had to reinstall the original ICS firmware using this method http://talk.sonymobile.com/thread/35239 . After that i re-rooted my phone, restored my nandroid backup, and tried installing Zally Cream v1.20 again. But I still get boot loops and now I'm getting desperate (so in summary i have bricked/boot looped my phone twice trying to install the Zelly Cream) :silly:
So can anyone please help me??
Any answer would be much appreciated. Thank you!!
After flashing stock firmware why did u restored nandroid backup??
Flash stock firmware using flashtool with full wipe
Root it, install cwm
Goto cwm & wipe cache, data, delvik cache, format system, data cache
Now flash the rom
Reboot
Sent from my MT11i using Tapatalk 2
So I plan on installing 4.4 kit kat. So I went ahead and downloaded cm11. I then went into recovery , I wiped data, wiped cache and dalvik.
Then went into mounts and storage and formated system ,data and cache. I then went to install cm11 and I got this error:
ELerror in /emmc/kitkat/cm11-xxxxx nightly.
(status 7)
Installion aborted
Please help me . How do I get past this error? I'd really love to have 4.4 on my phone
bump
You need to flash a KK compatible CWM first........
Sent from my Infected KitKat bar.....
First install 4.3 jelly bean, and then 4.4. This worked for me
Sent from my GT-I9100 using XDA Premium 4 mobile app
Except that you don't even need to install JB.......as I said in my original reply, the ONLY thing you have to flash is a KitKat compatible CWM......
To make things even easier, here's a copy of the CWM I flashed (via CWM) that enabled me to flash straight to KK..(CWM courtesy of @infected_)........
https://www.dropbox.com/s/rskqnncy8s0k05y/CWM-KitKatCompatible-i9100.zip
Sent from my Infected KitKat bar.....
I solve mine when I flashed CM10.2 nightly. Then do not restart your phone. Instead go to advanced options and restart recovery. Then you will see the latest CWM. Then flash CM11 and their GApps.
OP......flashing a temporary ROM is NOT necessary....it's just overcomplicating things......
ALL you have to do is......
1) download your chosen ROM and GApps....
2) download the CWM package I linked you to....
3) reboot into your EXISTING recovery....
4) flash the CWM that you downloaded at step 2....
5) reboot recovery...
6) flash your chosen ROM/GApps while following all wipe/install instructions......
JOB DONE.....SIMPLE AS.....
NO NEED TO FLASH A TEMPORARY ROM.......
Sent from my Infected KitKat bar.....
Stucked S2
keithross39 said:
OP......flashing a temporary ROM is NOT necessary....it's just overcomplicating things......
ALL you have to do is......
1) download your chosen ROM and GApps....
2) download the CWM package I linked you to....
3) reboot into your EXISTING recovery....
4) flash the CWM that you downloaded at step 2....
5) reboot recovery...
6) flash your chosen ROM/GApps while following all wipe/install instructions......
JOB DONE.....SIMPLE AS.....
NO NEED TO FLASH A TEMPORARY ROM.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
I ve just followed your list after root but my S2 stucked.
I will be happy for further info.
Thanks
OK.....this is the exact order that I did things coming from CM10.1....
1) downloaded ROM, gapps and KK compatible CWM to my REMOVABLE micro SD card.
2) rebooted the phone into existing CWM and flashed KK compatible version.
3) turned the phone off and removed micro SD card.
4) rebooted into new CWM, went to mounts and storage, and formatted EVERYTHING....
5) turned the phone off and re inserted micro SD card.
6) rebooted back into CWM and installed ROM and gapps.
7) wiped cache and dalvik and factory reset
8) rebooted the phone into Android....
Just remember that the first boot WILL take longer than normal.....
Good luck.....
Sent from my infected_ KitKat
Stucked
keithross39 said:
OK.....this is the exact order that I did things coming from CM10.1....
1) downloaded ROM, gapps and KK compatible CWM to my REMOVABLE micro SD card.
2) rebooted the phone into existing CWM and flashed KK compatible version.
3) turned the phone off and removed micro SD card.
4) rebooted into new CWM, went to mounts and storage, and formatted EVERYTHING....
5) turned the phone off and re inserted micro SD card.
6) rebooted back into CWM and installed ROM and gapps.
7) wiped cache and dalvik and factory reset
8) rebooted the phone into Android....
Just remember that the first boot WILL take longer than normal.....
Good luck.....
Sent from my infected_ KitKat
Click to expand...
Click to collapse
OK. let me explain my situation exactly right now.
I have "Samsung Galaxy S2 GT-I9100"
and it s original right now as software
I mean I didn't root it right now.
my question is "what should I do exactly from right now to CM-11"
Let me explain what I did before:
1) I ve rooted it with " Jeboo_kernel_i9100_v1-2a.tar " via Odin
2) I downloaded SuperSu then Titanium Backup Root
3) I copied to my SD card into phone
1# CWM-KitKatCompatible-i9100.tar
2# CM-10.1.3-i9100.zip
3# CM-11-20140308-SNAPSHOT-M4-i9100.zip
4# CM-11-20140310-NIGHTLY-i9100.zip
5# gapps-jb-.....zip
6# gapps-kk-....zip
4) I applied 2# then 5# (didn't occur any problem) and rebooted my phone
5) All is done!
6) Then I upgraded CWM with 1#
7) I applied 4# then 6# (didn't occur any problem) and rebooted my phone
8) Phone was stucked at the just start with "Samsung Galaxy S2" and there was a " ! " sign under it.
steps i need to follow for flashing rom
1. wipe (delvik, cache, system, data)
2. install rom (after flashing a message appears 'No OS installed)
3. then i press home button, and reboot to recovery.
4. Again install rom (this time without wiping any thing)
5. finally gets new rom.
why m not able to flash rom directly after wiping cache etc.
i have to always flash the rom two times (step 4) to install.
where i am getting it wrong?? help please
previously I was using Pixel experience Rom (decrypted)
edit solution: the issue was because of using older version of TWRP. hence solved.
your issue might be because of system partition not getting mounted properly after the wipe. Hence After wiping, reboot to recovery then flash rom.