Database Develop

Trying to install 4.4 Rom, falling at every hurdle.

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!

Help, CM 11 Nightly BOOTLOOP on Xperia SP

I was on stock firmware (no root), i unlocked bootloader (but im not shure if i done it correctly, ithink that this is the problem), i downloaded and extracted boot.img and flash it via command prompt, installed zip file from sd card (cm-11-20140915-NIGHTLY-huashan) and now im stuck at cyanogenmod bootloop animation, i tried it several older version nightlys, same thing, ANY HELP PLEASE? And yes i tried factory data and wipe cache, no luck...

and yes i tried factory data and wipe cache, no luck...

I followed this guide here:
wiki.cyanogenmod.org/w/Install_CM_for_huashan

Use the Edit/Delete button in the right down corner, no multi-post
Have u tried flash again Stock one? just to be sure ur BL is unlocked..... but I'm pretty sure it is due to bootloop in CM logo, not kernel one, what about CM11 from FXP for UBL?

yes my BL is unlocked, when i enter flashtool/BLU it said Relock, thats mean that is unlocked, right? Idont know to flash stock rom and where to find, and what do you mean with "CM11 from FXP for UBL", i downloaded cm11 from offical cite, from here https://download.cyanogenmod.org/?device=huashan&type=nightly

tried to flash another rom, the same thing happens!

Flash an FTF file using Flashtool...

Flashed stock rom (ftf), then repeat the procedure for CM11 installation and it worked, thanx for help !

[Q] Device gets crazy after flash Doomlord kernel

Hi! Some months ago I flashed a kernel from here in XDA. The kernel was from Doomlord, to install CWM Recovery. But the device came into infinite boot. Then to solve it I flashed a stock rom (12.0.A.2.254) to see if the problem was solved..
Solved problem, the device came to normal (at least the infinite loop was solved).
But after flashing the Doomlord kernel, even flashing a stock rom, when I receive a message and visualize it, the LED stays turned on, and off only when rebooting. When I reboot the device, date/time are lost. The date in the top bar is updated only if I turn off the screen and then turn on again.
I tried reblock bootloader and repair from PC Companion. I tried flash the stock 4.3. I tried flash only the stock kernel. But nothing solves the problem.
Someone can help me?
Sorry for my english, I'm brazilian

You CANNOT relock bootloader while in custom kernel.
Unlock bootloader again, go in flashtool and flash the stock ftf, doom kernel isn't stable yet, use only stock or try another kernel...

lucasgta95 said:
You CANNOT relock bootloader while in custom kernel.
Unlock bootloader again, go in flashtool and flash the stock ftf, doom kernel isn't stable yet, use only stock or try another kernel...
Click to expand...
Click to collapse
Do you have the link to some kernel .elf that I can try to flash? If I unlock BL again and flash some stock .elf the problem could be solved?

Yes, but I recommend to flash a whole stock rom ftf after unlocking bl...
I passed through this situation too

lucasgta95 said:
Yes, but I recommend to flash a whole stock rom ftf after unlocking bl...
I passed through this situation too
Click to expand...
Click to collapse
I unlocked BL and flashed a stock (12.1.A.1.207). The problem continues. I tried too flash a stock 12.0.A.2.254 after unlock BL. In 4.1 the only problem is the date that is lost when rebooting. But flashing 4.3 stock all the previous problems continues. After receive messages, even if I read it, LED still on until I reboot the device. Date is lost after reboot, bla bla..
Maybe the problem is not the kernel that I flashed some months ago. What do you think? Some idea?

Guy, try this rom, and say if the problem continues
http://forum.xda-developers.com/xpe...nality-update-xperia-performance-max-t2895506
Unlock bootloader to use this rom
It is a great rom
If you don't like custom roms you can try the stock I'm using
http://forum.xda-developers.com/xperia-sp/general/ftf-12-1-1-207-generic-au-xperia-sp-t2856432

S3 LTE won't go past bootscreen no matter what

So last time my phone was stuck on the device name and model number screen. I solved that issue by flashing TWRP using Odin.
but now the phone would not go past the boot screen no matter what I do. I re-flashed CM11 4 times now, factory reseted and wipe cache and dalvik cache. What should I do?

1. change your thread title please. Need help is not really helpful or directs to your issue.
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.

maultasche said:
1. change your thread title please. Need help is not really helpful or directs to your issue.
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
Click to expand...
Click to collapse
So I should flash TWRP 2.8.5.0 and flash CM11 again? (because I don't have stock rom for S3 LTE)
Where can I get stock rom fro S3 LTE I can't seem to find it all, I find is firmwares.
Also, a few questions
1) If I give it into my phone carrier (Optus) would they know that it is rooted?
2) If they know it is rooted and with a custom rom and don't fix it for free is it possible to get it fixed by paying money??

The firmware provided by Samsung is the stock ROM I'm talking about
No, since you tried to flash a ROM through the faulty recovery you need to flash either official firmware from Samsung or a custom ROM based on Samsung stock like AMCHA or N4 Elite. I'd recommend to go with official Samsung firmware. After that go to stock recovery (it will come when you flash official firmware), do a factory reset and let the phone boot once. After that you can flash TWRP 2.8.5.0 and flash any ROM you want.
The new recovery from TWRP is too big for the S3. The S3 recovery is a little over 8MB, the new one needs more and messes up partitions etc. You won't be able to mount /system, /data and the recovery can't read your internal partitions as it should. Go with the way I provided. It seems like a lot of work but it's done in a few minutes.
For your two questions: yes and yes. But you can fix that on your own and don't need your operator or Samsung to get your phone fixed.

Thanks a lot for helping. I was scared to death cause if something happened I would've had to start using a old brick Nokia phones

Is it possible that after I flash the stock firmware, my phone still doesn't boot up?
I am basically a level above newbie, so I don't get what is happening. I see tutorials and do what they tell me to do. sometime I get what I am doing sometime I don't

as i said, after flashing stock, go into the recovery and do a factory reset. The phone will boot then

maultasche said:
as i said, after flashing stock, go into the recovery and do a factory reset. The phone will boot then
Click to expand...
Click to collapse
Ok sorry for doubting you! My phone is working now, thanks a lot for your help

Glad it's working now, you're welcome

I have rooted my s3 via odin and now i wont to flash twrp via flashify. Now i have a bootloop on my s3. How can i recover the phone. i am a noob on s3 and i don*t know how i could go into fastbootmode. Please help me.

what S3 do you have? Which recovery did you flash?

maultasche said:
2. what version of TWRP are you using? The official TWRP 2.8.7.0 does not work. Too long to explain why's that. To fix this issue there are some solutions if you flashed the faulty recovery:
- flash Stock ROM again and stay on TWRP 2.8.5.0
- some users fixed this issue by just flashing another recovery or just flashing a stock based custom rom to get their phone working. You still need to change recovery.
In my case I had to flash stock again and flash my preferred recovery again to get my phone working.
Click to expand...
Click to collapse
I had this problem too! Flashed stock rom, then flashed TWRP 2.8.5.0 (I was using 2.8.7.0) and then flashed cyanogenmod 12 and boom it booted and worked!
Thank you very much!

Bricked ??? Black screen after sony logo :(

Hi Friends,
I have played a lot with xperia z and never got into such situation.
So i have been using this resurrection remix 7.1.1 rom 12122016 build, and wanted to switch device so to give this device to my family member i flashed .222 5.1.1 as he is not techy like me and wont be able to fix problems on his own.
now the thing is i am stuck at black screen after sony logo
I know kernel is there there is just some system issue and to fix it i did below things still no success.
1. flashed ftf 6602 (Double checked and re downloaded FTF in case ftf was courrepted)
2. used emma tool and updated phone
3. flash twrp and flashed Xperia_Z_eXistenZ_Premium_v4.0.0
non of about gave me stock Rom and now i am stuck at non system in my phone just kernel mean as soon as i start my phone there is sony logo but after that there is no process.
Help would be great solace.
Thanks

chauhanjayc said:
Hi Friends,
I have played a lot with xperia z and never got into such situation.
So i have been using this resurrection remix 7.1.1 rom 12122016 build, and wanted to switch device so to give this device to my family member i flashed .222 5.1.1 as he is not techy like me and wont be able to fix problems on his own.
now the thing is i am stuck at black screen after sony logo
I know kernel is there there is just some system issue and to fix it i did below things still no success.
1. flashed ftf 6602 (Double checked and re downloaded FTF in case ftf was courrepted)
2. used emma tool and updated phone
3. flash twrp and flashed Xperia_Z_eXistenZ_Premium_v4.0.0
non of about gave me stock Rom and now i am stuck at non system in my phone just kernel mean as soon as i start my phone there is sony logo but after that there is no process.
Help would be great solace.
Thanks
Click to expand...
Click to collapse
First of all: read the forum rules. After 1400 posts you should know that the GENERAL section is not the right place to ask questions like this.
Second: Wich file system are you using? If it's any other but ext4 you should format the storage using twrp.
Did you flash with Androxyde's flashtool, or just with Emma?

Hey ! i too experienced the same issue earlier today.. Only the latest build isnt working when flashed ..I flashed the kitkat build via flashtool and it worked.. is there any solution.. ? ive been trying since morning.. And another thing is that recovery also cant be flashed . So im literally stuck at this phase. :crying:

just flash a stock rom from flashtool i always encounter that when i corrupt flashing thru recovery.. like i fully wipe and forgot to put rom in internal lol

Flashed with both Emma and flashetool
Even tried custom lp rom via twrp but the same situation

Have you fixed your issue? I have the same case. I flashed it to stock ROM but the black screen is still occurring after xperia logo.

1. make sure your partition is ext4
2. download proper official Kitkat 4.4.4 firmware (.tft), flash it with Androxyde's flashtool (make sure the .ftf is not corrupted, driver is installed, good usb cable and 75% of battery or above).
3. if you wanna check the device is in good shape, try to boot up (in my case, I'll flash LP 5.1.1 right after flashing KK firmware is done).
4. if the device is boot up correctly, turn off your device and begin to flash LP 5.1.1 firmware
NOTE: somewhere on this forum say about the right version of flashtool to flash the firmware to our device, older version of flashtool. But I'm using version 0.9.22.3 and everything is fine. However, I can see that the flashtool is not using the newest engine while flashing my device (C6603) but using the older engine instead.

Hi,
I have already been in such a situation.
1) Try to flash (with flashtool) official 4.2 Android firmware, boot, then flash latest one (5.1.1)
2) Try to flash official firmware (4.2) with xflasher (https://forum.xda-developers.com/showpost.php?p=74122327&postcount=212, https://forum.xda-developers.com/showpost.php?p=74122295&postcount=2)
Good luck!

still having same issue with my z3, flashing with emma and tft but stuck on sony logo

I also met this problem yesterday.
I use the latest Flashtool and flash the latest firmware but it said The bundle does not match the connected device.
Then I use a older version like 0.9.18 to flash the latest firmware. The problem you said occurred. It stuck in black screen after Sony logo.
Here is how I fix it:
1. Use an older version of Flashtool to flash an older firmware such as 4.4.4_10.5.1.A.0.283 like me.
2. After flashing the old firmware it should be normally powered on. Then power off and enter the flash mode again. And flash the latest firmware, problem fixed.
Hope that my experience can offer a bit help for you.