Hi all,
A week ago I followed this thread to unlock and root my phone. All went well and I flashed Venom 4.3.0 but now cannot receive calls (I was told I need the international firmware?). Beforehand, my phone had an OTA update to Lollipop, and I was stupid and did not make a backup before flashing. I've looked and found some different options, one of which is a stock recovery here.
The biggest problem I'm having now is that I cannot get it to connect to the PC where I can copy over files. It says that the device has stopped responding or has been disconnected. I can delete and view everything, however. In searching around, it looks like some have had this issue with some corrupt files, but I cannot even copy a .jpg or empty .txt file. I have tried uninstalling HTC Sync and HTC Sync Manager, leaving them installed, uninstalling and leaving drivers, using just the drivers here, multiple cables, ports, and even different computers. Windows tries to install Android 1.0 when I connect while in the bootloader or TWRP, and it doesn't show up in explorer (I can see it in device manager as an android device).
Any help would be greatly appreciated!
rhughes93 said:
Hi all,
A week ago I followed this thread to unlock and root my phone. All went well and I flashed Venom 4.3.0 but now cannot receive calls (I was told I need the international firmware?).
Click to expand...
Click to collapse
I don't think firmware has much to do with it. Folks have had issues with some "international ROMs" (including ViperOne) on AT&T's network; and flashing various firmwares doesn't seem to help.
Best explanation I've seen, is that it has to do with changes AT&T is making to their network in preparation for rollout of Voice over LTE (VoLTE, or "HD Voice" and AT&T calls it).
I think Team Venom was looking into the problem. But I don't know if anything ever came of that. I'd say your best bet is to try another ROM, or the stock AT&T ROM (as you've already suggested).
rhughes93 said:
The biggest problem I'm having now is that I cannot get it to connect to the PC where I can copy over files. It says that the device has stopped responding or has been disconnected. I can delete and view everything, however. In searching around, it looks like some have had this issue with some corrupt files, but I cannot even copy a .jpg or empty .txt file. I have tried uninstalling HTC Sync and HTC Sync Manager, leaving them installed, uninstalling and leaving drivers, using just the drivers here, multiple cables, ports, and even different computers.
Click to expand...
Click to collapse
Try uninstalling all HTC software (Sync and HTC drivers). Then go to Device Manager, find the device, and select the option to manually install the drivers, and pick the generic Android MTP Device drivers. See if that gets adb/fastboot working.
Another option, is use a removable SD card and card reader, put the desired ROM on the card using your PC. Then insert card into the phone and flash the ROM in TWRP.
redpoint73 said:
I don't think firmware has much to do with it. Folks have had issues with some "international ROMs" (including ViperOne) on AT&T's network; and flashing various firmwares doesn't seem to help.
Best explanation I've seen, is that it has to do with changes AT&T is making to their network in preparation for rollout of Voice over LTE (VoLTE, or "HD Voice" and AT&T calls it).
I think Team Venom was looking into the problem. But I don't know if anything ever came of that. I'd say your best bet is to try another ROM, or the stock AT&T ROM (as you've already suggested).
Try uninstalling all HTC software (Sync and HTC drivers). Then go to Device Manager, find the device, and select the option to manually install the drivers, and pick the generic Android MTP Device drivers. See if that gets adb/fastboot working.
Another option, is use a removable SD card and card reader, put the desired ROM on the card using your PC. Then insert card into the phone and flash the ROM in TWRP.
Click to expand...
Click to collapse
Thanks for your help. I wasn't able to flash from the SD card for some reason - kept getting a failure. I tried manually installing drivers, but it was no different. I did figure out that even though the PC didn't recognize the phone in fastboot, adb/fastboot still worked and I was able to push files that way. Unfortunately, I tried flashing SkyDragon and still don't receive calls (though it thinks I'm on Tmobile - maybe I missed a step in my haste), and haven't been able to get that stock ROM I linked before to flash. Though, somewhere along the way it wiped Venom so that it didn't re-apply any of my previous settings and now I can directly copy files using the PC instead of pushing. Not sure exactly how that makes sense, but it'll make things easier I think.
I definitely think I'm getting closer, or at least have some options now that I can copy files either directly or pushing. I just have to find a ROM that works and that I can actually flash.
rhughes93 said:
I wasn't able to flash from the SD card for some reason - kept getting a failure.
Click to expand...
Click to collapse
What version of TWRP? Most common reason for ROMs failing to flash is outdated TWRP version.
rhughes93 said:
Unfortunately, I tried flashing SkyDragon and still don't receive calls (though it thinks I'm on Tmobile - maybe I missed a step in my haste).
Click to expand...
Click to collapse
You probably picked T-Mob in the AROMA installer when you flashed the ROM. You can flash again, and pick either AT&T, or the "other GSM" or whatever its called works fine for me on AT&T.
rhughes93 said:
and haven't been able to get that stock ROM I linked before to flash.
Click to expand...
Click to collapse
What you linked was a stock nandroid backup, not a flashable ROM. There is a distinct and important difference.
With a nandroid, it has to be placed in the exact right location, then you pick RESTORE in TWRP instead of INSTALL. If the nandroid folder isn't copied to the exact right location, TWRP won't see it when you select RESTORE (you can't browse for the file like you can a ROM).
The easiest way to determine the "exact location" for the nandroid is to make a backup in TWRP (if you haven't already) examine the folder structure in the folder named "TWRP" and copy the downloaded files (from the thread you linked) to the corresponding location.
But basically, all the nandroid files need to be unzipped than copied to: TWRP/BACKUPS/serial number
Where "serial number" is the actual serial number for your device. The TWRP folder can be on your internal storage, or on the removable SD, depenging on what location you choose in TWRP settings (internal storage is default).
I was using TWRP 2.8.6.0, but the issue was really what you described about it being a recovery and not a flashable ROM. I had figured that out, but missed the exact location because I had not created a backup, and therefore the folder with the serial number was not there. So, I was able to sort that out and restore and all is well again. Thanks for that!
As far as SkyDragon goes, I definitely picked AT&T in AROMA, but there are a few places in the software that still reference T-Mobile, such as in the software version under "about". Perhaps that's just the way it is. I'm still annoyed that I can't get it to work, as I'd rather use a custom ROM, but I can tinker around more now that I have made a proper recovery and can always roll back. Maybe now that I have a proper recovery, I can branch out more. I'll also try re-flashing SkyDragon and choose the "other GSM" to see if it works.
Related
Ok, last weekend I wanted to go all out and unlock my MoPho and install an ICS build (I had previously only rooted it). Everything went well and I got Jokersax 0.7.1 installed; there was only one problem, no WiFi. I tried several trouble shooting steps and couldn't get it to work, so I re-flashed with 0.7.0 and then I had WiFi....but no phone service.
I then saw the post for the CDMA fix and tried: Flashing twice, nothing; Flashing 0.3.1 and then flashing 0.7.1, still nothing. I tried modifying the build file, but the only way I could get that to work was to unzip the file, modify it, save it, then re-zip it...and then it wouldn't install (when I tried to modify it on the phone it says read only file, and when I copy the file to my computer and modify it, it won't let me replace the file on the phone).
The phone is currently functioning on 0.3.1 (with WiFi and phone), but a lot of the features in the menus don't work in this version.
I would really like to get one of the newer builds running, AND have WiFi and be able to use my phone...anyone have any ideas?
PS I love ICS on this phone; it's like having a whole new phone.
I think you have to clean you cache's and whatnot, and do a fresh install, not be coming from another rom. Read about it in the development area of the forum...
Neva Eva Forget 1984 said:
I think you have to clean you cache's and whatnot, and do a fresh install, not be coming from another rom. Read about it in the development area of the forum...
Click to expand...
Click to collapse
Oh, I didn't mention that, but I did all of the cache wipe, factory reset etc (I was following an install guide) when I first installed, and also when I tried to reinstall. I also tried installing 0.3.1 then rebooting and installing latest version (one recommended fix), which didn't work either.
Most of the threads I have found are a little old, so I was hoping someone had a new "fix" to try.
Try another kernel , preferably oleg's.
Sent from my MB855 using Tapatalk 2
azguy90 said:
Ok, last weekend I wanted to go all out and unlock my MoPho and install an ICS build (I had previously only rooted it). Everything went well and I got Jokersax 0.7.1 installed; there was only one problem, no WiFi. I tried several trouble shooting steps and couldn't get it to work, so I re-flashed with 0.7.0 and then I had WiFi....but no phone service.
I then saw the post for the CDMA fix and tried: Flashing twice, nothing; Flashing 0.3.1 and then flashing 0.7.1, still nothing. I tried modifying the build file, but the only way I could get that to work was to unzip the file, modify it, save it, then re-zip it...and then it wouldn't install (when I tried to modify it on the phone it says read only file, and when I copy the file to my computer and modify it, it won't let me replace the file on the phone).
The phone is currently functioning on 0.3.1 (with WiFi and phone), but a lot of the features in the menus don't work in this version.
I would really like to get one of the newer builds running, AND have WiFi and be able to use my phone...anyone have any ideas?
PS I love ICS on this phone; it's like having a whole new phone.
Click to expand...
Click to collapse
Hello! Okay, I'm assuming you're on sprint, meaning you obviously want cdma. .7.1 doesn't have working wifi. As of .7.0 you don't need 3.1 first. I would suggest trying the following...
Download .7.0 cdma version. Make two copies.
Download 7zip
Right click one rom, choose 7zip and open.
Browse to the buildprop, right click, click edit.
Find the default network portion, make sure the value is 7 and ensure it doesn't have a pound sign in front of that line.
Save the file and hit ok when it prompts you if you wanna save the changes to the zip.
Do the same with the other one except make the value 4.
Throw both of em on your sdcard.
Wipe cache, system, data, dalvik, then flash the value 7 one first.
Boot up, see if everything is peachy (it should be)
If that doesn't work wipe everything again and try the 4 value one. Let me know what happens for ya.
Also, go into dialer and type *#*#4636#*#* and make sure the network type is set to cdma auto prl. For whatever reason sometimes its not. It'll take a reboot to reflect that change, though.
Acvice said:
Hello! Okay, I'm assuming you're on sprint, meaning you obviously want cdma. .7.1 doesn't have working wifi. As of .7.0 you don't need 3.1 first. I would suggest trying the following...
Download .7.0 cdma version. Make two copies.
Download 7zip
Right click one rom, choose 7zip and open.
Browse to the buildprop, right click, click edit.
Find the default network portion, make sure the value is 7 and ensure it doesn't have a pound sign in front of that line.
Save the file and hit ok when it prompts you if you wanna save the changes to the zip.
Do the same with the other one except make the value 4.
Throw both of em on your sdcard.
Wipe cache, system, data, dalvik, then flash the value 7 one first.
Boot up, see if everything is peachy (it should be)
If that doesn't work wipe everything again and try the 4 value one. Let me know what happens for ya.
Also, go into dialer and type *#*#4636#*#* and make sure the network type is set to cdma auto prl. For whatever reason sometimes its not. It'll take a reboot to reflect that change, though.
Click to expand...
Click to collapse
Coincidentally, I'm having this exact problem at the moment. I followed your directions exactly. and Both 7 and 4 didn't restore service.
ryan8r said:
Try another kernel , preferably oleg's.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
this worked for me
recovery just says something is wrong, look at log?
I tried a few versions (of the backup sets), same error.
What am I doing wrong? How do I fix it? :crying:
Log from recovery run...
Starting recovery on Thu Aug 16 21:58:52 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
fuzzynco said:
recovery just says something is wrong, look at log?
Click to expand...
Click to collapse
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
I kind of follow... RA is an image backup
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
fuzzynco said:
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
Click to expand...
Click to collapse
In reply to the bolded part: Basically, yes. AR's nandroid places the backups in a folder with your phone's serial as the folder name. Attempting to restore any backup from a folder with any other name will fail to prevent the issues I mentioned above.
I do not and have not ever used Titanium Backup, so in regards to that, I can't be of any help.
If you have a linux machine, you can mount the data.img from any of your backups and then copy all the files from /data/app and data/data to your phone. This will restore most of your apps, and app data/settings. There will still be a few things you'll have to redo from scratch, and this may not work 100% for every app on your phone, but at least this way you don't have to redownload every single app and manually redo all your settings...
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
fuzzynco said:
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
Click to expand...
Click to collapse
not sure...
I couldn't get ViperROM 1.0.3 to not crash (com.android.phone kept crashing).
Trying a couple of others that are prerooted and deboated. So far the ICS &
Sense 3.6 looks fine. Still have the 'social network' stuff to freeze though,
Could I do something like make a zip (from adb shell) of the user apps
/data/app & /data/data directories (to preserve the unix permissions).
and leave that on fat32 sd card? Then merge that into the zip for the
rom to be installed so the installer will reload them?
Would I need to add lines to the installer script to have it load /data (with
the subdirs ../app and ../data)?
hmms maybe better to make a seperate zip to preinstall my saved
/data subdirs? Can I copy the ROMs installer binary and build
a installer script to mount /data, then install the /data directory,
umount /data?
a.mcdear said:
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
Click to expand...
Click to collapse
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
This app might work. I use it and it works great but I'm not sure if it restores data.
synisterwolf said:
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
Click to expand...
Click to collapse
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
a.mcdear said:
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
Click to expand...
Click to collapse
Good to know. Thanks
In my case, the backup is from a device that i bricked totally. couldnt get into download mode so im thinking they will just use it as parts
Sent from my iPhone...
Hi all,
I didn't find any relevant threads through searches, so I'm reduced to asking for help. Please!
My DNA's been running great on Newt's ROM. I'm S-OFF, rooted, using CM, and all's been great. I'm on T-Mo. I installed the most recent patch on the OP page and, now, my phone won't connect to wifi and in settings>storage it shows "unavailable" for storage.
I've wiped cache and dalvik, done a factory reset, and everything I can think of to get things right - but to no avail so far. When connected to my PC, the phone shows up fine and I can see and delete phone files. But, I cannot copy to the phone so I can't put the ROM zip there to start anew. And, since wifi is in a perpetual "turning on" (but never does) I cannot download directly to the phone.
My phone works fine for calls and texts and data, but I can't install apps or get wifi working.
So, gang, any ideas or suggestions?
Thanks much,
Ross
EDIT to add more detail: I just realized that I cannot even access storage through CM recovery. I may be totally hosed, right? I tried to use the install zip and restore functions in CM, but it reports no files found. And if I go to Gallery, for example, on the phone it says "install SD card". I clearly have some serious memory issue (on my phone too...). Help?
You try flashing back to the original ROM before the patch?
fr4nk1yn said:
You try flashing back to the original ROM before the patch?
Click to expand...
Click to collapse
No, I was already running Newt's NOS ROM and I just flashed the patch/update zip for GSM. I didn't do anything else.
rossvtaylor said:
Hi all,
I didn't find any relevant threads through searches, so I'm reduced to asking for help. Please!
My DNA's been running great on Newt's ROM. I'm S-OFF, rooted, using CM, and all's been great. I'm on T-Mo. I installed the most recent patch on the OP page and, now, my phone won't connect to wifi and in settings>storage it shows "unavailable" for storage.
I've wiped cache and dalvik, done a factory reset, and everything I can think of to get things right - but to no avail so far. When connected to my PC, the phone shows up fine and I can see and delete phone files. But, I cannot copy to the phone so I can't put the ROM zip there to start anew. And, since wifi is in a perpetual "turning on" (but never does) I cannot download directly to the phone.
My phone works fine for calls and texts and data, but I can't install apps or get wifi working.
So, gang, any ideas or suggestions?
Thanks much,
Ross
EDIT to add more detail: I just realized that I cannot even access storage through CM recovery. I may be totally hosed, right? I tried to use the install zip and restore functions in CM, but it reports no files found. And if I go to Gallery, for example, on the phone it says "install SD card". I clearly have some serious memory issue (on my phone too...). Help?
Click to expand...
Click to collapse
Ok, what you're probably going to want to try to do is get rid of CWM Recovery - it has proven short sighted in comparison to TWRP. Do the following;
1. Flash TWRP for the DNA (via GooManager or grab the flashable zip and flash via fastboot)
2. Wipe EVERYTHING - Davik, Cache, Data, System.
3. TWRP Main > Advanced > Sideload
4. Use the 'sideload' command via ADB to flash whichever ROM that you'd like to be running.
5. Reboot System (If it tells you no OS installed, click install from the main and install sideload.zip, normally sideloading the ROM will install aswell, but not always.)
With this method, you start with fresh radios, fresh kernels and a fresh storage.
Hopefully this helps get you back where you'd like to be. I had to do this when I switched from NEWT's NOS 4.3 GPE back to NEWT's NOS MY S5 ROM.
Mushroomhead, thanks. I'm up and alive again!
EDIT to add detail, in case someone else encounters this:
I've not ever used sideload before, but I now understand why it exists. I followed the guidance above, with the exception of changing from CWM to TWRP. I may, indeed, do that and give it a try. But I was unable to download any app - or, for that matter, take any photos or access the Play store or do anything which accessed memory. I couldn't even access my backup files. So, I forged ahead with ClockWorkMod Recovery, using sideload to install the original Newt NOS ROM I had. That worked great.
rossvtaylor said:
Mushroomhead, thanks. I'm up and alive again!
EDIT to add detail, in case someone else encounters this:
I've not ever used sideload before, but I now understand why it exists. I followed the guidance above, with the exception of changing from CWM to TWRP. I may, indeed, do that and give it a try. But I was unable to download any app - or, for that matter, take any photos or access the Play store or do anything which accessed memory. I couldn't even access my backup files. So, I forged ahead with ClockWorkMod Recovery, using sideload to install the original Newt NOS ROM I had. That worked great.
Click to expand...
Click to collapse
Glad to hear it! I've been in the modding game since the G1 was released. I know a bit or two about tons of phones. HTC & RUU. Samsung and ODIN. LG and BLEH (don't ever by an LG device). Glad that it worked out for you man, keep on keeping on.
Flashed My wife and I's OG's with CM 10.2. She was coming from stock 4.0.1 I was coming from 4.1.2
My has no problems. Hers wouldnt connect to wifi even though it could pick up the signals.
Last night her Kernel crashed. I figured maybe I didnt fully wipe her files clean so I rebooted her into recovery and did a factory wipe,
cleaning Dalvik, etc. and reinstalled.
Still no wifi connectivity.
Is this a driver, antennae, modem issue? Please help, I've run out of ideas.
Did you flash the correct radio?
Sent from my Optimus G using Tapatalk 4
Hmmmmm
Dr0!dFreek said:
Did you flash the correct radio?
Sent from my Optimus G using Tapatalk 4
Click to expand...
Click to collapse
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.1.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
brionbey said:
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
Click to expand...
Click to collapse
Roms for the OG don't contain modems, your wife's phone would still have ICS modem. If you had the ota to 4.1 on your phone it will have jb modem.
brionbey said:
I just used the one that came with CM.
Do you think since she was coming from 4.01 and I from 4.2 that I had the correct radio already that's why I have no issues?
And she still is running the 4.01 radio which is incompatible with android 4.3 which is what CM is running?
Click to expand...
Click to collapse
Yes, given that you avoided bricking your phone not having the rpm/tz partitions from the ota update, she would also have the ics modem, which hopefully is the only thing wrong, and is an easy fix.
matter of fact I'm not aware of anyone trying the ics modem on 4.3, or using 4.3 without the updated partitions
Still, (as a purely personal preference) I would restore the backup from before you flashed her to CM 10.2, then call up AT&T and make them push the OTA update, then backup again and reflash CWM.
-edit- this is of course, if you are on AT&T
also, you can probably make a nandroid of CM 10.2, restore to stock, get the OTA, and restore CM 10.2 and you wouldn't lose anything, since it only restores kernel,system,data,cache, etc it would be unaffected by the OTA.
technically this remains true for the LGNPST/teenybin route, but i haven't used lgnpst, i prefer forcing at&t to provide the OTA update since if it bricks then, they owe you a phone
[r.]GimP said:
Yes, given that you avoided bricking your phone not having the rpm/tz partitions from the ota update, she would also have the ics modem, which hopefully is the only thing wrong, and is an easy fix.
matter of fact I'm not aware of anyone trying the ics modem on 4.3, or using 4.3 without the updated partitions
Still, (as a purely personal preference) I would restore the backup from before you flashed her to CM 10.2, then call up AT&T and make them push the OTA update, then backup again and reflash CWM.
-edit- this is of course, if you are on AT&T
also, you can probably make a nandroid of CM 10.2, restore to stock, get the OTA, and restore CM 10.2 and you wouldn't lose anything, since it only restores kernel,system,data,cache, etc it would be unaffected by the OTA.
technically this remains true for the LGNPST/teenybin route, but i haven't used lgnpst, i prefer forcing at&t to provide the OTA update since if it bricks then, they owe you a phone
Click to expand...
Click to collapse
Just like to pass on a little info I learned recently, both Shellnutt2's cm10.2 and dvhexer's "alternate" cm10.2 use an e975 kernel.and can be flashed to phones without updating partitions.
adfurgerson said:
Just like to pass on a little info I learned recently, both Shellnutt2's cm10.2 and dvhexer's "alternate" cm10.2 use an e975 kernel.and can be flashed to phones without updating partitions.
Click to expand...
Click to collapse
Yeah I considered that, still terrifying to me though, but it would explain still having the ics modem.
How does this sound?
[r.]GimP said:
Yeah I considered that, still terrifying to me though, but it would explain still having the ics modem.
Click to expand...
Click to collapse
Ok, Just got back from work.
Today, Device crashed twice. Once a kernel error, once something about watchdog.
The kernel crash occurred when using the CM 10.4 camera. The same thing happened to my wifes device.
What I'd like to do it flash the Stock Rom Back with Stock modems to both phones.
Unfortunately, my backup didnt take because of lack of space or something, so I need to find the stock 4.1.2 rom.
I need action steps if possible.
I'm assuming I need:
4.1.2 Stock Rom for my device.w/ google apps
4.0.1 Stock for my wifes's./w google apps
I'm also assuming that I'd follow the same steps:
factory reset, flash the rom + apps reboot.
I'm using TWRP
If all that goes well I'd attempt to have at&t push the update to my wife's phone ( would I need to reset her bootloader?)
Then Reflash CM 10.2 with appropriate modems, and google apps.
Please catch any errors in this logic. Also Links to stock Rom's would be appreciated.
If anyone has any suggestions to a better custom rom then CM 10.2 I'm open to suggestions. I have not found it to be as stable as I would of liked...
FYI to make things worse, now my pc won't recognize that my device is attached.... trying not to panic.
brionbey said:
Ok, Just got back from work.
Today, Device crashed twice. Once a kernel error, once something about watchdog.
The kernel crash occurred when using the CM 10.4 camera. The same thing happened to my wifes device.
What I'd like to do it flash the Stock Rom Back with Stock modems to both phones.
Unfortunately, my backup didnt take because of lack of space or something, so I need to find the stock 4.1.2 rom.
I need action steps if possible.
I'm assuming I need:
4.1.2 Stock Rom for my device.w/ google apps
4.0.1 Stock for my wifes's./w google apps
I'm also assuming that I'd follow the same steps:
factory reset, flash the rom + apps reboot.
I'm using TWRP
If all that goes well I'd attempt to have at&t push the update to my wife's phone ( would I need to reset her bootloader?)
Then Reflash CM 10.2 with appropriate modems, and google apps.
Please catch any errors in this logic. Also Links to stock Rom's would be appreciated.
If anyone has any suggestions to a better custom rom then CM 10.2 I'm open to suggestions. I have not found it to be as stable as I would of liked...
FYI to make things worse, now my pc won't recognize that my device is attached.... trying not to panic.
Click to expand...
Click to collapse
Don't panic, you can always load onto the SD card externally, with a microsd to SD adapter or through TWRP/CWM with "mount usb storage" mode. Failing both of those things I'm fairly certain one of your two phones will be enough to load the SD card for the other phone if needed.
I'm thinking everything you need is going to be the LGNPST route now anyway, and that being said you may as well just flash them both to stock 4.1.2 in that case. First things first, you definitely want to backup before anything gets out of hand, if twrp isn't getting it then pull with adb. Quick breakdown of that below.
The universal drivers straight off the LG site work just fine, but in my experience to get the adb part happy you need to click on your devices, and find your phone, whether it says LG/Nexus4/MTP, doesn't matter. Open it and click on the hardware tab, it should list 3 devices.
unknown (or adb if you're lucky)
Your phone
USB Composite Device
If the top isnt some variation with ADB in the name, double click it, then change settings, it may say drivers not loaded, so on the driver tab we're going to give it one.
Update driver, and it will ask how, the option on the bottom is "browse my comp for driver software" and after that the bottom option again is "let me pick from a list..." I think then it shows a split list, the device type should be ADB something, and if you installed the LG universal drivers then near the bottom you will have "LGE Mobile Sooner Single ADB Interface" windows will complain because it couldn't figure out that its the right driver, confirm you want to use it and it will then show "this device is working properly" go ahead and close all those windows and it will update on the first one with the three devices listed the next time you open it.
At this point you need the adb application itself, I usually just download the whole android SDK personally, but where you get it from doesn't matter. If you're booted in android, make sure adb has root access in developer settings, and debugging is enabled.
open a command promt, for the sake of easy navigate to the folder where you put adb, in windows, or in the SDK example, /android/sdk/platform-tools/ hold shift and right-click on an empty space and select "open command window here"
If android is running, type "adb root" without quotes
and adb will inform you its restarting, if in twrp you will already be root.
Type "adb devices" and as long as its not blank you should be good
again, for the sake of easy "adb backup -shared -all"
and let it do its thing, it should start creating a default file named "backup.ab" it's bound to take awhile as -shared should grab all the sd card contents just to be safe.
Disaster recovery aside, I would use a combination of Titanium backup root, and "backup your mobile" - especially add the second option in addition to titanium, thats one of the only free backup apps that can get MMS as well as SMS, and restore them.
Again, if you're having issue with the computer normally seeing the device, these are still good tools, save to external sd card, remove card and transfer manually to your computer.
ok.. now that all your stuff is *hopefully* now redundantly backed up, depending on the stock image you find, you can either push it via fastboot commands or flash with lgnpst. I know the images are in our forum, most likely in the lgnpst thread. just follow through that and read well ahead before performing each step, you'll be ok.
I believe fastboot can relock your bootloader in all off one command, i don't have the answer if its necessary or not to receive the OTA, but having skimmed the lgnpst thread in the past, I'm positive people have done the flash and then had the OTA pushed from AT&T so they could get up to 4.1.2 for the official JB and partitions. Like I said in the beginning, your call if you want to skip that and just lgnpst to 4.1.2 since you're there anyway. Also, keep an eye out for one of the recent restore to stock / RPM/TZ partition threads, I think shellnutt making a cwm/twrp flashable zip to do the same thing lgnpst teeny bin would without even needing lgnpst.
So, barring a complete hardware failure, dont be scared. Get your data for now, then on to the next step.
Best xda technical support post I have seen in a long time. Thanks, gimp.
Sent from my Optimus G using XDA Premium 4 mobile app
DeathmonkeyGTX said:
Best xda technical support post I have seen in a long time. Thanks, gimp.
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Agreed.
Sent from my Optimus G using Tapatalk 4
I agree also! feels great to have some help with this. attempting fixes I'll report back.
Sent from my LG-E970 using XDA Premium 4 mobile app
I got stuck on the adb driver part. Through searching I found the backup I made for her. Can I restore her backup. Flash the jellybean rom to it, creating the neccessary. Partitions in the process, along with the correct radio, and then reflash Cm? My main concern is getting her wifi up. She's racked up 6gigs in 2 days herself! Were on the 4.gig shared plan. Or possibly just flash the radio...
Sent from my LG-E970 using XDA Premium 4 mobile app
brionbey said:
I got stuck on the adb driver part. Through searching I found the backup I made for her. Can I restore her backup. Flash the jellybean rom to it, creating the neccessary. Partitions in the process, along with the correct radio, and then reflash Cm? My main concern is getting her wifi up. She's racked up 6gigs in 2 days herself! Were on the 4.gig shared plan. Or possibly just flash the radio...
Sent from my LG-E970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes that sounds fine, in that case I would just make the apps and messages backups with titanium/backup your mobile
I'm not 100% if the lgnpst flash to JB wipes user data or not, but after that you can flash pretty much ANY rom for our device, then just download titanium/backup your mobile from the app store and point it to the directories on the sd card, and restore selectively.
For the most part you can move everything from /sdcard to /external_sd and move it back over when you're done, I think the JB radio (or modem, both terms apply) works very well for everything I've used (and yes they play a significant part in wifi and gps also), and I was a pretty hardcore flash-a-holic for a really good while, still haven't tried the hybrid modems and people rave about how well they work. Sounds like a good plan you got going, once you're up with the partitions and the JB modem from 4.1.2 you really should have no issues, and once you have that freedom, and she will as well to try out all manner of ROM's, you'll find you get really good at backup/restore out of necessity. Happy flashing.
If you need any specifics, aside from the step by steps of the other threads I'm glad to lend advice, just let me know
-edit- you can make multiple backups with each program by the way, titanium and backup your mobile.
Titanium free says only one backup per app, but in reality just hit the batch button on the top right, looks like a check mark, have it get all apps and system settings, then just move the whole folder you set for titanium off of the device for safe keeping. This way you can backup everything running right now, then if you want to restore the other one, you could even do it again, if you just wanted to cherry pick some stuff, then flash, etc. Titanium free wont let you make multiple copies of the same app, but it also WONT delete extras if you already have them, so if you dump a few titanium folders into eachother and merge them, you can then choose any of the backup files or data or both from each date.
The reason I use both programs is as I said earlier, backup your mobile handles SMS/MMS very efficiently, and occasionally I'll let it grab a few user apps, and system apps, because when it restores them, it restores for example, flash player from LG stock rom, as a user app, and it continues to work flawlessly. Titanium can't get over it being a system app, and sucks at restoring flash.
However, titanium is GREAT for also saving user data, not just the program itself. ie.. savegame states for any app you have that doesnt explicitly sync online, or the login data for facebook, or adfree with the most current hosts so you dont have to redownload or even type your logins, very convenient.
My personal order of operations before I flash a new rom, or even upgrade to a new version with a clean flash instead of a "dirty" is to fully backup all apps/system data with titanium, then hit ByM for contacts/sms/mms/bookmarks/user dictionary/apps
then a nandroid backup, since it is basically a perfect snapshot itself, just like turning the phone off, and back on.
after rom flash / gapps, I boot, setup google real quick, goto app store and cancel the 5 million downloads, except for titanium/ByM
after those download I roll my messages/user dictionary/contacts/ selective apps I know i'll use, and the same with a few from titanium.
This way I'm less bloated with crap I probably don't use everyday, and if i need it, its a few taps away. It's a very painless process and a lot of peace of mind having everything safe, and allows you to try alot of unstable crap knowing how easy you can always roll your CWM/TWRP backup over to the device like you never left.
Sorry, I'm a fan of ranting. Pics for adb driver steps explained in previous post, and the backup part, for reference if you ever need them.
View attachment 2263477
View attachment 2263478
Ok, I'm keepin cool but it seems to be one thing after another
I made the backup before the original flash.
I see it in the folder. When I restored it, it is the same rom that I'm on CM 10.2
I'm not sure how that happened.
Thanks for the images, that really helped unstuck me.
Question: I've checked the threads looking for the stock [ROM] 4.1.2 and Gapps for E970 and can't find them anywhere.
At this point I just need a doOver. I have to get my wife her phone back, ASAP and if I brick by some chance, I'll never hear the end of it.
EVER.
Or how about just flashing the radio? Can I do that to at least get her Wifi?
Here is the flashable jellybean radio by g33k3r.
http://forum.xda-developers.com/showthread.php?t=2220048
I recommend still updating her to the jellybean partition layout when you get a chance, but this should get you working WiFi at the very least.
Sent from my LG-E970 using xda app-developers app
Flash the Radio
Thanks SnowLeopard.
So all I need to do is just boot into recovery using TWRP and Install the radio, or should I factor reset and install the radio at the same time as the rom?
Thanks Again Guys. (or gals)
Lgnpst doesn't touch the /data partition.
Sent from my Optimus G using XDA Premium 4 mobile app
the modem work great.
Sent from my LG-E970 using XDA Premium 4 mobile app
At gimp, followed instructions exactly, computer recognize device, only thing left to do is run teeny bit, but getting error path not found
Sent from my LG-E970 using XDA Premium 4 mobile app
Hello my fella Developers.
lets do this again. i have the threat all typed up with details and closed it by an accident.
anyways
I have htc one max 8060-t6dug Chinese variant without OS. HTC-1
I had issues with this one, it came with bloatware and lots of it. some of it is pornographic. (got kids who play with my phone)
i decided to root, got the TWRP Recovery. flashed with latest SuperSU. got titanium pro (paid) to get rid of unwanted bloatware. i guess i missed out on something. as soon as i connect with wifi. it starts to download apps. and formatting doesnt help. so i thought maybe repeat the process. BUT in recovery i accidentally wiped system.
i have been through xda developers forums completely found some roms but dead links.
went though several other sites without any luck.
went though Chinese forums (Baidu i think) found some firmwares but TWRP gives me error trying to flash it.
i have tried to flash these with adb command, but mostly get remote not allowed error or space not allocated error.
came back to xda forums and found this
http://forum.xda-developers.com/htc...m-ruu-htc-one-max-809d-t6dwg-sense-5-t3006498
i know this is for t6dwg variant.
t6dwg and t6dug are both Chinese variants and dual sim. i have tried all roms listed on this thread. TWRP Flashed it fine but now when it boots up and gets to lock screen, when i unlock it it show HTC white screen and restarts after a min or so.
I went to the store and purchased another htc one max, same variant. HTC-2
i thought maybe make a nandroid back up and flash it to HTC-1
i repeated the steps and got HTC-2 rooted, latest TWRP, and made the back up. but i am unable to flash it into HTC-1
HTC-1 rooted with latest SuperSu, latest TWRP recovery, unlocked boothloader, s-off, cid-11111111
issues, NO OS!
http://picpaste.com/pics/htc1-l8ImCwQL.1462326306.jpg
HTC-2 rooted with latest SuperSu, latest TWRP recovery, unlocked boothloader, s-off, cid-11111111, boots perfect,
issues, bloatware
http://picpaste.com/pics/htc2-BrCDb5Tw.1462326402.jpg
lets not forget its been about a month since i am trying to figure this out without disturbing developers and wasting their time. this is my last resort
any help would be greatly appreciated.
Thanks in Advance
Anyone out there to my rescue?
@waqas9240 So you made the backup with TWRP? Why not backup to an sdcard one the working one. Place the sdcard in the non-working one and do a restore.
waqas9240 said:
Anyone out there to my rescue?
Click to expand...
Click to collapse
@Flyhalf205! I know i can always count on you for this. yes i used TWRP to make the backup from the working htc and stored it on SD card. and pushed SD card on the non-working Htc but it doesnt recognize it in restore mood in TWRP. i can see the file in Install method that if it has been compressed, but it doesnt let me flash it.
waqas9240 said:
@Flyhalf205! I know i can always count on you for this. yes i used TWRP to make the backup from the working htc and stored it on SD card. and pushed SD card on the non-working Htc but it doesnt recognize it in restore mood in TWRP. i can see the file in Install method that if it has been compressed, but it doesnt let me flash it.
Click to expand...
Click to collapse
Now if I remember correctly inside the TWRP folder will be another folder. The folder name could be the the serial. You'll have to get onto a computer and verify that the backup is in the correct folder inside the TWRP folder.
A good way to verify. On the non-working device, do a backup on just the boot to the sdcard. Then see if you can plug both devices into the computer at the same time to see the directory layout. Then you can copy the backup into the right folders.
Once you bring up TWRP on the non-working device. You should be able to select and swipe to restore perfectly.
Flyhalf205 said:
Now if I remember correctly inside the TWRP folder will be another folder. The folder name could be the the serial. You'll have to get onto a computer and verify that the backup is in the correct folder inside the TWRP folder.
A good way to verify. On the non-working device, do a backup on just the boot to the sdcard. Then see if you can plug both devices into the computer at the same time to see the directory layout. Then you can copy the backup into the right folders.
Once you bring up TWRP on the non-working device. You should be able to select and swipe to restore perfectly.
Click to expand...
Click to collapse
thats what i thought at first. i confirmed the path on both phones. i even got to push the back up in the non working htc to restore from the root as it was located in the working htc max. still does the samething. the second folder after TWRP is serial number folder. i even renamed the serial number to the non working htc ( i dont know if that would have made a difference or not) but still running the same issue. i dont have both phones on me right now. they are at home. let me finish work and will try it again as you explained.
meanwhile if you can figure out something else that would be great bro!
Thanks