So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Sounds to me like a permissions issue. I had that after I fiddled with the contacts database to unrestrict pictures from third party apps. I would double check any files you modified and make sure they got chmod'ed back to what they should be.
You will have to somehow access the Settings to re-enable adb. When you did a factory reset, you disabled USB Development (aka adb).
For now the only known way to recover is through adb. No fastboot or signed update.zip for now.
navalynt said:
So I as working on theming the Adeo ROM and must have messed something up. I didn't think it had to do with the framework files I had pushed so I did a factory reset to clear off all the 3rd party apps from the phone.
Well, since that reset, I can't access the phone in ADB, settings FC's, Market FC's, and I can't download/install an APK because of the security restrictions.
The phone is "functional", I can place/receive calls/sms and use the browser. USB to the PC works for everything except getting ADB access. I verified I can get it to recognize for RSDLite and for Fastbook so I figure using one of those methods should (eventually) provide me an avenue to get my phone 100% functional again.
Does anyone happen to have or know where I could find signed files for Fastboot to replace the entire /system partition or an SBF file to flash the phone back to stock? Or possibly any other solutions?
Also, before I get flamed as a n00b who broke a phone, I've worked on over a dozen different Android handsets and I was well aware I was working without a safety net. This is NOT my primary phone so if I need to I can patiently wait for an SBF to leak. I'm just checking to see if anyone knows any solutions already so I can get back to theming.
Click to expand...
Click to collapse
When I lost ADB access because of a hard reset (I think), this is what I did to fix my issue: http://forum.xda-developers.com/showthread.php?t=974824
I never lost root after a hard reset so I went to the market and bought root explorer and sqlite editor and copied the adbd to the /sbin folder to fix adb. I then bought sqlite editor and followed this: http://forum.xda-developers.com/showthread.php?t=972760 to re-enable side loading of apps. To install apps that I had the apk's for.
I still lose adb after a reset, but I can copy the adbd file to the /sbin folder and adb works again until I reset the phone.
I made a post about losing adb access on the motorola support forums: https://supportforums.motorola.com/message/332307#332307 to see if there were any solutions, but Mark said he would get back to me after trying to reproduce my problem.
I hope this helps.
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
No problem. That sucks, I'm not sure what you can do. Hopefully motorola or someone here will get a sbf soon so we can mess with our phones and have a way to fully recover. I hope you get it working again. Good luck!
navalynt said:
I think I'm just up **** creek without a paddle for the moment because I can't connect via ADB, the Market force closes, and the security restrictions won't let me side-load any applications via download from the browser. I can't manually add ADB because I have no way to move the files to where they need to be.
Thanks for the replies! airbillion, I'm following your thread at the Motorola Owners' Forum to!
Click to expand...
Click to collapse
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
shadowscreation said:
Have u not tried sideload wonder machine love that thing used it alot when my wife had her backflip
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Requires USB Debugging to be enabled, but I have no access to enabled it due to Settings force closing and no ADB access in pre-boot.
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
adlx.xda said:
Could you download Android Terminal Emulator 's apk to your sdcard, then install it using a apk install you may already have that work.
If you can get any terminal access from your phone, do a su, then launch /sbin/adbd. This should hopefully give you adb shell access. Without needing to enable USB debugging.
Click to expand...
Click to collapse
It won't let me install a downloaded APK because of the security restriction.
If you have an SD card, try booting into recovery with an update.zip on the file.
I can get into the recovery, but the update.zip file needs to be signed. I created one that will push the original copies of the framework files I was working with but it won't install because it's signed with test keys. The stock recovery 3e needs update.zip files signed with the manufacturer release-keys which only Motorola has.
https://supportforums.motorola.com/thread/46051?tstart=30
I started a thread on the official Motorola Owner's Forum in hopes I can find a full factory restore method for the OS. It's unfortunate that unlike HTC and other manufacturers who release full wipe RUU files Motorola has chosen to keep their restore files internally.
http://www.4shared.com/file/7YXo_gmO/update.html
That's the link to the update.zip file I was trying to use that fails because it's only signed with test-keys.
Retracteddd
Related
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Android Cowboy said:
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
johnnydowngrief said:
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
Click to expand...
Click to collapse
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Android Cowboy said:
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Click to expand...
Click to collapse
Then maybe this. http://forum.xda-developers.com/showthread.php?t=1379875 But I'm just guessing here. I dont want to spam this thread. Maybe someone more experienced can help you.
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I will try that. If I could just push a new build.prop to overwrite the old one I put probably be okay. How did restore system files using ADB.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That didn't work for me, I've also trying factory resetting again multiple times through recovery, but no dice.
I got my fastboot cable working, and was able to get the device recognized as "Qualcomm USB modem converter"
I opened a thread about it, any help is appreciated!
Android Cowboy said:
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
Click to expand...
Click to collapse
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
GSLEON3 said:
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
Click to expand...
Click to collapse
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Android Cowboy said:
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Click to expand...
Click to collapse
Did you try either of these drivers:
http://www.4shared.com/rar/kRIFBtGe/qualcomm_hsusb_device_drivers.html
http://drivers.softpedia.com/progDo...dows-7-x64-Windows-8-x64-Download-179130.html
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Since you didn't factory reset, does it show up on adb devices at all while it's trying to boot ?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
So currently its not showing up on adb while its booting, but that's probably because I haven't updated adb in a while. I'm going to update when I get home from work and report back.
EDIT: So I update ADB, which isn't recognizing it, but oddly enough, my computer can see it even after the screen shuts off as an android device. My only guess then is I'm missing a driver or something. Any suggestions?
Android Cowboy said:
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
S_transform said:
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
Click to expand...
Click to collapse
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Android Cowboy said:
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Click to expand...
Click to collapse
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
S_transform said:
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
Click to expand...
Click to collapse
When you ADB shell, are you seeing a "#" which means you are rooted. I'm not the world's expert on ADB but this should help. Once you are shell and rooted you can just chmod 644 or 777 on /system and see if that works. http://gizbeat.com/2103/how-to-change-file-permissions-through-adb/
Howdy folks,
Yesterday, I was the proud owner of a sleek little TCT.Alcatel OneTouch A554C, formally know as a Virgin Mobile Venture running Android version 2.3.5.
It was successfully and surprisingly easy to root by utilizing 2 cool little apps, Ministro and Poot-Debug.
After root, I subsequently downloaded some root tools (eg., Titanium Backup Pro, Superuser Elite, System App Uninstaller).
That was last week.
Yesterday, I got a bit cocky. I needed to clear up some internal memory so I used "System App Uninstaller" to uninstall a few apps. If I remember correctly, the apps were as follows: Google Maps, Google Maps Street View, Calculator, Digital Clock, Setup Wizard, Android Live Wallpaper, Live Wallpaper Picker, Magic Smoke Wallpaper, Music Visualization Wallpaper, and the TouchPal Keyboard French and Spanish Language Packs.
So far so good, right? However, I believe I may have snarfed-up when I uninstalled the Setup Wizard. But I'll get to that in a minute.
Now with Titanium Backup, I moved some apps to the sd card. Included was the stock launcher, Smart Launcher Pro, SPB Shell, AVG Anti-Virus, and Superuser Elite. Then I rebooted through Titanium Backup and I haven't viewed any pornographic material since!
After reboot, the phone got stuck on the final boot animation frame. I panicked, pulled the battery, booted into recovery then rebooted a 2nd time.
This time it booted to the pull-down lock screen. I unlocked and seen:
"Sorry! The application com.android.setup wizard has stopped unexpectedly. Please try again." Along with a "Force Close" option. I forced closed and the screen went black with the exception of the status bar. The phone is still on but otherwise...nada.
When I press the power button, same thing happens: pull-down lock screen, screen goes black. Or sometimes, it will turn on and boot loop.
Major panic time!!! I booted into recovery again and performed a factory reset to no avail.
Another clue to note: I can connect & access the sd card via usb to desktop.
Also, I did have the good sense to backup all apps, system and user, through ES File Explorer and stored them both on sd card and in the cloud via Yandex Disk prior to this bricking fiasco. Now, what do I do with them? I now realize it was possibly a mistake moving all 3 launchers to the sd card. How do I get the stock launcher back to the phone?
Or, should I:
1- Attempt a base rom reinstall or
2- Attempt a custom rom install or
3- Use it solely as a time piece/mass storage device or
4- Throw it very hard and very ******* far away from me!?
I realize this is an obscure little cheap phone but it's the only one I have. Any valid feedback would be greatly appreciated.
You can go to the Play Store on any browser and choose a launcher to install. Or if you have USB Debugging on, you can side load an launcher apk. Or if you install a custom recovery, you can install another rom or sideload an apk there. Or you can flash the original firmware via SP Flash Tool.
Lots of options and none of them need to be throwing it against the wall.
es0tericcha0s said:
You can go to the Play Store on any browser and choose a launcher to install. Or if you have USB Debugging on, you can side load an launcher apk. Or if you install a custom recovery, you can install another rom or sideload an apk there. Or you can flash the original firmware via SP Flash Tool.
Lots of options and none of them need to be throwing it against the wall.
Click to expand...
Click to collapse
Hmmm...Ok, thanks. Dig your username, by the way.
First thing is, install from play store would be possible if I had data service or if I was able to enable wi-fi. I only have calling & texting service on this phone and as for wi-fi, I can't enable it due to the problem of not being able to access the settings menu. All I have when it does boot, and it only fully boots when it is connected to a PC, is the pull-down lockscreen displaying time, date, status bar and the original wallpaper. Pull it down and the screen goes black with status bar still displayed along with time & battery level.
Secondly, USB debugging was enabled prior to all of this but I panicked & performed a factory reset. Don't think it's still on.
And lastly, is installing either a custom recovery, (which, to be frank, I'm just not that savvy) another rom or flashing original firmware even possible without a PC? Because I only have access to a PC without administrative privileges so therefore...no installing exe's without a password. Maybe this program lab will allow me, quite possibly not.
Hell, would I even still have root after a reset/data wipe?
Thanks, anyway, Esoteric Chaos
Off subject: The Joker was an Agent of Chaos. Loved Heath Ledger as The Joker.
Silver Rivers said:
Hmmm...Ok, thanks. Dig your username, by the way.
First thing is, install from play store would be possible if I had data service or if I was able to enable wi-fi. I only have calling & texting service on this phone and as for wi-fi, I can't enable it due to the problem of not being able to access the settings menu. All I have when it does boot, and it only fully boots when it is connected to a PC, is the pull-down lockscreen displaying time, date, status bar and the original wallpaper. Pull it down and the screen goes black with status bar still displayed along with time & battery level.
Secondly, USB debugging was enabled prior to all of this but I panicked & performed a factory reset. Don't think it's still on.
And lastly, is installing either a custom recovery, (which, to be frank, I'm just not that savvy) another rom or flashing original firmware even possible without a PC? Because I only have access to a PC without administrative privileges so therefore...no installing exe's without a password. Maybe this program lab will allow me, quite possibly not.
Hell, would I even still have root after a reset/data wipe?
Thanks, anyway, Esoteric Chaos
Off subject: The Joker was an Agent of Chaos. Loved Heath Ledger as The Joker.
Click to expand...
Click to collapse
You can go to ANY browser - even on the PC and log into your account and hit Install and it will send the command to your phone to install it. Pretty nifty. But you did say you factory reset, so that isn't actually going to work. Sorry.
The rest of the stuff would require a PC, though I don't think admin rights are needed, so there's that...
If you don't have your phone logged into Google or USB Debugging enabled, you're kind of stuck without a PC.
es0tericcha0s said:
You can go to ANY browser - even on the PC and log into your account and hit Install and it will send the command to your phone to install it. Pretty nifty. But you did say you factory reset, so that isn't actually going to work. Sorry.
The rest of the stuff would require a PC, though I don't think admin rights are needed, so there's that...
If you don't have your phone logged into Google or USB Debugging enabled, you're kind of stuck without a PC.
Click to expand...
Click to collapse
Well, on these PCs it certainly does. I thought I was on track yesterday and tried to install a copy of Odin that I found. Can't install without a frigging admin pass.
Someone else just suggested I try a stock rom flash. Might as well, right? Happen to know where I could find a good reliable copy? That also happens to be free?
Not sure why you were trying to use Odin for a non Samsung phone...?
The stock rom flash would only be possible via PC or if you had a custom recovery installed.
Here's what you would need to do for the Virgin Mobile Venture:
Download CWM: http://www.sendspace.com/file/4gt04i
Download adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download rom: http://goo.im/devs/LeslieAnn/Venture/Stock_Venture.zip - Put on SD card.
Drivers: http://pdanet.co/bin/PdaNetA4150.exe (this program is for USB tethering and installs the adb drivers for your phone as well as many others)
The CWM img will need to be in the folder you unzipped for adb/fastboot. You'll need to boot to fastboot mode by powering on with while holding Volume Up.
Open a terminal prompt and change directories to your adb/fastboot folder. Then run this command:
fastboot flash recovery nameofrecovery.img - fill in the nameofrecovery with whatever the CWM file name is.
(if this doesn't work - make sure that your PC is reading the phone correctly by using the command: fastboot devices . If you don't get anything back, make sure you check the Device Manager for errors. If you have them, try reinstalling the drivers and rebooting the PC)
Then pop the battery out and then reboot to recovery via powering on while holding volume down. Once there, you should be able to do a factory reset and then install the stock rom zip. The volume keys should scroll through selections and the Enter key for accept, or Power if that doesn't work. Not really sure about this particular phone.)
Actually, you might just be able to use adb to install a launcher apk once you have CWM installed. Might be a little easier.
launcher apk must be in adb folder then while in CWM:
adb install nameoflauncher.apk
Note: You can rename zips and apks to be easier to type the commands.
es0tericcha0s said:
Not sure why you were trying to use Odin for a non Samsung phone...?
Click to expand...
Click to collapse
Yeah, me either. I was all over the place yesterday grasping at anything. So Odin is only for Samsungs, huh? Guess I can delete the exe file from my sd.
Right then. I'm about to proceed with your advice. Cross your fingers and toes.
Thanks mate!
The CWM img will need to be in the folder you unzipped for adb/fastboot.
Click to expand...
Click to collapse
and
launcher apk must be in adb folder then while in CWM
Click to expand...
Click to collapse
Wait, what? Please excuse my ignorance, but am I missing something. ADB didn't come in a zip. It's an installer. I think you may have to dumb this down a bit more, mate.
Silver Rivers said:
and
Wait, what? Please excuse my ignorance, but am I missing something. ADB didn't come in a zip. It's an installer. I think you may have to dumb this down a bit more, mate.
Click to expand...
Click to collapse
Sorry, I meant in the folder that it extracts the files too.
es0tericcha0s said:
Sorry, I meant in the folder that it extracts the files too.
Click to expand...
Click to collapse
Right, got it.
Silver Rivers said:
Right, got it.
Click to expand...
Click to collapse
If you can't run the exe file, then let me know, and I'll just upload a zip / folder with the necessary files. You do not need admin access to run the adb commands.
es0tericcha0s said:
If you can't run the exe file, then let me know, and I'll just upload a zip / folder with the necessary files. You do not need admin access to run the adb commands.
Click to expand...
Click to collapse
That would be really cool, actually. But check this out:
I talked someone into allowing me to utilize his laptop. I installed ADB, moved the Launcher APK to the folder suggested, ran the commands but the command prompter responded with "waiting for device" and progressed no further. Could it be a driver issue? I was under the impression that if the PC recognizes your device (which it did) then a new driver install was not necessary.
Dude was real cool about it even though I ran his battery down quite significantly and didn't even accomplish anything.
So, if I had the ADB files then I could just copy them to...say the PC desktop and run the command prompter from there? If so, then yes please upload and I'll just try it that route rather than rely on someone's personal PC. Know what i mean?
I do appreciate all of this. I'm getting quite the education here. If you ever get married, let me know and I'll come and dance as my favor to you.:good:
Peace...I'll return tomorrow.
What mode were you in when trying to install? The laptop had the most up to date drivers? You checked the Device Manager to make sure there was no yellow exclamation mark next to the phone? It's not unheard of for the PC to recognize in one mode, but not load the correct drivers in another, as there are different drivers for the phone depending on if it is booted, in recovery, or download mode or whatever they call it for that phone. Just make sure to get the PDAnet drivers installed and reboot. That should do the trick.
Everything else you should need will be in here:
https://dl.dropboxusercontent.com/u/9903887/adbfastboot.zip
es0tericcha0s said:
What mode were you in when trying to install? The laptop had the most up to date drivers? You checked the Device Manager to make sure there was no yellow exclamation mark next to the phone? It's not unheard of for the PC to recognize in one mode, but not load the correct drivers in another, as there are different drivers for the phone depending on if it is booted, in recovery, or download mode or whatever they call it for that phone. Just make sure to get the PDAnet drivers installed and reboot. That should do the trick.
Everything else you should need will be in here:
https://dl.dropboxusercontent.com/u/9903887/adbfastboot.zip
Click to expand...
Click to collapse
I was in Recovery and I was also attempting to install the just the Launcher versus the entire ROM. And I was also feeling a tad bit rushed, cause dude was right there informing me of his battery status. "Well, it's down to 30%." Then 2 mins later.."Ok, looks like it just fell to 25%."
Haha...so yeah, with him pressuring me, I spaced on checking the device manager. This desktop that I'm on today seems to be cool. Just checked the manager & it informs me that my device is 'working properly'.
Off to give it another bloody joust, mate. Wish me luck...
Can you fully explain how to do this
es0tericcha0s said:
Not sure why you were trying to use Odin for a non Samsung phone...?
The stock rom flash would only be possible via PC or if you had a custom recovery installed.
Here's what you would need to do for the Virgin Mobile Venture:
Download CWM: http://www.sendspace.com/file/4gt04i
Download adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download rom: http://goo.im/devs/LeslieAnn/Venture/Stock_Venture.zip - Put on SD card.
Drivers: http://pdanet.co/bin/PdaNetA4150.exe (this program is for USB tethering and installs the adb drivers for your phone as well as many others)
The CWM img will need to be in the folder you unzipped for adb/fastboot. You'll need to boot to fastboot mode by powering on with while holding Volume Up.
Open a terminal prompt and change directories to your adb/fastboot folder. Then run this command:
fastboot flash recovery nameofrecovery.img - fill in the nameofrecovery with whatever the CWM file name is.
(if this doesn't work - make sure that your PC is reading the phone correctly by using the command: fastboot devices . If you don't get anything back, make sure you check the Device Manager for errors. If you have them, try reinstalling the drivers and rebooting the PC)
Then pop the battery out and then reboot to recovery via powering on while holding volume down. Once there, you should be able to do a factory reset and then install the stock rom zip. The volume keys should scroll through selections and the Enter key for accept, or Power if that doesn't work. Not really sure about this particular phone.)
Actually, you might just be able to use adb to install a launcher apk once you have CWM installed. Might be a little easier.
launcher apk must be in adb folder then while in CWM:
adb install nameoflauncher.apk
Note: You can rename zips and apks to be easier to type the commands.
Click to expand...
Click to collapse
I have a old ass iMac desktop that has not been used in 5plus years at all and I'm a mother of 3 with no clue how to do any of this if you can dumb it down for me that would be very help full as well I have no clue where to download any of the needed files please help. My email is [email protected]
Thank you
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
After trying for a few weeks now, I've still had no success. One idea has come to me though- installing a rom. Would downloading a custom ROM change my hosts file? Also, if so, could anyone recommend one that is similar to default android? One last idea that I've got at the moment is sonehow completely wiping the hard drive of the phone and reinstalling androud on it, though I have no idea whether that is even possible, and if so, how to do it. I would really appreciate some help here!
Thanks again,
Louis
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
J2270A said:
After reading, I can only talk as one who knows less than you.
Let me say this from the start.
Root=/= unlock bootloader
Find a way to unlock boot loader first, with a Google search.
Use fastboot to flash a recovery (.IMG) made for your phone. fastboot is something like adb.
Let's just say that that is more complicated than rooting. It gave me a headache at first.
_______/
Pertaining to your problem, how about a reflash of the system image?
The official lg mobile support tool may help you with this.
Search for your phone model on the lg support page, look under manuals and downloads, then under software update.
Click to expand...
Click to collapse
I'm not entirely sure I understand you here, but I'll try. What would unlocking the bootloader do to my phone? Would it enable r/w on the system folder? Also, what is a reflash of the system image? How would I do that?
I'll try these things if I can, but would still appreciate help.
Look around on http://wiki.cyanogenmod.org/w/Basic_concepts?
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
J2270A said:
Look around on [I can't post urls yet ]
It should give you some info in flashing and unlocking.
It can give people quite a headache, with all those terms.
________
As for the part under the line, I'm talking about a restoring of the phone to the default state via official methods.
Instructions would be given by the official support programme.
Click to expand...
Click to collapse
Ok, so from what I can work out, cyanogen does not support my device. Would doing it for a similar device work? Are there any ROMs that support my device?
under the line, restoring the phone via the official ways actually just wipes the user data, not including the HOSTS file which is what I need to wipe. What I really need it is basically a ROM that completely wipes my phone and reinstalls some version of android.
Any other ideas?
While there may not be official support for a phone for a custom ROM, you may be able to find unofficial ports/versions if you search for it in the forums.
From what I know, a system reinstall via official methods wipes data and almost everything else, then downloads from its servers system files to be installed to the phone. At least, my phone was reverted to a stock ROM when I restored it after using a custom ROM. It may be different for some, but generally, this is what I think.
Important: only use a ROM made for your device model only, do not use the ones made for a similar phone, the small differences are no longer small in this case and will cause a system error(?)
Generally, once you have successfully unlocked boot loader using a method for your phone, the instructions afterwards are generally the same for all phones. You'll be able to get better answers in the threads specifically for your phone, so try to look for one and look for the already tried methods,
Here's one:
<You'll need to quote to copy link>
Louietheflyisme said:
Hello everyone,
I use an LG Optimus L4 II (e445). I rooted it but then decided I had too much on it and decided to restore to factory settings. It all worked fine. However, when I got to the Google Account sign in page, it gave me the "couldn't establish a reliable connection to the server" error message. I followed every single tutorial I could find online as to how to solve this. None of them worked. Eventually, I re-rooted it (using VRoot) and managed to download an apk of ES file explorer and locate the hosts file. This had one line that shouldn't have been there:
127.234.104.240 android.clients.google.com
From what I can make out, this is the address of google's sign in servers. So somehow (I suspect malware/dodgy rooting program?) my hosts file has been edited to stop me logging into google. Restoring the device does nothing, neither does unrooting/rerooting. When I open up the file in ES (when rooted) and edit out the bad lines, I can't save for some reason- I think the /system folder is write protected.
So I tried to make the /system folder writeable. I used the android sdk to do this (mount -o command) but this did not do anything. I downloaded the mount /system apk and installed that, it did not help either. I tried /pull and /push on the hosts file to edit it and send it back using the apk. I could successfully pull and edit it, but it would not let me push it back. I'm kind of stuck here. I can effectively not use my phone- I can't use most apps and can't download any, and have no other solutions up my sleeve. Any ideas?
Thanks a lot,
Louis
(PS I hope I've posted correctly, I'm a n00b to this website )
Click to expand...
Click to collapse
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Ish Takkar said:
Well, the same problem persists on my phone as well. Whenever I change the hosts file by removing the additional line, it saves but after some time it comes again and I have to remove it again and again!
Click to expand...
Click to collapse
I have this problem with my S3 and I always delete the "hosts" file! I should find witch process make this file!!
I am using a RCT6573W23, I have rooted it using Kingo and editing the ADK file... Everything went well, and I had installed SU and Busybox, Developement was on, but I don't think it remains on... I did some build.prop tweaks, and when messing with the LCD I messed up my system, disabling it from booting up.
I boot into Recovery just fine, and I DID BACKUP AND HAVE my original build.prop file, however, good ol' RCA doesn't provide any "files" for support at all, and connecting ADB is "SIDELOAD" only... I've read several places but everyone suggests going INTO recovery, which, I can do, or using ADB, but fail to realize it's sideload issue... I've pushed several files, but every single file is a bad footer, and wrong signature... I'm at a loss... Does ANYBODY have a recovery.zip from their Apollo 8" who could make a backup for me, so that I could sideload an official zip file. I would MUCH appreciate it... Thank you.
I have the same model... you're the only one I've heard of that has successfully rooted this one... is there a way I could get my official stock ROM copied without root?
Rooting it was simple, I believe you can go to settings backup and restore to get a .zip of your stock.. If you could shoot me a copy that'd be great. I can share how it was rooted, although it was super easy to look up.
There's not an option to backup entire system just app files.
What recovery did you use? and did you use the kingo universal rooting tool? And what edits did you have to do to the ADK?
I've successfully rooted but have no way, as of yet, to zip up my ROM. Any thoughts?
Anybody know if xposed framework or clockworkmod will work on this device?
-- Rooting your RCT6573W23 --
Install your USB drivers... If you don't have them, or you can't make your system acknowledge them, use the SDK-Method to fool your computer into reading the correct USB for your device... That method can be found at: addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Once you've got your drivers, before even plugging in your phone, make sure you have all of these options checked... From the developer's menues: "USB Debugging" "Allow Mock Locations", and in your security & screen lock settings: "Device Administrators", and "Unknown Sources" need to be checked...
Install Kingo from kingoapp.com
NOW, simply plug it in and click root on the pc... It'll install SuperUser and enable you to use just about any feature a rooted device can use, but without flashing roms... Still nice for cheatengine and stuff.
----------- Finished, Now... -------------------
Hmmm, once getting it going how would you go about making a backup that could fix my device? All I can do is adb update, and apparently no zip files have the proper signature. Is there no files that put Rom-to-Zip? I guess even if there were, I'd just need the permissions right to push over my build.prop which they wouldn't be most likely... And I can't nandroid...
I've acheived root and have SU, but Here's no way to make a nandrid without some sort of recovery...
Edgia said:
Hmmm, once getting it going how would you go about making a backup that could fix my device? All I can do is adb update, and apparently no zip files have the proper signature. Is there no files that put Rom-to-Zip? I guess even if there were, I'd just need the permissions right to push over my build.prop which they wouldn't be most likely... And I can't nandroid...
Click to expand...
Click to collapse
I believe these tablets have the RK3188T chipset, and I found These CWM Recovery images: http://androtab.info/clockworkmod/rockchip/
I don't have time to mess with it right now but I thought I'd share. I'm going to do some more reading on the subject before trying anything real crazy. Let me know if this works out for you...
Any luck on this? I was hoping to install a mod on this tablet myself
Hello.
I'm trying to copy a savegame from my phone (Mi9 Lite) so I can use it in Bluestacks for when I'm home.
I know it's location but it's in user/0/ as a com. and I only know because I can access it in Bluestacks.
I do not want to modify it so I just need read rights. Mixplorer doesn't do the trick.
Is there a way? How do apps even access the root folder when I can't.
Notes: Within the game main menu there is an option to upload and download save files to the Google Play cloud but unfortunately I cannot sign in in this game anymore. The reason is that I have modified it yesterday with 8x Speeder. If I remove the hack my offline save will be wiped again. Therefore I have to somehow access user/0/ and it's designated com. so I can back that up. Since i have no issues with Google Play itself I take it it has do with the Speedhack.
Before I modified the apk with 8x Speeder, I made legitimate purchases and those purchases were actually pulled from the Play Store but now I simply cannot sign in anymore inside of the game. Outside of the game I'm stilled logged on and have no issues. I have tried wiping the cache in both the game and the Playstore.
If you are going to ask why I used an app modifier in the first place, my first save was wiped when I had progressed for over 50 hours and I was mad as hell. Since the game is pretty much auto offline I enjoy it very much and would like to be able to backup my savegame so I can use it on Bluestacks.
Hello,
For what I understood your best hope would be to use ADB to pull these files. No need for root here I guess, only enabling developer mode and USB debugging.
Atronid said:
Hello,
For what I understood your best hope would be to use ADB to pull these files. No need for root here I guess, only enabling developer mode and USB debugging.
Click to expand...
Click to collapse
Thank you for your answer.
Unfortunately pull in adb gives me a permission error
banes768 said:
Thank you for your answer.
Unfortunately pull in adb gives me a permission error
Click to expand...
Click to collapse
That's what I feared. Try to see if you using the ADB (deprecated) backup utility helps. But I think the only valuable way would still be root, or at least a custom recovery to pull the file
Atronid said:
That's what I feared. Try to see if you using the ADB (deprecated) backup utility helps. But I think the only valuable way would still be root, or at least a custom recovery to pull the file
Click to expand...
Click to collapse
Ah, that's fine then I won't bother with that. Just a game afterall Thanks!