Database Users

[WARNING] Do not downgrade to 1.0xxxxx after root.

I should of published this notice sooner. This was discussed early on, but we didn't think anyone would downgrade to the buggy firmware after rooting.
We were wrong.
Newer hboots (like the one in stock, hboot version 1.04.0000) flash/check images in an way that prevents the phone from encountering a SECURITY WARNING mid flash. This is good, prevents us from bricking.
Older hboots, like the one in 1.03.605.10 (hboot version 0.95.0000) on the otherhand do not, and flashing over custom firmware with them can lead to the dreaded SECURITY WARNING. This firmware is from January 3rd, is buggy and well should not be used for any reason outside of initail root. Avoid it.
A tester helping develop a one click root encountered this today, he tried to downgrade from custom firmware.
So, do not downgrade below 1.12.605.6 without a reason, if you do understand how to recover. You most likely have no reason to be on old firmware at this point, outside of initial root.
If you have a SECURITY WARNING, don't freak.
Recovering from this error:
Until we have newer RUUs, you only have one maybe two chances to do this. Since you obviously know how to flash an RUU, I am not going to go through the
process again.
Flashing this firmware the stock (1.12.605.6) firmware will fix this error.
LINK: http://www.multiupload.com/JWLPZAS15T
However if you get a MAIN VERSION HIGHER error while flashing, you only have one choice to recover, by flashing the newer than stock (1.12.605.9) firmware.
LINK: http://www.multiupload.com/UF40S2HZA7
If you are having issues, or are freaked out come find me in the chat (check my signature for a link). If I help you, I expect a donation to the Boys and Girls Club in the name of REWT.
-jcase
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bumpity bump!

hello there i got the exact thing on my TB and i downloaded the files to fix it but i get back a Main Version Older am i doin somethin wrong

you can only flash files that are newer than your firmware. what were you trying to flash,overtop of what, when you got this security warning?

scotty1223 said:
you can only flash files that are newer than your firmware. what were you trying to flash,overtop of what, when you got this security warning?
Click to expand...
Click to collapse
i was trying to flash this [ROM][TH3ORYROM] SHIFTAO5P V1.2X [AOSP/CM7] Eclipse B5 Kernel (8/26/2011) but when i was trying to flash the radio, i wasnt getting any receptions and i tried all four radio listed, so my stupid self thinkin hey let me use the radio PM05IMG from the root process and see if that would work, well as soon as the bootloader started flashin the files it pop back into bootloader with the security warning, i tried the file the jcase said to use to get out of that problem but the file never open or go thru it come back saying Main Version Older file not updated.

"Main version higher" means that the firmware you're trying to flash is older than the firmware on the phone.
Have you tried both files above? If so,the next thing I would do is try and flash the mr2 ruu(1.70.605.0) it is newer than both files above,and both of the root files(downgrade and mr1 upgrade) so that one should work for you.
Afterward,you can run revolutionary to reroot and not encounter this prollem again when you flash something that you should have researched more before flashing.
Sent from my SHIFTAO5P using XDA Premium App

scotty1223 said:
"Main version higher" means that the firmware you're trying to flash is older than the firmware on the phone.
Have you tried both files above? If so,the next thing I would do is try and flash the mr2 ruu(1.70.605.0) it is newer than both files above,and both of the root files(downgrade and mr1 upgrade) so that one should work for you.
Afterward,you can run revolutionary to reroot and not encounter this prollem again when you flash something that you should have researched more before flashing.
Sent from my SHIFTAO5P using XDA Premium App
Click to expand...
Click to collapse
Hey there Scotty i really appreciate you helping me out here, im sitting at work with my TB stuck in Bootloader, getting ready to bust out my old rooted Eris out, but ima go and try that MR2 RUU do you have a link to where i can download that. and also where you said Main Version Higher mines Said Main Version Older,
and yes i thought i did everything correctly i mean i guess since i had the rom flashed but wasnt getting any reception made me make the stupid mistakes, by the way scotty do you have a tb

i have never seen "main version older" but it means the same thing... the firmware youre trying to flash is older that what is on the phone.
you can download MR2 from here: http://forum.xda-developers.com/showthread.php?t=1160286
just put your sd card in a cardreader to transfer and rename PG05IMG and flash in hboot. let us know how it goes.
and yes,i have a TB.

scotty1223 said:
i have never seen "main version older" but it means the same thing... the firmware youre trying to flash is older that what is on the phone.
you can download MR2 from here: http://forum.xda-developers.com/showthread.php?t=1160286
just put your sd card in a cardreader to transfer and rename PG05IMG and flash in hboot. let us know how it goes.
and yes,i have a TB.
Click to expand...
Click to collapse
Ok ima download it but my other prblem is that the phone doesnt charge the battery its not enough voltage to run the files, i have no other way of charging the phone i might have to buy a battery charger or somethin

only thing i know of is to use an external charger,or swap it into a good TB. if you have to,you could take it to a store and see if they will put it in a phone and charge it for you,tho i would take some care in what you tell them as to why you need to do that
i got an external charger and 3 extra generic batterys on ebay for about $30 so i wont ever ben in that situation. i dont like charging my phone during the day so i just go until it shuts off then put in a new battery.
ive heard of people hacking up usb cables to directly power the phone,but thats not something id really reccomend.
at any rate youre good to be caustious,an hboot flash is NOT a time that you want to run out of battery

take an old pair if headphones and strip them til you have only the cooper wire and connect them to the gold connector from your phone to your eris battery and that should work

scotty1223 said:
only thing i know of is to use an external charger,or swap it into a good TB. if you have to,you could take it to a store and see if they will put it in a phone and charge it for you,tho i would take some care in what you tell them as to why you need to do that
i got an external charger and 3 extra generic batterys on ebay for about $30 so i wont ever ben in that situation. i dont like charging my phone during the day so i just go until it shuts off then put in a new battery.
ive heard of people hacking up usb cables to directly power the phone,but thats not something id really reccomend.
at any rate youre good to be caustious,an hboot flash is NOT a time that you want to run out of battery
Click to expand...
Click to collapse
Ok so today i brought an HTC dock charger with a extra slot to charge the battery alone, so i charge that puppy up, put the battery back in with the file you gave me to put on my sd card and bootloader comes on does its checking the file and loaded the update ask me to press yes and BAM it took 5 mins to do its process and rebooted itself and now back to where it was when i first brought it, damn so thx you Scotty for the help and guide, so can youo tell me a method to use to root it back,

good,glad it worked out for you. use this to reroot: http://revolutionary.io/
its quick and easy and leaves you with a permanet hboot that wont accidentally get overwritten

scotty1223 said:
good,glad it worked out for you. use this to reroot: http://revolutionary.io/
its quick and easy and leaves you with a permanet hboot that wont accidentally get overwritten [/QUOTED]
do i need my pc to do this root process or i can do it on the phone.
Click to expand...
Click to collapse

portebr3 said:
do i need my pc to do this root process or i can do it on the phone.
Click to expand...
Click to collapse
you will need a pc

scotty1223 said:
you will need a pc
Click to expand...
Click to collapse
Ok ill need a pc, how will i know im rooted will it give me the superuser app like the other root method does

theres a video here on android forums: http://androidforums.com/thunderbolt-all-things-root/402115-thunderbolt-rooting-methods-updated.html
it will give you a permanent s-off hboot and flash clockwork recovery. tehre is a download for a superuser.zip that you will flash in recovery. then you will see the superuser app in your drawer after flashing that .zip/

scotty1223 said:
theres a video here on android forums: http://androidforums.com/thunderbolt-all-things-root/402115-thunderbolt-rooting-methods-updated.html
it will give you a permanent s-off hboot and flash clockwork recovery. tehre is a download for a superuser.zip that you will flash in recovery. then you will see the superuser app in your drawer after flashing that .zip/
Click to expand...
Click to collapse
ok Ima go go ahead and go that route and i think i should be able to download superuser from the app store, but yeaha ill keep you posted, so tell me what ROM are you using, i heard gingerbread is buggy as hell,

portebr3 said:
ok Ima go go ahead and go that route and i think i should be able to download superuser from the app store, but yeaha ill keep you posted, so tell me what ROM are you using, i heard gingerbread is buggy as hell,
Click to expand...
Click to collapse
the market will only have the superuser app,youll need the matching binary files. the superuser app is linked on revolutionarys page,you must flash that in recovery to become rooted.
from: the revolutionary website:
Does Revolutionary give me root?
No. You will need to flash this this zipfile from recovery.

jcase said:
I should of published this notice sooner. This was discussed early on, but we didn't think anyone would downgrade to the buggy firmware after rooting.
We were wrong.
Newer hboots (like the one in stock, hboot version 1.04.0000) flash/check images in an way that prevents the phone from encountering a SECURITY WARNING mid flash. This is good, prevents us from bricking.
Older hboots, like the one in 1.03.605.10 (hboot version 0.95.0000) on the otherhand do not, and flashing over custom firmware with them can lead to the dreaded SECURITY WARNING. This firmware is from January 3rd, is buggy and well should not be used for any reason outside of initail root. Avoid it.
A tester helping develop a one click root encountered this today, he tried to downgrade from custom firmware.
So, do not downgrade below 1.12.605.6 without a reason, if you do understand how to recover. You most likely have no reason to be on old firmware at this point, outside of initial root.
If you have a SECURITY WARNING, don't freak.
Recovering from this error:
Until we have newer RUUs, you only have one maybe two chances to do this. Since you obviously know how to flash an RUU, I am not going to go through the
process again.
Flashing this firmware the stock (1.12.605.6) firmware will fix this error.
LINK: http://www.multiupload.com/JWLPZAS15T
However if you get a MAIN VERSION HIGHER error while flashing, you only have one choice to recover, by flashing the newer than stock (1.12.605.9) firmware.
LINK: http://www.multiupload.com/UF40S2HZA7
If you are having issues, or are freaked out come find me in the chat (check my signature for a link). If I help you, I expect a donation to the Boys and Girls Club in the name of REWT.
-jcase
Click to expand...
Click to collapse
all multiupload.com links are non-functional and should be disabled, and refreshed with current mirror links.

Errors in /cache/recovery -- Bricked????

Yesterday, it randomly started force closing all apps repeatedly (force close loop) and often freezing until the battery was pulled. It would work fine after powering on for 30-60 minutes at a time but then start messing up again. Sometimes it messed up right away though.
Today I made a nandroid backup and then tried wiping data/factory reset and wiping cache. I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know that is not good. But what does it mean??
---
Anyway, now no matter what ROM I flash (CM7.0.0, or an old nightly 37, 41, etc), I click "Reboot system now" and the screen just goes to black forever. I have to pull the battery again.
But then it freezes at the MyTouch 4G screen (left it for 10+ minutes). It never gets past that.
Yes, I even did a nandroid backup before wiping. But even restoring that does the same thing: it restores, I click reboot, and it goes to a black screen.
But no matter what, after a battery pull, it just freezes at the MyTouch 4G screen forever.
I *can* get into the white hboot/fastboot screen via Power + Volume Down and then get into CWM Recovery from there.
It just can't *boot* into any Android rom.
Am I bricked?? Is there a way to fix this??
Please help!

Everyone that i am aware of that has encounter this has not been able to recover from it.
It looks like it might be truly bricked.

Do u have the good emmc chip or bad? Theres plenty of threads regardin that issue...
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.4

Yup it looks like your eMMC chip went bad. I have a phone here that is doing the same exact thing. I have tried everything from fastbooting a new bootloader to the PD15 whatever its called full restore image. Nothing is working at all. I fear you have a truly bricked phone.

Ah [email protected]#!#[email protected]#[email protected]#$!$ !!!!!
A) What could have caused this?? From my viewpoint, of course it seems totally random but from reading other people's cases, have you guys seen any common link or can think of something that could have caused this?
[Edit] And B) Also, do you think T-Mobile would warranty replace it even though it is rooted with CyanogenMod 7 (even though it cannot be seen)? It was purchased Oct 2010, and I do have insurance on it.

Paul22000 said:
Ah [email protected]#!#[email protected]#[email protected]#$!$ !!!!!
A) What could have caused this?? From my viewpoint, of course it seems totally random but from reading other people's cases, have you guys seen any common link or can think of something that could have caused this?
[Edit] And B) Also, do you think T-Mobile would warranty replace it even though it is rooted with CyanogenMod 7 (even though it cannot be seen)? It was purchased Oct 2010, and I do have insurance on it.
Click to expand...
Click to collapse
once they see Clockwork ROM manager they'll know it was rooted.

cmdmilitia13 said:
Do u have the good emmc chip or bad? Theres plenty of threads regardin that issue...
Mytouch 4g-white
Permrooted s-off
Root Method-gfree
CWR-3.0.2.4
Rom-Royalginger v2.1
Kernel-Ckisgen~smartass~v1.4
Click to expand...
Click to collapse
How do I check?

neidlinger said:
once they see Clockwork ROM manager they'll know it was rooted.
Click to expand...
Click to collapse
Well, A) that's only if they press Volume Down + Power button. Do they normally know how to do that?
Also, B) is there a way to remove CWM?

Paul22000 said:
How do I check?
Click to expand...
Click to collapse
you have to be able to get into recovery.
http://forum.xda-developers.com/showpost.php?p=13834944&postcount=1

neidlinger said:
once they see Clockwork ROM manager they'll know it was rooted.
Click to expand...
Click to collapse
I have heard of people frying their motherboards by over volting the charging port so they no longer turn on before sending it in for a warranty return. I cant comment on this but if I can get mine warrantied that way I will do it. Not like the motherboard is any good now so might as well try. However! I do not suggest doing this.

Paul22000 said:
Well, A) that's only if they press Volume Down + Power button. Do they normally know how to do that?
Also, B) is there a way to remove CWM?
Click to expand...
Click to collapse
I'm sure they check first thing.
technically you could if you have the .85 hBoot.
But if you have the .85 hBoot they'll know the phone was tampered with since the engineering screen is different

neidlinger said:
you have to be able to get into recovery.
http://forum.xda-developers.com/showpost.php?p=13834944&postcount=1
Click to expand...
Click to collapse
Unfortunately, I'm not able to use adb even though I have it installed:
What am I missing here to get adb working?
In case I can't get that working, do any of these help to see if my emmc is bad?

Paul22000 said:
Unfortunately, I'm not able to use adb even though I have it installed:
What am I missing here to get adb working?
In case I can't get that working, do any of these help to see if my emmc is bad?
Click to expand...
Click to collapse
to get the phone working again? nope. To get it to an honest warrant-able state yes.

I was able to check the eMMC chip version on my bricked phone so you should be able to also. You need to be in clockwork recovery to do it.

neidlinger said:
to get the phone working again? nope. To get it to an honest warrant-able state yes.
Click to expand...
Click to collapse
Yes, at this point I don't care about getting this phone working. I have been paying for insurance every month since October, so getting it replaced is fine by me.
I just want to know how to get the phone in a state so that T-Mobile doesn't deny my warranty because I put CyanogenMod on it.
How do I get to back to a warrant-able state? That would be AMAZING. Any would would be MUCH appreciated!

Paul22000 said:
Yes, at this point I don't care about getting this phone working. I have been paying for insurance every month since October, so getting it replaced is fine by me.
I just want to know how to get the phone in a state so that T-Mobile doesn't deny my warranty because I put CyanogenMod on it.
How do I get to back to a warrant-able state? That would be AMAZING. Any would would be MUCH appreciated!
Click to expand...
Click to collapse
it's pretty much impossible at this state. If you have the .85 hBoot you could flash the stock image. but you need a working rom to flash back to .86 hBoot. When you do not have.

neidlinger said:
it's pretty much impossible at this state. If you have the .85 hBoot you could flash the stock image. but you need a working rom to flash back to .86 hBoot. When you do not have.
Click to expand...
Click to collapse
Wait? I thought you said I could get it back to warrant-able state in your last post? Did I misunderstand what you said?
Either way, is there a way to just get rid of CWM?
If I can do that, then the *ONLY* way for them to tell I did anything would be the hboot version at the top, correct?
I would be willing to try going to multiple T-Mobile stores and hoping to find someone that didn't know about hboot versions.
So as long as I can get rid of CWM, I will be confident enough to go to multiple T-Mobile stores in order to TRY to get a replacement.
Is there a way to get rid of CWM on a bricked phone?

Paul22000 said:
Wait? I thought you said I could get it back to warrant-able state in your last post? Did I misunderstand what you said?
Either way, is there a way to just get rid of CWM?
If I can do that, then the *ONLY* way for them to tell I did anything would be the hboot version at the top, correct?
I would be willing to try going to multiple T-Mobile stores and hoping to find someone that didn't know about hboot versions.
So as long as I can get rid of CWM, I will be confident enough to go to multiple T-Mobile stores in order to TRY to get a replacement.
Is there a way to get rid of CWM on a bricked phone?
Click to expand...
Click to collapse
i did say to get it to a warrant-able state you need ADB up and running. But there lies a problem when, and i mentioned, it will not get the phone working again.
you need two things 1) a stock recovery image 2) to flash the stock .86 hBoot.
If you have the engineering hBoot, .85 you can flash the stock recovery image. Just has you would flash clockwork via hBoot. but to get back to the stock .86 hBoot you need to have the phone up and running. Which you cannot do at this point. You are correct the only way they would tell if it's been tampered with is the .85.xxxxx hBoot version at the top of the screen.
If you have the .85 hBoot you could try flashing the stock recovery image to the phone and see if that will overwrite CWM.

neidlinger said:
i did say to get it to a warrant-able state you need ADB up and running. But there lies a problem when, and i mentioned, it will not get the phone working again.
you need two things 1) a stock recovery image 2) to flash the stock .86 hBoot.
If you have the engineering hBoot, .85 you can flash the stock recovery image. Just has you would flash clockwork via hBoot. but to get back to the stock .86 hBoot you need to have the phone up and running. Which you cannot do at this point. You are correct the only way they would tell if it's been tampered with is the .85.xxxxx hBoot version at the top of the screen.
If you have the .85 hBoot you could try flashing the stock recovery image to the phone and see if that will overwrite CWM.
Click to expand...
Click to collapse
A) So just to make absolutely sure. Even with ADB, there's 0% chance of ever getting this phone booting into Android again, correct?
B) If so, well replacement is the only opton. So from the pictures above in post #12, I have 0.85, yes?
C) So I just need to flash the stock recovery image from CWM to overwrite CWM?
D) If all three are correct, then which file do I need to flash? Is is one of the two files listed here? http://forum.xda-developers.com/showthread.php?t=843289

Paul22000 said:
A) So just to make absolutely sure. Even with ADB, there's 0% chance of ever getting this phone booting into Android again, correct?
B) If so, well replacement is the only opton. So from the pictures above in post #12, I have 0.85, yes?
C) So I just need to flash the stock recovery image from CWM to overwrite CWM?
D) If all three are correct, then which file do I need to flash? Is is one of the two files listed here? http://forum.xda-developers.com/showthread.php?t=843289
Click to expand...
Click to collapse
a) with adb up and running you can flash the stock recovery image, but not the old school hBoot
b) i am at work and WebSense blocks alot of images.
c) yes
d) depends on if you had the pre or post OTA recovery image.

[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions

[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions
This is a guide on how to go from Froyo to rooted Gingerbread. Also, I'm on AT&T. Others beware. I take no responsibility if you hard or soft brick your phone.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
I didn't actually discover or develop any of this, but I figured someone might like to have a comprehensive guide, instead of searching through 500 different threads like I did.​Known/potential issues:
- Fingerprint scanner not functional False alarm
- Avoid using RSDLite for *anything* if you installed the OTA 2.3.4 build
- Battery reading is sometimes inaccurate
- If you have a limited RAM issue, read here http://forum.xda-developers.com/showthread.php?t=1169409​Step 0 - BACK UP EVERYTHING. Use Titanium backup, or just copy everything off your phone, whatever. This will leave you with an unlocked, rooted, but otherwise stock Motorola phone. Once this is done, set your USB mode to "None"
Step 1 - Install moto drivers
For x64 windows, use these: http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
For x32, http://www.multiupload.com/QNFILE4F07 (I havent tested these, I run Win7 x64)
Step 2 - Unlock your bootloader Note: some have hard bricked using RSDLite to install 1.8.3 over 4.5.91. Read warning here: http://forum.xda-developers.com/showthread.php?t=1160408
Download latest moto-fastboot from here: http://forum.xda-developers.com/showthread.php?t=1138092 *the win32 version worked for me, and I run 64bit windows 7*
Follow instructions here: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Step 3 - Flash stock Gingerbread image (you can do this without restarting your phone from the unlock bootloader step)
Follow instructions here: http://forum.xda-developers.com/showthread.php?t=1163342
Step 4 - Flash CWM Recovery
Instructions here: http://forum.xda-developers.com/showthread.php?t=1138541
Step 5 - Install root
Instructions here: http://forum.xda-developers.com/showthread.php?t=1159572
Note: I used my phone's USB Mass Storage mode to put the .zip on my external SD card. To get to recovery mode, shut down the phone. Then hold the power and volume up buttons until you see "fastboot." Use the volume down key to cycle through until you see "Android Recovery" then press volume up again. This will get you into the CWM environment, where you can navigate the menus to install the root .zip.
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.​
Feel free to make any corrections, or ask questions. Hopefully someone finds this useful. All credit to the OP of each thread I linked to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nice for you to localize everything, ATT users will be grateful.

I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
Click to expand...
Click to collapse
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.

From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.

humjaba said:
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
Click to expand...
Click to collapse
I didn't either. I downloaded a .zip and installed via stock recovery from a thread in the General Atrix forum.

Deggy said:
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
Click to expand...
Click to collapse
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.

Magnetox said:
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Click to expand...
Click to collapse
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?

Deggy said:
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Click to expand...
Click to collapse
What firmware did you flash? Can you link me to the thread you downloaded from?

Magnetox said:
What firmware did you flash? Can you link me to the thread you downloaded from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1159604

Deggy said:
http://forum.xda-developers.com/showthread.php?t=1159604
Click to expand...
Click to collapse
Ah you have the deadly firmware
You simply cannot use RSD to flash down to 1.83 or 1.26 etc.
Or you will brick.
Clarify in Q&A, make your own thread with your question.
Taken from this thread kennethpenn said:
"What if I already flashed the official 4.5.91?
If you flashed the official update from XDA or by downloading through a dev-blur server (note: this excludes this ROM), you should avoid flashing SBF files in RSD Lite. We've confirmed this problem exists when users flash the 1.8.3 build specifically. It may happen with other SBF files, though."
So it looks like you can flash 2.3.4 builds via CWM. But double check by asking in Q&A.

Check out this thread.
http://forum.xda-developers.com/showthread.php?t=1163009
Fruit cakes basically dont touch your bootloader, they're basically modified sbf files that only contain the needed files to flash stuff. There's a 1.8.3 fruitcake in there as well as a 2.3.4 fruitcake.
An HKTW fruitcake is in development.
Fruitcake is the .sbf equivalent file that is flashable via CWM.

The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer

theres the moto-fastboot file i was looking for!
much appreciated.

Now there's a guide
I just did this like 3 hours before this guide came out. Though it at least seems like I was going to all the right threads that are in this guide anyways.

humjaba said:
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
Click to expand...
Click to collapse
From my understanding, if you flashed the official firmware of death you CANNOT use RSD in any way. All of your flashing has to be done via CWM and fruitcakes. Full .sbfs will brick your phone. Hard brick. As in #@$% ME hard brick.

humjaba said:
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Click to expand...
Click to collapse
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.

So I guess no sweet Roms for me. Still haven't found a good thread to root my phone. I'm not sure if the FOD would mess with the rooting part of it.

SoberGuy said:
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
Click to expand...
Click to collapse
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.

humjaba said:
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
Click to expand...
Click to collapse
Perhaps it was settings then and not apps. Appreciate the information. I'll be doing that tonight

after i unlocked the bootloader
i flashed CWM
then i use CWM to flash 2.3.4 GB beta 4 zip from kenn
i like it better my way

Help, Phone is stuck on the myTouch 4G screen!

Hi guys, I bought a 'bricked' phone on eBay, thinking it would be easy to fix it. Apparently not. I read the 'If you think your HTC Glacier is bricked' thread already. I have no idea of the history of the phone. I took it apart, and it has no water damage. The phone boots into hboot OK and is S-ON. I put the PD15IMG.zip on the SD card. However, the bootloader isn't showing the message that it is looking for this file. I've flashed the same PD15IMG.zip on another phone, so I know what I'm doing and the zip isn't corrupt. I'm not sure what SIMLOCK is supposed to do, but it shows 'SD init fail !!!' when I try it. So I was thinking that maybe the SD card reader was bad. I swapped it out with another working SD card reader from a working phone. Same problem still. I also tried factory reset, but the phone freezes at the white MyTouch 4g screen when it reboots. So maybe the motherboard is bad?
Can anyone think of anything else to try before I use this thing for parts? Thanks.

Hmm.. Somehow I got it to recognize the PD15IMG.zip. I think I plugged the USB cable into my laptop, pulled the battery, then disconnected the USB cable, then replaced the battery, and when it booted it found the file this time. I'm flashing it now. Wish me luck.

UPDATE: After flashing PD15IMG.zip, it's still locking up on the white MyTouch4G screen. Here is the output of the update:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?

firesnatch said:
Hmm.. Somehow I got it to recognize the PD15IMG.zip. I think I plugged the USB cable into my laptop, pulled the battery, then disconnected the USB cable, then replaced the battery, and when it booted it found the file this time. I'm flashing it now. Wish me luck.
Click to expand...
Click to collapse
ah yes, i should add that... lmao
good luck man.
find me if you need any help. pm should be fine.
EDIT: um press the power button to reboot

saranhai said:
EDIT: um press the power button to reboot
Click to expand...
Click to collapse
Yeah, of course I did that. When it reboots it locks up MyTouch4G white screen again.

firesnatch said:
Yeah, of course I did that. When it reboots it locks up MyTouch4G white screen again.
Click to expand...
Click to collapse
hm... :/
well try flashing it again i guess...
also try flashing the 2.3.4 version, since from what i see, you flashed the 2.2.1 one correct?

How long are you giving it? A first time boot on sense can take 10 minutes.
Sent from my HTC Glacier using XDA App

saranhai said:
hm... :/
well try flashing it again i guess...
also try flashing the 2.3.4 version, since from what i see, you flashed the 2.2.1 one correct?
Click to expand...
Click to collapse
Yeah, I flashed the 2.2.1 image I believe. Tried it 3 times now. Still sticks on the MyTouch4G white screen. I've waited 10-15 minutes before giving up.
I just flashed 2.3.4. Same problem. Here is a shot of the phone just prior to the reboot:
FYI, the Android 2.3.4 PD15IMG.zip in your post here doesn't pass the Image check when trying to flash. It is size 306,558 KB. I instead used the one from this post here, which is 322,694 KB and passes the check + flashes.
Any other ideas? Am I bricked?
Happy New Year everyone!

estallings15 said:
How long are you giving it?
Click to expand...
Click to collapse
Let it sit for 45 minutes just now. Definitely hung.

firesnatch said:
Let it sit for 45 minutes just now. Definitely hung.
Click to expand...
Click to collapse
Hmm, is it still under warranty? Sounds like it might need replaced. . . That's really strange that a PD15IMG.ZIP successfully flashes (according to the bootloader), but refuses to reboot properly. The only thing I can suggest is to try a few more times, then call T-mobile.
EDIT: Nevermind. You bought it on ebay. Hmm. Paperweight?
Sent from my HTC Glacier using XDA App

how much did u buy it for?

comc49 said:
how much did u buy it for?
Click to expand...
Click to collapse
$75 shipped. Oh well

firesnatch said:
$75 shipped. Oh well
Click to expand...
Click to collapse
You could try manually flashing new hboot as it could be that that is corrupted and it believes its flashing it correctly when in reality it's corrupting the partitions try going to the "flashing the eng h-boot" thread in dev section and I believe there is the stock hboot, try flashing that through ADB, I would hope if you're smart enough to disassemble and switch hardware parts you'd be familiar with adb/fastboot commands but let me know if you need help this could be as simple as that although it could be the eMMC but you would usually get the fail PU error which is when the partition update fails (PU). Good luck and let me know!

Nicgraner said:
You could try manually flashing new hboot as it could be that that is corrupted and it believes its flashing it correctly when in reality it's corrupting the partitions try going to the "flashing the eng h-boot" thread in dev section and I believe there is the stock hboot, try flashing that through ADB
Click to expand...
Click to collapse
Thanks for the tip. Unfortunately the phone is S-ON, so I don't think I can flash the engineering hboot. Let me know if there is a way with S-ON.

firesnatch said:
Thanks for the tip. Unfortunately the phone is S-ON, so I don't think I can flash the engineering hboot. Let me know if there is a way with S-ON.
Click to expand...
Click to collapse
No, try Re-flashing the stock one as it could've gotten corrupted somehow

I had this happen to me, i turned off the s lock and flash new rom
Sent from my HTC Glacier using XDA App

Have you try root again.?
sent from. my HTC glacier.s-off .xda premium.

I'm having the EXACT problem, and anyone have a detailed guide on how to turn off s lock for a phone in this condition? Most guides only work on a phone that can boot into the system, not for a phone like this.

[Q] Can't get to recovery...

Hi guys,
I'm having trouble getting into CWM recovery. When I try to boot into if from Rom Manager it gives me an error that says, "System software not authorized by verizon wireless". After filling my pants I figured out how to get past that and boot up my phone, but I don't know what to do from here. Any thoughts?
I'm running stock 4.4.2 Rooted
Thanks!

Retail devices can only use safestrap. Developer editions can use custom recoveries. Sounds like youre on a retail device.

waxcatharsis said:
Hi guys,
I'm having trouble getting into CWM recovery. When I try to boot into if from Rom Manager it gives me an error that says, "System software not authorized by verizon wireless". After filling my pants I figured out how to get past that and boot up my phone, but I don't know what to do from here. Any thoughts?
I'm running stock 4.4.2 Rooted
Thanks!
Click to expand...
Click to collapse
bmwh0r3 said:
Retail devices can only use safestrap. Developer editions can use custom recoveries. Sounds like youre on a retail device.
Click to expand...
Click to collapse
Like my buddy @bmwh0r3 stated, sounds like you're on a Retail device.
Check out this thread by @az_biker that walks you through all the things you need to know.

Shaggy Kobain said:
Like my buddy @bmwh0r3 stated, sounds like you're on a Retail device.
Check out this thread by @az_biker that walks you through all the things you need to know.
Click to expand...
Click to collapse
Yes I have a retail version rooted using the towelroot method. So I can just install Safestrap and move on from there?

waxcatharsis said:
Yes I have a retail version rooted using the towelroot method. So I can just install Safestrap and move on from there?
Click to expand...
Click to collapse
Correct. Make sure you grab SafeStrap 3.75B04 and you will be good to go :good:

Shaggy Kobain said:
Correct. Make sure you grab SafeStrap 3.75B04 and you will be good to go :good:
Click to expand...
Click to collapse
Great, I'll try that! Thanks guys!

Success! Only thing is I still need to do the workaround to boot up my phone(hold down home, volume down and power). Once I do that I'm able to boot into recovery or system. Do I need to remove CWM through some further process or is something else causing that?

I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bmwh0r3 said:
I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms
Click to expand...
Click to collapse
I was afraid of that...

bmwh0r3 said:
I would start over. Odin the stock tar and pit files. Root again and follow the instructions in the safestrap thread. Be re device you can only use the touchwiz roms
Click to expand...
Click to collapse
100% agree. Nothing like taking the chance that all is ok, just to get everything set up, issues show their ugly heads, and you end up starting from scratch anyway.
At this point, you're basically at square one, just do it right and save a ton of headaches down the road

az_biker said:
100% agree. Nothing like taking the chance that all is ok, just to get everything set up, issues show their ugly heads, and you end up starting from scratch anyway.
At this point, you're basically at square one, just do it right and save a ton of headaches down the road
Click to expand...
Click to collapse
As I mentioned earlier, I used the towelroot method to get root originally. Can you point me towards a thread that has the most current method to gain root on the Note 3?

waxcatharsis said:
As I mentioned earlier, I used the towelroot method to get root originally. Can you point me towards a thread that has the most current method to gain root on the Note 3?
Click to expand...
Click to collapse
If you're on NC4, towelroot is the most current.

thegamerdarkseid said:
If you're on NC4, towelroot is the most current.
Click to expand...
Click to collapse
Great, so to be clear you recommend unrooting and rooting again?

waxcatharsis said:
Great, so to be clear you recommend unrooting and rooting again?
Click to expand...
Click to collapse
Are you already rooted? Explain fully, are you still trying to use clockwork mod or have you gotten rid of that and trying safestrap?

thegamerdarkseid said:
Are you already rooted? Explain fully, are you still trying to use clockwork mod or have you gotten rid of that and trying safestrap?
Click to expand...
Click to collapse
I have root and safestrap now. I didn't remove CWM I just installed safestrap. It works fine but I am getting an error message that says "system software not authorized" on boot that I have to bypass by pressing volume down, home and power at the same time. It's really a minor inconvenience so I'm not too worried about it but if there's a simple fix I'd like to do that.

waxcatharsis said:
I have root and safestrap now. I didn't remove CWM I just installed safestrap. It works fine but I am getting an error message that says "system software not authorized" on boot that I have to bypass by pressing volume down, home and power at the same time. It's really a minor inconvenience so I'm not too worried about it but if there's a simple fix I'd like to do that.
Click to expand...
Click to collapse
You really may not want to but it'll be best to start over as there's no telling what kind of problems having clockwork mod on a phone with a locked bootloader might bring down the line. Things may seem okay now with a minor inconvenience but you just never know.

thegamerdarkseid said:
You really may not want to but it'll be best to start over as there's no telling what kind of problems having clockwork mod on a phone with a locked bootloader might bring down the line. Things may seem okay now with a minor inconvenience but you just never know.
Click to expand...
Click to collapse
Alright. I can wipe my phone from safestrap but do you know if that will get rid of CWM also?

waxcatharsis said:
Alright. I can wipe my phone from safestrap but do you know if that will get rid of CWM also?
Click to expand...
Click to collapse
You SHOULD be able to perform a FACTORY RESET / WIPE from Android download, that will return your phone to OEM, unrooted (should remove CWM) and all your peronal files.
Then start the process from scratch, the NC4 Root link in my sig has links to the files you need to get back up and running.
This will give you peace of mind that no 'unknowns' are hanging around waiting to surface...

az_biker said:
You SHOULD be able to perform a FACTORY RESET / WIPE from Android download, that will return your phone to OEM, unrooted (should remove CWM) and all your peronal files.
Then start the process from scratch, the NC4 Root link in my sig has links to the files you need to get back up and running.
This will give you peace of mind that no 'unknowns' are hanging around waiting to surface...
Click to expand...
Click to collapse
Thanks Biker, I was at a function last night and couldn't get back to him.