@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>
My m8 has an unlocked bootloader with s-on and i recently just used a nandroid backup which flashed the stock recovery and i updated to newest 5.0 update my phone was with t-mobile but it is factory unlocked now. Whenever I try to flash philz or twrp through fastboot it gives me:
target reported max download size of 1826414592 bytes
sending 'twrp' (16086 KB)...
OKAY [ 1.469s]
writing 'twrp'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.047s
How am i supposed to flash a custom recovery
Are you trying to do it in fastboot oem rebootRUU or just normal fastboot? You should be in the bootloader and just use fastboot flash recovery recovery.img
EddyOS said:
Are you trying to do it in fastboot oem rebootRUU or just normal fastboot? You should be in the bootloader and just use fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I tried both
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
Hi,
what i did so far was:
unlocked the bootloader
download the twrp recovery img (...ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/twrp-recovery-2.8.7.0-m8s-qlul/)
set phone on Fastboot USB
over the cmd bar (windows 10) i used fastboot and got this result:
C:\Android>fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
target reported max download size of 16510976 bytes
Invalid sparse file format at header magi
sending sparse 'recovery' 1/2 (15368 KB)...
OKAY [ 1.899s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.907s
I have no idea what i did wrong or how i can solve the problem. I just wanted run the twrp, use the Superuser. zip to have the rootet htc one m8s.
Thajin said:
Hi,
what i did so far was:
unlocked the bootloader
download the twrp recovery img (...ruu.lalleman.net/HTC_M8S%28QL_UL%29/Recovery/twrp-recovery-2.8.7.0-m8s-qlul/)
set phone on Fastboot USB
over the cmd bar (windows 10) i used fastboot and got this result:
C:\Android>fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img
target reported max download size of 16510976 bytes
Invalid sparse file format at header magi
sending sparse 'recovery' 1/2 (15368 KB)...
OKAY [ 1.899s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.907s
I have no idea what i did wrong or how i can solve the problem. I just wanted run the twrp, use the Superuser. zip to have the rootet htc one m8s.
Click to expand...
Click to collapse
Use HTC_fastboot and not the generic fastboot..
nopynel said:
Use HTC_fastboot and not the generic fastboot..
Click to expand...
Click to collapse
I have the same problem and just ask now because i am really confused about the hole stuff here.. Have we now to tipp in cmd
C:\Android>HTC_fastboot flash recovery twrp-2.8.7.0-m8s-qlul.img ??
Edit: Ok, i find HTC_Fastboot there > ruu.lalleman.net/HTC_M8S%28QL_UL%29/Tools/Fastboot/ and it solve this problem.
But i think its still not everything fine.. if i change to hboot on bootlader i get this infomations
fs5.directupload.net/images/160727/z9lr634u.jpg
whether unlock bootloader?
So, I'm trying to get TWRP installed so I can root my phone, but whenever I go to try and do the fastboot flah recovery recovery.img command, I get this:
C:\Users\darks_000\Downloads\platform-tools-latest-windows\platform-tools>fastbo
ot flash recovery recovery.img.img
target reported max download size of 536870912 bytes
sending 'recovery' (26498 KB)...
OKAY [ 0.766s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.781s
I'm not sure what to do?
MedievalFreakShow said:
So, I'm trying to get TWRP installed so I can root my phone, but whenever I go to try and do the fastboot flah recovery recovery.img command, I get this:
C:\Users\darks_000\Downloads\platform-tools-latest-windows\platform-tools>fastbo
ot flash recovery recovery.img.img
target reported max download size of 536870912 bytes
sending 'recovery' (26498 KB)...
OKAY [ 0.766s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.781s
I'm not sure what to do?
Click to expand...
Click to collapse
1. Make sure your device is unlocked.
2. Make sure fastboot is up to date.
3. That's not how you install twrp. It doesn't get flashed. You boot it temporarily and then use twrp to install itself into your current ramdisk.
4. You must also install a GSI afterwards or twrp will not work correctly. Twrp is not compatible with the stock OS because of some very hellish security Motorola has in place.
5. If you have a Verizon, Cricket, or At&t branded G7 Play, none of the above is possible. If you bought an unlocked or retail model and simply use one of them as a carrier though, it is possible.
Spaceminer said:
1. Make sure your device is unlocked.
2. Make sure fastboot is up to date.
3. That's not how you install twrp. It doesn't get flashed. You boot it temporarily and then use twrp to install itself into your current ramdisk.
4. You must also install a GSI afterwards or twrp will not work correctly. Twrp is not compatible with the stock OS because of some very hellish security Motorola has in place.
5. If you have a Verizon, Cricket, or At&t branded G7 Play, none of the above is possible. If you bought an unlocked or retail model and simply use one of them as a carrier though, it is possible.
Click to expand...
Click to collapse
Device is unlocked. Bootloader is also unlocked. As for fast boot im not sure how to update it. Unless it updates with the system updates. Ive not done them for fear of upgrading the software and then not being able to put twrp on or root it.