After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
avelinosilva said:
After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
Click to expand...
Click to collapse
Maybe this can help you:
** For those of you who are interested in the solutions i arrived at (with the help of some good friends) please read my final post @:
https://www.reddit.com/r/hwatch/comm...e_android_man/
avelinosilva said:
After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
Click to expand...
Click to collapse
You are not bricked.
In order to update to the new OTA you need to go back to fully stock LCB43B image. That means flashing stock boot, recovery and system. BUT unfortunately there's a problem when trying to flash the stock system.img in bootloader. So you have to boot into TWRP, use adb push to get the system.img file onto your internal memory and then flash it using adb shell commands. Use this thread: http://forum.xda-developers.com/showthread.php?p=63173308
Then reboot to bootloader and flash the stock recovery and boot files.
Next, download the OTA and reboot into stock recovery (not TWRP) in order to update using adb sideboard. Use the guide here: http://forum.xda-developers.com/showthread.php?p=65607393
Hit thanks if this has helped.
bigdave79 said:
BUT unfortunately there's a problem when trying to flash the stock system.img in bootloader. So you have to boot into TWRP, use adb push to get the system.img file onto your internal memory and then flash it using adb shell commands. Use this thread: http://forum.xda-developers.com/showthread.php?p=63173308
Click to expand...
Click to collapse
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
I had instaled Androi Studio and Sdk is any problema to use W10 64 bits.
Please can you help me with the commands to use?
is this one:
adb devices
In Twrp advance select adb sideload
fastboot flash recovery recovery.img
I´m doing something wrong??
If i will send the Wacth to Huawei assistance they can fix it?
Best regards and thank you all for your help.
avelinosilva said:
I had instaled Androi Studio and Sdk is any problema to use W10 64 bits.
Please can you help me with the commands to use?
is this one:
adb devices
In Twrp advance select adb sideload
fastboot flash recovery recovery.img
I´m doing something wrong??
If i will send the Wacth to Huawei assistance they can fix it?
Best regards and thank you all for your help.
Click to expand...
Click to collapse
No.
Boot to bootloader and type "fastboot flash system system.img"
You should not be in recovery trying to fastboot flash. It will not work.
Latest SDK is fine on Windows 10. Make sure you use the fastboot and ADB from the latest SDK.
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
/-\
|
|
This
Scott said:
/-\
|
|
This
Click to expand...
Click to collapse
Scott you are my hero.....i got my watch alive......:laugh:
Tank you veryyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyymutchhhhhhhhhhhhhhhhhhhhhhhhhhh mate.:good:
avelinosilva said:
Scott you are my hero.....i got my watch alive......:laugh:
Tank you veryyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyymutchhhhhhhhhhhhhhhhhhhhhhhhhhh mate.:good:
Click to expand...
Click to collapse
Good to hear!
Scott said:
/-\
|
|
This
Click to expand...
Click to collapse
I was stuck for last 12 hours and watch was in bootloop. i tried flashin again and agin . Scott i love you :laugh:
i think it was that i was using old adb and fastboot. the latest ones helped. Also there is no need to flash twrp. Even if you get file sparce issue.
Salute to You :good::good::good:
Now i am back to LCB43B will try to update to 1.4 via stock recovery now
Yeah, the ADB / Fastboot changed with Lolipop. Anything pre-lolipop will give issues.
I've never flashed anything onto my watch, but yesterday after recharging the battery after it going dead, I get stuck at the 4 dots boot animation. I'm able to reboot the watch, and even get into the normal fastboot menu, but clearing cache, data, and resetting to default doesn't help. I'm really hoping what you guys are doing will fix the trick for me. I simply want to return the watch to stock, but I'm seeing conflicting reports on how to proceed with this.
I've downloaded the Android SDK, but have never used it before. I keep hearing things about adb, and flashing system.img using the latest fastboot - I don't know where to find either of these or how to use them. Would you awesome people mind doing a little hand holding with me and give me a bit of detail on how to proceed with the solution from C3C076?
EDIT: So I think I figured it out myself, albiet with the wisdom gained from you awesome folk. I used fastboot to push the 6.0.1 boot and system images from this thread, and things seem back to normal. I haven't rebooted the watch yet, since I didn't load the 6.0.1 recovery image (the only part of the watch that had worked since the problem started), and I'm not sure if I'm going to have the problem reoccur once it does reboot. If anyone has insight on how to best proceed given the steps I've taken so far, it'd be greatly appreciated.
kurosen said:
I've never flashed anything onto my watch, but yesterday after recharging the battery after it going dead, I get stuck at the 4 dots boot animation. I'm able to reboot the watch, and even get into the normal fastboot menu, but clearing cache, data, and resetting to default doesn't help. I'm really hoping what you guys are doing will fix the trick for me. I simply want to return the watch to stock, but I'm seeing conflicting reports on how to proceed with this.
I've downloaded the Android SDK, but have never used it before. I keep hearing things about adb, and flashing system.img using the latest fastboot - I don't know where to find either of these or how to use them. Would you awesome people mind doing a little hand holding with me and give me a bit of detail on how to proceed with the solution from C3C076?
EDIT: So I think I figured it out myself, albiet with the wisdom gained from you awesome folk. I used fastboot to push the 6.0.1 boot and system images from this thread, and things seem back to normal. I haven't rebooted the watch yet, since I didn't load the 6.0.1 recovery image (the only part of the watch that had worked since the problem started), and I'm not sure if I'm going to have the problem reoccur once it does reboot. If anyone has insight on how to best proceed given the steps I've taken so far, it'd be greatly appreciated.
Click to expand...
Click to collapse
If fastboot flashing boot and system images went well, you can safely reboot your watch. First boot might take a while but it should boot OK.
@ausi
ausi said:
Maybe this can help you:
** For those of you who are interested in the solutions i arrived at (with the help of some good friends) please read my final post @:
https://www.reddit.com/r/hwatch/comm...e_android_man/
Click to expand...
Click to collapse
@ausi, can you please post again the solution, the link doesn't work anymore!!!
I really need it!!!
Please help!!!
I am in the same ****!!!
My watch doesn't work anymore!!!
Thank's for anyone help!!!
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
This DUDE RIGHT HERE. Did it. This was the missing piece. My fastboot files simply weren't good enough. x!!
Android SDK Platform Tools did the trick for me.
Related
I'm new to the forums and I've been searching and reading all over for help. This was my first time rooting. I was trying to flash a rom in TWRP and somehow erased everything, no OS or anything. Now when I boot up it only says google. It won't load past that. I can get into the fastboot screen but the adb options don't work. And now since trying two different tool kits to flash to stock image, I can't get on TWRP anymore. Any help would be great thanks. I'm not even sure what I did but I can try to add more information. Thanks
You can boot in fastboot and flash it back to stock.
I see Google hasn't posted the factory images out there yet, your tablet is fixable, but you need the image. Maybe someone else can chime in with a image I haven't found yet. BTW, you can fastboot flash the recovery if its a .IMG file to get that back.
Note: you'll need the android SDK because you'll need the fastboot drivers and the fastboot.exe program to flash back.
Sent from my Nexus 7 FHD using Tapatalk 2
trssho91 said:
Can you boot into fastboot mode by holding all three buttons for 5 seconds with the device off? It doesn't need a os or recovery just as long as you didn't kill the bootloader. Once in fastboot just flash it back to stock.
Download your image here: https://developers.google.com/android/nexus/images
Don't freak out yet, its hard to brick a nexus device
Edit, I just saw you said you can get fastboot. Use the link I posted to download your image, if you need the android SDK because you'll need the fastboot drivers and the fastboot.exe program to flash back.
Sent from my Nexus 7 FHD using Tapatalk 2
Click to expand...
Click to collapse
Obviously ADB would not work in fastboot. Erasing your ROM and recovery is no where near being bricked. You get into bootloader by holding Power + Volume down. Google has not released the official image package yet so flash the stock images from these -
http://forum.xda-developers.com/showthread.php?t=2381438
http://forum.xda-developers.com/showthread.php?t=2381582
I'll try this all out in the morning. It's getting late here. Thank you and I'll be back to give you all an update!
You could even skip flashing the stock recovery and reflash TWRP. Rename it "recovery.img" put it in platform-tools... Then:
fastboot flash recovery recovery.img
TWRP should be flashed. Install a stock deodex or odex ROM and wipe data before install. Should be good.
But, everyone else's solutions will also work too (ie you are NOT bricked )
Sent from my Nexus 4 using Tapatalk 4 Beta
I need help also im trying to restore with the images but its hanging when i get to the flash system part it just sits there and i dont have a system to bootup to if i wanted to what can i do ??
Okay i guess i just had to wait a lil bit longer its finally flashing the system
Sent from my Nexus 4 using Tapatalk 4 Beta
I think I'm having some problems trying to download things in the correct folders, seeing as I don't understand most of the lingo. I used a all in one tool to unlock the bootloader and root but when I tried putting things in the folder it wouldn't load properly. I deleted everything off of my pc and I'm going to redownload everything and try again.
Tried http://forum.xda-developers.com/showthread.php?t=2381582 early this morning and it wouldn't load properly. I ran it and it said ?????? fastboot and then said some files were missing. Let me get back at it though.
You're just gonna have to own up and install the SDK. It only takes a few commands once it's downloaded.
http://developer.android.com/sdk/index.html
Sent from my Nexus 4 using Tapatalk 4 Beta
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Geodude074 said:
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Click to expand...
Click to collapse
Yea thats correct zedomax made a zip on here that only has the files u need
Sent from my Nexus 7 using Tapatalk 4 Beta
Geodude074 said:
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Click to expand...
Click to collapse
+1 I didn't know somebody compiled that for the new N7. I was mostly trying to get this fellow to shy away from the toolkits - not that they're bad... But when they mess up, it's a headache to recover.
Sent from my Nexus 4 using Tapatalk 4 Beta
When I post on here I think its better to assume I'm posting to a noob rather assuming they know something they don't and making their situation more stressful. The SDK is a blanket install and you know everything is there. For someone inexperienced its better than: get this driver, and this one, and these files...move them here..you get the idea.
Sent from my SAMSUNG SGH-I747 running CyanogenMod.
Anisak said:
Tried http://forum.xda-developers.com/showthread.php?t=2381582 early this morning and it wouldn't load properly. I ran it and it said ?????? fastboot and then said some files were missing. Let me get back at it though.
Click to expand...
Click to collapse
The guide on that thread should work really well, but I will just point out that for me, ADB wasn't working (yet) while I was still trying to flash TWRP on it, so the 'ADB reboot bootloader' line in the "Recovery_Nexus7.bat" was pointless. In my case, I go to the bootloader/fastboot mode by holding the power button + volume down.
Once in fastboot/bootloader mode, ensure that fastboot can see your N7 2013 by typing 'fastboot devices'. If you see your device there, you are good to proceed with flashing all the files that are in that zip file. It even roots your device. Good luck and let me know if you need any further help.
zeppelin101 said:
The guide on that thread should work really well, but I will just point out that for me, ADB wasn't working (yet) while I was still trying to flash TWRP on it, so the 'ADB reboot bootloader' line in the "Recovery_Nexus7.bat" was pointless. In my case, I go to the bootloader/fastboot mode by holding the power button + volume down.
Once in fastboot/bootloader mode, ensure that fastboot can see your N7 2013 by typing 'fastboot devices'. If you see your device there, you are good to proceed with flashing all the files that are in that zip file. It even roots your device. Good luck and let me know if you need any further help.
Click to expand...
Click to collapse
Oh disregard my last comment. I got it to work! Thank you everyone for the help!
Anisak said:
When I type fastboot devices nothing comes up. And I can't seem to unlock or lock it now. (Was testing that command)
Click to expand...
Click to collapse
Are you logging in from your administrator account and is it windows 8 by any chance ?
Well, Rule is log into from your administrator account and windows 8 will need manual drivers installation for your Nexus 7 (2013). Try downloading USB drivers from SDK.
I am also attaching fastboot drivers which I hope will work
Good luck
Hnk1 said:
Are you logging in from your administrator account and is it windows 8 by any chance ?
Well, Rule is log into from your administrator account and windows 8 will need manual drivers installation for your Nexus 7 (2013). Try downloading USB drivers from SDK.
Good luck
Click to expand...
Click to collapse
I'm on windows 7 but I did read about something about being on admin and that did the trick. Before it wasn't letting me run anything and not warning me to do so either. But I got it! Thanks to everyone for the help and advice. :victory:
Hi.
As the title says, I have bricked my GPad and am stuck in Fastboot mode. I am able to pull up a command line on my computer and reboot the device from there, but that's about all I've tried. I have read online that there are commands for flashing a boot.img file, but I can't find one and I don't know how to do it. Do I wipe the device from my computer first, or just flash the .img file? Any help would be greatly appreciated.
God Bless, Mark
dadof10 said:
Hi.
As the title says, I have bricked my GPad and am stuck in Fastboot mode. I am able to pull up a command line on my computer and reboot the device from there, but that's about all I've tried. I have read online that there are commands for flashing a boot.img file, but I can't find one and I don't know how to do it. Do I wipe the device from my computer first, or just flash the .img file? Any help would be greatly appreciated.
God Bless, Mark
Click to expand...
Click to collapse
Don't wipe the device! At least I wouldn't. Might not be able to get back in!
Flash recovery and then a ROM.
sleekmason said:
Don't wipe the device! At least I wouldn't. Might not be able to get back in!
Flash recovery and then a ROM.
Click to expand...
Click to collapse
Thanks for the help, Sleek. Which recovery image should I flash and where can I get it?
Sent from my SM-G900V using XDA Free mobile app
dadof10 said:
Thanks for the help, Sleek. Which recovery image should I flash and where can I get it?
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
double check and make sure it is for your device. Link to Recovery
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
sleekmason said:
double check and make sure it is for your device. Link to Recovery
Click to expand...
Click to collapse
looks like you need loki also. There may be others that would be better suited to answer this question, as I have the Google Play edition. but at least this will point you in the right direction!
sleekmason said:
double check and make sure it is for your device. Link to Recovery
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
looks like you need loki also. There may be others that would be better suited to answer this question, as I have the Google Play edition. but at least this will point you in the right direction!
Click to expand...
Click to collapse
Ok. Thanks, I really appreciate it, take care.
Sent from my SM-G900V using XDA Free mobile app
dadof10 said:
Ok. Thanks, I really appreciate it, take care.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I love it when I see new members breaking theyre devices....lol....because I've been there....lol.....and xda is your friend, we are here to help....anyway....I agree with the previous advice, dont wipe device, how did you get in the situation your in?....flash recovery, and try and find a rom, make sure its for the VK810, other roms (v500 or V510) will only make things worse.... last I checked there are not many VK810 roms out there, let me know how you make out....
mcerk02 said:
I love it when I see new members breaking theyre devices....lol....because I've been there....lol.....and xda is your friend, we are here to help....anyway....I agree with the previous advice, dont wipe device, how did you get in the situation your in?....flash recovery, and try and find a rom, make sure its for the VK810, other roms (v500 or V510) will only make things worse.... last I checked there are not many VK810 roms out there, let me know how you make out....
Click to expand...
Click to collapse
I was rooted, running 4.4.2. I tried to flash 4.2.2 aboot.img with Flashfy, so I could flash TWRP recovery. Didn't work out.
Flashing a recovery is what I don't know how to do in fastboot mode. Can you walk me through it? Also, I don't know which recovery to flash.
Sent from my SM-G900V using XDA Free mobile app
dadof10 said:
I was rooted, running 4.4.2. I tried to flash 4.2.2 aboot.img with Flashfy, so I could flash TWRP recovery. Didn't work out.
Flashing a recovery is what I don't know how to do in fastboot mode. Can you walk me through it? Also, I don't know which recovery to flash.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img
sleekmason said:
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img
Click to expand...
Click to collapse
Ok, I got it. Duhhh...I re-read it and it makes sense now. Somehow I had it in my mind that I had to open terminal emulator on my GPad, which I can't do. I'll try it tonight when I get home from work and let you know how it goes. Thanks again.
Sent from my SM-G900V using XDA Free mobile app
sleekmason said:
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img
Click to expand...
Click to collapse
OK, Sleekmason, I put everything where it should be, but when I use the "adb" commands (adb push loki_flash...) I get "device not found" in terminal. As I said, I can reboot the GPad using "fastboot reboot" command, so it sees it in fastboot mode, but not in adb mode. I loaded the drivers during the adb install, so I'm pretty sure all of them are there. Is there something I'm missing? Is there a way to push the files to the GPad with fastboot?
dadof10 said:
OK, Sleekmason, I put everything where it should be, but when I use the "adb" commands (adb push loki_flash...) I get "device not found" in terminal. As I said, I can reboot the GPad using "fastboot reboot" command, so it sees it in fastboot mode, but not in adb mode. I loaded the drivers during the adb install, so I'm pretty sure all of them are there. Is there something I'm missing? Is there a way to push the files to the GPad with fastboot?
Click to expand...
Click to collapse
There is an lg recovery tool that is talked about here... But we are now out of my territory lol. maybe somebody else can chime in?
sleekmason said:
There is an lg recovery tool that is talked about here... But we are now out of my territory lol. maybe somebody else can chime in?
Click to expand...
Click to collapse
That's the first thing I tried and it wouldn't recognize the GPad either. I loaded all the drivers, but no luck. Thanks for trying, dude.
dadof10 said:
That's the first thing I tried and it wouldn't recognize the GPad either. I loaded all the drivers, but no luck. Thanks for trying, dude.
Click to expand...
Click to collapse
not saying you should, but you could always try to flash the recovery just to see if it would work.
same problem, but how I fixed it
How I got bootloop'd - I was on a trip and tried to root/flash twrp from a chromebook and as you can tell the process did not work. I ended up trying to flashfly a 4.2.2 boot.img over a 4.4.2 setup. Not the best idea. Once I returned to my windows machine, I was able to flash via adb/fastboot tools. So I found this thread and wanted to help anyone else if they arrived here and read thru the posts.
I was stuck at the fastboot text base screen on my Gpad (VK810). I dl'd the LG tools, the LG driver & tried a KDZ recover, but I was unsuccessful. Fastboot would control my device, reboots worked, but when I run fastboot devices, I only saw a single ? where the device serial number is. After a few attempts at various methods, I ended up guessing which file I had to flash.
After dl'ding a few roms from here and extracting them, it took the boot.emmc.win and flash my boot.img with that. worked with the following code and now I'm up and running.
Code:
fastboot flash boot boot.emmc.win
followed by
Code:
fastboot reboot
this worked for me and could work for you, but I can only say that it worked when I was able to access my tablet via fastboot commands.
Downgrade aboot
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
exit
exit[/HTML]
I am not able to do the above after installing Lollipop because can't get root, specifically can't update binaries in supersu and no su. Also Adbd Insecure not working. Now I am able to get into fastboot, strangely thru factory reset. Can I use 'fastboot flash aboot aboot.img' instead. Many thanks.
pakron said:
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
exit
exit[/HTML]
I am not able to do the above after installing Lollipop because can't get root, specifically can't update binaries in supersu and no su. Also Adbd Insecure not working. Now I am able to get into fastboot, strangely thru factory reset. Can I use 'fastboot flash aboot aboot.img' instead. Many thanks.
Click to expand...
Click to collapse
Sir or m'am, in the future, you shouldn't post the same thing in two different threads.
FynxSyndct said:
How I got bootloop'd - I was on a trip and tried to root/flash twrp from a chromebook and as you can tell the process did not work. I ended up trying to flashfly a 4.2.2 boot.img over a 4.4.2 setup. Not the best idea. Once I returned to my windows machine, I was able to flash via adb/fastboot tools. So I found this thread and wanted to help anyone else if they arrived here and read thru the posts.
I was stuck at the fastboot text base screen on my Gpad (VK810). I dl'd the LG tools, the LG driver & tried a KDZ recover, but I was unsuccessful. Fastboot would control my device, reboots worked, but when I run fastboot devices, I only saw a single ? where the device serial number is. After a few attempts at various methods, I ended up guessing which file I had to flash.
After dl'ding a few roms from here and extracting them, it took the boot.emmc.win and flash my boot.img with that. worked with the following code and now I'm up and running.
Code:
fastboot flash boot boot.emmc.win
followed by
Code:
fastboot reboot
this worked for me and could work for you, but I can only say that it worked when I was able to access my tablet via fastboot commands.
Click to expand...
Click to collapse
i was having the same issue, get the boot.img file and typed "fastboot flash boot boot.img" after moving the boot.img file into the same folder as adb/fastboot and it worked, thanks bro!
Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code
z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.
z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112
Sorry for another nubby question but how do I get flash_all.bat?
z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?
_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah
z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.
Hi all,
I hope someone can help as I am at my wits and sanity's end.
I am trying to install twrp into my phone to make a factory backup before rooting. I have unlocked the boot loader via htcdev all OK, I have followed the guide online to install twrp but it just will not work, I have tried various methods and every one of them failed. ADB and fastboot are installed OK, when I type "fastboot devices" it shows the phone and serial number, HTC sync is installed and updated, SDK is installed, everything the guide said to do I have done but it just won't flash. Error when I try to flash twrp every time. It is the latest version etc (I think) the twrp image is in the adb/fastboot folder and the cmd was opened from the folder.
I really don't know what I am doing wrong, can anyone please advise?
Thanks in advance
Gary Nixon
Belaris said:
Hi all,
I hope someone can help as I am at my wits and sanity's end.
I am trying to install twrp into my phone to make a factory backup before rooting. I have unlocked the boot loader via htcdev all OK, I have followed the guide online to install twrp but it just will not work, I have tried various methods and every one of them failed. ADB and fastboot are installed OK, when I type "fastboot devices" it shows the phone and serial number, HTC sync is installed and updated, SDK is installed, everything the guide said to do I have done but it just won't flash. Error when I try to flash twrp every time. It is the latest version etc (I think) the twrp image is in the adb/fastboot folder and the cmd was opened from the folder.
I really don't know what I am doing wrong, can anyone please advise?
Thanks in advance
Gary Nixon
Click to expand...
Click to collapse
are you in bootloader or download mode, you have to be in download mode, what command are you typing to flash recovery.
fastboot flash recovery (name of recovery).img
Yep download mode black screen and that command
i have installed java SE development kit 7 and java 8 update 66 as per the guide
Do i need an SD card in the phone for this as i just saw this mentioned but it wasnt on the guide i was using?
Belaris said:
i have installed java SE development kit 7 and java 8 update 66 as per the guide
Do i need an SD card in the phone for this as i just saw this mentioned but it wasnt on the guide i was using?
Click to expand...
Click to collapse
hmmm, not sure on that one, put one in and see
I think i may know the problem - S-ON - would this prevent anything being flashed?
Have you tried re-downloading TWRP to make sure it isn't a corrupted download?
Belaris said:
I think i may know the problem - S-ON - would this prevent anything being flashed?
Click to expand...
Click to collapse
no, if your bootloader is unlocked you don't need to be s-off to flash recovery. Are you flashing the correct twrp for your phone
2.8.7.1_CPTB-B1-hima.img
its cool i got it to work, next question how do i get the custom rom zip file into the phone
Belaris said:
its cool i got it to work, next question how do i get the custom rom zip file into the phone
Click to expand...
Click to collapse
download it, connect tehphone to pc, move the rom zip to either extsd or internal sd, boot to recovery select the zip and flash.don't forget to make a backup, and to wipe dalvik cache, cache, system,and data,under advanced wipe. nothing else then install the rom
what was causing the problem before, that you couldn't get recovery to flash, just curious
tbh i actually used the m9 toolkit by Squabbi - did it in 5 minutes
donation on the way
Belaris said:
tbh i actually used the m9 toolkit by Squabbi - did it in 5 minutes
donation on the way
Click to expand...
Click to collapse
ok cool, glad you got it going.
My ZE551ML is unlocked/rooted running the stock MM from asus, everything worked fine for a long time now.
This morning my phone booted in TWRP, and whatever I try, it always boot in TWRP. The only thing I know has changed is that yesterday Magisk installed an update.
How can I recover my phone? adb is working, I can go in TWRP, but what else?!?
Try wiping your misc partition:
Code:
adb shell dd if=/dev/zero of=/dev/block/by-name/misc
Problem was Magisk v11.5 that updated itself, it is not signed. I restored a previous boot backup and back in business.
So people, do not update Magisk using their builtin updater!
Hi, I have same problem. Can anyone please post an step by step to do that adb thing?? I mean, my ZF is stucked in recovery (via fastboot I installed TWRP) but I don't know how to execute that line posted before. I can only get my device as adb sideload so that line posted returns an error... please help or tell me how to find that info.
Thank you in advance!
michi6278 said:
Hi, I have same problem. Can anyone please post an step by step to do that adb thing?? I mean, my ZF is stucked in recovery (via fastboot I installed TWRP) but I don't know how to execute that line posted before. I can only get my device as adb sideload so that line posted returns an error... please help or tell me how to find that info.
Thank you in advance!
Click to expand...
Click to collapse
hello, same problem here. i update the magisk and all go wrong.
i fixed the problem only flashing the magisk again, in the TWRP.
and boot works fine
https://forum.xda-developers.com/an...igning-boot-images-android-verified-t3600606/
Flash this and your problem will be solved
itizar1 said:
https://forum.xda-developers.com/an...igning-boot-images-android-verified-t3600606/
Flash this and your problem will be solved
Click to expand...
Click to collapse
Hey, my phone randomly stopped booting, and I can't seem to get it to work. It boots to TWRP and I have full root access, with an unlocked bootloader. Do you have any idea how to fix this? I don't know what to do with this.
ZE552KL
Kaisogen said:
Hey, my phone randomly stopped booting, and I can't seem to get it to work. It boots to TWRP and I have full root access, with an unlocked bootloader. Do you have any idea how to fix this? I don't know what to do with this.
ZE552KL
Click to expand...
Click to collapse
You dirty flashed your rom then. Everytime you update, first wipe your system (not data!), then flash everything you need (not sure about gapps and stuff, just flash them to make sure)