[Q] Did I brick it? - Droid Incredible Q&A, Help & Troubleshooting

[Q] Did I brick it? - Droid Incredible Q&A, Help & Troubleshooting

SOooooooooooo, I was hoping to get Froyo installed on my DInc, and considered waiting for the OTA version, but wanted to do a full wipe and start from scratch. I got a hold of the RUU file and tried to install via the windows interface. When I couldnt get that to work I exctracted the Rom.zip file, renamed it PB31img.zip and ran it through the recovery screen. Everything seemed to work just fine. It verified the file several times, then asked me if I wanted to update. I hit volume up for yes and allowed it to do its thing. It showed several different screens with different progress bars, and seemed to reboot several times. One of the times though, it just went black. Now I cant get it to do anything.
So the question lies therein,,,, did I kill it? I researched a lot before, and have obviously been researching since, and feel like I followed everything correctly. If I did mess it up, is there any saving it?

Jimmydaux said:
SOooooooooooo, I was hoping to get Froyo installed on my DInc, and considered waiting for the OTA version, but wanted to do a full wipe and start from scratch. I got a hold of the RUU file and tried to install via the windows interface. When I couldnt get that to work I exctracted the Rom.zip file, renamed it PB31img.zip and ran it through the recovery screen. Everything seemed to work just fine. It verified the file several times, then asked me if I wanted to update. I hit volume up for yes and allowed it to do its thing. It showed several different screens with different progress bars, and seemed to reboot several times. One of the times though, it just went black. Now I cant get it to do anything.
So the question lies therein,,,, did I kill it? I researched a lot before, and have obviously been researching since, and feel like I followed everything correctly. If I did mess it up, is there any saving it?
Click to expand...
Click to collapse
Well let me ask you a few questions.
1) how much battery did you have
2) what radio and software were you on previously.
3)s-off, or s-on
4) does it give you the charging light on the phone when plugged in?

Do you remember if it got past the "flashing hboot" and "flashing radio" screens all the way? If it did, you can still probably recover. Does the light turn on when you plug it in?

I probably had 80-85% battery. It was stock other than an update to the 2.05 radio.
It went through a few screens but I wasnt paying much attention to what they were exactly. I think I was nervous enough that I had to work on something else while it was working *laundry*
Software was stock 2.1. I hadnt done anything with that. From the Ruu I think I remember it being 1.36 or something close to that. Deffinitely not the 3.xx that the RUU said it would flash it to.
And the one that I think is going to seal my fate,,, no, the battery light does not come on when plugged in.....
I think I sense the answer,,, hello expensive paper weight,,, door stop, potato gun ammunition...

Jimmydaux said:
I probably had 80-85% battery. It was stock other than an update to the 2.05 radio.
It went through a few screens but I wasnt paying much attention to what they were exactly. I think I was nervous enough that I had to work on something else while it was working *laundry*
Software was stock 2.1. I hadnt done anything with that. From the Ruu I think I remember it being 1.36 or something close to that. Deffinitely not the 3.xx that the RUU said it would flash it to.
And the one that I think is going to seal my fate,,, no, the battery light does not come on when plugged in.....
I think I sense the answer,,, hello expensive paper weight,,, door stop, potato gun ammunition...
Click to expand...
Click to collapse
The question though is: How did it happen?
It could be possible that the RUU download was corrupted. Specifically the bootloader. Do you have the insurance?
Also a battery pull / charge and pray couldnt hurt at this point. How long has it been this way?

Fretless said:
The question though is: How did it happen?
It could be possible that the RUU download was corrupted. Specifically the bootloader. Do you have the insurance?
Also a battery pull / charge and pray couldnt hurt at this point. How long has it been this way?
Click to expand...
Click to collapse
I totally agree, if on radio 2.05x it doesn't make much of any sense that a brick happened.

Agreed. In fact, I just performed this exact same procedure myself and it worked perfectly. The only difference was that I had s-off and the stock radio.

Were certainly missing a variable here.

Jimmydaux said:
It was stock other than an update to the 2.05 radio.
...
Click to expand...
Click to collapse
Bingo.
If I was to point to one thing, it would be the 2.x radio, as this ruu and the accompanying ota probably assume the use of the 1.x radio, since the 2.x ota was never publicly released. Unless the battery somehow died or fried in the middle of the flash. I feel for you man. I would cry if mine died...
I'd point my inexperienced unlearned finger squarely at the 2.05.x radio.
Dude, this is a very good chance for you to make verizon give you a new one. Think of it as a golden opportunity.

Fretless said:
Bingo.
If I was to point to one thing, it would be the 2.x radio, as this ruu and the accompanying ota probably assume the use of the 1.x radio, since the 2.x ota was never publicly released. Unless the battery somehow died or fried in the middle of the flash. I feel for you man. I would cry if mine died...
I'd point my inexperienced unlearned finger squarely at the 2.05.x radio.
Dude, this is a very good chance for you to make verizon give you a new one. Think of it as a golden opportunity.
Click to expand...
Click to collapse
Also called warranty fraud.

ACD168 said:
Also called warranty fraud.
Click to expand...
Click to collapse
Not so! Its called warranty use!
He did not root the phone, so its not fraud. All he was doing was installing what he thought was a legitimate RUU.
Not fraud.
Apologies if i missed something.

Fretless said:
Not so! Its called warranty use!
He did not root the phone, so its not fraud. All he was doing was installing what he thought was a legitimate RUU.
Not fraud.
Apologies if i missed something.
Click to expand...
Click to collapse
I agree, just being a smart ass lol. I'd make full use outta calling for a refurb.

ACD168 said:
I agree, just being a smart ass lol. I'd make full use outta calling for a refurb.
Click to expand...
Click to collapse
To be honest, I'd be a hot candidate for warranty fraud if mine messed up. Call me evil...

The 2.05 radio is not to blame. I had the that same radio and used the Rom.zip to update my phone with no problems. Only difference was I have s-off but that shouldn't make a difference here. Everything else was stock including the recovery.
Sent from my Droid Incredible

OP, did you perform a checksum on the RUU to verify it was a complete download?
I also don't think the 2.05 radio is to blame here either.
Hmm....

Technically, it is warranty fraud, since he's invoking the warranty right by damage caused by the user, which warranties don't cover unless they're accidental damage warranties.

The 2.05 radio shouldn't matter. The RUU contains a radio img not a patch like the 2.05 leak.

Well friends, I couldnt get anything to happen. I took it into the Verizon store and I told them that I was trying to install the update and something happened mid install and it died. I asked him if that would be something I would have to file an insurance claim on, but he said that it wasnt my fault if it died during the update........... his words.... so they gave me another phone to replace it. THey were all out of their 'replacement' phones, so I actually got a brand new phone because of this whole deal. I lucked out I know! And yes,,,, i may have shed a tear or two yesterday when it happend, but after walking into the V store, I had a crazy overwhelming relief that I wasnt going to be at a complete loss.
So, just in case anyone is following this,,, what other variables would need to be looked at in order to see why this happened.
I did not run a Checksum, but it seemed to run other than the driver issues. The Rom file that was installed was 168 mb, renamed properly and installed through the recovery screen from the sd card root. The phone was not touched during this time. Did I just have a misfortunate run in with what I thought was a legitimate way to get the update installed?

Jimmydaux said:
Well friends, I couldnt get anything to happen. I took it into the Verizon store and I told them that I was trying to install the update and something happened mid install and it died. I asked him if that would be something I would have to file an insurance claim on, but he said that it wasnt my fault if it died during the update........... his words.... so they gave me another phone to replace it. THey were all out of their 'replacement' phones, so I actually got a brand new phone because of this whole deal. I lucked out I know! And yes,,,, i may have shed a tear or two yesterday when it happend, but after walking into the V store, I had a crazy overwhelming relief that I wasnt going to be at a complete loss.
So, just in case anyone is following this,,, what other variables would need to be looked at in order to see why this happened.
I did not run a Checksum, but it seemed to run other than the driver issues. The Rom file that was installed was 168 mb, renamed properly and installed through the recovery screen from the sd card root. The phone was not touched during this time. Did I just have a misfortunate run in with what I thought was a legitimate way to get the update installed?
Click to expand...
Click to collapse
You brick your phone and they give you a brand new one. no way, how old was your other phone. and what state are you in. they took care of u.

You going to tell on him lol
Sent from my ADR6300 using XDA App

Related

Telus Desire ROM Needed ASAP.

Hi. I recently rooted and installed a WWE "sensefroyo" rom off the internet.
And I just figured out (since a couple of hours) that my speaker isn't working AT ALL.
Before, it worked when you left the battery out for a minute and put it back in. it worked flawlessly. But after a while it'd go back to being messed up.
Now its screwed. and wont work at all.
I didnt realise I needed to get it replaced till now.
I really need the Telus Desire rom asap. As I just emailed them about it, and most likely need to get it replaced/fixed. And I dont know much about Telus, if you lose warranty privileges if you root/custom ROM it.
Unless I can tell them that I installed the official 2.2 ROM (dont know if it needs root) off those .exe files (the RUU_Signed) kind. (They didn't work for me. So i rooted using recovery)
Or if you can link me to one where I can find a rom that does not require rooting, and has an .exe file and a copy of a .zip kind.
I wrote a lot here, and its all over the place.
Right now. Either link me to the Telus Desire rom. or one where I can flash without rooting.
I am going to unroot as soon as I get one of those two things^
Thanks. I just hope you guys know what kind of freaky situation I am in.

Where did you buy it, and how long has it been since you bought it?
Depending on those factors, you may not need to worry too much.

I had it activated on a 3 year contract almost a week ago(Not even a week)
What do you mean by I will not have to worry about these things?
Is Telus a carrier that is more on the 'chill' side of things?
EDIT - So I just got off the phone with Telus.
The representative told me if I installed something that Telus did not release. That basically voids my warranty. So now I really need to get back exactly as it was before.
Can someone please help me out here?
I need to go to a dealer soon to get it replaced.
I am pretty sure I can unroot it myself with no issues I guess.
I really need something that matches with the same stats as a Telus Desire.

You should probably try starting over.
If your rom is still rooted, get ROM Manager and install clockworkmod.
You can install something stable like opendesire and wipe data/cache.
You should be fine, unless you really have some unusual desire to be on Telus' rom.

I was wondering if someone can post what their 'software version' looked like on a Telus Desire
Maybe then I can try to get the same radio and 'stats' as a factory device.
I got on a rep and they also said that the worst thing that can happen is your device will be sent back.
They even said that some people wont even notice the software change and stuff.
If at the end I cant get a Telus rom. I would LOVE a link to an Eclair build rom. Possibly one that is an official.

Didn't you nandroid backup prior to moving to froyo?
From what I understand you can restore from that.

mfpreach said:
Didn't you nandroid backup prior to moving to froyo?
From what I understand you can restore from that.
Click to expand...
Click to collapse
I actually have NO idea what nandroid was.
I just followed instructions off a tut on xda.
So I cant seem to find factory eclair roms.
Now I read around a little bit more.
And just feel completely stupid.
Please. Someone. A factory Eclair build.

start by getting clockworkmod installed.
Without knowing what state your device is in, it's tough to help you.
but with clockworkmod recovery going, you will easily be able to switch between roms.

Honestly you couldn't have bought it that long ago, just return it to the store, the guys don't even know how to check.

routehero said:
start by getting clockworkmod installed.
Without knowing what state your device is in, it's tough to help you.
but with clockworkmod recovery going, you will easily be able to switch between roms.
Click to expand...
Click to collapse
I already do have it. Thats how i installed all the different roms (Leedroid, Nightly Cyanogen, and then eventually the official one)
Hold on for a couple of minutes as I can provide you with some of my hboot and so recovery options. (Using the WiFi hot spot at the moment)
Other then that. Here is my 'software version'
android 2.2 with the latest 32.43.00.32U_5.09.00.20 radio
Kernel is
2.6.32.15-g1fc4045
[email protected]#1
Build #
2.06.832.1 CL207528 test-keys
Software Number
2.06.832.1
with the obvious webkit 3.1
hboot info?
BRAVO PVT3 SHIP S-ON
HBOOT-0.83.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.00.20
Jun 10 2010, 12:12:05
Used ClockworkMod Recovery v2.5.0.1
Yes it is an SLCD display?
you needs more? - tell me what exactly you need and how I can get it

download opendesire 3.5.0, wipe data/cache, flash that.
after you set it up, let us know what's not working.

If I were you, I would go back to the store you got it from, with your recipt and contract. You have 14 days to return any phone. That's how I got my desire, I returned a Hero. Make sure you take everythign back you got, charger, phones, etc. Tell them waiting to get a band new phone fixed is a waste of your time, and you want to exchange the phone right away.
So long as you have a sense UI ROM running, I doubt they will know you have rooted the phone. The guys where I bought the phone didn't know too much about it.
If you managed to get a tech support guy to tell you they might not notice, you clearly have the power to get what you need from people. Be forceful if you have to, within 2 weeks they should just give you a brand new phone. After 14days though, your gonna have to live with no speaker, hope it's actually a software issue(doesn't sould like it if even stock it was failing), or send it back and hope they don't miss it. To the best of my knowledge there are no Telus official roms to be found, but there are many official roms from other places. As long as your background doesn't say VodaPhone or something, how will they know?

ajanu said:
If I were you, I would go back to the store you got it from, with your recipt and contract. You have 14 days to return any phone. That's how I got my desire, I returned a Hero. Make sure you take everythign back you got, charger, phones, etc. Tell them waiting to get a band new phone fixed is a waste of your time, and you want to exchange the phone right away.
So long as you have a sense UI ROM running, I doubt they will know you have rooted the phone. The guys where I bought the phone didn't know too much about it.
If you managed to get a tech support guy to tell you they might not notice, you clearly have the power to get what you need from people. Be forceful if you have to, within 2 weeks they should just give you a brand new phone. After 14days though, your gonna have to live with no speaker, hope it's actually a software issue(doesn't sould like it if even stock it was failing), or send it back and hope they don't miss it. To the best of my knowledge there are no Telus official roms to be found, but there are many official roms from other places. As long as your background doesn't say VodaPhone or something, how will they know?
Click to expand...
Click to collapse
Telus has 30 day DOA over the counter exchange.

YAh but he made the mistake of telling them e rooted and flashed it (why on earth would any one do that i dont know)
So they have flagged that IMEI in the system as void.
Your best bet is to try doing a wipe and flashing back to the telus 2.1 rom and radio, you will, the recovery is gone though as we dont hava ruu.

Actually. I didnt. I went straight for asking the question off a residential phone that uses Rogers. So they don't know who I was or any account related things.
The first time I called though, I told them that the speaker wasnt working and I wanted it replaced.
So no my IMEI is not flagged, guarantee you that part.
I will try using the OpenDesire 3.5.0 with "clear/wire cache"

This might work for you and i think its your best bet.
http://forum.xda-developers.com/showpost.php?p=6710085&postcount=3
Go to the above thread, follow the instructions and make a gold card.
then go to the following thread, download official froyo rom and flash it. It looks almost the same as the original rom.
http://forum.xda-developers.com/showthread.php?t=753672

I cant seem to do the goldcard thing.
I am using the official 2.2 at the moment.
It does look the same as 2.1 Telus itself.
What does it mean over here?
# Ensure you have unzipped the SDK, then open a command prompt to the extract location. Change to the 'tools directory.
# Type
Code:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
and press enter. You should get a very long number which looks like this: 532600bd227d9c0347329407514d5402.
Click to expand...
Click to collapse
I cant seem to do the "command prompt" location thing.
Someone wanna help me? maybe with some screenshots?

I am done making the GoldCard. What does it even do though?
It has something to do with switching to the factory rom..
Now. I have issues with the RUU. It does not wait long enough for the phone to be in bootloader.
EDIT - Is there any way I can "remove" or uninstall the Superuser Permissions app and the "Wi-Fi Hotspot" app? To make it appear even more legitimate.

da pavinator said:
I am done making the GoldCard. What does it even do though?
It has something to do with switching to the factory rom..
Now. I have issues with the RUU. It does not wait long enough for the phone to be in bootloader.
EDIT - Is there any way I can "remove" or uninstall the Superuser Permissions app and the "Wi-Fi Hotspot" app? To make it appear even more legitimate.
Click to expand...
Click to collapse
I packed up the telus stock rom from a nandroid dump you can try it.
http://www.mightyrom.com/mrx/MRX/Bravo/Stock/Telus_HTC_Desire_Stock_2.1_NoRADIO.zip

Hey I needed to unroot my phone too and I tried a bunch of things then I was following procedures to root my phone again because I tried installing the Rom that was posted by the person that posted before me and I messed up and got lots of errors when I got the phone started and had to force close a bunch of things constantly. Anyways I followed step 3 of the tut for rooting TELUS desires on this forum site and when it restarted I got my stock TELUS Rom back unrooted. This is the step I followed
3. Go to HBOOT, this is done by shutting down your phone and powering on the device while holding the Power button down and pushing Volume down at the same time, once HBOOT is loaded do a wipe (Clear Storage). You can navigate the menus by using the volume rocker and the Power button to select your option.
forum.xda-developers.com/showthread.php?p=7818278 is the link to the tut I was following.
I dunno how it worked but it did, I got my stock TELUS Rom by doing this. Maybe I got lucky and maybe you might too. Oh and just for your info, the tut I used to root my desire initially was this one forum.xda-developers.com/showthread.php?t=750888. Good luck

[official] Problems with Telus OTA update.

So, just to keep telus update waiters in touch with whats going on with the OTA Froyo 2.2 update.
EDIT : The RUU is also avaiable ! You can continue to mess with your desire..and get back to the factory ROM if any problem:
[RUU] RUU_Bravo_Froyo_TELUS_WWE_2.25.661.2_Radio_32.49.0 0.32U_5.11.05.27 (thanks to football)
http://www.multiupload.com/T5H6PHUL33
The update is now available. Go to settings > about phone >check updates....to force the update.
Before launching it....be sure to have 90mo on the SD card free and 25mo on the phone.
http://fotadl.htc.com/OTA_Bravo_Fro....2-1.29.661.1_R_release_Pf7sjzjrgcmpsve12.zip
radio for those who just want that. http://www.mightyrom.com/mrx/MRX/Bravo/Radio/Signed/32.49.00.32U_5.11.05.27.zip
For root users...if you have problems with installing the update or if you are sucked in a boot loop or if you get this message
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
Do this:
On your Phone
1. open Astro and go to "download" folder
2. long-press and select "edit"
3. press "move"
4. press back button
5. press "edit" from the top menu bar
6. press "paste"
7. long press the file
8. press "edit", then press "rename"
rename to update.zip then press OK
Installation
*power off phone
*hold "volume down" and turn on phone
A screen should appear showing your phone's system searching for various files. Scroll down to “recovery” using the volume down button and press the “Power” button
*When you see the triangle with an exclamation point symbol, press the “Power” and “Volume Up” buttons at the same time. This may take a few attempts
*From the menu that appears, use the trackball to select "Apply sdcard:update.zip." Press down on the trackball to start.
*When the screen displays "Install from sdcard complete" use trackball to select "reboot system now" and wait for the phone to power back up.
I will put links to how to resolve different problems later...

If it's not out tomorrow, I think that's gonna be the push I need to make one of those fancy goldcards and install an RUU version of Froyo. What does the telus one have anyway, EDGE disabled?
EDIT: Thanks for collecting this info; more than I knew before.

The telus update won't offer much as I know. They will put some of their crappy apps that you can't delete...add some feature in apps (music dowloading or ringtones downloading... with some downloadable stuff) and thats it.
Any developers on XDA could do this job within 1 week... Htc desire was out on july or august on Telus... and they struggle to get it done in time.
Gold card is not a bad idea at all. Avoiding warranty kinda hurt me.

ecitron said:
We've been waiting for 4 months now...1 week or two won't kill us.
Click to expand...
Click to collapse
I got one of the very first Desires from Telus and had it running a custom ROM within three days.
I'm on 2.2.1 now. LOL!

no reason in loosing your mind over this
my phone is currently not working because of radio not compatible with froyo issue. And this RUU might possibly be the only i can fix my problem. No one on this forum was able to give me any help.
Every minute is too long of a wait. RUUs should be out the second a phone is out with the original rom and so on. Not when updates come up and the whole world had time to test those updates..and then..you know what..last minute we notice there's an issue. It's ok, it's not like people stuck in a 3 year contract with a nice paper weight as a phone can do anything about it either..

marinierb said:
I got one of the very first Desires from Telus and had it running a custom ROM within three days.
I'm on 2.2.1 now. LOL!
Click to expand...
Click to collapse
Root and flash a custom ROM is an easy option... anyone can do it... but like I said... many people don't want to loose their one year warranty...
I'll wait to see what's in the update package... if too many ****ty telus's apps ... I will probably jump in the boat. Unbrand the phone with a gold card and get OTA updates directly from HTC seems to be the cleanest solution for me.
Come on Telus...don't disappoint us ...
btw: More then 50% Desire's owner (Canad) are not with telus... we all bought the phone at full price. And get stucked with telus's apps ( and you can't remove them) will defininetly be disappointing.

ecitron said:
Unbrand the phone with a gold card
Click to expand...
Click to collapse
No need to do the goldcard thing. You can use Unrevoked.

ecitron said:
btw: More then 50% Desire's owner (Canad) are not with telus... we all bought the phone at full price. And get stucked with telus's apps ( and you can't remove them) will defininetly be disappointing.
Click to expand...
Click to collapse
That could be the reason to why Telus took out the outright price. I'm with Telus and I even bought it outright then gave it off and bought another outright a month later.
And yes Telus are one of the worst for OS updates, the Hero just got the 2.1 update today. And the Milestone has been taking forever.

Good morning canada.
Last news from people who called this morning.
It will be the 28th, 29th, 30th and finally the last day for all the unlucky people 31st.
Click to expand...
Click to collapse
I will call later in the day by myself and get u in touch.
Sent from my HTC Desire using XDA App

Yeah my phone made a strange noise last night and i figured it was this update.
Telus is the worst with OS updates. It was a full year before the Black Berry os update came to the Storm. I tried to do some freaking out at the store to get a new phone style stuff when they told me the new update just came out. I told them it had been a year- why would I assume it would ever come out?
Ill wait to see what ****ty Telus apps they install (is that what is taking them so long?) before I decide what I want to do. I could unbrand or switch to a diff rom- but I think I like sense.

I can understand the "RAGE" about telus sucking at updates. But why are you guys so upset. they will release froyo, all the **** in it will be old as dirt. no one will use anything from it to build a custom rom. And if you want something good you will flash a custom one.
Its like telling the future, except im pretty much guaranteed to be right.
The only thing if at all im concerned about is the ril and the radio.
And maybe a telus voice call app cuz they have it on my account, but be ****ed if i know how to get it going right now.
As for telus and installing ****ty apps. they have been good about that lately, i expect to see little to no Telus apps on the rom. The 2.1 rom was devoid of anything telus but the home page.

Good is subjective my friend. If you find froyo old as dirt its ok... but four those who want to keep their warranty...we have no choice. The probability of loosing 600$ is enough to not make changes on our phone...that will result on loosing the warranty.
Your are not the first...and not the last person to tell us to root..unbrand and bla bla bla...
Sent from my HTC Desire using XDA App

ecitron said:
Good is subjective my friend. If you find froyo old as dirt its ok... but four those who want to keep their warranty...we have no choice. The probability of loosing 600$ is enough to not make changes on our phone...that will result on loosing the warranty.
Your are not the first...and not the last person to tell us to root..unbrand and bla bla bla...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Loosing warranty is relative to the knowledge of the user.
There is a pretty easy way to put the device back to factory software if you take the correct steps.
Thats if you have to. If the device is a brick before you return it then no harm.
ive already unrooted a telus desire, restored the stock rom from a nandroid backup (unrooted the backup) then flashed the radio back to the stock telus radio. after this i used fastboot to flash a stock recovery back on and lastly flashed the .83.0001 Hboot with fastboot, removing the s-off hboot. effectively returning the whole device back to stock. with all the correct software version numbers.

Juggalo_X said:
Loosing warranty is relative to the knowledge of the user.
There is a pretty easy way to put the device back to factory software if you take the correct steps.
Thats if you have to. If the device is a brick before you return it then no harm.
ive already unrooted a telus desire, restored the stock rom from a nandroid backup (unrooted the backup) then flashed the radio back to the stock telus radio. after this i used fastboot to flash a stock recovery back on and lastly flashed the .83.0001 Hboot with fastboot, removing the s-off hboot. effectively returning the whole device back to stock. with all the correct software version numbers.
Click to expand...
Click to collapse
It's good to know that it is possible to return to the stock config. I think a lot of us "waiters" would get off the bench if we knew it was possible to go back to stock if necessary.
Juggalo_X, would you consider writing a step by step process for returning a Desire to the stock config? Since you have already done it...

The thread is not about how to flash a stock ROM.
I will pay to see you restoring a stock rom when The screen is dead or when your phone wont start...
Sent from my HTC Desire using XDA App

I got a Telus Desire, so here is my delema (and question)
1. Like HTC Sense and would like to keep it
2. Have a lot of reason to move to 2.2 (BT dialing)
3. want to root phone
I'm guessing there are stock HTC Desire rom floating around (from the factory unlocked desire) but are those rooted/rootable? I heard HTC has been making it harder and harder for us to root. And will rom for AMOLED work with sLCD phone?
===============================================
Oky did some more Google-ing and found this, might be useful to you guys
://forum.xda-developers.com/showthread.php?t=741775
This is the rooted official Desire Rom
don't have time now but will have look through if this will work for our radio and sLCD issue.
if you guys already know, feel free to post and tell us
AlphaX

I tried a similar (probably the same) rom, but from this thread:
hxxp://forum.xda-developers.com/showthread.php?t=773997
I updated the radio to the latest, everything seems to be good and no bugs that I can see.

ecitron said:
The thread is not about how to flash a stock ROM.
I will pay to see you restoring a stock rom when The screen is dead or when your phone wont start...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
There would be no point in restoring a dead device.
I'm under the impression that you think htc checks the flash on every dead device? this is not so. its cheaper for them to replace the whole main board in a device rather then pay an engineer to remove the board put it on a bed of nails dump the rom via jtag routine and then analyze the binary images.
Also, If we're on the topic of paying me to restore a device with a blank screen send me one ill jtag it for fun and restore the device. How much you willing to pay? i need a Desire Z you know
On a side note, In the past 5 years ive probably sent at the VERY least 15 bricked devices back to HTC, WITH software that would void the warranty on them. and i have ALWAYS got my device returned fixed under warranty every single time.

Juggalo_X said:
On a side note, In the past 5 years ive probably sent at the VERY least 15 bricked devices back to HTC, WITH software that would void the warranty on them. and i have ALWAYS got my device returned fixed under warranty every single time.
Click to expand...
Click to collapse
Pretty difficult to believe that. 15 bricked...
Also just about anyone (cell carrier, manufaturer via phone, etc) will tell you rooting, unlocking and modifying (removing bloatware) will void warranty. I have heard of people sending in devices with those and succeeding but not very often.

15 bricked in 5 Sears. A reason to not listen to you. Not everyone has the time to mess with their phones that much...learn to jtag..etc..
Sent from my HTC Desire using XDA App

[Q] DZ BRICKED!!! nothing at all

Okay, so while doing some unadvised actions, my Desire Z is in the state of not even being able to go into bootloader, recovery or signs of booting up. Not being able to get into bootloader I am unable to get into fasboot to reflash to needed files. It happened when I flashed the radio with Vision_TMOUS_RADIO_12.21.60.09b_26.02.01.15, the G2 one. The phone is s-off with 0005 hboot. I used the newer gfree method of doing this. If anyone can help me to get the phone to connect to the computer, then maybe I can flash whats needed. Or help me do what else to fix this brick, kinda shy of opening it up.

As far as I know, your phone is F.U.B.A.R. due to the fact that they have different radios, one specific to the tmobile G2 which has the different 3G bands as its "world" euro version aka the Desire Z. Sorry bro, vaya con dios. Someone correct me if Im wrong.
Sent from my HTC Vision using XDA App

kholk said:
Welcome to the HTC Vision (TMOUS G2 and Desire Z) Radio ROM & Official BLs Thread!
Well, my old HD2 Radio ROM Thread became a reference for all HD2 users, so.. I'm retrying this here now
Radio ROM Downloads:
Vision_RADIO_12.28e.60.140f_26.04.02.17: MegaUpload
Vision_RADIO_12.28b.60.140e_26.03.02.26: MegaUpload
Vision_RADIO_12.28b.60.140e_26.03.02.18: MegaUpload
Vision_RADIO_12.28a.60.140e_26.03.02.08: MegaUpload
Vision_RADIO_12.26.60.1301_26.02.00.24: MegaUpload
Vision_TMOUS_RADIO_12.21.60.09b_26.02.01.15 (G2): MegaUpload
Official hBoot Downloads:
Vision_HBOOT_0.85.0005: MegaUpload
Vision_HBOOT_0.85.0002: MegaUpload
Vision_TMOBILE_HBOOT_0.82.0000 (G2): MegaUpload
Installing:
1. Download the archive
2. Decompress it, you'll have a .img file (its name should be "radio.img")
3. Copy it into your fastboot folder
4. Boot your device into FastBoot mode and connect it to your PC via USB
5. Go into your Android SDK folder with CMD (Windows) or Linux terminal
6. Flash the Radio on your device: "fastboot flash radio radio.img"
7. Wait until the process finishes. You should read "COMPLETE" on your device's display.
8. Reboot
9. Enjoy!
Please note that you should flash a new radio only if you really know what you're doing!
NOTE: 26.04.02.17 is known to work on G2 and most probably all the radios are flashable on both G2 and D-Z.
Happy flashing!
-kholk
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App

Hmmm, is there any way to force fastboot in cmd or anything of the sort? or what would it be like dealing with HTC?

Do you have adb? If so, you can flash another radio.
Also you might try putting stock rom on SD. Make sure its named update. Try booting into hboot. You may just not have an image. Hboot will pick up that update and do its thing. Good luck.
Sent from my G2 using xda app

The phone wont let me in hboot. I cant get adb or fastboot to recognize it without hboot right?
EDIT: Only sign of life i get outta the phone is the amber led showing that its charging

mdayjr said:
Do you have adb? If so, you can flash another radio.
Also you might try putting stock rom on SD. Make sure its named update. Try booting into hboot. You may just not have an image. Hboot will pick up that update and do its thing. Good luck.
Sent from my G2 using xda app
Click to expand...
Click to collapse
There is so much fail in that quote lol.

Well sure. Anything is worth a try. Trying to save the man $600. You have a better idea besides bashing my quote?
Sent from my G2 using xda app

wallyhonda said:
The phone wont let me in hboot. I cant get adb or fastboot to recognize it without hboot right?
EDIT: Only sign of life i get outta the phone is the amber led showing that its charging
Click to expand...
Click to collapse
Its bricked... send it back for a replacement. There is no way they can prove its been rooted, modded, or anything else.

mdayjr said:
Well sure. Anything is worth a try. Trying to save the man $600. You have a better idea besides bashing my quote?
Sent from my G2 using xda app
Click to expand...
Click to collapse
The thing is he already said he can't get into bootloader. Its a fail because you can't even read, lol

sino8r said:
The thing is he already said he can't get into bootloader. Its a fail because you can't even read, lol
Click to expand...
Click to collapse
Thing is I read fine. I ask him about adb and I mentioned putting stock rom on sd. Now. Do you have an idea?
And the biggest thing is this, we wouldn't be even trying to help this member if he could read. LOL
Sent from my G2 using xda app

Any advice on returning it to HTC for a replacement? cuz obviously i shouldnt of been doing what caused this to happen. Anyone have any experience getting phones replaced by HTC, specifically bricked phones?

wallyhonda said:
Any advice on returning it to HTC for a replacement? cuz obviously i shouldnt of been doing what caused this to happen. Anyone have any experience getting phones replaced by HTC, specifically bricked phones?
Click to expand...
Click to collapse
Enough is enough. Go through this forum and grab the ruu radio from football for desire z. I believe this is the only way you are going to break brick. Once you have the file, be on the page with ruu , pull your batt, hook up your phone to pc, hit ruu and wait for it to recognize your phone. If it doesn't, it should give you instructions on what to do. This is the only chance you have I believe.
Sent from my G2 using xda app

sino8r said:
Its bricked... send it back for a replacement. There is no way they can prove its been rooted, modded, or anything else.
Click to expand...
Click to collapse
He bricked it with the radio file. All the os info is still on the phone. Htc will know. These guys went to school for this stuff. Don't be so sure of yourself. There are techs that can pull info from a device that has been underwater so don't think they won't be able to tell. They will go through the phone to find out why it bricked or won't boot and then it will sit with the refurbs after they have put stock os back on that comes with radio file.
Sent from my G2 using xda app

Annnnd in the meantime before they figure all that out, will they send me a new one you think?

One of the first questions a tech will ask you is "did you root the phone?" And unless you purchased that phone directly from htc, you have to deal with your carrier and they wiill tell you that. Real thing is this, you have a nice $600 paper weight. Good luck.
Sent from my G2 using xda app

At that point do i just play dumb lol? As pathetic as it sounds, just until the point they send me a new unit or something. I mean they already told me to deal with the manufacturer. I just dont know what extent they"re going to take with it, ya know. Thanks alot for your time too.

mdayjr has no idea what he is talking about. I'm not meaning to sound insulting but you are simply wrong. He can not overcome this. You are bricked, very simple. The only way to overcome a TRUE brick is with JTAG which I'm sure is unknown how to do on a G2 as of now.
If you have insurance, call your carrier and tell them it just started acting up. If they ask about rooting at all just play dumb. They will not be able to ever know any different. Scouts honor. The only possible way to do this is very time-consuming, would be expensive if you had to pay for it, and is VERY risky. You think they can unbrick a phone? If they COULD unbrick a phone easily, they wouldn't replace it with a brand new one. They would make you send it in, fix it, and send it back. That's just better for business. Even if they could tell you rooted, you would already have your new phone before they knew and you would still be sitting there with a brand new phone.
Next time you flash a radio follow read to be sure other people with the same phone/SPL have flashed it and confirmed it working. Coming from a MT3G/G1 the most common reason for TRUE bricks is an improper radio or SPL flash.
If you are ever able to get into recovery or fastboot you are fine. Since you are unable to get into either recovery or fastboot your phone is bricked. If you would like to read about what's going on with your phone right now, you can read more here:
http://forum.xda-developers.com/showthread.php?t=655097

mdayjr said:
He bricked it with the radio file. All the os info is still on the phone. Htc will know. These guys went to school for this stuff. Don't be so sure of yourself. There are techs that can pull info from a device that has been underwater so don't think they won't be able to tell. They will go through the phone to find out why it bricked or won't boot and then it will sit with the refurbs after they have put stock os back on that comes with radio file.
Sent from my G2 using xda app
Click to expand...
Click to collapse
Lol! Are you a cell tech? No...
Am I?
Yes... well... was, for many years
No, you moron... they don't check or try and pull any info if it doesn't power on or have liquid or physical damage. They don't use the same recovery software that you use to recover criminal/goverment files on a damaged drive, lol! What a waste of time! They replace the board if it isn't flashable and obviously they can't see the previous build without a functional bootloader. Plus, a damaged radio is enough to brick. Reflashing a radio won't fix it for sure but its worth trying EXCEPT he can't get into bootloader or fastboot!!! Shut up and quit making this guy more confused, please!

wallyhonda said:
At that point do i just play dumb lol? As pathetic as it sounds, just until the point they send me a new unit or something. I mean they already told me to deal with the manufacturer. I just dont know what extent they"re going to take with it, ya know. Thanks alot for your time too.
Click to expand...
Click to collapse
If you can... get a replacement phone from your carrier. Tell them you charged it overnight and it won't power on. Simple as that! Don't listen to that other guy... he has no idea what he is talking about. He means well but is an idiot. He's what we call, in the IT profession, a user that has just enough experience to do some damage, lol! You will be fine... just play dumb. Same deal what I told you with HTC if you get referred there.

[Q] UK, rooted unbranded DHD on 2.2 - will gingerbread change this?

Hi everyone,
I have an unbranded DHD in the UK, and I'm running 2.2. Just did a check for updates and nothing. Any idea when gingerbread will be arriving? And will I lose root and/or radio s-off? I love my root apps a lot Also not really a fan of custom roms atm as I don't have enough time to play with it if it doesn't work as expected straight away.
Also, what will I lose and keep in the update? Contacts? accounts? apps? App data?
Thanks

Tamen said:
Hi everyone,
I have an unbranded DHD in the UK, and I'm running 2.2. Just did a check for updates and nothing. Any idea when gingerbread will be arriving?
Click to expand...
Click to collapse
Already have 3 too many threads about that and don't wish to start another.
Tamen said:
And will I lose root and/or radio s-off? I love my root apps a lot Also not really a fan of custom roms atm as I don't have enough time to play with it if it doesn't work as expected straight away.
Click to expand...
Click to collapse
You'll lose root. If you phone is still in a state that it can receive updates.
if you've rooted why not just flash a GB ROM? There are customised ones and even one that is just rooted.
Tamen said:
Also, what will I lose and keep in the update? Contacts? accounts? apps? App data?
Click to expand...
Click to collapse
Seems people are saying that nothing was lost but back it all up anyway (yes, lots of apps to back up info, all already mentioned).

Thanks for the swift reply - how do I know if my phone can receive updates? I've rooted with visionary and put radio s-off if that helps
The main reason I don't want to flash custom roms is that it starts become a lot more risky - things do go wrong and you see people bricking their phones. If I bricked my phone I wouldn't have a clue how to fix it and I can't afford the £75 excess on insurance to replace it if it couldn't be fixed, as HTC wouldn't replace it if I broke it trying to do root things to it. I've also read that the latest CWM is having problems?

Tamen said:
Thanks for the swift reply - how do I know if my phone can receive updates? I've rooted with visionary and put radio s-off if that helps
Click to expand...
Click to collapse
You should be ok. The actual state you can put a phone to and still receive the update is something I haven't been able to pinpoint yet. Certainly need a stock ROM.
Previous phones needed the stock recovery but I don't think that's the case here.
Tamen said:
The main reason I don't want to flash custom roms is that it starts become a lot more risky - things do go wrong and you see people bricking their phones. If I bricked my phone I wouldn't have a clue how to fix it and I can't afford the £75 excess on insurance to replace it if it couldn't be fixed, as HTC wouldn't replace it if I broke it trying to do root things to it. I've also read that the latest CWM is having problems?
Click to expand...
Click to collapse
The time when you are most at risk of bricking your phone is rooting and flashing a radio.
Flashing a ROM is 99% risk free. You've done the risky bit.

Cheers - though I haven't flashed a radio I don't think (unless radio s-off is flashing a radio). It says in the how to install a rom guide (http://forum.xda-developers.com/showthread.php?t=964996)
- Select "Install Zip from sdcard"
- Select "Choose zip from sdcard"
- Select full-wipe-1-3.zip (It's right under those folders)
- Confirm by selecting the Yes option in between those "NO"s
- Wait for it to finish
- DO NOT REBOOT!!! In case you were not aware, you now have no rom installed
If I somehow messed up or knocked the power button and rebooted, what happens? How do I then fix it? Is that a permanent brick?

Not a fan of that wipe.zip. You could do the less risky method first and use wipe from the recovery menu.
If you rebooted you MAY (unlikely) have a brick but more likely you'll just end up back at bootloader.
If something happens while the phone is installing the ROM then you might have a problem.
If the phone is bricked assume you will have to send it to HTC for repair (along with your best innocent "it was like that in the morning, honest" look.
You'll be fine. I'm sure. But know the risks.
Bottom line, don't knock it. It's quite hard to accidentally press the power button.

Haha claim innocence If they do look and say it's your fault, out of warrenty, how much do they charge? They don't have to replace anything, just presumably connect it to a htc computer and run some resets.
Does the phone stay connected throughout this process? What happens if it's not connected when run or becomes disconnected?
Sorry for all the questions, but I just really want to understand everything that happens. If able I'd much rather update to gingerbread then root with an updated visionary or equivalent, though how long that'll take to happen is anyone's guess :/

Unless the instructions say not to I'd leave it connected.
If the instructions say to remove something that means disconnecting the phone (such as swapping SD cards for example) and doesn't say re-insert the phone then don't (this is why you should always be 100% charged before you try these things).
If it is bricked, they will use there tool to get into the eMMC partition and re-install everything. It's unliekly (not happened yet) they will magically restore the phone and go "hold on, you did this".
Don't worry. Ask away (feel free to hit the thanks button IF I say anything useful).
Just to back track, it looks like your wanting to flash a ROM now. Is this a stock ROm or one of the beautiful customised ROM's like LeeDroid?

In a sec I'll thank every post on this thread, you've been really helpful (and patient!)
I heard about gingerbread updating and wondered if root would be lost with the update or if the update would even work at all. You suggested I get a gingerbread rom already rooted, and I said "aarrgh, I'm scared" The rest of the posts are you explaining things to me, though if possible I'd like to stick with official roms for the moment and then root it - will visionary work on 2.3?

No. You will need to use Gingerbreak which will involve downgrading the ROM first.
But to answer the question between the lines, if you update and lose root, all is not lost, it can be reclaimed.

[noob]But the Rom comes from OTA, so how can it be downgraded?[/noob]
But thanks, if root can be re-attained after the update, I'll wait till after the update before doing anything too fast

What you will have to do is take an old RUU, say version 1.32 and install that.
That then allows you to gain access to the required areas of the phone to give you root and anything else you wish (Engineering HBOOT (ENG S-OFF), Radio S-OFF etc.).
When you get to that stage and decide to root etc. you will kick yourself so hard for not doing it earlier

Oh so gingerbread will remove root but not Eng or radio s-off? I'm at 1.32 at the moment so I should get engineering s off while I still can cause getting root in the future will be easier?

Tamen said:
Oh so gingerbread will remove root but not Eng or radio s-off? I'm at 1.32 at the moment so I should get engineering s off while I still can cause getting root in the future will be easier?
Click to expand...
Click to collapse
It (The OTA GB ROM) will remove root if you already have it yes. I believe Radio S-OFF is safe. AS for ENG S-OFF (HBOOT) I'm afraid my memory is failing me but with root and Radio S-OFF it would be easy enough to redo ENG S-OFF.
Rooting etc. will only get harder with each update. Version 1.32 is the easiest of all to root and in fact most root / Radio S-OFF etc. threads start by saying "downgrade to 1.32"
[EDIT] Just re-read your post...
Yes, if you make plans now before the OTA update (still not convinced you will get it though) it will be easier in the future but the main one to worry about is Radio S-OFF. This is the easier of the two and IIRC the only one required should you get the OTA update and gain root (via GingerBreak) without having to downgrade first.

I had root + radio s-off, just got ENG s-off too in-case it can't be done after the update. Hopefully this means after gingerbread re-rooting will be easy-ish

Tamen said:
I had root + radio s-off, just got ENG s-off too in-case it can't be done after the update. Hopefully this means after gingerbread re-rooting will be easy-ish
Click to expand...
Click to collapse
Puts a huge grin on my face when someone just goes and does this....
But I really really really feel you can't stop now.
Ignoring that I don't think you will get the OTA update you have to now install a GB ROM. After what you have done, flashing a ROM is (relatively speaking) as safe as houses.
Go on!! Android Revolution HD (ARHD) is basically pure stock GB visually with a few goodies thrown in.
Top the day off and flash that ROM.
Do it!!!

Getting ENG s-off was just as simple as getting radio s-off (which I did about a week ago) - I've just heard it's less 'reversable' for if ever you need to go back to stock so had avoided it
The thing with me is that I my brain doesn't really consider things risky or safe based on other people being safe or risky, it's how many places there are to go wrong. One click apps like visionary are relatively safe I just feel a bit daunted by all the steps to flashing a rom. I'll give OTA a chance, but if everyone else on UK unbranded goes "woohoo" and I just sit there like a lemon, I'll maybe start thinking about it
I've got exams coming up (I'm only 15) but if after this week there's no update I'll dedicate a couple of hours to putting a gingersense rom on my phone
What's your preference? And why are there so many no-sense roms? Sense is amazing and is what in my opinion really sets HTC apart - lovely phones with a boosted UI. Why would you ever want to get rid of it?!
EDIT: When flashing a ROM, do you need to factory wipe? Does mybackup root work across roms? I'd like some way of restoring all my contacts, accounts and apps
EDIT2: Something I forgot about earlier; I can't open the compartment to take out my battery, so when there's a solution that says "take out battery, try again", it wouldn't work as I physically cannot take the compartment off to get to the battery. When my phone arrived and I needed to take it off to remove the wrapper on the battery, but I couldn't do it and neither could anyone in my family. So feeling stupid I took it to the orange shop but no luck, so t-mobile, phones4u, O2, carphonewarehouse... loads, none could do it.
One guy told me to take it to a different orange shop and "ask for dean" - so I took it to him and he took it out the back of the shop and somehow did it. He said it just needed force (but clearly an amount nobody before or after him has been able to replicate), and that it was nothing like any other DHD he'd seen as they are usually stiff but do open, this was basically glued. So I better not get into a boot loop that holding down the power button won't fix, as if it's hard to play innocent when it's visibly stuck in a boot loop from custom roms

Tamen said:
Getting ENG s-off was just as simple as getting radio s-off (which I did about a week ago) - I've just heard it's less 'reversable' for if ever you need to go back to stock so had avoided it
Click to expand...
Click to collapse
Nope, just as reversible.
Tamen said:
The thing with me is that I my brain doesn't really consider things risky or safe based on other people being safe or risky, it's how many places there are to go wrong. One click apps like visionary are relatively safe I just feel a bit daunted by all the steps to flashing a rom.
Click to expand...
Click to collapse
Put ROM on sdcard.
Boot to recovery.
wipe data and cache
install ROM
reboot
Get a brew and marvel and the wonderfulness of it all.
With ROM Manager it can be simpler still.
Tamen said:
I'll give OTA a chance, but if everyone else on UK unbranded goes "woohoo" and I just sit there like a lemon, I'll maybe start thinking about it
Click to expand...
Click to collapse
When you start thinking about it install ROM Manager just to get ready.
Tamen said:
I've got exams coming up (I'm only 15) but if after this week there's no update I'll dedicate a couple of hours to putting a gingersense rom on my phone
Click to expand...
Click to collapse
Schedule those hours in now. You WILL be flashing ROMs
Tamen said:
What's your preference? And why are there so many no-sense roms? Sense is amazing and is what in my opinion really sets HTC apart - lovely phones with a boosted UI. Why would you ever want to get rid of it?!
Click to expand...
Click to collapse
Hee hee. I like Cyanogen (a non-sense ROM) - Will come back to that.
My favourite sense ROMs are LeeDroid by a long way, the guy is a star and the ROM is perfection; after that, Android Revolution HD which will probably be your choice as it's closer to stock than Lee's. Based on what you've said I go with ARHD but if you really want to play, have fun (overclocking etc.) and want your phone to make R2D2 noises when it boots then LeeDroid every time.
And you're right, the Sense UI (which only gets better) does set HTC apart but even without it, I'd only buy a HTC phone now (when I'm buying an Android phone).
Why not [email protected]
Two part answer. The first part is I'm a huge open source and Linux fan. Use Ubuntu on PC and Kubuntu on laptop and my first Android phone was THE first Android phone, the Google (T-Mobile) G1. As such I love Android so I want my phone to be just about Android with a few little extras and NO ONE does that better than Cyanogen. NO ONE.
I still have my G1 and I still love it. That's a vanilla Android phone.
Second part is about bloat. Yes, I do really really like Sense UI. As far as manufacturers bloat-ware goes NOTHING beats Sense UI. It's visually stunning and things like htcsense.com, the clock / weather widget that actually shows weather and that cool windscreen wiper thing and the whole seamless integration twix phone and social is beyond words.
But at the end of the day what is it? It's pretty. I don't use facebook. For twitter I prefer Twidroyd and Tweetdeck. I don't need a massive clock on my screen. I don't want apps and widget I'm not going to use. Before I could root my Hero and DHD I installed ADW.Launcher.
I'll tell you what it's about: Choice. I don't want three buttons along the bottom I want five. And because I have a Google Apps account, HTC Picasa add-on doesn't work (they looking into it) and that pisses me off.
I'm prattling on now.
I have LeeDroid and ARHD on my sdcard as NAND backups and every now and then I restore one (I think of it as almost "dual boot") and for the next 24 hours I'm back coo-ing over it all but then 24 hours later it just doesn't feel right so back to CM I go.
It's personal choice but I will say one thing (more), try CM7. If you don't like it fine but just try it. You'll miss the widgets at first but see how you feel about it.
I'll shut up now.

That's great info, cheers I understand why now, but I do like my massive flip-over clock, regardless of how much battery it eats Also, htcsense.com has been a life saver once or twice when I've put it at home under a pile of papers or something and can't find it
ARHD said there were problems with Rom Manager and wiping within it - is that still a problem? Why do some roms need a different radio flashed? What actually is a different radio and why do you get problems with different roms and radios?
How long does it take between putting the rom on the sd card and actually having the rom installed with ROM Manager?
Also, I edited the above post but was doing so after you'd posted this, so I'll put it here too:
EDIT2: Something I forgot about earlier; I can't open the compartment to take out my battery, so when there's a solution that says "take out battery, try again", it wouldn't work as I physically cannot take the compartment off to get to the battery. When my phone arrived and I needed to take it off to remove the wrapper on the battery, but I couldn't do it and neither could anyone in my family. So feeling stupid I took it to the orange shop but no luck, so t-mobile, phones4u, O2, carphonewarehouse... loads, none could do it.
One guy told me to take it to a different orange shop and "ask for dean" - so I took it to him and he took it out the back of the shop and somehow did it. He said it just needed force (but clearly an amount nobody before or after him has been able to replicate), and that it was nothing like any other DHD he'd seen as they are usually stiff but do open, this was basically glued. So I better not get into a boot loop that holding down the power button won't fix, as if it's hard to play innocent when it's visibly stuck in a boot loop from custom roms

Tamen said:
That's great info, cheers I understand why now, but I do like my massive flip-over clock, regardless of how much battery it eats Also, htcsense.com has been a life saver once or twice when I've put it at home under a pile of papers or something and can't find it
Click to expand...
Click to collapse
I made great use of that too, so simple, plress a button on the website and instant ring. An app called Where's my droid can do that but you need another phone to be able to send it a text.
Tamen said:
ARHD said there were problems with Rom Manager and wiping within it - is that still a problem?
Click to expand...
Click to collapse
There used to be but I've never had a problem. But I like doing everything from recovery and that's works fine (from 3.0.2.6).
Tamen said:
Why do some roms need a different radio flashed? What actually is a different radio and why do you get problems with different roms and radios?
Click to expand...
Click to collapse
It's that some ROM's have been tested using certain Radios and some devs are only willing to recommend Radios that have been tested.
A radio is the software that is responsible for wifi, network signal including data, bluetooth and GPS. It's just another something that is constantly being improved. Most radios will work with most roms but one radio might work great for person a and be rubbish for person b. This is because some networks and phone hardware (they do differ) don't respond as well as others to a certain radio. The radio is something you will will push (via fastboot commands) a lot (which is why you have Radio S-OFF) as you need to experiment.
Tamen said:
How long does it take between putting the rom on the sd card and actually having the rom installed with ROM Manager?
Click to expand...
Click to collapse
Depends on ROM but on average about 5 minutes. It's not really any quicker than using recovery directly (ROM Manager is just a GUI for recovery) once you have done it a few times, it's just simpler.
Tamen said:
EDIT: When flashing a ROM, do you need to factory wipe?
Click to expand...
Click to collapse
ALWAYS. And every time.
The only exception is if you're upgrading the same ROM but even then, depending on the upgrade you may still have to wipe. Most issues after flashing a ROM are due to not wiping at least the cache.
Tamen said:
Does mybackup root work across roms? I'd like some way of restoring all my contacts, accounts and apps
Click to expand...
Click to collapse
Yes. Contacts are sync'd to Gmail so no worries there. Mybackup will backup SMS and MMS too.
Apps are a different matter. There is an option to Backup apps and app data to google servers which works 95% of the time. Titanium can do this too but in my experience is even more flakey. I still keep a list of all my apps just in case.
Tamen said:
EDIT2: Something I forgot about earlier; I can't open the compartment to take out my battery, so when there's a solution that says "take out battery, try again", it wouldn't work as I physically cannot take the compartment off to get to the battery. When my phone arrived and I needed to take it off to remove the wrapper on the battery, but I couldn't do it and neither could anyone in my family [snip]
Click to expand...
Click to collapse
That battry door is ****, no two ways about it. It does require a lot of force and you have to be brave with it. But as you say, hopefully you won't need to worry about it.

Looking for PIT files for SM-N910P

I'm looking for the PIT files for Sprint's Note 4. Or does anyone know if the PIT for SM-N910F will work. Is the (F) version compatible in all of the Sprint versions. I.E. when looking for Sprint programs there is no SM-N910(P) but always a SM-N910(F). Is it safe to use the F version? Or is there a safe way to update/redo the bootloaders? I flashed some bad files with Odin right around the BOB7 udate and my device has been spinning in circles around that since. Even if I go full stock and Odin the latest firmware my device is set back to that period from a protected file that is in between bootloaders. I can't touch it. The closest I can get is with a terminal command from TWRP [/sbin/recovery] I can then chmod the files and erase or do whatever with them but they are restored in cold boot. Even after flashing the official firmware it reverts to the files from BOB7. What's really crazy is I'm running stock firmware so can not use xposed but if I mount data and system wipe and then run uberwipe my device will boot with xposed apps functional. It is as if I am running two ROMS one that can not be removed or changed. I can see it happening but not from where exactly. In cold boot it loads the RO biuld from /dev/block/platforms/msm_scc1.by_name/hidden. I can find everything but the hidden. In the stock recovery logs it says the command to fix it is wipe_data_crypto but I can't accomplish it. Any suggestions?

PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk

samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
Yes I'm getting ready to flash bootloaders big AF. I will two the pit files first but if that doesn't work I've got a list. Involves downgrading to kit kat, rooting with auoto root (can't screw me thrice) running triangle away to lose the warranty bit, installing xposed and wanam so as to make it read official. Once samsungs stuff isn't all a scared anymore I delete the /dev/block/platform/msm1_byname/hidden/rape the dumbass that used to trust developers he didn't know until he knew better and the rape was done.
I'm not really looking to flash boot loaders per say. I realized that you can only install a newer version and I TiVo I'm out of updates if I need a new bootloader. Just went to erase the obtrusive piece of poo hidden in between the 2 bootloaders. I'm not even sure theres supposed to be 2 bootladers. I look at samsuny stock firmware it's nothing like the billithera of extra stuff I have on my device. Can't say for sure who caused it because I did some retarded stuff when I was even greener than I am now. But whether it be auto root or srs unlock that super su is obtrusive as it gets. The purpose of root was flee me the user to gain access tip everything. The whole limiting the user and granting permission to every creepy fook on this planet to stock me and my kids is not what I had in mind. These people are so adamant about their creepy stalking not only is my devices esp network cut by 90% they do dangerous stuff like hidden robuilds that has a value of 1 where the radio don't shut off I airplane mode.

samep said:
PIT for Sprint Note 4 is here:
http://www.sammobile.com/forum/showthread.php?p=137840 No links are permitted by the developer; please respect that.
Not experiencing what you have and not attempting to fix what isn't broken, can't say what works but from what you describe, it sounds like you may have attempted to flash an older bootloader which isn't advised.
You may consider it's risky to try to undo that but first verify your reactivation lock is disabled. If your eMMC is OK, it might be OK to try to Odin PIT with repartition and nand erase all with an acceptable tar OG5 or higher loaded in AP slot. Always use PIT for repartition but only use if needed. And use at your own risk.
No guarantee but consider the risk and IF you have an issue with boot after Odin, you may need to factory reset in stock recovery and try the stock tar again (it's important to try that first without panicking). Always power down and pull battery before flashing stock tar. Also make sure you have ample battery charge. These days, 80% is recommended because there's a lot of weak batteries out there. Consider a new battery if older than 12 months or requiring frequent charging or phone shuts down before 0%. (I don't recommend full discharge, just that some batteries start shutting down around 20% when going bad. It only gets worse after that.)
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I appreciate the advice. I hope to avoid allot with the PIT. That's what flashfire back up says it needs. Shutting the phone of is a good idea. The recovery log was actually making fun of me for not. Along with the simple command I needed to open /sbin/recovery then wipe cane and data crypto. The /sbin/recovery was an eye opener (try it from the emulator in twrp to see if root has crippled you. The thing is most of us use a universal supersu update to reinstall and that is not good. That is written to take out the marines if that's what it takes to accomplish root. Remember the food old days when superuser binary was a line compatible with your cu?
Anyways another good command people don't know is if odin fails don't pull the battery. I put am s4 tip sleep forever that way. volumedwn home and power reatart the bootloader and wipe the cache for the software out is rejecting.
Yes I'm getting ready to flash bootloaders big AF. I will two the pit files first but if that doesn't work I've got a list. Involves downgrading to kit kat, rooting with auoto root (can't screw me thrice) running triangle away to lose the warranty bit, installing xposed and wanam so as to make it read official. Once samsungs stuff isn't all a scared anymore I delete the /dev/block/platform/msm1_byname/hidden/rape the dumbass that used to trust developers he didn't know until he knew better and the rape was done.
I'm not really looking to flash boot loaders per say. I realized that you can only install a newer version and I TiVo I'm out of updates if I need a new bootloader. Just went to erase the obtrusive piece of poo hidden in between the 2 bootloaders. I'm not even sure theres supposed to be 2 bootladers. I look at samsuny stock firmware it's nothing like the billithera of extra stuff I have on my device. Can't say for sure who caused it because I did some retarded stuff when I was even greener than I am now. But whether it be auto root or srs unlock that super su is obtrusive as it gets. The purpose of root was flee me the user to gain access tip everything. The whole limiting the user and granting permission to every creepy fook on this planet to stock me and my kids is not what I had in mind. These people are so adamant about their creepy stalking not only is my devices esp network cut by 90% they do dangerous stuff like hidden robuilds that has a value of 1 where the radio don't shut off I airplane mode.

TheMadScientist420 said:
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man
Click to expand...
Click to collapse
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk

I never could find the files. The link was valid, samep, it just refused to let me have them. It turns out it is easier to get them off your own device and I've zero doubt they are for the 32gb Sprint Note 4. At least mine anyways. I tried the down grade to kitkat which would have worked because it downgrades you boatloader at least according to the page. I got a failed md5. So it wouldn't supirise me if these pit files are different than what the stock one was. Hard to tell what you have, for sure, when you are a flash junk that trusts random people on the inter web. At least I was/did. I gave myself this when it was brand new. It was hard to get it going again. I back up worked with plasma kernel then on the next official it was right again, well almost, I've had this problem almost two years now. I went without root for a while so didn't notice.
I
I hope this fixes it. If not I'll find the right files for the kk downgrade. It would be sweet to go back anyways. I'll leave a link in the next thread for the pit.

TheMadScientist420 said:
i dont know the problem seems to have been in a update.. playing with it for a while it started charging and turned on and finished a update....
i got a s6 active did the same thing to me just started working i run it for like 6 months no probs
of coarse its on sprints black list just found out due to non payment of ezpay. but ill deal with that on my own as such talks are downed and frowned upon.
man i got this thing for 20 bucks.... even if nothing else my buddy needs a screen for one in his shop. but most def thank you for responding..
too further your post i do all my own repairs ussually the cheapest route currently behind the wheel of a unrootable verizon note 5 and a lgg4 which is rooted but no twrp method available. each i have very little invested in.
Click to expand...
Click to collapse
Did you fix it? Your right totally worth it for the screen. You can unlock the imei. I only did it once just because some people are so adamant you can't. I like to believe anything is possible. I don't feel bad about getting those non paid because the phone companies are the thieves. Especially in the US. They bury a lot of people locking you down to have a phone and the policy on being to stupid to fix anything is raw. With two kids I paid out a lot of dead phones. It takes rooting one phone to have bested the entire knowledge of tech at sprint. That's the hard part. If they sold parts it would be nothing.
TheMadScientist420 said:
by chance i got one of these thats only in qloader9008 you got any ideas on that i am downloading the debrick img from sammobiles rite now. aint really ever had this issue on a samsung only lgs
thanks in advance man
Click to expand...
Click to collapse
Sent from my SM-N910P using XDA-Developers mobile app

PIT_SM_N910P
https://mega.nz/#!cJREFYqS
Sent from my SM-N910P using XDA-Developers mobile app

planb234 said:
Did you fix it? Your right totally worth it for the screen. You can unlock the imei. I only did it once just because some people are so adamant you can't. I like to believe anything is possible. I don't feel bad about getting those non paid because the phone companies are the thieves. Especially in the US. They bury a lot of people locking you down to have a phone and the policy on being to stupid to fix anything is raw. With two kids I paid out a lot of dead phones. It takes rooting one phone to have bested the entire knowledge of tech at sprint. That's the hard part. If they sold parts it would be nothing.
Sent from my SM-N910P using XDA-Developers mobile app
Click to expand...
Click to collapse
Y3a it just decided it was gonna start workin heck yea.
The battery is trashed on it. Im gonna order one here soon
Ive flashed a few roms on it. Rooted. But everytime i restart it the bat percentage is totally diffrent.. thank you. I got a s6 once same way
Wouldnt do nothing. Plyin with it and decided to boot up.
Again i know talks of bad imeis are not good conversation. But i use cdma workshop and basicly took a old sammy i had that was junk and destroyed it. Took the sticker and rewrite a new iemi. Havent done it yet but. When i get there i know i can.
Ofcoarse now i cant unlock it even if i follow all the guides. Ive tried and tried.

TheMadScientist420 said:
Y3a it just decided it was gonna start workin heck yea.
The battery is trashed on it. Im gonna order one here soon
Ive flashed a few roms on it. Rooted. But everytime i restart it the bat percentage is totally diffrent.. thank you. I got a s6 once same way
Wouldnt do nothing. Plyin with it and decided to boot up.
Again i know talks of bad imeis are not good conversation. But i use cdma workshop and basicly took a old sammy i had that was junk and destroyed it. Took the sticker and rewrite a new iemi. Havent done it yet but. When i get there i know i can.
Ofcoarse now i cant unlock it even if i follow all the guides. Ive tried and tried.
Click to expand...
Click to collapse
There's a couple of ways to calibrate the battery. the easiest is a root app in Play "Battery Calibrator" it resets the stats at 100% Another is *#0228# I believe you calibrate it then let it run all the way dry then charge it to full with the system off. Not too hard to find if you want to give it a shot. It's hard to say what the problem is. I just got a new one because the old was dying at 30%. I use both and they take turns on which one is weak. Neither is a problem with out root. I probably have too much working Or to much stuff in the background.
I've heard that about changing the sticker. i only change the sticker if I used another phone for the screen. It matches what is in the board that way, If you take it in the store to get it activated they may be a little less confused.
I took an S4 that was compiled of 3 previous ones and my daughters that just stoppede working to get activated at sprint. Of course he couldn't. His story the same "When you work on them .. . He was pretty adamant that as it. I couldn't figure out how that affected both of them. So i took it home and activated it myself. Turns out the S4 is a dual band so he generally has a 50% succes rate it will turn on in the mode.
The sticker definitly won't get it activated. I've got an LG3 that was given to me by some who did't care about sprint anymoe that was Imei locked out activated. It was $100 bucks for the server. The server was. It unlocked a s5 also that a jerk sold me was clean. It unlocked it too. It was through verizon so i never activated it. I was trying to flop it to sprint when it disappeard .I unloced my note 4 with it to. The SIM so the APNs aere never locked altough I'm not positve it could have been GTidonetehapp that did it. I did' know what I ws doing, I just like plaing with them. No real reason to unlock a phone you own. Well ther is the hotspot. I'm pretty sure that's how I crumbed up my note and my puter to. I dropped exec files in my win 32 folder and flashed in something with a crazy odin to get my phone unlocked. But again not positive, thier stuff workied so it was just to give my equiment herepes.

planb234 said:
PIT_SM_N910P
https://mega.nz/#!cJREFYqS
My bad. I did not know that there has to be a key for mega. This one should do better.
Fwd: https://www.dropbox.com/sh/b0b3ywj5rbiec7h/AAAUM9TvOLUCDPJXXZTZBd_Ea?dl=0
Click to expand...
Click to collapse

planb234 said:
There's a couple of ways to calibrate the battery. the easiest is a root app in Play "Battery Calibrator" it resets the stats at 100% Another is *#0228# I believe you calibrate it then let it run all the way dry then charge it to full with the system off. Not too hard to find if you want to give it a shot. It's hard to say what the problem is. I just got a new one because the old was dying at 30%. I use both and they take turns on which one is weak. Neither is a problem with out root. I probably have too much working Or to much stuff in the background.
I've heard that about changing the sticker. i only change the sticker if I used another phone for the screen. It matches what is in the board that way, If you take it in the store to get it activated they may be a little less confused.
I took an S4 that was compiled of 3 previous ones and my daughters that just stoppede working to get activated at sprint. Of course he couldn't. His story the same "When you work on them .. . He was pretty adamant that as it. I couldn't figure out how that affected both of them. So i took it home and activated it myself. Turns out the S4 is a dual band so he generally has a 50% succes rate it will turn on in the mode.
The sticker definitly won't get it activated. I've got an LG3 that was given to me by some who did't care about sprint anymoe that was Imei locked out activated. It was $100 bucks for the server. The server was. It unlocked a s5 also that a jerk sold me was clean. It unlocked it too. It was through verizon so i never activated it. I was trying to flop it to sprint when it disappeard .I unloced my note 4 with it to. The SIM so the APNs aere never locked altough I'm not positve it could have been GTidonetehapp that did it. I did' know what I ws doing, I just like plaing with them. No real reason to unlock a phone you own. Well ther is the hotspot. I'm pretty sure that's how I crumbed up my note and my puter to. I dropped exec files in my win 32 folder and flashed in something with a crazy odin to get my phone unlocked. But again not positive, thier stuff workied so it was just to give my equiment herepes.
Click to expand...
Click to collapse
I do my own i jusf activate sim cards the sticker is basicly for my refrance i sell a lot of phones but i keep ones like this for myself. So theres no issues i just swap sims all the time so no need for activations

planb234 said:
I never could find the files. The link was valid, samep, it just refused to let me have them. It turns out it is easier to get them off your own device and I've zero doubt they are for the 32gb Sprint Note 4. At least mine anyways. I tried the down grade to kitkat which would have worked because it downgrades you boatloader at least according to the page. I got a failed md5. So it wouldn't supirise me if these pit files are different than what the stock one was. Hard to tell what you have, for sure, when you are a flash junk that trusts random people on the inter web. At least I was/did. I gave myself this when it was brand new. It was hard to get it going again. I back up worked with plasma kernel then on the next official it was right again, well almost, I've had this problem almost two years now. I went without root for a while so didn't notice.
I
I hope this fixes it. If not I'll find the right files for the kk downgrade. It would be sweet to go back anyways. I'll leave a link in the next thread for the pit.
Click to expand...
Click to collapse
I do believe you have to sign into Sammobile to download files.
The PIT can also be found in the first stock tar for each OS update; the developer I linked says that the PIT hasn't changed. I've seen methods to extract PIT from phone but they don't match md5 when checked. I checked your linked PIT in the post above and it doesn't match either. I wouldn't recommend using that one.
If your phone has ever updated beyond OB7, you can't Odin full stock KitKat tars or OB7 stock tar. The bootloader will block the Odin flash.
Not looking at your phone, it's hard to say what's going on. But I hope the feedback helps. Ask if you have further questions; I'll try to reply, but I haven't experienced what you've having issues with. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk

samep said:
I do believe you have to sign into Sammobile to download files.
The PIT can also be found in the first stock tar for each OS update; the developer I linked says that the PIT hasn't changed. I've seen methods to extract PIT from phone but they don't match md5 when checked. I checked your linked PIT in the post above and it doesn't match either. I wouldn't recommend using that one.
If your phone has ever updated beyond OB7, you can't Odin full stock KitKat tars or OB7 stock tar. The bootloader will block the Odin flash.
Not looking at your phone, it's hard to say what's going on. But I hope the feedback helps. Ask if you have further questions; I'll try to reply, but I haven't experienced what you've having issues with. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yeah it didn't work . It just shut down . I'll explain what has going on. Thank you for this post. It's good to know there's more options.
I actually did take a note 4 and s4 back. It dependes on how they upgraded. The bootloader doesn't change in an fota. I could do the s4 again now.
Thanks again for the awesome info.

TheMadScientist420 said:
I do my own i jusf activate sim cards the sticker is basicly for my refrance i sell a lot of phones but i keep ones like this for myself. So theres no issues i just swap sims all the time so no need for activations
Click to expand...
Click to collapse
You don't have to unlock the SIM or anything? Even if you do that's a lot less than getting the imei forgot about. Don't you have to get an msl from a comany. I know it's very possible send easy in free countries but i live in murica. You pay and pay here and the still put a cap on the data. If we're not careful we may use up all that data and then there would be no way to watch us 24-7 just we might go rogue.
A sticker that changes the sim? Details please.

samep said:
You may have discovered this thread. I haven't had the issue or tried fixing one bricked but marked this thread because of all the theories, examples and links, it seemed a place to start for answers but I couldn't know without experiencing an issue, myself. What works? Don't know.
http://forum.xda-developers.com/showpost.php?p=63848150&postcount=1
It's probably a starting point but nothing new if you've devoted time with success in finding methods to try. It suggests also it could be the eMMC failing which is all too common for Note 4. Either way, if it's just bricked, maybe you recover it. If it's component failure, main board replacement should fix it. Main boards can be found on eBay and Amazon but I think they're all used or remanufactured boards. Samsung repair may be an alternative if you're not to inconvenienced by waiting. Just recently, I got a quote from my local uBreakItIfixIt and the guy said it's not a fixed estimate store to store but he'd only charge $10 to replace a main board in store.
Best wishes for timely procedure or economical repair.
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
I've been trying to reply to this for 2 days. You see it's not the way my phone runs that is the issue it is my network that is completely raped. I can't lose my parasite. I screwed up my bootloader petty bad when I was learning about Samsung. If you ask how to unlock a bootloader the most common answer you get is "you don't, you use auto root". Auto root is as amazing for sure but I can tell there is a lot of people who don't read anything and just do. The the disclaimer is "don't use this with a locked boot loader, you will likely brick your device." As i mentioned I'm a flash junky. I didn't know once you blew the hole in thy boot you only needed a custom recovery forever. I like changing roms so i rooted with it a couple more times. Things for real bad after I ran the kitkat auto root on lollipop. I could use one of my back ups and add plasma kernel for a few months until the next update. Worse than that i flashed a something from an unlock sight with a special version of Odin. I didn't even need to because i had all ready changed the csc to xas so my apns were open. The effects were scary but cool. I got locked out of my phone for awhile except for virtual access on my puter screen. My home network for straight raped after that. I had everything set to home and share because i didn't think there would be even more bored than me so as to waste there life watching my life. There is and they are smart as #. I go in intervals of being angry to amazed. I thought they were gone but no. I was not keen on interweb when i got on here. Now that i could protect myself I can't keep the evil at bay because it lurks in the dark spaces I can't reach. FlashFire says it can remove the seemles. It is incredible to but I don't think so. It definitely can't mine. What's crazy is I've had a couple new bootloaderers since then but it remains. I'm with out root at the moment and am able to look at some of the data and dev were files. I can see the usb files that block adb is in but still no. Even though auto root totally changes the way and where from the device boots, I'm needing to extract or other wise terminate what is probably one card a ftp or smb. I can see in my win logs that if uses a machine to confuse the system in a barrage of security log ins while opening a door for daddy. I had the xml explaing how it's done but then a brand new 125gb card magically went to sleep forever. Some script out there is beyond amazing to me. Virtual net adapters that aren't on top of actual hardware blow my mind. It would have never crossed my mind in a million years they there is going to be a need for antivirus software on hardware like a Bluetooth keyboard.

planb234 said:
You don't have to unlock the SIM or anything? Even if you do that's a lot less than getting the imei forgot about. Don't you have to get an msl from a comany. I know it's very possible send easy in free countries but i live in murica. You pay and pay here and the still put a cap on the data. If we're not careful we may use up all that data and then there would be no way to watch us 24-7 just we might go rogue.
A sticker that changes the sim? Details please.
Click to expand...
Click to collapse
this device had a bad iemi person i got it from said they didnt pay for it on the sprint ezpay.
i checked and that was the truth. so i changed the iemi with another old sammy i had and put the sticker in for my records. so i know what the new iemi is without the device being turned on.
im trying to sim unlock it so i can use it on domestic gsm but no go sofar always invalid sim.
i guess i need to take this dissussion to another thread as so i dont get to far off the orig topic here

@planb234
I'm not following well what you've tried since getting a PIT file. Did you get the PIT file from Sammobile yet? Did you try the latest stock tar? If older ones, which ones fail?
If Odin fails, can you post the log and text on screen?
I believe what you're talking about is not needing to root if flashing a custom ROM. After a stock tar, you could Odin TWRP and flash a custom ROM. Custom ROMs include root and su. If using Chainfire Auto Root for Note 4, make sure to use the right one and latest for Lollipop and Marshmallow. KitKat had its own Auto Root. But the auto root uses a modified stock recovery which may make its use redundant if flashing a custom or even wanting just TWRP for backups if stock rooted.
Some fun facts for you:
The bootloader on Sprint Note 4 is unlocked. Flashing a stock tar will un-root it. Factory reset will cause you to lose systemless root. But flashing a full stock tar successfully will replace the bootloader. If you're trying to flash OB7 or older KitKat stock tar, your bootloader won't be replaced. As far as OTA, it patches existing baseband, bootloader and effected system files and partitions that need patched. Even if it's just a revision number in the update, it gets rolled up to match the update revision. While I feel stock tar updates are full and need no patching, the patching is sequential and should match the Odin'd bootloader and baseband once sequentially rolled up accordingly. So IMO, a patched bootloader is same as newly Odin'd bootloader. I could be wrong about the patching so not necessarily a fact.
I think your problem is unsuccessful flash of full stock tar. A blown eFuse may cause that but from what I've read in past posts of others that had issues back then is that flashing the correct stock tar after full wipe in stock recovery overcomes the flash. It leads me to believe it's only activating reset protection to try to roll the bootloader back to OB7 or KitKat. Maybe I'm wrong but if your phone isn't suffering a hardware issue, you should be able to recover it.
Other bootloaders between OB7 and OG5 like OE1 and OF5 were also exhibiting an inability to downgrade but bootloaders OG5 and up can so far can be downgraded to OG5. I haven't tried downgrading bootloader to OE1 or OF5 though.
I've seen phone info from posters claiming to roll their bootloader back to OB7 or older and they've actually reported a newer bootloader, post OB7.
As far as I know, the only true way to get KitKat ROM to flash and boot is to flash a newer kernel after ROM flash, but prior to initial boot attempt. Currently, I'm only aware of Android 5.1.1 kernel and post OB7 bootloader booting a KitKat ROM after bootloader is updated beyond OB7.
If you're capable of doing otherwise, I'd like to see legit screenshot of phone info or galaxy tools application.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Sent from my SM-N910P using Tapatalk

Develop Bugs

welcome