As of right now, Google hasn't posted the factory images for the P4 and P4XL. I have my P4XL and want to root it to test a few things before I make my decision to return it or not. So, does anyone know of a way to extract the boot.img from this phone or must we wait for the images to drop?
Use payload dumper to extract it, and then patch the image via Magisk and flash that patched image in fastboot.
rickysidhu_ said:
Use payload dumper to extract it, and then patch the image via Magisk and flash that patched image in fastboot.
Click to expand...
Click to collapse
Did you perform this with success? Does Magisk allow for loading modules and root access?
rickysidhu_ said:
Use payload dumper to extract it, and then patch the image via Magisk and flash that patched image in fastboot.
Click to expand...
Click to collapse
Can you elaborate? I'm downloading the dumper, but not really sure how to dump files from the phone. Only guide I have found so far is talking about factory images which would defeat the point.
The factory image should be out within the hour, I would just wait.
vanydotk said:
The factory image should be out within the hour, I would just wait.
Click to expand...
Click to collapse
Oh? I wasn't expecting it to drop until the 24th-ish. If they're supposed to be out today then yeah, I'll just wait. lol.
GohanBurner said:
Oh? I wasn't expecting it to drop until the 24th-ish. If they're supposed to be out today then yeah, I'll just wait. lol.
Click to expand...
Click to collapse
When you get the dump or from the factory images, let me know of your success/failures with magisk if you take the plunge. How's the weather in Waukesha? Getting cold yet? I grew up in Oak Creek, WI.
GohanBurner said:
Oh? I wasn't expecting it to drop until the 24th-ish. If they're supposed to be out today then yeah, I'll just wait. lol.
Click to expand...
Click to collapse
Ah crap, you're right. I thought today was the official release date. Carry on, please ignore my last post.
Nice.
If someone manages to pull boot.img I'll try patching and flashing Magisk.
vanydotk said:
The factory image should be out within the hour, I would just wait.
Click to expand...
Click to collapse
LIES!!! lol
BadBoyNDSU said:
LIES!!! lol
Click to expand...
Click to collapse
AHH! I know. For some reason I had it in my head that the phone officially releases today. I took the day off work because I wanted to root and set my phone up! Imagine my disappointment when I realized the phone isn't officially released until Thursday.
rester555 said:
Did you perform this with success? Does Magisk allow for loading modules and root access?
Click to expand...
Click to collapse
I actually don't have mine just yet, but I believe the steps I mentioned should work without issue. Sorry I should have clarified that in my OP.
GohanBurner said:
Can you elaborate? I'm downloading the dumper, but not really sure how to dump files from the phone. Only guide I have found so far is talking about factory images which would defeat the point.
Click to expand...
Click to collapse
You extract the OTA zip and place the paylod.bin file in the input folder and then run the application. The output files would be in the output folder. I've only tested this on my OnePlus 7 Pro.
vanydotk said:
The factory image should be out within the hour, I would just wait.
Click to expand...
Click to collapse
Good advice, I'd do the same just in case things go south!
So in the end, it sounds like doing this when the factory images are available would be the best scenario. That way you can fall back to stock if needed.
Still no factory images
mk262 said:
Still no factory images
Click to expand...
Click to collapse
They say by 1pm Eastern. Well see.
Related
Here's the full System Dump from the Image that Google released yesterday and posted on their site:here:
https://developers.google.com/android/nexus/images#occamjop40c
I mounted, extracted, and zipped up the entire system dump from the system.img for download here:
DOWNLOAD SYSTEM DUMP HERE
MD5 Sum: 0a77c580900be234ddc86b7ff459c185
Mount points, thanks to mskip can be found HERE
This should give everyone a chance to start working on their ROMs for the device before they have them in hand. I know I'll start mine tomorrow.
Enjoy!
Why is this needed when we already have the factory image direct from Google?
EddyOS said:
Why is this needed when we already have the factory image direct from Google?
Click to expand...
Click to collapse
The image has been extracted and ready to deodex, or whatever you like to build your ROM.
If you have to ask the question..........
Maybe I should give it a try. Thanks
ATGAdmin said:
The
EddyOS said:
Why is this needed when we already have the factory image direct from Google?
Click to expand...
Click to collapse
image has been extracted and ready to deodex, or whatever you like to build your ROM.
If you have to ask the question..........
Click to expand...
Click to collapse
I sorta think that's his point, if you know what your doing, you can extract it yourself, it's like a 2 minute process.
I suppose this could be useful for people with really slow internet connections who would rather have just the system.img than the whole thing.
USSENTERNCC1701E said:
I sorta think that's his point, if you know what your doing, you can extract it yourself, it's like a 2 minute process.
I suppose this could be useful for people with really slow internet connections who would rather have just the system.img than the whole thing.
Click to expand...
Click to collapse
Well over 50 download since it was posted last night, so someone plans on using it.
Some things never change At XDA.
Try and be helpful, and......
Sent from my H D'licious Maxxx!
Development closed
Development closed
Why not simply link to official twrp download link
And what insecure servers 0.0
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
Why not simply link to official twrp download link
Click to expand...
Click to collapse
I just created a complete package, so even the hardest noob can free his device.
In case you mean link TWRP in the Credits, of course I will do that.
Didn't think about that idea.
Thanks, mate.
LastStandingDroid said:
And what insecure servers 0.0
Click to expand...
Click to collapse
To get files from official samsung repository you need to have a decryption key and that algorithm is not that hard to keep us out. :laugh:
Уважением/Regards,
Out of Order said:
I just created a complete package, so even the hardest noob can free his device.
In case you mean link TWRP in the Credits, of course I will do that.
Didn't think about that idea.
Thanks, mate.
To get files from official samsung repository you need to have a decryption key and that algorithm is not that hard to keep us out.[emoji23]
Уважением/Regards,
Click to expand...
Click to collapse
Hmm what files you mean is there?
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
Hmm what files you mean is there?
Click to expand...
Click to collapse
The ROM Files of course.
Out of Order said:
The ROM Files of course.
Click to expand...
Click to collapse
So you're talking about the system images now or if wow have it "decrypted" can you link info in pm (if Web browsing link"
Because I simply don't it
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
So you're talking about the system images now or if wow have it "decrypted" can you link info in pm
Click to expand...
Click to collapse
It's not a web browser link, it's bit more complicated.
Every request needs a special generated samsung request token, and that's a little developer secret.
In reference to the decrypting I'm still stucking a little bit. I can extract it exactly bit to bit and modify the system.img files, thats not the point.
The point is to get the modified files back into a working .img file that can be integrated along with boot.img and all its components to a .tar.md5 file.
If you want, I upload you all of the extracted system files, maybe two brains are better than one.
But I am sure you are smart enough to get your system.img extracted by yourself, since you released your own custom ROM and a tutorial.
Уважением/Regards,
Out of Order said:
It's not a web browser link, it's bit more complicated.
Every request needs a special generated samsung request token, and that's a little developer secret.
In reference to the decrypting I'm still stucking a little bit. I can extract it exactly bit to bit and modify the system.img files, thats not the point.
The point is to get the modified files back into a working .img file that can be integrated along with boot.img and all its components to a .tar.md5 file.
If you want, I upload you all of the extracted system files, maybe two brains are better than one.
But I am sure you are smart enough to get your system.img extracted by yourself, since you released your own custom ROM and a tutorial.
Уважением/Regards,
Click to expand...
Click to collapse
Ah uhm well thats not the part I know about since none of my images will work
Sent from my SM-G903F using Tapatalk
LastStandingDroid said:
Ah uhm well thats not the part I know about since none of my images will work
Click to expand...
Click to collapse
Thought you released your APA3 debloated ROM. Doesn't it work?
If so, we're in the same ****ing boat. :laugh:
I tried all possible ways, from Windows Tools over Linux ext4 tools but none of them get the right bit size for the image to flash properly.
For god's sake, bljad*.
Anyways, if you made a way to solve this problem, let me know.
Same goes for me, if I do, I'll drop you a message.
Уважением/Regards,
*bljad is the russian equivalent to ****
Out of Order said:
Thought you released your APA3 debloated ROM. Doesn't it work?
If so, we're in the same ****ing boat.[emoji23]
I tried all possible ways, from Windows Tools over Linux ext4 tools but none of them get the right bit size for the image to flash properly.
For god's sake, bljad*.
Anyways, if you made a way to solve this problem, let me know.
Same goes for me, if I do, I'll drop you a message.
Уважением/Regards,
*bljad is the russian equivalent to ****
Click to expand...
Click to collapse
Uhm well there was a typo my images doesn't work with odin I don't know why. And It isn't really needed as long as we have twrp sure it be good if we can make a tar out of the modified images I know djemby created images for s4 which came pre rooted but again, that was due to cache modified files? Not sure if he ever touched system image
Sent from my SM-G903F using Tapatalk
I have downloaded package. I am waiting for my phone to charge to 100% and to start with tutorial
I hope that I will not F*** something up
WeberKG said:
I have downloaded package. I am waiting for my phone to charge to 100% and to start with tutorial
I hope that I will not F*** something up
Click to expand...
Click to collapse
You either do or you won't.
Worst thing is it won't boot. But eventually if done correctly.
Sent from my SM-G903F using Tapatalk
WeberKG said:
I hope that I will not F*** something up
Click to expand...
Click to collapse
I made it as newbie-proof as I can. :laugh:
If you need any further assistance, let me know with a post or a private message.
Уважением/Regards,
I did not knew about FAP lock. It gave me some troubles at the start... I am doing this for the first time on Samsung device.
I have done it all, except #12. I could not flash auto root. Dont know why...
WeberKG said:
I have done it all, except #12. I could not flash auto root. Dont know why...
Click to expand...
Click to collapse
Due to FAP Lock.
This happens if your device is brand new or while the first ROM flash, due to the stock disabled setting of OEM Unlock.
Resolve:
#1 - Add your Google Account to your new flashed ROM
#2 - Settings - About Device - Tap 7 times on build number to enable developer options.
#3 - Settings - Developer Options - Enable OEM Unlock - Enable USB Debugging.
#4 - Power Off - Remove Battery - Press Power a few times (to eliminate the rest electricity like on a pc)
#5 - Insert Battery - Boot into Download Mode - Continue with Step #12 (Rooting)
If you still have any trouble, let me know.
Уважением/Regards,
LastStandingDroid said:
Uhm well there was a typo my images doesn't work with odin I don't know why. And It isn't really needed as long as we have twrp sure it be good if we can make a tar out of the modified images I know djemby created images for s4 which came pre rooted but again, that was due to cache modified files? Not sure if he ever touched system image
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
well dunno if it can help but i got this using sparsechunk2img:
number of sparse chunks is 3502
WILMANS2M said:
well dunno if it can help but i got this using sparsechunk2img:
number of sparse chunks is 3502
Click to expand...
Click to collapse
If I understand right, he's stucking with putting it back into working system.img.
Yep.
Envoyé de mon GT-I9505 en utilisant Tapatalk
I found a way how to repack it into system.img but I requires the file_contexts file.
Mine doesn't work I get a lot of line errors.
Maybe anyone has a solution.
Is it available? Or it is too early? thanks
I would really love it if we could get this.
The Nexus 6P already got it.
hopefully someone's working on one. If I knew how I would.
Android N Developer Preview OTA image - it is official flashable zip. So, we need someone who grub this OTA link.
droid-life.com/2014/06/05/download-nexus-ota-url-file/
Very surprised still we haven't got it.
manikandanguru said:
Very surprised still we haven't got it.
Click to expand...
Click to collapse
i used twrp to flash the N boot.img and system.img, since twrp flashes img files now. and i ended up dirty flashing it over pure nexus. took about 4 minutes.
simms22 said:
i used twrp to flash the N boot.img and system.img, since twrp flashes img files now. and i ended up dirty flashing it over pure nexus. took about 4 minutes.
Click to expand...
Click to collapse
If I want to flash it as my primary I would have done it when it was released.
I want to test it as a secondary rom using MultiROM.
It supports only flashable zip.
manikandanguru said:
If I want to flash it as my primary I would have done it when it was released.
I want to test it as a secondary rom using MultiROM.
It supports only flashable zip.
Click to expand...
Click to collapse
Tried that already, its not working with Multirom
I believe this is the link you're looking for
https://android.googleapis.com/pack...f7750fa94.signed-signed-shamu-ota-2659757.zip
I haven't done it but people are saying this works with multirom
danstah said:
I believe this is the link you're looking for
https://android.googleapis.com/pack...f7750fa94.signed-signed-shamu-ota-2659757.zip
I haven't done it but people are saying this works with multirom
Click to expand...
Click to collapse
Can this be flashable as secondary rom in MultiROM?
manikandanguru said:
Can this be flashable as secondary rom in MultiROM?
Click to expand...
Click to collapse
That was my understanding. I'm downloading right now to try it.
danstah said:
That was my understanding. I'm downloading right now to try it.
Click to expand...
Click to collapse
Downloading too.. Lets see
It's working with MultiRom for me.
danstah said:
I believe this is the link you're looking for
https://android.googleapis.com/pack...f7750fa94.signed-signed-shamu-ota-2659757.zip
I haven't done it but people are saying this works with multirom
Click to expand...
Click to collapse
Thanks man!
danstah said:
It's working with MultiRom for me.
Click to expand...
Click to collapse
This is the same file name and size as the link in the OTA thread to go to NPC56P from MMB29V. Not that I doubt you, but are you sure that this will install as is as secondary in MultiROM?
simms22 said:
i used twrp to flash the N boot.img and system.img, since twrp flashes img files now. and i ended up dirty flashing it over pure nexus. took about 4 minutes.
Click to expand...
Click to collapse
Can you link system and boot IMG plz
fubugang said:
Can you link system and boot IMG plz
Click to expand...
Click to collapse
i downloaded it then unzipped it.. then just pulled it out of N. i dont have anyplace to upload to at the moment, sorry.
fubugang said:
Can you link system and boot IMG plz
Click to expand...
Click to collapse
You can just pull them from Google's .tgz image file.
JimSmith94 said:
This is the same file name and size as the link in the OTA thread to go to NPC56P from MMB29V. Not that I doubt you, but are you sure that this will install as is as secondary in MultiROM?
Click to expand...
Click to collapse
Yup can confirm it works as a secondary ROM
fubugang said:
Can you link system and boot IMG plz
Click to expand...
Click to collapse
it'll be quicker downloading it then pulling it out. its only 842mb, the system.img unzipped is 1.2gb.
Got this OTA after doing an ODIN of EPF1 to my phone. Baseband is updated to match, unsure about bootloader but I doubt it. If someone wants a ROM dump and is willing to tell me how....
I got this update pushed to me also.
Question for anyone who knows: If you flash this do you lose the ability to install custom low level software (firmware, recoveries, etc)?
elroy253 said:
I got this update pushed to me also.
Question for anyone who knows: If you flash this do you lose the ability to install custom low level software (firmware, recoveries, etc)?
Click to expand...
Click to collapse
I didn't. I haven't tried downgrading but I flashed recovery after it updated. The one thing I have noticed is that wanam xposed/firefds kit has some functions that don't work or change anything...
Ugh, just got my S6 back from repair and they installed this update. Is it possible to root?
EncryptedCurse said:
Ugh, just got my S6 back from repair and they installed this update. Is it possible to root?
Click to expand...
Click to collapse
It's possible, our S6 won't get locked on any 6.0 firmware's
Maybe on 7.0 if we get it. but not 6.0
And for clarification EPH2 was just security fixes.. everything else is still the same.
Maqical said:
It's possible, our S6 won't get locked on any 6.0 firmware's
Maybe on 7.0 if we get it. but not 6.0
And for clarification EPH2 was just security fixes.. everything else is still the same.
Click to expand...
Click to collapse
OK, thanks — how should I go about doing this? I've always used CF Auto Root, but it doesn't seem updated yet.
I guess until further notice using Smart Switch as a lazy way to recover from my own stupidity is out
EncryptedCurse said:
OK, thanks — how should I go about doing this? I've always used CF Auto Root, but it doesn't seem updated yet.
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmo...l/how-to-flash-marshmallow-update-sm-t3362983
This guide will help you with all of it, just change the "the rom" part to whatever 6.0 rom you decide you want to use instead.
I'm downloading the complete TAR image from Sammobile, but due to finances I don't have the means to pay for the full speed..
So I'm downloading at the slow method.. If someone else has not uploaded the image, I will upload it by late tonite..
I'm still having issues with the damn Upload it gives me last second errors when I step away to do another task..
I'm making my final attempt to upload it onto my Android File Host... It should be up by morning if it uploads correctly.. Just Look For Zaphodspeaks in Android File Host if I haven't posted it yet..
I have many tasks to do this week ends.. Mainly upkeep the the old house and updating some of the old wiring while its getting cooler..
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Got my phone rooted, custom rom, and kernel that I was using before, no problem.
Last night (9/27) I got a firmware update for my factory USA unlocked 920T. Sammobile shows it was released on 9/26. It was a 50MB file that updated the Android secruity patch date to Sept. 1. No other changes. I noticed the Samsung Smart Manager app/widget shows I'm using 5% less memory now. I don't know if it's better RAM management or Samsung modified the app/widget to show different figures LOL. I suspect the t-mobile 920T will get the update soon.
JustZaphod said:
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Click to expand...
Click to collapse
Thanks!!
RFrancis said:
Thanks!!
Click to expand...
Click to collapse
At least someone replied.. It only took a month..
It looks like everyone abandoned ship and went to the S7
JustZaphod said:
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Click to expand...
Click to collapse
JustZaphod said:
At least someone replied.. It only took a month..
It looks like everyone abandoned ship and went to the S7
Click to expand...
Click to collapse
Only a month? Record time there...
JustZaphod said:
Finally, I uploaded the Image.. I had to recompress it since it kept giving me errors at the very end, just unzip and install in ODIN
https://www.androidfilehost.com/?fid=24651430732237823
Click to expand...
Click to collapse
thanks
Hortisimo said:
thanks
Click to expand...
Click to collapse
Thank me by hitting the Thanks Thumbs up!
JustZaphod said:
Thank me by hitting the Thanks Thumbs up!
Click to expand...
Click to collapse
already did
Was wondering if a kind person could deodex this new update? for some reason i cannot install ubuntu on my pc to get it done right.Thanks
How is Huawei handling root? Is it suspected to work or will this be a problem?
I guess the rooting process may be a bit similar to the Mate 20s. It took a while before root became available for Mate and the process relies on a somewhat compilicated procedure involving FunkeyHuawei and buying credits. If you really want to have root then probably better to wait or to buy a phone which is easier to root.
Hi,
Somewhat agree. Root might take time.
What I can confirm is that oem unlock is not greyed out.
P30 Pro dev options https://imgur.com/a/unJy0ZX
So do you think that someone will cook TWRP and magisk?
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
JazonX said:
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
Click to expand...
Click to collapse
Hope that someone will find a solution, maybe on chinese forums. I can't buy a non-rootable phone.
JazonX said:
I already extracted the ram disk and tried patching it with Magisk.
It didn't boot.
Any other bright ideas?
Click to expand...
Click to collapse
Is not ramdisk that you need to patch, try patch stock Recovery, at least works with EMUI 9.
kilroystyx said:
Is not ramdisk that you need to patch, try patch stock Recovery, at least works with EMUI 9.
Click to expand...
Click to collapse
Yeah, It was called Ramdisk_recovery
That's the one, isn't it?
JazonX said:
Yeah, It was called Ramdisk_recovery
That's the one, isn't it?
Click to expand...
Click to collapse
Is "RECOVERY_RAMDIS.img", in the tool is missing the "K". You can rename it to "RECOVERY_RAMDISK.img"
If you need to flash in the fastboot use this command:
fastboot flash recovery_ramdisk recovery_ramdisk.img
My p30 pro arrive today and i thought i can root it with this tutorial
https://myphoneupdate.com/root-huawei-p30-pro-unlock-bootloader-install-twrp-recovery/
And now i read here that its not possible? That is very Bad if this is so :/
Sorry for Bad English
Edit: oh... Yes now i See no Service sells this Codes at the Moment..
kilroystyx said:
Is "RECOVERY_RAMDIS.img", in the tool is missing the "K". You can rename it to "RECOVERY_RAMDISK.img"
If you need to flash in the fastboot use this command:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
JazonX said:
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
Click to expand...
Click to collapse
:crying::crying::crying:
JazonX said:
Yeah, I figured it. Output was patched_boot img. It flashed without any issues. But couldn't reboot afterwards. Went into bootloop, and then back to eRecovery. Normal boot is fine. Patched boot didn't work.
Click to expand...
Click to collapse
Unfortunately this means that Magisk is not ready to patch EMUI9.1
Has anyone tried the process ?
I might be doing it wrong, Please give it a try from your end as well!
JazonX said:
Has anyone tried the process ?
I might be doing it wrong, Please give it a try from your end as well!
Click to expand...
Click to collapse
Can you upload your stock img RECOVERY_RAMDISK?
I'll patch for you and then if the CRC/SHA is different you can try mine.
kilroystyx said:
Can you upload your stock img RECOVERY_RAMDISK?
I'll patch for you and then if the CRC/SHA is different you can try mine.
Click to expand...
Click to collapse
I have uploaded it here.
JazonX said:
I have uploaded it here.
Click to expand...
Click to collapse
Patched by me is different from yours.
Link:
https://mega.nz/#!ZZgHgapa!NO5_2VxavqN7v9RNwTlxjNTmKR40rOyWIW6k18LRJ-w
You can check the MD5, first is one that you patched and second is the one patched by me
Enclosed you can find the Magisk version used by my.
Check mine and let me know if it works.
kilroystyx said:
Patched by me is different from yours.
Link:
https://mega.nz/#!ZZgHgapa!NO5_2VxavqN7v9RNwTlxjNTmKR40rOyWIW6k18LRJ-w
You can check the MD5, first is one that you patched and second is the one patched by me
Enclosed you can find the Magisk version used by my.
Check mine and let me know if it works.
Click to expand...
Click to collapse
How to flash? Don't we need to unlock the bootloader first, if so I have to buy a unlock code right? I'm om 0.124
Puksom said:
How to flash? Don't we need to unlock the bootloader first, if so I have to buy a unlock code right? I'm om 0.124
Click to expand...
Click to collapse
Yes, to flash you need bootloader unlocked.
Don't waste your money yet, let's first JazonX test the recovery_ramdisk.img patched by me.
JazonX, have you tried? I hope it works