Database Develop

Installing stock rom with cwm recovery

hi.
Is it possible to install stock rom from this thread http://forum.xda-developers.com/showthread.php?t=1424997 wit cwm recovery?
Will instaling stock rom with cwm recovery overwrite my cwm recovery? If I am rootwd now, will I have still root after installing stock rom?

If you install a stock Rom, you'll lose both your CWMR and root, unless you do it using Mobile Odin.

yes you can flash Stock ROM with CWM. n you have to select 'keep CF root' when it ask.
For detail guide, Download guide from last link on my signature you will find ' Update ROM using CWM' in New folder.
---------- Post added at 02:18 PM ---------- Previous post was at 02:16 PM ----------
chasmodo said:
If you install a stock Rom, you'll lose both your CWMR and root, unless you do it using Mobile Odin.
Click to expand...
Click to collapse
Hey, your Note get recovered? This time you seems restless. He ask specifically about using CWM.
Anyway like to read your post always
Regards.

I am asking about cwm recovery.

dr.ketan said:
yes you can flash Stock ROM with CWM. n you have to select 'keep CF root' when it ask.
For detail guide, Download guide from last link on my signature you will find ' Update ROM using CWM' in New folder.
---------- Post added at 02:18 PM ---------- Previous post was at 02:16 PM ----------
Hey, your Note get recovered? This time you seems restless. He ask specifically about using CWM.
Anyway like to read your post always
Regards.
Click to expand...
Click to collapse
I must've skimmed the OP, hence the inappropriate reply.
My Note was never bricked BTW. I had flashed angelom's v1, not v1.1 or v1.2, and managed to pull back in time.
Your posts are always to the point and very helpful, too.

mod2000 said:
I am asking about cwm recovery.
Click to expand...
Click to collapse
Ya i got it, replied u just above your this post.
Sent from my GT-N7000 using xda premium

Thanks for your reply, but your guide is about cwm manager, but not cwm recovery.
What about cwm recovery, can I update rom and keep root and cwm?

mod2000 said:
Thanks for your reply, but your guide is about cwm manager, but not cwm recovery.
What about cwm recovery, can I update rom and keep root and cwm?
Click to expand...
Click to collapse
You need cwm from cf, with stock recovery can't flash any rom.
You are rooted already then get cwm first.
You said to keep cwm, means u have it, stock recovery can't b erased. Stock recovery hav limited set of function. I believe u have still confusion in understanding cwm, just read more.
Sent from my GT-N7000 using xda premium

I think you can not install stock rom with cwm recovery. But you can restore backups.
There is difference between CWM - its and application which can be opened when you boot in the phone, and CWM Recovery - you can access it without/before booting in the phone.
Sorry if my answer is wrong.

Boy124 said:
I think you can not install stock rom with cwm recovery. But you can restore backups.
There is difference between CWM - its and application which can be opened when you boot in the phone, and CWM Recovery - you can access it without/before booting in the phone.
Sorry if my answer is wrong.
Click to expand...
Click to collapse
Totally right. Thanks

Boy124 said:
I think you can not install stock rom with cwm recovery. But you can restore backups.
There is difference between CWM - its and application which can be opened when you boot in the phone, and CWM Recovery - you can access it without/before booting in the phone.
Sorry if my answer is wrong.
Click to expand...
Click to collapse
CWM recovery OR better term is stock recovery, which exist on all device(inbuilt stock function), which can be access with Vol up + Power + Home
This have limites set of function, Just wipe cache, n wipe data.
Niether stock Nor custome ROM can be flashed
Nither backup Nor Restore is possible with it.
For this fuction, you need to have CWM application, which can available only if you have your device rooted. If tou have flash CWM, then you can access it with same method(three keys), but menu will be more advanced.
Hope it should be clear Now.

n7000 stock android with cwm installed
Hello there,
I wanted to install kitkat on my note1, n7000. I rooted the phone with philz cwm6 ddlsc. Everything went good. I then tried to install the kitkat 4.4.4 and it keeps giving an error and does not install. Later doing some research i figured i need a version of 6.4 and above of cwm in order to install 4.4.4. So I decided to leave all this and go back to stock 4.1.2. I did not unfortunately create a backup. Now that im trying to install it through odin the stock android, odin does not detect the phone. I have wiped off cache, user data and dalvik cache. Everytime the phone is booted it goes to cwm menu.
Please help me install the stock android and remove cwm/root.
Your help is much appreciated.

on my note 2 i have backup stock rom with cwm and in cwm folder in my files backup file is ther and in that some date is there is that my back
i m having issue with my cm12 and i want to flash my stock rom so that backup file is my stock rom so i can flash it via cwm will my old galaxy stock rom of 4.4.2 kit rom will restore

muzammil9010mnm said:
on my note 2 i have backup stock rom with cwm and in cwm folder in my files backup file is ther and in that some date is there is that my back
i m having issue with my cm12 and i want to flash my stock rom so that backup file is my stock rom so i can flash it via cwm will my old galaxy stock rom of 4.4.2 kit rom will restore
Click to expand...
Click to collapse
Although this is the note 1 forum but yes usually that's how it works. If you backed it up using cwm, then restoring should also work. You will need to do a factory reset 1st.

[Q] Sick and tired of these bootloops on ICS!

As the title says, I am tired of these random bootloops who is making my phone bootloop and never startup. Now I can't even acess the phone to get a backup! I have tried almost all ICS roms and now the latest one is [ROM][4.0.4]BlueBerry Project - ICS by lippol94's point of view (based on CM sources)
Please helpe me!
1. To acess the phone in order to make a backup with titanium backup
2. Give me some tip on a stable ICS rom without any goddamn bootloop 1-2 weeks after installation!! PS. not roms like "slim ****" and so on, I want stock ICS without any extras!!
3. Stop working on these JB roms and start to stabilise ICS and then work for JB, just some tip for the devs!
thanks!

I stopped overclocking and the bootloops stopped for me.

Vertron said:
I stopped overclocking and the bootloops stopped for me.
Click to expand...
Click to collapse
I have never OC, clean install on every rom!

Bump at least help me get into the phone to take backup on my stuff
I have already flashed semaphore kernel via Odin but it's still bootlooping, I haven't lost access to the recovery but I don't understand this ****ing common boot loop i am facing
Sent from my MZ601 using XDA Premium HD app

romdroid. said:
Bump at least help me get into the phone to take backup on my stuff
Sent from my MZ601 using XDA Premium HD app
Click to expand...
Click to collapse
Go into download mode & flash a Semaphore.tar kernel using odin. That should hopefully make it boot. If it doesn't work reflash Semaphore in Odin, but this time check repartition.

Vertron said:
Go into download mode & flash a Semaphore.tar kernel using odin. That should hopefully make it boot. If it doesn't work reflash Semaphore in Odin, but this time check repartition.
Click to expand...
Click to collapse
I checked repartition and odin gave me this error
Can't open the specified file. (Line: 1815)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
what should I do now? I have flashed before with Odin no problem until now..I also removed sim-card and SDcard

romdroid. said:
I checked repartition and odin gave me this error
what should I do now?
Click to expand...
Click to collapse
I don't know it's never failed for me before. If Semaphore doesn't fix the bootloop problem for me then I'm forced to flash a GB rom and start from scratch. It's unlucky that you haven't been able to backup your apps, it happened to me before too, very annoying.
If you can get into recovery try clearing your cache & davik cache.

Vertron said:
I don't know it's never failed for me before. If Semaphore doesn't fix the bootloop problem for me then I'm forced to flash a GB rom and start from scratch.
If you can get into recovery try clearing your cache & davik cache.
Click to expand...
Click to collapse
I can get into recovery, I have also cleared cache & dalvik but with no sucess

Maybe someone else can jump in and help?

bump
desperate guy I need to take backup, just want to acess the phone :crying:

So after flashing semaphore you can access recovery but phone still doesn't boot?It's bootlooping from Galaxy S device boot to kernel boot image then back to device boot and so on?No eternal bootanimation?
Anyway,as recovery is accessible it could just be caused by a settings problem,there's advanced options to clear init.d folder in semaphore cwm menu,you could try this at first.
Everytime it happened to me i just flashed semaphore ICS as .tar even with auto-reboot ticked and my phone booted fine (when it was those strange device>kernel>device with lost access to recovery bootloops).
Previously i had good results with MnIcs kernel too,you could try:
http://dl.dropbox.com/u/25071013/MNICS-20120509-7-LR.tar
But the thing that worked all the times (for cwmless bootloops i mentionned) was cm7 initial kernel .tar:
http://dl.dropbox.com/u/25071013/cm7-galaxys-initial-kernel.tar
Note it's a ginger aosp (cm7) kernel,so once it is flashed (auto-reboot UN-ticked) and you are in his orange recovery menu you can flash any ICSkernel zip that hopefully lies on your sd and see if it boot now or flash your ics rom (no-wipe needed,it's not what you want thought but you'll have to flash the rom in two times:first flash will go into little and fast bootloop to recovery due to change of cwm so you pull off battery,go back to recovery that will bechanged and flash again the rom).
Another thing i see is making a nandroid backup in your actual recovery even if it's a bootlooping one cause you can restore only data and datadata (just apps and settings) once you will be able to use your rom or another similar again.

romdroid. said:
bump
desperate guy I need to take backup, just want to acess the phone :crying:
Click to expand...
Click to collapse
Options
First pull out battery to break that cycle
1) Flash a 512 PIT FILE with REPARTITION MUST BE UNCHECKED phone will Boot up
IF failed
2) IF On ICS ROM flash http://forum.xda-developers.com/showthread.php?t=1468795 ICS kernel

xsenman said:
Options
First pull out battery to break that cycle
1) Flash a 512 PIT FILE with REPARTITION MUST BE UNCHECKED phone will Boot up
IF failed
2) IF On ICS ROM flash http://forum.xda-developers.com/showthread.php?t=1468795 ICS kernel
Click to expand...
Click to collapse
What does the pit file do?
Sent from my GT-I9000

Bejda said:
So after flashing semaphore you can access recovery but phone still doesn't boot?It's bootlooping from Galaxy S device boot to kernel boot image then back to device boot and so on?No eternal bootanimation?
Anyway,as recovery is accessible it could just be caused by a settings problem,there's advanced options to clear init.d folder in semaphore cwm menu,you could try this at first.
Everytime it happened to me i just flashed semaphore ICS as .tar even with auto-reboot ticked and my phone booted fine (when it was those strange device>kernel>device with lost access to recovery bootloops).
Previously i had good results with MnIcs kernel too,you could try:
http://dl.dropbox.com/u/25071013/MNICS-20120509-7-LR.tar
But the thing that worked all the times (for cwmless bootloops i mentionned) was cm7 initial kernel .tar:
http://dl.dropbox.com/u/25071013/cm7-galaxys-initial-kernel.tar
Note it's a ginger aosp (cm7) kernel,so once it is flashed (auto-reboot UN-ticked) and you are in his orange recovery menu you can flash any ICSkernel zip that hopefully lies on your sd and see if it boot now or flash your ics rom (no-wipe needed,it's not what you want thought but you'll have to flash the rom in two times:first flash will go into little and fast bootloop to recovery due to change of cwm so you pull off battery,go back to recovery that will bechanged and flash again the rom).
Another thing i see is making a nandroid backup in your actual recovery even if it's a bootlooping one cause you can restore only data and datadata (just apps and settings) once you will be able to use your rom or another similar again.
Click to expand...
Click to collapse
YES! I can acess recovery after I have flashed semaphore kernel, but it keeps bootlooping for no reason. I have already tried to install the .tar semaphore without sucess. thank you for your respone I will try that!
should I unpack MnIcs kernel or just leave it and flash it as it is? I am not without a recovery so I'll try to flash that kernel first and see if it fixes it
xsenman said:
Options
First pull out battery to break that cycle
1) Flash a 512 PIT FILE with REPARTITION MUST BE UNCHECKED phone will Boot up
IF failed
2) IF On ICS ROM flash http://forum.xda-developers.com/showthread.php?t=1468795 ICS kernel
Click to expand...
Click to collapse
thanks for ur answer mate where can I find "512 PIT FILE" any links?

Yes,let the MnIcs or initial cm7 .tar as they are.

romdroid. said:
thanks for ur answer mate where can I find "512 PIT FILE" any links?
Click to expand...
Click to collapse
here http://forum.xda-developers.com/showthread.php?p=29331775#post29331775

Bejda said:
Yes,let the MnIcs or initial cm7 .tar as they are.
Click to expand...
Click to collapse
argh, seems like it didnt work
xsenman said:
here http://forum.xda-developers.com/showthread.php?p=29331775#post29331775
Click to expand...
Click to collapse
thanks! nothing will be deleted from the phone if I flash it, right?:good:

Helloworld294 said:
What does the pit file do?
Sent from my GT-I9000
Click to expand...
Click to collapse
It rearranges ROM space trade operation between /system and /dbdata
---------- Post added at 08:18 AM ---------- Previous post was at 08:17 AM ----------
romdroid. said:
argh, seems like it didnt work
thanks! nothing will be deleted from the phone if I flash it, right?:good:
Click to expand...
Click to collapse
yes, but make sure you untick repartition

xsenman said:
It rearranges ROM space trade operation between /system and /dbdata
---------- Post added at 08:18 AM ---------- Previous post was at 08:17 AM ----------
yes, but make sure you untick repartition
Click to expand...
Click to collapse
That is odd, I cant even click "start"? when trying to flash .512 pit
That is with odin 1.82
I downloaded odin 3.04 and when I click start I get "no binary selected"

romdroid. said:
That is odd, I cant even click "start"? when trying to flash .512 pit
Click to expand...
Click to collapse
just reboot PC and Phone after a battery pull
---------- Post added at 08:25 AM ---------- Previous post was at 08:23 AM ----------
use Odin 1.85 than

[Q] Flashing CM9,1

Well,
I have a Galaxy Note on hands trying to install CM9.1. It was with Official rom ICS 4.0.3. I flashed it without doing the 3 wipes, and after I flashed the rom i tried to wipe data/factory reset. Then the phone would turn off everytime. So, I tought it must be because I didn't flash, then I'm trying to go back to GB, like the tutorial we have in XDA, but I'm stuck at NAND Write Start! Cache.img, and it doesn't proceed, no error messages.
What should I do?
help!

was the 4.0.3 rooted? did you have CWM with kernel or did you use CWM.zip?

nokiamodeln91 said:
was the 4.0.3 rooted? did you have CWM with kernel or did you use CWM.zip?
Click to expand...
Click to collapse
I rooted it first, and after root i used CWM.zip file.
why?

CWM.zip file is known to cause bricks. What kernel where you on? do you remember installing a custom kernel?
---------- Post added at 01:27 AM ---------- Previous post was at 01:26 AM ----------
also it would be good it you can post the screen shot of odin .. how you selected the rom files and where.

nokiamodeln91 said:
CWM.zip file is known to cause bricks. What kernel where you on? do you remember installing a custom kernel?
---------- Post added at 01:27 AM ---------- Previous post was at 01:26 AM ----------
also it would be good it you can post the screen shot of odin .. how you selected the rom files and where.
Click to expand...
Click to collapse
I installed HydraCore 7.0 STD

msedek could be right.. if you can walk us through the procedure on how you tried to install the CM rom.. we could confirm a brick,,

nokiamodeln91 said:
msedek could be right.. if you can walk us through the procedure on how you tried to install the CM rom.. we could confirm a brick,,
Click to expand...
Click to collapse
Well
I was with Official Firmware 4.0.3. Then:
1. Installed Super SU
2. Installed CWM.zip
3. Installed CM9.1
4. Wipe data/factory Reset
5. Auto reboot the device, and styck on boot screen
6. Back to Recovery
6.1 Installed Hydracore 7.0 STD
7. Wipe cache and Wipe Dalwik
8. Tried to wipe Data/factory Reset
9. Auto-reboot and yet locked on boot screen
10 Download Mode
11. trying to install GB official rom and locked in Cache writing.
I need help because it is my boss's phone. I have a galaxy note and because of this procedure that worked fine on mine I did that.
Any help to solve this hard brick?

Anyone? I need help
Really desperate here.

Installing a rom using temp cwm.zip could have done the trick to brick your phone. Anyhow. Could you paste the odin logs.

nokiamodeln91 said:
Installing a rom using temp cwm.zip could have done the trick to brick your phone. Anyhow. Could you paste the odin logs.
Click to expand...
Click to collapse
oh,
I'm not anymore in the PC where I tried Odin. But the logs were pretty usual, stopping at NAND Write Start
like this image
http://forum.xda-developers.com/attachment.php?attachmentid=1224997&stc=1&d=1343392025
And I also tried to install ICS room 4.0.3. That went on till factoryfs.img, then stoped.
Super Brick? Really? How's that possible?

provettirodolfo said:
oh,
I'm not anymore in the PC where I tried Odin. But the logs were pretty usual, stopping at NAND Write Start
like this image
http://forum.xda-developers.com/attachment.php?attachmentid=1224997&stc=1&d=1343392025
And I also tried to install ICS room 4.0.3. That went on till factoryfs.img, then stoped.
Super Brick? Really? How's that possible?
Click to expand...
Click to collapse
The stopping at "factoryfs.img" in combination with using the temporary recovery in cwm.zip is typical for a bricked device.
Please read hg42's thread for checking the bad sectors and for a workaround by repartitioning (this will exclude the bad parts from using it). But first check the eMMC with his method for errors and real confirmation of the brick.
A complete repair is only possible with a replacement of the motherboard by Samsung.

[Q] How to UnBrick galaxy n7000

Hi,
other day I was playing game on my note 1 and then battery ran out and now my phone wont boot up and it is stuck at animated samsung logo.
It was running on stock rom and it was never rooted.
Now when i go in recovery mode it gives this error:
failed to mount /efs
I tried installing the stock rom but with no luck.
I am newbie into this all, so can you please guide how to fix this ..
Regards

ahmedmasu said:
Hi,
other day I was playing game on my note 1 and then battery ran out and now my phone wont boot up and it is stuck at animated samsung logo.
It was running on stock rom and it was never rooted.
Now when i go in recovery mode it gives this error:
failed to mount /efs
I tried installing the stock rom but with no luck.
I am newbie into this all, so can you please guide how to fix this ..
Regards
Click to expand...
Click to collapse
You should try to put your Note in download mode and flash a stock rom with Odin.
You must flash the PIT file to repartition your phone's storage, chose the right one (16 or 32 Gb).
I am almost sure that your phone is soft bricked and it is recoverable.
If it don't work, thant mean that your have bad blocks in your phone's storage. Have you wiped your note while under ICS android ?

what rom were you on? if JB, try a factory reset.

nokiamodeln91 said:
what rom were you on? if JB, try a factory reset.
Click to expand...
Click to collapse
I was on latest stock rom which is ICS.
Btw I tried to reset it to factory but with no luck

lionelia said:
You should try to put your Note in download mode and flash a stock rom with Odin.
You must flash the PIT file to repartition your phone's storage, chose the right one (16 or 32 Gb).
I am almost sure that your phone is soft bricked and it is recoverable.
If it don't work, thant mean that your have bad blocks in your phone's storage. Have you wiped your note while under ICS android ?
Click to expand...
Click to collapse
Thank for your reply.
I tried flashing the stock rom with Odin but the error remained there
Can you please give me a link from where I can get PIT file?

ahmedmasu said:
I was on latest stock rom which is ICS.
Btw I tried to reset it to factory but with no luck
Click to expand...
Click to collapse
You shouldn't be doing a reset on ICS stock at all.. Install Philz kernel for ICS and wipe data and cache.. When flashing a stock rom using odin, is it a success?

nokiamodeln91 said:
You shouldn't be doing a reset on ICS stock at all.. Install Philz kernel for ICS and wipe data and cache.. When flashing a stock rom using odin, is it a success?
Click to expand...
Click to collapse
Is there any guide\link to do this ?

http://forum.xda-developers.com/showthread.php?t=1901191

nokiamodeln91 said:
You shouldn't be doing a reset on ICS stock at all.. Install Philz kernel for ICS and wipe data and cache.. When flashing a stock rom using odin, is it a success?
Click to expand...
Click to collapse
I have successfully flashed rom on my phone which is : N7000ZSLPF_N7000OZSLPF_OZS
My phone is now out of bootloop but now I face a different issue that I cant get my sim card work, it gives no signal and I noticed one more thing that IMEI of my phone is blank.
I went into recovery mode and it is still showing that efs error as it was showing before...
Any suggestion what should I try to fix this ?

So you never installed any rom or a custom kernel?
---------- Post added at 03:15 AM ---------- Previous post was at 03:11 AM ----------
Look for a file on your storage named efs.autobackup.img. If nothing like that, check on this site http://www.cvxcvx.pl/en/podstrona-0/naprawa-efs-w-i9100-n7000/ for some instructions. Read carefully and proceed.

nokiamodeln91 said:
So you never installed any rom or a custom kernel?
---------- Post added at 03:15 AM ---------- Previous post was at 03:11 AM ----------
Look for a file on your storage named efs.autobackup.img. If nothing like that, check on this site http://www.cvxcvx.pl/en/podstrona-0/naprawa-efs-w-i9100-n7000/ for some instructions. Read carefully and proceed.
Click to expand...
Click to collapse
I followed the instructions provided by the manual ... after step 2 I get imei but after step 3 it get empty again.
Signals do come after step 2 but when I try to make some call it says "Not registered on network".
Looking forward to your reply.

i cannot help you in this case if there is no efs backup.. so.. you on your own..

nokiamodeln91 said:
i cannot help you in this case if there is no efs backup.. so.. you on your own..
Click to expand...
Click to collapse
Thanks for your help so far...
I currently have an imei but it is some random number starting with "004999" and I do get signals but cant make a call .. Do you know if there is some hope for me or not .. and what else I can try.

This is the developer imei. You may be able to make calls of you try a GB rom. Or there is one rom by ThaiDai which had some work around built into it. I don't know which one.
Else the site I mentioned earlier has contact info of cvxcvx. He can fix your phone remotely but by charging about 10 euros.

Need help for a bricked N7000
Hi guys,Im a complete newbie to the whole custom rom scenario. Yet, after being fed up of touchwiz on my N7000 i decided i wanted to taste some KitKat on my phone. After seeing many videos with positive reviews I thought it would be a rather easy process. But somehow I seem to have made a mistake and now my phone is stuck on Samsung Galaxy Note N7000 logo. I cant get into recovery mode as suggested on most places. As of now I only have access to the download mode but dont know what to do with it.
Here's what I tried doing :
1) I was on stock OS, and these are my specifics : Galaxy Note N-7000 running JB 4.1.2
Baseband version : N7000DDLS6
Kernel version: 3.3.31-906407
BUild number:JZO54K.N7000DDLSC
2) As I was following the procedure from Omnirom's official website, I first rooted my phone using Framaroot's single click root app. This gave me SuperSU app.
3) Then I tried installing TWRP recovery (recommended by Omni) but they dont support the N7000. I read a few other tutorials where it was stated the CWM recovery and that too Philz CWM recovery is the best to go with. Apparently it is just stock kernel with CWM recovery. Since the latest one(philz_touch_6.07.9-n7000) was not being installed, I installed the one before that which worked (PhilZ-cwm6-DDLSC-ODD-5.11.2-signed).
4) I even installed the ROM Manager as per the tutorial. However, uptil now I could access recovery mode ( Vol UP+Home+Power) and i saw the touch enabled philz recovery mode once. Then i did system reboot.
5)After reboot, this is where I did a mistake in my opinion. I opened ROM Manger and clicked on "open in recovery mode" option. Since then the phone is stuck on the Galaxy Note N7000 logo. Please help me revive the phone. Thanks in advance. Again, Im doing this for the first time and most terms are new to me. So please explain the procedure as other tutorials are not very clear.

You missed on reading the most important instructions.
Rom manager will not work with note. Recovery is built into the kernel on note and not as a separate partition.
Try harder to get into recovery mode. If you still can't, get the ddlsc Philz kernel tar version. Flash it using Odin. Then power off the device and boot into recovery. Then flash raw kernel. Reboot recovery. Flash omni and other required zips.

nokiamodeln91 said:
You missed on reading the most important instructions.
Rom manager will not work with note. Recovery is built into the kernel on note and not as a separate partition.
Try harder to get into recovery mode. If you still can't, get the ddlsc Philz kernel tar version. Flash it using Odin. Then power off the device and boot into recovery. Then flash raw kernel. Reboot recovery. Flash omni and other required zips.
Click to expand...
Click to collapse
How do I do i install the kernel using ODIN? I can only access download mode and nothing else. I cant access recovery mode. Please help.

PhilZ kernel has two versions, zip and tar. Use the tar version to flash via odin.
Sent from my GT-N7000 using Tapatalk 2

forest1971 said:
PhilZ kernel has two versions, zip and tar. Use the tar version to flash via odin.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Bro can i ask for the link of philz kernel and raw kernel. I'm new here. Thanks in advance.

ANDROID-000 said:
Bro can i ask for the link of philz kernel and raw kernel. I'm new here. Thanks in advance.
Click to expand...
Click to collapse
http://www.mediafire.com/?ep82ku4c6...o6dtlx8lbc3xz,ob3q9g36b9b3w22,d3v1gys7cbckiet

[Q] boot looping like no other

hey everyone.
really just want to make sure im flashing this rom correct.
mainly because after i wipe everything. data system, exc.
when i go to reboot the device reboots, goes to Samsung galaxy note 4.
then turns off.. vibrates twice then goes back to the samsung galaxy note 4.
rom i am trying to flash is alliance v1.1
the rom i am coming from is the alliance tmobile beta
any info would help
thanks!!!

holt3113 said:
hey everyone.
really just want to make sure im flashing this rom correct.
mainly because after i wipe everything. data system, exc.
when i go to reboot the device reboots, goes to Samsung galaxy note 4.
then turns off.. vibrates twice then goes back to the samsung galaxy note 4.
rom i am trying to flash is alliance v1.1
the rom i am coming from is the alliance tmobile beta
any info would help
thanks!!!
Click to expand...
Click to collapse
Dont wipe system after you flash the ROM. Only wipe cache. If you wipe system you are earasing the ROM.
Sent from my SM-N910T using XDA Free mobile app

Help!
Did you end up figuring this out? I've just had the same thing happen to me!

This build is a COD6..
have you folks updated your bootloader and modem???
If your flashing the partial firmware using odin.. then you need to boot directly into recovery and flash the Rom.
Please post a screen shot of "about device" so i can see your baseband..
Sent from my SM-N910T using Tapatalk

Flashvetrin said:
This build is a COD6..
have you folks updated your bootloader and modem???
If your flashing the partial firmware using odin.. then you need to boot directly into recovery and flash the Rom.
Please post a screen shot of "about device" so i can see your baseband..
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I'm not really sure what you mean, I'm still relatively new at this.
It wouldn't boot at all, but I managed to install twrp through the recovery. Afterwards I put the rooted stock ROM on the SD card and did a wipe/install from recovery and now it's stuck doing the loop and vibrating twice each time.
I can't figure out how to find that information when I only have access to recovery, it's the Bell version in Canada, SM-N910W8. I had it up to date and just rooted it last night.
Thanks for your quick reply!
Edit: I did change a couple of things with build.prop.editor before it happened, that's what I'm thinking screwed this.

AaronBG said:
I'm not really sure what you mean, I'm still relatively new at this.
It wouldn't boot at all, but I managed to install twrp through the recovery. Afterwards I put the rooted stock ROM on the SD card and did a wipe/install from recovery and now it's stuck doing the loop and vibrating twice each time.
I can't figure out how to find that information when I only have access to recovery, it's the Bell version in Canada, SM-N910W8. I had it up to date and just rooted it last night.
Thanks for your quick reply!
Edit: I did change a couple of things with build.prop.editor before it happened, that's what I'm thinking screwed this.
Click to expand...
Click to collapse
So you have twrp installed..
Ok. Do you have a nandroid back on your ext sd by chance?? If so reboot recovery under advanced wipe sys/data/dal/cache.. then navigate to your ext were your restore is and flash it..
If not follow these steps.[emoji16]
Step #1 download either a stock rom of your choice or something like This
And a copy of the bioshock kernal. If you decide to use the rom i provided the link for. Check the md5 sums from the download source after you download the files to make sure they match. Download them onto your ext sd card.
Step#2 reboot recovery go to wipe advanced and check/ system/data/dalvik/cache/and internal.. ×3
Then factory data reset x3
Then nav to ext sd and flash the rom.
Note: if you flash the link i provided you have to flash the kernel in the same session... READ THE OP..
Note: #2 when you wipe internal your internal sd card will be wiped so if you need to save pics or whatever do so prior..
You can try skipping the internal once but if it loops then you prob should wipe it like i said and flash kernal such as bioshock.
Ok thats it for now please follow and read what i wrote carefully..
And for now stay away from COD6 for now.. unless you understand the procedure... its all about the kernal flashing in the same session before you boot up..[emoji41]
One last thing.. its dangerous to be
"NEW AT THIS" and just start flashing stuff you need to be carefull and read read read.. in your case W8 you need to flash a kernel 90% of the time same setting..
Sent from my SM-N910T using Tapatalk

@Flashvetrin, +1 on the post, also, this guy may need and must start here.....
http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
AaronBG said:
I'm not really sure what you mean, I'm still relatively new at this.
It wouldn't boot at all, but I managed to install twrp through the recovery. Afterwards I put the rooted stock ROM on the SD card and did a wipe/install from recovery and now it's stuck doing the loop and vibrating twice each time.
I can't figure out how to find that information when I only have access to recovery, it's the Bell version in Canada, SM-N910W8. I had it up to date and just rooted it last night.
Thanks for your quick reply!
Edit: I did change a couple of things with build.prop.editor before it happened, that's what I'm thinking screwed this.
Click to expand...
Click to collapse
And did you happen to back up before making those changes? Anytime you do ANYTHING including sneezing, MAKE A BACKUP!

AxAtAx said:
@Flashvetrin, +1 on the post, also, this guy may need and must start here.....
http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------
And did you happen to back up before making those changes? Anytime you do ANYTHING including sneezing, MAKE A BACKUP!
Click to expand...
Click to collapse
Hes on W8 so unless im mistakin COD6 bootloader and modem will not work.
He can flash the builds but needs a kern to complete the boot... like bio..
And doesnt need the COD6 firmware..
He prob can flash the rom he wanted he just needs to follow it with the kern before he booted...
Easypeasy..[emoji3]
Sent from my SM-N910T using Tapatalk

i just ended up, starting over, doing a stock odin 5.0.2 then re rooting and re installing twrp.
and now it works fine!!