Related
Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks
What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.
You didn't unzip them did you?
You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery
I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?
Hi all, I am going to be as thorough as I can. I am rather new, and I'm stuck trying to downgrade my MT4G to froyo (PD15IMG). I have read the tutorials, and learned enough about adb to attempt this task, but I think by doing the HTC Bootloader unlocking update last week, it may be the reason I'm stuck. I follow the instructions on the tutorial, to gain temp root, until I get to the part where I should get a "#" in the command Window when I type "adb shell" but I keep getting "$" instead, although everything seems to be going ok until I get to that point.
*Also, I put the PD15IMG.zip on the root of my sd card, and start my phone in bootloader mode, and it finds the PD15IMG.zip, and a blue progress bar appears in the top right corner of my phone for about 90 seconds, it then displays "parsing PD15IMG.zip" then stops at the hboot screen and does nothing. I just select power down, then power on my phone and nothing will have been done to my phone. I guess what I need to know is, by doing the HTC bootloader unlock update (which I did before I read that it was a bad idea), can I still downgrade and root with normal methods, or will I have to do something different?
Sent from my HTC Glacier using Tapatalk
You can start differently. Since you've unlocked the bootloader, try to flash recovery directly, by downloading recovery image directly from Clockworkmod site, rebooting to FASTBOOT (adb reboot bootloader) and using the command "fastboot flash recovery your_just_downloaded_recovery.img".
If recovery flash doesn't work for you - download the 2.2.1 PD15IMG, unzip it, and flash the following 2 files from it:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
Then reboot. You should end up on 2.2.1, which is perm-rootable using the guide (Visionary for temp-root, gfree for S-OFF, and then perm-root if you want).
Then flash the recovery and the engineering bootloader.
Here is what I did, I am giving a link to pastebin as instructed, it seems to go perfectly until I try to flash the StockRom. In the meantime I will attempt what was just posted above^^^^^^^ http://pastebin.com/fYrC6tAZ
One last thing before i have to throw away my phone. I couldnt leave well enough alone. I did this "fastboot flash boot boot.img" as you stated in the post above. It was successful. I then entered this one "fastboot flash system system.img", and it failed (said the img was too big or something) so I did the "fastboot-windows reboot" command and it is now stuck on the white HTC MyTouch 4g splashscreen. Is my phone toast? My PC no longer recognizes that my phone is connected to the USB port, however I can hold the volume dwn & power button and it comes on in the hboot mode.Is there any hope?
Also, when I boot it up by vol/dwn & pwr, the Hboot screen comes up and finds the PD15IMG that is on my sd card, goes through a 1 minute or so process (a blue status bar loads in top right corner), then it just stays on the hboot. It did that before it stuck on the splash screen, but never actually wrote anything i dont beleive.
OK its letting me use FASTBOOT and here is exactly what I got when i tried to flash the 2nd file in your post above. It came from the PD15IMG.zip as you instructed:
C:\adb>fastboot flash system system.img
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.016s
Can someone please let me know if there is hope for my phone? I can communicate with it through Fastboot (on my PC) and it will boot up in hboot mode. But it WON'T go past the Tmobile/MyTouch splash screen. If I get it fixed, I promise to never touch it again until I study! I truly feel there is hope, but I think don't know enough to figure it out. I loaded the PD15IMG on my SD, and it attempts to flash it, (a blue status bar appears in top right corner and fills up in about 90 seconds), but afterwards, it still sticks on splashscreen. Is there anything I can do to fix it? Anything I can flash it with in Fastboot? Please anyone?
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Jack_R1 said:
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Click to expand...
Click to collapse
Thank for your response. I have tried doing the PD15IMG.zip by booting my phone in bootloader mode. It finds the PD15IMG.zip and then a blue progress bar appears in the top right corner of the phone, finishes in about 90 seconds, the a message appears that says "wrong zip file". I would be happy just to get my phone back on with the gingerbread 2.3.4 on it, and simply leave it alone until I know what Im doing. Is there a way to just flash the original s/w back on it? If so if you could tell me how I will not mess with it again until I study alot more. But flashing the PD15IMG doesnt appear to be working for me.
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Jack_R1 said:
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Click to expand...
Click to collapse
Ok you were right, the one I had the wrong MD5SUM, but i d/l the correct one, it had the correct MD5SUM, but it still gave me the "wrong zip file error". I feel like there is hope, but I cant figure this out!! Thank you for trying, is there anything else I can do? I also tried going into recovery and doing factory reset/ data wipe etc...but it continues to get stuck on the splash screen....
How did you copy the correct one to the phone's SD card, and where did you put it? You either didn't copy it to your SD card, or named it wrong, or put it in wrong location, not overwriting the older file.
In any case, if flashing PD15IMG fails for you:
Download CWM recovery from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-glacier.img
Boot to bootloader.
Enter FASTBOOT.
Execute:
fastboot flash recovery recovery-clockwork-5.0.2.0-glacier.img
Boot to recovery. You should have Clockworkmod.
Download a stock rooted 2.2.1 ROM from Development section.
Flash it in Clockworkmod recovery.
Extract boot.img from this ROM.
Flash it in fastboot, using "fastboot flash boot boot.img".
Boot into the ROM.
Proceed with gfree.
OK!! I got it fixed and it all makes sense to me now! I flashed the 2.2.1 boot.img to my phone, when it still had the 2.3.4 on it. It was as simple as that. I hadnt flashed the downgrade on it when I flashed the boot.img and I guess it was a mismatch. I read your last post to extract the "boot.img" from the rom and then it clicked! Yesterday I wrote the 2.2.1 boot img. to a phone that had 2.3.4...so I found a stock 2.3.4 rom, extracted the boot.img from it a BAM! its rolling again....thank you so much....
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Jack_R1 said:
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Click to expand...
Click to collapse
Well I will soon attempt it again, however I think I need to read a little more so I can understand the concept of what I am doing. I learned a ton by making that mistake. But as soo as I got it fixed, I couldnt resist, I used revovery and flashed [ROM]:: ProjectMIUI 2.2.17 [R6]- UPDATED 2/21/12 - [Stable + Smooth from the DEV section and I have never been happier with my phones performance! I will soon try the cyanmod, but I want to chill with this rom for a week or so. Again, I appreciate your help, I learned alot.
As long as you don't mind flashing kernels separately using fastboot for each ROM you flash, you can go indefinitely and flash ROMs as much as you like with your current setup, not needing anything else. The only good reason for you to go for S-OFF would be to flash Engineering HBOOT, to be able to flash kernels from recovery directly, avoiding extra fastboot step.
Also, thanks for finally confirming that you can flash recovery using fastboot on HTC-Dev-unlocked device. There was one device that didn't allow it (I think Incredible S, but not sure), so it's good to know that on MT4G it works as it should.
I rooted through cyanogenmod method, then unrooted (went back to stock 2.2.1) with the stock P15100.zip. I had another hardware issue with my phone (microphone failing) and thought it could be software. The mic was still broken and I wanted to root again so went through cyanogen method again flashing CWM. I was able to reboot once into recovery to flash synth's ICS. When I try to fully reboot, then reboot into recovery again, I got bootloop for a minute, then eventually booted into the rom. I tried flashing 4ext and same issue. I tried flashing CWM again from app and still have the issue. I'm just guessing recovery is corrupted and it needs to be formatted and re-flashed? Anyone know how to format recovery via adb and then push cwm or 4ext?
Any help much is appreciated.
You can flash a recovery through terminal emulator. As I recall, the commands are:
su
flash_image recovery recoveryname.img
Sounds like you might be having bigger issues, though. I hope your recovery partition isn't going kaput.
Jack_R1 might have an idea.
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Nicgraner said:
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Click to expand...
Click to collapse
I have used adb a bit (for root with cyanogen method). I'm guessing that the delete command will reformat the recovery partition? I'll give this a go when I get home and get back to ya. Thanks for the reply! Is there a way to download the 4ext recovery img file?
Edit:
I downloaded the CWM touch img and connected to the phone in fastboot. Was able to follow your instructions, but the command is erase not delete. When I put in the delete command it came up with the instructions and was able to figure it out. Flashed recovery and I can now boot into recovery every time from fastboot, terminal, adb, and from power prompt in rom! BOOYAH! Thanks a ton!
Jack_R1 said:
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Click to expand...
Click to collapse
Hey Jack,
I have HTC Glacier. Was a typo for the PD15IMG name. I think I have a decent understanding of the phone, and most likely have a corrupted recovery partition. Seems that instead of just flashing a recovery over a recovery, I may need to reformat the partition and then flash? I'll try flashing the file you suggest and report back. If it is not the recovery that is corrupted, what else could be the issue? Possibly an issue with the bootloader not allowing the phone to boot into recovery? Thanks for the reply.
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Jack_R1 said:
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Click to expand...
Click to collapse
Sorry if I wasn't more descriptive. I really appreciate your help and everything you have done for this community. Seems the recovery was corrupted by the 4ext app. I was able to extract the recovery.img from the 4ext download and was able to flash it via fastboot. Everything boots properly now. HBoot is 0.85.2007 FYI. Thanks again!
Hello,
I tried to root my P8 Lite, which is something I've already done on a lot of other smartphones. So I first unlocked my bootloader, then I tried to follow a guide to root it. Everything was going smooth, but when I hit enter for the last time into the command line (at this point of the process, it just installed superSU) my phone rebootd and stucked on the huawei logo. After 20mn I decided it was enough, I unplugged it and hard rebooted it, but still stuck on huawei logo.
Since this, I wasn't able to reboot my phone, nor enter the fastboot/rescue mode. Now I tried on more time to enter the fastboot, and I don't know why but after a few time it showd up !
So basically my phone is now on fastboot mode, unlocked, and I come here to seek answers about the method to flash it and start again with a fresh android. I don't even know where to find the correct rom to flash, nor how to flash, if for instance I should use adb, etc.
If someone here is able to help me, that would be greatly appreciated.
By the way, I manually updated the phone to android 6 and EMUI 4.
Thank you a lot for enlightments.
Hello! Since you are in fastboot mode you can easily fix the issue. Just download a stock rom you wanna flash and use (you can try the new B588) and with the Huawei Update Extractor, extract the boot.img, recovery.img, cust.img, system.img from the UPDATE.APP file. Then flash these in the order i wrote them (using the fastboot command for example:
Code:
fastboot flash boot boot.img
, same thing for all of these just change the file names). That is how i fixed my last 2-3 bootloops. I would suggest looking here first though: https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 on Chapter 4. Hope this helps and good luck
Hi,
Thank you for your answer.
Problem is now, my phone ran out of bttery so not in fastboot mode anymore and I just can't figure out how to go back in fastboot anymore.
I tried to power on the phone while pressing vol up, wait for the huawei logo and wait for ten more seconds, nothing except a black screen. I tried vol down, both vol up and down, still nothing. Thing is, yesterday I don't even know how I managed to enter fastboot, I just tried, didn't work, so I put my phone on the bed, and ten minuts later I realized it was on fastboot mode. Informatics huh.
If you have any idea on how to go back in fastboot mode, I tried using adb, but it needs the phone to reach systm to be able to reboot.
By the way you talked about a specific rom, where can I find this one ?
Thank you again for your time.
EDIT : Ok I managed to reach fastboot, what I did was to plug it on my laptop, powered off, then pressed vol down and power on, and it worked. Informatics has its reasons...
Still interested into the rom ou talked. I'll try to find it on my own though. But if you got a link, I would be happy to download it.
EDIT2 : Ok I tried to flash, everything went good, but my huawei is still in its bootloop. I extracted the B588 rom, but there was way more than 4 img files. I still flashed only the four you and the link you gave me told me, but maybe I need to flash more than these 4 ?
Try this https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 <-- follow the " Bootloop/Softbrick" method if you cannot install the latest firmware directly. You may need to flash original recovery first too. Any recovery version will do they are all the same, find the how too under the "install TWRP" section, but basically it goes "enter fastboot, type fastboot flash recovery recovery.img" while you have recovery.img in the same directory.
[edit]
Also, if you are on MM you should not be using a batch file to root. Once you have TWRP installed, you need to flash 2 zips via TWRP. They can also be found in the mega thread.
yodaofborg said:
Try this https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994 <-- follow the " Bootloop/Softbrick" method if you cannot install the latest firmware directly. You may need to flash original recovery first too. Any recovery version will do they are all the same, find the how too under the "install TWRP" section, but basically it goes "enter fastboot, type fastboot flash recovery recovery.img" while you have recovery.img in the same directory.
[edit]
Also, if you are on MM you should not be using a batch file to root. Once you have TWRP installed, you need to flash 2 zips via TWRP. They can also be found in the mega thread.
Click to expand...
Click to collapse
Single stable SuperSu v2.76 also works for builds less than b580.. For builds greater than that, use 2 zips method
Well, it obviously didn't
---EDIT, FIXED IT ALREADY, MORE INFO BELOW---
Dear members,
A little background; The installation of the latest Oxygen os (zip on storage - > twrp flash) failed.
I thought it was a good idea to wipe everything and reboot to start fresh.
Upon reboot I was unable to enter TWRP, only fastboot was possible.
When I flash twrp (by neither clockworkx or the bluex) the flash is successful but I cant boot into the recovery, also not by directly using fastboot boot recovery.img. When booting into recovery I get a black screen with only a white led.
So I decided to give the stock recovery a try and that one does boot up however I cant flash anything. When I use adb sideload it loads the file fine but then it errors with no error message.
I am getting suspicious that my internal memory is now corrupt so I am willing to give this msmtool a try which I have never touched so I would really appreciate some guidance. Anyone with any ideas? Thanks a lot in advance.
Other things I have tried:
I tried to flash the stock boot.img from the oxygen os using fastboot but it doesnt seem to be the problem.
---FIXED:---
Thanks to the wonderful documentation found at : /oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
I was able to fix it. If you are in the same pickle head over to his thread and thank him.