hey guys please please help i had the custom rom pac nightly now here is where the sh*t went down, i tried to put on carbon and flashed the kernel with that and since then im unable to get back root i have locked the bootloader and tried unlocked the bootloader, the screen comes up to the point where the rom loads and the lil vibrate happens, and then pufff it just goes back to the boot up and then again and again !!! how can i fix this please help
Flash a boot.img with recovery and reflash.
Sent from my Z Ultra
LordManhattan said:
Flash a boot.img with recovery and reflash.
Sent from my Z Ultra
Click to expand...
Click to collapse
thanks buddy for the response but tried it and wont work !!!
Is your bootloader unlocked at the moment?
It should work as lordmanhattan said.
Flash boot.img from carbon
Flash carbon from recovery.
You could start over and flash new ftf then do the above instructions...
Sent from CarbonROM on my Z-Ultra
blueether said:
Is your bootloader unlocked at the moment?
It should work as lordmanhattan said.
Flash boot.img from carbon
Flash carbon from recovery.
You could start over and flash new ftf then do the above instructions...
Sent from CarbonROM on my Z-Ultra
Click to expand...
Click to collapse
yes bootloader is unlocked
sorry i know im being tedious but just to re check ...
1. flash ftf (my zu is from HK so the latest is .681 ftf)
2. then fash the boot.img from carbon
3. then flash carbon onto my phone
in this order you reckon it would fix my problem?
(going ahead and giving it a try anyways in the above order lets see if it pans out)
ashankanand said:
yes bootloader is unlocked
sorry i know im being tedious but just to re check ...
1. flash ftf (my zu is from HK so the latest is .681 ftf)
2. then fash the boot.img from carbon
3. then flash carbon onto my phone
in this order you reckon it would fix my problem?
(going ahead and giving it a try anyways in the above order lets see if it pans out)
Click to expand...
Click to collapse
As you seem to be having issues I would go back to stock and satrt again, and the steps above should do just that for you. I would boot up after the first step just to check that everything is upto speed on the phone.
I wouldn't worry about getting a HK firmware, just use any of the unbranded/generic US/EU 757 FTFs
I cant see why it didn't work straight from PAC , hell the kernel in Carbon boots the latest PAC just fine
blueether said:
As you seem to be having issues I would go back to stock and satrt again, and the steps above should do just that for you. I would boot up after the first step just to check that everything is upto speed on the phone.
I wouldn't worry about getting a HK firmware, just use any of the unbranded/generic US/EU 757 FTFs
I cant see why it didn't work straight from PAC , hell the kernel in Carbon boots the latest PAC just fine
Click to expand...
Click to collapse
ok bud tired it now the problem is the dam phone keeps going into recovery boots and gets stuck on sony and then reboots and goes into recovery any advice!!!
Flash a stock tft with flashtool in flashmode and it should work again.
Anyways flashing the kernel with the boot.img in fastboot mode should work.
Have tried that flashed the latest ftf. Then used the root guide didn't work used the boot.img from carbon from pac rom. Still just reboots , my issue is I want a custom rom cos I'm happier with a custom rom, so I get root on the stock. But I can't seem to load a custom rom, first it was midway boot now it's recovery reboots , I want a custom rom any advice .
Sent from my C6833 using XDA Free mobile app
ashankanand said:
Have tried that flashed the latest ftf. Then used the root guide didn't work used the boot.img from carbon from pac rom. Still just reboots , my issue is I want a custom rom cos I'm happier with a custom rom, so I get root on the stock. But I can't seem to load a custom rom, first it was midway boot now it's recovery reboots , I want a custom rom any advice .
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
Do it like this:
- flash boot.img (flashtool: fastboot mode)
- wipe cache/dalvik cache (CWM Recovery)
- flash the ROM[.zip] (CWM Recovery)
- flash the GAPPS[.zip] (CWM Recovery)
- reboot
That should work.
I mean flashed ftf , fastbooted boot.img from carbon, had recovery reboots (meaning the phone would boot up stuck on Sony logo and then reboot into recovery ) then tried pac rom boot.img no help, infact flashed ftf cleard cache and data and then flashed boot.img flashed rom , had same recovery issue, then tried a full wipe, (ofcourse flashed ftf again) I mean went into mount storage and formated cache data system etc etc, now I'm really baffeld I have tried everything I find myself getting everything to work except putting the custom rom someone help
Sent from my C6833 using XDA Free mobile app
ashankanand said:
I mean flashed ftf , fastbooted boot.img from carbon, had recovery reboots (meaning the phone would boot up stuck on Sony logo and then reboot into recovery ) then tried pac rom boot.img no help, infact flashed ftf cleard cache and data and then flashed boot.img flashed rom , had same recovery issue, then tried a full wipe, (ofcourse flashed ftf again) I mean went into mount storage and formated cache data system etc etc, now I'm really baffeld I have tried everything I find myself getting everything to work except putting the custom rom someone help
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
You forgot to flash the rom itself. Just flashing the kernel (boot.img) doesn't to anything instead of flashing
the kernel. You need to flash the ROM to have working Operation System. That's why just the logo shows
up and goes into recovery. Put the ROM (the .zip file of the rom) on your SD Card and go into recovery
and go to "install .zip" and choose your file. After that the ROM should be loading after Boot Logo. Don't forget
to flash the GAPPS after flashing rom.
Pacman Rom: www.blownco.com/index.php/doc_download/13688-pac-togari-4-3-build-1-20131214-044914
Pacman Gapps: www.blownco.com/index.php/doc_download/13604-gapps-jb-20130813-signed
here is an example for installing the rom and gapps:
https://www.youtube.com/watch?v=n0In32vjxIg&feature=player_embedded
Just do the same with your files.
Flashed the rom buddy , every time ofcourse I thought I didn't need to mention that hehe ,
Sent from my C6833 using XDA Free mobile app
ashankanand said:
Flashed the rom buddy , every time ofcourse I thought I didn't need to mention that hehe ,
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
I was wondering man. Can you provide us with a link of the rom you want to use.
tr0teK said:
I was wondering man. Can you provide us with a link of the rom you want to use.
Click to expand...
Click to collapse
carbon rom : http://forum.xda-developers.com/devdb/project/dl/?id=5119
Pac-rom : http://pacman.basketbuild.com/download.php?file=main/togari/nightly/pac_togari-nightly-20140505.zip
How to reproduce your error step by step ?
tr0teK said:
How to reproduce your error step by step ?
Click to expand...
Click to collapse
ok not so clear on what you are asking but here goes
had a c6802 cracked the screen (using carbon rom on it loved it) bought a c6833 wanted to try pac rom put it on realized my batt consumption is way too high so tried to switch back to carbon now, while doing so i flashed carbon rom Double tap to wake and carbon kernel, here started the spiral, first few hours couldn get any thing to work read up looked up a few of the forum, and ftf fashed the generic hk rom things got ok, but then root was the issue so found out the root method, fastboot .img and flash cmw supersu.zip, all fine and dandy didnt mess with it in anyway
since then as i have explained im gettin a recovery loop even when i flash the stock rom (cmw flash not ftf) so now i have the latest stock rom with root but i have sony's stock i want a rock in which i can add a menu button and change the dip and everything doesnt crash if you know what i mean....
ashankanand said:
ok not so clear on what you are asking but here goes
had a c6802 cracked the screen (using carbon rom on it loved it) bought a c6833 wanted to try pac rom put it on realized my batt consumption is way too high so tried to switch back to carbon now, while doing so i flashed carbon rom Double tap to wake and carbon kernel, here started the spiral, first few hours couldn get any thing to work read up looked up a few of the forum, and ftf fashed the generic hk rom things got ok, but then root was the issue so found out the root method, fastboot .img and flash cmw supersu.zip, all fine and dandy didnt mess with it in anyway
since then as i have explained im gettin a recovery loop even when i flash the stock rom (cmw flash not ftf) so now i have the latest stock rom with root but i have sony's stock i want a rock in which i can add a menu button and change the dip and everything doesnt crash if you know what i mean....
Click to expand...
Click to collapse
maybe the solution for you would be too install xposed framework which gives you the features you want. It allows your to "modify" your stock rom like the advanced power button menu, editing the navigation and status bar and stuff like that.
http://repo.xposed.info/module/de.robv.android.xposed.installer
you obviously need ROOT for this.
tr0teK said:
maybe the solution for you would be too install xposed framework which gives you the features you want. It allows your to "modify" your stock rom like the advanced power button menu, editing the navigation and status bar and stuff like that.
http://repo.xposed.info/module/de.robv.android.xposed.installer
you obviously need ROOT for this.
Click to expand...
Click to collapse
so yeah not to be a buzz killl buddy i know i am here asking for help and i really appreciate it but i tried that and gives me system ui errors cos i would have been ok with xposed but its not working great especially the special xposed for xperia cos the generic xposed is not workin anyway
ashankanand said:
so yeah not to be a buzz killl buddy i know i am here asking for help and i really appreciate it but i tried that and gives me system ui errors cos i would have been ok with xposed but its not working great especially the special xposed for xperia cos the generic xposed is not workin anyway
Click to expand...
Click to collapse
Which ROM do you have installed exactly ? In which country do you live ?
Related
hi all!
after successfully flashing and rooting my neo v i started trying these excellent roms of XDA developers.
so, with locked BL, after installing XPERIA Ultimate HD and Zelly Bean i went for a try on Ice Cream pureness v14.
i guess my mistake was that after a full wipe from CWM i installed the ROM, the neo v patch and the upgrade without any reboot but the last one.
anyway, i am stuck on a bootloop now
can't access CWM (i guess because of system format....(?))
i flashed stock rom with flashtool but still nothing
i am searching for hours to avoid posting such an embarrassing "first post" but i really can't find a solution
thanx in advance!
EDIT : Just managed to recover the phone using Sony Ericsson update service software, turning it back to 4.0.4 stock. So i am going again for root etc. I guess there should be an easier way so if anybody knows it please share.
and if any admin could fix that "rootloop" in the title....
cheers!
Yes, there is an easier way. Unlock your phone bootloader with one of two methods. I would choose testpoint method.
Just some tips: When you flash zip, always do wipe cache/data (don't wipe system like someone does), check that it is for locked bootloader, for Neo V not L or Neo etc. I never had those problems. Anyway, I don't see advantage of those ROMs on locked bootloader except of removing bloatware, which you can do by yourself.
And it is called bootloop not rootloop.
ReznorNInchNails said:
Yes, there is an easier way. Unlock your phone bootloader with one of two methods. I would choose testpoint method.
Just some tips: When you flash zip, always do wipe cache/data (don't wipe system like someone does), check that it is for locked bootloader, for Neo V not L or Neo etc. I never had those problems. Anyway, I don't see advantage of those ROMs on locked bootloader except of removing bloatware, which you can do by yourself.
And it is called bootloop not rootloop.
Click to expand...
Click to collapse
Good one bro.. People should learn to help.. Like you did here.. :thumbup:
Sent from my MT11i using xda premium
ReznorNInchNails said:
Yes, there is an easier way. Unlock your phone bootloader with one of two methods. I would choose testpoint method.
Just some tips: When you flash zip, always do wipe cache/data (don't wipe system like someone does), check that it is for locked bootloader, for Neo V not L or Neo etc. I never had those problems. Anyway, I don't see advantage of those ROMs on locked bootloader except of removing bloatware, which you can do by yourself.
And it is called bootloop not rootloop.
Click to expand...
Click to collapse
Thanx for tips! I am quite new to all this so I thought unlocked bl would come at the next level. I guess I might go for it sooner.
I know about the rootloop mistake that's why I asked for a correction
Cheers
I feel like a noob again. My (rooted, bootloader unlocked, custom rom) Neo V is stucked at bootloop. I tried flashing a stock kernel and it just stucked at the Sony logo, Then I flashed a custom kernel and it only light up the screen and nothing happen. Really need help...
I was trying to flash a custom rom and it was telling me to wipe battery stat and cache in advance option
Gemichi said:
I feel like a noob again. My (rooted, bootloader unlocked, custom rom) Neo V is stucked at bootloop. I tried flashing a stock kernel and it just stucked at the Sony logo, Then I flashed a custom kernel and it only light up the screen and nothing happen. Really need help...
I was trying to flash a custom rom and it was telling me to wipe battery stat and cache in advance option
Click to expand...
Click to collapse
Just flash stock ftf file using flashtool.. Next time read the instructions properly before flashing..
Sent from my Xperia Neo V using xda premium
vishal_android freak said:
Just flash stock ftf file using flashtool.. Next time read the instructions properly before flashing..
Sent from my Xperia Neo V using xda premium
Click to expand...
Click to collapse
Ok, I flashed the .ftf and I was able to get into CWM, but when I go back and download the stable cm9 from Cyangenmod, It shows status 7 when flashing...
every rom I try to flash, I get status 7, I tried edit the "updater-script" and it just show installation aborted right away.
Flash kernel first and then ROM
Sent from my Xperia Neo V
Gemichi said:
Ok, I flashed the .ftf and I was able to get into CWM, but when I go back and download the stable cm9 from Cyangenmod, It shows status 7 when flashing...
every rom I try to flash, I get status 7, I tried edit the "updater-script" and it just show installation aborted right away.
Click to expand...
Click to collapse
Let me clarify this to you first,
CM doesn't work on Locked Bootloader.
So if you're having locked bootloader, there is one way to fix this:
Reflash ICS .ftf & do the whole rooting, installing CWM Recovery procedure again. Go to recovery & install the ROM with instructions stated in ROM thread.
If you have unlocked the bootloader, two ways to solve this problem:
1. Flash any other ICS kernel. Go to recovery, wipe everything except SDCard of course xD
Then power off the phone & flash kernel from CM9 zip. Install CM9.
2. If above doesn't fix the problem, reflash the ICS .ftf again. Flash CM9 kernel & install the zip usual way.
Cheers!
ak070
ak070 said:
Let me clarify this to you first,
CM doesn't work on Locked Bootloader.
So if you're having locked bootloader, there is one way to fix this:
Reflash ICS .ftf & do the whole rooting, installing CWM Recovery procedure again. Go to recovery & install the ROM with instructions stated in ROM thread.
If you have unlocked the bootloader, two ways to solve this problem:
1. Flash any other ICS kernel. Go to recovery, wipe everything except SDCard of course xD
Then power off the phone & flash kernel from CM9 zip. Install CM9.
2. If above doesn't fix the problem, reflash the ICS .ftf again. Flash CM9 kernel & install the zip usual way.
Cheers!
ak070
Click to expand...
Click to collapse
I have unlocked my bootloader lol. Finally I got it back to normal now. I flashed the stock ftf, then update it to a newer firmware to root it. Flash CWM, Follow the instruction on how to flash cm10 (I use cm9) and everything is fine now, but I still want to flash other custom rom...
@Gemichi
If your Bootloader unlocked,you dont need install CWM or root your phone...
What you have to do is just flash kernel which have built-in CWM.
I advice you read again how to flash kernel,I see your post you install CWM,from that I know your bootloader NOT unlocked
Sent from my Xperia Neo V
megatpanji said:
@Gemichi
If your Bootloader unlocked,you dont need install CWM or root your phone...
What you have to do is just flash kernel which have built-in CWM.
I advice you read again how to flash kernel,I see your post you install CWM,from that I know your bootloader NOT unlocked
Sent from my Xperia Neo V
Click to expand...
Click to collapse
Ok I got it back to normal now, got CWM, flashed cutsom rom. Thanks
I'm having troubles when i wan't to install this ROM :
http://forum.xda-developers.com/showthread.php?t=2555350 .
I'm using the dl from the first post, i'm using fastboot flash boot boot.img (the boot.img i'm getting from the zip-file).
I do a factory reset from the bootloader, then i do a factory reset in the twrp recovery
then i flash the boot.img in the jb hboot 1.25.0002
then i flash the zip file and i reboot.
but i never get to see the boot image. just a black screen...
Can someone help me?
tcornelis said:
I'm having troubles when i wan't to install this ROM :
http://forum.xda-developers.com/showthread.php?t=2555350 .
I'm using the dl from the first post, i'm using fastboot flash boot boot.img (the boot.img i'm getting from the zip-file).
I do a factory reset from the bootloader, then i do a factory reset in the twrp recovery
then i flash the boot.img in the jb hboot 1.25.0002
then i flash the zip file and i reboot.
but i never get to see the boot image. just a black screen...
Can someone help me?
Click to expand...
Click to collapse
You're definitely using a TWRP recovery made for JB hboot? @GtrCraft, did you put the right boot.img inside the zip?
Also, you can try flashing a custom JB kernel of your choice.
@dansou901 I believe so, flashing this (http://forum.xda-developers.com/showthread.php?t=2344254) work like a charm (except for the rom that hasn't got any wifi, ...)
How can i check to be sure?
tcornelis said:
@dansou901 I believe so, flashing this (http://forum.xda-developers.com/showthread.php?t=2344254) work like a charm (except for the rom that hasn't got any wifi, ...)
How can i check to be sure?
Click to expand...
Click to collapse
For booting that ROM a CM kernel is needed. As you have installed one (if it works like you said), you need to install a JB Sense kernel (just pick one from Original Android Development section). Then reinstall SuperSense and you should be fine.
I'll give that a go and let you know
@dansou901 , i've used this boot.img (http://forum.xda-developers.com/showthread.php?t=2337389) because i've already been able to flash that rom as well.
but now i can't seem to get rid of my previous custom rom. i've done a factory reset, i wiped everything there is to wipe, i've flashed the above boot.img and supersense but it's still another custom rom on my device :s
tcornelis said:
@dansou901 , i've used this boot.img (http://forum.xda-developers.com/showthread.php?t=2337389) because i've already been able to flash that rom as well.
but now i can't seem to get rid of my previous custom rom. i've done a factory reset, i wiped everything there is to wipe, i've flashed the above boot.img and supersense but it's still another custom rom on my device :s
Click to expand...
Click to collapse
That's a CM kernel as well. I told you to use a Sense kernel. Use this one for example: http://forum.xda-developers.com/showthread.php?t=2483489
and your recovery should work again as expected. Btw, which recovery did you install? Please give the link.
this is the twrp recovery.img http: // teamw . in / project / twrp2 / 140 (yeah, can't post outside links yet)
i'll give that one a shot
tcornelis said:
this is the twrp recovery.img http: // teamw . in / project / twrp2 / 140 (yeah, can't post outside links yet)
i'll give that one a shot
Click to expand...
Click to collapse
That one's made for ICS, if I recall correctly... Don't use it. Use this one instead: http://forum.xda-developers.com/showthread.php?t=2099513 But be sure to use a JB version.
After changing my recovery, finally i was able to flash the custom rom. I used the boot.img you gave me, but is that going to affect some of the features in the rom?
And i would like to thank you allready
tcornelis said:
After changing my recovery, finally i was able to flash the custom rom. I used the boot.img you gave me, but is that going to affect some of the features in the rom?
And i would like to thank you allready
Click to expand...
Click to collapse
No, it's not. You can however choose the kernel yourself as I said... But keep in mind that it has to be a JB Sense kernel (just read the OP of the kernel thread carefully, then you'll know). For recoveries, keep this in mind.
No Title Here
The boot.img in the SuperSENSE-dx5 zip is stock, every JB Sense kernel should work though
GtrCraft said:
The boot.img in the SuperSENSE-dx5 zip is stock, every JB Sense kernel should work though
Click to expand...
Click to collapse
His problem wasn't the kernel but the wrong recovery he used, it's fixed now.
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
His problem wasn't the kernel but the wrong recovery he used, it's fixed now.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect :good:
Hi, i'm new in these things so have a few questions.
Iwould like to flah thecyanogenmod but my galax 2s syas it is not a gt-I9100.
So i read some things about removing the assert line from a script and so on.
Do i need to flah an older rom before the cm11 nightly?
Do i need to flash the kernel first? or just use the latest cwm? (or rom manager/clockword?)
Can i reflash the S2 with an cyanogenmod kitkat version after i flashed it with an other kitkat rom for this device?
(still i did not succed to flash any rom to it)
thanks for any help !
JJSJJS said:
Hi, i'm new in these things so have a few questions.
Iwould like to flah thecyanogenmod but my galax 2s syas it is not a gt-I9100.
So i read some things about removing the assert line from a script and so on.
Do i need to flah an older rom before the cm11 nightly?
Do i need to flash the kernel first? or just use the latest cwm? (or rom manager/clockword?)
Can i reflash the S2 with an cyanogenmod kitkat version after i flashed it with an other kitkat rom for this device?
(still i did not succed to flash any rom to it)
thanks for any help !
Click to expand...
Click to collapse
First of all check if it g version or not.
To best of my understanding you can install it directly as far as you are rooted.
Sent from my GT-I9100 using xda premium
You don't need to flash an older version before KK. You just need KK compatible recovery. Or you can flash a KK compatible kernel, reboot to recovery and flash your KK rom.
Hello, thank you both for your replies.
Finally some clear answers
The model says GT-I9100 and not with g behind it, thanks.
I found some things about the status 7 error and about removing some line in a script in the zip.
So i will try the kitkat recovery (in my understanding this is also the kernel?) and then flash it with kitkat rom.
I would like to flash the one from cyangenmod, but doe it really mather which custom kitkat rom i take? At least they are all without the providers code like Vodafone or others?
Thanks again. I will update the thread if it succeeds or not.
Hi,
so i could not install the latest Recovery_CWM_6.0.4.7_I9100.zip as it gave an error E: signature verification failed.
then i tried recovery-clockwork-touch-5.8.1.5-galaxys2.zip and this works. But with this i can't install CM11. as i get the status 7 error.
So i will try some other versions kitkat compatible.
I also took a look at the kernels section but it is not clear wich one to use for CWM6 as i don't know what XXLSR or DDLS3 means, and which is correct for Netherlands.
Do you have any idea? (i am not allowed to post there yet)
Thanks for your help.
For choice of kernel -
1. Gustavo's - I don't remember the version. Check the op.
2. Dorimanx - you can try 10.43v100.
3. Apollo - 7.0b Cm
They will bring the KK compatible recovery you want on your phone. Then after rebooting to recovery you can flash any custom rom as they are not locked by any carriers.
banjara said:
For choice of kernel -
1. Gustavo's - I don't remember the version. Check the op.
2. Dorimanx - you can try 10.43v100.
3. Apollo - 7.0b Cm
They will bring the KK compatible recovery you want on your phone. Then after rebooting to recovery you can flash any custom rom as they are not locked by any carriers.
Click to expand...
Click to collapse
Thank you very much Banjara !
i'll keep trying, will report if i succeed
oh oh no good.....
JJSJJS said:
Thank you very much Banjara !
i'll keep trying, will report if i succeed
Click to expand...
Click to collapse
oh boy oh boy
i followed this http://forum.xda-developers.com/galaxy-s2/development/kernel-lazing-safe-stock-kernels-t2293576
and now it is stuck on boot screen, can't even reboot in recovery mode to get the back rom back pfffff
what should i do now......even the usb cable aint working, i'm flashing to the external sdcard via an other phone and the replace the sdcard to the galaxy s2
thanks for any help :crying::crying::crying::crying::crying:
JJSJJS said:
oh boy oh boy
i followed this http://forum.xda-developers.com/galaxy-s2/development/kernel-lazing-safe-stock-kernels-t2293576
and now it is stuck on boot screen, can't even reboot in recovery mode to get the back rom back pfffff
what should i do now......even the usb cable aint working, i'm flashing to the external sdcard via an other phone and the replace the sdcard to the galaxy s2
thanks for any help :crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
If you are able to go back to download mode
1. Flash a stock rom via odin
2. Flash a custom kernel via Odin. You might find some in the link you put there or you can search for hirox kernel. Remember, you have to download Odin flash able kernel and follow the op.
3. Once you have custom kernel, reboot to recovery. Flash any of the kernels in clockworkmod mentioned in my previous post.
4. Reboot to recovery. Flash your rom.
If you are unable to go to download mode try all the methods mentioned in the below link to bring it back to normal. It will need patience and perseverance. http://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
Thank you for your patience and your help Banjara.
This forum and it's people are 100 times better the on Gyanomed were totally no support is given...
I will try it and come back, at least the phone able to start in the download mode.
Probably the usb connector has some loose contacts as i can get no contact with pc.
I got this phone from my brother and he told me that it never worked, just loading the battery
So i tried an other cable from an cheap android pad, but also no luck
maybe tommorow, i have another cable from an android stick pc at my job, maybe it will work
else i have to open it to check the connector under a microscope and probably resolder(hotair) it with a lot of flux... what a pitty... :crying:
lucky i have some experience on it, i repaired a lot of qtek phone, some years ago, always that connector broken.
I'm originally an tv(crt,lcd,plasma) repair technician, but now on an other job
Pfew, i managed to rsolder the connector with help of the microscope on my job.
I could even connect to odin. so that's is good progression. i had a wrong kernel downloaded, so it failed.
now i have the correct one and will use Siyah-s2-v6.0b5.tar
But unfortunately the battery is really emptying quickly when it stays in the phone, i don't know why.
So i will have to charge it an then give it another try with this kernel.
The ROM should still be original as i did not flash it before, just the kernel.
The phone is now saying battery empty, can't download.
To be continued...
Jippieeee!
GREAT !!!!
It worked! flashed the kernel Siyah-s2-6.0b5 and it started ! :victory:
Now what is the best way to proceed, there are so many topics on this it is overwhelming.
Should i first flash a Kernel or first a rom?
Can i flash them right after each other? (kernel reboots) so ROM and directly Kernel in one go?
thanks for your help!
{SOLVED}
Ok this is solved, thank you guys and dolls !
i managed to flash the cwm 6++++ and then the OMNI kitkat (latest) and the gAPPs
and it is working ! i am verry happy ! :laugh::laugh::laugh::laugh::laugh:
:thumbup::beer::beer:
one more thing
i noticed there is also another kernel now in the phone.
How to get rid of the yellow exclamation mark?
i saw some footage on youtube how to do it with the correct kernel.
But can i also extract the kernel from the ROM.tar i used and flash it with Odin?
Or is there another way?
thanks for your help. ---> edit
ok found some here: http://forum.xda-developers.com/galaxy-s2/orig-development/30-10-2012-k-la-lp-t1103399
but is it also good enough to unroot your device or are some functionality's then lost when using OMNI- rom ?
Thanks for your help
there arent any funcions lost it just gives your phone informations so that it thinks its all fine and dont displays the yelow horror . Btw i used TWRP KK kernel on my gs2 and installed prerooted rom aosp neatrom 5.8 kk and dont have problems with triangle. Also neatrom 4.1.2 with extended battery life is there if you dont like kitkat =D
Radelos said:
there arent any funcions lost it just gives your phone informations so that it thinks its all fine and dont displays the yelow horror . Btw i used TWRP KK kernel on my gs2 and installed prerooted rom aosp neatrom 5.8 kk and dont have problems with triangle. Also neatrom 4.1.2 with extended battery life is there if you dont like kitkat =D
Click to expand...
Click to collapse
Thanks Radelos, then i will try to unroot it again. And that will be it then.
Now using the OmniKK nightly of 8th of june, it runs very smooth, no issues till now, all is working well. :good:
btw idk what is the exact rom your willing to use but for no triangle would also do an clean install of stock rom, then root with framroot that you can find here on site and then flash KK compatible recovery and ofc kk rom with it. Here is the rom i used, its prerooted and on first boot starts direct into recovery so its for lazy ppl =D factory format data/system then flash TWRP touch recovery and in cwm reboot recovery option. And then just flash rom
Rom
http://uloz.to/x13p4YVr/drhd-base-lpq-re-light-tar
KK TWRP touch recovery
http://uloz.to/xyw9UkTk/kk-kernel-21-04-twrp-zip
Radelos said:
btw idk what is the exact rom your willing to use but for no triangle would also do an clean install of stock rom, then root with framroot that you can find here on site and then flash KK compatible recovery and ofc kk rom with it. Here is the rom i used, its prerooted and on first boot starts direct into recovery so its for lazy ppl =D factory format data/system then flash TWRP touch recovery and in cwm reboot recovery option. And then just flash rom
Rom
http://uloz.to/x13p4YVr/drhd-base-lpq-re-light-tar
KK TWRP touch recovery
http://uloz.to/xyw9UkTk/kk-kernel-21-04-twrp-zip
Click to expand...
Click to collapse
So with this process, will there be no yellow triangle?
Right, I have a set of issues which all seem vaguely connected but I can't figure out how to resolve.
I've unlocked my bootloader and I've been messing about with recoveries and CM11 etc.
The situation however is that I installed doomkernel, got into CWM and installed CM11, all good.. went to go back into the recovery and it's gone, it just hangs if I try, no worries I thought I'll just reflash doomkernel, then the ROM doesn't boot so I have to reflash boot.img from the CM11 zip.
That kills the recovery again... rinse and repeat basically, it looks like I can't have CM11 and CWM which is a PITA.
Plenty of people in the CM11 thread seem to be having no issues with either retaining the recovery or using cyandelta, neither of which work for me and whilst CM11 is still in nightly I really need to be able to upgrade frequently.
Also, using flashtool to unlock the bootloader was fine but I can't flash a recovery from there as the option is greyed out on both CM11 and the stock ROM..
I'm lost, I've tried several combinations but I've also gone dangerously close to bricking the phone so I've backed off..
Can anyone give me any pointers?
The only thing I haven't done is download the ROM from the frexperia site as I can't make sense of which ROM I need, I can't see Z2 or Sirius mentioned anywhere and I've learned the painful way in the past not to flash the wrong ROM.
So now I'm back to the stock rooted ROM but there's a bunch of issues with it such as it loving switching the wifi on and off, proximity sensors thinking my face is my fingers, the useless lock screen etc etc.
HALP! Thanks all
Try this:
1 - install recovery.
2 - reboot into recovery.
3 - flash CM11, don't reboot.
4 - flash gapps, don't reboot.
5 - flash recovery & reboot.
Does this leave you with a recovery? There is an option to upgrade recovery in CM11 settings -> developer options -> update CM recovery. Try this and see what happens.
Sent from my SGP311 using XDA Free mobile app
I haven't been flashing the recovery from within CWM, in fact I'm not even sure you can with it being a kernel image as thats how Sony's work? If I flash the doomkernel again I know CM11 won't boot and sort of vice versa..
EDIT - Sorry I didn't see you had a Z2.. have you managed to pull this off? Any tips on a recovery flashable kernel?
mrmatt100 said:
I haven't been flashing the recovery from within CWM, in fact I'm not even sure you can with it being a kernel image as thats how Sony's work? If I flash the doomkernel again I know CM11 won't boot and sort of vice versa..
EDIT - Sorry I didn't see you had a Z2.. have you managed to pull this off? Any tips on a recovery flashable kernel?
Click to expand...
Click to collapse
Reintall stock. Skip Doom Kernel, directly fastboot CM boot.img. Flash CM in your now working recovery.
Thats what worked for me
Sent from my Xperia Z2 using Tapatalk
Sorry what do you mean by skin the kernel? I'm not a n00b but I've never heard that before?
but thanks for the help!
Myself5 said:
Reintall stock. Skin Doom Kernel, directly fastboot CM boot.img. Flash CM in your now working recovery.
Thats what worked for me
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
Still stuck on this, I do know I've got stock with doom kernel and I've fastboot flashed the CM boot.img from the CM11 nightly, that basically results in a phone that won't boot OR go into recovery.
Literally the only way I can get into CWM is by using doom kernel and the stock ROM (obviously rooted and using xposed etc if that makes a difference) and the moment I flash anything from within CWM it obviously overwrites the boot.img meaning I can boot normally but not with a working recovery.
I can't escape the feeling that I ought to be flashing a specific version perhaps from freexperia rather than the cyanogenmod website or I need a different kernel to kick the process off rather than doom kernel.
Very confusing and a real shame doom kernel only works with stock ROMs
Sorry the skin part was a spelling misstake. Should have been SKIP. I issued the same as you, my problem was somehow related to DoomKernel. So just Flash Stock now (using a ftf in flashtool) and then straight the boot.img from the CM zip. Now boot in the recovery (press vol down when the Amber led lights up at the boot process) and flash the CM zip in this recovery (wipe data/Factory reset and format /system before ofc (least that what I would recommend)). Flash Gapps if you whish. Reboot to your now working CM install.
Sent from my Xperia Z2 using Tapatalk
Myself5 said:
Sorry the skin part was a spelling misstake. Should have been SKIP. I issued the same as you, my problem was somehow related to DoomKernel. So just Flash Stock now (using a ftf in flashtool) and then straight the boot.img from the CM zip. Now boot in the recovery (press vol down when the Amber led lights up at the boot process) and flash the CM zip in this recovery (wipe data/Factory reset and format /system before ofc (least that what I would recommend)). Flash Gapps if you whish. Reboot to your now working CM install.
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
Absolutely 100% spot on, I'm so happy! Thanks
mrmatt100 said:
Absolutely 100% spot on, I'm so happy! Thanks
Click to expand...
Click to collapse
hello i'm having this exact same issue and i will be trying this taday when home from work. the only thing i'm not sure about is the ftf in flashtool.
don't know what ftf stands for, but i presume flashtool is the official sony flash tool?
http://developer.sonymobile.com/services/flash-tool/
thanks for the answer.
skuko said:
hello i'm having this exact same issue and i will be trying this taday when home from work. the only thing i'm not sure about is the ftf in flashtool.
don't know what ftf stands for, but i presume flashtool is the official sony flash tool?
http://developer.sonymobile.com/services/flash-tool/
thanks for the answer.
Click to expand...
Click to collapse
I think there's the official and an unofficial tool, I used the one from here http://www.flashtool.net/index.php
And a .ftf file is an official sony ROM, bit like how you end up with .zip files for non official ROMs, HTCs have .RUUs and iPhones have .ISPW files.
There's a list of .ftf files on here somewhere, grab the latest from there.
For what it's worth, I went CM11, got fed up with the camera quality so went to xistenz and romaur, both slightly unstable so I went back and back again to a stock .ftf, rooted it and I'm just using a bunch of xposed tweaks now and it looks pretty much the same as AOSP now. You only see the difference when you're in settings.
skuko said:
hello i'm having this exact same issue and i will be trying this taday when home from work. the only thing i'm not sure about is the ftf in flashtool.
don't know what ftf stands for, but i presume flashtool is the official sony flash tool?
http://developer.sonymobile.com/services/flash-tool/
thanks for the answer.
Click to expand...
Click to collapse
I meanwhile found a even easier way to solve this problem. Just go into faatboot mode (turn off phone press Vol+ and attach USB) and do "fastboot erase recovery" this will boot the kernels default recovery (CWM) again. This all is caused by some missing tools in the kernel which is not loading TWRP. However even with the tool provided by @Dees_Troy it does not load TWRP, now instead of hanging at the black screen with no recovery it still loads CWM after flashing TWRP to the recovery partition.
Sent from my Xperia Z2 using Tapatalk
Myself5 said:
I meanwhile found a even easier way to solve this problem. Just go into faatboot mode (turn off phone press Vol+ and attach USB) and do "fastboot erase recovery" this will boot the kernels default recovery (CWM) again. This all is caused by some missing tools in the kernel which is not loading TWRP. However even with the tool provided by @Dees_Troy it does not load TWRP, now instead of hanging at the black screen with no recovery it still loads CWM after flashing TWRP to the recovery partition.
Sent from my Xperia Z2 using Tapatalk
Click to expand...
Click to collapse
so if i want to get rid of the doomkernel, i still need to reflash the stock ftf, correct?
skuko said:
so if i want to get rid of the doomkernel, i still need to reflash the stock ftf, correct?
Click to expand...
Click to collapse
In case you want back to stock, yes. In case you want from Doom to CM just erase the recovery partition and fastboot flash the CM boot.img
Sent from my Xperia Z2 using Tapatalk
seems to have worked, my kernel in "about phone" now says:
3.4.0cyanogenmod-g449fd42
[email protected] #1
Mon Aug 18 09:30:35 BST 2014
i used the boot.img from your carbon rom nightly.
I unlocked my Bootloader, rooted and installed latest RR-Nougat. Now i want to go back to stock. At this point i have tried almost everything hence im asking for help. I have already searched the forum and internet. I have tried flashing pre rooted stock firmware from recovery but it didnt boot(Stuck at boot animation). Then i tried flashing Stock MM ftf file using flashtool, the flash went fine but i got the same problem again.Waiting for around 20 min then flashed recovery using fastboot and now i am back to RR.
bolt890 said:
I unlocked my Bootloader, rooted and installed latest RR-Nougat. Now i want to go back to stock. At this point i have tried almost everything hence im asking for help. I have already searched the forum and internet. I have tried flashing pre rooted stock firmware from recovery but it didnt boot(Stuck at boot animation). Then i tried flashing Stock MM ftf file using flashtool, the flash went fine but i got the same problem again.Waiting for around 20 min then flashed recovery using fastboot and now i am back to RR.
Click to expand...
Click to collapse
Just check all boxes of wipe section when you want to flash the FTF file(i mean ''userdata'' and ''apps_log'')
raminta said:
Just check all boxes of wipe section when you want to flash the FTF file(i mean ''userdata'' and ''apps_log'')
Click to expand...
Click to collapse
Trying this as i type, flash went fine, now waiting for boot. Success ! You are a life saver bro.