I seem to have temporarily bricked my gtab. When attempting to nvflash restore all goes well until I unzip the .bat file that is needed. When unzipped it seems to change the format of the file and it won't run. I've done a search on this and have heard of other people having this problem so I know it is solvable, but I just can't seem to get it to work.
Any help would be much appreciated.
Thanks!
deadeye,
Roebeet's original 5.0.0 thread in Developer Forum has a bunch of info as well as several links to posts others of us have put together about dealing with this problem.
There also is another post near the top of Developer I put together on the USB .zip files needed and where to get them.
And I know I have written a bunch of help messages with detailed info to other
folks with your problem.
Check these out and let us know if you have questions. I'm sure it can be brought back, but may take some research and learning.
Rev
got it
Thanks for your response!!!
First I want to appologize because I'm sure somewhere this problem has been solved. My search skill are less than great so I was not able to find the answer or even the problem before so here we go....I rooted my atrix using Pete's Motorola Root Tools and everything worked perfectly. Then without thinking I updated the phone to 2.3.6 from I believe 2.3.4 (I didn't pay attention like I should have). After the update I am no longer able to get to any of the hidden apps. They are still there installed it's like the SU function isnt working anymore.
I tried using Pete's tool to unroot the phone hoping that I'd be able to get the use of the apps again but I get the following error and I'm not sure what to do at this point.
ERROR: /restore/ backup doesn't exist or is incomplete!
These files must be downloaded and saved to your computer in a /restore/ subfolder
Download links can be found in the Help menu in this program
When I look in the Help menu it only shows downloads for DROID 3 versions 5.5.959 and 5.6.890
does anyone have any idea how to proceed? again I'm so sorry for the lack of experience on my part. BTW the phone is currently working with no issues other than me not getting the installed apps.
Thank you in advance for any help.
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
Hey Guys,
I'm having a couple of issues with setting up adb on my Linux Box (Xubuntu 12.04) I downloaded Android SDK and installed Platform-Tools. I've tried most of the methods on XDA but when I "./adb devices" I get nothing. I have a Micromax A87 which is a rebranded version of Mito A78 (Anybody heard of it???).
I would like help with another issue too. I recently got into theming, I edited some .pngs (not 9s) and compiled it, then signed it and zipaligned it but when I put it in /system/app and rebooted, it worked only partially. The one's with the default mode as RGB work, but the one's with the default mode "indexed" didn't. Does Anybody have any Ideas???
BTW, I use Gimp and I change the mode to RGB before editing them.
Thanks in Advance...
JasonKZLY said:
I would like help with another issue too. I recently got into theming, I edited some .pngs (not 9s) and compiled it, then signed it and zipaligned it but when I put it in /system/app and rebooted, it worked only partially. The one's with the default mode as RGB work, but the one's with the default mode "indexed" didn't. Does Anybody have any Ideas???
Click to expand...
Click to collapse
Might be worth reading this before starting another thread - [GUIDE] - XDA New User Guide - Getting started on XDA, I know you're new, you're obviously eager to do something based on your other thread, but keep this in mind, nothing you've got to ask (which so far) hasn't been asked or discussed many a time before, so if themeing is what you want to get into, click the second link in my sig, read it, bookmark it then try and put into practice what it is you're trying to learn, and if at first you don't succeed, starting a new thread to ask a question that you'll probably figure out the answer to whilst you wait for someone to reply with an answer you could have probably found by typing your thread title into Google, isn't going to speed things up or help you learn.
There are some links to using apktool with Linux in my guide btw which should be of help.
THANKS, XPERIENCED!!!
I already read your theming guide and about 5 others on XDA Forums and I decided to get a better understanding of Themes.
I still face an issue, I can't setup ADB! I've tried most of the methods on XDA Forums and everything I can think of, it isn't working. I did use Google, most of them simply don't work. My question is not "How do I set-up ADB on my Linux?", It's "I can't setup ADB, can anybody help me?"
*sigh* Can anybody please help me???
EDIT: Solved it, adb working now!
Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one
Morecrabs said:
Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one
Click to expand...
Click to collapse
1. No
2. Yes
You need to be on stock ics firmware for the NV edit to succeed and stick.
Use Android 4.0.4 Blur_Version.77.8.14.XT897.Sprint.en.US - http://sbf.droid-developers.org/phone.php?device=3
If you're downgrading from jellybean, you have to remove the line with flash gpt_main0.bin from the xml file, otherwise the flashing via rsdlite will fail.
Code:
[STRIKE]<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="6C05E70F1DCC59AD92B0BBEC4E6100ED" />[/STRIKE]
The firmware thread is here: http://forum.xda-developers.com/showthread.php?t=2095536
Then you can follow this (RadioComm):
http://forum.xda-developers.com/showthread.php?t=2166542
or this (CDMA WS) guide:
http://forum.xda-developers.com/showthread.php?t=2386871
After it's done, you should flash the stock Android 4.1.2 via rsdlite, then install CM10.2 (or any other custom ROM) again.
soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?
Morecrabs said:
soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?
Click to expand...
Click to collapse
That development ID is simply for identifying your device under debugging circumstances like ADB, every device has them. Also, flashing another ROM changes this value.
Sent from Google Nexus 4 @ CM11
ok so that was a dumb decision to come to, but its not something id ever seen on any of my other android devices, Droid 1,2,4 samsung captivate glide, so i figured it was related to the developer Models
Do I need to run my copy of radio Comm on a 32 bit machine to accomplish this hacking?
my 64 bit machines seem to have driver related issues with the software
was wondering if anyone could help me setup the drivers, I keep getting errors with Radio comm and cdma workshop, and it all boils down to driver issues, with cdma workshop i cant get the QC port setup because IM missing a driver, and with radio comm, I cant get it to communicate properly with the phone once i boot into fastboot any help suggestions? ive installed the moto drivers and setup on a PC with a 32 bit version of win7 starter to allow radio comm to setup properly
In radio comm it will ID the phone as xt897 and i can get software version if its booted into OS, but it will do nothing else
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http://bork.cs.fau.de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
Code:
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https://github.com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
EDIT2: This is now included as "unlock-us-gsm" in CM12.0 and up on XT897, XT907 and XT926. To use it run "unlock-us-gsm" in a root shell:
Code:
[email protected]_c:/ # unlock-us-gsm
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Reading value of NV-item 8322...
GSM locked in the US: 1
Setting value of NV-item 8322 to 0...
Reading value of NV-item 8322...
GSM locked in the US: 0
Setting logging_mode to usb...
Regards,
Michael
stargo said:
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer
Click to expand...
Click to collapse
Excellent! I picked a good day to try to figure out how to do this, I was making notes of all the various steps (install ics on phone, use radiocomm on pc, install jb on phone, then cm on phone) when I got to this post and realized I won't need to do any of that, thanks much!
Terminal Emulator Question
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http //bork cs fau de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
[CODE
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
[/CODE]
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https //github com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
Regards,
Michael
Click to expand...
Click to collapse
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.
DroidRazrMv said:
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.
Click to expand...
Click to collapse
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.
arrrghhh said:
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.
Click to expand...
Click to collapse
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.
DroidRazrMv said:
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.
Click to expand...
Click to collapse
Still confused as to where you're having issues - we are both talking about the same post. If you look, kabaldan's post redirects to the one I am referencing....
So once these steps are used to unlock the phone, which carriers can be used and how does flashing of carrier info occur?
Just want to say thanks again Michael. I just got my new Photon Q back from having sim card slot installed, ran your program and it worked perfectly on 21OCT2014 CM nightly.
I did also change a couple settings in the phone menu too, cuz I put an AT&T sim card in it, but sprint kept calling me to activate. Seems to be working well now, but not sure I understand everything, does this seem right - in regular CM11 settings menu under Mobile network settings, I set Preferred network type to "GSM/WCDMA Auto".
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
Click to expand...
Click to collapse
Samsung Galaxy Note Edge Developer Edition 4.4.4 vzw
I use FM pro with root option checked.
I noticed that APN was not editable or add'able. Then looked into ways of fixing. I read somewhere to use BuildProp Editor and make a backup of build.prop, then edit it.
I installed BP editor and tried to make the backup, it failed. So I thought maybe it's not getting access, so I tried making it a system app, then tried the backup again, failed again. Then I made it a user app again and tried the option in FM pro to make system folders writable, then tried the BP backup again, success. At that point I just decided to back out of BP editor and check with FM pro to find the backup file, upon entering I found only the backup file on emulated 0, When normally it shows both 0 and legacy within emulated. I couldn't find legacy at all freaked out and deleted the backup made by BP, then I reloaded FM pro, still not showing legacy, got panicky at that point because lots of stuff is GONE off to visit Elvis and all the greats. Now I'm in the black, I try uncheck in the root and writable option in FM pro and legacy along with 0 are showing together again with matching files as is the norm, rechecked options and poof GONE again, only an empty 0 dir.
Reboot did nothing, runs as normal, boots and goes good. No noticeable issues with any apps or system. But I'm dumbfounded as to WTF is happening here. I made no changes to the actual build.prop. Also I noticed the re'entering BP Editor the backup was not showing up that's when I checked into FM Pro to find said backup, saw it and deleted it.
Any help would be greatly appreciated.
Vorridor said:
Samsung Galaxy Note Edge Developer Edition 4.4.4 vzw
I use FM pro with root option checked.
I noticed that APN was not editable or add'able. Then looked into ways of fixing. I read somewhere to use BuildProp Editor and make a backup of build.prop, then edit it.
I installed BP editor and tried to make the backup, it failed. So I thought maybe it's not getting access, so I tried making it a system app, then tried the backup again, failed again. Then I made it a user app again and tried the option in FM pro to make system folders writable, then tried the BP backup again, success. At that point I just decided to back out of BP editor and check with FM pro to find the backup file, upon entering I found only the backup file on emulated 0, When normally it shows both 0 and legacy within emulated. I couldn't find legacy at all freaked out and deleted the backup made by BP, then I reloaded FM pro, still not showing legacy, got panicky at that point because lots of stuff is GONE off to visit Elvis and all the greats. Now I'm in the black, I try uncheck in the root and writable option in FM pro and legacy along with 0 are showing together again with matching files as is the norm, rechecked options and poof GONE again, only an empty 0 dir.
Reboot did nothing, runs as normal, boots and goes good. No noticeable issues with any apps or system. But I'm dumbfounded as to WTF is happening here. I made no changes to the actual build.prop. Also I noticed the re'entering BP Editor the backup was not showing up that's when I checked into FM Pro to find said backup, saw it and deleted it.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the Samsung Galaxy Note Edge at http://forum.xda-developers.com/note-edge . Because your issue might be related to root and permissions matters specific to the VZW variant, I suggest you post your question with all relevant details in the Verizon subforum there at http://forum.xda-developers.com/note-edge/verizon-note-edge-android-development where the experts familiar with your device will be best able to guide you.
Good Luck!
Mike B. said:
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble but fortunately there is an XDA area dedicated to the Samsung Galaxy Note Edge at http://forum.xda-developers.com/note-edge . Because your issue might be related to root and permissions matters specific to the VZW variant, I suggest you post your question with all relevant details in the Verizon subforum there at http://forum.xda-developers.com/note-edge/verizon-note-edge-android-development where the experts familiar with your device will be best able to guide you.
Good Luck!
Click to expand...
Click to collapse
Thank you, I did post in that area, and no hits yet. I posted here in hopes that it would get more attention to a possibly wide scale issue in newer models of android OS, as only a few people have this particular variant of the device. I'm not sure but it's probably not carrier specific.
Again thank you for your time in reading this and would be greatfull for any further technical input you or others may have.
Vorridor said:
Thank you, I did post in that area, and no hits yet. I posted here in hopes that it would get more attention to a possibly wide scale issue in newer models of android OS, as only a few people have this particular variant of the device. I'm not sure but it's probably not carrier specific.
Again thank you for your time in reading this and would be greatfull for any further technical input you or others may have.
Click to expand...
Click to collapse
No member can respond to you in this XDA Assist area as explained in the "Purpose of XDA Assist" thread at http://forum.xda-developers.com/showthread.php?t=2764768.
Because Verizon devices often have restrictions, such as locked bootloaders, not found on other models, the VZW Forum might be your best bet, but you might need to wait longer than a mere six or seven hours before anybody finds time to comment on your posts.
Thread closed.