Related
Sorry for being noobish, just got a nexus, UK and it's on 4.0.1, been reading a lot, and very much overwhelmind, now, coming from my galaxy s2, which, I had been used to flashing and routing daily. I managed to use the toolkit, to root my phone, smashing app, will definitely donate, to the dev, as i managed to root, in pretty much 5mins. My problem is, whats the best route, to follow, in order for me to have the latest stock 4.0.4, because I have read a lot of stuff, so now muddled as to what path to take. Is it a matter, of just downloading the official rom, in the general section, and flashing it via custom recovery, sorry for the noobish questions, it's been a long day, trying to get to know the phone, am sure, if someone can help me from here, all be fine. I also tried to seek for an update, under about, but phone says am on latest firmware, which is 4.0.1,so appreciate your guidance please.
marvi0 said:
Sorry for being noobish, just got a nexus, UK and it's on 4.0.1, been reading a lot, and very much overwhelmind, now, coming from my galaxy s2, which, I had been used to flashing and routing daily. I managed to use the toolkit, to root my phone, smashing app, will definitely donate, to the dev, as i managed to root, in pretty much 5mins. My problem is, whats the best route, to follow, in order for me to have the latest stock 4.0.4, because I have read a lot of stuff, so now muddled as to what path to take. Is it a matter, of just downloading the official rom, in the general section, and flashing it via custom recovery, sorry for the noobish questions, it's been a long day, trying to get to know the phone, am sure, if someone can help me from here, all be fine. I also tried to seek for an update, under about, but phone says am on latest firmware, which is 4.0.1,so appreciate your guidance please.
Click to expand...
Click to collapse
Follow the directions here. Note that this will wipe your data...
efrant said:
Follow the directions here. Note that this will wipe your data...
Click to expand...
Click to collapse
Phew cheers buddy, haven't tried this yet, as at work, will give it a short when I get home, anything easier than this please, as i just have a forbia for anything called adb please? Also, don't understand why my device is still on 4. 0. 1, been hitting the update button continously with no luck, but prepared to use other means, as suggested above, to get the device updated. Thanks again in advance.
marvi0 said:
Phew cheers buddy, haven't tried this yet, as at work, will give it a short when I get home, anything easier than this please, as i just have a forbia for anything called adb please? Also, don't understand why my device is still on 4. 0. 1, been hitting the update button continously with no luck, but prepared to use other means, as suggested above, to get the device updated. Thanks again in advance.
Click to expand...
Click to collapse
You CAN flash factory images through the toolkit you know. You can download them at Google, put them in the correct subfolder of the GNEX toolkit folder and flash away. In order to do that you do have to have an unlocked bootloader and you will loose your root. Unlocking the bootloader will loose all your data (including under the SDCARD folder (so everything you stored will be gone)!. Rooting can be done again through the toolkit...
Or you can download a different flashable zip file that you can flash from CWM recovery.
Hmm thanks this looks more like my sort of of a thing "different flashable zip file that you can flash from CWM recovery.", were can i find this please?. Thanks.
Thanks for looking everyone - The required QCN file was obtained and the Post-IMEI Recovery Bell Data Connectivity issue has been solved by PeopleArmy with the assistance of Jethro650!
Hey Bell users, I recently lost my IMEI and after restoring it using this method I now have no service. However their is a solution and but I need your help!
I need a backup of a specific file from a working BELL SGS3. Their is no flashing required as you only need to install a windows program and click a few buttons, then upload the file and PM it to PeopleArmy. The file will allow xda member, Peoplearmy to add BELL to his Data Restorer App for post-IMEI-injection issues. The file is small and will only take you a few minutes to retreive. As a bonus, the file you are retrieving is a backup of your IMEI data, which is good for you to keep in case you ever loose it.
If any Bell user already has a QCN file backup, please skip to step 7 so I can get this fix underway for my phone and the others waiting to get data back.
INSTRUCTIONS (for stock samsung rooted/unrooted roms - AOSP roms follow this):
1. DOWNLOAD and Install QPST V2.7.378 from HERE. Unzip the file and run the "setup.exe" to install QPST.
(Please note that QPST is a powerful program and can flash anything you throw at it. Don't do anything outside of the instructions as it can/could damage your phone)
2. You need open a hidden settings menu. Using the stock dialer dial *#7284#
3. Press the USBSettingsMenu button and put your phone in "RMNET + DM + MODEM" mode.
4. Plug your phone into your computer. Open your windows control panel and look in device manager under Ports and Serials you should see your phone there (note the COM##).
5. Find QPST in your start menu and open "QPST Configuration", click on the PORTS tab and then on Add New Port button. You should see the phone listed in the box on the right side. Click it and press OK. If you don't see it, type in COM## where ## is the port number you noted in step 4 and click OK. Close "QPST Configuration".
6. Find QPST in your start menu and open "Software Download". Click on the BACKUP tab. Make sure your phone is listed at the top under Port. Select the location you want to save your backup beside the "QCN File". Click Start and wait for it to finish. You should now have a QCN file of your NV wherever you made the save location.
7. Submitting your QCN is no longer required as this issue has been solved.
Please note that the instructions above were originally written by PeopleArmy but I modified them for people like me, who need it a little simpler
Thank you for your help,
Ian
I just replied to your thread here to his thread there hope I can help.
jethro650 said:
I just replied to your thread here to his thread there hope I can help.
Click to expand...
Click to collapse
I hope you can help too! I see your reply on PeopleArmy's thread. Probably for the better that it goes directly to the maker than to the public or a noob like me. I'm not really sure what kind of devious things could be done with a copy of someones QCN file. I think PeopleArmy only needed one file so I suppose anyone else can use the instructions to backup their QCN but don't post it online or send it out.
I'll edit the OP and ask to have this thread closed once everything is resolved.
Thanks again,
Ian
Ian1331 said:
I hope you can help too! I see your reply on PeopleArmy's thread. Probably for the better that it goes directly to the maker than to the public or a noob like me. I'm not really sure what kind of devious things could be done with a copy of someones QCN file. I think PeopleArmy only needed one file so I suppose anyone else can use the instructions to backup their QCN but don't post it online or send it out.
I'll edit the OP and ask to have this thread closed once everything is resolved.
Thanks again,
Ian
Click to expand...
Click to collapse
Yeah I'm not sure what all is contained in the backup but I do know that my imei number is in there so its not wise to throw it out to the general public.
On a side note mine was carrier unlocked when I took the backup so I don't know how that would play into it if at all. In the least I hope it helps him help people in your situation.
Good call! I decided to update the OP so that if anyone else decides to send their Bell QCM backups in, they will know to send them directly to PeopleArmy. I have no idea if your carrier unlocked file will have any effect on this fix so it couldn't hurt to have other people send theirs in too.
Thanks again for you're help. If you get any kind of updates that don't make it to the other thread, feel free to post them here as I'll be checking it every chance I get (only at home until my phone works again - no wifi at work)
Ian
Ian1331 said:
I hope you can help too! I see your reply on PeopleArmy's thread. Probably for the better that it goes directly to the maker than to the public or a noob like me. I'm not really sure what kind of devious things could be done with a copy of someones QCN file. I think PeopleArmy only needed one file so I suppose anyone else can use the instructions to backup their QCN but don't post it online or send it out.
I'll edit the OP and ask to have this thread closed once everything is resolved.
Thanks again,
Ian
Click to expand...
Click to collapse
Thanks for making a note of this on here. I have said in my thread repeatedly to never post any QCN backups publicly even if you are just storing it somewhere publicly accessible. I always discard of any QCN's that people send me once I look it over and once they are no longer needed. I even go as far as deleting the message that contains the link to a person's QCN after it is no longer needed for development (it also helps keep my message box from becoming too full...lol).
Jethro I sent you a message that I need a backup created using the 2.7.378 version of QPST. The one you sent me was made using the 2.7.323 version.
Thanks,
DX
@ian1331: It may be helpful to change your OP: It is a "QCN" backup, not QCM. No need to stress too much yet, I am pretty sure once peoplearmy gets what he needs you will be up and running again. I have seen him do it many times before.
David Dee said:
@ian1331: It may be helpful to change your OP: It is a "QCN" backup, not QCM. No need to stress too much yet, I am pretty sure once peoplearmy gets what he needs you will be up and running again. I have seen him do it many times before.
Click to expand...
Click to collapse
Haha, I noticed that earlier today and I took a couple minutes to look but I couldn't figure out how to change the thread title. I think I got all instances of "QCM" in the OP, just not that title. I'll take another look right now.
Thanks,
Ian
@peoplearmy new backup made and pm sent, actually two sent cause I don't think the first one went lol.
@ian1331, I stayed up last night and got peoplearmy what he needed and he has updated his program in his thread. You should be good to go. Please post your results and if it works just add (solved) to your thread title. Good luck.
Edit--> you can change the thread title by editing your first post and just edit the title....
It is done! I was able to use the Data Restorer Application to fix my phone. With the assistance of PeopleArmy and the timley response/donation from Jethro650, I have a new QCN file restored to my phone and everything is perfect!
This issue is solved for me! If anyone requires further assistance with this issue, please refer to PeopleArmy's thread.
Thanks,
Ian
Peoplearmy said:
Thanks for making a note of this on here. I have said in my thread repeatedly to never post any QCN backups publicly even if you are just storing it somewhere publicly accessible. I always discard of any QCN's that people send me once I look it over and once they are no longer needed. I even go as far as deleting the message that contains the link to a person's QCN after it is no longer needed for development (it also helps keep my message box from becoming too full...lol).
Jethro I sent you a message that I need a backup created using the 2.7.378 version of QPST. The one you sent me was made using the 2.7.323 version.
Thanks,
DX
Click to expand...
Click to collapse
I have somebody requesting a qcn file from me, not sure how to do this safely, looking for a middleman to edit me imei number (and anything else important) out of the file(s).
requesting a qcn file i need i747m qcn file please
Hey all,
I have NEVER tried to unlock or root a phone before, but I have the desire to try it now.
I have the T-mobile SGH-T999 with the new Android Jellybean 4.1.1 (Build Number JRO0L.T999UVDLJA)
I want to try to root my phone, but I would like to keep as much of the the new update (Jellybean) as possible instead of reverting to ICS. What I'm wondering is, what should I do to root the phone, and what programs are preffered, etc. Also, I was wondering how to back up my current build in case I want to set it back to default in case of warranty issues that I had to return it.
I am sure others have asked... maybe this would be a good sticky, I don't know... but I am hoping someone will take the time to point me in the right direction.
I need to know
a.) What I need to backup pre-root
b.) What software is best to root
c.) Any special instructions for rooting that may be specific for this build or this phone
d.) How to un-root in case I need to return the phone.
Any help would be appreciated, and apologies in advance if this is a repeated question. I just figured I'd ask because of the new update.
Thanks!
Skot in Seattle
sekellas said:
Hey all,
I have NEVER tried to unlock or root a phone before, but I have the desire to try it now.
I have the T-mobile SGH-T999 with the new Android Jellybean 4.1.1 (Build Number JRO0L.T999UVDLJA)
I want to try to root my phone, but I would like to keep as much of the the new update (Jellybean) as possible instead of reverting to ICS. What I'm wondering is, what should I do to root the phone, and what programs are preffered, etc. Also, I was wondering how to back up my current build in case I want to set it back to default in case of warranty issues that I had to return it.
I am sure others have asked... maybe this would be a good sticky, I don't know... but I am hoping someone will take the time to point me in the right direction.
I need to know
a.) What I need to backup pre-root
b.) What software is best to root
c.) Any special instructions for rooting that may be specific for this build or this phone
d.) How to un-root in case I need to return the phone.
Any help would be appreciated, and apologies in advance if this is a repeated question. I just figured I'd ask because of the new update.
Thanks!
Skot in Seattle
Click to expand...
Click to collapse
I would think the easiest is to use the root injected rom from this forum: http://forum.xda-developers.com/showthread.php?t=1771687
It is what I did and I have full root access and stock rom with no counter tripped. Backup preroot will be difficult but as long as everything is set up with google, you should be able to get all of your contacts back but not settings. Once rooted, you can use titanium backup. Great program. If you want to unroot you can use the same method you used to root but you can just odin back to the original rom again. If you like my response please click on Thanks.
Thanks!
I took a look at the thread you sent me, and have contacted the original member to get step by steps, just to make sure I dont screw it up.
Hopefully it will work as desired.
Thanks for your help and response!
sekellas said:
I took a look at the thread you sent me, and have contacted the original member to get step by steps, just to make sure I dont screw it up.
Hopefully it will work as desired.
Thanks for your help and response!
Click to expand...
Click to collapse
The person who wrote the thread may or may not have time to give a more detailed run-through.
I used that thread to root my phone - honestly, all the instructions have already been given in it. I have never done anything like this and I just followed the instructions as given - the process is covered completely. I'm not sure what more they could tell you.
Not trying to be rude. Just understand that they have already provided a full guide and it might be more considerate to ask questions to the open forum about any step that is troubling you - that way anyone who has free time can answer.
Ok
Pennycake said:
The person who wrote the thread may or may not have time to give a more detailed run-through.
I used that thread to root my phone - honestly, all the instructions have already been given in it. I have never done anything like this and I just followed the instructions as given - the process is covered completely. I'm not sure what more they could tell you.
Not trying to be rude. Just understand that they have already provided a full guide and it might be more considerate to ask questions to the open forum about any step that is troubling you - that way anyone who has free time can answer.
Click to expand...
Click to collapse
Thanks for that, I guess I just wanted to make sure I wasn't leaving anything to chance. Since the phone is a pretty penny, I didn't want to be screwed if I tried to root and somehow screwed up the phone.
I'll see if he responds in the next few days, if not, I'll give it a go.
thanks again!
sekellas said:
Thanks for that, I guess I just wanted to make sure I wasn't leaving anything to chance. Since the phone is a pretty penny, I didn't want to be screwed if I tried to root and somehow screwed up the phone.
I'll see if he responds in the next few days, if not, I'll give it a go.
thanks again!
Click to expand...
Click to collapse
It's so easy, you'd be hard pressed to screw it up.
Step 1): Download the Samsung USB Drivers from their site
Step 2): Download the pre-rooted stock firmware from the previously listed link here at xda(make sure you get the 4.1 with root)
Step 3): Download ODIN
Step 4): Plug phone into PC and launch ODIN
Step 5): Click "PDA" and then browse to the firmware you downloaded
Step 6): Hit Flash.
Step 7): Wait, wait some more. Wait more.
Step 8): Watch phone reboot and sweat manically as its your first time and you think you've bricked your phone.
Step 9): Tinker like a madman when your phone comes back and you see its rooted.
Step 10 through ifiniti): Continue to tinker, eventually find rom manager and aftermarket roms. some good, some bad.
PM me if you want and I can walk you through it via IM or something. I can even throw you my rom, which is essentially stock with all the tmobile BS removed.
Awesome (Easy) walkthrough
osbosb said:
It's so easy, you'd be hard pressed to screw it up.
Step 1): Download the Samsung USB Drivers from their site
Step 2): Download the pre-rooted stock firmware from the previously listed link here at xda(make sure you get the 4.1 with root)
Step 3): Download ODIN
Step 4): Plug phone into PC and launch ODIN
Step 5): Click "PDA" and then browse to the firmware you downloaded
Step 6): Hit Flash.
Step 7): Wait, wait some more. Wait more.
Step 8): Watch phone reboot and sweat manically as its your first time and you think you've bricked your phone.
Step 9): Tinker like a madman when your phone comes back and you see its rooted.
Step 10 through ifiniti): Continue to tinker, eventually find rom manager and aftermarket roms. some good, some bad.
PM me if you want and I can walk you through it via IM or something. I can even throw you my rom, which is essentially stock with all the tmobile BS removed.
Click to expand...
Click to collapse
Hey osbob, thanks for that walkthrough... I wanted to make sure I was using the right pre-rooted stock firmware... would it be the
New! - October 2012 - 4.1.1 JellyBean
Note: This is based off of the stock image TMO T999UVDLJA
Perm Mirror: Download - root66_TMO_T999UVDLJA.7z
Click to expand...
Click to collapse
?
And then, if I need to send it back, I'd have to unroot the phone too, so I wanted to make sure I saved whatever I needed to. As for using yoru version without the bloatware, the bloatware doesn't bother me, since I use the Visual Voicemail, and the My Account features to manage the account for my wife and I. I just want to make sure I'm injecting the right stuff.
Thanks a lot for your help and the walkthrough above
Skot
sekellas said:
Hey osbob, thanks for that walkthrough... I wanted to make sure I was using the right pre-rooted stock firmware... would it be the ?
And then, if I need to send it back, I'd have to unroot the phone too, so I wanted to make sure I saved whatever I needed to. As for using yoru version without the bloatware, the bloatware doesn't bother me, since I use the Visual Voicemail, and the My Account features to manage the account for my wife and I. I just want to make sure I'm injecting the right stuff.
Thanks a lot for your help and the walkthrough above
Skot
Click to expand...
Click to collapse
You can use Odin to return it to stock.
Sent from my SGH-T999 using xda app-developers app
sekellas said:
Hey osbob, thanks for that walkthrough... I wanted to make sure I was using the right pre-rooted stock firmware... would it be the ?
And then, if I need to send it back, I'd have to unroot the phone too, so I wanted to make sure I saved whatever I needed to. As for using yoru version without the bloatware, the bloatware doesn't bother me, since I use the Visual Voicemail, and the My Account features to manage the account for my wife and I. I just want to make sure I'm injecting the right stuff.
Thanks a lot for your help and the walkthrough above
Skot
Click to expand...
Click to collapse
Perm Mirror: Download - root66_TMO_T999UVDLJA.7z <-- that's correct.
You can always run a debloated rom and then reinstall the tmobile specific stuff.
I just finished writing up an account of how I got my boot-looped/stuck Dinc to execute a Nandroid recovery after screwing up the partitions. Somehow I messed up the phone's partitions while attempting to install Jelly Bean.
I got lucky, and found some notes that led to me being able to recover my previous build of Gingerbread. You can read what happened, and what fixed it on my blog, here:
blogDOTswiftpassageDOTcom/2013/02/03/htc-incredible-jelly-bean-nearly-bricked/
Please pass the link along if it is useful. I'm not much for posting, but I've had so much help from this forum in the past, and I wanted to repay the favor, so I hope this helps a few folks.
skyeman said:
I just finished writing up an account of how I got my boot-looped/stuck Dinc to execute a Nandroid recovery after screwing up the partitions. Somehow I messed up the phone's partitions while attempting to install Jelly Bean.
I got lucky, and found some notes that led to me being able to recover my previous build of Gingerbread. You can read what happened, and what fixed it on my blog, here:
blogDOTswiftpassageDOTcom/2013/02/03/htc-incredible-jelly-bean-nearly-bricked/
Please pass the link along if it is useful. I'm not much for posting, but I've had so much help from this forum in the past, and I wanted to repay the favor, so I hope this helps a few folks.
Click to expand...
Click to collapse
I converted the link for you as it looks like it might be useful to someone.
http://blog.swiftpassage.com/2013/02/03/htc-incredible-jelly-bean-nearly-bricked/
tiny4579 said:
I converted the link for you as it looks like it might be useful to someone./QUOTE]
I appreciate the help getting it clickable, Tiny. Thanks!
If you read the whole post, do you think I'm correct in assuming that using too early a version of CWM is what led to my partitions getting pranged? My version of CWM is still v.2.5.0.5 As I wrote, it's my best guess that there may be an incompatibility between that version of CWM and the rom I initially tried ( cm-10-20130118-TINY-inc.zip) .
If so, I guess the next step is to find and execute the right steps to update CWM in the phone. Any guidance in that direction would be deeply appreciated.
Elliott
Click to expand...
Click to collapse
It shouldnt mess up your partitions but that recovery is incompatible with ICS and later. Things just wont work right. To update use ROM manager from the play store or twrp can be installed via goo manager or more reliably from a PB31IMG.zip. either is acceptable.
Sent from my Galaxy Nexus using Tapatalk 2
Hi everyone.
I hope it's OK for me to post a thread here. I had posted in the TMobile specific help forums yesterday but I noticed that these forums are much more active and I have a somewhat new problem.
My phone is intermittently connected to windows and listed as "QHSUSB_Bulk". I've come across some help threads on this issue for other phones that I'm working through, but I was really hoping to perhaps get some M8-specific guidance. I'm supposed to be studying for my medical boards right now, so I'd really appreciate some help that could save me some time.
Here's the thread that I posted yesterday: http://forum.xda-developers.com/tmo...ruu-error-152-unable-to-restore-tmob-t2869758
(mods please move/merge/close if appropriate).
Thanks!
PDD
PasDeDeux said:
Hi everyone.
I hope it's OK for me to post a thread here. I had posted in the TMobile specific help forums yesterday but I noticed that these forums are much more active and I have a somewhat new problem.
My phone is intermittently connected to windows and listed as "QHSUSB_Bulk". I've come across some help threads on this issue for other phones that I'm working through, but I was really hoping to perhaps get some M8-specific guidance. I'm supposed to be studying for my medical boards right now, so I'd really appreciate some help that could save me some time.
Here's the thread that I posted yesterday: http://forum.xda-developers.com/tmo...ruu-error-152-unable-to-restore-tmob-t2869758
(mods please move/merge/close if appropriate).
Thanks!
PDD
Click to expand...
Click to collapse
bricked, sorry
rbouza1 said:
bricked, sorry
Click to expand...
Click to collapse
What do you think about this sort of thing: http://forum.xda-developers.com/showthread.php?t=2582142
I'm trying to find the other thread I was referring to where the guy said his phone was in the same state as mine but was able to recover it. Edit: Ah it was this thread, but was applicable when I had Error 152, not QHSUSB. http://www.xxxx.com/htc-one-x/help/error-152-ruu-update-t2861685
Do you have any tips for avoiding this problem in the future?
I'll probably have to return, just want to learn at this point.
Thanks! PDD
PasDeDeux said:
What do you think about this sort of thing: http://forum.xda-developers.com/showthread.php?t=2582142
I'm trying to find the other thread I was referring to where the guy said his phone was in the same state as mine but was able to recover it. Edit: Ah it was this thread, but was applicable when I had Error 152, not QHSUSB. http://www.zpiiets.com/htc-one-x/help/error-152-ruu-update-t2861685
Do you have any tips for avoiding this problem in the future?
I'll probably have to return, just want to learn at this point.
Thanks! PDD
Click to expand...
Click to collapse
I don't know what you did to get there, be careful with firmware and hboots.
rbouza1 said:
I don't know what you did to get there, be careful with firmware and hboots.
Click to expand...
Click to collapse
Tried to run an RUU. Thought it would be the safe route ha!
PasDeDeux said:
Tried to run an RUU. Thought it would be the safe route ha!
Click to expand...
Click to collapse
did you unplug phone before finishing ?
rbouza1 said:
did you unplug phone before finishing ?
Click to expand...
Click to collapse
Nope. I gave a pretty detailed summary of stuff that happened before the phone became unresponsive in the thread from my OP. I think the main problem was thinking I could update versions since the RUU said it "update." Should have stuck with same version RUU. Don't know why that would completely brick the phone, though. And it only bricked after the time I ran it and it said "congrats everything worked!"
RUU are normally the safest way to flash devices. If it was bricked because of it. It could be any number of things.
Corrupt RUU
Premature disconnect from either end
Or bad emmc table
I went through three m8 first two ended up in QHUSB mode and the third after playing it safe for while attempted again and it worked out just fine. All I was trying to do was flash the international 4.4.3 firmware zip.
First two came from T-Mobile while the third HTC sent it out to me. So maybe that made a difference, I did change the model and CID to that of the international version the third time so if that made a difference I wouldn't know for sure.