Related
Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??
Bzktz said:
Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??
Click to expand...
Click to collapse
I'm assuming you still have stock recovery even though you unlocked the tablet. You can't re-lock the tablet so you'll eventually want to start using a custom recovery. However, don't install a custom recovery yet because the firmware upgrades are going to wipe custom recovery every time.
This should help you get started with the upgrade process using only the stock recovery:
Pre-upgrade:
0) HIGHLY RECOMMENDED -- Take the time to make nvflash accessible and make backups so that you'll be able to recover from a brick situation. This is the ONLY chance you have to do this before upgrading to .30:
http://forum.xda-developers.com/showthread.php?t=1901479
0.25) Performing the upgrades shouldn't affect your apps and data, but back them up if you want to just in case.
0.5) Make sure your tablet is charged 60% or higher or is plugged in.
Simple Upgrade Process:
1) Download "Voodoo OTA RootKeeper" from the market to back up your root.
2) Follow these instructions to update to .30:
http://forum.xda-developers.com/showthread.php?t=1755576
3) Reboot the tablet 2 times or so to make sure the .30 update finishes completely -- it updates the camera firmware and some other stuff.
4) Run RootKeeper again and verify you can still restore root. If you have to, re-root and use RootKeeper to back it up. Restoring a backed-up root is is currently the only way to root on Jelly Bean, so this is your LAST chance.
5) Download the appropriate Jelly Bean OTA update zip from here:
http://forum.xda-developers.com/showthread.php?t=1915079
6) Repeat the instructions in step 2, except you can just directly rename the file you downloaded in step 5 (there's no "zip within a zip").
7) After the upgrade is complete, run RootKeeper again and restore root.
8) Install the custom recovery of your choice (edit: when a working one becomes available).
recovery works in JB?
lafester said:
recovery works in JB?
Click to expand...
Click to collapse
sorry my mistake, there isn't one that's working yet.
i tried the manual method and it wont work
i did what the instructions said and in the end when android logo and status bar come out, shortly it display android with red triangle indicating that it failed. it says "ID verification failed." does anyone successfully update their TF700 using this method?
Bzktz said:
Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??
Click to expand...
Click to collapse
If you are still on 26 the first thing i recommend you is to use the NvFlash tool (from the Development forum) so you can recover your device from any soft brick, then update to 30 and JB. Unlocking avoid your warranty so NvFlash tool is a wise thing to go with.
Just went through the motions (Including accessing nvflash)
no worries, I bricked it on purpose and then unbricked it just to make sure. nvflash is rad!
the new JB update, Forget the benchmarks, I don't even care what they say at this point, this is the best user experience I've had on this thing so far and it's just going to get better. at least with nvflash I can still load unsigned bootloaders, that's all I need for native linux experimentation.
yea though I walk through the valley of the shadow of flash I will fear no bricking, for blob.bin art with me. :good:
Thank you very much for the response. I am up to #5 in the process but now I am stuck. I renamed the file and stuck it on my sd card. However I am getting nothing when I then boot in recovery. It tells me SD Installation aborted, and gives me the Red Triangle. What am I doing wrong here?
So I originally rooted my s3 with the GS3_debugfs-root_r2.7z method, flashed CWM and unlocked my bootloader. Since then i have flashed several roms and all was well until a couple days ago when i decided to restore my first backup in order to retrieve some data. I was still on G7 and kept getting the notification of the HE update. Even though I excepted the OTA and let it fail in CWM i kept get getting the notice almost every time i turn on my phone. I was getting so annoyed with it that i decided to flash a rom with HE in hopes that that would stop the OTA. In this whole process of restoring my backup my bootloader must have locked and when i flashed the rom I got stock on that "unauthorized software, contact Verizon screen". It freaked me out when i couldn't boot into recovery.
I followed the whole Odin, root66 method and was able to save my phone...phew... but have a couple questions now.
1) my phone has the superuser app and it shows that it cannot be uninstalled, like a system app but yet root checker says i am not rooted? Why is this.
2) Would installing supersu and updating binaries get me rooted again?
3) This one is just for curiosity..The message when i soft bricked my phone said you have unauthorized software and to go see a Verizon store. Would they really have been able help me or just tell me i am SOL
ps. Thank you to the XDA community for sharing instructions like the one i used to save my phone.
microdot said:
1) my phone has the superuser app and it shows that it cannot be uninstalled, like a system app but yet root checker says i am not rooted? Why is this.
2) Would installing supersu and updating binaries get me rooted again?
3) This one is just for curiosity..The message when i soft bricked my phone said you have unauthorized software and to go see a Verizon store. Would they really have been able help me or just tell me i am SOL
Click to expand...
Click to collapse
2: That could work, but so should loading the default SU and updating binaries.
3: They would not have been likely to help you, and may have even voided your warranty.
Going to a store would have yielded a bunch of head scratching and them telling you to file an insurance claim.
In the future if you want to block ota's freeze sdm and fwupdate in titanium.
I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?
loonytoon500 said:
I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?
Click to expand...
Click to collapse
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk
ShapesBlue said:
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk
Click to expand...
Click to collapse
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).
loonytoon500 said:
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).
Click to expand...
Click to collapse
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk
ShapesBlue said:
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk
Click to expand...
Click to collapse
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.
loonytoon500 said:
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.
Click to expand...
Click to collapse
After all the reading I've done in order to take the OTA you have to unroot. I don't know the complete process as I am not on any OTA
From my S3 running BlissStalk
Even if you dont care about custom ROMs right now you may in the future when there are no updates released for the phone or you want to sell it and could have gotten a higher price with the lower system version. Before you update try some of the ROMs out and see if there are some you like and if you dont like any then update.
That being said I have updated using ODIN and the firmware I got from this site. look around and you will find the stuff you need.
i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?
loonytoon500 said:
i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?
Click to expand...
Click to collapse
Sure it's possible, but unlikely. To put into perspective, I don't believe there has been a bootloader unlock for Verizon Notes 2-4 and Galaxy S4-5 (which would allow one to natively run AOSP without Safestrap) so the likelihood is low.
Sent from my SCH-I535 using Tapatalk
So as the title says, I recently sunshine unlocked my 4.2.2 (12.15.15 firmware) MAXX. At this point, I have a custom recovery from the root method I used on the phone a year ago, but other than that I'm just running the stock 4.2.2 Camera update.
What is the easiest way to get up and running on a current 4.4.4 build? Can I use RSDlite to return to stock 4.2.2, or does that not work with an unlocked bootloader? Could I RSDlite to 4.4.4 directly? What about flashing TWRP to my phone now and using that to flash a 4.4.4 rom? I dont care about losing all of my data or anything like that.
I'm a little confused on what I can and can't flash depending on the current version of andoid I'm on, so any help would be greatly appreciated. Thanks!
now that your bootloader is unlocked you can have root on any fw version you decide to update to. but you have to be on stock everything before you update to 4.4.4. if the recovery is the only thing you have changed you can just extract it from the fxz for 4.2.2 if that's what your on right now. flash it using fastboot or the easy way using rashr an app from play store. my fav for flashing recoveries. then take the update. after that you can flash T.W.R.P 2.8.4.0 for obake. then reboot to recovery. reboot to system to gain root if it is removed by updating
Thanks for the reply. I'll look into flashing that recovery and try the OTA. Would flashing the whole fxz (which i believe includes a bootlader) hurt me? Also, is there any way one of the OTA's changes the bootloader in a way that could mess up my unlock?
no. once your bootloader is unlocked then it won't relock unless you lock it by command prompt. yes you could use rsd to go back to stock. it has to be the exact version you are currently on. if you try to rsd a version your not on it will fail.
Will it fail in a "your phone is bricked" kind of way or an error message telling you it wont flash?
it will error telling it was aborted. i have done it once that's all it took for me to realise it needed the exact version. i was lucky to have the right one handy
here is a site for all the stock firmware.
http://motofirmware.center/files/category/
I'm in the same boat and going to do this tonight on my wife's phone.
She's currently on 4.2.2, bootloader is unlocked, rooted, and currently has TWRP installed.
If I'm correct, I need to
1. Flash stock recovery
2. Boot up and take the OTAs
then
3. Flash the latest TWRP
4. Use TWRP to re-root
4. Then I can flash a 4.4.4 rom, such as http://forum.xda-developers.com/showthread.php?t=2716824
Is that correct?
As long as my bootloader is unlocked, can I still regain root with the latest OTA?
Thanks guys, just making sure as the wife will be miffed if I screw up her phone!
Honestly, I doubt you have waited this long, but if you have, here is what I am gathering from your question... You want to run 4.4.4 roms instead of 4.2? While on 4.2.2 (if you still are) you can run OSE, AOSB, CM11, and pretty much any 4.4.4 custom rom. (though i can't get cm12 to work on a mini (same software/bootloader/recovery for the most part) on 19.6.3 so that may be out) The only reason you would have to update would be to be on stock 4.4.4. I haven't read up too much on the new OTA's, but I can say this, YOU CAN NEVER GO BACK TO WHAT YOU ARE ON ONCE YOU UPGRADE STOCK. this may not be a big deal for you, but personally, I liked the JB software the best (specifically 12.7.7 that my DEV MAXX came with) I haven't heard anyone say anything positive (really) about VOLTE or any new features, and honestly, not being able to go back on a DEV EDITION sucks. On a side note, I recently bought a Mini (bc my charge port on my DEV maxx crapped out and Moto doesn't have any more, so i am in phone purgatory waiting for *something* but pretty much anyone I have talked to is useless.) I just fxz'd back to 19.5.3 from 19.6.3, but I cannot go backwards any further *completely* @NWKENT has done it numerous times as best as it *can* be done. also, @NWKENT can confirm you absolutely cannot go back from 4.4.4 to an earlier edition. I hope this helps if you haven't upgraded yet. If you have, for most intents and purposes, you haven't really lost anything.
HELLO GUYS
i really need help with my Razr HD , i want to downgrade from kitkat 4.4.2 to jelly bean since the kikat update caused nothing but trouble to me , i am newbie , so please someone help me to downgrade my phone to 4.1.2 step by step and make it simple as possible .
i have RSD lite 6.1 , tried to flash on fastboot mode , got failed flashing process 5/27 error ,
all drivers are installed
i have stock firmware 4.1.1 , 4.1.2 , 4.4.2 xlm files
must mention that my system version is on 183.46.15XT926
Developers mode activated , USB Debugging checked
:angel:
You cannot downgrade from 183.46.15 unless you unlocked your bootloader before upgrading to 183.46.15.
You cannot now unlock your bootloader if you have 183.46.15.
What trouble are you having with KitKat? You can get root, and I then installed Nova Launcher, Titanium Backup, and Xposed Framework with GravityBox to customize things the way I like them.
Spott07 said:
You cannot downgrade from 183.46.15 unless you unlocked your bootloader before upgrading to 183.46.15.
You cannot now unlock your bootloader if you have 183.46.15.
What trouble are you having with KitKat? You can get root, and I then installed Nova Launcher, Titanium Backup, and Xposed Framework with GravityBox to customize things the way I like them.
Click to expand...
Click to collapse
first thank you for replying to me , My bluetooth is gone , i can't seem to connect or send a file to any device
and now so is my wifi , it says saved but not connected and i know it's not router issue because others can connect to the same router with no problem at all
i have Droid razr hd toolkit 5.0 , couldn't unlock my bootloader with it , also couldn't downgrade to jb
how can i root my device using this toolkit with my bootloader still locked ? any instructions please !
First, I'd try reflashing the stock firmware (183.46.15) and see if that fixes your Bluetooth and WiFi problems. I use RSD Lite and it works well. I know the stock firmware works fine on this phone, that's the same configuration I'm using.
To get root, you can either use the "hydrogen peroxide" method, or kingroot. I'd get your radio problems straightened out first before worrying about root.
Spott07 said:
First, I'd try reflashing the stock firmware (183.46.15) and see if that fixes your Bluetooth and WiFi problems. I use RSD Lite and it works well. I know the stock firmware works fine on this phone, that's the same configuration I'm using.
To get root, you can either use the "hydrogen peroxide" method, or kingroot. I'd get your radio problems straightened out first before worrying about root.
Click to expand...
Click to collapse
i tired flashing the stock firmware , but i get this error on the 5th step
i rooted my device , installed superuser , now i am having issue with cmw recovery image
i can't install it on the device
You have to comment a couple of lines out of the install package to get the firmware to flash. There's details in the hydrogen peroxide instructional thread, down where it takes about upgrading from 182.46.15 to 183.46.15.
You can't really install an effective custom recovery (like CWM) with a locked bootloader.
What on earth are you trying to accomplish? If you're trying to fix your WiFi and Bluetooth problems, then both getting root and installing a crippled recovery isn't going to get you there very well. Focus on reflashing the stock firmware first, then come back to root (and don't even waste your time with that broken CWM and the deodexed ROM, they don't gain you anything, and cause more problems than they solve. I soft-bricked my phone three times trying to get anything out of them. The only way to recover from that was to....wait for it....reflash the stock firmware. Notice a pattern here?)
Spott07 said:
You have to comment a couple of lines out of the install package to get the firmware to flash. There's details in the hydrogen peroxide instructional thread, down where it takes about upgrading from 182.46.15 to 183.46.15.
You can't really install an effective custom recovery (like CWM) with a locked bootloader.
What on earth are you trying to accomplish? If you're trying to fix your WiFi and Bluetooth problems, then both getting root and installing a crippled recovery isn't going to get you there very well. Focus on reflashing the stock firmware first, then come back to root (and don't even waste your time with that broken CWM and the deodexed ROM, they don't gain you anything, and cause more problems than they solve. I soft-bricked my phone three times trying to get anything out of them. The only way to recover from that was to....wait for it....reflash the stock firmware. Notice a pattern here?)
Click to expand...
Click to collapse
i am trying to install cm 12 custom rom , since flashing the stock failed many times
i used motoeclipse to unlock the bootloader after rooting , don't know if it works or not
now i am giving a shot at custom roms
You cannot unlock the bootloader of 183.46.15. You cannot install custom ROMs, or even older stock ROMs, with a locked bootloader.
You did not unlock the bootloader, and you're lucky you didn't brick your phone trying.
Sorry, but with that phone and that firmware, there's just no way that anyone's discovered to unlock it (and it's been that way so long that very few are even trying any more).
That rudimentary CWM that's available is not designed for your phone, is only barely compatible, will not allow you to flash custom ROMs, and that fact is stated boldly and repeatedly in the post where you found it. You're stuck with a very specific Motorola 4.4.2 kernel in the bootloader and you can't change it, and if you install a ROM that's not perfectly compatible with it (that is, anything other than the 183.46.15 firmware) you'll end up with a phone that won't boot.
You might be "giving it a shot" but your magazine's full of blank ammo.
You must slow down and read carefully before you brick your phone, because you've already missed a lot of important information that you'll need to keep you out of trouble.
Also, if you can't figure out how to flash a stock ROM, you're not qualified to pursue custom ROMs even if you could. What do you think happens if a flash fails and you're stuck with a soft-brick? The only way out of that is to flash a stock ROM and start over.
You have two options at this point: Either accept your phone the way it is without Bluetooth and WiFi, or do the research necessary to learn how to reflash the stock ROM and fix your problem. Here's a hint: I know exactly why your flash attempts failed, and it's quite easy to fix it, and I've already told you where to find the information to do so, in a previous post.
Now you're on your own, as I probably cannot help you any more.
how can i get pass the 5th step is rsd ?
i wanna go back to the same stock firmware4.4.2 or downgrade to 4.1.2 but i cant
sorry sir for bothering you , i am just doing researches haven't done anything passed the root
my phone status now : rooted with superuser , stock recovery still in
bootloader still locked
i have heard of this tool DROID_RAZR_HD_Utility_1.41_KK here: http://forum.xda-developers.com/showthread.php?t=2474393
i don't know what to do ?
You must slow down and read carefully. Especially the first paragraph of post #7.
It's not useful to do research if you don't read the results.
Spott07 said:
You must slow down and read carefully. Especially the first paragraph of post #7.
It's not useful to do research if you don't read the results.
Click to expand...
Click to collapse
thanks , just to let you know , i have found the same stock firmware and flashed successfully , still with wifi and bluetooth issues
i have been told that downgrading to jelly bean will sort all my issues
waiting for advice , don't know what to do next
I don't know who told you that downgrading to JB will help you, but they're wrong, because 1) it's impossible for you to downgrade, and 2) the KK firmware works quite well with very few bugs.
Perhaps the wireless chip inside your phone is damaged. Does the GPS work?
Perhaps the wireless service is disabled in the settings. Do you have airplane mode turned on? Do you have WiFi and Bluetooth disabled? Have you tried deleting or "forgetting" your WiFi connection, and then re-entering it again from the beginning?
i tried all of this , airplane mode , wifi advanced settings , everything
what if i downgraded the kernel from 15 to 10 , would i be able to unlock my bootloader and downgrade to jelly bean ?
You cannot downgrade the kernel. It's within the locked bootloader. I told you that in post #9.
You cannot unlock the bootloader on this phone. End of story. Hundreds of the best developers have tried every possibility they could think of, and have given up.
Perhaps some miracle will occur and someone will find a way, but don't count on it. This phone is old and those with the proper skills have moved on to newer, better things. As of right now, and for the foreseeable future, it is impossible.
Also, you never answered whether your GPS works.
flashed back to stock , now my wifi works outta nowhere
Sorry, I got confused about the conversation, I'll explain below.
it's not like that , first i followed your instructions and flashed the stock 183.46.15 , when nothing worked then i flashed the modified 183.46.10 suddenly wifi started to pick up signals , then drops every once and a while
i have no issues with rooting , i can root the device in minutes which i have
Sorry for being so rude earlier, I got confused.
I usually use the Tapatalk app to read these forums, but right now the login server is down, so I had to log in on the website. When I looked on the website, the screwy timestamps appeared to indicate that you had replied a couple hours ago, so I clicked on the link. (The timestamp options are terribly difficult to find, so I hadn't corrected them for my timezone, and then forgot that fact.) Instead of taking me to the last post in the thread, it displayed the first page of 10 posts (I'm used to seeing 50/page with Tapatalk) and I saw your (old) post at the bottom asking how to get the firmware to flash with RSD. At that point I got frustrated and failed to check any farther, and responded as if that were another repetitious request for the same information.
So, between the Tapatalk login server, the awkward behavior of this site, and my frustration and impatience, I responded very badly.
You didn't deserve that response, and I'm sorry.
I don't know why re-flashing the 183.46.15 firmware didn't work, it has few bugs and is pretty stable for everyone who's stuck with it. I don't know anything about any "modified 183.46.10" firmware that could be flashed on our phones, where did you find that? Are you referring to this? If so, it's great that it works, but it's risky and certainly won't permit you to unlock your bootloader.
Scott