Database Users

How do i Soft-brick my I9000

Sounds a wierd thing to ask I know, but ill explain (briefly)..
I bought my Preowned SGS (OS 233) about 4 months ago, which powered down occasionally and was a bit slow.. so I flashed the ROMS successfully upto 235 JVT using ODIN 1.82 and Stock Roms.. no addons or customs.
But now its started locking up, crashing and powering down again.. Ive gone back to 233 & 234, hard and soft resets, checked SD cards, the lot.. but nothing helps.
I took it into the shop with reciept and box, as its faulting up.. even left it overnight with them twice now, but they keep saying theres nothing wrong with it and it runs fine, but it doesnt. Ive emailed the company CEX UK, they dont have a phone number.. but they havent emailed me back.
The shop.. the staff are all 19year old iPhone users.. say they can only change it if THEY find a fault, they wont even give me a replacment SGS.
Im really annoyed.. yes the phone DOES work but intermittently locks and resets. All im looking for is a soft/screen lockup or Anything, long enough to get out of the shop with a replaced SGS.
This is clearly why it was traded in the first place, whoever had it first, was smart enough to see that.
Can anyone PLEASE help.
Night

If it's running fine now : remove some system or framework files and see it bootloop.
They give you a replacement straight away when they see you have a problem ? Nice policy if you don't count the staff.
Just realized you needed a stock option, that's harder. Unplugging it during a system flash will do it I suppose.

Once i soft bricked my sgs by doing this:
Installed cyanogen mod 7 , wiped data,cache ,etc. then did a backup of darky rom (i'm sure any samsung firmware works) and voila ,it's soft bricked. Doesn't fully boot up, recovery is giving errors, but it's ok with download mode.
You can fix it by flashing samsungs firmfare with odin.
Sent from my GT-I9000 using xda premium

Thanks for the support folks, at last someone understands what i mean.. You'd think I was asking for a hip replacment.
Ill try removing some system core files, will I need to root it first or can i do it through USB or file browser...thanks Bubble-be. Ill leave the flashing for now Martis.
Night

Flash a firmware and in the middle of flashing,yank the usb cable out of you sgs.....do this when it flashes kernel and you got a brick for shure
Sent from my GT-P1000 using Tapatalk

easy, u installed XXJVT through Odin right, so just do the same thing and just pull the wire out whilsts its doing it XD, this WILL brick your phone (soft-brick)

[Q] Defy near death or worse. Please help!

Hi guys, you are my last hope!
Bought my Defy early 2011 and regularily updated with custom ROMs, so you could say I know a thing about rooting, RSD Lite, fixed sbfs, ...
Or at least I though I knew, but I still managed to kill my phone I think.
Here's what happend:
I tried to install Epsylon3s nightly from may 8th (http://defy.wdscript.fr/defy-cm9/). Before that, I was on CM 7.1
After installing the zip and rebooting, I saw the bootlogo, then i was asked for my pin code. As soon as i entered it, again to the bootlogo, again the pin, and so on.
So i realized something was wrong.
Could not get into recovery, so I flashed
JORDN_U3_97.21.51.sbf
as this often helped me in the past.
I then tried this one:
http://forum.xda-developers.com/showthread.php?t=1498843
Also didn't start.
So back to
JORDN_U3_97.21.51.sbf
But here it might be, that I misclicked (I have quite some SBFs in that folder, cause I wanted to be prepared in case something went wrong), as after that, I never got my Defy to work again.
I was stuck at the Motorola M logo.
Coudln't get into recovery, so no zips for me anymore, only flashing of sfb.
That's basically when I entered panic mode. As I didn't know what I just flashed, I could only guess the problem. So I tried the Ginger2Froyo (http://forum.xda-developers.com/showthread.php?t=1486731) in case I went to BL6. Also tried http://forum.xda-developers.com/showthread.php?t=1552152
But in this process, my RSD Lite started to behave strange:
when flashing, it's building the image, uploads it, checks checksum. But once it says "rebooting" it immediately jumps to 100% and pass. Phone how ever stays black and white LED.
Of course I can still flash other SBFs, and I tried various (JRDNEM_U3_3.4.3-36-1.7. sbf for example). But I either get the instant PASS, which tells me something didn't work, or sometimes I get the neverending bootlogo and RSD telling me to start the phone manually.
So... that's my story.
I can't seem to find a single SBF that would work for me. I screwed up big time.
To make this clear: at this point I don't care about downgradeability or anything thelike. Whatever makes my Defy work again, is fine. Froyo, Ginger, ICS, or whatever.
So if anybody still has any advice for me, I'll love you forever! Promise!
Thanks a lot in advance for any help you sure will offer,
Clock

Try this if you haven't :
Go into stock recovery and make a factory reset
Sent from my MB526 using XDA App

As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.

Have u tried this thread:
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade

Clock1999 said:
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Click to expand...
Click to collapse
Im sorry , thought you mean custom recovery when you say you can't enter recovery.
I was in the nearly same situation but i never changed my bootloader...., by me out works to power up my phone with pressed volume button down to enter stock recovery ...
So I'm sorry i couldn't help you
Sent from my MB526 using XDA App

You just like to play with your defy, don't ya
Have you tried the suggestions under Common problems/questions in this guide?

Thanks for all the responses.
However all the guides seem to point to two options only:
1) Flash this one Eclair (which I already mentioned that I did, that it used to work, but since the "instant 100% on rebooting" doesn't anymore.
2) Factory Reset/Wipe. Which I cannot, as I don't get into Recovery Mode. All I can do atm, is flash SBFs. Defy won't enter Recovery Mode (which I guess is a pretty bad sign)
But the way I always understood it, was that you only need to be careful what you install, so you don't lose downgradeability. And that, once lost, you wouldn't be able to flash "older" roms, but newer ones would always be possible.
So shouldn't there always be a rom, that saves me?
What about Defy+ roms? Any advice on that? Which best to try first? So far, I haven't touched Defy+ roms at all.
Thanks for the support!

Did you try this:
When Off, press Vol. down and power.
You'll get an exclamation mark inside a triangle.
Press both Vol. up and down at the same time.
Now you suppose to be in stock recovery and you can do factory reset.
Do the above after flashing stock SBF.

Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock

If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2

Clock1999 said:
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
Click to expand...
Click to collapse
If you flash any of the defy+ roms, camera won't work..there isn't a fix or patch for that..
Doesn't matter from where I send it, what matters is written above

corrinti said:
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Click to expand...
Click to collapse
Hi,
as I mentioned above, I already tried this ROM but it gives me the same result as all the others: stuck at bootlogo.
Maybe there is a special trick on which ROM I should flash before flashing this one?

Sorry, I do not know how to help. Just no idea now, try to dig the forum.
Once I had very similar problem - whatever I flashed I was stuck at bootlogo. And in my case I found out that just before flash my internal memory had been filled with some mess, which was not removed by any wipes (cache, dalvik cache, cache partition) and after any flash memory was too filled to start the system.
But finally I could flash Chinese eclair (CG5), which at last started horribly laggy, and I could wipe private data from a system - it gave me more than 1GB of internal memory back (from 40MB after all wipes and clean system install) and a way to flash whatever I wanted without a problem.
So even if it is also your problem, my way is not available to you now. Maybe you can find as small sbf file as possible and try then.

I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!

Clock1999 said:
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Click to expand...
Click to collapse
I could use CG5 full sbf which will not boot for you as you put BL6 and maybe BL7.
To boot from flashed sbf it cannot be lower BL version.
I suppose that now you have a memory problem - flashing sbf do not wipe the memory.
At first I would try getting into stock recovery (even several times, just pull battery out, wait a minute, power, vol -, battery in) - if successful then do a factory reset and reboot.
If not I would try to find out a smallest sbf with proper BL version - just to give it more chance to boot with small memory available, if not then again try to get into stock recovery.

I'm the happiest guy around, as I finally revitalized my Defy.
For all you guys, who already tried everything: here's what worked for me.
Just let it rest a few days.
After I hadn't touched my phone for a couple of days, I thought about giving it one last try. So I flashed the Defy+ SBF (4th in this list: http://sbf.droid-developers.org/umts_jordanplus/list.php), like I've done multiple times before.
But this time, when rebooting, I wasn't stuck at the M-logo, but in a bootloop. And that gave me the smiles as I knew, that now I should be able to enter Stock Recovery again. From there on, it was no problem to get to a stable base again. After flashing the BL6 Froyo, I'm now on CM9 and everything is fine.
Thanks for all you help.
Sometimes, you just have to give it a rest...
Clock

It is a next such case I see in moto forums ;-) but it is really hard to give a tip: leave it for few days and check again

Use the sbf_flash for Linux
Sent from my MB526 using Tapatalk 2

[Q] Stuck in boot loop with no recovery Please Help

Hi guys long time lurker, first time poster.
Here's the story:
Was running CM 10.2 on my Galaxy S4 AT&T. Everything ran great etc. I decided to flash a new kernel. Upon flashing the kernel I received an error (I must have not done such great research before I did this) but figured nothing had changed since the flash did not go successfully. I proceeded to reboot my phone and lo and behold I'm stuck with a black screen and a constant vibration as if the phone is going to boot up but it doesn't. I immediately went to Odin as I have done when things go awry. After flashing stock firmware Odin says that everything went successful and my phone reboots. However it does not reboot to any screen (no splash screen, no Samsung logo absolutely nothing) just constant vibration and I'm back to square one I cannot boot into recovery I have tried the button combo many, many times but the phone just keeps on fake vibrate booting. The only screen I can get to is the download menu. The things I have tried so far:
1. Flashing back to stock firmware with Odin.
2. Flashing stock kernel by itself with Odin.
3. Tried to flash a custom recovery but since my phone is no longer rooted Odin was giving me a failed message.
4. Tried flashing stock recovery by itself with Odin.
5. Tried Kies but no success either.
I assume no files from a custom ROM will flash successfully as my phone is not rooted. So I guess my question here is am I bricked forever? Odin recognizes my phone and I have read that there is some hope if this happens but I have come to many dead ends searching for a solution to this problem. Have I exhausted my resources on this one or are there a few more things to try? If I left out any information I'll be more than happy to provide what I missed. Thank you in advance.

You flashed a kernel not for your device and have hard bricked your phone. Look up jtag and mobiletechvideos.com

jd1639 said:
You flashed a kernel not for your device and have hard bricked your phone. Look up jtag and mobiletechvideos.com
Click to expand...
Click to collapse
Yep. That is exactly correct.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

Thanks guys. I actually went to AT&T and played dumb. Since the phone was still under warranty they just replaced it on site.

dmesserr said:
Thanks guys. I actually went to AT&T and played dumb. Since the phone was still under warranty they just replaced it on site.
Click to expand...
Click to collapse
Replaced it with MDL or MF3? If MDL, you better block the OTA quickly, If MF3, you better do some reading.

[Q] gt-i9500 and kitkat custom roms incompatibility? HUH?

As the title says I have an International GT_I9500 unlocked
Until now I was always able to install any custom rom I wanted , no problem, just wipe and install and away we went.
Now with KitKat, I AM COMPLETELY UNABLE TO INSTALL ANY OF THE CUSTOM ROMS FOR 4.4.2 -0 NONE WORKS. I can't believe i am jinxed.
I wiped everything, cache, dalvik, system and internal and also did a full wipe - NOTHING WORKED, There are 3 custom roms for 4.4.2 so far and NONE = NOT A SINGLE ONE WANTS TO INSTALL.
I downloaded one of Samsung original 4.4.2 firmware and using Odin I WAS ABLE TO INSTALL AND MAKE IT WORK, yet after doing this, I tried to install any of the 3 customs roms and BOOM, COMPLETE FAILURE
Can anyone help PLEASE GUYS, I feel like BROOMHILDA LONE PERSON WITH A CLOUD ONLY ON MY HEAD
I am curious as to why this is happening

maybe its a i9505 or i9506 rom

provide the Odin messages here.

custom roms failure, huh?
spamtrash said:
provide the Odin messages here.
Click to expand...
Click to collapse
I loaded the custom roms via recovery, not via odin,
so i go into recovery mode via TeamWin, wipe everything and load the custom rom, message says "successful" and i reboot system, that's it
the phone hangs into one of the boot animations and never finishes, left it for longer than 30 minutes, all of them , nothing loads.
go back the same custom roms but with android 4.3 and first shot, loads fine, all of them, same ones that won't load the 4.4.2 load the 4.3
most custom roms load via recovery not odin -
last try was load samsung original firmware 4.4.2 via download Odin, then root then install teamwin recovery. - worked fine
now removed it and reinstalled Thor 4.3 (thor 4.4.2 doesn't work) but tomorrow i'll wipe it and reinstall the samsung 4.4.2 unless you have an idea
*i hope)
sorry about the capitals - NO IT IS AN EXYNOS UNLOCKED GT-I9500 - almost a year after playing with nova settings, xposed and about a dozen custom roms, i THINK i know it's a 9500 - skip the silly suggestions - we're all noobs but not necessarily all boobs
thanks for your help - appreciated if we can solve it

custom roms failure, huh?
KingOfDope said:
maybe its a i9505 or i9506 rom
Click to expand...
Click to collapse
roms were downloaded exclusively from GT=I9500 AREA -
i don't go anywhere else because i know beforehand that they won't work - so why bother
thanks for your suggestion but obviously out of context - i don't live in the US in addition

Maybe wrong recovery ¿?

funny 4.4.2 roms
robertostorm said:
Maybe wrong recovery ¿?
Click to expand...
Click to collapse
i usually use teamwin version 2.6.3
and funny thing in one of the wipes even the teamwin was wiped so i wound using the regular android recovery, with the tiny tiny blue characters
that doesn't have all the teamwin recovery options - so even then it failed
after installing the saunsung 4.4.2 i downloaded a fresh teamwin version and installed via odin/download - like starting from zero. guess what
nope even then the roms freeze at the bootanimation - but the joke is ONLY IF THEY ARE VERSIONS 4.4.2 -they work fine with version 4.3
and when i mean wipe i mean wipe - cache/dalvik/system/internal - and even the other option where you have to type YES for the wipe to go on.
short of reformating the whole memory which i think is excessive, i THINK i tried with a clean clean memory install (according to me)
thanks for your patience
btw most of the custom roms install via recovery so there's no way to get a download install version

exlaval said:
i usually use teamwin version 2.6.3
and funny thing in one of the wipes even the teamwin was wiped so i wound using the regular android recovery, with the tiny tiny blue characters
that doesn't have all the teamwin recovery options - so even then it failed
after installing the saunsung 4.4.2 i downloaded a fresh teamwin version and installed via odin/download - like starting from zero. guess what
nope even then the roms freeze at the bootanimation - but the joke is ONLY IF THEY ARE VERSIONS 4.4.2 -they work fine with version 4.3
and when i mean wipe i mean wipe - cache/dalvik/system/internal - and even the other option where you have to type YES for the wipe to go on.
short of reformating the whole memory which i think is excessive, i THINK i tried with a clean clean memory install (according to me)
thanks for your patience
btw most of the custom roms install via recovery so there's no way to get a download install version
Click to expand...
Click to collapse
Once you flashed stock 4.4.2, your bootloader gets updated, so you can only use 4.4+ roms, also TWRP is full of bugs, just use cwm 6.0.4.5 and you're set.
Also, did you root the stock 4.4.2?

custom roms failure, huh?
robertostorm said:
Once you flashed stock 4.4.2, your bootloader gets updated, so you can only use 4.4+ roms, also TWRP is full of bugs, just use cwm 6.0.4.5 and you're set.
Also, did you root the stock 4.4.2?
Click to expand...
Click to collapse
as i said in a previous message - i used odin in download mode and flashed an original samsung 4.4.2 and it worked, i rooted and reinstalled teamwin
AFTER ALL THIS I tried to install one of the 4.4.2 custom roms - IT FAILED CONSISTENTLY - BY THIS I MEAN ALL ROMS DIED AT BOOTANIMATIONS - AND ALL FAILED TO START
thanks so much

Try with latest Philz recovery or any up to date CWM recovery.
And when coming from stock, you generally have to FULL wipe you phone

custom roms failure, huh?
ayedarts said:
Try with latest Philz recovery or any up to date CWM recovery.
And when coming from stock, you generally have to FULL wipe you phone
Click to expand...
Click to collapse
just downloaded cwm version 6.0.4.6 installed via recovery. launched recovery installed latest wanamlite for 4.4.2 - message was "installed successfully" please reboot
i rebooted and for the last 15 minutes all i have is a BIG SAMSUNG on the screen - nothing beyond
just another hitch with kitkat - i have a SONY XPERIA Z TABLET with wifi and sim - a couple of weeks ago i rooted it but the cwm version is not good because it's on the vertical side and you cannot see the bottom of the menu so it's useless - anyhow. i rooted it and left it at that.
i got notice from sony that a new os version (kitkat) was ready for install - so I just told the tablet to start - and the os install screwed the tablet,
there was no way to reload and it completely deleted the memory , it went to sony to reload - so i have a big hunch there is something not right somewhere -
anyway the phone still has the SAMSUNG and it ain't going anywhere while i am writing all this
very discouraging = sure as heck i ain't buying no more galaxys of any sort, i was ready to preorder the s5 at 455british pound, unlocked - but since this i am dropping samsung, i like very very much the xperia tablet it's faster than the s4 so perhaps i'll jump to the sony xperia fone and bbye korea

maybe i9505 rom

custom roms failure, huh?
i know you're trying to help - but if you read all the previous (long and boring) messages - there's no mistakes, there's no 9505
ALL THE ROMS I DOWNLOAD AND USE - ALL OF THEM WITHOUT EXCEPTION come for the i9500 development area, I DON'T BOTHER WITH
9505 - MOSTLY BECAUSE I DON'T HAVE A 9505
UPDATE - today after loading the latest cwm recovery i got lucky to be able to load ONE - READ IT - ONE CUSTOM ROM ( rom from HASAN)
this is the very only that i got to work, the other two just refuse to finish the boot - i don't know where they freeze.
even the wanamlite custom rom for 4.4.2 freezes - this is really annoying and a puzzle - this is my fourth samsung fone and never ever did i
find the bug that freeze everything. I hope that some of the other developers will come up with new kitkat versions for the 9500 and see if the bug persists or not -
any help will absolutely be appreciated, guys, some sort of boot log that can help pinpoint,
thanks again

You know the fact you keep using capital letters (so you might be trying to scream) is a little annoying.
I have a Samsung Galaxy S4 GT-I9500. I live in Costa Rica (so not in the US obviously).
I installed stock 4.4.2 using ODIN, then flashed ROOT and finally installed a custom CWM. First I tried Philz and ended up with 6.0.4.6.
I have already tried 2 different custom ROM's but I didn't like them so I went back to stock. I am very satisfied with the performance of my phone with stock, but that's not the point.
The thing is that I have the same phone you have, i installed the same software you installed, I followed the same steps you have followed yet I am able to install any custom ROM i like.
Maybe it is your phone, or maybe you're just looking for an excuse to quit Samsung and you're simply blaming kitkat your inability of installing ROMs now.
I'm just saying... there are several options you can tried if you quit being angry and actually try them.
Personally, I would start from scratch. Flashing via ODIN again, rooting accordingly with the right files, using a recovery that is recognized to work with 4.4.2, and finally using the right custom ROM.

custom roms failure, huh?
pinktheater said:
You know the fact you keep using capital letters (so you might be trying to scream) is a little annoying.
I have a Samsung Galaxy S4 GT-I9500. I live in Costa Rica (so not in the US obviously).
I installed stock 4.4.2 using ODIN, then flashed ROOT and finally installed a custom CWM. First I tried Philz and ended up with 6.0.4.6.
I have already tried 2 different custom ROM's but I didn't like them so I went back to stock. I am very satisfied with the performance of my phone with stock, but that's not the point.
The thing is that I have the same phone you have, i installed the same software you installed, I followed the same steps you have followed yet I am able to install any custom ROM i like.
Maybe it is your phone, or maybe you're just looking for an excuse to quit Samsung and you're simply blaming kitkat your inability of installing ROMs now.
I'm just saying... there are several options you can tried if you quit being angry and actually try them.
Personally, I would start from scratch. Flashing via ODIN again, rooting accordingly with the right files, using a recovery that is recognized to work with 4.4.2, and finally using the right custom ROM.
Click to expand...
Click to collapse
-------------------------------------------------------
First - The capitals I used were ONLY to emphasize certain aspects and not intended as screaming, which is the usual sense - That was not my intention,
Second - I have being using Samsung for the last 7 years, I was not intending to leave until I hit this brick and further I nearly went to Clove, UK (where I usually pre-ordered my last 3 Galaxy's - months ahead of delivery) so thumping me by saying I am looking for an excuse to dump Samsung, is way off base, so much so, that if that indeed was my intention, why for all heavens would i bother to find a solution, and waste so much time and effort to make it work
Third - I have being as polite as any person can be, with or without, this hitch, don't judge, about being angry or not, you don't know me well enough to know the difference, just stick to the point in question without getting personal.
Fourth - What I have described is EXACTLY to a tee what is happening to me, what happened to YOU , is IRRELEVANT, you may be one of the lucky ones who has no issues installing the roms in questions. so unless you do have a suggestion as to finding the reason the fone loops on boot, skip what you did or didn't do, they are IRRELEVANT, because they don't provide a solution.
Fifth - If you read my descriptions you will notice the many times I installed customs roms on the many galaxy's and Note's I have/had.That ought to clue you that i know a basic way on how to do the installations (Odin, recovery, teamwin. cmw,) you name it I've done it, and i've unbricked more than once my fones. so yes i do know how to use Odin
Sixth - For some reason I was able to install the "HASSAN" rom (the ONLY and ONLY) 4.4.2 custom that worked. the others they just won't, PERIOD
So if you have a technical solution as to how to get a log of the looping so we can tell exactly at what point the fone loops. or some other technical solutions, please let me know them asap I am dying to see my fone with a custom 4.4.2,
Seventh - Yes I am extremely disappointed that the S5 is just not fantastic enough to lay 455GBP to pre-order. there are a few more advances but it is "ALMOST" good = the bezel didn't disappear - the 2K display isn't there - the sharper casing is still missing - the better battery is still not there - the wireless charging - To have 2000 horse power engine under the hood of a beat up VW beatle. doesn't make you good looking enough to go cruising on a saturday nite and brag about your "car" -
BTW = I am absolutely no fan of the Iphone (yuk) nor of Sony (which is as restricted as apple)
Can you help solve my issue - thanks

Bricked? No custom or stock rom?

ive had my note 3 for awhile and have avoided rooting or modding it in any way for quite sometime, but i rooted the stock firmware i believe it was 4.4.2???? im not 100% with towelroot and i was able to install safestrap thats where my success ended I didnt make any backups for whatever dumb reason and also it has been quite sometime since modding any phones, now my phone wont boot into any rom ive tried i have tried two so far and i cant get the factory one back, half the time i cant install roms and the rest of the time they work but they wont boot ive tried creating rom slots but those dont work, read somewhere they arent supported in 4.4.2 ???? and when i tried overwriting the factory it still didnt work, now my phone wont boot into anything anymore and im not quite sure what i did wrong and if there is any way to fix it, i would have like to install knoxraid on this phone since it supposedely fixes the gps issues lots of people have when i try to install that particular rom i get a successful message but then when i wipe cache/dalvik it work and then i hit reboot nothing happens, all i get is a black screen oh and its says that safestrap is disabled
can anyone help i could really use some help here

ecuadorche said:
ive had my note 3 for awhile and have avoided rooting or modding it in any way for quite sometime, but i rooted the stock firmware i believe it was 4.4.2???? im not 100% with towelroot and i was able to install safestrap thats where my success ended I didnt make any backups for whatever dumb reason and also it has been quite sometime since modding any phones, now my phone wont boot into any rom ive tried i have tried two so far and i cant get the factory one back, half the time i cant install roms and the rest of the time they work but they wont boot ive tried creating rom slots but those dont work, read somewhere they arent supported in 4.4.2 ???? and when i tried overwriting the factory it still didnt work, now my phone wont boot into anything anymore and im not quite sure what i did wrong and if there is any way to fix it, i would have like to install knoxraid on this phone since it supposedely fixes the gps issues lots of people have when i try to install that particular rom i get a successful message but then when i wipe cache/dalvik it work and then i hit reboot nothing happens, all i get is a black screen oh and its says that safestrap is disabled
can anyone help i could really use some help here
Click to expand...
Click to collapse
May I know which variant on Note3 you are using.
and what's the OS version? 4.3? or 4.4.2 or 4.4.4
what's your region (CSC).??
I would suggest you to go into download mode and download appropriate stock firmware from SamMobile or from Samsung Updates (Link for N9005) and flash Stock ROM using ODIN.
Thanks.