I am just not sure how an entire phone can be bricked just by trying to flash a 32 bit Kitkat over a phone with clean storage. Notice my stress on the word clean. By clean I meant a phone with /boot and /system partitions entirely wiped off. By wiping off /boot, I am essentially clearing off the kernel and ramdisk.
To explain what I am trying to say, I'll give an example:
Lets assume the phone has lollipop installed. Lets also assume that the phone has 64 bit TWRP installed as recovery. Now in the recovery mode, if I wipe off /boot and /system, I am essentially getting rid of the entire operating system, kernel and the ramdisk. Now if I switch to fastboot mode from inside TWRP and re-flash stock KitKat, my /boot and /system will be recreated. And I don't see any reason, why the phone will not be able to boot into Kitkat from there.
What do you say guys? Did I assume something wrong here? I need your opinion.
Go to this thread you will find answer there http://forum.xda-developers.com/yureka/general/cyanogen-12-lollipop-to-cyanogen-11-t3096587
If you clean flash on your phone, what about your firmware? Have you wiped it as well?
Wow, finally there is a person who ask the question
sanj_cm_fan said:
I am just not sure how an entire phone can be bricked just by trying to flash a 32 bit Kitkat over a phone with clean storage. Notice my stress on the word clean. By clean I meant a phone with /boot and /system partitions entirely wiped off. By wiping off /boot, I am essentially clearing off the kernel and ramdisk.
Click to expand...
Click to collapse
Wow at last, a person with good question. Well first I don't know what have change with the x64 edition of stock lollipop (currently downloading the fastboot rom and then will do some hex comparison between all the image listed in the zip), cos just for your info, changing boot.img and system.img will not put your phone unrecognizable by windows (see all post in my thread HERE). The worse case, it will put your phone directly to QDLoader (9008) mode.
If you ask why, here is the simple answer, qualcomm's phone first will boot the "Secondary Boot Loader" a.k.a sbl1.mbn (sbl1 partition), then your phone "eMMC Boot Loader" a.k.a emmc_appsboot.mbn a.k.a the fastboot mode (aboot partition), then your phone "Resource and Power Management" a.k.a rpm.mbn (rpm partition), then the Trust Zone a.k.a tz.mbn (tz partition), then the HYP (now I don't really no what this is, but through hex reading on hyp.mbn, it includes some new protocol like SBL, but shorter), see below diagrams:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, by just flashing wrong boot.img and system.img, will not make your phone unrecognisable by windows, unless somehow you manage to complete formatted your whole eMMC.
I just wonder, how did actually those people really make their phone unrecognizable by windows. The safest thing to do when you downgrading or upgrading your phone via fastboot is first by formatting and erasing all of the old files respective to their partitions, and then flashing the new images, such as below:
Code:
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf erase modem
fastboot -i 0x1ebf erase boot
fastboot -i 0x1ebf erase recovery
fastboot -i 0x1ebf erase aboot
fastboot -i 0x1ebf erase abootbak
fastboot -i 0x1ebf erase hyp
fastboot -i 0x1ebf erase hypbak
fastboot -i 0x1ebf erase rpm
fastboot -i 0x1ebf erase rpmbak
fastboot -i 0x1ebf erase sbl1
fastboot -i 0x1ebf erase sbl1bak
fastboot -i 0x1ebf erase tz
fastboot -i 0x1ebf erase tzbak
fastboot -i 0x1ebf format system
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf flash modem NON-HLOS.bin
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash sbl1bak sbl1.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash abootbak emmc_appsboot.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash rpmbak rpm.mbn
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash tzbak tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash hypbak hyp.mbn
fastboot -i 0x1ebf flash boot boot.img
fastboot -i 0x1ebf flash recovery recovery.img
fastboot -i 0x1ebf flash system system.img
fastboot -i 0x1ebf reboot-bootloader
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
Just do this code, and you will safely downgrade your phone to kitkat.
tirta.agung said:
Wow at last, a person with good question. Well first I don't know what have change with the x64 edition of stock lollipop (currently downloading the fastboot rom and then will do some hex comparison between all the image listed in the zip), cos just for your info, changing boot.img and system.img will not put your phone unrecognizable by windows (see all post in my thread HERE). The worse case, it will put your phone directly to QDLoader (9008) mode.
If you ask why, here is the simple answer, qualcomm's phone first will boot the "Secondary Boot Loader" a.k.a sbl1.mbn (sbl1 partition), then your phone "eMMC Boot Loader" a.k.a emmc_appsboot.mbn a.k.a the fastboot mode (aboot partition), then your phone "Resource and Power Management" a.k.a rpm.mbn (rpm partition), then the Trust Zone a.k.a tz.mbn (tz partition), then the HYP (now I don't really no what this is, but through hex reading on hyp.mbn, it includes some new protocol like SBL, but shorter), see below diagrams:
So, by just flashing wrong boot.img and system.img, will not make your phone unrecognisable by windows, unless somehow you manage to complete formatted your whole eMMC.
I just wonder, how did actually those people really make their phone unrecognizable by windows. The safest thing to do when you downgrading or upgrading your phone via fastboot is first by formatting and erasing all of the old files respective to their partitions, and then flashing the new images, such as below:
Code:
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf erase modem
fastboot -i 0x1ebf erase boot
fastboot -i 0x1ebf erase recovery
fastboot -i 0x1ebf erase aboot
fastboot -i 0x1ebf erase abootbak
fastboot -i 0x1ebf erase hyp
fastboot -i 0x1ebf erase hypbak
fastboot -i 0x1ebf erase rpm
fastboot -i 0x1ebf erase rpmbak
fastboot -i 0x1ebf erase sbl1
fastboot -i 0x1ebf erase sbl1bak
fastboot -i 0x1ebf erase tz
fastboot -i 0x1ebf erase tzbak
fastboot -i 0x1ebf format system
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf flash modem NON-HLOS.bin
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash sbl1bak sbl1.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash abootbak emmc_appsboot.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash rpmbak rpm.mbn
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash tzbak tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash hypbak hyp.mbn
fastboot -i 0x1ebf flash boot boot.img
fastboot -i 0x1ebf flash recovery recovery.img
fastboot -i 0x1ebf flash system system.img
fastboot -i 0x1ebf reboot-bootloader
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
Just do this code, and you will safely downgrade your phone to kitkat.
Click to expand...
Click to collapse
Thanks a lot Tirta. Finally someone answered my query in such vivid details. So what it boils down to is to delete the firmware specific stuff: secondary boot loader, eMMC boot loader, resource and power management, trust zone and hyp (whatever that is). Then flash the old firmware (sbl1, aboot, rpm, tz, hyp and offcourse the modem) that came with cm11 fastboot package. This is just awesome. Can you tell me something? I don't see any sbl1, aboot, rpm, tz, hyp and modem partitions in the phone. This is what my phone's partition table looks like:
Code:
Filesystem Size Used Free Blksize
/dev 930.0M 56.0K 930.0M 4096
/sys/fs/cgroup 930.0M 12.0K 930.0M 4096
/mnt/asec 930.0M 0.0K 930.0M 4096
/mnt/obb 930.0M 0.0K 930.0M 4096
/system 1.1G 1.1G 76.6M 4096
/data 12.8G 3.0G 9.8G 4096
/cache 122.0M 100.0K 121.9M 4096
/persist 5.8M 96.0K 5.7M 4096
/firmware 64.0M 45.1M 18.9M 16384
/mnt/shell/emulated 12.8G 3.0G 9.8G 4096
/storage/emulated 930.0M 0.0K 930.0M 4096
/mnt/media_rw/sdcard1 29.5G 23.1G 6.4G 32768
/mnt/secure/asec 29.5G 23.1G 6.4G 32768
/storage/sdcard1 29.5G 23.1G 6.4G 32768
/storage/emulated/0 12.8G 3.0G 9.8G 4096
/storage/emulated/0/Android/obb 12.8G 3.0G 9.8G 4096
/storage/emulated/legacy 12.8G 3.0G 9.8G 4096
/storage/emulated/legacy/Android/obb 12.8G 3.0G 9.8G 4096
In the firmware partition (in /firmware/image directory), I do see files that may be related with sbl1, aboot, tz, rpm, hyp and modem.
So the partition names which are mentioned while flashing through fastboot, are more logical than physical? Or is it that you need to use some other executable to find out the entire partition table in Android?
Can I assume that on flashing cm11 fastboot package directly on top of the cm12s installation, it will screw sbl1 and aboot partitions and hence the brick?
Thanks,
Sanjay
sanj_cm_fan said:
Can you tell me something? I don't see any sbl1, aboot, rpm, tz, hyp and modem partitions in the phone.
Click to expand...
Click to collapse
Use this command to see those partitions:
Code:
adb shell
ls -al /dev/block/bootdevice/by-name/
sanj_cm_fan said:
Can I assume that on flashing cm11 fastboot package directly on top of the cm12s installation, it will screw sbl1 and aboot partitions and hence the brick?
Click to expand...
Click to collapse
You need first to empty those partitions, either by erasing the content of the partitions (sbl1, tz,rpm, and hyp) or formatting the partitions (cache, userdata, and system). I used to have "Nexus 4", and experience problem downgrading because the flash.bat does not erase or format previous partitions.
tirta.agung said:
I just wonder, how did actually those people really make their phone unrecognizable by windows.
Click to expand...
Click to collapse
@tirta.agung, having done just that to my Dad's YU Yureka last weekend, I can tell you it actually is fairly easy - how I wish it wasn't :crying:
All I did was to flash official CM11 rom using official an older copy of linux flash tools I had with me (they have removed the linux flashtools from YUPlayGod on github now, and I didn't bother to check any changes made to Windows tools - I now wish I had), powered-off the phone, never to see it wake it's beautiful screen again
I think one of the reasons (besides not erasing/formatting existing partitions) so many hard-bricked YU Yurekas (esp while downgrading to CM11) find a mention in these forums could be that "official" flash-all.bat at YUPlayGod github didn't flash 'hyp' partition till it was update on 21st Apr (please search for "commit 80dcc59d76 YUPlayGod" - I'm not allowed to post URLs yet). Missing an (apparently) critical partition while downgrading might make the kernel panic during boot-up.
Whether that has any direct bearing on the device being unrecognizable in Windows is something I wouldn't know yet - but surely my device is not getting recognized at all. No logs in "Device Remover" for Windows while connecting the device, no logs in 'dmesg' for Linux either. Only the red LED is lit (no continuous vibration as you've mentioned for a tell-tale sign of a device in QLoader 9008 Mode)
I also saw elsewhere you've recommended shorting some pins in the battery enclosure on handset to get Windows to detect the phone - if you can explain why you believe shorting them will help and then I'd attempt that as well.
Also, what's you opinion on the "theory" which says "partition sizes have been modified across CM11 and CM12"; ergo hence "the zip method" to downgrade is safer then flashboot because
Abhiram Shibu said:
When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone.
Click to expand...
Click to collapse
IMHO, if partition have really been re-sized, then there's not much you can achieve with either method (using 'zip' and 'flashboot' both shall be equally useless) unless there's some re-partitioning step/tool employed beforehand (quite like PIT files for Samsung devices). What is your opinion on this?
Need help..
I wiped all the 29 partitions that are present on Yu Yureka and now when I flash new ROM WiFi on my phone doesn't work also IMEI are wiped but I am.able to fix the IMEIs but not the WiFi and Hotspot issue. By 29 partitions I meant partitions including - sec, fsg, modemst1 modems2, ssd, panic, param etc . Guys help how can I fix my phone ?
Related
So after trying unsuccessfully to get RSD Lite to recognize my phone, I wanted to see if you guys could give me a little help. I want to flash back to stock JB so I started checking some other threads and this is what I came up with from the 4.1.2 xml file.
VRZ_XT907_9.8.1Q-94-1_CFC.xml
Code:
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash devtree device_tree.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cdrom cdrom
fastboot flash system system.img
fastboot erase tombstones
fastboot erase cache
fastboot erase userdata
fastboot reboot
If there is a specific order the commands have to run or if I'm missing anything, please let me know. Thanks guys.
So I tried it and it works perfect. Now I can go try some of JB bootloader only roms. Hope this helps someone out
Hi!
A few days ago I tried to flash the kitkat bootloader, bec. the lollipop one blocked my bootloader.
I used the official package but on mac, with the following commands:
./fastboot flash partition ./images/gpt_both0.bin
./fastboot flash tz ./images/tz.mbn
./fastboot flash sbl1 ./images/sbl1.mbn
./fastboot flash rpm ./images/rpm.mbn
./fastboot flash aboot /images/emmc_appsboot.mbn
./fastboot flash hyp ./images/hyp.mbn
./fastboot flash tzbak ./images/tz.mbn
./fastboot flash sbl1bak ./images/sbl1.mbn
./fastboot flash rpmbak ./images/rpm.mbn
./fastboot flash abootbak ./images/emmc_appsboot.mbn
./fastboot flash hypbak ./images/hyp.mbn
./fastboot erase boot
./fastboot flash modem ./images/NON-HLOS.bin
./fastboot flash system ./images/system.img
./fastboot flash cache ./images/cache.img
./fastboot flash userdata ./images/userdata.img
./fastboot flash recovery ./images/recovery.img
./fastboot flash boot ./images/boot.img
./fastboot flash persist ./images/persist.img
./fastboot flash splash ./images/splash.img
I've done it many times before without any problem, but now my mac turned off bec of a blackout and my phone only have a part of the bootloader, so it only do infinite vibration and my mac can't detect it.
Is there any solution for my problem???? Please help me!!!!!!!!! (and sorry for my bad english)
dabi01 said:
Hi!
A few days ago I tried to flash the kitkat bootloader, bec. the lollipop one blocked my bootloader.
I used the official package but on mac, with the following commands:
./fastboot flash partition ./images/gpt_both0.bin
./fastboot flash tz ./images/tz.mbn
./fastboot flash sbl1 ./images/sbl1.mbn
./fastboot flash rpm ./images/rpm.mbn
./fastboot flash aboot /images/emmc_appsboot.mbn
./fastboot flash hyp ./images/hyp.mbn
./fastboot flash tzbak ./images/tz.mbn
./fastboot flash sbl1bak ./images/sbl1.mbn
./fastboot flash rpmbak ./images/rpm.mbn
./fastboot flash abootbak ./images/emmc_appsboot.mbn
./fastboot flash hypbak ./images/hyp.mbn
./fastboot erase boot
./fastboot flash modem ./images/NON-HLOS.bin
./fastboot flash system ./images/system.img
./fastboot flash cache ./images/cache.img
./fastboot flash userdata ./images/userdata.img
./fastboot flash recovery ./images/recovery.img
./fastboot flash boot ./images/boot.img
./fastboot flash persist ./images/persist.img
./fastboot flash splash ./images/splash.img
I've done it many times before without any problem, but now my mac turned off bec of a blackout and my phone only have a part of the bootloader, so it only do infinite vibration and my mac can't detect it.
Is there any solution for my problem???? Please help me!!!!!!!!! (and sorry for my bad english)
Click to expand...
Click to collapse
same like me,
there's another way before take it to service center, please refer to http://en.miui.com/forum.php?mod=viewthread&tid=225276&mobile=2
I never doing thats, may help you
Thanks, I will try it
so I accidentally wipe everything including internal storage from TWRP. now everytime my device boot up it directly goes to the TWRP recovery. how can i flash rom again? :v
nelson_k said:
so I accidentally wipe everything including internal storage from TWRP. now everytime my device boot up it directly goes to the TWRP recovery. how can i flash rom again? :v
Click to expand...
Click to collapse
You connect to PC, mount sdcard with twrp and copy a rom from pc to your sdcard. Then install the rom within twrp.
strongst said:
You connect to PC, mount sdcard with twrp and copy a rom from pc to your sdcard. Then install the rom within twrp.
Click to expand...
Click to collapse
Helloo. I don't have sdcard neither otg. is there any other option? I've tried using adb sideload but still only boot to TWRP.
Go to twrp> Reboot> Bootloader
You'll then reboot into the fastboot mode.
Connect your USB-C Type cable and make sure that the device is connected.
Make sure that you have the stock COS 12.1 ROM in your adb folder and use these commands-
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata_64G.img
fastboot -i 0x2b4c flash persist persist.img
fastboot -i 0x2b4c flash system system.img -S 1G
fastboot -i 0x2b4c reboot
Take a otg and copy ROM and select file from twrp
moriyaprateek said:
Go to twrp> Reboot> Bootloader
You'll then reboot into the fastboot mode.
Connect your USB-C Type cable and make sure that the device is connected.
Make sure that you have the stock COS 12.1 ROM in your adb folder and use these commands-
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata_64G.img
fastboot -i 0x2b4c flash persist persist.img
fastboot -i 0x2b4c flash system system.img -S 1G
fastboot -i 0x2b4c reboot
Click to expand...
Click to collapse
Can someone please share system.img from the stock ROM for Zuk Z1? Thanks,
when i fix fastboot mode started with command:
fastboot flash aboot aboot.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase dbi
fastboot flash dbi dbi.img
fastboot erase laf
fastboot flash laf laf.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase rpm
fastboot flash rpm rpm.img
fastboot erase sbl1
fastboot flash sbl1 sbl1.img
fastboot erase tz
fastboot flash tz tz.img
fastboot reboot
i get "flash write failure"or failed to erase partition
why
can samone help me pls
Hence i was playing with fastboot commands i've tried the bunch of these commands and i'm not able to boot it but i've tried flashing in edl mode with the help of msm tool but it still doesn't works and it doesnt flash some partition. i can only access fastboot please someone can help with repartitioning of my device the list of fastboot commands that i've tried were ,
Now i don't know how to mount or what to do and this the only phone that i have with me
fastboot erase LOGO
fastboot erase abl
fastboot erase ablbak
fastboot erase apdp
fastboot erase bluetooth
fastboot erase boot
fastboot erase boot_aging
fastboot erase cache
fastboot erase cdt
fastboot erase cmnlib
fastboot erase cmnlib64
fastboot erase cmnlib64bak
fastboot erase cmnlibbak
fastboot erase config
fastboot erase ddr
fastboot erase devcfg
fastboot erase devinfo
fastboot erase dip
fastboot erase dpo
fastboot erase dsp
fastboot erase frp
fastboot erase fsc
fastboot erase fsg
fastboot erase fw_4g9n4
fastboot erase fw_4j1ed
fastboot erase fw_4t0n8
fastboot erase fw_8v1ee
fastboot erase hyp
fastboot erase hypbak
fastboot erase keymaster
fastboot erase keymasterbak
fastboot erase keystore
fastboot erase limits
fastboot erase logdump
fastboot erase logfs
fastboot erase md5
fastboot erase mdtp
fastboot erase mdtpsecapp
fastboot erase mdtpsecappbak
fastboot erase minidump
fastboot erase misc
fastboot erase modem
fastboot erase modemst1
fastboot erase modemst2
fastboot erase msadp
fastboot erase oem_dycnvbk
fastboot erase oem_stanvbk
fastboot erase param
fastboot erase persist
fastboot erase pmic
fastboot erase pmicbak
fastboot erase recovery
fastboot erase reserve
fastboot erase reserve1
fastboot erase reserve2
fastboot erase reserve3
fastboot erase rpm
fastboot erase rpmbak
fastboot erase sec
fastboot erase splash
fastboot erase ssd
fastboot erase sti
fastboot erase storsec
fastboot erase storsecbak
fastboot erase system
fastboot erase toolsfv
fastboot erase tz
fastboot erase tzbak
fastboot erase userdata
fastboot erase vendor
fastboot erase xbl
fastboot erase xblbak