Sorry to ask, im newbie but as far i understand.
Ascend xt got:
Unlockeable bootloader
TWRP
Root
So what is missing for our custom roms?
yunior597 said:
Sorry to ask, im newbie but as far i understand.
Ascend xt got:
Unlockeable bootloader
TWRP
Root
So what is missing for our custom roms?
Click to expand...
Click to collapse
maybe start with a system dump?
Sent from my LGLS676
Sands207 said:
maybe start with a system dump?
Sent from my LGLS676
Click to expand...
Click to collapse
cause its not easy for one or u would of released a rom already 2 we dont have original source code for device so that slows progress 3 if we go to build one we have to modify a source from another device. i tried porting it was fail everytime, but u can always try to make one. pick one you like and port it or build it. im working on lineage atm someone else resurrection remix. and thats all i think
madvane20 said:
cause its not easy for one or u would of released a rom already 2 we dont have original source code for device 3 if we go to build one we have to modify a source from another device i tried porting was fail everytime but u can always try to make one. pick one you like and port it or build it. im working on lineage atm someone else resurrection remix. and thats all i think
Click to expand...
Click to collapse
Start here, get your system dump and create a fresh device tree on github https://forum.xda-developers.com/showthread.php?t=2450045 then you will have a base for cm, rr whatever you choose to build. If you want to build aosp source would be needed I believe or backported but a system dump will literally give you the same files that you would gain from building from source, I just went through this myself. Just trying to help, follow the guide and if you need help with a device tree I could try and help. good luck ?
Sent from my LGLS676
Sands207 said:
Start here, get your system dump and create a fresh device tree on github https://forum.xda-developers.com/showthread.php?t=2450045 then you will have a base for cm, rr whatever you choose to build. If you want to build aosp source would be needed I believe or backported but a system dump will literally give you the same files that you would gain from building from source, I just went through this myself. Just trying to help, follow the guide and if you need help with a device tree I could try and help. good luck
Sent from my LGLS676
Click to expand...
Click to collapse
go for it as u will have noticed if u read the other thread we have dumped the system i have even dumped all partitions. just cause u have the files doesnt mean u can click here and magic full working os comes out. without original source code we have to make changes to the source from a device with similiar hardware. as well as make sure correct paths to files that the other source did not include. this is due to other phones sometimes have different file structures. i dunno bout anyone else but im doing my best and going as fast as i can without just 100% fail. uploading my source i made to build on my server if it boots after i build it good if everything works awesome if not if it boots then i can go through check whats missing
madvane20 said:
go for it as u will have noticed if u read the other thread we have dumped the system i have even dumped all partitions. just cause u have the files doesnt mean u can click here and magic full working os comes out
Click to expand...
Click to collapse
you wanna be rude then figure it out for yourself, was just trying to help you lol
Sent from my LGLS676
Sands207 said:
you wanna be rude then figure it out for yourself, was just trying to help you lol
Sent from my LGLS676
Click to expand...
Click to collapse
wasnt being rude i modified my last post being i was in a hurry and didnt type it out so well. i was just saying man if u know the easy way to make us a rom. go for it alot of people will thank you. if not give us time its not a easy process. also by the way my first time making a rom well building from source i tried to port for about week and a half on windows that didnt work. now im using linux so hope that gives more promising results. as well building it also takes some time why i switched to using my server to compile it uploading files still got 50 gig to go. after i get a wroking one im going to try and fix our twrp to allow for those who want stock to do ota updates from twrp and backup cust and other partitions if feel a need too. hope u dont take this as being rude as it providing info and and letting you know if u can build one then thats awesome. if not give people time heres a list of the partitions
lrwxrwxrwx root root 1969-12-31 21:59 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 21:59 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 21:59 boot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 21:59 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 21:59 config -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1969-12-31 21:59 cust -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 21:59 erecovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 21:59 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 21:59 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 21:59 hyp -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 21:59 log -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 21:59 misc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 21:59 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 21:59 modemst1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1969-12-31 21:59 modemst2 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1969-12-31 21:59 oeminfo -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 21:59 pad -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 21:59 pad0 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 21:59 persist -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 21:59 recovery -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 21:59 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 21:59 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 21:59 sec -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 21:59 sgb -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 21:59 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 21:59 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 21:59 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 21:59 userdata -> /dev/block/mmcblk0p28
Well, i see, good luck with that. I hope to see a rom in future. Hate all this bloatware and etc.
yunior597 said:
Well, i see, good luck with that. I hope to see a rom in future. Hate all this bloatware and etc.
Click to expand...
Click to collapse
i have a debloated rom however i need to upload a flashable zip that also removes the garbage from cust partition make a guide on how to remove it. or i may just repack the system image i debloated as well make guide to on how to get rid of stuff off there. theres already a guide how to backup and restore the cust as well as posts bout it all i might just make a guide for alot of it and also make a video on step by step rooting etc
madvane20 said:
wasnt being rude i modified my last post being i was in a hurry and didnt type it out so well. i was just saying man if u know the easy way to make us a rom. go for it alot of people will thank you. if not give us time its not a easy process. also by the way my first time making a rom well building from source i tried to port for about week and a half on windows that didnt work. now im using linux so hope that gives more promising results. as well building it also takes some time why i switched to using my server to compile it uploading files still got 50 gig to go. after i get a wroking one im going to try and fix our twrp to allow for those who want stock to do ota updates from twrp and backup cust and other partitions if feel a need too. hope u dont take this as being rude as it providing info and and letting you know if u can build one then thats awesome. if not give people time heres a list of the partitions
lrwxrwxrwx root root 1969-12-31 21:59 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 21:59 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 21:59 boot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 21:59 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 21:59 config -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1969-12-31 21:59 cust -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 21:59 erecovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 21:59 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 21:59 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 21:59 hyp -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 21:59 log -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 21:59 misc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 21:59 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 21:59 modemst1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1969-12-31 21:59 modemst2 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1969-12-31 21:59 oeminfo -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 21:59 pad -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 21:59 pad0 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 21:59 persist -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 21:59 recovery -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 21:59 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 21:59 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 21:59 sec -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 21:59 sgb -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 21:59 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 21:59 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 21:59 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 21:59 userdata -> /dev/block/mmcblk0p28
Click to expand...
Click to collapse
While i appreciate the info and don't worry about it try this at least to get started. Look up @superR's kitchen and take your files, throw down the 10 bucks and get the donate version with plugins, which i can say personally helps a ton or Android Studio maybe? and take what you have and make a ROM that way although the kitchen is like ly the easiest route. You are well on your way! Im passing through and trying to help, tonight ill download the files you have and see what i can piece together if you want but obviously i can't make any promises. Providing info like you did is the way to go ? link me to your files either in a pm or here and ill see what i can do.
Sent from my LGLS676
Sands207 said:
While i appreciate the info and don't worry about it try this at least to get started. Look up @superR's kitchen and take your files, throw down the 10 bucks and get the donate version with plugins, which i can say personally helps a ton or Android Studio maybe? and take what you have and make a ROM that way although the kitchen is like ly the easiest route. You are well on your way! Im passing through and trying to help, tonight ill download the files you have and see what i can piece together if you want but obviously i can't make any promises. Providing info like you did is the way to go link me to your files either in a pm or here and ill see what i can do.
Sent from my LGLS676
Click to expand...
Click to collapse
oh im doing fine free tools im uusing my 16 core 18gv burstable to 30 gb server to compile my builds as go throw to debug
---------- Post added at 05:46 AM ---------- Previous post was at 05:45 AM ----------
oh im doing fine free tools im using my 16 core 18 gb burstable to 30 gb server to compile my builds as go throw to debug
madvane20 said:
oh im doing fine free tools im uusing my 16 core 18gv burstable to 30 gb server to compile my builds as go throw to debug
---------- Post added at 05:46 AM ---------- Previous post was at 05:45 AM ----------
oh im doing fine free tools im using my 16 core 18 gb burstable to 30 gb server to compile my builds as go throw to debug
Click to expand...
Click to collapse
madvane20,
You mentioned earlier that we don't have source code. I checked the Huawei site and found the source code posted. Perhaps Huawei silently posted it without anyone noticing because people stop checking.
H1611 Huawei Ascend XT, Texas-A1(H1611), Android6.0, EMUI4.1
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
Search for "ascend" and it shows up as the only result. It contains kernel.tar.gz at 168 MB along with a readme.txt on how to build it. I extracted a *.c file to make sure it has real source code, and it sure does.
Perhaps this will help with development. Do you think this is the last piece we need to get it all going? If so, I am ready to go out and buy one!
Thanks for keeping it going.
pekcle
[/COLOR]
pekcle said:
madvane20,
You mentioned earlier that we don't have source code. I checked the Huawei site and found the source code posted. Perhaps Huawei silently posted it without anyone noticing because people stop checking.
H1611 Huawei Ascend XT, Texas-A1(H1611), Android6.0, EMUI4.1
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
Search for "ascend" and it shows up as the only result. It contains kernel.tar.gz at 168 MB along with a readme.txt on how to build it. I extracted a *.c file to make sure it has real source code, and it sure does.
Perhaps this will help with development. Do you think this is the last piece we need to get it all going? If so, I am ready to go out and buy one!
Thanks for keeping it going.
pekcle
Click to expand...
Click to collapse
Awesome that you found this, Huawei has released the source code. Should be easier to compile a ROM and tweak TWRP now.
In the search box, indeed type Ascend and it comes up from the above link
Awesome! Here's the direct download link if anyone wants to skip the search:
http://download-c1.huawei.com/downl...oadId=90665&version=353730&siteCode=worldwide
pekcle said:
madvane20,
You mentioned earlier that we don't have source code. I checked the Huawei site and found the source code posted. Perhaps Huawei silently posted it without anyone noticing because people stop checking.
H1611 Huawei Ascend XT, Texas-A1(H1611), Android6.0, EMUI4.1
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
Search for "ascend" and it shows up as the only result. It contains kernel.tar.gz at 168 MB along with a readme.txt on how to build it. I extracted a *.c file to make sure it has real source code, and it sure does.
Perhaps this will help with development. Do you think this is the last piece we need to get it all going? If so, I am ready to go out and buy one!
Thanks for keeping it going.
pekcle
Click to expand...
Click to collapse
yea im extracting it now check some thinks then i will upload or download it with my server im sure i can compile on it alot faster im going to build a twrp on my vm though faster atm then the server cause i have to fix some configs on my server i think
I'll be posting my H1611.STOCK.ROOTED.NOVA.B150.ROM.zip and H1611.B150.Debloated.Rom.zip along with instructions soon
clsA said:
I'll be posting my H1611.STOCK.ROOTED.NOVA.B150.ROM.zip and H1611.B150.Debloated.Rom.zip along with instructions soon
Click to expand...
Click to collapse
i hope to be posting a cooked version of lineage for us now that i have the source it might help me fix bugs that arise
This phone is so sad without custom roms...
yunior597 said:
This phone is so sad without custom roms...
Click to expand...
Click to collapse
It's taking time but it will come. We have a couple devs that are not all that experienced and learning as they go. I'm sure it will be worth the wait.
One thing people forget it's time consuming (especially when you are just learning) and everyone expects it for nothing. The devs do it as a hobby in their free time. If we want an experienced dev and want results, the answer is simple. Get as many people as we can, pool some money together and pay someone with all that knowledge for their time.
Then we would have some custom Roms ASAP... Three XDA members that I know of are working on it and once we have something I hope many of us will donate to thank them for their efforts.
I thought about starting a bounty to collect funds and pay someone. If you really know what you are doing it does not take very long. Say 100 members at $5 a pop, that would get us some pretty good results and what you are asking for
What do you not currently have which you expect to gain from a custom ROM?
yunior597 said:
This phone is so sad without custom roms...
Click to expand...
Click to collapse
Related
I would like to start a new thread with topic as listed. It´s just so much easier to do searches this way.
As of now, there is no custom recovery for our device. While the root method from the i9505 also works on our device, custom recoveries do not. The issue seems to be with the display driver.
I would greatly appreciate if someone more knowledgable than me could elaborate on this.
I would be interested in this too. Also whether there is any prospect of rom development for the international active.
Sent from my HTC One using Tapatalk 2
Bumping.
Wouldn't it be a good idea to have a separate section for the i9295?
Yes there's a lot less audience for the device, but it is still an S4 model.
Any ideas on who we could contact to get the separate section made? (Not to mention one for the S4 Zoom when it's released)
Sent from my GT-I9300 using xda app-developers app
tryerxda said:
Bumping.
Wouldn't it be a good idea to have a separate section for the i9295?
Yes there's a lot less audience for the device, but it is still an S4 model.
Any ideas on who we could contact to get the separate section made? (Not to mention one for the S4 Zoom when it's released)
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Agree and bump...I'm thinking of getting this phone (it was my ideal choice, like the S4...but can be put underwater!), but the lack of community is starting to put me off...
timonoj said:
Agree and bump...I'm thinking of getting this phone (it was my ideal choice, like the S4...but can be put underwater!), but the lack of community is starting to put me off...
Click to expand...
Click to collapse
Patience - this just startet selling and shops seem to find it hard to keep up with customers, at least here in Germany.
Doolittle Duckbill said:
Patience - this just startet selling and shops seem to find it hard to keep up with customers, at least here in Germany.
Click to expand...
Click to collapse
Here in Hong Kong, as usual you can find it before anywhere in the shady shops in some tech markets. Right now for some 450€, which to be honest isn't a bad price. But Fortress and all the big shops (kind of like Media Markt) still don't sell it. I hope you're right and the buyers will come around to it. I'm holding my purchase until this is cleared up, I woudln't want a phone with no support. I had enough trouble with the S2 and its unsupported Exynos chipset.
hope to see in the near future a custom recovery for this devise
this are the mountpoints?
atform/msm_sdcc.1/by-name <
lrwxrwxrwx root root 1970-01-06 01:35 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-06 01:35 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-06 01:35 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-06 01:35 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-06 01:35 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-06 01:35 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-06 01:35 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-06 01:35 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-06 01:35 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-06 01:35 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-06 01:35 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-06 01:35 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-06 01:35 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-06 01:35 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-06 01:35 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-06 01:35 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-06 01:35 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-06 01:35 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-06 01:35 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-06 01:35 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-06 01:35 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-06 01:35 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-06 01:35 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-06 01:35 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-06 01:35 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-06 01:35 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-06 01:35 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-06 01:35 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-06 01:35 userdata -> /dev/block/mmcblk0p29
[email protected]:/ $
And attached the log of the first TWRP build thx to Dees_Troy
At the moment the screen didn´t work.
when you run the logfile of the stock recovery, is there anything resembling these lines:
Starting the UI...Pixel format: 1080x1920 @ 32bpp
Pixel format: RGBX_8888
framebuffer: fd 4 (1080 x 1920)
??
One would suspect that´s where the difference is, as everything seems to run except graphics
Doolittle Duckbill said:
when you run the logfile of the stock recovery, is there anything resembling these lines:
Starting the UI...Pixel format: 1080x1920 @ 32bpp
Pixel format: RGBX_8888
framebuffer: fd 4 (1080 x 1920)
??
One would suspect that´s where the difference is, as everything seems to run except graphics
Click to expand...
Click to collapse
the log from stock recovery
Ok, so in the TWRP for the i9095 we have:
ro.sf.lcd_density=320
while in stock recovery for the i9295 we have:
ro.sf.lcd_density=480
OK is there anybody here who can compile TWRP and knows where to set lcd density? My head is too small for these things...
Edit: On second thought, this may just be the scale factor for the screen and may not have anything to do with the display driver, so I just might be on the wrong track here... don´t know for sure
Doolittle Duckbill said:
Ok, so in the TWRP for the i9095 we have:
ro.sf.lcd_density=320
while in stock recovery for the i9295 we have:
ro.sf.lcd_density=480
OK is there anybody here who can compile TWRP and knows where to set lcd density? My head is too small for these things...
Edit: On second thought, this may just be the scale factor for the screen and may not have anything to do with the display driver, so I just might be on the wrong track here... don´t know for sure
Click to expand...
Click to collapse
Do you have log files for the 9505 booting twrp? Or know where to get them? I'm obviously looking myself.
On the htc one (i run both) there was an issue with the TWRP screen driver after a firmware upgrade. Is it worth contacting the TWRP team to ask them about the drivers?
Sent from my GT-I9295 using Tapatalk 4 Beta
Doolittle Duckbill said:
when you run the logfile of the stock recovery, is there anything resembling these lines:
Starting the UI...Pixel format: 1080x1920 @ 32bpp
Pixel format: RGBX_8888
framebuffer: fd 4 (1080 x 1920)
??
One would suspect that´s where the difference is, as everything seems to run except graphics
Click to expand...
Click to collapse
This is also difference:
initalized graphics for qualcomm.
pixel format -> GGL_PIXEL_FORMAT_RGBX_8888
return for qualcomm. double_buffering = 0
framebuffer: fd 4 (1080 x 1920)
---------- Post added at 06:09 AM ---------- Previous post was at 06:07 AM ----------
Have somebody contact to the cwm team?
So I managed to get cwm booted. It's saying "Warning: No file_context". I've been googling I can't find an explanation and source code is of little help. Anyone has a clue what it could be?
I'm running a backup. See if I fry anything
A preliminary version is of cwm up
http://forum.xda-developers.com/showthread.php?t=2387980
Sent from my GT-I9295 using xda premium
LeJay said:
So I managed to get cwm booted. It's saying "Warning: No file_context". I've been googling I can't find an explanation and source code is of little help. Anyone has a clue what it could be?
I'm running a backup. See if I fry anything
Click to expand...
Click to collapse
Its only a warning displayed when the kernel does not support SELinux.
Envoyé depuis mon GT-I9103
Droid Turbo Think Tank
{
"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"
}
The main purpose of this thread is to discuss possible ideas for development and exploitation of the Motorola Droid Turbo. Topics can range from ideas on how to accomplish certain mods as we are trying to bake them into images to ways to flash different files to unlocking the BL. I am by no means an expert and I have some ideas I'd like to share with others on various topics. There is alot of hostility on this board, lets build some community!
__________________________________________________________________________________________________________
I do not however have total knowledge so I lack some skills to know if what I am saying is even possible. I am simply an android enthusiast, technologically inclined individual, and engineering student.
I will start us off: Since we have root permissions would it be possible to just dd a replacement recovery to the recovery partition, or even a modified bootloader. Or is that something R/W would prohibit/ not keep after a reboot? Would we be able to nandroid and restore/ install if we even could get a replacement recovery without the unlocked B/L?
Recovery Image DD:
Code:
dd if=/sdcard/recoveryfile.img of=/dev/block/mmcblk0p36
Here is a list of the partitions along with their name
Code:
[email protected]:/dev/block/platform/msm_sdcc.1 $ ls -al /dev/block/platform/msm_sdcc
.1/by-name
/platform/msm_sdcc.1/by-name <
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="Blue"]aboot[/COLOR] -> /dev/block/mmcbl
k0p6
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]abootBackup[/COLOR] -> /dev/block
/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]boot [/COLOR]-> /dev/block/mmcblk
0p35
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]cache[/COLOR] -> /dev/block/mmcbl
k0p38
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]cid[/COLOR] -> /dev/block/mmcblk0
p25
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]clogo[/COLOR] -> /dev/block/mmcbl
k0p28
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]ddr[/COLOR] -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]factorytune1 [/COLOR]-> /dev/bloc
k/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]factorytune2 [/COLOR]-> /dev/bloc
k/mmcblk0p37
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]kpan [/COLOR]-> /dev/block/mmcblk
0p34
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]logo [/COLOR]-> /dev/block/mmcblk
0p27
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]logs [/COLOR]-> /dev/block/mmcblk
0p20
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1dhob [/COLOR]-> /dev/block/mm
cblk0p23
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1hob [/COLOR]-> /dev/block/mmc
blk0p22
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefs1 [/COLOR]-> /dev/block
/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefs2 [/COLOR]-> /dev/block
/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefs3 [/COLOR]-> /dev/block
/mmcblk0p31
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]mdm1m9kefsc [/COLOR]-> /dev/block
/mmcblk0p32
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]misc [/COLOR]-> /dev/block/mmcblk
0p29
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]modem [/COLOR]-> /dev/block/mmcbl
k0p1
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]padA [/COLOR]-> /dev/block/mmcblk
0p11
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]padB [/COLOR]-> /dev/block/mmcblk
0p19
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]padC [/COLOR]-> /dev/block/mmcblk
0p30
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]pds [/COLOR]-> /dev/block/mmcblk0
p26
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]persist [/COLOR]-> /dev/block/mmc
blk0p21
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]recovery [/COLOR]-> /dev/block/mm
cblk0p36
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]rpm [/COLOR]-> /dev/block/mmcblk0
p7
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]rpmBackup [/COLOR]-> /dev/block/m
mcblk0p14
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sbl1 [/COLOR]-> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sbl1bak [/COLOR]-> /dev/block/mmc
blk0p12
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sdi [/COLOR]-> /dev/block/mmcblk0
p3
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sec [/COLOR]-> /dev/block/mmcblk0
p4
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]sp [/COLOR]-> /dev/block/mmcblk0p
24
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]ssd [/COLOR]-> /dev/block/mmcblk0
p33
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]system [/COLOR]-> /dev/block/mmcb
lk0p39
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]tz [/COLOR]-> /dev/block/mmcblk0p
9
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]tzBackup [/COLOR]-> /dev/block/mm
cblk0p16
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]userdata [/COLOR]-> /dev/block/mm
cblk0p40
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]utags [/COLOR]-> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 1969-12-31 19:00 [COLOR="blue"]utagsBackup [/COLOR]-> /dev/block
/mmcblk0p15
[email protected]:/dev/block/platform/msm_sdcc.1 $
If a more knowledgeable user would comment on this I'd appreciate it!
Which are the imei blocks?
cascade128 said:
Which are the imei blocks?
Click to expand...
Click to collapse
The IMEI is in the utags partition.
Code:
su
dd if="/dev/block/platform/msm_sdcc.1/by-name/utags" of="/sdcard/utags.bin"
Then pull utags.bin off of the internal storage of the device and open it in a hex editor (you need root to copy it to the internal storage)
What about 2nd init? This seems to have been a good solution in the past. I believe this is how Safestrap worked. It used an exploit in a log file to launch 2nd init from the data partition. In this case the system would boot from data and we would presumably have full access. I don't know if the exploit would still work in 4.4.4. This would be the key, but the exploit could be added to a system image and flashed. Safestrap would be awesome, but even a simple 2nd init could work to start. I am just throwing this out there for discussion. This is way outside of my means, but someone else might be able to help.
Harry44 said:
Would we be able to nandroid and restore/ install if we even could get a replacement recovery without the unlocked B/L?
Click to expand...
Click to collapse
To answer your first question, no, dd'ing a new recovery in place wouldn't work. I think wp(write protect) would stop it and even if it doesn't, booting it would fail, as it verifies the signature of the partition it's booting from unless the device is unlocked or an engineering model. For your second question, yes, if you could miraculously perform the act of getting a recovery in there and it boots (emphasis on "and it boots") you *should* be able to backup/restore/install stuff.
r3pwn said:
The IMEI is in the utags partition.
Code:
su
dd if="/dev/block/platform/msm_sdcc.1/by-name/utags" of="/sdcard/utags.bin"
Then pull utags.bin off of the internal storage of the device and open it in a hex editor (you need root to copy it to the internal storage)
Click to expand...
Click to collapse
Thx.
What is utagsBackup.bin? Do i need to change it?
cascade128 said:
Thx.
What is utagsBackup.bin? Do i need to change it?
Click to expand...
Click to collapse
Not sure what your local laws are but check before modifying IMEI.
cascade128 said:
Thx.
What is utagsBackup.bin? Do i need to change it?
Click to expand...
Click to collapse
Erh, I wasn't aware that you wanted to CHANGE your IMEI. I am afraid that I am unable to assist you with that (well, I'm able, I just don't want to because it's illegal).
Harry44 said:
Not sure what your local laws are but check before modifying IMEI.
Click to expand...
Click to collapse
r3pwn said:
Erh, I wasn't aware that you wanted to CHANGE your IMEI. I am afraid that I am unable to assist you with that (well, I'm able, I just don't want to because it's illegal).
Click to expand...
Click to collapse
In our country, you have to register to use the mobile phone brought a passport outside the country due to a ridiculous law. Also you invest 50$ before the bank for this purpose.
That's not all. The passport to be registered abroad in the last 2 months need to be logged in our country. In addition, within the last 2 years it is supposed to be saved to another mobile phone passport...
This transaction is being processed on the IMEI number...
We were so old that we bring to mobile phones from abroad, used condition but in our country we are writing the IMEI number of the phone is registered. However we have to...
Any way we could boot back up an IRC for people who want to throw ideas off eachother a bit quicker, or just a general DT Discuss?
Sareniah said:
Any way we could boot back up an IRC for people who want to throw ideas off eachother a bit quicker, or just a general DT Discuss?
Click to expand...
Click to collapse
This would actually be a good idea. Anyone willing to set it up?
If someone have moto maxx and check files whats changes in unlocking bootloader and try change in droid turbo too.
I have some ideas for bootloader unlock. They're probably really stupid, but bear with me. Like OP, I'm no developer, just an Android enthusiast with basic knowledge of the inner workings.
So the Moto Maxx US (XT1250) and Droid Turbo (XT1254) are essentially the same device, right? They essentially have the same specs, same hardware, software, and they both work on CDMA carriers like Verizon. The only difference is that the Maxx's bootloader is not locked by Verizon. So here are a few ideas pertaining to that.
***NOTE: It has to be the XT1250 variant
Idea A:
1. XT1250 Maxx user uses "fastboot oem get_unlock_data" or goes through WinDroid to get the unlock key
2. Key is given to a Turbo user
3. Turbo user uses "fastboot oem unlock <maxx_key>
4. Profit
Idea B (risky):
1. Turbo user downloads XT1250 system .img
2. User flashes to Turbo using RSDlite or MOFO (not sure which would work better, if at all)
3. Use WinDroid to unlock BL, root, and install a custom recovery
4. Profit
Yes, yes, I know...they are probably bad ideas, but we must consider every possibility!
jake7405 said:
I have some ideas for bootloader unlock. They're probably really stupid, but bear with me. Like OP, I'm no developer, just an Android enthusiast with basic knowledge of the inner workings.
Click to expand...
Click to collapse
These wouldn't work. Good start on ideas, though.
Thanks!
Just a quick n00b question, why wouldnt flashing the xt1250 img work?
Sent from my XT1254
Thank you.
jake7405 said:
Thanks!
Just a quick n00b question, why wouldnt flashing the xt1250 img work?
Sent from my XT1254
Click to expand...
Click to collapse
The phone data itself (IMEI and stuff) is still the same, so the unlock data generated would still be the same, meaning Motorola would still reject it.
Was shown this as potential ways to head towards bl unlock. Leaving it here for greater minds to dissect.
http://manualwire.com/view/19580/
JakeDHS07 said:
Was shown this as potential ways to head towards bl unlock. Leaving it here for greater minds to dissect.
http://manualwire.com/view/19580/
Click to expand...
Click to collapse
Unless I'm mistaken, that would only help with a bootloader bypass. Trust me. Unlocks are better than bypasses.
r3pwn said:
The phone data itself (IMEI and stuff) is still the same, so the unlock data generated would still be the same, meaning Motorola would still reject it.
Click to expand...
Click to collapse
Any way to modify or change it? Also, would this probably end up hard bricking me if I tried?
i remember a great developer ( odia ) who downgrade the I9300 xella
has someone try this way ?
http://forum.xda-developers.com/gal.../util-sboot-checker-simple-downgrade-t2081748
this method was used also for N7100
http://forum.xda-developers.com/showthread.php?t=2089353
I HAVE NOT TRY THIS WITH N910C I JUST ASK IF SOMEONE TRY THIS !!!
kondronaute said:
i remember a great developer ( odia ) who downgrade the I9300 xella
has someone try this way ?
http://forum.xda-developers.com/gal.../util-sboot-checker-simple-downgrade-t2081748
this method was used also for N7100
http://forum.xda-developers.com/showthread.php?t=2089353
I HAVE NOT TRY THIS WITH N910C I JUST ASK IF SOMEONE TRY THIS !!!
Click to expand...
Click to collapse
Very interesting....
Only thing to verify if partitions are the same. They should be. Since this is 2 years old wonder if Samsung has caught on.
dicksteele said:
Very interesting....
Only thing to verify if partitions are the same. They should be. Since this is 2 years old wonder if Samsung has caught on.
Click to expand...
Click to collapse
first look there are same, I am happy with the new rom and I haven't time to test .....
if someone want to test he must take last abd version .... (you can download the zip with batch...)
kondronaute said:
first look there are same, I am happy with the new rom and I haven't time to test .....
if someone want to test he must take last abd version .... (you can download the zip with batch...)
Click to expand...
Click to collapse
I just got my phone last month and did the OJ5 update not realizing it was locked. I was on ATT Note 2 for years and years and never got to try a Dr Ketan's ROM. Pissed with the new locked bootloader.
So I'm ODIN flashing to full COJ5.
Will back up efs, param, pit and whatever else I can think of and give it a shot.
Obviously it seems to simple to work.
I did a compare yesterday on the pre-locked 5.1.1 bootloaders and the locked one.
I saw a few things in there that were different and I modified them in the locked one.
My edited one flashed so I was surprised. But I tried to downgrade and it didn't work..... So what I changed didn't make a difference. Yet ! :laugh:
dicksteele said:
I just got my phone last month and did the OJ5 update not realizing it was locked. I was on ATT Note 2 for years and years and never got to try a Dr Ketan's ROM. Pissed with the new locked bootloader.
So I'm ODIN flashing to full COJ5.
Will back up efs, param, pit and whatever else I can think of and give it a shot.
Obviously it seems to simple to work.
I did a compare yesterday on the pre-locked 5.1.1 bootloaders and the locked one.
I saw a few things in there that were different and I modified them in the locked one.
My edited one flashed so I was surprised. But I tried to downgrade and it didn't work..... So what I changed didn't make a difference. Yet ! :laugh:
Click to expand...
Click to collapse
ok good luck
i think this is the better option in the past i do it for 3 or 4 I9300 without any pbm hope it's same again
kondronaute said:
ok good luck
i think this is the better option in the past i do it for 3 or 4 I9300 without any pbm hope it's same again
Click to expand...
Click to collapse
Double checking things Back on full stock
[email protected]:/dev/block/platform/15540000.dwmmc0/by-name $ ls -la
ls -la
lrwxrwxrwx root root 2015-11-28 11:15 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-11-28 11:15 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-11-28 11:15 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-11-28 11:15 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-11-28 11:15 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-11-28 11:15 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-11-28 11:15 DNT -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-11-28 11:15 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-11-28 11:15 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-11-28 11:15 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-11-28 11:15 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-11-28 11:15 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-11-28 11:15 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-11-28 11:15 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-11-28 11:15 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-11-28 11:15 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-11-28 11:15 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-11-28 11:15 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs3 -> /dev/block/mmcblk0p6
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1 BOTA0 Restore Bootloader (I hope!)
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2 BOTA1 Restore tz.img
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4 PARAM Restore PARAM
# dd if=/dev/block/mmcblk0 of=/sdcard/N910C.pit bs=8 count=580 skip=2176 Backup PIT
PIT -> /dev/block/mmcblk0
BOOT -> /dev/block/mmcblk0p9 Kernel
RECOVERY-> /dev/block/mmcblk0p10 TWRP
RADIO -> /dev/block/mmcblk0p13 Modem
Starting partition backups and continuing internal debate of how confident I am I won't f**k something up
dicksteele said:
Double checking things Back on full stock
[email protected]:/dev/block/platform/15540000.dwmmc0/by-name $ ls -la
ls -la
lrwxrwxrwx root root 2015-11-28 11:15 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-11-28 11:15 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-11-28 11:15 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-11-28 11:15 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-11-28 11:15 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-11-28 11:15 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-11-28 11:15 DNT -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-11-28 11:15 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-11-28 11:15 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-11-28 11:15 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-11-28 11:15 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-11-28 11:15 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-11-28 11:15 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-11-28 11:15 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-11-28 11:15 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-11-28 11:15 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-11-28 11:15 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-11-28 11:15 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs3 -> /dev/block/mmcblk0p6
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1 BOTA0 Restore Bootloader (I hope!)
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2 BOTA1 Restore tz.img
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4 PARAM Restore PARAM
# dd if=/dev/block/mmcblk0 of=/sdcard/N910C.pit bs=8 count=580 skip=2176 Backup PIT
PIT -> /dev/block/mmcblk0
BOOT -> /dev/block/mmcblk0p9 Kernel
RECOVERY-> /dev/block/mmcblk0p10 TWRP
RADIO -> /dev/block/mmcblk0p13 Modem
Starting partition backups and continuing internal debate of how confident I am I won't f**k something up
Click to expand...
Click to collapse
i think you can try without tz.img and param.bin
look at this rar (i put the last adb)
(when I do it with I9300 the phone was on ....)
kondronaute said:
i think you can try without tz.img and param.bin
look at this rar (i put the last adb)
(when I do it with I9300 the phone was on ....)
Click to expand...
Click to collapse
No dice with and without param.bin. Good news still boots.
Still shows bootloader of COJ5
Maybe it does need tz.img
dicksteele said:
No dice with and without param.bin. Good news still boots.
Still shows bootloader of COJ5
Maybe it does need tz.img
Click to expand...
Click to collapse
yes god news i boot but seem not do the job....
do you try w ith only this script
@files1\adb push sboot.bin /sdcard/sboot.bin
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1"
@files1\adb shell rm /sdcard/sboot.bin
@files1\adb reboot fota_bl
kondronaute said:
yes god news i boot but seem not do the job....
do you try w ith only this script
@files1\adb push sboot.bin /sdcard/sboot.bin
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1"
@files1\adb shell rm /sdcard/sboot.bin
@files1\adb reboot fota_bl
Click to expand...
Click to collapse
Yeah, I did that
Then I bumped it up a notch
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/platform/15540000.dwmmc0/by-name/BOTA0"
@files1\adb shell getprop ro.boot.bootloader
@pause
After the pause it comes back with the COJ5.
Rebooting, running same command, COJ5.
Assuming this will create a tz.img.... I haven't seen anything referring to it for 5.1.1
dd if=/dev/block/mmcblk0p2 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/platform/15540000.dwmmc0/by-name/BOTA1 of=/sdcard/tz.img bs=4096
Also just downloaded 11/27 firmware for Kenya going to try that. I've been using the sboot.bin from here
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
dicksteele said:
Yeah, I did that
Then I bumped it up a notch
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/platform/15540000.dwmmc0/by-name/BOTA0"
@files1\adb shell getprop ro.boot.bootloader
@pause
After the pause it comes back with the COJ5.
Rebooting, running same command, COJ5.
Assuming this will create a tz.img.... I haven't seen anything referring to it for 5.1.1
dd if=/dev/block/mmcblk0p2 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/platform/15540000.dwmmc0/by-name/BOTA1 of=/sdcard/tz.img bs=4096
Also just downloaded 11/27 firmware for Kenya going to try that. I've been using the sboot.bin from here
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
Click to expand...
Click to collapse
after the pause can you reboot directly in download mode and flash again the new bootloader with odin
try this bootloader
N910CXXU1COH4 Bootloader (5.1.1)(ONLY for N910C users)
http://forum.xda-developers.com/showpost.php?p=58867937&postcount=3
I am very pessimistic with this ...
kondronaute said:
after the pause can you reboot directly in download mode and flash again the new bootloader with odin
try this bootloader
N910CXXU1COH4 Bootloader (5.1.1)(ONLY for N910C users)
http://forum.xda-developers.com/showpost.php?p=58867937&postcount=3
I am very pessimistic with this ...
Click to expand...
Click to collapse
You should be .... No dice.
But again. I was able to pull battery go back into download mode and ODIN flash the COJ5 I had
Kenya firmware from 11/27 same thing...
dicksteele said:
You should be .... No dice.
But again. I was able to pull battery go back into download mode and ODIN flash the COJ5 I had
Kenya firmware from 11/27 same thing...
Click to expand...
Click to collapse
when you pull the battery after flashed a pre locked bootloader can you in the go reflash the same pre locked bl with odin ( it flash or it say error .....)
kondronaute said:
when you pull the battery after flashed a pre locked bootloader can you in the go reflash the same pre locked bl with odin ( it flash or it say error .....)
Click to expand...
Click to collapse
Same error NAND write fail
dicksteele said:
Same error NAND write fail
Click to expand...
Click to collapse
it was a pleasure to collaborate with u
i hope a developer look at this pbm; really i am happy with 5.1.1 coz i can use xposed and it's better than 5.0.1 but I love to have the choice, I love the idea to be free and I don't understand why samsung and other lock our phones; personally I have no care for guaranty.... i want just be free to play with my phone !
kondronaute said:
it was a pleasure to collaborate with u
i hope a developer look at this pbm; really i am happy with 5.1.1 coz i can use xposed and it's better than 5.0.1 but I love to have the choice, I love the idea to be free and I don't understand why samsung and other lock our phones; personally I have no care for guaranty.... i want just be free to play with my phone !
Click to expand...
Click to collapse
Agree.
I'm really having no issues with 5.1.1.
I'm with you, it was more of a challenge to see if it could be done. CM 13 seems to be moving along so that may take the desire to flash back to lessen. Take care. I'll be around
dicksteele said:
Agree.
I'm really having no issues with 5.1.1.
I'm with you, it was more of a challenge to see if it could be done. CM 13 seems to be moving along so that may take the desire to flash back to lessen. Take care. I'll be around
Click to expand...
Click to collapse
please guys for those who are on COH4 can you install partition backup (wanam) from store and give us the backup of
BOTA0
BOTA1
PARAM
please in raw partion image (img)
thank u by advance
please friends it will take you just a little of your time and if work it will help all
btw if you are in kitkat also you can give us
I am currently running CM 12.1
(Used CM13 with RazorKernel For some days which had a bootlogo)
Here's the partition info of our device
Code:
lrwxrwxrwx root root 2016-01-11 17:56 DDR -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-11 17:56 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-11 17:56 abootbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-11 17:56 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-01-11 17:56 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2016-01-11 17:56 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2016-01-11 17:56 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-11 17:56 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-11 17:56 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-11 17:56 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-11 17:56 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2016-01-11 17:56 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-11 17:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-11 17:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-11 17:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-11 17:56 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2016-01-11 17:56 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-11 17:56 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2016-01-11 17:56 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2016-01-11 17:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-11 17:56 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-11 17:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-01-11 17:56 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-11 17:56 sec -> /dev/block/mmcblk0p21
[COLOR="Red"]lrwxrwxrwx root root 2016-01-11 17:56 splash -> /dev/block/mmcblk0p18[/COLOR]
lrwxrwxrwx root root 2016-01-11 17:56 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-11 17:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-11 17:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-11 17:56 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-11 17:56 userdata -> /dev/block/mmcblk0p30
As you can see "mmcblk0p18" belongs to splash partiton.
I was successful in dumping splash.img on sdcard with adb shell as:
Code:
dd if=/dev/block/mmcblkp018 of=/storage/sdcard1/splash.img
But now what?
How to edit it?
I've searched for many hours but came up with mediatek or HTC guides which is pretty annoying -_-
Tools I've tried so far--> Android Kitchen, Kernel Kitchen, Logo Builder, nbimg tool.
Please help me through this.. I desperately want to make a splash image for my device.
noobpremium said:
I am currently running CM 12.1
(Used CM13 with RazorKernel For some days which had a bootlogo)
Here's the partition info of our device
Code:
lrwxrwxrwx root root 2016-01-11 17:56 DDR -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-11 17:56 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-11 17:56 abootbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-11 17:56 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-01-11 17:56 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2016-01-11 17:56 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2016-01-11 17:56 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-11 17:56 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-11 17:56 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-11 17:56 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-11 17:56 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2016-01-11 17:56 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-11 17:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-11 17:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-11 17:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-11 17:56 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2016-01-11 17:56 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-11 17:56 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2016-01-11 17:56 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2016-01-11 17:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-11 17:56 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-11 17:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-01-11 17:56 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-11 17:56 sec -> /dev/block/mmcblk0p21
[COLOR="Red"]lrwxrwxrwx root root 2016-01-11 17:56 splash -> /dev/block/mmcblk0p18[/COLOR]
lrwxrwxrwx root root 2016-01-11 17:56 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-11 17:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-11 17:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-11 17:56 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-11 17:56 userdata -> /dev/block/mmcblk0p30
As you can see "mmcblk0p18" belongs to splash partiton.
I was successful in dumping splash.img on sdcard with adb shell as:
Code:
dd if=/dev/block/mmcblkp018 of=/storage/sdcard1/splash.img
But now what?
How to edit it?
I've searched for many hours but came up with mediatek or HTC guides which is pretty annoying -_-
Tools I've tried so far--> Android Kitchen, Kernel Kitchen, Logo Builder, nbimg tool.
Please help me through this.. I desperately want to make a splash image for my device.
Click to expand...
Click to collapse
Which splash? Mi Logo splash? Tux Logo splash? Razor kernel splash I assume? If its Tux Logo splash, it is needed for some LCD types to work. For Mi Logo / Razor kernel splash I think, you must edit in kernel level and compile the kernel yourself.
I want to modify bootsplash too but im soo noob to do that,
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
nick37332001 said:
Which splash? Mi Logo splash? Tux Logo splash? Razor kernel splash I assume? If its Tux Logo splash, it is needed for some LCD types to work. For Mi Logo / Razor kernel splash I think, you must edit in kernel level and compile the kernel yourself.
Click to expand...
Click to collapse
Damn I dont have time to download sources and compile the kernel myself
Any other method to edit?
And yes its razor kernel splash (which is that blue thing ) or The Mi logo splash which appears before bootanimation.
But the thing is razor kernel had its splash and Kuma's cm12.1 dont!
Just that default "Linux's Penguin" appears in corner :3
Hope you got what I wanted to say
ketut.kumajaya said:
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
Click to expand...
Click to collapse
Okay Thanks for the reply. That's from kernel source I assume.
However I'll see to it
ketut.kumajaya said:
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
Click to expand...
Click to collapse
Too bad but I romoved ubuntu from pc just 2 dyas ago.. one more reason to regret -_-
maybe nick can do it :3
BTW any other method to do it? Like using cygwin?
noobpremium said:
Okay Thanks for the reply. That's from kernel source I assume.
However I'll see to it
Click to expand...
Click to collapse
Have you tried the latest version? I think kiran removed the logo
nick37332001 said:
Have you tried the latest version? I think kiran removed the logo
Click to expand...
Click to collapse
I dont want to flash CM13 now. I'm on 12.1.
Leave razorkernel. I'm not talking about 'only' razorkernel. If he is able to do so others should be too and for defferent kernel.
I've seen threads for bootlogo for motoX etc running lollipop
Anyways, do you have ubuntu? so you can run the script Kuma gave us link of.
noobpremium said:
I dont want to flash CM13 now. I'm on 12.1.
Leave razorkernel. I'm not talking about 'only' razorkernel. If he is able to do so others should be too and for defferent kernel.
I've seen threads for bootlogo for motoX etc running lollipop
Anyways, do you have ubuntu? so you can run the script Kuma gave us link of.
Click to expand...
Click to collapse
the script is python so you should be able to run it on windows.
nick37332001 said:
the script is python so you should be able to run it on windows.
Click to expand...
Click to collapse
Okay I'm nooob man. I didn't know that i can run it on windows, but I'll see to it.
Sent from my 2014818 using Tapatalk
nick37332001 said:
the script is python so you should be able to run it on windows.
Click to expand...
Click to collapse
Okay now here I am, successfully running that script on windows.
It created splash.img successfully but it was too small in size, around 65 KB :|
The one that i dumped was exactly 10MB.
Then also I flashed it but what I got was dessorted Mi logo and the same Penguin.
Now what? I'll see if I can decompile splash.img that I dumped using PIL.
Any help will be appreciated
Sent from my 2014818 using Tapatalk
You can give a try with Android Image Kitchen.....
Lennoard said:
You can give a try with Android Image Kitchen.....
Click to expand...
Click to collapse
Okay I'll see
Sent from my Xiaomi Redmi 2
noobpremium said:
Okay I'll see
Sent from my Xiaomi Redmi 2
Click to expand...
Click to collapse
Sorry for digging up old thread but how did it go? Did you manage to change default splashscreen?
What ive done myself so far was use X-Plore app with SuperSU access to copy splash file from /root/dev/block/bootdevice/by-name to external SD. In X-Plore splash file was 0b but upon copy it was 10MB.
Then i tried to use tool from other topic nbimg to convert splashscreen from 'unknown' format to BMP but result was bad. The tool is supposed to identify image resolution but it didnt know how in Redmi case (tool was orignally designed for HTC device i think) so i tried using w1280 h720 argument but result was like below:
http://i.imgur.com/sxYl65J.png
Well then i timply took any 720x720 image and used that nbimg tool to convert it to splash and then tried to replace it in /root/dev/block/bootdevice/by-name but on reboot it was reverted back to original
KonradIC13 said:
Sorry for digging up old thread but how did it go? Did you manage to change default splashscreen?
What ive done myself so far was use X-Plore app with SuperSU access to copy splash file from /root/dev/block/bootdevice/by-name to external SD. In X-Plore splash file was 0b but upon copy it was 10MB.
Then i tried to use tool from other topic nbimg to convert splashscreen from 'unknown' format to BMP but result was bad. The tool is supposed to identify image resolution but it didnt know how in Redmi case (tool was orignally designed for HTC device i think) so i tried using w1280 h720 argument but result was like below:
http://i.imgur.com/sxYl65J.png
Well then i timply took any 720x720 image and used that nbimg tool to convert it to splash and then tried to replace it in /root/dev/block/bootdevice/by-name but on reboot it was reverted back to original
Click to expand...
Click to collapse
No problem for digging old thread.
I did all the things exactly as what you did and had same results.
I still desperately want to make bootlogos for our belowed wt88047 but I just can't @ketut.kumajaya please just one hint for us and we will figure out rest.
I tried that python script on windows too but same broken splash.
Sent from my 2014818 using Tapatalk
@noobpremium @KonradIC13
[GUIDE] How to Create Custom Splash Screen (Boot Logo) for Redmi 2
No need to edit kernel.. The kernel has the logo that displays after Mi Boot Logo..
The boot logo (splash screen) is present in a separate partition..
GokulNC said:
@noobpremium @KonradIC13
[GUIDE] How to Create Custom Splash Screen (Boot Logo) for Redmi 2
No need to edit kernel.. The kernel has the logo that displays after Mi Boot Logo..
The boot logo (splash screen) is present in a separate partition..
Click to expand...
Click to collapse
What did you do exactly?
I'll have a look at your stuff and try it right now.
Seems you posted the thread just a while ago.
Sent from my 2014818 using Tapatalk
TWRP for backing up splash
noobpremium said:
What did you do exactly?
I'll have a look at your stuff and try it right now.
Seems you posted the thread just a while ago.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
Can I try the batman logo.bin file inside the zip I pointed you to, through this method?
Also, will taking a Backup through recovery work for this, or do I have to flash the whole fastbot ROM if this fails?
.
P.S - Found this, but am reluctant to try, as I have office in an hour. (Will it work if I have MM 6.0.1 installed as Primary ROM? As is says for KK in that thread)
http://en.miui.com/thread-114090-1-1.html
EDIT - Or will this be more relevant -
http://en.miui.com/thread-249552-1-1.html
shanx_verma said:
Can I try the batman logo.bin file inside the zip I pointed you to, through this method?
Also, will taking a Backup through recovery work for this, or do I have to flash the whole fastbot ROM if this fails?
.
P.S - Found this, but am reluctant to try, as I have office in an hour. [emoji14] [emoji14] (Will it work if I have MM 6.0.1 installed as Primary ROM? As is says for KK in that thread)
http://en.miui.com/thread-114090-1-1.html
EDIT - Or will this be more relevant -
http://en.miui.com/thread-249552-1-1.html
Click to expand...
Click to collapse
Just use his tool no need of any flashable zip or something.
Sorry I didn't get time for your batman logo. I'll try tonight.
Btw, you can make your logo easily with that tool.
After it's compiled, flash is with terminal emulator or just fastboot command
"fastboot flash splash splash.img" and done.
Sent from my 2014818 using Tapatalk
I recently flashed SuperSU v2.65 through TWRP since this seems to be the only SuperSU zip that flashes without freezing. Once the phone boots up, I update the SuperSU app through the Play Store, which brings me to v2.76. Upon launching the SuperSU app, it asks me to update the binary and then reboot, which runs smoothly. However, once I try to run Adaway, it gives me an error. Also, when I try uninstalling some apps through Titanium Backup Pro version, the app remains even after a reboot. And before anyone asks, yes, I did install BusyBox before launching both apps. Tell me what I need to do to resolve this. Perhaps TWRP is not flashing SuperSU correctly? I am not sure. Just thinking out loud.
So wait... this means your Axon 7 is basically rooted, right?
daneoleary said:
So wait... this means your Axon 7 is basically rooted, right?
Click to expand...
Click to collapse
Sounds to me like it's basically not rooted.
rczrider said:
Sounds to me like it's basically not rooted.
Click to expand...
Click to collapse
According to Root Checker, my device is rooted but I am stumped as to how to get these apps working.
B4oE said:
According to Root Checker, my device is rooted but I am stumped as to how to get these apps working.
Click to expand...
Click to collapse
Well you're more than halfway there! I'm impressed with the progress everyone is making.
B4oE said:
I recently flashed SuperSU v2.65 through TWRP since this seems to be the only SuperSU zip that flashes without freezing. Once the phone boots up, I update the SuperSU app through the Play Store, which brings me to v2.76. Upon launching the SuperSU app, it asks me to update the binary and then reboot, which runs smoothly. However, once I try to run Adaway, it gives me an error. Also, when I try uninstalling some apps through Titanium Backup Pro version, the app remains even after a reboot. And before anyone asks, yes, I did install BusyBox before launching both apps. Tell me what I need to do to resolve this. Perhaps TWRP is not flashing SuperSU correctly? I am not sure. Just thinking out loud.
Click to expand...
Click to collapse
Did you install the latest Adaway for systemless root?
Are the apps asking for root permission?
B4oE said:
I recently flashed SuperSU v2.65 through TWRP since this seems to be the only SuperSU zip that flashes without freezing..
Click to expand...
Click to collapse
Thanks you man, i try 2 different ones and the were freezing at Installing , but this one works...
daneoleary said:
So wait... this means your Axon 7 is basically rooted, right?
Click to expand...
Click to collapse
rczrider said:
Sounds to me like it's basically not rooted.
Click to expand...
Click to collapse
Yup the Axon 7 Have Root (systemless) and i'm afraid if you update via Play Store you lose systemless , but i'm not 100% sure about that , check screenshots
Kama45 said:
Are the apps asking for root permission?
Click to expand...
Click to collapse
that was exactly what i was going to ask cuz probably he decline or waited to long to accept the request
P.S. now i'm about to try and Install systemless xposed
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
B4oE said:
I recently flashed SuperSU v2.65 through TWRP since this seems to be the only SuperSU zip that flashes without freezing. Once the phone boots up, I update the SuperSU app through the Play Store, which brings me to v2.76. Upon launching the SuperSU app, it asks me to update the binary and then reboot, which runs smoothly. However, once I try to run Adaway, it gives me an error. Also, when I try uninstalling some apps through Titanium Backup Pro version, the app remains even after a reboot. And before anyone asks, yes, I did install BusyBox before launching both apps. Tell me what I need to do to resolve this. Perhaps TWRP is not flashing SuperSU correctly? I am not sure. Just thinking out loud.
Click to expand...
Click to collapse
I'm sorry if I'm taking your post out of context, my apologies if I screw up:
Does that means you already solved your bootloop issue or am I confusing the time stamps with this post and your bootloop post?
If you are past the bootloop, would you be so kind to explain what was wrong and how you fixed it? By updating your bootloop post!!
See, we can't be running around trying to please you, solving you issues because you are frenetically trying to root your phone (no offense intended), that's not how things works. Would you please be courteous and at least update your bootloop post, you did not reply a single time in there and there was people definitely trying to help.
B4oE said:
I recently flashed SuperSU v2.65 through TWRP since this seems to be the only SuperSU zip that flashes without freezing. Once the phone boots up, I update the SuperSU app through the Play Store, which brings me to v2.76. Upon launching the SuperSU app, it asks me to update the binary and then reboot, which runs smoothly.
Click to expand...
Click to collapse
Worked, thanks!
jkuczera said:
Worked, thanks!
Click to expand...
Click to collapse
Wow, weird. The phone *thinks* it's rooted. But it definitely is not.
Edit: Actually, I think it is rooted, but nothing persists after a reboot. I can get into /data/data and all the good spots.
But changing DPI/emojis doesn't take.
Someday, in android 4.4.2, i had exactly your problem.
I used kingroot, (chinese characters in su), only i done to fix, was change the kinguser, to superSu pro and ENGLISH CHARACTERS
Weird noh?
You can edit the flashable update.zip with winrar X86, or peazip X86, (ONLY) without extract the content, only you open the zip, and select the files , delete, and swipe the new files with mouse for recopy the zip architecture, ALL WITHOUT EXTRACTING (this is 100% that the zip file will not corrupt)
Much weird!
I learned this by practical facts...
Hehe
Sent from my XT687 using xda premium
Jose-MXL said:
I'm sorry if I'm taking your post out of context, my apologies if I screw up:
Does that means you already solved your bootloop issue or am I confusing the time stamps with this post and your bootloop post?
If you are past the bootloop, would you be so kind to explain what was wrong and how you fixed it? By updating your bootloop post!!
See, we can't be running around trying to please you, solving you issues because you are frenetically trying to root your phone (no offense intended), that's not how things works. Would you please be courteous and at least update your bootloop post, you did not reply a single time in there and there was people definitely trying to help.
Click to expand...
Click to collapse
You're completely correct. My apologies. I was simply busy at work. Anyway, I just replied to my original thread regarding my bootloop issue. Sorry again.
goalkeepr said:
Wow, weird. The phone *thinks* it's rooted. But it definitely is not.
Edit: Actually, I think it is rooted, but nothing persists after a reboot. I can get into /data/data and all the good spots.
But changing DPI/emojis doesn't take.
Click to expand...
Click to collapse
mmmm weird cuz this is after 2 reboots + reboot using my fav. reboot app (requires root -Simple Reboot App)
Code:
C:\ADB>adb shell
[email protected]_ii:/ $ su
su
[email protected]_ii:/ # ls -al /dev/block/bootdevice/by-name
ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 1970-01-08 21:12 aboot -> /dev/block/sde11
lrwxrwxrwx root root 1970-01-08 21:12 apdp -> /dev/block/sde21
lrwxrwxrwx root root 1970-01-08 21:12 bluetooth -> /dev/block/sde16
lrwxrwxrwx root root 1970-01-08 21:12 boot -> /dev/block/sde12
lrwxrwxrwx root root 1970-01-08 21:12 cache -> /dev/block/sda2
lrwxrwxrwx root root 1970-01-08 21:12 cdt -> /dev/block/sdd2
lrwxrwxrwx root root 1970-01-08 21:12 cmnlib -> /dev/block/sde19
lrwxrwxrwx root root 1970-01-08 21:12 cmnlib64 -> /dev/block/sde20
lrwxrwxrwx root root 1970-01-08 21:12 cryptkey -> /dev/block/sda8
lrwxrwxrwx root root 1970-01-08 21:12 ddr -> /dev/block/sdd3
lrwxrwxrwx root root 1970-01-08 21:12 devcfg -> /dev/block/sda5
lrwxrwxrwx root root 1970-01-08 21:12 devinfo -> /dev/block/sde15
lrwxrwxrwx root root 1970-01-08 21:12 dip -> /dev/block/sde9
lrwxrwxrwx root root 1970-01-08 21:12 dpo -> /dev/block/sde23
lrwxrwxrwx root root 1970-01-08 21:12 dsp -> /dev/block/sde8
lrwxrwxrwx root root 1970-01-08 21:12 echarge -> /dev/block/sde25
lrwxrwxrwx root root 1970-01-08 21:12 fbop -> /dev/block/sda6
lrwxrwxrwx root root 1970-01-08 21:12 frp -> /dev/block/sda7
lrwxrwxrwx root root 1970-01-08 21:12 fsc -> /dev/block/sdf3
lrwxrwxrwx root root 1970-01-08 21:12 fsg -> /dev/block/sde4
lrwxrwxrwx root root 1970-01-08 21:12 hyp -> /dev/block/sde3
lrwxrwxrwx root root 1970-01-08 21:12 keymaster -> /dev/block/sde18
lrwxrwxrwx root root 1970-01-08 21:12 keystore -> /dev/block/sda4
lrwxrwxrwx root root 1970-01-08 21:12 lksecapp -> /dev/block/sde17
lrwxrwxrwx root root 1970-01-08 21:12 mdtp -> /dev/block/sde10
lrwxrwxrwx root root 1970-01-08 21:12 misc -> /dev/block/sda3
lrwxrwxrwx root root 1970-01-08 21:12 modem -> /dev/block/sde7
lrwxrwxrwx root root 1970-01-08 21:12 modemst1 -> /dev/block/sdf1
lrwxrwxrwx root root 1970-01-08 21:12 modemst2 -> /dev/block/sdf2
lrwxrwxrwx root root 1970-01-08 21:12 msadp -> /dev/block/sde22
lrwxrwxrwx root root 1970-01-08 21:12 persist -> /dev/block/sdf5
lrwxrwxrwx root root 1970-01-08 21:12 pmic -> /dev/block/sde6
lrwxrwxrwx root root 1970-01-08 21:12 recovery -> /dev/block/sde14
lrwxrwxrwx root root 1970-01-08 21:12 reserve -> /dev/block/sdd1
lrwxrwxrwx root root 1970-01-08 21:12 rpm -> /dev/block/sde1
lrwxrwxrwx root root 1970-01-08 21:12 sec -> /dev/block/sde5
lrwxrwxrwx root root 1970-01-08 21:12 splash -> /dev/block/sde24
lrwxrwxrwx root root 1970-01-08 21:12 ssd -> /dev/block/sda1
lrwxrwxrwx root root 1970-01-08 21:12 sti -> /dev/block/sde26
lrwxrwxrwx root root 1970-01-08 21:12 system -> /dev/block/sde13
lrwxrwxrwx root root 1970-01-08 21:12 tz -> /dev/block/sde2
lrwxrwxrwx root root 1970-01-08 21:12 userdata -> /dev/block/sda9
lrwxrwxrwx root root 1970-01-08 21:12 xbl -> /dev/block/sdb1
lrwxrwxrwx root root 1970-01-08 21:12 xblbak -> /dev/block/sdc1
lrwxrwxrwx root root 1970-01-08 21:12 ztecfg -> /dev/block/sdf4
[email protected]_ii:/ #
that alone can only be pull having root + rebooting , maybe is something else???
P.S. i change the DPI using the following command NO REBOOT Require :
Code:
adb shell wm density 560
or Download the Terminal from Play Store and do
Code:
wm density 560
it will stick at boot, but there's some app that look pretty weird and the Bell/Notification at lock screen is huge LoL and yeah modifying Build.prop for some reason doesn't take place after boot.
I actually wanted to change dpi using textdroider specifically to test changes persisting after a reboot, which they didn't!
B4oE said:
You're completely correct. My apologies. I was simply busy at work. Anyway, I just replied to my original thread regarding my bootloop issue. Sorry again.
Click to expand...
Click to collapse
Hey sorry man, I've been really bothered trying to be everyone's dad around, that's not right, sorry about that.
I really appreciate you posted your method and that you actually provide the working flashable zip, you might help someone get a jumpstart right?
DrakenFX said:
Thanks you man, i try 2 different ones and the were freezing at Installing , but this one works...
Yup the Axon 7 Have Root (systemless) and i'm afraid if you update via Play Store you lose systemless , but i'm not 100% sure about that , check screenshots
that was exactly what i was going to ask cuz probably he decline or waited to long to accept the request
P.S. now i'm about to try and Install systemless xposed
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Click to expand...
Click to collapse
Were you able to get Xposed working?
goalkeepr said:
I actually wanted to change dpi using textdroider specifically to test changes persisting after a reboot, which they didn't!
Click to expand...
Click to collapse
yeah for some reason doesn't stick at boot using/modifying build.prop, only way is using either the Terminal or ADB , which instant no reboot and if you reboot will stick.
tdgillihan said:
Were you able to get Xposed working?
Click to expand...
Click to collapse
not yet, is way to much work LoL, i may just Flash the Original Xposed and give it a shot (don't care about Android pay or equivalent)....
backing up system and everything else will report after having xposed install
Jose-MXL said:
Hey sorry man, I've been really bothered trying to be everyone's dad around, that's not right, sorry about that.
I really appreciate you posted your method and that you actually provide the working flashable zip, you might help someone get a jumpstart right?
Click to expand...
Click to collapse
It's all good. No hard feelings. I'm just focused now on trying to find a stable SuperSU build that will allow root for Adaway and Titanium Backup. Just waiting for DrakenFX and Unjustified Dev to fix this.
tdgillihan said:
Were you able to get Xposed working?
Click to expand...
Click to collapse
yup, i have will brake systemless root if you are systemless, look at here http://forum.xda-developers.com/axon-7/how-to/guides-info-info-a2017u-bootloader-t3440254