I have a rooted Tbolt and the platic surrounding the pins in the USB port has broken off. One of the pins bent so my computer won't recognize my phone when connected. Still charges if I plug in carefully, but no data connection. Verizon is sending out a warranty replacement but I'd like to return the phone to stock in case they power up the phone - don't want the fact that I rooted to void the warranty. Any suggestion on how I can return to stock unrooted? Have not installed a custom ROM or kernel at this point, just rooted using dbzfanatic's EasyRoot + S-off program.
Download this on your phone, put in on root of SD card, rename to PG05IMG and flash it from recovery menu.
>>> http://forum.xda-developers.com/showthread.php?t=995819
Thanks for the reply. Quick question - if I reboot into recovery using CWM and select wipe data/factory reset, will this accomplish what I'm looking for? Will that have any effect on the backups on my SDcard? Sorry if these are n00b questions, but this is my first android device.
You don't need to boot into cwr, you can just boot into the default system recovery menu and flash the file directly from there.
Files on the sd card will not be effected.
Excellent. Thanks again for the prompt replies, yumms!
You may also be able to use Wireless ADB (on the market). Don't think you need it, but just in case - thought I would throw it in there.
yumms said:
You don't need to boot into cwr, you can just boot into the default system recovery menu and flash the file directly from there.
Files on the sd card will not be effected.
Click to expand...
Click to collapse
you dont flash that file in the stock recovery either, its done from the bootloader.
If things get a little hairy, I suggest a +1 for ADB over Wireless.
Related
Hello! I recently got a replacement for my Optimus V. It was having signal and SMS problems, so they decided to send me a replacement. I noticed this replacement has android 2.2.2 froyo pre-installed. so the first thing I tried was to root it with Rom Tools, but it didn't work, so I looked around and found Gingerbreak. Rooting was successful, and i had SuperUser privileges. So then I tried installing a custom recovery with RomTools, and it still told me I wasn't rooted. So then I tried Rom Manager, and it notified me the custom recovery was flashed, so i rebooted, and i just get a back-lit black screen. So then I tried booting into the bootloader, and it just boots to Android again, any idea why this is happening? Have they locked the bootloader?
I hope not, but that would I explain why I haven't been able to root my wife's "new" replacement phone.
Success!
Finally got my wife's phone rooted using GingerBreak. Restoring her apps (via TiB) as I type this.
FYI, I basically followed these steps: http://forum.xda-developers.com/showpost.php?p=13170826&postcount=171
RKBA said:
Finally got my wife's phone rooted using GingerBreak. Restoring her apps (via TiB) as I type this.
FYI, I basically followed these steps: http://forum.xda-developers.com/showpost.php?p=13170826&postcount=171
Click to expand...
Click to collapse
Not all phones are created equal. Make sure you have a stock 2G SD card formated to the default settings It gets really picky about the sd card some times. The more stuff on your sd card the longer it will take. Turn on USB debugging,your not going to plug it into your PC,but you need to have it enabled or the exploit wont work. Make sure you have a good file manager like Super Manager installed on your phone. Download the Gingerbreak.apk. With the file manager go to sdcard/downloads or download. Move the exploit to the root of the sdcard(somewhere near the bottom of the list of folders). Open up the exploit and select install. Once it's done installing the exploit to your phone select done,exit. Reboot phone. Go to app draw and select the exploit,select run. It might take up to 10 min.for it to run. If it goes 12min.pull battery and try again(it could take several tries). You must reboot after every failed attempt. If you get an error message it does not like your SD card. Reformat to default settings using you computer and try again. If you are using a sd card that is not 2G it might not work. Once it reboots and you are looking at your home screen,you are rooted. Now go to the market and download Busybox installer. With a file manager go and check where su has been installed. It's either /system/bin or /system/xbin. Install Busybox wherever su is. Go back to the market and update Super User. Gingerbreak will not install the proper flash_image to flash a custom recovery, but, You can use ROMTools to flash Xionia recovery,or ROM Manager to flash ClockworkMod recovery. Once you have a custom recovery on your phone you need to make a nandroid backup of your system because now that your ROOTed you now can delete things you may not want to, then it's to late. AHH, But you made a backup that you can restore and your phone is as good as new again....P.S.Sorry no links, till I have 8 or more posts,at least I think that's what it said
awerni said:
Hello! I recently got a replacement for my Optimus V. It was having signal and SMS problems, so they decided to send me a replacement. I noticed this replacement has android 2.2.2 froyo pre-installed. so the first thing I tried was to root it with Rom Tools, but it didn't work, so I looked around and found Gingerbreak. Rooting was successful, and i had SuperUser privileges. So then I tried installing a custom recovery with RomTools, and it still told me I wasn't rooted. So then I tried Rom Manager, and it notified me the custom recovery was flashed, so i rebooted, and i just get a back-lit black screen. So then I tried booting into the bootloader, and it just boots to Android again, any idea why this is happening? Have they locked the bootloader?
Click to expand...
Click to collapse
With power on,pull sd card. Put your sd card into PC and copy(don't move anything off the sd card)the contents into a new folder. Put the sd card back into phone with power on. If it boot's up properly let me know. You should be able to power off and on and it boots up properly. Don't do anything more to it until you let me know(your going to have to change some permissions on some files, check Busybox install,etc.).
awerni said:
Hello! I recently got a replacement for my Optimus V. It was having signal and SMS problems, so they decided to send me a replacement. I noticed this replacement has android 2.2.2 froyo pre-installed. so the first thing I tried was to root it with Rom Tools, but it didn't work, so I looked around and found Gingerbreak. Rooting was successful, and i had SuperUser privileges. So then I tried installing a custom recovery with RomTools, and it still told me I wasn't rooted. So then I tried Rom Manager, and it notified me the custom recovery was flashed, so i rebooted, and i just get a back-lit black screen. So then I tried booting into the bootloader, and it just boots to Android again, any idea why this is happening? Have they locked the bootloader?
Click to expand...
Click to collapse
With power on,pull sd card. Put your sd card into PC and copy(don't move anything off the sd card)the contents into a new folder. Put the sd card back into phone with power on. If it boot's up properly let me know. You should be able to power off and on and it boots up properly. Don't do anything more to it until you let me know(your going to have to change some permissions on some files, check Busybox install,etc.). If it doesn't work,you can try something else as well.EDIT: Try and see if your phone is still recognized by your computer. It might be,if it is then open up ROMTools and select ROMTools.exe . Type in 2(enter). Type in 2 (enter) Allow SuperOneClick to establish a Shell Root(temporary Root)click ok and close small window but not SuperOneClick. Click on command prompt window to bring it to the front. Type in 4(hit enter key). Let it do it's thing. If it was successful it will say so. Now try and pull SD card out with power on. Put SD card back in with power on.
i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
babybear293 said:
i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
Click to expand...
Click to collapse
can't do commands via usb, i'm reading this to mean, you don't have adb access.
after wiping the /data partition, where system settings are stored, including the toggle for adb access via, you will probably have to re-enable.
to enable adb access via usb on sense -> settings -> applications -> development -> usb debugging. this should be toggle on.
if that doesn't work, post back and we can start digging deeper but i'm hoping that'll resolve your isse!
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
thos25 said:
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
Click to expand...
Click to collapse
Well there is a lot going on in that post ... Not sure how my application Flash Image GUI failed. I would be more than happy to fix/resolve any bug or issue you've encountered!
Fastboot usb mode should always work. There is no setting in Android which will have any impact on fastboot usb mode (other than not allowing the device to boot into the bootloader). I generally find the best process to be, boot the device into the bootloader, plug in usb and then select fastboot.
Perhaps, once you're in the bootloader, you can also select fastboot and then plug in USB (this works best on my NS4G).
Either way, fastboot usb should always work. If you're using Windows, there could definitely be a drivers issue or Windows being finicky with the drivers and that might result in fastboot USB not working. A simple reboot of the Windows machine should clear any fastboot driver issues.
The best working method to correctly load a ROM is by properly loading the recovery to work with the HTC unlock method. HTC unlock method will only grant the recovery write access to the boot partition when the recovery image is temporarily fastboot boot'd. The command is: fastboot boot c:\android\cwm-recovery.img.
If you boot into the bootloader and select recovery from the menu, it will boot into the recovery, but the HTC unlock method will not grant the recovery write access to the boot partition. You can flash a ROM from here and restore a nand. Both will completely successfully and claim they flashed the kernel w/o any issues but the memory write lock will have prevented the kernel writes from being retained.
Also, regarding my application, Flash Image GUI, it should properly flash any EVO 3D kernel .zip file from normal Android mode as the HTC unlock method allows kernel write access while in normal Android mode.
Why did HTC block kernel write access from recovery mode? They haven't provided an answer .. we can only speculate ...
Hope that helps explain a few more steps to the process and provide greater clarity!
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
thos25 said:
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
Click to expand...
Click to collapse
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
I had a similar issue when i was switching to AOSP kernels/roms. I rebooted my phones once or twice and it connected fine. Maybe it have something to do with AOSP since MIUI is aosp also.
joeykrim said:
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
Click to expand...
Click to collapse
Thanks for the comments and lesson. I apologize for not responding sooner, but a recent death in family prevented me from really being on here too much lately.
1) I pretty much figured that. Yeah. I only try to flash using this method, that is why when my fastboot USB disapeared I thought I was really in a bad spot. Luckily I got it working again, so all was not lost.
2). Yes. I know it should remain on SD card, which was strange why I couldn't find it. However, thinking back on it, I do remember deleting some files off of my SD card on the same night. I probably just mistakenly deleted my CWM Recovery with my NAND backups. Sometimes when I double click a file to look at it, when I leave the file I see that there is a checkmark on that file. I may have just not noticed the checkmark on the CWM, went to delete another file, and mistakenly deleted CWM with it.
3) An RUU will not change a RADIO? I was under the impression that they did. Sort of like applying an OTA, but manually doing it through SYNC.
well, thanks again though. I learned some new things and appreciate it.
Flash image GUI works like a charm
Sent from my PG86100 using XDA App
i m a newbie
plz tell me how to get out of the fastboot usb mode. i m stuck with the G1 screen having fastboot usb title on the top.
PLZ HELP!!!
Hey!
A friend of mine recently got her S2 bricked due to a faulty OTA update. She was prompted to install ICS, even though the network operator's branded version is not to be released for another week or so (2 weeks after the stock release).
Now the device won't start, and customer support says she needs to hand it over to reset the phone. Although this fixes the phone, she would like to keep her pictures etc. that is saved in the phones internal memory.
Is it possible to mount the /data partition (or /user or whatever) to a Windows PC, and recover the files? I do believe the phone can boot in recovery, and I am moderately experienced with using ADB.
Optionally, is it possible to "abort" the update, and reset the phone to it's previous state? I was thinking to wipe the cache partition, but i'd love your input on this matter!
--excubated
You could try flashing a GB rom via Odin. Or if you can, flash CWM recovery and mount the internal card (its sd_card, I think). Otherwise, I haven't a clue.
Sent from my GT-I9100 using XDA
Try Recuva
jje
JJEgan said:
Try Recuva
jje
Click to expand...
Click to collapse
Recuva is for deleted files (which also doesn't work too well on flash memory).
If she's got a custom recovery like ClockworkMod, skip to step 2.
Step. 1) download and install ClockworkMod recovery onto the device.
Step. 2) boot into CWM.
Step. 3) Go to Mounts and Storage.
Step. 4) Select Mount USB Storage.
Step. 5) Download (the .zip version) and extract the Android SDK.
Step. 6) Open a command prompt (CTRL+R, type cmd, hit enter).
Step. 7) CD to where ever you extracted to the SDK, like say C:\Android_SDK
Step. 8) CD to \platform-tools
Step. 9) In the command prompt, enter:
adb pull /sdcard/DCIM DCIM\
That should pull the camera folder. If there's photos outside that folder, try adb pull /sdcard SDCARD\
If you're looking to delete the photos, go back into Mounts and Storage, and hit format /sdcard.
But, if you can, as stated above, try flashing to a Gingerbread ROM and copying over like normal. A lot less hassle than the above.
screamworks.
Try It
excubated said:
Hey!
A friend of mine recently got her S2 bricked due to a faulty OTA update. She was prompted to install ICS, even though the network operator's branded version is not to be released for another week or so (2 weeks after the stock release).
Now the device won't start, and customer support says she needs to hand it over to reset the phone. Although this fixes the phone, she would like to keep her pictures etc. that is saved in the phones internal memory.
Is it possible to mount the /data partition (or /user or whatever) to a Windows PC, and recover the files? I do believe the phone can boot in recovery, and I am moderately experienced with using ADB.
Optionally, is it possible to "abort" the update, and reset the phone to it's previous state? I was thinking to wipe the cache partition, but i'd love your input on this matter!
--excubated
Click to expand...
Click to collapse
try using different ROM of any other country but of same Model no. (e.g. GT-I9100) in the downloading mode throug ODIN3. And formatting Cache partition will not change anything, but speed up the phone. firmware up gradation will not wipe your phone internal memory.
Hope it works for you....
Thanks for your answers so far, but I do believe flashing over any recovery or firmware will void the warranty on the device? She's not very eager to venture into the realm of warrantylessness, unfortunately ..
If whe was, she'd have had the MIUI ICS experience from the day it was launched Need to keep everything stock, and if there is no way to retrieve the files without voiding the warranty, she'd rather send it in and lose all her data..
screamworks said:
adb pull /sdcard/DCIM DCIM\
Click to expand...
Click to collapse
Can't I enter the normal recovery's terminal with adb shell? From there I mean to remember it is possible to mount and pull whatever I want..
Even without installing a custom recovery (CMW), the SGSII will allow you to go in to either Download Mode or Recovery mode. And I believe you should be able enter either mode even if the phone isn't booting up successfully (from a failed upgrade).
To enter recovery mode, you press and hold the Up Volume, Home Key and Power buttons.
To enter Download mode, you press and hold the Down Volume, Home Key and Power buttons.
You should be able to find the latest official/stock Gingerbread ROM in the forums here, and then you use Odin to install the GB ROM (from Download mode). This won't increase the count of "unofficial" Roms on the phone and shouldn't void the warranty.
While Odin is often referred to as a means to flash a custom ROM, it's not limited to only that. And the same for recovery mode. Most posts reference the CMW recovery that allows you to change to custom kernels and update "unofficial" packages on a rooted phone.
But you should still be able to revert back to a GB-based ROM and not void any warranty.
[if you boot the phone in to the official Samsung Download mode, it will display a message on the screen about the number of non-Samsung ROMs have been installed on the phone, and you should not see any number, or maybe "Zero"... I can't check to be sure because I forgot my phone in the office when leaving work today After you downgrade to GB, you can verify that the number is still blank or "Zero" by going back in to Download mode after you're sure the GB install was successful (it's not destructive to go in to Download mode just to view the counter. just power it off (as long as you're in the middle of pushing code to the phone ) and then reboot]
I'm not as experienced as a lot of the folks on the site, but everything I've outlined above I've done at least a few times on my phone (to custom ROMs, back to official, even resetting/clearing the "counter", and I've always been able to recovery from a "bad install").
I hope that helps,
Hey,
I am currently trying to help my best friends dad out. He dropped his GS2 during his holiday. Now the lcd is dead. The digitizer is not broken and seems to be working, as I get a feedback from the lockscreen when I tap on it, but I am having a small suspicion, that one half of the digitizer doesn't work anymore. The phone has a pin lock screen, it is not rooted and developer options are not turned on.
Is there any way to get access to the internal storage, and recover files from there? (He wants the pictures back he made on holiday )
Btw: I haven't owned any Samsung smartphone yet and I don't know how the recovery stuff works there so if there is a solution for this problem I would really appreciate a step by step tutorial. I have knowledge about rooting, flashing and stuff, so if it would be a solution to root the phone, I could do that, as my best friends dad doesn't want to repair the device anyways.
Greetings
Bl4ckX
Nobody any idea? :/
Sent from my HTC One X using XDA Premium 4 mobile app
Hoping someone can answer me this. I have a broken USB miniport (Stood up too fast and yanked the cord hard enough to break connector off the mainboard). Fortunately I had a rom loaded and I was able to drop files on via USB stick or microSD or dropbox. My question now is, can I return to a stock ROM without NVFlash on the PC? If I created a backup from another tablet that was freshly loaded with stock/CWM could I simply restore it using CWM on the broken tablet?
Yes, it's possible, but, not advised because the stock ROM is not rooted, so you won't be able to fix things by using the command line utilities (to write partitions or to format, etc.) in case something goes wrong.
And, since recovery mode does not have networking enabled (it should be possible in CWM, though), you will need a working rooted ROM to do things without a working USB connection.
Additionally, going back to stock without nvflash (and without modifying the update.zip file) requires the recovery to be stock recovery and now CWM.
Why do you want to go back to the stock ROM anyway?
I have a Samsung Galaxy s3 which I successfully rooted over a year ago though I never bothered with a custom rom. I have now purchased a note 3 so in preparation for selling the S3 I did a factory reset through Settings to clear out all my apps, data and personal information. That all went well and the device booted back into the normal system a couple of times (I didn't check to see if root had been maintained or not) This weekend I got it out to sell it only to find that it boots through the first part of the routine with the Samsung moving logo but then sticks on the static SAMSUNG screen and will not go further.
I am able to boot into TWRP so would I be able to download a stock rom from somewhere, insert a micro sd card with the stock rom on it and recover through TWRP? Alternatively I do have an old full back up stored on my computer - I could transfer this to the micro sd and restore this through twrp - I can see this was made through twrm as the openrecovery-twrp-2.3.1.0-i9300.tar.md5 is stored with it. Of course if this works I would still need to perform a reset to get rid of all the personal data etc so could end up in the same situation later.
What recommendations do you helpful guys have?
gbswales said:
I have a Samsung Galaxy s3 which I successfully rooted over a year ago though I never bothered with a custom rom. I have now purchased a note 3 so in preparation for selling the S3 I did a factory reset through Settings to clear out all my apps, data and personal information. That all went well and the device booted back into the normal system a couple of times (I didn't check to see if root had been maintained or not) This weekend I got it out to sell it only to find that it boots through the first part of the routine with the Samsung moving logo but then sticks on the static SAMSUNG screen and will not go further.
I am able to boot into TWRP so would I be able to download a stock rom from somewhere, insert a micro sd card with the stock rom on it and recover through TWRP? Alternatively I do have an old full back up stored on my computer - I could transfer this to the micro sd and restore this through twrp - I can see this was made through twrm as the openrecovery-twrp-2.3.1.0-i9300.tar.md5 is stored with it. Of course if this works I would still need to perform a reset to get rid of all the personal data etc so could end up in the same situation later.
What recommendations do you helpful guys have?
Click to expand...
Click to collapse
try to some firmware dude
u have usb jig? use it to reset u binary :good:
and flash again with odin
if u have backup in cwm u can restore so Do it :good:
As you are going to sell it then follow the guide in general forum, stickies to return to stock. Factory reset before you boot the fresh firmware.
further
VerlyAnanda said:
try to some firmware dude
u have usb jig? use it to reset u binary :good:
and flash again with odin
if u have backup in cwm u can restore so Do it :good:
Click to expand...
Click to collapse
I don't have a usb jig whatever that is
I have an old back up on my computer which I can copy to an external SD card to put in the phone
I can then try using TWRP (I have this not CWM) to try restore the back up
This may work I can only try it - however I will still be in the position of needing to do the reset to clear all my data and put the phone back into "new" state and am concerned this may cause the problem again
Is this the best plan? I suppose once I get it working I can use ODIN to flash a stock rom
The problem is I understood all this a year ago when I rooted it but its all a little vague to me now as I decided not to do more than root the phone so I could back it up
formatting cache solved the problem!
gbswales said:
I don't have a usb jig whatever that is
I have an old back up on my computer which I can copy to an external SD card to put in the phone
I can then try using TWRP (I have this not CWM) to try restore the back up
This may work I can only try it - however I will still be in the position of needing to do the reset to clear all my data and put the phone back into "new" state and am concerned this may cause the problem again
Is this the best plan? I suppose once I get it working I can use ODIN to flash a stock rom
The problem is I understood all this a year ago when I rooted it but its all a little vague to me now as I decided not to do more than root the phone so I could back it up
Click to expand...
Click to collapse
I read someone had the same problem and just cleared the cache - so went into Team Win wiped cache and it restarted - guess I was looking for a complicated solution to something simple!