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?
For example
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
I use the recovery apps to resotre official ROM .... it always reboot halfway .... and enter into emergency mode....
Any help ???
Now I can only use other 3rd party recovery such as Recovery-v0.3.2.8-beta ...and restore Zip files format.....
Have you tried flashing the recovery.img and the corressponding rom image?
You can get these from the wiki
If all else fails, and you cannot recover using fastboot etc, then try QDLTool again from the wiki
(InsertNameHere) said:
Have you tried flashing the recovery.img and the corressponding rom image?
You can get these from the wiki
If all else fails, and you cannot recover using fastboot etc, then try QDLTool again from the wiki
Click to expand...
Click to collapse
Yes I did ......
Ok will try .............
trichard said:
Yes I did ......
Ok will try .............
Click to expand...
Click to collapse
Yes you did WHAT?
Normally installing stock ROM will cure most things unless you have internal issues.
Flash stock recovery.img for the stock ROM you want to get back to... I would suggest 360. You should already have downloaded the stock ROM update.pkg file that corresponds to the stock recovery.img you flashed in fastboot. Make sure you don't have any other files on the root of your SD that conflict with you update.pkg and MOST importantly, make sure it's named "update.pkg"
Boot into recovery and choose option 2 to update. IF it gets stuck (now this first boot after installing stock ROM may take 20 minutes or so), then pull the battery, boot into recovery, and choose to do a factory reset again
Hi guys
I'm hoping somebody could please help me with my somewhat-bricked device..bricked in the sense that I don't know what to do with it. (i'm a noob to this). I've tried installing a custom rom and completely screwed up my dell streak 5.
So the phone doesn't boot anymore and just takes me to the option to install update.pkg off the sd card. I added the file along with recovery.img to the sd card.
360 17397 00 May 31, 2011 PKG Recovery Hash Latest Retail rom
My problem is that I cannot for whatever reason get Flashboot to work in order to flash the recovery.img first. under device manager you see android phone/android adb interface but still can't manage the connection to use cmd prompt/fastboot.
Is there any other way of getting the recovery.img to work without fastboot/thru the sd card. I have no idea what i'm doing anymore. I've tried installing the update.pkg but after installation it just stays on the dell logo loading screen forever.
PLEASE help if you can.
Try QDLTool
cdzo72 said:
Yes you did WHAT?
Normally installing stock ROM will cure most things unless you have internal issues.
Flash stock recovery.img for the stock ROM you want to get back to... I would suggest 360. You should already have downloaded the stock ROM update.pkg file that corresponds to the stock recovery.img you flashed in fastboot. Make sure you don't have any other files on the root of your SD that conflict with you update.pkg and MOST importantly, make sure it's named "update.pkg"
Boot into recovery and choose option 2 to update. IF it gets stuck (now this first boot after installing stock ROM may take 20 minutes or so), then pull the battery, boot into recovery, and choose to do a factory reset again
Click to expand...
Click to collapse
Hi
Yes I did all these step .... take the recovery img and flash using fastboot ... and restore the full ROM image .... still half way .... reboot ... and into recover mode.... and then next rstore will have error ........
(InsertNameHere) said:
Have you tried flashing the recovery.img and the corressponding rom image?
You can get these from the wiki
If all else fails, and you cannot recover using fastboot etc, then try QDLTool again from the wiki
Click to expand...
Click to collapse
How to use Fast boot to restore complete image ROM ?
Command line is ?
trichard said:
How to use Fast boot to restore complete image ROM ?
Command line is ?
Click to expand...
Click to collapse
once in fastboot your command line is
fastboot flash recovery recovery.img (will take just about 3 or 4 seconds then type)
fastboot reboot (it will begin to reboot and you should press the volume up and down keys to get into recovery, you should already have the package on your sd card, choose option 2 to update... if it hangs, you don't have to flash recovery again, just boot into recovery and try a factory reset, if it hangs, well flash the ROM again
cdzo72 said:
once in fastboot your command line is
fastboot flash recovery recovery.img (will take just about 3 or 4 seconds then type)
fastboot reboot (it will begin to reboot and you should press the volume up and down keys to get into recovery, you should already have the package on your sd card, choose option 2 to update... if it hangs, you don't have to flash recovery again, just boot into recovery and try a factory reset, if it hangs, well flash the ROM again
Click to expand...
Click to collapse
No problem to get the recovery.img flash in FastBoot ...
It is getting the 150MB .pkg to install ....
Can FastBoot flash .pkg ?
Camera key don´t work
cdzo72 said:
Yes you did WHAT?
Normally installing stock ROM will cure most things unless you have internal issues.
Flash stock recovery.img for the stock ROM you want to get back to... I would suggest 360. You should already have downloaded the stock ROM update.pkg file that corresponds to the stock recovery.img you flashed in fastboot. Make sure you don't have any other files on the root of your SD that conflict with you update.pkg and MOST importantly, make sure it's named "update.pkg"
Boot into recovery and choose option 2 to update. IF it gets stuck (now this first boot after installing stock ROM may take 20 minutes or so), then pull the battery, boot into recovery, and choose to do a factory reset again
Click to expand...
Click to collapse
hey buddy, when I enter the recovey mode, and will install a new rom or another option, the camera button does not work. What can I do?
Hello folks,
To start, the tablet is an a500. It's running the ICS bootloader V8 with Thor's 1.7.3 recovery.
On my Nexus S, I was able to mount the device as USB mass storage from the recovery, drop a new rom on it from the computer and flash as usual. I can't do that with the a500 because it gives me the "Unable to write to ums lunfile" error. Thinking back, the recovery has always given me this error, but I've gotten around it by successfully mounting it from the booted tablet instead of from the recovery - I can't do that this time because booting hangs on the Tegra Owners screen and doesn't continue any further.
Things I'm wondering about
-Am I on the right recovery for the V8 bootloader? this indicates that I should switch to this
-Can someone point me to how to properly flash recoveries/roms via adb/fastboot?
-What can I do to be able to mount the a500 through the recovery?
I've tried to do some more research and I think my data might be pooched again. A few posts mentioned that formatting the data enabled them to mount their tablet as a USB device to load roms onto it. When I was still running the HC bootloader, I was able to successfully format the data using the hardware reset (power, volume+, screen lock). I'm trying to do that again, but it just boots straight into the V8 bootloader.
1) rotate lock set to the locked position
2) hold volume+
3) hold power until tablet vibrates, then release power and switch the rotate lock to the unlocked position
... but instead of giving the Formatting Data text, it boots straight into the bootloader menu. BLAST!
Wermut said:
Hello folks,
To start, the tablet is an a500. It's running the ICS bootloader V8 with Thor's 1.7.3 recovery.
On my Nexus S, I was able to mount the device as USB mass storage from the recovery, drop a new rom on it from the computer and flash as usual. I can't do that with the a500 because it gives me the "Unable to write to ums lunfile" error. Thinking back, the recovery has always given me this error, but I've gotten around it by successfully mounting it from the booted tablet instead of from the recovery - I can't do that this time because booting hangs on the Tegra Owners screen and doesn't continue any further.
Things I'm wondering about
-Am I on the right recovery for the V8 bootloader? this indicates that I should switch to this
-Can someone point me to how to properly flash recoveries/roms via adb/fastboot?
-What can I do to be able to mount the a500 through the recovery?
I've tried to do some more research and I think my data might be pooched again. A few posts mentioned that formatting the data enabled them to mount their tablet as a USB device to load roms onto it. When I was still running the HC bootloader, I was able to successfully format the data using the hardware reset (power, volume+, screen lock). I'm trying to do that again, but it just boots straight into the V8 bootloader.
1) rotate lock set to the locked position
2) hold volume+
3) hold power until tablet vibrates, then release power and switch the rotate lock to the unlocked position
... but instead of giving the Formatting Data text, it boots straight into the bootloader menu. BLAST!
Click to expand...
Click to collapse
Hard reset will not work this way on v8, u need to use fastboot...
Boot to fastboot pwr/vol UP
Connect to pc via micro USB cable
Open cmd prompt type:
fastboot devices
U should see a ?
Type:
fastboot erase userdata
fastboot erase cache
fastboot reboot
It might pay to reflash your recovery while you're there
Grab your chosen recovery
(I used cwm1.7.3 that came in civatos nvflash v8 pckge and renamed it recovery.img)
and copy it to the fastboot folder
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot reboot
Yes, v8/cwm 1.7.3 should work fine, not sure why u have errors mounting....someone else maybe able to help with that...
good luck
dibb
Sent from my A500 using Tapatalk 2
This is a super helpful post. Many thanks!
I'll try this in the next couple of days and report back.
Hello Dibb, thanks again for trying to help.
Using fastboot, I successfully:
-erased user data
-erased cache
-erased recovery
-reflashed the 1.7.3 recovery.
I didn't have any luck mounting the tablet in windows, so I tried the above steps again, but this time flashing the TWRP 2.1.3.
The recovery booted OK, so I know I did that correctly, but still no luck mounting.
Next, I tried redoing the bootloader/recovery using Blackthund3r's A500 APX Flashing utility back to the Bundle 17 (A500 and A501 BL v8 / Thor Recovery 1.7.3, ICS Unlocked / Skrilax Bootloader v8 and Thor Recovery 1.7.3 for the A500 and A501) to maybe get a fresh start. I rebooted into the recovery, but still no luck mounting the tablet.
I think I need to try pushing a rom straight onto the tablet using either fastboot or adb, but I'm not sure how to do it. I did some research and came up with the following cmd code:
fastboot flash boot boot.img
All of the roms that I've ever downloaded come in zips that you flash straight from the recovery, they're not .img files. Is there a way to push zips onto the SD card using adb/fastboot? I see a boot.img inside these zips, but I feel that if I flash that after extracting it from the rom zip, I'm not going to be getting any gapps or any of the other potentially important stuff in that zip. Do you mind explaining that, and maybe including some more awesome instructions on how to push a rom onto the tablet from windows, without having to mount the SD?
Thanks in advance!
K, lets back up a bit.....a quick question first
Are u just wanting to flash a custom rom via recovery?
As long as you have the unlocked bootloader (which you do) just flash via "install from zip" option from either
internal or external storage.....or am I missing something?
Sent from my A500 using Tapatalk 2
Yep, that`s exactly what I want to do.
My problem is that there's nothing on the internal disk (I have no SD card for the a500) and I can't put anything on the SD card because it won't mount to show up in windows for me to drag a zip onto it.
Roger that then
And no card reader either I take it?
Edit: what rom are u running right now
That's right, no card reader either. I do have a USB key, maybe I can put a new rom on that and mount the usb key in recovery?
I'm not sure what rom I'm on right now, it's been so long since the tablet successfully booted into a rom. The last one I think was Thor's JB v17 from tegraowners.
Yeh try the USB key first....
I didn't realise you couldn't boot your OS, thought you meant the recovery screen, no matter...
do you have your cpuid backed up somewhere....anywhere....pleeeaasssee say you do!!!
I'm just writing up a post now in case the USB key won't work...
Yep, I've got the CPUID, drivers, sdk, adb and fastboot work too.
I'm going to try the USB key method.
Wermut said:
Yep, I've got the CPUID, drivers, sdk, adb and fastboot work too.
I'm going to try the USB key method.
Click to expand...
Click to collapse
Awsum that's great:highfive::good:
adb push name-of-your-rom.zip /sdcard
I'm sure you will still need to mount it tho but this is not my speciality.....
If the key won't mount I'd strongly suggest you download timmydeans v4 - it does not require an sdcard. http://www.mediafire.com/download.php?fo4wqjeald4s3rj
This will downgrade you back to stock HC3.2.1 which is pre-rooted and comes with cwm....this will wipe everything and reset yr tab, that will deal with yr boot issue - and hopefully the mount issues too....
Holy**** the USB key worked, just installed CM10-FLEX_V6Supercharged_Rev2.3c.
Lets hope I don't have any SOD issues, which is what led me to upgrading my bootloader, which is what started all of this!
I searched the rom that you have in your sig, (I suppose you think it's pretty stable?), but I didn't manage to find it. Throw a link? Does it come with a kernel?
Thanks so much!!
Phew!!
Ive been using the v6 supercharge cm10 JB rom for a week or so and its fantastic http://forum.xda-developers.com/showthread.php?t=1935582
The one in my sig is ics but u know us tinkerers we have to have the latest and greatest.lol...
I never go too far from civato's roms - I'm a big fan! So can't offer feedback for anything else....
You should have no probs with SOD...mainly an issue with hc bootloader/ics rom and not wiping....thing of the past these days!
Well I'm pleased you got sorted without too many probs - happy tabbing
rgds dibb
Sent from my A500 using Tapatalk 2
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!
So it had been a while since I had tried getting into recovery twrp but I figured I could remember how so I did
fastboot flash boot twrp etc.img
This was a mistake according to the site here > https://twrp.me/nokia/nokia6_1.html
WARNING: If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Click to expand...
Click to collapse
Which is exactly what I did
So now my phone is either stuck on the Nokia logo, or I can load twrp.
They provide some info on fixing it but I'm not sure I understand what they are saying. Can anyone help with this?
The phone was running Oreo (not sure which version unfortunately) and it was fully rooted and running magisk/xposed/su just fine before my mistake.
I don't have access to fastboot. Only Twrp and adb commands.
Edit, I can get to fastboot/download mode through the twrp terminal.
[SOLVED]
So I was able to use twrp to copy all of my internal files onto an sd card.
Then I set about getting this tool here > https://github.com/RaghuVarma331/Nokia-Tool the firmware specific to my phone, and modifying the bat file found here > https://github.com/RaghuVarma331/Nokia-Tool/blob/master/batscripts/Nokia-Tool-DRG-B2N-PL2-CTL.bat (because windows for some reason gave me a 16 bit application warning when I tried to use the tool exe)
My phone flashed a bunch of time and I was able to load up an almost entirely stock android 10, still capable of using magisk, edxposed, etc.
And now all there is to do is to get everything back onto it and set up which is at this point, the best case scenario.