Related
I tried a search but didn't find much of any relevance to my Arc's problem.
My Arc was getting quite laggy so I decided to wipe and put a custom ROM on. I rooted, then unlocked the bootloader and managed to put on CWM using DoomLord's kernel. Everything fine up until here.
Then, mistakenly, I tried to put stable CM7 on without updating the stock ROM. I was still on 3.0 (2.3.3) something. Well, after that it got stuck in a boot loop with the SE and CM7 logos just coming up and restarting.
I then tried the Flashtool with a stock uptodate 4.0 something firmware. It flashed successfully, but it still was stuck in the loop, albeit now without the CM7 logo. I then tried the FTA unbricking tool for repairing the trim area but it still stayed in the boot loop.
What else can I do? Maybe there is a driver problem and that is why even after using Flashtool it still doesn't boot?
I would be very grateful if someone could help me on this.
You have to flash FXP's kernel and not DooMKernel.
But I also tried to flash a stock rom and that didn't work also.
EDIT: I flashed stock ROM again, still didn't boot. Installed DoomLord kernel and then arconium and it still doesn't boot.
EDIT 2: In CWM Recovery if I try to wipe data, it says this:
"E:format_volume: no MTD partition "userdata"
Has anyone got a fix for this?
It would be much appreciated.
can you charge your phone now?
Yep, I can charge the phone.
it means your kernel is still working....
then have it fully charged, then try to flashing again.
some tips:
1. always have latest flashtools
2. always have your phone fully charged b4 flashing.
3. proceed flashing carefully. if u miss one thing, then trouble come.
4. have cache and dalvik cache cleaned after flashing a kernel or Rom.
good luck mate...
gogo415 said:
it means your kernel is still working....
then have it fully charged, then try to flashing again.
some tips:
1. always have latest flashtools
2. always have your phone fully charged b4 flashing.
3. proceed flashing carefully. if u miss one thing, then trouble come.
4. have cache and dalvik cache cleaned after flashing a kernel or Rom.
good luck mate...
Click to expand...
Click to collapse
No luck with previous firmwares so I'll try to flash the latest .62 stock ROM and then see.
I'll let you know how I get on. Thanks!
Well lads, I managed to get it working by flashing the LT18i firmware (4.0.2.A.0.42_CE). Now I just need to go back to the drawing board and try to get CM7 on there.
Thanks for all the help! I'll update this thread with any experiences.
I've managed to do it. Installed latest .62 firmware, flashed CM7 kernel, flashed 7.2 ROM and then GAPPS.
I don't know why it took me two days to bring the phone back from the dead.
ZAnwar said:
I've managed to do it. Installed latest .62 firmware, flashed CM7 kernel, flashed 7.2 ROM and then GAPPS.
I don't know why it took me two days to bring the phone back from the dead.
Click to expand...
Click to collapse
hi, i came up with the same question:
E:format_volume: no MTD partition "userdata"
and my device is moto xt502
could you be so kind to give some details how you fix it
thank you very much
I am having the same problem too..please help! i flashed cm7 kernel n followed the instructions very carefully
ilamaan said:
I am having the same problem too..please help! i flashed cm7 kernel n followed the instructions very carefully
Click to expand...
Click to collapse
I followed the instructions too, though they are not so much noob-friendly (and neither are the people on the forums, it seems...). FXP is not responding (actually, they rarely respond to anything, they usually just post when new release is out), other people either don't know how to fix it, because they haven't experienced such issues, or they are just hostile because you're "a an annoying noob". Anyway... first time after trying to flash 64 baseband on 107 or 106 release, I got stuck on logo, then flashed back to .42 and it worked. Now, while updating to 108, I tried to flash the 64 libraries and patch, but it didn't work. Got back to .42, but this time nothing happened. Still stuck on logo. And when I try to restore data, it says:
E:format_volume: no MTD partition "userdata"
Error while formatting /data!
I think I'll go back to stock... love CM, but hate the poor/no help of the developers...
try these
flash new firmware using flashtool.
after flash.turn on your device.
enable uknown source n usb debug
then turn off your fon
flash baseband 64
then turn on your fon
put fxp108 updated-kang,gaps,baseband 64 libs on your memory card,
then turn off your fon
flash fxp kernel fastboot flash boot boot.img
after flash turn on your fon..go to recovery
formated factory reset,wipe cache,clear dalvik cache,wipe betry stats..
flash update cm7.update.zip,gaps.zip,baseband64libs.zip
reboot your fon..wait 2 or 3 mint..done
My thanks goes to you. I was hoping to avoid full wipe, but I don't care anymore, since I brought my phone back to life. I skipped these steps, though:
beranchoi said:
flash baseband 64
flash baseband64libs.zip
Click to expand...
Click to collapse
...because I went to check which baseband my phone was after flashing Global .62, and it said I was on -64, so it was no more necessary. For all of you having trouble with booting, follow the instructions given.
And now back to restoring all those apps
hey guys, can you post the link to that stock firmware, baseband and libs? maybe I've downloaded something wrong :/
btw. is there still that bug with a dark screen after locking phone?
lemon66 said:
hey guys, can you post the link to that stock firmware, baseband and libs? maybe I've downloaded something wrong :/
btw. is there still that bug with a dark screen after locking phone?
Click to expand...
Click to collapse
This is the link to the stock 4.0.2.A.0.42.. flash it using flashtool.. http://www.multiupload.com/W3B7BOKUXQ
Everything you need for flashing FXP is on his signature, including bb .64 (to be flashed with flashtool - doesn't erase a thing).. then download FXP (latest is 108) and inside the zip file you'll see boot.img, which contains the special kernel (to be flashed using fastboot, not flashtool).
Also there's no dark screen bug in the latest releases, certainly not in FXP 107 and 108, which I'm using now.
Please help!
beranchoi said:
try these
flash new firmware using flashtool.
after flash.turn on your device.
enable uknown source n usb debug
then turn off your fon
flash baseband 64
then turn on your fon
put fxp108 updated-kang,gaps,baseband 64 libs on your memory card,
then turn off your fon
flash fxp kernel fastboot flash boot boot.img
after flash turn on your fon..go to recovery
formated factory reset,wipe cache,clear dalvik cache,wipe betry stats..
flash update cm7.update.zip,gaps.zip,baseband64libs.zip
reboot your fon..wait 2 or 3 mint..done
Click to expand...
Click to collapse
Hey, this is my first post on here. I am new to android and just got an arc a few days ago. Even before i got it i was trying to figure out how to mod it. I am reasonably good at computers but a lot of the stuff i read on these forums is beyond me.
I have done my best to root and install CM7 on my arc but i have failed yet again.
I finally got it rooted and was all happy until when i tried to install CM7, all i can get to is the boot screen, but although the little android on the skateboard is very cool, i wish i could get it going!
So because I dont really understand the list of instructions you posted in this quote, i was hoping you could kind of translate into noob-speak. I still dont feel like i completely understand 'flashing'. In your instructions you say to "flash baseband 64" and that is the main point where I am stuck i think. Do you use a certain program (flashtool?) for this? or do it through a terminal window on the PC.
Also links to all the files mentioned would be awesome, its hard to find proper links with multiupload down and that kind of thing. Also with the rate this kind of tech evolves, things get outdated to quickly.
Please help! At the moment i have (i think) successfully returned my arc to the stock firmware using flashtool. Although i did this twice because i re-tried flashing CM7 and failed again. And the second time i couldnt seem to select LTI5i as the device to flash too, but LTI8i is what i used and it appears to have worked. So any help with that little conundrum would also be appreciated!
Cheers for any help given, I am so desperate to get this mod going as i have spent a solid 10+ hours trying already.
your bootloader unlock?right?
which kernel u use right now?
@tehknowitallnoob, I can lead you through the whole flashing process, if you want to, but only on Friday after around 9 pm GMT +1, since I don't have the time to do it earlier.
Sent from my LT15i (Xperia arc) on CM7
Try this:
Reflash back to stock ROM with a flashtool.
Then again flash the cm7 or try cm9
-cheers
Ok, so basically i have just gone ahead and followed these steps for flashing cyanogenmod:
wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Arc:_Full_Update_Guide
When i got up to step 7, i wasn't able to load clockwork mod, and because i am a noob and new to this, i actually didn't know that i had to install it beforehand. So now, i've got a phone which wont turn on properly (stuck with a lit up black screen) and will only connect into fastboot
Please, somebody help me!!!! I am really scared that i may have bricked my phone, if i can do anything to get it running again, i would be so happy. Please help
did you flash the CM kernel? and CM recovery comes with the kernel..you dont need to install it separately..
xperiaarcsnoob said:
Ok, so basically i have just gone ahead and followed these steps for flashing cyanogenmod:
wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Arc:_Full_Update_Guide
When i got up to step 7, i wasn't able to load clockwork mod, and because i am a noob and new to this, i actually didn't know that i had to install it beforehand. So now, i've got a phone which wont turn on properly (stuck with a lit up black screen) and will only connect into fastboot
Please, somebody help me!!!! I am really scared that i may have bricked my phone, if i can do anything to get it running again, i would be so happy. Please help
Click to expand...
Click to collapse
Alright first thing first. Which version of CM are you trying to flash? And where you downloaded it from?
---------- Post added at 04:15 AM ---------- Previous post was at 04:06 AM ----------
Ok we will come to flashing ROMs later lets first get you to boot your phone so that you can use it and not be scared. Whatever you have messed up, flashing the phone with flashtool and official FTF would make it normal. I hope you know how to do it. Google around and you can find flashtool. Get it installed to you PC then go here http://forum.xda-developers.com/showthread.php?t=1330314 and download the ftf file and flash it using flashtool. Then your phone will be back up and running. Once its done. Come back here and tell me. Ill help you with flashing ROMs.
@ arpith.fbi
Yes i flashed a boot.img that came with the CM9 zip file, but that is all.
@ gnirujan
I am flashing CM9, and i got it from the downlaods section of the CM website.
I have also downlaoded flashtool but im not sure how to flash the FTF file. By the way, that file is for LT18i, and i have a LT18a. Would it matter?
Thanks for the replies
also gnirujan,
I checked that FTF file, and its 370mb. Is it the full firmware? If it is, i will flash it but if there is a way to continue with the cyanogen flashing, i would love to avoid downloading that ftf.
P.S. LANKAN PRIDEEE!!!!
ok first tell me during startup do u see boot logo? or any logo?
When i boot up, all i see is a lit up black screen with nothing on it
Flash the attached boot.img which is the FXP CM9 kernel from this site, then install the zip.
Ok, thanks, i will try it.
That didn't work either , did the same thing as the other.
I have managed to flash a stock ics ftf file, and i have finally rooted my phone. Now i want to try Rom manager instead to install, but when i go to install Clockwork mod recovery, it says stuff about my phone not currently being officially supported.
Any ideas?
xperiaarcsnoob said:
I have managed to flash a stock ics ftf file, and i have finally rooted my phone. Now i want to try Rom manager instead to install, but when i go to install Clockwork mod recovery, it says stuff about my phone not currently being officially supported.
Any ideas?
Click to expand...
Click to collapse
Look in dev section for arc and look for post by pvyparts, his thread is all about cwm recovery check to see if your phone Is listed if not ask there.
Sent from my LT15i using xda premium
xperiaarcsnoob said:
That didn't work either , did the same thing as the other.
Click to expand...
Click to collapse
Your boot loader is unlocked right? You wanna install Cynogenmod 9 right? You dont install the one from cyanogenmod site. It has a non working kernel. In XDA there are these guys called FXP (Free Xperia Project) they are the ones responsible for CM for all Xperia devices. So do this. Go tho this thread http://forum.xda-developers.com/showthread.php?t=1356685 download the CM9 RC 1 FXP 128. Its a 130MB file. Download it and now extract it and flash that boot.img to your Arc S using fastboot. Now start your phone and you should see FXP boot screen then from there go to recovery and try flashing the CM9 RC 1 you have. That should work. I suggest if you can replace the CM9 you have in your memory cad with the FXP128 zip its better so that you can flash the latest FXP128 CM 9, which has lots of improvements.
Edit: Arc S and Arc same ZIP its called anzu
---------- Post added at 06:11 AM ---------- Previous post was at 05:53 AM ----------
xperiaarcsnoob said:
I have managed to flash a stock ics ftf file, and i have finally rooted my phone. Now i want to try Rom manager instead to install, but when i go to install Clockwork mod recovery, it says stuff about my phone not currently being officially supported.
Any ideas?
Click to expand...
Click to collapse
Allright as far as i know there are two ways you can get CMW installed on your phone. 1. Download CWM auto installer from play store and install CMW through that. 2. Flash a kernel which has CWM pre installed.
In this link http://forum.xda-developers.com/showthread.php?t=1680793 you can find stock sony kernel with CWM. You download it and flash it using fastboot. That will get you CWM. hope i helped you.
Thanks gnirujan,
I managed to find a FXP127 kernel yesterday and it worked. But this would be even better. I heard that FXP128 is much faster as well, but I've already set up my whole system and dont want to reset it now . Any way of updating it without wiping?
Thanks again !!!
xperiaarcsnoob said:
Thanks gnirujan,
I managed to find a FXP127 kernel yesterday and it worked. But this would be even better. I heard that FXP128 is much faster as well, but I've already set up my whole system and dont want to reset it now . Any way of updating it without wiping?
Thanks again !!!
Click to expand...
Click to collapse
I believe you can try flashing on top of your existing system. I personally have never tried it. But i think it is possible. I would recommend you to flash FXP 128. The improvements are very very visible. More fast and smooth.
gnirujan said:
I believe you can try flashing on top of your existing system. I personally have never tried it. But i think it is possible. I would recommend you to flash FXP 128. The improvements are very very visible. More fast and smooth.
Click to expand...
Click to collapse
Could anyone check to see if this is true
yes you can update it without wiping anything..but i recommend atleast wiping cache
arpith.fbi said:
yes you can update it without wiping anything..but i recommend atleast wiping cache
Click to expand...
Click to collapse
Will wiping cache delete any system settings or things like homescreen setup?
xperiaarcsnoob said:
Will wiping cache delete any system settings or things like homescreen setup?
Click to expand...
Click to collapse
nope...everything will be the way they were..nothing will change
Thank you very much arpith
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.
Dear masters,
After 20 hours of reading and trying new things to me, I thought I finally knew what to do to get a custom ROM on my XPERIA Arc with stock 4.0.2.A.62 firmware. .62 seemed to be a pain in the ass, because this version doesn't want to get rooted. So I unlocked my bootloader and then flashed 4.0.2.A.42 on it. Everything on my phone was working fine.
Now I wanted to get a custom ICS ROM on my phone so I decided to go for Xperia Ice Cream Pureness V13. I downloaded the ROM and the patch for the arc and succesfully installed it with CWM recovery.
I did this by going into fastbootmode, flashed this kernel by doing "fastboot flash boot boot_ARC.img", because I needed a stock kernel, so I thought it would be better to get an advanced stock kernel. Then I did "fastboot boot recoveryARC.img" and my phone booted into CWM recovery. I had no errors whatsoever during the installation of the ROM and the patch. Using this recoveryARC.img file is my only way, because via the ROM manager app, I don't get into recovery.
When I tried to reboot, I just got another boot logo appearing, but just stays there and won't boot. See the image in the attachment.
So now I'm here with a not working phone and my noobyness.
Please help, thanks in advance,
Ruben
You say that you have installed advanced stock kernel.
Is it compatible with your ROM??
Edit...
Readed a little. Any stockbased kernel is suppoused to work.
Try with the latest stock kernel.
He says to let it be for a hour.
If anything wont help, revert to all stock.
Sent from my LT15i using xda premium
TheHaso said:
You say that you have installed advanced stock kernel.
Is it compatible with your ROM??
Edit...
Readed a little. Any stockbased kernel is suppoused to work.
Try with the latest stock kernel.
He says to let it be for a hour.
If anything wont help, revert to all stock.
Sent from my LT15i using xda premium
Click to expand...
Click to collapse
Yea, so it's stockbased.
Anyways, I just kept on trying things and also tried a different ROM and now Jellybean Sandwich 7.3 just WORKS.
Still got no idea what caused the stuck booting screen.
To me, all these files, kernel, rom, flash, root, etc, etc complicates the whole thing and it doesn't make sense to me anymore what works with what etc... LOL. Anyways, it works now, thanks for caring
snsgn said:
Yea, so it's stockbased.
Anyways, I just kept on trying things and also tried a different ROM and now Jellybean Sandwich 7.3 just WORKS.
Still got no idea what caused the stuck booting screen.
To me, all these files, kernel, rom, flash, root, etc, etc complicates the whole thing and it doesn't make sense to me anymore what works with what etc... LOL. Anyways, it works now, thanks for caring
Click to expand...
Click to collapse
ahhh you are in JB rom....and so you aren't in stockbase rom/kernel -.-
you Must learn some of kernel,rom and other specifics or you brick your phone
now you are in Jelly Bean Version---> so with Rom JB and Kernel JB....if you flash kernel ICS or GB in rom JB not work and phone stop on boot (like your phone) ok??
Raschild6 said:
ahhh you are in JB rom....and so you aren't in stockbase rom/kernel -.-
you Must learn some of kernel,rom and other specifics or you brick your phone
now you are in Jelly Bean Version---> so with Rom JB and Kernel JB....if you flash kernel ICS or GB in rom JB not work and phone stop on boot (like your phone) ok??
Click to expand...
Click to collapse
When I go to 'About Phone' now, I see the kernel is 2.6.32.9-perf / [email protected] #1.
Seems like this is the original kernel, so the kernel never flashed? Strange...
Everything works fine...
No longer booting
So i saw this thread and its relevant to me. Figured i would start here.
Using CWM i loaded Iced bean ROM to my phone.. in my excitement i forgot to flash the arcknight kernal.. Now my phone simply boots to Sony Ericcson boot screen. No further..
on top of that i cannot seem to load into fastboot. When i try the steps from this thread.. http://forum.xda-developers.com/showthread.php?t=1034087 i cant get my fastboot to work.. no blue LED.
Have i ruined my phone?
I don't know it will work or not,but man, you can try ...
1: Using flash tool, put your Arc into Fastboot mode.
2: reflash boot_ARC.img
3: try some roms such as Ultimate HD 2.0 (recommended) , Jelly SandWich......
i hope it will be useful for you.
zazabo-san said:
I don't know it will work or not,but man, you can try ...
1: Using flash tool, put your Arc into Fastboot mode.
2: reflash boot_ARC.img
3: try some roms such as Ultimate HD 2.0 (recommended) , Jelly SandWich......
i hope it will be useful for you.
Click to expand...
Click to collapse
My problem is i cant seem to get into fastboot mode. I followed the steps to unlock bootloader but i cant get into fastboot. never get the blue LED.
@OP
The problem is, you 'jumped' from GB to ICS straight away with cwm flash. When changing OS, be sure to flash the new OS ftf first, then flash the kernel, then flash the ROM thru cwm at last. It's good to know though that now your phone is working again.
Sent from my LT15i
Got it fixed up using the SEUS software. Thanks to all for the help
I have a Sony Arco HD (Japanese version of the Acro S), and I have some weird experiences.
Firstly, I installed Nordic stock .200. Then, as I have LB, I installed trinity raptor rom. This uses the aroma installer.
Thought I'd try a different rom, so I tried the BlackZax7 rom, which flashes straight from a zip.
When I flashed it, my phone wouldn't go past the Sony logo.
So, I got it into flash mode, re-flashed stock 200, rooted, installed CWM again, than tried to restore the backup I'd made with CWM, but it failed. No idea why.
SO I reflashed Trinity, using aroma, no problem there.
Today, I thought I'd have another try at installing the BlackZax7 rom, so I backed up my rom again. Thought I'd test my backup, so I tried to restore my back-up straight away. Wouldn't boot past the sony screen, despite seeming to be successful in restoring my working rom.
In both cases, if I plug phone into a power source (USB or mains), it turns itself on, and sticks at the Sony logo. If I unplug it, I can turn it off using the hard reset. But as soon as I plug it in again, it will turn itself on.
When I get home, I will fix my phone with flash tool, but any idea why this oddness would happen?
Nagoyablue said:
I have a Sony Arco HD (Japanese version of the Acro S), and I have some weird experiences.
Firstly, I installed Nordic stock .200. Then, as I have LB, I installed trinity raptor rom. This uses the aroma installer.
Thought I'd try a different rom, so I tried the BlackZax7 rom, which flashes straight from a zip.
When I flashed it, my phone wouldn't go past the Sony logo.
So, I got it into flash mode, re-flashed stock 200, rooted, installed CWM again, than tried to restore the backup I'd made with CWM, but it failed. No idea why.
SO I reflashed Trinity, using aroma, no problem there.
Today, I thought I'd have another try at installing the BlackZax7 rom, so I backed up my rom again. Thought I'd test my backup, so I tried to restore my back-up straight away. Wouldn't boot past the sony screen, despite seeming to be successful in restoring my working rom.
In both cases, if I plug phone into a power source (USB or mains), it turns itself on, and sticks at the Sony logo. If I unplug it, I can turn it off using the hard reset. But as soon as I plug it in again, it will turn itself on.
When I get home, I will fix my phone with flash tool, but any idea why this oddness would happen?
Click to expand...
Click to collapse
Yeah, a real and correct flashing of a ROM is made with Flashtool, not through CWM, flashing through CWM will never install a ROM correctly,
That's just not true. It's normal to back-up and restore ROMs using cwm.
Sent from my Nexus 7 using xda app-developers app
Yes it's true. You are the example.
skywalkerdroid said:
Yes it's true. You are the example.
Click to expand...
Click to collapse
Then why did i manage to restore roms from cwm before?
You aren't helping. Please stop.
Sent from Pompey, via Nagoya.
Restore,maybe. Flashing through CWM it's not so accurate.
---------- Post added at 12:20 PM ---------- Previous post was at 11:52 AM ----------
Ok, you have to wipe everything,dalvik's cache included,after that power on your phone, install drivers,restore to factory settings just to prepare your phone for a clean ROM flashing.Do that and you can flash ROM through CWM without problems.
skywalkerdroid said:
Restore,maybe. Flashing through CWM it's not so accurate.
---------- Post added at 12:20 PM ---------- Previous post was at 11:52 AM ----------
Ok, you have to wipe everything,dalvik's cache included,after that power on your phone, install drivers,restore to factory settings just to prepare your phone for a clean ROM flashing.Do that and you can flash ROM through CWM without problems.
Click to expand...
Click to collapse
I've flashed roms to this phone, to my tablet, all through recovery.
There is some kind of problem with the combination of kernel, recovery and phone.
Flashing roms through recovery isn't hard, normally. I've even done it on the train to work!
Sent from Pompey, via Nagoya.
Nagoyablue said:
I have a Sony Arco HD (Japanese version of the Acro S), and I have some weird experiences.
Firstly, I installed Nordic stock .200. Then, as I have LB, I installed trinity raptor rom. This uses the aroma installer.
Thought I'd try a different rom, so I tried the BlackZax7 rom, which flashes straight from a zip.
When I flashed it, my phone wouldn't go past the Sony logo.
So, I got it into flash mode, re-flashed stock 200, rooted, installed CWM again, than tried to restore the backup I'd made with CWM, but it failed. No idea why.
SO I reflashed Trinity, using aroma, no problem there.
Today, I thought I'd have another try at installing the BlackZax7 rom, so I backed up my rom again. Thought I'd test my backup, so I tried to restore my back-up straight away. Wouldn't boot past the sony screen, despite seeming to be successful in restoring my working rom.
In both cases, if I plug phone into a power source (USB or mains), it turns itself on, and sticks at the Sony logo. If I unplug it, I can turn it off using the hard reset. But as soon as I plug it in again, it will turn itself on.
When I get home, I will fix my phone with flash tool, but any idea why this oddness would happen?
Click to expand...
Click to collapse
the only reason why you are facing problem is LB i also hve personal experience that installing rom through cwm on a LB went to soft brick and sony logo etc etc just unlock your bootloader and then try....... :victory:
and yes any rom which uses custom kernel needs also to hve an Unlocked BL...
n70shan said:
the only reason why you are facing problem is LB i also hve personal experience that installing rom through cwm on a LB went to soft brick and sony logo etc etc just unlock your bootloader and then try....... :victory:
and yes any rom which uses custom kernel needs also to hve an Unlocked BL...
Click to expand...
Click to collapse
Nope, that's not the answer. The roms I am trying to flash are for locked BL, ie they use the stock Kernel.
Anyway, I recovered it last night using flash tool, so I'll probably stick to stock Sony rom for a while seeing as there isn't much change in performance if you can't change the kernel.
Nagoyablue said:
Anyway, I recovered it last night using flash tool, so I'll probably stick to stock Sony rom for a while seeing as there isn't much change in performance if you can't change the kernel.
Click to expand...
Click to collapse
why not unlock your bootloader?
boyheadkick said:
why not unlock your bootloader?
Click to expand...
Click to collapse
You say it like I have a choice........:laugh::silly:
Nagoyablue said:
You say it like I have a choice........:laugh::silly:
Click to expand...
Click to collapse
oh right, you have an acro hd..silly question, BL unlockable?
boyheadkick said:
oh right, you have an acro hd..silly question, BL unlockable?
Click to expand...
Click to collapse
Yeah, Japanese carriers wouldn't even let you do a sim unlock after you finished paying for the phone until recently. I bought my first Japanese smartphone, a Sharp, but Softbank won't let me do a sim unlock. Unbelievable.
Regarding my problem, maybe due to having Trinity 2.7 installed? I had no problem flashing roms or reinstalling backups via CWM on rooted stock .200 or Trinity 2.6.