Related
First off I would like to thank everyone on this amazing site for all the advice, guides and tutorials.
I unlocked my nexus bootloader and flashed a couple different roms. I really like the rom manager so I've used that to download roms and then flash them using that app.
When I downloaded the stock version of 91and flashed it, the phone no longer seemed to have root or clockwork recovery but my bootloader was still unlocked. When I downloaded rom manager, it could not get super user permissions, this being useless in flashing a backup or new rom. So I used universal one click root to gain root access and then rom manager was able to flash a backup.
I know this may be a dumb question but hope someone could explain to me why I needed to re-root and why I lost clockwork recovery...?
Thanks for the help in advance.
cwazynit said:
When I downloaded the stock version of 91and flashed it
Click to expand...
Click to collapse
Right theres your problem. stock roms dont have root built in you have to root them again. unless you download a prerooted stock rom. hope this helps.
cwazynit said:
I know this may be a dumb question but hope someone could explain to me why I needed to re-root and why I lost clockwork recovery...?
Click to expand...
Click to collapse
also it isnt a stupid question its that you didnt know and you wanted to know. when i started i didnt know either. lol.
krypticos said:
Right theres your problem. stock roms dont have root built in you have to root them again. unless you download a prerooted stock rom. hope this helps.
Click to expand...
Click to collapse
Yep this seems to be your problem. If you're wanting stock with the basic add-ons then the first link in this thread is your answer: Link.
Thanks very much. That does make sense. I thought unlocked bootloader meant I was rooted regardless of rom! I'm in way over my head lol. Looking forward to learning more...thanks for the new rom link as well
Sent from my Nexus One using XDA App
cwazynit said:
Thanks very much. That does make sense. I thought unlocked bootloader meant I was rooted regardless of rom! I'm in way over my head lol. Looking forward to learning more...thanks for the new rom link as well
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The advantage of unlocking your bootloader means you can flash a custom recovery from Fastboot mode, without having to "root" the ROM. Next time this happens you can just boot into fastboot and flash clockwork from there like this:
fastboot flash recovery PATHTO\RECOVERYFILENAME.img
so say you download clockwork and save it to c:\sdk\fastboot named recovery.img from a command prompt you enter the following
cd \sdk\fastboot
fastboot flash recovery recovery.img
once it is done flashing you can do this
fastboot reboot recovery
and that should take you into clockwork where you can flash your favorite ROM (or restore a backup).
Thanks for the help. I will be sure to try that method out next time. Very helpful.
I have a Moto X developer edition and I've been trying to OTA update to 139.15.1 but my phone fails with the error code 410. I found the Flashable zip and so I'm going to install it with that but for future installs how do I do it with the OTA. The phone failed both while rooted and while running a stock nandroid I made before rooting. With the stock nandroid the only thing modified was the unlocked bootloader. Yes I am using the stock recovery. Any help would be greatly appreciated.
Scoopta said:
I have a Moto X developer edition and I've been trying to OTA update to 139.15.1 but my phone fails with the error code 410. I found the Flashable zip and so I'm going to install it with that but for future installs how do I do it with the OTA. The phone failed both while rooted and while running a stock nandroid I made before rooting. With the stock nandroid the only thing modified was the unlocked bootloader. Yes I am using the stock recovery. Any help would be greatly appreciated.
Click to expand...
Click to collapse
there are threads out there already describing how to take the ota on a dev phone. But pure curiosity here, how in the hell are you making nandroid backups with stock recovery? I had noidea stock recovery allowed you to make those backups. I thought that was the point of other recoveries.
jayboyyyy said:
there are threads out there already describing how to take the ota on a dev phone. But pure curiosity here, how in the hell are you making nandroid backups with stock recovery? I had noidea stock recovery allowed you to make those backups. I thought that was the point of other recoveries.
Click to expand...
Click to collapse
It isn't possible to make a nandroid backup with a stock recovery. I meant I reflashed the stock recovery after making the backup. Anyway it is possible to make a backup that includes your stock recovery by using the fastboot boot command to boot to a recovery over usb rather than flashing it to your recovery partition.
Scoopta said:
It isn't possible to make a nandroid backup with a stock recovery. I meant I reflashed the stock recovery after making the backup. Anyway it is possible to make a backup that includes your stock recovery by using the fastboot boot command to boot to a recovery over usb rather than flashing it to your recovery partition.
Click to expand...
Click to collapse
interesting. Still wouldn't expect the OTA to work if you booted that way though. The OTA would be checking the files on the phone not the files from the usb that are running the phone. I wouldn't think. But I could be really confused on what you just said. Either way, there are several threads on the matter that should adequately answer all your needs.
jayboyyyy said:
interesting. Still wouldn't expect the OTA to work if you booted that way though. The OTA would be checking the files on the phone not the files from the usb that are running the phone. I wouldn't think. But I could be really confused on what you just said. Either way, there are several threads on the matter that should adequately answer all your needs.
Click to expand...
Click to collapse
Yes it would appear you are confused on what I just said. Anyway I guess I'll browse around to find instructions on how to take an OTA for the next time there's an OTA released.
Scoopta said:
Yes it would appear you are confused on what I just said. Anyway I guess I'll browse around to find instructions on how to take an OTA for the next time there's an OTA released.
Click to expand...
Click to collapse
i get what you were saying now. I thought you were saying that you were booting your phone from a usb drive that had the stock recovery on it so you could see if the OTA would take on your phone. Anyway, I dont' remember all of the steps that people were taking but it was pretty simplistic.
jayboyyyy said:
i get what you were saying now. I thought you were saying that you were booting your phone from a usb drive that had the stock recovery on it so you could see if the OTA would take on your phone. Anyway, I dont' remember all of the steps that people were taking but it was pretty simplistic.
Click to expand...
Click to collapse
ok...thanks for the info. I'll see if I can find a thread on it.
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.
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 went to codeworks page:
There are 4 files for the x522 in firmware and 4 in modems. I am assuming the "19s" firmware is for India so is the "20s" for the US?
But the 4 files in the modem section is confusing, which one/one's are for the US model x522? here is the link for the modems https://host.llamasweet.tech/codeworkx/lineage/s2/
Thanks
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
leo221 said:
S2_x522-na-op-ifxnaop5802102141s-5.8.021s
Click to expand...
Click to collapse
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
veda1 said:
Thanks but there is no file with that name listed in codeworks page is there? I have provided a link in the OP.
Click to expand...
Click to collapse
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
leo221 said:
find here
https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079
Click to expand...
Click to collapse
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
veda1 said:
Oh you mean flash that entire rom? And will that install the bootloader and modem? In any case, i tried flashing those files but they won't flash, any suggestions?
Since those roms won't flash i had to look for individual bootloader and modem and stumbled into those files by codeworks, and i am assuming you are saying that those aren't the correct files?
Click to expand...
Click to collapse
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now?
Click to expand...
Click to collapse
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
leo221 said:
I just flashed 21S today on my 522. what recovery do you have right now? that's pure stock. flashing will erase everything and restore factory rom. https://youtu.be/v_aohNnvT_Q
Click to expand...
Click to collapse
Yep its still happening. Tried to flash it right now and it says "can't read" error.
veda1 said:
twrp-3.2.1-0-s2, can't remember if i had the same one or one version older than the current one; when i tried it. Should i try it again? But the question is will it install the origibnal boot loader and modem? because i was playing with those in the past and flashed the wrong ones i think, and it will be great if i can go back to the original ones.
Click to expand...
Click to collapse
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
leo221 said:
it certainty restores boot. not sure about modem, I never touched it. you have nothing to loose flashing it. it supposed to be bone stock. just delete two lines in the script and re-save zip. you have to do wipe, wipe data, then mount, copy zip, flash, reboot. in that order, I wasted hours today finding out that order is required. otherwise, it won't load.
https://forum.xda-developers.com/le-2/help/help-restoring-s3-x522-to-stock-rom-t3809619
Click to expand...
Click to collapse
Updated script according to the video, still not flashing, says "cannot read error"
veda1 said:
Updated script according to the video, still not flashing, says "cannot read error"
Click to expand...
Click to collapse
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
leo221 said:
then you have a more complicated problem than mine. I had stock fastboot, and twrp.
Click to expand...
Click to collapse
Unbelievable! It actually worked after the 2nd attempt. Even got the 21s update. Thanks :good:
The original question is still unanswered about which one is the correct firmware for the US model amng the firmware provided by codeworks, hopefully someone knows that and will share in interest of others that might have the same problem.
Thanks again @leo221 for providing a clear and easy solution.