Need instuctions for ADB pull cracked screen - Samsung Epic 4G Touch

i have an e4gt screen cracked and i need to get internal sd card data. i have done several searches and have come across ADB pull but not clear on how to perform this. i am rooted w stock 4.1 using whatever recovery came with the stock+rooted ROM. (SPH-D710_GB27_1014481_Rooted_Nodata.tar.md5 from Rwilco12's Android Repository). If I could just remember the exact steps to mount usb from recovery i would be good lol... any suggestions would be greatly appreciated!

Ive the same problem if someone would help.
Sent from my GT-I9300 using xda premium

No need. Just power up your device and connect to your pc. It will connect using mtp and allow you to access your files that way (as long as you hadn't deactivated it prior to cracking your screen.)
Sent from my SPH-D710 using Tapatalk 2

There's a way to get your screen to pc...
Sent from my GT-I9300 using xda premium

hlxanthus said:
No need. Just power up your device and connect to your pc. It will connect using mtp and allow you to access your files that way (as long as you hadn't deactivated it prior to cracking your screen.)
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
i have done that and i get a box that says "there was a problem installing this MTP device." then another box says MTP was not installed correctly. Well i do have the Samsung drivers installed. Even installed a fresh copy direct from samsung support. Maybe something to do with my screen being locked with pin? Just got the Galaxy4 cant wait to get my data back...lol

Okay, assuming you already have android SDK set up and working ( you get adb this way), flash a recovery. I would likely use the direct boot for simplicity.
http://www.rwilco12.com/downloads.p...overy Kernels/GB/Noobnl Direct Boot/One-Click
That is for the one click version of the direct boot kernel/recovery. It is gingerbread based, but that shouldn't matter if it will boot the ROM later a due to kernel mismatch due to the broken screen lol.
Give it some time too verify you are in the recovery. Now the magic. Find where your adb is at, usually within android/platform_tools if memory serves. You can do a system search for adb and it should pop up. Move to that location. Make a note of the exact path to that location. Now open a command prompt (search for cmd.exe). You then need to switch to the location of your adb. It should be something like the "cd c:/path/to/adb" (no quotes) where you fill in the path you noted earlier. Once there, give this a go. Type "adb devices" (again no quotes) and if you get a string of numbers that means you have adb access!!! Then you can just type "adb pull /sdcard/" and that will drop the contents of your internal storage into the folder holding your adb files (kind of a mess but it is the easiest way to do it). If you would rather it be dropped in a location of your choosing, use this "adb pull /sdcard/ /path/to/desired/location/" and note there is a space between /sdcard/ and your path to desired location.
I am not expert at this, but let me know if you get stuck somewhere in this and I will try to help.
Sent from my Nexus 7 using Tapatalk 2

Hi thanks for the detailed response. i will need to make some time to go through these steps lol however i will update!

Related

[Q] Soft bricked during de-CIQ, ACSRecovery won't load

Hey guys,
Was trying to de-Carrier IQ my phone today when I made a serious rookie mistake. I renamed the following two files and rebooted, and now only get the "Samsung" logo at boot:
/system/lib/libiq_client.so -> libiq_client_old.so
/system/lib/libiq_service.so -> libiq_service_old.so
I also renamed the "/system/bin/iqmsd" daemon (to iqmsd_old), set "setprop service.iq.active 0", and "pm disabled" the various CIQ services but I don't think these changes are related (successfully rebooted afterwards).
My restore plan was to flash ACSRecovery5 using Odin (not previously loaded) and then mount the /system directory, renaming those libraries (.so's) back to their original names. While Odin reports success in flashing ACSRecovery ("ACSRecovery5-1.0.0.0-epic4g.tar.md5" under PDA), when I boot into recovery mode (VolDown-Camera-Pwr) the stock Samsung recovery menu still appears :-( Also tried experimenting with ADB--"adb devices" reports the phone as "offline" during normal boot (where it freezes at the Samsung logo) and doesn't even show the device in download or recovery modes.
PHONE DETAILS:
Samsung Epic 4G (Sprint)
Stock Eclair (DI18)
Rooted using z4root
Apps + Data backed up to SDCard via TitaniumBackup (not sure if this captured my SMSs and notes)
Trying to avoid a wipe/flash back to stock (trying to preserve SMSs and notes) but realize this might be the only option. Much thanks to all who help.
You didn't run a nandroid backup before this?
Sent from my SPH-D700 using XDA App
Sadly no, I didn't even have Clockwork Recovery / ACSRecovery loaded. Thanks for your response!
Have you tried using an adb shell to push those files back?
Sent from my SPH-D700 using XDA App
Hmm...I'm a bit new to adb, but when I try adb pull /system/lib/libiq_client_old.so it returns error: device offline. Same with other adb commands. Thanks again!
tvh2k said:
Hmm...I'm a bit new to adb, but when I try adb pull /system/lib/libiq_client_old.so it returns error: device offline. Same with other adb commands. Thanks again!
Click to expand...
Click to collapse
Sounds like USB debugging was off or a bad cable. Also try other usb ports.
Sent from my SPH-D700 using XDA App
Possible USB debugging was off, though I do remember turning it on at some point in the past. Not sure how far in the boot process it needs to go before it can respond to adb commands. Is there a way to get a console-type debug output as it boots?
Will try other cables once I get home. Thanks for your persistence
Fixed!
New cable didn't work, but was able to load CWM Recovery and mount /system via adb. Thanks again for your help
what about odin back to stock ec05?
Sent from my SPH-D700 using Tapatalk
I bet you tried to use one of those detection/removal apps in the Market, rather than using k0nane's flashable mod for our device.
You honestly would've been better off just flashing a custom rom. If you were trying to stick with something as close to stock as possible, then there are custom options in the dev forum.
Glad you were able to get CWM going again and resurrect the phone.

Need Help ASAP

Sorry if this is the wrong thread.
The run down. My phone is bootloader unlocked rooted etc. already flashed xenon rom and everything was great. (Just got the device today)
Ok so here's the trouble i'm in. I decided I wanted to try another rom so i boot into clockwork recovery wipe system,data cache etc. suddenly all my files dont exist.
I have no back up file (my stupidity). I can still get into fastboot, clockwork etc, but it does not recognize a sd card on the device.
i tried loading up Samnsung Toolkit v7.8.0 and all i see in the top menu is
fastboot-toolkit is not recognized as an internal or external command operable program or batch file
adb-toolkit is not recognized as an internal or external command operable program or batch file
this is what worries me. I plug the device in on my windows computer it recognizes something no sd card.. currently downloading factory images
BUT WHAT DO I DO?!!!! pls help and pls do not flame me etc. All I'm asking is simple help thanks
http://forum.xda-developers.com/showthread.php?t=1626895
A. Do not use toolkit. Unless you know how to solve things manually
B. Google how to setup adb and fastboot.
C. "adb push NAME_OF_ROM.zip /sdcard/" while on custom recovery
D. Flash that ROM
kyokeun1234 said:
A. Do not use toolkit. Unless you know how to solve things manually
B. Google how to setup adb and fastboot.
C. "adb push NAME_OF_ROM.zip /sdcard/" while on custom recovery
D. Flash that ROM
Click to expand...
Click to collapse
thank you will try that...question when i goto recovery mode its clockwork...when i hit mount sdcard nothing happens.
kyokeun1234 said:
A. Do not use toolkit. Unless you know how to solve things manually
B. Google how to setup adb and fastboot.
C. "adb push NAME_OF_ROM.zip /sdcard/" while on custom recovery
D. Flash that ROM
Click to expand...
Click to collapse
also when tryin to access card via clockwork it states it cannot located directory...its like my sdcard does not exist
There is no sdcard on the gNex. As long as data is mounted you should be good
Sent from my Galaxy Nexus using Tapatalk 2
1st of all, Gnex doesn't have SDcard, therefore, you can't mount it. You can only use adb to push and pull files on recovery
2nd, are you sure you got proper driver? Do you actually have the ROM.zip on the same directory as adb.exe? If not, you need to do that. Also, if /sdcard/ doesn't work, /storage/sdcard0/ should work. It's a same directory. Just in different name for some reason.
3rdstring said:
There is no sdcard on the gNex. As long as data is mounted you should be good
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
just wanna say thanks guys!!!. i tried pushing as filename which pushed but still couldnt find it...decided to name the file update.zip and push then flash update zip and bang it worked i'm back up..dont know why my files disappeared but whatever i'm back up so i'm happy..thanks again
Gnex was a pain to get all the drivers installed, once they are Its a breeze to work with
Sent from my Galaxy Nexus using xda premium
daeshawn said:
just wanna say thanks guys!!!. i tried pushing as filename which pushed but still couldnt find it...decided to name the file update.zip and push then flash update zip and bang it worked i'm back up..dont know why my files disappeared but whatever i'm back up so i'm happy..thanks again
Click to expand...
Click to collapse
Just glad we helped
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
rsswga said:
Gnex was a pain to get all the drivers installed, once they are Its a breeze to work with
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
+1
Sent from my Galaxy Nexus

Erased everything. Stuck in recovery with no rom. Help?

So I screwed up, wasn't paying attention and wiped everything including the internal sd card. Now I'm stuck in recovery with no rom to flash. I tried mounting usb storage in recovery but nothing happens. My computer dings when I plug the phone in but it doesn't show up, then I press mount and nothing happens. Any ideas?
Sent from my SCH-I535 using Tapatalk 2
Guide in my signature.
Post one for ADB.
Post three for pushing a ROM.zip to your phone.
You can use ADB to push a ROM .zip to the internal storage while in the recovery.
Ok awesome, thanks guys. For a minute I was thinking I might be screwed since I couldn't mount.
Sent from my SCH-I535 using Tapatalk 2
ajk511 said:
Ok awesome, thanks guys. For a minute I was thinking I might be screwed since I couldn't mount.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ADB and fastboot can usually save your ass.
Ok, downloaded latest drivers, reinstalled ADB using the ADB for dummies app. copied rom to platform tools, held shift and right clicked inside the platform tools folder, clicked "open command window here".
In the command window I have after trying to push looks like this:
C:\android-sdk-windows\platform-tools>adb push milestone4.zip /sdcard/
error: device not found
C:\android-sdk-windows\platform-tools>
Any idea how to get my device to be found?
ajk511 said:
Ok, downloaded latest drivers, reinstalled ADB using the ADB for dummies app. copied rom to platform tools, held shift and right clicked inside the platform tools folder, clicked "open command window here".
In the command window I have after trying to push looks like this:
C:\android-sdk-windows\platform-tools>adb push milestone4.zip /sdcard/
error: device not found
C:\android-sdk-windows\platform-tools>
Any idea how to get my device to be found?
Click to expand...
Click to collapse
You have your phone connected and booted into recovery? Then you need to install the adb driver. Use the naked driver mentioned in the 101 & faq (link is in my signature).
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
You have your phone connected and booted into recovery? Then you need to install the adb driver. Use the naked driver mentioned in the 101 & faq (link is in my signature).
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Still not getting anything.
ajk511 said:
Still not getting anything.
Click to expand...
Click to collapse
Open the device manager before plugging in your phone. Plug in your phone watch for newly listed devices. You should see your phone be added to the list.
Petrovski80 said:
Open the device manager before plugging in your phone. Plug in your phone watch for newly listed devices. You should see your phone be added to the list.
Click to expand...
Click to collapse
Got it going now, in installed in device manager and reinstalled. Thanks for all the help man.
Sent from my SCH-I535 using Tapatalk 2

Pushing ROM using ADB! Help!

Alright so I was an idiot and wiped data and internal storage...I figured I could just mount the phone like I could my Thunderbolt, but apparently not. I have adb installed and currently been going to platform-tools folder and opening command window...type adb devices and it shows my device in recovery...which is good. However as soon as I try to do "adb push C:\android-sdk-windows\platform-tools\baldwinguy77_toro_aosp_011913-120824-signed.zip" and it doesn't do anything and just scrolls through all the available commands you can do...I have tried multiple variations of that and nothing seems to work. Help me please, as I need my phone working and I have been trying to figure this out for about an hour now.
CC268 said:
Alright so I was an idiot and wiped data and internal storage...I figured I could just mount the phone like I could my Thunderbolt, but apparently not. I have adb installed and currently been going to platform-tools folder and opening command window...type adb devices and it shows my device in recovery...which is good. However as soon as I try to do "adb push C:\android-sdk-windows\platform-tools\baldwinguy77_toro_aosp_011913-120824-signed.zip" and it doesn't do anything and just scrolls through all the available commands you can do...I have tried multiple variations of that and nothing seems to work. Help me please, as I need my phone working and I have been trying to figure this out for about an hour now.
Click to expand...
Click to collapse
Use side load.
Cwm : reboot recovery > install zip from side load.
In adb > using the side load command ( refer syntax on phone screen, when pH is in side load mode.)
Press thanks if helped
Sent from my Galaxy Nexus using xda app-developers app
Ashwa said:
Use side load.
Cwm : reboot recovery > install zip from side load.
In adb > using the side load command ( refer syntax on phone screen, when pH is in side load mode.)
Press thanks if helped
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I am using TWRP btw...how do I use sideload?? I see it in TWRP...but do I open command prompt and do something special??
EDIT: Ahh...finally figured it out and it installed the ROM! Thanks
CC268 said:
Alright so I was an idiot and wiped data and internal storage...I figured I could just mount the phone like I could my Thunderbolt, but apparently not. I have adb installed and currently been going to platform-tools folder and opening command window...type adb devices and it shows my device in recovery...which is good. However as soon as I try to do "adb push C:\android-sdk-windows\platform-tools\baldwinguy77_toro_aosp_011913-120824-signed.zip" and it doesn't do anything and just scrolls through all the available commands you can do...I have tried multiple variations of that and nothing seems to work. Help me please, as I need my phone working and I have been trying to figure this out for about an hour now.
Click to expand...
Click to collapse
cd C:\android-sdk-windows\platform-tools\
adb push baldwinguy77_toro_aosp_011913-120824-signed.zip /sdcard/
You didn't specify the destination.
Sent from my i9250
Ashwa said:
Use side load.
Cwm : reboot recovery > install zip from side load.
In adb > using the side load command ( refer syntax on phone screen, when pH is in side load mode.)
Press thanks if helped
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
bk201doesntexist said:
cd C:\android-sdk-windows\platform-tools\
adb push baldwinguy77_toro_aosp_011913-120824-signed.zip /sdcard/
You didn't specify the destination.
Sent from my i9250
Click to expand...
Click to collapse
But why put /sdcard on the end if there is no sdcard?? By the way I got it to work but didnt put the sdcard on the end
CC268 said:
But why put /sdcard on the end if there is no sdcard??
Click to expand...
Click to collapse
.... Please do some research.
CC268 said:
By the way I got it to work but didnt put the sdcard on the end
Click to expand...
Click to collapse
Through adb? I find that hard to believe, unless you specified another destination.
Sent from my i9250

[q] SOLVED: ADB ROM PUSH ERROR: DEVICE NOT FOUND

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

Categories

Resources