Database Users

Bootloop LS980

Hey,
I had installed TWRP and CM10.2 with no issue, ioroot11.
I let my buddy use the device, he jacked it up...its stuck in the LG boot logo loop... I can still boot in to TWRP but cm10.2 is gone along with everything else that was on the storage. Its clear now he wiped everything.
I need clear step by step instructions on how to overcome this issue.
Id rather just find a way to get cm back on to the storage but if i have to i will do a stock re install.
I need a list of working drivers, how to get adb set up and working correctly (adb devices says offline for my device atm), what commands to use to push cm10 back on to the device, what state the phone needs to be in order to push the cm10 zip (i only have bootlogo, download mode and twrp as device state options).
or i need a list of everything that is needed to install stock. as far as that goes, i need a direct link to sprints .tot file and directions on how to get that going.
TLR
Stuck in LG logo boot, still have TWRP..need help getting ANY type of rom installed. ADB push or Stock re install....
Thanks ahead of time to anyone who helps.
you guys are awesome!

HEWHOCORRUPTS said:
Hey,
I had installed TWRP and CM10.2 with no issue, ioroot11.
I let my buddy use the device, he jacked it up...its stuck in the LG boot logo loop... I can still boot in to TWRP but cm10.2 is gone along with everything else that was on the storage. Its clear now he wiped everything.
I need clear step by step instructions on how to overcome this issue.
Id rather just find a way to get cm back on to the storage but if i have to i will do a stock re install.
I need a list of working drivers, how to get adb set up and working correctly (adb devices says offline for my device atm), what commands to use to push cm10 back on to the device, what state the phone needs to be in order to push the cm10 zip (i only have bootlogo, download mode and twrp as device state options).
or i need a list of everything that is needed to install stock. as far as that goes, i need a direct link to sprints .tot file and directions on how to get that going.
TLR
Stuck in LG logo boot, still have TWRP..need help getting ANY type of rom installed. ADB push or Stock re install....
Thanks ahead of time to anyone who helps.
you guys are awesome!
Click to expand...
Click to collapse
For back to stock there's a thread in general forums you can also use the Verizon method with sprint files.....or you can read bout adb and download and setup on PC then push a ROM to TWRP and just flash.....you should always make a backup when your up and going again....I didn't post links cause I figured you could Google...instead of me

Thanks for your reply.
I have looked all over and was unable to find any information on what needed to be down to get adb working correctly on my device.
will you kindly link me to something explaining how to get adb working correctly with my phone. links to all the files needed.
when i use adb devices, it lists my device as offline. what state does my phone need to be in?
as for the stock restore, i download the sprint files but when i go to extract the TOT file, it does not extract correctly. will you please link me to the correct drivers needed for this process.
Thanks!

HEWHOCORRUPTS said:
Thanks for your reply.
I have looked all over and was unable to find any information on what needed to be down to get adb working correctly on my device.
will you kindly link me to something explaining how to get adb working correctly with my phone. links to all the files needed.
when i use adb devices, it lists my device as offline. what state does my phone need to be in?
as for the stock restore, i download the sprint files but when i go to extract the TOT file, it does not extract correctly. will you please link me to the correct drivers needed for this process.
Thanks!
Click to expand...
Click to collapse
Did you ever get your device back running? Im having the same problem? any help?

[Q] Help! Just broke my services.odex and cant get into my phone.

I was trying to unlock my wifi tether by editing services.jar. I renamed both services.jar and services.odex by adding ".bak" I replaced services.jar with the recompiled one but didn't replace services.odex. now when my phone boots up I get "unfortunately verizon login has stopped" as well as a few others and I can't get in. What can I do to fix this? Its a verizon S5 with the march 31 kernel version.

Restore your backup. Or you could replace just the files you renamed with an ADB shell session and push the required files. Or "dirty' flash just the system files. Or write a full, stock firmware image with Odin.
Those would be some of the ways to recover. Lots of existing threads on this, with further elaboration if you need further guidance.
.

fffft said:
Restore your backup. Or you could replace just the files you renamed with an ADB shell session and push the required files. Or "dirty' flash just the system files. Or write a full, stock firmware image with Odin.
Those would be some of the ways to recover. Lots of existing threads on this, with further elaboration if you need further guidance.
.
Click to expand...
Click to collapse
I don't have a backup or custom recovery, I just used towelroot and thought it would be pretty safe to unlock the wifi tether. I think I forgot to turn on USB debuging so I think ADB is out of the question. Is there a way to "dirty flash" with Odin?
Edit: just did a reset with Odin, this fixed the problem. The phone was new so there wasn't much on it and I do keep my contacts and messages backed up so not much is lost except for the inconvenience of setting everything back up. I will definitely be more careful in the future.

[Q] What can I do with system dump?

Can I recover my dead SG5 with system dump via CWM?
What can I do with it?

It is far from clear what you want to know?
You didn't say what happened to your phone, why it is "dead" or exactly what you mean by dead. CWM is a custom recovery but you didn't even tell us if you had it instlaled and therefore presumably have backups. Or if you are hopeful that CWM will fix your unspecified problem. And system dump is a vague term usually referring to making a backup on the command line using the dd utility.
We need a lot more information if you need help with something. Such as what happened to your phone, whether it boots to recovery or download mode, loads an ADB shell and so forth.
.

fffft said:
It is far from clear what you want to know?
You didn't say what happened to your phone, why it is "dead" or exactly what you mean by dead. CWM is a custom recovery but you didn't even tell us if you had it instlaled and therefore presumably have backups. Or if you are hopeful that CWM will fix your unspecified problem. And system dump is a vague term usually referring to making a backup on the command line using the dd utility.
We need a lot more information if you need help with something. Such as what happened to your phone, whether it boots to recovery or download mode, loads an ADB shell and so forth.
.
Click to expand...
Click to collapse
[Q] Somebody give me SCL23's build.prop(original)
I changed build.prop
My android phone is SCL23
AKA Galaxy S5
I am Korean but now I live in Japan for work.
So I used GalaxyS5 for KDDI AU
Some application didn't work on my phone.
Even impossible to install
So I tried to root. Then changed model and vendor from GalaxyS5 to Galaxy S4
But it didn't work for using those apps
So I copy all of texts of build.prop of GalaxyS4.
Then my phone dead.
AU's logo is the only thing I can see.
Before did that
I had do googling and find SCL23's CWM with Chinese letters.
It works well.
Factory reset? YES
Boot? NO
Can not normal boot
Odin mode
I connected phone to PC.
Fail to install USB driver.
I think it cause of phone's hardware and build.prop is not same.
I have external SDCard.
Odin work via USB
And I can go into CWM recovery mode.
So I think if I can find .zip, able to flash, of SCL23's build.prop
I can copy it into extsdcard with friend's android
Then go into CWM and flash it.
I need SCL23's build prop
And somebody make it .zip please
I don't know how to make it.
Please help me.
And thank you for read this poor English

fffft said:
It is far from clear what you want to know?
You didn't say what happened to your phone, why it is "dead" or exactly what you mean by dead. CWM is a custom recovery but you didn't even tell us if you had it instlaled and therefore presumably have backups. Or if you are hopeful that CWM will fix your unspecified problem. And system dump is a vague term usually referring to making a backup on the command line using the dd utility.
We need a lot more information if you need help with something. Such as what happened to your phone, whether it boots to recovery or download mode, loads an ADB shell and so forth.
.
Click to expand...
Click to collapse
I wrote it few days ago.
Nobody replied to me.
So I thought many ways and did googling for recover.
I found link of system dump of SCL23.
So now I want to know about what can I do with it for my android phone's revive.
Please help me

If you have a system dump made while your phone was working properly, you can simply restore that to resolve your problems. It's not clear that that is the actual case though.
In the alternative, the apparent cause of your problems is a non-viable build.prop. You should be able to boot to CWM and then use a ADB shell under CWM to rename or delete /sideload the bad build.prop file and replace it with a good copy. If you didn't keep a good copy, you can download the stock firmware for your phone and use winrar to extract the proper stock build.prop for your phone.
More than likely, if you can boot to recovery mode, then you will be able to boot to download mode as well. So Odin use should be possible. You can use Kies to install a driver. But try CWM first.
.

fffft said:
If you have a system dump made while your phone was working properly, you can simply restore that to resolve your problems. It's not clear that that is the actual case though.
In the alternative, the apparent cause of your problems is a non-viable build.prop. You should be able to boot to CWM and then use a ADB shell under CWM to rename or delete /sideload the bad build.prop file and replace it with a good copy. If you didn't keep a good copy, you can download the stock firmware for your phone and use winrar to extract the proper stock build.prop for your phone.
More than likely, if you can boot to recovery mode, then you will be able to boot to download mode as well. So Odin use should be possible. You can use Kies to install a driver. But try CWM first.
.
Click to expand...
Click to collapse
I tried everything you told to me.
But very problem is install USB driver.
Kies failed to find and install USB driver. It worked well before I did it.
So I can not do anything with ADB commands because of USB driver.
But only Odin work to phone.
So I can install CWM. And I can go into CWM recovery mode.
Of course I can go to Download mode.
Can I do something with Linux?
Can I mount My Phone with Linux without install USB driver and then change build.prop.bak to build.prop?
I really appreciate to your reply.
Thanks to your kindness.

If your USB driver was properly installed before the problem, it will continue to work just fine, at least for CWM mode. Build.prop will not interfere with that. So just go to the CWM command line and use the ADB commands to push (replace) the build.prop file.
Are you certain that Odin doesn't recognize the phone in download mode. Ensure that you are entering download mode by removing the phone battery, replacing it, then pressing and holding in order, the volume down, then home, then power key until you see the screen light up. Odin should see the phone and it should not matter if the build.prop file is corrupt. Only the normal boot will be affected by that.
If you have problems connecting ADB or Odin, a far more likely suspect is a bad USB cable. Try a different cable or USB port. And ensure that you are entering download mode in the manner described above. When Odin recognizes your phone, you can write a stock firmware image to you phone to recover.
I haven't used CWM for quite a while (I much prefer TWRP), but it should offer you a command line. So as an alternative, use your PC to write a good copy of the build.prop file to your SD card. Then in CWM you could mount the external SD card, then copy the file from the card to your system directory. In this method, you wouldn't even require the USB driver.
You have lots of options and there are lots of ttutorials on using CWM, ADB and so forth if you need elaboration. You should certainly be able to resolve this issue even though it may be a pain in the neck or somewhat intimidating if it is unfamiliar territory. Nevertheless you can fix it if you are patient.
If the worst case,an alternative would be to pay a cellular repair shop to do the software repair for you. Entirely up to you which is the better approach.
.

Easily Apply OTA Update To Rooted Nexus 6

I had a hard time finding this information, so thought I would post a new thread!
After you root your phone, even if using standard recovery, the OTA updates will no longer install. You may get the notifications, but after it reboots to install, you will get a failed notification. Even if you uninstall root. This is because if there is any change to the system image at all, the OTA update will fail.
To install it is actually easy, just requires some legwork. I assume you understand what the bootloader is, and what adb and fastboot tools are since your phone is already rooted. If you used a toolkit, there are plenty of guides on XDA on how to install these tools manually.
Step 1 - Collect Needed Files:
Visit the Google System Images page and download the image for your existing ROM. Check your About Device page to get the exact ID, it should say something like LVY48E.
Extract the system.img file so you can flash it later.
Download the OTA image. All OTA images are listed on the Nexus 6 OTA Images thread. Find the file which upgrades "From" your current ROM id. It will only work if from matches your current image version. It will be named something like 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip, and this file in particular flashes to the new LVY48F version from LVY48E version.
Step 2 - Flash Stock System Image:
This step replaces your system image with the stock system image. This will not delete your apps or other personal data, only the information stored on the system partition. The only exception is if you rooted and stored any data on this partition. Plug your phone into your computer. There is no way to do this without a PC.
Reboot into bootloader mode either from booting with POWER+VOLDOWN or via adb:
Code:
adb reboot bootloader
and flash the image
Code:
fastboot erase system
fastboot flash system system.img
At this point your system is stock again (unrooted).
Step 3 - Flash Update Image:
Enter the recovery mode. You can also do this via TWRP but I will cover with stock recovery. Press Volume Up/Down until you see RECOVERY and press power to choose. You are now in recovery.
Press and hold Power and tap Volume Up once to get the recovery menu. Then use Volume Up/Down to select "apply update from ADB" and then Power to select
I had to unplug and plug my phone back in at this point to get it to show up to adb. You can confirm it is visible with the command adb devices.
Apply the OTA update file using the following command, replacing the file name with your own:
Code:
adb sideload 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip
After a few minutes the sideload will complete, the phone will reboot and optimize apps, and you can verify the update worked by checking your about system page again.
To root your device again, re-install SuperSU and you're good to go.

I actually just asked about this in the T-Mobile thread, but thanks for making this. My question is, when installing system.img is there anything else you NEED to flash as well, specifically boot and/or cache?
Google has the latest stock image for T-Mobile so I was planning on flashing system and radio, but I wasn't sure if there was anything else required when flashing system.img.
I know I don't want recovery or userdata as that would replace TWRP and all my data, so I'd of course leave those out.

hayzooos said:
I actually just asked about this in the T-Mobile thread, but thanks for making this. My question is, when installing system.img is there anything else you NEED to flash as well, specifically boot and/or cache?
Google has the latest stock image for T-Mobile so I was planning on flashing system and radio, but I wasn't sure if there was anything else required when flashing system.img.
I know I don't want recovery or userdata as that would replace TWRP and all my data, so I'd of course leave those out.
Click to expand...
Click to collapse
Nope, system.img was all that I flashed, verified it worked fine with just that.

So you just have to re-root after right?

JTheAppMerchant said:
So you just have to re-root after right?
Click to expand...
Click to collapse
Correct

Thanks for this guide. I've been trying to figure out how to do this exact thing. When I do the command:
adb sideload 4458964f84d2e44ecd2c1c31c301d47eec4b080e.signed-shamu-LMY48M-from-LMY48I.4458964f
Click to expand...
Click to collapse
it gets to about 50%, then gives a Error message,
E:Error in /sideload/package.zip (Status 7) Installation aborted.
Click to expand...
Click to collapse
Any suggestions?

falconfox said:
Thanks for this guide. I've been trying to figure out how to do this exact thing. When I do the command:
it gets to about 50%, then gives a Error message,
Any suggestions?
Click to expand...
Click to collapse
First try a different USB cable and port.

Thanks for the guide. Does it wipe all the data and files in internal storage?

I did this successfully
torecdude said:
Thanks for the guide. Does it wipe all the data and files in internal storage?
Click to expand...
Click to collapse
I wanted to say thanks first of all for putting this up. It helps those rooted users out there that do actually want security patches applied to the system image. To answer the question above, No it does not wipe data or storage if you follow the instructions to only modify /system partition.
A note about the LMY48M update file and the above comments in the OP : This update changes the kernel (in other words), the boot.img file as well. So if you have flashed a non-stock kernel, you will need to go back to stock during the update (and I suggest just leaving it). That is the partition called boot where boot.img lives. It mainly is the kernel. The way to go back to stock (say if you flashed franco with the FKupdate tool and did not do it manually) is to simply do like above and flash it from the factory image he mentions above for 48I file.
You reboot to the bootloader (*I assume you know how*) with power and vol down button. And then the following command after flashing system.img:
fastboot flash boot boot.img
This takes you to stock LMY48I and should allow you to update now to 48M. I learned this by watching the update failure messages as well as noticed it has boot.img changed in the zip file. Hope this helps others. :good:

bitpushr said:
First try a different USB cable and port.
Click to expand...
Click to collapse
I'm having the exact same issue/error. Already tried new USB ports and cables.

falconfox said:
When I do the command:
it gets to about 50%, then gives a Error message, Any suggestions?
Click to expand...
Click to collapse
confused2much said:
I'm having the exact same issue/error. Already tried new USB ports and cables.
Click to expand...
Click to collapse
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.

jase33 said:
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
Click to expand...
Click to collapse
I'll try this now, thanks for the response!

Honest question: why would you flash a system image and an ota when you could just flash the new system image?

jhotmann said:
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
Click to expand...
Click to collapse
By flashing just the current system image your data stays in tact. Then you can take the OTA, it will see the system image unmodified, and it will update everything for that new version without wiping data.

jase33 said:
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
Click to expand...
Click to collapse
I do not have the text "assert" anywhere in that file....

jase33 said:
By flashing just the current system image your data stays in tact. Then you can take the OTA, it will see the system image unmodified, and it will update everything for that new version without wiping data.
Click to expand...
Click to collapse
Easier to just flash the new system image that gets you to the same place as the OTA.

jhotmann said:
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
Click to expand...
Click to collapse
I was wondering this same exact thing, but I was assuming it was because the OTA was hitting people before that matching Google Factory Image was available. This would bring you almost back a version (to being stock) so you could take the OTA.
If the OTA is to match the same Factory Image you can get from Google, I have no idea why you'd do both steps.

Hi, I have the LNX07M, and I don't find it in the google page. Can you help me? please!

hayzooos said:
I was wondering this same exact thing, but I was assuming it was because the OTA was hitting people before that matching Google Factory Image was available. This would bring you almost back a version (to being stock) so you could take the OTA.
If the OTA is to match the same Factory Image you can get from Google, I have no idea why you'd do both steps.
Click to expand...
Click to collapse
I think the only reason to do both steps is to apply the update ASAP. If you are ok waiting, then only flash the new system.img. That's definitely what I always do. I don't mind waiting. I have Google Play Services notifications hidden now anyway, so those update notifications don't show up and bug me.
Thanks for the walk through though, @bitpushr, I'm sure many can make use of it.

confused2much said:
I do not have the text "assert" anywhere in that file....
Click to expand...
Click to collapse
Honestly, you shouldn't edit those files as that can be dangerous, and disabling the filesystem check can be dangerous, and it probably won't work because then the zip would fail signing verification.
If you followed all of the instructions in OP and still get error 7, try, on top of erasing and flashing the stock system.img, also extract and erase then flash boot.img and recovery.img. You will get error 7 if your recovery and kernel (boot.img) aren't stock.

Almost soft-brick my device. Need help, Emergency!!

Hey guys!
This is my first ever thread on XDA! And my problem goes like
I have a Asus max Pro m2 device. And also I'm familiar with things like custom ROMs, custom recovery, rooting and all that stuff. I have been using custom ROMs, etc etc.. from a long time. And I use TWRP as my recovery system. Recently I tried to install lineage OS on my phone, but it gave me an error 7. Then I searched on google about what is error 7. Tried all the solutions, nothing worked. Then I thought it's happening because of my phone's modem. So I searched for the latest modem file for my device, then I got a file on XDA. And that was a TWRP backup file of the Modem and the EFS. So I downloaded it and restore the file through TWRP. And from there, I'm not able to install any custom rom on my device. I tried many of them but couldn't. All of them have me an error 7.
But before that everything was fine. I was in evolution X custom rom. And that file ruined my device completely. Now I'm completely helpless, clueless. So what to do. Any expert suggestions?
PLEASE RESPOND!!!

Hi, if you didn´t solve this problem watch this video that has the solution for asus zenfone max pro m2 brick devices. Keep in mind that when you do this, the phone gonna be with the first oreo version, relock bootloader and unroot your device so you have to uptade manually.

Copy the zip ROM file to your PC and unzip it using your favorite archiver (for example, 7-zip);
After unpacking find META-INF folder and go the META-INF/com/google/android line. In the last directory you will find two files called "update-binary" and "updater-script". We are interested in the latter one;
Rename "updater-script" to "updater-script.txt" and open it in any text editor (for instance, Notepad++);
Now remove the line starting with "assert" to the next semi-colon. Usually it is the first or a few first lines in the beginning of the text file;
Save the modified file;
Rename "updater-script.txt" back to "updater-script";
Update all files you have unpacked;
Copy the modified zip-file on your phone;
Reboot your Android device to recovery mode and try to update it again. Status Error 7 should be gone.