What is this screen, and how do I stop this from happening? - Samsung Galaxy Nexus

I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jmattp said:
I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
Click to expand...
Click to collapse
Its the stock Recovery screen. I would just do a fresh install using Odin
Sent from my Galaxy Nexus using XDA

That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.

jmattp said:
That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.
Click to expand...
Click to collapse
If you can get into fastboot and recovery then you don't have any serious problems.
Sent from my Galaxy Nexus using XDA

Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)

jmattp said:
Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)
Click to expand...
Click to collapse
It must've been something else, I've had the battery die a few times, its booted up fine. Glad you fixed it.
Sent from my Galaxy Nexus using XDA

Related

Help please guys galaxy nexus stuck in a loop

Hi guys, as the title says my nexus was going great, howver randomly it switched off then into a loop, it goes to the part were the google logo comes up then just keeps repeating this, ive cleared the cache, restored factory settings. none of it has fixed it! Please help guys.
I have no solution but the same thing happened to me, I used fastboot to lock the bootloader and took it to verizon and exchanged it.
I got it to boot once after locking the bootloader but then it just stayed in the boot loop. I chalked it up to a hardware failure and moved on.
Hopefully someone else will have a better suggestion.
Sent from my Galaxy Nexus using xda premium
sjameson6969 said:
Hi guys, as the title says my nexus was going great, howver randomly it switched off then into a loop, it goes to the part were the google logo comes up then just keeps repeating this, ive cleared the cache, restored factory settings. none of it has fixed it! Please help guys.
Click to expand...
Click to collapse
More info needed. GSM or LTE? Custom ROM or stock?
sjameson6969 said:
Hi guys, as the title says my nexus was going great, howver randomly it switched off then into a loop, it goes to the part were the google logo comes up then just keeps repeating this, ive cleared the cache, restored factory settings. none of it has fixed it! Please help guys.
Click to expand...
Click to collapse
Flash the factory image and you should be good. You can use the tool kit to do this if you are not familiar with manual methods.
http://forum.xda-developers.com/showthread.php?t=1392310
Sent from my Galaxy Nexus using Tapatalk
Have you been trying to root it ? it's weird it just switched off and is in a loop.
El Daddy said:
More info needed. GSM or LTE? Custom ROM or stock?
Click to expand...
Click to collapse
Im not sure I know the difference, its got a sim card so i think its GSM? I'm on three in the uk.
custom rom I downloaded it from here.
mine just switched off in google earth after the phone got real hot and after battery pull everything loaded fine but 10 seconds after launcher loaded up, GPS icon appeared in status bar and it rebooted again. Did this same thing continually for over an hour so I had to restore factory image. I've since installed 4.0.2 and it hasn't happened again.
Sent from my Galaxy Nexus using xda premium
han4mi said:
Have you been trying to root it ? it's weird it just switched off and is in a loop.
Click to expand...
Click to collapse
No it was already rooted. I was actually streaming a video off the internet at the time then the screen just went blank
Did you do a nandroid backup before flashing the custom rom? If so, restore that. If not try reflashing your current rom.
Sent from my Xoom using xda premium
the toolkit doesn't even pick the device up!
Probably has something to do with your drivers not recognizing it...are you using parallels?
Sent from my Galaxy Nexus using xda premium
sjameson6969 said:
the toolkit doesn't even pick the device up!
Click to expand...
Click to collapse
Looks like the adb driver is missing.
Sent from my Galaxy Nexus using Tapatalk
same thing is happening to my non-rooted GN (GSM and stock). Was using my phone then all of a sudden it turned off and rebooted, but it is stuck on the google screen, then black screen, then back to google screen (loop). Help!
missnexusone said:
same thing is happening to my non-rooted GN (GSM and stock). Was using my phone then all of a sudden it turned off and rebooted, but it is stuck on the google screen, then black screen, then back to google screen (loop). Help!
Click to expand...
Click to collapse
this happened to me too right now.
I can get into odin mode and the bootloader but if I try to get to recovery I see a garbled screen but I can see the android on his back and a red triangle with an exclamation point. After a few seconds there the phone reboots. what's going on?!?
missnexusone said:
same thing is happening to my non-rooted GN (GSM and stock). Was using my phone then all of a sudden it turned off and rebooted, but it is stuck on the google screen, then black screen, then back to google screen (loop). Help!
Click to expand...
Click to collapse
geemaan said:
this happened to me too right now.
I can get into odin mode and the bootloader but if I try to get to recovery I see a garbled screen but I can see the android on his back and a red triangle with an exclamation point. After a few seconds there the phone reboots. what's going on?!?
Click to expand...
Click to collapse
Exact same thing happened to me a week or two ago (GSM, stock, not rooted).
I followed these steps to solve the issue - http://forum.xda-developers.com/showpost.php?p=20302409&postcount=2
It was very simple, but it restored the phone and so wiped everything on it.
didn't work for me. now I'm stuck at a yellow triangle with an exclamation mark between a phone and a pc...
You did download the file properly right? It was around 180mb if I remember correctly.
Yeah, got it from the rs link. Zip was ok. when run, the exe checks crc ok. It gets stuck when starts writing nand for recovery. I really think there's something broken with the phone because of the screen desynchronisation.I'm gonna take it back monday morning...
Try giving it the fast boot command to lock the boot loader (your driver might not be configured for the phones regular state but if you can get it to recognize the decide when the phone is in the boot loader this may work). Give it the fast boot OEM lock command, and then give it the faatboot OEM unlock command. Make sure you have the stock .img on your ccmputer. When you unlock it, it will wipe everything. I mean everything, your Android backups and all. But, it managed to bring mine back after I got stuck in a boot loop that wouldn't make it passed the Google logo. After you unlock it, try and configure the drivers to recognize the phone again. Hopefully then you can push what you need from the computer
Here is what I mean with screen desync:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the recovery screen had the same "video effect".
The duplicate images have a flicker effect.

[Q] Crashing on Bootloader / Display Tear

OK so I've looked through the forum (admittedly the Galaxy Nexus specific one only) and tried some searches but may not be able to articulate this problem in clear way. Basically, I'm continuously crashing - started with a stock, but unlocked/rooted install. Now it won't boot and crashes in the boot loader as well after a few seconds (thus not allowing any non-trivial actions to actually complete.)
The first crash was after enabling face unlock for the first time. When I hit the power button to shut things off, the display "tore" and then went totally dark. Phone was completely unresponsive till I pulled the battery for a few minutes (found that one from search.) Couldn't complete a boot sequence though - would go to the animation, then display would go wonky and then shut down. Would usually have to pull battery again to get any response from that.
Went to recovery mode and wiped data - which completed - same problem on boot. Only thing I'd done was unlock and root (for eventual root apps, none of which had been run) so decided to undo that (using "Galaxy Nexus Root Toolkit 1.3.") On the factory restore there are several steps (boot loader, radio, etc.) and I haven't been able to complete that process.
I suspect it might even be bad hardware at this point, but can't go back to VZW with the phone still showing unlocked. Phone is a recent eBay purchase to replace a lost device but seemed fine for the 2-3 days I used before this all started.
Anyone seen something like this before?
So your able to get into recovery still? If it doesn't boot into the os it's probably a compatibility error between the kernel and rom your using (Just clearning data in recovery won't fix this).
So what rom/kernel combination were you using at the time?
Also have you tried flashing a completely different custom rom to the one your having issues with.
And any nandroid backups you have made in the past?
What's weird is that I was in stock kernel / rom at the time. (At least I'm nearly sure - it did come from eBay after all...)
I'll also try changing the ROM, that could be it. The big question is if that can complete before the thing melts. If I boot to recovery and wait, doing nothing, the system crashes in a minute or two.
My current thinking is that I might have a bad recovery / clockwork mod install.
can you still get to the bootloader and is it stable to sit on the bootloader?
I can get to the boot loader but it is not stable there (I think I was conflating the two.)
does your bootloader look like this? i want to make sure you and i are talking about the same thing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yep, that's the one (before it crashes. I have a pic of the amusing video display when it does that I'll put up when I hit the magic 8 posts...)
try using ODIN to restore your phone. instructions are found here: http://forum.xda-developers.com/showthread.php?t=1394051
also, how long can you sit on the bootloader before it crashes?
I'll try that as tonight - thanks!
Varies on time to crash, but no less than 30 seconds and no more than 5 minutes so far. Requires a battery pull and wait to come back after that.
i would like to see the picture of the crash you are talking about.
also, you can relock the bootloader real fast before you take it to VZW. only takes 1 command once you get to the bootloader
fastboot oem lock
Wow, same crash while in download mode. That can't be good...
yeah thats not good at all. i'd lock the bootloader and return it
http://dulinor.smugmug.com/photos/i-XkKWCrg/0/S/i-XkKWCrg-S.jpg
This is the crash I'm seeing
Yeah return to the store and show them this, the board is probably bad.
thats rough, but since you got it on ebay returning it may be a hassle and if the phone is not a north american model samsung might not even accept it for warranty.
did you try to flash the stock google image using fastboot instead of using the toolkit? it will only take a few mins. when you display crash like that does it still take commands from fastboot? you can test it when the display crash like that type in fastboot devices and see if you get the id number in command prompt. if your build was yakju then you can get the factory images from here http://code.google.com/android/nexus/images.html
Just got back from the store - they issued a replacement, none on hand so one should ship out today. (Thanks for the tip on re-locking it - not sure if they checked, but was happier having that.)
So of course, it actually completed booting (for the first time) but crashed during activation. Once they saw it crash on the Odin screen, they were happy to do the swap.
I had been trying to re-flash OEM Google - which it should have been all along.
Thanks everybody for your help.

Vzw Gnex gets stuck at google splash screen...

Ok i have a verizon gnex with latest ota. At times if i reboot or turn off the phone then turn it back on the phone will get stuck at the google splash screen. One time i pulled the lte sim card and then after a few tries it booted without the lte sim.. then i powered it down and placed the lte sim card in and it started back up... other times that does not work.... Twice today i had to turn it off and wait like 20 minutes or so and then turn it back on with the lte sim in and then it booted. I did use nrt nexus root toolkit and redid the phone but still have the issue.... should i try a custom rom and wipe the system or did the nexus root tool when i used that also wiped the system?
rezoundness said:
Ok i have a verizon gnex with latest ota. At times if i reboot or turn off the phone then turn it back on the phone will get stuck at the google splash screen. One time i pulled the lte sim card and then after a few tries it booted without the lte sim.. then i powered it down and placed the lte sim card in and it started back up... other times that does not work.... Twice today i had to turn it off and wait like 20 minutes or so and then turn it back on with the lte sim in and then it booted. I did use nrt nexus root toolkit and redid the phone but still have the issue.... should i try a custom rom and wipe the system or did the nexus root tool when i used that also wiped the system?
Click to expand...
Click to collapse
use the tootkit to flash the latest stock image and see if that fixes your problem
k786 said:
use the tootkit to flash the latest stock image and see if that fixes your problem
Click to expand...
Click to collapse
i am trying that now nexus tool klit 1.5.5
http://www.droidforums.net/forum/galaxy-nexus-development/192031-toolkit-nexus-root-toolkit-v1-5-5-updated-11-04-12-a.html
i selected the recovery / unroot with the checkbox of softbrick/bootloop....
So far so good... I have isntalled a few apps and now listening to ihart radio and will reboot the phone in a little bit and see what happens. Also is this nexus root kit 1.5.5 the best to root it as well...
Still doing the stuck at google logo... gonna leave it their for a bit and see what happens. It took about a minute or two... to get passed the google screen...
Don't use a toolkit because if something goes wrong (which it seems to be ) you won't know what, where or why it happened. Read the stickies, learn ADB and never have this problem again. Ever. It only takes a few minutes to learn.
I mean you wouldn't hoist your engine out of your car and begin to take it apart without having any idea what you're doing, would you? Go read the stickies..... seriously
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RoyJ said:
Don't use a toolkit because if something goes wrong (which it seems to be ) you won't know what, where or why it happened. Read the stickies, learn ADB and never have this problem again. Ever. It only takes a few minutes to learn.
I mean you wouldn't hoist your engine out of your car and begin to take it apart without having any idea what you're doing, would you? Go read the stickies..... seriously
Click to expand...
Click to collapse
you mean the mr fusion engine wont work in my DeLorian....
http://blogs.discovermagazine.com/discoblog/files/2008/04/mr-fusion.jpg
My gnex was doing the same thing every time I rebooted I had to pull the battery for it to start up. I actually just left it one day for like 30 mins on the splash screen and I guess it just took its time cause now it starts up normally
Sent from my Galaxy Nexus using xda app-developers app
My phone has done this twice. Both times, I solved it by pulling the battery for about 30 seconds, popping it back in, and letting it boot like normal.
Card83 said:
My phone has done this twice. Both times, I solved it by pulling the battery for about 30 seconds, popping it back in, and letting it boot like normal.
Click to expand...
Click to collapse
i wonder if it has something to do with automatically zip aligning at boot or something? I hate to waite as i did pull the battery at times for 3 or 4 minutes and still had to wait a few minutes at boot...
rezoundness said:
i wonder if it has something to do with automatically zip aligning at boot or something? I hate to waite as i did pull the battery at times for 3 or 4 minutes and still had to wait a few minutes at boot...
Click to expand...
Click to collapse
When running JellyBean, the Nexus can sometimes run a filesystem check (similar to Windows' chkdsk or *nix fsck) if it wasn't booted properly or for other random reasons. That check can take a few minutes, up to 10 minutes or so on some devices after certain actions. If anything, pulling the battery during this is doing more harm than good.

Can't enter bootloader

Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Ok so basically what he is saying is that his phone does NOT even have recovery mode. Where we get the dead android guy he gets this and is thus unable to flash his phone with new recovery or system.
That happened to a friend of mine a long time ago but he threw away his phone ( sold it for cheap ) without trying much.
Are there any ACTUAL solutions ?
Again Power + vol up keys DO NOT bring up recovery mode/fastboot or however you want to call it.
Anyone ?
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
debully said:
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
Click to expand...
Click to collapse
"moorefied" ?? Can you explain ?
xRanker said:
"moorefied" ?? Can you explain ?
Click to expand...
Click to collapse
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
debully said:
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
Click to expand...
Click to collapse
That is mostly because people touch where they are not supposed to ^^
But um thanks for reply.
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
debully said:
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
Click to expand...
Click to collapse
Not so sure of that, I really think its more user error than anything else, especially when it comes to fastboot. Copy and paste isn't your friend and it seems most people overwrite their boot or fastboot partitions with system files because they use the same command but change the img file name.
Have never had an unrecoverable brick, and those soft bricks I've had were my fault by not reading properly or skipping through steps quickly.
XepouH said:
Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Click to expand...
Click to collapse
Find your answer here

HELP! SYSTEM DESTROYED / LOCKED BOOTLOADER

First of all, let me say that I am not new to this flashing thing, but I am not an expert either.
My cousin's Redmi 7 has a locked bootloader. Since the phone has been acting up lately, he decided to factory reset it the normal way. However, it stuck at Redmi logo. I advised him to wait a little longer since that just could be a normal thing but it was more than a day already and still the same. He then decided to force shutdown the phone by press and hold the power button. Nothing happened.
Now the phone is with me and its been hell of a day and I can't fix it. The stock recovery is destroyed. The Bootloader is LOCKED. I just feel helpless here. I'm not sure what to do anymore and trust me, I did a lot of things already. Searched everywhere but nothing works. Again, I am not an expert nor trying to be one. I just want to help my cousin restore this thing. Please HELP. Ask whatever question you can about the device and I'll provide as long as it is available. TIA!
Please help...
ronniem18 said:
Please help...
Click to expand...
Click to collapse
Brother it is nit destroyed you have to wait a while to foramate the phone after relocking boot loader it will erase your all data from phone and restart the device .
ronniem18 said:
First of all, let me say that I am not new to this flashing thing, but I am not an expert either.
My cousin's Redmi 7 has a locked bootloader. Since the phone has been acting up lately, he decided to factory reset it the normal way. However, it stuck at Redmi logo. I advised him to wait a little longer since that just could be a normal thing but it was more than a day already and still the same. He then decided to force shutdown the phone by press and hold the power button. Nothing happened.
Now the phone is with me and its been hell of a day and I can't fix it. The stock recovery is destroyed. The Bootloader is LOCKED. I just feel helpless here. I'm not sure what to do anymore and trust me, I did a lot of things already. Searched everywhere but nothing works. Again, I am not an expert nor trying to be one. I just want to help my cousin restore this thing. Please HELP. Ask whatever question you can about the device and I'll provide as long as it is available.
Click to expand...
Click to collapse
ronniem18 said:
First of all, let me say that I am not new to this flashing thing, but I am not an expert either.
My cousin's Redmi 7 has a locked bootloader. Since the phone has been acting up lately, he decided to factory reset it the normal way. However, it stuck at Redmi logo. I advised him to wait a little longer since that just could be a normal thing but it was more than a day already and still the same. He then decided to force shutdown the phone by press and hold the power button. Nothing happened.
Now the phone is with me and its been hell of a day and I can't fix it. The stock recovery is destroyed. The Bootloader is LOCKED. I just feel helpless here. I'm not sure what to do anymore and trust me, I did a lot of things already. Searched everywhere but nothing works. Again, I am not an expert nor trying to be one. I just want to help my cousin restore this thing. Please HELP. Ask whatever question you can about the device and I'll provide as long as it is available. TIA!
Click to expand...
Click to collapse
If you are in this situation then simply flash redmi fastboot rom first and try it would suerly boot your device to orginal version or your problem will be solved
ronniem18 said:
First of all, let me say that I am not new to this flashing thing, but I am not an expert either.
My cousin's Redmi 7 has a locked bootloader. Since the phone has been acting up lately, he decided to factory reset it the normal way. However, it stuck at Redmi logo. I advised him to wait a little longer since that just could be a normal thing but it was more than a day already and still the same. He then decided to force shutdown the phone by press and hold the power button. Nothing happened.
Now the phone is with me and its been hell of a day and I can't fix it. The stock recovery is destroyed. The Bootloader is LOCKED. I just feel helpless here. I'm not sure what to do anymore and trust me, I did a lot of things already. Searched everywhere but nothing works. Again, I am not an expert nor trying to be one. I just want to help my cousin restore this thing. Please HELP. Ask whatever question you can about the device and I'll provide as long as it is available. TIA!
Click to expand...
Click to collapse
Did you find a solution?
ronniem18 said:
First of all, let me say that I am not new to this flashing thing, but I am not an expert either.
My cousin's Redmi 7 has a locked bootloader. Since the phone has been acting up lately, he decided to factory reset it the normal way. However, it stuck at Redmi logo. I advised him to wait a little longer since that just could be a normal thing but it was more than a day already and still the same. He then decided to force shutdown the phone by press and hold the power button. Nothing happened.
Now the phone is with me and its been hell of a day and I can't fix it. The stock recovery is destroyed. The Bootloader is LOCKED. I just feel helpless here. I'm not sure what to do anymore and trust me, I did a lot of things already. Searched everywhere but nothing works. Again, I am not an expert nor trying to be one. I just want to help my cousin restore this thing. Please HELP. Ask whatever question you can about the device and I'll provide as long as it is available. TIA!
Click to expand...
Click to collapse
....
hello, please help me, my system is destroyed and at the same time I can’t enter the recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Categories

Resources