Related
Im trying to do an ics update on my rogers captivate... I have the files i need to get it done but i just cant get it into the rom recovery mode. I know a little about this stuff but not a whole lot (learning as i go along!). I have Recovery 3e on it right now and by the sounds of it, this is not going to work to get it into rom recovery mode... so i downloaded the rom explorer and got a file that was supposed to replace 3e with 2e or something of that matter so i can get it in the right recovery mode to upload ics onto my phone. I moved the file to system/bin and renamed the old recovery file recovery.bak i than moved the other recovery file to the same place and changed the permissions! i rebooted my phone and still nothing! Any help would be greatly apreciatted... and dumb it down a bit so i can understand!
feeze said:
Im trying to do an ics update on my rogers captivate... I have the files i need to get it done but i just cant get it into the rom recovery mode. I know a little about this stuff but not a whole lot (learning as i go along!). I have Recovery 3e on it right now and by the sounds of it, this is not going to work to get it into rom recovery mode... so i downloaded the rom explorer and got a file that was supposed to replace 3e with 2e or something of that matter so i can get it in the right recovery mode to upload ics onto my phone. I moved the file to system/bin and renamed the old recovery file recovery.bak i than moved the other recovery file to the same place and changed the permissions! i rebooted my phone and still nothing! Any help would be greatly apreciatted... and dumb it down a bit so i can understand!
Click to expand...
Click to collapse
Simple way: Download the Heimdall one click in my signature. Backup the stuff on your phone. Go into download mode. Run the one-click. Install the drivers that come with it (it will tell you how). Click the big "flash" button. You will have CWM when it's done, and can flash from there.
^Or you could just flash a kernel with CWM build into it.
The ideal platform for flashing an ICS Rom has to be CWM + Root + Stock GB ROM ( kk4 leak ).
If you got some patience, do it in order.
1. Root your phone.
2. Install CWM recovery.
3. Optional :Flash any GB Rom ( Preferably any one of those captivate leaked roms) using CWM.
4. Download ICS ROM (teamhacksung seems to be stable) and Flash TWICE through CWM
Enjoy
"Thanks" , If I helped you
ROMMaker said:
The ideal platform for flashing an ICS Rom has to be CWM + Root + Stock GB ROM ( kk4 leak ).
If you got some patience, do it in order.
1. Root your phone.
2. Install CWM recovery.
3. Optional :Flash any GB Rom ( Preferably any one of those captivate leaked roms) using CWM.
4. Download ICS ROM (teamhacksung seems to be stable) and Flash TWICE through CWM
Enjoy
"Thanks" , If I helped you
Click to expand...
Click to collapse
rooting your phone is NOT necessary to install CWM.....
Locked
Do not post questions in General, use Q&A.
I know that. But CWM + Root is good for most guys
Have you fixed the issue yet? If not I know about how to fix it
ROMMaker said:
I know that. But CWM + Root is good for most guys
Click to expand...
Click to collapse
if you flash a rom, root is included. rooting your phone is NOT necessary to flash a rom....you do know what ROOT actually is right?
Pirateghost said:
if you flash a rom, root is included. rooting your phone is NOT necessary to flash a rom....you do know what ROOT actually is right?
Click to expand...
Click to collapse
Yes . Root is technically a Linux kernel super user privilege
ROMMaker said:
Yes . Root is technically a Linux kernel super user privilege
Click to expand...
Click to collapse
so then you know that it doesnt matter if you have root or not when you are in CWM, since you arent in an OS....?
therefore, ROOTING is not necessary to flash a new rom..
I also am on rogers and what I did was to use an heimdall 1-click package that flashed CWM for me then I used CWM to flash an ICS build.
Sent from my GT-I9000 using Tapatalk
Did You get this resolved?
If yes, what are the files required, I am new to the android rooting arena
Introduction
Many new users flash Clockwork Mod recovery on thier stock Gingerbread 2.3 roms and then suddenly they realize that they need to root their phone and want to root it. But, when they give it a try they find that they need to have stock recovery to root the device.
And, you shall then need to go through the tedious process of flashing stock firmware just to get back to stock recovery. You will lose all your settings, data, configuration and there are many other drawbacks. But, no more of flashing to stock rom from now on.
With this flashable tar file for stock recovery, you can now be able to revert (or go back) to stock recovery even if you flash CWM recovery with the necessity or going through flashing the whole firmware.
Use it at your own risk!!!
Experimental.... Recommended Testers : Users with stock Gingerbread DDKQ7 firmware
Disclaimer : I shall not be held responsible for any damage caused to you or your device through the use of the knowledge presented here.
Click to expand...
Click to collapse
Download :
Code:
1. stock-recovery-gt-s5570-yagya.tar.md5
http://www.mediafire.com/download.php?f4550044stp9eeg
Pass : [B]yagyagaire[/B]
See, next post for instructions on installing or using it.
Instructions on Flashing Stock Recovery!
So, let's begin.
Download Odin Multidownloader v4.38 for GTS5570, Tass_v1.ops and stock GB Recovery if you do not have them already. You can download them from here.
Run Odin Multi downloader v4.38 and select the Tass_v1.ops by clicking OPS button.
Select One Package Option and Click One Package button and select the stock recovery file name (stock-recovery-gt-s5570-yagya.tar.md5) file you downloaded.
Leave other settings to default (i.e. don’t change any other options/settings)
When you are done reboot your phone in download mode (Press Volume Down + Home + Power button to go to download mode)
Connect your phone in download mode to your computer via USB Cable.
When Odin detects your phone (If you see a com port number written in yellow background at the top left, then your phone is detected. View image.), click Start button.
Wait till Odin finishes the job (approx. 3-5 minutes) and when it reports ‘PASS’, you can disconnect your phone.
That's all. You have flashed back to stock recovery without having to flash a whole new firmware on your device.
Now, reboot to recovery mode (press Home + Power button) and see if your recovery changed to stock or not. Don't forget to share the result with us at the post below.
Source : This guide is taken from - http://yagyagaire.blogspot.com/2011/09/installing-clock-work-mod-recovery-in.html
Reserved For Future Use!!
--------------
nishanty13 said:
Why the hell would you need stock recovery to root your device ??
Click to expand...
Click to collapse
This is only for those who want it so, you can stay back if you don't need it. I want no spam in this thread.
AS you can read here http://yagyagaire.blogspot.com/2011/12/rooting-samsung-galaxy-pop-with.html those who doesn't want to install custom rom need stock recovery to root their device since the rooting scripts written till now, only work with stock one.
So, those who flashed CWM recovery but now wants to return to stock recovery since they are not going to flash any custom rom will use this to return to stock GB recovery.
yagya said:
This is only for those who want it so, you can stay back if you don't need it. I want no spam in this thread.
AS you can read here http://yagyagaire.blogspot.com/2011/12/rooting-samsung-galaxy-pop-with.html those who doesn't want to install custom rom need stock recovery to root their device since the rooting scripts written till now, only work with stock one.
So, those who flashed CWM recovery but now wants to return to stock recovery since they are not going to flash any custom rom will use this to return to stock GB recovery.
Click to expand...
Click to collapse
Sorry . No offence dude.
I didn't mean to be rude. I was just a little off that time.
I was just saying that there would be very little or negligible percentage of people that would go back to stock recovery.
And also if they have flashed GB they would themselves get stock recovery. And I think no CM or custom rom user would prefer stock recovery.
I guess it would be really very helpful in case if phone has any hardware problem and in warranty, so may be flashing stock recovery and then sending it back would help.
It is helpful.
jdwis said:
I guess it would be really very helpful in case if phone has any hardware problem and in warranty, so may be flashing stock recovery and then sending it back would help.
It is helpful.
Click to expand...
Click to collapse
In that case its better to flash stock rom
Sent from my GT-S5570 using xda premium
nishanty13 said:
Sorry
And also if they have flashed GB they would themselves get stock recovery. And I think no CM or custom rom user would prefer stock recovery.
Click to expand...
Click to collapse
Well not a problem.
No read carefully what you have written and what I am telling below. Yes, they will get stock recovery after flashing GB. But, the aim/focus here is to get stock recovery with out flashing GB firmware.
If you can get it, then all right. Otherwise, I would suggest us to stop this and leave it here only.
I wanted to share this since I got few request for this, and it's here now and those who want can use and those who doesn't can simply ignore it.
there is a typo in the first post.
I dont understand, if u want to reduce the tediousness then just make a flashable zip of the recovery. Why odin? They are using a custom recovery after all.
Hold it. There a ppl using cwm on stock roms!! What are they using it for without rfs support?
roofrider said:
there is a typo in the first post.
I dont understand, if u want to reduce the tediousness then just make a flashable zip of the recovery. Why odin? They are using a custom recovery after all.
Hold it. There a ppl using cwm on stock roms!! What are they using it for without rfs support?
Click to expand...
Click to collapse
Well, I understand flashing it in CWM is a good idea. So, I will update provide an zip soon.
There's no need to hold it . LOL! New users are not learned like you are, so they flash it. Later they want to revert back but find that they will need to flash whole rom , that will erase all data and apps. But, with this they can only change the recovery to stock.
mount system?
is it able to mount system on stock firmware 2.3.6 XWKTN?
addyhardiana said:
is it able to mount system on stock firmware 2.3.6 XWKTN?
Click to expand...
Click to collapse
Never..
Sent by Mister Mini ®
Help, my Note is stuck on the boot logo after trying to install a custom rom.
I have tried several roms now and non of them pass the boot screen. Getting a little scared now.
Here are the steps I have taken. Please tell me if I'm doing something wrong.
Stock rom
Root and install clockwork mod
nandroid backup
flash abyss kernal
wipe data
wipe cache
install custom rom
stuck on boot logo
I have just tried restoring the nandroid backup and the same thing happens... stuck on boot logo
Have I bricked the phone?
I can still access clockwork if that's any help.
I'm trying a restore via pc odin now.
Not got much hope though, seems to be stuck. The bar doesn't move anymore :'(
Hope an expert will assist.
What stock rom are you on, is it ics? If so nandroid backups and restores are dangerous on stock kernel.
Try flashing stock gb with pc Odin and go from there. If it fails, post at what point ie factory.fs.
Sent from my GT-N7000 using xda premium
K1LLER HORNET said:
....Stock rom
Root and install clockwork mod
nandroid backup
flash abyss kernal
wipe data
wipe cache
install custom rom
stuck on boot logo
......
Click to expand...
Click to collapse
Did you use CWM.zip to root your phone and flash Abyss?
Did you do wipe while still on Temp CWM?
If the answer is yes to both, you are Superbricked
Sent from my GT-N7000 using xda app-developers app
K1LLER HORNET said:
Help, my Note is stuck on the boot logo after trying to install a custom rom.
I have tried several roms now and non of them pass the boot screen. Getting a little scared now.
Here are the steps I have taken. Please tell me if I'm doing something wrong.
Stock rom
Root and install clockwork mod
nandroid backup
flash abyss kernal
wipe data
wipe cache
install custom rom
stuck on boot logo
I have just tried restoring the nandroid backup and the same thing happens... stuck on boot logo
Have I bricked the phone?
I can still access clockwork if that's any help.
Click to expand...
Click to collapse
After flashing abyss kernel have you rebooted to recovery to do all 3 wipes. ?
SpyderTracks said:
What stock rom are you on, is it ics? If so nandroid backups and restores are dangerous on stock kernel.
Try flashing stock gb with pc Odin and go from there. If it fails, post at what point ie factory.fs.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Yes it was stock ICS
I think I tried flashing stock GB. Odin just stops at a certain point; yes it's at factory.fs...
shoey63 said:
Did you use CWM.zip to root your phone and flash Abyss?
Did you do wipe while still on Temp CWM?
If the answer is yes to both, you are Superbricked
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I might have flashed Abyss while on temp. Can't really remember.
What do I do now?
Anything else I can try?
Get Amazon to replace it?
Edit: I can't seem to get into clockwork recovery anymore. It just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
But I can get into the 'downloading' mode.
Help.
Wipes using Temp CWM.zip will result in brick
''Odin just stops at a certain point; yes it's at factory.fs''
that means you have bricked your phone.
So what can I do now?
Return to Samsung/Amazon?
Will they know that it was my fault?
Warranty
Go to recovery mode and check whether its showing binary counter 1 or above, ''Staus'' Official or Custom
If binary count is 0 and status is official you will get warranty
tell service center people that while updating new update via ota , your phone bricked
deleted
Flash GB
just pull out the battery. wait for 10 secs.. reinsert. go back to download mode..
use odin 1.85 and just select the tar.md5 fine in pda section..
Flash Gingerbread rom.
anoopva said:
Go to recovery mode and check whether its showing binary counter 1 or above, ''Staus'' Official or Custom
If binary count is 0 and status is official you will get warranty
tell service center people that while updating new update via ota , your phone bricked
Click to expand...
Click to collapse
It says:
Custom Binary Download: No
Current Binary: Samsung Official.
So I take it that's good right?
nokiamodeln91 said:
May be try installing one of the gb roms
Click to expand...
Click to collapse
anoopva said:
just pull out the battery. wait for 10 secs.. reinsert. go back to download mode..
use odin 1.85 and just select the tar.md5 fine in pda section..
Flash Gingerbread rom.
Click to expand...
Click to collapse
I will try that in the next 20 mins once the stock rom downloads.
To stop this happening again, could someone please, please, please post some noob friendly instructions on how I should flash a custom rom from stock.
I know someone might say 'just google it' or 'there are plenty of guides out there', but I was sure I had the steps nailed down otherwise I wouldn't have tried it.
It would be very helpful.
Especially to see exactly where I went wrong.
Anyway, thanks for all the info.
[STOCK ROMS] N7000 All stock ROMs + install + Root guide All at 1place,Latest 4.0.4
[STOCK ROMS] N7000 All stock ROMs + install + Root guide All at 1place,Latest 4.0.4
http://forum.xda-developers.com/showthread.php?t=1424997
anoopva said:
[STOCK ROMS] N7000 All stock ROMs + install + Root guide All at 1place,Latest 4.0.4
http://forum.xda-developers.com/showthread.php?t=1424997
Click to expand...
Click to collapse
Yeah, I'm getting the stock GB (UK) rom from there.
Taking a while as a free user.
Thanks.
My Way of root + cwm (i have checked this in ICS only )
1. flashing safe kernels like hydracore 5.4 or Philz kernel 2.7 using PC odin
2. reboot
3. now you have root + CMW
4. open super su / superuse app
5. check for root access using Root Checker
6. Flash Supersu.zip in CMW if experience any root issues
7. now will be having stock ics with safe kernel and cwm.
anoopva said:
1. flashing safe kernels like hydracore 5.4 or Philz kernel 2.7 using PC odin
2. reboot
3. now you have root + CMW
4. open super su / superuse app
5. check for root access using Root Checker
6. Flash Supersu.zip in CMW if experience any root issues
7. now will be having stock ics with safe kernel and cwm.
Click to expand...
Click to collapse
Then what do I do?
Sorry, want to be as clear as possible.
Flashing Any Custom Roms
1. Flash Any Safe Kernel and reboot to recovery
2. do all 3 wipes (wipe data/factory, wipe cache partition, wipe dalvik cache)
3. Flash custom rom.zip
4. reboot
5. enjoy new custom rom
@ anoopva
Thank you for all your valuable info.
I may put it to use if I have the courage to risk a replacement phone.
Will update thread shortly on how flashing to GB goes.
I won't hold my breath.
You won't be able to flash a ROM anymore. Odin will get stuck. DO NOT attempt to flash a custom kernel through PC Odin. It will RAISE your flash counter and then it will be obvious that you have messed with your phone, so warranty will be voided! There is another way to get recovery, just wait.....
shoey63 said:
You won't be able to flash a ROM anymore. Odin will get stuck. DO NOT attempt to flash a custom kernel through PC Odin. It will RAISE your flash counter and then it will be obvious that you have messed with your phone, so warranty will be voided! There is another way to get recovery, just wait.....
Click to expand...
Click to collapse
Yes, just found that it got stuck.
Got further than with the stock ICS rom.
So do I have any options other than to return the phone?
hi
i will remove cwm from my handy.... i will make it original, how can i make it ?
sorry for my bad english
Download the cwm flashable file from here and flash it in cwm.You will have your original recovery back.
Download the stock recovery from HERE and flash it with CWM and you will have original stock recovery.
perfekt
Can I do this proccess with a Sony Xperia??
Enviado desde mi ST23i usando Tapatalk 2
miguelSony said:
Can I do this proccess with a Sony Xperia??
Enviado desde mi ST23i usando Tapatalk 2
Click to expand...
Click to collapse
Not with the files posted here.
Hi! I flashed I8190_stock-recovery-flashable.zip, but Rom Manager still write:
Recovery Setup
Current Recovery: ClockworkMod 6.0.2.7
Whats wrong?
somin.n said:
Hi! I flashed I8190_stock-recovery-flashable.zip, but Rom Manager still write:
Recovery Setup
Current Recovery: ClockworkMod 6.0.2.7
Whats wrong?
Click to expand...
Click to collapse
I don't know about rom manager as I don't really use it. Probably because it was the last known recovery..
Reboot to recovery and have a look..
tys0n said:
I don't know about rom manager as I don't really use it. Probably because it was the last known recovery..
Reboot to recovery and have a look..
Click to expand...
Click to collapse
Thanks for quick reply. It looks that it is there (in fact, I never seen stock recovery before, but now it looks different like cwm), but I can access it only via RomManger... Is there other way how to boot in stock recovery? I can boot in download mode (menu + volume down + power), but in this mode i can't do anything ... :/
edit:
I found [GUIDE] How to reboot in recovery, so maybe it is not only my problem
somin.n said:
Thanks for quick reply. It looks that it is there (in fact, I never seen stock recovery before, but now it looks different like cwm), but I can access it only via RomManger... Is there other way how to boot in stock recovery? I can boot in download mode (menu + volume down + power), but in this mode i can't do anything ... :/
edit:
I found [GUIDE] How to reboot in recovery, so maybe it is not only my problem
Click to expand...
Click to collapse
Good. Yeah, its different, and rommanager isn't compatible with stock recovery. You won't be able to flash anything but samsung-signed updates.
Not able to boot to recovery is well known. Good you found out. Have a look here..http://forum.xda-developers.com/showthread.php?t=2157105 for an easy way to enable three button combination :good:
tys0n said:
Good. Yeah, its different, and rommanager isn't compatible with stock recovery. You won't be able to flash anything but samsung-signed updates.
Not able to boot to recovery is well known. Good you found out. Have a look here..http://forum.xda-developers.com/showthread.php?t=2157105 for an easy way to enable three button combination :good:
Click to expand...
Click to collapse
Hehe, if I set reboot to recovery in RomManger after updating from cwm back to stock recovery, it reboot me in to Stock recovery
Btw, will flashing that 2MB file from "[HOW-TO] Enable Three Button Combo [RECOVERY]" increase binary counter? I know about TriangleAway, but for sure...
And one more question please. My story...
- I flashed pre-rooted 4.1.1 fw via odin
- than i installed RomManger and via it I install CWM
- than become 4.1.2 fw so I flashed this pre-rooted fw via odin - everything was good, phones restart after flash but boot in CWM??? Everything works good, but I was thinking, that with new fw the CWM will gone?!?
Trying to understand how android works (this is my first android phone, before that i had only symbian devices), i read many topic about s iii mini and it looks, that this phone in "unusual" android phone
somin.n said:
Hehe, if I set reboot to recovery in RomManger after updating from cwm back to stock recovery, it reboot me in to Stock recovery
Btw, will flashing that 2MB file from "[HOW-TO] Enable Three Button Combo [RECOVERY]" increase binary counter? I know about TriangleAway, but for sure...
And one more question please. My story...
- I flashed pre-rooted 4.1.1 fw via odin
- than i installed RomManger and via it I install CWM
- than become 4.1.2 fw so I flashed this pre-rooted fw via odin - everything was good, phones restart after flash but boot in CWM??? Everything works good, but I was thinking, that with new fw the CWM will gone?!?
Trying to understand how android works (this is my first android phone, before that i had only symbian devices), i read many topic about s iii mini and it looks, that this phone in "unusual" android phone
Click to expand...
Click to collapse
Yeah, it will let you reboot to recovery but that's all. No flashing, no backups or anything. Kinda sad to install an app just to reboot :silly:
You probably have to use triangle away after that file even though the files are taken out of service-firmware, but it only takes a minute.
These firmwares doesn't normally include recovery..don't know why. Thats what I'm used to from other models, but not for this one.
Hey Guys. Greetings. I wanted to update my galaxy note [GT-N7000, India] to Android OMNIRom 4.4.2 Kitkat nightly build from Android 4.1.2 [Kernel version DDLSC]. Following steps led to bricking my phone:-
1. I first installed philz custom kernel [Version DDLSC CWM version 6.0.3.7] so that I could have CWM and SU.
2. Then I went to CWM Recovery mode, did factory reset. Then Wipe Cache. Then Wipe Dalvik Cache. Then I tried applying the omnirom update. It failed and gave me some context error and status 7.
3. Then I restored my 4.1.2 image using the CWM recovery only.
4. I booted into 4.1.2 and tried updating the CWM to 6.0.4.3 using ROM Manager. It succeded.
5. I went back again to recovery mode but it said again 6.0.3.7.
6. I tried applying update to CWM from CWM itself. It stuck at something like “replacing the stock recovery….”.
7. I powered off my phone. It went into boot loop once but somehow it started.
8. Then again I went into ROM manager and selected Boot into recovery mode.
9. It bricked my phone. Unable to boot since then. I cannot access recovery mode but I can access download/ODIN mode.
Here’s what I tried to do.
1. Downloaded CWM 6.0.4.3 touch .zip from clockworkmode.com
2. Renamed it to recovery.img.
3. Converted it to tar.md5 using img to tar tool.
4. Using Odin version 3.07, I tried flashing CWM.6.0.4.3.tar.md5 It stucks at NAND Write start.
Please help me recover my phone.
Specs: Samsung Galaxy NOTE GT-N7000
Original firmware: 4.1.2 kernelDLSC
16 GB internal usb storage
Country India.
chirags1986 said:
Bricked Galaxy Note GT-N7000 using CWM
Click to expand...
Click to collapse
Few things you should have already read and understood.
1. Note N7000 doesn't have a separate active recovery partitions as the S3 and so on.. The recovery is built in to the kernel. So flashing Philz was a correct step.
2. You cannot update the recovery using ROM manager as it writes to the recovery partition which this phone doesn't use. Thus you didn't get the updated recovery.
3. Using odin will not work due to 1&2
Download the Philz kernel DDLC tar version and flash using Odin (uncheck Auto reboot). Once it shows Pass, then power off the phone and remove the usb cable. Boot into recovery using the vol up+home+power. The flash a kernel like Raw r4/r5. reboot into recovery and wipe. Flash Omni, Gapps, SU. Reboot.
Revive your phone by flashing stock firmware using.
So its not really "Bricked Galaxy Note GT-N7000 using CWM" but bricked due to sheer ignorance.
my device bricked
nokiamodeln91 said:
Few things you should have already read and understood.
1. Note N7000 doesn't have a separate active recovery partitions as the S3 and so on.. The recovery is built in to the kernel. So flashing Philz was a correct step.
2. You cannot update the recovery using ROM manager as it writes to the recovery partition which this phone doesn't use. Thus you didn't get the updated recovery.
3. Using odin will not work due to 1&2
Download the Philz kernel DDLC tar version and flash using Odin (uncheck Auto reboot). Once it shows Pass, then power off the phone and remove the usb cable. Boot into recovery using the vol up+home+power. The flash a kernel like Raw r4/r5. reboot into recovery and wipe. Flash Omni, Gapps, SU. Reboot.
Revive your phone by flashing stock firmware using.
So its not really "Bricked Galaxy Note GT-N7000 using CWM" but bricked due to sheer ignorance.
Click to expand...
Click to collapse
i flash philz kernel
then i wanted to flash cm11 so
i wiped data
wiped cache
wiped system
wiped dalvik
then i selected cm11 and it showed error status7
so i restored my backup rom
now i restarted my device and it says system ui has stopped..
amiransari2 said:
i flash philz kernel
then i wanted to flash cm11 so
i wiped data
wiped cache
wiped system
wiped dalvik
then i selected cm11 and it showed error status7
so i restored my backup rom
now i restarted my device and it says system ui has stopped..
Click to expand...
Click to collapse
nokiamodeln91 said:
Download the Philz kernel DDLC tar version and flash using Odin (uncheck Auto reboot). Once it shows Pass, then power off the phone and remove the usb cable. Boot into recovery using the vol up+home+power. The flash a kernel like Raw r4/r5. reboot into recovery and wipe. Flash Omni, Gapps, SU. Reboot.
Click to expand...
Click to collapse
Again you did not read properly.
bricked galaxy note gt n7000 using cwm
nokiamodeln91 said:
Again you did not read properly.
Click to expand...
Click to collapse
srry but i have flashed stock rom using odin now my prob is solved.......but why that prob incurred
Hello Sir,
I have the same problem as that guy above. I am unable to boot into download mode itself. How can I connect to odin? Please help sir.
nokiamodeln91 said:
Few things you should have already read and understood.
1. Note N7000 doesn't have a separate active recovery partitions as the S3 and so on.. The recovery is built in to the kernel. So flashing Philz was a correct step.
2. You cannot update the recovery using ROM manager as it writes to the recovery partition which this phone doesn't use. Thus you didn't get the updated recovery.
3. Using odin will not work due to 1&2
Download the Philz kernel DDLC tar version and flash using Odin (uncheck Auto reboot). Once it shows Pass, then power off the phone and remove the usb cable. Boot into recovery using the vol up+home+power. The flash a kernel like Raw r4/r5. reboot into recovery and wipe. Flash Omni, Gapps, SU. Reboot.
Revive your phone by flashing stock firmware using.
So its not really "Bricked Galaxy Note GT-N7000 using CWM" but bricked due to sheer ignorance.
Click to expand...
Click to collapse
techblazes said:
Hello Sir,
I have the same problem as that guy above. I am unable to boot into download mode itself. How can I connect to odin? Please help sir.
Click to expand...
Click to collapse
So no download and recovery mode? Is your battery charged?
nokiamodeln91 said:
So no download and recovery mode? Is your battery charged?
Click to expand...
Click to collapse
I got the download mode after removing and replacing the battery sir. But ODIN is not showing Added message when I connect my device...
techblazes said:
I got the download mode after removing and replacing the battery sir. But ODIN is not showing Added message when I connect my device...
Click to expand...
Click to collapse
Try different USB port, cables, and check if the drivers are installed properly.. Samsung USB drivers..
Looks like the drivers are working back after using Kies. Now I connected the device and ODIN is doing its task. Will update if it successfully finishes the job.
Thanks
Edit: Everything is working as expected. ODIN has flashed CWM on my device and now I am restoring my device using the backup I created yesterday...
Got into the same problem as the OP. Wiped everyting and only have Phliz recovery. Couldn't flash CM11 because according to CM thread must have latest version of CWM (6.0.3.4) while the philz recovery I installed is based on 6.0.2.7. Couldn't flash newer recovery I downloaded from CWM site, it would just freeze and get stuck.
My solution is to just flash CM10.1.3 stable plus gapps. Worked fine. Then proceed from there.
You must have CWM 6.0.4.4 or higher, which is fully SELinux compatible for KitKat.
Just flash Raw kernel r4, reboot in recovery (of raw kernel ) and then do your flash and wipes.
You can't simply install a newer recovery on our device, as kernel and recovery are bound together, but ...THIS IS BASIC KNOWLEDGE FOR OUR DEVICE!!!
#fail²
Just resurrecting this!
After failing to flash KitKat because I had Philz kernel installed, I've got into a real mess.
I'm trying to flash raw kernel r5 but recovery isn't able to mount the SD card and so can't see the zip files on it.
I'm on a Mac and don't have Bootcamp so can't use Odin. Any suggestions?
Oops didnt realise this was kinda necroed :/
Same problem...i have brisked my N7000
i want to know where you have got stock ROM 4.1.2....please help me sir. regards,
manojleo79 said:
i want to know where you have got stock ROM 4.1.2....please help me sir. regards,
Click to expand...
Click to collapse
Go find what you want Here
chirags1986 said:
Here’s what I tried to do.
1. Downloaded CWM 6.0.4.3 touch .zip from clockworkmode.com
2. Renamed it to recovery.img.
3. Converted it to tar.md5 using img to tar tool.
4. Using Odin version 3.07, I tried flashing CWM.6.0.4.3.tar.md5 It stucks at NAND Write start.
Please help me recover my phone.
Specs: Samsung Galaxy NOTE GT-N7000
Original firmware: 4.1.2 kernelDLSC
16 GB internal usb storage
Country India.
Click to expand...
Click to collapse
No need to do all this ^
Flash this using ODIN. Pick the tar file
techblazes said:
Looks like the drivers are working back after using Kies. Now I connected the device and ODIN is doing its task. Will update if it successfully finishes the job.
Thanks
Edit: Everything is working as expected. ODIN has flashed CWM on my device and now I am restoring my device using the backup I created yesterday...
Click to expand...
Click to collapse
Hi all,
I too have the same problem, tried following as instructed
- Download the Philz kernel DDLC tar version (PhilZ-cwm6-DDLSC-ODD-5.11.2.tar)
- flashed using Odin by unchecking Auto reboot option
- Once it showed Pass( it also showed RESTE then went on to became green), then power off the phone and removed the usb cable.
- Tried to boot into recovery by using the vol up+home+power
unfortunately got stuck in the initial screen with yellow triangle
Kindly help
---------- Post added at 04:22 AM ---------- Previous post was at 04:07 AM ----------
techblazes said:
Looks like the drivers are working back after using Kies. Now I connected the device and ODIN is doing its task. Will update if it successfully finishes the job.
Thanks
Edit: Everything is working as expected. ODIN has flashed CWM on my device and now I am restoring my device using the backup I created yesterday...
Click to expand...
Click to collapse
Hi all,
I am new to XDA, and has been following XDA for ROM upgradation on my GTN7000 Samsung note
But today I have landed in the problem when I tried to upgrade the CWM through ROM manager. May be because of half knowledge.
After searching on the XDA I came across above thread identical to the issue I am facing wit same note config, with a great relief I tried to replicate the same for my N7000
steps followed.
- Download the Philz kernel DDLC tar version (PhilZ-cwm6-DDLSC-ODD-5.11.2.tar)
- flashed using Odin by unchecking Auto reboot option
- Once it showed Pass( it also showed RESTE then went on to became green), then power off the phone and removed the usb cable.
- Tried to boot into recovery by using the vol up+home+power
unfortunately got stuck in the initial screen with yellow triangle
Kindly help.
Hi Experts,
please help. I am still stuck with yellow triangle and samsung logo.
Regards
n7000g said:
Hi Experts,
please help. I am still stuck with yellow triangle and samsung logo.
Regards
Click to expand...
Click to collapse
Try downloading XXLTA stock firmware. Flash it with odin, after finished reboot to stock recovery n do a factory wipe reset, reboot. After that download phils XXLTA kernel and flash it in stock recovery. It will give u root n phils recovery. After that u can do whatever u want with ur phone
Sent from my GT-N7000 using XDA Free mobile app