Related
Greetings,
I have two Vibrants - one I bought from TMobile (and running stock everything), and one I later bought on eBay (running Froyo thanks to TeamWhiskey). I bought the second phone so that I could mess around with flashing ROMs and be able to brick a phone without it mattering. Hah.
Last night, for no reason I can discern, my stock TMobile Vibrant phone spontaneously soft bricked itself. My eBay test phone is fine.
I don't hugely care WHY the Tmobile phone bricked itself, but what I do care about are the pictures that are on the internal storage area.
I used Odin last night to flash in T959UVJI6.tar (but I did NOT use the 512.pit file). One of the posts I read said that doing so should fix a soft brick, without messing up the internal user storage area where pictures are located. No change - when I power on the Tmobile phone it hangs at the Galaxy S logo and then goes black.
Does anyone have any suggestions of how to access the internal storage area of a soft bricked Vibrant? And/or, can someone explain or point me at an explanation of what impact using a PIT file (vs not) and checking the "reformat" box in Odin (vs not) will have on the internal storage area? I don't care about overwriting the apps - I am just hoping there is some way to pull off the pictures or unbrick the phone WITHOUT deleting them.
Many thanks!
Wrong section..probably going to get flamed. Odin again with the pit file and you still wont lose pics and stuff. But next time...Q and A section...not being a ****, but that's where you ask all your questions.
sent from the other side of my galaxy.
jmercil said:
Wrong section..probably going to get flamed. Odin again with the pit file and you still wont lose pics and stuff. But next time...Q and A section...not being a ****, but that's where you ask all your questions.
sent from the other side of my galaxy.
Click to expand...
Click to collapse
Thanks for the reply. Is there some way I can move my post to the Q&A section? Or is that something only a Mod can do?
Also, do I check the reformat box or leave it unchecked?
Thanks again.
noise said:
Thanks for the reply. Is there some way I can move my post to the Q&A section? Or is that something only a Mod can do?
Also, do I check the reformat box or leave it unchecked?
Thanks again.
Click to expand...
Click to collapse
No need to reformat.
That's only for special occasions, really. And yeah, as far as I've seen, only mods can move posts.
yeah i would also like to know to that. the other day i deleted the 3d gallery app apk odex files because it was annoying the hell out of me with it's referenced folders - i tried clearing the default folder and but it was still showing random pictures from the shutdown folder and where ever else - so what did i do? i backed up the apk and odex file then deleted them from the system folder. rebooted w/o any issues - then i tried installing the apk... nothing - kept giving me a failed app install notification. i tried this 3-4 times then gave up. at this point i restored the apk/odex file to the system folder and rebooted the phone - nothing... gets past the galaxy s animation screen then screen goes black... nothing....
tried multiple reboot and keeps getting to the same black screen of doom - the other odd thing is windows do recognize it after it gets past the galaxy s boot screen and into the blank screen when i check in the device manager
ADB pull /sdcard/"whatever u have on ur phone"
Learn ADB
Reading is Fundemental
I'd also like to know if there are anyways to access the internal memory of a soft bricked phone. I know I can use ODIN, but I could fix the problem right now sans computer or USB if Clockwork recovery could access my sd card; I flashed a new kernal on stock JI6 and apparently needed to to flash a backsupport.zip first.
So, I don't have a cable with me, so can't use ODIN, clockwork recovery doesn't restore kernals and doesn't access the SD so... I'm screwed until I get home (not a huge deal). Alternatively, I could also not get clockwork to USB mount so I don't think that works either.
boimarc89 said:
ADB pull /sdcard/"whatever u have on ur phone"
Learn ADB
Reading is Fundemental
Click to expand...
Click to collapse
lol thanks man. but i also tried that. adb can't recognize it - and i found out it's the hard lock t-mobile version where doing the three button power up does not get you into the recover screen. unless i read that wrong? lol
Update: I used Odin again, this time with both the TAR and the PIT file. Same result as last time. Odin appears to have completed copying everything over successfully, but upon reboot, I still get the soft-brick Galaxy S that doesn't go away.
I didn't try ADB earlier because all the posts/various docs I read thus far seemed to imply that ADB needed a normally functioning phone - not one that got stuck at the Galaxy S logo. I was wrong.
Here's what I did, hope it helps someone else. [Commands below assume you're using windows, and want to copy the entire contents of the internal SD memory (called "/sdcard") on your PC that you created (e.g., "c:\sdcard"]
1. Install ADB
2. Plug in soft-bricked phone and power on
3. Run command prompt and navigate to the directory where adb.exe is located. In my case, it was C:\Program Files (x86)\Android\android-sdk-windows\platform-tools.
4. From the command prompt:
adb pull /sdcard c:/sdcard
NOTE: the c:/ slash should be as shown - not c:\ as you would normally type under Windows.
392 seconds later, I had all 8G of photos on my PC.
I still don't know why the stupid phone won't boot properly, but now I don't care and can blast everything away. Thanks to everyone who contributed. Next time I'll be sure to post in Q&A instead.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
Today I tried to flash the CyanogenMod 9 Nightly 06-30-12, coming from Build 35 of AOKP and after factory resetting and clearing Dalvik I went to install the zip and while flashing it I got a build-prop related error!
All of my NANDROIDS gave me a data error when flashing and now I am pretty f'd! I /really/ need to fix this ASAP but have no idea how.
-Samsung Galaxy Tab 10.1 Wifi-
-CWM 4-
On a second note, does anywhere know where I can get my screen replaced for cheap? I dropped my tab a few months back and the screen got MAJOR cracked, though it still does technically work (I still use the screen, it works but it's cracked is all...) and after calling Samsung and waiting for over 1 and a half hours they told me they wanted $150 to fix it, which if I recall is about half of what I payed for it anyway...
To be honest, I'd be lying if I said I was happy with Samsung over all.
I mean, bad customer support, the proprietary connection cable, and lack of official updates (along with the ugly TouchWiz that I'm not sure /who/ likes ) don't make me that happy...
Anyway, can anyone help me please?
Thanks in advance!
Update your recovery: http://droidbasement.com/db-blog/?p=2655
If you have a GT-P7510 (p4wifi), in this post are flashable zips (with your current recovery) of CWM and TWRP, in case you prefer this method: http://forum.xda-developers.com/showpost.php?p=28051448&postcount=29
After that, flash your ROM like always.
Yeah, thanks, were it so easy. I fired up ODIN multiple times, no matter what, unsuccessful. Like always, my computer would not recognize my tablet. Yes, I have the bloody Samsung drivers, yes I've tried reinstalling them (several times in the last few months), yes I've tried using different USB ports! And what? Nothing. Nothing at all. For the last few months I have not been able to transfer movies/music to my tablet via file transfer and I can't even get the stupid odin download thing to work. To be honest, I really am pissed off with this broken pile of trash. Would trade it in for a similar tablet any time.
Did you try any of the flashable zips for a new recovery?
About the USB, it sounds like a different problem, but for the file transfers, are you sure you have MTP selected? (answer #5 --> http://forum.xda-developers.com/showthread.php?t=1642009 )
If you haven't tried it yet, you could use a different computer, another OS (some Linux distro and check that adb works), change the USB cable.
I can't use a flashable zip since I can't copy files onto the tablet >.>
Also, yes, for file transfers I /do/ have MTP selected always and it doesn't work eitherway.
Essentially, I am stuck with a $300+ ugly and broken thing that I can only use as a paperweight for the huge mess I call my desk. Yay.
>Rage sidenote; Samsung, go take the money I payed for **** and shove it.
And I guess you don't have your old ROM (AOKP build 35) in your tab.
Try with adb (in recovery), but if you can't get a working USB connection (using other computers or OS), maybe there's something physically wrong with your tablet.
No, I don't. I'm stupid enough to delete the ROM zip after flashing it to save space on the tablet...
How do I do this ADB thing? I've heard of it before alot but never used it or looked into it...
Read this: for windows -> http://forum.xda-developers.com/showthread.php?t=1387527 , for Ubuntu -> http://forum.xda-developers.com/showthread.php?t=921169
After everything is installed, boot your tablet into recovery and try running in your command line application (CMD for windows):
adb devices
If it shows that a device (and ID number and the actual state, e.g. recovery) is connected, your golden!
If you have another android device, try it too, to be sure that is working.
To transfer a file the command is
adb push /path/to/file /path/in/tablet
In windows I guess is something like this:
adb push C:\path\to\file /path/in/tablet
so I'd do something like
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip mnt/sdcard/ ?
Im dling the ADB files right now
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip /mnt/sdcard/
You need the slash at the star and end of the path of the tablet.
While installing PdaNet it failed, said it couldnt connect through to the device or w/e
Also,I don't recall having ADB on when I had the tablet. I might've but I don't think I kept debugging on for the general time...
This is so frustrating >.>
I'm not sure about that error in PdaNet, I can help you with adb but I don't use Windows, so there's things I can't test.
If you didn't select ADB debugging in your ROM it doesn't matter, you're doing this from recovery.
BTW, do you have other android device?
adb seems to be working and copying, but I can't find the file in Recovery while doing choose a zip to apply!
Yes, I have an LG Optimus V on Virgin Mobile running tdm's AMAZING Quattrimus Alpha 10 on Ice Cream Sandwich/ Android 4.0.4
this is what I get
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb push C:\CWM-5.5.0.4-p4wifi.zip
43C800340009517\sdcard\download
1328 KB/s (4147569 bytes in 3.048s)
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>
If you connect your phone and execute
adb devices
What's the output?
If you do the same with your tablet, what's the output?
with the tablet it's
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
with my phone it doesn't wanna show up in Recovery or not.... Hmm.
Well, it shows fine, then you should be able to transfer the files
First, in your recovery, go through the steps to install some zip file, but just go as far as selecting the directory, then go back
Now in your PC try running something like this, change your path in windows:
adb push C:\CWM-5.5.0.4-p4wifi.zip /sdcard/
The in your recovery, select install and should show there. The thing is that most likely the sdcard wasn't mounted in your tab
Edit, to mount your sdcard in recovery do: mounts and storage > mount /sdcard > Go back
The do the transfer in your PC.
Hmm
While I was holding it to my gut, pushing the end of the cable into my stomach (It was the only way to get it to be recognized) I fooled around and went into download mode, hoping that on the contrary I could do that, turn it off, and when I went back into Recovery it would be there when it finally said the cable WAS connected and then I rushed to open Odin and wrote it through, and it frickin' wrote CWM v5 right on and it worked, I'll be damned!
Maple, I can not thank you enough for helping me with this, I am in great debt.
You're welcome, I'm glad it worked. Knowing how to use adb is really useful. And now you know that something is wrong with your cable.
Or in the connector pins or w/e of the tablet... The cable works fine for charging though....
You are my savior, bro.
Hello there,
I just registered on this forum to hopefully resolve my problem with the Kobo Arc tablet. I apologize if any similar issue regarding this was posted. So basically, my Uncle bought me a Kobo Arc tablet about 2 months ago and I know quite alot of things about it. Due to my stupidity I couldn't play a game I really wanted to and so I edited my build.prop to make my tablet compatible with the game. In build.prop I changed the product model to: "GT-I9100", product brand to: "Samsung" and product manufacture to: "unknown". After this I restarted my device. As I did, the kobo arc logo appeared and then a never ending start-up boot. I restarted my device many times but still couldn't get my device to fully on. I entered recovery mode by holding the up volume and power button together and tried to reset to factory, but my Kobo Arc just still won't go pass the never ending start-up screen. I even tried to connect it to my computer but it doesn't recognize it. I'm assuming it's bricked, is there any possible fix for this? if so I need to know asap.
Someone please help me, it would be so kind, and I'll appreciate it soo much.
Thanks in advance
SmootZ
Please, I'm in urgent need of help. I really want to go on my tablet again..
Any help to get my kobo arc to its original state and working properly again, I would be sooo grateful.
Do you have a nandroid backup? If so, restore it.
Otherwise, do you still have access to your SD card (probably using an adapter and connecting it to your PC)? Try using AROMA FM to edit build.prop to the original values.
If not, I'd suggest installing ADB (GIYF) and using that to edit build.prop.
For the last two solutions, you'll need to use the shell, and use a text editor such as nano, pico or vi (depending on what's available). BTW, how did you edit build.prop?
You can also flash back stock/any ROM. Restoring to factory settings doesn't restore build.prop AFAIK.
EDIT: Just noticed your PC doesn't recognize your phone. That rules out solution #3. Are you sure the required drivers installed on your PC?
Yes, I'm sure. But when I plug my tablet into my PC through my usb cable it makes a noise connoting its connected but it won't appear.
Could you possibly give me instructions on how to do a nandroid back-up or something that will get my device back with the following condition:
-My device not able to be recognized on my computer
EDIT: When I connect my device to my computer it charges, but it won't appear on my computer or anything, if this helps.
It's too late to make a nandroid backup now. Try using AROMA FM.
GermainZ said:
It's too late to make a nandroid backup now. Try using AROMA FM.
Click to expand...
Click to collapse
Could you possible give any instructions, I'm kinda new to this stuff.
SmootZ said:
Could you possible give any instructions, I'm kinda new to this stuff.
Click to expand...
Click to collapse
Click the link I posted.
Read the first few posts in full.
Ask about the specific part you don't understand.
I cannot even access my device apart from putting it in recovery mode since my device gets stuck at the start-up and loops, In addition I don't know how to access my sd card since my computer doesn't recognize my device as I said. Will this be a problem?and can I still do it?How do I access my sd card?
Sorry if this question seems stupid
Is your device still not detected in recovery mode?
To access your SD card directly from your PC you'll need a special reader/adapter.
Nope, it doesn't recognize it even in recovery mode. What is this "special" reader/adapter and where can I get it? Could you provide me a link or something?
Well, I'm out of ideas. Just Google "SD card adapter".
Actually my device does not offer any external memory card slot. Meaning There is no support for MicroSD or SD cards on my Kobo Arc.
What shall I do now?
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
SmootZ said:
Hey Germain or anyone else,
Is there any other possible way I can unbrick my tablet from this? Any solution would be grateful.
Click to expand...
Click to collapse
I'm out of ideas you could try yourself. I'd try triple checking the drivers on your PC and see if you can get ADB to work.
Is sending your tablet to repair an option?
EDIT: Can't you update to the latest update using fastboot?
Hey.
First of all, messing with build.prop without backup wasn't the brightest idea in your life, but crap happens, like Forrest Gump used to say.
What is the exact model of your tablet? Kobo Arc? Kobo Arc 10 HD? Maybe Kobo released an update and you can update it directly by fastboot.
If not try to use Linux as it handles ADB much better than Windows, go to system and edit you build.prop back and wipe cache and dalvik cache. You need to have a working ADB to even think about reversing your changes.
Good luck.
Well thanks for the help.
Can I try taking this adb method without my device giving permissions for USB debugging? Since I haven't enabled this in my developer options as far as I know, in addition I cannot really check since my device is bricked but I'm 100% sure it's NOT enabled. Will this stop me from carrying an ADB method?
Hi guys, I have the Rock Jaw Vi phone which by all sense and purpose seems to be a clone of the HTC One. It's Quad Core with 2 mega pixel camera on the front and 8 mega pixel on the back. The case and all outward appearances are that of the HTC, the phone info screen displays the following ...
Model Number = RJViJGTL32SM
Andoid version 4.2.1
Baseband version = moly.wr8.w1248.md.wg.mp.v6.p8,2013/08/12 15:55
Kernel version 3.4.5 [email protected] #1 Mon Aug 19 16:54:14 CST 2013
Build Number = 0502H026_20130819
I can get into the boot options screen by doing the On/Volume Down press but the menu's are all in Chinese and just seem to go through self diagnostics and tests. I can drag n drop file from Mac OSx but none of the apps I have found so far will communicate with the phone via USB. I am trying to get root so i can do a full back-up and then to try and put HTC Android 4.3 on it.
Do you guys have any idea on how I can achieve this or to get the phone to display it's boot options in English ?
I am pretty much clueless and stuck, any advice, tips, hacks etc would be really appreciated
I did follow a link at one stage on the web that went to SRSroot but their tool was windows only
Hmmm More messing with the phone has revealed power on with volume up depressed gets me to some very small text menu with the options;
Boot Normal
Fastboot
Boot(UART)
Boot UART is all the test screens that I was getting in Chinese but now they are touch screen buttons and labeled in english ao that's good to know.
Using fastboot-mac from HTCRootOne tries to talk to it but comes back with error: could not clear input pipe; result -536854449, is this something that's platform specific, ie it's not a true HTC so the version of fastboot-mac is no good and needing a non specific version ?
Ok that error is generated to the oem get_identifier_token...
If i do a fastboot-mac devices i get the reply "mt6589_phone_720pv2 fastboot" ...
I'm getting there slowly
Done some more digging with the phone attached to the Mac here and checking my systems profile I see that the phone is listed under usb connections as seen in the screen grab, still referring the as a HTC. Getting a new usb cable delivered to see if the phones usb cable provided is for charging only. If anyone here has any other suggestions I would be all ears or eyes as the case might be
Done more grubbing around and have found it to be a HDC One, HTC One clone .... Now to go see if any are rooted on here
Can anyone help me
Well i am pretty much stuck here so if anyone is reading this and wants to offer some help and advice I could do with it
I have looked around on the phone and can't see any bin or system folders even with show hidden i can't find them.
adb wont give me a remote shell, it complains that there is no bin/bash
when i try and do an adb backup i get 0 byte files grrrrr!!
I still need to find a way of getting root
This phone is a tricky beast for a learner - lol
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
gbl08ma said:
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
Click to expand...
Click to collapse
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
tpwuk01 said:
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
Click to expand...
Click to collapse
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
gbl08ma said:
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
Click to expand...
Click to collapse
I already had the phone in usb debug mode. Had to set the phone to use usb as MTP and not mass storage device connection type. Now it allows me to get in to the blighter with adb, fastboot still errors with pipes. That method allows me to get adb shell running and i can get android file transfer .... back to the reading part again
Thanks for the information gbl08ma - if i can find a way to back-up the rom i will share it somewhere
Hmm yummy - lots of interesting things in there .... Forgive my ignorance again please, but if i can create an update.zip file from the shell on the device that compresses all files from \ and all subdirs would that be the same thing as a safe ROM backup ? i wanna be safe before i attempt to root the phone as someone on here has a lower spec version of this phone and says it's a partial brick now.
TpwUK
Rooted
This phone is easily rooted with the motochopper
http://forum.xda-developers.com/showthread.php?p=40747604
Now should I push my luck further and go for the ROM - lol
TpwUK
I believe i own the same mobile
@tpwuk01
I also asked the same here; http://forum.xda-developers.com/showthread.php?t=2180425&page=92
but i was only able to root using frama root app, and it worked like a charm, but thats the only thing i could achieve, dont know but it seems theres no official thread of developement going on for any cloned device, mine runs the MOLY.WR8.W1248.MD.WG.MP.V6.P8 2013/08/12 15:55 Baseband.
After root i just installed some root apps, ads blockers, cant get any recovery to work, (Playing safe actually not to brick this now, since no support yet) but would have appreciated trying out kitkat on it, using antutu to view up specs, its impressive, i got to find out our 13MP camera at the back can do a great job than it currently is we only need to figure out how to change the image compression, the one i stumbled upon online was the blast, the 13MP was great also the flash light was tweaked to be 50X its current brightness, our 1GB application space was increased to 3.5GB, GPS and the rest was also modded to work really great.
Would like to hear any new updates you stumble upon bro.
Still a nice and featured packed device.
Hello and thanks for reading / helping if you can.
In brief, I have a Samsung Tab 2 GT-P3110 tablet which was running android 4.2.2. It's main use was as a controller for my sonos sound system which no longer supports my device. I thought I'd try and update it rather than simply chuck it into landfill for no good reason other than it was old like me! I know almost nothing about what I am doing, sorry!
So far I have I think 'rooted' the device using something called odin, and installed the clockwork recovery mod. I have also installed the Samsung drivers onto my PC and I have on my pc a zipped file which I believe will install a newer version of android (perhaps some guidance might be required for best file to go for). Unfortunately I am unable to see my tablet's sd card (or anything to do with the tablet) when connected to my pc via USB in order to copy it. Moreover I have copied the same file to a micro sd card but when I put this directly into the tablet and try and boot off the external card I get an access error and the card is not read.
I am out of ideas now and wonder if one of you clever people might be able to help me? I think I read somewhere about having to switch on USB debugging and USB sharing or the like BEFORE rooting. The instructions I used only mentioned the former and so that's all I did. Maybe I've locked myself out for good.
Thanks again, Pezos
Blimey, I really must have killed it! Surely someone out there can help me fix it?