Related
I rooted & installed CWM via the one-click method. It installs Rogue XM Recovery 1.3.0.
http://forum.xda-developers.com/showthread.php?t=1689193
I backed everything up in CWM so that when & if I flashed back everything would be backed up. So I flashed Jelly Bean
[ROM][JB][4.1.1] AOSP build #4 http://forum.xda-developers.com/showthread.php?t=1779133
I played around with & didn't see what the big deal was with Jelly Bean was. Also was irritated that there was no file explore built into the ROM. I really like the one on Asus ICS ROM. Anyway I go back into recovery to install the stock Asus ICS ROM (US_epaduser9_2_1_27UpdateLauncher.zip). It tries but aborts
Finding update package...
Opening update package ...
Installing update...
Installation aborted.
What am i missing or doing wrong?
Well for starters the only reason the stock ICS roms have a file explorer is because its an Asus proprietary app, every custom ICS, or JB rom will require you to download one. Secondly are you trying to re-flash the stock rom or restore your back up? Id recommend you try using TWRP
JoinTheRealms said:
Well for starters the only reason the stock ICS roms have a file explorer is because its an Asus proprietary app, every custom ICS, or JB rom will require you to download one. Secondly are you trying to re-flash the stock rom or restore your back up? Id recommend you try using TWRP
Click to expand...
Click to collapse
Just trying to re-flash the stock ROM.
jadesse said:
Just trying to re-flash the stock ROM.
Click to expand...
Click to collapse
I think i seen this before you are trying to flash an update to a rom not that actual rom......check the file size. I haven't had any issue converting Jb back to ICS. you have to flash a fresh install of the version you backed up then you can flash the back up you made. The mounting from ICS to JB is different and you cannot go backwards without flahsing a clean rom first.
itj1228 said:
I think i seen this before you are trying to flash an update to a rom not that actual rom......check the file size. I haven't had any issue converting Jb back to ICS. you have to flash a fresh install of the version you backed up then you can flash the back up you made. The mounting from ICS to JB is different and you cannot go backwards without flahsing a clean rom first.
Click to expand...
Click to collapse
I downloaded the newest firmware straight from the Asus website. That is what I am trying to flash but it fails to. If I should be doing something else then please tell me.
Did you unzip the download and flash the zip that is inside? For some reason Asus packages a zip within a zip. You need the one on the inside to flash.
Woodrube said:
Did you unzip the download and flash the zip that is inside? For some reason Asus packages a zip within a zip. You need the one on the inside to flash.
Click to expand...
Click to collapse
I feel like such a moron because that was the issue. I found the .24 firmware that I had extracted to a folder with the need zip file in side. I was able to flash t e.24 with out an issue. I knew my issue was something stupid but I could put my finger on it right away.
You might want to go back to the ASUS site and download the newer firmware(.27) and do the same thing(install the zip inside the zip) That's the newest Official ASUS Firmware.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101&p=20&s=16
sfot said:
You might want to go back to the ASUS site and download the newer firmware(.27) and do the same thing(install the zip inside the zip) That's the newest Official ASUS Firmware.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101&p=20&s=16
Click to expand...
Click to collapse
I already had it.
ok so I was an original GS III owner (I preordered, used the original root66, waited for the unlocked bootloader, etc.)
I just rx'ed a 2nd replacement because the power button fell off my first replacement (my 1st gsIII had a faulty modem).
This one came preloaded with the 2nd OTA (VRALHE)
I was wondering the correct method to go about setting it up...
1.) odin the original root66 VRALF and continue in the same way I did with my original one (dd a TWRP and the insecure bootloader)?
2.) I could follow the directions in section 1 here: http://forum.xda-developers.com/showthread.php?t=1762709
and odin a pre-rooted VRBLJ1. It then says I can just go ahead and add a custom recovery (it mentions the EZ app but I'd rather just dd. then do the insecure aboot the same way)
3.) I could follow the directions here: http://forum.xda-developers.com/showthread.php?t=1974114
it mentions ODINing the VRBLJ1 leak and then ODINing a custom recovery but the recoveries INCLUDE "VRBLJ1 Bootchain." Why?
according to Invisiblek (http://rootzwiki.com/topic/29256-ro...-unlock-sch-i535-d2vzwverizon-galaxy-s-iii/):
What the locked bootloader prevents us from doing is flashing, via odin, a custom recovery or kernel. What we can do however, is revert to an older (semi-insecure) bootchain which we have acquired, flash our custom recovery, and then continue on from our freshly flashed custom recovery by flashing an unlocked bootloader and anything else we want.
Kernels from the newer OTA's prevent us from doing this process. We'll need to flash a kernel too...
Click to expand...
Click to collapse
he mentions flashing the VRALEC and then later (after flashing the VRALF2 kernel and a custom recovery) the VRALF2 bootchain. His explanation makes sense, but the other threads say to use the VRBLJ1 bootchain. why all the conflicting info?
Also, as I wrote this I used the rootDebugFS thing on my freshly rx'ed VRALHE. i then dd'ed a recovery and the insecure aboot. Everything is working fine. So what's all the fuss about? and will I encounter problems if I try to odin anything, like invisiblek said?
Thanks
preusstang said:
ok so I was an original GS III owner (I preordered, used the original root66, waited for the unlocked bootloader, etc.)
I just rx'ed a 2nd replacement because the power button fell off my first replacement (my 1st gsIII had a faulty modem).
This one came preloaded with the 2nd OTA (VRALHE)
I was wondering the correct method to go about setting it up...
1.) odin the original root66 VRALF and continue in the same way I did with my original one (dd a TWRP and the insecure bootloader)?
2.) I could follow the directions in section 1 here: http://forum.xda-developers.com/showthread.php?t=1762709
and odin a pre-rooted VRBLJ1. It then says I can just go ahead and add a custom recovery (it mentions the EZ app but I'd rather just dd. then do the insecure aboot the same way)
3.) I could follow the directions here: http://forum.xda-developers.com/showthread.php?t=1974114
it mentions ODINing the VRBLJ1 leak and then ODINing a custom recovery but the recoveries INCLUDE "VRBLJ1 Bootchain." Why?
according to Invisiblek (http://rootzwiki.com/topic/29256-ro...-unlock-sch-i535-d2vzwverizon-galaxy-s-iii/):
he mentions flashing the VRALEC and then later (after flashing the VRALF2 kernel and a custom recovery) the VRALF2 bootchain. His explanation makes sense, but the other threads say to use the VRBLJ1 bootchain. why all the conflicting info?
Also, as I wrote this I used the rootDebugFS thing on my freshly rx'ed VRALHE. i then dd'ed a recovery and the insecure aboot. Everything is working fine. So what's all the fuss about? and will I encounter problems if I try to odin anything, like invisiblek said?
Thanks
Click to expand...
Click to collapse
I'm assuming since VRBLJ1 is the newest JB leak then it uses the newer boot chain. The only reason you would need that boot chain to unlock the bootloader is if you used Odin to flash the newest VZW JB leak onto your phone. Then you would need it to unlock the VRBLJ1 JB leak. If you are are any of the ICS stock ROMs and want to unlock you can use the old way of doing it. The post you are reading from invisiblek is old, it was when we were on the VRALFW stock ROM.
Now I have no clue why you would want to use Odin to flash the newest JB leak when you can do it by downloading the version of the ROM made to be flashed with TWRP or CWM. I would love to have a dev or someone knowledgeable about these things to chime in and tell us if there is any benefit to using Odin to update to the newest JB leak or if there is no difference between having the JB leak or one of the OTA's on your phone before you flash a ROM.
Sent from one of the many Anthropomorphic Personalities on the Disc
shangrila500 said:
I'm assuming since VRBLJ1 is the newest JB leak then it uses the newer boot chain. The only reason you would need that boot chain to unlock the bootloader is if you used Odin to flash the newest VZW JB leak onto your phone. Then you would need it to unlock the VRBLJ1 JB leak. If you are are any of the ICS stock ROMs and want to unlock you can use the old way of doing it. The post you are reading from invisiblek is old, it was when we were on the VRALFW stock ROM.
Now I have no clue why you would want to use Odin to flash the newest JB leak when you can do it by downloading the version of the ROM made to be flashed with TWRP or CWM. I would love to have a dev or someone knowledgeable about these things to chime in and tell us if there is any benefit to using Odin to update to the newest JB leak or if there is no difference between having the JB leak or one of the OTA's on your phone before you flash a ROM.
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
Its just another way of basically doing the same thing. If your already rooted and have cwm recovery, then flashing a J1 rom via cwm or twrp recovery is by far the easiest method. Now if your stock and unrooted, it would be easier to odin root66 J1 , then unlock and get cwm recovery via the ez unlock/recovery apps. This is why I have 2 different methods in my guide...I also chose to not flash bootchains unless its a last resort because they can perma brick a device if something goes wrong. Also I like to use methods that dont trip the flash counter, makes for one less thing to do if the device ever needs to be returned.
droidstyle said:
Its just another way of basically doing the same thing. If your already rooted and have cwm recovery, then flashing a J1 rom via cwm or twrp recovery is by far the easiest method. Now if your stock and unrooted, it would be easier to odin root66 J1 , then unlock and get cwm recovery via the ez unlock/recovery apps. This is why I have 2 different methods in my guide...I also chose to not flash bootchains unless its a last resort because they can perma brick a device if something goes wrong. Also I like to use methods that dont trip the flash counter, makes for one less thing to do if the device ever needs to be returned.
Click to expand...
Click to collapse
Gotcha, that's been bothering me for a few days. I remember when I was flashing on my RAZR that the stock OTA was the base for everything and if you didn't have the latest OTA some of the ROMs wouldn't run on your phone until you updated and some of the older ROMs wouldn't work until they had been updated to work on the newest OTA or leak. The ROMs were just overlays and usually only added a little bit of added performance or functionality.
Would updating to the latest OTA via Odin add any benefits like it did on the RAZR ? I know the RAZR wasn't unlocked and we weren't flashing ROMs like we do on the GS3 but.....
Sent from one of the many Anthropomorphic Personalities on the Disc
no not on samsung devices...you can go from f2 to the latest with no issues.
droidstyle said:
no not on samsung devices...you can go from f2 to the latest with no issues.
Click to expand...
Click to collapse
No I get that, I was meaning are there any positive side effects from using the newest JB leak as your base ROM before flashing a new one. Like flashing the new JB leak via Odin, then unlocking and flashing a new ROM on top of it. Will there be any benefits like there were on the RAZR or when we flash in custom recoveries does it completely do away with the stock ROM that was on the system partition and replace it with whatever we flash? I know on the RAZR you would use the ROM you were on as a base you flash whatever else you wanted and there were benefits to having a certain OTA as your base before you flashed. I don't think I'm doing a very good job of phrasing my question, I apologize for that. Its just a hard question to put into words.
Sent from one of the many Anthropomorphic Personalities on the Disc
shangrila500 said:
No I get that, I was meaning are there any positive side effects from using the newest JB leak as your base ROM before flashing a new one. Like flashing the new JB leak via Odin, then unlocking and flashing a new ROM on top of it. Will there be any benefits like there were on the RAZR or when we flash in custom recoveries does it completely do away with the stock ROM that was on the system partition and replace it with whatever we flash? I know on the RAZR you would use the ROM you were on as a base you flash whatever else you wanted and there were benefits to having a certain OTA as your base before you flashed. I don't think I'm doing a very good job of phrasing my question, I apologize for that. Its just a hard question to put into words.
Sent from one of the many Anthropomorphic Personalities on the Disc
Click to expand...
Click to collapse
no not on samsung devices...the reason you needed to do that on the moto device is because of the locked bootloader. meaning you couldnt replace the kernel, so you had to ota to the latest, then root , recovery, and flash rom. since our device is fully unlocked, we dont have to worry about this. most if not all roms for d2vzw are packaged with a kernel. so it does not matter what current base your on, flashing a rom will overwrite it.
droidstyle said:
no not on samsung devices...the reason you needed to do that on the moto device is because of the locked bootloader. meaning you couldnt replace the kernel, so you had to ota to the latest, then root , recovery, and flash rom. since our device is fully unlocked, we dont have to worry about this. most if not all roms for d2vzw are packaged with a kernel. so it does not matter what current base your on, flashing a rom will overwrite it.
Click to expand...
Click to collapse
That's what I thought. I was just wanting a little clarification on that. Thanks man!!!
Sent from one of the many Anthropomorphic Personalities of the Disc
Currently my TF300T is unlocked, rooted, ICS TWRP 2.3.1, nvflash blob files created (copies made and moved elsewhere) with AndroidRoot.mobi custom bootloader. I'm running stock ICS v9.4.3.17 and never ran any OTA's (one is downloaded/pending for install, but doesn't seem to do anything - likely because I'm unlocked?).
It's been recommended to just flash the JB bootloader & use a custom JB ROM rather than updating fully to JB (was said there are or had been, issues flashing the full JB from ASUS' website). With the nvflash blobs, I should be able to go back to ICS so I'd rather do a full update if possible. An earlier post [Q] Upgrade to JB bootloader from Unlocked ICS BL? asked the same but I need clarification on the answer (plus making sure - they were running ICS stock bootloader, not the custom from AndroidRoot like me):
mikaole said:
just fastboot TWRP for ICS and then flash the 1st JB StockRom(dl from Asus and unzip once) in TWRP.
Then fastboot TWRP for JB, then flash the latest JB StockRom(dl from Asus and unzip once) .
Then fastboot TWRP for JB and then the Rom you like
Click to expand...
Click to collapse
If reading right, in fastboot mode first flash ICS TWRP (I ignore as I already have it), then from TWRP install the 1st JB Stock ROM zip, reboot into fastboot mode, flash TWRP for JB (or should I use nvflash?), and lastly, reboot into TWRP and install the latest ASUS stock ROM zip (v10.4.2.18).
Figuring my steps are correct, what version from ASUS is considered the 1st ROM? Currently only v10.4.2.17 and v10.4.2.18 are available. Also wondering why the need to flash an earlier version of JB and then the most current? And lastly, have others in same situation done this successfully or encountered any issues I should be aware of?
I did this a short time ago to go from BB6 on ICS bootloaded to BB6 on JB. All I did was dropped back to stock ICS, upgraded TWRP, then drop the unzipped zip of the latest ASUS release. This got me stock JB on JB bootloaded. I then flashed the next BB6 version and went on my way.
The only painful part was that the post called for moving the blob to a specific folder and creating a command file. None of that worked for me. But leaving the unzipped zip file in the root of the SD card and rebooting worked flawlessly.
Good luck.
Sent from my Transformer Pad TF300T using Tapatalk HD
bsaman said:
I did this a short time ago to go from BB6 on ICS bootloaded to BB6 on JB. All I did was dropped back to stock ICS, upgraded TWRP, then drop the unzipped zip of the latest ASUS release. This got me stock JB on JB bootloaded. I then flashed the next BB6 version and went on my way.
The only painful part was that the post called for moving the blob to a specific folder and creating a command file. None of that worked for me. But leaving the unzipped zip file in the root of the SD card and rebooting worked flawlessly.
Good luck.
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Thanks! So you were going from another set of instructions but ended up just flashed twrp-jb and installed the unzipped zip of Asus JB release via TWRP (I left out the revert to ICS part since I'm already there)? And do you have nvflash installed? No issue running the JB version of TWRP prior to upgrading to JB (had thought bootloader or ... would have an issue with it)? Would seem like order should be reversed, I may not be understanding it all fully!
Had come across various instructions but none seemed to fit being unlocked/rooted/nvflash/... and wasn't sure if would require different steps. Again thanks.
wha2do said:
Would seem like order should be reversed, I may not be understanding it all fully!
Had come across various instructions but none seemed to fit being unlocked/rooted/nvflash/... and wasn't sure if would require different steps. Again thanks.
Click to expand...
Click to collapse
I think you're right... I was on BB6 w/ICS bootloader (NVflashed, though I don't think it matters) and had to roll back to ASUS ICS ROM first, then rooted, then upgraded to ASUS JB ROM, and then it goes blurry. Not sure if I upgraded TWRP or rooted stock JB at this point.
In any case, I followed the "update to JB" thread to a tee, and all went well except for the step regarding the actual JB update.
Sent from my Transformer Pad TF300T using Tapatalk HD
wha2do said:
Currently my TF300T is unlocked, rooted, ICS TWRP 2.3.1, nvflash blob files created (copies made and moved elsewhere) with AndroidRoot.mobi custom bootloader. I'm running stock ICS v9.4.3.17 and never ran any OTA's (one is downloaded/pending for install, but doesn't seem to do anything - likely because I'm unlocked?).
It's been recommended to just flash the JB bootloader & use a custom JB ROM rather than updating fully to JB (was said there are or had been, issues flashing the full JB from ASUS' website). With the nvflash blobs, I should be able to go back to ICS so I'd rather do a full update if possible. An earlier post [Q] Upgrade to JB bootloader from Unlocked ICS BL? asked the same but I need clarification on the answer (plus making sure - they were running ICS stock bootloader, not the custom from AndroidRoot like me):
If reading right, in fastboot mode first flash ICS TWRP (I ignore as I already have it), then from TWRP install the 1st JB Stock ROM zip, reboot into fastboot mode, flash TWRP for JB (or should I use nvflash?), and lastly, reboot into TWRP and install the latest ASUS stock ROM zip (v10.4.2.18).
Figuring my steps are correct, what version from ASUS is considered the 1st ROM? Currently only v10.4.2.17 and v10.4.2.18 are available. Also wondering why the need to flash an earlier version of JB and then the most current? And lastly, have others in same situation done this successfully or encountered any issues I should be aware of?
Click to expand...
Click to collapse
First I want to address your possible OTA. Processing requires stock recovery on your tablet. Having Twrp or CWM means the update will not process.
When you flash a complete stock rom from fastboot, Twrp, or CWM you are flashing stock recovery as it is included in the blob.
Most versions of Asus firmware can be found here! Don't forget to look at the second post as It includes the ICS stuff and older JB.
The first version of JB was to my knowledge JB 10.4.2.9.
Sorry, I forgot why flash first version of JB.
It has been said that is when your internal sdcard was repartitioned for JB.
tobdaryl said:
First I want to address your possible OTA. Processing requires stock recovery on your tablet. Having Twrp or CWM means the update will not process.
When you flash a complete stock rom from fastboot, Twrp, or CWM you are flashing stock recovery as it is included in the blob.
Most versions of Asus firmware can be found here! Don't forget to look at the second post as It includes the ICS stuff and older JB.
The first version of JB was to my knowledge JB 10.4.2.9.
Sorry, I forgot why flash first version of JB.
It has been said that is when your internal sdcard was repartitioned for JB.
Click to expand...
Click to collapse
Thanks for the info. To add to your one comment (for others that may come across this looking for add'l info), flashing a full stock rom will overwrite any custom recovery previously in place. TWRP (using the appropriate version for your firmware) or CWM will need to be reflashed again...
Checking, it does appear v10.4.2.9 is the first version of JB on the TF300T.
I've come across at least one or more posts/guides that mention ICS v9.4.3.30 should be installed before updating to JB - one being: [GUIDE]Upgrade your TF300t to Jellybean, recovery, root & remove bloatware[Noobproof]. I'm wondering if it's because that method updates to JB using the dlpkgfile (not sure what format it is)?
My take is doing the additional flash to v9.4.3.30 first can't hurt anything, but quite possibly unnecessary here? Any other thoughts or words of warnings from anyone? Thanks!
Hi,
I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
Or, can I flash OTA update as update.zip in TWRP recovery?
sorry, for my bad english.
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
JohnKoeMan said:
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
Click to expand...
Click to collapse
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
Haha no problems friend!
I've found a link to a custom ROM using JB 4.1.1, you can look into that?
http://forum.xda-developers.com/showthread.php?t=1871866
Also you can instead remove TWRP (if you know how) and instead install CWM (clockworkmod).
I found CWM to work better than TWRP.
I myself am using CyanogenMod 10.1, very nice and clean, works perfectly ad has Android 4.2.1
That might also be an option if you want a clean ROM. ^^
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
orenfl said:
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
Click to expand...
Click to collapse
Since I'm facing the same problem, and there is no RUU for now, how and where to get a JB OTA nandroid... Haven't seen any around.
Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
tominozh said:
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
bo6o said:
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
Click to expand...
Click to collapse
Yes, you should be. Download zenrom, reboot recovery, wipe everything a few times, flash zenrom, set it up, then recovery, flash STOCK RECOVERY ( very important), prompt for update, download, install, set up, ( you may get a few errors here and there so just do factory reset in setting-->factory reset). Then flash twrp, flash superuser, backup.
Sent from my HTC One S using xda app-developers app
Hi, I unlocked my TF300T sotck ICS 4.0.3 with the Asus app, I flashed CWM and the root_signed thingy without a problem. I then did a data wipe, cache and dalvik wipe and flashed CM10 stable build for TF300T and the Gapps zip. I reboot and it's stuck on ASUS screen. I'm currently doing a restore of the "nandroid". Will this restore my tablet to ICS? What did I do wrong? How do I get either Cm10 to work or return to the ICS? Also, if I need to flash something else, how do I do it? Does the CWM recognize msd cards? Because all I have on the internal memory is the CM10 which currently did not work for me. I'm a little desperate right now. Thanks.
EDIT: DAMN IT, I just got an error restoring data. What the hell do I do? Please!
i tried restoring again and reflashing cm10 and the gapps and still nothing changes. I did wipe again the caches and still nothing. Also I can't download other roms to the tablet because my computer doesn't recognize the tablet because it hasn't booted and the cwm won't recognize micro sd cards. So I think flashing something else isn't an option. Did I break my tablet completely? I'm almost in tears
I tried several things due to some searches on different forums but nohitng works. I tried wiping caches and reflashing Cm10, didn't work. I tried pluggin my tablet to my computer and sending the asus stock rom via ADB and flashing that, but CWM gives me an "installacion aborted" error. I just don't know what to do nor I understand what went wrong. I did everything according to multiple tutorials. Unlocking, flashing CWM and rooting went just fine. But installing CM10 ended up pretty much destroying my tablet. I wanna kill myself.
I think you have a brick??!! :'( cm10 is jellybean and you where on ics and you probably didn't flash the jellybean bootloader did you?
Sent from my ASUS Transformer Pad TF300T
Not a single tutorial said that I had to do that. Every tutorial says "unlock bootloader, flash cwm, flash root_signed, flash cmrom". I did just that. Are you telling me that my tablet is lost forever?
in most cm threads (except cm9) their is stated that you atleast need android 4.1.1 with it's bootloader or 4.2 with it's bootloader, what i suggest you try is to flash a bootloader and upgrade staight to 4.1.1 you can download the firmware from asus the links are on this guide: http://forum.xda-developers.com/showthread.php?p=39272826 FOLLOW THIS GUIDE CORRECTLLY OR YOU MIGHT PERMANENTLY BRICK YOUR TABLET!!!!
EDIT: if you get an error during flash it's probably the drivers or a fastboot flash brick wich is only fixable by replacing the motherboard!!
Sent from my ASUS Transformer Pad TF300T
If what you say is true, then you can't flash CM10 on a stock ICS tablet, and that goes against every freaking tutorial I've read before messing with my tablet.
What exactly is your bootloader version?
Sent from my ASUS Transformer Pad TF300T
I'm not sure what my answer is. The "bootloader" was unlocked by the Asus app from their website. I did that by downloading (I believe it was V7) the apk from their website and installing that and unlocking the tablet. From there on, I just followed did fastboot flashing CWM and rooting. I never read a tutorial that said "you should flash JB bootloader before installing cm10". In fact I thought that just by unlocking the tablet, rooting and flashing the custom recovery one could just install a custom rom regardless of wether it's JB or not. It's funny because I didn't want to upgrade to stock JB because it seemed buggy from a lot of reviewers, and CM10 was the classic option to have JB and a lot of great features and speed. So I google time and time again how to flash CM10 on a ICS stock ASUS. I just followed the tutorials for that.
is my tablet unrecoverably bricked? I also tried fastbooting and "flash system blob" with the blob for the ICS 4.0.3 firmware, after a while of "sending" the file in the command prompt, I got a blue progress bar in the fastboot screen on the tablet and then "FAILED". So I guess that doesn't work either.
Nothing will work?
Try entering fastboot reboot: does your tablet reboot or does it hang?
cm10 is android 4.1 it seems logical that it only runs on a 4.1 bootloader and not on an ics one! most posts must have said that you atleast need jelllybean 4.1.1
I was confused in the beginning aswell because my phone accepts any rom no matter what bootloader version!
Sent from my ASUS Transformer Pad TF300T
If it makes so much sense that CM10 with JB 4.1 only boots with the JB bootloader, then how the hell one can go from ICS to CM10?! Google tutorial flash cm10 on asus tf300t stock ics and you'll find a thousand tutorials not one of which says you need JB bootloader. I mean, I assume one could upgrade to the official JB rom and then unlock bootloader, etc, but I'm telling you, every tutorial that said "stock ics to cm10" did no mention the bootloader version issue. I'm not trying toblame anyone other than myself for "bricking" my tablet, but I read so many tutorials to ensure I wouldn't mess it up that I'm very upset about this.
I can use fastboot and adb commands. But I haven't been able to flash the ICS stock rom so far. First of all, it's not on the Asus website anymore, and the one I got from the web gave me this error on CWM "instaling update.. installation aborted". I also tried flashing the .blob via fastboot and it also failed. It seems nothing works. Any thoughts, anyone?
philos64 posted links to some old ICS ASUS firmwares in this post:
http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Maybe worth a try ? Never been on ICS myself - just thought I'd mention this source...sorry for wasting your time if this is what you already tried.
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
samus88 said:
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
Click to expand...
Click to collapse
We would like to know what bootloader you now have. You use the bootloader menu to get to cwm. Tell us how many ICONS you have and what they are. This way we will have more info to consider options if any.
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
samus88 said:
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
Click to expand...
Click to collapse
I reread the thread and I believe I would make a blob with just stock recovery (4.03) to match your bootloader. I know fastboot is failing on a complete blob but may process something as small as recovery. The blob could also be pushed to your tablet with adb and flash with that.
I made these choices as a place to begin since we need to match your bootloader.
Once stock recovery was in place we could use adb to push a once unzipped stock firmware (4.03) and get stock recovery to install it for us.
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
samus88 said:
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
Click to expand...
Click to collapse
With stock recovery in place go into bootloader and pretend you are going into cwm that activates stock recovery now. If android lays down we'll rename the zip to EP201_768_SDUPDATE.zip and try again.
I'll download 4.03 and make the recovery blob tomorrow so we'll be ready.
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
samus88 said:
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
Click to expand...
Click to collapse
No, there is the full blob in the factory firmware and that is what I'll use. It only takes a couple of minutes to extract the recovery image file which might flash and then re-blob just the recovery partition.
Downloading takes longer than everything else.
Update:
This zip contains stock 4.03 recovery as a blob and as an image file.
Unzip and try flashing the blob - if it fails try flashing twice more or until success. If it still fails try flashing the image file - three times if it fails.
Note:
These are to be flashed with fastboot or adb, not cwm.
Great, thanks man. Unfortunately, I won't have my tablet until at least wednesday because of the holiday on my country (independence day and such). But I'll give it a try and get back to you.