Related
My phone is now updated to the 4.4.2 version, E98020h. The first error I kept getting in the command window for kitkatroottool running StartRoot.bat was that './adb.exe' is not a recognizable or executable command, whatever that error was. I was able to fix this by simply adding a line to the batch file to change the directory to the current folder I was using. Adb would execute, device gets found, and it reboots. But when this did happen, the phone would reboot into recovery and would hang on the screen with the little Android guy lying down with his front compartment/chest open and the red triangle with an exclamation point. I don't know if this is normal or not, but I have tried this several times, waiting up to 20 minutes on this screen before proceeding on the command window, and it is unable to push the necessary files. or properly continue the root process. I see nothing on the screen, even after pressing power/volume controls, along the lines of selecting files or browsing through some recovery menu. (Obviously I don't have a custom recovery flashed right now.... did I need one?) Is there a better guide I can follow to do this? any videos? USB debugging definitely was enabled, tried both with charge only and MTP (I didn't see anywhere that specified a connection mode...?)
Thanks in advance for the help. I DID search but couldn't find anything...my bad if I missed what I was looking for. Please just point me in the right direction
Try kingo ??? It might root it
2SHAYNEZ
shayneflashindaily said:
Try kingo ??? It might root it
2SHAYNEZ
Click to expand...
Click to collapse
Just tried that, got root but no loki support. Still could not get CWM to loki-ifiy properly.. keep getting that error that there was an "error loki-ifying the boot image" or something like that
frankp124 said:
Just tried that, got root but no loki support. Still could not get CWM to loki-ifiy properly.. keep getting that error that there was an "error loki-ifying the boot image" or something like that
Click to expand...
Click to collapse
Cwm off freegee?...
2SHAYNEZ
shayneflashindaily said:
Cwm off freegee?...
2SHAYNEZ
Click to expand...
Click to collapse
I tried that, but it kept giving the error that something was getting terminated while waiting for a process to finish, and then another error performing the action loki_recovery. I have attached the log.txt file from the app....
I don't know if CWM flashed successfully or not as I didn't bother trying to test is since the loki error was the initial problem anyway. If I had to guess I'd say that CWM would have launched and ran properly except for its tasks in loki-ifying.
I have been looking at this thread recently.... http://forum.xda-developers.com/showthread.php?t=2700086
Currently trying the method from the 2nd post: back to stock TOT on 4.1 with LGflashtools, root, VooDoo, OTA update, and then freegee again. Worthwhile? Advice?
Recently, whenever I use the fastboot command from my PC with my Zenfone 2 (64 gb) I am getting responses that read ”FAILED (remote permission denied)".
As an example, I flashed the new TWRP recovery with fastboot and got these messages:
Sending xxxxx
OKAY
Writing xxxxx
FAILED (remote permission denied
The odd thing is, the command appears to have worked as the new recovery has been flashed as desired. Anyone have an idea what's happening and how to eliminate the supposed error?
I should add that the phone is rooted and bootloader is unlocked.
I just noticed the same "problem". I caused a boot-loop (I believe by trying to get the root companion app for GSAM Battery Monitor installed to /system/priv-app), so went to attempt a fix somehow. My TWRP recovery was gone at first, tried reflashing and got the same message as you. But, likewise it did work.
Also a rooted ZE-551ML, bootloader unlocked and recently upgraded to 2.19.40.22 (maybe it's something in the .20 to .22 update)?
P.S. I'm considering myself lucky, managed to use TWRP to mount /system and then deleted the 'com.*' folder I copied into there. Rebooted fine after that...phew!
having the same issue.. any possible fix ?
stupid_productions said:
I just noticed the same "problem". I caused a boot-loop (I believe by trying to get the root companion app for GSAM Battery Monitor installed to /system/priv-app), so went to attempt a fix somehow. My TWRP recovery was gone at first, tried reflashing and got the same message as you. But, likewise it did work.
Also a rooted ZE-551ML, bootloader unlocked and recently upgraded to 2.19.40.22 (maybe it's something in the .20 to .22 update)?
P.S. I'm considering myself lucky, managed to use TWRP to mount /system and then deleted the 'com.*' folder I copied into there. Rebooted fine after that...phew!
Click to expand...
Click to collapse
I had the same fastboot problem, but now is worse. I did a unthetered recovery and rooted by flashing superuser.zip. Now i can´t go to bootloader or recovery, but i have root access (phone is strangely working normal, i just can´t uptade, acess bootloader and recovery)
Why did you deleted folders in your phone? I think i have some issue like that. Can i solve my problems like you did since i have root acess and can do that with root explorer?
same issue here, any known fix so far?
JulioQc said:
same issue here, any known fix so far?
Click to expand...
Click to collapse
nothing for me, but once my phone is rooted and unlocked i flashed twrp recovery and use only that.
Okay so I'm new to all this rooting and stuff and I was messing around with TWRP and now my when I turn on my OP3, it shows "md5 checksum failed" with "cache:failed", "system: failed", "system_aging:failed" and goes into a bootloop. And I cant even boot it to recovery mode. It's driving me crazy!
Can you still boot into fastboot? Turn on with volume up, if so reflash TWRP, and then restore your backup, or flash a stock rom.
ghostofcain said:
Can you still boot into fastboot? Turn on with volume up, if so reflash TWRP, and then restore your backup, or flash a stock rom.
Click to expand...
Click to collapse
I can boot it into fasboot and I tried flashing TWRP, OxygenOs and even Cyanogenmod. Still didnt work.
Didn't work how, are you getting errors in console?. Can you flash TWRP and boot into it?
You have successfully bricked your device.
Don't worry use a Oneplus download tool to download stock firmware to your device in download mode.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
The method 2 worked fine for me.
Go ahead..!!
Hope it helps
A bricked device is broken unable to be fixed, this is a soft brick as you can still get it to respond.
For future users if you broke something and want help please supply at least the following.
1. What you did, yes it's embarrassing but maybe someone can undo it.
2. What you are still able to do, can you access recovery, fastboot or adb.
3. What you've tried, if you try and flash something and get an error message let us know.
The more information you supply the better the chances someone can help. A simple my device is bricked help can't achieve much.
So I'm telling now how I got to this situation:
I'd installed a rooted OxygenOS with TWRP. I don't know how I thought it was a good idea to lock the bootloader after I installed TWRP, still did it. After that I was able to load in to fastboot, nothing else. Followed Method 1 on the link from Joyo-rocker and came to the posters message. Now I'm trying Method 2. Will update this post.
Edit: If your phone shows the boot messages "md5 checksum failed" with "cache:failed", "system: failed", "system_aging:failed" you need to fully reload your ROM over the unbrick tool. Look for Method 2 in Joyo-rockers link in this post (cant post links yet)
flobiwahn said:
So I'm telling now how I got to this situation:
I'd installed a rooted OxygenOS with TWRP. I don't know how I thought it was a good idea to lock the bootloader after I installed TWRP, still did it. After that I was able to load in to fastboot, nothing else. Followed Method 1 on the link from Joyo-rocker and came to the posters message. Now I'm trying Method 2. Will update this post.
Click to expand...
Click to collapse
Had the same issue, method 2 works fine.
Hi
I have same issue!!!
I tried the secund method! But the same.....after the 1+ logo :
cache: failed
boot: failed
boot_aging: failed
system: failed
md5 checksum failed
I opened the Msmdownloadertool v3.0.2 using Admin privileges!
Volume up 10s connected phone usb cable....
press 'start" ....after I get green indicator in the tool...My phone rebooted....and I got these messege ! .....and my phone turn off.....
Please help
Please...
kovacsabesz said:
Hi
I have same issue!!!
I tried the secund method! But the same.....after the 1+ logo :
cache: failed
boot: failed
boot_aging: failed
system: failed
md5 checksum failed
I opened the Msmdownloadertool v3.0.2 using Admin privileges!
Volume up 10s connected phone usb cable....
press 'start" ....after I get green indicator in the tool...My phone rebooted....and I got these messege ! .....and my phone turn off.....
Please help
Please...
Click to expand...
Click to collapse
You didnt download the right tool, method 2 includes every needed partition and should revert you to full stock 3.1.2
Oh,
Done.....
I fixed it! Thanks guys!
Deleted
---------- Post added at 09:07 AM ---------- Previous post was at 09:00 AM ----------
sashamalla said:
Okay so I'm new to all this rooting and stuff and I was messing around with TWRP and now my when I turn on my OP3, it shows "md5 checksum failed" with "cache:failed", "system: failed", "system_aging:failed" and goes into a bootloop. And I cant even boot it to recovery mode. It's driving me crazy!
Click to expand...
Click to collapse
Go to the folder where the recovery tool.exe is. Boot your phone into Fastboot.
Search for cache.img, system.img, system_aging.img and put them in your ADB file folder
Type this:
Fastboot devices > doesn't show up? No worries I'll help you later this day just let me now.
Fastboot flash system system.img
Fastboot flash system_aging.img
Fastboot flash cache cache.img
If it boots and you don't have Sim and WiFi. Then reflash Oxygen OS and don't boot it! Boot it into Fastboot and type:
fastboot erase modemst1
fastboot erase modemst2
Now boot it and u can do whatever you want!
Same happened to me, reinstall windows and start again with method two, was a driver issue
TheLoverMan said:
Same happened to me, reinstall windows and start again with method two, was a driver issue
Click to expand...
Click to collapse
Why would you install windows instead fix the driver thing.
Was having problems with uninstalling the drivers. They would always come back so only way I could do it was by a reinstall of windows.
This was already mentioned, as i remember. Just let me search for a minute cause i had this same issue.
http://forum.xda-developers.com/attachment.php?attachmentid=3875375&d=1473889816
Flash this TWRP, it is 3.0.2-19 for temporary but i use it as daily.
kovacsabesz said:
Oh,
Done.....
I fixed it! Thanks guys!
Click to expand...
Click to collapse
Hey! Im having the same problem. Please help me with the way you did, Im Stuck . please help
TheLoverMan said:
Was having problems with uninstalling the drivers. They would always come back so only way I could do it was by a reinstall of windows.
Click to expand...
Click to collapse
Ye well there is a driver enforce mode link even in the hardbrick guide... No need to reinstall Windows lol
I Unbricked Successfully
I unbricked the phone successfullly but now during startup its asking me password. The one I had isn't working and I dont know what to do. can anyone help me here? Can I find a Password in the recovery tool?
Pratik121 said:
I unbricked the phone successfullly but now during startup its asking me password. The one I had isn't working and I dont know what to do. can anyone help me here? Can I find a Password in the recovery tool?
Click to expand...
Click to collapse
You see.. OOS had force encryption. Go to Fastboot and type "fastboot erase userdata" then go to recovery and flash OOS or any other rom.. Password should be gone now.
Dear XDA Community,
in past 2 months i've been using CM13, constantly having some trouble with apps involving the camera, such as the camera app(surprise) and e.g. snapchat.
So yesterday I decided to update my CM Build, not knowing it would be to CM14 and with this Android 7.
So resulting from this I experienced a lot of issues with different apps, especially the google ones and for example Instagram. I DID NOT Upgrade my twrp, which was pretty stupid as I found out.
So this morning I checked again for CM Updates and Updated to Version Nightly...25 I think... but because I did not update my TWRP it did absolutely nothing except bricking my phone.
I already followed through the Guide for Hard Bricked OP3s (both steps) "http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700"
Though it sadly did not work for me. The Recovery tool and all works but when I want to boot my Phone the md5checksum pops up after the OP3 Logo and it tells me that everythings fine except "boot: failed".
I tried the procedure of the Hard Brick fix over and over again but nothing seems to work. I am fairly new to this whole Custom Rom stuff so I have absolutely no clue what do to.
Does anyone have any idea that could help?
Best Regards
Aliasalex
Try fastboot flashing the whole rom.
how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum
try the 1st method you mentioned in the OP but flash https://www.androidfilehost.com/?fid=24591020540821926 . from what I understand, you need to full write all your partitions since they seems corrupted.
aliasalex said:
how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum
Click to expand...
Click to collapse
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.
Demian3112 said:
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.
Click to expand...
Click to collapse
Yes a Kedacom USB Device "Android ADB Interface" is listed.
aliasalex said:
Yes a Kedacom USB Device "Android ADB Interface" is listed.
Click to expand...
Click to collapse
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk
Demian3112 said:
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk
Click to expand...
Click to collapse
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own
aliasalex said:
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own
Click to expand...
Click to collapse
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.
Demian3112 said:
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.
Click to expand...
Click to collapse
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.
aliasalex said:
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.
Click to expand...
Click to collapse
Nice, whdn you boot you still get those errors in red letter something with "failed boot". Then manually flash the boot. Img provided in the folder where you ran the Unbrick tool from. Command for Fastboot "fastboot devices", then "fastboot flash boot boot.img". Make sure that Kedacom is not in device manager when you are accessing Fastboot.
problem : received ota update, applying which, led to the soft brick. On booting -> OnePlus logo comes up after which screen goes black with permanent blue led light.
condition : able to boot into recovery and fastboot. Bootloader is locked and i cannot unlock it since oem unlock toggle is off.
solutions tried :
1) RECOVERY(stock) : wiped EVERYTHING. tried sideloading oos 9.0.6 through adb. reaches till 47% after which it fails. shows "Total xfer 1.00x" on adb and "installation failed" on recovery.
2) tried with unbricking tool. device identified as Qcom 9008 after which msm tool identifies the device too. process completes with no error and green message at the end. but the device is in same state as before.
Is it a hardware problem? I doubt if the motherboard is fried, since the display is coming and everything mentioned above is working.
Also : will oneplus service centre be able to unlock the bootloader if i ask them to?
Please help!
I had an same issue while flashing 9.0.6, but side loading latest OB solved the issue for me and my device is saved.:laugh:
JackSparrow17 said:
I had an same issue while flashing 9.0.6, but side loading latest OB solved the issue for me and my device is saved.:laugh:
Click to expand...
Click to collapse
what's OB?
JackSparrow17 said:
I had an same issue while flashing 9.0.6, but side loading latest OB solved the issue for me and my device is saved.:laugh:
Click to expand...
Click to collapse
what's OB?
Naveenjain said:
what's OB?
Click to expand...
Click to collapse
Open Beta OOS Rom
https://otafsg1.h2os.com/patch/amaz...43_OTA_054_all_1906241434_15cbb014579a206.zip
JackSparrow17 said:
Open Beta OOS Rom
https://otafsg1.h2os.com/patch/amaz...43_OTA_054_all_1906241434_15cbb014579a206.zip
Click to expand...
Click to collapse
This didn't work too!:crying:
failed at 47% again