5,601,062 Members 46,315 Now Online
XDA Developers Android and Mobile Development Forum

[Q] M7UL Baseband & IMEI Unknown - Partitions?

Tip us?
 
sotplug
Old
(Last edited by sotplug; 14th December 2013 at 08:33 PM.) Reason: added partition check info
#11  
Junior Member - OP
Thanks Meter 2
Posts: 17
Join Date: Aug 2011
Quote:
Originally Posted by nkk71 View Post
so even after a RUU, (no updates) it still doesn't hold? which RUU are you using, link please
Got my RUU from here:
ruu_m7_ul_jb_50_htc_asia_wwe_1-29-707-3_r_radio_4a-14-3250-13_10-33-1150-01_release_311678_signed-exe/
After lock screen, no Sense UI.
Just white HTC logo screen.
Then auto restarts every 1-2 mins.

Then using stock recovery, apply OTA:
ota_m7_ul_jb_50_htc_asia_wwe_1-29-707-16_r-1-29-707-3_r_release_318610_signedkaytj0xrerk0cnd9-zip/
Same result.

Not easy to find a x.xx.707.x RUU.
However, this is a hboot 1.44 RUU.
My phone started out originally as hboot 1.54.
Could this be a problem?

===== Update =====
adb shell

mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p36 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p37 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)

umount /data

umount /sdcard

e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

644 inodes used (0.04%)
4 non-contiguous files (0.6%)
1 non-contiguous directory (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 634
151815 blocks used (2.23%)
0 bad blocks
1 large file

40 regular files
593 directories
0 character device files
0 block device files
0 fifos
0 links
1 symbolic link (1 fast symbolic link)
1 socket
--------
635 files

e2fsck -n -v -f /dev/block/mmcblk0p35
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create? no

Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/block/mmcblk0p35: ********** WARNING: Filesystem still has errors **********


2367 inodes used (2.06%)
4 non-contiguous files (0.2%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2298
370293 blocks used (80.72%)
0 bad blocks
0 large files

2213 regular files
85 directories
0 character device files
0 block device files
0 fifos
0 links
60 symbolic links (60 fast symbolic links)
0 sockets
--------
2358 files
 
nkk71
Old
#12  
nkk71's Avatar
Recognized Contributor
Thanks Meter 2099
Posts: 4,321
Join Date: May 2010
Location: Beirut
Quote:
Originally Posted by sotplug View Post
Pass 3: Checking directory connectivity
/lost+found not found. Create? no

/dev/block/mmcblk0p35: ********** WARNING: Filesystem still has errors **********
Minor error, once the ROM boots up it should recreate lost&found when needed.



Quote:
Originally Posted by sotplug View Post
Not easy to find a x.xx.707.x RUU.
However, this is a hboot 1.44 RUU.
My phone started out originally as hboot 1.54.
Could this be a problem?
No, shouldnt be a problem.




Quote:
Originally Posted by sotplug View Post
Got my RUU from here:
ruu_m7_ul_jb_50_htc_asia_wwe_1-29-707-3_r_radio_4a-14-3250-13_10-33-1150-01_release_311678_signed-exe/
After lock screen, no Sense UI.
Just white HTC logo screen.
Then auto restarts every 1-2 mins.
starting to sound like a hardware issue.

1- try removing the SIM card
2- set CID back to original
3- run the RUU (you may need to downgrade hboot separately first)

once the RUU is successfully applied, go to bootloader and check "fastboot getvar all", that baseband and firmware versions are correct.
The Following User Says Thank You to nkk71 For This Useful Post: [ Click to Expand ]
 
sotplug
Old
(Last edited by sotplug; 15th December 2013 at 02:04 PM.) Reason: Used ruu hboot and recovery
#13  
Junior Member - OP
Thanks Meter 2
Posts: 17
Join Date: Aug 2011
Quote:
Originally Posted by nkk71 View Post
Minor error, once the ROM boots up it should recreate lost&found when needed.
I did let it boot/auto-reboot a few times until the HTC lock screen.
So it seems that the boots are incomplete.

Quote:
Originally Posted by nkk71 View Post
starting to sound like a hardware issue.

1- try removing the SIM card
2- set CID back to original
3- run the RUU (you may need to downgrade hboot separately first)

once the RUU is successfully applied, go to bootloader and check "fastboot getvar all", that baseband and firmware versions are correct.
Actually, this is exactly what I did.
I even used stock hboot and recovery from the RUU (decrypted using ruuveal)
Anyway, will try a few times again with different RUUs.
If still unsuccessful, maybe I should just bring back for warranty service.

And thanks a lot for trying to help. Really appreciate it.
 
nkk71
Old
#14  
nkk71's Avatar
Recognized Contributor
Thanks Meter 2099
Posts: 4,321
Join Date: May 2010
Location: Beirut
Quote:
Originally Posted by sotplug View Post
I did let it boot/auto-reboot a few times until the HTC lock screen.
So it seems that the boots are incomplete.



Actually, this is exactly what I did.
I even used stock hboot and recovery from the RUU (decrypted using ruuveal)
Anyway, will try a few times again with different RUUs.
If still unsuccessful, maybe I should just bring back for warranty service.

And thanks a lot for trying to help. Really appreciate it.
no problem, probably best to take it to service, we could try formatting the partitions (only data and system, not the raw ones), but i wouldnt hold my breath that it would help.
The Following User Says Thank You to nkk71 For This Useful Post: [ Click to Expand ]
 
z0me
Old
(Last edited by z0me; 8th January 2014 at 03:38 PM.) Reason: Just checked out the "Going back to stock guide" in nkk71's signature
#15  
Junior Member
Thanks Meter 10
Posts: 5
Join Date: Mar 2011
Default Running into the same problems

I have the same problems. I was about to try S-Off and RUU, but I just read here that it doesn't seem to work.

fastboot getvar all
 
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <removed>
(bootloader) imei: <removed>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0


As you see, I'm still on HBOOT 1.44. I never installed another one.

(it started with random auto-reboots, they got more frequent and regular, so I re-flashed different roms and restored a backup with TWRP. The baseband started to be unknown in every rom after the restore or after flashing CM)

Did you find a solution or send it to service ? Successfully ?
What should I do ? Do I have any chance with RUU and going back to stock ?

Or should I just send it to service and hope ?

Thanks !
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes