yashsingh1/xdaforums huggingface dataset:
[YU Yureka General] Abhiram Shibu:
That is good question, I appreciate that.​

So.... I got to say is that. 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. The procedure you told will work.

But zip just copies these files to that location..... Sounds great, i think.

IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.

If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!

Zip method is always safe. I mean the safest!

Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!

So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....

Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......

Good Luck! :good:

I hope this information helped you

Please hit thanks if I helped you in any manner!
[YU Yureka General] sanj_cm_fan:
Rather than flashing your zip via recovery, can I not use fastboot to flash the following in the order mentioned:

modem, sbl1, aboot, rpm, tz, hyp, recovery. The files that would be used are a part of cm11 fastboot package. After flashing all of these, boot to recovery and then flash the cm11 zip. I'll be essentially doing the same like you did. But I'll be using fastboot to flash firmware specific stuff. I strongly believe that these would not cause the infamous brick.

Thanks,

Sanjay
[YU Yureka General] coolboyforeva:
2 questions :-

1. ) As you said that do not use the fastboot method to flash kitkat rom. My question is, Can i use fastboot method to flash the lollipop 64bit zip file (that is basically the same OTA update file), using same method which was used to flash kitkat (by extracting the zip file contents to a common folder containing flash-all.bat, if u remmeber?). Basically i want to know a method to re-flash lollipop 64 bit , if any1 knows?

2.) Once i suceed to get kitkat rom back , from the lollipop 64 bit. Can i use FASTBOOT method in FUTURE flashes to flash kitkat based custom roms or should i permanently DISCONTINUE flashing through fastboot, even after getting kitkat rom back by your method?

thanks in advance .... :good:

---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------

Also i want to know. is there something like 32bit and 64 bit recovery. I hv heard that flashing incoatiable recovery can also lead to hard brick.

which recovery to flash when.??

could be great if any1 has positive information and can guide....
[YU Yureka General] Abhiram Shibu:
There is nothing to be confused. there are 32 bit and 64 bit recoveries. Flashing wrong recovery will only softbrick your phone. I did it ones accidentally

32bit recovery https://drive.google.com/open?id=0B4etFrzyEA01d2VGRXNuY2I1MGs&authuser=0

64bit recovery https://drive.google.com/open?id=0B4etFrzyEA01NnZBWHcxWlVHTW8&authuser=0

If you want to flash lollipop then download lollipop flash-able zip file click here for zip file

There are some good working fastboot upgrade packages. So if you have one of them ( Tried it yourself to upgrade and worked earlier) Then use that package it will work!. Flashing with zip file with recovery reduces risk!:good:
[YU Yureka General] coolboyforeva:
ok . m not gonna use fastboot. But how will i flash signed lollipop zip file on custom recovery and unlocked bootloader. it wont boot. I would need an unsigned lollipop 64 bit zip file or rather a locked bootloader + stock 64 bit recovery . Any link for stock 64 bit recovery ? is above link for stock or custom recovery?
[YU Yureka General] Abhiram Shibu:
Yes it will boot.

Link above is for custom CWM recovery.

Warning ******** Boring Story Ahead*********

So i purchased my yureka from Amazon. When i got it, I unlocked boot loader, installed cwm recovery right away. When the lollipop upgrade showed up I tried to download it via system upgrade. It downloaded but wont flash because of a custom recovery. So... I downloaded a signed zip file from xda attachment which i gave you. I cleared cache and tried installing the zip file.... It actually works.

Why it worked?

Stock rom looks for signed zips and it should be signed my their developer. But custom recoveries installs any zip file which is flashable regardless they are signed or unsigned. The only thing it looks for is the scripts and device compactability.

So try flashing the lollipop signed zip file. It will surely work...

So... What will the zip file do?

It will wipe system, modem, recovery etc exept data. Resize them and copy files in.

So ... What will you end up with.

Obviously,

A locked bootloader ( Which when unlocked wipes data)

A stock old cyanogen recovery.

Non rooted CM12.....

So this means that if you want to be a power user you have to start form beginning. So... consider taking a nandroid backup before you upgrade.....

STEPS TO BACKUP DATA ON CYANOGEN 11

So... Abhiram I cant find my backup on sdcard

answer to this question is very simple. You know that your sdcard and app memory are same. So they created a new folder 0 and mounted as your sdcard.

So... How do you get that out....

There are 2 methords

Common step boot into recovery and connect your mobile to your computer. Make sure that ADB drivers are installed

Methord 1

Type

"adb shell

cp -r /sdcard/clockworkmod/ /sdcard/0/android/

adb reboot"

So after the phone rebooted. Open file manage ( anyone ) Browse into android folder in your sdcard, you will find your backup there. If you cant find your whole backup , the chances are you r running out of memory.

Methord 2

type

"adb pull /sdcard/clockworkmod/ %UserProfile%/documents/backup_from_nandroid/ "

Your backup can be found in c:/users/<your user name here>/documents/backup_from_nandroid/

So that is it....

So when you unlock boot loader you can copy this backup into your phone by....

1) Copy backup to adb folder

2) Type adb push <Directory name> /sdcard/clockworkmod/

Then do a advanced restore. Select data and restore

done!
[YU Yureka General] coolboyforeva:
Ok.. I want to revert back to kitkat. i wont be using fastboot to flash rom(only to flash recovery image). Is there anything else which i should avoid and keep in mind in order to prevent hard brick?? please suggest
[YU Yureka General] Abhiram Shibu:
Tips to avoid hardbrick.

Don't flash ROM via fastboot

Don't Format partition using fast boot

You can flash boot and recovery via fastboot.

You can do anything in recovery.

Advice backup ROM before you install kernel, or any zip files. That will help you if you soft brick your phone.

Hit thanks if I help you in anyway till now.
[YU Yureka General] ujilraj:
On reading the OP's comments another doubt occurred, Do i need to unlock bootloader all the time when switching between KK & LP? (Will the internal SD memory gets wiped all the time... Do i need to backup every data on the internal SD memory onto PC before switching from KK to LP & vice-versa?)
[YU Yureka General] Abhiram Shibu:
Yes, but in case of upgrading and unlocking boot loader

Nice Question

When you downgrade from CM12 to CM11 your data will be safe. Unlocking boot loader will not do anything with your data:angel:

But When you are upgrading from CM11 to CM12 your data will be also safe, but the problem occurs when you try to unlock boot loader It will wipe all of your data.:crying:

When we unlock boot loader in kitkat CM11 by using command fastboot -i 0x1ebf oem unlock

It doesn't ask for any confirmations.

But in case of CM12 when you unlock boot loader by using the same command, before wiping data, it asks for confirmation. ie It tells to push vol+ to confirm or push vol - to stop.

If you see like this. Fastboot is going to erase your sdcard.

Its a good practice to backup your data when you r playing with your phones firmware, It will help you get back your memorable moments, favorite music etc.

If you have an otg cable. Keep a pendrive for backup

So concluding in unlocking CM11 no data loss unlocking in CM12 there is data loss.

Good luck:good:​
[YU Yureka General] ujilraj:
One more doubt, suppose i'm on KK & want to upgrade to some custom CM12.x rom, do i need to go through the process of installing stock cm12 all the time, or do u suggest any other simple way to directly do the same?
[YU Yureka General] Abhiram Shibu:
Yes you r correct!

Yes you have to upgrade to lollipop by system upgrade or recovery ( Use a zip file ) or fastboot (Don't use it. as it is not safe)

Only after upgrading to lollipop you can use 64 bit custom roms.

If you try to upgrade, recovery wont probably allow you to....
[YU Yureka General] Abhiram Shibu:
Yes you r correct!

Yes you have to upgrade to lollipop by system upgrade or recovery ( Use a zip file ) or fastboot (Don't use it. as it is not safe)

Only after upgrading to lollipop you can use 64 bit custom roms.

If you try to upgrade, recovery wont probably allow you to....

If you r on 32 bit roms
[YU Yureka General] ujilraj:
Why cant we replicate the 64bit changes to boot area through custom rom/recovery installation? What really makes it only possible through stock LP upgradation?
[YU Yureka General] Abhiram Shibu:
It is possible

I will make a zip file for that! And be tuned I will post it within 2 days....
[YU Yureka General] Abhiram Shibu:
Here it is. A zip to convert 32bit to 64 bit.

Download https://drive.google.com/open?id=0B4etFrzyEA01UDlvVUpNaHJVTjQ&authuser=0

Flash it via custom 32bit Kitkat recovery

Reboot to fastboot mode ( If you face any problem reply)

Install 64 bit recovery.

Reboot into recovery.

Flash any 64 bit based or Android L ROMS

Enjoy Hit Thanks if i helped you!
[YU Yureka General] ujilraj:
Is there any possibility of hard bricking the phone? Did u personally check the above zip? Will try once u confirm it :)
[YU Yureka General] Abhiram Shibu:
Yes I tried it..... I always take risks
[YU Yureka General] ujilraj:
A simple suggestion, Why not change the title of the thread to "KK to LP, & vice-versa" or something like that & add the above posted zip to the first post along with instructions... It will be helpful to all the YU fans out there :)
[YU Yureka General] Abhiram Shibu:
OK... I will create a new thread and post this zip file there!

Thank you fro your informative reply.
[YU Yureka General] Abhiram Shibu:
So here it is the recovery files made flashable

Download https://drive.google.com/folderview...50NnZjZEdVTjNCWVVYSXIyUmxNazdOaGM&usp=sharing

Steps.

Flash "Back to CM11 signed by abhiram" or "32 bit to 64 bit". and do not reboot ( If you reboot you will have to flash with fastboot as recovery partition is not valid)

Suddenly flash the required zip file download

If helped you please hit thanks!
[YU Yureka General] actinium15:
Ummmm...I doubt if partition sizes for bootloader (and helper) partitions have changed across 64-bit Lillipop and 32-bit Kitkat.

Is there any way to retrieve sizes of bootloader partitions to confirm your assertion, perhaps by examining /dev/block/bootdevice/by-name/ via 'df/fdisk' across 32-bit Kitikat and 64-bit Lollipop devices?

I think the reason why so many people are observing hard-bricks while flashboot downgrades is the "diff" for flash-all.bat (commit 80dcc59d76) at YUPlayGod/factory-image-flash-tools on github

You'd note that in the "official" flash-all.bat, a critical partition named 'hyp' wasn't being flashed till 21st Apr. If you were to exit fastboot-mode with any non-system/non-data/non-recovery partitions in an inconsistent state, there's a good chance you'd get a hard-brick instead of a soft-brick.
[YU Yureka General] Abhiram Shibu:
If you want you can extact the zip and read the scripts in it. It just does the same thing. Flashes all the important files of your android device. Any way flashing zip file is safe beacause, it does not erase the whole partition table lol. It just puts file as it is. Do you remember there is a way to upgrade form KK to LP using flashing zip method. I just reverted it lol.

There won't be any hard bricks I promise if you do it correctly
[YU Yureka General] actinium15:
I did open the .zip file and I do understand what you intend to achieve, bro - and honestly kudos to RDS (from YUPlayGod forums) and you for compiling this .zip! This shall be useful to many...I just wish I had seen this before I hard-bricked my device...

My point was to understand "why" fastboot can brick, whereas '.zip' can't, a doubt tirta.agung. And this doubt is not specific to Yureka.

I was unable to appreciate how patching ".zip" via recovery is any safer than fastboot in case partition sizes have been altered. IMO, both the methods will fail identically in case of partition-size-modifications.

Also, I brought-up missing 'hyp.mbn' in official linux-flash-tools' flash-all.sh because I think that IS THE reason my device hard-bricked (after execution of flash-all.sh, all the partitions had running 32-bit kitkat images, except hyp partition which was still 64-bit lollipop, probably that's why the hard-brick). If the .zip file misses:

package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");

then IMO, even patching the .zip will hard-brick the device.

I'm mentioning all this so that it can be understood that while this particular .zip is safe (because it was personally tested by you and verified to be safe), just because a downgrade has to be patched via .zip (instead of 'fastboot') doesn't automatically make it "absolutely-safe".

Hope I was able to make my point clear.
[YU Yureka General] Shivam Kumar Jha:
code 1 will be used in recovery mode.. to extract files in folder 'firmware-update' to their respective partition..

code 2 is for fastboot method.. for same thing

bdw in fastboot method,, if you erase all partition and then flash the firmware, it will not cause hardbrick..

ive tested this thread methods 20+ times and it works very well...

http://xdaforums.com/yureka/general/guide-downgrading-to-kitkat-t3097176
[YU Yureka General] ravi00777:
stuck in bootloop after successfully booting first time

Hello abhiram sir

I successfully booted the cm11 followed steps you recommended

But to root my phone,I press power+vol.up+vol down to go recovery mode but my phone does not go into recovery and stuck into YU logo
[YU Yureka General] Abhiram Shibu:
Now you have to flash recovery through fastboot and flash stock cm11.

If you need any assistance you feel free to reply I will be ready to help you!
[YU Yureka General] smitkesaria:
Bro i have a doubt. Do i need to flash the back to cm11 zip by abhiram in stock cm12 recovery or custom cm12 recovery? And also what if after flasing the back to cm11 zip i flash cwm recovery based on 32-bit and then restore a cwm backup of kitkat... will this work??? Coz the android file host is too slow and stops every time at 80%. Thanks in advanced
[YU Yureka General] Abhiram Shibu:
Does it work? Ask other users. It had worked perfectly for me. You can restore the CWM backup of cm11 or you can flash stock ROM or any 32 bit ROM.

After flashing this zipfile using custom 64 bit recovery. You can flash recovery with your PC via fastboot.

Flash any 32 bit ROM after flashing. It is 100% working !. Dont forget to hit thanks if you found this useful!
[YU Yureka General] erparnavarora:
Abhiram Sir, YOU ARE A GENIUS... A BRILLIANT PERSON

I don't know what's that in back to cm 11 zip file... but it downgrade my device... i am very happy.. I WILL RECOMMEND YOUR METHOD TO EVERYONE... YOU ARE A GREAT MAN
[YU Yureka General] _Ghost:
Sorry if I am asking this question again. Do I need to be on stock cm12? And can I flash any KitKat recovery+rom after flashing the backtocm11.zip?

Also will ota updates work?

Thanks a lot..
[YU Yureka General] ShehZadaSaagAr:
help

did it worked in my yureka plus
[YU Yureka General] Abhiram Shibu:
Sorry not for Yureka plus.

Sorry I dont have yureka plus. Most of the developers say that roms and tools on yureka are not working for yureka plus. I suggest u don't flash it. There is no stock KK for Yureka Plus. If you are ready to take risks like me. Try it but I really discourage it. Tell me the result if you do so.:rolleyes:
[YU Yureka General] Garib Akbar:
Did you root your Yureka to do this process ?

Please reply...
[YU Yureka General] Saroj Kumar Mahato:
HELP PLZZ

Just need some info

Will flashing the Going to 64bit zip will remove my custom recovery currently installed & relock bootloader?

mean to say will i have no recovery after installing this zip??

Plz reply fast !
[YU Yureka General] Abhiram Shibu:
Yes it will remove recovery but won't lock bootloader
[ONE Q&A, Help & Troubleshooting] hiteshakanero:
I am on cos 12 17L and fed up of bugs !!

I want to install cm12.1 nightlies without losing app and app data !!!

Bootloader unlocked !!

Twrp installed !!

Please help

I am noob in flashing !!
[ONE Q&A, Help & Troubleshooting] SimonTS:
Is your device rooted?
[ONE Q&A, Help & Troubleshooting] hiteshakanero:
Yes its rooted !!
[ONE Q&A, Help & Troubleshooting] Heisenberg:
Just use Titanium Backup to backup your user apps, then after flashing the nightly you can restore your user apps again with Titanium.

Transmitted via Bacon
[ONE Q&A, Help & Troubleshooting] hiteshakanero:
Thanks
[Galaxy S6 Q&A, Help & Troubleshooting] dilgit:
The latest released roms for the G920F are OD9 and ODE.. Which of the two is better?

Who knows what are the differences between them?
[8125, K-JAM, P4300, MDA Vario ROM Development] ranasrule:
which one of WM6 ROMs posted here is the latest one ? Faria, Pandora etc etc ??? thanks in advance for your help
[8125, K-JAM, P4300, MDA Vario ROM Development] mattk_r:
Pandora is using 5.2.1413, however it's not "perfect". If you want a good one, stick to Xplore 2.0, Crossbow Reloaded, or Faria's setup. The bleeding edge ones might leave you just that...
[8125, K-JAM, P4300, MDA Vario ROM Development] b.mann:
mfrazzz's crossbow reloaded 1.7 i think
[8125, K-JAM, P4300, MDA Vario ROM Development] ranasrule:
thanks a bunch for your replies guys....i cant seem to find the thread about XPLORE 2.0 .....can someone point me in the right direction ?

also what kind of experiences have yoou guys had with WM6 ? is it worth upgrading from WM5 ?
[8125, K-JAM, P4300, MDA Vario ROM Development] cuboosh:
im actually going back to..

http://xdaforums.com/showthread.php?t=304876

i tried antc's 3.0 but there are a few issues with it.. so im flashing back to kick ass core 2.0n
[8125, K-JAM, P4300, MDA Vario ROM Development] WDS Josh:
Xplore 2.0 is the Core 2.0
[8125, K-JAM, P4300, MDA Vario ROM Development] mfrazzz:
:)

I won't go back to wm5. I stick with stable wm6 roms (as opposed to more bleeding edge ones) and while they all have quirks, I've found them more reliable than official wm5 releases and faster. Aku 3.3 was also very good but apps in those builds are getting dated.
[Galaxy S 5 Q&A, Help & Troubleshooting] guyrulz:
Can I just install a rock rom of g900f on the g900m or g900t?

I tried to install the visionx cfw on the g900m and it is based on g900t stock rom and it works flaulesly

the reason is on these models the language I use hebrew is removed entirely from the stock rom And more local 2 can't use this language because it does not exist

is it possible to add a language to the rom or just install stock g900f on any model?

Thank you
[Galaxy S6 Q&A, Help & Troubleshooting] AAANNNDDDYYY:
I have jailbroken many an iphone and ipod, and I have recently bought the S6. I am keen to root but it seems far more potentially troublsome, and far less straightforward, or maybe its just because I am learning for the first time.

I bought this in New Zealand from Spark. I assume it is locked?

Is the bootloader locked?

I couldnt find the matching build on Chainfire, Can this particular model be rooted?

Is there any guide to rooting? It seems all the information is spread out all over the place and no definitive guide and FAQ.

I can't even find the original stock rom.

Is rooting not similar to jailbreaking in the way it is done?

My specs:

Model: SM-G920I

Android: 5.0.2

Build: LRX22G.G920IDVU1AOD1

Thank you in advance.
[Galaxy S6 Q&A, Help & Troubleshooting] blud7:
I have the SM-G920I and it's rooted.

Rooting the G920I is apparently not as straightforward as others but still possible.

I had to flash TWRP via Odin, then flash the [BETA][2015.04.28] SuperSU v2.49 package via recovery.

Details when I get back from work, or some kind soul decides to help.

There is a stock image thread and a few stock roms floating around. Request / search lower down in that thread
[Galaxy S6 Q&A, Help & Troubleshooting] AAANNNDDDYYY:
Thanks, is it better to reset the s6 before rooting? For a clean root?

And about all the warnings about 'you do this at your own risk blah blah'. If you do everything properly how could you actually hard brick the device? If you do it properly the worst that should happen is a soft brick, in which case you just restore the phone and try again right?
[Galaxy S6 Q&A, Help & Troubleshooting] d0ce:
Here is my experience, a fellow kiwi on Spark (with a 2D branded phone). I too have the 920I running on A0D1 via OTA.

It is unlikely Spark firmwares have locked bootloaders.

So long as you can get to download mode (holding volume down, home and the power button for up to 10 seconds), you can bring your phone back to life if something goes wrong . You will want a copy of Spark's firmware handy before you start, you can get it from here . Just in case.

Use the USB cable that come with your phone and make sure you have the drivers installed.

Any ways, first I flashed TWRP via Odin (through download mode Andy), flash was successful, however booting into recovery hung my phone. Managed to get back to download mode from there and flashed CF-Root for 920I. Boot loop.

Back to download mode and flashed CF-Root for 920F. Success, rooted and booted. Andy, if all you are looking for is root, avoiding the TWRP flash may work and going straight to CF-Root. Others have had issues with this, I'm not sure. I'd try the 920I first and if no good try the 920F. Again, as long as you can get to download mode, you can flash Sparks firmware through Odin to restore it to stock. Good luck and remember, attempting any of this WILL trip KNOX. If your using this as a company phone, you will run into issues. Can't imagine we will see Samsung pay any time soon in NZ.

For those interested in TWRP, after the root was obtained, my recovery was still busted. I flashed the TWRP image via Flashify and now I have also have TWRP. Good times.
[Galaxy S6 Q&A, Help & Troubleshooting] AAANNNDDDYYY:
Thanks mate, it all seems quite confusing, makes me want to go back to Iphone hahaha. I am not a dev, I just like the freedom to be able to do whatever I damn well please on my phone that I paid for.

This tutorial the way to go?

youtube.com/watch?v=BW5P8zqkFpY