Related
Okay here we go,
Thanks @pikeylfc for testing. :good:
Rootable Permissive Verity/RIC disabled.
Marvelous Super-Huge Thanks to
@AndroPlus for his kernel source
and helping me out with the kernel.elf situation.
This is in line with AndroPlus's sources at the time I cloned and compiled originally 9th March 2016 for the Z5 premium.
The kernel souce is the same for this device, the kernel was compiled last night.
Download
sxz3plus_ivy_MM_Rootable_Permissive_boot.img
It seems the dsds model may not be unlockable at least in one instance so far.
I'm going to leave this image in place however.
sxz3plus_ivy_dsds_MM_Rootable_Permissive_boot.img
This is for Marshsmellow, it's not rocket-science.
flash by normal means
This image is setup with the bootrec scenario. That information is covered in AndroPlus work and threads.
My defconfigs are attached.
Use @Chainfire 's latest SuperSU, this version will apply root to the boot.img (system-less root).
I do not intend any further effort outside of this.
ATTENTION: I don't have a recovery build for ivy. I don't own the device. The only reason i sorted the kernel for root is because the kernel source is the same from the z3+/z4 to the z5.
Someone who owns the device will have to start picking up proper development. Sorry.
I am still looking for confirmation as to whether or not the bootloader for the dsds model is unlockable, or if there is
some sort of country restriction that applies.
m
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
30920704 Sep 12 2015 boot-251.img
16293888 Mar 14 14:20 sxz3plus_ivy_MM_Rootable_Permissive_boot.img
Can you confirm the steps?
# Get into flastboot download mode
fastboot flash boot sxz3plus_ivy_MM_Rootable_Permissive_boot.img
fastboot boot recovery.twrp.2.8.7.0.img
in TWRP, flash SuperSU-v2.66.zip
reboot system
krusir said:
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
30920704 Sep 12 2015 boot-251.img
16293888 Mar 14 14:20 sxz3plus_ivy_MM_Rootable_Permissive_boot.img
Can you confirm the steps?
# Get into flastboot download mode
fastboot flash boot sxz3plus_ivy_MM_Rootable_Permissive_boot.img
fastboot boot recovery.twrp.2.8.7.0.img
in TWRP, flash SuperSU-v2.66.zip
reboot system
Click to expand...
Click to collapse
Yes that's what I did
krusir said:
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
Click to expand...
Click to collapse
k,
hi, instead of the "usual" kernel binary + dtb image
this package uses a compressed and concatenated kernel-dtb.
So where the "usual" setup results in a 20+mb kernel binary and a 700+kb - 2mb dt.img [depending]
the resulting image-dtb.gz generated during kernel compilation comes down to roughly 8.3mb total.
And since the ramdisk itself is largely text files with few small compiled binaries in sbin, the ramdisk itself
can be compressed from 13.1mb, uncompressed in this case, down to 6.9mb with gzip compression.
With lzma compression the ramdisk would be 2.8mb
m
Super. Install went perfect. Works as expected. Also flashed -arm64-custom-build-by-wanam-20160211.zip
Gravity works fine. I only tried few mods I used regularly.
Thanks for getting is available. I've been keep searching for past few days since upgrade.
Sent from my E6553 using Tapatalk
krusir said:
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
30920704 Sep 12 2015 boot-251.img
16293888 Mar 14 14:20 sxz3plus_ivy_MM_Rootable_Permissive_boot.img
Can you confirm the steps?
# Get into flastboot download mode
fastboot flash boot sxz3plus_ivy_MM_Rootable_Permissive_boot.img
fastboot boot recovery.twrp.2.8.7.0.img
in TWRP, flash SuperSU-v2.66.zip
reboot system
Click to expand...
Click to collapse
Hi, I'm a noob regarding root on the Z3+ so I would be very grateful if someone could explain a bit more detailed who this installation should be carried out?
I never rooted my device on lollipop, but I guess that in order to be able to flash this kernel, the bootloader must first be unlocked?
I assume that the procedure has not changed because of the update to MM, so i guess I could find the steps somewhere here in the Z3+/Z4 forum (of course if you want to explain those steps as well I wont protest )
Thanks in advance,
Andreas
Thank you so much! Now I finally got the iOS emojis ♥
Install was easy, boot time was same as normal!
bobboviking said:
Hi, I'm a noob regarding root on the Z3+ so I would be very grateful if someone could explain a bit more detailed who this installation should be carried out?
I never rooted my device on lollipop, but I guess that in order to be able to flash this kernel, the bootloader must first be unlocked?
I assume that the procedure has not changed because of the update to MM, so i guess I could find the steps somewhere here in the Z3+/Z4 forum (of course if you want to explain those steps as well I wont protest )
Thanks in advance,
Andreas
Click to expand...
Click to collapse
Andreas,
provided your device is single sim, just flash the img as normal using fastboot. As per OP this is for the MM firmware release.
If your device is dual sim [dsds] let me know and i will post a dsds version AFTER you post the kernel.sin image from the ftf firmware archive for your device.
NO MEGA! DIE CLOUD DIE !!
m
Its not that complicated, but yes, your bootloader must be unlocked. Once you have that sorted, just use flashtool to flash the firmware (you can download the one you want from within flashtool using xperifirm) by installing fastboot and flashmode drivers (those are in the folder you installed flashtool; on anything above Win8 youll need to turn off driver verification to install these drivers, just google that if you dont know how it works), then choosing flashmode, selecting the firmware and falshing it. If you want to do a clean install, just check all the Wipe settings. Two questions will come up while flashing, just click yes on both.
Then you put the phone into fastboot mode (oh and have supersu on the SD card helps) and once again using flashtool, flash the img file from this thread. Then hotboot into the bootable TWRP, found in some other thread here. The phone will restart into TWRP and there you choose install and install the superSU.zip you copied to your SD card before.
If you dont understand parts of what I said, reconsider if youre really so much into gaining root OR ask
Oh gosh. Do I need to unlock my phone first? Mine is dual sim, I'll post the kernel tomorrow, it's 2 a m here, sorry.
alexander43c said:
Oh gosh. Do I need to unlock my phone first? Mine is dual sim, I'll post the kernel tomorrow, it's 2 a m here, sorry.
Click to expand...
Click to collapse
Good deal :good:
I was waiting for someone with a dsds model to respond.
Again, post it to where i can get it.
NO MEGA! DIE CLOUD DIE !!
m
And yes, always now and forever, you will need to unlock your bootloader.
works perfect here! finally marshmallow, root and xposed! thank you very much !!!
oh and drmrestore.zip also works great! much better camera pictures, x-reality works etc! i'm really excited
Anyone else with system storage being shown as 16 GB?
moonbutt74 said:
Good deal :good:
I was waiting for someone with a dsds model to respond.
Again, post it to where i can get it.
NO MEGA! DIE CLOUD DIE !!
m
And yes, always now and forever, you will need to unlock your bootloader.
Click to expand...
Click to collapse
Here you go.
is gg driver ok by the way?
https://drive.google.com/open?id=0B80b07NYd46FYU5HWEdtaXoydm8
You need to set the sharing option!!!
moonbutt74 said:
You need to set the sharing option!!!
Click to expand...
Click to collapse
I've done that after you tried to get the link. Sorry for the inconvenience. I'll check it again
Sent from my E6533 using Tapatalk
And now you need to post the correct link!!!
alexander43c said:
I've done that after you tried to get the link. Sorry for the inconvenience. I'll check it again
Sent from my E6533 using Tapatalk
Click to expand...
Click to collapse
Okay good :good:
What is the device codename and model number?
derp nevermind , i have too much going on at once xD
moonbutt74 said:
Okay good :good:
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B80b07NYd46FYU5HWEdtaXoydm8
here you are
"I'm not responsible for any damage suffered by your device. You decide if you want to use my tool or not. Also you won't be able to update via OTA."
Ok guys, so as I promised, as soon as I received my Robin I started to work on this to finish it, and after some days of working and testing, here you have a toolkit for the cute Robin:
- Unlock/Lock the Robin (You should unlock your Robin the first time you use this tool. If not, as most of the tools below need the bootloader to be unlocked, you will lose your data when running any of them for the first time. In that case, creating a backup would be really unuseful. Unlock once, unlock forever)
- Backup/Restore
- Root
- Install TWRP
- Wipe Cache/Data (with and without TWRP installed)
- Install factory images (System, Boot and/or recovery, up to you - Not the last version, I have to update it)
- Install non-forced-encryption patched boot by @d3xt3r (Thanks bud!) [Possibly adding the @deadman96385 version too in a near future!]
Root, Install TWRP and Backup/Restore work 100% sure. Other like install factory images or the non-encryption mod I haven't tested them (I have zero time, literally), but they should work (95% sure).
Thanks also to @deadman96385, @d3xt3r, and @Baymax, who helped me testing and giving me their knowdledge!
Any suggestions and bug reporting are welcome!
Changelog
v1.2
No more using C:\ to store all the necessary files
Now using temp files, they're deleted when the Toolkit window is closed
No need to install adb anymore, it's installed the first time you run the .exe file
Update check added. You will get a message to download the new .exe everytime an update is available
Backup fixed (wasn't working)
DEAD
Great job mate! ^^
Nice job buddy!
good job david ? ? ?
Sharing violation
Getting sharing violation when I go to install adb. Any thoghts? Windows 10
Steve
flsocialist said:
Getting sharing violation when I go to install adb. Any thoghts? Windows 10
Steve
Click to expand...
Click to collapse
Can you give any more specific info (or screenshots)? Did you already have adb installed or not?
D
Good job David!! (I'm Darragh lol )
I can't seem to get this to detect that I have ADB installed...
daavm said:
"I'm not responsible for any damage suffered by your device. You decide if you want to use my tool or not. Also you won't be able to update via OTA."
Ok guys, so as I promised, as soon as I received my Robin I started to work on this to finish it, and after some days of working and testing, here you have a toolkit for the cute Robin:
- Unlock/Lock the Robin (You should unlock your Robin the first time you use this tool. If not, as most of the tools below need the bootloader to be unlocked, you will lose your data when running any of them for the first time. In that case, creating a backup would be really unuseful. Unlock once, unlock forever)
- Backup/Restore
- Root
- Install TWRP
- Wipe Cache/Data (with and without TWRP installed)
- Install factory images (System, Boot and/or recovery, up to you - Not the last version, I have to update it)
- Install non-forced-encryption patched boot by @d3xt3r (Thanks bud!) [Possibly adding the @deadman96385 version too in a near future!]
Root, Install TWRP and Backup/Restore work 100% sure. Other like install factory images or the non-encryption mod I haven't tested them (I have zero time, literally), but they should work (95% sure).
Thanks also to @deadman96385, @d3xt3r, and @Baymax, who helped me testing and giving me their knowdledge!
Any suggestions and bug reporting are welcome!
DOWNLOAD
Click to expand...
Click to collapse
Only if u had released this 3months earlier i wouldnt hav hard bricked my phone broo......... I've bcom a fan of urs bro....
Mountainmohawk said:
I can't seem to get this to detect that I have ADB installed...
Click to expand...
Click to collapse
@Mountainmohawk can you give me any more specific details? Thanks
D
Sunderesh said:
Only if u had released this 3months earlier i wouldnt hav hard bricked my phone broo......... I've bcom a fan of urs bro....
Click to expand...
Click to collapse
@Sunderesh at least nextbit's warranty covers accidental bricks!
D
Updated to v1.2!!
D
I got a trojan warning from this rootkit. Any thoughts? Or am I the only one?
joeminati said:
I got a trojan warning from this rootkit. Any thoughts? Or am I the only one?
Click to expand...
Click to collapse
@joeminati yes, it's already been reported. Some Antivirus software take any non-signed .exe package as a virus (trojan in this case). Better answer about this, in stackoverflow: http://stackoverflow.com/questions/...015-community-trojan-heur-qvm03-0-malware-gen
PD: Obviously my .exe is not signed
D
Attempted
I attempted to use this tool and it wouldn't acknowledge that my Robin was connected to it. I've installed adb and unlocked bootloader and twrp and custom rom without the tool but I wanted to try the tool and it didn't work.
dispatcher2412 said:
I attempted to use this tool and it wouldn't acknowledge that my Robin was connected to it. I've installed adb and unlocked bootloader and twrp and custom rom without the tool but I wanted to try the tool and it didn't work.
Click to expand...
Click to collapse
@dispatcher2412 yeah, some users are having the same problem. Thanks, will try to solve it!
D
daavm said:
@Sunderesh at least nextbit's warranty covers accidental bricks!
D
Click to expand...
Click to collapse
Really therz nothing like that in my country bro......
Sunderesh said:
Really therz nothing like that in my country bro......
Click to expand...
Click to collapse
@HyderAbad where did you buy your Robin? It usually has 1 year warranty from Nextbit, which covers accidental bricks. Contact Nextbit support and they will help you!
D
Does this toolkit also unroots the device to factory??
utsav_94 said:
Does this toolkit also unroots the device to factory??
Click to expand...
Click to collapse
I believe you can flash factory images. If not, you can check out our forums for more information. I did provide an unbrick tool that helps to do this.
Since K10 is now rootable for MTK variants. Anyone who try to enter TWRP recovery using an app called Root Rashr Flash Tool to enter the recovery without using adb and PC. I use it before but not a 100% sure if I do it in a right way. So anyone? This may help a lot of us to know if K10 may enter TWRP without PC
As far as I remember rashr doesn't have option to boot recovery from storage, but have only options to install recovery or boot to installed one. For K10 fastboot is required to boot to twrp. I'm not sure why twrp can't be flashed..?
Professor Woland said:
As far as I remember rashr doesn't have option to boot recovery from storage, but have only options to install recovery or boot to installed one. For K10 fastboot is required to boot to twrp. I'm not sure why twrp can't be flashed..?
Click to expand...
Click to collapse
There is a security signature in the stock recovery image that would be required to be pasted into the twrp (like in case of Bump! but it's smarter on newer lg phones). Without it phone gets bricked. I guess this signature is also there in the boot image and after making systemless root this signature probably gets corrupted so i don't know how can our device boot up after systemless root . I read some comments that newer security level firmwares (december and january) can't be rooted and maybe this is the reason (i mean maybe in newer firmwares the boot partition is also verified by this signature).
We would need something like bump. I tried some hex editors and pasted the final lines to the end of the twrp from the stock recovery but it didn't work. I guess this signature is like a crc code so it might be generated from the image base but i have no idea how...
gottlasz said:
There is a security signature in the stock recovery image that would be required to be pasted into the twrp (like in case of Bump! but it's smarter on newer lg phones). Without it phone gets bricked. I guess this signature is also there in the boot image and after making systemless root this signature probably gets corrupted so i don't know how can our device boot up after systemless root . I read some comments that newer security level firmwares (december and january) can't be rooted and maybe this is the reason (i mean maybe in newer firmwares the boot partition is also verified by this signature).
We would need something like bump. I tried some hex editors and pasted the final lines to the end of the twrp from the stock recovery but it didn't work. I guess this signature is like a crc code so it might be generated from the image base but i have no idea how...
Click to expand...
Click to collapse
I really don't get them, if they want to sell phones which won't get much updates, than they should make it easyer to instal twrp/unlock bootloader/make custom rom.
Hm I would like to help but my reverse engineering/developing skils are poor. Any hints how to find that signature?
I tought twrp couldn't be flashed because of size, but that won't be big trouble however.
Professor Woland said:
I really don't get them, if they want to sell phones which won't get much updates, than they should make it easyer to instal twrp/unlock bootloader/make custom rom.
Hm I would like to help but my reverse engineering/developing skils are poor. Any hints how to find that signature?
I tought twrp couldn't be flashed because of size, but that won't be big trouble however.
Click to expand...
Click to collapse
Size is not a problem anymore. The recovery partition is 16Mb while the 3.0.2 TWRP is approx 11-12Mb. However i already gave up on searching the signature. I spent days on it and i found a signature (quite long one actually) in the end of each partition (boot, recovery, laf,...). I succesfully added the same signature from the stock recovery to the TWRP but it bricked the phone after i flashed it. Then i found that each signature differs a bit depending on firmware security level and the partition itself so i believe the signature is generated like a crc code or some secret way and totally firmware and partition dependent... no way to generate it by ourselves if we don't know the method.
P.S. i don't care if they sell phones i'm unable to root etc... but why on earth can we not delete unnecessary stock apps to free up space and memory...
gottlasz said:
Size is not a problem anymore. The recovery partition is 16Mb while the 3.0.2 TWRP is approx 11-12Mb. However i already gave up on searching the signature. I spent days on it and i found a signature (quite long one actually) in the end of each partition (boot, recovery, laf,...). I succesfully added the same signature from the stock recovery to the TWRP but it bricked the phone after i flashed it. Then i found that each signature differs a bit depending on firmware security level and the partition itself so i believe the signature is generated like a crc code or some secret way and totally firmware and partition dependent... no way to generate it by ourselves if we don't know the method.
P.S. i don't care if they sell phones i'm unable to root etc... but why on earth can we not delete unnecessary stock apps to free up space and memory...
Click to expand...
Click to collapse
In that case probably signature is from more parts one part is to verify to the phone, and one part is to verify the name or some other specific from recovery so you can't just paste signature to any recovery. If we only could "decrypt" signature. And find a way to create it. Could you upload that signature you found to pastebin or whatever you like?
Professor Woland said:
In that case probably signature is from more parts one part is to verify to the phone, and one part is to verify the name or some other specific from recovery so you can't just paste signature to any recovery. If we only could "decrypt" signature. And find a way to create it. Could you upload that signature you found to pastebin or whatever you like?
Click to expand...
Click to collapse
I'll send it to you tomorrow or on Monday in pm.
You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img ,
{{{ bootloader "NO NEED" This Work Before Just Because v48 and v56 have the same bootloader version }}} , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
EDIT HELLO
Things Have Changed Dont Try To Downgrade Bootloader or The Phone Will Get Hard Bricked , Why well bootloader versions on new firmwares have been upgraded please check all the information on the Bootloader/Fastboot
MODE Of The Phone Which Version You Have , Now For Example If You Are On Version NCQS26.69-64-5 you will need SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml full package then extract and now you will need SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml extract it too , Now Just Move The 2 Oems Images And 4 System Images And Boot Image To SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml Folder Next Look for RSD_Lite_Motorola_XML_To_Batch_Script on Google Download it And Watch The Video Of Rootjunky on how to use it. Very Simple Wish All Of You Luck And im Not Responsible Of Any Damage Of Your Phone Use This Guide On Your Own Terms.
ozmage said:
You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img , bootloader , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
Click to expand...
Click to collapse
I flashed the Sprint firmware and had data working on my XT1766 after it got it's carrier update, the Sprint firmware does not soft brick the phone as I flashed it and can confirm it doesn't soft brick it, so you are incorrect in saying that.
I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?
dlinderaz said:
I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?
Click to expand...
Click to collapse
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?
madbat99 said:
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?
Click to expand...
Click to collapse
I restored the entire thing after flashed the indicated files causing the error message.
dlinderaz said:
I restored the entire thing after flashed the indicated files causing the error message.
Click to expand...
Click to collapse
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.
madbat99 said:
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.
Click to expand...
Click to collapse
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.
dlinderaz said:
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.
Click to expand...
Click to collapse
Keep in mind I have the virgin mobile version (sprint xt1766). Don't know which one you have. Some have had trouble with rsdlite on Windows 10, it worked fine for me though.
I used rsdlite from here
The newest one, 6.2.4 I think
Apn Xt1766
I just want to add apn and want to use hot spot again
As the phone is updated on latest build ..
I don't want the root access..
What's should I try then from previous build , can anyone
Guide me easy steps plz.
Xt1766 how to get working apn
Will anyone confirm
danishamini.saifi said:
Will anyone confirm
Click to expand...
Click to collapse
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.
madbat99 said:
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.
Click to expand...
Click to collapse
Thanks, ill try and share the result.
I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.
danishamini.saifi said:
I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.
Click to expand...
Click to collapse
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.
madbat99 said:
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.
Click to expand...
Click to collapse
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?
danishamini.saifi said:
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?
Click to expand...
Click to collapse
N/A will be there. But you can flash a new boot logo to kinda hide it. Instead of a black screen, any logo you want, maybe with a white strip at the top to hide it. I'll get you a link.
Here are some good ones. https://forum.xda-developers.com/mo...om-boot-logos-converted-t3759320/post75787882
And here is the guide to make your own
https://forum.xda-developers.com/moto-e4/how-to/replace-n-boot-image-t3687212/post74118155
@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks
danishamini.saifi said:
@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks
Click to expand...
Click to collapse
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.
madbat99 said:
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.
Click to expand...
Click to collapse
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.
dlinderaz said:
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.
Click to expand...
Click to collapse
Ota updates will likely always fail if you have twrp, or have modified the system in any way. The ota performs many checks (assert props) to see if the system is clean. If any asserts fail, the ota will fail. Even restoring the stock recovery doesn't guarantee the ota will work.
Hello community, I need some explanation first if my approach is incorrect. I am trying to downgrade to Android 10, but i was soul-crashed after reading some information about the bit/binary value that samsung uses on its firmware(basically you cant downgrade if this value is not equal to your targeted frimware). However even though i feel scammed by Samsung, i would like to ask you the community as my final resort to guide me.
Is there some way i can trick SW REV checker or delete this partition containing this binary file?. Does "deleting" it affect my ability to boot into the download mode?
{Temp_User} said:
Hello community, I need some explanation first if my approach is incorrect. I am trying to downgrade to Android 10, but i was soul-crashed after reading some information about the bit/binary value that samsung uses on its firmware(basically you cant downgrade if this value is not equal to your targeted frimware). However even though i feel scammed by Samsung, i would like to ask you the community as my final resort to guide me.
Is there some way i can trick SW REV checker or delete this partition containing this binary file?. Does "deleting" it affect my ability to boot into the download mode?
Click to expand...
Click to collapse
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp
JuanTamqd21 said:
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp
Click to expand...
Click to collapse
Hi, thank you for the reply.
Sorry for the late reply. I will try this today
JuanTamqd21 said:
you can downgrade by simply flashing system,kernel and vendor from android 10 on twrp
Click to expand...
Click to collapse
Okay. I am may be misunderstanding something because this way did not work for me. Do I have to manually extract files from the lz4 files?
{Temp_User} said:
Okay. I am may be misunderstanding something because this way did not work for me. Do I have to manually extract files from the lz4 files?
Click to expand...
Click to collapse
well, I can provide vendor and kernel in telegram. You can also get them by extracting lz4 files
make sure its from Android 10/Q/one ui 2.x firmware
I have with me the latest (previous) android 10 . I have extracted correctly ( used 7-zip zstd ) the lz4 files and flashed the vendor, system and kernel in that order.
upon reboot, I can not get past the splash screen. However i do see that an error appears on top left of my screen as CHECK FAIL binary 7(BOOT). The words are not clear though.
What did i do wrong?
JuanTamqd21 said:
well, I can provide vendor and kernel in telegram. You can also get them by extracting lz4 files
make sure its from Android 10/Q/one ui 2.x firmware
Click to expand...
Click to collapse
please provide an in-depth process?
Okay, so after a number of attempts i finally have android 10/Q on my phone. Keep in mind that i am not tech savvy, as all this was a guessing game(well not all of it)
I will share my story and hope it may be useful to others who intend to downgrade their android version.
SW REV ERRORSYou cannot and you should not change the bit version. If you see this error, it means you tried to flash a firmware or maybe just a boot file that is outdated or incompatible with the current secure boot loader.
With my limited knowledge, I went with what was easier for me at the time of writing this,
Flash latest firmware for model A505F,(yours may differ) using Odin.(SUCCESS)Boot into system normally.(make sure the OEM unlock is greyed out.Flash the latest custom recovery(TWRP or 'sky hawk recovery project', I chose the latter. )Boot into your recovery and Format data., also make advanced wipes. System kernel vendor Dalvik Cache Data.Pay attention to what exactly you are wiping.With your targeted firmware (A10) somewhere nearby, I recommend to use a reliable tool to extract the lz4 compressed file. I used this to get 'system.img' 'vendor.img' 'boot.img' . If you are on windows, look at the type column in your file explorer or enable 'view filename extension'.Flash/Install the image files in your recovery. Be patient.
Here is the tricky part for me. the boot loader wont accept this older kernel.(thus the boot loops).
A faster way to work around this, is installing a custom kernel that supports android 10. e.g. quantum kernel.
You may have to reboot a number of times before you can get past the splash screen. Be patient.Success, you now have a weird but working system. (I call it weird because the kernel you will use will carry along with its bugs e.g. camera fails, random reboots.)You can not update the system. this may be due to the different AP/CP/CSC/ match. This is not a step by step guide, i am only sharing with the public what i did to get my final point.
Of course this goes without saying that you are attempting a risky route and you the user shall carry all responsibility.
{Temp_User} said:
Okay, so after a number of attempts i finally have android 10/Q on my phone. Keep in mind that i am not tech savvy, as all this was a guessing game(well not all of it)
I will share my story and hope it may be useful to others who intend to downgrade their android version.
SW REV ERRORSYou cannot and you should not change the bit version. If you see this error, it means you tried to flash a firmware or maybe just a boot file that is outdated or incompatible with the current secure boot loader.
With my limited knowledge, I went with what was easier for me at the time of writing this,
Flash latest firmware for model A505F,(yours may differ) using Odin.(SUCCESS)Boot into system normally.(make sure the OEM unlock is greyed out.Flash the latest custom recovery(TWRP or 'sky hawk recovery project', I chose the latter. )Boot into your recovery and Format data., also make advanced wipes. System kernel vendor Dalvik Cache Data.Pay attention to what exactly you are wiping.With your targeted firmware (A10) somewhere nearby, I recommend to use a reliable tool to extract the lz4 compressed file. I used this to get 'system.img' 'vendor.img' 'boot.img' . If you are on windows, look at the type column in your file explorer or enable 'view filename extension'.Flash/Install the image files in your recovery. Be patient.
Here is the tricky part for me. the boot loader wont accept this older kernel.(thus the boot loops).
A faster way to work around this, is installing a custom kernel that supports android 10. e.g. quantum kernel.
You may have to reboot a number of times before you can get past the splash screen. Be patient.Success, you now have a weird but working system. (I call it weird because the kernel you will use will carry along with its bugs e.g. camera fails, random reboots.)You can not update the system. this may be due to the different AP/CP/CSC/ match. This is not a step by step guide, i am only sharing with the public what i did to get my final point.
Of course this goes without saying that you are attempting a risky route and you the user shall carry all responsibility.
Click to expand...
Click to collapse
Hello, you will not be able to downgrade your phone to Android 11, if it is not on theese firmware updates:
Of course, the reason is, that the binaries of newer updates are higher, than 7 (A505FNPUU7CUC2).
vmirrimv said:
Of course, the reason is, that the binaries of newer updates are higher, than 7 (A505FNPUU7CUC2).
Click to expand...
Click to collapse
So long as we both happy and got what we wanted. I finally have a working android 10 on my device(coming from a11)
vmirrimv said:
Hello, you will not be able to downgrade your phone to Android 11, if it is not on theese firmware updates:
Click to expand...
Click to collapse
You are correct. I gave up on changing the binaries after seeing it was impossible.
Camera should still work on custom android 10 one ui roms and GSI. I think I tested them before.