Related
I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-
Nerz said:
I'm not noob to flashing or soft brick recovering but this has me confused...
I was running unNamed lastest for a lil while now. Everything was working fine until here recently, while stopped at a rest area checking a webpage my phone cut of and got stuck on a boot loop, only showing the kernal splash screen. Was like wtf? Tried pulling battery ,wiping cache and dalvik. No help. Was like that's fine, have a cwm back up from week ago. Nope didnt work. Was like ok let me try flashing something on my phone that's saved on sd. Flashed Miui, didn't work. Finally got back and tried using this Odin One click "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" by entropy from the flashing without triggering flash counter guide. Still boot loops only showing the black Samsung Galaxy S II screen. This is after 3 what the odin says as 3 successful flash attempts.
I'm at my wits end, of all the soft bricking i've recovered from, where I assumed as long as a bad bootloader flash didn't happen and i could still get to download mode I'm fine, it could be fixed. But this has me stumped.
*After going into 3e recovery and trying to wipe data, it won't even now go back into 3e recovery. Attempts to but says something like deleting cryption meta data or something of that nature.
-confused-
Click to expand...
Click to collapse
The one-click downloader is NOT from me, it's a repack of my tar file - and it's starting to sound like the one-click is doing something weird and not flashing the kernel properly.
Use regular old Odin (or Heimdall) to flash the raw tar package.
I'll try it. Though I don't understand how I am in the position I am in from browsing the web on my phone to directly going into a hootloop that neither that odin one click will fix, or any cwm roms won't fix.
Sent from my GT-I9000 using XDA App
I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App
Nerz said:
I won't have access to computer till later today but I'm trying to figure out what could be wrong. I was thinking that maybe my partitions were bad, but doesn't that odin used, repartition, using a pit file (think that is what pit is for)? Although, this was not from a flash, but rebooted from a couple weeks old successful flash of unNamed while browsing the web so I don't see how that can be the problem. However, even if the partitions were bad, wouldn't odin fail a flash because it has no where to send the firmware files? Also if it was a type of hardware failure, such as processor, wouldn't it not even show the kernel Galaxy S II splash screen? Or is this something that only the gpu handles? It was able to get into cwm before I used the odin though so I can't believe it's cpu because I'm sure that recovery should use it. Just can't figure it out, never had a problem with a boot loop a flash couldn't fix.
If I can't get it to work, will flashing a stock kernel with cwm increment the flash counter? If not I guess I could access my internal sd, try and pull my pictures and the roms off there and then send it to warranty. However I really don't want to. Thanks to anyone in advance.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Ok so after flashing the odin file from http://forum.xda-developers.com/showthread.php?t=1286432 it is still bootlooping at splash screen.
I'm not sure what my options are right now. I'm pretty sure bootloaders can't be the problem. I can't re-partition from odin because it says it can't open the specified file "(Line: 1828)". Is this because it doesn't have pit file? I don't understand how this problem manifested.
If I need to pull contents from sd card from cwm, will flashing a cwm kernal increment flash counter?
Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Don't repartition using a PIT, it's a great way to screw up your phone. (Hopefully you haven't flashed a PIT at all yet... If you have, I don't quite know what's going on.)
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Have yet to flash a pit file.
Sent from my GT-I9000 using XDA App
I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?
Juq said:
I'm in the same situation, except with a Sprint GSII. Have you found a fix, yet?
Click to expand...
Click to collapse
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.
hardgrid said:
Hello there from colombia, i have the same thing over here, i`m stuck with a SGS SGH I777 the flash counter says 7 and either flashing CWM 5 or re-uploading stock room wont work, i have no way to buy a jig and it is pretty odd that im in a different country and i can`t send my phone for warranty repair, i`ve read all over and seems like there is no answer for this. Can anyone get rid of the Deleting Crytion Meta data?? this is all i get. ( and eternal boot loop ).
Thanks in advance.
Click to expand...
Click to collapse
Will try to help, but will need more specific information.
The OP of this thread started bootlooping while checking a web page in his browser. So, how did it happen for you? Please give as much exact information as possible. Was it after a flash? Or did it start while you were using the phone? Or how?
Mine was connected to an aftermarket car charger while it happened. I read a post somewhere and a couple ppl it happened to believed the same thing, since it was in my 30 day trail period I sent it back to Sams club and got my replacement today. Since I didn't have a jig at the time, I didn't want to flash a cwm kernel and increase my flash counter so I lost some pics of my kids.
Not sure if it was charger related but I couldn't find a fix and wouldn't really call myself a noob at flashing. Might have some things to learn nut far from a noob.
Sent from my I897 using XDA App
I recently tried to root my Galaxy tab 10.1 "4G" that I got from Rogers using the files under the 4G portion in the Look Here First thread. Went into recovery to flash kernal and recovery files okay. Rebooted.
Then the bad stuff started: Boot screen loop.
After doing some more research it seems the reason why this happened is because the Rogers device is actually not a 4G device but a 3G device. Accordingly flashing the 4G files onto a 3G device has most likely caused this.
I am able to boot using the volume down + power button, however I cannot access recovery mode. I can access Downloading mode with Odin recognizing it. I tried to see if I was able to flash CWM onto it with no avail with the following screen
My guess is that it is due to flashing an incompatible Kernel... sigh.
So now I ask you gurus, is my Galaxy Tab 10.1 fully bricked or is there some other way I can unbrick this?
Thanks in advance.
I am going to assume that since you are able to get into download mode that you are not hard bricked but just soft bricked. In which case there must be some files that you can flash with odin to get you back to a stock version of honeycomb...or actually rather be able to flash another kernal through odin.
Again im not sure with how flashing with the gtab since I havent flashed anything on mine yet but I have experience flashing different kernals on my captivate and that was what happened to me numerous times.
That was my first thought too when I realized Download mode was still accessible. The file I tried was Overcome's CWM recovery file so that's one possibility why it was not able to go through. I would try flashing various kernels to see if I can get anywhere but I have yet to find any stock/relevant kernels to do so.
UPDATE: ... I apparently had KIES running in the background so I closed that and bam, it is now able to enter recovery mode. I did a factory reset, cache wipe and all but it still is not able to boot up. I reckon I still require a proper kernel. It still is impossible to access the device's internal storage however so I am not able to simple drag and drop the necessary files.
Is there a way of doing this via ODIN as is the only method I have available?
teamovercome net
Install new Recovery, then skip to restoring stock mod, I am doing it right now, hope it works. Was looking for solutions all day nothing else is there
did the very same thing when I first got my Rogers Tab: follow the Overcome guide exactly and all will be well again -- flash the re-stock package first, then jump straight to the latest Overcome 2.2.0 with the CWM and you can use Pershoot's kernel too if you wish.
lgsshedden said:
did the very same thing when I first got my Rogers Tab: follow the Overcome guide exactly and all will be well again -- flash the re-stock package first, then jump straight to the latest Overcome 2.2.0 with the CWM and you can use Pershoot's kernel too if you wish.
Click to expand...
Click to collapse
have you updated to the new 3 version? I did the update, one major issue was Browser was not syncing with chrome, gives an error, I am gonna try a full wipe and see, just wondering if anyone found something wrong with Ver. 3.
MyNameIsDan_ said:
That was my first thought too when I realized Download mode was still accessible. The file I tried was Overcome's CWM recovery file so that's one possibility why it was not able to go through. I would try flashing various kernels to see if I can get anywhere but I have yet to find any stock/relevant kernels to do so.
UPDATE: ... I apparently had KIES running in the background so I closed that and bam, it is now able to enter recovery mode. I did a factory reset, cache wipe and all but it still is not able to boot up. I reckon I still require a proper kernel. It still is impossible to access the device's internal storage however so I am not able to simple drag and drop the necessary files.
Is there a way of doing this via ODIN as is the only method I have available?
Click to expand...
Click to collapse
I have the exact same problem and i was wondering how do you close KIES while not being able ti boot because i need to go to recovery mode and everywhere i have looked there has been no answer.
Alecn8r7 said:
I have the exact same problem and i was wondering how do you close KIES while not being able ti boot because i need to go to recovery mode and everywhere i have looked there has been no answer.
Click to expand...
Click to collapse
KIES is a program that's running on your PC. I would hazard a guess that you just need to close it as you would with any program. The op was apparently connected to the computer when trying to get into recovery mode. If you're not connected to the computer when you hold power and volume - and you get the two options. Recovery on the left, download mode on the right. Choose the one on the left with the volume -button and start recovery when it's highlighted with volume +
Hope this helps.
Sent from my GT-P7510 using XDA Premium HD app
MyNameIsDan_ said:
I recently tried to root my Galaxy tab 10.1 "4G" that I got from Rogers using the files under the 4G portion in the Look Here First thread. Went into recovery to flash kernal and recovery files okay. Rebooted.
Then the bad stuff started: Boot screen loop.
After doing some more research it seems the reason why this happened is because the Rogers device is actually not a 4G device but a 3G device. Accordingly flashing the 4G files onto a 3G device has most likely caused this.
I am able to boot using the volume down + power button, however I cannot access recovery mode. I can access Downloading mode with Odin recognizing it. I tried to see if I was able to flash CWM onto it with no avail with the following screen
My guess is that it is due to flashing an incompatible Kernel... sigh.
So now I ask you gurus, is my Galaxy Tab 10.1 fully bricked or is there some other way I can unbrick this?
Thanks in advance.
Click to expand...
Click to collapse
Ok,...I see that there is enough info posted to get you back up... but just an FYI.. this device has a seperate recovery and kernel...in other words.. to root you just need to Odin a compatible recovery and then install the correct binaries to gain root access.
This device is so simple to root... I have an e4gt..and that device(until framaroot)..was a pain.. it's recovery is part of the kernel.. not only that, but it can be implemented different ways into the kernel
Back on topic..... locate a recovery.. Odin it... reboot.... boot to recovery.. flash root zip... If you have flashed something wrong but still have Odin mode.. like said above.. flash the stock rom or if you can't find it... flash the recovery(for the device) then boot to it and then put a custom rom on...
Gil81- You do realize the post you replied to was made back in January?
Sent from my GT-P7510 using XDA Premium HD app
Hi all, I hope you guys can help as I'm coming up blank here after days of trying to fix this.
First, yes I read this thread and a few people were reporting the same problem but the solution was always to flash a stock firmware with odin.
Right now my wife's phone is stuck in a boot loop, she doesn't do anything out of the ordinary with it, I rooted it when she first got it 3 months ago and then flashed a stock kernel to get rid of the yellow triangle and it has worked perfectly until last week when she told me it was stuck at the galaxy s2 logo. No problem I though, I'll just flash a stock rom with odin and all will be well.
Well it didn't work out that way, I've flashed the original firmware, an ICS leak, Villainrom 1.1 and XXKI3 multiple times, with and without pit file + re-partition. I've flashed the old bootloader and I've tried a few custom kernels as well, and multiple combinations of the above. Nothing is getting it past the boot loop. The only result I've had that is any different to how I started is with an ICS build I got a screen saying kernel panic upload (or something like that, I don't have that rom flashed at the moment). When I connect at this time odin recognises the phone so I guess it's in download mode.
I can't get into recovery mode so I can't do a factory reset, when I press vol-up, home and power I get a blank screen for a moment followed by the same boot loop. I can get into download mode and odin is reporting successful on every flash. When I flash a custom rom or kernel I get the yellow triangle, it goes away when I flash a stock rom or kernel.
According to my wife just before the crash android market reported updates available and she installed them. I don't know if that's related or not but she says when she went back to the phone it had hung so she turned off the phone, upon turning it on it was stuck in boot (the big animated purple S part of the boot) so she removed the battery and since then it doesn't get past the initial galaxy S2 screen, sometimes, depending on which kernel it's on, the galaxy screen goes blank for a second or two and then the logo comes back.
I've really tried everything I can think to try, warranty isn't really an option as I'm in Saudi Arabia and I've been told it will take 3 months to get the phone back, also I can't easily access a jig, I'd have to make one and I'm not too confident in my ability to do that.
If anyone has any ideas at this point please help, I can't think of anything else I can do here.
tl;dr random boot loop, tried flashing everything I can find, no recovery mode but download mode works fine, help!
davegene said:
If anyone has any ideas at this point please help, I can't think of anything else I can do here.
Click to expand...
Click to collapse
Flash a full wipe firmware and see if that helps, if you need one there is a link at the bottom of my insecure kernel thread.
Thanks Odia,
I just flashed the firmware at the bottom of your thread, I9100XWKE7_CL215725_REV02_user_low. Tried it twice for good measure.
Unfortunately nothing has changed on the phone, still can't get into recovery or past the galaxy s2 logo.
davegene said:
Thanks Odia,
I just flashed the firmware at the bottom of your thread, I9100XWKE7_CL215725_REV02_user_low. Tried it twice for good measure.
Unfortunately nothing has changed on the phone, still can't get into recovery or past the galaxy s2 logo.
Click to expand...
Click to collapse
Have you tried with repartition and update bootloader ticked?
I didn't tick either of those this time but I have ticked repartition with a different firmware that came with a pit file. Do I need a pit file or can I tick repartition without it?
Sent from my GT-I9100 using XDA App
davegene said:
I didn't tick either of those this time but I have ticked repartition with a different firmware that came with a pit file. Do I need a pit file or can I tick repartition without it?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
You need a pit file, use the 1 from the other firmware.
Ok, I just tried XWKE7 again with a pit file with re-partition ticked. Also tried flashing the old bootloader again with update bootloader ticked.
No change I'm afraid.
davegene said:
Ok, I just tried XWKE7 again with a pit file with re-partition ticked. Also tried flashing the old bootloader again with update bootloader ticked.
No change I'm afraid.
Click to expand...
Click to collapse
Most strange, look like your off to service
That's most unfortunate, I'm in Saudi Arabia and they have quoted 3 months to get the phone back under warranty although in reality I'd be lucky to get it back at all.
Are my options really exhausted or is there anything extreme I can try?
I ended up making a jig and took it for warranty repair and they were able to do it locally, it only took a few days.
The curious thing is even though I repartitioned several times using two different pit files the sdcard partition was still intact.
I'm pretty sure I was doing it right and the yellow triangle was coming and going as I was flashing stock and custom kernels so the flashes were taking.
I don't speak Arabic so I couldn't ask how they fixed it but what do you think was the problem? I was very surprised to find the data intact, it even had the same stock ROM that I flashed before I took it for service still installed.
Anyway thanks for your help in this thread odia.
Sent from my GT-I9100 using xda premium
I'd love to know what they did.
Sent from my GT-I9100 using XDA App
Ok... i´ll tell you the whole story
is the first samsung i have, i wanted to flash a custom rom i guess i was suposed to flash a MAIN ROM and then the rom but i didnt know so i just flashed the ROM with out the MAIN rom then my phone got stuck in the Samsung logo but everything was "fine" i was able to get into recovery and download mode .. but i needed to get the main rom into the phone memory then my plan was flash stock rom put all the files and then flash the custom so i began searching how to flash the stock saw odin3 1.85 was the programs i downloaded it and a stock rom the odin3 came with a pit file so i though i had to use it since i came there so i put the pit and the rom on pda i could flash dont really remembered why i was too late so i just took the battery off and went to sleep today i turned on the phone and the screen was just ALL WHITE .. i tried to flash the room again(now wothout pit or anythig just changed PDA) but couldnt.. i got stuck on nand write or boot.bin (i used many roms) then i read(about the pit files) that if i couldnt flash the rom but i was able to flash a kernel the memory may be screwed (because i used the pit) then i tried to flash a kernel not the whole rom and it worked pluged the phone with vol down (neve saw anything sreen was wthite) but i worked! y flashed siyah 3.4.2 phonw reboot and samsung logo was back so now the screen works but useless cuz get stuck on the logo i cant get into recovery or download mode, if i try recovery(both volume and power) a icon like circule(made with lines) change but gets stuck same if try download mode and now the computer do´t recognize the phone so i cant flash another kernel
i know is too much but please i really need your help i´ve tried everything i´ve been the whole day in the computer looking for something to do but i dont know that to do anymore :/
From your description, it sounds like you own the GT-I9100 or similar version of the Galaxy S II. Since this is the SGH-I777 forum, we wouldn't be able to help you very much unless you have the AT&T US version of the phone. If you have the international version, you should post in the international forums.
Jtag
Sent from my SGH-M919 using xda app-developers app
Hello, I've been rooting my phones for a long time and have never had any issues with the phone bricking on me. I made some noobish mistakes when flashing illusion ROM and formatted the system partition and thats where everything went downhill. After that i could get into TWRP and I tried several different ROMS and nandroid backups and nothing would work, just kept giving me the Galaxy Note 2 start screen that wouldn't go away, I waited hours several times I tried this. I found out how to get back to stock with Odin so I tried that and finally got back to stock 4.1.2.
I then tried the casual root method and got partition errors and when I unplugged my phone and tried to boot it back up all I get is a yellow triangle saying that my phone is trying to run unauthorized software and to take it to my nearest Verizon store. I can boot into download mode still but now my computer(Windows 8) will not recognize my phone. It makes the connection sounds but it doesn't show up in my device list or in my device manager. From here I tried uninstalling and re-installing the Samsung drivers but to no avail it still doesn't recognize my phone. Neither my computer or Odin recognize it plugged in. Can someone please help me? give me anything else to try, please.
casual killed the odin driver...the same thread you restored to stock look at the bottom of the section for the link to restoring the odin driver.
Keep reading.... at least thats how I fixed my phone today. I didnt realize I needed to unlock the bootloader so I ended up with the unauthorized software yada yada yada.....lots of reading, youtube video research, xda posts, trial and errors and sheer luck not to brick it worse and I was back up and running in a few hours learning a lot on the way....dont give up!!!
Sent from my SCH-I605 using xda app-developers app
How did you fix your phone?
I got the message about unauthorized software on my i605 note2. When I boot into recovery, I get the message. If I boot into download mode, I can use odin. I tried in reroot with root66 (just grasping at straws) and it took it. Then, the minute I unplugged, boom, the message.
I tried note 2 toolbox and got now where.
I downloaded original firmware from Sammobile.com. I have to unzip it, then look for it with odin I guess.
Amy ideas? Help??
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------
How did u get back to stock w odin?
I have the message when I boot into recovery. I can boot into download mode and odin sees my phone.
Sent from my SCH-I545 using xda app-developers app
ciniob said:
How did you fix your phone?
I got the message about unauthorized software on my i605 note2. When I boot into recovery, I get the message. If I boot into download mode, I can use odin. I tried in reroot with root66 (just grasping at straws) and it took it. Then, the minute I unplugged, boom, the message.
I tried note 2 toolbox and got now where.
I downloaded original firmware from Sammobile.com. I have to unzip it, then look for it with odin I guess.
Amy ideas? Help??
Sent from my SCH-I545 using xda app-developers app
---------- Post added at 04:55 PM ---------- Previous post was at 04:53 PM ----------
How did u get back to stock w odin?
I have the message when I boot into recovery. I can boot into download mode and odin sees my phone.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Stay away from that toolbox. Only use droidstyle's guide. Did you try the vramc3 file? That will make it completely stock again. Then use casual. Then flash roms again
Sent From My Sticky Note, Too?
How do I get Odin to recognize I605.zip file?
BoostedB18C said:
Stay away from that toolbox. Only use droidstyle's guide. Did you try the vramc3 file? That will make it completely stock again. Then use casual. Then flash roms again
Sent From My Sticky Note, Too?
Click to expand...
Click to collapse
I downloaded odin and unzipped it. I downloaded I605vramc3_I605VZ...zip.
I unzipped odin (I've used it before but I decided to unzip the latest copy just in case there were some upgrades...). I pressed "Pit" and looked for the file. I was unable to find it. So per the guide, I unzipped the .zip file with 7zip. Odin is still unable to find something that I can use. It's like Odin doesn't see the .zip or the unzipped .zip.
How do I get all those files that unzipped turned into something that Odin can find and that I can use?
I know Odin works. Grasping at straws I injected Root 66 into my note2. But of course that didn't remove the offending files so I still get the Unauthorized Software notice.
So in sum, can you tell me how to get Odin to locate the files I downloaded per the guide?
Thank you so much in advance for your patients. I'm not really new to this it's just that this is the first time that I've bricked my phone. Funny thing is the S4 took the goo manager just fine and then I was able to load TWRP onto the S4 with no problem.
I have not unlocked the S4 and I don't thing I unlocked the Note2. I know I used Easy Unlock on one of my phones but I think it was the Razr Maxx.
Anyway, the Note 2 was doing just fine until I tried to put TWRP on it. then I got the dreaded message.
Can't get Odin working
Bean running Beans v21 since it came out and loving it. Yesterday I installed the NBC Million Second Quiz app from the play store, and it froze my phone on a black screen....capacitive buttons would light up, and I could get the reboot menu, but selecting reboot did nothing. No worries -- I pulled the battery and restarted, and was stuck on boot animation. No worries -- booted into TWRP recovery, wiped cache and davlik. Reboot. Still stuck on boot animation. Now worried. Go back into TWRP and re-install Beans v21...It goes through Aroma, but stays on 0% installing forever. Now I figure that somehow the boot loader got re-locked, though can't imagine how that would happen. Boot into Bootloader, and it does say that it is the Samsung standard. Next I put it into download mode and ran CASUAL for 605. It takes, says it rewritten the bootloader, but when it tries to reboot the phone, I am again stuck on the boot animation forever. No problem -- now I should be able to go back into TWRP, wipe data, re-install a ROM since the phone is unlocked again, and move forward. But now when I go into recovery I no longer get TWRP..now I get the Verizon yellow triangle, I assume becuase CASUAL couldn't reboot to complete. I downloaded odin, the pit, and the 605 image and tried to restore to factory, but odin can't connect. I am guessing that this is because CASUAL replaced Odin.
I see a link to a youtube video, but can't open it from work.
So ... Can someone outline for me how to get odin to connect again after using CASUAL. Or, if there is a better next step, I'm all ears!
I am starting to think that someone at Verizon stumble across some way to slam that dreaded triagle onto our note2. Mine worked just fine until a few days ago when i tried to load twrp.
My counter shows 1 and my kernel shows custom (hence giving verizon a way out of the warranty). Funny thing though, i never opened the bootloader, i never re-rommed. I just rooted.
I am stuck. I can't get odin to see the original firmware i downloaded from this forum. I tried unzipping it w 7zip. I have the unzipped files but still odin can't see them.
What am i doing wrong here?
What does your counter show? Does it show a custom kernel ("yes" displayed when you open the note into downloadmode under kernel)?
Where did u c the video? Point me in that direction and I'll watch it for u and me and let u know.
Sent from my Nexus 10 using xda app-developers app
It WORKS!! My Note2 is back!!
ciniob said:
I am starting to think that someone at Verizon stumble across some way to slam that dreaded triagle onto our note2. Mine worked just fine until a few days ago when i tried to load twrp.
My counter shows 1 and my kernel shows custom (hence giving verizon a way out of the warranty). Funny thing though, i never opened the bootloader, i never re-rommed. I just rooted.
I am stuck. I can't get odin to see the original firmware i downloaded from this forum. I tried unzipping it w 7zip. I have the unzipped files but still odin can't see them.
What am i doing wrong here?
What does your counter show? Does it show a custom kernel ("yes" displayed when you open the note into downloadmode under kernel)?
Where did u c the video? Point me in that direction and I'll watch it for u and me and let u know.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
For those of you who have been following my saga. I have now recovered my Note2. I installed I605Vramc3 using Odin for the S3. I had to find the file that I downloaded (C:\Users\John\Desktop\KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5). I then copied that file into DESKTOP on my notebook. Now, I was able to point Odin in that direction. I plugged in my note while in Download mode, injected the file, and waited for the reboot. Botta bang, botta boom, the note rebooted with a flurry on downloaded new app updated.
The only problem I have is that I don't have root. Now I have to figure out how to inject root. But that's for another day!! As for now, I am up an running. I thought for sure I had a $600 paper weight.
The warning is gone and thank God it all works.
Thank you to everyone that participated in this saga. It's nice to know that I am not alone.
By the way, Casual repartitions your device. That may be why it failed for an earlier poster.
Update!
I just finished installing No You Verizon R515. My Baseband is I605VRAMC3. I am on 4.1.2. The instalation was a breeze. I am now safely backed up w TWRP.
Many thanks to Adam. Also thanks to Droidmotter video.
I am stoked I am so looking forward to going back into the Verizon store I went to for help and telling them I will not be spending $700 bones on a new note2!!
What kind of computer are you using?
Sent from my SCH-I605 using xda app-developers app
ciniob said:
I am starting to think that someone at Verizon stumble across some way to slam that dreaded triagle onto our note2. Mine worked just fine until a few days ago when i tried to load twrp.
My counter shows 1 and my kernel shows custom (hence giving verizon a way out of the warranty). Funny thing though, i never opened the bootloader, i never re-rommed. I just rooted.
I am stuck. I can't get odin to see the original firmware i downloaded from this forum. I tried unzipping it w 7zip. I have the unzipped files but still odin can't see them.
What am i doing wrong here?
What does your counter show? Does it show a custom kernel ("yes" displayed when you open the note into downloadmode under kernel)?
Where did u c the video? Point me in that direction and I'll watch it for u and me and let u know.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I have had a rooted for for 3 years now. G Nexus and now note 2. Wiped....flashed....backed up....wiped and flashed again hundreds of times. 2 days ago I wiped and tried to flash a nightly and bam.... nothin. Went to nandroid back and nothing there! Re booted and got yellow triangle. Wouldnt let me even boit into odin. After hours of screwing around I threw it against a wall.....dunked it in the toilet.... poured gas on it and lit that mofo. Paid 99 bucks and had assurion send me a replacement. My wife said I better not root it! Have made it 24 hours so far. Dont think im gonna make it much longer..... m u s t r o o o o t!
jersey droid said:
My wife said I better not root it! Have made it 24 hours so far. Dont think im gonna make it much longer..... m u s t r o o o o t!
Click to expand...
Click to collapse
You..., must..., root. You..., will..., root. TWRP, Titanium backup, they are calling you from the path less traveled. You can not resist. Your wife does not understand. You..., will..., ROOT..., ROOt..., ROot..., Root..., root..., roo... , ro... , r...,
You now it was funny. When I finally recovered my note2, I paused to contemplate my success.
I spent a few minutes then reading the posts of those who unsuccessfully tried to root using Casual. All I could think of was the fact that after a week of not being able to use my Note, I was not going to risk it.
Besides, I have my rooted S3. I am running android apps on my BB Q10. Hell, I even have the Nexus 10 and the Ipad (and two ipods) (I devices jb'n of course).
Did I really want to take the time and risk the yellow triagle?
I rooted it. No hick ups what-so-ever.
You must root. You can't not root.
Sent from my SCH-I605 using xda app-developers app
BoostedB18C said:
Stay away from that toolbox. Only use droidstyle's guide. Did you try the vramc3 file? That will make it completely stock again. Then use casual. Then flash roms again
Sent From My Sticky Note, Too?
Click to expand...
Click to collapse
Vramc3 was the solution, well, almost... I couldn't get Odin to see the file. Fortunately I placed it in the desktop folder on my notebook, odin saw it and i'm up and running.
Thank you for your help.
Sent from my SCH-I605 using xda app-developers app
DaveKnowsAll said:
Bean running Beans v21 since it came out and loving it. Yesterday I installed the NBC Million Second Quiz app from the play store, and it froze my phone on a black screen....capacitive buttons would light up, and I could get the reboot menu, but selecting reboot did nothing. No worries -- I pulled the battery and restarted, and was stuck on boot animation. No worries -- booted into TWRP recovery, wiped cache and davlik. Reboot. Still stuck on boot animation. Now worried. Go back into TWRP and re-install Beans v21...It goes through Aroma, but stays on 0% installing forever. Now I figure that somehow the boot loader got re-locked, though can't imagine how that would happen. Boot into Bootloader, and it does say that it is the Samsung standard. Next I put it into download mode and ran CASUAL for 605. It takes, says it rewritten the bootloader, but when it tries to reboot the phone, I am again stuck on the boot animation forever. No problem -- now I should be able to go back into TWRP, wipe data, re-install a ROM since the phone is unlocked again, and move forward. But now when I go into recovery I no longer get TWRP..now I get the Verizon yellow triangle, I assume becuase CASUAL couldn't reboot to complete. I downloaded odin, the pit, and the 605 image and tried to restore to factory, but odin can't connect. I am guessing that this is because CASUAL replaced Odin.
I see a link to a youtube video, but can't open it from work.
So ... Can someone outline for me how to get odin to connect again after using CASUAL. Or, if there is a better next step, I'm all ears!
Click to expand...
Click to collapse
Follow up -- Simply put: Delete installed samsung drivers in applications and device manager (plug in the device so you can see them, then delete them) and then plug in the phone and allow it to re-install drivers from windows update (or you can download yourself, since windows update can take a long time).
Once I got connected, I was able to ODIN in a stock image -- couldn't use Route 66, as it still gave me the yellow triangle, but VRAMC3 stock worked. Then back to Casual, TWRP, and freedom once again.