Related
I was wondering if it was possible to un-root a G1. I'm honestly having the hardest time with it. I've downgraded to RC29 but when trying to add "RC33: (md5: f24b6c237775147cb4bc42efc2393973)" it doesn't want to add when ... I followed the steps on the step by step of adding it and it always hangs up and wont add when in recovery mode while pressing Alt-S to apply the update.
-Could this be a problem because for some reason while i was putting in the info into Telnet it hung up at the recovery.img portion. Sorry new about moding phones... Cars i know phones i don't
I'm in the LA area if anyone else is and is willing to on there free time show me how i keep screwing up. Thanks
All you gotta do is reflash the DREAIMG.NBH file onto your G1 and it'll update by itself, which means you'll be back to stock.
Edit: Are you by any chance unzipping the file? If you are, you have to leave it unzipped and just rename to update.zip in the SD card.
skiptomylou11 said:
All you gotta do is reflash the DREAIMG.NBH file onto your G1 and it'll update by itself, which means you'll be back to stock.
Edit: Are you by any chance unzipping the file? If you are, you have to leave it unzipped and just rename to update.zip in the SD card.
Click to expand...
Click to collapse
no i'm leaving it update.zip like the set by step said. And how do i refresh it? Im on yahoo messenger by the same name on here if your on this to help me. Thank You
-i rather keep it rooted and not have to revert to tmo's software but 4 hours and i feel like a total moron
Why would you want to unroot your phone? But if you really want to then just flash back to RC29 then wait for the phone to get the OTA updates.
I don't want to unroot but im unable to add 1.5 like i intended on doing. So right now im stuck with rc 29 and not cuppycake like i want. I wanted to re-up back to 33 like it said in the posting i was using as step by step and it wont allow me to update
Questions on Android 1.5 and rooting
Some advice will be appreciated!
I just got my G1 a few days a go I was reading from the Official t-mobile web site that the up-grade for android will be out randomly to customers and their expecting that all of us customers will have it by the end of May
Now should I go thru all the work of rooting my G1 and getting cupcake or just wait for the upgrade?
Is there a difference between the two of them?
In the upgrade to 1.5 I don’t see or read anything about the apps getting install and running from the memory card does anyone about this?
Thanks in advance!
In the upgrade to 1.5 I don’t see or read anything about the apps getting install and running from the memory card does anyone about this?
Thanks in advance!
Click to expand...
Click to collapse
Thats only available to rooted phones.
Now should I go thru all the work of rooting my G1 and getting cupcake or just wait for the upgrade?
Click to expand...
Click to collapse
It all depends... If youre ONLY rooting to get cupcake, I would just say wait. See this link for some reasons why you would want to root and step by step instructions:
http://forum.xda-developers.com/showthread.php?t=442480
You can render your phone useless however while doing this. So BE CAREFUL... Youve been warned!
how to unroot my g1
So I rooted my phone and installed JF1.5 and my SD card is now acting a bit weird, and I want to undo the root and mod so I can go back to factory. How do I do this? Is this even possible now?
Thanks
yes, just flash an original RC33 firmware update... use search next time.
i got ya dude
http://forum.xda-developers.com/showthread.php?t=491350
go there
Interesting root problem
Hey guys, been playing in a cupcake irc channel, while we are all waiting for ota cupcake, helping half a dozen or so people root, and i came across one that i figured i'd post here, and see if anyone has any ideas. Obviously i don't have his phone in hand, so i can't be 100% sure that he isn't flubbing a step, but he seems compitent enough to follow simple instructions. He has a stock g1 pvt board with an 8 gig transcend class 6 sdcard, we have formatted this card many times, we get through the nbh file, installs fine, telnetd steps no problem, put the update.zip on the sd card and boot into the bootlader, and everything goes hey wire, it cant find nor install the update.zip, we have redownloaded different spl's to try, triple verified the files weren't named update.zip.zip. the only odd thing i found about his phone, was in one of the threads on here, people were checking the output of the mount command, and for some reason for his sd card his output is /dev/block/mmcblk0p5 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0 where everyone esles is p0 or p1 i cant quite remember. anyhow any ideas or suggestions would be great and no he does not have another sdcard at the moment for us to get it done with
Thanks in advance
ps this is his output form the boot loader
The top says:
Android system recovery utility
using test keys
e:cant open /cache/recovery/command
then when I hit alt+s
Installing from sdcard...
Finding update package...
E:Cant mount /dev/block/mmcblk0 p1 (or /dev/block/mmcblk0)
(Invalid arguement)
E:Cant mount sdcard:update.zip
installation aborted
should be something simple like editing fstab or mount.conf or useing a symlink right, can anyone help me with the commands searching left and right here over edge is killing me
wat is the whole output of the mount command?
n1gh7m4r3 said:
Hey guys, been playing in a cupcake irc channel, while we are all waiting for ota cupcake, helping half a dozen or so people root, and i came across one that i figured i'd post here, and see if anyone has any ideas. Obviously i don't have his phone in hand, so i can't be 100% sure that he isn't flubbing a step, but he seems compitent enough to follow simple instructions. He has a stock g1 pvt board with an 8 gig transcend class 6 sdcard, we have formatted this card many times, we get through the nbh file, installs fine, telnetd steps no problem, put the update.zip on the sd card and boot into the bootlader, and everything goes hey wire, it cant find nor install the update.zip, we have redownloaded different spl's to try, triple verified the files weren't named update.zip.zip. the only odd thing i found about his phone, was in one of the threads on here, people were checking the output of the mount command, and for some reason for his sd card his output is /dev/block/mmcblk0p5 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0 where everyone esles is p0 or p1 i cant quite remember. anyhow any ideas or suggestions would be great and no he does not have another sdcard at the moment for us to get it done with
Thanks in advance
ps this is his output form the boot loader
The top says:
Android system recovery utility
using test keys
e:cant open /cache/recovery/command
then when I hit alt+s
Installing from sdcard...
Finding update package...
E:Cant mount /dev/block/mmcblk0 p1 (or /dev/block/mmcblk0)
(Invalid arguement)
E:Cant mount sdcard:update.zip
installation aborted
Click to expand...
Click to collapse
is the phone plugged into computer UsB?
korndub said:
is the phone plugged into computer UsB?
Click to expand...
Click to collapse
hehe no its looking at mmcblk0p1 which doesn't exist
Getting Root on the 1.5 CRB43...The same process as before???
Im so sorry for posting... I can't clearly find any answer.
What is needed, if anything to access root on the G1 with the 1.5US crb43 OTA "cupcake" update.
Thanks in advance!!!
Clay
htcclay said:
Im so sorry for posting... I can't clearly find any answer.
What is needed, if anything to access root on the G1 with the 1.5US crb43 OTA "cupcake" update.
Thanks in advance!!!
Clay
Click to expand...
Click to collapse
Usual steps I would imagine, downgrade to RC29 with DREAMING,,,, ya da ya da ya! follow the link
Dantehman said:
Usual steps I would imagine, downgrade to RC29 with DREAMING,,,, ya da ya da ya! follow the link
Click to expand...
Click to collapse
You are the man!
Thanks for the quick reply!!!
Anyone finds out differently please post.
I'm going to give it a shot...
Clay
I just manually updated my phone to the new cupcake 1.5 US version. I would like to root my phone but don't I have to wait until the modify version comes out? Or can I root right now by downgrading and then manually upgrading to stock cupcake again? Will upgrading with the stock cupcake update wipe out the root?
Goog1e Phone said:
I just manually updated my phone to the new cupcake 1.5 US version. I would like to root my phone but don't I have to wait until the modify version comes out? Or can I root right now by downgrading and then manually upgrading to stock cupcake again? Will upgrading with the stock cupcake update wipe out the root?
Click to expand...
Click to collapse
root now...root later...no difference
Hi, i stumbled upon a problem which noone else seems to notice.
I appplied the danger spl to gain more space for my apps.
Since then im using a qwerty keyboard layout instead of qwertz. Y is replaced with z, umlauts are broken, etc. Took me a while to find out its the spl. First i thought its the rom but the only way to get it fixed was to roll back to hard spl. i have two questions about this: wth has the spl to do with the keyboard layout and is there a way to edit keymap files in /system or something to workaround the problem? Strangely the usual keymap settings there dont seem to do the trick.
You usually need to do a wipe after you apply a new SPL
may i suggest using apps2sd for more space for apps. danger spl is only used to allow larger roms to be flashed.
sHR00m said:
Hi, i stumbled upon a problem which noone else seems to notice.
I appplied the danger spl to gain more space for my apps.
Since then im using a qwerty keyboard layout instead of qwertz. Y is replaced with z, umlauts are broken, etc. Took me a while to find out its the spl. First i thought its the rom but the only way to get it fixed was to roll back to hard spl. i have two questions about this: wth has the spl to do with the keyboard layout and is there a way to edit keymap files in /system or something to workaround the problem? Strangely the usual keymap settings there dont seem to do the trick.
Click to expand...
Click to collapse
Well, i have the same problem. How can i change the layout?
The problems does indeed lie within the "Danger" SPL. But you only need to change the keychars file. No need to switch to another SPL, or install some apps2sd gibberish.
http://www.mediafire.com/?tdnna5atnzn
Download the file and move it into the tools folder of your SDK. Now use adb to push the file to the device.
ex.
Code:
adb remount
adb push trout-keypad-v3.kcm.bin system/usr/keychars/
adb reboot
Done.
shane, of course i did a wipe before
joe, im aware that i can store apps on sd, but i simply dont have a class6 card atm and the danger spl worked fine except for this phenomenon. also i wanted to try a hero rom, which was the first reason to flash it. but since it gives me a double sized data partition, why dont use it anyway? hell even the browser temp files can fill that partition quickly..
ah thanks bavilo. i think i tried that before but maybe i did something wrong
edit: YEP ITS WORKING, thanks! =)
Introduction
If you are rooted and running a Hard SPL or a Stock SPL and really want to flash a ROM that claims to require Danger/Haykuro SPL, but you do not want to upgrade your SPL there are alternative ways to make these ROMs work on your phone without upgrading your SPL.
This is a very easy process, Ive done it with a few ROMs with no problems:
First off, keep in mind that on a Stock SPL
/system = about 67MB
Any ROM that has a system partition 67MB or Greater will require Danger/Haykuro SPL, UNLESS you can shrink that ROM's /system down below 67MB.
How do you do this, you ask?
------------------------------------------------------------------------------------------------------------------------------------------------------
Method #1 (Easy) -Move/Delete unneeded Apps, Sounds, Files
------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE: This Method does NOT apply to HERO/SENSE ROMs, they are way too big! Check Method 2 if you want to fit ANY ROM on any SPL (Advanced)
Make sure you have 7-Zip! Dont have it? Google is your friend!
1) Read the first post and changelog of the ROM you wish to install on your phone. After youve made yourself familiar with what needs to be Wiped (ie: dalvik cache, ext, data) the Partition Layout the developer suggests (ie: FAT32/Ext3/Swap), then go ahead and download the ROM. Unzip it to a folder, name it something short. for example: C:\1\rom
now click on the system folder, scroll down and click on the media folder, and delete the audio folder. This will erase every sound effect and ringtone on your phone and usually will free up about 2MB in system.
To get your ringtones and sounds back download this (thanks Robot Teapot!) and unzip the folder to the root of your sdcard. (note: your ringtones might not show up the first time you boot the rom, in this case, reboot and theyll all be right there)
If removing your ringtones isnt enough to keep /system under 67MB then move on to step 2), if youre already below 67MB skip to step 3)
2) Return to the first post and changelog of the ROM you are trying to install. Look for apps the dev has added to the ROM that dont seem necessary for the ROM to function such as Twidroid.apk, Facebook.apk, NeroMedia.apk, WirelessTether.apk, WiredTether.apk, Maps.apk(takes up a lot of room, and sometimes outdated...just delete it and install the latest from the market!)etc.
You can use Android Barebones/Necessary Apps - CyanogenMod Wiki as a general guideline to determine which apps are essential to Android running properly and the functions of many system apps.
Delete those unnecessary apps or move them to your sdcard, and use ASTRO File Manager or a similar app to install them after you flash the ROM.
3) Okay, assume youve trimmed /system down below 67MB, good job! now you need to get those folders you extracted and the boot.img zipped up and signed. select the folders from the ROM you extracted and modified, the boot.img, right click, and select 7-Zip < Add to .zip
4) Download Stericson's Autosign place it in any directory and follow the instructions in the thread to sign your zip file.
5) Move the signed zip to your SD Card, making sure you have the proper partitions, wipe the necessary things, then flash your zip file and cross your fingers!
------------------------------------------------------------------------------------------------------------------------------------------------------
Method #2 (Advanced) -"Cache Hack"
------------------------------------------------------------------------------------------------------------------------------------------------------
NOTE: This Method will fit any ROM on any SPL but is more advanced than Method 1
lbcoder introduced the concept of moving files to the /cache partition of the phone and linking them back to /system or /data.
Firerat has come up with a way to make this concept work and explains the whole process in his thread and shows some examples of his method by providing some ports:
[HACK][ROM][BOOT.IMG][CACHE]-Stk SPL ROMs with Danger SPL size & extra 30mb! any SPL!
------------------------------------------------------------------------------------------------------------------------------------------------------
There you have it folks! Congrats if youve bypassed the Danger SPL requirements! Be sure to always keep a Nandroid/BART backup!!!!
Disclaimer: Not saying these methods will brick or damage your phone, but in the rare event this occurs I am NOT responsible for bricks or or any damages to your phone!
Autosign doesnt need to be in the SDK place, I had it in my music folder and it worked fine.I accidentally formatted my PC last night and dont have the SDK installed but autosign works for me so im happy.
Note to OP-You cant brick from flashing any 32B rom, you would only get a blank screen that stays..which some seem to call soft-brick, i call it nonsense though.
Thanks for this excellent tutorial
Ace42 said:
Autosign doesnt need to be in the SDK place, I had it in my music folder and it worked fine.I accidentally formatted my PC last night and dont have the SDK installed but autosign works for me so im happy.
Note to OP-You cant brick from flashing any 32B rom, you would only get a blank screen that stays..which some seem to call soft-brick, i call it nonsense though.
Click to expand...
Click to collapse
Really? I had no idea that the SDK wasnt required, ill remove that.
and yeah i know its usually a soft brick, if anything, and youre right its nonsense, and can be solved using a nandroid backup and wiping the proper things, but im playing it safe with that disclaimer just like the rom devs do lol
migalito said:
Thanks for this excellent tutorial
Click to expand...
Click to collapse
.
Youre welcome! I hope it works out for you!
Will this work with the Super D rom?
cg87 said:
Will this work with the Super D rom?
Click to expand...
Click to collapse
yes! I tried it on Super D!
speedysilwady said:
yes! I tried it on Super D!
Click to expand...
Click to collapse
Then I'm so confused. If it's possible, why does the rom still require the Danger SPL? Why didn't bbuchacher make it so it doesn't require the Danger SPL? Doesn't make any sense to me. Can someone please enlighten me?
cg87 said:
Then I'm so confused. If it's possible, why does the rom still require the Danger SPL? Why didn't bbuchacher make it so it doesn't require the Danger SPL? Doesn't make any sense to me. Can someone please enlighten me?
Click to expand...
Click to collapse
Well, to be honest, im not sure why, but im assuming some developers like to include features and apps that arent necessarily required for the rom to run properly but to make their rom more appealing to users, than other roms. keeping those apps in system prevents those apps from disappearing after you wipe your phone/ext. Plus devs always keep ringtones and sounds included in their roms for completeness's sake.
Now a Hero ROM on the other hand is loaded with system apps that cant be deleted and i dont think theyll ever fit on a Stock SPL, except maybe MicroHero, but im not sure.
But for whatever reason, a lot of regular ROMs are fat and bloated with apps and extras that dont necessarily have to be saved on the system partition,so the best thing to do is shrink those roms down till they fit, if you can't or dont want to upgrade your SPL.
How to make it work *WITHOUT TRIMMING*
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Seems someone else is in the same boat as I am.
Can't update my radio, looks like some kind of hardware problem almost. Tried everything in any possible way.
So it looks like we're stuck with the standard or engineering SPL, which is fine but means there are some restrictions.
I'll try some of the tips you gave and flash something besides Cyanogenmod tonight.
lbcoder said:
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Click to expand...
Click to collapse
I thought about that but I'm not 2 good @ programing unless its cars/video console. But doesn't the cache get used for something after the rom is up and running? Or is it only for ota updates?
If only for ota updates how come the danger spl doesn't give you 120mb or so since cache and system are 67mb each
That's a very good question. Just tried it and it seems to work, though. It's booting as we speak. All system/app files in the cache directory.
EDIT: Actually, all apps seem to force close on boot. So I'll just try it the regular way I guess.
try the Fix apk uid mismatches maybe idk ill try it in a lil bit
*update*
Got a boot loop on openeclair1.0.1 not sure why but dont got the time to fig. it out right now.
also why does a boot loop drain the crap out of your battery?
lbcoder said:
Take a look at your update.zip archive.
Probably has 4 things in the root:
boot.img
system
META-INF
data
If system is greater than about 67MB (or lets say 60 just to be real safe...), then create ANOTHER directory and call it "cache".
Now MOVE /system/app into /cache/
You now have the space cleared up, but it still won't work.
So go into META-INF/com/google/android and edit the script "update-script".
just below the line where it says "format CACHE:", add these lines:
copy_dir PACKAGE:cache CACHE:
set_perm_recursive 0 0 0755 0644 CACHE:
symlink /cache/app SYSTEM:app
Wow, did we just move the extra crap into cache? Yep.
May require slight modification. Use your head.
Click to expand...
Click to collapse
I remember you suggested this a while back when I asked about eclair roms on stock spl, I'm guessing if you use this method and wipe, you'll have to reflash the rom because those system apps are gone, correct?
yea anytime you wipe you would have to reflash the rom because a wipe deletes. data and cache folder
Dr-b said:
That's a very good question. Just tried it and it seems to work, though. It's booting as we speak. All system/app files in the cache directory.
EDIT: Actually, all apps seem to force close on boot. So I'll just try it the regular way I guess.
Click to expand...
Click to collapse
Might be a minor goofup on the permissions. Just verify the permissions and it will be fine.
What programming?
There is no programming involved in this.
Mainly cache is for OTA, but also some other crap related to the download manager.
As for the deathspl allocation, it puts *some* of the /cache into /system, *some* of the /cache into /data, and the balance of /cache remains in /cache.
xile6 said:
I thought about that but I'm not 2 good @ programing unless its cars/video console. But doesn't the cache get used for something after the rom is up and running? Or is it only for ota updates?
If only for ota updates how come the danger spl doesn't give you 120mb or so since cache and system are 67mb each
Click to expand...
Click to collapse
speedysilwady said:
I remember you suggested this a while back when I asked about eclair roms on stock spl, I'm guessing if you use this method and wipe, you'll have to reflash the rom because those system apps are gone, correct?
Click to expand...
Click to collapse
Why would you want to wipe it?
Note: you could just create an update.zip with an update-script that says ONLY "format DATA:" That would wipe the data withOUT wiping the /cache. Maybe name it "betterwipe.zip" and put it on your sdcard. Boot into recovery and apply "betterwipe.zip".
lbcoder said:
Why would you want to wipe it?
Note: you could just create an update.zip with an update-script that says ONLY "format DATA:" That would wipe the data withOUT wiping the /cache. Maybe name it "betterwipe.zip" and put it on your sdcard. Boot into recovery and apply "betterwipe.zip".
Click to expand...
Click to collapse
true, with fix permissions, and wipe dalvik, there really isnt much use in wiping data anymore, but would fix permissions still work if the apps are in cache? i know theyre syslinked, but im not sure how that works with the fix_permissions script. sorry if im asking dumb questions, im still learning.
Ill try your idea a really big rom and see if it works.
just wanted to confirm that all Hero ROMs seem to require Danger SPL, I see no way of shrinking system anywhere close to 67 or less.
But my method should still work on any eclair or donut rom. I still havent had a chance to try lbcoder's method though it should work. if people can get lbcoders method to work ill add it to the first post!
I was just beginning some work on a new rom. I used the same rom kitchen setup I have used before. (adding the Edison file). I imported a backup I just took with CWM, which has always worked, then just to test it I built it without any mods so that I could make sure it was OK. I wiped data and dalvik, then flashed the zip. success. I rebooted and it popped into the fastboot boot failure screen. below were three errors that I do not remember exactly, but they were all CG system something or other. one was 0x18, the other were actual words.
This was not a big deal, I just had to fxz back to stock, root, and then restore the backup I made before hand, but it still scared me for a sec and is a little odd. Does anyone have an Idea what I did wrong?
EDIT: I just realized I forgot to change format system to delete recursive in the updater script. Could that be it?
lkrasner said:
EDIT: I just realized I forgot to change format system to delete recursive in the updater script. Could that be it?
Click to expand...
Click to collapse
Yep that's it. From what I understand... our bootloader checks for certain signatures on /system and other partitions, and if the signatures are wrong or nonexistent then it gives an error similar to what you have. That's the reason we can't flash international system.img's, the signatures don't match up.
Changing "format("...")" to "delete_recursive("/system")" should work.
cogeary said:
Yep that's it. From what I understand... our bootloader checks for certain signatures on /system and other partitions, and if the signatures are wrong or nonexistent then it gives an error similar to what you have. That's the reason we can't flash international system.img's, the signatures don't match up.
Changing "format("...")" to "delete_recursive("/system")" should work.
Click to expand...
Click to collapse
cogeary is 100% correct, you can not use the format keyword in the installer script, it has to be the delete_recursive keyword, lfaber06 and I had these exact same issues when we first started this whole ROM building experiment back in Dec. last year.
thanks, good to know! this scared the crap out of me until I realized it was sitting in fastboot just waiting for me to flash it back.
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!