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
Related
EDIT: Ok, this isn't the I can't boot into WG-Slide thread =P
I want to make it more clear that there is absolutely no point in flashing the Engineering NBH
All it does is downgrade your radio, recovery, boot, and system images
The only image that mattered with the Engineering nbh doesn't get downgraded
I repeat something here... Using the Engineering nbh is NOT what gets you adb in recovery / clockwork / etc
Repeat again.. it is NOT what gets you that
Final Note: Keep in mind downgrading your radio isn't that safe... (anyone end up with one of those bricked G1's and had to get an exchange or even worse do a JTag?!) That could possibly happen if they changed the SPL version to a higher version than the radio compensates for - be careful!
Just wanted to let everyone know that flashing the ENG build is unnecessary and now found to be harmful...
Using the ENG build does NOT replace the SPL - which controls the ability to use fastboot or the ability to flash a recovery.img outside of an nbh file (thus we are unable to get ClockWork recovery to stick after reboot)
[This is the current theory, but using the ENG build then trying to flash any ROM that uses the majority of the /system like WG-Slide will not boot]
Using the ENG build does replace the recovery.img which is still stock recovery (unable to flash test signed update.zip files) but with an older kernel which is causing problems
Normal version of ClockWork recovery contain it's own kernel in the recovery.img - with our rooting situation...
When doing the root process to get into ClockWork recovery it maintains the kernel from the recovery.img already on the phone and just pushes is in the ClockWork binary, images, and scripts
It seems as if the older recovery.img has incorrect knowledge on the partition sizes with the SPL on the stock phones such that the /system partition is a smaller size than it really is
Which is why, you can flash Eugene's with no problem because he keeps the system partition size down in his builds and in the latest uses deodex'ed apps
In WG-Slide, after flashing there is only around ~7mb to spare (which is ok because you never write to the /system after flashing a ROM)
So for anyone wanting to try WG-Slide or ROMs coming out in the future that do use the full system partition size, you will have to revert to the original NBH at: http://bit.ly/wesaspin#280
You can do this:
Flash the production NBH from above
Redo the root process (only to the point where you get into ClockWork recovery (if using Eugene's)) and do a nandroid restore (this will only flash your boot.img, system.img, userdata.img (aka your data)
recovery.img will not be flashed via the nandroid process (because of the locks on the SPL)
wesgarner said:
...
Click to expand...
Click to collapse
Wes, awesome! Thank you for tracking down this issue. It is much appreciated.
After placing the downloaded ESPRIMG onto the root of your sdcard
1.Power Off the Phone either by Power Down / Battery Pull..
2.Hold Volume Down + Power Button..
3.Walk away, get a soda / Give the Better half a Kiss or two
4.Hit the Volume Up key to Confirm to Flash.
Once Done you will have a Stock Espresso Phone again..
OH, delete ESPRIMG after otherwise it will load each time you boot into bootloader....lol...just happen to me....
so those of us that are rooted should go and UN-root and then re-do everything this way?
tubaking182 said:
so those of us that are rooted should go and UN-root and then re-do everything this way?
Click to expand...
Click to collapse
Well, to flash any ROM you have to go through the process to get to a usable recovery...
so really you are just putting the nbh on there then going back through the recovery process (as you would if you wanted to flash a diff rom from where you are now), and flashing your current data and ROM back to the phone (using nandroid)
here.david said:
1.Power Off the Phone either by Power Down / Battery Pull..
2.Hold Volume Down + Power Button..
3.Walk away, get a soda / Give the Better half a Kiss or two
4.Hit the Volume Up key to Confirm to Flash.
Once Done you will have a Stock Espresso Phone again..
Click to expand...
Click to collapse
Oo yea I forgot those steps lol
plus... forgot to mention to put the nbh on your sdcard - but it's all good lol
Thanks for the more important details past the blah blah blah I posted lol
Just when I think I'm getting the hang of things... If anyone can help I would much appreciate.
These steps:
"1.Power Off the Phone either by Power Down / Battery Pull..
2.Hold Volume Down + Power Button..
3.Walk away, get a soda / Give the Better half a Kiss or two
4.Hit the Volume Up key to Confirm to Flash.
Once Done you will have a Stock Espresso Phone again.."
Are how to get back to stock Slide status correct? Does that mean it will be unrooted?
I never did the eng-release flash because I have yet to flash more than one ROM. Is there another method to flash the ClockWork recovery that ISN't using the loop exploit?
Thanks for the hassle
**** me. Wes, I re-flashed the Stock image and re-rooted my phone. I then flashed WesBlend 1.0.2 and my phone is stuck in an infinite bootloop that I cannot seem to escape! I can't get into flashboot or recovery. If I pull the battery, it immediately boots up as soon as I put the battery back in. No key commands are working...
This is very bad...
Anyone able to help?
You need time the battery placement with holding the volume down power button. Hold the buttons and then place the battery in while still holding the buttons. That should get you where you need to be.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Alright so if WE DID flash the Eng-Build before, we:
1. Flash production
2. Re-root
3. Flash new ROMs
HebrewToYou said:
**** me. Wes, I re-flashed the Stock image and re-rooted my phone. I then flashed WesBlend 1.0.2 and my phone is stuck in an infinite bootloop that I cannot seem to escape! I can't get into flashboot or recovery. If I pull the battery, it immediately boots up as soon as I put the battery back in. No key commands are working...
This is very bad...
Anyone able to help?
Click to expand...
Click to collapse
Have the lower volume button pressed already while putting the battery back in.
Oakley44 said:
Have the lower volume button pressed already while putting the battery back in.
Click to expand...
Click to collapse
Tried it. No luck.
EDIT: Left the battery out for a few minutes. Didn't auto-boot upon putting the battery back in. Was able to pop into fastboot and access recovery. Trying to sort out my giant error...
HebrewToYou said:
**** me. Wes, I re-flashed the Stock image and re-rooted my phone. I then flashed WesBlend 1.0.2 and my phone is stuck in an infinite bootloop that I cannot seem to escape! I can't get into flashboot or recovery. If I pull the battery, it immediately boots up as soon as I put the battery back in. No key commands are working...
This is very bad...
Anyone able to help?
Click to expand...
Click to collapse
Man... that sucks! Hmmm..... it looks like you bricked it. Remove the battery and unplug it from any usb or power cord and wait a while. Then put the battery back in....
Make sure your USB is unplugged! If you don't the phone will autoboot and get stuck in the loop.
sino8r said:
Man... that sucks! Hmmm..... it looks like you bricked it. Remove the battery and unplug it from any usb or power cord and wait a while. Then put the battery back in....
Click to expand...
Click to collapse
This worked, thankfully. Meh...
So, at some point I went from having to spoof the update.zip signature to not having to do that to get into clockwork.
What allowed that?
Will the update.zip sig have to be spoofed every time I want to get into Clockwork Recovery if I reverted?
Sent from my T-Mobile myTouch 3G Slide using XDA App
So the problem appears to be that after rooting and booting into ClockworkMod, I'm getting MD5 checksum errors when trying to nandroid restore. I try rebooting recovery and flashing update.zip and I get a signature verification failed error.
This never happened when I flashed the eng nbh after rooting. I can't get this **** to stick. Any thoughts on what I'm missing?
Jeebus, this is driving me nuts. Not only do I have to do the adb devices loop spam trick to get clockwork to boot up into the custom recovery now, I can't frickin get my Nandroid restore to pass MD5 checksum.
Any insight?
Until this issue is resolved I must firmly recommend that nobody else try this as it doesn't appear to work -- unless I'm missing something very important.
Without flashing the eng build you...
Can't boot into ClockworkMod from the stock recovery without repeating the root process
Can't restore your nandroid backup
Not only that, attempting to flash wesblend 1.0.2 after following these instructions caused the worst bootloop I have yet to experience.
HebrewToYou said:
Until this issue is resolved I must firmly recommend that nobody else try this as it doesn't appear to work -- unless I'm missing something very important.
Without flashing the eng build you...
Can't boot into ClockworkMod from the stock recovery without repeating the root process
Can't restore your nandroid backup
Not only that, attempting to flash wesblend 1.0.2 after following these instructions caused the worst bootloop I have yet to experience.
Click to expand...
Click to collapse
Yikes! Well, I think this throws Wes's theory out the window, lol! Back to the drawing board...
I've searched high and low for someone having a similar problem to no avail, so here it goes:
I previously rooted my phone using the one touch root method, and flashed kaosfroyo. I ran that ROM for a good while until I started having issues receiving text messages. I took my phone back to stock to see if that would fix the issue, which it did, but now I can't boot back into recovery to try to re-root. The issue I'm having is that when I try to boot into recovery using either the Vol up+end method or going through the hboot menu, it flashes the Androids on skateboards splash screen and the screen then goes black. I have to pull the battery and restart for the phone to do anything after that. Anyone have any ideas? Thanks in advance for the help!
*I do apologize if this has been covered before, but I've been looking for it for a few hours now and have not found it.*
Flashing back to stock unroots you which means you no longer have a custom recovery. Just download the 1 Click Root apk again, install, and run it. After it has worked it's magic and your phone has rebooted, you will have access to amon-ra recovery and can flash a new ROM.
MongooseHelix said:
Flashing back to stock unroots you which means you no longer have a custom recovery. Just download the 1 Click Root apk again, install, and run it. After it has worked it's magic and your phone has rebooted, you will have access to amon-ra recovery and can flash a new ROM.
Click to expand...
Click to collapse
I actually have tried that, and it doesn't work either. I forgot to mention that, sorry. I run the root, power down, but when I try to boot into recovery it does the same thing.
twiztedxtreme said:
I actually have tried that, and it doesn't work either. I forgot to mention that, sorry. I run the root, power down, but when I try to boot into recovery it does the same thing.
Click to expand...
Click to collapse
If you haven't already, maybe try the rooting method on the wiki:
How to Root Eris - XDA Wiki
Instead of the Recovery.img file they tell you to download, I'd suggest using the "1.7.1" recovery by scary alien which is a modified version of amon-ra. It allows the use of other physical buttons to navigate so if your trackball dies, you are still able to use recovery.
Amon_RA 1.6.2 Custom Recovery
If that doesn't work, I'd try following bftb0's instructions in this thread.
twiztedxtreme said:
I actually have tried that, and it doesn't work either. I forgot to mention that, sorry. I run the root, power down, but when I try to boot into recovery it does the same thing.
Click to expand...
Click to collapse
With 1-click root, you need to run the app, power down, power back up (like you wanted to make another phone call) - then power down and power up to recovery. From what you describe, you missed that intermediate power-up step.
doogald said:
With 1-click root, you need to run the app, power down, power back up (like you wanted to make another phone call) - then power down and power up to recovery. From what you describe, you missed that intermediate power-up step.
Click to expand...
Click to collapse
Yeah, that's what it sounds like to me too. The first few times I rooted my phone I missed that step too and thought I'd bricked the phone, only to realize I needed to boot back up fully and then go into the recovery.
Hello,
I too faced same problem in the initials of rooting. what i did is rooted again, but super one click doest work.
So i rooted with,
unrevoked.com/recovery/
It worked for me.
and for switching recovery, i think best way is via droid explorer. downlaod droid explorer and then download amon recovery, and flash it.
Dear all,
Here is the situation. I decided to root my evo 3d gsm (hboot 1.5++) today, and all went well until I flashed a rom (virtuous). Now whenever I boot on the phone, it shows me this "V" logo and loads for more than 10minutes or so. I can go into my bootloader, but when I attempt to do anything from my clockworkmod recovery, when I press the power button to select different options, I get blank menus and I can attempt nothing. I am an unexperienced user, and can anyone out there who is experience render some assistance? I am at my wits end...
Thanks
Well I'm not too familier with the gsm version... the "V", is that part of the boot animation? and does it just loop over and over? maybe try reflashing clockworkmod and re wipe and install?
netwokz said:
Well I'm not too familier with the gsm version... the "V", is that part of the boot animation? and does it just loop over and over? maybe try reflashing clockworkmod and re wipe and install?
Click to expand...
Click to collapse
The "V" is the part of the boot animation. And the "V" just glows again and again, yeah so i guess it loops. Why I am so worried is because I saw a window of my HTC sense booting to life earlier on, but I saw the words "Unfortunately... has... crashed..." but it was very brief, and after which the animation began again. Is it because I waited for too short a period of time? (around 15 minutes or so) or because it really boot looped? And how do I reflash clockwordmod when I can't access my phone and sd card? Will appreciate your kind help...
I've never had to wait more than 5 minutes for something too boot, and it should really never take longer than that. Can you tell me the steps you took to flash the rom(not to root it). and could you give some more info about your phone? are you s-on or s-off? And what do you mean by blank menus in clockwork mod? Do you know how to boot into your hboot menu? from there you can boot to fastboot and install the recovery from your pc. connect your phone to the pc while in fastboot mode and get your recovery.img file and type the following command from the command line:
Code:
fastboot flash recovery /path/to/<recovery>.img
netwokz said:
I've never had to wait more than 5 minutes for something too boot, and it should really never take longer than that. Can you tell me the steps you took to flash the rom(not to root it). and could you give some more info about your phone? are you s-on or s-off? And what do you mean by blank menus in clockwork mod? Do you know how to boot into your hboot menu? from there you can boot to fastboot and install the recovery from your pc. connect your phone to the pc while in fastboot mode and get your recovery.img file and type the following command from the command line:
Code:
fastboot flash recovery /path/to/<recovery>.img
Click to expand...
Click to collapse
Ok, here is the infomation. I live in Singapore, which is a part of Southeast Asia, my phone is the GSM version with HBoot 1.530007(i cant remember the decimal placing).
I firstly used HTCDEV to unlock my bootloader, which went well, then I went to evohacks to get the conventional rooting method, which went well too. And it all came when I was careless, and I accidentally forgot to wipe the data and cache of my evo before i flashed the rom. And now it gets stuck in the "V" logo loading phase. If the hboot menu is the menu where I have to press the powerbutton and the volume down button then yes. I can also get into my recovery, but the problem is that it shows a blank menu in (clockwordmod specifically), thus rendering whatever me helpless. i have downloaded the PG86IMG.zip and Im waiting for it to finish. So how do I go about solving this matter? This phone is my only asset and I really want to save it...
Blank menu as in for example when I click "Reboot", or "Factory Reset" or perhaps "Restore" in the CWD Recovery, it just shows me a blank menu with the CWD logo in the background, with no options or drop down words or whatsoever. And the sad thing is that I did not make any recoveries at all.... So I plucked my sd card out, and now im waiting to finish downloading the PG86IMG.zip to put on my sd and into my phone, and flash it to revert it back to stock and stuff..... I hope this works
Ok, well as long as you can get to either hboot or recovery you'll be ok. I would recommend flashing 4ext recovery, as it has never failed me and seems to help others. here is the link to it. Download that and pull the recovery.img out and flash that from your pc with the command I gave above. It sounds like you are either pushing the wrong button in the recovery or it might just be messing up for some reason. Is it the touchscreen version of clockworkmod?
netwokz said:
Ok, well as long as you can get to either hboot or recovery you'll be ok. I would recommend flashing 4ext recovery, as it has never failed me and seems to help others. here is the link to it. Download that and pull the recovery.img out and flash that from your pc with the command I gave above. It sounds like you are either pushing the wrong button in the recovery or it might just be messing up for some reason. Is it the touchscreen version of clockworkmod?
Click to expand...
Click to collapse
The recovery is the free version, so it shouldn't be the touch one. May I ask, what do you mean by recovery.img? I emptied my SD card so that I can put the PG86IMG.zip into it later. Any more specific steps you can give? Sorry but Im really a newb in the android world
mrkittyhawk said:
The recovery is the free version, so it shouldn't be the touch one. May I ask, what do you mean by recovery.img? I emptied my SD card so that I can put the PG86IMG.zip into it later. Any more specific steps you can give? Sorry but Im really a newb in the android world
Click to expand...
Click to collapse
The recovery.img is the image that the phone flashes to install the recovery. If you look in the zip I posted in the link you'll see that file in there. the one I posted is the 4ext touch recovery. you can manually flash that file to your phone in case you can't get it to boot(like your case). I would suggest trying the 4ext recovery I linked, or maybe try to boot to recovery again and see if its touch based. Were the menus working when you flashed the virtuous rom, and then it stopped working?
OH stupid me. Whoops. Actually I CAN navigate. Ive been pressing the wrong button all this while. I pressed the power instead of the camera, which is the select button. Whoops. seems like CMD was working after all. sorry...
ok but still, can I just attempt to install the RUU file I downloaded in the CWD menu? Will it work? Will my phone be reverted back to its original unrooted state? I saw someone say it could...
There is something bugging me though. My SD card is now completely empty. Will it have any negative effects on what i do?
I thought something like that was happening, glad you got it sorted. Try to wipe everything and reinstall your virtious rom again first. yes the PG86IMG.zip will return you back to complete stock, recovery and all. So if you do that you might have to re-root all over again.
mrkittyhawk said:
There is something bugging me though. My SD card is now completely empty. Will it have any negative effects on what i do?
Click to expand...
Click to collapse
no it won't.
thank you so much! So since now everything is clean, you recommend another shot at the virtous? I just drag it and put it in my sd card right? Neat! Will go try, if i encounter another problem will come back here. Thanks a lot! It really means a lot to me!
mrkittyhawk said:
thank you so much! So since now everything is clean, you recommend another shot at the virtous? I just drag it and put it in my sd card right? Neat! Will go try, if i encounter another problem will come back here. Thanks a lot! It really means a lot to me!
Click to expand...
Click to collapse
I would recommend trying it before you go back to stock just to re-do it all, but its up to you. yeah if you need more help just come here or pm me. glad you got it working again!
Thank You!
Oh ok! I thought by clearing the data using recovery on the phone and sd will render the root useless. Will try redoing it again. Will update you on the further details
Many thanks!
mrkittyhawk said:
Oh ok! I thought by clearing the data using recovery on the phone and sd will render the root useless. Will try redoing it again. Will update you on the further details
Many thanks!
Click to expand...
Click to collapse
If you only wipe /data/ you will still have root. sdcard doesn't matter.
mrkittyhawk said:
Oh ok! I thought by clearing the data using recovery on the phone and sd will render the root useless. Will try redoing it again. Will update you on the further details
Many thanks!
Click to expand...
Click to collapse
So theoretically flashing the ROM shouldn't take more than... around 15 minutes?
correct
Its now 10 minutes and so far my phone had made 2 major vibrations. So if this doesn't work, can i just wipe all the data again, put the PG86IMG.zip in my phone, go to recovery to install it, and then I just press reboot right?
mrkittyhawk said:
Its now 10 minutes and so far my phone had made 2 major vibrations. So if this doesn't work, can i just wipe all the data again, put the PG86IMG.zip in my phone, go to recovery to install it, and then I just press reboot right?
Click to expand...
Click to collapse
Sometimes sense roms can take a bit, but if its vibrating than it should be working. if not just put the PG86IMG.zip on the root of your sdcard and boot into hboot and let it do its thing. no need to wipe data for that.
Hey all used this guide to upgrade stock jellybean,
http://forum.xda-developers.com/showthread.php?t=1909819
Worked brilliantly and then got above my skill level when removing some bloatware, normally i copy the apks i remove however this time i pressed delete by mistake, now have huge issues with play store and other apps. I have deleted too many apks
Have tried installing google apks again but still no joy. Does any one know of a way i can install JB again to start afresh i did try downgrading as per the guide but that didnt actually remove the JB firmware. I feel although even with huge amounts of help from flumpster (many thanks) we arnt cracking it so a fresh install is prob best, i just hope someone knows how to.
Thanks in advance.
wesley.neary said:
Hey all used this guide to upgrade stock jellybean,
http://forum.xda-developers.com/showthread.php?t=1909819
Worked brilliantly and then got above my skill level when removing some bloatware, normally i copy the apks i remove however this time i pressed delete by mistake, now have huge issues with play store and other apps. I have deleted too many apks
Have tried installing google apks again but still no joy. Does any one know of a way i can install JB again to start afresh i did try downgrading as per the guide but that didnt actually remove the JB firmware. I feel although even with huge amounts of help from flumpster (many thanks) we arnt cracking it so a fresh install is prob best, i just hope someone knows how to.
Thanks in advance.
Click to expand...
Click to collapse
I would assume you can do a factory reset. With the until off, press and hold vol dwn, then press and hold the pwr button for a few seconds, release the pwr button but continue to hold vol dwn, then release when the bootloader is displayed, from there you should have an option to Wipe Data (Factory Reset).
imadork8317 said:
I would assume you can do a factory reset. With the until off, press and hold vol dwn, then press and hold the pwr button for a few seconds, release the pwr button but continue to hold vol dwn, then release when the bootloader is displayed, from there you should have an option to Wipe Data (Factory Reset).
Click to expand...
Click to collapse
I did try try that however it didnt replace the missing apps.
wesley.neary said:
I did try try that however it didnt replace the missing apps.
Click to expand...
Click to collapse
enter the bootloader, select Fastboot (USB icon)
Go to this forum and download the jb-twrp-recovery
http://forum.xda-developers.com/showthread.php?t=1911024
>> Download tf201-jb-twrp-recovery.blob and flash it via fastboot (fastboot -i 0x0b05 flash recovery tf201-jb-twrp-recovery.blob) and reboot.
Click to expand...
Click to collapse
Go back and follow the steps again
INSTRUCTIONS:
1. Download the ROM update zip (us-tf201-jro03c-10.4.2.15-stock-deodexed.zip)
2. Download the Superuser update zip (Superuser-3.2-arm-signed.zip)
3. Copy the files to your device and reboot into recovery
4. Wipe data/factory reset [VERY IMPORTANT STEP!! Just use the recovery wipe/factory reset, do not use any full wipe update zips or scripts]
5. Flash the ROM update zip and immediately after that, flash the Superuser update zip.
6. Reboot your device and wait for the new bootloader, kernel & recovery to flash (the blue progress bar) and then let the device boot up.
7. Enjoy JB on your device!!
Click to expand...
Click to collapse
imadork8317 said:
enter the bootloader, select Fastboot (USB icon)
Go to this forum and download the jb-twrp-recovery
http://forum.xda-developers.com/showthread.php?t=1911024
Go back and follow the steps again
Click to expand...
Click to collapse
The poster is not unlocked and cannot do this.
wesley, you know I told you to force close them apps and wipe data and cache for them, did you restart before trying play again?
flumpster said:
The poster is not unlocked and cannot do this.
wesley, you know I told you to force close them apps and wipe data and cache for them, did you restart before trying play again?
Click to expand...
Click to collapse
Yes force stopped wiped data and rebooted but still as soon as device reboots i get the error google play store has stopped.
Thanks for all your help guys it is appreciated, and is probably all that has stopped me throwing the thing at the wall.
wesley.neary said:
Yes force stopped wiped data and rebooted but still as soon as device reboots i get the error google play store has stopped.
Thanks for all your help guys it is appreciated, and is probably all that has stopped me throwing the thing at the wall.
Click to expand...
Click to collapse
because you are not unlocked we are purely guessing on fixes for this at the moment but I know you now have google services framework back. When you was asked above to do the volume down and power and then select wipe was this done after we got google services back or before?
flumpster said:
because you are not unlocked we are purely guessing on fixes for this at the moment but I know you now have google services framework back. When you was asked above to do the volume down and power and then select wipe was this done after we got google services back or before?
Click to expand...
Click to collapse
The plot thickens as now i tried the wipe as described and its force closing on the new setup wizard im guessing im running out of options as i now cant get past the setup wizard.
wesley.neary said:
The plot thickens as now i tried the wipe as described and its force closing on the new setup wizard im guessing im running out of options as i now cant get past the setup wizard.
Click to expand...
Click to collapse
Well there are still options. If you had USB debugging enabled in developer options you can still adb stuff to the device. If you don't as a last resort you could unlock the bootloader and install it as a custom rom. Also as you are not unlocked at all asus would probably accept it as an rma under warranty.
flumpster said:
Well there are still options. If you had USB debugging enabled in developer options you can still adb stuff to the device. If you don't as a last resort you could unlock the bootloader and install it as a custom rom. Also as you are not unlocked at all asus would probably accept it as an rma under warranty.
Click to expand...
Click to collapse
Ok how can i tell if i still have adb and if so whats the best file to try and push.
wesley.neary said:
Ok how can i tell if i still have adb and if so whats the best file to try and push.
Click to expand...
Click to collapse
You need to have the adb files on your computer. Open a command prompt where adb files are by holding down shift and right clicking on the folder adb is in and selecting open command prompt here. Then type adb devices into command window.
if you get waiting check in your device manager to see if you have any devices with explanation marks on it. If there are then install naked drivers from the top of developer section.
i need solution .. M8 Att stuck on logo after flash Custom Firmware . (ViperOneM8 4.6.0) I tried other firmware but condition same i need help how solve that problem
current condition .. Stuck On Htc Logo
S-On
TWRP Rec Installed
Thanks In Advance
Was the phone on Kitkat or Lollipop when you unlocked the bootloader?
What version TWRP?
Did you make a nandroid (TWRP backup) of your stock ROM before you flashed the custom ROM?
Don't use the word "firmware" when you mean ROM (that seems to be what you mean). On this device "firmware" is typically used to mean something completely different (firmware.zip that includes hboot, radio, etc., but not the OS/ROM).
redpoint73 said:
Was the phone on Kitkat or Lollipop when you unlocked the bootloader?
What version TWRP?
Did you make a nandroid (TWRP backup) of your stock ROM before you flashed the custom ROM?
Don't use the word "firmware" when you mean ROM (that seems to be what you mean). On this device "firmware" is typically used to mean something completely different (firmware.zip that includes hboot, radio, etc., but not the OS/ROM).
Click to expand...
Click to collapse
I have the same issue but mine is s-off. I put the LP firmware on first and now I am stuck.
suzyq42 said:
I have the same issue but mine is s-off. I put the LP firmware on first and now I am stuck.
Click to expand...
Click to collapse
Its not clear what you or the OP tried to flash, as you need to be specific (and provide links if possible).
Plus, I already asked you to provide getvar data (which should be mandatory for anyone asking for support here) in the thread you started, but you never did so.
redpoint73 said:
Its not clear what you or the OP tried to flash, as you need to be specific (and provide links if possible).
Plus, I already asked you to provide getvar data (which should be mandatory for anyone asking for support here) in the thread you started, but you never did so.
Click to expand...
Click to collapse
So, now, I updated my firmware to 4.16.401.1 and it took good. Went to TWRP and did a wipe of cache (both), system and data to prep the new ROM (Viper one M8 4.6.1). From my ext SD, loaded it and this is where we are at. This was 2.5 hrs ago.
suzyq42 said:
So, now, I updated my firmware to 4.16.401.1 and it took good. Went to TWRP and did a wipe of cache (both), system and data to prep the new ROM (Viper one M8 4.6.1). From my ext SD, loaded it and this is where we are at. This was 2.5 hrs ago.
Click to expand...
Click to collapse
What version TWRP?
Flash it again, or try a different ROM.
redpoint73 said:
What version TWRP?
Flash it again, or try a different ROM.
Click to expand...
Click to collapse
TWRP is 2.8.4.
Phone is locked up.
suzyq42 said:
TWRP is 2.8.4.
Phone is locked up.
Click to expand...
Click to collapse
Flash it again, or try a different ROM.
redpoint73 said:
Flash it again, or try a different ROM.
Click to expand...
Click to collapse
I can't! Will not let me get back to recovery. All it does is cycle power.
suzyq42 said:
I can't! Will not let me get back to recovery. All it does is cycle power.
Click to expand...
Click to collapse
Meaning what? You can get into bootloader, but when you try to select recovery, it reboots? Or you can't get into bootloader?
redpoint73 said:
Meaning what? You can get into bootloader, but when you try to select recovery, it reboots? Or you can't get into bootloader?
Click to expand...
Click to collapse
looks like it's bricked. All you can do is cycle the power. you can't get to anything.
suzyq42 said:
looks like it's bricked. All you can do is cycle the power. you can't get to anything.
Click to expand...
Click to collapse
If the screen comes on, its not bricked.
Hold the power button for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of the power button, and hold only the vol down button. Don't let go of vol down, until you see the hboot screen. Failure to access hboot is virtually always caused by not performing the button combo correctly, either not pressing vol down fast enough; or letting go too early.
From hboot, you should be able to boot into recovery, use fastboot, etc.