Database Users

[Q] Forge Recovery?

Any skilled dev here is able to make recovery for Razer Forge? I know it's nexus forums but these 2 are kinda similar both run android tv etc.. root can be achieved with kingroot then one can swap (if knows how) to SuperSU.
I would love to have some CM 12.1 on it.. and don't know where to ask.
Any help?

the only thing they seem to have in common is the fact that they run android tv, they are totally different when it comes down to hardware. but if your wanting it to happen you should post some dumps from the system so devs can take a look at them and possibly build a recovery. if the bootloader is locked that can be another issue also.

pbanj said:
the only thing they seem to have in common is the fact that they run android tv, they are totally different when it comes down to hardware. but if your wanting it to happen you should post some dumps from the system so devs can take a look at them and possibly build a recovery. if the bootloader is locked that can be another issue also.
Click to expand...
Click to collapse
How can I find out if bootloader is locked or not?
fastboot oem unlock ? I would need USB to USB cable to do adb first.
Would that be good way to find out?

pbanj said:
the only thing they seem to have in common is the fact that they run android tv, they are totally different when it comes down to hardware. but if your wanting it to happen you should post some dumps from the system so devs can take a look at them and possibly build a recovery. if the bootloader is locked that can be another issue also.
Click to expand...
Click to collapse
Hey a late update about 3 weeks ago razer provided tools with home image etc.. I'd like to post system dump when I get back to the states in couple days,bootloader is unlockable with fastboot oem unlock.
You think you could help me out ?

Please help want to unlock bootloader

Guys please help I can't unlock the boot loader(ze550kl) for the following model I wanted to install cm. Thank you
ASUSSKU WW
BOARD msm8916
BOOTLOADER unknown
BRAND asus
CHARACTERISTICS phone
COUNTRYCODE WW
CPU_ABI arm64-v8a
DEVICE ASUS_Z00L_63
DISPLAY LRX22G.WW_user_1.17.40.1234_20160304
FINGERPRINT asus/WW_Z00L/ASUS_Z00L_63:5.0.2/LRX22G/WW_user_1.17.40.1234_20160304:user/release-keys
HARDWARE qcom
HOST builder5-pc
ID LRX22G
MANUFACTURER asus
MODEL ASUS_Z00LD
PRODUCT WW_Z00L
TAGS release-keys
TYPE user
USER builder5
CODENAME REL
INCREMENTAL WW_Z00L-WW_user_1.17.40.1234_20160304-user-20160304
RELEASE 5.0.2
SDK_INT 21
RADIO 202c10_11.1.0_160304
Root Access:no access
SU:not found
How to unlock bootloader?

Use the boot loader unlock app found in the General subforum.

HampTheToker said:
Use the boot loader unlock app found in the General subforum.
Click to expand...
Click to collapse
I tried it just restarts and there is no white logo screen

The white logo screen is only for the ZenFone 2 base models. For ZenFone 2 Laser variants, the logo screen will and should remain black. To verify whether your device hadha been truly unlocked, head over to fastboot mode on your device, and type the command: "fastboot oem device-info" (without the quotes) into the command prompt/terminal.
If it says device unlocked: true, that means your device had been successfully unlocked.
Another method is to try flashing TWRP onto your device, then attempting to boot into recovery. If it boot successfully, your device had been unlocked. If the ASUS logo just flashes and goes instantly, and then rebooting back to the system, it is still locked.

Rizzed said:
The white logo screen is only for the ZenFone 2 base models. For ZenFone 2 Laser variants, the logo screen will and should remain black. To verify whether your device hadha been truly unlocked, head over to fastboot mode on your device, and type the command: "fastboot oem device-info" (without the quotes) into the command prompt/terminal.
If it says device unlocked: true, that means your device had been successfully unlocked.
Another method is to try flashing TWRP onto your device, then attempting to boot into recovery. If it boot successfully, your device had been unlocked. If the ASUS logo just flashes and goes instantly, and then rebooting back to the system, it is still locked.
Click to expand...
Click to collapse
Thanks Rizzed I'll check via fastboot

Any results?

Same device and same problem
I have tried with a few "different" unlock apps and still get the following result after running
Code:
fastboot oem device-info
HTML:
...
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.004s]
finished. total time: 0.004s
Also I noticed that Asus' support page from the country where the device was bought does not have "utilities" section where the unlock apk would be located. (can't post a direct link since I'm new here, so here's part of the link: asus.com/br/Phone/ZenFone-2-Laser-ZE550KL/HelpDesk_Download/)

for this version of firmware(WW_user_1.17.40.1234_20160304) it does not work.. I have tried many times ... I am downgrading to 1.16.... will check.. For 1.16, bootloader unlock works with the unlocker app for ze600kl

hemantjangid39 said:
for this version of firmware(WW_user_1.17.40.1234_20160304) it does not work.. I have tried many times ... I am downgrading to 1.16.... will check.. For 1.16, bootloader unlock works with the unlocker app for ze600kl
Click to expand...
Click to collapse
Does it really work after downgrading? I'm currently sitting right here pulling my hair out over this. Would be great if it really works.

Did you manage to downgrade?
I tried downgrading but failed with fota_return_code 409 ("can't install this package [date] over newer build [date]").

igorrafael said:
Did you manage to downgrade?
I tried downgrading but failed with fota_return_code 409 ("can't install this package [date] over newer build [date]").
Click to expand...
Click to collapse
Before attempting to downgrade, go to FASTBOOT mode, and type this commands (in order),
fastboot erase system
fastboot oem reboot-recovery
It should be able to flash successfully now.

Rizzed said:
Before attempting to downgrade, go to FASTBOOT mode, and type this commands (in order),
fastboot erase system
fastboot oem reboot-recovery
It should be able to flash successfully now.
Click to expand...
Click to collapse
Thanks for the tip. Erasing system didn't work but your gave me the idea of changing the recovery partition. I managed to flash the stock version from this post. Only after the second line of the recovery screen showed "1.16" I managed to flash the file UL-Z00L-WW-1.16.40.763-user.zip
Unfortunately still didn't manage to unlock after a factory reset with the new firmware. Using unlock apk from this post:

igorrafael said:
Thanks for the tip. Erasing system didn't work but your gave me the idea of changing the recovery partition. I managed to flash the stock version from this post. Only after the second line of the recovery screen showed "1.16" I managed to flash the file UL-Z00L-WW-1.16.40.763-user.zip
Unfortunately still didn't manage to unlock after a factory reset with the new firmware. Using unlock apk from this post:
Click to expand...
Click to collapse
Really sorry about that..
I'm currently trying out all the other previous software, starting from the latest to the oldest. I will inform you immediately if it works out.

nrv.patel said:
I tried it just restarts and there is no white logo screen
Click to expand...
Click to collapse
I have been trying to unlock using the official unlock app since seven days. @Rajko said the app works sometimes. Also I have noticed that devices that were updated to 1.17 build are facing the same problem. Others who unlocked their device before the update were able to unlock BL. I even tried downgrading to 1.15 and 1.16 but no success till now. Maybe Asus has patched the bootloader with the 1.17 update and as you know bootloaders cannot be downgraded normally and can be fatal for any device. We may be able to unlock when Asus releases unlock app for Z00L.

sziraqui said:
I have been trying to unlock using the official unlock app since seven days. @Rajko said the app works sometimes. Also I have noticed that devices that were updated to 1.17 build are facing the same problem. Others who unlocked their device before the update were able to unlock BL. I even tried downgrading to 1.15 and 1.16 but no success till now. Maybe Asus has patched the bootloader with the 1.17 update and as you know bootloaders cannot be downgraded normally and can be fatal for any device. We may be able to unlock when Asus releases unlock app for Z00L.
Click to expand...
Click to collapse
Can confirm this. I downgraded to the oldest but to no avail.
Is there any way to downgrade the bootloader though? I really am thinking of selling this device for those high-end phones (Samsung S7/HTC 10) if there really is no solution.
Sent from my ASUS_Z00LD using XDA-Developers mobile app

Rizzed said:
Can confirm this. I downgraded to the oldest but to no avail.
Is there any way to downgrade the bootloader though? I really am thinking of selling this device for those high-end phones (Samsung S7/HTC 10) if there really is no solution.
Sent from my ASUS_Z00LD using XDA-Developers mobile app
Click to expand...
Click to collapse
if we don't figure it out within a month I'll also look into a replacement. For now I'll try to live with the stock rom...
btw, any reason you'd go for Samsung/HTC instead of Motorola/OnePlus?

igorrafael said:
if we don't figure it out within a month I'll also look into a replacement. For now I'll try to live with the stock rom...
btw, any reason you'd go for Samsung/HTC instead of Motorola/OnePlus?
Click to expand...
Click to collapse
The HTC looks to be an excellent choice. Their last few devices weren't up to par, and it's cost them dearly. They've stepped their game up with the 10, and I think it'll be the device to put them back in the game.
The Galaxy S7 family speaks for itself.
As for Motorola, I'd avoid them like the plague. They're horrible with updates and are getting sued right now for failing to properly honor their customers warranty claims.
Oneplus is a toss up, IMO. The Oneplus 3 could be a hit or a miss. I'm not sure when it's supposed to drop, but I'd keep my eye on it.

HampTheToker said:
The HTC looks to be an excellent choice. Their last few devices weren't up to par, and it's cost them dearly. They've stepped their game up with the 10, and I think it'll be the device to put them back in the game.
The Galaxy S7 family speaks for itself.
As for Motorola, I'd avoid them like the plague. They're horrible with updates and are getting sued right now for failing to properly honor their customers warranty claims.
Oneplus is a toss up, IMO. The Oneplus 3 could be a hit or a miss. I'm not sure when it's supposed to drop, but I'd keep my eye on it.
Click to expand...
Click to collapse
Interesting, I personally had very good experience with Motorola and have seen a lot of people having trouble with samsung phones.
My view on Samsung is biased though, as I barely consider them android phones. Prejudice aside , I see them as designed for people who want the status of iPhones but want something "like an android".
I hope the OnePlus 3 turns out to be good

igorrafael said:
Interesting, I personally had very good experience with Motorola and have seen a lot of people having trouble with samsung phones.
My view on Samsung is biased though, as I barely consider them android phones. Prejudice aside , I see them as designed for people who want the status of iPhones but want something "like an android".
I hope the OnePlus 3 turns out to be good
Click to expand...
Click to collapse
Well, sorry for saying this, but I personally do not trust any companies from (you know which country). Their phones may pack in very high specifications at very low and attractive prices, but really, there must be a catch, right? (personal opinion)
I live in Singapore and unfortunately, I don't see any Motorola smartphones being sold at any of our major electronics store or even online.
Sent from my ASUS_Z00LD using XDA-Developers mobile app

igorrafael said:
Interesting, I personally had very good experience with Motorola and have seen a lot of people having trouble with samsung phones.
My view on Samsung is biased though, as I barely consider them android phones. Prejudice aside , I see them as designed for people who want the status of iPhones but want something "like an android".
I hope the OnePlus 3 turns out to be good
Click to expand...
Click to collapse
I didn't say Moto makes a bad phone. On the contrary, their phones are usually pretty solid. It's their business practices and weak update support that turns me off, but they undeniably make good phones. Just don't expect to run the latest and greatest Android has to offer a year after release.
My opinion of Samsung is biased as well. My previous device was a Galaxy S4, and I LOVED it. It was a damn good phone that could take whatever I threw at it. And, the dev support...that phone had every ROM and mod you could ever want. The only reasons I didn't stick with Sammy were the price, and I the fact that my Samsung experience had gotten a little stale after three years with a Galaxy S4. Plus, these Zenfone variants dropped when I was ready to upgrade, and they were pretty attractive. I don't regret it for a second. Like I said previously, if Asus would drop ZenUI, I'm certain that the root community would want what they have to offer.
Oneplus is due to release a good device. I have a good feeling that they'll drop that crappy invite system this time around. If they do that and give us another flagship killer, the Oneplus 3 would be more than likely sell like hotcakes.

Does unlocked BL automatically mean root is possible.

I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?

Bubba Fett said:
I've always been a Samsung fan, but this phone is packed with features I like. With samsung , unlocked BL then twrp, then flash SU..done. is LG a little different or is it Nouget that is making the process harder or even not possible? Any thoughts from any LG veterans?
Click to expand...
Click to collapse
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.

lightninbug said:
AFAIK it's Nougat. This is my first LG device, coming from HTC 10. I've had many others, just never LG.
Click to expand...
Click to collapse
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.

Bubba Fett said:
Did you get the phone yet? Try to unlock? I think i saw you involved over at the s7 edge root thread when i was watching that right? The things I'm going to have to get used to is power button and no physical home/back buttons however if root is achieved and maintained through FW updates I think this phone will be the best out there and development for LG should rise.
Click to expand...
Click to collapse
No.. thought I was getting it today via UPS... Guess I was tracking the wrong package lmao (stoner moment)... The G pad X came today instead... Lammmmme!!!

LG blocked fastboot commands since MM so the standard would usually be Unlock BL, flash recovery then flash SU.
But its not the case anymore.
Now its Unlock BL wait till an official.tot or .kdz to be released or leaked from LG, then repack it with root or a recovery and flash via LGUP or LG Tool.

just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.

Z51 said:
just curious, what do you need root for?
phones nowadays come great out of the box. just disable what you dont need.
Click to expand...
Click to collapse
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.

lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.

douger1957 said:
Does someone really need to want to root his phone to be on XDA? There's a whole lot of learning and shared experience going on out in those threads and there's not one rooted V20 to be found.
The fact of the matter is, a lot of people who come to XDA shouldn't be allowed anywhere near an ADB command or a one touch root.
On my short time with the Note 7, XDA showed me that it really wasn't smart to root that phone. Rooting broke too much of the stuff I used, and the developers didn't get enough time to iron out those problems. If they root this phone, I won't be doing it to mine until I see how all of the problems shake out.
Click to expand...
Click to collapse
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!

Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
Amen to that lol! Do you know how long does it take to restore every single app when you dont have titanium backup installed and your device rooted? (i have 113 user apps in my lg g3), you can easily take up to 2 hours installing and setting up. while when you have titanium, you can sit there and drink up your coconut juice while it does everything on its own and everything already set up, and it is pretty quick too. Also, i hate ads. unless the benefit me (that's how i found out about the LG V20 lol) Not to mention that many of the ads out there are either scam or viruses . Also, rooting is the way to really owning your device. a device is not yours until whatever thing you want to do can actually be achieved because you (the owner) wanted to and not because the company wanted to. :good:

I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.

Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
Lol you might as well return it now then. Beucase i doubt it will be done that quick. I mean, i bought this phone because of its great features. And even though i like to root, flash, and all that, well, i have set up my mind in a balanced mode and said "well, chances to get root are 50%, sure i like to root my phone but probably it wont be possible ". To be honest i usually wait about 3 month before buying a new released smartphone because by around that time, they usually have root and have gotten bugs already fixed. But i couldnt resist the offers on this one LOL. so, if it doesnt get root, i will stuck with it for a while anyway.

Amd4life said:
I need root for adblocking and xprivacy , that's it. No root within 15 days, its getting returned.
Click to expand...
Click to collapse
I'm in the exact same boat as you. My V20 is sitting all pretty on my desk. T-14 days before I return it if no root. Been rocking the OnePlus 3 with an awesome ROM since the first Note 7 recall. Absolutely loving it. Got the V20 only because of the screen, camera, and supposedly better sound--all of which are probably marginal upgrades compared to OP3 especially considering it's well over twice the price.

V521 didn't have root until update was released. I grabbed and uploaded the ROM, and soon rooted .dz was there.

Confirmed: Similar to T-Mobile LG G5 there are not flash commands in fastboot to write a new recovery. Will need someone to create a TOT file to get us TWRP and root I think.

confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT=&quot]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
c:\adb>fastboot boot v20.img
downloading 'boot.img'...
OKAY [ 0.700s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.721s
Click to expand...
Click to collapse

lightninbug said:
Are you really on XDA posting this?...What do we need root for???... Maybe head to the T-Mobile forums bro.
Click to expand...
Click to collapse
Don't get your panties in a bunch. It was a simple question. I come on here to make money. I fix phones for a living and I come here to fix what people attempting to root broke and brought to me to fix. If you don't want to root, you don't have to. If you do, then by all means root your phone. No need to be a **** about it.
Sent from my SM-G928V using Tapatalk

Amd4life said:
confirmed that I have unlocked my t-mobile bootloader also. TRY THIS AT YOUR OWN RISK!!!!
booted into fastboot mode by
a) powering down the device
b) putting the cable into the PC USB drive
c) hold down - volume down button, insert USB-C cable into the phone.
d) check the USB drivers in device manager.
e) I manually installed USB driver using the google USB drive from SDK tools 2.2 (LG drivers may also work)
f) cmd, run as administrator, changed directory to my adb folder
g) fastboot oem device, listed my device (so im good to go)
h) [FONT=&quot]fastboot oem unlock (doing such will erase your phone)
I) fastboot getvar unlock[/FONT]
j) fastboot reboot
device boots with security warning (ie bootloader unlocked), boots fine, clean device
went back into fastboot tried to compile a basic TWRP using my v10 TWRP as a basis....fail on my coding skills ( I am still learning)
using command fastboot boot XXX.img
Click to expand...
Click to collapse
Apparently LG disables boot/flash. I'm going to try to get a tmobile TOT file tomorrow. I'm working on updating a TOT extractor tool right now to work it.

Can someone run this:
Code:
fastboot getvar all

Bubba Fett said:
I think that's a good opinion. Mine is I want to be the administrator of my $800 hand computer. Not tmobile. Not LG, Samsung , or anyone else. I bought it. It's mine. If I want to block ads, or change the color of my clock then I should be able to. I agree on waiting for bugs to be fixed, but being able to flash a backup or backed up app is a nice feature. I miss the days where root came easy and we owned the rights to our devices. It's bull5hit!
Click to expand...
Click to collapse
I will most likely root my phone when the time comes. I am not against rooting at all... I rooted all of my phones except the Note 7. What I'm saying is that root isn't for everyone, not everyone should root their phone even if they think it's the thing to do and that I think there's a place at XDA for people who don't want to learn ADB commands.

Potential way to unlock bootloader?

Since we are using engboot, write protection seems to be off, so it appears you can use dd to write to normally write protected partitions such as the bootloaders (ex: "dd if=/sdcard/aboot of=/dev/block/sdd10"). In my testing I was successfully "dd" a backed up aboot (secondary bootloader) partition and also write to the modem partition and have it stick (which means write protection should be off akaik). If you were to "dd" the Chinese bootloaders, you might be able to flash and re-partition onto the Chinese firmware and then use the CROM service to unlock the bootloader from there. I personally don't know too much about this type of stuff and haven't tried to actually "dd" the Chinese bootloader, but for those more knowledgeable, could this potentially work?
Partitions likely needed are:
- rpm (Resource and Power Manager / Primary Bootloader) located at /dev/block/sdd1 (/dev/block/bootdevice/by-name/rpm)
- aboot (AP Bootloader / Secondary Bootloader) located at /dev/block/sdd10 (/dev/block/bootdevice/by-name/aboot)
- xbl (Extended Bootloader) located at /dev/block/sdb1 (/dev/block/bootdevice/by-name/xbl)
- ? located at /dev/block/sdc1
Modifying the bootloader is dangerous and could permanently brick your device. I take no responsibility if you try this and it breaks your device.
Edit 5: Additional Details

qwewqa said:
Since we are using engboot, write protection seems to be off, so it appears you can use dd to write to normally protected partitions (ex: "dd if=/sdcard/aboot of=/dev/block/sdd10"). In my testing I was successfully dd a backed up aboot (secondary bootloader) partition and also write zeros to the modem partition and have it stick (which means write protection should be off). If you were to dd a Chinese bl/ap, you might be able to flash/re-partition onto the Chinese firmware and then use the CROM service to unlock the bootloader from there. I personally don't know too much about and haven't tried to actually dd the Chinese bootloader, but for those more knowledgeable, would this work?
Edit: Modem partition sticks after reboot.
Click to expand...
Click to collapse
@Binary100100 you probably know somebody that knows little bit more about this, tell them to check it out

Magnifik81 said:
@Binary100100 you probably know somebody that knows little bit more about this, tell them to check it out
Click to expand...
Click to collapse
Nope. Don't know anyone specific.

Wish I had the $175 for my insurance deductible, I'd give it a try. All in all, it should work. The hardware is the same.

thescorpion420 said:
Wish I had the $175 for my insurance deductible, I'd give it a try. All in all, it should work. The hardware is the same.
Click to expand...
Click to collapse
Well, if it WORKS, I'm sure the bounty on unlocking the bootloader is a lot higher than $175! ?

DOMF said:
Well, if it WORKS, I'm sure the bounty on unlocking the bootloader is a lot higher than $175!
Click to expand...
Click to collapse
Lets start a thread . . . I am willing to contribute $25.00 :good: into a pool with others here at XDA to the developer who can produce an unlocked bootloader that is rooted with a decent rom that works great and better than stock, something that will fix all of the untold bugs and address the known issues.
Anyone else?

serendipityguy said:
Lets start a thread . . . I am willing to contribute $25.00 :good: into a pool with others here at XDA to the developer who can produce an unlocked bootloader that is rooted with a decent rom that works great and better than stock, something that will fix all of the untold bugs and address the known issues.
Anyone else?
Click to expand...
Click to collapse
$25? Hell think about how much we spend on the phone itself and bill every month.. I'd easily pledge $100 for an unlocked bootloader with twrp support.
That's the 1 thing I don't understand.. this is the most highly sought after phone right now with 0 developer support. I understand the limitations with the locked bootloader but other phones have overcome the same through the works of various motivated individuals. There is no one even interested in trying it seems on ANY carrier forum. Instead we have countless threads with people more interested in getting the nougat update early which will hardly provide anything useful compared to an unlocked bootloader with working root.

serendipityguy said:
Lets start a thread . . . I am willing to contribute $25.00 :good: into a pool with others here at XDA to the developer who can produce an unlocked bootloader that is rooted with a decent rom that works great and better than stock, something that will fix all of the untold bugs and address the known issues.
Anyone else?
Click to expand...
Click to collapse
"Start?" It was started ages ago and it thousands of dollars. https://forum.xda-developers.com/tmobile-s7-edge/how-to/bounty-unlocked-bootloader-s7edge-t3339857

bdvince said:
$25? Hell think about how much we spend on the phone itself and bill every month.. I'd easily pledge $100 for an unlocked bootloader with twrp support.
That's the 1 thing I don't understand.. this is the most highly sought after phone right now with 0 developer support. I understand the limitations with the locked bootloader but other phones have overcome the same through the works of various motivated individuals. There is no one even interested in trying it seems on ANY carrier forum. Instead we have countless threads with people more interested in getting the nougat update early which will hardly provide anything useful compared to an unlocked bootloader with working root.
Click to expand...
Click to collapse
Root right now is just too impractical for most people. I'm still rooted, but for most people it isn't worth the hassle and trade-offs, for many it's worse than stock. I think most people who are really into root probably switched devices. Switching to android N could actually prevent bootloader unlock in this way, unless root for N comes out. That is if this unlock method could actually work, hard to say without anyone experienced in bootloaders and write protection though.

I'd like to find someone with a sm-g9350 to DD a dump of sdd10.

thescorpion420 said:
I'd like to find someone with a sm-g9350 to DD a dump of sdd10.
Click to expand...
Click to collapse
Sdd1 is the primary bootloader, probably also necessary.

Came to the realization that the Chinese bootloader is v2 where all US models are v4. I'd imagine the Chinese nougat update will make it v4, so we wait to try.

Don't want to a be downer or anything but I'm pretty sure you can't just replace the bootloader, even if write protection is off on the Eng kernel. Even if you did replace it you'll have probably bricked your phone.
Sent from my SM-G935T using Tapatalk

dogredwing1 said:
Don't want to a be downer or anything but I'm pretty sure you can't just replace the bootloader, even if write protection is off on the Eng kernel. Even if you did replace it you'll have probably bricked your phone.
Click to expand...
Click to collapse
The thinking is that since the devices are virtually the same hardware wise, there is a chance the bootloader could be replaced. I do agree that there is a good chance of hard bricking though. I haven't done any testing other than apparently successfully dding a backed up version of the same bootloader.

If I wasn't on nougat I would try it if someone posted instructions and devs confirmed the directions are correct..
Sent from my SM-G935T using Tapatalk

I was actually playing with the bootloader, and found this thread when I went to post. I'm going to be pulling fastboot commands also to see if I can find anything interesting. I'm tired of not being able to use a custom kernel

My device is on nougat. Bit I can easily downgrade and test if someone has a rock solid idea. I don't mind bricking as the device has a cracked screen and I have my s6 edge plus to use until the s8 drops...
Sent from my SM-G935T using Tapatalk

Count me in as well!
I have a theory that we can open the BL file in WinRAR and extract the rpm.mbn file from G9350 odin file,
and flash to our device. But I cannot determine which one is for aboot. I have not tested this yet.

aaron007 said:
Count me in as well!
I have a theory that we can open the BL file in WinRAR and extract the rpm.mbn file from G9350 odin file,
and flash to our device. But I cannot determine which one is for aboot. I have not tested this yet.
Click to expand...
Click to collapse
What I know is:
RPM = Resource and Power Manager = Primary Bootloader
ABoot = AP Bootloader = Secondary Bootloader
I believe the boot process is "RPM > ABoot > boot.img (Main OS)", so both the rpm and aboot file would be needed. Also I think the partition layout in the Chinese version is slightly different, so a flash and repartition would be needed after replacing bootloader to actually root. I don't know what the chances success are though, the devices are virtually the same hardware wise, and the Chinese rom with the U.S. bootloader works according to the Verizon fourm, but there is a chance there are other differences what might prevent this from working.
Flippy125 said:
I was actually playing with the bootloader, and found this thread when I went to post. I'm going to be pulling fastboot commands also to see if I can find anything interesting. I'm tired of not being able to use a custom kernel
Click to expand...
Click to collapse
Isn't fastboot disabled on the s7. Also, were your results the same?

qwewqa said:
What I know is:
Isn't fastboot disabled on the s7. Also, were your results the same?
Click to expand...
Click to collapse
Yes, found that out when I started playing with it more. I'm currently reading sdd10 line by line. I did find an entry "Device is unlocked! Skipping verification...". I'm starting to think we need to look into recovery-side exploits. I'm too scared to try and mess with the bootloader too much.
EDIT: If we can find a way to get fastboot working, possibly piggybacking off of Odin, I found a command written in the aboot code 'fastboot oem unlock-go'
EDIT2: Using that command requires some sort of key. May be a dead end.
EDIT3: I'd be willing to test modifying the recovery image to see if it triggers the bootloader's hash checking. If anything, this could lead to writing a custom boot image that would open TWRP.

Rooting ZTE Blade A7 Prime

I've used the search function and found nothing for this phone. I've used Google and found nothing about rooting this exact model.
I'm looking for the technique to root this phone and I'm finding nothing. Has anybody rooted and flashed a Custom ROM/custom recovery on this device and how did you do it?

I just got this phone as well, and I have been looking and also have found nothing for this exact variant. I have tried the usual one-click methods to no avail. Is there any development in the works? If you need a test dummy, let me know. I have several other phones to use as spares, so I am not afraid of a soft brick.

Rooting ZTE Blade a7 Prime
I too can be a test dummy to root this phone. Since Visible is such a hands off company you really need your phone to be rooted to do things for yourself. Currently for some reason my ZTE BLADE A7 Prime can’t send or receive calls and their techs are telling me 3 to 5 business days... counting yesterday and today that’s a week! Ridiculous! The APN settings look off compared to my wife’s phone but you can’t edit the settings.

ZTE Blade prime A7 Visible
I've been having the exact same problem with making and receiving calls also with losing service(for the service prob. Found great n easy solution- till find permanent one-**go to airplane mode in settings turn it on for 30secs to a minute then turn airplane mode back off TAKES SIGNAL FROM 0-4 BARS EVERYTIME AND I CAN GET/MAKE CALLS INSTANTLY ETC AGAIN ?)

Data saver seems to work for resetting connection as well. I too would be interested in rooting. I kinda like the phone, but it does have its issues.

First glance at unlocking bootloader
I just received the phone today. I was excited to see that I could get into developer mode and move the OEM Unlocking icon to allow bootloader unlock... Unfortunately, that's where the excitement ended. The typical fastboot oem unlock and fastboot flashing unlock yielded no results. I then did some research and it would seem MediaTek only implements two oem commands, and unlock is not one of them...
"The bootloader may implement additional, manufacturer-specific commands. These do not follow the usual protocol command format, and they cannot have a payload. Some manufacturers implement a lot of OEM commands, as can be seen here. MediaTek just implements two: fastboot oem p2u on and fastboot oem p2u off, these enable or disable the redirection of Linux kernel messages to the UART."
Will tinker with it some more later since I'm limited with time. Hope someone figures out how to unlock the bootloader and go from there.

Has anybody tried this?
https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
I don't own this phone (yet), so I can't give it a shot myself.

I'm not very familiar with mediatek processors in general, but that looks rather promising with some restrictions... If I have time over the weekend, I'll give that a whirl and report back whether it works or bricks my device

seems lke ts gonna be a long process before were able to fiddle with roms but im atleast glad this is close to stock android.

I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.

virx14 said:
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
Click to expand...
Click to collapse
Ditto here too. Couldn't get it working at first. Turned out I miss read the instructions and put all files in the init.d folder instead od the two files in the bin folder. Then your tip on using the 32bit binary got it working. Thanks.

Anybody figured out a way to change build.prop to make it stick after reboot? I am trying to enable APN editing by modifying /system/build.prop, but whenever I reboot I lose the changes.

/system and the root filesystem are mounted as a kind of RAM Disk. You would have to modify the actual image files (varies depending on partition scheme) and reflash to make things stick. Now, to my knowledge, doing so would require an unlocked bootloader, which currently is not possible with this phone.

wunderdrug said:
/system and the root filesystem are mounted as a kind of RAM Disk. You would have to modify the actual image files (varies depending on partition scheme) and reflash to make things stick. Now, to my knowledge, doing so would require an unlocked bootloader, which currently is not possible with this phone.
Click to expand...
Click to collapse
Looks like we can not add an APN even with root then? It's a bummer.

sasuke33 said:
I just received the phone today. I was excited to see that I could get into developer mode and move the OEM Unlocking icon to allow bootloader unlock... Unfortunately, that's where the excitement ended. The typical fastboot oem unlock and fastboot flashing unlock yielded no results. I then did some research and it would seem MediaTek only implements two oem commands, and unlock is not one of them...
"The bootloader may implement additional, manufacturer-specific commands. These do not follow the usual protocol command format, and they cannot have a payload. Some manufacturers implement a lot of OEM commands, as can be seen here. MediaTek just implements two: fastboot oem p2u on and fastboot oem p2u off, these enable or disable the redirection of Linux kernel messages to the UART."
Will tinker with it some more later since I'm limited with time. Hope someone figures out how to unlock the bootloader and go from there.
Click to expand...
Click to collapse
They removed the fastboot command to unlock the bootloader. I found it out by comparing the similar ZTE Blade 10 and Blade 10 Prime. The Blade 10 non-prime has the unlock command and it works whereas the prime version has the command removed but funnily enough the lock command is still there but is useless. I then looked at the bootloader for the a7 prime and same thing the unlock command is removed from the bootloader. So there isn't much hope for it unless a bypass can be found.

virx14 said:
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
Click to expand...
Click to collapse
+1 to another confirmation that the above works. Root is available, but there are limitations. I cannot install many of the modules from magisk, but this is still a great start. Thanks for the links :good:

I installed the magisk, however, it seems no root permission when I installed Titanium to remove stock apps, it never get root permission.

I was able to add new APN easily to make it work on AT&T 4G LTE data network. Are you saying any reboot of phone will make the newly added APN disappear?

ultrasoul said:
I was able to add new APN easily to make it work on AT&T 4G LTE data network. Are you saying any reboot of phone will make the newly added APN disappear?
Click to expand...
Click to collapse
I was also able to add and APN by just clicking on the "+" icon on the top-right corner of the APN configuration screen. When I inserted by MINT SIM Card (T-Mobile MVNO) there were not default populated APNs, but was able to get everything to work after adding an APN -- even after rebooting.
Big Tip: After entering the APN data and before leaving the data entry screen, make sure that you save the APN or it will not be persisted. Click on the "three dots" menu on the top-right corner and hit the Save menu item.
---------- Post added at 05:49 AM ---------- Previous post was at 05:39 AM ----------
AmazerG said:
I installed the magisk, however, it seems no root permission when I installed Titanium to remove stock apps, it never get root permission.
Click to expand...
Click to collapse
After studying the process a bit, I've come to conclude that this isn't really permanent root. All this does is the equivalent of running a script to gain temporary root after after reboot. This is done very late in the boot process, if you can even call it a part of the boot process since it's really just a user-space application auto-starting.
The modules are probably trying to be instantiated well before the root is made available through the pseudo "init.d" scripts.
It's still nice to have root access using this technique, but its usability is pretty limited. For example, I can't even get AFWall+ to start up, even if I configure it with a startup delay (hoping that it kicks in after temporary root).

So what are the odds we can make this a permanent root using a firehose file and QPST/QFIL? Similar to the Visible R2 phone?