Related
Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
razorseal said:
Hey guys
I'm a bit worried, I have gingerblur on the phone now, and apparently OTAing from it can be bad juju
I read the fastboot way of doing it, but just want to make sure I got this right so I dont mess it up
1. DL fastboot
2. download all the images from the link provided on the thread
**here is where I need to make sure I got this right***
3. I have to put all the images in the same folder as the fastboot.exe I guess
4. use the commands given on the link
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
5. I wipe the data and reboot
moto-fastboot -w
moto-fastboot reboot
6. should be gtg
now my questions are
is it going to be rooted when I do this, or will I have to reroot the phone (is it posisble to root the 2.3.4?)
and can I do this coming from gingerblur? I don't wanna mess anything up
and lastly, what about all the other img files? webtop, radio etc...
thanks!
ps. sorry I'm in a rush, supposed to goto dinner and then see captain america, so I figured I put this up real quick b4 i leave, gf is waiting at the door! lol
Click to expand...
Click to collapse
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Are you unlocked??
Sent from my MB860 using XDA App
Paschalis said:
Are you unlocked??
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
As long as he's on 1.8.3. that shouldn't matter.
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Paschalis said:
Yes, but if he's locked, I think he won't be able too use fastboot..
Edit: if the images he want to flash using fastboot, are for unlocked device, he will end bricked.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Refer to the link I sent him...
Unlocked as in rooted?
I'm running gingerblur, so yes, I'm rooted so i have access to cwm...
Can I just flash that? And yes I'm on 1.8.3
Flashing via sbf?
Sent from my MB860 using XDA App
mpalatsi said:
Don't make things so complicating, just flash this if you're on 1.8.3.
http://forum.xda-developers.com/showthread.php?t=1182526
Click to expand...
Click to collapse
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
razorseal said:
So what are allll these posts about phones hard bricking? Why isn't everyone just doing this?
I realized unlocked as in bootloader unlocked... That part I'm not sure, I did the OTA 1.8.3 update, so I assume not...
I doubt I'll be downgrading though, so is it safe to just use that link? I'd hate to hard brick
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA. Edit: actually, that one is modified with the unlocked bootloader.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Edit2: If it makes you feel any better, I personally used the method you described in the OP to upgrade. Wasn't that hard or "complicated".
feisty_noodle said:
@razorseal,
You will not hard-brick if you use the link posted by @mpalatsi.
It appears to be the official SBF version of the OTA.
However, you will not be able to go back to any other SBF after you flash this thing. It modifies the bootloader in a way that will cause damage if you try to revert. This is ok if you have no plans to revert, but one never knows when they need to take a step back.
So, you can commit to this SBF or you can do the sensible thing: unlock your bootloader (if you haven't already done so) and follow with your procedure (or use the Fruit Cakes which are equivalent to the fastboot flashing, but using the recovery).
I would recommend staying away from SBF's in general, especially from the ones that cause irreversible changes to the bootloader.
Edit: If you need help unlocking your bootloader, look up the Pudding thread in the Dev section. Everything is straightforward and has been done by many users successfully.
Click to expand...
Click to collapse
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
I'm in the same boat. I'm on ginger blur and 1.83 and I just want to update, unlock and root.I would like to revert back if need be.
Sent from my MB860 using XDA App
razorseal said:
ok, got it...
I understand no downgrading, but how about upgrading in the future?
so if I want to do it the 'safe' way, how do I do that? the way I mentioned it? (the thread via fastboot)
How can I check if i'm unlocked my bootloader or not?
Click to expand...
Click to collapse
This link was exactly what I used.
As far as upgrading in the future, you can use the resources found here, on XDA. People will be dissecting new updates to remove the nasty bits (bootloaders and such).
If you decide that you want to play with custom ROMs, you can do that, too.
You will NOT be able to use OTA's unless you backtrack to a fully stock ROM via official OTA's or SBF's. This can be done, but will require some careful work on your part.
For the bootloader unlocking--go read the Pudding thread here. It is very a straightforward procedure.
Edit: if your first Motorola boot screen has the word "Unlocked" in the upper left corner, then you are unlocked. If not, then ...
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Paschalis said:
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Click to expand...
Click to collapse
well then I should stay from that link that was provided here considering it's an sbf file...
Paschalis said:
Don't you remember if you unlocked your bootloader?
There is a method to check that I think in the pudding thread.
With unlocked bootloader, when moto makes an OTA, the devs here take it, mod it, made it a flashable zip, and you can upgrade your phone.
For downgrading.
Personally I m on gingerblur 4.5. With unlocked bootloader, and tenfars port of cwm recovery installed.
I currently have CWM nandroid backup.
I can install the 2.3.4 cherryblur e.g( with cwm installation also), and whenever I want I can restore this backup..
I can also have 2 backups of 2.2 and 2.3 and switch between the 2 backups.
Its very good advice to stay away from sbf's.
Safer seems the cwm zip files.. Of known devs..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
feisty_noodle said:
I agree with almost everything.
The 'almost' part is that using stock system.img can be a good idea. Whenever new firmware updates come out, I am always curious to see what the OEM envisioned to be the 'normal' look for their device.
Flashing these is perfectly safe because you are only touching the system partition. As long as you have functional fastboot (unlocked bootloader) or recovery, you will have two fallback positions in case something goes wrong (like a bad flash).
Trusting OEM's to give you a good product has historically been a losing proposition. They always take waaay too long. And they make stupid mistakes (like the ****ed up battery monitor in the new Gingerbread ROM, the 4.5.91). And to fix those mistakes they take their sweet time again.
Anyway, @razorseal:
After you upgrade, you will likely see poor battery performance. The way to fix this is to flash the new radio 01.77.30P found here; this will be done through recovery. I am not sure if Ken's thread here is the same thing. The image files look different.
Also, to fix the aforementioned screw-up by Motorola, follow the instructions here.
Click to expand...
Click to collapse
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
razorseal said:
Thanks bud
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I looked at that, and that says it will unlock it... isn't the link provided here already unlocked?
Click to expand...
Click to collapse
Yes, zomgunlock-lite.sbf is the contents of "pudding".
That is your bootloader that has the unlock code. Just follow Ken's instructions from the page you linked to.
Also, here is the link for an easy root method after you are done.
If you are still scared, watch the videos of the process here. I didn't have time to look too carefully, but it clearly shows what the bootloader screen should look like when you've successfully unlocked.
Good luck, I have to sleep now.
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
razorseal said:
ah ****... not working
I have something that says 'failed to boot 4'
starting RSD mode
uh oh
Click to expand...
Click to collapse
You are not in a bricking situation! Take a deep breath.
I have not seen this, but others have ...
http://forum.xda-developers.com/showthread.php?t=1062727
Do some homework.
I am really going now.
I just reflashed.... I guess something got corrupted it works now
alright, off to unlocking, and doing the radio tweak along with battery % and att logo removal
I can navigate adb and everything just fine and no I don't need to know how to set up unlock or want to know if there is a root method lol. I'm way past all that.
I have been reading about TWRP 2.0 though and can't seem to find what I am looking for. I have read it's suggested to actually remove the other recovery then install the new one. How exactly to I go about that? and do I HAVE to leave the twpr2.0ect...name intact or can I rename it?
2nd, and semi related but not, when flashing Roms I know I can flash kernels in the same set up time but can I also SAFELY flash other items?
Example: I have been having to reflash OLYMPUS for various reason but I also use the stock lock ring zip, Anthrax and now would like to use the Leedroid tweaks.
Can I flash all in the same recovery session? If so is there a suggested order for multiple items?
blizzard1017 said:
I can navigate adb and everything just fine and no I don't need to know how to set up unlock or want to know if there is a root method lol. I'm way past all that.
I have been reading about TWRP 2.0 though and can't seem to find what I am looking for. I have read it's suggested to actually remove the other recovery then install the new one. How exactly to I go about that? and do I HAVE to leave the twpr2.0ect...name intact or can I rename it?
2nd, and semi related but not, when flashing Roms I know I can flash kernels in the same set up time but can I also SAFELY flash other items?
Example: I have been having to reflash OLYMPUS for various reason but I also use the stock lock ring zip, Anthrax and now would like to use the Leedroid tweaks.
Can I flash all in the same recovery session? If so is there a suggested order for multiple items?
Click to expand...
Click to collapse
To install new recovery, simply boot your phone into the bootloader. The latest (and sadly probably last) version of TWRP is here. Plug a USB cable into your phone from your computer. You should see FASTBOOT change to FASTBOOT USB. Now in a command prompt window, go to the directory where your fastboot.exe is located, (place the recovery that you want flash in the same folder to make things easier). Type in the command
fastboot.exe flash recovery thenameofyourrecovery.img
Wait a few seconds. It should output a message saying that the recovery image had successfully been flashed.
--
Now, to flash Roms, Kernels, addons, etc... Unfortunately, an issue with HBOOT 1.50, you can't just flash kernels, etc straight from recovery. What you'll have to do is flash either using Flash Image GUI (not too familiar with it) or Boot a recovery image using fastboot on your computer.
Similar command follows.
fastboot.exe boot thenameofyourrecovery.img
It will boot into recovery, from here you can go ahead and flash your ROMs, etc. If you haven't done a NANDroid backup, do that first just in case. On you phone, now you can flash the ROM, then Kernel, lockring, one after another (as far as I know, you should be fine doing things in that order - ROM goes first though).
For a better explanation, look at post #2 of this thread.
Best of luck.
Thank you on the 2nd part, I got the adb into recovery part down.
As far as the 1st part, is there any truth to needing to delete the original recovery before I flash the new? If so how would I do that?
Are team win defunct? I don't follow their threads very close.
Sent from my PG86100 using xda premium
blizzard1017 said:
Thank you on the 2nd part, I got the adb into recovery part down.
As far as the 1st part, is there any truth to needing to delete the original recovery before I flash the new? If so how would I do that?
Are team win defunct? I don't follow their threads very close.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Glad I could help.
Nope, you don't need to delete the original recovery before flashing the new one. You can safely flash the new recovery without doing anything before.
About TeamWin. It would probably be best for me to point you to their most recent blog post. I'm not too sure about the future, I guess we'll have to see what happens.
I have unlocked, rooted, made nandroid backup before flashing ziggy's kernel with cwm. I have seen to diferent answers on here about getting back to stock kernel. I have heard all I have to do is reboot into recovery and restore nandroid. I also have heard I have to flash the stock kernel. How exactly do I go back to stock kernel?? Also if I wanted to try another kernel, do I have to get back to stock kernel before flashing another one?
Download the stock kernel located at the bottom of the first post HERE.
First, and most importantly, make sure you have no PH98.IMG files on the root of your Sdcard, if so delete them. After your nandroid restore, go back to the main menu in recovery and power down the device.
Extract the Boot.img from the Stock kernel downloaded and flash via fastboot. Reboot the phone and you should be good.
sorry i'm a noob with the htc devices. Ok so i've downloaded the stock rooted kernel. after that, I erase that PH98.IMG from my sd. shut my phone off, pull battery, put battery back in, hold down power and -vol, select recovery with power button, go to back up/restore, then run nand restore, go to main menu and power down. after that i'm lost!! I downloaded stock rooted kernel on my computer, where do I extract the boot.img to and how do I flash it with fastboot? I'm sorry i'm a noob!!
Thanks in advance
Unzip it to the same folder you have fast boot in. Open cmd window and CD to that directory. Then fastboot flash boot boot.img
sent from my cm7 rooted fire
what about the boot.img thats in my nandroid backup folder? couldn't I just flash that with fastboot? still not sure how to flash with fastboot.
papapena25 said:
what about the boot.img thats in my nandroid backup folder? couldn't I just flash that with fastboot? still not sure how to flash with fastboot.
Click to expand...
Click to collapse
I don't see why not...should be the same file if it is indeed a stock nandroid.
ok thanks!! sorry i was thinking I didn't need to se my computer. think I got it now. So from now on if I want to try diferent kernels I have to do this to go back to stock before switching to another kernel right?
papapena25 said:
ok thanks!! sorry i was thinking I didn't need to se my computer. think I got it now. So from now on if I want to try diferent kernels I have to do this to go back to stock before switching to another kernel right?
Click to expand...
Click to collapse
It's cool. In order to flash kernels/recoveries we need to do so through fastboot from the PC because we are not S-Off. We just have to deal with it but it's not all that bad.
You don't necessarily need to go back to stock, you can flash a modded kernel over an existing on, however, you need to make sure to flash the modules that come with the boot.img from that kernel as well. Otherwise you may have issues such as wi-fi not working.
thanks so much. what exactly is or does s-off and s-on mean? I'm used to my ogdroid and droidx
papapena25 said:
thanks so much. what exactly is or does s-off and s-on mean? I'm used to my ogdroid and droidx
Click to expand...
Click to collapse
The S stands for "Security". While we have an unlocked bootloader aka. S-On we cannot flash new/leaked radios or kernels in recovery (.img or image files). Only S-Off devices can do that.
The HTCdev unlocked bootloader allows us to almost anything to the phone except flashing radios that are not signed by HTC. For kernels, we need to flash them in fastboot which is essentially a workaround.
That may not be the best explanation but it's time to leave work . Searching will provide you with more detailed information.
To those that responded to the op, I commend you. This was about the most civilized conversation I have seen in quite awhile, along with giving out the info requested. This is what I signed up for on XDA.
Sent from my ADR6425LVW using xda premium
trickster2369 said:
To those that responded to the op, I commend you. This was about the most civilized conversation I have seen in quite awhile, along with giving out the info requested. This is what I signed up for on XDA.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yeah I am very happy with the fast and polite answers I got. I have seen some other people post questions like mine on here and get nothing but rude comments back with no answers. So I was a little hesitant to even ask,but i'm glad I did. Thanks again to everyone that helped me out!!
http://forum.xda-developers.com/showthread.php?p=20990402
jmorton10 said:
http://forum.xda-developers.com/showthread.php?p=20990402
Click to expand...
Click to collapse
Thanks for the link, now I'm confused?? If I have a nandroid backup do I still have to flash that lib in recovery first??
papapena25 said:
Thanks for the link, now I'm confused?? If I have a nandroid backup do I still have to flash that lib in recovery first??
Click to expand...
Click to collapse
Those are the files you would need in order to run the stock kernel if you don't want to restore your nandroid. Flash the stockmodules.zip in recovery and place then flash the PH98IMG.zip in the bootloader.
Marcismo55 said:
Those are the files you would need in order to run the stock kernel if you don't want to restore your nandroid. Flash the stockmodules.zip in recovery and place then flash the PH98IMG.zip in the bootloader.
Click to expand...
Click to collapse
I figured thats what they were for. Thanks again for your help.
I did my research on how to install ROMS with a locked S On and Kernels, but just got even more confused about the process. I am coming from an Evo 4g CDMA.
I have H BOOT 1.5 unlocked S ON. My back up was lost. I tried to flash something like the newest MIUI using TWRP 1.1. w/e. I can't get past the boot screen for MIUI. As I was reading up on the forums, it seemed to me that you had to use a program called Flash Image GUI to get a kernel going on a ROM. Though, here is where I was confused. If a ROM has a kernel in it and I flash the ROM, does the Kernel part of that flash not get set up as well?
Would I need to flash the rom like normal from the SD Card then use something separate to flash a Kernel? If so, I am kinda boned. I can't get into the phone, just the recovery and can't get that program installed on the phone Trying to flash up Xplode now to see if maybe I just got a bad download.
If these questions were answered, please forgive me, I did try to find the answers, but as I read up more and more, it was getting to be more and more confusing to my personal issue at hand.
Thanks for the help!!
If you grab the kernel from your Miui zip, it's in the zips root called boot.img
Put that into your folder with your fastboot exe
Boot into bootloader the same as when you flashed the CWM
Use fastboot command... fastboot flash boot boot.img
this will flash the kernel and you should be able to boot up properly
Oh, well that is the problem. I had someone else flash TWRP for me. Guess I need to find out more on how to flash up that to get the kernel going. This S On thing is a massive PITA, lol. Guess once I get the phone up and going and I can use that program, things will be way easier
Nametaken said:
Oh, well that is the problem. I had someone else flash TWRP for me. Guess I need to find out more on how to flash up that to get the kernel going. This S On thing is a massive PITA, lol. Guess once I get the phone up and going and I can use that program, things will be way easier
Click to expand...
Click to collapse
I see. i skipped the how to part since i thought you had alrady flashed the CMW your self, it's fairly easy.
you need..
1) to install the evo 3d usb drivers.. filename HTCDriver3.0.0.007.exe .sorry i don't have a link, i got them off these forums somewhere
2) you need the fastboot.exe , again search google/these forums
then shut down your phone
pull battery out, then back in
hold down volume- (minus) and then hold the power button as well, only let go once in the bootloader, choose the fastboot option then insert usb cable to phone->pc .. you should see fastboot-usb message come up on your phone
then you can type out that fastboot command in the previous post from a dos command prompt, from the directory with your fastboot exe and boot.img
It's easier to put rom you want on the SD card make sure debug is on.
Adb reboot bootloader . Now
Fastboot boot recovery.img now wipe and flash rom you are good to go man. Works flawless .
Sent from the Reaper.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Sorry about posting in the wrong area.
What I did, which can help out other 3D noobs is this:
Since I just unlocked and have no back up, my kernel was still stock
Downloading a stock rom and moving it to my phone via comp, twrp recovery mode>> USB Toggle allows you to connect to PC! Put the rom on the main part of the SD card and just flash like normal.
Here you should be able to boot up like normal again.
Let me say, Flash Image GUI is a noobs friend till you can learn to use adb more.
I was told you can put a Rom on your card and just flash allowing the kernel to flash as well. I have not had success with this with HBoot 1.5 S On.
Flash Image GUI:
Download the rom you want, Aosp to Sense is fine.
Open Flash GUI and choose the Browse option.
Locate your rom on your card and choose it.
The app will give you a message saying the rom is big yada yada, say yes.
Wait a few moments as it finds the kernel. Once it does, choose flash Image.
Choose reboot recovery and flash the exact rom you picked with the App. Reboot and win.
This is just what I, a noob, have found to work.
I have NOT been able to just flash any rom on the SD Card and have it work. Flash Image UI has NOT been able to get Virus' Rom to load
A's I find more noob friendly tips I can report.
Thanks everyone else for the input! I won't lie, I came from an Evo 4g and am totally lazy as I am used to S Off and just flashing away. S On, I hate you. ADB, I fear you. Flash Image GUI, I want to marry you!
CDMA 3D, I wish we had more AOSP lol
Hope this helps out some people.
Sent from my PG86100 using XDA
Nametaken said:
Sorry about posting in the wrong area.
What I did, which can help out other 3D noobs is this:
Since I just unlocked and have no back up, my kernel was still stock
Downloading a stock rom and moving it to my phone via comp, twrp recovery mode>> USB Toggle allows you to connect to PC! Put the rom on the main part of the SD card and just flash like normal.
Here you should be able to boot up like normal again.
Let me say, Flash Image GUI is a noobs friend till you can learn to use adb more.
I was told you can put a Rom on your card and just flash allowing the kernel to flash as well. I have not had success with this with HBoot 1.5 S On.
Flash Image GUI:
Download the rom you want, Aosp to Sense is fine.
Open Flash GUI and choose the Browse option.
Locate your rom on your card and choose it.
The app will give you a message saying the rom is big yada yada, say yes.
Wait a few moments as it finds the kernel. Once it does, choose flash Image.
Choose reboot recovery and flash the exact rom you picked with the App. Reboot and win.
This is just what I, a noob, have found to work.
I have NOT been able to just flash any rom on the SD Card and have it work. Flash Image UI has NOT been able to get Virus' Rom to load
A's I find more noob friendly tips I can report.
Thanks everyone else for the input! I won't lie, I came from an Evo 4g and am totally lazy as I am used to S Off and just flashing away. S On, I hate you. ADB, I fear you. Flash Image GUI, I want to marry you!
CDMA 3D, I wish we had more AOSP lol
Hope this helps out some people.
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
ADB is pretty simple to flash with lol
All you do is keep a copy of the recovery.img you are using in your adb folder...
You hold shift down right click on the folder that adb is in platform tools folder is where it's at say open cmd prompt to it. That is the fast painless method
Make sure you have a rom on your sd card.... Also that debug is turned on...
Plug phone in hook to computer...
ADB:
adb reboot bootloader
now:
fastboot boot recovery.img takes you into recovery...
Now wipe don't wipe SD card...
Flash rom your set works on virus roms and any other rom 0 issues
Also Flash GUI works for everyone nothing wrong with it....
I just prefer Good Old Adb to do my work If you need any help feel free to ask man.. I'll do what I can to help ya out if you get stuck..
reaper24 said:
ADB is pretty simple to flash with lol
All you do is keep a copy of the recovery.img you are using in your adb folder...
You hold shift down right click on the folder that adb is in platform tools folder is where it's at say open cmd prompt to it. That is the fast painless method
Make sure you have a rom on your sd card.... Also that debug is turned on...
Plug phone in hook to computer...
ADB:
adb reboot bootloader
now:
fastboot boot recovery.img takes you into recovery...
Now wipe don't wipe SD card...
Flash rom your set works on virus roms and any other rom 0 issues
Also Flash GUI works for everyone nothing wrong with it....
I just prefer Good Old Adb to do my work If you need any help feel free to ask man.. I'll do what I can to help ya out if you get stuck..
Click to expand...
Click to collapse
You can not flash some ROMS through ADB/Fastboot with s-on, it just doesn't work no matter which way you go about it. Flashing a recovery is easy but that was not the OP's problem. The "noob" way that the OP suggested is the only way to get roms with custom boot.img in the zip to stick. I just installed CM9 and ADB/fastboot was of no use. Getting into recovery is easy but will not provide results unless you have used FlashImageGUI.apk first on a working ROM.
Nether CWM nor TWRP work to flash such ROM's with the right boot.img. You must use FlashImageGUI.apk!
StevetotheH said:
You can not flash some ROMS through ADB/Fastboot with s-on, it just doesn't work no matter which way you go about it. Flashing a recovery is easy but that was not the OP's problem. The "noob" way that the OP suggested is the only way to get roms with custom boot.img in the zip to stick. I just installed CM9 and ADB/fastboot was of no use. Getting into recovery is easy but will not provide results unless you have used FlashImageGUI.apk first on a working ROM.
Nether CWM nor TWRP work to flash such ROM's with the right boot.img. You must use FlashImageGUI.apk!
Click to expand...
Click to collapse
I never had any issues using cwm the older version 4.0 to flash any rom the fastboot method Anyway's older TWRP and Newest CWM had some issues with not wiping right to flashing funky...
I will help the OP out if he ever gets stuck
Yeah reaper your right! I think I came off like a ****, I am one, but didn't mean to come off sounding snide.
Sent from my HTC Evo 3D using XDA
StevetotheH said:
Yeah reaper your right! I think I came off like a ****, I am one, but didn't mean to come off sounding snide.
Sent from my HTC Evo 3D using XDA
Click to expand...
Click to collapse
It's all good man no worries Your cool
Sent from my PG86100 using xda premium
Dah da dat ta ta! (Swoops in with my 2 cents)
See the Guide/Flashing Notes in my signature for a walkthru for flashing roms, recoveries, etc. All up to date. Choose your method: fastboot & recovery or flashimage & recovery.
Note: TWRP 2.0 with Dumlock is a workaround to avoid using fastboot (pc). FlashImage is not a requirement, its also a workaround vs fastboot.
mpgrimm2 said:
Dah da dat ta ta! (Swoops in with my 2 cents)
See the Guide/Flashing Notes in my signature for a walkthru for flashing roms, recoveries, etc. All up to date. Choose your method: fastboot & recovery or flashimage & recovery.
Note: TWRP 2.0 with Dumlock is a workaround to avoid using fastboot (pc). FlashImage is not a requirement, its also a workaround vs fastboot.
Click to expand...
Click to collapse
Nice I was wondering when you was gonna pop in . LOL
Sent from my PG86100 using xda premium
Thanks erryone. I hope others were able to get some help here that are new to 3vo and flashing. I am so waiting for a nub proof s-off method.
Sent from my PG86100 using XDA
There is the HBOOT downgrade. I have ZERO linux experience whatsoever and thought the process was very easy. I know it says to 'brick' the phone, but it is honestly not that scary. I have done two of these already both being successful on the first attempt. The live cd by closeone actually takes care of almost everything, except for actually doing the brick. Trust me being on 1.40 s-off is much much nicer.
Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
ten6 said:
Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
Click to expand...
Click to collapse
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Dark Nightmare said:
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Click to expand...
Click to collapse
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
ten6 said:
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
Click to expand...
Click to collapse
Don't download that one, it has issues, hold up, I'll give you a link to the most recent file.
Here, get this: http://d-h.st/3VD
Download speed should be faster as well. rename it PH85IMG and place it on your sd card after you relock your bootloader, then boot into bootloader, it's gonna detect the file and ask you if you wanna update, follow the on screen instructions to update, voila! Follow the basics to install the new energy rom.
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
It is useful, I fully agree with you, it's like we come here to answer the same questions over and over, but I'm just trying to be nice, cause I usually just say, read the amaze bible, but then they go and do something even more noobish, so to avoid the tear jerks I just give the basic info, though I'm fading away slowly.
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
I came across this issue. As earlier posts said, install the new ICS update. The partitions were messed up and the ruu will clean it up.
ten6 said:
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
Click to expand...
Click to collapse
Lol, never pointed fingers buddy, so calm down.
Maybe I should create a new topic but my issue is similar to this one except for the fact that I read quite a lot and tried quite a few things.
My situation is that I made a backup with cwm only booted not flashed so I have the 100% stock backed up, after this I flashed cwm and tried to install the Energy rom based on ics and that was my mistake as I used to be on a Nexus device I didn't have to worry about this.
So I got stuck on a bootloop and tried factory reset/wiping everything, tried to reinstall a stock ROM (t-mobile one as I only found a .exe for the videotron one and I did not feel like exploring the exe as I am a Linux user) by relocking bootloader and using the HTC method, tried to install manually the stock Kernel with Energy ROM using adb and fastboot commands, tried to restore my backup but nothing seems to work, I'm still bootlooping.
Is-it possible to s-off without a regular adb access (only the cwm adb access)? And would s-off allow me to flash anything as I wish? Is there a way to have any ROM working on my device? (i know the answer is yes to the last one, at least )
Thanks!
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
johnride said:
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
Click to expand...
Click to collapse
Okay okay, calm down, there's currently only one method of going about restoring your device since you're s-on and no you cannot s-off with just cwm adb, I think JB s-off method is only an exe file, never saw linux files anywhere on his site. Anyways, you have to use the GB exe for videotron and restore to stock via it then update to ics to use the most recent energy rom, BUT if you just want a working device, this is just an idea, though it should work fine, you can flash a custom recovery and flash the GB version of energy rom, you should be able to restore your backup as well, but you said you can't, which is odd, it may be because of the kernel not being flashable as since CWM cannot flash kernels while s-on, in which case I'd advise you to get 4EXT recovery and then try restoring your back once again, it should work fine since 4EXT can flash kernels while S-ON.
My two cents.
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
johnride said:
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
Click to expand...
Click to collapse
I got lost halfway through that post, after flashing a rom, if the kernel isn't flashed (reboots and does it automatically), then flash the kernel manually, should boot fine, does anyone ever really read anymore? This very issue both s-on and s-off has been answered more times today than I can count. If you read the details on JB's site, you'd see and know all you need to.
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
johnride said:
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
Click to expand...
Click to collapse
How did you go about flashing the kernel?
Sent from my SGH-T679 using xda app-developers app
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
johnride said:
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
Click to expand...
Click to collapse
Okay here's a few tips, cwm cannot flash kernels with son devices, get 4ext recovery for that. Second thing, reflash the from after doing a super wipe, if 4ext doesnt reboot and flash the kernel, do it manually, ill assume you know how to use ad, if not check my Bible tutorial on it, use the boot command for flashing boot images, take the boot file from the zip file, place it in the folder where your adb files are and flash it to your device while its in fastboot mode.
Sent from my SGH-T679 using xda app-developers app
Well, I think I have done all you mention above, the only thing i'm not sure to understand is what you mean by "super wipe" I found some executables about it but I guess it can't do much more than the flash all partitions (except external sdcard) in 4ext recovery wich I finally managed to install properly.
So, I made that global formatting thing, I tried to install an ICS based ROM and 4ext rebooted to install kernel, same bootloop. Tried to install manually the kernel that came with this rom via the classic fastboot flash boot boot.img. Same bootloop. Tried to put the modules manually via the recovery adb access (performing a mount -a in adb shell to have everything present in fstab mounted) and flashing this stock kernel with no more success.
Achieved the same operations with a GB based ROM (this one: http://forum.xda-developers.com/showthread.php?t=1535173) with both the faux and the stock kernel without any more success.
Did I miss something? Am I so dumb? Do you have any other rom to suggest that have higher chances to succeed?
Do you think trying to restore my sotck nandroid with 4ext has more chances to succeed?
Thanks, again and always!