Related
Hi,
I tried finding a better place to post this, but there are no device forums for the bSquare MDP 8660 probably because its not that common and its a 'development phone'.
I'm using one of these devices in the lab I'm working in and I wanted to see if I could flash Google Apps on it since it comes without any of them (Market, Maps, Gmail, etc.).
Since it has an unlocked bootloader, can I just flash Google Apps (from Cyanogen's website) to it the same way you do it when installing the Cyanogen ROM? Are these files device independent? Or would this be an almost sure way of bricking the phone?
Device website: bsquare.com/snapdragon-mobile-development-platform.aspx
OS: Android 2.3.4
I would really appreciate any guidance/suggestions. Thanks!
gjain89 said:
Hi,
I tried finding a better place to post this, but there are no device forums for the bSquare MDP 8660 probably because its not that common and its a 'development phone'.
I'm using one of these devices in the lab I'm working in and I wanted to see if I could flash Google Apps on it since it comes without any of them (Market, Maps, Gmail, etc.).
Since it has an unlocked bootloader, can I just flash Google Apps (from Cyanogen's website) to it the same way you do it when installing the Cyanogen ROM? Are these files device independent? Or would this be an almost sure way of bricking the phone?
Device website: bsquare.com/snapdragon-mobile-development-platform.aspx
OS: Android 2.3.4
I would really appreciate any guidance/suggestions. Thanks!
Click to expand...
Click to collapse
Most probably yes.
Well here's my advice. Follow at your own risk. It might not probably brick it but there's always the slight risk of stuff going awry.
1) Make a Flash backup.
2) See if you have the system/app folder intact.
3) Flash the Google Market(yes, only the market.)
4) Install whatever the apps you want from the Market.
All Google apps except Market and Talk can be downloaded from the Market. You can of course flash the whole gapps update but downloading this way gives you some peace of mind and chances of avoiding any possible incompatible apps. (Like Voice Search which may not work properly on all ROMs. But, if it's AOSP, all Google apps would work and should work. )
Most of the Google apps would be device independent since most of them would use the Android API and not the native platform.
Flashing custom recovery - didn't work
Thanks for the guidelines.
I tried flashing ClockworkMod recovery so that I could make a backup of the phone, but every time I boot into recovery it shows a blank screen now. ADB doesn't recognize the device either. I tried Amon Ra's recovery and the phone is doing the same thing.
Before flashing any of the custom recoveries, the phone would just show the triangle when booting into recovery. It did show up on ADB though.
Would you have any suggestions on how I should continue? In case its of any use, I do have a package that I downloaded from the manufacturer's website that contains the original boot, recovery, and system images (along with some other files).
gjain89 said:
Thanks for the guidelines.
I tried flashing ClockworkMod recovery so that I could make a backup of the phone, but every time I boot into recovery it shows a blank screen now. ADB doesn't recognize the device either. I tried Amon Ra's recovery and the phone is doing the same thing.
Before flashing any of the custom recoveries, the phone would just show the triangle when booting into recovery. It did show up on ADB though.
Would you have any suggestions on how I should continue? In case its of any use, I do have a package that I downloaded from the manufacturer's website that contains the original boot, recovery, and system images (along with some other files).
Click to expand...
Click to collapse
As I told earlier, I'm not so familiar with the device.
If ADB is not working in recovery, it could either mean that the USB drivers(the drivers in the device, not PC) are corrupted or that the recovery is incompatible.
If CWM recovery you used is 100% compatible with your device(ie other people are using it without issues), it means that you must reflash all your files to factory and then flash a fresh copy of recovery. Simply, you must start it from scratch.
If you have no idea of the compatibility of CWM with your device,
1) Check and see if ADB/fastboot is working well with your device in other modes(boot, system). You can perform a simple file transfer and check the checksum of the original copy and copy on your device to ensure integrity.
2) If ADB/fastboot works well in all other modes but fails only in recovery, flash stock recovery(only recovery) and see if adb is working well. You can do the same thing as before. If adb/fastboot works well in stock recovery but fails in CWM recovery, it probably means CWM is not fully compatible with your device.
If CWM works well, go ahead and make a backup and proceed to flashing market. But, if like I said in 2), if CWM is not fully compatible with your device, proceed with caution.
As an an alternative, if you are going through all these ONLY to get the market, you can extract the market update and push the relevant files to the correct paths in the device using ADB in recovery or bootloader mode.
Installing only the Market app
Hi Nibras,
Sorry for not replying back to you. My college classes got started and I couldn't spend much time on this project.
I liked the idea of just extracting the Market app and installing that (since that is all I really need).
Do you think I could just use the procedure outlined below, even though I won't be doing it on Honeycomb:
Installing Android Market over your freshly installed HoneyComb will require a different approach than just installing an APK.
Make sure you have ADB up and running, and your device recognized. Refer to our guides on what is ADB and how to install it, and how to enable ADB USB drivers for NVIDIA Tegra and Tegra 2 based devices.
Download this version of the Market (2.2.11).
Download GoogleServicesFramework.apk.
Place the files in any folder on your computer and open a Command Prompt window, browsing to that folder.
Enter these commands in the Command Prompt window:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb push Vending.apk system/app/Vending.apk
adb push GoogleServicesFramework.apk system/app/GoogleServicesFramework.apk
adb shell
cd system/app
chmod 6755 Vending.apk
chmod 6755 GoogleServicesFramework.apk
exit
adb reboot
Now go to apps, open the market and sign in. If the Market won’t open at first, reboot and try again and it should work.
Click to expand...
Click to collapse
gjain89 said:
Hi Nibras,
Sorry for not replying back to you. My college classes got started and I couldn't spend much time on this project.
I liked the idea of just extracting the Market app and installing that (since that is all I really need).
Do you think I could just use the procedure outlined below, even though I won't be doing it on Honeycomb:
Click to expand...
Click to collapse
That should work I guess. But, flashing via recovery is just a one step process. =)
Update.zip also does just the above process, I guess. It just saves us a couple of steps. Also, if you make a recovery backup, if anything goes wrong(say boot loop or force close of system at boot), you can revert very easily since recovery is independent of all the other data on phone.
And, I guess you might have to push Talk.apk too. I'm not sure about it though. Some people complained that removing Talk.apk broke the Market authentication.
If you want to push Talk.apk, get the apk file and,
Type adb push Talk.apk system/app/Talk.apk after adb push GoogleServicesFramework.apk system/app/GoogleServicesFramework.apk
Also, type, chmod 6755 Talk.apk after chmod 6755 GoogleServicesFramework.apk.
Btw, you can also ignore Android Market altogether and use Amazon App Store as well as GetJar.com. They both offer install-able Market apps. Of course, they don't have a collection as large as Android Market.
@gjain89:
Did you ever try pushing the Market files to the MDP? If so, then did it work? I have one of these and I'm in a similar position.
Thanks
I have one of these...
I used adb to push the files. However the system partition barely has any room for more apps. so apps larger than 2MB won't install, unless you obtain the APK from a secondary source.
Refer to this thread for more information: http://forum.xda-developers.com/showthread.php?t=1400737
And this one: https://developer.qualcomm.com/forum/qdevnet-forums/general-discussion/6864
Plus, many apps force close.
Enjoy!
PS: Let's try to stick together, we might be able to fix some of these problems. Maybe someone could build a custom rom.
To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...
I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium
Is there perhaps any way to perform a ROM backup with ADB?
DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
bluenote73 said:
Hey guys
I screwed up my vold.fstab trying to get "_ExternalSD" back.
Unfortunately! I did not run a nandroid before I made the change.
Now, I can dirty flash my rom on top, or go back to a nandroid from a few days ago, but I'd really just like to recover and go on my merry way. And maybe learn something in the process.
Only thing is, I can't figure out how to access the phone other than the External SD card through CWM.
Can I mount the internal /system and access through USB? Is there some facility to copy a file from one point to another? Any other methods? I guess the phone has to be up to run ADB, right?
I don't know how to generate a flashable zip but I could extract the original version of the file from the original rom. I assume that its non trivial to create a flashable zip, but maybe someone can comment? It looks like there is signing and certificates involved..
thanks for any ideas
Click to expand...
Click to collapse
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM. (you can try dirty flashing but i dont think itll work)
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
EDIT: re read your post, if your feeling adventurous and want to give it a shot, boot into CWM and connect it via usb. you can now get into an ADB shell on your phone by typing 'adb shell' if you have adb all setup and working. (im working from memory here so dont quote me on any of this)
now, you should be able to access your /system folder from that shell. be very careful though, i dont have much experience right here, and if i remember correctly you might not be in the full root directory yet)
if you can get into it try replacing your vold.fstab with a stock one,
if you dont have a stock one lying around, make a nandroid of the current state of the rom, then flash another rom, pull the vold.fstab, then re-restore back to the broken one and restore it (id upload mine but my phone is OOC right now )
after that just reboot and hope it resolves itself, if not then just follow my advice above
and keep that guide i linked to handy, messing around in CWM has the ability to brick your phone, if it does, then just follow that guide.
Klathmon said:
this is why i hate it when people make those guides.
messing with the vold.fstab is dangerous (even though its only a few lines) if your trying to recover your data, give up. its not going to happen. (sorry)
when you edit the vold.fstab it messed up the partitions on your internal SD card and most likely did the equivalent of wiped your /system partition. (or another important one.) your actually lucky it did not completely brick your phone.
your post was a little vague, but if you can, just restore an older nandroid, or wipe everything and install another ROM.
if you cannot access CWM, then follow the steps in This guide. it should get you back up on your feet. after you follow that guide flash a gingerbread ROM (any gingerbread rom will do fine) then you can reboot and flash any ROM you want. (it needs this to fix a quirk in that script)
Hope you get it fixed
Click to expand...
Click to collapse
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
N00BY0815 said:
How bout adb and pushing the file back in? Or cant you access the phone via adb?
Sent from my LG-P970 using XDA
Click to expand...
Click to collapse
re read your post and updated my last post right after you posted
after dealing with noobies all day, i forget sometimes people want to try big things
Thanks guys. The info I was missing was there's no special trick to attaching adb while in CWM! Just plug in!
My phone is back up and running and partitions are fine as far as I can see after just booting up.
Hi there! I messed up with the vold.fstab filfe on my tablet – I replaced it with a downloaded file with the intention to transfer apps to my external SD card.
Now my tablet is only showing the startup logo and won’t continue loading. I can access recovery mode. Now I want to restore the original vold.fstab file.
My questions:
1. Using the Android SDK, the file explorer does not show any files, though my tablet is recognized.
2. Using adb push, it yields an error: permission denied, how to successfully push the original vold.fstab and replace the existing vold.fstab?
3. If I dump an image of my tablet and edit the dumped image, would this be easier compared to the steps above?
Thanks!
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
BryanF said:
Thanks, I will try it later when I got home. My tablet is not found here. I have a Skyworth S71(3G) with RK3066 chipset.
Click to expand...
Click to collapse
You need to do an adb remount before you can push. Was it rooted before?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Mansa_noob, yes, my tablet is rooted. I followed some instructions about adb but had an error saying access denied, and also no files are displayed at file explorer. See my posts above. I also mounted it successfully. I will post some sreenshots later.
Please if you have some instructions, I am willing to try.
---------- Post added at 07:06 AM ---------- Previous post was at 07:02 AM ----------
TwitchyEye said:
http://forum.xda-developers.com/showthread.php?t=1646108
Try this.
If this doesn't help you should ask in the section for your tablet to get more specific advice.
Click to expand...
Click to collapse
Hi twitchyEye, it did not work. It attemps to install (using the install update from ext sd card) but then says installation aborted.
Any more suggestions? Thanks
What recovery are you using? I suck with adb so I got nothing on that front.
It was the stock recovery from my Tablet. I don't have it on hand right now, I will post later. The chipset is RK3066. My problem is my tablet has no official support on the internet (maybe becaue it's still new). Model is Skyworth S71(3G).
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
TwitchyEye said:
I see. Yeah this is over my head man. I thought for sure you were running a custom recovery and it was an easy answer. I'm actually struggling right now with adb myself with a similar issue something about permissions whenever I try to do anything to my phone. So I guess right now would be a perfect time for somebody to chime in with a smarter answer!
Click to expand...
Click to collapse
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
Are you doing adb remount and still getting permission denied?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
Yes, I did adb remount and still access denied
BryanF said:
Yes, I did adb remount and still access denied
Click to expand...
Click to collapse
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
This is strange. A properly rooted phone would adb remount to r/w system. Something is fishy. Is it rooted+
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
BryanF said:
I am sure it is rooted, because I downloaded an application from Google play to check it it is rooted or not. It is really rooted. I alvo confirmed this as I can now fully backup and restore my apps using Titanium backup before the tablet is messed up.
Click to expand...
Click to collapse
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
mansa_noob said:
OK. Odd or not, it is what it is. Is it possible for you to load a custom recovery?
-- The noob says:
This just in... my IQ has increased 50 points thanks to the g2x!
Click to expand...
Click to collapse
I want to try, but the stock recovery is my last hold as I have no stock ROM. If I overwrite the stock ROM, I cannot reinstall it as I don't have a copy of it.
So why not flash cwm with nvflash and then make a backup of your current stock rom? I did exactly that.
Sent from my LG-P999 using xda premium
READ ME FIRST!! USE AT YOUR OWN RISK!! I and/or XDA are not responsible if this bricks your phone!!! If this transforms your phone into a decepticon and shoots your eye out...
OK....what a few months its been...sorry guys been out of commission...car wreck...
Had to start over...so here we go..
First...You must be rooted...if not google it..
install your favorite root file explorer
install your favorite term emulator
ok got that...now the good stuff..
download http://dl.dropbox.com/u/56403887/L45C_CWM_Recovery-v6.0.1.2.zip
or http://dl.dropbox.com/u/56403887/L45C_CWM_Recovery-v5.0.28.zip
this is the cwm recovery 6.0.1.2 compiled from source by me...it is only for the L45C...Cant stress that enough...had to make changes to graphics from source to get it to work...
also the v5.0.28 recovery because as of now v6.0.1.2 has no sdcard partioning support because it is new.
you can choose which you like best...
put on root of your sdcard ...
make sure the file name is recovery.img
now download http://dl.dropbox.com/u/56403887/flash_image.zip
this is the flash_image file to to flash the recovery..
unzip it should have the name flash_image
use root explorer to copy the file to /system/bin
open term emulator get su rights and cd to /system/bin and type chmod 0755 flash_image
now cd back to /
still with su rights type flash_image recovery /sdcard/recovery.img
if no output... wahoo.... if you get error start over
dont reboot yet...
go to playstore and download a app called Quick Boot its free and handy you want have to hold buttons to reboot into recovery..
ok...now the moment of truth run quick boot and choose recovery...you should get a su ask from superuser grant it....phone should reboot into cwm recovery...if it did... wahoo... you now have cwm
keymap is fixed and is like this.... search button to select.....return button to return..home button to scroll..
way better than before,,,to me any way...
still will get error about bad boot message but i will fix later it don't affect anything..
Here is the stock rom , rooted , busybox , http://dl.dropbox.com/u/56403887/Stock_L45C_Rom.zip
Here is the stock recovery also http://dl.dropbox.com/u/56403887/L45C_Stock_Recovery.zip
i am at present working on kernel...for cm7...
Give thanks to Koushik for CWM...And to TWO.BIT.CODER for all the help...Thank You...
Reserved
Hey ICE.....Is it suitable for Optimus Net P690 in India.....?????
Does this support custom themes?
p690f can't get qtadb to link phone/PC
Hi
I am stumped, as a complete novice to smart phone/linux.
At present my status is:
1. Phone is rooted, so I was able to get this done from my PC.
2. Now I have copied the recovery.img & flash.img to SD card.
3. I have Terminal emulator on phone &/or Sd card.
4. When in USB storage is activated & connected to PC, I can see all the files but on terminal emulator.
5. I have Qtabd on my PC but it will not 'see' my phone either in USB storage activated or not activated or in debug mode.
6. When debug mode activated, USB storage is deactivated. Seems both not able to be on.
7. In one of the XDA threads there was mention of 'demounting' the sd card so have also tried that in same combinations of SD/ debug.
I have been trying to sort this out on another forum but seems there is more info available on here.
I am having a huge problem tying to get Recovery working direct on the phone, mainly due to my inexperience on these devices, I am very happy to learn if pointed in right direction. Of course my concern also is not to brick the phone!!
Any assistance or links to suitable areas appreciated.
Whoops seems I posted on wrong thread, thought it was the similar one for P690, applogies.
WaHooo
I managed to finally get recovery activated using the terminal emulator on the SMALL screen of my phone!!
However I would still very much appreciate sorting out Qtadb connection as I am sure sometime in the future I will need to do some additions/deletions to my p690.
So, any info etc will be appreciated.
For any other Newbies who may see this,
1. To copy from a browser text long touch at start/end of text, then drag to high light.
2. To copy, touch highlighted area, you should get a message 'copied to clipboard'. To cancel, if you make a mistake like I made MANY touch some where else on screen.
3. With Terminal emulator started, (P690), after entering 'su' tap touch screen to bring up keyboard and select 'return/enter key'. This gives you Super User.
Long touch screen brings up menu withe 'paste',select.
4. To toggle back to browser, to same screen you were working on, hold down second key on bottom. This will bring up all the recent icons for what you were working on, select 'browser'. Continue copy line by line.
5. To toggle back to emulator, long press 2nd from left key & select emulator.
Hope this assists someone.
The p690 and this phone are not the same. This phone is from Net 10, idk about the p690, but this phone is. This one is also cdma. I think the p690 is gsm. They are NOT cross compatible. I'd brick my phone if I used a p690 rom.
sorry guys been working on code....
oldfella2... spark is right... this is for l45c on net10 or tracphone...only...the p690 is diff...there is a thread here on that phone...spark you can coustom theme. I haven't yet but I don't see why not...
I have been able to unlock bootloader and to fix cwm recovery for this phone..will post it here later this week...also been testing cm7....but I can't seem to find wifi bug... it drops and reconnects const...
lce67 said:
sorry guys been working on code....
oldfella2... spark is right... this is for l45c on net10 or tracphone...only...the p690 is diff...there is a thread here on that phone...spark you can coustom theme. I haven't yet but I don't see why not...
I have been able to unlock bootloader and to fix cwm recovery for this phone..will post it here later this week...also been testing cm7....but I can't seem to find wifi bug... it drops and reconnects const...
Click to expand...
Click to collapse
dude! if you can get cyanogen working i will be forever in your debt
Update please
Hi there. Been crack flashing my phone for a while and finally got my wife's phone rooted today.
Just wondering if anyone has had any luck flashing a custom recovery yet (eg CWM or Amon Ra)? If so, please post a guide. As I have been unable to find anything using my Google-fu.
Also, all your links were removed. So other than hinting at a solution. This thread is zero help.
Thanks in Advance!
My Phone: HTC Evo 4G (flashed to Cricket)
Wife's Phone: LG Optimus (LGL45C)
I have a question regarding etc..... Does your rom include a tun.ko file and if not do you know of anyone or anyway to run openvpn/droidvpn or just changeing kernels would be nice...
I can't root.
I have an L45C with 2.3.4 on it and it just won't root. I have tried: Gingerbreak, z4root, and unlock root, none of them worked. I tried gingerbreak a few times at day, and all night as I slept, but my phone just isn't rooting!
If any of you have gotten root please do tell me how.
no updates yet?
Can someone please post a link to this ROM? I had it but can't find ir and I need it bad, phone is semi-bricked and I have a corrupt backup. PLEASE!!
Regards,
rast4man
request fulfilled
Request fulfilled
lce67 said:
READ ME FIRST!! USE AT YOUR OWN RISK!! I and/or XDA are not responsible if this bricks your phone!!! If this transforms your phone into a decepticon and shoots your eye out...
OK....what a few months its been...sorry guys been out of commission...car wreck...
Had to start over...so here we go..
First...You must be rooted...if not google it..
install your favorite root file explorer
install your favorite term emulator
ok got that...now the good stuff..
download http://dl.dropbox.com/u/56403887/L45C_CWM_Recovery-v6.0.1.2.zip
or http://dl.dropbox.com/u/56403887/L45C_CWM_Recovery-v5.0.28.zip
this is the cwm recovery 6.0.1.2 compiled from source by me...it is only for the L45C...Cant stress that enough...had to make changes to graphics from source to get it to work...
also the v5.0.28 recovery because as of now v6.0.1.2 has no sdcard partioning support because it is new.
you can choose which you like best...
put on root of your sdcard ...
make sure the file name is recovery.img
now download http://dl.dropbox.com/u/56403887/flash_image.zip
this is the flash_image file to to flash the recovery..
unzip it should have the name flash_image
use root explorer to copy the file to /system/bin
open term emulator get su rights and cd to /system/bin and type chmod 0755 flash_image
now cd back to /
still with su rights type flash_image recovery /sdcard/recovery.img
if no output... wahoo.... if you get error start over
dont reboot yet...
go to playstore and download a app called Quick Boot its free and handy you want have to hold buttons to reboot into recovery..
ok...now the moment of truth run quick boot and choose recovery...you should get a su ask from superuser grant it....phone should reboot into cwm recovery...if it did... wahoo... you now have cwm
keymap is fixed and is like this.... search button to select.....return button to return..home button to scroll..
way better than before,,,to me any way...
still will get error about bad boot message but i will fix later it don't affect anything..
Here is the stock rom , rooted , busybox , http://dl.dropbox.com/u/56403887/Stock_L45C_Rom.zip
Here is the stock recovery also http://dl.dropbox.com/u/56403887/L45C_Stock_Recovery.zip
i am at present working on kernel...for cm7...
Give thanks to Koushik for CWM...And to TWO.BIT.CODER for all the help...Thank You...
Click to expand...
Click to collapse
DUDE! Thanks a TON! Now I can get my phone working again! Sorry to hear about your wreck and I wish you a speedy recovery! Thanks again!
Regards,
rast4man
ROM/Recovery LGL45C
What are the results of flashing this recovery? Was it successful to flash as I have a backup for the phone that I have made thankfully.
results are great. For what little ROM development, this is the best we have. Its just a ClockworkMod recovery image and then a rooted ROM. I'm still using it to this day and with all the apps and tweaks I've added, this phone rocks!!
My only complaint is I'm running out of internal space so I need to figure something out with that. Maybe I will try to re-partition my card to ext4 and try to increase internal memory by like 100mb. Apps2SD only goes so far sadly. I'm also going to try to put Team Win recovery on after I make sufficient backups. Let me know if I can help.
Regards,
rast4man
rast4man said:
results are great. For what little ROM development, this is the best we have. Its just a ClockworkMod recovery image and then a rooted ROM. I'm still using it to this day and with all the apps and tweaks I've added, this phone rocks!!
My only complaint is I'm running out of internal space so I need to figure something out with that. Maybe I will try to re-partition my card to ext4 and try to increase internal memory by like 100mb. Apps2SD only goes so far sadly. I'm also going to try to put Team Win recovery on after I make sufficient backups. Let me know if I can help.
Regards,
rast4man
Click to expand...
Click to collapse
I was able to install the CWM Recovery to the phone just fine. Realized what I was doing incorrectly. Now to test the only ROM's that I know of that are available for the Q from Area51. Are there anymore ROM's being developed. The L45C is not a bad phone, just needs more lightweight ROM's to work with it.
Hello,
I thought of myself as a pretty experienced user, but you never learn enough!
However, I flashed some roms (lollipop) that, probably due to my mistakes, screwed up my file system, to the point that my recovery (latest PhilZ) wasn't able to find its backup anymore. Eventually I solved the problem as I was able to find my backups and use them to revert my phone to the rom I wanted to run (Carbon 4.4.4). But I was really annoyed by the fact that my file system was a bit off and still I was having problems with the recovery. So I decided to begin investigating the possibility to restore my phone to factory default. Before going with it, I tried the soft approach, i.e. I used the soft factory reset available from the settings menu. It all seemed fine and I re-flashed a lollipop rom that suited me.
Now the problem is that, after all the ordeal, I decided to make a new backup and so I did. It appears all fine, my recovery can actually "see" it, but I cannot identify it using a root browser! It seems to have disappeared unless I open the recovery and then I see it there. It is located in a folder that I can, of course, access, but,when I do so, I can't find the file!
I tried to put on my phone an old backup (always a PhilZ one), but when I try to put it on the phone I can't find the Backup folder in the Clockworkmod folder!
Anyone has any idea of what is going on and can give me a suggestion on how to overcome the problem?
Thanks
Luca
PS An alternative would be suggesting how to do a restore from a sideload: I thought I saw a similar option, but I can't seem to find it anymore within the recovery's options! I tried also restoring via NRT, but although all seem to go fine and the software return no failure notice, I can't find the backup file that should have been pushed (successfully) on my device!
Its not a recovery issue. Its an L issue.
Best thing to do would be to wipe data and storage then fastboot flash userdata.IMG
http://forum.xda-developers.com/showthread.php?t=2938749
rootSU said:
Its not a recovery issue. Its an L issue.
Best thing to do would be to wipe data and storage then fastboot flash userdata.IMG
http://forum.xda-developers.com/showthread.php?t=2938749
Click to expand...
Click to collapse
Thanks a lot for your help.
How can I find the img. file to flash?
Would it be ok to just go ahead and start from 0 using this:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
How can fastboot flash an image file? I've never done that before! As I said, been doing this for a while, but never done this before...I think!
Luca
Alas, after reading your post on one-click toolkits, I'm afraid I'm one of those who thinks they can do things, but rely on simple tools to do them. However, I never (almost never) forgot to make a nandroid backup before flashing a new rom and, to be honest, I'm not a flashoolic. I never, ever bricked my phone (got a few bootloops). If I find a rom that suits my need, I stick with it for as long as I can.
The changes between KK and L are such that are beyond my comprehension, but I try hard to solve the problems I have without bugging everyone at the first obstacle. But now, after fidgeting with my phone for 2 days, I had to give up. With a few words, you singled out the reason why I couldn't come on top of this: things change and I was not informed of how much they did!
Luca
Problem partially solved..I think! Now I can see the folder and found my backup!!
I used the restorecon command you suggested. I couldn't make it work using terminal emulator (just did not accept the su command: why I don't really know). Then I thought about using adb shell via pc and, I really surprised myself; I was able to pull it through. I'm not totally brain damaged as I felt when I couldn't even reproduce the command you indicated. It is probably the application that doesn't work. It was my first time with adb shell, so a new thing learned.
However, now I would like to ask you: if I place in the proper folder the backup folder I saved on my pc, will I be able to restore the nandroid backup? I just need some data that I forgot (trivial things, such as text messages and a few app data, like passwords and stuff) but it would be useful.
Thanks once more for your help.
Luca