[Q] Reboot Loop - Dual Core Screen - Help Needed - Atrix 4G General

Hello everyone,
As a new member I would like to extend my sincere thanks to everyone who posts here and that makes working with my Atrix possible. Please forgive any misuse of terms etc. As I said I am new and I truly would like to learn to flash roms and recover easily etc, but I am overwhelmed right now and just want my phone to work again - with any rom!
Last night I unlocked my phone (rooted ATT 4.5.140 - 2.3.6 OTA) using unlock v4.2 and everything went smoothly. I downloaded CWM manager and Superuser and then thought I was creating a backup. I then tried to flash to CM7 and began having what I assume are boot loop issues: The CM7 splash screen with the circling arrow would repeat several times and then I would see the skateboard guy move across the screen several times and then the phone would just shut down. From here I tried to go to Android Restore and restore from the back up but that wouldn't work. I next downloaded Blue 5.0.2.7-atrix5 (because the writing on my screen is blue), moved it to my external SD card via PC, booted phone to Android Restore, then ran the zip. Same issue. Lastly I tried to restore to an older stock ROM (ATT 4.5.140 - 2.3.6). Now I am stuck in a "boot loop" that gets to the dual core screen to appear for a second or two, then repeats itself. I also tried to flash using moto-fastboot with the same results. I can still get to the restore screens and fastboot so I don't think I am dealing with a brick situation.
I am hoping someone can help me get around this. I have read so many 85+ page threads that my head is spinning and I am really no closer to resolving on my own.
Thanks in advance for everyone's patience and any assistance rendered!
Cheers!
Chris

Did you do proper wipes? Try fastboot erase system, fastboot erase cache etc etc. You can search the forums for the various fastboot erase commands. You definitely aren't hardbricked yet
Sent from my MB860 using xda app-developers app

Hey Aaron
I know I did wipes from the Android Recovery screens - I'll try from fastboot and post back. Thanks for answering!
Chris

bert26 said:
Hey Aaron
I know I did wipes from the Android Recovery screens - I'll try from fastboot and post back. Thanks for answering!
Chris
Click to expand...
Click to collapse
What version of cwm recovery are you using? Make sure you have it up-to-date. Older versions don't wipe properly.
Sent from my MB860 using xda premium

I've executed the following:
boot to recovery
Wipe Dalvik
wipe cache
factory reset/data
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
flash ROM in recovery
wipe Dalvik
wipe cache
reboot
The device has been on the dual core screen (steady - not just for a couple of seconds at a time) for over 5 minutes. I will give it a few more and then pop the battery.
As far as I know I am running CWM 5.0.0.8 although I don't know how to be certain. It was the first one that came up in the play store.

but it's not giving you any errors on the logo/bios screen? like Fail to boot 0x00010 something?
i'm out of ideas beyond trying a different rom. you could try the wipe process again and test a different rom like nottachtrix. i'd wait for someone else to post who might have more ideas

No errors at all, just stuck on the dual core screen, even after battery removal. I am searching other threads for this specific issue now. Feels like I'm making progress since it's at least not looping. Thanks again!

Wow! Looks like I just caught a break. Out of desperation I tried to re-flash CM7 and whaddya know! The thing booted right up! I can only assume it was due to the full on wiping that was suggested.
Thanks so much for pointing me in the right direction and for taking the time to help a n00b.
Cheers!

Related

[Q] flashing problems, stuck on the same rom(Solved!)

Hey Guys, I first tried searching to see if anyone else had the issue but i couldnt find any related threads. I am currently running either turl's or joxersax11's CM9 rom. The problem is when i try to install a different rom (take gingerblur for example). Ive tried installing new roms by both rom manager and directly through CWM (and I have been clearing my data/caches/dalvik) , but upon first boot after the flash, the loading screen is still the CM9 animation (the one with the rainbow tiles flpping over) and when Android loads up, I'm still on CM9. What am I doing wrong? Is there a better way to wipe my phone or flashing roms?
Thanks for your help
Erase system and boot using fastboot commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata
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
That'll do it!
thanks guys, im waiting for my battery to charge to get into fastboot. How often should i erase these things in fastboot? Every flash? Or just whenever something is broken?
Ubers said:
thanks guys, im waiting for my battery to charge to get into fastboot. How often should i erase these things in fastboot? Every flash? Or just whenever something is broken?
Click to expand...
Click to collapse
When ever you flash a new rom. If you're just updating a never version of the same rom, usually you don't have to fastboot wipe, unless you have a problem.
Long story short... I soft bricked my phone. My phone won't boot past the Motorola dual core screen. I can boot to cwm, fastboot, rsd. The gingerblur rom is flashable from inside cwm, but it doesn't want to boot to boot after flashing. How do I get out of this mess? I'm not very familiar with flashboot or RSS, or sbf files but I'm sure I could use them if I had baby step instructions.
Ubers said:
Long story short... I soft bricked my phone. My phone won't boot past the Motorola dual core screen. I can boot to cwm, fastboot, rsd. The gingerblur rom is flashable from inside cwm, but it doesn't want to boot to boot after flashing. How do I get out of this mess? I'm not very familiar with flashboot or RSS, or sbf files but I'm sure I could use them if I had baby step instructions.
Click to expand...
Click to collapse
Gingerblur... Jesus..... Answers needed below:
- Is your bootloader unlocked?
- What/who's recovery are you using?
- What firmware and/or Android version were you running?
- Do you have a micro/ext. sd card?
- Is your bootloader unlocked?
Yes, when I turn on the phone, unlocked appears in the top left corner
- What/who's recovery are you using?
This is the software I get into when I select "android recovery" from the boot menu right? I'm pretty positive its an up to date version of clockworkmod
- What firmware and/or Android version were you running?
Up until a few days ago I had stock 2.3 gingerbread courtesy of at&t. First i tried jokersax cm9 and then i tried turls cm9 most recently before this brick
- Do you have a micro/ext. sd card?
Nope. And to make matters worse I don't believe the SD slot works
Inside your noob guide there is a section titled
WHAT DO I DO IF MY DEVICE WILL NOT FULLY BOOT??? (i.e. Boot Loop or Soft Brick):
This is my predicament right? There is a subsection:
c) If you can boot into fastboot, you can fastboot flash the "stock" 2.3.4 Gingerbread .img/system files by following the instructions on this page:
http://forum.xda-developers.com/show....php?t=1163342
*Note: The .img files to install via fastboot are located under "Download Gingerbread Stock Images" on the download page
Should I try this method?
Ubers said:
- Is your bootloader unlocked?
Yes, when I turn on the phone, unlocked appears in the top left corner
- What/who's recovery are you using?
This is the software I get into when I select "android recovery" from the boot menu right? I'm pretty positive its an up to date version of clockworkmod
- What firmware and/or Android version were you running?
Up until a few days ago I had stock 2.3 gingerbread courtesy of at&t. First i tried jokersax cm9 and then i tried turls cm9 most recently before this brick
- Do you have a micro/ext. sd card?
Nope. And to make matters worse I don't believe the SD slot works
Inside your noob guide there is a section titled
WHAT DO I DO IF MY DEVICE WILL NOT FULLY BOOT??? (i.e. Boot Loop or Soft Brick):
This is my predicament right? There is a subsection:
c) If you can boot into fastboot, you can fastboot flash the "stock" 2.3.4 Gingerbread .img/system files by following the instructions on this page:
http://forum.xda-developers.com/show....php?t=1163342
*Note: The .img files to install via fastboot are located under "Download Gingerbread Stock Images" on the download page
Should I try this method?
Click to expand...
Click to collapse
Try wiping data first in CWM & see if it will boot.
The reason you can't get it to wok with Gingerblur, is b/c that's was for froyo... you might as well delete that .zip.
If you had a micro SD card, you could just stick a fruitcake on it and then flash that.
You might try fastboot installing Rom Racers recovery (see his OP) then installing whatever CM7 or 9 Rom you were trying to install.
As a last resort, you could try fastboot installing that .img file or sbf flashing 4.5.91 sbf... whatever you do don't flash or install a earlier version of the firmware like 1.2.6 or 1.8.3, or you'll hard brick!!! If you go this way, you'll most likely have to unlock your bootloader again.
Sent from my CM7 Atrix 4G
Well i tried it and im back up and running again. Thank goodness for your comprehensive noob guide! It took me a while to track down moto-fastboot but when i found it, it was all smooth sailing!
thanks again
Ubers said:
Well i tried it and im back up and running again. Thank goodness for your comprehensive noob guide! It took me a while to track down moto-fastboot but when i found it, it was all smooth sailing!
thanks again
Click to expand...
Click to collapse
Good to hear!
Sent from my CM7 Atrix 4G
CaelanT said:
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
That'll do it!
Click to expand...
Click to collapse
I'm not an expert at this but doesn't "fastboot erase boot/system/etc" delete the clockworkmod recovery ? I have flashed cm7 roms before with only wiping the data/cache/dalvik and never had a problem, why is it different now when flashing cm9 ?
Thanks in advanced.

[Q] Morrisoft Gen Always Stuck

Hi. I believe the Morrisoft Gen thread would be better than a new thread, but I can't post there since I'm a new user.
I tried installing the MorrisoftGen v0.7 now, and it stuck in the Motorola screen forever, and not only in the fir reboot. I pulled out the battery at least 5 times, waited several minutes, and it simply doesn't move.
I followed this steps:
moto-fastboot erase system
moto-fastboot erase userdata
moto-fastboot erase cache
moto-fastboot erase preinstall
moto-fastboot -w
moto-fastboot reboot
Apply .zip from sdcard
And then reboot. Then waited a bit in the stuck screen (as said in the main thread), then pulled out the battery, and turned it on again. Nothing. I did enter recovery one more time just to reboot using this option, and nothing. Pulled out the battery two more times, and still.
I just reinstalled the old pieCrust rom I was using, just to have a working phone tonight. At least I now the phone is working, but what I did wrong that MorrisoftGen didn't work?
Thank you very much.
Now I tried to flash Neutrino 2.5 GT, and the same problem happened. Just stuck at the Motorola Screen. Came back to pieCrust 0.7 again, and it works.
You probably need to install a new recovery. Download rom manager from the market and flash that recovery. Or look in the dev section for the atrix specific one and install via fastboot.
Sent from my MB860 using Tapatalk
How long do you wait when you reboot after flashing?
Some ROM's take a loooonnnngggggg time.............10-15 minutes to reboot first time after flashing, especially if a new kernel is included in the ROM.
Maybe you just aren't waiting long enough.
I waited more than 20 minutes one time, and both these ROMs were supposed to boot fast.
But I solved that updating my CWM Recovery, that was a bit old. The first boot was a lot buggy, with all the processes closing, but a new cache wipe solved the problem.
Thank you all for your help!

[Q] phone won't boot....please help!

Last night I was using my Nexus 4 and it wouldn't connect to any web pages so I thought I'd reboot to see if that fixed it. I powered off then back on and it won't get past the Nexus logo on the start up screen.
I'm unlocked and rooted but haven't installed any Roms ever. I used Wug's toolkit to root.
the only thing I can think of is that I was copying fonts from the system folder and maybe I moved a font instead of copying it, but I really don't think moved anything without replacing. Either way, i really don't think that moving a font would cause the phone to not boot up.
The phone booted up just fine an hour or so before this happened, so the font thing is the only thing I can come up with. I tried to use Wug's toolkit to push the font file to the N4 but the script gets stuck when trying to reboot.
Please help!! any suggestions?
------
addt'l info:
CWM not installed, phone does not bootloop, just gets stuck at X
nvillamob said:
Last night I was using my Nexus 4 and it wouldn't connect to any web pages so I thought I'd reboot to see if that fixed it. I powered off then back on and it won't get past the Nexus logo on the start up screen.
I'm unlocked and rooted but haven't installed any Roms ever. I used Wug's toolkit to root.
the only thing I can think of is that I was copying fonts from the system folder and maybe I moved a font instead of copying it, but I really don't think moved anything without replacing. Either way, i really don't think that moving a font would cause the phone to not boot up.
The phone booted up just fine an hour or so before this happened, so the font thing is the only thing I can come up with. I tried to use Wug's toolkit to push the font file to the N4 but the script gets stuck when trying to reboot.
Please help!! any suggestions?
------
addt'l info:
CWM not installed, phone does not bootloop, just gets stuck at X
Click to expand...
Click to collapse
do a factory reset via recovery
by copying system fonts which are not made for jb, your system could be damaged and thats the reason why you are in a bootloop..
What font did you push and how?
Sent from my HTC6435LVW using Tapatalk 2
pa.pn2 said:
do a factory reset via recovery
by copying system fonts which are not made for jb, your system could be damaged and thats the reason why you are in a bootloop..
Click to expand...
Click to collapse
I'd really like to avoid doing a factory reset if possible, but that may be inevitable.
What I did was copy (move?) fonts from the system folder to a folder on the sd card so the fonts would be accessible to something I was making in UCCW.
When I boot into recovery all I see is the Android laying on its back with a red triangle and beneath that it says "No command."
And this is why you don't use a toolkit. It gives you ability to do things when you didn't know how to get there.
You should just factory reset and get your phone booting. I don't think you're in a position to be trying to save your data because you did things without know what was going to happen. Don't ever touch things in system unless you truly know what you're doing. Especially not without a nandroid backup.
Sent from my Nexus 4 using xda premium
I'm in over my head now, but I knew what I was doing at the time. I *think* I moved a ttf file instead of copying it. A brain fart led to all this. Live and learn and hopefully the community can help me out.
I do have a nandroid from a couple weeks ago that I'd be happy to flash but I'm not familiar with adb but I'm willing to give it a shot if anyone could help. Google hasn't brought me much luck.
nvillamob said:
I'm in over my head now, but I knew what I was doing at the time. I *think* I moved a ttf file instead of copying it. A brain fart led to all this. Live and learn and hopefully the community can help me out.
I do have a nandroid from a couple weeks ago that I'd be happy to flash but I'm not familiar with adb but I'm willing to give it a shot if anyone could help. Google hasn't brought me much luck.
Click to expand...
Click to collapse
Best thing I can say is to fastboot flash back to stock. Google on how to do it, there's a guide on XDA on how to restore factory stock images.
Start all over as if you just got your phone and don't do the same mistakes again. Spend the 25-30 minutes and read how to use fastboot, and don't do things without asking or thinking beforehand. If you don't know what you're going to be modifying or whatever, don't do it.
You don't flash a nandroid. You restore it via recovery in recovery mode.
So I booted into recovery, chose wipe data/factory reset.
After that runs, I reboot the phone and I'm still stuck on the X.
I've got the factory image tgz file but I don't know how to flash it
nvillamob said:
So I booted into recovery, chose wipe data/factory reset.
After that runs, I reboot the phone and I'm still stuck on the X.
I've got the factory image tgz file but I don't know how to flash it
Click to expand...
Click to collapse
Use search + read stickies in the future.
Here is the thread you're looking for, http://forum.xda-developers.com/showthread.php?t=2010312
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10l.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional (NOT optional for n00bs) -- Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Click to expand...
Click to collapse
the files within the tgz will contain those imgs that you need. you may skip on fastboot flashing the radio, recovery, bootloader
do flash the system and boot flash for sure.
thanks again. I must be awful at searching because I can never find what I'm looking for.
In the mean time, I figured out how to use the toolkit to flash the stock image and I'm back in business. i sincerely appreciate the help.
nvillamob said:
thanks again. I must be awful at searching because I can never find what I'm looking for.
In the mean time, I figured out how to use the toolkit to flash the stock image and I'm back in business. i sincerely appreciate the help.
Click to expand...
Click to collapse
It's all good, I mainly use Google and type random tags on google like "how do i restore nexus 4 back to stock" or something between those lines and something would pop up. In general, Q&A there are stickied threads that has an index with a link to all the other pages that you're looking for.
It all comes with experience.
Errrrrrrr. Um.... you kinda killed me when you said toolkit. Don't use them it's what got you in this situation in the first place. Learn from your mistakes. The toolkit didn't necessarily bring you to this situation but you're not familiar with what the toolkit is actually doing and you're doing changes to the system because you aren't aware of what's going on in your surroundings.
http://forum.xda-developers.com/showthread.php?t=1469909 is a good thread on why you don't use toolkits. How do you think I know all this knowledge? Certainly not by using a toolkit. You have to know how to do these things, otherwise the next problem you'll have you'll ask questions some more. Please just take the time and read it and figure it out how to do it. It's not difficult by any means.
Good luck and glad I can help. I hope I could change your mind on the dangers of using toolkits and do it the traditional way with backgrounds of why you're doing this and that. If everyone used a toolkit then no one would be in Q&A forums could help others, like myself. If i used a toolkit, i wouldn't know how to fix your situation either. Thanks.

Rooting my Nexus 4 - Kinda scared to do

The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
ZyreHD said:
The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
Click to expand...
Click to collapse
setup adb and learn how to flash back to stock in fastboot. you will never brick your device beyond repair as long as you are capable of following directions for flashing and rooting and such
Here's the sticky from the other forum.
That is very useful and they talk in layman's terms. When I first got my N4, I followed this and got custom everything following the instruction posted there.
I'm no expert, but I rooted my N4 in the first week very easily, and as long as you follow all the instructions in the XDA thread then you won't go wrong. If you are really worried then you can use a toolkit as that will automate everything, but I'd never recommend that as you aren't really learning.
As for backing everything up, you can back up some things like your contacts, WiFi passwords and so on to your Google account. Apps is a lot harder if you want the data, but I believe an ABD backup will work - again, look at the appropriate thread (or use the toolkit for backing up).
And Roms, most of them have a stock feel with more features such as extra customization, but if you want a different look you can use themes - you can get touchwiz themes on the play store for ROMs like CM.
Sent from my Nexus 4 using xda premium
you dont need root to flash roms or kernels, you need a custom recovery(and an unlocked bootloader). you need root to run root apps and to mess around with the root file system.
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
username8611 said:
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
Click to expand...
Click to collapse
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
ZyreHD said:
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/showthread.php?t=2010312 well, it will show you exactly how to get back to stock if need be.
We were all scared and nervous too when we first rooted an android device. Lol. When you get it done you soon realize how easy it was. :thumbup:
Sent from my Nexus 4 using Tapatalk 2
Can someone help? So I have Cyanogenmod installed on the phone and got USB debug on. When i unplug and go into the bootloader and then plug the micro-usb in my PC doesn't detect the phone. I do have the drivers installed.
It did work, now it doesn't meaning I can't perform the stuff needed.
ps: If your wondering if I use the SDK to put everything to stock well sorry but I can't get the SDK to work. Java issues and errors. Pain in the ass so I stop with that.
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Edit 2: 5min later and still at the X logo. It does move but nothing. Is my phone dead?
ZyreHD said:
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Click to expand...
Click to collapse
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
im not sure if i reading it right, but from what i can gather, you flashed cm10.1, then found out adb doesnt work right so you are ditching it and going back to stock? i wouldnt worry about it too much. as long as you can still use fastboot in the bootloader, thats all you need to do anything to save yourself from certain death. adb is more helpful for gathering up data if you cant lose it before flashing back to stock
username8611 said:
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
Click to expand...
Click to collapse
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Edit 3:
Retrying in the meantime. Now at writing system (done)
Edit 4:
Now I'm at the point where it's erasing userdata....
Edit 5: couple of minutes later and still going.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Click to expand...
Click to collapse
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to the bootloader. type this in fastboot, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
username8611 said:
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to fastboot. type this, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
Click to expand...
Click to collapse
I got a different option now. format userdata and I get options. Flash all, erase, update filename etc.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Click to expand...
Click to collapse
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
El Daddy said:
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I only have 4 options there.
Reboot system now
apply update from ADB
wipe data/factory reset....
Oh I got it. It formatted and I rebooted. For now it only shows the X logo. Will go downstairs in the meantime to get something to drink. It might take some time maybe?
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
nevermind, you were talking about the options in recovery
ZyreHD said:
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
Click to expand...
Click to collapse
Congrats. That's why I wrote what I did in your other thread. Read, read, read. Its better to know how to fix things before they happen then frantically trying to find out how fix them while they happen.
Sent from my Nexus 7 using xda premium

[SOLVED]A500 Stuck on OS Load

Tired, Frustrated and Helpless I am at the moment.
My A500 was running OK with a Jelly Bean Rom( I forgot which one) with Skrilax_CZ's bootloader V8 and CWM v5.5.0.4.
I decided to try a different Jelly Bean Rom. Forgot to keep a CWM backup and my misery started.
Any rom and gaps will install fine. But after reboot it will be stuck on Cyogenmod or Android LOGO. I have tried several ROM. Exact same result.
This happened a few months back and after trying numerous times I gave up for that time.
But I need to get the tablet back to working.
So, since yesterday I have been trying my best to get this one to work.
Started with "[A500 & A501] Android 4.4.4 (OmniROM unofficial)".
According the installation note for that rom, I installed CWM 6.0.4.5 on secboot following the "[Recovery]CWM 6.0.4.5[UPDATED WITH INSTRUCTIONS][25/12/2013]" process.
Same exact situation. ROM will install then after reboot it will be stuck on OS load.
Tried with a few other older rom such as CM10-FLEX_V6Supercharged_Rev3.4. Same issue.
I even, Installed TWRP recovery openrecovery-twrp-2.6.3.0-a500 on secboot. Same Issue.
Then, Updated Skrilax_CZ's bootloader V8 to Skrilax_CZ's bootloader V9. Same Issue.
Weird thing is now when I go to "CWM 6.0.4.5" from "Skrilax_CZ's bootloader V9", CWM doesn't really let me do any task. Any menu I enter on CWM 6.0.4.5 it freezes and then reboots the tablet. But initially when I first installed CWM 6.0.4.5 on secboot it worked for the first few times.
I am a noob in this. I do not want to try anything else myself as I think I will eventually brick the device and there will be no coming back.
I have searched on XDA for this issue. Many other people have similar issue with a500 but I couldn't find any situation same as mine.
Need help from you awesome people.
I do not want to give up on this tablet. But without your HELP I am lost.
Please HELP.
Need help on this please.
iamtapu said:
Need help on this please.
Click to expand...
Click to collapse
Have you tried wiping the device in fastboot mode? If not, try that!
The partitions to wipe are system, data and cache. The command is "fastboot erase cache".
HenrikE said:
Have you tried wiping the device in fastboot mode? If not, try that!
The partitions to wipe are system, data and cache. The command is "fastboot erase cache".
Click to expand...
Click to collapse
tried that. same issue.
it keeps circling on cyanogenMOD logo.
Apologies for reply late. I was not well and could not attend to you reply.
anything else i can try?
Please help.
Hey Bro,
I had exactly the same issue. What I did to solve it, was to delete all folders manually. Boot to recovery and choose "mounts and storage". Unmount everything and then format every folder. Then Wipe everything again. Reboot and flash the image with recovery. Then everything should work fine.
Same here
I have had exactly the same issue and haven't yet found a decent solution.
Mine was stuck on the Acer logo with the stock ICS ROM.
I found my CPUID and SBK, the linux way.
I tried everything you tried, managed to have bootloader V9 installed, TWRP as a recovery (Thor's version), CWM as secboot.
I was able to wipe and flash with no errors, but it would always stuck on the Acer logo. No custom ROM would ever boot.
I will definitely try Unimatrix-zero's solution and tell you guys if it worked for me.
So far, the only thing that worked for me was to use an EUUs package (GEN1) to get back to stock HC 3.01.
As you may guess, there are no more OTA updates via wifi in 2014.
So I downloaded several update packages and so far I only managed to update to HC 3.2. I haven't yet found a working package for stock ICS.
Anyway, if Unimatrix-zero's workaround actually works, a custom ICS ROM will do the trick for me.
Unimatrix-zero said:
Hey Bro,
I had exactly the same issue. What I did to solve it, was to delete all folders manually. Boot to recovery and choose "mounts and storage". Unmount everything and then format every folder. Then Wipe everything again. Reboot and flash the image with recovery. Then everything should work fine.
Click to expand...
Click to collapse
Significant result but did not resolve the issue.
As you have mentioned, I have wiped off everything that i can find in the recovery menu.
rebooted after that to recovery and for the first time I could go to TWRP 2.7.
tried to install a custom rom. but same issue. Either it reboots when I tried omni rom 4.4.4 on the "booting from primary" menu or the CM blue circle going on forever, when I tried with a CM 10.1 rom.
and just now after trying the cm 10.1 rom it went back to the way it was before. now the TWRP 2.7 will just keep on blinking on the screen .
Help bro...help....
You can try the following fastboot commands to wipe your device:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
And then flash the rom.
Unimatrix-zero said:
You can try the following fastboot commands to wipe your device:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
And then flash the rom.
Click to expand...
Click to collapse
you are a GOD SEND for me.:highfive::highfive::highfive::victory::victory::victory::victory::victory:
Did the following as you mentioned.
Code:
fastboot erase boot
fastboot erase system
fastboot erase data
fastboot erase userdata
fastboot erase cache
boot recovery TWRP 2.7.
Installed OMNI 4.4 rom.
Installed GAPS.
NOW its booting to OMNI rom...
awesomeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

Categories

Resources