Related
Please
I tried several times to ask on this forum if someone can help me, but no luck so far i am verry desperad now
I have install Skrilax CZ bootloader V8 on my tab, but thats all i dont now what i need to do now to install a custom rom, i have put the update file in to the sd kart but it wont install.
I have this option only
option
Reboot
Fastboot Mode
Boot Primary Kernel Image
Boot Secondary Kernel Image
Boot Recovery
Set Boot Secondary kernel Image
Set Debug mode on
Wipe Cache.
So cany anyone tel me what i must do to root and install CWM recovery
so i can install then after custom roms?
Is ther no tutorial from heren to folow!!
Please don't double post it gets confusing -
remember, this is the holiday season and alot of us are having a break and spending time with our long neglected family members, we can't be around here as much as we would like....
Yes there are guides on using fastboot, skrilax's bootloader thread for one...
PLEASE don't flash an update.zip it doesnt work that way, you'll end up stuck again
you should read the first 2 guides linked in my sig..
I too need help exactly on this point
I have not the slightest clue what to do and i do not think this is a duplicated post.
I spent days to come at this point and i don't want to **** things up.
I red your posts dibb_nz and it just gets more confusing
You write in this post :
PLEASE don't flash an update.zip it doesnt work that way, you'll end up stuck again
and then you write here: http://forum.xda-developers.com/showthread.php?t=2049778
Have your Custom Rom downloaded and copied to your External SD Card ready to install immediatelyafter flashing skrilax's patched bootloader
So is it too hard for someone to tell what to do here to install a custom rom ?!
P.S. I also got [ ERROR: Invalid primary (LNX) kernel image ] on my screen.
http://s15.postimg.org/e02avn6aj/IMG_0020.jpg
something to worry about ?
Thread closed, duplicate of this one:
http://forum.xda-developers.com/showthread.php?t=2076510
ONE Click Warranty Back
hello Friends This My First Thread on G 2014(Titan)
Now Get Yours Warranty Back In just one Click
No need to rememberer all this such big commands of FastBoot
i gonna present the simplest way to revert back to stock official Roms with both locked and unlocked Boatloader(after flash) which r Provided in the below links
Pls do press thanks If u really liked my work i need it :good:
best simple way in simple one click (action performed)
!!Disclaimer!!
NOTE: I am not responsible for any kind of boot-logo, corrupt partition,bricked devices, dead SD cards,other Issue etc As I am just new to android developing
This process have been tested personally on my device moto g 2104
NOTE :This Will wipe all your data so pls take all yours useful databackup
INSTRUCTION
1) Download and install the Basic Moto Drives in this http://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97326/p/30,6720,9050
2)Download the required Official Firmware(KitKat,Lollipop) form here https://mega.nz/#F!Q9YHCQzY!dgyvAJ8eNA3t7az4vizwOQ which i have taken Through Original Motorola Firmware Collection[Thread] thanks to @gregor160300
all the Firmware are Official images and are uploaded Recently
3)Download the OneClick Tool zip according to yours need a(locked) and b(Unlocked) form Here
a)restore with locked Boatloader Here https://drive.google.com/open?id=0By-2WiK-9wJqfmlMT3BoMmxqakU0M0lJdDk0OGF3UmVJZWN5eW90a0pIdUtSU3BRb0pxbms
b)restore with unlocked Boatloader Here https://drive.google.com/open?id=0By-2WiK-9wJqfktRWG1wbFJ6S2JnLU5FTFBNUWp2ckRZWnZmMUVfV1hiX3JjUGw0am1LR2s
4)Now Extract the Firmware zip to a Particular Folder at your given location on your PC/Laptop
5)After That Extract the OneClick zip to a Same Folder (Where U have the Extracted the Firmware Files)
6)Boot your Moto G 2014 into FastBoot Mode and plug your Device into your computer (pls Make sure u have all the proper device drivers are installed)
6)Finally Go To the Extracted Folder and u will see OneClick .bat file just click on OneClick
U r done Njoy till its gets Completed
All the Firmware are Official images Your warranty may not Void also u may get Yours Warrenty Back
hope u Enjoy this
PLS DON'T MIRROR THE LINKS
sry for my bad english i will improve
special Thanks to both @ archies20 @gregor160300,Shawn5162 for their thread:laugh::laugh:
Please Do press Thanks button if u really liked My Work i really need it :good:
It's For Indian Version ?
yes u can check this according to the indian baseband
Tried it today and it worked flawlessly, thanks!
heeey thanks 4 the reveiw hope i will come with other thread
so hey guys. i have a moto g 2014 xt1068 dual sim variant. for some reason after unlocking bootloader, flashing TWRP, and flashing an other ROM(blisspop 5.1.1) for some reason my first sim card slot was like not working at all and my second sim doesnt have mobile data only calls. So I flashed stock firmware 5.0.2(RETAILDSDSALL_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml) but the problem still exists. I dont know what to do :'( any help?
Mike20017 said:
so hey guys. i have a moto g 2014 xt1068 dual sim variant. for some reason after unlocking bootloader, flashing TWRP, and flashing an other ROM(blisspop 5.1.1) for some reason my first sim card slot was like not working at all and my second sim doesnt have mobile data only calls. So I flashed stock firmware 5.0.2(RETAILDSDSALL_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml) but the problem still exists. I dont know what to do :'( any help?
Click to expand...
Click to collapse
Change both sim slots?
do a clean Install make a try if still not working change the baseband version and check out again if still not working den hope a hardware fix will resolve it
Hello,
First things first: thanks for this great tool! I needed to restore the original firmware and didn't know how to do that. With this tool it's quite simple.
I had only two small problems:
- the first time I've run tour .bat file I seen several commands being executed, all of the m with an OK in the end, but after all process the phone didn't boot, no recovery also. I ran the .bat file a second time and it's OK now.
- another strange thing happened: the boot logo screen reverted to the "unlocked bootloader" screen.
A question: can I flash only the bootlogo screen via adb?
Moto bootloop struck help help
Hello can any senior member plz help me out.
I have unlocked and rooted moto g2 2014 mobile it was working fine.
But I done a stupid thing by editing system file and overwriting it.
Then my phone stuck in boot loader
I can access recovery TWRP i tried to wipe Delvic and cache and factory resetting but it did'nt worked.
Therefore buy following the link i tried to flash with orginal frimware
www droidviewsmoto g 2014 to stock and lock the bootloader
it was not successful again it strucked in boot loop with Android dead symbol in recovery
------>> Then tried to install TWRP recovery it was successful, but unable to install super user.
There fore I tried to repeat the process buy using both sdk windows platfom tools and vfastboot
buy typing command in cmd as mfastboot.exe oem lock begin
and noticed error saying
hab check failed for boot
failed to verity hab image boot
failed to validate boot image
Plz sir can any one help me out plz
yes
yes u can using the img file
follow this instructions to remove the warning instruction
http://www.bhudroid.com/2015/08/remove-unlocked-bootloader-warning-on.html
Kindly First Update yours boot loader Version
Kindly First Update yours boot loader Version
this can be the an issue
and after that cleanly flash the latest TWRP recovery
and Finally any Latest Build Custom Rom
this may Works
Marcelo_RJ said:
Hello,
First things first: thanks for this great tool! I needed to restore the original firmware and didn't know how to do that. With this tool it's quite simple.
I had only two small problems:
- the first time I've run tour .bat file I seen several commands being executed, all of the m with an OK in the end, but after all process the phone didn't boot, no recovery also. I ran the .bat file a second time and it's OK now.
- another strange thing happened: the boot logo screen reverted to the "unlocked bootloader" screen.
A question: can I flash only the bootlogo screen via adb?
Click to expand...
Click to collapse
yes u can using the img file
follow this instructions to remove the warning instruction
http://www.bhudroid.com/2015/08/remove-unlocked-bootloader-warning-on.html
Kindly First Update yours boot loader Version
sudheerkk87 said:
Hello can any senior member plz help me out.
I have unlocked and rooted moto g2 2014 mobile it was working fine.
But I done a stupid thing by editing system file and overwriting it.
Then my phone stuck in boot loader
I can access recovery TWRP i tried to wipe Delvic and cache and factory resetting but it did'nt worked.
Therefore buy following the link i tried to flash with orginal frimware
www droidviewsmoto g 2014 to stock and lock the bootloader
it was not successful again it strucked in boot loop with Android dead symbol in recovery
------>> Then tried to install TWRP recovery it was successful, but unable to install super user.
There fore I tried to repeat the process buy using both sdk windows platfom tools and vfastboot
buy typing command in cmd as mfastboot.exe oem lock begin
and noticed error saying
hab check failed for boot
failed to verity hab image boot
failed to validate boot image
Plz sir can any one help me out plz
Click to expand...
Click to collapse
Kindly First Update yours boot loader Version
this can be the an issue
and after that cleanly flash the latest TWRP recovery
and Finally any Latest Build Custom Rom
this may Works
thnks .......
woow its working great . very simplest way thank u so much
bhu999 said:
heeey thanks 4 the reveiw hope i will come with other thread
Click to expand...
Click to collapse
Can I get OTA update after this ?
I just want to know can I get OTA update after this if Motorola roll out any update in the near future.
mudit56 said:
I just want to know can I get OTA update after this if Motorola roll out any update in the near future.
Click to expand...
Click to collapse
Yes
woow...
wow its working great for me... very simply to use ... am not face any bugs.......... thanks for your work:good:
@bhu999 Thanks it worked awesome.
one question can i get official OTA update from Motorola if i root my device now ??? Because for rooting custom recovery is required and it is impossible to get OTA while on custom recovery. Right ??
yes u can but with stock recovery
just flash the stock recovery to get the available update also
In One Click method u can get the official available update after completing the whole procedure
Hello, guys this is my first post but i am quite sure that my methods work.If there any problems then u can surely ask in the section below. This thread will be a GUIDE TO ROOT AND INSTALL CUSTOM RECOVERY FOR MOTO G 1st Gen users.
Some prerequisites are:
1. Motorola drives (https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481)
2.Fastboot and recovery files (https://www.dropbox.com/sh/9jf2va51ffg0pzq/AAAxDT-ETf7AESIcHGnfEgv7a?dl=0)
[ Let these files be downloaded and kept in Cdrive of ur pc and and place them on the desktop.. Please name this folder MOTO FILES]
3. SuperSu files https://download.chainfire.eu/696/supersu/ and[/url] paste it in ur phones internal memory and please do this after unlocking the bootloader cause bootloader unlocking will delete everything so its better to do it after unlocking bootloader
Download these files and ur done... Now lets continue to the fun part
This process involves three very simple steps :
1. Unlocking the Bootloader:-
This process is infact very easy to do. There are several guides on the internet regarding this process but the one that i suggest is by High On Android/ Max Lee . Follow his method and u can very easily unlock ur bootlader. Copy this url and see it for urself fellow guys...http://highonandroid.com/android-smartphones/how-to-unlock-bootloader-on-motorola-android-smartphone
2. Erasing ur previous recovery and installing a new one and rooting ur phone all in one process
Some users have been reporting that even after installing custom recovery , whenever they go into recovery they enter into stock recovery. The actual problem is that the stock rom of the Moto G rewrites over the new custom recovery installed.
So we have to install the recovery actually twice but it only takes a few minutes
i) Firstly be sure to have lots of juice in your phone
ii) Boot ur phone into the bootloader by power offing ur device and then pressing the volume down and power button together for 10 seconds and then leaving both of them together.
iii) Now connect ur device to ur pc/laptop
iv) Now open a cmd and enter the following commands(press enter after every command)
- cd Desktop
-cd MOTO FILES
-fastboot flash recovery Recovery2.img
-fastboot reboot-bootloader
[MAKE SURE NOT TO REBOOT UR DEVICE ]
v) Now ur phone has custom recovery installed in it and u shud now enter into recovery mode by choosing the option from the bootloader, by pressing volume down and then volume up while in bootloader mode.
vi) This will open the Philz recovery that i have provided with. I prefer the philz recovery over the cwm one. Now go on and install the SuperSu update zip file. And BOOM ur Device is now rooted !!!!.
vii) Now reboot ur phone and u must install
-ROOT CHECKER (to check root)
- and most importantly ROOT EXPLORER
viii) After following step (vii), now if u try to go into recovery, u will be booted to stock recovery. So to prevent that use the ROOT EXPLORER app and go to the root \system\etc and delete the file named install-recovery.sh .
ix) After deleting the file u will once again have to follow step (iv) and install custom recovery this will ensure u having custom recovery even after rebooting ur device and u will have ROOT access as well
On which android version , were you on before rooting . 5.01 or 5.1 .
This method works for both 5.1 and 5.01
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Is the first post too heavy for you?!
Follow the steps and be happy.
Gesendet von meinem Moto G mit Tapatalk
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Andus1988 said:
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Click to expand...
Click to collapse
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Ajay P said:
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Click to expand...
Click to collapse
whats the problem u facing ?
sanilch99 said:
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Click to expand...
Click to collapse
It could cumber the inbuilt root!
sanilch99 said:
whats the problem u facing ?
Click to expand...
Click to collapse
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Ajay P said:
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Click to expand...
Click to collapse
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
sanilch99 said:
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
Click to expand...
Click to collapse
Thank you
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
notuger said:
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
Click to expand...
Click to collapse
I will recheck that super su. file and make sure its perfect... Thanks for the response:good:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Works but could be simplified
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
issam029 said:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
i have edited the previous link and given the new one. You can use this SU file. It will solve ur prob.
pcgardner said:
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
Click to expand...
Click to collapse
Reinstallation of custom recovery is not must its just for safety precautions and I have finally updated the SuperSu link. As far as Busybox u will have to install it customly only.
issam029 said:
once i finished steps all, when i open supersu, popup window says, "there is no su binary installed, and supersu cannot install in it. This is the problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
If i check with root checker,
sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
use the new su files i updated the link
facing problem after unlock bootloader mood for moto g 1st gen
Thanks a lot for your information...:good:
Bro!! I have already unlock bootloader mood.. Before rooting is it necessary to clear all data & app...??
Info :
Greetings and Welcome. Here's the latest firmware update for Sony Z2(D6503) Build23.5.A.1.291_R4D with (Recovery + Root)
Enjoy!
How To Flash :
Method 1 Clean Flash :
1. Download Prerooted Rom + Bootloop Fix and place them on ur device storage,
2. Reboot to Recovery,
3. Do A Full Wipe Except the storage partition where u put Prerooted Rom + Bootloop Fix,
4. Flash Prerooted Rom and then Bootloop Fix
5. Reboot.
Method 2 Dirty Flash Over Previous Build Of Android MM :
1. Download Prerooted Rom + Bootloop Fix and place them on ur device storage,
2. Reboot to Recovery,
3. Flash Prerooted Rom and then Bootloop Fix,
4. Wipe Cache And Dalvik/Art
5. Reboot.
6. After Finishing booting process wait a few mins,
7. Now go to app drawer and check if supersu is there or not, If not then simply download it from google play store and install it and open it and select SU Binary install normal & Click Reboot,
8. Enjoy!
Stuff Used to Create This Pre-rooted Room :
D6503_Customized AU_1281-9715_23.5.A.1.291_R4D
PRFCreator_v1.3
UPDATE-SuperSU-v2.76-SYSTEMMODE
RecRootV4_combined
My Dell Laptop,
A Keyboard + Mouse,
My Experiences With This Build Of Android MM :
Now We can transfer apps to "EXTSDCARD" using "Transfer data to SD card"
STAMINA mode is back
Multi Tasking Is better than Previous Build Of Course XD
Significantly faster & smoother than previous build (23.5.A.0.575)
Screen Recording Error still exist
Anything Else? :good:
Download Links :
Rom : Click On ME
Bootloop Fix : Click On ME
Screenshots :
http://imgur.com/a/i7icA
Instead of Typing Thanks, You can simply press on it :good:, Try not to spam this thread, If u have any Question regarding my upload Ask here.
First Comment
Keep Up Bro (Y)
Thank you. ?
Thanks!
I'll try to build the same file but for Customized FR (my country) !
Why bootloop fix from 570 build need to flashed too ?
Sent from my D6503 using Tapatalk
itsnie said:
Why bootloop fix from 570 build need to flashed too ?
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Because that's a life saver for Z2 with Prerooted rom. That's the only bootloop fix exist here on xda for now. Can you try flashing without it at see if it boots? And report back here! Unless u wanna waste some times on re-flashing LP rom and rooting it again to get back on a rooted mm rom
Will previous D6502 patches work?
RICdefeat & byeselinux
Have you used byeselinux & RICdefeat in the firm compilation??
Or only the bootloopfix?
Thank you
supercfc said:
Will previous D6502 patches work?
Click to expand...
Click to collapse
Can't say since I don't have a D6502 Model. Try and let me know if it works
LunaFree said:
Have you used byeselinux & RICdefeat in the firm compilation??
Or only the bootloopfix?
Thank you
Click to expand...
Click to collapse
"RecRootV4_combined" Include all of those stuff as well as recovery
@op
Will dummy_flashable.zip works as well making the ZIP? im on .575 with root and recovery. i have already downloaded the ftf before seeing this post
Thank you so much!!!!
So I finally made the same thing for the french firmware !
https://www.wetransfer.com/downloads/9d69b9f8a30da16970abc3f5655fa01720160804144653/d99f41
Dilesh Perera said:
@op
Will dummy_flashable.zip works as well making the ZIP? im on .575 with root and recovery. i have already downloaded the ftf before seeing this post
Click to expand...
Click to collapse
As I already said "RecRootV4_combined" Includes Root + Recovery. So u don't need anything else. Except Bootloop Fix
rakeshbro said:
"RecRootV4_combined" Include all of those stuff as well as recovery
Click to expand...
Click to collapse
I've do my compilation with 23.5.A.1.291 firmware using the ITALIAN customized and SUPERSU with PRF creator.
I've install busybox from appstore and DUAL recovery with the install.bat from pc and then in RECOVERY MODE i´ve flashed byeselinux+RICdefeat without bootloopfix, and works too!!
Thank you Rakeshbro!! :good::good:
LunaFree said:
I've do my compilation with 23.5.A.1.291 firmware using the ITALIAN customized and SUPERSU with PRF creator.
I've install busybox from appstore and DUAL recovery with the install.bat from pc and then in RECOVERY MODE i´ve flashed byeselinux+RICdefeat without bootloopfix, and works too!!
Thank you Rakeshbro!! :good::good:
Click to expand...
Click to collapse
Yeah I saw some feedback on "23.5.A.0.575" build as well that some ppl didn't flashed bootloop fix and they got it boot.
But for me I'd to flash bootloop fix to get into os. I remember Last time when I was on MM build "23.5.A.0.570_R4D" I've like 350+ apps installed on my z2 and after a few weeks later Build "23.5.A.0.575" came out. And guess what I've flashed it without the bootloops fix and that's it, I got stucked on lockscreen and whenever I unlock my device it just reboot again & again, And I can't even boot to recovery. With a broken heart I've to flash LP rom again and root it and then flash the latest MM build. I just did't want to take that risk again this time, since I've now more than 360+ apps installed on my Z2. So It's upto All of u guys. U want to flash the old bootloop fix or not. Try and let us know Good Luck!
Yeah you need bootloop fix. The same thing happened to me but I just pressed volume button during the bootloop, I entered TWRP, connected to USB, copied bootloop fix and flashed it without reinstalling everything
rakeshbro said:
Yeah I saw some feedback on "23.5.A.0.575" build as well that some ppl didn't flashed bootloop fix and they got it boot.
But for me I'd to flash bootloop fix to get into os. I remember Last time when I was on MM build "23.5.A.0.570_R4D" I've like 350+ apps installed on my z2 and after a few weeks later Build "23.5.A.0.575" came out. And guess what I've flashed it without the bootloops fix and that's it, I got stucked on lockscreen and whenever I unlock my device it just reboot again & again, And I can't even boot to recovery. With a broken heart I've to flash LP rom again and root it and then flash the latest MM build. I just did't want to take that risk again this time, since I've now more than 360+ apps installed on my Z2. So It's upto All of u guys. U want to flash the old bootloop fix or not. Try and let us know Good Luck!
Click to expand...
Click to collapse
I think we have do the same, but i dont use the bootloop fix...
I will flash recroot v4 next time without bootloop fix and i tell you. Thank you!!
Thanks for your work
flashing without a probleme
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app