Rooting/Unlocking the EE Rook (ZTE Blade A410) -- Help needed plz
Rooting/Unlocking the EE Rook (ZTE Blade A410) -- Help needed plz
10-02-2016, 02:32 PM
I have done it. We have done it. You would not BELIEVE what the problem was.
I just succeeded this moment, so I'm still basking in success, before I actually verify with root checker and discover that it's all nonsense and I'm wrong
. Actually, I'm stopping to ask if I need to "wipe caches", or can I simply reboot system?
too late, i just rebooted. I will get you the screen shot in a moment. and then I'll tell you what was wrong. (Hint: you could have seen this too
)brb
scott
(10-02-2016, 02:23 PM)hovatek(10-02-2016, 03:55 AM)scott If you can suggest a way to update the phone with that factory original update.zip file (even though the recovery partition is zeroed out), perhaps I can begin again. BUt of course, if you can do that, then perhaps you can tell me how to flash your TWRP. (of course, they are very different files, one is update.zip and the other is a recovery.img)
I suspect the scatter file isn't a perfect fit.
I suggest you put that update.zip aside for now. As I earier said, I don't see it helping at this point.
What we need to focus on now is to get an sp flash tool format of a stock ROM / firmware for your exact model
10-02-2016, 02:59 PM
If i may, just a few last questions (for now anyway):
1. I had thought i would have to wipe all user data in the process. But in the end, i don't think i even needed to back up
. Is this because the bootloader is still locked?2. Is the bootloader still locked? And if so, is there some known way to unlock it?
3. Should I in fact wipe the cache or perform any other maintenance task before I go further?
Finally, you might be curious to know why it took me three solid days to be able to spend 3 minutes flashing the phone. In the end, I got the answer from the flash tools logs. I'm pretty sure that somehow I zeroed out my stock recovery, and I started looking at the logs to try to understand why i couldn't flash back the stock recovery. And the reason that I couldn't flash ANYTHING was this mismatch S_INVALID_BBCHIP_TYPE (1003). Why was this?
Because the phone reported having an MT6735M -- but the scatter file named the platform as MT6735 -- once I added the 'M' to the scatter file it worked instantly. There were two places, but I think only one matters:
1. The filename itself was Blade A410-MT6735_Android_scatter.txt. I changed it to Blade A410-MT6735M_Android_scatter.txt
2.In the general config section, I changed the line:
platform: MT6735
to
platform: MT6735M
Thank yo for your patience, truly.
Attached Files
10-02-2016, 08:59 PM
(10-02-2016, 02:59 PM)scott Thank yo for your patience, truly.
Glad I stopped by to check this post. Had been comparing other variant scatter files. there was MT6753M , MT6753P, MT6753 and then it hit me... The M and P suffix; but you already figured that out for your own type of scatter file.
Now, we face the Bootloader
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
11-02-2016, 08:14 PM
11-02-2016, 10:24 PM
(10-02-2016, 08:59 PM)hovatek(10-02-2016, 02:59 PM)scott Thank yo for your patience, truly.
Glad I stopped by to check this post. Had been comparing other variant scatter files. there was MT6753M , MT6753P, MT6753 and then it hit me... The M and P suffix; but you already figured that out for your own type of scatter file.
Now, we face the Bootloader
Wow, thank you for caring!!
Yes, the bootloader.
I shall look in the support pages of the 4 carriers that OEM this model phone. Otherwise, i'm stuck.
11-02-2016, 10:29 PM
(11-02-2016, 08:14 PM)jamieede Hi guys, I'm a brand new member, BUT I have been following this from day 0. This tread is the only REAL attempt to root my beloved ee rook. I see you have made real progress and it has been intriguing following it all. Good work. I just wish my USB port on the phone wasn't shot and only charges!
I'm glad that at least someone found my banging my head against the wall for a week to be entertaining.
I now have root, which is nice. I have one or two small detail questions to get clear about, and then I will write up a short end-to-end straight-line to go from out-of-box to root. No question but that I can save the next person to do this some time (and head-banging marks).
But I'd like to get the bootloader too, so stay tuned.
12-02-2016, 01:51 PM
(11-02-2016, 08:14 PM)jamieede Hi guys, I'm a brand new member, BUT I have been following this from day 0. This tread is the only REAL attempt to root my beloved ee rook. I see you have made real progress and it has been intriguing following it all. Good work. I just wish my USB port on the phone wasn't shot and only charges!
The rooting guide is @ https://www.hovatek.com/blog/how-to-root...k-from-ee/
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
12-02-2016, 01:54 PM
(11-02-2016, 10:24 PM)scott Wow, thank you for caring!!
Yes, the bootloader.
I shall look in the support pages of the 4 carriers that OEM this model phone. Otherwise, i'm stuck.
Have you tried fastboot OEM unlock in fastboot mode?
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
12-02-2016, 06:32 PM
(12-02-2016, 01:51 PM)hovatek(11-02-2016, 08:14 PM)jamieede Hi guys, I'm a brand new member, BUT I have been following this from day 0. This tread is the only REAL attempt to root my beloved ee rook. I see you have made real progress and it has been intriguing following it all. Good work. I just wish my USB port on the phone wasn't shot and only charges!
The rooting guide is @ https://www.hovatek.com/blog/how-to-root...k-from-ee/
Thank you!!
As my USB port on phone only charges and doesnt sow in device manager etc at all, I suspect broken pins, is it possible to adjust this method to make it on-device only using SD card? If not I shall take my phone apart and see if i can rectify the broken part
This post was last modified: 12-02-2016, 06:59 PM by jamieede.
Edit Reason: Extra info
12-02-2016, 10:01 PM
(12-02-2016, 06:32 PM)jamieede(12-02-2016, 01:51 PM)hovatek(11-02-2016, 08:14 PM)jamieede Hi guys, I'm a brand new member, BUT I have been following this from day 0. This tread is the only REAL attempt to root my beloved ee rook. I see you have made real progress and it has been intriguing following it all. Good work. I just wish my USB port on the phone wasn't shot and only charges!
The rooting guide is @ https://www.hovatek.com/blog/how-to-root...k-from-ee/
Thank you!!
As my USB port on phone only charges and doesnt sow in device manager etc at all, I suspect broken pins, is it possible to adjust this method to make it on-device only using SD card? If not I shall take my phone apart and see if i can rectify the broken part
Hovatek will have to give the authoritative answer, but I believe it will be "unfortunately not." The problem is that this phone has a locked bootloader, and this implies directly that only factory-signed .zip files can be installed. Custom recovery .zip files are of course not factory-signed and so cannot be installed.
Flashing via SP Flash Tool replaces the bits of the partition at a lower level than the install from an sd card; in particular, it doesn't matter if the bootloader is locked.
I suspect that one could bring up a terminal emulator on the phone and use mount and busybox dd to flash the necessary .img file to the correct /sys/class/block/mmcblk* piece of memory..... if one were root. Not much help.
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Users browsing this thread:
1 Guest(s)
1 Guest(s)
