Develop Bugs

Ouya Bricked ?

Hello !
Here's my prob :
I installed CWM Recovery on my OUYA, and then i wanted to flash a ROM via recovery.
Unfortunately, i've done a full wipe while in recovery, and restarted the console.
Now it's turning on, with the power button on, black screen, and identifyed as an MTP USB device.
I tried the alt + Sysreq + i trick, but it doen't seems to work here ...
Any chance to get it back to life in other way ?

Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything

imerrn said:
Keep trying alt + sysreq + i trick my takes about 50 times before the light on the ouya flashes then i have to hit the home key some times to see anything
Click to expand...
Click to collapse
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?

ElMeteK said:
What timing of button's hitting have you used ?
The light of the OUYA is flashing when in recovery mode ?
Click to expand...
Click to collapse
Try these timings. I had the same issue and these worked for me. The keyboard trick is currently your only hope.

I keep pressing alt + sysreq + i keys at the same time takes me about 30 times to get to recovery the light will flash one time then i know im in recovery some times iget the ouya smile with a ! mark some time a black screen then i press home button to get to recovery push the home button again it goes away i have done about three ouya.

Problem solved.
My ouya doesn't loved my Microsoft Keyboard...
I used a generic on, and it works directly
Ouya saved
Another advice : if it doesn't work, try another keyboard !

Ouya Bricked Need Help Reward For The Fixer
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.

labossiere said:
Here is my Issue I installed The CWM and flashed over a few ROMS but really wanted to try out the CM10. I had all my files backed up but some how they were all deleted and when I turn on my machine I get the Cyanogen boot loop and I can do the keyboard trick print screen/ Alt / I but there is no files to recover and I have no way to load any ROM directly to my internal nand flash unless there is something I am missing.
I am so upset I with thy would have put a sd card slot on this thing. Can anyone help me to try to recover putting any stock ROM back on my machine or is there a way to get my PC to read my device to load the ROM to my internal HD?
Please any help and instructions would be greatly appreciated.
I need some serious help here. Thanks to anyone who can get me back up and running again I will even send the person who has the solution one of my devices that run XBMC like a champ. Here is my site for anyone who is up for the challenge. www.xbmcandroidtv.com the EXOON Q2 Plus is the device I will send to the person who solves my dilemma.
I have tried the keyboard trick but all I get it to do is load into CWM and there is nothing to load. Am I doing something wrong?
Thanks in advance and eager to get my OUYA back up and running.
Click to expand...
Click to collapse
You have to fastboot the "boot.img" supplied with CM10. I had the same issue so pm me if you need help.:good:

Never, ever ever ever ever ever wipe the boot.img, if you want to be safe, never replace it either, you can always 'fastboot boot boot.img" it.
Sent from my SAMSUNG-SGH-I317 using xda premium

at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?

glitchhawk said:
at what point does your Ouya connect back to your pc so you can do a fastboot command? do you have to be in CWM?
Click to expand...
Click to collapse
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.

BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
ok, cuz im basically in the same boat as everyone else. i flashed CM10 and now its hanging at the CM boot screen. so i guess its time to sit there and tap keys for hours lol.

BUS DR1V3R said:
You can do it from CWM, but you don't have to be there. Depends on what you've done to your system. If you flashed CM10 and now it's detected as an MTP device your best bet is to reboot into recovery and 'adb reboot bootloader' then use fastboot commands. That's what worked for me.
Click to expand...
Click to collapse
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu

glitchhawk said:
in stock recovery am i suppose to go into sideload sub menu? my pc doesn't detect the ouya in the main recovery menu
Click to expand...
Click to collapse
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.

BUS DR1V3R said:
How does the Ouya show up in device manager? Is there an exclamation point beside it?
If the drivers are fine then try mounting /data in recovery.
Click to expand...
Click to collapse
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition

glitchhawk said:
sorry, how do i mount it? the only options i have in stock recovery is
Reboot system now
Apply update from ADB (if i go into this menu i have the driver installed on pc and it comes up adb composite device)
wipe data/factory reset
wipe cache partition
Click to expand...
Click to collapse
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.

BUS DR1V3R said:
Ah, stock recovery.... You could go into Apply Update From ADB. Then type "adb reboot bootloader" then you can type "fastboot boot boot.img" to boot successfully into CM10.
You can put the boot.img for CM10 in the same folder as fastboot.exe to make things easier.
Click to expand...
Click to collapse
well this is lame.. it keeps telling me Error: Closed

glitchhawk said:
well this is lame.. it keeps telling me Error: Closed
Click to expand...
Click to collapse
What keeps telling you that? What are you doing? I need more information.

BUS DR1V3R said:
What keeps telling you that? What are you doing? I need more information.
Click to expand...
Click to collapse
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.

glitchhawk said:
I put the Ouya on sideload from adb.
Then i open adb on my pc, check to make sure it finds the Ouya and then i try to adb reboot bootloader. and that error comes up. if i try to load an .img file from the same place it just says <waiting for device> and doesn't ever move.
Click to expand...
Click to collapse
If it says <waiting for device> then its probably a driver issue with fastboot. When you reboot into the bootloader go into device manager and check the driver again. I also had this issue.

Nexus 7 2013 stuck at Google screen

So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you

See this thread: http://forum.xda-developers.com/showthread.php?t=2381582

krazzyjman said:
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
Click to expand...
Click to collapse
Return it.
You have a defective unit.

[email protected] said:
Return it.
You have a defective unit.
Click to expand...
Click to collapse
Another one of many. ASUS quality control FTW.

anjelika said:
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
This thread doesn't work for me since my nexus is in a bricked like state

hard reset ?
hard reset always works for me. 20 seconds

krazzyjman said:
This thread doesn't work for me since my nexus is in a bricked like state
Click to expand...
Click to collapse
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.

sfhub said:
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
Click to expand...
Click to collapse
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen

Is your device rooted? If not that is just rediculous on asus's part

slamdunksaliby said:
Is your device rooted? If not that is just rediculous on asus's part
Click to expand...
Click to collapse
My device is not rooted at all.
I've had it for 2 days.
I have to say, I am very disappointed in all of these issues.

I would return it..I'm sorry to hear that I have had troubles myself with two devices so far

krazzyjman said:
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Click to expand...
Click to collapse
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.

sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
It was not working, but my tablet just died and I was able to charge and get into the bootloader.
Now to see if it will work.

sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?

krazzyjman said:
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
Click to expand...
Click to collapse
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.

sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
Where am I typing in those lines?
And all the files I need are in the download link?

sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
I figured out where to type, but I have to unlock my bootloader?

I have no way to enable usb debugging since I cant tun on the device, right?

krazzyjman said:
I have no way to enable usb debugging since I cant tun on the device, right?
Click to expand...
Click to collapse
You don't need to enable USB debugging for fastboot mode.
You just need to press Power+VolDown until you get into the bootloader. That is fastboot mode. It will install Android Bootloader Interface (usb debugging does android debug bridge interface)
I actually didn't realize you weren't unlocked. If that is the case, the unlock process will erase your userdata, so you might as well just do the full factory restore.
First goto bootloader mode using Power+VolDown and connect USB, type
fastboot oem unlock
You'll see a question on the tablet screen, Press VolUp to go to yes and Power to select.
On the command prompt in windows, you should see it erase userdata and cache.
On the bootloader screen it should have "Start" highlighted (if not, use VolDown to cycle until you see "Start"). Press Power to accept. You should see Google, then it'll go into recovery and format userdata and cache. It'll then try to boot and since /system is having issues, you'll be stuck in Google again.
Go back into bootloader mode, hold Power+VolDown for a while until you see the bootloader screen.
Now grab the factory image as above, gunzip, untar, and you should have a folder razor-jss15j
Copy these files from your adb directory to the razor-jss15j directory
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
In command prompt in the razor-jss15j directory, type
flash-all
It should output a bunch of stuff, essentially writing a factory image to your tablet.
When it is done, it'll reboot and hopefully you'll get the initial setup window.
I wrote this up from memory, so hopefully I didn't forget stuff. If something doesn't seem right just ask.

Thanks for all of your help.
It really means a lot you took the time to help me.
I'm going to Best Buy today and I am going to see if I can do an exchange.
If not, I will try this later.
Again, thank you

[Guide] Install TWRP and Root your Robin

I am not responsible if you damage your device in any way you are the one that has decided to modify your device.
Guide
1. Download the Beta 2.68 SuperSU zip
2. Make sure you have adb and fastboot and robin usb drivers installed there are tons of guides just google it if you need to install them.
3. In cmd line type the following after connecting robin to your computer (and accepting the computer on robin if first time)
Code:
adb devices
It should start adb and you should see a device listed if it properly connected with developer options enabled, if not go back and make sure you have the proper drivers installed and USB debugging is indeed enabled.
4. Next we are going to unlock the bootloader, if you already have then skip this step.
-It will wipe ALL you data if you are coming from a locked bootloader so back up your internal storage
- You will need to enable developer options in your settings, this is done by going Settings->About phone and tapping Build number 7 times or until you "become a developer". Then you will need to go back to Settings->Developer options and enable USB debugging
First you must reboot to bootloader use the following command to do that:
Code:
adb reboot bootloader
Then after the device has rebooted into the bootloader screen you need to type this command
Code:
fastboot oem unlock
6. Now that we are still in bootloader you can install twrp download the latest twrp img from here
https://twrp.me/devices/nextbitrobin.html
7. Run the following command to flash twrp:
Code:
fastboot flash recovery twrp-3.0.0-0-ether.img
8. Now the easiest way to root it with out having to time mashing the buttons to reboot to recovery again is to fastboot boot the recovery image and install your SuperSU zip then.
Code:
fastboot boot twrp-3.0.0-0-ether.img
9. MTP does work so if you forgot to move your SuperSU zip over you can do it in recovery. Now you just do the normal proccess to flash a zip.
Troubleshooting
1. Some fastboot binarys do not recognize the Robin's fastboot id so if your device is not showing up please add the following to your fastboot commands -i 0x2c3f so a command would look like this
Code:
fastboot -i 0x2c3f flash recovery twrp-3.0.0-0-ether.img

Mine just in case

WOWWWW!!! AWESOMEEEE!! THIS IS AMAZING!!!
Xposed will work right? Will unlocking bootloader reset device??

varun.gid said:
WOWWWW!!! AWESOMEEEE!! THIS IS AMAZING!!!
Xposed will work right? Will unlocking bootloader reset device??
Click to expand...
Click to collapse
Xposed works, unlocking the bootloader wipes all data on the device.

I keep having issues with adb. It connects when the phone is on and USB debugging. But when I go to fastboot, it doesn't connect for me to go forward.
Drivers are good and whatnot.

Use fastboot -i 0x2c3f
Sent from my Robin using Tapatalk

joeminati said:
I keep having issues with adb. It connects when the phone is on and USB debugging. But when I go to fastboot, it doesn't connect for me to go forward.
Drivers are good and whatnot.
Click to expand...
Click to collapse
Fastboot mode doesn't have ADB enabled genius. Fastboot is within the bootloader, while adb is a daemon started by the kernel's init.rc on first boot.

AMAZING THANK YOU SO MUCH! I had to use fastboot -i 0x2c3f

You think Nextbit will support flashing updates through TWRP?

deadman96385 said:
Mine just in case
Click to expand...
Click to collapse
I'm having a problem.. I unlocked bootloader.. flashed recovery... booted into it there was nothing.. Empty folder for internal storage.. Then i booted up the ROM, and then again booted to TWRP.. it asks for password to decrypt.. Please Help!

varun.gid said:
I'm having a problem.. I unlocked bootloader.. flashed recovery... booted into it there was nothing.. Empty folder for internal storage.. Then i booted up the ROM, and then again booted to TWRP.. it asks for password to decrypt.. Please Help!
Click to expand...
Click to collapse
You have to put in your encryption password, it is the one that you have to put in when you boot up the device normally.

deadman96385 said:
You have to put in your encryption password, it is the one that you have to put in when you boot up the device normally.
Click to expand...
Click to collapse
I tried that it didn't work! N then i did advanced wipe and in a hurry i checked system... Now I'm screwed i have No OS Lol!

varun.gid said:
I tried that it didn't work! N then i did advanced wipe and in a hurry i checked system... Now I'm screwed i have No OS Lol!
Click to expand...
Click to collapse
I will upload a full stock twrp backup later today so you and others can recover until factory images are released.

deadman96385 said:
I will upload a full stock twrp backup later today so you and others can recover until factory images are released.
Click to expand...
Click to collapse
Awesome! Please try n load rooted one if possible! Thanks once again life saver!!!

deadman96385 said:
I will upload a full stock twrp backup later today so you and others can recover until factory images are released.
Click to expand...
Click to collapse
I am in the same boat. Can't access internal files if password does not release them. So he can't flash without the TWRP password. Or am I missing something?

deadman96385 said:
I will upload a full stock twrp backup later today so you and others can recover until factory images are released.
Click to expand...
Click to collapse
Any luck in putting it up.. The stock rom?

@deadman96385
Sorry for pushing but please please can u upload stock TWRP /Backup..

Didn't work for me, not only the TWRP kept asking me for a password no matter what, but latter on when I decided to flash through adb sideload, got stock in the bootloader and wiping didn't solve the issue for me. So now I don´t now what to do, I guess I´m going to have to wait for the image as well...

Here is a rooted twrp backup:
http://forum.xda-developers.com/nex.../rom-rooted-twrp-backup-t3336828#post65843511

Does somebody have robin image?
I had wiped my robin system...
Does somebody have robin image ?
Or somebody can backup the image and upload for me ?
Thank a lot!!
---------- Post added at 05:52 AM ---------- Previous post was at 05:40 AM ----------
nelson0521 said:
I had wiped my robin system...
Does somebody have robin image ?
Or somebody can backup the image and upload for me ?
Thank a lot!!
Click to expand...
Click to collapse
I see the link, thanks everyone.

I'm pretty sure I bricked my device, does anyone have a miracle?

I have a Redmi note 5 pro, I was using a custom rom, but was experiencing some bugs so I decided to put another ROM in it, I already did this lots and lots of times and I always followed this procedure:
Reboot into recovery(TWRP), Transfer the ROM, GAPPS and MAGISK to the phone > wipe Cache, Dalvik Cache and System. > Install ROM, GAPPS > WIPE DATA > FLASH MAGISK > WIPE INTERNAL STORAGE > DONE.
Never had a problem, but this time idiot me was doing this at 5am, dying to go to sleep, and I started by wiping everything, without moving the files to the phone beforehand.
Well, apparently once you wipe the system the phone internal storage doesn't show up in the computer anymore, I didn't know that. I always thought that since TWRP was MTP compatible, it would always be a thing, welp.
I then thought of 2 solutions to this: I remember ADB sideload was a thing, and I also could buy a memory card, put the files there, and just load into the phone, bam.
Since it was 5am the memory card would have to wait, and I couldn't get ADB sideload to work, it would't recognize my device for some reason.
I then remembered fastboot existed, and weirdly enough my phone was recognized as a fastboot device on my pc. So I went, downloaded the correct fastboot rom from xiaomi website and tried flashing it using a official tool that they provide, and then tried again using a third party tool that also does something similar.
I was getting a few errors, and then in one of my restarts the phone just stopped showing stuff. It would still turn on, but it's just a black screen, no icons, no recovery, no fastboot, nothing. The battery icon when I put the charge in is the only thing that still shows up.
I already know the answer to this, but hope is the last thing to die, so, is it irreparably ****ed up ? Is there anything I can do? Is it even worth it sending it to repair services? (It wouldn't be Xiaomi, they don't have stores here in my country)

EDL
i´m pretty sure that at least EDL Method works, many tutorials on youtube. Search for "redmi note 5 edl method"

Try to find something about edl mode as mentioned above. It might be your last chance to revive this phone, but you need to take the back cover to be able to find the edl pins and short them. There are many guides on the internet as well as on youtube. But before you try to do that, first try to enter the fastboot mode somehow, you may succeed, so tinker with it for couple of minutes.

As you are able to boot it into Fastboot mode,
1. boot into fastboot mode
2. boot into recovery using "fastboot boot twrp-name.img"
You should be able to see your device in PC after booting in TWRP
3. format data.
(If you are not able to see Internal storage of your RN5 in PC then,
1.boot in fastboot from twrp.
2. boot in twrp again using command above)
4. then copy your files and flash them.
5. wipe cache/dalvik
6. reboot

rasik107 said:
As you are able to boot it into Fastboot mode,
1. boot into fastboot mode
2. boot into recovery using "fastboot boot twrp-name.img"
You should be able to see your device in PC after booting in TWRP
3. format data.
(If you are not able to see Internal storage of your RN5 in PC then,
1.boot in fastboot from twrp.
2. boot in twrp again using command above)
4. then copy your files and flash them.
5. wipe cache/dalvik
6. reboot
Click to expand...
Click to collapse
As I said in the post
and then in one of my restarts the phone just stopped showing stuff. It would still turn on, but it's just a black screen, no icons, no recovery, no fastboot, nothing.
Click to expand...
Click to collapse
I can't boot into fastboot. Right now my only chance seem to be EDL mode, I'll give it a try as soon as I can.

Vitorvlv said:
As I said in the post
I can't boot into fastboot. Right now my only chance seem to be EDL mode, I'll give it a try as soon as I can.
Click to expand...
Click to collapse
And then dont forget to post what happened..
Whether you fixed your phone or not..
Is she dead or not... :angel:
I cant handle the suspense, you are holding...

Sreehul R said:
And then dont forget to post what happened..
Whether you fixed your phone or not..
Is she dead or not... :angel:
I cant handle the suspense, you are holding...
Click to expand...
Click to collapse
she or he posted as soon as she / he can do.

Question What to do? Phone stuck on fastboot

Phone is stuck on fastboot after following steps in flashing rom which was wipe dalvik and now is stuck on fastboot

Dernasurboi said:
Phone is stuck on fastboot after following steps in flashing rom which was wipe dalvik and now is stuck on fastboot
Click to expand...
Click to collapse
Need more information. What rom? What steps did you do?

1finger said:
Need more information. What rom? What steps did you do?
Click to expand...
Click to collapse
First I wiped dalvik and when that happened I couldn't find my rom on my internal storage. Then I tried to get out of twrp because when phone reboots it just went to it automatically. Then I tried to flash a stock miui thinking it would solve the problem but it still didn't work. And now its stuck on fastboot

Dernasurboi said:
First I wiped dalvik and when that happened I couldn't find my rom on my internal storage. Then I tried to get out of twrp because when phone reboots it just went to it automatically. Then I tried to flash a stock miui thinking it would solve the problem but it still didn't work. And now its stuck on fastboot
Click to expand...
Click to collapse
Are you able to use any fastboot commands when connected to your PC?

Veiranx said:
Are you able to use any fastboot commands when connected to your PC?
Click to expand...
Click to collapse
yes I am able to use commands via pc

Try command "fastboot continue"

ApexPrime said:
Try command "fastboot continue"
Click to expand...
Click to collapse
it just says "FAILED (remote: Failed to load image from partition: Load Error)"

Just clean flash using miflash and start over

ApexPrime said:
Just clean flash using miflash and start over
Click to expand...
Click to collapse
This is the way.

Dernasurboi said:
Phone is stuck on fastboot after following steps in flashing rom which was wipe dalvik and now is stuck on fastboot
Click to expand...
Click to collapse
If your phone is stuck in fastboot mode after following steps to flash a ROM and wiping the dalvik cache, here are some steps you can try:
Try restarting your phone by holding down the power button for a few seconds. If it doesn't respond, you can try holding down the power button and the volume up button together for a few seconds to see if that triggers a restart.
If restarting the phone doesn't work, try disconnecting it from any cables or power sources and then holding down the power button for at least 10-15 seconds to force a shutdown. Once the phone is off, you can try turning it on again to see if it boots up normally.
If the phone is still stuck in fastboot mode, you can try connecting it to a computer and using the fastboot commands to flash a new ROM or restore a backup. You can find instructions on how to do this online for your specific device.
If none of these steps work, you may need to seek assistance from a professional or contact the manufacturer for support. It's also possible that there is a hardware issue with the phone that needs to be addressed.

I suggest watching Munchy's videos on how to flash a ROM. He does good, easy to understand guides.