No matter what I do, I cannot get a single thing to flash anymore with CWM. I'm on the dark side rom, unlocked bootloader & rooted, 4.5.91, and using romracers 4.0.1.5 cwm recovery. I even tried tenfars and the one rom manager gives me, but the problem persisted. Is there any fix for this because it is getting VERY frustrating!
The only fix available would be to figure out what you've done. The CWM versions all work fine and don't require a fix. It's something at your end and with the information you've given, there's not much to go on.
It must corrupt the files when I transfer them from the computer to the phone. I've downloaded straight from the source and MANY other sources of the exact same rom/kernal/ect... and it all ends up not working. Is it better to download on the phone? Oh, missed one detail but I don't think it matters, I'm using a mac and when I download a file it auto unzipps, then I just re-compress it and throw it on the phone. Would that affect anything?
change ur cable... try different machine...
Same problem
I've encountered the same problem! I flashed darkside on my rooted AT&T Atrix, (unlocked bootlader, rooted). My friend borrowed my phone and saw the AT&T system update and installed it. the phone reboots and I couldn't move past that, then i got the little green android dude with the /!\ sign behind him. Tried factory resetting, restoring from backup, and even flashing over Gingerbread, but nothing worked! If you have found a fix, an answer would really be appreciated!
dcben09 said:
I've encountered the same problem! I flashed darkside on my rooted AT&T Atrix, (unlocked bootlader, rooted). My friend borrowed my phone and saw the AT&T system update and installed it. the phone reboots and I couldn't move past that, then i got the little green android dude with the /!\ sign behind him. Tried factory resetting, restoring from backup, and even flashing over Gingerbread, but nothing worked! If you have found a fix, an answer would really be appreciated!
Click to expand...
Click to collapse
Not the same problem! You tried to OTA on an unlocked bootloader.
CaelanT said:
Not the same problem! You tried to OTA on an unlocked bootloader.
Click to expand...
Click to collapse
Would you happen to know how I might go about fixing it?
Gfrt94yn said:
Oh, missed one detail but I don't think it matters, I'm using a mac and when I download a file it auto unzipps, then I just re-compress it and throw it on the phone. Would that affect anything?
Click to expand...
Click to collapse
That's probably your problem right there. Use a Windows machine to download to, put the zip file on your phone from Windows, do a FULL fastboot wipe, and try flashing the ROM. (Or download right to your phone).
Sorry, I don't use a mac, so can't help there. I can tell you that just zipping files without the correct compression settings will cause the flash to fail.
e.g. If using 7-Zip you need to set Archive format to "zip" and Compression level to "store" when creating flashable zip files or they won't work.
In any event, do a FULL fastboot wipe before flashing:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
There are a couple of scripts in the forums which are almost completely automated to do this.
Actually I figured this out forever ago (moved on to new phone), but I'll still help. Anyway download the file DIRECTLY to your phone, no computers!! Then place it on root of sd card (for convenience, you don't have to) and flash. Problem solved! if that doesn't work, the file is most likely corrupt or the way your phone downloaded it is outta wack. Hope this helped
Sent from my SAMSUNG-SGH-I727 using XDA App
Gfrt94yn said:
Actually I figured this out forever ago (moved on to new phone), but I'll still help. Anyway download the file DIRECTLY to your phone, no computers!! Then place it on root of sd card (for convenience, you don't have to) and flash. Problem solved! if that doesn't work, the file is most likely corrupt or the way your phone downloaded it is outta wack. Hope this helped
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
Please see my post right before your post. Your problem was downloading to a MAC and the files being unzipped. Then when you zipped them back up it was not done correctly. Computers are not the problem!
Related
so, my HTC Evo 3D is bricked, I think. I was bored last night at work and I was moving some apps to my sd card. One of the apps I moved was Plume for Twitter. When I launched Plume, it told me I had to restart my phone for the notification settings to be applied. So I did. It booted up fine but when I turned my screen off when I was done with work, the screen wouldn't unlock. There was just the notification bar and my wallpaper. I couldn't hit any buttons, or slide the notification bar down. I tried calling my phone from work but it just said missed call from work. It boots into bootloader and adb is working. I am downloading PG86IMG.zip now and I'm going to try to flash that unless someone else has a better idea what to do. Can someone please help?
Thanks in advance!
chupacabra_evo said:
so, my HTC Evo 3D is bricked, I think. I was bored last night at work and I was moving some apps to my sd card. One of the apps I moved was Plume for Twitter. When I launched Plume, it told me I had to restart my phone for the notification settings to be applied. So I did. It booted up fine but when I turned my screen off when I was done with work, the screen wouldn't unlock. There was just the notification bar and my wallpaper. I couldn't hit any buttons, or slide the notification bar down. I tried calling my phone from work but it just said missed call from work. It boots into bootloader and adb is working. I am downloading PG86IMG.zip now and I'm going to try to flash that unless someone else has a better idea what to do. Can someone please help?
Thanks in advance!
Click to expand...
Click to collapse
Restore from a backup. If you don't have one just gun the PG zip and it should work fine. Just note you will lose everything.
iTzLOLtrain said:
Restore from a backup. If you don't have one just gun the PG zip and it should work fine. Just note you will lose everything.
Click to expand...
Click to collapse
I tried restoring from a backup. I tried factory resetting also. And now its just bringing me to the white HTC screen and not getting any farther. I'm on HBOOT 1.5 and I've been using HTCDumLock to flash roms. Should I just do it the old fashioned way and flash the PG.zip using fastboot?
Have you tried flashing the rom then reboot to recovery via fastboot then flash the kernel. Or flashing the boot partition???
#Root-Hack_Mod*Always\
laie1472 said:
Have you tried flashing the rom then reboot to recovery via fastboot then flash the kernel. Or flashing the boot partition???
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I tried that. But now when I try to copy over the PG.zip file it says I don't have enough space on my SD card so I deleted some things that I don't need and its still saying it. I tried flashing the rom I had before it, and all it says is unable to unzip.
Back up your sd. The format it and restore the default partitions. Then try it.
#Root-Hack_Mod*Always\
laie1472 said:
Back up your sd. The format it and restore the default partitions. Then try it.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I will try that when I get home from work! Thank you..I'll let you know if it works!
No problem you can pm me as well or post back. Hopefully it works.
#Root-Hack_Mod*Always\
Flash the Boot.img
you might have a "softbrick" on your hands.. An easy way to fix it is to extract the Boot.img from your current custom rom and then flash it using fastboot like so:
Be sure to cd/ to the location of the boot.img
Fastboot flash boot boot.img
then Fastboot boot boot.img to restart
Somewhere along the lines you might have accidentaly tried to boot the wrong rom on the wrong boot.img.
Sorry if this doesn't help...
laie1472 said:
No problem you can pm me as well or post back. Hopefully it works.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I tried that..no luck. I'm currently using my friends old phone, the Samsung Moment...which is sprints first crack at an android phone. Its a far cry from my EVO 3D, but I will have to live with it until I can figure what I will do next. Thanks for trying to help, I appreciate it!
kiewee3 said:
you might have a "softbrick" on your hands.. An easy way to fix it is to extract the Boot.img from your current custom rom and then flash it using fastboot like so:
Be sure to cd/ to the location of the boot.img
Fastboot flash boot boot.img
then Fastboot boot boot.img to restart
Somewhere along the lines you might have accidentaly tried to boot the wrong rom on the wrong boot.img.
Sorry if this doesn't help...
Click to expand...
Click to collapse
yeah a buddy of mine said I soft bricked it. I'm not quite sure what that means but he's going to look at it and hope to get it back in working order so I don't have to use this awful phone (samsung moment)
Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
ten6 said:
Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
Click to expand...
Click to collapse
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Dark Nightmare said:
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Click to expand...
Click to collapse
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
ten6 said:
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
Click to expand...
Click to collapse
Don't download that one, it has issues, hold up, I'll give you a link to the most recent file.
Here, get this: http://d-h.st/3VD
Download speed should be faster as well. rename it PH85IMG and place it on your sd card after you relock your bootloader, then boot into bootloader, it's gonna detect the file and ask you if you wanna update, follow the on screen instructions to update, voila! Follow the basics to install the new energy rom.
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
It is useful, I fully agree with you, it's like we come here to answer the same questions over and over, but I'm just trying to be nice, cause I usually just say, read the amaze bible, but then they go and do something even more noobish, so to avoid the tear jerks I just give the basic info, though I'm fading away slowly.
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
I came across this issue. As earlier posts said, install the new ICS update. The partitions were messed up and the ruu will clean it up.
ten6 said:
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
Click to expand...
Click to collapse
Lol, never pointed fingers buddy, so calm down.
Maybe I should create a new topic but my issue is similar to this one except for the fact that I read quite a lot and tried quite a few things.
My situation is that I made a backup with cwm only booted not flashed so I have the 100% stock backed up, after this I flashed cwm and tried to install the Energy rom based on ics and that was my mistake as I used to be on a Nexus device I didn't have to worry about this.
So I got stuck on a bootloop and tried factory reset/wiping everything, tried to reinstall a stock ROM (t-mobile one as I only found a .exe for the videotron one and I did not feel like exploring the exe as I am a Linux user) by relocking bootloader and using the HTC method, tried to install manually the stock Kernel with Energy ROM using adb and fastboot commands, tried to restore my backup but nothing seems to work, I'm still bootlooping.
Is-it possible to s-off without a regular adb access (only the cwm adb access)? And would s-off allow me to flash anything as I wish? Is there a way to have any ROM working on my device? (i know the answer is yes to the last one, at least )
Thanks!
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
johnride said:
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
Click to expand...
Click to collapse
Okay okay, calm down, there's currently only one method of going about restoring your device since you're s-on and no you cannot s-off with just cwm adb, I think JB s-off method is only an exe file, never saw linux files anywhere on his site. Anyways, you have to use the GB exe for videotron and restore to stock via it then update to ics to use the most recent energy rom, BUT if you just want a working device, this is just an idea, though it should work fine, you can flash a custom recovery and flash the GB version of energy rom, you should be able to restore your backup as well, but you said you can't, which is odd, it may be because of the kernel not being flashable as since CWM cannot flash kernels while s-on, in which case I'd advise you to get 4EXT recovery and then try restoring your back once again, it should work fine since 4EXT can flash kernels while S-ON.
My two cents.
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
johnride said:
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
Click to expand...
Click to collapse
I got lost halfway through that post, after flashing a rom, if the kernel isn't flashed (reboots and does it automatically), then flash the kernel manually, should boot fine, does anyone ever really read anymore? This very issue both s-on and s-off has been answered more times today than I can count. If you read the details on JB's site, you'd see and know all you need to.
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
johnride said:
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
Click to expand...
Click to collapse
How did you go about flashing the kernel?
Sent from my SGH-T679 using xda app-developers app
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
johnride said:
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
Click to expand...
Click to collapse
Okay here's a few tips, cwm cannot flash kernels with son devices, get 4ext recovery for that. Second thing, reflash the from after doing a super wipe, if 4ext doesnt reboot and flash the kernel, do it manually, ill assume you know how to use ad, if not check my Bible tutorial on it, use the boot command for flashing boot images, take the boot file from the zip file, place it in the folder where your adb files are and flash it to your device while its in fastboot mode.
Sent from my SGH-T679 using xda app-developers app
Well, I think I have done all you mention above, the only thing i'm not sure to understand is what you mean by "super wipe" I found some executables about it but I guess it can't do much more than the flash all partitions (except external sdcard) in 4ext recovery wich I finally managed to install properly.
So, I made that global formatting thing, I tried to install an ICS based ROM and 4ext rebooted to install kernel, same bootloop. Tried to install manually the kernel that came with this rom via the classic fastboot flash boot boot.img. Same bootloop. Tried to put the modules manually via the recovery adb access (performing a mount -a in adb shell to have everything present in fstab mounted) and flashing this stock kernel with no more success.
Achieved the same operations with a GB based ROM (this one: http://forum.xda-developers.com/showthread.php?t=1535173) with both the faux and the stock kernel without any more success.
Did I miss something? Am I so dumb? Do you have any other rom to suggest that have higher chances to succeed?
Do you think trying to restore my sotck nandroid with 4ext has more chances to succeed?
Thanks, again and always!
I was trying to disable FSYNC using the method described by poofyhairguy. I did it via terminal, in su. I mounted /system in rw mode, I copied libsqlite.so and libsqlite_jni.so into backup copies, and overwritten them with copied provided by poofyhairguy. Alas, I forgot to chmod, so they were left with whatever permission they came from. I rebooted the tablet and now it is permanently in the starting screen with big ASUS letters across. I cannot even turn it off!
Help, please, what do I do? I don't really know much about Android, so please use simple explanation.
Just to add some details. My Prime is stock, rooted but not unlocked.
I also don't seem to be able to reach it from ADB. I did install ADB and drivers on my PC a while ago, when I rooted it. I'm trying this now:
- connect Prime to PC
- reboot with volume down, select a USB symbol
- PC says "installing drivers" and "ready"
- in adb shell, when I try "adb devices" it shows an empty list
Any help?
OK, here is more information and more questions. I can start the tablet in fastboot mode (USB symbol on screen). After reinstalling ASUS suite and Google SDK I connected the tablet to my Windows 7 laptop. It searched for drivers for a while, installed and said "ready".
"adb devices" returns and empty list. "fastboot devices" returns one entry, a long hexadecimal number and the word "fastboot". Does it mean that I can see my tablet via fastboot but not adb? Does adb work when tablet is in fastboot mode at all?
Does it mean that the only option is to reflash ASUS firmware?
@Felisek Did you tried to wipe aka hard reset the device via bootloader? or you have important files which you don't want to reset? or you don't see wipe option in bootloader?
Sorry, I'm not much expert in android underhood that I can help you more but looking at your problem doesn't look like you have bricked your device so keep hopes. Someone having more knownledge might come and help you.
btw; AFAIK, adb and fastboot are different kinds. You see fastboot.exe in the sdk package? yes that links with fastboot option on the devices. But I might be wrong as well.
May be you try entering into fastboot and use fastboot.exe, then go to the path where you modified the files. Either replace them to original ones or chmod. But I don't know whether this gonna work.
CRACING said:
Did you tried to wipe aka hard reset the device via bootloader? or you have important files which you don't want to reset? or you don't see wipe option in bootloader?
Click to expand...
Click to collapse
There is a wipe option, but I don't think it is going to work. As far as a know (correct me if I'm wrong), factory wipe does not change /system folder. In particular, there are two "wrong" files in /system/lib that cause the problem, so wiping everything else is not going to help. I need to change/restore these files.
I think I can reflash the stock ROM using recovery, but I'd like to try and fix it without wiping everything first. I don't have anything unmissable on the tablet, but reinstalling everything and rooting is a bit of a hassle.
Felisek said:
There is a wipe option, but I don't think it is going to work. As far as a know (correct me if I'm wrong), factory wipe does not change /system folder. In particular, there are two "wrong" files in /system/lib that cause the problem, so wiping everything else is not going to help. I need to change/restore these files.
Click to expand...
Click to collapse
Hmm may be you are right so reflashing whole ROM is required.
Felisek said:
I think I can reflash the stock ROM using recovery, but I'd like to try and fix it without wiping everything first. I don't have anything unmissable on the tablet, but reinstalling everything and rooting is a bit of a hassle.
Click to expand...
Click to collapse
Recovery? but you said you haven't unlocked or you mean stock recovery?
Yeah, upon reflashing, you will lose root but hey, you can root again using the new method (motorola's) and its not at all risky as unlocking. :good:
May be you can wait for sometime, I hope someone comes up guiding you how to replace/modify the system files using adb or fastboot.
CRACING said:
Recovery? but you said you haven't unlocked or you mean stock recovery?
Click to expand...
Click to collapse
There is a "RCK" option on startup, I thought that was recovery. But, yes, I mean stock recovery, if this is how it is called. Download stock firmware, put it on a microSD, rename it to EP201_SDUPDATE.ZIP, reboot and apparently it installs automatically.
When I was making my guide I tried using the old ICS libsqlite.so and libsqlite_jni.so files and softbricked in the same mannor. The only way I found to fix it was to flash the stock ROM as it says to do in my guide.
Note that unless you purposefully wipe your data in the recovery your data should remain intact from my experiance with it. The way the stock Asus recovery seems to do it is to blow /system away (so yes you must re-root, etc).
Good news. I unbricked my Prime by reflashing the stock ROM, using the method described by poofyhairguy. All my apps and settings survived. I only lost root, so even rootkeeper cannot recover it. Not too bad, after all.
Sent from my Transformer Prime TF201 using Tapatalk HD
Hi guys,
I've been using my Sola for over a year now and I like the phone, i got the CM9 build from freeXperia on it (FXP 210 CM 9 PEPPER) with cwm on it and loved it.
Two weeks ago trouble began when the phone was very unreliable, it rebooted several times a day, sometimes I noticed that the phone got very warm when rebooting.
I found out that there was no diskspace left, so I deleted some of the playlists on Spotify that I downloaded and that gave me back about 2 gb of internal room.
Since yesterday some processes where quitting and this happened a couple of times (it was the google media process), this morning after being on the adapter for the night the problem was still there. So I rebooted the phone (normal reboot) and then the trouble really kicked in.
When I boot now I see a message stating "Android is being updated, starting apps" then I see my normal lockscreen and the errors start rollling in.
The only errors I can see are the "android.phone process stopped working" and "NFC service stopped". When I press close on those they keep coming back, so fast I cant't even get past my lockscreen anymore.
On the phone is some very critical data to me, I have to restore that data (its in a encrypted app database). As long as I can save that data and restore it to use when the android/app is restored I'm fine.
Can someone give me advise on how to continue?
**bump, I really need my phone
VeldMuijz said:
**bump, I really need my phone
Click to expand...
Click to collapse
Bump! Getting desperate here...
VeldMuijz said:
Bump! Getting desperate here...
Click to expand...
Click to collapse
Where is that data located? If it's on internal memory in it's own directory it will remain intact if you repair/flash firmware.
EDIT: some other thoughts, try to remove the SIM or switch to airplain mode.
I'm not 100% percent sure where it is located, It's on the internal memory but I'm not sure if where it is exactly. It's a database of an app.
Won't I lose all my files on reflash? Reflash can be done with fastboot right? And I should reflash the firmware (kernel?)? Not the rom itself?
Already tried rebooting with SIM and sdcard out, no luck though.
No luck on connecting to ADB, I tried but USB debugging is turned off and my drivers seem to let me down... I can get connect to fastboot
Other ideas?
VeldMuijz said:
I'm not 100% percent sure where it is located, It's on the internal memory but I'm not sure if where it is exactly. It's a database of an app.
Won't I lose all my files on reflash? Reflash can be done with fastboot right? And I should reflash the firmware (kernel?)? Not the rom itself?
Already tried rebooting with SIM and sdcard out, no luck though.
No luck on connecting to ADB, I tried but USB debugging is turned off and my drivers seem to let me down... I can get connect to fastboot
Other ideas?
Click to expand...
Click to collapse
Too bad USB debugging is off.
If database is on device memory than it will be lost if you wipe data on flash. If you don't wipe data you may still have those errors, but you can take your chances and try without wiping data.
Yes with flashtool, do you have the FTF file for the firmware you are currently using?
Is it tooted and have CWM on it?
I don't have the FTF anymore, but I know where to find it.
Luckily I have CWM on it.
Do I have to reflash with the zip or just run the update?
VeldMuijz said:
I don't have the FTF anymore, but I know where to find it.
Luckily I have CWM on it.
Do I have to reflash with the zip or just run the update?
Click to expand...
Click to collapse
I think best is to make your own FTF.
Start repair with PC Companion, and when it finish downloading the files and ask to shut down the phone, stop and create the FTF as explained here.
The FTF can only be flashed with flashtool.
I don't mean to sound rude but why do I want my own FTF?
Do you mean a FTF from the OEM firmware, they can be downloaded from XDA as well.
Or do you mean creating an FTF from the files that are now on my phone?
VeldMuijz said:
I don't mean to sound rude but why do I want my own FTF?
Do you mean a FTF from the OEM firmware, they can be downloaded from XDA as well.
Or do you mean creating an FTF from the files that are now on my phone?
Click to expand...
Click to collapse
I've seen a few people hat flashing firmware they download didn't work well for them but flashing with SUS or PCC did.
I'm not twisting your hand, if you rather use FTF you can download somewehere and it works then do that.
Ok so i tried to flash the kernel, the flashing went well but the error persists.
I think it's time to conclude that my data is gone..
It gave me some headaches and I sweared a lot but i got it working again.
I've flashed the boot.img, didn't resolve the issue.
I've updated the same rom over my old rom, didn't solve the issue.
I wiped cache only (to try and see if it would work) and this worked.
So it might have been a cache problem after all.
The updating android thingy was shown again only this time it said it had to update 100+ apps, and it did. After that I could use my phone again.
First things first, lets make a backup .
Thanks ChickeD (i've thanked you on XDA for your help)
This can be marked as [RESOLVED]
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
riekkir said:
Hello XDA members,
I was hoping somebody would help me out, I'm fairly new when it comes to installing custom roms so I require your patience. I don't know how to install a custom rom onto my Bell Atrix HD MB886, everytime I try it says abortion failed, what can I do to fix this. I have wiped data and all that probably 5 times in the past week alone. I would like to know how to successfully install roms without errors. Both the times that I have done this I had my bootloader unlocked, and I had clockword recovery mod latest version 6.0.4.4. I bought an SD card today to help install the roms because otherwise I can't do it from my internal storage. I really hope somebody can help me out.
Regards,
Roger
Click to expand...
Click to collapse
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
es0tericcha0s said:
Hi there. A failed abortion certainly seems like an issue... I guess I am not totally clear on the status here. You say that you had CWM. Do you still have it? Bootloader is still unlocked? What rom are you trying to install? Are you certain it's for the Bell version and not like the AT&T one? What is the exact error message?
Click to expand...
Click to collapse
No I don't have it atm as I just wiped the data/cache last night but will I already have CWM, I just need to unlock the bootloader and try again...I'm trying to install this one:
Android 4.4.2 KitKat Mokee Rom, and it says the version is a nightly. Yes I'm positive it's the Bell Version as I purchased it at a Bell Store and my carrier is Bell. The error message is "Installation Aborted." It begins installing, and then halfway through I get that error message. How do I fix this?
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960
es0tericcha0s said:
I figured you knew what phone you had. I was wondering if you had a rom built for the Bell version vs an ATT one. But since you are using a CM based rom, it obviously doesn't matter. Curious as to why you are bothering with relocking the bootloader? But I suggest to either try a different version of the rom, or to change your recovery to one of the Philz Touch versions as that's what some of the other users in that thread for the rom for your phone were using. You can find them here:
Click to expand...
Click to collapse
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
riekkir said:
No I was bothering to unlock it again, not lock it. Where can I find different versions for the 4.4.2 Mokee Rom? I've tried using the Philz Touch version: Motorola Atrix HD One Click Philz recovery installer and when I tried it a couple of times it said it failed to install although I'm not sure why. I came across these images the other day but how do I use the .img files on my device, as I'm not sure to proceed from here once I have them downloaded.
Click to expand...
Click to collapse
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
http://forum.xda-developers.com/showthread.php?t=2619489
For installing recovery:
http://forum.xda-developers.com/showthread.php?t=2262726
es0tericcha0s said:
I was curious as why you relocked it in the first place.
Where are you getting Mokee from that doesn't have a link to their Downloads?
For installing recovery:
Click to expand...
Click to collapse
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
riekkir said:
thanks will try this out and let you know later how it works! I download the custom rom from true android blogspot.ca (can't post links just yet, annoying).
Click to expand...
Click to collapse
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
es0tericcha0s said:
Right on. Well, you should bookmark the thread here on XDA because that's typically where the action happens.
Click to expand...
Click to collapse
Okay so I'm trying it now and the program won't even open :/
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
es0tericcha0s said:
Odd. I just downloaded it to test and I didn't have any issues. If you can't get the actual application / exe file to open, then just use the Main-Skip.bat. Does the same thing.
If it doesn't open still, make sure that you have your anti-virus off as sometimes those interfere with programs like this. Might also try as admin.
Click to expand...
Click to collapse
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
riekkir said:
Okay I wasn't looking at the actual .exe sorry, I got it to work and all I installed the Philz One Touch Recovery from that program, just downloaded a different rom and all and then I select the apply update from external storage and when it gets to the verifying update package, it gave me the same error message as yesterday, Installation Aborted.
So again, how do I fix this, am I doing something wrong? Why won't my custom rom install?
Click to expand...
Click to collapse
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
es0tericcha0s said:
I don't think that is the most updated version. What's the version number of the recovery that was installed? It should be listed on the main page of it when you boot there. I was suggesting to use one of the new ones. It might have something to do with the SELinux support that KK roms need. You just have to put the img file in the tools folder and rename the new one the same. But here's no other error that shows up other than Installation Aborted? I was thinking usually it would have an error code or some other message.Have you checked the md5 of the rom zip to make sure it's not corrupted (if the dev provided it)?
Click to expand...
Click to collapse
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
riekkir said:
Use one of the new versions of that program or to use the latest CWM which I have been. Okay I really don't know how to do that and where to move it to, how do I do such a thing? No it just says Installation Aborted... How would I do that? And yes I downloaded the new rom directly from his site.
Click to expand...
Click to collapse
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
es0tericcha0s said:
Look in the tools folder of the zip you downloaded. Download the newest Philz Touch img from the other link from earlier. Rename it to replace the one in the tools folder. Redo the recovery install. But you didn't say what version you already have.
Click to expand...
Click to collapse
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
riekkir said:
Okay that did the trick, properly got philz recovery installed, did the install again, this time it worked, clicked reboot and now it's stuck at the Dual Core bootlogo screen
Click to expand...
Click to collapse
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
es0tericcha0s said:
Did you do a full wipe, including wiping /system?
If you didn't, it should be under Mounts and Storage > Format /system of something of that sort.
Click to expand...
Click to collapse
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
riekkir said:
No I forgot to do that dammit, can't get into recovery mode and my computer doesn't recognize my phone now, think I bricked it.
Click to expand...
Click to collapse
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
es0tericcha0s said:
Pop the battery out for a bit, then pop it back in and hold Volume Down while powering up. Should get you into fastboot where you can skip to the recovery.
Click to expand...
Click to collapse
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
riekkir said:
The battery doesn't come out of my phone as you can't take the back off. I got into fast boot easily them selected recovery and nothing happened, I think my phone is screwed
Click to expand...
Click to collapse
Oh yea, forgot you have to undo the screws on the bottom. So you scroll down to hit recovery and use the Power button to select and it doesn't do anything? That's odd.. Try and reflash the recovery since you can still get to fastboot. If that doesn't work, you're not totally screwed since you can still get to fastboot, that means you should be able to restore it to stock and start over.
Alternatively, if you have fastboot set up, you could make sure that philz touch is in the fastboot folder and use this command:
fastboot boot recovery nameofphilztouchfile.img
If you don't have fastboot, then just grab this one: http://forum.xda-developers.com/showthread.php?t=2317790 , drop the recovery img in that folder and open the CMD prompt on your computer and change directories to it and run the command.