Hi i am using x8 and i unlocked the bootlaoder put thealfs kernel butafter that stock rom cant load and icant upload my gingerdx rom any ideas how to fix ?
One more thing after i unlocked the Bl before i put alfs kernel i had no signal
Relock your bootloader and try unlocking again with Setool2. That should give you signal back but not sure as I can't really remember .
You should have flashed a custom before flashing a kernel. Go into recovery by pressing back button on logo, go down to mounts and storage then mount USB. Then copy the rom over.
Sent from my XPERIA X8 using xda premium
new problem
new problem now restored the stock kernel uploaded the gingerdx than i put the new kernel (alfs08 no_fps_cap) and its stuck on infinity loop and GingerDX logo ..... I tried to wipe the cache from xrecovery but still the same
lol
NIMBAH said:
Relock your bootloader and try unlocking again with Setool2. That should give you signal back but not sure as I can't really remember .
You should have flashed a custom before flashing a kernel. Go into recovery by pressing back button on logo, go down to mounts and storage then mount USB. Then copy the rom over.
Sent from my XPERIA X8 using xda premium
Click to expand...
Click to collapse
I have no intentions to pay for this tool setool2 moreover i uplaoded the kernel and the rom successfully but the problem is no taht i am stuck at infinity loop on GingerDX logo... :X
I will be really glad if someone can help i managed to put new kernel , rom and now i am stuck with infinity boot loop :X:X:X:
Try install back the stock 2.1 eclair with stock kernel and do everything again, use SEUS.
new problem now i restored the bootloader relocked it now ito nly vibrates and nothing happens it tursn off and i can enter in flash mode only. But i cant restore stock kernel icant do anything after i relocked the bootloader
EDIT:
I restored flash kernel but i want new kernel adn when i unlock bootloader there is nos ignal :X:X:
That's not a surprise. Since Alfs has a built-in recovery You should enter to it, then do wipe data / factory reset and then flash ROM using install zip from sd card. Because You had installed ROM before and didn't wipe data - that's why it stuck and it's bootlooping.
Bolussimo said:
That's not a surprise. Since Alfs has a built-in recovery You should enter to it, then do wipe data / factory reset and then flash ROM using install zip from sd card. Because You had installed ROM before and didn't wipe data - that's why it stuck and it's bootlooping.
Click to expand...
Click to collapse
New problem mate when i unlock the bootloader i have no signal i put alfs kernel gingerdx runs normally but no signal . I relock the bootloader and than the phone cant boot and i must restore the old kernel:X
Did You check what type of Simlock Certificate is in Your x8 using s1tool? Cause there shouldn't be any problem with signal when it's SEMC... I suppose it's "not recognized simlock certificate" in Your case.
did you try unlock with flashtools? i read somewhere that some people with your same problem works fine with flashtools
Related
Hi guys, I'm having trouble with new ROM installation. I've been using Gingercruzt ROM since last spring with stock kernel. Bootloader is not unlocked, I've only rooted the phone. It's been working fine until I decided that I want to try something new today. I downloaded the GingerDX rom and installed it with CWM. Everything went fine and I rebooted the system. The phone didn't start, it got stuck on the SE logo. I couldn't enter CWM or xRecovery anymore. It bricked. Using SEUS I brought back the stock rom. I rooted the phone again, installed newer version of CWM from the toolkit, etc. I downloaded the zip again, installed it again - it bricked the phone the same way. Then I tried with two different roms - FroyoPro and Free Dom experience with full wipes on everything before installing - same thing, doesn't start. I was able to enter xRecovery with FroyoPro but no CWM and it get stuck at rom's loading screen.
Help please, what happened to my phone Why doesn't it load a ROM like it did yesterday?
Thanks in advance!
vgaBG said:
Hi guys, I'm having trouble with new ROM installation. I've been using Gingercruzt ROM since last spring with stock kernel. Bootloader is not unlocked, I've only rooted the phone. It's been working fine until I decided that I want to try something new today. I downloaded the GingerDX rom and installed it with CWM. Everything went fine and I rebooted the system. The phone didn't start, it got stuck on the SE logo. I couldn't enter CWM or xRecovery anymore. It bricked. Using SEUS I brought back the stock rom. I rooted the phone again, installed newer version of CWM from the toolkit, etc. I downloaded the zip again, installed it again - it bricked the phone the same way. Then I tried with two different roms - FroyoPro and Free Dom experience with full wipes on everything before installing - same thing, doesn't start. I was able to enter xRecovery with FroyoPro but no CWM and it get stuck at rom's loading screen.
Help please, what happened to my phone Why doesn't it load a ROM like it did yesterday?
Thanks in advance!
Click to expand...
Click to collapse
Did u cleared 'dalvik-cache' in case of froyopro & when u are stuck at 'Sony Ericsson' logo did u checked that u have downloaded thi Rom zip for 'stock kernel' I think this the problem download zip for stock kernel
Hit thanks if this helped u
sent from my W8 using client-server technology
Yes, I cleared all the possible caches, system and other folders. I even formated my sd card, just in case...
I downloaded all the right roms for stock kernel, all three of them. As I said, I've done this before and it worked from first try.
Thanks for trying to help me!
vgaBG said:
Yes, I cleared all the possible caches, system and other folders. I even formated my sd card, just in case...
I downloaded all the right roms for stock kernel, all three of them. As I said, I've done this before and it worked from first try.
Thanks for trying to help me!
Click to expand...
Click to collapse
You should not format /system, cause you are actually removing recovery+rom
& are you sure that froyopro supports stock kernel?
Sent from my ULTIMATE using Tapatalk 2
jay-z-s said:
You should not format /system, cause you are actually removing recovery+rom
& are you sure that froyopro supports stock kernel?
Sent from my ULTIMATE using Tapatalk 2
Click to expand...
Click to collapse
yup froyopro support stock
vgaBG said:
Yes, I cleared all the possible caches, system and other folders. I even formated my sd card, just in case...
I downloaded all the right roms for stock kernel, all three of them. As I said, I've done this before and it worked from first try.
Thanks for trying to help me!
Click to expand...
Click to collapse
Then don't format /system
sent from my W8 using client-server technology
try to redownload the rom. flash it again after a full wipe, then reboot.
signature under repair
I cleared the system folder before flashing a new ROM just to make sure I have deleted the stock ROM.
I tried with three different new ROMs, none of them started. Strange thing... everything goes well with the install and then it just won't turn on.
Do you think it's going to be different If I try to unlock the bootloader and flash nAa's kernel? I don't really want to do that but the phone is manufactured before the 29th week so it's capable.
are you sure it doesnt turn on?,first boot may take some minutes...
Yeah, I know, I've left it for more than 15 minutes with any of the tried roms.
I think I should write down the steps I'm taking after the flash back to stock rom with SEUS.
1. Activating debugging mode and unknown applications.
2. I already have the Android SDK, adb server and drivers from before so I open SuperOneClick and root the phone. Busybox is installed and Superuser is on. Everything goes smoothly during the process.
3. Using x8toolkit I install xRecovery and CWM via Dualrecovery.
4. Reset and entering CWM. Full wipe, install from zip, installation goes without problems and says - Go on buddy, restart and start using
5. Reset, Sony Ericsson logo and that's it. Nothing more happens. With GingerDX and Free Dom experience I can't enter recovery any more. FroyoPro's starting screen shows up after the SE logo but that's all it does - it never goes any further. I can enter xRecovery but no CWM.
I tried installing roms with both xRecovery and CWM - all the same. Could it be some physical damage even though the stock rom runs perfectly well? I don't know, I'm a bit desperate as the battery lasts half a day with the stock rom.
Just to end this thread, nothing worked for me so I unlocked the bootloader, flashed nAa's kernel and got a new ROM compatible with it - it works like a charm now. Thanks for your support guys!
So , i rooted my X8 yesterday and then installed CWM. Everything went fine (I was following tutorials made here - awesome work by the way)
then when i loaded 3 custom roms , i went to CWM made a backup , formated cache , data , system and then when i tried installing them i got the error 7. ive seen that its a common error. So after that , i couldnt load the phone and it was stuck in "Sony Ericsson" screen forever. couldnt load CWM aswell. Then i flashed the original ftf and it booted normally. rooted again and installed CWM. Next thing , i flashed 2.6.29.6-nAa-jb-03 Custom jb kernel. Everything went fine , then i formated data , cache and system. But when i tried to load the Roms it couldnt mount sd card.
So now i can neither install a rom nor restore the phone.
Can someone help me ?
(by the way , phone stays at nAa Freedom Within screen. or the CWM )
What's the point in flashing that kernel?
Sent from my E16i using Tapatalk 2
XPERIAnced said:
So , i rooted my X8 yesterday and then installed CWM. Everything went fine (I was following tutorials made here - awesome work by the way)
then when i loaded 3 custom roms , i went to CWM made a backup , formated cache , data , system and then when i tried installing them i got the error 7. ive seen that its a common error. So after that , i couldnt load the phone and it was stuck in "Sony Ericsson" screen forever. couldnt load CWM aswell. Then i flashed the original ftf and it booted normally. rooted again and installed CWM. Next thing , i flashed 2.6.29.6-nAa-jb-03 Custom jb kernel. Everything went fine , then i formated data , cache and system. But when i tried to load the Roms it couldnt mount sd card.
So now i can neither install a rom nor restore the phone.
Can someone help me ?
(by the way , phone stays at nAa Freedom Within screen. or the CWM )
Click to expand...
Click to collapse
re insert the sd card, i too have experienced this problem many times, try it mate
Okay , so i tried inserting it again and again. nothing really changed.
Gogeta to be honest , im a total newb @ these things i just started readin about custom roms rooting e.t.c
So , can you tell me why i didnt need to flash that kernel?
i mean i wanted to instal MiniCM10 and the requiremenents were these
Requirements:
Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: M76XX-TSNCJOLYM-53404015
Unlocked bootloader
Latest version of the 2.6.32 nAa JB kernel
latest not old, naa05 is the latest
Sent from my katana with a sharpness over 9000!
Oh , so that would be the problem right?
How do i fix this? i need to flash the original tft then root again - install recovery - unlock using s1tool and then flash the latest nAa?
Thank you by the way.
you can enter recovery so you can flash the new version by wiping data cache and system, but first, is your sd card formatted? format it first to avoid those problems
Sent from my katana with a sharpness over 9000!
XPERIAnced said:
Okay , so i tried inserting it again and again. nothing really changed.
Gogeta to be honest , im a total newb @ these things i just started readin about custom roms rooting e.t.c
So , can you tell me why i didnt need to flash that kernel?
i mean i wanted to instal MiniCM10 and the requiremenents were these
Requirements:
Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: M76XX-TSNCJOLYM-53404015
Unlocked bootloader
Latest version of the 2.6.32 nAa JB kernel
Click to expand...
Click to collapse
You said it yourself, its .32 kernel not .29 which u flashed
XPERIAnced said:
Oh , so that would be the problem right?
How do i fix this? i need to flash the original tft then root again - install recovery - unlock using s1tool and then flash the latest nAa?
Thank you by the way.
Click to expand...
Click to collapse
Just flash the latest 2.6.32 nAa jb ftf
sent from your device using Facebook app :screwy:
i tried flashing the latest but i get an error 995 it also says that i need to install the drivers for the device and the flashtool but they are already installed
- EDIT.
It works. thank you very much everyone, i just flashed one more time and it worked. its really amazing.
One last thing. whats that zip with google apps? should i install it too ?
yeah you should after installing the rom, good luck!
Sent from my katana with a sharpness over 9000!
Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers
Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk
Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!
Helo , im using Xperia Z C6603 with locked bootloader.
Now im using .292 UK official rom with root and XZ-lockeddualrecovery 2.8.3
After flashing any rom like Criskelo or Existen, my Xperia never boot up. I see only Sony logo and then black screen, and recovery doesnt work even when i flash it again after rom. Can any one help me ? What i do wrong.
I allways make full wipe before install rom.
OmenHTX said:
Helo , im using Xperia Z C6603 with locked bootloader.
Now im using .292 UK official rom with root and XZ-lockeddualrecovery 2.8.3
After flashing any rom like Criskelo or Existen, my Xperia never boot up. I see only Sony logo and then black screen, and recovery doesnt work even when i flash it again after rom. Can any one help me ? What i do wrong.
I allways make full wipe before install rom.
Click to expand...
Click to collapse
Actually, you can't boot on custom rom with locked bootloader, therefore you might brick your device if you'll keep trying to flash custom roms on your phone.
Firstly, you've to unlock your Bootloader if you want to use any custom rom (unlocking bootloader will lead you to DRM keys and its functions remove, with TA Partition backup you'll be able to recover it).
i solwed my problem, i just cant wipe system partition ... so i install custom rom, then make factory reset and its works!
hi guys ,so this is the story:starting with stock xxx.1.A.1.2xx (cant remember)
1.i rooted withe towelroot............ sucess
2:then unlocked BL with sony's guide ............success
3.installed recovery 'CWM_SP_4.4.1' ,every thing was normal until i flashed VANIR rom,the rom didn't flash
i waited 20min the turned the phone off
tryed again nothing
tryed with another kernel and recovery and same happened
finally i tryed another rom AOSPA kitkat and the same boot loops
Q:did i damage anything by turning phone off during the install
Q:What to do!!
taha1994 said:
hi guys ,so this is the story:starting with stock xxx.1.A.1.2xx (cant remember)
Q:did i damage anything by turning phone off during the install
Q:What to do!!
Click to expand...
Click to collapse
1.You actually did!:laugh:
2.Flash stock ftf and start over
Btw I dont think you have successfully unlocked your bootloader. Check it. Use flashtools it is million times easier.
i think you'r right
i flashed a stock signed rom (using TWRP) and it is back on
i will try flashtool unlocking
THANKS