Related
My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Things to try
acesofbelkan said:
My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Click to expand...
Click to collapse
It looks like you've tried just about everything and you are very capable of getting it done. My only suggestion is that when I thought I was bricked, I kept wiping all the data I could find. From CWM I started with a wipe data/factory reset and that had the best results for me. After that, wipe dalvik, wipe battery stats, and I tried loading a new ROM from sdcard. I wouldn't try to install a new kernel or any other mod until you successfully boot into your new(or old) ROM.
Like I said, you probably already knew all of this but I wanted to make sure all the bases were covered. If it doesn't help you, I hope it at least helps someone else. Good luck, and please post your progress!
try using fastboot to erase the system and other partition.
fastboot erase system
fastboot erase userdata
faseboot erase boot
fastboot erase recovery
Then flash stock from fastboot
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
acesofbelkan said:
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
Click to expand...
Click to collapse
Fastboot does not require mounting of anything -- it writes to the entire partition.
efrant said:
Fastboot does not require mounting of anything -- it writes to the entire partition.
Click to expand...
Click to collapse
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
acesofbelkan said:
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
Click to expand...
Click to collapse
No. Root has nothing to do with fastboot. Root has nothing to do with your device. Root has to do with the Android build that you are running.
When you are booted into the bootloader (i.e., fastboot mode), there is no Android OS running, so how can there be root?
The fastboot executable on your PC interacts directly with the bootloader, and it will wipe an entire partition, or write an image to a partition.
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
NoorGnex said:
[snip]
first off you need to download wugfresh's Gnex toolkit
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1469909
efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
I've personally never had problems with tool kits and have found them very helpful, because of my busy schedule I don't have the time to do it myself even with my amateur coding skills, and have found only people who dont understand what there getting themselves into get bricked, thats not to say you cant brick your phone if your smart but if your smart you would have done a nandroid before flashing anything.
thanks again for that enlightening post
NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
Click to expand...
Click to collapse
Link is bringing up a 404 error. Did the toolkit move locations?
JackG058 said:
Link is bringing up a 404 error. Did the toolkit move locations?
Click to expand...
Click to collapse
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
NoorGnex said:
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
JackG058 said:
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
Click to expand...
Click to collapse
This is what you should be reading for due diligence...
efrant said:
This is what you should be reading for due diligence...
Click to expand...
Click to collapse
I will add this to my reading list, and send you my kind thanks.
edit: And bookmarking, of course.
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
That's what I was trying to get across earlier...
Use this: http://forum.xda-developers.com/showthread.php?t=1626895 That way, you can see where you are having issues.
And in case you missed it earlier: http://forum.xda-developers.com/showpost.php?p=30015315&postcount=9
NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
Click to expand...
Click to collapse
Only after you learn what is going on in the background.
I think i'm going to stop trying to help people using toolkits if it seem that they did not even bordered to read up on fastboot and adb..
efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
+1
acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
This quote pretty much defines why people hate toolkits.
I'm experiencing some issues. I flashed a bad rom and now I'm stuck at boot screen (google logo). I can enter fastboot, but I can't get into CWM. I've tried the nexus toolkit, but the ADB drivers won't function.
What do I do next?
Hope I haven't bricked my phone...
If you can enter fast boot then your phone is not bricked. Read up on how the flash the stock Google image using fast boot. You will loose all you data but you will have a working phone again.
Sent from my Galaxy Nexus using xda premium
Ok, the problem is that suddenly my computer won't see the phone as an ADB device. I've tried every usb driver I can find. I've tried the PDAnet, but I won't install properly when I can't enter the rom and tick the usb debugging mode.
killbox said:
Ok, the problem is that suddenly my computer won't see the phone as an ADB device. I've tried every usb driver I can find. I've tried the PDAnet, but I won't install properly when I can't enter the rom and tick the usb debugging mode.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
I managed to get into CWM
What I'm actually trying to do is to restore a cwm backup I made before I sent my device to repair the usb port.
So far I've figured out that you must be using a ICS rom to be able to restore a ICS backup right?
killbox said:
I managed to get into CWM
What I'm actually trying to do is to restore a cwm backup I made before I sent my device to repair the usb port.
So far I've figured out that you must be using a ICS rom to be able to restore a ICS backup right?
Click to expand...
Click to collapse
Not necessarily but you will need to format/wipe data if restoring a different OS version.
Sent from my Galaxy Nexus using xda premium
Ok, will I loose everything on SD card then? included cwm backups?
killbox said:
Ok, will I loose everything on SD card then? included cwm backups?
Click to expand...
Click to collapse
Nah only app+data. Your "SD Card" will be fine.
Ok, tried that.
I get:
Error while restoring /system!
I'm not quite sure, but I think the rom I'm trying to restore is ARHD 4.1.0, while the one I have now is ARHD 6.1.0
killbox said:
Ok, tried that.
I get:
Error while restoring /system!
I'm not quite sure, but I think the rom I'm trying to restore is ARHD 4.1.0, while the one I have now is ARHD 6.1.0
Click to expand...
Click to collapse
Did you ever figure out how to fix this??
I just ran into a similar dilemma and have yet to fix it.
On my Verizon Galaxy Nexus, I had Vicious Jellybean V.5
Starting acting up.
Made a backup using CW.
Went to recovery.
Wiped the device for a clean install.
Then went to use the toolkit and the drivers wont install properly..
FML.
I can boot into FASTBOOT, CWM recovery, and ODIN. But Google logo is as far as it gets when I try to get into android..
I'm using the latest version of Galaxy Nexus Toolkit V.7.8
Any way to flash using Odin?? Way back when, there was something like odin that I used for my Droid X.. Does that exist?
PLEASE HELP :\
mikeright25 said:
Did you ever figure out how to fix this??
I just ran into a similar dilemma and have yet to fix it.
On my Verizon Galaxy Nexus, I had Vicious Jellybean V.5
Starting acting up.
Made a backup using CW.
Went to recovery.
Wiped the device for a clean install.
Then went to use the toolkit and the drivers wont install properly..
FML.
I can boot into FASTBOOT, CWM recovery, and ODIN. But Google logo is as far as it gets when I try to get into android..
I'm using the latest version of Galaxy Nexus Toolkit V.7.8
Any way to flash using Odin?? Way back when, there was something like odin that I used for my Droid X.. Does that exist?
PLEASE HELP :\
Click to expand...
Click to collapse
If you can boot into recovery you can just flash a ROM onto your phone. If for some reason you don't have one then just boot to recovery, go to mounts and storage, mount the SD card, then you should be able to put a ROM on there and flash it.
For future reference I would personally stay away from the toolkit. It's convenient but there isn't really a substitute for knowing how to do everything yourself =]
If you need more help feel free to PM me!
foxehkins said:
If you can boot into recovery you can just flash a ROM onto your phone. If for some reason you don't have one then just boot to recovery, go to mounts and storage, mount the SD card, then you should be able to put a ROM on there and flash it.
For future reference I would personally stay away from the toolkit. It's convenient but there isn't really a substitute for knowing how to do everything yourself =]
If you need more help feel free to PM me!
Click to expand...
Click to collapse
Hey,
Thanks so much for the quick response! Unfortunately, the biggest problem lies in the fact that I am unable to push anything to CWM recovery because my computer wont install the driver properly and I've been trying to figure out a way to do that or push a file to the phone for 6 hrs now
When I did a factory reset and wiped cache it actually deleted the backup that I made and everything else..
So I need to find a way to get a zip file on to the phone to flash or figure out how to get this driver working. Maybe a different computer.. Ugh.
I've been looking into ODIN and such, But this is so frustrating. Can't believe I made such a rookie mistake.
-Mike
mikeright25 said:
Did you ever figure out how to fix this??
I just ran into a similar dilemma and have yet to fix it.
On my Verizon Galaxy Nexus, I had Vicious Jellybean V.5
Starting acting up.
Made a backup using CW.
Went to recovery.
Wiped the device for a clean install.
Then went to use the toolkit and the drivers wont install properly..
FML.
I can boot into FASTBOOT, CWM recovery, and ODIN. But Google logo is as far as it gets when I try to get into android..
I'm using the latest version of Galaxy Nexus Toolkit V.7.8
Any way to flash using Odin?? Way back when, there was something like odin that I used for my Droid X.. Does that exist?
PLEASE HELP :\
Click to expand...
Click to collapse
If you can go to CWM, AND you have fastboot and adb files, you can always push one of the ROM to sdcard via "adb push ROM_NAME.zip /sdcard/"
If you don't have adb and fastboot files, just google them. It wouldn't be hard to find
mikeright25 said:
Hey,
Thanks so much for the quick response! Unfortunately, the biggest problem lies in the fact that I am unable to push anything to CWM recovery because my computer wont install the driver properly and I've been trying to figure out a way to do that or push a file to the phone for 6 hrs now
When I did a factory reset and wiped cache it actually deleted the backup that I made and everything else..
So I need to find a way to get a zip file on to the phone to flash or figure out how to get this driver working. Maybe a different computer.. Ugh.
I've been looking into ODIN and such, But this is so frustrating. Can't believe I made such a rookie mistake.
-Mike
Click to expand...
Click to collapse
Did your computer recognize the device before? If so then you shouldn't need to reinstall the drivers. PM me and I can try to wlk you through it over gtalk or something.
---------- Post added at 04:05 PM ---------- Previous post was at 03:58 PM ----------
The drivers can also be found here. http://dl.dropbox.com/u/15110285/FYA Files/GNexus-root-package-FYA.zip
Have you tried downloading the drivers again?
Sent from my Galaxy Nexus using xda app-developers app
Change operating systems..
Just uninstall all drivers, reboot, feed it the same driver again.
bk201doesntexist said:
Change operating systems..
Just uninstall all drivers, reboot, feed it the same driver again.
Click to expand...
Click to collapse
Thanks guys for the ideas
But, yes my computer used to recognize the Nexus just fine.
Now, tried all usb ports didn't work, and trying it in my old computer (with the 32bit version of win7 instead of x64) gave a pnpui.dll error (which I'm going to assume means plug n play user interface error).
The first kind of fresh idea is using ADB commands [good thought], but I haven't used those since I first got it, when the nexus was released.
And I believe, in that case the drivers will still need to be recognized..Right?
I'm going to try going through the precise steps in the WugToolkit for installing the drivers, but I have a feeling that something that affects the drivers may have been wiped when I did the whole factory reset/cache wipe (to an already corrupt version of jellybean)
Any other ideas guys?
mikeright25 said:
Thanks guys for the ideas
But, yes my computer used to recognize the Nexus just fine.
Now, tried all usb ports didn't work, and trying it in my old computer (with the 32bit version of win7 instead of x64) gave a pnpui.dll error (which I'm going to assume means plug n play user interface error).
The first kind of fresh idea is using ADB commands [good thought], but I haven't used those since I first got it, when the nexus was released.
And I believe, in that case the drivers will still need to be recognized..Right?
I'm going to try going through the precise steps in the WugToolkit for installing the drivers, but I have a feeling that something that affects the drivers may have been wiped when I did the whole factory reset/cache wipe (to an already corrupt version of jellybean)
Any other ideas guys?
Click to expand...
Click to collapse
I recommend using this package by 1wayjonny. It works perfectly and, unlike most other packages, 1wayjonny’s repack does not install any crapware along with it. That said, it doesn’t include an .exe file, so it needs to be installed manually from the .inf file. If you do not now how to do that, see here for instructions.
killbox said:
Ok, the problem is that suddenly my computer won't see the phone as an ADB device. I've tried every usb driver I can find. I've tried the PDAnet, but I won't install properly when I can't enter the rom and tick the usb debugging mode.
Click to expand...
Click to collapse
Just a quick FYI "adb" is only accessible once booted up to the rom.
Had my note 2 for several months now on Wind Mobile. I woke up this morning and it was working fine, went out for a walk and 5 minutes into the walk my phone was stuck in the boot loop. I never flashed or rooted my phone. Its stuck where the samsung logo comes up and the blue and purple halo circles it. I have access to both the volume up+home button+power button menu, aswell and the volume down menu. I already cleared the system cache and was wondering what to do?
If possible i would like to be able to extract my data before doing a factory reset. Any help would be great!
It doesnt seem that wiping data will fix your problem it looks like system corruption try flashing new software
Sent from my GT-N7100 using xda premium
Note2Dan said:
Had my note 2 for several months now on Wind Mobile. I woke up this morning and it was working fine, went out for a walk and 5 minutes into the walk my phone was stuck in the boot loop. I never flashed or rooted my phone. Its stuck where the samsung logo comes up and the blue and purple halo circles it. I have access to both the volume up+home button+power button menu, aswell and the volume down menu. I already cleared the system cache and was wondering what to do?
If possible i would like to be able to extract my data before doing a factory reset. Any help would be great!
Click to expand...
Click to collapse
You will have to factory reset your device not sure if there is a possible way to recovery Data as its not booting.
aukhan said:
You will have to factory reset your device not sure if there is a possible way to recovery Data as its not booting.
Click to expand...
Click to collapse
cleared cache, flashed new stock rom, and wipred all data. still stuck in boot?
Note2Dan said:
cleared cache, flashed new stock rom, and wipred all data. still stuck in boot?
Click to expand...
Click to collapse
SIMPLE goto stock recovery and do a factory reset that will boot up your device.
aukhan said:
SIMPLE goto stock recovery and do a factory reset that will boot up your device.
Click to expand...
Click to collapse
Did this multiple times, also when i go to that menu it says cannot mount efs
Note2Dan said:
Did this multiple times, also when i go to that menu it says cannot mount efs
Click to expand...
Click to collapse
this seems to a new level let me check on this.
Note2Dan said:
cleared cache, flashed new stock rom, and wipred all data. still stuck in boot?
Click to expand...
Click to collapse
have u tried using odin flashhttp://www.nobutaka.es/web/index.php/component/jcomments/feed/com_content/203.html
shhbz said:
have u tried using odin flash
Click to expand...
Click to collapse
Yes i used odin to flash the stock rom, did not work.
Note2Dan said:
Yes i used odin to flash the stock rom, did not work.
Click to expand...
Click to collapse
give this a try translate using google translator http://www.nobutaka.es/web/index.php/component/jcomments/feed/com_content/203.html and follow the procedure
shhbz said:
give this a try translate using google translator and follow the procedure
Click to expand...
Click to collapse
Ok, will try in the morning. Google translate doesnt seem to give a very clear translation of the page but i will try my best.
shhbz said:
give this a try translate using google translator and follow the procedure
Click to expand...
Click to collapse
Im trying to follow this guide but it gets confusing, ive manage to download adb + fastboot but im not sure where i go from here.
Note2Dan said:
Im trying to follow this guide but it gets confusing, ive manage to download adb + fastboot but im not sure where i go from here.
Click to expand...
Click to collapse
well u need to set up adb in windows and make sure its connecting with your device
u need to flash stock then chainfire auto root
check if its entering recovery now then proceed with adb hopefully u have efs backup .tar file safe in pc or anywhere ,search google how to set adb
it seems to be an issue with efs partition,
i blv this can be even done by flashig pit file http://d-h.st/Dlv here and then the stock firmware.
and since u have never rooted use ur warranty and give it to service guys if not able to solve
edit:read this thread in english hope u understand now http://forum.xda-developers.com/showthread.php?t=2204960
the solution lies here http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
u can get some idea on setting up adb from a very old thread of mine http://forum.xda-developers.com/showthread.php?t=1038338 read part installing custom recovery and how to make adb work
Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.
jakubmi9 said:
Hello everyone!
I suspect that my N7(2013) bricked itself overnight. Before going to sleep, I was watching videos on YouTube. If I remember correctly it was around 45% of battery left. I just put it to sleep as usually, and gone to sleep. In the morning it was dead, so I plugged it to charger and left it that way. After an hour, when I came back I turned it on. It showed the google screen and I put it down. After a while I noticed, that it's still on google logo. I decided to hold the power button so it could reboot. After a reboot, nothing has changed. Next idea I came up with was to enter the bootloader. Tablet booted to bootloader normally and then:
-Start option hangs on google logo
-power off works just fine
-reboot bootloader also works
-recovery mode hangs indefinitely on TeamWin logo.
By now, I have no idea what to do with it. The point is would like to save my data. Is there anything that could be done?
Nexus 7 (2013) Wi-Fi
Stock KOT49H - rooted with Xposed Framework
Stock kernel
TWRP 2.6.3.0 if i'm not mistaken
Thanks in advance.
Click to expand...
Click to collapse
Sound like pretty much your only option is to flash a factory image thru fastboot, you can download them from here
https://developers.google.com/android/nexus/images#razor
Make sure your boot loader is unlocked
Boot the tablet in to fastboot and run the flash-all.bat file if your using windows, of flash-all.sh for Mac and Linux.you should now have a stock tablet, with the stock recovery, I would also perform a factory data reset thru the stock recovery before rebooting the tablet.
If you would rather use a toolkit, wugs fresh is a good toolkit, and should be able to automate the above steps.
http://www.wugfresh.com
I should also point out that you need to have the proper driver's installed on your PC wugs fresh should guide you thru the process, if you don't already have them installed
I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk
jakubmi9 said:
I forgot to mention: Yes my bl is unlocked, but doesn't flashing factory image wipe all data? I have one more question: On my PC xperia fastboot drivers are installed. Can I use them, or do I have to install some other drivers? Fastboot recognizes device but I want to be sure.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
If it is recognize in fastboot you should be good to go, and yes it will wipe you data unfortunately if you can't enter recovery, there's not much that can be done. I have never been in this situation myself, and maybe someone with more experience than I will have a solution, such as reformatting your partitions thru fastboot, but as I said I've never found myself in this situation, and if it were me I would just flash back to stock, if you happen to have a backup on your PC, you can reinstall your recovery, and restore your backup, anything else is above my understanding of this, or is not possible.
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
If adb is working then you can adb pull your files assuming the file path it not corrupted
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
jakubmi9 said:
All backups are on tablet both titanium and TWRP. I just wanted to know if it's possible to recover it. I'll try to flash everything w/out wiping data. I think there was such option in wugfresh's toolkit. Maybe it's just one partition that's broken. But I've got feeling like it's going to be data partition that's broken. Thanks for help anyway. I'll try that tomorrow, because it's late night now.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.
LinearEquation said:
Just Swipe to factory reset in TWRP (leaves data in tact) and flash your Nandroid. Then reboot into system. You can adb sideload onto TWRP from your computer as well. This requires adb not fastboot.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe he cannot boot into recovery, so he cannot simply factory reset, no? I also thought that to use the adb side load feature, you had to be able to access twrp advanced>adb Sideload and that's for installing zips, no? I was thinking maybe he could adb pull a backup from the device, then install factory image, flash twrp, then restore from there? Or maybe simply reflashing the recovery? (I personally wasn't going to recommend any of this, since I don't have any personal experience in the situation) Maybe I'm missing something? or maybe I'm just an idiot, and I'm in over my head, and I need to read into things more before I post? feel free to tell me so. I'm always trying to learn about anything I can, and someone with more experience setting me straight is always a good way to achieve this lol. I like mpdamaged idea, but isn't that pretty much a dirty flash, and carries some inherent risks, seeing as how he's using xposed, I know it doesn't make any permanent changes to your system, but wouldn't this be the same concept as accepting an ota, in witch case you would need to first remove the xposed framework? Anyway hopefully someone can fill me in and he fixes his tablet, and I learn something lol.
mdamaged said:
There is a file called flash-all in the factory images, open it and remove the -w from the command line, that is what wipes the data.
Click to expand...
Click to collapse
This. You can flash a factory image without data getting cleared and it's a very simple mod. Alternative is to extract the factory image until U have all .img files extracted (have to extract twice if I remember right) then u can fastboot flash system.img and boot.img only and that should work
Another thing, have you tried to reflash TWRP since it stopped working? Could just be corrupted and a reflash could fix it.
Nexus 7 LTE
Carbon Rom
Faux Kernel
---------- Post added at 01:04 PM ---------- Previous post was at 12:58 PM ----------
@ Thisguysayswht flashing just the system.img will wipe any system mods such as Xposed, used to do it when I was on stock to be able to install OTA
Nexus 7 LTE
Carbon Rom
Faux Kernel
Don't know if you figured out how to save your data before flashing factory image but there is a very easy way to save your Titanium Backups and TWRP backups,
Plug your Nexus 7 into your computer and using MTP (assuming that still works) and look for the TB and TWRP files you can copy them to your computer and once you get your N7 back working just copy the files back to your N 7 and all your backups will be there for you to use. You can even open the files and save just what is important or save everything.
Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
Yes I know that, but as I said tablet is totally unconnectable via adb. Can't boot to Android and can't boot to recovery. By the way I realized that when I hotbooted stock kernel from fastboot it froze on the bootloader screen but I left it plugged to PC and after a while my PC recognized "unknown MTP device" but couldn't find any drivers for it. If I hotboot TWRP.img is it gonna boot to recovery or it doesn't work like that?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
TWRP will work like that.
fastboot boot twrp-whaetver.img
If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk
jakubmi9 said:
If my memory serves me right, Titanium Backup can restore apps from TWRP backup, right? That way I should be able to save all my data.
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yes, so does Nandroid Manager.
I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
I've just tried to hotboot TWRP 2.7 but it got stuck on TeamWin logo. It's been two or three minutes now. I don't think it will boot anymore, am I right?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Yeah, it would come up pretty quick. Something's not right...try an older version to rule that out, I know 2.6.3 worked for me using fastboot boot.
TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk
jakubmi9 said:
TWRP is still hanged but device manager showed up "nexus 7" with everything else unknown and code 28 which is no driver installed. Which driver should I install for it?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
Officially these: http://developer.android.com/sdk/win-usb.html#download
This one worked for me until I figured out how to do it right but must be with PTP not MTP: http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
I think that my nexus boots up everything normally but the screen just hangs on first frame of that thing. Any ideas what would that mean?
Sent from my HTC One S using Tapatalk
HTC M8 AT&T
I have been dealing with this all morning and I am about to blow my brains out.
I thought i was running twrp but was instead running CWM.
Previously had Cyanogen Mod working fine on the phone no issue. Just wanted android instead
Tried to install Android Revolution from zip. Boom done. Reboot
Encryption. Try all 10 passwords i EVER use a couple hundred times it seems.
Fail. So i go back to CWM and try to reset phone to factoy. Gives me error "unknown volume for path /sd-ext/
error mounting /sdcard/.android_secure!
Skipping Format
Data Wipe Complete
Boot up still asks for password try a hundred times again. Still nothing
Boot into fastboot to attempt to put TWRP on it. and no computer sees my phone in fastboot.
Any ideas how to save my phone?
Do you a nandroid backup? You can restore your phone and try one more time.
Tapatalked with my "refrigerator look" HTC one M8
Go me the noob. No nandroid.
Any other idea..
Do you get the ding when connecting the phone and are running a command prompt from the folder with fastboot binary and required files?
What response does 'fastboot devices' give?
ashyx said:
Do you get the ding when connecting the phone and are running a command prompt from the folder with fastboot binary and required files?
Click to expand...
Click to collapse
No and when i run adb devices i get nothing
xagesz said:
No and when i run adb devices i get nothing
Click to expand...
Click to collapse
Adb won't respond unless you sideload or boot Into os.
Check your usb cable, make sure it's the original cable and you have fastboot drivers installed.
ashyx said:
Adb won't respond unless you sideload or boot Into os.
Check your usb cable, make sure it's the originals cable and you have fastboot drivers installed.
Click to expand...
Click to collapse
I tried sideloading a rom. but still encryption screen. and Fastboot has worked before because i used it to install cwm. BOot into it how?
xagesz said:
I tried sideloading a rom. but still encryption screen. and Fastboot has worked before because i used it to install cwm. BOot into it how?
Click to expand...
Click to collapse
If you don't hear the ding then you either have a cable problem or a driver problem. Just re-install the drivers and check the cable
http://forum.xda-developers.com/showthread.php?t=2588979
ashyx said:
Adb won't respond unless you sideload or boot Into os.
Check your usb cable, make sure it's the original cable and you have fastboot drivers installed.
Click to expand...
Click to collapse
ashyx said:
If you don't hear the ding then you either have a cable problem or a driver problem. Just re-install the drivers and check the cable
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I am working this angle now but even so what do I need to do to save my phone
xagesz said:
I am working this angle now but even so what do I need to do to save my phone
Click to expand...
Click to collapse
From what I seen you going to need to format the sd. You can see if twrp will format it but if that don't work try stock recovery and do a factory reset in bootloader.
Darknites said:
From what I seen you going to need to format the sd. You can see if twrp will format it but if that don't work try stock recovery and do a factory reset in bootloader.
Click to expand...
Click to collapse
DARKNITES YOU ARE THE MAN. I send you a case a beer. Anyway... CWM menu down at the bottom is format data and media. never spotted this before and did that and the phone finally went around the darn encryption menu. THank you.
xagesz said:
I am working this angle now but even so what do I need to do to save my phone
Click to expand...
Click to collapse
As said if you get fastboot working you can flash a custom recovery or stock. You can then download a stock nandroid back up from the stock backups thread then flash the required backup from custom recovery.
All explained in that thread.
ashyx said:
As said if you get fastboot working you can flash a custom recovery or stock. You can then download a stock nandroid back up from the stock backups thread then flash the required backup from custom recovery.
All explained in that thread.
Click to expand...
Click to collapse
Yeah. Fastboot was not working AT ALL. I tried and tried. But the issue is now resolved. Thanks.
xagesz said:
DARKNITES YOU ARE THE MAN. I send you a case a beer. Anyway... CWM menu down at the bottom is format data and media. never spotted this before and did that and the phone finally went around the darn encryption menu. THank you.
Click to expand...
Click to collapse
Don't drink beer but thanks away and no problem dude.