The scenario is that:
I purchased for the past year, ChainFire3d and found out to be effective. And right now I got a new phone and got it rooted. BUT, I forgot its running on 4.2.2 and ChainFire3d doesn't work on it. So, I am stuck on boot screen
I tried the following:
ADB commands to uninstall ChainFire3d, but in 4.2.2 roms, adb doesn't work in stock recovery for it has already have an alternative "update by adb support" which will let you go to adb sideload. And adb sideload mode doesn't support any other adb commands except sideload.
So, I tried to download a stock rom from a site, and tried to install it by "update by sdcard" and it says "Installation aborted" maybe because the stock recovery doesn't support the updater-script.
So, I tried fastboot, but fastboot cannot detect any device because stock recovery doesn't support adb.
And alas, I am out of options here.
Please help, somebody.
BTW, my phone is Lenovo A369i
OK... I managed to fix it.. after like... 10 hours .. whew
if you're wondering how I did it... here's how
...................
Related
Guys,
I need help. I tried to work the solution myself and spend days reading different forums and tried different tricks but no luck.
So basically I was asked by my wife to root her Hero as she wanted a higer version of Android to install Viber and some other programmes. I did that using instructions on a Cyanogenmod wiki and everything went fine. However the new rom made the phone a bit slow and clumsy, so I thought I'd look for a different older version that works. I tried numerous roms and they all for some reason were not suitable - either wouldn't boot or were force closing etc...
So at the end of the day I read somewhere that for some ROM you need to install a CWM recovery and I was running a RA 1.7. So I tried to download a newer version of a recovery (to be honest I forgot which one - it was a week ago) and I flashed it and then I realised I have installed a recovery for CDMA and I have a GSM.
So, currently the phone boots and gets stuck at the HERO logo forever. There is no way I can boot into recovery. I have no problem to boot into fastboot, but any attempt to install a different recovery brings a failed signature error. I tried fastboot erase recovery and it did work, but no instalation is possible. When the phone is powered on and while on HERO logo I can run adb and can make it reboot from the command line, but when I try the instructions http://forum.xda-developers.com/showthread.php?t=1630519 I get past the first two lines:
Code:
adb push recovery-clockwork-2.5.0.7-hero.img /data/local/
adb push flash_image /data/local/
and then when I attempt this
Code:
adb shell chmod 777 /data/local/recovery-clockwork-2.5.0.7-hero.img
I get an error message
-exec /system/bin/sh failed no such file or directory
Please help!
PS. A screen shot in fastboot:
http://i3.photobucket.com/albums/y78/tsvet/fastboot.jpg
I managed to fix that with a stock rom and Hboot installation.
Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
NinjaKenZen said:
Alright lads, I got a major issue that is kicking my ass. I need your help please.
Basically the HTC ONE X+ keeps getting error closed in ADB sideload whenever I try to sideload a rom or do anything else for the matter.
adb usb = Error Closed
Adb push and pull = Error Closed.
I can get my device listed but thats about it.
The Issue goes further. I relocked the bootloader in order to install the RUU. Yet I get the error 131 custormer ID error.
I can't access the SD partition on the my computer screen as it doesn't show.
I can't get back to stock rom.
I can't install a new rom.
I can unlock and relock my bootloader.
I can install TWRP and CWM.
I can use fastboot usb. [Very limited]
The issue with fastboot usb is that it keeps saying error device not found and then it refuses to do anything.
I have installed and reinstalled the ADB drivers, SDK manager and htc sync manager.
The biggest issue at the moment is that I can't install any rom whatsoever.
Which basically means, its a potato.
HALLLLP. The htc one x is a international version. UK Vodafone more specifically. Hboot-1.35.0000
Oh yeah, the mount does not work in TWRP and CWM.
I tried different USB ports, cables and even a different computer.
Everything has been wiped. I factory reset it and wiped out other parts in TWRP and CWM in an effort to start from scratch.
Nothing seems to work though...
Edit: I narrowed down the issue
It seems that i can't flash boot.img when my bootloader is unlocked as:
'boot.img'...FAILED (command write failed (Unknown error))
therefore I can't load roms without it crashing on me.
I can however put things into the 'sd card' by loading a broken rom [crashes to process android]. But thats about it. so far.
Oh I also updated the hboot to 1.72
Click to expand...
Click to collapse
If you can push files on sd card, use the TWRP back-up from here to restore to stock.
http://forum.xda-developers.com/showthread.php?t=2414238
You'll at least get it working again.
Thanks, somehow when I updated the bootloader, the boot.img restriction got lifted after I just entered the command again when 'unknown failure' came up. I was at this point able to access the sd card under a buggy rom start-up.I used TWRP to flash a new rom.
Fixed.
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
loaybilal said:
Hi..
I also can't connect my device to PC
I need help ..
fastboot not working never
Click to expand...
Click to collapse
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
imcontreras said:
To anyone in the same situation adb sideload does not transfer the file to the sdcard permanently. To sideload correctly, you need to pick that option from the recovery first and then when the phone is waiting for the sideload type:
adb sideload <PACKAGE>
after some hours of research mine worked (TWRP v2.7.0.1)
Click to expand...
Click to collapse
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
roshak said:
I am in the same situation and my phone in TWRP is waiting for Sideload...
but adb gives error: closed
Click to expand...
Click to collapse
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
roshak said:
So now! I could get my devices connected and listed with updating the drivers (Win 8.1) ...
Then I could push the SuperSU.zip and install it... Is there any way to check if it's ready for flashing a ROM?
Click to expand...
Click to collapse
Im not sure if this will answer your question:
When you upload your rom using sideload will automatically flash it to your device
imcontreras said:
Can you see your phone connected?
adb devices
Or
adb usb
If you're able then in sideload
Go to command prompt on your computer and type
adb sideload (and the file you want to upload)
adb sideload file.zip
Click to expand...
Click to collapse
Thank you!
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
sued said:
Hi, to all.
I know that this has been ask many times,but....
I did search and try almost a every solution i could find on XDA fórum.
I did i complete wipe and voilá, no OS on my Droid DNA, i was rooted but on S-ON, and i had the Venon 3.0.1
I was installing the new Viper 3.1.0 but did the full system wip,and now only can acess my Bootloader and Recovery (TWRP).
Also when rebboting or turning off from recovery it says that there's no root app instaled,and try's to install but it can find it.
I can connect to fastboot, but no adb (when i do adb devices it shows a blank on the device) but on Fastboot it shows the device number.
I try to upgrade drivers and android adb /fastboot, but no luck, in sideload or push the Rom to the phone.
Also i can navigate on the recovery, and try to mount system etc,but also with no luck.
I tryed on Linux and Windows 8, but still no luck.
I'm trying right now another thing that i found on this question and answer thread (that is install pdaneta4126) but still nothing.
Can anyone provide me some insight or light on this matter?
I know that if i have acess to recovery not all is lost, so after a lot of fight and banging with my head, i would like some assistance if it would be possible)
I'm rooted since the 1.15 and didn´t upgrade Hboot or Radios, if this helps and i was in TWRP 2.63, but now flashed 2.7.
Or can i RUU back to stock, and re-root, or what i can do to solve this?
Thank you for all the help you can give me.
Click to expand...
Click to collapse
Can you get into recovery and sideload a rom to install?
RLGL said:
Can you get into recovery and sideload a rom to install?
Click to expand...
Click to collapse
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Try this thread::: Even if you have accidentally formatted your internal storage and you have no files on your phone, this section is down the bottom of the thread. Only follow this if you have no access to your phone and have nothing installed on your sdcard. For everybody else simply follow from step 1.
above is an excerpt from the text.
sued said:
I can go to the recovery, and connect the sideload, but the Linux and the Windows 8 but when i try to adb sideload viperDNA.zip to the internal storage, it just says "error device not found"
But if i do in fastboot (fastboot devices) the pc detects and returns the number.
In adb (adb devices) the system returns a blank space where it should be the device number.
Also i unable to push a file to sdcard.
Click to expand...
Click to collapse
Download PdaNet and it will reinstall your adb drivers and you should be able to find your device.
Adb push can push a rom to the phone and then just flash it and your good.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Recently I rooted and changed my vold.fstab in a hope of bigger phone storage and then all I got after reboot is a logo.
I using Philips w6610.
I have original vold.fstab file
My phone rooted, and have recovery
My phone don't have usb debug
I tried to make an update.zip but maybe I did not know how to do it right
Now I can't not do anything and through the search on google nothing can help too.
Thank in advance
Update, The update.zip always endup with installation aborted . adb shell commend end up with closed line
Pls helppppppppp ( I just used my phone for 2 weeks
OMG nobody care!
The only two things that pop to mind, are an update.zip (like you already tried) or trying to access 'adb shell' in recovery. Though in the last case you probably need to mount stuff manually, or via the UI of the recovery to get to the vold.fstab file and revert it back.
Can you flash your firmware
The only two things that pop to mind, are an update.zip (like you already tried) or trying to access 'adb shell' in recovery. Though in the last case you probably need to mount stuff manually, or via the UI of the recovery to get to the vold.fstab file and revert it back.
Click to expand...
Click to collapse
Update.zip will be aborted in the first step. I got an installation aborted everytime I update via sdcard.
I also tried adb shell and get command: closed . adb sideload update.zip return same thing with update via sdcard
Can you flash your firmware
Click to expand...
Click to collapse
I really don't know how to flash it right way.
I got and cook ROM from a russian forum for my phone. Only tried to update through sdcard and adb sideload
I am able to get into fastboot but I can not do anything with it!
Is there any methods I can do ?
I received my LG G Watch today and immediately set out to unlock the boot loader and to root it. It went easy, used the tools from http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. ADB drivers worked for both fastboot and sideload at this point.
Now I wanted to upgrade to the new 5.1.1 from 5.0.2 so I downloaded the update.zip file and tried to use sideload to install it, which got me a code 7. I looked up how to solve this issue and came across this post:
JaLex77 said:
I was getting Status 7 as well.
I flashed TWRP, did a full wipe of system, Data, Cache.
(Do not install Supersu) Reboot to Bootloader.
Fastboot Flash system, recovery, boot from LG G Watch Restore Tools.
Reboot to Recovery.
ADB Sideload option.
Adb sideload update.zip from PC.
Sucess!
Optional:
reboot bootloader
Fastboot flash TWRP
reboot
Click to expand...
Click to collapse
So yes, I wiped /system/ and now it no longer boots. I can't install custom recovery OR revert to stock because the ADB driver no longer works in the fastboot screen. Sideload still works but I can't do anything useful with that AFAIK.
I've tried the Google usb_driver and Universal ADB USB driver with no change. In Device Manager it's identified as "Android" with the yellow triangle and as "Android Bootloader Interface" when the default driver installs.
How can I solve this?
Restore to stock with unlocked bootloader u cant update of its rooted.
Register ADB Driver
Lodorenos said:
I received my LG G Watch today and immediately set out to unlock the boot loader and to root it. It went easy, used the tools from http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863. ADB drivers worked for both fastboot and sideload at this point.
Now I wanted to upgrade to the new 5.1.1 from 5.0.2 so I downloaded the update.zip file and tried to use sideload to install it, which got me a code 7. I looked up how to solve this issue and came across this post:
So yes, I wiped /system/ and now it no longer boots. I can't install custom recovery OR revert to stock because the ADB driver no longer works in the fastboot screen. Sideload still works but I can't do anything useful with that AFAIK.
I've tried the Google usb_driver and Universal ADB USB driver with no change. In Device Manager it's identified as "Android" with the yellow triangle and as "Android Bootloader Interface" when the default driver installs.
How can I solve this?
Click to expand...
Click to collapse
There shouldn't be a yellow Triangle when the driver installs. You have to assign the proper driver.
Update Driver>Browse My computer for Driver Software>Let me Pick from a list of Drivers on my computer>Android Composite ADB Interface>Next Complete
I had received this error because I had my phone rooted when I attempted to install the OTA via the /cache method.
What I sugest to you, to get this installed properly is to download the newest version of LG G Watch Tools and restore your watch to 5.0.2 and root it, push the update to /cache and make the /cache/recovery/command file but instead of rebooting normally like you would to trigger the update, instead run adb reboot-bootloader and restore your watch again to 5.0.2. The restore leaves /cache alone so this will work. Once 5.0.2 has been restored, use the fastboot options to boot into Recovery Mode, the update will start and install properly.
I do suggest doing a factory reset after running the update, as I was experiencing some performance issues after having done this until I had done a quick reset. Now it's running fantastically.
To solve any ADB problems, you should install the ClockworkMod ADB drivers, then open Device Manager, find G Watch in there and then right click, hit Update Driver, Let me find one, choose to choose a driver manually and then tell it that it is an ADB Interface, choose any of the ADB drivers that appear and then hit next. ADB should work for you after that.
ADB however does not seem to work inside recovery for 5.0.2 as I was unable to sideload mine due to it not showing in device manager at all while in recovery mode.