Develop Bugs

Intki E91 ROM (Alps E91) - iPhone 5 clone replica Bricked, need stock or custom ROM

Hi all,
I've been playing around lately with this Dual Core Dual Sim device, named Intki E91, with Android 4.0.4, rooted it, then replaced the iPhone iOS style launcher with Samsung's TouchWiz launcher, all fine so far, but then proceeded to wipe all non-useful built-in apps with the help of Uninstall Master 3.2.0, then deleted all Chinese related stuff from the internal memory, at which point the phone resets, no longer boots and I am now stuck in the Android System Recovery 3e with no chance of ever restarting it. Power button + Volume Down takes me to a screen where it says "Enter factory mode" and it just hangs there so one has to remove the battery and then reboot only to get to the stock recovery again.
Now there is no ClockworkMod for this phone and the manufacturer here http://www.intkimobile.com/ did not reply to me when I mailed him about the problem, asking for the factory ROM.
I could only find a find a custom ROM (（E91动力）软件z19b-intki-e91-01_R01_user) on a Chinese website with a "MT6575_Android_scatter" file, but when attempting to flash it with SP Flash Tool 3.1304.0.119 it says Sp Flash Tool Error : 8200, "the load and target are inconsistent", "the load to be downloaded is for MT6575", "the target platform is MT6577_S00".
Afterwards, I looked for a different scatter file for 6577 processors and I found "MT6577_Android_scatter_emmc" file all over the web, then attempted to flash using that, but got the BROM ERROR : S_DA_EMMC_FLASH_NOT_FOUND (3144)
At this point I really do not know what else to attempt to revive this phone, I would really appreciate if someone extracted their stock ROM for this device and post it here as an "update.zip", or give instructions on how to bypass the SP Flash Tool errors, or made a custom recovery for this device so i could flash the above mentioned ROM with no errors, or even develop a custom ROM altogether.
Thanks for your time.
Edit: I flashed a custom recovery using the tutorial here: http://www.labandroid.com/china/2013/02/flash-cwm-recovery-to-mtk-phones-without-sp-flash-tool/ but it doesn't work, so now I no longer have a recovery.
My only hope is a solution through Smart Phone Flash Tool.
If only someone could make the errors go away...

The only thing left to do now is to try and format the Flash using SP Flash Tool, an see if that can enable a error-free flashing.
But it's a lot of hassle writing the imei's back afterwards. And if it doesn't work I will have a total brick...
Before proceeding, can someone confirm if formatting the flash fixes the SP Flash Tool errors (especially given its internal memory is a mere 512mb ? - could that be the cause of errors?)
Please advise...
Thanks

im in the same boat as u - struggling to find a working alps iphone 5 rom

hiphone5 MT6573
ushir said:
im in the same boat as u - struggling to find a working alps iphone 5 rom
Click to expand...
Click to collapse
Hello i have a clone hiphone 5 mt6573 and need some help please
can i install any custom roms please help. here's
my phones info
board: Unknown
bootloader: Unknown
brand: Aple
cpu_abi: Armeabi
cpu abi: Unknown
device: konka73_gb
display: alps.gb.fdd2.mp.v2.14
hardward: mt6573
manufacturer: Unknown
model: phone5
product: konka73_gb

Note II GT-N7102 16GB Dual-Sim Soft-bricked Help (& files) needed

Symptoms:
1. Boot loop. GT-N7102 logo comes and the device reboots.
2. Can go to download mode. Model no. GT-N7102 is visible
3. Recovery mode-Android shows up for ~4 seconds and then phone reboots and goes into a boot-loop.
Was running N7102ZCUEOJ1_JB43_deodex_gapps_root_noknox_lite_by _neopunk88 (since March'16), when the phone suddenly decided to go into a boot-loop.
The phone was rooted. I had installed LSpeed the previous night and had set it to run in recommended mode.
What I have tried so far
1. Odin 3.07, 3.09 etc
2. stock recovery flash fails
2. tried to flash N7102ZCUEOJ1_N7102CHNEOJ1_N7102ZCUEML1_HOME.tar.md5 (last stock), but fails
3. After I had exhausted possibilities, tried the following pit files, one at a time, first from here and then here and then here along with the stock ROM. All pit files seem legit and the correct ones, but I have no way to verify. I have tried first without and then with re-partition option selected in Odin. Flash fails.
4. All drivers, USB ports and cable okay as I can flash my wife's S6.
Phone still going into download mode.
Odin fail modes
1. without pit file, while flashing either recovery or stock rom, Odil fails just after sboot.bin at NAND write-start.
2. with pit file and re-partition checked, Odin gets stuck in "get pit file for mapping"
3. with pit file but re-partition unchecked, Odin fails is the same as (1)
4. I have tried setting Odin compatibility to XP but it does not result in anything different. I haven't needed xp compatibility setting this while flashing anything before.
Please could I have some guidance on what options I have left and the files, if I am not using the correct ones?
My belief is that if I can get to the download mode, there has to be way to un-brick the phone..fingers crossed.
Thanks in advance.
UPDATE: Fixed phone by replacing the motherboard from here. Everything working fine now.

still waiting for a response..

@jam_27 It is possible that eMMC got corrupted. (it's a hardware fail)
If I were you I would try to flash TWRP. http://www.twrp.me - For N7100, as it doesn't matter for recovery.
READ: http://forum.xda-developers.com/galaxy-note-2/help/nt7100-wont-boot-wont-charge-recover-t3504290

Thanks, TWRP recovery flash fails at NAND write start.

jam_27 said:
Thanks, TWRP recovery flash fails at NAND write start.
Click to expand...
Click to collapse
Below the JTAG tool report from FoneFunShop UK
eMMC Flash Memory Chip is damaged
===============
= JTAG REPORT =
===============
Open serial port...OK
Connecting to the RIFF Box...OK
Connecting to the dead body...OK
Detected dead body: DETECTED
Set I/O Voltage reads OK, TCK Frequency is OK
Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK
Flashing the dead body...
No Resurrection Data is available for the eMMC Chip with Capacity = 0B
ERROR: Failed use to Resurrection Data for the eMMC Chip with Capacity = 0B
ERROR: Selected FLASH Chip was not initialized by the DCC Loader.
----
I wont be able to replace the emmc chip myself (don't have the correct tools) but should be able to replace the motherboard.
Any other suggestions before I open up the until.

i9190 flash write failure error on boot recovery mode

Hi everyone,2 days ago when i woke up i pressed a home button for checking hour,my phone got freezed (i can't open lock screen) after like 30 second's my phone turn off itself. when i try to open it theres no response with power button also with volume+home+power button. after little search i found a file pit. file for booting phone with sd card,i did it and it partly works. i boot my phone on boot recovery mode but it stuck here afterwards.if you can help me i will be so grateful. what screen my phone stuck at is :
BOOT RECOVERY MODE (yellow colored letter's)
CHECK BOOT PARTITIONS.
COPY FROM T-FLASH.
BOOT RECOVERY. .
WRITE 139008 sectors. .
FLASH WRITE FAILURE (red colored letter's)
ddi : mmc_read failed
ODIN MODE (red colored letter's)
(after this line everything seem's normal) product name : gt-i9190 , current binary : Samsung Official , System Status : Custom , Knox kernel lock:0x0 , knox warranty void : 0x0 , csb-config-lsb : 0x30 , bootloader ap swrev 2 , write protection : Enable .
that's all on the screen where i stuck at..have a nice day , waiting your help

Failed to unbrick (flash write failure), please help

thank you for your kind help.
Serrano i9190 stopped worked today, I copied the debrik.img for i9190 4.4.2 (i've found it here: https://mega.nz/#F!wZtS2KzD!BSQdVcQkUNnE1yu5R8UowA) and the phone booted with it, but display:
WRITE 139008 sectors
FLASH WRITE FAILURE
ddi : mmc_read failed
ODIN MODE
...
WRITE PROTECTED: ENABLE
then I tried to flash with Odin an original Serrano i9190 .pit file and phone wrote:
MMC: read fail
PIT FAIL: TOTAL SECTORS (0)
Now am I using the proper files for debrik? Is it possible the Flash went fault and I can't read and write anything? What can I do here? Thank you!

Barabba11 said:
thank you for your kind help.
Serrano i9190 stopped worked today, I copied the debrik.img for i9190 4.4.2 (i've found it here: https://mega.nz/#F!wZtS2KzD!BSQdVcQkUNnE1yu5R8UowA) and the phone booted with it, but display:
WRITE 139008 sectors
FLASH WRITE FAILURE
ddi : mmc_read failed
ODIN MODE
...
WRITE PROTECTED: ENABLE
then I tried to flash with Odin an original Serrano i9190 .pit file and phone wrote:
MMC: read fail
PIT FAIL: TOTAL SECTORS (0)
Now am I using the proper files for debrik? Is it possible the Flash went fault and I can't read and write anything? What can I do here? Thank you!
Click to expand...
Click to collapse
That debrick image is for another phone, the i9195L. Not sure if that is why you get that msg, I would think it's not, but could be wrong. I think your memory chip has died most likely, probably needs replacing,

IronRoo said:
That debrick image is for another phone, the i9195L. Not sure if that is why you get that msg, I would think it's not, but could be wrong. I think your memory chip has died most likely, probably needs replacing,
Click to expand...
Click to collapse
thank you for your kind answer, on file was written i9190 4.4.2, so I guess was right one, but my phone was @ Nougat 7.1.2, can someone confirm that this debrick.img works also under these conditions?
How much can I be sure it there the mmc problem is not caused from the wrong .img? Also with Odin I have a failure if trying to write a .pit, what other tests can I do?
Thank you!

@Barabba11
FLASH WRITE FAILURE
ddi : mmc_read failed
That mines your Emmc Memory are dead.

bierma32 said:
@Barabba11
FLASH WRITE FAILURE
ddi : mmc_read failed
That mines your Emmc Memory are dead.
Click to expand...
Click to collapse
Thank you for you kind help,
just for being 100% sure, would you exclude that:
1) the debrick.img based on i9190 4.4.2 should work in any i9190, including if the phone was flashed with Nougat, it should write those 139008 sectors anyway so the fail is not connected with that.
2) WRITE PROTECTED: ENABLE, this is not a software protection rised up for some reasons. The mmc is failing and not a software protection, it is impossible to have a write protection booting with SD
So I can trash the motherboard and try to find a working one (for example from a broken screen)

Rooting Blackview A20

I have a blackview A20 which is a low spec phone running android oreo go.
I would like to use this phone for experimentation with android development and learning about android on a cheap device without risk of breaking my main phone. To do this I would like it rooted and as a bonus with a custom recovery so I can test custom ROMs.
State of device:
Unlocked bootloader
Unchanged ROM
Unchanged Recovery
OEM unlocking enabled
USB debugging enabled
What I have tried:
Flashing recovery images with fastboot
Using fastboot flash recovery recovery.img with some TWRP and CWM recovery images all yield:
target reported max download size of 134217728 bytes
sending 'recovery' (4690 KB)...
OKAY [ 0.169s]
writing 'recovery'...
OKAY [ 0.276s]
Click to expand...
Click to collapse
finished. total time: 0.448s
or similar. Then I restart phone and select boot into recovery mode. The phone hangs for a small while before restarting and booting into the normal OS. On restart into recovery the unchanged recovery is there still.​
Various 'one-tap' methods
All of which were unsuccessful. If needed I can give details.​
Installing SuperSU zip from recovery
In a futile attempt I tried to use the android recovery to push a SuperSU zip with its update from zip option. I knew this wouldn't work but I found something interesting. On the Apply update from SD card option I get an error saying couldn't mount /sdcard​
Booting recovery images with fastboot
I have tried the fastboot boot recovery.img command to try to boot directly into the images. I get this
downloading 'boot.img'...
OKAY [ 0.211s]
booting...
OKAY [ 0.047s]
finished. total time: 0.261s
Click to expand...
Click to collapse
output but the device just restarts and boots normally into the normal OS.​
What I would like from this question (In order of importance):
A way to root the device
A way to access a custom recovery (even if temporary)
Ability to install custom ROMs
A permanent custom recovery

mejakep said:
I have a blackview A20 which is a low spec phone running android oreo go...
Click to expand...
Click to collapse
I don't have this device but, you may find the following threads helpful because they, apparently, are compatible with your specific device. Don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=3709659
https://forum.xda-developers.com/showthread.php?t=3767690
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Hello,
I'm also trying to root the Blackview A20 with no success. Where you able to find a way?
Thanks!!

I'm afraid I still haven't found a way. Other than TWRP or something making a custom recovery specifically for this phone I don't see a way to root it at all. Sorry

I have a Blackview A20 Pro (note this is probably different in specification to the A20) - Here is how I rooted it by using Magisk on a boot image read and written using SPFlash tools. I had previously unlocked the bootloader on the phone by using the Developer option for OEM unlock and then fastboot unlocking as standard.
- Obtain the MT6739_Android_Scatter file from an archive of the a20 stock rom available by googling
- Install Magisk manager apk on the phone
- Run the latest version of SP Flash tools on the PC with the associated drivers. Load the scatter file in to it.
- Work out the size of the boot partition by subtracting the start value of the next partition (Logo) from the start position of (Boot)
- I did using Windows calculator in programmer mode - set to hex, subtract the two values. Note the start position of the boot partition
- Go to the Read Back page, add an item to read back, enter a filename to save it like a20-stock-boot-image.img and then enter the start position of the boot partition and the size you calculated. Make sure to get them exactly correct and avoid changing the number of digits in the entry box as I don't know how fussy sp-flash tools is.
- Unplug the phone from PC if it is plugged in and remove the battery.
- Tell SP Flash tools to start the read-back
- Plug the phone in, within a few seconds it should read and save the boot partition from the phone. Keep this backed up. File should be something between 8-25mb I would expect.
- Put the battery in the phone and power it up and unplug/plug it in to the PC via usb and then in the notification area on the phone select "Transfer Files" from the very bottom so it appears to your PC as a drive.
- Drag over the stock boot image from your PC somewhere on the phone - like the Downloads folder.
- On the phone open magisk and select install - when prompted select to use local boot image, select the stock boot image file you transferred
- Magisk should now patch this file - make sure the text it outputs looks like it recognized the boot image and is working.
- Now unplug and replug the phone to PC as I found PC doesn't seem to see new files on the phone. Pull over the patched boot image Magisk has made. Don't worry if this is smaller than the original file. The extra bytes were likely just zeros.
- Using SP Flash tool, go back to the Download screen and select the patched boot image for the boot partition. This will write the new boot image to your phone.
- Power down the phone and remove the battery.
- Tell SP flash tool to start and then plug the phone in with no battery. It should then flash the patched boot image.
- Put the battery back in and boot the phone. When you open magisk app on the phone now it should say you are rooted.
Enjoy!
If it doesn't work, repeat the download process with the stock boot image you saved and that should restore things to how they were before. I assume if it doesn't work it will just be because you need to unlock the bootloader or because your phone is different to the scatter file, but in that case I would expect Magisk to fail to patch it before you get to that stage.

How do you remove the battery? Have I missed something?
Sorry, wrong phone!!