Database Info

[Q] GT-I9000 bloatware removal and ICS

Hello everyone,
I have been searching around these forums and Google for 4 days now and i am unable to find what i am looking for. I can find a lot of stuff that is similar to my problem but none of those solutions have worked so far.
I want to try to get ICS to run on my GT-I9000 if possible, and most of all i wish to get rid of any bloatware that is on my phone. (BOL.com app and MMM amongst others)
I believe i managed to root it using Superuser and ClockworkMod.
Here is the actual problem, Upon installing a rom from SDcard i get the following error.
--Install /sdcard ...
E:Short write of /tmp/sideload/package.zip (No space left on device)
Installation aborted.
Click to expand...
Click to collapse
This error occurs AFTER i wiped data and the cache partition.
Obviously i missed something here, What did i miss?
Model : GT-I9000
Firmware: 2.3.6
Baseband: I19000XXJVT
Kernel : 2.6.35.7-I9000XWJW1-CL788890 [email protected] #2
Build : Gingerbread.XWJW1
Click to expand...
Click to collapse

[Q] [Help please] assert failed!

Hi all,
Sorry if this has been posted before, I have had a look but cant find the solution!
I have a HTC Desire HD that I have rooted using the AAHK, this has worked fine.
Next, I have searched around for a rom to use and found the Cibernodo Mod2Bravo V7.1 (English version) . . . I have put the zip file on to my SD card . . . restarted in recovery mode, wipe data/factory reset, wipe cache partition, wipe Dalvik cache, wipe battery stats, install zip from SD card, chosen the Cibernodo file and gone through the installation process . . . .
I have done all of this several times, and downloaded the zip again but I constantly get the same results:
Mounting and formatted partitions
Mounting /data
Mounting /sd-ext
Formatting /system
Mounting /system
Intalling System & Data partitions
Installing Gingerbread Keyboard
Installing Zeam Launcher
Installing ES File Manager
Installing CM/GB player
Installing 3DGallery
Removing Apps NOT selected
Installing Cibernodo Bootanimation
Configuring installed files
Setting permissions of /data
Configuring System Files
assert failed: write_raw_image("/tmp/boot.img","boot")
Yes, I am a noob, and no, I dont know much about this but I have followed everything to the letter as far as I can see ... is there something glaringly obvious that I am doing wrong?
To top it off, each time I complete this process a message pops up telling me:
Congratulations...
Cibernodo Mod2Bravo has been installed correctly on your phone
Click Finish, and restart your phone.
Thanks
Installation State: 1792
So is the 'assert failed' the issue here, and if so, how do I fix it?
Sorry to go into so much detail but I just want to see where I have gone wrong ... many thanks in advance!
[EDIT]
when my phone reboots it goes back to where I started from, i.e. the downgraded version of android from after rooting . . .

I will also try downloading and installing a previous version, V6.1z ...

Same issue with that version, so Im pulling hair out lol!

This has now gone from bad to worse ... I ran the aahk again as super user and busy box disappeared, thinking I would start from fresh again . . . there was a pause in the process and now my phone is stuck on the white HTC screen . . . anyone able to shed any light on this at all?

I've managed to speak to someone and apparenly I am not bricked and can run a ruu ... when I re-run the aahk it wont start as the error message comes up ... the phone is plugged in, the drivers are installed but I am guessing the USB debugging has been disabled . . . so does anyone know how to enable this from the aahk main screen with regards to the fact I can't boot into android?

Looks like there are lots of reasons for this... and it's a can of worms. Also, the Desire HD is one handset that my network has never sold direct, so I have seen one in eighteen months. I'm less familiar with it than I'd like... Just checking the thread and you're using the Desire HD, yes?
This thread degenerated a little and I think you've tried the chatroom too, but there are some useful pointers here: http://forum.xda-developers.com/showthread.php?t=1646178
And also here:
http://forum.xda-developers.com/showthread.php?t=1645285
Good luck. Keep us posted.

Thank you for that, I have got to the point where I don't know what to look for anymore lol! I will have a read through those ...

Data partition remounts as read-only ?

Hi Guys,
Since a couple of days I had a lot of apps crashing on my OneX (rooted, Android Revolution) and thought there was something wrong with the rom so I reflashed it but even with a clean rom crashes kept coming back, even without installing anything a couple of processes like com.htc.bgp and android.acore kept crashing/stopping.
I started looking at the logcat output and noticed that the crashes were the result of the data partition being read only and causing Sqlite to throw all kinds of exceptions when trying to write (logically)
When booting everything seems fine, the data partition is mounted RW but somewhere during operation the system remounts /data as readonly.
Usually this is because Linux detects a disk- or journaling error, so I tried running e2fsck on the partition from Clockwork Recovery and this indicated some errors so I fixed these but the problem still persists, random ro remounts with no apparent cause.
So a few questions I have :
- Does anyone have any idea why the system keeps remounting the partition ?
- How to circumvent it from remounting it as read-only ?
- Could this be a hardware failure of the internal memory ?
- Could an application error / exception cause this ?
Thanks in advance !!!
Cheers
Rob

Think your in the wrong forum this is the HTC one xl and it appears you have the international one x tegra 3
Sent from my HTC One XL using Forum Runner

Please refrain from double posting. Also, please search before creating threads. Chances are, your question has already been asked.
Thread Closed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my HTC One X, using XDA Premium.

[Q] Corrupt GPT, SBF and Fastboot have no effect

Dear all,
I have flashed my MZ605 (32GB) using EOS 3.0 for MZ601 with TWRP and that has worked quite well for some time, but last week I was fiddling with the navigation app and the tablet suddenly froze. The only way to get it back to life was doing a volume-up+power. Now the system still boots: i get to the lock screen, but as soon as I unlock (no password, just swiping to the right), I receive a shower of f/c messages and no icons apear. The settings screen still seems to work, but since the stream of f/c messages doesn't stop, it's very hard to do anything at all. I tried all the standard stuff first: Flashing EOS 3.0 using TWRP and Factory Reset: It seems to do nothing at all. Everything stays the same! When trying to delete cache, userdata, etc. Right after displaying the message "updating partition details", it complains that it is not able to access certain files in /data/media (a bunch of mp3 files)
Figuring that something must be wrong with the filesystem, I fired up the console of TWRP and did an e2fsck (e2fsck -vfcp) on partition 8,9 and 10, resulting simply in "unable to set superblock flags". I tried formatting the thing by hand but when doing mke2fs, it acts like it it's creating the fs (you see the numbers fly by), but when mounting the fs again, nothing changed at all!
About the partition table: Accessing the kernel messages (dmesg) with ADB says that the primary gpt table is corrupt and will try to use the backup table. It then merrily continues booting. However, when checking the partition table with gdisk (using ADB): it says nothing is present. Using the recovery options show that the primary table contains garbage and the backup partition table doesn't seem to contain anything. :S This contrasts with the fact that kernel still sees the partitions and that they are mountable both when booting normally as well as with TWRP
As a last resort I downloaded RSDLite 5.7 and the most recent SBF image. It flashes the whole thing without any errors, but when booting the system: nothing changed at all???
For the tl;dr people: Sorry! In a nutshell: fs seems to be frozen: mke2fs does nothing, fastboot flash does nothing and even sbf flash doesn't do anything at all. However the device still boots, albeit with a shower of f/c on unlock screen.
Any suggestions what to? I have been googling for many days now and reading this forum. Nothing has helped so far...
My next try would be to redefine the gpt partition table using gdisk and then hope that'll fix the frozen that. After that I would of course do a wipe all and flash a new ROM. The problem is, I can't find the standard partition layout details for the Xoom anywhere, nor do I have any other ideas what to do in case this does not work
If anyone has any hint or idea, please let me know. Thanks!

Nobody?
If anyone could please tell me their partition layout, like start - end - type for each partition. It'd really appreciate it!
Thanks!

No one?

Hello,
have you fixed it ?

Nope
jkd said:
Hello,
have you fixed it ?
Click to expand...
Click to collapse
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.

ioish said:
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
Click to expand...
Click to collapse
Actually I have the same problem, I have read several forums and I have not found an answer

jkd said:
Actually I have the same problem, I have read several forums and I have not found an answer
Click to expand...
Click to collapse
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?

ioish said:
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
Click to expand...
Click to collapse
my xoom caracteristic:
- Recovery: TWRP v2.6.3.0 (RunAndHide05 Edition), I can not tell if it's a bigpart or no recovery. Also I am unable to change recovery is cwm or another version of TWRP. I always find my TWRP recovery v2.6.3.0.
- ROM omni: 4.4.2-20140102-1218 + 0100-wingray-HOMEMADE (I don't know if is bigpart rom)
- kernel:2.6.39.4-ElementalX-Xoom-2.1+

[Q] Challenging Link2SD issue

Hey guys...
I would have loved to post this to the author of this CM10.1 rom i'm running but the forum won't allow me to do that yet. It's the HTC Aria/Gratia/Liberty running user WinSuk's CM10.1 homebrew mod. S-OFF and working beautifully with a bunch of other apps for many weeks now.
I've read a couple of dozen threads with the same issue and after trying maybe 10 different suggestions that solved other peoples problems, I am forced to post another topic with this boring subject. Any suggestions would be very helpful and grateful.
The questions is about Link2SD in conjunction with this ROM. Are there any limitations on using Link2SD with this rom?
I must have read 20 forum threads and I see that there are literally thousands out there about the "Mount script cannot be created"-error.
I've tried all file systems for the second partition (FAT16/FAT32/EXT2/EXT3/EXT4) and all give this error. The only difference is that when the file system is EXT3 I get a different error. Instead of being just plain "Mount script cannot be created" I get instead "Mount script cannot be created. Mount: Invalid argument".
Either Ext3 is showing some progress or it's the only file system not supported.
The phone is obviously S-OFF so nand is unlocked. I'm very close to trying the CronMod script instead but I really would like to try Link2SD before falling back on something potentially less popular.
Thanks for reading and helping out... /s