Related
To flash an image:
1. start your phone up in Fastboot mode. you can do this by holding power and VOL+DOWN.
2. push files to phone: fastboot flash splash1 evosplash1.rgb565
3. reboot phone: fastboot reboot
heh...not bad
Cool but next time try themes and apps
I like the skeleton, very different.
Did you sign this? I get signature verification failed.
Mast3rpyr0 said:
Did you sign this? I get signature verification failed.
Click to expand...
Click to collapse
You don't flash this in recovery. You have to get into the bootloader, choose fastboot, have it connected to the PC, go into cmd or terminal, navigate to where your android-sdk/tools is, and run "fastboot flash splash1 evosplash1.rgb565" followed by "fastboot reboot"
RikusHaven said:
You don't flash this in recovery. You have to get into the bootloader, choose fastboot, have it connected to the PC, go into cmd or terminal, navigate to where your android-sdk/tools is, and run "fastboot flash splash1 evosplash1.rgb565" followed by "fastboot reboot"
Click to expand...
Click to collapse
Thats what i did.
Mast3rpyr0 said:
Thats what i did.
Click to expand...
Click to collapse
Try the one I have attached then. All I did was load the .png into EVOSplash from this tread: click. Should work.
Mast3rpyr0 said:
Did you sign this? I get signature verification failed.
Click to expand...
Click to collapse
dont mean this to be offensive, but just to double check and be thorough, you do have the eng hboot loaded, yea?
as a general FYI, fastboot is basically very limited on all other RUUs, except eng. perhaps the OP could list, eng hboot required.
i guess the OP cant read this is the DEV section no the theme app section !
It would also be nice if the OP didn't post a new thread in apps/themes for every splash screen he makes. OP, do everyone a favor and put them all in one thread.
Got you!, thanks for the reminder
RikusHaven said:
You don't flash this in recovery. You have to get into the bootloader, choose fastboot, have it connected to the PC, go into cmd or terminal, navigate to where your android-sdk/tools is, and run "fastboot flash splash1 evosplash1.rgb565" followed by "fastboot reboot"
Click to expand...
Click to collapse
Thanks for the help!
Sweet ass twist with the Powell ripper splash, man. Think you could do one up with the Powell screaming hand?
neckface said:
Sweet ass twist with the Powell ripper splash, man. Think you could do one up with the Powell screaming hand?
Click to expand...
Click to collapse
Wow... You are bringing up some past... The old Lucero behind bars logo or the Natas Claw/prism would be sweet too.
thenewguy821 said:
Click to expand...
Click to collapse
Dude! Those would be so sick. Especially the behind bars logo. Is the signed Natas deck yours? That thing is worth money.
Nah.. I had both of those back a few years (cough 23-25 years ago). I actually had the First Lucero behind bars, which was just eyes looking out and the bars were straight, as my first board. Later got one like the one I linked, but in a dark tealish color. A couple years later, I had the Natas design I posted, on a black board. The later designs had a little more detail, but similar logo. Some of the old Dogtowns were sweet. I think I remember them having an old ST (Suicidal Tendencies) logo board.
ok, I had to formatt my computer the other day and reinstall windows, i reinstalled sync and not sure what Im missing here, when I go into bootloader and open a command window, I type in adb devices and it wont show my device, but my computer shows that the phone connected with its little "ding" and yes usb debugging is on, before I formatted I had successfully pushed the "black splash" screen so Im not sure whats goin on here.
BAleR said:
ok, I had to formatt my computer the other day and reinstall windows, i reinstalled sync and not sure what Im missing here, when I go into bootloader and open a command window, I type in adb devices and it wont show my device, but my computer shows that the phone connected with its little "ding" and yes usb debugging is on, before I formatted I had successfully pushed the "black splash" screen so Im not sure whats goin on here.
Click to expand...
Click to collapse
i'm having a similar problem. i can mount my sd card and transfer files back and forth all day, so communicating between my phone and pc isn't a problem, but i cannot get adb or fastboot commands to work to save my life.
full root, yadda yadda.
Did you reinstall sync?
Goto device manager and verify the drivers are installed. Also make sure u reinstalled android ask.
Sent from my PC36100 using XDA App
Mods, please move this to the General section...my mistake.
This OP is a work in progress. Any useful info will be added. This thread was solely created to help those who might overlook the thread that I linked below. ALL CREDIT for this solution goes to Buster99.
This is big news for me, and I hope that some of you can save some money in the future on new motherboards. Try this before you buy another!
Now, this solution is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)
Here is what you need to do, quoted from the link below.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=44244313
I hope that this has helped someone, as it has surely solved my problem.
THANKS, Buster for saving me money that I can't afford right now!
Side notes:
- The tablet seems to be a little slower, and lags/stutters a little bit. Not sure if that is because of the Stock 4.2 rom. I don't have much experience on it.
- Update: The stock rom was the cause of the lag. I'm flashed on a custom rom and enjoying the benefits!!!!
______________________________
HTC Evo 4G LTE
aarsyl said:
Mods, please move this to the General section...my mistake.
This OP is a work in progress. Any useful info will be added. This thread was solely created to help those who might overlook the thread that I linked below. ALL CREDIT for this solution goes to Buster99.
This is big news for me, and I hope that some of you can save some money in the future on new motherboards. Try this before you buy another!
Now, this solution is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)
Here is what you need to do, quoted from the link below.
http://forum.xda-developers.com/showthread.php?p=44244313
I hope that this has helped someone, as it has surely solved my problem.
THANKS, Buster for saving me money that I can't afford right now!
Side notes:
- The tablet seems to be a little slower, and lags/stutters a little bit. Not sure if that is because of the Stock 4.2 rom. I don't have much experience on it.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
Good idea mate!! maybe we can have a sticky for softbrick issues(looking at you MOD )
and I'm happy you saved your money since i had to get a replacement screen and know how much it hurts your wallet
cheers
-Buster
Buster99 said:
Good idea mate!! maybe we can have a sticky for softbrick issues(looking at you MOD )
and I'm happy you saved your money since i had to get a replacement screen and know how much it hurts your wallet
cheers
-Buster
Click to expand...
Click to collapse
Thanks I've been looking at my tablet depressed for months your method worked and i had tried just about everything good look
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Thanks a lots !
U're save my tablets !
Hi guys, help me please!!! when i try to flash system blob everything is ok, but i stuck on boot loop! Why??
So i try this guide, but it says ''waiting for device'' when i do ''fastboot erase system''.
sounds like you are not in fastboot anymore. please check that you still in fastboot.
gl
Sent from my GT-I9505 using xda app-developers app
I was about to send my tablet in but tried what you posted and saved my tablet !!!
Thanks a lot !
:good:
Wow this worked
After 6 months of trying almost every method out there this saved my tablet. Thank you so much.
Do I need to just press the reset button and volume down keys to power on the tablet or should I also press the power button?
Please help because my tablet just boots directly to twrp recovery and I can't do anything from the recovery as none of the partitions can be mounted.
Please help!
juzerali said:
Do I need to just press the reset button and volume down keys to power on the tablet or should I also press the power button?
Please help because my tablet just boots directly to twrp recovery and I can't do anything from the recovery as none of the partitions can be mounted.
Please help!
Click to expand...
Click to collapse
I am having the same problem right now (well - literally, as I was typing this reply, I was most of the way through the fix).
You want to get to fastboot mode (vol down).
Here is my situation as best as I can recall.
I have an unlocked bootloader from 10.6.1.27
I have (just removed) twrp-2.5.0
I am presently halfway through the second last step of the above instructions, and just waiting for the progress bar to finish.
(I got into my mess through playing around with encrypted partitions and then forgetting about it for a few weeks, coming back to I wasn't really sure what state the tablet was in other than what you described).
Progress bar has just finished, and I have a nice silver ASUS logo indicating that I'm likely back on stock.
Moral of the story: pays to read the instructions before asking for help. Good luck
Big thanks to OP too
carneeki said:
I am having the same problem right now (well - literally, as I was typing this reply, I was most of the way through the fix).
You want to get to fastboot mode (vol down).
Here is my situation as best as I can recall.
I have an unlocked bootloader from 10.6.1.27
I have (just removed) twrp-2.5.0
I am presently halfway through the second last step of the above instructions, and just waiting for the progress bar to finish.
(I got into my mess through playing around with encrypted partitions and then forgetting about it for a few weeks, coming back to I wasn't really sure what state the tablet was in other than what you described).
Progress bar has just finished, and I have a nice silver ASUS logo indicating that I'm likely back on stock.
Moral of the story: pays to read the instructions before asking for help. Good luck
Big thanks to OP too
Click to expand...
Click to collapse
The thing is that i just cant go to fastboot mode. Vol down + power key shows the asus logo screen and then goes directly to twrp. There seems to be no way to get into fastboot.
can you help with that?
when in twrp connect to your pc type: adb reboot bootloader. shoild boot into fastboot
gl
-buster
Sent from my GT-I9505 using xda app-developers app
I LOVE YOU GUYS <333 Thought my tablet was dead for sure
Buster99 said:
when in twrp connect to your pc type: adb reboot bootloader. shoild boot into fastboot
gl
-buster
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info, buster. However, ive already tried connecting via adb when in twrp but adb doesn't recognize my device as connected even though i have all the drivers correctly installed. Don't know what to do anymore
I've had this problem. Luckily, I had a computer with Ubuntu on it, and it recognized the device immediately. If you don't have a pic with a version of Linux, then you can look into making a LiveCD to boot Linux.
______________________________
HTC Evo 4G LTE
please bear in mind that you probably have to install the adb / fastboot drivers via apt-get. but true, i use for debugging mainly my linux now. If you new to linux try linux mint with cinnamon desktop its windowsesque. ubuntu with unit might be too confusing to start with for a quick adb / fastboot swith (but thats only imho)
gl
buster
Buster99 said:
please bear in mind that you probably have to install the adb / fastboot drivers via apt-get. but true, i use for debugging mainly my linux now. If you new to linux try linux mint with cinnamon desktop its windowsesque. ubuntu with unit might be too confusing to start with for a quick adb / fastboot swith (but thats only imho)
gl
buster
Click to expand...
Click to collapse
Thanks for your 2 cents (no sarcasm). Forgot about that extra step. But Linux actually tells you to go that within the terminal.
______________________________
HTC Evo 4G LTE
aarsyl said:
I've had this problem. Luckily, I had a computer with Ubuntu on it, and it recognized the device immediately. If you don't have a pic with a version of Linux, then you can look into making a LiveCD to boot Linux.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
Thanks for your tips, aarsyl and buster.. ADB in Ubuntu is recognizing my device now! But when I give the 'adb reboot bootloader' command, it gives me this message:
error: insufficient permissions for device
---------- Post added at 03:00 PM ---------- Previous post was at 02:53 PM ----------
Never mind... I ran the adb command via sudo and my device is showing 3 icons now!! I'm going to flash the latest JB blob now.. Will keep you posted on the progress
Holy crap, I'd given up on my TF201, thought it was gone, after doing this it lives! ! ! Thank you so much! ! !
Sent from my HTC_PN071 using Tapatalk 4
And finally I was able to restore my tablet to Stock JB 4.2.1!
Thanks a lot for the original recovery steps, Buster99! You're the man! I can't thank you enough!
Thanks for the Linux tip, aarsyl. Yet another reason why Linux rules over Windows!
Hi all,
Just having right now a BIG problem with my all new N5. I have received it a few hours ago.
I have just turned it on one time: the phone downloaded and installed an update, and I have configured my google account. After that, and before installing any app, I decided to unlock my bootloader.
Here is exactly what I have done se far:
- downloaded the ZIP archive by chainfire (CF-Auto-root tool) from this thread
- unzipped it,
- I just ran then: sudo chmod +x tools/fastboot-mac
- Then, I boot the N5 in fastboot mode
- And finally: sudo tools/fastboot-mac oem unlock
So, here, my phone asked me (on the screen) if I was sure to unlock the bootloader. I clicked on yes, and then :
- the screen turned off,
- I got on the shell:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Since, my phone does not respond to anything, the power button has no effect. It just seems off, and I can not turn it on.
So, any idea on what has just happened? I was just unlocking the bootloader through fastboot, so no heavy tweaking here...
Any help would be buch appreciated, but I have the feeling that my N5 is now a (pretty) brick...
Did you have all the drivers?
Can you get to bootloader?
pert_S said:
Did you have all the drivers?
Click to expand...
Click to collapse
Up to my knowledge, no driver is required on a mac.
pert_S said:
Can you get to bootloader?
Click to expand...
Click to collapse
No, and that's what makes me think my Nexus is dead. The device does not respond to the power button at all.
sylar12 said:
Up to my knowledge, no driver is required on a mac.
No, and that's what makes me think my Nexus is dead. The device does not respond to the power button at all.
Click to expand...
Click to collapse
Oh I see. I've never used a Mac for these things before but have you asked for help in the CF thread?
Do you see the battery icon when you plug your phone in? Try it a few times and see if the icon will show up.
pert_S said:
Oh I see. I've never used a Mac for these things before but have you asked for help in the CF thread?
Click to expand...
Click to collapse
Yep. No response so far, but the problem appears a few hours ago only.
I'm pretty sure my bootloader is corrupted. But does that prevent the device to power on?
Any other idea?
sylar12 said:
Any other idea?
Click to expand...
Click to collapse
If you can't do anything to it, then RMA. Google won't know you did something to it, because they won't be able to boot it too.
abaaaabbbb63 said:
If you can't do anything to it, then RMA. Google won't know you did something to it, because they won't be able to boot it too.
Click to expand...
Click to collapse
I have contacted google, RMA should be OK.
But I would like to understant what happened: is this because I tried to unlock from a mac? A what is the meaning of:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Just in case it could allow people to not have the same problem
sylar12 said:
Hi all,
Just having right now a BIG problem with my all new N5. I have received it a few hours ago.
I have just turned it on one time: the phone downloaded and installed an update, and I have configured my google account. After that, and before installing any app, I decided to unlock my bootloader.
Here is exactly what I have done se far:
- downloaded the ZIP archive by chainfire (CF-Auto-root tool) from this thread
- unzipped it,
- I just ran then: sudo chmod +x tools/fastboot-mac
- Then, I boot the N5 in fastboot mode
- And finally: sudo tools/fastboot-mac oem unlock
So, here, my phone asked me (on the screen) if I was sure to unlock the bootloader. I clicked on yes, and then :
- the screen turned off,
- I got on the shell:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Since, my phone does not respond to anything, the power button has no effect. It just seems off, and I can not turn it on.
So, any idea on what has just happened? I was just unlocking the bootloader through fastboot, so no heavy tweaking here...
Any help would be buch appreciated, but I have the feeling that my N5 is now a (pretty) brick...
Click to expand...
Click to collapse
Have you created a path for adb (in for windows) system/system variables/path/ commands to be recognized on your Mac (if this is needed off course)? I`am not xperienced with Macs but i guess they also need a path for passing on commands.
sylar12 said:
I have contacted google, RMA should be OK.
But I would like to understant what happened: is this because I tried to unlock from a mac? A what is the meaning of:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Just in case it could allow people to not have the same problem
Click to expand...
Click to collapse
Wait. Try this:
Press and hold the power button + BOTH volume buttons AT THE SAME TIME for about 15 seconds, then try booting.
It seems that the USB connection got interrupted, but that wouldn't normally brick your phone, nor corrupt the bootloader. Maybe it just got stuck.
Please keep us updated if you find out why this happened. I am waiting for my Nexus 5 to arrive on Monday and I was planning on doing exactly what you did.. Boot it up, configure Google account to check if everything is fine and then unlock the bootloader on a Mac. I've never used fastboot before on a mac as I only have one recently, but from what I remember of using fastboot in a windows machine, as long as we could run "fastboot devices" and got a response, everything should be fine. Isn't this the same in Macs?
Cheers.
gee2012 said:
Have you created a path for adb (in for windows) system/system variables/path/ commands to be recognized on your Mac (if this is needed off course)? I`am not xperienced with Macs but i guess they also need a path for passing on commands.
Click to expand...
Click to collapse
This is not "directly" required on mac. And the fastboot binay has been recognized by the shell, since the unlocking procedure started (my phone asked me if it was ok for unlocking the bootloader).
abaaaabbbb63 said:
Wait. Try this:
Press and hold the power button + BOTH volume buttons AT THE SAME TIME for about 15 seconds, then try booting.
It seems that the USB connection got interrupted, but that wouldn't normally brick your phone, nor corrupt the bootloader. Maybe it just got stuck.
Click to expand...
Click to collapse
I already tried this: nothing happens... I guess the phone is really bricked.
eddie_gordo said:
Please keep us updated if you find out why this happened. I am waiting for my Nexus 5 to arrive on Monday and I was planning on doing exactly what you did.. Boot it up, configure Google account to check if everything is fine and then unlock the bootloader on a Mac. I've never used fastboot before on a mac as I only have one recently, but from what I remember of using fastboot in a windows machine, as long as we could run "fastboot devices" and got a response, everything should be fine. Isn't this the same in Macs?
Cheers.
Click to expand...
Click to collapse
It should be the same, yes. Fastboot is very easy to use usually, it's the first time I have such a problem. And I have no idea why the unlocking has got wrong. 2 solutions imho:
- a phone harware problem which only reveals during the unlocking process;
- a fastboot problem/mac related problem.
Just trying to figure out which one is the correct answer.
El Daddy said:
Do you see the battery icon when you plug your phone in? Try it a few times and see if the icon will show up.
Click to expand...
Click to collapse
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
sylar12 said:
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
Click to expand...
Click to collapse
Congrats!
You have managed to be the first xda user to really brick their Nexus 5.
I'm sorry, but you'll have to rma.
sylar12 said:
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
Click to expand...
Click to collapse
I think you got really unlucky. Possibly a bad cable or USB port but some connection got lost while you were flashing. RMA is your best option right now. Sorry bro
abaaaabbbb63 said:
Congrats!
You have managed to be the first xda user to really brick their phone.
Click to expand...
Click to collapse
Yessssss, I did it!
...
:crying:
abaaaabbbb63 said:
I'm sorry, but you'll have to rma.
Click to expand...
Click to collapse
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't think they will).
sylar12 said:
Yessssss, I did it!
...
:crying:
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't they will).
Click to expand...
Click to collapse
You'll be fine on the rma. Been there done that on another device
sylar12 said:
Yessssss, I did it!
...
:crying:
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't think they will).
Click to expand...
Click to collapse
Maybe the XDA award for the1st N5 bricker is a new Nexus 5 32GB
abaaaabbbb63 said:
Congrats!
You have managed to be the first xda user to really brick their Nexus 5.
I'm sorry, but you'll have to rma.
Click to expand...
Click to collapse
Sorry to disappointed you but I was the first one. Last week I bricked mine
can anyone help me, i have this problem and i can install twrp.img i ty adb & windroid
fastboot flash recovery filename.img from bootloader to install recovery
gumymoty said:
can anyone help me, i have this problem and i can install twrp.img i ty adb & windroid
Click to expand...
Click to collapse
You need to post more info. The screenshots don't really tell us anything, and really are not that useful. In particular:
- What command you used. Fastboot is typically used to flash TWRP, not adb
- What outputs or error messages received.
- What version TWRP you tried to install (full filename)
redpoint73 said:
You need to post more info. The screenshots don't really tell us anything, and really are not that useful. In particular:
- What command you used. Fastboot is typically used to flash TWRP, not adb
- What outputs or error messages received.
- What version TWRP you tried to install (full filename)
Click to expand...
Click to collapse
https://youtu.be/mjC3fanJ4rQ
https://youtu.be/yVJcrii2HFA
gumymoty said:
Click to expand...
Click to collapse
Videos don't play. Are those videos that you made, and posted on YouTube? Don't understand why you would do all that, instead of just taking a few minutes to answer the questions I asked (cut/paste text from command prompt, if needed).
redpoint73 said:
Videos don't play. Are those videos that you made, and posted on YouTube? Don't understand why you would do all that, instead of just taking a few minutes to answer the questions I asked (cut/paste text from command prompt, if needed).
Click to expand...
Click to collapse
ok, i bay my tablet recently from a store come with unloked bootloder
i try to instal twrp imge using WinDroid+Universal+Android+Toolkit+ i try all the versions + nvidia shield drivers . dev mode on tablet setings
WinDroid+Universal+Android+Toolkit+ divaice online when i give the command flash recovery i select twrp-3.2.1-0-shieldtablet.img the tablet rebot by the app and go in to boot menu, on the WinDroid+Universal+Android+Toolkit+ showin the mesage flashing recovery , if I choose continue on tablet boot option cold booting linux apears and
tablet reboot normaly turn on , if I choose option fastboot protocol noting hapens
gumymoty said:
if I choose continue on tablet boot option cold booting linux apears and
tablet reboot normaly turn on , if I choose option fastboot protocol noting hapens
Click to expand...
Click to collapse
Nothing is supposed to "happen" when selecting fastboot protocol. It simply puts the tablet in bootloader-fastboot mode, which lets your computer talk to the device using fastboot.
If you want to boot recovery, select recovery from the bootloader selections.
i really hope what thT NICE PERSON SAID TO YOU HELPED IN SOME SIGNIFICANT WAY because i was pissed off by the time i realized you already deleted the videos posted on youtube . You leave them up after you use them in a forum or else it undermines the whole premise of having a forum discussing problems you are having on a device. I know you like your account to be all pretty and neat incase your girlfriend is snooping around in there or what ever but.. If your one of those video in a forum guys have some respect i mean its not like your aol or something. "wow we have the largest tresure trove of information ever ammassed in earths history all on our servers... well delete it nobody is ever "gonna look at it." I was very dissapointed when they blocked access but hey they werent asking for my help. Please don't be offended i like the video guy. its much easier to see and understand than try to explain something to somebody.
welcome
I wanted to install twrp for xiaomi redmi 9 global version miui 12.5.1
These were the commands I used:
1 - fastboot flash recovery twrp-3.4.2B-0108.img
2 - fastboot flash misc misc.bin
3 - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4 - fastboot boot twrp-3.4.2B-0108.img
After that, the device restarted but MIUI did not start again. "Redmi" appears on the screen for a few seconds then restarts again and again.
And now comes the real problem and also the reason for this post...
I cannot access recovery or fastboot mode!
I can't even turn off the device.
I can't do anything but wait for the battery to run out.
If I hold Power + VolumeUp = It keeps rebooting
If I hold Power + VolumeDown = It keeps rebooting
If I only hold Power = It keeps rebooting
If I hold all of them it stops rebooting and keeps the black screen as if it's off, but when I stop holding, the bootloop starts again.
I don't know what to do, I hope any of you can help me.
Thanks for the attention.
Re-flash Stock ROM to get rid off of all modificatins you applied so far.
jwoegerbauer said:
Re-flash Stock ROM to get rid off of all modificatins you applied so far.
Click to expand...
Click to collapse
Hello
Thanks for the quick reply
Please can you explain how this works?
It's typically done via ADB Sideload method - what of course requires USB Debugging got enabled on phone and you have the Stock ROM in .ZIP-file format on hand.
jwoegerbauer said:
It's typically done via ADB Sideload method - what of course requires USB Debugging got enabled on phone and you have the Stock ROM in .ZIP-file format on hand.
Click to expand...
Click to collapse
I cannot access recovery or fastboot mode!
I can't even turn off the device.
I can't do anything but wait for the battery to run out.
You were told to to use ADB Sideload method: This has nothing to do with Recovery mode or Fastboot mode.
jwoegerbauer said:
You were told to to use ADB Sideload method: This has nothing to do with Recovery mode or Fastboot mode.
Click to expand...
Click to collapse
Sorry to bother you and thank you
But due to my lack of experience in the field, I was unable to find a detailed explanation of the ADB Sideload process that you told me about, could you please explain how this works Steps or send a link with details or a video, please Knowing that the phone does not appear on the computer due to its continuous restart all the time I am sorry again
That's another issue you report now,
My recommendation: Take phone to authorized service center and let them try to fix it.
I already took it to fix it but no result He told me that I have to replace the motherboard and this is wrong because my problem is a problem with the phone system
jwoegerbauer said:
That's another issue you report now,
My recommendation: Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
hey..I know I'm a whole year late but i have a solution!!!
reply if you still need it
vader404 said:
hey..I know I'm a whole year late but i have a solution!!!
reply if you still need it
Click to expand...
Click to collapse
hello I wanna know how you did it.
vader404 said:
hey..I know I'm a whole year late but i have a solution!!!
reply if you still need it
Click to expand...
Click to collapse
hellow whay is the solution? i got this problem too now, i have experience to unbrick some android phone, but this thing is very rare. Because it repeatedly restarting cant go to fastboot to connect to pc or to recovery mode to reformat. Thank u in advance.