Related
Hi everyone, I'm in major trouble right now.
I just flashed a modem package from this link
https://www.androidfilehost.com/?fid=23578570567721897
and now I cant get to recovery or fastboot and of course cant boot up. Caan anyone help?
I flash using nameless latest twrp and my rom is Omni 6.0 test build.
Hey I have one problem here..
Im using oppo find7a Android 5.0 color os 2.1.5..
Already root using kingroot..
I want to flash to other os like cyanogen, gummybaer, miui etc
I follow all the step on many video on YouTube using TWRP ..
After I flash twrp recover img and reboot, it stuck on fastboot menu
It cannot enter the recovery menu
How do I solve this problem so I can do wipe cache and flash other os
Some people say I must unlock the bootloader so that I can enter TWRP recovery menu
Shouheng said:
Hi everyone, I'm in major trouble right now.
I just flashed a modem package from this link
https://www.androidfilehost.com/?fid=23578570567721897
and now I cant get to recovery or fastboot and of course cant boot up. Caan anyone help?
I flash using nameless latest twrp and my rom is Omni 6.0 test build.
Click to expand...
Click to collapse
Hello, almost the same happend to me.....flashed modem package on nameless ROM.
After reboot, the phone si completely dead.
No vibration, no fastboot, no recovery.....
Did you manage somehow to solve this????
EDIT: found this guide and it works http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=
tw9 said:
Hello, almost the same happend to me.....flashed modem package on nameless ROM.
After reboot, the phone si completely dead.
No vibration, no fastboot, no recovery.....
Did you manage somehow to solve this????
EDIT: found this guide and it works http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=
Click to expand...
Click to collapse
What's your device model name? After unbrick mobile data working fine?
My device is X9006 and on latest Nameless nightly everything is ok.
tw9 said:
My device is X9006 and on latest Nameless nightly everything is ok.
Click to expand...
Click to collapse
Can you give me like of drivers? I used one in unbrick tool but it is not getting installed
I have no other drivers than those in the unbrick thread.
There is also a process of installing them described, which is tricky, because the drivers are not digitally signed.
If you are on windows 7, you must put them in test mode....don't know how it is with other versions of windows, because I used my older machine with W7 for unbricking.
It is all there, in the unbrick thread.....If I remember correctly....
tw9 said:
I have no other drivers than those in the unbrick thread.
There is also a process of installing them described, which is tricky, because the drivers are not digitally signed.
If you are on windows 7, you must put them in test mode....don't know how it is with other versions of windows, because I used my older machine with W7 for unbricking.
It is all there, in the unbrick thread.....If I remember correctly....
Click to expand...
Click to collapse
Finally unbrciked the device using that guide and after some workarounds got 3g working. But the biggest problem I am facing now is. I am stuck in stock 1.2..5i with twrp 2.7.0 can't old backup are not showing in recovery also can't flash anything. No system update. Flashing nameless Rom latest results in updater script error. Tried flashing latest twrp but it will reboot to system every time I try to boot into recovery. Sorry for my bulky English.
Yes, this exact problem I had also to face.
And I don't remember it exactly, but If I'm not mistaken, I flashed the original ColorOS recovery, did some updates and finally then I ended up with ColorOS 2.1.5i, I think.....
From that point TWRP recoveries worked alright, even the newest versions.
If you managed to unbrick your device, this is piece of cake, just remember - you need original ColorOS recovery firstly.
tw9 said:
Yes, this exact problem I had also to face.
And I don't remember it exactly, but If I'm not mistaken, I flashed the original ColorOS recovery, did some updates and finally then I ended up with ColorOS 2.1.5i, I think.....
From that point TWRP recoveries worked alright, even the newest versions.
If you managed to unbrick your device, this is piece of cake, just remember - you need original ColorOS recovery firstly.
Click to expand...
Click to collapse
Thank you for your reply mate. Now flashed cm13 nightly using 2.8.4 I will be selling this phone ASAP. This fourm is almost inactive.
EDIT: Resolved by following Naman Bhalla's Unbrick Guide.
I'm on latest Freedom OS community build right now. I have this problem where my OP3 won't boot into recovery at all. Trying to do it just kills it and only a very long power button press is able to revive it.
I have tried flashing the recovery via fastboot but that also doesn't work. Is there a way out of it? I can't flash zips. Are there factory images I can flash via fastboot that can replace everything? I don't care about the data. Any help would be appreciated.
flash modified recovery via fastboot
Sent from my ONEPLUS A3003 using Tapatalk
I have tried Garak's TWRP and the other TWRP. It doesn't change anything. Are there factory images like Google provides which can be flashed using fastboot?
i have the same problem, flashed the previouse version of Oxygen OS. But now i can't get in to recovery.. when i flash it trough fastboot everything goes ok, but when i want to go into recovery the screen is blank and the device does nothing.
Maybe read the OP of FreedomOS rom.
NevaX1 said:
Maybe read the OP of FreedomOS rom.
Click to expand...
Click to collapse
I have read the OP of Freedom OS. I understand that obviously I overlooked something because of which I ended up where I am but I am looking for solutions here. I did not dirty flash the community build if that's what you mean.
n33raj18 said:
I have read the OP of Freedom OS. I understand that obviously I overlooked something because of which I ended up where I am but I am looking for solutions here. I did not dirty flash the community build if that's what you mean.
Click to expand...
Click to collapse
You need the modified twrp version, the only way to recognize it, it has a mouse cursor in the middle of your screen.
n33raj18 said:
I'm on latest Freedom OS community build right now. I have this problem where my OP3 won't boot into recovery at all. Trying to do it just kills it and only a very long power button press is able to revive it.
I have tried flashing the recovery via fastboot but that also doesn't work. Is there a way out of it? I can't flash zips. Are there factory images I can flash via fastboot that can replace everything? I don't care about the data. Any help would be appreciated.
Click to expand...
Click to collapse
I tried that I got the same error and wipe everything even internal then got a thread in unbrick oneplus 3 and it worked try method 2 link (http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700)
NevaX1 said:
You need the modified twrp version, the only way to recognize it, it has a mouse cursor in the middle of your screen.
Click to expand...
Click to collapse
I had the same problem with 'no recovery' and this helped!
Thanks!
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
vvverma said:
I tried that I got the same error and wipe everything even internal then got a thread in unbrick oneplus 3 and it worked try method 2 link (http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700)
Click to expand...
Click to collapse
Yea, I used exactly the same thing to get back my device working correctly again. I missed the crucial information that modified TWRP was required.
Hi
Can anyone help with this ?
I am stuck on a Linux logo on my screen
I am unable to go into recovery or Bootloader mode
However if I Fastboot, it recognize the device
I tried flashing the recovery image and It Flashed successfully; Yet I cannot boot into Recovery
I tried Flashing the the Bootloader and the same
Funny thing is all Fastboot commands seem to work, like rebooting the Bootloader, but it goes straight to the Linux logo
see picture attached
Thank you.
Voyebanm said:
Hi
Can anyone help with this ?
I am stuck on a Linux logo on my screen
I am unable to go into recovery or Bootloader mode
However if I Fastboot, it recognize the device
I tried flashing the recovery image and It Flashed successfully; Yet I cannot boot into Recovery
I tried Flashing the the Bootloader and the same
Funny thing is all Fastboot commands seem to work, like rebooting the Bootloader, but it goes straight to the Linux logo
see picture attached
Thank you.
Click to expand...
Click to collapse
Did you erase the system? If not try to flash for fastboot just boot.img, maybe help you, if don't reboot flash the entire rom image
I was testing volte.zip. I already tried flashing the boot file, still nothing. I tried flashing miui global fastboot with miflash still no luck. It sees the device but flashed for 5s and then said successful.
did u check "clean all" and try edl mode (just a reminder,it happened to me many times,i was impatient/panicked forgot to check "clean all")
Voyebanm said:
I was testing volte.zip. I already tried flashing the boot file, still nothing. I tried flashing miui global fastboot with miflash still no luck. It sees the device but flashed for 5s and then said successful.
Click to expand...
Click to collapse
I have never seen this linux logo before on Mi Max and I can assure you I am on top of everything happening around it...
I think you did something hmmm... excuse me but stupid... That volte.zip is for kenzo and it flashes all partitions that you are not supposed to flash with anything but hydrogen specific images... Your only option is EDL mode flashing and I am not even sure if it is going to work.
Good luck...
nijel8 said:
I have never seen this linux logo before on Mi Max and I can assure you I am on top of everything happening around it...
I think you did something hmmm... excuse me but stupid... That volte.zip is for kenzo and it flashes all partitions that you are not supposed to flash with anything but hydrogen specific images... Your only option is EDL mode flashing and I am not even sure if it is going to work.
Good luck...
Click to expand...
Click to collapse
No Luck so far.
Voyebanm said:
No Luck so far.
Click to expand...
Click to collapse
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
SubwayChamp said:
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
Click to expand...
Click to collapse
I will give that a try. Thanks
http://en.miui.com/a-234.html
Install MiFlash from Xiaomi, download fastboot image and unpack it.
http://xiaomitips.com/guide/how-to-put-mi-max-into-edl-mode/
Boot to EDL mode with hard keys method, screen stays black, but Qualcomm QH USB device shows up in Device Manager/Ports. MiFlash fastboot image.
If you have 8 or newer Windows, you have to boot it driver signature verification disabled before MiFlash install:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
SubwayChamp said:
That seem be a similar case at inverse (Hydrogen on Helium) but maybe help you: http://forum.xda-developers.com/showpost.php?p=68205960&postcount=24
Click to expand...
Click to collapse
Thank you all for the suggestions, but this helped me to fix the problem and it was easy to perform
PS: I spoke too fast now my SIM card is not detected, in both slots
Voyebanm said:
Thank you all for the suggestions, but this helped me to fix the problem and it was easy to perform
PS: I spoke too fast now my SIM card is not detected, in both slots
Click to expand...
Click to collapse
What did you do to understand, maybe wrong firmware, maybe just a problem of modem partition, if you are using DualBootPatcher try with a CM based rom like primary, other possibility is to flash just NON-HLOS.bin of corrrect rom in fastboot mode, maybe wrong file in Update Firmware folder (in zip rom), go with a file explorer to /data/nvram if it`s generated for the new rom, take a backup first and delete after, reboot device (if this is the case) and check again your sim.
SubwayChamp said:
What did you do to understand, maybe wrong firmware, maybe just a problem of modem partition, if you are using DualBootPatcher try with a CM based rom like primary, other possibility is to flash just NON-HLOS.bin of corrrect rom in fastboot mode, maybe wrong file in Update Firmware folder (in zip rom), go with a file explorer to /data/nvram if it`s generated for the new rom, take a backup first and delete after, reboot device (if this is the case) and check again your sim.
Click to expand...
Click to collapse
Thank you though, I was able to resolved it by flashing the EFS backup that I had.
Problem SOLVED !!!
Thanks again for your Help.
I got a bricking when I tried flashing MIUI EU ROM over CM on a locked bootloader. Is there a way to flash the latest firmware files without also flashing a new boot image which could brick the phone? I had to do an EDL flash using MiFlash last time, I don't want to go through the hassle again.
Hi guys, I searched around the forum before posting this so I apologize but I recently installed a new rom and possibly a wrong kernel with it. Afterwards, if I try to turn it on, it just shows the logo and then turns right off. I can't even go into recovery since it does the same. The only thing I can do is boot it into fastboot but I'm not sure where to go from here. I tried using a guide with no success.
Any words of wisdom?
reflash your recovery via fastboot, then boot into recovery and do a clean install
fastboot flash [recovery].img
I tried reflashing recovery but all it does is show the old rom logo that was used and then shuts down.
Hi,
Read carefully and try this guide:
forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
which rom did you flash? You need the correct twrp file for your bootloader.
That's the first place I tried. Anytime I hook-up my phone to the PC it shows up as OnePlus Android bootloader interface under Android phone and I can't seem to update the drivers..
matze19999 said:
which rom did you flash? You need the correct twrp file for your bootloader.
Click to expand...
Click to collapse
I used the Freedom Rom 2.0
Arken2121 said:
I used the Freedom Rom 2.0
Click to expand...
Click to collapse
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835
matze19999 said:
you need this twrp file:
https://forum.xda-developers.com/devdb/project/dl/?id=21835
Click to expand...
Click to collapse
Thank you so much, I guess I installed the wrong TWRP and I can FINALLY get into recovery. Thank you so much.
Hi! Sorry about my english.
I have a problem with my oneplus 3.
Did the unbrick with msmdownload tool, worked.
Bootloader is unlocked.
Did the fastboot recovery flash of the modified twrp 3.0.2-1.28
When i want to start twrp it stucks at one plus logo screen.
When i flash an older twrp version (don´t know which one, 3.0.2.1) it boot into twrp. but i cant flash any rom. Its getting stucked at installing (tried a view roms).
What did i wrong?
branvan said:
Hi! Sorry about my english.
I have a problem with my oneplus 3.
Did the unbrick with msmdownload tool, worked.
Bootloader is unlocked.
Did the fastboot recovery flash of the modified twrp 3.0.2-1.28
When i want to start twrp it stucks at one plus logo screen.
When i flash an older twrp version (don´t know which one, 3.0.2.1) it boot into twrp. but i cant flash any rom. Its getting stucked at installing (tried a view roms).
What did i wrong?
Click to expand...
Click to collapse
Are you on OOS4? If so try 3.0.2.19 of TWRP or the bluspark version 11 by eng.stk
no, @ stock OOS 3.2.8
ok did the update to oos 4.0 now.
and doestn work...
i have no idea
Try: "fastboot erase recovery" then "fastboot flash recovery recoveryfilename.img".
Otherwise try re-downloading it.
thanks, but no success
when i flash modified twrp, get stuck into booting to twrp.
after rebooting oos4 and reboot to recovery, original recovery is getting started.
Tried everything now for hours. Without getting a working twrp. Has anyone the same problem?
branvan said:
Tried everything now for hours. Without getting a working twrp. Has anyone the same problem?
Click to expand...
Click to collapse
I have the same issue, I'm on OOS4.0.1 and TWRP won't boot, tried the blu sparks one and the one included in the toolkit 3.7
Neither would boot, just stuck at their splash screens. I'm also looking for an answer.
do you have the dm-verity screen too at booting?
xT-g-K said:
I have the same issue, I'm on OOS4.0.1 and TWRP won't boot, tried the blu sparks one and the one included in the toolkit 3.7
Neither would boot, just stuck at their splash screens. I'm also looking for an answer.
Click to expand...
Click to collapse
Did you solved the Problem?
branvan said:
Did you solved the Problem?
Click to expand...
Click to collapse
I flashed the blu_sparks one again, worked that time just has abnormally long boot times.
branvan said:
Hi! Sorry about my english.
I have a problem with my oneplus 3.
Did the unbrick with msmdownload tool, worked.
Bootloader is unlocked.
Did the fastboot recovery flash of the modified twrp 3.0.2-1.28
When i want to start twrp it stucks at one plus logo screen.
When i flash an older twrp version (don´t know which one, 3.0.2.1) it boot into twrp. but i cant flash any rom. Its getting stucked at installing (tried a view roms).
What did i wrong?
Click to expand...
Click to collapse
I recently posted a guide to solves issues like that. Here it is: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
I hope it helps.
There is a lot of reading there. So, read it carefully before proceeding any further.
---------- Post added at 11:37 PM ---------- Previous post was at 11:34 PM ----------
xT-g-K said:
I flashed the blu_sparks one again, worked that time just has abnormally long boot times.
Click to expand...
Click to collapse
Just a little bit.
Check this: https://forum.xda-developers.com/showpost.php?p=70541567&postcount=2522