Related
Hello,
I come here and make a new thread after I spent the day inside various forums to solve my problem but wasn't able to.
Here is the thing I tried to install the cyanogenmod earlier today. I unlocked my N1 properly and think I rooted it properly as well. But I was unable to install the custom rom. Actually my N1 won't even boot, it's stuck on the cross image with the unlocked lock and I can't boot the recovery either. I tried to install a custom recovery, the amon ra thing, but it still freezes on the cross screen.
I assume my N1 isn't completely bricked since I can still power it up, start the fastboot mode and my computer recognize de USB connection (however ADB won't find the phone even after I re-installed the drivers).
So here I come for help to either bring back my N1 to its former stock rom or any functionning rom.
Thanks.
Try the unroot/restore guide with PASSIMG of FRG33. Look at my signature.
oh thank you !!! It worked perfectly !
EDIT : Well spoke too soon I rebooted the N1 after its apparent recover and it froze again, so I started the operation once more and while updating the files ravio_v2 was checked "fail-pu" instead of "ok"
EDIT 2 : Well I rebooted after the update and the N1 never powered up again ... I guess now it is really bricked... though I can't figure why
olicyr said:
EDIT 2 : Well I rebooted after the update and the N1 never powered up again ... I guess now it is really bricked... though I can't figure why
Click to expand...
Click to collapse
You can't even get into fastboot any more?
Also, you say you followed the right steps to unlock the device and the right steps to root the device... What steps did you take exactly?
Hi,
to unlock the phone I used the oem command in the fastboot mode. Then I tried to install the amon ra custom recovery and I think that is what brought all this trouble.
Can you still see your device through fastboot? If so you should be able to flash a recovery image and a ROM of your choosing.
It should boot up fastboot like Dirk said. You can not brick the phone by flashing a recovery.
Sent from my Nexus One using XDA App
I guess there is some HW fault - might be a recent bad sector in one of the system critical areas. It's not something you can cause with SW - unless you're flashing hboot or radio, which should have been covered in the first restore attempt, which worked.
Anyway, if it doesn't power up at all - and doesn't react to charging - try pulling out the battery for several hours, and then put it back and try again. If it doesn't work - then you're up for a warranty repair...
DirkGently1 said:
Can you still see your device through fastboot? If so you should be able to flash a recovery image and a ROM of your choosing.
Click to expand...
Click to collapse
No the phone doesn't boot anything. I'll try to remove the battery and wait a few hours like said above, if it doesn't work I'm still under warranty I think
Hey you guys
I recently installed amon ra's recovery v. 1.7 on my magic 32a (radio 6.3.5 something) after I rooted my phone, of course.
Now, I thought that with the new recovery I would be easily able to flash a custom rom onto my magic. This was however not so easy, because the recovery behaves in a very weird way. Whenever I tell it to flash a new rom from a .zip image, or wipe the phone, or anything, it just reboots my magic and thats it. Also, the recovery happens to freeze quite regularly when I don't act very quickly. E.g. when I boot into recovery mode and don't touch the phone for the first 5 seconds, it wont respond any longer.
So, I'm probably doing something wrong here. I would appreciate any help from anyone. (and btw, i have the official android 1.5 sense rom installed on my magic, os I cant use rom manager either, since it only supports android 1.6 upwards.)
Look at the root guide in my signature..
Do step 0, 1, 2, 5 and 7 only.
It should flash the recovery partition one more time.
Hopefully it will fix your problem :0)
mumilover said:
Look at the root guide in my signature..
Do step 0, 1, 2, 5 and 7 only.
It should flash the recovery partition one more time.
Hopefully it will fix your problem :0)
Click to expand...
Click to collapse
hey, thanks for the quick response. I still have a few questions though, since I am quite a newb. So when I type all of those commands into cmd, doesnt my device need to be connected to the computer somehow? I read somewhere earlier that I simply connect it using the "mount" funtion, the problem is that that doesnt seem to work anymore for my magic, because after I hit "mount" it simply goes back to "usb connected" without acutally mounting. So ..how do I connect the device to the PC while entering the commands?
ok... my bad..
Try to read the ENTIRE guide... then do the steps i mentioned above :0)
Don't mount it... just connected... but again.. read the guide.
thanks a lot
I didnt use your method to flash the image, but the hero recovery works way better than the one I had before. I managed to flash a rom now. So happy ;D
ok i think i just did a bad mistake
i installed rom manager after i had flashed an android 2.1 rom on my magic. THen i told it to flash some rom from my sd card and also wipe some data, or something. Now my magic gets stuck on the magic bootscreen, like it keeps looping. Did i brick my phone ..or is there a way to fix this? please help me, (
most likely is that the rom you flashed doesn't have a compatible kernel for your phone.
Just boot into recovery and flash a rom that is compatible.
cant boot into recovery ..it just keeps looping
Then you will need to boot into fastboot and reflash a working recovery.
Clockwork has issues flashing the clockwork recovery sometimes.
to boot into fastboot i need to hold power and back, right? ..that doesnt work either. again, it just keeps looping.
so, guys ..did i brick my phonne..?? :S
da robat said:
to boot into fastboot i need to hold power and back, right? ..that doesnt work either. again, it just keeps looping.
Click to expand...
Click to collapse
you're probably not doing it right. you should still be able to get into recovery or fastboot and install a different recovery. i'm using RA-magic+v1.7.0.1 recovery it has bugs but pretty stable.
so what am i doing wrong??
just realized when i connect the phone to my pc over usb and then boot it, it connects to the pc for a second or less and then disconnects again. Dont know if this helps anyhow.
pull battery, put battery back in. hold back and push power.
Should be good.
tried that like 50 times. phone just keeps looping ..like, it restart over and over again.
What you have is what hundreds before you had when they used Rom manager.
The system will not boot into anything.
My advice is to never use Rom manager for 32A device.
The fix:
Keep pushing the back button while the system reboots... just mash the **** out of it..
I helped out someone before you, and he did it for over an hour or so...
It's a timing issue...
Good luck
haha ..so is there still hope?
cheers for all the answers ;D
i do have one question though, actually.
Shall i just press the back button continuously ...while it keeps looping, or should i rather restart the device after each loop and hold the back button?
just mash the back button.
Please delete, Ive fixed it
Backmankiller said:
Ok first let me start by saying im sorry if this is in the wrong thread or a repeat. Ok so heres the issue, I had my phone rooted and had a custom rom on it. I downloaded a animation and boot screen and installed them. I had to reboot my phone, when done so it was stuck on the new boot screen for a long time. I tried turning off and on several times each with the same results. So i went into my recovery screen and wiped the the system and and did a factory reset. Im on twrp recovery. I rebooted my phone and it tells me no OS. I have no back up now and dont know what to do. Ive tried using the toolkit to go back to stock but it wont let me saying it cant extract the files. Does anyone have any ideas what to do please? I can get into fastboot mode, download mode and recovery but thats it! Please please please help lol!!!
Click to expand...
Click to collapse
this is exactly why people need to learn adb commands and push commands. you are not bricked. you wiped your system you should have just did a factory reset. as far as the tool kit not extracting I don't know what that's about. stop relying on tool kits. they make things easy yes. but it takes the learning curve away
http://forum.xda-developers.com/showthread.php?t=2010312
If you can get into fastboot you are NOT bricked.
Read up on how to manually flash files in fastboot.
I got it, thanks guys!
================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit
The same just happened to me, wtf
Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.
GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too
Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.
Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop
Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?
I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.
Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?
And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT
Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.
I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!
Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?
Hi GusGold No its 9008
Hello, I own a Lenovo A6010, I recently tried to install a custom rom from a forum in this website, as i am newbie to all this, I think i screwed somewhere. Now my phone is stuck on boot screen. I cannot even start my phone in recovery mode or the menu that takes you to recovery mode.
Before flashing i had taken a backup of the dalvik cache and system and data and all those options available in the backup option in twrp which kept on my pc. Now i dont have any idea what do.
I even downloaded the stock rom of my phone from some website, but it was available in a rar file.
When I connect my phone with a cable while pressing the volume down button the same boot screen pops up and my computer starts to install device drivers. I think my phone can be brought back to normal, but i don't know how.
can someone please help me with some suggestions on what to do with my brick.
Thanks in Advance...
Warm regards
Do you have twrp installed? And by what method exactly did you try to install the custom rom?
Edit: Nevermind. Didn't realise this was a year old thread