I sold my TFP and was wondering if there are any tutorials on how to flash back to stock?
get outta here ya apple land lover....lmfao you stuck in the apple Matrix. they got you plugged in. they show you a nice new shiny screen n you Jump ship..SMH. its all good man. just busting your chops.
aside from that vv
I could've sworn I saw you said you unlocked your device in other threads. if this is true, there is no way to go back to stock. stock means you have a locked bootloader again. there is no relocking. if you want to go to stock firmware, look in developement section.
If it is unlocked, it will never be stock again. Otherwise, you can just root it and dd the blob file using the method detailed in the thread in the dev section about how to flash any version software,That will revert the kernel and boot and other stuff to stock and also unroot it. Then just do a factory reset/data wipe and you are good to go
I'm not concerned with the bootloader, I just want a stock looking ROM. Is that possible?
Sent from my Transformer Prime TF201 using xda premium
scook9 said:
If it is unlocked, it will never be stock again. Otherwise, you can just root it and dd the blob file using the method detailed in the thread in the dev section about how to flash any version software,That will revert the kernel and boot and other stuff to stock and also unroot it. Then just do a factory reset/data wipe and you are good to go
Click to expand...
Click to collapse
So can I atleast unroot and flash stock kernel and rom?
Sent from my Transformer Prime TF201 using xda premium
demandarin said:
get outta here ya apple land lover....lmfao you stuck in the apple Matrix. they got you plugged in. they show you a nice new shiny screen n you Jump ship..SMH. its all good man. just busting your chops.
aside from that vv
I could've sworn I saw you said you unlocked your device in other threads. if this is true, there is no way to go back to stock. stock means you have a locked bootloader again. there is no relocking. if you want to go to stock firmware, look in developement section.
Click to expand...
Click to collapse
I've had all android my life, never tried apple, don't hate lol ill be back. In the meantime help me out! I'm sticking with my galaxy nexus no iPhone here!
Sent from my Transformer Prime TF201 using xda premium
see the thing is, there have been several people who unlocked, used custom rom, then tried to flash back an official Asus stock rom and bricked their prime.
SO LET ME WARN YOU, IF YOU UNLOCKED, DO NOT TRY TO FLASH AN OFFICIAL ASUS ROM OR YOU WILL BRICK YOUR TABLET. ask Diamondback for proof. you could try unofficial versions. there is a stock rom but has some tweaks added to it like root n some other things. you have to look in developers section on it. I forgot the guy name. I think it may be Jermaine. look for his stock rom thread. just plz make sure to research it thoroughly first. wouldn't want you to brick your prime.
on another note, if you unlocked n flashed a custom rom, didn't you nandroid backup your stock rom first before flashing? if so then you can just flash/restore that nandroid backup you have through CMW manually.
demandarin said:
see the thing is, there have been several people who unlocked, used custom rom, then tried to flash back an official Asus stock rom and bricked their prime.
SO LET ME WARN YOU, IF YOU UNLOCKED, DO NOT TRY TO FLASH AN OFFICIAL ASUS ROM OR YOU WILL BRICK YOUR TABLET. ask Diamondback for proof. you could try unofficial versions. there is a stock rom but has some tweaks added to it like root n some other things. you have to look in developers section on it. I forgot the guy name. I think it may be Jermaine. look for his stock rom thread. just plz make sure to research it thoroughly first. wouldn't want you to brick your prime.
on another note, if you unlocked n flashed a custom rom, didn't you nandroid backup your stock rom first before flashing? if so then you can just flash/restore that nandroid backup you have through CMW manually.
Click to expand...
Click to collapse
Restoring a nandroid in CWM does not grab the kernel, he still has to do the blob method I detailed. I grabbed the blob from the official asus .15 zip and it has worked fine. Done it several times myself. Do that method and you are unrooted, stock recovery. Should be like all stock except for bootloader. You will still need to do a factory reset/data wipe I believe.
Deleted.
Sent from my HTC Mecha using XDA
scook9 said:
Restoring a nandroid in CWM does not grab the kernel, he still has to do the blob method I detailed. I grabbed the blob from the official asus .15 zip and it has worked fine. Done it several times myself. Do that method and you are unrooted, stock recovery. Should be like all stock except for bootloader. You will still need to do a factory reset/data wipe I believe.
Click to expand...
Click to collapse
How did you get back to stock recovery? OP of thread says that method will brick you if you are unlocked and rooted. Or am I looking at the wrong thread?
Sent from my HTC Mecha using XDA
I used this method:
http://forum.xda-developers.com/showthread.php?t=1492887
For what it is worth....that disclaimer was not up when I first tried it. I have the stock ROM with CWM and unlocked bootloader. It has worked fine for me....flashing the blob replaces the recovery with stock. I have done this 3 times without issue.....maybe I am lucky? Seems more like a CYA disclaimer to me. I can see NO reason why it would pose any threat, this code sits above the bootloader and would be the same whether unlocked or locked. the kernel would be the only concern....but it is replaced properly along with the recovery by the blob method
scook9 said:
I used this method:
http://forum.xda-developers.com/showthread.php?t=1492887
For what it is worth....that disclaimer was not up when I first tried it. I have the stock ROM with CWM and unlocked bootloader. It has worked fine for me....flashing the blob replaces the recovery with stock. I have done this 3 times without issue.....maybe I am lucky? Seems more like a CYA disclaimer to me. I can see NO reason why it would pose any threat, this code sits above the bootloader and would be the same whether unlocked or locked. the kernel would be the only concern....but it is replaced properly along with the recovery by the blob method
Click to expand...
Click to collapse
OK.thanks. so just dd that blob file to, in my case, internal sdcard and reboot and that's it, and that puts recovery and kernel back to stock?
Sent from my HTC Mecha using XDA
No. Place it on the sdcard, insert into tablet. When doing dd command, if=input file (file source) of=output file (destination). I used a USB Thumb drive actually, doesn't matter as long as you know where the blob is for the dd command
Make sure you properly locate the file for the if parameter and that you exactly input the value for of. Messing this up will probably brick the tab so be careful
scook9 said:
No. Place it on the sdcard, insert into tablet. When doing dd command, if=input file (file source) of=output file (destination). I used a USB Thumb drive actually, doesn't matter as long as you know where the blob is for the dd command
Make sure you properly locate the file for the if parameter and that you exactly input the value for of. Messing this up will probably brick the tab so be careful
Click to expand...
Click to collapse
Yeah I don't have an SD card.
Was hoping I could just do it from the internal sdcard..oh well thank you for the info
Sent from my HTC Mecha using XDA
You can do it from the internal SD Card/memory. Just have to change the path given for if=
You will need a computer at some point though as I am not sure there is a good method to extract the blob itself within android.
scook9 said:
You can do it from the internal SD Card/memory. Just have to change the path given for if=
You will need a computer at some point though as I am not sure there is a good method to extract the blob itself within android.
Click to expand...
Click to collapse
Cool.laptop I have...so I will give it a shot. Thanks
Sent from my HTC Mecha using XDA
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 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.
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!
Well, here goes nothing.... With a little effort, I've got this done...
1. A system partition nandroid of the Jelly Bean 10.4.2.15 update created using TWRP 2.2.2
2. A modified TWRP 2.2.2 recovery which works with the new bootloader
This system nandroid image has been created for developer use. So, it's not for everyone to play around with. It does not have the new bootloader or boot image, both of which are required to use this system image. It was created using my modified copy of the TWRP 2.2.2 recovery image.
The TWRP 2.2.2 recovery image below is a modified version of the original TWRP 2.2.2 recovery (credits TeamWin). I have merely replaced the kernel within the recovery image with the new JB kernel, thereby allowing it to work with the new bootloader. This is an un-blob'd recovery image. If you wish to directly flash this image, you need to have nvFlash enabled. Else you need to make a blob pack and flash it.
I've now added a zip with the de-odexed system apps and framework jar. This zip only has the /system/app & /system/framework folders. Just to make it easier if anyone wants to create an update zip.
I've also added blobpacked version of the new JB bootloader, kernel, stock recovery and my modified TWRP recovery. Be careful. If you don't know what your are doing and don't have nvFlash enabled, you could brick your device.
USE AT YOUR OWN RISK!!! THE NEW TF201 JB BOOTLOADER IS ESSENTIAL REQUIREMENT!!! BE CAREFUL OR YOUR COULD BRICK YOUR DEVICE
Let the modding begin!!!
tf201-jro03c-system.ext4.win (The system nandroid image)
twrp-2.2.2-jb.img (The un-blob'd modified TWRP recovery)
tf201-jro03c-deodex.zip (De-odexed system apps and framework jars only)
tf201-jb-bootloader.blob (Blobpack of the new JB bootloader)
tf201-jb-kernel.blob (Blobpack of the new JB kernel)
tf201-jb-stock-recovery.blob (Blobpack of the new JB stock recovery)
tf201-jb-twrp-recovery.blob (Blobpack of the my modified TWRP recovery)
I've use Wook's custom JB TWRP , Can I use this system NANDROID?
Thanks for posting.
Are you going to post the boot image?
Turge said:
Thanks for posting. Can you fix the link to the boot image? It's just pointing to d-h.st.
Click to expand...
Click to collapse
If anyone else needs this its at the link here, Craig was working hard and missed it
http://d-h.st/JMk
Thanks for putting this together Craig, you've done alot for us as of late, loved your CM10 builds
thank you for pulling this together, i look forward to what comes from this
ravenholm said:
I've use Wook's custom JB TWRP , Can I use this system NANDROID?
Click to expand...
Click to collapse
Wookie modified it so it would work for the TF300 JB base so my guess would be no.
Trying to get from HB 1.2 to stock JB with Nvflash bootloader as well...
---------- Post added at 05:52 PM ---------- Previous post was at 05:47 PM ----------
craigacgomez said:
Well, here goes nothing.... With a little effort, I've got this done...
1. A system partition nandroid of the Jelly Bean 10.4.2.15 update created using TWRP 2.2.2
2. A modified TWRP 2.2.2 recovery which works with the new bootloader
...
Click to expand...
Click to collapse
A little pointer here guys would be appreciated? Just where do I start with these files e.g. let's say from Stock ICS .28 to get to this one? e.g. copy files to device internal SDcard or use from PC? I see the one file is named .win? Not sure how to handle that?
Moe5508 said:
Trying to get from HB 1.2 to stock JB with Nvflash bootloader as well...
---------- Post added at 05:52 PM ---------- Previous post was at 05:47 PM ----------
A little pointer here guys would be appreciated? Just where do I start with these files e.g. let's say from Stock ICS .28 to get to this one? e.g. copy files to device internal SDcard or use from PC? I see the one file is named .win? Not sure how to handle that?
Click to expand...
Click to collapse
if you don't know what to do with these files, DO NOT DO ANYTHING WITH THEM.
I cannot stress this enough ATM. Yes, we know what to do with them, but until it is deemed safe, or until a better was of flashing is created, only very experienced users/devs should try this.
biggem001 said:
if you don't know what to do with these files, DO NOT DO ANYTHING WITH THEM.
I cannot stress this enough ATM. Yes, we know what to do with them, but until it is deemed safe, or until a better was of flashing is created, only very experienced users/devs should try this.
Click to expand...
Click to collapse
Em, boss, I hear you but we've probably not understood one another on the kind of clarity I'm looking for? What's the reference point for using this? (e.g. current ROM, operating system of PC etc etc)
For example am running a Linux machine at the moment and can easily run the following command to flash the recovery image using fastboot:
./fastboot-linux -i 0x0b05 flash recovery twrp-2.2.2-jb.img
or something to that effect and then would continue to reboot to recovery, copy the nandroid and restore from there?
Anyway, never mind...I take your advice and keep my fingers clear...
Moe5508 said:
Em, boss, I hear you but we've probably not understood one another on the kind of clarity I'm looking for? What's the reference point for using this? (e.g. current ROM, operating system of PC etc etc)
For example am running a Linux machine at the moment and can easily run the following command to flash the recovery image using fastboot:
./fastboot-linux -i 0x0b05 flash recovery twrp-2.2.2-jb.img
or something to that effect and then would continue to reboot to recovery, copy the nandroid and restore from there?
Anyway, never mind...I take your advice and keep my fingers clear...
Click to expand...
Click to collapse
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Ahhh, waiting a few more weeks/months wont hurt anyone ;p
jermaine151 said:
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Click to expand...
Click to collapse
Is it possible to take the bootloader from the its system dump file that's floating around? Or can twrp also backup downloader?
Sent from my HTC Sensation Z710e using xda premium
jermaine151 said:
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Click to expand...
Click to collapse
Yay, thanks for working on that! I am tempted to flash the jb stock image (from unpack) and do all the above, but still, I'd rather have a more reliable method step by step instruction set.
And yes, there is a new partition scheme. Flashing the image with old partition scheme intact will cause errors that could be fixed by nvflash.
Hawke84 said:
Is it possible to take the bootloader from the its system dump file that's floating around? Or can twrp also backup downloader?
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Yes, the bootloader is out but just give me a little time to fix wifi and you'll have a safe package to flash. I don't post threads here so you'll find it at rootz. I will post a link in this thread. That's assuming that someone else doesn't post a stock JB build for unlocked bootloaders before I do.
I've now added a zip with the de-odexed system apps and framework jar. This zip only has the /system/app & /system/framework folders. Just to make it easier if anyone wants to create an update zip.
Any I'm going to state this again... unless you have the new TF201 JB bootloader, do not attempt to use the recovery or nandroid image...
jermaine151 said:
Yes, the bootloader is out but just give me a little time to fix wifi and you'll have a safe package to flash. I don't post threads here so you'll find it at rootz. I will post a link in this thread. That's assuming that someone else doesn't post a stock JB build for unlocked bootloaders before I do.
Click to expand...
Click to collapse
Thanks, no rush mate
Sent from my HTC Sensation Z710e using xda premium
I think I understood this correctly but if I'm going to be able to flash this with an unlocked bootloader (I flash cm10 nightlies with cwm) Jermaine or whomever will be getting a pretty good chunk of my paycheck.... I use cm10 on a lot of my devices but it's not the best on the prime. I regret unlocking my bl but I know there's a way for official tfp jb.....
Regards,
Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
ManOnTheMoon said:
I think I understood this correctly but if I'm going to be able to flash this with an unlocked bootloader (I flash cm10 nightlies with cwm) Jermaine or whomever will be getting a pretty good chunk of my paycheck.... I use cm10 on a lot of my devices but it's not the best on the prime. I regret unlocking my bl but I know there's a way for official tfp jb.....
Regards,
Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
Click to expand...
Click to collapse
Yes, we will soon have an update zip for unlocked users... I have created an update zip, but haven't tested it yet... and jermaine has one in the works too...
I've also added blobpacked version of the new JB bootloader, kernel, stock recovery and my modified TWRP recovery. Be careful. If you don't know what your are doing and don't have nvFlash enabled, you could brick your device.
craigacgomez said:
Yes, we will soon have an update zip for unlocked users... I have created an update zip, but haven't tested it yet... and jermaine has one in the works too...
Click to expand...
Click to collapse
Let me know if u want me to test I have nvflash and some time this evening. I also half know what I'm doing
Sent from my HTC Sensation Z710e using xda premium
TL;DWR: I want to go back to absolute zero and revert my phone to factory. I'm new to android and just followed a youtube video guide to root and unlock boot loader and now don't know how to go back.
Hey guys, I am completely new to android and have been with iPhone for about 7 years so please forgive me for my questions as they are elementary in comparison with the topics that are typically discussed on here.
I decided to switch it up and try an M8 cause the build quality and screen really excited me so I sold my iPhone and made the switch. I was in absolute love for about a week while on stock. Just learning android and all it's small quirks was fun for me.
but now, I have the phone up for sale, I'm amazed at how convoluted it is just to return to stock after rooting and roming. I spent 6 hours last night with a phone that wouldn't boot and just hang at the opening htc one opening boot animation.
I installed TWRP, unlocked the boot loader and used Hassoon2000's all in one toolkit to root as well. I used this video posted on the toolkit thread on here to help guide me.: https://www.youtube.com/watch?v=Krw6H4gQ6g0&feature=youtu.be
I followed the video to a tee with some stops on my side cause what he said in the video didn't always happen on my end, so I would unplug my phone and plug it back in and continue where I left off until the whole process worked. It's at the very end when he used twrp to reboot back into his "normal phone" that my phone just hung on the HTC boot animation.
I have all neccasary drivers and software installed to run this the toolkit and still received the "error: no device found" from time to time when using the kit. so you can imagine all the hair I pulled out coming from jailbreaking an iPhone with one click to trying just to root my device to disable ads and not can't even use my phone.
after some digging to find what I thought what supposedly a stock rom/img/Whateverthenameis for my phone, I breathed a sigh of relief and flashed it using tarp adb side load option and it finally booted up. I now however don't have working Wi-Fi and some apps that came preinstalled on my phone are missing. I don't like and just feel like it's a buggy mess.
long story short, I just want to go back to absolute zero. all the way stock; I don't even care about keeping any root or unlock. It would be nice so I can adblock but I don't care about it if it will stop me from going back to zero.
Here are all the tools I used to ruin my android experience aka the tools I mentioned above:
Toolkit (thread): http://forum.xda-developers.com/showthread.php?t=2699065
rom/img/whateveritscalled that i used to get back into a buggy phone: http://www.androidfiles.org/?developer=M8&folder=StockRoms
video guide I used: https://www.youtube.com/watch?v=Krw6H4gQ6g0&feature=youtu.be
I ran all this on a Windows 7 64-bit desktop machine.
Did you flash the Shipped RUU?
orangekid said:
Did you flash the Shipped RUU?
Click to expand...
Click to collapse
I barely understood how to flash the rom I found to get my phone back on but how do I flash an ruu and where do i get it?
orangekid said:
Did you flash the Shipped RUU?
Click to expand...
Click to collapse
I would also love to know how to do this, I desperately need help
I think there was a shipped RUU for the M8 that could be used to go full stock, I'll see if I can find it.
RUU = Rom Update Utility, which was named that back in the old WinMo days. This would just be a file that you either flash thru SD via fastboot or thru your computer.
orangekid said:
I think there was a shipped RUU for the M8 that could be used to go full stock, I'll see if I can find it.
RUU = Rom Update Utility, which was named that back in the old WinMo days. This would just be a file that you either flash thru SD via fastboot or thru your computer.
Click to expand...
Click to collapse
If you could find that it would be most appreciated
I just looked and couldn't find one. Would this be the only way to revert to stock from either a bad flash, boot loop or just plain want to be stock again. I want to root but I'm just not confident enough to use the toolkit without any handups. At least if I knew how to get back to stock I wouldnt worry as much.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Word around was that there has been no RUU released for our device yet. There is a stock rooted TWRP recovery image on the Android Development forum but that's probably the closest you will get. I'm not sure if a straight up factory reset would do it or not, but you would need to flash the stock recovery as well. Overall a pretty drawn out process, especially if you are unfamiliar with adb and fastboot. You might have to wait for a RUU
Sent from my HTC One_M8
TheEmpyre said:
Word around was that there has been no RUU released for our device yet. There is a stock rooted TWRP recovery image on the Android Development forum but that's probably the closest you will get. I'm not sure if a straight up factory reset would do it or not, but you would need to flash the stock recovery as well. Overall a pretty drawn out process, especially if you are unfamiliar with adb and fastboot. You might have to wait for a RUU
Sent from my HTC One_M8
Click to expand...
Click to collapse
What would happen if I clicked att software update in settings? would it do something or no? Would it crash the whole phone?
TheEmpyre said:
Word around was that there has been no RUU released for our device yet. There is a stock rooted TWRP recovery image on the Android Development forum but that's probably the closest you will get. I'm not sure if a straight up factory reset would do it or not, but you would need to flash the stock recovery as well. Overall a pretty drawn out process, especially if you are unfamiliar with adb and fastboot. You might have to wait for a RUU
Sent from my HTC One_M8
Click to expand...
Click to collapse
I thought I saw a leaked RUU floating around that did the job..
RACEnSK8 said:
What would happen if I clicked att software update in settings? would it do something or no? Would it crash the whole phone?
Click to expand...
Click to collapse
It probably would not find one, but if it did nothing good would happen, it won't successfully take an OTA with a custom ROM, recovery, etc..
Non-rooted nand backup,which can be used to go back to stock
http://forum.xda-developers.com/showpost.php?p=51953376&postcount=352
Wonders_Never_Cease said:
Non-rooted nand backup,which can be used to go back to stock
http://forum.xda-developers.com/showpost.php?p=51953376&postcount=352
Click to expand...
Click to collapse
I think I need to find someone to help me, because I never had to deal with rooted devices before. So i wouldn't even know what to do with the files you posted
RACEnSK8 said:
I think I need to find someone to help me, because I never had to deal with rooted devices before. So i wouldn't even know what to do with the files you posted
Click to expand...
Click to collapse
It's pretty simple actually.
If you are using TWRP recovery, just place this in that folder on your SD card, boot into recovery, and hit "restore"
it will restore a stock ROM on your device.
Use the recovery version he mentions though.
orangekid said:
It's pretty simple actually.
If you are using TWRP recovery, just place this in that folder on your SD card, boot into recovery, and hit "restore"
it will restore a stock ROM on your device.
Use the recovery version he mentions though.
Click to expand...
Click to collapse
How do I figure out what recovery i have
RACEnSK8 said:
How do I figure out what recovery i have
Click to expand...
Click to collapse
reboot the phone into recovery (your power menu might have the option) and it will give you the version.
You can also access it from fastboot, or adb (typy adb reboot recovery)
RACEnSK8 said:
I think I need to find someone to help me, because I never had to deal with rooted devices before. So i wouldn't even know what to do with the files you posted
Click to expand...
Click to collapse
Yea, android phones are a complete different world then that of iPhones. I was in your shoes a yr after the ip4 release. I didn't jump right in...I didn't flash or root my 1st phone for months. To be fair, not all android phones have difficult root/restore methods...most I've used were 1 click, same goes for jb programs. The only thing I can think of that iPhone had a slight edge was if you bricked from a bad app or jb...DFU and restore thru iTunes but then you worry about restoring to the new firmware...waiting for the next exploit and praying its not tethered. If iPhone is your thing...great but don't bounce from android after your 1st set back...it happens to all of us.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
orangekid said:
reboot the phone into recovery (your power menu might have the option) and it will give you the version.
You can also access it from fastboot, or adb (typy adb reboot recovery)
Click to expand...
Click to collapse
I went into recovery and it says PhilZ Touch 6.25.5
Clockworkmod v6.0.4.7
nash2000 said:
Yea, android phones are a complete different world then that of iPhones. I was in your shoes a yr after the ip4 release. I didn't jump right in...I didn't flash or root my 1st phone for months. To be fair, not all android phones have difficult root/restore methods...most I've used were 1 click, same goes for jb programs. The only thing I can think of that iPhone had a slight edge was if you bricked from a bad app or jb...DFU and restore thru iTunes but then you worry about restoring to the new firmware...waiting for the next exploit and praying its not tethered. If iPhone is your thing...great but don't bounce from android after your 1st set back...it happens to all of us.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, luckily I went from WinMo to iOS, so I went from "if you flash one wrong file you're bricked" to "I cannot brick this device if I try"
coming back to Android was like the WinMo days.
Depends what you have too, my daily is a Nexus 5, pretty easy to do anything on it. Samsung are really easy too, you just Odin a factory tar no matter where you are for the most part.
But HTC is the difficult one, all these tokens and issues and hboot versions and patches etc...
You get used to it though, and then it doesn't seem so daunting...
In this case, these are things OP needs to know if he is going to mess with any Android phones, basic things like recovery and basic ADB / fastboot commands etc...
RACEnSK8 said:
I went into recovery and it says PhilZ Touch 6.25.5
Clockworkmod v6.0.4.7
Click to expand...
Click to collapse
Ok,
You need to flash TWRP:
http://forum.xda-developers.com/showthread.php?t=2695709
orangekid said:
Ok,
You need to flash TWRP:
http://forum.xda-developers.com/showthread.php?t=2695709
Click to expand...
Click to collapse
So how do I do that?
Sorry for being such a noob, but I just want my wifi to work lol