Related
Hi guys!
Well, I'm new in what concerns to root, unlock, ROM's, kernels (no idea of what it is still), etc. I have a Xperia Arc, GB 2.3.4, branded for T-Mobile.
As I'm fed up with the bunch of bloatware, I wanted to root/debrand it, in order to get rid of it.
First I tried with this thread: http://forum.xda-developers.com/showthread.php?t=1035276 Post #2
Links for the ROM were dead, so I searched for some other thread. After a lot, I found this one: http://forum.xda-developers.com/showthread.php?t=1042978
I found it easy to lead, so i tried. I got so far, to even unlock my bootloader, but then, trying to root, I found the images link for the Global firmware was dead.
Then I realized, I wanted to change to the global versión for the mere reason of having ICS sooner (branded phones take longer to receive it, as far as I know). Then I saw, that actually I went in the full wrong direction when unlocking the bootloader.
I tried to relock thebootloader, by following the steps in this thread: http://forum.xda-developers.com/showthread.php?t=1324703
It appears to have worked well, but I'm not sure.
My questions are:
1) I want the SE ICS update, that is due to be available this month anytime. Since unlocking the bootloader might have turned my phone to brick (or not?) when upgrading, how can I be sure I did actually re-lock my bootloader? The guys from Android Soul Comnunity used a "Test" on their videos, which was running a program in fastboot mode, which apparently does something if the phone is unlocked, although it said "it needs to be rooted". Is there a way to know if I did it correctly relock whitout damaging my phone or flashing it by mistake in the process.
2) I really want to flash it to a global version and get rid of the bloatware (maybe rooted if posible), but also getting the official upgrade. Is there a way? I have the latest flashtool version and I downloaded the ftf file for the global version, but whenever I press flash in flashtool, it doesn't show anything (nor sin files or anything else). Maybe I will give it another try if someone else provides me with a functional link to the functional ROM (I really don't remember where I got the one I have).
I hope you guys can help me. I'm not a native english speaker, so forgive me for any mistake. Thanks in Advance
HerrJuancho
seems like you are new to this....so was I about 4 months ago.
if your bootloader is unlocked, good - keep it that way.
the best way to learn how to mess around is follow this thread step-by-step:
http://forum.xda-developers.com/showthread.php?t=1299729
I know that this thread is instructing you to flash cm7 - but dont worry, once you have done that, you will understand the basics and the processes involved.
if you really want ICS - then you can just us Arconium 2.2 as it is the closed custom rom to a stock ICS - it is tweaked and customized, so it will be better than any global rom you try to flash.
http://forum.xda-developers.com/showthread.php?t=1515148
kaatisu84 said:
seems like you are new to this....so was I about 4 months ago.
if your bootloader is unlocked, good - keep it that way.
the best way to learn how to mess around is follow this thread step-by-step:
http://forum.xda-developers.com/showthread.php?t=1299729
I know that this thread is instructing you to flash cm7 - but dont worry, once you have done that, you will understand the basics and the processes involved.
if you really want ICS - then you can just us Arconium 2.2 as it is the closed custom rom to a stock ICS - it is tweaked and customized, so it will be better than any global rom you try to flash.
http://forum.xda-developers.com/showthread.php?t=1515148
Click to expand...
Click to collapse
Thanks, I thought no one would answer.
I don't know if I actually still have a unlocked bootloader. How can I tell the difference? By doing what?
If it is really that good, the I would prefer it over the official. Thanks
HerrJuancho said:
Thanks, I thought no one would answer.
I don't know if I actually still have a unlocked bootloader. How can I tell the difference? By doing what?
If it is really that good, the I would prefer it over the official. Thanks
Click to expand...
Click to collapse
Do this
1)Connect your phone on fastboot mode.
2) open cmd prompt in the fastboot folder
3) type this in the command window
fastboot.exe -i 0x0fce get var version
4) if you get a value like 0.3 or something its unlocked
Sent from my LT26i using xda premium
king-iyokan said:
Do this
1)Connect your phone on fastboot mode.
2) open cmd prompt in the fastboot folder
3) type this in the command window
fastboot.exe -i 0x0fce get var version
4) if you get a value like 0.3 or something its unlocked
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Well, that's actually one of the steps before unlocking, I thought it was just a sign that the device was well connected and that the drivers were up to date. My phone wasn't unlocked, and it did show 0.3 right before trying to unlock it.
HerrJuancho said:
Well, that's actually one of the steps before unlocking, I thought it was just a sign that the device was well connected and that the drivers were up to date. My phone wasn't unlocked, and it did show 0.3 right before trying to unlock it.
Click to expand...
Click to collapse
Ohh sorry. My bad. Try to boot a custom kernel via fastboot.
Fastboot.exe boot boot.IMG
If you get a notice "device not rooted" or similar the bootloader is loced.
If you are able to boot the kernel the bootloader is unlockd
Sent from my LT26i using xda premium
You can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (cheaper but FunkyHuawei is more certain)
As most of you already know, Huawei stopped giving away bootloader unlock codes. So it is up to us, to hack our way to root and custom ROMs.
Following, are a few things we could try,
Also, I own a Nova 3i currently. There are always the possibility that something working for me won't work for you, because of different chipsets, but I guess that this forum is also for the development of Nova 3i.
NOTE THAT SOME OF THE FOLLOWING ARE PAID SERVICES. I'M NOT RELATED WITH ANY OF THEM.
+DC-Unlocker:
I tried the latest version, got an unknown error 375. (This error also goes for the latest versions of P20 Pro, Mate 10, etc.). And the developers said that they won't support any new Huawei phones, and that they'll leave new Huawei phones for HCU-Client, because the two services are related.
+HCU-Client:
You can't try this without buying credits. If you feel generous, go on and try this. They released a couple of new versions in this week.
+Bootloader exploiting:
I really don't know anything about this, feel free to contribute.
+Secret Fastboot backdoors:
There can be a LOT of these, considering that there are a family of commands under <fastboot oem backdoor>. And I discovered quite a lot of secret commands, almost every one of them sounding like that they could seriously brick the device. For example, consider what <fastboot oem djtagtosd> sounds like. (Search Google for JTAG) If you would like to test some of the less-dangerous looking ones, please PM me, even an old Huawei device is okay as long as it has a Kirin chipsets.
Please check this link from P20 Pro Forum - we may have a chance to be supported if many of us do the request. I have done mine. - https://forum.xda-developers.com/hu...ol-tool-one-driversunlocktwrpfactory-t3779080
waltermsalomon said:
Please check this link from P20 Pro Forum - we may have a chance to be supported if many of us do the request. I have done mine. - https://forum.xda-developers.com/hu...ol-tool-one-driversunlocktwrpfactory-t3779080
Click to expand...
Click to collapse
Sorry, did not see this. So, this tool installs TWRP without unlock codes? Still we need to get TWRP compiled.
Huawei nova 3i rom
Dears I need stock firmware and flash tool officially for Huawei Nova 3i ine-lx1
cant EU do anything about this bootloader unlocking situation? I mean, isn't it our right to do whatever we want with our bought device? Im actually not from any EU country btw.
jioleight said:
cant EU do anything about this bootloader unlocking situation? I mean, isn't it our right to do whatever we want with our bought device? Im actually not from any EU country btw.
Click to expand...
Click to collapse
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Supersonic27543 said:
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Click to expand...
Click to collapse
mandated but no one is enforcing it so huawei will just delay the relase of the kernel source until the insterest has died out.
nope, not gonna take that risk :laugh:. $55 seems cheaper until it's converted to my country's currency. haha.
Supersonic27543 said:
Maybe there is some legislation about that, actually the issue of locked bootloaders runs more than 6/7 years (I think) and they had plenty of time if they wanted to do that... but we can hope, considering things like GDPR.
At least one of things they MUST do is releasing the kernel sources, because by using Android they agree to some license (I don't remember the name) that mandates releasing kernel source..
BTW you can now unlock the bootloader with FunkyHuawei for a fee of $55, or 30 Euros with Ministry of Solutions (they are cheaper, but they look more shady, and I can't help noticing that there website looks just like one of those poorly done scam sites :laugh
Click to expand...
Click to collapse
Another one source to unlock bootloader - $22
This method has already been tested on 4pda. Working TWRP can be taken from here
And HCU doesn't have NOVA 3 support yet to read the unlock code now
OEM Unlock option
Is it enought to enable "OEM Unlock" in "Developer Options" from the phone settings to unlock the bootloader and I can simply install TWRP afterthat? (the option "OEM Unlock" is not greyed out, and can be easily enabled, at least in the devices that are sold in my country).
Or do I still have to unlock it using unlock key from Huawei Website (or other sources)?
Jan oatcoal said:
Do I still have to unlock it using unlock key from Huawei Website (or other sources)?
Click to expand...
Click to collapse
Yep. It is like this when you issue the command in fastboot to unlock:
Without code and without enabling the toggle: Gives and error telling to turn on the toggle.
With code and without enabling the toggle: Same as above
Without code and toggle enabled: Error wrong password
With both: Success
I think we are lucky on that side, I think that the toggle is also disabled on Mate 20 series. So we can unlock the bootloader. with external sources for now, so it may be a good idea to block OTA updates.
Ine-lx2 8.2.0.131(c636)
*update*
so i checked using fastboot oem get-bootinfo. lo and behold it's really unlocked.
jioleight said:
does Phone Unlocked mean the bootloader or just the GSM part that is unlocked?
Click to expand...
Click to collapse
I did this then installed titanium backup and it said it wasn't rooted.
meekspace said:
I did this then installed titanium backup and it said it wasn't rooted.
Click to expand...
Click to collapse
you have to root first by installing magisk or supersu. and it needs twrp to root. in case of nova 3i there isnt any existing twrp. only on nova 3 since it has the same soc as p20pro.
was about to test it on my nova 3i. good thing i checked the specs of nova 3 first before proceeding.
Unfortunately, cant flash patched ramdisk since fastboot fail. Remote command not allowed. So close yet so far away.
jioleight said:
Unfortunately, cant flash patched ramdisk since fastboot fail. Remote command not allowed. So close yet so far away.
Click to expand...
Click to collapse
Let's try flashing the stock boot.img. If that works, I will patch the boot image to manually disable dm-verity and add Magisk.
Supersonic27543 said:
Let's try flashing the stock boot.img. If that works, I will patch the boot image to manually disable dm-verity and add Magisk.
Click to expand...
Click to collapse
"fastboot flash ramdisk patched_boot.img". That's what entered in cmd. Also after magisk patched the ramdisk the patched ramdisk is only 5mb. The original was around 25mb.
What should be patched anyway? I patched ramdisk.img via magisk ang since the partitioning is different with phones released with oreo. What is your method?
*update*
well, this sux. based on what i have read on other huawei device flashing via fastboot is not always the best way. the phone may display that the bootloader is unlock but it wont still allow any modifications. why cant this be straight forward like samsung/oneplus. this is frustrating.
jioleight said:
"fastboot flash ramdisk patched_boot.img". That's what entered in cmd. Also after magisk patched the ramdisk the patched ramdisk is only 5mb. The original was around 25mb.
What should be patched anyway? I patched ramdisk.img via magisk ang since the partitioning is different with phones released with oreo. What is your method?
*update*
well, this sux. based on what i have read on other huawei device flashing via fastboot is not always the best way. the phone may display that the bootloader is unlock but it wont still allow any modifications. why cant this be straight forward like samsung/oneplus. this is frustrating.
Click to expand...
Click to collapse
What if we try obtaining a code by one of the third party methods and try that? Maybe they just forgot or didn't care to set the variables you saw there as this is a new chipset. I think it is not really unlocked, if it was the phone will display the "Your device has been unlocked and cannot be trusted" message on boot.
Looks like what I said before is true. fastboot oem lock-state info returns USER Locked.
Has anyone tried this?
https://www.techdroidtips.com/unloc...i/#How_to_Unlock_Bootloader_on_Huawei_Nova_3i
stevefwt said:
Has anyone tried this?
https://www.techdroidtips.com/unloc...i/#How_to_Unlock_Bootloader_on_Huawei_Nova_3i
Click to expand...
Click to collapse
They are just copy pastes and no longer works as of Huawei stopping providing codes.
Google should try to remove them from coming at top of Google searches, IDK.
Anyone can help me for unlocking this device? i didn't know if the new patch can't be unlocking, i bought this phone since 2 weeks ago, and i updated 'til security patch January 2019, then, i search how to unlock, always patch 8.1.
so hopeless, i don't know how to send this problem to google support/chat with them.
help please, i need to root
Yosh2897 said:
Anyone can help me for unlocking this device? i didn't know if the new patch can't be unlocking, i bought this phone since 2 weeks ago, and i updated 'til security patch January 2019, then, i search how to unlock, always patch 8.1.
so hopeless, i don't know how to send this problem to google support/chat with them.
help please, i need to root
Click to expand...
Click to collapse
If it's a Verizon variant phone, I'm afraid you can't unlock the bootloader, much less root it. Sorry man
Badger50 said:
If it's a Verizon variant phone, I'm afraid you can't unlock the bootloader, much less root it. Sorry man
Click to expand...
Click to collapse
So hopeless, i just want to control my battery using kernel adiutor
Sent from my Pixel 2 using Tapatalk
Yosh2897 said:
So hopeless, i just want to control my battery using kernel adiutor
Click to expand...
Click to collapse
Sorry man. KA requires root, so that's not a possibility either :fingers-crossed:
Yeah I made the same mistake , grabbed a XL 2 for 200 and realized it was a vzw variant
Yosh2897 said:
So hopeless, i just want to control my battery using kernel adiutor
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
There are many ways you can better manage battery life with a locked, unrroted device.
Try these.
- use Greenify
- use Adaptive brightness
- reduce time for display to go to sleep
- use dark themes
- turnoff wifi & bluetooth scanning
- drain battery to 15%, remove from charger at 90%
- turn off apps you don't need running in the background
Az Biker said:
There are many ways you can better manage battery life with a locked, unrroted device.
Try these.
- use Greenify
- use Adaptive brightness
- reduce time for display to go to sleep
- use dark themes
- turnoff wifi & bluetooth scanning
- drain battery to 15%, remove from charger at 90%
- turn off apps you don't need running in the background
Click to expand...
Click to collapse
Please tell me configuration on your greenify, i will enable access user from adb, and how to turn off running in background? Cause it's minimal option, maybe 10 app on check background, not at all
Sent from my Pixel 2 using XDA Labs
And, hey everybody, I'm success activate unlocking bootloader, then i try to unlock using fastboot, it comes with failed command, then i reboot the device, oem unlocking turn greyed out again
Sent from my Pixel 2 using XDA Labs
Yosh2897 said:
And, hey everybody, I'm success activate unlocking bootloader, then i try to unlock using fastboot, it comes with failed command, then i reboot the device, oem unlocking turn greyed out again
Sent from my Pixel 2 using XDA Labs
Click to expand...
Click to collapse
Are you not paying attention? You can't unlock or root a Verizon branded 2XL.
Yehudah said:
Are you not paying attention? You can't unlock or root a Verizon branded 2XL.
Click to expand...
Click to collapse
Come on, i try so hard to enable that f*cking oem unlocking, try to unlock via fastboot, but command shows failed, and i restart oem unlocking greyed out again, i try by myself within 10 times, and yesterday i try again, it success to enable with command adb shell -d pm user 0 uninstall com.android.phone
But when try fastboot, it comes failed.
Dude, I'm not gonna paying attention about this, i really want install custom kernel
Yosh2897 said:
Come on, i try so hard to enable that f*cking oem unlocking, try to unlock via fastboot, but command shows failed, and i restart oem unlocking greyed out again, i try by myself within 10 times, and yesterday i try again, it success to enable with command adb shell -d pm user 0 uninstall com.android.phone
But when try fastboot, it comes failed.
Dude, I'm not gonna paying attention about this, i really want install custom kernel
Click to expand...
Click to collapse
I usually don't get involved in these B*tch sessions but come on man. The brightest minds on this device have all but given up on it. The road to root is littered with the carcasses of many a disappointed buyer. You are standing in back of a very long line of people that had to come to the realization that it's probably never ever going to happen on the Verizon Pixel 2XL. Period...
CyberpodS2 said:
I usually don't get involved in these B*tch sessions but come on man. The brightest minds on this device have all but given up on it. The road to root is littered with the carcasses of many a disappointed buyer. You are standing in back of a very long line of people that had to come to the realization that it's probably never ever going to happen on the Verizon Pixel 2XL. Period...
Click to expand...
Click to collapse
If you said never ever going happen on the verizon pixel 2XL
Sorry, but I'm on pixel 2, still no chance?
I feel you Cyberpod...but, looking through this specific thread...I don't believe he's actually stated outright or confirmed that it is in actuality a Verizon variant...
I would say that's first and foremost OP...I know you are rather impatient about it, and tried some things, and intend "...not gonna paying attention about this...", but you really should verify (for sure) if you have the proper variant.
Also, merely reading through this specific thread, he may simply want to talk/contact Google Pixel support but didn't know how... Although, even the smallest bit of effort would easily find the answer; I'll "throw you a bone"... you will find it here: https://support.google.com/pixelphone/?hl=en#topic=7078250&contact=1
But, to be blunt, if you are going to ask for help here on XDA, we at the very least expect the bare minimum of effort (without complaint) and not handing everything "on a silver platter"... this is just not that kind of place...
UPDATE: Post #12 seemed to have been input and came in a minute before this one (mine)... but see! Verifying if it's a Verizon variant was never established and needs to be...
bro, why i make this thread and try to ask you all,
i got command like this
C:\adb>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>fastboot flashing lock_critical
...
FAILED (remote: unknown command)
finished. total time: -0.000s
C:\adb>fastboot --version
fastboot version eac51f2bb6a8-android
C:\adb>fastboot flashing unlock_critical
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\adb>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
finished. total time: 0.016s
C:\adb>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash unlock
unknown partition 'unlock'
error: cannot determine image filename for 'unlock'
C:\adb>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
Yosh2897 said:
bro, why i make this thread and try to ask you all,
i got command like this
Click to expand...
Click to collapse
What answer are you expecting? It's not possible. Verizon locks the bootloader and nobody has found away around that. Either live with that or sell your phone and get one that's unlocked.
Yosh2897 said:
If you said never ever going happen on the verizon pixel 2XL
Sorry, but I'm on pixel 2, still no chance?
Click to expand...
Click to collapse
Constantly repeating a task and expecting the result to change is a sign of insanity. While I don't think you've lost your mind - yet - you're rapidly descending to that level. I've said this before and I'll say it again. If you want root you do not buy a Verizon device!
Since you apparently have a Verizon device, your options are to sell it or live without root, which actually is doable. No exploit has been found to bypass the bootloader encryption, and brute forcing the encryption itself will take a period of time greater than the age of the universe.
I never expect to get bundling device by verizon, but, indonesia doesn't have official store, all of them selling this phone without knowing what type they got and just sell to buyer, to be honest, hard to find a sparepart, warranty for this device, so the option, i just do by myself. I'm sorry if pushing you all, and always ask about this things. Have a nice day mate.
Moto G7 Play bootloader unlock issues - "bad key", not OTA, no way to roll back?
My plan was to unlock the bootloader before configuring the new phone - just in case I might need it later, then use the phone as out-of-box. I unlocked the bootloader for the new Moto G7 Play, following the official procedure via the Motorola Accounts page, resulting in:
- Fastboot page shows: "flashing unlocked"
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
- I could not try TWRP, as there is no TWRP for the G7 Play yet (so not sure if flashing would work)
My concerns now are that I will not be able to update the phone, and that the "bad key" issue might cause other problems.
So my plan would be to roll back and lock the phone again, to use it as out-of-box (not worrying about warranty loss that might already have happened - I did accept these terms). However, that does not work, too:
- Locking bootloader requires factory images, which are not available for the G7 Play
- Locking bootloader with fastboot OEM lock will not work without complete images
Any suggestions how bring the phone back to normal? I am disappointed by Motorola, as they officially offer the unlock procedure - which then does not produce the expected outcome, breaks updating, and provides no way to go back? Mind you, I did not apply any "hacks", nothing but the official Motorola unlocking steps.
Thanks for advice
I have the same problem and i cannot fix it.
I tried to get advice from Motorola support - but replies are very generic, referring to the bootloader unlock page (we obviously found that) or to the Motorola Forum (where the answer isn't). Will now just live with the unlocked phone and hope for the opportunity to OTA / update in a while
CoffeeMachineSwitch said:
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
Click to expand...
Click to collapse
Unlocking any Motorola bootloader will cause the bootscreen to display "Bad Key". This is normal. It is a warning that the bootloader has been unlocked and the phone may not be "safe". Once you root a Motorola phone, it will display "N/A" instead of "Bad Key". Again, this is normal behavior. There are image makers that can replace the "splash" image and "hide" the "N/A", but since this phone doesn't have TWRP yet, you'll have to live with it for now.
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
mn1968 said:
Unlocking any
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
Click to expand...
Click to collapse
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
CoffeeMachineSwitch said:
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
Click to expand...
Click to collapse
That would be an unfortunate change if true. Prior devices could be unlocked and still get OTA updates. They won't install if certain changes are made but still get notified of updates.
You still can install full ROM using fastboot commands and regain root by patching boot.img from updated ROM
I did it on both G6 and G7
Where did you get the ROM images from. I understand there are no officials?
CoffeeMachineSwitch said:
Where did you get the ROM images from. I understand there are no officials?
Click to expand...
Click to collapse
Have you tried the LMSA tool? It's a tool you download from Motorola. There is a discussion here about it. It has a rescue button with which, I understand that you can download stock images directly from Motorola, but I haven't used it myself.
umbrisle said:
Have you tried the LMSA tool? ....
Click to expand...
Click to collapse
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
CoffeeMachineSwitch said:
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
Click to expand...
Click to collapse
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Should've read the thread here before i go buy g7 play, not my phone get softbricked.
Unblocked bootloader successfully following the official doc but failed to install magisk by copying the wrong build number of boot.img of OTA from here mirrors.lolinet.com/firmware/moto
now my g7 says
Code:
failed to load kernel, no Bootable A/B slot,
Failed to book Linux
falling back to fastboot.
I downloaded `RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC` which i think this is the right build number when i see error like
Code:
river/retail corrupted
(can't remember exactly, but it's RETAIL not RETUS)
and make my own version of fastboot command stemming from servicefile.xml, still with unlucky.
there is no recovery.img and google has limited resource to make g7 play back to stock orm, i'd like to see if community has any idea or i have to give it to moto to fix it.
========================update=================================
update: i finally get the correct stock ORM which is exactly matching my build number "XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" i was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict, "second time rooting in my life".
not i has flash all of the original orm into my phone then fastboot reboot works, it give me the original error like
Android Recovery
motorola/channel_retail/channel9/PPY29.105-36/d7abeuser/release-keys
Use volum up/down and power
can't load Android system. Your data may be corrupt.
If you continue to get this message, you may need to perform a factory data
reset and erase all user data stored on this device
=====
Try again
Factory data reset
Click to expand...
Click to collapse
now i need to figure out what to do next
===============update=========
lol, turns out just press Factory data reset will bring the brick back to life!!!!!
just want to post my process for anyone having my issue.
the key point to find the correct build number
umbrisle said:
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Click to expand...
Click to collapse
.
The G6 Play is really slow, at least the Boost one. I was kind of sorry I bought one to put on Sprint's free unlimited plan. At least Sprint unlocked it for me after 60 days.
Give the G7Play some time, it just came out.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
gedster314 said:
.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
Click to expand...
Click to collapse
Yeah, but there is inconsistency in Motorolas communication, they actively offer the option to unlock the bootloader (with T&C and all) incl. a link to a rollback feature. Which then does not work. So in a scenario where a developer buys the device because it actively offers this features, they dont get what they paid for. Mind you, we are not discussing hacking a device here or jailbraking - we are discussing features that Motorola actively promotes with a dedicated webpage.
wallace_mu said:
was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict
Click to expand...
Click to collapse
You completely missed the wrong code name "river" in RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC it is for another device, while "channel" is the right one
Where did you get the correct Rom from? Thanks
I don't own Moto G7 Play and can not confirm, however this one worked for wallace_mu
wallace_mu said:
XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
realsine said:
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
Click to expand...
Click to collapse
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
CoffeeMachineSwitch said:
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
Click to expand...
Click to collapse
Hello,
I'm glad to read that I could help.
I have "my" image of 'https :// mirrors.lolinet.com/firmware/moto/channel/official/RETEU/'. There are also some others - just have a look. And please remove the spaces around '://'. I'm currently not allowed to post (external) links, so this way.
* Every 'LOCK' deletes all data and the system is "clean" again.
* The same applies (unfortunately) to EVERY 'UNLOCK'.
I don't care at the moment because I haven't set up my smartphone yet. But it's not nice.
Best regards
Hi guys
I do have an unusual situation here. Got a Honor View 20 Test device (or presample) directly from a Honor guy. I'm really happy about it as the bootloader is already unlocked. Okay, I honestly don't know what's the plus about it as I can't find a TWRP for this one.
Anyway, my main issue is the installed test ROM:
It shows:
Model: VNA-L29
EMUI Version 8.1
Android Version 8.0
Internal Memory 32GB
RAM 4GB
Using DevCheck System Info App it shows the truth:
Android Version 9.0
Internal Memory 128GB
RAM 6GB
There are some testing apps on it which I can't uninstall. One of them locks the phone after some days if I'm logging in. I have to do a hard reset to make it work again.
Updating the ROM in Recovery doesn't work. Uninstalling the app doesn't work. I'm thinking about trying to update to an official ROM thru DLOAD or HiSuite but this would lock the bootloader I guess - if it's even possible. So if I would be able to install TWRP and an official ROM to use with TWRP I should be able to update it.
Any idea? Every help is appreciated! Thank you!
---------------------
Update: I took the risk and just flashed the actual ROM 238 from androidhost.ru thru DLOAD. Phone works like charm and device still has an unlocked bootloader.
Thanks!
dude010 said:
Hi guys
I do have an unusual situation here. Got a Honor View 20 Test device (or presample) directly from a Honor guy. I'm really happy about it as the bootloader is already unlocked. Okay, I honestly don't know what's the plus about it as I can't find a TWRP for this one.
Anyway, my main issue is the installed test ROM:
It shows:
Model: VNA-L29
EMUI Version 8.1
Android Version 8.0
Internal Memory 32GB
RAM 4GB
Using DevCheck System Info App it shows the truth:
Android Version 9.0
Internal Memory 128GB
RAM 6GB
There are some testing apps on it which I can't uninstall. One of them locks the phone after some days if I'm logging in. I have to do a hard reset to make it work again.
Updating the ROM in Recovery doesn't work. Uninstalling the app doesn't work. I'm thinking about trying to update to an official ROM thru DLOAD or HiSuite but this would lock the bootloader I guess - if it's even possible. So if I would be able to install TWRP and an official ROM to use with TWRP I should be able to update it.
Any idea? Every help is appreciated! Thank you!
Click to expand...
Click to collapse
Send it back and ask for an actual phone
Hamza5682 said:
Send it back and ask for an actual phone
Click to expand...
Click to collapse
Thanks for the advice :laugh: :laugh:
I got this one for free so I wanna make the best out of it.
Huawei/Honor devices cannot be unlocked. So there is no active community with CFW developements so there is no point whatsoever of going in to shady sites and trying to 'unlock' your device bootloader.
You can try to update with download method(as it is the only way) If you brick the phone just recycle it and be done with it. There is not many options.
looneylv said:
Huawei/Honor devices cannot be unlocked. So there is no active community with CFW developements so there is no point whatsoever of going in to shady sites and trying to 'unlock' your device bootloader.
You can try to update with download method(as it is the only way) If you brick the phone just recycle it and be done with it. There is not many options.
Click to expand...
Click to collapse
Thanks for your feedback. As I wrote at the end of my first post I updated with the regular firmware. Everything works smooth and the bootloader is still unlocked.
I'll try this at the weekend with the manual I found on XDA. There are CFW for a lot of Honor and Huawei devices but the firmware is quite old so I'll not even try .
https://openkirin.net/devices/
Maybe it's just fake
looneylv said:
Huawei/Honor devices cannot be unlocked. So there is no active community with CFW developements so there is no point whatsoever of going in to shady sites and trying to 'unlock' your device bootloader.
You can try to update with download method(as it is the only way) If you brick the phone just recycle it and be done with it. There is not many options.
Click to expand...
Click to collapse
Why would you say that when it is clearly possible? My Honor View 20 is unlocked and has Magisk running on it. There are other people with an unlocked bootloader, just look at the "Root Guide" Thread.
The problem is getting the unlock code. As far as i know there are no trustworthy providers at the moment so please be carfeful!
Regards
garris_bibop said:
Why would you say that when it is clearly possible? My Honor View 20 is unlocked and has Magisk running on it. There are other people with an unlocked bootloader, just look at the "Root Guide" Thread.
The problem is getting the unlock code. As far as i know there are no trustworthy providers at the moment so please be carfeful!
Regards
Click to expand...
Click to collapse
Because there is no official way to unlock phones bootloader(you cannot get unlock code, at least officially) If you are willing to give your personal info in shady sites, that is your own risk and fault if your IMEI get's in to wrong hands....
So basicly im guessing there is 90% locked vs 10% unlocked Huawei/Honor phones in the world. :good: Congrats if you are 'geek' enough and went true the shady process to get in those 10%. BUT there is no active developements of CFW. Yes there is some but they are unstable...
Oh yeah and official security apps(like banking, to pay with nfc) for security reasons check phones bootloader and if it is rooted/unlocked then you cannot start them. I dont know if it is worth the trouble anymore to bang on your chest and root your android just because of ''freedom''....
Again, it IS possible, thats what i'm saying. Nothing more, nothing less. So if you say 'its is not possible to unlock bootloader' then thats just plain wrong. Everyone should be able to make an informed decision for themselves, we're not children anymore. I definitely agree that you shouldn't give your data to some shady site.
In addition, i'm not sure what unlocking and rooting yout phone has to do with 'banging on your chest'.
Although the advantages may be minor nowadays, they are still there. The banking apps (i'm using) work just fine. If you are used to rooting your phone then its hard to accept all the restrictions
Regards
Previously ive rooted all my androids aswell. But ive stopped on my last main device(4years ago) because when you have full official support, whats the point? The hustle of manually flashing weekly because of updates and bug fixes... Meehh. Its not 2010 anymore when it was 'cool' to have a rooted phone(thats why the chest expression. )
If the device is like 3years old and dosent have update support anymore from the manufacturer
then it is a different story. Then you can flash newer custom android version and play with the device more to extend phone pocket life.
Ehmm i guess it is in country's security law or something. Because here where i live none of the banking apps work if you have rooted phone, when you open it just sayes that security check failed and error code(that you have a rooted phone)
neither lot of cupon apps where there is your sensitive info. ???Even mcdonalds app dosent let to use cupons on my rooted phone.
I have older rooted android to play on in my spare time. ?
Think we're on the same page anyway, right?
Guess i am lucky that i have rooted phone with apps and updates working. Though, i have to mention this again, i'm not sure what that has to do with being cool. Ppl are not bragging about it (at least no one i know ever has), its just that i like to have as many customization options as possible. Coming from a Xiaomi device i felt pretty restricted at the beginning
Doesn't matter, have a nice day!
Regards