Related
For anyone who wants it, here's the STOCK PRE & Post-OTA recovery images. (I just added PRE-OTA if for some reason it's needed down the road.)
If you plan on flashing it back over the ClockWork recovery image, make sure S=OFF otherwise the flash won't complete successfully.
You can turn S=ON back after the flash.
THIS IS NOT A FLASHABLE ZIP - I only zipped it to get it to upload as an attachment! You will need to do a Fastboot Flash to install (there may be other methods but Fastboot is what I used).
Below are instructions I am borrowing from the Amen-Ra recovery installation from the N1 - they will apply the same here!
via fastboot
Code:
Copy recovery.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding volume down, then select fastboot)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery.img
via terminal app
Code:
Copy recovery.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter)
I hope this proves to be useful to at least 1 person!
Thanks a lot!
MYT4G (Glacier)
sounds like a good way to restore...now all we need are some roms
The reason I dug this up was that I am very curious as to whether after having rooted, if you have stock recovery and S=ON whether or not further OTAs will come to you.
Back in my N1 days if the stock recovery was not present an OTA couldn't install.
Sweet! Was looking for the stock recovery before exchanging my mytouch. Where/how did you get this?
Great contribution
c_licious said:
Sweet! Was looking for the stock recovery before exchanging my mytouch. Where/how did you get this?
Click to expand...
Click to collapse
Actually I merely extracted them from the stock Rom here on xda and from the ota update file someone posted but nobody has figured out how to apply. Both have been tested on my phone.
I figured I would make it easier on everyone who simply wants to download the recovery as opposed to the entire rom or update.
Does this then solve the problem people have of not being able to root because they downgraded? If so, we may not need that OTA update link anymore.
kitsunisan said:
Does this then solve the problem people have of not being able to root because they downgraded? If so, we may not need that OTA update link anymore.
Click to expand...
Click to collapse
Check this thread out - I was just reading it, should help out!
http://forum.xda-developers.com/showthread.php?t=843428
Nevermind, wasn't paying attention when I posted, thought it was something else. Still, will come in very handy for me, I just got my replacement today, and replacing clockwork recovery was the last thing I needed to do.
JWhipple said:
The reason I dug this up was that I am very curious as to whether after having rooted, if you have stock recovery and S=ON whether or not further OTAs will come to you.
Back in my N1 days if the stock recovery was not present an OTA couldn't install.
Click to expand...
Click to collapse
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
You got the first one after reverting back from being rooted?
gaww said:
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
gaww said:
Thanks for making these available. I also wanted to get the recovery to hopefully let me get OTA's again (got the first one).
I was hoping I could do so with everything stock (unroot with visionary) but also being able to leave s=off - does that absolutely have to be set back =on?
Click to expand...
Click to collapse
Not sure - but if you want to "appear" to be 100% stock w/ OTA update, probably best to set it to S=ON.
The thing is though, my understanding is that if even if you use the unroot, you still will have persistent root unless HTC or Google somehow patches the exploit that was used to get root in the first place. So, you'll have root but won't be able to change anything on the ROM unless you turn S=OFF again. I ran the unroot and S=ON and still have the ability to do everything (other than mess with the ROM) that your standard Rooted phone would be able to.
jjlean said:
You got the first one after reverting back from being rooted?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
You can force install the first OTA, but without forcing it I don't believe it's going to happen.
http://forum.xda-developers.com/showthread.php?t=843428 shows how to do it.
JWhipple said:
You can force install the first OTA, but without forcing it I don't believe it's going to happen.
http://forum.xda-developers.com/showthread.php?t=843428 shows how to do it.
Click to expand...
Click to collapse
I got the first OTA before doing s=off (needed the OTA to make it work at the time - did it first day).
I am trying to find out about the second OTA, about which there is practically no information available. I would I assume I have to have the first one installed to get the second (but what is it?).
Again - thanks for posting the original stock recoveries - have a feeling I may need one down the road (like when 2.3 finally comes out and I have a reason to go back to stock).
I've yet to see anyone say that they have actually received a 2nd OTA... Go figure?
Would I be able to use this recovery image to get my phone back up an running again?
I was messing around trying to apply the custom animations and somehow ended up getting my phone stuck in a constant reboot mode.
I have done some research and think that I am on the right track, but can someone verify this for me?
I have permroot with S-OFF, factory reset from the bootloader menu does not get me anywhere, but the phone is recognized through the "fastboot" prompt.
Would I just place the recovery image in the root of the sd card and run these commands?:
fastboot erase recovery
fastboot flash recovery.img
Thanks in advance for any help
From terminal im getting image not found? Do I have to mount or something?
Also... From pc ....Put .img in a place where fast boot can see it, where is thay
Sent from my HTC Glacier using XDA App
Ok guys, the absolute easiest way to do this... This is dependent upon you having S=OFF.
1) Install the android SDK....
2) In my case, fastboot is in C:\sdk\tools as I installed the SDK to C:\SDK. For fastboot to see the image file, I placed the image file (after extracted from the .ZIP) into the C:\sdk\tools folder.
3) Shut down the phone. Turn it back on while holding down the VOL-DOWN button.
4) On the bottom of the screen you'll see:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
5) FASTBOOT should already be highlighted. Press the POWER button.
6) If your USB isn't already plugged in, do it now.
7) Give the PC max of 30 seconds to recognize the bootloader mode.
8) From a DOS prompt, navagate into the C:\SDK\TOOLS folder.
9) Type "FASTBOOT DEVICES" (less the quotes) and press ENTER. If your phone is recognized it should show the serial info of your phone.
10) Type "FASTBOOT FLASH RECOVERY RECOVERY.IMG" (again, less the quotes) and press ENTER .
11) You should see the send and receive. If you do, SUCCESS.
I was able to do all of the steps listed, but I keep getting stuck at a boot loop.
Fastboot recognized my phone, flash recovery from fastboot says that it is successful, but still no luck.
Sent from my HTC HD2 using XDA App
Hello all, I was wondering if anyone can point me in the right direction. I have a acer iconia a100 rooted and currently running the carbon rom (4.2.2) and twrp recovery (2.6.3.0). I would like to go back to stock rom (ICS). I have not changed any kernals or anything like that. Can I just restore my nandroid backup of my stock rom or is there something specific I have to do? Also, I just looked and I dont have a stock backup with twrp, only with cwm. When I unlocked bootloader, I installed cwm, then must have done a backup of stock rom, then flashed carbon rom, then switched to twrp and made another backup so I would have to go back to cwm to restore nandroid. How do I go back to cwm from twrp?? Thanks for the feedback.
I looked in my internal storage and it looks like I have 2 zips, fastbootrecovery.zip and xsposeddisabler-cwm.zip, do I flash one of these?? and if I do, can I do it with es explorer?? Thanks
jreink01 said:
Hello all, I was wondering if anyone can point me in the right direction. I have a acer iconia a100 rooted and currently running the carbon rom (4.2.2) and twrp recovery (2.6.3.0). I would like to go back to stock rom (ICS). I have not changed any kernals or anything like that. Can I just restore my nandroid backup of my stock rom or is there something specific I have to do? Also, I just looked and I dont have a stock backup with twrp, only with cwm. When I unlocked bootloader, I installed cwm, then must have done a backup of stock rom, then flashed carbon rom, then switched to twrp and made another backup so I would have to go back to cwm to restore nandroid. How do I go back to cwm from twrp?? Thanks for the feedback.
I looked in my internal storage and it looks like I have 2 zips, fastbootrecovery.zip and xsposeddisabler-cwm.zip, do I flash one of these?? and if I do, can I do it with es explorer?? Thanks
Click to expand...
Click to collapse
Just the stock ROM or completely back to stock, 100%?
If you don't know what those zips are, or how to use them, then don't use them, period.
To get back cwm you can use fastboot to flash it back on or use one of the cwm installers in development, if any are still there, if you want to do it with fastboot you'll need some stuff to get ready, most of it should be there from when you rooted the first time, then a couple lines in a command prompt and you'll have it back. There's also stock rooted ICS ROMs available, so depending on what you want we can go from there.
Tapatalked from my HTC DNA - Akakaze
pio_masaki said:
Just the stock ROM or completely back to stock, 100%?
If you don't know what those zips are, or how to use them, then don't use them, period.
To get back cwm you can use fastboot to flash it back on or use one of the cwm installers in development, if any are still there, if you want to do it with fastboot you'll need some stuff to get ready, most of it should be there from when you rooted the first time, then a couple lines in a command prompt and you'll have it back. There's also stock rooted ICS ROMs available, so depending on what you want we can go from
I am going to sell my tablet so I would like to go to my backup of my stock rom. When I restore my stock backup, I can just do a full wipe, that will get me back to the starting point of just the basic rom, right?? That will wipe all my data from the backup rom, or will a full wipe erase the rom too?? I want to get back to the basic rom (just like if I install a new rom) have to set up accounts, wifi, etc).
Also, is there a tutorial or a step by step guide to reinstall cwm back on my tablet, since my stock rom was backed up with cwm? And where do I have the files to reflash cwm. Thanks for your assistance in helping me return my tablet to the state I want.
Click to expand...
Click to collapse
I found a site that has it step by step, installing cwm. Here it is.
Here it is guys, Stock CWM Recovery for the ACER A100.
Before anything make sure you have the latest ICS leak C/O Vache, Root, and Unlocked Bootloader.
Official ICS Leak c/o Vache:
http://forum.xda-developers.com/show....php?t=1510706
Root Instructions here:
http://forum.xda-developers.com/show....php?t=1531646
Unlock your bootloader for fastboot, follow here:
http://forum.xda-developers.com/show....php?t=1557445
once you have done all of the above, you should be ready to flash this recovery. Make sure you have ADB up and working properly. And place the recovery.img in your working folder (see below)
1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
But it says make sure you have the latest ics leak?? Are they refferring to the rom?? If so, I currently have carbon rom istalled which is jellybean. This will not work then?? I am a little confused and any feedback would be greatly appreciated.
jreink01 said:
I found a site that has it step by step, installing cwm. Here it is.
Here it is guys, Stock CWM Recovery for the ACER A100.
Before anything make sure you have the latest ICS leak C/O Vache, Root, and Unlocked Bootloader.
Official ICS Leak c/o Vache:
http://forum.xda-developers.com/show....php?t=1510706
Root Instructions here:
http://forum.xda-developers.com/show....php?t=1531646
Unlock your bootloader for fastboot, follow here:
http://forum.xda-developers.com/show....php?t=1557445
once you have done all of the above, you should be ready to flash this recovery. Make sure you have ADB up and working properly. And place the recovery.img in your working folder (see below)
1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
But it says make sure you have the latest ics leak?? Are they refferring to the rom?? If so, I currently have carbon rom istalled which is jellybean. This will not work then?? I am a little confused and any feedback would be greatly appreciated.
Click to expand...
Click to collapse
Does anyone have any suggestions?? Thanks
Well, before the tab got official ICS, we had a leak. If you had read down the topics some you would've found it. You do not want cwm, you want twrp.
Sent from my SPH-L710 using xda app-developers app
das_webos_transformer said:
Well, before the tab got official ICS, we had a leak. If you had read down the topics some you would've found it. You do not want cwm, you want twrp.
Does anyone have any suggestions on whether it is ok to do this? Thanks
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I need cwm to restore my stock rom. If I use the steps quoted below to reinstall cwm, will I run into any problems since I'm coing from carbon rom (jellybean) to stock rom which is (ICS)?
jreink01 said:
I need cwm to restore my stock rom. If I use the steps quoted below to reinstall cwm, will I run into any problems since I'm coing from carbon rom (jellybean) to stock rom which is (ICS)?
Click to expand...
Click to collapse
Does anyone know if this how to guide is good to use when coming from carbon rom (jellybean) to stock rom (ics))? Thanks
jreink01 said:
Does anyone know if this how to guide is good to use when coming from carbon rom (jellybean) to stock rom (ics))? Thanks
Click to expand...
Click to collapse
To just go back to stock to sell it you'll run into a couple issues coming from 4.2+, namely the storage path changes, you'll retain the /0 folders, however many were made. Otherwise following the guide that roman made will work to go back to 100% stock, I'll see if I can get a link, I'm in a waiting room with crappy data lol
Edit:
That guide will work for installing cwm, basically get your cwm image then get fastboot going, fastboot flash recovery cwmimageyougot.IMG
http://forum.xda-developers.com/showthread.php?p=33574648
Best way to return to 100% stock. No need to fuss with recoveries just install what he says then the ROM does the rest. While in twrp remember to go delete /0 directories or they'll remain there forever. Or until its deleted at a later date, but if you have stuff in there you should do it prior to going fully stock again.
Tapatalked from my HTC DNA - Akakaze
pio_masaki said:
To just go back to stock to sell it you'll run into a couple issues coming from 4.2+, namely the storage path changes, you'll retain the /0 folders, however many were made. Otherwise following the guide that roman made will work to go back to 100% stock, I'll see if I can get a link, I'm in a waiting room with crappy data lol
Edit:
That guide will work for installing cwm, basically get your cwm image then get fastboot going, fastboot flash recovery cwmimageyougot.IMG
http://forum.xda-developers.com/showthread.php?p=33574648
Best way to return to 100% stock. No need to fuss with recoveries just install what he says then the ROM does the rest. While in twrp remember to go delete /0 directories or they'll remain there forever. Or until its deleted at a later date, but if you have stuff in there you should do it prior to going fully stock again.
Tapatalked from my HTC DNA - Akakaze
Click to expand...
Click to collapse
Thanks for the response, youve fully confused me with the /0 folders?? What exactly is that?? When I go to es file explorer, I see sdcard0 (which looks like the internal storage) and sd01 which looks like my ext sd card. Is it one of those your are talking about??
Also, you said something about go delete in twrp, I went into twrp and did not find anything with that name?? am I deleteing something in twrp. Could you spell it out for me since I am a noob when it comes to reverting a device to stock. Thanks for taking the time to explain this.
jreink01 said:
Thanks for the response, youve fully confused me with the /0 folders?? What exactly is that?? When I go to es file explorer, I see sdcard0 (which looks like the internal storage) and sd01 which looks like my ext sd card. Is it one of those your are talking about??
Also, you said something about go delete in twrp, I went into twrp and did not find anything with that name?? am I deleteing something in twrp. Could you spell it out for me since I am a noob when it comes to reverting a device to stock. Thanks for taking the time to explain this.
Click to expand...
Click to collapse
that is something happening with cwm. i had this problem. it keeps creating a folder names 0 and keep moving old files into that whenever you install a new rom.
Hello guys. I need your feedback. I have a A100 that is rooted and is currently running carbon rom 4.2. I am going to be selling this in the next couple weeks because I just don't use it anymore now that I have a second pc.Do you think it would be more advantagious to sell this just the way it is (rooted and custom rom) or should I take it back to completely stock? Or if it is more advantagious to sell it with a custom rom, which rom would you guys suggest?? Thanks again for any and all suggestions.
Please Help!! I was trying to go to stock ics and these are the steps I used.The simple method to revert back to stock ICS from a custom ROM on an A100.
+++Locked bootloader, no custom recovery, no root. Full stock .014 rom. It will recieve OTA updates to latest Acer version.+++
Get Ready
1) Download this flashable Stock recovery zip, and place in your normal flashing location, - Thx 4 help pio
http://db.tt/VLmnMCzq
Also uploaded below
2) Download the Official .014 Stock ICS rom
The stock ICS zip from zeronull. http://forum.xda-developers.com/show....php?t=1611696
Here is a second link to it. http://ubuntuone.com/7DZtbNqZzOk7qsaQxNk99a - thx zleto
3) Rename the Stock ICS rom to "update.zip", no quotes (make sure you have "hide known file extensions" UNCHECKED, in the folder options). And place it on the root of your microSD card. This will allow you to see the file extension to verify that it is named properly.
Get it Done
1) Flash the Stock recovery zip with your custom recovery. Then wipe cache, davlik cache, and wipe data/factory reset.
2) Reboot to system.
3) Allow it to sit for 5 minutes or so.
4) Then Power off.
5) Update from the microSD card by holding down the power and volume rocker closest to the corner at the same time, until you see "erasing cache .".. ect, ect. The stock rom install should start by itself, dont touch anything, wait for it to reboot.
****** If it won't boot do a factory reset (with the hardware buttons, see below) and/or try to reflash the ics rom one more time. ******
Quote:
To perform a Factory Data Reset use the following steps:
1.Place the rotation lock switch in the up position (tablet held in portrait). Or to the left if held in landscape.
2.Press and hold the Volume down button, which is located farthest from the corner (it is volume up, if held in landscape).
3.With the Volume down button held, press and hold the Power button for 3 seconds then release it. Continue holding the Volume down button.
4.Once the tablet vibrates, switch the rotation lock on and off repeatedly while still holding the Volume down button.
5.Release the Volume down button and stop switching the rotation lock once the "Erasing Userdata..." message appears in the upper left corner of the screen
Now I get the android symbol with the red triangle, that stays for about a minute, then it reboots and stays on thye acer screen. When I did the steps and was going to reboot, I received a waring while in recovery sayiny that I dont have a op installed. I did it anyway, as posted and now I'm stuck, can anyone PLEASE help me.I tried doing a reset with steps 2 though 4 but while pressing the vol up and letting go of the power button, it does not vibrate.
I try to boot into recovery with vol up + power, it boots than says erasing cache, then booting into recovery, the the android synbol comes up with the red triangle.
I can't even get into recovery. It says bootloader (unlock mode) when I pwer it on. If I press power + vol up, it says erasing cache, then booting into recovery kernal, then the android symbol comes up with the red triangle.Thanks for responding and since this is the wrong thread, can we discuss this in the other thread?? While I was typing this, the android symbol with the triangle was on the screen for about 2 minutes, then it just rebooted and now its saying acer acer acer acer acer on the bottom of the screen.
Can anyone help me out with this please?
Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks
ovimunt said:
Hi,
This may be a stupid question but I'm new to Samsung phones so I don't know all the details (I've only been using HTC so far).
So I've followed all the steps and got root fine. However, I tried to reboot into recovery afterwards and it's like Clockworkmod has vanished.... It just gets into what looks to me like the stock recovery. Am I doing something wrong or does the phone automatically restore its stock recovery???
Also, can someone explain to me if it is possible to manually flash a recovery from the img file using fastboot like you do on HTC phones?
Oh, and another thing. What's this Odin thing? I never used anything like that with HTC...
Thanks
Click to expand...
Click to collapse
May I ask what variant you are using? GT-i9195?
Then please boot your phone into download mode, this can be done by first switching of your phone completely then holding the power button, home button and volume down button until the download screen appears where you press continue. Once you have done that connect your phone using the usb cable and make sure all drivers have been installed! Once the drivers are installed start up Odin uncheck the f.rest time box and click the AP section and then select the recovery file provided by Sir Arco in the root thread.
If you need more help please ask, If it worked then still reply
Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.
Whosat said:
Odin is the software used to flash files to Samsung phones.
You will need to catch the first recovery boot after flashing the recovery image, or else the stock recovery will be reflashed once the phone boots up. Just reflash the recovery via Odin and make sure to boot into recovery right after the phone reboots after the flash.
Click to expand...
Click to collapse
Thanks for the response. Yeah, I kind of realized that's what's happening. I've managed to boot into the custom recovery right after the flash and did what I had to do in there, but then after I reboot the phone again, the custom recovery is gone. Is there a way to stop stock recovery being reflashed automatically?
Also, if I want to install a custom kernel, how can I backup the current one so that I can restore it at a later date if I need to? I know how to do this on HTC phones but it all seems to be a bit different on Samsung and I don't want to mess up anything.
How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.
Whosat said:
How did you reboot? If you select the reboot option in the CWM recovery,it should follow with a question on whether you want to continue rebooting with reverting to stock recovery or not.
Click to expand...
Click to collapse
Umm... yeah, I think it did ask but I just accidentally pressed no before reading what it said... So I guess I'll just have to flash the recovery again and then answer yes to that question.
Thanks
Yes that would be the correct way to do it.
Hope all goes well!
I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.
resplin said:
I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.
Click to expand...
Click to collapse
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.
Still no stock recovery
wantabe said:
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.
Click to expand...
Click to collapse
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?
resplin said:
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?
Click to expand...
Click to collapse
I'm sorry about the link, not that it does any good now but the link is corrected. Using fastboot to flash the images is correct, I too often use adb as a generic term for both. When you boot into the stock recovery you will see the android with the exclamation mark and that is normal. Finally got the new 2012 N7 I bought as a gift and was updating it. Been a while since I've booted into a stock recovery. So... Boot into stock recovery, when the Android with the red exclamation mark appears, hold down power first, followed quickly by volume up. You should now see the recovery menu. Whoop, Whoop! :laugh:
It works!
Thank you very much for your patient explanation. That helps a lot.
I hadn't realized that there was an additional step after the display of the warning android in order to enter stock recovery. All that time I spent trying to fix something that wasn't broken! <sigh>
I was unable to get the device to display the stock recovery menu, because it appears to require a very precise timing (I just keep rebooting it back to the system by accident). However, encryption did work fine. My confusion with the encryption was compounded by the fact that encryption of the Nexus 7 in 4.4 doesn't always work the first time (see this thread at android central: forums.androidcentral.com/google-nexus-7-tablet-2013/337078-experiencing-difficulty-encrypting-my-2013-n7-after-4-4-build-krt16s-upgrade.html). After trying 4 times in a row, the device encrypted. I was then able to put Team Win Recovery back on the device, and everything works perfectly.
Thank you again for your help. I don't see how to mark the thread as solved, but I am glad that everything appears to work now.
Ok. I have seen several people asking about rooting their T-Mobile Note 3. I am sure there have been posts on how to accomplish this feat. I am going to put out the steps that I took and mention a few other options and my thoughts on those. I hope to make this an all inclusive post for newbies. This method works whether you are on 4.3 or 4.4 BUT you will need to make sure the recovery and ROM you download is for the correct version of android you are using. To make this easier I am going to assume you are already on 4.4 Not everything will be clear but should be able to be easily understood. If there is something you don't understand ask and I am sure people will try to help. That or you can do a google search and probably find the answer a whole lot faster. If you did have a problem and found the solution please post it so others can use your information. I don't have the time at the moment to provide all the links but I will try to update this thread as much as I can.
I am NOT responsible for bricked devices, voided warranties or downloaded virus to your computer.
That being said rooting should be a relatively simple and easy process.
1. Download Odin 3.07 or 3.09 .zip file and install on your computer. (I have found no real difference in between the two when attempting root.) (No link provided just google it.)
2. Download the custom recovery of you choice. (I use and prefer twrp, but some people have had problems flashing ROMs and have had better luck with philz recovery) Below is the link for TWRP. If using 4.4 make sure to download the img.tar file for 2.7. There are other files but you want the one ending in img.tar! http://teamw.in/project/twrp2
3. Open Odin and connect your phone. You need to put your phone into download mode before connecting. Shut your phone off and then turn back on while holding volume down, power and home key. You will see a special screen pop up and a warning. Acknowledge the warning and the connect to the computer. If you don't get a blue bar on the left side of Odin after connecting your phone then you need to update your driver's (google search).
4. Place the .tar file that you downloaded into the PDA(3.07) or AP(3.09) section. Make sure the ONLY boxes on the left are Auto Reboot and F. Reset Time are checked (that should be the default settings)!!
5. Hit the start button. Be advised that Flashing a custom recovery WILL trip Knox.
6. You should the blue bar turn green and say "pass." You know have a custom recovery on your phone and you can disconnect your phone.
At this point you do not have root access, you just have a custom recovery. You now have a choice to make. Do you want your phone rooted or do you want to flash a custom ROM. If you want to flash a custom ROM jump to #8. If you just want root and plan on staying on stock go to #7.
7. Download the latest version of SuperSU file from http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash from your custom recovery. when you restart your phone make sure you can open the SuperSU app. If you cannot go to the play store and reinstall it from there. Congrats!!
8. If you want a custom ROM you need to download the .zip file of that ROM. I would recommend placing it on your EXTERNAL sd card.
9. Go to your custom recovery. There are some things you are going to need to back up prior to Flashing the ROM.
a. Backup your stock ROM, This could save you from some major problems. Back up-system, data and boot-to your EXTERNAL sd card.
b. Backup you EFS files (this can be done via twrp, other wise you will need to do it another way-Google search)
10. Wipe the phone. You want to wipe Data, Cache and Dalvik
11. Flash you custom ROM. Almost every custom ROM comes rooted. You just need to read the info on that ROM
12. Your phone should reboot and you are done!!
Below is some Q&A and helpful tips.
If I upgrade to 4.4 from 4.3 to get a diffent ROM can I switch back? NO
What is "Bricked"? It is a phone that will not boot and only stays on a black screen. Soft Brick is where your phone constantly reboots without opening your ROM.
What is Knox? Google it
Will tripping Knox void my warranty? Probably
How do I get into the recovery? Shut your phone off and then restart while holding the volume up, power and home key. You have to let go as soon as you see the blue letters "Recovery Booting"
There are not that many ROMS for T-mobile can I use an international ROM? Yes! I currently run an international ROM but on most of them you do loose your wifi calling feature. You also need to download a custom T-Mobile Kernel and the Wifi/BT fix.
Should I use CF Auto root or Klingo? I personally don't like the idea of Klingo. Some of the things I have seen they appear to be a little fishy and with them rooting your phone they initially have access to EVERYTHING. CF auto root does not place a custom recovery. You CANNOT flash a custom ROM without a custom recovery. I did it my way because I wanted a custom ROM and just not root.
What about the De La Vega Method? I have no idea and it seemed more work that it was worth. I did not care about tripping Knox
Tips:
Some ROMS will delete your internal memory when flashing as will wiping your phone. That is why I strongly suggest placing the backups and ROMS on your external sd card.
Some ROMS come with an Auroma set up. You will automatically be directed into it when you flash from recovery.
If you are flashing an international ROM make sure that you flash the ROM, T-mobile Kernel and Wifi Fix before choosing the reboot option. If you don't have the t-mobile kernel prior to reboot you will go into a bootloop.
I hope this helps and I will add more and clarify this post in the next few days. I just hope this can help some of you new guys out a little bit and if you found it useful especially if you obtained root please hit the thanks meter.
OK, I deleted all the information here about all the errors I made so that this won't confuse anyone. To summarize my error, I thought I had purchased Android 4.4.2 and flashed the wrong versions. After flashing the correct version, 4.3, everything worked.
The SD-card is not visible in stock recovery and the ADB method won't work without first having root, so that leaves the Odin method.
The Odin method flashes TWRP recovery successfully and when I exited it asked me if I wanted to root the device. I chose 'yes' and it worked for a while then booted into the Android OS. In Android it booted normally, then after I did something which I did not think about and don't recall, a dialog advised me that the GUI portion of the root process still needed to be applied. I allowed it to proceed and now I am rooted with TWRP. I verified the root through ADB by creating a file in the root directory.
Frank
I will try to break this down for you.
1. You need to reflash twrp via Odin to make sure it works correctly since doing auto root.
2. That screen you saw is exactly what you wanted to see. As stated in the OP when you see that screen let go of the buttons and wait, twrp will open shortly. I get the same screen so don't worry. Once you get into twrp and if you need a tutorial on twrp I would suggest looking it up on YouTube.
3. If you reflash the stock ROM via Odin it should fix everything. I am not sure about the partition problem. I will get back if I get some more info.
I would not worry about trying to reflash stock. I would just reflash twrp, boot into recovery and then proceed as listed in the OP.
Frank Westlake said:
**************************************************************************
I found my problem. I think the box, or something, was mislabeled because "About" tells me I have Android 4.3, not 4.4.2. So I flashed the 4.3 version of TWRP and booted right into it. After another reboot to make sure it's stable I'll try rooting again.
Frank
Click to expand...
Click to collapse
Great. Yes, it did not work because 2.7 is written for the new bootloader in 4.4. Are you planning on staying stock jb or planning on flashing a ROM?
sm-n900t: Powered by X-Note V13
FFTony said:
Are you planning on staying stock jb or planning on flashing a ROM?
Click to expand...
Click to collapse
Stock. With root I'm able to customize everything right on the device about as much as the ROM builders. But there are things I cannot do on the device so I'll be keeping an eye on the ROMs to see if anything is attractive.
After I finished this update I refreshed this page and saw that you had been commenting. The screen you saw should be there was also there when I flashed the correct TWRP, and it did move on to TWRP as you said. I'm adding the following paragraph separately so that it's easier for people to find if they need it:
After I had flashed the wrong version of TWRP (4.4 instead of 4.3) it boot-looped to the "SEANDROID NOT ENFORCING" display. To get out of that boot-loop I held the Download Mode keys (HOME-POWER-VOLDOWN) until it rebooted into the first download mode screen, the warning which says you can press VOL-DOWN to boot normally. At that point press VOL-DOWN and it will boot normally. If you press VOL-UP and continue into Download Mode then you will still be in the boot-loop when you reset the device and you will need to reboot again into the Download Mode warning screen and press VOL-DOWN to boot normally.
Thank you very much for your help with this.
Frank
FFTony said:
What about the De La Vega Method? I have no idea and it seemed more work that it was worth.
Click to expand...
Click to collapse
Samsung explains about Root De La Vega here: Samsungknox.com/en/blog/about-root-de-la-vega