Hello, I tried to update via OTA and I have TWRP installed, after applying the update, I'm stuck at recovery. I have searched google for answers and found this :
Code:
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
Type in this codes in TWRP Terminal. After that, I was able to get pass through TWRP, and my G3 has not been updated.
Now the problem is:
1. When I checked my MAC Address, it has changed, same with my SW Version which is from V10i-ESA-XX to V10i-GLOBAL-COM
2. I tried to update via OTA (sw version is still v10i GLOBAL) but it tells me that I have already installed the latest version.
3. I have flashed a KDZ file based on my IMEI but the SW version is still GLOBAL, the MAC address too is not my old MAC address anymore
Mine is a D855. I could use some help.
Related
I had an Lg G3 D855 32Gb with V10a.
I applied root with purpledrake and I installed TWRP recovery.
By a mistake I made an OTA update that cause bootloop.
After wipe cache and use this command:
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
my LG G3 restarts with V10a firmware, but with different WiFi Mac Address.
1) I try to restore my backup made with TWRP;
2) I restore only modem (from backup I made with this command with adb shell:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/modemst2.img)
using adb shell;
3) I try to restore that two img using terminal command shell in TWRP;
4) I try to restore my LG G3 to stock using LG PC Suite restore
but WiFI Mac Address remain different from the original one!
Can you help me to restore original Mac Address?
Thanks!
Enter download mode and flash stock firmware?
Isn't it the same with LGSuite "restore after bad update"???
If not, where can I find the correct firmware for my phone?
Can you explain me?
[Guide] LG G3 Stock Firmware (Go Back to Stock)
aparty said:
I had an Lg G3 D855 32Gb with V10a.
....
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
...
Thanks!
Click to expand...
Click to collapse
You destroyed your misc partition, which held your wifi and bt mac's + region info. Which guide did you follow? Who's stupid enough to offer people to wipe phone-unique partition?..
No, it is not recoverable unless you have a backup (or access to LG's service tools).
You can ask someone to send their misc to you, then edit region/imei/mac's information via hex editor.
YaDr said:
You destroyed your misc partition, which held your wifi and bt mac's + region info. Which guide did you follow? Who's stupid enough to offer people to wipe phone-unique partition?..
No, it is not recoverable unless you have a backup (or access to LG's service tools).
You can ask someone to send their misc to you, then edit region/imei/mac's information via hex editor.
Click to expand...
Click to collapse
I made a complete backup with TWRP when I installed it.
Can I use that backup to recover that info, now?
If so, can you explain me how?
Thanks!
aparty said:
I made a complete backup with TWRP when I installed it.
Can I use that backup to recover that info, now?
If so, can you explain me how?
Thanks!
Click to expand...
Click to collapse
No, you can't. TWRP backup doesn't contain misc patition.
YaDr said:
No, you can't. TWRP backup doesn't contain misc patition.
Click to expand...
Click to collapse
No way to solve?
Can you explain me better how to edit a different partition?
Imei didn't change. Only Wifi Mac Address.
YaDr said:
No, you can't. TWRP backup doesn't contain misc patition.
Click to expand...
Click to collapse
can you share your misc partition? I really want to fix my generic mac address (00:90:4c:c5:12:38) but I have no idea which area to edit since i cant find the address in hex editor.
right now I only have temporary fix by changing my mac address from /data/misc/wifi but it wouldn't stick after reboot. If its too much, maybe just point me where to edit the partition? thanks!
First of all dont go to that menu. U will brick. Does anyone have a solution? Google is NOT helping!!!
thenobileone said:
First of all dont go to that menu. U will brick. Does anyone have a solution? Google is NOT helping!!!
Click to expand...
Click to collapse
Use ODiN find on XDA recommend version 3.10 and download a stock firmware based on your phone and flash it. Find a guide or so.
I am too stuck in the same boat. Did you find a fix for it?
I downloaded stock firmware and flashed it but still freezes then restarts.
im having the same problem... and the phone is restarting .. i cant access the menu againg... help please
This is a real bugger of a problem and simply reflashing firmware alone will not fix it. If your phone is still under warranty, I'd advise sending it back to Samsung for replacement. The following instructions were pulled off the GSM with credit to user Bsisco. You will need to know how to issue ADB commands and when it's all said and done, you may stop the bootlooping, but you will likely lose your original IMEI and have to write a new certificate which requires a Z3X box or other unlock repair box. KingRoot supplies a temporary root and requires repeating the steps after reboot. Proceed with caution and no guarantees included. Here is his solution:
1. Downgrade to 4.4.4 via Odin. Extract OC4, extract Odin, open Odin, select four files into correct position (BL, AP, CP, CSC) 4.4.4 OC4 Odin 3.09 (Samsung Mobile drivers required)
2. Once on 4.4.4 or below, enable developer options by tapping "build version" several times, enable USB debugging & mock location, and install KingRoot 4.0.0.233 to phone. Caution, newer versions did not work for me.
3. Open "Command Prompt" and type "adb version" should reply with "Android Debug Bridge version x.x.x", if does not, change to the correct directory where adb is installed via "cd" command.
4. These next two steps can be a little tricky as the phone often reboots before completed, must work quickly, I suggest copying the long command, then paste when ready.
5. Connect to working WiFi. Turn off your phone, reboot, or wait for it to reboot itself. Soon as phone turns on, open KingRoot, soon as WiFi connected notification appears, touch button in center of KingRoot app, soon as KingRoot reaches 30%, began adb commands.
6. ADB commands: first command "adb shell", second command "su", third command "dd if=/dev/zero of=/dev/block/mmcblk0p10 | dd if=/dev/zero of=/dev/block/mmcblk0p13 | dd if=/dev/zero of=/dev/block/mmcblk0p14 | dd if=/dev/zero of=/dev/block/mmcblk0p15 | dd if=/dev/zero of=/dev/block/mmcblk0p16" phone will reboot or you can reboot and after reboot boot-loop and unknown baseband will be fixed! Can now write new IMEI via "Write Cert" and possibly "Write QCN" if any network troubles, then all good to go!
brg7562 said:
This is a real bugger of a problem and simply reflashing firmware alone will not fix it. If your phone is still under warranty, I'd advise sending it back to Samsung for replacement. The following instructions were pulled off the GSM with credit to user Bsisco. You will need to know how to issue ADB commands and when it's all said and done, you may stop the bootlooping, but you will likely lose your original IMEI and have to write a new certificate which requires a Z3X box or other unlock repair box. KingRoot supplies a temporary root and requires repeating the steps after reboot. Proceed with caution and no guarantees included. Here is his solution:
1. Downgrade to 4.4.4 via Odin. Extract OC4, extract Odin, open Odin, select four files into correct position (BL, AP, CP, CSC) 4.4.4 OC4 Odin 3.09 (Samsung Mobile drivers required)
2. Once on 4.4.4 or below, enable developer options by tapping "build version" several times, enable USB debugging & mock location, and install KingRoot 4.0.0.233 to phone. Caution, newer versions did not work for me.
3. Open "Command Prompt" and type "adb version" should reply with "Android Debug Bridge version x.x.x", if does not, change to the correct directory where adb is installed via "cd" command.
4. These next two steps can be a little tricky as the phone often reboots before completed, must work quickly, I suggest copying the long command, then paste when ready.
5. Connect to working WiFi. Turn off your phone, reboot, or wait for it to reboot itself. Soon as phone turns on, open KingRoot, soon as WiFi connected notification appears, touch button in center of KingRoot app, soon as KingRoot reaches 30%, began adb commands.
6. ADB commands: first command "adb shell", second command "su", third command "dd if=/dev/zero of=/dev/block/mmcblk0p10 | dd if=/dev/zero of=/dev/block/mmcblk0p13 | dd if=/dev/zero of=/dev/block/mmcblk0p14 | dd if=/dev/zero of=/dev/block/mmcblk0p15 | dd if=/dev/zero of=/dev/block/mmcblk0p16" phone will reboot or you can reboot and after reboot boot-loop and unknown baseband will be fixed! Can now write new IMEI via "Write Cert" and possibly "Write QCN" if any network troubles, then all good to go!
Click to expand...
Click to collapse
If you try this fix you will ended up stuck in factory mode just like I did. On the original post someone said that we only have to wipe 3 partitions (this method wipes five .10,13,14,15,16). Since I don't have a box to completely repair my phone I'm gonna have to sell it for parts.
And Why this thread in Development???? It make me exited when I saw new thread in Development section ( thought permanent root came) Gzzzz
# adb shell
[email protected]:/ $ su
=/dev/block/mmcblk0p15 | dd if=/dev/zero of=/dev/block/mmcblk0p16 <
/dev/block/mmcblk0p16: write error: No space left on device
9+0 records in
8+0 records out
4096 bytes transferred in 0.006 secs (682666 bytes/sec)
/dev/block/mmcblk0p14: write error: No space left on device
8193+0 records in
8192+0 records out
4194304 bytes transferred in 0.477 secs (8793090 bytes/sec)
/dev/block/mmcblk0p10: write error: No space left on device
8193+0 records in
8192+0 records out
4194304 bytes transferred in 0.531 secs (7898877 bytes/sec)
/dev/block/mmcblk0p15: write error: No space left on device
8193+0 records in
8192+0 records out
4194304 bytes transferred in 0.547 secs (7667831 bytes/sec)
/dev/block/mmcblk0p13: write error: No space left on device
28673+0 records in
28672+0 records out
14680064 bytes transferred in 0.987 secs (14873418 bytes/sec)
Somehow my device truly hates me. I've been trying to get past a modem crash/ kernel panic with no success.
Hi, I have an Asus Zenfone 2 ZE551ML (Z00ADB) with the ROM/stock version: CN-2.20.40.195 and I want it to be WW instead of CN, since with CN version I can't have Google Services (can't log in into Google so can't use any of their apps). So what I'm trying to do is to flash de WW version, specifically I've tried , both from the official page, but when I0m adb sideloading it I type in the prompt "adb devices" and it recognizes my device, but when I type "adb sideload UL-Z00A-WW-2.20.40.184-user.zip" (and with the 194 version) it says "cannot read UL-Z00A-WW-2.20.40.184-user.zip"
-I'm using Windows 10.
-Phone is not rooted.
-Of course, when I'm typing in the prompt, the phone is in recovery mode, adb from sideload mode.
-zip file is located in the same folder as adb files.
-adb folder contains: adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe and the metioned zip files.
Thanks in advance for your help.
CarlosMD14 said:
Hi, I have an Asus Zenfone 2 ZE551ML (Z00ADB) with the ROM/stock version: CN-2.20.40.195 and I want it to be WW instead of CN, since with CN version I can't have Google Services (can't log in into Google so can't use any of their apps). So what I'm trying to do is to flash de WW version, specifically I've tried , both from the official page, but when I0m adb sideloading it I type in the prompt "adb devices" and it recognizes my device, but when I type "adb sideload UL-Z00A-WW-2.20.40.184-user.zip" (and with the 194 version) it says "cannot read UL-Z00A-WW-2.20.40.184-user.zip"
[...]
Click to expand...
Click to collapse
I have exactly the same problem as you now. In (stock) recovery and it won't read the zip file. Did you find a solution?
aPexalpha said:
I have exactly the same problem as you now. In (stock) recovery and it won't read the zip file. Did you find a solution?
Click to expand...
Click to collapse
Yes, you only have to change the name of the file to CN. I mean, if your software is CN and want to change to WW, just change WW in the name to CN, and the phone itself will recognize it and offer you to update via OTA.
Oh I don't have exactly the same problem. I don't have a Zenfone but a ZTE Axon 7. Also Chinese btw.
And adb keeps saying: cannot read zip file. Whatever I try to do. Using stock recovery in ADB mode. Adb devices recognizes it etc...
So you're saying the naming of the file might be the problem?
I reset my GPad10 to sell, but the new owner can't get past the logon screen. It wants my email and password, I am not giving that away. Is there a way around it? I called AT&T and they suggest I wait 24 hours (I changed my password) and logon, then change the info once inside. Why would I need to do that? I did a factory reset, not any WIndows refresh, it is suppose to be like it came from the factory.
Hi*
V700 USER PLEASE READ !!!!!!
We need an loader image from an working v700 Gpad 10.1 to unbrick" (required:*Root*+ Terminal emulator*App)
in terminal type :
su
(grant*Root)
dd if=/dev/block/mmcblk0 of=/sdcard/loader.img bs=1024 count=168960
Thx in Advance**!!!!
Hi everyone,
While i was doing imei repair, at one step i ran these commands :
dd if=/dev/zero of=/dev/block/mmcblk0p45 ( fsc)
dd if=/dev/zero of=/dev/block/mmcblk0p46 (modemst1)
dd if=/dev/zero of=/dev/block/mmcblk0p47 (modemst2)
I was gonna restore my qcn backup but after rebooted the phone sim got detected but it says no service. I got both my IMEI's and baseband intact. I restored my original QPST backup but didnt work.
I had MIUI 10 Global Stable ROM latest version.
Flashed "miui_HMNote5HMNote5ProGlobal_V9.6.4.0.OEIMIFD_44e6a174cf_8.1.zip" but still no service.