Can anyone please provide me the stock recovery image of realme 1?
My recovery has been destroyed and i brick my phone every time i go into the recovery mode. I have to wait till my phone gets fully discharged and then boot it up. Have done it twice . I can reboot the phone normally and there is no problem in that. Just the recovery.
I am currently rooted and my status bar is showing the notification that your devices has been rooted.
Related
I know this is a known issue, but the thing is that most solutions i have found regard looking into the phone's settings.
The thing is I can't even boot my phone any more. The moment I get the Galaxy SIII GTI9300 logo the phone simply freezes there forever.
It's been like hours like this. I even tried removing the battery for half an hour and put it back. It just won't boot any more.
I didn't install a custom ROm after rooting, the phone was freshly rooted and didn't got to that step yet.
I rooted the device by using the toolkit http://forum.xda-developers.com/gal...msung-galaxy-s3-unified-toolkit-v8-0-t1703488
which surprisingly worked pretty fast and I was able to confirm that my phoen was rooted by installing a root-only app (Root Uninstaller)
then i got a message asking me to update the SU binary and when i accepted the update the phoen restarted never to boot again.
I didn't even get the chance to get the ClockworkMod yet.
Now I don't even have ClockworkMod's menu at the beginning, i have nothing. only the classic boot mode that allows me to download software via Odin (which always fails no matter what package I try)
please help me, i have no other device than that right now....
Download-Mode
Hello and good morning,
have you tried to boot into download mode ?
It's the same like s3
Take the battery out for a few seconds . put it back in and boot into download mode again and it should work
Hi there,
I am new to android phone and I had an old Grand Quattro GT-I82552 to play with.
I followed the guide at xda http://forum.xda-developers.com/showthread.php?t=2494471, downloaded
- ODIN v3.07
- CWM Recovery v6.0.4.5
- Stock Recovery GT-I8552
I followed the steps and flash CWM Recovery v6.0.4.5, but on next boot it won't go to CWM recovery mode (I did removed battery first). I tried many times with other CWM from different sources and now my phone won't boot, it just show up the Samsung Logo with yellow triangles, then shutdown. It doesn't look like a loop boot, as it shutdown entirely. I can't charge the phone either.
I can still go in the usb downloading mode so I flashed the stock recovery, no luck, phone still can't boot.
Any advice is appreciated. Thank you.
EDIT: I found out that I was too careless to noticed that Volume UP is required for boot into CWM, instead as Volume DOWN. So I can boot into CWM now, however I supposed I can withhold my SuperSU install, and just boot into my stock Samsung appearance by normal shutdown and startup of my phone? I can't, everytime I tried to power on, it get's me to empty battery screen then shut off. I can't seem to charge the phone as well.
Have you tried charging the phone for a few hours while in recovery mode, and then turn the device on?
marco199609 said:
Have you tried charging the phone for a few hours while in recovery mode, and then turn the device on?
Click to expand...
Click to collapse
Thank you for your suggestion I will try that. Actually I tried to splice a USB wires and connect red/black to +/- contact for the battery and charge it for few hours, it doesn't seem to get hot, and certainly the phone still can't switch on with the battery.
Initially I thought maybe I messed up the firmware (really I only flash cwm) hence the phone's battery charge controller is not working that's why I tried external charging, but I am not too sure now.
My only hope is to get a way to verify I have enough battery power so I can flash the stock recovery in "downloading mode". I dare not flash recovery without full battery, though the download mode can be accessed while I plugin into PC's usb port.
tancb said:
Hi there,
I am new to android phone and I had an old Grand Quattro GT-I82552 to play with.
I followed the guide at xda http://forum.xda-developers.com/showthread.php?t=2494471, downloaded
- ODIN v3.07
- CWM Recovery v6.0.4.5
- Stock Recovery GT-I8552
I followed the steps and flash CWM Recovery v6.0.4.5, but on next boot it won't go to CWM recovery mode (I did removed battery first). I tried many times with other CWM from different sources and now my phone won't boot, it just show up the Samsung Logo with yellow triangles, then shutdown. It doesn't look like a loop boot, as it shutdown entirely. I can't charge the phone either.
I can still go in the usb downloading mode so I flashed the stock recovery, no luck, phone still can't boot.
Any advice is appreciated. Thank you.
EDIT: I found out that I was too careless to noticed that Volume UP is required for boot into CWM, instead as Volume DOWN. So I can boot into CWM now, however I supposed I can withhold my SuperSU install, and just boot into my stock Samsung appearance by normal shutdown and startup of my phone? I can't, everytime I tried to power on, it get's me to empty battery screen then shut off. I can't seem to charge the phone as well.
Click to expand...
Click to collapse
Don't worry your phone will charge while in recovery around 2% in 6-7 minutes. After that you can flash stock os via Odin. Next time you try to flash recovery don't check auto reboot in Odin when flashing of tar file will complete remove battery and boot to recovery. Then flash supersu
redhead77 said:
Don't worry your phone will charge while in recovery around 2% in 6-7 minutes. After that you can flash stock os via Odin. Next time you try to flash recovery don't check auto reboot in Odin when flashing of tar file will complete remove battery and boot to recovery. Then flash supersu
Click to expand...
Click to collapse
Thanks for your advice. I took both of your advice and had my phone flashed with Stock ROM and now it returned to normal with fully charged battery sign shown. My battery appears to be fine with and fully charged, the battery current probably can't be detected with my broken phone back then.
With StockROM in and fully battery, I redo the custom flashing and I am now on custom ROM! Though have some problem with the ROM (battery report not correct, no front camera..) but I am happy now the phone is back to work now.
Thank you very much.
Hi guys, I really need your help.
I'm new at this rooting stuffs and I tried to root my Oppo Neo 5.
I tried so many softwares like OneClickRoot, FramaRoot, and Kingroot but none seemed to work.
So I resorted to an app called oppo tools
It worked at first but I got really annoyed when my status bar suddenly colored to red when my phone discharges to 15% so I unrooted my phone and rooted back again. I really thought that was going to fix my problem but that's where the bootloop issue started.
I tried to flash some custom recovery zip but it failed since I only have a stock recovery.
But the thing is, I found a guide that says to rename the clockworkrecovery img to PG86IMG.zip.
So I did tried that and as soon as I flashed the zip from my stock recovery, my phone hanged.
I long-pressed the power button to restart and boot into recovery mode but nothing seems to happen.
I'll try to explain a bit more on how it looks when I boot my device.
When it boots normally (I mean not pressing the volume to enter recovery mode) it will only show the logo but when I try to go into recovery mode it will show the logo with a little text on the lower left portion "Recovery Mode"
Before I flashed the PG86IMG.zip, recovery mode was still working and the charging screen when off is working too.
but after I flashed the zip, every time I try to recovery mode the logo shows up with the little text but RECOVERY MODE isn't working. When I charge my phone it automatically boots up and shows the logo and text like it's trying to go recovery mode (I'm just trying to charge? It's going to recovery mode)
I tried using "adb devices" on cmd but it's not detecting any devices.
I'm really out of ideas guys, I know not all people use this model but what would be your suggestion?
A suggestion on how to fix this would really be appreciated :good:
I'm sorry I'm really new at this, please correct me if I did something wrong starting this thread. :angel:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Salman Al-Badgail said:
@DeepBricked please confirm your problem, Boot-loop and can enter into recovery.
Click to expand...
Click to collapse
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
DeepBricked said:
Oh, I'm sorry, I didn't notice.
Lately I can't access the recovery mode but now
I'm currently on Boot-loop and I can enter into recovery.
The ColorOS recovery mode only have limited function that I can mess around.
It only has the apply update, wipe data and cache, reboot, power off and system file verification.
As always I already did wipe the data and cache but nothing happens. Still boot-loop.
What should I do?
Click to expand...
Click to collapse
You made a soft brick, not to worry flash it with correct stock firmware, if the phone is in warranty than ask them to do flash, this will take approx 10-30min. If it isn't in warranty than you should try it own or else pay some amount and the rest they will do.
Salman.
how about bootloop, cant enter recovery, reboot continiously when turn on even going to recovery, only fastboot isnt rebooting automaticaly but pc days drivers not succesfuly installed, and when off it qont detect by pc because of rebooting auto,
where can i find a rom for my oppo neo 5
pls help me pls
Hello,
I've got a Wiko Jerry 2.
Wanted to root the device because the apps it comes with used up more then half the space.
So, Had some experience with Flashing, ADB and Fastboot with a other device.
Searched a tutorial and followed it.
Unlocked the bootloader, flashed and restarted the device.
It rebooted and showed the Android logo and Wiko logo, with orange code: warning your boot is unlocked and can't be trusted, reboot in 5 seconds. (It didn't reboot)
It stayed in this boot, removed the battery and went back into fastboot to flash the factory rom back.
After flashing the stock rom it ended in a bootloop with the same logo's and code orange.
Meaning it went wrong again. The problem I'm facing now is that I can't get the device in fastboot. not even with ADB.
ADB doesnt recognize the phone.
EDIT: The phone is showing in device manager. But it's refreshing the device manager every 2 seconds meaning the device is getting connected/disconnected every 2 seconds.
A bit lost here, someone got some ideas to try?
Thanks in advance,
Floeske.
recovery custom rom from wiko site official
Floeske said:
Hello,
I've got a Wiko Jerry 2.
Wanted to root the device because the apps it comes with used up more then half the space.
So, Had some experience with Flashing, ADB and Fastboot with a other device.
Searched a tutorial and followed it.
Unlocked the bootloader, flashed and restarted the device.
It rebooted and showed the Android logo and Wiko logo, with orange code: warning your boot is unlocked and can't be trusted, reboot in 5 seconds. (It didn't reboot)
It stayed in this boot, removed the battery and went back into fastboot to flash the factory rom back.
After flashing the stock rom it ended in a bootloop with the same logo's and code orange.
Meaning it went wrong again. The problem I'm facing now is that I can't get the device in fastboot. not even with ADB.
ADB doesnt recognize the phone.
EDIT: The phone is showing in device manager. But it's refreshing the device manager every 2 seconds meaning the device is getting connected/disconnected every 2 seconds.
A bit lost here, someone got some ideas to try?
Thanks in advance,
Floeske.
Click to expand...
Click to collapse
if your phone brick at restart try to download wiko Jerry 2 recovery custom rom you can find in the wiko official site web i resolve it but i have a problem twrp recovery touch dont respond
Hi Community,
I read some posts how to fix my Problem, but i cant go to a service Point.
So I was using the Evolution X for a long Time (Installed with TWRP 3.1.0).
And now i wanted to change to the Nusantara Project (Vanilla), I did a clean Flash, everything worked i could access the System.
Than i had problems installing Play Store, so i rebooted into Recovery via the System. But now im Stuck in the Loop.
Can i Somehow connect my Phone to the PC and Reset?
Can someone tell me if i Hard/soft bricked my phone ?
Just a little advice, would be really appreciated.
Thanks a lot
Go to TWRP, wipe system, cache, data and dalvik. Now flash nusantra and whichever GApps are recommended for it (if there are no recommendations then use OpenGApps, make sure the architecture is correct). Now wipe dalvik and restart. Sometimes, certain roms begin to bootloop if you boot into the rom first, then try to install gapps later.
If you still have issues, just reflash the stock rom.
I cant access the TWRP anymore, im just stuck on the Bootloader, no matter how i turn on The Phone (Volume Up + Power ON ), (Volume Down + Power), (All 3 Buttons)
Nothing works anymore i dont understand ....
Im searching the net but i cant go to fastboot or something else, its just keeps on rebooting ...
So it's bootlooping, but you cant access recovery?
When the screen turns off, press the key combo and it should go to recovery.
Your best bet is to take it to a service centre, but if that really isn't possible for you, then wait for its battery to drain completely, then when you plug in the charger, instead of turning the phone on, press the key combo to enter the recovery. From there, wipe and flash some other OS.
I've also heard that certain versions of TWRP don't support some roms, leading to a bootloop. In that case, you'll have to use orangefox recovery to flash the rom (orangefox is flashable via twrp)
Yes its Bootlooping.
When i turn it on, on the Left Corner "Recovery Mode" blinks for one second. Than the usual Text appears:
"Orange State
Your Device has been unlocked and cant be trusted
Your Device will boot in 5 Seconds".
So after a couple of seconds (around 10-20 sec)
It turns off and immediately on again. I Just can turn it OFF when i hold all 3 Buttons.
Than i try starting it with Volume up + Power / Volume down + Power, But i cant access Recovery or TWRP.
So i should wait til the battery gets low and try it again ?
Like i said, my custom Rom (Evolutionx) and TWRP just worked fine. I dont know man ...
Well since your bootloader is unlocked, try flashing the stock rom again. Look for a tutorial and follow it.
Hi I managed to unbrick my device with this guide, and im back on a stock rom
Unbrick
i ran following commands to get to my custom rom:
I run adb reboot bootloader,
add executed following commands.
(Pitch Black recovery 3.1)
- adb reboot bootloader
- fastboot flash recovery recovery.img
-fasboot reboot recovery
It just hang up and booted after a while into the normal system.
But im not able to get to the recovery menu ?
When I restart and hold Volume up + Power, i go in a loop and the phone keeps restarting over and over again.
what have i Fu**ed up ?
Do i need another recovery tool ?
sorry guys, i appreciate your help a lot tho !
EDIT: Is my bootloader unlocked ?
I can access via "adb reboot bootloader" the phone
and on the blackscreen on the phone it is written:
oppo verfiy pass
fastboot_unlock_verify ok
Update:
So i tried some Stuff and i got Red State. No Problem i Unbricked it once again and now im on Stock Android 10.
Now im Trying to enable the bootloader again.
I downloaded the In Depth Test_Realme_6.apk but i keep getting the Error that i should update the system.
So should i update the system ?
I cant find a CURRENT Tutorial to make this work, please help...
If you cant find a tutorial for your version, why not downgrade back to a previous one if possible.