After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie
siepod said:
After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie
Click to expand...
Click to collapse
You would have a better chance of finding a working solution if you go to the M8 forum.
I'll bet @xunholyx can get you straight, he's pretty experienced with the M8 I think.
siepod said:
After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie
Click to expand...
Click to collapse
You need to run a Sense RUU to resize your partitions. The GPE system partition is too small for Sense based ROMs and RUU is how you fix it. Just like you ran a GPE RUU to resize your partitions for that.
---------- Post added at 06:17 PM ---------- Previous post was at 06:11 PM ----------
If you don't know where to get the RUU, or if you need instructions, post/reply here and I'll give you complete directions on how to do it.
xunholyx said:
You need to run a Sense RUU to resize your partitions. The GPE system partition is too small for Sense based ROMs and RUU is how you fix it. Just like you ran a GPE RUU to resize your partitions for that.
---------- Post added at 06:17 PM ---------- Previous post was at 06:11 PM ----------
If you don't know where to get the RUU, or if you need instructions, post/reply here and I'll give you complete directions on how to do it.
Click to expand...
Click to collapse
Thanks for your reply. Really appreciate your help. I think I'm ok with the RUU process itself, as I ran it to get to this point, however I'm not sure where to locate the RUU I would need to effectively "roll back" to stock, so any help with that, and directing me in which of the plethora to choose would be greatly appreciated! Perhaps if you could give me simple instructions, so it's not too time consuming for you, but to ensure I'm not missing anything in the RUU process that could lead to further complications, that would be a big help too!
siepod said:
Thanks for your reply. Really appreciate your help. I think I'm ok with the RUU process itself, as I ran it to get to this point, however I'm not sure where to locate the RUU I would need to effectively "roll back" to stock, so any help with that, and directing me in which of the plethora to choose would be greatly appreciated! Perhaps if you could give me simple instructions, so it's not too time consuming for you, but to ensure I'm not missing anything in the RUU process that could lead to further complications, that would be a big help too!
Click to expand...
Click to collapse
Download this splash.zip, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Next, download this RUU onto your PC to update to Lollipop. Hook up your phone and double click on the download, then follow the prompts. You'll probably get a "fail hboot pre-update" (or something like that). The first run updates the hboot with old firmware. Just run the RUU a second time without disconnecting, and the conversion back to Sense will be complete.
xunholyx said:
, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Click to expand...
Click to collapse
You are an absolute star, thank you. Will give this a bash when I get home from football later today, and let you know how I get on or if I have any problems. Great written instructions though, thanks!
xunholyx said:
, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Click to expand...
Click to collapse
Just had a try, get Update Fail! in red text when I try to do the Hboot. Not sure why?
Thanks,
Sie
siepod said:
Just had a try, get Update Fail! in red text when I try to do the Hboot. Not sure why?
Thanks,
Sie
Click to expand...
Click to collapse
I'm not sure.
Try the splash.zip download and instructions from here. It should be the same file, but trying another download and flashing from your PC might work better for you.
xunholyx said:
I'm not sure.
Try the splash.zip download and instructions . It should be the same file, but trying another download and flashing from your PC might work better for you.
Click to expand...
Click to collapse
Brilliant, tried those and it worked a treat. Then installed using the RUU you gave me, and as promised I was greeted with a full back to stock Sense version, and have been able to install the ROM I wanted. Thanks once again for all your help, truly appreciated!
I'm guessing it was the CID that was causing the error, if anybody has the same problem in the future and ends up on this thread. I'm guessing if I'd have changed the CID your method with the HBOOT would probably have worked too (as out of curiosity I tried the HBOOT method with your file and it then worked).
Thanks again, great to know there are people out there willing to try and help each other. :highfive:
Related
Hi guys.
I know that the various aspects of this post are covered in other posts, but I haven't seen anything that acts like a step by step or repository for this info.
Basically, I have a VodafoneAU HTC Magic with 1.5 on it, and I'd like to flash on it one of the Hero roms. I used to have a Diamond and then Diamond Pro, but I know little about Android at this point.
My biggest fear is bricking the phone, followed by not being able to restore my previous rom (and even apps and settings would be awesome too, though not essential) should something go pear shaped.
I know the steps I need to follow are:
1 - Root the phone
2 - Back up ROM (settings/apps too?)
3 - Flash new ROM
4 - ?????
5 - Profit (in the form of enjoying an awesome Hero ROM)
Jokes aside, if someone can point me in the right direction for the first 3 steps, that'd be great. Even if it's as simple as
1 - Root it using this post (link)
2 - Use this App to back it up
3 - etc..
Like I said, I know this info is probably covered elsewhere, but not in one place (that I've found) and I'd hope this post could serve as a guide for anyone else looking to go the same steps as me.
Thanks for any help anyone can give.
Cheers.
First off, you don't need to root your phone, update the SPL, or any of that scary stuff. Which is great, cus that's the riskiest part of it all. Briefly, the procedure is as follows:
1. Boot your phone in fastboot mode (power the phone off, then hold the back button as you power it back on). You'll see a white screen with some text, the word "FASTBOOT" and some androids at the bottom.
2. Note the version numbers you see at the top of the screen - it'll look something like:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.3300.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
3. Download the ROM you want to upgrade to for your phone's version, rename the zip to update.zip and put it on the root of your phone's SD card
4. Boot a recovery ROM using fastboot (from the Android SDK)
5. Use Nandroid Backup to back up your current firmware to the SD card
6. Copy that backup (and the rest of the contents of your SD card) to your PC, just in case. This is the last point at which you can back out!
7. Use the recovery ROM to wipe your phone's existing firmware
8. Use the recovery ROM to apply the update.zip from the SD card
9. Wait for the update to complete
10. Reboot your phone and enjoy your new ROM!
I did this on my Vodafone NZ HTC Magic (PVT32B) running 1.5 yesterday and am enjoying Hero on it right now, barring a few quirks. If you like, I'll put together a detailed step-by-step of the procedure.
KarrdeNZ said:
First off, you don't need to root your phone....
I did this on my Vodafone NZ HTC Magic (PVT32B) running 1.5 yesterday and am enjoying Hero on it right now, barring a few quirks. If you like, I'll put together a detailed step-by-step of the procedure.
Click to expand...
Click to collapse
Awesome, cheers. I'll have a crack at it tonight then.
So Am I correct then in assuming step 5 backs up my phone as it is now? So essentially if I roll back it will be exactly as it was? Installed apps, settings, contacts (although sync sorts that out) and all?
papalazarou said:
So Am I correct then in assuming step 5 backs up my phone as it is now? So essentially if I roll back it will be exactly as it was? Installed apps, settings, contacts (although sync sorts that out) and all?
Click to expand...
Click to collapse
Nope. Nandroid only backs up the existing firmware (and I believe some settings). It doesn't back up texts, contacts (though those should be synced with your Google Account anyway), or apps. For the most part, apps are easy to retrieve from the Market, but if you have any you got from elsewhere you'll need to reacquire them. The app MyBackup Pro seems to be recommended on these forums for more thorough backups, though it isn't free (and I've not used it myself). As my phone was (relatively) new I wasn't too fussed about keeping backups of anything except the firmware.
I've done a couple of Nandroid backups and restores and it restores everything (except SD card), meaning applications, settings, everything is restored.
Also, I highly recommend RAv's recovery (http://forum.xda-developers.com/showthread.php?t=530492). Use it to make your Nandroid backup .
Wysie said:
I've done a couple of Nandroid backups and restores and it restores everything (except SD card), meaning applications, settings, everything is restored.
Click to expand...
Click to collapse
I've heard differing reports on what Nandroid does and doesn't back up, so was erring on the side of caution. But if it backs up everything, awesome.
And yep, that's the recovery ROM I used. I'm writing up the step by step instructions at the moment - will post em when they're done.
KarrdeNZ said:
I've heard differing reports on what Nandroid does and doesn't back up, so was erring on the side of caution. But if it backs up everything, awesome.
And yep, that's the recovery ROM I used. I'm writing up the step by step instructions at the moment - will post em when they're done.
Click to expand...
Click to collapse
depends how you restore it- you can restore system.img only and not get all your data etc (using fastboot) but if you fastboot data.img as well then you get it all..... the new recovery restores it all...
KarrdeNZ said:
First off, you don't need to root your phone, update the SPL, or any of that scary stuff. Which is great, cus that's the riskiest part of it all. Briefly, the procedure is as follows:
1. Boot your phone in fastboot mode (power the phone off, then hold the back button as you power it back on). You'll see a white screen with some text, the word "FASTBOOT" and some androids at the bottom.
2. Note the version numbers you see at the top of the screen - it'll look something like:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.3300.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
3. Download the ROM you want to upgrade to for your phone's version, rename the zip to update.zip and put it on the root of your phone's SD card
4. Boot a recovery ROM using fastboot (from the Android SDK)
5. Use Nandroid Backup to back up your current firmware to the SD card
6. Copy that backup (and the rest of the contents of your SD card) to your PC, just in case. This is the last point at which you can back out!
7. Use the recovery ROM to wipe your phone's existing firmware
8. Use the recovery ROM to apply the update.zip from the SD card
9. Wait for the update to complete
10. Reboot your phone and enjoy your new ROM!
I did this on my Vodafone NZ HTC Magic (PVT32B) running 1.5 yesterday and am enjoying Hero on it right now, barring a few quirks. If you like, I'll put together a detailed step-by-step of the procedure.
Click to expand...
Click to collapse
I am a noob...Why don't need to FLASH SPL and ROOT the phone?? But u can still flash into HERO rom. I would like to have a full flash procedure from you,thanks. My machine is running on PVT32A.
snowhk said:
I am a noob...Why don't need to FLASH SPL and ROOT the phone?? But u can still flash into HERO rom.
Click to expand...
Click to collapse
You can load the Hero ROM without replacing your SPL (in most cases) or rooting, so why replace it if you don't need to? I've done it myself without doing so and it's working fine.
My guide is now ready - check it out at http://www.karrderized.com/romguide/.
KarrdeNZ said:
You can load the Hero ROM without replacing your SPL (in most cases) or rooting, so why replace it if you don't need to? I've done it myself without doing so and it's working fine.
My guide is now ready - check it out at http://www.karrderized.com/romguide/.
Click to expand...
Click to collapse
Just ask for curiosity..But why did others do so?? Thanks. You provided a clear guide.^^
snowhk said:
Just ask for curiosity..But why did others do so?? Thanks. You provided a clear guide.^^
Click to expand...
Click to collapse
I think some SPL versions prevent ROM updates and so need to be replaced with versions that do, but I'm not sure. I'll let someone more knowledgeable take that question.
And thanks, I tried to make the guide as easy as possible
KarrdeNZ said:
I think some SPL versions prevent ROM updates and so need to be replaced with versions that do, but I'm not sure. I'll let someone more knowledgeable take that question.
And thanks, I tried to make the guide as easy as possible
Click to expand...
Click to collapse
My device shows the followings:
Sapphire PVT 32A Ship S-ON H
HBOOT-1.33.0009(SAPP10000)
CPLD-12
RADIO-3.22.20.17
Would my SPL version prevent the update?Coz I afraid of bricking my phone>< I got too many questions. Hope u can have a help. Thanks.
snowhk said:
My device shows the followings:
Sapphire PVT 32A Ship S-ON H
HBOOT-1.33.0009(SAPP10000)
CPLD-12
RADIO-3.22.20.17
Would my SPL version prevent the update?Coz I afraid of bricking my phone>< I got too many questions. Hope u can have a help. Thanks.
Click to expand...
Click to collapse
According to http://forum.xda-developers.com/showthread.php?t=529019 you should be fine. If you're unable to boot the recovery ROM (step 8 in my guide) then stop there, as I believe that's about where problematic SPLs first show signs of trouble. Just make sure you get ROMS for 32A.
KarrdeNZ, thanks for your fantastic guide! Are you OK to put it up as a stick thread within this forum?
i believe you can only do this with signed roms but this is only from what i have read on here, but to be fair its not hard to root anyway and aslong as your not a dumbass its pretty straight forward and can benefit from bluetooth file sharing and apps2sd and tethering so deffo worth it, opens up your phone to numerous possibilities
eva_d said:
KarrdeNZ, thanks for your fantastic guide! Are you OK to put it up as a stick thread within this forum?
Click to expand...
Click to collapse
Sure, not a problem I'd prefer the thread link to the guide so that new versions are easy to find, but whatever works.
KarrdeNZ, mate I followed your guide to the letter. I got all the way down to step 11 and then a problem occurred.
When I clicked 'Apply sdcard:update.zip' it just said cannot find or cannot load update.zip, or something like that, then said operation aborted?
I was trying to install the EXACT same ROM as you, I downloaded it to my laptop, renamed it update.zip and moved it to the root of the SD card.
Yet it didn't work, I can't for the life of me think where it's gone wrong as everything else up to that point had gone smoothly.
Any idea's?
Well I tried downloading the same file again. No luck this time either!
This is what it says when I click the install from sdcard button:
--install from sdcard...
Finding update package...
Opening update package...
E: Can't open /sdcard/update.zip
(no such file or directory)
Installation aborted.
Now I get that it's saying that it can't find the file but I really don't understand why? I mean the file is there, do I have to unzip the file onto my computer 1st and then put it on the sdcard?
I thought i just stuck the zipped file onto the root of the card making sure i renamed it 'update.zip'
Please help me out guys, thanks.
The exact thing happened to me; and I realized I was dumb and had named the file "update.zip", when in fact it should just be "update". The file extension should come naturally since the file is still compressed.
Roy_Drage said:
Well I tried downloading the same file again. No luck this time either!
This is what it says when I click the install from sdcard button:
--install from sdcard...
Finding update package...
Opening update package...
E: Can't open /sdcard/update.zip
(no such file or directory)
Installation aborted.
Now I get that it's saying that it can't find the file but I really don't understand why? I mean the file is there, do I have to unzip the file onto my computer 1st and then put it on the sdcard?
I thought i just stuck the zipped file onto the root of the card making sure i renamed it 'update.zip'
Please help me out guys, thanks.
Click to expand...
Click to collapse
KarredeNZ, THANK YOU for your awesome tutorial!! I looked through so many other pages for instructions and they went totally over my head. Your tutorial was the best and easiest to follow.
- Quick Flash Package: Radio_12.62.60.27_26.13.04.19_M - HTC 3.06.405.1
http://forum.xda-developers.com/showthread.php?t=877295&highlight=radio+thread
Trying to install the above for use with BinDroid. When Im bootloader mode and when its trying to write the radio it says it could't do it. What can I do?
I used the advanced hack toolkit, does this even do RADIO-OFF?
Thanks
mcvigo said:
- Quick Flash Package: Radio_12.62.60.27_26.13.04.19_M - HTC 3.06.405.1
http://forum.xda-developers.com/showthread.php?t=877295&highlight=radio+thread
Trying to install the above for use with BinDroid. When Im bootloader mode and when its trying to write the radio it says it could't do it. What can I do?
I used the advanced hack toolkit, does this even do RADIO-OFF?
Thanks
Click to expand...
Click to collapse
You must rename the downloaded file exactly "PD98IMG.zip". Once you do that, place on the root of your SD card (i.e. put it on the sd card). Once there, boot into bootloader and it should find the file and flash the radio. I cannot stress enough 2 things. You MUST name the file exactly "PD98IMG.zip" or it will not recognize the file. Also, if you have hide extension preference on, you may not need to add the .zip part to the end of the file. If you do add the .zip and it doesn't recognize in hboot, and you have named it exactly "PD98IMG.zip" then delete the .zip part and try again. Secondly, check the md5 number to be sure you didn't download a corrupt file. More times then not its fine but I cannot stress enough that only bad things can happen if you flash a corrupt radio. Lastly, search search search! there are numerous threads, especially in the dev section (1st thread) that details how to flash radios. Below I've added the link, while the radio that you're about to flash is on the DHD forum, the method to flash is still the same in the provided link below. If this has helped you, know where the thanks button is
FOLLOW THESE INSTRUCTIONS!
Edit: Uhm, not sure what you mean by does this do radio off? If you ran the hack kit and you have successfully installed Bindroid, you should be rooted with S-Off, enabling you to flash the radio with the above mentioned method..in bootloader it should say S-off, again though if you have flashed bindroid, you are rooted successfully I would think..
I did what you told me and its not working for some reason. What could this be? Says something like Wrong Image.
Tried flashing Radio with the toolkit too, it goes through the process but radio is the same.... So frustrating.
Stop. You can't just take any file and rename it to PD98IMG and it will magically work. There needs to be a script included to actually run it correctly. Now if you hold on for a while, I made a PD98IMG file for this radio a while ago for someone else. Let me look for it and I will post back.
The hack kit gives you S-OFF. That's all you need to flash a radio PD99IMG file. Also, please post if you have the Inspire or the DHD. Just curious.
thanks, I will wait. What I did was put the file in root, do a restart into bootloader, select hboot then started running saying wrong P98IMG.zip. Tried 3 different methods and no go. I have an inspire 4g from ATT and has the gingerbread stock radio on it. I want a new radio due to horrible battery life. I noticed that it gives me 3.9v instead of 4.2, is this a problem?
Before I post the file, please make sure you delete any other PD98IMG zip files that are on your sd card.
Yeah I know, also what method should I use with your file?
It seems it was the RADIO i was looking the problem. I put in this one,
Radio w/RCDATA: 12.59.60.26P_26.11.04.21_M
MD5 Sum: 57cccef401c372c6d421c986ee42e0fe and flashing worked perfectly. Guess Ill try this one for a while.
Boot into Hboot. You can do this by these methods. First go into your menu settings and it is usually under Power. Make sure the option for Fasboot is unchecked. After this power phone off. After phone is powered off, hold down the volume down key and keep pressing it. While still pressing volume down key press power buttonfor a second or two. You can let go of the volume button as soon as the white Hboot screen shows up. The phone will scan for files and find the PD98IMG file. It will then ask you if you want to update. Press the correct volume key to accept. DO NOT POWER OFF THE PHONE DURING THE UPDATE. It should take less than a minute. Once it is done, press power to reboot. After phone is running, make sure you delete PD98IMG file off of sd card. It will save you a headache if you ever need to go back into Hboot. Link is posted. Before you transfer to sd card, rename the file to exactly "PD98IMG", without the quotes. Just delete the underscore and the ending I added.
http://www.mediafire.com/?rysi497mkxmrh9g
---------- Post added at 10:58 PM ---------- Previous post was at 10:53 PM ----------
If you flash a radio file then make sure you flash the matching RIL file in recovery, not Hboot. In recovery options, go to mounts, mount system, then go back and select the RIL zip file to flash.
thanks alot, will try with the one you posted now. I was able to flash with another radio so it was that one specifically that was bad or w.e.
If you are going to use the ATT 421 radio you just posted, then flash the RIL file in recovery like I described. Flash the matching RIL file in recovery, not Hboot. In recovery options, go to mounts, mount system, then go back and select the RIL zip file to flash. I am posting the RIL for the radio you just listed and for the one I posted, which will end in 4.19.
I am also including a program created by ZikyHD. Install it on your phone. It is an easy way to check and see what radio and RIL you have installed.
ahhh! my apologies!! I thought he pulled the radio file from the same page I did (not the case) holy crap what a bonehead move by me! Wolf good man! I'm using BinDroid too and flashed the recommended radio recently and pulled the file from a different page...glad Wolf got you straightened out..I should have just posted the PD98IMG I had, glad wolf is on his game better then I am. Assumptions are really killing me lately!
It happens, but be careful when messing around with radio files because you can brick your phone if it messes up. To the OP, make sure you check the previous post made by me for additional information and downloads. Also let us know how it worked out. Test any new radio for at least a few days to a week. It needs to settle down. Remember, what works well for some people in their area may not work well for you, and vice versa.
Wolf_2 said:
It happens, but be careful when messing around with radio files because you can brick your phone if it messes up. To the OP, make sure you check the previous post made by me for additional information and downloads. Also let us know how it worked out. Test any new radio for at least a few days to a week. It needs to settle down. Remember, what works well for some people in their area may not work well for you, and vice versa.
Click to expand...
Click to collapse
I always take extreme caution when dealing with radios...and I cannot stress enough how important it is to delete the radio off the SD card..what nightmare that can become if you softbrick or something...not that I learned that the hard way or anything
I tried installing that app to check the RIL, doesn't phone says its not recognized.
mcvigo said:
I tried installing that app to check the RIL, doesn't phone says its not recognized.
Click to expand...
Click to collapse
well at the risk of making myself an ass again, I use terminal commands to check my ril..as far as I know it does work. If you want to take this route, download your favorite terminal app (I use terminal emulator). Open a command windown and type "su" and hit enter. First time it should prompt you to allow superuser permission. Allow it. then type: getprop "gsm.version.ril-impl" and hit enter. It will display the RIL file and hopefully the one you're expecting!
What phone do you have? That should work with most phones. It an Android program. If you are having trouble installing it then try a program like Easy Installer from the market. You can also run terminal commands on your phone or your computer to check the radio/RIL information.
In phone terminal, type the following after typing su and hitting enter:
getprop "gsm.version.ril-imp"
In command prompt, ADB, type the following after adb shell:
getprop "gsm.version.ril-impl"
Edit: Looks like I did not pay attention and refresh the screen. MMM answered the question. To the OP, what phone do you have and I am assuming the radio flash worked.
Thanks alot bro, with your file it was the only way I could this radio to install, tried alot of other methods and it would't work. Thanks alot again.
Okay, have found a lot of threads similar to this, but with key differences that are making the answers not-terribly-helpful in my particular circumstances. Not a comment on the answers, but enough that I feel the need to ask my question specifically.
I am trying to gain more control over my MyTouch 4g Slide (aka Doubleshot), obviously on T-Mobile.
It is running Android 2.3.4, and has hboot 1.45.0013. I have wiped it a few times in the process of fuxing with it, so right now I'm not worried about losing anything other than basic function (i.e., bricking it is still bad).
I have tried the zergrush exploit (it's been closed),
have managed to unlock the bootloader using the HTC unlock tool,
and have managed to flash the appropriate Clockworkmod recovery and get the blue menu to come up.
My overall goal isn't to do any major overhauls- I want to be able to allow some apps to turn my GPS on and off, clean out some bloatware, and put some new ringtones into the same folder as the stock ones. My understanding is that temporary root access is enough to do these things- go in and clean up, change some permissions on apps, then go back to being a normal user, just like with a well-managed Linux computer.
I just can't seem to get the next step to work.
My understanding is that I now somehow use Clockworkmod to install Superuser from the .zip archive. The options I get in the recovery screen are:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
install zip from sdcard
backup and restore
mounts and storage
advanced
power off
My impression is that I should be using "install zip from sdcard" to install Superuser, but when I select that, the menu just disappears, and I am left looking at the logo, with no further options. I have seen it implied that there should be choices about which zip to install- those never come up.
What am I missing? My google-fu is failing me in trying to find instructions or guides for this particular combination of limitations and progress.
EDIT TO ADD: Ah- found part of my problem... the recovery menu uses the camera button, not the power button. Still somewhat at a loss to see what's next. Installing from the SD card fails. Info in a second post.
Got the menu working, but now failing to install Superuser. I get the following output:
Mounting SYSTEM...
Deleting SYSTEM:bin/su...
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E:Error in /sdcard/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted.
Now what?
I am seeing in other places that HBOOT 1.45.0013 can't be rooted. I've been trying for about 9 hours to do this. . .no luck, even with a variety of methods.
bummer.
I'm in the same boat as the both of you. Spent the last two hours and enough tabs in my browser that my music player was skipping when switching between them, and my machine is nothing to be scoffed at!
There just doesn't seem to be enough clear information about how to root this device, and with only 7 pages of development threads, it's gonna be hard to be told to search!
In recovery you use the trackpad to navigate, and select....also, why not just flash a pre rooted stock rom? Follow the directions in this thread, it will work with any rom, not just ICS roms. I used the instructions in this thread to install Bulletproof on my Bf's phone which was an insurance replacement, so it had the same hboot that you guys have, and S-on. It worked flawlessly, I am not sure why so many people are having such a hard time, because it worked the first time perfectly for me.
http://forum.xda-developers.com/showthread.php?t=1508556
Edit: Which recovery are you using?
Woot! Oops...
Well, I managed to root my phone... and then borked it through my own overexuberance. :headdesk: Oh well, I can fix it. Important part:
I finally found out what "Status 0" means- the zip you are trying to install wasn't signed properly. I re-downloaded, no luck. But there is an option to turn off signature checking in CWM, and that worked, after some fiddling- Superuser installed and worked fine. Not sure if re-downloading ended up being relevant or not.
So, you can root this version without flashing a new ROM.
That said, I think I probably did enough weirdness to mine that I will go for a new stock ROM, so much thanks to yellowjacket for posting that thread link. Removed HTC Sense, then somehow borked Go Launcher Ex, so my phone doesn't have a home screen and I can't get to the app I used to move stuff to fix it. Of course I never found a set of instructions for making a Nandroid backup until after I messed things up... Oh, well, time to go looking for the stock ROM.
Thanks all!
If anyone has a Nandroid backup or copy of the dead-standard out-of-the-box ROM for this phone, please let me know. All I am finding is modified versions. Can't find the base that they were made from, and even the most basic version says it requires S-OFF to install. :headdesk:
Do you specifically need a nandroid backup, or would a flashable ZIP do? Pointers to the latter are available.
Flashable zip would actually be preferable, and pointers would be very much appreciated. I know they have to be out there somewhere, I'm just not finding the right search terms to locate them among all the modified versions.
Look at this post in the developer reference thread: http://forum.xda-developers.com/showpost.php?p=17384145&postcount=7
(There's lots of stuff listed there, but look for the 400 MB+ images.)
NOTE: Some ZIP tools get confused by these signed ZIPs, so they might seem corrupt. Check the MD5s to see that you got a good download. 7Zip seems to deal with them OK if you want to look inside.
I have personally flashed the 1.28 and 1.55 ZIPs without incident, but I did check the MD5s.
Well, I was not able to restore the ROMS from the links wjcarpenter linked- everything worked fine, as far as I can tell, but the phone said the "updates" were older than what was originally installed, so the installation was aborted. Not sure how to fix/handle that.
For the moment, I have one of the cleaned-up ROMs that is very similar to stock, but I would really rather it not be obvious that I rooted the phone the second you start it up (the one I found has changed the startup animations), so I will keep looking.
If it's going to be obvious that I changed the ROM, I guess I might as well start looking for the best custom ROM... any suggestions as to which is the most stable?
Firefairy said:
Well, I managed to root my phone... and then borked it through my own overexuberance. :headdesk: Oh well, I can fix it. Important part:
I finally found out what "Status 0" means- the zip you are trying to install wasn't signed properly. I re-downloaded, no luck. But there is an option to turn off signature checking in CWM, and that worked, after some fiddling- Superuser installed and worked fine. Not sure if re-downloading ended up being relevant or not.
So, you can root this version without flashing a new ROM.
That said, I think I probably did enough weirdness to mine that I will go for a new stock ROM, so much thanks to yellowjacket for posting that thread link. Removed HTC Sense, then somehow borked Go Launcher Ex, so my phone doesn't have a home screen and I can't get to the app I used to move stuff to fix it. Of course I never found a set of instructions for making a Nandroid backup until after I messed things up... Oh, well, time to go looking for the stock ROM.
Thanks all!
Click to expand...
Click to collapse
Just think of it as a big learning experience! The first time I rooted a phone, I messed it up so much I had to keep flashing back to stock and rerooting at least 3 or 4 times. Thankfully I had a phone that was virtually unbrickable. It was a good learning experience though, and I now feel comfortable rooting and flashing on several different devices.
Firefairy said:
Got the menu working, but now failing to install Superuser. I get the following output:
Mounting SYSTEM...
Deleting SYSTEM:bin/su...
Extracting files to SYSTEM...
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E:Error in /sdcard/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted.
Now what?
Click to expand...
Click to collapse
download from androidsu and either save it directly to the ROOT of your sdcard, or copy and paste to the root of your sd card. i always get that same error when i install superuser from a folder in my sd card.
Hello all,
I have a7272 Chinese phone and I accidentally deleted Google Contacts. Since I cannot reinstall it, I have to flash a new ROM.
Although the members here are brilliant, and I could find a lot of information here, I've been sitting a day and a half trying to solve my problem.
I managed to install CWMR by following this guide http://forum.xda-developers.com/archive/index.php/t-1825722.html- worked perfect.
I tried to flash this ROM http://forum.xda-developers.com/showpost.php?p=25575846&postcount=88 (I also need Hebrew in my phone), but I get error 16008 in SP Flash Tool, something about the partitions size.
Where can I find a suitable ROM for my phone?
I'm really frustrated :crying:.
Can someone help me please?
Wait isn't it just and android phone? How come you just don't find the APK file for Google Contacts?
Anyways with some research it seems that the partition tables are different in your phone or the recovery image isn't the right size. In the comments of the post Leonid says to do this "pressing the ::: (Format) * Auto Format Nand Flash -> Format whole flash except Bootloader and NVRAM Bin Region => OK
information is from here
http://bm-smartphone-reviews.blogspot.com/2011/10/mt65x3-flashing-tutorial.html
and if that doesn't work go here http://bm-smartphone-reviews.blogspot.com/2012/04/creating-rom-dump-of-your-mt65x3-device.html
Hope it helps, but try to find the APK File first.
obscuresword said:
Wait isn't it just and android phone? How come you just don't find the APK file for Google Contacts?
Anyways with some research it seems that the partition tables are different in your phone or the recovery image isn't the right size. In the comments of the post Leonid says to do this "pressing the ::: (Format) * Auto Format Nand Flash -> Format whole flash except Bootloader and NVRAM Bin Region => OK
information is from here
and if that doesn't work go here
Hope it helps, but try to find the APK File first.
Click to expand...
Click to collapse
It's not just contacts.apk, but maybe ContactsSynch and so. I still haven't found a proper way to reinstall this app, nor to flash my phone.
I saw that remark of Leonid, but I'm afraid that forcing this flash will do more harm than it is now. I didn't find any approval of this method anywhere.
MTK_Rom_Studio, for some odd reason, generating the scatter file with MT6516 in it's name, while my phone is 6573. This is strange.
PODLi said:
It's not just contacts.apk, but maybe ContactsSynch and so. I still haven't found a proper way to reinstall this app, nor to flash my phone.
I saw that remark of Leonid, but I'm afraid that forcing this flash will do more harm than it is now. I didn't find any approval of this method anywhere.
MTK_Rom_Studio, for some odd reason, generating the scatter file with MT6516 in it's name, while my phone is 6573. This is strange.
Click to expand...
Click to collapse
That sucks, but do you know the exact name of what you deleted, and did you every make like backups of your files.
PODLi said:
It's not just contacts.apk, but maybe ContactsSynch and so. I still haven't found a proper way to reinstall this app, nor to flash my phone.
I saw that remark of Leonid, but I'm afraid that forcing this flash will do more harm than it is now. I didn't find any approval of this method anywhere.
MTK_Rom_Studio, for some odd reason, generating the scatter file with MT6516 in it's name, while my phone is 6573. This is strange.
Click to expand...
Click to collapse
Did you check the posts on here? Try these suggestions:
http://forum.xda-developers.com/showthread.php?t=1409267
jhpianist said:
Did you check the posts on here? Try these suggestions:
http://forum.xda-developers.com/showthread.php?t=1409267
Click to expand...
Click to collapse
I gave up on the flashing idea. I said to myself I'll try to replace the missing apk's. Jhpianist, I saw that solution somewhere else already, and it somehow got to me that I can find the missing system apk's in one of the cooked ROMs I downloaded here.
Anyway, now I can sync my contacts and I'm able to dial or getting into my contacts, only through a third party app I had to install. Once I click on the original Contacts or Dial, I get the error "The process android.process.acore has stopped unexpectedly". No matter what I did, clearing the app cash, restore to default... nothing helped.
The guy who posted the solution, for reinstalling Contats.apk, said that one need to install the app once it's in system/app folder, in addition to changing its attributes. But I got a massage that the application wasn't installed once I tried.
How can I get rid of the stupid error? I feel I'm really close...
Thanks everyone :good:
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