Originally posted in general. Sorry.
My Evo won't charge unless it is turned off. When the phone is on, the usb won't give me any mode option. Phone doesn't see the sdcard. I've tried three different cards. PC won't see the phone. I have usb debugging checked. Device manager gives me three qualcomm CDMA Technologies and can't find drivers. Downloaded qualcomm drivers. Device manager now shows them as samsung items. Everything on the phone works except for apps using the sdcard. With the vol down and power the phone will read the PC36IMG.zip of the sdcard and load and run it. After rebooting it still doesn't recognize the sdcard. Using fastboot the device manager gives me Android Devices, but I can't use adb commands. I get and error device not found. Any help?
it should charge anyway, even without the drivers...but, sounds like you need 'em to me. they're in the forums...somewhere...or, you could just get the most recent sdk, and update the drivers using devmgmt.msc (i'm assuming you're on windows)
this happen to me yesterday, i was able to fix it... i have to find the steps
airauto said:
Originally posted in general. Sorry.
My Evo won't charge unless it is turned off. When the phone is on, the usb won't give me any mode option. Phone doesn't see the sdcard. I've tried three different cards. PC won't see the phone. I have usb debugging checked. Device manager gives me three qualcomm CDMA Technologies and can't find drivers. Downloaded qualcomm drivers. Device manager now shows them as samsung items. Everything on the phone works except for apps using the sdcard. With the vol down and power the phone will read the PC36IMG.zip of the sdcard and load and run it. After rebooting it still doesn't recognize the sdcard. Using fastboot the device manager gives me Android Devices, but I can't use adb commands. I get and error device not found. Any help?
Click to expand...
Click to collapse
here you go
http://forum.xda-developers.com/showthread.php?t=695243
The phone only charges when the phone is off. I've downloaded the latest sdk drivers. I tried the SD Card Fix, but I can't get to an ADB shell.
The phone worked great for a couple of weeks, but when I was using Rom Manager to load a rom, I got an error and a red triangle. I pulled the battery and started the phone. It couldn't load the sdcard, it wouldn't give me usb options. It did give me a short battery life and no way to use ADB commands. I can't use rom manager or titanium backup or nand to restore backups. I really need help please!
airauto said:
The phone only charges when the phone is off. I've downloaded the latest sdk drivers. I tried the SD Card Fix, but I can't get to an ADB shell.
Click to expand...
Click to collapse
if you can't get to a shell, that probably means that an adb devices command is not seeing the device.
i'll refer you to the earlier statement about you not having the drivers.
I checked and I have downloaded android-sdk_r06-windows.zip. I believe these are the latest drivers. They worked fine until it crashed while I was using rom manager to load a different rom. It seems strange that everything works except for charging while on, usb and the sdcard.
airauto said:
I checked and I have downloaded android-sdk_r06-windows.zip. I believe these are the latest drivers. They worked fine until it crashed while I was using rom manager to load a different rom. It seems strange that everything works except for charging while on, usb and the sdcard.
Click to expand...
Click to collapse
just having the sdk doesn't enable drivers. if you are on windows, in the 'search' field (or in a cmd shell) type
devmgmt.msc
there, you will probably see a device , i think it will have a yellow triangle and an exclamation point. right click on that device, choose the option that allows you to install drivers. then, browse for drivers (make sure you have the option to include subfolders checkmarked). the drivers are located in the 'usb drivers' folder in the sdk folder. once you have the 'usb drivers' folder highlighted, just choose 'okay', and it will search that folder and subfolders for the appropriate driver.
I've done that. When I use devmgmt.msc and I connect my phone it gives me three unknowns called Qualcomm CDMA Technologies MSM. I point these to the drivers folder and it doesn't recognize them. I downloaded qualcomm drivers and it recognized them as samsung devices and these don't work. When I hook up usb while in fastboot devmgmt.msc gets one device called android devices, but it still will not recognize the sdk drivers. Something happened when the phone crashed. Is there a way to do anything with hboot or fast boot or the other items in that menu to get the phone to recognize adb commands. The phone does load and install PC36IMG.zip, but the phone still acts the same, no sdcard, no usb and no charge.
I was trying this thread
http://forum.xda-developers.com/showthread.php?t=695243
How do you Run from a terminal emulator in Android since I don't have ADB?
airauto said:
I was trying this thread
http://forum.xda-developers.com/showthread.php?t=695243
How do you Run from a terminal emulator in Android since I don't have ADB?
Click to expand...
Click to collapse
you have to get a terminal emulator. and, you have to have downloaded those files to your sdcard. you also have to be rooted already.
OK, I have the two files extracted and on the sdcard. I called up the terminal emulator and typed
su
cat /sdcard/flash_image > /data/flash_image
at this point I get an error message /sdcard/flash_image: No such file or directory
at one time my phone was rooted, but I no longer have the Superuser Permissions.
help some more?
Edit/Delete Message
Ok thanks, I finally got it all working. After a week of learning about ADB, Terminal and Fastboot commands not to mention the structure of the Evo file system, charging, usb and sdcard are all working thanks to everyone contributing to the forum.
airauto said:
Ok thanks, I finally got it all working. After a week of learning about ADB, Terminal and Fastboot commands not to mention the structure of the Evo file system, charging, usb and sdcard are all working thanks to everyone contributing to the forum.
Click to expand...
Click to collapse
could you provide a step by step to how you got this issue resolved?
my brother's phone is experiencing the exact same symptoms you described.
we have been at it for a week.
we too cannot get the "adb shell" command to work when trying to use SDK.
we get the error "device not found" after typing "adb shell".
Im not sure its being done correctly either.
please assist, your help is greatly appreciated.
I used this thread:
http://forum.xda-developers.com/showthread.php?t=695243
Read through the whole thread and download the files. Install them on the root directory of your sdcard with a card reader/writer. Put the sdcard back in your phone.
Now to use the thread you have to get into recovery.
Hold vol down and press power on your phone.
Plug in the usb, and open device manager on your PC.
Choose recovery and make sure Android USB Devices show up in device manger
On the PC, get to a DOS prompt and change dir to where you have adb and fastboot and follow the thread for SD Card Fix and USB Fix exactly.
Good Luck!
And thank you to Calkulin for the thread!
airauto said:
I used this thread:
http://forum.xda-developers.com/showthread.php?t=695243
Read through the whole thread and download the files. Install them on the root directory of your sdcard with a card reader/writer. Put the sdcard back in your phone.
Now to use the thread you have to get into recovery.
Hold vol down and press power on your phone.
Plug in the usb, and open device manager on your PC.
Choose recovery and make sure Android USB Devices show up in device manger
On the PC, get to a DOS prompt and change dir to where you have adb and fastboot and follow the thread for SD Card Fix and USB Fix exactly.
Good Luck!
And thank you to Calkulin for the thread!
Click to expand...
Click to collapse
Yeah I had found that thread as well, I get all the way up to the adb commands.
when I type adb shell, I get "device not found".
also, just to verify, I boot the phone down and turn it on using "down volume" and "power".
when the "HBOOT" screen shows up and the scan finds nothing, I select "fastboot", and leave it there.
then back to the pc:
before I type "adb shell', I point to the directory "c:/users/desktop/android-sdk-windows/tools".
once the directory is pointed to "c:/users/desktop/android-sdk-windows/tools", I input "adb shell" command.
Is this correct?
That is the procedure I follow and I keep getting "device not found", and yes my sdk is fully updated.
Yes, but don't do ADB shell. In HBOOT hit the vol down button to highlight recovery. Hit the power button to select recovery and let it sit there. Go to your pc check your device manager. Then change dir to where you have ADB. Fastboot is also there
Fastboot is an executable program same as ADB. At the prompt just type the commands for the sdcard fix. ie:
fastboot oem enableqxdm 0
fastboot reboot
Your sdcard should be recognized. For the next section you will need to get the Android Terminal Emulator from the Android Market and enter the commands in it.
Have fun!
jdr6382 said:
Yeah I had found that thread as well, I get all the way up to the adb commands.
when I type adb shell, I get "device not found".
also, just to verify, I boot the phone down and turn it on using "down volume" and "power".
when the "HBOOT" screen shows up and the scan finds nothing, I select "fastboot", and leave it there.
then back to the pc:
before I type "adb shell', I point to the directory "c:/users/desktop/android-sdk-windows/tools".
once the directory is pointed to "c:/users/desktop/android-sdk-windows/tools", I input "adb shell" command.
Is this correct?
That is the procedure I follow and I keep getting "device not found", and yes my sdk is fully updated.
Click to expand...
Click to collapse
airauto said:
I used this thread:
http://forum.xda-developers.com/showthread.php?t=695243
Read through the whole thread and download the files. Install them on the root directory of your sdcard with a card reader/writer. Put the sdcard back in your phone.
Now to use the thread you have to get into recovery.
Hold vol down and press power on your phone.
Plug in the usb, and open device manager on your PC.
Choose recovery and make sure Android USB Devices show up in device manger
On the PC, get to a DOS prompt and change dir to where you have adb and fastboot and follow the thread for SD Card Fix and USB Fix exactly.
Good Luck!
And thank you to Calkulin for the thread!
Click to expand...
Click to collapse
That was it!! once we got the files on the SD card through my phone, and put it back in his phone, we did the commands and it worked!! good stuff, mad appreciation given here.
Congratulations. You got your EVO back better than ever!
Related
Alright so last night i ran the DCupdater and saw the damagecontrol v3.1.2 update. So i downloaded it and tried running that. Thats when my evo started freaking out and the sd card kept getting disconnected. After all that nonsense it got installed. But then as my phone restarted it was in for the loop of watching the HTC EVO 4G logo. Thats when i tried going to one of my backups and that seemed to work. So then after that i when back to damagecontrol v3. But that messed everything up even more because now im stuck on v3 without sd card. When i try going into the bootloader it wont let me. When i hook up the phone to my pc via usb it wont let me see the sd card contents. I tried doing the:
fastboot oem enableqxdm 0
fastboot reboot
but that had no effect and the cmd wouldnt even recognize the command
what do i do?
xarttyx said:
Alright so last night i ran the DCupdater and saw the damagecontrol v3.1.2 update. So i downloaded it and tried running that. Thats when my evo started freaking out and the sd card kept getting disconnected. After all that nonsense it got installed. But then as my phone restarted it was in for the loop of watching the HTC EVO 4G logo. Thats when i tried going to one of my backups and that seemed to work. So then after that i when back to damagecontrol v3. But that messed everything up even more because now im stuck on v3 without sd card. When i try going into the bootloader it wont let me. When i hook up the phone to my pc via usb it wont let me see the sd card contents. I tried doing the:
fastboot oem enableqxdm 0
fastboot reboot
but that had no effect and the cmd wouldnt even recognize the command
what do i do?
Click to expand...
Click to collapse
before you enter those commands you have to hold power and volume down and go into fastboot on the phone - after that connect it to the computer
click start - run - CMD
After that
type cd "location of your android sdk tools folder" - OR cd "drag the folder of your tools folder into the prompt"
THAN
type the commands -
fastboot oem enableqxdm 0
fastboot reboot
mongoose8p said:
before you enter those commands you have to hold power and volume down and go into fastboot on the phone - after that connect it to the computer
click start - run - CMD
After that
type cd "location of your android sdk tools folder" - OR cd "drag the folder of your tools folder into the prompt"
THAN
type the commands -
fastboot oem enableqxdm 0
fastboot reboot
Click to expand...
Click to collapse
where do i find that folder... im sorry i dont really know much of this
i'm assuming you are using windows. it's the location of your \android-sdk-windows\tools\ folder from when you installed the android sdk in order to root in the first place. it is also the location of adb. if need be, do a search for adb.exe and it should point you directly to the location of everything you need.
It keeps saying "the system cannot find the path specified". I dont even know what to do. This sucks.
it might be under a different path, where did u install ur android sdk?
i don't really remember. i found it though searching for adb and i guess i have 2 folders of it... zipped and unzipped... but i tried putting both path names in there and that went nowhere
When you search for adb or your android sdk tools folder, go into that folder and hit Shift+right click and "open command window here" then use your commands.
awesomeindeed said:
When you search for adb or your android sdk tools folder, go into that folder and hit Shift+right click and "open command window here" then use your commands.
Click to expand...
Click to collapse
that option does not pop up.. im running xp if that helps
im still having trouble figuring out what to do.
xarttyx said:
that option does not pop up.. im running xp if that helps
Click to expand...
Click to collapse
copy the path of the folder with adb.exe in it - start - run cmd - command "cd path of adb folder" - then follow the instructions above
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
I bought the Motorola Bravo which is similar to the Flipside and an app on the market called Z4ROOT was able to root the phone. It works on many phones not just the Bravo. Give that try and see if it works.
z4root does work for permanent root i have tried and can confirm
jediskywalker said:
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
Click to expand...
Click to collapse
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Got my Flipside rooted and non market apps allowed
I followed the instructions given at modmymobile dot com forum. Look up "fully unlock 3rd party apps backflip" It allowed me to root my phone and install non market apps. I tried and tried to follow the instructions given here, but i guess they weren't idiot proof. It is for the backflip, but it worked perfectly for my Flipside. I couldn't post the link here.
Someone found some typos in my scripts. I have updated them so they are accurate. Should make things run better.
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
ishiiisbooyah said:
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
Click to expand...
Click to collapse
Lets say you installed your SDK in the default folder, you would need to type
Code:
cd c:\"Program Files"
cd Android
cd appinventor-extras
Now, I put mine in c:\SDK, so all I type is
Code:
cd c:\SDK
you either must add the SDK to your PATH, or find the directory that you installed it to, and then try running adb from there. If adb.exe isn't in the folder, you aren't in the right folder.
jonsjava said:
Rooting a Motorola Flipside
[/url]
Click to expand...
Click to collapse
hi
i m new in unlocking field
can i unlock this handset "flipside" by motorola came from usa at&T
if yes then plz explain
thanks in advance
RZ4root does not appear on the marketplace and when I click the link above it starts to download, then says the content is not supported on my phone.
Model num MB508 Motorola Flipside running Android 2.1 update 1.
You need to push it to the phone from a computer using adb to install z4root, now that it has been removed from the market.
Sent from my Liberty using Tapatalk
adb.exe not in the zip file
jonsjava said:
Rooting a Motorola Flipside
grab the ADB SDK files
android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
(...snipped...)
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Click to expand...
Click to collapse
adb.exe is not present in the SDK that you linked. Are you sure that is the SDK we need to root the Flipside?
You have to install it manually. It comes with the platform-tools.
how do i install adb.exe from platform-tools
lol, i may ask stupid questions but this one wasnt me, i shouldnt leave my laptop lying around haha
jonsjava said:
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Click to expand...
Click to collapse
Notice:
For anyone having trouble rooting the Motorola Flipside with these instructions, after much trial and error I managed to get my girlfriend's rooted. I'll provide the method I took.
Note: The easiest way to do this is to have downloaded and extracted "android-sdk_r08-windows" directly to your (C: ) drive. Not under programs or another system folder.
Once you have it extracted to (C: ), copy and paste z4root.1.3.0.apk into the "android-sdk_r08-windows" folder. ADB.exe will most likely not be in here. What you have to do now is click on SDK Manager within the SDK folder. A Black Command window will pop-up, ignore it. A secondary window will pop-up prompting you to install the packages I went ahead and installed all of them (better if you don't know which to install).
Now that they've all been installed, a command line will state that ADB has to be restarted. Let it restart and it should say completed.
Now -- here's where everything was messing up. When you click open the SDK-R08 folder, you should have the z4root.apk file right there amongst a list of folders. Go to the "platform-tools" folder and in there you should see the ADB.exe file. Ignore that for now. While in platform-tools press Ctrl+A so that everything is highlighted. Right click and select Cut, back out to the main directory of the SDK R08 folder and select Paste so that the ADB.exe, .dll, and all the other files from within platform-tools is out and listed alongside the z4root.apk.
Next - Follow all of the instructions up to "Plug in your phone, and have it set to "Charge only" Like JonsJava said, open up command prompt (type in CMD in the "search programs and files bar"). If you extracted the "android-sdk-r08-windows" file directly to the (C: ) drive, all you have to type in is...
(Note: Before I go into that, it'll be easiest to rename the file "SDK" instead of the whole "android-sdk, etc, name... I'll complete the instructions assuming you renamed it to SDK. Continued below... all you have to type in is...
cd C:\SDK
(The next line below will look like this)
c:\SDK>
Here, type in... adb install z4root.1.3.0.apk
Total should look like... c:\SDK>adb install z4root.1.3.0.apk
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Last note:
Uploaded with ImageShack.us
This is what the main directory of the SDK folder should look like before you enter anything in the command line.
I don't seem to be able to get this...
I'm using x64 windows 7, I have a Flipside MB508 on 2.1, and I can't get this to work.
I followed all the instructions, updated all the platform-tools stuff, and now my problem lies with the driver, I believe.
I installed those Motorola drivers that were linked, with my phone unplugged, successfully..
copied the apk to C:\SDK...
found adb.exe in the platform-tools folder..
...and this happened..
C:\SDK\tools>cd C:\SDK
C:\SDK>cd platform-tools
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
error: device not found
C:\SDK\platform-tools>_
"error: device not found" every time i try this
USB debugging is on, phone is plugged in set to charge only..
Windows even sees it, the taskbar eject icon says 'Eject MB508"
please please help me get adb to see my phone.. I really want to be able to root this thing!!
EDIT: I noticed the Motorola drivers are 32bit.. I'm going to try 32 bit windows 7 instead of 64 bit and see if I get more successful results
EDIT 2: Bazinga!! Installed Win7 32 bit on my other HDD, booted up, followed the steps again, worked flawlessly! Thanks a lot for the easy instructions, got z4root installed, and my phone worked with permanent root
ErebusRaze said:
Notice:
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Click to expand...
Click to collapse
You wrote in here that once rooted, thebphone would no longer have low memory issues...i rooted my wife's phone, was able to sideload applications (but for some strange reason I am now unable to, as adb command prompt states 'device not found')- but she still gets low memory issues at least 2-3 times a week...
I should just hold up a sign...
LINK2SD
Its in the market
Sent from my MB508 using XDA App
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
thehotrod11 said:
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
Click to expand...
Click to collapse
Link2sd makes installing to sd card possible on 2.1...
Sent from my MB508 using XDA App
So i think I bricked my kindle fire. It is rooted and when trying to install a new ROM, i accidentally selected the fastboot option. Now, when I power it on, all i get is the logo and it never loads. I cannot get into the boot manager to try anything. I have tried the Kindle Unbrick utility from this link: http://forum.xda-developers.com/showthread.php?t=1428428 and it says waiting for device when I run the stuck on logo option. Is there anything else I can do? I really dont want to get another one. Any help would be appreciated! I can't post in the development forum so thats why i posted here. Thanks everyone.
What version of Windows are you using?
Read the WHOLE first post of the Unbrick Utility thread. It's a driver problem.
Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!
roykurka said:
Thanks I got it to work now but now when I plug it into the USB, it does not show that I can open it and drop files. I go into TWRP and try to mount the USB and it will not let me and I am unsure what to do!
Click to expand...
Click to collapse
If you're using an ICS ROM I don't believe mounting "mass storage" works on all of them.
Does it saying anything when trying to mount USB in TWRP? What does "won't let me" imply? Windows or TWRP throws an error message?
When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.
roykurka said:
When I go into TWRP and go to MOUNT and then try to select Mount SDCard it will not let me check the box. I have a ROM running on it now but I cannot access the SD card when I plug it into the computer.
Click to expand...
Click to collapse
What ROM are you using?
nchevaux said:
What ROM are you using?
Click to expand...
Click to collapse
i am using CyanogenMod 9.0.0-RCO-otter-UNNOFFICIAL
Also, when i go to the about tablet on the Kindle and look at Model Number, it shows Galaxy Nexus.....
Any other suggestions or help?
roykurka said:
Any other suggestions or help?
Click to expand...
Click to collapse
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.
roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
I set the path to where the android sdk is located and it still doesnt work.
Im sure I sound like a newb or something but I am just not as tech savy with these kind of things. thanks everyone for your help with this.
Click to expand...
Click to collapse
Find the adb executable through Windows Explorer. Once you find the folder containing adb, shift-right-click inside that folder and select "Open command window here" and then you'll be able to use the adb command.
Another way to do it is to download the Kindle Fire Utility distribution and follow the third post in this link...
http://forum.xda-developers.com/showthread.php?t=1552547
You don't have to set the path to anything special if you do it one of those two ways.
roykurka said:
I have not been able to get adb to run. When i boot to TWRP and go to the command prompt and type adb devices it says " 'adb' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
It seems you have set your path incorrectly. I found it easiest to just copy the entire platform-tools folder to the root of C:\ and run adb from there (You could also use a Windows shortcut to cmd with "start in" filled out, or use shift-right click through explorer).
Definitely try to get adb working; when I first rooted my Kindle it took me an hour to fix a boot-loop without adb (damn drivers), and only seconds with adb.
kinfauns said:
Boot into TWRP and get to a prompt using adb shell. Then use this command to open parted...
Code:
parted /dev/block/mmcblk0
When you get to the "(parted)" prompt...
Code:
print
The last line, the media partition, is what gets mounted as /sdcard on your device. It should have a "fat32" file system type. If you don't have that, you need to make a new filesystem on that partition.
Code:
mkfs 12 fat32
12 is the partition number and fat32 is the filesystem type you want to use to format the partition. If memory serves, parted will ask you for this information again to confirm. Remember... 12 and fat32. Once you are done, you can...
Code:
quit
Once you've done that, TWRP should be able to see the partition and allow you to mount it on your host computer. You might have to restart TWRP... I don't remember.
Click to expand...
Click to collapse
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?
roykurka said:
When i try the first command, i get the same response saying parted is not recognized as an internal or external command, operable program or batch file.
I have the kindle in TWRP and connected to the PC. What do I do now?
Click to expand...
Click to collapse
okay... I'm going to make this super easy for you... get ADB working...
1. Download attached "adb.zip"
2. Extract adb.zip to a folder
3. Double-click "CLICK ME!!!"
4. Type "adb" and see instructions come up
5. Type "adb devices" and see a 12-digit code
now reread your own thread and try all those instructions again in ADB
P.S. type "ADB shell" before trying the instructions from kinfauns
When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple
roykurka said:
When I type the adb devcies it says "list of devices attached but does not show anything.
I apologize for probably something so simple
Click to expand...
Click to collapse
I think you should back up a bit and read this...
http://forum.xda-developers.com/showthread.php?t=1552547
Start at post #1... follow the steps in #2 and confirm your device drivers are getting loaded properly... study #3 for fastboot and adb commands.
#2 is going to be the most important for you because it looks like there's a problem with your device drivers or you are missing a necessary initialization file. Following the directions there will get you fixed up.
After doing all that, go back to my previous post.
It works, I got to mount the SD card and everything. Thank You everyone for all of your help!
Hello,
if is one here to help me i wil give him thousands bottles with beers.
My s3 is stuck in boot loop, i cant to pass samsung logo, i cant to go in cwm or download mode. I have tried to connect on my pc via usb cable but nothing is happening, i have all drivers installed but odin cant to recognized my phone, i think debugging mode is off. When the phone is off and i connect the charger he show me battery what he trying to get power but is not green.
I attach two photos to be more suggestive.
How can to pass this logo to go in cwm or to make this phone to be recognized by odin?
Thank you for reading me and for your answers.
regards,
florin
DobreaFlorin said:
Hello,
if is one here to help me i wil give him thousands bottles with beers.
My s3 is stuck in boot loop, i cant to pass samsung logo, i cant to go in cwm or download mode. I have tried to connect on my pc via usb cable but nothing is happening, i have all drivers installed but odin cant to recognized my phone, i think debugging mode is off. When the phone is off and i connect the charger he show me battery what he trying to get power but is not green.
I attach two photos to be more suggestive.
How can to pass this logo to go in cwm or to make this phone to be recognized by odin?
Thank you for reading me and for your answers.
regards,
florin
Click to expand...
Click to collapse
First question.. Do you have the I9300 (is the international version of the S3) Sprint version is SPH-L710.. If you have the 710 and flashed I9300 stuff.. you probably bricked your phone. If you DO have the I9300 version, I would pop over to that section of the forums and ask there... Here's the I9300 Section. http://forum.xda-developers.com/forumdisplay.php?f=1563
They are not compatible sadly due to different hardware, so flashing something from here will break your I9300.
Ive been where you are about three times. What i have had to do is plug my phone into the computer and have terminal or cmd prompt open.
I have to navigate to a folder that has ADB in it.
I start the bootloop on the phone and when i see the samsung logo boot up i execute the command
./adb reboot recovery
in windows i think you have to go
adb
reboot recovery
not sure though because i currently dont have a windows machine at my disposal. But you have to time this right. There is a few seconds in the bootloop where you have the ability to adb into the phone and force it to reboot into recovery this way you can flush the bad rom/kernel you accidentally flashed.
Hope this helps.
Thank you for your helpp, quick answers, you are the best form internet. All the time i get solve here in xda.
Solved, my battery it was under 25% and he cant to pass on download mode, i charged to 100% and now i can to flash what i want in download mode.
Thank you again for your quick answers.
Regards,
Florin
Hamspiced said:
Ive been where you are about three times. What i have had to do is plug my phone into the computer and have terminal or cmd prompt open.
I have to navigate to a folder that has ADB in it.
I start the bootloop on the phone and when i see the samsung logo boot up i execute the command
./adb reboot recovery
in windows i think you have to go
adb
reboot recovery
not sure though because i currently dont have a windows machine at my disposal. But you have to time this right. There is a few seconds in the bootloop where you have the ability to adb into the phone and force it to reboot into recovery this way you can flush the bad rom/kernel you accidentally flashed.
Hope this helps.
Click to expand...
Click to collapse
hello can you please be specific how to go in adb folder can you please assist with if some kind of tutorial is there I have the same problem and I havent slept from last two nights trying to solve it please help me
rishidgr8143 said:
hello can you please be specific how to go in adb folder can you please assist with if some kind of tutorial is there I have the same problem and I havent slept from last two nights trying to solve it please help me
Click to expand...
Click to collapse
What S3 do you have and exactly what is wrong with it?
Have a great day!
edfunkycold said:
What S3 do you have and exactly what is wrong with it?
Have a great day!
Click to expand...
Click to collapse
I have GT-I9305
i installed cm 10.2 few days ago
it restarted suddenly and keeps restarting again and again
I cant enter into recovery mode nor in download mode
I some how manage to enter into recovery mode it starts again and give no time wipe factory data same is with download mode
please help me
rishidgr8143 said:
I have GT-I9305
i installed cm 10.2 few days ago
it restarted suddenly and keeps restarting again and again
I cant enter into recovery mode nor in download mode
I some how manage to enter into recovery mode it starts again and give no time wipe factory data same is with download mode
please help me
Click to expand...
Click to collapse
Ok your in the wrong section, this is Sprint d2spr. So you should be posting in the forum for your device.
But most likely what you have is SDS sudden death syndrome. Which means your power button has failed. Very common on the S3 devices. Try jiggling the power button maybe blowing some compressed air into the power button area. See if it will dislodge. It is a known defect.
Have a great day!
edfunkycold said:
Ok your in the wrong section, this is Sprint d2spr. So you should be posting in the forum for your device.
But most likely what you have is SDS sudden death syndrome. Which means your power button has failed. Very common on the S3 devices. Try jiggling the power button maybe blowing some compressed air into the power button area. See if it will dislodge. It is a known defect.
Have a great day!
Click to expand...
Click to collapse
Thanks I will try doing that. I hope this works
Stuck at splash screen.
Help! I have a D2SPR and was flashing my nightly for 9/6/13 CM10.2... and now I can't get past the splash screen. What, if anything, can I do to get recovery to boot? (yes, it was a dirty flash(
Power button + volume up + home button at same time should get you into recovery.
Have a great day!
same issue
I have the Sprint SPH-L710 and flashed a Cyanogenmod nightly this morning. At this point, the phone will not boot. I can get to the Samsung screen but there it hangs. I can also get the phone connected to a computer and Odin sees it but I can't do much else with it. Any thoughts on how to force it into recovery from Odin? Any help would be much appreciated.
midkemiapug said:
I have the Sprint SPH-L710 and flashed a Cyanogenmod nightly this morning. At this point, the phone will not boot. I can get to the Samsung screen but there it hangs. I can also get the phone connected to a computer and Odin sees it but I can't do much else with it. Any thoughts on how to force it into recovery from Odin? Any help would be much appreciated.
Click to expand...
Click to collapse
I was able to get into recovery mode after flashing the CWM recovery mod from here: http://forum.xda-developers.com/showthread.php?t=2391616. I also took a look at the Cyanogenmod forum here: http://forum.cyanogenmod.com/topic/77958-20130906-stuck-on-boot-screen-dont-install/.
johnbistricky said:
Help! I have a D2SPR and was flashing my nightly for 9/6/13 CM10.2... and now I can't get past the splash screen. What, if anything, can I do to get recovery to boot? (yes, it was a dirty flash(
Click to expand...
Click to collapse
Pull battery then do the recovery button combo. It is a a known issue that that nightly doesn't boot. You could just dirty flash another nightly that does work. May break some things though.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
@rishidgb
what ive had to do in the past to resolve these issues. Ill Copy/Paste the instructions i have used to Install ADB on my past computers but ill also throw links for the origionals at the bottom of the post.
1. Verify Battery is at least 50% charged. I usually do this by turning the phone off and plugging it into the charger, you should be able to see the battery charging up.
2. Install ADB on your computer. I have a mac, and this was kind of a pain in the ass to do at first but ill explain.
Mac-
1. Download the latest Android SDK from Google: Android SDK - http://developer.android.com/sdk/index.html
2. Extract the ZIP file to your desired location
3. To get ADB, you need to install the SDK: Installing the SDK - http://developer.android.com/sdk/installing/index.html
If you are not a developer and not planning to develop, then just download the following zip file containing only the ADB tool and
proceed with the tutorial: ADB - http://esausilva.com/wp-content/plu...silva.com/misc/android/platform-tools-osx.zip
Create an environment variable (Optional) **This is good because once you create the variable you dont have to navigate to the ADB folder every time to use it.
1. Open Terminal
2. Type cd ~ this will take you to your home directory
3. Type touch .profile this will create a hidden file named profile
4. Type open -e .profile this will open the file you just created in TextEdit
In the file, type export PATH=${PATH}:/pathToTheAndroidSdkFolder/android-sdk-mac_86/platform-tools
Save file, close TextEdit, Quit Terminal, and Relaunch Terminal
NOTE: By creating an environment variable you won’t need to cd to the Android/tools folder every time you want to run ADB
You are good to go, type in terminal adb devices, this should give you a serial number, which corresponds to your phone. Looks something like this:
List of devices attached
HT99PHF02521 device
NOTE: If you did not create an environment variable, then cd to the AndroidSDK/platform-tools folder, then type ./adb devices
Also make sure you have your phone plugged in and have USB Debugging turned on (Settings > Applications > Development)
In Android 4.2.x and up Developer Options is hidden, to make it visible, do the following
Tap seven times in Build Number: Settings > About Phone > Build Number
You will get a message saying you have enabled Developer Options or something like that, go back to Settings and you will see Developer Options in there.
PC-
Step 1: Head over to this link to download the latest version of Android SDK. http://developer.android.com/sdk/index.html
Step 2: Extract the contents of the downloaded file to your hard drive. Within the unzipped “sdk” folder, you’ll find another folder labeled ‘platform-tools’. Since we’re interested in only ADB and Fastboot, this is the one that we’re looking for.
Step 3: Move the platform-tools folder to a convenient location on your PC. The root of C: drive is usually a good idea. I also recommend renaming the folder to something easier, like C:\Android-adb.
By this point, ADB is essentially set up, but to use it, you’ll first need to navigate your command prompt window to this Android-adb folder, and then run all ADB commands inside it. Since it’s too much hassle for most users, we’ll add this location to Windows’ System Path Variable, so you can run ADB commands from anywhere.
Step 4: Right-click the Computer icon on your desktop, and go to Properties.
Step 5: Under System Properties, go to the Advanced tab, and click Environment Variables.
Step 6: The system variables are contained within the lower pane. Locate “Path” here, highlight it, and click the Edit button.
Step 7: There will already be a string of locations here; navigate to the very end, and add the following text (assuming that you have chosen C:\Android-adb as the folder; otherwise, enter whatever path you’ve located adb at):
;C:\Android-adb
Click OK, finally.
Your ADB folder is now configured, and you can run both ADB and Fastboot commands from anywhere in command prompt. To verify, connect your Android device to PC with USB Debugging enabled, launch a command prompt window, and type “adb devices” (without quotes). The daemon will start up, and all connected devices will be listed.
Mac Instructions
http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx/
Pc Instructions
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
Now that ADB is installed. If you find yourself in a Bootloop, OR you find yourself in a situation where it wont pass by the boot animation, open up terminal or command prompt. Then type Adb Devices, it should recognize your device and list the serial. And from there you can use the command:
Adb Reboot Recovery
From there you can wipe/Factory Restore and then Flash a new rom.
If you cannot reboot recovery but ADB still sees your phone. You can use command ADB shell to open a linux command prompt through your phone to push and pull files. Ive done this to push roms when the phone wouldnt mount properly.
I know this isnt "THAT" thorough, however ADB has litterally saved my ass a BUNCH of times. Id reccomend setting it up if you flash frequently.
Sorry it took me a couple days to respond, i am not on XDA as much as i used to be.
RE:
Thanks for documenting this.
So any solutions/ideas to people who can't get our computer's to recognize our device? Unfortunately, that's the position I'm in
EDIT:
I was trying to reflash JB 4.3 because of storage issues but unfortunately I accidentally deleted and formatted internal and sd storage, so Im left with no OS on my Gnex but I can boot on recovery and fastboot. Also before I deleted the internal I did not enable usb debugging yet at that time. Is there a way I can flash a stock image by just using toolkit? ty
I tried pushing through fastboot mode but it says error: device not found. I only have the platform tools on my pc.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
lastforone said:
Instead of using a toolkit, just push a file to ur sdcard using adb and flash it... Or you can download the official image, boot into fastboot and flash it..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well then i need to download sdk first ty anyways
lolobabes said:
well then i need to download sdk first ty anyways
Click to expand...
Click to collapse
You do not need the whole sdk package. Just the adb + fastboot and few required files ... You can find the zip in erants guide..
Sent from my Galaxy Nexus using xda app-developers app
when i tried to push error device not found lol
lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Use adb sideload from twrp and send the zip from your PC to your phone.
Sent from my Galaxy Nexus using xda app-developers app
lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Beauenheim said:
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
Click to expand...
Click to collapse
When I am on recovery yes theres an exclamation on samsung mtp device but in fastboot mode the samsung mtp does not appear but when I do fastboot devices there appears a device number so I thought I can do it on fastboot. thank you.
beekay201 said:
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Click to expand...
Click to collapse
I have read that already however I was hoping to just flash a file to the sdcard if is even possible considering I have formatted both internal and sdcard. I am very new to adb so its an easier way for me. But it seems then I will ave to do it the hard way. Thanks
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
lolobabes said:
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
Click to expand...
Click to collapse
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
sui785 said:
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
Click to expand...
Click to collapse
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
Take it out of a USB 3.0 port.
lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
lolobabes said:
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
Click to expand...
Click to collapse
no, there's no ADB interface on FASTBOOT interface. You'll never be able to push anything through ADB in FASTBOOT interface. Please read the thread i talked about earlier, and this one too -> http://forum.xda-developers.com/showthread.php?t=1626895 - Just the first post of each will do.
Beauenheim said:
Take it out of a USB 3.0 port.
Click to expand...
Click to collapse
*EPIC*
*facedesk*
*grows more white hair*
xD I actually had this issue a few days ago, had issues for 4 hours, realized I had my cord plugged in a 3.0 port.
Really dumb noob moment.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
lolobabes said:
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Click to expand...
Click to collapse
I'm glad you sorted it out, that's the thing instead of teaching you step by step just left a hint on what you should do, helps you learn to do it on your own..
Peace,
L4.1
Thanks
Thanks for this. Was stuck with no factory image because had to wipe data because of encryption. Then was in dilemma of how to load the ZIP to sdcard without having to reflash the stock all over. This saved me the time. Thanks again