Hi
I have bricked my Note after flash new CM9 from XpLoDWilD.
It was in CyanoFree ROM with LP6 modem.
I wipe factory/reset/cache/david
Flash CM9 ver 2
Flash Gapps date 20120429
I think LB2 modem is better as showed on XpLoDWilD screen capture, so plash it.
Wipe again (as XpLoDWilD instruction)
Dead ...
Everything right now completely no react.
the instructions was (even mentioned in the discussion threads) to flash from a GB kernel.
you did not follow instructions, it's your fault.
yeah we assume you flashed from a GB kernel and NOT a leaked ICS kernel..
praetorius said:
the instructions was (even mentioned in the discussion threads) to flash from a GB kernel.
you did not follow instructions, it's your fault.
Click to expand...
Click to collapse
I posted it here is not for penalty, Just for people warning
Think that the ROM have problem because it's not just easy to brick the phone by wipe data.
I read that it's very risky to do a wipe with a leaked ics kernel and can burn your emmc.
Maybe if you had followed the instruction your phone will be ok now.
{
"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"
}
beckend said:
MOD EDIT: Quote Removed, for reasons highlighted below
Click to expand...
Click to collapse
guys.....
although OP (perhaps) caused brick by himself, it's not nice to be "glad u bricked"!
just be polite and professional, hint him at his fault with a smile, but not this way!
br
Q2V said:
I posted it here is not for penalty, Just for people warning
Think that the ROM have problem because it's not just easy to brick the phone by wipe data.
Click to expand...
Click to collapse
No, CM9 doesn't have a problem, the kernel you wiped with has a problem.
There's a reason the instructions specifically told you NOT to flash from an I9220 repacked kernel in red text. But you did it anyway.
The ICS leak kernels are notorious for doing exactly what happened to you, which is why you were told NOT to flash from them.
OK...so I was trying to read all the pages and took from it this... I'm on cyanofree...
Boot to recovery...flash abyssnote kernel 4.2...reboot into recovery...full wipe...wipe cache. Advanced wipe dalvik. Install zip from SD and flash cm9. So that's what I set out to do. But I got as far as flashing abyssnote kernel and rebooting into recovery...
...recovery keeps flashing the screen and rebooting back to recovery...buttons are unresponsive ie. Volume for up and down...altho occasionally register a press...and it won't boot either...stalls after boot animation...maybe I flashed the wrong kernel but it was from dev section. Or maybe I did the wrong process. .. or maybe the process has this tendency. Can anyone shed any light? Sorry if I missed something obvious ....
I posted in cm9 section also sorry. Just checking in here
Edit : I understand instructions said to do another way but I guess this is a lesson to others following the thread and what others have done won't necessarily work for you. Follow the clear instructions instead of "yeah it worked for me" methods
Sent from my GT-I9100 using xda premium
Don't care. This happens when you don't read.
But this is an effective way to get rid of the noobs here. Just write an install guide that's longer than 3 lines, and voila! They won't read and then they're gone. Phone is dead.
Sent from my GT-N7000
NOZdroid said:
OK...so I was trying to read all the pages and took from it this... I'm on cyanofree...
Boot to recovery...flash abyssnote kernel 4.2...reboot into recovery...full wipe...wipe cache. Advanced wipe dalvik. Install zip from SD and flash cm9. So that's what I set out to do. But I got as far as flashing abyssnote kernel and rebooting into recovery...
...recovery keeps flashing the screen and rebooting back to recovery...buttons are unresponsive ie. Volume for up and down...altho occasionally register a press...and it won't boot either...stalls after boot animation...maybe I flashed the wrong kernel but it was from dev section. Or maybe I did the wrong process. .. or maybe the process has this tendency. Can anyone shed any light? Sorry if I missed something obvious ....
I posted in cm9 section also sorry. Just checking in here
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Try one of the Gingerbread CF-Root kernels
Entropy512 said:
Try one of the Gingerbread CF-Root kernels
Click to expand...
Click to collapse
I'm prob too noob to tell if ur having a dig or not ha. But yeah thanks I will. Appreciate your efforts
Few days without my note til I get access to a computer for Odin lol
Sent from my GT-I9100 using xda premium
Entropy512 said:
No, CM9 doesn't have a problem, the kernel you wiped with has a problem.
There's a reason the instructions specifically told you NOT to flash from an I9220 repacked kernel in red text. But you did it anyway.
The ICS leak kernels are notorious for doing exactly what happened to you, which is why you were told NOT to flash from them.
Click to expand...
Click to collapse
No, again (for people pay more attention on flash this CM9 ROM):
- I dont flashed any repacked i9220 ROM, also dont flash any Kernel.
- The problem is i have full wipe after flash the CM9 -> will make brick
- Flash Gapps, Modem, wipe cache .... is safe
As normaly, all other ROM is just request full wipe, wipe cache before flash the new ROM at all, but, because this ROM is another, request make this again after flash the ROM, my mistake is do the full wipe, so pls, pay attention because this is easy make a mistake and expensive!
Q2V said:
No, again (for people pay more attention on flash this CM9 ROM):
- I dont flashed any repacked i9220 ROM, also dont flash any Kernel.
- The problem is i have full wipe after flash the CM9 -> will make brick
- Flash Gapps, Modem, wipe cache .... is safe
As normaly, all other ROM is just request full wipe, wipe cache before flash the new ROM at all, but, because this ROM is another, request make this again after flash the ROM, my mistake is do the full wipe, so pls, pay attention because this is easy make a mistake and expensive!
Click to expand...
Click to collapse
we did read as per your original post
I have bricked my Note after flash new CM9 from XpLoDWilD.
It was in CyanoFree ROM with LP6 modem.
I wipe factory/reset/cache/david
Flash CM9 ver 2
Flash Gapps date 20120429
I think LB2 modem is better as showed on XpLoDWilD screen capture, so plash it.
Wipe again (as XpLoDWilD instruction)
Click to expand...
Click to collapse
This means you're on a leaked ICS kernel because thats the only way you were on CyanoFree..
You skipped the step
FLASH A GB KERNEL should have been step one.
among noobs they can be confused..and maybe the CM9 thread should maybe be a bit more noob friendly as in saying.
IF you have any other ICS rom downgrade to GB before flashing to the real CM9 ie downgrade via Odin and flash the pit + repartition..that way you know for sure that you are in a clean state
just my 1.3c
Bricking your device is A real pain. Thanks for the heads up and hope you get back your device soon with minimum loss
Sent from my GT-N7000 using XDA
MrDSL said:
we did read as per your original post
This means you're on a leaked ICS kernel because thats the only way you were on CyanoFree..
You skipped the step
FLASH A GB KERNEL should have been step one.
Click to expand...
Click to collapse
No, i was in LP5 kernel
Edit: yes, youre right, LP5, LP6 is leak i9220 kernel!
Q2V said:
- I dont flashed any repacked i9220 ROM, also dont flash any Kernel.
Click to expand...
Click to collapse
WRONG. You were on Cyanofree which uses a repacked I9220 kernel.
Yet you ignored the CM9 instructions and flashed directly from it anyway.
Q2V said:
No, i was in LP5 kernel
Click to expand...
Click to collapse
It doesnt matter they are BOTH LEAKED kernels..
Dude you didnt follow insturctions!! period!!
I am sorry YOU bricked your device because YOU didn't follow instructions but next time READ before you do something and this wont happen...
Also change your title of this thread because CM9 is NOT the cause of this brick..
anilisanil said:
Bricking your device is A real pain. Thanks for the heads up and hope you get back your device soon with minimum loss
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Checked with Samsung service, it cost about 300$ for mainboard replacement.
I dont have local warranty because i bough it from abroad.
Related
Before you read any further:
This thread will not discuss fixing Download Mode on effected mobile phones.
This thread will not discuss any method on flashing bootloaders only.
This thread will not discuss anything beside bootloaders of XXJVK and why they are needed in some cases.
Please keep the thread clean and stay on topic, thanks
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Why did I write this:
I have been across many threads, including the XXJVK firmware thread, and I did read many posts by members asking on which firmware to flash, if it should be the one with bootloaders included or the one without.
I did also find a post telling our members to flash the bootloaders only and not the whole firmware.
I would like to clear some things up for our members and why there is 2 versions, one with bootloaders and one without bootloaders.
Why 2 versions:
If you flash the firmware without bootloaders when your device have been running only Froyo and have not flashed the Gingerbread beta XWJV1 before, then your device is still using the old bootloaders and you will notice the followings:
* Graphics corruption during boot.
* The device will not be able to enter Recovery Mode.
Just to make it easy to understand, please look below:
XXJVK firmware with-out bootloaders + Froyo/Eclair bootloaders on device = Graphics/Screen corruption + Can't enter Recovery Mode
XXJVK firmware with-out bootloaders + XWJV1(GB Beta) bootloaders on device = OK!
XWJV1(GB Beta) firmware with-out bootloaders + XXJVK bootloaders on device = OK!
Froyo firmware with-out bootloaders + XXJVK or XWJV1(GB Beta) bootloaders on device = OK!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
After the device has been updated to the new bootloaders by flashing the firmware with bootloaders, then it will work with any firmware, and you don't have to flash the firmware with bootloaders again, this is why there is 2 versions, because bootloaders flash can be risky, the package that does not include bootloaders is for those that have already flashed a full XWJV1 or a full XXJVK with bootloaders included, may need/like to re-flash, or for those that only want to try the new firmware.
Why not flashing bootloaders alone:
Flashing bootloaders is risky, this is why when the XXJVK with bootloaders has been repackaged then it was repackaged so 2 files will be flashed prior to bootloaders, so if there is a bad connection between the PC and the phone or with Odin by any chance, then Odin is far from touching boot sectors, and by that a member can have a good flash even while flashing a full firmware with bootloaders included.
I don't advice to flash bootloaders only, if there is a bad connection or Odin hangs by any chance, then you have nothing but a paper-weight nice-looking-dead-device on your desk.
My question is: Do you see any thread or a post in this forum that stats a bricked or a dead device after 16000+ downloads and then take the risk of flashing bootloaders only?
{
"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"
}
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Note:
This thread is not intended for showing or discussing methods on how to flash bootloaders only, but about informing the members of the new bootloaders and what firmware XXJVK version to choose and why.
If you plan to discuss other methods on flashing bootloaders then make your own thread where you can take responsibility for it.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@Ramad, thanks for this information. Do we know for certain whether Samsung have 'locked' these new bootloaders like they did with the Galaxy Tab ones or can you flash back to a 2.2.1 Rom with no problems after flashing the Gingerbread bootloaders?
bdl1969 said:
@Ramad, thanks for this information. Do we know for certain whether Samsung have 'locked' these new bootloaders like they did with the Galaxy Tab ones or can you flash back to a 2.2.1 Rom with no problems after flashing the Gingerbread bootloaders?
Click to expand...
Click to collapse
Thanks
The bootloaders are not locked and will not prevent the device from flashing or using older releases(Froyo/Eclair), I have tested the new bootloaders with both Froyo and Eclair and they worked fine.
<Don't try it if you don't really know what that implies !>
I've only Flashed Sbl.bin (after add it in a tar on Linux machine, don't make it with another tool !) fixes graphics corruption and recovery and downgrade to 2.2.1 works like before.
</Don't try it if you don't really know what that implies !>
I must confess a noobish doubt, how can I see if I have bootloaders ?
I'm using a custom rom JS8 Froyo
So I can determine wich version should I use
Pisca said:
I must confess a noobish doubt, how can I see if I have bootloaders ?
I'm using a custom rom JS8 Froyo
So I can determine wich version should I use
Click to expand...
Click to collapse
Every device has bootloaders, but if you are asking if it's the old or new bootloaders that are installed in your, then you have old bootloaders if you have not flashed the beta XWJV1 or XXJVK package that has bootloaders included, those 2 firmwares has the new bootloaders.
Thank you once again ramad
Sent from my GT-I9000 using XDA Premium App
.Slane. said:
<Don't try it if you don't really know what that implies !>
I've only Flashed Sbl.bin (after add it in a tar on Linux machine, don't make it with another tool !) fixes graphics corruption and recovery and downgrade to 2.2.1 works like before.
</Don't try it if you don't really know what that implies !>
Click to expand...
Click to collapse
What would be the advantage over flashing both boot loaders? Because that also will not interfere with froyo...
Sent from my galaxy using the xda app
kasper_h said:
What would be the advantage over flashing both boot loaders? Because that also will not interfere with froyo...
Sent from my galaxy using the xda app
Click to expand...
Click to collapse
very good...the bootloaders are very important
I did'n upgrade bootloader when i flash 2.3.3(from samfirmware) using odin and i have no any isues with my phone.i can entry to recovery and.download mode.
So why some people have a proplem and some not at all?
Sent from my GT-I9000 using XDA App
bizkopt said:
I did'n upgrade bootloader when i flash 2.3.3(from samfirmware) using odin and i have no any isues with my phone.i can entry to recovery and.download mode.
So why some people have a proplem and some not at all?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Have you flashed the Beta XWJV1 before? Please read the first post before posting.
Thanks for that bootloaders it is then, but I have one more question, do I tick bootloadets in odin or not? Thanks again
Sent from my GT-I9000 using XDA App
squashfanatic said:
Thanks for that bootloaders it is then, but I have one more question, do I tick bootloadets in odin or not? Thanks again
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
That is not needed, Odin will flash those files anyway.
No, i did not flash beta before and when i flash 2.3.3 using odin i use 512 pit file and tick re-partition only. I never choice update bootloader.now i remember i have that isue when i was using darky 9.4. After upgrade to 9.5 and his new kernel,problem,was gone
Sent from my GT-I9000 using XDA App
bizkopt said:
No, i did not flash beta before and when i flash 2.3.3 using odin i use 512 pit file and tick re-partition only. I never choice update bootloader.now i remember i have that isue when i was using darky 9.4. After upgrade to 9.5 and his new kernel,problem,was gone
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Bootloader files are in the PDA tar archive, when you flash the PDA tar archive, the bootloaders on the device will be updated, this is why I wrote that checking 'Phone Bootloader Update' will not matter. If the file that you have is called PDA_XXJVK_Sbl.tar then the bootloaders in your device are updated now.
SBL Bootloader / Rooting.
[Ramdad], Thanks for the post.
I've got the SBL exe, which I assume will flash the bootloader in the correct way. Now my question is, if I want to update my firmware, is it safe (bootloader wise) to flash the JV1 & root kernel and then the JVK kernel?
Thanks!
LordVetinari said:
[Ramdad], Thanks for the post.
I've got the SBL exe, which I assume will flash the bootloader in the correct way. Now my question is, if I want to update my firmware, is it safe (bootloader wise) to flash the JV1 & root kernel and then the JVK kernel?
Thanks!
Click to expand...
Click to collapse
Thanks, just flash JVK that you have and you will be fine.
[Ramad],
Not trying to confuse people, cm7 and MIUI require 2.2 bootloaders even though the firmware is 2.3.3.
So if you are from Samsung rom like xxjvk or jv1 and going to cm7 or MIUI, you will encounter screen tearing as well. Downgrade to a 2.2 with bootloaders will eliminate the tearing.
Hope you can include this info as well.
P/S: As always, thanks for sharing this with the users here.
Sent from my GT-I9000
thanks for the information... I thought to flash with bootloaders... now I'm considering again...
Hey Ramad,
I have a little question : a few firmwares on Samfirmware have these files in PDA : sbl.bin, boot.bin and param.lfs. I have heard that these files can brick our phone.
Can i delete them without changing anything in the PDA and flash through Odin ?
Thanks for helping me.
Sorry for my bad english.
Hi Guys:
Finally, I found it the best way to root firmware .266
******** Just for unlocked bootloader **********
Click to expand...
Click to collapse
The best way to solve the problem of "lack of management Ram
{
"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"
}
Dedicated to all of you: Special Thanks to my good friend @RuchRha :fingers-crossed:
1 - .266 firmware Central Europe will flash via Flash Tools on the your XSP.
2 - Using the advanced stock kernel from doomlord (flash it via QuickIMG) and flash the root app in recovery "supersu" app on your phone .
3 - The stock kernel of firmware .266 Click this link to download and flash it via QuickIMG (Download it at Attachment) [ The QuickIMG best tool for flah any Kernel with any Format! ]
4 - Download CWM And TWRP For XSP .266 zip file from this link and follow the manual steps.
extract the folder in .zip file to desktop and run install.bat you will have to enable usb debugging and need root for it
Click to expand...
Click to collapse
********* CWM and TWRP for Xperia SP with Locked Bootloader (Compatible with .266 firmware ) **********
Click to expand...
Click to collapse
Requiments:
4.1.2
Root
CWM
Flashtool
Download: .266 kernel
Purestockdeodex v2
Step1: booting cwm and flash(factory reset, wipe cache, advenced/wipe dalvik) purestockdeodex v2
Step2: flash supersu
Step3: advenced/power off
Step4: using flashtool and flash. 266 kernel
Use the CWM and TWRP for Xperia SP with Locked Bootloader that is compatible with firmware .266
To Install it:
Click to expand...
Click to collapse
1.) down CWM_SP_LB_4.3.zip file.
2.) unzip it on your desktop.
3.) go to the CWM SP folder
4.) run the install.bat file
5.) select option number 1 to install.
6.) stay tuned on the phone as it calls super user permissions.
7.) Read the directions to see that everything went well.
8.) If all went well you press a key to continue and depues press 3 to finish
Special Thanks to my good friend @RuchRha for CWM And TWRP For XSP .266 and stock kernel of firmware .266
Thanks to @DooMLoRD for advanced stock kernel
Thanks to @dssmex for CWM&TWRP for locked bootloader
Thanks to @jancsessz for Rooting method .266 fw for locked bootloader
If this post was helpful to you, press the thanks button :fingers-crossed:
Unlocked bootloaders only I believe..
mrjraider said:
Unlocked bootloaders only I believe..
Click to expand...
Click to collapse
Yes, The best way to root .266 only for Unlocked bootloaders
what the hell!!!
just do this
http://forum.xda-developers.com/showthread.php?t=2646193
ps:
loghme ro dore saret mipichoni??
ya naghi
Of course its for unlocked bootloader only. But. When U have it unlocked I dont see any sense to use stock kernel after all
A reason to use stock kernel is that the advanced kernel from doomlord has very poor ram management. A lot of users complaining about that. Thanks for the tutorial.
Sent from my C5303 using Tapatalk
didar2 said:
what the hell!!!
just do this
http://forum.xda-developers.com/showthread.php?t=2646193
ps:
loghme ro dore saret mipichoni??
ya naghi
Click to expand...
Click to collapse
If I took the train up to an hour to write it, because this have:
The main reason for this approach is that the only way to fix the problem "Ram management" is the same way.
luccasvr said:
A reason to use stock kernel is that the advanced kernel from doomlord has very poor ram management. A lot of users complaining about that. Thanks for the tutorial.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Yes u got it! :good:, this is the main cause of this education.
You could also add in the thread if som1 is on .254 fimrware and rooted can take a backup of TA partition, then unlock bootloader and after following all steps restore TA and flash stock kernel, that's it locked bootloader with all DRM keys/TA partition present along with root and recovery's.
Edit : in 3rd step it's not needed to flash the stock kernel using fastboot, it can/should be flashed in flashmode.
I want this for LB!!!!
Enviado desde mi C5303 mediante Tapatalk
Sorry internet connection error
Amin.HVS said:
Hi Guys:
Finally, I found it the best way to root firmware .266
In this tutorial:
The best way to solve the problem of "lack of management Ram"
Dedicated to all of you: Special Thanks to my good friend @RuchRha :fingers-crossed:
1 - .266 firmware Central Europe will flash via Flash Tools on the your XSP.
2 - Using the advanced stock kernel from doomlord (flash it via fastboot) and flash the root app in recovery "supersu" app on your phone .
3 - The stock kernel of firmware .266 Click this link to download and flash on your phone via fastboot.
4 - Download CWM And TWRP For XSP .266 zip file from this link and follow the manual steps.
Special Thanks to my good friend @RuchRha for CWM And TWRP For XSP .266 and stock kernel of firmware .266 :fingers-crossed:
Thanks to DoomLord for advanced stock kernel
If this post was helpful to you, press the thanks button :fingers-crossed:
Click to expand...
Click to collapse
Step 3 should not be flashed in fastboot. or it will bricked your phone. use flash tool via flash mode since it is a tft file
You should modify the title of this topic and add [UB] cause it misleads people and make them believe that there is a working root for [LB]
update to. 266 while keeping root
Hi, I'm new to this, is there anyway to update to 4.3 without losing root? And if there isn't, is it possible to re-root on updated Xperia sp without unlocking the bootloader? Any help greatly appreciated...
monkeymind said:
Hi, I'm new to this, is there anyway to update to 4.3 without losing root? And if there isn't, is it possible to re-root on updated Xperia sp without unlocking the bootloader? Any help greatly appreciated...
Click to expand...
Click to collapse
Nope, you will surely lose root when you update but you still can gain root by following the OP. Works 100% though you will need to UNLOCK your BOOTLOADER to gain such permission. But you can relock later after installing SuperSU and its binaries if you 1st backup your TA partition
So instead of creating the obvious tutorials about how to root for UBL only it would be nice if you could find the way for LB.
Also this is more of a double thread since Doomlord has updated his CWM thread
RuchRha said:
You could also add in the thread if som1 is on .254 fimrware and rooted can take a backup of TA partition, then unlock bootloader and after following all steps restore TA and flash stock kernel, that's it locked bootloader with all DRM keys/TA partition present along with root and recovery's.
Edit : in 3rd step it's not needed to flash the stock kernel using fastboot, it can/should be flashed in flashmode.
Click to expand...
Click to collapse
Ok Bro!
Edit post #1 and best tool for flash kernel added. :good:
Verssetti said:
I want this for LB!!!!
Enviado desde mi C5303 mediante Tapatalk
Click to expand...
Click to collapse
Sorry! just for UB!
OP Updated!
QuickIMG tools is the best tool for flash any kernel added to post #1
Enjoy...
You put a [LB] tag in the title, and you say in the thread it is for unlocked bootloader only ...
update to 4.3 and root with locked bootloader
I'm new here! I can't unlock the bootloader. Am running rooted 4.1 on xperia sp. Could you put up a very simple step by step guide for doing the update and rooting. I've read through the thread and can't quite follow what to do. Have used flashtool for the original rooting process but apart from that am totally green I'm afraid...thanks in anticipation!
Elwino2.3 said:
When i try mount /system via cwm the log says "error mounting /system". How to fix this? Please help
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Anyone?
Sent from my C5303 using Tapatalk
H3G M7 Guru Reset Rom + File Collection
HTML:
In this thread I will be sharing my collection of file's for the HTC One M7 on H3G. All these files will be useful for returning to stock especially those with s-on. I hope someone finds them useful anyway [emoji14] All files in this thread are suitable for devices with the following CiD and MiD
Code:
modelid: PN0710000
cidnum: H3G__001
cidnum: H3G__106
cidnum: H3G__402
cidnum: H3G__G04
Guru Reset Rom Stock KitKat 6.14.771.2Guru_Reset_M7_H3G_6.14.771.2.zip MD5 :- 676e56aa7e5e725387b65dd14e322fba
Includes optional Stock Recovery, Stock Radio and Root.
Install with TWRP recovery like any other rom. (TWRP 2.6.3.3 Recommended)
OTA updates when available.
{
"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"
}
Thanks to @crushalot www.htc1guru.com for the original aroma guru reset package.
Stock Nandroid BackupsKitKat 4.4.3 6.14.771.2 TWRP Nandroid MD5 :- 72c8152a8179fbd4cb2d2e5b8b35b905
Full Stock for OTA's
KitKat 4.4.2 5.12.771.3 TWRP Nandroid
Full Stock for OTA's
JellyBean 4.3 3.62.771.3 TWRP Nandroid
Pre-Rooted and missing Preload Data, Not suitable for taking OTA's
Firmware Zips 2.24.771.3.zip MD5:- a56305ea6570ee4ff656a4357171ce11
3.62.771.3.zip MD5:- ba684b5207d74e24075cd4b02ead3ba1
4.20.771.17.zip MD5:- d4fba9da51321b95741440b647bc9bee
5.12.771.3.zip MD5:- 64f0d0a23fb5468d669bb2f922043d9c
6.14.771.2.zip MD5:- 0dd432cbf3ddddcdd74ee669b44ee376
7.19.771.1.zip MD5:- 0ec86aefeadf7e3c0e37fafaa1192777
OTA Update ZipOTA_M7_UL_JB_50_SENSE5_H3G_UK_2.24.771.3-1.28.771.6_release_328027_signedlnazfd1l6874pvs8.zip MD5:- d1eecfce64c7847a2ee35a9e9be8ca95
OTA_M7_UL_JB43_SENSE55_MR_H3G_UK_3.62.771.2-2.24.771.3_release_338684cjuf0j4gm1ogoo4n.zip MD5:- c7798f585b4ff326a3b8bad083ba05ed
OTA_M7_UL_K44_SENSE55_MR_H3G_UK_4.20.771.17-3.62.771.3_release_3536491kghgv33dtz4m18n.zip MD5:- 583dae463ffdf61b337f7946ed9db01a
OTA_M7_UL_K44_SENSE60_MR_H3G_UK_5.12.771.3-4.20.771.17_release_37214948ro8l36c6yo7dhi.zip MD5:- 44a3956d277141886af7ebc60a072766
OTA_M7_UL_K443_SENSE60_MR_H3G_UK_6.14.771.2-5.12.771.3_release_387423qg91a2pgfo5cx9ic.zip MD5:- 3dca820e82014f04afba66b41735bba4
OTA_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.1-6.14.771.2_release_420807iloxunzwjif4idfm.zip MD5:- 3dca820e82014f04afba66b41735bba4
What is H3G?
Which one should i have to use?
i'm on firmware 6.09.401.11, HTC__001 and S-ON.
Black_Eyes said:
What is H3G?
Which one should i have to use?
i'm on firmware 6.09.401.11, HTC__001 and S-ON.
Click to expand...
Click to collapse
H3G is the mobile carrier Three these files are no good to you. I believe you requested a nandroid backup for your device in the collection thread. Take a look I posted a link there for you
http://forum.xda-developers.com/showthread.php?p=58690924
Danny201281 said:
H3G is the mobile carrier Three these files are no good to you. I believe you requested a nandroid backup for your device in the collection thread. Take a look I posted a link there for you
http://forum.xda-developers.com/showthread.php?p=58690924
Click to expand...
Click to collapse
Thanks Again
They all look extremely tempting and I actually understand which each file is, well almost hehe. Which would you recommend downloading in order to start from scratch on the HTC One M7 to be able to download OTA's? Or would it be quicker to just flash stock recovery?
Sacrimony said:
They all look extremely tempting and I actually understand which each file is, well almost hehe. Which would you recommend downloading in order to start from scratch on the HTC One M7 to be able to download OTA's? Or would it be quicker to just flash stock recovery?
Click to expand...
Click to collapse
It depends on your current situation. If you have the Stock Rom complete with Preload data. Then flashing the Stock Recovery should do the trick just fine with little hassle.
If you have a Custom Rom or have at some point unlocked the bootloader with your Stock Rom then the Guru Reset would be your best option. As Unlocking the bootloader wipes the Stock preload data which will cause the OTA to fail.
Danny201281 said:
It depends on your current situation. If you have the Stock Rom complete with Preload data. Then flashing the Stock Recovery should do the trick just fine with little hassle.
If you have a Custom Rom or have at some point unlocked the bootloader with your Stock Rom then the Guru Reset would be your best option. As Unlocking the bootloader wipes the Stock preload data which will cause the OTA to fail.
Click to expand...
Click to collapse
Ah I see, well I think I fall under the latter category. So is it just a case of downloading the guru .zip and then booting into TWRP and then flashing the .zip through there? ?
Sent from my HTC One using XDA Free mobile app
Sacrimony said:
Ah I see, well I think I fall under the latter category. So is it just a case of downloading the guru .zip and then booting into TWRP and then flashing the .zip through there? ?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Yes the gurureset flashes in recovery. It uses the Aroma installer and can flash the Stock Recovery for you this is an option during the installer setup :good:
Danny201281 said:
Yes the gurureset flashes in recovery. It uses the Aroma installer and can flash the Stock Recovery for you this is an option during the installer setup :good:
Click to expand...
Click to collapse
Ah that is fantastic! So everything I need is included in the guru zip? Man, one again you've been amazing. Thank you so much!
Sent from my HTC One using XDA Free mobile app
Just a quick update on the guru zip. Everything has worked perfectly, up and running as new. Just thought I should mention that on the bootloader screen it still says Tampered and Unlocked. Plus there's no longer a recovery, is this a problem for OTA's? Knowing me I've probably messed something up along the way.
Sent from my HTC One using XDA Free mobile app[/QUOTE]
Sacrimony said:
Just thought I should mention that on the bootloader screen it still says Tampered and Unlocked.
Click to expand...
Click to collapse
Flashing a ROM will not change anything in the bootloader. You need s-off to remove both of these.
Plus there's no longer a recovery, is this a problem for OTA's? Knowing me I've probably messed something up along the way.
Click to expand...
Click to collapse
I think you probably mean that there's no more custom recovery installed on your phone? Because the reset rom flashed back the stock recovery, like danny said at post #8.
Sacrimony said:
Just a quick update on the guru zip. Everything has worked perfectly, up and running as new. Just thought I should mention that on the bootloader screen it still says Tampered and Unlocked. Plus there's no longer a recovery, is this a problem for OTA's? Knowing me I've probably messed something up along the way.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
alray said:
Flashing a ROM will not change anything in the bootloader. You need s-off to remove both of these.
I think you probably mean that there's no more custom recovery installed on your phone? Because the reset rom flashed back the stock recovery, like danny said at post #8.
Click to expand...
Click to collapse
Yep what @alray said ,
Just for clarity, with the stock recovery if your getting a black screen followed by a picture of a phone with a red exclamation mark then that's normal. That is the stock recovery. To reveal the recovery menu hold volume up and press the power button. You will see some errors about unable to mount sdcard this is also normal. The recovery is looking for an sd card slot which the M7 doesn't have. We only have the internal storage :good:
Danny201281 said:
Yep what @alray said ,
Just for clarity, with the stock recovery if your getting a black screen followed by a picture of a phone with a red exclamation mark then that's normal. That is the stock recovery. To reveal the recovery menu hold volume up and press the power button. You will see some errors about unable to mount sdcard this is also normal. The recovery is looking for an sd card slot which the M7 doesn't have. We only have the internal storage :good:
Click to expand...
Click to collapse
alray said:
Flashing a ROM will not change anything in the bootloader. You need s-off to remove both of these.
I think you probably mean that there's no more custom recovery installed on your phone? Because the reset rom flashed back the stock recovery, like danny said at post #8.
Click to expand...
Click to collapse
Ah I understand now. That is really helpful, thanks both of you for clearing that up. I've read on a couple of sites that you may need to re-lock the bootloader and to get rid of the "Tampered" sign if you're to receive OTA updates, do you guys know if that's the case?
Sacrimony said:
Ah I understand now. That is really helpful, thanks both of you for clearing that up. I've read on a couple of sites that you may need to re-lock the bootloader and to get rid of the "Tampered" sign if you're to receive OTA updates, do you guys know if that's the case?
Click to expand...
Click to collapse
The guru reset is everything you need to be ready for the OTA. :good: Unlocked bootloader is fine as long as the software is stock :good:
Danny201281 said:
The guru reset is everything you need to be ready for the OTA. :good: Unlocked bootloader is fine as long as the software is stock :good:
Click to expand...
Click to collapse
Ok, that's awesome. Many thanks once again for your help and for your patience with my annoying questions!
Sacrimony said:
Ok, that's awesome. Many thanks once again for your help and for your patience with my annoying questions!
Click to expand...
Click to collapse
Your welcome :good: it's better to get it right first time, than to try and fix it after it's gone wrong
It gets stuck at 10%.
GeoVali99 said:
It gets stuck at 10%.
Click to expand...
Click to collapse
Which recovery are you using?
TWRP 2.8
But it's irrelevant now. After a couple of system formattings it did install.
GeoVali99 said:
TWRP 2.8
But it's irrelevant now. After a couple of system formattings it did install.
Click to expand...
Click to collapse
Ok cool, for the record though installs getting stuck happens a lot with TWRP 2.8.X.X :good:
That's why I recommend 2.6.3.3 but glad you got sorted though. If youhavent checked recently h3g are pushing the update now
Gonna have to close the download Link temporarily. Got 1 report of Boot Issues...
I made this TWRP Back-up for you all that took the OE1 OTA And Would Like To Rock Hybrid-X 2.2.
The TWRP back-up contains Boot, Recovery (TWRP of course), System & Cache Partitions. No Data Or EFS.
At first Time Boot, It Will Go Through The Set-Up Process As If It Were A First Time Rom Flash.There Is
No Data That Wasn't In The Original Rom @tx_dbs_tx Cooked Up With 2 Exceptions:
1.Updated SuperSU To v2.49
2.Updated Galaxy Tools To v 3.1.8
Other Than That It Is As @tx_dbs_tx Made It, Without The Data Partition.
Go To Nandroid Download Link:
Here
Now, As I Am On OB7 (Hybrid-X 2.2) I Can't Test This On OE1 But Some Members Who Are A Lot Smarter Than
I Am Believe To High Degree Of Certainty It Will Get It Done.
Make Sure You Have A Back-Up Of Your Current Configuration!
Standard Stuff... Blah, Blah, Blah. Hate Standard stuff... Gimme Brick's, Cracked Screen's, OE1 And I'll
Cry Myself HAPPY!
EDIT:
You may have to update Profile & Prl after flashing this back-up
Id like to try this but im bout to head to work, subscribed and hope this works
Will report back
pbedard said:
Will report back
Click to expand...
Click to collapse
Appreciate it.
Its no good doesnt boot phone turns on but vibrates and goes black then turns off
pbedard said:
Its no good doesnt boot phone turns on but vibrates and goes black then turns off
Click to expand...
Click to collapse
Ok, thanks..
Damn :/
l330n said:
Damn :/
Click to expand...
Click to collapse
I'm going to put in some time tomorrow and try to get this figured out.
jhill110 said:
I'm going to put in some time tomorrow and try to get this figured out.
Click to expand...
Click to collapse
I didn't see the modem listed as included in your file. Wouldn't you need that to get the baseband back to OB7?
Sent from my SM-N910P using XDA Premium HD app
DreamingWolf said:
I didn't see the modem listed as included in your file. Wouldn't you need that to get the baseband back to OB7?
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
Yea u can find it somewhere here but IG don't boot still
pbedard said:
Yea u can find it somewhere here but IG don't boot still
Click to expand...
Click to collapse
I pushed baseband back to OB7 through a TWRP restore and am running Hybrid-X 2.2 right now. I flashed the ROM from their thread and the r16 emotion kernel and it booted fine. Baseband still shows OB7 though I know the bootloader is still OE1 because Odin fails eveytime on aboot.
Sent from my SM-N910P using XDA Premium HD app
{
"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"
}
Sent from my SM-N910P using XDA Premium HD app
DreamingWolf said:
I pushed baseband back to OB7 through a TWRP restore and am running Hybrid-X 2.2 right now. I flashed the ROM from their thread and the r16 emotion kernel and it booted fine. Baseband still shows OB7 though I know the bootloader is still OE1 because Odin fails eveytime on aboot.
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
Where did you get the baseband can you post it so we me be able to flash back?
kennethbb said:
Where did you get the baseband can you post it so we me be able to flash back?
Click to expand...
Click to collapse
I used a TWRP backup of an OB7 ROM that included all the partitions, especially the modem.
@Droid2drummer has a copy of my partitions to test. If it works for him I will post the link publicly.
UPDATE:
Spent today trashing and fixing my phone. I figured out that I didn't revert the baseband through a TWRP restore. (I have an OE1 base backup and I flashed the modem from that half a dozen times and it never changed to OE1 baseband). That means it must have been through one of the Odin flashes I did (that failed, but apparently AFTER writing the modem.bin)
Does anyone have an OE1 modem.bin? I can pull the boot.img from my TWRP backup, but the modem isn't stored in a bin format. I need one so I can test my theory.
Or, if there is a brave soul out there, I made an Odin flashable tar file of the OB7 modem and the r16 emotion kernel. I have flashed it multiple times on my phone with no issues. I know it changes the kernel because I have another file with the OB7 modem and the OB7 stock kernel that I was using as a base.
If anyone is willing to try the OB7modem/emotion kernel file and report back you can download it here.
Sent from my SM-N910P using XDA Premium HD app
Anyone confirm this working? I know dream has it working. Just checking. My phone didnt take the retore backup file
Sent from my SM-N910P using XDA Free mobile app
Im on it! It works. Just flash the modem tar in the section dreaming wolf posted. About to make another backup. So i have one oe1 complete. Then this one hybrid modem boot (i call it hybrid) so now i should be good to go. Now i think is the time to create a thread and secure this to keep the rom threads cleaned. Thank you all. Im reporting from fresh install via odin modem tar bob7 on oe1. I will test flash a bob7 rom and get back.
Sent from my SM-N910P using XDA Free mobile app
DreamingWolf said:
I used a TWRP backup of an OB7 ROM that included all the partitions, especially the modem.
@Droid2drummer has a copy of my partitions to test. If it works for him I will post the link publicly.
UPDATE:
Spent today trashing and fixing my phone. I figured out that I didn't revert the baseband through a TWRP restore. (I have an OE1 base backup and I flashed the modem from that half a dozen times and it never changed to OE1 baseband). That means it must have been through one of the Odin flashes I did (that failed, but apparently AFTER writing the modem.bin)
Does anyone have an OE1 modem.bin? I can pull the boot.img from my TWRP backup, but the modem isn't stored in a bin format. I need one so I can test my theory.
Or, if there is a brave soul out there, I made an Odin flashable tar file of the OB7 modem and the r16 emotion kernel. I have flashed it multiple times on my phone with no issues. I know it changes the kernel because I have another file with the OB7 modem and the OB7 stock kernel that I was using as a base.
If anyone is willing to try the OB7modem/emotion kernel file and report back you can download it here.
Sent from my SM-N910P using XDA Premium HD app
Click to expand...
Click to collapse
Attention. Its a go!
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 01:17 AM ---------- Previous post was at 12:53 AM ----------
Droid2drummer said:
Attention. Its a go!
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Ok. So i was successful in the tar flash of modem etc. Said update successful as well. I backed up the boot bob7 modem etc. Then tried to flash hybrid v2 rom. No go. Sorry. Not sure why. More testing i guess. I tried a kernel as well and no. So i got a bit excited. I hope we get a tar of beyond bob7 soon. That way my true testing will be safer in its trials. Im not sure what else to try. Unless i wipe internal. And then try the entire process. However not so sure. It is possible as dreaming wolf has done it. Need more time. Until then. Thank you all.
Sent from my SM-N910P using XDA Free mobile app
Droid2drummer said:
Ok. So i was successful in the tar flash of modem etc. Said update successful as well. I backed up the boot bob7 modem etc. Then tried to flash hybrid v2 rom. No go. Sorry. Not sure why. More testing i guess. I tried a kernel as well and no. So i got a bit excited. I hope we get a tar of beyond bob7 soon. That way my true testing will be safer in its trials. Im not sure what else to try. Unless i wipe internal. And then try the entire process. However not so sure. It is possible as dreaming wolf has done it. Need more time. Until then. Thank you all.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Does your baseband show up as BOB7 in the ROM you're currently running? - EDIT just saw you followup post, ignore this question.
Don't know if it makes a difference, but my flash process almost never varies. I factory reset X3, format data X3, advanced wipe everything except extsdcard X3, then flash Uberwipe.zip which reboots me into recovery (I seem to recall, I think it was with the Note 3, that certain flashings would work better if the phone was rebooted into recovery between the wiping of the old and the flashing of the new), then I flash the ROM, wipe cache and Dalvik, flash the kernel (if applicable, with Hybrid i flashed r16 seperately), wipe cache and Dalvik, then flash SuperSU (usually the beta 2.49 version), wipe cache and Dalvik, and after all that I will finally reboot into the system.
Obsessive I know, but following that proceedure I almost never have problems. And anything I usually need on the internal card I copy to the external then move back after the flash.
And +1 on getting a post OB7 tar soon.
Yeah. Even after restoring my oe1 backup still reads bob7 build and bob7 as i showed in screeny. Then oe1 baseband
Sent from my SM-N910P using XDA Free mobile app
---------- Post added at 02:39 AM ---------- Previous post was at 01:47 AM ----------
Droid2drummer said:
Yeah. Even after restoring my oe1 backup still reads bob7 build and bob7 as i showed in screeny. Then oe1 baseband
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
No sorry. Build number only shows oe1. Rest is bob7
Sent from my SM-N910P using XDA Free mobile app
???
I am not taking ownership of anything that I post below.
TWRP for DROID TURBO:
[RECOVERY][OFFICIAL TWRP 3.0.0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
https://dl.twrp.me/quark/twrp-3.0.0-0-quark.img.html
CM 12.1:
[Moto MAXX XT1225][OFFICIAL] CyanogenMod 12.1
http://download.cyanogenmod.org/?device=quark
@baybutcher27 also developed a custom kernel:
[Kernel][Moto Maxx]BHB27-Kernel[5.x.x][CM base][V-1.1.4]
http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526
https://github.com/bhb27/My_works
How to Install:
To Install the CM 12.1 you must:
Download the CM12.1 rom, (https://download.cyanogenmod.org/?device=quark)
Download the proper Gapps ( http://d-h.st/BX7Q)
Download the custom kernel for CM 12.1 (https://www.androidfilehost.com/?w=files&flid=42109)
Optional: Download SuperSU for root (https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Boot Into TWRP
Wipe including system partition
Flash rom
Flash kernel
Flash gapps
Wipe cache/dalvic
Do standard wipe again (not system partition this time)
Flash SuperSU if you need root
Reboot system
Profit
Thanks to @hotrodwinston for helping me out
All the links are here
http://forum.xda-developers.com/showthread.php?p=63956817
And here:
http://forum.xda-developers.com/showthread.php?p=63956441
Since I posted those, both CM and Resurrection Remix can be flashed on XT1254 with @baybutcher27 beta kernel found in those posts.
By tomorrow noon you can flash CM with it's own kernel, when the 11/28 nightly appears.
In those posts are also links for bootloader warning removal, Moto camera for CM, as well as 60fps custom bootloader animation.
ChazzMatt said:
All the links are here
http://forum.xda-developers.com/showthread.php?p=63956817
And here:
http://forum.xda-developers.com/showthread.php?p=63956441
Since I posted those, both CM and Resurrection Remix can be flashed on XT1254 with @baybutcher27 beta kernel found in those posts.
By tomorrow noon you can flash CM with it's own kernel, when the 11/28 nightly appears.
In those posts are also links for bootloader warning removal, Moto camera for CM, as well as 60fps custom bootloader animation.
Click to expand...
Click to collapse
Thankyou VERY much, updated OP, and im working on installing it myself right now for the guide.
bump for people looking for it
Just make sure you do this...
{
"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"
}
before flashing the new ROM + GAPPS + kernel.
I think this is why some people were getting system storage space errors. They had something else installed on their system before flashing new ROM and didn't wipe it clean first.
I did twrp back up , but I can't find it the back up folder in twrp folder ?? How this happened no idea ..
aneeshmbabu said:
I did twrp back up , but I can't find it the back up folder in twrp folder ?? How this happened no idea ..
Click to expand...
Click to collapse
See here:
http://forum.xda-developers.com/dro...e-location-t3259060/post64049328#post64049328
aneeshmbabu said:
I did twrp back up , but I can't find it the back up folder in twrp folder ?? How this happened no idea ..
Click to expand...
Click to collapse
On the stock rom TWRP doesn't show my backups at all like it usually does but in TWRP it shows them there like it should. No idea why.
Edit: just saw post above, its there lol
INCREMENTAL said:
On the stock rom TWRP doesn't show my backups at all like it usually does but in TWRP it shows them there like it should. No idea why.
Click to expand...
Click to collapse
You went to /data/media/0/TWRP/Backups?
On my phone which is running CM, I can see TWRP backups 3 ways: via USB connection as flash drive, in TWRP recovery mode, and through Root Explorer app.
Via USB, you can drag them off onto your computer to save elsewhere.
But of course you can only restore them in TWRP recovery mode.
Michaelmansour1997 said:
I am not taking ownership of anything that I post below.
TWRP for DROID TURBO:
[RECOVERY][OFFICIAL TWRP 2.8.7.0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308
CM 12.1:
[Moto MAXX XT1225][OFFICIAL] CyanogenMod 12.1
http://forum.xda-developers.com/mot.../moto-maxx-xt1225-cm12-0-pre-release-t3060089
@baybutcher27 also developed a custom kernel:
[Kernel][Moto Maxx]BHB27-Kernel[5.x.x][CM base][V-1.1.4]
http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526
https://github.com/bhb27/My_works
How to Install:
To Install the CM 12.1 11/27 nightly you must:
Download the CM12.1 rom, (https://download.cyanogenmod.org/?device=quark)
Download the Proper Gapps ( http://d-h.st/BX7Q)
Download the custom kernel for the 11/27 build (https://www.androidfilehost.com/?w=files&flid=42109)
Boot Into TWRP
Wipe including system partition
Flash rom
Flash kernel
Flash gapps
Wipe cache/dalvic
Do standard wipe again (not system partition this time)
Reboot system
Profit
Thanks to @hotrodwinston for helping me out
Click to expand...
Click to collapse
Okay two things: there are two 11/27 CM12.1 zips and the gapps link isn't working. Would open gapps or banks gapps work?
Marky__Mark said:
Okay two things: there are two 11/27 CM12.1 zips and the gapps link isn't working. Would open gapps or banks gapps work?
Click to expand...
Click to collapse
1) gapps link is working fine for me: http://d-h.st/BX7Q Same link from the op.
2) either 11/27 will work. Somehow duplicate got created. I used the 2nd one just in case.
aneeshmbabu said:
I did twrp back up , but I can't find it the back up folder in twrp folder ?? How this happened no idea ..
Click to expand...
Click to collapse
to get the twrp backup, boot into twrp and plug into pc then go into the twrp folder and you will find it there.
ChazzMatt said:
1) gapps link is working fine for me: http://d-h.st/BX7Q Same link from the op.
2) either 11/27 will work. Somehow duplicate got created. I used the 2nd one just in case.
Click to expand...
Click to collapse
Alright, I'll have to download it on my computer. Thanks
---------- Post added at 06:17 PM ---------- Previous post was at 05:25 PM ----------
Michaelmansour1997 said:
I am not taking ownership of anything that I post below.
TWRP for DROID TURBO:
[RECOVERY][OFFICIAL TWRP 2.8.7.0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308
CM 12.1:
[Moto MAXX XT1225][OFFICIAL] CyanogenMod 12.1
http://forum.xda-developers.com/mot.../moto-maxx-xt1225-cm12-0-pre-release-t3060089
@baybutcher27 also developed a custom kernel:
[Kernel][Moto Maxx]BHB27-Kernel[5.x.x][CM base][V-1.1.4]
http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526
https://github.com/bhb27/My_works
How to Install:
To Install the CM 12.1 11/27 nightly you must:
Download the CM12.1 rom, (https://download.cyanogenmod.org/?device=quark)
Download the Proper Gapps ( http://d-h.st/BX7Q)
Download the custom kernel for the 11/27 build (https://www.androidfilehost.com/?w=files&flid=42109)
Boot Into TWRP
Wipe including system partition
Flash rom
Flash kernel
Flash gapps
Wipe cache/dalvic
Do standard wipe again (not system partition this time)
Reboot system
Profit
Thanks to @hotrodwinston for helping me out
Click to expand...
Click to collapse
I also had to install SuperSU
Marky__Mark said:
Alright, I'll have to download it on my computer. Thanks
---------- Post added at 06:17 PM ---------- Previous post was at 05:25 PM ----------
I also had to install SuperSU
Click to expand...
Click to collapse
lol thanks for reminding me, i dont use many root apps if im on cm12.1 but ill add that to the OP
ChazzMatt said:
Just make sure you do this...
before flashing the new ROM + GAPPS + kernel.
I think this is why some people were getting system storage space errors. They had something else installed on their system before flashing new ROM and didn't wipe it clean first.
Click to expand...
Click to collapse
System storage issue was something different. It did end up being the file system type. Might have had a bad flash somewhere along the lines. One I moved /data back to ext4, restored my stock backup, I followed the same steps and everything worked fine. I'll chalk it up to a fluke, or bad download.
Thanks all I found the twrp back up in data/media/0/twrp/backup
I'm not brave enough to be one of the first to install a custom ROM. I also don't know how much modifying this needs coming from the Moto Maxx. Are they nearly identical?
Anyone else getting google play services has stopped message? I get it on every boot but only once. Probably cuz that gapps package is so old. Do we have anything else to work with?
Did all the steps in order above exactly and runs smooth but I can't make or receive calls I have signal and data but no calls says cellular connection not avalible. And here's a screenshot of phone status in settings
http://postimg.org/image/rbuysqvut/
DanielWEWO said:
I'm not brave enough to be one of the first to install a custom ROM. I also don't know how much modifying this needs coming from the Moto Maxx. Are they nearly identical?
Click to expand...
Click to collapse
You aren't the first. Many, many people installed both Resurrection Remix and CM 12.1 yesterday on their XT1254 Droid Turbos. You are actually late to the party.
Yes, they are exactly identical except for radio. They are all Quarks. Motorola released two Quark devices across the world under 3 model names. No, it was NEVER exclusive to Verizon. Forget that marketing lie. They even released the XT1250 U.S. Moto Maxx which was IDENTICAL even in radio to the Droid Turbo, with the SAME FCC ID. Sold by smaller regional LTE/CDMA carriers. it was the "dev" version of the Droid Turbo as it had unlock-able bootloader and runs on Verizon with a Verizon SIM card. The XT1254 Droid Turbo is just the last Quark to get the bootloader unlocked. Where have you been?