Hi guys,
weird problem- haven't used my tab in over 6 months, decided to 'unretire' it. I had CM11 installed using CWM recovery ages ago.
Long story short- the tab started, but quickly started acting funny. It restarted itself and got stuck on the boot screen, and now whenever I try to access recovery the screen is on but is blank.
Tried reflashing CWM using ODIN- didn't work. Tried re-flashing TWRP using ODIN- didn't work either (same blank screen).
Any ideas?? I also tried reflashing stock rom through Sammobile but ODIN won't flash it-- keeps giving a 'WriteRawData' error.
anyone have any thoughts? worth mentioning that I can still access download mode, but choosing recovery just gives a blank screen.
Hmm, how about manually writing the recovery.img into your system? Try this:
1. Get the latest twrp from decatf's 5.1 thread.
2. Unzip and copy the recovery.img file to your /sdcard.
3. Either in terminal or adb shell, type in this command
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p2
Sent from my GT-P7510 using Tapatalk
Related
I had a mt3g and was always able to get to recovery manually. I recently bought a vibrant, rooted using adb, installed clockwork mod recovery, and did a nandroid. I am unable to get recovery manually. Ive tried every combo of vol^ volv that I could find on these posts. Im ready to start having fun, but am worried for this reason. Any help would be appreciated. Heres my question.
If I start flashing, and my phone gets stuck (vibrant screen, galaxy screen, bootloop, etc.), is there any way I can get recovery without having to do it manually? Would I be able to reboot recovery with adb without mounting? Is there's any other way?
Also, if there is a way, how do I get into clockwork mod recovery so I can restore with nadroid? Would I have to have clockworkmod update zip on my sd and reinstall packages thru stock recovery first? Thank you for any help. Im lost!
make sure you have your clockwork recovery on the root of the internal memory and have it named update.zip
open terminal or command prompt and type adb shell. you will get $ type su to get # type reboot recovery then when in samsung recovery select reinstall packages and you will be in clockwork.
Ok, so I can do this on the computer even though the phone can't be mounted? It will recognize the devise and reboot anyway? Sorry, I'm new to adb.
Hi there,
Currently my phone has no ROM and a disfunctioning ClockworkMod Recovery. (It cannot install zips or take updates).
Therefore I'm using ADB to flash a new recovery and ROM into the phone.
Code:
mount data
Results in:
Code:
mount: can't find /etc/fstab: No such file or directory
So I copied my file into the /data/ folder with
Code:
adb push c:\rom.zip /data/
This was done successful.
After that I tried to install the rom.zip using
Code:
adb shell
recovery --update_package=DATA:rom.zip
Unfortunately this results in:
Code:
sh: /sbin/postrecoveryboot.sh: not found
Also tried to replace the recovery.img but this also resulted in:
Code:
sh: /sbin/postrecoveryboot.sh: not found
In short:
Can't mount USB in ClockWorkMod
Can't access phone files with Windows Explorer
Can't use Kies to recover phone.
Can't use ClockWorkMod to install a zip or update.
Can't do normal boot.
Can't mount data using ADB.
Can't install recovery ROM using ADB.
I can't think of any way to fix this, hope someone else can help me with this.
Simple Use Odin
Sent from my GT-I9100 using XDA
Can you get in to Download mode?
As the 2 people stated above:
If you are able to get into the download mode, then you should be able to install a stock rom via Odin.
Have a good day and good luck with your phone.
Sorry to mention. The first thing I tried was Odin, but I'm not able to get into download mode.
Magiciano said:
Sorry to mention. The first thing I tried was Odin, but I'm not able to get into download mode.
Click to expand...
Click to collapse
what happens when you try and get into download mode? is it just blank? when you plug it in to charge do you get the battery charging animation?
nutmegy said:
what happens when you try and get into download mode? is it just blank? when you plug it in to charge do you get the battery charging animation?
Click to expand...
Click to collapse
The download mode button combination has no effect, it won't even try to load.
I get a frozen image of a empty battery with the spinning wheel inside, the battery is more than half full tho.
Magiciano said:
Sorry to mention. The first thing I tried was Odin, but I'm not able to get into download mode.
Click to expand...
Click to collapse
USB recovery jig would be the next step before it all becomes expensive .
jje
I would say try using a USB jig to get into download mode. If that doesn't work, I think the only thing left to do would be to take it to Samsung.
Edit: Damn, I never saw JJE's post above. Sorry.
Jtag might be cheaper than taking it to samsung
Sent from my sgs2 running cm9 using xda app
Sounds annoying..
Tryed this?
http://forum.xda-developers.com/showthread.php?t=1449771
fastboot erase cache ( if failed ignore it)
fastboot oem rebootRUU ( not shure if RUU is htc dependent or not )
fastboot flash zip your_recover.zip
fastboot reboot-bootloader
it's worked for me, its basically change your recovery, so you can install a properly working clockwork
I've found my friend's sgs2 last few days ago as yours..
Couldn't go 2 download mode w/ buttons combination
..
Randomly as a noob (sorry4that.. ) I tried adb shell :
adb reboot download
N it worked ready2 next step flashing progress via Odin 1.85 (just try this ver!)
If yours don't: try USB Jig neither to JTaG or SSC @ last opt
Hope this may help & sorry about 'tittles'
I have tried to root and got the "Go to kies pick recovery' screen after an Odin fail. Replugged into a different USB plug and got successes from Odin. I flashed the huge AT&T stock ROM, then clockwork recovery then the rooted kernel pda.tar . The phone gets stuck at the logo. I can adb reboot recovery and get into CWM. I did an adb push SAUROM_XLA2_RCV.zip /emmc/ and then I tried install it. Instant reboot and stuck at logo. Tried to copy to a microSD card. Same. I can adb shell while recovery run. If I try to unzip, it works so it's not a read error.
The answer is, extract the img files from the huge ass AT&T stock pda tar and then mount /sdcard, dd if=/sdcard/system.img of=/dev/block/mmcblk0p24 and dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8. Now, you can untar the root pda.tar and also dd that. Checked Titanium Backup , got root.
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
Hi all. Before i start i want to say, i read a lot of threaths and comments before i started to booting recovery and i followed Tutorial that you can find somewhere here on XDA for MotoE.
I unlocked Bootloader correctly and everything was right. Then i downloaded latest version of TWRP and CWM if something will be wrong.
So i booted into bootloader, connected to PC (windows 8.1) and using adb i installed TWRP (by command window). After instalation was complete, i used comand: "fastboot reboot" to get my mobile start normally. Everything worked fine so i started last step. Turned off mobile, booted into bootloader(or maybe fastboot? idk...) and by volumebuttons i choosed "Recovery" . Then a black screen for a minute. After that mobile stuck on screen that i attached down below. So i tried this but with CWM (same process way). But nothing new... Someone said me i had to try "Minimal ADB and Fastboot" but again, nothing happend.
Can you help me guys?
The recovery isn't installed! Reinstall the recovery and follow correct steps!
I tried it one more time. I´m attaching image that is from command window showing that .img was booted ... Strange is, immediately after booting was completed, mobile restarted... and after i turned off mobile again, still i can´t reach recovery. Isn´t that problem in .img file? maybe it´s broken, isn´t it?
Tried once again
Ok last try didnt worked. So i complettly followed this guide http://forum.xda-developers.com/moto-e/general/guide-one-moto-e-beginners-guide-t2807891 STEP-BY STEP!
Command window screen attached, Fastboot screen attached.
After reboot, turn off i tried to open recovery and again that image that i posted in first coment. (android figure with words: no command)
By that guide i downloaded recovery from here: https://goo.im/devs/OpenRecovery/condor/
and i downloaded just "openrecovery-twrp-2.7.1.0-condor.img" as i have to do it (written in guide)
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
neo.ank said:
Well, your recovery is flashing fine from cmd but its not detected by your phone.
Try re-downloading the recovery and check md5 before flashing.
I'll look into it and see if the issue can be pinpointed.
Btw, you might need the flash the stock ROM back if nothing works.
Tapatalk with RAZR HD
Click to expand...
Click to collapse
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Mondop said:
Ok i will re-download recovery, is that file that i downloaded ok? i mean should i dowload same file as before?
+ sorry for that but i completly dont know what the "md5" is. can you send me link from where i can learn what it is? you can explain that too but i dont want take your free time.
Click to expand...
Click to collapse
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
neo.ank said:
Okay try this.
Flash CWM
If flashing fails or you get any error, then try booting into recovery.
Code:
fastboot boot recovery.img
If you boot into recovery, flash the SuperSU package.
Reboot and then flash the recovery.
See if it works.
Click to expand...
Click to collapse
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Mondop said:
no
flashed CWM from here http://forum.xda-developers.com/showthread.php?t=2793625
concretly from here http://www.mediafire.com/download/6odyyqgodw15f1b/recovery.img
then i flashed it, then i rebooted phone then i shuted it off (to boot into fastboot) in fastboot i selected recovery and again, that screen with android figure (no command) so i pressed power button for long. mobile rebooted. again i went into fastboot to write command you said me to boot into recovery. but i stucked at starting screen (that blue big M in "water" cycle)
this all means, files i downloaded was OK but my phone isnt :/
any idea :/
Click to expand...
Click to collapse
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
neo.ank said:
Do not flash CWM, just boot into it by the command I posted above.
Then try and flash SuperSU, (if you get a root prompt from CWM, select NO.)
Reboot device.
Then again boot into fastboot and now flash recovery (twrp).
Click to expand...
Click to collapse
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Mondop said:
so now what if i flashed that CWM before?
Now i tried go to fastboot and used just command that you said(to boot into recovery) and as i said, i stucked on motorola starting logo
+ you said i have to flash cwm
Click to expand...
Click to collapse
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
neo.ank said:
I said if flash is not successful, then boot into it. So you can't boot into recovery either.
Here's last resort, extract the stock recovery from stock ROM and flash it. Then we'll try flashing TWRP again.
If you don't have stock ROM, download it. as you might need it to recover.
Click to expand...
Click to collapse
Okay, can you give me link with tutorial? i found just this one which restores whole system (and its 4.4.3 and i have now 4.4.4, i mean this will be maybe problem, wouldn´t it?)
i mean this one (tutorial how to restore moto E)
http://forum.xda-developers.com/showthread.php?t=2759495
did you try updating / reinstalling USB-driver on your computer?
magicw said:
did you try updating / reinstalling USB-driver on your computer?
Click to expand...
Click to collapse
no i didnt, think you it will help? i mean if i can connect my mobile into pc without any problem in normal mode and in fastboot too... i will unninstal drivers, intall them again and them i will try unninstal motorola device manager and then again intall him.
(i had newest drivers i can update them)
LOL?
OK im in recovery i already flashed superSU...
What did i do?
As you said, i reinstalled all drivers...
then i downloaded same TWRP again (but with mirror source)
I downloaded attached md5 file ( still dont know what should i do with it )
moved recovery and .md5 files into minimal adb and fastboot (both files i renamed to "recovery")
turned off devices
started fastboot
connected to PC
started command window and entered command "fastboot flash recovery recovery.img"
then i didnt wrote sommand "fastboot reboot" as i done before
i just unpluged usb and navigate to recovery button and launched it
and VUALA im in recovery
hurraaa
just installed superSU and then rebooted.
everything works (superSU too)
i have one more question...
i downloaded twrp manager from google play
first start: asked for root permission a allowed it
then message appeard:
"The only compatible version of busybox we support is Stericson. All other cause havoc on all operations in this app. Please click yes to install Stericson busybox"
what the heck is busybox?
+Should i download it or not?
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
ok then
magicw said:
Do not use TWRP Manager, ROM Manager, CWM Manager or any other of these Tools. They often do not really work good together with "exotic" fones. Why the heck do you need TWRP manager? You have TWRP installed
Anyway - Busybox you also can download and install from Playstore. Busybox is a collection of executable terminal commands helpful for any kind of script. There are a couple of rooted apps who will ask for busybox support - so don't hesitate to install busybox - but do it directly with busybox app from playstore.
After you have installed the binaries you can de-install the busybox-app. Because all necessary binaries then are copied into /system/bin/ folder and the app itself only will become active once a new version would be available (but this is not the case very often).
Click to expand...
Click to collapse
i have no reason to want twrp manager, i just wanted to look at this app, and i found that busybox there so i wanted to ask here
thx for answer, now i undertand