Database Develop

Do I have to go back to stock?

I'm sorry if someone already asked this question but I was not able find an answer. I am running a custom ROM now, do I have to go back to stock before flashing another ROM?

It is usually not necessarily to do it but it a very good idea to return to stock and master clear with the odin-1-click
Sent from my GT-I9000 using XDA App

No you don't need to go back to stock. Nor is is necessary to master clear. Most if not all the roms on here will do a full wipe of your SD card during the install. Flashing back to stock just adds another chance to mess up your phone. This was advised, several months back but it's not necessary now. This doesn't apply if you want to flash to CM7. They have their own install procedure that is different than anyone elses.

Just to add to what the others said. Make sure u flash a 2.2 based rom over ur curent (if thats what u are.using atm). Also you cant restore system app, it will screw up with ur new rom!
Sent from my SAMSUNG-SGH-I897 using XDA App

BWolf56 said:
Just to add to what the others said. Make sure u flash a 2.2 based rom over ur curent (if thats what u are.using atm). Also you cant restore system app, it will screw up with ur new rom!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The 2.2 stock will not let you flash a rom over it. Go back to 2.1 stock
Sent from my SAMSUNG-SGH-I897 using XDA App

crystalhand said:
The 2.2 stock will not let you flash a rom over it. Go back to 2.1 stock
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Not what I meant.
If he flashed, lets say, FireFly (which is 2.2 based) then he can't flash over with, lets say, CM7 (which is 2.3 based). Just simple logic
@ OP - You can look on the ROM's thread to see what it is based on.

Thank you for all your help. I'm using Phoenix Ultimate now and want to try out the other ROM.

It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install. Plus all the devs put that in their instructions. I trust the devs.
If you download the CWM update.zip before you Odin to stock and leave it on your phones internal SD card, you don't have to root or get ROM manager. Place your new ROM on the internal card too. Just Odin to stock, allow to boot, and restart into recovery (3 button combo), install updates (twice) then use CWM to install zip from card (ROM you downloaded).
Sent from my SAMSUNG-SGH-I897 using XDA App

quarlow said:
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
One less time touching Odin is one less time tempting fate. But that's just me. I'm pretty sure every rom dev in here has bricked a phone at least once...

much agreed. less odin. less potential for problems.
roms do a wipe now. doesnt matter what you had on it 2.1 or 2.2
2.3 is the only rom version that has a different partition table.
there is no issue flashing a 2.2 rom over 2.1 or vice versa. how CAN you upgrade from 2.1 to 2.2?? CWM anyone? oh **** right!
the only issue with flashing over 2.2 is the 3e recovery... and thers a fix for that. you dont need to go back to 2.1 to avoid the signature verification error... @crystalhand...

quarlow said:
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install. Plus all the devs put that in their instructions. I trust the devs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Not all devs put it in their op. Some devs say flash first thru clockwork and only use odin when there are problems. Odin could be better used as a recovery tool only, not the first thing you do whenever you want to flash a new rom. Just my opinion.
Sent from my SAMSUNG-SGH-I897

1tontomato said:
Odin could be better used as a recovery tool only, not the first thing you do whenever you want to flash a new rom. Just my opinion.
Click to expand...
Click to collapse
EXACTLY as it should be.....

No, odin is potentially more dangerous than any standard rom flash. as has been mentioned, use in case your in some s

I've always flashed back to stock using Odin whenever I flash a new rom. Like someone else on this thread said, it just feels cleaner doing it that way. While I don't doubt you guys when you say it's dangerous, would anyone like to offer a brief explanation as to why that is? And would anyone be willing to guess at what the odds of a permanent brick might be? Are we talking something like 1 in every 10 flashes or more like 1 in 1000?
If it's closer to the first one then we really are playing with fire here but if the odds are more like the second one then I don't consider that much of a risk.

Juanmail15 said:
I've always flashed back to stock using Odin whenever I flash a new rom. Like someone else on this thread said, it just feels cleaner doing it that way. While I don't doubt you guys when you say it's dangerous, would anyone like to offer a brief explanation as to why that is? And would anyone be willing to guess at what the odds of a permanent brick might be? Are we talking something like 1 in every 10 flashes or more like 1 in 1000?
If it's closer to the first one then we really are playing with fire here but if the odds are more like the second one then I don't consider that much of a risk.
Click to expand...
Click to collapse
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.

axis01 said:
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
Click to expand...
Click to collapse
+1
Odin should only be used as a "Oh S**T I bricked my phone" program. But then again, if you read and know what you're doing than it should never be "needed"

axis01 said:
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
Click to expand...
Click to collapse
Completely agree just want to clarify 1 thing. The roms don't do a complete wipe of the sdcard. The wipe the /data /cache and /system partitions, leaving the /sdcard completely intact, just like flashing to stock would. Master clear just reformats /sdcard partition and is not really needed as the os doesn't use this to function and including this in a rom would be catastrophic if the zip is in fact on the /sdcard partition you are wiping with it.

The most I do is clear cache, data and disable lagfix.

quarlow said:
If you download the CWM update.zip before you Odin to stock and leave it on your phones internal SD card, you don't have to root or get ROM manager. Place your new ROM on the internal card too. Just Odin to stock, allow to boot, and restart into recovery (3 button combo), install updates (twice) then use CWM to install zip from card (ROM you downloaded).
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
So you'd just drop the update.zip on your internal drive, drop the ROM in as well, boot into recovery and flash it that way?

Lancered said:
So you'd just drop the update.zip on your internal drive, drop the ROM in as well, boot into recovery and flash it that way?
Click to expand...
Click to collapse
Yup. That's how u do it, if you have no need to root before hand and back up, I'm assuming you've done that if I remember right you are the girl I told to brick her phone yesterday to return, is the replacement on eclair or froyo? Ig it on froyo you will have to get past the 3e recovery that's why I ask.

[NEEDED] 6.893 100% stock backup

Does anyone have a backup of 6.893?
Typically I am very diligent, but somehow I forgot to make a backup of stock.
I have not switched to any other update. I have read through everything thoroughly and I apologize for failing to follow instructions. With 5 android devices and multiple flashes I have never missed this before. And I realized it as soon as I flashed TH3ORYS rom
From what I gather the easiest and most effective way to get back on track is to flash a stock 6.893 rom make a backup and move on from there.
I appreciate anyone's help!
I am also open to using this thread or creating one in delopment to post the stock roms of every version.
Sent from my DROID BIONIC using xda premium

http://forum.xda-developers.com/showthread.php?t=1279825
Restore the system apps and you'll be back to square one.

Mustang02 said:
http://forum.xda-developers.com/showthread.php?t=1279825
Restore the system apps and you'll be back to square one.
Click to expand...
Click to collapse
Not entirely true. His system will be back to 5.5.886, but his kernel/radio will be his previously upgraded 5.6.893. He is off the upgrade path until he gets the matching system file of 5.6.893. Only then can he continue updating. I just went through this exact thing, used the one step recovery, but went back to .886 and had to beg to find someone to send me a CWR back up of their 5.6.893, which got me back on track.

Oh yeah...nevermind. I completely thought you were wanting stock not the ota. That's what I get for speed reading.

stevessvt said:
Not entirely true. His system will be back to 5.5.886, but his kernel/radio will be his previously upgraded 5.6.893. He is off the upgrade path until he gets the matching system file of 5.6.893. Only then can he continue updating. I just went through this exact thing, used the one step recovery, but went back to .886 and had to beg to find someone to send me a CWR back up of their 5.6.893, which got me back on track.
Click to expand...
Click to collapse
You don't still have this do you? Because I am not above begging!
Sent from my DROID BIONIC using xda premium

I'm afraid I dont, I got back to 5.6.893 then immediately upgraded to 5.7.893 and backed that up, since .6.893 was no good to me any more. I'm sorry.

Someone out there has to have this!
....I hope
Sent from my DROID BIONIC using xda premium

Give this a try. (Can't post links yet)
rootzwiki.com/topic/8562-easily-upgrade-to-57893-and-keep-root/
I'm thinking you will only need steps 1 and 2.
Hope it helps!!

ripper2860 said:
Give this a try. (Can't post links yet)
rootzwiki.com/topic/8562-easily-upgrade-to-57893-and-keep-root/
I'm thinking you will only need steps 1 and 2.
Hope it helps!!
Click to expand...
Click to collapse
Wont it fail because I'm not coming from stock? And if I go all the way back it wont work because ill end up with a hybrid?
Sent from my DROID BIONIC using xda premium

I'm in the same situation. Yes, all attempts to upgrade fail because our sys filed don't match our radio. I need this nandroid as well.
Sent from my DROID BIONIC using Tapatalk

Giving someone a backup made on your device or restoring a backup made on someone else's device is an extremely foolhardy proposition. You are cloning the Android_id from one device to the other, which means that apps that use it as an identifier will push and pull data from both devices without any intervention from the unknowingly affected user.

system img
correct me if im wrong but, all we need is the system img right because im stuck with a hybrid

Does anyone know if restoring my 5.893 back up will work, or create a hybrid? I ask because I think it is the same radios?
Sent from my DROID BIONIC using xda premium

If anyone is just now rooting and starting to make their way up the update ladder I would greatly appreciate it if you would make a backup of 6.893 and send it to me. Thank you!
Sent from my DROID BIONIC using xda premium

Dakota0206 said:
If anyone is just now rooting and starting to make their way up the update ladder I would greatly appreciate it if you would make a backup of 6.893 and send it to me. Thank you!
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Check your pms and please don't share in case there is some of my data still left in the backup. just download all the files and put them in a folder and put in your clockwork backup folder on your sd/ext, probably the best way is to restore with advanced restore and just restore system only.

rgb2448 said:
Check your pms and please don't share in case there is some of my data still left in the backup. just download all the files and put them in a folder and put in your clockwork backup folder on your sd/ext, probably the best way is to restore with advanced restore and just restore system only.
Click to expand...
Click to collapse
Mad thanks!
Sent from my DROID BIONIC using xda premium

Dakota0206 said:
Mad thanks!
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Let me know if it works or you need some more help

I'm in the same boat here too. I hope someone can find a way to fix it soon. I'd really appreciate a backup too, but I understand the concern about data.

Calla969 said:
I'm in the same boat here too. I hope someone can find a way to fix it soon. I'd really appreciate a backup too, but I understand the concern about data.
Click to expand...
Click to collapse
What steps have you done already. and what is your current system and what updates have you done.

rgb2448 said:
Let me know if it works or you need some more help
Click to expand...
Click to collapse
rgb2448 said:
What steps have you done already. and what is your current system and what updates have you done.
Click to expand...
Click to collapse
I have really been through the ringer today. I started off this morning by noticing that I had no data at all. I was on 6.893 and TH3ORYROM 2.1 and have been for a few days with no trouble until today when I lost data. I tried everything to get it back, but nothing. I called VZW to make sure there wasn't a network problem in my area and they suggested that I try everything that I had already done (bat. pull, sim card re-register, turn off LTE radio, etc). When they couldn't fix anything, they wanted to transfer me to tier 2 tech support, but they apparently need to talk to me on a different phone so they can diagnose this one, but I didn't have access to another phone. So I decided I would try to flash one of the updates hoping it would reflash the radio file and wake it up. When I got home, I used the R3L3AS3DRoot to restore to stock and tried to install 7.893, but the update failed. I searched around and tried every method I could to get any of the updates to install, but nothing worked, still no 3g either. Eventually, in my desperate attempt to fix this myself I decided to wipe everything and start over. I wiped the webtop partition. I think that's what really screwed me up, because nothing else I did was any different that what I've done in the past. After wiping everything, I went back to the R3L3AS3DRoot and tried to run it. No matter which option I selected, it seemed to run fine, but I couldn't boot past the fastboot screen. I tried to fxz using RSD Lite, but every flash I tried failed. Then, in a panic, I came across P3's moto-fastboot method used to "get you back on the update path". I ran that and it freaking worked!! Then I figured I'd try to get up to 7.893, but I've tried absolutely everything I can find mention of and nothing works. Every install fails. I am getting some intermittent 3G now though. And to top it all off, I discovered that none of the nandroid backups I've made will restore and most of them don't even exist. I just discovered that I needed to check "use external storage" for the backups to take. I thought I had been covering my ass by making backups, but they weren't valid. Currently I have stock, rooted phone with an intermittent 3G signal. System Version 5.5.886, baseband CDMA_N_03.1C.57RLTEDC_U_05.15.02, kernel [email protected] #1, and build number 5.5.1_84_DBN-55. As I sit now, my plan is to see how it acts tomorrow and if I still have a lot of trouble with data, I will return it to stock unrooted and take it into a Verizon store and see if they will let me try a new SIM card. I don't really know what else to do at this point.

Troubles going from JB to KK

Ok, so here's the breakdown:
I was on KK (KNOXRAID 5.1), and wanted to try a different ROM. I always like starting fresh on things, and accidentally went a little too far. I wiped /data, /system/, /cache...everything. So then I lost everything and was always stuck on "No OS installed!". Then I used the guide here: http://forum.xda-developers.com/showthread.php?t=2559715 to kind of restart myself.
That works ok, and now I'm on a rooted stock MJ5. My next thing was to try to get to KK again, and so I used the other guide here: http://forum.xda-developers.com/showthread.php?t=2712039. I've tried this literally about eight times, and every time I end up stuck on the boot / splash screen after finishing every single time. I really have no idea why, as I've followed the instructions exactly.
I've also tried going from a custom ROM, using different USB ports, etc...no luck.
Would someone mind pointing me in the right direction? I want to be on FireNote.
Some details:
Running Windows 8.1 Pro 64-bit
Using OEM cable
I've attached a screenshot of my "About" screen on my current stock rooted MJ5 setup.
Thank you!!

Here you go follow the link. http://forum.xda-developers.com/showthread.php?t=2627234
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

lildoggs said:
Here you go follow the link. http://forum.xda-developers.com/showthread.php?t=2627234
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm afraid I don't follow? Are you saying that there is a post somewhere in the FireNote thread where the solution is mentioned?

Firenote is based on mj5 so no need to go to kk. Just make a slot in ss then flash it there or if you're a bit of an adventurer flash it on stock slot. Just make a backup first.

posersk8r said:
Firenote is based on mj5 so no need to go to kk. Just make a slot in ss then flash it there or if you're a bit of an adventurer flash it on stock slot. Just make a backup first.
Click to expand...
Click to collapse
Yeah...wish I would have realized that obvious fact early on. Only realized a few hours ago.
Apart from all this though, I just tried it on another computer and everything worked great. Don't know what's going on with my laptop, but the desktop worked great. Problem solved.
Thanks anyway everyone!

[Q] Rooted/s-on. Can I update anything.

Can I install stock recovery and then try to take a ota to update. Will I loose root and will I loose my rom? Will I be able to reinstall a rom or will I need to reroot?

you can try, you shouldn't loose root or anything but once you have unlocked and flashed stuff I doubt stock recovery will like your system enough to take the update. try this http://forum.xda-developers.com/showthread.php?p=53518227
HOW Change ...... ???
Sent from my SM-T217S using XDA Free mobile app

From my understanding, as long as /system is stock, you can install the stock recovery and then take the OTA. Afterwards, you'll need to re-root your phone. Make a backup of your current setup before you get started. Once you've taken the update and get rooted again, you can always restore your backup.
Sent from my HTC device

Magnum enforcer is correct.
Sent from my 831C using XDA Premium 4 mobile app

I will give it a try this weekend and let you know how it goes.
Edit does not work but thanks for helping me.
Must be the fact that I am s on. We need that s off before we can do anything as far as updating

This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.

dilaynie said:
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
Click to expand...
Click to collapse
I just tried it to and did the same exact thing except I had boot loops as we'll.

when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk

scott_0 said:
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
But after all that we're you able to update the radio and second did it fix the signal issues?

jdmohn12 said:
But after all that we're you able to update the radio and second did it fix the signal issues?
Click to expand...
Click to collapse
yes, I was able to take the latest OTA, and no, it did not help with my signal at all, my device didn't drop calls or anything, but it has a hard time latching onto lte at times before and after the OTA.......
sent from HTC M8 using tapatalk

Do we know how to get passed the build.prop error?
Sent from my 831C using XDA Free mobile app

this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.

Tbaggington said:
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Click to expand...
Click to collapse
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk

scott_0 said:
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?

Tbaggington said:
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Click to expand...
Click to collapse
yes sir, power off the phone completely, hold down power and volume down, select fastboot
sent from HTC M8 using tapatalk

Hey everyone.
I've spent the better of the last three hour scouring the inter webs, Google, and these forums trying to find the answers to my questions - but to no avail (I've found partial answers, but I am afraid a partial answer could lead to a total brick).
Here we go:
I bought one of the first Sprint HTC One M8's through Amazon. Here are the details:
Model: 831C
Android Version 4.4.2
Software Version 1.12.651.17
Unlocked but S-On (Using TWRP)
Naturally, right out of the box I rooted it. However, I did not save the original ROM.
* I want to restore the phone to its original state so I can accept the OTA update and hopefully address the god-awful cell signal.
I've found a lot of stock recoveries online, but none that match 1.12.651.17.
Do I need to find that specific recovery to flash to my phone? Will another one work (e.g. 1.54.654.13)?
I've never worried about saving my stock recovery in the past (been rooting since the HTC Evo days) but it looks like not doing so finally caught up with me.
Thanks in advance.
PS I did find something 1.12.651.17 related here, but how to flash this to my phone (or whether or not it will brick) is beyond me. I've downloaded all 6 files and am waiting to figure out how the heck to get them to my phone.
http://forum.xda-developers.com/showthread.php?t=2736048

Came back from M and now cm12.1 won't boot

Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app

Try a factory image?

sookieball said:
Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
advice, thought, or a suggestion.. dont use toolkits until you know what you are actually doing. do things the right way, until you learn how to do it properly. then use all the toolkits you want. the problem is that toolkits dont teach you a single thing, and doing things right on any nexus is very easy.
my suggestion would be to wipe data/system then reflaah cm again.

sookieball said:
Title says short part.
Used wugs NRT to downgrade and revert back to LMZ28E and used NRT to root and install twrp,
Tried flashing cm12.1 and it gets to the boot animation and won't boot past that. :-/ the down grade flashed old boorloader and radio and everything....
Don't know what the problem would be.
Advice? Thoughts? Suggestions?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Junk ROM anyway.. Lol

simms22 said:
advice, thought, or a suggestion.. dont use toolkits until you know what you are actually doing. do things the right way, until you learn how to do it properly. then use all the toolkits you want. the problem is that toolkits dont teach you a single thing, and doing things right on any nexus is very easy.
my suggestion would be to wipe data/system then reflaah cm again.
Click to expand...
Click to collapse
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Oh and thank you for the wipe/advice.
I did :-/ go fig
Reflashed before I restored backup but no go.
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Did you downgrade the bootloader back to 5.1.1?

Evolution_Tech said:
Did you downgrade the bootloader back to 5.1.1?
Click to expand...
Click to collapse
Yes, manually first and when it wouldnt* boot past animation, last resort was NRT
So I'm assuming NRT flashed boot loader associated to LMZ28E
Edit: maybe if I downgrade down to 5.0.1? Then reroot and recovery?
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
Yes, manually first and when it would boot past animation, last resort was NRT
So I'm assuming NRT flashed boot loader associated to LMZ28E
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Do we know for a fact the that we can downgrade the bootloader from m? We learned we couldn't downgrade from 5.1 bootloader.

rootSU said:
Do we know for a fact the that we can downgrade the bootloader from m? We learned we couldn't downgrade from 5.1 bootloader.
Click to expand...
Click to collapse
I reread the thread like 3x.
And it was mentioned that another user used NRT to downgrade successfully.
I thought the same thing, but didn't try it till I read that thread till 4am. This morning decided to take the plunge.
I was thinking also, if I just reflash bootloader and radio and put M back on, then just try manually flashing 5.1?
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
I actually am not a noob,
And I do know how to flash factory images manually using fastboot commands.
I downloaded all necessary files to flash manually.
I did that,
Wouldn't boot past boot animations.
Tried again with tmobile official (from google) files,
Same thing. So last resort was wugs.
Clean flashed cm12.1.
And wouldn't boot.
I appreciate your advice, but don't assume because I didn't succeed on a simple thing as a flash, that one is not familiar with this. The only thing I can think of that would have prevented boot was maybe I had a bad DL of cm.
But unlikely.
Planned on downloading a diff ROM and gapps.
If it doesn't I'll be flashing factory images of LMY47M manually and reroot and recovery and start from there.
Oh and thank you for the wipe/advice.
I did :-/ go fig
Reflashed before I restored backup but no go.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
i did flash the new bootloader, but i went back and forth from M to terminus(rom) about 5 times yesterday. flaah the new bootloader again, and keep it. you trying to downgrade it might be the issue. btw, i flashed m, and the bootloader, via twrp recovery, its much easier and faster that way. after, i made a backup in recovery. so now all i do to go back and forth is restore the backups.
oh, and i meant you no disrespect. while it doesnt include everyone, most people using toolkits around here are noobs. and they are the ones that usually get stuck. so, i apologize

simms22 said:
i did flaah the new bootloader, but i went back and forth from M to terminus(rom) about 5 times yesterday. flaah the new bootloader again, and keep it. you trying to downgrade it might be the issue. btw, i flashed m, and the bootloader, via twrp recovery, its much easier and faster that way. after, i made a backup in recovery. so now all i do to go back and forth is restore the backups.
Click to expand...
Click to collapse
I think that's where I messed up from the beginning when I flashed M.
I didn't notice the modified boorloader that doesn't force encryption and it was all downhill from there.
That being said,
Should I flash modified boorloader to not force encrypt, and blah blah blah?
Sent from my Nexus 6 using XDA Free mobile app

Disregard

sookieball said:
I think that's where I messed up from the beginning when I flashed M.
I didn't notice the modified boorloader that doesn't force encryption and it was all downhill from there.
That being said,
Should I flash modified boorloader to not force encrypt, and blah blah blah?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
moddified bootloader? huh? there is a modified kernel thats not supposed to force encryption. i did flash it, even though i am encrypted(by choice).

http://forum.xda-developers.com/showthread.php?p=61027468
I'm assuming that's what this is.
Lol I never tried or even downloaded it so not 100% but yeah
Lol **** my bad. Lol its boot.IMG not boorloader hahaha! #nooberror for reals lol
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
http://forum.xda-developers.com/showthread.php?p=61027468
I'm assuming that's what this is.
Lol I never tried or even downloaded it so not 100% but yeah
Lol **** my bad. Lol its boot.IMG not boorloader hahaha! #nooberror for reals lol
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
thats probably the same one i flashed. btw, in the op he has a twrp flashable version of the bootloader, the kernel, the radio, and the rom.. http://4ndr01d.com/repos/shamu/jdx/

simms22 said:
thats probably the same one i flashed. btw, in the op he has a twrp flashable version of the bootloader, the kernel, the radio, and the rom.. http://4ndr01d.com/repos/shamu/jdx/
Click to expand...
Click to collapse
God I wish it was a faster download link -_- lol
BTW, when I first downloaded and flashed boorloader via twrp (radio also) rebooted twrp to flash ROM, and sdcard was wiped
It shouldn't do that right?
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
God I wish it was a faster download link -_- lol
BTW, when I first downloaded and flashed boorloader via twrp (radio also) rebooted twrp to flash ROM, and sdcard was wiped
It shouldn't do that right?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
no, it shouldnt unless you accidentally did it yourself. ive seen people do that too often. if you go into the wipe menu, be sure to go into advanced options, where you can pick what you want wiped.or itll wipe everything.

K so everything's downloaded....
Going to flash in a sec all via twrp.
Report back .
Wish me luck lol
Sent from my Nexus 6 using XDA Free mobile app

sookieball said:
K so everything's downloaded....
Going to flash in a sec all via twrp.
Report back .
Wish me luck lol
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
fingers crossed

What cracks me up the most is people that posses limited knowledge about fastboot flashing partition images are just seemingly willy nilly flashing images not really fully understanding what they are doing/flashing. We all have to learn somehow but I wouldn't do it at the expense of flashing a boot loader. If anything went wrong during a boatloader flash you would definitely have an unrecoverable hard brick.
Moral of the story.... People, read the how to's and SLOW down... Think about what you are doing. After reading the above replies its clear to me that people are getting a bit confused with a boot.img and a bootloader.img. its OK guys. Just be careful