Need help with rooting and subsequently unlocking this phone free
Its carrier is Metro PCS and yes it does have a sim card slot
any help would be greatly appreciated
how to unlock unknown calls in to samsung exhibit t599n
i would like to know how to unlock the incomings calls in to exhibit t599n?
Rooted
dhizzy said:
Need help with rooting and subsequently unlocking this phone free
Its carrier is Metro PCS and yes it does have a sim card slot
any help would be greatly appreciated
Click to expand...
Click to collapse
I used Cydiaimpactor and it worked great. Still trying to figure how to install recovery mod though. But I can still use some rooted apps.
Help
wilbigdaddy2000 said:
I used Cydiaimpactor and it worked great. Still trying to figure how to install recovery mod though. But I can still use some rooted apps.
Click to expand...
Click to collapse
how did you do it i need help doing it
Help unlock my SGH-T599N please!
Hi... BRAND NOOB ALERT
*I've got the Metro PCS sgh-t599n*
It was rooted by my ex before he split*And Iv been trying to unlock my phone for almost a month since by myself. And I don't know what I'm doing.
So far, the only thing I was able to unlock was a virus onto my step moms laptop. Very nice way to say thanks to her. SMH. (My dad was able to fix that but not without being super mad =/)
*Do you know how I can unlock it??*I don't have one of those box thigs but I can connect it to my computer with USB*
I have the T mobile sim card (and like a total rookie) I activated (and paid for) prepaid service through them 3 wks ago... Sigh.*Guess I was a little over confident I would be able to figure this out lol I have done soooo much reading on it its insane! And although it's very interesting, ai t nobody got time.... So..
I have already canceled my metro service and didn't have them for 3 months prior, so getting my network sim unlock code from Metro isn't an option.
Also, (like a big giant noob) I thought I would be cute and try to guess unlock pin when I had some time to kill one day*SMH.*Now I may have made it to where I will need a PUK code also.*
IDK... That's probably obvious that tho
If anyone can help me with any advice or information, or even just point me in the right direction you would definitely be my hero. *This is the longest I have ever been away from my 6 yr old and although we Skype often, if I am not home (or somewhere with wif ) he has no way to reach me atm, even tho I'm paying for service.*Boooo. Lol. Someone help the newbie! Please and thank you =)*
T599n problems
After soft bricking and installing tysons dedoeoxed pre root for t599n i accidentally clicked repartition when i flashed in odin. Everything worked fine on phone for about a week or two then i didnt charge it for a night plugged it in then went straight to download mode. I have cruised these forums for about a month and a half straight tried numerous roms stock and rooted pits and everything else i can think of just fails... i am at a loss can anyone help me save this damn piece of tech lol?
joshjonte said:
After soft bricking and installing tysons dedoeoxed pre root for t599n i accidentally clicked repartition when i flashed in odin. Everything worked fine on phone for about a week or two then i didnt charge it for a night plugged it in then went straight to download mode. I have cruised these forums for about a month and a half straight tried numerous roms stock and rooted pits and everything else i can think of just fails... i am at a loss can anyone help me save this damn piece of tech lol?
Click to expand...
Click to collapse
What step does it fail at?
Found the pit here:
http://forum.xda-developers.com/showpost.php?p=51853378&postcount=256
So, I'd check off the repartition again, use that pit file and then redo the t599n Odin file from before.
es0tericcha0s said:
What step does it fail at?
Found the pit here:
http://forum.xda-developers.com/showpost.php?p=51853378&postcount=256
So, I'd check off the repartition again, use that pit file and then redo the t599n Odin file from before.
Click to expand...
Click to collapse
Thanks i will try this pit. every time i put stock Rom for T599v i believe Tmo model or for T599n when i put pit and prerooted it says writing pit never shows percentage bar then lags out or fails to write as it says. then when i try to use odin again it will freeze for 5 minutes or more then fail. I tried to use heimdall front end too but kept saying all firmware.xml was missing in the multiple Roms i put on there then when pit is put in heimidall it wants me to manually build it i would have no problem with that but dont know the partition segments. This is my first time getting this deep into phone tech. Sorry if i use wrong teminology. I will report back with my findings ASAP
---------- Post added at 04:02 PM ---------- Previous post was at 03:57 PM ----------
es0tericcha0s said:
What step does it fail at?
Found the pit here:
http://forum.xda-developers.com/showpost.php?p=51853378&postcount=256
So, I'd check off the repartition again, use that pit file and then redo the t599n Odin file from before.
Click to expand...
Click to collapse
joshjonte said:
Thanks i will try this pit. every time i put stock Rom for T599v i believe Tmo model or for T599n when i put pit and prerooted it says writing pit never shows percentage bar then lags out or fails to write as it says. then when i try to use odin again it will freeze for 5 minutes or more then fail. I tried to use heimdall front end too but kept saying all firmware.xml was missing in the multiple Roms i put on there then when pit is put in heimidall it wants me to manually build it i would have no problem with that but dont know the partition segments. This is my first time getting this deep into phone tech. Sorry if i use wrong teminology. I will report back with my findings ASAP
Click to expand...
Click to collapse
update:<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T599N-Pre-rooted.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is what i get everytime i run odin. I have tried every pot on my laptop and i have used 4-5 different usb cables. i have even unistalled all driver reinstalled them and also odin as well.
Another option might be to load a custom recovery and a rom to see if that will at least get you booting.
I have tried putting multiple recoverys pits roms everything i have found on XDA and Android forums. damn thing will not format. just only can get to download mode after i hit buttons to put it there. idk maybe its just hard bricked for good without JTAG and i should just use it for batting practice
---------- Post added at 04:49 PM ---------- Previous post was at 04:45 PM ----------
Well newest update. after 3 cord changes uninstalling all variotions on each usb port for drivers reset with intell android driver 1.4 came up with two come id's at first 0com:8 1com:5 tried couple times to repartition with pit and install preroot. failed . Now phone will not even turn on to get to download mode @[email protected]
---------- Post added at 04:55 PM ---------- Previous post was at 04:49 PM ----------
or do you mean pit file and recovery flash?
---------- Post added at 05:25 PM ---------- Previous post was at 04:55 PM ----------
i have since got phone to turn back on and put in download mode. Still failing to part even with recovery.tar in PDA with pit in PIT. but now it wont register anything but 0 instead of 1 and com like it was before.. Idk if that has something to do with it. I have removed Sd card to make sure it wasnt showing as two seperate ids. and even though it failed to flash on download mode it shows CUSTOM PIT BINARY!!
Ah, I was just suggesting to load the recovery, boot to it and flash a rom, without messing with the pit.
Something else to try:
http://forum.xda-developers.com/showpost.php?p=48072384&postcount=68
es0tericcha0s said:
Ah, I was just suggesting to load the recovery, boot to it and flash a rom, without messing with the pit.
Something else to try:
http://forum.xda-developers.com/showpost.php?p=48072384&postcount=68
Click to expand...
Click to collapse
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
i get this when i tried to flash param file. trying again. do you think maybe i fired something? it registers but i have only gotten odin to flash properly once.
---------- Post added at 11:38 AM ---------- Previous post was at 11:22 AM ----------
joshjonte said:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
i get this when i tried to flash param file. trying again. do you think maybe i fired something? it registers but i have only gotten odin to flash properly once.
Click to expand...
Click to collapse
Beginning session...
Session begun with device of type: 131072
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...
This is what i get trying to flash with Heimdall front end flashing with pit and param
Wanted to see if it was just odin. think it might be though because odin doesnt even try to show it loading up pit or anything. im using odin 3.04
You should be able to install a recovery without needing the pit file or anything else. Just make sure that Re-Partition is unchecked so it doesn't think it needs a pit file period.
es0tericcha0s said:
You should be able to install a recovery without needing the pit file or anything else. Just make sure that Re-Partition is unchecked so it doesn't think it needs a pit file period.
Click to expand...
Click to collapse
anything i flash in odin gives me pit failure
Hmm. You can try the newest Odin. But you get that error with Re-Partition off as well? Strange. You might possibly have to get it to an actual service who should have the full actual file instead of bits and pieces rolled into a tar. Or get a JTAG service.
es0tericcha0s said:
Hmm. You can try the newest Odin. But you get that error with Re-Partition off as well? Strange. You might possibly have to get it to an actual service who should have the full actual file instead of bits and pieces rolled into a tar. Or get a JTAG service.
Click to expand...
Click to collapse
I will try newest odin to see if that changes anything. ugh JTAG not what i wanted to hear :/
Related
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
http://forum.xda-developers.com/showthread.php?t=1727443
You can try that thread there. The same thing you are experiencing has happened before I Hard Bricked my phone.
Just be careful when you are messing around with the S3 it can be so confusing with all the S3 Variants out there.
Hopefully this will workout for ya
Fuzz21 said:
http://forum.xda-developers.com/showthread.php?t=1727443
You can try that thread there. The same thing you are experiencing has happened before I Hard Bricked my phone.
Just be careful when you are messing around with the S3 it can be so confusing with all the S3 Variants out there.
Hopefully this will workout for ya
Click to expand...
Click to collapse
Yeah, I'm reading this now. I just did what it said, but still no dice.
JibbsIsMe said:
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
Click to expand...
Click to collapse
Can you flash a rom in recovery? Also do you have Odin set to the correct settings?
I had a problem with mine where Odin wasn't doing anything at all. It would start but never finished. I changed the USB port and was good after that. Weird because my sgs2 and sgs3 international were fine using the one USB port. Just a thought to try a different port if it stops or fails
Sent from my SGH-I747M using xda app-developers app
brfield said:
Can you flash a rom in recovery? Also do you have Odin set to the correct settings?
Click to expand...
Click to collapse
I can't flash ROMs, since I can't seem to figure out how to get things onto my SD card or my External SD Card.
Problem solved!
JibbsIsMe said:
I can't flash ROMs, since I can't seem to figure out how to get things onto my SD card or my External SD Card.
Click to expand...
Click to collapse
OK, I got it. First, I followed this: http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
I stopped right after step 8. I then put my Ext SD into my old phone, formatted it, and put on this: http://forum.xda-developers.com/showthread.php?t=1732191
Then I went into recovery, and flashed that ROM. Then rebooted, and I'm fine now! YAY!
I almost wasted $730....
--Jeremy
Awesome stuff !!
Mine is still a 500$ paper weight, LOL hopefully I can fix it :S
Good luck, I would hate to lose my phone on it's first day...
JibbsIsMe said:
Good luck, I would hate to lose my phone on it's first day...
Click to expand...
Click to collapse
Thanks budd
I really hope I can resurrect it from the Dead.
JibbsIsMe said:
I have the Bell GSIII (i747) and I bricked it while playing around with the Toolkit. I downloaded the stock firmware from here, but whenever I flash it, Odin says this:
and by phone says: "SECURE CHECK FAIL: aboot"
aboot.mbn is a file inside the tar.
I can access Recovery and Download mode easily, but the problem is that when my phone boots, It flashes SAMSUNG, and then Samsung Galaxy S III, but then the screen goes black. To reboot it again, I have to pull the battery.
Any help would be greatly appreciated, thanks!
--Jeremy
Click to expand...
Click to collapse
I hate to threadjack, but this is the only thread I can find mention of this error with the sgs3 with.
mine did the same thing last night, thought I bricked.. but it didnt brick, used the phone all day today with no problems, tried to root again today with at&t method with odin, and I keep getting the same error. Its a bell i747m using odin 3.0.7
Any ideas?
Edit: Also I have tried several usb ports and a couple different cables.
Hey guys, a friend asked me to take a look at her old Samsung Fascinate because she wasn't getting any service on it. So, I took a peek and something's gone wrong. Under the About Phone section it seems the phone doesn't know a lot of things such as the Hardware version, Baseband version, phone #, MIN, PRL version, ERI version, MEID, etc.
I don't really know why it would be stuck like this, even after a hard reset and a factory wipe. The phone was never rooted or anything.
I did attempt to root it following a few different guides I found in this forum ,which I might add is not nearly as easy as it was for my Nexus S. None of my attempts worked, SuperOneClick just hangs and I tried the guide by droidstyle(?) but the links to "powerwashed 20 b3" result in a .7z that I can't successfully extract from.
So I'm kinda stuck on this and looking for a little guidance on what to try to get this thing working.
XavierBK said:
Hey guys, a friend asked me to take a look at her old Samsung Fascinate because she wasn't getting any service on it. So, I took a peek and something's gone wrong. Under the About Phone section it seems the phone doesn't know a lot of things such as the Hardware version, Baseband version, phone #, MIN, PRL version, ERI version, MEID, etc.
I don't really know why it would be stuck like this, even after a hard reset and a factory wipe. The phone was never rooted or anything.
I did attempt to root it following a few different guides I found in this forum ,which I might add is not nearly as easy as it was for my Nexus S. None of my attempts worked, SuperOneClick just hangs and I tried the guide by droidstyle(?) but the links to "powerwashed 20 b3" result in a .7z that I can't successfully extract from.
So I'm kinda stuck on this and looking for a little guidance on what to try to get this thing working.
Click to expand...
Click to collapse
You obviously didn't find droidstyle's guide because it's about as easy to follow as you're going to get. Follow his directions to go back to stock and go from there
Crawshayi said:
You obviously didn't find droidstyle's guide because it's about as easy to follow as you're going to get.
Click to expand...
Click to collapse
Not to be an ass, but...
XavierBK said:
I tried the guide by droidstyle(?) but the links to "powerwashed 20 b3" result in a .7z that I can't successfully extract from.
Click to expand...
Click to collapse
Crawshayi said:
Follow his directions to go back to stock and go from there
Click to expand...
Click to collapse
The phone still IS stock.
XavierBK said:
Not to be an ass, but...
The phone still IS stock.
Click to expand...
Click to collapse
If I were you, I'd go to DROIDSTYLES
GUUDE and ODIN back to stock( even though you say it IS stock). Try it, his guide is our BIBLE. :thumbup::thumbup:
Sent from my SCH-I500 using xda app-developers app
Okay my bad, didn't see that you mentioned droidstyle's guide already. Even so, if I were in your spot I would:
1) Odin back to stock via droidstyle's guide (yes I know you said you're already on stock, but it's better to start as fresh as can be)
2) Try a few different roms (AOKP ICS, CM10, AOKP JB, etc) and see if anything changes (personally I have been using CM10 nightlies as a daily driver and it's my current favorite)
3) Try to activate the phone via *228
Hopefully just flashing a new rom will fix this (she will LOVE you for installing a JB rom, they are simply the best the fascinate has ever been).
Note: You MUST Odin back to stock if you plan to go backwards (for example if you want to try a GB rom coming from CM10)
Well, I've been trying the "Back to stock" portion of the guide for a while now... haven't had any luck. I keep ending up with a solid color screen on the phone (blue, white, and magenta are what I've seen so far...) and Odin just seems to stall. Twice it has run the cycle but ended in FAIL. Any ideas?
As far as *228... it won't connect to anything, not even for emergency calls.
That could be caused by a bad cable or usb port... try different cables (if possible) and different usb ports. Also, I've heard uninstalling and reinstalling the samsung usb drivers can work as well
Different cables - Check
Different ports - Check
Uninstall/Reinstall drivers - check
Still a no go. I haven't gotten a solid screen color in the last 10 or so tries but they still fail. I'll post exactly what Odin reports...
Code:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> Enter CS for MD5..
<ID:0/010> Check MD5.. Do not unplug the cable..
<ID:0/010> Please wait..
<ID:0/010> Checking MD5 finished Sucessfully..
<ID:0/010> Leave CS..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> param.lfs
<ID:0/010> Sbl.bin
<ID:0/010> boot.bin
<ID:0/010> recovery.bin
<ID:0/010> zImage
<ID:0/010> factoryfs.rfs
<ID:0/010> dbdata.rfs
<ID:0/010> cache.rfs
<ID:0/010> movinand.bin
<ID:0/010> modem.bin
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
This still sounds like it's probably related to the cable, as I know there have been people here with problems like this and they had to really search around until finding a usb cable that would work. I wish I could help out more on that subject, but as I have never had this issue I don't have any specific recommendations. I think someone had said they finally got a Kindle Fire usb cable to work, but I'm not 100% on that.
My only other suggestions for this would be to make sure you're using the latest version of Odin and maybe try re-downloading the files in case one got corrupted somehow. Pull the sd card out too just for the heck of it while you're flashing. Maybe even try this on a different PC if you have one available?
I managed to try it on another machine with different cables and it still ended in failures. Any other ideas? I'm about to give up on this thing.
I'm out of ideas honestly. What I would do is maybe post this problem in the general Q&A forum to get more views and opinions as this might qualify as a general hardware failure
**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Under the root66 image the phone is only registering 4 gigs of available space.
Junior member, where did you find the alternate restore method?
exmeaguy said:
Junior member, where did you find the alternate restore method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
exmeaguy said:
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
Click to expand...
Click to collapse
It has an odd file extension .xz (perhaps meant to be .gz) so I told 7zip to extract it. resulting file ended in .tar.md5. Then it works.
Hope this helps.
Thanks Junior member I will try that.
exmeaguy said:
Thanks Junior member I will try that.
Click to expand...
Click to collapse
I'm curious why you keep calling him junior member?
Sent from my SCH-I605 (AKA NOTE 2)
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
exmeaguy said:
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
Click to expand...
Click to collapse
hahahaha
Wasn't sure if it was a newbie hazing kind of thing. That's funny though. No worries!
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
exmeaguy said:
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
Click to expand...
Click to collapse
Originally I was rooted with Adam Outler's casual / ODIN method (which was flawless first time round). I had tried the root66 this time just to see if it would actually take with ODIN since the stock restore kept failing. I was just desperate to find a rom that would "pass" on ODIN. I just needed to know my phone was still capable of booting fully back into android. Even if it happened to be without radio / activation capability or a wrongly registered internal storage space (which was friggin wierd, couldn't even take a screenshot).
I will re-root with Adam's process, when the kinks are out (say next weekend when I have a couple days it doesn't matter if my phone is dead . I had A.O.'s original root running for a couple weeks and it was great. The implementation was smooth, not requiring reinstalling / restoring anything. I'd backed up of course but it was one of those nice times the backups weren't necessary.
So at the moment for the sake of my job, I'm leaving it stock for the week. I just can't be without a phone for work.
rdeckerr said:
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Click to expand...
Click to collapse
Welli have the same exact issue. I am so lost its riddiculous. I have been working on this for over 20 hours and have gotten no where.
The only thing. Can add is that I attempted to root my device with the method that injects the 1 gig file in the system. Worked fine and installed cwm. Restarted and bricked with the unauthorized by verizon message. Downloaded the stock file without bootloader first and worked fine. I then tried every sinfle methodand trick I coild find to no avail.
Every time I try to install the baseline bootloader so I can unlock it fails at the end. If itry to put a full stock image on it fails at the beginning.
They both fail when tryinf to do the sboot.bin. so its obviously with that.
I need some ind of fix but no one seems to have it. I cant be doomed to a uncustomized device!
I am thinking of seeing if my verizon store will take it back and give me a fresh one so I can do the original exploit method.
It might work. Ive had the phone for less than a month.
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
universexda said:
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
Click to expand...
Click to collapse
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot.
Sent from my SCH-I605 using Tapatalk 2
rdeckerr said:
**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Click to expand...
Click to collapse
Is there a fix for this? I have been getting the same error message via odin. Can someone post the fix or link so we can get back up and running...thanks.
kintwofan said:
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot
Click to expand...
Click to collapse
The alternate restore won't attempt to restore the bootloader to stock right?
universexda said:
The alternate restore won't attempt to restore the bootloader to stock right?
Click to expand...
Click to collapse
That's right. It will restore everything except the boot loader. It's really to restore and keep boot loader unlocked, but add an added benefit let's unbrick the new ota.
Sent from my SCH-I605 using Tapatalk 2
Same problem
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
aka113 said:
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
Click to expand...
Click to collapse
Did you actually read any of this thread? We got his phone working.
Sent from my SCH-I605 using Tapatalk 2
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
I had the latest 4.1.2 stock OTA installed via CWM and I wanted to unroot and go back to stock and that seemed to work fine.... I went to the old version VRALL4 and once rebooted it asked me to update OTA so I did and that was fine........ and it asked me to do it again for some reason and now I'm in a boot loop. The Galaxy note 2 logo flashes on the screen real fast and turns off over and over. I can only get into ODIN and not stock recovery. I've tried re-flashing the original odin package, and the pre-rooted odin packages and nothing is working.... what can I do? am i fux0rd? thx
edit: also USB all drivers are installed .......
Click to expand...
Click to collapse
Checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it should fix your boot loop problem. You'll need the two files that he makes available just below the picture. I've had others tell me that they used those files to successfully fix boot loops.
RomsWell said:
Try a factory reset in the stock recovery. Then give it a whirl.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I can only get into odin... not even stock recovery. the odin app doesn't even work most of the time....
If i hold vol up + power + home it just continues to boot loop flashing the note 2 logo....... downloading one more odin file to see if this can fix it..... :crying:
I knew I should have used triangle away before doing this as if I take it to the VZ store they're going to be able to tell that it'd been modified before....
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
BoostedB18C said:
The lesson you should learn from this is DO NOT ACCEPT OTAS! Not sure how you haven't understood that since it has been stated more than enough times in almost every thread.
Click to expand...
Click to collapse
First of all, I'm not a noob and I did get the system back up.... as I said above i was trying to UNROOT not ROOT my device using Odin which I have done many times. This is the first time I've ran into the boot loop issue.... so I flashed a stock unrooted odin tar.md5 and this is the issue that I had.... now when I did that, I thought I was unrooted but obviously the bootloader did not get flashed back to stock... anyways thanks for your oh so useful post in lumping me in with the n00bz... :laugh:
anyways
now im facing another issue where its still has the rooted bootloader installed but an "official" stock rom on it.....
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
BoostedB18C said:
I'm not saying you're a noob. All I'm trying to get you to understand is to read before doing. As with your unlocked bootloader issue, you probably overlooked that there are 2 ways to restore to stock. One re locks the bootloader and the other doesn't. Read more and don't skim the guide, that's all I'm saying my dude.
Click to expand...
Click to collapse
thats what Ive been trying to find for ages and I've downloaded 4 or 5 different "stock" odin packages which puts me back to the original 4.1.1 I506VRALJB version....
So I'm trying to find the ODIN package that wipes everything (bootloader esp)....... thanks..... and with goo.im having so many issues its really tough finding all the files I need.
....hmmmmmmm so I updated superSU and unchecked a box that "hides" root - but if I accept another OTA i'm sure I'll be stuck with another boot loop until I really flash the unlocked bootloader with the OEM one right?
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
This is where I pointed the last person I helped and it worked for them
http://forum.xda-developers.com/showthread.php?p=41584579
BoostedB18C said:
DO NOT ACCEPT OTAS! Lol. I forgot which thread had the right file. I'll look around and try to find it. Which files from which threads have you tried?
Click to expand...
Click to collapse
lol yea my goal is to be on the latest and greatest OTA but of course im not going to accept an OTA until I'm 100% locked first....
http://forum.xda-developers.com/showthread.php?t=2040264
Tried this one which puts me on the original oem rom that came with the phone w/ no updates....
The only way I was able to get out of the boot loop is use the PIT file and this file root66_VZW_stock_system.tar.md5
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
http://d-h.st/Qd4
I think this is the baseline unrooted baseband......trying it out.
enkrypt3d said:
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
Here is where I Found the "pre-rooted" file... I put that in the bootloader section of ODIN along with the PIT file and this fixed my boot loop problem.
so even tho ODIN mode says "official" and not custom - this is bc I disabled root thru superSU even though its still rooted..
Click to expand...
Click to collapse
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
BoostedB18C said:
I would advise you to stay away from guides that are not on xda. Just because there is more knowledge here.
Click to expand...
Click to collapse
Just showing where I Got the file to recover from boot loop.... that guide isnt even for the right phone model...... read back as I added a bunch to my last post.
Trying to flash with the below file in the "phone" section so that it wipes the entire phone but it fails.... I've also removed superSU by using the option to "unroot" inside SuperSU..... whats going on? I have the PIT File in place, "phone bootloader update" checked or unchecked doesn't seem to matter..... and same for Phone EFS Clear......
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> hidden.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> param.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> recovery.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> sboot.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
http://forum.xda-developers.com/showthread.php?t=2120726
This is the exact problem I have.....
From what I am understanding you can't write boot on Vrall4. So you would need to be on vraljb before being able to re lock the bootloader. I'm my head it makes sense but not sure how you need to go about it. I only looked at it real quick and I can't look into it right now. I'll check with you later and see what you have figured out. So post anything that you come across.
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Or just don't unroot it. Problem solved??
Sent from my SCH-I605 using Tapatalk 2
enkrypt3d said:
finally resolved it by erasing nand and flashing root66, then factory reset, then flashing one without the sboot.bin......
it took so many times - i dont think ive ever flashed this phone this many times before....... ugh what a pIta.... never rooting this phone again as its so freakin tempermental.
Click to expand...
Click to collapse
please instruct me on all steps u took... where did u put the files and what u checked and what not.. i have the same exact problem except it gets stuck at Logo... i cannot go into recovery as well.
i have tried all the same files as u and all fail except root66 but it stays stuck on logo
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
enkrypt3d said:
as far as I can remember, take odin, put the pit file in the pit location in odin:
http://d-h.st/mKu
Then flash with root66...
http://androidfilehost.com/?fid=9390210501348163619
then see if u can get into stock recovery and do a factory reset and then go back into odin mode.... then tick nand erase and then use the alternate restore and put it in the phone section of the ODIN app and flash it....... of course this doesnt have the sboot but this was the only way i was able to get it back up....
if u are able to get the phone back up with root66, then stop there..... erasing the nand and not doing it right can brick it. i spent 2 days fixing mine and I must have tried flashing the phone at least 25 times... when I got root66 up and running I went into SuperSU app and went into settings and theres an option to remove or hide root. this may have helped. right now im finally on the latest OTA and it says official (not custom rom) in odin mode and in the about phone section. Hope this helps.
keep the back cover off the phone bc you'll be pulling the battery out if it gets stuck... good luck. FYI I always use the PIT file and that always seemed to have helped.
Click to expand...
Click to collapse
ah man... i can get PASS! on root66 but it still gets stuck at logo.. anything else i flash will just fail at boot.img nand write... think im just f*ck'ed dude..
my thread is here if anything... thank you !
http://forum.xda-developers.com/showthread.php?t=2296441
Best bet is to erase nand and try flashing with the alternative rom and pit file at the same time...tomorrow I'll post the files I used as most mirrors are slow as balls..
Sent from my SCH-I605 using xda app-developers app
Hi,
I've got this problem with a friends(girl) phone.
Her phone was stuck at the firmware upgrade screen(the one with firmware upgrade encountered an issue). So she searched the internet for a solution and did some things with kies and odin. But nothing worked so i offered to help her.
So i searched and found this article. i followed all the instructions and downloaded 3 different versions of odin V3.07, V1.3 and V1.85.
Specifications of the phone:
samsung Galaxy S II GT-I9100 16GB
what i've tried so far:
i followed the instructions from te link above and tried it with the following roms
-I9100GXXLB1_I9100GATOKL1_ATO
-I9100XWLP9_I9100KPNLP1_KPN
-I9100XXLSJ_I9100OXXLS1_OXX
i also tried the gingerbread and the ICS version
i also tried the pit file. but nothing works, the progress get stuck like in this example
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100GXXLB1_I9100GATOKL1_I9100GXXKL4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone help me with this problem? I also have a JTAG programmer but don't know how or what to do with it.
Check out this guide:
http://forum.xda-developers.com/showthread.php?t=2345831
Look for hopper8's thread.
And stop flashing pit files.
Sent from the little guy
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Basseytje said:
Ok, i've followed every step but the phone is still bricked.
i've noticed something else: i've tried some different packages and versions of odin, and when in download mode on the phone the custom binary download is saying Yes(5 counts) en the Current binary is changing from custom to samsung stock back and forth.
Click to expand...
Click to collapse
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
when u go to download mode, does it show your model number??
Hopper8 said:
I updated the OP today, with an extra option for i9100 (which you have). It's flashing JB leak (stock ROM, 3 part firmware) via Odin, which will wipe your device as it flashes. Give it a go.
Click to expand...
Click to collapse
I've already tried that one but odin is stuck at data.img.
tornado92 said:
when u go to download mode, does it show your model number??
Click to expand...
Click to collapse
Yes it shows the product name.
Basseytje said:
I've already tried that one but odin is stuck at data.img.
Yes it shows the product name.
Click to expand...
Click to collapse
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
tornado92 said:
then you can fix it by flashing i guess .. try different versions of odin/try different usb ports/ different usb cables/ different pc/ :fingers-crossed:
Click to expand...
Click to collapse
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Basseytje said:
i've tried several cables, 2 pc's, one laptop, all the ports, all the versions of odin, 6 different roms
Click to expand...
Click to collapse
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
tornado92 said:
it could be problem with your internal memory then... can u post a photo of your download mode.. what errors you get when u do a factory reset using recovery??? also when your phone is bricked dont try to unbrick using a custom rom or kernals because it can cause drawbacks like corrupting efs and all.. always try to unbrick using a stock firmwares.. also dont use pit immediately .. keep it for the last try...
also make sure kies and other tools are not running on backgroup ,, unistall them and reinstall samsung drivers and try again..
Click to expand...
Click to collapse
kies won't recognize the phone. the only 3 screens i can access are showed in the pics below. i've got 2 stock roms which don't work. after i tried kies, i immediately uninstalled it and left the drivers on the pc.
i40.tinypic.com/29gkdi1.jpg
i40.tinypic.com/qsnluc.jpg
i41.tinypic.com/2aep3yx.jpg
can't post any files yet.
I hope there is still someone who can help me...
odin is still stuck on data.img
If you say you've 'tried everything' (which everyone always says), then it's a service centre job. What else do you want anyone here to say ? No miracle fixes. If it were me I'd keep trying, it's almost always something really simple/small/obvious that's causing the flash not to work, and as we're not there looking over your shoulder at what you're doing, it's going to be almost impossible for anyone to say what that is (you have 'tried everything' after all).
is there a way to fix this with jtag?
Basseytje said:
is there a way to fix this with jtag?
Click to expand...
Click to collapse
Maybe. No one can say for sure mate. If you motherboard is really borked, it would have to be replaced nevertheless.
Remember that Jtagging leaves marks on your device, so you can kiss goodbye any warranty u might have.
"To err is human, to forgive is divine."
Sent from my SGS II
hey.. i had this problem too.. the only solution that i had is to use the galaxy note pit file and a stock rom for i9100 ... then the phone went back to normal ..but the memory went from 16 tb to 11.5 gb .. it was the only thing that made my phone work again..
i installed pit from galaxy note ..with and original stock firmware 4.1,2 then after install I did a factory reset via stock cwm and a clear cache ..and it worked.. a few bootloops and it went on:|
alexandru.j91 said:
hey.. i had this problem too..
Click to expand...
Click to collapse
You got so ridiculously lucky that I can't comprehend that it worked. Please don't advise others to do the same, I'd say what you did is normally a recipe for a hard brick. Don't flash files for other phones, let alone a pit file for another phone. Yes I know the note has the same hardware as i9100 but you know what? It's not an i9100.
Edit: Look at what you posted in your other thread:
alexandru.j91 said:
I hardbricked my phone about 3 months ago with the original firmware from orange 4.0.4 and I resolved the problem by putting samsung note PIT file ..but I don't have acces to all the memory on my phone ..I have almosst 12 gb from 16.. and my phone is getting wired ..and it is shutting off randomly since then .and to get it on again i have to remove the battery ..
Does anybody know how to get all my memory back for my phone? tx
Click to expand...
Click to collapse
I'd say that's a reason not to flash files from another phone.
i was just telling him that i had the same problem..not to do the same thing..because of the problem that I have got! i have told in my other post whathappened to my phone! and i know that my problem can be solved by rewriting the memorybut i don't know how!..
---------- Post added at 06:04 AM ---------- Previous post was at 05:05 AM ----------
what I did.. i did because of some threads on xda ..so I am not crazy ..I just told him what I have did.. I haven't advised him to do that ..because of the problem that i had .. and when I wrote what I have did to make my phone worked .. i hace told the fact that it shrinked my memory from my phone..
maybe i'm getting a little progress. when i try to flash a new bootloader. i see a progress bar on the phone. but odin is halfway stuck at sbl.bin
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> Sbl.bin
everywhere i read, people are saying use different cables. i already tried the samsung s2 cable, a htc desire cable, 3 deal extreme cables and an other htc(dont remember the model) cable. but i'm getting the same problems. stuck at zimage or something else...
anyone?