Develop Bugs

[Q] Installing MIUI on Defy; stuck on the Motorola logo

Hi,
I am trying to flash MIUI on my Defy which is currently running the official 2.2.2 released here in India.
What i have done so far (and repeated the entire process several times):
-Rooted the phone using SuperOneClick
-Installed ROM Manager
-Installed Clockworkmod Recovery 2.5.1.8 for Defy
-Downloaded 'miuiandroid_Defy-2.3.4a' the then latest version of MIUI from their site and the corresponding language pack
-Installed and booted into custom recovery
-Took a nandroid backup of the current ROM
-Wiped data, cache and dalvik cache
-Selected the .zip ROM file from the sdcard and installed it
-After the installation was done, i rebooted the system
This is where the problem started. I had read that the phone might take forever for its first boot. But in my case, the phone would stay stuck on the M logo till i removed the battery. On restart, the same thing repeated.
I found the SBF for the retail version of 2.2 i found on the forums and used RSD Lite 4.9 to flash it to the phone and then restored the nandroid backup i had made previously to get back to where i started from. And i repeated the entire process 4 times using 3 different versions of MIUI.
Am i missing something here? What can i do to get the phone to move past that M logo? I have been trying to find a solution to this issue since over a week now. None of the forums seem to have a solution to a similar problem. Any help would be appreciated.

Answer to all Your problems
It's a common mistake. You must have forgotten about wipe all (cache and personal data) before installing zip package containing MIUI.

hex24 said:
It's a common mistake. You must have forgotten about wipe all (cache and personal data) before installing zip package containing MIUI.
Click to expand...
Click to collapse
I did that. Everytime i tried to install the ROM i did all the three.

Install 2nd inti not CMW and than install MIUI...
Sent from my MB526 using XDA App

ifu said:
Install 2nd inti not CMW and than install MIUI...
Sent from my MB526 using XDA App
Click to expand...
Click to collapse
It worked! It worked!
Thanks a lot!

[Q] Stuck on boot loop

I tried a search but didn't find much of any relevance to my Arc's problem.
My Arc was getting quite laggy so I decided to wipe and put a custom ROM on. I rooted, then unlocked the bootloader and managed to put on CWM using DoomLord's kernel. Everything fine up until here.
Then, mistakenly, I tried to put stable CM7 on without updating the stock ROM. I was still on 3.0 (2.3.3) something. Well, after that it got stuck in a boot loop with the SE and CM7 logos just coming up and restarting.
I then tried the Flashtool with a stock uptodate 4.0 something firmware. It flashed successfully, but it still was stuck in the loop, albeit now without the CM7 logo. I then tried the FTA unbricking tool for repairing the trim area but it still stayed in the boot loop.
What else can I do? Maybe there is a driver problem and that is why even after using Flashtool it still doesn't boot?
I would be very grateful if someone could help me on this.

You have to flash FXP's kernel and not DooMKernel.

But I also tried to flash a stock rom and that didn't work also.
EDIT: I flashed stock ROM again, still didn't boot. Installed DoomLord kernel and then arconium and it still doesn't boot.
EDIT 2: In CWM Recovery if I try to wipe data, it says this:
"E:format_volume: no MTD partition "userdata"
Has anyone got a fix for this?
It would be much appreciated.

can you charge your phone now?

Yep, I can charge the phone.

it means your kernel is still working....
then have it fully charged, then try to flashing again.
some tips:
1. always have latest flashtools
2. always have your phone fully charged b4 flashing.
3. proceed flashing carefully. if u miss one thing, then trouble come.
4. have cache and dalvik cache cleaned after flashing a kernel or Rom.
good luck mate...

gogo415 said:
it means your kernel is still working....
then have it fully charged, then try to flashing again.
some tips:
1. always have latest flashtools
2. always have your phone fully charged b4 flashing.
3. proceed flashing carefully. if u miss one thing, then trouble come.
4. have cache and dalvik cache cleaned after flashing a kernel or Rom.
good luck mate...
Click to expand...
Click to collapse
No luck with previous firmwares so I'll try to flash the latest .62 stock ROM and then see.
I'll let you know how I get on. Thanks!

Well lads, I managed to get it working by flashing the LT18i firmware (4.0.2.A.0.42_CE). Now I just need to go back to the drawing board and try to get CM7 on there.
Thanks for all the help! I'll update this thread with any experiences.

I've managed to do it. Installed latest .62 firmware, flashed CM7 kernel, flashed 7.2 ROM and then GAPPS.
I don't know why it took me two days to bring the phone back from the dead.

ZAnwar said:
I've managed to do it. Installed latest .62 firmware, flashed CM7 kernel, flashed 7.2 ROM and then GAPPS.
I don't know why it took me two days to bring the phone back from the dead.
Click to expand...
Click to collapse
hi, i came up with the same question:
E:format_volume: no MTD partition "userdata"
and my device is moto xt502
could you be so kind to give some details how you fix it
thank you very much

I am having the same problem too..please help! i flashed cm7 kernel n followed the instructions very carefully

ilamaan said:
I am having the same problem too..please help! i flashed cm7 kernel n followed the instructions very carefully
Click to expand...
Click to collapse
I followed the instructions too, though they are not so much noob-friendly (and neither are the people on the forums, it seems...). FXP is not responding (actually, they rarely respond to anything, they usually just post when new release is out), other people either don't know how to fix it, because they haven't experienced such issues, or they are just hostile because you're "a an annoying noob". Anyway... first time after trying to flash 64 baseband on 107 or 106 release, I got stuck on logo, then flashed back to .42 and it worked. Now, while updating to 108, I tried to flash the 64 libraries and patch, but it didn't work. Got back to .42, but this time nothing happened. Still stuck on logo. And when I try to restore data, it says:
E:format_volume: no MTD partition "userdata"
Error while formatting /data!
I think I'll go back to stock... love CM, but hate the poor/no help of the developers...

try these
flash new firmware using flashtool.
after flash.turn on your device.
enable uknown source n usb debug
then turn off your fon
flash baseband 64
then turn on your fon
put fxp108 updated-kang,gaps,baseband 64 libs on your memory card,
then turn off your fon
flash fxp kernel fastboot flash boot boot.img
after flash turn on your fon..go to recovery
formated factory reset,wipe cache,clear dalvik cache,wipe betry stats..
flash update cm7.update.zip,gaps.zip,baseband64libs.zip
reboot your fon..wait 2 or 3 mint..done

My thanks goes to you. I was hoping to avoid full wipe, but I don't care anymore, since I brought my phone back to life. I skipped these steps, though:
beranchoi said:
flash baseband 64
flash baseband64libs.zip
Click to expand...
Click to collapse
...because I went to check which baseband my phone was after flashing Global .62, and it said I was on -64, so it was no more necessary. For all of you having trouble with booting, follow the instructions given.
And now back to restoring all those apps

hey guys, can you post the link to that stock firmware, baseband and libs? maybe I've downloaded something wrong :/
btw. is there still that bug with a dark screen after locking phone?

lemon66 said:
hey guys, can you post the link to that stock firmware, baseband and libs? maybe I've downloaded something wrong :/
btw. is there still that bug with a dark screen after locking phone?
Click to expand...
Click to collapse
This is the link to the stock 4.0.2.A.0.42.. flash it using flashtool.. http://www.multiupload.com/W3B7BOKUXQ
Everything you need for flashing FXP is on his signature, including bb .64 (to be flashed with flashtool - doesn't erase a thing).. then download FXP (latest is 108) and inside the zip file you'll see boot.img, which contains the special kernel (to be flashed using fastboot, not flashtool).
Also there's no dark screen bug in the latest releases, certainly not in FXP 107 and 108, which I'm using now.

Please help!
beranchoi said:
try these
flash new firmware using flashtool.
after flash.turn on your device.
enable uknown source n usb debug
then turn off your fon
flash baseband 64
then turn on your fon
put fxp108 updated-kang,gaps,baseband 64 libs on your memory card,
then turn off your fon
flash fxp kernel fastboot flash boot boot.img
after flash turn on your fon..go to recovery
formated factory reset,wipe cache,clear dalvik cache,wipe betry stats..
flash update cm7.update.zip,gaps.zip,baseband64libs.zip
reboot your fon..wait 2 or 3 mint..done
Click to expand...
Click to collapse
Hey, this is my first post on here. I am new to android and just got an arc a few days ago. Even before i got it i was trying to figure out how to mod it. I am reasonably good at computers but a lot of the stuff i read on these forums is beyond me.
I have done my best to root and install CM7 on my arc but i have failed yet again.
I finally got it rooted and was all happy until when i tried to install CM7, all i can get to is the boot screen, but although the little android on the skateboard is very cool, i wish i could get it going!
So because I dont really understand the list of instructions you posted in this quote, i was hoping you could kind of translate into noob-speak. I still dont feel like i completely understand 'flashing'. In your instructions you say to "flash baseband 64" and that is the main point where I am stuck i think. Do you use a certain program (flashtool?) for this? or do it through a terminal window on the PC.
Also links to all the files mentioned would be awesome, its hard to find proper links with multiupload down and that kind of thing. Also with the rate this kind of tech evolves, things get outdated to quickly.
Please help! At the moment i have (i think) successfully returned my arc to the stock firmware using flashtool. Although i did this twice because i re-tried flashing CM7 and failed again. And the second time i couldnt seem to select LTI5i as the device to flash too, but LTI8i is what i used and it appears to have worked. So any help with that little conundrum would also be appreciated!
Cheers for any help given, I am so desperate to get this mod going as i have spent a solid 10+ hours trying already.

your bootloader unlock?right?
which kernel u use right now?

@tehknowitallnoob, I can lead you through the whole flashing process, if you want to, but only on Friday after around 9 pm GMT +1, since I don't have the time to do it earlier.
Sent from my LT15i (Xperia arc) on CM7

Try this:
Reflash back to stock ROM with a flashtool.
Then again flash the cm7 or try cm9
-cheers

[Q] Help, won't boot any custom roms.

After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant

Did you wipe data and cache when you flashed the new rom?

nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM

cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you

chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik

nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.

nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.

Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app

[Q] What did I screw up? (Failed move to TWRP and new AOKP)

Hey -
First of all, thanks in advance for any help. I never thought I'd be one of the folks posting a "help, I killed my phone" thread, but I don't have a choice!
I was running AOKP JB Milestone 1 and CWM, and decided to flash TWRP 2.3.something and the new AOKP JB MR-1 build. I did a backup in TWRP, ran Ti Backup, and installed the new build and gapps that I dl'ed from GooManager. I wiped dalvik and cache. When I booted, every app crashed and the phone was unusuable, so I went back to TWRP recovery and did a factory reset (after googling to confirm that it would not delete my GNex's sdcard, so I should still have my backup images).
Now, I get past the AOKP boot animation, but the Setup Wizard appears, then stops. Clicking "ok" leads only to another "Unfortunately Setup Wizard Has Stopped" box. Infinite loop. Bad news.
What is scaring me is that I can't find any recovery images to flash in TWRP, and don't see them even in the /0 folder on the SD card. Now I'm thinking I somehow erased my backups, and have a version mismatch. I thought I had TWRP 2.3.3.0, but the recovery says 2.3.1, so I'm wondering if I have an ICS/JB issue.
Anyway, I'm clearly stumped. Do I need to start from scratch and load CWM and a stock image via my PC? I don't think I can load anything any other way, but can't try that until later today.
Thanks again for any advice...

Ok, not sure what is going on, but after multiple reboots I could at least access my roms via TWRP and was able to reflash and get past where I was stuck. I'm hoping a new flash of the current gapps package will at least clear this up enough to see if my data is gone...

What gapps version were you using?
Sent from my i9250

[Q]bootloop issues after factory reset

Hey all, I've tried searching but haven't had any luck. I believe I have a somewhat unique issue.
Back in June 2012 I originally tried flashing FXP CM10 but kept getting a boot loop. Since then I put on JJ's Hybrid rom and MIUI until I decided to try FXP again. (147 or something) It worked fine and I used it for quite a while until I just recently updated to FXP 203 without issue.
I got a new Nexus 4 and decided to do a complete wipe on my Arc so that I could give it away. I wiped cache, data and (stupidly) SD card.
After the wipe it froze on "Android is upgrading" and a battery pull made no difference.
After that, I decided to re flash the kernel and ROM, but made no difference. I flashed MIUI (a version I knew that worked) and the phone worked fine, but then I tried with FXP205 and right back to boot looping. (even tried downloading the rom to my work computer)
Most recently I left the phone to boot loop for a while and it actually managed to startup, and I could use it for a few seconds before it froze and restarted again.
Does anyone have any suggestions on what to try? I feel like I've tried everything, and it's strange that FXP worked totally fine for 6+ months and now this issue. I don't have any nandroids unfortunately since I wiped my SD card (like I said, stupid)

Youre flashing the following kernel by fxp inside the zip?
Remember to remove the boot.img from zip before installing.
Are you factory resetting, system format and dalvik wipe with cwm before installing zip?

Hey, thanks for the reply. I followed your instructions exactly, but I'm having the same problem. Any other ideas?

Flash a stock ftf as advised on the hundreds of other "bootloop" threads. CWM shouldn't even come into it.

XperienceD said:
Flash a stock ftf as advised on the hundreds of other "bootloop" threads. CWM shouldn't even come into it.
Click to expand...
Click to collapse
Tried that, no luck. Thanks for the suggestion though.