Heya all,
please will you kindly assist with the following:
I just got a Samsung Galaxy Tab 10.1 and i installed GalaxyTask_10_Full rom everything worked fine. Then I tried to install a different rom (CM9_KANG_ICS_4.0) to try it out but during the installation in CWM Recovery there was an error. so i rebooted the device and it still loaded up fine with GalaxyTask_10_Full rom. Then I decided to try the ICS theme b00sted_GalaxyTask_ICS_Theme_Batt_v10.0.2b for GalaxyTask_10_Full rom so i booted into CWM Recovery installed the then reboot. after this the device did not boot further than Samasung Galaxy Tab 10.1 screen.
Therefore i did the following:
1) booted into CWM Recovery tried to mount sdcard but the mount fails. so therefore I cant copy over the GalaxyTask_10_Full rom.
2) then i found a thread (i cant find the link of the thread any more!) about using adb shell to push the custom rom onto the device. So far I've been able to push the custom rom onto mounted /data/ folder but when i try to update i get the following error:
Code:
sh: /sbin/postrecoveryboot.sh: not found
I'm running ubuntu 11.10 64 bit
My steps using adb
Code:
[email protected]:~/SGT 10.1/roms$ adb shell mount data
[email protected]:~/SGT 10.1/roms$ adb push GalaxyTask_10_Full.zip /data/
1301 KB/s (366834611 bytes in 275.147s)
[email protected]:~/SGT 10.1/roms$ adb shell
~ # recovery --update_package=DATA:GalaxyTask_10_Full.zip
sh: /sbin/postrecoveryboot.sh: not found
thanks in advance for your kind assistance,
best always,
muzi
[SOLVED]figured it out!
i couldn't get devise to install custom from adb, every time i tried i kept getting the following error:
code:
Code:
adb shell mount data
adb push GalaxyTask_10_Full.zip /data/
adb shell
recovery --update_package=DATA:GalaxyTask_10_Full.zip
error:
Code:
sh: /sbin/postrecoveryboot.sh: not found
so i decided to use adb to move GalaxyTask_10_Full.zip from /data folder to /sdcard
Code:
adb shell mv /data/GalaxyTask_10_Full.zip /sdcard/
once move was done i used ClockworkMod Recovery install from sdcard and voilà the custom rom was there.
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
jigz23 said:
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
Click to expand...
Click to collapse
I'm having the same issue. Did you ever get it figured out?
jigz23 said:
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
Click to expand...
Click to collapse
Could be a sign of a degrading internal memory, but is is extremely unlikely that a solid state memory device would fail like that.
You could try reformatting the internal sd via your pc while in CWM, and installing your RUU after that, provided you can see the internal drive.
Sent from my HTC Flyer P510e using XDA Premium HD app
Run these adb commands while in CWM when connected to pc , see if it helps :
adb remount
adb shell rm -rf /system/sd/dalvik-cache
adb shell format DATA:
adb shell format SYSTEM:
adb shell format CACHE:
adb shell format MISC:
Warning: THIS WILL ERASE ALL USER DATA. DO AT YOUR OWN RISK.
Then run your RUU and you should be back in working order.
Sent from my HTC Flyer P510e using XDA Premium HD app
mhkabir98 said:
Run these adb commands while in CWM when connected to pc , see if it helps :
adb remount
adb shell rm -rf /system/sd/dalvik-cache
adb shell format DATA:
adb shell format SYSTEM:
adb shell format CACHE:
adb shell format MISC:
Warning: THIS WILL ERASE ALL USER DATA. DO AT YOUR OWN RISK.
Then run your RUU and you should be back in working order.
Sent from my HTC Flyer P510e using XDA Premium HD app
Click to expand...
Click to collapse
This has been a looong time but I figured it was worth a try. I did all these commands and run into trouble once I get to the adb shell format data:. I get an error message saying "/sbin/sh: format: not found"
jigz23 said:
This has been a looong time but I figured it was worth a try. I did all these commands and run into trouble once I get to the adb shell format data:. I get an error message saying "/sbin/sh: format: not found"
Click to expand...
Click to collapse
I get the same thing
I picked up an Archos G9/80 and immediately came here to root it. Instead I wound up installing SDE and flashing Freezenooks G9 Build8 from tis thread: http://forum.xda-developers.com/showthread.php?t=2171742
I just have one problem. I can't get Dropbear SSH II to install. I tried both from the Play store and adb installing it. I even tried the older version. The apk installs fine but it fails to install the service. They both fail during a step where it says its remounting read-only. This is interesting as I notice that the rootfs is mounted read-write by default. From adb shell I tried to force it read-only with mount -o remount,ro but it fails as the Device is busy. I'm guessing this is the same problem that the installer is encountering and since it can't remount rootfs as read-only it proceeds to remove the binaries it's copied over. I've been trying to find out where it copies them before it deletes them. I assume they would be in /system/bin but I can't ever find them there. I gets to the error step way too fast.
Does anyone have any workarounds? Could / should I "borrow" the binaries from another Android box and copy everything to the correct place?
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Thanks mate! You just saved my day.
I had the exact same problem and couldn't get sideload to work in TWRP 2.7.0.0 on Nexus5. But simple "adb push..." worked.
this doesn't work
thank you very much, you saved my day,too.
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
Thanks man... you just saved me a ton of trouble. Tried this on the Nexus 4 and works like a charm! :good:
just wanted to say thanks!
for some odd reason, my twrp (even though its the latest for my nexus7 grouper) had the same flashing no status error)
used the kill, usb, and push commands to copy over 3 different zips (rom,kernel,gapps) and it all copied over ready to flash
thanks!
23468
seriously thanks mate! work like charm :good::good:
for me it copies the small files but my rom is 1gb plus it gives me the error 'protocol failure' can some one give me a helping hand here?
please?
Same Issue
jacktackle said:
for me it copies the small files but my rom is 1gb plus it gives me the error 'protocol failure' can some one give me a helping hand here?
please?
Click to expand...
Click to collapse
Three days and All I can do is flash a recovery. Insertcoint goes though and says it's installed but nothing but HTC Screen
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
Thanks man. You're lifesaver
Awesome, this worked for me too
HELP
I have htc one s somthing wrong happend turned the storage from 16 giga into 48 mega byts i cant get back my storage what to do please help me* i still can push roms but i cant because there is no storage what to do
mahmoud hakim said:
I have htc one s somthing wrong happend turned the storage from 16 giga into 48 mega byts i cant get back my storage what to do please help me* i still can push roms but i cant because there is no storage what to do
Click to expand...
Click to collapse
Can you ruu. Then do a factory restore. That should reset the partition
This does not work for me. Firstly, I tried installing Cyanogenmod by putting it on my internal SD card, then booting to recovery and installing the zip, and this did not work. So I tried to sideload it and got the error " * failed to write data 'protocol fault (no status)' * ". I don't know what to do. I've also tried the same with Paranoid Android but I get the same errors. Any help would be greatly appreciated.
derekokelly said:
This does not work for me. Firstly, I tried installing Cyanogenmod by putting it on my internal SD card, then booting to recovery and installing the zip, and this did not work. So I tried to sideload it and got the error " * failed to write data 'protocol fault (no status)' * ". I don't know what to do. I've also tried the same with Paranoid Android but I get the same errors. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Exact same problem I have, any suggestions?
try changing to usb 2.0, usb 3.0 sometimes not working with adb command.
much love
Thanks for saving the day voxigenboy!!! I love you man. lol
And for those that simply can't get their stupid computer to recognize the LG drivers... PDANet wins with whatever voodoo they freaking use!
Thanks for your help, rescued my evening!
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
I'm sorry, that's a bit confusing.
So are u suggesting to "sideload" by:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)?
Waiting for your response.
Zenfone 5 a501cg (India) (WW)
Stock Recovery
This didn't work for me but I found this other way of passing the archive to my phone :
https://www.youtube.com/watch?v=Z3SpI7m7mFI
Hey guys,
before asking for help, I tried to solve my problem by myself but couldn't find a solution.
I bought a Xperia V, unlocked the bootloader, installed Xperia Recovery Manager to install TWRP to FOTA-Partition which worked.
Then I installed Cyanogenmod 11 and it worked. But actually, I wanted to install CM 14. I pushed the zip.file to internal storage via adb but couldn't find it in TWRP. Then I installed Clockworkmod Recovery which didn't solve this problem, too. I can't remember why, but I formatted everything possible with CWM and got an error message while trying to format /storage/sdcard0. After that I installed CM 11 again but the camera app didn't start and no download was possible: I got the message "couldn't find external storage". Even installing CM 10 didn't work. CWM says "error mounting /storage/sdcard0".
In adb shell no mount point shows up and command "chown sdcard_rw sdcard0" says "Unable to chown sdcard0: Read-only file system". Rootfs is read-only. At this point I gave up. Instead I tried to flash Android Stock ROM via flashtool but that didn't work because flashtool doesn't find my device although I installed the drivers. I run Windows 7 on my second Laptop and it says the drivers for Xperia V are current. Is there a chance to repair the device?
Thanks for help!