device Atrix 4g AT&T (2.3.6)
i install rom ICS or JB from http://forum.xda-developers.com/forumdisplay.php?f=997
i can't boot it, sometime i can here sound boot in display not show anything.
my device root and unlock now
how i can fix it?
"That Rom"
"ICSRom 1.4"
update: this time i can boot it but device very lag
update 2 : i close device and open it's black display after logo motorola
thanks
gatxclub said:
device Atrix 4g AT&T
i install rom ICS or JB from http://forum.xda-developers.com/forumdisplay.php?f=997
i can't boot it, sometime i can here sound boot in display not show anything.
my device root and unlock now
how i can fix it?
update: this time i can boot it but device very lag
thanks
Click to expand...
Click to collapse
Can you please be a little more informative about whats happening? I don't get anything.
i install rom from link by CWM in bootloader
in bootloader install finish, after i reboot it have logo motorola about 10 sec. display it's dark don't show anything.
but i can open bootloader in open device
gatxclub said:
i install rom from link by CWM in bootloader
in bootloader install finish, after i reboot it have logo motorola about 10 sec. display it's dark don't show anything.
but i can open bootloader in open device
Click to expand...
Click to collapse
Did you try to do a factory wipe ? and format cache?
joelorona said:
Did you try to do a factory wipe ? and format cache?
Click to expand...
Click to collapse
i try it but not good
If you can boot the phone but it's laggy, did you install the ramfix? Seems from your English (no offense) that you are an international user so you probably need it.
you can get the flashable zip here: http://forum.xda-developers.com/showthread.php?t=1240310
thanks, i will try it!
update : i download auto ram fix and install http://forum.xda-developers.com/showthread.php?t=1930645 my device can't boot to os, it can boot in motorola logo only and auto reboot
how did you install the rom if I may ask? did you format/wipe your system/data/cacha/dalvik cache?
else if you have a bootloop problem a possible answer given by upndwn4par is to pull out the battery, press volume down while placing the battery again and navigate to android recovery. Then reflash your rom (i would recommend first formatting the partitions mentioned first), and then flash the ramfix (don't forget this step).
Hi,
My device : Atrix 4G (AT&T)
i install rom with recovery mode (ClockworkMod 5.0.2.0)
i try to install "ThatRom" and ICSROM 1.4
- First i wipe Dalvik Cache in advance menu
- i install fixrom from ext-sdcard
- i install "ThatRom" from ext-sdcard
- Format wipe date/factory
- Reboot
result ICSROM 1.4 : it auto reboot in motorola logo in phase open device
result ThatRom : after boot device have logo motorola, logo fade out have sound and Screen off. + 3-4 min have sound boot and loop
how i can fix it.
This time i use rom CM. 9.0 for atrix but i don't like it because it's not have webtop
thanks
I first did a format cache/data/system in mounts and storage
then in advanced dalvik cache, afterwards installed the rom from ext-sd, flashed ramfix and rebooted.
worked fine for me but remember that it can take some time the first time (seems you know this but nevertheless), so maybe you could try it in that order?
else you can try the method for pulling battery (or do it immediatly, maybe it'll help)
This time i can install "That Rom".
in first boot it's use time to boot around 30 min. and i setup device and reboot.
second time to boot device i can't come in to os i here sound boot and my battery's hot.
So after first i can't boot to os.
how i can fix it's
thanks
update : i try to reinstall thatRom it's can't boot to os
Have you tried AtrICS rom? It's a newer release and has less bugs to my opinion.
You do know that webtop does not work with lapdock in these builds? and that battery life is terrible (if you don't get the screen glitches and random reboots)?
I think for now you could be better of with a GB build since these are not really daily driver compatible and perhaps not yet worth the hassle.
If you really want to, you can try installing AtrICS but hot battery etc etc are part of the rom and wont be solved without kernel sources.
yes, this time i try AtrlCS rom i can't boot too.
sometime i will use 2.3.6 only T_T
Related
Cause of I read it from many users, that they get WLODs anymore on the newest Cm7 release from J and I haven't problems, I'll share a list with steps to install it, with that it worked for me perfectly.
If you have a working Recovery you can start directly with step 6
1. Flash with Flashtool a stock firmware
2. Boot up into stock
3. Activate usb debugging
4. Root it (connect phone with activated debugging mode and press in flashtoll root)
5. Install FreeXperiaRecovery (connect phone again, click "ask root permissions" and then click on xrecovery button)
6. Download the Cm7 rom form here, and the two files from here: http://forum.xda-developers.com/showthread.php?t=1073859
7. Copying all files needed for flashing the rom on your sdcard: Cm7 rom and the Screen off fix
8. Reboot and check if you can enter Recovery
9. If not, start at the point where you install it via Flashtool
10. If yes, take out the battery and wait ~15-30 sec.
11. Now put your battery in again and flash the .ftf bundle from the thread i linked above
12. If it flashed succesfully reboot and enter Recovery. Make ALL available wipes (full wipe, wipe cache, wipe system, wipe battery stats, wipe dalvik cache. I think that are all, right?) Now DON'T reboot before you made the next step, cause you have to start from zero if you reboot before making the next step
13. Flash the Cm7 rom
14. Flash the screen off fix
15. Reboot and wait until you get into the rom.
Note:
I know that J provides a own Baseband package, but i use this .ftf bundle, where I mixed the 435 Firmware parts with the amss.sin of the bb.52 bundle available in the bbcollection thread and I haven't any problems with this and on that way, you haven't to flash always the normal and the modded bb if you switch between roms.
9Lukas5 said:
Cause of I read it from many users, that they get WLODs anymore on the newest Cm7 release from J and I haven't problems, I'll share a list with steps to install it, with that it worked for me perfectly.
If you have a working Recovery you can start directly with step 6
1. Flash with Flashtool a stock firmware
2. Boot up into stock
3. Activate usb debugging
4. Root it (connect phone with activated debugging mode and press in flashtoll root)
5. Install FreeXperiaRecovery (connect phone again, click "ask root permissions" and then click on xrecovery button)
6. Download the Cm7 rom form here, and the files from here: http://forum.xda-developers.com/showthread.php?t=1073859
7. Copying all files needed for flashing the rom on your sdcard: Cm7 rom and the Screen off fix
8. Reboot and check if you can enter Recovery
9. If not, start at the point where you install it via Flashtool
10. If yes, take out the battery and wait ~15-30 sec.
11. Now put your battery in again and flash the .ftf bundle from the thread i linked above
12. If it flashed succesfully reboot and enter Recovery. Make ALL available wipes (full wipe, wipe cache, wipe system, wipe battery stats, wipe dalvik cache. I think that are all, right?)
13. Flash the Cm7 rom
14. Flash the screen off fix
15. Reboot and wait until you get into the rom.
Note:
I know that J provides a own Baseband package, but i use this .ftf bundle, where I mixed the 435 Firmware parts with the amss.sin of the bb.52 bundle available in the bbcollection thread and I haven't any problems with this and on that way, you haven't to flash always the normal and the modded bb if you switch between roms.
Click to expand...
Click to collapse
Hi there. I am curious to try this. How is your battery life. Also, which version are you running, the previous "b" or "c". Reason i ask is because on your signature, it says "7.0.3-X10-J020b"
Thanks
where can i download FreeXperiaRecovery?? I will tray this!
avez197 said:
Hi there. I am curious to try this. How is your battery life. Also, which version are you running, the previous "b" or "c". Reason i ask is because on your signature, it says "7.0.3-X10-J020b"
Thanks
Click to expand...
Click to collapse
I have runned this way J020b, I would try the c, but I can't! It's bad, but my phone is at the se service point for repairing it. But if I get it back, I'll install directly the latest Cm7 version again.
9Lukas5 said:
I have runned this way J020b, I would try the c, but I can't! It's bad, but my phone is at the se service point for repairing it. But if I get it back, I'll install directly the latest Cm7 version again.
Click to expand...
Click to collapse
Thanks. Will give feedback after trying
barsom said:
where can i download FreeXperiaRecovery?? I will tray this!
Click to expand...
Click to collapse
If you download Flashtool 0.2.9.1 there is FreeXperiaRecovery included. Look into the list, there wrote to click on the xrecovery button for installing FreeXperiaRecovery. The files are included in flashtool.
@ 9Lukas5
Hey, just for clarification - I thought it was never a good idea to use the option
"format system" in the "partion tools" sub menu of xrecovery?
Doing this will erase everything - including xrecovery itself [self destruct] and therefore the user would not have any option except complete reflash if anything were to go wrong with the subsequent install.... ?
Correct me if I am wrong.
Edit: if this is what you meant by "wipe system" in OP !
nadiros said:
@ 9Lukas5
Hey, just for clarification - I thought it was never a good idea to use the option
"format system" in the "partion tools" sub menu of xrecovery?
Doing this will erase everything - including xrecovery itself [self destruct] and therefore the user would not have any option except complete reflash if anything were to go wrong with the subsequent install.... ?
Correct me if I am wrong.
Edit: if this is what you meant by "wipe system" in OP !
Click to expand...
Click to collapse
Yes i ment this.............maybe you're right, cause it will be formatted by installing the rom, too.........hm..will correct op.
Edit: I made it that way always, and had never problems, so i haven't thought about it.
no its COMPLETELY fine to format system AS LONG AS, you flash the rom RIGHT AFTER (DO NOT REBOOT THE PHONE BEFORE FLASHING ROM AS RECOVERY WILL HAVE BEEN ERASED).
When you format system, and install the rom, the rom has recovery built into it as well and it installs the recovery to your system partition when you flash the rom.
So as long as you dont reboot after format system and install the rom first, your fine.
Hello 9lukas5,
I thought I might mention that I've finally managed to fix my wlod but by installing setcpu on the earlier version of J's rom I was using, and setting it up to on boot run the processor at the usual 998 speed. Then I flashed the update.zip (from j's latest release, just formats the system) which didn't remove setcpu so the cpu was running at 998, this stopped all the random reboots and wlods.
I tried for a couple of weeks to use an update, trying so many different ways of stopping my phone being unusable as soon as I flashed the updates due to wlods.
Just though I'd mention it in this thread as it was on topic. Not everyones fix I'm sure, but helped me.
Cheers for all your support and help with installing the roms.
Sent from my X10 using XDA App
BULL3TPR00F said:
no its COMPLETELY fine to format system AS LONG AS, you flash the rom RIGHT AFTER (DO NOT REBOOT THE PHONE BEFORE FLASHING ROM AS RECOVERY WILL HAVE BEEN ERASED).
When you format system, and install the rom, the rom has recovery built into it as well and it installs the recovery to your system partition when you flash the rom.
So as long as you dont reboot after format system and install the rom first, your fine.
Click to expand...
Click to collapse
K - Right on, ty. Just so it's out there and people know ;-)
I believe the majority of WLODs are to due with the CPU constantly running at full speed.
I was getting a lot of WLODs with FreeXperia Kernel-10 on my ROM until I manually set the CPU governor to on demand.
Just go into Cyanogen Settings and change the CPU governor to on demand (it probably already is set to on demand, so change it to something else and then change it back to on demand).
After that my CPU was running at more than the max frequency and I haven't had many WLOD's (think I've had one since, a major improvement).
Erm not to be funny but their are no WLOD due to the changes J has made in his new version, regardless of how I flash it, no WLOD anymore... It has nothing to do with the way you flash the rom that caused this...
Hi guys,
I have follow ALL step from the step 1.
The phone boot, ask for the PIN code, then the page to change the language and then WLOD...
Do you think it come from the CPU frequency ?
I can't found the BTS kernel for this ROM.
Thank you for your help.
hmm....I shared it cause I hadn't any problems of WLODs yet on Cm7 since J019
Hello all,
the main trouble I had causing wlod, was definitely the clock speed. When I flashed the rom (about twenty times, different ways) I would not get enough time to configure any cpu settings, or any other settings, before my phone crashed and it would just start to bootloop with wlod.
I had to install setcpu on an older version of j's rom which didn't have overclock. Checked the box to apply settings on boot. So that when I flashed j's latest rom which is just the update of the system, all my apps were there (didn't bother wiping cache, data, etc) setcpu was still running on boot to keep the cpu set to 998.
Haven't had a single problem since, apart from low battery phone crash.
I tried so many different ways to flash before trying this, hope this helps someone.
Sent from my X10 using XDA App
Any body make a stock kernel image to flash to check sleep state vrs miniloader issue?????????
Worked a treat!! Thank you!
OK so.... NONE OF THE CUSTOM ROMS BOOT!!!??!??!?!??!! :'(
Device Summary:Carrier unlocked AT&T, UNLOCKED BL, with a 2.3.4 fruit cake flash -No webtop [current state] ( fruit cake flashes perfectly)
Followed all instructions supplied by the Dev's on their respective threads/sites.
Alien 2 Beta: Stuck at "DUAL CORE" screen
Alien 3 Beta: Stuck at "DUAL CORE" screen
CherryPi .3: Stuck at "DUAL CORE" screen
piCrust .3: Stuck at "DUAL CORE" screen
Have wiped all user data and cache via CWM, and even 'fastboot -w in other cases. Also have resorted to wipe Dalvik cache which shouldn't need be done.
*****EDIT*****: I'm also on the latest radio, and latest 'CWM' from tenefar via 'fastboot flash recovery'
Worth asking, though you've probably considered it:
Did you wait upwards of 10 minutes for each? New ROMs wipe app cache among other things, and the first boot takes quite a while. Definitely avoid RSD until you get your answer, though. G/L
-omni
Just have to ask because I have been stuck on the Dual Core screen before... Are you sure you are unlocked? You have the unlocked text in the upper left hand corner??
omni_angel7 said:
Worth asking, though you've probably considered it:
Did you wait upwards of 10 minutes for each? New ROMs wipe app cache among other things, and the first boot takes quite a while. Definitely avoid RSD until you get your answer, though. G/L
-omni
Click to expand...
Click to collapse
LOL, post usually note that the initial boot after flash is ridiculously long..... but I definitely waited >10 mins, almost an hour at longest on the Alien 3 beta flash just now, then I pulled batt and Fruit caked to 2.3.4.
(worried I might turn the soft-brick to a Hard-Brick if the battery died)
bamastang said:
Just have to ask because I have been stuck on the Dual Core screen before... Are you sure you are unlocked? You have the unlocked text in the upper left hand corner??
Click to expand...
Click to collapse
Yup still have the unlocked text...... :-/ FRUSTRATING
same thing happened to me with Ninja and Alien ...i waited 30+ mins..
so i just fruitcaked back to 2.3.4 ..
defnow said:
same thing happened to me with Ninja and Alien ...i waited 30+ mins..
so i just fruitcaked back to 2.3.4 ..
Click to expand...
Click to collapse
lol, it seems like no-one who has had this problem has posted till now? xD
But did you finally get into the launcher? or a complete Boot animation???
do you using correct kernel?
What did you use to unlock/root the device?
As in method/tools/etc.
EDIT-
http://forum.xda-developers.com/showthread.php?t=1182871
I used this tool personally, on Windows 7 x64, and it worked without a hitch.
If you read the thread carefully, all of the instructions are in the OP, but if you have any additional problems, you can find fixes/help throughout the thread (or just post of course).
Otherwise, should go off without a hitch!
Jean-DrEaD said:
do you using correct kernel?
Click to expand...
Click to collapse
Tried stock GB and Faux's kernel, but this wouldn't matter cause rom's flash their own kernel right? According to the progress scripts on CWM..
Jonestown said:
What did you use to unlock/root the device?
As in method/tools/etc.
EDIT-
http://forum.xda-developers.com/showthread.php?t=1182871
I used this tool personally, on Windows 7 x64, and it worked without a hitch.
If you read the thread carefully, all of the instructions are in the OP, but if you have any additional problems, you can find fixes/help throughout the thread (or just post of course).
Otherwise, should go off without a hitch!
Click to expand...
Click to collapse
I used the pudding/fastboot oem unlock method for x64 windows, the application put together should do the exact same thing but without the user needing to do the actual steps individually, but any ways will give it a go
weaz_da_smel said:
Tried stock GB and Faux's kernel, but this wouldn't matter cause rom's flash their own kernel right? According to the progress scripts on CWM..
Click to expand...
Click to collapse
flash kernel after flash the rom because that... try FR an ATT kernels...
weaz_da_smel said:
OK so.... NONE OF THE CUSTOM ROMS BOOT!!!??!??!?!??!! :'(
Device Summary:Carrier unlocked AT&T, UNLOCKED BL, with a 2.3.4 fruit cake flash -No webtop [current state] ( fruit cake flashes perfectly)
Followed all instructions supplied by the Dev's on their respective threads/sites.
Alien 2 Beta: Stuck at "DUAL CORE" screen
Alien 3 Beta: Stuck at "DUAL CORE" screen
CherryPi .3: Stuck at "DUAL CORE" screen
piCrust .3: Stuck at "DUAL CORE" screen
Have wiped all user data and cache via CWM, and even 'fastboot -w in other cases. Also have resorted to wipe Dalvik cache which shouldn't need be done.
*****EDIT*****: I'm also on the latest radio, and latest 'CWM' from tenefar via 'fastboot flash recovery'
Click to expand...
Click to collapse
start from scratch...go back to stock via RSD...
DO NOT DO THIS
if the fuse is blown YOU WILL BRICK
I would fruitcake back to 1.83 then flash to the rom you want, since its voda I would try a working international rom first.
DO NOT GO BACK VIA RSD YOU MIGHT HARD BRICK.
wipe all data in fastboot -> flash stock 2.3.4 via fastboot -> wipe all data again
Not trying to hi-jack the thread but I have the exact same problem so I thought I'd post here and give a detailed description of what I've done instead of creating another thread just like this one.
I unlocked the bootloader using the latest version of pudding
Then I downloaded fastboot and installed CWM
I downloaded the ROM of my choice meaning Alien 3 and the theme, and later when that didn't work Redpill 3. Also for the record I've tried installing with Alien 3 standalone and wait for boot up, and with both - neither worked and Redpill produces the same result.
Anyway back to the process
After downloading and putting the file of my choice on the external sd card I boot up into android recovery (flashed to CWM) I go to advanced and wipe the dalvik and then wipe the regular cache partition.
I reboot and immediately go to fastboot,
I do the fastboot -w command and then the fastboot reboot command and immediatley go back to CWM
I install using the external sd card and choose the zip of my liking.
It installs great and I then wipe the dalvik and cache again.
I reboot and I get stuck at the red M dual core screen.
The only way to get unstuck is to reflash with 183-sb-release.zip which is the fruitcake release I think. I got this from someone on a forum describing a similar problem for which this was the solution. However afterwards he was able to reinstall a custom rom without problems, while my problem remains.
*Edit - I have an AT&T phone
diviluxfloss said:
After downloading and putting the file of my choice on the external sd card I boot up into android recovery (flashed to CWM) I go to advanced and wipe the dalvik and then wipe the regular cache partition.
I reboot and immediately go to fastboot,
I do the fastboot -w command and then the fastboot reboot command and immediatley go back to CWM
I install using the external sd card and choose the zip of my liking.
It installs great and I then wipe the dalvik and cache again.
I reboot and I get stuck at the red M dual core screen.
Click to expand...
Click to collapse
To double check -> Are you using latest unlocked CWM from xda or rom managers one?
Also to double check -> you did Wipe data / Factory reset as well?
You should do all three Wipe options before and after flashing the rom -> wipe cache, wipe data / factory reset, wipe davik.
After that reboot and give it a couple of minutes to boot.
If that doesn't work, do a battery pull and try booting again.
Thank you for the swift reply
I have the latest CWM from XDA.
I have tried several enumerations including wipe cache, wipe dalvik and wipe data/factory reset.
I've also tried removing the battery.
Still no success :/
diviluxfloss said:
Thank you for the swift reply
I have the latest CWM from XDA.
I have tried several enumerations including wipe cache, wipe dalvik and wipe data/factory reset.
I've also tried removing the battery.
Still no success :/
Click to expand...
Click to collapse
Alright, then the second thing I would try is flashing one of the custom ROMs via fastboot:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
p.s. and if you don't have the latest radio,-
moto-fastboot flash radio radio.img
Again thank you for the swift reply
Is flashing with fastboot dangerous in comparison to cwm? Ie. is there a larger risk of inherent soft/hard-bricking?
Also here comes a noob question so I hope you'll be lenient with me, but what is a radio per say and how will it help during the flashing of a rom?
Thank you I appreciate the help so far!
diviluxfloss said:
Again thank you for the swift reply
Is flashing with fastboot dangerous in comparison to cwm? Ie. is there a larger risk of inherent soft/hard-bricking?
Also here comes a noob question so I hope you'll be lenient with me, but what is a radio per say and how will it help during the flashing of a rom?
Thank you I appreciate the help so far!
Click to expand...
Click to collapse
The only truly dangerous method of flashing is SBF (RSDlite). CWM and fastboot are safe.
If you unlocked the bootloader youserlf, you already know what fastboot looks like. Often, fastboot helps where CWM fails.
Before using fastboot, make sure you have phone drivers installed, also make sure you have "moto-fastboot" version and not "fastboot", as the latter can't flash large files, e.g. - system.img.
Phone drivers for Windows x64 can be downloaded here (though your probably have them already if you unlocked the BL) -
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
Download moto-fastboot for your operating system here (if you don't have it already, obviously) -
http://forum.xda-developers.com/showthread.php?t=1138092
"Radio" is software that handles cellular connection, mobile data, etc.
I've read that there could be a boot problem if wrong radio is used.
Besides, the latest 2.3.4 radio includes many bug fixes and better mobile data speeds.
You can check if you have the latest one under "About Phone" -> "Baseband version". Latest one for ATT is N_01.77.30P.
It can be downloaded here - http://bandbinnovations.com/xda/gingerbread/Gingerbread-4.5.91.zip
(The archive contains all stock 2.3.4 partitions, but you can simply extract radio.img and flash it separately via fastboot)
Cheers.
Great
I'll try flashing the radio and then the files as mentioned in your previous post. A problem though is that when I look through the zip files I only find a boot.img file for the custom rom.
Where is the system.img file located and if I simply install these through moto-fastboot (thanks for the heads up btw as I only had fastboot) what happens to the smaller files located on the zip which won't be associated to the img files?
*Edit I compared these to the fruitcake zip and in the custom roms I have a folder called system which I believe contains all the info while the fruitcake files have an img. I'm guessing not compatible? Or can I simply make an img file with the system folder and flash thusly?
My phone's rooted. I've read almost every thread trying to resolve my problem. I restored it to stock firmware, tried overclocking it and still no luck of resolving my screen from blacking out and leaving just the buttons lighting up. Like the other thread, i just pull out my battery to fix things but it's quite irritating to do that everytime. It happens almost 5 times a day at a random time. Can someone please help me resolve this? I'm not using any custom rom or anything.
which ROM u r using??
Optimus one
CM 6.5.8
Press THANKS if I helped...
loserkid520 said:
My phone's rooted. I've read almost every thread trying to resolve my problem. I restored it to stock firmware, tried overclocking it and still no luck of resolving my screen from blacking out and leaving just the buttons lighting up. Like the other thread, i just pull out my battery to fix things but it's quite irritating to do that everytime. It happens almost 5 times a day at a random time. Can someone please help me resolve this? I'm not using any custom rom or anything.
Click to expand...
Click to collapse
I think this is only a software problem; try flashing miks rom if you want stability, or adfad's for new features. I have not got this bug on nightly6 but the rom isnt fully working
I'm just using a stock firmware from a thread here on how to restore to stock firmware without kdz update. I'm a noob to android so i don't know how to put any ROM yet.
If you use stockROM Froyo (2.2.X) your problem could be solve with an update to Gingerbread (2.3.3). Other causes are poor quality microsd or modified kernel (i.e. Unofficial CM)
Enviado desde mi LG-P500h usando Tapatalk
loserkid520 said:
I'm a noob to android so i don't know how to put any ROM yet.
Click to expand...
Click to collapse
For stockROM I use KDZ Firmware Updater, for custom ROMs you need root and install a custom recovery, then, you can install any custom ROM.
Enviado desde mi LG-P500h usando Tapatalk
Rores said:
I think this is only a software problem; try flashing miks rom if you want stability, or adfad's for new features. I have not got this bug on nightly6 but the rom isnt fully working
Click to expand...
Click to collapse
Can you get me a link on those roms or tutorial? I'm still a noob at android.
loserkid520 said:
Can you get me a link on those roms or tutorial? I'm still a noob at android.
Click to expand...
Click to collapse
As your phone is rooted..
1. install ROM manager from market and install recovery from it... make sure you select the correct phone
2. DO NOT CHOOSE TO BOOT INTO RECOVERY VIA ROM MANAGER OR YOUR PHONE WILL GET STUCK...
3. If you are on gingerbread then you are using new baseband otherwise on froyo its old..
4. go to optimus one development section and choose the stable ROM according to your baseband..
5 download it and place it on sd card
6. Also download GAAPS and place it on sd card
7. turn off the phone and boot into recovery by holding home+ volume down+ power and hold then until you see recovery
8. use volume keys to navigate in recovery, back to go back and menu key to make selection
9. now wipe data/ factory reset,
wipe cache, wipe dalvik cache and wipe battery stats..(last two are under advanced options)
also go to mount and storage and format system if you want perfectly clean install
10. now choose install zip from sd card and choose the ROM you downloaded... let it complete and after that reboot phone
11. first boot will take time.. don't panic.. after it is started again boot into recovery and install GAAPS to get market and other google apps.. reboot and you are ready to go..
NOTE:- NEVER FLASH 2 ZIPS WITHOUT REBOOTING
NEVER DO FACTORY RESET FROM PHONE WHILE USING CUSTOM ROM.. DO IT FROM RECOVERY..
I hope this will do..
Optimus one
CM 6.5.8
Press THANKS if I helped...
fundoozzz said:
As your phone is rooted..
1. install ROM manager from market and install recovery from it... make sure you select the correct phone
2. DO NOT CHOOSE TO BOOT INTO RECOVERY VIA ROM MANAGER OR YOUR PHONE WILL GET STUCK...
3. If you are on gingerbread then you are using new baseband otherwise on froyo its old..
4. go to optimus one development section and choose the stable ROM according to your baseband..
5 download it and place it on sd card
6. Also download GAAPS and place it on sd card
7. turn off the phone and boot into recovery by holding home+ volume down+ power and hold then until you see recovery
8. use volume keys to navigate in recovery, back to go back and menu key to make selection
9. now wipe data/ factory reset,
wipe cache, wipe dalvik cache and wipe battery stats..(last two are under advanced options)
also go to mount and storage and format system if you want perfectly clean install
10. now choose install zip from sd card and choose the ROM you downloaded... let it complete and after that reboot phone
11. first boot will take time.. don't panic.. after it is started again boot into recovery and install GAAPS to get market and other google apps.. reboot and you are ready to go..
NOTE:- NEVER FLASH 2 ZIPS WITHOUT REBOOTING
NEVER DO FACTORY RESET FROM PHONE WHILE USING CUSTOM ROM.. DO IT FROM RECOVERY..
I hope this will do..
Optimus one
CM 6.5.8
Press THANKS if I helped...
Click to expand...
Click to collapse
I'm going to try this. I just flashed my phone again to stock firmware this time a european version. If my screen still goes black, i'll try this out.
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
New radios might help. Are you wiping EVERYTHING before flashing?
We're comin from a pure power source.
How can I flash this new radio? Just install .zip of the file from recovery, correct?
I do "factory reset" on the twrp 2.0 recovery before I install any rom
ninten5 said:
I do "factory reset" on the twrp 2.0 recovery before I install any rom
Click to expand...
Click to collapse
I'm using twrp2 and I do
Factory reset
Wipe cache
Wipe dalvic cache
Wipe system
Factory reset (again)
Flash Rom
Reboot system.
And i never have any bootloops or stuck in HTC white screen or any issues.
Sent From My Optimized R3Dimensions
Yea. Factory reset isn't enough. I encountered that issue when doin restores on me og evo. I had to wipe cache and dalvik to get it to work.
We're comin from a pure power source.
Use cwm older 4 version as recovery.
Fastboot boot recovery.img. make sure you have a copy of it in your adb folder.
Wipe everything and flash rom
OK ill try that.
What about backup and restores, my nAndroid backups don't work
ninten5 said:
So I rooted with HTC method with hboot 1.5.
I have lots of roms on it to check the speed, battery life, features of them but there has been a problem with many ROMs (MIUI, ICS alpha, Mik, Infected, Warm) all will act "wonky" after couple of days of using the rom. They will show red lines, slow downs, temporary freezes, battery would drop by 1% every 30 sec.
So, the usual thing to do is restart and BAM! They rom's logo shows up and it freezes there. Do I need a new radio update or RUU or something?
Never encountered anything close and I've been tweaking phones since the Moto Q days!
Click to expand...
Click to collapse
Either one of two things:
your phone is defective
stop using so many apps for stuff like checking on system statuses. Just install a ROM fresh and leave it for a week with just your base essential apps like email and stuff. If the problem doesnt arise you know all your crap is causing it.
A radio update isnt going to do anything for a system issue as it is just your signal and stuff that the radio firmware would affect.
Sounds like the flash went bad due to not a full wipe or boot.img.
Twrp 2.0 is known to have its own issues.
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
ninten5 said:
Update: So I have infected rom installed for a couple of days, installed it using the method mentioned with wiping cache, dalvik cache, system, battery stats and guess WHAT?
It happend again, I would lose touch screen and touch button control, only way to regain control was to close screen by hitting power and waiting a few seconds and pressing it again to open the screen. Got fed up after a while and decided a battery pull, froze of Infected LOGO
Is it the way I flash the rom that is causing issues? I install the zip first with cwm 2.0 then I connect to computer and type "fastboot boot boot.img" to push the boot.img for that rom.
Click to expand...
Click to collapse
Do this man
Get cwm 4.0 version ok now flash that then leave a copy of it in your adb folder where adb is...
Now make sure debug is on
adb reboot bootloader
fastboot boot recovery.img
Then wipe everything but not your SD card
and flash rom works this way just like the S off users use. You don't have to use flash gui or pull boot img..
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
ninten5 said:
So I took out twrp 2.0 recovery and put clockworkmod 5.0
I don't know why but I cant boot into the recovery without connecting my phone and pushing the .img through fastboot
Well at least two things are solved, after a restart the rom doesnt freeze and I dont have to fastboot boot.img for installing a new rom.
Click to expand...
Click to collapse
cwm 4 is better for this phone dude. he said 4 not 5.
Hi,
First I apologise for not having made a back up of my filesystem, I had grown overconfident from previous successful projects ;-/
I have unlocked the phone and installed TWRP recovery. I then used SUPERSU to root the phone under TWRP. After SUPERSU the phone did not boot, it stayed on the WARNING BOOTLOADER UNLOCKED splash for over an hour and did not boot after a reset.
I read through the forums and looked for a kernel to try as I had read that the OS may be damaged, and I wanted to flash a ROM in any case. I read to clean the boot partition before flashing so I did this. The kernel I tried was Squid. This made the phone display "fall through from normal boot mode". So I tried Cyanogen Mod 14, which put the phone on a very rapid bootloop cycle (about every 15 secs), then tried Squid Kernel R22B which put the phone on a long (about 8 minute) bootloop cycle.
Not sure what else I can do. I don't want to give up on the phone as it still mostly works (it has a bootloader, recovery and a file system). I have tried to find a stock ROM to install but proving difficult to track down - links seem to be down)
I apologise if I have got any technical terms wrong. I hope you can help!
Thanks,
Caroline
Caroline300 said:
Hi,
First I apologise for not having made a back up of my filesystem, I had grown overconfident from previous successful projects ;-/
I have unlocked the phone and installed TWRP recovery. I then used SUPERSU to root the phone under TWRP. After SUPERSU the phone did not boot, it stayed on the WARNING BOOTLOADER UNLOCKED splash for over an hour and did not boot after a reset.
I read through the forums and looked for a kernel to try as I had read that the OS may be damaged, and I wanted to flash a ROM in any case. I read to clean the boot partition before flashing so I did this. The kernel I tried was Squid. This made the phone display "fall through from normal boot mode". So I tried Cyanogen Mod 14, which put the phone on a very rapid bootloop cycle (about every 15 secs), then tried Squid Kernel R22B which put the phone on a long (about 8 minute) bootloop cycle.
Not sure what else I can do. I don't want to give up on the phone as it still mostly works (it has a bootloader, recovery and a file system). I have tried to find a stock ROM to install but proving difficult to track down - links seem to be down)
I apologise if I have got any technical terms wrong. I hope you can help!
Thanks,
Caroline
Click to expand...
Click to collapse
Assuming you've the Lineage 14 zip in your internal storage or micro sd,. Enter TWRP, select wipe, advanced wipe, check system data cache and dalvik, swipe to wipe. Now you've clean wiped your phone.
Then go "install", select the Lineage zip and flash it.
Hi DroidFreak32, thank you for your help. The phone is now booting for the first time since it's "adventure".
Hi,
Unfortunately the phone is still in the boot logo screen. It stayed on the Lineage logo for 2 hours. I have powered off and rebooted once more, and it is still in the boot logo screen now (1 hour later). I'll wipe and install again and post an update.
Hi,
I reflashed Lineage, same problem. I did notice that each time I installed a zip file, SUPERSU asked me to install it prior to reboot to root the phone and I have always hit Yes. On the final flash, I powered off the phone when it prompted me to install SUPERSU, and the phone booted normally. Very nice design on the mod, I like the way the apps are displayed alphabetically. Good work Lineage Team!