Develop Bugs

[Q] Bricked LTE Galaxy Nexus Help!

Does anyone happen to have a way to flash the stock img in fastboot? I can't find the stock LTE variant anywhere.
I unlocked the bootloader through fastboot, then ran p3Droid's root method for the LTE galaxy nexus, and now the phone will just get stuck at the google logo.
I did manage to install CWM onto the phone, but since there is no SD card, I can't push anything in ADB to the phone. It just gives me an error when I try. If there is anyone who could help, that would be amazing!
More information:
Yes, fastboot commands still work. I have tried flashing various boot.imgs to the phone to no effect such as the one from the nandroid on rootzwiki and also flashing the boot.img from the only LTE ROM on rootzwiki as well.

overlord727 said:
Does anyone happen to have a way to flash the stock img in fastboot? I can't find the stock LTE variant anywhere.
I unlocked the bootloader through fastboot, then ran p3Droid's root method for the LTE galaxy nexus, and now the phone will just get stuck at the google logo.
I did manage to install CWM onto the phone, but since there is no SD card, I can't push anything in ADB to the phone. It just gives me an error when I try. If there is anyone who could help, that would be amazing!
More information:
Yes, fastboot commands still work. I have tried flashing various boot.imgs to the phone to no effect such as the one from the nandroid on rootzwiki and also flashing the boot.img from the only LTE ROM on rootzwiki as well.
Click to expand...
Click to collapse
As simple as it sounds, have you tried booting into recovery and doing a factory reset and clearing your cache?

I have done this many times. Also, CWM keeps throwing an error about the sd card among other things

Have you posted your issue on MDW? P3 may have the necessary files to flash via odin. The files are out there, but people have been strictly instructed to not release them.
Again, I would check with P3 for the fix.
He is not responsible for the issue, but he may be able and willing to help.

Hmm I will post there. I have posted on his forum for something else, but maybe If I make a thread he will notice it

Doesn't the recovery have an option to mount USB storage?
Sent from my Sensation using Tapatalk

It says this, but it wont actually do it. Unless there is something I am missing when I try this. I am connected via the USB to the computer, but nothing pops up.

Just checking in. Have you found a solution yet?
I can tell you that on my VZW Gnex that it will not allow you to transfer files via usb in CWR, as you have stated. Your only hope is a .tar file for Odin. Did you get any reply at MDW?

overlord727 said:
It says this, but it wont actually do it. Unless there is something I am missing when I try this. I am connected via the USB to the computer, but nothing pops up.
Click to expand...
Click to collapse
adb push the files you need to the sdcard

KiNG OMaR said:
adb push the files you need to the sdcard
Click to expand...
Click to collapse
I cant believe I left this one out lol. Good call!

The issue is, I get an error every time I try to push anything to the SD card. I dont know what the problem is. What I really need is a systemimg

Why do people always say their phone is "bricked" when it clearly isn't lol :S

this is why I should wait before rooting. there seems to be no clear solutions available yet.
overlord727 said:
Does anyone happen to have a way to flash the stock img in fastboot? I can't find the stock LTE variant anywhere.
I unlocked the bootloader through fastboot, then ran p3Droid's root method for the LTE galaxy nexus, and now the phone will just get stuck at the google logo.
I did manage to install CWM onto the phone, but since there is no SD card, I can't push anything in ADB to the phone. It just gives me an error when I try. If there is anyone who could help, that would be amazing!
More information:
Yes, fastboot commands still work. I have tried flashing various boot.imgs to the phone to no effect such as the one from the nandroid on rootzwiki and also flashing the boot.img from the only LTE ROM on rootzwiki as well.
Click to expand...
Click to collapse
No worry...you probably soft-bricked it.

Use fastboot to flash CWM. If CWM cannot read the file system, wipe the cache and reboot.
Sent from my Galaxy Nexus using Tapatalk

thrillerbee said:
Use fastboot to flash CWM. If CWM cannot read the file system, wipe the cache and reboot.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I have the same problem, except its a GSM phone, not a LTE Verizon.
I tried wiping the cache clean and rebooting, the phone is still stuck at the google logo screen!
What should I do?!?!?! I'm desperate here...

you should be able to get into ADB mode at some point, to push the file to /data/media (= /sdcard).
If you're seeing CWM recovery mode, then you're fine. ADB would see your phone as ADB-recovery.
When it does, push boot.img, and recovery.img into "/data/media" not "/sdcard/". (There is a permission issue with soft link).
If you succeed pushing the files into your Nexus, the rest is just flashing the files in FASTBOOT.
Your last successul boot had 4.0.2? or 4.0.4? Be sure to match the two files above to the correct version. Otherwise, you'll be stuck with those google logo

[Q] Phone bricked, no ODIN access! E: Unable to mount '/data'

Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster

Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2

elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster

I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.

Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC

Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.

lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash

elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster

Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.

lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!

Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD

elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster

I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.

coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.

Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium

Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.

Nexus 7 (2013) self-bricked??

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

Bootloop into TWRP recovery

I flashed Slimkat 4.4.4 a couple weeks ago and don't like it so I attempted to change it to AOSP tonight and I wiped the cache, partition, formatted the system and attempted to flash the rom and got a "fail" sign. Now when I reboot from TWRP menu, it keeps going back into TWRP recovery, after I see the Samsung and Slimkat words on my phone. I tried rebooting into system, keeps going back into recovery. I was going to attempt to reflash Slimkat but now my laptop won't recognize my phone. I saw where someone pulled the battery out and it just booted into recovery. Please help me and thank you in advance.

This is why you should never manually format your /system partition. If your rom flash fails, you have no OS to boot into. I really dont know why so many people still say to do this.
You need to either use Odin to flash your firmware, or download another rom (or your previous one) and flash it from TWRP. Youll have to plug your external SD Card into your computer and copy it to there, then put the card back in and flash.

DocHoliday77 said:
This is why you should never manually format your /system partition. If your rom flash fails, you have no OS to boot into. I really dont know why so many people still say to do this.
You need to either use Odin to flash your firmware, or download another rom (or your previous one) and flash it from TWRP. Youll have to plug your external SD Card into your computer and copy it to there, then put the card back in and flash.
Click to expand...
Click to collapse
Lesson learned. I really don't know who to listen to, I should have just left it alone like a good girl. But I really did not like Slimkat. :laugh: My laptop is not recognizing my phone through usb. Would Odin recognize it if I put it in download mode?

Its worth a try I think. But otherwise do you have a way to plug your sd card into the computer? You could copy a rom to flash im recovery that way.
If not youll probably need to try installing different drivers. You can get plenty to try from the link in my sig.
I usually say to just follow the instructions in the OP of what you are trying to flash. If they tell you to format system, I would ignore that part unless they have a good explanation for why.

DocHoliday77 said:
Its worth a try I think. But otherwise do you have a way to plug your sd card into the computer? You could copy a rom to flash im recovery that way.
If not youll probably need to try installing different drivers. You can get plenty to try from the link in my sig.
I usually say to just follow the instructions in the OP of what you are trying to flash. If they tell you to format system, I would ignore that part unless they have a good explanation for why.
Click to expand...
Click to collapse
I'm guessing the only other way to plug an sd card into my computer is to stick the card in another phone? Meanwhile I will try to install drivers and get my computer to recognize my phone.

You can usually find an adapter for a few bucks online or at places like wal mart. Sorry. Was just assuming you had one. Without it, yes youll have to try different drivers or find another way to get it going via one of the two methods I mentioned.
When trying different drivers, just installing the package doesn't always do the job. You should go into device manager and manually select update drivers, then browse to the folder in Program Files and choose it there.
When you plug in now, does it at least detect it? Are you trying while in Download Mode?

DocHoliday77 said:
You can usually find an adapter for a few bucks online or at places like wal mart. Sorry. Was just assuming you had one. Without it, yes youll have to try different drivers or find another way to get it going via one of the two methods I mentioned.
When trying different drivers, just installing the package doesn't always do the job. You should go into device manager and manually select update drivers, then browse to the folder in Program Files and choose it there.
When you plug in now, does it at least detect it? Are you trying while in Download Mode?
Click to expand...
Click to collapse
I tried putting my SD card into my daughters phone which is a Samsung but different model and I thought I put the old Slimkat rom what looked to be the extsdcard folder but when I went to recovery to install the rom I saw the corrupt rom I attempted to install last night. When I went to device manager to manually update the drivers, the computer recognizes my phone but said that the drivers couldn't be installed. Maybe I'm getting confused with this TWRP recovery I'm not familiar with. It has an install feature, so I tried to flash the rom last night using that. Did I screw up?
Ok....I finally managed to get the files onto my SD card. I attempted to install the Slim rom (the one that's been on my phone the last couple weeks) and heres the message I get:
Format and Mount System, Mount Data.....
Symlinks and permissions....
set_metadata-recursive: some changes failed
E:Error executing updater binary in zip ' /extern
Error flashing zip '/external_sd/Slim-d2lte-4.4.
Updating partition details....
FAILED

What version of TWRP are you using? You could try flashing CWM or Philz recoveries and try the rom again. If you still get flashing errors you may have to find a way to get Odin to work.
Try uninstalling drivers from device manager. Then with the phone unplugged, reinstall the driver package. Plug phone back in and hopefully itll automatically install the drivers and work.
And have you tried connecting while booted to Download Mode?

DocHoliday77 said:
What version of TWRP are you using? You could try flashing CWM or Philz recoveries and try the rom again. If you still get flashing errors you may have to find a way to get Odin to work.
Try uninstalling drivers from device manager. Then with the phone unplugged, reinstall the driver package. Plug phone back in and hopefully itll automatically install the drivers and work.
And have you tried connecting while booted to Download Mode?
Click to expand...
Click to collapse
I'm using TWRP 2.6.3.0. Ok friggin awesome...I rebooted it into download mode and the computer recognizes my phone.

You might need an updated recovery to flash that rom. Latest TWRP is 2.7.1.0.
But since you can connect in Download Mode you can flash your firmware via Odin...hopefully.
If you have the I747, it depends on if you have ever updated via ota. If so, do you remember if you had updated to 4.3 or 4.4.2?

DocHoliday77 said:
You might need an updated recovery to flash that rom. Latest TWRP is 2.7.1.0.
But since you can connect in Download Mode you can flash your firmware via Odin...hopefully.
If you have the I747, it depends on if you have ever updated via ota. If so, do you remember if you had updated to 4.3 or 4.4.2?
Click to expand...
Click to collapse
I have the i747. I've never been able to do an OTA update, I heard because it was rooted. When I tried to unroot it, I still wasn't able to do an OTA update. I'm going to try to update the recovery first and then the rom. Which rom do you use? The main reason I don't like SlimKat is because of the Google search bar on the home screen and all the extra crap on the lockscreen I couldn't get rid of.
Update: I flashed the latest TWRP and it still bootlooped. So I flashed CWM instead and it booted right back into CWM recovery.

I have a T999 and I only use Touchwiz roms. Personal preference.
When you are in Download Mode, if you do not see a Warranty Bit, youll be free to flash any firmware you want with Odin. You can download it at http://sammobile.com/firmwares

DocHoliday77 said:
I have a T999 and I only use Touchwiz roms. Personal preference.
When you are in Download Mode, if you do not see a Warranty Bit, youll be free to flash any firmware you want with Odin. You can download it at http://sammobile.com/firmwares
Click to expand...
Click to collapse
Doc, Thank you so much for helping me. I flashed the slimkat rom in cwm recovery and its fine now. However I don't want Slimkat and I was eyeing Touchwiz. Someone was saying how great a rom it is so I'm going to try that shortly. No more TWRP for me. I'm comfortable with CWM. Thanks again. :victory:

Bricked Nexus 7 while installing Lollipop - fastboot kinda works

Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.

Just restart device to bootloader, unpack official Lollipop image and run flash-all.bat within directory with fastboot.
It's very difficult to hard brick..

kuba9519 said:
Fastboot works, but adb doesn't see my device now.
Click to expand...
Click to collapse
FWIW adb only works when booted into Android. Fastboot only works in the bootloader.

kuba9519 said:
Hello.
So I tried to install Lollipop on my Nexus 7 2013 WiFi. I used their official instructions developers.google.com/android/nexus/images . Before that I made a backup in recovery (if something went wrong) and wiped data. So I did all that and tried to install Lollipop using their instructions, but now after turning the device on I see Google logo and that's all. Also recovery doesn't work. It just shows dead android. Fastboot works, but adb doesn't see my device now.
Before this I had Clean Rom installed.
EDIT: I can see it using fastboot, but it f'd recovery.
EDIT2: I used flash-all second time and now it works, God, for a moment I thought I lost my baby.
Click to expand...
Click to collapse
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now

Nexus still in mortal peril
GalaxySN00B:0 said:
Just download wuzwigs Rom toolkit and revert back to kitkat and start over. Ive had moments where i could barely get fastboot to work because my freaking power went. Just run through that and follow the appropriate steps and try again... Or just wait for the official update next time. It cant be more than a few days away now
Click to expand...
Click to collapse
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?

This shows how to get to recovery mode from the dead Android screen http://www.robschmuecker.com/how-to-boot-into-recovery-mode-nexus-7/
Sent from my XT1080 using XDA Free mobile app

atrielienz said:
My problem is I tried to unroot in order to flash the update to lollipop and now unfortunately I seem to have actually hard bricked the device. I can boot into the bootloader. My device is still ulocked. However when I try to access recovery I get the dead android icon. I tried reinstalling adb. It didn't take. I can't get device to show up in the command line. I tried reinstalling drivers and that's where I'm stuck. I can't seem to make this work. Even if I can just go back to 4.4.4 I'll be happy. What are my other options that don't involve sending it in for repair?
Click to expand...
Click to collapse
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!

DMF1977 said:
I accidentally wiped my internal storage and my operating system this weekend! Mskips toolkit is the only one i could find that would install the drivers properly and then flash a factory 5.0.1 image... Everything works great now!!
Click to expand...
Click to collapse
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.

Use wugs but make sure you tick tablet is in bootloop, worked for me.

atrielienz said:
The problem is that I can't boot up. Which means I can't put the device in ADB mode. Which means I can't use the skipsoft tool kit.
Click to expand...
Click to collapse
U can't boot in to android, but u did state earlier that u can boot to the bootloader, and that it was unlocked, so its definitely not hard bricked!