i am just looking for a simple guide on how to install insertcoin from 4.2 , i have firewater hboot soff and rooted, ? can i just flash the rom , i see problems with the operating system attempting to locate the drives if they are not partitioned correctly which is why i am asking here first, if it is as simple as just flashing the ROM then i apologize in advanced,
Thanks
U cant flash it bec its for kk
[email protected] said:
i am just looking for a simple guide on how to install insertcoin from 4.2 , i have firewater hboot soff and rooted, ? can i just flash the rom , i see problems with the operating system attempting to locate the drives if they are not partitioned correctly which is why i am asking here first, if it is as simple as just flashing the ROM then i apologize in advanced,
Thanks
Click to expand...
Click to collapse
Zara UL or CL? If UL use this modified rom for Zara UL 2.20.0000 and firewater hboot. Use recovery for Jelly Bean
https://drive.google.com/file/d/0B6bGr-ir8saMR1JvUW5qS3ZlNzg/edit?usp=sharing
standak14 said:
Zara UL or CL? If UL use this modified rom for Zara UL 2.20 and firewater hboot. Use recovery for Jelly Bean
https://drive.google.com/file/d/0B6bGr-ir8saMR1JvUW5qS3ZlNzg/edit?usp=sharing
Click to expand...
Click to collapse
its for zara cl virgin mobile, and to the guy who said it wasn't possible, that just don't make any sense , ( no pun intended ) i don't care if i have to upgrade the device to 4.4.2 or have to repartition the the drive manually , i am pretty technical and can handle any task. i just want to know the proper procedure. thanks in advanced.
[email protected] said:
its for zara cl virgin mobile, and to the guy who said it wasn't possible, that just don't make any sense , ( no pun intended ) i don't care if i have to upgrade the device to 4.4.2 or have to repartition the the drive manually , i am pretty technical and can handle any task. i just want to know the proper procedure. thanks in advanced.
Click to expand...
Click to collapse
For CL use this file. Open you rom in winrar, find path \META-INF\com\google\android and add from winrar menu downloaded file updater-script
https://drive.google.com/file/d/0B6bGr-ir8saMc20xc1RYQTJfbjQ/edit?usp=sharing
standak14 said:
For CL use this file. Open you rom in winrar, find path \META-INF\com\google\android and add from winrar menu downloaded file updater-script
https://drive.google.com/file/d/0B6bGr-ir8saMc20xc1RYQTJfbjQ/edit?usp=sharing
Click to expand...
Click to collapse
going to test within the hour and post back results, have you verified that this works, is this just a remapping of the partition tables that the rom writes to when flashing?, isnt the operating system going to be looking at the predefined paths set by the operating system?
[email protected] said:
going to test within the hour and post back results, have you verified that this works, is this just a remapping of the partition tables that the rom writes to when flashing?, isnt the operating system going to be looking at the predefined paths set by the operating system?
Click to expand...
Click to collapse
Post updated. Use this updater-script file.
Only changed instalation path in file updater-script
if
file_getprop("/tmp/aroma-data/wipe.prop","selected.0") == "2"
then
set_progress(0.10);
ui_print("@Executing Full Wipe");
ui_print("-> Erasing & formatting /cache as EXT4");
unmount("/cache");
format("ext4", "EMMC", "/dev/block/mmcblk0p34", "0"); Kitkat 36
set_progress(0.15);
ui_print("-> Erasing & formatting /system as EXT4");
unmount("/system");
format("ext4", "EMMC", "/dev/block/mmcblk0p33", "0"); Kitkat 35
set_progress(0.20);
ui_print("-> Erasing & formatting /data as EXT4");
mount("ext4", "EMMC", "/dev/block/mmcblk0p35", "/data"); Kitkat 37
package_extract_file("tools/wipe/wipe.sh", "/tmp/wipe.sh");
set_perm(0, 0, 0777, "/tmp/wipe.sh");
run_program("/tmp/wipe.sh");
etc.
This modifications works on Zara UL firewater hboot 2.20.5555 without problem
standak14 said:
Post updated. Use this updater-script file.
Only changed instalation path in file updater-script
if
file_getprop("/tmp/aroma-data/wipe.prop","selected.0") == "2"
then
set_progress(0.10);
ui_print("@Executing Full Wipe");
ui_print("-> Erasing & formatting /cache as EXT4");
unmount("/cache");
format("ext4", "EMMC", "/dev/block/mmcblk0p34", "0"); Kitkat 36
set_progress(0.15);
ui_print("-> Erasing & formatting /system as EXT4");
unmount("/system");
format("ext4", "EMMC", "/dev/block/mmcblk0p33", "0"); Kitkat 35
set_progress(0.20);
ui_print("-> Erasing & formatting /data as EXT4");
mount("ext4", "EMMC", "/dev/block/mmcblk0p35", "/data"); Kitkat 37
package_extract_file("tools/wipe/wipe.sh", "/tmp/wipe.sh");
set_perm(0, 0, 0777, "/tmp/wipe.sh");
run_program("/tmp/wipe.sh");
etc.
This modifications works on Zara UL firewater hboot 2.20.5555 without problem
Click to expand...
Click to collapse
im just going to hang tight ill try flashing it later , ul and cl are different devices and different partition tables due to different partitions being required.
[email protected] said:
im just going to hang tight ill try flashing it later , ul and cl are different devices and different partition tables due to different partitions being required.
Click to expand...
Click to collapse
Need help or not?
Partitions table is same. Zara CL have 2 partitions more
Zara UL
cat proc/emmc
dev: size erasesize name
mmcblk0p21: 000ffa00 00000200 "misc"
mmcblk0p32: 00fffe00 00000200 "recovery"
mmcblk0p31: 01000000 00000200 "boot"
mmcblk0p33: 71fffc00 00000200 "system"
mmcblk0p28: 00140200 00000200 "local"
mmcblk0p34: 0efffe00 00000200 "cache"
mmcblk0p35: 130000000 00000200 "userdata"
mmcblk0p24: 01400000 00000200 "devlog"
mmcblk0p26: 00040000 00000200 "pdata"
mmcblk0p29: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p22: 00400000 00000200 "modem_st1"
mmcblk0p23: 00400000 00000200 "modem_st2"
mmcblk0p30: 01fffc00 00000200 "reserve"
Zara CL
dev: size erasesize name
mmcblk0p21: 000ffa00 00000200 "misc"
mmcblk0p32: 00fffe00 00000200 "recovery"
mmcblk0p31: 01000000 00000200 "boot"
mmcblk0p33: 71fffc00 00000200 "system"
mmcblk0p28: 00140200 00000200 "local"
mmcblk0p34: 0efffe00 00000200 "cache"
mmcblk0p35: 130000000 00000200 "userdata"
mmcblk0p24: 01400000 00000200 "devlog"
mmcblk0p26: 00040000 00000200 "pdata"
mmcblk0p29: 00010000 00000200 "extra"
mmcblk0p36: 01900000 00000200 "carrier"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p22: 00400000 00000200 "modem_st1"
mmcblk0p23: 00400000 00000200 "modem_st2"
mmcblk0p36: 01900000 00000200 "carrier"
mmcblk0p30: 01fffc00 00000200 "reserve"
Here is modified insertcoin 6thsense zara cl-3.0.6 rom for Zara CL 2.20.0000 and firewater hboot. Use recovery for Jelly Bean
https://drive.google.com/file/d/0B6bGr-ir8saMNkV2X3B0Zy1vNDQ/edit?usp=sharing
sorry for the long delay i could not take a change because i need the phone to work at all times i have tested the updated rom and it is working 100%
Thank you very much.
standak14 said:
Need help or not?
Partitions table is same. Zara CL have 2 partitions more
Zara UL
cat proc/emmc
dev: size erasesize name
mmcblk0p21: 000ffa00 00000200 "misc"
mmcblk0p32: 00fffe00 00000200 "recovery"
mmcblk0p31: 01000000 00000200 "boot"
mmcblk0p33: 71fffc00 00000200 "system"
mmcblk0p28: 00140200 00000200 "local"
mmcblk0p34: 0efffe00 00000200 "cache"
mmcblk0p35: 130000000 00000200 "userdata"
mmcblk0p24: 01400000 00000200 "devlog"
mmcblk0p26: 00040000 00000200 "pdata"
mmcblk0p29: 00010000 00000200 "extra"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p22: 00400000 00000200 "modem_st1"
mmcblk0p23: 00400000 00000200 "modem_st2"
mmcblk0p30: 01fffc00 00000200 "reserve"
Zara CL
dev: size erasesize name
mmcblk0p21: 000ffa00 00000200 "misc"
mmcblk0p32: 00fffe00 00000200 "recovery"
mmcblk0p31: 01000000 00000200 "boot"
mmcblk0p33: 71fffc00 00000200 "system"
mmcblk0p28: 00140200 00000200 "local"
mmcblk0p34: 0efffe00 00000200 "cache"
mmcblk0p35: 130000000 00000200 "userdata"
mmcblk0p24: 01400000 00000200 "devlog"
mmcblk0p26: 00040000 00000200 "pdata"
mmcblk0p29: 00010000 00000200 "extra"
mmcblk0p36: 01900000 00000200 "carrier"
mmcblk0p16: 02d00000 00000200 "radio"
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p19: 007ffa00 00000200 "radio_config"
mmcblk0p22: 00400000 00000200 "modem_st1"
mmcblk0p23: 00400000 00000200 "modem_st2"
mmcblk0p36: 01900000 00000200 "carrier"
mmcblk0p30: 01fffc00 00000200 "reserve"
Here is modified insertcoin 6thsense zara cl-3.0.6 rom for Zara CL 2.20.0000 and firewater hboot. Use recovery for Jelly Bean
If I use the modified version can I still get the OTA updates to flash or will this cause problems?
What is the process to use the regular version?
Click to expand...
Click to collapse
Coach56 said:
If I use the modified version can I still get the OTA updates to flash or will this cause problems?
What is the process to use the regular version?
Click to expand...
Click to collapse
Different partition table in hboots 2.20 and 2.22
Ota updates should work. I have not tested.
Related
These are the partition mounts on the Amaze 4G:
Code:
dev: size erasesize name
mmcblk0p24: 00fff600 00000200 "misc"
mmcblk0p23: 00fffc00 00000200 "recovery"
mmcblk0p22: 01000000 00000200 "boot"
mmcblk0p29: 5ffffc00 00000200 "system"
mmcblk0p30: 13fffe00 00000200 "cache"
mmcblk0p31: 9ffffe00 00000200 "userdata"
mmcblk0p32: 01fba800 00000200 "devlog"
mmcblk0p34: 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"
nice!!! thanks cayniarb!! cant wait to see your work on this device!!
Cayniarb said:
These are the partition mounts on the Amaze 4G:
Code:
dev: size erasesize name
mmcblk0p24: 00fff600 00000200 "misc"
mmcblk0p23: 00fffc00 00000200 "recovery"
mmcblk0p22: 01000000 00000200 "boot"
mmcblk0p29: 5ffffc00 00000200 "system"
mmcblk0p30: 13fffe00 00000200 "cache"
mmcblk0p31: 9ffffe00 00000200 "userdata"
mmcblk0p32: 01fba800 00000200 "devlog"
mmcblk0p34: 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"
Click to expand...
Click to collapse
Thanks bro
Sent from my HTC_Amaze_4G using xda premium
I was thinking... could we pull the bootloader, hex edit it with S-OFF and flash it by the flash_image command?
Binary100100 said:
I was thinking... could we pull the bootloader, hex edit it with S-OFF and flash it by the flash_image command?
Click to expand...
Click to collapse
I dont think so.. if you could you would brick the phone all the way..
Sent from my HTC Sensation XE using xda premium
Good morning. I just dumped the mmcblk0p12 partition since it was 1024 bytes in size (same size as hboot). I then compared this dump to the hboot available in the bootloaders thread. The Md5sum of the dump matched up with the one I downloaded. This tells me that the partition we need access to is definitely number 12. When I tried to use gfree I noticed that it's trying to write to partition 18 I believe. Does anyone have that devs contact info ? Maybe they can recode the program to work for the Amaze just as a quick test ?
ok so after digging through some updater-scripts and what not I've determined that
mmcblk0p29 = system
mmcblk0p30 = cache
mmcblk0p31 = data
I'm trying to update some virtuous optimization scripts to work with our device and I need to know what partition is the devblock and is it even writeable for us without s-off? if not then I'll just comment out that part of the script, but if you know which partition that is could you please reply, thanks!
Code:
adb shell mount
Run that comand in adb, you will see all mounts.
Here are mounts I just dug up from an old PM...
dev: size erasesize name
mmcblk0p24: 00fff600 00000200 "misc"
mmcblk0p23: 00fffc00 00000200 "recovery"
mmcblk0p22: 01000000 00000200 "boot"
mmcblk0p29: 5ffffc00 00000200 "system"
mmcblk0p30: 13fffe00 00000200 "cache"
mmcblk0p31: 9ffffe00 00000200 "userdata"
mmcblk0p32: 01fba800 00000200 "devlog"
mmcblk0p34: 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
Click to expand...
Click to collapse
These are correct AFAIK but it was sent to me a long time ago...so run the command in ADB.to be sure. I am away from my pc or I would do it myself.
Sent from my HTC_Amaze_4G using xda premium
mcs117 said:
Lemme post what I found so far....
mmcblk0p1(sbl1)
mmcblk0p2(sbl2)
mmcblk0p4(CID & IMEI)
mmcblk0p5(CID & IMEI)
mmcblk0p7(S-on sbl1)
mmcblk0p8(S-on sbl2)
mmcblk0p9(sbl3)
mmcblk0p10(rpm)
mmcblk0p12(hboot)
mmcblk0p13(S-off SID)
mmcblk0p14(splash)
mmcblk0p17(radio)
mmcblk0p18(mdm9k)
mmcblk0p19(radio_config_or_empty)
mmcblk0p20(mdm9k_config)
mmcblk0p21(adsp)
mmcblk0p22(boot)
mmcblk0p23(recovery)
mmcblk0p24(misc)
mmcblk0p25(empty)
mmcblk0p26(empty)
mmcblk0p27(mdm_efs1)
mmcblk0p28(mdm_efs2)
mmcblk0p30(cache)
mmcblk0p32(devlog)
mmcblk0p33(empty)
mmcblk0p34(pdata_or_empty)
mmcblk0p35(empty)
Click to expand...
Click to collapse
Dug this up too, hope this helps...Good luck...Ben
Sent from my HTC_Amaze_4G using xda premium
awesome man, thanks, really appreciate that!
Anyone know how to copy the stock recovery?
I can't get around unless I flash custom recovery to get root to do it either in custom recovery or using root, but that is useless as I have already overwritten the recovery
Code:
cat /proc/emmc
dev: size erasesize name
mmcblk0p23: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffe00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p35: 4dfffc00 00000200 "system"
mmcblk0p30: 00140200 00000200 "local"
mmcblk0p36: 0dfffe00 00000200 "cache"
mmcblk0p37: 89fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p38: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
mmcblk0p17: 02d00000 00000200 "radio"
mmcblk0p18: 00a00000 00000200 "adsp"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p19: 00500000 00000200 "wcnss"
mmcblk0p20: 007ffa00 00000200 "radio_config"
mmcblk0p24: 00400000 00000200 "modem_st1"
mmcblk0p25: 00400000 00000200 "modem_st2"
mmcblk0p32: 00040000 00000200 "skylink"
mmcblk0p33: 00040000 00000200 "cdma_record"
What are the rest of the partitions (and where can I find this information?)
For example, from the splash screen thread, mmcblk0p14 is where the boot splash is stored.
hello.
For SIM Unlock of HTC J butterfly (HTL21 / KDDI japanese ver),I want radio.img of DROID DNA...
Probably the number of the block is mmcblk0p16.
c:\adb\DLX_J>adb shell cat /proc/emmc
dev: size erasesize name
mmcblk0p21: 000ffa00 00000200 "misc"
mmcblk0p20: 00fffe00 00000200 "recovery"
mmcblk0p19: 01000000 00000200 "boot"
mmcblk0p32: 73fffc00 00000200 "system"
mmcblk0p28: 00140200 00000200 "local"
mmcblk0p33: 17fffe00 00000200 "cache"
mmcblk0p34: 2f8000000 00000200 "userdata"
mmcblk0p24: 01400000 00000200 "devlog"
mmcblk0p26: 00040000 00000200 "pdata"
mmcblk0p29: 00010000 00000200 "extra"
mmcblk0p16: 03200200 00000200 "radio" ← this!!
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 007ffa00 00000200 "radio_config
mmcblk0p22: 00400000 00000200 "modem_st1"
mmcblk0p23: 00400000 00000200 "modem_st2"
mmcblk0p30: 00100000 00000200 "cdma_record"
mmcblk0p35: 01400000 00000200 "nfc_record"
mmcblk0p31: 06069e00 00000200 "reserve"
Will you upload it...?
thanks
Ruh roh
Sent from my HTC6435LVW using xda premium
fnoji111 said:
hello.
For SIM Unlock of HTC J butterfly (HTL21 / KDDI japanese ver),I want radio.img of DROID DNA...
Probably the number of the block is mmcblk0p16.
c:\adb\DLX_J>adb shell cat /proc/emmc
dev: size erasesize name
mmcblk0p21: 000ffa00 00000200 "misc"
mmcblk0p20: 00fffe00 00000200 "recovery"
mmcblk0p19: 01000000 00000200 "boot"
mmcblk0p32: 73fffc00 00000200 "system"
mmcblk0p28: 00140200 00000200 "local"
mmcblk0p33: 17fffe00 00000200 "cache"
mmcblk0p34: 2f8000000 00000200 "userdata"
mmcblk0p24: 01400000 00000200 "devlog"
mmcblk0p26: 00040000 00000200 "pdata"
mmcblk0p29: 00010000 00000200 "extra"
mmcblk0p16: 03200200 00000200 "radio" ← this!!
mmcblk0p17: 00a00000 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 007ffa00 00000200 "radio_config
mmcblk0p22: 00400000 00000200 "modem_st1"
mmcblk0p23: 00400000 00000200 "modem_st2"
mmcblk0p30: 00100000 00000200 "cdma_record"
mmcblk0p35: 01400000 00000200 "nfc_record"
mmcblk0p31: 06069e00 00000200 "reserve"
Will you upload it...?
thanks
Click to expand...
Click to collapse
The commands are as follows.
adb shell
$ su
# dd if=/dev/block/mmcblk0p16 of=/sdcard/radio.img
radio.img is in to Storage
Here you go radio.img - 50.00 MB
thanks!
androidoholic said:
Here you go radio.img - 50.00 MB
Click to expand...
Click to collapse
special thanks!!!
I don't know that much about modding/rooting other than what I can find on the internet. I also don't fully understand how android interfaces with hardware.
I purchased an HTC One Max from ebay. It was new in oem packaging. OS version 4.4.2. I haven't been able to get the phone to update beyond this version of android so I Rooted and installed a custom ROM that is a port of the M8 modified to work on the Max display and hardware. It works fine but I'd like to actually get the Dev version RUU 4.14.1540.11 installed on my phone.
Yes it is an older model from HTC.. I love it
model info:
One Max T6wl (Verizon)
MID 0P3P1000 modified to 0P3P5000
CID 11111111
bootloader 2.49.0000
baseband 1.36.60.0520
Version 3.09.605.2 (4.14.1540.11 showing either from current ROM or RUU fail)
Code:
adb shell cat /proc/emmc >emmc.txt
dev: size erasesize name
mmcblk0p21: 000ffa00 00000200 "misc"
mmcblk0p38: 00fffe00 00000200 "recovery"
mmcblk0p37: 01000000 00000200 "boot"
mmcblk0p39: 98000000 00000200 "system"
mmcblk0p28: 00140200 00000200 "local"
mmcblk0p41: 3ffffe00 00000200 "cache"
mmcblk0p42: 640000000 00000200 "userdata"
mmcblk0p24: 01400000 00000200 "devlog"
mmcblk0p26: 00040000 00000200 "pdata"
mmcblk0p29: 00010000 00000200 "extra"
mmcblk0p34: 05000000 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p18: 00500000 00000200 "wcnss"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p22: 00400000 00000200 "modem_st1"
mmcblk0p23: 00400000 00000200 "modem_st2"
mmcblk0p31: 00040000 00000200 "skylink"
mmcblk0p32: 01900000 00000200 "carrier"
mmcblk0p30: 00100000 00000200 "cdma_record"
mmcblk0p20: 016ffc00 00000200 "reserve_1"
mmcblk0p35: 02fffc00 00000200 "reserve_2"
mmcblk0p36: 05fffc00 00000200 "reserve_3"
mmcblk0p40: 03fffa00 00000200 "reserve_4"
mmcblk0p33: 04729a00 00000200 "reserve"
mmcblk0p27: 00004000 00000200 "control"
I've searched for months now and all that I can find is what everyone else is doing and nothing I want. In fact a great deal of the adb commands I've found haven't worked for me. None of which apply to what I want to accomplish.
When I tried to run dev RUU on my phone after modifying the MID it would fail and give me the 4 corner triangles. I tried to extract the rom.zip from RUU and flash via fastboot
If RUU failed why would this work right?
Doing anyway ...
Code:
fastboot oem rebootRUU
fastboot flash zip rom.zip
succeed...
succeed...
failed bypassing...
succeed...
succeed...
bla bla..
FAILED (remote: 51 partition update fail)
don't have the actual output for each update section. Maybe I'll try to run again and attempt and output to file during.
I imagine it could be do to partition size variations but I have no way of confirming it. I've left my recovery and boot images and it still failed on system partition. any help would be appreciated.