Database Info

[q] can you flash rom w/fastboot

I somehow have locked myself out but still have access to CWM and FASTBOOT. So, how do I use FASTBOOT to install a rom? Is it even possible? I just flashed CWM again, but still cannot get my CWM Backup copy to work.

up.
My friend has same issue, change build.prop.. no backup, no adb, only fastboot with cwm. Any ideas? Ext SD don't work in CWM\TWRP.
upd: Answer myself - Plug into usb in recovery, update driver in device manager to ADB Device, use adb

See here http://forum.xda-developers.com/showthread.php?t=1680570

What happens if clockworkmod recovery cannot read zip files???

fastboot flash zip rom.zip

prototype7 said:
fastboot flash zip rom.zip
Click to expand...
Click to collapse
Do I need a system.img file???

ri123 said:
Do I need a system.img file???
Click to expand...
Click to collapse
No, just the regular zip, you could also try reflashing the recovery (fastboot flash recovery recovery.img).

prototype7 said:
No, just the regular zip, you could also try reflashing the recovery (fastboot flash recovery recovery.img).
Click to expand...
Click to collapse
What about fastboot update command???

No
Hit the thanks button if i helped

Is this procedure compatible with the meta inf folder???

noooo!! i try "fastboot flash zip rom.zip" and it says FAILED remote partition does not exist!! what can i do now??

nooo!!! it says ( failed remote partition does not exist)

Xperia S with the same problem mine says
(remote: Partition not found)

The command you can used to flash a zipped ROM like the stock one from Asus is...
Fastboot -i 0x0b05 flash system yourrom.zip
I usually flash these using twrp recovery but I think that will do it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Maybe I just can't follow instructions or anythng, but I attempted my first ROM flash and it didn't work.
I tried the Blackbean 5 ROM, with TWRP. I found a set of instructions saying how to flash with TWRP, so I followed them, and I think I've soft-bricked my TF300T. Just stays on the Asus logo, and in top left it says "The Device is UnLocked."
I DID make a recovery in TWRP, and I attempted to flash that back with no luck.
Maybe I'm doing it wrong, so can someone help me out here?
funnel71 said:
The command you can used to flash a zipped ROM like the stock one from Asus is...
Fastboot -i 0x0b05 flash system yourrom.zip
I usually flash these using twrp recovery but I think that will do it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I tried this with the stock ROM, from their website, and it didn't help...
So I'm not sure what my problem is now.
Then again, when it comes to ROMs, I'm a noob.
EDIT: I still have TWRP, my recovery, and the Blackbean ROM .zip on the device.

TsarProdigy said:
Maybe I just can't follow instructions or anythng, but I attempted my first ROM flash and it didn't work.
I tried the Blackbean 5 ROM, with TWRP. I found a set of instructions saying how to flash with TWRP, so I followed them, and I think I've soft-bricked my TF300T. Just stays on the Asus logo, and in top left it says "The Device is UnLocked."
I DID make a recovery in TWRP, and I attempted to flash that back with no luck.
Maybe I'm doing it wrong, so can someone help me out here?
I tried this with the stock ROM, from their website, and it didn't help...
So I'm not sure what my problem is now.
Then again, when it comes to ROMs, I'm a noob.
EDIT: I still have TWRP, my recovery, and the Blackbean ROM .zip on the device.
Click to expand...
Click to collapse
Background first when stock were you JB or ICS? Blackbean OP does not specify. At the moment I'm to lazy to read through thread or flash to find the answer. If you were on stock JB you can only use JB roms, if you were on ICS you can only use JB after stock upgrade to JB.
Forget Blackbean for now and let's concentrate on getting you fully functional on stock again. If you were on ICS then download stock 9.4.3.30 and unzip once that leaves you with a zip. Place that zip on your ( /sdcard ) or external sdcard ( /Removable/MicroSD ) and flash with Twrp. If you were JB then the instructions are the same except use stock 10.4.2.13.
If you do this you will loose your recovery ( Twrp ) but you should have a functional unit.
Non stock rom install.
Be sure you use proper rom for your bootloader ( ICS or JB ). Choose one that gives you instructions as to what to wipe, etc. You can adlib after you get your feet wet. If the op gives instructions use them if not then you may or may not have a happy ending with generic instructions.:good:
If you need anything explained let me know and I'll step by step for what you don't understand.
The reply you tried to follow said "I think", you should have investigated before following. Don't get me wrong, I'm not saying that was incorrect but the poster was in doubt and you should be also.
When we say "I think" we kind of assume you are going to do some reading and be comfortable with everything before you continue.
I took a little time to look over Blackbean and as I suspected it is for the ICS bootloader not JB.

same problem
I am having the exact same problem. I did manage to install the clean rom 2.5 custom rom successfully originally, and i made a backup through CWM, but I cant install any other rom on there for some reason. Yesterday I managed to go back to stock Asus jellybean rom successfully, and then had to root it and install CWM again successfully. I have again tried again today to install that EuroSkank rom, but alas, I get stuck at the ASUS boot logo permanently and nothing happens?
What might I be doing wrong??
I am on Jellybean. Thankfully the CWM is working fine and I could also restore my cleanrom2.5 backup.
tobdaryl said:
Background first when stock were you JB or ICS? Blackbean OP does not specify. At the moment I'm to lazy to read through thread or flash to find the answer. If you were on stock JB you can only use JB roms, if you were on ICS you can only use JB after stock upgrade to JB.
Forget Blackbean for now and let's concentrate on getting you fully functional on stock again. If you were on ICS then download stock 9.4.3.30 and unzip once that leaves you with a zip. Place that zip on your ( /sdcard ) or external sdcard ( /Removable/MicroSD ) and flash with Twrp. If you were JB then the instructions are the same except use stock 10.4.2.13.
If you do this you will loose your recovery ( Twrp ) but you should have a functional unit.
Non stock rom install.
Be sure you use proper rom for your bootloader ( ICS or JB ). Choose one that gives you instructions as to what to wipe, etc. You can adlib after you get your feet wet. If the op gives instructions use them if not then you may or may not have a happy ending with generic instructions.:good:
If you need anything explained let me know and I'll step by step for what you don't understand.
The reply you tried to follow said "I think", you should have investigated before following. Don't get me wrong, I'm not saying that was incorrect but the poster was in doubt and you should be also.
When we say "I think" we kind of assume you are going to do some reading and be comfortable with everything before you continue.
I took a little time to look over Blackbean and as I suspected it is for the ICS bootloader not JB.
Click to expand...
Click to collapse

maggoty said:
I am having the exact same problem. I did manage to install the clean rom 2.5 custom rom successfully originally, and i made a backup through CWM, but I cant install any other rom on there for some reason. Yesterday I managed to go back to stock Asus jellybean rom successfully, and then had to root it and install CWM again successfully. I have again tried again today to install that EuroSkank rom, but alas, I get stuck at the ASUS boot logo permanently and nothing happens?
What might I be doing wrong??
I am on Jellybean. Thankfully the CWM is working fine and I could also restore my cleanrom2.5 backup.
Click to expand...
Click to collapse
( EuroSkank ) is also an ICS rom not JB - Clean rom 2.5 is JB. For now unless you have NVFlash you can't go back to ICS from JB and you can't run ICS rom with JB bootloader. (I'm using ICS and JB here to declare the bootloader )

Ok, Thank you very much.
tobdaryl said:
( EuroSkank ) is also an ICS rom not JB - Clean rom 2.5 is JB. For now unless you have NVFlash you can't go back to ICS from JB and you can't run ICS rom with JB bootloader. (I'm using ICS and JB here to declare the bootloader )
Click to expand...
Click to collapse

any1 with Partition not found problem, open zip and look at the folders, delete everything except folder you want (which is propably system) then write
fastboot flash system yourzip.zip
if this doesn't work for you then extract files from the folder and repack only files from the system folder and use the command above.
It doesn't work for me (dunno why) but it's something

[Q] JB update and custom kernel

Hi all,
I'm sorry about my stupid question but I really don't know nothing about that . I had rooted and flashed my NS and installed the matr1x kernel (very good btw), and now I knew that JB will be available to NS. My question is, need I back to stock kernel to receive the update?
Thanks
Sent from my Nexus S using xda app-developers app

Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
EDIT:
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Wish you the best of luck, and I am waiting for the Nexus S JB to come out as soon as possible

Ota binary patches the boot image iirc. So it can get all messed up.
Sent from my Samsung Epic 4G using Tapatalk 2

Yeah, what he said!
MДЯCЦSДИT said:
Ota binary patches the boot image iirc. So it can get all messed up.
Click to expand...
Click to collapse

andezzat,
Thank you very much for the help.
andezzat said:
Gnng
You have to understand that installing an OTA (official update) on a rooted device regardless of what kernel can cause problems, as it did with my Nexus S before. I suggest you make a NANDroid backup at all times before you install any ROMs, official or Custom. You can also use Titanium backup and others.
Click to expand...
Click to collapse
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
There's still a slight while until the new JB 4.1 comes out. It's suggested that you install a Custom JB 4.1 ROM for your Nexus S as though you don't cause any problems. I think it's OK if you do it with the kernel pre-installed. But people always install the Custom ROM THEN they install the Kernel, I think installing a new ROM always overwrites the kernel, if it comes with it.
Click to expand...
Click to collapse
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
In short, wait for the JB Custom ROM and you don't have to revert back to stock kernel, when you do the update it will automatically overwrite. Most Custom ROMs come with Stock/ordinary kernels. So then the user can flash whatever kernel they like in your case, matr1x.
Click to expand...
Click to collapse
I don't need to remove the kernel even unroot my cell, alright?
Thank you!!

Gnng said:
I didn't any backup before flashing a new kernel :crying:, so what can I do now if I want my stock kernel back?? What's a NANDroid (I know that is a tool but how can I do it?) ? Is Titanium bkp easily?
Click to expand...
Click to collapse
A NANDroid backup is a internal memory backup. You can create one by booting into Recovery (Power off your phone and Hold Power and Down on your volume buttons.) If you rooted your phone and unlocked your bootloader (that's what you had to do to flash a new kernel), you should be able to load ClockworkMod or TeamWin Recovery and do a backup of your phone.
Gnng said:
I prefer wait for stock JB Rom and probaby I'll , but, can I already find some JB ROM?
Click to expand...
Click to collapse
There's one rom but it's a port from the SDK and the amount of major bugs is high so it's not recommended but you could try another custom rom meanwhile, I can't go back to stock after trying custom roms, like AOKP and Cyanogenmod 9. Make sure you backup your apps and some settings (not everything will be compatible between stock and custom so pay close attention to which system setting you'll backup) with Titanium Backup.

To sum it all up for you
There's a Jelly Bean release which is unstable and has no sound, and will not be fixed until the REAL version comes out.
NANDroid backs up the whole internal memory on the phone including the system, it can be done from clockworkmod recovery.
Titanium backup, backs up specific settings and information that you choose, available from the playstore.
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
If you want to go back to a STOCK ROM after rooting a device, there's a way, check this guide
http://forum.xda-developers.com/showthread.php?t=1063664
and choose your Nexus S model: To acquire model, go to Settings - About - Baseband version. if it says I9023 at the start that's your Nexus S's model
Choose one of the Fastboot Stock ROMs and use the Fastboot method to flash the ROM. That is a good way to go back to STOCK ROM if anything bad happens
By the way you should expect the new OTA official 4.1 update for the Nexus S to be on your model's page.
NOTE: Using Fastboot to flash a ROM is very clean. However this will delete all your data and if you do everything correctly will lock your bootloader and unroot your phone. So use Fastboot only when you really feel the need to.
Cheers
and stay tuned for Jelly Bean :victory:

andezzat said:
To sum it all up for you
You don't need to unroot or go back to a STOCK kernel in order to flash a CUSTOM ROM. DO not however flash a STOCK rom after rooting, as at times that can cause problems.
Click to expand...
Click to collapse
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?

Gnng said:
That means, when I receive the official 4.1 update notification, I should unroot my phone first and just install it after?
Click to expand...
Click to collapse
OK first off, do not install the update using the system update method from about, as that is a 100% stuff up if you're still rooted or on a Custom ROM.
However to update I think flashing a stock ROM but USING Clockworkmod works fine!
Someone please confirm, as I am not 100% sure
However what I am sure about is that if you run into any troubles installing your STOCK ROM using Fastboot is very very good and clean, however there are 2 things:
1. You will wipe everything COMPLETELY
2. You need the ROM to be in a fastboot format kind of way for you to flash it
There's a guide and everything for fastboot.
---------- Post added at 12:35 AM ---------- Previous post was at 12:33 AM ----------
Personally I will wait for a custom ROM for 4.1 if it doesn't take too long as that's guaranteed and will obviously be faster and safer to install on a ROOTED device.
Someone still confirm if installing Stock ROM while over Custom ROM while ROOTED through CWM is OK or not!?

Hummm, ok...
I'm already using the Stock ROM, I just flashed a new kernel, and I prefer install the stock kernel and unroot my phone. Just to let it clean.
After I install the JB official update, maybe I flash and root again, depends of Google :laugh:
Do you know where can I download a trust official 4.0.4 kernel from the forums? My phone is a Nexus S I9020AUCKJ1, Version Number: IMM76D
Thanks!!!

[HOW-TO] Revert to Stock ROM JB for user with new HBOOT

Hi to All,
I want to share my experience about revert to stock for users that have new HBOOT, unlocked bootloader and custom recovery; can't execute official RUU. ( This method i think is more safe that downgrade HBOOT )
Step ONE:
Install this custom ROM: MaximuS ROM ( read the thread for instruction about installation of this ROM )
( this ROM allow you to receive the message of OTA JB update, if you know another ROM that receive this message you can use as well i think )
Step TWO:
install the stock recovery of HTC One S via fastboot ( after flashing recovery erase cache )
Step THREE:
Reboot your phone in system, configure the rom for first use, go to settings, information, software update and press check now for update.
You'll receive the message for an update, download and install, and now you have stock JB ROM. after reboot you can do a reset ( go to setting => backup and restore ) to clean the application migrated from previous ROM ( MaximuS )
I hope this can help someone else.
p.s. Sorry for my English!

Thanks bro for this, but my problem is not resolved because this rom couldn't install on my HTC One S, i dont know why... Log show me: MD5 files not found

CybulPL said:
Thanks bro for this, but my problem is not resolved because this rom couldn't install on my HTC One S, i dont know why... Log show me: MD5 files not found
Click to expand...
Click to collapse
Witch recovery are you using at the moment? I installed this ROM ( MaximuS ) with Team Win Recovery ( TWRP ) v2.3.3.0 and it's works for me.
( after flashing ROM from recovery remember to flash boot.img by fastboot )

Maverick87Shaka said:
Witch recovery are you using at the moment? I installed this ROM ( MaximuS ) with Team Win Recovery ( TWRP ) v2.3.3.0 and it's works for me.
( after flashing ROM from recovery remember to flash boot.img by fastboot )
Click to expand...
Click to collapse
I use TWRP and CWM and the same. My mate told me that i have unmount 1 and 2 partition in recovery but i don't know how.

Hi everyone,
thanks a lot, this saved my ass ... I had upgraded my stock ICS to stock JB and then tried to go back to stock ICS with a CWM backup - with the result that I had a brick booting only to a black screen.
I still had access to CWM recovery and so could install the Maximus 2.5 ROM and also the update to stock JB ran through just fine.
I did a factory reset afterwards, is it 100% sure that I now have a pure stock JB or could there be some leftovers from the Maximus 2.5 ROM?
Cheers,
Tim

tim_h said:
Hi everyone,
I still had access to CWM recovery and so could install the Maximus 2.5 ROM and also the update to stock JB ran through just fine.
I did a factory reset afterwards, is it 100% sure that I now have a pure stock JB or could there be some leftovers from the Maximus 2.5 ROM?
Cheers,
Tim
Click to expand...
Click to collapse
Yes you have a stock JB, because with factory reset you've removed all extra application that there is inside MaximuS v.2.5.
All other unneeded file or executable ( like root executable and all other script in /system ect. ) was removed during installation of new ROM.
Remember just that you need to revert to stock to give your phone back to HTC for guarantee, I thinks you must leave on it the stock recovery.
tim_h said:
Hi everyone,
thanks a lot, this saved my ass ... I had upgraded my stock ICS to stock JB and then tried to go back to stock ICS with a CWM backup - with the result that I had a brick booting only to a black screen.
Cheers,
Tim
Click to expand...
Click to collapse
It's happened because from recovery the system was unable to flash the boot partition. So after you did the CWM restore, you have all the phone with ICS android, but JB kernel, this cause your black screen after boot!!!
If you have the boot.img ( with suitable kernel of your old ROM ) to flash after you did the CWM recovery, you can get back to your BACKUP without any problem.
Also if you don't have the exactly boot.img of your previous ROM of the backup, you can flash any boot.img by fastboot of ICS kernel and this is should be enough to keep your backup running again.

Thanks very much for the additional explanations. I do have the boot.img of my original CWM backup, so should be able to restore it via fastboot. Great!
But first I have to send in my phone to have the USB port fixed under warranty.

Holy ****, is working, thanks man...

zujko said:
Wait to see if i understood, i have now Custom ( Virtuous Ville+ RC-1) JB ROM, with hboot 2.15.0000... unlocked, root, twrp
1.install maximuS V2.5, wipe..
2. flash boot.img with fastboot
3.Check update for JB, and flash new update JB?
And that's it?
I guess we have to make relock bootloader, after flash ICS?
Tnx
Click to expand...
Click to collapse
You just forgot in the list to install the HTC Stock recovery before check the message of update, so:
1 => Wipe and install MaximuS V2.5 ROM
2 => flash with fastboot boot.img of MaximuS V2.5 ROM
3 => flash stock HTC Recovery via fastboot ( fastboot flash recovery ville_recovery_signed.img , then fastboot erase cache ) or get it from One_S_All-In-One_Kit_v1.0
4 => start the phone and check for the JB update
5 => after JB installation do a factory reset to clean up the ROM from the extra application that MaximuS ROM have.
You don't need to relock your bootloader, you just need to install the stock recovery, that's enough.

Hmm, wait, why need install stock recovery?
This JB will be working with custom twrp?
EDIT: I got it

I did it! I unmounted first 3 partitions in TWRP and installation successful.

I am on stock Rom now and used HTC offical update to get to jb...do u think I will have trouble rooting again?
Sent from my HTC One S using xda premium

k1llacanon said:
I am on stock Rom now and used HTC offical update to get to jb...do u think I will have trouble rooting again?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I will let you know if I can get it working and flashed it will be rooted in seconds just need stock recovery.

Rooted without a problem, recommend the attached superuser app.

Maverick87Shaka said:
You just forgot in the list to install the HTC Stock recovery before check the message of update, so:
1 => Wipe and install MaximuS V2.5 ROM
2 => flash with fastboot boot.img of MaximuS V2.5 ROM
3 => flash stock HTC Recovery via fastboot ( fastboot flash recovery ville_recovery_signed.img , then fastboot erase cache ) or get it from One_S_All-In-One_Kit_v1.0
4 => start the phone and check for the JB update
5 => after JB installation do a factory reset to clean up the ROM from the extra application that MaximuS ROM have.
You don't need to relock your bootloader, you just need to install the stock recovery, that's enough.
Click to expand...
Click to collapse
Will this work on a T-Mobile HOS with CID HTC__001?
I have followed all the steps from above
- installed the rom
- installed the stock recovery
- then I was able to start the update but when it finished downloading .. I was told that the HTC software on my device has been modified and please revert back and try the update again and it would not preform the update.
What am I doing wrong?
Thanks in Advance

Hi once more,
after going back to pure stock JB this way, can I relock the bootloader to get "RELOCKED" instead of "UNLOCKED/TAMPERED"? (That would be good for sending in my phone under warranty.) Or will the phone stop booting if I relock the bootloader?
As far as I understood, the "canonical" way to get "RELOCKED" would be to lock the bootloader and install the RUU, but since there is no RUU for the unbranded JB yet and downgrading with an older RUU is not possible, I cannot do this.
Cheers,
Tim

tim_h said:
Hi once more,
after going back to pure stock JB this way, can I relock the bootloader to get "RELOCKED" instead of "UNLOCKED/TAMPERED"? (That would be good for sending in my phone under warranty.) Or will the phone stop booting if I relock the bootloader?
Cheers,
Tim
Click to expand...
Click to collapse
You can do Relock bootloader, i think it will boot to system without problem(?)

blah blah blah said:
Will this work on a T-Mobile HOS with CID HTC__001?
I have followed all the steps from above
- installed the rom
- installed the stock recovery
- then I was able to start the update but when it finished downloading .. I was told that the HTC software on my device has been modified and please revert back and try the update again and it would not preform the update.
What am I doing wrong?
Thanks in Advance
Click to expand...
Click to collapse
+ 1
Sent from my HTC One S using xda app-developers app

The only word of caution that I think needs to be shared on almost all threads related to JB updates is to make sure you DO NOT have SuperCID... There have been numerous reports of phones bricking with the OTA JB update with a SuperCID... So if you had previously SuperCID your phone with 11111111, definately change it to something else.

AKToronto said:
The only word of caution that I think needs to be shared on almost all threads related to JB updates is to make sure you DO NOT have SuperCID... There have been numerous reports of phones bricking with the OTA JB update with a SuperCID... So if you had previously SuperCID your phone with 11111111, definately change it to something else.
Click to expand...
Click to collapse
I had to go supercid to run the euro ruu and changed it to HTC__001. Ota still didn't work
Sent from my HTC One S using xda app-developers app

[Q] Question on ICS to JB update - Bootloader or Full?

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!

Lidenburg's Padfone 2 ROM [11.8.3.3-0]

Note: All of these are for SKU version WWE
This is a simple ROM for the Padfone 2, which has been deodexed, rooted (SuperSU), zipaligned, debloated and has busybox installed.
Instructions: Download the zip and flash it through your custom recovery of choice (stock recovery will not work), no need to wipe anything (assuming you're already running kitkat). I would only recommend flashing the kitkat version if you're already on Kitkat, since I haven't tried going straight from my Jelly Bean ROM to Kitkat.
These are the apps that were removed:
Asus Setup Wizard
Asus Social Network
Asus Task
Kindle
My Asus
My Frame
Omlet
Party rim binary
Press reader
Share rim binary
Splashtop
What's Next
Zinio reader
[Kitkat update]11.8.3.3-0: Download: https://drive.google.com/file/d/0B7ERGWwrBwR8RmhmeGsxaTUzbjQ/edit?usp=sharing
10.4.17.7-0: Download: https://docs.google.com/file/d/0B7ERGWwrBwR8d3N3bjA0T2Y5amM/edit?pli=1
10.4.16.8-0: Download: https://mega.co.nz/#!Xd5i1KKR!NWGRF2Tp8xEF0oVQEsiod3H06QhpRkqVDeiDkmxBdKs
10.4.15.1-0: Download: https://mega.co.nz/#!OBJFxQgS!EXbdDAiNwMcLDmixsEP6enEcJcJabhzYPVHQQekCKm8
10.4.12.24-0: Download: http://www.4shared.com/zip/1xHdyELY/A68-update-1224-rooted-deodexe.html

Thank you so much! Downloading now.

@lindenburg
My Padfone2 is running KitKat, rooted (towelroot) but with locked bootloader (since I updated to KitKat and Unlock.apk doesn't work on it).
Can I install your rom through stock recovery?

so we have to update to stock kitkat first?
i am using Guerilla ROM atm.

@rafael_mfr No I'm pretty sure that won't work, I'm pretty sure you can only flash Asus zip files that have the Asus signature with the stock recovery.
@BPM Yes I would only recommend flashing this from kitkat, I haven't tried flashing it from Jelly Bean, so I don't know if it will work or not, but there's a good chance it won't considering that I had problems going from modded Jelly Bean to a slightly modified version of Kitkat.

Lidenburg said:
@BPM Yes I would only recommend flashing this from kitkat, I haven't tried flashing it from Jelly Bean, so I don't know if it will work or not, but there's a good chance it won't considering that I had problems going from modded Jelly Bean to a slightly modified version of Kitkat.
Click to expand...
Click to collapse
so i have to flash back to stock => then update to kitkat => then your rom.
3 firmwares to reach the goal ;-(

You shouldn't have to flash back to stock and then flash kitkat, just wipe everything, flash the stock recovery and flash kitkat through there and then flash the custom ROM.

Lidenburg said:
You shouldn't have to flash back to stock and then flash kitkat, just wipe everything, flash the stock recovery and flash kitkat through there and then flash the custom ROM.
Click to expand...
Click to collapse
I think this won't work ... Don't know what ASUS did with this KK update, but it just doesn't work when flashed clean. Tried many times (both stock and custom recovery, wiped everything including system) and always got stuck on white ASUS logo. It only works when upgraded from stock Jelly Bean.
So yeah, I'd say 3 ROM flashes are necessary in this case.

I tried to flash to lindenburg's 11.8.3.3-0.zip
From the original Asus kitkat Rom on my Padfone 2
Used power on + volume down
Boot to recovery
Apply update from extended storage
Selected lindenburg's 11.8.3.3-0.zip
Then got system needs to reboot
It started the check to flash
E: footer is wrong
E: signature verification failed
Installation aborted
Any hint on how to flash it to this Rom without bricking my phone?

Flash Lidenburg's 11.8.3.3-0
Hi,
for me it worked using TWRP 2.6.3.0
Regards

Sins my new pc running win 8.1 I have trouble using adb
Can't I do it from my phone the easy way please lol

You're using the stock recovery that's why it's not working, I thought that was common knowledge but since I've had 2 people ask why they're getting that error I guess it's not, I'll edit post to clarify that you need a custom recovery.

Thanks been a few years sins I moded or flashed android

I am missing something
Got me towelroot supersu busybox all successfully installed and working
Installed twrp works too
Select lindenburg's zip to install
Phone boots to recovery I select the zip again and errors stay the same
so I am still missing a custom recovery I reckon
Anyone who can give me a hint on how to get one?
And what way to get it on my phone

Make sure to remove system/etc/install-recovery.sh, otherwise the stock recovery will get flashed automatically again.

Lidenburg said:
Make sure to remove system/etc/install-recovery.sh, otherwise the stock recovery will get flashed automatically again.
Click to expand...
Click to collapse
well my recovery image of choice was the wrong choice
all i get now is bootscreen that sais on top Invalid Kernel !!!
i used [ROOT] Rashr - Flash Tool got it from playstore
selected twrp under recovery and then selected the highest (A68) image version 1.7.1.0 i believe
only hope i did not brick it
any help is greatly appreciated
---------- Post added at 07:36 AM ---------- Previous post was at 07:24 AM ----------
and a lionk to a custom recovery image that works on my padfone with kitkat would also be nice if i did not brick it

wel i found the TWRP 2.6.3.0 recovery image but fastboot FAILED (remote: can't flash unsigned image)
so now i can only hope someone here can make the original stock recovery image available for download

It sounds a lot like you haven't unlocked the bootloader, have you downloaded the Unlock.apk from Asus' website and followed the instructions in the app?
I linked the stock recovery to this post for you, unzip it and flash it in fastboot.

thanks for helping me out here bro
this keeps me from sending my device to asus
---------- Post added at 08:02 PM ---------- Previous post was at 07:51 PM ----------
recovery flash says writing recovery okay
but keeps hanging in boot screen with invalid kernel !!!
but could boot to recovery and after whipe cache i got my phone back to life
it now boots normal again

oke renamed system/etc/install-recovery.sh to original.install-recovery.sh-a got twrp 2.6.3.0 recovery image installed
boot to recovery checked the version on top now only shows e3
apply update from external storage
selecting your zip
Finding update package
opening update package
verifying update package
installation aborted
droid lying on his back with a red red triangle with ! on it out of its belly
if i reboot all works normal
only wonder what i am still missing here
---------- Post added at 09:47 PM ---------- Previous post was at 09:39 PM ----------
just checked Rashr tool history and the strange thing is
openrecovery-twrp-2.7.1.0-A68.img broke my device with Invalid Kernel !!!!
it is newer than the 2.6.3.0 i am using now