Hey everyone!
Bone head move of the century, tried to flash a 4.2 rom on a 4.1 bootloader. After making some more mistakes, I've done a factory wipe and cannot restore from my external sd.
Tablet can still get into recovery and fastboot. Every time I try to flash a zip from my external sd, I get an error (red triangle).
Is there any way to go back to stock via fastboot? Just start over fresh? On my phone, I can unroot back to a stock rom from my computer.
Sorry if this has been answered/done before, but I've been searching for a while and I'm up sh*t creek right now without a paddle.
Thanks!
Yeah you should be able to flash back to stock 4.1.1 (10.4.2.20) via fastboot without issue.
Have a look here:
[HOW-TO] Upgrade or Downgrade to any stock JB Firmware
Related
On the other day, I manage to soft brick my phone. Since then, my journey started on improving my phone.
My question is this. The steps I took were all correct right?
Flash Firmware ( I535VRBLK3) using Odin,
Flashing the Bootchain (VRALEC.bootchain.tar) with Odin,
Flashing CWM6012TouchVZW.tar.md5 with Odin,
install ROOT and Unlock Bootloader(SuperSU + Unlocked Bootloader) from storage by using CWM recovery,
Flash the VRBLK3 Bootchain using ODIN to restore the Original Jelly bean VRBLK3 Bootchain,
Copy CleanROM to storage
Reboot to Recovery
Recommend wiping data / Factory Reset in Recovery!
Flash ROM and choose options
Now, here comes my question. I want to do these steps again because I messed around a bit too much again. The main question I have is Firmware is necessary in order for Roms to work??? To clarify, I535VRBLK3 firmware needs to be installed in order for CleanRom to be installed? Am I getting this correct?
krnspwn said:
On the other day, I manage to soft brick my phone. Since then, my journey started on improving my phone.
My question is this. The steps I took were all correct right?
Flash Firmware ( I535VRBLK3) using Odin,
Flashing the Bootchain (VRALEC.bootchain.tar) with Odin,
Flashing CWM6012TouchVZW.tar.md5 with Odin,
install ROOT and Unlock Bootloader(SuperSU + Unlocked Bootloader) from storage by using CWM recovery,
Flash the VRBLK3 Bootchain using ODIN to restore the Original Jelly bean VRBLK3 Bootchain,
Copy CleanROM to storage
Reboot to Recovery
Recommend wiping data / Factory Reset in Recovery!
Flash ROM and choose options
Now, here comes my question. I want to do these steps again because I messed around a bit too much again. The main question I have is Firmware is necessary in order for Roms to work??? To clarify, I535VRBLK3 firmware needs to be installed in order for CleanRom to be installed? Am I getting this correct?
Click to expand...
Click to collapse
No, you can be on a ICS build then flash a JB rom if you want. You dont need to reflash with odin either, you can just wipe in recovery and reflash the rom.
My phone's bootloader is unlocked and phone rooted using CWM.
When I try and do the OTA update the signature fails and the phone reboots or just shuts down after the os loads. The only way I can get it to stop is to wipe the cache
I'm guessing you want to take the OTA?
As I have said many times around here lately... You cannot take OTA's on custom recovery. You have to flash back to stock recovery, and then take the OTA.
While you're flashing back to stock recovery, you might as well just use the FXZ for JB and go straight to the JellyBean update.
Awesome thanks for the link to FXZ.
Just to Add notes, If you FXZ you will be brought back to stock and the phone will be wiped, if this is not what you want there is a stock recovery floating around and all you have to do is 'fastboot flash recovery <name of stock recovery>' this will allow you to upgrade without wiping, Though a good wipe has never hurt and can always help
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The stock Asus firmware includes bootloader, kernel, recovery and apps. You have flashed the stock recovery. Head over to the twrp thread or my ROM thread in my sig to see how to get twrp 2.5 onto your tab.
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
Yes, you did. Everytime you install stock file of any version, it will update your bootloader, rom, and kernel. Just use Motochopper to root your device and reinstall your custom recovery with goomanager.
No, it is stock recovery. Just reroot with motochopper and install custom recovery with goomanager. Have fun. :good:
Right, thanks! If I want to stay completely stock I just need to figure out why the newer update is failing. Could be the file name now I think about it.
Otherwise I'll re-root and re-TWRP...
Anatosuchus said:
Hi,
Sorry for the noob question here, I've managed to get myself very confused as to the state of my tf700t.
Some time ago I unlocked my bootloader and rooted my device (stock ROM with su I believe) and installed TWRP. All was well, but of course I couldn't get Android 4.2 OTA, so given I don't really use root much I decided to try to get back as close to stock as possible. I downloaded the 10.4.4.20 firmware from Asus and flashed it in using TWRP, so far so good.
Still no option to OTA, so I figured I would download and flash 10.6.1.14 instead and do the same thing, but I have problems! If I boot into recovery, instead of TWRP I get the android logo with the open door and spinning blue icosahedron. Poor old android then keels over backwards with an open chest and an alert sign. The tablet then reboots normally.
Question 1: Have I overwritten my recovery when I flashed the stock ROM? - I'm not sure if the ROMs should even overwrite the recovery partition; if this shouldn't happen, are there any clues as to what I have done?
The system actually recognises that I have 10.6.1.14 on my SD card and offers to install it, but that reboots and gives me the same dead android lying on his back. Question 2: Could this be related to the (broken?) recovery image, or could it just be a duff download of the firmware?
I suppose the bug question is how should i proceed? Should I look for a way to re-root the device, reinstall TWRP (maybe using goomanager) and flash again or am I just hopelessly misunderstanding where I am? Many thanks for any steers you chaps can offer.
Click to expand...
Click to collapse
The Android on his back is your stock recovery and it does not find a valid update file.
Weird is, that your system seems to see the 10.6.1.14 file (I assume you get an automatic notification and click "install" or "update" ) and then the recovery does not seem to install it...?
You could have a bad download, so try that first if you want to get the latest stock rom, or you can try to rename the downloaded file to EP201_768_SDUPDATE.zip, put it on your microSD card and reboot into recovery. The recovery should recognize the update file and start flashing it.
But since you are unlocked anyway - why don't you give CromiX a try? It runs so much better than the stock rom!
And for that, yes you would have to root again using the Motochopper tool and then install TWRP 2.5 with Goo Manager.
If you go that route make sure you flash the latest bootloader from the OP of the CROMiX thread first, boot back into your old rom once before you flash CROMiX.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Anatosuchus said:
Alright, I'm convinced - I'll try going totally custom! Presumably CromiX handles the external keyboard and touch pad properly?
Click to expand...
Click to collapse
It's based on the stock rom, cleaned up and tweaked and optimized. Everything works - and better than on stock! I recommend selecting the option to disable fsync during installation. It boosts performance considerably, and since the rom is totally stable, the "risk" is neglible.
You will love it!
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
OK, ChromiX installed! Looks interesting already, will tinker with it over the next couple of days.
So when the whole shield tablet recall program started, I installed blisspop on my old tablet. Now I want to return that tablet to stock. I downloaded the 2.2.2 recovery image and tried to flash it off of a micro SD card through twrp, but I keep getting a error that's says failed to sysMapFile and nothing happens. How can I revert back to stock? And I picked 2.2.2 because I was worried about the killswitch, can I actually use the 3.1.1 image and then re root and remove the Tegra update file? When I return to stock rom, will I be able to reinstall a custom recovery but keep the stock rom? Sorry for all the questions, I'm pretty new at this. Thanks for the help!
Flash what ever you want in fastboot.
IF you let it boot make sure it's been factory reset, if it connects to WiFi your F****D.
From recovery delete the "TegraOTA" folder/apk from /system/app (or /system/priv-app, I forget). As long as you nuke the updater before it connects to WiFi you're fine.
fro03 said:
So when the whole shield tablet recall program started, I installed blisspop on my old tablet. Now I want to return that tablet to stock. I downloaded the 2.2.2 recovery image and tried to flash it off of a micro SD card through twrp, but I keep getting a error that's says failed to sysMapFile and nothing happens. How can I revert back to stock?!
Click to expand...
Click to collapse
As the poster above me said, you must flash this with fastboot.
fro03 said:
And I picked 2.2.2 because I was worried about the killswitch, can I actually use the 3.1.1 image and then re root and remove the Tegra update file?
Click to expand...
Click to collapse
You can use whatever image you want as long as you remove TegraOTA.
fro03 said:
When I return to stock rom, will I be able to reinstall a custom recovery but keep the stock rom?
Click to expand...
Click to collapse
Yes, you can also just flash the custom recovery from fastboot when you are installing the custom ROM. Or you can just not flash a new recovery at all. If you leave your current recovery partition intact you can still flash your custom ROM using fastboot.
weedy2887, sockusminimus
would either of you be up to creating a potential debrick image for this device ?
thanks
m
Hey guys,
I was previously on xtresolite 2.4 lollipop rom and saw that he had a new rom out based on Marshmellow 6.01.
The instructions for the installation the new rom said to flash the new bootloader, modem and recovery before installing the new rom.
I flashed the bootloader with Odin using the BL button as instructed and how it's stuck on the Samsung Screen. I can still boot into download mode, but that's about it. It won't let me boot into recovery. Doing a bit of research it says to boot into download warning screen and cancel. Then quickly do the recovery buttons (volup, home, power), but it still won't go in.
So now I'm stuck! i'm trying to download the new stock Marshmellow firmware to see if I can install that, but aside from that I'm not sure what else I can do.
Any suggestions? Since I'm still able to use Odin, can I try to re-install the correct bootloader or is that too late? I'm not even sure which bootloader to install now. :crying::crying::crying:
Any help is much appreciated!
Thanks,
kc
as long as you can boot into the download mode, everything's alright. try flashing the latest stock rom for your model. then a new recovery, and then the new xtrestolite rom.
if something fails. do it again.... flash the latest stock rom, and so on.
Just make sure you have the correct model software for your phone and there won't be any issues. Did you backup your imei way back when you rooted on lollipop? If you did then everything will be fine if you didn't, Restore stock ROM and root, then backup your imei, hopefully you won't have any issues with your modem
Try pressing on power + vol down untill the phone shuts down then quickly press home+power+vol up before the phone starts . you will be in recovery try a factory reset then wait for the first boot. Voila !
hey all, just wanted to update. I still couldn't get into recovery, but was able to flash the stock rom and it's working as stock right now. Been using it for the past week or so and no major issues noted. I'm a bit scared to mess around again
Now that I'm on stock Marshmallow 6.0.1 rom, do I still need to try and flash the modem and boot loader for it?
Also, now that i'm on stock do I need to unroot again to install the twrp recovery? or can I just go into odin and flash it right away?
Thanks again for the help and suggestions!!!
tnimk said:
hey all, just wanted to update. I still couldn't get into recovery, but was able to flash the stock rom and it's working as stock right now. Been using it for the past week or so and no major issues noted. I'm a bit scared to mess around again
Now that I'm on stock Marshmallow 6.0.1 rom, do I still need to try and flash the modem and boot loader for it?
Also, now that i'm on stock do I need to unroot again to install the twrp recovery? or can I just go into odin and flash it right away?
Thanks again for the help and suggestions!!!
Click to expand...
Click to collapse
Stock rom overrides everything so your root is long gone & you now have the latest bootloader & modem already - don't stress & no need to do anything else! If you want custom recovery simply flash with latest TWRP using Odin in download mode (in tar format using AP button). Don't root with TWRP if asked to - instead download latest recovery flash-able SuperSU (ZIP) onto your device & then flash it using TWRP. This will be the safest option for you (with root if you want).
AFAIK one always uses the "AP" button if you wanna flash <anything> with Odin - not the BL button (I've never used this). The rest are for pro's only (of which I'm not one). I'm simply a regular rom flasher & read/study/compare several guides before attempting anything I've never done before with my device. If the overall feeling is not a good one, rule of thumb is I don't proceed until I feel confident enough about what I'm attempting to do.
Good luck.
On my sm-G920I
I flashed the xtresolite ROM without first flashing the bootloader and modem and it worked fine for me, if you back up everything with an otg cable onto a USB then flash the ROM everything should work fine but you will have to wait around 5 minutes for it to boot. If your still waiting after 10-20 minutes then you did something wrong and you can just wipe your entire phone then recover everything from your backup on your USB ????????