[Q] Troublehooting with bricked Galaxy Note needed - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?

Try an older philz. That one you used is to new gor Stock Samsung Rom. What rom is currently installed?

grosserzampano said:
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Click to expand...
Click to collapse
The phone doesn't boot because the kernel you flashed is a kitkat kernel.
You should have recovery mode. Try to remove the battery for couple of seconds and then try to get into recovery. If still no go..
Go to Philz thread and look for tw kernels link. Go there and flash XXLTA kernel using odin. Now try recovery mode again.

User_99 said:
Try an older philz. That one you used is to new gor Stock Samsung Rom. What rom is currently installed?
Click to expand...
Click to collapse
I have the Stock Samsung Android 4.1.2 installed. I'll try it again with an older kernel. Thanks for your help.

nokiamodeln91 said:
The phone doesn't boot because the kernel you flashed is a kitkat kernel.
You should have recovery mode. Try to remove the battery for couple of seconds and then try to get into recovery. If still no go..
Go to Philz thread and look for tw kernels link. Go there and flash XXLTA kernel using odin. Now try recovery mode again.
Click to expand...
Click to collapse
I tried it several times, also after removing the battery. no success. Is is necessary to use ODIN? I use Heimdall as I mentioned, because I am running Mac OS.
I'll try it with a different kernel and report back here about my results. Thanks a lot.

Thanks for your help. I searched through that Philz Thread and found the link to the older kernels. Then I picked this version after asking google for a compatible kernel with N7000 Samsung Rom Android 4.1.2.
Kernel PhilZ-cwm6-XXLTA-ATL-5.15.0
I flashed it with Heimdall and finally the device boots again. Still not able to boot into Clockworkmod. Device does not enter Recovery mode at all. But at least I have a working device for now again.

What
grosserzampano said:
Thanks for your help. I searched through that Philz Thread and found the link to the older kernels. Then I picked this version after asking google for a compatible kernel with N7000 Samsung Rom Android 4.1.2.
Kernel PhilZ-cwm6-XXLTA-ATL-5.15.0
I flashed it with Heimdall and finally the device boots again. Still not able to boot into Clockworkmod. Device does not enter Recovery mode at all. But at least I have a working device for now again.
Click to expand...
Click to collapse
Install terminal emulator and try the command
su
reboot recovery.

Now that is weird. After the device booted again I seemed to lost root access to the device. I tried to get root again with Framaroot, also installed SuperUser again since it was magically deinstalled. Now the device booted into the logo with the yellow triangle and then the screen turned black. Nothing happened from there.
Fortunately I had the idea to use adb on the device before trying to flash an original Samsung Rom back on the device out of pure despair. adb listed the device and stated that the device is in recovery mode. It seems that the device always booted into recovery, altough I tried to boot normally. Recovery still not working. But using "adb reboot" helped to reboot the device again.
Trying to start in recovery mode, i.e. with adb reboot recovery always ends up in a black screen. Somehow this is broken.
I think I have to go back to zero and try to follow a good guide from the beginning without mixing several guides.

grosserzampano said:
Now that is weird. After the device booted again I seemed to lost root access to the device. I tried to get root again with Framaroot, also installed SuperUser again since it was magically deinstalled. Now the device booted into the logo with the yellow triangle and then the screen turned black. Nothing happened from there.
Fortunately I had the idea to use adb on the device before trying to flash an original Samsung Rom back on the device out of pure despair. adb listed the device and stated that the device is in recovery mode. It seems that the device always booted into recovery, altough I tried to boot normally. Recovery still not working. But using "adb reboot" helped to reboot the device again.
Trying to start in recovery mode, i.e. with adb reboot recovery always ends up in a black screen. Somehow this is broken.
I think I have to go back to zero and try to follow a good guide from the beginning without mixing several guides.
Click to expand...
Click to collapse
May be the recovery partition is messed up due to the usage of rom manager earlier. Try to flash a stock rom.

grosserzampano said:
Ok ,
I tried to extend the lifetime of my Galaxy Note through replacing the official (sloooow) rom with a custom one. I read so many how-to's online that I got confused. Here is what I did:
First I rooted my phone.
Then I installed CWM via RomManager, which did not work. Altough Rommanager shows an installed CWM the phone always start into Stock Recovery.
I learned that the N7000, in order to use CWM needs a flashed kernel.
I flashed the kernel via Heimdall (Mac OS) with this philz_touch_6.48.4-n7000.tar.md5.
The flashing went successfull (according to Heimdall), and the phone rebooted automatically, but all I see since then is the Samsung Logo (Samsung Galaxy Note GT-N7000) and a yellow triangle. From there is goes nowhere. I can enter Download Mode, but is does not boot. Also no Recovery Mode. Weird.
Any advice where to take it from here? Do I have to flash back the original kernel?
Click to expand...
Click to collapse
go to download mode and flash stock rom of note 1 via odin then after successful installation u can go to recovery mode and install this zip ur phone will be rooted and phliz touch will be installed
for any help u can PM me

Related

[Q] Tab Missing Recovery?

Hello all..
So I picekd up a t-mobile tab off craigslist yesterday, which was pre-rooted (no superuser though) and has the Roto JMI rom (if that's what it is) installed with the 2.6.32.9 [email protected] #1 kernel.
Last night I tried rooting/installing CWM with the one click thing, run.bat or run.sh in my case since I'm on a mac. It wouldn't work and got stuck in a recovery loop. Every time I would boot, it would go straight to recovery. So I managed to get a data wipe done and now I'm back to the way it was before.
I rooted it with SimpleOneClick and it's rooted with superuser now. I've installed rom manager, tried to flash CWM, but when I do it just says successfully installed CWM.
When I try to boot to recovery, it just stops at the 'Galaxy Tab' loading screen. No stock recovery, no CWM, no nothing. The only way to get it out of this mode is to issue an ./adb reboot bootlaoder command. After I do that, it works fine. Can start up, shut down etc.
What did I do??? Is there any way to flash the recovery via adb push like I did the first time I rooted my phone? I can't seem to find the recovery to push to the phone, so yeah.. I'm confused here.
Thanks!!
sanchez said:
Hello all..
So I picekd up a t-mobile tab off craigslist yesterday, which was pre-rooted (no superuser though) and has the Roto JMI rom (if that's what it is) installed with the 2.6.32.9 [email protected] #1 kernel.
Last night I tried rooting/installing CWM with the one click thing, run.bat or run.sh in my case since I'm on a mac. It wouldn't work and got stuck in a recovery loop. Every time I would boot, it would go straight to recovery. So I managed to get a data wipe done and now I'm back to the way it was before.
I rooted it with SimpleOneClick and it's rooted with superuser now. I've installed rom manager, tried to flash CWM, but when I do it just says successfully installed CWM.
When I try to boot to recovery, it just stops at the 'Galaxy Tab' loading screen. No stock recovery, no CWM, no nothing. The only way to get it out of this mode is to issue an ./adb reboot bootlaoder command. After I do that, it works fine. Can start up, shut down etc.
What did I do??? Is there any way to flash the recovery via adb push like I did the first time I rooted my phone? I can't seem to find the recovery to push to the phone, so yeah.. I'm confused here.
Thanks!!
Click to expand...
Click to collapse
Not sure about t-mobile tabs (I've heard they can be a bit tricky) but if you can install Modaco/paulobrian kernel (thread in the dev section) then that has a fully working CWM built in. Backups and restores work perfectly with this. The "official" one from koush (sp) is abandonware...
paulshields said:
Not sure about t-mobile tabs (I've heard they can be a bit tricky) but if you can install Modaco/paulobrian kernel (thread in the dev section) then that has a fully working CWM built in. Backups and restores work perfectly with this. The "official" one from koush (sp) is abandonware...
Click to expand...
Click to collapse
I actually just got it all set up after trying many things using this thread:
http://forum.xda-developers.com/showthread.php?p=11713685
Worked like a champ.
sanchez said:
I actually just got it all set up after trying many things using this thread:
http://forum.xda-developers.com/showthread.php?p=11713685
Worked like a champ.
Click to expand...
Click to collapse
Excellent .

Stuck in boot screen with no recovery

I had a russian stock 4.1.3 firmware on my i9070 with standard samsung recovery and it was kinda buggy(Google Play wouldn't work) and I decided to flash TWRP (yes, I now realize it couldn't have worked since it is for gingerbread) and I got stuck in boot screen with no recovery. The only solution I could think of is to flash stock JB again, so I downloaded stock Romania(Cosmote) Firmware and tried to flash it with both Odin v1.87(with and without pit file) and v3.07 and Odin gave me a PASS each time, but I am still stuck in boot screen with no recovery.
Clearly I am doing something wrong, and it probably is something I should have read somewhere, but there are so many details that I don't know where to start looking...
Later Edit:
It finally booted! Sorry for the new thread.
I don't know why it wasn't working with the Romanian firmware but I used the Greece one and it works fine.
Hi, my friend is facing same problem. Its showing PASS always.
But, its not booting to custom recovery.
It goes to samsung recovey and says "Downloading"
How you got it cleared? Do u need to wait at that previous screen?
aby2aby said:
Hi, my friend is facing same problem. Its showing PASS always.
But, its not booting to custom recovery.
It goes to samsung recovey and says "Downloading"
How you got it cleared? Do u need to wait at that previous screen?
Click to expand...
Click to collapse
If you are flashing custom recovery, but you still have stock Samsung recovery, you are clearly doing something wrong.
When I flashed custom recovery, I had JellyBean Android installed and the recovery was made to work with Gingerbread, so it wouldn't boot recovery at all.
Since you are still getting the standard Samsung recovery, you haven't flashed the custom recovery correctly.
I suggest you retrace your steps and find some tutorial that could help you with your problem HERE.
When I couldn't access recovery, I just flashed stock JellyBean again with Odin.

I9001 bricked/soft-bricked, please help

Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
zerkylo said:
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
Click to expand...
Click to collapse
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
kalpetros said:
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
Click to expand...
Click to collapse
Thank you for answering!
I fixed the issue. Tried different usb port along with a different version of CWM (5.5.0.4) which I installed with Odin v4.43. CWM 5.5.0.4 caused a bootloop, but i used it only to install CWM 6.0.4.9 from external_sd, so the bootloop problem was gone. Then flashed CyanogenMod 11 and now works like a charm !
I attached an archive with CWM 5.5.0.4, AriesVE.ops and Odin v4.43, so that anyone having my problem can solve it the way i did. But keep in mind that this version of CWM *may* cause a bootloop, so prior to installing it, you should have a working version of CWM on your external_sd. Use CWM 5.5.0.4 to install the better version of CWM from your external_sd. Also, whatever you do is at your own risk!

cant flash anything using odin

the galaxy tab 8.9 is quite aged so i thought that i could pump some newer juice in it. bad luck, it got bricked. stuck at the samsung logo, bootlooping over n over
it started when i tried to install twrp, my current recovery is cwm. currently, i can only boot into download mode. so, i tried flashing back cwm, twrp and even stock recovery but all of it failed. i also tried flashing another stock rom but it also failed. odin didnt even tried, it stucked at "SetupConnection"
can anyone hand out a helping hand?
when i tried to reboot it back now, it asks me to "select recovery from kies" something like that about an error.
?*
bumayang said:
the galaxy tab 8.9 is quite aged so i thought that i could pump some newer juice in it. bad luck, it got bricked. stuck at the samsung logo, bootlooping over n over
it started when i tried to install twrp, my current recovery is cwm. currently, i can only boot into download mode. so, i tried flashing back cwm, twrp and even stock recovery but all of it failed. i also tried flashing another stock rom but it also failed. odin didnt even tried, it stucked at "SetupConnection"
can anyone hand out a helping hand?
Click to expand...
Click to collapse
I have a similar problem. I am waiting for tablet to die (battery dead) then plug into wall charger and it should bring up download mode.
Do you have the LTE model?
droiduzr2 said:
I have a similar problem. I am waiting for tablet to die (battery dead) then plug into wall charger and it should bring up download mode.
Do you have the LTE model?
Click to expand...
Click to collapse
im afraid i dont
Going to necro this because I've had the same problem as the OP (but not 2nd message).
I had CWM 5, tried to flash TWRP (so I could get Nougat), ended up with no recovery bootable. Can anyone help me get back with a recovery?
Tried to flash TWRP 3 but stuck at "failed". The tab was stuck in like 2% status, and wouldn't respond to Odin commands to flash again, so I had to reboot it.
Then there was no recovery I could boot into (icon would just flash when I tried to enter recovery from bootloader menu).
If I don't try to boot into bootloader menu, it sometimes would show the message "Software update failed", but would still accept Odin flashing.
I tried flashing via odin TWRP 2.6, 2.7, 3.0, CWM 5.5, Stock recovery and all did not work. TWRP <=2.7 and CWM would flash OK but still could not enter it, icon would just flash the icon but not change screen.
It doesn't display "Software update failed" screen anymore, but when I try to boot it normally with power button, it will always go into bootloader mode. If I restart with power + vol -, it would go into bootloader menu for you to choose between recovery and bootloader mode.
What should I do next to get a recovery back?
I haven't tried from Odin flashing a full stock image since I can't find a working download link anymore since hotfiles and devhost are down. Does anyone have a .tar or .tar.md5 for Odin flashing they could link me?
Never mind. I managed to find a stock image flashable by odin, flashed that and recovered stock recovery (and a stock ROM). I used the stock recovery to flash TWRP and then used TWRP to flash a new ROM, and all seems to be well now!
pd12 said:
I used the stock recovery to flash TWRP and then used TWRP to flash a new ROM, and all seems to be well now!
Click to expand...
Click to collapse
It is not possible with Stock recovery to flash the TWRP Recovery.
I think your Stock image has an CWM Recovery ( its a modified Stock Recovery ) and it is possible to flash TWRP.
pd12 said:
I managed to find a stock image flashable by odin, flashed that and recovered stock recovery (and a stock ROM).
Click to expand...
Click to collapse
Hi, that's great news! Would you be able to share where you got the ROM from and what version of Odin you used (and where you got it) please?
I am stuck on the boot screen with my GT-P7300. The stock images I have found so far don't flash through Odin and also fail in the recovery.
Many thanks in advance
dertobes

Can't flash recovery on my S3

Hello, just bought an used i8190. Since last friday i have been trying to flash a custom recovery on this phone via Odin, but after i flash it returns to the default recovery on next boot.
Yes, i have unchecked the "Auto-reboot" option on Odin. I turn off the phone and then manually enter recovery but with no results. I rooted the phone pretty easily and installed both TWRP and CWM apps to flash from android, but they don't work either (twrp crashes always and CWM just gives me an error.
Mi baseband model is XXAll2
kernel is 3.0.31 [email protected] (root name seems weird)
I searched the forum and found similar cases with the baseband, but even so i haven't found a concrete solution.
I even flashed a new pre-rooted rom from this thread: https://forum.xda-developers.com/showthread.php?t=2030282
Mi compilation number has changed to XXAMG1 but the baseband remains the same. I can't flash a recovery whatever i try.
I hope someone can give me an answer, cause i really want to use this phone feautures to it's fullest
Update:
Somehow, i managed to flash CWM via it's app successfully. However, when i tried to flash the TWRP via zip all i got was a blank screen and the phone booted directly to Android. I had to reflash the cwm with the app. However, i tried flashing via odin the Lineage os 14 from novafusion and i got a bootloop, reflashed the old stock firmware and now my device works but the recovery doesn't, and can't even flash this time via the app.
I tried flashing via ODIN stock recovery and other recoverys and i still get the same result. I have downloaded some stock roms, but im afraid to flash them in case i end up in a bootloop and unable to access recovery still
Any clues?
Glass_Arcana said:
Update:
Somehow, i managed to flash CWM via it's app successfully. However, when i tried to flash the TWRP via zip all i got was a blank screen and the phone booted directly to Android. I had to reflash the cwm with the app. However, i tried flashing via odin the Lineage os 14 from novafusion and i got a bootloop, reflashed the old stock firmware and now my device works but the recovery doesn't, and can't even flash this time via the app.
I tried flashing via ODIN stock recovery and other recoverys and i still get the same result. I have downloaded some stock roms, but im afraid to flash them in case i end up in a bootloop and unable to access recovery still
Any clues?
Click to expand...
Click to collapse
Flash the stock rom as it will fix bootloops and bricked devices. Make sure to have the right ROM and flash it with Odin. The os may take longer on first boot and make sure to factory reset it as data may cause bootloops, then try flashing the recovery.
I flashed twrp 3.1.1 through Odin

Categories

Resources