Develop Bugs

[Q] evo wont boot and RUU fails with error

I tried one of the rooting processes today and it didn't work. Now when I turn my Evo on it goes no further than the white HTC screen that you get when you turn it on. When I try to run the RUU it gets a connection error and won't go through. Can someone please help?

Robes1 said:
I tried one of the rooting processes today and it didn't work. Now when I turn my Evo on it goes no further than the white HTC screen that you get when you turn it on. When I try to run the RUU it gets a connection error and won't go through. Can someone please help?
Click to expand...
Click to collapse
If you pull the battery can you get to the bootloader screen? (hold volume down and power button when turning on)

You should be able to do what Greenfieldan suggests. It is possible to work through this issue, so don't fear but it make take a few tries.

Greenfieldan said:
If you pull the battery can you get to the bootloader screen? (hold volume down and power button when turning on)
Click to expand...
Click to collapse
once I get to this screen how do I get the RUU to connect to the phone? I've tried it several times from this screen and nothing is working.

Robes1 said:
once I get to this screen how do I get the RUU to connect to the phone? I've tried it several times from this screen and nothing is working.
Click to expand...
Click to collapse
Thread stalking is fun, I see which thread you are reading, but you may have to reset you phone.
Do you either:
Have a recovery installed (if you aren't sure, then you may not)
have a PCIMG36 on the root of your sdcard, (if you aren't sure then you may not)

Robes1 said:
once I get to this screen how do I get the RUU to connect to the phone? I've tried it several times from this screen and nothing is working.
Click to expand...
Click to collapse
Go in to fastboot and you should see something toward the top that says "FASTBOOT USB", once there run the RUU

SnoopDawg said:
Thread stalking is fun, I see which thread you are reading, but you may have to reset you phone.
Do you either:
Have a recovery installed (if you aren't sure, then you may not)
have a PCIMG36 on the root of your sdcard, (if you aren't sure then you may not)
Click to expand...
Click to collapse
I have a pc36img file on the root of my sd card. It says that it can't open it when i select flash zip from sd card.

Just download the actual ruu from http://forum.xda-developers.com/showthread.php?t=884060. It will be one of the .exe files same version of you had on the phone will prolly work best. Then do what xhausx said and run the ruu file once there. Thanks xhausx btw cause i was confused too.

aclearersky said:
Just download the actual ruu from http://forum.xda-developers.com/showthread.php?t=884060. It will be one of the .exe files same version of you had on the phone will prolly work best. Then do what xhausx said and run the ruu file once there. Thanks xhausx btw cause i was confused too.
Click to expand...
Click to collapse
or download an unrooted version of your software in pc36img.zip format and boot into the bootloader and it will restore your phone to stock if you cant run any ruu

Need Help
I know this is an old thread, but I'm working on an old phone. Hopefully some of you guys are still following this.
My father has an EVO 3D that showed up one day stuck on the white HTC screen. The only remedy was to pull the battery. I thought it would be no big deal to just go into the boot menu and either try and run recovery, or at worst do a factory reset. Both of these options failed. I even made a few attempts at trying from the SD card with a ROM or two. So I downloaded the RUU direct from HTC thinking that would finally take care of the problem. But after connecting up in FASTBOOT mode and running the RUU, it eventually fails when the update gets to the point that it's supposed to restart the phone in bootloader mode. Because at that point the phone just restarts to the white HTC logo again, and the software times out telling me that it can't connect to the device. Any help here other than passing me a trash can Thanks in advance!

Unable to get into bootloader or recovery mode, stuck at white HTC logo screen

Hey everyone,
I have read the various topics with a similar title but none helped.
Here is my problem, I bought a used HTC Desire on eBay. It booted just fine on the first start, then I did a factory reset (from within the Android system menu).
Since then, I'm stuck at the white screen with the green HTC logo. I have tried to get into bootloader mode by removing the battery, holding vol down and power, but it just goes straight to the white screen again.
Also connected the phone to the pc, but adb isn't picking up anything...
Any ideas?

Try Power+Back button.

just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?

Goddchen said:
just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?
Click to expand...
Click to collapse
So you bought a Desire with broken volume keys.
Are you s-off?

abaaaabbbb63 said:
So you bought a Desire with broken volume keys.
Are you s-off?
Click to expand...
Click to collapse
looks like...
in fastboot mode it shows that it is s-on.

Goddchen said:
looks like...
in fastboot mode it shows that it is s-on.
Click to expand...
Click to collapse
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot

abaaaabbbb63 said:
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot
Click to expand...
Click to collapse
Thanks for the advice, I downloaded the 2.3 RUU and it starts the process, sais
rebooting to bootloader
erasing data
sending...
and after ~30 seconds it just shows me a screen that sais "ERROR_UNKNOWN"
On the phone I see a black screen with a silver HTC logo during the process and when I unplug the USB cable after the error it shows the hboot screen that now sais "update failed".

right before the error is shown it display "updating signature"

Goddchen said:
right before the error is shown it display "updating signature"
Click to expand...
Click to collapse
It only says "Error_Unknown"? No error number, anything?
Weird.
This may be the reason:
Now, that may not sound too bad to some of you, but there's more: the 2.3 RUU update is limited regionally, as well. It's not available to users in Germany, North America, South America, South Korea, or Japan.
Click to expand...
Click to collapse
You live in Germany, right?
Use this guide then:
Section 2, S-on
http://forum.xda-developers.com/showthread.php?t=1275632

yes I am in Germany,
made some progress (or not?)
I noticed that the device was "unlocked", so I did "fastboot oem lock" and it was "relocked".
Then the RUU update went through - nearly. At the very end if failed again and now I am stuck at a black screen with the silver HTC logo and triangles in every corner.

AW: Unable to get into bootloader or recovery mode, stuck at white HTC logo screen
Sent from my Nexus 4 using xda app-developers app

wtf... tried again flashing the 2.3 RUU, this time it worked, YEAY
But now I have a bootloop, device starts, vibrates 1 time, waits for 3 seconds, and then vibrates 7 times. And restarts...

Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369

abaaaabbbb63 said:
Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369
Click to expand...
Click to collapse
freecer did it, was able to flash the 2.3 RUU again successfully. But now I'm back at the bootloop, but now, it simply does vibrate once (no more 7 vibrations) and reboots after some seconds.
So what can I do now? RUU flashed successfully, I'm running out of ideas...

and again the freezer did it, put it in, normally started via POWER button, it booted right through into Android.
Well, let's see if it keeps running now or if this overheating issue also exists in normal operation mode...
Thanks so much for you help so far, the freezer hint saved this device and hopefully will make my gf very happy tomorrow

Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app

dethrat said:
Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.

do you think installing a custom rom of any kind might help?

Goddchen said:
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.
Click to expand...
Click to collapse
It's a motherboard fault. If you don't send it to repair, you just got yourself an "Ice-Phone", or a very complex paper holder.

i think a custom rom would help a small bit, like the rom in abaaaabbbb63 sig (mildwild redux) because its small and lite unlike a sense rom. therefor it mite not overheat as quick or as often. but thats only a guess. the only dodgy thing is trying to get ur phone s-off or rooted because if ur phone overheats in the middle of the s-off/rooting progress u could brick ur phone. plus charge ur phone using ur computer coz it uses less power and the phone does'nt heat up as much as plugging into the wall.

[Q] Galaxy Nexus shows "No Command" after Recovery

I have a Galaxy Nexus, GSM version. It was working fine about ~3 weeks ago. I turned it off and removed the SIM card as I upgraded to a new phone.
Now I've turned it on and it just hangs on boot showing the animated X.
I tried recovery mode and get a "No Command" error.
I've never done anything to this phone before, in other words it's just running standard Android. Any advice? I've looked through some past posts but it seems like a lot of people have rooted the phone with custom OS, etc. I've never done any of that. So trying to figure out what the issue is with this phone. Any advice would be appreciated.
Thanks,
GR

<BUMP> sorry for pinging on this again but haven't seen any replies and I'm stuck... not able to get the phone to start. Any help would be much appreciated. Not sure if anyone else has had this problem? Thanks so much. GR
GR5000 said:
I have a Galaxy Nexus, GSM version. It was working fine about ~3 weeks ago. I turned it off and removed the SIM card as I upgraded to a new phone.
Now I've turned it on and it just hangs on boot showing the animated X.
I tried recovery mode and get a "No Command" error.
I've never done anything to this phone before, in other words it's just running standard Android. Any advice? I've looked through some past posts but it seems like a lot of people have rooted the phone with custom OS, etc. I've never done any of that. So trying to figure out what the issue is with this phone. Any advice would be appreciated.
Thanks,
GR
Click to expand...
Click to collapse

GR5000 said:
<BUMP> sorry for pinging on this again but haven't seen any replies and I'm stuck... not able to get the phone to start. Any help would be much appreciated. Not sure if anyone else has had this problem? Thanks so much. GR
Click to expand...
Click to collapse
when you see this "no command", press power + volume up to see the recovery menu

Thank you so much for the info. I'm trying this when I see the no command screen but nothing happens. The phone is just completely locked / frozen. I have to remove the battery. Any additional help would be much appreciated!
Thanks,
GR
samersh72 said:
when you see this "no command", press power + volume up to see the recovery menu
Click to expand...
Click to collapse

Maybe you don't even have a custom recovery installed yet? Not necessary, but since custom recovery are far more convenient than the stock one, you might wanna give it a try.
Sent from Google Nexus 4 @ CM11

The phone is completely stock. I've never done anything to it so not sure why I'm having this issue to begin with. But what custom recovery would you recommend I try? Is there a link that you can send me? And how would I install it given that I cannot even get the phone to boot?
Thank you
AndyYan said:
Maybe you don't even have a custom recovery installed yet? Not necessary, but since custom recovery are far more convenient than the stock one, you might wanna give it a try.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse

GR5000 said:
And how would I install it given that I cannot even get the phone to boot?
Click to expand...
Click to collapse
Hold both VOLUME+ and VOLUME- keys, and while holding, long press POWER key. Do you see a green Android robot with its lids open? If yes, you're in fastboot mode, from which you can flash recovery, stock ROM, etc. (but if no...)
I'm on the phone now and can't provide links... Just first tell us whether you could boot into fastboot, will catch up later depending on your answer.
Sent from Google Nexus 4 @ CM11

When the phone is off, if I turn it on it just hangs at the animated X.
When the phone is off, if I press volume up/down + power then yes I see the screen that you're talking about. So I can boot into fastboot. When I choose Recovery Mode it restarts and that's when I get the No Command error.
Thank you so much for your help.
GR
AndyYan said:
Hold both VOLUME+ and VOLUME- keys, and while holding, long press POWER key. Do you see a green Android robot with its lids open? If yes, you're in fastboot mode, from which you can flash recovery, stock ROM, etc. (but if no...)
I'm on the phone now and can't provide links... Just first tell us whether you could boot into fastboot, will catch up later depending on your answer.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse

GR5000 said:
When the phone is off, if I turn it on it just hangs at the animated X.
When the phone is off, if I press volume up/down + power then yes I see the screen that you're talking about. So I can boot into fastboot. When I choose Recovery Mode it restarts and that's when I get the No Command error.
Thank you so much for your help.
GR
Click to expand...
Click to collapse
Install the correct ADB and fastboot drivers and files on your PC (I can't help you with this).
When your GNex is in fastboot, connect it to your PC, wait for it to get recognized.
Download CWM recovery here: http://www.clockworkmod.com/rommanager - you'll have to choose your device variant (GSM/Verizon/Sprint), and choose if you want touch or not. Downloaded file should be an *.img file.
Open a command prompt window on your PC, enter "fastboot flash recovery *PATH-TO-YOUR-RECOVERY*.img" (no quotes). After flashing completes, just boot into recovery and do what you should do.
Sent from Google Nexus 4 @ CM11

Just want to thank everyone for all of the help. I really appreciate it. Andy, I did try several of the steps that you mentioned but for some reason the PC just wouldn't recognize the phone in fastboot mode. I tried both the Google and Samsung drivers.
In my searching I found this post though:
http://forum.xda-developers.com/nexus-4/help/nexus-4-stock-recovery-command-issue-t2113478/page2
And realized that I should check samer's advice again. Turns out that I just wasn't pressing those two buttons in the correct sequence. I was doing it simultaneously and I guess you have to do it serially. At any rate was able to restore factory and now the phone is booting. Wow. What a pain. Still not sure what caused the phone to blow up in the first place.
At any rate really appreciate everyone's help.
Warm regards,
GR
AndyYan said:
Install the correct ADB and fastboot drivers and files on your PC (I can't help you with this).
When your GNex is in fastboot, connect it to your PC, wait for it to get recognized.
Download CWM recovery here: http://www.clockworkmod.com/rommanager - you'll have to choose your device variant (GSM/Verizon/Sprint), and choose if you want touch or not. Downloaded file should be an *.img file.
Open a command prompt window on your PC, enter "fastboot flash recovery *PATH-TO-YOUR-RECOVERY*.img" (no quotes). After flashing completes, just boot into recovery and do what you should do.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse

Motorola G6 Play (Boot loop)

I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy

Perchy35 said:
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Click to expand...
Click to collapse
Just use my guide, at the bottom of it it has everything you need to reflash stock firmware hold the power and volume down button until you get to the fastboot/ bootloader screen, also since you replaced the battery and did your own repair we still might not be able to help you because there's to many variables of user interference now, and yes Google kind of has made it a bit more complicated to root devices now unfortunately

Thanks for the reply, please can you put a link to your guide?

Perchy35 said:
Thanks for the reply, please can you put a link to your guide?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928

Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.

Perchy35 said:
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Click to expand...
Click to collapse
Yes. Hold power and volume down, it'll look a few times and catch, you'll see fastboot. The Android guy and red and white text. May take a few loops

sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?

Perchy35 said:
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Click to expand...
Click to collapse
Whats the carrier?

The phone was bought direct from Amazon so in my mind a generic model to take any SIM.

Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Here you go. Amazon Jeter Firmware. That's the main folder.

I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Spaceminer is correct, once you catch that sweet spot with the phone to get it in bootloader/fastboot mode just flash the firmware and you should hopefully be good to go, if you want it rooted my guide covers that to but let's just get you a working phone first before you try to root lol
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
You can either flash 8 or 9, what I would do is flash 8 then update it to 9 then if you want it rooted root it

Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hey so out of curiosity did you get it fixed and working?

ninjakira said:
Hey so out of curiosity did you get it fixed and working?
Click to expand...
Click to collapse
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
Also can I check that without USB debugging selected this method will override and flash still?

Perchy35 said:
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
I am having issue with the last part, getting "The credentials you provided cannot be determined to be authentic" ?
Also can I check that without USB debugging selected this method will override and flash still?
Click to expand...
Click to collapse
Wait what are you needing your Moto id for? The links for the stock firmware are in my guide, just follow the bottom section of it

Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a

ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..

Perchy35 said:
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
Click to expand...
Click to collapse
If you don't have the bootloader unlocked then that is something you can do if you want the phone rooted if not you don't have to unlock the bootloader to flash stock firmware
Perchy35 said:
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Click to expand...
Click to collapse
You either didn't install adb minimal or you have a bad cord, type fastboot devices and if nothing pops up saying you have a device in fastboot then it's one of the 2 things I said, extract the contents from the rar or zip file you got from adb minimal download, then install what you extracted

I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.

Perchy35 said:
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Click to expand...
Click to collapse
Sorry been at work and I'm ona break, I totally forgot though you can use Moto smart Assistant for pc to fix this more than likely, so download and useMoto smart Assistant

Just UNBRICKED Redmi Note8 PRO - This works need someone to test!!!

So I have bricked my phone for the 3rd time, the last 2 times I had to have someone with an authorized account fix it for me cost was 30EUR. Sucks. I have read every post on here and was just going to toss this thing in the trash after flashing and bricking it last night. This morning I came across a thread claiming if you used the SP Flash Tool with some other files that it would work, it didn't for me but in the process I found another thread talking about holding the volume down key while flashing, it did work. Here are the steps and how did I brick it, I flashed the files from MEGATHREAD so preloader was in place, I had working and install TWRP and was in the process of flashing vendor and PE ROM from TWRP. The zip was corrupted and it wiped me out and before rebooting I got the No OS installed message but figured I would to a clean flash of the OEM image from fastboot. Nope it failed and I got the LED light with nothing else, no boot no fastboot and no recovery. Dead. Here is what I did someone please try this.
I am on a Ubuntu box with ADB and Fastboot installed for the system I assume Windows or MAC would work just have those tools working and installed you must or you wouldn't have bricked your phone. I have begonia_global_images_V11.0.6.0.PGGMIXM_20200108.0000.00_9.0_global ROM and I went to the image directory, and typed:
Code:
fastboot devices
fastboot flash boot boot.img
When it was listed in fastboot devices I was like WHAT??? Sure enough it flashed it but do this right before you issue that command ITS IMPORTANT plug in the phone via USB and hold down the volume down key the phone will within a few seconds vibrate then hit the commands. Please see attached image you can see what I did. After that when I unplugged the phone it freaking booted into the OS and I had to set my phone up again but for the most part and this is weird my data was still intact, I don't care but it was nice. I really don't understand this phone at all but I hope others will try this and unbrick it would be awesome.
DC

dcindallas said:
So I have bricked my phone for the 3rd time, the last 2 times I had to have someone with an authorized account fix it for me cost was 30EUR. Sucks. I have read every post on here and was just going to toss this thing in the trash after flashing and bricking it last night. This morning I came across a thread claiming if you used the SP Flash Tool with some other files that it would work, it didn't for me but in the process I found another thread talking about holding the volume down key while flashing, it did work. Here are the steps and how did I brick it, I flashed the files from MEGATHREAD so preloader was in place, I had working and install TWRP and was in the process of flashing vendor and PE ROM from TWRP. The zip was corrupted and it wiped me out and before rebooting I got the No OS installed message but figured I would to a clean flash of the OEM image from fastboot. Nope it failed and I got the LED light with nothing else, no boot no fastboot and no recovery. Dead. Here is what I did someone please try this.
I am on a Ubuntu box with ADB and Fastboot installed for the system I assume Windows or MAC would work just have those tools working and installed you must or you wouldn't have bricked your phone. I have begonia_global_images_V11.0.6.0.PGGMIXM_20200108.0000.00_9.0_global ROM and I went to the image directory, and typed:
When it was listed in fastboot devices I was like WHAT??? Sure enough it flashed it but do this right before you issue that command ITS IMPORTANT plug in the phone via USB and hold down the volume down key the phone will within a few seconds vibrate then hit the commands. Please see attached image you can see what I did. After that when I unplugged the phone it freaking booted into the OS and I had to set my phone up again but for the most part and this is weird my data was still intact, I don't care but it was nice. I really don't understand this phone at all but I hope others will try this and unbrick it would be awesome.
DC
Click to expand...
Click to collapse
Thanks for sharing this. I've had a bricked rn8 pro for 3 weeks now and none of the other fixes worked for me. I'm looking forward to giving this a try when I get home from work. Perhaps I should've tried using my Kali box rather than windoze in my previous attempts.
I'll update with results if interested.

Hi, what exactly you did? Because I'm tired to test any possible method, I've tried disconnecting the battery, Press Volume - while try to flash, and now I'm waiting to prove the method that drain the battery adn then can connect and flash.
Did you flash with Ubuntu? It works? How can you do it If the phone can't enter to fastboot mode?

To what I understood you unlocked it 3 times and in one of those you updated the preloader?
Because if so. spflash unlocks it without asking for the happy account

Yup on Arch Linux and this worked fine

Melon_Bread said:
Yup on Arch Linux and this worked fine
Click to expand...
Click to collapse
What you did? Pls help ):

GERATKDASD said:
What you did? Pls help ):
Click to expand...
Click to collapse
Made sure the device was off completely, held down VOL-DOWN while pluging in phone and had it show up in my fastboot devices. Reflashed the system via fastboot with the begonia_global_images_V11.0.2.0.PGGMIXM_20191201.0000.00_9.0_global system image (flash-all.sh)

Melon_Bread said:
Made sure the device was off completely, held down VOL-DOWN while pluging in phone and had it show up in my fastboot devices. Reflashed the system via fastboot with the begonia_global_images_V11.0.2.0.PGGMIXM_20191201.0000.00_9.0_global system image (flash-all.sh)
Click to expand...
Click to collapse
I will try, thanks

Still not working ): IDK if I don't doing it right, I don't know, I'm tired of this phone ):

GERATKDASD said:
Hi, what exactly you did? Because I'm tired to test any possible method, I've tried disconnecting the battery, Press Volume - while try to flash, and now I'm waiting to prove the method that drain the battery adn then can connect and flash.
Did you flash with Ubuntu? It works? How can you do it If the phone can't enter to fastboot mode?
Click to expand...
Click to collapse
I already tested battery draining, doesnt worked :/

KonahZave said:
I already tested battery draining, doesnt worked :/
Click to expand...
Click to collapse
Holy cow, and then? now who can help us? ): I don't have 30 bucks right now ._.

Sed lyf
GERATKDASD said:
Holy cow, and then? now who can help us? ): I don't have 30 bucks right now ._.
Click to expand...
Click to collapse
I know how bad it is... Im sorry bro, if this guide couldnt help... then only paying. (╯︵╰,)

KonahZave said:
I know how bad it is... Im sorry bro, if this guide couldnt help... then only paying. (╯︵╰,)
Click to expand...
Click to collapse
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.

pablo159 said:
To what I understood you unlocked it 3 times and in one of those you updated the preloader?
Because if so. spflash unlocks it without asking for the happy account
Click to expand...
Click to collapse
None of that matters and no the preloader was over written, the point here is it was hard bricked only got the white LED light, then I did exactly what I wrote and it saw the phone in fastboot and it wrote the boot.img and then it rebooted and worked. Period. Worked for me. Someone else tested it worked for them. Try it but follow the directions....

dcindallas said:
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.
Click to expand...
Click to collapse
Man, Im not trying this method or such thing, Im not bricked. Im just telling for the dude my old experience with old guides.

dcindallas said:
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.
Click to expand...
Click to collapse
Sorry If I look like an annoying guy that don't understant, but litteraly i've tried that, I opened a Terminal window, typed fastboot devices, holding down volume -, but, IDK, how many time I need to press it;
I need to connect phone before hold the button, or vice versa?

GERATKDASD said:
Sorry If I look like an annoying guy that don't understant, but litteraly i've tried that, I opened a Terminal window, typed fastboot devices, holding down volume -, but, IDK, how many time I need to press it;
I need to connect phone before hold the button, or vice versa?
Click to expand...
Click to collapse
Plug the phone in and hold it down the phone will vibrate keep holding it down and try flashing it continue to hold it down until the flash is successful. All I had to do was flash the boot image but others have flashed_all. Hit me on telegram if you need help @dcindallas

dcindallas said:
Plug the phone in and hold it down the phone will vibrate keep holding it down and try flashing it continue to hold it down until the flash is successful. All I had to do was flash the boot image but others have flashed_all. Hit me on telegram if you need help @dcindallas
Click to expand...
Click to collapse
Ok, so, you only need to installed adb and fastboot right? no drivers or other things?