Related
So, yes - I need to know how to brick my phone beyond repair please....
"Why !?" I hear you ask....
Imagine the situation: Some b*st*rd has stolen your phone . You are never going to see it again... ever... absolutely zero chance of getting it back...
If you had the option to brick it so no one could sell or use it, would you?
Yes, of course you would!!
It's possible to remotely execute any BusyBox/Terminal Command using the application Tasker and I want to know which one would do the most damage!?
Please let me know! "How do I totally brick my phone?"
load a corrupted radio file
ohhh, sorry to hear that. I had the perfect solution if you still had the phone. But um yea I don't take out my phone near any friends. My brother got his vibrant stolen only after 2 weeks.
Didn't mean to mislead! My phone hasn't actually been stolen! But I'm working on security profiles and need to know what the final command should be to end its life....
Can you flash a radio from the Terminal Emulator?
Sent from my HTC Desire using XDA Premium App
This is what I did and I actually got Verizon to give me a re-furb. What it does is bring you to the htc inc white screen then nothing else. Use root explorer go into systems/fonts and change the name on one of the droidsans.ttf files. I think I totally erased the files but changing them should cause the phone to be totally [email protected]#$. I hope this messes up your phone. Lol
skinny jeans piss me off
BIGshot87 said:
This is what I did and I actually got Verizon to give me a re-furb. What it does is bring you to the htc inc white screen then nothing else. Use root explorer go into systems/fonts and change the name on one of the droidsans.ttf files. I think I totally erased the files but changing them should cause the phone to be totally [email protected]#$. I hope this messes up your phone. Lol
skinny jeans piss me off
Click to expand...
Click to collapse
Great, thank you! Shall test and hopefully be able to revert in fastboot?!
skinny jeans piss me off too...
Further to the above, does anyone know if it's possible to disable entering recovery by deleting certain system files?
brandall said:
Further to the above, does anyone know if it's possible to disable entering recovery by deleting certain system files?
Click to expand...
Click to collapse
Flash a stock recovery image to disable flashable recovery. Also renaming a file doesn't make the phone broken, it just doesn't allow it to boot.
Sent from my Hero that never dies! ;D
dastin1015 said:
Flash a stock recovery image to disable flashable recovery. Also renaming a file doesn't make the phone broken, it just doesn't allow it to boot.
Sent from my Hero that never dies! ;D
Click to expand...
Click to collapse
Thanks - I need it to boot - just don't want someone else to be able to wipe and/or flash a custom ROM
I need to read up if there's a way to flash a recovery image from the Terminal...
hmmm...
brandall said:
Thanks - I need it to boot - just don't want someone else to be able to wipe and/or flash a custom ROM
I need to read up if there's a way to flash a recovery image from the Terminal...
hmmm...
Click to expand...
Click to collapse
To flash a recovery image from TE use this if your ROM supports it: flash_image recovery /sdcard/(name of recovery)
An example for me is: flash_image recovery /sdcard/recovery-clockwork-2.5.0.7-heroc.img
Sent from my Hero that never dies! ;D
dastin1015 said:
To flash a recovery image from TE use this if your ROM supports it: flash_image recovery /sdcard/(name of recovery)
An example for me is: flash_image recovery /sdcard/recovery-clockwork-2.5.0.7-heroc.img
Sent from my Hero that never dies! ;D
Click to expand...
Click to collapse
That's brilliant thank you. Do you know if that can be reverted by flashing the custom recovery image again? Or will I lose the ability to do that once I flash back to stock?
Sorry for the questions, this stuff confuses me...
brandall said:
That's brilliant thank you. Do you know if that can be reverted by flashing the custom recovery image again? Or will I lose the ability to do that once I flash back to stock?
Sorry for the questions, this stuff confuses me...
Click to expand...
Click to collapse
As long as you're on a custom ROM that supports flash_image you can flash a recovery image through TE.
Sent from my Hero that never dies! ;D
dastin1015 said:
As long as you're on a custom ROM that supports flash_image you can flash a recovery image through TE.
Click to expand...
Click to collapse
Thanks again - mine does, so sorted
Never thought of using lookout?
Sent from my MB860 using XDA App
makr8100 said:
Never thought of using lookout?
Click to expand...
Click to collapse
Hopefully going way beyond that... see >>here<<
Do you have the information to know whether it's truly been stolen yet? I'd make sure that it's really been stolen and you, for sure, wouldn't get it back before attempting something like this. I definitely wouldn't want to brick my own phone on purpose just to find out I forgot it somewhere...
ChrisDang said:
Do you have the information to know whether it's truly been stolen yet? I'd make sure that it's really been stolen and you, for sure, wouldn't get it back before attempting something like this. I definitely wouldn't want to brick my own phone on purpose just to find out I forgot it somewhere...
Click to expand...
Click to collapse
See the link above Chris. My phone hasn't actually been stolen, but these commands will be a last resort feature of Sherlock Droid.
Agreed, it would be a nightmare to brick it and then find it under the sofa!
Sent from my HTC Desire using XDA Premium App
You shouldn't brick it quite the opposite, the thief should be able to keep using the phone as much as possible but in the mean time the gps should be secretly turned on and photos should be make so you can track the thief or if that fails publish his info and name and shame him
godutch said:
You shouldn't brick it quite the opposite, the thief should be able to keep using the phone as much as possible but in the mean time the gps should be secretly turned on and photos should be make so you can track the thief or if that fails publish his info and name and shame him
Click to expand...
Click to collapse
You are absolutely right godutch, that is the main aim of the profiles to keep booting into the OS at every opportunity, even using fake recovering images (as in a photo of the custom recovery screen) for the splash and boot animation that appear to be the device gathering system information - all the time it will actually be booting with the launcher, notification bar and lock screen etc disabled so not to give it away - once there the priority is to get a GPS fix
However, there will come a point when you've not heard a peep from the device in days and perhaps your insurance (if you have it) have already paid out... In which case, some users will want to execute the remote 'self destruct' command, to make sure the phone will never be usable to anyone else....
Edit: Trying to make the thief provide a valid gmail address and forwarding the new number if the SIM is changed are all in there too!
What if thief changes to SIM that has no data plan or does not enter any wifi area?
I am taking no credit in the release of the OTA files these were from lightningdude and credit goes to him for his efforts to bring these files out. Files size is around 43mb, but I am guessing that it is compressed and when it flashes it uncompresses to 63mb.
Link to original post from lightningdude,
http://forum.xda-developers.com/showthread.php?t=1621431&page=35
DB link from lightningdude
http://dl.dropbox.com/u/21955004/fota.zip
What we know so far it looks like flashing the OTA removes all possibility for root and early signs suggest that the methods for unlocking our bootloaders has been patched. So anyone who OTA's is not able to root and or unlock your BL.
I dont know much about developement of these files and am merely bringing them out to the masses in hopes of some good stuff to come from it, and again dont thank me, thank lightningdude.
DON'T THANK ME, Hit THANKS for lightningdude
Dang, j-greg, I didn't think it needed such bold font.
On-point: Is there any way to actually open this thing? I mean, there's got to be, if our phones update from it, right? There must be a way!
lightningdude said:
Dang, j-greg, I didn't think it needed such bold font.
On-point: Is there any way to actually open this thing? I mean, there's got to be, if our phones update from it, right? There must be a way!
Click to expand...
Click to collapse
I am messing with the files now trying to see if it can uncompressed if it is. And the font is so big because someone already thanked me for the post, and I dont think its right I get the thanks as you were the one who brought them out... I'm just a messenger. So big font to get peoples attention to thank you not me
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
KeiranFTW said:
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
Click to expand...
Click to collapse
My Mom was just saying today how she wants to sue Verizon in a class action for raising fees and what not. Maybe we should all get together and start that badn wagon. Haha.
KeiranFTW said:
I think these are compressed with some sort of compression method, maybe proprietary.
I'm guessing this patches the bootloader.
If so, time we overthrow Verizon. With a lawsuit.
Click to expand...
Click to collapse
I dislike VZjust as much as the next guy, but VZ feels that if you are a subsidized phone with a plan then the phone is not yours until the contract is up. For me i bought my phone off ebay to replace the total crap that is Motorola Droid 2 Global (loved the keyboard, hated the Motorblur and locked BL)
But I agree, VZ is raping everyone who has a wirelss plan with them, but no news here all Carriers do that.
My phone was free so they have no right to say what we can and can't do with our phones
Sent from my R800x using XDA
droidjunkie said:
My phone was free so they have no right to say what we can and can't do with our phones
Sent from my R800x using XDA
Click to expand...
Click to collapse
Free with a 2 year contract or free from someone you knew? If its free from a contract of 2 years to them they own the device for the length of the contract. I am not trying to support VZ, just saying that I have seen attempts (not firsthand) of people trying to sue VZ or other carriers for the same thing and they are always squashed
jgregoryj1 said:
I am taking no credit in the release of the OTA files these were from lightningdude and credit goes to him for his efforts to bring these files out. Files size is around 43mb, but I am guessing that it is compressed and when it flashes it uncompresses to 63mb.
Link to original post from lightningdude,
http://forum.xda-developers.com/showthread.php?t=1621431&page=35
DB link from lightningdude
http://dl.dropbox.com/u/21955004/fota.zip
What we know so far it looks like flashing the OTA removes all possibility for root and early signs suggest that the methods for unlocking our bootloaders has been patched. So anyone who OTA's is not able to root and or unlock your BL.
I dont know much about developement of these files and am merely bringing them out to the masses in hopes of some good stuff to come from it, and again dont thank me, thank lightningdude.
DON'T THANK ME, Hit THANKS for lightningdude
Click to expand...
Click to collapse
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
netizenmt said:
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
Click to expand...
Click to collapse
Can you PM me a Nandroid backup of this?
Did a baseband update come with this?
Leraeniesh said:
Can you PM me a Nandroid backup of this?
Click to expand...
Click to collapse
oohh, that would be awesome...... net.... got lucky. But in a good way.
netizenmt said:
Hey, maybe it's because my BL was unlocked with the testpoint method, but I still have full root. I returned to stock with the .88 ftf file and then rooted it. I ran tha OTA Rootkeeper also. Once the FOTA was finished, I checked and I still have root without even touching the OTA Rootkeeper program. I ran Root Checker, and it verified I have full root access as well.
Click to expand...
Click to collapse
I'm also rooted on 2.3.4 but with locked bootloader. Same method of flashing as you minus the ota rootkeeper.
Sent from my R800x using xda premium
kelvenha55 said:
I'm also rooted on 2.3.4 but with locked bootloader. Same method of flashing as you minus the ota rootkeeper.
Sent from my R800x using xda premium
Click to expand...
Click to collapse
Any chance you can make a nandroid backup? And if so post a download link for it here so Devs can browse its files?
You can try and fastboot recoveryplay.img and do a nandroid, dont need an unlocked BL for that.....
jgregoryj1 said:
Any chance you can make a nandroid backup? And if so post a download link for it here so Devs can browse its files?
You can try and fastboot recoveryplay.img and do a nandroid, dont need an unlocked BL for that.....
Click to expand...
Click to collapse
Seriouslly?!?
I thought you needed to be unlocked to hotboot recovery.
Leraeniesh said:
Seriouslly?!?
I thought you needed to be unlocked to hotboot recovery.
Click to expand...
Click to collapse
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
jgregoryj1 said:
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
Click to expand...
Click to collapse
Ill re-lock and try it using both Keiran's recovery and FXP's recovery.
Lets hope for luck
Edit: Dident work. Just as expected
jgregoryj1 said:
I might be wrong, been on an unlocked BL since last Aug so maybe my memory is boinked but I thought anyone can do a recoveryplay.img boot and do a nandroid that way? If I am wrong someone please correct me
Click to expand...
Click to collapse
Don't think you can hotboot without unlocked boot. But if has kept root he can install the recovery installer app or the manual way to install it (thread in this section of the forum).
Leraeniesh said:
Ill re-lock and try it using both Keiran's recovery and FXP's recovery.
Lets hope for luck
Click to expand...
Click to collapse
Just a reminder, now that I am thinking on it I am not so sure it will work.... not 100% sure, so you might relcok and find you cannot unlock.....
poo-tang said:
Don't think you can hotboot without unlocked boot. But if has kept root he can install the recovery installer app or the manual way to install it (thread in this section of the forum).
Click to expand...
Click to collapse
Oh yeah that right! We have the custom recovery app from google play store.... sweet, that will help..
https://play.google.com/store/apps/details?id=com.pvy.CWMinstaler&hl=en
First, some backup on my problem: http://forum.xda-developers.com/showpost.php?p=26683314&postcount=4114 (tl;dr: any ROM I flash puts me in a seemingly inescapable boot loop, and rewriting boot.img sadly doesn't seem to help). This is still unresolved, and I think I've tried just about everything... getting pretty desperate there.
To make matters worse, my battery just died. I've heard there's a way to trick it into thinking it's charged so that you can access the bootloader at least temporarily (see: http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking -- I'm aware the article only mentions the DROID X, but I thought there must be some way to do this on the EVO 3D as well). Any ideas? I don't really want to have to buy a second battery, especially seeing as I'd have to wait several days for it to arrive - and wouldn't be able to use my phone until then.
Any help with either issue would be MUCH appreciated. Thanks so much!
3vo-noob said:
First, some backup on my problem: http://forum.xda-developers.com/showpost.php?p=26683314&postcount=4114 (tl;dr: any ROM I flash puts me in a seemingly inescapable boot loop, and rewriting boot.img sadly doesn't seem to help). This is still unresolved, and I think I've tried just about everything... getting pretty desperate there.
To make matters worse, my battery just died. I've heard there's a way to trick it into thinking it's charged so that you can access the bootloader at least temporarily (see: http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking -- I'm aware the article only mentions the DROID X, but I thought there must be some way to do this on the EVO 3D as well). Any ideas? I don't really want to have to buy a second battery, especially seeing as I'd have to wait several days for it to arrive - and wouldn't be able to use my phone until then.
Any help with either issue would be MUCH appreciated. Thanks so much!
Click to expand...
Click to collapse
if you plug the charger into the phone, the bootloader should be able to draw power from it, if I'm not mistaken.
3vo-noob said:
To make matters worse, my battery just died. I've heard there's a way to trick it into thinking it's charged so that you can access the bootloader at least temporarily (see: http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking -- I'm aware the article only mentions the DROID X, but I thought there must be some way to do this on the EVO 3D as well). Any ideas? I don't really want to have to buy a second battery, especially seeing as I'd have to wait several days for it to arrive - and wouldn't be able to use my phone until then.
Any help with either issue would be MUCH appreciated. Thanks so much!
Click to expand...
Click to collapse
Try- adb reboot-bootloader
that should boot up into your bootloader.
3vo-noob said:
To make matters worse, my battery just died. I've heard there's a way to trick it into thinking it's charged so that you can access the bootloader at least temporarily
Any help with either issue would be MUCH appreciated. Thanks so much!
Click to expand...
Click to collapse
I've accessed the boot loader without the battery installed. Plug into AC and use adb or power volume down to boot into boot loader.
Sent from my PG86100
rotheens spirit,
coal686 said:
I've accessed the boot loader without the battery installed. Plug into AC and use adb or power volume down to boot into boot loader.
Sent from my PG86100
Click to expand...
Click to collapse
Nope... Plugged into AC, but no matter how long I hold volume down + power, it won't get to the bootloader. Interestingly, when I plug it into my Mac, it still gives me a popup asking whether to connect the device to OS X or Windows (I have Fusion)... ideas?
3vo-noob said:
First, some backup on my problem: http://forum.xda-developers.com/showpost.php?p=26683314&postcount=4114 (tl;dr: any ROM I flash puts me in a seemingly inescapable boot loop, and rewriting boot.img sadly doesn't seem to help). This is still unresolved, and I think I've tried just about everything... getting pretty desperate there.
To make matters worse, my battery just died. I've heard there's a way to trick it into thinking it's charged so that you can access the bootloader at least temporarily (see: http://www.engadget.com/2010/09/23/editorial-the-dark-side-of-android-hacking -- I'm aware the article only mentions the DROID X, but I thought there must be some way to do this on the EVO 3D as well). Any ideas? I don't really want to have to buy a second battery, especially seeing as I'd have to wait several days for it to arrive - and wouldn't be able to use my phone until then.
Any help with either issue would be MUCH appreciated. Thanks so much!
Click to expand...
Click to collapse
I guess the first thing we need to know is, is your phone CDMA or GSM?
If you are flashing CDMA roms on a GSM or vise versa, it will never work. Its like putting diesel fuel in a gas engine. It won't run.
You have to flash a rom that is compatible with your phone.
Reckon we start there.
zcink said:
I guess the first thing we need to know is, is your phone CDMA or GSM?
If you are flashing CDMA roms on a GSM or vise versa, it will never work. Its like putting diesel fuel in a gas engine. It won't run.
You have to flash a rom that is compatible with your phone.
Reckon we start there.
Click to expand...
Click to collapse
Yup... I have a CDMA model & I'm checking each ROM to make sure it's specific to the CDMA EVO 3D
3vo-noob said:
Yup... I have a CDMA model & I'm checking each ROM to make sure it's specific to the CDMA EVO 3D
Click to expand...
Click to collapse
Have you tried the latest version of 4EXT Recovery Touch?
or how are able to flash any rom?
zcink said:
Have you tried the latest version of 4EXT Recovery Touch?
or how are able to flash any rom?
Click to expand...
Click to collapse
I'm using clockworkmod recovery touch... all the ROMs flash just fine, but once the flashing is done, the phone gets stuck in a bootloop
After an hour or so on the AC, my phone is able to power on & enter bootloader mode, but I still can't get out of the boot loop. Help plz?
3vo-noob said:
After an hour or so on the AC, my phone is able to power on & enter bootloader mode, but I still can't get out of the boot loop. Help plz?
Click to expand...
Click to collapse
Wanna try 4ext recovery?
your bootloader should say Unlocked and you are probably S-ON. Correct?
In fastboot. When you plug in your USB cable to the computer, it should now say fastbootusb.
If you can get that far, yeah, just flash the newest 4ext Recovery and try to flash your roms through that.
The newest has the ability to flash S-ON with one extra boot that will eliminate the need to flash the boot.img separately.
here is the link for it:
http://forum.xda-developers.com/showthread.php?t=1560279
***one possible thing I can think of that you may be doing wrong is when you flash the boot.img, it has to be the SAME one from the rom you flash.
anyway use 4ext instead.
zcink said:
your bootloader should say Unlocked and you are probably S-ON. Correct?
In fastboot. When you plug in your USB cable to the computer, it should now say fastbootusb.
If you can get that far, yeah, just flash the newest 4ext Recovery and try to flash your roms through that.
The newest has the ability to flash S-ON with one extra boot that will eliminate the need to flash the boot.img separately.
here is the link for it:
http://forum.xda-developers.com/showthread.php?t=1560279
***one possible thing I can think of that you may be doing wrong is when you flash the boot.img, it has to be the SAME one from the rom you flash.
anyway use 4ext instead.
Click to expand...
Click to collapse
Thanks SO much to everyone who helped! Thanks to you, I'm now happily using MeanROM!
3vo-noob said:
Thanks SO much to everyone who helped! Thanks to you, I'm now happily using MeanROM!
Click to expand...
Click to collapse
Glad to see you got it working. Thumbsup!
zcink said:
Glad to see you got it working. Thumbsup!
Click to expand...
Click to collapse
On an unrelated note, the one major feature that seems to be missing from 4EXT Recovery Control is the ability to update your ROM from within the app... I really admired that feature in ClockworkMod. Is there any other way to do this?
3vo-noob said:
On an unrelated note, the one major feature that seems to be missing from 4EXT Recovery Control is the ability to update your ROM from within the app... I really admired that feature in ClockworkMod. Is there any other way to do this?
Click to expand...
Click to collapse
Well yes, as the Developer updates the rom, you just use 4ext and reflash it over the top of the old one. Takes about 3 mins.
---------- Post added at 11:46 PM ---------- Previous post was at 11:34 PM ----------
Did you order another battery?
I just bought a lot of 10 of em from this company:
http://www.dhgate.com/new-li-ion-ph...r-htc/p-ff808081321fe6450132294c18783c3d.html
Should be like a lifetime supply. As long as you don't charge them, the shelf life should be many years.
$38.00 for 10 of them = $3.80 each. Very cheap! Took about 2 weeks to get them.
The title says it all. Nothing good can come of flashing with Odin except returning to stock. Stick with CWM or TWRP flashable zip files. If you disregard this message you will end up with a locked device, or even worse, a hard bricked device. Please use Odin as a factory restore tool only. I'm concerned that after unlock using our methods that people will flash the wrong thing and cause problems in the future.
The unlock method we have provided is not a standard Bootloader Unlock. It is an IROM unlock. This means you can quite literally flash anything to your device without any sort of signature checks. It is important that you stay safe and try to stay away from Odin unless absolutely necessary.
Thanks for all the hard work
Sent from my SCH-I605 using xda app-developers app
Excellent words of advice from an ERD who KNOWS what's he's talking about... Please take his advice everyone... It will save you A LOT of pain...
Stickied
Thanks for your hours of work. People WILL screw this up, unfortunately.
Sent from my SCH-I605 using xda app-developers app
thejron said:
Thanks for your hours of work. People WILL screw this up, unfortunately.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Yup! I can already see the threads starting.... It is good to know that we can still use Odin though cause I was under the impression that Odin was a no-go at this point... So flashing the factory image from imnuts would be the best resort to get back to stock if we needed to return a device?
shojus said:
Yup! I can already see the threads starting.... It is good to know that we can still use Odin though cause I was under the impression that Odin was a no-go at this point... So flashing the factory image from imnuts would be the best resort to get back to stock if we needed to return a device?
Click to expand...
Click to collapse
yes...check my guide out! I have step by step instructions that clearly state what and what not to do!!
droidstyle said:
yes...check my guide out! I have step by step instructions that clearly state what and what not to do!!
Click to expand...
Click to collapse
Thanks buddy! I just checked it out and I am very thankful for your guides as it has helped me and MANY others! I have thanked so many people that my limit is up (for the day) but I appreciate your time that you have put forth to helping people! :good:
I know I'm off topic. I'm not an owner of the note 2 but wanted to say awesome signature to the OP. From one vet to another thank you
Sent from my LG-LS970 using xda premium
droidstyle said:
yes...check my guide out! I have step by step instructions that clearly state what and what not to do!!
Click to expand...
Click to collapse
I still have plenty of "Thanks" so Thanks, and I am gonna study this weekend, hopefully by then the other issues folks have been having will at least be identified if not corrected.. then it's freedom for me!!
AdamOutler said:
The title says it all. Nothing good can come of flashing with Odin except returning to stock. Stick with CWM or TWRP flashable zip files. If you disregard this message you will end up with a locked device, or even worse, a hard bricked device. Please use Odin as a factory restore tool only. I'm concerned that after unlock using our methods that people will flash the wrong thing and cause problems in the future.
The unlock method we have provided is not a standard Bootloader Unlock. It is an IROM unlock. This means you can quite literally flash anything to your device without any sort of signature checks. It is important that you stay safe and try to stay away from Odin unless absolutely necessary.
Click to expand...
Click to collapse
Adam- but we ARE ok flashing with Odin so we can retrun to complete stock correct? your not saying that doing that may completely brick are phones are you? just want to be clear. i only use ODIN to go complete stock..
thank you for your work
dvigue said:
Adam- but we ARE ok flashing with Odin so we can retrun to complete stock correct? your not saying that doing that may completely brick are phones are you? just want to be clear. i only use ODIN to go complete stock..
thank you for your work
Click to expand...
Click to collapse
"Please use Odin as a factory restore tool only"
In Androidstyle's guide thread, Adam asked him to point the unlock guide to his unlock thread, but I don't see an unlock thread from Adam, only the Revision3 thread which has no steps to unlock. I see the video Adam made, but my understanding is that the process has changed and the links to download Adam's ROM are dead on the Youtube page. Anyone have the link to Adam's unlock step by step guide?
wmaudio said:
In Androidstyle's guide thread, Adam asked him to point the unlock guide to his unlock thread, but I don't see an unlock thread from Adam, only the Revision3 thread which has no steps to unlock. I see the video Adam made, but my understanding is that the process has changed and the links to download Adam's ROM are dead on the Youtube page. Anyone have the link to Adam's unlock step by step guide?
Click to expand...
Click to collapse
It's in "Verizon Galaxy Note II Android Original Development". Go up one level and you'll see it. There are only two threads there so it shouldn't be too hard to find.
I don't mean to sound mean but if you really can't figure out how to get to his unlock thread do you really think it's a good idea to be unlocking your bootloader? Maybe you should just stick to a rooted image and read up and learn for awhile before jumping in over your head
Sent from my SCH-I605 using xda app-developers app
LordRalh3 said:
I don't mean to sound mean but if you really can't figure out how to get to his unlock thread do you really think it's a good idea to be unlocking your bootloader? Maybe you should just stick to a rooted image and read up and learn for awhile before jumping in over your head
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
To be fair, the distinction between "Android development" and "Original Android development" is new for many of us. I, too, was wondering how to get back to this thread since I tend to browse XDA through bookmarks instead of the site hierarchies. I didn't realize there was an "original Android development" section until after I double checked the name on the thread jumper. It's not that one is technologically illiterate (I got through all this in one fell swoop with no issues and have rooted and unlocked every phone I've owned since the G1), it's just that it's different. Last device I had didn't have a section for original development, so it wasn't immediately obvious to me (though I quickly understood what it was for). so cut him some slack and just kindly point him to the right direction. I know you said you weren't trying to sound mean, but if you really weren't trying to sound mean you could have just helped him out without all of the extra, unnecessary commentary. You know what they say about assumptions, after all.
Just got the Note 2 on verizon and loving it so much I'm going to hold off for a bit before unlocking & rooting. Normally on all my android phones that is done day 1... but this time w/ the dev community just now unlocking it, I think I'm going to wait a few weeks.
In context, imnuts has put out a Recovery flash-able version of CWM. If one tries his CWM but wants to go back to TWRP then currently it seems that one need to ODIN it. To Adam Outler's point it would be safer to have a Recovery flash-able version of TWRP. [?]
AdamOutler said:
The title says it all. Nothing good can come of flashing with Odin except returning to stock. Stick with CWM or TWRP flashable zip files. If you disregard this message you will end up with a locked device, or even worse, a hard bricked device. Please use Odin as a factory restore tool only. I'm concerned that after unlock using our methods that people will flash the wrong thing and cause problems in the future.
The unlock method we have provided is not a standard Bootloader Unlock. It is an IROM unlock. This means you can quite literally flash anything to your device without any sort of signature checks. It is important that you stay safe and try to stay away from Odin unless absolutely necessary.
Click to expand...
Click to collapse
Does the same go for Heimdall aswell then?
trevd said:
Does the same go for Heimdall aswell then?
Click to expand...
Click to collapse
Yes because it does the same job as ODIN but on a different operating system.
Sent from VZW Note 2
Clarkkent434 said:
Yes because it does the same job as ODIN but on a different operating system.
Sent from VZW Note 2
Click to expand...
Click to collapse
That's what I figured , I thought I'd ask the dumb question to explicitly clarify it.
hi,
well, my amaze was running very smooth.. i was using super sense and all was good, i decided to flash the source build pacman,after flashing the ROM i didn't get any good battery so i flash viper 1.6.7 because of its great battery life... after booting the ROM i just realize that my phone is not showing any network signals... after messing with it for some time i decided to start from the scratch so i downloaded RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L.17DC_30.78.550L.15_release_262141_signed_13.zip, renamed it ph85img,put it to the root of my ext sd card, pulled my battery and rebooted it into the boot loader, fastboot auto detect it and started flashing, after the update phone still was not showing any signals, but when i activate and deactivate airplane mode, signals just came from nowhere just for 10 seconds and then got vanished, i flashed recovery and then rooted my phone and again flash viper ver 1.7.1 but the result is still the same... on/off airplane works but only for 10 seconds...i also cleaned out the back antenna connectors but no luck... :crying:
i am so confused right now as i do not know what is the problem ...is this somewhat related to the radio? i don't know . .
i hope you guys will help me to find out and solve this problem..
i have unlocked bootloader, s-off, supercid, 4ext recovery, any my hboot version is 1.93.2222..
please help me guys... and sorry for my bad english..
@ravike14, @SuperAfnan ....
Retrace your steps
carbon_guy said:
hi,
well, my amaze was running very smooth.. i was using super sense and all was good, i decided to flash the source build pacman,after flashing the ROM i didn't get any good battery so i flash viper 1.6.7 because of its great battery life... after booting the ROM i just realize that my phone is not showing any network signals... after messing with it for some time i decided to start from the scratch so i downloaded RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L.17DC_30.78.550L.15_release_262141_signed_13.zip, renamed it ph85img,put it to the root of my ext sd card, pulled my battery and rebooted it into the boot loader, fastboot auto detect it and started flashing, after the update phone still was not showing any signals, but when i activate and deactivate airplane mode, signals just came from nowhere just for 10 seconds and then got vanished, i flashed recovery and then rooted my phone and again flash viper ver 1.7.1 but the result is still the same... on/off airplane works but only for 10 seconds...i also cleaned out the back antenna connectors but no luck... :crying:
i am so confused right now as i do not know what is the problem ...is this somewhat related to the radio? i don't know . .
i hope you guys will help me to find out and solve this problem..
i have unlocked bootloader, s-off, supercid, 4ext recovery, any my hboot version is 1.93.2222..
please help me guys... and sorry for my bad english..
Click to expand...
Click to collapse
@carbon_guy
Can you try and flash PACman, and see if the IMEI gets restored? If it doesn't, flash Super Sense again. Hopefully that will restore it. :good:
Unfortunately, flashing does go wrong sometimes. It is definitely possible to lose an IMEI, but you *could* get it back if you retrace your steps! Some guy lost his IMEI because of Google Talk, but got it back by retracing his steps on another thread.
SuperAfnan said:
@carbon_guy
Can you try and flash PACman, and see if the IMEI gets restored? If it doesn't, flash Super Sense again. Hopefully that will restore it. :good:
Unfortunately, flashing does go wrong sometimes. It is definitely possible to lose an IMEI, but you *could* get it back if you retrace your steps! Some guy lost his IMEI because of Google Talk, but got it back by retracing his steps on another thread.
Click to expand...
Click to collapse
i will,
and then i will post the results, thanks for your precious reply..
carbon_guy said:
i will,
and then i will post the results, thanks for your precious reply..
Click to expand...
Click to collapse
Wow I didn't know you guys were camping out waiting for me.
If it DOESN'T work, then you should bring it back to bone stock by flashing a RUU, hide the "Re-locked" status by using scotty's mod bureied in the dev section, and send it to HTC for repairs, or claim warranty.
Sometimes flashing random ROMs *may restore it, but that might be unlikely. Good luck! :fingers-crossed:
SuperAfnan said:
Wow I didn't know you guys were camping out waiting for me.
If it DOESN'T work, then you should bring it back to bone stock by flashing a RUU, hide the "Re-locked" status by using scotty's mod bureied in the dev section, and send it to HTC for repairs, or claim warranty.
Sometimes flashing random ROMs *may restore it, but that might be unlikely. Good luck! :fingers-crossed:
Click to expand...
Click to collapse
i just flashed pacman but the result is the same...
what should i do... should i try to flash super sense...?
i heard in forums that this problem is also relate to a bad radio...so what about it ?
carbon_guy said:
i just flashed pacman but the result is the same...
what should i do... should i try to flash super sense...?
i heard in forums that this problem is also relate to a bad radio...so what about it ?
Click to expand...
Click to collapse
Flash super sense, then perhaps you can try to flash the radio. :good:
SuperAfnan said:
Flash super sense, then perhaps you can try to flash the radio. :good:
Click to expand...
Click to collapse
i am on it...
SuperAfnan said:
Flash super sense, then perhaps you can try to flash the radio. :good:
Click to expand...
Click to collapse
just flashed super sense... no luck.. :crying:
so what about the radio... how could i flash one?
carbon_guy said:
just flashed super sense... no luck.. :crying:
so what about the radio... how could i flash one?
Click to expand...
Click to collapse
Here's the link to jordin's radio he pulled from the OTA.
http://forum.xda-developers.com/showthread.php?p=39820467#post39820467
http://www.mediafire.com/download/nw0qhkjhthsekji/PH85IMG.zip
Put it on your external_sd and run it in the bootloader. Let's see if it works/ :fingers-crossed:
SuperAfnan said:
Here's the link to jordin's radio he pulled from the OTA.
http://forum.xda-developers.com/showthread.php?p=39820467#post39820467
http://www.mediafire.com/download/nw0qhkjhthsekji/PH85IMG.zip
Put it on your external_sd and run it in the bootloader. Let's see if it works/ :fingers-crossed:
Click to expand...
Click to collapse
flashed it...still the same... and now even airplane on/off stopped working..
carbon_guy said:
flashed it...still the same... and now even airplane on/off stopped working..
Click to expand...
Click to collapse
You may need to flash the T-Mobile OTA.
Did you use hangouts or talk by any chance?
Sent from my SGH-T999 using Tapatalk
SuperAfnan said:
You may need to flash the T-Mobile OTA.
Did you use hangouts or talk by any chance?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
nop...never used on my amaze...
carbon_guy said:
nop...never used on my amaze...
Click to expand...
Click to collapse
If everything fails, go back to bone stock and flash the RUU.
If that fails, you may need to call your carrier, or send it to a HTC repair center.
Sent from my SGH-T999 using Tapatalk
SuperAfnan said:
If everything fails, go back to bone stock and flash the RUU.
If that fails, you may need to call your carrier, or send it to a HTC repair center.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
hmmm... thanks for your efforts man, could you please point out that which RUU or OTA i should flash..
carbon_guy said:
hmmm... thanks for your efforts man, could you please point out that which RUU or OTA i should flash..
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1617644
Use the T-mobile one, since it's the most used. If there was an international RUU, that'd be great, but there isn't, unfortunately.
SuperAfnan said:
http://forum.xda-developers.com/showthread.php?t=1617644
Use the T-mobile one, since it's the most used. If there was an international RUU, that'd be great, but there isn't, unfortunately.
Click to expand...
Click to collapse
how about this one...
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
carbon_guy said:
how about this one...
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
Click to expand...
Click to collapse
Yes just flash it. I can't guarantee anything though because nobody ever found a cure for IMEI's being erased on the amaze. But on the s3, odining to stock usually fixed it.
Sent from my SGH-T999 using Tapatalk
SuperAfnan said:
Yes just flash it. I can't guarantee anything though because nobody ever found a cure for IMEI's being erased on the amaze. But on the s3, odining to stock usually fixed it.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
bootloader detected it, started to loading it and then parsing and then came back to normal...didn't flash it, i am supercid and s-off, do i have to relock bootloader in order to flash this OTA?
carbon_guy said:
bootloader detected it, started to loading it and then parsing and then came back to normal...didn't flash it, i am supercid and s-off, do i have to relock bootloader in order to flash this OTA?
Click to expand...
Click to collapse
You might have to.
Look up a fastboot tutorial, you will need to type in "fastboot oem lock" using command prompt in the sdk folder. You should look up a tutorial or guide on how to do this because it's going to take too long to explain in one thread.
Once your boot loader is relocked, proceed to the RUU. If this ruu fails to restore signal, I'm out of ideas. Sorry @carbon_guy.
Sent from my SGH-T999 using Tapatalk