I haven't been able to find stock .img files for anything...
Most especially need a stock boot.img and a stock recovery.img
It would nice to have all of them though. Where can these be found?
Yes i also would love those files, or another way to get my phone COMPLETELY back to stock. Recovery and everything... if possible
I could use a stock boot.img as well... that is the correct size to flash with fastboot.
+1
10chars
Koush has the the stock boot.img: http://koush.tandtgaming.com/samsung/crespo/
But it wont flash with fastboot.
He said we need to truncate it so it will flash via fastoot.
Anyone knows how to do this?
clubtech said:
+1
10chars
Koush has the the stock boot.img: http://koush.tandtgaming.com/samsung/crespo/
But it wont flash with fastboot.
He said we need to truncate it so it will flash via fastoot.
Anyone knows how to do this?
Click to expand...
Click to collapse
Yeah, I have that one as well. But it doesn't work with fastboot. It's too big. I'm going to wait until someone links the correct boot.img for fastboot.
I just posted a thread with aosp images. The factory images everyone wants aren't available from google yet unfortunately, however the ones I posted should work just fine.
People reported not being able to flash the OTA with your AOSP img's
jroid said:
I just posted a thread with aosp images. The factory images everyone wants aren't available from google yet unfortunately, however the ones I posted should work just fine.
Click to expand...
Click to collapse
Will those allow you to update the new OTA update?
I'm pretty sure that is why everyone wants the stock boot.img right now.
edit: Nope that boot.img won't allow you to update, at least not through CWR. I get an error. Also breaks wifi (assuming wifi works if you flash all the .imgs).
Luxferro said:
Will those allow you to update the new OTA update?
I'm pretty sure that is why everyone wants the stock boot.img right now.
edit: Nope that boot.img won't allow you to update, at least not through CWR. I get an error. Also breaks wifi (assuming wifi works if you flash all the .imgs).
Click to expand...
Click to collapse
I fixed the wifi bug. See my thread's OP. As far as the not being able to update, it's a recovery issue, and nothing to do with the boot.img
jroid said:
I fixed the wifi bug. See my thread's OP. As far as the not being able to update, it's a recovery issue, and nothing to do with the boot.img
Click to expand...
Click to collapse
k, I'll check out your fix. And then flash back the original recovery and try again.
jroid said:
I fixed the wifi bug. See my thread's OP. As far as the not being able to update, it's a recovery issue, and nothing to do with the boot.img
Click to expand...
Click to collapse
Thanks for fixing the wifi on those, but the update still won't flash using this boot.img (sadly) and CWM.
Koush is claiming that we really need the stock boot.img.
To do the update just do the nandroid for it that the other guy posted around here... It works well
here you go: http://forum.xda-developers.com/showthread.php?t=884416
Worked great! Allowed me to update to 2.3.1.
also this will work:
http://forum.xda-developers.com/showpost.php?p=10029195&postcount=19
Related
I can no longer write any custom roms to my N6. Started with PURE 3.5 but now effects any rom i try to flash. I have brought my N6 back to factory state multiple times even relocking it. Only thing I can do is Fastboot flash N6 image from google manually piece by piece. I do have working 5.01 and phone works. Roms either hang or have errors. or just write the boot.img file. TWRP works other wise i can backup and restore, I am using 2.8.3.1. I have searched all over for a fix....
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
dipstik said:
There used to be some weird mounting stuff that would make roms not boot. Thought that was worked out in pure shamu 3.1 ish.
Where do the roms hang? Did you ever fix permissions using twrp? Any kind of log you can pull?
Click to expand...
Click to collapse
I had no problem updating Pure for over a month from like 2.0 to 3.4.
they all hang when writing to system as far as i can tell. happens regardless of Pure....from a fresh clean image of 5.0 or 5.01 i can not flash any roms. driving me nutzo....i can no longer flash pure 3.4 either but i can restore the phone from a nandroid backup i had on my pc and run Pure 3.4 just fine.
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Pilz said:
Did you wipe everything except internal storage first? I had this issue earlier until I realized that I forgot to do that when coming from the stock ROM.
Click to expand...
Click to collapse
yes and both cache.....
also made sure system not mounted.
very frustrating.
Bignoze73 said:
yes and both cache.....
also made sure system not mounted.
very frustrating.
Click to expand...
Click to collapse
That is very odd, did you try reflashing TWRP or using a different version.
Pilz said:
That is very odd, did you try reflashing TWRP or using a different version.
Click to expand...
Click to collapse
mutiple times......tried all versions of TWRP too.
I can write a custom kernal like elementalx no problem.....just not roms.
Bignoze73 said:
mutiple times......tried all versions of TWRP too.
Click to expand...
Click to collapse
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Pilz said:
It doesn't make sense considering you also flashed back to stock. Have you also tried to flash a ROM from your PC rather than from your phone? There has to be some reasonable explanation for why it's not working.
Click to expand...
Click to collapse
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Bignoze73 said:
how do you do that? the custom roms dont have system.img file like N6 image. The Pure 3.92 is in .dat format, another rom is folders. I also get checksum errors when extracting.
I also noticed in the last 24 hours there are 2 other threads with people have almost the same issues flashing roms. I think it has something to do with TWRP but no matter becuase no version works for me.
Click to expand...
Click to collapse
If you restore your stock recovery on your phone you could try this.
Make sure TWRP is not installed on your phone and that the stock recovery is installed and working:
Have TWRP in your platform tools folder named however you want
Then use "fastboot boot recovery 'whatever you named TWRP' "
This will boot TWRP without installed it. Then try to flash the ROM using TWRP. You can also use the"adb push" to sideload the ROM onto your phone so you can find it via TWRP.
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Bignoze73 said:
nope did not work.....roms just hang or flash new boot.img only.
i even tried erasing recovery partion and reflashing stock than twrp 2.8.3.1......that did not work either....something is stopping TWRP from writing to system.
thanks for your help
Click to expand...
Click to collapse
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Pilz said:
You're welcome, have you tried to contact some of the devs here to see if maybe they could help? I think the worst case scenario would be to RMA the phone.
Click to expand...
Click to collapse
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
laureanop said:
RMA the phone??? ?What are you gonna tell them?? ? That you can't flash any custom Roms through TWRP?? ?
Click to expand...
Click to collapse
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Pilz said:
No obviously not look, but if you have other issues (in assuming you might if you can't flash a ROM) then that's the worst case scenario option.
Click to expand...
Click to collapse
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
laureanop said:
This is a tough one cause if his factory image works without issues they're gonna have no reason to send him a replacement
Click to expand...
Click to collapse
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Pilz said:
That's true, but there must be something wrong if he can't flash anything else so I'm sure he could find some issues.
Click to expand...
Click to collapse
Is there a tool or command to do a full memcheck of both ram and storage
rgraville said:
Is there a tool or command to do a full memcheck of both ram and storage
Click to expand...
Click to collapse
I'm not sure I've never had the need to do one from adb or fastboot
Pilz said:
I'm not sure I've never had the need to do one from adb or fastboot
Click to expand...
Click to collapse
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Bignoze73 said:
yeah its pretty nuts....how can I return a phone that works fine other than the fact it wont flash a custom rom?
Must be another way to write a rom but TWRP......
thanks!
Click to expand...
Click to collapse
I assume you are also out of the return window. Well if you are unlucky or lucky (depending on how you view it) you could have an issue eventually. They will RMA for burn in, camera issues etc... The camera issue was common in the earlier production models that I had. There should be another method, I would look into it if you have time.
So my phone is rooted with unlocked bootloader running faux kernel. I just received the ota update and clicked the button for restart and install. When I did that it brought me to my main option list in twrp. I didn't know what to do so I hit reboot system. It rebooted but nothing showed updating when I did that. Showing I'm still on 5.0.0.
What did I need to do? How do I still update now?
You cannot accept ota if you're modified.
You'll have to flash a ROM.zip or fastboot flash system.and boot image.from the factory images
rootSU said:
You cannot accept ota if you're modified.
You'll have to flash a ROM.zip or fastboot flash system.and boot image.from the factory images
Click to expand...
Click to collapse
See that's what I thought but was confused that I got the ota. I'm having a problem finding the rom.zip. Only finding images and I don't want that. Do you happen to have a link?
HyperM3 said:
See that's what I thought but was confused that I got the ota. I'm having a problem finding the rom.zip. Only finding images and I don't want that. Do you happen to have a link?
Click to expand...
Click to collapse
If you download the image from google there is a zip drive with the files you are looking for inside of them. You can fastboot them individually.
Or you could just flash one of the many roms on here that are using the newer 5.0.2
xxfwmxx said:
Or you could just flash one of the many roms on here that are using the newer 5.0.2
Click to expand...
Click to collapse
That's the thing, I was trying to keep it relatively stock for a while. I don't see any reliable roms out there yet.
Give Sinless rom a try. There is a thread on here for it. It is based off of the office 5.0.1 image and not aosp. Great speed and features and decrypted
HyperM3 said:
So my phone is rooted with unlocked bootloader running faux kernel. I just received the ota update and clicked the button for restart and install. When I did that it brought me to my main option list in twrp. I didn't know what to do so I hit reboot system. It rebooted but nothing showed updating when I did that. Showing I'm still on 5.0.0.
What did I need to do? How do I still update now?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-5-0-1-lrx22-stock-root-t2980206
^^ thats stock rooted, that you can flash thru TWRP. I don't personally use it because I rooted and modified my own.
t2noob said:
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-5-0-1-lrx22-stock-root-t2980206
^^ thats stock rooted, that you can flash thru TWRP. I don't personally use it because I rooted and modified my own.
Click to expand...
Click to collapse
Great, thanks for that!
5.02 is out?
cobyman7035 said:
5.02 is out?
Click to expand...
Click to collapse
Only aosp
I made a thread outlining how to update to 5.0.1 after rooting/unlocking yesterday after noticing the same problem:
http://forum.xda-developers.com/nexus-6/help/how-to-flash-ota-updates-rooted-custom-t2996149
Should help
I need the stock recovery image (from 23.16.3.victara_retca.retca.en.CA) so I can flash the 6.0 update since it won't work with TWRP.
Any help? Google isn't providing me with much.
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
ellisbodds said:
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
Click to expand...
Click to collapse
I have no clue. I doubt it would have to be the retCA version. I'm sure everything besides radio and system will be the same.
This is from the latest RETCA XT1097 5.1 firmware:
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
ellisbodds said:
Does it have to be from the Canadian variant (not sure if the recovery images are different between variants)?
Tried looking here for the correct zip, which should contain the recovery image?
Click to expand...
Click to collapse
Gus.Ottawa said:
This is from the latest RETCA XT1097 5.1 firmware:
VICTARA_RETCA_XT1097_5.1_LPE23.32-48.3_cid14_CFC.xml.zip
Click to expand...
Click to collapse
Thank you both! I'll play around with these files and make it work
DonDizzurp said:
Thank you both! I'll play around with these files and make it work
Click to expand...
Click to collapse
Any update on whether this worked for you? I'm in the same boat
jullyfush said:
Any update on whether this worked for you? I'm in the same boat
Click to expand...
Click to collapse
Worked perfectly.
My process
- Flash stock 5.1 using fastboot (Steps can be found on Motorola's site or somewhere on XDA)
- Install Marshmallow OTA
- Flash cracked boot.img for Marshmallow. This step is needed in order for TWRP to stick and for you to root without getting stuck on the warning screen. (I'll find the link for you if you can't. It's somewhere on XDA.)
- Flash TWRP
- Create backup so I don't have to go through this process next time haha
DonDizzurp said:
Worked perfectly.
My process
- Flash stock 5.1 using fastboot (Steps can be found on Motorola's site or somewhere on XDA)
- Install Marshmallow OTA
- Flash cracked boot.img for Marshmallow. This step is needed in order for TWRP to stick and for you to root without getting stuck on the warning screen. (I'll find the link for you if you can't. It's somewhere on XDA.)
- Flash TWRP
- Create backup so I don't have to go through this process next time haha
Click to expand...
Click to collapse
Awesome! Thanks for the tip. I got as far as the 6.0 OTA (RETCA), and am now trying to get root back again. Where did you find the cracked boot.img?
Cheers!
jullyfush said:
Awesome! Thanks for the tip. I got as far as the 6.0 OTA (RETCA), and am now trying to get root back again. Where did you find the cracked boot.img?
Cheers!
Click to expand...
Click to collapse
Grab it from here
http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
DonDizzurp said:
Grab it from here
http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Click to expand...
Click to collapse
Something odd has happened since upgrading to 6.0.
'adb devices' still sees my phone, but 'fastboot devices' no longer sees anything, and making a desktop back-up with adb now creates a file containing 0 bytes.
Everything else seems fine. Are there some new permissions I need to give before this will work?
Thanks again.
Edit: I managed to get fastboot working, however now I've run into a new problem.
To confirm, when you say flash the cracked boot.img for Marshmallow, I should execute 'fastboot flash boot boot.img' for the cracked boot.img?
I'm getting the error: mismatched partition size (boot)
I can still enter TWRP with fastboot, but it's not permanent without the cracked boot.img
Am I missing a step?
Edit #2: Finally got TWRP to stick another way and have root now. Thanks for everything!
Hey guys, I was hoping to flash a pure stock 7.x preferably via twrp.
A buddy of mine a year ago and me to flash pure Nexus for him but now needs a stock phone for business security net purposes.
Is there a link for this? I've searched and have come up short.
I'm guessing it'll have to update bootloader, radio and kernel as well?
I know how to do this via command line. Was really hoping for a way to do it on the fly since this is not my phone and taking a PC for a TWRP ready device is a hassle.
mrkhigh said:
Hey guys, I was hoping to flash a pure stock 7.x preferably via twrp.
A buddy of mine a year ago and me to flash pure Nexus for him but now needs a stock phone for business security net purposes.
Is there a link for this? I've searched and have come up short.
I'm guessing it'll have to update bootloader, radio and kernel as well?
I know how to do this via command line. Was really hoping for a way to do it on the fly since this is not my phone and taking a PC for a TWRP ready device is a hassle.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Pkt_Lnt said:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks for the links,
But I was really hoping TWRP flash able.
Does TWRP allow flashing these images?
mrkhigh said:
Thanks for the links,
But I was really hoping TWRP flash able.
Does TWRP allow flashing these images?
Click to expand...
Click to collapse
Google search says that TWRP can not flash factory images.
Check the TWRP FAQ if you'd like.
http://teamw.in/FAQ/
Pkt_Lnt said:
Google search says that TWRP can not flash factory images.
Check the TWRP FAQ if you'd like.
http://teamw.in/FAQ/
Click to expand...
Click to collapse
That's what I thought.
Thanks for the links,
But I'm still looking for TWRP flashable if anyone knows of one?
This should be a relatively easy thing so I'm surprised it doesn't exist
there is no reason for it to HAVE to be twrp flashable, just google for "NEXUS ROOT TOOLKIT" you will see on there restore to stock, and re-lock boot-loader, not positive but i think twrp cant flash stock unrooted images, i could be wrong
leo5111 said:
there is no reason for it to HAVE to be twrp flashable, just google for "NEXUS ROOT TOOLKIT" you will see on there restore to stock, and re-lock boot-loader, not positive but i think twrp cant flash stock unrooted images, i could be wrong
Click to expand...
Click to collapse
TWRP can flash a stock image if someone creates it. Unless there is something odd about the nexus, but I doubt that. The only thing that shouldn't be flashed stock would be recovery.
I don't think I need to use some toolkit... adb and fastboot commands are simple enough.
I was hoping to avoid needing a PC at another persons house, I mean that is kinda the point of twrp.
I am surprised this doesn't exist. It does for every other device I've owned. It's honestly just a wiped clean, twrp backup of a stock device with TWRP installed.
If I owned the device I would make it for you guys. It seems something that is lacking that is really handy.
I guess I'll round up a laptop. Thanks for the links and suggestions.
Google has done that for you already. Just unpack the archive you choose and the four images are in there.
https://developers.google.com/android/images
I thought we've already decided I cannot flash these images with TWRP....
mrkhigh said:
I thought we've already decided I cannot flash these images with TWRP....
Click to expand...
Click to collapse
http://www.droidviews.com/now-flash-image-files-using-twrp-2-8-4-0/
Different Google search gave this. I can find nothing else on TWRP site or G+
Appears you can also use FlashFire.
Thanks for the help.
OP could flash one of the stock lite ROMs in the development forum and get the TWRP-flashable stock ROM he's looking for. Danvdh and tupac4u both offer one that is nothing more a debloated stock ROM.
TWRP is able to flash system images from 3.0.2 and on. Just unpack the archive and select install img. Remember to flash stock kernel and newest radio and bootloader too (bare in mind that flashable bootloader is harder to find. You might have to find older one and update the files inside on your own). Afterwards flash stock recovery and lock bootloader with a zip. Now you can just reboot it. It's not that hard.
Lawstorant said:
....bare in mind that flashable bootloader is harder to find....
Click to expand...
Click to collapse
For Nexus 6 https://forum.xda-developers.com/showthread.php?p=59728002/
Thank you.
I went ahead and simply flashed him 100% stock via flash and fastboot.
This is probably resolved now, just adding info though. I had flashed stock 7.1.1 zip downloaded from google via twrp 3.0.3.0. It removed twrp itself too and I was back on stock.
mrkhigh said:
I am surprised this doesn't exist. It does for every other device I've owned. It's honestly just a wiped clean, twrp backup of a stock device with TWRP installed.
I guess I'll round up a laptop. Thanks for the links and suggestions.
Click to expand...
Click to collapse
Try the app FlashFire.
I read here, somewhere, that you need stock recovery to do the update. Since I have flashed another recovery (and rooted and installed Xposed), I'm not sure if I can update to EMUI5.
Furthermore, I'm not even sure how to do the update. The update (b351) is available in FF and checks out as "compatible", but I don't know what the install procedure is. Especially without stock recovery.
Any help or info is much appreciated
yeah, you should flash stock recovery thru ADB and thn try updating...
Not adb but fastboot
thomaskmaagaard said:
I read here, somewhere, that you need stock recovery to do the update. Since I have flashed another recovery (and rooted and installed Xposed), I'm not sure if I can update to EMUI5.
Furthermore, I'm not even sure how to do the update. The update (b351) is available in FF and checks out as "compatible", but I don't know what the install procedure is. Especially without stock recovery.
Any help or info is much appreciated
Click to expand...
Click to collapse
You will also need to reflash the stock boot.img, since you're rooted.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
You will also need to reflash the stock boot.img, since you're rooted
Click to expand...
Click to collapse
Thanks a lot. Any help, perhaps, on where I get that. And the recovery mentioned above?
Oh, and why is it not possible to flash the ROM like if it was a custom one? Just wondering
thomaskmaagaard said:
Thanks a lot. Any help, perhaps, on where I get that. And the recovery mentioned above?
Oh, and why is it not possible to flash the ROM like if it was a custom one? Just wondering
Click to expand...
Click to collapse
That you may need to find your own. Well in custom ROMs, they are designed to work with custom recoveries like TWRP. While in stock, the whole system is inside update.app, which can't be read by a custom recovery.
adriansticoid said:
That you may need to find your own. Well in custom ROMs, they are designed to work with custom recoveries like TWRP. While in stock, the whole system is inside update.app, which can't be read by a custom recovery.
Click to expand...
Click to collapse
Okay, thanks anyways, again. I guess it's time to hunt down those images
thomaskmaagaard said:
Okay, thanks anyways, again. I guess it's time to hunt down those images
Click to expand...
Click to collapse
You can ask @DRUGER for that.
Any links to stock recovery and whatever else needed?
Jstyants said:
Any links to stock recovery and whatever else needed?
Click to expand...
Click to collapse
Check repository thread
Jstyants said:
Any links to stock recovery and whatever else needed?
Click to expand...
Click to collapse
You can also extract stock images from update.app