[Q] N7105 in boot loop - Galaxy Note II Q&A, Help & Troubleshooting

I have a Samsung galaxy note 2 LTE n7105 in a boot loop, i was trying to flash ''http://forum.xda-developers.com/showthread.php?t=2761937'' but under the installation a made the mistake of wiping everything on the device including the rom that was saved on the internal phone memory, i also had a 4.4 bootloader and Philz CWM touch recovery..
so when i put the device in download mode it does it fine and odin finds it, but it wont go in recovery, it just shows the bottom touch keys of the recovery then goes into a boot loop again, i would like to flash it to stock again without unrooting it if possible but i need to know whats wrong here?

athoxworld said:
i would like to flash it to stock again without unrooting it if possible but i need to know whats wrong here?
Click to expand...
Click to collapse
Recovery must work fine since you didn't messed it up. Try again and try to flash rom from sd card. If not, flashing stock rom using odin is the next best option (will remove root though). Goodluck.

Fixed
erljayp said:
Recovery must work fine since you didn't messed it up. Try again and try to flash rom from sd card. If not, flashing stock rom using odin is the next best option (will remove root though). Goodluck.
Click to expand...
Click to collapse
Fixed the problem, just flashed stock 4.4.2 rom with odin and it was in fully working order, then i flashed CWM Touch with odin then installed the the rom i wanted in the first place, jumped over deleting everything, and now it works great ^^

Related

[Q] Tried to change flash a new rom but no backups are found

I didn't like the rom I was using, tried to flash a new one and my phone bricked, Note 2 splash then three vibrates ad infinitum. Can get into TWRP recovery but my backups are not showing up. How can I get a new rom onto my SD if my phone isn't booting thus not being seen by the PC?
davbob said:
I didn't like the rom I was using, tried to flash a new one and my phone bricked, Note 2 splash then three vibrates ad infinitum. Can get into TWRP recovery but my backups are not showing up. How can I get a new rom onto my SD if my phone isn't booting thus not being seen by the PC?
Click to expand...
Click to collapse
well i will suggest to move to philz though its bias but it works wonder flash philz then dirty wipe including system flash your rom file then again wipe cache and dalvik and boot up. if still not then get into download mode and flash stock using odin. go to original dev section and read dr.ketan guide its stickied so it will help you to how to proceed with odin and make the phone detect on pc
shhbz said:
well i will suggest to move to philz though its bias but it works wonder flash philz then dirty wipe including system flash your rom file then again wipe cache and dalvik and boot up. if still not then get into download mode and flash stock using odin. go to original dev section and read dr.ketan guide its stickied so it will help you to how to proceed with odin and make the phone detect on pc
Click to expand...
Click to collapse
It never occurred to me to flash stock via odin. Doing it now, thanks.
davbob said:
It never occurred to me to flash stock via odin. Doing it now, thanks.
Click to expand...
Click to collapse
You could have donwloaded a Rom and then placed it on your SD Card and flashed using a card reader or any other device.

Problems downgrading from 4.3

Hello! I have been flashing roms/kernels for awhile now. I have tried probably 12-15 different roms and beanstalk has been my favorite for awhile now.
Anyway, i decided to revert back to stock so i could update and try stock 4.3. First thing i did was flash stock 4.1.1(i think thats what version it was) firmware with odin. Everything went fine and phone booted up and worked perfectly. So i proceeded to update via software update in the settings menu. My phone updated flawlessly and before i knew it i was on stock unrooted 4.3. Needless to say I did not like the changes, so i decided to go back to the older version.
So, i flashed the stock 4.1.1 firmware with odin again and it was a pass. I then tried to turn my phone back on and it would hang at the samsung logo. So i figured i would restore my old beanstalk backup. I tried to restore it and there was an error. So i rebooted my phone and it hanged on the samsung logo again, only this time there is that little blue cyanogenmod guy there like it used to be when i was running beanstalk. I tried flashing different stock firmwares and now they all fail with odin. I rebooted into recovery and did a data wipe many times and i still cannot boot or flash anything with odin.
I can still get into cwm recovery and download mode. Im thinking that the older stock rom i flashed caused problems because i was on 4.3. Something wrong with the bootloader maybe?
Any help or advice to get this fixed would be great. I still feel there is hope because i can reboot into recovery and download mode.
well nvm, my phone is really screwed now. I read another post and it said to flash a boot image file. I flashed the file and tried to reboot and now the phone wont come on and i cant get into recovery or download mode. =-( now i officially have a paper weight
be there... done that
scorey03 said:
Hello! I have been flashing roms/kernels for awhile now. I have tried probably 12-15 different roms and beanstalk has been my favorite for awhile now.
Anyway, i decided to revert back to stock so i could update and try stock 4.3. First thing i did was flash stock 4.1.1(i think thats what version it was) firmware with odin. Everything went fine and phone booted up and worked perfectly. So i proceeded to update via software update in the settings menu. My phone updated flawlessly and before i knew it i was on stock unrooted 4.3. Needless to say I did not like the changes, so i decided to go back to the older version.
So, i flashed the stock 4.1.1 firmware with odin again and it was a pass. I then tried to turn my phone back on and it would hang at the samsung logo. So i figured i would restore my old beanstalk backup. I tried to restore it and there was an error. So i rebooted my phone and it hanged on the samsung logo again, only this time there is that little blue cyanogenmod guSD there like it used to be when i was running beanstalk. I tried flashing different stock firmwares and now they all fail with odin. I rebooted into recovery and did a data wipe many times and i still cannot boot or flash anything with odin.
I can still get into cwm recovery and download mode. Im thinking that the older stock rom i flashed caused problems because i was on 4.3. Something wrong with the bootloader maybe?
Any help or advice to get this fixed would be great. I still feel there is hope because i can reboot into recovery and download mode.
Click to expand...
Click to collapse
I would first download a fresh version of a rom and the corresponding version of GAPPs and on your computer. Transfer you files onto you misco SD card via the SD card slot on the computer. Boot your phone into recovery and flash them from the /sdcard1 option. Should flash successfully. Then reboot. I always keep spare ROM versions on my removable card for such emergencies. Also, keep a current ROMbackup there as well. Good luck.
Walknmemfs said:
I would first download a fresh version of a rom and the corresponding version of GAPPs and on your computer. Transfer you files onto you misco SD card via the SD card slot on the computer. Boot your phone into recovery and flash them from the /sdcard1 option. Should flash successfully. Then reboot. I always keep spare ROM versions on my removable card for such emergencies. Also, keep a current ROMbackup there as well. Good luck.
Click to expand...
Click to collapse
i tried doing this http://forum.xda-developers.com/showthread.php?t=2549068
but thats not working either. cant get the phone to do anything. wont come on in download mode, recovery...wont come on at all.
debrick
scorey03 said:
i tried doing this http://forum.xda-developers.com/showthread.php?t=2549068
but thats not working either. cant get the phone to do anything. wont come on in download mode, recovery...wont come on at all.
Click to expand...
Click to collapse
hey try another debrick image if you want i can email the one the worked for me,after going in download mode flash cyanogenmod 11 forget about downgrade or stock 4.3 you are stuck just like me your phone wont reboot without the sd card so you gona have to flash modem and bootloader manually here is wher to get it bootloader = http://www.androidfilehost.com/?fid=23212708291681451 modem= http://www.androidfilehost.com/?fid=23212708291681456 put both zip files in the internal storage rebot to recovery remove debrick sd card then flash both zip files wipe cache and dalvin and try to reboot it worked for me .
xjunior said:
hey try another debrick image if you want i can email the one the worked for me,after going in download mode flash cyanogenmod 11 forget about downgrade or stock 4.3 you are stuck just like me your phone wont reboot without the sd card so you gona have to flash modem and bootloader manually here is wher to get it bootloader = http://www.androidfilehost.com/?fid=23212708291681451 modem= http://www.androidfilehost.com/?fid=23212708291681456 put both zip files in the internal storage rebot to recovery remove debrick sd card then flash both zip files wipe cache and dalvin and try to reboot it worked for me .
Click to expand...
Click to collapse
i've tried 3 different debrick images and still cant get the phone to go into download mode. and yes i would appreciate it if you could send me the one that worked for you. thanks man
image
scorey03 said:
i've tried 3 different debrick images and still cant get the phone to go into download mode. and yes i would appreciate it if you could send me the one that worked for you. thanks man
Click to expand...
Click to collapse
download the image here and unzip it then burn with win32diskimager , drive.google.com/file/d/0B4b7I4izs-CwdWFUdFQ2YTNZSU0/edit?usp=sharing remove the battery put it back hold home power and volume down at the same time .
---------- Post added at 07:53 PM ---------- Previous post was at 07:32 PM ----------
scorey03 said:
i've tried 3 different debrick images and still cant get the phone to go into download mode. and yes i would appreciate it if you could send me the one that worked for you. thanks man
Click to expand...
Click to collapse
assuming you have the [email protected] galaxy s3
download the image here and unzip it then burn with win32diskimager , drive.google.com/file/d/0B4b7I4izs-CwdWFUdFQ2YTNZSU0/edit?usp=sharing remove the battery put it back hold home power and volume down at the same time .it wont work for other models [email protected] only but the process is the same only need to find the right file for your phone.
that one didnt work either
scorey03 said:
that one didnt work either
Click to expand...
Click to collapse
It's kind of been a known issue since the day the OTA came out that downgrading the bootloader from the one that comes with 4.3 will hard brick your device. No known fix.

[Q] TWRP 2.6.3.1 Asks for password

I woke up this morning to my phone perpetually rebooting.
I was running a nightly of CM 11.
Now when I try to go into Recovery I get a screen that asks for a password. I have no idea what that password is as I did not set one. I tried wiping data to no avail. I tried flashing a new recovery via Odin this did not work (Odin said successful but the screen on the phone never showed the transfer of the file). No matter what wipe method I use in recovery it just says fail, doesn't work at all and hangs or will say it can't mount. I have searched and searched and tried and tried and I'm stuck. I even tried ADB that didn't work either. Please help!
Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
audit13 said:
Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Click to expand...
Click to collapse
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.
therecker said:
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.
Click to expand...
Click to collapse
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This did not work. When I use ODIN all that is happening is that ODIN says it has succeeded but the little progress bar that usually shows up on the phone when you are in download mode never comes up. I did try this method though and it didn't work.
I restarted the phone in ODIN mode then opened ODIN then connected the USB cable then unchecked the two boxes you mentioned then flashed a new non TWRP recovery then waited for ODIN to say successful then the phone never showed the progress bar so I waited 2 mins until I pulled the battery then I restarted phone directly to recovery and still have the password prompt. Even after hitting cancel I cannot interact with recovery because every option I choose just says fail. I cannot even mount external sd card.
What phone do you have? What was the most recent stock ROM on your phone? Maybe you can flash a stock ROM.
There is a copy of the stock Samsung 3e recovery (which we can't use to flash zips with) I'm curious if maybe it can overwrite what you have going on? On the password screen I wasn't hitting cancel I was simply hitting the back arrow key. I will see if I have a copy of the stock recovery, just maybe you can flash it then flash another recovery after that so you can fix your phone.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have Samsung Galaxy S 3 At&T (d2att) SGH-I747 whichever one of those you want. The most recent stock rom on the phone was when I bought it brand new a few months after it came out. I tried installing a stock rom. I tried this using ODIN and it failed. The issue here is that TWRP somehow encrypted the entire file system so NOTHING at all in recovery works. When I use ODIN mode it never shows on my phone that it is accepting a transfer from the computer. When I tried the stock rom via ODIN method it actually failed in ODIN instead of telling me it succeeded and then just not work. It failed at the point when it says Firmware Update Start...aboot.mbn...NAND Write Start!...Complete(Write) operation failed. I am up for any suggestions but I need them to be detailed instructions because I have tried so many things I need to know what exact steps to follow.
I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.
audit13 said:
I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.
Click to expand...
Click to collapse
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?
therecker said:
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?
Click to expand...
Click to collapse
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?
audit13 said:
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?
Click to expand...
Click to collapse
It was a CM11 Nightly ROM from the very beginning of February. And before that it was a CM10.2 Stable ROM.
Which stock ROM was on your phone before you loaded a custom ROM?
audit13 said:
Which stock ROM was on your phone before you loaded a custom ROM?
Click to expand...
Click to collapse
I have no idea. It was when I first got the phone in November of 2012.
Sounds like your phone may be running a 4.3 bootloader which means your bootloader is locked and cannot be downgraded. This may explain why you are getting errors when trying to flash Odin. There is no stock AT&T 4.3 ROM that can be flashed via Odin.

[Q] Bricked my I747 - Please Help?

Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?
loc626 said:
Hello,
I'm sure there are many threads on about what I'm about to asked but I am a noob and I don't know what to do!!
I tried to flash cm11 to my I747 last night but it failed. So I tried to flash my recovery and it failed at first but second time around it was successful. Only thing is that when it booted, it got stuck on AT&T splash. I left it for about 15-20 minutes but nothing happened. Wasn't sure if my screen was going to burn the image so I turned it off and removed the battery. I have been doing research on how to recover but I want to make sure I do everything correct so I can at least go back to stock.
If there is anyone out there that can please give me some help I would greatly appreciate it!
Thanks!!
Is this fixable?
Click to expand...
Click to collapse
\
Yeah. Should be fixable. First, can you try booting to recovery and doing a wipe/reset? I presume you have custom recovery? If this doesn't work, then you can try flashing a complete compatible stock restore image via recovery to get the phone working or flash a custom ROM? What Android version were you on prior to the attempt to flash CM? This would let us know what stock version to revert to.
I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.
loc626 said:
I was running 4.3 before trying to flash the custom rom. I tried flash the stock rom last night using Odin, but it the flash failed on me twice. I also noticed that the micro sd I had in my cell is now completely dead. When I plug it into my pc it does not show up. I think it still shows up in recovery but it doesnt seem to be working. Im worried about sticking another card in and for some unknown reason it going dead too.
I only found a flash for 4.1.1 as far as stock rom goes.
Click to expand...
Click to collapse
If you were already on 4.3, please do not try to flash 4.1.1 now otherwise you could risk bricking your phone. If you tried doing the hard wipe/reset via (custom) recovery and this did not work, you can try flashing a complete stock restore image via recovery. See the instructions in the following thread ....
http://forum.xda-developers.com/showthread.php?t=2658486
Unfortunately, you would need to load the stock restore zip to a (micro) SD card. Unless you are able to save files to your phone, there is no other way. Once you have the restore zip ready, boot your phone to recovery mode and flash. You can revert to a custom ROM once your phone is back to working normally.
I had this problem TeamWin Recovery. I put Philz recover on there and it worked fine. You will probably have to ADB philz recovery to your phone, if you chose to try Philz. This is what worked when I rooted my girlfriend's phone.
An easy way to install Philz Touch recovery would be to download and install the latest tar version for the d2lte and flash it via Odin.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte
Thanks to everyone for your help and solutions.
My co-worker, who flashed my root and recovery, was able to get it back to 4.3 stock. Unfortunately, the backup that he made before rooting did not work in recovery [twrp]. So I lost all my pics from the last two months since getting my phone.
As sad as I was that I couldn't recover the pics, I am happy to have my phone back to normal+root.
I'm not sure, but maybe it bricked from trying to flash cm11 thru twrp?! Can't really say, but the recovery did not go thru either.... It went thru "successfully" but after I would reboot then it would stay on ATT splash.
Oh well... all is good now. I will steer away from custom roms for now and wait until the 4.4 update comes out for my i747. Or if i get another phone later on, I can use the s3 as a lab rat.
Again, thanks to everyone!

[Q] Wiped OS & TWRP installs Failed

So I had 4.4 stock TouchWiz, then installed TWRP recovery and CM11. Then I wanted back to stock again but TWRP doesn't seem to want to flash anything. It just says Failed. Tried wiping everything, ended up wiping the OS... just trying to get stock back going.
You have the i747 or i747m?
Twrp cannot flash a stock ROM unless that ROM was compiled to be flashed in twrp.
If you have the 4.3 or 4.4.2 bootloader, do not attempt to downgrade the bootloader.
What bootloader is on your phone?
audit13 said:
You have the i747 or i747m?
Twrp cannot flash a stock ROM unless that ROM was compiled to be flashed in twrp.
If you have the 4.3 or 4.4.2 bootloader, do not attempt to downgrade the bootloader.
What bootloader is on your phone?
Click to expand...
Click to collapse
Sorry, i747 AT&T version.
How do I tell which bootloader I have? When I try to boot it looks stock, just stays on the s3 logo. When I boot into download mode it's a Cyanogen guy.
Last working version of ROM I had was TouchWiz-based 4.1. I found on here but I did have CM11 and stock 4.4. before that.
Did you update your phone via OTA to get to 4.4.2? It's important to know so we can give guidance in terms of what can and cannot be flashed to your phone.
What cyanogen guy do you see in download? You mean the green Android dude?
Do this: copy CM10.2 to your external SD card, boot into TWRP and flash the ROM from the external SD card. If the flash is successful but the ROM gets stuck at the boot animation, boot into TWRP and wipe the cache, dalvik, and reboot.
Sorry for such a late reply! Been messing with other stuff lately, not enough time for my phone..
Anyhow,
audit13 said:
Did you update your phone via OTA to get to 4.4.2? It's important to know so we can give guidance in terms of what can and cannot be flashed to your phone.
Click to expand...
Click to collapse
Yes, I did update to 4.4.2 OTA.
When I boot into download it says bootloader rp swrev 3. When I said earlier I thought I had the cyanogen guy when booting into download mode I had it wrong. Download mode is still just the Android guy. I was talking about recovery which I have TWRP, with the Cyanogen guy (?).
When I just try to reboot the phone regularly it gets stuck on the SIII logo.
I tried installing CM10 like you said from my SD card and the install fails.
Any other ideas of what I can try?
Thanks!!
OK I installed CM11 and that's working.
At least I have a working ROM.
Originally the only reason I tried going back to stock from CM11 was so that I could have access to Galaxy Apps for my Gear 2.
I will fool with going back to stock later possibly.
Thanks again for your help, audit13.
GaggleFree said:
OK I installed CM11 and that's working.
At least I have a working ROM.
Originally the only reason I tried going back to stock from CM11 was so that I could have access to Galaxy Apps for my Gear 2.
I will fool with going back to stock later possibly.
Thanks again for your help, audit13.
Click to expand...
Click to collapse
Not related to your original post but if you dig enough you can probably find a form of Galaxy Apps that'll work on CM11! Or you could possibly rip the APK and get it to work.
This may work for you, but I don't own a Gear 2 so I'm not 100% sure.
http://forum.xda-developers.com/showthread.php?t=2593004

Categories

Resources