Related
Ok, where do I start. Here is my problem: Any of the leaked based rom get stuck at the black & white stripes (wich I flashed many time without problem) Let me explain the chain of event that got me that point.
Last week I installed the leak ( Acer_A500_1.031.00_WW_GEN1 ) and rooted it and patched the bootloader with blackthunder's apx tool that also installed a modified version of thor's cwm that work with ICS bootloader. Everything worked fine but knowing that civato's flexreaper support the ics bootloader I decided to install it...R11 worked fine (even the b&w stripes at boot was gone...thx to the ics bootloader).
This is where it got crazy, while doing simple web browsing, i got a freeze that obliged me to force shutdown. On reboot, I got a bootloop at bootanim. Decided to flash FlexR11 over it to fix. During the flash I received an error about flexrom. Rebooted and the bootloop persisted. Then cwm started to be slow responding to navigation with volume rocker, so I decided to flash Acer_A500_1.031.00_WW_GEN1 again wich didn't boot too. Cwm was still there but even more screwed, would not see any sdcard int or ext. I tried to apx push a recovery with blackthunder's tools with no success.
I finally got it back to life with TimmyDean's EUUs flashing a rooted 3.2.1. with HC bootloader. Now the only ICS rom I can install is thor's rom ..everything work fine. BUT any of the leaked based rom get stuck at the lines and even the leak itself after being installed get stuck at the acer logo...and cwm is still present where it should have been overwriten.
I think it may have something to do with flexrom (i guess thor don't use that partiton since it's for acer crapware)...but im not sure since 3.2.1 work with acer's stuff & all. Maybe the bootloader is corrupt in some way, but it was reinstalled by the EUUs tool anyway.
I tried to format everything including flexrom..tried both civato's kernel in case there are some bits of ics bootloader left... Im desesperate trying to understand what's wrong exactly and how to fix this.
Anyone have an idea? Thx in advance & sorry for my average english.
lowsum said:
Ok, where do I start. Here is my problem: Any of the leaked based rom get stuck at the black & white stripes (wich I flashed many time without problem) Let me explain the chain of event that got me that point.
Last week I installed the leak ( Acer_A500_1.031.00_WW_GEN1 ) and rooted it and patched the bootloader with blackthunder's apx tool that also installed a modified version of thor's cwm that work with ICS bootloader. Everything worked fine but knowing that civato's flexreaper support the ics bootloader I decided to install it...R11 worked fine (even the b&w stripes at boot was gone...thx to the ics bootloader).
This is where it got crazy, while doing simple web browsing, i got a freeze that obliged me to force shutdown. On reboot, I got a bootloop at bootanim. Decided to flash FlexR11 over it to fix. During the flash I received an error about flexrom. Rebooted and the bootloop persisted. Then cwm started to be slow responding to navigation with volume rocker, so I decided to flash Acer_A500_1.031.00_WW_GEN1 again wich didn't boot too. Cwm was still there but even more screwed, would not see any sdcard int or ext. I tried to apx push a recovery with blackthunder's tools with no success.
I finally got it back to life with TimmyDean's EUUs flashing a rooted 3.2.1. with HC bootloader. Now the only ICS rom I can install is thor's rom ..everything work fine. BUT any of the leaked based rom get stuck at the lines and even the leak itself after being installed get stuck at the acer logo...and cwm is still present where it should have been overwriten.
I think it may have something to do with flexrom (i guess thor don't use that partiton since it's for acer crapware)...but im not sure since 3.2.1 work with acer's stuff & all. Maybe the bootloader is corrupt in some way, but it was reinstalled by the EUUs tool anyway.
I tried to format everything including flexrom..tried both civato's kernel in case there are some bits of ics bootloader left... Im desesperate trying to understand what's wrong exactly and how to fix this.
Anyone have an idea? Thx in advance & sorry for my average english.
Click to expand...
Click to collapse
Sounds like you have data leftover (either not a good enough wipe, or corrupted data)
Try this. Note that this will reformat your entire internal memory, but will ensure all remaining data is cleaned up and removed.
Before installing your rom;
1. Wipe User Data
2. Wipe Cache
3. Wipe DalviK
4. Wipe Battery Stats
go to Backup and Restore. Select "Toggle backup and restore of internal storage (/data/media). Enable this setting by selecting it. By default, it is disabled. Then proceed to the formatting steps. This will format the Entire Internal Memory when you proceed.
Select Go Back, Goto Mounts and Storage
1. Format System
2. Format Cache
3. Format Dalvik
4. Format Flexrom
This WILL format your entire internal memory, so if you have something important, you need to copy it out. Note that this should not effect things on the Ext SD Card.
Thanks for replying, yes I already done that, the problem persist. I wonder if it could be the bootloader, but like I said, other roms works, only the leak based have problem. Is there a way to "format" the bootloader? It should have been reset to HC when I applied 3.2.1 in apx... hmmm very strange!
lowsum said:
Thanks for replying, yes I already done that, the problem persist. I wonder if it could be the bootloader, but like I said, other roms works, only the leak based have problem. Is there a way to "format" the bootloader? It should have been reset to HC when I applied 3.2.1 in apx... hmmm very strange!
Click to expand...
Click to collapse
Well, more than likely it is indeed a bootloader issue. But you must understand, all these "leaked" ICS roms are what they are... BETA. And with each new leak, there's a different bootloader. So you have to pay attention to the instructions for the specific leak. Usually involves flashing a newer or older bootloader to match the rom.
Until Acer releases an "official" ICS Rom and source code for the 500/501, these issues are going to be around for awhile.
My choice, would be to run a 3.2.1 rom. Very few issues with some of the mildly modded ones. Then wait awhile, till the official ICS updates come out.
One good thing out of this, you learned some tricks on how to recovery from some "semi-bricks"
I think the leak may not be the source of the problem, I already installed 009 when it first appeared a couple of weeks ago, and restored with EUU without problem, but this time with 031 I rooted it with blackthunder's root tool and applied a modified bootloader and cwm recovery. Even if I restore 3.2.1 with timmydean's EUU package and hc bootloader, the leak base rom get stuck at the b&w lines (where it's looking for the bootloader or loading kernel). It make no sense to me that the leak is the source of the problem. Is there a diagnosis tool that can check my partition integrity? Still wonder...!
lowsum said:
I think the leak may not be the source of the problem, I already installed 009 when it first appeared a couple of weeks ago, and restored with EUU without problem, but this time with 031 I rooted it with blackthunder's root tool and applied a modified bootloader and cwm recovery. Even if I restore 3.2.1 with timmydean's EUU package and hc bootloader, the leak base rom get stuck at the b&w lines (where it's looking for the bootloader or loading kernel). It make no sense to me that the leak is the source of the problem. Is there a diagnosis tool that can check my partition integrity? Still wonder...!
Click to expand...
Click to collapse
Well, this is one of the reasons I decided not to mess any further with the ICS builds till a good official version comes out
I'm not aware of any tools to check partition integrity. Maybe there may be something in the main Android Dev forum.
RA Recovery has an option to check your partitions, but I believe it only gives a current status whether they are EXT3 or EXT4.
Moscow Desire said:
Well, this is one of the reasons I decided not to mess any further with the ICS builds till a good official version comes out
I'm not aware of any tools to check partition integrity. Maybe there may be something in the main Android Dev forum.
RA Recovery has an option to check your partitions, but I believe it only gives a current status whether they are EXT3 or EXT4.
Click to expand...
Click to collapse
It is possible to rebuild your partition structure from scratch (using SBK + bootloader + nvflash create command + bct + flash.cfg + system image + recovery image + boot image + probably some other things) but I'm not sure of anyone that has done this and I can't say I have myself. Using timmydean's method (with a, what looks like, leaked Acer A500 Flash Tool) should, in theory, wipe it clean and start again.
I created a flash bundle to reset back to version EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 (it's on the forum I use which I got tempbanned for mentioning publicly ) but it's untested. I see no reason it shouldn't work, however.
I tried another way to restore my tab, this time flashing a leak based rom with RA recovery instead. This time i had a little different behavior, during flash process, formating flexrom froze for a while outputing this error: Random Offset : 0x188 ...the rest flashed normally. At first boot it froze after 2sec during bootanimation, before it froze at the black & white lines.
I think I may have a corrupted flexrom partition, so Im wondering, does the recovery*doing a quick format erasing only the first sectors? If so, is there any way to do a deep format?
Hello
I have Motorola Bravo, everything stock 2.2.1 ROM
but I want to install custom ROMs and I have one question: Does Motorola Bravo's bootloader need unlock? I ask that, because I also have Motorola Atrix 4G and I had to unlock it's bootloader to install Cm7
Enigmavision said:
Hello
I have Motorola Bravo, everything stock 2.2.1 ROM
but I want to install custom ROMs and I have one question: Does Motorola Bravo's bootloader need unlock? I ask that, because I also have Motorola Atrix 4G and I had to unlock it's bootloader to install Cm7
Click to expand...
Click to collapse
No, just install 2nd-init recovery (search the Defy Forums\CM7 threads here) then flash away . Our bootloader is locked up like a con in a SuperMax with a triple life sentence. I'm getting ready for work so I don't have time to hotlink.
skeevy420 said:
No, just install 2nd-init recovery (search the Defy Forums\CM7 threads here) then flash away . Our bootloader is locked up like a con in a SuperMax with a triple life sentence. I'm getting ready for work so I don't have time to hotlink.
Click to expand...
Click to collapse
Here you go: https://www.box.com/shared/p07z8hangnqxydducrhr.
Edit: on a side note, I've had issues restoring my JB nand from the cm7 recovery. I get "error restoring system" in the middle of a nand restore. It also completely screws up mounts and the only thing I can do is install a ROM from scratch. The md5 checks out as well. Any ideas?
Dr. Orange said:
Here you go: https://www.box.com/shared/p07z8hangnqxydducrhr.
Edit: on a side note, I've had issues restoring my JB nand from the cm7 recovery. I get "error restoring system" in the middle of a nand restore. It also completely screws up mounts and the only thing I can do is install a ROM from scratch. The md5 checks out as well. Any ideas?
Click to expand...
Click to collapse
JB has a newer recovery. Install a JB rom then restore the nand of the JB backup.
Flash JB rom (cache\data wipes don't matter since you won't be booting into the system)
Reboot directly into recovery (don't let the system boot up, even once)
Restore JB Backup as usual
This is actually a common problem with Defy users running older MS2 roms trying to flash JB -- the different recovery versions can be a pita to deal with sometimes; but its usually fixed by flashing a rom with a compatible recovery version then restoring the nand afterwards.
While I won't go into the full details, you can also take the recovery from a JB rom and a GB rom and make them into a flashable zips -- basically open the rom's zip and delete all the /system folders except /system/bootmenu and edit the rom's updater-script to only set permissions to /system/bootmenu. It would also be a good idea to add in ramdisk backup commands as well (the init.rc files under 2nd-init and 2nd-boot) since they can change from rom to rom. Once all that's done you'll be able to flash the required recovery version for the nand you intend to restore or flash the JB recovery after flashing any rom and have an up-to-date recovery with an older rom. If you use multiboot it would be a good idea to merge it into your new recovery zip as well.
/About to test a CM7 port with many tweaks -- if it boots I'll start adding in some market apps and finish it up later today . Then its off to start updating PA with a Custom Kernel . I may have to drop MS2 PA support if the MS2's Custom Kernel differences makes it incompatible with the Defy base
skeevy420 said:
JB has a newer recovery. Install a JB rom then restore the nand of the JB backup.
Flash JB rom (cache\data wipes don't matter since you won't be booting into the system)
Reboot directly into recovery (don't let the system boot up, even once)
Restore JB Backup as usual
This is actually a common problem with Defy users running older MS2 roms trying to flash JB -- the different recovery versions can be a pita to deal with sometimes; but its usually fixed by flashing a rom with a compatible recovery version then restoring the nand afterwards.
While I won't go into the full details, you can also take the recovery from a JB rom and a GB rom and make them into a flashable zips -- basically open the rom's zip and delete all the /system folders except /system/bootmenu and edit the rom's updater-script to only set permissions to /system/bootmenu. It would also be a good idea to add in ramdisk backup commands as well (the init.rc files under 2nd-init and 2nd-boot) since they can change from rom to rom. Once all that's done you'll be able to flash the required recovery version for the nand you intend to restore or flash the JB recovery after flashing any rom and have an up-to-date recovery with an older rom. If you use multiboot it would be a good idea to merge it into your new recovery zip as well.
/About to test a CM7 port with many tweaks -- if it boots I'll start adding in some market apps and finish it up later today . Then its off to start updating PA with a Custom Kernel . I may have to drop MS2 PA support if the MS2's Custom Kernel differences makes it incompatible with the Defy base
Click to expand...
Click to collapse
Yep that makes sense. Thanks for the help as always skeevy.
*edit* Same issue.
Restoring system...
Error while restoring /system!
Problem while restoring system!
Maybe I didn't reboot correctly...bad backup maybe? I've restored this backup before with no problems. : \
*edit again* I goofed. Your instructions worked fine.
Hi guys, I've accidentally flashed a p4wifi aokp milestone6 on my nexus S (didn't pay enough attention)
Now my phone boots correctly, but I can't mound sdcard, and this happens on recovery too
Is there anything I can do? I can't flash back any roms
P.S: It seems that I have my old rom installed (aokp jb), that's what the Info says
Flash back the stock Rom buddy it ill help you
shazzy1 said:
Flash back the stock Rom buddy it ill help you
Click to expand...
Click to collapse
But How? I can't copy it
what version of recovery do you use?
Use odin man
I use CWM. I think that I can solve everything if I format the sd, but I really need to access it to save some files first
I use cwm 6.0.1.3 version and has problem mounting sd thats why i asked you. Try to flash a 5 version with fastboot to mount sd.
Sent from my Nexus S using xda app-developers app
fastboot
fastboot can update rom too.
fastboot flash [partition name] [image name]
three partition, system boot radio, needed for rom flashing.
fastboot flash system filename.img
fastboot flash boot boot.img
fastboot flash radio radio.img
Never had any problem with mounting sdcard with cwm, it would be way too coincidental that it stopped working just exactly when I flash a wrong rom.
And I have 5.5.0.4...
In theory, flashing the wrong boot.img could create a missmatch on the mount points. If all else fails you can fastboot in the various partitions directly to correct.
i have this problem too on my brother's gnex.
i currently downloading stock factory image to flash from fastboot.
just try that.
hope we can get back our usb storage.
if you found another way please share.
thanks.
Hey guys, just a quick question, do I have to wipe userdata when installing a new ROM? Should I install a rom and hope it works? And then suffer the consequences? I'm running stock with Trinity kernel, trying to go to latest cm 10 or whatever it is.
Thanks
-Micro
You can get away with over-flashing (or "dirty flashing") very closely related ROMs.
For instance if you were testing CM nightlies from night to night.
In general though it is not a good idea, and even in the case of closely-related ROMs there really are no guarantees. It is certainly not a good idea for a random pairing of before/after ROMs.
BTW the "wipe" that you want is a wipe of /data that clears everything but /data/media (so the "/sdcard" doesn't get nuked), plus a wipe of /cache. In TWRP this is called "factory reset"; I'm not sure what it is called by CWM (note that in the stock recoveries all of /data gets wiped by the "factory reset", so the term means slightly different things in different contexts)
good luck
Hey thanks a lot. Did not know it would't erase the "sdcard" so I installed cwm cm and trinity kernel. Then reinstalled all my apps with titanium. Okay one more question. How exactly do I install cm and trinity kernel? Here's how I did it. I went into ROM manger, downloaded cm, added gapps and then clicked the add zip and selected trinity kernel.. Is this right? Does it matter what order you go in? How would I get rid of trinity kernel? If I were to get rid of trinity kernel, I would have to install a different kernel right? Cm doesn't come with a kernel since its just a ROM right? Also does the cm 10 come with a boot animation? Since I installed trinity second, I have trinity boot animation..
Thanks again!
-Micro
Whew that's a lot of questions - I'll answer a few but not all. (I don't ever use ROM manager.)
By convention, all dev ROMs come with a boot image (which contains a kernel and ram disk), so if you combine an arbitrary ROM and kernel, the kernel needs to be flashed after the ROM.
If you don't like that kernel and want to revert to the one the comes with the ROM, just dirty-flash the ROM again. (This is an example where dirty-flashing should be completely safe - it's the identical ROM! /system won't change even though it is being flashed... unless you customized the ROM since you installed it. FYI some root-aware apps & even TiBu can do this depending how you use it... so dirty-flashing could bust things in that circumstance).
An even safer method would be to get a nandroid backup of the ROM before you flash the kernel mod. TWRP allows you to the option to restore only individual partitions, and this would allow you to restore only the boot partition. I'm not sure if you have this kind of flexibility in CWM or ROM manager.
Backups give you freedom and confidence. Make sure you are making them, and getting copies of them off the tablet, as it is easy to make a mistake and accidentally wipe all of /data including the pseudo-SD card.
I was wondering whenever I should post this in the "bricks" thread, I'm still not sure what the term "brick" means entirely but what I'm gathering is that it's usually when people try to flash sommat and mess it up, this isn't exactly the case for me, either way I believe this case to be special enough to deserve a separate thread, this is not your usual "guys help I installed custom rom x and am bootloop".
Context: A couple days ago I was in a call with someone and right after hanging up my phone froze completely, I had to reboot but then I was stuck at boot (bootloop), decided to try and wipe data (didn't really have anything important there) but I got an error when I tried to mount /data. After a while I decided to flash stock with odin, I was confident that would fix it, but it didn't, I was stuck at boot again, I went into recovery and tried to check if I could mount /data, but nope, none of that.
This is the error I get when I try to mount /data:
In stock recovery
Code:
-- Wiping data...
E:format_volume: rfs format failed on /dev/stl11
In CWM
Code:
-- Wiping data...
formatting /data...
Error mounting /data!
Skipping format...
Sometimes it'll just freeze at "Formatting /data...". By the way, the errors were the same before and after flashing stock.
Apparently something is wrong with my data partition, here is a list of things I have and have not tried so I eliminate the potentially not-useful replies, oh yes I can see them coming already:
I have tried:
-flashing stock with odin, it all works fine and I get PASS, only error I get is when my phone is installing CSC during recovery, but that's only because /data is unusable
-including PIT and bootloader
-yes, it's the correct PIT.
-yes, I checked re-partition.
-flashing PDA, MODEM, CSC, BL and PIT in every possible order
-trying mount /data (duh, that's the very issue)
-trying mount /data after flashing stock
-googling a lot
I have not tried:
-Any odin option other than the default ones and re-partition
I'm not really sure why this keeps happening after flashing PIT, as far as I know that's supposed to re-partition my phone, doesn't that mean it should wipe out anything in the partitions, thus getting a completely new /data partition?. I'm not an expert when it comes to android phones, I'm just comparing it to linux.
Is there a way to just REMOVE my /data partition and make a new one?, I believe that would fix the issue.
Some extra background, I have been using Hyperion 9 (not sure if it was 9?, I know it was the latest OFFICIAL hyperion rom though), I have bricked my phone in the past many times when I was a teenager (yes, this very same phone, I've had it for years), and also fixed it many times by flashing stock, at the end I got bored of it and stayed at stock, then about a year or two ago (I think?) I decided to find a custom rom + a kernel to save up on battery, I don't really remember what I did but I got Hyperion 9 and some kernel, haven't messed with my phone since.
Also, yes, I know this is a very old model, but if I can fix this phone I definitely will, I have my reasons.
EDIT: added more info
EDIT: I think one part sounded a bit rude, edited
Where you get stock rom?
Did you tried stock from this thread?
This stock only have 3 file: csc, modem, pda.
And don't use .pit Odin file.
noob&noob said:
Where you get stock rom?
Did you tried stock from this thread?
This stock only have 3 file: csc, modem, pda.
And don't use .pit Odin file.
Click to expand...
Click to collapse
I'm getting my stock from sammobile.
catwank said:
I'm getting my stock from sammobile.
Click to expand...
Click to collapse
Maybe you can try xda topic stock rom
noob&noob said:
Maybe you can try xda topic stock rom
Click to expand...
Click to collapse
I've tried multiple stocks from sammobile just to be sure, even stocks from different regions, I see little point in trying more. The stock rom is not the problem, it works fine and I've used the same stock rom effectively in the past.
same problem here in cwm or odin
error mounting data