Help with latest Custom Recovery for Infinix Hot 4. Android 7.0 v163
Help with latest Custom Recovery for Infinix Hot 4. Android 7.0 v163
30-11-2017, 10:10 AM
(29-11-2017, 11:26 PM)Ernest Ogberahwe I was able to unlock the bootloader. Your reply came later as I had already tried the fastboot flash recovery recovery.img . It was successful I rebooted and tried rebooting into recovery still brought the stock recovery.. I was almost giving up thinking it something that has to do with the recovery until I saw your reply tonight. So I tried the other command boot recovery.img ... It booted into Philz recovery... Lol... SuperUser zip was already in my sdcard so I installed it but along the operation of installation I noticed that when it got to _Boot Image Patcher" it ended with a failure..
I will write out the chain of strings . Something like this:
Boot image Patcher
--Finding boot image
--Boot image:/Dev/block/mmcb1kop7
--Extracting ramdisk
--Decompressing ramdisk
--Checking patch status
--Creating backup
--Patching sepolicy
--Adding init script
--Creating mount point
--Patching init,*rc, database, file_contexts, dm-verity
--Creating ramdisk backup
--- Failure, aborting
--Unmounting System
-- Done!
Install from sdcard complete
Press any key to continue.
While still in Philz recovery I attempted to reboot system. Something like this showed up:
Root access is missing/broken
THIS CAN NOT BE UNDONE
--NO
--YES — Apply root (/system/xbin/su)
-- NO
I first picked No but upon rebooting SuperUser wasn't installed.. Even If I pick yes SuperUser is not installed on phone.. that means the installing wasn't successful from recovery mode.. So am thinking maybe it has to do with the SuperUser ....
The SuperUser zip I have is v2.76
P.s.: somehow somehow Philz recovery seems to have been flashed and with the help of adb phone now boots into Philz recovery..
What do you suggest we do now? At least Philz recovery has now replaced the stock recovery.. so no more issue of recovery not flashing...
Could it be the version of SuperUser??
I knew the recovery wasn't the problem
When Philz asks to apply root, always select NO. YES could have bricked your phone.
Try using the latest version of SuperSu and copy to phone storage, not SD card .
If that fails then you'll need to consider using Magisk
This post was last modified: 30-11-2017, 10:11 AM by hovatek.
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.
30-11-2017, 12:03 PM
(30-11-2017, 10:10 AM)hovatek(29-11-2017, 11:26 PM)Ernest Ogberahwe
I knew the recovery wasn't the problem
When Philz asks to apply root, always select NO. YES could have bricked your phone.
Try using the latest version of SuperSu and copy to phone storage, not SD card .
If that fails then you'll need to consider using Magisk
Philz recovery only detected/brought out the sdcard but not phone memory because I put SuperSU in both phone number sdcard memory.
Nawa ooo.. from sp flash tools to Miracle Box to adb fastboot to bootloader now Magisk.
Please tell me about the Magisk. Lemme be prepared down before evening....
30-11-2017, 09:07 PM
Rebooted device. Now my phone is officially Rooted...
Below is a link to root checker verification
https://www.dropbox.com/s/3ratpzp9pd5zrt...2.png?dl=0
Hovatek. Thank you so much for your time and patience. I really appreciate your efforts ...
This post was last modified: 30-11-2017, 09:08 PM by Ernest Ogberahwe.
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Users browsing this thread:
1 Guest(s)
1 Guest(s)
