true, u may b able to flash that way, but most people need to learn how to use adb and fastboot. if they brick their phone, they r gonna have to need to know how to install and use fastboot/adb, as they wont have access to their app. adb/fastboot is essential if u r gonna b playing with flashing anything. it will be the only way to recover.
lol, i meant no offense. im just letting people kno the downside to not learning how to install/use adb. it sounds like that could be a really useful tool to some people who have issues getting adb to work, but they should also realize the potential of adb and still work at getting it to work, even after using the app to flash recovery. :-)
have u tried googling "adb tutorial"? im sure u will get a lot of hits. please always use google or your favorite search engine as a point of reference before posting. if u arent able to find the info you need, we would be delighted to help! :-)
just flash cwm recovery and flash a new rom. i did the same thing with beats right after rooting. :-P it will fix it. if u just want the stock rooted rom, there is a link for that here too.
If anyone needs help using Recovery Flasher Utility to do this here are the steps:
(If you can't get this to work you shouldn't be trying anything more advanced...)
1. Download CWM-Recovery.img
2. Download Recovery Flasher Utility
3. Rename 'CWM-Recovery.img' to 'recovery.img'
4. Save it to your SD Card (Root, no folder)
5. Run RFU & follow the steps
6. Thats it! Reboot in to recovery to see your fancy new CWM-Recovery
***MUST BE ROOTED***
Even tho I havent learned myself I'm told ADB/Fastboot is VERY useful so theres the disclaimer
Last edited by Jeni_James; January 9th, 2013 at 06:35 PM.
jeni, if u r gonna b suggesting such an app, u need to include ALL instructions such as making sure the flash_image binary is in place, and the fact that they MUST b rooted. chances are that people who will be interested in using this app in place of adb/fastboot will more than likely either not have a PC, or is a noob, so ALL instructions are very necessary. it seems like this method WILL work for most people, but there is no escaping the fact that the adb/fastboot setup is proven tride-and-true, and is a lot more universally accepted of a method for flashing. dont get me wrong, this app may be very useful for noobz to get their recovery in place, but please dont dismiss adb/fastboot alltogether, as it is a MUCH more useful (notice i say useful, not easy) utility. if u r gonna promote this app, please also state the fact that learning how to use adb/fastboot is still very important.
Last edited by Dracable; January 9th, 2013 at 06:08 PM.
I never dismissed Adb/fastboot but I figured since Ive had people asking me (in PM) for instructions on my method Id post the steps
Most people who are trying ANY of this stuff know u need to be rooted
Also you don't need the Flash_image binary with this... I still haven't learned ADB/Fastboot & Im having no troubles using any of the stuff on this forum.
the instructions for the app specifically say:
"If the app fails to detect the flash_image binary, there is a high chance that this app will fail to work."
i just wanted to make sure that if people decide to go this route instead of adb/fastboot, that every bit of info is covered. thats all.
the flash_image binary is located within this thread right next to the link for the cwm image.
and the ONLY reason im pushing adb/fastboot is because if something were to go wrong with flashing, adb/fastboot will b necessary to recover ur phone from a bricked state. im not saying this is a BAD utility, im just saying that adb/fastboot is fairly easy to learn and worth the extra effort if u r gonna b flashing things to ur phone. we are more than happy to help anyone learn, at least i am! ;-)
Last edited by Dracable; January 9th, 2013 at 07:05 PM.
jeni, r u sure u didnt just already have the flash_image binary left over on ur sd card from a previous attempt to flash recovery via fastboot when u were attempting to learn it?
I saw that, I have said flash_image binary but that program has never asked me for it. It just asks for recovery.img to be in the root of the SD. Thats odd that it mentions that in the description cuz EVERYONE I've helped with it hasn't even had that file but its worked no problem. I'll email the dev & find out what he means
I was able to root my Virgin Mobile PCD Venture cell phone, and I installed Busybox as recommended in the instructions. I have no clue of what to do next. My reason for rooting the phone is because I want to use Foxfi full version on my venture. Could someone please instruct me on what to do. I've downloaded foxfi to my venture, and installed it, but I can't get foxfi to stay active. When I click the on function, the count begins 1 2 3. Then it goes hotspot active for a half second, and then hotspot off. Please, please help.
I was able to root my Virgin Mobile PCD Venture cell phone, and I installed Busybox as recommended in the instructions. I have no clue of what to do next. My reason for rooting the phone is because I want to use Foxfi full version on my venture. Could someone please instruct me on what to do. I've downloaded foxfi to my venture, and installed it, but I can't get foxfi to stay active. When I click the on function, the count begins 1 2 3. Then it goes hotspot active for a half second, and then hotspot off. Please, please help.
there is a file on the phone called /system/build.prop
in it is a setting ro.tethered.denied=1
this must be set to 0
If you rooted successfully, you should be able to change this from the phone using a root file-explorer/editor. I use ES File Explorer. If you install ES File Explorer to do this, you have to go into settings and enable root explorer and up to root and mount file system...
Then make the above change to /system/build.prop
Then you have to reboot the phone [so the phone will load the build.prop settings]
I got tethering working with barnacle without this. The reason [I believe] is because Barnacle sets the wifi up in adhoc mode and the ro.tethered.denied is virginmobile's way of keeping your venture from setting the wifi up as an access point in infrastructure mode. It is why none of the market tethering apps work except Barnacle, tho there may be other apps in market now that use adhoc.
The Following User Says Thank You to ww227 For This Useful Post:
ive gotten both barnacle and wifi tether to work without modifying the build.prop. modding the build.prop didnt seem to yeild any results for me. my advice is to use barnacle if u are looking to use ur phone as a hotspot.
wifi tether will work, but u need to change up some of the options to get it to work correctly, and i dont remember which options they were, at the moment. barnacle works great out-of-the-box. hope that helps!
Last edited by Dracable; January 16th, 2013 at 10:08 PM.
Device(s): PCD/ZTE/Alcatel Virgin Mobile Venture/JukeB
Carrier: Not Provided
Thanks: 16
Thanked 32 Times in 16 Posts
Quote:
Originally Posted by ww227
there is a file on the phone called /system/build.prop
in it is a setting ro.tethered.denied=1
this must be set to 0
If you rooted successfully, you should be able to change this from the phone using a root file-explorer/editor. I use ES File Explorer. If you install ES File Explorer to do this, you have to go into settings and enable root explorer and up to root and mount file system...
Then make the above change to /system/build.prop
Then you have to reboot the phone [so the phone will load the build.prop settings]
I did this. After rebooting I checked in case build.prop was reverted and it was not, it says ro.tethered.denied=0, but I still get "Hotspot blocking notification" when I try to enable standard hotspot. (I used Quick Settings but plenty of other apps toggle the same standard hotspot function.)
Device(s): PCD/ZTE/Alcatel Virgin Mobile Venture/JukeB
Carrier: Not Provided
Thanks: 16
Thanked 32 Times in 16 Posts
Barnacle works for me too, as I've mentioned before in other threads. This isn't currently important to me, it's just an exploration/learning process. In the future I may want to use a device that doesn't support ad-hoc.
roadkill42, i sent u a private message. ill help u there. lets keep this board decluttered, as almost every possible question has been answered somewhere in this thread. fyi to everyone, i plan on writing up a full and complete guide to installing cwm and flashing roms on the Venture. it will be targeted for noobs and will be easy to understand. our recovery info has been quite spread out and cluttered, so to avoid further confusion, i will be releasing it soon, as long as i get the permission from the OP.
i was able to flash cwm on my venture via fastboot after i had already got it stuck in a bootloop. just waitin on that stock rom to get back up and goin!
can u text me back have a few questions thanks
Last edited by roadkill42; May 14th, 2013 at 05:57 AM.
People, I'm really confused. So you download the files and then you somehow install them because I've downloaded the files and it says "Application not available" when I click on the files. D:
u need to read thru all 3 pages of the recovery thread buddy... its a process of getting adb/fastboot on ur PC, and then flashing the image to your phone from your pc. read everything carefully first.
ok. u already downloaded the 2 files at the beginning... on ur pc, download pdanet (look for a link in the thread) and install. next, download android sdk and install (link also in thread). pay attention to the folder u installed sdk to. after u r done installing the sdk, copy the first 2 files u downloaded (the recovery files) into the "platform-tools" subfolder of ur sdk folder. after that, open a command prompt, point it to the platform-tools subdirectory of your sdk folder, and copy each line of code (listed at the beginning of this thread) one at a time into command prompt. if u followed directions closely and there were no issues, cwm should now be flashed.
When I put in the first code for the flash it says "cannot stat 'flash image' :No such file or directory"
Is there something I am doing wrong? I followed every step. :/
Device(s): PCD/ZTE/Alcatel Virgin Mobile Venture/JukeB
Carrier: Not Provided
Thanks: 16
Thanked 32 Times in 16 Posts
Approximately the past 50 posts in this thread have been about "cannot stat 'flash-image': No such file or directory". Here is a review of the relevant posts since the first one about that error, to make it easier to review for people having that error. Please also review the first page of the thread. Next I'll try to write up some more specific advice.
Quote:
Originally Posted by isaac188
I am having trouble trying to flash this recovery the way u guys are saying. I have read and re-read every post. I placed the two files into the folder called platform-tools. That is right? Now when i try to adb push the file with the first command from the abov directions and it tells me cannot stat 'flash_image' : no such file or directory.. I don't get it. I am new to flashing recoveries so any help appreciated. Google has been no help to me as i continue my quest. Thanks in advance.
Quote:
Originally Posted by Dracable
the process is all there. just read every step and do it as you read. are you pointing the command prompt to platform-tools in your sdk folder with the "cd" command before trying the adb command?
Quote:
Originally Posted by divinebovine
Copy and paste what you see when this happens so we can see what leads up to it.
Quote:
Originally Posted by isaac188
Ive never flashed or used adb before because i never had to. I need to know how to point adb to c:/adnroid/sdk/platform-tools which is where i have the two downloaded files. I tried to ask google but it sucks ass. Then if i point to there and i copy and paste the commands in the top of the post it should flash the recovery? im trying to learn with as less questions asked its not easy.
Itll reflash the recovery file & POOF it works, Ive done it a 2x on 2seperate phones & this works GREAT, no issues, no problems. SIMPLE
Quote:
Originally Posted by Dracable
true, u may b able to flash that way, but most people need to learn how to use adb and fastboot. if they brick their phone, they r gonna have to need to know how to install and use fastboot/adb, as they wont have access to their app. adb/fastboot is essential if u r gonna b playing with flashing anything. it will be the only way to recover.
Quote:
Originally Posted by Jeni_James
If anyone needs help using Recovery Flasher Utility to do this here are the steps:
(If you can't get this to work you shouldn't be trying anything more advanced...)
1. Download CWM-Recovery.img
2. Download Recovery Flasher Utility
3. Rename 'CWM-Recovery.img' to 'recovery.img'
4. Save it to your SD Card (Root, no folder)
5. Run RFU & follow the steps
6. Thats it! Reboot in to recovery to see your fancy new CWM-Recovery
***MUST BE ROOTED***
Even tho I havent learned myself I'm told ADB/Fastboot is VERY useful so theres the disclaimer
Quote:
Originally Posted by Dracable
jeni, if u r gonna b suggesting such an app, u need to include ALL instructions such as making sure the flash_image binary is in place, and the fact that they MUST b rooted. chances are that people who will be interested in using this app in place of adb/fastboot will more than likely either not have a PC, or is a noob, so ALL instructions are very necessary. it seems like this method WILL work for most people, but there is no escaping the fact that the adb/fastboot setup is proven tride-and-true, and is a lot more universally accepted of a method for flashing. dont get me wrong, this app may be very useful for noobz to get their recovery in place, but please dont dismiss adb/fastboot alltogether, as it is a MUCH more useful (notice i say useful, not easy) utility. if u r gonna promote this app, please also state the fact that learning how to use adb/fastboot is still very important.
Quote:
Originally Posted by Jeni_James
I never dismissed Adb/fastboot but I figured since Ive had people asking me (in PM) for instructions on my method Id post the steps
Most people who are trying ANY of this stuff know u need to be rooted
Also you don't need the Flash_image binary with this... I still haven't learned ADB/Fastboot & Im having no troubles using any of the stuff on this forum.
This DOES work for anyone.
Baby steps folks
Quote:
Originally Posted by Dracable
the instructions for the app specifically say:
"If the app fails to detect the flash_image binary, there is a high chance that this app will fail to work."
i just wanted to make sure that if people decide to go this route instead of adb/fastboot, that every bit of info is covered. thats all.
the flash_image binary is located within this thread right next to the link for the cwm image.
and the ONLY reason im pushing adb/fastboot is because if something were to go wrong with flashing, adb/fastboot will b necessary to recover ur phone from a bricked state. im not saying this is a BAD utility, im just saying that adb/fastboot is fairly easy to learn and worth the extra effort if u r gonna b flashing things to ur phone. we are more than happy to help anyone learn, at least i am! ;-)
Quote:
Originally Posted by Bohka209
When I put in the first code for the flash it says "cannot stat 'flash image' :No such file or directory"
Is there something I am doing wrong? I followed every step. :/
Quote:
Originally Posted by HeyItsJoeyG
I get cannot stat 'flash-image': No such file or directory
Quote:
Originally Posted by Dracable
did you make sure to copy it to the platform-tools directory of the SDK on your PC before starting the process?
Device(s): PCD/ZTE/Alcatel Virgin Mobile Venture/JukeB
Carrier: Not Provided
Thanks: 16
Thanked 32 Times in 16 Posts
When asking about it, please copy and paste enough code (or a screenshot) for us to see what you did before you got the error and exactly how the error showed up. That error can actually come from different commands.
Quote:
Originally Posted by Bohka209
When I put in the first code for the flash it says "cannot stat 'flash image' :No such file or directory"
Is there something I am doing wrong? I followed every step. :/
If by "the first code" you mean "adb push flash_image /data/local/tmp/flash_image", you need to make sure that flash_image is in the current working directory on your computer, and that /data/local/tmp on the phone can be written.
If you aren't good at moving files around, you can instead go to where the file is. You'll need to specify the full path to adb. It might be something like
C:\> D:
D:\> cd d:\myAndroidDownloadFolder
D:\myAndroidDownloadFolder> C:\Program Files\android-sdk-windows\tools\adb push flash_image /data/local/tmp/flash_image
To make sure /data/local/tmp on the phone can be written, use adb shell and enter these commands:
$ su
# cd /data/local
# ls -ld tmp
The output should begin with a string of letters and hyphens like drwxr-xr-x. The first four letters should be drwx and the end of the line should say "tmp/".
Quote:
Originally Posted by HeyItsJoeyG
I get cannot stat 'flash-image': No such file or directory
Quote:
Originally Posted by HeyItsJoeyG
First I'm mac And YES Plus ADB Wifi to connect
Screenshots would definitely help, or at least an indication of which step you're on. Also, I'm experimenting with Mac lately, could you point me to whatever instructions/programs you're using?
Device(s): PCD/Alcatel Venture, Samsung Glaxay Tap 2 7.0
Carrier: Virgin Mobile
Thanks: 0
Thanked 0 Times in 0 Posts
[divinebovine;5823323]When asking about it, please copy and paste enough code (or a screenshot) for us to see what you did before you got the error and exactly how the error showed up. That error can actually come from different commands.
If by "the first code" you mean "adb push flash_image /data/local/tmp/flash_image", you need to make sure that flash_image is in the current working directory on your computer, and that /data/local/tmp on the phone can be written.
If you aren't good at moving files around, you can instead go to where the file is. You'll need to specify the full path to adb. It might be something like
C:\> D:
D:\> cd d:\myAndroidDownloadFolder
D:\myAndroidDownloadFolder> C:\Program Files\android-sdk-windows\tools\adb push flash_image /data/local/tmp/flash_image
To make sure /data/local/tmp on the phone can be written, use adb shell and enter these commands:
$ su
# cd /data/local
# ls -ld tmp
The output should begin with a string of letters and hyphens like drwxr-xr-x. The first four letters should be drwx and the end of the line should say "tmp/".
Screenshots would definitely help, or at least an indication of which step you're on. Also, I'm experimenting with Mac lately, could you point me to whatever instructions/programs you're using?
I am using the app Jeni_James referred.
Last edited by HeyItsJoeyG; May 14th, 2013 at 05:19 PM.
well, have u tried going with the adb/fastboot route? adb and fastboot are the standard for flashing files to android partitions. technically, the flasher utility is not supported for all devices, including ours. it may work, but if u are having issues with it, i would suggest installing the android sdk and using adb or fastboot to flash.
the flash tool in google play works on venture with out any problems i done a couple since my pc went down but like drac said adb be better way its safer thought i say drac nows his stuff he helped me on my first he aculay did throughj his phone to my pc .thanks for all ,the others here for ur help ur great:-):-)
yup. some people the flasher utility works for, some it doesnt. adb will work for everyone tho. thanks for the kind words! yup, one of the many remote connections i have made (via android to pc while at work! haha) to help people set up adb and help them flash recovery. ;-)
13Likes
