Hello,
First of all I read all topics regarding this issue and I'm using Windows as my operating system (no linux/unix).
My problem is I cannot make the device available when issuing the adb device command, in adb, although I ran all steps (read the hole 72 pages from [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 ).
I read a thread in which someone gave a hint to similar issue, by flashing the stock image to one "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307), where I can see my device mapped at some COM port, but after successfully flashing I expected to have my device showed in "adb device" command, but I don't.
Also I tried using the drivers from above topic, the ones from Samsung (which allowed me to use ODIN and successfully flash), I'm using the up volume key after booting in order to put Samsung device in "download mode", but still...I'm not able to see it under adb (because I want to use it to retrieve files).
Is there anything else I can try? As long as I can successfully flash, isn't there an image with debugging mode on? For now I think this is the only "variable" which I'm not able to alter, as I do not have the display.
Many thanks,
miborion said:
Hello,
First of all I read all topics regarding this issue and I'm using Windows as my operating system (no linux/unix).
My problem is I cannot make the device available when issuing the adb device command, in adb, although I ran all steps (read the hole 72 pages from [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 ).
I read a thread in which someone gave a hint to similar issue, by flashing the stock image to one "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307), where I can see my device mapped at some COM port, but after successfully flashing I expected to have my device showed in "adb device" command, but I don't.
Also I tried using the drivers from above topic, the ones from Samsung (which allowed me to use ODIN and successfully flash), I'm using the up volume key after booting in order to put Samsung device in "download mode", but still...I'm not able to see it under adb (because I want to use it to retrieve files).
Is there anything else I can try? As long as I can successfully flash, isn't there an image with debugging mode on? For now I think this is the only "variable" which I'm not able to alter, as I do not have the display.
Many thanks,
Click to expand...
Click to collapse
Have tried today, 3 different phones (some Sam I9300, Sam A3), but still same issue, devices not shown in devices command although I had enabled developer mode.
Should I check somethings regarding the PC? the port if is opened or not?
Look at below forum for your device Samsung I9300i
http://forum.xda-developers.com/galaxy-s3-neo
Please search for your problem and still having problems please create a new thread in below url
http://forum.xda-developers.com/galaxy-s3-neo/help
There is thread called [GUIDE] How to UNBRICK Samsung Galaxy S3 Neo ( i9300i & i9301i )
please select this url and search for it if u had a brick
http://forum.xda-developers.com/galaxy-s3-neo/help/how-to-unbrick-t2911301
Please search before making any new thread.
If I helped you please press THANKS button
Thanks
Salman Al-Badgail
Salman Al-Badgail said:
Look at below forum for your device Samsung I9300i
http://forum.xda-developers.com/galaxy-s3-neo
Please search for your problem and still having problems please create a new thread in below url
http://forum.xda-developers.com/galaxy-s3-neo/help
There is thread called [GUIDE] How to UNBRICK Samsung Galaxy S3 Neo ( i9300i & i9301i )
please select this url and search for it if u had a brick
http://forum.xda-developers.com/galaxy-s3-neo/help/how-to-unbrick-t2911301
Please search before making any new thread.
If I helped you please press THANKS button
Thanks
Salman Al-Badgail
Click to expand...
Click to collapse
Hello Salman,
The reason why I opened this post is that I need something which is not specific to my mobile model, in my case Sam. i9300i, but something which is useful for any other user as well, especially ones in my situation (broken display, with no debugging mode activated).
What I was trying to find in this section of the forum and trust me, by now I have read everything it was to read on this topic, was a custom build rom, which could have that debugging mode activated, as without it I (or somebody else in this predicament) cannot extract the needed data via ADB.
Therefore if somebody has any idea or knowledge about a such image, please do share.
Regards,
maybe you could try to enable the adb before you flash the stock rom by editing the build.prop file.
or you simply could try with this http://forum.xda-developers.com/tools/general/tool-gstreamer-emergency-toolbox-t3289951
good luck bro
Related
Hello all,
Like seemingly many others, my io edtion galaxy tab 10.1 is blocked in a boot loop. I've read about some methods allowing to reset the tablet thanks to adb and or fastboot.
But my problem is that in whatever state my tablet is, adb and fastboot never seem to be able to detect it, so I can't use them to wipe it and I don't see an other so I can't repair my tablet.
My question is : has anyone been able to make a boolooping tablet detectable by android dev tools ?
Alternatively, has anyone been able to get in touch with samsung support on that issue ? Are io edition tablets under warranty ? I haven't seen any reports related to that.
Thanks in advance for your answers, it is my last chance attempt to make that tablet work again.
Are you able to enter Download Mode? If so, you should be able to communicate with your tablet using Odin.
Go to the link in my signature and read Sections IV and VI.
If someone else can point you to the correct .tar file for your device (do not use the one T-Mobile one), you can just follow directions in Section VI to restore your tablet.
Regarding warranty, if you have messed around with your device's firmware, it should be void. Try to solve the issue yourself.
Teovald said:
Hello all,
Like seemingly many others, my io edtion galaxy tab 10.1 is blocked in a boot loop. I've read about some methods allowing to reset the tablet thanks to adb and or fastboot.
But my problem is that in whatever state my tablet is, adb and fastboot never seem to be able to detect it, so I can't use them to wipe it and I don't see an other so I can't repair my tablet.
My question is : has anyone been able to make a boolooping tablet detectable by android dev tools ?
Alternatively, has anyone been able to get in touch with samsung support on that issue ? Are io edition tablets under warranty ? I haven't seen any reports related to that.
Thanks in advance for your answers, it is my last chance attempt to make that tablet work again.
Click to expand...
Click to collapse
The issue here is having the right driver. Assuming you imstalled the amdroid ask, run sdk mamager tick 3rd party then usb drivers and let the sdk manager install the drivers. Thwm go to your pc control panel and check for android or samsung device (going by memory here) if there is an exclamation mark, right click and selwct update driver then 'let me choose' then find android device among the listed. Click that and try odin
Sent from my GT-P7510 using Tapatalk
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Thanks a lot for those answers, I have finally been able to restore my tablet using this method found on rootzwiki / topic 2525 guide wifi flashing stock bootloader to io tab (sorry but i can't post links on xda)
Sadly, it also installed samsung's touchwiz but that is nothing that a custom rom can't fix .
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
adiemask said:
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showthread.php?t=1706918
if it didnt help u just reply and we´re gonna look whats next to unbrick ur phone
Hi
Thanks for your reply, I have hit the 'Thanks' button
I read the posting you referenced but it doesn't really offer a solution to my problem.
As described earlier I rooted my phone and flashed a Rom (Maximus) succesfully but on turning the phone on after installing the new Rom I got into a cycle of the phone rebooting without actually getting past the lock screen. My thoughts at that stage were to re flash using stock rom but on running fastboot and plugging into my Mac OSX machine via USB, the phone doesn't show up in 'devices' on the Mac. I have also tried 'adb devices' form within Android Dev Tools and although 'adb' runs fine no device is reported. Of course without devices being avaialble to 'adb' then I cannot reflash!
I have also tried from within a bootcamp installation of 'Windows XP' installed on the mac with the same results, this with 'HTC Sync' installed and therefore providing the USB Drivers required within Windows.
I have tried logging into fastboot using 'power' and 'Down Volume' at various stages of the boot process on the phone but have never seen the phone within devices.
Clearly prior to installation of the Rom (Maximus) I could see devices at both the Finder window on the Mac and from adb devices.
Any help or insight you could provide would be very gratefully received
Ok ok ok dont worry
I had to read a bit and found quit much german threads where they flash back the stock rom
as is suggested u cant flash it with odin...
the only solution i woul suggest is that u have to find a computer running windows
there its very easy to restore the stock with the methods u described earlier in the thread...
hope u get done let me know what happend
=)
The question remains; how can I flash anything be it a hacked rom or an official rom when I cant see the 'device' in both windows and mac osx?
I think what I am looking for is a reason why the phone isn't seen when plugging in via USB. Once it is seen as a 'device' I will be able to flash anything via 'adb'.
Thank you for your continued interest and assistance
ok so u know how the get it back but ur phone is not really recognized by ur computer
but i found a method using the bootloader
the problem is that the instructions are in german
but i think if u google a bit u may find it
Don't know if I misunderstood what you said..but to get into recovery, you hold volume down and the power button when the phone is turned off. Not during the boot process.
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
moksha098 said:
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
Click to expand...
Click to collapse
Yes, I know that. He said he attempted to do that DURING the boot process. I was stating that he had to do it while the phone was powered down.
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
adiemask said:
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
Click to expand...
Click to collapse
But if this doenst work why dont u try the method with the recovery mode or the bootloader i suggested
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Potentional Tutorial
philipkroberts said:
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Click to expand...
Click to collapse
philipkroberts said:
Hello all,
I have googled, and searched forums high and low to no result so I thought i'd ask.
I recently purchased "KVD APOLLO ONE K6589 Quad-Core Android 4.2.1 WCDMA Smartphone w/ 5.5"
Im new so I can't post external links, however if you go to google or deal extreme and search, you'll find it easy enough.
The phone itself was next to nothing ($180) so even if its Unrootable, I'm not too fussy.
I would however prefer it rooted, I have read that you can basically use the MTK6577 rooting tool on the device?
Would this risk bricking the device.
I'v attempted to contact the manufacturer however to no avail! This is a rather new model so I know im being a tad impatient but if anyone can help then please do
Thanks guys
Click to expand...
Click to collapse
Also looks like im getting the Star N9589 just due to the more support available.
Anyhow until then, failing any answers from here, another chinese forum a spanish one and Yahoo answers I am going to go with the following method, If it dies, It dies this was my own fault for not doing enough research and at least it lets others know. I would send it back to DX But cba with postage fees and the hassle;
THIS IS DONE AT YOUR OWN RISK! -
APOLLO ONE - MTK 6589 K6589
Please note all tools and zip files mentioned I cant link to yet should you feel you want them please post in this thread and I will PM you, Gotta get my post count up first!
Guide by philipkroberts Twitter @philipkroberts
Revision 1 - People to be added to credits for leehed source, currently untested, concept only
Before anything try and boot into any form of recovery mode and backup if possible!
DISABLE UAC in WINDOWS 7
RIGHT CLICK RUN AS ADMIN ON ALL FILES
ALLOW NON TRUSTED DRIVER INSTALLATION (Google this if unsure)
On the phone install anububu on pc phone. - See what model it detects as and note it down.
Run MTK DROID TOOLS and connect phone see if drivers After a few seconds, the box should turn blue, and it should say "Apollo ONE or Other Name " besides it. The drivers are working.
If not try the other drivers in the drivers folder using device manager, there are many tutorials for this I cba typing one im so tired! and make sure you have the only trusted drivers thing turned off, if you constantly get unknown driver then your out of look and wil have to try and source some yourself.
Win7 (This method has not been tested by myself. Confirmation required.)
HOW TO MANUALLY INSTALL ANY DRIVERS IF NEEDED
a - Downloading This tool Called EASYBCD
b - Use it to restart your computer in advanced boot mode. (PRESSING F8 WHILST BOOTING UNTIL YOU GET THE OPTION FOR Disable signed driver enforcement)-Must be done everytime you wanna root a phone with this method.
c - Follow instructions and disable SDE.
d Manually install drivers, if above did not work (Yellow sign issue)
e Navigate to control panel - > Hardware and Sound - > Device Manager
f You should see a driver notice with a yellow warning sign next to it.
g Right click on it and choose "Update driver..".
h- Manually assign drivers, usually the choice furthest down.
i- In the window which should have appeared, navigate to the preload/Mt6590 folder and press OK.
j- If SDE is turned off, you should see a red warning window. This is normal, just accept the message prompted.
k- The drivers should now be successfully installed.
l - Once this is done open C:\Users\Hate\Desktop\Chinese Droid Rooting\MTKROOT TOOLS\Root_with_Restore_by_Bin4ry_v28\runme.bat Hope it ****ing works if so your rooted, If not try this next few steps, AGAIN at your own risk, no need to format just continue from here.
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
THE FOLLOWING STEPS ARE FOR THE STAR S5 - SAME PROCESSOR BUT NO GARUNTEE. DO NOT FOLLOW THESE STEPS UNLESS YOU ROOTED ANOTHER WAY AND NOW JUST WANT TO INSTALL A CWM
0 - Use PC to copy UPDATE-SuperSU-v.1.25.zip to the root of SD CARD, do not unpack just leave whole zip there.
1 - Turn off your phone, remove your battery. (Do not connect your phone to the computer yet!)
2 - Navigate to the "SP Flash Tool" folder, and run the tool.
3 - On the right side of the tool, there should be a button, iconed with a folder, named "Scatter-Loading". Click this.
4 - Navigate to the "Yulypis Recovery" folder, and double-click on the "Mt6589_Android_scatter-emmc.txt".
5 - You should be back at the SP Flash Tool start-screen, and there should have appeared a list of text and hex-codes.
6 - The "Recovery" line, should be ticked off, and preloader should be red.
7 - Now, click on the button named "Download", with a blue arrow on it. Press "YES" on the NOT ALL images has been correctly loaded warning.
8 - Connect your phone to a USB 2.0, with removed battery. The program should now work, and if drivers is set up correctly, the 0% will turn 100% and a green circle will appear in the middle of the screen. If your phone disconnects before the flashing tool is able to recognize your device, try putting the battery back into the phone before running SP Flash tool. Additionally, if this doesn't work, try using different drivers in the drivers folder
9 - Disconnect your K6589 from the computer when you see the green circle, insert the battery and boot the phone. Wait for it to get to the start screen.
11 - Installing SuperSU through Yulypis recovery
12 - Run "MtkDroidTools.exe" from the folder.
13 - Connect your device, and after a few seconds, information about your device should appear.
14 - Click on reboot, on the mtkDroidTools start-screen, and choose "..recovery".
15 - If recovery has been properly flashed, your device will now enter Yulypis recovery. Blue, with english text.
16 - Controllers: "Power = Enter, Initialize", "Volume down = Scrolling down". (Don't remember if volume up was bugged or not)
17 - Enter "Install zip from SDcard" - > Navigate to the earlier copied "UPDATE-SuperSU-v.1.25.zip and initialize it by pressing the power button.
18 - Follow the on-screen instructions, and it should be prompted to install after 1-2 more screens.
19 - Reboot the device by clicking on "+++++back+++++" and "Reboot now / Reboot Device".
Either way I am going to smash this in a week or so when the phone arrives from DX and will keep people update.
Peace
Please I want to buy this phone. Can you answer me a few doubts I have?
- How is the viewing angle? Cause i purchased a tablet from china and the angle is very bad.
- Has proximity sensor?
Are you ok with the phone?
thank you.
cabrote said:
Please I want to buy this phone. Can you answer me a few doubts I have?
- How is the viewing angle? Cause i purchased a tablet from china and the angle is very bad.
- Has proximity sensor?
Are you ok with the phone?
thank you.
Click to expand...
Click to collapse
I'm still awaiting the phone, hence why that guide is at your own risk.
However from what I have been told and gather that should root the phone no problems.
As for custom roms, I wouldn't even bother trying!
Once the phone gets here I will test my tutorial and re-write it into a more easy on the eyes fashion.
Thanks
http://www.fastcardtech.com/APOLLO-ONE-K6589?u=37825
They sell the phone, for an extra $3 they root before sending.
It cant be that hard, I'd love to know someone in that factory!
I'm looking for a link to download the full stock firmware for this device.
Anyone, please?
...or at least a firmware dump from a non-modified working phone.
One could use MTK Droid Tools and SPFlash to perform this task easily.
PM me for assistance if you need it.
Thank you.
Unbrick Oppo R5
Since oppo forums support is minimal and a lot of Oppo R5/ R5s owners are facing difficulties flashing new rom and since Oppo is unbrickable here are a guide as posted to oppo forum members by the member Ricky.
I had clear instructions not to post this tool anywhere BUT THEY DON’T SUPPORT ANY DEVICE and I have to break my promise as they broke any kind of support.
This community (XDA) is to help all members
The tool works with windows 10 and not only with windows 7 as they mention in their instructions
Packages you have to download first
1- Firmware ColorOS https://www.partage-facile.com/LM6Y85FF7Z/r8106ex_11_a.16_150806.tar.bz2.html
File Name: R8106EX_11_A.16_150806.tar.bz2
Size: 1.4GB
MD5: F85ED63BA637B559976D9BFF0AED0187
2- Instructions:
https://drive.google.com/file/d/0B3AWkNVCRSNVZGNRUE1rQW5YOFk/view?sid=
3- Driver : http://en.oppo.com/downloads/firmware/driverForFind5.rar
Mirror for driver http://www109.zippyshare.com/v/MEMiPlOv/file.html
Attention
a-Unbrick tool will wipe all data on your device including photos and music etc, if do you want to reserve your data please make o back up on your PC
b- After unbrick the first time power up take around 5-15 minutes
c- The most important things are to install the driver. For windows 10 you must enable unsigned signature verification through windows advanced settings (google it) prior driver installation.
d- In order to shut phone completely hold the power button for 8 -10 secs
How to use the tool
I tried to use the tool and the files you provided to revive my Oppo R5, but the layout of the tool which you provided is different from the one in the picture (you gave in the links). It is also in foreign characters so difficult to choose with option to tick.
In fact, the version that came with you package does not have as many option as the one in the picture. My confusion actually starts from when the program starts. There is a drop down menu to chose from a long list of 14005 to 15065. Which one do I choose for Oppo R5?
As for the qualcomm port, the device manager identified my phone on port 9006, whereas the picture shows 9008.
Please help me. I really need to get this phone to work. The phone would not do any thing is the buttons are pressed individually or in combination, other than being detected by the computer and enumerated in the device manager.
Many thanks in advance for your help.
amadoro said:
I tried to use the tool and the files you provided to revive my Oppo R5, but the layout of the tool which you provided is different from the one in the picture (you gave in the links). It is also in foreign characters so difficult to choose with option to tick.
In fact, the version that came with you package does not have as many option as the one in the picture. My confusion actually starts from when the program starts. There is a drop down menu to chose from a long list of 14005 to 15065. Which one do I choose for Oppo R5?
As for the qualcomm port, the device manager identified my phone on port 9006, whereas the picture shows 9008.
Please help me. I really need to get this phone to work. The phone would not do any thing is the buttons are pressed individually or in combination, other than being detected by the computer and enumerated in the device manager.
Many thanks in advance for your help.
Click to expand...
Click to collapse
For R5 use 14016.
mermigas said:
For R5 use 14016.
Click to expand...
Click to collapse
Thank you for your reply. I tried to use the tool again, but there is not option for 14016. The full list is here: 14005, 14006, 14023, 14037, 14039, 14040, 14041, 14042, 14043, 14045, 14046, 14047, 14050, 14051, 14052, 14061, 14062, 14065, 14068, 140083, 14085, 14097, 14098, 15005, 15005_4G, 15006, 1500_4G, 15007, 15007_4G, 15011, 15012, 15013, 15018, 15057, 15061, 15065.
The flash tool that I am using is V1.5. Is is possible that I am using a wrong version for what I need to do?
Many thanks for your attention.
amadoro said:
Thank you for your reply. I tried to use the tool again, but there is not option for 14016. The full list is here: 14005, 14006, 14023, 14037, 14039, 14040, 14041, 14042, 14043, 14045, 14046, 14047, 14050, 14051, 14052, 14061, 14062, 14065, 14068, 140083, 14085, 14097, 14098, 15005, 15005_4G, 15006, 1500_4G, 15007, 15007_4G, 15011, 15012, 15013, 15018, 15057, 15061, 15065.
The flash tool that I am using is V1.5. Is is possible that I am using a wrong version for what I need to do?
Many thanks for your attention.
Click to expand...
Click to collapse
Sorry mistyped
14061
Also there is an English Version for the flashing tool here
https://forum.xda-developers.com/r7-plus/help/oppo-r7plusm-msm-tool-t3313759.
Just download it and copy to the folder that there is the Chinese tool
For me the Chinese version works fine
Also there is a same guide here
http://community.oppo.com/en/forum.php?mod=viewthread&tid=51497&extra=
mermigas said:
Sorry mistyped
14061
Also there is an English Version for the flashing tool here
https://forum.xda-developers.com/r7-plus/help/oppo-r7plusm-msm-tool-t3313759.
Just download it and copy to the folder that there is the Chinese tool
For me the Chinese version works fine
Also there is a same guide here
http://community.oppo.com/en/forum.php?mod=viewthread&tid=51497&extra=
Click to expand...
Click to collapse
Thank you so much. it worked. Not my Oppo r5 is back alive.
Where is the download?
Is it normal that when I hit the download link there appear aliexpress??
I thought I had bricked my R5 but while trying to follow this guide it wasn't showing up in the "Ports" section of the Device Manager. I found that my phone still had fastboot, so I used it to install latest TWRP and then the repair rom. And now my phone is finally back to working condition! I hadn't modified in any way my phone and one day it got stuck at the logo. Anyway, thanks for the guide Mermigas!
anyone mirror pls
mega
[email protected] said:
anyone mirror pls
Click to expand...
Click to collapse
[dead link]
If it asks for a key leave it blank
Kushracer said:
https://mega.nz/#F!q8YFEJyB
If it asks for a key leave it blank
Click to expand...
Click to collapse
No asking for decryption key
mirror
Uploading here: R5S Unbrick Tools
Please help
After i have done all those instructions: my phone was completely dead(no more display and can't use any buttons).
Please what should i do for revive that.
Link Broken
cpuld you re-load the link of Color Os firmware please?
Its not valid now =(
Number for R5S?
Hi, I tried the 14061 for my OPPO R5S. Unfortunately it did not work. Now the phone is not starting.. help? Should I use another number?
Update 2021.01.24: I consider the problem mentioned here as solved, since it can be resolved with MTK Bypass explained in the Guides Section. BE CAREFUL however to ONLY choose "Download Only" from the dropdown box in SP Flashtool! DO NOT select anything with "Format" in it, else you will lose S/N, MACs and IMEIs!
--- Original post ---
Hi, I have hard-bricked my new Realme 6 while trying to root it with Magisk. At the moment I am stuck in a bootloop at the power-on logo (realme in white letters). The boot animation (yellow realme letters) does not appear, instead the phone reboots after ~35 seconds. The bootloader says "Orange State".
I can NOT enter fastboot nor recovery mode by any key combination. Holding Power and Vol- makes the string RECOVERY MODE appear for a split second in the lower left part of the screen, however nothing happens afterwards.
I can power down by holding Power and Vol+ an releasing them immediately after the screen goes blank.
Holding Vol- and Vol+ while the phone is off and connecting USB makes a USB serial device appear on a windows machine for about 1-2 seconds before it disappears again.
I am very thankful for any hints on how to unbrick the device.
Here's what I have done in detail to mess up the phone:
1. OTA-Update to the latest OS in my region (EU11.A.48)
2. Unlocked the bootloader with the realme In-depth Test app (everything fine so far)
3. Download stock firmware RMX2001EU_11.A.48 ozip from realmeupdater.com
4. Unzipped with gnu unzip (content was readable, no extra decrytion tool for the ozip needed?) and extracted boot.img
5. Installed Magisk Manager and uploaded boot.img to the phone
6. Patched boot.img with Magisk Manager (and if I remeber correctly DIDN'T UNCHECK Preserve AVB 2.0/dm-verity)
7. Certainly FORGOT to do anything with vbmeta.img
8. Did NOT erase cache and userdata
9. Flashed patched boot.img directly and WITHOUT --disable-verity or --disable-verification
10. Rebooted the phone.
Am I correct that my problem is the AVB/dm-verity part?
Why does the modified boot.img affect the recovery (I thought they were seperate)
Can I try something with SP Flashtool?
I do have a second intact device that I didn't dare to touch yet, if that helps resolving the issue (e.g. for SP Flashtool readbacks).
As said any advice is highly welcome. Please ask I you need any more information to help.
I did that too... Magisk patched boot .img process of rooting is the risky process , I bricked my device, got it into red state.. tried thick and thin to revive using various flash tools, unable to do it, finally went to a shop , got it fixed, go-to a good repair shop, if you go to the service center, they will say replace motherboard for 5 k , I hope it helps, do traditional unlock bootloader TWRP recovery then flashing Magisk zip method for rooting process.
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Yes, you are right , red state means that, I guess bcoz, I may have formatted it and ran again unlocked bootloader but it showed unlocking failed, but I thought that I had previously unlocked it so it should be unlocked but I forgot to do that app thing process of deep test again, and I was on Android 10 latest and patched boot img of previous version using magisk, now I understand what mistake I made, I should have used boot IMG of current version of a 10 , but still I am afraid of doing this magisk method of rooting by patching boot IMG bcoz repair cost me 800/- , and I found out on YT that the latest version of a 10 of my device doesn't readily allows twrp and flashing zip of magisk.... Plus there are half baked info on important things, this is new device for me, I have had rooted Samsung and Lenovo, but rooting this is kind of tricky, bcoz it's still new, I think.... Want to try .... But I m afraid.... Tried fastboot method of TWRP flashing but can't replace stock room, so I guess I can't root .....
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
cmfan said:
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
Click to expand...
Click to collapse
Thnx man, I have rmx 1825 , but the process would be same for my device, I would have to search for it...
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
daeSundae said:
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Click to expand...
Click to collapse
I think there is no Emergency Download Mode in Realme devices.. pls guide ...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
daeSundae said:
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
Click to expand...
Click to collapse
Thnx that's a life saver, I am afraid to go forward with the device, this is promising, I will try, I found out that the new version c17 os Android 10 I am unable to root by twrp magisk zip flashing method, twrp isn't installing, there's an .ofp extracter, but it gives virus with software, unable to do, even talked on WhatsApp and gave him Gmail id, will try this method , I wanted the SP flash tool method, it's simple and can readily restore the stock rom... Thnx Sundae.. daesundae ... What kind of name is that...?? .. chuckles...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
cmfan said:
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
Click to expand...
Click to collapse
I saw everything that You posted, incidentally the YouTube video on this is on rmx1825 , thnx, whatever you posted it helped..