Develop Bugs

[SOLVED] BELL QCN Backup Needed

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

Wouldn't boot: Partitions screwed up: fixed it this way:

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

[Q] Rooting 8.3.0

Sorry for the seemingly noob question - I am a very experienced user and have read the entirety of the KFHD 8.9 android dev and Q&A forums and cannot find a satisfactory answer. I want to root my new KFHD8.9 (on 8.3.0) and then install TWRP and a new launcher etc and then install CM10 (when it has audio). I see that there is a tutorial but that appears to be for 8.1.4. Also, I see that a number of users have repeatedly failed to gain root and/or cannot access their OS. I have never had difficulties rooting any of my devices but this one looks like it will be much more complicated.
I know it is a lot to ask but could someone possibly provide the (working) steps to root the KFHD8.9 which is already on 8.3.0.
Thanks in advance

apd said:
I know it is a lot to ask but could someone possibly provide the (working) steps to root the KFHD8.9 which is already on 8.3.0.
Thanks in advance
Click to expand...
Click to collapse
Had absolutly no problems with 8.3.0 following those steps (choose second option for tablets). Some error messages occure. If it does not work try to reboot and do it again (-> that was the key for me)
Those reporting 'real' problems (=device not working ...) tried to reflash a new bootloader (TWRP) which is digging a lot deeper into the system than rooting.

bighead2k said:
Had absolutly no problems with 8.3.0 following those steps (choose second option for tablets). Some error messages occure. If it does not work try to reboot and do it again (-> that was the key for me)
Those reporting 'real' problems (=device not working ...) tried to reflash a new bootloader (TWRP) which is digging a lot deeper into the system than rooting.
Click to expand...
Click to collapse
Thanks. I will try that this evening. I suspect I will also want to install TWRP - is there a 'safe' way to do that?

apd said:
Thanks. I will try that this evening. I suspect I will also want to install TWRP - is there a 'safe' way to do that?
Click to expand...
Click to collapse
I just followed Hashcode's guideline (link). For me it's working 100% as it should. But I've read that some people had trouble.

bighead2k said:
I just followed Hashcode's guideline (link). For me it's working 100% as it should. But I've read that some people had trouble.
Click to expand...
Click to collapse
Excellent. Have now rooted (bored at work!) following those steps. 2 main things to watch out for - ignore the many error messages and make sure to follow the instructions typing in the commands exactly - I missed them first time :silly:

LG G4 Root?

Hello XDA community,
I recently traded in my old iPhone for this new LG G4, and am so glad to be converted from iOS to Android! Anyways, one of the main reasons I switched is because root access would enable me to maximize the potential of my phone. The only problem is...I have looked vastly throughout XDA and other Android developer havens for root guides and have gotten so confused as to where to start. Can somebody direct me to the right place, or even better, guide me through the process?
Thanks!
(I am using the Verizon G4 (VS986) with Android 5.1.)

DId you have a good look through this thread?
http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
It seems daunting but the first things you can do prior to the flashing are
-Get the software you need installed and tested
-Learn how to put your phone into download mode
-test to make sure your phone can communicate with your computer the way it should
-Download all the files you need (stock kdz and matching rooted image version)
Take the time to read each step, and if you have any questions, ask before you proceed, not after you have completed the step.
Good luck! The group here is very helpful so do not hesitate to ask.

goofball2k said:
It seems daunting but the first things you can do prior to the flashing are
Click to expand...
Click to collapse
I will definitely look into that thread! Quick question, what exactly is flashing? I know it has to do with modifying the operating system..but I honestly do not understand the purpose and benefit. Could you explain that to me?

Flashing is basically copying OS onto your phone and installing it.

Okay. So in this root you copy an OS with root permission?

cl_miller said:
Okay. So in this root you copy an OS with root permission?
Click to expand...
Click to collapse
Yes. With this method, you are basically putting a portion of the OS on that is already rooted. That is why it is important to make sure you have the correct versions.

Done?
I followed all of the steps provided in the link you shared, and believe that my device is now rooted! At least, I think and hope. How can I be sure? And if it was successful, what should I do next to make use of my root access?
Thanks again

You should see the SuperSU app. Open it, it may/should prompt you to update.
Otherwise, download root checker from the play store

Done! Now, are there any resources for what I can do next?

Help Tech-Savvy NOOB get started

I have an old Sony Xperia M C1905 that I want to root/load a custom, cut-down ROM to free up space for the Apps that seem to be growing with every update. I am a NOOB (as you say) to installing custom F/W on my phone, BUT I am tech-savvy. What I need is access to a set of instructions/tools that I can use with my phone and PC combination. I realise that this is an old phone and you are trying to help, but for me it is frustrating when all the links to tools from the threads seem to be dead or don't work. Please can someone have a read and let me know a way to do this that has a set of working tools. Thanks
My PC is a MS Windows 10 laptop – If necessary, I could resurrect an old laptop and install Linux on it, if that is a simpler approach.
I have had a look at what is available and will probably load the ROM from:
https://forum.xda-developers.com/xperia-m/orig-development/rom-slim6-marshmallow-t3418258
What I think I need to do (and have tried to start) is:
1. Root the phone.
2. Backup the current ROM.
3. Unlock the boot-loader.
4. Load the Slim6 ROM.
To do 1. I have tried two methods, the first recommended from the backup thread and a second found by searching.
i. Easy Rooting toolkit: https://forum.xda-developers.com/showthread.php?t=2292598 but the download link for DooMLoRD_Easy-Rooting-Toolkit_v17_perf-event-exploit.zip. The Download site for this tool tells me (eventually) that the file has expired or has been deleted by the owner - so i can't get this tool. Any Ideas How to get this?
ii. Also tried: https://forum.xda-developers.com/showthread.php?t=2529561 but for me, the cydia impactor tool does not see my phone or have any options. Yes, I have enabled - and allowed USB debug mode, before you ask. And yes the PC can see the phone so the connection is good.
To do 2. I am proposing to use the instructions from this thread: http://forum.xda-developers.com/showthread.php?t=2292598 Please confirm this is still valid.
iii. [Update] Also tried rooting by using this thread: https://forum.xda-developers.com/showthread.php?t=2457174 but this requires Framaroot 1.5.3, When I try and download this, the download site says: "The file link that you requested is not valid. Please contact link publisher or try to make a search."
Update 2. Managed to get a download of Framaroot, installed, but does not work for Xperia M with Android 4.3. Any idea of a way forward?
To do 3. I am proposing to use: https://forum.xda-developers.com/showthread.php?t=2484622 Please confirm this thread is still valid - and the best approach.
To do 4. https://forum.xda-developers.com/xperia-m/orig-development/rom-slim6-marshmallow-t3418258 - Please let me know if there is a more appropriate ROM to install to free up some space.

You can follow this link :
And for root, I think slim6 is pre rooted. Means in Developer options, select root for adb and apps.

What about backing up the current ROME?
Thanks for your reply, but to my understanding this just does 2. & 3. from my list. Most of the ROM installation guides say to take a backup of the current ROM so that you can restore the original system.
To do this I need to get root access with the current build. Is this now impossible?
Maybe I just need to bite the bullet and just not bother with the backup.

You should definitely take a backup.
This is because of the TA partition. As soon as you unlock the bootloader of your phone it will format the TA partition, so without the backup you won't be able to restore it which might be needed. Using a TA backup from another phone will NOT work.
So you are right about the steps, you need to root the phone, backup, unlock the boot loader and flash the new ROM. I didn't check all of the links you posted now, but if Framearoot is not working for you you might want to try out iovyroot. Also check that you downloaded the right tool to root for your Android version.
If it's still relevant and you need any additional help I'll post some instructions for you another day.

Thanks for the confirmation of the process.
Iovyroot is not a root method I have tried. I will Investigate tomorrow.
I will post back here when I have tried it.
I have tried a couple of versions of Framaroot, one recommended version for the phone, and the latest version I could find. Neither worked.

Maninfrontofpc said:
Thanks for your reply, but to my understanding this just does 2. & 3. from my list. Most of the ROM installation guides say to take a backup of the current ROM so that you can restore the original system.
To do this I need to get root access with the current build. Is this now impossible?
Maybe I just need to bite the bullet and just not bother with the backup.
Click to expand...
Click to collapse
You don't need to get root access to have a backup. Just unlock your bootloader and install cwm or twrp through fastboot and take backup with help of it. Now if you are on stock rom and you need root anyway, you can use towelroot. And then install supersu from playstore. OR flash superSU through cwm. In that case no need to install towelroot.

Is nidhoegg mistaken?
Please can you confirm that the TA partition will Be NOT be formatted when I unlock the boot loader?

Maninfrontofpc said:
Please can you confirm that the TA partition will Be NOT be formatted when I unlock the boot loader?
Click to expand...
Click to collapse
Why are you so much worried about TA partition?

My understanding is that this contains various sets of system data including: S/W signatures for the Sony Apps (if I want to restore the Sony ROM to the phone); calibration data of the various devices on the phone - accelerometer etc. So surely, even if just for the calibration data, I would not want to lose this data even if I loaded a custom ROM - I have no way of re-calibrating the devices, so would need the factory acceptance calibration values.
Am I mistaken?

TA backup for our device isn't necessary. Actually I don't know anyone from xda taking TA backup. TA backup is for newer sony devices and z series devices. In those devices, somethings like sony camera wouldn't work if you lose drm keys. It's not the case with our mobile.

Are you saying that all the threads from when this was the current phone are wrong, and I don't need to backup this partition?
TA = Trim Area; as well as holding the DRM Keys/S/W signatures, my understanding is that at contains Trim data to adjust the various sensors on the phone to read accurately. I have been led to believe that these are written during the automated Factory Acceptance Testing to adjust for small differences in the components on the phone, and are unique to the device. Surely if I lose this data the sensors will not read accurately.
Is this wrong?