Hi all, my nexus is a very poorly little thing at the moment. Bootloops on the google screen on start and can't get to recovery from the bootloader. I have tried flashing with a stock rom but it is still bootlooping. I'm assuming the next step is to try flashing the bootloader, something I'm very scared of doing without being absolutely sure that I'm not about to turn my critically ill nexus into a completely dead nexus. Could anyone give me the exact commands I need to use to do this?
cthulhu_tentacles said:
Hi all, my nexus is a very poorly little thing at the moment. Bootloops on the google screen on start and can't get to recovery from the bootloader. I have tried flashing with a stock rom but it is still bootlooping. I'm assuming the next step is to try flashing the bootloader, something I'm very scared of doing without being absolutely sure that I'm not about to turn my critically ill nexus into a completely dead nexus. Could anyone give me the exact commands I need to use to do this?
Click to expand...
Click to collapse
I think all you need to do is reflash the recovery. Your bootloader may be fine. Did you accidentally erase your recovery partition? What were you doing when you first saw the problem?
DroidIt! said:
I think all you need to do is reflash the recovery. Your bootloader may be fine. Did you accidentally erase your recovery partition? What were you doing when you first saw the problem?
Click to expand...
Click to collapse
I didn't do anything unusual. Went to sleep. Woke up in the morning and it was frozen. Gave it a long press on the power key and has been stuck ever since. Just tried the one-click restore here http://forum.xda-developers.com/showthread.php?t=2381582 and it is still bootlooping after that.
OK, I'd download a recovery to your computer and fast boot flash it that way. I've not used that tool, but I did the same once. I accidentally erased my recovery partition. So I just redownloaded the latest twrp .IMG and did fast boot flash recovery and all was fine. That's what I'd suggest for a start.
---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------
Ah I see, that tool wipes your entire device. So I'd go here https://developers.google.com/android/nexus/images and download the latest factory image. While in your boot loader, connect to your computer and run the .bat file from the download. That all return you to stock. Be patient it takes some time, but that should solve your issue.
Thanks, giving it a shot now
Yep, download, unzip, connect to computer while in bootloader, and double click the .bat file. It will go through a series of flashings. It's restoring everything to factory. Just leave it plugged in until it starts to boot up. ?
Related
All,
I flashed JellyBelly last night, flash the JB bootloader, then the ROM etc...everything was working fine, restored apps via titanium etc...my phone was up and running in JellyBean. I was playing around with it, then notice some apps wasn't starting, media(music) wasn't being scanned so I attempted to reboot into recovery and fix permissions thinking that will fix my problem. Anyways, I rebooted, and was stuck in the Google screen. I took the battery out, got into recovery and tried to dirty flash the rom, it failed. I tried to restore from nandroid i did, and it also failed.
Now all I can get into is to recovery. Seems like everything I tried whether its nandroid or the jellybelly rom, it would fail. Is my SD corrupt? I did attempt to restore from Liquid 1.5, that went through, but when it tried to reboot, it would fail and reboot again and again.
Is my phone dead? What are my options?
Please help!
Thanks!
you are far from dead, as of now. How long did you let it sit? I've done some ROMs where it sat at the Google splash for 5 minutes before it started to boot. I would get the Kies, go into download mode and start from the beginning. That will put it back to how it was straight from the factory (minus the locked bootloader).
I am not familiar with Kies...can you explain a bit?
I googled a bit and found this link for GNex ToolKit V7.4, could this be an option to unbrick my phone?
http://forum.xda-developers.com/showthread.php?t=1400871
leoingle said:
you are far from dead, as of now. How long did you let it sit? I've done some ROMs where it sat at the Google splash for 5 minutes before it started to boot. I would get the Kies, go into download mode and start from the beginning. That will put it back to how it was straight from the factory (minus the locked bootloader).
Click to expand...
Click to collapse
This is a Nexus. We don't use Kies or Odin...
OP, fastboot flash the stock images. Don't use toolkits. If you can get into recovery then you will be able to restore back to stock 100%.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=1626895
Actually, I am very new to the GNex so I am still figuring out where everything is. Since it's a Nexus device, it may not have a Kies, I just automatically think Kies when I think of any Samsung phone. Somebody will come along that is much more familiar with the GNex than I am and point you in the right direction.
---------- Post added at 01:59 AM ---------- Previous post was at 01:55 AM ----------
martonikaj said:
This is a Nexus. We don't use Kies or Odin...
OP, fastboot flash the stock images. Don't use toolkits. If you can get into recovery then you will be able to restore back to stock 100%.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Yeah, you beat me to it.
Thanks all!! I FINALLY got my phone back. I used the WUG Nexus Root Toolkit. THANK GOD FOR THAT!! Was painless to bring my phone back to stock.
Now I'm going to reflash JellyBelly Again!!
Where to begin?
I upgraded from Paranoid Android (Android 4.3.1 variant) to KITKAT 4.4 which I believe has turned my phone into an LG E960? Nexus 4.
After some data issues with 4.4 I decided to go back to PA and things seemed OK for a day or two outside of com.android.phone crashes once in a while. Then a random power cycle (initiated by me) brought me to a softbrick? beyond repair (at least every flash/fix seems to do little)
I have been able to boot into both DLmode and Recovery (TWRP 2.6) since this problem began but nothing allows me past either of those or any of the following : LG Logo (reached after my 8th or 9th teenybin attempt, and first attempt at flashing stock teeny. OR the Google logo with tiny unlock symbol at bottom.
I became frustrated and wiped everything (formatted data) through TWRP and have failed miserably with every attempt to sideload or lgnpst both .zips and .bins respectively. Now any attempt to sideload results in a "failed" attempt as it there is no folder "TWRP/Backups/......."
I have tried LGFLASHTOOL and followed directions to a T. but the issue here seems to be this. LGFLASHTOOL recognizes my phone as the LG E960 and states the LG LS970.dll isn't compatible with my phone.
Is there anybody out there that can make sense of my ranting explanations here?
The two MAIN problems troubling me seem to be this:
1) The phone is being recognized as the E960 via FLASHTOOL thus any LS970 flash or file creates a not compatible error.
2)Though TWRP seems functional, it is maybe only partially so. It wants to access a folder within itself that isn't there TWRP/Backups/....(specific random backup number)
ANY help would be GREATLY APPRECIATED. I have been at this for a day and a half.
p.s. a very odd side note. One sideload rom I flashed was Carbon, which failed to boot initially. I DID manage to have teenybin unlock, flash and reboot the phone directly into Carbon (with no data or gapps) and was able to usb over a couple .zips before getting an error "cannot be copied because device has been disconnected or has stopped responding" I thought I was in the clear and booted back into recovery via the carbon rom to flash gapps only to revert right back to my initial problem(s).......
WTF! I am lost. I've had this phone for almost a year and have used LGNPST more than a couple times with great success. I've flashed, unbricked and restored this phone and many others multiple times over the years (i.e. not a noob) Just effing dumbfounded.
edit: I have searched and read through countless threads in an attempt to find a fix for my problem with no luck. I've searched constantly to find a fix with no luck.
That was a lot of info. So lets see if you've tried these things yet.
Are you sure you don't still have the att TWRP to flash KK?
Flash TWRP 2.5.0.0
And try to flash a Stock ROM.
to get sideload to work: there is an option to make a log. it will make the partition writable after a format. had a similar issue when i first go the phone.
otherwise use an img. not a teeny bin and go back to stock zvb.
engine95 said:
That was a lot of info. So lets see if you've tried these things yet.
Are you sure you don't still have the att TWRP to flash KK?
Flash TWRP 2.5.0.0
And try to flash a Stock ROM.
Click to expand...
Click to collapse
I noticed in bootloader it references the device as mako, with a bootloader version of MAKOZ10f
I'll try TWRP v2.5.00 now. I just downloaded a Stock ZVC build.
I feel dumber and dumber as this process drags on. But appreciate the replies. I now realize my OP wasn't full of a ton of specific information. Sorry.
octhrope said:
to get sideload to work: there is an option to make a log. it will make the partition writable after a format. had a similar issue when i first go the phone.
otherwise use an img. not a teeny bin and go back to stock zvb.
Click to expand...
Click to collapse
in TWRP (still 2.6) I went into Advanced and ran 'Copy Log to SD' a button/feature I have always saw before, and never used.
I'm going to try to install TWRP 2.5 back onto the device first per previous post(er) and then I'll run this again before I try to install a stock rom.
Thanks for the idea.
I've used fastboot to flash twrp 2.5 and proceeded to 'Copy log to SD' before attempting to sideload stock rom.
In CMD this error is now returned when using commnd "adb sideload update.zip" :
failed to write data 'protocol fault <no status>
LGNPST method still giving same results. Gets to 85% error (I know this is normal) but when rebooting, boots to nothingness/black screen after quick glimpse of Google logo....
toastedjelly said:
in TWRP (still 2.6) I went into Advanced and ran 'Copy Log to SD' a button/feature I have always saw before, and never used.
I'm going to try to install TWRP 2.5 back onto the device first per previous post(er) and then I'll run this again before I try to install a stock rom.
Thanks for the idea.
Click to expand...
Click to collapse
Glad to hear ZVC almost worked for you.
If you can get into fastboot, you can install a different TWRP. fastboot erase recovery then fastboot flash recovery recovery.img
Or in TWRP flash a different TWRP, octhrope has them all here. http://forum.xda-developers.com/showpost.php?p=47679587&postcount=123
EDIT. Yeah... I was slow. lol
---------- Post added at 01:36 PM ---------- Previous post was at 01:27 PM ----------
toastedjelly said:
I've used fastboot to flash twrp 2.5 and proceeded to 'Copy log to SD' before attempting to sideload stock rom.
In CMD this error is now returned when using commnd "adb sideload update.zip" :
failed to write data 'protocol fault <no status>
LGNPST method still giving same results. Gets to 85% error (I know this is normal) but when rebooting, boots to nothingness/black screen after quick glimpse of Google logo....
Click to expand...
Click to collapse
2 things:
Are you running as admin in the CMD prompt?
Make sure to use USB 2.0. Not USB 3.0
After LGNPST, press and hold the power button+vol up for 20sec+. Then press power+vol up again and maybe TWRP?
engine95 said:
Glad to hear ZVC almost worked for you.
If you can get into fastboot, you can install a different TWRP. fastboot erase recovery then fastboot flash recovery recovery.img
Or in TWRP flash a different TWRP, octhrope has them all here. http://forum.xda-developers.com/showpost.php?p=47679587&postcount=123
EDIT. Yeah... I was slow. lol
---------- Post added at 01:36 PM ---------- Previous post was at 01:27 PM ----------
2 things:
Are you running as admin in the CMD prompt?
Make sure to use USB 2.0. Not USB 3.0
After LGNPST, press and hold the power button+vol up for 20sec+. Then press power+vol up again and maybe TWRP?
Click to expand...
Click to collapse
A similar thing happened when flashing a stock ZVB rom via lgnpst. This time it hit 85% and rebooted past Googe and hung briefly on the LG logo. It started to boot and ran the "optimizing apps" function. It loaded the OS and a couple seconds later rebooted itself back into the hanging LG logo bit.
In using sideload, I had COMPLETELY forgot to "erase recovery" before flashing a new one. Maybe that was causing the issue? Flashing a recovery over a recovery. Time to try sideload again.....
When it gets back to lg logo and goes no further then turn it off and get back in recovery and do a factory reset
Sent from my LG-LS970 using xda app-developers app
foxsdaddy67 said:
When it gets back to lg logo and goes no further then turn it off and get back in recovery and do a factory reset
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
WOOOOOOO that did it for me! I'm now on stock 4.1.2 LMAO. I used LGNPST to get a stock (rooted) ZVB build onto it. I let it reboot and sit on the LG logo for 10 minutes to err on the side of caution, Then powered down and back into recovery to do a factory reset.
It can make calls and connect to wifi. But no data. Probably just need to flash the zvb radio but again I'm almost scared to turn off/reboot/update anything at this point. Just happy to see the phone back after 2 plus days all jacked up.
Thanks for the help everyone!
toastedjelly said:
WOOOOOOO that did it for me! I'm now on stock 4.1.2 LMAO. I used LGNPST to get a stock (rooted) ZVB build onto it. I let it reboot and sit on the LG logo for 10 minutes to err on the side of caution, Then powered down and back into recovery to do a factory reset.
It can make calls and connect to wifi. But no data. Probably just need to flash the zvb radio but again I'm almost scared to turn off/reboot/update anything at this point. Just happy to see the phone back after 2 plus days all jacked up.
Thanks for the help everyone!
Click to expand...
Click to collapse
Ive had that happen before and it was the only thing that i could find that would work. glad it worked for you
try updating your PRL and Profile now might get data back
foxsdaddy67 said:
Ive had that happen before and it was the only thing that i could find that would work. glad it worked for you
try updating your PRL and Profile now might get data back
Click to expand...
Click to collapse
I managed to do a complete back-up in TWRP of the fully functional 4.1.2 I got up and running. My data (wifi + lte) came back after I eventually flashed the correct radio.
I'm going to maybe stay stock for a couple days. I honestly can't remember the last time I used stock Android on my phone....
Right now I'm attempting to update it to zvc because i'm impatient. Fingers crossed.....
Normally I run stock rooted. Can't beat the battery life on stock. Running asop kit Kat right now
Sent from my LG-LS970 using xda app-developers app
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
MrDelicious said:
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
Click to expand...
Click to collapse
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
Click to expand...
Click to collapse
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
Click to expand...
Click to collapse
Thanks! I shall look into this.
Hi Hope someone can help.
History of what I did.
Im on BPA1
1. Rooted with Kingroot
2. Ran ADB Commands step by step.
3. Booted into Download mode, phone showed Developer
4. Booted into Android phone was fine.
5. Booted back into Download Mode.
6. Flashed TWRP with Odin.
7. Phone went into bootloop would not go past Galaxy note 4 screen.
This went on for an hr so I decided to flash stock BPA1 to try get phone back to original state. It flashed fine in ODIN but its still boot looping and wont go passed Note 4 screen.
Im getting very worried. Can someone help please
gersrt said:
Hi Hope someone can help.
History of what I did.
Im on BPA1
1. Rooted with Kingroot
2. Ran ADB Commands step by step.
3. Booted into Download mode, phone showed Developer
4. Booted into Android phone was fine.
5. Booted back into Download Mode.
6. Flashed TWRP with Odin.
7. Phone went into bootloop would not go past Galaxy note 4 screen.
This went on for an hr so I decided to flash stock BPA1 to try get phone back to original state. It flashed fine in ODIN but its still boot looping and wont go passed Note 4 screen.
Im getting very worried. Can someone help please
Click to expand...
Click to collapse
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
Cheers Mate, I'm sure I've already tried this, I will try again when I get home.
Thanks for your input.
Il let ya know.
felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
First and foremost... THANK YOU!
I've been pulling my hair out for weeks trying to get my phone to boot, but this boot loop has been driving me insane! I've probably flashed 7 different factory ROMs in Odin no less than 5 times each!
And all I had to do was pull my SD card out??
Second:
How did you know that???
Sent from my SM-G900V using XDA-Developers mobile app
Wired4Fun said:
First and foremost... THANK YOU!
I've been pulling my hair out for weeks trying to get my phone to boot, but this boot loop has been driving me insane! I've probably flashed 7 different factory ROMs in Odin no less than 5 times each!
And all I had to do was pull my SD card out??
Second:
How did you know that???
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
It's a common mistake.
Well, thank you again....
Sent from my SM-G900V using XDA-Developers mobile app
Tiny little explanation, When rooting and unlocking your bootloader via ADB, the script wipes your SD card and puts a special code in it to backup your phones original CID. This may be used to unbrick your phone one day. So your NEWLY unlocked phone is using a new CID and your SD card is on the old one. Hence the boot loop. So when reading the OP, I thought the same thing. I didn't seem his say he pulled out his SD card after rooting. Hopefully you guys got it working again.
Lol, Honestly I dint figure it out. I read somewhere in the forums about it. Dont remember exactly who suggested it. But, it worked for me.
Did it work for you?
I have same problem, was on BPA1, unlocked bootloader, flashed twrp, something went wrong had to flash stock again, CPL1 loads up fine but when flashing back to BPA1 runs into bootloop, help.
you rock
felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
you rock mate ... itried this for 2 hrs and all i had to so is take the damn sd out...thanks
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.