I installed twrp over cwm and lost all my userdata. Furthermore theres no ROM on the device, so its not able to boot. I Need a ROM zip on my device, but adb push and adb sideload isnt working.
Related
After trying to flash AndroWook using Goo Manager, I managed to become stuck in the boot animation. I've tried fastbooting stock system blobs, with no good results. I flashed CWM over TWRP, but CWM can't find any files on my SD. Now I'm trying to ADB push a blobfile (using these directions http://forum.xda-developers.com/showpost.php?p=25216525&postcount=23), but I'm not finding my device.
Can anyone please help me out? I'm so tired of my bricked Prime. There has to be some way that I can be able to flash a ROM onto this thing.
If you have a ROM in a blobbed format, then try the following, as you apparently can connect to your TFP via fastboot:
fastboot -i 0x0b05 flash staging BlobbedRomThatYouAreLoading
This should be similar to the method you used in flashing CWM over TWRP, except you're flashing to the staging partition instead of the recovery partition. On reboot, your ROM should install and load.
A lot of users seem to be having problems connecting to TFP over ADB when in CWM. I'd personally stick with TWRP, as it seems more stable.
Edit:
If the above doesn't work, then I would try flashing TWRP again, then while in TWRP, see if you can connect via ADB. If ADB is still not recognizing your device, then please see this thread and try re-installing your ADB drivers using there:
http://forum.xda-developers.com/showthread.php?t=1426502
kokopuphz said:
If you have a ROM in a blobbed format, then try the following, as you apparently can connect to your TFP via fastboot:
fastboot -i 0x0b05 flash staging BlobbedRomThatYouAreLoading
This should be similar to the method you used in flashing CWM over TWRP, except you're flashing to the staging partition instead of the recovery partition. On reboot, your ROM should install and load.
A lot of users seem to be having problems connecting to TFP over ADB when in CWM. I'd personally stick with TWRP, as it seems more stable.
Edit:
If the above doesn't work, then I would try flashing TWRP again, then while in TWRP, see if you can connect via ADB. If ADB is still not recognizing your device, then please see this thread and try re-installing your ADB drivers using there:
http://forum.xda-developers.com/showthread.php?t=1426502
Click to expand...
Click to collapse
been here done this, install the universal naked drivers first.... then install twrp since it seems to work better then cwm.... then adb push a small file to see of it actually works then push rom and install....
I've got this working up until I try to push something. Pushing something fails because of a "Read only file system."
How do I get my prime to be read/write?
You should fastboot flash twrp, boot to recovery, fixpermissions, then push the rom
Sent from my Transformer Prime TF201 using xda premium
Fixing permissions from TWRP did not help.
im just getting told that fastboot is a not a recognised command which seems like a nooby outcome
I tried to install a KitKat Rom but ended up having my One boot up and reboot to recovery. Unfortunately I decided not to make a backup because I felt I had gone through the motions enough times to know what I was doing, and now I can only boot to the Rom that won't work. I found another rom that I used before sitting in my computer, but I can't seem to use adb to push it (unless I'm doing it wrong) into my phone's storage so I can use recovery to boot into it. Help!
TunedTimbre said:
I tried to install a KitKat Rom but ended up having my One boot up and reboot to recovery. Unfortunately I decided not to make a backup because I felt I had gone through the motions enough times to know what I was doing, and now I can only boot to the Rom that won't work. I found another rom that I used before sitting in my computer, but I can't seem to use adb to push it (unless I'm doing it wrong) into my phone's storage so I can use recovery to boot into it. Help!
Click to expand...
Click to collapse
First kitkat roms require s-off and the newest version of TWRP 2.6.3.3
so you can update your recovery and get s-off and reflash the kitkat or you can push the old rom you have to the phone.
http://rumrunner.us/ for s-off
recovery is here - http://techerrata.com/browse/twrp2/m7
ADB Push from Recovery
adb push rom.zip /data/media/0/
the file you push must be in the same directory as ADB
Hi,
Few days ago I managed to put my Archos 79XE into a bootloop during an attempt to deodex the stock rom. Now, I can boot into stock recovery and fastboot modes only.
I contacted Archos customer service, and they sent me an update.zip file, with instructions to copy the update.zip to my sdcard, then flash it through recovery mode. This solution is not applicable, though, since the device recognizes two different sdcard's, one internal and one external, the recovery only sees the internal sdcard, which i can't copy the file to since i don't have ADB access now.
What I did next was an attempt to create a fastboot flashable system.img. But couldn't flash that, as fastboot flash system system.img gets stuck at erasing the partition and never go past it.
So, my question is: is there a way to make the stock recovery work with the external sdcard, instead of the internal? I was thinking maybe fastboot -c and pass some kernel command line to switch both mount points?
Or is there any custom recovery that can apply the update.zip? I couldn't find any cwm or twrp custom recovery for this device.
P.S.
The device reports being a tk8983 in fastboot devices.
Any ideas?
Hi All
I own a Pantech Vega r3 IM-A850s which was running a custom Kitkat rom and has the CWM 6.0.2.8 recovery loaded.. I was looking to try get either lollipop or another version of Kitkat on there since the current one was having issues. I do not have any OS loaded as I had somehow wiped it trying to get this to work.
Loading up CWM then going to sideload, I am unable to load roms onto the phone.
ADB Devices - works
ADB sideload - failed to write data 'protocol fault (no status)
All other ADB commands (e.g. push, reboot, etc) gives 'error: closed'
Going to fastboot mode:
Fastboot devices - works
Fastboot erase recovery/fastboot flash (file.img) gives 'FAILED (remote: It is not surpport in user build.)'
I still have CWM loaded into the recovery but am not able to flash with any other recovery version/type. I cannot load the internal sd card as it returns 'E: Can't mount /sd card/ and same for external sd.
---Edit---
I appear to have resolved this.
Downloaded the recovery from the thread below, then ran the Run in Fastboot.bat and was able to temporarily load TWRP to sideload the zips required. From there, got Kitkat installed and all is well (nearly)
http://forum.xda-developers.com/android/development/kitkat-rom-english-guide-custom-rom-t2995865
Hi.
I unlocked the phone correctly via CMD.
Then, I flashed recovery VIA cmd too.
After that, I booted to recovery and the screen showed vertically half blurred screen after it booted into TWRP.
Finally, tried to install the rom unsuccessfully as TWRP didn’t detect any file in the SDCARD path. Some issue "mount sd card failed" related.
Tried, sideloading another zip file just in case but it says something about "closed device".
Now I cannot flash anything and I cannot reboot normally as It seems to be everything erased.
I can access fastboot and TWRP (although I cannot flash or side load anything...)
What could I do?
Flash this twrp https://dl.twrp.me/x2/twrp-3.2.1-0-x2.img
Boot into twrp
Wipe data partition
Install any rom you want
Heyyo, unfortunately adb sideload is currently broken on x2 official builds.
I'd recommend using...
adb push NameOfROM.zip /sdcard
That will push the ROM to your Sdcard folder. Same can be repeated for Gapps