Database Develop

[Help] White screen

Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?

Killa_vatt said:
Hi there.
So I wanted to install cyanogenmod on my htc incredible s. So i rooted my phone without big problems. Then I tried to install cyanogenmod through 4ext recovery via zip file. And now all I have is a static white screen. I tried over 10 ruu's that supposed to be installed from pc and phone. I tried another recovery, custom OS, hard reset through recovery and bootloader, goldcard and some other things that I cant even remember. I also tried to lock bootloader, unlock it, reset root etc.
android version before brick was 4.0.4, sense 3.6.
vivo s-on
hboot 2.02.0002
radio 3831.18.00.11_M
Also when i install cm or some other custom OS through 4ext zip install it says OK but when i reload nothing changes.
Help?
Click to expand...
Click to collapse
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.

tpbklake said:
With an unlocked bootloader 2.02.0002, you need to extract the boot.img from the CM ROM's zip.file and manually flash it in FASTBOOT USB mode.
You cannot simply flash a custom ROM from 4EXT recovery when you only have an unlocked bootloader. There are plenty of sticky threads in this forum that document the procedure you need to follow. You need to read, study and understand before you try modding your phone.
Click to expand...
Click to collapse
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\

Killa_vatt said:
Still stuck at HTC boot screen. Maybe bad cm file?
I readed many guides on tons of sites but all of them says different things =\
Click to expand...
Click to collapse
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???

prunzzz said:
if the cm.zip is bad; recovery itself tells BAD ZIP
BTW why dont you flash another rom??
there are much better roms than CM!!
try it!!
so that we will know whether the problem is in phone or rom that you are flashing???
Click to expand...
Click to collapse
I have already tried many ways to install many other roms. What will you recommend?

Killa_vatt said:
I have already tried many ways to install many other roms. What will you recommend?
Click to expand...
Click to collapse
what kind of errors did you get when you flashed other roms??

prunzzz said:
what kind of errors did you get when you flashed other roms??
Click to expand...
Click to collapse
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.

Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
have you tried flashing through HBOOT??

prunzzz said:
have you tried flashing through HBOOT??
Click to expand...
Click to collapse
That is done by renaming a file to PG98***?

Killa_vatt said:
If I am flashing from exe file through fastboot I get ERROR [131]: CUSTOMER ID ERROR.
If I use fastboot flash boot boot.img I get no errors but it still stucks on HTC screen.
If I flash using 4ext install zip mode I still get no errors but it stucks.
I also got error that I dont have boot.prop in my system.
I cant remember other errors that I had.
Click to expand...
Click to collapse
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.

tpbklake said:
The ERROR 131 means that you are trying to flash an official RUU for a different carrier/region. You need to create a goldcard in order to successfully flash a RUU.
Why don't you try flashing a custom ROM from recovery and then flash the boot.img file.
Click to expand...
Click to collapse
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.

Killa_vatt said:
Ive created a goldcard.
I tried to flash a custom rom-still stuck at whitescreen.
Click to expand...
Click to collapse
OK, after re-reading your posts, here are some additional tips:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
As for trying to flash 10 different RUU's there ERROR 131 indicates that you have a bad goldcard.

Killa_vatt said:
That is done by renaming a file to PG98***?
Click to expand...
Click to collapse
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Also consider what tpbklake said
HIT THANKS IF I HELPED YOU

tpbklake said:
When flashing a custom ROM from 4EXT, please make sure you do a full system wipe and then clear both Cache and Dalvik cache before you flash the ROM.
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
prunzzz said:
Hey not PG98!!!!
PG32IMG.zip!!!!!
Try it now
Click to expand...
Click to collapse
I mean PG32IMG,forgot that.
I fully wiped everything.
I did not flashed rom's boot.img,thanks! Gonna try it later.

tpbklake said:
After you flash the ROM, then you need to immediately flash the ROM's boot.img file contained in the zip file using FASTBOOT USB mode.
Click to expand...
Click to collapse
Thank you very much! I feel dummy now =)
Flashing rom's boot.img fixed all problems. Most of roms works now. Thanked everyone in topic.

[Q] How to Flash Radio via fastboot

I am using ATT htc one with developer edition OS. And I learned from the forum there was new radio released be att. So I tried to flash it.
However, since I want OTA work, I chose to stay with the stock recovery and therefore I cannot flash it via custom recovery like a lot of threads in here talking about. I searched and only found the procedure from other htc product's forum as below.
1) adb reboot-bootloader
2) fastboot flash radio radio.img
But "fastboot flash radio radio.img" has no response at all.
I got the img from http://forum.xda-developers.com/showthread.php?t=232556. It was extracted from Radio_4A.16.3250.24_10.38.1150.03.zip.
My current build is 1.29.1540.17, while baseband is still 4A.14.3250.13, which is the original. And Ive already s-offed and unlocked bootloader.
Any help about flashing? Thanks in advance.

lowirve said:
I am using ATT htc one with developer edition OS. And I learned from the forum there was new radio released be att. So I tried to flash it.
However, since I want OTA work, I chose to stay with the stock recovery and therefore I cannot flash it via custom recovery like a lot of threads in here talking about. I searched and only found the procedure from other htc product's forum as below.
1) adb reboot-bootloader
2) fastboot flash radio radio.img
But "fastboot flash radio radio.img" has no response at all.
I got the img from http://forum.xda-developers.com/showthread.php?t=232556. It was extracted from Radio_4A.16.3250.24_10.38.1150.03.zip.
My current build is 1.29.1540.17, while baseband is still 4A.14.3250.13, which is the original. And Ive already s-offed and unlocked bootloader.
Any help about flashing? Thanks in advance.
Click to expand...
Click to collapse
Did you try the fastboot flash command in RUU mode? Fastboot oem reboot RUU. This is just a guess on my part, but that's the mode for firmware flashing, so guessing it might work for the radio too.

In order for a radio to be flashed in fastboot it has to be packaged in a zip file that rubootRUU mode understands. It's easier for most people to just flash in recovery

gunnyman said:
In order for a radio to be flashed in fastboot it has to be packaged in a zip file that rubootRUU mode understands. It's easier for most people to just flash in recovery
Click to expand...
Click to collapse
Thanks, gunny. I had an idea that was how it worked, I appreciate the knowledge! Is the OP out of luck then? Is there any way for him to flash a radio if he's on stock recovery?

It's easy enough to flash custom recovery then radio then put stock recovery back on.

gunnyman said:
It's easy enough to flash custom recovery then radio then put stock recovery back on.
Click to expand...
Click to collapse
Oh, so like the normal way the rest of us did it lol! Thanks, gunny!

Thank you all. Looks like the only choice for me now is stop being lazy and use custom recovery, then flash it back to stock.
In the first place, I thought there was an easy method to use fastboot like other htc products.

gunnyman said:
In order for a radio to be flashed in fastboot it has to be packaged in a zip file that rubootRUU mode understands. It's easier for most people to just flash in recovery
Click to expand...
Click to collapse
So I guess the zip file I got was prepared for recovery use only, right? I have been comparing it with firmware zip file found in RUU flashing thread (http://forum.xda-developers.com/showthread.php?t=2365506&highlight=flash+latest+radio+fastboot). RUU flash's file includes android-info.txt to enable fastboot read the image inside zip file.

lowirve said:
So I guess the zip file I got was prepared for recovery use only, right? I have been comparing it with firmware zip file found in RUU flashing thread (http://forum.xda-developers.com/showthread.php?t=2365506&highlight=flash+latest+radio+fastboot). RUU flash's file includes android-info.txt to enable fastboot read the image inside zip file.
Click to expand...
Click to collapse
I forgot about this file that was posted in AT&T Developer Forum, it's a packaged firmware file with only radio updates. The post also contains the latest firmware that includes newest touch driver. Newest touch driver doesn't work with 4.1.2 ROMs and older recoveries.
http://forum.xda-developers.com/showthread.php?p=44260480
Sent from my HTC One using xda app-developers app

ilal2ielli said:
I forgot about this file that was posted in AT&T Developer Forum, it's a packaged firmware file with only radio updates. The post also contains the latest firmware that includes newest touch driver. Newest touch driver doesn't work with 4.1.2 ROMs and older recoveries.
http://forum.xda-developers.com/showthread.php?p=44260480
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the finding:good:. I haven't read it before.

[Q] How can I reinstall a good image after flashing my boot with CWM?

My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as Understood​I was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial Solution​At first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
Question​So how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682

1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img

Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload

abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.

bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread

Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!

bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way

bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.

russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?

bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"

So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app

stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted

astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!

Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...

Wont boot to recovery after flashing

Hey,
I dont know how different things are now, i installed a RUU with lollipop and i've been trying to flash TWRP but after i try to get into recovery and i got stuck at the logo with "entering into recovery...", adb detects device and nothing happens, tried to delete cache still didnt work. I bet i'm missing something as stupid as a simple boot...

Terramoto said:
Hey,
I dont know how different things are now, i installed a RUU with lollipop and i've been trying to flash TWRP but after i try to get into recovery and i got stuck at the logo with "entering into recovery...", adb detects device and nothing happens, tried to delete cache still didnt work. I bet i'm missing something as stupid as a simple boot...
Click to expand...
Click to collapse
you flash the recovery for the m7wls.

Aldo101t said:
you flash the recovery for the m7wls.
Click to expand...
Click to collapse
what kind of statement was that? Or was it a question? Yep i flashed m7wls isn't that sprint version of TWRP?
EDIT: I think i know what you mean, TWRP is not working well with lollipop, is that it?

Terramoto said:
what kind of statement was that? Or was it a question? Yep i flashed m7wls isn't that sprint version of TWRP?
EDIT: I think i know what you mean, TWRP is not working well with lollipop, is that it?
Click to expand...
Click to collapse
no just checking you installed the correct recovery, for lollipop you should have the latest recovery, that's all

I can't either get root or flash a ROM without access to recovery?

what else can i do?

Terramoto said:
what else can i do?
Click to expand...
Click to collapse
Reflash latest firmware from here http://forum.xda-developers.com/showthread.php?t=2795856 (i recommend Modified Firmware....removed hboot, recovery & boot (fastboot flashable))
Then flash latest recovery twrp-2.8.6.0-m7wls..

crazykas said:
Reflash latest firmware from here http://forum.xda-developers.com/showthread.php?t=2795856 (i recommend Modified Firmware....removed hboot, recovery & boot (fastboot flashable))
Then flash latest recovery twrp-2.8.6.0-m7wls..
Click to expand...
Click to collapse
Didnt work, it tries to enter recovery but its like there's no recovery. The phone's not letting me flash the recovery only the stock one

Terramoto said:
Didnt work, it tries to enter recovery but its like there's no recovery. The phone's not letting me flash the recovery only the stock one
Click to expand...
Click to collapse
Did you flash the firmware first?

crazykas said:
Did you flash the firmware first?
Click to expand...
Click to collapse
yeah, i flashed the modified first then tried to flash recovery, it just wont go into recovery. Is there a way to downgrade back to kitkat? Everything was working good with kk, i had to replace the display, camera and battery so i flashed lollipop RUU thinking there wouldnt be any difference... Now i can't even get root

Terramoto said:
yeah, i flashed the modified first then tried to flash recovery, it just wont go into recovery. Is there a way to downgrade back to kitkat? Everything was working good with kk, i had to replace the display, camera and battery so i flashed lollipop RUU thinking there wouldnt be any difference... Now i can't even get root
Click to expand...
Click to collapse
Was there any error when you flashing recovery?It just doesn't boot to recovery?Then you should flash FULL RUU..It should be the fix

crazykas said:
Was there any error when you flashing recovery?It just doesn't boot to recovery?Then you should flash FULL RUU..It should be the fix
Click to expand...
Click to collapse
no error, everything went smooth its just the boot part, funny thing is im able to flash and boot twrp 2.5.0.0 but im not able to use it because it doesnt respond to touch. I'm currently with stock recovery but i'd like to root and remove crappy apps from my phone :\

Terramoto said:
no error, everything went smooth its just the boot part, funny thing is im able to flash and boot twrp 2.5.0.0 but im not able to use it because it doesnt respond to touch. I'm currently with stock recovery but i'd like to root and remove crappy apps from my phone :\
Click to expand...
Click to collapse
i faced that prob too,but i just had to update to latest firmware & recovery.Flash twrp 2.6.0 & try.

crazykas said:
i faced that prob too,but i just had to update to latest firmware & recovery.Flash twrp 2.6.0 & try.
Click to expand...
Click to collapse
I think i did that, isnt that what RUU's suppose to do?
Anyway, here's the log and last_kmsg if anyone knows how to trace this
log:
http://www.pastebin.ca/2978960
Last_kmsg:
http://pastebin.ca/2978961
@mdmower

I was told that since i replaced parts i might have replaced a part thats not the same as the original one and that i would need to make a custom recovery. I've already download the kmsg report (http://pastebin.com/USayUFqx) i just need some eyes that understand whats happening.

How do I change the radio and boot loader?

Go easy....
Wanting to flash some of the newer M ROMs.
Requirements are latest radio, boot loader and TWRP
How do I change those?
I'm root and twrp installed. Are there zips to flash in recovery 1st?
Steps or even a video would be HUGE, and thank you for helping.

The information is everywhere. You have to flash the radio/bootloader in fastboot mode. You can't flash them in recovery.

SirBindy said:
The information is everywhere. You have to flash the radio/bootloader in fastboot mode. You can't flash them in recovery.
Click to expand...
Click to collapse
I beg to differ :
http://forum.xda-developers.com/showthread.php?t=3066052
This is how i did it, in recovery.
It's all just an illusion

robfromga said:
Go easy....
Wanting to flash some of the newer M ROMs.
Requirements are latest radio, boot loader and TWRP
How do I change those?
I'm root and twrp installed. Are there zips to flash in recovery 1st?
Steps or even a video would be HUGE, and thank you for helping.
Click to expand...
Click to collapse
I was in a similar situation, I have MultiRom, and I wanted to preview M out without getting rid of PureNexus. So this is what I did
Download factory image for M
Make sure you have the latest android SDK!!!
extract the factory image
rename bootloader file to bootloader.img; rename radio file to radio.img
connect your device and reboot into bootloader
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
then reboot your phone, and you are good
if you are uncertain about it, take a look at flash-base.sh, or flash-all.bat, and follow those steps.

most bootloaders and radios ARE available via a flashable zips that can be flashed via twrp, you just have to look for them. otherwise, fastboot is very easy.

I found the zips and flashed them with flashify. How do I know if it took? What is the radio listed under settings?
Settings-about phone-?

robfromga said:
I found the zips and flashed them with flashify. How do I know if it took? What is the radio listed under settings?
Settings-about phone-?
Click to expand...
Click to collapse
If you flashed the marshmallow radio, the baseband should end in .27r.
It's all just an illusion

robfromga said:
I found the zips and flashed them with flashify. How do I know if it took? What is the radio listed under settings?
Settings-about phone-?
Click to expand...
Click to collapse
i dont think you can flash the bootloader via flashify.

Does flashing marshmallow factory image not update the boot loader and radio with it ? Ie flashing marshmallow from NRT toolkit ?

bigup7 said:
Does flashing marshmallow factory image not update the boot loader and radio with it ? Ie flashing marshmallow from NRT toolkit ?
Click to expand...
Click to collapse
if you flash the whole thing it does.

simms22 said:
if you flash the whole thing it does.
Click to expand...
Click to collapse
Ahh great. Had me confused for a bit

bigup7 said:
Ahh great. Had me confused for a bit
Click to expand...
Click to collapse
if youre rooted, and dont want to go through the process again, and dont want to lose your data, all you have to do is flash the boot.img and the system.img to update the rom. and then reflash supersu in twrp

Right baseband?

robfromga said:
Right baseband?
Click to expand...
Click to collapse
That's what I have. You should be good.
It's was all just an illusion

Sweet!
So if I'm understanding everything, I'm now on the latest update of TWRP ,bootloader and radio....so its OK to flash M?

Yep
It's was all just an illusion