[4.4.2][HBOOT2.22] New partition layout with 4.4.2 OTA

[morschesholz]

Update

Watch out! Beginning with the 05/01 nightly the CM11 nightly builds are safe to flash no matter which partition layout you have. Other ROMs may not be independent from the partition layout yet and therefore still need to be modified before flashing. Read your ROM's FAQ or ask the devs for more information on that particular issue.


Introduction - What is this good for?

If you have been on a Stock ROM and got a Stock OTA update to 4.4.2 then it's very likely that you've got a "new partition layout".
This has the effect, that pretty all of the currently available ROMs flying around can't be one-click-flashed via recovery. (Technical background: The install scripts in the usual ROM zips contain instructions that refer to the old partition layout. With the "new layout" the scripts won't work anymore and flashing will fail.)
If you tried already and your phone isn't booting anymore ... Don't panic! As long as you get into fastboot mode, it is highly unlikely that your phone is bricked. And if you're able to flash and boot a recovery you're pretty safe.

Read on to find out how to deal with this.

What do you need?
You need adb and fastboot on your computer and you should basically know how to work with these tools. If you have a Windows computer you need the fastboot and adb drivers to be installed. Just use Google or refer to other sections of this forum on how to do that.


So first let's find out, if you're on the "new partition layout"

As far as I know for now the "new partition layout" comes with HBOOT 2.22. So boot into bootloader and check this out.
If you're not on 2.22 then you still could check the following thing. With 2.22 you definitely should continue.

Boot to your recovery and run the following adb command on your computer:

adb shell cat /proc/emmc

Compare your output to this:

$ adb shell cat /proc/emmc
dev:        size     erasesize name
mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 85fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 29fffe00 00000200 "cache"
mmcblk0p37: 2d8000000 00000200 "userdata"
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p23: 00400000 00000200 "modem_st1"
mmcblk0p24: 00400000 00000200 "modem_st2"
mmcblk0p32: 01fffc00 00000200 "reserve"
mmcblk0p28: 00004000 00000200 "control"

Please check very carefully, especially the lines ending with "system", "data", "cache", "boot" and "recovery"!!!

If your output looks the same then you have the "new partition layout". Then you will need a modified recovery that respects the "new partition layout".
Just use one of these (thanks to @kyasu):
TWRP 2.7.0.5: http://forum.xda-developers.com/showpost.php?p=51612358&postcount=15 (MD5: 0bd688e0f39a6c37806b8695022afcdf)
CWM 6.0.4.7: http://forum.xda-developers.com/showpost.php?p=51740162&postcount=26 (MD5: 061fe34b19a817fb5b039a3531fba5a5)

Flash it via fastboot:

fastboot flash recovery twrp-2.7.0.5-m4kk.img

If you even can't boot into recovery you have to flash one of these anyway.


Flash a ROM that has been modified to respect the new partition layout

As already said, almost all ROMs currently available don't match your partitions. The updater-scripts within have to be modified.
So let's collect all ROMs or zips that has been modified already and are therefore ready to flash (from the recovery as usual, as long it's one of the aforementioned).
Don't forget to flash boot.img via fastboot if you're S-ON.

Stock ROMs or nandroid backups:

Stock 4.4.2 (3.10.401.4) odexed or Stock 4.4.2 (3.10.631.5) deodexed can be found here:
http://forum.xda-developers.com/showthread.php?p=51779967 (infos about both ROMs in the first post of the thread)

Stock 4.4.2 (3.10.111.4) odexed nandroid backup from a German T-Mobile device:
https://drive.google.com/file/d/0ByRc8IR1ZBiveTludUt1ZUp4QUk/edit?usp=sharing (MD5: 0a1f21529328c7581f366954eeeba46a)
(should work on non-German devices, too)


Customized ROMs:

CM11 nightly 0403: https://drive.google.com/file/d/0ByRc8IR1ZBivZmpjWmt2YXhfT28/edit?usp=sharing (MD5: 3bc8d4694f1ee80992665138b252431f)
CM11 nightly 0412: https://drive.google.com/file/d/0ByRc8IR1ZBivZ2R0Q01fZHpxd1E/edit?usp=sharing (MD5: f502e43aa9cea3dab5a6b05f68953333)

 

[AnGrY sCoTsMaN]

great work, this should clarify things for people. i imagine users with the modified partition will not be able to flash cm11 nightlies until the roms are modified also ?

I currently s-off, hboot 2.19 & twrp 2.6.3. so ....flashing one of these (TWRP 2.7.0.5: http://forum.xda-developers.com/show...8&postcount=15 (MD5: 0bd688e0f39a6c37806b8695022afcdf)
CWM 6.0.4.7: http://forum.xda-developers.com/show...2&postcount=26 (MD5: 061fe34b19a817fb5b039a3531fba5a5)
recoveries will up modify my partition layout ??

cheers

 

[morschesholz]

so ....flashing one of these (TWRP 2.7.0.5: http://forum.xda-developers.com/show...8&postcount=15 (MD5: 0bd688e0f39a6c37806b8695022afcdf)
CWM 6.0.4.7: http://forum.xda-developers.com/show...2&postcount=26 (MD5: 061fe34b19a817fb5b039a3531fba5a5)
recoveries will up modify my partition layout ??

No, they don't. They're just modified to match the new partition layout (if you have it already).

 

[AnGrY sCoTsMaN]

OK,thanks.
Seems to me,that the way forward (only speculating) devs will produce Roms that will work with the new modified partition layout as its the latest firmware, meaning that pre hboot 2.22 will become obsolete and user will need to upgrade there hboot? surely there must be a simpler way than the route of supercid and flashing an ruu ?
forgive me if my question is wrong, just been off xda for the last few weeks n trying to catch up.

cheers

 

[EdiBese]

hi

I think thats the problem why i cant flash CM 11, because i have this 2.2.2 hboot new layout.

BUt i have a new problem now. I cant pull the rom via adb push onto my device. it says

*deamon started succesfull*
error device

Just dont know what to do..

PS: I have flashed the new TWRP 2.7.0.5, but i cant get the rom zip on the phone dunno why, it worked with 2.6.0.0...

 

[romy134]

I think thats the problem why i cant flash CM 11, because i have this 2.2.2 hboot new layout.

BUt i have a new problem now. I cant pull the rom via adb push onto my device. it says

*deamon started succesfull*
error device

Just dont know what to do..

PS: I have flashed the new TWRP 2.7.0.5, but i cant get the rom zip on the phone dunno why, it worked with 2.6.0.0...

I had a similar problem, I just used a OTG (On The Go) cable, with a flash drive.

 

[morschesholz]

OK,thanks.
Seems to me,that the way forward (only speculating) devs will produce Roms that will work with the new modified partition layout as its the latest firmware, meaning that pre hboot 2.22 will become obsolete and user will need to upgrade there hboot?

I'm not sure if the new partition layout will become the standard among the devs. Most of the users here switched to custom ROMs way before the OTA with HBOOT 2.22 was released. They all depend on ROMs made for the classic partition layout.
Since upgrading HBOOT isn't that easy (as you mentioned this needs performing a RUU or having S-OFF which is generally not necessary or recommended) it would be the best to stick with the old partition layout as long as possible.

I think thats the problem why i cant flash CM 11, because i have this 2.2.2 hboot new layout.

BUt i have a new problem now. I cant pull the rom via adb push onto my device. it says

*deamon started succesfull*
error device

Just dont know what to do..

PS: I have flashed the new TWRP 2.7.0.5, but i cant get the rom zip on the phone dunno why, it worked with 2.6.0.0...

Did you check the output of cat /proc/emmc as I mentioned above? Do that with the recovery that seems to work well (2.6.0.0 in your case). That's the only way to be absolutely sure about your partitions. Perhaps checking HBOOT version only is not sufficient.

 

[EdiBese]

hi

I'm not sure if the new partition layout will become the standard among the devs. Most of the users here switched to custom ROMs way before the OTA with HBOOT 2.22 was released. They all depend on ROMs made for the classic partition layout.
Since upgrading HBOOT isn't that easy (as you mentioned this needs performing a RUU or having S-OFF which is generally not necessary or recommended) it would be the best to stick with the old partition layout as long as possible.


Did you check the output of cat /proc/emmc as I mentioned above? Do that with the recovery that seems to work well (2.6.0.0 in your case). That's the only way to be absolutely sure about your partitions. Perhaps checking HBOOT version only is not sufficient.

no i didnt check

but i cant flash cm 11 with 2,6.3

it says symllink failed
error in binary counter or something like that

---------- Post added at 11:10 AM ---------- Previous post was at 10:59 AM ----------

I checked it out bro, it seems to be the same

mmcblk0p22: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 85fffc00 00000200 "system"
mmcblk0p29: 00140200 00000200 "local"
mmcblk0p36: 29fffe00 00000200 "cache"
mmcblk0p37: 2d8000000 00000200 "userdata
mmcblk0p25: 01400000 00000200 "devlog"
mmcblk0p27: 00040000 00000200 "pdata"
mmcblk0p30: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_con
mmcblk0p23: 00400000 00000200 "modem_st1
mmcblk0p24: 00400000 00000200 "modem_st2
mmcblk0p32: 01fffc00 00000200 "reserve"
mmcblk0p28: 00004000 00000200 "control"

 

[morschesholz]

Does your adb really only say: error device?
Usually the output is a little more verbose.
Are you on Windows or on Linux or Mac? On Linux or Mac you could try starting adb with sudo:

sudo adb kill-server
sudo adb devices

Then your device should be listed (a line containing the id of your device and the word "recovery").

 

[EdiBese]

hi

The problem is now.

When i flash 2.7.05, my phone cant be recognized when i am in TRWP mode. And this means i cant push the rom on the device iam stuck here.


I just see something bro look..

i have 2.6.0.0 now and pushed cm on the phone, but now i see i had cm on the /sdcard

But when i flash 2.7.0.5 i cant find cm on the sd card any more? ican find nothing on the sdcard

 

[morschesholz]

Just flash 2.7.0.5 again (be sure that it's the modified one from the first post here, it's name should be twrp-2.7.0.5-m4kk.img).
Then run

sudo adb kill-server
sudo adb devices

and tell us the exact output.

 

[EdiBese]

hi

C:\Android>adb devices
adb server is out of date.
* daemon started successfu
List of devices attached

If i try to push

C:\Android>adb push cm-11-20140411-NIGHTLY-m4.zip sdcard/
error: device not found

And in TWRP 2.6 it show 1620 MB Internal Storage, but in 2.7.05 it says 11308 MB, something is wrong..


I cant type in sudo, it doesnt work

---------- Post added at 11:47 AM ---------- Previous post was at 11:27 AM ----------

I downloadede the twrp of your post... flashed again.. same problem

I just cant get this rom on the phone!

 

[morschesholz]

Man, you have to use the modified 2.7.0.5 since it matches your new partition layout. That's why 2.7.0.5 is showing you the correct amount of free space: 11308 MB. That's the free space on your userdata partition (which is now at mmcblk0p37). 2.6.0.0 is made for the old layout and expects userdata to be at mmcblk0p35. As you can see from your emmc output, mmcblk0p35 is now /system on your device. That's why 2.6.0.0 is showing you only 1620 MB free space. That's the free space on the system partition.
So stay with 2.7.0.5!!!

The problem you have is that adb is not working. First of all, you can't adb push anything if your device is not recognized. That's what adb devices is doing: listing all recognized devices. So if adb devices shows nothing, nothing is recognized. It's that simple.
But as you can see adb devices tells you "adb server is out of date". Googling that error will give you lots of tips on how to deal with that problem: uninstalling HTC Sync should help.
Then you should be sure to have the latest adb and fastboot versions. You can download a current package here: http://forum.xda-developers.com/showthread.php?t=2317790

Then you first should do this again:

adb kill-server
adb devices

If - and really only if !!! - your output is something like that:

[[email protected] ~] adb devices
List of devices attached 
HTxxxxxxxxxx	recovery

then you're safe to continue.
But before flashing anything to the phone you should wipe all partitions. Go to Wipe > Advanced Wipe, select everything except USB OTG and Internal Storage and then swipe to wipe. After that you can adb push a cm.zip (a modified one) to your sdcard and install it. Finally flash boot.img via fastboot and you're done.

 

[EdiBese]

Man, you have to use the modified 2.7.0.5 since it matches your new partition layout. That's why 2.7.0.5 is showing you the correct amount of free space: 11308 MB. That's the free space on your userdata partition (which is now at mmcblk0p37). 2.6.0.0 is made for the old layout and expects userdata to be at mmcblk0p35. As you can see from your emmc output, mmcblk0p35 is now /system on your device. That's why 2.6.0.0 is showing you only 1620 MB free space. That's the free space on the system partition.
So stay with 2.7.0.5!!!

The problem you have is that adb is not working. First of all, you can't adb push anything if your device is not recognized. That's what adb devices is doing: listing all recognized devices. So if adb devices shows nothing, nothing is recognized. It's that simple.
But as you can see adb devices tells you "adb server is out of date". Googling that error will give you lots of tips on how to deal with that problem: uninstalling HTC Sync should help.
Then you should be sure to have the latest adb and fastboot versions. You can download a current package here: http://forum.xda-developers.com/showthread.php?t=2317790

Then you first should do this again:

adb kill-server
adb devices

If - and really only if !!! - your output is something like that:

[[email protected] ~] adb devices
List of devices attached 
HTxxxxxxxxxx	recovery

then you're safe to continue.
But before flashing anything to the phone you should wipe all partitions. Go to Wipe > Advanced Wipe, select everything except USB OTG and Internal Storage and then swipe to wipe. After that you can adb push a cm.zip (a modified one) to your sdcard and install it. Finally flash boot.img via fastboot and you're done.

Friend, i am on 2.7.0.5 the whole time. I know that my phone is not reognized but i dont know why, because on 2.6.3 it is recognized!

 

[morschesholz]

I'm sorry but that's all I can tell you. Do you have HTC Sync installed? Then I advise to uninstall it and use original adb and fastboot executable from the thread I linked to.

 

[EdiBese]

I'm sorry but that's all I can tell you. Do you have HTC Sync installed? Then I advise to uninstall it and use original adb and fastboot executable from the thread I linked to.

Yes HTC sync is installed, i just did everything what you said

But my phone is not recognized, dunno why

 

[morschesholz]

Just to be sure: Do you have restarted your computer after uninstalling all the HTC Software?

 

[EdiBese]

Just to be sure: Do you have restarted your computer after uninstalling all the HTC Software?

DId.. the same..

What i dont understand is, under 2.6. my phone i recognized and i can push files, i tried it out an hour ago.. but with 2.7.0.5 it isnt, means there is no problem with the software and drivers on the computer..

 

[morschesholz]

What about fastboot? Boot into fastboot mode and check if fastboot devices lists your phone.

 

[EdiBese]

hi

What about fastboot? Boot into fastboot mode and check if fastboot devices lists your phone.

Yes it does


C:\Android>fastboot devices
HT37NWA00458 fastboot