long story short, i had root and oclf, i uninstalled it and installed voodoo, let system sit for 30 mins, i guess i got impatient, so i pulled and restored, i created the disable_lagfix file and it ran through the paces, so i decided to put one of the other roms back on that had d1 update.. anyways, it loaded but i had NO cell radio, none, also i seem to get a invalid argument when booting up to recovery but i can still boot into CWM, i have tried to restore just the modem file part to see if that works but i think it freezes about 2/3 of the way and i get a scirpt ABORTED MESSAGE (STATUS 7).
I really need someones help.
any suggestions
Odin! Or you can just odin clockwork kernal and find the nanadroid back up on here. Then restore.
magicriggs said:
Odin! Or you can just odin clockwork kernal and find the nanadroid back up on here. Then restore.
Click to expand...
Click to collapse
tried that, several times, no luck.. i took it back to the store cuz i was under 30 days, it was just easier that way. Ill run a proper CWM back up this time
Andwhy81
Not saying u did this but not having a cell radio is often a symptom of flashing something in the "phone" part of Odin instead of in the "PDA" again not saying u did this but I've seen several instances of people having this problem in irc all being caused by that. Be a little more careful with the new one. I do t think a backup will even save u if u flash something to the phone part. Goodluck sir
Sent from my SCH-I500 using XDA App
ksizzle9 said:
Andwhy81
Not saying u did this but not having a cell radio is often a symptom of flashing something in the "phone" part of Odin instead of in the "PDA" again not saying u did this but I've seen several instances of people having this problem in irc all being caused by that. Be a little more careful with the new one. I do t think a backup will even save u if u flash something to the phone part. Goodluck sir
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
That is a possabilty, i was up late and tired, thanks for not flaming.
i now have voodoo and loving it,
andwhy81 said:
That is a possabilty, i was up late and tired, thanks for not flaming.
i now have voodoo and loving it,
Click to expand...
Click to collapse
You could easily determine this by looking in setting - about phone - baseband version. If it says uknown, you've killed your cell radio by flashing to "phone" instead of "pda." If you have a version number, you're fine.
I flashed CWM into "phone" instead of "pda". Is there really no fixing it? I've tried nandroid recovery, Odin, everything and still no cell radio and also force closes everywhere...
Also will VZ take the phone back? The phone's less than a week old...I'll make sure to be more careful next time
Try and say you tried to run the ota update and it loaded that
Sent from my SCH-I500 using XDA App
Ahodson1985 said:
I flashed CWM into "phone" instead of "pda". Is there really no fixing it? I've tried nandroid recovery, Odin, everything and still no cell radio and also force closes everywhere...
Also will VZ take the phone back? The phone's less than a week old...I'll make sure to be more careful next time
Click to expand...
Click to collapse
Yes, there's really no fixing it. To fix the FC issues you need to get to the OS to do a privacy wipe, or wipe /dbdata from the shell. I would start with restoring everything from the Odin post to get everything back to stock. At least when you go to return it, it will look like a fully functioning phone, with just a radio that happened to crap-out.
namebrandon said:
Yes, there's really no fixing it. To fix the FC issues you need to get to the OS to do a privacy wipe, or wipe /dbdata from the shell. I would start with restoring everything from the Odin post to get everything back to stock. At least when you go to return it, it will look like a fully functioning phone, with just a radio that happened to crap-out.
Click to expand...
Click to collapse
yep i flashed something to the phone part of my phone too. no signal and no baseband version. took it to verizon and they said since i didnt get it from them, they cant relplace it. samsung said that i hafta mail it in to be repaired. freakin gay. if they dont fix it, its not much a problem for me cause my contract expires next month so ill make a new one and get the same phone. until then im on my sch-u740 lol
hopefully some baseband files get leaked so those of us who did this can fix it.
This has scared me from using odin behond installing CWM, i hope froyo wont crap anything with voodoo.
em.Tea said:
yep i flashed something to the phone part of my phone too. no signal and no baseband version. took it to verizon and they said since i didnt get it from them, they cant relplace it. samsung said that i hafta mail it in to be repaired. freakin gay. if they dont fix it, its not much a problem for me cause my contract expires next month so ill make a new one and get the same phone. until then im on my sch-u740 lol
hopefully some baseband files get leaked so those of us who did this can fix it.
Click to expand...
Click to collapse
so there is no way to fix this at the moment?
lucious584 said:
so there is no way to fix this at the moment?
Click to expand...
Click to collapse
nope. unless someone somewhere releases the complete baseband file, and we flash that. the only thing we have close to that is the modem update which is just an update to an existing modem.
btw random question that might save us,
if someone skilled pulls SCH-I500_OpenSource.zip from opensource.samsung.com, maybe theres a baseband file there somewhere that just needs to be built? idk just a desperate thought
em.Tea said:
nope. unless someone somewhere releases the complete baseband file, and we flash that. the only thing we have close to that is the modem update which is just an update to an existing modem.
btw random question that might save us,
if someone skilled pulls SCH-I500_OpenSource.zip from opensource.samsung.com, maybe theres a baseband file there somewhere that just needs to be built? idk just a desperate thought
Click to expand...
Click to collapse
yeah i fixed my problem i just did a nand restore. Fixed it right up
lucious584 said:
yeah i fixed my problem i just did a nand restore. Fixed it right up
Click to expand...
Click to collapse
really? that didnt work for me
em.Tea said:
really? that didnt work for me
Click to expand...
Click to collapse
He was talking about some other problem.. There's no way to fix the modem.bin file issue at this point. It's been a problem since the device was released, the only fix I can see in our future is an official firmware release from Samsung.
namebrandon said:
He was talking about some other problem.. There's no way to fix the modem.bin file issue at this point. It's been a problem since the device was released, the only fix I can see in our future is an official firmware release from Samsung.
Click to expand...
Click to collapse
Yeah different problem. I found out i did have cell service but it took forever for the phone to find it. It took about 30-40 minutes.
namebrandon said:
He was talking about some other problem.. There's no way to fix the modem.bin file issue at this point. It's been a problem since the device was released, the only fix I can see in our future is an official firmware release from Samsung.
Click to expand...
Click to collapse
Yeah lets not start breath holding
For that
Sent from my 1.2Ghz voodoo fascinate
I don't have a baseband file but i may have a fix for this. I just need to know if you are able to boot into CWM.
Related
So before anything this is what I have.
SPL: Danger SPL
MOD:Cyanogen 4.0.4
RADIO: latest
THEME: CyanogenMod-4.0.4-CustomV7 by: Z҉A҉L҉G҉O
So what happened was after I installed this theme everything was running smoothly. My phone was low on battery so I pluged in my Charger. After being on the phone while charging for 30 - 60 minutes my touch stopped working, so I turned it off and on thinking it'll fix the problem and it didn't.
I leave it alone hoping the touch will comeback the the next morning and it didn't. So I wiped and reinstalled CyanogenMOD 4.0.4 hoping that'll do the trick and it juat made things worse.
Now I'm stuck a the "Tap the Android Screen To Begin" and I can't tap it because my touch isn't working.
Is there any way to fix this or just skip that screen?
I need to ge4t back to my gf or all hell is going to break loose.
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
lbcoder said:
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
Click to expand...
Click to collapse
i agree if a reflash didnt work your g1 needs to go under the knife
JJbdoggg said:
i agree if a reflash didnt work your g1 needs to go under the knife
Click to expand...
Click to collapse
He never said it was a "G1"...
lbcoder said:
You could restore your nandroid backup (you have one, dont you?) to get past the tap-the-android screen, or USB/adb kill the process.
Sounds like your digitizer is dead or disconnected. You might need to perform surgery.
Click to expand...
Click to collapse
No I don't, it would always say error when I tried that.
and how do I kill the process?
Thanks in Adavance if you teach me how.
Is your current issue related to your little trick?
http://forum.xda-developers.com/showthread.php?t=564592
marlopainter said:
Is your current issue related to your little trick?
http://forum.xda-developers.com/showthread.php?t=564592
Click to expand...
Click to collapse
No way!
This happened out of know where haha.
I think I'm going to just try and install cupcake 1.5 if I can find it.
AustinAce said:
No way!
This happened out of know where haha.
I think I'm going to just try and install cupcake 1.5 if I can find it.
Click to expand...
Click to collapse
Anytime you put a device in a freeze, or fridge, there will be condensation on the device. It will then create rust, or short things out. So it could 100% be because of your little "trick".
fenixnr said:
Anytime you put a device in a freeze, or fridge, there will be condensation on the device. It will then create rust, or short things out. So it could 100% be because of your little "trick".
Click to expand...
Click to collapse
Exactly, why would you think it's a good idea to put your phone in the fridge?!
THIS ENTIRE THING HAPPENED BEFORE I PUT MY PHONE IN THE FRIDGE.
Can someone just help me skip the initial process, or just teach me how change the Cyanogen image at the beginning to the original android image.
stop!!! i had this issue were you using a custom user.conf?
i messed up something on mine and phone would lock up nothing at all would happen i was cm 4.11.1 but i had just switch from xrom so went back to and went away but it bothered me so i rent back to rc29 then had more issues up graded to cupcake did one click root and all is good.
jmon777 said:
stop!!! i had this issue were you using a custom user.conf?
i messed up something on mine and phone would lock up nothing at all would happen i was cm 4.11.1 but i had just switch from xrom so went back to and went away but it bothered me so i rent back to rc29 then had more issues up graded to cupcake did one click root and all is good.
Click to expand...
Click to collapse
I kinda don't know what that is.
from the beginning:
I had the hard SPL and wanted the custom V7 them cyan 4.0.4 so I installed Danger.
Then installed the theme, and once I plugged my charger in my touch stopped working so I tried turning it off and on to fix it and it still wasn't working.
So i tried to wipe and reinstall 4.0.4 and got stuck into "tap android screen"
Now I'm back to the hard SPL but I still get stuck at the beginning.
I'm going to send it in, because I think it's a hardware issue not a software issue.
user.conf and userinit.sh and files you push to your ext to tell the ROM what CompCache/Swap settings to use. If you don't know what it is then it's clearly not causing the problem.
So I should jusr send it in?
AustinAce said:
So I should jusr send it in?
Click to expand...
Click to collapse
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
AdrianK said:
user.conf and userinit.sh and files you push to your ext to tell the ROM what CompCache/Swap settings to use. If you don't know what it is then it's clearly not causing the problem.
Click to expand...
Click to collapse
you can also edit cpu speeds as well has some other things. but your right mainly used for swap settings.
jmon777 said:
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
Click to expand...
Click to collapse
I flashed back to the rc29
And when I tried flasjing cupcake it said something about no signatures error
jmon777 said:
if i was you i would flash back to rc29 the flash back up to stock cupcake. and see if that helps because you should unroot before you send it in. hope this helps
Click to expand...
Click to collapse
I flashed back to the original radio
And when I tried flasjing cupcake it said something about no signatures error
AustinAce said:
I flashed back to the original radio
And when I tried flasjing cupcake it said something about no signatures error
Click to expand...
Click to collapse
Are you useing the one that came from tmobile? If its hard to find there a guy that has I like in his sig ill try and find it for u if u can't.
Hello. Please help me. my phone can not use the rom manage. I have used one once, but can not be used again. when I turn on the program, still connected 3g/wifi but nothing more happened at all. I have copied the program into the correct directory. My phone rooted.This phenomenon occurs after I Flast 2.1
What doesnt work? Does it not install? Why are you copying the app at all? Why not install from Market?
I installed the application from Market but I can not use the rom manage.
I don't know!
duongthanhcong said:
I installed the application from Market but I can not use the rom manage.
I don't know!
Click to expand...
Click to collapse
Rom Manager*
You have to be rooted to use it.
You can't expect people to help you if you don't tell them the problem.
So its installed, did you flash the clockworkmod? Should be the top most option.
dcontrol said:
You can't expect people to help you if you don't tell them the problem.
So its installed, did you flash the clockworkmod? Should be the top most option.
Click to expand...
Click to collapse
Also, did you download it from the market, or did you steal the pro version from online? I am asking because you said "I copied it to the right directory"
Maybe I understand his/her problem. Rooted, installed RM but cannot install Clockwork?
Few options here, search for the standalone update.zip with Clockwork and do it that way OR wait a few hours and try again.
The 1st choice I had to do once because RM wasn't liking my phone and the 2nd choice sometimes the server is down.
First, my phone t959 rom UVJI6 normal. Then my rom to version 2.2 T959UVJFD. I do not feel satisfied so I returned to the Odin 2.1.
My phone has a normal root and fix lag.
but then, I could not manage to use the rom again.
Sorry for my english level is limited. I'm from Vietnam
blizzard1017 said:
Maybe I understand his/her problem. Rooted, installed RM but cannot install Clockwork?
.
Click to expand...
Click to collapse
Yes. this is my problem. How do I do now?
Thanks!
If youre trying to flash another rom you need to disable the lagfix first.
Sent from my SGH-T959 using XDA App
My assumption is you have OCLF, try removing it then giving it a go.
Google a clockwork update zip that is pushable with ODIN, I found one the other day. I MAY have it still but I am not sure and I honestly have no clue where I found it, wasn't xda I am about 90% sure. It is not really a solid fix but will get you to where you have CWM. Rom Manager will not recognize you have it installed but when you go to enter recovery mode it will enter into CWM.
Did you by chance also flash a custom kernal? When I tested out a few I noticed my phone did the same thing, my knowledge currently doesn't expand far enough to know if they can even be related though. I am still learning a lot myself.
blizzard1017 said:
My assumption is you have OCLF, try removing it then giving it a go.
Google a clockwork update zip that is pushable with ODIN, I found one the other day. I MAY have it still but I am not sure and I honestly have no clue where I found it, wasn't xda I am about 90% sure. It is not really a solid fix but will get you to where you have CWM. Rom Manager will not recognize you have it installed but when you go to enter recovery mode it will enter into CWM.
Did you by chance also flash a custom kernal? When I tested out a few I noticed my phone did the same thing, my knowledge currently doesn't expand far enough to know if they can even be related though. I am still learning a lot myself.
Click to expand...
Click to collapse
(See attachment)
Master™ said:
(See attachment)
Click to expand...
Click to collapse
Always living up to your name...
I had mine fixed up through some trial and error hopefully this gets the OP in the right direction.
Oh ****, think I bricked the phone!
I rooted the phone yesterday and put bonsai4all rom on it...
Then i had a problem where the apps would delete themselves after a reboot... After having the non apps after reboot problem, I did a reinstall and then i started getting random reboots about every 3 mins.
Did another install, but this time, I also formatted system besides cache and data...
Now no matter what I do, I'm stuck at the sanding screen. I tried another wipe of all items and a restore back to fresh root. No go...
Please help
You are not bricked
You need to use Odin to get your phone back to a usable state.
Once you use odin to go back to stock it will be fine ,also what are you running ext4 rfs.
just look in the threads and you will find the tutorial for going back to a stock rom.
Can ya link me to a recovery via Odin thread?
I'm at work on the iPad so it's hard to search around...
I'll have to wait til I get home to use Odin.
No ext4 afaik, I didn't touch any of that stuff
Thx bud..
Ps I do have access to clockwork still if that helps
razorseal said:
Oh ****, think I bricked the phone!
I rooted the phone yesterday and put bonsai4all rom on it...
Then i had a problem where the apps would delete themselves after a reboot... After having the non apps after reboot problem, I did a reinstall and then i started getting random reboots about every 3 mins.
Did another install, but this time, I also formatted system besides cache and data...
Now no matter what I do, I'm stuck at the sanding screen. I tried another wipe of all items and a restore back to fresh root. No go...
Please help
Click to expand...
Click to collapse
Look at my tutorial by clicking my name, clicking threads and choose my guide. When you are in my guide, follow the odin part.
Sent from my SPH-D700 using XDA App
Ok got it. I'll do itnwhen I get home...
I suppose I'll loose root when I do that?
I really hope thatll fix it!
Is this something I can't fix via cwm?
razorseal said:
Ok got it. I'll do itnwhen I get home...
I suppose I'll loose root when I do that?
I really hope thatll fix it!
Is this something I can't fix via cwm?
Click to expand...
Click to collapse
Yes, it will, and yes. This isn't an attack of the op but this thread is more evidence we need a sticky guide of how to deal with this.
Sent from my ext4 Epic 4G running Bonsai4all 1.1.3!
Not trying to steer a user away from XDA, but I wanted to read marcusant's threads and could not get them to open for me.
And as to the suggestion for stickies, I read both this and Android Central. There forums are not as technical, so the combo is great.
But they do have easy to read and use stickies at the beginning of the Epic Forums for help which eliminates the need to try to search through the forums for what I consider an emergency help need from a panicked member (can you tell I have been there from that statement!!!)
Hi, I got my Nexus 7 yesterday. Everytime I leave it in sleep mode for more than 10 minutes it shuts down and i need to hard reboot. I've read somewhere that its possibly Sleep of Death. I tried shutting wifi of during sleep, installed an auto airplane mode app, reset to factory settings about 5 times but nothing seems to help. I run stock rom, not rooted. Do you think i should return it or is there a possible sollution? Greatings
I'd return it
What build number are you in? Settings/about tablet maybe its somthing to do with JR3O0S?
Sent from my Nexus 7 using Tapatalk 2
leelaa said:
What build number are you in? Settings/about tablet maybe its somthing to do with JR3O0S?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Build number is JRO03D
Goldcell said:
Build number is JRO03D
Click to expand...
Click to collapse
I'm the same build JRO03D and I can say that mine dies sometimes after I press the power button to turn the screen off.
I've noticed it happens when I'm reading a pdf book on adobe reader and when I turn my screen off it just doesn't turn on and I have to hold it so it resets and turns on.
Is this a bad build number? The one that ends with a D?
kris4o2 said:
I'm the same build JRO03D and I can say that mine dies sometimes after I press the power button to turn the screen off.
I've noticed it happens when I'm reading a pdf book on adobe reader and when I turn my screen off it just doesn't turn on and I have to hold it so it resets and turns on.
Is this a bad build number? The one that ends with a D?
Click to expand...
Click to collapse
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Silentbtdeadly said:
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Click to expand...
Click to collapse
I'm stock. I've never used a custom ROM or rooted my devices.
Silentbtdeadly said:
Are you guys using a custom rom, or stock? I am showing JRO03D (MoDaCo Custom Rom Jr7) and have no issues.. so either his rom fixed the issue of the build, or perhaps the update you received is bad?
I asked somewhere else the best way to go back to stock, a way that re-writes the partitions.. like flashing a RUU with HTC, or using Odin on Samsung.. but never got an answer. I would recommend you find a way to get back to stock firmware, then allow it to update again, or update it yourself- or get a custom rom..
And what hardware version are you on? Mine is C80.. no issues whatsoever.
Click to expand...
Click to collapse
I'm running the stock rom from google. I don't know what hardware version I'm on. Thanks for the replies so far!
If the device is otherwise perfect and free of any defects, I might take a stab at trying to fix it by wiping it and reflashing the stock Image. If you can't get it to work you can always return it then.
Goldcell said:
I'm running the stock rom from google. I don't know what hardware version I'm on. Thanks for the replies so far!
Click to expand...
Click to collapse
The first few letters on the sticker on the back of the tablet, at the bottom, will tell you the hardware version..
And you have a choice, if you just got it and can return it, it is unlikely you will have the issue with a new one.. if you can't, you may want to figure out how to flash a stock firmware, as I have a feeling the OTA update may have went wrong. Resetting your tablet(factory reset) just deletes your /data partition, the system partition is not rewritten.. so if there was something wrong with the update in the system files, that won't help.
I am pretty damn sure it is likely kernel related, yet another option to look into.. the nook color(I used to use) has that issue, so it is sad to hear anyone hear have that issue too.
If you are willing to root, you may want to try increasing the minimum clock speed just one step, or if you have undervolted(which I don't think you've said) you may want to raise the voltage or allow stock voltage, as that can also be the issue.
irishrally said:
If the device is otherwise perfect and free of any defects, I might take a stab at trying to fix it by wiping it and reflashing the stock Image. If you can't get it to work you can always return it then.
Click to expand...
Click to collapse
Is reflashing the stock rom the same as resetting it to factory settings?
Silentbtdeadly said:
The first few letters on the sticker on the back of the tablet, at the bottom, will tell you the hardware version..
And you have a choice, if you just got it and can return it, it is unlikely you will have the issue with a new one.. if you can't, you may want to figure out how to flash a stock firmware, as I have a feeling the OTA update may have went wrong. Resetting your tablet(factory reset) just deletes your /data partition, the system partition is not rewritten.. so if there was something wrong with the update in the system files, that won't help.
I am pretty damn sure it is likely kernel related, yet another option to look into.. the nook color(I used to use) has that issue, so it is sad to hear anyone hear have that issue too.
If you are willing to root, you may want to try increasing the minimum clock speed just one step, or if you have undervolted(which I don't think you've said) you may want to raise the voltage or allow stock voltage, as that can also be the issue.
Click to expand...
Click to collapse
I don't have my box anymore. Is there another way to see what your hardware number is?
kris4o2 said:
I don't have my box anymore. Is there another way to see what your hardware number is?
Click to expand...
Click to collapse
I'm not exactly sure, I know the sticker on the back of the tablet itself, toward the bottom has it.. I'm still somewhat new to this tablet yet.
Goldcell said:
Is reflashing the stock rom the same as resetting it to factory settings?
Click to expand...
Click to collapse
I said in my last post, restoring to factory just deletes the /data partition, and leaves the /system files exactly the same. Reflashing actually overwrites the system files.
I get it occasionally but I'm running a CM nightly and Clemsyns elite kernel so I chalk it up to that.
I've flashed stock rom and several other roms, but it did not help so I've returned it for a new device, i have to wait 3 weeks for a new one . Thanks for the replies!
Okay, so I recently (yesterday) rooted my Note 3, I was running X-Note v7.0 and CWM Based Recovery v6.0.4.5., Samsung Voice was annoying me so I decided to delete it via Root Explorer, it seems it wasn't actually Samsung Voice and upon reset it struggled to boot into the ROM, the background was black, I couldn't access anything but the notification bar.
I was a bit annoyed, but no worries, I'll just re-install X-Note and it'll replace the missing file and I'll be good to go. Wrong. It was exactly the same. So I thought I'll have to wipe and re-install, slightly more annoyed as it's taken me a day to set the device up nicely!
I wiped, re-installed and still, it's the same. I've wiped the data and factory reset five times in a row from recovery, wiped dalvik, formatted, /System, /Data & /Cache separately. Re-installed the ROM again and it still won't work.
It will do the normal long boot, showing the boot animation, then boot into the setup screen, won't let me use Wi-FI, so I skip that and all Google logins etc etc, load the new ROM and it's just black, again.
So now I am soft bricked, I can't wipe, I can't re-install, I cant't lay my stock backup over the ROM. I'm currently downloading Omega v6.0 to see if another ROM will fix it.
Any advice? I'm fast running out of ideas! Is there any way to totally format the internal memory like the Galaxy Nexus had? That way I can do a complete fresh install which should fix my issue. :crying:
Flash stock
Root
Flassh cwm
Flash xnote
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Killberty said:
Flash stock
Root
Flassh cwm
Flash xnote
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Click to expand...
Click to collapse
Do you know where I can find the stock UK Vodafone ROM? I haven't seen a repository.
Kalavere said:
Do you know where I can find the stock UK Vodafone ROM? I haven't seen a repository.
Click to expand...
Click to collapse
Sammobile, but if you want a faster download grab one from dejmbey's thread in the dev section (pre-rooted)
radicalisto said:
Sammobile, but if you want a faster download grab one from dejmbey's thread in the dev section (pre-rooted)
Click to expand...
Click to collapse
I've found the thread here, can I install any on a UK Vodafone N3? Is the first one okay to flash?
Okay, so I have no baseband or IME it seems, I've found this thread and I think it will solve my problem. I am getting zero reception and my phone is rebooting so fast I can barely get into the settings menu.
Kalavere said:
Okay, so I have no baseband or IME it seems, I've found this thread and I think it will solve my problem. I am getting zero reception and my phone is rebooting so fast I can barely get into the settings menu.
Click to expand...
Click to collapse
Here flash this HERE this will fix your bootloop, efs corrupted, it happens sometimes, so don't panic too much!!
radicalisto said:
Here flash this HERE this will fix your bootloop, efs corrupted, it happens sometimes, so don't panic too much!!
Click to expand...
Click to collapse
Radicalisto, you are my new best friend! :victory:
Okay, so the ROM seems stable enough. I have data service as I'm writing this through the network, but, I can't receive texts or calls, I can call and send texts out, but I can't receive any in return.
Any ideas?
Kalavere said:
Okay, so the ROM seems stable enough. I have data service as I'm writing this through the network, but, I can't receive texts or calls, I can call and send texts out, but I can't receive any in return.
Any ideas?
Click to expand...
Click to collapse
Double check your APN regarding the txts - calls however, you may need to fresh flash as it may have caused some coruption - did you dirty flash? if so, probably your issue.
radicalisto said:
Double check your APN regarding the txts - calls however, you may need to fresh flash as it may have caused some coruption - did you dirty flash? if so, probably your issue.
Click to expand...
Click to collapse
It was a clean flash, which wasn't great. So I restored an older backup which was also crap, so I dirty flashed over it and I've got some call and texts received but it keeps dropping to one bar of HSDPA and then dropping out completely.
Regarding the APN, I'm on stock Vodafone contract. I've not looked into changing it. It all seems in order.
Kalavere said:
It was a clean flash, which wasn't great. So I restored an older backup which was also crap, so I dirty flashed over it and I've got some call and texts received but it keeps dropping to one bar of HSDPA and then dropping out completely.
Regarding the APN, I'm on stock Vodafone contract. I've not looked into changing it. It all seems in order.
Click to expand...
Click to collapse
It could be a modem/radio isssue then - I'm not 100% on that subject and would hate to hazard a guess on how to fix, as they can brick your device if you mess up. Safer to see if anyone else chimes in mate, I wouldn't wanna risk telling you something that may ruin your device
I'm sure you'll get sorted though :good:
radicalisto said:
It could be a modem/radio isssue then - I'm not 100% on that subject and would hate to hazard a guess on how to fix, as they can brick your device if you mess up. Safer to see if anyone else chimes in mate, I wouldn't wanna risk telling you something that may ruin your device
I'm sure you'll get sorted though :good:
Click to expand...
Click to collapse
I've flashed many radios via ADB before, it's no worse than flashing a ROM. Although I doubt it's as easy on a frigging Samsung phone!
I can't see how the radio got messed up though, I'll have to have a look through the dev section for updated radios.
It seems of all the days for Vodafone to have a bad signal day, yesterday was it. After getting into work this morning a couple of work colleagues also struggled to send and receive texts/calls. I text 'web' to 40127 on Vodafone UK to get the correct APN settings delivered to my phone regardless and I'll seems well except a double boot when rebooting or cold booting the phone, but I can live with that.
Kalavere said:
It seems of all the days for Vodafone to have a bad signal day, yesterday was it. After getting into work this morning a couple of work colleagues also struggled to send and receive texts/calls. I text 'web' to 40127 on Vodafone UK to get the correct APN settings delivered to my phone regardless and I'll seems well except a double boot when rebooting or cold booting the phone, but I can love with that.
Click to expand...
Click to collapse
Ahahaha bloody typical eh! - Least you're sorted man :good:
radicalisto said:
Ahahaha bloody typical eh! - Least you're sorted man :good:
Click to expand...
Click to collapse
I walked into Carphone Warehouse yesterday in a strop and nearly bought a Nexus 5 instead, if they'd have had the 32gb version I'd be messaging on that right now. Good job they didn't have it in stock, haha.
Thanks again Radicalisto. :victory:
Lmao! - No problem man