So I just updated my Note 4 to ANK4 through Kies. It completed and booted fine after that. I then booted into recovery and flashed CF Auto Root. This completed and I confirmed Root.
Upon reboot the phone boots into recovery, but the green droid is just flashing and nothing is happening. I cannot even see the phone within Odin.
I did have TWRP installed prior to the ANK4 upgrade.
Anyone have any idea of what I may try?
msherman123 said:
So I just updated my Note 4 to ANK4 through Kies. It completed and booted fine after that. I then booted into recovery and flashed CF Auto Root. This completed and I confirmed Root.
Upon reboot the phone boots into recovery, but the green droid is just flashing and nothing is happening. I cannot even see the phone within Odin.
I did have TWRP installed prior to the ANK4 upgrade.
Anyone have any idea of what I may try?
Click to expand...
Click to collapse
Never mind - i was able to fix this by Power + Volume down to get into download mode and reflash TWRP.
Thanks!
Related
Ok, so I tried following the method described here:
http://forum.xda-developers.com/showthread.php?t=2712039
I was on JB. Installed SS 3.71, downloaded the odexed version of UrDroid and odin files.
Procedure I followed:
Booted into SS
Factory reset
Install urdroid - deodexed
Installation failed, zip wouldn't open
Booted back up, downloaded urdroid again - odexed version this time
pulled battery, booted to safestrap
factory reset
install new zip, worked this time
tried booting to download mode with vol down key, didn't work for some reason. just went to SS splash screen then tried to boot
pulled battery, booted SS again, used the reboot menu to get to download mode
followed steps to set up partitions in ODIN, seemed to work fine
Now when I try to boot it just shows me the SS splash screen, then when I let it boot it just goes to a black screen with a solid blue indicator LED.
Next, I tried to verify the MD5 on the UrDroid zip and it didn't match. I downloaded it again, copied it to my external SD, and it then checked out.
Wiped, installed, ran the odin stuff again. Same problem.
I'm guessing the next step is to restore it back to MJ5 using this method: http://forum.xda-developers.com/showthread.php?t=2559715&page=118
Except several of the files linked there are no longer available....
I'm feeling a little panicked now, this is my only phone lol. Can anyone give me a hand?
If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005
andygev35 said:
If you're on MJ5 and If you can access Safestrap recovery, this should work : http://forum.xda-developers.com/showthread.php?t=2619005
Click to expand...
Click to collapse
I thought that once you update to KK, you can't go back to JB... except I don't know if I ever completed the update. I'm not entirely sure how this process even works.
Do you flash the rom, and then the ODIN portion of it prepares your phone for KK?
Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.
andygev35 said:
Boot into safestrap recovery, click reboot, click reboot to recovery (which will boot you into system recovery). Near the top of the system recovery screen it will show you what version of firmware you have. If it's MJ5, then just do a restore within safestrap recovery to the restore files you get from the link I posted earlier.
Click to expand...
Click to collapse
First of all, thank you for your help.
In recovery, it just says "Android system recovery <3e>". Then goes down to the options you can select.
Before you posted, I tried installing a MJ5 custom rom (FireNote) in the stock slot and now it successfully boots. Which is certainly an improvement. I tried the same process again with UrDroid and had the same result as before - no boot. Now I'm back on FireNote again.
Since FireNote works fine, is it safe to conclude that the Odin process did not properly prepare my boot system for KitKat, and that is why the KK rom isn't working at all?
Have I stumped XDA?? Haha.
I went over the guide again and can't see anything that I've done wrong, but I certainly could have. Are there glitches in Odin3 with Windows 7 that I should be looking out for or anything?
Another thought: I was attempting to do this with SafeStrap 3.71 installed. I thought that 3.72 should be sideloaded after I had switched to KitKat. Was this incorrect? Should I have started by installing 3.72 in my JB rom?
Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.
steveh_131 said:
Well, I just let out a string of bad words.
When I ran Odin it defaulted to my 'return to stock' files even though I ran it from a completely different folder... and I didn't realize it.
I'm guessing using the right files will resolve this problem.
Wow, I'm an idiot.
Click to expand...
Click to collapse
I wouldn't say you're an idiot. You're human!
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
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
monkeny said:
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
Click to expand...
Click to collapse
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
BACARDILIMON said:
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
Click to expand...
Click to collapse
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
monkeny said:
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
Click to expand...
Click to collapse
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
monkeny said:
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
Click to expand...
Click to collapse
Which rom u trying
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
nosympathy said:
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
Click to expand...
Click to collapse
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
monkeny said:
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
Click to expand...
Click to collapse
I have not messed with CM since I had the Note 2, which was until the Note 3 came out. Was a different carrier too. Generally the rule was flash CM then boot then reboot and flash GAPPS. I haven't looked but I would assume it is still the same.
Glad it worked
Trying to flash my Note 4 (Canadian version - N910W8) with either the AllianceROM 1.1 or TEKXodus 3.6 ROMs. Can't seem to get it done and I'm so incredibly frustrated.
Chronologically-speaking, here's what I did.
1. Rooted with appropriate Auto-Root file with Odin 3.09
2. Used Flashify to flash the latest TWRP files (2.8.7)
Most of the time, I just reboot onto "dm-verity verification failed." I've tried everything I can think of.
Sometimes, I get lucky and boot into TWRP. When I flash using TEKXodus 3.6 ROM, it proceeds to do everything but then, the screen goes black and I can never boot. I've read it can take 15 min for it to boot. I've waited 30 min with nothing. Only thing I could do is boot back into Download mode to reflash it with a stock ROM through Odin.
I don't understand why this doesn't work and I've flashed a bunch of phones before without any issue! Help? Anybody? UGH!
need help
Strat-Mangler said:
Trying to flash my Note 4 (Canadian version - N910W8) with either the AllianceROM 1.1 or TEKXodus 3.6 ROMs. Can't seem to get it done and I'm so incredibly frustrated.
Chronologically-speaking, here's what I did.
1. Rooted with appropriate Auto-Root file with Odin 3.09
2. Used Flashify to flash the latest TWRP files (2.8.7)
Most of the time, I just reboot onto "dm-verity verification failed." I've tried everything I can think of.
Sometimes, I get lucky and boot into TWRP. When I flash using TEKXodus 3.6 ROM, it proceeds to do everything but then, the screen goes black and I can never boot. I've read it can take 15 min for it to boot. I've waited 30 min with nothing. Only thing I could do is boot back into Download mode to reflash it with a stock ROM through Odin.
I don't understand why this doesn't work and I've flashed a bunch of phones before without any issue! Help? Anybody? UGH!
Click to expand...
Click to collapse
i m also having the same problem
did u find any solution
Strat-Mangler said:
Trying to flash my Note 4 (Canadian version - N910W8) with either the AllianceROM 1.1 or TEKXodus 3.6 ROMs. Can't seem to get it done and I'm so incredibly frustrated.
Chronologically-speaking, here's what I did.
1. Rooted with appropriate Auto-Root file with Odin 3.09
2. Used Flashify to flash the latest TWRP files (2.8.7)
Most of the time, I just reboot onto "dm-verity verification failed." I've tried everything I can think of.
Sometimes, I get lucky and boot into TWRP. When I flash using TEKXodus 3.6 ROM, it proceeds to do everything but then, the screen goes black and I can never boot. I've read it can take 15 min for it to boot. I've waited 30 min with nothing. Only thing I could do is boot back into Download mode to reflash it with a stock ROM through Odin.
I don't understand why this doesn't work and I've flashed a bunch of phones before without any issue! Help? Anybody? UGH!
Click to expand...
Click to collapse
So i see your posting about your flashing but what about your wipes..
Nandroid backup ext sd.
Then reboot twrp.
Wipe sys/dal/cache/data..
Include the internal if after what i posted above doesnt work.
Check the md5 sum of your downloaded rom..
Nav to your ext sd were you should have the rom stored..
And flash the rom..
Curious as to why you used flashify to get twrp.. it comes in a tar and flashes easy in odin..
You might wanna try that as well twrp may not be installed 100% corectlly.
Ok..[emoji41] [emoji106]
Last but not least you need to use bishock kern in your flash after the Rom flash, in the same session before reboot.
Or it will never work.
You booting problem more than likely kernel related..
Flashvetrin
For the longest time, I was on CM12 with TWRP on my Note 4. I had progressively updated the thing to every nightly update over the year and a half, and decided I wanted to go back to a stock non-rooted state so I can use Android Pay.
Everything flashed ok, the phone is working stock, but recovery is not. If I go into Recovery mode, it says "Installing Update..........................No command!". But then proceeds to "appear" to work. I'm worried this weird error into recovery may prevent recovery mode from installing future samsung updates. Is it normal for recovery to say no command on a stock reflash? I flashed EPG2 via ODIN.