So I'm wondering if any intrepid dev is willing to compile TWRP for our lovely phone. I am willing to contribute to a fund for whoever is able to get a functional version of the recovery.
This is such a nifty phone. The WW version works great in the US, and it'd be nice if we could get full functionality sooner than later.
mrbubs3 said:
So I'm wondering if any intrepid dev is willing to compile TWRP for our lovely phone. I am willing to contribute to a fund for whoever is able to get a functional version of the recovery.
This is such a nifty phone. The WW version works great in the US, and it'd be nice if we could get full functionality sooner than later.
Click to expand...
Click to collapse
Well for starters, we'd need the bootloader unlocked (as per Asus) and a preferably better rooting method to get started. Other than that, you'll be pleased to know that we may end up receiving OFFICIAL TWRP since DeesTroy is planning to get a Zenfone 2!:thumbup: (as mentioned here: http://forum.xda-developers.com/showthread.php?p=60352547)
Sent from the Ace's MB865 using Tapatalk
I thought the bootloader was already unlocked, as you can push system.img via bootloader. Or does the locked bootloader only prevent the changing of the boot.img file?
mrbubs3 said:
I thought the bootloader was already unlocked, as you can push system.img via bootloader. Or does the locked bootloader only prevent the changing of the boot.img file?
Click to expand...
Click to collapse
I don't really have the details on that, I'm only reiterating what was confirmed by a mod on the Zentalk forums that it is indeed locked. It's rather interesting that we can flash through it, but I'm not really experienced in bootloader unlocking enough to tell what's going on.
Sent from the Ace's MB865 using Tapatalk
mrbubs3 said:
So I'm wondering if any intrepid dev is willing to compile TWRP for our lovely phone. I am willing to contribute to a fund for whoever is able to get a functional version of the recovery.
This is such a nifty phone. The WW version works great in the US, and it'd be nice if we could get full functionality sooner than later.
Click to expand...
Click to collapse
Are you sure that the WW version works great since it doesn't support Band 17 (700MHZ) which is mainly used by AT&T?
huzgu444 said:
Are you sure that the WW version works great since it doesn't support Band 17 (700MHZ) which is mainly used by AT&T?
Click to expand...
Click to collapse
I use T-Mobile, so perhaps those limitations do not apply to me. I have not seen anyone reporting on service issues with AT&T at the time of posting.
The difference between a locked and unlocked bootloader is that a locked bootloader only accepts signed packages (packages built with the unique keys from Asus) while an unlocked bootloader will accept packages signed by anyone.
The rooted images are signed by Asus themselves, which lets us flash them through a locked bootloader.
If you push a system.img not signed with Asus' keys your device will not boot.
seshmaru said:
The difference between a locked and unlocked bootloader is that a locked bootloader only accepts signed packages (packages built with the unique keys from Asus) while an unlocked bootloader will accept packages signed by anyone.
The rooted images are signed by Asus themselves, which lets us flash them through a locked bootloader.
If you push a system.img not signed with Asus' keys your device will not boot.
Click to expand...
Click to collapse
That's ^ said by people who never tried it by himself.
Locked bootloader won't boot unsigned kernel images only (you can flash them through fastboot, but won't be able to boot). This includes recovery.img and boot.img. There is no signature in system.img, that's why you can flash pre-rooted system.img an boot.
sorg said:
That's ^ said by people who never tried it by himself.
Locked bootloader won't boot unsigned kernel images only (you can flash them through fastboot, but won't be able to boot). This includes recovery.img and boot.img. There is no signature in system.img, that's why you can flash pre-rooted system.img an boot.
Click to expand...
Click to collapse
Feel free to try and unpack, modify, and pack system.img. Then feel free to attempt to flash it.
Hey, so maybe instead of having a pissing match between superusers/devs, can we perhaps focus on the task of seeing how probable it will be to unlock the bootloader/compile TWRP?
mrbubs3 said:
Hey, so maybe instead of having a pissing match between superusers/devs, can we perhaps focus on the task of seeing how probable it will be to unlock the bootloader/compile TWRP?
Click to expand...
Click to collapse
if asus follows its usual pattern, they'll have a bootloader unlock tool released eventually
seshmaru said:
Feel free to try and unpack, modify, and pack system.img. Then feel free to attempt to flash it.
Click to expand...
Click to collapse
I did it already. Works fine. I've uploaded pre-rooted system.img in this topic: http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
What i'm doing wrong?
lyeith said:
if asus follows its usual pattern, they'll have a bootloader unlock tool released eventually
Click to expand...
Click to collapse
I hope so. I am itching to make this my DD. After that, I would need TWRP, a more robust kernel, and a nifty protective case to make me firmly comfortable. Then I say au revoir to my Moto G 2014.
huzgu444 said:
Are you sure that the WW version works great since it doesn't support Band 17 (700MHZ) which is mainly used by AT&T?
Click to expand...
Click to collapse
I'm in Dallas on At&t and no complaints here. My girl is in PR at the moment and all good too. So I'd say check your zone and what bands it runs thru.
lordpipa said:
I'm in Dallas on At&t and no complaints here. My girl is in PR at the moment and all good too. So I'd say check your zone and what bands it runs thru.
Click to expand...
Click to collapse
Are you getting 4g or 4gLTE and which firmware are you using. My Z00A is not getting 4gLTE atm on ATT in dallas (plano), only getting 4g. Currently connected on Band 5 not band 17
yeah Im getting 4gLTE but im not running stock firmware.
Related
Just saw it on the verizon note 4 forum. How come no one is posting about i? Can it be used on N910A variant?
Well.. they have been talking about it.. for over 2 weeks actually.
And no, as of right now it cannot be used for att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
atx84 said:
Well.. they have been talking about it.. for over 2 weeks actually.
And no, as of right now it cannot be used for att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes i have converted to Developer mode, unlocked rooted retail verizon note4 as of now only works for that phone. I also have a retail verizon edge and there is no unlock yet for that....
bigbooker455 said:
Yes i have converted to Developer mode, unlocked rooted retail verizon note4 as of now only works for that phone. I also have a retail verizon edge and there is no unlock yet for that....
Click to expand...
Click to collapse
So the N910A still is no go. What a bummer!
Is that because at&t left out the developer mode?
I hate at&t so much never in the history of stupidity has anyone screwed up a perfectly well manufactured item as they do.
Remember when they were the only company to add the PMA standard of wireless charging on the lumia 1520?
Man I hope someone fired that idiot. LOL
cxyjordan said:
So the N910A still is no go. What a bummer!
Click to expand...
Click to collapse
YUP!
adambomb_13 said:
Is that because at&t left out the developer mode?
I hate at&t so much never in the history of stupidity has anyone screwed up a perfectly well manufactured item as they do.
Remember when they were the only company to add the PMA standard of wireless charging on the lumia 1520?
Man I hope someone fired that idiot. LOL
Click to expand...
Click to collapse
I was reading note4 AT&T thread and found this, like i said do not take any updates!
AT&T released an update with security enhancements yesterday, any word about this and how this affects us?
I am not sure. I know that I have my OTA blocked; however, I too find it interesting that a sudden security update is released now about two weeks after the Verizon hack is discovered and rolled out. It is stuff like this that tells me that their devs know something that we have yet to discover.
This may work for you AT&T guys.......
Plus, the tools to finish this are already public.
You compile SamsungCID (in a KitKat tree), and use it to change the CID using temp root, then you can flash the corresponding developer edition aboot via ODIN. The reason I haven't release it is that there is an easier method.
Ryan has a slightly better method, he extracts the CID blob from the developer edition aboot, and places it into the current aboot partition, then changes the CID to match the blob. This allows us to convert without needing to be on the developer edition aboot's increment version to unlock.
I have opted to not release the former method, as it could result in people who don't read thoroughly enough bricking due to flashing the old aboot on a newer increment.
bigbooker455 said:
This may work for you AT&T guys.......
Plus, the tools to finish this are already public.
You compile SamsungCID (in a KitKat tree), and use it to change the CID using temp root, then you can flash the corresponding developer edition aboot via ODIN. The reason I haven't release it is that there is an easier method.
Ryan has a slightly better method, he extracts the CID blob from the developer edition aboot, and places it into the current aboot partition, then changes the CID to match the blob. This allows us to convert without needing to be on the developer edition aboot's increment version to unlock.
I have opted to not release the former method, as it could result in people who don't read thoroughly enough bricking due to flashing the old aboot on a newer increment.
Click to expand...
Click to collapse
Now that sounds feasible..... if i had all the tools and a full set of instructions i would love to give it a try in a heart beat.......
giga8547 said:
Now that sounds feasible..... if i had all the tools and a full set of instructions i would love to give it a try in a heart beat.......
Click to expand...
Click to collapse
Make that two of us, I am typically very thorough when I read instructions and have a way of thinking outside the box when looking at issues. Not to mention, if we can unlock the darn bootloader on these things, many of us could do a MM OS update from a more unbloated and pure form.
bigbooker455 said:
This may work for you AT&T guys.......
Plus, the tools to finish this are already public.
You compile SamsungCID (in a KitKat tree), and use it to change the CID using temp root, then you can flash the corresponding developer edition aboot via ODIN. The reason I haven't release it is that there is an easier method.
Ryan has a slightly better method, he extracts the CID blob from the developer edition aboot, and places it into the current aboot partition, then changes the CID to match the blob. This allows us to convert without needing to be on the developer edition aboot's increment version to unlock.
I have opted to not release the former method, as it could result in people who don't read thoroughly enough bricking due to flashing the old aboot on a newer increment.
Click to expand...
Click to collapse
We should be able to change the CID on any Note 4 so I don't see why this wouldn't work. Don't we need root to copy the aboot? My understanding was that the kingroot method doesn't work anymore after an AT&T update. It is now soft bricking phones. I am wondering if the security update could be removed by flashing the original 5.1.1 or maybe even 5.0.1.
dkmac said:
Make that two of us, I am typically very thorough when I read instructions and have a way of thinking outside the box when looking at issues. Not to mention, if we can unlock the darn bootloader on these things, many of us could do a MM OS update from a more unbloated and pure form.
Click to expand...
Click to collapse
I don't own a AT&T version of the Note4, can you roll back?
bigbooker455 said:
I don't own a AT&T version of the Note4, can you roll back?
Click to expand...
Click to collapse
Unfortunatly, once you are on 5.1.1 you are stuck there. I believe that all attempts to roll back to 4.4.4 ended either in failure or a bricked device. To complicate matters more, after king root released I believe version 4.2 it became successful and unstable. Once the phone reboots automatically or manually, you cannot make it past the boot screen. You get a display that tells you to return to an att store. If you root now, you have to reboot via Odin to get the phone up and going again. With all that said, king root is stable to use, but only for a few minutes before unstability and then ultimately reboot. I always have faith in the possible and know that there is and will be a way around all this mess for a permanent unlock bootloader and root.
dkmac said:
Unfortunatly, once you are on 5.1.1 you are stuck there. I believe that all attempts to roll back to 4.4.4 ended either in failure or a bricked device. To complicate matters more, after king root released I believe version 4.2 it became successful and unstable. Once the phone reboots automatically or manually, you cannot make it past the boot screen. You get a display that tells you to return to an att store. If you root now, you have to reboot via Odin to get the phone up and going again. With all that said, king root is stable to use, but only for a few minutes before unstability and then ultimately reboot. I always have faith in the possible and know that there is and will be a way around all this mess for a permanent unlock bootloader and root.
Click to expand...
Click to collapse
I feel you!
bigbooker455 said:
I feel you!
Click to expand...
Click to collapse
Yea, that's why I have been looking for the info that you were talking about. I want to see what I could do to help breath new life back into our phones.
Hello, I'm new
I'm not sure if this is the right place, I felt a discussion area was an okay place to share and discuss my findings
I'm working with the Boost Mobile Motorola E4, the contents to this thread will relate solely to the Boost E4
Bootloader Unlocking
Unlocking the E4's bootloader was very simple through Motorola's website, it is for certain unlocked
After unlocking the bootloader I got the bad key screen but in my experience that's normal
You can verify that your bootloader is unlocked by using fastboot or checking the Developer Options
Rooting
Other people claim to have success with it, I have not yet had that success Just flash Magisk 13.1 after flashing the verity zip, don't bother with anything else, root will work first try. If you tried another root method, you will have to restore with the method in post #2 before it will work without giving the error.
After flashing the superuser zip and the verity zip, I wasn't led to a successful root I instead downloaded SuperSU-v2.82-201705271822 and flashed that after the verity zip and i was able to reach home menu
I tried flashing Chainfire's SuperSU zip but the device stuck at the boost mobile logo, I will try again after I can get back to stock and do the processes over again and find a way to have 100% success each time Downloaded a new version SuperSU-v2.82-201705271822 as noted above and i was able to fully boot
The issue now is that SuperSU app isnt detecting root but Terminal is gaining root, I'm going to try reinstalling app from the market. I got the SU Binary Occupied error, going to try to downgrade it to 2.79 and see how that goes. It didn't work for me, now it says improperly installed.. Going to try something else. It's 1:55AM August second, taking a small break from the root, at least I got other things figured out for now.
verity zip link (flash first): https://www.androidfilehost.com/?fid=24459283995297893
Stock Resources
Sprint 7.1.1 stock RSD file: https://androidfilehost.com/?fid=673368273298975628
-update- I added the stock RSD file to the list, going to be doing some pulls of stock files for us to work with when I can.
I'm going to try to collect as much information as I can about this device and provide as much detail as possible
NOTE: The below IS NOT Boost Mobile stock, it's sprint will update when I figure out Boost Stock
The sprint stock does fully work with the Boost Mobile device, LTE/data services seems to not work until you do a Factory Reset (in settings). ##72786# didn't work. It is now working for me fully after the factory reset from settings. The boost apps automatically install after the factory reset and after the celluar setup on first boot.. My Boost, etc.
After a few times of flashing and re-setup I've ended up with HFA error 701 which asks me to contact service provider to configure the device for service. Fixed by turning phone off for 20 minutes to an hour and the activation processed correctly.
If your experience differs, let us know!
Restoring to Stock
Install Motorola Drivers
Download RSDlite v6.2.4: http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Download the Sprint firmware file: https://androidfilehost.com/?fid=673368273298975628
Rename the zip to sperry.zip, the reason for this is to avoid the long file name error in RSD in some locations
Let the flashing process complete
Some people reported RSD not working in Windows 10, this is not fully true, install all moto and android drivers and it will show up fine as seen in below image
http://imgur.com/a/vdQxG
Thanks!,
rootjunky for RSD mirror
moto firmware team for the e4 stock 7.1.1
Have you check if this phone have gsm bands?
USA or International Variant?
zoofie666 said:
Hello, I'm new
I'm not sure if this is the right place, I felt a discussion area was an okay place to share and discuss my findings
I'm working with the Boost Mobile Motorola E4, the contents to this thread will relate solely to the Boost E4
Bootloader Unlocking
Unlocking the E4's bootloader was very simple through Motorola's website, it is for certain unlocked
After unlocking the bootloader I got the bad key screen but in my experience that's normal
You can verify that your bootloader is unlocked by using fastboot or checking the Developer Options
Rooting
Other people claim to have success with it, I have not yet had that success Just flash Magisk 13.1 after flashing the verity zip, don't bother with anything else, root will work first try. If you tried another root method, you will have to restore with the method in post #2 before it will work without giving the error.
After flashing the superuser zip and the verity zip, I wasn't led to a successful root I instead downloaded SuperSU-v2.82-201705271822 and flashed that after the verity zip and i was able to reach home menu
I tried flashing Chainfire's SuperSU zip but the device stuck at the boost mobile logo, I will try again after I can get back to stock and do the processes over again and find a way to have 100% success each time Downloaded a new version SuperSU-v2.82-201705271822 as noted above and i was able to fully boot
The issue now is that SuperSU app isnt detecting root but Terminal is gaining root, I'm going to try reinstalling app from the market. I got the SU Binary Occupied error, going to try to downgrade it to 2.79 and see how that goes. It didn't work for me, now it says improperly installed.. Going to try something else. It's 1:55AM August second, taking a small break from the root, at least I got other things figured out for now.
verity zip link (flash first): https://www.androidfilehost.com/?fid=24459283995297893
Stock Resources
Sprint 7.1.1 stock RSD file: https://androidfilehost.com/?fid=673368273298975628
-update- I added the stock RSD file to the list, going to be doing some pulls of stock files for us to work with when I can.
I'm going to try to collect as much information as I can about this device and provide as much detail as possible
If you would like me to test anything you can hit me up on Discord: Zoofie#6780 and we can brainstorm
Click to expand...
Click to collapse
Do you have the USA or international variant of the phone? The only bootloader unlocking guide I've found was for the international variant.
Mensarius said:
Do you have the USA or international variant of the phone? The only bootloader unlocking guide I've found was for the international variant.
Click to expand...
Click to collapse
Read the root thread
@zoofie666 were you able to actually flash the moto g5 twrp or did you just boot it? I can get it to boot with fastboot but I get a not signed or corrupt error when trying to flash it.
amarc78 said:
@zoofie666 were you able to actually flash the moto g5 twrp or did you just boot it? I can get it to boot with fastboot but I get a not signed or corrupt error when trying to flash it.
Click to expand...
Click to collapse
You can only boot it
mendelgordon said:
You can only boot it
Click to expand...
Click to collapse
Yeah, I came to that conclusion. Just read it elsewhere also. I'm going to see what I can do about building twrp.
is it possible to take backup of Moto E4 stock rom with RSD lite ?
kartik verma said:
is it possible to take backup of Moto E4 stock rom with RSD lite ?
Click to expand...
Click to collapse
Not sure, but you can do so by booting the Moto G 5 twrp with fastboot. Restoring works also.
amarc78 said:
Not sure, but you can do so by booting the Moto G 5 twrp with fastboot. Restoring works also.
Click to expand...
Click to collapse
For the international variant?
mendelgordon said:
For the international variant?
Click to expand...
Click to collapse
I have the Boost Mobile variant.
Is there anyone with the Boost Mobile variant that made a working system and boot backup? If so, could you please upload it for me? Mine got corrupted somehow and won't restore.
@amarc78 You should be able to use the Sprint firmware posted by zoofie666 - Boost is Sprint's prepaid brand.
The weirdness with the activation on Sprint/Boost seems to be normal, because I had trouble with two phones recently. The first was a retail unlocked e4 (to be used on Sprint), done before rooting, and activated at a Sprint corporate store last week by a rep who had trouble. The second phone was a retail unlocked Moto g4 Play (also to be used on Sprint), that I rooted first, got the SIM and back-end computer part taken care of by a rep at the same store yesterday, and did the rest myself.
hitokage004 said:
@amarc78 You should be able to use the Sprint firmware posted by zoofie666 - Boost is Sprint's prepaid brand.
Click to expand...
Click to collapse
Yeah, I know all about that. I've already made a stock rom zip with sprint firmware but I want Boost so I can make a zip for that.
Sent from my LGLS755 using XDA Labs
I can provide a backup of system but already rooted / disabled dm verity before I took the backup so /boot you'd have to snag the stock kernel, let me know if you want the nandroid tho.
CodyF86 said:
I can provide a backup of system but already rooted / disabled dm verity before I took the backup so /boot you'd have to snag the stock kernel, let me know if you want the nandroid tho.
Click to expand...
Click to collapse
Dang bro, you pop up everywhere I go around here, lol. Remember me from the moto g helping getting data on cm? Your the one who posted the nasa gif when we got it right? Anyway, I would gladly take what you have rooted or not, and any other imgs you would be so kind to provide me with. I was about to buy another now that they're $20 cheaper than when I got my first. I knew that would happen. I wanted to get my wife one anyway. I was a dumb ass and ran a flash all script for sprint stock firmware and forgot to remove everything but the system sparse chunks. So now I really need full stock firmware. Thanks a lot for responding man!
amarc78 said:
Dang bro, you pop up everywhere I go around here, lol. Remember me from the moto g helping getting data on cm? Your the one who posted the nasa gif when we got it right? Anyway, I would gladly take what you have rooted or not, and any other imgs you would be so kind to provide me with. I was about to buy another now that they're $20 cheaper than when I got my first. I knew that would happen. I wanted to get my wife one anyway. I was a dumb ass and ran a flash all script for sprint stock firmware and forgot to remove everything but the system sparse chunks. So now I really need full stock firmware. Thanks a lot for responding man!
Click to expand...
Click to collapse
I member..... 5.1 for falcon was a trial.... imma be getting this device next month. Love seeing the future happening before my eyes
SykkNyzz said:
I member..... 5.1 for falcon was a trial.... imma be getting this device next month. Love seeing the future happening before my eyes
Click to expand...
Click to collapse
Hey, don't you have a LG volt?
Hello guys, i have two questions:
a) after you unlock bootloader on this device, is it possible to flash the non boost (international e4) rom on it? if so, have you done it?
b) i used to have a moto e2 from boost mobile (xt1526) and did this with the unlocked international e2 rom (xt1527) and i was able to use my gsm networks with it as i dont live in the U.S and CDMA bands dont work in my country, would it be possible with this device too? Because GSM bands are embeded in snapdragon chipsets, so flashing a stock unlocked firmware should make it work, but i want to know if you have tried it
It's forcibly locked. Just curious if that's likely to be changed anytime soon.
I know they can.. When HTC opened their devices to unlocking the bootloader they did it with a flashable update.. And we already know the rest of them are unlockable, so I don't think it would be that hard.. However whether it was an oversight or intended, I don't know. I've tried posting on there official forums and tweeted them, but seen no response to either. Hopefully someone else has better luck getting a reply. I'd really like to see it since they have aosp code for their other devices.
I was thinking about this and not sure if it would work.. I'm no developer by far.. But what if we got the official images for the g3223 from Sony site and flashed those.. Would the bootloader still be locked? I know the images contain everything (bootloader, radio, and system) so if we we got the US g3223 images and flashed them,wouls it work? Or even a non-freedom image (original direct from Sony Canada)?
mikeandjaimie said:
I was thinking about this and not sure if it would work.. I'm no developer by far.. But what if we got the official images for the g3223 from Sony site and flashed those.. Would the bootloader still be locked? I know the images contain everything (bootloader, radio, and system) so if we we got the US g3223 images and flashed them,wouls it work? Or even a non-freedom image (original direct from Sony Canada)?
Click to expand...
Click to collapse
i doubt a non-freedom image would work. that would be scandalous if it did work tho. freedom hasn't deployed anything since the June updates..................................................
bromanbro said:
It's forcibly locked. Just curious if that's likely to be changed anytime soon.
Click to expand...
Click to collapse
I got the bootloader code right from Sony along with videos & flash program
SRSCAA said:
I got the bootloader code right from Sony along with videos & flash program
Click to expand...
Click to collapse
For the Canadian g223 model?
I have my bootlock unlock code from Sony. But without fastboot access we are screwed. Freedom branded G3223 have gotten the shaft. Hopefully some method gets released for now it's all a waiting game.
bromanbro said:
For the Canadian g223 model?
Click to expand...
Click to collapse
Yes for tge G3223
SRSCAA said:
Yes for tge G3223
Click to expand...
Click to collapse
What flash program is this? share some bootloader unlock results when you have a chance. Thanks! :good:
poy said:
What flash program is this? share some bootloader unlock results when you have a chance. Thanks! :good:
Click to expand...
Click to collapse
This.
Hello Folks!
As soon as I got the tablet I spent a good few hours looking around for the combo firmware to start looking for exploits so figured I would provide you guys with a link to the firmware for free
It was quite funny actually, after I soft bricked and got stuck in a boot loop I realized I couldn't find any stock firmware anywhere either haha, so I spent a few hours looking for that as well.
I have the Verizon variant, I am not sure if it will work on other USA variants or not as I have no way of trying. With that being said, below will be the links. I will provide a rev1 combination firmware and a rev1 stock firmware as well as a link to a modified ODIN for easy flashing!
And with all that being said, the combo firm is good to bypass FRP. You can enable the oem unlock switch but other than removing FRP it is useless as of right now. You can however, mix and match the firmware unlike my S9+. I am currently on stock firmware with a permissive boot.img for example.
If you got questions or need help, well, you probably shouldn't be downloading anything or flashing haha. But I will try to help when I have time. I do not have any current plans to keep this thread going with updated filese as I had to pay for these. If I can find em free moving forward I will re-upload if I can but I typically stay on the lowest rev/firmware I can until I find a root method
T837VVRU1ARG4 COMBINATION FIRMWARE/FACTORY BINARY
T837VVRU1ARGG STOCK FIRMWARE
MODDED ODIN v3.13.1
If you feel like buying me a beer...
What is the main benefit of this?
In the q&a section someone wrote it is readily rootable with Magisk. Is that not the case?
@elliwigy
Is there any firmware for the unlocked LTE snapdragon. I got the Verizon version but it's not playing nice with AT&T. Any ideas? Maybe flashing the unlocked firmware would help.
apascual89 said:
@elliwigy
Is there any firmware for the unlocked LTE snapdragon. I got the Verizon version but it's not playing nice with AT&T. Any ideas? Maybe flashing the unlocked firmware would help.
Click to expand...
Click to collapse
to my knowledge no.. different models.. not sure if there is a U version or if the sammy one is lte capable
apascual89 said:
@elliwigy
Is there any firmware for the unlocked LTE snapdragon. I got the Verizon version but it's not playing nice with AT&T. Any ideas? Maybe flashing the unlocked firmware would help.
Click to expand...
Click to collapse
I think it's just the tablet, my Verizon one isn't playing nice with my Verizon service. Constantly not switch towers and losing service when full service is available. Or it's a tower problem but my note8 doesn't do it when my tablet does
Thanks for this, have been looking for a couple days for the build.prop file.
If you get permissive boot, try adb verity disable and mod through push pull adb style like we did on Att note 5
Will this work on sm-t817v?
pujuois said:
Will this work on sm-t817v?
Click to expand...
Click to collapse
lol no.. its for t837v.. the 817 is a completely different tablet.. i dont even think there is an 817v.. u sure its not a 818v?
either way, search the internet and you will b rewarded i am sure
TechNyne66 said:
If you get permissive boot, try adb verity disable and mod through push pull adb style like we did on Att note 5
Click to expand...
Click to collapse
its adb disable-verity but no, doesnt work as its not userdebug..
combo firmware are always permissive boots..
i am going to mess with it some more tonight
elliwigy said:
lol no.. its for t837v.. the 817 is a completely different tablet.. i dont even think there is an 817v.. u sure its not a 818v?
either way, search the internet and you will b rewarded i am sure
Click to expand...
Click to collapse
I actually had a 817v. They called it the pro version. It was just an updated version at the time.
OEM Unlock
I have the T837V and would like to ODIN flash your files, but as you know there is no OEM unlock in the Developer Options on this tablet. Are you saying that you can flash these files without enabling the OEM unlocking?
I would like to install TWRP, but I believe this is not possible without enabling the OEM unlock. Do you know if this is true?
Thanks
gene5522 said:
I have the T837V and would like to ODIN flash your files, but as you know there is no OEM unlock in the Developer Options on this tablet. Are you saying that you can flash these files without enabling the OEM unlocking?
I would like to install TWRP, but I believe this is not possible without enabling the OEM unlock. Do you know if this is true?
Thanks
Click to expand...
Click to collapse
there is no unlocking the bl so no twrp is possible..
you can however flash T837V/A/P/T/T1/R4/R7/W firmwares using modified odin
elliwigy said:
there is no unlocking the bl so no twrp is possible..
you can however flash T837V/A/P/T/T1/R4/R7/W firmwares using modified odin
Click to expand...
Click to collapse
@elliwigy any idea what I could flash on a T835C without breaking Knox? Do you think I could flash a T835N or T835 no suffix ROM with modified Odin?
philow said:
@elliwigy any idea what I could flash on a T835C without breaking Knox? Do you think I could flash a T835N or T835 no suffix ROM with modified Odin?
Click to expand...
Click to collapse
not sure.. i dont really look at other region devices
Sent from my SM-N960U using Tapatalk
elliwigy said:
there is no unlocking the bl so no twrp is possible..
you can however flash T837V/A/P/T/T1/R4/R7/W firmwares using modified odin
Click to expand...
Click to collapse
Forgive my apparent noobishness but what exactly will that do? Looking for a way to root and wanna know if u have found something I haven't.
Flash firm then what? Does it make OEM show or what? I just happen ta have the most difficult version of the tab S4 which is SM-T837V
Tybirdy9 said:
Forgive my apparent noobishness but what exactly will that do? Looking for a way to root and wanna know if u have found something I haven't.
Flash firm then what? Does it make OEM show or what? I just happen ta have the most difficult version of the tab S4 which is SM-T837V
Click to expand...
Click to collapse
I am currently working on a root method with the N9 but it should also work on Tab S4 once all is said and done. I actually found the exploit I use on the Tab S4 originally before I started workin the N9. Nothing is released yet as so far have only gained root on S9 Exynos and I am currently super bricked and waiting for a device replacement lol
Flashing other carrier firmware won't help you unlock any bootloaders or anything nor will it necessarily help you root. Only benefit I can see really in flashing other carrier firmware is say if you have an sim unlocked tablet (we'll say it's a Verizon tablet) and you want to use it on say Sprint. You can flash the Sprint software in ODIN and everything should work. It would be like you purchased the tablet from Sprint essentially.
elliwigy said:
I am currently working on a root method with the N9 but it should also work on Tab S4 once all is said and done. I actually found the exploit I use on the Tab S4 originally before I started workin the N9. Nothing is released yet as so far have only gained root on S9 Exynos and I am currently super bricked and waiting for a device replacement lol
Flashing other carrier firmware won't help you unlock any bootloaders or anything nor will it necessarily help you root. Only benefit I can see really in flashing other carrier firmware is say if you have an sim unlocked tablet (we'll say it's a Verizon tablet) and you want to use it on say Sprint. You can flash the Sprint software in ODIN and everything should work. It would be like you purchased the tablet from Sprint essentially.
Click to expand...
Click to collapse
Thanks for the quick reply. I really wanna rid myself of bloatware and unwanted ram usage. I mean really 4gigs for a so called productivity device. I'm sure u understand
Welp here's to a hopeful outcome
837T firmware
elliwigy said:
Hello Folks!
As soon as I got the tablet I spent a good few hours looking around for the combo firmware to start looking for exploits so figured I would provide you guys with a link to the firmware for free
It was quite funny actually, after I soft bricked and got stuck in a boot loop I realized I couldn't find any stock firmware anywhere either haha, so I spent a few hours looking for that as well.
I have the Verizon variant, I am not sure if it will work on other USA variants or not as I have no way of trying. With that being said, below will be the links. I will provide a rev1 combination firmware and a rev1 stock firmware as well as a link to a modified ODIN for easy flashing!
And with all that being said, the combo firm is good to bypass FRP. You can enable the oem unlock switch but other than removing FRP it is useless as of right now. You can however, mix and match the firmware unlike my S9+. I am currently on stock firmware with a permissive boot.img for example.
If you got questions or need help, well, you probably shouldn't be downloading anything or flashing haha. But I will try to help when I have time. I do not have any current plans to keep this thread going with updated filese as I had to pay for these. If I can find em free moving forward I will re-upload if I can but I typically stay on the lowest rev/firmware I can until I find a root method
I was wondering if i could flash firmware for my 837T for tobile to work on AT&T? I understand how to work odin etc, i just was not clear on the software variants and their capabilities.......
thanks
chris
Click to expand...
Click to collapse
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.