regardless of what i try the command prompt says "sending..." and goes nowhere from that. i cant flash anything. any ideas?
US Dell Streak for att (not from att) rooted with first leaked 2.1 rom
It would be easier to diagnose if you would be more specific.
Please copy-paste the command you gave and response you got.
smokku said:
It would be easier to diagnose if you would be more specific.
Please copy-paste the command you gave and response you got.
Click to expand...
Click to collapse
smokku's right, does it say 'fastboot' on the streak screen?
Is the device in fast boot mode?
Sent from my Dell Streak using XDA App
phone is in fastboot mode and says as much on the phone screen. what i am currently trying to do is flash back to 1.6 and the guide i was following said flash stock dell recovery. i downloaded the stock recovery file and in cmd i typed
fastboot flash recovery recovery.img
i was in the correct directory and the recovery.img file was there
the cmd then says sending recovery.img... and sits there. it doesnt fail it just does nothing. ive tried flashing several different recoveries including the clockworkmod recovery and i still get nothing but sending...
Try this worked for me
http://www.streaksmart.com/2010/08/...d-16-on-dell-streak-after-21-update.html#more
lufc said:
Try this worked for me
http://www.streaksmart.com/2010/08/...d-16-on-dell-streak-after-21-update.html#more
Click to expand...
Click to collapse
still getting no response from fastboot. i had this problem before and i just kept unlplugging the usb and reinstalling drivers. but its not working for me this time
Right the way to do it is download the recovery image from the last link download the stock recovery from here
http://android.modaco.com/content/d...1-6-downloads-how-tos-rom-superboot-recovery/
open them both up
in the r1-4399-streak-recovery delete the RECOVERY and copy over the recovery from the other file and rename it recovery
put device in fastmode and start the windows batch and the recovery will install
If i ever need to install a stock recovery just install it into the r1-4399-streak-recovery rename it recovery and it will install every time
lufc said:
Right the way to do it is download the recovery image from the last link download the stock recovery from here
http://android.modaco.com/content/d...1-6-downloads-how-tos-rom-superboot-recovery/
open them both up
in the r1-4399-streak-recovery delete the RECOVERY and copy over the recovery from the other file and rename it recovery
put device in fastmode and start the windows batch and the recovery will install
If i ever need to install a stock recovery just install it into the r1-4399-streak-recovery rename it recovery and it will install every time
Click to expand...
Click to collapse
i'll give it a try. thanks
well i finally was able to flash recovery, boot, and system after a reboot of my pc and phone and reinstaling drivers before each flash. now im stuck at the dell logo. ugh...
update: was able to flash to stock 02 1.6 rom. via the link lufc provided (thank you) i guess i'll have to retry flashing back to stock att 1.6 after a few more people have tweaked it and make an update.pkg for it.
punkrckriot said:
well i finally was able to flash recovery, boot, and system after a reboot of my pc and phone and reinstaling drivers before each flash. now im stuck at the dell logo. ugh...
update: was able to flash to stock 02 1.6 rom. via the link lufc provided (thank you) i guess i'll have to retry flashing back to stock att 1.6 after a few more people have tweaked it and make an update.pkg for it.
Click to expand...
Click to collapse
Yeah i got stuck at the dell log a couple times before it successfully flashed. I think something is up with fastboot not properly writing the files because i'll flash the clockworkmod recovery 3 or 4 times in a row with no result. give up on it and flash stock recovery then when i go into recovery mode, its the clockworkmod one :/
fone_fanatic said:
Yeah i got stuck at the dell log a couple times before it successfully flashed. I think something is up with fastboot not properly writing the files because i'll flash the clockworkmod recovery 3 or 4 times in a row with no result. give up on it and flash stock recovery then when i go into recovery mode, its the clockworkmod one :/
Click to expand...
Click to collapse
i just think my PC and fastboot dont agree with eachother. before i can flash anything i have to uninstall the drivers, restart my pc, reboot phone into fastboot again, reinstall drivers, and then flash what im trying to flash one at a time, then restart the whole process to get any results on what i try to flash next. I have no idea whats up with the recoveries because i ran into the same issue of flashing clockworkmod and having it work fine till next reboot and its back to stock.
lufc said:
Try this worked for me
http://www.streaksmart.com/2010/08/...d-16-on-dell-streak-after-21-update.html#more
Click to expand...
Click to collapse
Used this yesterday to go back to 1.6 so my streak gould go off for repair, worked a treat.
spences10 said:
Used this yesterday to go back to 1.6 so my streak gould go off for repair, worked a treat.
Click to expand...
Click to collapse
yeah im on an att streak though so i needed to get back to the US stock rom. its good to go now. thanks though
Related
My recovery image seems to be messed up since I can't boot into it. My phone will boot but everytime it does ADW crashes over and over not allowing me to do anything. What can I do to go about getting the recovery fixed again and reflashing to try to smooth everything out?
*Edit*.I think I may have thought of a work around. I emailed my self the launcherpro.apk and installed it through gmail. Now I can access my phone. Now I just need to flash a working recovery..
I do appreciate your help though Riley.
You can try downloading ADW Launcher, putting it on your SD card and boot from recovery, then flash the launcher. It is a far shot, but if launcher is the only problem, maybe reflashing it will do the trick.
** EDIT ** My apologies. I misunderstood. I thought you were referring to a corrupted recovery image that you had made of your ROM!
You say you can't boot into recovery/ what's your phone do or say when trying to boo4 in recovery? You may have to push new recovery image via fastboot.
CGriffiths86 said:
My recovery image seems to be messed up since I can't boot into it. My phone will boot but everytime it does ADW crashes over and over not allowing me to do anything. What can I do to go about getting the recovery fixed again and reflashing to try to smooth everything out?
Click to expand...
Click to collapse
If you have USB debugging turned on you can flash Amon_RA via an adb shell using the flash_image tool - exactly the way the original Eris rooting process worked. With your phone looping, it will run very slowly, but will still succeed.
If you have the S-OFF bootloader installed, you can flash the recovery with fastboot.
I'll have an XDA admin move this thread to the Q&A forum.
Ok guys..I got launcher pro installed so I can actually access my phone now. I attempted to Flash a recovery with Rom Manager and it says it succeeds but it will never boot into it. I do have the bootloader with the "off". Is there a market app or something that can easily flash the recovery? I only ask because I am not at my PC with the android sdk stuff.
CGriffiths86 said:
Ok guys..I got launcher pro installed so I can actually access my phone now. I attempted to Flash a recovery with Rom Manager and it says it succeeds but it will never boot into it. I do have the bootloader with the "off". Is there a market app or something that can easily flash the recovery? I only ask because I am not at my PC with the android sdk stuff.
Click to expand...
Click to collapse
If you can't get to a PC to use adb, you could use a root shell in a terminal emulator to flash recovery using flash_image. That's kind of painful/tedious though - almost enough so to make it worth your while to just wait until you get back to your PC.
It is technically feasible to put together a flashable ROM to re-flash the recovery, but I'm not aware of anyone having done so for the Eris.
Oh ok..well I have RA Eris 1.6.2 recovery on my sd card. So I can just flash it via the termninal emulator, right?
** I tried to install via terminal and it says "header is the same, not flashing recovery". Do you think I could install the stock Eris recovery and reflash Amon's?
UPDATE!!: I got a recovery to flash..YAY..thanks guys
CGriffiths86 said:
Oh ok..well I have RA Eris 1.6.2 recovery on my sd card. So I can just flash it via the termninal emulator, right?
** I tried to install via terminal and it says "header is the same, not flashing recovery". Do you think I could install the stock Eris recovery and reflash Amon's?
Click to expand...
Click to collapse
are you using "flash_image"? If so, where is it from? To my knowledge (the statically linked version from Amon_RA - /sbin/flash_image) is a pretty simplistic program - it performs no checks, and will let you flash total garbage to any named partition on your phone. (Which is why you should verify the md5 of the recovery image before you flash it, BTW; you can use the AFV app for that)
I've already read a billion posts here and on other web pages but of no use.
I ws running android froyo on my dell streak which I later upgraded to a custom ROM (gingerstreak) with base 2.3.3
Now I ws trying to change from the custom ROM to the official gingerbread ROM by ohlle. I used fastboot mode to do so. The entire process went fine however when my device booted after the update.pkg was installed, it got stuck at the dell logo.
It does not go into fastboot or recovery mode. QDL tools don't detect my device. It doesn't even switches off from the dell logo screen. I have to pull out the battery to reboot it only to get stuck at the dell logo screen again.
Please help me
Did you try to do a system restore?
rans4all said:
I've already read a billion posts here and on other web pages but of no use.
I ws running android froyo on my dell streak which I later upgraded to a custom ROM (gingerstreak) with base 2.3.3
Now I ws trying to change from the custom ROM to the official gingerbread ROM by ohlle. I used fastboot mode to do so. The entire process went fine however when my device booted after the update.pkg was installed, it got stuck at the dell logo.
It does not go into fastboot or recovery mode. QDL tools don't detect my device. It doesn't even switches off from the dell logo screen. I have to pull out the battery to reboot it only to get stuck at the dell logo screen again.
Please help me
Click to expand...
Click to collapse
i get the same problem whenever i try to install .pkg. you just download the update.zip file from the below link provided by the manni. install the recovery of update 406 then flash the update.zip you downloaded, it should work.
http://mirror2.streakdroid.com/manii/407/update.zip
Sent from my Dell Streak using XDA
nitin1978 said:
i get the same problem whenever i try to install .pkg. you just download the update.zip file from the below link provided by the manni. install the recovery of update 406 then flash the update.zip you downloaded, it should work.
http://mirror2.streakdroid.com/manii/407/update.zip
Sent from my Dell Streak using XDA
Click to expand...
Click to collapse
I think you need StreakMod Recovery to flash .zip files. Stock recovery to flash .pkg files.
rsfinsrq said:
I think you need StreakMod Recovery to flash .zip files. Stock recovery to flash .pkg files.
Click to expand...
Click to collapse
yes streakmod recovery is definitly needed, but still you'll get same problem if you try to install update.pkg, but if you flash update.zip it'll surely work... telling this as per my experience with same type of problem....
most important I think.... we cannot flash .pkg file using streakmod recovery if i am not wrong ?
i am sure OP means he CANNOT access recovery/fastboot with the usual buttons combination and just stuck at DELL logo.
i know because i also have the problem at this moment. dunno what to do..
QDL tool failed, Streakflash failed,
so help plss
Same case here...
-posible charge
-streakflash success but cannot entering fastboot
-QDL fail .. ERROR[D2]: wait ADB fastboot mode timeout! don't know how to intall ADB driver while Streak cannot entering fastboot with power+camera button
same problem
rans4all said:
I've already read a billion posts here and on other web pages but of no use.
I ws running android froyo on my dell streak which I later upgraded to a custom ROM (gingerstreak) with base 2.3.3
Now I ws trying to change from the custom ROM to the official gingerbread ROM by ohlle. I used fastboot mode to do so. The entire process went fine however when my device booted after the update.pkg was installed, it got stuck at the dell logo.
It does not go into fastboot or recovery mode. QDL tools don't detect my device. It doesn't even switches off from the dell logo screen. I have to pull out the battery to reboot it only to get stuck at the dell logo screen again.
Please help me
Click to expand...
Click to collapse
When you say "I used fastboot mode to do so" did you perhaps type in "fastboot -w" or "fastboot -erase" at some point? If you didn't then something became corrupted within the Streak. In any case, try to recall exactly what you did and post it.
The symptoms you describe point to one of two things that I can think of:
1. The Streak is bricked and will require someone with a JTAG device to resurrect.
2. The internal MicroSD has become unreadable and needs to be replaced.
Alright, so i have an EVO 4g lte and i attempted to root it today. It didnt turn out very well to say the least... I unlocked bootloader and flashed TWRP recovery.I then flashed superSU, and at the same time i flashed a custom rom and gapps zip. Then hit reboot. It has not booted up since.. It will just sit at the white HTC screen. i tried clearing cache and Dalvik cache, also did a factory reset. tried flashing cm10 rom onto the device as well as a rooted stock rom. nothing works! the farthest i have gotten was with the cm10 rom and it went to the cyanogenmod boot logo but was in bootloop still. I downloaded the ADT tool bundle but the phone wont show up on the device list. Can anyone help? im completely stumped.. Im fairly new to rooting and custom roms, but i have rooted multiple tablets and samsung galaxy phones and havent had any issues. this is my only phone also, i just gave my backup to my mother because her phone broke... please if anyone knows how to fix this let me know. when i boot into recovery mode it says Tampered and Unlocked at the top as well as S-On. I can also go into TWRP recovery with no problems. just cant use fastboot with my computer (windows 7 PC).
I am pretty sure i know what i did wrong, I flashed SuperSU to gain root at the same time i flashed the custom rom and gapps.. on all the other devices i would reboot after root and then flash the custom rom seperately.. but is there a way to correct my mistake?
Since you are s-on you have to fastboot flash the boot.img/kernel first and then flash CM and gapps
Any questions PM me
OK sorry to be a noob but how do I do that? I used cmd.exe while rooting but now it won't recognize my device. Much thanks for any help!!
Sent from my GT-P5110 using xda app
If in bootloader type fastboot devices
In recovery type adb devices
See if you get a reply
In fast boot USB menu on the phone, I typed fastboot devices on cmd and it came up blank.
Sent from my GT-P5110 using xda app
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
bigdaddy619 said:
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
Click to expand...
Click to collapse
ok ill uninstall all that and give it a try. is pm a better contact method for you?
AUSRA15 said:
ok ill uninstall all that and give it a try. is pm a better contact method for you?
Click to expand...
Click to collapse
Here is fine
bigdaddy619 said:
Here is fine
Click to expand...
Click to collapse
OK rebooting now I'll see if it uninstalled everything.
:fingerscrossed:
OK were connected now, now what? :good:
PC and phone are talking ?
fastboot devices
yes they are talking now. fastboot devices and my phone shows up.
i tried fastboot flash boot.img but it wont recognize the command, i placed the boot.img file into the platform-tools folder inside my C drive. what am i doing wrong? its late at night and im frustrated so i know im screwing something up...
ok good BTW which version of twrp are you using? Let me know before you continue.
pull the boot.img from the rom zip and copy it to the folder you opened your cmd window from
then type fastboot boot boot.img
once it says successful press the power button to return to HBOOT and use the vol keys to navigate to recovery
Once there choose wipe and wipe cache/dalvik cahce/system/data or factory reset depending which version of twrp you are using
then flash CM and gapps
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
AUSRA15 said:
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
Click to expand...
Click to collapse
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
bigdaddy619 said:
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
Click to expand...
Click to collapse
same thing, cannot load unknown error. also i am using twrp 2.6.0.0
Ok lets try something different at least it will get you up and running
Get twrp v2.4.1.0 from http://techerrata.com/browse/twrp2/jewel
put it in the same folder you are using and we will downgrade your twrp for now
copy and paste this in the cmd window
fastboot flash recovery openrecovery-twrp-2.4.1.0-jewel.img
then fastboot erase cache
ok got the twrp done succesfully as well as the wipe cache. whats next? i think i figured out what i was doing wrong, i hadnt opened the file directory. cd downloads, cd android files, etc.
should i try going into recovery now on the phone and flash a rom, or should we stay on fastboot and push the boot.img?
Easiest way to open a cmd window is to press shift and right click inside the folder and choose open cdm window here
That way you know you are in the correct folder.
Yeah go ahead and try to flash the boot.img again
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
Hi all
I am in big trouble. Please help me out.
I have HTC One X+ since last 1.5 years. It came with everything locked.
In order to install CyanogenMod i tried to root my HTC OneX+ and successfully did. The phone went back to factory settings.
After this, the real problem started. I downloaded a recovery.img and boot.img from somewhere over the net (I was careful but not sure if i downloaded the right one) and flashed it into my device. Afterwards, boom!!!!. My phone went into recovery loop and everything has been wiped out.
I am still able to fastboot it through my pc but nothing else.
Can anybody suggest what to do??
This is the right twrp recovery for the hox+:
http://dl.twrp.me/enrc2b/twrp-2.8.6.0-enrc2b.img
Download the rom you want to install and extract the boot.img from the zip.
In fastboot flash new recovery.Reboot into recovery and adb push rom's zip into your sd card.
Reboot in fastboot and flash boot.img.Reboot into recovery and flash rom.
Will try this and let you know. Thanks for the advise
If it doesn't work try to flash a working kernel first and then twrp recovery.
Coolgoly said:
If it doesn't work try to flash a working kernel first and then twrp recovery.
Click to expand...
Click to collapse
Because doing that will change the outcome.................Right?
It will make zero difference. The issue is the user.
As directed, i downloaded the twrp file and flashed it. Now the phone is getting into Recovery mode. Thanks!!
However, after that, i copied many compatible ROMs (Venom, Evagelincia, etc...), extracted their boot.img on my computer and flashed them one by one on my phone. Every time, the the process gets stuck. Each time i waited for 15-20 min for the boot to be flashed but nothing.
Did i miss something in between or i am not using the right boot.img?
pokharna said:
As directed, i downloaded the twrp file and flashed it. Now the phone is getting into Recovery mode. Thanks!!
However, after that, i copied many compatible ROMs (Venom, Evagelincia, etc...), extracted their boot.img on my computer and flashed them one by one on my phone. Every time, the the process gets stuck. Each time i waited for 15-20 min for the boot to be flashed but nothing.
Did i miss something in between or i am not using the right boot.img?
Click to expand...
Click to collapse
cmd needs to have ADMINISTRATOR access for fastboot on windows or you need to use SUDO on linux
OF course i used CMD as ADMINISTRATOR