[GUIDE][DISCUSSION] A2017U Firmware on A2017G - ZTE Axon 7 Guides, News, & Discussion

First of all,
all this was performed on a bootloader locked unbranded A2017G shipped with B05 bought some days ago in the german electronic market Saturn.
I can't guarantee that your device will react the same way to A2017U firmware as mine did.
So all actions you perform on your device happen under your responsibility
​
In the following I collected some information on how to flash A2017U's firmware on A2017G.
Requirements:
- Working adb environment
- A2017G
- Computer
- At least 4gb sdcard
- USB-C Cable
Guide
BACKUP YOUR DEVICE BEFORE CONTINUING (/data will be wiped!)
1. Download needed files.
2. Put ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip on an external sdcard
3. Install Qualcomm drivers with WWAN option
4. Make sure everything is backed up and power off your device
5. Press volume down and power key to boot your phone to FTM Mode
6. Connect it to your computer and reboot it to edl using
Code:
adb reboot edl
7. Determine port number from device manager
9. Extract TWRP recovery.img next to axon7backup.exe
10. Flash TWRP using cmd and axon7backup.exe
Code:
axon7backup.exe -p *your port* -r
11 Unplug your device and hold power and volume up
12. In TWRP wipe data and cache
13. Flash ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip from your external sdcard
14. Reboot and enjoy
More info on points 3 to 8
Downloads
EDL Drivers from @tenfar
http://d-h.st/35tx
TWRP from @tenfar:
http://d-h.st/dgWW
axon7backup.exe from @tenfar
http://d-h.st/Ienb
ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip from @DrakenFX
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Bugs
- Dual-SIM settings crashing (Dual-SIM functionality is said to be working)
Code:
11-06 18:21:07.745 2334 2334 E guojingdong: case=4Preference mIsIndicator=true
11-06 18:21:07.745 2334 2334 E guojingdong: Preference attr=3 a.getIndexCount()=511-06 18:21:07.935 914 982 E ModemAPI: qmi_vs_client_send_msg_sync returned error -45
11-06 18:21:07.935 914 982 E ModemAPI: modem_read_efs, exit result 0
11-06 18:21:07.935 914 982 E ModemService_D: modem_service_response_send_succeed_response error : out of max data size
- Missing locales (workaround it by changing your locale with this app https://play.google.com/store/apps/details?id=sightidea.com.setlocale)
- You tell me
Differences between A2017U and A2017G firmware
- US Version has optional notification bell
- US Version has fixed 1440p playback
- EU Version has the option to start apps at specified fingerprints
- EU Version has interchangable fonts
- EU Version has "Assertive display" (Maybe US Version has it too but there is no settings option to turn it on or off)
I will keep this updated as discussion in this thread goes on
Assorted, other information + Back to A2017G
About OTA:
You will probably recieve them as your device seems no different to ZTE servers than a legitimate A2017U
But I really wouldn't recommend applying these as they sometimes bundle bootloader files with them and we don't know if these will work on A2017G.
Just wait for @DrakenFX or someone else to create a flashable zip with boot and system only
Back to A2017G:
Just wipe data/cache and flash the flashable zip for B03 from @DrakenFX in TWRP
http://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Then apply B05 by OTA or downloaded update.zip on external sdcard.
Sources/Thanks
Thanks to @tenfar for TWRP and the tool to flash it
http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Thanks to @DrakenFX for the A2017U stock images
http://forum.xda-developers.com/showpost.php?p=68873482

Can you please upload the file if we want to return back to stock B05.
It will be very helpful.
Even take some time to do that.(you can do in the next couple of days)
Thanks for the guide also.
Sent from my iPad using Tapatalk

paatha13 said:
Can you please upload the file if we want to return back to stock B05.
It will be very helpful.
Even take some time to do that.(you can do in the next couple of days)
Thanks for the guide also.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Updated OP with according information
Regards,
mischa_martin

Well done! this will probably help a lot of the people who complain about the european ZTE support!
I will personally wait for one more update and if I don't like it I will probably switch to the US software too!
One question: Does this include the better audio performance (louder sounds etc.) like some US users reported?
Cheers

Thank you so much!

How exactly go into adb environments?
What step do we need to do within windows?
Sent from my iPad using Tapatalk

paatha13 said:
How exactly go into adb environments?
What step do we need to do within windows?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2317790

Well I'm having trouble with Qualcomm drivers.
Not recognize by windows.
I try it second time after uninstalling it but again nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my iPad using Tapatalk

paatha13 said:
Well I'm having trouble with Qualcomm drivers.
Not recognize by windows.
I try it second time after uninstalling it but again nothing.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Did you put your phone into FTM mode?
EDIT:
No, you have to install adb drivers too

Hmmm, would like to switch to the US firmware too but what's with the Dual-SIM not working?...

Abiram26 said:
Hmmm, would like to switch to the US firmware too but what's with the Dual-SIM not working?...
Click to expand...
Click to collapse
Code:
11-06 18:21:07.745 2334 2334 E guojingdong: case=4Preference mIsIndicator=true
11-06 18:21:07.745 2334 2334 E guojingdong: Preference attr=3 a.getIndexCount()=511-06 18:21:07.935 914 982 E ModemAPI: qmi_vs_client_send_msg_sync returned error -45
11-06 18:21:07.935 914 982 E ModemAPI: modem_read_efs, exit result 0
11-06 18:21:07.935 914 982 E ModemService_D: modem_service_response_send_succeed_response error : out of max data size
Do you understand what is going on here?
No?
Me neither

mischa_martin said:
Did you put your phone into FTM mode?
EDIT:
No, you have to install adb drivers too
Click to expand...
Click to collapse
Ok drivers installed successfully both Qualcomm and adb.
Now I'm in cmd.
This is my port.
And now I'm here.
What exactly do I write?
Sent from my iPad using Tapatalk

Does it work with A2017?

paatha13 said:
Ok drivers installed successfully both Qualcomm and adb.
Now I'm in cmd.
This is my port.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Just read @tenfar 's thread or my instructions.
Extract the TWRP recovery.img next to the axon7backup.exe and open an cmd window in which you execute the given command.

mischa_martin said:
Just read @tenfar 's thread or my instructions.
Extract the TWRP recovery.img next to the axon7backup.exe and open an cmd window in which you execute the given command.
Click to expand...
Click to collapse
TWRP is ISO file when extracting it.
Sent from my iPad using Tapatalk

paatha13 said:
TWRP is ISO file when extracting it.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Nooo put that recovery.img file next to the exe and execute the command

paatha13 said:
TWRP is ISO file when extracting it.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
axon7root-a2017g-b03.zip
In this file, there is the proper recovery.img next to boot.img and axon7root app itself.
Abiram26 said:
Hmmm, would like to switch to the US firmware too but what's with the Dual-SIM not working?...
Click to expand...
Click to collapse
Dual SIM is working but the settings. :cyclops: I have my main SIM in tray 1 using for calls+data+messaging and my SIM2 is in the 2nd slot, I'm just answering calls from work. If you need any special setup, you'll be in trouble.

thefiqs said:
axon7root-a2017g-b03.zip
In this file, there is the proper recovery.img next to boot.img and axon7root app itself.
Dual SIM is working but the settings. :cyclops: I have my main SIM in tray 1 using for calls+data+messaging and my SIM2 is in the 2nd slot, I'm just answering calls from work. If you need any special setup, you'll be in trouble.
Click to expand...
Click to collapse
But I'm on B05.
Does it matter if I use B03 recovery img
I'm giving up.
Thanks for he help but just don't understand how will do the all process.
I've never done this kind in the past and don't know what exactly to do.
If there's a video instructions on YouTube would be more helpful to me.
The all problem begins from step 7-9.
Sent from my iPad using Tapatalk

mischa_martin said:
Code:
11-06 18:21:07.745 2334 2334 E guojingdong: case=4Preference mIsIndicator=true
11-06 18:21:07.745 2334 2334 E guojingdong: Preference attr=3 a.getIndexCount()=511-06 18:21:07.935 914 982 E ModemAPI: qmi_vs_client_send_msg_sync returned error -45
11-06 18:21:07.935 914 982 E ModemAPI: modem_read_efs, exit result 0
11-06 18:21:07.935 914 982 E ModemService_D: modem_service_response_send_succeed_response error : out of max data size
Do you understand what is going on here?
No?
Me neither
Click to expand...
Click to collapse
I would try to replace/copy the firmware files from B05 to the B29 Rom. Just copy the files from the attachment into the folder etc/firmware in your system partition. I'm quite sure the modem files are not the right one for th A2017G. But I can't tell you which from them are modem related.

paatha13 said:
But I'm on B05.
Does it matter if I use B03 recovery img
I'm giving up.
Thanks for he help but just don't understand how will do the all process.
I've never done this kind in the past and don't know what exactly to do.
If there's a video instructions on YouTube would be more helpful to me.
The all problem begins from step 7-9.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Because I didn't take the risk and downgraded from B05 to B03 before the whole process, I honestly don't know. And just recommend the same to you. If you don't know how to downgrade:
Download the B03 from the link below. Extract it and copy the update.zip to the root folder of your internal SD. Open Settings and go to Updates. Hit Install.
https://mega.nz/#F!kYtRAJjJ!5tD1zPpo0nw2tJwhANA9pQ!tNsQhD5Y
I have my much more detailed guide almost ready. But I need to go work, so won't start to explain it.
---------- Post added at 08:44 PM ---------- Previous post was at 08:43 PM ----------
tron1 said:
I would try to replace/copy the firmware files from B05 to the B29 Rom. Just copy the files from the attachment into the folder etc/firmware in your system partition. I'm quite sure the modem files are not the right one for th A2017G. But I can't tell you which from them are modem related.
Click to expand...
Click to collapse
Please let us know your experiences.

Related

[GUIDE-VDO] How to make your own KitKat ROM with Root+TWRP from KDZ

Hi all,
I'm from Thailand.
I try to make flashable file for 4.4.2 kitkat kdz file for LG G2 ,It can use for LG G2 all model if you have kdz file.
I am testing with kdz file from http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW545195432109876543213/D80220A_00.kdz
( A6SFBK )
I reccommend 7zip for unzip/zip file.
Step by Step Guide
Before doing follower by instruction please read warning in red line before
1. Goto
http://forum.xda-developers.com/showthread.php?t=2600575
Download WindowsLGFirmwareExtract-ver.1.2.1.0 new version
2. Unzip WindowsLGFirmwareExtract-ver.1.2.1.0.zip and open WindowsLGFirmwareExtract.exe
3. At kdz/tot file select open and select 4.4.2 kdz that matching your G2 model (select all files extract)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Select extract kdz and waiting for success
5. At dz files select open and select .dz from step (4) (select all files extract)
6. Select extract dz and waiting for success
7. Select merge system-bin and waiting for success
8. Download
You must select one from 2 template
- KKROM_template.zip
https://mega.co.nz/#!kcVxSLaB!BJ4hHTF_3H8HR6EJTuak2hjiK1g1JosdKDfhcQ9Kr8g
(Stock firmware all partition include when you flash can not use custom recovery)
- KKROM_template_new.zip
https://mega.co.nz/#!BN1EFYRY!RJDpGwN4r3Q7q7lJmQil5RH_1s1lQWLHGZt21vY-Ffw
(New customize for still has custom recovery)
9. Unzip KKROM_template_new.zip/KKROM_template.zip
10. Copy system.img and all bin file as list below from WindowsLGFirmwareExtract-1.2.1.0-Release folder to KKROM_template_new/KKROM_template folder and use bat file in rename_droidth.zip rename all bin file
- KKROM_template_new.zip
KKROM_template_new folder must have
- KKROM_template.zip
KKROM_template folder must have
11. Zip all file in KKROM_template_new/KKROM_template. Now you get KKROM_template_new.zip/KKROM_template.zip ready to flash
12. Download
- Supersu from http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip (For all template)
- Patched Kernels and KitKat BaseBand from http://forum.xda-developers.com/showthread.php?t=2680948 (For KKROM_template_new)
Thank @Cloudyfa for work Patched Kernels and KitKat BaseBand
13. You must on 4.2.2 root+custom recovery (TWRP 2.6.3.3 or 2.7 That I am testing) .
Copy KKROM_template_new.zip/KKROM_template.zip to sdcard
Copy Patched Kernels,KitKat BaseBand to sdcard (For KKROM_template_new)
Copy UPDATE-SuperSU-v1.93.zip to sdcard to sdcard (For all template)
14. Reboot to recovery
15. Wipe
- Dalvik Cache
- System
- Data
- Cache
16 . Install
Warning :
When flash KKROM_template_new.zip finish.Do not Change or Flash Recovery on KK or JB (in case use backup/restore from Recovery or use Custom ROM)
if do not flash kdz before.Your G2 may be can not boot.
For KKROM_template_new
- KKROM_template_new.zip
- KitKat BaseBand
- Patched Kernels
- UPDATE-SuperSU-v1.93.zip
For KKROM_template
- KKROM_template.zip
- UPDATE-SuperSU-v1.93.zip
17 . Wipe cache/dalvik
18. Reboot
19. Enjoy
Guide for KKROM_template
Thank
@AndroidUser00110001
@Cloudyfa
@shriom_manerker
I have KK rooted. Thanks?
Do you still have a custom recovery after you class this?
**** Ripple said:
Do you still have a custom recovery after you class this?
Click to expand...
Click to collapse
์No.
OMG thank you very much
With this it's easier to make custom rom
Thanks awesome
is this for 16gb or 32gb or both?
Seem your file not yet finished uploading?
Both
Sent from my Nexus 7 using Tapatalk
kennytung said:
is this for 16gb or 32gb or both?
Seem your file not yet finished uploading?
Click to expand...
Click to collapse
Thank you. I edited link file.
hi..
thanks, this is exactly what i need.
one question though,
what about "cust.bin"?
someone said in other thread that it's needed to avoid bootloop.
farhanito said:
hi..
thanks, this is exactly what i need.
one question though,
what about "cust.bin"?
someone said in other thread that it's needed to avoid bootloop.
Click to expand...
Click to collapse
In this this:
http://forum.xda-developers.com/showthread.php?t=2665985
I got bootloop then I solve problem by add cust.bin in ROM.it's work for me.
Sent from my Nexus 7 using Tapatalk
somboons said:
In this this:
http://forum.xda-developers.com/showthread.php?t=2665985
I got bootloop then I solve problem by add cust.bin in ROM.it's work for me.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
so, you need to put cust.bin inside the zip, and add this line in updater-script
Code:
package_extract_file("cust.bin", "/dev/block/platform/msm_sdcc.1/by-name/cust");
am i right?
farhanito said:
so, you need to put cust.bin inside the zip, and add this line in updater-script
Code:
package_extract_file("cust.bin", "/dev/block/platform/msm_sdcc.1/by-name/cust");
am i right?
Click to expand...
Click to collapse
Yes.
Sent from my Nexus 7 using Tapatalk
farhanito said:
so, you need to put cust.bin inside the zip, and add this line in updater-script
Code:
package_extract_file("cust.bin", "/dev/block/platform/msm_sdcc.1/by-name/cust");
am i right?
Click to expand...
Click to collapse
Oh Thank,I will edit instruction .Wrong picture.
I'm already in KK
So i need to downgrade to JB first right?
Sent from my LG-D802 using xda app-developers app
GaYoung28 said:
I'm already in KK
So i need to downgrade to JB first right?
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
yes
@somboons thanks for the awesome tutorial just did it and its working just fine on my D802 cheers
This is awesome. It would be easier to flash back to stock this way then requiring a PC. Would this work for Verizon? I'd love a backup of the stock rom incase I'm t hours away from a PC and Verizon forces a bricking OTA update and leaves me completely lost and without a phone.
Sent from my VS980 4G using XDA Premium 4 mobile app
i got error lokiflyng and unsuportted aboot image file :\
help please
player911 said:
This is awesome. It would be easier to flash back to stock this way then requiring a PC. Would this work for Verizon? I'd love a backup of the stock rom incase I'm t hours away from a PC and Verizon forces a bricking OTA update and leaves me completely lost and without a phone.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am not sure it's support Verizon but I think it should work too.
GaYoung28 said:
i got error lokiflyng and unsuportted aboot image file :\
help please
Click to expand...
Click to collapse
Can your G2 boot completely?
I did see this error on my device but At thread http://forum.xda-developers.com/showthread.php?t=2665985
 @AndroidUser00110001 he told don't worry about error
If you get an error with flashing about loki then do not worry. ROM is ok and will boot. It just can't add loki to boot.img so it gives error but no big deal.
Click to expand...
Click to collapse

[ROM] [PREVIEW] Android M

Basic Info:
2nd Preview
Build Number :MPZ79M
Radio (Baseband): M8974A-2.0.50.2.26
Bootloader: HHZ12h
1st Preview --OTA to MPZ79M now available
LINK : hxxps://android.googleapis.com/packages/ota/google_hammerhead/68f7e8ac9439071ba8a987cb956b977d27653a54.signed-hammerhead-MPZ79M-from-MPZ44Q.68f7e8ac.zip
Build Number :MPZ44Q
Radio (Baseband): M8974A-2.0.50.2.26
Bootloader: HHZ12h
So Bootloader and Radio same as that of Lollipop
How to Install ??
Method One: Via cmd
Download the preview directly from :
http://developer.android.com/preview/download.html#top
then follow:
1.You need to setup adb and fastboot
Let's setup ADB and fastboot
Windows:
- You can use my ReducedSDK Kit from Here
- Automated: http://forum.xda-developers.com/show....php?t=2588979 (follow the steps in the software)
- Manual Method:
Download this file and extract the folder called "adb" to your C: drive. Your path should look like this:
Code:
C:\adb\
You will need to open a command prompt window using this method:
Code:
- Go to the C:\adb\ folder
- hold down SHIFT key and RIGHT-CLICK
- select "Open command window here".
In order to use ADB & Fastboot from anywhere - use the following steps to setup windows environment variables:
Navigate to & click on Start > Right-Click on Computer > click on Advance System Settings >
Click on Environment Variables (under the advanced tab) > Click on New (User Variables) >
Variables Name: ADB (Or anything you want) Variables Value: ;C:\adb (this is the Path of my adb.exe file)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mac & Linux:
you can use the reduced SDK as in attachments or :
Install ADB & fastboot using: this file
1. Extract the downloaded zip to your desktop
2. Open Terminal and type in:
Code:
su
cd Desktop/Android/ (note: Android is the directory extracted from zip file)
3. Now type
Code:
./ADB-Install-Mac.sh
Note: By using the method above, your adb and fastboot files are stored at this location on your Mac: /usr/bin/
----
Click to expand...
Click to collapse
^I have taken 90% of this from @vomer 's installation procedure for flashing android M on shamu
2.Backup all contents of your phone ,your phone will be completely wiped in this process
3.Extract the downloaded android m .tgz file and further the tar file in it .
(If using the ReducedSdk) then lace the ReducedSdk file in this folder
4.Connect your phone with your pc in fastboot mode (boot using Volume down and Power button)
5.click flash all and wait..
6.Enjoy Android M
For linux users
After step 3
{IN TERMINAL }cd to the directory having the extracted files and then run
Code:
sudo ./flash-all.sh
All those having problem installing or bootloops
either factory reset via stock recovery or See : Here
Click to expand...
Click to collapse
Method 2:Via Recovery
1.Download the ROM from Preview 1
https://yadi.sk/d/Ua3YaU28hmxUH -- preview 2
2.Now place this file in your phone's memory
3.Boot in recovery
4.Format Data
5.Flash the download zip.
Click to expand...
Click to collapse
A Must Read : http://goo.gl/abVXRL
Screenshots:
http://imgur.com/a/V1UA4 --Preveiw 1
http://imgur.com/a/uz6pU -- preview 2
MOD: MultiWindow
How to Root ?
1.Download Despair Kernel and SuperSu 2.49.
2.Place them in your phone's internal sdcard.
3.Boot in recovery flash Despair Kernel AND then SuperSU.
4. Voila ! Your phone is rooted!!!
linuxteddy said:
Hi,
something else: there was a post in the MultiROM thread about BOKROM, where a TWRP backup usable with MultiROM has been provided. Look here http://forum.xda-developers.com/goo...rom-cm12-unofficial-hammerhead-gapps-t2969820. In the OP there is a "Special Download: M Preview 2 Backup *** NEW ***"
It works for me.
LT
Click to expand...
Click to collapse
stephanmc said:
Hi all. I made a working flashable ZIP for M Preview 2. Working on my N5, with root.
http://forum.xda-developers.com/google-nexus-5/development/rom-android-m-preview-2-flashable-zip-t3157299
I also fixed Titanium Backup not showing previous backups
Click to expand...
Click to collapse
vampsoft said:
Ambient Display
https://mega.nz/#!2MFH2C5L!zCRGKd6fRqPYeB5L01TFGG3LHmMX0JmaiYjlEp7k9KY
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
blackbird5308 said:
For anyone who wants, i built stock kernel with root support, in sync with the MPZ79M sources, it fixes video issues with M DP2.
https://mega.nz/#!zUJyDaBD!SyCb_F2icUO9PBHQSY7kzu35ut9_e-6N36khoxGEkU8
it's only the zImage as i made no modifications on ramdisk. You MUST flash stock MPZ79M boot.img, and then as usual flash this with "fastboot flash zimage zImage-dtb"
Click to expand...
Click to collapse
PS: Thread on Portal .Thanks for your support
Hit
if I helped you !!
Woot!
Now...
Thanks I really need a flashable zip.
Sent from my Nexus 5 CAF.
Any screenshots??
bibhu059 said:
Any screenshots??
Click to expand...
Click to collapse
Uploading Soon
Do you know when a multirom zip is coming?
Any chance there'll be a modified kernel with permissive or disabled SELinux when this ROM gets updated to a flashable zip? Just wondering. I'm already on M Preview but I hear that the kernel change is like the only way to use root for now until SuperSU is updated.
Thanks, dowloading, no root yet?
davehasninjas said:
Any chance there'll be a modified kernel with permissive or disabled SELinux when this ROM gets updated to a flashable zip? Just wondering. I'm already on M Preview but I hear that the kernel change is like the only way to use root for now until SuperSU is updated.
Click to expand...
Click to collapse
Normally @sykopompos and/or his team seem to come up with this first i believe
Sent from my Nexus 5 using Tapatalk
Found this kind of interesting about Android M...
Is our device supported by dsixda's Android kitchen? If yes I'll make a flashable zip myself.
Sent from my Nexus 5 CAF.
Ehi guys when the zip?
punticci said:
Ehi guys when the zip?
Click to expand...
Click to collapse
https://basketbuild.com/filedl/devs?dev=Tassadar&dl=Tassadar/stock_zips/mpz44q_hammerhead.zip
punticci said:
Ehi guys when the zip?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=23991606952611474
[emoji15][emoji15][emoji15][emoji15][emoji15][emoji15][emoji15][emoji15][emoji15]
Are the Radio and bootloader the same of the last version?
33bca said:
https://basketbuild.com/filedl/devs?dev=Tassadar&dl=Tassadar/stock_zips/mpz44q_hammerhead.zip
Click to expand...
Click to collapse
fishman0919 said:
https://www.androidfilehost.com/?fid=23991606952611474
Click to expand...
Click to collapse
This are a flasheable zip android m vía recovery?
adrianedu said:
This are a flasheable zip android m vía recovery?
Click to expand...
Click to collapse
Yes
Hybrid Core said:
Are the Radio and bootloader the same of the last version?
Click to expand...
Click to collapse
I used the one that came with 5.1.1 update (LMY48B) it works flawlessly. So, my guess it does come with the same version of boot loader and radio.

[APP] [UNOFFICIAL] DualBootPatcher with fixed TZ version issue for OnePlus 3T

DualBootPatcher
with fixed TrustZone issue for the OnePlus 3T​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Dual Boot Patcher is an app created by chenxiaolong, which allows you to have multiple ROMs on a single device. This thread was originally to present a port of this app while the OnePlus 3T wasn't officially supported. However it is also official supported now but there is an issue with the official app more precisely with the TZ version while installing patched ROMs. Then you get an error like
Code:
oppo.verify_trustzone() failed to read current TZ version
This is because some ROMs use a special partition called TrustZone (TZ) to identify your device. But this partition is not accessible by ROM zip files patched with the official app. I fixed it by making the TrustZone partition accessible during flashing. I also gained much experience with the Dual Boot Patcher app so feel free to ask questions but please note that if flashing fails, first look up the error at /sdcard/MultiBoot.log and google it before reporting it... Please leave a 'Thanks' if this was helpful!
Important:
I am not responsible for any damage on your device!!! Use this app on your own risk!!!
Make a full Backup of your phone with TWRP or CWM before doing anything!!!
Click to expand...
Click to collapse
If you want to know more about how to use this app, read the official Thread:
https://forum.xda-developers.com/showthread.php?t=2447534
Working:
- patch ROM zip files
- patch GAPPS zip files
- patch SuperSu zip files
- Boot UI​
Issues:
- Sometimes after flashing something, all pins, patterns or passwords are wrong in one of the ROMs. Then simply delete the file /data/system/locksettings.db (your saved fingerprints won't be lost) with TWRP.
- If flashing of a patched zip fails for any reason, you have to choose another install location ("Partition Configuration" in the app) when patching the same zip file again!​
Important instructions for the OnePlus 3T:
- To save a patched zip file, select "OnePlus 3T" instead of "Internal storage" on the sliding menu, otherwise you won't be able to save it.​
- You should patch zip files only for data-slot because the other partitions are usually too small!​
Screenshots:
​
Licenses:
https://github.com/chenxiaolong/DualBootPatcher/tree/master/licenses​
Download:
Version 170306
DualBootUtilities.zip​Changelog:
170305:
- added the OnePlus 3T to the supported Devices
170306:
- fixed TrustZone issue (the one with removing a string from updater-script)​
davan7 said:
any issues with it?
Click to expand...
Click to collapse
As far as I know, there are no special issues when using it on the OnePlus 3T apart from the mentioned ones.
How do i boot in to secondary? No need for DualBootUtilities?
Laapander said:
How do i boot in to secondary? No need for DualBootUtilities?
Click to expand...
Click to collapse
Just select ROMs on the sliding menu of the app and then click on secondary. You don't need DualBootUtilities but you can use it to select in to which ROM you want to boot via recovery.
I have a problem, when I patch the rom file I see only OnePlus 3 and not OnePlus 3T device in the selection, I tried to flash from TWRP but also if I delete the string that is mentioned in the instruction, I received an error. The message say that file is patched for OnePlus 3 and not for OnePlus 3T.
When I used it on Nexus 6P all worked very smooth.
Now solved first problem, I wrongly edited file script but now the zip give me the follow message.
Is there any way to install Aroma zip?
MyStyle0714 said:
Is there any way to install Aroma zip?
Click to expand...
Click to collapse
You can patch and install an Aroma zip as well!
VampireHeart said:
I have a problem, when I patch the rom file I see only OnePlus 3 and not OnePlus 3T device in the selection, I tried to flash from TWRP but also if I delete the string that is mentioned in the instruction, I received an error. The message say that file is patched for OnePlus 3 and not for OnePlus 3T.
When I used it on Nexus 6P all worked very smooth.
Now solved first problem, I wrongly edited file script but now the zip give me the follow message.
Click to expand...
Click to collapse
This is because flashing the first zip failed. You have to patch your zip file again but choose another install location. If you download the updated app, you also don't have to delete the string from updater-script anymore.
Glove007 said:
This is because flashing the first zip failed. You have to patch your zip file again but choose another install location. If you download the updated app, you also don't have to delete the string from updater-script anymore.
Click to expand...
Click to collapse
Thanks but I just have the last version of the application and of I don't remove the string I have the error of verification, I can try to repatch the file.
Glove007 said:
You can patch and install an Aroma zip as well!
Click to expand...
Click to collapse
But after I tried to install it, it showed error.
MyStyle0714 said:
But after I tried to install it, it showed error.
Click to expand...
Click to collapse
Which error? (look also at /sdcard/MultiBoot.log)
Glove007 said:
Which error? (look also at /sdcard/MultiBoot.log)
Click to expand...
Click to collapse
http://imgur.com/PRvCAOJ
MyStyle0714 said:
http://imgur.com/PRvCAOJ
Click to expand...
Click to collapse
The error is displayed clear on the screen: "Zip files using AROMA installer can only be flashed from recovery", so flash it from recovery...
I always seem to get this error, no idea what I'm doing wrong.. any ideas?
Here the logs
Pharrax said:
I always seem to get this error, no idea what I'm doing wrong.. any ideas?
Click to expand...
Click to collapse
The system partition of the OnePlus 3T is probably too small for two ROMs, so try for example a data-slot!
Pharrax said:
Here the logs
Click to expand...
Click to collapse
Yes, is's because the system partition is too small. (Ich kann auch auf Deutsch schreiben...)
Glove007 said:
The system partition of the OnePlus 3T is probably too small for two ROMs, so try for example a data-slot!
Click to expand...
Click to collapse
Glove007 said:
Yes, is's because the system partition is too small. (Ich kann auch auf Deutsch schreiben...)
Click to expand...
Click to collapse
Thank you that fixed the issue :good:
(Bleiben wir bei Englisch damit andere die das Problem haben es auch verstehen )
I try to flash Aurora Rom V8 in TWRP. I am getting symlink error in aroma. Any ideas? Tried secondary and multi slot. Decrypted phone.
Edit. Something to do with V8 is 7.1.1?
Edit2. Can't take screenshot in Aroma
Laapander said:
I try to flash Aurora Rom V8 in TWRP. I am getting symlink error in aroma. Any ideas? Tried secondary and multi slot. Decrypted phone.
Edit. Something to do with V8 is 7.1.1?
Click to expand...
Click to collapse
Try data-slot and post /sdcard/MultiBoot.log!

How To Guide [ROM][STOCK][FASTBOOT][OP9R] Stock OxygenOS Fastboot ROMs

Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you . I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
1). Download the zip
2). Unpack the zip in a folder
3). Reboot the OnePlus 9R in fastboot-bootloader mode (Power and volume + and volume-)
4). Connect the OnePlus 9R to PC
5). Run flash-all.bat flasher
6). Wait until the process end
7). Voila! your OnePlus 9R will now boot into OxygenOS
POINTS TO REMEMBER
* "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
* These ROMs can't be used to update or downgrade your phone but just to restore your phone. Downgrade from OOS 12 works now.
* This can’t be used to switch from ColorOS to OxygenOS you can use MSM unbrick tool to do that.
DOWNLOAD:-
https://sourceforge.net/projects/op8t-9r-fastboot-roms/files/OnePlus_9R/
Nice
Hi OP, I changed the tag from Development to How To Guide, because we only use Development for original work like you build the ROM from kernel/device tree etc... Thanks.
HELLBOY017 said:
Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you . I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
1). Download the zip
2). Unpack the zip in a folder
3). Reboot the OnePlus 9R in fastboot-bootloader mode (Power and volume + and volume-)
4). Connect the OnePlus 9R to PC
5). Run flash-all.bat flasher
6). Wait until the process end
7). Voila! your OnePlus 9R will now boot into OxygenOS
POINTS TO REMEMBER
* "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
* These ROMs can't be used to update or downgrade your phone but just to restore your phone.
* This can’t be used to switch from ColorOS to OxygenOS you can use MSM unbrick tool to do that.
* !!! IMPORTANT !!!
Before flashing make sure you know about which type of ram your device supports i.e LPDDR4X/LPDDR5 as flashing wrong xbl config will hardbrick your device.
Here’s how you can check what type of ram your device has:-
Now, as to exactly find out which variant that you have, turn on USB debugging and enter this command:-
Code:
adb shell getprop ro.boot.ddr_type
If the value is 0, that means you have LPDDR4X. If the value is 1, that means you have LPDDR5.
This command is more reliable than the Devcheck and other apps.
DOWNLOAD:- https://drive.google.com/file/d/1LTknGhfR2JTtXhN0rGMCS4OwmUdqt3PF/view?usp=sharing
Click to expand...
Click to collapse
Errr sorry I can make sure that I have the DDR5,but it seems that when I complete the flash using the DDR5 profile config,my phone hard bricked, so how can I get it back? Now it can not even enter 9008 mode
zwk22160 said:
Errr sorry I can make sure that I have the DDR5,but it seems that when I complete the flash using the DDR5 profile config,my phone hard bricked, so how can I get it back? Now it can not even enter 9008 mode
Click to expand...
Click to collapse
You will most likely need to visit the service center and get your phone repaired.
Are you sure that your device had DDR5?
theincognito said:
You will most likely need to visit the service center and get your phone repaired.
Are you sure that your device had DDR5?
Click to expand...
Click to collapse
Actually,I checked my DDR type via devcheck instead of the adb command. Seems that the dev check is no so reliable. Anyway, I have already sent my phone to the service center to repair, I have a OnePlus 7 pro as the backup phone, so it doesn't affect me too much.
Created a Tutorial based on your firmware/instructions. Hoping you will like it.
https://androidmtk.com/install-firmware-oneplus-9r
zwk22160 said:
Actually,I checked my DDR type via devcheck instead of the adb command. Seems that the dev check is no so reliable. Anyway, I have already sent my phone to the service center to repair, I have a OnePlus 7 pro as the backup phone, so it doesn't affect me too much.
Click to expand...
Click to collapse
Yeah. The apps aren't reliable at this. Always use the adb command. 100% reliable. And since it's harbricked for you, I am pretty sure that you have a DDR4X variant.
zwk22160 said:
Errr sorry I can make sure that I have the DDR5,but it seems that when I complete the flash using the DDR5 profile config,my phone hard bricked, so how can I get it back? Now it can not even enter 9008 mode
Click to expand...
Click to collapse
It’s clearly written to not trust devcheck and other apps that prop is the only trusted source of finding which type of ram ur device has. It has also come to my attention that DDR5 devices can boot to EDL if we flash wrong xbl configs on them but the DDR4 ones can’t boot to EDL if wrong xbl config is flashed. (Means ddr4 users would have to get phone repaired by service center if wrong xbl config is flashed on their device)
PetiaWarzel said:
Created a Tutorial based on your firmware/instructions. Hoping you will like it.
https://androidmtk.com/install-firmware-oneplus-9r
Click to expand...
Click to collapse
Appreciate it a lot! Thanks
I faced the same problem
Service center says they can't flash it back
They ended up replaced a new motherboard for me
hmm for me the
Code:
adb shell getprop ro.boot.ddr_type
returns empty.
I guess that infers I'm using LPDDR4X?
Edit:
Code:
adb shell getprop
This would return a complete list of all the properties you can query with this command. For me, this list doesn't seem to have any field called "ro.boot.ddr_type"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm using the Chinese variant of OP9R, not so sure if it matters.
Also, DevCheck would not report RAM variants under the hardware tab as well.
Leohearts said:
I faced the same problem
Service center says they can't flash it back
They ended up replaced a new motherboard for me
Click to expand...
Click to collapse
I checked it again and
OnePlus9R:/ $ getprop | grep ddr
[ro.boot.ddr_type]: [1]
[vendor.boot.ddr_type]: [1]
OnePlus9R:/ $
I'm sure flashed the ddr5 version, but it hard-bricked and even cant boot into 9008
*UPDATED*
* Added OxygenOS 11.2.6.6 Fastboot ROM
* Removed xbl configs so that now no more hardbricks happen
* Reduced partition sizes for inactive slot so that ROMs can be flashed properly through fastboot
will this work on Chinese variant 12gb/256gb ddr4 ? LE2100 bl is already unlocked
Mkkt Bkkt said:
will this work on Chinese variant 12gb/256gb ddr4 ? LE2100 bl is already unlocked
Click to expand...
Click to collapse
If ur using oxygenos then yes
HELLBOY017 said:
If ur using oxygenos then yes
Click to expand...
Click to collapse
yes , for some reason it came with oxygenos preinstalled
HELLBOY017 said:
Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you . I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
1). Download the zip
2). Unpack the zip in a folder
3). Reboot the OnePlus 9R in fastboot-bootloader mode (Power and volume + and volume-)
4). Connect the OnePlus 9R to PC
5). Run flash-all.bat flasher
6). Wait until the process end
7). Voila! your OnePlus 9R will now boot into OxygenOS
POINTS TO REMEMBER
* "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
* These ROMs can't be used to update or downgrade your phone but just to restore your phone.
* This can’t be used to switch from ColorOS to OxygenOS you can use MSM unbrick tool to do that.
DOWNLOAD:-
https://mega.nz/folder/ePIETB4D#sU8cJ54l4UI7JCXGwc7Nog
Click to expand...
Click to collapse
Download link in Mega can't download with standard account, requires premium. could you please upload in other hosting website if possible? Thanks!
logeshwywan said:
Download link in Mega can't download with standard account, requires premium. could you please upload in other hosting website if possible? Thanks!
Click to expand...
Click to collapse
Will do
Link updated.
*Apologies for updating it late as I had fever so didn't have time for mirror it somewhere else

How To Guide [EU model] Unlock bootloader of European model

As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post.
First of all, this is only for the European RMX3301, but you can try on any other global model that doesn't allow the unlocking of the bootloader. I'm not talking about temporary errors, but of the infamous This phone model does not support deep testing error message.
Before starting I would like to thank polygraphene for their implementation of the Dirty Pipe vulnerability on Android. Without that, this would not have been possible.
Requirements:​
The phone with a decent charge. Do not attempt this procedure with the phone at 10% and then cry if something goes wrong
A compatible build, read below
A Windows or Linux PC with adb and fastboot drivers installed
Check if your build is compatible:​
Go to Settings -> About device -> Version and check Build number:
If your build is between RMX3301_11_A.14 and RMX3301_11_A.21, go to the procedure below
If your build is lower than RMX3301_11_A.14, or higher than RMX3301_11_A.21, install this OTA package to downgrade (or upgrade) to RMX3301_11_A.14
Procedure:​
Make sure under Developer options you have OEM unlocking and USB debugging enabled
Download and extract the attached gt2pro_eu_unlock_dirtypipe_v0.2.zip file
Open a terminal in the folder of the extracted files
Connect the phone to the PC and select the File transfer option
Run the script:
On Windows, type run.bat and press enter
On Linux, type ./run.sh and press enter
Now the phone is temporarily rooted and the phone model is changed to RMX3301. Do not reboot or you will lose this status.
At this point you can follow the procedure on the official forum to unlock the bootloader of the global model. If you already have the Deeptesting app installed, clear its data to make sure it will update.
Changelog:​v0.2:
Show more info about device for better debug
Show the model at the end to check if it worked
For technical people: how does it work?​The script abuses a vulnerability of the Linux kernel called Dirty Pipe (or CVE-2022-0847). For further details, you can visit the official website. This allows us to gain temporary root and overwrite the ro.product.name property, the only one checked by the Deeptesting app. The vulnerability is present in Android and it has been fixed, at least for the Pixel 6, in the May 2022 security update. On the GT 2 Pro, the vulnerability has been fixed with the Android 13 update, while the latest Android 12 build (RMX3301_11_A.21) is still vulnerable. I have tested the procedure personally up to build RMX3301_11_A.16. If you're on a newer build and it doesn't work, please report it in the comments.
Will it work on device X?​If the following conditions are met:
it is a Realme device;
the kernel version is 5.10.66;
there's a global model with a different ro.product.name that can be unlocked;
then you can edit the startup-root file and replace RMX3301 (near the end) with the ro.product.name of the global model and try if it works. If it doesn't, it could be for a lot of reasons. Unfortunately, I can't help you without physically having the device in hand.
If you have further questions about the procedure, please post them below.
woowww... thanks for you aport
I wonder if we can use this temporary root to do some modifications on system.
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
Click to expand...
Click to collapse
Excellent question... for example try modific the build regist
Click to expand...
Click to collapse
Rapper_skull said:
As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post.
First of all, this is only for the European RMX3301, but you can try on any other global model that doesn't allow the unlocking of the bootloader. I'm not talking about temporary errors, but of the infamous This phone model does not support deep testing error message.
Before starting I would like to thankpolygraphene for their implementation of the Dirty Pipe vulnerability on Android. Without that, this would not have been possible.
Requirements:
The phone with a decent charge. Do not attempt this procedure with the phone at 10% and then cry if something goes wrong
A compatible build, read below
A Windows or Linux PC with adb and fastboot drivers installed
Check if your build is compatible:
Go to Settings -> About device -> Version and check Build number:
If your build is RMX3301_11_A.14, RMX3301_11_A.15 or RMX3301_11_A.16, go to the procedure below
If your build is lower than RMX3301_11_A.14, or higher than RMX3301_11_A.16, install this OTA package to downgrade (or upgrade) to RMX3301_11_A.14
Procedure:
Make sure under Developer options you have OEM unlocking and USB debugging enabled
Download and extract the attached gt2pro_eu_unlock_dirtypipe.zip file
Open a terminal in the folder of the extracted files
Connect the phone to the PC and select the File transfer option
Run the script:
On Windows, type run.bat and press enter
On Linux, type ./run.sh and press enter
Now the phone is temporarily rooted and the phone model is changed to RMX3301. Do not reboot or you will lose this status.
At this point you can follow the procedure on the official forum to unlock the bootloader of the global model. If you already have the Deeptesting app installed, clear its data to make sure it will update.
For technical people: how does it work?
The script abuses a vulnerability of the Linux kernel called Dirty Pipe (or CVE-2022-0847). For further details, you can visit the official website. This allows us to gain temporary root and overwrite the ro.product.name property, the only one checked by the Deeptesting app. The vulnerability is present in Android and it has been fixed, at least for the Pixel 6, in the may 2022 security update. At the time of writing, the latest build for the GT2 Pro is RMX3301_11_A.16, and it's still vulnerable.
If you have further questions about the procedure, please post them below.
Click to expand...
Click to collapse
When you try the procedure... delete al date of phone? whe finish---- type run.bat and press enter ---- erase all?
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
Click to expand...
Click to collapse
Theoretically you can do everything you can do on a rooted phone (Magisk, but without modules and Zygisk). In practice I never got Magisk to work properly, so I just limited myself to change the property. My goal was to unlock the bootloader, so I did it and installed Magisk.
manu81cba said:
When you try the procedure... delete al date of phone? whe finish---- type run.bat and press enter ---- erase all?
Click to expand...
Click to collapse
My procedure will not delete any data, but after that you have to follow the official procedure to unlock the bootloader, and that will factory reset your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have this error... why?
manu81cba said:
View attachment 5634133
I have this error... why?
Click to expand...
Click to collapse
Can you post the output of adb devices?
Rapper_skull said:
Can you post the output of adb devices?
Click to expand...
Click to collapse
You can explain? no understand.. what do you say?
manu81cba said:
You can explain? no understand.. what do you say?
Click to expand...
Click to collapse
In the terminal, where you are, type adb devices and press enter, then post the output.
Rapper_skull said:
In the terminal, where you are, type adb devices and press enter, then post the output.
Click to expand...
Click to collapse
manu81cba said:
View attachment 5634133
I have this error... why?
Click to expand...
Click to collapse
Yes i have same output on A.16 installed.
manu81cba said:
View attachment 5634153
Click to expand...
Click to collapse
I can see that you have two different versions of adb, one inside the platform-tools folder and one installed elsewhere. Please confirm that by running adb version inside platform-tools and then outside.
Rapper_skull said:
In the terminal, where you are, type adb devices and press enter, then post the output.
Click to expand...
Click to collapse
now put all file decripted to plataform adb... and this result... all ok?
manu81cba said:
now put all file decripted to plataform adb... and this result... all ok?
View attachment 5634159
Click to expand...
Click to collapse
Yes. To make sure, run adb getprop ro.product.name and confirm it's RMX3301.
manu81cba said:
now put all file decripted to plataform adb... and this result... all ok?
View attachment 5634159
Click to expand...
Click to collapse
Working now?
Is rooting temporary? i can modific build.pro? or this process is only for change the model propety?
manu81cba said:
Working now?
Is rooting temporary? i can modific build.pro? or this process is only for change the model propety?
Click to expand...
Click to collapse
No, you can't modify any files, since /system is read-only. Even if you manage to do it, you will brick your device since the bootloader is still locked. If you want to unlock your bootloader, follow the official guide I've linked.
Rapper_skull said:
Yes. To make sure, run adb getprop ro.product.name and confirm it's RMX3301.
Click to expand...
Click to collapse
manu81cba said:
View attachment 5634169
Click to expand...
Click to collapse
Sorry, adb shell getprop ro.product.name

Categories

Resources