Okay it's been a few months since this has happened so I'll try to remember as best as I can; I had rooted my Nexus using WugFresh's kit, everything went fine. It was rooted for about 6 months and eventually got stuck in a boot loop (no clue how this happened, I hadn't installed any kernals, roms, even apps in months). I tried like 4 or 5 different methods to fix the issue; I finally was able to get the phone working again using ODIN mode, it completely restored it to stock (as far as I'm aware).
So I tried to re-root the phone; no luck, using ANY method I've been able to find. The main problem is I can't seem to get into TWRP, every time I try to it simply gives me the dead android with the red exclamation point. I'm not an advanced user by any means, but I'm not totally clueless and I can follow directions. If anyone has any advice for me on this I'd GREATLY appreciate it, I have an excellent 4G signal where I live and the only other internet option is AT&T basic DSL so I'd really like to be able to use my wifi hotspot again. Thanks in advance for your time, I appreciate anyone who takes the time to try to help.
1) android on its back is stock recovery.
2) follow this: http://forum.xda-developers.com/showthread.php?t=1529058
it works 100% of the time if you read and take your time.
it sounds like you have root but cant flash a recovery, let me know if im wrong but if this is the case I would just download goo manager from the market and go into settings and flash a custom recovery and that should fix your recovery problem but sometimes you have to download the recovery twice ive noticed that in the past, let me know if this works for you or you could go through the longer process above but your fix may be very simple
Thanks for the info, I will try this either tonight or tomorrow and get back to you; I certainly hope it works!
jaymazz13 said:
it sounds like you have root but cant flash a recovery, let me know if im wrong but if this is the case I would just download goo manager from the market and go into settings and flash a custom recovery and that should fix your recovery problem but sometimes you have to download the recovery twice ive noticed that in the past, let me know if this works for you or you could go through the longer process above but your fix may be very simple
Click to expand...
Click to collapse
I thought that too, but I tried installing super user and a couple of other root-only apps and it said that my device wasn't rooted. =P
Zepius said:
1) android on its back is stock recovery.
2) follow this: http://forum.xda-developers.com/showthread.php?t=1529058
it works 100% of the time if you read and take your time.
Click to expand...
Click to collapse
This is driving me insane. I'm trying this method; I followed the directions step by step, but my phone is showing that it is unlocked already (when I entered the fastboot oem unlock command in CP it returned FAILED: Invalid Command, but it is showing as unlocked in bootloader.
Now for the weird part; I rebooted to bootloader and tried fastboot flash recovery recovery-clockwork-6.0.2.3-toroplus.img and it returned immediately FAILED: Invalid Argument. I decided to start the process over, and now I can't reboot from CP, it's saying error: device not found.
I really want to just smash this f*%&ing thing into several hundred thousand pieces right about now, so I'm going to take a break for the moment. Are there different types of bootloaders, or is it possible the my bootloader is just corrupted or something?
There are different bootloaders, but the fastboot commands should work just the same. You're on Windows i'm assuming? You could also look at efrant's guide, http://forum.xda-developers.com/showthread.php?t=1626895, as well as his 101 in the general section stickies. It does not make sense that the device would become not found, and I would try reflashing the bootloader. Don't smash the phone!
Have you tried this method?
http://forum.xda-developers.com/showthread.php?t=1400871
lockehart12 said:
Now for the weird part; I rebooted to bootloader and tried fastboot flash recovery recovery-clockwork-6.0.2.3-toroplus.img and it returned immediately FAILED: Invalid Argument. I decided to start the process over, and now I can't reboot from CP, it's saying error: device not found.
Click to expand...
Click to collapse
your drivers are not installed correctly.
Related
While once again needlessly flashing stuff on my phone I lost SMS with the Cyanogen6 Snap kernel with Snap Turbo. From what I read I decided I had to reflash a stock rom to regain my ability to receive SMS. A flash of the update file has left me stuck in the bootloader. I had thought I good having used Unrevoked a few weeks ago. My Hboot was updated and is -S. When I turn the phone on it gets stuck on the white htc screen. Same when I try to boot into recovery. So I need to know how to reflash my phone with a stock rooted rom so I can start over. Shell commands work for fastboot but I am getting remote:not allowed responses when I try and flash recovery.
Please can you help me? I am going to sleep and letting the Evo get a full charge. Please do not delete this and link me to a solution.
Came here for the same, Did you fix this? my problem got worse, since adb doesn't seem to recognize the device, and none of Caulkin's methods here: seemed to work either. Somehow, along the way, Clockworkmod recovery got lost too, and I can't even flash a different rom.
shogun26 said:
Came here for the same, Did you fix this? my problem got worse, since adb doesn't seem to recognize the device, and none of Caulkin's methods here: seemed to work either. Somehow, along the way, Clockworkmod recovery got lost too, and I can't even flash a different rom.
Click to expand...
Click to collapse
I'd like to add a "me too" here.
I'm stuck with only fastboot available for getting the phone to work again.
I have a nandroid backup on my PC, that I could put on it. But I don't know the
fastboot command to use, or if there's even one available to use for a nandroid.
I also have a complete PC36IMG.zip. But again, I don't know the fastboot command
to use, or whether it's even possible.
Please help.
Thank you.
--Chris
I have the SAME PROBLEM! What's going on guys? Any fix?
So I was trying to put JB on my GN using this:
pcworld.idg.com.au/article/429778/how_update_your_galaxy_nexus_jelly_bean/[/url]
I reached to apoint where i had 4.04 yakju, but when I put the file to get JB, It said error and aborted, i went to wipe data and reboot, wipe data worked fine, reboot led me to the google home screen and is stuck there.
I can access fastboot. Recovery mode takes me to that android with the danger sign, doing another reset doesnt work, clicking reboot doesnt work.
I'm pretty nooby at this. I read a few other forums and they said something about flashing a new rom or something but I don't understand.
Please help! The phone isn't mine! Need help ASAP before owner finds out I messed up their phone, thanks!
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people shouldn't just one click everything they do. If you understood how fastboot worked you would be golden.
Reflash recovery. Then mount USB storage and then get a ROM on there and flash it.
Sent from my Galaxy Nexus using xda app-developers app
xjman said:
If you can access fastboot and your bootloader is unlocked just flash a stock system image.
These are the reasons people should just one click everything they do. If you understood how fastboot worked you would be golden.
Click to expand...
Click to collapse
The site I went to dumbed down everything, and all i had to do was input numbers into some program. I double checked what a fastboot was. I definitely don't know how to work that. I mixed up the fastboot with the bootloader...
how do i reflash recovery and get a rom on there? I know this is asking alot....sorry
My bootloader is unlocked but im not rooted. I will (figure out how to) root if needed.
Open up a terminal on your computer use fastboot to flash the recovery image.
Since you didn't take the time learn what you were doing to begin with, I would take the time now to go read. The answers are easily found with google, or searching this site.
Roughly, install adb and fastboot on your computer, load drivers for your phone, download the proper recovery and put it in the fastboot directory on your pc, plug in the phone boot to the bootloader
open term
./fastboot oem unlock
./fastboot flash recovery <nameofrecoveryimage>
I reached the fastboot part, but when i type in "fastboot flash recovery (file name) it says it cannot load file name...
What is the proper file that I should use? Running 4.04 YAKJU looking to just recover the phone back or switch to jelly bean, whichever is easier. (jelly bean if they are both the same)
okay okay okay, i think im almost there...got a rom and extraced it, i know how 4 files:
Boot 4,148KB
Recovery 4,478 KB
System 316,112 KB
Userdata 137,555 KB
Which one do I put for fastboot oem recovery (fileimagename)
Thanks
Stuck on Google screen
Background: GN is unclocked and rooted. I've had quite a few devices and have rooted them all and run custom ROMs. I am fairly familiar with all of the tools needed, but by no means an expert. I have the Android SDK with adb and fastboot installed on my Win 7 x64 machine as well as the samsung drivers. I loaded a Jelly Bean ROM the day after it was announced at Google I/O and ran it for awhile before I started having touchscreen issues. I removed the battery and restarted the phone and had no problems for about a week or so.
Problem: I started having touchscreen problems again, but figured it was perhaps due to the early version of JB that was ported over from the GSM version (I believe). I tried a few other versions that were released later and they would work for a few days and then the touchscreen issue would pop up again. At this point I started thinking it might be a hardware problem because if I twisted the phone (weird, but it worked) the touchscreen would respond. I flashed another version of the Jelly Belly ROM yesterday (//rootzwiki.com/topic/28677-rom-jelly-belly-v33-07122012-jellybean-411-pure-aosp-its-all-about-speed/") to see if it would work by chance. Unfortunately, I still encountered the touchscreen problem. After rebooting a few times my GN started bootlooping and would not load into Android.
Actions: At this point I tried to recover from a backup, but much to my dismay it failed (don't remember exact error). I tried a few other backups with no luck. I tried reflashing another ROM, no luck. Then I started seeing some errors when booting into recovery (E: can't mount cache/recovery/log. Around this time I also noticed I was getting errors with sdcard. I decided to take the phone back to stock using the verizon ICL53F factory image. I tried via numerous toolkits (Odin, Galaxy Nexus Toolkit and directly from fastboot) and have been unsuccessful. I've searched every forum and have literally tried everything I with no luck. I can flash new recoveries, but it doesn't solve my problem. Right now phone is back to stock with stock recovery and just bootloops at the Google screen.
I assume my phone is completely hosed, but am hoping someone might know something I don't and might be able to help me restore this phone.
Edit: I tried flashing an imm76k factory image via fastboot and was finally able to get in. I must have had a bad icl53f factory image...close call.
Hello, I've spent about the past 5 days trying to figure this out. So, how this started was, a while back when I first got the phone, I wanted 4.4, so I rooted my phone, and tried to flashify a recovery like CWM and TWRP. Both of these failed. I tried many times, and no matter what I tried, flashing always failed. But guess what, my stock recovery was erased in the process. I forgot about it until today, where I found the OTA update to 4.4 was released, and attempted to do it. To my dismay, I forgot I had no recovery mode, and instantly got the "boot certification verify" error screen. Now All I can access is download mode, to my knowledge. So I've been trying to fix this, either by installing stock recovery, or another way to install a custom. All to no avail. When I use the lg flash tool for the stock recovery, it fails at "BIN CRC Check". Every.... Single.... Time. Despite downloading multiple replacement files. I would be perfectly content with installing a customer recovery, but the ways I see require the phone to be on, and use the built in recovery mode. At this point, my phone is bricked, and I am looking for any and all ways to either A) boot back up normally without installing a recovery and fix it later, or B) install a recovery, even if it's the hard way.
Update:
I followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582142
It looked like it was going to work. I am using a Xubuntu virtual machine. I was copying the files over, and every time it finished copying a file, it unmounted and remounted my phone (I don't know if that was suppose to happen, just worth mentioning if it wasn't suppose to). I was super excited to do it. Hard rebooted my phone. And now it's just a blank screen. I have no logo, no error, and no download mode like I had before. Seriously need some help here.
Update#2:
I have the flash tool correctly working. Awesome! But..... I still have no download mode here.... So I can't use the tool....
Lastly, I am aware of the title.... i don't know how that happened. I intended to type "need", but somehow that happened. I do not know how to edit it.
Can you enter recovery?
Sent from my LG-LS980 using XDA Premium 4 mobile app
Ouch bud you are hard bricked pretty much. It sounds to me from what you explained all the partitions are wiped clean. I don't think there is any recovery from that unless you have a nand programmer
Sent from my LG-LS980 using xda app-developers app
brockzilla said:
Hello, I've spent about the past 5 days trying to figure this out. So, how this started was, a while back when I first got the phone, I wanted 4.4, so I rooted my phone, and tried to flashify a recovery like CWM and TWRP. Both of these failed. I tried many times, and no matter what I tried, flashing always failed. But guess what, my stock recovery was erased in the process. I forgot about it until today, where I found the OTA update to 4.4 was released, and attempted to do it. To my dismay, I forgot I had no recovery mode, and instantly got the "boot certification verify" error screen. Now All I can access is download mode, to my knowledge. So I've been trying to fix this, either by installing stock recovery, or another way to install a custom. All to no avail. When I use the lg flash tool for the stock recovery, it fails at "BIN CRC Check". Every.... Single.... Time. Despite downloading multiple replacement files. I would be perfectly content with installing a customer recovery, but the ways I see require the phone to be on, and use the built in recovery mode. At this point, my phone is bricked, and I am looking for any and all ways to either A) boot back up normally without installing a recovery and fix it later, or B) install a recovery, even if it's the hard way.
Update:
I followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582142
It looked like it was going to work. I am using a Xubuntu virtual machine. I was copying the files over, and every time it finished copying a file, it unmounted and remounted my phone (I don't know if that was suppose to happen, just worth mentioning if it wasn't suppose to). I was super excited to do it. Hard rebooted my phone. And now it's just a blank screen. I have no logo, no error, and no download mode like I had before. Seriously need some help here.
Update#2:
I have the flash tool correctly working. Awesome! But..... I still have no download mode here.... So I can't use the tool....
Lastly, I am aware of the title.... i don't know how that happened. I intended to type "need", but somehow that happened. I do not know how to edit it.
Click to expand...
Click to collapse
Im confused you said you had download mode then didnt? If it works try using the alternate G2 dll named 8974, because the second time I used Flashtool only the alternate dll worked which is weird because just hours earlier I had used the original, the original said wrong model/download failed the second time.
abhinav.tella said:
Im confused you said you had download mode then didnt? If it works try using the alternate G2 dll named 8974, because the second time I used Flashtool only the alternate dll worked which is weird because just hours earlier I had used the original, the original said wrong model/download failed the second time.
Click to expand...
Click to collapse
As I explained in my update, the method I used didn't work and had removed all modes I could boot into, including download mode.
brockzilla said:
As I explained in my update, the method I used didn't work and had removed all modes I could boot into, including download mode.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2477595
Then use LG Flash Tool, the Verizon guide works for LS980. Except use LS980 dll, and you must use Verizon USB drivers (Not T-Mobile, ATT etc), or Flash Tool wont work.
http://forum.xda-developers.com/showthread.php?t=2448960
I definitely hope you only semi bricked..... Tell me if that works.
brockzilla said:
As I explained in my update, the method I used didn't work and had removed all modes I could boot into, including download mode.
Click to expand...
Click to collapse
abhinav.tella said:
Try this
http://forum.xda-developers.com/showthread.php?t=2477595
Then use LG Flash Tool, the Verizon guide works for LS980. Except use LS980 dll, and you must use Verizon USB drivers (Not T-Mobile, ATT etc), or Flash Tool wont work.
http://forum.xda-developers.com/showthread.php?t=2448960
I definitely hope you only semi bricked..... Tell me if that works.
Click to expand...
Click to collapse
from what he said it sounds like a hard brick
Damn, not even fastboot? Feel sorry for you.
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
iSike said:
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
Click to expand...
Click to collapse
Open SuperSU->Settings->Unroot?
j to the 4n said:
Open SuperSU->Settings->Unroot?
Click to expand...
Click to collapse
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
iSike said:
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
Click to expand...
Click to collapse
When I unrooted using SuperSu it ruined my installation also. I was stuck in a bootloop until I installed TWRP and reinstalled SuperSu, terrible!!! It eventually unrooted and I relocked bootloader but nothing worked so I was forced to root and unlock bootloader again.
I am wondering though, how did you return to stock? I really want the latest AT&T stock but when I install that RUU .exe it gives me error 155 so I can't install it. I was using 1.32 stock AT&T and wanted to install 2.6 (I think that's what it is, it's Android 5.1).
I am S-On, and not S-off, could that be an issue? Bootloader is unlocked and I am rooted now.
You know how u r supposed to rename the ruu u want to flash (assuming you downloaded the stock ruu for your carrier and device). The problem for me was, I could never connect my device thought adb after I rooted it (fast boot worked when I put it in fastboot). Even when I could give a command , it could never load the ruu. So what I did, was right click the ruu and click run as admin. It should open up a page on the top saying something about a ruu/rom utility. Make sure you device is connected and had usb debugging( before you got stuck in the loop hopefully). Now click accept and all that good stuff on the utility, it should scan your phone and show u your current rom image, and then show you the latest rom image. Click update and it will boot your phone to boot loader and begin sending it to your phone. IMPORTANT: DO NOT TOUCH YOUR PHONE. Now here's the catch, if it said it failed or something about a USB error, close the program and start it up again. If your phone is stuck without the download bar moving(displayed on your phone), you are going to have to hard reset it. Google how to do it for your device (just a button holding combination). And start the program again. It will take a couple times for the program to work (mine took about 5-6 times). But it will work sooner or later. I am not home atm, but when I get home, I will find the link to the page where this info is displayed in a more orderly fashion and with pictures. It will be tonight, probably about 9 hours. Try this though, if it is too confusing, wait till I post the link. Good Luck!!
EDIT: Sorry just got back home from a long day haha, I'll be sure to look for the link tomorrow. But my directions above should be good, give it a try.
I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.
PasserbyPassingBy said:
I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.
Click to expand...
Click to collapse
I do the same! Now my phone stuck on boot screen.
Does anybody can help us?
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
mr_gourav2000 said:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.
PasserbyPassingBy said:
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.
Click to expand...
Click to collapse
All necessary to read.
Hope you fix the problem.
Fixed
I managed to fix my phone, but not with the method Mr Gourav so kindly posted. I chose not to use mr_gourav2000's IntelSoC fix because the guide was written in a way that made it very hard to follow, and I was unsure if MOOREFIELD was supposed to flash briefly or stay on the Device Manager. Regardless, I wasn't going to risk bricking my phone beyond help by pushing on without knowing what i was doing.
The key was bypassing Status 7 (or 1), which prevents you from downgrading firmware. If your phone says something like "Installation failed with Status 1" or "Status 7," or you get the "Can't install this package over newer build" error when you attempt to flash a previous firmware, this fix can help you. Funny enough, the fix was posted by the very same person earlier this year:
http://forum.xda-developers.com/showpost.php?p=65995574&postcount=116
First, download the latest full firmware from Asus' support site: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Then, open or extract the .zip file, and go to into UL-Z00A-WW-(Firmware.Version.Number)-user.zip\META-INF\com\google\android\ . Select updater-script (no file extension), and open it in a plain text editor like Notepad++.
Remove lines 1-6, beginning with "(!less_than_int" and ending with "getprop("ro.product.device") + "\".");". The result should look like this.
Then, insert the edited updater-script into the .zip file, overwriting the old updater-script. At this point, I should mention that one of the removed lines probably checked your phone's model number to see if it was compatible with the firmware. I sure hope you downloaded the right file for your phone. If not, brick city here you come.
Finally, put the edited .zip into a microSD card, and insert that into your phone. If you want to use the stock recovery to install the firmware, rename the .zip to MOFD-UPDATE.zip and put it in the root of the SD, then restart the phone and let it update. Presumably. I didn't use the stock recovery. I used the temporary ClockworkMod recovery to fix my phone, so I'm not sure if it's that simple. If you're using that temporary CWM, just go to the zip installation menu and apply the zip from external_sd.
If you were going through the same problems I was, your phone should boot into stock, unrooted firmware again. Pat yourself on the back and never do whatever dumb thing you did to get to this point in the first place (like absentmindedly apply an OTA update in the middle of a lecture)!
Once again, thanks to mr_gourav2000 for posting this fix earlier. I may not have understood the IntelSoC fix, but I did understand this one!
.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me
Redtexan said:
.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me
Click to expand...
Click to collapse
If it's the 1st boot it generally will as it is recreating cache, dalvik-cache or ART...
It seems to take forever to clear cache too when using recovery but about a heartbeat when using fastboot.... Just another quirk of the phone...
Thank you much
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.
mastet68 said:
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.
Click to expand...
Click to collapse
You need to flash boot, droidboot and recovery for the build you are using.
I use fastboot to do this but make sure developer settings are enabled and USB debugging is ticked before trying to flash.
To find the img files for the above mentioned, go to Shakalaka's pre-rooted rom thread in Android Developement, you don't need to download the rom if you don't want to but it sure makes rooting easy.
Find the version of Android you need and download boot,droidboot and recovery img files. Flash with fastboot using these commands -
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
***Make sure the right commands are used or it may result in a brick...***