hello, I'm Spanish so excuse my bad English.
I'm trying to load some rom eclair and no I finished the installation,
error busybox sys,
and all abortions.
I checked the integrity of the downloaded rom.
I have recovery: 1.6.2g. that screenshot is old
here a screenshot of the error:
The following observations were made by me :
1: Wrong Forum
2: Minimal information provided by Original Poster
To assist you i need more information such as your radio/spl and what rom it is you are trying to flash.
Since english isnt your native language, guys dont flame the guy plz.
apology for the location on forum
spl: original htc g1
rom: SuperEclair v8.2 (htcmania) and SuperEclair v3.0 (xda-developers)
Ok i would re-download the rom just to be sure no corruption has occured.
Then i would do a phone wipe.
Then i would backup my information on my sdcard and create an ext partition
Then i would flash this rom.
Daneshm90 said:
Ok i would re-download the rom just to be sure no corruption has occured.
Then i would do a phone wipe.
Then i would backup my information on my sdcard and create an ext partition
Then i would flash this rom.
Click to expand...
Click to collapse
room tested with sha1, correct code, downloaded two times
wipe: all, the five wipe.
sd: partitioned into ext3, swap, fat32 (without deleting content for:fat32 loading rom)
I found this on their thread. Try it
+ boot into recovery
+ Wipe everything (data, dalvik, ext, batt stats, rotation)
+ partition sd (96/128 swap, 512/1024/whatever you want, rest fat)
+ repair ext
+ ext2 to ext 3
+ ext 3 to ext4
+ Put rom sd (toggle MS)
+ wipe data and dalvik again
+ flash zip from sd
+ reboot system
Click to expand...
Click to collapse
Daneshm90 said:
Ok i would re-download the rom just to be sure no corruption has occured.
Then i would do a phone wipe.
Then i would backup my information on my sdcard and create an ext partition
Then i would flash this rom.
Click to expand...
Click to collapse
Daneshm90 said:
I found this on their thread. Try it
Click to expand...
Click to collapse
now I do.
question:
repairing ext. that achievement? returns since ext3 to ext2?
ext repairing fixes any file access issues u get from switching roms. Just do as it says.
Daneshm90 said:
ext repairing fixes any file access issues u get from switching roms. Just do as it says.
Click to expand...
Click to collapse
Indeed the steps!.
error screenshot:
K that error i remember seeing when i had the wrong spl. So it seems as though you need danger spl for his rom or you could use firerat's patches to make it work on stock spl
Daneshm90 said:
K that error i remember seeing when i had the wrong spl. So it seems as though you need danger spl for his rom or you could use firerat's patches to make it work on stock spl
Click to expand...
Click to collapse
I would like to retain the original spl. by the break.
Ok try this.
Flash the rom, when u get the error flash again. Dont reboot or do anything just flash again.
I just flashed on my phone with stock spl and it worked.
So its something wrong with urs.
Daneshm90 said:
Ok try this.
Flash the rom, when u get the error flash again. Dont reboot or do anything just flash again.
Click to expand...
Click to collapse
hise what I intended.
update the rom, error.
new charge, without rebooting. and error. :S
elfasito said:
hise what I intended.
update the rom, error.
new charge, without rebooting. and error. :S
Click to expand...
Click to collapse
Are you sure you are downloading it without any corruptions because it sounds like you are downloading bad files left and right??? I just re downloaded and flashed and worked fine...
You need EXT 4 for some reason but that isn't the problem when your flashing your missing files try re downloading in a new browser like Firefox or Opera
Somthing like this happened to me one time after flasing an eclair rom. I couldn't restore nandroid ("error: try running nandroid from adb" blah blah), and if i wiped and flashed it wouldn't get past splash screen. I finally flashed super d OVER an eclair rom, booted up, did sign it, went back to recovery, wiped and reflashed super d, and viola. I think my errors were like his, too.
Edit: HOWEVER! I could reflash the eclair rom and it boot up perfectly. I didn't try a different ROM. So I can't really say if another eclair would have done the same thing.
One more edit: This actually happens to me everytime i flash an eclair rom then try and go back to a donut. that's why i just stay away from them. really like them, just scared one day it wont be fixable.
XxKOLOHExX said:
Are you sure you are downloading it without any corruptions because it sounds like you are downloading bad files left and right??? I just re downloaded and flashed and worked fine...
You need EXT 4 for some reason but that isn't the problem when your flashing your missing files try re downloading in a new browser like Firefox or Opera
Click to expand...
Click to collapse
I assure you that is not corrupt.
and I tried to load 2 different rom.
and also have tested the code with sha1.
if you have time, adjuntame the rom that was downloaded.
use firefox
r3s-rt said:
Somthing like this happened to me one time after flasing an eclair rom. I couldn't restore nandroid ("error: try running nandroid from adb" blah blah), and if i wiped and flashed it wouldn't get past splash screen. I finally flashed super d OVER an eclair rom, booted up, did sign it, went back to recovery, wiped and reflashed super d, and viola. I think my errors were like his, too.
Edit: HOWEVER! I could reflash the eclair rom and it boot up perfectly. I didn't try a different ROM. So I can't really say if another eclair would have done the same thing.
One more edit: This actually happens to me everytime i flash an eclair rom then try and go back to a donut. that's why i just stay away from them. really like them, just scared one day it wont be fixable.
Click to expand...
Click to collapse
I do not understand much, (English)
you could spend the steps or explain a little better?, I would appreciate
edit:I never flash an eclair.
single donut
without error flash this rom: http://forum.xda-developers.com/showthread.php?t=633957
the others give error
Related
So after trying, and trying, and trying some more to get Faux's Roms/Kernels to run on my G2x. I know a handful of other people are having the same issues.
Due to the lack of efforts on trying to get this to work other than "Get a new device" (which I refuse to believe that its the release date of the phones that can't do it) I would like to give a bit of info about what i've done so far, and start a think tank to get those of us who want to run this great rom a future where we CAN run it!
So that being said;
When faux first released the AOSP gingerbread and I flashed it, I HAVE had it running. Something between the most recent updates, and the Clockwork recovery updates caused me to not be able to. SO
I put my phone back to complete stock 100%
Then rooted the phone.
flashed the original clockwork recovery ( orange color one ) (EXTERNAL not INTERNAL)
copied over faux AOSP latest, gapps, and ext4 kernel
wiped data
wiped cash
wiped dalvik
format /system
installed from SD faux AOSP, then flashed gapps
rebooted
(went to LG screen, then went black, then lit-up, then black again)
pulled battery (went back into recovery)
I've tried full wipe/format then flashing aosp with and without gapps, and fixed permissions, and tried it without fixing permissions. NOTHING.
Any other ideas from anyone else who can't get it to work, or maybe couldn't but then figured out how?
check the md5 checksum of the ROM
worker1 said:
check the md5 checksum of the ROM
Click to expand...
Click to collapse
you wanna give me more info about how to do that and what it is?
javolin13 said:
you wanna give me more info about how to do that and what it is?
Click to expand...
Click to collapse
Md5 checksum is a unique string if numbers that you compare to ensure that you did not download a corrupt file.
Most rom cookers will provide an md5 that you can compare against.
Google md5 checksum for freeware to generate the number.
diablos991 said:
Md5 checksum is a unique string if numbers that you compare to ensure that you did not download a corrupt file.
Most rom cookers will provide an md5 that you can compare against.
Google md5 checksum for freeware to generate the number.
Click to expand...
Click to collapse
Thanks for the reply, i'll give this a check
So after downloading the 1.2.0 file again, and comparing the MD5 checksum's are both the same:
MD5 checksum: 295e1224a85794ec354e69906432c560
Mine worked right away. I went from stock to eb froyo to cm7 then to this. I did the usual wipes prior to installing. I'm using the ext4 red text recovery.
Not sure if it matters but try cm7 then wipe then install this rom?
G2x with faux AOSP
tackleberry said:
Mine worked right away. I went from stock to eb froyo to cm7 then to this. I did the usual wipes prior to installing. I'm using the ext4 red text recovery.
Not sure if it matters but try cm7 then wipe then install this rom?
G2x with faux AOSP
Click to expand...
Click to collapse
Testing now.
After trying, now it no longer goes to the black screen. I flashed cm7, then wiped ALL again, and reflashed AOSP ginger 1.2.1, rebooted, and it is stuck now at the LG screen and does nothing ( I waited for 10 minutes at the LG screen )
did you flash the ext4 kernel after you flashed the rom? if you have ext4 partitioned and you flash a rom with an ext3 kernel it will boot hang until you install a kernel that uses ext4...
easiest way to solve this is restore the stock nandroid, which uses ext3 and start all over with whatever you want, in your case from there wipe everything, flash rom, then flash whatever ext4 kernel you want...
JHaste said:
did you flash the ext4 kernel after you flashed the rom? if you have ext4 partitioned and you flash a rom with an ext3 kernel it will boot hang until you install a kernel that uses ext4...
easiest way to solve this is restore the stock nandroid, which uses ext3 and start all over with whatever you want, in your case from there wipe everything, flash rom, then flash whatever ext4 kernel you want...
Click to expand...
Click to collapse
Latest update:
I flashed CM7 back on the phone, using red cw recovery, then tried the latest faux cm7 kernel which has ext4 and it would not boot, it hung at LG, then went to a black screen.
did a full wipe again, and didn't flash the kernel, and the phone boots fine with cm7
so whatever the issue is, it seems to be only with things faux is cooking/building ( i've flashed EVERY rom for g2x and they all work fine except faux )
javolin13 said:
Latest update:
I flashed CM7 back on the phone, using red cw recovery, then tried the latest faux cm7 kernel which has ext4 and it would not boot, it hung at LG, then went to a black screen.
did a full wipe again, and didn't flash the kernel, and the phone boots fine with cm7
so whatever the issue is, it seems to be only with things faux is cooking/building ( i've flashed EVERY rom for g2x and they all work fine except faux )
Click to expand...
Click to collapse
When you say "full wipe" are you formatting /system as well?
sryan1983 said:
When you say "full wipe" are you formatting /system as well?
Click to expand...
Click to collapse
Yes that is correct full wipe;
wipe data
wipe cash
wipe dalvik
format /system
hmmm sounds like a kernel incompatibility of some sort... i dont have everything on my phone right now to try and recreate the situation or else id help you out... i will check tomorrow and if you have not figured it out i will see what i can do...
for now, nandroid back to complete stock and start from there and see if that fixes anything...
JHaste said:
hmmm sounds like a kernel incompatibility of some sort... i dont have everything on my phone right now to try and recreate the situation or else id help you out... i will check tomorrow and if you have not figured it out i will see what i can do...
for now, nandroid back to complete stock and start from there and see if that fixes anything...
Click to expand...
Click to collapse
Thanks for your input, i've already went to 100% stock, and rooted, put cw recovery (red) on and wiped everything, then flashed faux and gapps, and it didn't work.
intriguing. I was thinking it was a hardware change that did it. Have you tried the Trinity kernel? I am guessing that something must be changed in the hardware between ones that work and ones that don't. I have run every version of this ROM since day 1 without a single issue with booting. That includes all kernels as well.
javolin13 said:
Thanks for your input, i've already went to 100% stock, and rooted, put cw recovery (red) on and wiped everything, then flashed faux and gapps, and it didn't work.
Click to expand...
Click to collapse
I am in the EXACT same boat.
I've flashed every possible rom and it loads without fail. Anything faux and it locks at the LG boot screen.
Trinity kernel loads just fine as well as all the stock ones.
Wow I'm so dumb... after you flash the rom then do a wipe and then flash the kernel of your choice...
javolin13 said:
Thanks for your input, i've already went to 100% stock, and rooted, put cw recovery (red) on and wiped everything, then flashed faux and gapps, and it didn't work.
Click to expand...
Click to collapse
You need to flash 0.1.1 ext4 kernel if you are using CW recovery *RED*. Faux's AOSP rom only comes with ext3 built-in. You have to flash ext4 kernel after flashing rom then GApps.
JHaste
"Wow I'm so dumb... after you flash the rom then do a wipe and then flash the kernel of your choice"
-flash the ROM then do a wipe, then flash the kernel???? What was the point in flashing the ROM then?
Last night, I decided to try out the Trinity kernel. I downloaded and flashed, and everything went without error. After that, I pushed a custom boot animation over ADB. The first one didn't work, and after the splash screen disappeared it was simply a black screen, but then I pushed one I downloaded from XDA and it was fine.
Now, though, I want to make a nandroid, but CWM is running into some issues. I started the ROM manager app, entered a name for the nandroid as usual, and hit OK, but when it rebooted into nandroid, it gave me an error saying "Error mounting /system" and rebooted back into CM7. That's odd, I thought, I never had any problems like that before. So I rebooted into CWM myself by holding down power+vol down and tried making a nandroid there. No luck. Then I went to mounts and storage and tried to manually mount /system. CWM gave me the error again.
I'm not really sure what's causing this. I thought it might be because now I'm using an ext4 filesystem because of Trinity (right? haha I'm new to kernels and such) and CWM might not support reading it, but if that's the case, I think I would not be the first to have this issue. Yet I searched, on that thread, on Google, on XDA general search, and didn't see anything. I also doubt it's the boot animation.
My last nandroid was yesterday. The only changes to the system I remember right now is that I flashed CM7 nightly 101, then flashed Trinity, rebooted, and flashed the boot animation mentioned. I installed apps since then but none of them had root so I doubt that's it. I would reflash CM7 to overwrite Trinity, but I read on the Trinity thread that if I did that without restoring an old CM7 kernel nandroid first, I'd be stuck in a bootloop because of ext4...?
So, what should I do? I don't want to make anything worse than it already is by tinkering with this myself, I no longer have a current nandroid, that's why I'm asking XDA. Does anyone have an idea why this might be happening? I'm sorry if a thread like this already exists or if this is in the wrong forum (if so mods please move it), this is my first time posting and my search skills could suck (although I looked in all the places I could think of)
Thanks for your help! My G2x is running CM7 nightly 101. Both the nvflashed CWM in recovery and the CWM started by the rom manager app are version 3.0.2.7.
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
ritthyhang said:
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Good, so I'm not the only one! I thought that was too odd to be true.
Here's what I've done. I reflashed cm7 nightly 101 to get my CM kernel back and rebooted. Sure enough, bootloop. Or it never got past the splash screen to the CM7 android skateboard boot animation. I went back in recovery, though, and was able to mount /system. Odd. So I flashed trinity again and tried mounting /system again and no go. So this definitely has something to do with Trinity... I restored my nandroid, reflashed 101,and that's where I am now. Tomorrow, I will make an up-to-date nandroid and do some tinkering to try to figure out what's going on. Maybe it has something to do with the boot animation, maybe not, exactly what's going on is what I am going to try to figure out if no dev shows up here.
Could you give me a few details about your case? Were you coming from cm7 too? Did you do any boot animation tinkering like me?
Sent from my LG-P999 using XDA App
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
ritthyhang said:
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Hmm. So to clarify: You were running MIUI, then you flashed eb followed by trinity. Then, eb 1.7 was released and you went to nandroid, but you couldn't mount /system, so you took the risk and upgraded anyways. The new be came with a new version of superuser, and you were able to make nandroids once again. Is this correct?
One very important question if it is. Did you flash trinity again after flashing the eb 1.7 update?
Also, could I ask what version of superuser came in this update? I am using version 2.3.6.3, which is the latest according to Superuser check for updates, but ROM Manager lists a 3.0 beta version and I'm wondering if you're using that. To check, open Superuser, go to the settings tab, and scroll all the way down. It's the second to last option for me. It's unlikely that superuser is making the difference, since it works as a part of Android and our problem is in recovery, before Android loads, but I can see how it might be possible. If you're using the 3.0 beta, I will flash to that and see if it fixes.
I will look into this some more tomorrow, specifically right now I want to know what filesystem eb's kernel recommends.
Sent from my LG-P999 using XDA App
G2X here same problem.
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
Update cwm to latest recovery 5.0.2.0 i believe.
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
I just stopped using Trinity and went back to the stock CM kernel. I don't think it's just miui, I never used that. But...
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
squish099 said:
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
YESS! Looks good. I did hear about that. Looks like it's time to give Trinity another try
Error mount/system!
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
Update your recovery, both, fake and nvflash.
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
jblah said:
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
Click to expand...
Click to collapse
Where do I find the latest clockwork mod and how do I install it? I currently have a soft bricked phone, and I can't seem to get it unbricked. I tried using the pit files with the stock rom, the dbdata stuff and everything else. What happened was the the system was in ICS, but something happened and I couldn't load into CWM 4 and the system wouldn't boot. So to fix, I used odin to install the stock rom (v2.3.3), but the stock rom came with CWM 3.0, so now I'm at 3.0 and can't mount the file system and it's not booting. I'm assuming that if I upgraded the CWM back to a newer version, I'll be able to restore the system and gain access to the file system again.
reboot problem
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Abizer98 said:
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Click to expand...
Click to collapse
I'd ask in the samung galaxy forums bud.
"my mind draws lots of blanks actually"
Solution
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
actually yes. the /system folder is corrupt and it need to be formatted. so all you need to do is format / system then it will work as it should
hope that helps
To Flash****UPDATED******
- Boot into safestrap
-Select safe system
-toggle safe system on
(It seems we have an issue wiping the safe strap /data and /cache so these additional steps are needed for now)
-quick toggle safe system off *****MUST BE A QUICK TOGGLE*****
-wipe data/factory reset
(To be safe wipe the following)
-Wipe Cache partition
-format /system
-wipe dalvik cache (Found a bug in safestrap that prevents us from wiping dalvik cache see thread)
-quick toggle safe system on *****MUST BE A QUICK TOGGLE*****
Now, flash the rom. (Selecting external Sdcard)
Safestrap works alot like a dual boot, so you can always return to your stock system by simply disabling safestrap in the safe boot menu.
http://forum.xda-developers.com/showthread.php?t=1425026
This is ics for the droid 3 by hashcode, same guy that gave us permission to unofficially port and support safestrap. It does boot and work on our phones.
This is what i know for sure right now
-Wifi works
-Most tasks and apps work
-market is broken
-calling/texting is broken, looks like its stuck on cdma?
-accelerometer is broken
What I'd like to see from here is some one willing to take over my project on this rom. I have a few of my own flash able zips complied with various tweaks to hopefully be able to make and receive calls, no success yet. I will keep trying but this is a project better suited for some one who is not so new to the linux environment. (I just got my first linux box 2 weeks ago)
Please enjoy and the thanks button is below the download link
http://forum.xda-developers.com/showthread.php?t=1425026
Proof It works! http://youtu.be/B_J3fs80dV0
**************-Edit*************************************************************************
I have decided to take on this project. I will post a more "ported" version as I progress on it, These things take time so please be patient. The information contained above should only be used as a "prof of concept" sort of thing. Anyone willing to help may do so here: http://forum.xda-developers.com/showthread.php?t=1428117
Great work !!! Thank you very much!!! Waiting the update!!
Don't we need the source code for the Atrix 2 to make this work?
I've followed all the steps in safestrap, got it working, except mounting SD (is that expected?), but after I flash the CM9 zip while in safe mode, I reboot and get stuck with a black screen. Anyone else get this working? It seems to flash rather fast which seems abnormal to me.
I agree that this Alpha 4 is stuck on CDMA. If anyone has gotten 3g to work, please let me know how you did it. I tried entering their little trick *#*#4636#*#*, rebooted, wiped cache and dalvik like they said and still nothing.
lfaber06 said:
Flash this using safestrap only.
To Flash
Boot into safestrap
Select safe system
toggle safe system on
wipe data/factory reset
(To be safe wipe the following)
Wipe Cache partition
format /system
wipe dalvik cache
Now, flash the rom. (Selecting external Sdcard)
Safestrap works alot like a dual boot, so you can always return to your stock system by simply disabling safestrap in the safe boot menu.
http://forum.xda-developers.com/showthread.php?t=1425026
This is ics for the droid 3 by hashcode, same guy that gave us permission to unofficially port and support safestrap. It does boot and work on our phones.
This is what i know for sure right now
-Wifi works
-Most areas of the phone work
-phone is broken, looks like its stuck on cdma?
What I'd like to see from here is some one willing to take over my project on this rom. I have a few of my own flash able zips complied with various tweaks to hopefully be able to make and receive calls, no success yet. I will keep trying but this is a project better suited for some one who is not so new to the linux environment. (I just got my first linux box 2 weeks ago)
Please enjoy and the thanks button is below the download link
http://forum.xda-developers.com/showthread.php?t=1425026
Click to expand...
Click to collapse
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Why can't I get this to boot? I go into safestrap, put it on safemode, wipe all the necessary things, flash the zip, reboot, and I get a black screen. If I take it off safe mode it goes back to my stock ROM successfully.
Calundle said:
Why can't I get this to boot? I go into safestrap, put it on safemode, wipe all the necessary things, flash the zip, reboot, and I get a black screen. If I take it off safe mode it goes back to my stock ROM successfully.
Click to expand...
Click to collapse
Try this. Using safestrap, make a Full backup Including webtop to be safe. then disable safe mode and factory reset, then wipe dalvik cache, then format /system, then wipe /data, enable safe mode, flash it, and let me know.
lfaber06 said:
Try this. Using safestrap, make a Full backup Including webtop to be safe. then disable safe mode and factory reset, then wipe dalvik cache, then format /system, then wipe /data, enable safe mode, flash it, and let me know.
Click to expand...
Click to collapse
Alright I'm trying it as we speak. So is the SD card currently unmountable in safestrap? If I do a backup while in safemode, won't that backup the safemode ROM, which is the CM9 one I can't get to work? I don't really understand how the safemode/no safemode works. I was under the impression that my stock ROM is under no safemode so anything I do with safemode off will effect that (meaning when I do the format and wipes you're talking about it would do that to my stock ROM), then when I turn safemode on everything I do effects the other ROM. Can you clarify for me?
Calundle said:
Alright I'm trying it as we speak. So is the SD card currently unmountable in safestrap? If I do a backup while in safemode, won't that backup the safemode ROM, which is the CM9 one I can't get to work? I don't really understand how the safemode/no safemode works. I was under the impression that my stock ROM is under no safemode so anything I do with safemode off will effect that (meaning when I do the format and wipes you're talking about it would do that to my stock ROM), then when I turn safemode on everything I do effects the other ROM. Can you clarify for me?
Click to expand...
Click to collapse
Not exactly..... safestrap knows which ROM is your stock system, and which one is the "safestrap". It calls your stock rom /systemorig or something similar, and then when in safe mode, it will mount the stock system to /systemorig and back that up as well as /system, which will be the CM9 rom, that is why you had to partition your card a certain way, to make this work right.
jimbridgman said:
Not exactly..... safestrap knows which ROM is your stock system, and which one is the "safestrap". It calls your stock rom /systemorig or something similar, and then when in safe mode, it will mount the stock system to /systemorig and back that up as well as /system, which will be the CM9 rom, that is why you had to partition your card a certain way, to make this work right.
Click to expand...
Click to collapse
Ah thanks for the explanation. So, when you backup it does a backup of both system and systemorig, both roms, how do you go about wiping one rom and not the other? Am I correct in saying if you have safemode off and do wipes/restores it will do that to your stock rom, but if it's on it will do it to the systemorig one, then backing up with it off does a backup of stock rom, and when it's on it backs up both?
Calundle said:
Ah thanks for the explanation. So, when you backup it does a backup of both system and systemorig, both roms, how do you go about wiping one rom and not the other?
Click to expand...
Click to collapse
Safestrap will only allow you to wipe your non safe data. it will not let you wipe your safe system aka "stock rom".
lfaber06 said:
Safestrap will only allow you to wipe your non safe data. it will not let you wipe your safe system aka "stock rom".
Click to expand...
Click to collapse
Awesome. Sorry for all of the questions, I'm familiar with CWM, but this is new territory for me. I really appreciate it. I'm doing the steps you provided. Am I basically doing a complete backup, complete wipe of both ROMs, then trying to install CM9 on the safe partition?
EDIT: I don't want to clutter this thread with questions about safestrap so I'll take any further questions to it's thread. Thanks again.
Calundle said:
Awesome. Sorry for all of the questions, I'm familiar with CWM, but this is new territory for me. I really appreciate it. I'm doing the steps you provided. Am I basically doing a complete backup, complete wipe of both ROMs, then trying to install CM9 on the safe partition?
Click to expand...
Click to collapse
No, you will only be making changes to the safestrap ROM, not the system ROM.... The backup will currently only be the stock ROM. now if when you enable safestrap do a backup, then disable safestrap, while in safestrap and taking a backup, you can backup the "safetrap" ROM, not the system ROM....
Now if you follow the directions in the original post, you will end up with two bootable ROMs on your phone. you really are only interested in the safestrap one right now, so doing the backup before flashing will ONLY backup the stock ROM. and you will not wipe the stock ROM either so to speak, because you can "dual" boot both ROMs by enabling and disabling the safestrap.
jimbridgman said:
No, you will only be making changes to the safestrap ROM, not the system ROM.... The backup will currently only be the stock ROM. now if when you enable safestrap do a backup, then disable safestrap, while in safestrap and taking a backup, you can backup the "safetrap" ROM, not the system ROM....
Now if you follow the directions in the original post, you will end up with two bootable ROMs on your phone. you really are only interested in the safestrap one right now, so doing the backup before flashing will ONLY backup the stock ROM. and you will not wipe the stock ROM either so to speak, because you can "dual" boot both ROMs by enabling and disabling the safestrap.
Click to expand...
Click to collapse
Ah okay okay, I think I understand how it works now. I've tried the steps in the OP and the ones faber mentioned and I'm still getting a blank black screen after reboot. How long should it take to flash the CM9 zip? It takes like 6-10 seconds for me and from my experience that's rather short for a ROM. Could the zip have gotten corrupted?
jimbridgman said:
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Click to expand...
Click to collapse
Yup just tried it, I get "Unfortunately, phone has stopped" over and over so i guess its force closing.
So, without phone or 3g capabilities, this port is basically just pretty window dressing for our Atrix 2 right?
jimbridgman said:
Have you tried replacing /system/lib/hw, /system/etc/bluetooth, /system/etc/firmware, and /system/etc/ppp, and /system/etc/wifi, with the directories from our ROM, also try replacing /system/app/TelephonyProviders.apk, with the one from our ROM?
That might actually work. That is what I have done for the one I am working on, we shall see how far that gets me..... I had read someplace, that those are very important, right after the radio image, for proper hardware operation on a phone with another ROM.
Jim
Click to expand...
Click to collapse
Has anyone tried this yet? If not I will mess with it and let you know what happens.
lfaber06 said:
Yup just tried it, I get "Unfortunately, phone has stopped" over and over so i guess its force closing.
Click to expand...
Click to collapse
duke8804 said:
Has anyone tried this yet? If not I will mess with it and let you know what happens.
Click to expand...
Click to collapse
Yep lfaber06 tried it, and if you read his reply noted in the top quote here in my reply it keeps force closing..... To bad, I am guessing because it is ICS and not GB, like out phone is currently.
jimbridgman said:
Yep lfaber06 tried it, and if you read his reply noted in the top quote here in my reply it keeps force closing..... To bad, I am guessing because it is ICS and not GB, like out phone is currently.
Click to expand...
Click to collapse
Sorry about that, I guess i overlooked that one.
In first place, i have a InsertCoin ROM, concretely "Insert Coin Sense 2.3.5 Sense 3.5 v3.4.6".
Now, when i want to install the new ICS vesion of InsertCoin, i read on thread that i need to update the firm, with this (mediafire.com/?utpdjggalstxz)
I just installed it, and now, my HTC restart again and again. I have tried to go into the bootloader by pressing VOLUP+POWER but it isnt work.
Please, i need help.
edit: i have downloaded the firm from the htc, and i have moved it with "ES explorer"... (the zip could be corrupt, but now what can i do?)
[Please forgive me if I have any gramatical error, im spanish. THK]
try taking battery out and put it back in.
mickh said:
try taking battery out and put it back in.
Click to expand...
Click to collapse
Yes, i tried that, but nothing...
How did you try to flash that PG58IMG? It has to be a Zip file and has to be flashed via Hboot. Just put it on your sd card, turn your phone off and start it again by pressing vol. down and power. Confirm, reboot to recovery, flash rom, be happy.
[I would do a fullwipe and format sd card before flashing ICS, that does magic to me. After formating sd card, toggle to usb storage and put your rom on sd card]
Your phone is probably bootlooping because the new 3.24 firmware is not compatible with the rom you have on your phone.
You need to get the new IC 4.4.3 rom onto your phone, boot into recovery and install it. Then you'll be fine.
Rootz23 said:
How did you try to flash that PG58IMG? It has to be a Zip file and has to be flashed via Hboot. Just put it on your sd card, turn your phone off and start it again by pressing vol. down and power. Confirm, reboot to recovery, flash rom, be happy.
[I would do a fullwipe and format sd card before flashing ICS, that does magic to me. After formating sd card, toggle to usb storage and put your rom on sd card]
Click to expand...
Click to collapse
Yes, that is that i have done. The only thing that i didnt know is that the firm installation delete my rom. Now i need to install a new rom.
But i would like to know something before, could i to reinstall my old rom without doing any wipe? I would like to do some backups of some apps data before wipe all. Is this possible?
TheDave86 said:
Yes, that is that i have done. The only thing that i didnt know is that the firm installation delete my rom. Now i need to install a new rom.
But i would like to know something before, could i to reinstall my old rom without doing any wipe? I would like to do some backups of some apps data before wipe all. Is this possible?
Click to expand...
Click to collapse
You have to flash the old Hboot, 1.17 or 3.12 i think. But the new ICS works only with 3.24
But you shoudn't restore anything, brings only new problems... make a full wipe and format everything before flashing, even sd card
Rootz23 said:
You have to flash the old Hboot, 1.17 or 3.12 i think. But the new ICS works only with 3.24
But you shoudn't restore anything, brings only new problems... make a full wipe and format everything before flashing, even sd card
Click to expand...
Click to collapse
Ummm, thanks for all. Where i could find the 3.12 firm? Only for try...
TheDave86 said:
Ummm, thanks for all. Where i could find the 3.12 firm? Only for try...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1459767
It's called "Noob friendly"
Rootz23 said:
http://forum.xda-developers.com/showthread.php?t=1459767
It's called "Noob friendly"
Click to expand...
Click to collapse
Thanks for all!
Since I'm too new to post in the Development section and didn't want to start a new thread, I'll ask here..
I'm running ICS 4.4.2. The latest version 4.4.3 just got released. Do I need to do a full wipe to upgrade?
and also, If I was to upgrade to 4.4.3, should I select "upgrade from zip" or "install from zip"?
1) Full wipe is not necessary. I would clear the cache, though.
2) Install from zip
I'm not sure what happened to my tablet. I really can't seem to figure it out. I was using it last night before I went to sleep, and I just closed it away (I have the keyboard dock), and packed it in the case this morning for work. When I took it out to use it at work it had already been stuck in a boot loop. I have wiped, and reinstalled 3 different roms on it since. It's still doing the same thing. Is there anything else I can do? What could have caused this?
I know that you've tried to flash several ROMs, but please check if you've done all the steps described below:
Copy ROM to /sdcard
Reboot in recovery
Wipe /system, /cache and dalvik-cache
Install ROM
Reboot and see if it works
If not, you might also want to delete /data, but make sure you backup it first (you can do that with a nandroid) and use /external_sd to store the ROM (just in case).
You can also try restoring your nandroid backup.
VibrantWind said:
You can also try restoring your nandroid backup.
Click to expand...
Click to collapse
I have tried both. When I flashed the original backup back onto the tablet I got the same result. I have completely wiped all data as far as I know. I even went a step further and formatted my sd card to ensure none of the ROM files were corrupt, then placed them back on the card. Is there even more data I can delete other than the system wipe/cache/dalvic cache?
wipe staging
wipe battery stats
ummmmm yeah those are the only 2 not listed and are not all that usefull to you
Do you have nvflash ? If so i would do a complete wipe ie format everything even recovery etc then flash a nvflash rom then restore my nandroid if i knew the integrity of it was good
Sent from my Transformer TF101 using xda premium
theres a Super wipe I use in mikes Android Revolution HD thread..
I have used this before to fix a few problems I was having..
Check "how to flash" section for it
http://forum.xda-developers.com/showthread.php?t=1245892
I had the same thing happen to me. Just boot loop out of the blue. It was sitting at home charging, came home to it boot looping.
I tried re-flashing the rom I was on (prime) and flashing other roms and nothing worked.
I had to use the super-wipe script to get it working.
fone_fanatic said:
I had the same thing happen to me. Just boot loop out of the blue. It was sitting at home charging, came home to it boot looping.
I tried re-flashing the rom I was on (prime) and flashing other roms and nothing worked.
I had to use the super-wipe script to get it working.
Click to expand...
Click to collapse
I have tried the Revolutionary Rom, and after it wipes and installs, and reboots it just says at the Asus eEE screen. What on earth could I have possibly done? Is the super wipe something that can be manually done, or does this only occur while installing the rom?
Holy Canoli, I think I may have forgot one step.....one second..."tinkering"...
Edit: update, I'm not going to tell anyone what I forgot to do after the super wipe (which is a godsend), but alas, my Transformer is functional again. Thanks guys!
MrAutomatic said:
Holy Canoli, I think I may have forgot one step.....one second..."tinkering"...
Edit: update, I'm not going to tell anyone what I forgot to do after the super wipe (which is a godsend), but alas, my Transformer is functional again. Thanks guys!
Click to expand...
Click to collapse
Let me guess... You flashed super-wipe, but didn't install any ROM after...
Don't worry, we're here to help, not judge!
AzureusPT said:
Let me guess... You flashed super-wipe, but didn't install any ROM after...
Click to expand...
Click to collapse
My bet is on that as well! haha
Not going to lie.. I've done that before.