I need some help.
My Note 2 is rooted and unlocked with TWRP. I flashed Jelly Beans Build 4 and the installation seemed to go fine. Rebooted the phone when it was done and it hung on the first Samsung Galaxy Note 2 screen. After about 30 mins of waiting, I popped the battery and got the same thing. Reflashed and got the same thing. Flashed CleamROM and again stuck on the Samsung boot screen.
Not sure where to go from here. Any advice?
Did you make a back up before you flashed the rom?
I also have a usb otg cable and that allows me to save roms or even back ups in this case. Then in twrp for install you just choose external memory.
Have you tried wiping data again in recovery also?
Travisdroidx2 said:
Did you make a back up before you flashed the rom?
I also have a usb otg cable and that allows me to save roms or even back ups in this case. Then in twrp for install you just choose external memory.
Have you tried wiping data again in recovery also?
Click to expand...
Click to collapse
No, I screwed up and didn't make a backup.
And yes, I tried to wipe the data again. It was a no go. Tried to revert back to stock, but it looks like there's an issue with the Odin image currently (MD5 hash value is invalid).
Do you have a usb otg cable? Can you download another rom onto a thumb drive and flash that in recovery? Or re download the stock odin file and check md5 you might of got a bad download.
I just tried to reflash Jelly Bean and now I have "system software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
Not sure how in the hell that happened since I'm rooted and unlocked. Guess I have to wait to go back to stock. Need the file fixed though since there's 2 others that had the same hash check error.
Did you flash a rom with odin after you unlocked bootloader or did you use twrp or cwm?
Related
Okay so I was updating my i717 from UCLF5 team perfection to UCLF6 Collective AoCP ROM and think I bricked my phone. T_T
I forgot that I had encrypted both the phone and external SD Card. When I went into CWM Touch 5.8.3.4 I hung on the formatting /cache I then forced reboot back into CWM and went through a manually formatted stuff and wiped the caches. I then went to install the zip ROM and it said read-only bad.. I didn't know what to do so I tried to factory wipe again and no luck. So I then thought well Odin could work, but I couldn't download the hotfile without hotfile host bugging out with too many downloads.. So I final find a default stock official ROM that is a tar that Odin v1.85 can use, but it is taking forever and I don't know if it will complete, it is currently stuck at "SetupConnection.."
I can get the phone into CWM Touch 5.8.3.4 and can get into download mode, but cannot do ****. The external SD card does still have my titan backup of all system apps all user data and all user apps on it. I know the password for the encrypted SD card. However I cannot do anything because it keeps say read-only....
I also for some reason probably me not being patient enough 3 flash counters on the phone. Now if I take the phone back to ATT to exchange or somehow get it un-bricked will I be able to return the flash counter to 0 before turning the phone in...or will I have to cross my fingers and hope that they don't see it lol?
Does anybody know the best way to go about fixing this phone? I don't really know how to use Odin well and since CWM seems to be hanging on reformatting /cache it won't ever finish getting the phone to factory by itself. I have also tried to fix the permissions but doesn't work. Also tried to mount into USB while plugged in and it didn't want to do that either.
I did notice that a couple times it did boot into the UCLF5 ROM that was previously on the phone but it was back to stock ICS theme with no apps but settings and couldn't use the USB mass storage it just kept cycling itself and not connecting.
Okay so I did infact get it on the third try to flash 2.3.6 android factory default back onto the phone and in the process lost CWM recovery and when I went back into the market place to reinstall ROM manager after I put the ROM I want onto the internal it won't connect to Google Play even after getting onto wifi...weird and even said there wasn't an update after trying to update through att to ICS stock...
Your not still rooted right? An official update won't install if you are
Sent from my SAMSUNG-SGH-I717 using xda premium
adramalech707 said:
Okay so I did infact get it on the third try to flash 2.3.6 android factory default back onto the phone and in the process lost CWM recovery and when I went back into the market place to reinstall ROM manager after I put the ROM I want onto the internal it won't connect to Google Play even after getting onto wifi...weird and even said there wasn't an update after trying to update through att to ICS stock...
Click to expand...
Click to collapse
>ok so you got up with GB correct?
>Why not just put CWM back on the touch CWM is very simple to use odin one file in the pda slot and click then put the ROM you wanted to install in your OP. Links are in my signature
>then you can put the AOCP, that you said originally
BTW if you are trying to put the Off ICS use kies while putting your phone in download mode, not sure what you are doing with/thru ATT
There are several thread around for this method.
I have a Samsung Galaxy s3 which I successfully rooted over a year ago though I never bothered with a custom rom. I have now purchased a note 3 so in preparation for selling the S3 I did a factory reset through Settings to clear out all my apps, data and personal information. That all went well and the device booted back into the normal system a couple of times (I didn't check to see if root had been maintained or not) This weekend I got it out to sell it only to find that it boots through the first part of the routine with the Samsung moving logo but then sticks on the static SAMSUNG screen and will not go further.
I am able to boot into TWRP so would I be able to download a stock rom from somewhere, insert a micro sd card with the stock rom on it and recover through TWRP? Alternatively I do have an old full back up stored on my computer - I could transfer this to the micro sd and restore this through twrp - I can see this was made through twrm as the openrecovery-twrp-2.3.1.0-i9300.tar.md5 is stored with it. Of course if this works I would still need to perform a reset to get rid of all the personal data etc so could end up in the same situation later.
What recommendations do you helpful guys have?
gbswales said:
I have a Samsung Galaxy s3 which I successfully rooted over a year ago though I never bothered with a custom rom. I have now purchased a note 3 so in preparation for selling the S3 I did a factory reset through Settings to clear out all my apps, data and personal information. That all went well and the device booted back into the normal system a couple of times (I didn't check to see if root had been maintained or not) This weekend I got it out to sell it only to find that it boots through the first part of the routine with the Samsung moving logo but then sticks on the static SAMSUNG screen and will not go further.
I am able to boot into TWRP so would I be able to download a stock rom from somewhere, insert a micro sd card with the stock rom on it and recover through TWRP? Alternatively I do have an old full back up stored on my computer - I could transfer this to the micro sd and restore this through twrp - I can see this was made through twrm as the openrecovery-twrp-2.3.1.0-i9300.tar.md5 is stored with it. Of course if this works I would still need to perform a reset to get rid of all the personal data etc so could end up in the same situation later.
What recommendations do you helpful guys have?
Click to expand...
Click to collapse
try to some firmware dude
u have usb jig? use it to reset u binary :good:
and flash again with odin
if u have backup in cwm u can restore so Do it :good:
As you are going to sell it then follow the guide in general forum, stickies to return to stock. Factory reset before you boot the fresh firmware.
further
VerlyAnanda said:
try to some firmware dude
u have usb jig? use it to reset u binary :good:
and flash again with odin
if u have backup in cwm u can restore so Do it :good:
Click to expand...
Click to collapse
I don't have a usb jig whatever that is
I have an old back up on my computer which I can copy to an external SD card to put in the phone
I can then try using TWRP (I have this not CWM) to try restore the back up
This may work I can only try it - however I will still be in the position of needing to do the reset to clear all my data and put the phone back into "new" state and am concerned this may cause the problem again
Is this the best plan? I suppose once I get it working I can use ODIN to flash a stock rom
The problem is I understood all this a year ago when I rooted it but its all a little vague to me now as I decided not to do more than root the phone so I could back it up
formatting cache solved the problem!
gbswales said:
I don't have a usb jig whatever that is
I have an old back up on my computer which I can copy to an external SD card to put in the phone
I can then try using TWRP (I have this not CWM) to try restore the back up
This may work I can only try it - however I will still be in the position of needing to do the reset to clear all my data and put the phone back into "new" state and am concerned this may cause the problem again
Is this the best plan? I suppose once I get it working I can use ODIN to flash a stock rom
The problem is I understood all this a year ago when I rooted it but its all a little vague to me now as I decided not to do more than root the phone so I could back it up
Click to expand...
Click to collapse
I read someone had the same problem and just cleared the cache - so went into Team Win wiped cache and it restarted - guess I was looking for a complicated solution to something simple!
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
ryanskeltis said:
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
Click to expand...
Click to collapse
In the stock recovery do a full wipe as well. The wipe is more comprehensive than the custom recoveries. Perhaps that will help with the booting.
Which version did you try flashing? Mj9? More recent?
ryanskeltis said:
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
Click to expand...
Click to collapse
I understand you are probably panicking a bit over the trouble you have gotten yourself into with your Note, but I think you've been around long enough to know where to start this sort of topic. If you posted in the correct sub-forum, then you'd get better results. Right? :good:
Anyway, I wish you the best of luck fixing your phone.
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
ryanskeltis said:
I was running a custom firmware before i went to go restore it back to stock (going to exchange it for credit at a store). I made sure everything important i needed was backed up, then i booted it to Download mode like i would to flash it back to stock with Odin, everything worked fine. It finished and after it rebooted, it just started flashing the samsung galaxy note 2 white text for a quarter of a second then shuts off and just does that until i take the battery out. I tried going into recovery mode but it doesn't. I can get to download mode and try reflashing the firmware but it fails everytime.
What can i do to fix it? In my 5 years of using custom ROMs iv'e never had this issue. is my phone bricked?
Click to expand...
Click to collapse
What image did you flash in Odin? Also, when you flashed it did you use the pit file with it?
I've been running rooted with Alliance Rom build 32 for about a year with zero problems. The phone battery ran low last night and the phone turned off. When I turn it on it stops at the first logo. I can't get into Philz
recovery. It will go into downloader mode. I tried using Odin to revert to the stock MJ9 I started from when I used Casual. It flashed successfully (stock pit and MJ9) but still gets stuck at the the first logo and won't go into recovery.
SD card is removed. I haven't made any modifications to the phone for the past six months except adding a few well known apps from the store.
Any advice on how to get back to where I can load recovery and proceed to reinstall would be greatly appreciated.
PS.
I would have bought a new phone last year but it seems all the ones I like are bootloader locked. I can live without the stylus (would love a new note though...). Any recommendation on a replacement for the Note 2 would be much appreciated.
dsteinschneider said:
I've been running rooted with Alliance Rom build 32 for about a year with zero problems. The phone battery ran low last night and the phone turned off. When I turn it on it stops at the first logo. I can't get into Philz
recovery. It will go into downloader mode. I tried using Odin to revert to the stock MJ9 I started from when I used Casual. It flashed successfully (stock pit and MJ9) but still gets stuck at the the first logo and won't go into recovery.
SD card is removed. I haven't made any modifications to the phone for the past six months except adding a few well known apps from the store.
Any advice on how to get back to where I can load recovery and proceed to reinstall would be greatly appreciated.
PS.
I would have bought a new phone last year but it seems all the ones I like are bootloader locked. I can live without the stylus (would love a new note though...). Any recommendation on a replacement for the Note 2 would be much appreciated.
Click to expand...
Click to collapse
If you're looking for a newer phone that lets you unlock the bootloader, you might want to check out last year's Nexus 6 or the newer Moto X Pure Edition. The Nexus 6P from Huawei also looks nice and I'm keeping an eye on it as my next potential phone. The Nexus 5x from LG should also have a boo that can be unlocked.
-----------
Hopefully, you didn't flash the stock Verizon MJ9 4.3 firmware back onto your phone. If so, then you have locked your bootloader with no way to unlock it.
I'm thinking that you're probably getting confused with needing to flash Beanstown106’s modified MJ9 firmware (which doesn't return the phone to stock or contain the 4.3 bootloader). See one of my previous posts ( http://forum.xda-developers.com/showthread.php?p=58541771 ), which discusses a similar issue and has a link on how to flash the stock recovery back onto the phone if you'd like to try that rather than restoring the phone back to stock 4.1.2.
You could also just Odin restore the phone back to Verizon factory stock 4.1.2 and run Casual again to start fresh. See Droidstyle's restore guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ) to get instructions on how to flash back to 4.1.2.
Once back on 4.1.2, you need to go into the stock recovery and wipe cache /factory reset to make sure everything is wiped off the device for a fresh start. (Odin doesn't wipe everything in it's flashing process).
If you restore back to stock 4.1.2, then be careful not to let your phone take an OTA because if it gets updated to 4.3+, then you won't be able to unlock the bootloader any longer.
I usually remove my Sim card when restoring to stock 4.1.2... just to ensure I don't accidentally take an OTA update before I get it rooted again. (You can skip the initial phone Setup screen with the method in this YouTube video - https://youtu.be/qekEpn1Bufc ). It says it's for the S3 but works on the Note II as well. Once you get back into the phone and enable USB debugging in Developer options, you should be able to run Casual again. The phone doesn't have to be activated or on wifi to do this.
Once Casual is successful, it's safe to put the Sim card back in because I don't believe an OTA can install successfully with a custom recovery installed.
Good luck.
mattnmag said:
I
Hopefully, you didn't flash the stock Verizon MJ9 4.3 firmware back onto your phone. If so, then you have locked your bootloader with no way to unlock it.
Click to expand...
Click to collapse
All the ROM's and tools are from threads here so pretty sure I'm using Bean's modified MJ9. I was on Beans 4.3 for over a year before I went to the Alliance ROM.
You could also just Odin restore the phone back to Verizon factory stock 4.1.2 and run Casual again to start fresh. See Droidstyle's restore guide here: ( http://forum.xda-developers.com/showthread.php?p=34891181 ) to get instructions on how to flash back to 4.1.2.
Once back on 4.1.2, you need to go into the stock recovery and wipe cache /factory reset to make sure everything is wiped off the device for a fresh start. (Odin doesn't wipe everything in it's flashing process).
If you restore back to stock 4.1.2, then be careful not to let your phone take an OTA because if it gets updated to 4.3+, then you won't be able to unlock the bootloader any longer.
Click to expand...
Click to collapse
4.1.2 sounds like a better idea - I have that also.
Thanks your advice here is just what I was looking for in my effort to get this phone running again.
Update: I can still go into Download mode but cannot get a computer to recognize the phone now.
Not one of three computers, numerous cables including one out of the Galaxy Note 2 box and all the tricks I could find like pulling the battery while connected helped.
The first day of this problem (stuck at first logo) I was able to connect to the phone with Odin. I flashed the following:
1. sch-i605-16gb.pit
2. CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
Would something like http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 help?
Should I look into the JTag guys on ebay?
Thanks,
dsteinschneider said:
Update: I can still go into Download mode but cannot get a computer to recognize the phone now.
Not one of three computers, numerous cables including one out of the Galaxy Note 2 box and all the tricks I could find like pulling the battery while connected helped.
The first day of this problem (stuck at first logo) I was able to connect to the phone with Odin. I flashed the following:
1. sch-i605-16gb.pit
2. CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
Would something like http://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707 help?
Should I look into the JTag guys on ebay?
Thanks,
Click to expand...
Click to collapse
I don't know if a USB jig would help the computer recognize the phone again.
Since you tried 3 different computers and still couldn't get it recognized... I'm wondering if something got fubared when you Odin flashed the VRLJB stock Rom. So when you go to Device Manager in the computer, the computer doesn't even show anything connected at all?
I don't know that it would be worth the time, but (on the computer that last worked for your phone), you could try uninstalling the Samsung Drivers, and then use a program like DevManView to totally uninstall all Android related drivers. Restart the computer afterwards and then reinstall the Samsung USB Drivers (from here: http://www.samsung.com/us/support/owners/product/SCH-I605) . Then connect your phone back to the computer in Download Mode to see if it will reinstall the drivers and recognize it.
If the computer still doesn't recognize the phone after all that, then I'm out of ideas.
I'll try the devmanview driver cleanup (love nirsoft utils!) and install the driver in your link on the orginal pc which I use for flashing ROMs. If that doesn't work I'm going to look into sending it out to a JTag guy although they claim if you can get into download mode after they perform their magic that they were successful.
Went with the LG G4 which I'm very happy with. As far as getting the Note 2 running again I've been thinking l might buy a used Verizon Galaxy Note 2 motherboard on ebay rather than sinking a lot of time into trying to... should I say "unbrick" it.
If you ran casual first, it will not connect to the samsung driver, until you uninstall the USB services from the device manager, and then run find new hardware.
But maybe this will not help considering you already tried 3 machines?
I may have had the Samsung driver on all 3 machines. Good suggestion - I'll post back if it works.
Related question. I see you are running CM 12.1 - do you have standby battery drain issues? My 4.4.2 Alliance 32 would drain the battery down to 0 if I didn't plug it in at night even though I might still have 1/3 charge.
dsteinschneider said:
I may have had the Samsung driver on all 3 machines. Good suggestion - I'll post back if it works.
Related question. I see you are running CM 12.1 - do you have standby battery drain issues? My 4.4.2 Alliance 32 would drain the battery down to 0 if I didn't plug it in at night even though I might still have 1/3 charge.
Click to expand...
Click to collapse
Right, it was in the Adam Antler video, for casual. Once you use the casual on USB, the samsung driver will not work until you uninstall and reinstall USB system.
I can get almost 3 days out of a phone battery with little or no use. The one I am using could make it a day and 1/2, but I charge that one every night because I do not need and down time just in case.
I am using the nightly build, 12.1-20151222 12/22/15, I am not sure how the other builds are, or even the stable build for that matter?