So i was running BCM ICS and came across a Sense ROM, so i changed the partiton scheme on blackrose to 250/10/176 without any problems, when i went into recovery i encountered the usual message that occurs in 4EXT Recovery when you change HBOOT Partiton, something like "ATTN: 4EXT HAS BOOTED INTO SAFE MODE BECAUSE THE FOLLOWING PARTITON IS INACCESSIBLE 'system' IF YOU HAVE CHANGED HBOOT PLEASE WIPE ALL PARTITONS (EXCEPT SD-CARD)" Now this happens to me all the time so i went into the wipe menu and started to do that, half an hour later i noticed that it was still stuck on "Formatting system" and boot was wiped so the phone will now boot straight into the bootloader. This is my main phone that i use to answer important phone calls with so i really need the magic of you guys to help me in this situation.
Thankyou.
I also forgot to mention that flashing a rom wont help as the recovery will go onto the progress screen but will freeze after that
I figured out that i had to use fastboot erase system. It works now.
humzaahmed155 said:
I figured out that i had to use fastboot erase system. It works now.
Click to expand...
Click to collapse
FYI: If you solved the problem yourself, then please edit your original title with the word "Solved" so we know you don't need any further help.
Thanks, but this new layout needs getting used to, I don't suppose you know where to change it?
Sent from my Nexus One using xda app-developers app
Related
Hey guys i don't know if anyone of you had the same issue but any info/help could be helpful.
I used to flash my N1 A LOT! but today i have this strange issue. I wiped and flashed rodriguezstyle again for a clean start, but i only got the colorful X with the unlocked symbol at the bottom and then just a black screen. i thought I've done something wrong and flashed again, but with the same results.
i changed my sd and downloaded again the rom but still no luck, did a nandroid restore and the phone was working properly. then i got a bit frustrated. downloaded 2-3 more roms but the result was the same.
i read somewhere that flashing with battery <50% may cause some errors so left the phone off to fully charge and tried again... no luck
then i remembered i upgraded the radio and i downgraded it to the old one, but still the same results and nandroid doesn't work... jeeeesh... back to the new radio and to my nandroid, but its no fun owning a smart-phone if you cannot flash it.
anyone with the same issue or any helpful tips/instructions?
Try this:
When the phone hangs at boot, reboot to recovery, wipe cache and dalvik-cache and reboot from recovery. Does that work?
If not, you'll need to logcat the boot process and post the log somewhere for us to have a look at.
So, assuming adb is working on your computer, plug in via usb, use adb logcat > output.log and reboot the phone. Continue logging for about 60 seconds after the phone stops.
Post the log to www.pastebin.com and then link back here.
hmmmm ok i will post results in abt an hour. thanx!
hmmmm i think i sorted it out... reflashed recovery. propably i messed smthing in there! thanx for your effort!
Hello everyone!
Weird problem here, too.
I was backing up my SD card in view of a format/cleanup....and when I went to boot into recovery, my N1 was stuck on the black screen with the white letters at the bottom "Build : RA-nexus-v1.7.0.1"... The phone actually boots great, it is just not loading the recovery image. Is it possible that part of the flash got corrupted? If so, I'm pretty much done flashing my N1, right???
I'll post a log asap (if it could help any)...
Oh and btw i tried to re-flash Amon-RA's recovery twice already...Superboot said it was successful....but I doubt it...
Well try flashing stock rom! I flashed it through fastboot step by step and it worked. Also check if the rom you try to flash needs ext partition or if apps2sd is enabled
Sent from my Nexus One
Test
Sent from my Nexus One using XDA App
Thanks nica.
I had to flash stock boot and rom to fix it...
Sent from my Nexus One using XDA App
The Story:
I bought a new Nexus one.
Got the OTA updates and updated the phone (first 2.1 then 2.2 and 2.2.1)
Since then the phone is not rebooting properly. usוally it just reboot and reboot and reboot.
After I formated the SD card the phone booted succeussfully but crashed again after a minute back to the endless loops.
can someone please help?
I tried to unlock the bootloader, root the device and flash Amon's recovery but although the cmd windows said that it ewent alright besides of the open lock sign nothing seems to change.
Please Please Please Help, It's a brand new phone...
p.s.
if there is any way to just erase everything (already tried earse cache and userdata from the recovery...) and get a "new" phone - please tell me how.
I know how to use adb/fastboot, I'm not a noob...
Thanks a lot!!!
Where is my question...?
I can't find it...
It's right here.
Anyway, I suspect your problem after flashing recovery is you're rebooting, and the OS is reverting to stock. Go straight into it first, take a backup and wipe it.
Failing that you'll need to grab FRG83 image from http://developer.HTC.com and use fastboot to flash over system.img and boot.img
You'll be able to format every partition on your Nexus One by using Clockwork Recovery.
By Amon's recovery you can do similar thing but it doesn't offer ability to format System partition (it's not quite useful to format System partition anyway..)
You mentioned that your phone could boot successfully with a formatted SD card and then ran into problem, my guess is that your SD card has bad block(s), please verify this by take your SD card out and use your phone for few hours, is there any stability issue?
so... an update:
I downloaded the original files and flashed them all in fastboot (recovery.img, userdata, boot and system).
The phone is on the "nexus-one sign" screen for over then half an hour now and nothing seem to change.
a. Is there somthing else that I should do? how long it should take...?
b. what are the odds that it's a hardware problem...?
c. could it be a problem related to incompatible radio?
Thanks...
and other update...
even after reflashing the original files I can't enter recovery (original) so I guess the problem lies within it.
with this information and the other messages - does anyone has an idea...? please...?
did you try another SD card?
try this and let me know if it works
kuldrivedotcom/host/n1/Back2Stock.zip
just unzip the file and follow the instructions.
let me know if it worked
nexus @ kuldrive dot com
PCNemy said:
try this and let me know if it works
kuldrivedotcom/host/n1/Back2Stock.zip
just unzip the file and follow the instructions.
let me know if it worked
nexus @ kuldrive dot com
Click to expand...
Click to collapse
Thank you, but the problem solved.
It was a big HARDWARE problem.
HTC knew right away what the problem is.
Sent the phone to HTC, got it back in 3 days, everything work just fine since.
Thanks anyway...
I apologize in advance if this same issue has been replied to elsewhere. I'm in kind of a unique situation and couldn't find an answer anywhere.
I'm got an N1 with 2.3.6 stock ROM, rooted. Recently I downloaded Titanium Backup PRO and while attempting to integrate dalvik cache to ROM, my phone rebooted into a bootloop. I'm assuming this is a bootloop. I get the colorful splash screen, it freezes for a second of two, then continues on, and on, and on....
Is there a way to get me out of this loopwithout having to wipe all my data, so I can backup all my stuff before I flash a custom ROM?
Everything I see about bootloops, mentions unlocking the bootloader and wiping all your data. I've seen downgrading using PASSIMG and loading stock rom. I'd really just like a simple way to get out of this loop hell and get my phone back up. It's in teh ship now getting it's power button fixed.
Thanks in advance
first thing i do on bootloops is pull battery
if no go pull battery and then pwr on by pressing pwr and trackball at same time--you can then get to recovery and maybe wipe dalvik and cache and reboot
i have never used TB for anything other than backup/restores, so can't help with dalvik integration
You might be able to fix it by wiping your cache from recovery.
Sent from my Nexus One using xda premium
Thanks for the advice! I'll give it a try as soon as I get my phone back from being fixed.
Hey guys, I hope you can help. I got my phone back with new power button, Yay! When I try to boot into recovery, teh Nexus X logo comes on for a moment and then I get a white triangle with an orange exclamation point. Do I need to use ADB to try and go to recovery and wipe my cache? I've never installed a recovery image. Do I need to do that or should there be a stock image already on my phone? Am I SOL?
One more thing that might help. I notice that when I go into HBOOT, the phone searching for 4 images from my SD card and can't find them. They go by too fast to write them all down but I think some are PASSIMG, PASSDIAG, etc. Again, do I need to load a recovery like clockworkmod on my phone first and then go into recovery to attempt to wipe my cache?
I get the same passimg all the time--no problem
If your phone came back from repair, you are probably unrooted and hence the triangle. At least that is the way I remember it, but has been two years since I rooted
If that is comfirmed by someone else, you wil need to reroot and install a recovery
A good time, if you haven't, to install android sdk and root/install recovery the right way and have full adb/fastboot features
there other ways I am not familiar with
does the lock show unlocked on the screen, they could have relocked bootloader
the wiki has the instructions, just have to navigate to the htc smartphones and N1
jus to make sure that if u still got root. install su checker app from play store and confirm.
if not root using SUPER ONE CLICK ROOT.
flash recovery (4EXT is good) www.4ext.net
do a backup and then flash the rom u want
Sent from my Nexus One using Tapatalk
Thanks I'll check. I only had teh power button fixed and not by HTC so I doubt they unrooted it. I'm still in a bootloop but I can use superoneclick still, so I'll give that a try.
so what I'm trying to do is wipe my cache without wiping my data. I don't think my bootloader is unlocked. Am I screwed?I'm in a bootloop, so I can 't install anything to the phone. I probably could put a recovery image on the SD card, but if my bootloader is locked, I'm guessing that won't work. I'm rooted. When I go to HBOOT, the phone looks for passim files and doesn't find them, then when I choose recovery I get the white triangle. I've try to flash a recovery image through ADB but I get an error, failed to load image. Again, is that a bootloader issue?
I'm almost at the point of just wiping my data and hoping I can get it all back somehow.
holtonhj said:
so what I'm trying to do is wipe my cache without wiping my data. I don't think my bootloader is unlocked. Am I screwed?I'm in a bootloop, so I can 't install anything to the phone. I probably could put a recovery image on the SD card, but if my bootloader is locked, I'm guessing that won't work. I'm rooted. When I go to HBOOT, the phone looks for passim files and doesn't find them, then when I choose recovery I get the white triangle. I've try to flash a recovery image through ADB but I get an error, failed to load image. Again, is that a bootloader issue?
I'm almost at the point of just wiping my data and hoping I can get it all back somehow.
Click to expand...
Click to collapse
You really know nothing huh. The triangle is the recovery. Press power button and volume up at the same time, it will the show you some options like wipe cache.
n1newbie said:
jus to make sure that if u still got root. install su checker app from play store and confirm.
if not root using SUPER ONE CLICK ROOT.
flash recovery (4EXT is good) www.4ext.net
do a backup and then flash the rom u want
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
Did you miss the "stuck in boot loop" part?
sorry,
meant that the triangle is your stock recovery--
you install recovery thru fastboot not adb
i would still, if you haven't, install android sdk on pc-unlock bootloader (fastboot oem unlock) and fastboot recovery--all in wiki
i think it was mentioned--holding down pwr and tb will get you into fastboot mode--phone connected and usb debugging selected on phone
you'll just have more flexibility with flashing roms etc and getting out of trouble
hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3
spazzy1912 said:
hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3
Click to expand...
Click to collapse
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone
markj338 said:
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone
Click to expand...
Click to collapse
woops, i forgot to mention that i was on 4ext touch before and it still happened :S
it used to happen before, but not as frequently, so that is why i am a bit worried
when i get my pc back ill try reverting back to 1.13 bootloader :S
Alright so for the past six hours I have been trying to make up for my mistake. I accidentally tried to flash the color os rom like most others and failed to read. I know stupid, right? Anyway, I cannot access recovery. It just goes to the HTC logo, says I can access bootloader, and I have s-on. However, I have tried to flash a new recovery image and it says okay everything worked and it still does the same thing. So does that mean I am no longer rooted? I just need to figure out a way to get a rom back to my phone, since obviously it erased everything on my sd card. Thanks in advance. Anything will help.
carbonfiber2gsx said:
Alright so for the past six hours I have been trying to make up for my mistake. I accidentally tried to flash the color os rom like most others and failed to read. I know stupid, right? Anyway, I cannot access recovery. It just goes to the HTC logo, says I can access bootloader, and I have s-on. However, I have tried to flash a new recovery image and it says okay everything worked and it still does the same thing. So does that mean I am no longer rooted? I just need to figure out a way to get a rom back to my phone, since obviously it erased everything on my sd card. Thanks in advance. Anything will help.
Click to expand...
Click to collapse
Hey there! Do you have an unlocked bootloader? That could be an issue.
Sent from my GT-N7105 using Tapatalk
yes i do and i also believe i have access to adb however i have tied to reflash twrp and erase cache and reboot but it just keeps getting stuck on white htc screen
carbonfiber2gsx said:
yes i do and i also believe i have access to adb however i have tied to reflash twrp and erase cache and reboot but it just keeps getting stuck on white htc screen
Click to expand...
Click to collapse
Problem is fixed I ended up flashing stock recovery through adb and the using the ruu kit and got it to work after re locking my phone