So I was on koush IRC channel asking somneone to try and compile a recovery and voila "jcase" agreed to do it if I could procure some reliable testers!
I can't do it as I am in South Africa on vacation and havent rooted my phone but please help you coud help in a huge way and ake a change for development on our devices!
All you have to do is head over to the IRC channel #koush and say "primo" and then jcase will ask you all that he needs!
EDIT: Post result of this!
adb shell cat /proc/emmc
adb shell cat /proc/partitions
FAST HE TOLD ME HE ISN'T GOING TO BE THERE FOR LONG
EDIT2: Post output in thread only because he has gone from IRC and I have to contact him elsewhere.
I'm currently in the process of compiling it aswell, we will have to wait some time for beta testers as very few people have the device (very new)
I have all details as attached:
mount
cat proc/emmc
cat /proc/partitions
ls -l /dev/block
Bump
Sent from my HTC One V using Tapatalk 2
Anyone managed to get successfull compilation of CWM recovery?
handryg555 said:
Anyone managed to get successfull compilation of CWM recovery?
Click to expand...
Click to collapse
No..
Sent from my HTC One V using XDA
i have the phone and i want try the recovery but im not that professional , so tell me how to do it simply and i'll try
Whenever I try to create the device tree I get error message 'unpackbootimg not found is you android environment setup?'. Any suggestions?
Sent from my Desire S
mmmcfc said:
Whenever I try to create the device tree I get error message 'unpackbootimg not found is you android environment setup?'. Any suggestions?
Sent from my Desire S
Click to expand...
Click to collapse
Even madmaxx82 told me that he would have to change his entire build environment as the One series was different from others...
Sent from my HTC One V using XDA
shubhamchamaria said:
Even madmaxx82 told me that he would have to change his entire build environment as the One series was different from others...
Sent from my HTC One V using XDA
Click to expand...
Click to collapse
I think I've got past that problem now . In school now .. will do next step later
Sent from my Desire S using xda premium
mmmcfc said:
I think I've got past that problem now . In school now .. will do next step later
Sent from my Desire S using xda premium
Click to expand...
Click to collapse
Thanks...
Sent from my HTC One V using XDA
emmc and partitions
Here's my output from my One V.
I have it rooted according to the steps described in the General post.
cat /proc/emmc
dev: size erasesize name
mmcblk0p17: 00040000 00000200 "misc"
mmcblk0p21: 0087f400 00000200 "recovery"
mmcblk0p22: 00400000 00000200 "boot"
mmcblk0p25: 31dffe00 00000200 "system"
mmcblk0p28: 0afffe00 00000200 "cache"
mmcblk0p26: 3cfffe00 00000200 "userdata"
mmcblk0p29: 017ade00 00000200 "devlog"
mmcblk0p31: 00040000 00000200 "pdata"
mmcblk0p30: 00011c00 00000200 "extra"
mmcblk0p32: 05ffe000 00000200 "fat"
mmcblk0p27: 07fffe00 00000200 "swap"
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
7 1 10427 loop1
179 0 2396160 mmcblk0
179 1 500 mmcblk0p1
179 2 64 mmcblk0p2
179 3 4500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 30000 mmcblk0p5
179 6 12500 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 8751 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 8957 mmcblk0p16
179 17 256 mmcblk0p17
179 18 1024 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1280 mmcblk0p20
179 21 8701 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 256 mmcblk0p23
179 24 2047 mmcblk0p24
179 25 817151 mmcblk0p25
179 26 999423 mmcblk0p26
179 27 131071 mmcblk0p27
179 28 180223 mmcblk0p28
179 29 24247 mmcblk0p29
179 30 71 mmcblk0p30
179 31 256 mmcblk0p31
179 32 98296 mmcblk0p32
179 64 7772160 mmcblk1
179 65 6715392 mmcblk1p1
179 66 1048576 mmcblk1p2
254 0 2110 dm-0
254 1 10426 dm-1
Good luck with the CWM-building
shubhamchamaria said:
Thanks...
Sent from my HTC One V using XDA
Click to expand...
Click to collapse
Unfortunately my laptops hard drive crashed while I was compiling the recovery. As a result I am without a laptop at the moment. I would very grateful towards anyone who donates towards replacing the hard drive. If anyone wants to help just click here
Hi,
I will try to build the recovery for this device.But need testers.I have successfully build touch based CWM for Optimus Me and Optimus One.This is my first time working with HTC device.I have downloaded the boot.img from TITTANIUM KERNEL .I hope that kernel is working on your devices.
I need to know how to flash the recovery to this device.is Root available for this device??
Yes:
[TUT] How to Unlock Bootloader and Root your Htc One V
I have compiled CWM for this device(recovery.img) .it is about 4.7 MB size.is it supported?
How is this flashed ?
Through fastboot?
hey one v owners. Im looking to get one v official support from koush for CWM. All I need is a tester for the recovery. I built it from source. So that way koush will support it.
Just flash like you would any recovery. I need any tester to go to mounting and mount every partition. Then flash a rom, backup a rom, and restore a rom without rebooting. Then connect phone to computer and run "adb pull /tmp/recovery.log" and post that here. If everything looks good I will submit to koush for official rom manager support and future updates from him.
For testing I would suggest running the command fastboot boot recovery.img
http://tinyw.in/2DqY
Yet another WFS user shows up on the One V forum. Welcome, JMZ! Give me a little time and I'll see if I can't get through your list and give some feedback.
CafeKampuchia said:
Yet another WFS user shows up on the One V forum. Welcome, JMZ! Give me a little time and I'll see if I can't get through your list and give some feedback.
Click to expand...
Click to collapse
Well I don't have device. Just heard this device needs some love. And I'm bored with the ones I have.
Sent from my PG86100 using xda premium
Can't flash it.
Code:
FAILED (remote: image error! (BootMagic check fail))
My bad. The download was corrupt. Reflashing in a bit.
Related
Hi!
Today i got my LG P970 Optimus Black. But unfortunately there is not yet a ClockworkRecovery Image or any custom Roms availible. So i decived to build Clockworksmod myself. Now i got a little Problem on setting up the recovery.fstab.
cat /proc/partitions shows the following:
Code:
179 0 1912832 mmcblk0
179 1 128 mmcblk0p1
179 2 512 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 660480 mmcblk0p8 <-- System
179 9 1161088 mmcblk0p9 <-- Data
179 10 65536 mmcblk0p10 <-- Cache
179 11 128 mmcblk0p11
179 12 128 mmcblk0p12
179 16 1955840 mmcblk1 <-- SD-Card
So now my Question is how can i find out, which Partitions are the Recovery and Boot? And what are all the other ones?
I tried the mkvendor.sh Script on all Dumps i didn´t know what they are. The only ones the Script runs through without any errors are mmcblk0p3 & mmcblk0p4.
It seems nobody is interested in developing this phone
hi there,sry for my poor English
can anybody tell me where does hboot locate on? i cant google it
thank u for your help
major minor #blocks name
31 0 1024 mtdblock0
31 1 4608 mtdblock1
31 2 3328 mtdblock2
31 3 184320 mtdblock3
31 4 5120 mtdblock4
31 5 261888 mtdblock5
179 0 984064 mmcblk0
179 1 719872 mmcblk0p1
179 2 263168 mmcblk0p2
i am sure mmcblk0 is sdcard and mmcblk0p1 is the partition1 mmcblk0p2 is partition2
and mtdblock5 is "data" mtdblock4 is "cache",mtdblock3 is "system"
my question is what is mtdblock0,1,2
hboot?first screen?something else?
i guess is
mtdblock0=hboot ,the other partition is recovery and first screen ,and they are more than 2m,and hboot is less than 1m,so i 90% sure this is hboot
and
mtdblock1 is recovery ,i remember the default recovery partition is about 5m,60% sure
mtdblock2 is first screen
can somebody tell me is that right?
Hi guys I got Xperia T3 D5102 few days back.
I rooted it & deodexed rom & now making few mods.
I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot.
Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone.
Also I tried to go the hardware way by trying key combinations in many ways
Power + Volume up/down doesn't work
Power + Volume both btns also didn't work.
Also tried using ADB commands for Advance power menu . But no luck then too.
I suspect there is no recovery partition and hence didn't boot.
The below table shows the partition table
Code:
Number Start End Size File system Name F
1 131kB 2228kB 2097kB TA
2 2228kB 2753kB 524kB sbl1
3 2753kB 3015kB 262kB s1sbl
4 3015kB 3080kB 65.5kB dbi
5 3080kB 3604kB 524kB aboot
6 3604kB 4129kB 524kB rpm
7 4129kB 4653kB 524kB tz
8 4653kB 5177kB 524kB alt_sbl1
9 5177kB 5439kB 262kB alt_s1sbl
10 5439kB 5505kB 65.5kB alt_dbi
11 5505kB 6029kB 524kB alt_aboot
12 6029kB 6554kB 524kB alt_rpm
13 6554kB 7078kB 524kB alt_tz
14 8389kB 9961kB 1573kB fsg
15 12.6MB 14.2MB 1573kB modemst1
16 16.8MB 18.4MB 1573kB modemst2
17 21.0MB 37.7MB 16.8MB ext4 persist
18 37.7MB 105MB 67.1MB fat16 modem
19 105MB 126MB 21.0MB boot
20 126MB 136MB 10.5MB fat32 ramdump
21 136MB 153MB 16.8MB FOTAKernel
22 153MB 153MB 32.8kB DDR
23 153MB 170MB 16.8MB ext4 LTALabel
24 172MB 180MB 8389kB apps_log
25 180MB 2248MB 2068MB ext4 system
26 2248MB 2458MB 210MB ext4 cache
27 2458MB 7818MB 5360MB ext4 userdata
(parted)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 64 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 256 mmcblk0p9
179 10 64 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 2019328 mmcblk0p25
179 26 204800 mmcblk0p26
179 27 5234671 mmcblk0p27
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ $
Need help from developers /modders on how to proceed further and lemme know some hint to proceed.
I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone.
Request someone to throw light on this !
Thanks
Hello, just a question : how did you root your T3 ? are you allways on .14 ?
dan15 said:
Hello, just a question : how did you root your T3 ? are you allways on .14 ?
Click to expand...
Click to collapse
Yes my Android version is 4.4.2 build version is 18.2.A.1.14
ok, as my D5103 is ugrade to .17, i have to wait for a solution, if i don't want to downgrade, but i'm not sure that the rot will stay if i upgrade after root on .14...
Xperia devices don't have a recovery partition. Neither do they have any stock recovery.
AJ
Abhinav2 said:
Xperia devices don't have a recovery partition. Neither do they have any stock recovery.
AJ
Click to expand...
Click to collapse
You wrong, only a few xperia devices does NOT have a recovery partition, all others have it
CreasingMass Dev said:
You wrong, only a few xperia devices does NOT have a recovery partition, all others have it
Click to expand...
Click to collapse
None of them has AFAIK. Can u give some example of device which might have? Because recovery is basically flashed in FOTA partition
AJ
Al parecer no existe recovery
Xenon1978 said:
Hi guys I got Xperia T3 D5102 few days back.
I rooted it & deodexed rom & now making few mods.
I tried making advance reboot Mod with restart options to recovery, system restart & soft reboot.
Reboot & soft reboot option is working fine but reboot to Recovery is not working. It ends up in just normal reboot of phone.
Also I tried to go the hardware way by trying key combinations in many ways
Power + Volume up/down doesn't work
Power + Volume both btns also didn't work.
Also tried using ADB commands for Advance power menu . But no luck then too.
I suspect there is no recovery partition and hence didn't boot.
The below table shows the partition table
Code:
Number Start End Size File system Name F
1 131kB 2228kB 2097kB TA
2 2228kB 2753kB 524kB sbl1
3 2753kB 3015kB 262kB s1sbl
4 3015kB 3080kB 65.5kB dbi
5 3080kB 3604kB 524kB aboot
6 3604kB 4129kB 524kB rpm
7 4129kB 4653kB 524kB tz
8 4653kB 5177kB 524kB alt_sbl1
9 5177kB 5439kB 262kB alt_s1sbl
10 5439kB 5505kB 65.5kB alt_dbi
11 5505kB 6029kB 524kB alt_aboot
12 6029kB 6554kB 524kB alt_rpm
13 6554kB 7078kB 524kB alt_tz
14 8389kB 9961kB 1573kB fsg
15 12.6MB 14.2MB 1573kB modemst1
16 16.8MB 18.4MB 1573kB modemst2
17 21.0MB 37.7MB 16.8MB ext4 persist
18 37.7MB 105MB 67.1MB fat16 modem
19 105MB 126MB 21.0MB boot
20 126MB 136MB 10.5MB fat32 ramdump
21 136MB 153MB 16.8MB FOTAKernel
22 153MB 153MB 32.8kB DDR
23 153MB 170MB 16.8MB ext4 LTALabel
24 172MB 180MB 8389kB apps_log
25 180MB 2248MB 2068MB ext4 system
26 2248MB 2458MB 210MB ext4 cache
27 2458MB 7818MB 5360MB ext4 userdata
(parted)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 64 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 256 mmcblk0p9
179 10 64 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 16384 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 20480 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 32 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 8192 mmcblk0p24
179 25 2019328 mmcblk0p25
179 26 204800 mmcblk0p26
179 27 5234671 mmcblk0p27
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ $
Need help from developers /modders on how to proceed further and lemme know some hint to proceed.
I suspect recovery partition missing. Anyone can confirm the same ? The above table would give a clear layout of the memory partitions of the phone.
Request someone to throw light on this !
Thanks
Click to expand...
Click to collapse
No se si alguno de ustedes o tengo instalar un gestor de recuperación (Recovery) anteriormente a este modelo
Ahora he intentado hacerlo y puff.. el paquete ABD me dice que no EXISTE
Code:
FAILED <remote: Recovery partición doesn't founded>
Hi guys
I have a best method for Nokia x liquid smooth lollipop developers for flashing this ROM without DAT.
________________________
System folder of this rom is compressed into DAT file.....developers easily extract system folder but sometimes they face some errors for Compressing To DAT.
For fix these errors.I build a updater-script for flahing this ROM like a kitkat roms flashing method.
so let's start for the hack
for accept this method you have to download the script from the given link....
you only want
Meta-Inf folder (go to the given link)
Boot.IMG
System folder (not DAT)
file_contexts
compress these files into zip and flash the ROM
that's it you flashed liquid lollipop without having DAT
remember
this script is only use for liquid smooth lollipop ROM by Ahmed hady
please press the thanks button
thank you
Link
http://www74.zippyshare.com/v/EhmIGNdK/file.html
Has the ril bug fixed?
we are truing to fix......by this updater-script I don't waste my time to compress system folder to DAT
Thanks Man ,,,
you welcome
hope you fix the ril soon , goodluck
okay
l.k said:
okay
Click to expand...
Click to collapse
Hey bro do you have knowledge of partitions of nokia x if yes then please explain
Share information about partitions I.e, which is boot partition,system partition etc
Here is my nokia x partitions list
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 20 mmcblk0p1
179 2 250 mmcblk0p2
179 3 51200 mmcblk0p3
179 4 1 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 3072 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 768 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 13576 mmcblk0p14
179 15 10240 mmcblk0p15
179 16 10240 mmcblk0p16
179 17 13576 mmcblk0p17
179 18 471040 mmcblk0p18
179 19 102400 mmcblk0p19
179 20 20 mmcblk0p20
179 21 1228800 mmcblk0p21
179 22 1370112 mmcblk0p22
179 23 40960 mmcblk0p23
179 24 10240 mmcblk0p24
179 25 399360 mmcblk0p25
179 26 59099 mmcblk0p26
179 32 15558144 mmcblk1
179 33 15554048 mmcblk1p1
253 0 102400 zram0
[email protected]:/ $
I don't know about that
Nokia X/XL Partitions
matrixex said:
Hey bro do you have knowledge of partitions of nokia x if yes then please explain
Share information about partitions I.e, which is boot partition,system partition etc
Click to expand...
Click to collapse
Bootloader 179 3 51200 mmcblk0p3
Persist 179 16 10240 mmcblk0p16
Boot 179 17 13576 mmcblk0p17
System 179 18 573440 mmcblk0p18
Cache 179 19 102400 mmcblk0p19
Storage 179 21 1172480 mmcblk0p21
Data 179 22 1267712 mmcblk0p22
YSH ALSAGER said:
Bootloader 179 3 51200 mmcblk0p3
Persist 179 16 10240 mmcblk0p16
Boot 179 17 13576 mmcblk0p17
System 179 18 573440 mmcblk0p18
Cache 179 19 102400 mmcblk0p19
Storage 179 21 1172480 mmcblk0p21
Data 179 22 1267712 mmcblk0p22
Click to expand...
Click to collapse
Thanks
I was searching for it
Well please also explain how did you find it
I'm working on cm13 compiled by thinhx2
ROM have a script error.....some symlink failed status 7....trying to fix it...
matrixex said:
Thanks
I was searching for it
Well please also explain how did you find it
Click to expand...
Click to collapse
Using Parition app
I've tried many times to fix the ril problem, but I can not. is there any other way to fix this problem ?
the rom using huawei device tree and the rom only for single rom bro,,,
we want twrp 3.0.0 for flashing cm13.....inches twrp 2.8.7.0 gave me error
some symlinks failed......
l.k said:
we want twrp 3.0.0 for flashing cm13.....inches twrp 2.8.7.0 gave me error
some symlinks failed......
Click to expand...
Click to collapse
That happens with me too I have created Nokia x stock rom after symlinking I have flashed it ,TWRP error displays "some symlink failed"
yeah as well as twrp 3.0.0 also isn't working
your rom file is not match with your sript,,
no twrp recovery isn't have complete symlinks which r used in cm13's script
hi so im using adb shell and i'd like to take a closer peek at the init files. i was pointed in the direction of downloading my bootloader first. i have since used adb shell command cat /proc/partitions and this was displayed:
major minor #blocks name
7 0 98304 loop0
179 0 30535680 mmcblk0
179 1 19456 mmcblk0p1
179 2 66464 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 64 mmcblk0p5
179 6 32 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 6144 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 14336 mmcblk0p13
179 14 4096 mmcblk0p14
179 15 4096 mmcblk0p15
179 16 4 mmcblk0p16
179 17 17408 mmcblk0p17
179 18 19456 mmcblk0p18
179 19 4084 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 8 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 9216 mmcblk0p23
179 24 3891200 mmcblk0p24
179 25 512000 mmcblk0p25
179 26 40960 mmcblk0p26
179 27 25894892 mmcblk0p27
253 0 1572864 vnswap0
179 32 4096 mmcblk0rpmb
179 64 124868096 mmcblk1
179 65 124851712 mmcblk1p1
[email protected]:/ #
which one of these contains the bootloader or how do i download the correct partition?