Hey,
I bootlooped my MT6575-based phone (a Motorola RAZR D1, not much information on it in English) by doing a bad build.prop edit (LCD density modder). I'm trying to recover it by reverting build.prop, but I'm running into several problems:
Can't use ADB from stock recovery. Windows gives "USB Device Not Recognized" and Linux gives "can't read configurations, error -22" on dmesg. I tried PDAnet, Mediatek VCOM and Motorola Device Manager drivers.
There's no CWM (let alone zip-format ROMs) for the device
I tried making a recovery script for the stock recovery myself, but it says "Installation aborted" for a fraction of a second then reboots
Flashing the stock ROM with Motorola's tools (tried 2 of them) doesn't work, the phone reboots after flashing starts
I found somebody who dumped the stock ROM as a .backup file made using the stock recovery, but it seems to be checksum-verified, so it fails on my device
SP Flash Tools seems to require an authentication file, and the one included in Motorola's stock ROM doesn't work. From what I read on a shady-looking phone flashing website (nothing about authentication errors on XDA), there's no way out of that.
I have access to the SD card, stock recovery (no ADB) and fastboot (locked, unlocking gives "..."). I have the stock ROM in Motorola .mzf (also uncompressed into partition images) and stock recovery .backup formats. Am I SOL?
Related
Problem:
My phone stopped working, due to a software issue (i'm 99% sure about this). I tried flashing it with a new rom, that almost bricked it (well, i can flash other roms to it, the led lights up, keypad lights up, etc).
I used SP Flash Tool (the only tool i know how to use), i load the scatter file and then click download, connect the phone, etc... the rom loads ok, just that i didn't had the proper rom.
I have recently found a RECOVERY ROM for this (don't know if ROM is the proper word for this, i've found the files that are used with SP Flash) - but it's missing the system.img, secro, cache and userdata .img files
I tried to load these files from other roms, all went ok, phone started but it hangs when it starts at the boot screen.
A few hrs ago i've found the proper software for my phone, but instead of the .img files i need, i have only the system folder that contains the build.prop file and the other folders, app, bin, etc, fonts...
How can use the SP Flash Tool to load this on to my phone? How can i convert this into the .img files i need?
Hello everybody !
Two days ago, I bought the Acer Liquid E3 (single SIM, not Duo), and after some research and a good thinking time, I went for rooting my device. I used the instructions provided on the official thread (actually, I used this simpler and french version provided by Shreps, since that's my mother tongue, but I checked that every step was the same).
I also checked that since my device is the single sim model, it wouldn't prevent the operations to go as intended. There is no clear info about this on the thread, but some guy having the same model as me didn't complain about anything, so I assumed he was able to root his phone with no problem.
As said in the instructions, I put the UPDATE-SuperSU-v1.99.zip file on my SD card, I installed the VCOM drivers to my computer, used SP Flash Tools to flash CWM 6.0.3.0 Recovery on my device, booted in Recovery mode (it was indeed CWM Recovery that booted), then navigated to :
install zip from sdcard > choose zip from sdcard > "UPDATE-SuperSU-v1.99.zip" > Yes - Install UPDATE-SuperSU-v1.99.zip
Everything seemed to go well, no error prompted and the operations ended with "Done !"
However, when I rebooted in normal mode ("reboot system now" in CWM Recovery) and checked with Root Checker, it was said that I wasn't root. SuperSU isn't installed, and when I manually look for the su binary, it can't be found neither in bin nor in xbin.
I did everything (from flashing CWM to install root from sdcard) again and again, and nothing changes. I tried to download again my SuperSU file or use an anterior version (v1.86) but it's still the same problem.
tl;dr : I tried to root via CWM Recovery, but even if no error prompts, su isn't neither in bin nor xbin.
Would you have an idea of what I'm doing wrong ? (And would be able to explain it to me in understable terms ? Even if I understand every step I've been through, I'm not very familiar with the rooting glossary...)
Also, by looking into the SuperSU zip, I found the installation script. Would it be dangerous to try these commands manually via ADB ? Could it work where the script failed (or help find the 'root' of the problem ?)
I have a last (but secondary) question : on the tuto from the official thread and its french version, it is said that I should change the name of "/system/recovery-from-boot.p" to "/system/recovery-from-boot.p.bak" to keep my custom Recovery ROM after a reboot, or the Stock Recovery would wipe it. As I failed to root the phone, I could change this file name, of course, but however, when I boot my phone into Recovery mode (unplugged from the computer), it boots directly on CWM Recovery.
It doesn't bother me as long as I have an operating Recovery ROM, but I was wondering if it was normal since I did nothing to keep CWM.
NB : I attached to this question a screenshot of the About menu of my Device, since it contains informations on my build version and maybe other things.
Hello,
i have a THL T6s smartphone with Android 5 official OTA update, 5-point touch version.. But there's a little problem.. I can't root him, i can't flash custom recovery.. I managed to delete recovery-from-boot.p file from phone (very difficult way, i had to readback rom with SP Flash tool, then install drivers and mount system.img in Windows 8.1, rename that file and then flash it back.. ). I still have that modified system.img, it's working, MTK droid tools are no longer displaying an error (with that file, it's flashing stock recovery on every boot), but when i flash a custom recovery from internet, the screen displays horizontal black stip and then the screen slowly fades out.. I can't create CWM using MTK Droid tools, because it's displaying error (--- ERROR :No find KernelGZ --- ERROR :No Split Boot Image).. I see only one way, rooting the system.img with PC.. Can anyone tell me how to do it? I'll be glad, if anyone can post there a tutorial or something similiar, step by step..
P.S.: to create CWM i'm using boot.img from readed back rom..
Thanks,
Neth
Phone Details:
Phone: Huawei G525
Recovery: TWRP
Bootloader: Unlocked
Access through Fastboot - Yes
Access through ADB - Yes
Status: Bootloop/No OS
I made a terrible mistake and someone managed to ruin the stock ROM came with this, when I was trying to install a custom ROM. Ever since, despite all my efforts, I can't flash either a stock ROM or a custom ROM. Here are the methods I've tried and failed.
Standard custom ROM update by placing the dload folder - it fails after a few minutes. Tried a few different ROMs
Standard custom ROM install method using recovery - gives errors such as zip cannot be opened. Tried 2-3 different zips using two different microSD cards.
ADB sideload custom ROM zip - It loads the zip but returns an error "E: ZIP file is corrupt!"
Extracting img files from stock ROM and loading through fastboot - I can load all except system.img as it is too big to load. I looked everywhere to find a way to create a smaller size img file but none of the attempts worked.
Could someone direct me to the right direction to get this fixed pretty please?
Many thanks in advance!
Hey friends,
I want to see if anyone has had this experience and can point me to a fix/resolution. The "main" issue is the Micro USB port is no longer operable, so I CAN NOT just re-flash with SP Tools (I so would have just). I'm keeping the phone charged with a wireless charger. I can boot to TWRP, in fact it bootloops into TWRP. I'm using the "DOOGEE-S60-Android 8.0 (9.2)_TWRP_ROOT_Final" rom, which I was flashing with SP Tools and extracting .imgs from it for testing.
Here's how the issue started; I was updating Magisk Modules and configuring the Hide Props for device emulation (I've done this multiple times looking for a solid working set and had to reflash for the same reasons several times, so I know it started with the Magisk module updating the boot img). At some point during the module updating the boot image seems to get corrupted and I get stuck bootloop into TWRP. This is an MTK device so reflashing with SP Tools and going about business is the normal simple fix..
Since my Micro USB is damaged and I can't flash with SP Tools now, TWRP recovery is the only resolution for this slowly dying device. I simply don't have a lot of experience with this particular issue and this is my first MTK device. I've been able to in TWRP;
1. Factory Reset - No resolution
2. Flash .imgs for boot.img, System.img, tee.img, and recovery.img (built in TWRP recovery for the rom which just resets TWRP, luckily) - No resolution, still bootloops to TWRP
3. chomd 755 adb & fastboot bins to system/bin (for the hell of it so I can terminal to either from within TWRP, can't seem to connect device though)
4. Wiped system completely and restored with with the system.img, by accident actually, and thought TWRP didn't have access enough to write it back, but it does
*edit1; 5. Tried using "dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc" from here. Returned "no such file found". After looking through the file explorer I imagine the file structure maybe different for this device though "dev/block" root is there. Maybe a transfer of different files?
So now I'm coming to see if anyone has any helpful info for recovering the boot to normal system on an MTK device only through TWRP (Which I'm pretty sure I've done multiple times over devices on Snapdragon devices)
Things that do work as current;
1. TWRP
2. External SD for transfering
3. Terminal within TWRP
4. Mounting System R/W
I'm thinking I "could" flash an OTA "Update.zip" for the device in TWRP, but there isn't one. This device only uses FOTA which seems to need the SP Tools type approach.
DemonLoader said:
Hey friends,
I want to see if anyone has had this experience and can point me to a fix/resolution. The "main" issue is the Micro USB port is no longer operable, so I CAN NOT just re-flash with SP Tools (I so would have just). I'm keeping the phone charged with a wireless charger. I can boot to TWRP, in fact it bootloops into TWRP. I'm using the "DOOGEE-S60-Android 8.0 (9.2)_TWRP_ROOT_Final" rom, which I was flashing with SP Tools and extracting .imgs from it for testing.
Here's how the issue started; I was updating Magisk Modules and configuring the Hide Props for device emulation (I've done this multiple times looking for a solid working set and had to reflash for the same reasons several times, so I know it started with the Magisk module updating the boot img). At some point during the module updating the boot image seems to get corrupted and I get stuck bootloop into TWRP. This is an MTK device so reflashing with SP Tools and going about business is the normal simple fix..
Since my Micro USB is damaged and I can't flash with SP Tools now, TWRP recovery is the only resolution for this slowly dying device. I simply don't have a lot of experience with this particular issue and this is my first MTK device. I've been able to in TWRP;
1. Factory Reset - No resolution
2. Flash .imgs for boot.img, System.img, tee.img, and recovery.img (built in TWRP recovery for the rom which just resets TWRP, luckily) - No resolution, still bootloops to TWRP
3. chomd 755 adb & fastboot bins to system/bin (for the hell of it so I can terminal to either from within TWRP, can't seem to connect device though)
4. Wiped system completely and restored with with the system.img, by accident actually, and thought TWRP didn't have access enough to write it back, but it does
*edit1; 5. Tried using "dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc" from here. Returned "no such file found". After looking through the file explorer I imagine the file structure maybe different for this device though "dev/block" root is there. Maybe a transfer of different files?
So now I'm coming to see if anyone has any helpful info for recovering the boot to normal system on an MTK device only through TWRP (Which I'm pretty sure I've done multiple times over devices on Snapdragon devices)
Things that do work as current;
1. TWRP
2. External SD for transfering
3. Terminal within TWRP
4. Mounting System R/W
I'm thinking I "could" flash an OTA "Update.zip" for the device in TWRP, but there isn't one. This device only uses FOTA which seems to need the SP Tools type approach.
Click to expand...
Click to collapse
Any chance of a hardware fix? Replacing the damaged port?
Nephiel said:
Any chance of a hardware fix? Replacing the damaged port?
Click to expand...
Click to collapse
I "would" just simply do that, but the device is older, and since there aren't any factory updates for the OS, it's not really worth the time and effort to buy and solder. It's more fun to find a way through the software at this point..
Why is there no custom rom for Doogee S60? . android 8? 9? 10 ?. where can I find it?
Why is there no custom rom for Doogee S60? . android 8? 9? 10 ?. where can I find it?. Compatible for Doogee S60? custom rom android 8 9 10?