Related
I recently purchased an LG Phoenix by At&t, the problem I have is that I cannot leave ClockworkMod Recovery v5.0.2.0
I rooted it, restarted in recovery. and everything worked fine. I then upgraded my firmware, not sure what version though.. I backed up my phone before I upgraded into the new firmware. I then backedup my phone because it rebooted into recovery. Now everytime it boots it goes straight to Clockwork and I cant get out of it. I restored to my previous restore and it still doesn't work. What could I do? Should I install cwr 3? I read that cwr 5 has bugs and is known to brick phones..
Edit: Also the phone without the sd card still boots into clockworkmod menu
I have a ROM(Phoenix ULTIMATE) I'd like to flash but I'm not sure if I should right now considering I'm stuck at this menu.
Info- in my restores It says;
2011-10-04.21.37.48/
2011-10-04.21.56.13/
I'v tried both.
Another edit with potentially important info getting an error stating;
E: bad boot message "recovery"
Sorry If this is a n00b post.. I'm in sort of a rush because I'm moving in a few hours!
Edit; tried flashing the phoenix, didnt work.
installation was aborted
said i needed to switch to Edify scripting, and amend scripting is no longer supported.
What could I flash too to fix this, please help. I don't care if I lose data. Just need my phone back soon.
I have android SDK.
I was reading up on http://developer.android.com/guide/developing/tools/adb.html and http://forum.xda-developers.com/showthread.php?t=517874 here
Would I be-able to push somesort of boot file or firmware to my phone? Or something in that manner?
THIS:
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
Seems to be perfect for what I should try, where could I get the stock imgs for my phone? (p505)
I moved this here temporarily for you to be assisted...after that it will be moved beck to the right forum
Good luck!!
M_T_M said:
I moved this here temporarily for you to be assisted...after that it will be moved beck to the right forum
Good luck!!
Click to expand...
Click to collapse
thanks
Really hope I can get this fixed soon.
Xery said:
I recently purchased an LG Phoenix by At&t, the problem I have is that I cannot leave ClockworkMod Recovery v5.0.2.0
I rooted it, restarted in recovery. and everything worked fine. I then upgraded my firmware, not sure what version though.. I backed up my phone before I upgraded into the new firmware. I then backedup my phone because it rebooted into recovery. Now everytime it boots it goes straight to Clockwork and I cant get out of it. I restored to my previous restore and it still doesn't work. What could I do? Should I install cwr 3? I read that cwr 5 has bugs and is known to brick phones..
Edit: Also the phone without the sd card still boots into clockworkmod menu
I have a ROM(Phoenix ULTIMATE) I'd like to flash but I'm not sure if I should right now considering I'm stuck at this menu.
Info- in my restores It says;
2011-10-04.21.37.48/
2011-10-04.21.56.13/
I'v tried both.
Another edit with potentially important info getting an error stating;
E: bad boot message "recovery"
Sorry If this is a n00b post.. I'm in sort of a rush because I'm moving in a few hours!
Click to expand...
Click to collapse
Are you on Ecliar , Froyo or Gingerbread ? Sorry , I don't know much but I would like to help
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
Are you on Ecliar , Froyo or Gingerbread ? Sorry , I don't know much but I would like to help
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
I didn't change anything, everything is stock I got it yesterday. Rooted it today and it's stuck in recovery. So I guess whatever stock is..
Xery said:
I didn't change anything, everything is stock I got it yesterday. Rooted it today and it's stuck in recovery. So I guess whatever stock is..
Click to expand...
Click to collapse
Try adb .
(If you know what it is)
Type these in:
adb shell
su
reboot bootloader
See if it works
Forever living in my Galaxy Ace using XDA App
I don't know what adb is. :c
Could you explain a bit more about it?
Xery said:
I don't know what adb is. :c
Could you explain a bit more about it?
Click to expand...
Click to collapse
Okay then .
Download and install the Android SDK Tools first
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
Okay then .
Download and install the Android SDK Tools first
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
OH Android SDK I have that, just updating.. another 30 minutes..
While we wait, could you explain to me what I'd do with it, and just some tips or things I could do?
Xery said:
OH Android SDK I have that, just updating.. another 30 minutes..
While we wait, could you explain to me what I'd do with it, and just some tips or things I could do?
Click to expand...
Click to collapse
If you have platform-tools , everything will be done in a flash
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
If you have platform-tools , everything will be done in a flash
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
"Installed Android SDK Platform-tools, revision 7"
Still installing a bunch of other things though..
"Downloading SDK Platform Android 3.2, API 13, revision 1"
Probably won't be done till tomorrow, horrible internet.
Xery said:
"Installed Android SDK Platform-tools, revision 7"
Still installing a bunch of other things though..
"Downloading SDK Platform Android 3.2, API 13, revision 1"
Probably won't be done till tomorrow, horrible internet.
Click to expand...
Click to collapse
All you need now is platform-tools . The rest can be cancelled .
Use cmd (best if used with administrative rights) to navigate to the Android SDK folder , then to platform-tools .
Once you get there , connect your phone through USB then don't touch it .
In cmd , type:
abd shell
su
reboot bootloader
Forever living in my Galaxy Ace using XDA App
EmoBoiix3 said:
All you need now is platform-tools . The rest can be cancelled .
Use cmd (best if used with administrative rights) to navigate to the Android SDK folder , then to platform-tools .
Once you get there , connect your phone through USB then don't touch it .
In cmd , type:
abd shell
su
reboot bootloader
Forever living in my Galaxy Ace using XDA App
Click to expand...
Click to collapse
How would I use the cmd to navigate to the SDK folder?
I see the cmd, I also see a window called Android SDK and AVD manager, What now?
Xery said:
How would I use the cmd to navigate to the SDK folder?
I see the cmd, I also see a window called Android SDK and AVD manager, What now?
Click to expand...
Click to collapse
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\platform-tools
Then this
adb shell
reboot bootloader
cdesai said:
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\tools
Then this
adb shell
reboot bootloader
Click to expand...
Click to collapse
Follow his instructions .
Forever living in my Galaxy Ace using XDA App
cdesai said:
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\tools
Then this
adb shell
reboot bootloader
Click to expand...
Click to collapse
I opened the cmd, I'm not really suer where I installed SDK but I'm pretty sure it was c:\program files\android\android-sdk\tools
That seemed to work, whenever i type adb shell it says abd is not recognized as an internal or external command, program or batch.
I need more detail because I'm a noob. :/
cdesai said:
Do this
Hold start button and R(on desktop)
Run will open
Type cmd in the box and press enter
A black window will open
CD to sdk dir
E.g.
If u installed sdk in C:\sdk
Then do this
cd C:\sdk\tools
Then this
adb shell
reboot bootloader
Click to expand...
Click to collapse
I opened the cmd, I'm not really suer where I installed SDK but I'm pretty sure it was c:\program files\android\android-sdk\tools
That seemed to work, whenever i type adb shell it says abd is not recognized as an internal or external command, program or batch.
I need more detail because I'm a noob. :/
EDIT: GOTIT! got the dir, i typed adb and it says device not found should i connect my phone correct?
Edit: okay,i did that, it just rebooted my phone and it went back into the CWR.. :c wut now?
Are you able to try and boot into bootloader? Try that. Also, try and flash a new ROM in recovery, test to see if it may be the ROM. Don't be afraid to backup again, you can always access the backups based on date.
-How cruel is the golden rule, when the lives we live are all golden plated-
What's bootloader?
I tried to flash my backups before the firmware update and it didn't work, I also can't find any wp505 roms.. I found a few but they wont help in my situation. Do you know any? My rom is stock as I only rooted and got stuck in cwr.
Thanks!
EDIT: I did do that adb shell, reboot bootloader, didnt work.
Xery said:
What's bootloader?
I tried to flash my backups before the firmware update and it didn't work, I also can't find any wp505 roms.. I found a few but they wont help in my situation. Do you know any? My rom is stock as I only rooted and got stuck in cwr.
Thanks!
Click to expand...
Click to collapse
First off, not to lecture you...but you definitely should look into these kind of things before flashing a ROM.
I haven't looked at the ROMs so I'm not sure. But whatever fancies you, it's just to troubleshoot the problem. The problem itself may actually be the recovery. Do you know how to do logcats in ADB? Try and do a logcat and boot up your device while connected to ADB.
So go "adb logcat". This should show you exactly what your device is doing. When it runs and goes straight to recovery paste all that information into a .txt document and upload it onto xda so others can take a look.
I'll try and help more tomorrow but I have to get some rest. Good luck on getting this fixed.
-How cruel is the golden rule, when the lives we live are all golden plated-
can you help me fix this problem
after wipe all data, cache and anotherthing wipe (it's name very hard to remember ).
I cant use recovery mode, my phone can open fastboot and bootloader, but can't open recovery mode (it's only show a android logo when i press "recovery")
please help me (
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
justflikwalk said:
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
Click to expand...
Click to collapse
can you show me more, i dont know adb commands, and push new recovery is "recovery clockwork" and "recovery RA". I tried apply them, but it's not work,may be i wrong in some thing, it's the first time i use android phone . throught usb, i have "fastboot usb"
please help me
http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide
but my phone cant connect with PC, atlthough i installed google usb driver.
i might be wrong but cant you just flash a original ruu, than root and reinstall recovery
#1)Go and download yourself a recovery.img file that is compatible with your device and put the image on the root of your SD card (that means on the main directory and not in a folder)
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
#3)Open up your terminal and type in
Code:
su
to gain root access. If you are root the next line should show the
Code:
# symbol
#4)At the next line type in
Code:
flash_image recovery /sdcard/name-of-recovery.img
you will need to replace the code that says name-of-recovery.img with the exact name of the file on your SD card.
#5)Hit enter, wait a few seconds and viola ! you have a recovery again.
Good luck man.
hxq88 said:
but my phone cant connect with PC, atlthough i installed google usb driver.
Click to expand...
Click to collapse
Try the driver from this thread.
It helped me set up my ADB for the N1
http://forum.xda-developers.com/showthread.php?t=613217
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
hxq88 said:
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
Click to expand...
Click to collapse
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
baseballfanz said:
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
Click to expand...
Click to collapse
i typed ADB devices on command prompt, it'show
View attachment 763802
and it's my driver after update from your link
View attachment 763803
what is passimg method, is the way rename room.zip => PASSIMG.zip
You did have debugging turn on correct?
Not sure what else to suggest except the passimg method, worth a shot.
Sent from my Transformer TF101 using Tapatalk
And... if you try to install a stock rom? When starts the HBOOT automatically detect the rom and ask to install. One time you've installed the rom, root & install recovery
I think that work because, It happens to me 1 week ago.
I have Imilika's AOSP ICS ROM V6,
I changed the buid.prop
ro.sf.lcd_density=213
for tablet mode. after I reboot, my GNote is not booting. I cannot go to recovery mode or download mode.
Please help. I don't know what to do
Got it
OK, I was really sad about what happens to my phone, but finally I managed to fix it .
As I told you, my phone was not booting to recovery or download modes (key combinations not worked). finally I try to connect to PC via USB and luckily my PC could detect my phone . So i realized that the problem is the display not coming but phone is halfway booted.
So, I tried to change my build.prop via adb but failed due to cannot grant root permission (becoz display is off).
Finally I issue a adb commad to reboot in recovery mode.
"adb reboot recovery"
yeah, that command directly take me to the CWM recovery. then I flash AOSP v6 again.
Now, my phone is working again.
P.S. I just note this down for others if they get same problem future !
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
If you don't know what ADB is, you probably shouldn't be flashing so regularly. Anyway, ADB stands for "Android Debug Bridge" and it is a protocol for device control, development, and debugging.
Sent from my GT-N7000 using Tapatalk
priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
adb is a connection type. we can run shell commands (in the phone), file transfer via adb by using our PC. for that we should have to enable usb debug mode in our mobile.
Actually you might used adb, when you root your phone in the first place . If you have CF-Root zip file, just extract it. you will see a folder called "files", in there you can see adb.exe .
If you need test run,
connect phone via USB(make sure you've enabled USB debug), open command prompt, navigate to that "files" directory.
run "adb shell ls" (to run "ls" command in phone)
run "adb push <anyfile in the PC> /system/sdcard/" (copy files from PC to sdcard)
like that
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
priyanv said:
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
Click to expand...
Click to collapse
Its functionality is not only to copy files from pc to mobile and vice versa.You can use it to get logs due to bad flashing,zip align apps,reboot into recovery,DL mode,normal reboot etc...
My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
We tried a different computer and solved the ADB problem, then I did just like you told and it's OK now.
Thank you.
You're welcome. glad it's all all OK for you
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Same problem as you --> fixed
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
If you found that adb worked from a different machine, you might check whether you had any tethering drivers installed (eg EasyTether) on the machine that was not able to see the phone via adb. I found that they interfered with adb's operation on my Macbook previously; it was maddening.
woraz said:
My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Click to expand...
Click to collapse
if you have problems always use Hasoon All-In-One_Kit for HTC
Am having the same issues, have tried everything I can think off and everything google has suggested. I'm beyond stuck any and all help would be greatly appreciated
my bad exp
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Was he by chance having issues charging his phone before he wiped it?
Myself and my brother both a had issues with the USB port going. Couldn't charge while phone was on. PC wouldn't pick it up so no adb. However was able to pickup fastboot and charge while in fastboot mode.
If that's the case you could try running a zip in oemRUU mode just to get an os on there.
Is he soff?
Sent from my HTC One using xda premium
makkasi said:
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Click to expand...
Click to collapse
This worked for me. Thanks!!
Once I removed all the extra crap from control panel and used the latest I was able to do adb devices successfully from bootloader / recovery.
I was just having the same problem on the new LG G2 (D803). It was perplexing because the computer *bleeped* every time it attached so I knew that it saw something. Based on the tips here I went to the Device Manager and sure enough there it was... I reinstalled the drivers inside device manager and then I got an easy adb hit on the phone... hmmm :fingers-crossed:
EazyVG said:
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Click to expand...
Click to collapse
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
timekills said:
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
Click to expand...
Click to collapse
Man, I just wanted to say thank you. I've been stuck on this for hours and this did the trick!
Worked
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
the drivers mentioned here worked for me.
Device : HTC One M7
Recovery : TWRP
Thanks
Thank you so much! This universal driver worked for me! (HTC One Mini with TWRP, soft-bricked)
NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
Years later, thank you sir, for helping a noob with "adb kill-server"
I was so freaked as to why TWRP wasn't sideloading but PhilZ was.
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
ADB didn't recognize my Xperia SP in Clockworkmod. That driver worked like a charm Thank you!
This worked for me...
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
Thank you so much for this. This really helped me out.
guys i need support , i want to downgrade my sony from 7.1.1 to 6.0.1 to root and backup that key but i ended up twice with
ERROR - Processing of system.sin finished with errors.
please help , i cant find anything usefull than extract that file and install it , but that wont work if i soft brick it
Do you use the latest Flashtool(0.9.23.2) to flash the FTF file?
If yes, sometimes just flash FTF again right after error occurs may fix the problem.
f870103 said:
Do you use the latest Flashtool(0.9.23.2) to flash the FTF file?
If yes, sometimes just flash FTF again right after error occurs may fix the problem.
Click to expand...
Click to collapse
its sloved, it seems it was a corrupt fileso i dled the koran ver and that worked, thx , the only problem is back up ta, i cant find out howto without losing the drm kry,
i watched a couple youtubes, i readed a few guides but nothing is clear enough how to , i got that script but it say device not found , i tried in dwonload mode and local charging mode
Use this tool to backup your TA partition.
You need to backup it in Android system with adb access, not Download mode or Flash mode.
To check if your computer has adb access, simply type "adb devices" in the command window.
f870103 said:
Use this tool to backup your TA partition.
You need to backup it in Android system with adb access, not Download mode or Flash mode.
To check if your computer has adb access, simply type "adb devices" in the command window.
Click to expand...
Click to collapse
i installed adb and drivers and alot other stuff to get it to work like flashtool and so , but can't seems to get it to work, best i could do is rollback rom
thats why i asked if someone can pass me a guide i can folow and understand, because simple im missing something
i never had it this hard with samsung
would be nice if i had more support on this mather
Wesley_NL said:
i installed adb and drivers and alot other stuff to get it to work like flashtool and so , but can't seems to get it to work, best i could do is rollback rom
thats why i asked if someone can pass me a guide i can folow and understand, because simple im missing something
i never had it this hard with samsung
would be nice if i had more support on this mather
Click to expand...
Click to collapse
I see you have enabled ADB on your device, and connected to your computer. But ADB did not find your device.
Maybe you should re-install your adb driver.
You can download ADB Installer by @Snoop05 here.
After installing ADB driver correctly, you should see your device on adb device list.
f870103 said:
I see you have enabled ADB on your device, and connected to your computer. But ADB did not find your device.
Maybe you should re-install your adb driver.
You can download ADB Installer by @Snoop05 here.
After installing ADB driver correctly, you should see your device on adb device list.
Click to expand...
Click to collapse
i get more details now, so am i good now ?
-edit guess not
Wesley_NL said:
gumm i get more details now, so am i good now ?
Click to expand...
Click to collapse
It's "adb deviceS" not "adb device".
f870103 said:
It's "adb deviceS" not "adb device".
Click to expand...
Click to collapse
oops my bad lol i simply copy pasted missed s
but still not able to see phone i guess ?
Wesley_NL said:
oops my bad lol i simply copy pasted missed s
but still not able to see phone i guess ?
Click to expand...
Click to collapse
Yes. adb still can't find it. Did you try ADB Installer I mentioned before?
f870103 said:
Yes. adb still can't find it. Did you try ADB Installer I mentioned before?
Click to expand...
Click to collapse
uhuh i did,
but i did not install it as admin so i tried again and i guess i have a result now
but in ta still no device found
Wesley_NL said:
uhuh i did,
but i did not install it as admin so i tried again and i guess i have a result now
but in ta still no device found
Click to expand...
Click to collapse
Just type "adb devices" again.
f870103 said:
Just type "adb devices" again.
Click to expand...
Click to collapse
i did after reinstall, adb devices, go to ta folder and pressed the bat file and error device not found while adb see it right ?
-edit, i tried again this time in 1 windows but same result
Wesley_NL said:
i did after reinstall, adb devices, go to ta folder and pressed the bat file and error device not found while adb see it right ?
Click to expand...
Click to collapse
Well, try another installer in the attachment.
f870103 said:
Well, try another installer in the attachment.
Click to expand...
Click to collapse
still not T.T something is blocking it probaly ?
maby the android studio ? although i removed the google driver and reinstalled that adb driver but no luck
I've PM you for the problem.