FORUMS
Remove All Ads from XDA

Need help rooting coolpad legacy 3705A. Can't find any info anywhere.

3 posts
Thanks Meter: 0
 
By djdruin, Junior Member on 29th July 2019, 03:15 AM
Post Reply Email Thread
17th October 2019, 09:40 AM |#21  
Xplorer4x4's Avatar
Senior Member
Thanks Meter: 312
 
More
Quote:
Originally Posted by Sapphiress

Well let's see you do something there buddy, obviously you're the expert on the subject.

Cracking enterprise level security isn't just clicking a button. and you ain't paying me. I have a stack of phones and other devices to work on and other more pressing things to do with my life. So, kindly, take your opinion and shove it, root will be released when it's released.

Glad someone's working on it!
The Following User Says Thank You to Xplorer4x4 For This Useful Post: [ View ] Gift Xplorer4x4 Ad-Free
20th October 2019, 06:11 AM |#22  
Sapphiress's Avatar
Member
Flag Tampa, FL
Thanks Meter: 54
 
Donate to Me
More
Just a reminder as a new update for mPCS was pushed today, Do NOT update. This will update your devices security patch to August(even though it's October, really Metro? Can't even give up to date SecPatches?). I'm not 100% sure it's August just going by the build date of the file. It's most likely not android 10 as it's only 335.6MB.
23rd October 2019, 12:24 AM |#23  
Junior Member
Flag Orlando
Thanks Meter: 0
 
More
No update pushed to my cp. Hmm.... Wonder if it's a regional update? Still have June sec patch.
25th October 2019, 10:48 PM |#24  
Junior Member
Thanks Meter: 1
 
More
For every naysayer, there are many more of us who support you and appreciate your work.
The Following User Says Thank You to Baryn For This Useful Post: [ View ] Gift Baryn Ad-Free
3rd November 2019, 05:52 AM |#25  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by Sapphiress

I'll see if I can find one. They have the board incorrectly listed as both an MTK board and as an msm8953 even though from what I've been able to find msm8953 is strictly the snapdragon625. And Snapdragon 450 doesn't have an msm designation. This thing is a mess inside.

It's been awhile since I've done this mind you. Android has changed a bunch since the 2.X and 4.X days. I've been on a Nexus 6P for years which is open by default.

Wish it was as easy as installing gingerbreak and tapping root like the old days. Lol

---------- Post added at 03:14 PM ---------- Previous post was at 03:03 PM ----------



I would get temp root via a RCE or EoP pull the boot image, modify it and flash it in EDL therefore enabling fastboot and making the phone ready for TWRP. After that it's just a matter of writing a program that does this for you and the phone would be ready for development.


Ok, so I've done a little research and digging around and I found a couple large stashes of firehose files. One of them has quite a large collection of 8953 programmer files. Among those I came across one named prog_emmc_ddr_debug_8953_mmx.mbn and it seems to actually boot but once booted it wont list any partitions or work like we want it to probably because its not necessarily for this particular device. Long story short, it seems to partially work and the board listing for msm8953 isn't entirely incorrect apparently. I still have like 12 or so other variants of the 8953 firehose to test but I thought this was someone interesting and hoped maybe someone else with more knowledge on firehose files had some insight as to why it partially works. Information on this device is sparse to say the least but hopefully this is something we can work with. Any insight on this would be greatly appreciated! I'm linking the firehose in question so that someone else can help figure this out. Thanks!

Edit: I dont have enough posts on the forum to link yet so PM for a google drive link for prog_emmc_ddr_debug_8953_mmx.mbn.
3rd November 2019, 05:45 PM |#26  
Junior Member
Thanks Meter: 0
 
More
Anyone notice it doesn't come with a stock recovery?
Um.. not trying to be a n00b but has anyone tried to use the hardware keys to boot into recovery mode? Or even say using the ADB command to reboot recovery? Notice anything odd about the android logo and no other details or info what so ever. I would like to have root on the device, sure but i'd love to get a Recovery.img installed onto the device first and foremost. Unless there is a thread on XDA that i've missed due to wording the thread wrong or using a different information on the device. And just a small bit of reading their fine print. The CoolPad is owned by a company named: Yulong
So, since they really don't have much in software or even a footprint in the mobile phone game to be recognized as a brand to be listed on any site that i know of even by their mother company. I tried to look for a basic recovery that was made for Android P devices in general but i guess that would be the ideal method for the request.
4th November 2019, 06:26 AM |#27  
Junior Member
Thanks Meter: 0
 
More
Any update
4th November 2019, 09:02 AM |#28  
Sapphiress's Avatar
Member
Flag Tampa, FL
Thanks Meter: 54
 
Donate to Me
More
Quote:
Originally Posted by jpen7

No update pushed to my cp. Hmm.... Wonder if it's a regional update? Still have June sec patch.

It nagged me for about a week and now it's gone, they must have pulled it.

Quote:
Originally Posted by m3nty

Ok, so I've done a little research and digging around and I found a couple large stashes of firehose files. One of them has quite a large collection of 8953 programmer files. Among those I came across one named prog_emmc_ddr_debug_8953_mmx.mbn and it seems to actually boot but once booted it wont list any partitions or work like we want it to probably because its not necessarily for this particular device. Long story short, it seems to partially work and the board listing for msm8953 isn't entirely incorrect apparently. I still have like 12 or so other variants of the 8953 firehose to test but I thought this was someone interesting and hoped maybe someone else with more knowledge on firehose files had some insight as to why it partially works. Information on this device is sparse to say the least but hopefully this is something we can work with. Any insight on this would be greatly appreciated! I'm linking the firehose in question so that someone else can help figure this out. Thanks!

Edit: I dont have enough posts on the forum to link yet so PM for a google drive link for prog_emmc_ddr_debug_8953_mmx.mbn.

Send me a pm and I'll look into it.


Quote:
Originally Posted by TH3.CHNK

Um.. not trying to be a n00b but has anyone tried to use the hardware keys to boot into recovery mode? Or even say using the ADB command to reboot recovery? Notice anything odd about the android logo and no other details or info what so ever. I would like to have root on the device, sure but i'd love to get a Recovery.img installed onto the device first and foremost. Unless there is a thread on XDA that i've missed due to wording the thread wrong or using a different information on the device. And just a small bit of reading their fine print. The CoolPad is owned by a company named: Yulong
So, since they really don't have much in software or even a footprint in the mobile phone game to be recognized as a brand to be listed on any site that i know of even by their mother company. I tried to look for a basic recovery that was made for Android P devices in general but i guess that would be the ideal method for the request.

It's stock recovery it's just a strange thing with Android pie. My Nexus 6P would also do it sometimes, and a couple Samsung phones I've had e.g note 8, or j7 also do this. Recovery is there though.

Coolpad has been around awhile, I had the Coolpad Quattro back in the day when that was a giant screen phone. They're a small company and they're terrible at QC because this ROM in riddled with bugs, none that are useful just frustrating.

Quote:
Originally Posted by Zerkxy

Any update

Waiting on exploits. Any time you hear Android zero-day in the news would be a good time to check back

Unfortunately even though we're on a couple month old sec patch were there's only 2 notable exploits, neither of which were vulnerable to.



Tip: if you set the minimum width in developer settings to 600 you get the phablet UI in some apps. And this includes the desktop UI for chrome. Although it does make things small so if you don't have great eyes this may not be viable, and the gboard layout takes some getting used to.
6th November 2019, 07:11 AM |#29  
Member
Thanks Meter: 6
 
More
Just got this phone today haven't done any updates jw if root is available yet? Seems like people are working on it but no luck so far anyway I could be of help I've rooted my fair share of devices
6th November 2019, 08:32 AM |#30  
Junior Member
Thanks Meter: 0
 
More
Not sure if anyone has found this or not but I got it into fastboot. U have to enter it through stock recovery. I believe it second to last option under locale. Computer is broke down so can't try now if anyone else does, plz let us all know if it works thanks......
7th November 2019, 12:54 AM |#31  
Sapphiress's Avatar
Member
Flag Tampa, FL
Thanks Meter: 54
 
Donate to Me
More
Quote:
Originally Posted by Paulb98

Not sure if anyone has found this or not but I got it into fastboot. U have to enter it through stock recovery. I believe it second to last option under locale. Computer is broke down so can't try now if anyone else does, plz let us all know if it works thanks......

Fastboot is accessible but refuses all useful commands, OEM unlock switch literally does nothing. As this is on pie, and has dm-verity enabled, the best way to go about doing this to find a CvE that we're vulnerable too. However since this phones secpatch is only a coulple months old, there have only been 2 worthy exploits, but we are not vulnerable to them. In order to root it before a zero-day exploit would to be able to find a zero-day on the device itself, which I don't have the expertise nor patience for.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes