Database Develop

con247's Automatic Kernel Installation for S-ON Unlocked Devices (Rezound Dev Forum)

Automatic Kernel Installation for S-ON Unlocked Devices
http://forum.xda-developers.com/showthread.php?t=1419587
Currently testing this out to see if it is compatible, has anyone had any luck. Its been on the xda front page for about a day
Modifying for Vivid Usage

Just letting you know we do have some batch file (automatic) kernel flashers. Better yet, we have a working kernel/recovery flasher that does it from an android app so it is computer (windows/mac/etc) independent. It even finds the kernel image in a Rom zip. That'd be great if you want to port it, but I don't want you to feel like you wasted your time.
Sent from my HTC PH39100 using xda premium

slapshot30 said:
Just letting you know we do have some batch file (automatic) kernel flashers. Better yet, we have a working kernel/recovery flasher that does it from an android app so it is computer (windows/mac/etc) independent. It even finds the kernel image in a Rom zip. That'd be great if you want to port it, but I don't want you to feel like you wasted your time.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
My way is better. doesn't require fastboot/adb to be working or installed. I can port it if you get me the mount points for /sdcard while in recovery and /boot
This can be done by going into recovery, mounting the sd card, and typing "df" into adb shell.
Then to get the boot mount point, type "cat /proc/emmc" in adb shell while in Sense. Both commands are without quotes. Just PM me the copy and pasted output and I will whip up a port in a few minutes.

con247 said:
My way is better. doesn't require fastboot/adb to be working or installed. I can port it if you get me the mount points for /sdcard while in recovery and /boot
This can be done by going into recovery, mounting the sd card, and typing "df" into adb shell.
Then to get the boot mount point, type "cat /proc/emmc" in adb shell while in Sense. Both commands are without quotes. Just PM me the copy and pasted output and I will whip up a port in a few minutes.
Click to expand...
Click to collapse
That would be awesome. I'm still at work but ill forward you a copy as quick as I can
Sent from my HTC PH39100 using xda premium

mmcblk0p24: 00fff600 00000200 "misc"
mmcblk0p23: 00fffc00 00000200 "recovery"
mmcblk0p22: 01000000 00000200 "boot"
mmcblk0p29: 3ffffe00 00000200 "system"
mmcblk0p35: 11fffe00 00000200 "cache"
mmcblk0p34: fffffe00 00000200 "userdata"
mmcblk0p30: 01fba600 00000200 "devlog"
mmcblk0p32: 00040000 00000200 "pdata"
mmcblk0p17: 02800000 00000200 "radio"
mmcblk0p21: 02000000 00000200 "adsp"
mmcblk0p19: 007ffc00 00000200 "radio_config"
mmcblk0p25: 00400000 00000200 "modem_st1"
mmcblk0p26: 00400000 00000200 "modem_st2"
mmcblk0p18: 02800000 00000200 "mdm9k"
mmcblk0p20: 007ffa00 00000200 "mdm9k_config"
mmcblk0p27: 00400000 00000200 "mdm_efs1"
mmcblk0p28: 00400000 00000200 "mdm_efs2"

con247 said:
My way is better. doesn't require fastboot/adb to be working or installed. I can port it if you get me the mount points for /sdcard while in recovery and /boot
This can be done by going into recovery, mounting the sd card, and typing "df" into adb shell.
Then to get the boot mount point, type "cat /proc/emmc" in adb shell while in Sense. Both commands are without quotes. Just PM me the copy and pasted output and I will whip up a port in a few minutes.
Click to expand...
Click to collapse
Gotcha, nice work. The more tools we can get, the better.

Well, I got it done (I think). You didn't get me the sd card mount point I needed, but I am assuming it is the same. The instructions are the same as those for the rezound.
I can't test it, so if it doesn't work, then it just won't work. The only issue that is possible is the sd card mount is wrong. If the script doesn't work, it DOESN'T pose a danger to your phone.
YOU HAVE TO SWAP OUT THE ZIMAGE IN THE FOLDER THOUGH, AS THERE IS A REZOUND KERNEL IN THERE. Worst thing that could happen with this is a bootloop and you would need to reflash your boot image with a backup or something.

[SOLVED] Soft bricked my HTC One M7, ADB not working

Hi there,
So I was installing CM10.2 on my HTC One (GSM) m7ul this evening when suddenly everything went wrong.
- I copied the CM .zip and GAPPS .zip to the internal storage using windows (7) file explorer;
- I installed the CM boot.img via fastboot flash boot boot.img;
- I rebooted into recovery mode (twrp 2.6.3.0);
- wiped cache and dalvik cache;
- Tried to find the installation.zip;
No zip files found. Actually, twrp did not find any file and could not mount f.i. system, cache, sdcard, etc
I tried using another bootloader (clockwork touch 6.0.4.3), but has the same issues as twrp.
ADB is not working as my phone was not in developer mode when I started to install CM10.2. Rebooting my phone is not working also because I replaced the boot.img via fastboot. I cannot reach my backup via twrp (on phone and PC).
Do you have tips for me to get my phone to work properly again?

basv81 said:
So I was installing CM10.2 this evening when suddenly everything went wrong.
- I copied the CM .zip and GAPPS .zip to the internal storage using windows (7) file explorer;
- I installed the CM boot.img via fastboot flash boot boot.img;
- I rebooted into recovery mode (twrp 2.6.3.0);
- wiped cache and dalvik cache;
- Tried to find the installation.zip;
No zip files found. Actually, twrp did not find any file and could not mount f.i. system, cache, sdcard, etc
I tried using another bootloader (clockwork touch 6.0.4.3), but has the same issues as twrp.
ADB is not working as my phone was not in developer mode when I started to install CM10.2. Rebooting my phone is not working also because I replaced the boot.img via fastboot. I cannot reach my backup via twrp (on phone and PC).
Do you have tips for me to get my phone to work properly again?
Click to expand...
Click to collapse
Mate you made a bad move flashing the boot.img file before installing the .zip. Always install the zip first then flash the boot.img and after clear cache. And make sure the zip is at the root of your sdcard in twrp before proceeding to anything!
I tried using another bootloader (clockwork touch 6.0.4.3)
Click to expand...
Click to collapse
You mean ''I tried another RECOVERY''
Rebooting my phone is not working also because I replaced the boot.img via fastboot
Click to expand...
Click to collapse
try holding power + Vol down and reboot in bootloader
Nowt that you are in bootloader, select fastboot and connect usb cable, navigate to your adb/fastboot folder of your computer and start a cmd prompt from there.
you can flash twrp again as your recovery
Code:
fastboot flash recovery <name-of-recovery>.img
reboot into bootloader
Code:
fastboot reboot bootloader
then go in recovery (adb is supported inside twrp).
push your zip files to your phone
Code:
adb push <name_of_rom>.zip /sdcard/
adb push <name_of_gapps>.zip /sdcard/
- install the zip of your cm rom first via twrp ---> select ''install'' and then navigate to /sdcard/ and select your zip.
- reboot phone in bootloader ---> select reboot from twrp main menu, after select bootloader.
- when in bootloader select fastboot
flash your kernel:
Code:
fastboot flash boot boot.img
after go back in twrp recovery and install you gapps.zip and after clear cache and dalvik cache then reboot normally.

Thanks for your reply.
alray said:
Mate you made a bad move flashing the boot.img file before installing the .zip. Always install the zip first then flash the boot.img and after clear cache. And make sure the zip is at the root of your sdcard in twrp before proceeding to anything!
You mean ''I tried another RECOVERY''
Click to expand...
Click to collapse
:good:
try holding power + Vol down and reboot in bootloader
Nowt that you are in bootloader, select fastboot and connect usb cable, navigate to your adb/fastboot folder of your computer and start a cmd prompt from there.
you can flash twrp again as your recovery
Code:
fastboot flash recovery <name-of-recovery>.img
reboot into bootloader
Code:
fastboot reboot bootloader
then go in recovery (adb is supported inside twrp).
Click to expand...
Click to collapse
Done all that. ADB sideload option tells me it cannot mount /sdcard, /data, /system.
push your zip files to your phone
Code:
adb push <name_of_rom>.zip /sdcard/
adb push <name_of_gapps>.zip /sdcard/
Click to expand...
Click to collapse
ADB cannot find the device.
- install the zip of your cm rom first via twrp ---> select ''install'' and then navigate to /sdcard/ and select your zip.
Click to expand...
Click to collapse
twrp and cwmod can't see any files (although I allready put the zip files in the root directory of the device)
- reboot phone in bootloader ---> select reboot from twrp main menu, after select bootloader.
- when in bootloader select fastboot
flash your kernel:
Code:
fastboot flash boot boot.img
after go back in twrp recovery and install you gapps.zip and after clear cache and dalvik cache then reboot normally.
Click to expand...
Click to collapse
I think the data on my device somehow got corrupt.

./

Stolpert said:
I assume you've got the correct drivers installed, you should be able to use ADB in recovery, at least in cwm but I guess also in twrp. Try and install HTC Sync manager for all the drivers, go back in recovery and type:
Code:
adb devices
If it's there you can follow the guide above.
Click to expand...
Click to collapse
Most recent drivers installed. I only don't get any serial numbers on my screen (only "List of devices attached" and below is empty). Not sure whether I get te "error: device not found" message with that command.

basv81 said:
Thanks for your reply.
:good:
Done all that. ADB sideload option tells me it cannot mount /sdcard, /data, /system.
ADB cannot find the device.
twrp and cwmod can't see any files (although I allready put the zip files in the root directory of the device)
I think the data on my device somehow got corrupt.
Click to expand...
Click to collapse
to check you're /data partition, reboot to recovery then:
adb devices -> to make sure it's connected, if OK proceed with below:
adb shell
~ # umount /data
umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
and see if it reports errors or not. (copy/paste your command prompt)

nkk71 said:
to check you're /data partition, reboot to recovery then:
adb devices -> to make sure it's connected, if OK proceed with below:
adb shell
~ # umount /data
umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
and see if it reports errors or not. (copy/paste your command prompt)
Click to expand...
Click to collapse
I'll do that tonight (that's within 12 hrs).

alray said:
you can flash twrp again as your recovery
Code:
fastboot flash recovery <name-of-recovery>.img
reboot into bootloader
Code:
fastboot reboot bootloader
then go in recovery (adb is supported inside twrp).
Click to expand...
Click to collapse
basv81 said:
Thanks for your reply.
Done all that. ADB sideload option tells me it cannot mount /sdcard, /data, /system.
Click to expand...
Click to collapse
ADB tells you that? You are using the fastboot commands? ADB cannot communicate with fastboot and shouldn't tell you anything.

basv81 said:
I'll do that tonight (that's within 12 hrs).
Click to expand...
Click to collapse
We're one hour apart, so hopefully I'll check in on you tonight

Stolper said:
ADB tells you that? You are using the fastboot commands? ADB cannot communicate with fastboot and shouldn't tell you anything.
Click to expand...
Click to collapse
fastboot commands work perfectly within fastboot, but adb does not as the ADB sideload options in twrp and cw fail.

Are you using a Sprint Htc one? (M7WLS) If yes you need a different version of twrp. Go back in fastboot and type "fasboot getvat all" and copy paste info here (remove imei and s/n)
Sent from my HTC One using xda app-developers app

alray said:
Are you using a Sprint Htc one? (M7WLS) If yes you need a different version of twrp. Go back in fastboot and type "fasboot getvat all" and copy paste info here (remove imei and s/n)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No, I'm using a HTC One (GSM) m7ul
I'll post the info tonight.

I had the same crap happen on SPRINT HTC One. All I ended up doing in the end was booting to bootloader and derp- I mean, uh, running a stock RUU. Repartitioned all the partitions.
Sent from my HTC One using XDA Premium 4 mobile app

nkk71 said:
to check you're /data partition, reboot to recovery then:
adb devices -> to make sure it's connected, if OK proceed with below:
adb shell
~ # umount /data
umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
and see if it reports errors or not. (copy/paste your command prompt)
Click to expand...
Click to collapse
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT35CW***** recovery
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
~ # ←[6numount /data
umount /data
umount: can't umount /data: Invalid argument
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n

alray said:
Are you using a Sprint Htc one? (M7WLS) If yes you need a different version of twrp. Go back in fastboot and type "fasboot getvat all" and copy paste info here (remove imei and s/n)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **********
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

basv81 said:
nkk71 said:
Hi basv81,
If "e2fsck -n -v -f /dev/block/mmcblk0p37" returns an error, send me a PM so it get's my attention to check your thread, before proceeding. Another guy turned out to have this and we were able to fix it, coincidentally he was from the Netherlands too.
I'll probably be here till 10~11pm your time.
Click to expand...
Click to collapse
Hi nkk71,
I get the following results:
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT35xxxxxxxxxxxxx recovery
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
~ # ←[6numount /data
umount /data
umount: can't umount /data: Invalid argument
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n
I think I can be pretty sure the file system is corrupt :crying:
Click to expand...
Click to collapse
oh man, it's pretty late. can we pick this up anytime tomorrow or over the weekend? i need to get some sleep, and yeah looks like a corrupt partition. sorry man, i hate to be the bad guy
check into this: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
first thing you need to make sure of, is "cat /proc/emmc" to make sure we're looking at the right partition.
I can't do this tonight, but you might wanna check: http://forum.xda-developers.com/showthread.php?t=2504542
page 8 or 9 and onwards.
sorry man, but too late for me, i need to get some sleep before work tomorrow

nkk71 said:
oh man, it's pretty late. can we pick this up anytime tomorrow or over the weekend? i need to get some sleep, and yeah looks like a corrupt partition. sorry man, i hate to be the bad guy
check into this: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
first thing you need to make sure of, is "cat /proc/emmc" to make sure we're looking at the right partition.
I can't do this tonight, but you might wanna check: http://forum.xda-developers.com/showthread.php?t=2504542
page 8 or 9 and onwards.
sorry man, but too late for me, i need to get some sleep before work tomorrow
Click to expand...
Click to collapse
No problem I have to go to sleep too because of the same.
cat /proc/emmc responds as follows:
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ←[6ncat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata" <<----------
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
I don't dare to format the partition yet (http://forum.xda-developers.com/showthread.php?t=2504542&page=9&p=47046727 and onwards). I'm online in the vicinity of my phone again tomorrow night after 8/9PM CET and Thursday night. After that it will be after the weekend.

basv81 said:
No problem I have to go to sleep too because of the same.
cat /proc/emmc responds as follows:
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ←[6ncat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata" <<----------
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
I don't dare to format the partition yet (http://forum.xda-developers.com/showthread.php?t=2504542&page=9&p=47046727 and onwards). I'm online in the vicinity of my phone again tomorrow night after 8/9PM CET and Thursday night. After that it will be after the weekend.
Click to expand...
Click to collapse
Anyway back to your thread, so /data isn't mounting, even if encrypted it should mount, but not be readable.
Here's what I'd like you to do, reboot to recovery, then:
adb shell
# e2fsck -v -f /dev/block/mmcblk0p37
and let's see if it ask for repair of any kind

alray said:
push your zip files to your phone
Code:
adb push <name_of_rom>.zip /sdcard/
adb push <name_of_gapps>.zip /sdcard/
- install the zip of your cm rom first via twrp ---> select ''install'' and then navigate to /sdcard/ and select your zip.
- reboot phone in bootloader ---> select reboot from twrp main menu, after select bootloader.
- when in bootloader select fastboot
flash your kernel:
Click to expand...
Click to collapse
This first part is working by the way: adb push worked when I used another USB port on my PC. I can see the two zip files I pushed, but cannot install them.

nkk71 said:
Anyway back to your thread, so /data isn't mounting, even if encrypted it should mount, but not be readable.
Here's what I'd like you to do, reboot to recovery, then:
adb shell
# e2fsck -v -f /dev/block/mmcblk0p37
and let's see if it ask for repair of any kind
Click to expand...
Click to collapse
Code:
~ # ←[6ne2fsck -v -f /dev/block/mmcblk0p37
e2fsck -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
I think I know what happened: I got my work e-mail on the phone, so the storage is encrypted. That's probably the reason that I don't see any files in there. Only problem is that I can't boot the phone to undo the encryption.

[TOOL][WIP/RECOVERY]TWRP 2.7.0.x[OFFMODE CHARGING FIX]

This is a WIP(work in progress)..built from latest source(maintained)..this is untested since none of you wants to help..used the latest OTA images for some parts of the recovery(built it with dependency mode)
Grab the image here
for both S-ON and S-OFF:
- Grab the recovery image..
- Setup Fastboot tools and drivers..
- Reboot phone to Bootloader mode(pressing Volume down while powering it on and pressing on Bootloader option)
- Run command prompt on your fastboot directory by Holding Shift(keyboard) and pressing right click on your mouse..choose open command window here..
- Issue commands:
Code:
fastboot erase cache
- Then after finishing the previous command..
Code:
fastboot flash recovery [COLOR="Red"][I]image.image[/I][/COLOR]
note: where image.image is the filename of the recovery image you have downloaded..
- Reboot bootloader and try to enter recovery..and give yourself a HUG..if all goes well you will be greeted by the Teamwin screen and will enter the menu shortly..
Kindly test and give feedback.. if you like it a Thanks cannot be as harmful as it seems..it will keep me motivated to work things out for FREE..
Credits:
DeesTroy(TWRP), Flyhalf205(device tree), Omni git, tropical_cactus(tester), moonchy(tester), migascalp(tester) and to those who donated my biggest Thanks!!
XDA:DevDB Information
TWRP for Butterfly S, Tool/Utility for the HTC Butterfly S
Contributors
kairi_zeroblade
Version Information
Status: Testing
Created 2014-10-18
Last Updated 2014-10-18

Installed on my 901S and it does not work. Wanting to get into recovery the phone will restart.:crying:
We hope you manage to fix the problem charging the phone is off.
For the moment, thanks!

fiorello said:
Installed on my 901S and it does not work. Wanting to get into recovery the phone will restart.:crying:
We hope you manage to fix the problem charging the phone is off.
For the moment, thanks!
Click to expand...
Click to collapse
they removed the offmode charging on kitkat..even on the HTC One,,if you want offmode charging downgrade your bootloader..can you dump me a last_kmsg and a recovery log from /cache/recovery.log or sumthin..
edit:
here's a new image..can you try this??this is still using your own stock recovery image..dl here

kairi_zeroblade said:
they removed the offmode charging on kitkat..even on the HTC One,,if you want offmode charging downgrade your bootloader..can you dump me a last_kmsg and a recovery log from /cache/recovery.log or sumthin..
edit:
here's a new image..can you try this??this is still using your own stock recovery image..dl here
Click to expand...
Click to collapse
Thanks. Will try when I get my damn phone back from the service centre. After chasing everyday, it's finally repaired. Can I give your kernel a try?

Not even the new image works. Advice concerning the same: the phone will restart.

fiorello said:
Not even the new image works. Advice concerning the same: the phone will restart.
Click to expand...
Click to collapse
logs please..i dont know if the recovery of 901s even differs from the 901e..build is successful and no issues..

The file /cache/recovery.log is not created because the recovery will not start

fiorello said:
The file /cache/recovery.log is not created because the recovery will not start
Click to expand...
Click to collapse
last_kmsg will be created..i need to know where it is having issues..

I am attaching the file that I last_kmsg taken immediately after the restart of the phone

fiorello said:
I am attaching the file that I last_kmsg taken immediately after the restart of the phone
Click to expand...
Click to collapse
it cannot mount the partition thats why it restarts..can you do on a terminal for me a cat /proc/emmc command??so i can check the partitions..

kairi_zeroblade said:
it cannot mount the partition thats why it restarts..can you do on a terminal for me a cat /proc/emmc command??so i can check the partitions..
Click to expand...
Click to collapse
Here's one from my phone, running the system:
Code:
dev: size erasesize name
mmcblk0p20: 000ffa00 00000200 "misc"
mmcblk0p37: 00fffe00 00000200 "recovery"
mmcblk0p36: 01000000 00000200 "boot"
mmcblk0p38: 8bfffc00 00000200 "system"
mmcblk0p27: 00140200 00000200 "local"
mmcblk0p39: 17fffe00 00000200 "cache"
mmcblk0p40: 2d0000000 00000200 "userdata"
mmcblk0p23: 01400000 00000200 "devlog"
mmcblk0p25: 00040000 00000200 "pdata"
mmcblk0p28: 00010000 00000200 "extra"
mmcblk0p34: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p21: 00400000 00000200 "modem_st1"
mmcblk0p22: 00400000 00000200 "modem_st2"
mmcblk0p30: 00040000 00000200 "skylink"
mmcblk0p31: 01900000 00000200 "carrier"
mmcblk0p29: 00100000 00000200 "cdma_record"
mmcblk0p19: 01bffe00 00000200 "reserve_1"
mmcblk0p33: 034ffa00 00000200 "reserve_2"
mmcblk0p35: 05fffc00 00000200 "reserve_3"
mmcblk0p32: 04729a00 00000200 "reserve"
mmcblk0p26: 00004000 00000200 "control"

Result for cat / proc / EMMC attachment

ok so this is the fstab for twrp that its trying to mount..
Code:
# Android fstab file.
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p36
/cache ext4 /dev/block/mmcblk0p39
/data ext4 /dev/block/mmcblk0p40
/recovery emmc /dev/block/mmcblk0p37
/system ext4 /dev/block/mmcblk0p38
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
so everything seems to match..will rebuild in just a while..
edit: new image here..took me around 8 minutes to rebuild..lolz..kindly test and give feedback

To me it does not work: the phone is restarted.

fiorello said:
To me it does not work: the phone is restarted.
Click to expand...
Click to collapse
what recovery are you using recently??

TWRP 2.7.0.0 with SELinux support

fiorello said:
TWRP 2.7.0.0 with SELinux support
Click to expand...
Click to collapse
ok..am doing a rebuild now i think i got the fix..(wink*)
edit: here a new test build

:good: Now the phone easily fits into recovery, and also the problem of charging the phone is off it seems to work well. Now I want to try to do a backup and then a restore. I'll know in a few minutes.
For the moment, thank you very much.:fingers-crossed:
---------- Post added at 03:34 PM ---------- Previous post was at 03:30 PM ----------
Immediately an error: Unable to mount '/ cache'

fiorello said:
:good: Now the phone easily fits into recovery, and also the problem of charging the phone is off it seems to work well. Now I want to try to do a backup and then a restore. I'll know in a few minutes.
For the moment, thank you very much.:fingers-crossed:
Click to expand...
Click to collapse
hit the thanks button..i knew it..it was chickening me out..nonetheless will update this in a few days time..
dump me a recovery log this time..so i can double check..
edit: can you wipe cache and see if it mounts on next reboot?

I did a wipe cache and now it works. I do a backup and a restore and let you know.
---------- Post added at 04:08 PM ---------- Previous post was at 03:50 PM ----------
:good: Backup and Restore completed successfully!!!!

[Q] HTC Desire 626s - Need Root/Recovery

Hey everyone!
I am trying to get root access to my HTC Desire 626s.
I have been able to unlock it via HTCDev site.
At this point I believe I need to get root access.. I have tried the one click option Kingroot which was unsuccessful.. It always stops at 16-17%....
I believe I can obtain root access by flashing a CWM recovery which would have to be built for the 626s..
I am not sure if builder.clockworkmod.com is still functional?
Is anyone able to build a CWM recovery for this device? If so what would I need to provide?
Any help or responses would be much appreciated!
EDIT: Dump from /proc/emmc
130|[email protected]_a32eul:/ $ cat /proc/emmc
dev: size erasesize name
mmcblk0p1: 00004000 00000200 "board_info"
mmcblk0p2: 00400000 00000200 "pg1fs"
mmcblk0p3: 00100000 00000200 "sbl1"
mmcblk0p4: 01af7c00 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "rpm"
mmcblk0p8: 00200000 00000200 "tz"
mmcblk0p9: 00400000 00000200 "aboot"
mmcblk0p10: 00a00000 00000200 "sp1"
mmcblk0p11: 00008000 00000200 "ddr"
mmcblk0p12: 00100000 00000200 "rfg_0"
mmcblk0p13: 00100000 00000200 "rfg_1"
mmcblk0p14: 00100000 00000200 "rfg_2"
mmcblk0p15: 00100000 00000200 "rfg_3"
mmcblk0p16: 00100000 00000200 "rfg_4"
mmcblk0p17: 00100000 00000200 "rfg_5"
mmcblk0p18: 00100000 00000200 "rfg_6"
mmcblk0p19: 00100000 00000200 "rfg_7"
mmcblk0p20: 00180000 00000200 "fsg"
mmcblk0p21: 03b00400 00000200 "radio"
mmcblk0p22: 00a00000 00000200 "tool_diag"
mmcblk0p23: 00500000 00000200 "wcnss"
mmcblk0p24: 00000400 00000200 "limits"
mmcblk0p25: 00447c00 00000200 "reserve_2"
mmcblk0p26: 00100000 00000200 "misc"
mmcblk0p27: 00001000 00000200 "debug_config"
mmcblk0p28: 00180000 00000200 "modem_st1"
mmcblk0p29: 00180000 00000200 "modem_st2"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p31: 01600000 00000200 "persist"
mmcblk0p32: 00004000 00000200 "sec"
mmcblk0p33: 00100000 00000200 "cdma_record"
mmcblk0p34: 00000400 00000200 "fsc"
mmcblk0p35: 00002000 00000200 "ssd"
mmcblk0p36: 00020000 00000200 "rfg_8"
mmcblk0p37: 00020000 00000200 "rfg_9"
mmcblk0p38: 00020000 00000200 "rfg_10"
mmcblk0p39: 00020000 00000200 "rfg_11"
mmcblk0p40: 00020000 00000200 "rfg_12"
mmcblk0p41: 00020000 00000200 "rfg_13"
mmcblk0p42: 00020000 00000200 "rfg_14"
mmcblk0p43: 00020000 00000200 "rfg_15"
mmcblk0p44: 00004000 00000200 "control"
mmcblk0p45: 00010000 00000200 "extra"
mmcblk0p46: 00140400 00000200 "local"
mmcblk0p47: 00040000 00000200 "skylink"
mmcblk0p48: 02800000 00000200 "carrier"
mmcblk0p49: 00080000 00000200 "frp"
mmcblk0p50: 01400000 00000200 "fataldevlog"
mmcblk0p51: 01e00000 00000200 "devlog"
mmcblk0p52: 00a00000 00000200 "ramdump"
mmcblk0p53: 00a00000 00000200 "battery"
mmcblk0p54: 01000000 00000200 "absolute"
mmcblk0p55: 023a4800 00000200 "reserve"
mmcblk0p56: 03000000 00000200 "hosd"
mmcblk0p57: 02000000 00000200 "boot"
mmcblk0p58: 02000000 00000200 "recovery"
mmcblk0p59: 10000000 00000200 "cache"
mmcblk0p60: a0000000 00000200 "system"
mmcblk0p61: 12000000 00000200 "apppreload"
mmcblk0p62: 02800000 00000200 "cota"
mmcblk0p63: f0000000 00000200 "userdata"
When attempting to dd the recovery block I get an error since I don't have permission.
dd if=/dev/block/mmcblk0p58 of=/sdcard2/recovery.img

Was this the app or pc version of kingroot that failed?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

Anyone able to root this yet ?

http://forum.xda-developers.com/showthread.php?t=3181038 I made a thread got the stock recovery
Sent from my LGMS345 using Tapatalk

Just picked up this phone, awaiting a way to root, kingroot and kingoroot do not work. Cricket 626S. Already ran htcdev on it, need recovery to install supersu.

Update on Root?
I was hesitant to buy a new phone from MetroPCS lineup given that I was aware a root would not be available. This phone is great but has so much more capability. Not writing to SD card is crazy. You can trasnfer files on a PC between internal storage and SD. Anyway enough said. Does anyone have any updates on a root?

i found a thread with the stock recovery, i do not understand how to create a custom recovery ive gone over it over and over. i also tried the clockworkmod builder but it doesnt seem to be working i just get 404 errors. here is the link to the thread its the op. hopefully some one can make a custom recovery
http://forum.xda-developers.com/general/xda-assist/htc-desire-626s-cwm-build-t3181038

I'm also interested in this. I spent most of my time trying to extract the stock recovery from the RUU (which you can download from HTC's website, then extract using instructions here on XDA. It's basically starting the exe, then going to your temp directory). Some of the files can be extracted, but I think the others are encrypted. I've read that HTC started doing this a while back.
If the above link really is a copy of the stock recovery (and I'm curious to know how this was obtained), then we may be able to build CWM following these instructions- http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
Or maybe we also need the boot.img. I can't remember if this was one of the files I was able to extract from the RUU. Either way, there's some process by which we should be able to create a custom recovery.
Once we have something built and want to test it, you can try to boot your phone into the recovery without actually flashing it by running
Code:
fastboot boot recovery.img
. See these links- https://aubykhan.wordpress.com/2013/07/21/android-tip-boot-into-twrp-or-cwm-recovery-without-flashing/ http://androidforums.com/threads/stock-recovery-partition-image-backup.612148/ http://optionkey.blogspot.com/2013/12/backing-up-your-android-phones-stock.html
I'm kinda busy the next few weeks, but I definitely want to work on this when I get the chance some time. This is about the extent of what I know at this point. Have at it.

i tried that one, wont boot with fastboot boot cmd, says its a incomplete boot image

Here's something else worth looking into -https://twitter.com/srsroot/status/639544040489357312?s=09 which links to http://www.srsroot.com
If that doesn't work, it appears we can modify the boot.img file to gain root adb. I found it here http://androidforums.com/threads/htc-desire-626s-root.946455/ with more detailed instructions here http://android.stackexchange.com/questions/28653/obtaining-root-by-modifying-default-propro-secure
Again, I'll try this sometime, but I'll be pretty busy for a while.

k, ill take a looksie
edit: problem with this is, we need boot.img, but we can only get that with root xd

I might have that file. HTC posts their RUU files on their developer website. There are instructions floating around here showing how to extract them. It didn't have recovery, but it might have had boot.img. I just got to work, but I'll check when I get home.
Edit: Just check on TeamViewer. I've got a boot_signed.img file. We might be in business.

k man, that root kit doesnt work either im afraid
tried a few times
but is there a safe way to test the bootimg? can we boot that like we do recovery?

Perhaps you could boot it through fastboot, but I'm not finding any mention of it online. I'll probably give it a shot. Whenever I get to make it, I'll flash it on my device. Even if it's bad, we ought to be able to boot into fastboot and reflash the stock boot image. If that even fails, we have an RUU from HTC that should completely restore everything. And if THAT fails, then I wouldn't mind helping myself to the new Nexus 5X

lolol, i see how it is xD
here is hoping that it goes bad huh?

I tried modding the boot.img file I pulled from the RUU. I flashed it, and my phone booted fine, but didn't seem to have any root access via adb or terminal. I tried "adb root", but apparently you need a modded version of the adbd binary per this page- http://bclary.com/blog/2014/04/14/splitting-and-packing-android-boot-images/. I followed these instructions http://forum.xda-developers.com/showthread.php?t=2593581 and included an insecure adbd, but this made my phone go into a bootloop.
I was able to reflash the stock boot.img (from the RUU) after each time with no troubles. So, no bricks, but no root yet either. I notice that my device still has "s-on". Haven't been an HTC guy before, but I think that needs to be "s-off". I'll try again some other time.
Just to be thorough (in case anyone else wants to try), these tools helped to unpack the boot.img file - http://forum.xda-developers.com/showthread.php?t=1494036

i been a htc user for a few years now, and although i always got s-off before, im almost 100% certain that for gaining root its not needed.
unlocking bootloader should be enough, if we can get a custom recovery on it that is...

It may be worth investigating other ways of modifying the boot.img to give us root access over adb, but it seems that we need a version of adbd that won't cause a bootloop. I should mention that whenever I used the modified adbd binary (which always made it bootloop), I got a red warning/copyright message really quickly. It said something like "this HTC development something is property of HTC". I never got that message when I only modified default.prop.
A custom recovery would be the best option for sure. There's a post on XDA University about making CWM for a new device, and this method needs the boot.img (unlike the other method, which needs the recovery.img we don't have apparently). Reading the instructions, I'm not entirely sure it works for devices CM doesn't support, since it makes mention of the device codename, but I'm hopeful. Since I know for a fact we have a working stock boot.img (my phone is using it to boot now, lol), this looks like a good option.
---------- Post added at 08:57 AM ---------- Previous post was at 08:57 AM ----------
It may be worth investigating other ways of modifying the boot.img to give us root access over adb, but it seems that we need a version of adbd that won't cause a bootloop. I should mention that whenever I used the modified adbd binary (which always made it bootloop), I got a red warning/copyright message really quickly. It said something like "this HTC development something is property of HTC". I never got that message when I only modified default.prop.
A custom recovery would be the best option for sure. There's a post on XDA University about making CWM for a new device, and this method needs the boot.img (unlike the other method, which needs the recovery.img we don't have apparently). Reading the instructions, I'm not entirely sure it works for devices CM doesn't support, since it makes mention of the device codename, but I'm hopeful. Since I know for a fact we have a working stock boot.img (my phone is using it to boot now, lol), this looks like a good option.

well, we could always try TWRP recovery, if CWM doesnt work
Edit, thanx to another member here, i got files from a RUU, for the 626s, dont think that changes much, that "S"
anyway, in it i got boot, aboot, recovery etc, do you think we can do stuff with it?

From my understanding you need to set Selinux to permissive for an insecure boot.img to work on lollipop. I am unaware on how to do this but I believe we need to wait for HTC to post the Kernel source on HTCdev in order to do this.

htc one m7 bootloop problem please help

I flashed a viper4arise zip file from a thread from moto g4 plis section and now my phone is stuck on bootloop...
No switches are responsive...
When i press power button the home and back button led keeps blinking
Since i cannot remove battery im stuck...
Please help me

[/QUOTE]I have installed SwanSong and the sound is amazing. SwanSong have an aroma interface and it will be easy for you to install it with all the guides inside the installer. Here are the steps I have done to install it (Same as provided by @tywinlannister).
1. Install the BusyBox app and also install BusyBox inside it.
2. Set SELinux to be permissive. (This is important, but you can do it during the installation of SwanSong).
3. Flash Arise Sound Systems zip from the link https://www.androidfilehost.com/?w=files&flid=151719
(Click Aroma & look for ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip)
4. Reboot to system.
5. Configure the mods.
6. Reboot again.
This is the recommended setup from the developer itself while flashing SwanSong in Aroma. (Thanks to guitardedhero)
I would recommend Core (mandatory, if not already installed), ViPER4Arise™ 2.5.0.5, Profiles, Arkamys™, ICEsound™, Skip Config and Preset, MusicFX (unless you know it's already installed, this script will leave an existing MusicFX installation intact and end, just in case), permissive (do not, if Enforcing Mode is preferred), Repair SD Card Permissions (allow up to 3-5 minutes of additional time for this script).
Once booted:
Android Settings > Apps > Menu > Show System > Arkamys > Enable Phone Permissions
Android Settings > Apps > Menu > Show System > ViPER4Arise > Enable Storage Permissions
Open ViPER4Arise™ and select Audiophile™ X profile from the Load Effect Profile option in Menu.
On displayed output tab:
Master Power > Off
Master Power > On
Menu > Device Status
Should show Enabled, Normal, and Processing: Yes (at least during audio playback for some scenarios)
If you want to select ViPER4Arise™ through a media player's Equalizer option (not necessary, recommended for users that prefer to get to ViPER4Arise™ through a media player rather than launch the app from Recents or App Drawer):
Android Settings > Apps > Menu > Show System > MusicFX > Disable
Reboot for good measure.
Hope it will help for you. If anything bad happens, just dirty flash your rom (only wipe cache and dalvik) and everything will be good. :good:
NB: There will be a lot of modules during the aroma installation which you can skip (Toolkit, Dolby Plus, Dolby Atmos etc) if it is not mentioned in the recommended setup. Its your choice. Enjoy a crystal clear sound from the great developers.[/QUOTE]

This is the post ..
Please help it is urgent

Now i booted to recovery

Adarsh balu said:
Now i booted to recovery
Click to expand...
Click to collapse
Restore your phone back to stock using a RUU. Which one is hard to tell without seeing your "fastboot getvar all". What I can say is, appart from the problem described above, that your phone is messed up. Bootloader says M7_UL but its running the M7_WLS 5.05.651.2 firmware.... You bought it like that or....?

alray said:
Restore your phone back to stock using a RUU. Which one is hard to tell without seeing your "fastboot getvar all". What I can say is, appart from the problem described above, that your phone is messed up. Bootloader says M7_UL but its running the M7_WLS 5.05.651.2 firmware.... You bought it like that or....?
Click to expand...
Click to collapse
Please give correct steps on about it....please...

Adarsh balu said:
Please give correct steps on about it....please...
Click to expand...
Click to collapse
Post the output of "fastboot getvar all".

alray said:
Post the output of "fastboot getvar all".
Click to expand...
Click to collapse
Here is screen shot

<bootloader> version : 0.5
<bootloader> version-bootloader: 1.57.0000
<bootloader> version-baseband : N/A
<bootloader> version-cpld:None
<bootloader> version-microp:None
<bootloader> version-main :5.05.651.2
<bootloader> version-misc: PVT SHIP S-OFF
<bootloader> serialno:FA37VS920060
<bootloader> imei:355859054863182
<bootloader> meid:99000146057450
<bootloader> product:m7_ul
<bootloader> platform:HBOOT-8064
<bootloader> modelidN0720000
<bootloader> cidnum:11111111
<bootloader> battery-status:good
<bootloader> battery-voltage:3275 mV
<bootloader> partition-layout:Generic
<bootloader> security: off
<bootloader> build-mode:SHIP
<bootloader> boot-mode:FASTBOOT
<bootloader> commitno-bootloader:dirty-1f512bb6
<bootloader> hbootpreupdate: 11
<bootloader> gencheckpt:0
Please excuse me if there is typing mistake because i rushed it .....
Now can u help me ? @alray

Can anyone send stock rom kitkat for htc one m7 gsm....
Flashing that might work right
I have an unlocked bootloader now
Please tell me about it...
I'm desperate in need of help friends

Adarsh balu said:
<bootloader> version : 0.5
<bootloader> version-bootloader: 1.57.0000
<bootloader> version-baseband : N/A
<bootloader> version-cpld:None
<bootloader> version-microp:None
<bootloader> version-main :5.05.651.2 This is the Sprint M7_WLS version
<bootloader> version-misc: PVT SHIP S-OFF
<bootloader> serialno:*******20060
<bootloader> imei:3558590*******
<bootloader> meid:9900014******* A M7_UL should not have an meid...
<bootloader> product:m7_ul Says M7_UL but other vars indicates a M7_WLS
<bootloader> platform:HBOOT-8064
<bootloader> modelidN0720000 This is the Sprint (M7_WLS) modelid
<bootloader> cidnum:11111111
<bootloader> battery-status:good
<bootloader> battery-voltage:3275 mV
<bootloader> partition-layout:Generic
<bootloader> security: off
<bootloader> build-mode:SHIP
<bootloader> boot-mode:FASTBOOT
<bootloader> commitno-bootloader:dirty-1f512bb6
<bootloader> hbootpreupdate: 11
<bootloader> gencheckpt:0
Please excuse me if there is typing mistake because i rushed it .....
Now can u help me ? @alray
Click to expand...
Click to collapse
Really strange, the M7_UL variant is a GSM phone, GSM phones doesn't have MEID (should be all "0"), only the CDMA variants does (e.g Sprint M7_WLS).
Your MID (PN0720000) is for M7_WLS, not M7_UL and your version-main is also the Sprint M7_WLS version. But your "product" line says M7_UL. We must determine which variant your phone really is so we can know what files to use in order to restore it.
The M7_WLS does have a different partition layout than the M7_UL so by listing your partitions we should be able to determine what variant is your phone.
Flash twrp recovery if its not already done:
Code:
fastboot flash recovery twrp-3.0.0-2-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot in TWRP recovery so you have adb connectivity, start an adb shell then list your partitions using "cat /proc/emmc".
Code:
adb shell
cat /proc/emmc
The output should look like this (for a M7_UL):
Code:
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0[B][COLOR="red"]p35[/COLOR][/B]: 73fffc00 00000200 "[B][COLOR="Red"]system[/COLOR][/B]"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p38: 01900000 00000200 "carrier"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
mmcblk0p25: 00004000 00000200 "control"
The M7_WLS will have this partition layout:
Code:
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p36: 00fffe00 00000200 "recovery"
mmcblk0p35: 01000000 00000200 "boot"
mmcblk0[B][COLOR="red"]p37[/COLOR][/B]: 73fffc00 00000200 "[B][COLOR="red"]system[/COLOR][/B]"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p38: 27fffe00 00000200 "cache"
mmcblk0p39: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p33: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p29: 00040000 00000200 "skylink"
mmcblk0p30: 01900000 00000200 "carrier"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p32: 034ffa00 00000200 "reserve_2"
mmcblk0p34: 05fffc00 00000200 "reserve_3"
mmcblk0p31: 04729a00 00000200 "reserve"
Code:
For example, look at the "system" partition, it's located at p35 on a M7_UL but it's p37 on a M7_WLS.

alray said:
Really strange, the M7_UL variant is a GSM phone, GSM phones doesn't have MEID (should be all "0"), only the CDMA variants does (e.g Sprint M7_WLS).
Your MID (PN0720000) is for M7_WLS, not M7_UL and your version-main is also the Sprint M7_WLS version. But your "product" line says M7_UL. We must determine which variant your phone really is so we can know what files to use in order to restore it.
The M7_WLS does have a different partition layout than the M7_UL so by listing your partitions we should be able to determine what variant is your phone.
Flash twrp recovery if its not already done:
Then boot in TWRP recovery so you have adb connectivity, start an adb shell then list your partitions using "cat /proc/emmc".
adb shell
cat /proc/emmc
The output should look like this (for a M7_UL):
The output should look like this (for a M7_UL):
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p38: 01900000 00000200 "carrier"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
mmcblk0p25: 00004000 00000200 "control"
The M7_WLS will have this partition layout:
For example, look at the "system" partition, it's located at p35 on a M7_UL but it's p37 on a M7_WLS.
Click to expand...
Click to collapse
Main prob is that the roms the supesu gapps etc files won't completely copy into my internal storage...
Since there is no external slot i have to do this only by this way....
That i have found may be the problem while installing roms..
In the files it shows same size as that of the source file...That is really confusing ... Waiting for a reply from u @alray

Adarsh balu said:
Main prob is that the roms the supesu gapps etc files won't completely copy into my internal storage...
Since there is no external slot i have to do this only by this way....
That i have found may be the problem while installing roms..
In the files it shows same size as that of the source file...That is really confusing ... Waiting for a reply from u @alray
Click to expand...
Click to collapse
The problem is that I do not know for sure what phone variant you have (read my previous post). Without knowing for sure what it is, I can't suggest any solution (don't want to make the situation worse), both variants will requires to use different files. M7_UL roms, recoveries, kernels, ruu etc are not compatible with the M7_WLS.
If you prefer to keep flashing random files on it, if its up to you.

alray said:
The problem is that I do not know for sure what phone variant you have (read my previous post). Without knowing for sure what it is, I can't suggest any solution (don't want to make the situation worse), both variants will requires to use different files. M7_UL roms, recoveries, kernels, ruu etc are not compatible with the M7_WLS.
If you prefer to keep flashing random files on it, if its up to you.
Click to expand...
Click to collapse
In the recovery it is showing wls..see this pic. @alray

Adarsh balu said:
In the recovery it is showing wls..see this pic. @alray
Click to expand...
Click to collapse
adb shell
cat /proc/emmc
post the output
Btw no need to mention me if you're already quoting me, I get notified twice each time and its a bit annoying

alray said:
adb shell
cat /proc/emmc
post the output
Click to expand...
Click to collapse
Where to do this on pc ??
See im new and do not know much
So please can u tell me in detail when where and how..:crying:

Adarsh balu said:
Where to do this on pc ??
See im new and do not know much
So please can u tell me in detail when where and how..:crying:
Click to expand...
Click to collapse
Sure, do you have adb installed on your computer?

alray said:
Sure, do you have adb installed on your computer?
Click to expand...
Click to collapse
Yes

Adarsh balu said:
Yes
Click to expand...
Click to collapse
right click a blank space in the folder where you have adb.exe on your computer and from the contextual menu, select "open a command window here".
In that window, type:
Code:
adb shell
then hit enter and type
Code:
cat /proc/emmc
and hit enter again. This should list your partitions. Copy/paste (or screenshot) the output and post it here so we can take a look at it and finally be 100% sure what your phone really is.

alray said:
with click a blank space in the folder where you have adb.exe on your computer and from the contextual menu, select "open a command window here".
In that window, type:
then hit enter and type
and hit enter again. This should list your partitions. Copy/paste (or screenshot) the output and post it here so we can take a look at it and finally be 100% sure what your phone really is.
Click to expand...
Click to collapse
Im using pc and there is no current right now..
I will take screenshot just as it arriveea