Hi all.
I need some help with the neutrino rom. I used to be on darkside ROM previously and it worked fine. Decided to move over to neutrino.
The problem im having is that everytime it boots, the boot animation keeps looping. The screen shows Neutrino ROM ..system loading and it starts to flash the same thing over and over. Have tried battery pull too.
Dalvik cache and cache have been wiped. Tried with 2.2GT and GT+.
Any help will be greatly appreciated.
Thank you for looking.
Try full system format and reapply the ROM. That what helped me when I jumped from the stock 2.3.4 directly to Neutrino 2.2 (CM7 based).
It started to behave bad so I made a full system clean up, reflashed and cleaned again (probably for nothing). Now stable (GT, not GT+ which I didn't try).
P.S. Backup better to be actual...
sms2000 said:
Try full system format and reapply the ROM. That what helped me when I jumped from the stock 2.3.4 directly to Neutrino 2.2 (CM7 based).
It started to behave bad so I made a full system clean up, reflashed and cleaned again (probably for nothing). Now stable (GT, not GT+ which I didn't try).
P.S. Backup better to be actual...
Click to expand...
Click to collapse
Thanks for the reply man.
I just tried that now and got the same results. Did a full wipe of the onboard memory and got the same loop again. The only exception is that the indicator light is blinking light blue.
Any suggestion?
Try "fastboot" wiping all the partitions, like so:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
There is a batch script that will do this for you also:
http://forum.xda-developers.com/showthread.php?t=1421261
dunnoX said:
Thanks for the reply man.
I just tried that now and got the same results. Did a full wipe of the onboard memory and got the same loop again. The only exception is that the indicator light is blinking light blue.
Any suggestion?
Click to expand...
Click to collapse
This happens sometimes, I have no idea why. Try a completely clean reflash, by erasing via fastboot and then reinstalling the ROM.
Also, store the ROM onto the internal SD and install from there.
Notorious544d said:
Also, store the ROM onto the internal SD and install from there.
Click to expand...
Click to collapse
Yeah, that's mandatory.
Related
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?
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.
This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Taz3rburned said:
This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Click to expand...
Click to collapse
Have u tried these fastboot commands
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
Okay, I've done that and then I flashed CWM Recovery through fastboot. I then booted into CWM and flashed the jokersax's CM9 ROM and rebooted. What I still get is:
No OS detected, going to RSD mode in 5 seconds
Press a key to stop count down
Available Modes are:
1 RSD
2 Fastboot
3 NvFlash
etc. etc.
It isn't detecting an OS still, and I don't get a boot icon just that menu. What would you suggest?
I'm thinking of trying this: http://forum.xda-developers.com/showthread.php?t=1421522
Taz3rburned said:
This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Click to expand...
Click to collapse
1. Re: CWM wipe and spazzed out touch screen: Sounds like you erased your PDS partition. If you made a back up, flash it. Otherwise search for a thread titled PDS Partition Fix (or something similar) here in the Q&A section for an alternative fix.
2. I don't recall if doing the PDS fix will also fix the missing boot logo. If not, you can find a stock replacement in the Themes section. You're looking for logo.bin.
That fixed it, thanks! I did a full wipe of those partitions then restored from my CWM restore. That didn't fix the screen but I tried that fix you suggested and everything is perfect now. Thanks for the help.
Figured out that I posted in the wrong section(mods please remove that thread)
Ok guys..... newbie here .... literally I'm new to Boot unlocking, root, Flashing etc.
Anyway I have followed this forum for so long that I decided to take plunge yesterday and get my hands dirty.
Here is what I did:
Unlock bootloader, root and install recovery on my Atrix 4G. Atrix was @ 2.3.4 and 4.5.91 during unlocking & root(rooting & unlock from this thread:http://forum.xda-developers.com/showthread.php?t=1182871)
Rebooted the phone and everything seems to be in place. Atrix loaded like the way I bought it 7 months back. No problem until now.
Also created a restore folder on my external SD. Worked fine and was successful in creating backup with time stamp
Now here are my steps and subsequent issues that I'm facing:
1. Downloaded CM9 zip file from this thread(http://forum.xda-developers.com/showthread.php?t=1500535) along with Gapps to my external SD
2.Entered recovery mode during bootup and tried to flash CM9 and Gapps. Flashing seem to have gone well and completed (note I did not do clear data, clear cache or clear dalvik cache under advanced options being a newbie)
3. Reboot the phone and can only see red Moto logo and unlocked on top. Left for about 5 minutes and nothing happened.
4.Did a battery pull and entered recovery mode. wiped data, cache & cleared dalvik cache
5.Went to Install zip from sdcard option and tried to reflash CM9. Flashing seems to have gone well and completed
6. Reboot phone and again can only see Moto Red logo with unlock on top and nothing more.
7.Battery pull followed by recovery. But This time I tried to restore from my external SD. also wiped data, cache & dalvik cache
8.Restore took about 3 minutes and completed.
9.Reboot the phone. Now the phone boots and goes to Rethink possible screen and get sstuck.
10. Left it for 1 hr....nothing.
11.tried steps 7-9 again and still stuck in "Rethink possible" screen during boot.
12.Entered Recovery mode to try stable Nutrino ROM, same problem (stuck @ M logo screen which says unlocked)
13. Cleared data, cache and tried restore and now my phone boots up with flashing M screen.
What did I do wrong? Did I soft brick the phone? I can still enter recovery mode and read my internal and external SD and can see all files. i hope I didn't brick my phone doing this. If I did, I would regret!
Here are my options:
1.I know there is a way to hide 'unlock' during boot up (if someone can point to it obviously). Hide the 'unlock' and return the phone to ATT and tell them that phone would not boot after 2.3.6 update and get a refurbished one
Please let me know what your thoughts are. I'm currently crapping on my pants
Hmm... I would "fastboot -w", wipe cache/dalvik/data again, and try restoring your nandroid backup. (Or was that your Neutrino attempt?)
OR, do the wipe again and flash a 2.3.6 fruitcake to see if it boots normally. Just to see if there's some issue with your rom download or if it's really the phone.
The only way to hide the unlocked text is to flash an SBF using RSD Lite, which runs the risk of bricking your phone if you flash the wrong version.
Download a Fruitcake from here > http://forum.xda-developers.com/showthread.php?t=1163009 and put it on your sdcard.
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
reboot
Let your phone sit until it boots up completely, then let it sit for another 10 minutes. Remember, your phone can take 15 minutes to boot up the first time after flashing a ROM, especially if a new kernel was flashed with it.
Yeah I would try a fast boot wipe the whole shabang fastboot -w and then fastboot erase preinstall
Then also erase boot
System
Cache
Userdata
Web top
Then go into cwm and do the wipes you've been doing then flash the rom
Sent from my MB860 using XDA App
jonnyboyC13 said:
Yeah I would try a fast boot wipe the whole shabang fastboot -w and then fastboot erase preinstall
Then also erase boot
System
Cache
Userdata
Web top
Then go into cwm and do the wipes you've been doing then flash the rom
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Think I covered all that already, and fastboot -w just wipes cache and userdata anyway, so no need to do a fastboot -w. What I have in the post before you is the cleanest way to wipe and flash a new ROM.
Thank you....I haven't tried the soft brick fix yet.
But from reading one other thread which had similar problem, it looks like after installing romracer's CWM, things got fixed.
http://forum.xda-developers.com/showthread.php?t=1527453
Will be trying this tomorrow.
Hmm.. this thread seems to be dead..
This treads seems to be dead... I was hoping to get some help with some soft bricked atrix HD... any suggestions?
Pharawer said:
This treads seems to be dead... I was hoping to get some help with some soft bricked atrix HD... any suggestions?
Click to expand...
Click to collapse
This is the Atrix 4G board, not Atrix HD.
ravilov said:
This is the Atrix 4G board, not Atrix HD.
Click to expand...
Click to collapse
Yeah i know, but what i want to know if this method is compatible with a soft bricked atrix HD becaused there isn't much info about this particular phone on the web.
Pharawer said:
Yeah i know, but what i want to know if this method is compatible with a soft bricked atrix HD becaused there isn't much info about this particular phone on the web.
Click to expand...
Click to collapse
No. Totally unreleated hardware. There's an Atrix HD section you can ask in over here, which you clearly already knew about because you've already asked your question in it. Why spam over here? I'm sure somebody who actually knows the device you have will answer your question, but this is not the place to ask it.
Edit: But feel free to flash an Atrix SBF/Fruitcake on your Atrix HD if you'd like to actually brick it.
Pharawer said:
Yeah i know, but what i want to know if this method is compatible with a soft bricked atrix HD becaused there isn't much info about this particular phone on the web.
Click to expand...
Click to collapse
You should take your question back to the HD Thread, a discussion at this one is TOTALLY off topic for this thread due to the entire device being different.
Thanks!
P.S. Closing thread
so ive had a bunch of issues with this, but now everything seems to be running smooth, except my wifi. i cant get it to turn on after wiping caches, re flashing both rom and kernal, everything. i dont know what to do next, plz help someone
ixi_devo_ixi said:
so ive had a bunch of issues with this, but now everything seems to be running smooth, except my wifi. i cant get it to turn on after wiping caches, re flashing both rom and kernal, everything. i dont know what to do next, plz help someone
Click to expand...
Click to collapse
I flashed the new Viper 2.0 and I am having the same problem. I came from Elegancia ROM, flashed the kernel for viper then did factory reset, cache and dalvik wipe for 2.0 independently before full wiping in the ROM. Everything else seemed to work but I remember at the set up screen there wasn't an option to install Wi-Fi.
I tried flashing the ROM again on top of the newly installed viper 2.0 but still the Wi-Fi just says it's turning on.
Going to start over again with full wipe to see if it works this time.
Edit: shouldn't have said everything else worked because didn't do full test. Just got install failed message and next screen said install successful where the reboot system, wipe buttons are. Does boot and go through motions but no radio it seems. MD5 checked out for both kernel and ROM. Starting over with new downloads.
effezie said:
I flashed the new Viper 2.0 and I am having the same problem. I came from Elegancia ROM, flashed the kernel for viper then did factory reset, cache and dalvik wipe for 2.0 independently before full wiping in the ROM. Everything else seemed to work but I remember at the set up screen there wasn't an option to install Wi-Fi.
I tried flashing the ROM again on top of the newly installed viper 2.0 but still the Wi-Fi just says it's turning on.
Going to start over again with full wipe to see if it works this time.
Edit: shouldn't have said everything else worked because didn't do full test. Just got install failed message and next screen said install successful where the reboot system, wipe buttons are. Does boot and go through motions but no radio it seems. MD5 checked out for both kernel and ROM. Starting over with new downloads.
Click to expand...
Click to collapse
Ok so here was my soultion after msgn turge, the kernal in the ZIP folder is ****ed up, u need to go to post 2 in the thread (nice bold red note cause of me haha) get that kernal. Now when I went to flash, I usually use fastboot flash bootimg boot.img
For what ever reason I got many errors until I did full wipe, caches and all, and before I let it try to boot I caught it into boot loader .
To flash it sucessful I had to use fastboot flash boot boot.img. very subtle difference from the other one... But made all the difference.
Full working here, clean smooth. WiFi on.
ixi_devo_ixi said:
Ok so here was my soultion after msgn turge, the kernal in the ZIP folder is ****ed up, u need to go to post 2 in the thread (nice bold red note cause of me haha) get that kernal. Now when I went to flash, I usually use fastboot flash bootimg boot.img
For what ever reason I got many errors until I did full wipe, caches and all, and before I let it try to boot I caught it into boot loader .
To flash it sucessful I had to use fastboot flash boot boot.img. very subtle difference from the other one... But made all the difference.
Full working here, clean smooth. WiFi on.
Click to expand...
Click to collapse
My problem was how I flashed the kernel. As soon as I started over I saw what was wrong with my preperation. Glad your up and running.