Develop Bugs

[ROM][G3U] HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox+init.d

@SPSPaWn posted the Russian Desire 300 dump on 4pda, so I decided to mod it with Android Kitchen.
It's deodexed, zipaligned, rooted and has busybox and init.d support added.
Flash it in recovery and do a full wipe before flash (system also has to be wiped as well)
Download link - http://d-h.st/t4R
@xaak

Thnkx buddy ...!!

thanks..Anyone tried it? it works?
Sent from my HTC Desire 300 using XDA Premium 4 mobile app

FOR HTC Desire 300/Zara Mini
CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn enhanced
How to install CWMRecovery:
1. extract archive CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn.rar
2. folder clockworckmod copy to your sd card
3. reboot device into fastboot
4. flash recovery - fastboot.exe flash recovery recovery.img
5. reboot device
How to install root:
1. download UPDATE-SuperSU-v1.86.zip and copy in your sd card
2. reboot device into CWMRecovery
3. select - install zip from sd card and install SuperSU
my Thread in 4PDA HTC Desire 300

Is this confirmed working?

will this work on chinese 301e ....because these is no playstore in chinese version

aamszia said:
will this work on chinese 301e ....because these is no playstore in chinese version
Click to expand...
Click to collapse
Can I have a copy of your build.prop?

MameTozhio said:
@SPSPaWn posted the Russian Desire 300 dump on 4pda, so I decided to mod it with Android Kitchen.
It's deodexed, zipaligned, rooted and has busybox and init.d support added.
Flash it in recovery and do a full wipe before flash (system also has to be wiped as well)
Download link - http://d-h.st/t4R
@xaak
Click to expand...
Click to collapse
i got status(0) error while flashing this rom :'( . what's wrong ?

MStevie said:
i got status(0) error while flashing this rom :'( . what's wrong ?
Click to expand...
Click to collapse
maybe this was created to kill your phone?

so i recieved another phone ... still no rom
chinese 301e

SPSPaWn said:
FOR HTC Desire 300/Zara Mini
CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn enhanced
How to install CWMRecovery:
1. extract archive CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn.rar
2. folder clockworckmod copy to your sd card
3. reboot device into fastboot
4. flash recovery - fastboot.exe flash recovery recovery.img
5. reboot device
How to install root:
1. download UPDATE-SuperSU-v1.86.zip and copy in your sd card
2. reboot device into CWMRecovery
3. select - install zip from sd card and install SuperSU
my Thread in 4PDA HTC Desire 300
Click to expand...
Click to collapse
i got status(0) error while flashing this rom

I also have this error when I try to flash the HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox + init.d
Stock ODEX root 1.10.401.4 updated works without a problem.

what is problem ?
C:\>fastboot devices
SH3CRWL00209 fastboot
C:\>fastboot flash recovery recovery.img
target reported max download size of 421527
sending 'recovery' (6910 KB)...
OKAY [ 1.250s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.016s
---------- Post added 12th October 2014 at 12:05 AM ---------- Previous post was 11th October 2014 at 11:40 PM ----------
i need coustom rom ....

maplegsm said:
what is problem ?
C:\>fastboot devices
SH3CRWL00209 fastboot
C:\>fastboot flash recovery recovery.img
target reported max download size of 421527
sending 'recovery' (6910 KB)...
OKAY [ 1.250s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.016s
---------- Post added 12th October 2014 at 12:05 AM ---------- Previous post was 11th October 2014 at 11:40 PM ----------
i need coustom rom ....
Click to expand...
Click to collapse
You need to unlock the bootloader go to http://www.htcdev.com/ and click "Unlock Bootloader" select other device from the list and follow the instructions. Hope this helps.

where is dev? say something? Ram cosuption, speed, specs, changelog(or in OP is what it has done?), where are testers??? Nobody could confirm that rom is: fully working, partially, not working, bugs...??????

RamHa said:
where is dev? say something? Ram cosuption, speed, specs, changelog(or in OP is what it has done?), where are testers??? Nobody could confirm that rom is: fully working, partially, not working, bugs...??????
Click to expand...
Click to collapse
This is just a stock system dump I did about 2 years ago that was meant to be flashable with root but it doesn't flash properly for some, I won't be updating it any further.

Hello!
I flashed CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn to Unofficial TWRP Recovery 2.6.1.0 and wipe all data and installed from zip via Recovery this ROM [G3U] HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox+init.d and I have to tell you that is working.
Finally this phone get some speed.Wife is happy

Riski3Run said:
Hello!
I flashed CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn to Unofficial TWRP Recovery 2.6.1.0 and wipe all data and installed from zip via Recovery this ROM [G3U] HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox+init.d and I have to tell you that is working.
Finally this phone get some speed.Wife is happy
Click to expand...
Click to collapse
That's good! Just be sure to disable automatic receiving of MMS messages as this is vulnerable to all the stagefright exploits.

f
C:\Users\mwesiga2015\Desktop\htc\ADB> fastboot.exe flash recovery recovery.img
< waiting for device >
sending 'recovery' (6910 KB)... OKAY [ 1.463s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.563s
C:\Users\mwesiga2015\Desktop\htc\ADB> fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.340s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.440s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.310s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.410s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.347s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 9.641s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.382s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.482s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.330s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.430s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.340s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.440s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.330s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.430s
C:\Users\mwesiga2015\Desktop\htc\ADB>

Need help with rooting M8

I apologize for my n00b-ness. I went to Windows Phone (yeah, go ahead and laugh) for a little over a year, and am somewhat out of the rooting scene.
So I installed the TWRP 2.7.0.3 recovery based on the thread in this sub-forum here:
http://forum.xda-developers.com/showthread.php?t=2698134
Everything appears to have worked:
Code:
C:\android-sdk\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.247s]
finished. total time: 0.247s
C:\android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (12496 KB)...
OKAY [ 1.212s]
writing 'recovery'...
OKAY [ 0.763s]
finished. total time: 1.974s
C:\android-sdk\sdk\platform-tools>
I'm not sure what to do from here. When my phone boots, I hold power to reboot, and I don't see any "reboot into recovery" option like I've seen on past phones. Is there another way I should access recovery so that I can finish rooting my phone? Or should flashing TWRP have effectively rooted it?
Thanks for any help.

ChodeNode said:
I apologize for my n00b-ness. I went to Windows Phone (yeah, go ahead and laugh) for a little over a year, and am somewhat out of the rooting scene.
So I installed the TWRP 2.7.0.3 recovery based on the thread in this sub-forum here:
http://forum.xda-developers.com/showthread.php?t=2698134
Everything appears to have worked:
Code:
C:\android-sdk\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.247s]
finished. total time: 0.247s
C:\android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (12496 KB)...
OKAY [ 1.212s]
writing 'recovery'...
OKAY [ 0.763s]
finished. total time: 1.974s
C:\android-sdk\sdk\platform-tools>
I'm not sure what to do from here. When my phone boots, I hold power to reboot, and I don't see any "reboot into recovery" option like I've seen on past phones. Is there another way I should access recovery so that I can finish rooting my phone? Or should flashing TWRP have effectively rooted it?
Thanks for any help.
Click to expand...
Click to collapse
Press power restart when it goes off hold power volume down
Or download twrp app from play store

ChodeNode said:
I apologize for my n00b-ness. I went to Windows Phone (yeah, go ahead and laugh) for a little over a year, and am somewhat out of the rooting scene.
So I installed the TWRP 2.7.0.3 recovery based on the thread in this sub-forum here:
http://forum.xda-developers.com/showthread.php?t=2698134
Everything appears to have worked:
Code:
C:\android-sdk\sdk\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.247s]
finished. total time: 0.247s
C:\android-sdk\sdk\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 1830711296 bytes
sending 'recovery' (12496 KB)...
OKAY [ 1.212s]
writing 'recovery'...
OKAY [ 0.763s]
finished. total time: 1.974s
C:\android-sdk\sdk\platform-tools>
I'm not sure what to do from here. When my phone boots, I hold power to reboot, and I don't see any "reboot into recovery" option like I've seen on past phones. Is there another way I should access recovery so that I can finish rooting my phone? Or should flashing TWRP have effectively rooted it?
Thanks for any help.
Click to expand...
Click to collapse
Why don't you use one of the toolboxes:
http://forum.xda-developers.com/showthread.php?t=2699065

b0gd4n said:
Why don't you use one of the toolboxes:
http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
Cause toolkits are lazy and it should be encouraged to do everything manually where possible so that you understand what's actually happening so you have the knowledge to fix any possible issues
Just my 2p...

It appears the issue was my n00bness. I assumed the hboot menu would be replaced with the recovery screen. Didn't see the recovery option there in the list. Of course I use that menu item and I'm good to go.
Yeah - I'm dumb.

[SOLVED] Can't flash stock recovery 4.20.531.4

I downloaded the stock recovery for 5.0.1 from here http://forum.xda-developers.com/showpost.php?p=51836232&postcount=1
When I go into fastboot and try to flash I get an error:
$ fastboot flash recovery Tmo-M8-4.20.531.4-recovery.img
target reported max download size of 1826152448 bytes
sending 'recovery' (16046 KB)...
OKAY [ 1.753s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
This is with bootloader unlocked, if I try with bootloader locked I get:
$ fastboot flash recovery Tmo-M8-4.20.531.4-recovery.img
target reported max download size of 1826152448 bytes
sending 'recovery' (16046 KB)...
OKAY [ 1.757s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.763s
I notice theres a 1mb difference between twrp-2.8.7.0-m8.img (17.4mb) and Tmo-M8-4.20.531.4-recovery.img (16.4mb)
How am I supposed to get the stock recovery back without erasing anything else?
Device is S-OFF

Wow, turned out to be a bad download :| Redownloaded and it flashed fine
CHECK MD5 SUMS BEFORE FLASHING
Some screwed up stuff could have happened, thankfully even S-OFF does have some precautions.
MOD EDIT

Stuck on TWRP after accidental factory reset

I was about to manually install the lineageOS update, but I accidentally swiped factory restore. Is there anyway I can get the update file online? I tried starting from the top by wiping everything and reinstalling the rom but it only boots me into TWRP. I also tried restoring backup files but is also boots me into TWRP. I am stuck.
PS: I tried the "fastboot continue" method but it boots me into TWRP.

reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually

sukhwant717 said:
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
Click to expand...
Click to collapse
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?

lemuelermita said:
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
Click to expand...
Click to collapse
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash

sukhwant717 said:
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
Click to expand...
Click to collapse
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?

lemuelermita said:
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
Click to expand...
Click to collapse
raw is definitely best option. are you able to mount data and cache partition in TWRP

sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?

sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
Defensively smartest guy about phones in the world!!! ahaha <3

lemuelermita said:
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
Click to expand...
Click to collapse
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thank you very much, Sir! I will give you an update soon.

lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
Followed the instructions on the link but my phone boots up on a blinking screen with an android saying "Error". The command prompt failed at steps 4,5, and 11.
C:\Users\Lemuel\Documents\RESTOCK>fastboot devices
F5AZFG14A156 fastboot
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem erase_osip_header
...
OKAY [ 0.217s]
finished. total time: 0.219s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.228s]
finished. total time: 0.231s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.194s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.384s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.205s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.394s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem partition /tmp/partition.tbl
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.560s]
finished. total time: 0.561s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase data
******** Did you mean to fastboot format this ext4 partition?
erasing 'data'...
OKAY [ 1.447s]
finished. total time: 1.448s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase APD
******** Did you mean to fastboot format this ext4 partition?
erasing 'APD'...
OKAY [ 0.290s]
finished. total time: 0.294s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase ADF
******** Did you mean to fastboot format this ext4 partition?
erasing 'ADF'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem wipe splashscreen
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.210s]
finished. total time: 0.212s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash splashscreen splash_sign.bin
target reported max download size of 536870912 bytes
sending 'splashscreen' (270 KB)...
OKAY [ 0.192s]
writing 'splashscreen'...
OKAY [ 0.236s]
finished. total time: 0.431s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash token MFG_BOM_Full.bin
target reported max download size of 536870912 bytes
sending 'token' (3 KB)...
OKAY [ 0.194s]
writing 'token'...
OKAY [ 0.370s]
finished. total time: 0.566s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash ifwi ifwi-prod.bin
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 0.294s]
writing 'ifwi'...
OKAY [ 1.027s]
finished. total time: 1.326s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash boot boot_sign.bin
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.648s]
finished. total time: 1.182s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash recovery recovery_sign.bin
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.636s]
finished. total time: 1.163s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash fastboot droidboot_sign.bin
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.558s]
writing 'fastboot'...
OKAY [ 0.739s]
finished. total time: 1.302s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash APD APD.img
target reported max download size of 536870912 bytes
erasing 'APD'...
OKAY [ 0.204s]
sending 'APD' (183963 KB)...
OKAY [ 4.927s]
writing 'APD'...
OKAY [ 0.912s]
finished. total time: 6.049s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.233s]
sending sparse 'system' 1/5 (518551 KB)...
OKAY [ 27.274s]
writing 'system' 1/5...
OKAY [ 5.563s]
sending sparse 'system' 2/5 (523662 KB)...
OKAY [ 22.886s]
writing 'system' 2/5...
OKAY [ 6.964s]
sending sparse 'system' 3/5 (520607 KB)...
OKAY [ 24.630s]
writing 'system' 3/5...
OKAY [ 8.077s]
sending sparse 'system' 4/5 (500735 KB)...
OKAY [ 23.704s]
writing 'system' 4/5...
OKAY [ 7.983s]
sending sparse 'system' 5/5 (188368 KB)...
OKAY [ 8.849s]
writing 'system' 5/5...
OKAY [ 1.187s]
finished. total time: 137.827s
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>fastboot reboot
rebooting...
finished. total time: 0.126s

lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!

lemuelermita said:
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
Click to expand...
Click to collapse
hmm good to know device working again. strongly recommend you to perform a factory reset even device working perfectly.

problem flashing recovery

Hello people i hope someone can help me with a bit of a problem i have flashing twrp. I have done this many times in the past but i am having problems on this phone whn i try to flash recovery i am getting error below.
target reported max download size of 536870912 bytes
sending 'recovery' (11206 KB)...
OKAY [ 0.246s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.135s]
finished. total time: 0.387s
but iff i use command fastboot boot recovery.img it will boot into twrp no without problems.

sam00561 said:
Hello people i hope someone can help me with a bit of a problem i have flashing twrp. I have done this many times in the past but i am having problems on this phone whn i try to flash recovery i am getting error below.
target reported max download size of 536870912 bytes
sending 'recovery' (11206 KB)...
OKAY [ 0.246s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.135s]
finished. total time: 0.387s
but iff i use command fastboot boot recovery.img it will boot into twrp no without problems.
Click to expand...
Click to collapse
Ignore that error ... Don't boot in to system after flashing recovery instead boot to recovery first and then boot to system from twrp recovery
:good:
Hope this helps

jatinkhatri said:
Ignore that error ... Don't boot in to system after flashing recovery instead boot to recovery first and then boot to system from twrp recovery
:good:
Hope this helps
Click to expand...
Click to collapse
Cheers figured it out in the end