I have read all the posts and have tried everything but ODIN will not load the 2.2 firmware upgrade.
I have changed USB cables, ports etc etc and nothing works.
I have the phone in Download mode and ODIN sees in on COM5 but then gives me this and just hangs there:
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005>
<OSM> All threads completed. (succeed 0 / failed 1)
My advice to all is DO NOT USE THIS UPDATE.
I have to say guys i am a little ticked off at this. After following all the directions the experts gave, it just doesnt work.
I'm sure it will work for some but i'm willing to bet this upgrade is a failed experiment for most users.
shane.kelly55 said:
I have read all the posts and have tried everything but ODIN will not load the 2.2 firmware upgrade.
I have changed USB cables, ports etc etc and nothing works.
I have the phone in Download mode and ODIN sees in on COM5 but then gives me this and just hangs there:
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005>
<OSM> All threads completed. (succeed 0 / failed 1)
My advice to all is DO NOT USE THIS UPDATE.
I have to say guys i am a little ticked off at this. After following all the directions the experts gave, it just doesnt work.
I'm sure it will work for some but i'm willing to bet this upgrade is a failed experiment for most users.
Click to expand...
Click to collapse
i am going to go out on a limb here and say:
IT'S BETA!!!!!!
it has actually worked for LOTS of people that use it. have you bothered to ask to get some help?
do you have a previous rom on or voodoo/oclf lagfix mod?
what do you have done to your phone?
again, this leaked firmware is BETA, and according to the number of posts, there are hundreds, maybe thousands, running it. this isnt a samsung/att official rom, so you are warned that it is BETA/NOT OFFICIAL and you can cause harm to your phone if you screw up the process.
my suggestion is use the one click jf6 to go back to stock and try again....
please dont post FUD like this.
Are you sure your in download mode or just recovery..
When that was happening to me(the hang at file analysis), i was in recovery mode.
Like Pirateghost said, don't go about blaming everything on the programs/phones/developers...
usually its small details that you may be missing, trust me I spent a good hour or so failing before I finally flashed lol
shane.kelly55 said:
I have read all the posts and have tried everything but ODIN will not load the 2.2 firmware upgrade.
I have changed USB cables, ports etc etc and nothing works.
I have the phone in Download mode and ODIN sees in on COM5 but then gives me this and just hangs there:
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005>
<OSM> All threads completed. (succeed 0 / failed 1)
My advice to all is DO NOT USE THIS UPDATE.
I have to say guys i am a little ticked off at this. After following all the directions the experts gave, it just doesnt work.
I'm sure it will work for some but i'm willing to bet this upgrade is a failed experiment for most users.
Click to expand...
Click to collapse
Plus, thats prob not helping you man.
Dino. said:
Plus, thats prob not helping you man.
Click to expand...
Click to collapse
I agree, I am one of those user, I had no problem with this Froyo update. Don't blame the developers like it was mentioned this worked for the majority of users. What did you have running on your phone before flashing? Do you know the difference between recovery and download? I find that usually when something fails a step somewhere was missed. We all have it happen, I've made mistakes, soft bricked my phone at least 4 times in 2 days playing with Framework-res.apk. Odin always works for me.
Don't tell others not to use something because you couldn't get it to work without giving sufficient details of previous mods to your phone. Odin dosen't like the Voodoo Lagix and if it wasn't disabled that is what could be causing the problem, if you were previously using one.
It's a failed experiment when users don't follow instructions well and claim they do. eventually we learn that they did something wrong. Don't blame developers, it isn't their fault, everyone knows you do this a t your own risk, don't be pissed at the people developing tools to make your phone better. Everyone claims they read and they don't read everything and then things like this happen.
You need to flash back to stock with Odin3 one click with the stock JF6 preinstalled and let it run, disable any lagfixes first. After you are back to stock then you use the Odin preloaded with the Froyo beta.
Sounds like you are missing a step. Relax and read a little more about what you are doing before doing it and try again, sometimes it takes a few times to get it right.
shane.kelly55 said:
I have read all the posts and have tried everything but ODIN will not load the 2.2 firmware upgrade.
I have changed USB cables, ports etc etc and nothing works.
I have the phone in Download mode and ODIN sees in on COM5 but then gives me this and just hangs there:
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005>
<OSM> All threads completed. (succeed 0 / failed 1)
My advice to all is DO NOT USE THIS UPDATE.
I have to say guys i am a little ticked off at this. After following all the directions the experts gave, it just doesnt work.
I'm sure it will work for some but i'm willing to bet this upgrade is a failed experiment for most users.
Click to expand...
Click to collapse
Take out your battery, close Odin, and then replace your battery. Next, start Odin up, then hold down the vol +- (holding it in the middle of the volume rocker will achieve this). Make sure your USB cable is plugged in to your PC and then plug it in to the phone while you have the vol +- rocker held in. That should put you in download mode and the update should work then.
You are using the original, onc click package, right?
Is PEBKAC appropriate here?
I'd say a large majority got it to work by the threads I have read here and elsewhere. Take a DEEP breath, walk away for a day or two and give it another shot.
Years ago when I began tweaking my mobiles, I had issues, and I can a
honestly say that it was PEBKAC at the time.
I had what I think maty have been the same issue...Yes I am a newb. But from what I remember when I was doing the Odin3 it was connected on COM4 not COM5. At one point I did have COM5 but that is when I was having issues. I could be wrong but that is what I remember. MAKE SURE you have the UPDATE.ZIP file in the RIGHT SD Card which is the INTERNAL. I first had mine in the EXTERNAL and it gave me issues. Try it again once you relax a bit. I KNOW how you feel, I tried one night and epically failed and got frustrated. I tried the next day, figured out what I was doing wrong. Followed the directions and it worked. good Luck. And as far as being a BETA, I do not care cause after 2.2 and rooting this thing IS SMOKING fast and I have NO complaints.
No, no it doesn't work. That's why I had to flash back to JH7 after having successfully flashed the 2.2 leak.
Wait for it.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
My friend's Infuse just bricked for flashing some wrong ROM maybe. I told him to flash the stock ROM with odin. The flashing process just can passed successfully but the device stucked at the first screen (SAMSUNG logo). UCKD5 stock stucked normally, and UCKE3 stock will stucked with a little rainbow.
He checked odin at this status:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and passed the flashing:
When the device is power off, he plug the data cable, the screen just show the very frist screen (a cricle) but no battery comes up.
Is his Infuse became a real brick? Any other thing he can do?
knightxmu said:
My friend's Infuse just bricked for flashing some wrong ROM maybe. I told him to flash the stock ROM with odin. The flashing process just can passed successfully but the device stucked at the first screen (SAMSUNG logo). UCKD5 stock stucked normally, and UCKE3 stock will stucked with a little rainbow.
He checked odin at this status:
and passed the flashing:
When the device is power off, he plug the data cable, the screen just show the very frist screen (a cricle) but no battery comes up.
Is his Infuse became a real brick? Any other thing he can do?
Click to expand...
Click to collapse
Did you try these instructions and files?
http://forum.xda-developers.com/showthread.php?t=1116251
Sent from my SGH-I997 using xda premium
nelomen said:
Did you try these instructions and files?
http://forum.xda-developers.com/showthread.php?t=1116251
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
yes, but stucked too! it's the UCKD5 stock ROM.
re: unbrick
knightxmu said:
My friend's Infuse just bricked for flashing some wrong ROM maybe. I told him to flash the stock ROM with odin. The flashing process just can passed successfully but the device stucked at the first screen (SAMSUNG logo). UCKD5 stock stucked normally, and UCKE3 stock will stucked with a little rainbow.
He checked odin at this status:
and passed the flashing:
When the device is power off, he plug the data cable, the screen just show the very frist screen (a cricle) but no battery comes up.
Is his Infuse became a real brick? Any other thing he can do?
Click to expand...
Click to collapse
No wonder it did not work. He did not flash using the Ultimate Unbrick found here with step by step instructions:
http://forum.xda-developers.com/showthread.php?t=1116251
The filenames are all wrong in PIT/PDA/PHONE ........
Also the phone is NOT bricked at all.
Just need to remove battery, replace battery then go into download mode, Load Odin
with the correct files and while pressing both volume buttons plug usb cable into phone.
Then when com: lights up yellow with a number in it click START in odin window and
wait til the phone reboots into stock Froyo.
Misterjunky said:
No wonder it did not work. He did not flash using the Ultimate Unbrick found here with step by step instructions:
http://forum.xda-developers.com/showthread.php?t=1116251
The filenames are all wrong in PIT/PDA/PHONE ........
Also the phone is NOT bricked at all.
Just need to remove battery, replace battery then go into download mode, Load Odin
with the correct files and while pressing both volume buttons plug usb cable into phone.
Then when com: lights up yellow with a number in it click START in odin window and
wait til the phone reboots into stock Froyo.
Click to expand...
Click to collapse
it have been done, but not work!
my picture show another stock ROM, that is UCKE3. the UCKD5 stock ROM you mentioned have been tested! all the 3 files were loaded and the Re-Partition was checked, and flash it step by step 3 or 5 times.
i'm not a noob, i used to flash the stock ROM to unbrick my phone many times, but, i have no ideal with his device.....
help is needed!
I'm having the exact same issue
knightxmu said:
it have been done, but not work!
my picture show another stock ROM, that is UCKE3. the UCKD5 stock ROM you mentioned have been tested! all the 3 files were loaded and the Re-Partition was checked, and flash it step by step 3 or 5 times.
i'm not a noob, i used to flash the stock ROM to unbrick my phone many times, but, i have no ideal with his device.....
Click to expand...
Click to collapse
ive tried multiple methods found here and from google and androidcentral.com
<ID:0/005> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCKD5.tar.md5 is valid.
<OSM> PHONE_UCKD5.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> factoryfs.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> cache.rfs
<ID:0/005> param.lfs
<ID:0/005> zImage
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
sigh similar problems
MisterJunky is correct.
You have the wrong files loaded into Odin.
I am a noob but If it were me, here is a list of steps that I would try, one at a time, until I have tried everything. Yes, I know ODIN says passed, but try each step anyway. One step at a time, try ODIN and see if it works.
1. Make sure your Anti-virus is disabled and start ODIN as Admin(win7)
2. If you are running Win7, start ODIN with XP SP2 compatabilty. ( I don't need to do this but I have read of others doing this to make it work)
3. Make sure Win7 has no other programs running and leave the computer alone while it is downloading to the phone.
4. Remove all other USB devices connected to your computer (except keyboard and mouse) and change the USB port you have the phone plugged in to. No extended cables. Direct to the motherboard no USB hubs or through a USB connection on another device (this was one of my problems)
5. Boot CWM recovery (red) and format everything; boot, system, data, cache, sdcard and wipe Dalvik cache and battery stats. Pull out you SD card and format it with windows (not a quick format but a full format. Depending on the size coule take 15-20 minutes).
6. Delete all ROM files and ODIN files and download everything again. (constant problem when I had a HTC Inspire) Boot CWM and wipe everything again.
6. Uninstall all Samsung drivers, clean you registry, reboot, download current Samsung drivers. boot CWM and wipe everything again.
7. Scream, boot cwm and wipe everything again
Good Luck,
6
knightxmu said:
My friend's Infuse just bricked for flashing some wrong ROM maybe. I told him to flash the stock ROM with odin. The flashing process just can passed successfully but the device stucked at the first screen (SAMSUNG logo). UCKD5 stock stucked normally, and UCKE3 stock will stucked with a little rainbow.
He checked odin at this status:
and passed the flashing:
When the device is power off, he plug the data cable, the screen just show the very frist screen (a cricle) but no battery comes up.
Is his Infuse became a real brick? Any other thing he can do?
Click to expand...
Click to collapse
Rainbow???? Does your friend have a Rogers Infuse?
If his is from Rogers and not AT&T, you need the Rogers Gingerbread UXKG3 unbrick. It tends to get buried deep down in the forums since there are far more AT&T users than Rogers users.
Sigh, so i'm back again, 2nd time messing up my phone in 3 weeks......This time its going to cost me if I don't get an answer. I bricked my phone, i tried everything, and I mean everything, and it just won't finish flashing via Odin "pc" and I can't my mac to find the Pit files because of Stupid Kies.
Anyway, what did I do again? well i flashed the abyss kernel and then immediately via CWM tried to restore my Criskelo ROM and it would not get past the boot up screen, "the one before the animation" ....i wiped cache, tried restoring my stock Rom, tried wiping dalvick cache, you name it. None of that work, the only thing i could get into at the time was CWM and Odin mode "download mode".....I continued to try to figure it out for my self, and tried repeatedly to flash via odin.....back to a stock rom and i screwed up so much more now because of that. I can't get into clockworkmod anymore....i can't get into recovery, NONE OF THAT ....Only thing i see when i put on my phone is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." ...I can get into Odin mode, but NOTHING ELSE. PLEASE SOMEONE HELPPPPP ME!. I don't know what I am going to do if i don't back my phone.
btw, if you wanted to know how far I got in the whole flashing via Odin.
It is showing this:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N7000XXLPY_N7000OXXLPT_N7000ATOLP2_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
cache.img
NAND Write Start!!
factoryfs.img
"then it gets stuck and doesn't go beyond it....turn oof the phone and then i see this"
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1):crying::crying:
You are the victim of the eMMC bug. Welcome.to the club...
If your SGN is still under warranty and your binary counter is zero, rush to your nearest samsung service center. Tell them the phone booted after the update and never started.
If you arent in warranty, try repartitioning method explained by Forest in his detailed guide @ http://forum.xda-developers.com/showthread.php?t=1661590 check the 12th post.
After trying unsuccessfully for 6hrs to unlock and root my new S3, i finally found this thread. i just got this phone in the mail from my insurance plan. I had just unlocked and unrooted without any problem on the last phone i got a few months ago. i have no idea what version this phone was on before i tried flashing and i can't see now either but after seeing that thread I'm suspecting vrucml1. whenever i press the power button i get a "Firmware upgrade encountered an issue. Please use Software Repair assistant and try again."
As i was trying to flash images odin kept getting hung up at
Code:
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also, i am able to get into a stock recovery. don't know if that makes a difference or not.
After reading that discussion i linked, i'm afraid i may have bricked my phone bc i can't seem to even get it to boot past the error screen. If this thing is bricked, I'm seriously switching carriers. Can somebody help?
What is the advantages with this Odin flashable file containing only the lollipop bootloader and modem?
- It means you can flash it in ODIN, without having to wipe your beloved custom ROM or Recovery to get the Lollipop Bootloader and Modem
The firmware I extracted the modem and bootloader from is the Polish XEO version.
Info from Sammobile.com:
Model SM-N9005
Model name GALAXY Note 3 LTE
Country Poland
Version Android 5.0
Changelist 3643614
Build date Wed, 25 Feb 2015 12:57:23 +0000
Product code XEO
PDA N9005XXUGBOB6
CSC N9005XEOGBOA4
Please follow these steps if you would like to flash:
1. Completely turn of your phone, usb cable must me disconnected.
2. After the phone is turned off, remove the battery for 5 seconds
3. Put the battery back in and boot directly in to download mode (vol down + home + power) then press vol up 1 time to enter download mode.
4. Open ODIN on your PC and put the downloaded file in the AP section (Odin v3.09)
5. Now connect your phone to the pc via USB
6. When you can se that the phone is connected to Odin, press start and just let Odin do its thing.
7. Check on your phone if the bootloader and modem has updated. I use an app called Phone Info Samsung from the play store.
8. Profit
When I did the flash as described above everything went perfect.
I have read that some people haveing issues getting the modem to stick, if that happens:
1. Untic auto-reboot in ODIN before you flash.
2. When the flash is finished in ODIN force a new direct reboot in to download mode (vol down + home + power)
3. Then tick back the auto-reboot tab, flash the file one more time and let the phone autoreboot. Hopfully the modem will have sticked.
Please flash at your own risk, I take no responsebility for bricked devices etc.
Download link: http://www.filedropper.com/hltelollipopbootloadermodemtar
What is the point exactly to flash only the bootloader? I can't find it using the search function, sorry for asking
mantiyeah said:
What is the point exactly to flash only the bootloader? I can't find it using the search function, sorry for asking
Click to expand...
Click to collapse
The point is, if you are on a custom ROM.
You can flash this file and get the latest lollipop bootloader and modem without installing the full stock firmware and wipe your ROM.
Why?
Because some lollipop based custom kernels and roms needs the lollipop bootloader and modem to function properly.
One example is arter97 great custom kernel v5 and up needs lollipop bootloader and modem to work.
Hope it helps
But the bootloader makes other problems. Recovery have bugs with this.
Schrotty35 said:
But the bootloader makes other problems. Recovery have bugs with this.
Click to expand...
Click to collapse
Can you please enlighten me what type of bugs?
Im asking because I am curious since my recovery seems to work very well on lollipop bootloader.
Im using philz_touch_6.48.4
Thanks in advance
Whene you format cache or data/media this is very very slow. With kitkat is very fast. Whene you install a asop rom and will install later a custom stock rom this not work and many other problems but with twrp there is the same problems too. Only wipe is on twrp faster.
Schrotty35 said:
Whene you format cache or data/media this is very very slow. With kitkat is very fast. Whene you install a asop rom and will install later a custom stock rom this not work and many other problems but with twrp there is the same problems too. Only wipe is on twrp faster.
Click to expand...
Click to collapse
I just formatet cache and it went just as fast now as it used to go with KitKat bootloader.
I also installed Temasek CM12 Unofficial v8.9 and that went fast too.
I even booted in and out of recovery from CM boot menu and also enterd in to recovery from a "cold" boot to se if there were any issues getting in to the recovery.
No issues what so ever. I made a nandroid backup just to have tried that too, also worked like a charm.
Cant say Im having your issues with the lollipop bootloader. For me everything works the way it should do.
I hope you get the Lollipop bootloader to work for you in the future
Nice to see you have posted bootloader and modem. Unfortunately found it out after I have downloaded full original LP, installed it, softbricked my phone, recovered from that, wiped out everything, installed Temasek's ROM, restored applications so finally ready to install Arter's kernel You can imagine how much time it took instead of option you have provided
Kuratko said:
Nice to see you have posted bootloader and modem. Unfortunately found it out after I have downloaded full original LP, installed it, softbricked my phone, recovered from that, wiped out everything, installed Temasek's ROM, restored applications so finally ready to install Arter's kernel You can imagine how much time it took instead of option you have provided
Click to expand...
Click to collapse
Yes I can imagine
Thats why I desided to post it, so maby I could save some people from the hassle you went through
But I`ll guess Arter97`s kernel was worth the hassle anyway, just an amazing kernel for the Note 3
just ask can i update lollipop bl & m over my custom rom super fast v8.0 4.4.2 & it will work without any prob ?
Hi iketil
I just used your file to flash latest bootloader and modem to my N9005 and it worked perfectly
No need for me to flash a second time to make the bootloader stick.
I did have an older version of CWM which went into boot loop when I tried to enter recovery, but flashing the latest TWRP fixed that.
Thanks for taking the time to make this, saved me a bunch of time :good:
There is no persist file but this need it to.
how big is this file supposed to be? the filehost keeps cutting me off during the download and it fails the MD5 checkes.
---------- Post added at 08:12 AM ---------- Previous post was at 08:05 AM ----------
6. When you can se that the phone is connected to Odin, press start and just let Odin do its thing.
Click to expand...
Click to collapse
At which stage should i consider that Odin has done its thing? Below is the log of the flashing thus far, but the phone is still on the screen with "Samsung GALAXY Note3 SM-9005" logo after 10 mins.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> hlte_lollipop_bootloader_modem.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> hlte_lollipop_bootloader_modem.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> hlte_lollipop_bootloader_modem.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Added!!
Click to expand...
Click to collapse
cojak72 said:
just ask can i update lollipop bl & m over my custom rom super fast v8.0 4.4.2 & it will work without any prob ?
Click to expand...
Click to collapse
Thats what I did on Temasek CM12 Unofficial ROM.
I had no problems at all. But I cant give you any insurance that you wont have any.
Just follow the instructions carefully and it should work if you have the sm-n9005 (hlte).
3XTR3M1ST said:
how big is this file supposed to be? the filehost keeps cutting me off during the download and it fails the MD5 checkes.
---------- Post added at 08:12 AM ---------- Previous post was at 08:05 AM ----------
At which stage should i consider that Odin has done its thing? Below is the log of the flashing thus far, but the phone is still on the screen with "Samsung GALAXY Note3 SM-9005" logo after 10 mins.
Click to expand...
Click to collapse
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I keep getting a file thats 56.6MB everytime I download the file. Is this safe to flash. Odin passes the md5 check...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3XTR3M1ST said:
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse
Sorry to see you are having problems with your phone :\
I have read your thread and as others have suggested, flashing the official samsung firmware downloaded from sammobile.com would be the way to go.
Seems like your phone is in a bad state, really hope that you have not recievd a fake\clone
And my file does not include the recovery, but if you flash the original samsung firmware it should bring back the original recovery and restore your phone to a working condition.
Hope you mange to fix it Good luck!
shiverz07 said:
I keep getting a file thats 56.6MB everytime I download the file. Is this safe to flash. Odin passes the md5 check...
View attachment 3223697
Click to expand...
Click to collapse
If you check the size of the file you downloaded in windows file manager it should be 58 041 KB (thats what mine is)
I put the 58 041 KB big file in my ODIN just to check and mine ODIN says the binary size is 56,7, that is the same number your ODIN shows in the picture
I think you can flash safely, if the file is corrupted it simply should not pass the md5 check
iketil said:
If you check the size of the file you downloaded in windows file manager it should be 58 041 KB (thats what mine is)
I put the 58 041 KB big file in my ODIN just to check and mine ODIN says the binary size is 56,7, that is the same number your ODIN shows in the picture
I think you can flash safely, if the file is corrupted it simply should not pass the md5 check
Click to expand...
Click to collapse
I just flashed it and it worked. Thanks a million man. You saved me a ton of time, effort and data. :good:
I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!
mryanmarkryan said:
I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!
Click to expand...
Click to collapse
If you can't even mount it on Windows or get into recovery that's not good.
True Dat!
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?
mryanmarkryan said:
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?
Click to expand...
Click to collapse
I would suggest pushing the root kernel to it anyway just to see if it will go.. I do have an FRPbypass but it's an apk meaning you need to install it and if you cannot mount to push it and then try to do adb shell pm install FRPbypass.apk then there's no point in that either.. Can you even get into download mode? If not the last thing I could suggest is the PIT file to repartition it. Unless someone else has a better idea? I do have the PIT file for odin too.
Also I think you're past the point of losing your data and if you can hold the volume down button and power button at the same time until it shuts off and turns back on again you can select factory reset and that's going to ruin all data..
My god, this happened to me on my first Note 5 I had. I was trying to restore it to stock before selling it and like an asshole I forgot to check for "OEM Unlock" and ran into that exact message. It put the fear of god into me. Like you I didn't have the serial number written down and I couldn't get it from anywhere. T-Mobile tech reps tried to tell me the IMEI number acts as a serial number, cool, that doesn't help me. I gave up on Kies and just played around with Odin after I was FINALLY able to find a stock firmware. I can't believe how difficult that was to get. I managed to flash the stock firmware thru Odin and I got the phone back! Stock as it came out the box.
I can't remember how I was able to get it into download mode but whatever button order I kept trying I finally did because Odin recognized the mofo and I flashed that stock firmware as fast as I could. It rebooted and I saw that beautiful stock welcome screen once more. Try to do this, I didn't need to do anything else.
For this reason I now keep a copy of stock firmware along with screen shot of my phone's status screen showing the serial number and everything else. All that's backed up to one of my external drives. Alone with several nandroid backups of various stages of owning this second Note 5 I have now. I'm running V10 of Darthstalker but I haven't heard of other users running into FRP lock. That would mean something tripped their OEM unlock option but how would that happen without you doing it? Is there something inside the ROM (a bug) that's tripping the option in Developer Options?
Best of luck with this, I know how stressful this can be. As far as getting your data back, yeah that's likely a no go. At this point you should be hopeful of getting a working phone back, let alone recover any personal data. Hope you can sort this.
More Info
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Yeah if you can get it into download mode and you've got the stock firmware you should be good to go and flash tru Odin. That's key. If I were you I'd be like, "To hell with my personal data! Get me a working phone back!".
Good luck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!
MrMike2182 said:
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!
Click to expand...
Click to collapse
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
Try downloading the newest odin version sometimes that can help.. Can you tell me how it's failing? Like what exactly happens when you try to do all the flashing? Did you try the adb commands that I suggested? You only need to install minimal adb and Fastboot on the windows pc and then connect your device and then open a terminal in the same exact folder where adb and Fastboot were installed and then type Fastboot devices or adb devices if it give you a bunch of numbers it means that it can see the device and we can then manually push and install the firmware. The other thing I suggest you try to do is flash the Lollipop 5.1 T-mobile firmware because I think it doesn't have frp on it yet and before flashing it go into the actual firmware you downloaded and delete cm.bin then rezip the firmware again and flash that one without the cm.bin but first try flashing the entire firmware as is with the md5 and all before resorting to deleting cm.bin.. Don't try flashing the Marshmallow 6 rom because that's where they started that frp bullcrap if you ask me. FRP stands for Factory Reset Protection... I understand the need for it and it's importance but Google could have been a lot more open about it and explaining to its customers what it's for and what it does not just do it and let most of us learn the hard way!!
When you try to flash in Odin tell me what file it fails on.
If none of this works this page is your last bet buddy
https://www.sammobile.com/forum/showthread.php?t=31136
I'm working on it now! Give you guys a summary of what happened as I as check off your suggestions..
SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol
Progress!
mryanmarkryan said:
SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol
Click to expand...
Click to collapse
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Advice?
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
mryanmarkryan said:
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.
mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
It stopped right while trying to flash the recovery part of it so here's what I suggest you try to do.. unzip the 5.1.1 firmware you downloaded and unzip it again until you can see all the files in it and then manually flash them 1 by 1 in the AP slot but don't allow the phone to auto reboot uncheck that option and after 1 files flashed hold the volume down button and power button until you can select shut down device or turn off whichever then again hold the buttons to get into download mode again and continue until they are all flashed and then finally again hold the volume down button and power button and when it comes back on then select factory reset.
---------- Post added at 08:31 PM ---------- Previous post was at 08:28 PM ----------
E-POUND said:
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.
Click to expand...
Click to collapse
If he flashes the latest firmware with the security updates he can never go back to 5.1.1 so I don't suggest he do that yet
Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?
mryanmarkryan said:
Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?
Click to expand...
Click to collapse
You're not rooted at all right now but you should not have needed to turn the imgs back into md5s again you should have just flashed them the way they were they don't need md5 just to flash. Try holding the volume down button and power button until it shuts off and turns back on again then select factory reset if that doesn't work then go into download mode again and connect to a Windows pc and use Smart Switch to try and fix it.
The reason I converted them was because Odin wouldn't find the files.. I tried just running them by typing a *.img but it didn't work. I'll go read about smart switch.. I"m learning stuff here
Update,: On a hunch I went back and ran the firmware install again, but just in it's original format. It succeeded and I'm setting up the phone now.. Thanks for your help MrMike. I appreciate you putting the time in..
mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
You are using the wrong stock firmware. Download the DPG1 firmware since that is was darthstalker v.11 is on. If you backed up your ROM then you don't have any troubles at all. Just ODIN back to stock, root, twrp recovery data only and done. But not all at once. First get the firmware going and reboot your phone. Once you know it's working the try rooting. Once you are rooted download TWRP and recover your data only.
Btw - FRP is when you log into your google account in the beginning of the setup so don't do that if you want to flash other ROMs.
P.S. I'be been running Darthstalker v.11 since it came out with no problems.