So I found my old s2 and when I turned it on it always boots to safe mode where nothing comes up only screen with status bar and absolutely nothing else. Volume up works only when holding power button and volume down isn't working at all even in recovery so I am unable to get it into download mode or navigate recovery to try factory reset. Is it a lost cause? Or any ideas to fix?
Sent from my XT894 using Tapatalk
rruleford said:
So I found my old s2 and when I turned it on it always boots to safe mode where nothing comes up only screen with status bar and absolutely nothing else. Volume up works only when holding power button and volume down isn't working at all even in recovery so I am unable to get it into download mode or navigate recovery to try factory reset. Is it a lost cause? Or any ideas to fix?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Nope, your phone is fine. Your volume button is stuck, which makes you boot into safe mode.
Open up your phone (if comfortable) and gently wipe the switch for any debris present.
Will try. Thanks
Sent from my XT894 using Tapatalk
sagirfahmid3 said:
Nope, your phone is fine. Your volume button is stuck, which makes you boot into safe mode.
Open up your phone (if comfortable) and gently wipe the switch for any debris present.
Click to expand...
Click to collapse
I was kinda weary on taking apart since its still insured but it was a lot simpler than I had anticipated and wiped it down with alcohol pad and sure enough it worked like a charm. I was then faced with android.acore crashing but since I can now navigate recovery just did hard reset and back to normal. Any advice on best ROM and kernel combo and best way to flash? Thanks again
Sent from my XT894 using Tapatalk
Personally, I like the Hellybean 4.2.2 ROM. It has excellent performance, overclocked GPU, init.d support, overclocking/volting support, and a sick dark theme. (Don't go with the 4.3 Hellybean, it has memory leaks). I'm pretty sure there is a Hellybean 4.4 in beta at the moment, you can check that out if you wish.
sagirfahmid3 said:
Personally, I like the Hellybean 4.2.2 ROM. It has excellent performance, overclocked GPU, init.d support, overclocking/volting support, and a sick dark theme. (Don't go with the 4.3 Hellybean, it has memory leaks). I'm pretty sure there is a Hellybean 4.4 in beta at the moment, you can check that out if you wish.
Click to expand...
Click to collapse
well so heres what i ran into. it wouldnt read my tmobile sim card and just had a circle with slash through it in the notification bar where signal should be and in settings its unknow baseband and imei and the same issue others have came across. tries gs2 repair from market and no go so i odined jb firmware from ics and now it just reboots while upgrading android. :-/ hoping its just corrupt download so redownloading it from another source and will try but my question is how i can fix the not reading sim issue. thanks ahead of time for any help
rruleford said:
well so heres what i ran into. it wouldnt read my tmobile sim card and just had a circle with slash through it in the notification bar where signal should be and in settings its unknow baseband and imei and the same issue others have came across. tries gs2 repair from market and no go so i odined jb firmware from ics and now it just reboots while upgrading android. :-/ hoping its just corrupt download so redownloading it from another source and will try but my question is how i can fix the not reading sim issue. thanks ahead of time for any help
Click to expand...
Click to collapse
For CM10 and abovre, the minimum version radio firmware that you need is UVMC6. If you do not have that installed already, baseband will show up as unknown. Your SIM card is probably not being recognized because of this.
Search for the UVMC6 zip and flash it FIRST in your recovery (CWM,TWRP), before you install any ROM.
sagirfahmid3 said:
For CM10 and abovre, the minimum version radio firmware that you need is UVMC6. If you do not have that installed already, baseband will show up as unknown. Your SIM card is probably not being recognized because of this.
Search for the UVMC6 zip and flash it FIRST in your recovery (CWM,TWRP), before you install any ROM.
Click to expand...
Click to collapse
iam completely stock.
rruleford said:
iam completely stock.
Click to expand...
Click to collapse
Well then, install CWM or TWRP via ODIN, then install the UVMC6 radio zip.
Most likely, your current radio firmware is corrupted.
my issue with this is as follows. i can only odin into stock ICS any other attempt to odin jb or flash custom ROM on it results in constant rebooting during "android is upgrading" upon first boot... wipes have not alleviated this issue. on stock ICS i get a circle with a slash through it no baseband or imei. have flashed multiple radios and they dont seem to stick at all. the one thing i havent tried is flashing an ICS rom like cm9 or such and flashing the radio to see if itll stick that way. so i guess my question is is there a way to fix this issue or could the radio be fried?
Try using Odin 3.0.4. Only version I had luck with flashing stock jelly bean. Before you Odin tho....use the 2 infamous wipes. Cache one and superwipe one. Found in dev section.
Give that a go.
Sent from my Moto X cellular telephone...
---------- Post added at 06:10 PM ---------- Previous post was at 06:09 PM ----------
You could also try telus or tmobile stocks.
Sent from my Moto X cellular telephone...
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
Remember no matter what you do.....to check your apn settings after. If they are right...you should get a signal.
Sent from my Moto X cellular telephone...
Also, could you please check if the /efs partition is intact?
That is where things like the IMEI and MAC address, etc, are stored.
Boot to recovery;
mount /efs;
Open a terminal:
adb shell
# cd /efs
# ls -a >> /sdcard/efscontents.txt
# exit
adb pull /sdcard/efscontents.txt
Paste the file here so I can compare it to my /efs.
kj2112 said:
Try using Odin 3.0.4. Only version I had luck with flashing stock jelly bean. Before you Odin tho....use the 2 infamous wipes. Cache one and superwipe one. Found in dev section.
Give that a go.
Sent from my Moto X cellular telephone...
---------- Post added at 06:10 PM ---------- Previous post was at 06:09 PM ----------
You could also try telus or tmobile stocks.
Sent from my Moto X cellular telephone...
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
Remember no matter what you do.....to check your apn settings after. If they are right...you should get a signal.
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
sagirfahmid3 said:
Also, could you please check if the /efs partition is intact?
That is where things like the IMEI and MAC address, etc, are stored.
Boot to recovery;
mount /efs;
Open a terminal:
adb shell
# cd /efs
# ls -a >> /sdcard/efscontents.txt
# exit
adb pull /sdcard/efscontents.txt
Paste the file here so I can compare it to my /efs.
Click to expand...
Click to collapse
Will definitely do once I have a few minutes to tinker. Thank you again for your help
Sent from my XT894 using Tapatalk
sagirfahmid3 said:
Also, could you please check if the /efs partition is intact?
That is where things like the IMEI and MAC address, etc, are stored.
Boot to recovery;
mount /efs;
Open a terminal:
adb shell
# cd /efs
# ls -a >> /sdcard/efscontents.txt
# exit
adb pull /sdcard/efscontents.txt
Paste the file here so I can compare it to my /efs.
Click to expand...
Click to collapse
Adb shell returns Device not found
Sent from my XT894 using Tapatalk
Did you flash the latest TWRP (I believe 2.6.3.1) via Odin or Heimdall? If not, do that first.
Unless your USB port is broken on the phone, it should work and get recognized.
Have you used adb before on your phone?
sagirfahmid3 said:
Did you flash the latest TWRP (I believe 2.6.3.1) via Odin or Heimdall? If not, do that first.
Unless your USB port is broken on the phone, it should work and get recognized.
Have you used adb before on your phone?
Click to expand...
Click to collapse
Using cwm. Will try twrp when I get a few to flash cuz I do know that allows u to use terminal within recovery unlike cwm where I had to reboot into ROM and use terminal emulator.. I haven't messed with adb a lot on the phone.
Sent from my XT894 using Tapatalk
Well it seems as though it was just dying. Went to Odin back to ICS again and now it doesn't come on at all. :-/
Sent from my XT894 using Tapatalk
rruleford said:
Well it seems as though it was just dying. Went to Odin back to ICS again and now it doesn't come on at all. :-/
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
If it is dying, and the screen and other components are in working condition, you could sell it on eBay for around $85-90.
The SGH-I727 (Galaxy S2 Skyrocket) has similar specs to the T989, and you can find those being sold on eBay for around $100 to $150. I am not sure exactly why it costs lesser than the T989, but it is (and I bought one for my dad for $133 USD). Both have the same specs, same processor, GPU, storage, etc.
sagirfahmid3 said:
If it is dying, and the screen and other components are in working condition, you could sell it on eBay for around $85-90.
The SGH-I727 (Galaxy S2 Skyrocket) has similar specs to the T989, and you can find those being sold on eBay for around $100 to $150. I am not sure exactly why it costs lesser than the T989, but it is (and I bought one for my dad for $133 USD). Both have the same specs, same processor, GPU, storage, etc.
Click to expand...
Click to collapse
Ended up buying a new galaxy note i717 brand new for 200$ I was actually thinking of posting it on eBay. Everything is flawless except seems the motherboard fried but everything else was working. Since screen and case are flawless was thinking of putting it for 100$ too much you think?
Sent from my XT894 using Tapatalk
rruleford said:
Ended up buying a new galaxy note i717 brand new for 200$ I was actually thinking of posting it on eBay. Everything is flawless except seems the motherboard fried but everything else was working. Since screen and case are flawless was thinking of putting it for 100$ too much you think?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
$100 seems a fair price if you're including the case. Go for it.
Related
Wasn't paying attention when updating my ROM for a AT&T GS3 and accidentally tried to install the Verizon Equivalent. Original ATT Rom was AOKP Jelly bean.
Anybody have any ideas on what to do? The phone doesn't seem to be able to enter recovery mode, but can enter "Downloading... Do not turn off target !!"
FML
Odin back a stock firmware and see if that works. Look in the stickies in development section.
Sent from my SAMSUNG-SGH-I747 using xda premium
Yeah, if you get the "downloading" then you're golden. Just use Odin to restore to stock.
http://forum.xda-developers.com/showthread.php?t=1722686
---------- Post added at 08:27 PM ---------- Previous post was at 08:21 PM ----------
And here is the stock image you would flash to your phone using ODIN:
http://www.samsdroid.com/2012/07/i747ucalem-android-404-usa-at-stock-rom.html
Or at least it's the one I use for my ATT SIII.
Filename is: I747UCALEM_I747ATTALEM_I747UCALEM_HOME.tar.md5
Thanks guys. I started getting worried when the new version of Odin was not connecting with my GS3. Luckily, the older version on my computer synced right up and am going back to stock.
Phew!
KTownGT said:
Thanks guys. I started getting worried when the new version of Odin was not connecting with my GS3. Luckily, the older version on my computer synced right up and am going back to stock.
Phew!
Click to expand...
Click to collapse
Good thing it seems like the architecture of the US GS3s is similar enough that flashing another carrier's ROM won't result in a nice hard brick that requires JTAG/warranty fix.
KTownGT said:
Thanks guys. I started getting worried when the new version of Odin was not connecting with my GS3. Luckily, the older version on my computer synced right up and am going back to stock.
Phew!
Click to expand...
Click to collapse
Just becareful next time bro....not alway lucky like this....
Hello guys, I'm pretty new to cellphone ROM flashing and modifying.
I successfully flashed the Jedi X7.2 on to my Mobilicity Note 2 T889V, and with a little effort I even flashed the Rogers modem on to it and fully enabled 4G/LTE service since I use Fido, they pretty much share the same frequency.
Then I tried the Bullet Kernel 1.9.01b made by cmenard on top of the Jedi x7.2, which then I lost my data, no 2G, 3G, 4G at all.
So I went ahead and tried to flash back to Jedi with all the wipe data/factory restore and everything, still no luck.
I also formatted the entire sdcard directory, trying to start from fresh, with some other types of ROMs such as MyRom and so on. Now my phone even keeps restarting every minute or so.
After a while I started to become frustrated, it was perfect if I've stopped when I got the 4G, any suggestions? I really really appreciate any input on this problem. Thanks a ton
Deleted
pegapega02 said:
It hapen to me as well what I did to fix it. I wipe everything 3 times and flash tha room an modem and reboot wait 10 minute restar to recovery fix permission restar set up your phone and then you can go back to recovery ad what you are goind to add from the godie bag dont install any kernel or theme they are a new theme on the theme section for this room but if you tried a difrent one this will hapen and always make a back up why dont you tried the new update from tmobile it has multi windows working fine
---------- Post added at 06:19 PM ---------- Previous post was at 06:16 PM ----------
And also most at the time this hapen when you install something that is not supported by the room especially with the themes so be careful with that
Click to expand...
Click to collapse
OMFG, punctuate. My crypto devices can't decipher the longest run-on sentence in history!
To the OP, I would odin the original stock image back onto your phone. Then, update to the latest update via keis or OTA. At this point, you are at least functioning again. THEN, maybe try out Jedi.
Side note, why did you try the new kernal in the first place?
pegapega02 said:
It hapen to me as well what I did to fix it. I wipe everything 3 times and flash tha room an modem and reboot wait 10 minute restar to recovery fix permission restar set up your phone and then you can go back to recovery ad what you are goind to add from the godie bag dont install any kernel or theme they are a new theme on the theme section for this room but if you tried a difrent one this will hapen and always make a back up why dont you tried the new update from tmobile it has multi windows working fine
---------- Post added at 06:19 PM ---------- Previous post was at 06:16 PM ----------
And also most at the time this hapen when you install something that is not supported by the room especially with the themes so be careful with that
Click to expand...
Click to collapse
Your posts are really really bad. Not to insult you. But ive read some of them and also you give bad advice and frequently dont really know what you are doing yet you give advice to people. ...this is not good.
OP you lost your data possibly because you did not remove the t889 modem from the firmware that you flashed? Does jedi come with the t889 modem....or t889v modem? What about imei number....do you still have that?
Sent from my GT-N7105 using Tapatalk 2
I'm pretty sure that Jedi X has the saber kernal built in...no need to flash a kernel. The developer is packing it with the ROM because it is not ready to be a stand alone kernel in his opinion (last i read anyways)
I'm on Jedi X and I didnt have to do anything to the kernel and my data works fine (minus MMS)
Hes using CANADIAN T889V
dont you think that has something to do with it?
Sent from my GT-N7105 using Tapatalk 2
Thanks guys for the advice. The Jedi was actually working great, and the Bullet kernel is nothing wrong either, it's just the Bullet kernel I added in on top of the Jedi that screw things up.
Mine is the T889V, the Canadian version of T889, so according to some posts the developers made here the only difference is the modem, and that's why the Jedi ROM has a T889V modem patch.
However, as I mentioned, I unlocked the phone and I'm with Fido right now, and Fido uses Rogers' transmitting towers so I flashed the modem of SGH-i317M to get the 4G LTE frequency for Fido and I actually succeeded.
I'll try something out, thanks guys again.
Any other suggestions are very very welcomed!
I got your PM, but this sort of question is better discussed in-thread.
Let's backtrack a little here...
So you've got a T889V flashed with an I317M modem, on Fido, does service work on it currently? What about your IMEI?
Are your drivers correct? You should be seeing one and probably two serial ports appear in the Windows device manager.
Did you try disconnecting and reconnecting the USB cable after changing to DM mode?
Darkshado said:
I got your PM, but this sort of question is better discussed in-thread.
Let's backtrack a little here...
So you've got a T889V flashed with an I317M modem, on Fido, does service work on it currently? What about your IMEI?
Are your drivers correct? You should be seeing one and probably two serial ports appear in the Windows device manager.
Did you try disconnecting and reconnecting the USB cable after changing to DM mode?
Click to expand...
Click to collapse
Thanking for getting back to me, really appreciated.
To answer your questions:
- Yes the I317M Rogers' modem did work until I flashed a custom kernel on top of the Jedi ROM
- After the kernel flashing my mobile data was gone, and the IMEI became 0
- My drivers are the newest samsung 1.5.9.0 USB Driver for Mobile Phones
- Yes I did disconnect the device before changing it to the DM+MODEM+ADB mode.
ashwill said:
Hello guys, I'm pretty new to cellphone ROM flashing and modifying.
I successfully flashed the Jedi X7.2 on to my Mobilicity Note 2 T889V, and with a little effort I even flashed the Rogers modem on to it and fully enabled 4G/LTE service since I use Fido, they pretty much share the same frequency.
Then I tried the Bullet Kernel 1.9.01b made by cmenard on top of the Jedi x7.2, which then I lost my data, no 2G, 3G, 4G at all.
So I went ahead and tried to flash back to Jedi with all the wipe data/factory restore and everything, still no luck.
I also formatted the entire sdcard directory, trying to start from fresh, with some other types of ROMs such as MyRom and so on. Now my phone even keeps restarting every minute or so.
After a while I started to become frustrated, it was perfect if I've stopped when I got the 4G, any suggestions? I really really appreciate any input on this problem. Thanks a ton
Click to expand...
Click to collapse
your issues is running a modem that is not compatible with the modules you flashed when you flashed the kernel.
this is why it is a good idea to just run things that are built for your device and your device only. you might have to odin back to stock to get your device working again. you should check your settings>about device> and see if your IMEI is still there.... i would suggest sticking with t mo builds in the future if you are not quite sure what you are doing. blindly flashing things without doing some careful reading can be a recipe for a bricked device or permanently lost data/device ID
---------- Post added at 02:19 AM ---------- Previous post was at 02:13 AM ----------
ashwill said:
Thanking for getting back to me, really appreciated.
To answer your questions:
- Yes the I317M Rogers' modem did work until I flashed a custom kernel on top of the Jedi ROM
- After the kernel flashing my mobile data was gone, and the IMEI became 0
- My drivers are the newest samsung 1.5.9.0 USB Driver for Mobile Phones
- Yes I did disconnect the device before changing it to the DM+MODEM+ADB mode.
Click to expand...
Click to collapse
never mind... just saw this.
to be honest, that really sucks. not sure what to tell you.
Can you see the serial port show up in Device Manager?
Darkshado said:
Can you see the serial port show up in Device Manager?
Click to expand...
Click to collapse
Yes I can, and it can connect too with QPST, just thar it will show "No Phone" and not be able to read/write anything to the phone.
Try rndis + dm + modem, and make sure Kies isn't interfering?
Beyond that I'm not too sure. What exact drivers load for the ports?
Sent from my SGH-T889V using xda app-developers app
Let me start by saying I've read through several other threads with a similar issue, but they all have a common connectivity problem that I'm NOT experiencing so I thought I'd ask this in a new thread. I was using AOKP build 5, and I decided to try out a more TW stock rom to see how devs have modified it. I chose Intergalactic v 2.8, wiped data/cache and installed like ya do. Almost immediately I got the pop up saying, "Unfortunately, Factory Test has stopped." I didn't think much of it, even though I had never seen it before. I restored my app data via Titanium Backup and starting fiddling with my settings. Made a couple calls, a few texts. Put my phone down to go about my morning. Later when I went to unlock my phone I realized I don't have a lockscreen. Thought that was funny so I went to boot into recovery but punching the power button just turned the phone off; So I investigated and I realize I'm in factory mode. and I can't seem to get out of it. I've tried running the terminal commands to turn it off, but that didn't work. It looks like my ESF folder is empty or doesn't exist.
So here's what I know after all of my research: My IMEI somehow seems to be intact since I can make calls and get on the network, but because my ESF is empty or gone can't turn off factory mode, which is causing all kinds of other buggy issues such as no lockscreen, no power menu, and the annoying Factory Test pop-up. If there is a thread out there that had a similar problem, I apologize that I couldn't find it. is there any way to recover this info, since the IMEI is still intact? Thanks.
Flash a stock rom
Sent from my SGH-I747 using Tapatalk 2
did that, no dice
peneoark said:
Flash a stock rom
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Tried to restore the stock JB with Odin and it didn't fix the problem. I'm attempting to flash the stock ICS, then attempt an OTA update to see if that does the trick. Will keep you posted.
So I flashed ics and then allowed AT&T to push my JB update to me OTA. Still in factory mode. I guess I'll just have to investigate this more thoroughly. I'm using widget locker as a work around for my lockscreen, but still no power menu and the popups are still showing up every now and then. Super annoying, but at least my phone is still functioning. If anyone has any other ideas I'd greatly appreciate it. Thanks.
Sent from my SAMSUNG-SGH-I747 using xda premium
drunkenscholar said:
So I flashed ics and then allowed AT&T to push my JB update to me OTA. Still in factory mode. I guess I'll just have to investigate this more thoroughly. I'm using widget locker as a work around for my lockscreen, but still no power menu and the popups are still showing up every now and then. Super annoying, but at least my phone is still functioning. If anyone has any other ideas I'd greatly appreciate it. Thanks.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Try taking and EFS folder from a stock ROM and push it to your current ROM and see if that helps
DamageSource said:
Try taking and EFS folder from a stock ROM and push it to your current ROM and see if that helps
Click to expand...
Click to collapse
How would I extract it from the EFS folder from the stock image? I figured I would need to do with through ADB, but I have no idea what commands I would have to execute.
http://forum.xda-developers.com/showthread.php?t=1801997
Would this not work for you ?
---------- Post added at 10:05 AM ---------- Previous post was at 09:50 AM ----------
hednik said:
http://forum.xda-developers.com/showthread.php?t=1801997
Would this not work for you ?
Click to expand...
Click to collapse
Is your efs folder completely gone ?
hednik said:
http://forum.xda-developers.com/showthread.php?t=1801997
Would this not work for you ?
---------- Post added at 10:05 AM ---------- Previous post was at 09:50 AM ----------
Is your efs folder completely gone ?
Click to expand...
Click to collapse
I saw this fix, but frankly, I'm skittish to try it as my IMEI is still intact and I'm afraid of making the problem worse. My EFS folder is there, but it's empty.
drunkenscholar said:
I saw this fix, but frankly, I'm skittish to try it as my IMEI is still intact and I'm afraid of making the problem worse. My EFS folder is there, but it's empty.
Click to expand...
Click to collapse
Don't be skittish. It really and truly is the only way to get everything back to how it should be. Ton's of people have tried it and this allows you to push the IMEI back into your phone the way it came from the factory. It's not for spoffing or doing anything illegal.
Now its usually for replacng a lost IMEI from flashing a ROM. Sometimes happens when going from a non-stock type ROM (i.e. CM or AOKP) to stock type ROM (i.e TW)
Search on how to push files with ADB and you should be good to go
BE CAREFUL though and don't skip steps or go fast.
I meant to ask...can you use your phone ? does data work ? Have you tried to get into download mode ?
If you can then download good manager and select reboot into recovery or any other number of apps that let you boot into recovery without having a power menu
hednik said:
Don't be skittish. It really and truly is the only way to get everything back to how it should be. Ton's of people have tried it and this allows you to push the IMEI back into your phone the way it came from the factory. It's not for spoffing or doing anything illegal.
Now its usually for replacng a lost IMEI from flashing a ROM. Sometimes happens when going from a non-stock type ROM (i.e. CM or AOKP) to stock type ROM (i.e TW)
Search on how to push files with ADB and you should be good to go
BE CAREFUL though and don't skip steps or go fast.
I meant to ask...can you use your phone ? does data work ? Have you tried to get into download mode ?
If you can then download good manager and select reboot into recovery or any other number of apps that let you boot into recovery without having a power menu
Click to expand...
Click to collapse
Yeah, the phone works perfectly other than a lack of lock screen, no power menu, and the pop ups that annoyingly show every once in a while. Download mode works, and I pushed stock back to my device using ODIN. It now occurs me me to wonder if I might have had a different result if I had flashed my stock rom using ADB.
drunkenscholar said:
Yeah, the phone works perfectly other than a lack of lock screen, no power menu, and the pop ups that annoyingly show every once in a while. Download mode works, and I pushed stock back to my device using ODIN. It now occurs me me to wonder if I might have had a different result if I had flashed my stock rom using ADB.
Click to expand...
Click to collapse
I hate to ask but did yo factory reset the phone...like in stock recovery ?
drunkenscholar said:
Yeah, the phone works perfectly other than a lack of lock screen, no power menu, and the pop ups that annoyingly show every once in a while. Download mode works, and I pushed stock back to my device using ODIN. It now occurs me me to wonder if I might have had a different result if I had flashed my stock rom using ADB.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1703175
check out post #8
the user restored the backed up EFS folder with Root Explorer and his device is fixed now.
xBeerdroiDx said:
http://forum.xda-developers.com/showthread.php?t=1703175
check out post #8
the user restored the backed up EFS folder with Root Explorer and his device is fixed now.
Click to expand...
Click to collapse
Beer,
I'm not thinking he has a backup of his EFS though
Try his first but this might do the trick as well:
http://forum.xda-developers.com/showthread.php?t=1703175&page=2
post #14
Odia said:
# echo -n ON > /efs/FactoryApp/factorymode
(and yes ON is the correct setting to turn it off)
Click to expand...
Click to collapse
hednik said:
Beer,
I'm not thinking he has a backup of his EFS though
Try his first but this might do the trick as well:
http://forum.xda-developers.com/showthread.php?t=1703175&page=2
post #14
Click to expand...
Click to collapse
you are correct. i looked back over the thread. i had thought he posted something yesterday about having an EFS backup.
your find seems like it should do the trick
hednik said:
I hate to ask but did yo factory reset the phone...like in stock recovery ?
Click to expand...
Click to collapse
Yessir. When the phone booted back up it didn't go through the setup process. Just goes straight to the homescreen. Also when I boot into restore mode I see this under the menu options:
E:failed to mount /efs (Invalid Argument)
E:failed to mount /efs (Invalid Argument)
# MANUAL MODE #
--Applying Multi-CSC...
Applied CSC-code : unknown
Successfully applied multi-CSC.
I tried turning it off with terminal emulator at one point last night, but it didn't seem to work, I THINK because the EFS folder is empty. I'll have to re-root tonight and try it again since I've restored my stock firmware.
It may seem like I'm shooting down every suggestion you guys throw at me, but I really appreciate the input. XDA is a big place and I tried to be very thorough when searcing for a solution before posting this thread, but I'm sure there's something out there I've missed. Thank you for your efforts.
I think I found something that will allow me to restore a generic EFS here:
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
Asked the originator if it will work to restore my files. If so, gonna try it when I get off work tonight.
drunkenscholar said:
I think I found something that will allow me to restore a generic EFS here:
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
Asked the originator if it will work to restore my files. If so, gonna try it when I get off work tonight.
Click to expand...
Click to collapse
Ah exactly what I have been looking for on this one for you. I found a few that explained how to push your old EFS folder with ADB but none about making another. How crazy it was yesterday it popped up on a post. That looks like your best shot as you folder seems to be corrupted and although IMEI is intact you need a new one folder that is intact. Let us know how it turns out
Can you hit me with the stuff you found about pushing it through ADB? My efforts have been less than fruitful on that front. I'd rather be armed with as much information as possible.
drunkenscholar said:
Can you hit me with the stuff you found about pushing it through ADB? My efforts have been less than fruitful on that front. I'd rather be armed with as much information as possible.
Click to expand...
Click to collapse
Here is one I had found earlier:
http://forum.xda-developers.com/showthread.php?t=1169805
xaurion said:
[/COLOR]Problem fixed!! give read write permissions for user/group/others to the keystr file.[/QUOT
Have you looked at this ? (or is this just the same thing as turning it off)
- One more thing, what file explorer are you looking at the efs folder with ?
Click to expand...
Click to collapse
So, I was working with a friends SIII and I read about running reboot nvbackup. Like a dumba$$ I decided to run it on my N900T in terminal and now I'm boot looping. I've Odin'd back to the stock ROM with no resolve. What did I do and how can I fix it?
TIA
re: boot loop
zonly1 said:
So, I was working with a friends SIII and I read about running reboot nvbackup. Like a dumba$$ I decided to run it on my N900T in terminal and now I'm boot looping. I've Odin'd back to the stock ROM with no resolve. What did I do and how can I fix it?
TIA
Click to expand...
Click to collapse
Before you Odin'ed back to stock did you do a full wipe using TWRP/CWM which includes:
"Wipe Data", "Wipe System", "Wipe Cache", "Wipe Dalvik Cache" and last but not least did
you do a full "Factory Reset" in TWRP/CWM ?
After doing all the above your phone should no longer boot loop, what it should do after doing
the all the above is to go into download mode and or recovery mode.
If it boots into download mode then odin flash the official stock rom which must match the specific
model number of your phone. After doing that you should be good to go.
Best place to find and download the official stock rom is at " SamMobile.com ".
The only roms that SamMobile.com has are the official stock odin flash firmwares which
displays exact baseband (model numbers) which needs to match your phone's baseband.
Good luck!
Thanks for the reply. I've done what you have mentioned, but still boot looping. Trying other methods that I've found and will report back unless someone has any other suggestions. Primarily, I'd like to know what the reboot nvbackup actually did.
zonly1 said:
Thanks for the reply. I've done what you have mentioned, but still boot looping. Trying other methods that I've found and will report back unless someone has any other suggestions. Primarily, I'd like to know what the reboot nvbackup actually did.
Click to expand...
Click to collapse
I skimmed through the thread on nvbackup and it seems like you borked your efs/IMEI. Could be wrong, I only scanned the thread... This was made for the S3, why would you do this to your Note 3?? Anyways try this thread here: let me grab it real quick..
Sent from my SM-N900T using Tapatalk 2
---------- Post added at 11:31 AM ---------- Previous post was at 11:19 AM ----------
EDIT:
Could not find the thread but your welcome to try this:
Note* I'm not responsible from this point on for further damage to your device*
-----
Originally Posted by*bakachu*
I fixed my brickloop by doing the following:
(I would backup your efs partition before doing this, just for completeness sake)*
Installed Stock firmware via Odin,*
Installed TWRP 2.6.3.2 via odin, rebooted to recovery
Did an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: Wiped the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12*
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
(the last two commands probably did nothing, but thats what I did anyway)
Did a Factory Reset*
Then... reboot to system
Afterwards, no more boot looping, the phone successfully registered on the mobile network, and my IMEI is there and correct. Seems like the EFS partition can rebuild itself now I guess...
----
Sent from my SM-N900T using Tapatalk 2
lm that guy said:
I skimmed through the thread on nvbackup and it seems like you borked your efs/IMEI. Could be wrong, I only scanned the thread... This was made for the S3, why would you do this to your Note 3?? Anyways try this thread here: let me grab it real quick..
Sent from my SM-N900T using Tapatalk 2
---------- Post added at 11:31 AM ---------- Previous post was at 11:19 AM ----------
EDIT:
Could not find the thread but your welcome to try this:
Note* I'm not responsible from this point on for further damage to your device*
-----
Originally Posted by*bakachu*
I fixed my brickloop by doing the following:
(I would backup your efs partition before doing this, just for completeness sake)*
Installed Stock firmware via Odin,*
Installed TWRP 2.6.3.2 via odin, rebooted to recovery
Did an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: Wiped the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12*
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
(the last two commands probably did nothing, but thats what I did anyway)
Did a Factory Reset*
Then... reboot to system
Afterwards, no more boot looping, the phone successfully registered on the mobile network, and my IMEI is there and correct. Seems like the EFS partition can rebuild itself now I guess...
----
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
I did it because I'm a dumba$$...no, really...it seemed innocent enough to me...no files to load, etc. Lesson learned.
Anywho, yes, I've also tried that one too to no avail. Just since it is already borked, I ran the reboot nvrestore and that locked it right up to the Samsung Galaxy Note 3 screen. I then Odin'd back the original factory rom and tried the above steps again. Back to boot looping. I would imagine there is an answer since I'm able to get into recovery, but I just need that silver bullet.
Thanks for trying though.
zonly1 said:
I did it because I'm a dumba$$...no, really...it seemed innocent enough to me...no files to load, etc. Lesson learned.
Anywho, yes, I've also tried that one too to no avail. Just since it is already borked, I ran the reboot nvrestore and that locked it right up to the Samsung Galaxy Note 3 screen. I then Odin'd back the original factory rom and tried the above steps again. Back to boot looping. I would imagine there is an answer since I'm able to get into recovery, but I just need that silver bullet.
Thanks for trying though.
Click to expand...
Click to collapse
i have the note 3 i odin back to stock got stuck bootloop then i tried to clear everything still not working . also did recovery from back up no good . i also did fresh install via kias samsung desktop software it loaded everything good but was still stuck in bootloop. i did install jedi 3.1 ithink it loaded and booted up after 5 reboots . when it did load it was slow then i checked options and settings and clicked about or status i say imei missing and baseband missing so i have a brick.
MERK77 said:
i have the note 3 i odin back to stock got stuck bootloop then i tried to clear everything still not working . also did recovery from back up no good . i also did fresh install via kias samsung desktop software it loaded everything good but was still stuck in bootloop. i did install jedi 3.1 ithink it loaded and booted up after 5 reboots . when it did load it was slow then i checked options and settings and clicked about or status i say imei missing and baseband missing so i have a brick.
Click to expand...
Click to collapse
You can try here: http://forum.xda-developers.com/showthread.php?t=2471421
I cannot get adb to see my device, but maybe it will help you.
zonly1 said:
You can try here: http://forum.xda-developers.com/showthread.php?t=2471421
I cannot get adb to see my device, but maybe it will help you.
Click to expand...
Click to collapse
You may want to look here too...just found this: http://forum.xda-developers.com/showthread.php?p=46331142
zonly1 said:
You may want to look here too...just found this: http://forum.xda-developers.com/showthread.php?p=46331142
Click to expand...
Click to collapse
Hey zonly1, were you able to fix your note 3? I'm did what you did.
No, I'm still dead in the water.
Sent from my DROID RAZR HD using Tapatalk
Hey guys, I did the same thing on my note 3 and I tried everything to fix it but in the end I was still within my 14 days and I took it to the store I bought it and swapped it out. At this point you have a couple of options, call Tmobile and do a warranty swap or go through samsung directly. If you go through samsung expect to not have your note for about 1-2 weeks.
Sent from my SM-N900T using Tapatalk 2
Did you ever figured out the solution?
Solved
This thread might help. I had the same problem
http://forum.xda-developers.com/showthread.php?t=2657519
Funny, replying to a thread 2 months old...
krelvinaz said:
Funny, replying to a thread 2 months old...
Click to expand...
Click to collapse
Broken note3's aren't funny. Mine was broken for over 6 weeks, I didn't give up, and today I figured out how to fix the FSG partition that Samsung left vulnerable by the toxic "reboot nvbackup" command. Hope one or two of the guys read my fix and get their note3' gowning again
It wasn't meant to be funny as in ha ha, but rather a doubtful funny that anyone in the thread still has this as a problem. They would most likely of had the issue fixed or replaced their phone by now. Going on now more than 60 days is a but long for most here for a working phone.
I do commend you on coming up with a solution, most don't have that kind of patience.
this is no joke as you all have stated, it's an easily caused brick, but it would have equally been as easy to look up if this unfamiliar command (at least to me) would cause a brick/loop. I'm familiar with adb but had no idea that's a problem samsung left. please let me know of a fix or provide me with a device dump for those partitions, I think it's mmcblk0p's 12,13..17,18, thanks in advance
So I've rooted my phones for the last 5 years, nexus 1, droid, rezound, gs4, n5 and then the m8. finally i screwed up, and i was getting bootloops. in my slightly panicked state i managed to wipe the OS completely off of the device.
i can get into fastboot and from there also TWRP recovery. i've read a million threads, adb sideload, One_M8 all in one kit, etc....
I can't figure out how to now simply flash a stock ROM onto my device. can anyone spell it out in a way this idiot can get it? i;ve downloaded a gazillion things. i'm stuck. i had to go pay full retail for a phone because as a realtor i simply can't be without one even for a day. it's my lifeline. i'd like to fix this one so i can return the new one and save $700.
thanks.
When you say you wiped the OS, did you also clear the partitions? Are you booting into recovery by flashing TWRP and then booting into recovery... or are you booting into recovery via "fastboot boot"? If you have partitions still, you can use a USB OTG adapter and memory stick (or just sdcard) to store the firmware.zip file and flash it from TWRP.
IF, on the other hand, you wiped your partition table, you are in a bigger mess. It's possible a RUU can help, but I'm not familiar with them so can't comment beyond suggesting that you look into that more...
In the development section there is a system dump by (Mike1986). If your computer still recognizes your phone, download system dump to computer, copy it to your phone's internal storage, get into twrp and flash.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Tdeljr said:
In the development section there is a system dump by (Mike1986). If your computer still recognizes your phone, download system dump to computer, copy it to your phone's internal storage, get into twrp and flash.
Click to expand...
Click to collapse
How would you go about copying to the phone's internal storage?
After downloading Rom right click on it select cut, go into your phone's storage on computer (as long as computer recognizes phone) find empty space right click and select paste.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Tdeljr said:
After downloading Rom right click on it select cut, go into your phone's storage on computer (as long as computer recognizes phone) find empty space right click and select paste.
Click to expand...
Click to collapse
Please re-read the original post. The phone doesn't boot into android.
garyd9 said:
Please re-read the original post. The phone doesn't boot into android.
Click to expand...
Click to collapse
Well considering your not the original poster, and I've read the original post several times and can't seem to find where it says it doesn't boot into android. I'm just trying to offer whatever help I can.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
There is a DEV RUU out. You can use that. Or if you want ATT, or GPE, find the zips, and use fastboot commands to flash. If the computer can see the phone and you can issue commands, then there is nothing to worry about. Been there done that dozens of times with the M7. After playing with this M8, seems to be the same. Let us know where you are stuck, i.e. don't know the commands, or don't know where to find the zips.
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
Tdeljr said:
Well considering your not the original poster, and I've read the original post several times and can't seem to find where it says it doesn't boot into android. I'm just trying to offer whatever help I can.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
He wiped the OS, which is Android, thus he can't just plug it in and transfer files back and forth anymore.
hack14u said:
There is a DEV RUU out. You can use that. Or if you want ATT, or GPE, find the zips, and use fastboot commands to flash. If the computer can see the phone and you can issue commands, then there is nothing to worry about. Been there done that dozens of times with the M7. After playing with this M8, seems to be the same. Let us know where you are stuck, i.e. don't know the commands, or don't know where to find the zips.
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
He wiped the OS, which is Android, thus he can't just plug it in and transfer files back and forth anymore.
Click to expand...
Click to collapse
That's my bad, didn't put 2 & 2 together. Thanks for explaining.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Surely if you've only deleted the OS just flash a nandroid from the stock backup thread via TWRP?
pixelsquish said:
So I've rooted my phones for the last 5 years, nexus 1, droid, rezound, gs4, n5 and then the m8. finally i screwed up, and i was getting bootloops. in my slightly panicked state i managed to wipe the OS completely off of the device.
i can get into fastboot and from there also TWRP recovery. i've read a million threads, adb sideload, One_M8 all in one kit, etc....
I can't figure out how to now simply flash a stock ROM onto my device. can anyone spell it out in a way this idiot can get it? i;ve downloaded a gazillion things. i'm stuck. i had to go pay full retail for a phone because as a realtor i simply can't be without one even for a day. it's my lifeline. i'd like to fix this one so i can return the new one and save $700.
thanks.
Click to expand...
Click to collapse
Have you got an external sd card? whack it on there using a card reader and flash from external sd
---------- Post added at 11:04 AM ---------- Previous post was at 11:01 AM ----------
If that won't work on TWRP use philz
not sure if i wiped the partitions. don't think so.
i can't transfer files to the device, the pc recognizes it to give fastboot commands via a command prompt, but not as a removable device.
i'll get an sd card on my way home today and try flashing a rom using recovery.
hack14u said:
There is a DEV RUU out. You can use that. Or if you want ATT, or GPE, find the zips, and use fastboot commands to flash. If the computer can see the phone and you can issue commands, then there is nothing to worry about. Been there done that dozens of times with the M7. After playing with this M8, seems to be the same. Let us know where you are stuck, i.e. don't know the commands, or don't know where to find the zips.
---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------
He wiped the OS, which is Android, thus he can't just plug it in and transfer files back and forth anymore.
Click to expand...
Click to collapse
i think i got the right zip. nm not the right one.
If you want, set up a TeamViewer session and I will fix it for you.
My thread is here: http://forum.xda-developers.com/showpost.php?p=43588969
Matt said:
If you want, set up a TeamViewer session and I will fix it for you.
My thread is here: http://forum.xda-developers.com/showpost.php?p=43588969
Click to expand...
Click to collapse
oh pretty cool. i have the sd card now and going to try. otherwise i may take you up on your offer.
anyone have a link to the right ROM zip file to flash for AT&T version phone?
EDiT: NM Found the thread in the Development section. Flashed it. Currently it's booting up, Android is upgrading optimizing all apps.
pixelsquish said:
oh pretty cool. i have the sd card now and going to try. otherwise i may take you up on your offer.
anyone have a link to the right ROM zip file to flash for AT&T version phone?
EDiT: NM Found the thread in the Development section. Flashed it. Currently it's booting up, Android is upgrading optimizing all apps.
Click to expand...
Click to collapse
very strange. after flashing and rebooting, i didn't have a clean install of Android, all my customizations and apps from before were installed. and i got the same random reboots. so all that info was still on the phone. went back into recovery and wiped everything, then re-flashed. now have a fresh clean install of stock 4.4.2
Thanks everyone! i kinda thought the sd card thing would be the easiest but the comments in this thread confirmed it and it worked.
pixelsquish said:
very strange. after flashing and rebooting, i didn't have a clean install of Android, all my customizations and apps from before were installed. and i got the same random reboots. so all that info was still on the phone. went back into recovery and wiped everything, then re-flashed. now have a fresh clean install of stock 4.4.2
Thanks everyone! i kinda thought the sd card thing would be the easiest but the comments in this thread confirmed it and it worked.
Click to expand...
Click to collapse
That's the beauty of the sd card slot mate, i have saved my m8 countless times. i would always make a backup of your phone prior to tinkering but this really helps save ur ass if you forget to backup.
Glad everything is ok and that this simple solution worked :highfive::good: