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:
Related
The problem I encountered must be the worst problem ever! For some reason my nexus reboot randomly and its not just a regular reboot but it reboot as a DEEP FREEZE. So basically once it rebooted, it goes back to a same specific point of time. I can't even delete stuff from the phone, for example if I deleted 1GB of music off my phone, after few second the phone will reboot automatically OR if i reboot the phone myself the 1GB of music would be back in my phone. Like WTH? I am completely lost. I have no idea how it happened, but I know it happened after I installed Paranoid Android AOSP 2.99 beta5. I was fine when flashing Paranoid Android 1,3,4. ALSO I cannot do a factory reset or install a factory rom. It just go back to 4.2.1 AOSP 2.99 beta5...
please guys, if anyone can help me that would be great. If you guys need more explaining please email or PM me. I will be glad to write a whole essay on what you guys need to know to help me out. Thank you
Go back to stock and start fresh.
Sent from my i9250
bk201doesntexist said:
Go back to stock and start fresh.
Sent from my i9250
Click to expand...
Click to collapse
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..
Yellowfriedrice said:
Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here
ahmadallica said:
Which "ROM" is not there? Do you have any flashable zip of any ROM on your internal sdcard to flash?
I think you should go ahead and post a video so it will be much easier to understand what is going on exactly then hopefully we can help you here
Click to expand...
Click to collapse
You cant brick a nexus! Try making a jig with this link http://www.youtube.com/watch?v=jKRrTZayRxU Then get download odin and an img file of whatever rom you want and flash it through odin. Problem should be solved.
Yellowfriedrice said:
That didn't work either. I tried going back to stock but it didn't do anything, I keep booting into 2.99 beta5. I was able to get into recovery mode but I think that when it load the "Google" boot up screen, that's when it start the deep freeze process. Do you get what I mean though? I can post a video to show you guys what I mean. So like if I wanted to flash another ROM I have to go into recovery, but before getting to recovery, you have to go through the "Google" loading screen correct? Then when I get into recovery to flash, the ROM is not there..
Click to expand...
Click to collapse
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out
khuzema9 said:
man what i think is you should download nexus toolkit , i think its latest edition is 10. something and try to reflash your stock image and recovery . just try that.
---------- Post added at 08:48 PM ---------- Previous post was at 08:27 PM ----------
did something work out
Click to expand...
Click to collapse
Based on the language used in the OP I think he used a toolkit to root/unlock his Nexus and that's why he knows nothing about his device and how to fix it.
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again
altimax98 said:
OP- look up fastboot images nexus and follow what you read. Basicly you should download the fastboot images and flash them all in fastboot. Then start from scratch again
Click to expand...
Click to collapse
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck
still didn't work
ahmadallica said:
That's right and probably the cleanest way of going out of this mess. Here is a thread that can help you accomplish that:
http://forum.xda-developers.com/showthread.php?t=1626895
Read the instructions carefully because this will delete all your data including the internal (and only) sdcard of your GNex, so consider the backup part of that thread very well.
Good Luck
Click to expand...
Click to collapse
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you
Yellowfriedrice said:
I couldn't use the driver from the thread you sent, it says "access denied" and I tried to disable windows signature verification but that didn't work either. So I thought maybe I'll use the driver from Nexus toolkit. I manage to complete all the steps from the instruction to the core except for the driver but it still didn't work. It would not erase the 2.99 beta5 and so I cannot go back to stock. Perhaps I should try to use the driver from the thread but I just don't know how to get pass the signature verification when installing the driver. Assist me if you can please. Thank you
Click to expand...
Click to collapse
I really have not done anything to my GNex via Windows becuse I am using Ubuntu Linux so I have not experienced installing these drivers on Windows. I also have neither returned my phone to stock before nor used the Nexus toolkit. I am doing everything manually.
I think you are referring to the drivers in this page. If you are using Windows 8 then there are some steps mentioned on how to get pass the driver signature enforcement.
If you are on Windows 7, then look here.
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?
ahmadallica said:
Just to confirm something else because I did not read that you have done it, did you try wiping system, factory reset, cache and dalvik cache from the recovery then install any other flashable zip of a ROM on your sdcard (if you have) and still nothing is erased and you are stuck on the same ROM?
Click to expand...
Click to collapse
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol
Yellowfriedrice said:
Yes, I have but that didn't seem to work either. I put a flashable ROM into the internal memory when it was rebooted, when I tried to go into recovery the file is not there anymore. Its because the phone erases everything that was placed into the internal during the Google reboot process. I even tried using the nexus toolkit to flash a stock ROM, the procedure went through successfully but it still loads 2.99 beta5.
I will try to post a video as soon as I buy a webcam.. But a webcam is cheaper than a nexus phone right now so I don't mind. lol
Click to expand...
Click to collapse
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!
ahmadallica said:
You may try to boot into recovery then use "adb push" to send the file to your sdcard from your computer. If the file is sent successfully, then you can find it in the recovery and install it thus escape the reboot problem.
Hope this works!
Click to expand...
Click to collapse
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.
Yellowfriedrice said:
still no good.. used the recovery sideload to push but it still didn't work.
tried odin but that didn't work either.
Click to expand...
Click to collapse
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
ahmadallica said:
Was there any progress of pushing the file then it did not appear in your recovery or it did not show any progress at all of being pushed?
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.
ahmadallica said:
I have experienced this and used to push the file two times (one after another while still in recovery mode) in order to successfully find the file in recovery. Give it a try and good luck
Click to expand...
Click to collapse
Thank Goodness im not the only one who has this issue... Bugs the crap outta me lol..
To the OP:
Try this, 1: make sure your an admin on your PC. From the sounds of it you may not be if it said 'access denied'. 2: Plug your nexus in while in the 'device manager' section of windows. 3: Find the new device and delete it. Delete anything that says Android ADB or Android anything or galaxy Nexus or Galaxy phone. Just delete them. Windows will warn you but do it anyways... 4: reboot the pc. 5: Plug your nexus back in, it should either install the device or fail. At that point find and download the newest samsung naked drivers and use the option on windows to install driver from disk and navigate to your unzipped folder.
That is the sure fire way to get it working again. Sorry to say if you still have driver issues then your doing something wrong. Do alot of reading and the answer will show itself.
1. Can you boot your phone into fastboot mode?
2. If so, once in fastboot mode, what happens when you connect the phone to the computer?
It is very very difficult to brick a nexus, so don't worry... .
Yellowfriedrice said:
I pushed it before and while it was in recovery mode. Tried both ways but I didnt see any file in there.
I also just noticed that all the files within the folders are missing. The folders are there but when I go into any folders, it said no files found within the folders.
Click to expand...
Click to collapse
Sorry for not being able to help you better. I'm sure that others who are familiar with Windows can help you overcome your earlier issues with drivers and so on thus be able to return to stock and start fresh
Good Luck
It is very very difficult to brick a nexus said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse
OKAY i tried everything.. nothing seem to work.. selling my nexus!
Yellowfriedrice said:
challenge accepted!!
But yes I can get it into fastboot mode. Nothing special happen? What are you trying to look for to happen? It look like it functioning normally in fastboot mode.
Click to expand...
Click to collapse
Hi, I just got a Sprint Galaxy Nexus off ebay. It came rooted with team win recovery and a custom rom based on jelly bean 4.1.1. It worked fine. It had goo manager, so I downloaded two different roms to flash before I activated the phone. I wiped the system, factory reset, casce and Dalvik Cache, then flashed the rom. It failed. I hit wipe cache/dalvik, it said successful. Like a dumbass, I rebooted even though it said there was no os installed. Now, neither rom will flash, it will only boot into win recovery and it won't mount to my pc. Is there anyway I can fix this?
Nadreo said:
Hi, I just got a Sprint Galaxy Nexus off ebay. It came rooted with team win recovery and a custom rom based on jelly bean 4.1.1. It worked fine. It had goo manager, so I downloaded two different roms to flash before I activated the phone. I wiped the system, factory reset, casce and Dalvik Cache, then flashed the rom. It failed. I hit wipe cache/dalvik, it said successful. Like a dumbass, I rebooted even though it said there was no os installed. Now, neither rom will flash, it will only boot into win recovery and it won't mount to my pc. Is there anyway I can fix this?
Click to expand...
Click to collapse
Did you do a backup before you flashed? If so, have you tried using the backup? If you did not, maybe the person before you who rooted the phone did a backup.
[email protected] said:
Did you do a backup before you flashed? If so, have you tried using the backup? If you did not, maybe the person before you who rooted the phone did a backup.
Click to expand...
Click to collapse
no, I did not make a backup. I unwisely assumed the person before me did. they did not.
I'm not sure where the guide is but you should search on how to push files to the phone via ADB, once you have the file on your phone I think you should be able to flash a new rom and be back to normal.
Since you now own a nexus, you should learn how to use fastboot and adb. I'd restore every thing to stock by flashing the factory images for your phone. See my post below:
http://forum.xda-developers.com/showthread.php?p=35247414
Sent from my Galaxy Nexus using xda premium
mwalt2 said:
Since you more own a nexus, you should learn how to use fastboot and adb. I'd restore every thing to stock by flashing the factory images for your phone. See my post below:
http://forum.xda-developers.com/showthread.php?p=35247414
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I almost wish the toolkit didn't exist so everyone would do this and never need help ever again. Teach a man to fish...
mwalt2 said:
Since you now own a nexus, you should learn how to use fastboot and adb. I'd restore every thing to stock by flashing the factory images for your phone. See my post below:
http://forum.xda-developers.com/showthread.php?p=35247414
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I downloaded the factory image, unzipped in the same directory as fastboot and adb, restarted phone into bootloader, ran the commands, got <waiting for device> like the other guy in that post, already had the drivers but reinstalled anyway, updated driver in device manager--it sees it as Android 1, but has the correct driver and says is working properly--tried several different ways to flash the system.img, still get the <waiting for device> any suggestions?
thanks for your help by the way, really appreciate it.
Nadreo said:
I downloaded the factory image, unzipped in the same directory as fastboot and adb, restarted phone into bootloader, ran the commands, got <waiting for device> like the other guy in that post, already had the drivers but reinstalled anyway, updated driver in device manager--it sees it as Android 1, but has the correct driver and says is working properly--tried several different ways to flash the system.img, still get the <waiting for device> any suggestions?
thanks for your help by the way, really appreciate it.
Click to expand...
Click to collapse
It should say Android ADB Interface under ADB Interface in Device Manager. Mine says Samsung Android ADB Interface. The waiting for device is a driver issue. I've usually had to install drivers for it to recognize the phone in fastboot, even if it is already recognized by adb.
mwalt2 said:
It should say Android ADB Interface under ADB Interface in Device Manager. Mine says Samsung Android ADB Interface. The waiting for device is a driver issue. I've usually had to install drivers for it to recognize the phone in fastboot, even if it is already recognized by adb.
Click to expand...
Click to collapse
Praise baby jesus and yourself kind sir! I finally got the ****ing thing to work. It was the drivers all along. Had to go into the registry and edit the string for portable devices and fix the port numbers. After that everything worked just fine, Thanks again for your help!
Nadreo said:
Praise baby jesus and yourself kind sir! I finally got the ****ing thing to work. It was the drivers all along. Had to go into the registry and edit the string for portable devices and fix the port numbers. After that everything worked just fine, Thanks again for your help!
Click to expand...
Click to collapse
Haha, glad you got it working. It's really nice having an open device like the nexus and now you learned how to use some of the tools (no need for a 'toolkit'!).
Sent from my Nexus 7 using xda premium
Hi guys. I recently flashed the Glitched Kernel (http://forum.xda-developers.com/showthread.php?t=2449919) to my Nexus, but I accidently downloaded the wrong one. Not knowing this, I flashed it via TWRP and now my device crashes completely (my computer won't even recognize it) on the lock screen. I can still boot into the bootloader, TWRP, and MultiROM easily. I just can't boot up Cyanogenmod (Only rom I have on the device as of now). I really don't know what to do. I've tried connecting via USB in the bootloader, my computer won't even pick up the device. I've also tried adb sideload a new rom and a new kernel, but I get the error 'protocol fault (no status)' which is weird, because ADB recognizes my device (I typed the 'adb devices' command in CMD) How can I flash the stock kernel back onto it?
Thanks in advance,
~NascarBoy119
Just clean flash cyanogenmod again if you have the Rom as .zip on your device. If not use ADB to get a Rom for flashing on your device.
Restore your backup (nandroid).
detoxN said:
Just clean flash cyanogenmod again if you have the Rom as .zip on your device. If not use ADB to get a Rom for flashing on your device.
Click to expand...
Click to collapse
I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]), as I stated above.
Also @wantabe
Shortly before this I ran Clean Master on my device. Turned out it deleted my backups... After that, all this drama happened. Probably kinda my fault as I used the TWRP backup feature instead of NanDriod.
NascarBoy119 said:
I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]), as I stated above.
Also @wantabe
Shortly before this I ran Clean Master on my device. Turned out it deleted my backups... After that, all this drama happened. Probably kinda my fault as I used the TWRP backup feature instead of NanDriod.
Click to expand...
Click to collapse
adb is your friend. There is plenty of opportunities. You could download a ROM on your computer and sideload or push it in adb. You could also download stock images and fastboot it in the bootloader. Simple...
Sent from my Nexus 7 using Tapatalk
NascarBoy119;49329133]I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]).
Click to expand...
Click to collapse
nikr123 said:
adb is your friend. There is plenty of opportunities. You could download a ROM on your computer and sideload or push it in adb. You could also download stock images and fastboot it in the bootloader. Simple...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
As you see the text that I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?
NascarBoy119 said:
As you see the text what I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?
Click to expand...
Click to collapse
what android version are your running?
anyways grab the gltiched kernel for your device this time.
then put your device i to recovery: up/down volume plus power when device is off
once in recovery type thus from your computer.
fastboot flash boot boot.img
you will need to extract the image from the glitched-kernel.zip
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.
NascarBoy119 said:
As you see the text what I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?
Click to expand...
Click to collapse
Fastboot is your friend in this case, as long as you didn't relock your bootloader you can flash without losing your data.
userdelroot said:
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.
Click to expand...
Click to collapse
^this
Not using cleanmaster to delete your backups was a lesson you learned the hard way, but it is not unrecoverable and you can chalk it up as a learning experience.
Let us know how it worked out, everything will be fine as long as you take your time and relax. This is something that happens to most people sooner or later and is a great confidence builder (once you work through it).
To avoid this I keep all my backups, zips and other flashaholic stuff on a USB drive mounted using an USB OTG cable. You can mount it and use it in recovery.
megabatteryman said:
To avoid this I keep all my backups, zips and other flashaholic stuff on a USB drive mounted using an USB OTG cable. You can mount it and use it in recovery.
Click to expand...
Click to collapse
This may very well be the top reason to buy an OTG cable and/or OTG Micro SD reader / hub device
Sent from my Nexus 7 using XDA Premium HD app
userdelroot said:
what android version are your running?
anyways grab the gltiched kernel for your device this time.
then put your device i to recovery: up/down volume plus power when device is off
once in recovery type thus from your computer.
fastboot flash boot boot.img
you will need to extract the image from the glitched-kernel.zip
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.
Click to expand...
Click to collapse
oldsoldier2003 said:
Fastboot is your friend in this case, as long as you didn't relock your bootloader you can flash without losing your data.
Not using cleanmaster to delete your backups was a lesson you learned the hard way, but it is not unrecoverable and you can chalk it up as a learning experience.
Let us know how it worked out, everything will be fine as long as you take your time and relax. This is something that happens to most people sooner or later and is a great confidence builder (once you work through it).
Click to expand...
Click to collapse
I did what you guys said and it work flawlessly. Thank you so much! I was worried I permanently bricked my device. I though about buying an OTG cable, but now I think I'm buying it for sure. I'll try to store some backups on it too.
Awesome, glad we could help
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!
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.