I noticed that my brother had ICS for his droid razr maxx and so I went about updating my phone so that I could have ICS as well. During the first attempt it downloaded fine, rebooted and started the installation. During the installation though it stopped around 30-40%? ish and rebooted saying the update failed. I have had this problem before and so I thought it was because my phone didn't have some of the applications that It came with from Motorola. I recovered it to my last recovery which I saved with everything still installed but the phone still rooted. The installation didn't work so I figured that I would just factory reset and try it again, thinking the phone would update then.
Phone: Droid razr X912, stock ROM, no root, Superuser is installed but does not work, installed OTA root keeper to check if I had root but didn't work. Bootstrap doesn't work.
Where I am now:
1. Stock ROM
2. factory reset
3. Gingerbread 2.3.6
4. No root and unable to re root
5. Cannot update ICS
Where I am trying to get:
1. Either I would like to get back to one of my recoveries that I made using CMrecovery or
2. Get to ICS.
What I have read so far:
Something about locking the bootloader. Said to use some adb reboot recovery command in a command prompt? I am really new at this so I don't know what this means(should provide somewhat of a idea of how much I know) I can read articles if someone can point me in the right direction
I am unsure what to do in this situation. Thanks.
Edit: Tried Doomlords unrooting script and that didn't work, Says that the phone is in R/O mode most likely (that is my conclusion) from reading a few articles.
Ok...I'm no expert but I can tell you what I would would do and hopefully we can you all fixed up. So you're on stock Gingerbread right? Do you have the stock recovery too or a different one? Anyways try booting into recovery, wipe the cache, do a factory reset/data wipe, clear cache again. Then restart the phone to see if it boots up all good.
Now, do you have the official ICS .211 .zip update file? I'm assuming you do, make sure it's on the "external" SD card. Shut the phone down, and boot back into recovery. Select update.zip from SD card and run the update. Give it plenty of time to run. Sometimes it seems like it is hanging but it's just thinking. Might take in upwards of 10-15 minutes to run through completely so make sure you have a full battery before beginning.
Mine did hang and installation failed. This is actually common when doing a forced update in recovery. Don't worry, all you have to do is force shut it down and repeat the above steps and run the install again. It "should" install fine on the second try, mine did and many others on here too. After it's finished and you're all booted up you should be on the official .211 ICS version.
If you want to root, search for matt's utility for the .211 version (I believe it's the 1.7 version) and simply follow those instructions, works great and don't forget to donate. He's saved lots of us RAZR users. Also, if you want the .215 leaked update, get Voodoo OTA rootkeeper, run that, get the .215 .zip update file from you're external SD card in recovery.
When all is said and done. You should be on the most recent stock .215 ICS version, and rooted. Hope this helps
Edit.. .If this doesn't work, and I don't know if it will, I hope it does, you'll probably have to use RSD to flash a stock image. I think they are .fxz files, not sure. I've never used RSD on my RAZR, only my OG Droid1.
Thanks for the Reply, I do not have the .211 ICS .zip, Though if you or anyone else know where to find it? I do know how to do the force install that you recommended that I do.
http://eclipserom.com/vforum/showth...cial-4-0-4-(211-OTA)-Fastboot-Files-for-XT912
There you go
Thank you. Will try it and let you know if that worked!
Matt's utility (found in the Dev forum) is really all you need. I'm guessing that having bootstrap installed is one of the issues as well.
Oh, I will check that right now while I wait for the ics rom to download, thanks for more options, may try it first if it is all that I need.
You can get the utility at same link I posted earlier..^^^
I just wanted to let you know that I did get it working again with your help! I ended up having to use RDSLite to restore it but its back up and got it working again! Thanks so much guys!
Tried the ics t-mobile leak and worked awesomely for me! (goo.gl/aQuKS) its German but Google translates it brilliantly!
another opportunity is (like I did) installing miui which is officially supported and use Nova launcher if u like.
Nevertheless, T-Mobile leak works like a charm!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT910 Miui V4 using xda premium
kadosEidetic said:
I just wanted to let you know that I did get it working again with your help! I ended up having to use RDSLite to restore it but its back up and got it working again! Thanks so much guys!
Click to expand...
Click to collapse
did you get it re-rooted again?
I was having an issue with the update also. Had to go through an arduous process but finally figured it out.
Related
now i'm no noob, i've odined plenty of times. but ever since i flashed eugenes 2.2.1 the first update, my phone has went crazy. i had to flash back to bionix and it worked but everytime my phone rebooted or i turned it off then on i wouldn't get service because flight mode was always active for some reason, but bionix was the only one after i unchecked it i would get service, because i flashed tons of 2.2.1 roms and other 2.2 roms and flight mode would always be checked after boot. even though bionix still worked it was acting funky sometimes so i just odined and i used the true firmware 2.1 from eugene instead of froyo but i doubt thats the deal, now after a successful odin , it passed, it keeps coming on and i flight mode is still checked but after the second media sd card scan it boot loops, everytime... the phone won't stay on past the sd card scans.. wtffffffff help pretty please
which recovery do you have? root it, get clockwork, format system, data, cache, reflash to jfd, mini kies to kb5. I just did this from a borked voodoo recovery.
Lol its been rooted. Im not a noob man. I just odined eugenes 2.2 official jk2 stock. Now phone boots and works fine. But when I reboot flight mode is always on... and some apps keep fcing over unistalled and re installed bunch of times same result. I did two odins wtf is wrong wit my phone
BTW something I forgot to mention, ever since flashing eugenes 2.2.1 under about phone my baseband version always says unknown, even after the odin twice it still says that on every rom. Everything was alwaya fine until I flashed that rom. Odins didn't fix so idk wut is up.
Sorry not to spam but ever since I flashed dead horse and the rom my IMEI always shows up as unknown, even after odin, on any rom.
Couple of things if you odin back t ostock and you still have issues then try
1. Use three button method to get into recovery mode.
2. Click delete all user data.
3. Reboot Enjoy!
Or try clearing the cache, reset phone in recovery and clear dalvik
oka1 said:
Couple of things if you odin back t ostock and you still have issues then try
1. Use three button method to get into recovery mode.
2. Click delete all user data.
3. Reboot Enjoy!
Or try clearing the cache, reset phone in recovery and clear dalvik
Click to expand...
Click to collapse
I do this before every rom flash :/
Where did you get the pit/tar for jfd?
Did you check the md5 sum?
Try my Alt Method in the noob guide (signature, bottom of post one)
Which recovery do you have?
s15274n said:
Where did you get the pit/tar for jfd?
Did you check the md5 sum?
Try my Alt Method in the noob guide (signature, bottom of post one)
Click to expand...
Click to collapse
I got the pit and pda from the eugene does not brick thread then I used the true stock 2.1 firmware after flashing eugenes does not brick. Phone turned on but after media scanning finished it went into boot loot doing the same thing. I then odined the stock official jk2 and phone works again. BUT the reasons I odined in the first place is still there. In about phone no matter what rom or modem I flash it always says unknown under baseband version , and it says unknown on my imei number too, and when I reboot the phone no matter wut rom flight mode is always on so I don't get service untill I turn it off. None of this ever happened until I flashed eugenes newest 2.2.1 rom and even after two odins it still is affected from it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
get clockwork and flash kb5 modem. then save all bytes from the sd card (internal) and wipe it. whatever is causing your problems is persistent through a full \system, \data, \sys, \etc, etc wipe, so it must be on the internal memory.
I am about to do the same to my phone right now...
1freedude said:
get clockwork and flash kb5 modem. then save all bytes from the sd card (internal) and wipe it. whatever is causing your problems is persistent through a full \system, \data, \sys, \etc, etc wipe, so it must be on the internal memory.
I am about to do the same to my phone right now...
Click to expand...
Click to collapse
Let me know of it works for u
worked
everything copied over fine except the hong kong stock rom, so i deleted it. the phone rebuilt the necessary folders and files (Android, dcim, external_sd, lost.dir, and sd).
So does it no longer say unknown for all of those things under about phone?
i didn't have that problem, i ****ed up my kernel/recovery. worse than boot loop, couldn't mount internal, voodoo wouldn't mount \system. my saving grace...odin back to stock.
firtst, i went back to ji6, but didn't have a data connection (probably had the same issue as you have now, i didn't bother to dig deeper), then tried mini kies to get updates, but kies didnt do anything so, i flashed to jfd, (im trying to find it now for you) this got me back to a shipped straight from the box state. with data.
kies (pita) updated to kb5 on its own, went wonderbar. fast data, really smooth ui, i thought it was a tweaked rom. i think i m gonna root it and keep the stock rom...
so, the moral of the story? install mini kies if you don't have it already, wait for the link when i find the jfd i used, flash it, and then upgrasde through mini kies. ou, then put the personal stuff back onto internal
here, i found it
http://www.multiupload.com/IFSJECTS3L
or this is from the source
http://forum.xda-developers.com/showpost.php?p=10871041&postcount=234
My G tab doesn't go pass the boot animation.
When i do the Vol + plus power botton. It doesnt go into recovery mode.
I did Root the device and i was running
[ROM] VEGAn-TAB GingerEdition STABLE RC1.
How i got here
Last night i was a little drunk and i decided to play with my G-tablet. In my drunkenness i uninstall Rom manger and did a factory reset on the device. I want it to take it back to stock so i can return it and preorder an asus transformer. I only have today to return the device any help will be wonderfull
Start Here:
http://forum.xda-developers.com/showthread.php?t=861950
Use Bekit's 1105 image (nvflash_gtablet_2010110500.zip) do a factory data wipe as soon as it boots up. That should get you back to stock.
Thanks i will look into it
I did the NVFlash but it won't get pass the boot animation. The good thing is that the boot animation is the stock one that came with the phone.
Sent from my Droid using XDA App
thats a mighty big phone you have there.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jk
If your returning it, now you have the best excuse "it won't boot"
im having a similar problem. ive been stuck in a bootloop for days now. i managed to get it back to the "3 birds" but thats about as far as i can get.
it feels like im pretty close to getting this thing back up and running i just need to flash a new rom. the problem im having with this is i cant find the rom to flash. i put the rom on the sd card, but when i put it back in and boot up i cant find it anywhere in clockwork. (says no files found when trying to install zip from sd card.
So my question, is there a way to mount my device to the computer through clockworkmod so i can finaly flash a new rom.
or can anyone point me into the direction where i can find the files on the sd card
thanks in advance!
Lol I mean tablet.. omw to return the device..using the excuse that I updated the device and this happen. Can't wait till the 26th...Transformer FTW
Sent from my Droid using XDA App
Classic example why the G Tablet is getting a bad rep from the retail chains. If people would take the time to read the instructions that people have posted on these forums, all this could be prevented. If you don't understand them, ask a question. Nvflash is your friend when some thing goes wrong. Just saying.
jhreid1969 I agree 100% and was experiencing the same problem the user was above just a few weeks ago right after I bought my G Tab and began to play around with it. All one has to do is read the comments at the bottom of Roebeet's post on nvflash using bekit and they will find a post from Sprdtyf350 explaining that you must install and use clockwork mod to reformant after using nvflash and then it works fine !
Kartiel,
If you read the comments under Roebeet post for nvflash using bekit you will see a comment from a user named Sprdtyf350, he explains what you have to do using the clockwork mod to partion AFTER using nvflash !
What I did was install nvflash onto an external sd card then put it in my GTab and installed it. I then went throgh the process to format my sd card which if you are not familiar with can be found in the directions for installing clockwork mod.
After you format the card reboot and all should be well !
Yes... After nvflashing to get out of the loop you must clear cache and data and then in most cases repartition the device.
jhreid1969 said:
Classic example why the G Tablet is getting a bad rep from the retail chains. If people would take the time to read the instructions that people have posted on these forums, all this could be prevented. If you don't understand them, ask a question. Nvflash is your friend when some thing goes wrong. Just saying.
Click to expand...
Click to collapse
You are to quick to assume, sometimes issues arise even when instructions and steps are followed to the T.
Citi said:
You are to quick to assume, sometimes issues arise even when instructions and steps are followed to the T.
Click to expand...
Click to collapse
Yes on this particular issue I am. I have read on the forums about your problems Citi and you and others have gone in great depths trying to repair it. This person hardly tried and is going to blame the product for his mistake. My thoughts are you have a faulty unit and probably will not be repairable by flashing alone. This other person, probably used other conventional means to install ROMs which were not made to work with the G Tablet without maybe causing some serious problems, such as a ROM manager and didn't bother to learn how to do it safely by reading some facts first here on the furoms. If I have seen where he tried to get some help, or said he tried this and thar to repair it and not openly admitted to using a ROM manager, I would probably have a different oplnion about it.
I have clockwork recovery installed.
my question is
is there *anything special* i need to do to go from this to the new ICS or JB Roms??
thanks in advance!
Yes. Make sure you flash Gingerbread bootloader. There is an easy to follow guide available. Search for Vibrant Custom GB Bootloader on Google and it should take you directly to the thread here.
It's a simple guide to follow, just follow it carefully. *a misstep can hard brick you*
After you have that you can find a suitable 4.0.4 ICS to flash. Just follow the directions in the OP and you should be fine.
Or, you could flash a JB ROM. In that case I would recommend (because I had to) flash cm9 nightly FIRST, then go to JB from there. Would probably make your life easier
As my buddy Woodrube says: read, read, read. When you've read enough, read more.
I still sit back and read about an hours worth of old solved threads and new ones alike on an everyday basis.
Note: if you for choose an ICS ROM, please read the threads titled EU bug, and Encryption Unsuccessful. It may not ever affect you, but you should become familiar with it.
You don't need to flash Gingerbread bootloaders.
theexel said:
You know, everyone always says to go to CM7 then CM10.
I ODIN'ed back to stock today, no idea why, I got bored. xD
Note: Skip steps 1, 3, 4 if you already have a custom recovery, which you do, you're running Bionix and don't want to ODIN back to stock for a complete clean install.
These are the steps I use to go to CM10 coming from stock:
1. ODIN to stock, wipe everything, you know.. clean install.
2. Download all the zips you need. (CM10, JB GAPPS, CM10 FFC support zip, update.zip that has clockworkmod recovery.) and put them on your phone.
3. Reboot into recovery, install 'update.zip' it'll reboot, do it again.
4. It should boot into CWM now, the old version.
5. Flash CM10, it should reboot or get stuck.
6. Boot into recovery (Should be new recovery from now on.), wipe data/factory reset.
7. Boot into recovery, flash twice before rebooting.
8. Reboot system and wait for it to boot up, if it doesn't boot up, flash again.
9. Once it boots, flash GAAPS.
10. Flash CM10 FFC support.
Enjoy?
Click to expand...
Click to collapse
No you don't need GBbl's anymore. Lets just say they are not "required" anymore, but are still "recommended".
OP, I have a ICS install guide in my signature if you need it. Has details about EU bug too.
Woodrube said:
No you don't need GBbl's anymore. Lets just say they are not "required" anymore, but are still "recommended".
OP, I have a ICS install guide in my signature if you need it. Has details about EU bug too.
Click to expand...
Click to collapse
so i need to install CM7 before installing these roms(ICS)? (the guide says skip to the CM7 part). is CM7 required??
if so, how to go about installing the CM7 in place of the Froyo bionix build??
and is there a custom CWR for ICS roms that I need to install?
sorry for the dumb questions. ive been knee deep in my sgs4g and havent kept up with vibrant...
You do not need to flash CM7, people just say it's safer. (Not sure on that one.)
Follow the steps I gave up and skip the ones that I said to, you should be just fine.
theexel said:
You do not need to flash CM7, people just say it's safer. (Not sure on that one.)
Follow the steps I gave up and skip the ones that I said to, you should be just fine.
Click to expand...
Click to collapse
Ive been looking for the JB GAAPS file to dl for vibrant and I cant find it any where
http://goo.im/gapps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
theexel said:
http://goo.im/gapps
Click to expand...
Click to collapse
No wonder I couldnt find it, I was spelling it wrong ffs I feel like a a dip**** now lol
---------- Post added at 11:55 PM ---------- Previous post was at 11:40 PM ----------
Just trying to be thorough here. On step 7 it says "7. Boot into recovery, flash twice before rebooting." What exactly should I be flashing 2x here? Never mind I figured it out
The ROM, but you figured it out.
I suggest you just flash CM7 because it doesn't take that long and you get some practice before going onto another ROM.
FC3SRedSuns said:
I suggest you just flash CM7 because it doesn't take that long and you get some practice before going onto another ROM.
Click to expand...
Click to collapse
I had already flashed 2 other ROMs before going to CM10, 1 successful on not so successful. This time it went flawlessly. Im loving CM10 so far. I see why this is so addicting now haha
Now you guys see what I mean about steps before leaps?
If you have a bad flash on 2.2 or 2.3.x, they are fairly easy to recover from and start over. Sometimes a bad flash on ICS can cause irreparable damage, al'a EU bug. I've also seen motherboards borked, USB/PC unconnectivity and the worst of all a bootloader bad flash, hardbrick.
But yes, I as well as almost everyone here will agree, it is very addicting.
Hey.
I have managed to get a really funny issue with, sadly, my moms Xperia P.
The P is running Nemesis kernel v6.3 and Honami MW v8, and of course unlocked BL, and have been working okay-ish(I cant say I particularly like the P).
Since its my mom's phone, and shes... well, not the youngest nor most tech-savvy person around, Ive done what I can to make it as 'user friendly' as possible.
But this time I mustve fked up badly...
Heres what I did: I was checking if I could get the AOSP incoming call screen in the same manner as the lock screen, so I tried renaming semcPhone.apk to something else, thinking the worst thing that could happen was a boot loop... Boy was I wrong...
Not only did the phone not start(no surprise there), but it even froze before the first "vibrate", making it impossible to enter recovery
Okay, no worries, I can still enter fastboot... So I went into fastboot and reflashed the boot - nope, still froze right away...
After much struggle to no avail, I tried a 'fastboot erase system' and lo' and behold! The stupid thing didnt freeze right away anymore and I could enter recovery!
Once In recovery I restored a backup I made a couple of weeks ago, and finally the phone started again! yay! :victory:
All is good then, right? .... nope...
Did a reboot, and it did the exact. same. thing. again. And I had to erase the system and restore the backup for the phone to boot again... wtf...
Okay, maybe erasing the system wasnt enough, right? So I did a factory reset, formatted system, data and cache, and went ahead of installing a fresh copy of Honami MW.......... Phone froze right away.... back to square 1...
Okay, so I repeated the process, but instead of installing a fresh MW, I restored the backup - phone booted fine Restarted the phone and back to square one again...
I tried installing a fresh copy a few more times, and it refused to boot each time. But restoring the backup boots the phone fine every time... whaaat?
The phone works perfectly fine once its booted, and I cant see anything wrong in the system at all, yet everytime I do a reboot it freezes right away and I have to erase system through fastboot(to get into recovery at all) and restore my ~2 week old backup. Its even enough to just do an "advanced restore" and chose system, leaving data and cache alone.
Ok so.. TL;DR: Phone freezes right away on first reboot, a fresh install of the ROM doesnt work - only restoring a backup do(it makes no sense!!)
I am completely out of ideas as to what can be the issue here... I have never experienced this kind of issue - especially not just by renaming "wrong" file(which gets restored during the reinstallation processes anyway)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try flashing stock ftf completely and see if the issue persists(I guess it shouldn't)
Cheers,
AJ
Mm yes, flashing it back to stock ftf is the only thing I havent tried yet... But it still makes no sense. Why does it behave like this, regardless of complete wipes? And why is only a backup working, and not a clean install :s... My head's gonna explode over this >_<
Same here, have never been able to restore nandroid backup, always boots oince then its dead.
Anyone else have any bright ideas? I havent tried stock ftf yet(dont have access to the phone yet ), but somehow I have my doubts it will work...
I get the feeling the phone fails to mount the various partitions upon boot, but when checking permissions everything is exactly as it should be. Obviously Ive tried running 'fix permissions' in CWM, but that only results in a "/bin/sh: fix_permissions not found" which I also noticed my ZTE Blade says(which works fine despite all the cruel experiments Ive done on it lol).
Ive also tried to do a fresh install of BB and SU, as well as the whole rooting process(even though the ROM is already rooted) to no avail. (edit: also reinstalled recovery several times...)
Anyway, is there any app that can do a fix_permissions? Might be worth a shot...
Goatshocker said:
Anyone else have any bright ideas? I havent tried stock ftf yet(dont have access to the phone yet ), but somehow I have my doubts it will work...
I get the feeling the phone fails to mount the various partitions upon boot, but when checking permissions everything is exactly as it should be. Obviously Ive tried running 'fix permissions' in CWM, but that only results in a "/bin/sh: fix_permissions not found" which I also noticed my ZTE Blade says(which works fine despite all the cruel experiments Ive done on it lol).
Ive also tried to do a fresh install of BB and SU, as well as the whole rooting process(even though the ROM is already rooted) to no avail. (edit: also reinstalled recovery several times...)
Anyway, is there any app that can do a fix_permissions? Might be worth a shot...
Click to expand...
Click to collapse
Boot it wait 5-10 mins and then shut it down,do it again,and again until phone Boots needed to do it three times on Xperia U.
It only related to stock custom roms od 4.1.2.
Sent from my Xperia U using Tapatalk
XperianPro said:
Boot it wait 5-10 mins and then shut it down,do it again,and again until phone Boots needed to do it three times on Xperia U.
It only related to stock custom roms od 4.1.2.
Sent from my Xperia U using Tapatalk
Click to expand...
Click to collapse
You mean boot it to where it freezes(right away) and wait 10mins, or boot into system and wait 10mins? If the first, I think Ive tried that a few times. Doesnt hurt to try again though...
Do you have to do this every boot or just once after a flash?
Still makes no sense why it just started doing this "out of the blue"(If we ignore the fact I renamed a file, cause I seriously doubt that that specific action could cause this issue).
Edit: Dude.... That **** actually worked! I didnt wait 10mins, but maybe 2-3... Forced shutdowned it and started it roughly 5 times, the 6th time it started! Im currently rebooting it all the time(3 times so far... 4 now lol.. ok 5..) and it has started every time!!
Thank you for your tip (I should make some more accounts so I can hit 'thanks' a few more times lol)
Hi everyone,
I have a Samsung Galaxy Note 3 (SM-N900P) on Sprint and am currently running the latest Cyanogenmod.
I absolutely NEED for both Wi-Fi Teather AND GPS to work on my phone and so far, the Wi-Fi Teathering works perfect on Cyanogenmod, but GPS will not work no matter what workaround I try on the phone.
So, I thought I'd come here to ask you all for recommendations on the best and stable ROM that BOTH Wi-Fo Teathering and GPS work on without a doubt.
If I need to go to a ROM that is extremely close to Stock, then so be it. I just need to be sure that these two things work without issues.
Any suggestions are GREATLY appreciated!!
Best,
Jason
I use stock rooted touchwiz and they both absolutely work for me! :good:
inkmachine said:
Hi everyone,
I have a Samsung Galaxy Note 3 (SM-N900P) on Sprint and am currently running the latest Cyanogenmod.
I absolutely NEED for both Wi-Fi Teather AND GPS to work on my phone and so far, the Wi-Fi Teathering works perfect on Cyanogenmod, but GPS will not work no matter what workaround I try on the phone.
So, I thought I'd come here to ask you all for recommendations on the best and stable ROM that BOTH Wi-Fo Teathering and GPS work on without a doubt.
If I need to go to a ROM that is extremely close to Stock, then so be it. I just need to be sure that these two things work without issues.
Any suggestions are GREATLY appreciated!!
Best,
Jason
Click to expand...
Click to collapse
Stick to stock or stock based ROMs. Asking what's the "best" is always relative here and often meaningless. If you are looking for a non-TW based ROM for all of this then a 1000 factors come into play. Did they flash the ROM clean or dirty? If dirty from what ROM? Was these things working before flashing? If they got GPS working...did they have to do something more? Does that work for everyone? Are they calling the ROM the BEST because they like the color? How many have they tried?
Another thought is, has anyone gotten GPS to work on CM? If so, have you tried the same methods? If it worked for them and not for you, that should tell you something about trying to find another non-TW ROM where it does work. There are variances from phone to phone causing something to work on one and not another.
With all that said, if you are not heading to a TW ROM, the trial and error may be in your hands to work this out, not someone's opinion.
FreddyFredFred said:
I use stock rooted touchwiz and they both absolutely work for me! :good:
Click to expand...
Click to collapse
Can you provide a link to that stock rooted touchwiz that you use? Just want to make sure I get the correct one lol.
inkmachine said:
Can you provide a link to that stock rooted touchwiz that you use? Just want to make sure I get the correct one lol.
Click to expand...
Click to collapse
If you are new to the note 3 my thread linked here http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 will give you step by step how to root your device. There is no magic pill, it takes about a hour or less to do. All stock roms on the Note 3 are touchwiz, so it does matter what version of KitKat is on your phone i.e. 4.3 NAB, 4.4.2 NC5 or 4.4.4 NH7, when you root your device it will become stock rooted touchwiz.
jimzweb1 said:
If you are new to the note 3 my thread linked here http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 will give you step by step how to root your device. There is no magic pill, it takes about a hour or less to do. All stock roms on the Note 3 are touchwiz, so it does matter what version of KitKat is on your phone i.e. 4.3 NAB, 4.4.2 NC5 or 4.4.4 NH7, when you root your device it will become stock rooted touchwiz.
Click to expand...
Click to collapse
Hi!
Thanks for the info! I'm going to read through it after work today.
I'm already currently rooted with CWM based Recovery v6.0.4.7
compiled by Xiaolu (20140125)
My current and only ROM on the phone is the most current version of CyanogenMod.
I hope none of the above causes any problems for me when trying to go to the rooted stock touchwiz!!
inkmachine said:
Hi!
Thanks for the info! I'm going to read through it after work today.
I'm already currently rooted with CWM based Recovery v6.0.4.7
compiled by Xiaolu (20140125)
My current and only ROM on the phone is the most current version of CyanogenMod.
I hope none of the above causes any problems for me when trying to go to the rooted stock touchwiz!!
Click to expand...
Click to collapse
I'm going to assume you received the phone that way. First I would make a backup of the Cyanogen rom on the device, "you know that one works", to an external sd card, or use the internal sd card, and then copy and paste the back up file you just made to the desktop of your PC via USB cable. Now the with phone connected to your PC go to the internal sd card, copy and paste the DCIM, music, and any other data you want to keep to the desktop of you PC. Then go to settings/general/Backup and reset/Factory Data reset/reset basically you are going to do a factory reset. That should take you back to unrooted stock. It will delete all your data, like the device was new. Now, you need to go to settings/general/about device and see what version of KitKat you have. Then you need to go to download mode ( press the power button, volume down button, and home button at the same time a screen will come up then push the volume up button) it should look like this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If both lines are not OFFICIAL the you need to flash a fresh copy of what ever stock version of KitKat 4.3, 4.4.2, 4.4.4 you want with odin. Check out the thread I listed above to do that, and get to stock, then follow the steps to stock rooted touchwiz. Make a backup of the stock rooted TW rom that way you can always get back to square one it's like system restore on your PC.
Ok, with the stock rooted TW rom up and running get the device connected to the PC, and copy and paste the data files on your PC desktop back on the internal sd card. Get the device to the point of a daily user, then make a backup. Now one more twist and your done, if and when you try to restore that Cyanogen rom first backup you made, the md5 will not match your new stock rooted rom. Here is the fix, first try and restore the Cyanogen backup maybe you will get lucky. If not download a root file manager like Root Explorer, go to the Cyanogen backup that failed and click on it all the files that make the OS will come up. Find the file named "nandroid.md5" and delete it. Now use root explorer and create a new file and install in the same place, check permissions should be rwxrwx--- . Then go ahead and restore the Cyanogen backup again, this time the system will ignore the empty nandroid.md5 file and install the Cyanogen backup. I know this looks tough but you can do it, and be a flashaholic like the rest of us !!! Lol