Related
YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
*Also note that not all sections will apply to you. I have tried to seperate different senerios using * at each one. Also more then one section here may be needed by you.
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, s-on, and post OTA, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Thank you, really, for taking the time to write this guide. I shared that dreadful feeling of a brick a little while ago, but made it out alive. I know this will help a lot of people.
I'm not bricked, semi bricked or none of that. Rootrd and running BB 0.3
This is the best guide to everything you would need. Too bad you can't post this at the beginning of every thread or some kind of link on every page. This would answer a lot of question if some people would look hard enough. I'm not some smart phone guy by no means. I just read a lot before I ask. In my further reading I can direct people.with further problems here.
Thanks for all your work and giving me another fun hobby
Peace
Sent from my T-Mobile G2 using XDA App
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Good point . Not sure on that one
Sent from my T-Mobile G2 using XDA App
renn9420 said:
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
if you look where im saying /mmcblk0p21 we are replacing RECOVERY with CWM. i do that because i just dont like the idea of trying to replace hboot from a looping system. worst case something goes wrong, you still have hboot and you can try again. screw up hboot, game over! then once android is back up and running we worry about hboot on mmcblk0p18.
you should not state that steps can be changed if people are brave, someone is going to sip parts and cry that their hboot is boned and now they have a BRICK, this is the best post i have seen in the G2 section thus far and i have been through almost every thread(with any kind of importance) in the dev section and 90% of them in general and Q&A. thank you for this post and let's hope people READ at least 5 times before even starting on this.
Gotcha
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Amazing guide, thanks a lot.
fastludeh22 said:
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
Click to expand...
Click to collapse
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
reycat said:
Amazing guide, thanks a lot.
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
Click to expand...
Click to collapse
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
{golf clap} on the post.
you sir, have incredible patience... and it's truly appreciated.
fastludeh22 said:
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
Click to expand...
Click to collapse
Mmm... It seems all of it is quite a bit over my head.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
Click to expand...
Click to collapse
Don't ask me how I did it, but I actually downloaded a web page instead of the actual hboot file I should have used . I did it from the phone and didn't notice. Since I was supposed to rename it to make the typing easier, I didn't notice it was the wrong file.
Anyway, right now the phone is a complete brick. It doesn't respond to any button presses, the LED doesn't do anything when you plug in the charger... A complete brick.
Device offline?
fastludeh22 said:
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Click to expand...
Click to collapse
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
-FuRBz- said:
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
Click to expand...
Click to collapse
Download and instal PDANet, that gave me the drivers i needed for adb, now if only i could figure out how to get my device to register online through the ADB command interface.....
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
marley097 said:
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
Click to expand...
Click to collapse
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
-FuRBz- said:
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
Click to expand...
Click to collapse
Glad you got it! After drivers installed, did you fix it per a section of the op?
it all happened because i had tried flashing cm 6.1- it got stuck on the splash screen but i had done a recovery prior to trying to flash... once i got the drivers installed i was able to get in to adb and do a reboot-bootloader and was able to get into the recovery file
fastludeh22 said:
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
Click to expand...
Click to collapse
Lame....so how often do they release official pic10img's....? are we talkin a month....or a year?
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.
So I was loading a new cm9 rom last night and everything seemed fine until reboot now its stuck at the roms boot screen...
So I attempted to get it to reboot to recovery or fast reboot no dice...
went through all the forums and couldnt get anythign to work...
adb devices sees my kindle fine...
i can adb shell and do a ls and it see directorys and i can cd to a different directory...
and time i try too do the commands to push fbmode or any of that i always get
failed to copy 'fbmode' to '/data/local/temp': No such file or directory
if i try to put it in a different directory or mkdir through shell i get an error for read-only file system
someone please help me out here...
First of all, what recovery are you using?
Bornxero said:
So I was loading a new cm9 rom last night and everything seemed fine until reboot now its stuck at the roms boot screen...
So I attempted to get it to reboot to recovery or fast reboot no dice...
went through all the forums and couldnt get anythign to work...
adb devices sees my kindle fine...
i can adb shell and do a ls and it see directorys and i can cd to a different directory...
and time i try too do the commands to push fbmode or any of that i always get
failed to copy 'fbmode' to '/data/local/temp': No such file or directory
if i try to put it in a different directory or mkdir through shell i get an error for read-only file system
someone please help me out here...
Click to expand...
Click to collapse
/data/local/tmp not /data/local/temp
soupmagnet said:
First of all, what recovery are you using?
Click to expand...
Click to collapse
think i was using cwm cant remember for sure but i cant get it to boot into anything but the cm9 bootscreen...
and tmp vs temp doesnt matter...all directories show either no such directory or read only system
Bornxero said:
think i was using cwm cant remember for sure but i cant get it to boot into anything but the cm9 bootscreen...
and tmp vs temp doesnt matter...all directories show either no such directory or read only system
Click to expand...
Click to collapse
It is important to know because the newer ICS roms won't work with CWM, only TWRP.
from the screenshots ive seen of twrp looks like it was cwm...I just want to be able to restore to stock first then I'll do another rom via twrp...
I previously loaded the hellfire ICS without issue as well...
Hey is it a 3.0 kernel from like energy's, I ,may have your answer then. I just need to know if thats the issue you are having.
Sent from my Amazon Kindle Fire using Tapatalk 2
Bornxero said:
I previously loaded the hellfire ICS without issue as well...
Click to expand...
Click to collapse
How recently? Trust me, from what I've seen here, you need TWRP. None of the 3.0 kernel based ICS roms work well or at all with CWM these days, including Hellfire.
Bornxero said:
So I was loading a new cm9 rom last night and everything seemed fine until reboot now its stuck at the roms boot screen...
So I attempted to get it to reboot to recovery or fast reboot no dice...
went through all the forums and couldnt get anythign to work...
adb devices sees my kindle fine...
i can adb shell and do a ls and it see directorys and i can cd to a different directory...
and time i try too do the commands to push fbmode or any of that i always get
failed to copy 'fbmode' to '/data/local/temp': No such file or directory
if i try to put it in a different directory or mkdir through shell i get an error for read-only file system
someone please help me out here...
Click to expand...
Click to collapse
I would try to use KF utility which is very useful for all kinds of issues with KF and very easy to use. It has helped me a great deal.
Yea its was a 3.0 kernel...gedeROM..
forest1971 said:
I would try to use KF utility which is very useful for all kinds of issues with KF and very easy to use. It has helped me a great deal.
Click to expand...
Click to collapse
I deff. tried everything in the kindle unbrick utility if thats what your talking about...
Bornxero said:
I deff. tried everything in the kindle unbrick utility if thats what your talking about...
Click to expand...
Click to collapse
I'm guessing you still have the stock bootloader ("kindle fire" bootlogo when the device first powers up) or you would have gotten yourself to recovery already. You'll want to try and get the bootmode changed to recovery and reboot like this...
Code:
adb shell idme bootmode 5001
adb reboot
If you can get back to CWMR, the first thing you should do is flash a new bootloader... probably FFF 1.4a that you can find in the dev section. Then use that to get into fastboot mode and flash TWRP.
If you cannot change bootmodes through adb. You'll have to push fbmode or rcmode in some writeable directory. I'm guessing /data/local/tmp doesn't exist in CM9, so try pushing it to /data instead.
If none of that works and my guess about your bootloader is right, you're going to need a factory cable.
kinfauns said:
I'm guessing you still have the stock bootloader ("kindle fire" bootlogo when the device first powers up) or you would have gotten yourself to recovery already. You'll want to try and get the bootmode changed to recovery and reboot like this...
Code:
adb shell idme bootmode 5001
adb reboot
If you can get back to CWMR, the first thing you should do is flash a new bootloader... probably FFF 1.4a that you can find in the dev section. Then use that to get into fastboot mode and flash TWRP.
If you cannot change bootmodes through adb. You'll have to push fbmode or rcmode in some writeable directory. I'm guessing /data/local/tmp doesn't exist in CM9, so try pushing it to /data instead.
If none of that works and my guess about your bootloader is right, you're going to need a factory cable.
Click to expand...
Click to collapse
w00t solved thanx....i was crying over here lol...
used this to put back the old rom I was using then used KFU to install twrp and installed the new rom without issue....
thanx again....
Folks, i really don't know what to do to get a specific problem log file to be sent/showed to someone to fix my problem, any help or suggestions will be really appreciated here
If you just had a hard reboot, once booted up, from pc
Adb pull /proc/last_kmsg
This will get last kmsg file related to the last boot session to your pc.
If no hard reboots but freezes etc, then
Adb shell dmesg > /sdcard/dmesg.txt
To see what's been going on since the boot at kernel level. File gets created on sdcard. Use
Adb pull /sdcard/dmesg.txt
To get it to your pc.
To get a log of something, before trying it, start the logcat with
Adb logcat > logcat.txt
File will be created on the pc.
This is from my post 6843 in official cm10 thread. You can also use
Adb shell cat /proc/kmsg > /sdcard/kmsg.txt
To see kernel logs since last boot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Edit: /proc was missing 3 lines above
eyosen said:
If you just had a hard reboot, once booted up, from pc
Adb pull /proc/last_kmsg
This will get last kmsg file related to the last boot session to your pc.
If no hard reboots but freezes etc, then
Adb shell dmesg > /sdcard/dmesg.txt
To see what's been going on since the boot at kernel level. File gets created on sdcard. Use
Adb pull /sdcard/dmesg.txt
To get it to your pc.
To get a log of something, before trying it, start the logcat with
Adb logcat > logcat.txt
File will be created on the pc.
This is from my post 6843 in official cm10 thread. You can also use
Adb shell cat /kmsg > /sdcard/kmsg.txt
To see kernel logs since last boot.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
thanks eyosen you are the best
what if i already rebooted it several times due to weird signal loss? please check this http://forum.xda-developers.com/showthread.php?p=32791585#post32791585
does this means i've lost the latest log? if no, then how to extract the specific problem log from it such as the signal loss? or shall i send the whole log?
Hossam.Abdelsalam said:
thanks eyosen you are the best
what if i already rebooted it several times due to weird signal loss? please check this http://forum.xda-developers.com/showthread.php?p=32791585#post32791585
does this means i've lost the latest log? if no, then how to extract the specific problem log from it such as the signal loss? or shall i send the whole log?
Click to expand...
Click to collapse
use "adb logcat -b radio"
Press the thanks button if you want to thank me
You are welcome.
Just send the whole log. Best practice is to post it to pastebin and post the link in the forum.
After every reboot you will lose the previous last_ksmg.
Sent from a gadget on my balcony.
wcypierre said:
use "adb logcat -b radio"
Press the thanks button if you want to thank me
Click to expand...
Click to collapse
i already pressed it
but it seems this shows you the log at the run time, but what am trying to get is the log of my weird signal loss for incidents happened yesterday, is this even possible?
No that's not possible. You can start a logcat, repeat the steps that caused the problem, after the problem , post logcat and kmsg.
Sent from a gadget on my balcony.
Hossam.Abdelsalam said:
i already pressed it
but it seems this shows you the log at the run time, but what am trying to get is the log of my weird signal loss for incidents happened yesterday, is this even possible?
Click to expand...
Click to collapse
well, it should be able to trace back if the time duration is not that long, but you can just try and do what eyosen had suggested
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