Since there still seems to be a lot of interest in manual updates of PRL's, I'm introducing the Quick and Dirty PRL Update Kit (QADPUK) for people that can't or don't want to use the diagnostic mode and QPST/CDMA Workshop on a Windows PC.
Note: If you prefer to use an ICS Sense ROM to change you PRL see the discussion beginning with this post. You can still use the downloads for the utilities linked below. (Thanks to gunfromsako and rulingczar on the Evo 4G LTE forums for that option)
The basic tool is an old version of the Senseless GB ROM with some utilities pre-installed to facilitate changing and testing the PRL's.
The utilities included in the kit are:
1. MSL Reader
2. Speedtest.net
3. Network Signal Info
4. An EPST.apk capable of updating the PRL
5. Assortment of current PRL's
6. ShootMe so I could take the screenshots on an old GB ROM
The ROM is fully functional and all radios are available for testing, but it will be in airplane mode initially after it is restored and booted. The PRL will not update while in airplane mode.
Instructions for installation:
Important Note: Flashing and booting GB ROM's requires an hboot version lower than 1.57. If you are S-OFF you can use this procedure to downgrade your bootloader but S-ON users won't be able to use this guide unless you are already using a supported hboot.
1. Download the kit from here
2. Copy it to the /sdcard/clockworkmod/backup directory
3. Unzip the QADPUK-1.0 directory to that location
4. Restore the backup with 4EXT or CWM recovery
5. Boot the ROM (pic #1)
Instructions for use:
1. Verify that airplane mode is off.
2. Use MSL Reader to get the code for your device
3. Open the dialer and key in ##775#
4. Enter the code from MSL Reader when prompted
5. Select the PRL you want to use (pic #2)
6. Press OK to confirm the selection
7. Use the menu button to get the commit option and press that (pic #3)
8. Reboot the phone as it probably won't boot on its own
9. Go to About phone/Software information/More is system settings and confirm that the PRL was installed (pic #4)
10. Run whatever tests you want to evaluate the performance of the selected PRL
Notes:
1. Here's a tutorial that matches this process but you can start with step 9 since since 1-8 have already been done in this ROM
2. The /sdcard/PRL directory is recreated with the default PRL's during each boot so additional PRL's should be placed in another directory on the SD card
3. A general description of the PRL's can be found in this post but I've tried to find newer versions where possible
4. This SGS3 thread on Sprint PRL's that might have something useful, but be aware that PRL's for LTE devices are different than those for WiMax devices
5. PRL 61009 is for Boost/Virgin Mobile
6. The "Verizon" 00002 PRL has been included but use it with extreme caution since roaming abuse can cause your account to be cancelled
7. It's been verified by liquidplmr and myself that this ROM works fine with Boot Manager.
ramjet73
what were your results like after you used this?
did you have improved speeds or were they all myths
johnnyboi1994 said:
what were your results like after you used this?
did you have improved speeds or were they all myths
Click to expand...
Click to collapse
To be honest, I haven't done much testing yet but I plan to use this kit myself to answer that question.
Some people seem to be religious about PRL's, and others don't think they make much difference, but the corporate versions at least allow for data roaming which is why I used one of those for my example.
ramjet73
If I'm reading this correctly this is a nandroid from your evo3d and this method requires the user to restore the nandroid made from your evo3d to there's, is this correct ???
#Root-Hack_Mod*Always=LTE
laie1472 said:
If I'm reading this correctly this is a nandroid from your evo3d and this method requires the user to restore the nandroid made from your evo3d to there's, is this correct ???
Click to expand...
Click to collapse
Yes, it's a modified nandroid that restores only the the boot, system, data and cache partitions. The only setup that was done for the ROM was to sideload the utilities and apps required and test. There was no customization beyond that so market updates and other functions that require it will need to be performed by the user.
ramjet73
ramjet73 said:
Yes, it's a modified nandroid that restores only the the boot, system, data and cache partitions. The only setup that was done for the ROM was to sideload the utilities and apps required and test. There was no customization beyond that so market updates and other functions that require it will need to be performed by the user.
ramjet73
Click to expand...
Click to collapse
Thanks for the quick response.
I'm a little puzzled as to why you chose to provide a nandroid for users instead of a stock rom with the modifications made given the potential issues that could occur with restoring a nand made from one device to another.
#Root-Hack_Mod*Always=LTE
laie1472 said:
Thanks for the quick response.
I'm a little puzzled as to why you chose to provide a nandroid for users instead of a stock rom with the modifications made given the potential issues that could occur with restoring a nand made from one device to another.
#Root-Hack_Mod*Always=LTE
Click to expand...
Click to collapse
I PM'd you. There's no personal customization or passwords in the ROM that was backed up to the nandroid and I've removed the WiMax portion or the backup. I've tested it on two different Evo 3D's, and used nandroid backups in the past to restore ROM's I've setup on my backup Evo 3D to my primary phone without any issues.
ramjet73
I replied to your pm as well.
Also no "real" concern at all man that's not what I meant. Let me clarify. I've never seen a method posted using a nand before. Not saying that they don't exist. Besides the worst thing the users would have to do in a worse case scenario is wipe all partitions and restore original or flash new. It just seemed puzzling to me because from a fresh install your pretty much good. Restoring nand's can be troublesome at times.
#Root-Hack_Mod*Always=LTE
laie1472 said:
I replied to your pm as well.
Also no "real" concern at all man that's not what I meant. Let me clarify. I've never seen a method posted using a nand before. Not saying that they don't exist. Besides the worst thing the users would have to do in a worse case scenario is wipe all partitions and restore original or flash new. It just seemed puzzling to me because from a fresh install your pretty much good. Restoring nand's can be troublesome at times.
#Root-Hack_Mod*Always=LTE
Click to expand...
Click to collapse
No problem. Thanks for the feedback.
There was some setup of the scripting app (Script Manager) to copy the default PRL's to the SD card that I had to do since the SD card isn't mounted at the time the init.d scripts are run. I also started all the apps requing root privileges and pre-authorized them in superuser. The superuser pre-authorization isn't a big deal, but I couldn't figure out how to do the scripting setup as part of a flashable zip, and the PRL's have to be on the SD card to be picked up by EPST.apk.
If users that want to use the kit have problems or concerns with the nandroid approach, I can try to figure out another method, or they can just flash a GB ROM and add the required components themselves. I'm just trying to make it easier for those that want a "quick and dirty" solution to flashing and testing PRL's.
ramjet73
You can DL a custom stock rooted rom and use 7zip to add the apk"s. Also another option is to have the prl's as a separate DL. If users are downloading then from here "the app" or the web as long as they are on mobile the prl's will download to the sd. This method is a keeper for sure don't get me wrong. However as I posted before issues can occur with restoring a nand. And having a good method based off something that's known to give users a headache from time to time "IMO" hinders the overall intention of the method. Also I'd be more than willing to lend a hand in the process of getting the prl's to default to the sd when the user flashes the rooted rom. If that's something your looking at doing. Nevertheless excellent method.
#Root-Hack_Mod*Always=LTE
Since the kit has worked for me on two different Evo 3D's, I'm leaving it as a nandroid restore for now. If anyone has problems with the nandroid or would prefer to use another GB ROM the additional pieces required are linked in the list of utilities included.
ramjet73
ramjet73 said:
Since the kit has worked for me on two different Evo 3D's, I'm leaving it as a nandroid restore for now. If anyone has problems with the nandroid or would prefer to use another GB ROM the additional pieces required are linked in the list of utilities included.
ramjet73
Click to expand...
Click to collapse
Thanks for this quick method! I don't have time to flash and setup a full Rom just to change my prl. It's why I haven't changed mine in almost a year. This method changes that for me. Quick and efficient! Thanks ramjet
Sent from my shooter using xda app-developers app
ramjet73 said:
Since there still seems to be a lot of interest in manual updates of PRL's, I'm introducing the Quick and Dirty PRL Update Kit (QADPUK) for people that can't or don't want to use the diagnostic mode and QPST/CDMA Workshop on a Windows PC.
The basic tool is an old version of the Senseless GB ROM with some utilities pre-installed to facilitate changing and testing the PRL's.
The utilities included in the kit are:
1. MSL Reader
2. Speedtest.net
3. Network Signal Info
4. An EPST.apk capable of updating the PRL
5. Assortment of current PRL's
6. ShootMe so I could take the screenshots on an old GB ROM
The ROM is fully functional and all radios are available for testing, but it will be in airplane mode initially after it is restored and booted. The PRL will not update while in airplane mode.
Instructions for installation:
1. Download the kit from here
2. Copy it to the /sdcard/clockworkmod/backup directory
3. Unzip the QADPUK-1.0 directory to that location
4. Restore the backup with 4EXT or CWM recovery
5. Boot the ROM (pic #1)
Instructions for use:
1. Use MSL Reader to get the code for your device
2. Open the dialer and key in ##775#
3. Enter the code from MSL Reader when prompted
4. Select the PRL you want to use (pic #2)
5. Press OK to confirm the selection
6. Use the menu button to get the commit option and press that (pic #3)
7. Reboot the phone as it probably won't boot on its own
8. Go to About phone/Software information/More is system settings and confirm that the PRL was installed (pic #4)
9. Run whatever tests you want to evaluate the performance of the selected PRL
Notes:
1. Here's a tutorial that matches this process but you can start with step 9 since since 1-8 have already been done in this ROM
2. The /sdcard/PRL directory is recreated with the default PRL's during each boot so additional PRL's should be placed in another directory on the SD card
3. A general description of the PRL's can be found in this post but I've tried to find newer versions where possible
4. The 61009 is a Boost/Virgin Mobile PRL
5. The "Verizon" 00002 PRL is been included but use it with extreme caution since roaming abuse can cause your account to be cancelled
ramjet73
Click to expand...
Click to collapse
Now to find out if this will load into boot manager. If it does ramjet will you have my bearded babies?
Sent from my GT-P7510 using Tapatalk HD
liquidplmr said:
Now to find out if this will load into boot manager. If it does ramjet will you have my bearded babies?
Click to expand...
Click to collapse
LOL!
I don't want any of your bearded babies, but have you tried restoring it as a native (phone) ROM? If you can do that and it works you should be able to install Boot Manager and do your own nandroid. I have Boot Manager Pro installed on one of my Sense ROM's so if you can't get it to work I'll give it a try.
ramjet73
No dice. But boot manager hasn't been working properly for me lately might be 4.21 or may just be user error. Had it working fine on aokp, a lot toy with.
Sent from my Evo 3D CDMA using Tapatalk 2
liquidplmr said:
No dice. But boot manager hasn't been working properly for me lately might be 4.21 or may just be user error. Had it working fine on aokp, a lot toy with.
Click to expand...
Click to collapse
I just installed it successfully using the nandroid with Boot Manager Pro 3.2.6 and am booted into it right now and it seems to be working fine. My phone ROM is MeanROM ICS 2.6 so that might be the difference.
Edit1: I attached a screenshot of the Boot Manager slot and the PRL update seems to work fine.
Edit2: Just changed my phone ROM to mazda's AOKP 3.5.2 with Boot Manager installed and this ROM works fine in that configuration too.
Thanks for the idea.
ramjet73
Something is wrong with my boot manager install then I'll give it another try when I get home later. Are you forcing large boot images or anything?
Sent from my Evo 3D CDMA using Tapatalk 2
liquidplmr said:
Something is wrong with my boot manager install then I'll give it another try when I get home later. Are you forcing large boot images or anything?
Click to expand...
Click to collapse
No, I've seen that mentioned a few times as being necessary, but I think mainly what it does is force busybox to be included and I've never needed it for the ROM's I've used with Boot Manager.
ramjet73
ramjet73 said:
No, I've seen that mentioned a few times as being necessary, but I think mainly what it does is force busybox to be included and I've never needed it for the ROM's I've used with Boot Manager.
ramjet73
Click to expand...
Click to collapse
Tried yet again wondering if its my phone ROM screwing it up at this point. I'll flash back to Mazda's 4.1.2 build and see if I can make it cooperate.
Sent from my GT-P7510 using Tapatalk HD
liquidplmr said:
Tried yet again wondering if its my phone ROM screwing it up at this point. I'll flash back to Mazda's 4.1.2 build and see if I can make it cooperate.
Click to expand...
Click to collapse
I just added Viper3D r330 to my Boot Manager Pro 3.2.6 configuration with the JBear 1.50.5050 hboot and that's running fine too. The Jelly Bean ROM's will boot fine as the phone ROM but they have a few glitches on Boot Manager as slot ROM's.
ramjet73
Related
My Thunderbolt received an OTA update last week and keeps rebooting. I have ClockworkMod Recovery so the Install fails. I cleared the Cache with CWM and restarted the phone like it suggests in other posts elsewhere. I get a failed update message, I cancel out of it and reboot the phone. I also used Titanium Backup to Freeze "Update" and "Updater", but the phone keeps self booting into the OTA update every day . I searched for an update.zip and cannot find one on the SD card.
Can anyone suggest how to stop the phone from updating/rebooting everyday? I cannot seems to find the answer anywhere.
Thanks and I wish everyone a safe holiday!
DD
Just to confirm, are you rooted but on the stock rom? If so, you should be able to find some threads to go on from searching, but here are a couple where people got the update install while rooted:
http://forum.xda-developers.com/showthread.php?t=1330325
http://forum.xda-developers.com/showthread.php?t=1324682
Sorry I forgot to mention it
Yes, I'm rooted, I'll check out the links.
more than likely you wont have an update.zip but rather an RUU. Remove the RUU from the SD card and see how that works. If I was having this problem I would do a full wipe on the phone backup my full SD card contents and format the SD card and flash a custom rom with CWM. I never understand what the point of rooting is if you are not going to flash a custom rom. Are you afraid? Worried about bricking? I just don't get it. Put the new MIUI on it. You will be pleased.
I installed Liquid ROM 3.1 and it's working like a charm. I was concerned about the 3G/4G compatability problems that most custom ROMS seem to have.
Using Titanium Backup Pro I backed up all my apps then restored them after installing Liquid ROM and re-setup the desktop and all is well.
bigd5783 said:
I never understand what the point of rooting is if you are not going to flash a custom rom.
Click to expand...
Click to collapse
Really? The ability to fix things like security holes, use ad filters, make complete, easily restorable backups, install a certificate for a private CA, or just have fairly complete control over hardware you've purchased isn't enough?
mike.s said:
Really? The ability to fix things like security holes, use ad filters, make complete, easily restorable backups, install a certificate for a private CA, or just have fairly complete control over hardware you've purchased isn't enough?
Click to expand...
Click to collapse
I was actually broken hearted that I was compelled in install a custom rom to avoid the problems the op has described. Everything "works" in standard rom. When you go custom you get lots of fun new features but you always lose something..... Could be vzw vvm or nfl live or fast gps lock or photo effects in gallery but it seems there is always someting you lose.
recDNA said:
I was actually broken hearted that I was compelled in install a custom rom to avoid the problems the op has described. Everything "works" in standard rom. When you go custom you get lots of fun new features but you always lose something..... Could be vzw vvm or nfl live or fast gps lock or photo effects in gallery but it seems there is always someting you lose.
Click to expand...
Click to collapse
really,cause everything you mentioned has work on soab from the get go.
Sent from my ADR6400L using xda premium
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...
Is there anyone out there who is willing to point me in the right direction for re purposing my retired Eris (RIP 02-12-13)? Hoping it can be a tool for learning (still in A- shape), instead of a paperweight! I have been doing some reading, but downloading is another story, mostly 404s out there now.
P.S. First post in any forum ever, just a humble android noob searching for knowledge and stable Roms from those who offer, sorry if I have posted this in the wrong place, obviously I have posted at the wrong time! A million thanks in advance to anyone with good news or advice!
DB73 said:
Is there anyone out there who is willing to point me in the right direction for re purposing my retired Eris (RIP 02-12-13)? Hoping it can be a tool for learning (still in A- shape), instead of a paperweight! I have been doing some reading, but downloading is another story, mostly 404s out there now.
Click to expand...
Click to collapse
What is it you are looking for? I have copies of a lot of ROMs.
doogald said:
What is it you are looking for? I have copies of a lot of ROMs.
Click to expand...
Click to collapse
Hello, and thank you, I am happy to here some good news. I am obviously new to this, but I love to try out different OSs and remaster them the way I see fit. I have just not taken the plunge with android. Since I have never installed any, it's hard to say witch ones I would like best. I would take any ROMs I could get. I figure I can experiment and learn with my Eris, then re purpose it for my son to play games, take pictures etc.
P.S. I downloaded the Jcase / Eclipse3 one click root. Is this the method you would recommend for getting su privileges? I would love to hear your preference on an easy and up to date rooting method. My Eris is currently bone stock with official 2.1, and up to date according to it.
DB73 said:
Hello, and thank you, I am happy to here some good news. I am obviously new to this, but I love to try out different OSs and remaster them the way I see fit. I have just not taken the plunge with android. Since I have never installed any, it's hard to say witch ones I would like best. I would take any ROMs I could get. I figure I can experiment and learn with my Eris, then re purpose it for my son to play games, take pictures etc.
P.S. I downloaded the Jcase / Eclipse3 one click root. Is this the method you would recommend for getting su privileges? I would love to hear your preference on an easy and up to date rooting method. My Eris is currently bone stock with official 2.1, and up to date according to it.
Click to expand...
Click to collapse
Yes, if you can find the JCase 1-click root, that will root the phone just fine.
There is another method very well documented here: http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html (which also walks you through installing for your first custom ROM.)
I have some ROMs in my Dropbox if you can't find links.
xtrSENSE (stock 2.1 Eris ROM, rooted): https://dl.dropbox.com/u/220420/Eris/xtrSENSE/xtrSENSE5.0.1.zip
Workshed's GSB: https://www.dropbox.com/s/dvpuv4sbwmun43f/GSB.v4.5-final_ODEXED_CM7.2-Eris.zip
CondemnedSoul's CM7.2: https://www.dropbox.com/s/g1irvshpg7u7trr/CCM7_Eris_V24_RIP.zip
The last two are CyanogenMod Gingerbread ROMs. I think that GSB requires that you also flash Google apps in order to get the market. If so, you can get it from CyanogenMod here: http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip
(So, if you need to flash gapps, you go into Recovery. Wipe data/factory reset. Flash the ROM. Flash google apps. THEN restart the phone.)
doogald said:
Yes, if you can find the JCase 1-click root, that will root the phone just fine.
Just realized why it wouldn't let me post, because of the links in my reply, :silly:
Thank You, I downloaded the ROMs. The link for gapps is dead though. Was that just needed for Workshed's GSB or also for CM7.2?
I have a few questions to throw out there:
1. I was thinking about doing another factory reset, my attempt to have a clean recovery. What will non-activation after boot with no service do?
2. Does vanilla = fast, lightweight, performance, more partition space for user? If so, do you have any recommendation / or a link?
3. Rumored Jellybean for the Eris, love to find the latest build, is it still available? Links point here (XDA) but no download.
4. Is there any way to get google play instead of market working on the Eris?
(((Thanks again for everything)))
XML Parsing Error: unexpected parser state
Location: jar:file:///C:/Program%20Files/Mozilla%20Firefox/omni.ja!/chrome/toolkit/content/global/netError.xhtml
Line Number 308, Column 50:
Click to expand...
Click to collapse
DB73 said:
Thank You, I downloaded the ROMs. The link for gapps is dead though. Was that just needed for Workshed's GSB or also for CM7.2?
Click to expand...
Click to collapse
Try this one: http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
CondemnedSoul's includes the Google apps already and does not require a separate flash of the gapps zip file.
Ok, I just checked: GSB does NOT require google apps, either; they are already included. You can ignore that step.
I have a few questions to throw out there:
1. I was thinking about doing another factory reset, my attempt to have a clean recovery. What will non-activation after boot with no service do?
Click to expand...
Click to collapse
Oh, good question. I would avoid it if you can. The Eris will insist that you activate. However, if you follow the prompt to activate and then press the disconnect button as soon as you hear it ring, it will try activation again two more times. If you disconnect after hearing the ring those two times as well, the phone will give up on activation and allow to continue with setup.
2. Does vanilla = fast, lightweight, performance, more partition space for user? If so, do you have any recommendation / or a link?
Click to expand...
Click to collapse
Not necessarily. In my experience, xtrSENSE is fastest, but the GB ROMs are just fine. You may not notice the difference. However, xtrSENSE has a method called cache2cache that frees up more storage space or user applications and data. If you install a lot of apps, xtrSENSE may give you more space.
That said, there are disadvantages, including missing out on apps that do not run on android 2.1.
There is something called xtrcache2cache that you can flash on the GB ROMs to give you the same sort of space. I'll try to find a link.w
3. Rumored Jellybean for the Eris, love to find the latest build, is it still available? Links point here (XDA) but no download.
Click to expand...
Click to collapse
I've never tried it, and I can't believe it runs with any sort of decent performance anyway.
4. Is there any way to get google play instead of market working on the Eris?
Click to expand...
Click to collapse
Not on android 2.1, but the two gingerbread ROMs will update the market to the play store.
xtrcache2cache is here: http://forum.xda-developers.com/showthread.php?t=924562
The download link there seems to work.
Copy that file (xtrCMCache2cache.zip) to your SD card. This is only for the Gingerbread ROMs - it's not necessary for xtrSENSE.
Restart the phone to recovery. If you have already flashed one of those ROMs, simply flash that xtrCMCache2cache.zip file - do not wipe data or Dalvik cache first. Restart the phone, and you'll have probably about 20-30 MB more free storage space for apps and data.
If you have not already flashed GSB or CondemnedSoul's, do this:
- restart in Recovery
- wipe menu
- wipe data/factory reset
- main menu
- flash a zip file, and choose GSB or Condemned
- flash a zip file, and choose xtrCMCache2cache.zip
- restart the phone
doogald said:
xtrcache2cache is here: http://forum.xda-developers.com/showthread.php?t=924562
OK, I will read what I have gathered one or two more times before taking the plunge. I am thinking of using the Jcase method, it seems pretty much idiot proof. I have the file and ROMs stored on my PC, and now on a CD as well, just so I don't loose them. If I have this right, I will:
Pre-Steps:
Copy the Jcase one click root file to an empty SD card, install a file explorer app capable of launching it, take a deep breath, here we go Or maybe I have to copy to android filesystem first?
1. Execute Jcase's one click, and after reboot, I should have the Amon Ra recovery. This is simple, but also the most dangerous part? If this were to fail, it would be similar to a bad BIOS flash. This would brick the phone, if I am understanding this correctly.
2. Then Use the recovery to flash rootme.zip now located on SDCard. Going to use a 2 Gb card from my old LG 8350 (phone before Eris).
3. Do Nand backup of semi clean stock OS. By doing so I will loose the stock recovery for good, meaning no more resets to OG clean?
3.5? On second thought, doing one last reset first would remove all user data with my name and credentials. It may be wise to do this, as it will eventually be in the hands of a 5 year old. This would prevent accidental purchases, I think! On the other hand, if I ever break or loose my new phone and need a temp phone, I could keep this image (as is) to use temporarily with Verison until I get a replacement! I can only choose one of these options. I guess the latter is best, and use only a custom ROM for my son to play with. Hopefully I can temporarily disable or somehow limit su before giving it too him.
4. Do Nand backup of original official image, and put somewhere safe, like 2 places + on CD then remove from SD for more available space.
5. Flash one of the 3 downloaded ROMs and also xtrCMCache2cache if desired to desire-c
6. I assume that appstoSD is something I would need to download now, then add after previous steps, if I feel the need!
7. Then its off to test land! I hope I understand this correctly. The one step I have missed is definitely very important. I did not verify the MD5 on Jcase's one click. In fact I don't even remember where I downloaded it from. Truth being told, I have never manually done a MD5 verification! I guess I have one more step that I absolutely need to learn as it is much more important in Android, especially for recovery!
Edit: I have re downloaded the file from here (XDA), did not see a sum to compare it to? I hope the file still is OK!
Edit # 2 I downloaded a MD5 calculator and this is the output (F34FECFFB985553B68D66F6AC1EF27D3) for the erisone010.apk file
Another big thank you Doogald, If I have something wrong here, please, feel free to beat it into me now, before I do something stupid!
Click to expand...
Click to collapse
DB73 said:
Pre-Steps:
Copy the Jcase one click root file to an empty SD card, install a file explorer app capable of launching it, take a deep breath, here we go Or maybe I have to copy to android filesystem first?
Click to expand...
Click to collapse
No, Your regular SD card is fine. You do need to enable third-party app installs; you'll find that setting in settings->applications.
1. Execute Jcase's one click, and after reboot, I should have the Amon Ra recovery. This is simple, but also the most dangerous part? If this were to fail, it would be similar to a bad BIOS flash. This would brick the phone, if I am understanding this correctly.
Click to expand...
Click to collapse
Yes. You must restart the phone as if you wanted to make a phone call. Many people get too eager and try to get into Recovery before full restarting.
I can't believe that flashing Amon_RA is all terribly dangerous. There are ways to recover. In fact, I have not seen anybody report a brick after running the JCase 1-click. I'm sure that it will be fine.
2. Then Use the recovery to flash rootme.zip now located on SDCard. Going to use a 2 Gb card from my old LG 8350 (phone before Eris).
3. Do Nand backup of semi clean stock OS. By doing so I will loose the stock recovery for good, meaning no more resets to OG clean?
Click to expand...
Click to collapse
You *could* do the Nand Backup before running rootme.zip. Actually, you only really need to run rootme.zip if you want to do something with root with the stock Android you have now. Some people may, for example, install the application Titanium Backup Pro (which requires root) and batch backup all user apps (menu->batch and choose to run that option from the list) and then, after installing a new custom ROM, reinstall Titanium from the market/play store and then batch restore all missing apps and data. It's a very powerful way to get the phone running all of your apps and data without reinstalling from scratch.
That brings up one more thing: if you decide to install xtrSENSE, you do not need to do a factory reset if you want to keep all of your apps and data. Of course, if you want a fresh start you may, but xtrSENSE will keep all of your apps and data and give you a faster Eris with more room for apps and data.
Also, it *is* possible to get stock recovery back, though not without losing all of you data. There is a ROM called Flashback_21v2 that will bring back stock recovery and an unrooted Eris if you wish. The phone will act as if it was never rooted. You can find it here: http://forum.xda-developers.com/showthread.php?t=792026
That would be a good thing to keep on your phone, just in case. (Though I have to say that I am hosting the location of those files on my website and I have no plans to stop doing so, so they should be around for a while...) You'll probably be fine with the "no radio" version, but if you can spare the space on your computer, (that's a bit of a joke; the files are small), I'd download both.
3.5? On second thought, doing one last reset first would remove all user data with my name and credentials. It may be wise to do this, as it will eventually be in the hands of a 5 year old. This would prevent accidental purchases, I think!
Click to expand...
Click to collapse
In that case, you DEFINITELY want to wipe data, even with xtrSENSE!
On the other hand, if I ever break or loose my new phone and need a temp phone, I could keep this image (as is) to use temporarily with Verison until I get a replacement! I can only choose one of these options.
Click to expand...
Click to collapse
No, you can do both. Do a Nand Backup of the phone after you root it, which will be stored on the SD card. Wipe data/factory reset and you can installa ROM and then always go back into recover and Nand restore what you backed up originally to get your phone back as it was when you ran the backup. Familiar with Norton Ghost for Windows PCs? That's what Nand backup and restore does - it takes a full snapshot of your phone as it is, and when you restore, it's as if you had just turned off your phone for a long time - it's back to the way it was at the time you made the backup. You can have multiple backups stored - as many as will fit on the SD card.
6. I assume that appstoSD is something I would need to download now, then add after previous steps, if I feel the need!
Click to expand...
Click to collapse
Well... xtrSENSE support apps2sd as it is, and there are scripts to turn that functionality on. The GB ROMs support using the Android-native moving of apps to sd, so I would avoid apps2sd for them.
7. Then its off to test land! I hope I understand this correctly. The one step I have missed is definitely very important. I did not verify the MD5 on Jcase's one click. In fact I don't even remember where I downloaded it from. Truth being told, I have never manually done a MD5 verification! I guess I have one more step that I absolutely need to learn as it is much more important in Android, especially for recovery!
Edit: I have re downloaded the file from here (XDA), did not see a sum to compare it to? I hope the file still is OK!
Click to expand...
Click to collapse
The MD5 I have for 1click is f34fecffb985553b68d66f6ac1ef27d3
HOWEVER, can I suggest instead that you use the 1-click root here, prepared by Scary Alien: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
If you look at the bottom of the first post, "Scenario 5", there is another version of 1click with a better version of Amon_RA (that allows you to use the hardware keys to navigate recovery, rather than just the trackball; sometimes the trackball doesn't work in the original Amon_RA). That version I guarantee is safe, and Scary Alien has the MD5 right there.
I am guessing multi-quote is what I should have tried on this instead of deleting?
OK, running 1 click directly from from SD card. Third-party apps ticked on before hand, check.
After running 1 click, do normal restart, then shutdown, then go into recovery via vol / end start up.
No bricks reported, that is very good news. Also good to hear that there may be a procedure for un-bricking in the unlikely event!
My Eris already has already has all apps removed, I tried to make it as clean and small as possible. Just looked at the xtrSENSE page and copied some tips, sounds nice and fast, liking that!
Awesome, I downloaded all 3 including Cupcake, in case I want to remember what that was like.
I did exactly that, downloaded both.
I will give this some extra thought before giving it to my son.
I have never used Norton Ghost, but I have used Macrium Reflect, Seagate Disk Wizard, Acronis etc. I get the image/snapshot thing. I plan to store backups in other locations, then copy back to SD if and when needed.
Just did some reading on the xtrSENSE page about aps2sd, guess I will do some more reading about native moving of apps to sd soon.
The MD5 I have matches yours. I downloaded MD5 Calculator and I guess it works.
After reading the page including "Scenario 5" I absolutely agree. I downloaded it, and will use the "scary alien" modded version with the added functionality. Thank you very much for pointing this out. Looks like no change in the simple execution besides the app/file to run, very nice!
Doogald, I can clearly see that you go out of your way to help others to say the least, I am sure its appreciated by more than just me, Thanks!
DB73 said:
I will give this some extra thought before giving it to my son.
Click to expand...
Click to collapse
Hey, one other thing: CondemnedSoul posted a script that you can run that disables the mobile radio, so you can make the device WiFi only. It's here: http://forum.xda-developers.com/showthread.php?t=1216571
I have to say that I have never tried it, but it seems from the replies in that thread that many have, successfully.
Jelly Bean build anyone?
This may be redundant, but does anyone have a copy of the eris jelly bean rom laying around? Just found my old rooted eris with cyanogenmod and I would like to try jelly bean or ICS.
foodude1 said:
This may be redundant, but does anyone have a copy of the eris jelly bean rom laying around? Just found my old rooted eris with cyanogenmod and I would like to try jelly bean or ICS.
Click to expand...
Click to collapse
Of course it isn't redundant, in fact this maintains the forum active, well a bit.
Here is the Jellybean Rom you requested, it is from MongooseHelix's build. It has a different Gapps package from what MongooseHelix actually established but I assume no issues may occur. :highfive:
https://copy.com/TgfFHxTqOHPJ
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