Ok, I know I am a noob to android phones and to this forum, but I already spent many hours online researching the problem and didn't find anything that helped.
So, here's what happened:
I got my MyTouch 4G about 2 weeks ago unlocked. I wanted to get rid of a lot of the garbage that came with it, so I followed the steps and successfully rooted it and then removed several of the preinstalled apps with Titanium backup. So far, no noticeable problems.
Then I wasn't happy with how quickly my battery was draining, so I installed Advanced Task Killer, and set it to automatically kill certain apps periodically.
A few days later when I was trying to add a widget to the desktop, I got the familiar to some message "Sorry, com.htc.launcher has stopped working". Everything else was still working fine on the phone. I researched the problem and the first proposed solution to clear the data for the process from Settings/Applications, did not help. The second proposed solution was to do a factory reset. So, I rebooted with volume down + power pressed together and chose factory reset.
After 4-5 min, I got into the welcome screen where I did the initial setup. After this was complete, the phone checked off that everything was setup correctly (apps, widgets, etc). Then it started loading the desktop and the message "loading..." appeared. This is where it froze.
Basically, I can't get past the "loading..." message on the home screen, no desktop ever loads, and I have access to nothing other than the camera key.
I let it stay for hours to see if it will eventuall load, but nothing happened. I also rebooted and tried factory reset many times and it always get stuck at the same point. I tried all of the above with and without a SIM card, with and without a memory card - basically I exhausted all possible combinations but I always get the same frozen "loading..." screen.
Has anyone experienced this problem? I feel helpless rebooting or reseting the phone from the phone itself because it always get stuck. Is there a way to factory reset from a computer?
Thank you so much if you can help me with any advice and Happy New Year!
Vess
Sounds like u deleted something dealing with the launcher. Doing factory reset well not put it back. I would say, do a nandroid backup, flash iced glacier rom. U could just download another launcher, but being that u wiped the phone, u can't even get to market in that state.
esincho said:
Sounds like u deleted something dealing with the launcher. Doing factory reset well not put it back. I would say, do a nandroid backup, flash iced glacier rom. U could just download another launcher, but being that u wiped the phone, u can't even get to market in that state.
Click to expand...
Click to collapse
Hi, thank you for your message. I think you are correct about deleting the launcher and factory reset not fixing it.
But I don't know how to do "nandroid backup, flash iced glacier rom". Could you point me to instructions on that? Sorry, I'm really new to android phones.
I'm on my phone, go to the development section for this rom. You're see iced glacier. Instructions on the first post
esincho said:
I'm on my phone, go to the development section for this rom. You're see iced glacier. Instructions on the first post
Click to expand...
Click to collapse
I did what you suggested but from what I understand to flash a rom I need to be able to boot into Recovery mode, which I can't do either. Every time I choose Recovery I get the "!" screen and I'm stuck. Am I doing something wrong?
Thank you.
vess22 said:
so I followed the steps and successfully rooted it
Click to expand...
Click to collapse
You didn't by any chance install Clockwork ROM Manager, flash ClockworkMod Recovery and then make a Nandroid backup before doing all of this, did you?
shlongwoodian said:
You didn't by any chance install Clockwork ROM Manager, flash ClockworkMod Recovery and then make a Nandroid backup before doing all of this, did you?
Click to expand...
Click to collapse
No sir, I didn't do any of the above unfortunately. From what I understand had I done that, I wouldn't have a problem booting into Recovery mode, correct?
I believe you might still be able to get to what you need via adb. That's not my specialty though, even though I can mash out a few commands and comprehend what I'm doing. It would be remiss of me to guide you any further, but I don't think all hope is lost for you. Search the forums for 'adb' and 'recovery' and let's also see who replies back with some better advice.
Find the raw .img of cw recovery then adb flash_recovery /location/of/recovery.img
If that doesn't work you'll need to use fastboot assuming you updated to eng spl.
Sent from my HTC Glacier using XDA App
sounds like your boot.img is borked.... try flashing one of the many available kernels (make sure it will work with your rom first... if you haven't flashed a rom or flashed a sense based rom then use an HTC kernel if you're running CM or MIUI use a CM based kernel) and then when you get it running read this and understand why task killers are bad FAQ: You shouldn't be using a task killer with Android
Yes, I'm starting to realize that now my only option is to do flash recovery through adb. So, I've spent all night last night trying to understand what adb is. I installed and updated the sdk, but my adb shell doesn't see my phone as a listed device, so I'm stuck at this point. And yes, I read probably 5 tutorials on installing various usb drivers/ modifying sdk ini files/etc to make your computer recognize the phone as an adb device. I tried everything that was suggested but no luck so far.
I've spent nearly 30 hours so far since this whole disaster started and although I haven't made much progress, I've learned quite a few things.
And, no, I won't mess with Advanced Task Killer or Titanium Backup any more, just give me my phone back and working
Are you s=off with eng boot loader, I don't think you will be able to get a stable adb connection with the ROM acting all wonky.
Best bet is fastboot flash recovery
Sent from my HTC Glacier using XDA App
ESKIMOn00b said:
Are you s=off with eng boot loader, I don't think you will be able to get a stable adb connection with the ROM acting all wonky.
Best bet is fastboot flash recovery
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yes, s=off with eng boot loader. However, I never did a custom ROM flash, so I cannot go to recovery mode from the phone. I thought even for fastboot flash recovery I need an adb connection, no? How else can I do that?
Thanks.
vess22 said:
Yes, s=off with eng boot loader. However, I never did a custom ROM flash, so I cannot go to recovery mode from the phone. I thought even for fastboot flash recovery I need an adb connection, no? How else can I do that?
Thanks.
Click to expand...
Click to collapse
Boot into fastboot and then you should have access to adb. You can then use fastboot to flash clockwork recovery.
There is a STOCK NANDROID RESTORE somewhere in the development section here. Use clockwork recovery to restore that nandroid, boot up and go on your merry way.
EDIT:
download clockwork recovery and save it to c:\android-sdk-windows\tools (or maybe platform-tools, depending on where the fastboot.exe file is located)
CLOCKWORK RECOVERY LINK
power off phone
hold vol down + power
select FASTBOOT
connect phone to computer - let windows do it's hardware detecting/installing thing
open a command prompt and navigate to your sdk tools folder
type this, without quotes "fastboot flash recovery recovery.img"
disconnect phone and power off/reboot/etc
You should now have access to clockwork recovery and be able to flash whatever you want
Phateless said:
Boot into fastboot and then you should have access to adb. You can then use fastboot to flash clockwork recovery.
There is a STOCK NANDROID RESTORE somewhere in the development section here. Use clockwork recovery to restore that nandroid, boot up and go on your merry way.
EDIT:
download clockwork recovery and save it to c:\android-sdk-windows\tools (or maybe platform-tools, depending on where the fastboot.exe file is located)
CLOCKWORK RECOVERY LINK
power off phone
hold vol down + power
select FASTBOOT
connect phone to computer - let windows do it's hardware detecting/installing thing
open a command prompt and navigate to your sdk tools folder
type this, without quotes "fastboot flash recovery recovery.img"
disconnect phone and power off/reboot/etc
You should now have access to clockwork recovery and be able to flash whatever you want
Click to expand...
Click to collapse
Thank you, thank you! You saved my life. Finally a solution that worked for me. God bless you
BTW, I was never able to get adb detect my phone but fastboot did! So, I followed the steps you suggested and it worked. So relieved now
Vess
vess22 said:
Thank you, thank you! You saved my life. Finally a solution that worked for me. God bless you
BTW, I was never able to get adb detect my phone but fastboot did! So, I followed the steps you suggested and it worked. So relieved now
Vess
Click to expand...
Click to collapse
lol, glad I could help! ADB should be working in Clockwork Recovery now, btw.
You should have seen how I freaked out the first time I tried to root my mt3g. I forgot to wipe and it kept freezing on boot, lol.
So what are you gonna do now? Load a custom rom or stay with stock?
Phateless said:
lol, glad I could help! ADB should be working in Clockwork Recovery now, btw.
You should have seen how I freaked out the first time I tried to root my mt3g. I forgot to wipe and it kept freezing on boot, lol.
So what are you gonna do now? Load a custom rom or stay with stock?
Click to expand...
Click to collapse
I just loaded ice glacier 1.1.4 unthemed. To be honest I don't see much difference except that the bloatware is gone, so I'm happy with it. I don't know if it makes sense to go back to stock. My phone is not under warranty. Is there another reason one might want stock?
vess22 said:
I just loaded ice glacier 1.1.4 unthemed. To be honest I don't see much difference except that the bloatware is gone, so I'm happy with it. I don't know if it makes sense to go back to stock. My phone is not under warranty. Is there another reason one might want stock?
Click to expand...
Click to collapse
You make an appealing case for Iced Glacier.
Stock tends to be the most stable and reliable, plus you get OTA updates. Other than that, not much reason. I can tell you from recent experience that my phone gets a gps lock much quicker with stock than with cm6, but I'll do further testing to see if that's really the case.
I'm having a similar problem and I'm following these steps, but not having any luck.
Info on my phone: It's a MT4G that I got just this past week from eBay, worked fine up until this morning. Does not have an SD card and the one I have from my previous phone (Vibrant) is a highly suspect piece of junk so it's not in the phone right now. I was running VISIONary+ on it and had just set it to temp root on boot, but never got it to reboot. I plugged it in to charge this morning, thought it was plugged all the way in (maybe it wasn't? Would that cause this kind of borking?) and the phone froze. Rebooting didn't help. Actually I had pulled the battery, rebooted it, stuffed it in my pocket and then 2 hours later realized it was still on the boot up screen. That's when I got scared. It's running ADW, Superpower, TIBackup and Tasker, but there's no other software I can think of on the phone that might have mattered. Never installed Clockwork or anything like that before, regretting that now.
On the hboot screen I have:
GLACIER PVT SHIP S-ON
HBOOT 0.86.0000
MICROP-0429
RADIO 26.03.02.26_M
eMMC-boot
Sep 27 2010, 11:12:59
Click to expand...
Click to collapse
Going to Fastboot, I can get the phone to be recognized as an HTC Bootloader in my device manager, and I can try and get the recovery.img loaded as was instructed above using adb but it always fails. Output from that is:
sending 'recovery' (8701 KB)... OKAY [471.891s]
writing 'recover'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 473.125s
Click to expand...
Click to collapse
When I try and do recovery, I get a quick flash of a phone with a red exclamation point over it, then black screen of nothing. Booting regular leads to a constant white MyTouch4g screen, no change. Trying Factor Reset leads to the skateboarding androids, no change even after a long time. In any of these cases, I have to pull the battery before I can try anything again.
Did I bork my phone? How the heck did I do that? Is there any way to further save it? Any help you guys could give me would be massively appreciated, thanks in advance.
RedDonkey said:
I'm having a similar problem and I'm following these steps, but not having any luck.
Info on my phone: It's a MT4G that I got just this past week from eBay, worked fine up until this morning. Does not have an SD card and the one I have from my previous phone (Vibrant) is a highly suspect piece of junk so it's not in the phone right now. I was running VISIONary+ on it and had just set it to temp root on boot, but never got it to reboot. I plugged it in to charge this morning, thought it was plugged all the way in (maybe it wasn't? Would that cause this kind of borking?) and the phone froze. Rebooting didn't help. Actually I had pulled the battery, rebooted it, stuffed it in my pocket and then 2 hours later realized it was still on the boot up screen. That's when I got scared. It's running ADW, Superpower, TIBackup and Tasker, but there's no other software I can think of on the phone that might have mattered. Never installed Clockwork or anything like that before, regretting that now.
On the hboot screen I have:
Going to Fastboot, I can get the phone to be recognized as an HTC Bootloader in my device manager, and I can try and get the recovery.img loaded as was instructed above using adb but it always fails. Output from that is:
When I try and do recovery, I get a quick flash of a phone with a red exclamation point over it, then black screen of nothing. Booting regular leads to a constant white MyTouch4g screen, no change. Trying Factor Reset leads to the skateboarding androids, no change even after a long time. In any of these cases, I have to pull the battery before I can try anything again.
Did I bork my phone? How the heck did I do that? Is there any way to further save it? Any help you guys could give me would be massively appreciated, thanks in advance.
Click to expand...
Click to collapse
The instructions above only pertain to a rooted phone. Your phone is not rooted and you dont have eng bootloader. Without superuser access you cant even flash recovery like you were trying. A factory reset didnt fix your problem?
Side note, im an opponent of doing the whole temp rooting only thing cause if you screw something up you dont have access to tools to fix anything, your just screwed if something happens like this.
Ok, so before I get flamed, let me say that I did do a search and did see that there are ways to unroot the phone...however, I have what I believe to be a bit of a different case here and am just looking for info before trying any of them.
Background...(this is for a friends phone, not mine, or I would just Odin and call it good. He however does not want to loose any of his settings blah blah blah so doesnt want to go that route unless necessary)...Buddy got his first Epic and had me root it for him (One Click Root 2.5.1), that phone took a **** and had to be replaced. When he took it to Bestbuy (I think there, could be the sprint store, dont know that it matters) they hooked it up to their little file transfer machine, let it do its thing and gave him his new phone. Now, after doing that, it still shows as having Clockwork Mod installed, and you can boot into CWM, but none of the functions work, which I found out when I tried to install EC05 on his phone. I installed the zip to his sd card, rebooted into CWM and selected to install zip from sd...nothing happened...just went to a blank screen and locked up and I had to pull the battery. Rebooted the phone and it went straight to CWM without the three finger grip, I selected to just reboot the phone, lock up and battery pull required. Long story short (I know, too late for that) I tried several options and all of them resulted in a lock up and wouldn't let the phone boot normally...I was really feeling bad thinking that I had actually managed to brick his phone...last thing I tried was the advanced menu and selected to reboot recovery and luckily, that actually worked and booted me into sammys stock recovery mode and I was able to run the zip. Had to reboot several times, but it took and his phone is running well now on EC05.
So now to my question. Since CWM is obviously corrupted on his phone from that transfer and not being properly installed on this phone (I was actually blown away that it transfered in the first place) in order to correct that, do I just apply the newer CWM like its a stock phone and let it try to write over those corrupted/missing files or do I need to try to uninstall what is there first or is he going to be stuck having to Odin and take whatever losses he gets?
Thats actuarry an interesting diremma...
Does the phone show up in adb? Can you SU
Sent from my SPH-D700 using XDA Premium App
If you are rooted still, run MyBackup Root for him and then run Odin. If you're not, run the One Click Root 2.5.5 and then use MyBackup Root.
No, its not still rooted, just showing CWM. Thanks, I will try running 2.5.5 over it. I just wasnt sure if that would cause any problems...will let you know how it goes.
I've had a similar thing happen to me when updating a kernel. Reinstalling the same CWM right over the top worked for me.
My N7 is rooted and stock... I used the N7 Toolkit method... My N7 is 32gb non-3G version...
It's been working fine, no problems. I thought that it was a little laggy since I installed a 2nd account on it ... so a day ago I deleted the 2nd account hoping to get rid of the lagginess that started after installing the 2nd account.
Today I came home with the N7 and I heard some notifications when it logged into my Wifi... And about 30 mins later I went to use it and the wall paper that is usually showing went black, the screen did some funny things and the tablet reset.
Now it's stuck in a boot loop...
I can get into the bootloader and recovery, but whenever I exit, it goes back into the boot loop.
Since I hadn't installed anything custom when rooting, do I even have Nandroid? Can I back it up and connect to USB before wiping?
Does wiping erase the SD portion of the memory?
Any ideas for troubleshooting? Would love to know what happened here...
Thanks...
What did you come up with by searching the forums or Google?
Hemidroids said:
What did you come up with by searching the forums or Google?
Click to expand...
Click to collapse
As with many things, the info that I found is conflicting. Since I had been burned by trying things before verifying what I was doing, for once, I decided to reach out for advice BEFORE I erased something that isn't recoverable.
Yes, I know that many on XDA hate users who ask for help before researching on their own. The problem for me is that I couldn't find a clear answer.
Since I made my post, I tried a few things...
Details and questions are here: http://forum.xda-developers.com/showthread.php?t=2089144
Thanks for your response, although I get the feeling that you had expected me to know the answer to my question...
OldDogEyes said:
My N7 is rooted and stock... I used the N7 Toolkit method... My N7 is 32gb non-3G version...
It's been working fine, no problems. I thought that it was a little laggy since I installed a 2nd account on it ... so a day ago I deleted the 2nd account hoping to get rid of the lagginess that started after installing the 2nd account.
Today I came home with the N7 and I heard some notifications when it logged into my Wifi... And about 30 mins later I went to use it and the wall paper that is usually showing went black, the screen did some funny things and the tablet reset.
Now it's stuck in a boot loop...
I can get into the bootloader and recovery, but whenever I exit, it goes back into the boot loop.
Since I hadn't installed anything custom when rooting, do I even have Nandroid? Can I back it up and connect to USB before wiping?
Does wiping erase the SD portion of the memory?
Any ideas for troubleshooting? Would love to know what happened here...
Thanks...
Click to expand...
Click to collapse
First if you have a custom recovery, boot into that, wipe cache, then dalvik, and try rebooting. See if that works.
Nandroid would be the backup of your entire ROM that you made either using ROM Manager or manually initiating a backup in recovery.
Wiping using ClockworkMod Recovery or TWRP Recovery will leave the /sdcard area (/data/media) alone, however it'll remove your ROM. At that point, you'll need to re-flash a custom ROM to your device. If you reload the stock N7 images from Google, it WILL erase your /sdcard section!
You can push files to your device while in recovery using the adb push command. You can also pull files from your device using the adb pull command.
adb push <name of file> <location on device you want to push to>
EXAMPLE: adb push ROM.zip /sdcard/
adb pull <location of file on device>
EXAMPLE: adb pull /sdcard/ROM.zip
Research adb, adb push, adb pull commands.
Hi, It may not be completely bricked but as far as I am concerned it is. I tried to free up some space on the phone by formatting everything in ClockworkMod. Factory resets did nothing and the phone showed I had used over 10 GB. I figured formating was just going to clear out all the backups and old files.
As of now I can get into recovery but that's about it. When I try to reboot all it does is bring up the words GOOGLE. My PC wont recognize it as I cant enable USB debugging. I thought if I could just drag a new rom, gapps, zip file into the internal storage I would be good. I also thought I might be able to restore it to stock with a toolkit but again they request USB debugging on.
I am real new to this so any help would be greatly appreciated. Is there a way to bring this phone back to life in some sort of straight forward way?
PS. As of this morning things seem to have gotten worse. I used a toolkit to try and get things working and now I cant boot into recovery. All I get is the robot on its back with red triangle icon. I can press power, then volume up and get another menu but I am really at a loss. Any further help would be great. Thanks.
Thanks
You're definitely not bricked.
You must restore the factory image, which you can find from Google... Google "nexus factory image" and restore in bootloader mode.
I'm not going to go into detail on how to restore, there are dozens of threads on how to do that. Start by Googling "how to flash nexus factory images"...
I'm assuming that since you've dabbled with modifying your Nexus that you are familiar with the super duper important ADB/Fastboot procedures? If not, you've got a lot to learn before you start messing with your phone...
Edit: You can also attempt to ADB push a stock rooted ROM (only so you don't have to mess with gapps at the moment) through your custom recovery. Again though, do your due diligence and read before messing with this sort of thing.
Sent from my Nexus 4 using xda premium
Just sideload a rom with adb.
adb push a ROM into your memory via cmd prompt. I think you can adb push data using the Nexus 4 toolkit in the stickies.
When you figure out how to push files into your phone, flash the new ROM.
Alternatively, use efrant's guide from my signature. The only correct & educative way of returning to stock. Avoid toolkits!
Hello.
I just rooted my phone for the first time with Motochopper and flashed the Google Wallet Mod. Everything was working fine until after a while I tried turning my screen on and it wouldn't turn on. I rebooted the phone and the Samsung Logo with the Custom Lock logo appears for a short while, then the screen goes black. After about 20 seconds the blue LED stays constantly lit and slowly fads in and out - after a few minutes the device becomes really hot. The screen stays black and I can't do anything. Is there any way to get my phone back to normal without deleting everything off my phone and restoring the stock ROM?
I have a US AT&T Samsung Galaxy S4 16GB (SGH-I337).
Any help is appreciated,
Thank you.
-Problem fixed.
You have any backups? try restoring one and see if you get the same result. If not, odin back to stock would be your only option.
TheAxman said:
You have any backups? try restoring one and see if you get the same result. If not, odin back to stock would be your only option.
Click to expand...
Click to collapse
Unfortunately I don't have any backups. This is my first Android phone, coming from an iPhone, and I'm still getting used to rooting as opposed to jailbreaking. I installed TWRP before I flashed the Google Wallet mod but thought I would be fine until I get an external micro SD card to create the backup on. Is there any way I can access and transfer my photos that are on the device either via Recovery Mode or Download Mode to my computer before I loose everything restoring back to stock?
If you just rebooted thru power menu, try pulling battery--
Did you try manually booting into recovery--
rugmankc said:
If you just rebooted thru power menu, try pulling battery--
Did you try manually booting into recovery--
Click to expand...
Click to collapse
The first time I rebooted, I used some combination of the power and home button because when I tried to turn it on the screen was black. Something must have happened while the device was idle because everything was fine but when I turned it on it wouldn't come on so I rebooted. When it boots, the screen stays black with the blue LED and if I try to reboot, the same thing happens - it's stuck in a loop and the only way to turn it off is to pull the battery out. I can manually boot into recovery, but I have no backups. I've tried doing a Factory Reset in the TWRP, but no dice.
Wow--lesson learned hard way--ALWAYS have backup on phone and pc, including a copy of your sdcard--
That should be at top of every phone forum stickies--
I am not expert on Samsung yet. But, on my HTC phone we would have downloaded a rom to the pc and thru adb pushed it to phone then wiped and flashed it.
It is easy, but you will need to get adb files on your pc or download and install Android ADK. I think if someone has them for this phone you can copy them to pc and put in adb folder and bypass SDK. They are in some of the exploits like motochopper. Matter of fact you could probably extract motochopper and put in your download folder or to desktop and run adb from there. It has all the commands.
Some one else more expert on phone can confirm that and give exact push command to get rom to phone. I can Google it, just haven't used those commands for awhile,
It will be something like putting motochopper extracted folder onto pc. Opening a terminal window and cd'ing to where ever you put it
Then typing adb push rom.zip /sdcard rom.zip
Of course you need to rename rom to "rom.zip" or use the exact name of the rom you put on pc.
That command will have rom.zip on root of sdcard
I pretty much had this happen to my phone -
http://forum.xda-developers.com/showthread.php?t=2331112
Sent from my SGH-I777 using xda premium
---------- Post added at 11:17 PM ---------- Previous post was at 11:15 PM ----------
Bilateral Pneumothorax said:
Unfortunately I don't have any backups. This is my first Android phone, coming from an iPhone, and I'm still getting used to rooting as opposed to jailbreaking. I installed TWRP before I flashed the Google Wallet mod but thought I would be fine until I get an external micro SD card to create the backup on. Is there any way I can access and transfer my photos that are on the device either via Recovery Mode or Download Mode to my computer before I loose everything restoring back to stock?
Click to expand...
Click to collapse
Connect the phone to PC, then you can access the internal folders
Sent from my SGH-I777 using xda premium
Bilateral Pneumothorax said:
Unfortunately I don't have any backups. This is my first Android phone, coming from an iPhone, and I'm still getting used to rooting as opposed to jailbreaking. I installed TWRP before I flashed the Google Wallet mod but thought I would be fine until I get an external micro SD card to create the backup on. Is there any way I can access and transfer my photos that are on the device either via Recovery Mode or Download Mode to my computer before I loose everything restoring back to stock?
Click to expand...
Click to collapse
I am on an iMac and use Android File Transfer. Not sure how they do it on PC as I thought we still can't mount sdcard in Recovery. Maybe Kies if it works for you. But, if you can only get to recovery and no backup, pushing a rom may be the answer. Come morning you'll get more answers. One thing I noticed coming from TMobile HTC to US ATT, not much overnite posts since we are all within 3 hour time zones. With Tmobile, lots of Europe folks.
rugmankc said:
Wow--lesson learned hard way--ALWAYS have backup on phone and pc, including a copy of your sdcard--
Click to expand...
Click to collapse
Lesson well learned. When I get my phone up and running my first priority after re-rooting will be making a backup.
rugmankc said:
I am on an iMac and use Android File Transfer. Not sure how they do it on PC as I thought we still can't mount sdcard in Recovery. Maybe Kies if it works for you. But, if you can only get to recovery and no backup, pushing a rom may be the answer. Come morning you'll get more answers. One thing I noticed coming from TMobile HTC to US ATT, not much overnite posts since we are all within 3 hour time zones. With Tmobile, lots of Europe folks.
Click to expand...
Click to collapse
I was actually able to mount USB Storage via TWRP and use the ADB command adb pull /sdcard/DCIM/Camera to extract the photos off my phone to my computer. Now it's not so bad if I have to restore to default.
Always always backup FIRST before attempting to do anything, that is lesson one period.
Sent from my SAMSUNG-SGH-I337 using xda premium
Bilateral Pneumothorax said:
Lesson well learned. When I get my phone up and running my first priority after re-rooting will be making a backup.
I was actually able to mount USB Storage via TWRP and use the ADB command adb pull /sdcard/DCIM/Camera to extract the photos off my phone to my computer. Now it's not so bad if I have to restore to default.
Click to expand...
Click to collapse
Great. Since you are up on adb you can easily push a rom. I will have to try to mount in recovery again. I think android file transfer messes with mounting.
Sent From My 32gb Samsung Galaxy S4 using Tapatalk 2
rugmankc said:
Great. Since you are up on adb you can easily push a rom. I will have to try to mount in recovery again. I think android file transfer messes with mounting.
Click to expand...
Click to collapse
Instead, I used Odin to flash the stock GS4 firmware. Now my phone is working again. Oh and I made a backup this time.
Thank you to all who helped me.
/thread
Super. Having not used Odin and on an imac, not sure that was an option in your case. Glad you got it.
Sent From My 32gb Samsung Galaxy S4 Running Tapatalk 4 Beta