Long story short my G4 Plus started to loop boot after it just turned off, and I do know my LineageOS was kinda messed up for recovering a backup from an old phone on top of it, so now I decided to just wipe everything and flash back to the stock ROM, but the moment I try to flash the stock ROM according to a guide here I get an error on every single file that I try to transfer, and before I tried just flashing a new lineage after a complete wipe of everything, but I believe it wouldn't boot because the bootloader is locked again, don't know why, basically I'd really appreciate some in-depth help while I try and fix it, and I totally forgot the model of my phone, basically I just wanna start from zero again with a stock ROM, first step I guess would be to link me everything I need in case I've done something wrong and I'll start from scratch.
First I'd like to ask for a way to check my exact phone model so I can be sure I'm downloading a proper stock ROM, and yeah I don't have the box and it's a latin american one.
If you can boot to the bootloader, you can get the model info and other information from getvar:
1)Boot your device to the bootloader. Connect your device to a computer with ADB/fastboot installed, use a high quality data cable or the original USB cable to connect.
2)Open an ADB terminal on your computer. Type 'fastboot devices' without quotes into the terminal. Press Enter. If your device is responding, you should see your device's serial code appear.
3)If your device is communicating, then type 'fastboot getvar all' without quotes into the terminal. Press Enter. You should get a list of parameters corresponding to your device. You may wish to post or upload that in a text file here - please omit your IMEI from this upload.
What guide are you following, what stock ROM are you using and what errors are you getting when you flash?
I find it weird that my device doesn't appear when I type the command 'adb devices' but the getvar command does work still, otherwise, here's what came out.
I was using this guide and stock ROM https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
When I tried the OEM flash it didn't work at all, it kept giving me errors as if it couldn't reach the phone I guess, I really can't say what it was exactly but no option worked, even doing it manually like that guide said. I'm not touching the phone at all right now, except for what I just did, deleted system, data, cache everything, also weird thing is I woke up and the phone would initiate, I had previously installed a new lineageOS version when last night it didn't ever initiated, prompted me to backup from google account or start fresh but then it rebooted, tried with SD card in, and it rebooted even faster I guess; that's all I can say.
I'm none to talk, but I'd like to get guided if possible which the proper guides and if I get an error obviously report it, cuz every single time there's a new error I encounter.
Update: Turns out that after I installed a new version of LineageOS I tried to delete system, cache, dalvik, etc all of them again and I got this error in TWRP and I didn't notice
Code:
E:Primary block device '/dev/block/bootdevice/by-name/userdata' for mount point '/data' is not present
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Failed to mount '/cache' (Invalid argument)
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/firmware' (Invalid argument)
Failed to mount '/persist' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
E:
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (Invalid argument)
Failed to wipe dalvik
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/firmware' (Invalid argument)
Failed to mount '/persist' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Failed to wipe dalvik
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/firmware' (Invalid argument)
Failed to mount '/persist' (Invalid argument)
...done
Unable to mount storage
Lineage is still installed and I can boot into it but it quickly reboots like I said before, but now it seems I can't even wipe my device, cool.
Code:
Microsoft Windows [Version 10.0.17134.165]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\adb>adb devices
List of devices attached
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B0.0E(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223NT5FX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: 0919B70100000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 11-04-2016
(bootloader) sku: XT1641
(bootloader) battid: SNN5970A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon May 16 17:55:26 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:6.0.1/M
(bootloader) ro.build.fingerprint[1]: PJ24.139-23.1/1:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.24.1.athene.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.3-02720-8976.0
(bootloader) version-baseband[0]: M8952_70004.04.03.32R ATHENE_LATAM_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gcf01273 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld52) (gcc version 4.9.x-google 20
(bootloader) kernel.version[2]: 140827 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Thu Apr 28 13:04:48 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7
(bootloader) rpm.git: git=1dc910e
(bootloader) tz.git: git=9fa1804
(bootloader) hyp.git: git=9fa1804
(bootloader) keymaster.git: git=9fa1804
(bootloader) cmnlib.git: git=9fa1804
(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retla
all: listed above
finished. total time: 0.094s
@dante0397
Link you gave is old Nougat firmware, while getvar result shows your device has MarshMallow firmware..
I recommend you to download latest from this thread [https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ]
Also your bootloader is still unlocked, you can exclude lock commands to keep it unlocked..
In addition, keep eye on commands, if you are getting OKAY at end of command or what...
Edit: didn't noticed another text about not mounting anything.. it may be because of wrong firmware and also bootloader version is strange [ 0E * ] it looks like you have flashable completely wrong firmware.. try latest and paste cmd screen result if fails..
Thank you, I'll try just that once the ROM downloads, I'll let you know in like 30 min or so, sourceforge is pretty slow.
so yeah it worked, but it reboots at random times, so far longest it has stayed on has been until it asks for my wi-fi to backup my apps from my account, otherwise it is the stock ROM, with the motorola logo and at the beginning telling me the device is unlocked and untrusted, so it's fine, maybe it's a hardware issue, since I've had like 3 family member that had this phone and eventually they had to be repaired cuz they all just rebooted at random times, like mine, could that be the issue?
Related
-Hello. A friend gave me a phone wich he supposed to manipulate. He installed some wierd firmwhare.
Ok. What I want to do is flashing Stock ROM back.
Problem I face. Cannot enter Download Mode. When i press the button combination it drops me a Chinese menu. Even translating this menu (google) it has no Download Mode option.
Model: SM-G935F
-phone NOT rooted (Cannot root it since the method I find implies flashing through Odin. CANNOT ENTER DOWNLOAD MODE).
-USB Debugging Enabled
-Unlocked Bootloader (oem-unlock)
I try: "adb reboot download mode" It reboots into normal mode.
When I try to flash stock recovery.img or TWRP image trough fastboot I get the following message:
C:\Apps\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (45048 KB)...
OKAY [ 1.484s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.500s
(Anything i try to flash, same problem. size too large). And I got the right FW/img's for SM-G935F from sammobile.com
Please someone help me. I don't know what the hell to do.
C:\Apps\platform-tools>fastboot getvar all
(bootloader) max-download-size: 134217728
(bootloader) partition-size:bmtpool: 1500000
(bootloader) partition-type:bmtpool: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: f000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 5dc00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 300000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:sec_ro: 600000
(bootloader) partition-type:sec_ro: ext4
(bootloader) partition-size:recovery: 600000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 600000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:uboot: 60000
(bootloader) partition-type:uboot: raw data
(bootloader) partition-size:seccfg: 20000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizerotect_s: a00000
(bootloader) partition-typerotect_s: ext4
(bootloader) partition-sizerotect_f: a00000
(bootloader) partition-typerotect_f: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizero_info: 300000
(bootloader) partition-typero_info: raw data
(bootloader) partition-size:ebr1: 80000
(bootloader) partition-type:ebr1: raw data
(bootloader) partition-size:mbr: 80000
(bootloader) partition-type:mbr: raw data
(bootloader) partition-sizereloader: 1400000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: AEON6582_WT_L
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.297s
This is very likely fake chinese S7.
ed1337 said:
(bootloader) product: AEON6582_WT_L
Click to expand...
Click to collapse
Look like a Mediatek mt6582 soc phone which definitely not S7.
Sent from my SM-G935F using Tapatalk
S7 edge doesn't even have fastboot lol
---------- Post added at 01:04 AM ---------- Previous post was at 01:03 AM ----------
After searching this model name, it's probably mediatek Galaxy J5. Check their forums.
After update about 6 months ago I got errors on my Nexus 10. It was stuck in the boot animation thing.
Booting to the recovery menu and trying things like, clear cache, etc gives the failed to mount cache errors eg:
E:failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_kmsg
E: Can't open /cache/recovery/last_kmsg
But it seems without cache, and since it is oem locked I am caught in catch-22.
Since to do oem unlock, or sideload, or recovery menu options, they all hang - I suspect because it is trying to put some file in cache directory.
For fastboot oem unlock
I can connect to it via fastboot, and try
fastboot oem unlock
which brings up the Yes/No screen on the Nexus 10, I can navigate with the volume, select Yes or No, but if I select Yes, it hangs - I suspect it is hanging doing the user wipe (although I've done that a heap anyway). Need to restart it <pwr> <vol+> <vol-> to get back to boot menu.
<screenshot coming - need to wait 10hrs>
h t t p s :/ /drive.google.com/open?id=0B6cJseueu7P6enNpbFR5cFFXN1BNbjg3UWVkMDNvb0ZhNV9B
Clearly the Power button works, since I used it to navigate to this screen, and others, and works when I press No - so pressing Yes hangs for some other reason.
For sideload
when I select recover menu "load update from adb" then run
C:\...\platform-tools>adb sideload mantaray-lmy49j-factory-b24f40e6.zip
It gives details of loading on the tablet screen, along with errors about mounting /cache and then goes back to the recovery menu.
Erase userdata & cache seem to work
C:\...\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata' OKAY [ 3.025s]
Finished. Total time: 3.034s
C:\...\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 3.018s]
Finished. Total time: 3.049s
But formatting them requires unlock
C:\Users\odoma04\AppData\Local\Android\Sdk\platform-tools>fastboot format:ext4 cache
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 135168 4k blocks and 33840 inodes
Filesystem UUID: 83b1b5c6-1224-11e9-aa85-856a55f9d0b8
Superblock backups stored on blocks:
32768, 98304
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'cache' (200 KB) OKAY [ 0.032s]
Writing 'cache' FAILED (remote: 'Locked - Use "fastboot oem unlock" to Unlock')
Finished. Total time: 0.119s
Nexus Settings
C:\...\platform-tools>fastboot getvar all
(bootloader) variant: wifi-only
(bootloader) serialno: R32XXXX
(bootloader) version-hardware: 8
(bootloader) version-bootloader: MANTAMF01
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) off-mode-charge: enabled(1)
(bootloader) signing: yes
(bootloader) boot partition- type: raw, size: 0x0000000001000000
(bootloader) recovery partition- type: raw, size: 0x0000000001ff0000
(bootloader) metadata partition- type: raw, size: 0x0000000000010000
(bootloader) misc partition- type: raw, size: 0x0000000000400000
(bootloader) cache partition- type: ext4, size: 0x0000000021000000
(bootloader) system partition- type: ext4, size: 0x0000000032000000
(bootloader) userdata partition- type: ext4, size: 0x0000000352c00000
all:
Finished. Total time: 0.033s
So I suspect if I had : (bootloader) unlocked: yes
I would be ok, without it I don't have any options to reset the cache or the device.
Questions :
a) so what is the invalid parameter on the mount command ?
(mount is pretty simple, on unix, the partition seems to be ext4, so is it possible my mount table had ext2 or something since it was older version ? )
b) any way to run adb when the system doesn't come up, so can at least go have a look at the system files with shell etc ?
c) any way to check the memory - maybe I have a mem chip failure ?
And of course any other ideas welcome, hate to junk something that worked well & seems to have got caught with just some update (or out of memory issue ) going wrong.
Thanks in advance.
Cheers - Mark
Hi everyone,
First sorry for my English, I'm Vietnamese. I bought fire hd 8 6th used for a cheap price, I want to flash new rom via sideload becase i didn't find any topic about flashtool for fire hd tablet, so i decided to sideload it but unfortunately sideload processing to 47% and fail all of time, so i did some research and know that method only working on non modification devices, and my tablet already unlocked bootloader.. maybe, i knew it by using fastboot getvar unlocked and it say Yes. I thought with unblocked bootloader might be able to flash custom recovery to install a new rom, i tried and the results is writing recovery done but when device boot to recovery mode by holding power + volume down button nothing appear still remain blackscreen with recovery mode text from bottom left and with the bonus thing is Stock recovery is gone. Just for my stupid action, its bricked with only fastboot mode is accessible
I'm sorry for taking to long. Please let me know if you have any advice and stock recovery please share me
Thank you so much!
Issue solved thanks for k4y0z. Here is the recovery image file
https://forum.xda-developers.com/showpost.php?p=79663247&postcount=21
and the instruction for create recovery
https://forum.xda-developers.com/showpost.php?p=79656602&postcount=10
vnhatduy2010 said:
Hi everyone,
First sorry for my English, I'm Vietnamese. I bought fire hd 8 6th used for a cheap price, I want to flash new rom via sideload becase i didn't find any topic about flashtool for fire hd tablet, so i decided to sideload it but unfortunately sideload processing to 47% and fail all of time, so i did some research and know that method only working on non modification devices, and my tablet already unlocked bootloader.. maybe, i knew it by using fastboot getvar unlocked and it say Yes. I thought with unblocked bootloader might be able to flash custom recovery to install a new rom, i tried and the results is writing recovery done but when device boot to recovery mode by holding power + volume down button nothing appear still remain blackscreen with recovery mode text from bottom left and with the bonus thing is Stock recovery is gone. Just for my stupid action, its bricked with only fastboot mode is accessible
I'm sorry for taking to long. Please let me know if you have any advice and stock recovery please share me
Thank you so much!
Click to expand...
Click to collapse
Impossible that you have unlocked BL. Can you post the output of fastboot getvar all?
Thanks!
Rortiz2 said:
Impossible that you have unlocked BL. Can you post the output of fastboot getvar all?
Thanks!
Click to expand...
Click to collapse
Hi sorry for late reply
this is the output of getvar all
C:\Users\1\Desktop\fire7\ADB FASTBOOT FILES WINDOWS>fastboot devices
G000L40360860685 fastboot
C:\Users\1\Desktop\fire7\ADB FASTBOOT FILES WINDOWS>fastboot getvar all
(bootloader) secure: yes
(bootloader) prod: 0
(bootloader) unlock_status: false
(bootloader) unlock_code: 0x2a2097d9656b4eed
(bootloader) serialno: G000L40360860685
(bootloader) max-download-size: 0x6d00000
(bootloader) partition-size:userdata: 69d6fbe00
(bootloader) partition-type:userdata: ext4
(bootloader) partition-sizeMT: 438000
(bootloader) partition-typeMT: ext4
(bootloader) partition-sizeersisbackup: 1000000
(bootloader) partition-typeersisbackup: ext4
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: ext4
(bootloader) partition-size:dfs: 20000000
(bootloader) partition-type:dfs: ext4
(bootloader) partition-size:dkernel: 1000000
(bootloader) partition-type:dkernel: ext4
(bootloader) partition-size:cache: 1a800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 64e48000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:dkb: 100000
(bootloader) partition-type:dkb: raw data
(bootloader) partition-size:kb: 100000
(bootloader) partition-type:kb: raw data
(bootloader) partition-size:metadata: 2760000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: fe3000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 7d000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: GIZA
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
(bootloader) partition-size:userdata: 69d6fbe00
(bootloader) partition-type:userdata: ext4
(bootloader) partition-sizeMT: 438000
(bootloader) partition-typeMT: ext4
(bootloader) partition-sizeersisbackup: 1000000
(bootloader) partition-typeersisbackup: ext4
(bootloader) partition-size:MISC: 80000
(bootloader) partition-type:MISC: ext4
(bootloader) partition-size:dfs: 20000000
(bootloader) partition-type:dfs: ext4
(bootloader) partition-size:dkernel: 1000000
(bootloader) partition-type:dkernel: ext4
(bootloader) partition-size:cache: 1a800000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 64e48000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:dkb: 100000
(bootloader) partition-type:dkb: raw data
(bootloader) partition-size:kb: 100000
(bootloader) partition-type:kb: raw data
(bootloader) partition-size:metadata: 2760000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: fe3000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:lk: 7d000
(bootloader) partition-type:lk: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
all: Done!!
finished. total time: 0.207s
C:\Users\1\Desktop\fire7\ADB FASTBOOT FILES WINDOWS>
Click to expand...
Click to collapse
Thank you
vnhatduy2010 said:
Hi sorry for late reply
this is the output of getvar all
Code:
(bootloader) secure: yes
(bootloader) prod: 0
(bootloader) unlock_status: false
(bootloader) unlocked: yes
(bootloader) secure: no
Thank you
Click to expand...
Click to collapse
What?
You can create the recovery from the boot-image using the install-recovery.sh script.
If you have unmodified boot and system it should happen automatically on boot.
Otherwise you can modify the script to read boot.img from a file.
What?
You can create the recovery from the boot-image using the install-recovery.sh script.
If you have unmodified boot and system it should happen automatically on boot.
Otherwise you can modify the script to read boot.img from a file.
Click to expand...
Click to collapse
Hi that mean my device not unlocked yet?
I'm just google to find the firmware extractor tool, I manage to extract it and found recovery-from-boot.p file & install-recovery.sh inside /bin
I don't want to bother you but please I don't know what to do next to create recovery from sh file, the internet said that need using Linux OS but I don't know how to modify the script.
I will dualboot Ubuntu if necessary. Can you give me instruction?
Thanks~
vnhatduy2010 said:
Hi I'm just google to find the firmware extractor tool, I manage to extract it and found recovery-from-boot.p file & install-recovery.sh inside /bin
I don't want to bother you but please I don't know what to do next to create recovery from sh file, the internet said that need using Linux OS but I don't know how to modify the script.
I will dualboot Ubuntu if necessary. Can you give me instruction?
Thanks~
Click to expand...
Click to collapse
Post the contents of the script here please.
The firmware-bin is just a ZIP-file, no special tools needed to extract it.
vnhatduy2010 said:
Hi that mean my device not unlocked yet?
I'm just google to find the firmware extractor tool, I manage to extract it and found recovery-from-boot.p file & install-recovery.sh inside /bin
I don't want to bother you but please I don't know what to do next to create recovery from sh file, the internet said that need using Linux OS but I don't know how to modify the script.
I will dualboot Ubuntu if necessary. Can you give me instruction?
Thanks~
Click to expand...
Click to collapse
Are you sure that is the Fire HD8 2016? Nvm, yes it's 2016: GIZA.
How did you unlocked the BL?
k4y0z said:
Post the contents of the script here please.
The firmware-bin is just a ZIP-file, no special tools needed to extract it.
Click to expand...
Click to collapse
yes I extracted with Winrar but after that I stuck with img file and windows can't open that file type.
btw here is the scritpt
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:9218048:a1aff37711937c43c8bd4396803fb254a35db53a; then
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:8607744:05901192d8e64b20a9eabbddbf8b92b1ec0ca492 EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery a1aff37711937c43c8bd4396803fb254a35db53a 9218048 05901192d8e64b20a9eabbddbf8b92b1ec0ca492:/system/recovery-from-boot.p && echo "
Installing new recovery image: succeeded
" >> /cache/recovery/log || echo "
Installing new recovery image: failed
" >> /cache/recovery/log
else
log -t recovery "Recovery image already installed"
fi
Rortiz2 said:
Are you sure that is the Fire HD8 2016? Nvm, yes it's 2016: GIZA.
How did you unlocked the BL?
Click to expand...
Click to collapse
I don't know this is the used device maybe the old owner unlocked it, I'm not sure about it maybe my wrong,
did you noticed anything from my getvar output?
vnhatduy2010 said:
yes I extracted with Winrar but after that I stuck with img file and windows can't open that file type.
btw here is the scritpt
Code:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:9218048:a1aff37711937c43c8bd4396803fb254a35db53a; then
applypatch -b /system/etc/recovery-resource.dat EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:8607744:05901192d8e64b20a9eabbddbf8b92b1ec0ca492 EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery a1aff37711937c43c8bd4396803fb254a35db53a 9218048 05901192d8e64b20a9eabbddbf8b92b1ec0ca492:/system/recovery-from-boot.p && echo "
Installing new recovery image: succeeded
" >> /cache/recovery/log || echo "
Installing new recovery image: failed
" >> /cache/recovery/log
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
OK, make sure the firmware you have extracted is the same version you have installed.
Then copy the boot.img from the firmware to /sdcard
Code:
adb push boot.img /sdcard/
Then go into adb shell and run the following command
Code:
applypatch -b /system/etc/recovery-resource.dat /sdcard/boot.img /sdcard/recovery.img a1aff37711937c43c8bd4396803fb254a35db53a 9218048 05901192d8e64b20a9eabbddbf8b92b1ec0ca492:/system/recovery-from-boot.p
It should create /sdcard/recovery.img
You can pull it
Code:
adb pull /sdcard/recovey.img
If it isn't the same version you have installed (or the files have been modified to prevent recovery from being overwritten), you will have to extract the files
Code:
/system/etc/recovery-resource.dat
/system/recovery-from-boot.p
and place them on the device as well.
Thanks k4y0z but like i said on first post when i boot into recovery mode by holding power + volume down, nothing come up only the blackscreen with recovery mode text and my pc only regconize fastboot mode but recovery mode pc regconize as MTP device and no devices attached in cmd even i'm trying to reinstall driver and try on different pc, that mean i can't use adb command.
it's no hope:crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
vnhatduy2010 said:
Thanks k4y0z but like i said on first post when i boot into recovery mode by holding power + volume down, nothing come up only the blackscreen with recovery mode text and my pc only regconize fastboot mode but recovery mode pc regconize as MTP device and no devices attached in cmd even i'm trying to reinstall driver and try on different pc, that mean i can't use adb command.
it's no hope:crying:
Click to expand...
Click to collapse
Yes it's likely your recovery is broken.
You will have to flash the recovery produced by the scripts.
Make sure you are using the correct versions of all the files.
k4y0z said:
Yes it's likely your recovery is broken.
You will have to flash the recovery produced by the scripts.
Make sure you are using the correct versions of all the files.
Click to expand...
Click to collapse
Why he has the BL unlocked if it is a HD8 2016? Did you ported the exploit to that device?
Rortiz2 said:
Why he has the BL unlocked if it is a HD8 2016? Did you ported the exploit to that device?
Click to expand...
Click to collapse
No, I don't own that device. I don't think it really is unlocked, but the getvar output seems to be self-contradicting, as I noted above:
(bootloader) secure: yes
(bootloader) prod: 0
(bootloader) unlock_status: false
(bootloader) unlocked: yes
(bootloader) secure: no
Click to expand...
Click to collapse
k4y0z said:
Yes it's likely your recovery is broken.
You will have to flash the recovery produced by the scripts.
Make sure you are using the correct versions of all the files.
Click to expand...
Click to collapse
you right recovery completely broken, i tried to figure out but still don't know how to flash recovery produce by the script can we flash recovery.img file from the other kindle fire tablet like Hd 7 or Hd 8 older gen?
k4y0z said:
No, I don't own that device. I don't think it really is unlocked, but the getvar output seems to be self-contradicting, as I noted above:
Click to expand...
Click to collapse
Amazing. Never saw that...
So he can flash the recovery tought fastboot right?
Rortiz2 said:
Amazing. Never saw that...
So he can flash the recovery tought fastboot right?
Click to expand...
Click to collapse
I hope so, if can be flash recovery it will great
Rortiz2 said:
Amazing. Never saw that...
So he can flash the recovery tought fastboot right?
Click to expand...
Click to collapse
vnhatduy2010 said:
I hope so, if can be flash recovery it will great
Click to expand...
Click to collapse
According to the OP, you said, that fastboot flash was working.
Another option would be to flash from a rooted system.
k4y0z said:
According to the OP, you said, that fastboot flash was working.
Another option would be to flash from a rooted system.
Click to expand...
Click to collapse
yeah, fastboot still working fine but recovery is broken so i can't access and using adb command just only fastboot command, fastboot flash recovery command working but when i reboot to recovery nothing come up, maybe recovery image not compatible with hd 8 6th gen
vnhatduy2010 said:
yeah, fastboot still working fine but recovery is broken so i can't access and using adb command just only fastboot command, fastboot flash recovery command working but when i reboot to recovery nothing come up, maybe recovery image not compatible with hd 8 6th gen
Click to expand...
Click to collapse
Well, what recovery are you flashing?
It needs to be for GIZA.
I have given you instructions how to create a proper recovery-image.
What firmware-version do you have installed?
Hello,
So my U Ultra was rooted, then unrooted.
Months later, the phone has some sort of software issue causing it to restart (probably a corrupt file)
Now i want to take it back to being a fully unrooted stock.
Please see details below
Fastboot getvar all:
kernel: lk
(bootloader) product: htc_ocedugl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: FA72F1700260
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 355167081167528
(bootloader) version-main: 2.19.400.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF20000
(bootloader) cid: HTC__060
The bootloader shows following info:
*** RELOCKED ***
*** FUSED (PRODUCTION)***
htc_ocedugl PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v24.0.8996.00007_1206_OCE
OS-2.19.400.1
Feb 13 2018,16:29:19(1026541)
It's an Indian region phone i think, since the ota files i find online with the matching radio reads HTC INDIA
So i've tried the sdcard method as well as fastboot flash zip method, trying with 2 different files:
OTA_OCEAN_N[email protected]80211.2_63.34_release_522885kzkqxuugr4zk0yr5.zip
link: https://androidfilehost.com/?fid=746010030569965797
&
2PZFIMG_OCEAN_NOTE[email protected]70502_53.34_release_503372_signed_2_4.[email protected]
link: https://androidfilehost.com/?fid=3700668719832236174
Yes, i renamed it to "2PZFIMG.zip" and placed it on root of the sdcard,
for the OTA file mentioned above, i end up with the following error:
"99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0
99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0
99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0"
For the 2nd zip, I receive the following error:
"19 RU_MAIN_VER_FAIL os-version in android-info missing or i
19 RU_MAIN_VER_FAIL os-version in android-info missing or i
FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i"
fastboot flash zip concludes with the following error:
"zeeraks-mbp-2:~ zeerakata$ /Users/zeerakata/Documents/android/platform-tools/fastboot flash zip /Users/zeerakata/Documents/android/platform-tools/rom.zip
ERROR: Couldn't create a device interface iterator: (e00002bd)
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 904116903 is not a multiple of the block size 4096
Sending sparse 'zip' 1/2 (1048572 KB) error: write_sparse_skip_chunk: don't care size 904116903 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 904116903 is not a multiple of the block size 4096
OKAY [ 52.655s]
Writing 'zip' (bootloader) HOSD CL#1026541
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_b
(bootloader) xkQ1e
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: '22 RU_HEADER_ERROR ')
fastboot: error: Command failed"
I'm not a pro at this, but i've been playing around with android rooting and stuff for a while now.
Please help me with this.
Need to go back to stock
UPDATE:
So i downloaded a file with the following title,
2PZFIMG_OCEAN_NOTE_DU[email protected]80211.2_63.34_release_524957_combined_s
and it is successfully flashed via SDcard method:
I still am stuck on a bootloop, i cant make it past the htc logo, onto the loading screen
PLEASE HELP
Found the right RUU
The OTA file mentioned wouldnt flash, so i found an RUU of the same variant.
https://androidfilehost.com/?fid=11410963190603866517
It did the job, but seems like this wasn't it for my phone. Seems like a hardware issue to me since it would randomly freeze, even followed by a long-timed vibration till it turned off. So i'll be taking it for repair to a shop.
Hello I've messed up every partition I had in my MOTO G5 PLUS (potter) with fastboot. I can get to install twrp, but whenever I try to do anything it fails to mount.
This is what TWRP says when I wipe anything:
Could not mount /data and unable to find crypto footer
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder
Failed to mount '/cache' (No such device)}
Updating partitio ndetails...
Failed to mount '/data' (Invalid Argument)
Failed to mount '/cache' (No such device)
...done
Unable to mount storage
Failed to mount '/data' (Invalid Argument)
FULL SELinu Support is Present
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (Invalid Argument)
E: Unable to wipe '/cache' -- unknown file system 'auto'
Updating partition details...
Failed to mount '/data' (Invalid Argument)
Failed to mount '/cache' (No such device)
...done
Unable to mount storage
Click to expand...
Click to collapse
and whenever I boot into system it says NO COMMAND.
Anyone knows any workaround?
Thanks
Up. Should I just buy a new phone?
crata said:
Hello I've messed up every partition I had in my MOTO G5 PLUS (potter) with fastboot. I can get to install twrp, but whenever I try to do anything it fails to mount.
This is what TWRP says when I wipe anything:
and whenever I boot into system it says NO COMMAND.
Anyone knows any workaround?
Thanks
Click to expand...
Click to collapse
You should flash the stock firmware to get the partitions fixed.
Here is the procedure to flash.
https://forum.xda-developers.com/g5...-flash-stock-romfactory-t3691396/post74221633
crata said:
Hello I've messed up every partition I had in my MOTO G5 PLUS (potter) with fastboot. I can get to install twrp, but whenever I try to do anything it fails to mount.
This is what TWRP says when I wipe anything:
and whenever I boot into system it says NO COMMAND.
Anyone knows any workaround?
Thanks
Click to expand...
Click to collapse
Or here a bit more actual tutorial:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
if you can find someone with the same model of phones as your phone, you may be able to recover it using a "blankflash" made from a working same model. The blankflash is to recreate partitions, and then you fastboot stock ROM.
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-oreo-hard-brick-t3874458
I cant help, I have XT1687.
Nivead said:
if you can find someone with the same model of phones as your phone, you may be able to recover it using a "blankflash" made from a working same model. The blankflash is to recreate partitions, and then you fastboot stock ROM.
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-oreo-hard-brick-t3874458
I cant help, I have XT1687.
Click to expand...
Click to collapse
Are you taking about mmcblk0 file, method to recover the device?
riyan65 said:
Are you taking about mmcblk0 file, method to recover the device?
Click to expand...
Click to collapse
yes.
you can look at your partitions via fastboot
C:\ADB>fastboot oem partition
...
(bootloader) sbl1: offset=128KB, size=512KB
(bootloader) rpm: offset=640KB, size=256KB
(bootloader) tz: offset=1152KB, size=1792KB
(bootloader) devcfg: offset=3200KB, size=64KB
(bootloader) aboot: offset=3456KB, size=1536KB
(bootloader) cmnlib: offset=4992KB, size=256KB
(bootloader) cmnlib64: offset=5248KB, size=256KB
(bootloader) keymaster: offset=5504KB, size=256KB
(bootloader) prov: offset=5760KB, size=192KB
(bootloader) sbl1bak: offset=6016KB, size=512KB
(bootloader) rpmbak: offset=6528KB, size=256KB
(bootloader) tzbak: offset=7040KB, size=1792KB
(bootloader) devcfgbak: offset=9088KB, size=64KB
(bootloader) abootbak: offset=9344KB, size=1536KB
(bootloader) cmnlibbak: offset=10880KB, size=256KB
(bootloader) cmnlib64bak: offset=11136KB, size=256KB
(bootloader) keymasterbak: offset=11392KB, size=256KB
(bootloader) provbak: offset=11648KB, size=192KB
(bootloader) modem: offset=11904KB, size=102400KB
(bootloader) fsc: offset=114304KB, size=1KB
(bootloader) ssd: offset=114305KB, size=8KB
(bootloader) dsp: offset=114313KB, size=16384KB
(bootloader) DDR: offset=130816KB, size=32KB
(bootloader) sec: offset=130848KB, size=16KB
(bootloader) utags: offset=130944KB, size=512KB
(bootloader) utagsBackup: offset=131456KB, size=512KB
(bootloader) modemst1: offset=131968KB, size=2048KB
(bootloader) modemst2: offset=134016KB, size=2048KB
(bootloader) fsg: offset=136064KB, size=8192KB
(bootloader) persist: offset=144256KB, size=32768KB
(bootloader) frp: offset=177024KB, size=512KB
(bootloader) cid: offset=177536KB, size=128KB
(bootloader) logo: offset=177664KB, size=16384KB
(bootloader) carrier: offset=194048KB, size=16384KB
(bootloader) metadata: offset=210432KB, size=512KB
(bootloader) kpan: offset=210944KB, size=8192KB
(bootloader) boot: offset=219136KB, size=16384KB
(bootloader) recovery: offset=235520KB, size=20580KB
(bootloader) misc: offset=256128KB, size=1024KB
(bootloader) limits: offset=257152KB, size=32KB
(bootloader) mota: offset=257280KB, size=512KB
(bootloader) dip: offset=257792KB, size=1024KB
(bootloader) syscfg: offset=258816KB, size=512KB
(bootloader) logs: offset=259328KB, size=2048KB
(bootloader) apdp: offset=261376KB, size=256KB
(bootloader) msadp: offset=261632KB, size=256KB
(bootloader) dpo: offset=261888KB, size=8KB
(bootloader) padA: offset=262016KB, size=128KB
(bootloader) sp: offset=262144KB, size=8192KB
(bootloader) hw: offset=270336KB, size=8192KB
(bootloader) oem: offset=278528KB, size=671744KB
(bootloader) cache: offset=950272KB, size=262144KB
(bootloader) system: offset=1212416KB, size=3538944KB
(bootloader) userdata: offset=4751360KB, size=56319983KB
OKAY [ 0.312s]
finished. total time: 0.328s
This is from one of my XT1687 - I'm sure there will be similarities, but also differences between your model and mine. Might look and see if a partition ended up too big, or maybe zero... just an idea.
If you could find somebody with the same phone ... you could fastboot their partitions and see a difference. Or if you buy another phone, hang onto this inoperative phone and continue to hack away on it.
I just have the same problems, is there any update on this ?