Hi guys!
So I was flashing my mums moto g (xt1032) for the first time in ages. I was upgrading from 4.1 (i think) to 6.0 (http://forum.xda-developers.com/moto-g/development/caf-aosp-aosparadox-project-1-0-t3135626). After all this happened I have realised the xt1032 is not the falcon and I wonder if this is what caused all my problems...?
Anyway, to the problem at hand. After trying to flash, it told me my bootloader was incompatible so I upgraded it to 41.18, flashed the rom again and it went fine. Then I restarted to boot into the rom but it put me into the bootloader. It comes up with "Fastboot Reason: Fall-through from normal boot mode". Now something else that is weird...I can move down the bootloader options with the down key but when I press "up" to select it just flashes the motorola boot screen for a split second (was the "your bootloader is unlocked" screen but I have flashed another boot logo since). This happens when I try to select any option [EDIT 1] I should note that I have a feeling this may have been the case for a while and not related to me flashing the rom or bootloader before - but I can't say for certain. I have tried using mfastboot to flash stock, specifically - ASIA-DS_4.4.4_KXB21.14-L1.40_34_cid7_CFC_1FF which ran mostly successfully but failed to flash the motoboot.img (guessing it can't downgrade the bootloader). This didn't make any difference to the operation of the phone. Now I'm currently downloading the BRASIL_XT1032_5.0.2 stock rom but it is taking forever, really bad host.
Also, I can flash a recovery image but when I try to boot it with "fastboot boot recovery.img" it starts doing it but then shows me an error - something about "remote failed".
[EDIT 1] I have noticed that it does allow me to select the option "barcodes" to show imei information. But for any other option it just says "Boot up failed".
Anyone got any ideas? Been out of the phone flashing biz for too long, it's my mums phone and I'm supposed to be doing my dissertation so any help would be greatly appreciated!
[EDIT 2]
C:\android-sdk\platform-tools>mfastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 4118
(bootloader) product: peregrine
(bootloader) secure: yes
(bootloader) hwrev: 0x82D0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: TA47XXXXXXXX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x41
(bootloader) uid: 9D00EB0315000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 22 16:54:20 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/peregrine_reteu/peregrine
(bootloader) ro.build.fingerprint[1]: :4.4.4/KXB21.14-L1.46/42:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.1.46.peregrine_re
(bootloader) ro.build.version.full[1]: teu.reteuall.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g26ca2df ([email protected]
(bootloader) kernel.version[1]: ilclbld26) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue May 27 02:43:50 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.18-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.18-0-g5742832
(bootloader) rpm.git: git=MBM-NG-V41.18-0-gcecd6e9
(bootloader) tz.git: git=MBM-NG-V41.18-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.18-0-g99084d5
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: retgb
all: listed above
finished. total time: 0.093s
DoNiMaToR said:
So I was flashing my mums moto g (xt1032) for the first time in ages. [...] After all this happened I have realised the xt1032 is not the falcon and I wonder if this is what caused all my problems...?
...
(bootloader) product: peregrine
Click to expand...
Click to collapse
XT1032 is a falcon, XT1039/40/45 is peregrine. You are trying to install stuff for the wrong device, which is generally a bad idea.
Yep was a silly mistake by me! I'd assumed it was an XT1032 for some reason that I cannot remember, it's actually the XT1039 - flashed it with the correct ROM now. Thanks for your help
All working as normal now. For anyone with similar issues, get the IMEI number from the bootloader and check exactly what model you have using this - IMEI info checker.
Hi all,
I've just got given a Chinese Hisense phone. I'd like to root the phone and install a custom ROM. Problem is, I can't find too much info on this device. On the package, it shows as a "Hisense F25M".
Navigating through the device, it shows as Model Number HLTE100M.
Hopefully someone on here can direct me to the right rooting and ROM.
Many thanks,
Arj
Hi all,
I have a Hisense A2M (Hisense A2 Pro) running Vision 5 Android 7.1.2
with Hardware V1.00 Software L1414.6.01.02.00 Kernel 3.18.31 and
I cannot unlock the bootloader and thus I cannot root it.
fastboot does not accept the command "oem unlock".
These are all available fastboot variables:
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4125000
(bootloader) variant:QRD eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xd295faa00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x100000000
(bootloader) serialno:35601126
(bootloader) kernel:lk
(bootloader) product:A2M
all:
finished. total time: 0.213s
Hints are highly appreciated.
Many thanks, Siegfried
Hi,
There are software versions on the Chinese forum fans"dot"hisense"dot"com , e.g. thread-132062-1-3.html which I could not manage to download.
Any idea how to get an international software version for that phone?
Thanks, Siegfried
Hi i flashed lineage OS 16 to my u11 , problem is now i want to sim unlock it i believe i need to revert back to stock. Ive been trying lots that appear to match but to no avail. Can I sim unlock without going back toorig firmware if not can some point in the direction of a rom , posted getvar below
C:\>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) serialno: HT75K1800461
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 356124080054164
(bootloader) version-main: 2.33.91.7
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711161638
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: EVE__001
all:
finished. total time: 0.009s
C:\>
CorinOB said:
Hi i flashed lineage OS 16 to my u11..........
Click to expand...
Click to collapse
I don't have this device myself but, you should be able to obtain some member guidance within one of the following threads that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=2411840
https://forum.xda-developers.com/showthread.php?t=3619042
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Asking for 2.33.91.7 EE UK rom
did u find it i need it
Is it me or the website is not allowing people to unlock their bootloader, did anybody experience this issue yet if you did please comment below let me know your thoughts.
I got Verizon I try to unlock it yesterday the bootloader it still says code fail so their isn't no Verizon unlocking on this phone.
Sent from my moto g stylus using Tapatalk
I've tried repeatedly phone was released but as of this post I'm still unable to unlock bootloader.
I got mine unlocked yesterday with no problem
i get remote unlock error please help full getvar
Microsoft Windows [Version 10.0.19041.264]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) product: sofiap
(bootloader) board: sofiap
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 128GB SAMSUNG DV6DMB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 06 10 12
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZF6523J4FN
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid:
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-06-2020
(bootloader) sku: XT2043-4
(bootloader) carrier_sku: XT2043-4
(bootloader) battid: SB18C71380
(bootloader) battery-voltage: 3793
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/sofiap_t/sofiap:10/QPR30.
(bootloader) ro.build.fingerprint[1]: 80-64/777253:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_10.11.03.22R SOFIAP_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Sat Feb 22 04:
(bootloader) kernel.version[3]: 41:00 CST 2020
(bootloader) git:xbl: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:xbl_config: MBM-3.0-sofiap_t-37f1d83-200222
(bootloader) git:rpm: MBM-3.0-sofiap_t-ffcccb0-200222
(bootloader) git:tz: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:hyp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:devcfg: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:cmnlib64: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:keymaster: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) gitrov: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) git:abl: MBM-3.0-sofiap_t-20deb5d-200222
(bootloader) git:qupfw: MBM-3.0-sofiap_t-f848623-200222
(bootloader) git:uefisecapp: MBM-3.0-sofiap_t-92c2c9f-200222
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C69985
all: listed above
finished. total time: 0.312s
jcastro889 said:
I got mine unlocked yesterday with no problem
Click to expand...
Click to collapse
Show and prove photos
Sent from my moto g stylus using Tapatalk
Been knew that go ahead to the Motorola website
Sent from my moto g stylus using Tapatalk
Yep, unlocked mine on 5/6/2020.
Tried to unlock one a few days ago but it wouldn't work. I will try again today
Mine unlocked fine. Did it a few days ago
The new update came out and they gave me a dumb code that isn't working good enough
Sent from my moto g stylus using Tapatalk
I got mine unlocked it's the XT2043-5 sku
god_of_wisdom said:
The new update came out and they gave me a dumb code that isn't working good enough
Sent from my moto g stylus using Tapatalk
Click to expand...
Click to collapse
You said you got one from Verizon? More than likely it is not unlockable....
Don't get discouraged yet. You gotta think outside of the box. I had a Verizon variant Google Pixel and updated it before learning about depixel8.
Shortly there was a bounty out for the Google Pixel. Soon there was someone who found out how to break it greyed out unlocked bootloader on the Google Pixel.
What I'm trying to say is that it's not impossible to get it done if you have the right mindset, but I'd caution you from buying from Verizon. It's a respectable company, however they make their bootloaders hard to crack.
ShadowWeasel said:
You said you got one from Verizon? More than likely it is not unlockable....
Don't get discouraged yet. You gotta think outside of the box. I had a Verizon variant Google Pixel and updated it before learning about depixel8.
Shortly there was a bounty out for the Google Pixel. Soon there was someone who found out how to break it greyed out unlocked bootloader on the Google Pixel.
What I'm trying to say is that it's not impossible to get it done if you have the right mindset, but I'd caution you from buying from Verizon. It's a respectable company, however they make their bootloaders hard to crack.
Click to expand...
Click to collapse
My oem isn't grey out that's the strange part when I got the code it was a dumb code AAAAAAAAAAAAAAAAAAAA i was like wtf I thought be a code that be easy but this code hell no
Sent from my moto g stylus using Tapatalk
god_of_wisdom said:
My oem isn't grey out that's the strange part when I got the code it was a dumb code AAAAAAAAAAAAAAAAAAAA i was like wtf I thought be a code that be easy but this code hell no
Sent from my moto g stylus using Tapatalk
Click to expand...
Click to collapse
Yeah, that is a dummy code. It makes me wonder, though. Is all bootloader keys the same or unique? Many if not all says unique....
you could try mine which is 4JXK6WCCVJTD5VXEKFGV
If it works, then good. If not, I feel for you.
I had mine unlocked for 1 day and still looking how to root the thing. Many say patch the boot.img for magisk, but I cant find it...
U download the stock rom and u find the boot.img from there I will post the root method
Sent from my moto g stylus using Tapatalk
god_of_wisdom said:
U download the stock rom and u find the boot.img from there I will post the root method
Click to expand...
Click to collapse
it's been a while since I rooted a phone but what does everyone use these days to check if bootloader is unlocked
god_of_wisdom said:
U download the stock rom and u find the boot.img from there I will post the root method
Sent from my moto g stylus using Tapatalk
Click to expand...
Click to collapse
yeah, i was fatigued when i sent that last message. anyways i digress....
attempted root. failed miserably....
what happened is the same as a few others on another thread. touchscreen unresponsive. also shows no service and 0% battery.
good thing i backed up everything and downloaded the stock rom.
anyways has anyone had a successful root?
ShadowWeasel said:
yeah, i was fatigued when i sent that last message. anyways i digress....
attempted root. failed miserably....
what happened is the same as a few others on another thread. touchscreen unresponsive. also shows no service and 0% battery.
good thing i backed up everything and downloaded the stock rom.
anyways has anyone had a successful root?
Click to expand...
Click to collapse
I didn't have any problems rooting. Downloaded the stock rom with the Lenovo Rescue & Smart Assist software on my PC. Copied the boot.img to the phone & patched it with Magisk 20.4 / Magisk Manager 7.5.1. Copied the patched boot image back to my PC & flashed it via fastboot.
dafunk60 said:
I didn't have any problems rooting. Downloaded the stock rom with the Lenovo Rescue & Smart Assist software on my PC. Copied the boot.img to the phone & patched it with Magisk 20.4 / Magisk Manager 7.5.1. Copied the patched boot image back to my PC & flashed it via fastboot.
Click to expand...
Click to collapse
How did you do it? I did my 2nd attempt and still failed.
Also, comparing the boot.img is way different. The original boot.img is 60mb while the patched boot.img is about 10mb. Is that supposed to be right?
ShadowWeasel said:
How did you do it? I did my 2nd attempt and still failed.
Also, comparing the boot.img is way different. The original boot.img is 60mb while the patched boot.img is about 10mb. Is that supposed to be right?
Click to expand...
Click to collapse
All I did to root is listed in the steps above. My patched boot images are also much smaller, I think the original boot image is just padded as it's a perfect 64MB. My patched boot image is 11.8MB. All I can think of is that the boot image your patching & flashing may not be the exact version that phone is running. My phone shipped with SOFIAP_RETAIL_QPR30.80_58 & the update from last week was SOFIAP_RETAIL_QPRS30.80_58_3. Where are you getting your original boot.img file from?
I recently bought an amazon echo dot second generation with the idea of hacking it to install my own OS onto it. I have tried poking at it with fastboot tools but I haven't been able to unlock the bootloader, let alone install a custom rom. When I run
Code:
fastboot getvar all
, I get this:
Code:
(bootloader) lk_build_desc: f379dba-20170906_000423
(bootloader) pl_build_desc: 531fa14-20170929_175430
(bootloader) prod: 1
(bootloader) unlock_status: false
(bootloader) unlock_code: 0xea7ab546330135bf
(bootloader) serialno: G090LF1182070BR6
(bootloader) max-download-size: 0x6d00000
(bootloader) warranty: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: BISCUIT
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.005s
I'd like to draw attention to the unlock_code line. I can't seem to find what that means, but it could allow me to unlock the bootloader and get one step closer.
Before you comment something like "Oh yeah that's not possible", Don't. That's not helpful and could possibly be wrong.
You can already exploit them using amonet if you want to boot your own code. Take a look at http://andygoetz.org/tags/dot/