Procedure if you ARE NOT running baseband JYUS06032013 (ICS Basebands) :
boot ICS CWM
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
restart start recovery/adb reboot recovery (JB CWM is installed - do not try to fastboot boot ICS CWM)
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
Procedure if you ARE running baseband JYUS06032013 (JB Baseband) :
get root (Instructions HERE - use GANDALF)
install CWM (Instructions HERE)
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
reboot to CWM
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
This ROM is Pantech stock stock stock with no mods other than CWM installation protection and all stock permissions and symlinks carefully maintained and consistent with the product of a successful OTA. It runs well with nothing broken. You MUST be on JB firmware (below) to run it properly.
The firmware is also stock, with the exception of the open aboot allowing fastboot boot <bootimage>, and installation of JB CWM with nothing else added or changed.
You can let the new CWM root it if you like when you exit - it will prompt you.
Downloads:
md5: 1a0ca5f177bce2f4c428931616e0ecd1 FLEX-JB-JYUS06032013-FIRMWARE.zip
md5: 17c0e611ab6dfbca230571c1e40f3d14 FLEX-JB-JYUS06032013-ROM.zip
Code:
[B]GPL INFO[/B]
The kernel used in the ROM is the unaltered, stock rom
and boot image provided by the Pantech OTA.
The kernel used in CWM provided I built from unaltered
Pantech provided source code.
The source code for both kernels can be obtained on the
[URL="http://opensource.pantech.com/"]Pantech Open Source[/URL] website.
:good::good::good::good::good::good::good:
much appreciated. i am dreaming of it will do it tonight and post the result.
attn1 said:
Procedure if you ARE NOT running baseband JYUS06032013 (ICS Basebands) :
boot ICS CWM
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
restart start recovery/adb reboot recovery (JB CWM is installed - do not try to fastboot boot ICS CWM)
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
Procedure if you ARE running baseband JYUS06032013 (JB Baseband) :
get root (Instructions HERE - use GANDALF)
install CWM (Instructions HERE)
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
reboot to CWM
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
This ROM is Pantech stock stock stock with no mods other than CWM installation protection and all stock permissions and symlinks carefully maintained and consistent with the product of a successful OTA. It runs well with nothing broken. You MUST be on JB firmware (below) to run it properly.
The firmware is also stock, with the exception of the open aboot allowing fastboot boot <bootimage>, and installation of JB CWM with nothing else added or changed.
You can let the new CWM root it if you like when you exit - it will prompt you.
Downloads:
md5: 1a0ca5f177bce2f4c428931616e0ecd1 FLEX-JB-JYUS06032013-FIRMWARE.zip
md5: 17c0e611ab6dfbca230571c1e40f3d14 FLEX-JB-JYUS06032013-ROM.zip
Code:
[B]GPL INFO[/B]
The kernel used in the ROM is the unaltered, stock rom
and boot image provided by the Pantech OTA.
The kernel used in CWM provided I built from unaltered
Pantech provided source code.
The source code for both kernels can be obtained on the
[URL="http://opensource.pantech.com/"]Pantech Open Source[/URL] website.
Click to expand...
Click to collapse
after a few days to stay with this JB on my flex. i found big problem with WIFI connectivity:
1 - connect and used about 10 to 30mn,, it is still connected but no internet.
2 - reconnect -> authentication problem.
3 - reboot a fews time to make wifi back to work.
4 - back to problem number 1
5 - Camera App still randomly cant be used unless restart. ( same problem since ICS )
6 - some intensive graphic games cause reboot the phone, eg Clash of Clans ( new in this JB)
What is good about JB is feel smooth and faster.
Any help, please?
Thanks @attn1! Works great.
Sent from my PantechP8010 using Tapatalk
tangbunna said:
after a few days to stay with this JB on my flex. i found big problem with WIFI connectivity:
1 - connect and used about 10 to 30mn,, it is still connected but no internet.
2 - reconnect -> authentication problem.
3 - reboot a fews time to make wifi back to work.
4 - back to problem number 1
5 - Camera App still randomly cant be used unless restart. ( same problem since ICS )
6 - some intensive graphic games cause reboot the phone, eg Clash of Clans ( new in this JB)
What is good about JB is feel smooth and faster. My wifi works fine, and the camera works fine.
Any help, please?
Click to expand...
Click to collapse
Try flashing my firmware package again, then flashing the ROM again. If you still have these issues, then wipe data/factory reset from clockworkmod. This is working for everyone else reporting, including me.
THIS work on Motorola defy
ela1103 said:
THIS work on Motorola defy
Click to expand...
Click to collapse
highly unlikely to impossible in this version of reality.
Look at mac address of both phone. They are the same. And both phone connected to the same ip of a router.
Even i use 2 routers, and connect one each, they seems to drop connection very often.
Unless a phone turn wifi off to let other one stay in good connection.
Do you have another alternative firmware file? So it could have different mac address ?
tangbunna said:
Look at mac address of both phone. They are the same. And both phone connected to the same ip of a router.
Even i use 2 routers, and connect one each, they seems to drop connection very often.
Unless a phone turn wifi off to let other one stay in good connection.
Do you have another alternative firmware file? So it could have different mac address ?
Click to expand...
Click to collapse
Looks like you restored the same /data backup to each phone. MAC address is determined by your wifi hardware, not this firmware.
attn1 said:
Looks like you restored the same /data backup to each phone. MAC address is determined by your wifi hardware, not this firmware.
Click to expand...
Click to collapse
I did not restore anything. While both phones on ics they both worked fine without duplicated mac address issue. Then i followed the instruction of the 2 files for upgrade to jelly bean. I didnt do any back up or restore. Just flash the firmware zip then jb rom zip the. Everything of my data are still there wifi are working fine untill i flash another phone to jelly bean too, both phone must have one wifi to turn off to make another one's wifi works fine.
Do you have the flex and upgraded to jelly bean by this two files? Could you tell me your mac address of your wifi ?
tangbunna said:
I did not restore anything. While both phones on ics they both worked fine without duplicated mac address issue. Then i followed the instruction of the 2 files for upgrade to jelly bean. I didnt do any back up or restore. Just flash the firmware zip then jb rom zip the. Everything of my data are still there wifi are working fine untill i flash another phone to jelly bean too, both phone must have one wifi to turn off to make another one's wifi works fine.
Do you have the flex and upgraded to jelly bean by this two files? Could you tell me your mac address of your wifi ?
Click to expand...
Click to collapse
Apologies. I've verified the problem, have traced it to mmcblk0p10, and here's a fix for you that changes the MAC by one:
Flash this from CWM:
md5: 4e7940c1b5d3690e0e38b083f224a7f1 OSCAR-WIFI-MACFIX.zip
NOTES:
This problem is because the hardware MAC is stored in that partition and read by the wifi firmware. It should never present a problem for people unless they have more than one Flex running this update on the same local area network subnet.
The MAC address starts in mmcblk0p10 at hex offset 30204, and an image file of this partition can be edited CAREFULLY with a hex editor and copied back to that partition. Doing this wrong may result in a bricked device.
attn1 said:
Apologies. I've verified the problem, have traced it to mmcblk0p10, and here's a fix for you that changes the MAC by one:
Flash this from CWM:
md5: 4e7940c1b5d3690e0e38b083f224a7f1 OSCAR-WIFI-MACFIX.zip
NOTES:
This problem is because the hardware MAC is stored in that partition and read by the wifi firmware. It should never present a problem for people unless they have more than one Flex running this update on the same local area network subnet.
The MAC address starts in mmcblk0p10 at hex offset 30204, and an image file of this partition can be edited CAREFULLY with a hex editor and copied back to that partition. Doing this wrong may result in a bricked device.
Click to expand...
Click to collapse
you are genius man! my wifi now changed from ending e9 to f9. no more duplicated :good::good::good::good::good:.
send me your paypal to my inbox, i will buy you a beer! :highfive:
big thanks and cheers !!!
Flex stuck on logo.
only 25% complete. then said signature verification failed?? pls help. (no cwm. only stock)
shusan said:
only 25% complete. then said signature verification failed?? pls help. (no cwm. only stock)
Click to expand...
Click to collapse
You have not provided enough information for me to help you. What was the detailed sequence of events leading to this. Be precise and make sure you list exactly the packages you flashed.
Flex stuck on logo.
thanks for ur quick reply. i was too sick to answer u. so sorry for late. i tried with sd memory update which show me 25% with stock image then show signature verrificatin failled. al most same result from fastboot. signature verification failed. no connection via ADB. i downloaded almost each and every rom and image i found from xda or other forum result r all same. sorry for my English. best regards
attn1 said:
You have not provided enough information for me to help you. What was the detailed sequence of events leading to this. Be precise and make sure you list exactly the packages you flashed.
Click to expand...
Click to collapse
shusan said:
thanks for ur quick reply. i was too sick to answer u. so sorry for late. i tried with sd memory update which show me 25% with stock image then show signature verrificatin failled. al most same result from fastboot. signature verification failed. no connection via ADB. i downloaded almost each and every rom and image i found from xda or other forum result r all same. sorry for my English. best regards
Click to expand...
Click to collapse
In recovery (cwm), check the md5 of the file on the sdcard against the posted md5 like so:
adb shell md5sum /path/filename
If it's not matching, you will get that error.
If you don't have the shipping ICS aboot, you may be stuck. You can't flash or boot images if you've taken the jb update. You still haven't detailed what you started with and what you have tried to do and where it went wrong, so it's hard to tell you exactly what to do or even if there is anything to do.
Any idea about stock rom? I don't have cwm. Only need to restore using original farmware. P8010 already stuck.
shusan said:
Any idea about stock rom? I don't have cwm. Only need to restore using original farmware. P8010 already stuck.
Click to expand...
Click to collapse
There is no stock firmware from Pantech available. If you messed up and can't boot with the JB bootloader, you are screwed.
attn1 said:
There is no stock firmware from Pantech available. If you messed up and can't boot with the JB bootloader, you are screwed.
Click to expand...
Click to collapse
No stock firmware from Pantech? I thought the firmware in the first post is STOCK? No? What about a caught copy from the OTA from AT&T?
Related
I'm some noob with Asus Transformer
I was using Revolver ROm, but I want to go back to stock rom, so with CWM I've used my nandroid backup of 8.5.9.19 rom, with root and cwm, which worked perfect, then with OTA Root I've tried to remove temporarily and that's ok, but when I've tried to updade via no way to do it, since que cwm it's not the stock one.
I've downloaded the 2 files from the 1st post and execute as indicated, it worked, now with .13, but I have to major issues:
1 - WIFI - not recognizing my router, find's all the ones around but not my own, never had issues with this, I have my Galaxy working perfect, I remember with Galaxy that there some change to be made in order to make it work when that happens
2 - Stock Recovery - if I want to do a wipe data, it works ok, but when I try to use it for Recovery,starts and hangs right after with the triangle displayed
I have a B70 device, so reading around looks that nvflash as some problems
My ideia is to have a net connection to download a newer version and correct the mess I've done
Thanks for your help
I have Razor Root and RecoveryInstaler in my microcard, but if I want to aply them returns an error
Sorry for the double post
edit. Problem with WIFI related to channel in my router, changed to 11 and works, update made and chennel 13 can be used again
Pisca said:
I've downloaded the 2 files from the 1st post and execute as indicated, it worked, now with .13, but I have to major issues:
2 - Stock Recovery - if I want to do a wipe data, it works ok, but when I try to use it for Recovery,starts and hangs right after with the triangle displayed
I have Razor Root and RecoveryInstaler in my microcard, but if I want to aply them returns an error
Click to expand...
Click to collapse
Stock recovery is just that, it doesn't have options like a custom recovery (CWM).
Basically when you boot into stock recovery it scan for an update package, if not there it goes no further.
You indicate you have .13 firmware. Razorclaw need .19 firmware to work.
baseballfanz said:
Stock recovery is just that, it doesn't have options like a custom recovery (CWM).
Basically when you boot into stock recovery it scan for an update package, if not there it goes no further.
You indicate you have .13 firmware. Razorclaw need .19 firmware to work.
Click to expand...
Click to collapse
THanks for your explanation, now I'm with .21 stock one, no root, for now, after solve the wifi issue, remember that .13 rom, do not work with wifi with channel 13, only after that
I decided to return to stock today so i could check out the newest ota which was not implemented in my fav rom yet. I soon realized its a pain in the ass to get there. Flash rom, update, update, etc, etc. And even worse is tracking down all the threads required for it.
Though I've narrowed it down to three or four, I thought i'd make a thread to put it all in one spot.
First off thanks to the members/devs that make these updates and roms for us. I dev on the HTC eVO 4g and know how time consuming and tedious it can be.
I am renaming and reuploading all the files required to ensure links stay current and are easy to follow. I will however be linking to all original threads where i got the files as well as giving props to the members who provided them.
I have a US version TF101 and will only be testing on that device. I dont know what works on tf101G, WW, TW models etc
I will update this thread as new rooted ota's come out.
ALL YOU NEED TO INSTALL IS A ALREADY ROOTED ASUS TRANSFORMER WITH A CUSTOM RECOVERY
THIS WILL NOT ROOT YOUR DEVICE, UN-ROOT YOUR DEVICE OR CHANGE YOUR CURRENT RECOVERY.
DONT FORGET TO BACK UP ALL YOURS APPS/DATA
FOR US VERSIONS ONLY
- STEP 1 - WIPE (DOWNLOAD) (This wipe zip was originally provided HERE by mike1986.
This script will erase and format your system and cache partition using EXT4 file-system ---Your external SD card and internal virtual SD card (/data/media) will remain untouched
- STEP 2 - FLASH STOCK ROOTED 9.2.1.11 FULL ROM AND REBOOT/SETUP (DOWNLOAD) originally provided here by MrNago
- STEP 3 - FLASH ROOTED OTA 9.2.1.17 AND REBOOT (DOWNLOAD) originally provided HERE by daoist
-STEP 4 - FLASH ROOTED OTA 9.2.1.21 AND REBOOT (DOWNLOAD) originally provided HERE by gee one
FOR WW VERSIONS ONLY
- STEP 1 - WIPE (DOWNLOAD) (This wipe zip was originally provided HERE by mike1986.
This script will erase and format your system and cache partition using EXT4 file-system ---Your external SD card and internal virtual SD card (/data/media) will remain untouched
- STEP 2 - FLASH STOCK ROOTED 9.2.1.11 FULL ROM AND REBOOT/SETUP (DOWNLOAD) originally provided here by MrNago
CANT FIND ROOTED VERSIONS OF THE NEXT FEW UPDATES THAT DONT REQUIRE ROOT KEEPER, SO IM STOPPING HERE. THIS WILL GET YOU STARTED THOUGH. i JUST DONT WANT TO BE RESPONSIBLE FOR NEWBS THAT CANT READ LOSING ROOT.
FAQ
-Will this root my transformer = no
-Will I lose root if i flash this = NO
-Can i flash this on top of a custom rom = NO
-Will this replace the custom recovery with the stock recovery? = NO, this will not touch your current recovery
-OMG, I lost root after this = NO you didnt or you did something wrong.
Can you explain why step 2 and 3 are needed?
You couldn't go from 1 to 4 if you want 9.2.1.21?
locutus7o9 said:
Can you explain why step 2 and 3 are needed?
You couldn't go from 1 to 4 if you want 9.2.1.21?
Click to expand...
Click to collapse
its my understanding that you have to have the last prior ota installed to be able to install the next. The last update may not include everything from the others.
Will this replace the custom recovery with the stock recovery?
xbs said:
Will this replace the custom recovery with the stock recovery?
Click to expand...
Click to collapse
I knew i'd forget one of the typicals in the FAQ..
Answer is no, this will not change/touch your current recovery
I wanted to return to stock Rom too, but I have seen your topic too late....
I first saved my root with rootsavekeeper
I have wiped cache and dalvik, and then install the rom
Now, I have a bootloop with the Asus logo, and if I try boot in recovery, I have the red robot
If u have a solution, I take it
Sorry for my english
jouix said:
I wanted to return to stock Rom too, but I have seen your topic too late....
I first saved my root with rootsavekeeper
I have wiped cache and dalvik, and then install the rom
Now, I have a bootloop with the Asus logo, and if I try boot in recovery, I have the red robot
If u have a solution, I take it
Sorry for my english
Click to expand...
Click to collapse
What ROM did you flash? If you flashed the official ROM from Asus you unrooted the TF.
Looks like you have stock recovery now.
Yes I have
My biggest problem is to get out on this sh*t Now
jouix said:
Yes I have
My biggest problem is to get out on this sh*t Now
Click to expand...
Click to collapse
Try this.
Hold Vol down plus power button
When you get the option of COld boot Linux or wipe data,
choose wipe data.
jouix said:
Yes I have
My biggest problem is to get out on this sh*t Now
Click to expand...
Click to collapse
What model do you have? B50, B60, B70?
If you have a B50 or B60, try this
Once you get back to stock honeycomb, you'll have to root it again.
@baseballfanz : Guy, you have saved my tablet .. I had almost throwed it in the garbage
@ldc2335 : I have bought it in France, and no idea about the version, sorry .. (I don't have the dock)
Well, now, I willl see if it is stable or not :
- if it is, I need to find the way to root it (but I have read it's not possible with the last Rom, right ?)
- if not ... I will try to return to Honeycomb and sell this piece of sh*t, and I will buy the Galaxy S3 or will wait for the Note 2
Thx again !!!!
I use NVflash way and from modded(rooted/CWM/Overclock) 9.2.1.17 directly flash back to stock clean 9.2.1.17 and it's very quick... and root it agan via Vipermod and flash 9.2.1.21 update zip.. Takes about lest than 30mins..
Thats one way to do it. I just dont wanna re-root etc.
Flash, reboot, flash, reboot, flash, reboot..done Definitly 30 mins or less.
jouix said:
@baseballfanz : Guy, you have saved my tablet .. I had almost throwed it in the garbage
@ldc2335 : I have bought it in France, and no idea about the version, sorry .. (I don't have the dock)
Well, now, I willl see if it is stable or not :
- if it is, I need to find the way to root it (but I have read it's not possible with the last Rom, right ?)
- if not ... I will try to return to Honeycomb and sell this piece of sh*t, and I will buy the Galaxy S3 or will wait for the Note 2
Thx again !!!!
Click to expand...
Click to collapse
If you can return to honeycomb, then just reroot and then flash any rom you want. Whats the issue?
Simple, clear, straightforward directions - very nice. The file naming is clever also, no "now which file do I flash next?..."
Does anyone have a clue where i can find cwm flashable WW Stock Roms with Original Recovery and no root?
Want to revert back to full basic!
(Tried to flash Stock Rom from Asus Website via CWM, didn't work...)
Try This
JohnMcLane said:
Does anyone have a clue where i can find cwm flashable WW Stock Roms with Original Recovery and no root?
Want to revert back to full basic!
(Tried to flash Stock Rom from Asus Website via CWM, didn't work...)
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=1558170
i just used the search bar above, im sure theres more than this one.
You will also need a NVflashable tf101 with this....
I hve succesfully flashed the .11 version, but when I try to update to the next version, it restarts, and starts loading the installation as it is supposed to, ut then it says "installation aported"
I am using Rootkeeper and CWM, and have temp. unrooted, I am using a B70 WW.
Anyone have a solution?
Sumsar94 said:
I hve succesfully flashed the .11 version, but when I try to update to the next version, it restarts, and starts loading the installation as it is supposed to, ut then it says "installation aported"
I am using Rootkeeper and CWM, and have temp. unrooted, I am using a B70 WW.
Anyone have a solution?
Click to expand...
Click to collapse
Same here, its an assert issue, I remember dealing with it when flashing my epic touch and I believe that had to do with the version of CWM that it was being flashed from
can anyone confirm?
EDIT: B40 using roach v5.5.0.4 r2 CWM
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
Hi eveyone, I updated my stock from 4.0 to 4.1 through odin and it was really painless. Sorry if this sounds lazy but can you install cm the same way? Doing the whole CW etc. seems a lot of steps - i'd rather upload one file only if possible. Thanks!
Guiyoforward said:
Hi eveyone, I updated my stock from 4.0 to 4.1 through odin and it was really painless. Sorry if this sounds lazy but can you install cm the same way? Doing the whole CW etc. seems a lot of steps - i'd rather upload one file only if possible. Thanks!
Click to expand...
Click to collapse
i do not think you can install zip with odin
LitD said:
i do not think you can install zip with odin
Click to expand...
Click to collapse
Thanks. You cannot - what I mean is: is CM ever realeased as a TAR-compatible ODIN file?
That can certainly be done. But it's not the norm.
Sent from my SGH-T699 using Tapatalk
James chdset
Nardholio said:
That can certainly be done. But it's not the norm.
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
Thanks Nardholio. I'm obviously missing some important feature CWM offers thatthe "odin process" does not. Is it seamless backup amd restore? Or is it the possibility of adding patches and new stuff - say, gapps on top of CM?
Thanks again!
G.
Deleted because I reposted in the intended thread
Guiyoforward said:
Thanks Nardholio. I'm obviously missing some important feature CWM offers thatthe "odin process" does not. Is it seamless backup amd restore? Or is it the possibility of adding patches and new stuff - say, gapps on top of CM?
Thanks again!
G.
Click to expand...
Click to collapse
CWM offers both of those things as an advantage, yes. You also can use CWM with the Stock image to gain the backup and restore features, amongst others.
And really, if you're already running Stock JB, the process is as simple as:
Place The cm-10.2-XXXXXXXX-NIGHTLY-apexqtmo.zip and gapps zip files on your phone, either on the 'internal' or external SD Card. (This even is optional, as they can be sideloaded if you have adb)
Flash CWM with Odin or Heimdall.
Reboot into recovery
Flash the cm nightly.zip
Flash the gapps.zip
wipe /cache with CWM.
Issue a factory reset with CWM.
Reboot to system.
If you're still on ICS, then you just need to add the steps of flashing the JB-stock-modem.zip and JB-stock-bootloader.zip before flashing the cm-nightly.zip (Turn GPS OFF before flashing these, specifically the modem, just to be on the safe side)
If you perform a backup with CWM before flashing anything, you can restore your stock system as you please.
If you simply want to root your relay, flash an appropriate recovery flashable zip copy of Superuser or SuperSU instead of flashing anything else.
kilr00y, along with providing the JB-stock-modem and JB-stock-bootloader recovery-flashable zip files, also provided a JB-stock-image.zip that can be used to go back to a stock-like system.
CWM allows you for a much greater amount of control over your phone, even when still running a stock image, due to the flexibility of being able to flash new applications directly to the system directories (such as Superuser/SuperSU) without having to have everything be signed by Samsung.
Magamo said:
CWM offers both of those things as an advantage, yes. You also can use CWM with the Stock image to gain the backup and restore features, amongst others.
And really, if you're already running Stock JB, the process is as simple as:
Place The cm-10.2-XXXXXXXX-NIGHTLY-apexqtmo.zip and gapps zip files on your phone, either on the 'internal' or external SD Card. (This even is optional, as they can be sideloaded if you have adb)
Flash CWM with Odin or Heimdall.
Reboot into recovery
Flash the cm nightly.zip
Flash the gapps.zip
wipe /cache with CWM.
Issue a factory reset with CWM.
Reboot to system.
Click to expand...
Click to collapse
THANKS! This is by far the easiest step by step instructions I've seen, and gladly I'm on stock JB already.
Will give this a try
thanks again!
just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!
Guiyoforward said:
just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!
Click to expand...
Click to collapse
In all honesty, ODIN itself is an underdocumented POS, the recovery.img file (or in this case, the renamed apexq_recovery-10.2.img file if you were following along with the wiki) comes right from the build process, it can be flashed directly without much tooling about with it using heimdal, which is an open source replacement for ODIN, that works very well. Heimdall can be used optionally with a GUI, but I personally use it from the command line, to get it to flash a recovery image to the recovery partition of a Relay, it's simply:
heimdall flash --recovery apexq_recovery-10.2.img
Guiyoforward said:
just booted into apex CM 347 nightly after the... ehem... peculiar apex logo thanks a lot for your effort.
now, I am a noob but can find my way around. I still think the whole process (CM and co, not the relay 4g per se) is a bit convoluted and underdocumented. just an example: I downloaded the IMG file from CWM but it took me a while to figure out that I had to transform it into md5 for it to play nice with odin, etc.
buy hey. I'm going to setup my system.
thanks everyone!!
Click to expand...
Click to collapse
How did you transform the img to md5 (I can also take the cwm in md5 format from the root thread, am I right?) ?
So I can flash anything without root using this method (even recovery) ? I couldn't do this with my desire Z, it's confusing me !
Which recovery should I flash to use cm10.2 (the cwm or the apexq_recovery-10.2.img ?) ?
=> If I use an older recovery I can't flash any jelly been rom's ?
robuser007 said:
(I can also take the cwm in md5 format from the root thread, am I right?)
Click to expand...
Click to collapse
yes, you can
robuser007 said:
So I can flash anything without root using this method (even recovery) ? I couldn't do this with my desire Z, it's confusing me !
Click to expand...
Click to collapse
there are several differences. you can flash recovery via odin to a not rooted device
robuser007 said:
Which recovery should I flash to use cm10.2 (the cwm or the apexq_recovery-10.2.img ?) ?
Click to expand...
Click to collapse
google 'install cyanogenmod samsung relay' and follow 'how to install cyanogenmod for samsung relay' wiki. 'installing cyanogenmod from recovery' is the same as for desire z
Ok so.. here's a quick guide to flashing 5.0.1 on the Nvidia Shield Tablet. I have the 16GB Wifi version so if you have a different version (LTE or non-US tablet) this guide may or may not apply to you. I also essentially dirty flashed this in CWM recovery. If you're using TWRP WIP, no idea if it will blow up or not. Standard disclaimer applies if your Tablet blows up or anything, i'm not responsible. You do these steps at your own risk. I'm going on the premise that you have the Shield drivers already installed and have some flashing knowledge.
This is an upgrade from 5.0 to 5.0.1
This guide DOES NOT utilize the OTA zip that your tablet downloaded.
1. Download http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29082_493.9700.zip (AGAIN, US 16gb WIFI only, there's another thread here somewhere with other full download links) I copied it to external SDCard rather than tablet storage.
2. adb reboot recovery to get into CWM or shut down and use the hardware keys to reboot to recovery
3. In CWM, install zip from external sd card and flash it like a normal rom. CWM reports this sucessful and reboot to 5.0.1 and let it settle. It updates binaries and blah blah. Oh also root and recovery are now gone. You should still have fastboot.
4. reboot into fastboot, hardware keys again or using adb reboot bootloader.
5. Now you follow the excellent post by sandrodjay for restoring CWM and root. (If you didn't wipe, most of the preliminaries in sandrodjay's post should already be done. Debug mode and whatnot) http://forum.xda-developers.com/shi...t-lollipop-t2972316/post57719881#post57719881
After the dust settled for me, i was on 5.0.1 and had CWM and root back. YMMV.
terrigan said:
Ok so.. here's a quick guide to flashing 5.0.1 on the Nvidia Shield Tablet. I have the 16GB Wifi version so if you have a different version (LTE or non-US tablet) this guide may or may not apply to you. I also essentially dirty flashed this in CWM recovery. If you're using TWRP WIP, no idea if it will blow up or not. Standard disclaimer applies if your Tablet blows up or anything, i'm not responsible. You do these steps at your own risk. I'm going on the premise that you have the Shield drivers already installed and have some flashing knowledge.
1. Download http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29082_493.9700.zip (AGAIN, US 16gb WIFI only, there's another thread here somewhere with other full download links) I copied it to external SDCard rather than tablet storage.
2. adb reboot recovery to get into CWM or shut down and use the hardware keys to reboot to recovery
3. In CWM, install zip from external sd card and flash it like a normal rom. CWM reports this sucessful and reboot to 5.0.1 and let it settle. It updates binaries and blah blah. Oh also root and recovery are now gone. You should still have fastboot.
4. reboot into fastboot, hardware keys again or using adb reboot bootloader.
5. Now you follow the excellent post by sandrodjay for restoring CWM and root. (If you didn't wipe, most of the preliminaries in sandrodjay's post should already be done. Debug mode and whatnot) http://forum.xda-developers.com/shi...t-lollipop-t2972316/post57719881#post57719881
After the dust settled for me, i was on 5.0.1 and had CWM and root back. YMMV.
Click to expand...
Click to collapse
What CWM version are you using? My CWM is reporting a failure to update because it thinks I'm still running Android 4.4.2.
dibblebill said:
What CWM version are you using? My CWM is reporting a failure to update because it thinks I'm still running Android 4.4.2.
Click to expand...
Click to collapse
Did you for download full ota zip 700mb or did you try flashing partial which you would get through system update
Full ZIP not OTA. The 700mb download. Also i'm using the flashed recovery.img from sandrojay's post which is CWM 6.0.5.0. Are you guys on 5.0 or 4.4.4? I suppose i should mention this is an upgrade from 5.0 to 5.0.1
terrigan said:
Full ZIP not OTA. The 700mb download. Also i'm using the flashed recovery.img from sandrojay's post which is CWM 6.0.5.0. Are you guys on 5.0 or 4.4.4? I suppose i should mention this is an upgrade from 5.0 to 5.0.1
Click to expand...
Click to collapse
I'm running the stock lollipop build. I tried removing the checks from the updater script but it still won't install.
dibblebill said:
I'm running the stock lollipop build. I tried removing the checks from the updater script but it still won't install.
Click to expand...
Click to collapse
Are you running the same CWM?
dibblebill said:
I'm running the stock lollipop build. I tried removing the checks from the updater script but it still won't install.
Click to expand...
Click to collapse
It sounds like you are trying to install the partial ota can you confirm
Yeah this guide isn't meant to utilize the OTA zip. My first instruction is to download the whole 700mb update.
mcord11758 said:
It sounds like you are trying to install the partial ota can you confirm
Click to expand...
Click to collapse
terrigan said:
Yeah this guide isn't meant to utilize the OTA zip. My first instruction is to download the whole 700mb update.
Click to expand...
Click to collapse
I see that now. Downloading the full OTA. Modified your link to the "do" version.
It worked this time though I oddly didn't need to reflash CWM
Sent from my Sony Xperia Z3
Thanks for the topic. Anyone has a link for full 5.0.1 for EU WIFI version ?
Aanze said:
Thanks for the topic. Anyone has a link for full 5.0.1 for EU WIFI version ?
Click to expand...
Click to collapse
I flashed the NA one as someone mentioned that they seems to be the same - worked fine on my system.
Thanks for the feedback, trying it right now
terrigan said:
Ok so.. here's a quick guide to flashing 5.0.1 on the Nvidia Shield Tablet. I have the 16GB Wifi version so if you have a different version (LTE or non-US tablet) this guide may or may not apply to you. I also essentially dirty flashed this in CWM recovery. If you're using TWRP WIP, no idea if it will blow up or not. Standard disclaimer applies if your Tablet blows up or anything, i'm not responsible. You do these steps at your own risk. I'm going on the premise that you have the Shield drivers already installed and have some flashing knowledge.
This is an upgrade from 5.0 to 5.0.1
This guide DOES NOT utilize the OTA zip that your tablet downloaded.
1. Download http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29082_493.9700.zip (AGAIN, US 16gb WIFI only, there's another thread here somewhere with other full download links) I copied it to external SDCard rather than tablet storage.
2. adb reboot recovery to get into CWM or shut down and use the hardware keys to reboot to recovery
3. In CWM, install zip from external sd card and flash it like a normal rom. CWM reports this sucessful and reboot to 5.0.1 and let it settle. It updates binaries and blah blah. Oh also root and recovery are now gone. You should still have fastboot.
4. reboot into fastboot, hardware keys again or using adb reboot bootloader.
5. Now you follow the excellent post by sandrodjay for restoring CWM and root. (If you didn't wipe, most of the preliminaries in sandrodjay's post should already be done. Debug mode and whatnot) http://forum.xda-developers.com/shi...t-lollipop-t2972316/post57719881#post57719881
After the dust settled for me, i was on 5.0.1 and had CWM and root back. YMMV.
Click to expand...
Click to collapse
Does this upgrade method loose all data (like factory reset) or not loosing anything other than CWM and root? Thanks.
If you don't wipe, no. Everything stays.
layanto said:
Does this upgrade method loose all data (like factory reset) or not loosing anything other than CWM and root? Thanks.
Click to expand...
Click to collapse
I've got good news... Your data and apps remain untouched, only litle problem depending on number of apps is time to "optimize apps" on first boot after update
Thank you for this!
Aanze said:
Thanks for the feedback, trying it right now
Click to expand...
Click to collapse
Did it work?
Just to make it clear for all, I've flashed the wifi version....
Tried with all (really all) the recovery in XDA ending with error.
The only recovery that worked is the 6.0.5.0!!
Updated dirty flashed but ended with lag for me, so clean install, and now all is good.
(was unlocked bootloader)
Lost recovery and lost root of course, but with adb takes 2 minutes to put them back.
ciribaski said:
Just to make it clear for all, I've flashed the wifi version....
Tried with all (really all) the recovery in XDA ending with error.
The only recovery that worked is the 6.0.5.0!!
Updated dirty flashed but ended with lag for me, so clean install, and now all is good.
(was unlocked bootloader)
Lost recovery and lost root of course, but with adb takes 2 minutes to put them back.
Click to expand...
Click to collapse
+1 as I've also just flashed the full wifi update to 5.0.1 using CWM v6.0.5.0, without wiping data, and everything came back up nicely. Still giving the tablet a chance to settle in after re-rooting with SuperSU v2.40, but hoping that the extreme lag doesn't return. If it does, I suppose I'll have to try a full wipe.
One thing I noticed is that after the very first reboot (without rooting, immediately after flashing the update), the system was very busy, and this could have been due to FolderMount trying to mount folders on boot using root when the tablet was NOT rooted. I'd recommend disabling FolderMount from auto-mounting on boot if you have it configured that way.
Thanks for providing this full 5.0.1 update package OP!