We got a handful of free On5's when we signed up with TMO (from VZW) last year. No one really liked them much, so they have been mostly replaced by better phones. We do have two in use, however. Once was for my daughter, who was just using it on WiFi. I had loaded TWRP 3.0.2.0 on it and rooted it, but had all sorts of problems with the com.android.phone error messages. Since she is starting middle school next year, we thought it was time to add a line for her. I got the SIM via next-day air, but noticed that whenever it was in, the IMEI and IMEISV would show up as "Unknown". If I removed the SIM and rebooted, it would show a proper IMEI number.
I did a full wipe (including the internal SD card) and restored from some downloaded md5/tar files to quote-unquote "start over". Now the incessant com.android.phone messages are gone (thank God), but the IMEI is still showing "unknown", except now, it's even showing unknown when the SIM slot is empty. I also tried throwing my SIM in to see if it was an issue with her SIM, but it still shows unknown and SIM not inserted in the status bar.
From what I understand, the EFS partition contains the IMEI info. I tried a dd command to rebuild the EFS, which actually worked on my Axon 7 when I had a similar issue (no radio functions to speak of), but it didn't help. The phone is exactly the way it was.
Here are the commands I ran. Maybe they are different for the Galaxy On5?
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2 bs=16384
While I didn't save the output, it was very similar to this (including the "no space left" messages) output from my Axon 7.
Can anyone help?
Code:
/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst1 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst1': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001917 seconds, 1.0GB/s
/dev/block/platform/soc/624000.ufshc/by-name # dd if=/dev/zero of=/dev/block/boo
tdevice/by-name/modemst2 bs=16384
dd: writing '/dev/block/bootdevice/by-name/modemst2': No space left on device
129+0 records in
128+0 records out
2097152 bytes (2.0MB) copied, 0.001829 seconds, 1.1GB/s
/dev/block/platform/soc/624000.ufshc/by-name #
c:\Users\chris\Desktop\Chris Phone\Axon\modem_a2017u>
Bump.
You may give a try to z3x box.
It is good tool to repair null/unknown imei or baseband..
@ßh! said:
You may give a try to z3x box.
It is good tool to repair null/unknown imei or baseband..
Click to expand...
Click to collapse
I ended up picking up a Moto G4 to unlock and use instead, but I still would like to fix this and sell the phone. I will try z3x box tonight.
I have a issue with Efs. I cannot boot into the OS, have no root, or a custom recovery. In the stock recovery, I get an efs invalid argument message. Any ideas?
Trying the first method on this page
https://www.technobezz.com/fix-samsung-galaxy-unknown-baseband-version/
vtinoc said:
Trying the first method on this page
https://www.technobezz.com/fix-samsung-galaxy-unknown-baseband-version/
Click to expand...
Click to collapse
That was one of the first things I tried. I tried both methods. I don't remember how they failed, but they did. I'll try again, hopefully this weekend.
Try
in TWRP select "Mount" then tick efs, go back then select "Advanced" "File Manager" open efs folder select the check mark icon on lower right delete, then reboot phone.
If this works and you get network reboot into TWRP and backup efs.
vtinoc said:
Try
in TWRP select "Mount" then tick efs, go back then select "Advanced" "File Manager" open efs folder select the check mark icon on lower right delete, then reboot phone.
If this works and you get network reboot into TWRP and backup efs.
Click to expand...
Click to collapse
That was easy enough to try... but it didn't work. The folder won't delete. Here's the error I get:
Code:
rm -rf "/efs" process ended with ERROR: 1
Did the process look like this?
Or can you just clear out the folder from a root browser. Then reboot.
Have you recovered from Kies by input of your model name and S/N
Yup. It looked just like that. I also tried via terminal and root browser. Both of those actually deleted the folder. They were back after a reboot, but were still empty.
I did try Kies. It seemed to work,but after it was done, I still had no radio/imei.
Steps I have taken
Have a good rom that you can Flash from TWRP via zip On ext SD, One I use is Superstarz On5.
Steps:
Recovered from Kies from S/N let boot into setup but dont setup
Turn off, boot into Download mode flash TWRP via Odin(untick auto reboot), remove battery
Place back battery boot into phone boot into recovery. Select Wipe and tick all but Ext SD.
Then install Rom Zip. If Superstarz in Aroma choose Hard Format, once done reboot let sit to install rom.
vtinoc said:
Steps I have taken
Have a good rom that you can Flash from TWRP via zip On ext SD, One I use is Superstarz On5.
Steps:
Recovered from Kies from S/N let boot into setup but dont setup
Turn off, boot into Download mode flash TWRP via Odin(untick auto reboot), remove battery
Place back battery boot into phone boot into recovery. Select Wipe and tick all but Ext SD.
Then install Rom Zip. If Superstarz in Aroma choose Hard Format, once done reboot let sit to install rom.
Click to expand...
Click to collapse
You think that will restore the IMEI?
Its how I got mine back atlest
Odin has a Clear ESR tick, try reading on what that does
vtinoc said:
Its how I got mine back atlest
Odin has a Clear ESR tick, try reading on what that does
Click to expand...
Click to collapse
Cool. I will try that tonight.
Trying to resist not shooting the damn thing with my .308.
You can go to
https://firmwarefile.com/samsung-sm-g550t
Download file for Odin
Unzip
Run odin untick auto reboot click CP look for download CP file from Unzipped Odin files
Flash.
CP is the Baseband firmware
vtinoc said:
You can go to
https://firmwarefile.com/samsung-sm-g550t
Download file for Odin
Unzip
Run odin untick auto reboot click CP look for download CP file from Unzipped Odin files
Flash.
CP is the Baseband firmware
Click to expand...
Click to collapse
So if I do that, I don't need to do the recovery from Kies?
I would try the odin 1st its the fastest and seems like the best way
vtinoc said:
I would try the odin 1st its the fastest and seems like the best way
Click to expand...
Click to collapse
I'll try that first then. Hopefully I get some time tonight to mess with it.
Both of those say "Thailand". I would need the US-based ROM. Or does it matter... since I'll probably be putting something else on it anyway? If I'm stopping at the setup screen, it doesn't even need to be in English, I suppose.
Related
N900W8 - unlocked Canadian version
Long story short, phone's stuck in a bootloop.
I can get into Download/Recovery, but can't mount anything in recovery. I can connect via Odin, but Win7 doesn't see the phone (so I can't transfer files).
I have a feeling my EFS is ****ed, which is why it won't boot. Is there a way to fix this, considering my connectivity situation?
I'm coming from a GNEX, which is obviously much easier to deal with than the note 3.
Any help is (obviously) greatly appreciated.
In case anyone else has this problem, I figured out the solution.
1 - boot to custom recovery (TWRP).
2 - follow steps outlined here: http://forum.xda-developers.com/showthread.php?t=2471421
Using TWRP Terminal Command To Complete this evolution...
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command"
3. Hit "Select" (lower right corner)..Do not select any specific folder, just hit select..
4. keyboard will open, type in the following commands, make sure you put the spaces and / where they need to be, it needs to look exactly as outlined..
mke2fs /dev/block/mmcblk0p12
Hit Go - The command will run. Clear the box, type the following command
mkdir /efs
Hit Go - The command will run. Clear the box, type the following command
mount -t ext4 /dev/block/mmcblk0p12 /efs
Hit Go - The command will run.
Click to expand...
Click to collapse
3 - reboot to recovery
4 - follow the steps outlined here: http://forum.xda-developers.com/showthread.php?p=47530627#post47530627
Download latest MJ4 firmware from SamMobile for the N900W8
Boot into custom recovery wipe System, Data, Cache, Dalvik
Boot into download mode and flash MJ4 via Odin (brings you back to stock)
Click to expand...
Click to collapse
n900w8
hi I have a samsung galaxy note 3 SM-N900W8
I lose my efs folder
My phone gets the bootloop
I can get download mod and recovery mod but the phone always rebooted (bootloop)
I'm trying all solution like
-fix boot loop .zip
-terminal commanded with TWRP
-flash it with a stock ROM ........
But no way my phone always bootloop
I think the problem about my efs folder
Can you give me efs folder N9020W8??
Please help ….
I’m sorry about bad English & thxxxxxxxxxxxxxxxxxxxxxxxxx a lot
Anyone know where I can get twrp for SM-G390W?
I am having the same problem as you are efs folders won’t mount and phone is stuck in bootloop. If anyone can help with this problem it would be greatly appreciated thx.
TWRP is twrp.me
Or the forum for your phone .
Hi all,
I just recived my sprint lg g2, i was asked whether to update the system to the sprint network, being a mistake i clicked yes. Im in new zealand so i thought it wouldnt matter. Bad mistake and it took me to the twrp menu... I simply wanted to restore the phone back to factory settings or just return to how it was before. (I had no idea that twpr was installed on ge phone to begin with)
However i cant seem to figure it out. Ive backed it up not that that really matters, but when i go to reboot system it says
"your device does not appear to be rooted, install supersu now? This will root your device".
I swipe and it reboots simply back to twrp... How do i escape this?
Thank you so much
Someone please help me
I do not know what to do... When i go into the restore folder there are no files. Does this mesn i have turned the phone into a brick?
Before there were two files in the restore section niw they have disappeared! I have not connected this phone to a computer... I am really upset because all i simply did was allow sprint to update the phone and it is not connected to any network! Eifi only......
I just want to get out of the twrp and go back to how the phone was when i recieved it, is it possible? Please help me
Hotbunny said:
Hi all,
I just recived my sprint lg g2, i was asked whether to update the system to the sprint network, being a mistake i clicked yes. Im in new zealand so i thought it wouldnt matter. Bad mistake and it took me to the twrp menu... I simply wanted to restore the phone back to factory settings or just return to how it was before. (I had no idea that twpr was installed on ge phone to begin with)
However i cant seem to figure it out. Ive backed it up not that that really matters, but when i go to reboot system it says
"your device does not appear to be rooted, install supersu now? This will root your device".
I swipe and it reboots simply back to twrp... How do i escape this?
Thank you so much
Click to expand...
Click to collapse
in twrp go to advanced, go to terminal command, press select, then type this
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
datechnerd said:
in twrp go to advanced, go to terminal command, press select, then type this
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Click to expand...
Click to collapse
ok thank you!
so it came up with this:
finished running boot script.
E:Storage partition '//TWRP/BACKUPS/04816da2910e8952' not found
then the above command dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota completed with 'no space left on device'
Somehow it seems the backup has been deleted.... I must have done this somehow trying to reboot.
What should I do next? thanks!!
This is what came back to be precise:
Finished running boot script.
E:Storage partition '//TWRP/BACKUPS/04816da2910e8952' not found
/ # dd if=/dev/zero of=dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd: writing 'dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota' : No space left on device
65537+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied.
2.004260 seconds. 16MB/s
Hey all. A couple of days ago it seem that there was an auto update that came in OTA. I had my phone plugged it to charge when the update showed up on the home screen. I did not do the update but left my phone on and plugged in to charge overnight. The next morning, I went to get my phone and the TWRP screen (TWRP that I previously installed) was on the home screen. Now I am stuck. I can not boot into the phone.
When I try to power my phone, I get the LG logo then the phone immediately boots into TWRP and here I remain. I can not get into the down load mode to restore to phone to factory defaults. I did have the phone rooted, unlocked, TWRP installed, Flashify installed, and Goo Manager installed, as well as being SU enabled.
I had a backup of Flashify, but it is gone. I have a TWRP backup, but when I try to restore it, I am still stuck in the TWRP screen after I reboot.
Here is what happens. I select the restore of the file that I have on the phone and on the TWRP log screen, it shows the following:
Finished running boot script.
[Restore Started]
Restore folder: '/data/media/0/TWRP/BACKUPS/016d06d0ce078bbe/1970-01-02--04-03-34 JDQ39B'
Skipping MMD5 check based on user setting.
Restoring 7 partitions...
Restoring boot...
[Boot done (1 seconds)]
Restoring Recovery...
[Recovery done (0 seconds)]
Wiping System...
Removing all files under '/system'
Restoring System...
[System done (156 Seconds)]
Wiping Data...
Wiping data without wiping /data/media ...
Done.
Restoring Data
[Data done (79 seconds)]
Wiping Cache...
Removing all files under '/cache'
Restoring Cache...
[Cache done (1 seconds)]
Restoring EFS...
Restoring efs2...
[EFS done (0 seconds)]
Restoring efs2...
[efs2 done (1 seconds)]
Updating partition details...
[RESTORE COMPLETE IN 243 SECONDS]
After that, I get the Reboot System. I reboot the system and the result is: I get the LG G2 symbol and I go right back into the TWRP screen with the options of "Install" "Wipe" "Backup" "Restore" "Mount" "Settings" "Advanced" and "Reboot".
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
It is like there is a file structure on the phone but no data whatsoever in the files structures.
NevetsDrassel said:
Hey all. A couple of days ago it seem that there was an auto update that came in OTA. I had my phone plugged it to charge when the update showed up on the home screen. I did not do the update but left my phone on and plugged in to charge overnight. The next morning, I went to get my phone and the TWRP screen (TWRP that I previously installed) was on the home screen. Now I am stuck. I can not boot into the phone.....
Help needed
It is like there is a file structure on the phone but no data whatsoever in the files structures.
Click to expand...
Click to collapse
Its funny and probably not a coincidence that this just happened to me two days ago. Fortunately, you have all the right safeguards installed and this should be an easy process.
Now, in mine, I had the exact same issue. What you will need to do is use either the terminal emulator on the twrp recovery menu or hook up the phone to your computer and use adb. There are only three lines of code to enter, one deleting the update, one disabling it's start, and one to clear the misc partition. I am currently in my phone now so I don't have the code but I will get on my computer soon and update with the code and it's source. Just make sure it is exact. Hold on a minute.
LG G2
livebyknight said:
Its funny and probably not a coincidence that this just happened to me two days ago. Fortunately, you have all the right safeguards installed and this should be an easy process.
Now, in mine, I had the exact same issue. What you will need to do is use either the terminal emulator on the twrp recovery menu or hook up the phone to your computer and use adb. There are only three lines of code to enter, one deleting the update, one disabling it's start, and one to clear the misc partition. I am currently in my phone now so I don't have the code but I will get on my computer soon and update with the code and it's source. Just make sure it is exact. Hold on a minute.
LG G2
Click to expand...
Click to collapse
Very much appreciated.
NevetsDrassel said:
Very much appreciated.
Click to expand...
Click to collapse
http://www.photo-cool.com/?p=48043
Here you go. Really simple process, just copy and paste the code after entering ADB terminal within the folder you have it in.
If drivers are an issue, look up Koush's universal android drivers
livebyknight said:
http://www.photo-cool.com/?p=48043
Here you go. Really simple process, just copy and paste the code after entering ADB terminal within the folder you have it in.
If drivers are an issue, look up Koush's universal android drivers
Click to expand...
Click to collapse
Within the folder that I have "what" in?
Got the drivers loaded and the system now recognizes an android device.
Started ADB
Copy and paste the code into "what" folder?
Thanks
Sorry I am new to this. Is this is what I was suppose to get?
C:\LG\Root Tools\ADB + Fastboot + Drivers>adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
~exit
# ←[6nadb rebootdd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fo
ta-backup.img
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 1.056265 seconds, 30.3MB/s
~ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/fota': No space left on devi
ce
65537+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 2.493231 seconds, 12.8MB/s
~ # dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on devi
ce
32769+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.675348 seconds, 23.7MB/s
~ # exit
C:\LG\Root Tools\ADB + Fastboot + Drivers>
And do I now reboot? or what?
Damn, it worked..... My phone is working again? Was this some type of virus or what?
Thank you thank you thank you for you assistance. You have saved me from the blackness of hell.
NevetsDrassel said:
Hey all. A couple of days ago it seem that there was an auto update that came in OTA. I had my phone plugged it to charge when the update showed up on the home screen. I did not do the update but left my phone on and plugged in to charge overnight. The next morning, I went to get my phone and the TWRP screen (TWRP that I previously installed) was on the home screen. Now I am stuck. I can not boot into the phone.
When I try to power my phone, I get the LG logo then the phone immediately boots into TWRP and here I remain. I can not get into the down load mode to restore to phone to factory defaults. I did have the phone rooted, unlocked, TWRP installed, Flashify installed, and Goo Manager installed, as well as being SU enabled.
I had a backup of Flashify, but it is gone. I have a TWRP backup, but when I try to restore it, I am still stuck in the TWRP screen after I reboot.
Here is what happens. I select the restore of the file that I have on the phone and on the TWRP log screen, it shows the following:
Finished running boot script.
[Restore Started]
Restore folder: '/data/media/0/TWRP/BACKUPS/016d06d0ce078bbe/1970-01-02--04-03-34 JDQ39B'
Skipping MMD5 check based on user setting.
Restoring 7 partitions...
Restoring boot...
[Boot done (1 seconds)]
Restoring Recovery...
[Recovery done (0 seconds)]
Wiping System...
Removing all files under '/system'
Restoring System...
[System done (156 Seconds)]
Wiping Data...
Wiping data without wiping /data/media ...
Done.
Restoring Data
[Data done (79 seconds)]
Wiping Cache...
Removing all files under '/cache'
Restoring Cache...
[Cache done (1 seconds)]
Restoring EFS...
Restoring efs2...
[EFS done (0 seconds)]
Restoring efs2...
[efs2 done (1 seconds)]
Updating partition details...
[RESTORE COMPLETE IN 243 SECONDS]
After that, I get the Reboot System. I reboot the system and the result is: I get the LG G2 symbol and I go right back into the TWRP screen with the options of "Install" "Wipe" "Backup" "Restore" "Mount" "Settings" "Advanced" and "Reboot".
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
It is like there is a file structure on the phone but no data whatsoever in the files structures.
Click to expand...
Click to collapse
Hey man im having the exact same problem, how do i exactly run the adb file? Im not sure if i still have it, what do i need to download, and when i did try it before it said my phone cannot be recognized, how did you fix your problem, can you walk me through please. Currently I am traveling and need my phone its useless right now.
fromc2m said:
Hey man im having the exact same problem, how do i exactly run the adb file? Im not sure if i still have it, what do i need to download, and when i did try it before it said my phone cannot be recognized, how did you fix your problem, can you walk me through please. Currently I am traveling and need my phone its useless right now.
Click to expand...
Click to collapse
I think that this will only work if you have TWRP already installed and have a TWRP backup file on the phone as the phone will revert to the last backup. Although this is an assumption on my part. It may revert to the phone factory default if you do not have a backup on the phone. As I indicated, I had been rooted, had Super User installed, had Flashify and TWRP installed on the phone and was locked in a TWRP bootloop that I could not get out of no matter what I did.
I am running Windows 7 Pro so these instructions may vary if you are running a different OS on your computer.
Get the Koush's universal drivers and install them on the computer. The regular LG drivers will not recognize the phone.
Get and download the "ADB + Fastboot + Drivers.zip" file found here and install in on the computer. Or found here.
Plug your phone into the computer and the computer should see your phone under the device manager properties as an "ADB Interface" "AndroidNet Sooner Single ADB Interface" (from the Koush universal drivers you installed. Originally, I think my phone was listed as a VZW device but it did not matter)
You have to run the ADB.EXE script from the computer in a CMD.EXE window that you are running with administrative privileges. Open a CMD.EXE window and navigate to the directory that has the ADB + Fastboot + Drivers folder. I had to navigate from /windows/system32 directory to C:/LG/ADB + Fastboot + Drivers/ directory (this is where I installed it on my computer) and type DIR and you will see the ADB.EXE command. Type "ADB SHELL (paste script here from other thread)", (without the quotes) then enter and it will run the script on the phone.
Restart the phone and it should work.
My phone reverted to an October backup, last one that I had on the phone.
If this does not work for you, I suggest that you start a new thread with your specific problem. You may have to flash the phone.
I do not know what the OTA update was but I read a thread that indicated that it was a rolling advert widget. I think that it was more than that though.
Let me know if you have success with this as it worked for me.
If you do not have access to a computer, I do not know what you have to do. You may be able to enter the script using the terminal emulator on the phone if you have access to it in TWRP.
NevetsDrassel said:
I think that this will only work if you have TWRP already installed and have a TWRP backup file on the phone as the phone will revert to the last backup. Although this is an assumption on my part. It may revert to the phone factory default if you do not have a backup on the phone. As I indicated, I had been rooted, had Super User installed, had Flashify and TWRP installed on the phone and was locked in a TWRP bootloop that I could not get out of no matter what I did.
I am running Windows 7 Pro so these instructions may vary if you are running a different OS on your computer.
Get the Koush's universal drivers and install them on the computer. The regular LG drivers will not recognize the phone.
Get and download the "ADB + Fastboot + Drivers.zip" file found here and install in on the computer. Or found here.
Plug your phone into the computer and the computer should see your phone under the device manager properties as an "ADB Interface" "AndroidNet Sooner Single ADB Interface" (from the Koush universal drivers you installed. Originally, I think my phone was listed as a VZW device but it did not matter)
You have to run the ADB.EXE script from the computer in a CMD.EXE window that you are running with administrative privileges. Open a CMD.EXE window and navigate to the directory that has the ADB + Fastboot + Drivers folder. I had to navigate from /windows/system32 directory to C:/LG/ADB + Fastboot + Drivers/ directory (this is where I installed it on my computer) and type DIR and you will see the ADB.EXE command. Type "ADB SHELL (paste script here from other thread)", (without the quotes) then enter and it will run the script on the phone.
Restart the phone and it should work.
My phone reverted to an October backup, last one that I had on the phone.
If this does not work for you, I suggest that you start a new thread with your specific problem. You may have to flash the phone.
I do not know what the OTA update was but I read a thread that indicated that it was a rolling advert widget. I think that it was more than that though.
Let me know if you have success with this as it worked for me.
If you do not have access to a computer, I do not know what you have to do. You may be able to enter the script using the terminal emulator on the phone if you have access to it in TWRP.
Click to expand...
Click to collapse
Wow thanks for the detailed instructions and explanations! ok sorry about this but what do you mean by koushes universal drivers?? where do i get those, and also paste the adb shell from which thread are you referring to? I will try this
---------- Post added at 11:41 AM ---------- Previous post was at 11:34 AM ----------
NevetsDrassel said:
I think that this will only work if you have TWRP already installed and have a TWRP backup file on the phone as the phone will revert to the last backup. Although this is an assumption on my part. It may revert to the phone factory default if you do not have a backup on the phone. As I indicated, I had been rooted, had Super User installed, had Flashify and TWRP installed on the phone and was locked in a TWRP bootloop that I could not get out of no matter what I did.
I am running Windows 7 Pro so these instructions may vary if you are running a different OS on your computer.
Get the Koush's universal drivers and install them on the computer. The regular LG drivers will not recognize the phone.
Get and download the "ADB + Fastboot + Drivers.zip" file found here and install in on the computer. Or found here.
Plug your phone into the computer and the computer should see your phone under the device manager properties as an "ADB Interface" "AndroidNet Sooner Single ADB Interface" (from the Koush universal drivers you installed. Originally, I think my phone was listed as a VZW device but it did not matter)
You have to run the ADB.EXE script from the computer in a CMD.EXE window that you are running with administrative privileges. Open a CMD.EXE window and navigate to the directory that has the ADB + Fastboot + Drivers folder. I had to navigate from /windows/system32 directory to C:/LG/ADB + Fastboot + Drivers/ directory (this is where I installed it on my computer) and type DIR and you will see the ADB.EXE command. Type "ADB SHELL (paste script here from other thread)", (without the quotes) then enter and it will run the script on the phone.
Restart the phone and it should work.
My phone reverted to an October backup, last one that I had on the phone.
If this does not work for you, I suggest that you start a new thread with your specific problem. You may have to flash the phone.
I do not know what the OTA update was but I read a thread that indicated that it was a rolling advert widget. I think that it was more than that though.
Let me know if you have success with this as it worked for me.
If you do not have access to a computer, I do not know what you have to do. You may be able to enter the script using the terminal emulator on the phone if you have access to it in TWRP.
Click to expand...
Click to collapse
I cant open the adb+fastboot drivers, it says windows cannot open. I have a windows 8 computer.
fromc2m said:
Wow thanks for the detailed instructions and explanations! ok sorry about this but what do you mean by koushes universal drivers?? where do i get those, and also paste the adb shell from which thread are you referring to? I will try this
---------- Post added at 11:41 AM ---------- Previous post was at 11:34 AM ----------
I cant open the adb+fastboot drivers, it says windows cannot open. I have a windows 8 computer.
Click to expand...
Click to collapse
You can get the Koush drivers from here.
You can get the script from http://www.photo-cool.com/?p=48043
Can't help you with Windows8. I know nothing about it. The ADB + Fastboot + Drivers is a .zip file. You have to unzip the file and put it on a directory of your choosing. I put my in C:/LG/ADB + Fastboot + Drivers/
Once you unzip the file (you can use 7Zip found here ) you will see the ADB.exe application along with 5 other .dll/applications/files in the folder.
livebyknight said:
http://www.photo-cool.com/?p=48043
Here you go. Really simple process, just copy and paste the code after entering ADB terminal within the folder you have it in.
If drivers are an issue, look up Koush's universal android drivers
Click to expand...
Click to collapse
This link is dead. Can you please give me another link? It's very urgent.
Just use this Toolkit
http://www54.zippyshare.com/v/29970713/file.html
Download D800 Rom and then add the .zip folder to Toolkit v1,5 - sideload folder
First you need to enter TWRP and then go to Advanced and press ADB Sideload Swipe
It's easier to rename it like rom.zip
Now start the start.bin
Select language
Enter
In my opinion it's 1 , enter
Then press 7) Install ROM/ Unbrick via SideLoad
Enter
and write the rom name that is in the sideload folder ( becouse i renamed it it's rom.zip in my opinion)
Now wait for the rom is pushin trough sideload
The installation process will start automatic .
I hope you got this by now,., had this happen to me...I found the thing to do..
On your TWRP terminal command type this codes.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then hit enter and back out of terminal to reboot system
Help me plz same thing im facing with my lg g2
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
mehler said:
I reboot into the following screen with "System" "Power Off" "Recovery" "Bootloader"
If I reboot into System - I wind up at the TWRP screen again after the LG logo.
If I reboot into Recovery - I wind up at the TWRP screen again after the LG logo.
If I reboot into Bootloader - I wind up at the TWRP screen again after the LG logo.
If I reboot into Power Off - when I power on I wind up at the TWRP screen again after the LG logo.
I tried a hard factory reset - back into the TWRP screen after the LG logo.
My computer does not recognize the LG G2 like it used to - I was able to see the SD card and get into it. Now, all I can find is the LG G2 under the Device Manager, Other Devices, G2 but the advanced properties show "Drivers not installed" and I can not install them.
How do I save my phone? I have some LG G2 backups on the computer, I have a Flashify Back Up on the computer, and I have a copy of the TWRP backup on the computer. But I can not get into "download mode" and doing a factory hard reset does nothing.
Help needed
Click to expand...
Click to collapse
I am also in same situation. I have cyanogen recovery. haven't find any solution by readings in forums. biggest problem is my phone and adb server. adb shell never works. my phone is unauthorized. only work is sideload, but cannot install zip file. stuck every time on 47% and thee phone reboots and back to cyanogen recovery screen.
anybody had really solved this kind of problem.
any help is highly appreciated. there might be guys like me looking for solution.
Hey Guys,
i good a little problem with my axon 7. ive got the g model with cm13 and yesterday i tryed to flash the b29 o n my phone.
now the problem is that my sim card is accepted and the imeis are correct but i have no data connection at all.
so i tryed to go back to b03 oder other otas for the g model but i cant install any of this updates.zips in recovery because of error 8.
older backups dont fix the problem even and when i want to go back to the first backup i made after rooting the phone then it tells me that something is wrong withe the encoding...
so has anyone an idea how i can fix that problem?
for everyone with the same issue:
is used this guide (https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484) and it worked.
-> if you get the "encryption error1 after flashing the rom then just press reset phone.
-> if the divice doesnt boot after flashing just boot into recovery frist and reboot system in there.
but be sure that you havent any impiortant flies on internal sd card!
Try this: boot into TWRP recovery and in "advanced" go to Terminal Emulator
There, enter these codes
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
and execute and then enter
Code:
dd if=/dev/zero of=/dev/block/bootdevice/modemst2
and execute
This should erase those partitions and they should regenerate automatically on boot.
If this doesn't help, you could indeed try to use someone else's modems
EDIT: damn, too late
Now we have two solutions!
thank you
OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521
Your first link for the userdata image says file not found when you go to that link.
UPDATED USERDATA
freedomwarrior said:
Your first link for the userdata image says file not found when you go to that link.
Click to expand...
Click to collapse
Sim unlock
Hey guys,
has anyone managed to find a way to simunlock this phone? I bought one on blackfriday for $49 and since then its been sitting in my closet because it does not accept any other network's sim.
aslezak said:
UPDATED USERDATA
Click to expand...
Click to collapse
That one don't work either
FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs
The problem with this seems to be, at least for me, that a .bz2 file is not recognized by the recovery as an installable zip.
The dd trick worked for me, but the system image here, is not full stock. IT seems to have a mix of super_su and magisk in it.
Root is working, but I can't seem to mount system as r/w
So trying to figure this out. I used this image to do a restore, and my phone was rooted with magisk.
First time a program tried root, it said that super su was installed. When I went to another one, it said that magisk was installed.
Anyrate, at one time I was able to mount system r/w and make changes. Now it seems that I can't for whatever reason. I don't know exactly how I got it
to the state to be able to modify the system.
I actually pulled an entire copy of the rom at one time, with a dd command. Of course that can't be reflashed from twrp. But I'd like to be able to mount it somehow on a pc so I could do a stringsearch for all files that have an ro, in them to find the master files where the filesystems are mounted, and edit those....
crashburn833 said:
OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521
Click to expand...
Click to collapse
the system.img requires a monthly membership, could an updated link using something like mega or mediafire be created please?
one789 said:
FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs
Click to expand...
Click to collapse
what custom rom?
HELP PLEEEASE! Bricked h1711
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!
mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Hard bricked Dreaded QHSUSB_BULK issue. Need mmcblk0.img PLEASE PLEASE HELP!!!! I've lost recovery and fastboot! Nothing but a black screen and a blue light.
Click to expand...
Click to collapse
divineBliss said:
mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Click to expand...
Click to collapse
What do you recommend I do? All I have is a black screen and a blue light? thank you btw
If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Whit3Rabbit said:
What do you recommend I do? All I have is a black screen and a blue light? thank you btw
Click to expand...
Click to collapse
divineBliss said:
If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Click to expand...
Click to collapse
That's what I was afraid of Thank you for the quick response.
Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!
Click to expand...
Click to collapse
What is the link to the info you found?
I have the image you need, but it is 15 GIGs in size, and there is no practical way to send that. I also have a system image, and a boot image with magisk in it, as per the OP.
P.M. me.
I don't see how you can recover this if you don't have recovery or fastboot, and can't boot into the phone. If the bootloader is corrupted, well I just don't know.
Can you get into twrp?
You do know that there are two recoveriess, one erecovery and another recovery.
It seems that POWER and VOL up may get you into one, and POWER and VOL down may get you into another one.
NOTE: I KNOW you can't flash the image via fastboot, cause I tried it. it is just to big.
The files are all to big to post here....
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 I put this up 6 days ago for someone else. I don't know how long the link is good for.
This is the system image from the non-working link. You will need to untar it.
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 <<<<<<<<<< file from Original Post
https://nofile.io/f/vTRffT3CM0s/erecovery.zip <<<<<<<<<< erecovery is same as stock recovery
https://nofile.io/f/3DRA4bYjdsq/twrp-xt2.7z <<<<<<<<<< Hweng's original twrp
https://nofile.io/f/uAET5bTqQVk/patched_boot.zip <<<<<< bootloader patched with magisk for a root that does not touch the system partition.
I'll try to put the 15 gig mmblockp0 up here if it will take it, but it is at the office.
I hope this helps.
I now also have a virgin system image, stock. The image given above appears to also have supersu installed it int.
at least it has a su in the system image. Where magisk, just patches the boot image as I understand it.
Any luck on that stock system.img? I formatted mine like an idiot and now sitting on a phone with no OS
same as above, i will even take the rooted system.img i have all other files needed.
I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it
littletech said:
I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it
Click to expand...
Click to collapse
step by step root > https://forum.xda-developers.com/hu...ooting-restoring-huawei-elate-h1711z-t3764391
the files for root are the same for the Elate and the XT2
Blue light black screen fix
Whit3Rabbit said:
That's what I was afraid of Thank you for the quick response.
Click to expand...
Click to collapse
My device suffered the same fate, only a blue light black screen unable to enter boot or recovery. I slowly removed the back cover using my fingernails and removed the two screws holding the metal plate above battery on the right. Popped the left most plug to disconnect the power flow and allow phone to power off completely. Be careful not to touch any of the metal near the plug or you will short. I plugged it back in and held volume down while I inserted USB connected to computer. Tada!! Back in action fastboot ready... So OK now what?? I can't seem to be able to flash an update. Zip just keeps saying failed to load, and system image is too big. Can someone point me to the correct files I need to get her working again? Thanks in advance.