Database Develop

[Q] kernel panic upload mode in ICS rocket rom

Hi,
I was on Rocket Rom V23 and updated to ROCKET ROM - v1 - ICS - XXLPY by following the instructions from portion a) in the post http://forum.xda-developers.com/showthread.php?t=1654838
update was successful but the phone works for 2 mins and then goes to black screen with ''kernel panic upload mode''
i went through lots of post & tried to load stock GB Rom via Odin by when i connect the usb cable its not recognized by Odin.
how can i fix this problem?

Install kies or something to make sure u have all the needed drivers maybe

Are you putting your phone in download mode before connecting the usb cable to the pc and run odin?

@Elusivo: i have the drivers for it as i used the same laptop to do the root
@pakalrtb: yes, im putting the phone in download mode before connecting the usb cable to the pc and running odin as per dr.ketan thread on how to install N7000 stock roms.
do you guys advise me to install stock GB or stock ICS as now rocket rom ICS is installed?
also am i doing the right thing by installing the stock rom to resolve this issue?

I managed to install GB stock rom KK2.
now on the setup page where it asks to press the android to start i keep getting the force close error and cant proceed further.
what should i do?

osam87 said:
I managed to install GB stock rom KK2.
now on the setup page where it asks to press the android to start i keep getting the force close error and cant proceed further.
what should i do?
Click to expand...
Click to collapse
if you are sure to be on GB kernel then
reboot into recovery and wipe , and pray....

@friedje : i reeboted into and tried to do full wipe but its asking me to confirm password which i don't know.

osam87 said:
@friedje : i reeboted into and tried to do full wipe but its asking me to confirm password which i don't know.
Click to expand...
Click to collapse
is that in Recovery Mode, Normal Mode or PC Utility??

antiguangenius said:
is that in Recovery Mode, Normal Mode or PC Utility??
Click to expand...
Click to collapse
Recovery mode

osam87 said:
@friedje : i reeboted into and tried to do full wipe but its asking me to confirm password which i don't know.
Click to expand...
Click to collapse
Only do a cache and dalvik wipe. If that fails, install abyss42 and do your wipe from there. If that still fails, flash another stock GB.
Zapped through server hops to XDA forums

I had mine asking for password which was my 4 digit unlock key that I used for screen unlock, might be assigned to Sim unlock as well.
Sent from my GT-N7000 using xda premium

just to update, i flashed ICS LPY and did wipe cache and full wipe.
all is working fine now.

osam87 said:
just to update, i flashed ICS LPY and did wipe cache and full wipe.
all is working fine now.
Click to expand...
Click to collapse
You're lucky your phone's still alive! Wiping in LPY kernel causes superbrick!!
Sent from my GT-N7000 using XDA

[Q] Install CM for Galaxy S i9000 stuck

Hi All,
I've tried to find the answer but cannot see one specific to what I am experiencing.
I followed the guide from wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Semaphore's ClockworkMod Recovery was not working so I used the file from Replicant's recovery.img as per instructions at bottom of the page.
I followed the instructions. I rooted the phone, but I'm stuck. I can get into the recovery mode but I cannot mount the phone back to the PC so I can put the CM zip file onto the sdcard.
As soon as I turn on the phone, it goes into the CM Recovery menu.
Anyone know how to get the phone to mount to the PC and how I can get a CM image to the phone to install?
Thanks, please help. Need to get this phone working as I want to give it to my daughter to use in Italy.

malvic88 said:
Hi All,
I've tried to find the answer but cannot see one specific to what I am experiencing.
I followed the guide from wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
Semaphore's ClockworkMod Recovery was not working so I used the file from Replicant's recovery.img as per instructions at bottom of the page.
I followed the instructions. I rooted the phone, but I'm stuck. I can get into the recovery mode but I cannot mount the phone back to the PC so I can put the CM zip file onto the sdcard.
As soon as I turn on the phone, it goes into the CM Recovery menu.
Anyone know how to get the phone to mount to the PC and how I can get a CM image to the phone to install?
Thanks, please help. Need to get this phone working as I want to give it to my daughter to use in Italy.
Click to expand...
Click to collapse
Put ur phone in download mode return to stock 2.3.6 then root it again and flash a different ROM or flash a differant kernel using Odin should fix ur problems
Sent from my GT-I9000 using xda premium

kevtrysmoddin said:
Put ur phone in download mode return to stock 2.3.6 then root it again and flash a different ROM or flash a differant kernel using Odin should fix ur problems
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Thanks, but I figured it out late last night. In recovery mode, there is an option to turn on USB mode. With USB on, the PC will see the phone. I downloaded the CM image (zip) to install. Put this into the root folder. Also downloaded the correct Google App as described in the link and put this into the root of the phone.
Turn off the USB. Leave phone plugged into the pc. With recovery mode, select install zip and select the CM zip file you put onto the root. This will install the CM. It will do this twice to convert the phone file system.
Phone will boot up and your in with CM. Now turn off and boot phone into recovery mode again using 3 button method. Select the Google apps zip file to install. This will install the Google Play and other software. Reboot and setup the phone!
Got the Galaxy S i9000 working again!

Help. My device is stuck on boot animation - cwm and twrp will not load

The title says it all.
I went ahead and tried to install Paranoid android RC2, I flash it then subsequently the GApps using TWRP. Now, the device is stuck forever in the boot animation and neither TWRP or CWM (installed with DualZRecovery) will work.
Is there any way by which I can somehow revert what has happened here? This has never happened to me before.
Needless to say if I can avoid having a $400 paperweight, I have sworn to never risk custom roms on my main phone again.

Just flash some kernel with recovery and restore your backup. If you don't have backup, download some of stock or custom roms and flash via Flashtool or recovery......or just use search function

kraseto said:
Just flash some kernel with recovery and restore your backup. If you don't have backup, download some of stock or custom roms and flash via Flashtool or recovery......or just use search function
Click to expand...
Click to collapse
As I said, the main problem is that for some ungodly reason CWM is not working despite the fact that it is what i used to flash PA into the phone in the first place. I have never had a case where CWM itself failed. I need to be in Fastboot mode for flashtool right?
Well the phone wont even go into recovery so im not sure how to get it into fastboot.

1. Download some of newest stock ftf and put it to firmware folder in Flashtool
2. Start Flashtool, press flash btn and pick stock rom
3. Press vol- and connect usb simultaneously and wait about 3 min.
That's it.
Your phone is brand new stock :good:

kraseto said:
1. Download some of newest stock ftf and put it to firmware folder in Flashtool
2. Start Flashtool, press flash btn and pick stock rom
3. Press vol- and connect usb simultaneously and wait about 3 min.
That's it.
Your phone is brand new stock :good:
Click to expand...
Click to collapse
Well I'd come to the same conclusions myself but I thank ye kind ser.

Did u unlock your bootloader when u flashing pa?
Sent from my C6603 using Tapatalk 2

secondkai said:
Did u unlock your bootloader when u flashing pa?
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
I think it was because I forgot to wipe the dalvik cache after installation of the ROM - although why CWM itself stopped working I have no clue.

How did u unlock your bootloader? Flashing aosp base rom require u to unlocked your bootloader first bcos of the custom kernel..if u unlocked your bootloader, did u fastboot flash boot.img?
Sent from my C6603 using Tapatalk 2

[Q] Bricked Galaxy Note GT-N7000 using CWM

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

How can i unbrick my phone? (no usb connection)

I was on NL1 rom, but trynig to use safestrap, i've flashed NC2 kernel.
Because of that my phone doesn't show screen after showing Galaxy note logo.
Everything works fine, but it only doesn't shows screen.
I really want to fix it, but I can't use ODIN to fix my phone.
When i connect it to pc, windows only shows Unknown device(every pc, every cable).
Is there has any way to fix my phone? (using stock recovery... etc).

Can you boot into download mode?

Of course, i can.
But also in Download mode, windows cannot recognize my device. It only says Unknown device.

Wait for pc to install driver completely after booting to download mode is what it sounds like to me. A icon in the windows taskbar tells when it is completed.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

Muzhiwan said:
Of course, i can.
But also in Download mode, windows cannot recognize my device. It only says Unknown device.
Click to expand...
Click to collapse
If Windows is not installing the drivers, then install these drivers. SAMSUNG_USB_Driver_for_Mobile_Phones.exe https://www.androidfilehost.com/?fid=24052804347818748. I always install these drivers on all my computers.

Rooted i747 said:
If Windows is not installing the drivers, then install these [AFH link]. I always install these drivers on all my computers.
Click to expand...
Click to collapse
I've installed Samsung driver to my pc.
And other phones work fine.
Only my phone doesn't work. :crying:
My phone doesn't recognize usb connection when it was working normally. It only charges.

Muzhiwan said:
I've installed Samsung driver to my pc.
And other phones work fine.
Only my phone doesn't work. :crying:
My phone doesn't recognize usb connection when it was working normally. It only charges.
Click to expand...
Click to collapse
Since you flashed the NC2 kernel, restart your phone and see if you see Safestrap splash screen. If you do, then boot to Safestrap and flash this SM-N900A_NL1_KERNEL_RecoveryFlashable.zip https://www.androidfilehost.com/?fid=96042739161891595 from your Sd Card.

Rooted i747 said:
Since you flashed the NC2 kernel, restart your phone and see if you see Safestrap splash screen. If you do, then boot to Safestrap and flash this SM-N900A_NL1_KERNEL_RecoveryFlashable.zip from your Sd Card.
Click to expand...
Click to collapse
After flashing NC1 kernel and installed Safestrap. But i can't see splash screen while on boot.
I tried to flash that but i can't get in safestrap recovery..

Muzhiwan said:
After flashing NC1 kernel and installed Safestrap. But i can't see splash screen while on boot.
I tried to flash that but i can't get in safestrap recovery..
Click to expand...
Click to collapse
Put your phone in download mode and connect it to your computer wait for it to say, unknown device and click the Start icon and type device manager, click to open it and right click to uninstall the drivers (mine shows Bluetooth, but your' s should say unknown device). After you uninstall them, restart your computer and see if that fixes the problem. After you flashed the NC2 Kernel, did you wipe anything in Safestrap or in Stock recovery?

Rooted i747 said:
Put your phone in download mode and connect it to your computer wait for it to say, unknown device and click the Start icon and type device manager, click to open it and right click to uninstall the drivers (mine shows Bluetooth, but your' s should say unknown device). After you uninstall them, restart your computer and see if that fixes the problem. After you flashed the NC2 Kernel, did you wipe anything in Safestrap or in Stock recovery?
Click to expand...
Click to collapse
htt#p://i.imgur.com/QqeeNY0.png (I can't add link due to xda's policy for new users)
Tested on Windows7 and 10. Both of them doesn't work...
After installing safestrap, I cannot see safestrap splash screen while on boot. So I tried wipe data on stock recovery.
Phone boots up, vibration, sound, touch, led notification... everything works except screen.
It only shows screen on Galaxy Note 3 logo, recovery mode, download mode.

Muzhiwan said:
htt#p://i.imgur.com/QqeeNY0.png (I can't add link due to xda's policy for new users)
Tested on Windows7 and 10. Both of them doesn't work...
After installing safestrap, I cannot see safestrap splash screen while on boot. So I tried wipe data on stock recovery.
Phone boots up, vibration, sound, touch, led notification... everything works except screen.
It only shows screen on Galaxy Note 3 logo, recovery mode, download mode.
Click to expand...
Click to collapse
What it needs to boot right, is the NL1 kernel, but Safestrap is gone since you did a wipe with stock recovery. You can't get a computer to see your phone, so you can't flash the kernel in Odin either. Only thing I know to do is do a wipe/factory reset, then do a wipe cache partition in stock recovery. After you do that, see if it boots and if it don't you would have to put this on your Sd Card and apply update from external storage in stock recovery. Instructions to Flash the Lollipop OTA http://www.droidviews.com/update-att-note-3-with-lollipop-ota-and-root-it/. You only need the one file. BUT if you can't use your usb port, you will be stuck on non rooted lollipop. This will either pass or fail, but you can try to flash the NL1 kernel with stock recovery SM-N900A_NL1_KERNEL_RecoveryFlashable.zip (link in post #7).

Rooted i747 said:
What it needs to boot right, is the NL1 kernel, but Safestrap is gone since you did a wipe with stock recovery. You can't get a computer to see your phone, so you can't flash the kernel in Odin either. Only thing I know to do is do a wipe/factory reset, then do a wipe cache partition in stock recovery. After you do that, see if it boots and if it don't you would have to put this on your Sd Card and apply update from external storage in stock recovery. Instructions to Flash the Lollipop OTA http://www.droidviews.com/update-att-note-3-with-lollipop-ota-and-root-it/. You only need the one file. BUT if you can't use your usb port, you will be stuck on non rooted lollipop. This will either pass or fail, but you can try to flash the NL1 kernel with stock recovery SM-N900A_NL1_KERNEL_RecoveryFlashable.zip (link in post #7).
Click to expand...
Click to collapse
I can't use ota update.zip as you know i'm not in stock firmware.
Also can't install NL1 kernel because it used not allowed zip signature on stock recovery.

Muzhiwan said:
I can't use ota update.zip as you know i'm not in stock firmware.
Also can't install NL1 kernel because it used not allowed zip signature on stock recovery.
Click to expand...
Click to collapse
You're just going to have to replace the USB Dock Charger Charging Port Flex Cable, then you can do thing with Odin then.

Rooted i747 said:
You're just going to have to replace the USB Dock Charger Charging Port Flex Cable, then you can do thing with Odin then.
Click to expand...
Click to collapse
I'll try, thanks.