Related
Last night I installed geefree on my phone from the app store and used it to install TWRP. I downloaded a nightly CM11 and an appropriate gapps. Using geefree I rebooted to recovery (never figured out the button combination to boot to recovery "naturally") and installed both of the zips. This could be where I made my mistake, I installed both at the same time.
Now my phone loops, displaying the LG logo for a few seconds, then shutting off and rebooting before repeating the process. I can't seem to get it to go into download mode or the recovery menu. I've tried power+up, power+down, down+up and each of those while plugging the device in, etc. I can get the device to a hardware key control mode, though it doesn't seem too useful.
How can I save my phone? This forum has been a great resource in the past and I'm very grateful for the many tutorials I've followed rooting other devices. Hopefully you guys can save the day once again!
Volume up plus power is how to access recovery on sprint.
What stock sw version were you on before you flashed cm?
Did you wipe data before flashing?
Sent from my LG-LS970 using xda app-developers app
I was using stock 4.2.2, I believe. I didn't wipe the data (shame on me), a bad habit that I picked up from my first rooted device, the Samsung Moment. It didn't ever matter on that one, afaik. Thanks for the reply!
Edit: Volume up and power whether plugged in or not takes me to the hardware key control mode screen.
Second Edit: http://forum.xda-developers.com/showthread.php?t=2432476&page=35 I also found this thread where someone seems to be experiencing similar issues and they fix it with "LG Utility." Is that a PC application? It's a little vague to google, but I've been trying!
I have a bootloop issue every time i flash a rom i have to wipe all but sd flash roms and gapps the i do a restore from twrp and oly restore my boot image only and they boot no prob
I'm kind of starting to suspect my power button doesn't work at all for whatever reason. I have a lot of difficulty getting the phone to shut down, then it doesn't seem to easily power up. It's a strange collection of problems. Would a Sprint repair place be able to fix this?
If they have parts on hand if not either a swap out or a sendoff
Same problem here - bootloop and no download mode - CWM works! - urgently need help
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Device is recognized but can´t be mounted - bricked forever?
Parinibbana said:
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Click to expand...
Click to collapse
I tried a few things on Linux.
After terminal-command "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
So sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
Does it mean that the phone isn´t mounted or what? Now I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted. Does that mean my device is bricked for good? That´s it?
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb into the phone first then hold VOL+ and plug into usb port on the computer.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, it will shut off eventually!!
plug the phone in while in download mode to install drivers and set com ports, then unplug before you begin your flash with LGFlashTool, hope this helps you out.
Cronic2009 said:
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb in first then hold VOL+ and plug into usb port.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, hope this helps
Click to expand...
Click to collapse
Thanks Cronic2009 for your advice.
There are, however, szenarios where download-mode is not accessible any more. Neither by using the hardware-keys, nor by using the adb-command.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of that thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.
no problem buddy, glad you got it figured out, good luck to you from here on out!
FYI, that link doesn't work
I just wanted to ask anyone who might know, since the bootloader of the LS980 is locked, we cannot "break" this correct, so no matter what commands we decide to run through root, we cant touch the true bootloader there for LS980 fail safe? (Besides Acts of God, EMP, ect)
Cronic2009 said:
no problem buddy, glad you got it figured out, good luck to you from here on out!
Click to expand...
Click to collapse
Thanks for letting me know. I corrected the link in my previous post.
Be sure if you use a aosp based rom to flash the ZV8 modem. Your can use dr87 or furnance kernals after you flash the zva modem althought i have encountered soft brick due to this.
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
pitbullmommy45245 said:
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
Click to expand...
Click to collapse
Thank You for sharing you fixed your issue pittbullmommy but the link you posted points back to a post about a failed run on LGFlashTool, will you please fix the link and point it to the post/guide you used to fix your phone, it may help others stuck in a similar situation, glad to hear you got it fixed and working, best of luck with it from here on out!
Hi all
was just about to start a new thread but didn't want to get into trouble..anyway I am in need of some assistance please.my ls980 has been bricked for some time now been searching all over the internet for a solution to be stuck back at square one.found this video on youtube which is pretty much exactly what my phone is doing.I have used lg flash tool to revert to stock and still nothing I lost root doing that but last night,I managed to regain root access I have no idea how but it happened when i clicked ioroot batch file i went into download mode and it stated bottom left ROOTED in red so i managed that but that is it still doing what is being shown in the video its on youtube
watch?v=PjLF-pBhZSY
please if anyone has the know how I would like to fix this phone rather then bin it thank you all happy 4th everyone
After using tot and flash tool to get back to stock, did you try going into stock recovery and do a factory data reset? I know it sounds stupid especially after a tot but try it. Couldn't hurt
Sent from my LG-LS980 using Tapatalk
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Yes sir I've tried that and more to no avail is there anything I can do through adb I'm on stock recovery phone doesn't stay on long enough to install anything
sarfdawg said:
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Click to expand...
Click to collapse
You ever get her fixed?
Installed CWM Recovery (recovery-clockwork-6.0.4.8-m8.img) using Fastboot,
and then installed UPDATE-SuperSU-v1.94.zip
then took a nandroid backup.
Booted into Android - no problems.
But now :
- when I power down it reboots straight into CWM Recovery.
- when I select the advanced options of CWM Recovery / Power Down,
it reboots into CWM Recovery.
- when I select Fastboot/Power Down it also reboots into CWM Recovery.
From CWM Recovery I can
Boot System Now
and it boots into the system,
But when I power down, it reboots again into CWM Recovery.
ie, I can't power down.
The above only happens if a power or usb cable is connected.
If no power cable is connected, it shuts down normally.
But, if after it is fully shut down, I connect a power cable,
it again boots, by itself, into CWM Recovery !!
Notes:
- A restart from Android does an actual restart into the phone OS, not into CWM Recovery.
- if I turn back on Power/Fastboot, then I can shutdown properly even with power connected,
so the problem happens when Fastboot is off.
Anybody have any idea what is causing this
and what I can do about it?
some things I can think of trying
but I don't want to make things worse.
Have done this before on a Galaxy Nexus with no problems,
and have put CyM on an S3 with no problems.
[previously posted in the wrong forum (M7) moved here.]
undecidable said:
Installed CWM Recovery (recovery-clockwork-6.0.4.8-m8.img) using Fastboot,
and then installed UPDATE-SuperSU-v1.94.zip
then took a nandroid backup.
Booted into Android - no problems.
But now :
- when I power down it reboots straight into CWM Recovery.
- when I select the advanced options of CWM Recovery / Power Down,
it reboots into CWM Recovery.
- when I select Fastboot/Power Down it also reboots into CWM Recovery.
From CWM Recovery I can
Boot System Now
and it boots into the system,
But when I power down, it reboots again into CWM Recovery.
ie, I can't power down.
The above only happens if a power or usb cable is connected.
If no power cable is connected, it shuts down normally.
But, if after it is fully shut down, I connect a power cable,
it again boots, by itself, into CWM Recovery !!
Notes:
- A restart from Android does an actual restart into the phone OS, not into CWM Recovery.
- if I turn back on Power/Fastboot, then I can shutdown properly even with power connected,
so the problem happens when Fastboot is off.
Anybody have any idea what is causing this
and what I can do about it?
some things I can think of trying
but I don't want to make things worse.
Have done this before on a Galaxy Nexus with no problems,
and have put CyM on an S3 with no problems.
[previously posted in the wrong forum (M7) moved here.]
Click to expand...
Click to collapse
Well I haven't had this happen to me ever so, not sure how much help I'll be but...
Have you tried reflashing CWM? Perhaps clear the cache? Try to flash TWRP and see if it does the same, can always flash CWM again afterwards.
BerndM14 said:
Well I haven't had this happen to me ever so, not sure how much help I'll be but...
Have you tried reflashing CWM? Perhaps clear the cache? Try to flash TWRP and see if it does the same, can always flash CWM again afterwards.
Click to expand...
Click to collapse
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
undecidable said:
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
Click to expand...
Click to collapse
Don't think a system reset is necessary just yet. First try to clear the cache and re-flashing CWM to see what it does. If nothing then you can try TWRP to see if it does the same thing.
Have you tried searching for a similar problem in the CWM thread if it's recovery related?
---------- Post added at 06:21 AM ---------- Previous post was at 06:10 AM ----------
undecidable said:
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
Click to expand...
Click to collapse
I also just noticed the version number for the CWM you're using, are you sure that's the right version? What device variant are you using, International, Verizon etc?
I see only these versions for international
philz_touch_6.25.5-m8.img
philz_touch_6.26.6-m8.img
philz_touch_6.41.6-m8.img
philz_touch_6.43.6-m8.img
Maybe you have wrong version if you use international version.
Download newest one here and reflash. That is IF you use international.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8
BerndM14 said:
Don't think a system reset is necessary just yet. First try to clear the cache and re-flashing CWM to see what it does. If nothing then you can try TWRP to see if it does the same thing.
Have you tried searching for a similar problem in the CWM thread if it's recovery related?
Click to expand...
Click to collapse
A system reset is no problem. I already did one before starting, and it is new. So no data/apps to lose.
Yes, spent about 6 hours searching last night. Haven't come across anything like it.
Plus, there doesn't seem to be a CWM thread for the HTC One M8 - there are threads for TWRP and Philz (CWM Advanced).
got info below nevermind =oD
I also just noticed the version number for the CWM you're using, are you sure that's the right version? What device variant are you using, International, Verizon etc?
I see only these versions for international
philz_touch_6.25.5-m8.img
Click to expand...
Click to collapse
I'm not using philz, I'm using standard CWM:
http://clockworkmod.com/rommanager
which is the recommendation in the Cyanogenmod instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_m8
So I think my version of CWM is correct.
BerndM14 said:
Yeah just linked the same to you now as well. Where did you get that version from then?
Nevermind, I got where you downloaded it from http://forum.xda-developers.com/showthread.php?t=2708520
So you're on Verizon?
Click to expand...
Click to collapse
No, I have the international version, and the recovery is from
http://clockworkmod.com/rommanager
the last line on the page, labelled M8.
I think it is the official version.
Well it seems we're back to square one then, erase cache.
Hook up device to PC, go into fastboot, adb reboot bootloader
fastboot erase cache
If it doesn't work then try another recovery, Philz or TWRP. Did you want to flash CM hence why you followed their tutorial?
BerndM14 said:
Well it seems we're back to square one then, erase cache.
Hook up device to PC, go into fastboot, adb reboot bootloader
fastboot erase cache
If it doesn't work then try another recovery, Philz or TWRP. Did you want to flash CM hence why you followed their tutorial?
Click to expand...
Click to collapse
I always read about 20 tutorials first: some are vague, some unreliable, some incomplete, some assume you have more experience, to make sure I fully understand what I have to do.
I chose CWM because I've used it before on a Galaxy Nexus and an S3 and it has been reliable.
I will install Cyanogenmod as soon as it goes to Stable for the M8. I have it on the S3 and am over-the-moon happy with it. However that could be a year.
Might wait a day before I try flashing TWRP. See if I can discover more, or if anyone has an insight to offer. I mean, why would it boot when you plug in the power cable?! Too strange to not be cautious.
undecidable said:
I always read about 20 tutorials first: some are vague, some unreliable, some incomplete, some assume you have more experience, to make sure I fully understand what I have to do.
I chose CWM because I've used it before on a Galaxy Nexus and an S3 and it has been reliable.
I will install Cyanogenmod as soon as it goes to Stable for the M8. I have it on the S3 and am over-the-moon happy with it. However that could be a year.
Might wait a day before I try flashing TWRP. See if I can discover more, or if anyone has an insight to offer. I mean, why would it boot when you plug in the power cable?! Too strange to not be cautious.
Click to expand...
Click to collapse
It seems like it's an old issue with CWM though on various devices.
HTC Desire S same problem as you also CWM recovery.
Desire Z same problem also with CWM recovery.
Desire HD same problem ALSO CWM.
Don't know if there is a problem with CWM and HTC devices maybe...Those 3 are all for HTC devices. Though doing a google search you do get the same problem with different manufacturer phones also with CWM
BerndM14 said:
It seems like it's an old issue with CWM though on various devices.
HTC Desire S same problem as you also CWM recovery.
Desire Z same problem also with CWM recovery.
Desire HD same problem ALSO CWM.
Don't know if there is a problem with CWM and HTC devices maybe...Those 3 are all for HTC devices. Though doing a google search you do get the same problem with different manufacturer phones also with CWM
Click to expand...
Click to collapse
wow! Clearly the issue! And it seems changing recoveries fixes it. Will try in the next hour.
what was the search phrase you used? All I tried returned irrelevent results, though mostly I was using G not XDA.
As my father used to say, your blood is worth bottling (its a compliment).
thankyou!
undecidable said:
wow! Clearly the issue! And it seems changing recoveries fixes it. Will try in the next hour.
what was the search phrase you used? All I tried returned irrelevent results, though mostly I was using G not XDA.
As my father used to say, your blood is worth bottling (its a compliment).
thankyou!
Click to expand...
Click to collapse
https://www.google.co.za/search?q=w...ite:forum.xda-developers.com&biw=1920&bih=979
Tossed in plenty of keywords into google, of course doing it normally gives a lot of results from other sites too but I just decided to narrow it down to xda(Most sites refer help questions to xda anyways so...)
I think it's better to use Google for searches anyways, it records info from a lot of sites. XDA works on a "keyword" basis it seems and most people when making threads don't really add any keywords to it so finding it is difficult. Heck, I even had issues finding HTC__622 in a thread where I knew for a FACT HTC__622 was mentioned at least 4 times, the results in xda itself turned up nothing.
I didn't even bother to try and search within xda for this issues, went the Google route and narrowing it down to xda, much better :good:
Back to the issue though, it would still be interesting to know what actually causes it to boot into recovery when it gets plugged in, it's strange and I'm curious about it. I also think flashing either Philz or TWRP should help, there are quite a few people on here using Philz and I can't recall an issue like this being mentioned before so perhaps it's not a problem with Philz.
BerndM14 said:
Back to the issue though, it would still be interesting to know what actually causes it to boot into recovery when it gets plugged in, it's strange and I'm curious about it. I also think flashing either Philz or TWRP should help, there are quite a few people on here using Philz and I can't recall an issue like this being mentioned before so perhaps it's not a problem with Philz.
Click to expand...
Click to collapse
Thanks. I did try an XDA search from G, but you are just better at it
There is code that gets executed when you plug in the power cable:
it shows the battery charging.
The battery charging icon that is showing just before boot into CWM recovery is different from the normal battery charging icon (that I can see when I have settings /power / fastboot on).
I wonder if CWM changes that code? If that is the case, flashing TWRP might not fix it - will soon know.
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
Now, when I power-off,
1. initially this funny black/white battery charging logo appears
with words in red at the bottom like:
This build is for Developement Purposes only
Do not distribute outside of HTC
without HTC Permission...
Click to expand...
Click to collapse
2. Then the normal green battery icon appears
3. but then the TWRP screen appears and disappears.
4. For about 2 secs the TWRP screen may flash back briefly
before returning to the green battery icon with the backlight.
5. Then it settles on the green battery icon,
and the backlight stays on for about 10 secs.
6. then the screen switches off
and it really appears to be powered off.
But if I quickly 'touch' the power button
the TWRP screen briefly appears (with a lock over it) once
and then the green battery screen reappears.
If I unplug then replug in power,
the same things happens: steps 1-6 above.
Tried flashing TWRP 3 times - no change.
Will now try flashing philz.
undecidable said:
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
....
Will now try flashing philz.
Click to expand...
Click to collapse
Philz does exactly the same as CWM - not surprising given that it is CWM based.
So have returned to TWRP, which is at least usable.
Any idea how to file a bug against CWM?
Philz I can do on their forum here.
undecidable said:
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
Now, when I power-off,
1. initially this funny black/white battery charging logo appears
with words in red at the bottom like:
2. Then the normal green battery icon appears
3. but then the TWRP screen appears and disappears.
4. For about 2 secs the TWRP screen may flash back briefly
before returning to the green battery icon with the backlight.
5. Then it settles on the green battery icon,
and the backlight stays on for about 10 secs.
6. then the screen switches off
and it really appears to be powered off.
But if I quickly 'touch' the power button
the TWRP screen briefly appears (with a lock over it) once
and then the green battery screen reappears.
If I unplug then replug in power,
the same things happens: steps 1-6 above.
Tried flashing TWRP 3 times - no change.
Will now try flashing philz.
Click to expand...
Click to collapse
Well removing the red development purposes text is easy enough if you have S-OFF. Remove Red Text on Splash screen
I'm not sure if the same issue with CWM is applicable to all or most users of Philz on here, like I said before, I haven't noticed any threads popping up discussing the issue, unless they discussed it in Philz thread itself.
I myself haven't noticed the issue you have with TWRP, will look into it more as I get some time, gonna be a hectic week Personally I only use custom recovery when I need it, which isn't that often, not a big "flasher" of ROMs etc, so I'm on stock recovery.
BerndM14 said:
Well removing the red development purposes text is easy enough if you have S-OFF. Remove Red Text on Splash screen
I'm not sure if the same issue with CWM is applicable to all or most users of Philz on here, like I said before, I haven't noticed any threads popping up discussing the issue, unless they discussed it in Philz thread itself.
I myself haven't noticed the issue you have with TWRP, will look into it more as I get some time, gonna be a hectic week Personally I only use custom recovery when I need it, which isn't that often, not a big "flasher" of ROMs etc, so I'm on stock recovery.
Click to expand...
Click to collapse
Yes, found the post for Remove Red Text on Splash screen early this morning. Seems to be related to Root, and separate from the TWRP issue.
I have to wonder if the TWRP problems aren't caused by the initial flashing of CWM. Anyway will post the issue on the TWRP forum tomorrow and see what they say.
Seems Philz has had this problem before, it comes from CWM, and fixed it before.
I have to say, this is the last HTC phone I buy - Samsungs are so much friendlier to flashing. Also I greatly dislike the big Tampered sign.
Reason for flashing recovery this time is I wanted root so I could remove garbage from the phone.
I don't flash ROMs much. High learning curve and risky. I do just one flash: from stock to CyangenMod. so much nicer it is worth it. I have to say if I had to choose between my old S3 with CyanogenMod and a stock M8, it would be the S3. If I can't get the garbage off the M8, I will just put it in a drawer till CyM goes stable for it.
Solved: Power Down reboots into Recovery
undecidable said:
Seems Philz has had this problem before, it comes from CWM, and fixed it before.
Click to expand...
Click to collapse
The solution! From the Philz M8 thread.
http://forum.xda-developers.com/showthread.php?p=53464839
An earlier version of Philz: 6.26.6-m8.zip.
The earlier version doesn't have the problem.
Thanks to @donmarkoni
Yesterday I tried to flash Color OS 2 Beta posted here. although the rom is not for the Oppo N1 W the XDA member cleonardo insure that it works very well. Then I flashed it in my OPPO N1, everything is ok during flashing, but then the phone freeze and the screen became black, I tried to go to recovery but nothing happened, I also connected the phone with my pc, flashed recovery, nothing happened and I thought my phone is dead. I could not find any solution for that, no one experienced the same situation. I post my problem in the same thread and he replayed (Dont worry , when you complete flash , at screen appear text chinese black colour , you wait some minutes), but i wait alot of time, restart my phone, i even put it for one hour to start and nothing happened. During my search, I came to this link: http://www.shuame.com/faq/restore-tutorial/547-oppo-n1-oppo-n1t.html in Chinese, using google translate I figured I can use their software to restore my recovery through RootGenius software, and then I can flash the stock or CM 10 or even CM 11 M8 again. After many hours, finally, I recover my phone again, flash the stock recovery and it came to life. Now everything working again. With this software, you can download roms, flash roms and recovery, use fastboot and even root your phone. You just need to connect your phone to it, ensuring that the USB debug is on, accept any notification and then you can browse your phone, flash roms and custom and stock recovery. It is the only way I found to recover my phone when fastboot not work, note that the ADB in the software is not working too but you can reboot in the fastboot with one click on the software itself.
Download from here: http://dl.shuame.com/files/RootGenius/1.8.7/RootGenius_en.exe
azharisadig said:
Yesterday I tried to flash Color OS 2 Beta posted here. although the rom is not for the Oppo N1 W the XDA member cleonardo insure that it works very well. Then I flashed it in my OPPO N1, everything is ok during flashing, but then the phone freeze and the screen became black, I tried to go to recovery but nothing happened, I also connected the phone with my pc, flashed recovery, nothing happened and I thought my phone is dead. I could not find any solution for that, no one experienced the same situation. I post my problem in the same thread and he replayed (Dont worry , when you complete flash , at screen appear text chinese black colour , you wait some minutes), but i wait alot of time, restart my phone, i even put it for one hour to start and nothing happened. During my search, I came to this link: http://www.shuame.com/faq/restore-tutorial/547-oppo-n1-oppo-n1t.html in Chinese, using google translate I figured I can use their software to restore my recovery through RootGenius software, and then I can flash the stock or CM 10 or even CM 11 M8 again. After many hours, finally, I recover my phone again, flash the stock recovery and it came to life. Now everything working again. With this software, you can download roms, flash roms and recovery, use fastboot and even root your phone. You just need to connect your phone to it, ensuring that the USB debug is on, accept any notification and then you can browse your phone, flash roms and custom and stock recovery. It is the only way I found to recover my phone when fastboot not work, note that the ADB in the software is not working too but you can reboot in the fastboot with one click on the software itself.
Download from here: http://dl.shuame.com/files/RootGenius/1.8.7/RootGenius_en.exe
Click to expand...
Click to collapse
hello
i need your help
i have the same problem
my phone is oppo n1w also
i try root genius but whane i open the program it ask to enable usb debugging mode
i cannot do anything with the phone and when i connect it to my pc and switch on nothing happened
whicj version did you use ?
thanks in advance for your help my phone is dead pls pls help
Hi, if your phone is totally black, when you connect it to the PC insure that you connect through the recovery (which will looks black too) then open the software in your PC, let it connect to your oppo, then open the tool area (an icon with 4 dots), select recovery ( the third one on the second row) open it, in the open window select the yellow folder and choose the stock recovery Oppo.N1.Recovery.1.0.0 ( search for it in the internet) then press the right Chinese icon. Now you can access the recovery again and flash the ROM back.
Sent from my N1 using XDA Free mobile app
If you fail in the first step, try connect again with the same steps, then use the fastboot icon to restart on fastboot, then use the recovery icon again.
i just complete video clip , its really easy my friend https://www.youtube.com/watch?v=v_NMsLLxUuw&feature=youtu.be
azharisadig said:
If you fail in the first step, try connect again with the same steps, then use the fastboot icon to restart on fastboot, then use the recovery icon again.
Click to expand...
Click to collapse
i made the process
everything is ok
i can flash recovery 1.0
BUT when i reboot look at the picture i attach and how the scrren appear and after turn black again
any idea ?
many thanks for your help
This is normal, just reboot into recovery through the software itself. When you select the recovery file there is an option to accept replacing the recovery, just tick yes... After flashing the recovery just boot through the software
Sent from my N1 using XDA Free mobile app
Everything is ok now
Many thanks for your help brother
Sent from my N1 using XDA Free mobile app
cleonardo said:
i just complete video clip , its really easy my friend https://www.youtube.com/watch?v=v_NMsLLxUuw&feature=youtu.be
Click to expand...
Click to collapse
Can you send us the link for the ROM you used.. Thanks
Sent from my N1 using XDA Free mobile app
link dowload rom 2.0 is new ,14/7th , its upgrade from rom coloros 2.0 , 9/5th . here. http://pan.baidu.com/s/1c08EuXE
my oppo n1 is dead
my oppo n1 is dead give me a link to repair my oppo n1
please help my oneplus 3 can't boot to system or recovery after unbricking with mega unbrick method 1 and 2
the phone boot to black screen and led notification shining white
i try unbricking method again and flash recovery from fastboot dosn't work
sorry my english
Did you solved? I have the same issue ... No ideea what to do... How did you solved?
bibiii79 said:
Did you solved? I have the same issue ... No ideea what to do... How did you solved?
Click to expand...
Click to collapse
If you follow the instructions for method 2, and repeatedly do it a few times, you can succeed. The important thing is to follow the instructions strictly, however silly they may look like.
I did several times, double checking all steps, still boot loop. After apply the method 2 , is doing a boot loop. Than I tried to apply again method 2 I have the successful download with green ...than I go in recovery and flash over adb sideload oos 3.2.8 ...than I start , no more boot loop, but after Oneplus logo goes into black screen with a withe stable notification led turned on ....I left over night ... But it keep staying like that until I force to power off by pressing and holding power button( after I want to turn off i cannot only going into bootloader and from there I choose power of, because is automatically turning on if I press and hold only the power button in order to turn off the device).
Pfiu difficult... I am thinking, some files are missing, this , and where I go in bootloader in missing the values on. Bootloader version- , and baseband version- ....
bibiii79 said:
I did several times, double checking all steps, still boot loop. After apply the method 2 , is doing a boot loop. Than I tried to apply again method 2 I have the successful download with green ...than I go in recovery and flash over adb sideload oos 3.2.8 ...than I start , no more boot loop, but after Oneplus logo goes into black screen with a withe stable notification led turned on ....I left over night ... But it keep staying like that until I force to power off by pressing and holding power button( after I want to turn off i cannot only going into bootloader and from there I choose power of, because is automatically turning on if I press and hold only the power button in order to turn off the device).
Pfiu difficult... I am thinking, some files are missing, this , and where I go in bootloader in missing the values on. Bootloader version- , and baseband version- ....
Click to expand...
Click to collapse
The bootloader and baseband versions were missing when i bought the phone new and are still blank today after flashing a few ROMs and Recoveries/Firmware and modems. So that is not an issue.
Are you downloading the correct files?
tnsmani said:
The bootloader and baseband versions were missing when i bought the phone new and are still blank today after flashing a few ROMs and Recoveries/Firmware and modems. So that is not an issue.
Are you downloading the correct files?
Click to expand...
Click to collapse
Yes, I am using the unbrick method with msm download tool, using the Method 2, after apply, installing all's the Qualcomm drivers 9008 , drivers signature off in windows.... The unbrick tool is passed with the green message .... Reversing back to oos 3.1.2 Android 6.0.1 ..stock, I have recovery working and bootloader also working, bootloader is locked ....so I cannot do too mutch. I start the device right away after unbrick tool and still boot to op logo that is going to vibrate as restart .... And stays in boot loop. Next step I go into recovery , and do over sideload an update with a full ROM, oos 4.0.1 , also tried with full ROM 3.2.8 ...I can sideload the whole ROM , than i start the device and after op logo goes in black screen and white motivation led lighted .... I leave it for 30 min, and still in the same, now I force turn off by going into bootloader and power off. Notice that after this sideload flash I cannot access the recovery. So I need to apply back the unbrick msm download tool for op3.
I tried also to flash over sideload a signed script from Ahmed , unified toolkit , to activate the USB debugging, but gives an error.
I run out of ideas .....any help is welcome ....
Thanks
bibiii79 said:
Yes, I am using the unbrick method with msm download tool, using the Method 2, after apply, installing all's the Qualcomm drivers 9008 , drivers signature off in windows.... The unbrick tool is passed with the green message .... Reversing back to oos 3.1.2 Android 6.0.1 ..stock, I have recovery working and bootloader also working, bootloader is locked ....so I cannot do too mutch. I start the device right away after unbrick tool and still boot to op logo that is going to vibrate as restart .... And stays in boot loop. Next step I go into recovery , and do over sideload an update with a full ROM, oos 4.0.1 , also tried with full ROM 3.2.8 ...I can sideload the whole ROM , than i start the device and after op logo goes in black screen and white motivation led lighted .... I leave it for 30 min, and still in the same, now I force turn off by going into bootloader and power off. Notice that after this sideload flash I cannot access the recovery. So I need to apply back the unbrick msm download tool for op3.
I tried also to flash over sideload a signed script from Ahmed , unified toolkit , to activate the USB debugging, but gives an error.
I run out of ideas .....any help is welcome ....
Thanks
Click to expand...
Click to collapse
Hi bro, did you solved it? Im facing the same problem here
bluuquthug said:
Hi bro, did you solved it? Im facing the same problem here
Click to expand...
Click to collapse
Unfortunately not yet ... Yes I solve it, I bought a Moto Z with dual SIM and snapdragon 820 and 64 GB and SD card with 280 euro .... I am disappointed at the moment about Oneplus 3 , I was a Nexus fan and switched to oneplus ... I thought will be opensource ... But way to expensive repair this done in service , Easter to buy another one ... You save time .. you cannot save money on it ..
bibiii79 said:
Unfortunately not yet ... Yes I solve it, I bought a Moto Z with dual SIM and snapdragon 820 and 64 GB and SD card with 280 euro .... I am disappointed at the moment about Oneplus 3 , I was a Nexus fan and switched to oneplus ... I thought will be opensource ... But way to expensive repair this done in service , Easter to buy another one ... You save time .. you cannot save money on it ..
Click to expand...
Click to collapse
Had the same problem with my oneplus x.
P
oneszero said:
Had the same problem with my oneplus x.
Click to expand...
Click to collapse
And what was the end of your story with Oneplus x?
bibiii79 said:
P
And what was the end of your story with Oneplus x?
Click to expand...
Click to collapse
RMA'd it to a service center for repair, after two tech support calls. They actually told me that they couldn't repair it due to "water damage." Funny thing is, that phone was never dropped in or on anything, let alone in WATER. Then to add insult to injury they refused to send it back to me stating that I had to pay for return shipping. My wife got on the phone with them and by the end of the phone call they said that they would send it back for free. HAHA. So I bought a Oneplus 3 after that whole ordeal. All the while the Oneplus X sat in the box on my desk for about 5 months. Last week I decided to pick it up and tinker with it some more. I scoured the net trying to find any other programs or solutions that I hadn't tried prior to sending it off. I came across somethings that I hadn't seen before. https://forum.xda-developers.com/oneplus-x/help/fastboot-mode-available-stuck-kindly-t3387918. http://rootmygalaxy.net/oneplus-x-s...w.pickmod.com/rom/4187/coloros-for-oneplus-x/. Ended up flashing Color OS via msm tool. Wouldn't load OS, but i didn't end up with a black screen and white LED, it just sat there. So right after I flashed Color OS, i Flashed the mini unbrick tool by Naman, and BOOM it booted into OS. Hope this helps.
I tried to root my phone last night, but I stop midway of the process because of some problems like "phone not turning on with no vibrate at all when I restart after its stuck to inverted white screen, when I luckily turn it back on but it bootloops".
Heres the details:
I run unlock.bat then after its done it reboots with inverted white screen with logo then I run restore.bat and after it restart there is no sign of warning "failed verification" until it fully loads up, I go back to fastboot again to flash TWRP after running twrp.bat it says "flash succesfully" and the program closed by itself, then I go to recovery mode after rebooting I saw android error just like how it use to be. I press power button + volume up then release the volume up then I see the stock recovery (which it should be TWRP since I've done flashing it).
I think that my bootloader is still locked since there's no warning display of "failed verification". So I repeat the steps again after running unlock.bat, it reboots and the screen is inverted but it's stuck up to white logo, I waited for a while but nothing happens so I tried to reboot my phone "holding power button (power off)" when power on, it wont turn on, no vibration just a sound on laptop "connected sound and disconnected sound" I tried to power it on many times but still no luck I got panicked, jittery walking back and forth :crying:. Then I disconnect the usb cable and I tried to turn it on and suddenly I feel the vibration on my phone then it boots up but still stuck in white screen then it restart after keeping it for too long (while watching videos related to my problem)...
then my friend here said "ohh it bootloop" he read the instruction and he said to try this
"FAQ 1. Stuck at white screen with asus logo?
Sol. a) White screen means you are unlocked (action of unlock.bat), so you may give a try to restore.bat in fastboot mode."
and it solve my problem my phone is working again ... But I want to continue to root it but I'm afraid which steps I should go next, I still don't see the warning "failed verification" after my phone boots up and works again... I need HELP thank you
I also got question: is my bootloader unlock since it inverted white screen? or it still locked since there no sign of warning "failed verification"?
@PrinceLys
What is your build number in settings ,about phone ?
timbernot said:
@PrinceLys
What is your build number in settings ,about phone ?
Click to expand...
Click to collapse
ahmm I think this?
model number: ASUS_Z00AD
android version: 6.0.1
software information: WW_4.21.40.223_20161216
P.S my phone is back on working state.
I just don't know if I can proceed to root after the incident. I don't know, I just want to make sure that my bootloader is still unlocked after what I've done (it did white screen with black asus logo) or.... it doesn't unlocked at all since I don't see this warning "your device has failed verification and may not work properly." (I've attach screenshot from the video tutorial)
I tried to manualy check if my bootloader is really on unlock state but I can't using these methods
method 1: on device’s dialer dial *#*#7378423#*#* (failed)
method 2: fastboot oem device-info (failed)
my recovery it still on stock recovery even after I flash twrp
btw guide source: https://forum.xda-developers.com/zenfone2/general/root-install-xposed-marshmallow-6-0-1-t3456443
Q: should I still continue to flash twrp until it install?
Theres 2 bootloader unlock tools in general section , one is automatic
Read this from start to finish before doing anything.. also have on another device to refer to as you are doing the steps also download the ROM and gapps you want and put on SD card before you start even if you have to download them and move them from PC to SD card. https://plus.google.com/113955136844726294013/posts/aLJdNZN3g8q
Sent from my ASUS_Z00A using Tapatalk
timbernot said:
Theres 2 bootloader unlock tools in general section , one is automatic
Click to expand...
Click to collapse
I'm going to look for it... thanks
musicman5844 said:
Read this from start to finish before doing anything.. also have on another device to refer to as you are doing the steps also download the ROM and gapps you want and put on SD card before you start even if you have to download them and move them from PC to SD card. https://plus.google.com/113955136844726294013/posts/aLJdNZN3g8q
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I've haven't fully read the instruction maybe tomorrow I will read it.
I just downloaded the files early and look into it... it seems like the versions are kinda latest (I don't know much about the droidboot ver. but I just look at the number on it "the higher the latest /heh") also the twrp is 3.0.3.
the ones that I used are all in package and it was 3.0.2 so I kinda go for the link you gave me
Thanks :good:
Hi,I've had the same situation,but it is solved now.If you have any problem,maybe I can help you .
nanobrain---- said:
Hi,I've had the same situation,but it is solved now.If you have any problem,maybe I can help you .
Click to expand...
Click to collapse
(I've finally think my bootloader is unlock after all.)
btw, did you succesfylly flash twrp?
Mine didn't flash (using twrp.bat), I guess I will try it again tonight if it fails again im gonna dl twrp from official and manually flash it.