Sprint Note 4, when flashing the official Rom i clicked on Nand Erase All, flash went fine, but the phone stays forever on the Sprint Spark screen, any steps to fix this issue? I can get into recovery and download mode, tried to wipe cache and dalvik in TWRP but i get errors, can not mount.
thanks in advance for the help.
anybody please?
MHeat said:
anybody please?
Click to expand...
Click to collapse
You flashed TWRP after it failed to boot? If so, I wish you didn't do either the nand erase or flash TWRP.
If TWRP fails to mount to wipe, you need factory recovery or Philz CWM to wipe cache and factory reset.
To be clear, you need to wipe cache, dalvik-cache and data and power down. Boot into download mode and flash stock tar with Odin defaults. I'm not sure if the Note 4 just requires a wipe and Odin stock tar or the PIT with repartition (PIT for Sprint Note 4 seems to be MIA). Hopefully just the wipe works.
Here's Philz CWM recovery for Note 4:
http://downloadandroidrom.com/file/GalaxyNote4/CWM/philz_touch_6.59.0-trlte.tar
If that doesn't work, you need stock recovery. Last time I flashed stock recovery, it required a tar.md5 to flash. Had to search for a Windows tool to modify it, adding the md5 hash to tar so Odin would see and use it.
And one more thing. If you succeed in wiping, try to boot before Odin of stock tar. Seems Odin is risky these days. I've read recently that there's yet another "fix" Samsung has identified for Odin flashing for upcoming security patch. Best to limit Odin flashes to as needed only.
Sent from my SM-N920P Note 4 via Tapatalk
thanks for you explanation, i will try it. Let me tell you, remember i already flashed the stock tar multiple times, i might be mistaken but i thought the stock tar has the oem recovery included, the problem is i can not get into stock recovery, it just bootloops and the phone restarts again, i will try flashing the stock tar again and then Philz touch recovery and see if i can wipe. Will let you know how it goes in a few minutes.
thanks again.
just to let you know, the phone booted, had to flash the clean stock image, then extract the recovery image from the tar file, after that i used a utility to convert recovery.img to a tar file in order to flash it in odin, after a while it booted, right now updating over the air to cok1, lets hope it works now.
appreciate the time you took to help me out.
I'm not clear on what you're saying. I gather that flashing the tar didn't allow you to get to stock recovery and it still wouldn't boot?
Then you tried Philz CWM recovery to wipe and it booted? If so, I'd think you were in the clear at this point, not needing to restore stock recovery but flash the tar?
When you say you had to extract stock recovery, was it still not allowing you to get to stock recovery when tar was flashed or did that fail? If so, which tar? I'd think you could have moved on to OK1 tar?
Or were you thinking that I meant you had to use both recoveries to wipe to restore function?
It's good you're making progress on your own, I'm just not following the results and reasoning fully. I'd like to know so I'm asking. TIA.
Edit: Or did you have to flash stock recovery to wipe? Philz CWM recovery didn't flash or wouldn't mount or what? Read your reply again and thought this may be the direction you went.
Sent from my SM-N920P Note 4 via Tapatalk
sorry for the confusion, i flashed the stock tar file COJ6, still the phone would not boot and could not get into stock recovery, do not know why
then i flashed just Philz recovery and was able to wipe cache,dalvik and data
For some reason it did not boot, then after i flashed just the stock recovery ( in order to do that, i extracted the recovery from the COJ6 tar, then used a program to convert the recovery.img to .tar in order to be able to flash it in Odin, after that the phone booted and updated over the air to COK1) Just to make sure i tried to go into stock recovery ( VOL UP+HOME+POWER) and was successful, got access to stock recovery. Before i was not able to go into stock recovery for some reason.
So you didn't try to flash stock tar after the Philz recovery wipe? I was suggesting try to boot; if it didn't boot, try the stock tar.
Am I wrong to say that maybe you didn't have to flash the stock recovery? Philz recovery maybe gets the credit as the easier fix in this case. Would you agree with that or is that unknown?
Thanks for clarifying. Your response may clarify the suggested fix. TIA.
Sent from my SM-N920P Note 4 via Tapatalk
Well, after i wiped with Philz it still did not boot, then after the stock recovery it booted, it took a while, i thought it did not work but eventually it did boot, the phone definitely had something wrong since i could not even access the stock recovery before, now i can, it says installing system update, then its says something like no command, and then it enters recovery, this was impossible to achieve before.
Did the OK1 OTA complete and boot yet?
Sent from my SM-N920P Note 4 via Tapatalk
It did complete and booted just fine, everything seems to be in order, crossing fingers LOL
Related
I went back to odin to get a fresh of my gs3. I did the 4.1.1 update and now i have an issue.
I can't seem to install any recovery on my samsung galaxy s3 in order to root it.
I have tried just about all the downloadable clockworks out there and even tried twrp...its no go. I do not know why this is happening because I never had this problem before when rerooting my gs3.
Any one faced this before? suggestion?
You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.
Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).
bikrame said:
You need to flash recovery via odin.
If you want just flash root66 lastest firmware which is in rooted version too.
Click to expand...
Click to collapse
I do, personally I only flash via odin....root66...is that a rom? how do I flash that without rooting?
Aerowinder said:
Stock recovery is overwriting your custom recovery. Need to access recovery mode after you flash, but before the device can boot (so that the custom recovery can disable to automatic flashing script).
Click to expand...
Click to collapse
I am not quite sure what you are saying here about needing to access recovery mode after I flash...I flash the clockwork recovery mode and when i go to access it, i only see the stock.
I i reflashed odin again and decided to root using 4.0.4 ics...now it worked..I guess we can't flash over 4.1.1 anymore?
anyway, thank you both ^.^
The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?
Aerowinder said:
The problem is with the newer roms, when your phone boots, your custom recovery is overwritten with stock recovery. This operation is done with a script that comes with the newer stock firmwares - it's built into the startup procedure. So when you flash a custom recovery with Odin, you need to drop to recovery mode before the phone ever gets a chance to boot into the OS, so that the custom recovery can disable this script. If the phone boots, it will wipe out your recovery. Do you understand now?
Click to expand...
Click to collapse
Oh now that make a lot of sense. So I was not suppose to reboot before going into recovery with 4.1.1...will keep that in mind next time!
Even though you're rooted, flash the 4.1 root66 in Odin. You don't want to go from ICS to JB via recovery, it doesn't flash all partitions. After you flash root66 in Odin, you will already be rooted. Then you can just flash a custom recovery.
Sent from my SGH-T999 using Tapatalk 2
If I remember correctly you can still root normally on the later builds, you just have to pop out you battery after you flash, don't let it auto-reboot, then you can put the battery back in and get to clockwork recovery.
I just accepted the cyanogen 10 snapshot update today for my d2spr; after the update finished it left me stuck in a bootloop, and Im unable to access recovery! I want to go back to the rom I was at before the update, which was the cm-10.1.3. Please help!!
Download mode and flash a custom recovery tar
CNexus said:
Download mode and flash a custom recovery tar
Click to expand...
Click to collapse
Thanks for the reply, I just downloaded a stock rom from samsung, and flashed via odin. It was successful, however even with the stock rom, I am still stuck in a boot load, and it still wont let me into recovery mode....
Solved!!
So I finally solved the issue. After I had flashed the stock rom via odin, I needed to find away to wipe cache's and do a factory reset. I finally accomplished this by downloading the .pit file, and re-flashing it together with the stock rom all through odin. After doing so, I was finally able to get into recovery, wipe, and do a factory reset. For anyone else having this issue, here is a link where I found the .pit file, and a thread with some basic instructions:
:laugh:
PIT Files: http://d2tehp.chickenkiller.com:22222/pits/
Basic Instructions: http://teamuscellular.com/Forum/topic/3882-pit-files-for-all-us-variants-of-sgsiii/
Help. I think I bricked my phone. I was running S3Rx 3.0 with JB4.3 on my T999 GS3. I attempted to update the rom to its latest version 3-20-14. I made a nandroid backup. I wiped cache and dalvik and then tried to install the zip file in TWRP, but it said install failed. I tried again with same failed results. I then did a factory reset, wipe cache, dalvik, data and system. I tried to flash the zip file and it failed again. So giving up on the failed update, I then restored my nandroid backup. After the restore was complete, I rebooted the phone and it got stuck at bootup with the Samsung logo and the blue LED light. I let it sit for over 15 minutes and it was still stuck there. I powered off the phone and went back into TWRP recovery and repeated the restore and reboot again, and it was stuck at that same part for over 15 minutes. Should it take that long? I've done backups and restores in the past and I don't recall it having take that long to bootup.
Does anyone have any suggestions? Please let me know if you need more explanation. Thanks in advance.
Try using odin to update the recovery system and flashing a rom.
Sent from my SGH-T999 using Tapatalk
It's been a long while since I used odin. I want to get the steps right before I risk further damaging my phone. Should I download odin and latest TWRP tar file to my pc. Put my phone into download mode and go thru the odin process...run as admin, placing tar file in pda... Then do I reboot into recovery mode? From there I'm not sure what to do. How do I flash a rom to my phone? Do or can I download a zip file via odin? One other option I thought of is to odin root66. So am I actually downloading 2 files via odin? Sorry for my confusion.
Ok, so I odined root66. My phone initially booted up to stock, but I got a pop up "unfortunately system ui has stopped". I went to recovery mode to do a factory reset. It took me to android system recovery. Apparently i lost my TWRP recovery. I did a factory reset and rebooted. Hallelujah!! my phone booted up into stock successfully. Whew...
Cool.
Sorry I couldnt respond earlier, I just woke up.
I always keep copies of odin flashable packages for the latest cwm and twrp recoveries just in case some craziness happens.
Ive had a similar issue when dualbooting. Recovery seemed to work 100% but one bad flash sent me into a bootloop I couldnt get out of. Booting to recovery just tried booting my corrupt 2nd rom and I had to odin cwm on to stop the boot script from locking me out of recovery.
Sent from my SGH-T999 using Tapatalk
All part of the hazards of tinkering with the phone. It goes with the territory. But as long as I can get into download or recovery mode I believe there's always a fighting chance.
Separately I reinstalled TWRP via odin. Next will be to reflash the custom rom.
Hi this is a long post so I will highly appreciate it if anyone helps me even after reading this.
I was on xperia z-ized v3.4 (based on android 4.3) with mj5 as the bootloader. I was tired of that rom and wanted to try dn3 rom and downloaded the zip as well but the OP of the rom thread said that twrp recovery is recommended over cwm. So I went to thread given in the page which showed me how to flash twrp. It was just download the zip and flash it in recovery, which is exactly what I did. Now ever since then I am not able to turn on my phone, nor does it go to recovery, it just goes into download mode which made me change my decision. Now I am thinking to downgrade back to 4.1.2 and I will try dn3 rom later on. I downloaded the firmware from sammobile but just wanted to ask that given my previous firmwares and flashes, is it safe to flash or will I risk bricking my phone.
Thanks for reading this and please help me out if you can
RazaVakil7995 said:
Hi this is a long post so I will highly appreciate it if anyone helps me even after reading this.
I was on xperia z-ized v3.4 (based on android 4.3) with mj5 as the bootloader. I was tired of that rom and wanted to try dn3 rom and downloaded the zip as well but the OP of the rom thread said that twrp recovery is recommended over cwm. So I went to thread given in the page which showed me how to flash twrp. It was just download the zip and flash it in recovery, which is exactly what I did. Now ever since then I am not able to turn on my phone, nor does it go to recovery, it just goes into download mode which made me change my decision. Now I am thinking to downgrade back to 4.1.2 and I will try dn3 rom later on. I downloaded the firmware from sammobile but just wanted to ask that given my previous firmwares and flashes, is it safe to flash or will I risk bricking my phone.
Thanks for reading this and please help me out if you can
Click to expand...
Click to collapse
Well if you still want to try DN3 ROM you can flash philz recovery tar.md5 via odin and then once you boot into recovery you can get twrp zip file that you downloaded previously and flash twrp over philz.That's what i do when i switch recoveries.I never used CWM except when i was on 4.1.2 but once i rooted my phone the same day i switched to philz.If you don't want to try dn3 at the moment yes you can go back 4.1.2 since you are on mj5 bootloader which makes downgrading back to 4.1.2 possible.I'm giving you links below for philz tar.md5 and instructions on how to flash it via odin incase you change your mind.
philz tar.md5
Put your phone into download mode,open odin on pc,uncheck auto reboot in odin,dont touch anything else,connect phone to pc,wait for port ID to lit up and be blue.Select the AP/PDA tab and navigate to flash this downloaded philz tar file.Click start and you are done.Exit odin on pc.Pull battery out your phone.Wait a minute then put it back in and manually enter recovery mode your newly flashed philz recovery will load.Now go and install twrp recovery zip file and select "reboot recovery" in philz advanced options.Your twrp recovery will load.Do all the wipes in twrp by going under advanced wipe (dont wipe external sd and otg) this will fully wipe your internal phone memory clean then go back to main menu and flash DN3.Enjoy.
singhpratik87 said:
Well if you still want to try DN3 ROM you can flash philz recovery tar.md5 via odin and then once you boot into recovery you can get twrp zip file that you downloaded previously and flash twrp over philz.That's what i do when i switch recoveries.I never used CWM except when i was on 4.1.2 but once i rooted my phone the same day i switched to philz.If you don't want to try dn3 at the moment yes you can go back 4.1.2 since you are on mj5 bootloader which makes downgrading back to 4.1.2 possible.I'm giving you links below for philz tar.md5 and instructions on how to flash it via odin incase you change your mind.
philz tar.md5
Put your phone into download mode,open odin on pc,uncheck auto reboot in odin,dont touch anything else,connect phone to pc,wait for port ID to lit up and be blue.Select the AP/PDA tab and navigate to flash this downloaded philz tar file.Click start and you are done.Exit odin on pc.Pull battery out your phone.Wait a minute then put it back in and manually enter recovery mode your newly flashed philz recovery will load.Now go and install twrp recovery zip file and select "reboot recovery" in philz advanced options.Your twrp recovery will load.Do all the wipes in twrp by going under advanced wipe (dont wipe external sd and otg) this will fully wipe your internal phone memory clean then go back to main menu and flash DN3.Enjoy.
Click to expand...
Click to collapse
Thanks a lot for the help, unfortunately I didn't like dn3 that much so tried to go back to stock but odin shows fail, so stuck with dn3 for a while until I find a solution
RazaVakil7995 said:
Thanks a lot for the help, unfortunately I didn't like dn3 that much so tried to go back to stock but odin shows fail, so stuck with dn3 for a while until I find a solution
Click to expand...
Click to collapse
Well try other 4.4.2 custom TW rom,dn3 isn't the only ROM available on xda for our note II.Look around and I am sure you'll find something that suits you.
singhpratik87 said:
Well try other 4.4.2 custom TW rom,dn3 isn't the only ROM available on xda for our note II.Look around and I am sure you'll find something that suits you.
Click to expand...
Click to collapse
Actually to be honest I want to go back to stock but I odin shows fail, so is there any workaround for that.
PS: even dn3 doesn't boot up now after flashing. Stuck on the note II logo. Tried wiping cache, dalvik cache and factory reset but to no avail
RazaVakil7995 said:
Actually to be honest I want to go back to stock but I odin shows fail, so is there any workaround for that.
PS: even dn3 doesn't boot up now after flashing. Stuck on the note II logo. Tried wiping cache, dalvik cache and factory reset but to no avail
Click to expand...
Click to collapse
Well which recovery are you using now?TWRP?Do you have a back up of any ROM? I suggest go under advanced wipe and wipe everything except external sd card and otg.This will fully wipe your phone.Other suggestion is flashing stock 4.4.2 ROM and then trying custom ROM.
singhpratik87 said:
Well which recovery are you using now?TWRP?Do you have a back up of any ROM? I suggest go under advanced wipe and wipe everything except external sd card and otg.This will fully wipe your phone.Other suggestion is flashing stock 4.4.2 ROM and then trying custom ROM.
Click to expand...
Click to collapse
Tried whatever you said just now, still not booting up. I am on philz recovery and I did not take any backup. I only have stock 4.1.2 rom which is not getting flashed via odin and I cannot download stock 4.4.2 because my internet connection is slow..
what should I do?
I've had AOKP & TWRP installed for nearly 3 years. The phone started rebooting occasionally when I would go to manage apps and kill an app. It finally got hosed really good on the last reboot and it got stuck in a TWRP boot loop. I was able to use odin to reflash TWRP and after the initial flash I could get into TWRP recovery. Unfortunately I don't have any of the necessary image files on the sdcard. I then tried to flash a converted AOKP zip (now a tar converted with toolkit). I am not able to get either the toolkit or adb detect the device although I am able to flash with odin. I flashed the AOKP tar image with odin but now when it boot it stays on the Galaxy Note 2 screen and goes no further.
Now I can only get in download mode and since odin seems to be the only thing that is working for me my question is can I use it to flash AOKP and GAPPS (both of which I have on computer)? If so, what format does the AOKP file need to be? img, tar or what? Also can I convert the gapps zip file to a tar and use odin to flash it?
Much thanks in advance. I plan to purchase a new device soon but would like to get this working again as a backup.
Regards, ~metafizik
Use a stock/rooted .tar image to restore the device partition structure.
It contains the PIT for remapping...
Once a stock rooted rom is flashed and running...flash TWRP 2.8.6.0 via Odin...
Then create a nandroid backup to SD CARD..
You can then flash AOKP and GAPPS as .zip files...in TWRP
It's a bit more work....but you'll have a clean backup and a way back if trouble hits...along with fresh partitions...g
I recommend flashing back to stock, get the phone set up using stock, install TWRP, take a nandroid backup, and then flash a custom ROM.