Hi ! I have a specific question about 5.1 lollipop. If I install cyanogenmod 12.1 and then decide to revert back to KitKat, will there be a problem with bootloader, csc or anything else ? I never tested Android Lollipop on any device, so I'm very intersted to try it. Thanks.
MrYoan said:
Hi ! I have a specific question about 5.1 lollipop. If I install cyanogenmod 12.1 and then decide to revert back to KitKat, will there be a problem with bootloader, csc or anything else ? I never tested Android Lollipop on any device, so I'm very intersted to try it. Thanks.
Click to expand...
Click to collapse
No problem doing that
Hello,
no problems on Lolipop-ROMs. Try it out
No problems to revert back, but why would you do that? ?
Trafalgar Square said:
Hello,
no problems on Lolipop-ROMs. Try it out
Click to expand...
Click to collapse
larswars said:
No problems to revert back, but why would you do that?
Click to expand...
Click to collapse
I want to finally "touch" Android 5. Thank you both for the answer !
Hey I did go back to kitkat from lollipop because it didn't run as smoothly as my last rom, but be careful when you do that. I did a full wipe with fastboot and flashed an older version of my recovery.
I hope you won't encounter any problems.
Galaxplus said:
Hey I did go back to kitkat from lollipop because it didn't run as smoothly as my last rom, but be careful when you do that. I did a full wipe with fastboot and flashed an older version of my recovery.
I hope you won't encounter any problems.
Click to expand...
Click to collapse
Too late but thanks.. I nearly bricked my device after something failed while installing TWRP. Now ODIN is not working and I cant revert to stock, install Recovery or anything else. It freezes somewhere and the phone is not booting but it goes in Download Mode. After hours trying to put ANY custom recovery I succeded in installing CWM. But that was not full success. I couldn't install any ROM including Cyanogen Mod 12, 11, N4 Elite ROM and etc. It always reported: Error in mounting /system, even after I formatted it. The only working ROM was one of these - http://forum.xda-developers.com/gal...m-samsung-stock-4-4-4-rom-collection-t3124027 Now it is with this ROM, barely working, but ODIN is still not working, it totally freeze on one place, everytime at different moment. Samsung Kies also freezes on 4% on firmware restoration. I'm not very sure is my phone now bricked or not, it's working except Download Mode. At least I'm happy now that my phone boot normal even with KitKat, it's better than nothing.
Sh**t, sorry that happened. One thing you could do is for one get rid of Kies, it won't do anything good. Did you try to fastboot erase system, data, cache and userdata before flashing anything?
Galaxplus said:
Sh**t, sorry that happened. One thing you could do is for one get rid of Kies, it won't do anything good. Did you try to fastboot erase system, data, cache and userdata before flashing anything?
Click to expand...
Click to collapse
No. I used fastboot once years ago on LG device and it was kinda hard for me. I thought fastboot is only for old non-samsung devices..
Oh, there's plenty ^^ if you don't really know what fastboot is I suggest you google adb and fastboot, they are tools you need when you mess around with an android device. Here is the short version: Kies is Samsung software, you can't really do anything useful with it, and once you began surfing on XDA, you should have shredded that thing away from your computer (sorry for the funny use of english, I'm french )
On the other hand, fastboot is a protocol that allows you to send commands trough your computer (windows works, linux is easier, macOS I have no idea) when the phone is in... Download mode! For that you need fastboot.exe (again, google that) and a nice tutorial (plenty of those around) as well as the correct drivers from Samsung. One thing though, I advise against trying the command "fastboot -w" (you'll get it when you see it) because I think that is quite brutal. Better fastboot erase system, etc.
Galaxplus said:
Oh, there's plenty ^^ if you don't really know what fastboot is I suggest you google adb and fastboot, they are tools you need when you mess around with an android device. Here is the short version: Kies is Samsung software, you can't really do anything useful with it, and once you began surfing on XDA, you should have shredded that thing away from your computer (sorry for the funny use of english, I'm french )
On the other hand, fastboot is a protocol that allows you to send commands trough your computer (windows works, linux is easier, macOS I have no idea) when the phone is in... Download mode! For that you need fastboot.exe (again, google that) and a nice tutorial (plenty of those around) as well as the correct drivers from Samsung. One thing though, I advise against trying the command "fastboot -w" (you'll get it when you see it) because I think that is quite brutal. Better fastboot erase system, etc.
Click to expand...
Click to collapse
Yeah, I know at least this. Actually, I'm using adb almost everyday. Kies once helped me when my device was blocked (not bricked) and that's why I decided to try it, I really don't use it. And so on, if someday I decide to change the ROM I must do this:
1. "fastboot -w"
2. Install ROM from Recovery or ODIN, right ?
For now on, this rom is really good and it have the things I use.
I'd rather try "fastboot erase" if I were you. The only roms you can flash with Odin are te stock roms in .tar format. For .zip files, yes, use the recommended recovery.
Galaxplus said:
I'd rather try "fastboot erase" if I were you. The only roms you can flash with Odin are te stock roms in .tar format. For .zip files, yes, use the recommended recovery.
Click to expand...
Click to collapse
Ok, but which partition to erase with this command ?
What I wrote earlier, system, data, userdata and cache.
Related
My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as UnderstoodI was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial SolutionAt first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
QuestionSo how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682
1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app
stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
abispac said:
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
Click to expand...
Click to collapse
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
reefuge said:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
Click to expand...
Click to collapse
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
abispac said:
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
Click to expand...
Click to collapse
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
reefuge said:
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
Click to expand...
Click to collapse
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
abispac said:
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
Click to expand...
Click to collapse
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
reefuge said:
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
Click to expand...
Click to collapse
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Its going to take 5hrs to upload my backup
abispac said:
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Click to expand...
Click to collapse
ok ii'm thinking corrupted partitions too.... but if you are willing to try i've made a xt1063 easy installer script for you to try now normally i work on xt1068 and would test on my xt1068 - so have NO xt1063 its UNTESTED - use at own risk.....
just stock firmware / drivers / adb and mfastboot ( same as my xt1068 script) I see no reason it should not be compatible.
download to pc / unzip to folder / read instruction inside
https://mega.co.nz/#!Tok2DJ6T!ggMoQDfAzuA7cmQQjbGCbXolWZTnx_567vG02CiURVsxt1063 4.4.4 easy installer
I repeat it YOUR choice - if it works- great - if runs ok but rom remains same would suggest somethings corrupt - if it doesnt work at all back to square 1....
now im presuming your boot loader is unlocked, as will fail if locked or relocked - if you use and get error please report what they are, i would have done 5.0.2 but its only 50% downloaded with a 1 hr+ to still go, estimate 2 hrs from time of this post until I can post a link
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
abispac said:
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
Click to expand...
Click to collapse
just to let you know TWRP is now 2.5.8.0 fixes some bugs cause older versions know to break permissions in Lollipop!!
https://mega.co.nz/#!Dx03wTbD!3sDFubGomhegQqdoGzNb1RWnQwApzyaTlVq69uX1TqkFlash-able version (unzip to pc and flash from there) 2.5.8.0
https://mega.co.nz/#!n5cUQCAY!uf66vEcQlmtu6VZMLPxksEFMEioZUFpystzTP6kwU4I Temporary boot version (no flash) 2.5.8.0.
will look but cant promise
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
abispac said:
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
Click to expand...
Click to collapse
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
reefuge said:
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
Click to expand...
Click to collapse
Yeah i tried those erase commands many many times and same result, i cant replace recovery at all, only boot of it, so when i do " mfastbooot flash recovery twrprecovery.img " then try to boot of recovery, i boot into factory recovery not, twrp, but if i do, "mfasboot boot twrprecovery.img" i can see the recovery img gets flashed and the phone boots of twrp. Weird behavior. So when i notice that i tried to flash a rom with mfastboot, and at the end i gave the command mfasboot boot recovery.img (the original rom recovery) then it gets flashed, and phone reboots, but i gets stuck at the motorola logo. This phone its playing hard to get....
heres, my backup https://mega.co.nz/#!md0AwbLR!uWe9PLklIugOziPLV6O_plbU-Zz9EXbqRvUVpYxECk0 hope you can find something.
Im going to take this phone to a shop to see if they can fix it as i have lost all hope, thanks refuuge for your help.
My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.
Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.
I tried using tge NRT to flash it back to stock but it didn't work.
I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1
When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...
celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.
prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.
So I feel like I am really screwed on this.... attempted flashing stock via RSDLite. It began flashing fine until about halfway through the system.img ...all of a sudden it loses fastboot and my computer freaks out saying that an unkown standard usb device is attached. I figured that I would just flash a batch through recovery, but now there is not recovery image either.
So... I have no fastboot mode and no recovery mode and an unrecognizable usb device. Please help me
Edit: I have a feeling its due to a driver issue... during the downgrade the required driver probably changed... and thus disconnected in the middle of flash. If this is the case, then I feel like an idiot
diabl0w said:
So I feel like I am really screwed on this.... attempted flashing stock via RSDLite. It began flashing fine until about halfway through the system.img ...all of a sudden it loses fastboot and my computer freaks out saying that an unkown standard usb device is attached. I figured that I would just flash a batch through recovery, but now there is not recovery image either.
So... I have no fastboot mode and no recovery mode and an unrecognizable usb device. Please help me
Click to expand...
Click to collapse
Try setting up another computer. You should be able to go into bootlader mode by pressing power and volume down buttons at the same time. Hopefully you have enought battery. If that doesnt work someone should be able to help you out.
Downgrading the bootloader on Motorola devices (Nexus 6 included) results in a permanent (well, unless you can upgrade the bootloader to what it was originally) brick.
r3pwn said:
Downgrading the bootloader on Motorola devices (Nexus 6 included) results in a permanent (well, unless you can upgrade the bootloader to what it was originally) brick.
Click to expand...
Click to collapse
Wow I hope that my edit was right instead... I know for a fact that it failed during the system image portion of the flash. all I did was follow the instructions posted somewhere on this forum which basically just said... download 21.12 firmware, go to fastboot, flash with rsdlite. Guess the fact that they left out remove bootloader image is no big deal.. NOT
diabl0w said:
Wow I hope that my edit was right instead... I know for a fact that it failed during the system image portion of the flash. all I did was follow the instructions posted somewhere on this forum which basically just said... download 21.12 firmware, go to fastboot, flash with rsdlite. Guess the fact that they left out remove bootloader image is no big deal.. NOT
Click to expand...
Click to collapse
It's nothing they did wrong. At the time of writing it, that was probably the latest version. Can you still flash things via rsdlite? If so, take a look at this copy of the latest update.
r3pwn said:
It's nothing they did wrong. At the time of writing it, that was probably the latest version. Can you still flash things via rsdlite? If so, take a look at this copy of the latest update.
Click to expand...
Click to collapse
Okay so good news... I installed the older sdk drivers and my phone will now connect to fastboot mode again. wooo!!! Now, to make sure I do this right, @r3pwn , the link you just sent me was a superuser image, right? Background story as to why I am doing this, I have root and I ended up breaking google play services pretty bad and reinstalling would not fix the problem and neither would cache clear or system.img flash. So I was just gonna try to start fresh. So, I attempted to flash 21.12 firmware and thats how I ended up here. What should I do next? Flash that SU firmware or flash the 21.12 firmware? Should I remove the bootloader and boot images from those .xml files? Thanks for your time, I should be good after that information
diabl0w said:
Okay so good news... I installed the older sdk drivers and my phone will now connect to fastboot mode again. wooo!!! Now, to make sure I do this right, @r3pwn , the link you just sent me was a superuser image, right? Background story as to why I am doing this, I have root and I ended up breaking google play services pretty bad and reinstalling would not fix the problem and neither would cache clear or system.img flash. So I was just gonna try to start fresh. So, I attempted to flash 21.12 firmware and thats how I ended up here. What should I do next? Flash that SU firmware or flash the 21.12 firmware? Should I remove the bootloader and boot images from those .xml files? Thanks for your time, I should be good after that information
Click to expand...
Click to collapse
That's not the root firmware, that's just plain stock. I would recommend you flash that image (the one I linked) then re-root.
r3pwn said:
That's not the root firmware, that's just plain stock. I would recommend you flash that image (the one I linked) then re-root.
Click to expand...
Click to collapse
I realized that after I downloaded the file and took a look at it further... thanks for your help and for bearing with me. It worked!
can someone give me steps or link how to flash MM?
I am on 6.0.1 without twrp and just want to factory flash image
thanks
fromgeorgia said:
How to Flash 6.0.1 MM
can someone give me steps or link how to flash MM?
I am on 6.0.1 without twrp and just want to factory flash image
thanks
Click to expand...
Click to collapse
You are already on 6.0.1 Marshmallow. You said it yourself. You said you even still have stock recovery. So, seems like you don't need to do anything?
Maybe you wrote something wrong or left something out? Please clarify, and we'll be glad to help if we can.
ChazzMatt said:
You are already on 6.0.1 Marshmallow. You said it yourself. You said you even still have stock recovery. So, seems like you don't need to do anything?
Maybe you wrote something wrong or left something out? Please clarify, and we'll be glad to help if we can.
Click to expand...
Click to collapse
you are right i am, but phone crashes and when receiving phone calls and restarts sometimes so i want to try to reflash it. thanks
fromgeorgia said:
you are right i am, but phone crashes and when receiving phone calls and restarts sometimes so i want to try to reflash it. thanks
Click to expand...
Click to collapse
OK, then you need to flash this via RSDLite or ADB.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
You can google how to download/use RSDLite or ADB. But that's the most recent stock firmware you need to flash with either of those tools.
ChazzMatt said:
OK, then you need to flash this via RSDLite or ADB.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
You can google how to download/use RSDLite or ADB. But that's the most recent stock firmware you need to flash with either of those tools.
Click to expand...
Click to collapse
i've tried RSDLite but it was unable to detect the phone(drivers was right and phone was in recovery).
i will try ADB than. with ADB should i flash every partition manually?
fromgeorgia said:
i've tried RSDLite but it was unable to detect the phone(drivers was right and phone was in recovery).
i will try ADB than. with ADB should i flash every partition manually?
Click to expand...
Click to collapse
As far as I know you need to be on the bootloader screen, not recovery screen. Maybe that was your problem? RSDLite just automates a bunch of stuff ADB does.
Also, sometimes you need to use msfastboot instead of fastboot commands. I sort of remember why, but I don't want to state anything incorrectly. But try msfastboot if fastboot doesn't work.
For ROMs I use TWRP, so I'm not an ADB expert -- but I have used it. However, it's been over two years since I've had to flash a full firmware image via ADB (but I have flashed individual elements since then like modems, boot logos, etc.), so I'm just going to say yes flash every partition manually.
ChazzMatt said:
As far as I know you need to be on the bootloader screen, not recovery screen. Maybe that was your problem? RSDLite just automates a bunch of stuff ADB does.
Also, sometimes you need to use msfastboot instead of fastboot commands. I sort of remember why, but I don't want to state anything incorrectly. But try msfastboot if fastboot doesn't work.
It's been over two years since I've had to flash a full firmware image via ADB (but I have flashed individual elements since then), so I'm just going to say yes flash every partition manually.
Click to expand...
Click to collapse
thanks you're good man :good::laugh: