Database Develop

Bricked Tab???? HELP

HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks

geoyakult said:
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
Click to expand...
Click to collapse
If you can boot into CWM, then you should easily be able to get into Download mode as well. You can go back to the stock image for your Tab, or try and reflash a different rom via CWM... sounds like just a bad flash for a soft brick..

pvtjoker42 said:
If you can boot into CWM, then you should easily be able to get into Download mode as well. You can go back to the stock image for your Tab, or try and reflash a different rom via CWM... sounds like just a bad flash for a soft brick..
Click to expand...
Click to collapse
Hi there, thanks for reply back to me.
I've managed to actually get it going again, by reflashing to the Overcome kernel.
However, some apps has disappeared and also the market.
Anyways, i wish to revert the whole thing back to stock, kernel and firmware. Is there a way I can do this via Kies?
Let me know what information regarding my tab you need. I believe it is the CPW (GSM) UK version.
cheers

geoyakult said:
HELP! I am so scared...somebody help me!
I tried to installed the Overcome kernel but didn't like it, as each time I boot up, that voice comes up.
And plus, a few of my original apps was lost (including Market). So I thought i'd install with Odin again the:
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
And now, when i switch on the tablet, it'll boot with the animation and sound, but then a blank screen.
I can manage to boot into ClockworkMod recovery. Can i be saved? Please somebody help me!
Thanks
Click to expand...
Click to collapse
LOL. FYI, your Tab is not haunted. That voice that you refer to, is basically an indicator that the file-system on the Tab is being converted from RFS to EXT4 (what some would affectionately refer to as the lag-fix). You should have left it to continue. That's the reason we ask people to let it finish booting before doing anything else. As always, when it comes to flashing a new firmware/kernel, it's always better to read up and know what to expect.
Anyway, by the looks of it, you might have a corrupted file-system, since you keep shutting it down mid-conversion. That's the reason "the voice" keeps coming back. If you'd allowed it to complete, it should not have returned.
Secondly, flashing the Overcome Kernel alone will NOT remove the Market application. If you were already on the CF-Root kernel, it might remove the CF-Root specific applications like the CwM "app" (and not the recovery functionality, mind you...) and the Tweaks app as these apps were created by ChainFire specifically for his kernel.
Best advice would be to re-flash a stock firmware first, to get your Tab into a clean system. From there, you can continue to to install the kernel of your choice (like ChainFire or Kouxudaxi's fine kernels as well.... these kernels, if I'm not mistaken, do not do automatic EXT4 conversions)
If you're unsure of how to do this, refer to the guide in teamovercome.net and it'll guide you in basic re-stocking (but using our Stock safe package which will provide you with the Gingerbread-based JQ1 firmware).

LOL, +100000000000000000000000 thepitbull...

thepittbull said:
LOL. FYI, your Tab is not haunted. That voice that you refer to, is basically an indicator that the file-system on the Tab is being converted from RFS to EXT4 (what some would affectionately refer to as the lag-fix). You should have left it to continue. That's the reason we ask people to let it finish booting before doing anything else. As always, when it comes to flashing a new firmware/kernel, it's always better to read up and know what to expect.
Anyway, by the looks of it, you might have a corrupted file-system, since you keep shutting it down mid-conversion. That's the reason "the voice" keeps coming back. If you'd allowed it to complete, it should not have returned.
Secondly, flashing the Overcome Kernel alone will NOT remove the Market application. If you were already on the CF-Root kernel, it might remove the CF-Root specific applications like the CwM "app" (and not the recovery functionality, mind you...) and the Tweaks app as these apps were created by ChainFire specifically for his kernel.
Best advice would be to re-flash a stock firmware first, to get your Tab into a clean system. From there, you can continue to to install the kernel of your choice (like ChainFire or Kouxudaxi's fine kernels as well.... these kernels, if I'm not mistaken, do not do automatic EXT4 conversions)
If you're unsure of how to do this, refer to the guide in teamovercome.net and it'll guide you in basic re-stocking (but using our Stock safe package which will provide you with the Gingerbread-based JQ1 firmware).
Click to expand...
Click to collapse
Hi there,
Thank you so much for your time in replying - I've managed to install what i believe is stock Gingerbread from Samsfirmware. So everything looks back to normal... tho i have posted another Question, with all my firmware details so I can be reassured I am back to stock.
So sorry, I panicked so badly last night..ha!

You have also special thread with many scenarios how to fix your tablet if anything goes wrong.
It helped me yesterday to revive my Galaxy Tab. Just suddenly it started freezing and restarting, after 3 weeks working perfectly on Overcome. Nothing changed, or updated, nothing installed for days, and all what was ever installed are programs I already have on my two other Android phones, it simply froze in the middle of work. Wipe didn't work, changing file system didn't work, etc...
Read the thread: http://forum.xda-developers.com/showthread.php?t=1133590
Very good material.

nidza said:
You have also special thread with many scenarios how to fix your tablet if anything goes wrong.
It helped me yesterday to revive my Galaxy Tab. Just suddenly it started freezing and restarting, after 3 weeks working perfectly on Overcome. Nothing changed, or updated, nothing installed for days, and all what was ever installed are programs I already have on my two other Android phones, it simply froze in the middle of work. Wipe didn't work, changing file system didn't work, etc...
Read the thread: http://forum.xda-developers.com/showthread.php?t=1133590
Very good material.
Click to expand...
Click to collapse
Im very glad that the guide helps many ppl
@the Op : do me a fav and flash safe
Sent from my GT-P1000 using Tapatalk

k0sh said:
Im very glad that the guide helps many ppl
@the Op : do me a fav and flash safe
Sent from my GT-P1000 using Tapatalk
Click to expand...
Click to collapse
Yup, in future i will be more careful when flashing, so glad that my tablet is back to normal (albeit with the Italian release of GB ) but everything works fine.
Will do more reading on the forums before undertaking any more flashing, make sure i know what i am doing and which Rom is best for me to use.
Cheers
Sent from my GT-P1000 using XDA App

geoyakult said:
Yup, in future i will be more careful when flashing, so glad that my tablet is back to normal (albeit with the Italian release of GB ) but everything works fine.
Will do more reading on the forums before undertaking any more flashing, make sure i know what i am doing and which Rom is best for me to use.
Cheers
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
best reaction i never read

[Q] FASTY III problem/question

HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!

nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
in terminal emulator type su and then reboot recovery maybe it work
or may be you just flashed unsupported recovery

nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
I have been having the same problem recently, but not just with this rom. I have flashed many roms to my device, but it appears that almost everytime i try to flash something now, the same exact thing happens as the OP. any information on what is wrong or how to fix this would be greatly appreciated.

When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.

studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
Sometimes this happens, but i am usually still able to use the rom after i wait for awhile. Recently it just gets stuck at the ATT logo screen and does nothing else.

HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK

studacris said:
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
Click to expand...
Click to collapse
i just tried it with a solid connection and it almost instantly said failed in the red box. now i cant turn it on or get to download mode so im pretty sure it is hard bricked. is there any way you can help me with this?
EDIT: False alarm, i can still get to download mode so i can ODIN back to stock, but i do not know if i should risk it again

Whew that was close.
You can flash to stock using a bootloader less package, that way if it fails it can't hard brick.
Then if that works, find an entire stock gingerbread package with bootloaders included, and flash that instead of just the bootloader one click. this again, will involve risk, but full Odin package seem to work better on some phones than one clicks do.

I tried to flash the bootloader again and it succeeded. i then proceeded to try and flash Fasty KK4 v1.1 and once again i was stuck at the ATT logo. For some reason with every rom i flash, when the logo pops up, it starts dim and then get bright. After it gets bright, it stays that way and it is a real pain not being able to use custom roms anymore.

If you have the GB bls just make sure you follow LL's instructions in the OP for Fasty. I had the same issue, but it was me mistake for not following the istructions properly

studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
i DO get a very colorful white noise screen whenever it boots up ...the screen goes away once it fully reboots....I wondered about it but just assumed it was a quirk of the FASTY III package...
Is Rom Manager a froyo based app?

No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS

studacris said:
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
Click to expand...
Click to collapse
Really? Rom Manager helped me a lot until this Fasty III installation....even in my previous rom Fasty II it worked fine and did great for backing up and restoring backups....saved my asss a few times with those restores lol....But if this program doesn't work for fasty III what comparable program can I use?
Also I still can't intorecovery mode...nothing works...I even tried using ADB and Droid Explorer....nothing seems to get it into recovery mode...
Am I going to have to flash back to stock ROM and try reinstalling fasty iii again? This seems all so tedious lol...
OR is there a way for me to flash back to Fasty II without having to go back to stock rom? or without having to access the recovery screen?
Thank you^

All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.

studacris said:
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
Click to expand...
Click to collapse
Thank you for the info!
Looks like fasty III is a GB based mod after all...I guess I should read up more on the rom before installing lol....I did not expect the dev to go from froyo to gb -_-
I was thinking of using your previous post for the one click gb bootloaders only....but it seems a little iffy and I can't afford to hardware brick the phone lol...
Makes me wonder tho...is it really THAT risky to flash bootloaders? It would make things simpler if i could just flash the gb bootloaders and go from there....

the whole flash should take less than a minute, where the actual writing takes only a few seconds...but if you were to lose communication in that awful window then it would be bad day.
But that is a small window, and if you have never had connection issues you should be ok if Odin tends to be iffy, you van try heimdall I've heard that works better for some.

Still haven't tried flashing the bootloaders because i'm scared of the possibility of hard bricking my phone... If worst case scenario was to happen and it gets hard bricked....are there any options to restore that phone? or is it just paper weight after?
Also until I flash those bootloaders there is no way to back up my phone or anything?
Thanks for all ur help btw!

another issue i am having is that the phone seems pretty laggy after installing this rom...even with tegra overclock premium and tweaking it up to 1252mhz 1275mv 1100mv setting...it still seems laggy when opening sms etc....is this just the results of a bad rom install? also battery life seems crappy....even after doing the battery recalibration...of course i couldn't wipe the battery stats since i cant get into recovery...

Hard bricks are recoverable by a hardware modification known as unbrickable mod, search for user Adam outler, or go to mobiletechvideos.com they both offer this service if you're not a soldering expert.
Battery recalibration does NOTHING the stats are reset everytime you charge to 100, and besides that they don't calculate your current battery level, just what's been using it, its what's used in settings> about phone> battery use. It has nothing to do with extending battery life.

oh lol...i have been reading all these threads where people are talking about how much their battery life improved after they did the recalibration and stat wipe ....well anyways I am going to attempt the bootloader flashing...I hope everything goes well! after that I want to try reflashing the fasty III ROM...
Do you have any recommendations as far as a good ROM for teh captivate? One that doesn't lag and has good gps & battery life? I would appreciate any help you can give.
Thanks!

[Q] GT-S6500D (jenad) problems with WiFi and SD (internal sdcard0)

Dont stone me if repost, but believe it is not, I honestly tried to study this and other forums for last almost 2 weeks without any results:
I got Mini2 with GB stock ROM and first rooted (using Poot exploit) and upgraded gradually to CWM 6.0.4.5 and CM 10.1 and later CM 11. Didnt discovered any problems except for sdcard0 mount problem as described may times. sdcard0 is not mountable under CWM 6.0.4.5 and CM11 but I think that this can be solved using other threads in this forums, so not a matter here and now, however, it may hint you what is possibly going on. The main thing is, that after trying to experiment with OC kernel, my WiFi always indicates ERROR when trying to switch it on. No matter if in Stock ROM or CM (any version). I tried to reflash Stock and CM (10.1; 10.2 and 11), even repartitioned with ODIN (3.09) and reflashed Stock ROM. No improvement, no change.
Strange thing is, that it was said, that after flashin CM (or CWM not clear now), the offline battery charging does NOT work and phone alway reboots. That can be confirmed by me, but with that exception, that it does NOT work either after reflashing Stock ROM and Stock RECOVERY. Even after this, phone never switches OFF when connected to the charger, just reboots.
I have always did full WIPE (data,cache, format system).
Currently I have Stock ROM 2.3.6
kernel 2.6.38.6-1248583 [email protected] #1 dated Thu Nov 7 20:39:38 KST 2013
Baseband S6500DXXMK1
Recovery reports "Android system recovery (3e)
During last Stock reflash the baseband got upgraded. I am a PC guy, not an Android specialist, but from everlasting WiFi problems and offline charging not working even with Stock ROM and Stock recovery, it looks, like something somewhere got left from my tries with either OC kernel or CWM/CM and prevents Wifi from being switched on. Curently my Stock is rooted so I can get some logs/info anybody can need willing to help/investigate..
Any help or pointers to troubleshooting are highly appreciated as I really love my little cute Mini II.

Alternative
prgbear said:
Dont stone me if repost, but believe it is not, I honestly tried to study this and other forums for last almost 2 weeks without any results:
I got Mini2 with GB stock ROM and first rooted (using Poot exploit) and upgraded gradually to CWM 6.0.4.5 and CM 10.1 and later CM 11. Didnt discovered any problems except for sdcard0 mount problem as described may times. sdcard0 is not mountable under CWM 6.0.4.5 and CM11 but I think that this can be solved using other threads in this forums, so not a matter here and now, however, it may hint you what is possibly going on. The main thing is, that after trying to experiment with OC kernel, my WiFi always indicates ERROR when trying to switch it on. No matter if in Stock ROM or CM (any version). I tried to reflash Stock and CM (10.1; 10.2 and 11), even repartitioned with ODIN (3.09) and reflashed Stock ROM. No improvement, no change.
Strange thing is, that it was said, that after flashin CM (or CWM not clear now), the offline battery charging does NOT work and phone alway reboots. That can be confirmed by me, but with that exception, that it does NOT work either after reflashing Stock ROM and Stock RECOVERY. Even after this, phone never switches OFF when connected to the charger, just reboots.
I have always did full WIPE (data,cache, format system).
Currently I have Stock ROM 2.3.6
kernel 2.6.38.6-1248583 [email protected] #1 dated Thu Nov 7 20:39:38 KST 2013
Baseband S6500DXXMK1
Recovery reports "Android system recovery (3e)
During last Stock reflash the baseband got upgraded. I am a PC guy, not an Android specialist, but from everlasting WiFi problems and offline charging not working even with Stock ROM and Stock recovery, it looks, like something somewhere got left from my tries with either OC kernel or CWM/CM and prevents Wifi from being switched on. Curently my Stock is rooted so I can get some logs/info anybody can need willing to help/investigate..
Any help or pointers to troubleshooting are highly appreciated as I really love my little cute Mini II.
Click to expand...
Click to collapse
Alternatively, can someone direct me to steps to COMPLETELY WIPE EVERYTHING (I mean really everything to the bone and start with STOCK ROM from scratch?
Thanx.

prgbear said:
Alternatively, can someone direct me to steps to COMPLETELY WIPE EVERYTHING (I mean really everything to the bone and start with STOCK ROM from scratch?
Thanx.
Click to expand...
Click to collapse
Use this code:
*2767*3855#
Click to expand...
Click to collapse

What will it do? Need to know before I use it. Cannot afford to **** it up.
Thanks, Ondrej

prgbear said:
What will it do? Need to know before I use it. Cannot afford to **** it up.
Thanks, Ondrej
Click to expand...
Click to collapse
1 google search : https://www.facebook.com/kasmirnewsagency/posts/384662564983666

[Q] I messed up the RADIO on my i8190L and now stuck in bootloop

Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery

You downloaded the wrong modem file. You need the one for the I8190L, but you flashed one for the I8190.
Sent from Tapatalk on my GT-I8190 running Novafusion's Carbon 4.4.2

chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck

No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11

chan1628 said:
Let's start with a little background as to how I got into this mess
- I had a perfectly working i8190L running SlimBean 4.3 from Maclaw (and I should've left it alone since its the wife's phone)
- I wanted to try out the new SlimKat 4.4 (http://get.novafusion.pl/?id=955)
- After a clean flash of slimkat, the new ROM was running fine after I completed setup EXCEPT baseband was 'xxxx'
- I rebooted into recovery and flashed GT-I8190_modem.bin-XXAMJ3-update2.zip because it was in my sdcard. I thought flashing a new radio would change the baseband except now I'm stuck in a bootloop with NO ABILITY TO BOOT TO RECOVERY!!!!
- I can only boot into Download mode, so I can still ODIN flash the system
Can someone suggest how/if I can fix this? I'm just kicking myself for turning a fully working phone into a brick with my wife breathing down my shoulders
my working setup was TWRP 2.7, SlimBean 4.3 and I had no idea which radio the i8190L came with default
I created a nandroid before all this mess, but I just need a way to get back into Recovery
Click to expand...
Click to collapse
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.

jstath1972 said:
Sorry but you are going to sleep on the couch tonight I suggest this:
You must download the original rom from SamMobile, install it through Odin and then install again through Odin the Recovery and through Recovery your "old" new Rom. When you are in the new Recovery check for the nandroid backup that you made . If it isnt there look for the couch because the phone is with the "old" new Rom without any of the past data.
Btw if you want you can upgrade your baseband from here:http://forum.xda-developers.com/showthread.php?t=2526831
Good luck
Click to expand...
Click to collapse
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already

KoolKid98189 said:
Don't bother trying to flash it if nothing happens, drain the battery, return to seller and get replacement. I got free replacement from Amazon with my bricked rooted S3 mini.
Click to expand...
Click to collapse
its not going to be that easy for me... i've had this phone for almost 2yrs already
tys0n said:
No recovery at all or bootloop in recovery as well?
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
no recovery at all... it bootloops if i power on normally

chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.

chan1628 said:
its not going to be that easy for me... i've had this phone for almost 2yrs already
no recovery at all... it bootloops if i power on normally
Click to expand...
Click to collapse
It was a tough decision for me, it was either stick to a ****ty BlackBerry or get a free replacement and sacrifice the data. Some of it should be synced to your Google account

tys0n said:
It depends on what country you're in and if the phone is locked to any specific carrier.
If it's not locked then I believe any i8190L firmware will do, just to get the phone running again.
Click to expand...
Click to collapse
ok, i will give all this a try and hope for the best
thanks everyone for the quick responses :good:

You could also try to reflash just recovery thru Odin and see if it works.
Sent through time and space from my s3mini/CM11

chan1628 said:
just to clarify... what is consider "the original rom from SamMobile"? There are plenty of versions and country codes to choose from... I just wanted to make sure I'm downloading the correct one.... i've done enough of using the wrong files already
Click to expand...
Click to collapse
You are in Canada but the L version is for the Latin America countries. So the firmware must be from one of that countries. Which one i can't tell you. You should ask your seller.

[problem solved]
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)

chan1628 said:
Ok, I was able to restore the phone with /u/jstath1972's suggestion
1. I went to http://www.sammobile.com/firmwares/ and downloaded the latest 'L' firmware
2. I used ODIN to flash the firmware
3. the phone REBOOTED!!!
(once the phone rebooted, the rest was easy)
4. powered off and ODIN flashed the lastest TWRP
5. powered off and booted into recovery
6. RESTORED NANDROID so wife would stop giving me the look
7. updated baseband as suggested: http://forum.xda-developers.com/show....php?t=2526831
THANK YOU THANK YOU :good:
side note: i wish my work was this effective in resolving technical issues (just my 2 cents)
Click to expand...
Click to collapse
Good sleep tonight, my friend ! :good:

Note 4 - Most stable ROM (custom or stock)

Hey guys, been a while since I've been here.
Currently, I'm running stock android 6.0.1 (N910FXXU1DPB1) on my Note 4 (Snapdragon).
I flashed this via Odin (because back then it wasn't released in my country yet). Did the usual, clean reset and when i flashed there were no problems (besides meh battery time). But since a week or two I'm having a lot of problems, a lot of random reboots, reboot time is way too long, battery drainage is awful and random freezes. A lot of these problems occur when using snapchat, not sure why.
So now I'm wondering what is the most stable ROM around. Battery life and smoothness are most important to me. At this point, I don't really care if it's a custom ROM or stock. With my old phone (S3) i had a lot of problems after i started running custom ROMs so I'm hoping you guys have some options where this won't happen.
Thanks in advance, Sam
BTW: Sorry for my bad English, it's not my main language.

Another weird thing happened. Just installed TWRP (once again via Odin), but when I reboot into recovery, I first get the message 'installing system update', then it says 'no command' and then it reboots in Android Recovery. Any ideas how to solve this?

Note 4 sucks after this MM update it is worst than any other small budget phone.

anasrizvi said:
Note 4 sucks after this MM update it is worst than any other small budget phone.
Click to expand...
Click to collapse
So you'd recommend going back to stock kitkat?

SamC95 said:
Hey guys, been a while since I've been here.
Currently, I'm running stock android 6.0.1 (N910FXXU1DPB1) on my Note 4 (Snapdragon).
I flashed this via Odin (because back then it wasn't released in my country yet). Did the usual, clean reset and when i flashed there were no problems (besides meh battery time). But since a week or two I'm having a lot of problems, a lot of random reboots, reboot time is way too long, battery drainage is awful and random freezes. A lot of these problems occur when using snapchat, not sure why.
So now I'm wondering what is the most stable ROM around. Battery life and smoothness are most important to me. At this point, I don't really care if it's a custom ROM or stock. With my old phone (S3) i had a lot of problems after i started running custom ROMs so I'm hoping you guys have some options where this won't happen.
Thanks in advance, Sam
BTW: Sorry for my bad English, it's not my main language.
Click to expand...
Click to collapse
I use and have been using Alexndr's ROM's for ages! They are reliable have plenty of options (root/no root, odexed/deodexed, xposed or not) ... he regularly updates and sorts out peoples' problems (although I have never had one) and produces a very stable ROM.
His instructions are clear and easily understood and he knows what he is doing! My favourite ROM maker ... Thanks Alexndr!!

robmeik said:
I use and have been using Alexndr's ROM's for ages! They are reliable have plenty of options (root/no root, odexed/deodexed, xposed or not) ... he regularly updates and sorts out peoples' problems (although I have never had one) and produces a very stable ROM.
His instructions are clear and easily understood and he knows what he is doing! My favourite ROM maker ... Thanks Alexndr!!
Click to expand...
Click to collapse
Thanks for you reply.
Seems like a nice ROM, would want to flash it, but seems like I'm not going to be able to flash new ROMs (due to the problem described above.

I had the same problem. you must have the newest version of odin.

DrQuestion said:
I had the same problem. you must have the newest version of odin.
Click to expand...
Click to collapse
Seriously? Is it that simple lol? I'll try that, thanks.
EDIT: Turned out it wasn't that simple, got the message 'There's no PIT partition.'

anasrizvi said:
Note 4 sucks after this MM update it is worst than any other small budget phone.
Click to expand...
Click to collapse
I've been running Marshmallow on my N910C since it was released for my device, and I haven't experienced any major problems with it. Other than not getting the official OEM spare battery to charge correctly on it. Everything is work just fine.

I've been running the MM PaulPizz Rom for a few days and it's been rock solid so far. Not a single crash or error.

SamC95 said:
Another weird thing happened. Just installed TWRP (once again via Odin), but when I reboot into recovery, I first get the message 'installing system update', then it says 'no command' and then it reboots in Android Recovery. Any ideas how to solve this?
Click to expand...
Click to collapse
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download

aaron74 said:
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download
Click to expand...
Click to collapse
Thanks for your reply.
Alright man, I will try that tomorrow.
I think the download should be okay, downloaded V3.12.3 a few hours ago, or do I need a different one?
And should I also do this if I get the message that there's no PIT partition?
Thanks for your help, I'll let you know if it works or not.

SamC95 said:
Thanks for your reply.
Alright man, I will try that tomorrow.
I think the download should be okay, downloaded V3.12.3 a few hours ago, or do I need a different one?
And should I also do this if I get the message that there's no PIT partition?
Thanks for your help, I'll let you know if it works or not.
Click to expand...
Click to collapse
I always use 3.11.1 straight from Sam mobile site. Here http://dl.sammobile.com/Odin3-v3.11.1.zip
Never had a problem with it.

Stock ROM's all the way.
I've used KK, LL and MM. After upgrading to MM (by mistake) and using it for 2 weeks, had to throw it away! MM is the worst case ever! I've went even back to KK, used about 2 days and went finally for 5.1.1 - best case ever! No lag, no "app stop working", no delay (which with MM was about 3 secs between opening closing apps). But, the 5.1.1 has a little distress about battery drain (about 5% more than KK or MM). Is the only thing is keeping LL for being best version. If you rollback from MM to LL or KK, you MUST untick Auto Reboot! Just let the flash go till the end and then take the battery out; put it back, start with recovery and wipe everything prior booting normally. And for the downgrade you have to use:
1. from MM to LL - Odin 3.11
2. from MM to KK - Odin 3.09

After trying myriad of roms(Almost all roms from Snapdragon section) + kernels, I prefer Stock rom for it's batterylife + stable performance. I haven't rooted after returning to stock. But i will return some sort of custom rom soon as my phone looks so boring without ported apps, multi dpi compatible apps, etc. If u prefer stable performance move to pure stock, If u need assortment of features use one of the ported note7/S7 roms, If u want slick and fast roms use AOSP/CM based roms but as far my experience goes they are not much stable while compared to touchwiz.
Currently running latest MM stock on 910G.

Stonewolf said:
Stock ROM's all the way.
I've used KK, LL and MM. After upgrading to MM (by mistake) and using it for 2 weeks, had to throw it away! MM is the worst case ever! I've went even back to KK, used about 2 days and went finally for 5.1.1 - best case ever! No lag, no "app stop working", no delay (which with MM was about 3 secs between opening closing apps). But, the 5.1.1 has a little distress about battery drain (about 5% more than KK or MM). Is the only thing is keeping LL for being best version. If you rollback from MM to LL or KK, you MUST untick Auto Reboot! Just let the flash go till the end and then take the battery out; put it back, start with recovery and wipe everything prior booting normally. And for the downgrade you have to use:
1. from MM to LL - Odin 3.11
2. from MM to KK - Odin 3.09
Click to expand...
Click to collapse
Using Odin 3.11 to downgrade from MM to KK works just fine. I just did 2 days ago.

I had errors with 3.11; once changed to 3.09 worked like a charm. I've posted from my experience. Anyway, good to know other opinions and good to know that works either way (maybe my system had some conflict with vs. 3.11). However, that downgrade was done only to my first device, not the second one. I still keep MM on my second N4.

Stonewolf said:
I had errors with 3.11; once changed to 3.09 worked like a charm. I've posted from my experience. Anyway, good to know other opinions and good to know that works either way (maybe my system had some conflict with vs. 3.11). However, that downgrade was done only to my first device, not the second one. I still keep MM on my second N4.
Click to expand...
Click to collapse
Have you tried 3.12? It's the only one that worked for me.

back to lollipop .......... one of the best Note 4 ROM ever build ...........
Been using Nameless ROM V7 ............

aaron74 said:
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download
Click to expand...
Click to collapse
This did the trick, thanks a lot! I finally got to flash TWRP and ended up installing Alexndr ROM (thanks for the tip @robmeik) but sadly I'm still having random reboots