Related
Hi all,
Sorry if this has been posted before, I have had a look but cant find the solution!
I have a HTC Desire HD that I have rooted using the AAHK, this has worked fine.
Next, I have searched around for a rom to use and found the Cibernodo Mod2Bravo V7.1 (English version) . . . I have put the zip file on to my SD card . . . restarted in recovery mode, wipe data/factory reset, wipe cache partition, wipe Dalvik cache, wipe battery stats, install zip from SD card, chosen the Cibernodo file and gone through the installation process . . . .
I have done all of this several times, and downloaded the zip again but I constantly get the same results:
Mounting and formatted partitions
Mounting /data
Mounting /sd-ext
Formatting /system
Mounting /system
Intalling System & Data partitions
Installing Gingerbread Keyboard
Installing Zeam Launcher
Installing ES File Manager
Installing CM/GB player
Installing 3DGallery
Removing Apps NOT selected
Installing Cibernodo Bootanimation
Configuring installed files
Setting permissions of /data
Configuring System Files
assert failed: write_raw_image("/tmp/boot.img","boot")
Yes, I am a noob, and no, I dont know much about this but I have followed everything to the letter as far as I can see ... is there something glaringly obvious that I am doing wrong?
To top it off, each time I complete this process a message pops up telling me:
Congratulations...
Cibernodo Mod2Bravo has been installed correctly on your phone
Click Finish, and restart your phone.
Thanks
Installation State: 1792
So is the 'assert failed' the issue here, and if so, how do I fix it?
Sorry to go into so much detail but I just want to see where I have gone wrong ... many thanks in advance!
[EDIT]
when my phone reboots it goes back to where I started from, i.e. the downgraded version of android from after rooting . . .
I will also try downloading and installing a previous version, V6.1z ...
Same issue with that version, so Im pulling hair out lol!
This has now gone from bad to worse ... I ran the aahk again as super user and busy box disappeared, thinking I would start from fresh again . . . there was a pause in the process and now my phone is stuck on the white HTC screen . . . anyone able to shed any light on this at all?
I've managed to speak to someone and apparenly I am not bricked and can run a ruu ... when I re-run the aahk it wont start as the error message comes up ... the phone is plugged in, the drivers are installed but I am guessing the USB debugging has been disabled . . . so does anyone know how to enable this from the aahk main screen with regards to the fact I can't boot into android?
Looks like there are lots of reasons for this... and it's a can of worms. Also, the Desire HD is one handset that my network has never sold direct, so I have seen one in eighteen months. I'm less familiar with it than I'd like... Just checking the thread and you're using the Desire HD, yes?
This thread degenerated a little and I think you've tried the chatroom too, but there are some useful pointers here: http://forum.xda-developers.com/showthread.php?t=1646178
And also here:
http://forum.xda-developers.com/showthread.php?t=1645285
Good luck. Keep us posted.
Thank you for that, I have got to the point where I don't know what to look for anymore lol! I will have a read through those ...
Hi
I am trying to install the Jellybean 4.1.1 ROM on my rooted Nexus S.
The history of my attempts so far are here: Rooted Nexus S OTA Upgrade to 4.1 http://forum.xda-developers.com/showthread.php?t=1833420
I have downloaded the "image-soju-jro03e.zip" form the Android open source website, and used the Nexus Root Toolkit to install it.
This failed, and I attempted to install the image using ROM Manager.
This also failed, and produced a lengthy Recovery Log.
I have read through it and it seems to be telling me that certain files or folders are missing from the download.
e.g can't open /dev/tty0: No such file or directory
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
can't find /sd-ext in /etc/fstab
Is that what this means?
How can I correct it?
The full log is here: https://docs.google.com/document/d/1HWeYsXPnppQbgoloz72RH81E8a479LBmvYXIlzYPETo/edit
S
Help with recovery log
Hello?
Can anyone help me to understand this recovery log?
Should I direct my question to the "ROM Manager" people?
I have tried without success to install JB 4.1.1 from the Google Android Images page, and I think it must because something is missing from the file structure of my current ROM.
Am I on the right track?
M S
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
new hope
nightsky87 said:
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
Click to expand...
Click to collapse
Hello nightsky ( is that like, "nice guy",?) thanks for taking a look.
My phone is a Nexus S i9020, no suffix.
It is running Andriod 4.0.4 ICS. It is "rooted" and "unlocked".
I have Clockwork Mod v.6.0.1.0. Superuser v.3.1.3. and ROM Manager v.5.0.2.0.
I have tried over and over again without success to upgrade to JB 4.1.1 and I am getting sick and tired of this stupid game.
I would be happy to just stick with ICS 4.0.4, but every week, the phone tells me that an "update is available", and I have to dismiss the message every time I look at the phone! When I tried to apply the update It used to crash, requiring a battery-pull reset. Now I have CWM it takes over and says "failed to verify file signature", "install untrusted package?"
If I press on and install, it fails and the android is on its back with a red triangle on its belly.
If you look at the posts I have linked to, I have been on a steep learning curve regarding ROM flashing, and I understand the basic idea, its just that when I follow the instructions given on the forum, It doesn't happen that way for me and I suspect that there is something wrong with the file structure on my phone. That is why I have posted the link to my recovery log.
If you can help, please reply.
I have had a look at the "Random Phantasmogoria" site that you recommend, is it offering anything different than the Google developers site https://developers.google.com/android/nexus/images that I have downlooaded my image from?
MS
another version!
PS I have just had a look at the Google Dev. site and there appears to be a new version of 4.1.1 called JRO03L.
My next attempt, I'll try that.
MS
goodnight
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
jus to add on the post above. the instruction to install the factory images are on the same page where you downloaded the image in question.
and there is something to be wary of : flashing the factory image will WIPE the phone CLEAN (except what's on the usb storage o/c).
albundy2010 said:
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
Click to expand...
Click to collapse
Smashing buttons and hoping something works?
That's not very nice, or fair!
If you take the trouble to read my post, and the linked previous posts, you will see that I am trying my best to follow the instructions given on this forum, where I hoped to find knowledgeable professionals who contribute their valuable time free of charge to help noobs like me.
So far I have followed the instructions, only to get something other than the result described. This is why I am asking for your help to understand the recovery log, so that I can work out for myself what went wrong, and what I should change next time to get it right.
At this point in the journey I am still unsure about backup. I have "backed up" using the nexus root tool kit, which is a Nandroid back up, and I have "backed up" using ROM manager, but Titanium Back-Up does not recognise the backups and wants me to "back up" some more. After all this is over will I be able to clear out all the dross that my phone memory is accruing? Is there any point backing up Apps like "Google Earth" when I can easily download them from the Play Store after I have my new OS? etc... etc...
Anyway, I am going to try again, this time with the new JRO03L image, and this time I shall do it Command Line style instead of the "one click crap", as you recommend, my friend. I'll let you know how I get on.
MS
To whom ever can help out, I have a Galaxy Tab 2 7.0, and cannot seem to get my problem resolved by myself. I have somehow inadvertently managed to install an update.zip that had or had no relations to this particular OS of this particular model of android.
My problem is that I wanted to be able to, migrate my apps to the external SdCard or extSdCard, and I think I used an update.zip designed for the cellphone HTC Evo 4g. Not realizing that I will be later unable to use the restore feature from a previous backup I had made using CWM 6.0.1.0 to recover from my inadvertent mistake (not to comfortable making a backup, and thinking I can restore properly anymore, like I can on my cellphone that I am spoiled with).
Silly of me to think I could use an update.zip designed for another type of device such as the HTC Evo 4g, but… (anyway my bad what was I thinking…?). The update.zip, by the way is "dtapps2sd-2.7.5.2-signed", like I mentioned this is clearly designed for the HTC Evo 4g, and not for the Samsung GT2 7.0.
The problem I experience now is not complete lose of my GT2 7.0 device I can still install and change out OS through the CWM-Recovery and install apps through the Android Market. I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Now my question is, how is-it possible to resolve this issue. I have tried to complete a fresh install of the OS, CWM-Recovery, and also attempted to wipe everything possible that the recovery will allow, but I am not expecting much, as I cannot even get the backup and restore feature to work efficiently enough to provide me with what I need it to do…
I have provided this post with a download of the update.zip I used as well as the version of the OS I have provided my Samsung GT2 7.0. If anyone can shine some insight on what direction I should attempt to do to resolve this issue I would be more that interested to take a look at what I could use to correct this error of mine…
-Samsung GT2 7.0 - OS (Use the Download link above the Rosewell signature)
http://forum.xda-developers.com/showthread.php?t=1784318
-dtapps2sd-2.7.5.2-signed
http://www.mediafire.com/?7jpc5oudzt6o76p
I might be comfortable to ADB Shell into my device to make changes, or if one was able provide me an update.zip/script that would be great. Also is there a better recovery out there than the ClockWorkRecovery.
Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Sent from my GT-I9300 using xda app-developers app
Mohamedselim said:
Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Click to expand...
Click to collapse
Mohamedselim, Thanks...
Will look into this..., any links by the way in regards to the "fresh firmware with a pit file"...?
Have you tried downloading and flashing a full Odin tar file to restore your device to stock?
imnuts said:
Have you tried downloading and flashing a full Odin tar file to restore your device to stock?
Click to expand...
Click to collapse
Yeap...!, I have tried this already, have had no promising results...
This is the only compatible version of a .pit file...;
http://forum.xda-developers.com/showthread.php?t=1642744
Can anyone provide me another one for the GT-p3113...?
Just checking in..., and wondering if anyone has a solution for this...?
Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.
WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.
RomsWell said:
Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.
Click to expand...
Click to collapse
MultipleMonomials said:
WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.
Click to expand...
Click to collapse
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...
Ok, so I was successful in taking RomsWell and MultipleMonomials advice, and was able to return my device back to "Normal" state, including "Stock Recovery". But I still have the original problem as in my request I asked in my first post...
I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Click to expand...
Click to collapse
I think now, if I cannot get a sizable remedy..., is just to try and send it in Samsung so they can take a look at it...
Any suggestions...?
FYI; I have also tried connecting to Kies, but due to the inability to posses a "MTP" (Media Transfer Protocol), is the reason I cannot connect to my SdCard & extSdCard. I can "PTP" (Picture Transfer Protocol) into it, using "adb shell", but not using "MTP"...
So I do not know how much "MTP" has to do with this relationship of the other three items that I mentioned in my bullet list in my quote, but...
Anyway, I don't know what I am trying to say, but thank you two, for getting me this far...!
grassy-sneakers said:
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...
Click to expand...
Click to collapse
Did you try formatting internal storage in CWM?
MultipleMonomials said:
Did you try formatting internal storage in CWM?
Click to expand...
Click to collapse
I am not quite confident on how much this will work. As I have tried this multiple times to wipe "Wipe Factory/Data", "Wipe Cache", including all the partitions under the "Advance" section found in CWM Recovery. Even using TWRP Recovery.
Per this post; I just attempted to flash a "Stock Rom", but not before doing a factory/data, cache wipe using "Stock Recovery", including after a successful install...
No luck, the same problem still exist as above...
Ok, this was all just the rudest experience I put my self threw. As I have an HTC Evo 4g - cellphone and have become comfortable with installing ROM's, Kernels, and Updates.zips, as well as, other modification. All threw the Recovery designed for this particular device, and don't get me wrong there has been a couple of times. Maybe more than a couple, more like a few times I have installed incompatible downloads I find in the XDA forums. Which makes this screw up, difficult form me to know that as long as you can get into a Download/Bootloader or a modified Recovery designed for a particular device that was successful flashed correctly. Well the screw up are easily redeemed/recoverable.
So, to make a long story short. After having called Samsung Customer Care (the 1-800-SAMSUNG) number, it seems to have been a External SdCard getting in my way from having been real short from sending my Tab off to the repair department (where ever it is...). I in fact already had it in an envelope, all I needed was an address to send it to. Anyway the nice person on the other side of the phone requested that I remove my External SdCard, and confirm that I was able to get into my "Storage" tab under my settings. Well after success getting this option back, I then made the suggestion that maybe my Eternal SdCard is corrupt or incorrectly formatted. She then agreed maybe this is the case. After ending the phone call. I quickly restarted my Tab, again only to find out that I was no longer receiving the error messages like mentioned above, which is great, because after multiple flashes of "Stock Roms w/Stock Recovery", and forcing myself to believe that it was a system install error. It in fact the External SdCard in place preventing me from throwing my Tab against the wall / in the mail to Samsung Repair Center...
"Man what an ordeal...!!!"
Thanks to all that helped with the suggestions, as to what direction I most defiantly tried.
I am now in the process, since I am living back in Stock mode. To receive an OTA (Over The Air) Update, and am still in the process of seeing if this thing still possess any residual silent errors...
I will keep you posted.
If not, well it off to happy rooting for me...!!!
That is it, my problem is resolved. Damnedest thing this problem of mine, it seems the only thing I screwed up was the micro SdCard. to the point it was the cause of all the error I received when I started up the device, as well as when I attempted to access my storage through me settings options...!!!
Now re-rooted, and a happy camper, Cheers...!
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]LG Optimus One Device Family[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: How do I root my LG Optimus One?[/SIZE]Rooting can be accomplished with Gingerbreak.apk 1.20 for most devices running stock Froyo ( 2.2 ) and Gingerbread( 2.3 ). There is also Z4Root and SuperOneClick for those instances when GingerBreak doesn't work.
[SIZE=+1]Q2: How do I install a custom recovery?[/SIZE]This is too broad a topic to cover in detail in this FAQ. Please refer to any of the methods listed below...
Install recovery with 'flash_image' binary or LGMDP
All in one how-to for rooting, installing ADB, installing recoveries, etc...
Install ROM Manager from Play Store. To use ROM Manager you MUST be rooted. Use ROM Manager to install a custom recovery.
Most P500 and P505 models got their official updates. Choose the Optimus One item
The P506 and P509 did not get official updates. Choose the Optimus One (OldBB) item
Device models not mentioned, old baseband models choose the "Optimus One (OldBB)" item. New baseband models choose the "Optimus One" item.
There is also my utility Android Flash Recovery to flash a recovery via fastboot and fastboot mode.
[SIZE=+1]Q3: Why do I have to "trim" my ROMs?[/SIZE]
The allocated system partition on any of these devices is only 190 MB. Not really huge. However since Android 4.0, the space required for everything has increased to a point that it will almost completely fill the system partition only leaving a few KB free. OOne ROM Editor is a Windows utility designed specifically for this task.
[SIZE=+1]Q4: I've flashed ( any ICS or JB ) ROM and Google Apps. Why doesn't my Home and or Search button work?[/SIZE]Did you trim the ROM prior to installation? If not, see question #3 above.
Did you wipe your /cache and Dalvik cache prior to the ROM installation?
[SIZE=+1]Q5: Why doesn't Link2SD work with CM10+?[/SIZE]
There are several reasons. There is an actual procedure required in order to get Link2SD to work properly with these devices.
The ROM must be trimmed prior to installing or immediately after installing on to the device. See question #3 above.
The biggest issue with Link2SD is the lack of free space on the devices system partition. I recommend a minimum 1024 MB ( 1 GB ) partition on the sdcard, formatted as ext4.
Now install Link2SD. After it installs, open it and let it create it's mount scripts.
Reboot device. On this first boot Link2SD will create it's symlinks and move whatever files it needs to move.
Reboot device once more for good measure.
From here, assuming that you have removed enough from the ROM when trimming it, the Google Apps package should be installed via your preferred recovery.
Reboot. You should see a "Android is updating apps" notification as the ROM starts.
[SIZE=+1]Q6: How can I get rid of Link2SD before migrating to another *2SD script?[/SIZE]
Link2SD installs scripts etc. in 2 places
/system/etc/init.d
/system/etc/install_recovery.sh
Delete both mounting scripts and delete the /data/sdext2 folder to get rid of Link2SD. For credit and more details please see this post.
[SIZE=+1]Q7: I have installed CM10.1. What happened to the Developer Options?[/SIZE]
On the device, go to Settings -> About Phone. Scroll to and tap on the build number 7 - 8 times until you get a toast notification that states that Developer Options are enabled. Press the "Back" button. A Developer Options item should appear in the main settings list, usually just before About Phone. Press the Developer Options item and then enable Developer Options with the toggle at the top of the page.
[SIZE=+1]Q8: I'm running CM10.1. Where is the advanced power menu?[/SIZE]
If Developer Options are not enabled, see question #7 above. Go to Settings -> Developer Options and enable "Advanced Reboot".
[SIZE=+1]Q9: I just flashed a ROM and I have no network. What should I do?[/SIZE]
All ROMs from CM7 and newer are built for new baseband. This is more than likely because of the wrong baseband. The P509 and P506 are old baseband devices. P500 and P505 devices that didn't get the official update are also old baseband. You can flash the old baseband patch via CWM or any other recovery to remedy this problem. Please see post #8 for the old baseband patch.
It is also possible the the APN for your carrier is either not set up or is incorrectly set up.
[SIZE=+1]Q10: What is the best method for installing a ROM?[/SIZE]
In my opinion it is always best to perform all wipes, even when upgrading the same Android version, although it is not really required when upgrading. The following steps are assuming that you are using CWM.
Boot device in to Recovery. If you don't have a custom recovery, please see question #2 above.
Perform "Wipe data/factory reset". This will format the /data, /cache, /sdext, and .android_secure
Select the "Advanced" option and on the next screen select "Wipe Dalvik Cache". Confirm the wipe.
Not necessary but I do it anyway, in the "Advanced" screen select "Wipe battery stats" and the confirm that wipe
For a clean installation I recommend formatting the system partition too. From CWM home screen select "mounts and storage". On the next screen select "format /system" and then confirm the format.
Press the back button until you are back in the CWM home screen. Select "Install zip from sdcard" and then select "Choose zip from sdcard". Browse your sdcard for the ROM to install and select it. Confirm the installation. Now wait for the install to finish.
Go back to CWM's home screen. Select "reboot system now" option and let the device boot. The initial boot will take a couple of minutes. Don't panic.
If you intend to install any patches or Google Apps, reboot device into recovery and repeat step 6 for each additional package to install.
[SIZE=+1]Q11: How can I make Voice Search work with Google Now in JB roms?[/SIZE]
I have gathered links to several posts regarding this, and they can be found here
*
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to everyone who contributed to the production of this FAQ
Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread. More Frequenty Asked Questions and their answers are welcome here and I will add them to the OP.
Q: How can I get rid of Link2SD, before migrating to another *2SD script?
A: Link2SD installs in 2 places, /system/etc/init.d & /system/etc/install_recovery.sh
You need to delete them both mounting scripts, and also delete the /data/sdext2 folder to get rid of link2sd...
Credit here
Personally, I like Mounts2SD :good:
Let's see if we can get this into a sticky...
Q: Can changing baseband from Lgmdp brick my phone?
A: No.
Sent from my LG-P500 using Tapatalk 2
shinobisoft said:
It's in the Q&A forum
Click to expand...
Click to collapse
Found it! Oh, and they made it sticky too... great work!!
We need a list of working *2sd with cm10/10.1
Does this F.A.Q. meant to be only for cm10/10.1?
uf0999 said:
We need a list of working *2sd with cm10/10.1
Does this F.A.Q. meant to be only for cm10/10.1?
Click to expand...
Click to collapse
No. It's not meant for any specific Android version at all. This FAQ is still a WIP. This FAQ is intended to be a starting point for new members. It is not designed or intended to go in to too much detail about anything. Questions with lengthy answers are answered in short form when possible. If more explanation is needed, then a link or links will be included to direct the member to the correct thread.
As for what you have stated, I will see what I can come up with. Some of the *2SD scripts can be problematic setting up and require special details. Link2SD and Mounts2SD are two problematic ones right off the top of my head.
Thanks for the suggestion.
Old baseband patch
Here's the old baseband patch.
Q: How can I make Voice Search work with Google Now in JB roms?
A: I have gathered links to several posts regarding this, and they can be found here:
http://forum.xda-developers.com/showpost.php?p=39156799&postcount=169
sent from a jellybean sitting on an ice cream sandwich (and a 3.0 kernel)
Hey Bill, I just now figured out what dovidhalevi was talking about. The link that I posted above works. But the copied link that you posted does not. Gotta love this great software. Got no choice.
Yup. Your link in Q11 is to:
http://forum.xda-developers.com/show...&postcount=169
While it should be to:
http://forum.xda-developers.com/showpost.php?p=39156799&postcount=169
ibub said:
Hey Bill, I just now figured out what dovidhalevi was talking about. The link that I posted above works. But the copied link that you posted does not. Gotta love this great software. Got no choice.
Click to expand...
Click to collapse
post-mortem said:
Yup. Your link in Q11 is to:
http://forum.xda-developers.com/show...&postcount=169
While it should be to:
http://forum.xda-developers.com/showpost.php?p=39156799&postcount=169
Click to expand...
Click to collapse
Thanks
No sure how the URL error came about as I copied the link directly from ibub's post, but in any case link has been fixed in Q#11.
ibub said:
Q: How can I make Voice Search work with Google Now in JB roms?
A: I have gathered links to several posts regarding this, and they can be found here:
http://forum.xda-developers.com/showpost.php?p=39156799&postcount=169
sent from a jellybean sitting on an ice cream sandwich (and a 3.0 kernel)
Click to expand...
Click to collapse
will all roms will work on this baseband
That "oldbasebandfix.zip" is to make a new baseband rom work with a phone that has old baseband. Check the thread for the rom to check for baseband requirements.
sent from the p509 that I thought I killed again... no trouble at all
What is the most stable Jelly Bean ROM i can install on my P500? there are a lot of ROM. i tried CM10(Build 7) from Rashed97 but after a few weeks it crashes some (well most) of my application. Thanks in advanced!
mackoyskii said:
What is the most stable Jelly Bean ROM i can install on my P500? there are a lot of ROM. i tried CM10(Build 7) from Rashed97 but after a few weeks it crashes some (well most) of my application. Thanks in advanced!
Click to expand...
Click to collapse
reboot to recovery, clear cache once a couple of days.
mackoyskii said:
What is the most stable Jelly Bean ROM i can install on my P500? there are a lot of ROM. i tried CM10(Build 7) from Rashed97 but after a few weeks it crashes some (well most) of my application. Thanks in advanced!
Click to expand...
Click to collapse
I'm afraid that I cannot personally answer your question. One note, this is not a general discussion thread. Please read or reread the OP.
Ok so I have a couple of problems with my p500.
First of all my phone, doesn't want to connect to my pc. I don't have a clue why, I think it happened for the first time a long time ago while I was fidling with it (can't remember what) and once it connects, my computer says that the device got disconected when it is still connected! I've tried to factory reset but nothing happened still the same.
Secondly the problem that I have is that sometimes the phone boots into emergency mode for no good reason.
It is running on 2.3.3 android and it is not rooted or anything but stock!
Looking forward for your sollutions guys!
Gkikas said:
Ok so I have a couple of problems with my p500.
First of all my phone, doesn't want to connect to my pc. I don't have a clue why, I think it happened for the first time a long time ago while I was fidling with it (can't remember what) and once it connects, my computer says that the device got disconected when it is still connected! I've tried to factory reset but nothing happened still the same.
Secondly the problem that I have is that sometimes the phone boots into emergency mode for no good reason.
It is running on 2.3.3 android and it is not rooted or anything but stock!
Looking forward for your sollutions guys!
Click to expand...
Click to collapse
This is not a general help thread. Please reread the OP. In this case you should've started another thread. But in any case...
A partial answer to your question can be found here
Sounds like the drivers need to be reinstalled on your PC. They should be uninstalled, reboot PC, reinstalled, and reboot once more. Power off your device. Attach data cable to device assuming its already attached to a USB port that is not a hub. Now power on the device and let the driver installation do it's thing.
The above is assuming you've managed to get your device to properly boot.
Best of luck.
Hello everyone!
Since xda won't let me ask directly in the relevant thread (as I am a 'noob' here), I guess here's the correct place. So here we go:
Does anyone know how to enable a hardware video playback on P-500 with Evoking 2.1 ROM (Skydragon)? I use Mobo Player, and in several earlier versions of Evoking it simply did a software mode fallback. Tried V-Player, but it simply crashes (as well as 'Now playing' and some other media-related apps in this ROM).
-regards
-p
I am a total newbie to Android modifications, and tried to find a way of specifying custom notifications on my HTC One Max. I have later found the application Ringdroid that fixes everything that I needed, but before I did that, I believed that I had to root the phone to achieve this. So, I read a lot of stuff, downloaded a lot of files, messed with adb, clockworkmod, rumrunner etc. without really knowing what I was doing, and in the end gave up, since it didn't look like I managed to root the phone properly after all. But, anyway, I understood that something had changed, since a couple of applications were missing. Anyway, the phone has worked fine since then, until recently, when I got a notice that software update 4.13.401.7, containing Android 5.0 Lollipop, and various other stuff, was ready for installation. So, I downloaded the update, and told it to install. The phone reboots, and then I get the following message:
CWM-based Recovery v6.0.5.1
E: Invalid command argument
E: Invalid command argument
Finding update package...
E: unknown volume for path [INTERNALSDCARD:0/Do
wnload/OTA_T6_UL_L50_SENSE60_MR_HTC_Europe_4.1
3.401.7-3.23.401.1_release_4360116ezjvoz69qm8r
zky.zip]
E: Can't mount INTERNALSDCARD:0/Download/OTA_T6
_UL_L50_SENSE60_MR_HTC_Eutope_4.13.401.7-3.23.
401.1_release_4360116ezjvoz69qm8rzky.zip
Installation aborted.
Rebooting...
Is there a way of letting me a) reset my phone to the default settings, letting me do this upgrade? or b), do this upgrade without resetting it?
XDA Visitor said:
I am a total newbie to Android modifications, and tried to find a way of specifying custom notifications on my HTC One Max. I have later found the application Ringdroid that fixes everything that I needed, but before I did that, I believed that I had to root the phone to achieve this. So, I read a lot of stuff, downloaded a lot of files, messed with adb, clockworkmod, rumrunner etc. without really knowing what I was doing, and in the end gave up, since it didn't look like I managed to root the phone properly after all. But, anyway, I understood that something had changed, since a couple of applications were missing. Anyway, the phone has worked fine since then, until recently, when I got a notice that software update 4.13.401.7, containing Android 5.0 Lollipop, and various other stuff, was ready for installation. So, I downloaded the update, and told it to install. The phone reboots, and then I get the following message:
CWM-based Recovery v6.0.5.1
E: Invalid command argument
E: Invalid command argument
Finding update package...
E: unknown volume for path [INTERNALSDCARD:0/Do
wnload/OTA_T6_UL_L50_SENSE60_MR_HTC_Europe_4.1
3.401.7-3.23.401.1_release_4360116ezjvoz69qm8r
zky.zip]
E: Can't mount INTERNALSDCARD:0/Download/OTA_T6
_UL_L50_SENSE60_MR_HTC_Eutope_4.13.401.7-3.23.
401.1_release_4360116ezjvoz69qm8rzky.zip
Installation aborted.
Rebooting...
Is there a way of letting me a) reset my phone to the default settings, letting me do this upgrade? or b), do this upgrade without resetting it?
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
First, please create an account so you can post in other forums.
Here is the main forum area for your device:
http://forum.xda-developers.com/htc-one-max
Here's where you should ask for help:
http://forum.xda-developers.com/htc-one-max/help
Consider bookmarking these sites for future reference.
Your device experts are located there and will be able to help.
Good luck!