Hi guys here is the Lollipop 5.0 Nexus 10 Factory image from developers.google.com
Download link https://dl.google.com/dl/android/aosp/mantaray-lrx21p-factory-ad2499ea.tgz
Eagerly waiting for rooted stock
Guess the modified boot image work for this too. However not sure anything else has changed from compiled root friendly boot to the one in final factory image.
Skickat från min GT-I9505 via Tapatalk
Can you give us instructions how to pass to factory lollipop coming from root
How long does it take to boot. My nexus 10 is already showing the boot animation for 20 minutes (factory images)
I'm the same have reflashed to check, been waiting ages.
jahaangle said:
I'm the same have reflashed to check, been waiting ages.
Click to expand...
Click to collapse
I freaking hate staged rollouts, you might as well flash the image
Mike took long time. But not more than 5-10 minutes.
Trying Wug's toolkit this time, will see if I have any joy
And I managed to brick my nexus 10
scanno said:
And I managed to brick my nexus 10
Click to expand...
Click to collapse
No!! Man, we need you for lollipop homebrewed roms! Please tell us that's a joke
Sent from my Galaxy Nexus using Tapatalk 2
Injek said:
No!! Man, we need you for lollipop homebrewed roms! Please tell us that's a joke
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
All I can say is do not do a factory reset in TWRP after flashing the stock images.... [emoji35]
Tried Reflashing the stock images but that does not solve the non booting problems.
Cannot boot and cannot get into recovery.... Bootloader works.... Guess I need to format /data [emoji17]
Not having any luck either, has anyone been able to flash the factory image for the Nexus 10?
Yes. No problem here. Just trying out get root. Doesn't stick ?
Tried modified boot but doesn't work. Guests I'll try again.
I think that as long as you can boot to the BL everything is fine and dandy
Working this time, set the toolkit to force flash and changed usb ports to be on the safe side.
Fidelator said:
I think that as long as you can boot to the BL everything is fine and dandy
Click to expand...
Click to collapse
Well I can reflash the stock images, but still not booting. Guess the encrypted internal storage is the problem.
scanno said:
Well I can reflash the stock images, but still not booting. Guess the encrypted internal storage is the problem.
Click to expand...
Click to collapse
For those having issue booting after flashing follow these steps!!!
Make sure you flash the stock recovery (using twrp doesn't seem to work and can easily be flashed after the initial boot)
Wait for fastboot to finish the install, the device will restart when finished.
Stop the Device during the boot process then go back to the bootloader (pwr, vol +, vol -)
Select Recovery Mode
You will see an image that looks like a robot with its front cover over.
You can open the menu from here with Power + Volume Up.
Factory Wipe, then clear the cache.
Reboot
What's the easiest way to reinstall TWRP?
fillyo said:
What's the easiest way to reinstall TWRP?
Click to expand...
Click to collapse
flash one of these... preferably the latest update!
fastboot flash recovery openrecovery-twrp-2.8.1.0-manta.img
http://techerrata.com/browse/twrp2/manta
Related
Update:
New Test build to see if it is finally working. I no longer have V500 to test with so if anyone wants to test and give me feedback.
Well it does not work...file removed
This will flash the persist.img from V510 to V500 which might be the key to get wifi and other hardware working. If it does not work and you need to flash old one back let me know. Make sure you back everything and be prepared to do a restore to stock if all else fails. That is the worst that can happen. Easy thing if it does not work is you flash the old persist.img which I will make if needed. I am downloading the TOT file now for v500 if it is needed...
Web Presence:
Twitter
Google+
Thanks to @Demetris for latest tip..
Thanks to @thoughtlesskyle and @Mixinitup4Christ for the system dump and all of their help.
Download HERE - File name V500_to_V510.zip
Awesome,good work!
Sent from my Nexus 7 using Tapatalk
Apart from Wifi and Bluetooth, is it functioning 100% Can it play games, which CM11 can't?
I flashed this using TWRP (was previously on cm11) and the G pad doesnt boot up. I just stay at that beginning screen where there is an LG logo with the text on the top left corner (secure booting error!, Cause device unlock so boot success!). I've had this message since i flash cm11 though.
Any idea what to do, it doesnt look like i can start-up in TWRP.
Im assuming you did a factory reset first?
yes, i did
ekolb123 said:
I flashed this using TWRP (was previously on cm11) and the G pad doesnt boot up. I just stay at that beginning screen where there is an LG logo with the text on the top left corner (secure booting error!, Cause device unlock so boot success!). I've had this message since i flash cm11 though.
Any idea what to do, it doesnt look like i can start-up in TWRP.
Click to expand...
Click to collapse
It should have not touched your recovery. Did you use the right button combo to the get into the factory reset screen and then keep pressing power button to get into TWRP?
Enter recovery mode do full wipe and try again
To enter recovery follow my guide in general
Through some miracle of button combinations i was able to get back into twrp. Back on CM. Thanks guys!
ekolb123 said:
I flashed this using TWRP (was previously on cm11) and the G pad doesnt boot up. I just stay at that beginning screen where there is an LG logo with the text on the top left corner (secure booting error!, Cause device unlock so boot success!). I've had this message since i flash cm11 though.
Any idea what to do, it doesnt look like i can start-up in TWRP.
Click to expand...
Click to collapse
Happened to me too
Sent from my LG-G2 using Tapatalk
I have been trying to get wifi to work for the past few hours but no luck...
AndroidUser00110001 said:
I have been trying to get wifi to work for the past few hours but no luck...
Click to expand...
Click to collapse
Thank you for your awesome work!! I´m sure you´ll get it!:laugh:
somebody else having no sound from the speakers?
I mdofied patch and got 4.4.2 up and running but no wifi or bt yet
Yeah so after I got the basic patch to flash with no boot.img or aboot and other images, I decided to flash the imgs to see if I can covert tablet to GPE. Well folks...DO NOT TRY TO CONVERT!!! You may end up with a nice paper weight. Tablet will not even turn on now
AndroidUser00110001 said:
Yeah so after I got the basic patch to flash with no boot.img or aboot and other images, I decided to flash the imgs to see if I can covert tablet to GPE. Well folks...DO NOT TRY TO CONVERT!!! You may end up with a nice paper weight. Tablet will not even turn on now
Click to expand...
Click to collapse
not even download mode?
thoughtlesskyle said:
not even download mode?
Click to expand...
Click to collapse
Nope and it is showing as QHSUSB_DLOAD in my device manager on PC.
AndroidUser00110001 said:
Nope and it is showing as QHSUSB_DLOAD in my device manager on PC.
Click to expand...
Click to collapse
That's rough bro I'm sorry
Sent from my LG-G2 using Tapatalk
thoughtlesskyle said:
That's rough bro I'm sorry
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
**** happens when you do things you should not...lol. Maybe I can play dumb and return it
AndroidUser00110001 said:
**** happens when you do things you should not...lol. Maybe I can play dumb and return it
Click to expand...
Click to collapse
i've never done something like that.........
So today I was very foolish and formatted the System folder on an HTC Vivid that had cm-10-20131006-NIGHTLY-holiday installed. Needless to say, I no longer had an operating system . . .
I am still able to go into Recovery (TWRP), and I have successfully reflashed the build of Cyanogenmod. However, after booting, it is always stuck on the loading screen. I do not (and apparently cannot) have USB debugging enabled, so using fastboot or developer tools is out of the question.
What to do? Any suggestions would be appreciated.
Flash the old rom via recovery
Sent from my A11 using Tapatalk
arnabbiswasalsodeep said:
Flash the old rom via recovery
Sent from my A11 using Tapatalk
Click to expand...
Click to collapse
. . . the old ROM? Every time I flash a ROM the operating system becomes stuck on the "Cyanogenmod" loading screen.
Please help.
AntoineDC said:
. . . the old ROM? Every time I flash a ROM the operating system becomes stuck on the "Cyanogenmod" loading screen.
Please help.
Click to expand...
Click to collapse
Maybe your CM is stable insufficiently.
Try an more stable ROM.
I was used to use an HTC phone which had this problem.
Do full wipe.
Phone will boot
Enviado do meu GT-I9300 através de Tapatalk
+1 to above post
Do full wipe/format and make a clean install of a stable one.
Pete
AntoineDC said:
So today I was very foolish and formatted the System folder on an HTC Vivid that had cm-10-20131006-NIGHTLY-holiday installed. Needless to say, I no longer had an operating system . . .
I am still able to go into Recovery (TWRP), and I have successfully reflashed the build of Cyanogenmod. However, after booting, it is always stuck on the loading screen. I do not (and apparently cannot) have USB debugging enabled, so using fastboot or developer tools is out of the question.
What to do? Any suggestions would be appreciated.
Click to expand...
Click to collapse
I had a bricked HTC Velocity 4G and fortunately TWRP was still functioning from the Factory Reset Choice of my Boot List. So I tried many, one, the most sucessful, and gave me back full operation except WiFi, was: HOLICS_1.3_official_en_release.zip. it's link is available from this website if you read the forum on HTC Vivid/Raider/Velocity.
I am going to try and get my WiFi working with an Add-In before I completely forget that one? Good luck Amigo. Happy Flashing :laugh:
Hello,
I've looked around, but I haven't found anyone with this peculiar error message. So, I'm trying to flash the 5.0.2 OTA on my N9, but I get this message:
package expects build fingerprint of google/volantis/flounder:5.0.1/LRX22C/1602158:user/release-keys or google/volantis/flounder:5.0.2/LRX22L/1816899:user/release-keys; this device has google/omni_flounder/flounder:5.0.2/LRX22G/dees_troy03251233:eng/test-keys
I thought it was because I had a modifier my kernel boot.img (to unencrypt my N9), so I restored the stock IMG. It encrypted my tablet after a reboot. I came back in recovery, but I still get the message. I'm rooted/unlocked, stock Android and xposed is also installed. Before returning my N9 to it's stock state, I wanted to know if there was something I could try? What does the message means?
Thanks a lot!
I'm on the same boat,kinda...Stock ROM,only rooted...Is there an easy way to unroot without wiping the device?
It has already been reported that you can't simply install the OTA .zip as it comes, since Google is doing a checksum to the whole partitions (i guess boot and system) and as long as this isn't the original, it won't allow for the installation of the update.
I am not sure how can you override this check and make the .zip to install without reverting to a perfect stock (kernel+rom) system.
Flash the factory image (there is a line on the instal file that you need to edit so it doesn't wipe) or you can download the image , extract the zip inside and manually flash the system partition. Then try to run the update
Sent from my Nexus 9 using Tapatalk
Hello,
I've figured it out. I've used "WugFresh Nexus Rootkit 2.0.5" to flash LRX22C without Wiping the userdata and I was then able to apply the OTA 5.0.2.
Thanks for the help guys!
Majesty00 said:
Hello,
I've figured it out. I've used "WugFresh Nexus Rootkit 2.0.5" to flash LRX22C without Wiping the userdata and I was then able to apply the OTA 5.0.2.
Thanks for the help guys!
Click to expand...
Click to collapse
I must really be stupid not finding exactly what to choose,can you please tell me which option did you use on Wug's Toolkit?Thanks in advance!
tagari said:
I must really be stupid not finding exactly what to choose,can you please tell me which option did you use on Wug's Toolkit?Thanks in advance!
Click to expand...
Click to collapse
Sure, no problem. I did Option #1 from this FAQ:
http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Good luck!
Majesty00 said:
Sure, no problem. I did Option #1 from this FAQ:
http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Good luck!
Click to expand...
Click to collapse
Cheers mate!! I was looking in the advanced utilities!!THanks for your time !!
Hm... I tried the Wug method, and it was erroring out on the "flash LRX22C without Wiping the userdata" step, so it told me to check "Force Flash". I did, and it seemed to work, but I had to manually reboot (it didn't reboot for me at the end like it was supposed to). Now I'm stuck in an eternal bootloop. I can't get past the colored balls, and I can't turn the dang thing off; holding down the power button just performs endless force restarts.
Only thing I can think of is to run the battery down, plug it in, then go to the bootloader and do the Flash Stock + Unroot option again. Any other suggestions?
Thanks
generosity21 said:
Hm... I tried the Wug method, and it was erroring out on the "flash LRX22C without Wiping the userdata" step, so it told me to check "Force Flash". I did, and it seemed to work, but I had to manually reboot (it didn't reboot for me at the end like it was supposed to). Now I'm stuck in an eternal bootloop. I can't get past the colored balls, and I can't turn the dang thing off; holding down the power button just performs endless force restarts.
Only thing I can think of is to run the battery down, plug it in, then go to the bootloader and do the Flash Stock + Unroot option again. Any other suggestions?
Thanks
Click to expand...
Click to collapse
Did you try a factory reset in Hboot in the bootloader menu? Just hold the volume down button when it reboots, select Hboot, then Factory Reset. Or do the same to boot into the bootloader and try Wug's toolkit again with force flash AND the wipe settings I think it is. I checked, it's with the 'No Wipe Mode' unchecked.
KedarWolf said:
Did you try a factory reset in Hboot in the bootloader menu? Just hold the volume down button when it reboots, select Hboot, then Factory Reset.
Click to expand...
Click to collapse
You're a genius. I keep reading that I need to hold power+vol down+vol up. Holding power+vol down got my right out of the boot loop, and so I'm back in Bootloader and can hopefully get it figured out from there. Thanks!
generosity21 said:
so I'm back in Bootloader and can hopefully get it figured out from there. Thanks!
Click to expand...
Click to collapse
You can't flash the OTA if you are rooted. If you want to go the OTA route you will need to flash the stock 5.0.1 system.img, boot.img(if you have a modified kernel) and vendor.img first.
F.Y.I.
even if you mount vendor and or system
as rw and still change nothing
that will not let the ota flash
hi,
i wanted to flash stock android (used an rom before) so i erase recovery system etc.. and when i want to flash the system img it says "
(bootloader) Device State : Locked
FAILED (remote: Can not flash any images while device state is locked!)
-.- what can i do ?
any solutions ?
thanks
Not much. Only thing you can do with a locked boot loader is flash OTA updates, and they don't have an OTA that will flash the full system. OTAs only update an existing system. You shouldn't have erased your system.
You need to return your N9 to HTC for a replacement.
Sent from my Nexus 9
enriquejones666 said:
Not much. Only thing you can do with a locked boot loader is flash OTA updates, and they don't have an OTA that will flash the full system. OTAs only update an existing system. You shouldn't have erased your system.
You need to return your N9 to HTC for a replacement.
Sent from my Nexus 9
Click to expand...
Click to collapse
hmm okey, so send it back to HTC (or amazon cause i buyed it there)
but it should be no problem cause its locked and therse no sign that it was/is rooted, right?
also i have buyed an insurance for 2 years so i think it should be okey... i hope so
So I'm in a similar pickle, with one huge difference: my bootloader is unlocked, and reflects such in the fastboot menu.
Long story short, I have no image of any kind on it at this point. All attempts with any interface to flash either 5.1.1 or 6 fail. When attempting to flash the system.img, I get the "too many links" error. I've not found a solution that works.
At this point, I have no recovery and no image. I can't successfully flash one either. Not sure what to do from here...
Sent from my LG-H810
disturbd1 said:
So I'm in a similar pickle, with one huge difference: my bootloader is unlocked, and reflects such in the fastboot menu.
Long story short, I have no image of any kind on it at this point. All attempts with any interface to flash either 5.1.1 or 6 fail. When attempting to flash the system.img, I get the "too many links" error. I've not found a solution that works.
At this point, I have no recovery and no image. I can't successfully flash one either. Not sure what to do from here...
Sent from my LG-H810
Click to expand...
Click to collapse
are you using the right fastboot commands? Eg. not something dumb like fastboot flash boot system.img. Also are you flashing your stuff in the correct order? Make sure to grab a good copy of whatever version of android you're trying to flash from here
tdct12 said:
are you using the right fastboot commands? Eg. not something dumb like fastboot flash boot system.img. Also are you flashing your stuff in the correct order? Make sure to grab a good copy of whatever version of android you're trying to flash from here
Click to expand...
Click to collapse
Thanks, I ended up getting it in a workable state last night. Ran a temporary recovery via Wug's toolkit, got TWRP installed, and went from there. I now have Marshmallow on it via AOSP, but I think the bootloader might still need updating.
Sent from my LG-H810
disturbd1 said:
Thanks, I ended up getting it in a workable state last night. Ran a temporary recovery via Wug's toolkit, got TWRP installed, and went from there. I now have Marshmallow on it via AOSP, but I think the bootloader might still need updating.
Sent from my LG-H810
Click to expand...
Click to collapse
Just download the newest build and fastboot flash bootloader bootloader.img :good:
oediv said:
hmm okey, so send it back to HTC (or amazon cause i buyed it there)
but it should be no problem cause its locked and therse no sign that it was/is rooted, right?
also i have buyed an insurance for 2 years so i think it should be okey... i hope so
Click to expand...
Click to collapse
Definitely send it back to Amazon. They are very good about taking returns. You can just say you tried to update the OS, and now the device doesn't boot (i.e. product is defective).
Sent from my Nexus 9
enriquejones666 said:
Definitely send it back to Amazon. They are very good about taking returns. You can just say you tried to update the OS, and now the device doesn't boot (i.e. product is defective).
Sent from my Nexus 9
Click to expand...
Click to collapse
2 people 1 idea
It's on the way, I said " want to update the OS and Made a factory reset before"
Have you tried flashing the factory images with fastboot? Pretty straight forward...
For future reference, how did you erase things with the bootloader locked?
https://developers.google.com/android/nexus/images?hl=en
Wow nice !!!
Let's Rock!
Can't wait for pure nexus to update to N
Sent from my Nexus 6P using Tapatalk
YES!
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
I only flash via fastboot and when going between versions I'd personally want to do a fully clean flash. Mind you I reverted to MM after trying N for a couple days, but again, I'd never flash a full factory image via Flashfire.
Vegeta700 said:
Is it possible to flash the factory image using flashfire?
Im currently using this ROM (Stock+Nougat-NRD90M Debloated-Prerooted-Odex-Busybox-Fast & Stable).
Click to expand...
Click to collapse
Unless a lot of users have certified that flashing via dlash fire works, I would recommend a clean flash via fastboot. This way you are flashing the images the most direct way possible. Doing this will also reduce possible entry points for issues.
First person to find an .mbn file in the boot.img or bootloader.img gets SO much cred.
Oh my .. Time to flashing silently
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
kaslopis said:
Is there a list of apps that currently don't work (or do work) with 7.0? I'm trying to switch over but there's a couple core apps that I need to know will work fine.
Click to expand...
Click to collapse
There's a thread called "Android N: What doesnt work" here in general
david279 said:
There's a thread called "Android N: What doesnt work" here in general
Click to expand...
Click to collapse
Most of the apps on that list that I use did not have the stated issues... None of them did.. I'm not sure if that list is up to date.
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
E30Nova said:
You're welcome.
I just finished flashing back to 6.0.1 and getting everything set up.
Of course now it gets released...
Click to expand...
Click to collapse
You aren't alone. Went back a day ago myself.
Sent from my Nexus 6P using Tapatalk
From what I've seen, this version isn't all that superb. Being on 6 isn't so bad
I've honestly had zero issues with the factory image for N. I wiped everything and clean flashed the image flat. Once I restored all my apps (around 80), so far it seems very smooth. No issues with lag in either the system or the fingerprint scanner.
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Soured Lie said:
I keep getting an error about not being able to find systsem.img in its package.. In thought they fixed this in the flash all script in 5.0 for factory images?
Click to expand...
Click to collapse
Flash-all is still broken afaik, better flash the individual img`s in fastboot.
Hey y'all,
Sorry to bother here. I looked around but couldn't find anything. I'm running NRD90M on my phone. I install TWRP and I rooted my 6P + unlocked bootloader. However I just downloaded the full image on google NRD90U. I'd like to put back my phone to stock with this new image and be able to just keep it stock and receive OTA. Can someone help me out or giving me a link where there's a tutorial. I already downloaded Fastboot/ADB and installed my drivers.
PS: It's find if it wipes everything. I just want it clean.
Thanks!
StangATX