Remove carrier boot animation - G3 General

I own a 3UK unlocked out of the box device and run it on the EE network. Everything works fine but there is an annoying 3 boot animation. On this device the carrier boot animations are hard coded into data/.OP folder and are not affected by installing another kdz. I rooted my device and deleted the complete data/.OP folder which contains the startup and shutdown animations and also contains any carrier bloatware. Once done, these are gone forever (I think ) and I installed a generic kdz and now have a generic unlocked device.
......I am beginning to suspect that, on this device, there is no such thing as a carrier kdz, I think they are all the same with their crap installed permanently (unless removed) in this folder.:cyclops:

My device (Three UK) debranded itself after I flashed SphinX ROM, so I am guessing it deleted that folder when flashing So now if I restore to the Three KDZ...it is still un branded ^_^

leomd333 said:
My device (Three UK) debranded itself after I flashed SphinX ROM, so I am guessing it deleted that folder when flashing So now if I restore to the Three KDZ...it is still un branded ^_^
Click to expand...
Click to collapse
I believe so. :laugh:

Is there any way to remove the Three boot logo by installing another official firmware?

techbananas said:
Is there any way to remove the Three boot logo by installing another official firmware?
Click to expand...
Click to collapse
Basically no you have to be rooted and delete the animation zips from /data/.OP/H3G_COM

Hi,
Could you clarify how you found the relevant folder? I'm on three, rooted, but can't find the Data folder you mentioned?
What are you using to find and delete this folder and where is it?
Cheers
A
---------- Post added at 05:00 PM ---------- Previous post was at 04:47 PM ----------
Ah - found it. I was having a blonde moment.
Is it safe to delete the entire data/.OP folder? Or just the animations within H3G_COM?

D850?
reach /data/local/
Step 6) Paste your .zip file into that /data/local/ and double check to make sure it’s named bootanimation.zip
http://www.oneclickroot.com/root-an...ing-android-heres-the-best-place-to-get-them/

Related

[Guide]{Root}{Recovery} How to Root and install Recovery on Locked BL for NOOBS

How to root Xperia Z3 with Locked Bootloader​
Move all your important data from Internal storage to a computer and remove SDcard (make this in case you loose something)
You need to have firmware version 23.0.A.2.93 (for D6603/D6653) or 23.0.F.1.74 (for D6633) installed on your phone. If not, please download ftf file and flash it with Flashtool (newer firmware versions will fail root:
D6603_23.0.A.2.93 | Mirror
D6653_23.0.A.2.93
D6633_23.0.F.1.74​
Start the phone, don't make any initial setup. Skip it and go directly to Settings > About Phone. Tap 7 times on Buld number and a Developer options will be activated.
Go to Settings > Developer options and tick USB debugging an Allow mock locations.
Go to Settings > Security and tick Unknown sources, untick Verify apps.
Enter your phone in Flight mode
Download giefroot rooting tool v3.1 and extract the files on your PC (Windows only). [original thread: http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598]
Connect your phone to the computer.
Start install.bat
If until that moment you have never connected you phone to this PC via adb you will get a popup message on you phone to authorize this computer. Do it.
​
The procedure will start. After a while your phone should restart by itself.
After the phone boots up wait until a popup from SuperSu appears asking for adb shell root rights. Do it.
​
When you give the permission you have to see on the computer the sign "Device rooted".
If it says Device not rooted repeat all the steps running install.bat again.
​
Big thanks to:
@zxz0O0
@serajr
and to all involved
How to install Recovery on Xperia Z3 with Locked Bootloader​
Download ES File explorer or you favourite Explorer with root rights and mount /system rw.
​
Download Z3 Dualrecovery on your computer. (If the link is broken go to http://nut.xperia-files.com/ > XZDualRecovery and look for Z3 installer)
Extract the zip on your PC and start install.bat
Choose option 1 and follow the on screen instructions.
The phone will test reboot to Team Win Recovery.
Restart your phone and you are good to go.
You now will have a new application NDR Utils, which can easily boot you phone to the chosen recovery.
Big thanks to:
@[NUT]
and to all involved
How to update to Lollipop (23.1.A.0.690) or to KK (23.0.1.A.5.77) or newer firmware version without loosing root​
Follow this guide here
or
this guide here
Big thanks to:
@meetdaleet
@G-FACE
Nice video tutorial made by @ogunja
And another video tutorial made by @Koogly
Part 1
Part 2
Part 3
-
is it necessary to install recovery?? what if i dont install recovery and update to new version?
junaidali15 said:
is it necessary to install recovery?? what if i dont install recovery and update to new version?
Click to expand...
Click to collapse
You will lose root
Nice, thx for the tutorial but you should uploud the pictures to another site because I guess we need an account to see them yet. For example http://tinypic.com/
Really, will reupload them lil bit later. Thanks.
Sent from my Leo toy using Tapatalk.
Report it works, thanks for the guide, im on newest firmware with root access
does it effect the camera performance????
greatgrandking said:
does it effect the camera performance????
Click to expand...
Click to collapse
No.
If I at some point would like to return to stock completely (not rooted no dualrecovery etc.) after rooting using this method could I just flash the Stock Firmware with flashtool?
joakim_5937x said:
If I at some point would like to return to stock completely (not rooted no dualrecovery etc.) after rooting using this method could I just flash the Stock Firmware with flashtool?
Click to expand...
Click to collapse
Yes, that's right!
Oops
G-FACE said:
Yes, that's right!
Click to expand...
Click to collapse
Buddy i already have an upgraded firmware v23.0.1.A.5.77
Could you tell me how can i downgrade it so that i can root without losing warranty.
Thanks in advance
devilstutor said:
Buddy i already have an upgraded firmware v23.0.1.A.5.77
Could you tell me how can i downgrade it so that i can root without losing warranty.
Thanks in advance
Click to expand...
Click to collapse
Use flashtool (From flashtool.net) to flash the downgraded FTF file found in the FTF mega collection thread
EDIT @G-FACE, thanks for the reminder, the file you need is also, conveniently, found in the OP of this thread.
devilstutor said:
Buddy i already have an upgraded firmware v23.0.1.A.5.77
Could you tell me how can i downgrade it so that i can root without losing warranty.
Thanks in advance
Click to expand...
Click to collapse
Our just download .93 firmware from the first post and flash it with flashtool.
Sent from my Leo toy using Tapatalk.
This is legit man. Really needed this noobed down version. The main thread was getting full of bs.
@[g-face] a few quick questions that I saw some ppl were having issues w/
(I'm running d6603 global, .77FW)
Read / Write r/w system access is solved from what I understand - correct?
Read / Write r/w to SD card solved as well (read a few quick comments about ppl experiencing issues w/ this).
Some people were experiencing issues w/ Xposed not working (r/w or something), can you please point me to a good guide on how to get Xposed running well w/ no issues foreseeable.
Again, really appreciate this. Cheers.
---------- Post added at 06:54 PM ---------- Previous post was at 06:26 PM ----------
MOD EDIT OP quote removed @gregbradley
Tried this but the same issue as with another procedure I tried.
"Drivers need to be installed for connected device"
Why? I selected which FTF fw file the flashtool should be using, but it's still giving me this error. So strange that no one has had this issue, even though no guide mentions that one needs to install these drivers... :S
munsabin said:
Tried this but the same issue as with another procedure I tried.
"Drivers need to be installed for connected device"
Why? I selected which FTF fw file the flashtool should be using, but it's still giving me this error. So strange that no one has had this issue, even though no guide mentions that one needs to install these drivers... :S
Click to expand...
Click to collapse
Maybe others actually install the drivers then
Goto C:\Flashtool\Drivers
and run
drivers.exe
Choose fastboot, flashmode and Z3 drivers
Then try again. The guides also do not mention that you have turn the PC on, some sort of self help in overcoming errors does help. If it says drivers need to be installed, install them...
PS, also there is never a need to quote the whole OP, I will edit that out for you
Greg
munsabin said:
This is legit man. Really needed this noobed down version. The main thread was getting full of bs.
@[g-face] a few quick questions that I saw some ppl were having issues w/
(I'm running d6603 global, .77FW)
Read / Write r/w system access is solved from what I understand - correct?
Read / Write r/w to SD card solved as well (read a few quick comments about ppl experiencing issues w/ this).
Some people were experiencing issues w/ Xposed not working (r/w or something), can you please point me to a good guide on how to get Xposed running well w/ no issues foreseeable.
Again, really appreciate this. Cheers.
---------- Post added at 06:54 PM ---------- Previous post was at 06:26 PM ----------
MOD EDIT OP quote removed @gregbradley
Tried this but the same issue as with another procedure I tried.
"Drivers need to be installed for connected device"
Why? I selected which FTF fw file the flashtool should be using, but it's still giving me this error. So strange that no one has had this issue, even though no guide mentions that one needs to install these drivers... :S
Click to expand...
Click to collapse
Ohhh...and this happens even after I do go into the Drivers folders where's there's an .exe run program, and I install the XperiaZ3 Drivers.
munsabin said:
Ohhh...and this happens even after I do go into the Drivers folders where's there's an .exe run program, and I install the XperiaZ3 Drivers.
Click to expand...
Click to collapse
Choose the flashmode and fastboot drivers as well
If you are running Windows 8/8.1 you need to allow installation of unsigned drivers.
No problems with rw access if you follow the steps. Xposed installs normaly, as always, no problem installing it.
Rw access to SD is solved by installing SDfix from Market. I did it, and it's working as expected.
Sent from my Leo toy using Tapatalk.
@gface only if he read a lot like I do he find the way not easy the part of win8 but have a great vídeo on you tube about.... Try to search for fastboot win8 8.1. After that is easy to install with Gface tut
gregbradley said:
Choose the flashmode and fastboot drivers as well
Click to expand...
Click to collapse
I got it to flash .93 BUT now I keep having these freaking annoying pop ups... android.process.core and android.process.media has stopped. (I flashed btw without removing data)
---------- Post added at 10:00 PM ---------- Previous post was at 09:59 PM ----------
G-FACE said:
If you are running Windows 8/8.1 you need to allow installation of unsigned drivers.
No problems with rw access if you follow the steps. Xposed installs normaly, as always, no problem installing it.
Rw access to SD is solved by installing SDfix from Market. I did it, and it's working as expected.
Sent from my Leo toy using Tapatalk.
Click to expand...
Click to collapse
I got it to flash .93 BUT now I keep having these freaking annoying pop ups... android.process.core and android.process.media has stopped. (I flashed btw without removing data)

How to upgrade from C368B140 to C432B170???

Hi
I'm struggling with updating my P8 Lite (Austria, single sim) and I would appreciate your help.
I downloaded the newest firmware C432B170 from the Austrian Huawei website but I just can't update.
Tried with the Updater's local update but it didn't work.
Tried with force update and that didn't work too.
I have unlocked bootloader, root and TWRP.
Can somebody help me out??
grzdom said:
Hi
I'm struggling with updating my P8 Lite (Austria, single sim) and I would appreciate your help.
I downloaded the newest firmware C432B170 from the Austrian Huawei website but I just can't update.
Tried with the Updater's local update but it didn't work.
Tried with force update and that didn't work too.
I have unlocked bootloader, root and TWRP.
Can somebody help me out??
Click to expand...
Click to collapse
Ok, so this i fearly easy... (once you know it).
the problem is that you tried installing a European dual sim build on a Austria single sim build.
That's not gonna work does it?
1. make sure your device is a Ale-L21 (settings -> about phone -> modelnumber)
2. boot into twrp and wipe everything except sd card.
3. boot into bootloader (twrp can help you with it or just plug your device into the computer and power it on while holding volume down)
4.download this file
5. open the 'FLASH ALL' file in the folder and read the instructions on your screen
6. boot up your device and see that you have the balong bug and no reception. (settings -> about phone in the buildnumber it should say balongXXXXX)
7. take the file in the attachement of this post and unzip it
8. put the unzipt directory in the root of your sd/internal memory
9. go to settings->upgrade->menu->lokal update
10.select 'UPDATE.APP'
11.wait for it to start.
12.once it starts the balong should be gone in buildnumber
13. use the updater to update trough b170 if that doesn't work download it here and extract it and set it in a folder named dload on your sd/internal memory (delete the first file first) the do a lacal update to b170.
14 eat a sandwich because this is gonna take some time and by now you should be hungry
15. everything should work now. you should have 2 imei's and receptions.
make sure you got minimal adb installed (normally you do)
if you have location issues you can chance it by following this thread.
Lordbannakaffalatta said:
Ok, so this i fearly easy... (once you know it).
the problem is that you tried installing a European dual sim build on a Austria single sim build.
That's not gonna work does it?
1. make sure your device is a Ale-L21 (settings -> about phone -> modelnumber)
2. boot into twrp and wipe everything except sd card.
3. boot into bootloader (twrp can help you with it or just plug your device into the computer and power it on while holding volume down)
4.download this file
5. open the 'FLASH ALL' file in the folder and read the instructions on your screen
6. boot up your device and see that you have the balong bug and no reception. (settings -> about phone in the buildnumber it should say balongXXXXX)
7. take the file in the attachement of this post and unzip it
8. put the unzipt directory in the root of your sd/internal memory
9. go to settings->upgrade->menu->lokal update
10.select 'UPDATE.APP'
11.wait for it to start.
12.once it starts the balong should be gone in buildnumber
13. use the updater to update trough b170 if that doesn't work download it here and extract it and set it in a folder named dload on your sd/internal memory (delete the first file first) the do a lacal update to b170.
14 eat a sandwich because this is gonna take some time and by now you should be hungry
15. everything should work now. you should have 2 imei's and receptions.
make sure you got minimal adb installed (normally you do)
if you have location issues you can chance it by following this thread.
Click to expand...
Click to collapse
This worked!! Thank you so much for your help!! I really appreciate it!! :good:
I still have some questions though.
After this process, is my phone dual sim now?? Should I use dual sim version updates from now on???
Why should I have 2 IMEIs now?? It still shows only 1.
grzdom said:
This worked!! Thank you so much for your help!! I really appreciate it!! :good:
I still have some questions though.
After this process, is my phone dual sim now?? Should I use dual sim version updates from now on???
Why should I have 2 IMEIs now?? It still shows only 1.
Click to expand...
Click to collapse
yes it's dual sim...
about the imei's i really don't now.
never had a single sim myself but it could be that you only have one. and yes you should upgrade dual sim software from now
Lordbannakaffalatta said:
yes it's dual sim...
about the imei's i really don't now.
never had a single sim myself but it could be that you only have one. and yes you should upgrade dual sim software from now
Click to expand...
Click to collapse
OK got it!!
Again thank you very much for your help!!
Re-upload
Hi,
please can you re-upload file in step 4 again?
Thanks a lot.
Vymi
grzdom said:
This worked!! Thank you so much for your help!! I really appreciate it!! :good:
I still have some questions though.
After this process, is my phone dual sim now?? Should I use dual sim version updates from now on???
Why should I have 2 IMEIs now?? It still shows only 1.
Click to expand...
Click to collapse
---------- Post added at 04:03 PM ---------- Previous post was at 03:38 PM ----------
Sorry. It was my fall. I got it.
Vymit said:
Hi,
please can you re-upload file in step 4 again?
Thanks a lot.
Vymi
Click to expand...
Click to collapse
You can find everything here
http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994

Where is located the original firmware in nova plus ?

Is there a way to retreive the full firmware backup in my wife's phone to put it back in mine ?
i did the clown but now,i have the wrong Nougat/emui5.0 in my phone
thing is...phone mla-lo3
but,in settings / VERSION it says, NRD90M TEST KEYS 9 (official)
YESS phone is workit ...almost everything is working except that, Theme manager is not....no themes at all in the folder.....if i add some,the manager sees them but,wont apply them
if this thing could be fixed well...
virusdunil said:
Is there a way to retreive the full firmware backup in my wife's phone to put it back in mine ?
[...]
thing is...phone mla-l03
Click to expand...
Click to collapse
Same phone here, mla-l03, fido Quebec, I'm also looking for the original firmware... after wiping the data partition (to be able to access it in twrp and backup all the other partitions) I'm stuck in huawei e-recovery (twrp is still working).
I may try to flash another ROM, but I'm not sure what to try flashing... can't find anything for my device. I backed up all my partitions (except data).
Haven't formatted my data yet as im waiting for the decryption to come, maybe, well... so far i haven't anyways. Lol
But i messed up things somehow and it wouldn't boot either. So I Unzipped the 1.6 gig version of Nougat (there's one out now for
MLA-L03C654B300D001 for Fido/Rogers as well as C578 which is what I've been using as it works perfect and with full "ok Google" support from any screen) and put it in the dload directory on my SD and rebooted with all three buttons and it reinstalled everything for me and fixed it all up. So far I've yet to find another full version of our OS besides in the Nougat updates. All others seem to be ota update not full version in firmware finder. Themes I had to download and add into the hwtheme directory my self.
hi...could you please share the dload link please ?...i may give it a go...and have the darn theme working again hahaha
cheers
virusdunil said:
hi...could you please share the dload link please ?...i may give it a go...and have the darn theme working again hahaha
cheers
Click to expand...
Click to collapse
Do you want to back to emui 4? The only way possible to do this is through bluesmoothie backup. The full firmware won't be possible to be applied because nougat has different system partition size, so it will result in error when trying to fastboot flash it the original system.img
---------- Post added at 04:59 PM ---------- Previous post was at 04:56 PM ----------
Oh, just one thing.
It seems it is impossible to have a unencrypted phone with nougat. So don't format data partition, because it will be impossible to boot the phone.
Until xelfmade and others find out how to make twrp work with the encryption, we will not be able to access data partition through twrp in nougat. In marshmallow it is possible, though
Ok thanks...lets say ill stay on the nougat i have now but want the theme manager to wor again....what should i do ?
I have absolutely nothing to complain about nougat (for now hehe)...its just the themes and theme manager thats not working
thanks again
my phone never got rooted or bootloader unlocked...ive upgraded with Firmware finder with a supposed version for OUR mla...and my taughts are that its a disguised firmware cuz now,on my phone it says MLA-L03 but with NRD90M test keys....
or if i could flash with a nougat one that everything in it works....see what i mean
I think that theme manager is broken for now, because we are in beta, not a official release. It would explain the naming too
Ahh...that could be a possibility...lets wait for a while and see what will happend... thanks
Vinnom said:
Do you want to back to emui 4? The only way possible to do this is through bluesmoothie backup. The full firmware won't be possible to be applied because nougat has different system partition size, so it will result in error when trying to fastboot flash it the original system.img
---------- Post added at 04:59 PM ---------- Previous post was at 04:56 PM ----------
Oh, just one thing.
It seems it is impossible to have a unencrypted phone with nougat. So don't format data partition, because it will be impossible to boot the phone.
Until xelfmade and others find out how to make twrp work with the encryption, we will not be able to access data partition through twrp in nougat. In marshmallow it is possible, though
Click to expand...
Click to collapse
Ya after 10 tries I found that out the hard way as well. It roots and unlocks fine but never boots after data format.
Rymcbc said:
Ya after 10 tries I found that out the hard way as well. It roots and unlocks fine but never boots after data format.
Click to expand...
Click to collapse
What files did you use to get it working again?
fellowlurker said:
What files did you use to get it working again?
Click to expand...
Click to collapse
First time I had to extract the recovery, boot , and system images from the Nougat release I'm using, thank god not ota, and flash em with fastboot then reboot and then a factory reset in stock recovery got it working. Everytime after that I left the rom files in my dload folder so if it went sideways I could just 3 button reboot and reload back to full stock and start over again with unlocking bootloader then root after first boot.
Please respond to the fist post...nobody gave me a good answer and the post switched subject...
Is there a way to retreive the full firmware backup in my wife's phone to put it back in mine ?
i did the clown but now,i have the wrong Nougat/emui5.0 in my phone
thing is...phone mla-lo3 and first attempt of upgrade to Nougat
but,in settings / VERSION it says, NRD90M TEST KEYS 9 (official)
YESS phone is working ...almost everything is working except that, Theme manager is not....no themes at all in the folder.....if i add some,the manager sees them but,wont apply them
My second attempt...now with,Phone MLA-L03... Version number MLA-L03C654B300 Nougat EMUI5...
still the same problem...phone runs 95% perfect EXEPT for the darn THEME MANAGER that is STILL not working...
When i flashed the firmware,again the HWTheme folder was empty...so,dloaded genuine emui5 themes from emui's website and,the theme manager wont load them .
if this thing,the THEME MANAGER could be fixed ,or a patch well... maybe i would change my mind about reverting to marshmallow/emui 4.1
For now,to have a decent theme with some good options to play with.i'm using ADW Launcher
virusdunil said:
Please respond to the fist post...nobody gave me a good answer and the post switched subject...
Is there a way to retreive the full firmware backup in my wife's phone to put it back in mine ?
i did the clown but now,i have the wrong Nougat/emui5.0 in my phone
thing is...phone mla-lo3 and first attempt of upgrade to Nougat
but,in settings / VERSION it says, NRD90M TEST KEYS 9 (official)
YESS phone is working ...almost everything is working except that, Theme manager is not....no themes at all in the folder.....if i add some,the manager sees them but,wont apply them
My second attempt...now with,Phone MLA-L03... Version number MLA-L03C654B300 Nougat EMUI5...
still the same problem...phone runs 95% perfect EXEPT for the darn THEME MANAGER that is STILL not working...
When i flashed the firmware,again the HWTheme folder was empty...so,dloaded genuine emui5 themes from emui's website and,the theme manager wont load them .
if this thing,the THEME MANAGER could be fixed ,or a patch well... maybe i would change my mind about reverting to marshmallow/emui 4.1
For now,to have a decent theme with some good options to play with.i'm using ADW Launcher
Click to expand...
Click to collapse
I've run both versions you are speaking of and I'm currently in C654300 also on a MLA-L03, theme manger is in fact working there are just no themes installed beyond what it loads with as it's a mildly debloated beta firmware, also no Vendor apps preloaded kinda deal. If you click on customize you can still make the theme editor work. I have downloaded a bunch of themes and placed them in the hwthemes folder and they show up and can be used and customized n the theme manager fine.
The ndkeys build number is simply because it's a beta version.. It's not the wrong version just not a final release.
As of yet I haven't found a full version of 6.0 for our variant or a roll back app for going backwards and most have allot of issues trying so wouldn't advise it. Even restoring a nandroid backup is not possible on 7.0 as data encryption is not available to grab a full backup, the data partitions don't work that are out there on 7.0/Emui 5. Hope that helps.

New Firmware QI5 released 10/11/2017...still lists August 1 Security Update

551 meg update, It says it's a security update, but it's a little bigger than the typical security-only update. Oddly, the device info still shows August 1 security level but the kernel is dated September 18th.
According to Sammobile, this is a limited update to fix the BlueBorne vulnerability. More info at https://www.sammobile.com/2017/09/27/blueborne-fix-galaxy-note-4-galaxy-j3-2017-galaxy-s5-plus-galaxy-tab-s3-released/
Note, the links to firmware in this article are not for the Sprint version.
Do you have a link to the Sprint version?
Hello,
After installing this update, I couldn't install any other older version by using Odin, I get ''FAIL! (Auth)''
Any ideas, please?
Also anyone has link for the latest firmware but not Sammobile link, please.
Thanks,
Sent from my SM-N910P using Tapatalk
i also need its link ??? odin firmware
---------- Post added at 08:40 AM ---------- Previous post was at 08:33 AM ----------
or anyone have have OTA file . i need modem from it
jam97 said:
Hello,
After installing this update, I couldn't insall any other older version by using Odin, I get ''FAIL! (Auth)''
Any ideas, please?
Also anyone has link for the latest firmware but not Sammobile link, please.
Thanks,
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Same thing here. But I also restored TWRP backup with previous firmware - and got a boot loop. Tried many firmwares, even stock 6.0.1 (just removed aboot from tar and load all else), but phone still rebooting after about 45-60 seconds from power up. Android may boot, show desktop, wifi networks - all seems to be ok, but it WILL reboot after short time from power on (in TWRP reboots not occur)... Probably because I now have previous modem + new aboot...
Could you please make a TWRP backup of your current firmware (boot, modem, system at least, or better anything exclude cache and data), and please-please share it?
---------- Post added at 09:53 AM ---------- Previous post was at 09:44 AM ----------
jam97 said:
Hello,
After installing this update, I couldn't insall any other older version by using Odin, I get ''FAIL! (Auth)''
Any ideas, please?
Also anyone has link for the latest firmware but not Sammobile link, please.
Thanks,
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have one idea - but I really not sure that it will work.
As I wroted in previous post, I haved same situation - OTA and after it Odin don't want to update firmware because aboot version fail. I've loaded all other files from stock tar - system.ext4 needs to be edited with winhex to change version from 3 to 4 - and after that odin loads it. But I don't have found how to change version from aboot to override version check.
But, if we have TWRP, we can copy aboot to micro SD, and in TWRP do something like
dd if=/external_sd/aboot.mbl of=/dev/block/<partition name for aboot>
This will overwrite aboot in phone memory, and IF all will be good - you will have state like before OTA. But, if something goes wrong, OR if Samsung stores, let's say, md5 of aboot in some other region of memory and check if before every phone booting - we will have a brick that probably can't be updated with odin anymore...
Ran into same problem. The only way I found to get a somewhat factory setup was...
Be rooted and from there use flashfire to flash the previous firmware. It won't install the aboot and the modem if you don't want. I was left with almost factory state. Everything is on QI5 firmware but the actually "system" partition. You can't take an ota. System shows custom. Recovery shows dm-verity fails. Other than that everything seems to be fine.
I tried Kies and smart switch as well to get the firmware.
Hopefully sammobile or updato will get the current update soon.
Dmitry_Sysoletin said:
Same thing here. But I also restored TWRP backup with previous firmware - and got a boot loop. Tried many firmwares, even stock 6.0.1 (just removed aboot from tar and load all else), but phone still rebooting after about 45-60 seconds from power up. Android may boot, show desktop, wifi networks - all seems to be ok, but it WILL reboot after short time from power on (in TWRP reboots not occur)... Probably because I now have previous modem + new aboot...
Could you please make a TWRP backup of your current firmware (boot, modem, system at least, or better anything exclude cache and data), and please-please share it?
---------- Post added at 09:53 AM ---------- Previous post was at 09:44 AM ----------
I have one idea - but I really not sure that it will work.
As I wroted in previous post, I haved same situation - OTA and after it Odin don't want to update firmware because aboot version fail. I've loaded all other files from stock tar - system.ext4 needs to be edited with winhex to change version from 3 to 4 - and after that odin loads it. But I don't have found how to change version from aboot to override version check.
But, if we have TWRP, we can copy aboot to micro SD, and in TWRP do something like
dd if=/external_sd/aboot.mbl of=/dev/block/<partition name for aboot>
This will overwrite aboot in phone memory, and IF all will be good - you will have state like before OTA. But, if something goes wrong, OR if Samsung stores, let's say, md5 of aboot in some other region of memory and check if before every phone booting - we will have a brick that probably can't be updated with odin anymore...
Click to expand...
Click to collapse
I have slow Internet connection, I could only share the boot and the modem if you want, system is too big.
Thanks,
Sent from my SM-N910P using Tapatalk
system.ext4 needs to be edited with winhex to change version from 3 to 4
Click to expand...
Click to collapse
offset?
jam97 said:
I have slow Internet connection, I could only share the boot and the modem if you want, system is too big.
Thanks,
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
It will be much more than I have now
So, please, share at least boot and modem.
Thank you!
---------- Post added at 08:27 PM ---------- Previous post was at 08:21 PM ----------
wolflingsu said:
offset?
Click to expand...
Click to collapse
In WinHex, please go to 0x00000080A, in right text panel you'll see "SERPTRUS003". I've changed it to SERPTRUS004 (0x00000080A change from 33 to 34) - and this works for me. No more SW version error, and I able to load this image with Odin.
But I can't do same with aboot
QI5 Twrp backup
boot.emmc.win
https://drive.google.com/file/...qZVkzLXM1QUE/view?usp=drivesdk
modem.vfat.win
https://drive.google.com/file/...mcjQ1b3hwa2M/view?usp=drivesdk
boot.emmc.win.md5
https://drive.google.com/file/...LZ2J6QXJUcmc/view?usp=drivesdk
modem.vfat.win.md5
https://drive.google.com/file/...sVkdmR21MNWs/view?usp=drivesdk
modem.info
https://drive.google.com/file/...LZ2J6QXJUcmc/view?usp=drivesdk
firmware.vfat.win
https://drive.google.com/file/d/0ByW8hRv6G0bmUmNQSXJaWW5ZZTA/view?usp=drivesdk
firmware.vfat.win.md5
https://drive.google.com/file/d/0ByW8hRv6G0bmUmNQSXJaWW5ZZTA/view?usp=drivesdk
firmware.info
https://drive.google.com/file/d/0ByW8hRv6G0bmUmNQSXJaWW5ZZTA/view?usp=drivesdk
jam97 said:
QI5 Twrp backup
boot.emmc.win
https://drive.google.com/file/d/0ByW8hRv6G0bmazNqZVkzLXM1QUE/view?usp=drivesdk
modem.vfat.win
https://drive.google.com/file/d/0ByW8hRv6G0bmT1lmcjQ1b3hwa2M/view?usp=drivesdk
boot.emmc.win.md5
https://drive.google.com/file/d/0ByW8hRv6G0bmREpLZ2J6QXJUcmc/view?usp=drivesdk
modem.vfat.win.md5
https://drive.google.com/file/d/0ByW8hRv6G0bmbXJsVkdmR21MNWs/view?usp=drivesdk
modem.info
https://drive.google.com/file/d/0ByW8hRv6G0bmREpLZ2J6QXJUcmc/view?usp=drivesdk
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks a lot!
I able to restore boot, but unable to restore modem - TWRP wants firmware.win backup also, but I don't have it.
Could you share it, please?
Dmitry_Sysoletin said:
Thanks a lot!
I able to restore boot, but unable to restore modem - TWRP wants firmware.win backup also, but I don't have it.
Could you share it, please?
Click to expand...
Click to collapse
Main post has been updated.
Sent from my SM-N910P using Tapatalk
jam97 said:
Main post has been updated.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks a lot for sharing!
I'am now able to restore my modem and boot from your images. But it is not helps for me - phone still rebooting after about 45-60 seconds from powering up.
Dmitry_Sysoletin said:
Thanks a lot for sharing!
I'am now able to restore my modem and boot from your images. But it is not helps for me - phone still rebooting after about 45-60 seconds from powering up.
Click to expand...
Click to collapse
Try to flash an old https://www.androidfilehost.com/?fid=24459283995309727 rom, it works fine in my friend's phone without rebooting problem. For no reason this one is only working!!
Sent from my SM-N910P using Tapatalk
jam97 said:
Try to flash an old https://www.androidfilehost.com/?fid=24459283995309727 rom, it works fine in my friend's phone without rebooting problem. For no reason this one is only working!!
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks.
I've tried it - but have same picture - phone vibrates and reboots after some time. I tried many ROMs, Lineage, for example, starts fast enough to show android desktop - it looks like ROM itself booted normally, but after some time (about 45-60 seconds) phone will vibrate and reboot...
Can this be because of some problems with EFS partition? How to you think? Could you please share it also? Actually, EFS and aboot - only two things that can be blamed... I tried to change all else - but symptoms is not changing.
Dmitry_Sysoletin said:
Thanks.
I've tried it - but have same picture - phone vibrates and reboots after some time. I tried many ROMs, Lineage, for example, starts fast enough to show android desktop - it looks like ROM itself booted normally, but after some time (about 45-60 seconds) phone will vibrate and reboot...
Can this be because of some problems with EFS partition? How to you think? Could you please share it also? Actually, EFS and aboot - only two things that can be blamed... I tried to change all else - but symptoms is not changing.
Click to expand...
Click to collapse
So weird!
My friend's phone has exactly the same symptoms, whenever he tries to install an ota update, his photo boot up then as you described, vibrates the restart, the only build that works is PC1!
Now he is on QI5 boot loader and modem and PC1 rom, other roms don't work! they vibrate then restart!
If you find fix please share it.
Could you check under the battery what is version do you have, ex. 14.10 or 14.11,..?
Sent from my SM-N910P using Tapatalk
jam97 said:
If you find fix please share it.
Could you check under the battery what is version do you have, ex. 14.10 or 14.11,..?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Of couse I'll share solution, if I'll able to find one. But for now I'am stuck... Tried many roms - but behaviour same on stock 6.0.1 and on Lineage OS...
I have 910P camouflaged to 910F, under battery I don't see 14.0/14.1 or some looks like to it. Model under battery is SM-N910F, I can see 910P only in Odin load mode.
Do you have stock recovery from QI5??
jam97 said:
QI5 Twrp backup
boot.emmc.win
https://drive.google.com/file/...qZVkzLXM1QUE/view?usp=drivesdk
modem.vfat.win
https://drive.google.com/file/...mcjQ1b3hwa2M/view?usp=drivesdk
boot.emmc.win.md5
https://drive.google.com/file/...LZ2J6QXJUcmc/view?usp=drivesdk
modem.vfat.win.md5
https://drive.google.com/file/...sVkdmR21MNWs/view?usp=drivesdk
modem.info
https://drive.google.com/file/...LZ2J6QXJUcmc/view?usp=drivesdk
firmware.vfat.win
https://drive.google.com/file/d/0ByW8hRv6G0bmUmNQSXJaWW5ZZTA/view?usp=drivesdk
firmware.vfat.win.md5
https://drive.google.com/file/d/0ByW8hRv6G0bmUmNQSXJaWW5ZZTA/view?usp=drivesdk
firmware.info
https://drive.google.com/file/d/0ByW8hRv6G0bmUmNQSXJaWW5ZZTA/view?usp=drivesdk
Click to expand...
Click to collapse
chumpalunski said:
Do you have stock recovery from QI5??
Click to expand...
Click to collapse
Unfortunately no, I don't have it.
Sent from my SM-N910P using Tapatalk
Guys, I've found solution.
Here is odin-flasheable QI5 firmware!
https://drive.google.com/open?id=0B1blPsoKK5taRk5SZ3NwdmUtTzA
Please note, if you'll load it, you CAN'T downgrade! This will update aboot to version 5.
So, load it only if you know what are you doing!
This helps me with reboots issue, so now I'am able to load custom ROMs, and they at least don't reboot every 70 seconds.
Celluar part, data over celluar modem - don't tested yet.

having trouble rooting SM-G860P (US Sprint), need to Unlock for US carrier

I need to unlock my Samsung Galaxy S5 Sport (US, Sprint) to I can use another SIM card (FreedomPop). I bought the phone on eBay back in May and it has a clean IMEI. At the time I was only planning to use it for games etc and not as a phone. Contacted the buyer and they are a reseller and do not have the account information of the previous owner and cannot contact Sprint to unlock. Sprint won't unlock and Samsung won't unlock it (I called both). I googled and found an unlocking service that requires it to be rooted. So I tried rooting it but had no luck.
I was able to complete the CF-Auto-Root process with ODIN successfully but the phone is never rooted afterwards. I think it is because on the Download screen I can see a message "SECURE DOWNLOAD ENABLE". I was trying with this build MMB29M.G860PVPU2CQB2. Then I downloaded the stock firmware with PD1 and then tried the PD1 files to root it and still the same problem. I tried the superboot program too but after the first command the phone goes into download mode and the second command just sits "Waiting for Device".
Any ideas on how to unlock this phone? And/or root it? I really just care about unlocking it.
lam3001 said:
I need to unlock my Samsung Galaxy S5 Sport (US, Sprint) SM-G860P ... Any ideas on how to unlock this phone? And/or root it? I really just care about unlocking it.
Click to expand...
Click to collapse
If anyone is interested I finally rooted this darn thing after trying about a million things. Here's what worked (note I had the latest 6.0.1 g860pvpu2cqb2 firmware and had rolled back to g860pvpu2cpd1):
1. Install the Magisk Manager app (search this web site and find a link to the apk)
2. Downloaded the stock firmware I currently have installed (G860PVPU2CPD1_G860PSPT2CPD1_G860PVPU2CPD1_HOME.tar.md5) and used 7-Zip to move all the files from a .md5 to a .tar and copying that onto an SD card to put in the phone
3. Use Magisk's "Install" feature and pointed it to the above mentioned .tar file
4. Moved the patched_boot.img file created to the SD card and on a PC renamed that to boot.img and used 7-zip to put that into a new tar file (temp.tar)
5. Used ODIN on a PC to upload the patched boot.img file from temp.tar into the phone ... new I was finally in good shape as it was rebooting there were no red warning messages just a yellow "set warranty bit kernel" which I had never gotten in my other attempts ...
6. Verified with Root Checker Basic ... yay!
I assume the above would work for other Samsung devices too. Now to figure out how to unlock ...
I used miracle box to unlock.
Went through the process only an hour ago. I am waiting to find my sim card adapter to confirm it worked.
I found a cracked version of Miracle Box and under the samsung selection it has a sprint unlock.
I plugged in the phone, one click and 30 seconds later it was done.
I will post a link to the box shortly.
---------- Post added at 08:37 AM ---------- Previous post was at 08:20 AM ----------
lam3001 said:
If anyone is interested I finally rooted this darn thing after trying about a million things. Here's what worked (note I had the latest 6.0.1 g860pvpu2cqb2 firmware and had rolled back to g860pvpu2cpd1):
1. Install the Magisk Manager app (search this web site and find a link to the apk)
2. Downloaded the stock firmware I currently have installed (G860PVPU2CPD1_G860PSPT2CPD1_G860PVPU2CPD1_HOME.tar.md5) and used 7-Zip to move all the files from a .md5 to a .tar and copying that onto an SD card to put in the phone
3. Use Magisk's "Install" feature and pointed it to the above mentioned .tar file
4. Moved the patched_boot.img file created to the SD card and on a PC renamed that to boot.img and used 7-zip to put that into a new tar file (temp.tar)
5. Used ODIN on a PC to upload the patched boot.img file from temp.tar into the phone ... new I was finally in good shape as it was rebooting there were no red warning messages just a yellow "set warranty bit kernel" which I had never gotten in my other attempts ...
6. Verified with Root Checker Basic ... yay!
I assume the above would work for other Samsung devices too. Now to figure out how to unlock ...
Click to expand...
Click to collapse
https://drive.google.com/open?id=1NfGQ9grF8PH1rMdbM5Uq3czNNVqIlXrJ
it is a large file. but its real and it works.
---------- Post added at 08:40 AM ---------- Previous post was at 08:37 AM ----------
sloWmotion01 said:
I used miracle box to unlock.
Went through the process only an hour ago. I am waiting to find my sim card adapter to confirm it worked.
I found a cracked version of Miracle Box and under the samsung selection it has a sprint unlock.
I plugged in the phone, one click and 30 seconds later it was done.
I will post a link to the box shortly.
https://drive.google.com/open?id=1NfGQ9grF8PH1rMdbM5Uq3czNNVqIlXrJ
it is a large file. but its real and it works
Click to expand...
Click to collapse

Categories

Resources