Database Develop

[Q] Unable to flash recovery - error

I am trying to flash twrp through fastboot, but am not having any luck. Here is what I've done so far:
Flashed cm10.1. This flashed fine using nvflash, it also booted fine...could not, however,boot to fastboot or recovery at all. Using nvflash I restored to stock using images p2-p14 in another thread. After flashing I rebooted into a bootloop. Powered it off and booted into recovery and did factory reset, then rebooted. Now currently back on stock 2.2.2 boots fine. I then hopped into fastboot and attempted to flash twrp using "fastboot flash recovery recoveryname.img" This is where I'm recieving the following error:
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas on what has happened here?
Thanks
devx

devastatorx said:
I am trying to flash twrp through fastboot, but am not having any luck. Here is what I've done so far:
Flashed cm10.1. This flashed fine using nvflash, it also booted fine...could not, however,boot to fastboot or recovery at all. Using nvflash I restored to stock using images p2-p14 in another thread. After flashing I rebooted into a bootloop. Powered it off and booted into recovery and did factory reset, then rebooted. Now currently back on stock 2.2.2 boots fine. I then hopped into fastboot and attempted to flash twrp using "fastboot flash recovery recoveryname.img" This is where I'm recieving the following error:
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas on what has happened here?
Thanks
devx
Click to expand...
Click to collapse
Why are you flashing TWRP? As there is no version for Android 2.2 available. Android 2.2. has a different layout than any TWRP setup I have created.

giveen said:
Why are you flashing TWRP? As there is no version for Android 2.2 available. Android 2.2. has a different layout than any TWRP setup I have created.
Click to expand...
Click to collapse
I've now got it on Honeycomb, and booting into fastboot to flash recovery presents an identical error
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas?
Update: I figured I'd try booting from the image file rather than try to flash just to see, oddly enough this works using: fastboot boot recoveryname.img. Now if I could get it to flash...

Again, I will ask you.
Why are you flashing a recovery on stock Android 2.2¿
Sent from my Nexus 7 using Tapatalk 2

giveen said:
Again, I will ask you.
Why are you flashing a recovery on stock Android 2.2¿
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm don't intend to be condescending, but I clearly state in my last post that I had since successfully flashed Honeycomb and was no longer working with 2.2. Since then I have attempted to flash both cwm and twrp with no success. I am able to boot either of them from fastboot and have flashed ics-b5 cm9 which is what I am currently running. So I'm working around by booting the image from fastboot rather than flashing. I'm curious as to why it is throwing the error and what the error means exactly.

Okay, where did you get the copy of fastboot.
And I don't mean to be condescending but i made the twrp port. I know exactly what it needs.
Sent from my Nexus 7 using Tapatalk 2

giveen said:
Okay, where did you get the copy of fastboot.
And I don't mean to be condescending but i made the twrp port. I know exactly what it needs.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using fastboot from the android sdk

devastatorx said:
I'm using fastboot from the android sdk
Click to expand...
Click to collapse
If you got it from the SDK, thats your problem.
Recently in the Android 4.2.2 update Google decieded to add ADB signing. This required an update to the ADB and fastboot program. This resulted in total breaking of our devices ability to flash with the updated program. I am still researching a work around.
Please go to the Streak 7 Android Development section, and at the top of the forum is a link to drivers. In that pack of drivers is a copy of ADB/Fastboot that will work.

giveen said:
If you got it from the SDK, thats your problem.
Recently in the Android 4.2.2 update Google decieded to add ADB signing. This required an update to the ADB and fastboot program. This resulted in total breaking of our devices ability to flash with the updated program. I am still researching a work around.
Please go to the Streak 7 Android Development section, and at the top of the forum is a link to drivers. In that pack of drivers is a copy of ADB/Fastboot that will work.
Click to expand...
Click to collapse
I'll give that a go, thanks giveen.

error getvarartition-type:userdata user(0x2)
Hi !
My DS7 dosn´t boot.
I did a master reset, factory reset (User data only), factory reset (user data and Internal tablet storage), but the table didn`t boot.
I download the fastboot + driver from http://forum.xda-developers.com/showthread.php?t=1484406, but when I run the command "fastboot -w", it doesn´t work.
Please help me!
Thanks!

santi1928 said:
Hi !
My DS7 dosn´t boot.
I did a master reset, factory reset (User data only), factory reset (user data and Internal tablet storage), but the table didn`t boot.
I download the fastboot + driver from http://forum.xda-developers.com/showthread.php?t=1484406, but when I run the command "fastboot -w", it doesn´t work.
Please help me!
Thanks!
Click to expand...
Click to collapse
1. Start your own thread, don't hijack others
2. Need more info , as in logs, more description on what happens when you press power, charge status, did you install the drivers after downloading them, did you put the device in fastboot mode, what color of underwear are you wearing etc etc etc

****deleted*****

[Q] I am stuck on CryanogenMod startup screen

i rooted my htc vivid yesterday and i wanted to get a custom rom do i downloaded it and flashed it on my phone but when i rebooted my phone all that comes up is the cyanogenmod startup screen with the spinning circle and nothing else happens i deleted my recovery by mistake and now im stuck like this can anybody help?

tpaina380 said:
i rooted my htc vivid yesterday and i wanted to get a custom rom do i downloaded it and flashed it on my phone but when i rebooted my phone all that comes up is the cyanogenmod startup screen with the spinning circle and nothing else happens i deleted my recovery by mistake and now im stuck like this can anybody help?
Click to expand...
Click to collapse
Have you wiped data and both cache as well..??
Also have your flashed latest Gapps..?

i need to correst apps
i was hoping to flash it back to the stock Rogers [ICS] 4.0.3 ruu do you know where i can get that ruu?

Yes
Yes ive done that and it still shows the cyanogenmod screen when i start up the phone it wont load past that

If its your first time installing... you need to wipe data as well
Sent from my Vivid 4G using Tapatalk 2

Did you fastboot flash the boot.img
Sent from my HTC PH39100 using xda app-developers app

No
i dont know where the boot.img is

tpaina380 said:
i dont know where the boot.img is
Click to expand...
Click to collapse
It's in the Rom zip, assuming your not s-off it must be flashed separately
You can check if your s-off by going to hboot, toward the top it will say s-off or s-on...which basically means security off/on - its another level of security HTC added on above the bootloader
Sent from my HTC PH39100 using Tapatalk 2

It says s-on
so what do i do from here?

Put your boot.img into the folder which your fastboot and adb are and then open a terminal to the folder. Then put your phone into fastboot by entering the bootloader. Then type fastboot devices to see if your device is connected to the computer. If it comes up with your serial number continue if not try again. Then type fastboot flash boot.img and then go to recovery and reflash the rom.
---------- Post added at 11:13 AM ---------- Previous post was at 11:10 AM ----------
If you need help with a better guide try
http://forum.xda-developers.com/showthread.php?t=1416836
and read the flash custom kernel/recovery the third option

Didnt work
all is says is
C:\Fastboot Command Folder>fastboot devices
MB201VJ21706 fastboot
C:\Fastboot Command Folder>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'

I worked!!!!!!!!!!! DDDDDD
When i typed in "fastboot flash boot.img" it didn't work so i tried "fastboot flash boot boot.img" and it worked i flashed cm-10 afterwards and then i flashed the ics gapps and it loaded up my holiday is now running android 4.1.2 and it is awsome!!!!!!!!!!!!!!!!!!!!! thank you for the help much appreciated

You figured out what you where doing wrong before i could tell you. Well done glad to help.

tpaina380 said:
i rooted my htc vivid yesterday and i wanted to get a custom rom do i downloaded it and flashed it on my phone but when i rebooted my phone all that comes up is the cyanogenmod startup screen with the spinning circle and nothing else happens i deleted my recovery by mistake and now im stuck like this can anybody help?
Click to expand...
Click to collapse
yea bro i had the same issue. first thing redownload the cm10 rom. sometimes you can get a bad dl. second you have to take the boot.img and flash it using fastboot. once you do that perform the wipes. then immediantly flash the cm10 rom from recovery. that should work. if you deleted the recovery witch is hard to do lol. u will have to use odin. hope i help

Bigc13 said:
yea bro i had the same issue. first thing redownload the cm10 rom. sometimes you can get a bad dl. second you have to take the boot.img and flash it using fastboot. once you do that perform the wipes. then immediantly flash the cm10 rom from recovery. that should work. if you deleted the recovery witch is hard to do lol. u will have to use odin. hope i help
Click to expand...
Click to collapse
No no... bad advice... ODIN is for Samsung...
Sent from my Vivid 4G using Tapatalk 4 Beta

Download either TWRP or WCX recovery. As long as your phone can get to the bootloader, you can get into Fastboot and flash the recovery again. Make sure the recovery is in the same folder where you have the adb.exe and fastboot.exe. Open up a command prompt, then change directory to where your fastboot and adb are. Type in fastboot flash recovery "recovery".img where "recovery" would be the name of the recovery file you download. This will flash pretty quickly. Once you get to that point, you probably are S-On so you need to make sure to extract the boot.img from the ROM you downloaded. Use either winrar or 7zip to extract the boot.img to the same location where you have the fastboot.exe and adb.exe. Then go to the command prompt again and change directories to the same folder where you have fastboot and adb. Type in fastboot flash boot boot.img. I usually would run this 3 times to make sure it loads properly. Once that is done reboot the phone again.

Sorry I used it on the HTC evolution 4g and it worked so I figured it would work for vivid
Sent from my Vivid 4G using xda app-developers app

Bigc13 said:
Sorry I used it on the HTC evolution 4g and it worked so I figured it would work for vivid
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
?
How...
I've never heard of using ODIN on anything other than Samsung?
Anyone else?
Sent from my Vivid 4G using Tapatalk 4 Beta

Man I used a jig to put in dl mode to flash a file I can't remember exactly it was a couple years ago lol but sorry I shouldn't have said nt

rignfool said:
?
How...
I've never heard of using ODIN on anything other than Samsung?
Anyone else?
Sent from my Vivid 4G using Tapatalk 4 Beta
Click to expand...
Click to collapse
That would be a no for me as well... but these Springdale-ians... never know what they will come up with. JK.

[Q] Trying to downgrade

Firstly, thanks to SafinWasi and Red_81 who both helped me on other threads, this question follows on from those threads.
I'm trying to downgrade from 7.4.9 user 4952320. Eventually, I will probably install CM11 (I tried once and bricked my device), but for now I just want to downgrade the OS and be able to change the wallpaper, I'm sick of the black paper. (I've tried Stunts wallpaper fix and it didn't work)
When the device upgraded to 7.4.9 I made backups of the whole 12 img files (inc boot0block).
I've read that you need a 7.2.3 boot image to be able to install TWRP as part of the CM11. I obtained a rooted 7.2.3 boot image from Red_81s google drive. I then flashed that boot image and tried rebooting the device. No joy. I got the red triangle. I flashed my 7.4.9 boot image and rebooted. The device rebooted and worked as normal.
I then flashed the 7.2.3 rooted system image and rebooted. Again I got the red triangle. I then flashed the 7.2.3 boot image, (so the device had 7.2.3 system and boot images) but again I got the red triangle.
So, how do you downgrade? Should I have flashed all 3 of the 7.2.3 images? (I don't have the checksums of the images so I recognise if one of the images was corrupted the exercise was doomed to failure.)
By flashing my 7.4.9 system and boot images, my device was restored to functionality, and I learned a bit, but not enough to achieve the goal. I'm hoping someone can show me how to downgrade.

Thought I'd add that I did try Kindle Fire First Aide but got lots of errors about dropbox not being available.

Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app

cecr said:
.
Click to expand...
Click to collapse
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app

Red_81 said:
Did you flash the system and recovery? Both are needed to successfully downgrade. I always wipe data too.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't flash recovery, at my first attempt, just boot, then I tried boot & system. Both tries gave the red triangle.
I've tried again, with all 3 rooted images from your gdrive - recovery, boot & system, and again got the red triangle. I tried again with the 3 images from another source (my own unrooted 7.2.3 backup when I first got the HD7) and again, got the red triangle.
I haven't wiped the data because I would prefer to keep it so I can use the device (and think it should be possible to downgrade without wiping). I haven't been able to find a command to wipe just the cache...
So I'm more than a bit puzzled. The fastboot commands (eg fastboot -i 0x1949 flash boot boot.img) all return with "sending" then "OKAY", then "writing", then "OKAY" so I don't think there's any problem there.
I must be doing something wrong or missing something.

LinearEquation said:
You need to flash a custom recovery on a second bootloader as well. You can't just flash the system. You also need to flash the 7.2.3 boot.img and stack override. Any tutorial dealing with this mod will include all the steps. It important to pay attention to details and not skip any steps. http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Nexus 7 Flo running Paranoid Android 4.4.3 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your response, but at this stage I don't want to flash a new custom ROM, that may (probably will) come later, but at this stage I want to just downgrade. I've been warned that installing TWRP etc may leave the stock system in a bootloop, so a working stock backup won't be possible.
As I have to downgrade the stock boot image anyway in order to install a custom ROM, I thought I'd downgrade the whole OS in order to have a functioning stock system, then I can make a backup of it in TWRP, then install a custom ROM.
If I'm having problems with a simple downgrade, I might have more severe problems flashing a new ROM and be left with a dead device like I was previously, hence my caution and not wanting to move on until I know I can recover to the previous step if things go wrong.

Did you try downloading the original 7.2.3 from the thread and try flashing them ?

Red_81 said:
Did you try downloading the original 7.2.3 from the thread and try flashing them ?
Click to expand...
Click to collapse
Yes, I did. Tried them twice, in a different order (didn't think it would make a difference but you never know....). Anyway, tried again, this time, wiped data and cache (took 45 mins) and it worked! I now have 7.2.3 and access to Gplay (was already there).
I haven't registered it to my Amazon account yet, so email and contacts don't work, and am wondering if I should go straight to installing a custom ROM. I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
It's been a bit of a task getting this far, but at least I'm more confident about getting into ADB and Fastboot!

cecr said:
I'm thinking if it isn't registered to Amazon, then they can't update it via OTA...... or can they?
Click to expand...
Click to collapse
well, I know the answer, yes, even though it hasn't logged into an Amazon account (I realise they pre-register them to your account before dispatch), it updated back to 7.4.9 just as I finished the above post and whilst I was thinking I should disable OTA updates using KFFA!
flip. This is turning into hard work. lol, still I know how to do it now.

I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.

greg2074 said:
I was having many issues after the last OTA and got mine to cm-11-20140609-SNAPSHOT-M7 last night. Mine was at 7.4.9 also. I followed rootjunky youtube videos to get mine re-rooted, flashed and working. After getting it rooted, he uses Fire Flash app to put twrp on the Kindle. I deviated a little and put the twrp 2.7.0.0 version other than that, I followed to a T. Once I got all that done, I went on the internet to Hashcode's repository and downloaded the newest cm-11 UNOFFICIAL he had listed directly to the device. I downloaded the latest Gapps from cyanogenmod and then booted into recovery(twrp) and installed. Everything is working beautifully now. Everything seems faster and smoother so far. I did go ahead and do an update from the about area in the settings to cm-11-20140609-SNAPSHOT-M7. I was also able to get all my books that I had purchased through kindle in the kindle reader.
Click to expand...
Click to collapse
Nice to know. Think I'll be doing something very similar, now I've made backups of 7.4.9 "just in case". Just have to go through all the above again!

(SOLVED) TWRP won't stick after flashing 5.1

Flashed 5.1 OTA last night.
This morning, trying to reinstall TWRP.
Command prompt screen on PC, did usual "fastboot flash recovery openrecovery-twrp-2.8.5.0-shamu.img"
Appears to execute properly.
Reboot device. Then when booting to recovery, it's still stock recovery.
Any suggestions welcome.

Flash twrp, go into recovery then root. It will stick after.
Sent from my Nexus 6 using Tapatalk

david279 said:
Flash twrp, go into recovery then root. It will stick after.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks, but after flashing twrp, when I boot to recovery, it's stock recovery. I can not flash SuperSU from stock recovery.

Don't reboot after you flash it Go straight into recovery from the bootloader. When you reboot it wipes the recovery and replaces it with stock.
Sent from my Nexus 6 using Tapatalk

david279 said:
Don't reboot after you flash it Go straight into recovery from the bootloader. When you reboot it wipes the recovery and replaces it with stock.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thank you kind sir! I learned something today, and that's always a good way to start the day.
I'm glad that it was "user error" and not something with 5.1.

Hit the thanks button
Sent from my Nexus 6 using Tapatalk

david279 said:
Hit the thanks button
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I will later. I've exceeded my quota already today.

david279 said:
Don't reboot after you flash it Go straight into recovery from the bootloader. When you reboot it wipes the recovery and replaces it with stock.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks for this! I've looked through a bunch of guides and for some reason all of them just say to reboot after flashing twrp.

Not sticking n my shamu running 7.0
Edit: sorted with different root zip

jimbomodder said:
Not sticking n my shamu running 7.0
Click to expand...
Click to collapse
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP.
https://twrp.me/devices/motorolanexus6.html

Nexus 6 stuck on bootup

My nexus 6 is soft bricked I'm assuming, I can't get past the 6.0.1 boot up screen it just keeps on booting . The device is unlocked with TWRP recovery but not rooted as far as I know it's not rooted. The only way I can check MTP is through twrp but it's showing an exclmation point in device mgr. I'm in wugs toolkit now under Advanced Utilities, before I got the boot logo it had the you're device is corrupt. I fixed the corrupt message by putting my device in boot loader mode and in Advanced Utilities under fastboot flash then I clicked Boot [Kernel] I flashed the stock kernel and that got rid of the corrupt device warning screen. I'm gonna try flashing a modified boot img next but I'm having trouble. I just need someone to stick with me for awhile and help me fix this thing because I gotta return it and I don't have long.
Sent from my HTC6600LVW using Tapatalk

Ok now I have the corrupt device message back again.
Sent from my HTC6600LVW using Tapatalk

mwebb34 said:
My nexus 6 is soft bricked I'm assuming, I can't get past the 6.0.1 boot up screen it just keeps on booting . The device is unlocked with TWRP recovery but not rooted as far as I know it's not rooted. The only way I can check MTP is through twrp but it's showing an exclmation point in device mgr. I'm in wugs toolkit now under Advanced Utilities, before I got the boot logo it had the you're device is corrupt. I fixed the corrupt message by putting my device in boot loader mode and in Advanced Utilities under fastboot flash then I clicked Boot [Kernel] I flashed the stock kernel and that got rid of the corrupt device warning screen. I'm gonna try flashing a modified boot img next but I'm having trouble. I just need someone to stick with me for awhile and help me fix this thing because I gotta return it and I don't have long.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
If TWRP is installed there's no problem. Just a matter of the pc let recognize the device. Quit the toolkits though!
Do you have google drivers installed? Once they are installed your device should be recognized and you can copy any of the fine roms that can be found here.

Droidphilev said:
If TWRP is installed there's no problem. Just a matter of the pc let recognize the device. Quit the toolkits though!
Do you have google drivers installed? Once they are installed your device should be recognized and you can copy any of the fine roms that can be found here.
Click to expand...
Click to collapse
I need a lot of help installing the drivers.
Sent from my HTC6600LVW using Tapatalk

Like I said I now have the corrupt device message back instead of the 6.0.1 boot logo. I tried flashing the stock img file and the stupid corrupt screen came back. Ok I'm just craps out luck I guess,
Sent from my HTC6600LVW using Tapatalk

Ok I have what says is the latest Google usb drivers which was Aug 2015 downloaded. On my device I'm using I'm gonna transfers the drivers to my pc now, and attempt to install them. I hope this works and fixes my device. I sat in front of my pc yesterday for 7 hrs trying to fix this stupid phone.
Sent from my HTC6600LVW using Tapatalk

the corrupt device message is only there because you have twrp and a stock kernel. flash a custom kernel.

It's fixed, everything is running as it should no boot loops or corrupt screen, now I gotta check to see if recovery is gone. I used wugs to flash stock 6.0.1
Sent from my HTC6600LVW using Tapatalk

I used to have the corrupt message also, but it would go away and boot just fine. Started when I had TWRP. As someone mentioned, if this is a really annoyance, just flash a custom kernel . Though mine went away when I rooted with SuperSU (which patches the kernel I think)

Tower1972 said:
I used to have the corrupt message also, but it would go away and boot just fine. Started when I had TWRP. As someone mentioned, if this is a really annoyance, just flash a custom kernel . Though mine went away when I rooted with SuperSU (which patches the kernel I think)
Click to expand...
Click to collapse
I used wugs toolkit to flash back to complete stock it worked my device is running as normal, but when I power of the device and power it back on the corrupt message then disappears and boots right up. When I boot into boot loader mode and boot recovery it shows the green android robot laying down. After I flashed back to stock 6.0.1 it got rid of twrp and root but I'm still unlocked . The unlocked part I'm not worried about. In order to fix this do I have to 're root and flash twrp all over again or is there an easier way. I need step by step, on how to get rid of the corrupt message. Example, like when someone says flash img to me that's about as clear as mud.....
Sent from my HTC6600LVW using Tapatalk

mwebb34 said:
I used wugs toolkit to flash back to complete stock it worked my device is running as normal, but when I power of the device and power it back on the corrupt message then disappears and boots right up. When I boot into boot loader mode and boot recovery it shows the green android robot laying down. After I flashed back to stock 6.0.1 it got rid of twrp and root but I'm still unlocked . The unlocked part I'm not worried about. In order to fix this do I have to 're root and flash twrp all over again or is there an easier way. I need step by step, on how to get rid of the corrupt message. Example, like when someone says flash img to me that's about as clear as mud.....
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
flash twrp then when you root, flash a custom kernel as well, that will get rid of the message.

Anybody here?
Sent from my HTC6600LVW using Tapatalk

mwebb34 said:
Anybody here?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
me. well not here, but in nyc. here in spirit though

simms22 said:
me. well not here, but in nyc. here in spirit though
Click to expand...
Click to collapse
I'm trying to get my brain working,lol my device is stock unrooted without twrp but the corrupt message still shows up I gotta get this fixxed. It's hard for me to understand what all I need to do. All I need is the corrupt message to go away and I'll be good. At start up it shows the corrupt message, but a few seconds later it goes away and it boots up normally.
Sent from my HTC6600LVW using Tapatalk

mwebb34 said:
I'm trying to get my brain working,lol my device is stock unrooted without twrp but the corrupt message still shows up I gotta get this fixxed. It's hard for me to understand what all I need to do. All I need is the corrupt message to go away and I'll be good. At start up it shows the corrupt message, but a few seconds later it goes away and it boots up normally.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
i believe that your bootloader is unlocked, thats why its showing up on a non rooted n6. you can lock your bootloader(i wouldnt, you can have problems later) or you can flash twrp recovery, then a custom kernel, and you dont need to root it for that.

simms22 said:
i believe that your bootloader is unlocked, thats why its showing up on a non rooted n6. you can lock your bootloader(i wouldnt, you can have problems later) or you can flash twrp recovery, then a custom kernel, and you dont need to root it for that.
Click to expand...
Click to collapse
If I flash the kernel with twrp it's gotta be a zip? Is there anyway that you can link me to stock 6.0.1 kernel
Sent from my HTC6600LVW using Tapatalk

mwebb34 said:
If I flash the kernel with twrp it's gotta be a zip? Is there anyway that you can link me to stock 6.0.1 kernel
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
a stock twrp flashable, then theres no zip version of it available. BUT twrp can also flash .img kernels as well. if you have the factory image available, you can unzip it and just flash the boot.img in twrp(or fastboot). but why the stock kernel?? if you just want stock, id recommend just fastboot flashing the boot.img from the factory image. boot.img is the kernel.

simms22 said:
a stock twrp flashable, then theres no zip version of it available. BUT twrp can also flash .img kernels as well. if you have the factory image available, you can unzip it and just flash the boot.img in twrp(or fastboot). but why the stock kernel?? if you just want stock, id recommend just fastboot flashing the boot.img from the factory image. boot.img is the kernel.
Click to expand...
Click to collapse
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk

mwebb34 said:
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
nope. the kernel is what connects the operating system(software) to the hardware and also serves as the devices main "brain"
---------- Post added at 05:10 PM ---------- Previous post was at 05:08 PM ----------
mwebb34 said:
I'm gonna try to find it. My device wouldn't boot at all if I didn't have a kernel would it?
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
just download the factory image, then grab the boot.img out of it. link to the 6.0.1 factory image https://dl.google.com/dl/android/aosp/shamu-mmb29k-factory-9a76896b.tgz

simms22 said:
nope. the kernel is what connects the operating system(software) to the hardware and also serves as the devices main "brain"
Click to expand...
Click to collapse
Ok, with no twrp recover when I boot into boot loader mode and then boot into recovery mode what should I see come up on the screen?
Sent from my HTC6600LVW using Tapatalk