I have flashed several time and after reboot it stays stuck on the droids on skate boards,which i think is called boot loop.I have done a wipe and nanodroid back up.what am I doing wrong?
deanwards said:
I have flashed several time and after reboot it stays stuck on the droids on skate boards,which i think is called boot loop.I have done a wipe and nanodroid back up.what am I doing wrong?
Click to expand...
Click to collapse
The flash procedure should be:
- download and copy to SD the GSB and Google apps zip files
- restart in Recovery
- [optional] Nandroid backup, if you want to save what you have now
- wipe data/factory reset
- wipe Dalvik cache
- flash GSB
- flash Google apps
- restart
try rebooting into recovery and wiping the dalvik cache (assumung you are using RA_eris recovery) and rebooting again. That's solved most of my bootloop issues.
yeah, real talk i would completely do a full wipe
-data/dalvik
-format your sd card
then
-move GSB 2.8 and gapps to your sdcard and flash.
if it still won't boot i would try and flash kaosfroyo or something and see if that works
hope you figure it out
Just tried to install GSB 2.8 on my stock 2.1 Eris (first custom rom) but it seems to be stuck in the Cynogen7 boot animation (it's been a good 20 minutes now.)
Steps I took:
1. root
2. format sd
3. wipe dalvik
4. flash gsb
5. flash gapps
6. reboot
7. where I am now
Should I just reboot it?
EDIT - fixed
Gigamaster89 said:
Just tried to install GSB 2.8 on my stock 2.1 Eris (first custom rom) but it seems to be stuck in the Cynogen7 boot animation (it's been a good 20 minutes now.)
Steps I took:
1. root
2. format sd
3. wipe dalvik
4. flash gsb
5. flash gapps
6. reboot
7. where I am now
Should I just reboot it?
EDIT - fixed
Click to expand...
Click to collapse
Was the fix wiping data, since you didn't mention that?
Had the same problem so I just went back to xtrROM 5. I'd like to hear how you fixed it.
I battery pulled, rewiped the dalvik then rebooted. 10 minutes later it booted.
Cause of I read it from many users, that they get WLODs anymore on the newest Cm7 release from J and I haven't problems, I'll share a list with steps to install it, with that it worked for me perfectly.
If you have a working Recovery you can start directly with step 6
1. Flash with Flashtool a stock firmware
2. Boot up into stock
3. Activate usb debugging
4. Root it (connect phone with activated debugging mode and press in flashtoll root)
5. Install FreeXperiaRecovery (connect phone again, click "ask root permissions" and then click on xrecovery button)
6. Download the Cm7 rom form here, and the two files from here: http://forum.xda-developers.com/showthread.php?t=1073859
7. Copying all files needed for flashing the rom on your sdcard: Cm7 rom and the Screen off fix
8. Reboot and check if you can enter Recovery
9. If not, start at the point where you install it via Flashtool
10. If yes, take out the battery and wait ~15-30 sec.
11. Now put your battery in again and flash the .ftf bundle from the thread i linked above
12. If it flashed succesfully reboot and enter Recovery. Make ALL available wipes (full wipe, wipe cache, wipe system, wipe battery stats, wipe dalvik cache. I think that are all, right?) Now DON'T reboot before you made the next step, cause you have to start from zero if you reboot before making the next step
13. Flash the Cm7 rom
14. Flash the screen off fix
15. Reboot and wait until you get into the rom.
Note:
I know that J provides a own Baseband package, but i use this .ftf bundle, where I mixed the 435 Firmware parts with the amss.sin of the bb.52 bundle available in the bbcollection thread and I haven't any problems with this and on that way, you haven't to flash always the normal and the modded bb if you switch between roms.
9Lukas5 said:
Cause of I read it from many users, that they get WLODs anymore on the newest Cm7 release from J and I haven't problems, I'll share a list with steps to install it, with that it worked for me perfectly.
If you have a working Recovery you can start directly with step 6
1. Flash with Flashtool a stock firmware
2. Boot up into stock
3. Activate usb debugging
4. Root it (connect phone with activated debugging mode and press in flashtoll root)
5. Install FreeXperiaRecovery (connect phone again, click "ask root permissions" and then click on xrecovery button)
6. Download the Cm7 rom form here, and the files from here: http://forum.xda-developers.com/showthread.php?t=1073859
7. Copying all files needed for flashing the rom on your sdcard: Cm7 rom and the Screen off fix
8. Reboot and check if you can enter Recovery
9. If not, start at the point where you install it via Flashtool
10. If yes, take out the battery and wait ~15-30 sec.
11. Now put your battery in again and flash the .ftf bundle from the thread i linked above
12. If it flashed succesfully reboot and enter Recovery. Make ALL available wipes (full wipe, wipe cache, wipe system, wipe battery stats, wipe dalvik cache. I think that are all, right?)
13. Flash the Cm7 rom
14. Flash the screen off fix
15. Reboot and wait until you get into the rom.
Note:
I know that J provides a own Baseband package, but i use this .ftf bundle, where I mixed the 435 Firmware parts with the amss.sin of the bb.52 bundle available in the bbcollection thread and I haven't any problems with this and on that way, you haven't to flash always the normal and the modded bb if you switch between roms.
Click to expand...
Click to collapse
Hi there. I am curious to try this. How is your battery life. Also, which version are you running, the previous "b" or "c". Reason i ask is because on your signature, it says "7.0.3-X10-J020b"
Thanks
where can i download FreeXperiaRecovery?? I will tray this!
avez197 said:
Hi there. I am curious to try this. How is your battery life. Also, which version are you running, the previous "b" or "c". Reason i ask is because on your signature, it says "7.0.3-X10-J020b"
Thanks
Click to expand...
Click to collapse
I have runned this way J020b, I would try the c, but I can't! It's bad, but my phone is at the se service point for repairing it. But if I get it back, I'll install directly the latest Cm7 version again.
9Lukas5 said:
I have runned this way J020b, I would try the c, but I can't! It's bad, but my phone is at the se service point for repairing it. But if I get it back, I'll install directly the latest Cm7 version again.
Click to expand...
Click to collapse
Thanks. Will give feedback after trying
barsom said:
where can i download FreeXperiaRecovery?? I will tray this!
Click to expand...
Click to collapse
If you download Flashtool 0.2.9.1 there is FreeXperiaRecovery included. Look into the list, there wrote to click on the xrecovery button for installing FreeXperiaRecovery. The files are included in flashtool.
@ 9Lukas5
Hey, just for clarification - I thought it was never a good idea to use the option
"format system" in the "partion tools" sub menu of xrecovery?
Doing this will erase everything - including xrecovery itself [self destruct] and therefore the user would not have any option except complete reflash if anything were to go wrong with the subsequent install.... ?
Correct me if I am wrong.
Edit: if this is what you meant by "wipe system" in OP !
nadiros said:
@ 9Lukas5
Hey, just for clarification - I thought it was never a good idea to use the option
"format system" in the "partion tools" sub menu of xrecovery?
Doing this will erase everything - including xrecovery itself [self destruct] and therefore the user would not have any option except complete reflash if anything were to go wrong with the subsequent install.... ?
Correct me if I am wrong.
Edit: if this is what you meant by "wipe system" in OP !
Click to expand...
Click to collapse
Yes i ment this.............maybe you're right, cause it will be formatted by installing the rom, too.........hm..will correct op.
Edit: I made it that way always, and had never problems, so i haven't thought about it.
no its COMPLETELY fine to format system AS LONG AS, you flash the rom RIGHT AFTER (DO NOT REBOOT THE PHONE BEFORE FLASHING ROM AS RECOVERY WILL HAVE BEEN ERASED).
When you format system, and install the rom, the rom has recovery built into it as well and it installs the recovery to your system partition when you flash the rom.
So as long as you dont reboot after format system and install the rom first, your fine.
Hello 9lukas5,
I thought I might mention that I've finally managed to fix my wlod but by installing setcpu on the earlier version of J's rom I was using, and setting it up to on boot run the processor at the usual 998 speed. Then I flashed the update.zip (from j's latest release, just formats the system) which didn't remove setcpu so the cpu was running at 998, this stopped all the random reboots and wlods.
I tried for a couple of weeks to use an update, trying so many different ways of stopping my phone being unusable as soon as I flashed the updates due to wlods.
Just though I'd mention it in this thread as it was on topic. Not everyones fix I'm sure, but helped me.
Cheers for all your support and help with installing the roms.
Sent from my X10 using XDA App
BULL3TPR00F said:
no its COMPLETELY fine to format system AS LONG AS, you flash the rom RIGHT AFTER (DO NOT REBOOT THE PHONE BEFORE FLASHING ROM AS RECOVERY WILL HAVE BEEN ERASED).
When you format system, and install the rom, the rom has recovery built into it as well and it installs the recovery to your system partition when you flash the rom.
So as long as you dont reboot after format system and install the rom first, your fine.
Click to expand...
Click to collapse
K - Right on, ty. Just so it's out there and people know ;-)
I believe the majority of WLODs are to due with the CPU constantly running at full speed.
I was getting a lot of WLODs with FreeXperia Kernel-10 on my ROM until I manually set the CPU governor to on demand.
Just go into Cyanogen Settings and change the CPU governor to on demand (it probably already is set to on demand, so change it to something else and then change it back to on demand).
After that my CPU was running at more than the max frequency and I haven't had many WLOD's (think I've had one since, a major improvement).
Erm not to be funny but their are no WLOD due to the changes J has made in his new version, regardless of how I flash it, no WLOD anymore... It has nothing to do with the way you flash the rom that caused this...
Hi guys,
I have follow ALL step from the step 1.
The phone boot, ask for the PIN code, then the page to change the language and then WLOD...
Do you think it come from the CPU frequency ?
I can't found the BTS kernel for this ROM.
Thank you for your help.
hmm....I shared it cause I hadn't any problems of WLODs yet on Cm7 since J019
Hello all,
the main trouble I had causing wlod, was definitely the clock speed. When I flashed the rom (about twenty times, different ways) I would not get enough time to configure any cpu settings, or any other settings, before my phone crashed and it would just start to bootloop with wlod.
I had to install setcpu on an older version of j's rom which didn't have overclock. Checked the box to apply settings on boot. So that when I flashed j's latest rom which is just the update of the system, all my apps were there (didn't bother wiping cache, data, etc) setcpu was still running on boot to keep the cpu set to 998.
Haven't had a single problem since, apart from low battery phone crash.
I tried so many different ways to flash before trying this, hope this helps someone.
Sent from my X10 using XDA App
Any body make a stock kernel image to flash to check sleep state vrs miniloader issue?????????
Worked a treat!! Thank you!
Situation : 2 SE X10i's.
1 black with xRecovery. Works ok.
1 white with xRecovery. After (re)booting the phone, xRecovery is loaded immediately.
It's a bit annoying, how can I fix this?
Have you try to ReFlash the RoM..?
Hope it can be fix after ReFlashing..
Is it ROM-related or must I reflash/re-install xRecovery?
I'm not sure..but some ROM put a Reboot/Restart options that in Power Menu and sometime Reboot/Restart options mean Restart to xRecovery..
But Re-Installing XRec. is better to solve the problem..
Coz I've the same problem when I Flash My RoM with WB 3.6..but after ReFlashing (Fresh Install)..I solve the problem..
If you press reboot in recovery, its boot to your rom or not?
Try wipe dalvik and fix permission.
And let me know if it solved.
Sent from my SO-01C using XDA App
Reboot in xRecovery is to ROM.
Reboot from phone is with option 'reboot' not into recovery. The X10 doesn't support this.
Even when the phone is turned off, it boots into xRecovery.
I'll try Dalvik cache and permissions.
Do you have "RebooT Options Application (.Apk from market or anywhere not include with the Rom)" installed before..?
If you have..I think you need to Re-Flash the both Rom nor xRec..Remember to BackUp your data first..it's only take 15 mnt and you done..no more problem is you do it correctly..
Never heart of that app.
We don't reboot that often.. It's off or reboot.
Our X10's don't listen to other options I think
hello everyone,
i think i bricked my Xperia S somehow.
what i did is :
1 unlocked the boot loader.
2 update my kernel with ics13.elf
after this my phone was still working.
then i put the FXP134-cm-9-20120817-UNOFFICIAL-anzu on my internal space (turned out to be for Arc, how stupid ididnt read)
i started with the custom recovery and installed CM9 but it gave an error and stopped ( cause of arc software i think but didnt knew it then)
then i did the following as explained on some sites:
-wipe data/factory reset
-advanced > wipe dalvik
-mounts > format system
-mounts /mount system
after this step i rebooted, cause then i found out i gotthe wrong CM9 and wanted to put the right one on my internal space.
after the reboot Sony logo prompted and just freezes there.
cant turn of or on my phone, have to wait till the battery is empty.
but then again when i charge it a little the logo comes and freezes again.
now i try to do safeboot or recovery both wont work.
PLZ plz help me.
ty P.
you've got 2 possibilities:
1st:
reflash the advanced stock kernel and boot into recovery
download the right CM9 file > http://get.cm/get/jenkins/5933/cm-9.0.0-nozomi.zip
try to mount USB mass storage and place the file on your phone
restart the process of installing CM9 like you did before
2nd:
flash a stock firmware via flashtool
let it boot, download the CM9 file and place it on your phone
flash advanced stock kernel , boot into recovery and install CM9.