Hi,
I'm trying for 2 complete days to install android 2.2 on my polaris now but I cant get it working.
Since i'm a complete newby probably it will be something very simple (i hope) but i'm getting verry frustrated at the moment haha.
I'm stepping over from WM6.1
What i have done:
I have a HTC Polaris POLA100
I have a 4gb Micro sd HC class 4
I'm trying to install Incubus26Jc's Super FroYo RLS16 All Languages trough NAND
I have HARD SPL V2 on the phone
I have done all this steps: sourceforge. net/apps/ trac/androidhtc/wiki/HowToInstallWithAtoolsNand
When i boot my phone now i get:
linux logo in top: lots of text lines
then I get:
Mount: mounting /dev/block/mmcblk0p1 on/sdcard failed: invalid argument
sh: 0: unknown operand
found boot parameter for system
system on nand partition
found boot parameter for data
data on nand partition
failed
install module for this kernel
On the sd-card I have
POLAIMG.NBH
andboot
*androidupdate.TGZ
*androidinstall.TGZ
*install-seq.sh
I've tried the NAND option on this page also: http://forum.xda-developers.com/showthread.php?t=921053
But i get the massage:
failed
install module for this kernel
hooliead said:
I've tried the NAND option on this page also: http://forum.xda-developers.com/showthread.php?t=921053
But i get the massage:
failed
install module for this kernel
Click to expand...
Click to collapse
Download the modules form here:
http://sourceforge.net/projects/androidhtc/files/modules/
Rename the tgz file to "androidupdate.tgz" ,than put it in /sdcard/andboot/.install it when you enter the installer menu.Problem will be solved.
Same problems...
When i restart te phone with a soft reset and wait i will get the massage:
Failed
Install module for this kernel
When i manual try to install by keep pressing up the volume button after soft reset i get the massage
there is no such file on sdcard androidupdate.tar
I have checked several times there is a androidupdate.tar and a androidupdate.TGZ (same for androidinstall)
I also tried with only the .TGZ file and only the .TAR file
reformat the sd card.
done it several time... no succes
A little background, I am trying to flash a Honeycomb rom to my Archos 7HTv2. This is a custom rom that I put together. I know that Honeycomb requires much more power than my Archos can give me. I know that it would probably be unusable, but I was curious, and it brought up a problem.
The system.img for the HC rom is ~112mbs, the total update.img is ~123mbs
The system.img for the stock rom is ~51mbs the total update.img is ~54mbs
I first tried to flash it and got a "not enough space" error when flashing the system. I assumed that the stock rom barely fit in the system partition, so I went looking for how to make it bigger.
Flashing on the Archos is by putting an update.img in the SDcard, or by using the "BatchUpgrade" utility from the computer, which copies it to some temp on the device. Then the recovery takes over and installs the rom.
Code:
Writing KERNEL:...
Checking KERNEL:...
Writing BOOT:...
Checking BOOT:...
Writing SYSTEM:...
E:Write failed(No space left on device)
E:Failure at line 16:
write_image PACKAGE:system SYSTEM:
Update failed, please reboot and update again!
Line 16 refers to the update-script file which has the list of Writing & Checking.
When I flash the rom from the computer using "BatchUpgrade" it fails before it can attempt unpacking. It just tells me "FAILURE" and no specifics as to why. Because the img never begins unpacking makes me believe it might be the temp area is not big enough for the .img and the extracted components.
I found this mtd information in the HWDEF file (part of update.img)
Code:
#Format: part_name offset:size
parameter 0x00000000:0x00002000:fh
misc 0x00002000:0x00002000:f
kernel 0x00004000:0x00004000:f
boot 0x00008000:0x00002000:f
recovery 0x0000A000:0x00004000:f
system 0x0000E000:0x00030000:f
backup 0x0003E000:0x0003A000:
cache 0x00078000:0x0003A000:
userdata 0x000B2000:0x00100000:
user 0x001B2000:0xFFFFFFFF:
END
I changed the system and backup partitions to be bigger (the above is stock) but nothing happened. I then found the PARAMETER file which had a similar string of mtd definitions, I updated them as above. Still no luck.
Anyone have any ideas?
Thanks
Do you had any luck?
Guys,
I have had an device impacted by TWRP 2.7.X build that created the problem of not being able to mount /data and sometimes(/cache & /system) partitions.
I have managed to make it run a ROM by using information from
http://forum.xda-developers.com/showthread.php?t=1869673 & http://forum.xda-developers.com/showthread.php?t=1843062.
the problem is that the mounts are not remaining permanent and my modified boot.img does not boot the devices. So i have to mount the partition manually during the boot process over a shell and then the device boots.
Need help from experts to do a kernel which can mount sdext partition and an updated recovery image which also mounts the sdext partition as /data so that roms can be flashed easily.
I will try and do a writeup of how i made it run.
Resurrecting Pyramid
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Jack Daniel's said:
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
rmann said:
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
Click to expand...
Click to collapse
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Jack Daniel's said:
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Which recovery are you using... I have re-tested the script and it works ok for me.
rmann said:
Which recovery are you using... I have re-tested the script and it works ok for me.
Click to expand...
Click to collapse
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
antiziclon said:
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
Click to expand...
Click to collapse
did you try to update the recovery to the latest version?
rzr86 said:
did you try to update the recovery to the latest version?
Click to expand...
Click to collapse
Just tested with v1.0.0.6 RC3 build 8, same error
antiziclon said:
Just tested with v1.0.0.6 RC3 build 8, same error
Click to expand...
Click to collapse
redownload the zip file
after that i am out of ideas
ok, I found out the issue.
The issue is on the encoding of the "updater-script" file.
It needs to be in Unix encoding. If you use Windows (as I do) when unzipping the Zip file or when creating a new file with a text editor, the encoding gets changed and it is not Unix encoding.
To solve it:
- Open the file in Notepad++.
- Go to Edit --> EOL Conversion --> UNIX
It will change the enf of lines to comply with Unix encoding. Then add the file to the Rom zip file and you are ready to go
Enjoy!
Successful Pyramid rescue
I have a sensation with corrupted emmc caused by TWRP, /data cannot be mounted.
I followed your instructions and addition re script encoding and successfully installed Revelation to partitioned sdcard.
Phone boots and works.
That's great, thanks.
I have some questions:
1. Is 512 MB sufficient for swap partition? What would be the optimal size?
2. My sensation is s-on unlocked, and I had to flash boot via fastboot after install, 4ext did not flash it despite smartflash option turned on. Is that normal?
2. Superuser does not seem to work, I have no root. I checked with root validator and I have su binary, superuser and busybox, but no root is given to apps that require it, su binary update fails, and there are no logs left in superuser to check (or I simply don't know where to look).
Thank you.
rmann said:
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Click to expand...
Click to collapse
Ok try to make that in unix
Extreme lag
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Extreme unuseful slow
With my sensation XE i also followed all steps. Revelation 1.0.3 is booting, but not to use at all, it stucks in every step, cant even receive a call, can't go to any menu. Pls someone help me out of here. Do I need a swap partition? Or are the partitions to small? sd-ext has 1024Mib; sd-ext2 1537Mib.
danilandroid said:
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Click to expand...
Click to collapse
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
probably you need a sdcard with high speed of w/r but i am not sure
Lag
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
danilandroid said:
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
Click to expand...
Click to collapse
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
So, I bought a class 10 card, revelation is running now!! At first start it was still very slowly an got stuck allover. But at second start it is running now! Thanks for that perfect thread!!:good:
I wonderd why vipers wont start the same way? When I try to boot it , 4ext recovery is starting rightaway with little delay!
Hi, when I got the same problem with /data, /cache and /system not mounting. I followed the steps from #2 post http://forum.xda-developers.com/showpost.php?p=55157092&postcount=2
and when I try to install from zip it says that the zip isn't meant to be flashed in recovery and it aborts the installation. First I tried renaming the new_boot.img you provided to boot.img but it's the same result.
Hello guys,
Today I wanted to update my Honor 8 (FDR-L09) because it was showing me, that there is a new update ready to install (FRD-L09C432B405) and I was on a very old firmware (something from mid 2017). So it was time for me to update.
I downloaded the latest update (FRD-L09C432B405) and tried to wipe the cache, dalvik, and Data, but for some reason it "couldn't mount /data" and the wipe failed.
After an advanced wipe it worked and I tried to flash the stock image (the update which was shown to me (FRD-L09C432B405) with TWRP (3.1.1.1.)).
Now my hassle starts:
1. The Rom couldn't get flashed because of "Error: 7" --> I fixed it with the common "Error 7 fix --> editing the update-script and removing the assert line. (And yes, I'm 100% sure that it was the right ROM.
2. Now TWRP seemingly starts to flash the rom but inbetween the lines there is "mountencrypt: failed to mount /data: no such file or directory and it ends with "unknown command [[]" and it takes just two seconds, so the flash obviously isn't succsessfull.
I tried the "failed to mount /data" fix, where I change the data system to ext3 and then back to f2fs and change it back, but it won't work.
In my frustration I did another pretty bad thing and made another advanced wipe and wiped the system too, so now I don't have an OS on my system.
Maybe it's also important to note that there was a window showing up for a very short amount of time, with something like "encryption/encrypted" showed up.
What should I do now? Is there a way to fix the "/data couldn't be mounted" problem? Or am I missing a vital step in flashing the stock rom?
Thanks for your kind help!
You can not flash an update with twrp unless you use hurupdater. You essentially bricked your phone. Look for hurupdater here on xda and follow the instructions and you'll be fine