Avoid and pass by a fool and a madman
Great effort! thank you very much.
can you update the boot extractor from your previous post? i don't understand how to change the code u said here. thanks
jaygan93 said:
can you update the boot extractor from your previous post? i don't understand how to change the code u said here. thanks
Click to expand...
Click to collapse
It seems that many suffered from the payload_dumper, including me, and I'm thinking of a new extractor, something like that it's a standalone executable, containing all needed runtime libraries inside it so you don't need to install python/vc++, based on latest android sources, automatically detects many things, could be used universally on any ota for any brand, any version, and if it can't, it shows an warning and needed info if possible, at least.
Big problems to do this is that android build environment doesn't support windows (linux or macOS only and I don't use them), I can't spend much time on this, some phones such as black shark uses different their own codes and hide/never reveal those... etc...., so it requires a huge effort/time and I'm just thinking....
However, I will update the extractor or build a new extractor in any ways better, even though it takes some time.
wga0 said:
It seems that many suffered from the payload_dumper, including me, and I'm thinking of a new extractor, something like that it's a standalone executable, containing all needed runtime libraries inside it so you don't need to install python/vc++, based on latest android sources, automatically detects many things, could be used universally on any ota for any brand, any version, and if it can't, it shows an warning and needed info if possible, at least.
Big problems to do this is that android build environment doesn't support windows (linux or macOS only and I don't use them), I can't spend much time on this, some phones such as black shark uses different their own codes and hide/never reveal those... etc...., so it requires a huge effort/time and I'm just thinking....
However, I will update the extractor or build a new extractor in any ways better, even though it takes some time.
Click to expand...
Click to collapse
Yeah, actually i found out there is some payload dumper without instal phyton or something else and just an exe to extract the full ota payload.bin like in this post https://forum.xda-developers.com/mi-a2/how-to/guide-install-payload-bin-twrp-t3865319 i did try to extract the full ota an it did extracted all the img like boot, vendor, system etc. but i'm not sure that the system.img extracted from this payload dumper is useable or faulty one, so i'm not dare to flash it. Btw, thanks for the response i appreciate it. i hope you can find the best solution for us too.
It will get an unlock when it produces the firmware in a complex way. When it will flash the system partition and get lock again when the system is booting.
This is not necessary.
jaygan93 said:
Yeah, actually i found out there is some payload dumper without instal phyton or something else and just an exe to extract the full ota payload.bin like in this post https://forum.xda-developers.com/mi-a2/how-to/guide-install-payload-bin-twrp-t3865319 i did try to extract the full ota an it did extracted all the img like boot, vendor, system etc. but i'm not sure that the system.img extracted from this payload dumper is useable or faulty one, so i'm not dare to flash it. Btw, thanks for the response i appreciate it. i hope you can find the best solution for us too.
Click to expand...
Click to collapse
I'd tried them also, and they also generated some images corrupted when using on Black shark ota. I tried almost payload_dumper I could find at internet, only one, payload_dumper-master for incremental has the needed operation for full payload, and no one worked for incremental.
MCT_ said:
It will get an unlock when it produces the firmware in a complex way. When it will flash the system partition and get lock again when the system is booting.
This is not necessary.
Click to expand...
Click to collapse
I can't understand your word exactly, but the system never do lock/unlock during update. And... why are you talking that here? It has nothing to do with this.
{
"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"
}
com.blackshark.ota/com.blackshark.ota.ui.TestActivity
MCT_ said:
View attachment 5008907
com.blackshark.ota/com.blackshark.ota.ui.TestActivity
Click to expand...
Click to collapse
It seems that you're sending wrong letter to worng address... This thread is for image_extractor/payload_dumper
wga0 said:
It seems that you're sending wrong letter to worng address... This thread is for image_extractor/payload_dumper
Click to expand...
Click to collapse
I don't see any problems with it, other than checking the signature.
And I don't see any posts about how happy everyone is to use TWRP on their device.
MCT_ said:
I don't see any problems with it, other than checking the signature.
And I don't see any posts about how happy everyone is to use TWRP on their device.
Click to expand...
Click to collapse
then use it yourself and don't disturb others. This is not for TWRP, not for update as you did. No relation at all! If you want to help others, do it right way in right place. I will not answer you again sorry...
wga0 said:
then use it yourself and don't disturb others. This is not for TWRP, not for update as you did. No relation at all! If you want to help others, do it right way in right place. I will not answer you again sorry...
Click to expand...
Click to collapse
First you guys talked about how to break the integrity of the system, then began to flash twpr recovery, now take the topic to the section of how you are going to install the update despite the modems. All you are on is trying to install an update. You have disabled a lot of devices, but there is not a single img backup in the discussion topic to restore it. It feels like you're deliberately stalling.
MCT_ said:
First you guys talked about how to break the integrity of the system, then began to flash twpr recovery, now take the topic to the section of how you are going to install the update despite the modems. All you are on is trying to install an update. You have disabled a lot of devices, but there is not a single img backup in the discussion topic to restore it. It feels like you're deliberately stalling.
Click to expand...
Click to collapse
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
wga0 said:
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
Click to expand...
Click to collapse
This code is just a ".cmd " project and some draft entries from the "one-click" flashing engine using ADB.
wga0 said:
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
Click to expand...
Click to collapse
This guy seems to be high lol. he is actually accusing us of bricking his phone and many others deliberately. I never said flash TWRP but I guess he doesn't know the difference between flashing TWRP and booting it.
Anyways, just ignore him he is talking meaningless and talk about non related things in different threads.
KM7 said:
This guy seems to be high lol. he is actually accusing us of bricking his phone and many others deliberately. I never said flash TWRP but I guess he doesn't know the difference between flashing TWRP and booting it.
Anyways, just ignore him he is talking meaningless and talk about non related things in different threads.
Click to expand...
Click to collapse
When you get root, via /data/media/... there is a dependency of the partition with internal storage, but you do not mention this and suggest using flash in its various variations. :good:
I don't even have a development section:
My bootloader is closed, I'm waiting for an update.
I've tried everything here, from bs2pro firmware on bs2 to payload_dumper and update.
With Google's floating code, this won't work, or you'll end up in the stone age.
Code is constantly moving.
You must obtain superuser rights legally, via the server.
Why do you need ROOT if you don't have a BootLoader, Recovery and ROM ?
What would delete installation APKs from system/app without disabling services ?
You made a copy of the system in img format for two months, with ROOT license on Board.
wga0 said:
EDIT: I found that more images in the full Android 10 OTA are corrupted when extracted with the payload_dumper, even including the boot image and modem.img, which is critically related to boot. I write this urgently... and will update soon... (Plz use with REPLACE part, or with below modified code)
Please be careful when you use the payload_dumper for full payload.
I found the payload_dumper doesn't have all the operations needed. It supports only two operations, REPLACE_XZ(lzma compression), REPLACE_BZ(bz2 compression), but BlackShark full OTA requires REPLACE(no compression, bsdiff or other format) also, and it generates some images incorrectly. It doesn't show you an error or any sign of malfunction also.
It seems that using it for the boot image only is okay, but images such as vendor.img, system.img are not correctly generated and it can brick your phone.
You can use payload_dumper-master instead. It supports the REPLACE operation for full payload, although it requires the vc++14.0 to compile the bsdiff library. I think easy way is to copy the REPLACE part in payload_dumper-master to payload_dumper, and use that.
Or you can modify the boot_extractor I uploaded to extract all files. Just delete the search part (comparing partition name), then it will extract all images.
oh... you need to change one more part...
Code:
#SOURCE_BSDIFF for Black Shark
elif op.type == op.REPLACE:
if pat[:3] == b'BSD':
odata = bytes()
for ext in op.src_extents:
ofile.seek(ext.start_block*block_size)
odata += ofile.read(ext.num_blocks*block_size)
pat = bsdiff4.patch(odata,pat)
ndata = io.BytesIO(pat)
for ext in op.dst_extents:
nfile.seek(ext.start_block*block_size)
nfile.write( ndata.read(ext.num_blocks*block_size) )
This will work for all images, all OTA for other phones (universally), and for both full, incremental of course.
Click to expand...
Click to collapse
i wish i saw this before hard breaking my black shark 2 pro now it is stuck in EDL i bought it before 6 days and now i think i will throw it into the trash
abd96iq said:
i wish i saw this before hard breaking my black shark 2 pro now it is stuck in EDL i bought it before 6 days and now i think i will throw it into the trash
Click to expand...
Click to collapse
Salam bro, try to hold down volume down button + power button while you are in EDL mode "this might take upto 60 seconds". If this doesn’t work, then try holding volume down when your phone reboot. This should take you to fastboot, from there you can run my full restore Black Shark 2 Pro batch, which you can get it from here.
Hope this works for you, goodluck.
KM7 said:
Salam bro, try to hold down volume down button + power button while you are in EDL mode "this might take upto 60 seconds". If this doesn’t work, then try holding volume down when your phone reboot. This should take you to fastboot, from there you can run my full restore Black Shark 2 Pro batch, which you can get it from here.
Hope this works for you, goodluck.
Click to expand...
Click to collapse
I tried but unfortunately doesn't work bro
I have even contacted s-unlock team but to avail
I think i will throw it in trash .
I am really sad
Thank you bro
Related
WARNING!!!!!Use of the following has been know to cause bricks and/or loss of functions in most of the devices it was attempted on. Because of this, the Thread was permanently closed. However the files will remain to assist in further development. Additionally, there is no promise if any of the links still work. So if you choose to mess with these files, you do so knowing it will probably brick your device.
Moscow Desire, XDA Moderator*******************************************************************************
[Pudding]
WARNINGS: READ ALL OF THIS BEFORE CONTINUING
1. All phones You most likely will lose 4g data connectivity from using this, hopefully a workaround is on the horizon.
2. All phones This has received limited testing, use at your own risk and accept that there may be a risk of hard bricks now or in the future (Unless you get your SBK.)
3. All phones Charge your phone, all the way please.
4. Use at your own risk. Have a backup phone, insurance plan or other means of recovering from a possible brick or loss of functionality. You are using experimental software at your own risk.
Works/Does not work list
Sprint en/us 45.2.5: Warning: Loss of 4g connectivity very likely
Electrify 2.3.5: Danger: Untested, I do not own one and cannot test
Click to expand...
Click to collapse
Updates
8/30/2011 Added stock recovery image for those wishing to use pudding remover.
8/25/2011 Pudding remover added. This restores your stock bootloader. 4G will be restored but your phone will be locked again. This is only the bootloader, so system changes will not be removed (root, recovery, program data, etc). Having the custom recovery still installed with the locked bootloader may cause problems (soft-brick, you will need to use full sbf or re-unlock and flash back the stock recovery). will cause you to soft brick. You will need to reflash the unlocker to recover and either leave it unlocked or restore the stock recovery and use the pudding remover afterwards. Thank you tuxy for being the only one basically willing to test this.
8/16/2011 Just a quick update on the 4g issue, most likely this will go unresolved until your kernel source is released and someone with the appropriate skills in kernel hacking fixes your ATAGS passed by the bootloader. For now you can either be unlocked and use 3g, or locked and use Wimax/4g. Pick your poison, at least neither is a permanent thing.
Click to expand...
Click to collapse
Who does/doesn't need this.
You need this if:
1) You need to flash custom single partitions such as system, osh, boot.img, recovery, or data.
2) Mainly for testing custom kernels, see number one.
3) You have a real ROM with a custom kernel, like CM7 or MIUI, and want to flash it.
You don't need this if:
1) Number one in the last section doesn't make any sense to you or sounds like gibberish.
2) You wanna show your friends how much cooler or better than them you are.
3) You just want to install P-ROMs and Themes.
Click to expand...
Click to collapse
You want pudding for Photon? There is pudding in space too!
Pudding:
http://diamantephoto.com/photon_pudding.rar 1mb bootloader only
Fastboot:
Use this to unlock after flashing pudding sbf (not available), also to flash custom partitions.
Windows: Moto-fastboot for windows thanks to romracer. Direct Download Link
Linux/Mac: Moto-fastboot for linux in several flavors thanks to eval-.
RSD/Drivers/SBF_FLASH:
You may need to reinstall drivers after the unlock.
RSDLite 5.5 Download
http://mophoforum.com/Roms/rsdanddrivers.zip
64bit windows drivers
SBF_FLASH(*nix/Mac)
Pudding remover:
Directions:
1) Make sure you are on the stock Recovery. If not, flash the image I provided below using this command:
Code:
fastboot flash recovery stock_recovery.smg
2) Flash the nopudding4u sbf using RSDLite or sbf_flash.
3) Done
http://www.multiupload.com/A4KCLBTL3K - 3.6mb stock recovery image from CM5
http://diamantephoto.com/photon_nopudding4u.rar - 1mb bootloader only, stock locked bootloader. For those of you who want a quick way to return to 4G.
Howto:
Is your phone fully charged? This should be first thing you check whenever you flash anything.
0) Back up all your apps and anything else you want to keep that is stored in /data, YOU WILL LOSE ALL FILES IN /DATA
1) Flash the pudding sbf file via sbf_flash(*nix/Mac) or RSDLITE(Windows).
2) Get moto-fastboot in your $PATH or at least in the same directory as the command line you open.
3) Open a command line or well, linux users know what to do, in the folder with pudding.
4) Type moto-fastboot oem unlock
5) Look for the UNIQUE ID number and copy it, use copy or your fat fingers might mistype it.
6) Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED
7) Enjoy!
Here is a picture of the steps on a windows command line (yes, I renamed moto-fastboot to just fastboot on my PC.) The blurry bits are where YOUR unique ID shows/is entered.
{
"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"
}
Root:
A moto-fastboot flashable /system image with su already in /system/bin (pre-reooted) This is based of the system in Yay4jugg's thread (NB: you need to be unlocked to flash this .)
Instructions:
0) Make sure your phone is charged.
1) Boot your phone in to fastboot mode, connected to PC.
2) At the prompt/cmdline type moto-fastboot flash system system.img
3) Make sure you have superuser app installed from market.
4) Enjoy!
CWM:
Romracer's official CWM thread for Photon
Calkculin's CWM thread
A video guide on how to root and install CWM for unlocked Bootloaders by qbking77
Kernels:
Hewett Kernel
Shabby's OC kernel
Problems?:
1) Don't panic.
2) Stop panicing.
3). If you get the following error messages, try restarting the flash process from the start:
- The "secure_motorola_flash" interface could not be found the super-file is secure and for re-flash, the phone needs a super-file that is not secure and for reflash. (0x7066)
4) Just try and go through with the unlock process anyhow
5) Try a different USB port, this is most likely because windows will reinstall all the drivers.
6) Try a different version of RSD Lite.
7) Make sure you put your phone in to USB NONE before plugging it back in. If you do not do this your system will not install all the devices correctly. Alternately, try Motorola Phone Portal mode.
8) Last resort PM me with very specific information about your problem and if applicable screen shots from your computer or phone.
Big thanks to Yay4juggs and Edgan.
The attached file below is only for Electrify owners and is untested
MOD EDIT: Attachment Removed
Yea BL unlock and root without dock? I gotta sleep, hope christmas comes in the morning!! I get some cash soon, gonna buy you guys a round! Man you guys are persisting and pushing tonight...
-DJ
Grats to everyone involved. You did amazing work.
Sent from my MB855 using XDA App
My stomach is ready. Thanks for the efforts and the work into this, we are grateful.
Chocolate pudding.
Has anyone tried this?
Sent from my MB855 using XDA App
evonate said:
Has anyone tried this?
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I beleive its still being tested isnt it?
Hey you,
My name is Rick, and I am never gonna give you up. All of you have let me down, made me cry, and spent all day telling lies and hurting people. Your heart's been aching but you're too shy to say it. Honestly, have any of you ever gotten this from any other guy? I mean, I guess it's fun knowing the game and playing it, but you all take to a whole new level. Inside we both know what's been going on.
Don't be a stranger to love. You know the rules and so do I. I'm pretty much perfect. I have been nominated for a Grammy, and had a #1 hit. What games do you play, other than "running around deserting people"? And if you ask me how I’m feeling, I also have a banging hot girlfriend (We’ve known each other for SO long). I just wanted to tell you how I was feeling. I gotta make you understand.
Sent from my MB855 using XDA Premium App
newalker91 said:
When this is official, make sure to post this thread about 50 times in the Evo4G/3D sections. They've been talking trash since day one about this phone because the bootloader is locked.
Click to expand...
Click to collapse
theres a handful of people that actually knew anything about the photon and motorolas in general. i knew it wouldnt take long....im selling my nexus s as we speak, im that confident we will see awesomeness very soon.
newalker91 said:
When this is official, make sure to post this thread about 50 times in the Evo4G/3D sections. They've been talking trash since day one about this phone because the bootloader is locked.
Click to expand...
Click to collapse
I'll leave that up to you I don't own a Photon or Evo.
I was feeling good about 20 min ago. I have root (dock method) and started to get off the high that created figuring that it would be a while before somone unlocked the bootloader.......AHhhhhhh. Im gonna be checking this damn thread all night.......LMAO
ooxcfhxoo said:
I was feeling good about 20 min ago. I have root (dock method) and started to get off the high that created figuring that it would be a while before somone unlocked the bootloader.......AHhhhhhh. Im gonna be checking this damn thread all night.......LMAO
Click to expand...
Click to collapse
it is very exciting. i saw this right here and sold my nexus s this is my Photon in the picture btw...
Huge thanks to the2dcour for making this happen!!!!
what are the chances of getting the sbf tonight from someone?
ooxcfhxoo said:
what are the chances of getting the sbf tonight from someone?
Click to expand...
Click to collapse
0% check back tomorrow around noon EST.
I was thinking along the lines of a small (coffee sized) donation?....on say..........Newbury Street
ooxcfhxoo said:
I was thinking along the lines of a small (coffee sized) donation?
Click to expand...
Click to collapse
I _never_ ask for donations so don't feel obligated to, the work I do is a lot less intensive and technical than people imagine. As I've said before 99% credit belongs to moto for making this, 0.5% to the leaks/people who provide the leaks, and I'm happy to take the last 0.5% credit for being the script kiddie that assembles the pudding.
Before the files are posted for the public to download, we need to make sure that there are no side effects from this. Yay4Juggs and the rest of the testers should take their time and check to see if anything else was affected. Maybe if there was a ROM or 2 that they could test to see that it works that would be great.
I am already excited today to find out about dockless rooting but if the unlocked bootloader can be released, that would be a double whammie weekend.
ericdabbs said:
Before the files are posted for the public to download, we need to make sure that there are no side effects from this. Yay4Juggs and the rest of the testers should take their time and check to see if anything else was affected. Maybe if there was a ROM or 2 that they could test to see that it works that would be great.
I am already excited today to find out about dockless rooting but if the unlocked bootloader can be released, that would be a double whammie weekend.
Click to expand...
Click to collapse
That's precisely the reason that it hasn't been posted yet. There still may be side effects in the future as we are seeing with the atrix. Be warned, the unlock is irreversible and you should be careful. Most people will not need an unlocked bootloader. When you get custom kernels and CM that is another matter. People who dev this stuff can certainly use the unlock wisely. Till there is a reason for you to unlock I wouldn't bother unless you are adventurous and have a spare phone 99% of the reason people need / want unlock is for a custom kernel the other 1% is for using fastboot or non-bootstrap cwm. Hopefully you will have a non-bootstrap CWM soon. I'm rambling so I'll stop talking.
Im waiting and could care less if it bricked my phone......I'll recover from it. I'm prepared.
I would be using ......fastboot or a non-bootstrap cwm (when one is available).
i understand CWM is possible now and the reason for me unlocking my boot-loader is to get it done before someone puts the brakes on it.
I like to have access to the things i own based on principal. Its the same reason why i refuse to pay twice for the same data stream i already pay for in order to tether.
ooxcfhxoo said:
Im waiting and could care less if it bricked my phone......I'll recover from it. I'm prepared.
Click to expand...
Click to collapse
Coming tomorrow, I promise.
Need link to download the specific software specified in the title of this thread. Came across the one loaded on Google by another xda member but having difficulties downloading it. If you have it mirrored to another cloud service please provide me with the link. I am mostly gunning to get my hands on all of the .img files which come inside it so that I may review them via a hex editor and unlock my bootloader the sneaky way since Huawei refuses to reply back to my emails. Many thanks in advance.
Update: I was able to get my hands on the update.app file. So now will begin extraction and making my changes to hack the bootloader status on my device. If Huawei has responded back to you with your proper bootloader unlock code then you were fortunate. I myself have run out of patience with them and am now handling this on my own personal level.
Modding.MyMind said:
Need link to download the specific software specified in the title of this thread. Came across the one loaded on Google by another xda member but having difficulties downloading it. If you have it mirrored to another cloud service please provide me with the link. I am mostly gunning to get my hands on all of the .img files which come inside it so that I may review them via a hex editor and unlock my bootloader the sneaky way since Huawei refuses to reply back to my emails. Many thanks in advance.
Update: I was able to get my hands on the update.app file. So now will begin extraction and making my changes to hack the bootloader status on my device. If Huawei has responded back to you with your proper bootloader unlock code then you were fortunate. I myself have run out of patience with them and am now handling this on my own personal level.
Click to expand...
Click to collapse
Having trouble getting the bootloader unlock code? Try this:
Most of the issues are that emails sent outside of Shenzhen China business time during the week are not answered. They go into an email black hole. You'd have to send in the bootloader unlock request email really late here in the US or set up some way to send your email later automatically like I did with the Chrome extension Boomerang to get the code for my second HAM2. Currently sending in a request around 9pm EST to 4am EST Sunday - Thursday is the best time to email for the unlock code Sun-Thurs corresponds to Monday-Friday at Huawei in China.
I have emailed outside of those times and not gotten a response. After figuring out the time difference and setting up boomerang for an automated send later feature with my email the code arrived a couple hours after it was sent and I saw it when I woke up the next morning.
Sent from my MT2L03 using Tapatalk
@arcadesdude, thanks for your input, but unfortunately that route has failed me as well. Been at it with these emails since late last year. My guess is that my emails are getting lost in middle of a bunch of other emails they may be receiving or I'm going to their spam mail which they probably ignore. Either case, all attempts have not been successful. I found the EFI image and boot image inside the update.app last night. So far so good as it looks like I can easily hack this update and finally get my bootloader unlocked so I may do what I need to do with it.
Modding.MyMind said:
@arcadesdude, thanks for your input, but unfortunately that route has failed me as well. Been at it with these emails since late last year. My guess is that my emails are getting lost in middle of a bunch of other emails they may be receiving or I'm going to their spam mail which they probably ignore. Either case, all attempts have not been successful. I found the EFI image and boot image inside the update.app last night. So far so good as it looks like I can easily hack this update and finally get my bootloader unlocked so I may do what I need to do with it.
Click to expand...
Click to collapse
You can unlock the bootloader without the bootloader unlock code?
Did you try another email address? Another member on here used another address and got through to Huawei.
Sent from my MT2L03 using Tapatalk
arcadesdude said:
You can unlock the bootloader without the bootloader unlock code?
Did you try another email address? Another member on here used another address and got through to Huawei.
Sent from my MT2L03 using Tapatalk
Click to expand...
Click to collapse
No, the bootloader code is still required. All I am going to do is modify the source via a hex editor so that I can input a code of my choosing and force it to accept that code and thus unlock my bootloader. That is very possible . Should of done this already but I wanted to give Huawei a chance - but they failed.
Modding.MyMind said:
No, the bootloader code is still required. All I am going to do is modify the source via a hex editor so that I can input a code of my choosing and force it to accept that code and thus unlock my bootloader. That is very possible . Should of done this already but I wanted to give Huawei a chance - but they failed.
Click to expand...
Click to collapse
I didn't know you could do that. Is it essentially just flashing your modified bootloader partition to the phone using adb like we flash the recovery partition?
arcadesdude said:
I didn't know you could do that. Is it essentially just flashing your modified bootloader partition to the phone using adb like we flash the recovery partition?
Click to expand...
Click to collapse
Pretty much, but not with adb. Using fastboot.
also, i guess you also need disable the verification chain? but how? I heard it probably start from very beginning, ROM, a real read only rom. if you flash hacked aboot, sbl probably refuse to boot it, right?
xordos said:
also, i guess you also need disable the verification chain? but how? I heard it probably start from very beginning, ROM, a real read only rom. if you flash hacked aboot, sbl probably refuse to boot it, right?
Click to expand...
Click to collapse
With a bootloader being locked you are presumably limited on what can and cannot be flashed. With that in mind should a modification be incorrectly done for a device with a locked bootloader then it would be safe to say that the flash would be denied and no harm done. Because I will be modifying the source to accept my personal code then this will not have any affect towards flashing. The device will even accept it. Then, when I enter my code and reboot, the device will simply say it is unlocked. The only catch to this though is that if I flash back to the original then the bootloader should technically relock itself. I will open a thread on this procedure down the road when I get time and even include my mods so others may compare it with the stock to see the differences.
Modding.MyMind said:
With a bootloader being locked you are presumably limited on what can and cannot be flashed. With that in mind should a modification be incorrectly done for a device with a locked bootloader then it would be safe to say that the flash would be denied and no harm done. Because I will be modifying the source to accept my personal code then this will not have any affect towards flashing. The device will even accept it. Then, when I enter my code and reboot, the device will simply say it is unlocked. The only catch to this though is that if I flash back to the original then the bootloader should technically relock itself. I will open a thread on this procedure down the road when I get time and even include my mods so others may compare it with the stock to see the differences.
Click to expand...
Click to collapse
Regarding the limitation, early I thought you are going to modify/repackage the UPDATE.APP, as that way, if (a big if) it works, ideally you can flash to any partition. (There is some thread in xda that discussion about read/repackage the huawei UPDATE.APP)
But as we discussed briefly long time back, this whole thing is really really risky, if the booting path to fastboot got damage, then pretty much the phone is hard bricked.
Probably if you stick with flash with fastboot, then the risk will be lesser but man, this is scary stuff..
Regarding the validation chain, I got info from following article:
http://www.newandroidbook.com/Articles/aboot.html
A few paragraph after the Figure One.
Let's see...
PS, maybe you can continue try some different email address and sent at correct time to Huawei for the code...
PS2, another thought, maybe inject a superSU to the UPDATE.APP system image will work? not sure how strict they are validating when flashing UPDATE.APP and/or when booting the system partition.
xordos said:
Regarding the limitation, early I thought you are going to modify/repackage the UPDATE.APP, as that way, if (a big if) it works, ideally you can flash to any partition. (There is some thread in xda that discussion about read/repackage the huawei UPDATE.APP)
But as we discussed briefly long time back, this whole thing is really really risky, if the booting path to fastboot got damage, then pretty much the phone is hard bricked.
Probably if you stick with flash with fastboot, then the risk will be lesser but man, this is scary stuff..
Regarding the validation chain, I got info from following article:
http://www.newandroidbook.com/Articles/aboot.html
A few paragraph after the Figure One.
Let's see...
PS, maybe you can continue try some different email address and sent at correct time to Huawei for the code...
Click to expand...
Click to collapse
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Modding.MyMind said:
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Click to expand...
Click to collapse
Just curious, what are you planning to do that requires an unlocked bootloader?
ScoobSTi said:
Just curious, what are you planning to do that requires an unlocked bootloader?
Click to expand...
Click to collapse
Something lol
I'm not sure why you can't get the code from Huawei ...but I'm kinda glad you can't. seems your gathering nice info about this phone.
Sent from my MT2L03 using XDA Free mobile app
Modding.MyMind said:
Something lol
Click to expand...
Click to collapse
Just in case you're being super extremely nice and kind and trying to make a ROM for us, the other developer has hit a huge roadblock on CM11/12 you should know about.
ScoobSTi said:
Just in case you're being super extremely nice and kind and trying to make a ROM for us, the other developer has hit a huge roadblock on CM11/12 you should know about.
Click to expand...
Click to collapse
Even he is not plan to build CM, but as the man who build first recovery for us, I think he wont stop until he can play with his own baby in his phone.
Modding.MyMind said:
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Click to expand...
Click to collapse
1. How are you going to flash image via fastboot if your bootloader is locked?
2. You have to hack fastboot image to pass throuth unlock code verification without or with some random code. But even if you do so, you won't be able to flash fastboot image via fastboot even with unlocked bootloader.
I would'nt touch fastboot at all 'cause it's a high risk to get a hard brick.
I have found unlock code in some partition of my device, but I dunno was it there initially or was written there after unlocking. If the first case is and fastboot just compares entered code with saved one in device, then you can try to make update.app with injected su, as xordos offered, to be able to read this partition.
Injecting su into the update.app woukdnt work. The update.app has it's own crc and such. So to simply say, it won't work. You also answered your questions with remarks 1 and 2. One exception is that yes, you can flash the image. As for risks, it's only there if you mess something up - development typically is about taking risks . The fastboot image won't technically brick the device anyways. At best a soft brick may occur, but to be honest since "bricking" is up for discussion; bricking can occur simply by making a change to the build.prop file and not fixing it's permissions prior to rebooting. Unless you "hard" brick the device, then it can always be recovered.
You said the image or images can't be flashed with a locked bootloader, while yes is technically true, but understand that it isn't 100%, because you see, when your device recieves an update initially the devices bootloader is expected to be locked, right? Yet, magically enough the update goes through, the phone reboots, you either hate or love the new update. Something to think about before actually saying an image can't be flashed . Instead, I would have you ask yourself, "how?".
xordos said:
Even he is not plan to build CM, but as the man who build first recovery for us, I think he wont stop until he can play with his own baby in his phone.
Click to expand...
Click to collapse
And best believe, I want to play
It's not on the net anywhere either, google is not working for the OT Elevate. There are no custom ROMs for the OT Elevate either.
I know that someone has one of these OT Elevate 5017B phones lying around somewhere. Post a stock ROM for download. People are suffering from bricks and soft-bricks. HELP more, we need to start a project making an attempt to catalog stock ROMs for every android device on earth.
There needs to be a larger archive of these ROMS. iOS developers are killing you. They have a database of all of the iOS firmwares, and there is a database of custom firmwares even for the iPhone 6S.
I know that the iPhone's situation is different, that one company designs the hardware and the software, and that everything is proprietary. I also feel there are too many companies making android phones. competition is one thing, but security of an OS is another. different phones from the same year with older versions of the OS on them, not good.
Marshmellow has been released and there are still 2016 phone releases with 4.5 OS on them. That's not secure. Why can't we make Android more secure by building better custom ROMs for more devices? I know there is a big shortage of developers, but you can recruit. Maybe even get funded by an organization, research grant?
Everyone needs more ROMs. Especially for Alcatel OT Elevate. Let's do something about this.
On 3. 1-2-3, Go Team!!!! :highfive: Let's Get It!
I have one of those Alcatel OneTouch phones right now, and I agree completely upon the notion for a catalog of all android devices that can be flashed.
@mU$!c @tyrex420
These Alcatel devices can only get attention if developers have them in their hands to work with. These devices are running a MediaTek SoC and not many developers like to work with those phones because of a lack of source code to work with or incomplete source in some cases. Yes you are correct in saying that Apple is different as it's one software, one hardware but you have to understand Google only set the stage and the companies do the rest. Not every company is Samsung or Sony. Alcatel has a tool which is really good called Mobile Upgrade Tool which has the factory ROM for their devices (which imho they need work on getting those newer devices supported). It works well if you haven't done much modification to your phone. Now the thing is that when those companies take the phones and modify them in some way like in locking the bootloader or hiding fastboot mode (Tracfone,MetroPCS), there's not much that a developer can do about that. Also those companies do not have that same support tool that Alcatel has which re-downloads the factory ROM because they are modified in some way.
Here's the good part about the phone running a MTK SoC. There are third-party tools such as MTK Droid Tools or SmartPhoneFlashTool (SPFT) which enables the users to make factory backups of their ROMs in the event that their devices suffers from a bootloop. What you can now do is become that developer that you are asking for to work on your phone and make something out of it. Be the first to upload a flashable factory ROM for your phone. Create a thread where users can come and post their issues and assist each other positively. It's nothing hard to do unless as I said before the company locks some part of the phone and makes these tools useless. By the way, MTK Droid Tools developer dropped support at Jelly Bean so KitKat and up won't work with the tool as it should.
Again, yes I agree with you in saying it would be nice for a users to find a compilation of ROMs that they can just follow instructions and flash but the thing is source code and users themselves not knowing how to use the tools mentioned above. If you want you can ask me for help in guiding you on how to use the tools. I've been doing this for 3 years now working with MTK and I'm learning something new everyday.
Sorry for my long reply, I hope to see a reply from you concerning getting a factory ROM for this device maybe a thread similar to mine .
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
bg260 said:
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
Click to expand...
Click to collapse
You're welcome .
kirito9 said:
You're welcome .
Click to expand...
Click to collapse
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
bg260 said:
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
Click to expand...
Click to collapse
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
kirito9 said:
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
Click to expand...
Click to collapse
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
bg260 said:
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
Click to expand...
Click to collapse
Yeah although the information is quite old still useful.
Root with Kingroot and backup with flashify haha. But won't you need the unlocked bootloader to root?
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
bg260 said:
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
Click to expand...
Click to collapse
Ahh cheap phone problems. Let me know if you get through.
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
{
"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"
}
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
bg260 said:
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
View attachment 3906591
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
Click to expand...
Click to collapse
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
kirito9 said:
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
Click to expand...
Click to collapse
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
bg260 said:
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
Click to expand...
Click to collapse
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
kirito9 said:
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
Click to expand...
Click to collapse
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
bg260 said:
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
Click to expand...
Click to collapse
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
kirito9 said:
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
Click to expand...
Click to collapse
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
bg260 said:
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
Click to expand...
Click to collapse
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
kirito9 said:
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
Click to expand...
Click to collapse
See if this is what you need. Created it with DiskInfo Pro. I used a different machine and mounted the system image fine. I thought it was a bad copy because the Build.prop displayed as broken. Then I realized it was just a symlink to the actual build.prop in custpack. At any rate, there's a copy of the build.prop in there as well.
View attachment build.prop-partitions-5017b.zip
DEPRECATED
This firmware is old and deprecated.
See the below link for new firmware and a better root method.
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
You can just flash the BL_ tarball if you don't want to install a new system
but want the better screen and modem drivers.
PART 2: FIRMWARE RELOADED
I have done extensive research into the issues reported by those of you who are still experiencing screen issues.
I was unable to reproduce the screen issue on my then-current firmware with this update.
Not being content to leave people with buggy screens, I learned as much as I could about the s8 firmware.
This is what I did with that information.
Flashable Custom Firmware Package For ALL SM-G950U/U1 ON US CARRIERS
If you have a non-us G950U and want to install this pm me or ask in the thread and ill make one. Its very simple but I wanted to get this out to everyone else ASAP
NOTICE!
This an UPDATE (and More) to the Green/Garbled Screen Issue firmware.
There is NEW firmware to download below, and everyone who is rooted should read on, even if you installed the previous version.
Background
At the core of the issue with the garbled screen, modem panics, and sd card issues are two central themes: Bugs, and Incompatibilities. The S8 family of phones was fraught with issues early in its release, including the infamous "Red Tint', Fingerprint scanner malfunctions, mysteriously poor battery life, and surely a bunch of smaller others. Many of these bugs were caused by issues in the device's underlying firmware. Like most devices, Samsung has worked to fix these bugs and improve device performance throughout the phones lifetime for sale in public.
Root Bugs
The problem was unfortunately worse for users of one of the rooting methods for the S8. The biggest reason for this is that in order to relax security constraints enough to make rooting possible, a "non-user oriented", "factory" combination firmware was used. This firmware, being designed apparently for configuration/repair processes inside a factory, was not tuned to the normal level as the public firmware, likely did not go through the same testing, and ultimately any bugs unique to this "Combination" firmware that did not directly affect basic functionality or also stock were probably largely initially ignored.
This is where most of the issues that you all have had come from.
Finding a Solution
As I was unable to reproduce the issue on my device without resorting to the original firmware shipped out with the root method I used, I decided to think about what made my device different than the other devices reporting these issues. While sure we may have slightly varying hardware and that may contribute to these issues as well. What I am absolutely certain of is that most of us have different releases of software from each other. Not only have people essentially ad-hoc upgraded from the original firmware they rooted with until now, many have not upgraded at all or, only partially upgraded (such as with the pervious version of this).
While I could have simply packaged up my firmware/bootloader flashfire backup, I decided to take it a step further.
THE GOODS
Without further ado, I present to you:
S8Root Improved: A SM-G950U1 Custom Firmware Package for Root Users
This package contains a custom mix of the latest AQH3 STOCK (not combination) firmware used wherever possible with the Necessary boot/kernel images from the combination firmware necessary to keep root working with permissive SELinux. It contains all of the improvements from the previous version, and many more.
RESULTS
I can only speak for myself, but the results I experienced were amazing:
- Better UI Responsiveness.
Things surprise me how they move
- Sharper/brighter screen colors
I thought it couldn't get better than the last version but it has! Everything just looks crisper and are super bright without being oversaturated like with the Adaptie Mode.
- POSSIBLY Improved LTE network connectivity.
Note I said POSSIBLY. I personally regularly experienced 8-10Mb/s download bumps and 2-3Mb/s upload bumps in LTE while moving back and forth from this new firmware. I have my LTE radio locked to a specific channel (there are two i pick up at my place and one is terrible) and I carefully measured -107 to -112 dBm RSRP and -13 to -14 dB RSRQ prior to each measurement. I almost left this out but I figured it would be better to give you the information with no conclusion either way. It ABSOLUTELY could be Atmospheric changes, Traffic level changes, or any other of a million thins. YMMV
- Could POTENTIALLY still any remaining fix long-standing SDCard issues
I did not experience this, but had a few reports from users that did. The same pieces used in that version that would touch SDcard usage are used here, so that fix/improvement will carry over.
DISCLAIMER
Unfortunately proving beyond any shadow of a doubt that this package fixes the issue was impossible . I have TRIED AND TRIED AND TRIED to trigger the screen issues, including tweaking on and off every setting (auto brightness, multiple DPIs, different graphs modes, etc) I could get my hands on and it just was not happening. I used every software/systems trick I could think of to break this again, and I was completely unable to tickle the bug on this firmware, despite being able to reliably trigger it almost on command using my previous firmware.
The only thing left to do is either:
- Get the source from samsung, fix the bug myself, and get them to sign my new kernel image with their key so our locked bootloaders would allow it (HAHA I DOUBT IT)
- Acquire a large fleet of S8s (and S8+s) to run distributed integration testing (like the kind Android use at Google). Well if someone wants to buy me a few dozen s8s and s8+s (each) sure I'll take a month off work and squash this, but otherwise not gonna happen either.
If it STILL happens for you, I'm sorry.
I have done everything I can think of, and if it happens to you and you have suggestions, I'm all ears.
BUT HEY, but this is XDA right? Land of mods like Xposed which will brick one persons device and work flawlessly on the identical one next to it. And we love Xposed don't we?
Despite absolutely hilarious comments to the contrary, this package absolutely meets the (aka "BugFix") as well as just about any android update ever does, given the wide variety of environments, usecases and software configurations out there. I surely hope that this works for you.
Instructions
1) Download the package from the link above.
- Here it is Again for good measure.
2) Reboot into download mode and flash using Comsy Odin
Thats it! I packaged this in a way to make the process as smooth as possible.
There is NO reinstall, NO wipe of any kind, nor ANY further work on your part needed to install and use this.
The file size is small so the download is fast, and again, there is NO WIPE or config change needed.
if (for some inexplicable reason) you want to roll back, or go to 100% stock sans root, that process should not be made any more difficult as well.
Legacy Information
If you were here before and either looked at or downloaded the previous version, AND YOU HAVE NO QUESTIONS you can skip this part.
If you have questions, please read through to the end of the post before asking them, as I tried to answer as many as I could before hand and all of this information still applies.
WHAT IT IS NOT:
I wanted to outline a few things it is NOT about, to make a valliant effort to stem off the flow of questions before they begin (ha!):
NOT: A new Stock ROM for Your Phone
THIS IS NOT A FULL OS BUILD! DO NOT DOWNLOAD THE WHOLE THING AND FLASH IT EXPECTING AN ENTIRELY UPGRADED OS.
There is no full stock AQI1 image I have found. Believe me I looked a bunch of places after I found it
NOT: Oreo Early Preview
Given the predictions that the next release from Samsung would likely be Oreo, there was some initial over excitement. This wound up being NOT the case and if you read at least current Samsung Oreo projections they are predicting AQB now.
NOT: A Fix for the 80% Battery Issue
I know this is completely futile to hope for but:
THIS DOES NOT FIX THE 80% BATTERY ISSUE!!!!
NO WE DO NOT HAVE A FIX FOR THAT OR ONE COMING ANY TIME SOON!
YES SOME PEOPLE ARE STILL TRYING!
PLEASE DO NOT ASK! OFF TOPIC FOR THS THREAD
NOT: Currently Tested by ANYONE but ME
Since the moment I installed this I have not had ONE SINGLE screen issue, where previously I would have them several times throughout the day (at least 3 sometimes upwards of 6). For the case of ME and MY device, I am confident in declaring that this boot ROM does not have the same kernel bug that was causing the issue on the boot.img provided as part of your traditional root method.
NOTE: This is for the s8 G950 US Snapdragon models ONLY! Do NOT Flash this on your exynos, your Chinese/HK S8, your N8, your MOTO RAZR flip phone, whatever else you have. Kernels/boot.img files are very device specific and you will surely break it if not completely brick it.
DISCLAIMER:
YOUR WARRANTY IS ALREADY VOID if you are paying attention and are doing this to fix bugs with the existing sampwnd root.
HOWEVER IT IS EVEN VOIDER NOW. FLASH THUS TO YOUR DEVICE AT YOUR OWN RISK!
and if you break it I AM NOT RESPONSIBLE! FLASH AT YOUR OWN RISK!
As I said I have not tested this anywhere but my phone as I dont have any other s8s nor do I have access to any locally. I hope it works for you as well as it has for me.
STEPS
Download Boot Image
Use the URL here to Download the AQI1 boot.img file: Go Download the New Hotness
Prepare Phone for Flashing in FlashFire
If you did not download it on your phone, copy it somewhere FlashFire can see it.
Flash it
Open up FlashFire
Hit the "+" button
Select the "Flash Firmware Package" option, NOT the "Flash Zip or OTA" option!
You should see a popup window thing that has a checkbox next to the word BOOT, with "boot.img, 22MiB" underneath.
Make sure the checkbox is checked.
Make sure that it says BOOT above boot.img.
I have no idea if its possible for this to get messed up, but BOOT implies flashing the BOOT partition so if it says something else you are headed towards brick town, abort immediately.
Press the Check mark at the top right corner once you have confirmed the two things above.
MAKE SURE EVER ROOT IS DISABLED!!!
Click on the "Reboot" box, and choose "Recovery". MAKE SURE PRESERVE RECOVERY IS NOT CHECKED!
Back at the main menu, click the lightening bolt next to the word FLASH. Confirm.
Wait for FlashFire to do its thing. Sometimes it takes a minute for FF to wake up and start flashing. Occasionally for me it never happens, if this happens DO NOT PANIC ITS FINE. Hold down power+volDown until you eventually wind up in upload mode, then just reboot normally and everything will come back fine.
When FlashFire finishes (it will go really fast, the image is only 22MB we arent flashing a 5GB system here), it will auto-reboot your device into the recovery men
Select Wipe Cache and Confirm
This will wipe cache which is fine and safe. Again maybe not needed, feel free to skip if you know what you are doing. If you mess up and accidentally click factory reset instead, please tell me so I can laugh at you.
Reboot into a Clear New World
Select reboot and boot the system normally. If you formatted the cache partition above, it will take a little longer to start your phone. This is just the first time per normal.
Thats it! Welcome to the world of clear screens and bright colors. It could be a total placebo effect but I actually think this kernel drives the display better sometimes.
Please let me know what you think, and if this works for you. I wi;; be here for a while to answer questions or fix anything i typoed above or whatever.
FYI: A s8+ thread is coming too, as I sprung for purchasing both downloads to be an equal opportunity XDAer (at least with US flagship Samsung devices lol) but since I have an s8 and thus had the files locally already I made this one first
@jhofseth for nerding out with me the last few nights on trying crazy **** to get a bootloader unlock which prompted me to dig at this in the first place
Most of all, all of the tons of you who have made so many aewesome mods, themes, apps, what have you that I use every day and that make me enjoy my device all the more. I could not be happier to have the opportunity to give back a little.
Here is the restof the s8 combo firm if you are interested, but don't just flash this as its not a full OS:
EDIT: DOWNLOAD THE NEW ONE ABOVE
Can I Get The Link To The S8+ Boot im willing to try it
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Coming very soon I promise! 10m max
Ok thanks
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Its up now! https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673815
whats the bootloader verison? it can be found by booting into download mode manually.
Cameron581 said:
whats the bootloader verison? it can be found by booting into download mode manually.
Click to expand...
Click to collapse
This isn't a bootloader change, it's boot.img which is the kernel and root filesystem essentially
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
mweinbach said:
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
Click to expand...
Click to collapse
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
wildermjs8 said:
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
Click to expand...
Click to collapse
i mean legally a warranty can not be void through software modifications unless it causes physical damage to the device. Since the efuse was not tripped no physical damage has been caused and no warranties have legally been void.
I had the green screen/graphics corruption after flashing this still...
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
wildermjs8 said:
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
Click to expand...
Click to collapse
I have auto brightness off and still get it here and there.
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
wildermjs8 said:
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
Click to expand...
Click to collapse
We flash the tar in the AP slot correct?
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
Yep
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Seems to be running better to me. Thanks bro
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
It actually does not matter, as Odin will do the right thing no matter what.
Sorry I should have made that clear. I will update the op to make that clear
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
Nope, only need the tar file bud. The old boot.img file is just basically the previous version of this.
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
The old image is actually part of the new tar, do you will have it anyway . I packaged it in Odin this time because there are some pieces of firmware FF either can't or warns against using it for. Plus one clean simple tar seemed easier, no?
Do you see the boot.img in the op? I thought I nixed all the instances of the link but I may have missed one.
I almost rewrote all the old text to reflect now but it felt like editing history so I tried to preserve what made the most sense still. It sounds like it's still a little confusing sobrskr another crack at it shortly.
Please let me know if you have any trouble! I'll be here to help all evening
I have the variant of this phone by boost Mobile. There is so far as I can tell no way to do a normal bootloader unlock procedure on this device. So I have been trying to experiment trying to break or disable verity. Before I get any more excited, let me make sure I understand correctly. None of the partitions for example system, or boot or recovery cannot be flashed while verity is enabled, most certainly if you don't have root access on the device.
Well somehow, and I have yet to be able to repeat this, I was able to flash a system image in Odin, but the device would not boot because I successfully flashed it but because the other binaries did not match the signature of the "custom system". While doing this I was also able to downgrade from binary 8 to binary 7 (android 10 to 9). So I guess my question is, if I am able to repeat this process then how good is it that I am able to flash a system image and How likely would I be able to continue flashing the other partitions? Before I get into detail on how I managed or how I think I managed to do this I want to make sure that this can actually go anywhere before I waste my time.
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
i rooted it
{
"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"
}
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
DragonFire1024 said:
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
Click to expand...
Click to collapse
What files did you flash through odin?
sikkinixx said:
What files did you flash through odin?
Click to expand...
Click to collapse
only the ones I am able. Still haven't figured out how i downgraded from 10 to 9. I flashed the stock firmware (AIO firmware. apparently all carrier stock firmware can be flashed, regardless if its Boost Mobile [BST]). I however did flash the modem (CP) with modem.bin and modem_debug.bin from a combination firmware that's supposed to be factory binaries (which I can't flash any others from that combination because it tells me to get permission to flash them lol).
Im glad someone is trying this I just frp unlocked a galaxy s7 and im feeling confident about rooting this sm-a102u but its what i am using for my every internet access but Im cheering for you DragonFire1 You Got this !
majored said:
Im glad someone is trying this I just frp unlocked a galaxy s7 and im feeling confident about rooting this sm-a102u but its what i am using for my every internet access but Im cheering for you DragonFire1 You Got this !
Click to expand...
Click to collapse
I'm quite sure I don't. I've been able to mimic what I've been able to flash to the device. But regardless it doesn't matter because no matter what way I do or what I flash it fails all kinds of check sums. A lot of things do flash, but a bunch of red text comes across the screen that tells me about binary checks sum errors.but the images do flash to the device but until you restore the firmware that was previously on there it will never work again. I really do hate boost Mobile.
DragonFire1024 said:
I'm quite sure I don't. I've been able to mimic what I've been able to flash to the device. But regardless it doesn't matter because no matter what way I do or what I flash it fails all kinds of check sums. A lot of things do flash, but a bunch of red text comes across the screen that tells me about binary checks sum errors.but the images do flash to the device but until you restore the firmware that was previously on there it will never work again. I really do hate boost Mobile.
Click to expand...
Click to collapse
interesting well now that you mention that if you flash similar firmware cant you essentially add whats misssing i mean ive flashed over an install and still had wifi password saved and some apps im confusing myself now but im pretty sure thats how it went
majored said:
interesting well now that you mention that if you flash similar firmware cant you essentially add whats misssing i mean ive flashed over an install and still had wifi password saved and some apps im confusing myself now but im pretty sure thats how it went
Click to expand...
Click to collapse
It depends. So far I have only been able to use a different modem image and nothing else. Even if I flash the images that do match the flashed files that fail checksum, it still fails secure check. What i am confused about is how I am able to flash anything and even get a check sum failure. I was under the impression that images that fail anything, check sum or secure check, won't flash. So my question is how is it I am able to do so? If something is flashing there has to be a way to flash the files it needs.
So I have successfully made kingroot device owner. Not that it does any good because it doesn't seem to give me root. But using one of my favorite apps to seek the activity
Code:
com.kingroot.kinguser/.receiver.DeviceOwnerReceiver
I used dpm to set-device-owner. I did this from the most recent available firmware for this device on a fresh factory reset with no accounts attached.
Before that I also was able to make icebox apps freezer device owner and disable knox apps.
If anybody knows any other tricks I can use for device owner or something that can escalate privileges from here...
I love icebox apps freezer. You can set it as device owner and have the ability to freeze all applications Including system apps. I have been doing so one by one and as I do, some of Samsung's UI disappears and stock Android fills in. This is probably as close to root as I'll get for a while.
DragonFire, which files did you change in order to obtain root? I want to try this out for myself. Please respond
Nothing in the thread mentioning what files he flashed?
for anyone who needs to test code on this type device i have a sm-a102u1 unlocked running android 9 i wont send it off but i will test anybodys wierd root code maybe this exploit could work https://github.com/grant-h/qu1ckr00t let's make history guys i will be the dude who doesn't know what hes doing somebody compile this and tinker with it all you want and send it off to me to test i think CVE-2019-2215 will be our best bet of pwning this sucker i got a laptop running windows 10 for all your needs so if you like just wanna help but dont have the device or dont wanna brick yours be my guest
and even if you have almost 0 coding knowlage feel free to send your abomnation of a rooting software to just get it tested no matter how bad it is
even if you don't have the device
DragonFire1024 said:
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
Click to expand...
Click to collapse
DragonFire1024 said:
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
Click to expand...
Click to collapse
Sounds like debugging level needs set to Mid or High from the stock setting of low. This can be done and allow the root to stick until a user reboot.
Applying that whole method After, setting debug level, might actually work. It did for the Note5.
At that point, once root is achieved, it really comes down to making sure all partitions are mounted with the same options.
You can't just remount system as read/write only, if that partition normally has "noatime, etc" mounting options. That automatically triggers a verity panic reboot
You got to do the profit work, as well as, get every letter down to the T as far as copying stock fw. File names in Odin, CB, QL, Date fingerprints, file size to the byte (almost).
It's possible to spoof ALL Day, but most don't think (aka Over Think) all the possible checks and balances that would deviate from a standard stock download/flash.
DragonFire1024 said:
Well somehow, and I have yet to be able to repeat this, I was able to flash a system image in Odin, but the device would not boot because I successfully flashed it but because the other binaries did not match the signature of the "custom system". While doing this I was also able to downgrade from binary 8 to binary 7 (android 10 to 9).
Click to expand...
Click to collapse
Plenty of stock firmware packages in revision 8 ship as Android 9. So really it might not have downgraded as much as you think then.
And going from revision 8 to 7....which part of the firmware downgraded? Just the system image? Do you know this for sure if it couldn't boot?
The old samFAIL method would work something similar to that but you would've had to modify the system image you flashed first.
DragonFire1024 said:
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
Click to expand...
Click to collapse
But will flash successfully like you state or are you asking that question without modifying the otacerts first? Because normally the fota.zip contains a lot of data for most of those things you're saying is failing the checks.
So I'm just not sure about the entire story now....
Delgoth said:
Plenty of stock firmware packages in revision 8 ship as Android 9. So really it might not have downgraded as much as you think then.
And going from revision 8 to 7....which part of the firmware downgraded? Just the system image? Do you know this for sure if it couldn't boot?
The old samFAIL method would work something similar to that but you would've had to modify the system image you flashed first.
But will flash successfully like you state or are you asking that question without modifying the otacerts first? Because normally the fota.zip contains a lot of data for most of those things you're saying is failing the checks.
So I'm just not sure about the entire story now....
Click to expand...
Click to collapse
strange how he didnt post anything on how he did it
timba123 said:
If we pay $50 to $75 for a flash token, maybe factory combo could be flashed then root figured out from there but its not worth it to me to spend that for this pos. So stuck with adb debloat I guess. Oh well
Click to expand...
Click to collapse
I mean, after upgrading, yeah the A10e is a bit dated. BUT WAIT...
The A10e is still a device using an Exynos octa-core SoC. Not a snapdragon or mtk chipset. With full command line access and root privileges the hardware itself is actually still quite capable with its 2gb of RAM.