Database Develop

[Q] stuck in update loop

my 1st post here .. hi all :silly:
my n7000 was flashed to ( N7000JPLSB N7000OJPLSA - United Arab Emirates ) 2 months ago and i used a phil's kernel and rooted the device .. device worked good 2 months later a system update popped in and i pressed ok .
now device stuck at boot loop at the android robot .. i removed the battery so it isnt derained .. once i put the battery back and try to charge the battery the device enters the loop again
any help well be appreciated

mustafa811 said:
my 1st post here .. hi all :silly:
my n7000 was flashed to ( N7000JPLSB N7000OJPLSA - United Arab Emirates ) 2 months ago and i used a phil's kernel and rooted the device .. device worked good 2 months later a system update popped in and i pressed ok .
now device stuck at boot loop at the android robot .. i removed the battery so it isnt derained .. once i put the battery back and try to charge the battery the device enters the loop again
any help well be appreciated
Click to expand...
Click to collapse
Weird you got an update when you were running a custom kernel. Anyways, go into recovery, plug your phone into your computer and copy other Philz kernel for... JPLSB. Flash it, reboot. Do the following wipes: data factory reset, cache, dalvik, /system /preload. Once that is done just reflash again with Odin. You will loos all of your data. This will take you to complete stock - no customs kernel. If you want root again then you will have to download Philz kernel.

XxPixX said:
Weird you got an update when you were running a custom kernel. Anyways, go into recovery, plug your phone into your computer and copy other Philz kernel for... JPLSB. Flash it, reboot. Do the following wipes: data factory reset, cache, dalvik, /system /preload. Once that is done just reflash again with Odin. You will loos all of your data. This will take you to complete stock - no customs kernel. If you want root again then you will have to download Philz kernel.
Click to expand...
Click to collapse
it is a stock rom not custom but with philz kernel for the root

Philz kernel is well custom kernel, not stock kernel.
When a stock ROM having root, normally it doesn't receive any more automatic update from Samsung.
You'd better follow hints from XxPixX.

qnt said:
Philz kernel is well custom kernel, not stock kernel.
When a stock ROM having root, normally it doesn't receive any more automatic update from Samsung.
You'd better follow hints from XxPixX.
Click to expand...
Click to collapse
it is a stock rom with stock kernel but to root the galaxy note i read that flashing or wiping might cause a brick
on a stock kernel soooooooo usually after flashing the stock rom and before rooting i flash a safe kernel
i used odin in download mode and flashed the same stock firmware and surprise the device returned to its pre-brick
state exactly with all my contacts and all apps but root and kernel gone
so i am gonna root it now after installing safe kernel
thx all

qnt said:
Philz kernel is well custom kernel, not stock kernel.
When a stock ROM having root, normally it doesn't receive any more automatic update from Samsung.
You'd better follow hints from XxPixX.
Click to expand...
Click to collapse
Stock rom on any kernel will receive updates but will not be able to install it as it needs stock recovery. Notification of new update will come.

nokiamodeln91 said:
Stock rom on any kernel will receive updates but will not be able to install it as it needs stock recovery. Notification of new update will come.
Click to expand...
Click to collapse
Thanks for that info on stock recovery need to update.

had the issue too with some custom roms i use jonrom 4.1.2 LT4 custom rom now and everything is working well

So, re-flashing the ROM is the final answer..
Be it stock or custom ROM..

CWM recovery with stock kernel? - Help

Hi,
I unlocked the bootloader, flashed CWM into it. I backed up everything through CWM recovery.
However somehow the stock rom/kernel/etc don't work with this set-up. I just have "free xperia" logo until the universe will implode.
Therefore I installed cyanogenmod and it works. But I don't have the Xperia pkgs and since I own a lot of stuff from sony..those apps are usefull.
Question 1: Can I use CWM recovery with the stock sony rom?
Question 2: I just downloaded the ftf (700MB file), how can I restore everything? If I fastboot everything inside the package will it also correct the boot problem?
Question 3: Can I install sony pkgs as a 3rd party zip like google-apps?
Thanks for the help!!

Yes, you can use stock kernel with recovery.
But, since you are unlocked, you can install DoomKernel, its based on stock , it has a recovery and root included, and it is compatible with stock roms. Install it via fastboot, then you can flash a stock ftf excluding the kernel so you don't lose custom kernel.

DrKrFfXx said:
Yes, you can use stock kernel with recovery.
Click to expand...
Click to collapse
You mean in CWM menus? and install the .ftf?

forevertheuni said:
You mean in CWM menus? and install the .ftf?
Click to expand...
Click to collapse
CWM can't flash ftf, for that you need Flashtool.
CWM can only flash flasheable zips.

If you want to keep stock rom with a working cwm recovery you have choice using advanced stock kernel or doomkernel both have a recovery working normally. If you don't want to overclock/underclock and tweak stuff choose advanced it is the stock kernel with a recovery with nothing more.
Flash ftf and then fastboot the kernel you choose, or vice versa fastboot and then flash ftf and exclude kernel in flashtool.
edit : read this http://forum.xda-developers.com/showthread.php?t=2153167

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!

(Q) Any way to flash a rom without needing an FTF

As the title states, is there a way to flash a new rom without being tied down to a PC / laptop?
Bootloader's unlocked, rooted, it's strange how with this phone we're forced to stay locked down to a PC.
Have never flashed anything from the Original Dev section on this phone yet, would that be the same method as normal rom's like monx's and IHackers?
Cheers.

huh? TFTs are for returning to stock ROM and/or kernel and baseband, custom ROMs come in ZIP files which are flashable in recovery. What I do is download the ROM zip on my phone and flash it straight after via recovery, no need for a computer at all.

tomascus said:
huh? TFTs are for returning to stock ROM and/or kernel and baseband, custom ROMs come in ZIP files which are flashable in recovery. What I do is download the ROM zip on my phone and flash it straight after via recovery, no need for a computer at all.
Click to expand...
Click to collapse
FTF's are not just for returning to stock, not at all, they're used to flash rom's too as the kernel and baseband needs to be flashed also.
Check out monx's thread, the instructions for install states to flash the rom and then without allowing a reboot, flash kernel and system (afaik)
Simply flashing the rom wouldn't be enough without flashing those files via flashtool.
What i'm trying to ascertain is do I have to do this every time as it's a pain in the backside.
Quote from Monx
LOCKED & UNLOCKED BOOTLOADER
BACKUP any critical data to microSD
Copy this rom zip package to microSD
Reboot in recovery, (do nandroid backup), do factory reset & install rom until finish
IGNORE RECOVERY INSTALLATION WARNING. SELECT NO & PROCEED AT THE END OF RECOVERY IF USING CWM RECOVERY
Skip (x) steps if u already running same base firmware with latest monxDIFIED base rom. Else, proceed.
(x) Turn off device. (Hold power button + vol up until vibrates 3 times) [or use recovery turn off device option, if any]
(x) Flash latest Sony's firmware (FTF) matching current latest monxDIFIED base rom using latest flashtools. UNCKECK all WIPE options and CHECK only SYSTEM & TA in EXCLUDE options.
(x) Disconnect USB cable & turn on phone. Done.

Notice how I write "and/or kernel and baseband"?
FTF only necessary if changing bases, don't need to flash every time going from ROMs on same base.
Sent from my C6903 using Tapatalk

tomascus said:
Notice how I write "and/or kernel and baseband"?
FTF only necessary if changing bases, don't need to flash every time going from ROMs on same base.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Because you wouldn't be performing a full wipe right?
Thing is I would never do a dirty flash over another rom, you're asking for problems if you do, so in which case I'm guessing that I'd need to use an FTF file to replace the files needed that aren't flashed with the rom right?
Thanks by the way.
Reason i'm asking all this is because this is the first phone that i've had were i've needed to be tied down to a PC to flash a rom, it's a bit crap really.

dladz said:
Because you wouldn't be performing a full wipe right?
Thing is I would never do a dirty flash over another rom, you're asking for problems if you do, so in which case I'm guessing that I'd need to use an FTF file to replace the files needed that aren't flashed with the rom right?
Thanks by the way.
Reason i'm asking all this is because this is the first phone that i've had were i've needed to be tied down to a PC to flash a rom, it's a bit crap really.
Click to expand...
Click to collapse
I used to have the HTC One X which required the same trouble-some computer steps.
The kernel and baseband don't even get affected when you do a full wipe, they're separate from the system, data, and cache partitions which gets wiped. Basically the stripped FTF holds the stock kernel and baseband needed to get compatible mobile signal and this only needs to be done once moving from base to base.
Going to and from ROMs with same base:
1. Full wipe
2. Flash ROM
ps. some ROMs flash their own kernel during ROM install i.e iHackers.

tomascus said:
I used to have the HTC One X which required the same trouble-some computer steps.
The kernel and baseband don't even get affected when you do a full wipe, they're separate from the system, data, and cache partitions which gets wiped. Basically the stripped FTF holds the stock kernel and baseband needed to get compatible mobile signal and this only needs to be done once moving from base to base.
Going to and from ROMs with same base:
1. Full wipe
2. Flash ROM
ps. some ROMs flash their own kernel during ROM install i.e iHackers.
Click to expand...
Click to collapse
Nice one m8, that's put an end to my misery, cheers for that, makes a lot of sense now, i wasn't aware of how Sony rom's were flashed, it's strange as the bootloader is unlocked? What more is needed lol.
As for the one x, that's the only HTC i skipped and glad i did apparently they had a lot of problems with flashing and stuff, S-OFF.
Anyway, thanks m8.

[Q] Preserve my recovery while flashing ROM zip

Hello all,
as long as I would like to test new CM12 official nightlies as they become available for my Xperia T, I'd also like to have a fast and easy way to revert back to my previous ROM.
This would be easily done with the backup and restore function of any CWM based recovery, but every time I flash a nightly I get my recovery replaced by Cyanogen's one, that (AFAIK) lacks this useful feature.
Is there any way to prevent my current recovery from being replaced every time I flash a nightly, or a simple way to put it back?
I tried hard not to, but today I ended up restoring bootloader lock, stock firmware and all, then repeating all the steps to install a custom recovery.
Please, tell me there's another way 'round it.

You can flash a boot.img that includes CWM before restoring your backup.
I recommend DoomKernel for this purpose.
Another way would be to flash a revovery for FOTA partition, which will replace all recoveries in kernel.

I flashed DoomKernel v12 via fastboot and it worked really nicely. It's a fast way to put a recovery on my device when I want to flash something, and I can even choose what recovery to use. Thanks!
Having installed a FOTAKernel recovery, are there any precautions I must take while flashing other ROMs if I want to keep the recovery in place? Also, what operations will erase it or make it unavailable?

Darsil said:
I flashed DoomKernel v12 via fastboot and it worked really nicely. It's a fast way to put a recovery on my device when I want to flash something, and I can even choose what recovery to use. Thanks!
Having installed a FOTAKernel recovery, are there any precautions I must take while flashing other ROMs if I want to keep the recovery in place? Also, what operations will erase it or make it unavailable?
Click to expand...
Click to collapse
No rom I know of contains an integrated FOTA recovery, so you shouldn't have to worry about that when flashing a new rom.
The only way to revert to stock recovery is to flash a stock ftf via Flashtool.