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

Search This thread
By:
Advanced…
M

morschesholz

Senior Member
Apr 3, 2014
87
17
Well then maybe you should try to flash TWRP 2.7.0.5 again.
I know it sounds annoying but you should check if there are more adb.exe files on your computer which could be used by mistake when you type the adb command.
I really can't imagine that it is related to the recovery since it's working fine for others out there.
 
E

EdiBese

Senior Member
Oct 10, 2013
52
2
SHall we try it with CWM?

Can you tell me the command line for your specific version posted ?
 
M

morschesholz

Senior Member
Apr 3, 2014
87
17
You can try it with CWM, of course. There's a link in the first post, too. Personally I haven't used this version yet.
What command do you mean? I'm on a Mac, that's why my console/terminal looks different. Usage of adb and fastboot is the same.
It all comes down to the output of fastboot devices and adb devices.
 
E

EdiBese

Senior Member
Oct 10, 2013
52
2
flashed it again...

C:\Android>fastboot flash recovery twrp-2.7.0.5-m4kk.img
target reported max download size of 800227328 bytes
sending 'recovery' (9282 KB)...
OKAY [ 1.239s]
writing 'recovery'...
OKAY [ 2.301s]
finished. total time: 3.544s

Going into recovery

typing..

C:\Android>adb devices
List of devices attached

always same problem :((

ps kannst du deutsch?
 
Last edited:
M

morschesholz

Senior Member
Apr 3, 2014
87
17
Well, at least it doesn't give the error "adb server is out of date" anymore, right?
It simply doesn't output anything except the line: List of devices attached
Is that right?

Then please try the following. Close the console/terminal and open a new one with administrator privileges.
Then cd to Android again and run:
Code: 
adb kill-server
adb devices
 
E

EdiBese

Senior Member
Oct 10, 2013
52
2
morschesholz said:
Well, at least it doesn't give the error "adb server is out of date" anymore, right?
It simply doesn't output anything except the line: List of devices attached
Is that right?

Then please try the following. Close the console/terminal and open a new one with administrator privileges.
Then cd to Android again and run:
Code: 
adb kill-server
adb devices
Click to expand...
Click to collapse



DId

C:\Android>adb kill-server

C:\Android>adb devices
* daemon not running. starting it now on port 5037
* daemon started successfully *
List of devices attached


Right it says list of devices, bu it doesnt show my phone
 
M

morschesholz

Senior Member
Apr 3, 2014
87
17
Well, then the next thing to check would be if the driver is installed correctly. I assume it isn't since you uninstalled HTC Sync.
Go to device manager and look for an "Android ADB Interface" or "Android Composite ADB Interface" or something like that. Did you find any?
Or are there unrecognized devices (that is, havin a yellow exclamation mark)?
So now you need the adb drivers. Try this one: http://xdaforums.com/showthread.php?t=2588979 although I'm not sure if they work with the HTC One mini.
Only if Windows has fully recognized the device you'll be able to list it with adb devices.
 
E

EdiBese

Senior Member
Oct 10, 2013
52
2
morschesholz said:
Well, then the next thing to check would be if the driver is installed correctly. I assume it isn't since you uninstalled HTC Sync.
Go to device manager and look for an "Android ADB Interface" or "Android Composite ADB Interface" or something like that. Did you find any?
Or are there unrecognized devices (that is, havin a yellow exclamation mark)?
So now you need the adb drivers. Try this one: http://xdaforums.com/showthread.php?t=2588979 although I'm not sure if they work with the HTC One mini.
Only if Windows has fully recognized the device you'll be able to list it with adb devices.
Click to expand...
Click to collapse

when i put the phone in adb mode there is a yellow mark in the device manager "one mini!"

i am downloading the sdk bundle..

---------- Post added at 01:44 PM ---------- Previous post was at 01:03 PM ----------

i still dont get on.. can you help me `?
 
M

morschesholz

Senior Member
Apr 3, 2014
87
17
Download the attachment and unzip the folder.
Go to device manager, right click on "one mini" and select "update driver", then select "search on my computer" (or sth similar) and select the folder you just unzipped. Then the driver should be installed and the name of the device should change to sth with "ADB Device".

Are you on Windows 7? If you're on Windows 8 it may be more difficult. Just tell then.
 

Attachments

  • usb_driver_one_mini.zip
    8.3 MB · Views: 69
E

EdiBese

Senior Member
Oct 10, 2013
52
2
morschesholz said:
Download the attachment and unzip the folder.
Go to device manager, right click on "one mini" and select "update driver", then select "search on my computer" (or sth similar) and select the folder you just unzipped. Then the driver should be installed and the name of the device should change to sth with "ADB Device".

Are you on Windows 7? If you're on Windows 8 it may be more difficult. Just tell then.
Click to expand...
Click to collapse

Hi

I tried it, it begins to install the drivers but in the end it says "the hash number is not existing in the cataloge, the file is corrupt or has been changed.
 
M

morschesholz

Senior Member
Apr 3, 2014
87
17
J

J0ro

Member
Feb 28, 2012
21
0
I need to get to 2.22

Somehow I downgraded to 2.21 (don't really know how, don't ask me). I can't seem to find hboot 2.22 anywhere, neither a RUU I could use. Please help.

BTW: what is the latest radio version? Thanks in advance.
 
V

vegaz

Member
Sep 6, 2007
37
1
Germany
Samsung Galaxy Tab A series
HTC One (M9+, ME, E9+)
morschesholz said:
The links in the first post have been updated. Sorry, seems as if Dropbox doesn't like that much traffic.
Click to expand...
Click to collapse

I have fixed this ROM "Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip"

from here
http://androidfiles.org/?developer=M4&folder=Stock_Roms

edit updater-script file - line with txt editor in folder "/META-INF/com/google/android/"

run_program ("/ sbin/mke2fs", "-t" , "ext4", "-m", "0", "/ dev/block/mmcblk0p33"); mount ("ext4", "EMMC", "/ dev/block/mmcblk0p33", "/ system");

from mmcblk0p33 to mmcblk0p35 if you came from android 4.4.2

zipped again (not rar) and flash it.
 
E

EdiBese

Senior Member
Oct 10, 2013
52
2
Again big thank to morschescholz. Without his modified versions i couldnt use this phone any more, at least not so fast..

@ vegaz

The problem was Hboot 2.22 and my pc did not recognize my phone under adb mode, only under fastboot mode. But it was necesarry to push the rom on the sd card. But now all is working fine.

PS: Akkulife is much more better, but it 12% Android OS normal?
 
E

EdiBese

Senior Member
Oct 10, 2013
52
2
hi

I have a question

I am now on still on the nightly which is modded for the new partition layout. but it seems the version has some bugs. i cant use wlan anymore, the list dont refreshes any more so i cant find my router..

My question is, can i flash the newest nightly?

Other question. How do i wipe and reflash the new nightly. Should i wipe again after i flashed the new nightly?
 
You must log in or register to reply here.

Similar threads

V
4.3 update OTA 2.12.401.1
Replies
124
Views
116K
O
orst3n
jenkins-84
4.4.2 Update
Replies
230
Views
103K
T
thehetfield
T
Roms for hboot 2.22 and new partition layer
Replies
10
Views
52K
T
TommyR22
V
Sense 6 update OTA 4.09.401.3
Replies
45
Views
86K
T
teeodor
cmvienneau
MODDED HBOOT v4 2.22.0000 updated 4/16/2014
Replies
108
Views
114K
410eaL
410eaL

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 6
    M
    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:
    Code: 
    adb shell cat /proc/emmc

    Compare your output to this:
    Code: 
    $ 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://xdaforums.com/showpost.php?p=51612358&postcount=15 (MD5: 0bd688e0f39a6c37806b8695022afcdf)
    CWM 6.0.4.7: http://xdaforums.com/showpost.php?p=51740162&postcount=26 (MD5: 061fe34b19a817fb5b039a3531fba5a5)

    Flash it via fastboot:
    Code: 
    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://xdaforums.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)
    View
    1
    M
    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
    Code: 
    sudo adb kill-server
sudo adb devices
    and tell us the exact output.
    View
    1
    AnGrY sCoTsMaN
    AnGrY sCoTsMaN
    mircead1979 said:
    Can someone tell me how to update to new partition layout? My hboot is 2.19, s-on.
    Thank you!

    Sent from my HTC One mini using XDA Free mobile app
    Click to expand...
    Click to collapse

    From what I remember, if you are S-ON you will need to re-lock bootloader first
    So instead,
    what I would do is this ( Others may suggest a different way):

    obviously do a backup first
    S-OFF your device using Ramrunner
    Go Supercid, or you will have to find a Firmware update that matches your current CID & MODELID
    Download firmware zip from here https://drive.google.com/folderview?id=0B0xIhMfx77oQNHlzWXE0T2RSYWs&usp=sharing&tid=0B0xIhMfx77oQTGpOUXFiS3l0Z3M thanks to cmvienneau
    Copy it to your fastboot folder, and flash in fastboot
    You will need an updated recovery http://mdmower.cmphys.com/twrp-m4/ (some people have reported issues of device not being recognized by pc with this recovery, hence the threads re: otg cables...i do not have that problem)

    edit: there is also an updated cwm recovery, but i have not used that.

    and this is optional... flash cmvienneau modded Hboot to remove tampered flag etc etc http://xdaforums.com/showthread.php?t=2584810
    View

New posts