So I'm not completely new to the android dev scene but I wouldn't say I'm an expert. I know enough that I have rooted my phone and have tried several different ROM's over the past year. I use titanium back up pro, with cwm 6.0 and running carbon 1.7. I haven't tried a new ROM in a while so I went browsing for the latest and greatest. I decided to try the latest aopk milestone1 and something happened. It got stuck in the boot animation. I was able to boot into recovery and undo what I did. I reflashed carbon ROM. After I did that I noticed I could not connect to my sprint network. I went through all the steps to manually program the phone but got error after error. One error message in particular said there was a modem error. Under "about phone" in settings I see that there is no info for msid or anything else. And when I try to update profile and or prl it says no no sprintacct user name device ID is null. Please help me someone for I am way out of my league on this one. Thanks in advanced to all the people smarter than me out there.
Sent from my Galaxy Nexus using xda app-developers app
Update. After some more thread browsing and research I believe I have screwed up my radio and need to flash new ones. I think I need to flash CDMA and LTE. But now I'm having trouble figuring out which is the right one to download and flash. I have searched many threads but a bit confused. I know how to flash them using android sdk
Sent from my Galaxy Nexus using xda app-developers app
Related
Hi guys
I have a rooted GSM Gnex cunning running JB 4.1.1. I have used Toolkit v7.6.0 to root which was the easiest way for me, all went well and is rooted.
However on the Fastboot screen (blue bar at the bottom) reads "Fastboot Status- FAIL Invalid Command"
If I attempted to install any ROM via CWM TRWP ROM Manager etc, have tried 3/4 today, I get the error below
E: Error in /sdcard/(which ever ROM I'm installing)
(Status 7)
Installation aborted.
Along with the wee Android and red triangle
And suggestions where I have gone wrong?
My Gnex rooted and installed ROMs without an issue prior to a repair with o2 where they apparently installed 'new o2 software'.
Thanks folks
wworx said:
Hi guys
I have a rooted GSM Gnex cunning running JB 4.1.1. I have used Toolkit v7.6.0 to root which was the easiest way for me, all went well and is rooted.
However on the Fastboot screen (blue bar at the bottom) reads "Fastboot Status- FAIL Invalid Command"
If I attempted to install any ROM via CWM TRWP ROM Manager etc, have tried 3/4 today, I get the error below
E: Error in /sdcard/(which ever ROM I'm installing)
(Status 7)
Installation aborted.
Along with the wee Android and red triangle
And suggestions where I have gone wrong?
My Gnex rooted and installed ROMs without an issue prior to a repair with o2 where they apparently installed 'new o2 software'.
Thanks folks
Click to expand...
Click to collapse
Flash cwm again, sometimes it doesn't stick, and without it it's really hard to flash roms
Tried that a couple of times with no success, still the same error
what command are you typing in?
Now your asking me to open a command window
I have been trying to install ROM through CWM GOO manager and ROM Manager most of the day with the same error
I'm a complete newbie when it comes to command prompts etc
I hate using 'I told you so' like comments, but you really shouldn't be rooting, especially via tool kits, if you are a noob. I really suggest reading/learning what tool kits are doing so you can troubleshoot.
Sent from my Galaxy Nexus using xda app-developers app
ttahatt said:
I hate using 'I told you so' like comments, but you really shouldn't be rooting, especially via tool kits, if you are a noob. I really suggest reading/learning what tool kits are doing so you can troubleshoot.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Agreed. If you can't use fastboot/command prompts, you have no business rooting. Tool kits shouldn't even exist because they allow this. For first time rooters, always learn fastboot/adb, it isn't very hard
Sent from my Galaxy Nexus
Thanks for the replies guys.
The 'I told you so' comments not a problem, we all learn by our mistakes, and hopefully better ourselves.
The phone has been successfully rooted and a few ROM tested until I found one I like, it was unrooted to see what the OTA JB update was like.
Now any pointers on where I will learn the required fastboot/command prompts?
Give me gas boilers and turbines anyday
follow this: http://forum.xda-developers.com/showthread.php?t=1529058
should tell you how to flash ROMs as well without using ROM manager so you have a less chance of it not working.
Agreed, that's a great option. I personally used this guide to get moving, http://www.droid-life.com/2011/12/1...extended-batteries-day-one-thoughts-and-more/ , but this forum will answer pretty much any question you might have at this point in the process.
Sent from my Galaxy Nexus using xda app-developers app
And by this forum I mean xda.
Sent from my Galaxy Nexus using xda app-developers app
Okay, last week, my old droid died in it's sleep. I'm currently unemployed and a friend was kind enough to give me his old Incredible. He has it rooted with CyanogenMod, and I have been trying to activate it on PagePlus. I have not been able to OTA activate it as is, and I've read it's because of the non-stock mod flashed on. I've been scouring these and similar forums for the past week, going through solution after solution to no avail. It's become a time-sensitive issue.
What I have done so far:
Downloaded the s-on and pb31img.zip: The s-on thing flashed properly, but when I try to flash the PB31IMG.zip, it just says installation aborted. I've tried downloading the zip file from multiple sources, in case it was an issue with the file. I've tried flashing Jellybean just to see if there was an issue with flashing any other roms at all and it worked fine.
Downloaded, installed, and updated HTC Sync and the correct RUU to go with my baseband. I can not for the life of me get either of these programs to recognize my phone while it's plugged in, despite the phone and computer separately recognizing each other and being able to interact normally otherwise. I believe this to be a driver issue, and I can not find the appropriate driver. All inquires to the correct one have guided me towards getting the SDK package, downloading the driver from there and installing it. I did this. When I attempt to search for drivers in the designated folder, it tells me that it can't be installed correctly. I have tried this from two computers with Windows 7 to the same effect.
I would appreciate any help on this asap, as I am waiting on several employment-related calls and have reached my wit's end on finding a solution on my own.
Did you tried to flash stock rom?
May be this helps
doug piston post, just found it in a quick search on the web
http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html
Hope it helps mate.
Sent from my GT-S5830i using xda app-developers app
axyllum said:
Did you tried to flash stock rom?
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
Yes, I did. It did not work. That, from my understanding, is what I was attempting to do with the PB31IMG.zip.
axyllum said:
Did you tried to flash stock rom?
May be this helps
doug piston post, just found it in a quick search on the web
Hope it helps mate.
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
I appreciate the quick search, but I have done those things to the letter multiple times and described doing them as such, as well as the issues I encountered.
IanStraka said:
Okay, last week, my old droid died in it's sleep. I'm currently unemployed and a friend was kind enough to give me his old Incredible. He has it rooted with CyanogenMod, and I have been trying to activate it on PagePlus. I have not been able to OTA activate it as is, and I've read it's because of the non-stock mod flashed on. I've been scouring these and similar forums for the past week, going through solution after solution to no avail. It's become a time-sensitive issue.
What I have done so far:
Downloaded the s-on and pb31img.zip: The s-on thing flashed properly, but when I try to flash the PB31IMG.zip, it just says installation aborted. I've tried downloading the zip file from multiple sources, in case it was an issue with the file. I've tried flashing Jellybean just to see if there was an issue with flashing any other roms at all and it worked fine.
Downloaded, installed, and updated HTC Sync and the correct RUU to go with my baseband. I can not for the life of me get either of these programs to recognize my phone while it's plugged in, despite the phone and computer separately recognizing each other and being able to interact normally otherwise. I believe this to be a driver issue, and I can not find the appropriate driver. All inquires to the correct one have guided me towards getting the SDK package, downloading the driver from there and installing it. I did this. When I attempt to search for drivers in the designated folder, it tells me that it can't be installed correctly. I have tried this from two computers with Windows 7 to the same effect.
I would appreciate any help on this asap, as I am waiting on several employment-related calls and have reached my wit's end on finding a solution on my own.
Click to expand...
Click to collapse
Reflash soff and then just flash touch of blue and you can activate on page+ from there and if you want cm back just flash cm7 and the gapps because a factory wipe in recovery won't make you reactivate
Sent from my ADR6300 using Xparent ICS Tapatalk 2
Thread moved. Please post in the correct sections of the forum, all questions belong here in Q&A, unfortunately ticking the "Is this a question" box doesn't automatically put it in here.
Thanks
AvRS
I would get s-off back, as it will not affect activating. Then either do this ruu http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip, thru hboot, or as stated earlier reroot and flash the stock 4.08.605.15 rom or Touch of blue. If the ruu dosent work, try reformating your sdcard fat32 and then try again.
IanStraka said:
Okay, last week, my old droid died in it's sleep. I'm currently unemployed and a friend was kind enough to give me his old Incredible. He has it rooted with CyanogenMod, and I have been trying to activate it on PagePlus. I have not been able to OTA activate it as is, and I've read it's because of the non-stock mod flashed on. I've been scouring these and similar forums for the past week, going through solution after solution to no avail. It's become a time-sensitive issue.
Click to expand...
Click to collapse
Page Plus doesn't care a hoot if you've got a stock ROM, CyanogenMod, are rooted, or any of that stuff. And they certainly can't tell if you are s-off or s-on. I have had zero issued doing OTA programming on my Dinc regardless of the many ROMs I've had on it. I've always just dialed *22890 to activate and *22891 to update the PRL. Granted, I haven't changed my phone number or deactivated in quite a while...
But yeah, like others said, get s-off back if you at all can. If you flash Touch of Blue or another stock-based ROM, you will have more access to manually programming it that you can get with CyanogenMod.
I was rooting a Sprint S3 phone and I looked at the description on the toolkit and it said it was jellybean compatible so I thought what the hell. I am stuck now with it starting up and only going to a black screen, but the sound of it starting is in the background. Other people in the thread had this issue and have given ways to fix it, but for some reason my computer can't recognize the phone anymore in usb so I can't transfer files to it, but odin3 is able to do whatever it wants.
So I am just wondering if someone could help me restore it to working condition. I have searched around and checked the ways other people did it, but I can't transfer to the phone.
Can you get into download mode? Sounds maybe bricked. Does ODIN recognize it at all?
this post sent from my Jellybombed GalaxySIII
Try this
http://forum.xda-developers.com/showthread.php?t=1904099
Sent from my SPH-L710 using xda app-developers app
yeah odin was able to recognize it and I was able to restore it with a tar. Thank you guys for helping out though
I began with the QCom toolkit, however I did not proceed because the serial number of my device never showed up on the QCom main menu as it stated it should. Everything else seemed ok, but the missing serial number made me suspicious.
I ended up using Odin to push CWM instead (a process I am very familiar with coming from the Epic4G) and then I used the team Epic root zip.
sent from a secret underground bunker
So I offered to put a custom ROM on my wife's Galaxy S II T989, because she likes my S3. First problem was it would NOT root. It would install the superuser app but it wouldn't verify as rooted, says the su binaries were not installed... Ok. I wanted to use the CM11 Kit Kat Rom, so the instructions said that I had to be rooted so I kept looking and finally found one for su v0.92, it failed in CW recovery so I tried it using Odin, and again it failed. So I rebooted the phone to try again later and it is now stuck in a boot loop. I have read that Odin can be a little finicky so I kept trying and to no avail. I even tried Heimdall Suite and it said that it detected my device but after I tried to install the root package that way it said device could not be detected and threw an error. I couldn't figure that out, so I verified that the USB drivers were installed and they were. The forum says I have what's called a soft bricked phone and to download a recovery kernel for it and it should fix the problem, but I can't find one for android version 4.1.2.
I have tried two different USB cords, and two different USB ports and nothing. I am just so lost confused. I completely abandoned Android after Froyo and went to a Windows Phone for over 2 years but recently came back because of the lack of app support. I used to flash ROMs on my LG Optimus T all the time without a problem. Things have changed I guess. I'm pretty sure that my wife is going to have a cow when she wakes up this morning. Any help that anyone can provide would be most helpful. Thanks in advance!
So I fixed the problem with the boot loop. Odin finally wanted to cooperate this time. I downloaded a stock time and extracted the md5 file out of it and flashed it using Odin v1.85 with defaukt options checked and it worked! I hope this helps someone who was having the same problem I was with the Galaxy T989.
Sent from my SGH-T999 using xda app-developers app
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
joshuaerda said:
Hi friends. Long time lurker here.
I've had many Samsung phones and many other android devices, but this is my first brick.
I had flashed the rooted SM-T217s rom, and the wifi wasn't working, so I tried to reflash it, at which point everything went wonky. I searched the forums and found some threads on bricked 217s's, but nothing specific to my situation.
The tablet went to the emergency firmware update screen, and I haven't been able to get Kies to even recognize it. I try to Odin back to the latest stock (B8) but it fails at 'Get PIT for mapping.' My google-fu tells me this is not a good thing.
Am I hosed here? What else can I try?
Thanks XDA, you're my only hope.
Click to expand...
Click to collapse
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
joshuaerda said:
Good news, I guess. I was able to flash TWRP recovery and the stock rooted rom from another computer, but now Wifi is borked and there's no network connection. HALP.
Click to expand...
Click to collapse
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
254336992952
joshuaerda said:
Okay well I fixed it.
Turns out, the problem was that I was using Odin on a VM on my Mac. I had tried to use a PC, but I think the USB controller was too old, so that failed too. I had to use Heimdall to flash each of the partitions from the B8 zip manually. It worked, and I'm back in business, though not rooted. I suppose I'll wait until there's a better way to root before I try it again.
Click to expand...
Click to collapse
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
IAMRUDYT said:
You should have made a backup. I used twrp recovery flashed a rom same thing wifi wouldnt work so I restored back. If you get it working again make a backup imo. Goodluck.
Click to expand...
Click to collapse
same here, I have the rom, but hesitated on the firmware, waiting to see if someone gets the wifi working, not to many developers here for this tablet.
sm t217s
Ok guys. Heres my deal with this TAB. Ive rooted... Unrooted. wipe wipe wipe wippty wipe . WiFi not working. Fixed it with NB8. So here now I sit with:
----NB8 Wifi works---
----TWRP-----
Yup, pathetic i know. I cant even get the supersu to flash. TWRP wont move it over to flash off external sd card. Im not hip to abd plus i heard you leave yourself wide opento visitors when using that.
Ive eye hustled a thread on here that some friends are getting back together to rock it on a custom rom so my fingers are crossed. This tab is so neglected i mayjust go get the 210r. But i really dont want to. So my question is....
Can someone please give me links to files that work with the NB8 stock firmware. Some of the links are outdated after sprint uploaded the new bootloader. We are a small community on this tab so lets stick together on this. I dont think cynogen isgoing to do anything for it. As they concentrate on thier new phone which looks pretty sweet by the way. K im done. Going to wait for help and play with this htc one s
thats been collecting dust.
Rooted
Sent from my SM-T217S using XDA Premium 4 mobile app